Related
FlyKernel is an overclockable kernel for the Hero GSM, aimed to improve stability, battery life and performance (generally in that order).
The Hero GSM now also has a newer .35 kernel "Las Venturas" you should also check that one out. At the time of writing these lines, the newest version of Las Venturax is found on the second post of the above thread (my post ) - you should check which post is more up-to-date on that thread.
Download and instructions are on this post.
FAQ and advanced subjects are on the second post.
Change log and previous versions are on the third post.
WARNING: Please make sure to have an up-to-date backup before you flash this kernel!
FlyKernel-13 (#253)
FlyKernel 13 - Desean
FlyKernel 13 - Mediafire
FlyKernel 13 - Multiupload
This is a post-LasVenturas update for FlyKernel, after quite some time without any updates.
Although I currently have a bit of a personal preference for Las Venturas, I believe that it is even better to have two excellent kernels for the hero (internally totally different ), so that the users can choose whichever works best for them. Possibly, on some of the older ROMs this kernel might work better. This should also help isolate kernel issues vs. ROM issues.
SmartassV2 (informal description and comparison with the first smartass)
SmartassV2 is a governor (controls the frequency of the CPU at each give moment) which like the first smartass is generally based on the implementation of interactive with some major changes and the addition of a built in sleep profile (behaves a bit differently when screen is off vs. on).
The smartassV2 improves the very naive scheme which the first smartass had: The first smartass (with the values I set for the hero), would cap the max frequency at 352Mhz for sleep and when screen is on, would do the opposite and keep the frequency at 518Mhz or above. For sleep this was very effective but a bit crude and unclean, and there could be some cases where you would need processing power even when screen is off (something is updating and music is playing and etc.). For screen on, smartass1 was too quick to jump to the max available frequency and again would never go below the 518Mhz, so in a nutshell its was using "too high" frequencies.
SmartassV2, introduce (internally) an "ideal" frequency which is the frequency we are "aiming" for, in some sense. The way I see it is that the "ideal" frequency is a hint to the governor what is a good balance between performance and battery life. Now when screen is on, I set (on the hero) the ideal frequency to 518Mhz which will ensure nice responsiveness but limit unnecessary use of higher frequencies when they are not needed. When screen is off, I set the ideal frequency to 352Mhz (0 will disable the screen state tracking all together). From my testing this will "convince" the governor to spend most of the its time during sleep at the lowest available frequencies. Note, that both during sleep and when awake the entire frequency range (as defined by the "user" - i.e. selected with SetCPU) is used by smartassV2. For example, when the CPU is loaded heavily, the highest available frequency will be used regardless if screen is on or off.
Boot OC and optional tweaks
Optionally, you can rename the update file before you flash to change bootup frequencies and other options.
If you don't rename the file and flash "FlyKernel-13.zip" you will get the default tweaks and the min/max frequencies will remain as they where before.
For example, to set the max/min frequencies on boot to 614/176, rename "FlyKernel-13.zip" to "FlyKernel-13-M614-m176.zip".
Supported "flags" are:
Notice, all flags are case sensitive.
-MXXX - set max frequency to XXX
-mYYY - set min frequency to YYY
Supported max frequencies:
518 576 614 633 652 672 691 710 729 748
Supported min frequencies:
19 176 264 352 518 576 614 633 652 672 691 710 729 748
Default behavior, if these flags aren't given, is not to change your current settings.
For frequency recommendations and more info see FAQ #5.
Technical details: max/min frequencies are set in the kernel's ramdisk init.hero.rc file. Previous settings will be replaced. Furthermore, if one of your init.d script sets the max/min frequencies, these lines will be removed.
If you have SetCPU or other program changing the speed at boot, their change will take effect and overwrite this setting as soon as the ROM completes to boot.
-nologo - Don't show boot animation.
-logo - Show boot animation.
Default behaviour, if no flag is given, is not to change your current settings.
-noatime - Mount all partitions with -noatime to improve IO.
-atime - Mount no partition with -noatime.
Assuming, your ROM did not mount any partition with noatime, then the -atime option should undo the -noatime option perfectly. Unfortunately, it seems some ROMs (i.e. VR12) mount only some of the partitions with -noatime. It seems that in some cases, changing the noatime configuration causes boot problems.
Therefore, I highly recommend you make a backup before trying the -noatime flag - this is the only full proof way to go back if it messes something up.
Notice, this does not effect the ext partition as it is not mounted in the ramdisk init.rc. As far as I know, all ROMs mount the ext partition with noatime.
-notweak
By default, the updater will remove scheduler tweaks which exists in the ramdisk init.rc script, in order for the scheduler default compiled into the kernel to apply. This flag will disable this behavior.
More techinical information for developers about the smart update package has been updated in my github wiki.
Limitations and known bugs:
- This kernel will not make you coffee (I hope)!
Integrating kernel in a custom ROM (for ROM developers)
You can use my from above:
http://floyo.desean.net/FlyKernel-13-Floyo.zip
This file has a regular boot.img with a ramdisk compatible with Floyo 1.4, boots at 576/352 (smartassV2) and has all the kernel modules unpacked.
If you need to edit the ramdisk, you can either unpack the above boot.img as explained here. Or you can get the kernel binary file from my smart update package, under tmp/flykernel/kernel. The kernel modules are package in the smart update package under tmp/flykernel/syslibs.tar.
Kernel Sources
My sources with all my updates and changes are found on github:
http://github.com/erasmux/hero-2.6.29-flykernel
Use hero_defconfig for the regular version and hero-bfs_defconfig for the BFS version.
See the wiki for more information about building the kernel and more.
Please feel free to contact me regarding my sources and kernel development.
Using my Kernel Sources
Feel free to use my kernel sources, fully or partially in any (legal) way you see fit.
If you modify the sources, I urge you to share your changes with the community (as GPL obliges you to do), preferably using github. You can fork my sources on github, and this will make it easier for you to grab new changes from me and also allow you to fill pull requests so I can pull your changes back to my kernel.
GPL
Yes I am GPL complaint, all is included inside the sources, including the GPL license itself.
Thanks
Huge thanks to Desean for giving me file hosting that makes my life easier
Many thanks to all the Kernel/ROM developers here, especially those with open source kernels on github - LoxK, Cyanogen, Ninpo, Radu and especially Decad3nce.
Big thanks to all those who helped test the pre versions and reported bugs, specifically also to my long time testers (moonshield and floomat)
Donations are always welcome and accepted but are in no way required.
FAQ and Advanced Subjects
FAQ
0. When reporting a problem, do I need to include the ROM and exact kernel version I am using?
YES!
1. How do I flash the kernel update file?
You flash it from recovery, like any other custom ROM. If you are not familiar with recovery and/or haven't rooted your phone, start here.
2. Do I need to wipe anything when installing the kernel?
No you don't need to do any wipes. Just install the kernel through recovery and reboot
3. The update from recovery failed with errors/warning?
Please, in the same recovery session which you tried to apply the update and failed, select the "Move recovery.log to SD" from the "Other" menu and post in this thread with the recovery.log attached (for example in a .zip file).
4. After flashing the kernel my ROM does not boot
A logcat of the boot process might help me understand the problem. Using adb you can generate one with the following command and attach it to your report:
Code:
adb logcat > logcat.txt
You need to run this command relatively close to the start of the boot. Close the window after the phone is stuck for few minutes (say 2 mins with no change should do). You can start by running "adb logcat" and seeing if you get any output at all. If so, reboot once more and run the above command from the start of the boot (approximately).
Please also clearly state which ROM you are using and which kernel did work for you (which one did you use before).
To recover from such a scenario, boot into recovery and restore a backup of your working state. If you do not have a backup, and its the kernel fault, flashing your old kernel should solve the problem.
5. What min/max frequencies should I choose?
The short answer: min 176, max 614, if you have wake up issues up the min speed to 264 and then to 352.
To play with the speeds I suggest you install SetCPU (or similar app), so you can view and change your settings interactively. To change it permanently from the bootup see instructions on first post. You also use options like "Set on boot" in SetCPU if you prefer that.
The long answer:
The max frequency will effect the speed and responsiveness of your phone when screen is on. Note, that any speed above 528Mhz is above the specification of the manufacturer, hence is overclocking and could, in theory, shorten the life of your device. At high enough frequencies all devices will stop functioning, the exact threshold depends on your luck with your specific device. From my experience and knowledge, running at stable frequencies (or say one or two steps down to be on the safe side), should not harm your device - of course all overclocking is done at your sole responsibility.
As far as I know, almost all device can handle 652Mhz, most can reach the 691/710 area and some can even reach higher than the 748Mhz cap of this kernel. To find out which speed your phone supports, use SetCPU (or similar app), start from 614 for example and up the speed one tick a time. Don't select "Set on boot". At each step play with the phone a minute or two. If the phone gets stuck, reboot it (take out battery if necessary) and go one tick down.
Additionally, note the higher your max frequency the higher the battery drain will be when the screen is on. It is true that the display, data, wifi, gps, etc. should drain much more than the cpu. Still, I recommend staying in the sane frequencies range, no more than say 691Mhz (even if you phone can handle it).
Finally the min speed will effect standby battery life (when screen is off). From my experience there is a difference in battery life between 19Mhz and 352Mhz min frequencies but it is relatively small (much less than I expected). 19Mhz is not stable for me, almost stable, but over a period of weeks you will probably experience weird and possibly very rare instabilities. For me this was the when playing music with screen off the phone got stuck at 19Mhz (very hard to find this out), and became totally unresponsive until I rebooted it. Therefore, I recommend starting from 176Mhz, and if you have wakeup issues to bring it up. With 352Mhz you should have no wake up issues at all.
6. I am having wakeup issues (such as unresponsiveness to wakeup, weird coloring after wakeup, screen inversion, caller id not working on wakeup)
Up the min speed to 264 and then to 352. With a min frequency of 352 you should not have any wake issues.
See the FAQ #5 above for more information.
7. I am experiencing bad battery life with FlyKernel
First, please make sure to reboot the ROM at least one time after you flash the kernel. There have been reports that ROM/kernels behave badly on the first boot.
Personally, I do not do battery calibration, but if it makes you happy go for it. I do recommend at least charging the battery overnight, or a couple of hours after it has reached 100% to be sure it is full. Then use it, your regular usage for a few days and only then judge the battery life.
The battery percent indicator, over short periods of time seems extremely inaccurate and its very hard to reach any correct conclusions based on it.
If you do want to report bad battery life, please state your settings (kernel version, min/max speeds, governor, etc.), over which period you have been testing the battery, under what usage, what is the battery life you are used to having with which kernel and what is the battery life you are experiencing now.
Note, that roughly speaking, I lose less than 1%/hour when screen is off (wifi, data, gps, etc. also off), and about 10%/hours when just screen is on but phone does nothing at all (again wifi, gps, etc. off). About 20%+/hour when stressing my phone (although I have no data plan so can't test that). I am using the latest FlyKernel @ smartass 614/176.
8. What size should I give the swap partition?
short answer: 0.
long answer: I do not recommend using swap on the hero, hence 0. If you have a very fast SD card, and want to try it, give it say 64Mb. Note that I know of no ROM for the hero which activates swap automatically - you'll need to add a init.d script or something to activate it (see a bit more info here). Let me know if you find a scenario where the swap gives substantial improvement over no swap.
Finally note that FlyKernel versions before 12 do not support swap.
9. Should I use ext2, ext3 or ext4 for my ext partition?
Short answer: ext4. Note that FlyKernel versions before 12 did not support ext4, ext3 is supported since version 10.
Long answer:
Previously, I was under the impression that a journaling file system is a very bad idea for flashable storage. I still think its not ideal but better than the other alternative:
I have been using dual booting, placing an entire development ROM on an ext2/4 partition and using it for development. And when using ext2 it would get errors almost every boot and every couple of days get corrupted to the point I needed to manually restore damaged files to get it working....
It seems that if you only use it for app2sd, there are very infrequent changes to this volume (only when you install a new app), hence it does not get corrupted. But this also means that ext4, in this scenario, will not pay much overhead because there are very few changes. And in the case there are many changes, if I have to choose between a slightly shorter SD life with ext4 (and then I can finally get a faster one ) or risking my data getting corrupted on a daily basis with ext2 - I prefer the first (ext4).
Questions 10-13 are now obsolete with smartassV2 - see the first post for details about it
10. Do I need a SetCPU (or similar) screen off profile with smartass?
No, smartass automatically limits the screen on frequency to >= 518Mhz to ensure responsiveness, and screen off frequency to <= 352Mhz to keep standby battery life under control. Much like HTC's perfllock, it does this at the kernel level so it is much better than app level screen off profiles.
11. Using smartass the CPU frequency does not drop below 518Mhz (with screen on)
Intentional to ensure responsiveness. From my testing, when screen is on battery drain difference of speeds < 518Mhz is not significant relative to the drain by the screen itself.
12. Using smartass the CPU frequency does go above 352Mhz (with screen off)
Intentional to keep standby battery life under control.
13. Using smartass the CPU frequency is always at its max (or always at 352Mhz when screen is off)
See "Monitoring the CPU frequency" in the "Advanced subjects".
14. I am experiencing spontaneous reboots
Please post, in this thread, with as much detail as possible about the problem.
Please also attach the last_kmsg, which you can get from example using:
Code:
adb pull /proc/last_kmsg
15. What happend to the BFS version?
With the FlyKernel-12 scheduler tweaks (CFS scheduler), it surpasses the BFS version in every way. I tried to compile a BFS from the FlyKernel-12 code but even in neocore, in which the BFS was always much better, the new tweaked CFS leaves the BFS in the dust. Hence, I see no reason to continue and build/support a BFS version. The hero-bfs_defconfig is still up to date in my sources if anyone wants to build it themselves.
*. I am experiencing an issue not covered in the FAQ which I believe is kernel related
Please post, in this thread, with as much detail as possible about the problem.
Please also detail why you believe this kernel related. The best "proof" that it is the kernel's fault, is to flash back your old kernel and verify the problem is solved, then reflash the new kernel and verify the problem reappears. In any case please detail the kernel and version(s) on which your are experiencing the problem and those on which you do not.
Advanced Subjects
* Monitoring the CPU frequency
Will rewrite this more clearly. In the meantime:
http://forum.xda-developers.com/showpost.php?p=9925116&postcount=903
http://forum.xda-developers.com/showpost.php?p=9929325&postcount=919 <-- Mainly this one!!!
http://forum.xda-developers.com/showpost.php?p=9989996&postcount=970
http://forum.xda-developers.com/showpost.php?p=10010110&postcount=990
Change log and previous versions
FlyKernel-13
- Scheduler tweaks: use the scheduler settings that worked well on flykernel-11c and 12pre6 (tweaked them very very little), responsiveness should now be better than on the FlyKernel-12 release
- Backported the new smartassV2 - now the default
- Added interactiveX governor also
- A few config changes and compiler optimizations
FlyKernel 12a (mediafire)
- Fix wake up issues with new scheduler tweaks
- Smart update script: make noatime tweak option to (hopefully) solve boot problems
FlyKernel 12
- Smart update script
- Optimized scheduler parameters
- Fix Usb mass storage after usb tethering (at least on CM ROMs)
FlyKernel-12pre6
- Align ext2/3/4 config options
- Merge small fixes to lowmemorykiller module.
FlyKernel-12pre5
- Backport of smd rpcrouter to avs333 request.
FlyKernel-12pre4
- Partial fix for the lockscreen flickering when locked/unlocked rapidly (with smartass).
- Very small tweak to other smartass parameters.
FlyKernel-12pre3
- Fixed frequency table according to Radu's comments. Frequencies which are not on PLL2 have been removed!
- Tweaked smartass to spend more time at the lower frequencies to improve battery life. Also smartass's allergy to 19Mhz has been cured!
- Some configuration tweaks, mostly sleep related.
- 528Mhz frequency does not work well with OC, so it has been replaced with 518Mhz which does work fine.
FlyKernel-12pre2
FlyKernel-12pre2 optimized for CM based ROMs (default speed 576/352)
- Added compcache support
- Added 19Mhz and 264Mhz frequencies
FlyKernel-12pre1
- Lower voltages of high frequencies (>= 528Mhz)
- Added ext4 support (I currently use it for dual booting)
- Interactive updated (does anyone find it better than smartass? in what scenario?)
- Smartass fixes and optimizations - should be more responsive now and battery life should (hopefully) still be excellent.
- Camera backport from .32 (12pre1-cam32)
FlyKernel-11c
FlyKernel-11c #66 (Generic)
FlyKernel-11c-BFS #67 (Generic)
- Smartass: now wakeups up from sleep first at 528Mhz (no OC), to hopefully help with wake up issues.
- Bunch of fixes/optimization from CM espresso kernel and from Decad3nce (see github)
- BFS version
"Optimized Kernel Packages" (only for CM6 based ROMs: Floyo, Elelinux, Froyd):
Find the appropriate kernel for you by its name in the FlyKernel-11c directory
The naming conversion is:
flykernel-11c-CM-<min>-<max>.zip (with boot animation)
flykernel-11c-CM-<min>-<max>-nologo.zip (no boot animation)
flykernel-11c-BFS-... (BFS version)
FlyKernel-11
- New smartass governor (see technical detail below). Previous governors still supported.
- Added IPv6 (only for Google Googles?!)
- Fixes camera freezing CM6-based ROMs (thanks Ninpo for a "code cleanup" which fixed this )
- Fixes detection of USB connection during boot on CM6-based ROMs.
- Various squash-sets imported (see github)
- NORMALIZED_SLEEPER disabled.
FlyKernel-10a (rapidshare megaupload)
- Optimize some sleep/idle code (thanks to ninpo)
- Add module for IP header compression - hopefully this helps google apps (inspired by ninpo).
FlyKernel-10a-BFS (rapidshare megaupload)
- BFS version of 10a.
- Whats is BFS? see wikipedia and more details here.
FlyKernel-10
- Fixes for Froyo ROMs (FroydVillain and Elelinux)
- Added some more modules inside the kernel (notably using VPN should now work). I am now more aligned with the modules included in other kernels (well mainly ninpo's kernels), so hopefully you should not run into any missing modules.
I even added support for ext3.
- Generic update for all ROMs.
Flykernel-09:
FlyKernel-09 for VR12,RCMix,ChoclateEclair,Modaco and SuperHero
FlyKernel-09 for Kimera and Sensehero
FlyKernel-09 for MMod 1.2.3
FlyKernel-09 for FroydVillain and elelinux - Beware there are problems with 09 and Froyo ROMs.
FlyKernel-09 for CM6
- Added the excellent minmax governor.
- Removed interactive as it does not behave well at all - just use minmax
- added version which supports the 288M data partition - removed now since MAX appears to be fading out - just use dalvik2SD instead.
FlyKernel-08
FlyKernel-08 for Froyo and ASOP
Added Mike Chan's interactive governor, adaptation to Hero by Nadlabak and Ninpo. Added some tweaks of my own - now works well also with big frequency table.
Tweaked conservative governor for better performance.
Fixed/cleaned kernel co/nfig and modules - among other things iptables should work fine now.
Bigger frequency table.
FlyKernel-05 (BFS)
BFS version of the FlyKernel-04
FlyKernel-04
Based on HTC 2.6.29 official kernel source.
Includes patchset 2.6.29.6 and various fixes
Boot OC - Only for Sense based ROMs (The smart update script added in FlyKernel-12 provides a cleaner and better solution for all ROMs)
Boots very quickly by setting the OC speed right from the start. Also sets the original HTC boot animation which is quicker for most ROMs. Finally, replaces the 09zipalign with 09betterzipalign (again thanks ninpo).
Please have a backup before you try this, as there is no other easy way to undo this.
Select the update file according to the speed your phone can handle:
boot @ 653/160: http://www.multiupload.com/5RAXNJ7AWY (rapidshare megaupload)
boot @ 672/160: http://www.multiupload.com/RRQ0HYI8O8 (rapidshare megaupload)
boot @ 691/160: http://www.multiupload.com/20AJV7FLQI (rapidshare megaupload)
boot @ 710/160: http://www.multiupload.com/WHROUYNGQ6 (rapidshare megaupload)
Theoretically, this should now work on any ROM and any OC kernel. I have tested the 691 update on VR12 and Froyd 1.4 with my kernel and it works fine. Above files (now with "_" at end of name) updated to also work on ChocolateEclair and hopefully other ROMs on 31/8.
Note that in my recent kernel versions the lowest frequency is 176, so it will boot with a min frequency of 176.
cool.. will try. like the idea of overclocking before boot
can you post a diff file of what you modified?
diffs of which change?
there are a lot of changes and fixes, which range from fixes by me in the source code, to just copying/applying files from others.
I think it would be better to keep this thread open for issues and questions about the usage of these fixes. Still I will be more than happy to share anything I have done - please contact me with the exact change you are interested, either by PM or open a new thread if you think it is of general interest for developers.
There are literaly dozens of different kernels floating arround, all of which are always "brand new super fast ultra optimized". From a user perspective it's hard to tell which one is the best. I think this community needs more openness in the developpement. I think it would be a good habit if developpers posted their diff files (of everything) instead of just saying that they made "optimizations".
thanks for your work
zorxd said:
There are literaly dozens of different kernels floating arround, all of which are always "brand new super fast ultra optimized". From a user perspective it's hard to tell which one is the best. I think this community needs more openness in the developpement. I think it would be a good habit if developpers posted their diff files (of everything) instead of just saying that they made "optimizations".
thanks for your work
Click to expand...
Click to collapse
Trying it out might help in deciding which is the best for you. There is no such thing as an absolute best, sorry. To each his needs and his preferences. I also included a convenient undo update script which restores the original kernel.
Personally, I am not aware of any other kernels for the VillainROM (except the original one by ninpo) and for me my kernel works better. Additionally, I have gotten very good feedbacks for my kernel and fixes on iandroid (using HebVillain which is very tightly based on VR12). So I thought others here might want to try it and maybe would also like it. Please also feel free to bash it, but please try it first and then reply with comments which I can relate too.
Finally, I am all for complete openness: If you are really interested in the kernel sources, you can find them along with all my changes here which could be of great to help to you especially if you want to compile the hero kernel yourself. In such a case I would recommend starting from here. The biggest other change is the RTL fix, for which you find the diffs here (it is verses the eclair branch of the android source code). As for the other files & changes I did, I have tried to detail as much as possible in my original post.
Feel free to contact me (also by PM) if you want more info or help.
I just installed your Kernel and the Boot Optimization and brother my phone is flying!!!! GREAT JOB!!!
100% recommended flash for your VR12
THANKS!!!
yep!
all great! you are the MAN =)
good work erasmux, does it work with Arabic language with Arabic fonts installed ? I mean connected letters
Thanks a lot
I hope it does. I don't use Arabic, but if there are problems, report them and I'll do my best to fix them.
Good job erasmux!
Problems for me.....
Installed Kernel & Optimization and Boot time optimization
Made all my icons go to pot,
"problem loading gadget" on powerbar,
"problem loading gadget" on Battery Meter Widget
Game Icons, CoPilot live, System Widget all showing default app icon.
Lost a WHOLE LOAD of installed apps, simply not there listed any longer. So many gone I can't recall what I have lost.
Tried the undo file Original VR12 Kernel:
Got my apps back but still probs with some widgets, boot screen remained the HTC one (didn't revert to the villian screen)
First, I have fixed the kernel restore file in the original post to also restore the original villain boot animation, note that the new file is called: V12-RestoreKernel_.zip (with additional _ at end)
Thanks, for the remark.
Regarding the apps, that is very weird. Did you get these "problem loading gadget" on the screen or where? A logcat from the start of the boot would be very helpful (although I can understand if you don't want to flash it again just to help me debug...).
Regarding the widgets (when the apps do appear) ,try clearing the HTC Sense data (unfortunately this will reset your desktop but it should restore your widgets and its better than having to reinstall everything).
I'll have to have a go later.. tied up at the mo..
Prob loading gadget appeared on the screen (still does).
Will try clearing sense and post back later.
EDIT: Clearing Sense worked. Thanks.
made battery callibration (http://www.villainrom.co.uk/viewtopic.php?f=97&t=1789&start=20#p19769).. full charge (~17:15).. after 5 hours using phone.. 5-7 calls (1-5min each), 30 min wifi and playing =) and now ( 22:40) 99% battery!!! blja, im very happy!!!!!!!!!!
cpu always 245-576mhz
only like with original VR12 kernel after few hours of use at 576mhz linpack score down from 2.5 to 1.8 , but after installed autokiller ( preset 60mb) it's always 2.45-2.57
now i think VR12 the best!
Thank you one more time! will write back tomorrow eve =)
is this included stuff really usefull or it can be disabled?
ipv6 (lot of different options)
LZO and ARC4 crypto stuff
extra PPP stuff (MPPE, PPPOLAC, PPOPNS)
DSCP and TCPOPTSTRIP
INET_TUNNEL
XFRM_IPCOMP
CPU_FREQ_GOV_CONSERVATIVE
the /proc/config.gz (kernel .config support)
Also, I noticed that the device boot with mem=64M. Does it mean that the rest of the RAM isn't used?
AFAIK the only way to change this is to recompile the kernel.
Many of what you said I saw requests here on XDA that kernel developers add (there applications which use it). Please note that many of those modules do not automatically load and need to be manually loaded so they should not have any effect.
Others stuff, mainly the IPv6 stuff i doubt anyone uses - must have "inherited" it from the config i used as a base. I will look into it for future release if I can remove that stuff.
About the mem=64 I am not sure what that is, my phone is definitively using the full memory. I will also try to understand and possibly adjust that for future releases.
Thanks for the input.
An other question, is a kernel really tied to a specific ROM? I have VR12 right now so I could try it, but I was also thinking of upgrading to a 2.2 ROM.
About the modules, I think that most of the stuff that I noticed was compiled in (=y) and not as modules (=m). If they are only used by 1% of the users, I think it would be better to have them as modules and make sure that they don't load automatically at boot.
Also, do you know if it is better to have a small frequency table (with, let say, only 3 choices) to avoid excessive frequency switching?
Is the dalvik to SD trick included worth it for those of us with the original 2GB SD card?
hi this is not my rom i just saw this from a thread and im just translating it
[06/30/1910] EDGE Hero 1.1.2 - OC, A2SD, based on EU
Well, after throwing me almost all day yesterday and this morning fighting with new ROMs, I got a rooter, overclocking, put a2sd, change the launcher, optimize pngs, etc. And here it is:
EDGEHero 1.1.2 - based on the U.S. ROM
What's in?:
Root.
Superuser.apk nicer (see screenshots).
Apps2SD.
Dalvik2Cache
Autokill.
Busybox.
Own theme.
Kernel overclock up 810 MHz (Not you pass the 710-768, is too unstable).
CPU usage optimizations.
PNGs optimized to load faster and save space.
3D Gallery running like an angel.
Wifi working.
Linpack \u003d> 2.2-2.3 MFLOPS without OC, OC to 3.1 with 768. 5 MFLOPS with JIT.
Market ALL apps running.
Deodexada ROM
JIT Patch (Goes well, but make Nandra just in case).
Livewallpapers with launchers - with Sense T_T not go, you could modify a little Rosie.apk that appeared on the forums of Villain and allows the LWP, but it would be foolish because at the end while stop working.
I accept suggestions for future versions. That the work already achieved ROM. Now people need to say what he would like to include.
Instructions:
Do you come from another ROM?
-Make three wipes of rigor (or 5 as you give).
-Flashing the ROM.
-Restart.
"Upgrading from an older version?
-Wipe the Dalvik-cache.
-Falsheo.
Why JIT?
Start the normally-ROM, change wallpaper for one you have in the SD. REQUIRED.
"Reset> Recovery> Backup Nandra> Wipe Dalvik.
JIT-Flashing.
"Pray, pray a lot.
WARNING: DO NOT WIPE OF DATA. If borráis the data folder and my theory is correct, you **** the JIT and the ROM, I loved those bootloops come. If you're going to wipe the data for an update or something, you have to put the patch of JIT-OFF. Then you can put it back, but if not, do not start.
Difficult, eh?
"A2SD?
"If you already have the SD partitioned, no problem.
"The partitions must have is a fat and a ex2/ext3 (preferably ext2), minimum. You can also have swap partition, but this ROM does not use it.
"It is obligatory to do so, but advisable.
Download:
Version 1.1.2:
http://www.multiupload.com/C2KLJV3QN7
MD5SUM: f12bb83c25f496b7654ead34481b7b39
Version 1.1.1:
http://www.multiupload.com/D6I9LSVS5M
MD5SUM: d17e48b0d4f32f16985af04c444a0fce
Version 1.1.0:
http://www.multiupload.com/GLME2WGYW3
MD5SUM: 2986ec120aa2b0a04dcf83a3d4afa717
Version 1.0.2:
http://www.multiupload.com/HBAM7OF2OY
MD5SUM: 37ff4d0259ee5b3f1e6efa7fd8afb288
Patch to add search and voice dialing and set the default keyboard Castilian (added from 1.0.2):
http://www.multiupload.com/QV7NP9P0LT
Stock kernel (disables all optimizations, it is assumed):
http://www.multiupload.com/VZT5PXX9UM
Protected-apps-patch (is already installed as standard on versions> 1.0.1):
http://www.multiupload.com/909MI94LIA
Sense transparent clock (subject to metamorph)
http://www.multiupload.com/HSPX5KXNIU
JIT Pache VERY IMPORTANT INSTRUCTIONS VIEW:
http://www.multiupload.com/TMDBJELUBO
Patch JIT-OFF (warning if it does not work):
http://www.multiupload.com/YOWHLLENCG
FIX to use voice recognition on the keyboard (to be included from 1.1.1):
http://www.multiupload.com/75LO1BZO0S
FIX the Lockscreen (the bar no longer cover the "Snooze", including from 1.1.2):
http://www.multiupload.com/CYLNCRZ1YC
Changelog:
-1-07-10 -
Version 1.0.2:
Overclock fixed (theoretically), added file manager (Estrong file manager), fixed update-script to be no need to wipe data or yes (theoretical as well, I could not prove it), and added HTC_IME MOD, which comes with recognition voice.
-30-06-10 -
Version 1.0.1:
Fixed the OC to 810 MHz, protected from market applications, custom loading screen Sense.
Version 1.0:
Root, OC 691, and CPU optimizations several pngs, first version.
Thanks to:
The kid who sacrificed so that we have the root, the team Villlain APPS2SD the script to kendon the source code of your kernel and build a magnificent guide to Feeyo by some of the commands and build optimization . prop.
looks good
Awsome! Will add link to this thread in my thread right away
C0mpu13rFr34k said:
Awsome! Will add link to this thread in my thread right away
Click to expand...
Click to collapse
no problem mate if u want me to translate more i will u just tell me =)
Nuclear Overclocking holy moly that does not sounds to good
Feeyo said:
Nuclear Overclocking holy moly that does not sounds to good
Click to expand...
Click to collapse
844mhz lol
Err... a "CD-ROM" based rom for my hero.. think i might just stick with an established one rather than a peripheral one
these numbers..... 800 mhz and above.... are impresive, but i am absolutely sure that NOONE will find them usable.... (i don't mean to offend the aouthors of the rom) .
woah
let me know if somebodies device can use it! 800Mhz...
liljom said:
woah
let me know if somebodies device can use it! 800Mhz...
Click to expand...
Click to collapse
Computerfreaks does
Wow, thanks for the info, but this translation is horrible lol
Where it says "nuclear overclocking" it should say "kernel overclockable", sorry to disappoint you
Also, I haven't tested it, but it says it's overclockable to 810Mhz, don't know where you get the 844Mhz from
aleixps said:
Wow, thanks for the info, but this translation is horrible lol
Where it says "nuclear overclocking" it should say "kernel overclockable", sorry to disappoint you
Also, I haven't tested it, but it says it's overclockable to 810Mhz, don't know where you get the 844Mhz from
Click to expand...
Click to collapse
i now i think the guy who wrote it must of been sleepy lol and i heard u can go 844mhz i cant cuzz i hae a week hero mine can only go up to 768mhz
aleixps said:
Wow, thanks for the info, but this translation is horrible lol
Where it says "nuclear overclocking" it should say "kernel overclockable", sorry to disappoint you
Also, I haven't tested it, but it says it's overclockable to 810Mhz, don't know where you get the 844Mhz from
Click to expand...
Click to collapse
maybe it was made by gtranslate.
but it goes up to 844Mhz. I installed it : )
Nice one, very nice
asad510 said:
Computerfreaks does
Click to expand...
Click to collapse
Yeah baby! xD It gets EXTREMELY unstable with JIT on though and it cannot take more than 800MHz with JIT and still it is VERY unstable but with JIT of I can take it all the way only with minor problems
EDIT: Seems like it does nothing when you overclock over 787MHz seems like it's the max... Going to try overclock widget and see if that can move it further
EDIT2: Set the overclock to 787MHz and it worked fine then I set it to 806MHz and it seemed like it set the clock but also that the max speed was now set to 768MHz. Then it put it all the way up to 844MHz and my phone froze... There must be some kind of bug...
EDIT3: I have no idea if my phone is actually running over 800MHz cause everytime I set it over 787MHz it just shows 480MHz all the time...
so.. does the 100mhz jump show any drastic improvement in the response of the touch and program loading?
rafi300 said:
so.. does the 100mhz jump show any drastic improvement in the response of the touch and program loading?
Click to expand...
Click to collapse
Nope OC over 729 MHz on my phone slows it down but I guess if i kept pressing the linpack button eventually it would hit that record breaking spot xD
It can be translated on the website...
The text can be translated on "HTCMania"...
Just go tho the bottom and click on the British Flag... It is about the twelfth from the left...
Aqmaqr said:
The text can be translated on "HTCMania"...
Just go tho the bottom and click on the British Flag... It is about the twelfth from the left...
Click to expand...
Click to collapse
lol never saw that lol
Aqmaqr said:
The text can be translated on "HTCMania"...
Just go tho the bottom and click on the British Flag... It is about the twelfth from the left...
Click to expand...
Click to collapse
It seems that instead of that, it was translated to taiwanese from HTCMania, and then to english using gtranslate lol
Since i've installed this ROM my Phone doesn't ring anymore. Is there any solution for this.?
thx in adv.
TG 2.0 is probably my final Gingerbread build for Hero. I think it's pretty complete, stable enough for daily use and fast, much faster than 1.x.
Screenshots and more info in post #2
IMPORTANT NOTES:
1. Don't use any other OC app, please only use the included one.
2. On the first boot many internal tweaks that require a restart are set up, so please do so before setting up stuff, this is pretty critical.
3. Wipe absolutely everything, even if you come from TastyGinger 1.1.
Changelog:
- updated to latest sources
- fixed text rendering
- added power widget in notification bar AND their settings in settings/display
- much faster(as in snappiness, dunno about benchmarks &co)
- EXT-A2SD - moves apps and dalvik cache to SD works now, I've tested it again and again
- added LWP
... and other minor stuff too
Features:
- RaKern 200 kernel @614MHz default
- new CPU governor, MOBILE GOVERNOR, written from scratch, based on the ondemand governor's behavior, with some tweaks -> limited frequency when CPU is idle, optimized frequency stepping based on CPU load and others too *** at the moment the governor comes as a module, and I'm not going to release the source code until I make it a perfect option for mobile, battery-powered devices; I still have to test it on other types of CPUs to see what can be done to improve.
- default Gingerbread launcher, with a few tweaks to make it faster
- built-in low-DPI
- built-in overclocking app, very basic and straight forward, but with a very nice way of doing things(see post #2 for more info)
- no ads in browser and apps
- compatibility mode disabled by default
... and many others
DOWNLOAD TastyGinger 2.0 for HTC Hero(mdpi)
MD5: 3ad7c8523b75f371ae99b5fdbd05a376 (please check if your installation is not working according to changelog/feature list)
Alternative
Reserved for screenshots and more info
downloading...
Sent from my Hero using XDA App
Downloading now... Thanks
being a bit of a noob, but how does a2sd work? i know the option on recovery, what should swap be? i know aaaages ago i used 512mb for apps, so how do i do this??? lol
Swap is useless with this ROM.
is this right? swap is 0mb, change ext2 to ext3 and when the option on flashing, male ext2 as 512mb??? all done???
Leave it as EXT2. And yes, but do this BEFORE flashing the rom.
Games?
Does Homerunbattle 3d and Backbreaker work on this build? In other (1.1) doesn't work.
Do you think a 8GB Class 2 would be sufficient for Apps2SD?
Any SD Card will do the job
holyshit1 said:
Does Homerunbattle 3d and Backbreaker work on this build? In other (1.1) doesn't work.
Click to expand...
Click to collapse
Hey, Radug can you answer on my question?
I don't have the apps installed so I don't know
ETA on screenshots?
See the TG1.1 screenshots... the default wallpaper is different and that's about it... and yeah the text rndering is better.
I'll try to post them later today.
Nice rom! Any idea on how to add dictionaries to the stock keyboard?
RaduG is there any possibility to change screens to only 3?
Not with the default launcher.
Umm, any way to get "Friendstream" or something? Basically I want a widget, that shows latest messages on facebook/twitter and lets me respond to them
Mirrored version 2 on my server . here
Welcome to Lightning ROM
MAJOR UPDATE, REV3, CHANG LOG IN SECOND POST**********
The goal when creating this today has been simple. Squeezing the most performance out of the T-Mobile Galaxy S III as I possibly could, without destroying your battery. This ROM was build with two things in mind - optimization and speed. Nuff said. It is based off the official Jelly Bean leak as of late last night and wild child's deodexed version he was kind enough to throw down. It will probably impregnate you, with twins, then not pay you child support. If you are ready to propel your device to levels above 9 thousand, you should probably keep reading. You have been warned. IT IS FAST! ..... yet... friendly...
Like myself, in the spirit of android, I am sure you all love customization. I am doing something a little different with this. Rather than add all the toggles, mods, themes, etc, I focused today on the performance aspect and will leave the theming up to you, and after you get it set up the way you want (as there will soon be and already is tons of pretty extras for this build) revert to post 2 of this thread for a nice little guide to odex this bad boy straight from Android UI via terminal emulator. I'll take care of the tweaking, you theme it the way you want, then wrap it up with some memory optimization of your own, or don't. Sound good? Thought so
Getting right down to it - a quick list of things modified here, and I know I am missing some things:
-Init.d support
-Busybox
-Deodexed (until you odex - see post 2)
-Rooted - duh
-CIQ removed***
-Debloated: removed a lot of stuff, but it is all avail' in the market, youtube, etc, you would have had to update it anyways -__-
-File system and SD read optimized for speed
-added freeza's custom CPU script to init.d ***see changelog in post 2
-Build.prop has been modified.
*added the 0 ring delay script
*wifi scan adjusted to 600
*media streaming optimized
*media recording optimized (video and image)
*data speeds optimized
-Database df on each boot / sql support - totally kanged this from somewhere else it was kanged... all credits due
-Memory optimizations
-Default IO scheduler optimized for flash-type disks (android devices)
-Carefully modified CPU parameters with performance in mind. Tweaked values to optimize IO throughput during heavy workload and multi-tasking, yet on the other end, CPU cycles are greatly reduced when system is not under heavy load. You will see this in performance :highfive:
INSTALLATION - follow this to the T, or I will ignore you. And keep in mind you might still have issues. Not every device is the same.
1. download ROM, put it on your external SD card, and verify it is good with an MD5 check
2. once all is well, boot to recovery
3. do a factory reset/data wipe (I have always been in the habit of being thorough and formatting anything 3 times)
4. format/wipe system (3 times recommended)
5. flash ROM
6. reboot (it will take a couple minutes)
7. once the device boots, let it stand alone for about a minute or so (i typically wait until it shuts off the display on its own) and ENJOY
NOTE: DO NOT TRY TO SIGN IN TO DROP BOX. I REMOVED IT. DL FROM MARKET!!
Also, some other things removed: browser, YouTube, calculator, some other stuff. I didn't remove anything that was not available in the play store. Wanted to keep it light weight. Do not try to sign in to anything other than your google account when you boot. Again, enjoy.
thanks to wild child, freeza, virus, steelH, dj, luke, ktoonz, and many others. mad respect to you all. i have implemented things that are either your direct work or things i have learned from you. so here is my humble shout out. if there is something i left out, somebody i didn't mention, please forgive me and post in this thread and call me out, i will happily update the OP with thanks. respect to you all
REV_3 - ready, set.. ok click now!
With morfic's kernel..... clocked at 1.83
ok... so if you are like me, and you REALLY wanna get intense with this, and just make it as bad A as you possibly can, keep reading....
This will essentially odex all files in your /system/framework and it will do it straight from the Android UI via my personal favorite app ... this is good because it frees up mem, and reduces DVM size. OPTIMALLL
1. download the odex.zip here --> PURPLE
2. extract all files with a file explorer, i prefer root explorer or fx file explorer
3. place the extracted folder and all of it's contents in /data/local/tmp ... so you should have /data/local/tmp/odex/+(misc files in new odex directory)
4. give the new directory and ALL contents FULL permissions. full read, write, and execute perms. your file explorer, if it has taken you this far, should be able to accomplish this
5. download this app TERMINAL EMULATOR dont worry it is free. open the app
Type the following commands - each new line should be executed with the enter key:
su (hit enter, it will ask for root)
/data/local/tmp/odex/odex (hit enter, you will see
you will see a bunch of outputs. there will be a message when it is done (honestly, like 10 seconds if that) saying something like "enjoy your hybrid ROM"
type "reboot recovery" (without the quotes)
device will boot into recovery immediately after you hit enter...
wipe cache and dalvik cache once more each, and reboot your device.
viola <--- this was spelled wrong. but i am going to leave it. because i can. rofl
THANKS*** freeza for sending me the the odex script, and you're welcome, for the bootclasspath for the script.. lulz. and thanks freeza for convincing me to download titanium backup again... and you're welcome for giving you the peace of mind that you can odex framework from android. el o el
****change log*****
rev3-December 1st, 2012 -uploading
-added morfic's alpha 23 kernel. OC'able to 1.83, no UV, L2 cache tables optimized, CPU hot plugged (for now, panel of=cpu1 off), pretty much an overhaul here. performance is ridiculous.
-removed CPU tweak by freeza (i still love you tho)
-optimized IO, AGAIN. adjusted ondemand parameters for a little bit better performance
-removed unneeded scripts from init.qcom.post_boot.sh file - positive effect on IO
-cleaned up build prop, added scripts for TCP windows, added network hack by... somebody... can't remember. File is in /etc/init.d/ "internet"
-optimized BT audio streaming
-added properties for optimal accessibility of T-Mos spectrum/towers
-disabled unneeded logging - save CPU cycles and power
-debloated some more. lightweight. DO NOT... try to sign in to dropbox upon first boot (if it even gives you the option) download the latest version of the app on the play store.
rev2-NOVEMBER 19, 2012
-removed some UI audio sounds (charger connection [for those that listen to music], lowbattery sound, volume toggle sounds, other annoying useless sounds such as boot up and power off)
implemented freeza's CPU control script for some amazing performance and battery life. thanks bud, as always, great work. i have been running this since he was finished with it, and it is absolutely amazing. your device with tons of unique and user friendly, editable scripts.
-freeza's CPU script adjusts CPU parameters for both cores based upon whether your device is charging, and how much battery you have left. it is a performance and battery friendly script that is power efficient and editable depending on what YOU want your device to do.
beta1-
initial release
all the things...
In rev 2, with freeza's CPU mod, you can navigate to init.d and you will see a "70cputweak" file. if you open that up, you can adjust CPU values and parameters of governors to your liking. for now, i left them as is - the way they were when freeza gave them to me. edit them with a file explorer and reboot and you are now adjusting your OWN values based on the performance and battery YOU desire. follow instruction in OP to flash
Thanks will try this later today
Sent from my SGH-T999 using xda app-developers app
Does teathering work on this?
ScottBroker said:
Does teathering work on this?
Click to expand...
Click to collapse
wireless/native? no. but my easy tether app works perfectly. i'll implement it, if i have time, in beta2... i haven't slept in two days lol
OP updated
Will the odex.me app work with this rom? I'm not lazy, just curious if there's an easier way to odex..tia
Sent from my SGH-T999 using Xparent Blue Tapatalk 2
Yeah does the odex me app work the same way than doing all that other stuff?
Sent from my SGH-T999
which tether app you using ?
Thanks
Odex me app will not work
great Rom thanks
Is this still running Touchwiz? How much RAM available? Other then your optimizations for speed what has been added or removed? Are animations gone due to the optimizations?
EGBTMagus said:
Is this still running Touchwiz? How much RAM available? Other then your optimizations for speed what has been added or removed? Are animations gone due to the optimizations?
Click to expand...
Click to collapse
All I have done is tweak properties listed. Didn't mess with animations, or anything. You guys can do all that with a theme, kitchen, etc... I would recommend wild child's work. It's great stuff. Like I said the reason for this is because after you get it the way you want, you can go in and odex it and finalize your OWN build the way you want it to look. I'm not too big on aesthetics. But I can make your device run better
And to answer your question, yes, it is still running touchwiz launcher by default. Again I would recommend apex or nova. touchwiz is awful IMO. nothing unique about it.
Rom looks great will be testing it tonight!
Can anyone confirm wildchilds kitchen is working?
Sent from my SGH-T999 using xda app-developers app
Liking the rom so far, only issue I have come across is that I can't get App2ExtSD2 working.
Can we use your Odex wizardry in any deodexed TW Rom?
SiNJiN76 said:
Can we use your Odex wizardry in any deodexed TW Rom?
Click to expand...
Click to collapse
yeah
http://forum.xda-developers.com/showthread.php?t=1994048
Thanks...didn't know he created a separate thread.
Anyway, the first thing I noticed was that when I try to sign into Drop Box from the initial boot sequence, it FCs... I also got nowhere near the Quad score the OP got. Mine was in the 3Ks. Just my experience.
CIQ?
SiNJiN76 said:
Thanks...didn't know he created a separate thread.
Anyway, the first thing I noticed was that when I try to sign into Drop Box from the initial boot sequence, it FCs... I also got nowhere near the Quad score the OP got. Mine was in the 3Ks. Just my experience.
Click to expand...
Click to collapse
I got over 5K in Quadrant, but I also came from a 100% stock phone (reset it to make sure there were no issues). DropBox fails intially because he removed dropbox from the rom.
EDIT:
I can't seem to find the stock web browser... has it been removed?
There are many different ways to tweak a android phone in XDA, here I want to share about what I did to my Gio
1) Rom: CM7 by ItachiSama 20121225 Nightly + U235 Kernel by farzad.u235
2) CM7 Performance setting: Disabled Compcache, surface dithering, Use 16bit transparency
3) CPU setting: 245Mhz - 844Mhz + SmartAssV2
4) Script: V6Supercharger U9RC8.2 & 3G TurboCharger, CronMod-INT2EXT+ for 500MB sd-ext
5) Swap: 64MB swap file in sd-ext
6) Scheduled Fast Engine Flush every 3 hour by Script Manager
7) App Quarantine for Apps that hardly use but keep start itself in the background
I think that's all, any other suggestion?
Usually when i use cm7 i only use these settings
CM7 Performance setting: Disabled Compcache, surface dithering
CPU setting: 245Mhz - 800Mhz + LagFree
And the rom is smooth enough for me
With cm7:
Ondemand + noop
245 min / 864 max mhz
Adrenaline engine (or tweakzv6 + default.prop from adrenaline engine) + cronmod int2ext4+
Init.d: 98netforks_tweak + loopy smoothness + 14enable_touchscreen_1 script
Pimpmyrom apk with only ondemand governor tweaks enabled + entropy set on boot.
And with cm9 I only use supercharger with patched services.jar and with latest cm10.1 no tweaks because lots of problems with patched services.jar and supercharger script and other scripts like mmb or adrenaline engine works only for 50%.
Verstuurd van mijn GT-S5660
Thanks for reply~
I suspect that the scheduler in Script Manager drain the battery pretty fast, so I disabled it,
Also I find this link to force GPU to render: http://madteam.co/forum/tutorials/%28tut%29big-performance-increase-on-cm79/15/?PHPSESSID=fnattahs63jq78lie5nd7f6ee3
I tried PimpMyRom before but I think basically it is like a script generator
zivgt2 said:
There are many different ways to tweak a android phone in XDA, here I want to share about what I did to my Gio
1) Rom: CM7 by ItachiSama 20121225 Nightly + U235 Kernel by farzad.u235
2) CM7 Performance setting: Disabled Compcache, surface dithering, Use 16bit transparency
3) CPU setting: 245Mhz - 844Mhz + SmartAssV2
4) Script: V6Supercharger U9RC8.2 & 3G TurboCharger, CronMod-INT2EXT+ for 500MB sd-ext
5) Swap: 64MB swap file in sd-ext
6) Scheduled Fast Engine Flush every 3 hour by Script Manager
7) App Quarantine for Apps that hardly use but keep start itself in the background
I think that's all, any other suggestion?
Click to expand...
Click to collapse
Can we get a link on how to for every relevant method.Things like
Swap,scheduling,quarantaine...
Are i think not that common.If there are scrips procedures... The thread will gain a lot of attention
Enthusiastic Gio User
Very glad with the work done
But sometimes a pusher for results( nothing bad intended)
i use tyuxmod + wolf script and myphone is so smooth
dreuzel said:
Can we get a link on how to for every relevant method.Things like
Swap,scheduling,quarantaine...
Are i think not that common.If there are scrips procedures... The thread will gain a lot of attention
Click to expand...
Click to collapse
For swap, you can install a app called Swapper for Root,
then use it to create a swap file in sd-ext, then use terminal:
su
swapon /sd-ext/swap.swp
And App Quarantine is just a app.
After trying a whole bunch of tweaks on a whole bunch of roms , i got to the conclusion that it`s not worth it on the long run to use them , my personal opinion only. If the rom has a CPU manager i usually just set the min to 245 and maybe maybe i switch to smartassv2 and that`s all. If the rom doesn`t have that included i just leave it like that , like AOSP roms for example , they are great exactly as they are.
bogdanwp said:
After trying a whole bunch of tweaks on a whole bunch of roms , i got to the conclusion that it`s not worth it on the long run to use them , my personal opinion only. If the rom has a CPU manager i usually just set the min to 245 and maybe maybe i switch to smartassv2 and that`s all. If the rom doesn`t have that included i just leave it like that , like AOSP roms for example , they are great exactly as they are.
Click to expand...
Click to collapse
agreed...after 1 year of using gio and after trying several roms/scripts, in cm 7.2 at least all it is needed to be done: governor smartassv2, 245-800 and nothing, NOTHING else...the phone is as smooth as butter..no swap, no scripts, no overclock, no lag (except for when updating/installing something, but this is normal even in full desktop PCs)
Glisse said:
agreed...after 1 year of using gio and after trying several roms/scripts, in cm 7.2 at least all it is needed to be done: governor smartassv2, 245-800 and nothing, NOTHING else...the phone is as smooth as butter..no swap, no scripts, no overclock, no lag (except for when updating/installing something, but this is normal even in full desktop PCs)
Click to expand...
Click to collapse
Yes it is just like a PC, and the more Apps you use and the more resources they require, the more power is needed.
I have 336MB Apps on my Gio(only 3 games, less than 40MB), if there isn't any tweaking available I think I am using a better phone months ago.
Even a simple minfree tweak on a stock 2.3.6 rom by Apps like "AutoKiller Memory Optimizer", the difference is pretty noticeable.
And about the smooth as butter thing, I cannot agree with you, if only you are comparing Gio with something like HTC Hero.
Just sharing my opinion
zivgt2 said:
Yes it is just like a PC, and the more Apps you use and the more resources they require, the more power is needed.
I have 336MB Apps on my Gio(only 3 games, less than 40MB), if there isn't any tweaking available I think I am using a better phone months ago.
Even a simple minfree tweak on a stock 2.3.6 rom by Apps like "AutoKiller Memory Optimizer", the difference is pretty noticeable.
And about the smooth as butter thing, I cannot agree with you, if only you are comparing Gio with something like HTC Hero.
Just sharing my opinion
Click to expand...
Click to collapse
I am not using gio as my primary phone, i own an htc one s.. ofc, there is a big difference between a single core 800 mhz and a dual core 1.7 ghz.. still, on gio i have no lag, hence i call it smooth as butter.. no, i am not playing games which most likely are NOT smooth, nor am i using on gio cpu/graphic extensive apps like photoshop or whatever.. i am not one of the guys complaining that their 1000 $ 20 years old car is not able to go from 0 to 100 in 3 seconds like a Ferrari.. yes, starting opera from sd-ext is taking much longer than on the htc, but i was talking about the snappiness of the phone during menus, doing stuffs, how fast reacts to inputs, commands and all that, with stock settings and no scripts and "optimizers".. maybe it matters the specific ROM each one uses? i dont know what the minfree values are in my ROM, but i have no issues with memory, no need to have an autokiller (which by the way is absolutely useless unless you disable the services..it autokills programs which start again right away, i am talking about facebook, google`s one, etc) .. but it is good that we disagree, this is how the world evolves
Glisse said:
I am not using gio as my primary phone, i own an htc one s.. ofc, there is a big difference between a single core 800 mhz and a dual core 1.7 ghz.. still, on gio i have no lag, hence i call it smooth as butter.. no, i am not playing games which most likely are NOT smooth, nor am i using on gio cpu/graphic extensive apps like photoshop or whatever.. i am not one of the guys complaining that their 1000 $ 20 years old car is not able to go from 0 to 100 in 3 seconds like a Ferrari.. yes, starting opera from sd-ext is taking much longer than on the htc, but i was talking about the snappiness of the phone during menus, doing stuffs, how fast reacts to inputs, commands and all that, with stock settings and no scripts and "optimizers".. maybe it matters the specific ROM each one uses? i dont know what the minfree values are in my ROM, but i have no issues with memory, no need to have an autokiller (which by the way is absolutely useless unless you disable the services..it autokills programs which start again right away, i am talking about facebook, google`s one, etc) .. but it is good that we disagree, this is how the world evolves
Click to expand...
Click to collapse
I admit I am just trying to push it to the limit
It spends hours to trying/wiping/rebooting to squeeze 1%, many would just go buy a new phone.
And some people are still trying to make CM10.1 fully working on Gio
Some people (like me) are still dreaming for a better phone. So yeah have to live with what i have now (galaxy gio)
Sent from my GT-5660 using xda app-developers app
I use Jellybread ROM and it's great enough
Do you guys use Compcache?
the best tweaks that you can install is the combination of fly-on mod 1.4(or later)+Fly-On ram manager gamers edition+ full gpu rendering
Well I use cm 7.2 by mmb team + activospeeder 3.5 + geva's megabass = awesome phone
Sent from my GT-5660 using Tapatalk 2
wowwwww
wow