I'm facing an issue after i switched to LineageOS (lineage-15.1_j21_20180602_NIGHTLY-o7prolte ). When i unlock the phone it takes a while to play and is laggy until i restart it. I read many forums saying about Deep Sleep and SOD and faulty ROMs. I tried reflashing but that too in vain. Only working solution is to have a wake lock via SODKiller app, Wakelock or similar apps but that comes at the cost of battery drain.
Can any one suggest a working solution?
Please don't spam this thread with "maybe solutions" as no previous thread mentions the exact solution.
Also my audio jack isnt working but thats not what im worried about
Related
Hello xda,
my girlfriend and I are using the latest nightlies from CM11 out of THIS thread since a week, and I want to report some bugs we expericened. I would post this in the official thread of the ROM, but I don't have enough posts to post in there. :/
So, here is a list of the issues we experienced:
- camera doesn't work --> not focusing, crashing (known issue that exists since a long time)
- freezing when you try to unlock it --> sometimes if you want to unlock it with pressing the power button it just does not respond, you have to restart it when this happens (only read once, so I don't know if I am the only one with this kind of issue)
- WiFi still does not work after the update 30012014 (also known, for a few people it works, not for us)
- battery life is pretty... awkward for us since CM11 (both of our C2's where in repair a week ago and both our batterys got changed, so it doesn't bugs because of this reason)
Hope I can contribute with this little listing to fix these issues, if you can, could you say to me how the fixing status is?
Greetings,
- sinkingFX
Hello people,
I have been experiencing a weird issue lately with my OPO. It seems that for no apparent reason, my accelerometer's X-axis gets stuck in 0.000m/s² value, resulting in the inability to rotate the screen to landscape mode. And, again for no apparent reason, it starts working correctly... until the time it breaks again!
It's really crazy. Last night for example it was broken, I was browsing xda from chrome just to find a possible solution, and suddenly it started working, device just turned from portrait to landscape! When I woke up it was not working again. Sometime around the afternoon it started working again -without me doing anything-, not even handling the phone, it was flat on my desk! After 8 hours of working, it got stuck again right as I was writing this post...
Even when it's stuck however, If I try to shake the device very hard (to the point that it almost flies off my hands) I get a very small reading, around ~0,050m/s² to ~0.200m/s².
(readings were taken with Sensors app)
A reboot does not fix this. I have tried lots of configurations, it's not app/xposed related since it also happens after a full wipe and after flashing the 44S fastboot image. It's not kernel related (I think...) since it happens both with Stock and Franco. So it's either hardware, or related to the ROM.
I believe (and really hope) it's not hardware related since it started a while after flashing 44S, before that the accelerometer worked flawlessly. Also, I may be ignorant here, but if it was hardware it would break down once and for all, it wouldn't work intermittently, right? Either way, the device of course was never dropped or hit so as to damage the sensor in any way.
I've also read one report of the exact same problem on the OPO forum, but could not contact the poster, and several other reports of the accelerometer breaking down (and later being fixed) but in CM nightlies.
I have already tried to calibrate/reset through several apps but without any success. Is there anything else I can try to, erm, "un-stick" it? Maybe there's a configuration file I need to delete or something or a specific way to reset/calibrate it in CM. Or even tapping the device in a specific place? (lol I'm reaching here, but I can't think of anything else).
I have already reported the issue to Jira, if someone is experiencing the same please provide your input here.
Hi there,
I'm experiencing massive issues with the Nexus 5 of my wife. Everything is basically broken
It started 2 days ago, the phone start rebooting without reason and heating a lot. Applications sometimes hang for a long time, or the screen stays black with only the notification bar displayed.
Wifi is never able to connect, even though the welcome screen is able to display available wifi. On the welcome screen after a fresh flash, nothing happen when I enter the WIFI password and try to connect. Only the "ignore" button is available, as if I have done nothing.
LTE connectivity seems to work, but I have removed the SIM card for further testing, so it's hard to say.
Parameters screen sometimes works, sometimes won't. Battery consumption screen never works.
The phone is never able to shutdown properly, it hangs forever on the shutdown loading circle; I always have to hard-reboot.
I changed the battery (I had a spare one ordered few days before the problem occurs just to see if it improves the battery life), with no luck.
When I opened the phone to change the battery, it is clear the heat come from the CPU.
I tried (I wiped everything each time in between):
- factory reset
- flash a stock rom from Google website (MMB29K)
- flash latest Cyanogenmod rom (ZNH0EAO2NM)
I have the same issues with any of those 3 roms. I captured some logs while running MMB29K and ZNH0EAO2NM:
Stock (MMB29K) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3M28tM2xjTmJKa28
Cyanogenmod (ZNH0EAO2NM) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3TVUtTmExZDBLUms
The only state where the phone is stable is when TWRP is booted, which is not so useful...
I'm thinking of a hardware issue, but is there anything else I can try? What do you think?
Thanks a lot!
Nobody?
I said the same thing in another post. The fact that flashing different ROMs with the same issues kinda point to hardware problem. I'd guess something fried on the motherboard and it's causing weird behavior. Funny thing, the other post also reported wifi not connecting issues, so I'm thinking there is something that breaks in older Nexus 5 phones that cause wifi issues along with other random reboot problems.
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.
Ever since updating to ColourOS11, android auto has been freezing on me when the screen is off however activating the screen will unfreeze it.
Is anyone else experiencing this or if anyone knows a fix besides 30m screen timeout.
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Craphead said:
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Click to expand...
Click to collapse
Yea I had a look through some other threads. Turning off AOD and Fingerprint while screen off seems to somewhat work abiet still glitchly. Been in contact with Oppo who seems to only want me to send the phone into the service centre but I am waiting for Christmas break to be over and send it then otherwise hopefully a update by then but doubts.
I just had the issue, but by leaving it plugged in and letting the connection time out, it reset and connected. Took about a minute.
I finally got the ColorOS 11 update and now Android Auto is having this issue. Really rather annoying as I've only just got a new car and had Android Auto so was enjoying it!
Basically same issue where the car screen just locks up until you unlock the phone screen (i still get audio prompts for directions in google maps etc so Android Auto is still running). Seems to be a standoff between the OEM's and Google. Looking at other forums some OnePlus phones have the same issue (BBK group thing perhaps!)
Google answer...
[FAQ] Can't connect to Android Auto on Android 11 - Android Auto Community
support.google.com
I solved this issue going into developer options and activating the "keep screen on while charging" mode. The display will remain on, but with a very low brightness level.