Database Users

[Q] Random Restarts

Hey everyone,
I just put the cyanogenmod 7.0.2.1 on my HTC EVO 4G about a month ago. At first it was working fine, now it will just randomly restart not while I'm ever using it, but when it is sitting idle it will just restart at odd times. Has anyone else had this issue?
Everything else with the ROM is working awesome. Please Help.

No issues here, why don't you come up to date and flash the stable 7.0.3.1. Are you running any custom kernels by chance?
Here's the link to 7.0.3.1 just flash over your current rom and wipe dalvik-cache.
http://mirror.teamdouche.net/get/update-cm-7.0.3.1-Supersonic-signed.zip

Oh thanks, been really busy with work, and hadn't had time to check for any updates. I appreciate the help very much. DL'ing the new ROM now.

Upgrade to the newer version. Maybe it'll help? Definitely clear cache & dalvik when you update.
Evo 4G / CM 7.0.3.1 - Tiamat 4.0.2 SBC / XDA Premium

I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App

misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What ROM did you go to?

misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.

dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
Yeah I like the CM7 ROM, but just can't take the restarts. I am going to upgrade to the newest stable release and see if that fixes it. I would like to stay with the CM7 if at all possible.

Swype
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?

beaukincade said:
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
Click to expand...
Click to collapse
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.

dirkyd3rk said:
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
Click to expand...
Click to collapse
no its gone and won't let me use titanium backup to reinstall it either

beaukincade said:
no its gone and won't let me use titanium backup to reinstall it either
Click to expand...
Click to collapse
Do you have the latest titanium backup version? If you can't get it going the swype apk is all over the place lol. *wink wink*
Get the latest version (beta) from their site.
http://swypeinc.com/

dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
I have ran many different roms and CM7 was the ONLY one that caused my phone to reboot many times a day. A quick google search can show you threads about owners who had phones that bricked after running CM7. I never said it was gospel, I just dont need my phone rebooting multiple times during the day and it was way more often when I had wimax connected. CM is a great rom but its not the second coming of Android and not worth my phone rebooting during the day.
And I am running Smooth N Sexy V1.2 A sense ROM that looks like gingerbread.

Reboots
I've been through several ROMs now and the reboot problem appears to be not a ROM issue!
Here is the story. I had started with Baked Snack, very good, but I wanted more battery and to try CM and get away from Sprint messaging update nag.
CM worked great, I updated to 7, until the reboots started to happen during heavy use of Angry birds.
So I restored to early CM 6.x, and reboots continued off and on every few days, getting progressively worse.
So I tried Warm 2.2, same issues.
I went back to CM7 and still trouble.
I went to Fresh and It was fine for a week, and then on Friday, (I noticed that Friday was significant), reboots again.
So after a month of this the reboots are so bad that I can't use the phone. I called Sprint, de-provisioned the EVO, went back to my Palm, and then unrooted and went back to Stock ROM, but with no Cell access.
The phone is stable now. As long as it's off the Sprint Cellular network!!!
All of the reboots were related to cellular activity. Messages coming in, ads being updated, calls coming in, tower switching, roaming, or worse of all, no tower signals at all.
I will post back here if the phone remains stable without cellular. But all of the research I have done on the issue has pointed to cellular access. I am on wifi and all the apps and functions are working without issues so far. I am starting a dialog with HTC to see if there is a hardware problem.
The reboots also caused heat in the general area of the SD card...don't know what else is there but I do know the cellular antennas are on that side of the phone. Leaving the battery out all night, after an off state recharge would help stabilize the phone for a while, including cache wipes and factory resets.
But once the phone had been on for a while, or Friday morning would come, the reboots would continue.
I have been a computer nut for 30+years and I solve issues for a living. I strongly suspect the radio hardware or firmware as the culprit in this reboot issue. Every other account of this has had similar connections to the radio use.

Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.

dirkyd3rk said:
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
Click to expand...
Click to collapse
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.

misterzeno said:
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
Click to expand...
Click to collapse
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....

dirkyd3rk said:
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
Click to expand...
Click to collapse
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.

misterzeno said:
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
Click to expand...
Click to collapse
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though

