Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
I had a stock Froyo on my phone and I tried following the steps of this thread : http://forum.xda-developers.com/show....php?t=1894737
The first mistake I did, was I flashed XXKPQ directly by mistake instead of XXKPE, which I noticed while I was in the middle of doing it.
The phone was working properly on the GB rom. After that I rooted it, following the guide using a cf root of XXKPQ.
Now, I didn't know if there was prerequisite for it or not, but I flashed the custom rom of http://forum.xda-developers.com/show....php?t=2300693
The first problem I saw was that while installing it from the sdcard, for a long time, the screen was blank. I left it thinking that it was part of it, but since it persisted, I rebooted it. The phone opened properly and after that I installed the gapps later through recovery mode.
The first major problem I saw was that the phone after screen locking, it used to shut down automatically. After looking through solutions, where none were working, I tried flashing to stock rom via odin (stock rom : http://forum.xda-developers.com/show...php?p=16107097)
After that though, whenever I open the phone, it just stucks at the samsung logo screen and doesn't go further.
Also, when in download mode, I tried it attaching to Odin but "USB device not recognized" comes all the time.
I don't know what to do.. I know I must have made loads of huge mistakes and I should have done everything, being properly informed, but now I really need a solution..
Click to expand...
Click to collapse
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?
tyson123g said:
Okay, I am practically a beginner with this. Also, I did my flashing/rooting a month back, so I might muddle some of the facts.
The thing is, at first I had this problem : Thread
So, in the end, I remember re-flashing it to DDLF2 and then doing the XXKPE + XXKPQ + BAM Kernel + CWM 10.1.
But there is a SOD. After a while, it suddenly switches off.
Can anyone tell me what to do, to solve this problem and if someone has patience, please help me step by step? In the end, I want to have a JB custom rom in my phone. I just want to get there, without having any problems.
Any help please, removing this SOD?
Click to expand...
Click to collapse
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.
karthik gowtham said:
Flash It Again From First In Download Mode And Root It And Go To An Custom Rom.
Click to expand...
Click to collapse
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?
tyson123g said:
Do you mean the same process I used? DDLF2 -> XXKPE + XXKPQ -> BAM Kernel + CWM 10.1
Or am I missing something or adding something in the mix, which I shouldn't?
Click to expand...
Click to collapse
Why Do You Got To XXKPE From DDLF2 ,All I Was Trying To Say Was
XXKPE--->DDMF1--->CF-Root or Custom Kernels--->CM10.1 or Any Other Rom.
Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?
tyson123g said:
Thanks, the above way helped.
I installed using the process you mentioned, installing the CF Root for DDMF1 and then finally installing REMICS latest one (5.x).
But it is still a bit slow. So, I was thinking of overclocking it.
Can you tell me, which kernel should I flash?
Click to expand...
Click to collapse
REMICS v6 now is out (smoother and more stable)
kernel 3.0.8 by dhiru1602 does not support OC but you can change the governor to ondemand or performance (performance>>processor>>CPU governor) and the I/O scheduler to deadline (performance>>I/O scheduler) but first you have to enable the developper options (7 hits on the Build number).
Hit thanks "button" if i helped you!
regards
Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.
tyson123g said:
Thanks for the suggestion, but I think I am missing something here.
I tried searching for the kernel, but I just can't seem to find it.
Am I doing something wrong?
Edit : Okay, so I searched and found out that most of the newer ROMs have it installed in itself, is that right?
But when I installed the REMICS 5.8 and tried using the no frills CPU app, I just don't see any option beyond 1 GHz.
Click to expand...
Click to collapse
Yes, because as i know kernel 3.0.8 by dhiru1602 which is the default (preinstalled) kernel of CM10.1 (Jelly bean 4.2.2) (REMICS 5.x and 6 and the newer jelly bean roms are based on CM10.1 by dhiru1602) does not support OC and you won't find other kernel for CM10.1 better than dhiru1602 kernel (it's only my idea).
I think dhiru1602 didn't implement OC in his kernel for reasons of stability and battery backup...and you don't have to use no frills CPU app anymore, just 7 hits on the Build number (About the phone >> Build number) will enable the "developper options" and "performance" (in "performance" you can change the CPU governor and I/O scheduler).
And don't use REMICS 5.8, REMICS 6 is better because many bugs were fixed!!!
Hit thanks "button" if i helped you!
regards
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
in CM10.1 kernel overclocking is not there for some stability issues... overclocking is possible but do it at your own risk
tyson123g said:
Thanks for the reply.
Just had one little question..
Even in the performance options, as the same in the no CPU app, my maximum frequency is always 1000 MHz?
Is it always like that, or should I go beyond it as well? I thought I was overclocking so I expected an option beyond it..
Click to expand...
Click to collapse
You really don't need to OC your CPU....if you are facing some lags in CM, this maybe because you didn't wipe data before install CM.
Usually I downclock my cpu to 600MHz and set the governor to conservative to save battery without facing lags...so really CM10.1 A8 is not lagging!!!
Okay. I have to install REMICS 6 anyway. I will try again. Hopefully this time, it is quick.
Well, I changed my mind and went with CM 10.1 A8. It is fast and good.
But for some reason, my phone is rebooting by itself.
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
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.
Few questions after installing Revolver 4.2...
I try to install Guevor's 22.6 kernel, it goes through the process and it says complete. I reboot and the kernel still says 2.6.39.4 android @mars. What am I doing wrong?
Also when I tried to install the kernel through Revolver Parts, it doesn't download the file into sdcard/Downloads. I couldn't find it anywhere so I had to download it manually.
Also, am I able to boot my system so it automatically loads the rom? Everytime I boot it automatically loads into CWM and you have to manually get it to boot. Anyway around this?
Finally, can someone explain overclocking real quick to me? Can I overclock on this android @ mars kernel? (If guevor's works, I'd do it on that). I thought I could go on SetCPU and just change the clock speed to whatever I wanted (1.5GHZ for example). Instead there are two filters, one that is maxed at 1GHz and the other at 200MHz. What would the equivalent of 1.5GHz to set both bars accordingly?
I would REALLY appreciate if someone could help me out, total NOOB lol.
short answers:
its not an overclockable kernel then
and
if you can Nv Flash a rom and recovery then its probably the easiest way to resolve the cwr loop.
if you used rom manager then i would advise not doing that ever ever again on the Tf. (just a guess)
Read me and if you get it resolved with Peri then remember to thank Thing of Doom.
scottyf79 said:
short answers:
its not an overclockable kernel then
and
if you can Nv Flash a rom and recovery then its probably the easiest way to resolve the cwr loop.
if you used rom manager then i would advise not doing that ever ever again on the Tf. (just a guess)
Read me and if you get it resolved with Peri then remember to thank Thing of Doom.
Click to expand...
Click to collapse
I just read that Guevor's 22.6 is a stable kernel. Even if I don't overclock it, it should replace the stock kernel no?
And yeah I used ROM manager to install the latest version, why would it mess it up? What is "Nv Flash"?
Okay got everything working. Transformer boots perfectly, new recovery works a lot better, installed the kernel and have it clocked to 1.5GHz
Thanks again!
BTW- Uninstalled ROM Manager :silly:
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
spidasense said:
so I, for the first time, flashed that new kernel on the front page of this discussion which overclocks the cpu. I have the newest version of jellybean installed so I considered that a stock based rom and thought it would work. in power svae mode the screen would go all crazy, balanced mode it was aalright except it would crash after a while. peformance mode would crash even sooner. so I found a stock based kernel and flashed that. Everything is fine now except the previous kernel changed some settings on the screen rresolution or something with the gpu which increased screen size I guess cause now my custom Hubs GUI is all spaced out which I had previously and meticulously spaced before hand. it caused smaller screen titles and smaller widgets basically making things look out of proportion. is there a way to revert those settings? it seems since the stock kernel doesnt innately change gpu settings that it didnt revert the settings initially set by the first kernel. the kernel I flashed to fix it was a stock kernel slightly modified from cleanrom to do something dpi and some other unimportant thing so it isnt the completely stock kernel but it is stock based. does anyone think If I flash a true stock kernel it will get fixed? if so can I get a link to said kernel or will I have to extract it myself from a stock rom
Click to expand...
Click to collapse
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
buhohitr said:
You can't use custom OC kernel with stock rom. You need to flash custom rom like Cleanrom and you can flash what ever kernel you want that designed for CleanRom.
Click to expand...
Click to collapse
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
p.s. can I flash roms on my tablet without losing app data or settings or my hub UI settings? im on 4.1.1
Click to expand...
Click to collapse
You should able to flash cleanrom without losing any data, during the install there're options for many kernels, I suggest try the "_that stock kernel" first
spidasense said:
ooh I see. the kernel I flashed was the clemsyn kernel and I just saw that it was for clean rom. damn ok lesson learned. anyway to revert the setings it changed on my gpu?
Click to expand...
Click to collapse
Anyone else with an unlocked bootloader uses a custom ROM that sets the display dpi. This has nothing to do with the GPU, it's just a setting that tells Android the display resolution so that it can scale UI elements accordingly.
To get your 240 dpi back, either install CleanROM Inheritance, or the first kernel in this thread:
http://forum.xda-developers.com/showthread.php?t=2106689
that is actually the kernel Iflashed to ttry and fix the dpi. thanks for informing me on that, I had a hunch dpi had something t odo with the problem I was having. I only tried one of them I guess theother one (ill have to check my sd card to find out which one ) will fix it.
and to be clear, I can flash clear rom inheritince and not lose app data or settings?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Hey everyone,
After trying almost every single ICS ROM available for my O1 P500h, every ROM seems to have the same problem. Although they all run very good, the phone will just hang at random points, but mostly when installing apps. Then requires a hard reset battery pull, or will reset itself after about a minute. Does anybody know of a solution to this? It wouldn't really be that much of a problem if the phone didn't take so long to restart.
I've seen other users report this problem to ROM dev's as well however the problems seemed to be fixed for them by a newer update for the ROM, but even if I use the newest version I still get this problem.
It's not present on CM7, or Jelly Bean (4.1 or 4.2) ROM's as far as the ones that I've tried. I feel like I've tried every single ROM for this phone already. I wanted to move on from CM7 because of it's lack of new-ness compared to ICS and above, and on the other hand Jelly Bean ROM's don't have a lot of internal storage compared to ICS ones, which is a problem for me because I download lots of apps.
Any help would be greatly appreciated!
TheCrazyDirectioner said:
Hey everyone,
After trying almost every single ICS ROM available for my O1 P500h, every ROM seems to have the same problem. Although they all run very good, the phone will just hang at random points, but mostly when installing apps. Then requires a hard reset battery pull, or will reset itself after about a minute. Does anybody know of a solution to this? It wouldn't really be that much of a problem if the phone didn't take so long to restart.
I've seen other users report this problem to ROM dev's as well however the problems seemed to be fixed for them by a newer update for the ROM, but even if I use the newest version I still get this problem.
It's not present on CM7, or Jelly Bean (4.1 or 4.2) ROM's as far as the ones that I've tried. I feel like I've tried every single ROM for this phone already. I wanted to move on from CM7 because of it's lack of new-ness compared to ICS and above, and on the other hand Jelly Bean ROM's don't have a lot of internal storage compared to ICS ones, which is a problem for me because I download lots of apps.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
which recovery You are Using & How do you flash the Rom & what rom you flashed try CM9.2.0 By hephappy
umm
Amitosh said:
which recovery You are Using & How do you flash the Rom & what rom you flashed try CM9.2.0 By hephappy
Click to expand...
Click to collapse
I've tried TWRP, CWM 5.0.2.7 and CWM 6.0.2.7. I've been flashing by formatting everything but sdcard (so boot, system, data, cache, etc.) and then installing zip from sdcard. I tried flashing HepHappy's ROM, IcySnap, XperiaICS and Protos9.
TheCrazyDirectioner said:
I've tried TWRP, CWM 5.0.2.7 and CWM 6.0.2.7. I've been flashing by formatting everything but sdcard (so boot, system, data, cache, etc.) and then installing zip from sdcard. I tried flashing HepHappy's ROM, IcySnap, XperiaICS and Protos9.
Click to expand...
Click to collapse
Stock kernel..?
umm
Amitosh said:
Stock kernel..?
Click to expand...
Click to collapse
The stock kernels which come with the ROM's, which allow you to overclock the phone to 800-something MHz. I never use the overclock though and keeping it on 600MHz that comes out of the box still has the problem. With GB I'd overclock it to 729 for normal use, and on JB 748 for snappier performance with no bad things happening (well, besides battery life)
TheCrazyDirectioner said:
The stock kernels which come with the ROM's, which allow you to overclock the phone to 800-something MHz. I never use the overclock though and keeping it on 600MHz that comes out of the box still has the problem. With GB I'd overclock it to 729 for normal use, and on JB 748 for snappier performance with no bad things happening (well, besides battery life)
Click to expand...
Click to collapse
Do You Run Plenty Of apps at a time Because that cause Reboot..., The kernel candied(Ice) Give me problem like yours. if there is no solution switch to 4.1.2 AOKP it is stable.