Related
Hello, I set my phone up using CyanMod4.2.6 + Recovery 1.4 I came across a problem this morning where my phones screen was very glitchy. As in seeing multiple lines of things as I scrolled up or down. I've tried wiping and resetting.. converting back to stock.. new recovery image. All the same results. The kicker is... When the screen is open (I can see the keyboard) its perfectly fine.. No glitches or anything. Help if you can, please. Hope this is the right place to put it. Not sure if I need to send it back or get a new one. Thanks/Sorry in advanced!
can you enlighten us a little more, perhaps with some screenshots?
Since youve already wiped and reflashed I thinks its just dying on you man. Best way to check that i can think of is flash another rom and see if you still have the problem. If its still glitchy then i guess its call tmobile time. I hope u still have warranty bro. Dont forget to revert back to stock before you send it in.
Yup
Thanks guys, it got worse so just reverted back to stock and have my replacement coming by the end of this week. The software changes didn't do this right? They called it layering. Most def modding the phone again just wasn't sure if there was another cause then this other than crap happens..
I have a stock N1, updated to Froyo. So every now and then, ever since I got the phone, the screen just stops responding when waking it up. Sometimes, the screen doesn't turn on at all, but the soft buttons light up. And the only way I've found to fix the problem is to either restart the phone, or connect it to my USB.
Was wondering if it's a hardware or software issue?
same thing happening to me aswell...seems to be only since Froyo flash. Really crappy when you are trying to show off the phone and you have to reboot first. Im gonna mess around a bit tonight and see if I figure anything out...Im also not getting any trackball notifications... I think its software related, for now.
I can say it's not Froyo since I've had this problem before the update, unfortunately.
mailliw320 said:
I can say it's not Froyo since I've had this problem before the update, unfortunately.
Click to expand...
Click to collapse
Ok some weird stuff going on for sure..
With CM 5.0.6 every couple days I would the keyboard would "uncalibrate", but the screen would never freeze up.
Since installing Froyo I am getting the freezing and unresponsive screen at least once a day.
Lets hope my it is not my screen getting worse. Ill have to flash back to CM 5.0.6 and see if I still get freezing.
Bye bye Froyo, see you in a couple days!!
So...anyone else with this issue pre-Froyo?
ive never had my nexus freeze, then i flashed froyo and that day it froze for about a minute, now it has done the hard sleep thing and it does it more times per day each subsequent day.
I know that we have an early "test" version of froyo so this stuff isnt grave, but since there seem to be groups of people experiencing different issues, i also wonder if its possible that specific apps can cause problems unrelated to the app since they arent really ready for froyo...is that possible and does anyone know of apps to beware of? not so much apps that dont work but apps that cause other problems?
Edit: my phone is stock by the way
i used to have a lot of problems when i switched from landscape to portrait mode with the calibrations but since ive put on 2.2 that problem is long gone and i have no other issues...
I had shocking touchscreen issues on 5.0.6, to the point where the phone was unusable and I had to reboot or pull the battery. Turning the screen off and on using power button would work occasionally but not always. Unfortunately I am still having the occasional problem on froyo. I had some mates trying to troubleshoot for me and took a few logs, the recurring error was (CM 5.0.6):
I/InputDevice( 117): Dropping bad point #1: newY=176 closestDy=3401 maxDy=2779
I haven't taken a log while on froyo
Thanks for the input, fellas. Sounds like it's a more apparent issue in this test release of Froyo. I've had the issue since before flashing the update, with stock 2.1, but it's sounding like it's software related and nothing actually wrong with my phone. Guess I won't bother contacting HTC haha
I tried to search but alas Tapatalk isn't very good at that.
I bought a Captivate via eBay. Before I press to return it, is there a fix or ROM that fixes the dreaded random shutoffs? I tried resets and the GB Serenity ROM but alas I'm still encountering it...rather frequently. Every hour or less it'll shut off. So, other than the battery draining Captivate Keep Alive app...is there a real solution?
barring anything physical with your phone .. I have not had any sleep deaths or random reboots since switching to Fusion-CM-ICS-beta. It used to be a chronic issue with my phone.
Thanks for the fast reply Garyth. I'll give it a go.
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
So far, so good. Data is consistently faster as well. Thanks again!
Hmm. Still getting random yet pervasive shut downs.
I believe this was a known hardware issue as well. There is a thread around somewhere will effected build numbers.
I saw that thread and don't believe mine is in the range. I'll be calling the seller tomorrow anyway.
Not sure if you are in the same boat as me, since the IMEI of my phone does fall into that catergory of the "recalled" phones, but since it was out of warranty by the time I saw that post, they wouldn't exchange it at the store.
At any rate, here's what I've gone thru:
Back in the Froyo times, I "think" CM7 fixed the issue, but I was too fidgety at the time so I was always trying new roms so I don't remember 100% if that was true or not.
I read somewhere that this could be caused by the battery shifting around due to temp changes as it charge/discharges, and that you should put some electrical tape or whatever to make sure your batt. made good contact. Didn't work for me at all.
So finally what fixed the problem was Captivate Keep Alive app, it's in the market.
First I tried it with two ICS roms: ICSSGS and Fusion, with Platypus and IcyGlitch kernels. The app work fine with a setting of 85%, but I was getting "charge death" as well, which I've never had before.
So now I've rolled back to KK4 (Serenity ROM) with the latest Corn kernel, and for some reason I have to set the app to 80% charge but works.
There'll be definitely an increase in battery drain, but for me it hasn't been that bad.
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
mrhaley30705 said:
I've heard the aosp roms seem to help the problem (this includes the ICS roms). They use different drivers than Samsung roms.
Click to expand...
Click to collapse
Can anyone confirm this?
crt60 said:
I used to have that problem when I first got my cappy, had froyo KB1 on it, and it would randomly shut down. Eventually when I got into hacking the android, when I finally updated to newer bootloaders, the problem went away. Though I can't recommend flashing bootloaders, since you can hard brick your phone if unsuccessful. Just saying that's what seemed to solve the problem for me.
Click to expand...
Click to collapse
But what bootloader fix that to you?
Mine only rebooted randomly once when on eclair. Haven't had a problem in gb or ics.
Posted from my ICS'd Captivate
That would help if eclair wasn't completely useless.
Sent from my Samsung Captivate running Team ICSSGS 4.0.3
I tried Captivate Keep Alive. Even it didn't work. A replacement phone is on its way. The IMEI was actually affected, but I didn't realize at first because I only looked at the last digits. Apparently was a really early build. The seller photographed the new IMEI before shipping it out so I could verify.
I have Dark Knight's 4.0.4 ROM since 2 weeks ago.
At the moment, and I hope it remains 0 reboots.
Just wanna share with you, is up to you to try it....
http://forum.xda-developers.com/showthread.php?t=1501615
By the way, with this ROM also I got the best Quandrant Benchamark score (2400) without overcloking...
I'll keep that in mind but I got a replacement that works really well. I ended up getting it from another seller though.
Hi
I am new to Android world. So please handle with care
I used to use an iPhone. Recently (bout 3 weeks ago) I bought a galaxy note and am loving it.
I was going through a lot about Android system and found out 'rooting a phone'.
so I rooted the note and installed Rocket rom v22, GoLauncher Ex and few apps like Setcpu, Adfree, Bank, Xchange etc. I don't have games or many apps on my phone.
My phone turns itself off randomly every now and then. during phone conversation it rebooted itself once so far. and when my phone is stand-by, I found my phone is turned off.
I am not sure why it's happening. Is there any settings i shouldn't set?? or ???
Could anyone please tell me how to fix this issue?
If the phone is faulty, I need to make my phone as the same as when I first got which I am not sure how to :-( yet
The first thing to do is go completely stock. Flash the lastest stock rom and see if that fixes the problem.
When using ICS ROMs there's a known bug called Sleep of Death (SOD) that is similar to what you're experiencing. The phone simply won't turn on the screen and you have to press the power button for several seconds to turn it on again.
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Hi
Thanks for the reply.
Before the rom v22, I had v19. my phone still did turn itself off several times. after flash the room v22, it didn't happen as many as v19 so I am not sure that the ICS causes the issue.
anyway, I will try the one you suggested and see how I go.
Thank you
kelvin fong said:
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Click to expand...
Click to collapse
I am more worried about the alarm. if the phone turns itself off while i am in sleep, i won't be able to hear the alarm going off.
well if that happens again, i might have to get a alarm clock.
i was thinking of setcpu app might cause the issue... not sure though.
Thanks for your help
I experience the same issue when i was running stock. I've tried several stock versions but the problem still exists.
Sent from my GT-N7000 using XDA App
I have definitely never ever experience SOD when the phone is stock and lock.
The only time i did experience SOD is when i change to modded kernel.
I'm running stock with cf root and have never ever experienced this, so not all notes are affected. That would really suck!
Sent from my superior GT-N7000 using Tapatalk
Never had Sleep of Death on stock rom.
I am on stock ICS Rom n it has happenedwith me twice.
My GNote goes dead randomly and only starts up after pulling out battery.
Weird!
Install an ICS from Clean
Start from a Stock ICS rom using PC Odin, then follow my Post as follow :
http://forum.xda-developers.com/showpost.php?p=26772618&postcount=12
Try another rom other than that you had, or a higher versionof it.
The MIDTEAM v1.4.2 is Good and Stable.
Good Luck
I had this problem most of ICS ROMs on my Galaxy Note. SO I guess it's an ICS related bug and it is very uncomfortable to have to reset it to unlock it .
I too have tried several Stock ROMs but it still gets into the Sleep of Death at least once a day.
I guess that it should help to have a Kernel that changes the Deep Sleep settings...
Of my 2 GNotes, one of them had this problem. Happens when you put the note on the table with small drop or whatsoever.
The problem disappeared when inserted 3-fold 80g paper between battery and the edge of battery compartment. The battery tolerance is not so tight so when small drop (like putting on the windowsill) happens, the phone shut down.
The problem completely disappeared after inserting paper.
Of course, more professional would be go to Samsung repairs and show it and ask for replacement - either battery or phone internal casing. You can reproduce the problem by turning the screen on and dropping phone 10cm into hard surface.
But I did not bother.
I won't say that yours has exactly the same problem. But check the tolerances of battery 1st. Sometimes solutions are too obvious to see 'em.
I upgraded from stock to CM9 3 days ago and my Note has turned off several times a day since then. Never before upgrade, so I don't think it has to do with battery being loose in its compartment - not in my case.
I am loving ICS, but I will have to downgrade to gingerbread to get rid of this irritating bug.
this is happening to my galaxy nexus!!! yeah it turns off at random like sleep of death and small drops can trigger it. if i knew this could happen i would have never rooted
lol root itself has nothing to do with it.
if small drops cause it, and paper adding in compartment fixes it. its the gap between battery and whatever should fixate it.
if it occurs during deep sleep, dig into logs what you can find there. Also check roms/kernels feedback if others have it with that version. Many ways to illiminate possibilities.
I miss some good analyzes in this is issue from those experiencing stuff. Android I guess is not user friendly that way.
Sent from my GT-N7000 using Tapatalk 2
Galaxy Note Sleep of Death on 4.1.2 JB
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
rasielbz said:
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
Click to expand...
Click to collapse
What is the status of your phone now :
Working or not?
It works then it turns off by itself
Bootloop
Stuck on the white Samsung logo
Completely Off?
It does work but it turns itself of, the longest its gone without restarting is 44 hrs. I contacted Amazon where I bought and they are offering s full refund, so I , might send it back but I love it and had wanted tho keep it if the problem is fixed.
Sent from my GT-N7000 using xda app-developers app
Turning off problem too
I don't know if it is exactly the same problem, but my GNote keeps turning off every time, but not seem to be randomly. Looks like ti shut down every time a high performance is required. I tested several roms, ICS and JB, custom and stock, but the problem still goes on.
Please, any ideas?
I just updated from roger's v20c to at&t v20p which really isn't all that different, but I wanted my phone to say p925 instead of p925g. Everything is working great, I don't use my phone for calls much so I don't notice ghost calls. What I do notice is that my phone doesn't seem to keep the right time. It slows down little by little even though I have use network-provided values. Yesterday I was 30 mins slow when I noticed, today it was about 10. When I reset the phone, the goes back to the right time but eventually it just loses sync. Has anybody experience this on their thrill updated to v20p or even heard to something similar to this cause I would like to keep this rom but if I can't figure it out, I'm gonna have to flash back to v20c.
I just noticed this tonight after flashing v20p as well. I know that you can set the time yourself which would fix things. I also read something a while back about others having this issue with gb rom on this phone. I can't remember if it was in the thrill or o3d section though. Ill have to look and see if there is another way around it and ill check back.
Mine does this too...I was almost late for work because of it. I did a factory reset and it seems to have fixed it so far. We will see.
Sent from my LG-P925 using XDA
Has there been a fix to this? I've noticed this at random times. The phone will lose up to two hours. Will taking it off from Automatic network values fix this or prevent it from losing time?