I don't know how to put this but not so recently I found out that my galaxy nexus' screen behave strangely after reboot. It's like a distortion for about 1ms (I guess). It's just a glimpse of distortion. Happen after bootanimation (right/exactly when home screen comes up) or just before bootanimation ends. It happens too when the battery is about to die (3 or 4% left, the warning pops up and the background is distorted but the pop up message not).
anyone has any experience as such above?
is this software related issue or hardware related issue?
any suggestion, explanation, help, or anything else would be highly appreciated.
thank you.
ps: bought my galaxy nexus 3 months ago, had zero experience prior buying my galaxy nexus, had experience of wiping system but could not able to flash stock rom via cwm (at that moment not knowing that cwm can only flash flashable zip not tgz or tar), right now running custom rom xylon 011 JB 4.2.1.
It used to happen to me when I was running cyanogen mod 10 the same way you described. Went back to stock and haven't seen that again.
Wow, thank you very much for confirming this. I forgot to put additional info that I had run CM10 too and had same kind of behavior.
So I guess that is software issue rather than hardware, rite?
Anyone else having this issue?
Related
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
I don't know but think people either don't know the meaning of stock or I have to learn the meaning
What you described is not stock Rom.and to your answer no I don't get sod.
True. I'm not on stock, I guess I meant to say that my ROM was created from stock. Good to know that someone else is not experiencing this though. Thanks.
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
Click to expand...
Click to collapse
+1
I was having screen freeze while using the google reader app. Had to pull battery.
Am running the same ROM, with battery percentage mod as well. Stock kernel. Not sure why.
possible sleep of death fix?
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB?.
Click to expand...
Click to collapse
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
chorner said:
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
Click to expand...
Click to collapse
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
063_XOBX said:
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
Click to expand...
Click to collapse
good point. i also was wrong about the sd card anyways. i flashed cm9 back on it. turned auto brightness off. it had the issue. rebooted. turned it back on. re-enabled autobrightness. no issue.
thanks for the compliment.
I'm on 4.2 and have the issue. A few times a day, I'll pull it out of my pocket and I see the "backlight" turn on but screen is on. (I'm not sure how there is a backlight if is amoled but i do see some kind of something very very faint )
In Developer Options put all animation scales to .5x.
el_charlie said:
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
Click to expand...
Click to collapse
I experienced a similar issue on 4.1, but it would happen almost once day (very annoying). I'm now on a 4.2 rom and I haven't seen the issue in weeks. :laugh:
Issue reported here, please star if your device is similarly afflicted.
I dont know if things have just gotten out of hand (excessive modding) or if it is a hardware problem, but my gnex reboots and boot loops with my MHL adapter plugged.
I have gotten my kernel messages from before the reboot.
It seems that according the TI technical reference manual for the OMAP 4460 that my phone rebooted due to mpu watchdog timer event and it was a warm reset. (PRM_RSTST=0x10)
The mpu watchdog timer indicates that the system considered itself stuck and so made a hasty and determined decision to start all over again.
The warm reset flags reveals that software initiated the reset.
This is the way I take it: so either my Processor has seen better days and has grown to old and decrepit to do what it once did, MHL, or the way the new jellybean stock kernel in dealing with MHL is taking entirely too long. Seeing as how this isn't a widespread issue, though, I have seen others with this problem, I don't think the kernel is the cause really. But, I hope it is software related.
Will someone please help me here?
Is there a better place to ask this question?
I would appreciate someone with a working phone on jb 4.1.1 plugging in their MHL, rebooting their phone and then posting their /proc/last_kmsg file (requires root). So, I can see what should be happening and determine any differences.
I changed from stock jb 4.1.1 to bigxies deodexed and my mhl now works, if that helps anyone.
Any luck figuring out why bigxies deodexed rom works and stock doesn't?
It has had me stumped for weeks.
Not really,
I looked at the kernel logs between stock and bigxie and there was no real difference. Stock just rebooted, where bigxie kept going. The stock set some flags that indicated a software reboot due to a hang (watchdog timer).
I guess that maybe some apk or odex in the stock isn't aligned right, or compression is corrupt or something and when bigxie de-odexed he was able to fix it.
Plus the bigxie update is the OTA, not the factory image, so maybe there is some difference, though technically there shouldn't be.
There is definitely a difference in size and CRC between the two, see here.
Same problem here, reported.
I just want to say that using paranoid android fixes this issue at least on the current version 2.17 as well. I don't know why it fixed it. But i know of no other cyanogen mod based rom that works for affected phones.
So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?
Bump. Any help? Still happening, though not as common, when I flashed stock
Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?
Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium
Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium
I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.
Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..
@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.
+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2
I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag
Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?
Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app
SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.
solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you
Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be
anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.
Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!
I wanted to ask someone with expertise regarding my d2tmo.. I am experienced with flashing roms and anything with rooting and trying roms. I wanted to ask you about a camera issue I am having. The problem is when my camera is using flash to snap pics and also sometimes when making videos without flash my system crashes and forces reboot. Before seemed like was only in aosp roms and i was thinking it could be just that cm10 bug with the cameras, but then I noticed it was happening in Tw roms and so i odin flashed stock firmware and the problem still persists. I asked someone before and they told me it for sure was a software issue and not hardware, but since I was on stock seems like could be hardware. Have you heard if this happening before? could you offer me some kind of insight for this? I am sending the phone back to tmo and getting a warranty replacement for another issue ( and yeah i triangle awayed lol) , but i was wondering if this would happen still with the new phone if i decided to flash some custom roms.. Is there a chance that samsung could of improved components or did anything different since I bought my s3 last october? I am sorry for the long story, but I really can't find help anywhere else and I really use my camera alot for work.
thanks in advance.
- J.RAD
Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!
sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?
I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).
I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.