Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
(summarized below in tl;dr version)
Since my problem I need help with showed up after going back to stock + root, I thought I'd ask in general before filling up the ROM discussion in development about the problem that I found after updating to ICS (leaked).
Had an odd problem crop up on me with scrosler's CleanROM 2.2 SP1 running (will 'splain in a sec, and tl;dr sum-up at the end), so I relocked, flashed back to pre-OTA official firmware and then let the OTA run. All was good, and I was happy. I unlocked again, installed Amon Ra, reinstalled SU, and started putting in my happy-fun root required tools (Oh Titanium, I likes you so). Then, my problem reappeared.
So my problem is occasionally the touchscreen would act "wacky" at times. Specifically, while in my browser, sometimes when I tried to scroll while browsing, the display would act like I was using pinch-zoom. It acted like I was touching the top left corner of the display in portrait mode, and zoom-in/-out according to how I was moving my touch that I intended to scroll. Then I noticed that games which required multi-touch had significant problems reading constant touch on most of the top-half of the display (left half in landscape mode with the carrier name on the left). I like Age of Zombies, and while the game would start off running right, within 20-60 seconds, the movement virtual controller would rapidly turn on and off, leaving me able to fire but not move. Grand Theft Auto was unplayable, as every time I touched a direction key in driving mode, the system would lose track of my holding the gas.
Troubleshooting took a while, as I had installed a lot of apps, and made a few changes at once after everything appeared to run properly. Ultimately, the problem appears to be caused by underclocking, and I can't figure out how to kill that and lock myself at stock speed. Haven't tried an overclocking capable kernel to see if they run any better, and haven't tried checking voltages to see if bumping them on underclocks would fix it.
I have used Antutu CPU master, an old version of SetCPU, and System Tuner Pro (from 3c). I can set the min and max CPU to 1.52, and it seems to stay for a while, but eventually, the setting reverts to allowing underclocking and my touchscreen gets goofy.
tl;dr: My system, even after restoring to RUU/OTA, wants to underclock. When the CPU runs under stock speed, my touch-screen misbehaves, particularly in gaming, but also in browsing. Any help?
Thanks
Can almost definitely confirm it's just bad hardware at this point.
After running 2 days without problem other than the touch-screen issue noted above, the phone entered an persistent bootloop after I loaded Juice Defender today. Phone would reboot, come up to home screen, get a data connection, tell me how many new email and texts I had, then tell me an app (same every reboot) was not responding and reboot 2-3 seconds after I cleared the error. Even when I managed to get to market before a reboot and uninstall the last 2 apps I'd installed, the phone is still in a boot loop.
Appreciate all that took the time to read, and wanted to share that there's a pretty good reason no one could respond with a solution.
Well, it probably is bad hardware but two cardinal rules I have when working on any Rezound is NEVER restore with Titanium BU & don't use Juice Defender (and I have a paid version of it).
I have had both mess up certain phones & I do this stuff all day at work.
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
AtLemacks said:
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
Click to expand...
Click to collapse
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Me 2
aostl said:
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Okay so I have a similar problem.
I have hephappy cm9 prefinal installed just started having problems with rom. screen was acting funny so I turned on the touch point developer tool supplied with the rom. I have found that I have multiple touch points when scrolling with one finger.
So I used a apk called touch recalibrate that I got when I was on mik's cm7.
Which I have recalibrated aprox 7 times with no improvements so I set my cpu to min 600 max 600 smartassv2 this did not help either. If anyone has the answer to this problem please let me know.
Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
plotinus said:
Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
Click to expand...
Click to collapse
Yes, the average wake time on GB was about 650ms, in ICS its about 1000ms, this is how it works, there is nothing that custom kernel or ROM devs can do about the situation at the moment.
Home button lag has always been an issue, there is a fix for this issue incorporated into a a few roms and themes, maybe try one of them
what cpu governor are you using and are you on stock frequencies? I use 500mhz as a min (voltage diff between is 200 and 500 at lowest values is on 25mV for me) and this improved it slightly.. could be placebo though
viva.fidel said:
Home button lag has always been an issue, there is a fix for this issue incorporated into a a few roms and themes, maybe try one of them
what cpu governor are you using and are you on stock frequencies? I use 500mhz as a min (voltage diff between is 200 and 500 at lowest values is on 25mV for me) and this improved it slightly.. could be placebo though
Click to expand...
Click to collapse
I thought and read that home button lag refers to the moment I'm in an application and press the menu button to go to Home screen. The lag was because the phone kept waiting for another press to open voice commands. Am I right? I've read it somewhere around here..
And I've been using 200mhz min and 1200 max with ondemand governor. Stock values
~ ~
° °
----
plotinus said:
Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
Click to expand...
Click to collapse
Which rom and kernel are you on?
Sent from my GT-I9100 using xda premium
I believe I read a while back in the CM9 thread, entropy512 said the 1000ms delay is hard coded deep in the ICS kernel code, and there is nothing much anyone can do about it, its up to Google.
Sent from my GT-I9100 using XDA
kilometers4 said:
Which rom and kernel are you on?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I've been on paranoidandroid, hidrogenICS, Epsilon project and stock ICS,fluxi kernel, siyah, speedmod, stock kernels and they've been the same. It's not much of a problem but I wanted to know if it was rom related or something else. Think I've found my answer thanks
~ ~
° °
----
TheReverend210 said:
I believe I read a while back in the CM9 thread, entropy512 said the 1000ms delay is hard coded deep in the ICS kernel code, and there is nothing much anyone can do about it, its up to Google.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Oh. I see, well, found my answer thanks for your help!
~ ~
° °
----
Try this way
its happend to me before and its gone !
if you have external SD card remove it and try again without it
i think the reason of this delay for me was the SD card .. it comes with 4 GB and class 4
i replaced it with 16 GB class 10 and everything is ok
if it was the same reason for you try any SD card with class higher than 4 .. class 10 recommended accurding to my experience
______________
if the reason was't the SD card .. i'm sorry because I'm trying to help
it only happens on ics its the way they have made it to save on battery
if you go to the market and get the the app called soft locker it will solve the prob :laugh:
JKAY's framework v 14.0 may help
jkay's framework has an option under set common lockscreen settings>> fast unlock
When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
wman2 said:
When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
Click to expand...
Click to collapse
Flash other ROM can make it faster...
Or tune off power saving mode.
photomrq said:
Flash other ROM can make it faster...
Or tune off power saving mode.
Click to expand...
Click to collapse
Power saving mode is already off. I don't particularly want to flash a ROM unless I have to because I've had warranty troubles in the past. Are you certain a ROM would fix it? Which ROM?
And I also tune lock screen off.
Do you install any power save app??
Two Whole Seconds close your eyes and count to ten not worth the bother wait for JB release ,
jje
I get this also. Got it on the Stock ROM and ARHD. I have also seen this on my gf's Galaxy Ace, but only when upgraded to GB. On Froyo (Yes, that old version) it turns on instantly. So think it might be a Samsung thing. Not yet tried an AOSP ROM on my S III yet so may give that a go as itching to get some Jelly Bean on it.
Hello! I am new to xda forums and this is my first post
I also have a problem with slow wake up time from sleep after flashing the latest Synergy rom. Any ideas why this lag happens?
Thank you in advance!
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
bojler said:
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
Click to expand...
Click to collapse
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Lag is hardware-related looks like. Present on CM10 based ROMs as well. On stock-based disabling S-Voice helps just a little bit when it comes to waking up from Home button...
Killing me as well. :\ What I getting used to is to press Home while pulling phone out - straight away so by the time I get it in position to work with, the screen is either already on or will be on in a 200-500 ms.
Still this is a most frustrating "feature" of SGS3 that will most likely force me to look for replacements once those are available on the market.
The issue is still present even in the latest Paranoid Android ROM.
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
inteq said:
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
Click to expand...
Click to collapse
No difference here
Sent from my GT-I9300 using xda premium
This problem annoys me to death too. I've tried many ICS/JB stock ROM and custom ROM (including CM10), but none of them could solve the problem.
I did notice some trend: right after a reboot, the screen turns on fairly quickly. Then after turning on the network (mobile data or wifi) and use facebook or other apps that access network for a few minutes, the delay starts to increase to the usual ~2sec. Looks like some network process might be causing the problem. FYI, My cousin's Note 2 don't seem to have this problem.
Any hacker out there can give some hints or help find out what process might be the culprit?
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
"not as good" would be too soft of a term. It'll kill your battery life probably
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
ligu said:
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
Click to expand...
Click to collapse
no other brands have this problem. only samsung, thats so strange.
I too suffer from wakeup delay of 1-2 seconds and it's driving me crazy.
After 2 long years I had to live with majestically f**ed up LG Optimus 2X, I finally decided to throw that junk away and get a phone that works as expected, phone performance of which would be equal to it's price (and the price was not something that limited me).
Now I own a phone which even though is snappy and nice and everything, takes ages to wake up. And what pisses me off the most is that Samsung is OK with that, because obviously majority of the customers / owners is OK with that. How is that possible ffs. Low end devices for fraction of that price resume from deep sleep almost immediatelly (in time I don't consider waiting). How's that this is not a big issue ?!
Sorry, I'm just frustrated
EDIT: To add something constructive ... the deep sleep really is the problem here. If the phone doesn't go to deep sleep, wake up to lockscreen is instantaneous (try that by yourselves with SoftLocker app). It's believed that S3 suffers from this issue because of the way the GSM modem is integrated with (or in ? I am not sure) Exynos4 - source.
I just smacked my phone in the table, while in my pocket and now I"m experiencing the same problem. Is this even possible, or I had it before and just didnt notice till now?!
Hello all,
Could anyone please explain to me why when the 'show screen updates' option is ticked in the developer options and the phone is kept in landscape mode, a small portion of the screen next to the SONY logo refuses to update with the rest of the screen ?
The resulting pattern is not a flash of color per update but a couple of vertical black lines that aren't evenly spaced.
This pattern however disappears when the screen is touched several times and reappears when the scrolling is stopped.
This seems to occur only in stock [.10,.54,.89] firmwares and stock based ROMs .
It DOES'NT occur in CM based ROMs however. So a hardware issue is ruled out .
I thought that the problem was 'screen tearing' but now I'm not sure ...
Edit: Video link :http://www.youtube.com/watch?v=KjwNp8CcjDc .
I could really use some help in debugging this problem :fingers-crossed:
I can post a video of the above problem if anyone needs me to.
EDIT: Video link posted see post No. 7
Its because Sony hates our device and dont want to male good firmware for it. Fa*s
Sent from my ST25i using Tapatalk 4 Beta
Mikulic1802 said:
Its because Sony hates our device and dont want to male good firmware for it. Fa*s
Sent from my ST25i using Tapatalk 4 Beta
Click to expand...
Click to collapse
LOL .... Does it occur on your phone too?
Afaik screen tearing in landscape mode, just there next to the sony logo, is a know bug, and that must be connected to your problem. And yes it occurs on my phone too
Sent from my ST25i using Tapatalk 4 Beta
Mikulic1802 said:
Afaik screen tearing in landscape mode, just there next to the sony logo, is a know bug, and that must be connected to your problem. And yes it occurs on my phone too
Sent from my ST25i using Tapatalk 4 Beta
Click to expand...
Click to collapse
So you suspect screen tearing too huh ? :good:
I've tried adding available Vsync scripts but it doesn't work... CM ,MIUI & Stock GB Roms have no occurrence of this
I'm on GB ROCKS V3 now coz I cant stand this one issue.
Sony seems to be releasing ICS firmwares regularly [Ref. new b.100 firmware]BUT Still NO SIGN OF A FIX!!
Even stock unofficial JB has the problem =( .
Ive tried asking a kernel developer for help but he seems too busy.
See ,
I've observed that if the kernel frequency is kept above 400Mhz i.e 500Mhz and above then there is ZERO distortion! , now the only kernel with a frequency table having 500Mhz is the Transcendence kernel which can't seem to keep the MIN frequency fixed over time so it jumps back to 200Mhz .I've reported the problem and I hope it's addressed. This seems to be the only work-around . Try it yourself keep min frequency at 800Mhz and max at 1Ghz and BAAM ! No tear !
I really hope that a developer takes notice of this problem and attempts to fix it without messing with the CPU frequencies ...:crying:
Video link
Here's a link to the video
Hope that someone figures out what the problem is :
http://www.youtube.com/watch?v=KjwNp8CcjDc .
:fingers-crossed: