This kernel is totally stock with the overclock tweak.
Download xDKernel - boot.img http://dl.dropbox.com/u/13729847/boot.img
WiFi Module - modules.zip http://dl.dropbox.com/u/13729847/modules.zip
[v2]Added ClockworkMod Recovery from DooMLord's sources.
[v1]Changed version string to _xD
[v1]Added 2GHz CPU Overclock
Why did I make this kernel?
Because when I was on DooMLord's kernel, battery drain was worse than usual, and I didn't really like the splash screen much either, all I wanted was stock with overclock.
Will CPU governors be added? Maybe - depending on battery drain, if I add something, and it drains the battery, I will have to remove it.
To apply, first you need to use fastboot to flash the boot.img:
To flash the kernel execute the command:
Code:
fastboot flash boot boot.img
Then unplug your phone, boot into recovery, to do this turn on your phone and when the blue LED on the power switch lights up keep pressing the back button.
After this, flash the WiFi module (you need to have it on SDCard first), install zip from sdcard then select modules.zip
hey man this is aweosme ive been waiting for somein like dis ur d man i installed it all works fine now to test it i ddn tuse doomlord cos of the battery drain
Hi!
Aside from the bootscreen,
1. How is this any different from DooM's Kernel with regards to battery issues you were referring to?
2. Is there any other tweak that DooM does to his kernel to support your claim for battery drains?
3. What tweak did you do for you to have a separate Wifi Module to be flashed?
4. Is the CWM source you got the latest one? Does the sd-ext mounting applies too?
thanks and regards!
faisaldante said:
hey man this is aweosme ive been waiting for somein like dis ur d man i installed it all works fine now to test it i ddn tuse doomlord cos of the battery drain
Click to expand...
Click to collapse
Thanks, if you like it, click the thanks button.
Sent from my R800i using Tapatalk
Can you release doom kernel with stock logo?
Swyped from my Xperia Play via Tapatalk
Is this for 2.2.3 or 2.2.4?
Sent from my R800i using Tapatalk
Just installed on 2.3.4 gingerbread running nicely do a full test later..
Sent from my R800i using XDA App
noojster said:
Hi!
Aside from the bootscreen,
1. How is this any different from DooM's Kernel with regards to battery issues you were referring to?
2. Is there any other tweak that DooM does to his kernel to support your claim for battery drains?
3. What tweak did you do for you to have a separate Wifi Module to be flashed?
4. Is the CWM source you got the latest one? Does the sd-ext mounting applies too?
thanks and regards!
Click to expand...
Click to collapse
1. In doom's kernel he has added things such as tiny RCU, I have added none of this.
2. Sort of answered your question in 1
3. Changing kernel string name requires flashing new WiFi modules.
4. I use Doom's latest recovery.
This is based on stock .42 sources so is for 2.3.4
Sent from my R800i using Tapatalk
The battery drain aint perfect over night 11 hours it went down 22 percent but its not as bad as doomlords though i have to say
faisaldante said:
The battery drain aint perfect over night 11 hours it went down 22 percent but its not as bad as doomlords though i have to say
Click to expand...
Click to collapse
Try changing Min CPU speed to the lowest setting, this is what I have done and battery seems okay.
I used to get 2% gone every five minutes on my HTC Wildfire, so 2% decrease each hour is okay and seems reasonable to me.
i aint complaining im allright with this mate just saying but im curious to why my last precent was 2 hours long hmmm
q?
hello! I'd like to try this but I need to know if it will mess up my link2sd setup (1.2 gig ext3 hidden partition mounted (linked) as internal storage).
I don't want to lose half of my installed programs....
thanks.
alex.mircea0509 said:
hello! I'd like to try this but I need to know if it will mess up my link2sd setup (1.2 gig ext3 hidden partition mounted (linked) as internal storage).
I don't want to lose half of my installed programs....
thanks.
Click to expand...
Click to collapse
It shouldn't mess it up at all.
KeiranFTW said:
It shouldn't mess it up at all.
Click to expand...
Click to collapse
are you sure? if this is stock kernel and only doomlords kernel has support for ext 2/3/4 then this will prevent ext? or this for the internal memory?
UPDATE: EXT not working on this kernel and therefore i cant use it
according to link2sd no init script could be created and therefore the apps2ext script can not be added to startup
hello!
just flashed it and everything works ok...
2GHz works as well on my rig, but I nailed it @1.9 (I guess I want my hardware to last longer... )
I will come back with my feedback
Link2sd works and all my programs are right there. @fma965 before I flashed I had an ext3 part linked on stock kernel, not on doom, and worked fine... doomskernel draines my battery for no reason (with no overclock, just installed) and that's why I stuck on stock until 2nite. I guess play's kernel natively knows how to mount ext FS
ps: lov that you kept the original boot screen
thx
alex.mircea0509 said:
hello!
just flashed it and everything works ok...
2GHz works as well on my rig, but I nailed it @1.9 (I guess I want my hardware to last longer... )
I will come back with my feedback
Link2sd works and all my programs are right there. @fma965 before I flashed I had an ext3 part linked on stock kernel, not on doom, and worked fine... doomskernel draines my battery for no reason (with no overclock, just installed) and that's why I stuck on stock until 2nite. I guess play's kernel natively knows how to mount ext FS
ps: lov that you kept the original boot screen
thx
Click to expand...
Click to collapse
SO WHY wasn't link2sd working for me? it error'd i am using ext4 though so ....
please fix - although i am now on .58 kernel (recently released in hongkong and on wotanserver) so this wont work for me now anyway
dunno mate.. I'm still on .42 - the one with lots of chineeese **** at start (but not anymore)
link2sd worked from market with no tricks... and it is free.. did my partitions with paragon.. i don't use anything else.. (app2sd hack or smth... no; just link2sd).
only once it failed to mount on a reboot... but then worked everysingle time...
I couldn't find any .58 for flashtool (to keep my data)... but that's already out of topic..
now enjoying videos that got out of sync before. thanks faisaldante !
if baterry will also be ok, I'll be so much gratefull.... will come back to tell
alex.mircea0509 said:
dunno mate.. I'm still on .42 - the one with lots of chineeese **** at start (but not anymore)
link2sd worked from market with no tricks... and it is free.. did my partitions with paragon.. i don't use anything else.. (app2sd hack or smth... no; just link2sd).
only once it failed to mount on a reboot... but then worked everysingle time...
I couldn't find any .58 for flashtool (to keep my data)... but that's already out of topic..
now enjoying videos that got out of sync before. thanks faisaldante !
if baterry will also be ok, I'll be so much gratefull.... will come back to tell
Click to expand...
Click to collapse
lol no problem mate i wanted a good firmware im trying .58 now with wutan server lets see hwo it goes trust me mate the xperia play the best phone ever
Going to add some CPU governors tomorrow as well as updating the interactive one.
Going to set the minimum clock speed lower for battery and performance.
Sent from my R800i using Tapatalk
mounting sd-ext at CWM didnt work for me,
it says error getting script in Link2Sd just like fma965's problem
was worth a try..
reverting to my original setup on my signature
Related
First off - I must acknowledge that that code this came from, is not mine. All credit goes to Geniusdog254, fat-tire, mbm (irc advice), and those who have committed to their branches; i would like to eventually make my own branch, but for now, this is a great start. Hopefully this is ok with them - if not, i will happily take it down.
UPDATE AT YOUR OWN RISK.
So, for all those lucky 2.1 users, you have have a nice overclocked kernel. Well, today lucky 2.2 users get the same enjoyment! Just as a teaser - Quadrant gives a score of 1618
0.2:
950Mhz: http://www.mediafire.com/?mbfnt3i39cz8q9o
900Mhz: http://www.mediafire.com/?opmajiyx1puf11t or http://www.megaupload.com/?d=AQKPIPHR
Changes:
***ROTATION IS FIXED***
Original Kernel base proved unstable for the Froyo build. So, went back to basics, and modified the original Nookie Froyo Kernel, as found here: https://github.com/fat-tire/nook_kernel
Future code will be branched from this for the time being.
Built two different kernel speeds, for those whose systems dont like 950.
0.1:
http://www.mediafire.com/?aoadpgt2foxhby9
Compiled from https://github.com/fat-tire/Quickie, as of 1/18/11.
Kernel defaults to 950Mhz
Kernel made compatible to 2.2 standards, with other minor fixes (as noted in Github
To Install:
[Pre Install]
Wipe Dalvik Cache
As suggested here: http://forum.xda-developers.com/showpost.php?p=10749287&postcount=12, it is best to wipe the dalvik cache (if this is not the first boot of the system,). To do so (after connecting your nook to a PC):
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
This can also be done in root explorer.
[Install]
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
[Tested on]
I have tested this Kernel on both a fresh copy of .5.8, as well as the custom .5.9 as posted here: http://forum.xda-developers.com/showthread.php?t=922324
[Recomendations]
Get SetCPU (from this friendly forum!), and change the governor to on-demand. It is currently defaulted to conservative for battery, but OD should give better performance.
Future & Reserved:
Ideally, i would like to build on this kernel, and add features other kernels have, such as different governors, BFS, and HAVS. I don't know much I can actually do, but as time goes I am sure i will learn more. Please be patient with me, and remember this is a WIP. While i am not new to coding, I am new this kind of kernel work, so I am still picking up things here and there..
Issues -
Quadrant is stupidly picky. I am not sure what i did to get it to run when I did, but the best i can say s to keep trying. Right now, it seems to really hang at 2/4 on the I/O.
I believe the default governor is set to conservative; i recommend downloading SetCPU and setting it to ondemand.
Woot Saw the IRC work and couldnt wait.
And i was going to say the wait at 2/4 on I/O was like that before
1607 Quadrant score
Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.
kassemja said:
Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.
Click to expand...
Click to collapse
Just boot a copy of nookie froyo from a mircosd and mount the /data partition from the emmc to delete the davlik cache. That's how I was making changes to nookie froyo when I was running it off the emmc. Once hardware decoding for media is supported I will put NF back on the emmc. Can't wait till clockwork supports froyo. I will be all over this!
Nook [email protected]+Nookie=Awesome
Not working on my Froyo'ed Nook
Divine_Madcat said:
To Install:
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
Click to expand...
Click to collapse
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA
xyzolog said:
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA
Click to expand...
Click to collapse
Same thing happening here.
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
I have used the 950 kernel on 2.1 for about a week no issues. I'm happy to test again with a davlik cache wipe. On the way to work now. So hopefully you can post new build by then.
Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk
Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Yes. 950 Mhz ran fine for me. The 1Ghz though did not.
I didn't do a Dalvik cache wipe first. When i get a chance I'll try that and give it another go.
deitiphobia said:
Same thing happening here.
Click to expand...
Click to collapse
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...
jasoraso said:
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...
Click to expand...
Click to collapse
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
Gave this a shot, hopefully this helps!
EDIT: first two reboots > boots fine!
watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
I can get it to boot every 4th or 5th time, but only into instability. It will crash shortly thereafter for one reason or another. Currently it's bootlooping, but NOT off the SD card and Nookie Froyo, it's bootlooping off of the internal memory and 2.1.
I think I'm going to give up on this for now till a more stable solution is reached.
My 2.1 is still running fine at 950Mhz though despite not being able to get this to work for Nookie Froyo.
FOr anyone interested - There are two new Kernels posted, based off different (more stable) code, with one built at 900Mhz, and the other at 950. Please test and use, i think you will find them more stable than the previous..
Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer
Homer_S_xda said:
Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer
Click to expand...
Click to collapse
Download from the server? Or working on the nook?
Divine_Madcat said:
Download from the server? Or working on the nook?
Click to expand...
Click to collapse
Cannot download it from the server. The 950 was fine, but I could not get the 900 zip from the server.
My NC/NF is rocking 950! Cleared the Dalvik cache via Root Explorer, powered off via QuickBoot, swapped the uImage (after backing up the NF 0.5.9 one and verifying that my backup worked) and powered on. Booted on the first go and it already seems snappier. In the About Phone the kernel now shows as
2.6.29-omap1
[email protected] #2
UPDATE: WOW just wow! Dolphin HD is actually usable now, it was really dragging before. When this gets stable from the internal memory it will be amazing.
Excellent!
Homer
Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!
Divine_Madcat said:
Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!
Click to expand...
Click to collapse
The alternate server worked fine. I dl'd the 900 version just in case. Will you be trying a 1GHz version?
Also, any chance you can figure out how to implement IPtables? I'm dying to get proxy for wifi working at least near to how it works on my iPod touch. I can't get over the fact that Google really doesn't seem to want to get into businesses with Android.
Homer
Hi all,
I have a mini pro/U20i running Eclair, specs as follows;
Firmware: 2.1-update1
Baseband: M76XX-TSNCJOLYM-53404006
Kernel: 2.6.29
Build no: 2.0.A.0.504
Rooted, xrecovery installed
I'm looking to upgrade to the latest stable android version available for my phone, but must admit the in-depth tech talk does go over my head a little when looking at the ROM threads. I have enough tech savvy to be able to flash etc, but not too great with the programming speak.
I'd like to ensure that bluetooth, wireless, root, gprs etc are all 100% working on the ROM I upgrade to. Not bothered about radio or anything you can get an alternative of from the market.
From what I've seen gingerbread is available but not yet 100% functional, and I know there are stable Froyo versions available however the requirements state the baseband as above, but ending in 53404015 is required.
Is there considerable risk flashing a ROM if my baseband is slightly different?
I'm particularly looking for stable multitouch too, but the thread I read says manual edit of .sh and .prop files must be done - and I don't know how to do this
Dev and user opinions would be muchly appreciated.
Hi you will need the newer baseband just update with seus then you will need to reroot and install xrecovery again then once you have done that go to this thread ( http://forum.xda-developers.com/showthread.php?t=1059361 ) its the most stable I think and dual touch is included so no messing around
Hope this helps you
Sent from my U20i using XDA App
just use the flasher and baseband files from the baseband thread. much faster and easier than using seus and rooting again. just put the rom you want on with xrec, pull the battery out, flash, and youre done! shouldnt take more than 10 minutes once you know what youre doing!
For me, using SEUS is safer, even if I have to root and install xRecovery again.
I you want the most stable ROM with all functions working, you have to choose CM6-MiniCM hybrid noOC from Slade.
I'm using that ROM since he released it and never had a reboot, and everything is working.
If you have stock rom, you should format SD card.
Temes
temes said:
For me, using SEUS is safer, even if I have to root and install xRecovery again.
I you want the most stable ROM with all functions working, you have to choose CM6-MiniCM hybrid noOC from Slade.
I'm using that ROM since he released it and never had a reboot, and everything is working.
If you have stock rom, you should format SD card.
Temes
Click to expand...
Click to collapse
yeah using SEUS is better... and you can reflash after you update using it....
after root and xrec, just make a backup on xrec so you can reflash to 2.1 back... and dont waste time on reflash+root+xrec again.... i did that save lots of time
ps: make sure full wipe+dalvic clear before restore backup... ^^
riesan said:
after root and xrec, just make a backup on xrec so you can reflash to 2.1 back... and dont waste time on reflash+root+xrec again.... i did that save lots of time
Click to expand...
Click to collapse
Yeah, I did it too, but never needed that backup I flashed with SEUS last, when I first updated to slade's ROM
Temes
Cyanogen Froyo CM6-Latest (based on MiniCM/CM6v2) - v2.0 + DualTouch is the most stable ROM for me. Just flash using SEUS or flasher to get the required baseband.
I recommend using the flasher because it helps you understand the flashing process. Just follow the tutorial.
Thanks for all your help guys, that's helped me out no end
I am now the proud owner of an x10mp android 2.2.1 (went with Slade's ROM - big thumbs up, it's beautiful!!)
I have one final question.. when I installed the last ROM I had, I used flashtool, so doing it with xrec was a new experience for me... I did notice that before it installed the rom, it said 'formatting /system' or words to this effect.
I need to install the two hotfixes that are posted with the rom - the drain and browser ones... do I package the files within these zips into an update.zip and run again from xrec or can I transfer the updated system files just using root explorer? I'm worried that xrec will take the update.zip as a full rom and will delete the contents of my system folder - please reassure me this isn't the case and it will just update with newer files!
MANY thanks again for your help and advice!
kao_u20i said:
Thanks for all your help guys, that's helped me out no end
I am now the proud owner of an x10mp android 2.2.1 (went with Slade's ROM - big thumbs up, it's beautiful!!)
I have one final question.. when I installed the last ROM I had, I used flashtool, so doing it with xrec was a new experience for me... I did notice that before it installed the rom, it said 'formatting /system' or words to this effect.
I need to install the two hotfixes that are posted with the rom - the drain and browser ones... do I package the files within these zips into an update.zip and run again from xrec or can I transfer the updated system files just using root explorer? I'm worried that xrec will take the update.zip as a full rom and will delete the contents of my system folder - please reassure me this isn't the case and it will just update with newer files!
MANY thanks again for your help and advice!
Click to expand...
Click to collapse
Just use each from xrec, it will replace some file but it won't format your system, only the big release file does that (100MB++).
hansip87 said:
Just use each from xrec, it will replace some file but it won't format your system, only the big release file does that (100MB++).
Click to expand...
Click to collapse
It depends what formatted, deleted or owerwrited on update script. Don't worry, slade knows what he's doing
Anyway DON'T TRY TO FORMAT YOUR SYSTEM WITHOUT INSTALLING NEW ROM!!!
Just always follow install notes and everything will be fine.
Temes
Right then, an update (excuse the pun!)
I followed SEUS to get the xx 4015 baseband
I flashed Slade's noOC rom and then hotfixes using xrecovery
I now have a happy 2.2.1 android mini pro with multitouch!
At first, it was a little slow and I had a few blank screens and FCs....
Screen brightness was very low even when I was actively using the phone, so I unchecked the auto display option and set a brightness I'm happy with. Sorted!
With Titanium I restored my backups, including my wifi connections. Saves having to re-enter all the passwords right? Wrong!
I had a number of connection issues. Data was very slow, to slow to even register my google account on market. Wifi wouldn't load market or bring up anything in the browser...
When I did establish a fast enough data connection, market was completely out of sync with my phone apps.
Turns out the data connection just needed to 'warm up' along with the new android system. As for the wifi, I removed all my connections with the 'forget' option, and manually scanned and entered the passwords again. Now my wifi flies
So all in all, a very smooth upgrade process, a couple of hiccups with the data/wifi and brightness that have been ironed out, and now I am loving my new android again. The multitouch is very slick and having superuser, jit and xrec preinstalled is just brilliant! Games are lag free too which makes a big difference (yep, I'm an Angry Bird club member)
Think I've made my iphone user hubby a bit jealous. I like to remind him every now and then that apple have him by the balls, and he has to buy a whole new phone to do any update such as the one I've just done (again )
The battery drains a little quicker than on the previous rom, but I expect that will settle down after a few days. One thing I have noticed is that I'm repeatedly ending apps with ATK that I hadn't even opened - on my last rom I'd never see anything that I hadn't opened myself.
An example being, just opened ATK and I have the following running;
APN OnOff
Gmail
Maps
None of these I've opened since I last ran ATK Other repeat offenders are Browser, google search and camera,
Any ideas? WhatsApp used to open randomly until I moved it to the SD card. It's behaving itself now.
Don't need to use taskkillers in 2.2.1, android handles battery quite efficiently.
Battery increase is due to overclocking and because it's a custom rom.
Hope that helps.
XDA ♥
My battery life has stabilised now. Took phone off charge about 8.30 am and now, 1.30pm it's at 83%, so can't complain
I find apps such as maps and google voice/search do drain the memory quite a bit so still prefer to use atk. Just opened atk to find I have;
maps
handcent
apn OnOff
gmail
google voice
ROM manager (I've never opened this since installing the rom)
calendar
camera
all running and memory at 41M. Killed apps and memory now at 71M
Is there a way to stop these apps from randomly running? Apart from a calendar alert for today, I haven't manually opened anything from the list
cheers,
K
Sorry for ignorance:
Can I flash a rom and do all the nec. stuff from Ubuntu? Or will I need Window$ to flash a mini pro?
kao_u20i said:
My battery life has stabilised now. Took phone off charge about 8.30 am and now, 1.30pm it's at 83%, so can't complain
I find apps such as maps and google voice/search do drain the memory quite a bit so still prefer to use atk. Just opened atk to find I have;
maps
handcent
apn OnOff
gmail
google voice
ROM manager (I've never opened this since installing the rom)
calendar
camera
all running and memory at 41M. Killed apps and memory now at 71M
Is there a way to stop these apps from randomly running? Apart from a calendar alert for today, I haven't manually opened anything from the list
cheers,
K
Click to expand...
Click to collapse
It's normal to have applications taking up memory. It is so that it will be speedy in opening those apps so try not to use a taskkiller. The only time these idle apps use battery is when there is CPU usage: so check with your spare parts. If they don't use CPU, no need to kill.
If you're insistent that the apps are frustratingly persistent, then freeze the app using titanium backup. Note that freezing certain system apps may cause problems eg freeze google talk and market won't work.
Try at your own risk.
XDA ♥
Can i get the link to ''CM6-MiniCM hybrid noOC'' Thanks
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
dvigue said:
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
There is a huge debate about this, but if you are not ready for a new Kernel, you can try an app call Autokiller Memory Optimizer and set it to the Optimum setting.
This will kill apps that are eating up your RAM and over time can slow your phone. This is one simple and quick solution.
This app adjust the memory killer that is already used by the phone. This just helps it to work more efficiently.
dvigue said:
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
Join the club; I just did the same thing
Has anyone seen John Connor?
moved
sageDieu said:
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my Fascinate was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Relaxasaurus said:
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my device was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Click to expand...
Click to collapse
oh trust me i want to be on CM7 or MIUI, but i CANNOT get around the SD mount error. i have another thread about it. i have tried everything and nothing works. i was thinking of ordering a smaller 8 gig card to try and see if its my cards, what class/type card should i get just to install and MTD rom?? i cant CM7 and MIUI bad
Where's your other thread? I had an SD Card mount error but found a fix and posted it here:
http://forum.xda-developers.com/showthread.php?t=1296694&page=2#post18859876
Let me read your thread and I'll see if it's the same issue.
here is mine http://forum.xda-developers.com/showthread.php?t=1325525
Jsut so I have the steps down:
1) You have the ROM zip file on your SD Card
2) Reboot into ClockworkMod
3) Select install Zip from SD card
4) Navigate to the Zip file
5) Install
You're saying the process breaks for you at #3 because CWM can't read your SD Card?
If the above problem is true, try using rom manager to find and flash the file. if not try a different sd card.
Sent from my MIUI SCH-i500
back to the lag issue...when running these roms are you restoring backups from Titanium. If so, are your backups from a froyo rom, that could be part of the problem if you also get force closes. I had the same problem a while back. I have also noticed if changing fonts(such as with absolute system root tools) certain more elaborate fonts can cause some lag as well. also check into the widgets you are using, even on CM7.1 i get insane lag and launcher force closes if I use Fancy Widgets but everything else is fine.
Hopefully one of those things will solve the issue...if not wipe it clean and start fresh lol but seriously hope you figure it out
after re-reading the op it really sounds like your problem could be with restoring apps, it sounds identical to when I first switched to the GB roms. You run smooth as butter for a while the it all goes to hell. I would start with wipe data/factory reset but when intalling backups try WITHOUT DATA if you still get lag, wipe again and install your apps manually from the market or where ever. I ended up going with the latter and haven't had issues since.
ok, here we go.
Last days peetr_ and me worked on fixing kernel stuff for cm9.
I want to post here our current state of kernel, based on latest github sources of jokersax (thank you for hard working all the time).
any kernels from here: ramdisk will not work with joker's beta 0.1.0 since it has sdcard-ext standart, use his latest builds with emmc/sdcard
[V1]
Some info about fixes:
1. integrated 1% battery directly to kernel, you don't need to install zip fix that I did myself before.
2. activated xt_quota[2], xt_qtaguid addons, it means Network statistics, Battery statistics work now as they should; actually it should increase battery life.
3. some small things
tested as update on beta 0.2, I didn't try full wipe with that kernel.
to be continued.
++++++++++++++++
[V2b]
changes [added]
1. battery fix from peetr_, great idea.
2. jit for cpu
3. avp patch
4. ppp stability patch
5. more cpu patches
6. mem cache improvement
7. some kernel small fixes
++
8. bluedroid lib replacing, it is from CM7 [temp_fix] -> less errors of bluetooth dbus, less drain, but it is still broken (concerning battery life)
++
8. separated version of 1.4 kernel by PM request, not tested. - ready, file was updated.
9. includes all fixes of V1
links at the bottom
10. fix of V2 old version regarding touchpad strange states.
++++++++++++
[V3]
1. touchpad major fix
2. cpu improvements
3. irq improvements
4. tcp/udp patches ()
5. battery will not fool you with 101% ++
6. other things
++++++++++++
[V4]
1. kernel
1.1 tons of fixes + peetr_'s awesome ramdisk work
1.2 as test showed, better battery life in idle mode.
1.3 separated to 1.0, 1.3, 1.4 kernels.
1.4 download in mediafire, can't attach files for strange reason here.
1.0 GHz
1.3 GHz
1.4 GHz
2. ROM
2.0 MUST WIPE /cache partition before installing
2.1 fixed bluedroid (compiled for cm9)
2.2 torch works
2.3 included 1.3 v4 kernel with modules
2.4 fixed some phone app mistakes (credits to avalakvista)
2.5 GSM fix (for international GSM, not USA): it must be installed if you wipe ALL data, (/data and /cache partitions). If you want to install this ROM after other CM9 without wiping /data and you had working GSM, then flashing GSM fix is optional. If you have com.android.phone error after first boot of ROM, then you should wipe all /data and /cache and install ROM, then GSM fix.
download GSM fix
2.6 recommend to use joker-gapps-v10 (can be found in his thread-first post-of cm9)
2.7 there some other fixes but I dont actually remember
2.8 download link here.
+++++++++++
===========
+++++++++++
[V7]
added fixes from turl and faux, thanks to them.
[1.3GHz only]
Outdated and no more supported until some ics kernel source will be out!
peetr_ said:
reserved for future
Click to expand...
Click to collapse
nice work guys!
olegfusion said:
ok, here we go.
Last days peetr_ and me worked on fixing kernel stuff for cm9.
I want to post here our current state of kernel, based on latest github sources of jokersax (thank you for hard working all the time).
Some info about fixes:
1. integrated 1% battery directly to kernel, you don't need to install zip fix that I did myself before.
2. activated xt_quota[2], xt_qtaguid addons, it means Network statistics, Battery statistics work now as they should.
3. some small things
tested as update on beta 0.2, I didn't try full wipe with that kernel.
to be continued.
Click to expand...
Click to collapse
2 Questions....
1) Is this based on the 1.3oc Joker had out?
2) Does it have the SDcard and keyboard fixes for 0.2.0?
Thanks guys...I'll nandroid and then test it out in a few....charging battery up now
thx will try now
Th3Bill said:
2 Questions....
1) Is this based on the 1.3oc Joker had out?
2) Does it have the SDcard and keyboard fixes for 0.2.0?
Thanks guys...I'll nandroid and then test it out in a few....charging battery up now
Click to expand...
Click to collapse
1) yes
2) sdcard connects fine (again, I flashed without full wipe), but android keyboard is not fixed looks like, I have other keyboard installed and android keyboard is disabled. Please install other keyboard before install kernel
update.
actually please test and say
olegfusion said:
1) yes
2) sdcard connects fine (again, I flashed without full wipe), but android keyboard is not fixed looks like, I have other keyboard installed and android keyboard is disabled. Please install other keyboard before install kernel
Click to expand...
Click to collapse
Already have swiftkey x and swype on it
Sucks! I ran out of Thanks for the day! I'll make sure to come back tomorrow and thank
I did the test of android keyboard wrong, to be more correct now, just saying that keyboard works.
thanks for peetr_
Very nice, gentlemen! Looking very good so far! Thanks for your hard work!
---------- Post added at 02:34 PM ---------- Previous post was at 02:30 PM ----------
olegfusion said:
I did the test of android keyboard wrong, to be more correct now, just saying that keyboard works.
thanks for peetr_
Click to expand...
Click to collapse
I can second that keyboard works...while I have swiftkey and swype, I had android inverted keyboard in use, and still working
Hopefully it's fixes my battery issue for dieing faster than hell
Sent from my MB855 using XDA App
Just downloaded, gonna give it a try after work. I'll report back with findings.
Sent from my CM9 Electrify.
I've been using it all afternoon pretty much. So far, so good. I haven't had anything FC since flashing. Looks to be nice and clean
i still cannot get it to read my SDcard.
bigelroy123 said:
i still cannot get it to read my SDcard.
Click to expand...
Click to collapse
Both show up on my phone. Probably haven't done the fix for the sd card that's listed in the "cm9 fixes" thread....
This is just a kernel...sd card issue is in vold.fstab
Th3Bill said:
Both show up on my phone. Probably haven't done the fix for the sd card that's listed in the "cm9 fixes" thread....
This is just a kernel...sd card issue is in vold.fstab
Click to expand...
Click to collapse
i did the fix and its still not working...changed that line and saved it. when i reboot its back to mmc2, and sdcard reading unmounted.
bigelroy123 said:
i did the fix and its still not working...changed that line and saved it. when i reboot its back to mmc2, and sdcard reading unmounted.
Click to expand...
Click to collapse
Do you have "use internal storage" checked in your "advanced" under system settings? That will cause problems....storages (internal and external) will read backwards...
The Emmc(internal storage) shows up at the BOTTOM of the "storage" section...
Which file manager did you use? If you use Root Explorer, mount as R/W, and open in text editor, it shouldn't revert...
Did you make sure you changed the correct 2? I had a guy last night who was changing the wrong one...it needs to be the one specific one...
Th3Bill said:
Do you have "use internal storage" checked in your "advanced" under system settings? That will cause problems....storages (internal and external) will read backwards...
The Emmc(internal storage) shows up at the BOTTOM of the "storage" section...
Which file manager did you use? If you use Root Explorer, mount as R/W, and open in text editor, it shouldn't revert...
Did you make sure you changed the correct 2? I had a guy last night who was changing the wrong one...it needs to be the one specific one...
Click to expand...
Click to collapse
Thanks a lot....i had to mount as R/W in root explorer...everything is fine now.
Gonna test now... Does anyone have jokers stock kernel handy in case we need to revert?
Feel free to call my lazy about backing up and restoring but it'd be much easier and quicker to just flash the kernel ;0)
MobileAllStar said:
Gonna test now... Does anyone have jokers stock kernel handy in case we need to revert?
Feel free to call my lazy about backing up and restoring but it'd be much easier and quicker to just flash the kernel ;0)
Click to expand...
Click to collapse
I've been running this one all afternoon...its a modified joker kernel. So far very nice and stable. Also seems good on battery
Sent from my MB855 using xda premium
Does this fix solve gsm problem? Im out of usa
Sent from my Sensation using XDA App
Since I keep getting msgs from people asking me how I have optimized my Xperia S for less lag and such, I thought I would make a thread teaching others all I know. First a little background info.
I have used a HTC Hero for 3 years before I got this phone, so I know a few things about optimizing and getting the most out of old hardware. This means that I am quite versed in memory management, deleting unneeded apks and proper overclocking for maximum effect and battery life. I hope to install my knowledge upon others so we can stop getting noob threads like "I have less than 1gb of ram" or "ICS lags so I am going back to gingerbread, you suck Sony!".
Before we start, if you have used any of the older kernels with old CWM versions, those versions of CWM can bork your data or system. This leads to root issues, apps still showing after clearing, unable to mount partitions in CWM and any other number of issues. To fix this i recommend flashing a stock Sony ICS firmware, then fastbooting the latest version of Advanced Stock Kernel. This will give you a nice clean slate to work with. Also you can make a backup of stock firmware to roll back to if you have problems.
Now off to the races.
Build.prop tweaks
there are plenty of build prop tweaks out there, but here are the ones i use. I will continue to update this list as I try new stuff
davlik.vm.execution-mode=int:jit
dalvik.vm.heapsize=110m
ro.max.fling_velocity=150000
ro.min.fling_velocity=80000
ro.semc.batt.capacity=1750
ro.telephony.call_ring.delay=0
view.scroll_friction=0.01
windowsmgr.max_events_per_sec=250
Systcl Tweaks
Coming soon.
Memory Management/Free Ram - Many many people complaining about free RAM just don't understand how it works. In any efficient modern OS (Windows 7, ICS) free ram is wasted ram. I theory you should be using your free space to preload resources you might possibly be needing or using them to run a variety of apps and such. The only time where you would really need a large amount of free RAM would be when you want to play a game/ use an app which requires a larger amount of memory than is normally required. Sometimes Android will have a problem freeing up this required space which can lead to lag/freezing or even a reboot. If you don't play a ton of games, then don't worry about having a ton of free RAM. Secondly, more lag is created by the OS needing to resart an app or service (ie Home launcher) than if it needs to kill an app to free RAM. This is why you get Home redraws which lag for a split second, because the OS has killed off the home and it is restarting it. So less free RAM generally means less lag.
PS. Android takes up space for the system and this space is not shown on the ram usage screen. This means that if you have a device that says 1gb of RAM, the free RAM may show only 600mb. Don't freak out, this is normal all devices have it though it varies depending on skinned versions of android and which android version it is using (ie ICS uses more ram than previous versions).
How to fix Android Memory Management - Android memory management has made massive steps forward from how terrible it used to be, but it is still not optimal to say the least. We can help fix this by running a script by our not so friendly XDA member Zepplinrox.
http://forum.xda-developers.com/showthread.php?t=991276
Go to this link and read everything that you can comprehend before reading my explanation. This can be tricky and can force bootloops so make sure you back up with Nandroid.
Step Zero - Get script manager off the market. Run as root
Step One - Download the kit and the latest Supercharger Script
Step Two - Run the kit, generally on the ROMS i have tried at least, you dont need to install a new busybox or root version so skip those.
Step Three - Run the auto mode in the script or Download the automatic patcher which patches your smali files and pushes over the new services jar required for locking the home in memory. (alternatively you can do it the hard way with the smali patcher script but I dont recommend it)
Step Four - Run the script and read through things. It should make sense but ask me if you need help.
Step Five - Clean and Reboot. Sometimes it can freeze on first boot, hold vol up and power to restart. This latest script is still in testing so you may have issues but it is certainly better than the original setup.
I love the Sh1t out of supercharging and have used it for years.
Supercharging is really easy on KA17 as the services.jar is already ready to go. Just run the script which fixes oom memory settings and you are done. Dont forget to clean and reboot.
Follow-up- Run a flush engine option in the script which will then create a quick launch script in V6 supercharger directory. Put this on a schedule to run every few hours and you wont have to worry about rebooting your phone as much. Run it as superuser.
Want even less lag? - Delete any unneeded apk files either with a root explorer or Titanium Backup. This way you wont have apps you dont use fighting for memory and cpu. I delete powersaver and the exchange client as I dont use either. Other roms may have much more.
Kernel - Your kernel and kernel settings will make a huge difference in the feel of the device. I recommend XSX v6 (doesnt have crappy CWM). Set it to 1876-30 hotplug and try things out. Not every chip is the same so they all wont run great. My Hero hated the max frequencies, but my Xperia S will take all the way up to 1900 just fine. Choose a scheduler, I use deadline, but CFQ or noop are good too.
Thanks for the helpful info
Btw which setting do you use in the superscript? Aggressive, balanced etc?
does the new v6 supercharger script patch services.odex automatically? because 'im using stock .45 rom, and it is odexed which made it a lot harder to patch in the past
in the past i did the smali edits myself but i just couldn't be bothered doing it with every new stock ICS release
ttiimm said:
does the new v6 supercharger script patch services.odex automatically? because 'im using stock .45 rom, and it is odexed which made it a lot harder to patch in the past
in the past i did the smali edits myself but i just couldn't be bothered doing it with every new stock ICS release
Click to expand...
Click to collapse
Use the windows patcher or there is a new auto patcher that works pretty good integrated. Check it out.
Windows Patcher for some reason doesnt work for me :/ Btw, which auto patcher are you talking abt? Is it in the script? Which number config?
Btw, if I use a deodexed ROM such as KA ROM, do I have to follow the same steps or are there fewer steps compared? Thanks
SickL1408 said:
Windows Patcher for some reason doesnt work for me :/ Btw, which auto patcher are you talking abt? Is it in the script? Which number config?
Btw, if I use a deodexed ROM such as KA ROM, do I have to follow the same steps or are there fewer steps compared? Thanks
Click to expand...
Click to collapse
Hmm, the windows patcher works good for me. Try the ICS center in the latest version of the script. I use KA rom and have no problems. If you need to I can post an edited services.jar file, but try and see if you can get it to work yourself first.
When I try to run the script it says missing essential tables, what does that mean? Running it without root works until, it asks for root
EDIT: If it is about the starter kit, I have successfully used it
googleye said:
When I try to run the script it says missing essential tables, what does that mean? Running it without root works until, it asks for root
EDIT: If it is about the starter kit, I have successfully used it
Click to expand...
Click to collapse
Its a root problem. What kernel and rom are you on and did you install the root version from the starter kit or not.
V6 supercharger can be a pain to deal with when you havent used it, but hang in there and I will help you with it. Once you figure it out, it is easy to do.
mrsatan said:
Its a root problem. What kernel and rom are you on and did you install the root version from the starter kit or not.
Click to expand...
Click to collapse
Advanced stock kernel build 15 stock .45. Yes, should I flash the kernel again?
EDIT: Reflashing kernel did not work.
Skickat från min LT26i
googleye said:
Advanced stock kernel build 15 stock .45. Yes, should I flash the kernel again?
EDIT: Reflashing kernel did not work.
Skickat från min LT26i
Click to expand...
Click to collapse
Its probably the stock .45 version. Stock roms can be notoriously difficult to supercharge. I use KA12 and havent had any problems beyond a couple root problems caused by the XSX version with the bad ramdisk.
mrsatan said:
Its probably the stock .45 version. Stock roms can be notoriously difficult to supercharge. I use KA12 and havent had any problems beyond a couple root problems caused by the XSX version with the bad ramdisk.
Click to expand...
Click to collapse
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
googleye said:
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
Click to expand...
Click to collapse
Yeah I can see that, I love KA12 though.
googleye said:
Ah. Well compared to KAxx I'm very happy with stock so this will have to wait I guess
Click to expand...
Click to collapse
I'll update my kernel soon now I'm upating my rom
Sent from my LT26i using xda app-developers app
I've installed it on my Acso S (LT26w) and don't see some difference.
My steps:
download all, copy to sdcard and prepare
path jar file via exe
run script and follow instructions
What I must to get in sum?
mrsatan said:
Yeah I can see that, I love KA12 though.
Click to expand...
Click to collapse
Sorry for ot but. Compared to KA10, how's the rom now? When trying both stock was significantly faster and more smooth for me. And do you use the ka kernel?
Skickat från min LT26i
Desperanto86 said:
I've installed it on my Acso S (LT26w) and don't see some difference.
My steps:
download all, copy to sdcard and prepare
path jar file via exe
run script and follow instructions
What I must to get in sum?
Click to expand...
Click to collapse
What does the final part of supercharger script say? What percentage supercharged?
googleye said:
Sorry for ot but. Compared to KA10, how's the rom now? When trying both stock was significantly faster and more smooth for me. And do you use the ka kernel?
Skickat från min LT26i
Click to expand...
Click to collapse
No I dont use KA kernel, I use XSX kernel. KA12 is faster than stock for me and has more options.
mrsatan said:
What does the final part of supercharger script say? What percentage supercharged?
Click to expand...
Click to collapse
something about he (script) finished and now I can manualy choose options from 1 to 33. Option EXIT also was there. I chose exit
Desperanto86 said:
something about he (script) finished and now I can manualy choose options from 1 to 33. Option EXIT also was there. I chose exit
Click to expand...
Click to collapse
You should be fine then