Related
Just flashed imoseyon's kernel on my rooted thunderbolt and now I'm stuck in a bootloop...any advice? I've running stock rom.
It's the lean version of his kernel and thats the only thing I flashed. I cleared cache + davik cache before flashing.
I was able to do a restore, but I want to use this kernel
It sounds stupid, but try again. Clear cache and dalvik
I've tried 5 times Even tried uninstalling setcpu and unfreezing all the bloatapps that I had frozen. Still get stuck on boot
I've also tried re-downloading the kernal file in case it was corrupt...no luck still.
Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.
brenick said:
Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.
Click to expand...
Click to collapse
I said its the lean version, and he doesnt post md5sum so I have nothing to compare to. But thanks for using my thread to +1 your post count....
wifi is broke and my data is stuck on 1X only now after doing advanced restore-->reboot only.
Did you flash the GB Sense kernel instead of the Froyo kernel?
I used this 1... http://forum.xda-developers.com/showthread.php?t=1021404 It says Froyo... where can I find the stock kernel that you get after rooting? I need to get wifi/data working again now.
I mount the phone as disk drive on my computer, and I can only view the SD Card...ugh whats going on, so many issues after flashing this kernel
I did a factory reset now and I still cant connect to wifi/3g/4g...I think I need to flash the stock kernel to fix it. Can someone point me in the right direction please?
Flash another rom such as BAMF, whenever you flash a rom it flashes the kernel that is included in the rom as well.
I'm using his kernel just fine. Can you check your radio version?
Sent from my ADR6400L using XDA App
radio 1.16.00.0402, and Im on the stock ROM, dont want to use a special ROM...
Flash a rom or the stock rom that should get you on another kernel. Also, my TB couldn't handle some of the kernels. I was never able to get it at 1.92ghz. I can only use the normal version. Try one of the other versions. Best of luck!
Sent from my DROID PRO using Tapatalk
make sure the kernel is not oc'd to 1.92.................most phones can not handle that.
I recently rooted my TF101 using Razorclaw root and installed clockwerk recovery. I have a B70 tablet that wont use NVflash so im assuming i have the SBK2. I tried to install a kernel and kept booting with a very distorted screen and i couldnt do anything. My question is: is my TF bricked? Does flashing a custom kernel not work on the TFs with the newer SBK's or can my processor not handle being overclocked that high. Because i believe it was a 1.8Ghz kernel that i flashed. I fixed it by pulling out the stock kernel from a rom and flashed that in recovery. Just wondering what's going on here.
Could be your TF not able to handle the 1.8Ghz. Did you install any app to manage
the frequencies, ect.... I use SetCPU but there's other apps that does it.
Make sure it's set to about 1Ghz first before flashing the OC kernel.
After which you can increase it slowly
Well it wouldnt even boot to the lock screen and the screen was all distorted. I dont know if its set at 1.8 right when it boots or lower. or maybe a bad download. but i didnt even have a chance to unlock the thing.
Are you still on the stock but rooted ROM? If so it's probably not compatible with a OC kernel.
im not sure what the problem is. because now, i tried to do custom roms again and im on revolver with a 1.6Ghz overclock and having no problems at all.
kernel flashing problems
I have had the same thing with a couple different kernels. I found some various kernel source trees on git for TF101 and tried rebuilding them and cross-compiling on my Ubuntu system. Most of the time it works fine but there were a couple that when I tried to flash them all I got was a screen full of snowy colored lines, kind of like the snow on an old color TV and could hear some weird 'spacey' sounds coming from it but it wouldn't boot any further. I don't know if these sources were for projects working on ICS or if they were trying to modify source from some other device or what the deal was, but those 2 wouldn't boot.
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,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.
1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)
15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.
As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.
Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.
NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?
Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.
Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!
Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !
It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.
So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.
Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.
Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/
It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.
Megatron is really stable, I've found. I like aosp better too.
Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app
Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?
You'll want to RMA to ASUS if nothing works :/
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.