dirkyd3rk said:
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
Click to expand...
Click to collapse
You win, you obviously have the bigger nerd e peen. I should go back to a flip phone. *Bowing to phone gawd*
You wouldn't be as much as an ass if you happen to suggest ONE resolution to the rebooting.

Wonk Fix Donations

I thought I would post a thread listing the Paypal address for those who would like to donate to the developer who helped bring about a fix for the dreaded wonk.
I think this guy deserves a couple bucks thrown his way by most of us who use and enjoy ASOP based firmwares.
The last couple of cyanogenmod nightlies have had ZERO wonk.
Lets keep in mind that this issue was starred with Google a couple of times and we couldnt get Google to even recognize that a problem exists!
The problem was so bad that cyanogen was releasing roms marked as stable that still had the wonk because it was an ASOP bug...
Anyway, send this dude a couple of bucks if you can. All of us running a N1 with ASOP based firmwares are benefiting from the wonk fix.
His paypal address is: [email protected]
Thanks!
-Dweebs

Ok, I just sent the guy $10 USD. Its not much but every little bit helps.

Umm what?
Google acknowledged the issue and even fixed it, which is probably why it is working in CM roms now.

GldRush98 said:
Umm what?
Google acknowledged the issue and even fixed it, which is probably why it is working in CM roms now.
Click to expand...
Click to collapse
Dunno if the email is the right guy, but it was fixed independently of asop.

Two different forms of wonk ..
One is the call delay bug
The other is the black screen bug
I "think" he found the issue for the call delay
Not sure about status of black screen bug
Google said the delay bug was not across all devices and only specific to Nexus so they closed the report. Last time i heard about it
Again i might have my bugs mixed up but ehhh

http://forum.xda-developers.com/showthread.php?t=1080147
This is the thread where you can see the results of the guys work. All I know for sure is that for several iterations of Cyanogenmod there was a "call delay". People would call me and not be able to hear me for several seconds. Very annoying bug. I resorted to using a CM Froyo build for a while and then a rooted OTA build of Gingerbread. It was acknowledged as an ASOP bug but wasnt present in the OTA builds of Gingerbread. This guy took the time and tracked the issue down and repaired it with a simple patch.
@Devastatin: The email is the right developer if you follow the above link you can see the name of the guy who I contacted via PM.
@GldRush98: You may have never seen this bug because I remember you commenting in a thread where you stated you only used OTA builds and not "janky custom builds like Cyanogenmod" which I am sure ruffled a few feathers.
But regardless it was a very real problem and there were a couple of threads in which people were asked to "star the issue" on Google forums. The first starred thread was closed, Google said it was hardware specific on the N1 and didnt address it. I dont know what happened with the second thread.
If you guys dont want to donate to the guy, nobody is forcing you. I just felt like the guy deserved some props for fixing an issue that noone else was addressing.
-D

I'm not actively soliciting donations, but if anyone wants to donate to me, I appreciate it. I just thought I'd post here to confirm my identity.
My changes to cyanogenmod are listed here:
http://review.cyanogenmod.com/#dashboard,1030
The a1026 suspend commit deals with the wonk, the call delay commit is obvious. If you click any of the commits, you'll see my email address there, as well.

