OpenLauncherTeam / openlauncher

Customizable and Open Source Launcher for Android
Apache License 2.0
1.41k stars 413 forks source link

[Meta] Widget Issues - Cannot add certain widgets, crashes etc #645

Open gsantner opened 3 years ago

gsantner commented 3 years ago

This is a meta issue for Widget related issues. Users tend to open issues and feature requests over and over again for Widgets without using search. Use this topic to talk about Widget issues, feature requests, crash logs, ... as well implementation and opening pull request.

Currently nobody is working on OpenLauncher Widgets code, so why YOU who reads this message, not steps up? :wink:

sudomain commented 3 years ago

Regarding #560 and other crashes related to widgets, the issue template is rather vague about what kinda of logs would be useful for the devs. I no longer use OpenLauncher, so #560 is no longer a problem for me, but I realized that I neglected to include logs because I didn't know how to get them. Just thought I'd mention it in case other crash reporting users run into it.

Best of luck with this launcher

Catfriend1 commented 3 years ago

Ok.

woutput commented 3 years ago

+1 for #567 And thank you for this launcher, I think it's one of the best.

adamwong246 commented 2 years ago

This is the one issue preventing me from using OL as my daily launcher. Until, then, it's just a pet-project for me. However, I've got the code running on Android Studio and I'll see if I can carve out some of my schedule to debug some widget crashes.

gsantner commented 2 years ago

Help is totally welcome.

barbeque-squared commented 2 years ago

I'm not sure if this qualifies as a widget or is something else, but if my screen has been off for a few hours (sometimes less time, more often overnight) that when I turn it on again, the screen only shows the wallpaper but nothing else. I'm not sure if this is Android killing the launcher or something else. It happens fairly consistently about once or twice a day. Just pressing a few buttons (home, task switch) or turning the screen off and on again fixes it.

At first I thought it was my (only) widget causing this (NetSwitch) but removing that still triggered it just as often, so I put that back and tried something else. A couple of days ago I disabled the search bar (which also hides the date, sadly) and I haven't experienced it since then. It also feels like it's using less battery, or maybe it's just taking longer to manifest now, but either way, I thought I'd leave this here if anyone else comes searching for it.

Specs: Android 11 on Alcatel 1S 2021.

It's not a dealbreaker for me, I have so few apps everything fits into one page anyway.

Soundtoxin commented 2 years ago

when I turn it on again, the screen only shows the wallpaper but nothing else. I'm not sure if this is Android killing the launcher or something else. It happens fairly consistently about once or twice a day. Just pressing a few buttons (home, task switch) or turning the screen off and on again fixes it.

When this happens, can you access the mini bar and then go to OL settings -> advanced -> restart? I get a similar issue, seemingly when switching between apps and home screen back and forth too fast, like when setting up split screen apps.

Soundtoxin commented 2 years ago

I recently ran into an issue setting up OpenLauncher on a new device. I added the termux widget to my homescreen, and it didn't appear where I wanted it. However, I was unable to move it or remove it. Recently I added it a second time, and now I'm stuck with both I think. I get a vibration feedback when long-pressing it, but no options to move/resize/delete. I wish I could enter an "edit mode" to show the controls by every app/widget to work around it.

Using Android 11 / LineageOS 18.1 on a OnePlus 8T

edit: I just tried a little harder and managed to move one, and remove the other. I quickly locked the homescreen and backed up my settings in case I mess it up... The remove options don't show long enough, I think.

barbeque-squared commented 2 years ago

can you access the mini bar

I have the mini bar disabled

darioandreella commented 2 years ago

I have the same kind of issues plus random crashes/restarts on Android 11 (LineageOS 18.1 vanilla/no gApps on a OnePlus 3T). I agree with who rated this launcher as one of the most feature rich, but it is a pity that it feels quite abandoned.

What I experience:

I could add as a final note that the resizing of the widgets done with those 4 little arrows is quite inconvenient, one can resize only to the right and downwards, and can not move the widget while resizing. I would appreciate so much if the moving and resizing was integrated into one single drag-and-drop operation, like most modern launchers do.

I am still using OL as my daily driver while dealing with this bumps, and can not find any valuable alternative. I came from Nova Launcher in the ages of non-open-source stuff, then went with LawnChair that worked fine but got left over, and landed here so far.

What I love and make OL standing out of the "minimalistic crowd":

All the other launchers always miss one or more of these points.

Thanks guys!! Cheers Dario

osirisinferi commented 2 years ago

@gsantner I'm pretty sure this meta issue, covering multiple issues, wasn't closed entirely with 3c1ab2f?

E.g. #596 was closed in favour of this meta issue, but is an issue still. Also note that #596 was not restricted to widgets per se.

ei14 commented 1 year ago

Issue is not fixed. I suggest this issue be re-opened, or I shall create a new issue. Open Launcher continues to interrupt other apps with a pop up saying "Create a widget and allow access?" Even when the launcher is not visually open, the pop up appears.

It interrupts whatever app is running and suspends it, sometimes erasing progress. For example, while watching a YouTube video in the YouTube app, the OpenLauncher pop-up may appear, closing the YouTube app and resetting the video's position in time. It makes the launcher quite unusable.

This specific issue was noted in #573, but the issue was closed in favor of this meta-issue. Shall I create a separate issue?