Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.
First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated
First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.
for me
another one for me
last one for me
Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!
How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!
Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know
flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere
I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..
I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....
Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,
Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks
Related
...............................................
.....................................
.........................................
`````````````
nice job...try it now!...i saw it on twitter two days ago...
zhang yixi said:
nice job...try it now!...i saw it on twitter two days ago...
Click to expand...
Click to collapse
Okay cool, Let me know how you like it and if you got any problems just post and i will get to them
Fastest way to send a bug is with twitter
LOL i am a twitter addict and have it refreshing every 5 minutes haha
And which is the default frequency? 528? Or...
Anyway, flashing right now. I LOVE ur Roms.... hehehe
Just flash.
I feel abit slower than cm5.0.7 test3.
Thanks for the hard work.
Hello New Thread.
I kinda figured you fell asleep last night Kolohe. I will check your beta when I get home from work later today and put up the mirror. I am going to keep your old ROMs up there too
got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?
Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, Restoring APPS Does Nothing.(No APPS Restored) It Was trying use the Dusted-donuts hack that caused the apps to be Broken.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
EDIT: JIT-HACK It does work.http://droidbasement.com/db-blog/?p=245 this is what i used.
Thanks again for a great rom!
This thing Flies!
I'm using the Jit-Hack And AnyKernel OC Patch,changed swappiness to 95 in 86supersettings,and cpu refresh to 1000000(kills batt),and Cpu Min/Max to 122800/716000. Still using SetCPU for Sleep/failsafe Profile.
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)
well gonna give this a try let u know soon for any bugs
To confirm this is JACP?
Watching logcat I saw that debugger daemon is enabled. I/Debug.
and is this based on CE-5.0 t2? or are patches for T3 in place?
quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.
Will fix the apparently problem but that might be caused by thenew boot script that wipes the dalvik cache. .. will be working on that later today
quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.
Click to expand...
Click to collapse
You can I suppose,
Just needs to be a CM5 based rom
Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, it is just trying to restore apps that messes it up.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
Also as a side note, I think apps2sd must be enabled by default,or get rid of the auto app restore thing. I think it is going to confuse people and clutter up the threads.
But thanks again for a great rom!
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)
Click to expand...
Click to collapse
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works
got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?
Click to expand...
Click to collapse
Yes it is normal but if you want to turn it off before you log in press menu button in setup andthere should be an option to turn it off
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a test
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.
Click to expand...
Click to collapse
Okay when I get home I willtry and fix
UPDATE 8/24! Please go to the site and download the latest version RC1b which corrects 2 small bugs people have reported. It now sets the proper permissions on batt-diag so it runs, and it changes the way the program tries to SU so that you can choose to not have the program attempt to run SU if your rom has trouble running su from terminal;
---Original Below---
I decided to create a new forum for the latest battery tweak as so much has changed since the initial versions.
To get things started, I'll just say that collin_ph battery tweak is a collection of scripts designed to make the hero (for now) last longer on battery, run faster, and run better. The tweak includes CPU management, Battery Management, Disk Performance Boost, Scheduler Boost, LED Fix, Audio Quality boost and other features to improve the usability of your Hero.
Instructions: Go to http://www.primoweb.com/froyo to download the latest version and get the documentation.
Boot into recovery and flash the zip file.
After reboot, you may run batt-cfg from shell or terminal (Note, that the scripts will all request root access, so there's no longer a need to su before running them).
to run batt-cfg
go to terminal in the phone or use adb shell from your PC
once there, type
batt-cfg
It will pull up a menu of choices. For further info, see http://www.primoweb.com/froyo
You can load a 691 mhz default (most Cyanogen kernels now only support up to 691 mhz anyway), or, if you have an uncapped kernel, you can choose a 768 mhz setting. Note: Both settings actually run at 691 when on battery and only run higher when plugged in.
The basics of how the battery is extended is that this tweak causes your phone to scale down (to lower frequencies) faster and to scale up slower. In stock configuration, the cpu scales up when only under 70% load -- while part of this tweak causes it not to scale until it's at 95% load, avoiding unnecessary scaling and battery drain. A second (and arguably more important) feature, is that as the battery drains, it lowers the maxumum CPU frequency. So when you have 1% battery left, you may be running at 468mhz instead of 691. Another plus is that the phone runs in a "higher performance" mode while charging via AC, and another mode to make sure the phone is actually charging when connected bia USB, in addition to the settings mentioned above when the phone is on battery.The best part is that almost every parameter in the system is adjustable through terminal or adb shell using a program called batt-cfg -- just run it and you'll be presented with a menu of options.
I'm constantly updating the documentation, so please check back often as I'll update this thread until there's a final 3.0 version. We're already working on a 4.0 which will be available on the market. We'll post more info there as it happens at www.tweaktool.com
COMPATIBILITY NOTES:
This tweak only works with clockable kernels. A lot of ROMS have reclockable or overclockable kernels which should work. I recommend Froyo roms, but I have heard of the tweak running with 2.1 releases. The main incompatibility seems to be with the service startup-- on some roms, the service doesn't automatically start up.
to verify if your rom is compatible and that the tweak is working, reboot.
Then go to terminal or adb shell and type:
pidof batt.sh
if it returns a number, then the service is running. If not, you'll have to start it manually every time the phone reboots by going to terminal or adb shell and typing
batt-cfg
then choose the option to save and exit. This will manually start or restart the service. Note: if your rom does not start the service automatically, you'll have to do the above batt-cfg procedure after EVERY boot or battery tweak will not run.
If you're a ROM developer, you'll can probably make your ROM compatible by adjusting your rom (ramdisk) to call (import) /system/etc/init.local.rc from init.rc -- assuming your ROM has an overclockable kernel like fresh, darch, or others.
ROMS based on unclockable kernels like Damage Control, won't work without a kernel upgrade and may still not start the service automatically upon reboot.
Thanks to Decad3nce for testing and improving several parts of the battery tweak.
So to flash this tweak and have it working on the latest Froyo nightly, do we need to flash overclockfix.zip ??
I had to flash this fix almost with ever nightly, coz the frequency list would not show up when i need to customize tweak settings.
I was reading the documentation and saw the CFS tweaks are disabled by default. Will this correct the GPS issue that was on beta 10?
Froyo Hero to the rescue
Thank you for all your work on this, got 12 hrs on 50% today with beta 10 and Decad3nse #8, 768 pre-set, most time I've ever gotten outa my Hero. Flashed your RC1 (with Darch's RC1) about 45mn ago and used custom settings to jack-up the max to 768 across the board, min.s and intervals stock. Thank you for explaining the 768 pre-set is really 691! Gonna sit on what I've got for a day and then try w/ Darch's "fix" kernel. Hope I can keep the max on batt @ 768 'cause it seems to make my Hero more responsive/less laggy.
I was not able to use the batt-diag in adb shell. I'll report back tomorrow how the tests go.
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
it made my hero laggy!!!
ToxicToastKatz said:
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
Click to expand...
Click to collapse
Follow the uninstall steps form the documentation
How do I uninstall it?
adb shell
batt-rm.sh
Follow the prompts and the tweak will be uninstalled.
Click to expand...
Click to collapse
Then flash the new version, this is how I have been doing it.
Excellent tweak! Used it through Beta and now enjoying the RC. Well done!
wow.. the way things are going i don't think i am going to jump into a evo... i am loving my hero so much.... thank you for all your hard work..
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
imb951 said:
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
Click to expand...
Click to collapse
Thanks for the notes on batt-diag. I'll look into it and release a fix this evening. Thanks.
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
I'm getting the same root problem with 8/22 nightly.
Sent from my HERO200 using XDA App
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
collin_ph said:
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
Click to expand...
Click to collapse
I'm using my red dawn rom with a modded ramdisk to allow for the battery tweak. The beta 10 worked and even the rc1 asked for su and I said allow the the whoami just kept going and going. I uninstalled via ur instructions on ur site and flashed again and same results
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
zachslavin said:
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
Click to expand...
Click to collapse
Were you doing the updates through ADB or terminal? When would it hard lock up.. during save changes?
CFS Tweaks and Decad3nce Kernel
I understand from reading the Kernel info, that the CFS on this tweak needs to be disabled first....did you make CFS tweaks on by default? Arent we supposed to flash the kernel first, then disable cfs tweaks and reboot? Im confused as to the order in which things are flashed. WIPE, ROM, GSHITZ, BLACKMOD, KERNEL#7, COLLINS RC1. Then go to term EMU and disable CFS, then save then go back into batt-cfg and choose option 1 768 and save and exit then reboot. Woudl that be correct?
Like i've posted in the setup thread from Liquid, this setup is the best i've tried until now, the only one that make missing call an old history in fact
Another better than ever pola 100 nand / nand setup
Download rom (5.5 version - 6 doesn't work with polaris kernel) : Scoot CyanogenMod (RLS5.5) [16.03.2011] and put it on your sdcard in a directory named andboot (at the root level)
with atool download the latest 2.6.32 kernel, modify it as desired
flash your unlocked phone following this tutorial or use atool scripting ability
update needed : none
work : everything except camera !!!! very smooth and very reliable(no missed call for 1 week, that's a revolution) and not so bad battery life
finally, development kernel seems to be not so far from "ready to production" status, with even better nand stability
we're waiting rom update and next krazykilla's kernel with polaris support, for a better stability and ability tu put data on ext4 partition
Thank you to scooter, liquid nr2jt and all androidhtccrew for their tuff work
Nand is not perfect and run corruption sometime that crash your setup : use the nand startup "backup/restore" data ability after you have configured your rom and favorite applications, to avoid loss of everything : it will create a 256Mb image of nand memory in your SD card /andboot directory that you can restore later in case of crash.
you can increment this backup later if you are happy with future modification of your rom
TIPS : noticed that setup as it is is good enough, people at cyanogenmod know their business
- Tip 1 : in atool, you can try to increase advanced battery capacity to improve accuracy because N2jrt has noticed battery calculation is not good and there's a correction factor of 1.6 to apply (i put 1900 but you can increase to 2200 in theory)
- Tip 2 : you can download Roguetool from the market to overclock your phone
- Tip 3 : try the app named killerauto from the market, it does a very good job with very comprehensive settings to free your ram in real time (and increase battery life)
- Tip 4 : In cynogenmod parameters/performance : check the "keep home in memory option" and activate compcache (10%) to get better result - i don't activate JIT
- Tip 5 : i've noticed that's the battery widget is cause of some trouble sometime, you can get rid of it in this case
what's next
- make polaris' atool development kernel compatible with release 6 : thx to scooter and liquid by advance
- Make crazykilla kernel with ext4 support available for polaris (release from his #54 thread doesn't work for me) or maybe unified every kernel to get the best one
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
l1q1d said:
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
Click to expand...
Click to collapse
i get the error message
"install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge"
maybe i missed something
Blinking screen
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Krysiul said:
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Click to expand...
Click to collapse
i don't know such setup sorry, i work on nand only to get real speed
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
arzakem said:
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
Click to expand...
Click to collapse
Yes i've read this technique somewhere, maybe i will try it next time
thank you for the tip anyway
Krysiul said:
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
Click to expand...
Click to collapse
yes if i remember well my past haret experience, i had to deactivate PIN in WM to make android work
arzakem said:
although no camera.
Click to expand...
Click to collapse
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
I've tried deactivating in WM, but that doesn't work as I've written above. I also tried to disable PIN using my friend's LG AT&T and it didn't work either so I guess I have to try some PC software or go to my service provider and ask them to do it. Thanks for replies.
chourmovs said:
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
Click to expand...
Click to collapse
lol i've read about the 2.6.25 working camera several times yet i chose to follow the blunt idea that "everything current is best ever" setup.
Anyway ill follow your advise now hehe and finally will have a working camera back again. anyway we have a backup hehe. Thanks man!!!
by the way, i liked your post title a lot haha.
arzakem said:
anyway we have a backup hehe.
Click to expand...
Click to collapse
yeah that's why i try other roms today (i'm in a rom rush ) to see if situation is better with backup trick
i saw the great nr2jt say in a topic that he save is data every morning to prevent its loss
that's why i give another try with scoot 5.5 with liquid's 2.6.32
Hey liquid do something for us to use 6 release
post 1 updated
After numerous builds+kernels, loads of frustration (and the inevitable revert to wm for a while) I think I like this setup. Simplicity at its best, Scoot CyanogenMod (RLS5.5) and latest 2.6.32 from atools as per 1st post. Just re-purposed the camera button as 'home'. Even my headset works, albeit intermittently.
Which settings for ATools for pola200?
Hi,
i tried to install this rom on my german pola200. But on the Linux Bootscreen the text is scrolling down and sayes that it installs the rom. But than it scrolls down error messages.
I tried this for houres but it shows no final error or something. The Text is scrolling on and on.
So i think that i used the wrong settings in atool. I used this tutorial to set up atool: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
What settings should been used?:
- What version to select?: Donut, Eclair or Froyo?
- Best settings for sd-card-partition? I used first partition 3 gb fat32, second partition 1 gb ext2.
- where should i install system and data? Both on second sd-partition? Or should there be a third partition? (the first time i tried to install the system on intern memory but install runs out of space)
Can you please explain the right settings in atool?
best version is froyo.
to choose sd-card partition, you must have your sdcard PREPARED beforehand. Atool does not partition your sdcard for you. As of what to use to partition your sdcard you can search it at google. (im sorry im a little bit short on time now). choose NAND on both system and DATA.
atools has sd partioner inside so you can repart sd card (boot script editor Y), but the sdcard must have only one partition on it (fat32).
i stand corrected thanks l1qu1d.
USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.
Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)
Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html
reserved for even more future use
Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium
Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.
I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.
Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium
Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium
mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.
Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+
Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl
After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
azreal8 said:
hi
I clean flashed cromi-x 5.4 and ran the quadrant benchmark and get around 5000.
according to the screenprints of results here, I should be getting 7500ish.
can anyone explain or help?
the tf is unusably slow. at least 5 second lag before it responds to anything.
in twrp mod, it flies though. any ideas???
Click to expand...
Click to collapse
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
berndblb said:
You are running Quadrant in performance mode, are you?
Did you choose to install with fsync off?
Try data2sd but that lag is not normal even with fsync on....
Tons of widgets on your home screens? Tell us more about your setup.
Click to expand...
Click to collapse
azreal8 said:
hi..
no widgets but for one (asus weather).
my microsd port is not working so i can't use data2sd.
i did a wipe and clean install of cromi-x 5.4 with the extreme tweaks bunds and selected to disable the fsync and my quadrant standard edition results are still "poor".
my concern is more WHY my devices frezzes and takes at least 5 seconds to even respond after i launch and app or even press the settings button despite a new rom and kernel.
doesn't that suggest something else is amiss?
Click to expand...
Click to collapse
That is really strange and unusual and certainly a PIA. But let's make sure we are on the same page:
Define what you mean by 'clean install'
Post your bootloader and recovery versions please.
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but is unusable when running a rom, stock or otherwise?
azreal8 said:
yes has me baffled so am here for help
when I am in twrp, I press install and along the process i'm asked if I want to wipe which is the recommended option. I select this option.
is that the correct way?
side point/question, what does it mean if when going thru aroma installer, the TF flies but it unusable when running a rom, stock or otherwise?
Click to expand...
Click to collapse
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
berndblb said:
So you never did a clean install
The option in the installer only wipes cache and Dalvik. You HAVE to wipe /data before installing a new rom.
Boot into TWRP.
Go to Wipe
Just swipe the button
That will wipe all your apps but not your personal files like pictures etc.
Then reflash the rom, select _that's kernel, select fsync off, select the two GPU options and everything else you desire.
Once the Aroma installer finished it's your choice if you want to try CROMi-X as is or flash LMK's tweaks right away.
Once you reboot, you will have to go through the setup process again, reinstall all your apps but I can almost gurantee: It will be worth it!
Click to expand...
Click to collapse
sbdags said:
What is wrong with your microsd card slot? This could be causing other issues if the device thinks it has to keep polling for something that isn't there.
Click to expand...
Click to collapse
all of a sudden the microSD slot doesnt work.
the slot on the keyboard however does. is that weird?
quite disappointing. also as i've unlocked, ive lost my warranty.
azreal8 said:
thanks!
wiped properly and just did the install.
let it settle for a while and quadrant score was 6600 so im happy with that. i ran it earlier and it varied from 3500 to 4500. is that odd?
the result is still less than the 7500+ though. ideas? i'll have to look up these LMK things you mentioned....im a newbie.
seems like the freezing has been solved such that the tablet is usable...fingers crossed it stays that way.
Click to expand...
Click to collapse
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
sbdags said:
6600 is very respectable for the TF700 and it should feel quicker. 7500 is extreme - I doubt most users will get that - I never did on ET either
Click to expand...
Click to collapse
Haha, you never get up to 7500... My average on the latest ET is around 7800ish and pass 8000+ on the high end.. BTW, if you would like to try out the new ET, please give the .9 a run because I am be able to have an extra one hour comparing to the .8 without performance loss. The average battery life on my daily usage on .8 is about 4+ hours and the .9 is about 5+ hours. Please give some feedback if you try it, thanks..
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
azreal8 said:
newbie question..
just trying now...where is the init.d folder ? i looked using root explorer and dont know the path.
cannot see a systems folder.. thx
Click to expand...
Click to collapse
It should be under /system/ect/init.d..
If you flash my zip file, everything should set up properly for users to use...
LetMeKnow said:
1. Go to the twrp and do a backup for your device
2. Go here and download the ET v1.13.9 with the suffix "ext4" http://forum.xda-developers.com/transformer-tf700/general/et-v1-13-8-cromi-x-t2843054
3. Install the zip in the twrp
4. Report back how it goes
If you don't like it, you can restore your backup to the previous setup...good luck...:fingers-crossed:
Click to expand...
Click to collapse
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
azreal8 said:
Got 5800 Max with this one.
I'd like to try another cromi-x which has scores in the 9000s.
It needs bootloader version 10.
How do I get this? Newbie qn I know..
Click to expand...
Click to collapse
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.8GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
LetMeKnow said:
That score seems like you were running balance mode which is set 1.4GHz for CPU and 520MHz for GPU. My balance mode is around 6000+. You could try to run the quadrant in Performance mode and should be easy getting 7500+ on your current setup...
I don't think there is a 9000+ score for Cromi X unless you are running ART on Crombi kk. There are only two users running Cromi X with the score 8000+. One is lucius.zen who set the CPU with 1.9GHz and GPU with 700MHz on Hund's kernel. The second user is set the CPU with 1.7GHz and 700MHz with GPU on Hund's kernel... If you can get that 9000+ on Cromi X, then you are the first user who is achieved the best score out of this tf700 forum, good luck....:fingers-crossed:
If you want to update the bootloader to .10, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=2688891
I hope that helps...
Click to expand...
Click to collapse
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
azreal8 said:
Cool. Was wanting to try this one..
http://forum.xda-developers.com/showthread.php?t=2672751
skimmed the link but couldn't see how to change to .10.
I tried saving the Asus firmware to an SD and renaming but my tf didn't detect and update..
Click to expand...
Click to collapse
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
LetMeKnow said:
Oops, it is my bad.... You could follow the Cromi X first page to update your bootloader but you may want to update your twrp after that because it is an old version of the twrp, good luck....:fingers-crossed:
Click to expand...
Click to collapse
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
azreal8 said:
cool. was trying to flash the asus .10 version with twrp and it failed.
can someone pls confirm if i have done something wrong?
this is what i did:
1 boot into twrp
2 clicked install button
3 selected the asus extracted zip file ( renamed to this to EP201_768_SDUPDATE.zip as apparently its a trick) which i saved on my internal drive
4 swiped to install
result - got failed message.
Click to expand...
Click to collapse
What does the failed message say - it probably tells you what failed?
Also extract the recovery log from TWRP after.