jyxent said:
I'm not actively soliciting donations, but if anyone wants to donate to me, I appreciate it. I just thought I'd post here to confirm my identity.
My changes to cyanogenmod are listed here:
http://review.cyanogenmod.com/#dashboard,1030
The a1026 suspend commit deals with the wonk, the call delay commit is obvious. If you click any of the commits, you'll see my email address there, as well.
Click to expand...
Click to collapse
The other fixes were for a CM related issue due to merging of 2.3.3 with 2.3.4 which broke receiving MMS from certain other phones. All bugs were a major source of complaints on both the xda nightly thread (along with Fitsnugly's Gigglebread build) and the CM nightly thread with who knows how many countless other threads in both forums.
And AFAIK, google has not fixed the call-delay bug (the wonk didn't exist on the stock ROM) from everything I have read. It still existed on various 2.3.4 builds that I tested.
jyxent fixed some of the major bugs that were plauging N1 users (and who knows how much sleep cyanogen lost due to the wonk). If I can come up with some money on this next paycheck, he will be getting some... Until then, I will just sing his praises

Gonna give this thread a final bump in the hope that the N1 users out there will show this guy some love.
I realize fixing broken code and releasing it to the community is in the spirit of open source software but every once in a while I like to give credit where credit is due. My N1 is perfect (again)!!

I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?

Estimated Prophet Hawk said:
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
Click to expand...
Click to collapse
It's for real, and also seems to have side effect of greatly increasing battery life as well. Bit the fix is only in the nightlies which is why you don't have it.

You could apply the fix to the stable firmware. The dewonkificator was just a band-aid as this actually corrects the bug.
And the guys not trying to make any money off the code, it's freely available. I just think he deserves a few bucks for fixing a huge problem with our phones.
Sent from my Nexus One using XDA App

I believe that this was truly fixed for most devices and the developer who solved it deserves the credit for it, but I'm sorry to say that I'm also still experiencing that call delay occasionally on my N1 running CM 7.0.3...
Edit: just after posting I saw the comment that this is only available on the nightly builds... thought this was already included in 7.0.3. Anyone has a clue on when it will be included on the stable versions ?

I would think it would be included in 7.1 (or the next stable release (candidate) but I'm most likely wrong.
Oh, and the call delay exists in stock OTA builds. My husband has an N1 that is completely stock and not rooted, He has the call delay bug.
I didn't write that. Prove it!!!

this patch can be applied to another ROM like stock GB 2.3.4?

I'll wait for the next stable CM
If the next stable CM has fixed the call delay, wonk, and has better battery life you can be sure I'll be sending out some donations! I flamed on the google thread about this issue; it was clearly an AOSP bug because I experienced it on CM *and* vanilla AOSP. I'm looking forward to the upgrade back to gingerbread but until CM drops another stable I'll be rocking Froyo

This problem is completely fixed in the latest nightly builds. You can apply the fix to the 7.03 build by pushing over the fixed libaudio.so file. Step by step directions are available here if you are uncomfortable using adb, search the forum. I attached the corrected file to this post. The fix was made by jyxent and he deserves the credit for fixing this problem.

Just so everyone is clear...the call delay bug is not just AOSP. I had it right from the get go in OTA 2.3.3 and it continued to 2.3.4. I am now using an AOSP build and don't have it . I may have the MMS bug though as I can't receive certain MMS pics from certain phones/carriers. Have not narrowed down the exact issue yet.

Estimated Prophet Hawk said:
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
Click to expand...
Click to collapse
CM7.0.3 is ancient compare to the latest nightly.

plz vote ( are u with LPY ICS or going back to GB)

THERE IS ANOTHER POST AND POLL THIS IS REDUNDANT
~~~THREAD CLOSED~~~
plz vote ( are u with ICS or going back to GB)

There is already a post with this exact same question and a poll to answer.
Pointless waste of a thread.
On topic: LPY ICS !

Using stock ics latest update and ....hell no! No never gb for me. This rom is f!cking great. All i need now is a custom kernel(thats made with original sourses). No home made brick kernels with no wifi, black camera screen, buggy speaker.

updated to LPY two days ago... loving it so far...
wifi is good, battery life is good, no overheating problems...
The only 'complaint' i have is that it seems to be a bit of a memory hog... but i can wait for a strimmed down custom Rom based on this one to take care of that issue...
overall, pretty damn happy with it
M

Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now

just i want to know the no of bricked phones compared to all

ratcom said:
Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now
Click to expand...
Click to collapse
Considering what we've seen CM9, repacked i9220 kernel, or home made kernel has been the common denominator in every brick

Totally using official ics and loving it. ;-)
Sent from my GT-N7000 using XDA Premium HD app

Note_E said:
Considering what we've seen CM9 has been the common denominator in every brick
Click to expand...
Click to collapse
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?

If it ain' broken, DON'T FIX IT!!!
Zapped through server hops to XDA forums

sehooo said:
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?
Click to expand...
Click to collapse
Are you rooted with CWM?

Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?

Ueihtam said:
Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?
Click to expand...
Click to collapse
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to believe that source considering the amount of donations. I look at what's happening and the results of the numerous upgrades being flashed over the past few days to use that as an indicator. Until LPY kernel source is released and the experts can comb through it, there is no real answer. I don't use CM, it's just not my flavor...but I really mean no disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.

Note_E said:
Are you rooted with CWM?
Click to expand...
Click to collapse
just flashed LPY and not rooted till now

sehooo said:
just flashed LPY and not rooted till now
Click to expand...
Click to collapse
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged, but his home grown kernel is not, but all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering it's a source of donations.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
just i want to know no of bricked phones as there are alot of rumors and i read alot and didn't find the solution to get back to gb OR stay on LPY and go for root

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering the amount of donations. I don't use CM, it's just not my flavor...but I really mean not disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!

Note_E said:
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).
Click to expand...
Click to collapse
i got force close with some applications like youtube and applications which need root which i setuped before on rooted GB before upgrading

vetchems said:
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!
Click to expand...
Click to collapse
Correction: before "official" CM9 there was imilkas...which bricked many others. then there was xplod's donated device during kernel development which you can take that as you will.
My argument is valid...I'm using common denominators. But if you read my whole post, I said there is no real answer...so I'm not trying to be "right"...it's my opinion/observation

I moved back my sister phone to GB because of the brick issues in LPY ICS and high battery usage !
Sent from my GT-I9100 using Tapatalk

Did anyone with multitouch download a new ROM?

Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference

fedreta said:
Did you find it cleared multi-touch issues or improved it at all? Some people say Cyanogenmod fixed things, but I'd just like more confirmation that it'd make a difference
Click to expand...
Click to collapse
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.

**Menos** said:
I also have this problem. Tomorrow planning to flash on ParanoidAndroid or Cyanogenmod. Tomorrow otpishus the results.
Click to expand...
Click to collapse
I've never tried flashing a ROM before, my device is already unlocked/rooted. What do you do exactly to flash Cyanogenmod?

Just installed Cyanogenmod and saw that the problem is not solved. I fear starting to appear that the problem is hardware. Now have to wait for an update from Google.

IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.

Tony_YYZ said:
IIRC, the screen issue is due to a firmware config that cannot be addressed by flashing a new ROM. An updated firmware package will have to be pushed via Google.
Click to expand...
Click to collapse
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide

fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update. All the nexus devices start their lives like this, one of the few annoying things about being a nexus fanboy, you get to enjoy the bugs before anyone else gets to.
http://www.engadget.com/2013/08/13/2013-nexus-7-multitouch-bug/

fedreta said:
Did Google confirm this was the problem? I just need to make sure it is their problem before I go and swap it out since I have 1 more week to decide
Click to expand...
Click to collapse
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.

Tony_YYZ said:
I'm trying to remember the source of my information. But it was stated a few times that the second OTA is what causes the screen issues after powering your device up for the first time.
Click to expand...
Click to collapse
Yeah I remember this too, something about the kernel supplying not enough voltage to the touchscreen in an attempt to improve battery life. This has to be a kernel bug.

Try flashing a different kernel as that is what bridges hardware and software.

Aren't all kernels based on stock?
Sent from my Nexus 7 using xda premium

uprightbass360 said:
From what I have seen, google is aware of all the big bugs and is working on a big update. Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.

sfhub said:
I would love to see that happen, but where do you see Google acknowledged and commited to fix all those problems?
If it is just speculation, that doesn't help folks who are within their return period and can get out instead of playing guinea pig.
Click to expand...
Click to collapse
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation. I think that judging by past examples anyone who has bought a nexus device at launch has either knowingly or unknowingly already agreed to be a guinea pig. In the end I am one of the last people to say that someone shouldn't return a defective piece of hardware, but it seems a lot of the issues people are having are being misdiagnosed as hardware issues when in fact they can (and most likely will) be fixed by an OTA.

I can dare to say that the issue is present in Android 4.3 affecting any device running it even Custom Roms I'm on CyanogenMod 10.2 on my d2spr (S3 Sprint) and the issue is present there too. Also that causes reboots too. I could be wrong too.
Sent from my SPH-L710 using Tapatalk 4
Team SXTP

Also the jss build is giving problems in the nexus 4 thread
Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...

uprightbass360 said:
Looks like screen flicker, multitouch, overheating, corrupted images on startup, gps, wifi performance etc are going to be fixed in a bugfix update.
Click to expand...
Click to collapse
uprightbass360 said:
According to the minions on their google+ "they are working on these issues". I by no means know that google is in fact going to be able to fix all of these issues, nor am I able to guarantee what they do, but I don't see that by repeating what their reps are saying is pure speculation.
Click to expand...
Click to collapse
No problem with repeating what they are saying, but you seem to have commited them to more than they are saying in their personal comments, not those as official reps.
IMO everyone should get accurate information so they can evaluate for themselves whether it is worth the risk to keep it or just to return the unit.
Personally I think the random reboots and GPS can be addressed in software and the multi-touch is probably 50/50 something that can be worked around in software, but everyone has their own tolerance levels for these kind of issues and "are looking into it or are working on it" and "going to be fixed" are quite different levels of commitment.

I'm sorry but what issues are you having because I exchanged my first n7 because I was having multitouch stuttering and issues with unresponsiveness which made the device unusable. The new device is okay.

Screen gets black sometimes

Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip

If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee

dbal said:
If it gives us both any relief, I can confirm the issue - it's like the blink of an eye, so fast, quite rare and absolutely random. A quick Google search only hinted towards the Moto display function which might be the issue but I didn't disable it because it's one of the phone's killer features
So, I 've decided to wait for an app update or the Nougat update that's on the way (?) and see if it gets fixed - otherwise I will pay a visit to the local Moto service center in terms of guarantee
Click to expand...
Click to collapse
Thanks for your answer. Basically, the problem as I see might be related to GBoard or Moto Display, as you say.
Also, I don't know if you've checked the logs I uploaded, but there are a lot of OMX decoding errors, I'm almost sure that there's no hardware failure there.
I'm now going to unlock Bl and see what's up with a custom ROM.
Sent from my Moto G Play (4th gen.) using Tapatalk
------
EDIT: Before proceeding, disabled Moto Display. Will give more feedback later.
Anyways, flashing again got the issue completely gone. Maybe your theory is the most appropriate.

Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well

dbal said:
Well, I wouldn't suspect Gboard because I 've noticed the thing days before I got it installed
I also don't vote towards hardware issue that's why I am not extremely eager to visit the service plus the fact that the issue happens 1-2 times a week and I almost forget it in the meantime
If you go for a custom ROM, this might shed some light whether it's firmware or app related and what we have to expect as a solution - don't forget to post some feedback after a few days testing
Let's see btw if anyone else posts here for having the issue as well
Click to expand...
Click to collapse
BTW, I've already disabled Moto Display. I haven't fell asleep yet and it's 7 am here. Tomorrow I'll keep testing and hope it doesn't fail anymore. If not, I'll go for Bl unlocking and get rid of this Motorola's buggy attempt of softly modded AOSP.
Sent from my Moto G Play (4th gen.) using Tapatalk

Here I've uploaded a screencast of what appears to be related to the bug and shows clearly it's a software bug related to the video render in Marshmallow.
https://youtu.be/qhmUN43y0Pk
Sent from my Moto G Play (4th gen.) using Tapatalk

facuarmo said:
and shows clearly it's a software bug related to the video render in Marshmallow.
Click to expand...
Click to collapse
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?

dbal said:
That's great news to know :victory: (since it's not hardware related and could be fixed in an updated firmware) but can you please elaborate a bit, how you prove this claim and this short video shows it?
Click to expand...
Click to collapse
Sometimes, life's about taking the risk.
I've unlocked BL, flashed recovery and installed AOKP.
Now, no flickers found.
Prove:
https://youtu.be/T3e8-6dnyl0
Hope you like guys, and you take the risk too. Flashing a ROM solved everything.

Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat

dbal said:
Getting back to the thread after 2 weeks just to confirm your long testing now...is the bug still away or has reappeared somehow?
I am asking before I make the switch to LineageOS which seems a pretty good implementation of nougat
Click to expand...
Click to collapse
I've compiled a kernel based on Squid2's sources with the fixed SELinux setup, then you should see no flickers so far in any ROMs.
Mine's working without any flicker, but I've only tested in Custom ROMs. Maybe you can try on stock?
https://forum.xda-developers.com/g4-play/development/kernel-somefeak-moto-g4-play-t3544556
Good luck and sweet flashes! :fingers-crossed: