Related
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
76redrum said:
i flashed and my phone seems to lock its self when the screen goes black i cant get it to turn on or for the lock screen to show up the only thing that happens is that the lights at the bottom come on the home buttons the back etc. can someone tell me why plz
Click to expand...
Click to collapse
Hi,
What version did you install?
3.6.8 or 4.1.8?
Did you do a MD5 checksum?
Did you super wipe?
Did you add any mods?
If you want help,you need to post more information...
Hi i had the same sort of problem with my ARHD but I find out that the faux kernel was causing for difficulties.
Installed a stock kernel and all problems solved.
Still respect all developers
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
76redrum said:
did a the super wipe, did a md5 checksum, and didnt do any mods, and it arhd 3.6.8
Click to expand...
Click to collapse
Hi,
It does sound like a kernel problem.
Try the kernel in my signature.
Absolutely no problems there.
ill try the stock kernel thanks to all
phone:htc senation
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any digestions would be very appreciated
So I've tried the stock kernel I even tried flashing arhd 3 times as I read that sometimes on the third try everything works right but no luck so if I can't get it working properly I'm going to try another Rom but I was thinking could the problem be daemon controller...any sugestions would be very appreciated
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
seatown1two said:
Recently flashed arhd 3.6.8 and I am having similar problems. More often than not, i will lose responsiveness with the touchscreen and have to pull battery. Also my phone randomly reboots and restarts. Can someone tell me how to fix this???
Click to expand...
Click to collapse
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
---------- Post added at 03:15 PM ---------- Previous post was at 02:25 PM ----------
Hawke84 said:
try flashing the kernel in my sig, this sounds like a kernel problem. theres a new ARHD 3.6.9 but the kernel in my sig is newer than the included kernel, hopefully this should fix it for u..
Click to expand...
Click to collapse
Hi, i've been running the 3.6.x Roms for a while now and think they're great, but was getting interested in the sense 3.5 stuff. What in particular do you like about the 4.1.x roms? Just seeing if it's worth the full wipe effort .
Thanks
Mike
ArcticWolf91 said:
I sold a Sensation ebay with this same rom, and the buyer is reporting the exact same issuse you are having. I think there might be something going on here.
Click to expand...
Click to collapse
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Hawke84 said:
hmm maybe not the best move selling a sensation with custom firmware, u may be stuck troubleshooting it now...
Click to expand...
Click to collapse
Lol yes, you are not the first to tell me that, and believe me lesson learned. Though I did mention that it was rooted and that it would be running this Rom. But yes now I am troubleshooting the phone with this person and I may have to give them a refund because they opened a case with eBay.
mrew42 said:
Up the minimum sleep clock speed to 384000 or 432000. the cpu is too idle to react properly and this should fix it. I had the same issues with Faux & Bricked kernels until I did this. No problems at all now.
Click to expand...
Click to collapse
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
seatown1two said:
How exactly do I do this???
Also if it comes down to it... how do I flash the kernel or w/e and wtf is it going to do...
Click to expand...
Click to collapse
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
mrew42 said:
Daemon Controller comes with Revolution HD roms.
Run the app and you can see the options for setting the clock speed of your CPU while active and idle.
If you do flash a new Kernel you should generally be OK without a wipe/factory reset, though make sure you do a NAND backup via clockworkmod first.
Flashing the Kernel works in exactly the same way as flashing a Rom, via clockworkmod (or whatever recovery tool you use - EXT4?) - Download the new kernel to your SD card and install from there.
If you get the latest version of the ROM it will have the latest Faux Kernel in anyway, so maybe it's worth trying that? - again you should have no need to wipe/factory reset unless your moving from 3.6.x to 4.1.x Roms (different base android versions 2.3.4 vs 2.3.5)
Like I say, I used to suffer from the same issues with the screen not responding to wakeup but since I upped the clock speed for idle (and recent updates do this by default now) It hasn't happened since
Regards
Mike
Click to expand...
Click to collapse
how do you up the speed for idle..silly question i know
Hello. I have got very annoying problem. I'm using Kyrillos 9.4.
Sometimes (twice a week) my g3 get freeze, and I can't unlock it, because screen don't light on. I must get battery off and on and after battery remove phone works as new.
I have this freeze on every kernel (G3MOD oc, non-oc, kyroarokernel)
Is there any fix for this issue?
This is annoying in the long run.
Do you have this problem too? Or my g3 has got defect?
PS. When I'm using stock, Samsung rom this issue does not exist.
Do u undervolt?
Cheers
Sent from my i9003 powered by Poseidon's Rom/Dxkp9 Junior + UC kernel
No. (10 characters)
mosak said:
No. (10 characters)
Click to expand...
Click to collapse
Then I'm not very sure. The only causes I know of freezes is undervolting and overclocking. Since u do neither, I don't know. I would wipe cache and dalvik cache, if doesn't work factory reset, if doesn't work reflash. Are u sure u tested on non-oc kernel?
Cheers
Sent from my i9003 powered by Poseidon's Rom/Dxkp9 Junior + UC kernel
Yes, I'm sure. Now i have got Non-OC kernel (G3MOD 2.3 non-oc). In set CPU I can set max frequency 667Mhz.
But on non-oc i have got this issue less frequently than on oc.
Maybe 1-2 times at month.
Have you ever got same frezze like mine?
Thank for help
Maybe once or twice on oc. I'm nt sure wad is causing your problem, but if its very little freezes then maybe you can live with it?
Cheers
Sent from my i9003 powered by Poseidon's Rom/Dxkp9 Junior + UC kernel
mosak said:
Hello. I have got very annoying problem. I'm using Kyrillos 9.4.
Sometimes (twice a week) my g3 get freeze, and I can't unlock it, because screen don't light on. I must get battery off and on and after battery remove phone works as new.
I have this freeze on every kernel (G3MOD oc, non-oc, kyroarokernel)
Is there any fix for this issue?
This is annoying in the long run.
Do you have this problem too? Or my g3 has got defect?
PS. When I'm using stock, Samsung rom this issue does not exist.
Click to expand...
Click to collapse
try flash the kernel with odin, using tar file. And next wipe data
Ok. I flashed kernel via Odin and now it's ok.
I post new reply after 100h uptime (or first freeze )
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?
Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL
Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.
UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.
fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.
hi guys, i'm having lots of problems with faux's kernel both ultimate and mainline. everytime i flash the kernel or use a rom that includes the kernel (clean flash of course) i always get constant random reboots, system FC's, freezing that forces me to battery pull.... pretty much every error you can get besides a bootloop. this is really strange to me because i've ran the faux ultimate kernel when i was running GalaxyMod RLS11. i've tried everything i can think of to fix this, does anyone have any ideas on why i can't use this kernel anymore?
mrchu001 said:
hi guys, i'm having lots of problems with faux's kernel both ultimate and mainline. everytime i flash the kernel or use a rom that includes the kernel (clean flash of course) i always get constant random reboots, system FC's, freezing that forces me to battery pull.... pretty much every error you can get besides a bootloop. this is really strange to me because i've ran the faux ultimate kernel when i was running GalaxyMod RLS11. i've tried everything i can think of to fix this, does anyone have any ideas on why i can't use this kernel anymore?
Click to expand...
Click to collapse
Have you tried going back to GalaxyMOD RLS11 to see if its having current errors?
freestyle350z said:
Have you tried going back to GalaxyMOD RLS11 to see if its having current errors?
Click to expand...
Click to collapse
i would but i cant find it on PM's file hosting site :/
Have you thought about simply switching kernels?
mrchu001 said:
i would but i cant find it on PM's file hosting site :/
Click to expand...
Click to collapse
Like ^ said try other kernels, Imoseyon LeanKernel or Ktoonsez KT747 would be good substitutes to start with, you can compare them if needed I have no personal preference for these, as they are both reliable.
Hi guys,
As the title stated, I couldn't get the wifi to work at all. I tried flashing both stock and custom roms, but I still couldn't make it work. When I slide the wifi "on", it immediately slides back to "off". It didn't even scan for networks. Does anyone know what is the cause of this problem and how can I fix it? The last working custom rom I used was the Infusion rom. Right after I install the stock firmware, the wifi no longer works anymore.
Thanks.
failmuch said:
Hi guys,
As the title stated, I couldn't get the wifi to work at all. I tried flashing both stock and custom roms, but I still couldn't make it work. When I slide the wifi "on", it immediately slides back to "off". It didn't even scan for networks. Does anyone know what is the cause of this problem and how can I fix it? The last working custom rom I used was the Infusion rom. Right after I install the stock firmware, the wifi no longer works anymore.
Thanks.
Click to expand...
Click to collapse
I got the same exact problem after I flashed the faux kernel. :/ Were you able to find a solution yet?