When I wake the phone after installing this ROM, It takes 2-3 seconds before taps on icons are functional. Almost like the device is still half 'asleep'.
Anyone seen this? Any suggestions?
I really like this ROM and would like to keep it, as it is pretty Vanilla and I prefer the pure Android experience.
Thank you for your time.
Chris
cditty said:
When I wake the phone after installing this ROM, It takes 2-3 seconds before taps on icons are functional. Almost like the device is still half 'asleep'.
Anyone seen this? Any suggestions?
I really like this ROM and would like to keep it, as it is pretty Vanilla and I prefer the pure Android experience.
Thank you for your time.
Chris
Click to expand...
Click to collapse
Have you checked voltages? Perhaps your min cpu speed is very low keeping your phone from fully waking. I cant say for sure thats the problem but its a start. Some kernels can be undervolted to as little as 194mhz which can cause it not to wake. AOSP roms on the S3 have come a long way but still have issues. Hope this helps.
Like the previous post said, first thing is to check voltages. Next I would check min and max CPU clock speeds. If those don't work, consider flashing Lean Kernel. I love the Liquid and Lean combo.
I guess you could also check and see how many programs you have running. Hold home button til they pop up. If you have a ton of running apps then that could also lag you down.
jmarch said:
Like the previous post said, first thing is to check voltages. Next I would check min and max CPU clock speeds. If those don't work, consider flashing Lean Kernel. I love the Liquid and Lean combo.
I guess you could also check and see how many programs you have running. Hold home button til they pop up. If you have a ton of running apps then that could also lag you down.
Click to expand...
Click to collapse
Thank you very much. I will make the adjustments and see what happens.
Related
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
DuratecPaul said:
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
Click to expand...
Click to collapse
Sorry, I doubt it's the kernel. Sometimes things go wrong when installing software. Something went wrong.
Less likely, but still possible, hardware issue. Things do break sometimes.
Can you boot to recovery or bootloader? Does screen work in recovery? Do you know/use ADB? What happens when you're connected via ADB?
Hope you can sort this out.
P.
Try to enter bootloader. From there You will see if your phone is really damaged. You can also flash stock firmware from there, even blind. It will not be hard. I don't think that kernel is Your LCD killer, so try flashing stock and send it to warranty repair.
Sent from my HTC Sensation Z710e using Tapatalk
DuratecPaul said:
Hi Guys not trying to scare anyone couldnt post in developers section, so brought it out here.
Was running RevolutionHD 4.1.5 and wanted to use the 2-way phone recorder.
so installed Bricked-Kernel v1.4r1 installed the radio and cleared dalvik cache and installed system tuner pro so I could underclock 50%.
I noticed it was getting very hot right bottom side under sd microSD card and the screw at right bottom was 70c plus. So I am leaning towards graphics chip being over clocked to far and damaging the connector.
The screen faded to black so i turned it off pulled battery let it cool down and tried a reboot.
System boots and buttons are responsive, no screen , backlights are there.
heat build up is quick and really hot.
Also just connecting the battery, it lights up and starts generating heat.
but still can be booted.
I did under clock and set to boot but did not try to undervolt and set to boot.
Not angry or blaming anyone --->> show-p1984
just putting it out there as a report kinda thing.
Click to expand...
Click to collapse
1st Question: Why would you want to underclock by 50% !?!?
2nd Question: What clock speed did you set it at?
3rd Question: Was the Kernel running fine at the default clock speed?
I haven't used system tuner myself - but if i'm not mistaken you can also set the cpu voltages? Did you change anything there OR maybe you had to change the voltage and didn't?
It could also simply be a hardware failure waiting to happen. I had the same problem with my first sensation. After I moved from ARHD 3.5.2 to 3.6.0 my phone died when I was playing a game. This was due to a slightly faulty graphics chip. I use to have random restarts when I was on stock ROM but never thought about why it happened until my phone died.
My phone has been fixed by HTC and is all good now
Yeah I Have tried to boot to recovery, But its like hitting baseballs blindfolded.
as for ADB Ive got it and used it be4, but havent tried this option yet, Nor do I know all the commands I need to use... good thing search is here 8)
1st Question: Why would you want to underclock by 50% !?!?
2x 780000 is plenty fast enough helps with the battery and theres not many programs I use that needs more than that speed atm
2nd Question: What clock speed did you set it at?
I had it set to low 34.6mhz and to a high of 96mhz ondemand gov.
3rd Question: Was the Kernel running fine at the default clock speed?
yes but was warm ...nothing abnormal tho
I haven't used system tuner myself
I did the cpu clock, tested for half a day.
then set it to boot. was fine.
I set the voltages lower ran them for other half of day, but never set them to boot.
It could also simply be a hardware failure waiting to happen. I had the same problem with my first sensation. After I moved from ARHD 3.5.2 to 3.6.0 my phone died when I was playing a game. This was due to a slightly faulty graphics chip. I use to have random restarts when I was on stock ROM but never thought about why it happened until my phone died.
Yes Ive had the gaming/App crashes on stock kernal too
My phone has been fixed by HTC and is all good now
Yeah Im considering doing a DIY screen replacement, but Im thinking this wont cure it.
And then you get to sort out that nasty lag with the digitiser after doing it
DuratecPaul said:
2nd Question: What clock speed did you set it at?
I had it set to low 34.6mhz and to a high of 96mhz ondemand gov.
Click to expand...
Click to collapse
what kind of clocks are these, are you serious?
RussianBear said:
what kind of clocks are these, are you serious?
Click to expand...
Click to collapse
+1
either its a typo or
surprised the phone even worked at these clocks.
just to be clear. if you boot into recovery (with fully powered off, holding vol- and power button) nothing appears on screen ?
RussianBear said:
what kind of clocks are these, are you serious?
Click to expand...
Click to collapse
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
PaulGiz said:
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
He said his max was 96mhz....you do realise no android phone can run at that max speed? esp a Sense 3 based Sensation. You need at least 400mhz peak freq to be able to use the phone without lag.
but yes that wont cause the screen it go off so not the problem.
PaulGiz said:
Um, minimum clock on most kernels is 192MHz or thereabouts.
If you were really clocked as low as claimed (though I don't see how), I see why phone would blow up.
P.
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
Nah, his phone just hasn't finished booting up yet. It takes a few hours at that speed.
aww dang ... yeah was a typo
was 360 and 920mhz.
but still is fried unfortunately and generating heat....
hmm gonna have to use my gal s2 till this gets fixed
I had something similar with bricked kernel. Installed the one before his latest, phone booted ok but got really hot very quickly, it smelt like a burnt out scalextric car . Quickly pulled the battery and restored my backup. Luckily mine still works fine.
Sent from my HTC Sensation Z710e using XDA App
good luck bro
---------- Post added at 12:17 AM ---------- Previous post was at 12:16 AM ----------
good luck bro..don mess it up
I wouldn't be so quick to deny this as the kernel's fault. I mean, the odds are low, but it is possible. Plus, there is a reason kernel devs, ROM devs, and mod devs always write up a disclaimer, sometimes humorously, stating that it's not their fault if anything happens to the phone. Kernels are direct interaction with the hardware, I've sent bad code to microprocessors before only to have them literally crack open with that nasty, burning component smell.
Some examples that took about 3 minutes to find.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)
Click to expand...
Click to collapse
Disclaimer:
You are flashing this at a risk. I am not responsible for any bricked devices! Thanks!
Click to expand...
Click to collapse
DuratecPaul said:
installed the radio and cleared dalvik cache and installed system tuner pro
.
Click to expand...
Click to collapse
Ever check the md5 & sha1?? If you installed a corrupt zip, then bummer, you f'd your phone.
Try pushing a ruu from adb.
Sent from my Bricked Energy Sensation.
yes checksum's were checked shar's were shar'ed.
cache's cleared and superwiped
I still maintain bricked kernel was the culprit, but I am not blaming but myself.
Just an update to this, the problem still exists but I can plug my hdmi dongle in and see and use the OS (guess that proves I didn't uc/undervolt too much), altho I cant use it to get to recovery.
Im a nub when it comes to ADB, but can use most commands now 8).
its definately graphics chip burn. that 1 corner gets to 80c + within 5mins. which leaves me with no time to flash.
Ive pulled it apart and going to replace the bottom board from here www.parts4repair.com
other than that I picked up a evo3d gsm for cheap and am now playing with that.
There is an easy way to keep it cool. Take cover off, plug in usb, put the phone in the condom. Immerse in water with ice, but make sure condom "neck" is above water. Flash. Boast to people about water cooled sensation. If flashing different Rom/kernel works-profit
Sent from my HTC Sensation Z710e using XDA App
Oh, BTW, you don't need 5 mins to flash kernel.
Sent from my HTC Sensation Z710e using XDA App
Can't figure out why my phone is all of a sudden extremely laggy whenever i wake up the phone. I'm running liquids latest nonsense rom and zooms 1.0.3 kernel. Its so bad I almost want to go back to stock. Whenever I wake most of the time it will wake up and go right back to sleep. then when i can keep it awake it won't catch my input on the pattern pw lock and when it does catch it sometimes won't let me finish my pattern. i can't even answer the phone right away when its sleeping. I have to constantly swipe over and over until it finally goes. anyone experience this? could it be that im min is too low or i'm on smartassv2?
topaz330 said:
Can't figure out why my phone is all of a sudden extremely laggy whenever i wake up the phone. I'm running liquids latest nonsense rom and zooms 1.0.3 kernel. Its so bad I almost want to go back to stock. Whenever I wake most of the time it will wake up and go right back to sleep. then when i can keep it awake it won't catch my input on the pattern pw lock and when it does catch it sometimes won't let me finish my pattern. i can't even answer the phone right away when its sleeping. I have to constantly swipe over and over until it finally goes. anyone experience this? could it be that im min is too low or i'm on smartassv2?
Click to expand...
Click to collapse
Are you over/under clocking?
Are you using an app like SetCPU and have profiles for when your screen is off? (if this is the case, try settings the min a little higher for when the screen is off)
Run fix permissions twice then reeboot.....
Sent from my HTC Mecha using XDA App
orkillakilla said:
Are you over/under clocking?
Are you using an app like SetCPU and have profiles for when your screen is off? (if this is the case, try settings the min a little higher for when the screen is off)
Click to expand...
Click to collapse
tried setting min higher but didn't work. i was using stock speed. Ended up being the kernel as I flashed another kernel and all is well now.
Alright, I've been having this "glitch" on 2 GSIII's. When I hit he power button to lock my phone and what not and then click the physical button to turn it on I always have to hit it multiple times to get the screen up. I've had it on both Liquid Smooth & Codename ROMS and the kernel is the newest version of KT746. Any help or way I can fix this? Its rather annoying..help is greatly appreciated.
Also, my phone is getting really hot quickly, even when all I do is text..
STVERDI said:
Alright, I've been having this "glitch" on 2 GSIII's. When I hit he power button to lock my phone and what not and then click the physical button to turn it on I always have to hit it multiple times to get the screen up. I've had it on both Liquid Smooth & Codename ROMS and the kernel is the newest version of KT746. Any help or way I can fix this? Its rather annoying..help is greatly appreciated.
Also, my phone is getting really hot quickly, even when all I do is text..
Click to expand...
Click to collapse
Have you overclocked at all??? I use my phone very very heavily and have NEVER felt any heat or anything...... As far as the screen issue that could also be the kernel or very possible even the ROM itself.... I know for a while mine wouldn't respond to touching it after I woke it up I would have to hit the power button to darken the screen and wake the screen again... but after a few times it solved itself....
dr12volt1338 said:
Have you overclocked at all??? I use my phone very very heavily and have NEVER felt any heat or anything...... As far as the screen issue that could also be the kernel or very possible even the ROM itself.... I know for a while mine wouldn't respond to touching it after I woke it up I would have to hit the power button to darken the screen and wake the screen again... but after a few times it solved itself....
Click to expand...
Click to collapse
Yes, I'm OC'd to 1809. I'm beginning to believe its the kernel (KT747), this problem has followed me from CM10 Night lies, CNA, Paranoid, and so on and so forth.
I just disabled over clocking and it still took me twice to hit the physical button in order for my screen to come on.
I had this problem on mine when i used the CleanKernel. It would take like 5 or 6 times of me pressing the power button to get it to respond. I changed the kernel back to the stock original kernel via a naindroid backup and i have not had the problem since. Im nervous to flash other roms cause of that issue. Im waiting for more stable builds even though i really wanna try Synergy.... lol
Set from my Verizon Stock Rooted (Modded) Galaxy S3 using xda-developers app
It seams to be kernel related, was running kt with slimbean and could not get power button to wake up the device. Changed to lean and it works when it wants to. I also had the same thing happen on cm9 on another device, so it may just be an aosp thing. Be sure that the option is selected in the main menu too, but as of now I think it is what it is.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
---------- Post added at 06:31 PM ---------- Previous post was at 06:31 PM ----------
Edit: home button
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Video - http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be
Simular to this issue
http://forum.xda-developers.com/showthread.php?t=1826676
legauxg said:
I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Click to expand...
Click to collapse
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.
MasterDecker said:
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.
Click to expand...
Click to collapse
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.
legauxg said:
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.
Click to expand...
Click to collapse
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel
pops106 said:
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel
Click to expand...
Click to collapse
From you response, this is why I am thinking this is related to software. I do not have the proper knowledge to research but I am asking help from a knowledgeable person.
I screen losses touch regularly now. it is taking away from my experience. Are there any drivers particularly for the screen input that can be updated or downgraded to a known working version.
Thanks for not making me fell like I am the only crazy person!
Video to show what Im talking about
http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be
So a friend of mine gave me his old d2g to play with since I've hated my revolution since I got it.
I was playing with some different roms and I really like the CM9 build. Everything works very well except location services and one other major issue. I can reboot the phone and everything is fine. If I shut down the phone, on power up the phone gets stuck on the red M logo screen and that's it. The only way to recover the phone is to reflash 629, re-root, reinstall cm9, etc, etc. Is there a fix for this?
The other big issue is that sometime last night my phone must have reset itself or something. I woke up with it on the red M logo screen. Even though it was plugged in the battery must not have been charging. Now all I can do it get into the bootloader but the bootloader is complaining the battery is too low to program.
What do I do now?
Thanks,
Michael
Update
Update:
Well I got the low battery issue sorted so I was able to SBF the phone.
But I am still having issues with CM9. Any help here? The phone works great until power off or attempting to boot to CWM. Then the phone just freezes at the red M logo screen and I have to start all over.
Update again: I think I solved the CM9 power off problem. I hate it when problems get solved but the solutions never get posted, so here are the steps:
1: Restore 629 sbf
2: Root
3: Install CWM Droid 2 bootstrap
4: Boot to CWM
5: Format System
6: Wipe/Factory reset
7: Wipe Cache
8: Install ROM - do NOT install gapps yet!
9: Reboot
10: Set up most of phone
11: Reboot into CWM
12: Install gapps-ics-20120422-signed - Do NOT use 429
13: Reboot
14: Let phone complete update process
15: Enjoy
I have no idea why that order worked for me and I have no idea why gapps 429 would not work for me. But after 1 day and a half it's working and I am happy. The phone is now very nice. This ROM rocks!
Glad you got everything sorted out, that sounds miserable to have to SBF your phone every time it resets or the battery dies. Welcome to the D2G party even though a little late. So CM9 is pretty dang smooth, battery life isn't the best for me and I don't know if you noticed if you have it set to auto brightness the keyboard back lights stay on whenever the phone is on. Just a heads up.
tuffasagong said:
Glad you got everything sorted out, that sounds miserable to have to SBF your phone every time it resets or the battery dies. Welcome to the D2G party even though a little late. So CM9 is pretty dang smooth, battery life isn't the best for me and I don't know if you noticed if you have it set to auto brightness the keyboard back lights stay on whenever the phone is on. Just a heads up.
Click to expand...
Click to collapse
Late to the party? I would say I showed up after everyone already went home.
Hmm interesting. I have noticed that battery life isn't the greatest and MMS doesn't seem to work.
Mine doesn't seem to be leaving they keyboard backlights on in auto brightness mode though.
So far I am pretty happy with this ROM. Huge improvement over stock.
Radius118 said:
Late to the party? I would say I showed up after everyone already went home.
Hmm interesting. I have noticed that battery life isn't the greatest and MMS doesn't seem to work.
Mine doesn't seem to be leaving they keyboard backlights on in auto brightness mode though.
So far I am pretty happy with this ROM. Huge improvement over stock.
Click to expand...
Click to collapse
Ya, I guess you are correct that pretty much everyone is gone, hahaha.
There is an MMS fix you just have to manually enter in the settings to get it to work, I'm guessing you have Verizon right? It is an issue with CM9 not putting in the APN settings for MMS to send over the internet check out this thread and you will be good to go :good:
http://rootzwiki.com/topic/24897-mms-fix-for-aokpcm9-gummy-and-any-other-ics-based-2nd-init-roms/
Off the subject, if you enjoy playing emulators on your phone for SNES, NES or Genesis one of the benefits of having the qwerty keyboard is you can purchase a rubber gamepad that fits over the keyboard called Game Gripper, than it's like having a portable little gaming machine for old school games.
Edit: One more thing, I just found this thread yesterday and it is supposed to help with battery life, so none of the Cyanogenmods have governors other than ondemand, performance, and userspace. Over on Rootzwiki this person created conservative, smartassv2 and interactive. Just dload them and flash the zip through CWM, I just flashed conservative lastnight so I don't the battery life difference yet but here is that thread http://rootzwiki.com/topic/10911-co...e-interactivex-and-smartass-v2-cpu-governors/
good luck
tuffasagong said:
Ya, I guess you are correct that pretty much everyone is gone, hahaha.
There is an MMS fix you just have to manually enter in the settings to get it to work, I'm guessing you have Verizon right? It is an issue with CM9 not putting in the APN settings for MMS to send over the internet check out this thread and you will be good to go :good:
http://rootzwiki.com/topic/24897-mms-fix-for-aokpcm9-gummy-and-any-other-ics-based-2nd-init-roms/
Off the subject, if you enjoy playing emulators on your phone for SNES, NES or Genesis one of the benefits of having the qwerty keyboard is you can purchase a rubber gamepad that fits over the keyboard called Game Gripper, than it's like having a portable little gaming machine for old school games.
Edit: One more thing, I just found this thread yesterday and it is supposed to help with battery life, so none of the Cyanogenmods have governors other than ondemand, performance, and userspace. Over on Rootzwiki this person created conservative, smartassv2 and interactive. Just dload them and flash the zip through CWM, I just flashed conservative lastnight so I don't the battery life difference yet but here is that thread http://rootzwiki.com/topic/10911-co...e-interactivex-and-smartass-v2-cpu-governors/
good luck
Click to expand...
Click to collapse
Sweet! Thanks for the links. I will definitely be trying that out.
I just got a problem recently with my d2g where it heats up and drains battery like crazy. It usually happens after I have it plugged in for a while and then unplug it, and better battery stats tells me it's a usb kernel wakelock, but that shouldn't be happening while the phone unplugged. Anyone else experience this before?