I'm wondering if anyone else is has this problem. Every time I plug in my phone, the USB debugging option turns on. I turn it off in developer settings, but it turns back on as soon as I plug it in.
Also, I change my screen timeout to 1 minute but when I restart the phone, it turns back to 30 seconds. I already tried the fix permissions option in Recovery and it didn't work. I'm using the Viper ROM if that helps.
Also, I always turn Auto Sync "on" under settings but it turns itself back off.
Anyone else with the same problem?
Anyone?
There's a known bug with some settings not sticking on reboot if I recall but what your describing does not seem to be this bug. Typically when weird little issues like this are happening, step one is to redownload and check md5 wipe everything and do a fresh flash. Obviously this would be a big issue, well documented for a ROM as popular as Viper XL so I would say no, other people are not experiencing this issue.
Thanks anyway. I'll Google it some more and see if I find something
Hey there, I have kind of trouble with my PQ.
The PQ sometimes fails to boot correctly.
Booting the PQ results in a short (a few seconds) backlight and then dark. (Important: No picture or text is shown!)
Then there are two errors I've experienced so far:
- after the backlight is dark, I press a button (POWER/VOL_UP-DOWN/CAMERA) and it vibrates. After a few times of pressing and vibrating, it vibrates long and it then seems to be off. Since the backlight is off, I can't know if it's really off.
- after the backlight is dark, I do nothing except sliding out the keyboard (backlight is off). In this error it seems to start "correctly", because after some time the keyboard backlight goes on. That means, that "android" has bootet and is waiting for password entry (because of encrypted phone).
Either way, I have to reboot several times until it boots correctly. (With some luck it takes only 2-3 times.)
Some notes:
- I have to put my sdcard off, because the password entry doesn't appear if it's in. (ext4 filesystem, android seems to want to decrypt that -.-)
- [needs more testing] The phone has had force resets. I think it was my Access Point/Router, causing the WLAN (or qualcomm SoC) to hang. I changed the screen-part (touchscreen+display etc.), seems not to help. (I also disabled that Access Point/router, so I'm still waiting for a force reset.)
- [needs more testing] Sometimes the SIM-card and/or sdcard is not recognized after a reboot/cold boot. I have to reboot to get it back to work. SIM-card recognition may take more than one reboot.
What's in /system?
- CM11 M11 snapshot
- gapps
- XPosed framework (it boots and everything actually works fine)
...if I forgot anything, I will notice that in a later post or edit this and notice in a new post.
I also have a problem with wakeups again (started just a few days ago, after uninstalling two apps...). That's weird, but I can't find the cause. Neither in the XPosed Logs nor in catlog. I need to investigate it further.
I tried to be very exact and I've put anything that might be relevant into this post.
If you have any ideas (no matter how implausibly they are), post them. I am out of any ideas.
It might be helpful to get a log when it boots "incorrect", but I'm sure it's not written anywhere inside the system.
The good thing is, my wakelock problem "disappeared".
The PQ is having deep sleep again.
I have no idea what the wakelock caused...
No force reboot so far.
Another good thing: the force reboots are gone after disabling the AP/router which probably was the cause.
A stable week for me, the phone didn't crash at all.
Of course the other issues stays.
Saturdays (today) the phone is being rebooted by Titanium Backup. Like a wonder, the phone chose to show the password input (encrypted phone; with sdcard inserted).
After entering the password and some boot-time, the mobile part (SIM-card etc.) chose not to work.
A reboot didn't help and I've got into the annoying problem, that I get a blank black screen with backlight but it boots "normally" (without anything displayed).
It took about 20-30 minutes with trial and error on getting it up with the mobile part again.
BUT: I've found today something new, beside the issue this morning.
Bluetooth seems to be enabled always! It's probably caused by Llama (android app).
Needs also further testing, just wanted to write that somewhere down, so I don't forget.
More details: After disabling it, my "PS3 headset" wanted to pair with "all" devices nearby.
I got pairing messages on the PQ even with disabled BT.
Loader009 said:
Another good thing: the force reboots are gone after disabling the AP/router which probably was the cause.
Click to expand...
Click to collapse
(If anyone cares) the force reboots are gone after setting preamble to "long" (PQ malfunctioning if set to "short") in the router.
The other problem persists but are not that bad because it happens rarely that I need to reboot (soft reboot is mostly enough).
Hi folks,
There are two issues with WiFi on my Nexus 5. The first, which was happening before I upgraded to Lollipop, is that my phone no longer remembers WiFi passwords and I have to re-insert them every time. I've searched around for this and been told that it's because Android only remembers a certain number of passwords so I've tried forgetting quite a few old WiFi access points but to no avail. Any ideas on this issue?
The second issue has only started occurring since I upgraded to Lollipop and is driving me nuts. Basically I can only very rarely access the WiFi menu in settings now, making it near impossible to connect to new access points. Pulling down the notification shade and tapping the wifi icon just seems to turn it on and off rather than taking me to the WiFi area in settings - is that right? And then if I go into settings and tap on WiFi the screen goes blank and I get a force close message. Very occasionally or after re-starting settings a few times it will work.
Any thoughts on either issue would be much appreciated. I've read the thread on WiFi not turning on but don't think that's the issue and as I say the latter issue has only occurred since the Lollipop upgrade.
Thanks
Alex
With the quick settings, you have to tap the network name to go into the wifi options. The wifi pie slice thing turns it on the off.
Sounds like you could use a factory reset to fix your other problems.
Dr Doom said:
Hi folks,
There are two issues with WiFi on my Nexus 5. The first, which was happening before I upgraded to Lollipop, is that my phone no longer remembers WiFi passwords and I have to re-insert them every time. I've searched around for this and been told that it's because Android only remembers a certain number of passwords so I've tried forgetting quite a few old WiFi access points but to no avail. Any ideas on this issue?
The second issue has only started occurring since I upgraded to Lollipop and is driving me nuts. Basically I can only very rarely access the WiFi menu in settings now, making it near impossible to connect to new access points. Pulling down the notification shade and tapping the wifi icon just seems to turn it on and off rather than taking me to the WiFi area in settings - is that right? And then if I go into settings and tap on WiFi the screen goes blank and I get a force close message. Very occasionally or after re-starting settings a few times it will work.
Any thoughts on either issue would be much appreciated. I've read the thread on WiFi not turning on but don't think that's the issue and as I say the latter issue has only occurred since the Lollipop upgrade.
Thanks
Alex
Click to expand...
Click to collapse
I haven't ever encountered #1, so I can't help with that. However, with #2- touching the icon will turn wifi (or bluetooth, etc) on and off. If you touch below the line (where it says wifi, bluetooth, etc) it will open the settings menu. It matters where you tap.
anactoraaron said:
I haven't ever encountered #1, so I can't help with that. However, with #2- touching the icon will turn wifi (or bluetooth, etc) on and off. If you touch below the line (where it says wifi, bluetooth, etc) it will open the settings menu. It matters where you tap.
Click to expand...
Click to collapse
Thanks for the replies chaps - I hadn't realised that tapping on different bits did different things. Regardless of whether I go in through the settings 'cog' or by tapping on the word 'WiFi' under the pulldown shade though the next screen is still blank and I get a force close message. In fact today one of the times I tried it the phone just froze on a white screen and only holding down the power button for ten seconds allowed me to turn it off and use it again. Anyone had any similar issues?
I'm having the same issues as you (both of them), and I'm also looking for the solution to it. For the first one, I'm trying to disable backup and renabling them. Read online that sometimes there's something wrong with the sync. Not sure if it solved the problem but will try.
For the second one, the problem is because it takes a very long time for the phone to search for wifi hotspots. So if you turn on wifi (ie clicking on the big button) and wait for about 2 minutes for it to search, wifi will work find. However, the 2 minutes is a long painful wait.... Im not sure what is the reason for the wait though, my nvidia shield tablet has no such issues.
Anybody has any solutions?
Dr Doom said:
Hi folks,
There are two issues with WiFi on my Nexus 5. The first, which was happening before I upgraded to Lollipop, is that my phone no longer remembers WiFi passwords and I have to re-insert them every time. I've searched around for this and been told that it's because Android only remembers a certain number of passwords so I've tried forgetting quite a few old WiFi access points but to no avail. Any ideas on this issue?
The second issue has only started occurring since I upgraded to Lollipop and is driving me nuts. Basically I can only very rarely access the WiFi menu in settings now, making it near impossible to connect to new access points. Pulling down the notification shade and tapping the wifi icon just seems to turn it on and off rather than taking me to the WiFi area in settings - is that right? And then if I go into settings and tap on WiFi the screen goes blank and I get a force close message. Very occasionally or after re-starting settings a few times it will work.
Any thoughts on either issue would be much appreciated. I've read the thread on WiFi not turning on but don't think that's the issue and as I say the latter issue has only occurred since the Lollipop upgrade.
Thanks
Alex
Click to expand...
Click to collapse
Both of these issues sound like you need a factory reset
rootSU said:
Both of these issues sound like you need a factory reset
Click to expand...
Click to collapse
I tried to do a factory reset yesterday. Took me a really long time but failed. So i ended up having to sideload the 5.01 factory firmware, which formated my entire phone.
In any case, it did not work. It still takes me a very long time 'turning wifi on...'
Any other suggestions?
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
jfpesant said:
Am I alone ?!
Lineage OS works fine, for a couple of days, then, out of nowhere, the homescreen and menu buttons are not responsive. Then, upon reboot, homescreen turns black, showing nothing except the status bar. The status bar can be swiped down, but everything you click is not responsive.
Wiped Dalvik and cache, issue is still there...
* After a reboot, the device shut down inexplicably. Upon next reboot, issue resolved... WTF is going on?!
Click to expand...
Click to collapse
I have the exact same problem! Installed LOS on Friday evening and it worked great until Monday afternoon. Screen was on and had full notification bar contents - it looked like the phone was working properly. It could even take calls, receive emails and texts, but the rest of the screen was black and the buttons reset to original settings and didn't even work correctly. The Home button did nothing except a double tap would create a brief white border around the edge of the whole screen. A single press did nothing. The back button worked properly. The switcher button did nothing at all. I think it was doing the Google assistant thing. Holding in the power button was setup to press restart and then give restart options, but it was reset to just restart and confirm.
Restarting never worked to correct it. Wiped cache and Dalvik cache, still no go. Letting it sit for over 30 mins did let it recover once and one other time while driving it went from this black state to fully functional for no reason. It was good for a few minutes and then the buttons stopped working again. The soft buttons did not help either. They behaved badly as well.
It seems to have no pattern. I wiped the phone and flashed the newest LOS on Monday evening and it worked great until tonight. I have no idea what is going on!
Glad to know I am not the only one... Just need a permanent fix!
Nice, a brother !
The back button worked properly.
Click to expand...
Click to collapse
Same thing here.
Also, I can't tell if receiving calls work, cause I didn't try, but I can confirm the quick settings tiles keep working. The drop down notifications show up, but clicking an individual notification won't bring up the app it is refering to.
So far, the "shutdown, wait a little and reboot" seems like the only thing resolving the issue temporarely. So yeah, before wiping everything and reflash LineageOS, keep calm and wait !
Also, be sure to do a backup your working OPO/LineageOS phone in TWRP mode, so you don't waste time reflashing OS, restoring apps with Titanium Backup and restoring settings manually, like I did three times over the past two weeks...
Too bad we don't see the changelogs with each weekly LineageOS builds releasing or any bug report compilation.
I am conducting some trial and error testing to help isolate the problem. So far it feel like it is related to profiles, specifically with either a trigger or disabling the lock screen. It seems when I add a profile to unlock and disable my lock screen via a wifi "on connect" trigger, that is when things seem to go down hill. generally shortly after is when I get the black screen. I am using the Pixel launcher and have added a Home profile with triggers for wifi and then set my lock screen to disabled. I am currently using the default profile and have not added any others and the phone seems to work well with no issues. It is still too early to say that is the problem, or even exactly what the specific problem is, but I will continue with the default profiles as-is for the next few days or week to see if it remains stable.
Maybe this will help steer someone else to find a fix...
Also this has just happened to me.
All was working fine for a few days since flashed now have same issue as above
Also had Profiles set up for home network for lock screen and sync etc
Phone is Redmi Note Pro 3 though
Stumbled across this while looking for info on this issue
https://www.nico-maas.de/?p=1537
That link is going down the exact same path as I am. Coming to the same conclusions. Thanks for posting it.
With the default profiles in use, I no longer get the black screen and everything is working fine. I will need to keep an eye on the change logs to see if a profiles fix come down the pipe.
For me, it was changing the Lockscreen to none (from pin) that caused the black screen. That link defiantly helped me out. Only thing I did was edit the "profiles.xml" and changed '<screen-lock-mode>' to 0 instead of 2
Yep, also using System profiles to disable lockscreen at home or in car.
Lately, I get no issue at home, but only in car, where my system profile is also setup to activate hotspot when Bluetooth connected to my radio. As soon as hotspot turns off, issue is resolved.
On another side, I mentioned earlier that LineageOS doesn't list its changelogs. I was wrong. You can find them here : https://www.cmxlog.com/14.1/
Fixed!
I experienced the same problem today with my OnePlus 2. Guess time does heal. I waited for a good half an hour and it seemed to fix itself.
When the screen is off, hold down the power button for a second and you should see the power menu. Select 'restart' and let the phone reboot. Simple as that!
Tell me if the problem still persists.
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Help me
I got issues with LO, my back, home, recent buttons not working (capacitive) so I'm using on screen button. But after all happen, now I'm having problems with my volume button, it didn't work at all, already restarting my phone many times, also, chance the system profile to default, sadly, it didn't help. Can someone help me with it.
This is not a new issue. I first encountered on CyanogenMod 3 years ago, and I'm disappointed to find that it still hasn't been fixed in
Lineage os. In CyanogenMod disabling "reduce power consumption" in the adaptive display section resolved it. But now with lineage is there doesn't seem to be any specific setting that causes it.
had the same issue - pretty sure it has something to do with "Profiles" set up. For instance, I set up profiles for turning off Lockscreen when Home - using the WiFi detection.
After a restart, the screen went black, but funny enough, the quick menu and the Bar still showed up. I turned on Airplane mode, to switch to the default Profile - which enables the Lockscreen when not in wifi and restarted. That worked.
So I think something with the Lockscreen + Profiles is a bit buggy.
It only occurs after a reboot.
I am using LineAge OS for M7 14.1 - which runs great!
AD
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
taalojarvi said:
Still having issues.
Notification cannot be seen , I can only hear them.
I haven't configured any profiles.
Home and recents don't work.
Can't open developer options, its says its not available for this user
Anyone have ideas ?
Click to expand...
Click to collapse
romap0 said:
Have the same problem. Tried to update Lineage OS, but it didn't work out. Can anybody help me?
Click to expand...
Click to collapse
I solved this by clean flashing ( Data wipe + LOS Reflash ).
It's a Known LineageOS source bug ( according to their reddit )
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
I have a Nexus 10 running the latest 7.1 Lineage image and had the same problem after updating the system and the GApps... here’s how I solved this problem on my tablet... maybe it will help someone else...
1) Use TWRP as your recovery loader
2) Backup your image using TWRP
3) Install the latest GApps - I use the Nano version
4) Wipe the Cache after the install is complete
5) Reboot and wait for the system to settle
6) Reboot into recovery (TWRP)
7) Install the latest Lineage (I use nighties)
8) Wipe the Cache after the install is complete
9) Reboot and wait until everything loads
10) Problem solved.
So... install GApps over the existing install... reboot let it do it's cleanup, then reboot into recovery and install the nightly update... wiping the cache of course... its worked for me three times now.
AlexInvar said:
I've started getting this as soon as I tried getting the first time setup to work again. Try this:
adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
2. adb shell settings put secure user_setup_complete 1
and if it doesn't work try adb shell settings put secure user_setup_complete 0
Click to expand...
Click to collapse
Great! Setting secure user_setup_complete to 1 seems to work for me.
EDIT: Nevermind, the problem only occurs when I connect to wifi with the screen off, which I didn't test. So no solution yet.
hello there! i have a similar bug on lineageos 15.
everything worked fine until today. no new apps installed or settings changed.
i flashed on 1. December and im really happy with this ROM, but today the hardware touch-keys stopped working correctly. The back button is ok, home button don´t work (except the double-tap function which starts splitscreen) and the menu button wich is set to swich last app with a single tap and show all open apps with a long tap opens the app-menu instead (that function that we know from android 4...).
after rebooting everything start to work again but only for a random period of time.
sry for errors or bad english...
i hope it will be patched cause the ROM is really one of the best i had.
I just turned off wifi scanning in setting and now every time I unlock the phone there is a notification that you have to dismiss. Tried everything can't get it to stop showing. Attached image.
Found a temp fix, on another forum.
Try it out, worked for me
https://forums.androidcentral.com/g...8-annoying-wifi-scanning-popup-wont-stop.html
jsowen321 said:
Found a temp fix, on another forum.
Try it out, worked for me
https://forums.androidcentral.com/g...8-annoying-wifi-scanning-popup-wont-stop.html
Click to expand...
Click to collapse
Thx a lot I did fix it by turning wifi+ off before I saw your reply.
Mine started doing the same thing after a reboot this morning. I turned off WiFi + and it still did it. I just hit Cancel on the pop-up when I seen it again and haven't had it come up since.
I updated Google play services after uninstalling the updates and it seems to be gone for now.
Mine randomly started showing this popup one morning, every single time I unlocked my phone. I checked location settings, found WiFi scanning was turned off. Turning it back on didn't fix the issue as WiFi scanning kept turning back off.
The only fix for me was to carry out a factory reset.