Today a tried ogo2's beta3 ROM. In SetCPU I can't change the frequency. There are min 480-max 600 Mhz, if I change the value, nothing happens. That's wrong because it drains my battery.
Yeah, same problem here... such a pity because other than that its a great ROM!
Not really an 'issue' - the kernel isn't set up to allow overclocking, so why would it?
Not just overclocking. I can't go under 480 Mhz. That's a bigger problem for me.
cserepg said:
Not just overclocking. I can't go under 480 Mhz. That's a bigger problem for me.
Click to expand...
Click to collapse
I don't think the kernel allows you to change clock speeds from the MAX600 MIN480 HTC set as the default. Not an issue, but that feature will be added sometime (ogo2 said it would eventually I think)
OK, I thought that the default min clock speed is 245 Mhz.
Oh ok, didn't know it depended on the kernel, thanks.. This may be a totally noob question, but this is the Q&A section so, can I not just flash another kernel that does enable overclocking...?
Guys, cannot start neither beta3 nor beta4. When flash beta3 (through Clockworkmod 3), the system doesn't load, green 'HTC' letters tend to reboot. After beta4 installation the same screen, but static - without any reboots. I have S-ON. Wiping doesn't help.
Please, advise what to do.
Cheers!
cserepg said:
Today a tried ogo2's beta3 ROM. In SetCPU I can't change the frequency. There are min 480-max 600 Mhz, if I change the value, nothing happens. That's wrong because it drains my battery.
Click to expand...
Click to collapse
I eventually answered my own question.. You can just flash another kernel.. Look under the Overclocking tutorial in the Dev section...
It's ok now, I am using B-ROM. In this I've got too much reboot, battery drain, GPS issues, etc. Maybe beta 5-6-7 will get a chance...
cserepg said:
It's ok now, I am using B-ROM. In this I've got too much reboot, battery drain, GPS issues, etc. Maybe beta 5-6-7 will get a chance...
Click to expand...
Click to collapse
I'm using Blay0's ROM as well, haven't had any issues so far... are u doing a full wipe before you flash the ROM...?
If I installing a different ROM I always do a full wipe sure. I did not do full wipe, if I installing a newer version of a same ROM. Btw the most stable ROM is Blayo's, next Cyanogen, but there are no new sense...
Related
A 'Team Highly Medicated' Release:
Hello everyone,
As highly anticipated, here is my port of dumfuq's overclocking patches ported to 2.6.35.10.
If you test it and Android either doesn't boot or is very slow, then you are experiencing an incompatibility that cannot and will not be fixed. Please note, I do not know if this kernel is compatible with Android versions below Gingerbread (2.3) because the Interprocess Communication (IPC) agent version differs.
http://www.multiupload.com/CNKQEWXIUH
Notice (added 7/20/2011): It has been made apparent by users and myself that as your battery gets lower, the slower your phone will become despite it showing it is overclocked. This is most likely because 787MHz requires the max voltage and the phone is unable to maintain that voltage as the phone loses charge. While batteries are measured in mAH (milliamps), the voltage exerted from the battery progressively decreases with the loss of mAH. The reason it requires this voltage is because of FSB and CPU multipliers... it is otherwise impossible to obtain that clock-rate with lower voltages. I will investigate possible workarounds.
No need to disable perflock. Remember to use SetCPU to actually overclock! Interactive governor enabled by default - it's a beauty!
Version 3, UPDATE 6/22/2011 @ 8:18pm CST:
- dumfuq was very helpful and I have (hopefully) now fixed the instability issues present in version 2.
- Due to complications with how frequencies are stepped I am limiting the max frequency to 787MHz.
- Please note, this is a TEST version and I am seeking any feedback regarding stability.
Version 2, UPDATE 5/27/2011 @ 11:24pm CST:
- Fix wifi.
- Actually enable Interactive governor by default.
Like it? Click the "Thanks" button - or even better "Donate"!
Peace out.
Is this the kernel that was mentioned to be added to the Salsa Slide ROM?
Although I suppose that's more of a question for Ohgami.
Can I just use this with it anyways? Thanks nbetcher!
SefEXE said:
Is this the kernel that was mentioned to be added to the Salsa Slide ROM?
Although I suppose that's more of a question for Ohgami.
Can I just use this with it anyways? Thanks nbetcher!
Click to expand...
Click to collapse
Ohgami wanted to have me release it separately. So yes, you most certainly can use it with it anyways.
Thanks nbetcher
Sent from my T-Mobile myTouch 3G Slide using XDA App
Ah yes what we've been waiting for. I agree though this kernel is Damn snappy without oc. But I have to try it out right. I'm curious to know though, if you said this works with ext2/3/4, will darktremor a2sd work with this and salsa port?
Sent from my fingertips using Android.
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Wagedroid said:
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Click to expand...
Click to collapse
retry i was stuck for a little bit but it came around
EDIT: the kernel keeps freezing my phone on salsa rom
Force Close City. Running CM Nightly 76. Fixed permissions and I still get a bunch of FC popups.
Hi, great job!
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Thanks.
ogo2 said:
Hi, great job!
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Thanks.
Click to expand...
Click to collapse
From the O.P.
Apps2SD included: http://www.multiupload.com/9EVC6CL8FP (your ROM needs Apps2SD support though!)
Non-Apps2SD: http://www.multiupload.com/8N1JPBM4N0
(By "Apps2SD", I mean the old-school Ext2/3/4 separate partition on your SD card. Either of these zips support the crappy Froyo (or higher) "Move to SD" function.)
I removed Perflock from the kernel entirely, so no need to disable Perflock.
koolkidjay1321 said:
retry i was stuck for a little bit but it came around
EDIT: the kernel keeps freezing my phone on salsa rom
Click to expand...
Click to collapse
I'm sorry to hear it's freezing. It's most likely clocked too high. Please make sure to clock it down.
ogo2 said:
Just want to ask you what do you mean by "Apps2SD included"?
Is this meaning that you have included ext2,3,4 support directly in the kernel (not as module)?
Click to expand...
Click to collapse
No, it's been included by Kitchen via the init.rc. Kitchen batches the init.rc to add Apps2SD support.
Wagedroid said:
I got stuck on splash screen for 20 minutes. No luck. I did a clean install of salsa 2.0.1 and flashed this update. Could it be that I didn't let the Rom boot then flash the updated kernel?
Sent from my fingertips using Android.
Click to expand...
Click to collapse
Same here, using latest CM nightly.
this kernel freezes my legend
ogo2 said:
this kernel freezes my legend
Click to expand...
Click to collapse
Overclocking or at boot?... Try lowering your speed and don't set it to start at boot.
Sent from my fingertips using Android.
I have not set anything connected to overclocking.
The system just hangs on boot (after entering the pin code and before the sense is loaded).
ogo2 said:
I have not set anything connected to overclocking.
The system just hangs on boot (after entering the pin code and before the sense is loaded).
Click to expand...
Click to collapse
I don't know if the Legend has the same frequency/voltage/bus speeds as Latte, so I can't promise that this would work on another device like the Legend. I'm learning that although the Legend is similar to Latte, they do have some very different parts.
nbetcher said:
I don't know if the Legend has the same frequency/voltage/bus speeds as Latte, so I can't promise that this would work on another device like the Legend. I'm learning that although the Legend is similar to Latte, they do have some very different parts.
Click to expand...
Click to collapse
They are both based on the MSM7227 SoC, so there shouldn't be any dramatical difference between them.
i had to load the rom before loading the kernel
koolkidjay1321 said:
i had to load the rom before loading the kernel
Click to expand...
Click to collapse
Tried this, thank cwm for backups. Fail, stuck on splash.
Sent from my fingertips using Android.
I'm using Franco's Kernel v15 + ZRAM with Mik's CM7 6.5.2. At first it was a dream, 1352 points on quadrant and 58.5fps on neocore @480/729Mhz Smartass. Everything running smooth and really fast.
About 6 hours of intense testing some apps (many, in fact) started crashing for no reason. Mostly google apps like Calendar and even Market. But also some widgets and running services.
I reflashed everything, even re-formatted (and re-partitioned) my sdcard and everything was fine again but after a reboot to install google applications (gapps-gb-20110325-signed.zip) the crashes started again. And I was running w/o overclocking at this time.
Searching for some info on the issue I saw a post stating that v15 kernel is for FROYO only so it's not compatible with CM7 but Franco always said that his Kernel was compatible with CM7 and there's no such info coming from Franco himself so I want to be sure of it before flashing a Froyo ROM.
Any thoughts on this issue? Any help is appreciated.
Edit:
Maybe it's worth noting that my phone is a O1 p500h, apart from the 3.2mp camera I don't really know if there's other differences in hardware that may cause problems.
That h is ur problem I think
I really hope not. I've been using Franco Kernel + CM7 for many versions and never had any problems with it (well, aside CM7's known bugs).
I'm from Brazil and CM7 is the only ROM I know that has Brazilian Portuguese (pt-BR) language support. All other ROMs I tried are strictly european and only have support for Portugal's Portuguese (pt-PT), which is kinda different and "sounds" quite annoying at some times.
And while I feel quite confortable using english, it's not the same thing as your mother tongue.
Its weird some users reported this kind of stuff.
I think its safer to use dookmatt kernel than franco kernel
Could a theme cause this kind of instability? I just remembered that on both times the crashes started I was experimenting with a XperiaArc theme for CM7.
Are you using app2sd or data2sd? These may cause such conflicts at time.
Vip_blast said:
Are you using app2sd or data2sd? These may cause such conflicts at time.
Click to expand...
Click to collapse
Nope, but I have an Ext4 partition on my SD-Card so I get more "internal" memory for installing apps.
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
doktornotor said:
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
The answer remains "no", I'm not using app2sd nor data2sd.
You missed the point. Whatever are you using for this can cause the instability. Apparently top secret stuff, so... go help yourself I guess.
Sent from my LG-P500 using XDA App
I am facing certain problems like you after flashing devoid.franco+kernel V15+ ZRAM.
I had following issues for the past 15 days.
1. changed the stock ROM to devoid Franco + V14
I agree the performance of the phone increased. Did OC using Set CPU. Score over the Quadrant was never over 650, not an issue with this as long as i can feel the diff in the performance.
One major change i saw was - as you all know the SMSes get threaded with a particular contact (both recd and sent msgs.). In my case if i receive sms from TD-I-mint, the message was shown as received from TD-Reylon, similar with all the SMSes, the actual sender was never possible to know when you see the list of msgs. Only after you open the msgs then you could find out the sender.
this is continuing still with Kernel 15.
2. same situation after flashing V14.1, V14.2, V14.2.2.
3. with Kernel V 15 + devoid.francoROM with little change. I wiped everything, SD was partitioned and upgraded to EXT 4. Flashed new ROM (05-06-2011), rebooted, flashed Kernel V15, rebooted, flashed ZRAM, rebooted, but phone never came to life, had to remove the battery and reboot, same result. Then wiped cache and dev cache, then flashed ZRAM, the phone was breathing.
Then tried to flash the system apps downloaded from first post of http://forum.xda-developers.com/showthread.php?t=1049518&page=1, the phone lost its life and had to re-do the whole process of flashing ROM....
With update of ROM + Kernel V15, i had to re-do the whole process for 5-6 times. I never had this problem with older kernels or flashing custom ROM.
One major issue is - msgs and other apps like TB (list of backups) some times display vertically. Today for the first time the SMS app was force closed.
Any-body facing issues like this or issues and you have the solution , I request you to post here.
I guess the best solution for me is to use the stock ROM with franco.kernel. This way I maintain my country's language (and, most important, GPS configuration) and still get some nice tweaks from Franco's.
By reading the comments on v15 kernel, it seems wise to wait for a new version before installing it. There are several users experiencing heavy battery drain. Or maybe install v14.2, but I don't have it anymore.
So, is it safe to use franco.kernel v14-v15 with LG stock ROM (mine came with v10A, android 2.2.1)? Or does it have any compatibility issues?
Thanks for your replies.
touch fix
hi, Does this kernel has the touch fix like Mik_os' kernel?
cas0404 said:
hi, Does this kernel has the touch fix like Mik_os' kernel?
Click to expand...
Click to collapse
Yes it does. Am running stock 2.2.2 with Franco's kernel v15 and its smooth as butter.
Running 2.2.1 stock ROM + franco.kernel v15 for about 10 hours now, so far no significant change on battery use.
But I miss mik's ROM performance... FPS on neocore dropped from 57fps to 36.5fps. And my old score on quadrant was 1350 and now is 615.
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
drakull said:
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
Click to expand...
Click to collapse
Wait for 2.3 to be released.
Well currently I'm using MiniCm7 pro V21 rom and using stock kernel.
I go to setting>CM settings>Performance>CPU setting and ticked OverClock.
Whenever I try to overclock my phone over 600mhz,for example: I set the phone to overclock to 652mhz, return to home, and then I go to setting again, it revert back to 600mhz itself
Why is that? Is it because I'm using stock kernel?
Can't overclock in MiniCm7 v20 pro rom
I have the same problem, when i choose more than 600mhz, then it will ben chosen automaticly 600mhz, could anyone help us ?
i'm using cm7 v20
I had the same problem, I don't remember what I did but you can try maybe installing SetCPU? Or you can go bottom on Settings>...>CPU Settings and tick "Set on Boot", then turning off the decive just after that.
Just an advice, don't OC it to 748+, just leave it at 748. Why? Because, if more than that, my phone gets unstable and it reboots after a few minutes. Just happens to me, I don't know about others.
nico444164 said:
I had the same problem, I don't remember what I did but you can try maybe installing SetCPU? Or you can go bottom on Settings>...>CPU Settings and tick "Set on Boot", then turning off the decive just after that.
Just an advice, don't OC it to 748+, just leave it at 748. Why? Because, if more than that, my phone gets unstable and it reboots after a few minutes. Just happens to me, I don't know about others.
Click to expand...
Click to collapse
Thanks for your method, but both of it doesn't work. So.... any other ideas?
Jericho4869 said:
Well currently I'm using MiniCm7 pro V21 rom and using stock kernel.
I go to setting>CM settings>Performance>CPU setting and ticked OverClock.
Whenever I try to overclock my phone over 600mhz,for example: I set the phone to overclock to 652mhz, return to home, and then I go to setting again, it revert back to 600mhz itself
Why is that? Is it because I'm using stock kernel?
Click to expand...
Click to collapse
Hi, Jericho4869
I tried many custom roms. almost all version of MiniCM7pro too.
And I'm not sure about which version, but early versions of MiniCM7pro was I can over clocked.
But I can't over clock on after v15 of MiniCM7pro.
What's the differences between the both ?
So I got some idea, it's a modules, specifically differences of x8oc.ko and x10minioc.ko I think...
>x8oc.ko is a can over clock without problems but if not set over clock to make device to slow down and lag coming up.
(So when I was not use over clock, I did delete or rename x8oc.ko fot the save performances of device)
>x10minioc.ko is a difficult to over clock on some device but if not use over clock but no adverse effects to processing speed.
It's can not o.c setting to enable or over 710 mhz to get unstable or shutdown or freeze and restart, it has many cases on my U20i
Anyway, I can't over clock over 710 mhz on MiniCM7pro v21 and MiniCM'9'Pro v1.2 (based on MiniCM7pro v21) both too, because the both use x10minioc.ko for over clocking.
My opinion is: If you want to try over clocking, you should to be choose another roms with custom kernels !!
However now I'm using ZombiePanic kernel and I choosing custom roms conditional on it's supported custom kernels. Because no problems for testing o.c.
IMPORTANT NOTES: (I know, maybe you already to know)
If you want to try to over clock, please you don't try on main device !!
If in case of under 710 mhz but it is get a alot of load on cpu of your device.
keep on over clock in long time is a serious risk of failure to your device !!
its not possible to overclock in minicm7pro. u can if u flash simple kernel. it has inbuilt oc modules. so try it!
i am trying for some time now to find a thread or post to help me overclock my mini at about 748 mhz . tha result : i found nothing..
please if someone knows how to do that help me..
i am using the latest minicm7 2.1.6 for mini and latest E10_nAa-08_2.6.29.6-nAa-08
kernel..
What exactly is your problem?
first thanx for replying
then.. what you cannot understand??
i said that i would like to overclock my x10 mini (E10i)
up to 748 mhz and if its not possible (i think it is)
i would like at least to OC it at 729 mhz..
now.. when i try to OC it , it freezes !!
(every time and if the OC is at 729 mhz or more..)
the most i have achieved is 691 mhz
edit:
also i saw your video and you had 729 mhz
the first time you tried putting cyanogenmod at 729 mhz
didnt it freeze?
salvinluckys said:
first thanx for replying
then.. what you cannot understand??
i said that i would like to overclock my x10 mini (E10i)
up to 748 mhz and if its not possible (i think it is)
i would like at least to OC it at 729 mhz..
now.. when i try to OC it , it freezes !!
(every time and if the OC is at 729 mhz or more..)
the most i have achieved is 691 mhz
Click to expand...
Click to collapse
this is what I did to my u20i.
go to cwm. do full wipe.
using nAa + cm7 you can:
OC= interactiveX gov + 768+
OC= ondemand gov +748
minimum OC should be 200+ to run smooth.
You can try these three variants of solving problem.
1.Reflash the rom, wiping battery stats, dalvik cache and factory reset.
2.Before setting maximum cpu, set minimal cpu up to 480 Mhz. Also uncheck Undervolt and set Perfomance mode.
3.Install another rom (not the good opinion ^_^)
Hope it helps.
P.S. My phone is now running 806 Mhz =), that means, that you had a mistake while installing firmware
Mrakoris/ said:
You can try these three variants of solving problem.
1.Reflash the rom, wiping battery stats, dalvik cache and factory reset.
2.Before setting maximum cpu, set minimal cpu up to 480 Mhz. Also uncheck Undervolt and set Perfomance mode.
3.Install another rom (not the good opinion ^_^)
Hope it helps.
P.S. My phone is now running 806 Mhz =), that means, that you had a mistake while installing firmware
Click to expand...
Click to collapse
is it running smoothly at 806? how did you do it? can you share your settings?
Mrakoris/ said:
You can try these three variants of solving problem.
1.Reflash the rom, wiping battery stats, dalvik cache and factory reset.
2.Before setting maximum cpu, set minimal cpu up to 480 Mhz. Also uncheck Undervolt and set Perfomance mode.
3.Install another rom (not the good opinion ^_^)
Hope it helps.
P.S. My phone is now running 806 Mhz =), that means, that you had a mistake while installing firmware
Click to expand...
Click to collapse
Ok... i have tried all these except for the last (third) option..
Unfortunately i didnt achive to make it work..
Do you think the problem is that i have flashed naa - 08 kernel instead of the naa -07
that it says it requires??
Also i ve thought about overvolting..
if you have any idea post..plzzz
again i thank all of u for the help you provide!!
EDIT:
I was playing around with higher freqs and when i tested 806 mhz
It froze instantly and the red led light came up..
I think this is a clue..
When red flashlight comes- that means your phone will reboot now, because it is freezed. It is normal. Try to install another rom, maybe your currently running firmware is not fully compatible with your phone, because it is custom :/
Hope It Helps.
Mrakoris/ said:
When red flashlight comes- that means your phone will reboot now, because it is freezed. It is normal. Try to install another rom, maybe your currently running firmware is not fully compatible with your phone, because it is custom :/
Hope It Helps.
Click to expand...
Click to collapse
Firstly, my phones red led comes up only when using 806 mhz.
With any other frequency it just freezes and reboot..
i have also noticed that when i apply 729 mhz
it doesnt freeze instantly even if i am using performance governor but only when i do something (ex. Press the home button or back button )..
shall i ask something?
Will this happen to all minicm future releases??
Hi all, sorry to interrupt but i have u20i and my cpu is only stable upto 729mhz. i think it is not the kernel and the rom but the chip and processor they have added in the phone. it is a hardware matter.
so guys, whatever rom you install it is the same result. no change.
i have installed numerous roms and i have the same oc 729mhz max. not more than that.
so stop fighting with how to get it to 800+mhz.
Thanks!
Tommylee567 said:
Hi all, sorry to interrupt but i have u20i and my cpu is only stable upto 729mhz. i think it is not the kernel and the rom but the chip and processor they have added in the phone. it is a hardware matter.
so guys, whatever rom you install it is the same result. no change.
i have installed numerous roms and i have the same oc 729mhz max. not more than that.
so stop fighting with how to get it to 800+mhz.
Thanks!
Click to expand...
Click to collapse
Are you trying to tell me that it will never work at such speeds (Over 691) ???
Thats a pity for such a good smartphone
yEAH he is right. its all about the chip you have some processor can go upto 800 Mhz and some remain only on lower frequencies even i remain on 691Mhz. We cant do nothing about it
@salvinluckys,
Yes, if you want a 800mhz phone then you have to have a luck to get one like you want.
It is hardware matter. you might consider looking at the scores after you do benchmarking, you will find some 800+ mhz doing just little near or above 2000 score. it doesnt matter if you have the highest score, all matters if your phone is capable to do whatever you need to do. that is what i am looking at.
Good day!
EDIT: Even people with the same frequency have 1800 (something) score. Dont feel bad about your phone. It is a good phone. and we are lucky to have awesome devs giving roms for us.
Thanks to all of you for helping me understand that its a hardware incapability..
Last question..
will this persist even if i overvolt and then OC my device?
(I dont know the way yet .. if you want to help me)
salvinluckys said:
overvolt and then OC
Click to expand...
Click to collapse
???
How is that?
Better you get a PC and try that. it is better so you will forget to do it for your phone
NEWS
Guys.. i have some news !!!
with the latest update of minicm 2.1.9 ( naa 11 kernel )
on 729 mhz my device is partially stable.. i will reboot either with hard use or
after a day or so..
NOW the big part..
while i was playing around with benchmarking ( antutu ) at 729 mhz i saw that the device was freezing only during the read or write test of my SD card which is 8 gb
and splitted in 3 partitions [ fat32 , ext4 ( or ext3 i dont remember ), swap ].
what do you believe??
is there a chance that the problem with overclocking has to do with the SD card??
(748 mhz still reboots after a few clicks on the screen depending on the governor)
salvinluckys said:
Guys.. i have some news !!!
with the latest update of minicm 2.1.9 ( naa 11 kernel )
on 729 mhz my device is partially stable.. i will reboot either with hard use or
after a day or so..
NOW the big part..
while i was playing around with benchmarking ( antutu ) at 729 mhz i saw that the device was freezing only during the read or write test of my SD card which is 8 gb
and splitted in 3 partitions [ fat32 , ext4 ( or ext3 i dont remember ), swap ].
what do you believe??
is there a chance that the problem with overclocking has to do with the SD card??
(748 mhz still reboots after a few clicks on the screen depending on the governor)
Click to expand...
Click to collapse
sorry but i really think it has nothing to do with sd card but a hardware limitation as u were told before... im in ur same situation... my x10mini cant oc over 691... its as simple as some phones can, others not, maybe depending on the date it was made... but dont worry!! ive been using it with 691 since last update and runs btilliant
I can go up to 825mhz without problem i have an x10 mini (E10i) with minicm7 2.1.9 and nAa's 11 kernel, thank you very much
I could oc it to 787 mhz,it is mostly stable.
Each device is different, not every device is capable of overclocking above 691. The most stable all over those devices is 691. No more! I am stable ta 748 with nAa.
I have Galaxy 5.0 player (US version) running Eryigit-GB-2.3.6 ROM on it from last 6 months, While everything worked great during that time, i want to try one of the newer ROMs now, may be ICS if all the bugs have been fixed. Can anybody help me where to start now, I used Odin before, I have no idea about Heimdall..Can i still use Odin? also can anyone recommend me what ROM i should go for ? and what should be the correct steps to flash it again? do i need to backup the current ROM?
thanks in advance.
ministerjee said:
I have Galaxy 5.0 player (US version) running Eryigit-GB-2.3.6 ROM on it from last 6 months, While everything worked great during that time, i want to try one of the newer ROMs now, may be ICS if all the bugs have been fixed. Can anybody help me where to start now, I used Odin before, I have no idea about Heimdall..Can i still use Odin? also can anyone recommend me what ROM i should go for ? and what should be the correct steps to flash it again? do i need to backup the current ROM?
thanks in advance.
Click to expand...
Click to collapse
I'm in the same position as you. I know how to use CWM (I think), at least it worked for me before.
I would like to try out JackpotClavin's apparently awesome :good: new Kernel.
Should I wait for the PAC-Man version of iurnait or just flash jackpot's rom?
Lots of bugs are still being reported, so I'm wondering if it's already running stable enough for daily use.
And do I need to make a clean install if I install Jackpot's ROM now and later on want to switch to PAC-Man?
Thanks in advance!
I've been keeping with the Jellybean releases as they come, and would say it's definitely good enough for daily use. The only thing that doesn't work yet on 4.2.2 is taking pictures with the rear camera.
The speed and fluidity of the UI is definitely worth checking out and a lot of apps use the new framework. Overall, it just feels like a much more polished and intuitive experience.
If you are going from gingerbread to jellybean you have to wipe or you'll get some serious issues. coming from ice cream sandwich or 4.1 jellybean, you should be fine with just wiping /cache, /system, and the dalvik cache. coming from any other 4.2 rom, you're perfectly fine.
halomademeapc said:
I've been keeping with the Jellybean releases as they come, and would say it's definitely good enough for daily use. The only thing that doesn't work yet on 4.2.2 is taking pictures with the rear camera.
The speed and fluidity of the UI is definitely worth checking out and a lot of apps use the new framework. Overall, it just feels like a much more polished and intuitive experience.
If you are going from gingerbread to jellybean you have to wipe or you'll get some serious issues. coming from ice cream sandwich or 4.1 jellybean, you should be fine with just wiping /cache, /system, and the dalvik cache. coming from any other 4.2 rom, you're perfectly fine.
Click to expand...
Click to collapse
Okay, thanks. That sounds good.
Tomorrow I will probably try and flash Jackpot's Rom then.
As I am coming from Eryigit-GB-2.3.6 ROM I will have to do a full wipe first and then I am good to go flashing from CWM? Or do I have to install another Kernel first, and/or format everything?
Thanks for your help!
my problem is i do not have CWM installed. If i remember correctly i used SuperoneClick to root and Odin to put Gingerbread ROM with Entrophy512's Kernel.
Do i need to install CWM before i try another rom?
Looks like we still do not have any ICS/JB ROM with all bugs fixed????
ministerjee said:
my problem is i do not have CWM installed. If i remember correctly i used SuperoneClick to root and Odin to put Gingerbread ROM with Entrophy512's Kernel.
Do i need to install CWM before i try another rom?
Looks like we still do not have any ICS/JB ROM with all bugs fixed????
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1445840
It states here, that Entropy's kernel does in fact come with CWM. And if you're on the same version of Erygit's Rom as I am (3.5), then you should have an application called RebootMenu, where you can choose to reboot directly into recovery.
Weird
Okay now, I managed to flash it, wasn't as easy as I thought, though Lots of assert failed errors, google apps not installing, etc. but now everything is working fine!
i do have rebootmenu and i can reboot into CWM.i want to try Chips ROM.i think its very stable like my current one Eryigit
do i do this after copying rom on SD card???
Backup Existing ROM
Wipe Data and Cache
install from zip
reboot
ministerjee said:
i do have rebootmenu and i can reboot into CWM.i want to try Chips ROM.i think its very stable like my current one Eryigit
do i do this after copying rom on SD card???
Backup Existing ROM
Wipe Data and Cache
install from zip
reboot
Click to expand...
Click to collapse
Yes that will work great.
thanks
one last question
how is the battery life on Chips ROM, is it same as Eryigit. ???????
On Eryigit it pretty good, (just doesnot go over 80 fully charged)
How to install jelly bean coming from stock gingerbread ?
halomademeapc said:
I've been keeping with the Jellybean releases as they come, and would say it's definitely good enough for daily use. The only thing that doesn't work yet on 4.2.2 is taking pictures with the rear camera.
The speed and fluidity of the UI is definitely worth checking out and a lot of apps use the new framework. Overall, it just feels like a much more polished and intuitive experience.
If you are going from gingerbread to jellybean you have to wipe or you'll get some serious issues. coming from ice cream sandwich or 4.1 jellybean, you should be fine with just wiping /cache, /system, and the dalvik cache. coming from any other 4.2 rom, you're perfectly fine.
Click to expand...
Click to collapse
I have stock gingerbread on my player and flashed CWM v5.0.2.7 and I want install the PAC MAN ROM 4.2.2. The install instructions say to wipe data, dalvik, system and dbdata. But I can't find anything that says dbdata on my player the closes one I found was format /datadata. What exactly do i need to do so i can install this ROM on to my player and get it working ? I'm a noob to flashing roms
Ki6465 said:
I have stock gingerbread on my player and flashed CWM v5.0.2.7 and I want install the PAC MAN ROM 4.2.2. The install instructions say to wipe data, dalvik, system and dbdata. But I can't find anything that says dbdata on my player the closes one I found was format /datadata. What exactly do i need to do so i can install this ROM on to my player and get it working ? I'm a noob to flashing roms
Click to expand...
Click to collapse
yea, its named /datadata in older versions of CWM, so wipe that
iurnait said:
yea, its named /datadata in older versions of CWM, so wipe that
Click to expand...
Click to collapse
Thank you , I installed the ROM and it worked. :good:
Ki6465 said:
Thank you , I installed the ROM and it worked. :good:
Click to expand...
Click to collapse
Should also try mercuis new kernel or sultan kernel with it!
Sent from my YP-G70 using xda premium
lazepr said:
Should also try mercuis new kernel or sultan kernel with it!
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
I have the sultan kernel installed and its good though i don't overclock beyond 1.2 if i do i start to get force closes in apps. I haven't tried mercuis new kernel. Is there a kernal to get better battery life ?
we have both lowered in our kernels lcd screen voltage which greatly improves batterylife You can also lower cpu voltages but if your device turns off while overcloking that means your chip has poor quality
Wysyłane z mojego Nexus S za pomocą Tapatalk 2
kernel
Well I'm looking for a kernel that has the 100 MHz and 200 MHz range included since all I pretty much do is listen to music. When I had stock rom, kernel, everything I had amazing battery life on both music playback and standby time. I just installed the the sultan kernel r4 and the lowest CPU speed is 400mhz. Wish the lowest speed was 100 MHz speed. is ever going to be at 100 MHz or at least 200mhz ?
Voltage difference is slight between 200mhz and 400mhz and 100mhz has equal to 200mhz 100 is totally useless unless you don't undervolt
Wysyłane z mojego Nexus S za pomocą Tapatalk 2
Ki6465 said:
Well I'm looking for a kernel that has the 100 MHz and 200 MHz range included since all I pretty much do is listen to music. When I had stock rom, kernel, everything I had amazing battery life on both music playback and standby time. I just installed the the sultan kernel r4 and the lowest CPU speed is 400mhz. Wish the lowest speed was 100 MHz speed. is ever going to be at 100 MHz or at least 200mhz ?
Click to expand...
Click to collapse
100MHz and 200MHz were causing SODs so as a dirty fix KOala and I removed them from our kernels. However, the SODs might be fixed now so I'm going to test 100MHz and 200MHz again today
Also, 100MHz and 200MHz are pretty useless because they're too weak to do anything. When the screen is off the player sets the CPU to 800MHz so having 200MHz and 100MHz won't get you better battery life if you're listening to music while the screen is off.
Sent from my HTC Sensation using xda app-developers app
android1234567 said:
100MHz and 200MHz were causing SODs so as a dirty fix KOala and I removed them from our kernels. However, the SODs might be fixed now so I'm going to test 100MHz and 200MHz again today
Also, 100MHz and 200MHz are pretty useless because they're too weak to do anything. When the screen is off the player sets the CPU to 800MHz so having 200MHz and 100MHz won't get you better battery life if you're listening to music while the screen is off.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Well hopefully they work. :fingers-crossed: