i'm sure many of you use widgetlocker. i much prefer it to the stock lockscreen, however i'm encountering some issues with it that i've never seen on my previous device (an htc thunderbolt).
first issue: i can't get widgetlocker to override the stock lockscreen on initial boot. i always see the stock lockscreen at first, and then if i turn off the screen and turn it back on, widgetlocker shows as it should. i've disabled the stock lockscreen in widgetlocker settings and even checked that setting that mentions showing widgetlocker on boot (forget exactly where this setting is, as i don't have my phone in front of me at the moment).
second issue: i think widgetlocker is interfering with trickster. i use trickser to set a custom color profile on boot (using the latest franco nightly with pa and i love me some halfbreed colors!). due to the first issue i outlined, my boots are sometimes a little flaky and then i end up with a notification from trickster about a "dirty reboot" and my color settings aren't applied as a result.
anyone else having trouble with widgetlocker? is there something i'm missing?
i'm running pa 3.60 (the latest beta) and franco nightly r154.
Related
Hi all. I've just been wondering... has anyone else besides me ran into countless problems using the Nexus Launcher/Launcher2 on their phone? I'm running Fresh 2.0d with the included .apk, and here are some bugs I've found:
Unresponsiveness
Screen turns black and stays black requiring a battery pull
Launcher will launch without displaying icons in the menu
Now, it is not only Flipz's ROM that has these problems either... it is EVERY ROM I've tried. I'm sure most of you will tell me to use Helix Launcher. I have tried it, but it doesn't have the same feel that the Nexus Launcher has.
Has anyone found a fix for these stability issues? If not, I'd like to start a project so we can get this working, because I'm sure it's completely possible. After all, Flipz was able to get the 2.1 lockscreen working!
mrinehart93 said:
Hi all. I've just been wondering... has anyone else besides me ran into countless problems using the Nexus Launcher/Launcher2 on their phone? I'm running Fresh 2.0d with the included .apk, and here are some bugs I've found:
Unresponsiveness
Screen turns black and stays black requiring a battery pull
Launcher will launch without displaying icons in the menu
Now, it is not only Flipz's ROM that has these problems either... it is EVERY ROM I've tried. I'm sure most of you will tell me to use Helix Launcher. I have tried it, but it doesn't have the same feel that the Nexus Launcher has.
Has anyone found a fix for these stability issues? If not, I'd like to start a project so we can get this working, because I'm sure it's completely possible. After all, Flipz was able to get the 2.1 lockscreen working!
Click to expand...
Click to collapse
I am running fresh2.0d and stock screen turns black and needs battery pull when I use camera app and hit back button or any button.
Launcher has been pretty responsive except here and there....
I do get to the mode where no icons on home screen for few seconds at times but it recovers pretty soon....
As far as the lock screen, I ran in to an issue while my corporate policy forced me to assign lock/unlock password! Soon I enable password and lock, phone stops responding!!! I have to either pull the battery or issue reboot command via prompt!!!
I hope this helps.... I am not a developer though....
I have been disappointed by the nexus launcher's performance as well.
The black screen requiring a reboot (or if you hold home and happen to have settings in the app switch menu you can force kill it and restart it) is a common occurrence with seemingly no pattern. Sometimes it after a long browsing session, other times its happens after deleting a single e-mail message and returning to the main screen. The only consistent way to make it happen is to hit back after launching camera from the app drawer.
Ive also noticed in every rom with launcher, that when coming out of the launch screen the app shortcuts and widgets on the home screen don't load instantly. Almost as if the launcher was killed while it was asleep and when unlocking it, it is reloaded.
It's disappointing because as you said, while helixlauncher is an OK alternative, nothing else has quite the same feel as nexus launcher. Unfortunately I think it will take a good bit of modification to make it a perfect match with the hero and I have absolutely 0 idea where to even begin .
Flipz, if you ever read this, could you offer some insight on this? You've worked your magic on the 2.1 lockscreen
The only rom i had it running great on was Darchlegend v4.1 i think it was, i finally said forget it and started using helix
Every one i have tried has been buggy as well. Things mught improve once we get the hero 2.1 source. Or once google decouples them.
There's this little bug that's been really pissing me off lately, and has forced me off any ROM based on AOKP.
When you click the recent apps button, the animation shows a screenshot of a different app, usually the one you opened first (For example, when you first open up settings, the animation shows a screenshot of the settings app contracting, then when you open up GPlay, the contraction animation still shows the same screenshot from the settings app)
I know it's not from either CM or PA because neither ROM has it. For some reason, PACMan is also free from this bug. Literally every other ROM that's based off AOKP or is AOKP has it though.
What I'm wondering is, is there a quick fix for this (I know the PIE screen sticking bug was fixed by enabling HW overlays, I'm looking for something of that sort)? AOKP has, by far, the most options out of any ROM for statusbar and navbar customization and I want to be able to use the vast majority of the ROMs on Original Dev and Android Dev.
And yes, I am autismal about this stuff, check your cis privilege, scum.
I am on the official CM10.1 RC2. I didn't flash anything else other than a fix for Wi-Fi ARP when in sleep mode, as well as an older radio to enable LTE.
What has been going on every since I flashed my first CM10.1 nightly (got the phone on May 2) is that every other time I wake the phone, the lockscreen widgets disappear.
This is a 100% predictable and totally consistent pattern. If I wake the phone and my lockscreen widgets are visible, then the next time I lock the phone and wake it, the lockscreen widgets disappear. If I wake the phone and my lockscreen widgets are missing, I can guarantee they'll come back if I immediately lock and wake it again.
I know it's not an Android 4.2 problem, because my sister's HTC One S doesn't have this issue and it's set up the same way.
To illustrate what I mean, these are the two states my lockscreen always alternates between:
Been trying to find an answer for this... maybe I'm not using the right keywords :/
EDIT: SOLVED - Turns out Lockscreen Policy was the culprit. I disabled both widgets and camera and that was causing cLock to disappear every other time. Allowing widgets while disabling the camera eliminated the problem. Hope this helps others in the future!
Make sure you don't have two lockscreen clocks. If so, delete one.
Sent from my Nexus 4 using xda premium
El Daddy said:
Make sure you don't have two lockscreen clocks. If so, delete one.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I don't think I have two clocks. All I can find in the settings is the "Clock widget" in the Lock screen section which is what I want to use.
Any idea where I might have accidentally placed a second clock if that's the case? I didn't download any clock or calendar apps - I use the stock ones. I did restore a lot of stuff from Titanium backup on my old phone, but I clearly remember that system settings wasn't something I restored.
edit: I checked Titanium Backup and noticed that the "Clock" app (not the cLock app/widget) had been restored from my previous phone which ran CM10, not CM10.1. I remember that on CM10, the clock was right-justified, not centered, and that is what my 2nd screenshot (the scenario I want to get rid of) is showing.
Is it possible that I inadvertently restored the CM10 lockscreen clock from my old phone? I hope that doesn't mean having to wipe. I really can't find anything in the settings that might indicate the presence of more than one clock.
EDIT: SOLVED! It turns out that the Lockscreen Policy app was the culprit. I had disabled both widgets and the camera in Lockscreen Policy because I don't want people messing with my phone as a joke (otherwise what's the point of a PIN...). Re-enabling the widgets while keeping camera disabled solved everything. I confirmed that disabling widgets in Lockscreen Policy would immediately bring back this problem.
Tbh, I'd prefer having the old CM10 lockscreen, without those side widgets or the camera, and the ability to slide to a ring shortcut before bringing up the PIN
I just updated from CM10.2 to the latest CM11 nightly with a dirty flash (wiped cache and dalvik and flashed gapps)
I lock my phone with a PIN code. My settings are to have the widgets minimized with the PIN entry area immediately accessible when I wake the screen. In this mode, the clock is still visible and a smaller-sized version of the weather is also visible on top of the PIN entry area.
But on CM11, I see this instead:
http://i.imgur.com/bI4pMlQ.png
As you can see, the weather widget failed to minimize properly and is being partially obstructed by the PIN entry area. I checked the settings and the "show when minimized" is checked - as it was on CM10.2.
Anyone got a fix for this?
I should also note that if I UNCHECK the "show when minimized" box, the weather widget also doesn't disappear when the PIN entry area is empty (it would have disappeared on CM10.2). Instead it behaves exactly like described above.
Just realized this is an ongoing issue with CM11 that isn't resolved yet.
In the meantime, I downloaded the DashClock app which is more or less identical to CM's own LockClock app, and the weather widget minimizes properly with this one - now I restored the visual appearance to what I had in CM10.2. Not the most convenient solution, but pretty simple and elegant (no complex file modification needed, haha).
Case closed, hope the CM team resolves this soon...
I have a separate question regarding the new yahoo weather powered lock screen widget that rolled out with CM11.
I have CM11 installed on my Nexus 5 and just updated to the 2/10/14 stable which came with this lock screen widget from Yahoo. I don't see the widget as an installed app either in apps or widgets and I cannot find a settings for this widget.
I want to manually set the zip code and change the readout from Celsius to Fahrenheit but cant figure out how.
Any ideas?
I have noticed minor issues cyanogen 12s issues on the ONEPLUS ONE. Anyone with issue can can report them here. Hopefully everyone here has a work around or modification to fix the issue.
BT headset, have 3 different one. Pressing the button will kill the call while on GV. IDEAS?
I'm occasionally seeing the lockscreen flash up when turning the screen off.
Also, if there's a way to disable the lockscreen transparency I'd be interested to hear it - it looks rubbish.
Seeing the old issue of the notification drawer appearing in/after calls, too. Hadn't had this for a while on latest nightlies
benj! said:
I'm occasionally seeing the lockscreen flash up when turning the screen off.
Also, if there's a way to disable the lockscreen transparency I'd be interested to hear it - it looks rubbish.
Click to expand...
Click to collapse
Set a wallapaper through Theme and click the wench thingy and find edit lockscreen wallpaper
There's also a bug you could use the physical buttons for idk what reason to fix it go to settings and disable then enable the on-screen keys
another bug my settings keep crashing for no reason ._.
Lag on launcher3 while opening the app drawer.
Tarun95 said:
Lag on launcher3 while opening the app drawer.
Click to expand...
Click to collapse
I solved doing the setup again after wipe...
Tarun95 said:
Lag on launcher3 while opening the app drawer.
Click to expand...
Click to collapse
yes same here!!
Google play services wakelock still exists....
L10nH34Rt said:
Google play services wakelock still exists....
Click to expand...
Click to collapse
Go to Google play services in privacy guard and deny it the permission to keep awake. Then reboot.
---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------
fbr79 said:
I solved doing the setup again after wipe...
Click to expand...
Click to collapse
I don't want to reset my phone lol. Everything is working fine other than that.
color os camera problem
It worked perfectly on kitkat .
After updating to lollipop (official update) cm 12s , it seems to show some problem.
I can't see any live preview of the effects. It just shows the normal camera without any effects. But after I click, the picture comes with effect. So its just a problem about the live preview of the effects. Has anyone else experienced this problem ? Plz help me.
The now infamous two halves in pictures with flash are still there. I wonder if the community could extract the camera driver from oxygenOS kernel sources (when OP will finally release them) and use them, since it doesn't happen on that ROM.
Tarun95 said:
Go to Google play services in privacy guard and deny it the permission to keep awake. Then reboot.
Click to expand...
Click to collapse
I prefer using this method. Much cleaner IMO.
benj! said:
I'm occasionally seeing the lockscreen flash up when turning the screen off.
Also, if there's a way to disable the lockscreen transparency I'd be interested to hear it - it looks rubbish.
Seeing the old issue of the notification drawer appearing in/after calls, too. Hadn't had this for a while on latest nightlies
Click to expand...
Click to collapse
I think the lockscreen flashing after the screen turns off is a lollipop thing. I noticed it when I had a nexus 5 and upgraded to 5.0. I think I noticed it out of the corner of my eye so to speak, after I had set my phone down and the screen timed out, thought it flickered/flashed but that's just the screen off animation now.
Still playing around with all the settings to see what's new (and removed) and noticed:
No longer have the ability to configure the auto-brightness settings which I actually quite liked in 11S if for no other reason that I could set the auto brightness for low light down to 0% (instead of the, what... 5% normal setting?).
Screen Color calibration wouldn't work and crashed the settings app (screen went black and I couldn't get back into settings). A reboot seems to have fixed it.
The settings app may just be buggy as it crashed again when trying to access Developer Options (screen went black and required a reboot).
EDIT: Couldn't sign into my Cyanogen account but that could be a problem on Cyanogen's side as it didn't recognize my account.
Still seems like there are a lot of new things to try and there are more options than Oxygen OS.
Switching profiles:
from owner to guest: Cyanogenmod-log crashes
from guest to owner: code to unlock phone isn't shown and no matter what you type, it always incorrect. Fixed by rebooting
Fr3lncr said:
Still playing around with all the settings to see what's new (and removed) and noticed:
No longer have the ability to configure the auto-brightness settings which I actually quite liked in 11S if for no other reason that I could set the auto brightness for low light down to 0% (instead of the, what... 5% normal setting?).
Screen Color calibration wouldn't work and crashed the settings app (screen went black and I couldn't get back into settings). A reboot seems to have fixed it.
The settings app may just be buggy as it crashed again when trying to access Developer Options (screen went black and required a reboot).
EDIT: Couldn't sign into my Cyanogen account but that could be a problem on Cyanogen's side as it didn't recognize my account.
Still seems like there are a lot of new things to try and there are more options than Oxygen OS.
Click to expand...
Click to collapse
no problem like yours.
but there's no led notification (when lock and screen on) only ambient flashed-up display.
i do agree that autobrightness is not working like in cm11s.
But, i do have those problems after flashing from stock cm11s 05Q and via bootloader with fastboot image from the cyngn.
And cm12s from cm11s is have this kind of lagging typing/touching to be compared if you were flashing from cm12/cm12.1, strange indeed.
I'm back on nightlies. CM12S ain't for me, thought OxygenOS was better
Lags on interactive governor
Hi guys, did you notice any lags on interactive governor in games ? It lags on cm11s too, I thought that they will fix it in today released cm12s. It didn't happen before brick of my phone, since unbrick and flash of cm11s, games are lagging so much on interactive governor. Do you know how to fix that without any change of governor, hotplug or profiles ? Thanks a lot.
Com. Google. Gapps. Continual fc so rapid about impossible use phone.. Back to O2 for now which is very smooth
All of you with issues, did you dirty flash or wipe first? it DOES matter...