Team, I think I have found the coralation between the banding issue experianced by some users post ICS update... unfortunatley I do not see a solution until we have root and Kernal access avalible. My observations as follows:
1. Post update restart banding issue begins in an itermitent fashion, seemingly random.
2. Confirmed fact that overclock has been applied to update raising processor frequency to 1.6GHz
3. On initial cold boot after charging issue seems to to have subsided, only to return after aprox 15 min of constant device use.
So, my theory as follows:
After many years of overclocking my PC's there seems to be a corallation between this and what i seem to be experiancing on my prime. So OC'd processor starts from cold... and the system runs fine, until it starts heating up.... at this point the artifacts start coming onto the screen, with increasing frequency the "warmer" the device becomes. Seems a very plausible reasoning to our problem and exactly what is typically experianced when OC'ing a computer. It also explains why when left over night, either idle or off and charging, I had no problems from startup as the system was cold. So I guess at this point it would be good to open up the thread and discuss this, though I am not sure to what avail.... it seems there could really be no fix until we can turn the clock speed down to see if this effects the Prime.
Also this thread is meant to be a positive exchange of information, please do not come on here to flame or use this as a catalyst for screaming why the Prime sucks, or glad you did not buy it. I have no time to deal with trolls, and know you are not welcome here
i had a similar notion, however:
-i think we have confirmed 1.5 and 1.6 ghz are locked out
-if it was a gpu/cpu heat issue, this would appear immediately when gaming/benchmarking starts.
My initial thought was GPU artifacting, but this doesn't appear like GPU artifacting i have encountered from overclocking or excessive heat. More like a driver issue.
tdrussell said:
i had a similar notion, however:
-i think we have confirmed 1.5 and 1.6 ghz are locked out
-if it was a gpu/cpu heat issue, this would appear immediately when gaming starts.
Click to expand...
Click to collapse
Well, I do agree with you but I think it also has to do with how fast the unit is able to dissappate heat.. I am on the ferry to work now and had not touched my Prime for at least 45 min... upon picking it up after it had "cooled" down so to speak it was fine... then a few minutes ago began with banding agin, unfortunatly I have no games installed after the update so I can not verify this, but I there may still be an explanation. When overclocking certain chips are sweet while others not so much... I had 2 identical Q6600's in almost identical machines and while one could reach a 4 GHz clock the other only 3.2... so a differance in the manufacture of the chip could explain why some users do not have problems and others do.
Can I take it from your post that you only experiance this issue while in ICS and not in game?
Element_01303 said:
Well, I do agree with you but I think it also has to do with how fast the unit is able to dissappate heat.. I am on the ferry to work now and had not touched my Prime for at least 45 min... upon picking it up after it had "cooled" down so to speak it was fine... then a few minutes ago began with banding agin, unfortunatly I have no games installed after the update so I can not verify this, but I there may still be an explanation. When overclocking certain chips are sweet while others not so much... I had 2 identical Q6600's in almost identical machines and while one could reach a 4 GHz clock the other only 3.2... so a differance in the manufacture of the chip could explain why some users do not have problems and others do.
Can I take it from your post that you only experiance this issue while in ICS and not in game?
Click to expand...
Click to collapse
i definitely know what you mean about binning.
True, i have not seen this occur in a game yet, but i just fired up glowball for a few seconds to confirm it was working.
Did many runs of quadrant after updating last night though.
I'll try some movie clips and more gaming today.
I was having the same problem as well. Not sure if this the fix bit it seemed to go away. Go to settings -- Developers Options, and check off. "Force GPU Rendering". After doing this my screen banding seemed to go away.
Sent from my Transformer Prime TF201 using Tapatalk
tdrussell said:
i definitely know what you mean about binning.
True, i have not seen this occur in a game yet, but i just fired up glowball for a few seconds to confirm it was working.
Did many runs of quadrant after updating last night though.
I'll try some movie clips and more gaming today.
Click to expand...
Click to collapse
Now see this is intresting, I am not familar with Bench software on Android but does Quadrant stress CPU or GPU or both? We can cofirm the additional boost to the CPU as seen in other posts but I take it we do not have method of ascertaining clock frequency on the GPU... do we? I am at work now so I will run some sly tests in the backgrouds on the unit and see if I can get the issue to replicate in a game as soon as its installed and will report back. Thanks for the input, was hoping for more but will take one positive poster over 1000 trolls
mardukeme said:
I was having the same problem as well. Not sure if this the fix bit it seemed to go away. Go to settings -- Developers Options, and check off. "Force GPU Rendering". After doing this my screen banding seemed to go away.
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Intresting... this was already set to off on my install in the developer settings but provides an intresting insight that the GPU may have been OC'd too to accomodate ICS' increased graphical demand (not really much though compared to hard gaming) ...but possibilities arise!
Bump for Dev input... Anyone?
Ok, so even if no more input on the subject... is there a way to downgrade back to .33?
can someone that had this issue post a video or screenshots of this occurring. Several minutes ago, for the first time, I noticed the bottom left hand corner, where the back n home tabs are at, looked like it was glitching or something. just only at the bottom left hand corner in the black area. looked like glitching lines or something. The rest of screen wasn't affected but opening up the notification area seemed like the screen was shaking ever so slightly. this went on for a min. or so. Since it didn't go away on its own, my immediate response was reboot. I rebooted(by the way my start up times are very fast, very impressed with it now..lol) and the issue went away. I hope it never comes back also..lol. I had Prime in balanced mode and just surfing the web posting here in the forums.
This was the first time this ever happened andbit was only very briefly. Rebooting seemed to fix the problem. I just want to see a video or screenshot of this so called screen banding to see if this was what I experienced or something else minor. Prime hasn't shown none of this since the speedy reboot.
thanks
demandarin said:
can someone that had this issue post a video or screenshots of this occurring. Several minutes ago, for the first time, I noticed the bottom left hand corner, where the back n home tabs are at, looked like it was glitching or something.
...
Click to expand...
Click to collapse
Mine looks like the attached...
But my latest theory is graphics activity in the notification area as wifi activity or charging (wifi off) causes the bars to flash on and off. Also doesn't happen if you sit in the gallery app as it hides the notification area...
I'm having the same issue, just sitting on the lock screen.
I agree that it is acting like a bad overclock. The thing is the "fix" will be to slow it back down. Mine is rebooting all the time and yes it happens faster and faster after being powered off. It also lasted longer when plugged in (slightly more voltage from recharging?) However if only some are doing this than we won the "bad bin" lottery.
what I would like to know is, when sent in via RMA to "fix", is ASUS just software limiting the CPU/GPU or changing a part of the hardware?
If they just slow it down in software, then I'm better off returning it and getting a new one... if they are swapping a part then I'm better off RMA'ing.
1) Check CPUSpy or similar for time in each clock state.
2) Check Temperature (maybe battery is all we have, but mine is reading only a couple of degrees above ambient - no problems seen so far)
/sys/devices/platform/tegra_tsensor/tsensor_temperature
Oddly, ever since the first night I haven't had the banding issue, it seems ot have gone away, and yet to come back, which is quite surprising, but good news for me nether-less.
No, the update did not overclock the prime... Already a few threads about this explaining why the prime is still only at 1.4gz max. So it has nothing to do with overclocking because overclocking is not happening.
Regardless of what any app is telling you, the TFP IS NOT overclocked. Find the thread about it and it will explain everything in great detail.
"Mine looks like the attached..." One of the times mine crashed, the screen froze and there were white lines just like the black lines you show. I do feel the "banding" and the "rebooting" are the same issue. And I would bet CPU/GPU clock speed boost if there was one to be the issue. And yes it does seem to be booting much faster, might be ICS but could also be a clock speed boost. What is the best ap to show CPU clock speeds in real time on the tegra3?
demandarin said:
can someone that had this issue post a video or screenshots of this occurring. Several minutes ago, for the first time, I noticed the bottom left hand corner, where the back n home tabs are at, looked like it was glitching or something. just only at the bottom left hand corner in the black area. looked like glitching lines or something. The rest of screen wasn't affected but opening up the notification area seemed like the screen was shaking ever so slightly. this went on for a min. or so. Since it didn't go away on its own, my immediate response was reboot. I rebooted(by the way my start up times are very fast, very impressed with it now..lol) and the issue went away. I hope it never comes back also..lol. I had Prime in balanced mode and just surfing the web posting here in the forums.
This was the first time this ever happened andbit was only very briefly. Rebooting seemed to fix the problem. I just want to see a video or screenshot of this so called screen banding to see if this was what I experienced or something else minor. Prime hasn't shown none of this since the speedy reboot.
thanks
Click to expand...
Click to collapse
I noticed this when trying to use the stock video player, it was all glitchy lined. Apon closing the app it went away. I have notcied that ICS requires a reboot once every other day to stay smooth otherwise it seems to start glitching out when trying to do heavy tasks like play games. But once rebooted all is well again.
Maybe the TFP doesnt have enough ram for ICS. Or maybe its just a bug that needs to be worked out in the next update.
*again the TFP has not been overclocked... demandarin can point you in the right direction of his thread explaining it further.
shawnfr said:
Mine looks like the attached...
But my latest theory is graphics activity in the notification area as wifi activity or charging (wifi off) causes the bars to flash on and off. Also doesn't happen if you sit in the gallery app as it hides the notification area...
Click to expand...
Click to collapse
Oh no..lol sorry..I would've went off if my screen started doing that. I guess I didn't experience what y'all have then. that is really bad n severe. did it go away or is it still happening?
dang, this has to be one of the worst issues I've seen. that is horrible. what I saw was nothing like that. it was very minute and only occurred in bottom left hand corner in the black area over the back n home area. Rebooting my prime fixed it. plusbthst was the only time that ever happened. if what you showed me didn't go away after reboot, I'd exchange that immediately.
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
Yes its true. we are not overclocked. I thought we were at first when ICS first dropped. Although different apps and benchmarks show a higher clocked top speed its not really that high. of you use CPU spy, it will show you that those higher clocks are dormant or deactivated. its there but we can't use it. We had several people look further into the issue and found although its possible by devs, stock ICS has the higher clocks in a suspended state. sorry for the confusion from my thread. I was only half correct. we do have higher clocked speed bit not actually using it. if it makes any sense.
demandarin said:
Oh no..lol sorry..I would've went off if my screen started doing that. I guess I didn't experience what y'all have then. that is really bad n severe. did it go away or is it still happening?
dang, this has to be one of the worst issues I've seen. that is horrible. what I saw was nothing like that. it was very minute and only occurred in bottom left hand corner in the black area over the back n home area. Rebooting my prime fixed it. plusbthst was the only time that ever happened. if what you showed me didn't go away after reboot, I'd exchange that immediately.
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
Yes its true. we are not overclocked. I thought we were at first when ICS first dropped. Although different apps and benchmarks show a higher clocked top speed its not really that high. of you use CPU spy, it will show you that those higher clocks are dormant or deactivated. its there but we can't use it. We had several people look further into the issue and found although its possible by devs, stock ICS has the higher clocks in a suspended state. sorry for the confusion from my thread. I was only half correct. we do have higher clocked speed bit not actually using it. if it makes any sense.
Click to expand...
Click to collapse
i got a bunch of shots of mine doing this today...
Sent from my Transformer Prime TF201 using xda premium
Related
Has there been any resolution to the 1 - 2 second wake up lag yet? I've seen several "fixes" like reducing the resolution of the lock screen wallpaper etc but none of these work for me. I've experienced the lag on KE7 stock ROM, Cognition ROM, Villain ROM and now on Lite'ning ROM.
Not sure if I agree that it's being caused by the CPU clocking down when the phone is asleep either. When I use SetCPU to set the minimum clock speed to 1.2Ghz the wake up lag is still there.
Also the lag does not occur when the phone is plugged in and SetCPU is telling me that the phone still clocks down to 200Mhz when asleep and plugged in.
Someone must have some idea what is causing this #$%$## lag.
I use Softlocker Free for this.. Works perfect for me, a bit reduced battery life but not enough to stop me from using it..
Thanks for the reply. I tried Softlocker a while back and found the battery drain pretty heavy. Might give it another go. I was thinking there must be a permanent fix for this lag problem though. Hopefully it's just a matter of someone finding it.
I also noticed the lag on my old i9000 as soon as I updated to GB so know this is across the different samsung models on GB in addition to SGS2. I really do think its the clock going down despite your setcpu settings. Use cpuspy free from market and you will see what I mean. Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
It will happen on every rom right now since they are all based on the firmware. I really think it saves battery going into that clock mode and if someone comes up with a fix the cpu will have to run at a higher clock rate and battery loss will be significantly higher
Sent from my GT-I9100 using XDA App
Mines instant with No Lock.
Sent from my GT-I9100 using Tapatalk
Tell us what you did to stop the wake lock. Is it plugged in though?
Sent from my GT-I9100 using XDA App
I am using Lite'ning rom 1.4 right now, when I press the home button til the screen on take around 0.5 second, is it normally?
I've tried this app,and it did seem work. I'll try to see how about the drain of power.
I was using No Lock and it didn't make any difference. What is really annoying me about this is that some users are seeing the lag and others apparently aren't. The lag on my phone is probably about 1 second. This isn't a really big deal unless this sort of thing annoys you. My iPhone didn't have the lag, my Desire didn't have the lag and I feel a high end phone like this shouldn't have the lag either.
blue265 said:
Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'll have a play and see.
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
djsaad1 said:
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
Click to expand...
Click to collapse
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
appro77 said:
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Don't want to fork/derail the thread, but are you guys experiencing only the "Wake Up Lag" or also the lag when pressing the Home button while unlocked. I see some lag when using the home button to go back to Homescreen 1 for example. In case you folks are seeing lag in both the cases like me, could it be that both have the same underlying cause.
There is this other theory about the bundled Voice Talk app from Vlingo having the shortcut of Home button double tap, which causes any Home button tap to wait until the double tap window before doing its thing. I don't see that mentioned in this thread, but it kind of makes sense for the Home button lag, but perhaps not so much for the Wake lag (at least I could not think of a reason for that to happen). What do you guys think about both these problems?
appro77 said:
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Well well finally users are reporting this problem, good to see its not only me.
Anyway, I don't think the Phone goes to any underclocked frequency when it goes to sleep. Cause if you can test SetCPU by setting it to 200 MHz then you will notice that in 200 MHz the phone turns itself off, you have to turn it on manually. So the problem is related with firmware definitely. And there are no fortunate users, some users don't take this as a problem, some don't notice it and some notice but doesn't agree, but here or there everyone has the bug. I hope the issue will be fixed in future firmware upgrade.
Regards.
Sent from GT-I9100
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
rdy2go said:
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I've just tested that, it's the same no matter what background I use.
Wow..
Seems like the thread I can finally count on! Lots of behavior that I experience as well. I have the home button lag and the wake up lag and it's bugging me.
One thing to note.. The wake up lag is worse when you have an SD card inserted -> This scenario was the same for the SGS1 too. Anyone can confirm this?
I'm using No Lock as personal preference but the lag is always there. All behavior you guys mention (abt headphones plugged in, charging, within 5-10secs) are all being observed.
Eagerly waiting for a fix!
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
TheBishopOfSoho said:
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
Click to expand...
Click to collapse
I did flash a newer ROM, but didn't do a hard reset.. all my apps were intact. Perhaps I will spend sometime on it this weekend. By the way, which ROM did you flash on your first SGS2 that fixed the problem?
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep. That bring me to say that the delay is not caused by the voice input function, but rather due to the device going into deep sleep (which may be normal). But it's the waking up that's taking long.
Still seeking for more ideas...
MasK said:
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep.
Click to expand...
Click to collapse
Yes, I found that SoftLocker is not really a solution because of the battery drain and some other bugs it introduced.
Anyone who is experiencing this lag should be contacting Samsung. I contacted Samsung Australia and they told me they had not heard of the problem. If everyone who is experiencing the problem reported it to Samsung, I think there may be a far better chance of a fix. Anyone who is annoyed by this bug, please email Samsung via the link on their website. If they are flooded with complaints they "may" act and provide a fix.
Apologies ahead of time for the wall of text...
I got my wife the Prime for Christmas. It took her a couple of days to finally open it, as I gave her the choice of going with it or the iPad2. After a couple of days, she seems to like it and is slowly getting the hang of the OS.
I've played with it some. For the most part, it seems smooth. I've managed to make it glitch (lag) a time or two by going in and out of apps and even had the launcher itself FC on me forcing me to reboot.
That was while checking out Alice in Wonderland in MyBooks, which by the way, is not exactly usable. The page animations worked at first, then stopped, then the pages stopped turning altogether and the app FC'd. Not that I care or am surprised. I'm used to included software being half-baked.
Browser experience has been fine using stock and Opera. Dolphin doesn't seem to work as well on the TF201 as it does on my Atrix. Perfect experience? No. I have a $4,500 i7 2920-XM workstation with an SSD and 16gigs of RAM at work and even with it, the browsing experience (or OS experience in general) can lag/glitch from time to time. Nature of the beast.
I can't really comment on battery life. She took it off the charger Monday night at 100%. It hasn't been used steadily for more than 1-2 hours at a time. It's down to about 15% this morning. I can't really say how many hours of use she's gotten out of it but it doesn't seem to drain much overnight, even with Facebook, email and other notifactions. It felt like it was draining pretty quick when in use but I'll have to pay closer attention.
There's minor light bleed around the edges but I had to turn the lights off during boot up to notice. I haven't attempted to watch an entire movie in the dark with it to tell if it's something that will be bothersome. I'll tell you, I went through THREE Sony XBR2 LCDs a few years ago. They suffered from horrible "clouding" (blotchy white areas all over the panel) and light bleed in the corners. That was noticeable under normal use and since I primarily watched movies in pure darkness, it was bothersome. I don't think it's going to be an issue w/ the TF201 unless I'm being nitpicky.
WiFi seems OK. I have yet to compare it to the laptop, but compared to my Atrix (CM7) it's getting the same signal. It fluctuates some, even staying in the same spot, but it's never caused a problem.
I haven't tested GPS. Something tells me it's not going to operate properly though It's low on my list of concerns and I'll use it as an excuse to return the thing to Gamestop in the next 15 days (for exchange only, which is irksome), but otherwise, I'm not too concerned. If it turns out to be hardware, I imagine an RMA will correct it. It would be cool to use the thing for GPS but I own an actual GPS and rarely use it. I would still prefer the device have its features work, of course.
Aside from the launcher FC and subsequent reboot and the occasional glitchiness/lag using the stock launcher and jumping through apps, the only other issue I've noticed happened this AM. I woke up to the room filled with light. The TF201 was on. I didn't wait long to see if it would go back to sleep so maybe it would have. However, when I got up to see what it was doing, I noticed it had rebooted. Hopefully that doesn't happen often and hopefully not while in use!
I'm confident that a lot of these issues can be fixed with firmware updates and hopefully those are pretty quick to release. Overall, I'm pretty happy with the device. Hopefully ICS will only make the experience better. And hopefully it will come soon so all of the speculation, etc can end! I know my Atrix went from all right to pretty frickin' awesome when I put CM7 on it.
So this time when my TFP shut down I got white lines across the display.
I have a thought, maybe some of you can test.
ICS is supposed to use hardware to do screen draws.
What if what we are seeing is the GPU overheating?
It sure looks like it to me... also if the "update fix" is to slow down the GPU this would suck.
Any way to test this? aka have some external way to cool it and see if it still crashes?
fenturi said:
So this time when my TFP shut down I got white lines across the display.
I have a thought, maybe some of you can test.
ICS is supposed to use hardware to do screen draws.
What if what we are seeing is the GPU overheating?
It sure looks like it to me... also if the "update fix" is to slow down the GPU this would suck.
Any way to test this? aka have some external way to cool it and see if it still crashes?
Click to expand...
Click to collapse
I'm not so sure it's related to the GPU overheating. Sometimes it happens while the tab is booting up, before I've even had a chance to stress the GPU. Also, last night I got in a fairly long game of Shadow Gun, then exited out and was able to use the browser for a while and *then* it locked up.
It's definitely not overheating related mine does it once every 1 to 3 hours no matter what it's doing even idle overnight. The developer that took my log files said it looks like a Linux stability issue.......
jdbaker82 said:
It's definitely not overheating related mine does it once every 1 to 3 hours no matter what it's doing even idle overnight. The developer that took my log files said it looks like a Linux stability issue.......
Click to expand...
Click to collapse
Well software fix would be better than flawed hardware.
Humm..
http://stackoverflow.com/questions/8654424/ics-crashes-when-intent-getextras-is-called
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Galaxy_S_ said:
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Click to expand...
Click to collapse
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Acvice said:
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
I work outside every day and its bout 100 degrees out consistantly now... I'm not running cm9 anymore but I've noticed I still get the occasional overheat while its in my pocket, it most definitely gets annoying sometimes having to pull the battery and let everything cool down but I think the benefits outweigh the annoyance level a million to one. I guess what I'm saying is you're not alone friend, it definitely happens to me as well. I have my CPU set to 1k though and messed around with undervolting as well and feel like I get a little better results this way. Keep playing with your settings until you find the one that works best for you is the advice I can give. Good luck!
Sent from my MoPho running MIUI.us official port!
Party Spock is in the house, everybody have a logical time!
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Acvice said:
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Click to expand...
Click to collapse
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Galaxy_S_ said:
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Click to expand...
Click to collapse
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Acvice said:
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Thank you. I will definitely try that =] Thank you. I really hope it fixes the problem. I can't wait for the stable release. haha
I got my 920 today and I'm quite happy with it. However I'm facing a weird issue. My screen is noticeably flickering. At first I tried to restart the phone a few times, and at last with a soft reset I got rid of it in some areas (eg the unlock screen) but in some others (typing an address in the browser, typing into Bing search) it's still there, even tho it's not very noticeable anymore. However I'm quite picky so it annoys me a bit, also I don't think it's fair that I have to use a phone behaving this way. Anybody else having this? Workarounds of any sort? Otherwise I guess this guy is going back to the store...
Edit: I found out that this issue pretty much comes and goes randomly, I happen to have it for a few hours then it goes away, so on so forth. I really don't know if I'll ever be able to get the phone replaced if the issue is so hard to be reproduced.
Same intermittent problem
vnvman said:
I got my 920 today and I'm quite happy with it. However I'm facing a weird issue. My screen is noticeably flickering. At first I tried to restart the phone a few times, and at last with a soft reset I got rid of it in some areas (eg the unlock screen) but in some others (typing an address in the browser, typing into Bing search) it's still there, even tho it's not very noticeable anymore. However I'm quite picky so it annoys me a bit, also I don't think it's fair that I have to use a phone behaving this way. Anybody else having this? Workarounds of any sort? Otherwise I guess this guy is going back to the store...
Edit: I found out that this issue pretty much comes and goes randomly, I happen to have it for a few hours then it goes away, so on so forth. I really don't know if I'll ever be able to get the phone replaced if the issue is so hard to be reproduced.
Click to expand...
Click to collapse
You're not going crazy as I have the same issue with my 920. It is VERY intermittent and probably happens about once every 3 weeks I guess.
I'll wake the phone to check it and it seems that the display is not working fully and looks interlaced and flickering. No loss of functionality and when I put it to sleep and wake it up a few times it's fine and back to normal. Appears to be an intermittent issue with either the display or drivers but no way to reproduce unless you separately take a video/photo of the screen when it is in this state when you are returning it to the store for an exchange. For me it doesn't happen enough to really worry me although it is slightly annoying...
mad_style said:
You're not going crazy as I have the same issue with my 920. It is VERY intermittent and probably happens about once every 3 weeks I guess.
I'll wake the phone to check it and it seems that the display is not working fully and looks interlaced and flickering. No loss of functionality and when I put it to sleep and wake it up a few times it's fine and back to normal. Appears to be an intermittent issue with either the display or drivers but no way to reproduce unless you separately take a video/photo of the screen when it is in this state when you are returning it to the store for an exchange. For me it doesn't happen enough to really worry me although it is slightly annoying...
Click to expand...
Click to collapse
Man, this is driving me nuts. I noticed it does it every time the phone reaches a somewhat hotter temperature (like body temperature, a couple minutes of usage normally) or when it's plugged. When the battery is 100% loaded it usually stops, but then after a few minutes it comes back, very annoying. Since it does it like 90% of the time I guess the guys at the shop will notice it, when I'm at max brightness it's like a freaking strobe, I can't take this any longer, makes my head ache. One thing I also noticed is the fact that the lowest light setting available is still way brighter than when on auto in a dark room: low looks more like medium, so to speak. Is this ok?
Today I'm bringing it back to the shop anyway, I'll keep you posted.
Update: I got my phone replaced. We had to open 3 boxes before finding a non flickering one, insane. For the last try I decided to open a white one and it was flawless, weird...
Are you guys in cold areas or keep your phones in cold areas? By cold I mean under 65 F. I have noticed in certain types of LCD's that if they are cold they seem to slow in refresh rate. Try warming your phone up and see if it gets better.
R: Screen flickering madness
Solarenemy68 said:
Are you guys in cold areas or keep your phones in cold areas? By cold I mean under 65 F. I have noticed in certain types of LCD's that if they are cold they seem to slow in refresh rate. Try warming your phone up and see if it gets better.
Click to expand...
Click to collapse
Not really my case I guess, actually the phone kept acting up even after an hour usage, so it was plenty hot. No problems with new one so far, fingers crossed...