Database Info

Making the HERO FASTER project

howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views

I think the problem with this is that processes in Android drop in and out of memory. So, for example, Rosie will be dropped out of memory to make way for the browser and a heavy web page. Applications that are dropped have their state saved, so when you go back to them you are taken back to the position you were in. However, big processes like Rosie take a noticeable time to get back to where they were.
I think the key to speeding up Hero is increasing "memory" so that processes don't need to get dropped. Hence why I've been looking for that elusive perfect Compcache build. If we can make 100Mb of usable memory work more like 200Mb or more, then that might do the business.

ahh i see, but would not doing this speed up the pick up time of the for instance rosie apk?i can see where you are coming from because if we had more memory we would not need to drop the rosie out of memory, im thinking tho if you had both more memory and a process manager it could be some speedy stuff...hmm

Changing process priority probably wouldn't help, because (using Rosie reloads as an example) there isn't a process to prioritise - Rosie isn't actually there any more to give increased priority to. Maybe you could give priority to the process that does the reload but the subjective speed increase would be I think negligible, because loading from sd or memory is going to depend on the speed of the memory, not how much processor grunt the reload process gets.
A nice idea but I think the way Android works would make it problematic.

cool cheers for the insight into android glad someone knows there stuff lets hope someone comes up with a working solution

hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.

Has there been any optimization of hero or just a straight port?

bademasta said:
hmmm. also i think that android itself is doing it's job not sooo bad. i can't imagine that loading back the rosie process is not getting enough cpu time, that would be a huge design failure ...
correct me if i'm wrong, but i really hope, that android is intelligent enough to do this on it's own.
Click to expand...
Click to collapse
but what ur missing is that hero is not built for the magic with 192mb of ram is it now? so somewhere u are guna have to make some OPTIMIZATION

Android is very good at managing resources and applications...
Having developed some Android applications, I can't really think of a good way to improve on the current system. Perhaps all I could suggest is running a Manual Process Manager... and closing applications/Services which you no longer are using but are still running.
A quick tip would be, when you are running an application and no longer need it... use the back button, not the Home button.
If you use the Back button, the application will Destroy... the Home button will 'Pause' the application and assume that you will want to come back to it later.
Android maintains a chain of open Activities, you can keep opening new Activities and it will maintain the old one you were running in a 'Paused' State. If you keep moving forward and opening new applications, but never go backward... you will end up with a lot of things running... so each time you open something, it may need to free up some memory by closing an application that has not been used for a long time which is still in a paused state.
You could speed things up in that scenario by running a task manager and killing processors... or I usually just reboot my phone...
Here is a diagram which shows the Life cycle of applications. Services have a slightly different Life cycle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can read more here
Hopefully this info helps, sorry for wandering a little bit bit off topic...

Hello,
Before tweaking Android to try to run Rosie properly, perhaps we can try to optimize Rosie ?
For example, in the first roms we found here, Rosie.apk was about 4Mo. Now in the Qtek 1.2 swap, it is only about 690Ko. Here, we can find a 330ko version.
But perhaps some people can do the same job to optimize all the UI of Rosie, i think about all the widgets ,the browser, the keyboard ...
The more lighter UI Rosie is, the less memory Rosie need ?
Scargoll.

I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...

MarcoNieddu said:
I did that but it's not finish yet. i just use a png optimizer so i can make every apk a bit smaller but my problem is that i don't really know how to sign an .apk file
when i know how to do that will have an fully working hero rom with compcache about 60 mb ...
Click to expand...
Click to collapse
Good news !!!
I don't know how to sign apk files, but i found this, perhaps this can help ?
http://www.anddev.org/signing_your_apk-application_for_release_keytooljarsigner-t3069.html
Scargoll.

I follow this tutorial more than 3 times now. when i want to install the signed apk to my phone there ist always an error -- > can't install ...

You're trying to install an app that's already running. You need to flash it with an update.zip+script or copy it with ADB when your device is in fastboot.
Ill see if I can optimize rosie's images, I brought down the HTC_IME size down by 25% just by optimizing the png images.
Sizes of the IMAGES in rosie.apk, not total size.
141 KB smaller than the original. Good result if I say so myself!

bump.
No one wants to continue? I'll optimize any image I can find and reduce the size of all images by 20% as well ending up with a probably faster running phone

Can you post directions on how to optimize???

A lot of people have already done some work trying to optimise Rosie. Speaking personally, the ne thing I always do when I install a new Hero build is to push the Rosie from
http://forum.xda-developers.com/showthread.php?t=532822
onto the phone. It's the stablest I've found that manages to do everything in a small-ish footprint without making it crash prone and buggy. There's a 300-odd K one in the same thread that I've never been able to get to work. There's also a 300-odd K one that came with Drizzy's 1.2 Hero release which was buggy - his next release took the file size back up to 3.5Mb!
tl;dr: there are already optimised Rosies, but not all of them work particularly well.

Has anyone been able to tweak the drivers to get slightly better fps or anything?

briggs81 said:
Has anyone been able to tweak the drivers to get slightly better fps or anything?
Click to expand...
Click to collapse
I wonder this too.

sibbor said:
I wonder this too.
Click to expand...
Click to collapse
My main phone is an HTC device running Android on sd card.. developers were able to get the fps to run up to 24, which is about 6-7 lower then a stock Magic.. not bad.. for a 2 year old phone!
Perhaps when other things are going smoothly someone with that type of knowledge will be able to play with driver software or something.
I think right now, Magic users get about 27-29 fps.

Battery Tweak Epic Edition RC1

Plans for next revision:
*Add in Decad3nce's temperature control
*Bug nullghost till he gets init scripts running so we can have this startup at boot
This is really a tool for power users
If you don't consider yourself 'comfortable' with messing with your phone, then don't.
This is mostly the work of collin_ph, all the ideas are mostly his and I have only contributed in part to getting some things functioning correctly and some optimizations for the Epic.
What does it do?
This tweak creates a service that periodically checks the phone's power source.
If the power source changes, it reconfigures the device for maximum performace, battery and safety.
Tweaks memory settings for current power source
Re-clocks CPU based upon battery remaining or current power source
Reclocks for maximum performance if on AC power
Reclocks for maximum performance and charging safety if on USB
Reclocks for performance and battery if on Battery
As Battery life is diminished, Maximum CPU frequency is lowered
Tweaks scaling charactaristics depending on power sourcee
CPU Scales up less frequently on battery power
CPU Scales up more frequently on USB/AC power
The CPU is allowed to scale dynamically in all charging states based upon CPU usage
Includes a batt-cfg utility to configure the system
You may load 1 of 3 pre built profiles
Manually configure CPU Frequencies in all charging states
Determine the percentage of underclocking as the battery drains
Configure how often to poll the power state / battery statys
Disable batt.sh service from running at startup
Includes a batt-rm.sh uninstall utility
Includes a batt-diag diagnostic utility
Includes optional Disk performance tweaks (enabled by default)
The Tools
The entire 'application' is written in shell code and was first written just to give a performance and battery boost, but since has evolved more and more.
All the tools mentioned will be utilized either through the terminal, or in adb shell.
batt.sh
This is the core of the entire script. Don't mess with it.
The one thing you should do after installing the script:
Code:
Code:
pidof batt.sh
If theres any number showing up after it, then it's working fine.
batt-cfg
This is the 'main menu' of sorts, as it gives the user all the options and allows them to toggle tweaks/mods on the fly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
batt-diag
It's a diagnostics utility, allowing you or someone knowledgeable to figure out any issues that you may be having with your device and be able to pinpoint exactly where the problem is.
batt-diag -v gives a more thorough output as you can see here; http://pastie.org/1162034
batt-rm.sh
It's a battery tweak removal script, follow the onscreen prompts and it should remove just about any trace of the battery tweak script.
The Presets
The presets are just default configurations that I have set up that can make your phone more efficient without you, the user, having to manually set everything.
The preset of 800 literally means that 800000 is the scaling_max_freq, or the max frequency, that your phone can achieve after you enable it.
Just typing 1, and then enter, you'll be ready and set to go. Same with 2 or 3.
Customize Settings
This is only for the experienced user, and it allows you to manipulate most/ifnotall the configurables on your device.
Note, you do not need to configure anything to enable this battery mod. Default settings will be assigned at 800MHz.
All the settings explain what each option does, so read them carefully.
Disk Boost
Remounts via noatime and nodiratime. Look up what that means on your own, and why it benefits performance the way it does.
Prerequisites needed to run this
Phoenix kernel 1.48 with Epic Experience should run this just fine
If you're running any other kind of rom, feel free to try it but i cannot guarantee that it will work.
This script will WORK even if you don't have the import call at boot, but it won't survive on the next reboot.
You can check via:
Code:
Code:
pidof batt.sh
NOTE: This script will also prompt you to try to run itself as root if you use it in terminal.
Contributors:
Collin_ph
Decad3nce
myn
onicrom
shabbypenguin
nullghost (aka tehdarkknight)
*make sure you are running these as root*
*disable setcpu while running this*
*been reported as rom manager fc's after batt tweak, simple fix reinstall rom manager* - thanks for the tip Raiderep

Finally got that working

This is perfect. As a former hero user, I was thinking to myself a couple days ago "I wonder if anyone is going to port the collin_ph battery tweak," and here it is.
Thanks!

I'm about to head into work and I got this downloaded. I'll put it to the test for the day. Thanx for the port or whatever you call it, I had this on hero and loved being able to get rid of setcpu(which I never really liked) but still have something governing battery use

Is this compatible or even needed with the mix up kernel?

compatible? maybe as i said this is known working on phoenix kernel as for others i cannot say. needed? well that depends are you happy with your current battery life?

Using Phoenix kernel 1.48 with Epic Experience bogged down my phone after installing, im only at 76% battery life, i cant imagine how slow it would be at 20%
edit:
its fine now, i guess it had to load initially?

Whats the best settings you think we should run..for the best battery life

800mhz or you can use configure to keep that even lower... obviously the lower the cpu freq the less voltage it uses = better battery life

I just set this up to the 800mhz defaults. I will come back with results

How does this govern cpu clocking and usage? I'm assuming there's no live governer such as ondemand or interactive at play here?

phoenix 1.48 has a working interactive governor

shabbypenguin said:
compatible? maybe as i said this is known working on phoenix kernel as for others i cannot say. needed? well that depends are you happy with your current battery life?
Click to expand...
Click to collapse
I don't think anybody is That being said, great work shabby, can't wait til nullghost gets his init scripts working.

shabbypenguin said:
phoenix 1.48 has a working interactive governor
Click to expand...
Click to collapse
So how does this affect setcpu? I'm runnin baked 1.3 ghz kernel..does this mean after I install I won't be at 1.3?
Sent from my SPH-D700 using Tapatalk

this is set for 800/1ghz/1.2ghz i included the configure option so people can make teh .conf however they see fit.. if batt.sh runs on it then it will scale from 1.3ghz after you configure it. witht he beta versions i dont believe anyone got it working on baked snack but if you try please let me know if it works what doesnt etc etc

when i try to run batt.sh i get this message...Mount: cant find /mnt/sdcard in /proc/mounts..what does this mean

its an issue im trying to figure out, batt.sh works fine without it, thats part of the disk speedups, in batt-cfg you can disable it

new feature will update tomorrow

not sure why but shootme is screwy for me recently as you can see. i have 0% tws, 37% voice calls at 30 mins 29s display is on for over an hour. screen is at auto, 3g, drm services RUNNING. oh yea im at 1.2ghz

Still have problems with this tweak...this is wat iam getting when I do batt-cfg I hit number one and I get this....
Loading 800mhz default
[: Bad number
Save settings...
Settings saved
Starting batt.sh
Note: when you exit ADB or terminal, you may have to hit
CTRL-C
Then my phone freezes and I have to pull the battery
Sent from my SPH-D700 using Tapatalk

[ROM][7/7/11] Virtuous Doubleshot v1.0.1 :: Sense 3.0 Espresso (Base 1.01.531.1)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doubleshot
Virtuous Doubleshot is a port of the ROM from the MyTouch 4G Slide, which features a custom version of Sense 3.0. It is based on the final/official base (Doubleshot_TMOUS_1.01.531.1). The custom Sense variant featured in this ROM is called Espresso, which is quite different visually from standard Sense UI. Additionally, the MT4G Slide is a WVGA device, meaning no re-sizing was needed.
Click to expand...
Click to collapse
​
Features
Click to expand...
Click to collapse
Based on the official MyTouch 4G Slide shipping ROM (Doubleshot_TMOUS_1.01.531.1).
Native rotating Rosie (launcher) support. (DesireZ/G2 and MT4G only).
Ported for full functionality on each supported device.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Click to expand...
Click to collapse
Desire HD
Desire Z / T-Mobile G2
Porting Information and Credits
Click to expand...
Click to collapse
Virtuous Doubleshot, or any components therein, may not be ported to other devices without explicit email approval from the development team. We will be approving ports, presuming the develop of a given port is ready and willing to follow the same revision control and release processes currently employed existing devices.
Important Notes
Click to expand...
Click to collapse
For Vision users, the DesireZ hboot is REQUIRED. I have written a guide for G2 users who need to make this transition.
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Disconnect your USB cable prior to the first boot, otherwise the Market apps do not install. This is because the default USB connection mode is "Disk Drive". We will resolve this issue in a future release.
Download ROM (305MB)​​​
Click to expand...
Click to collapse
(Please remember to hit the "Thanks" button if you download the ROM)​

Changelog:
Click to expand...
Click to collapse
Code:
v.1.0.1:
- Initial release
Introduction to the new Overclocking Daemon
Click to expand...
Click to collapse
This ROM features a completely new way of Overclocking and managing screen states.
The History
But before explaining it further, let's talk about previous solutions.
There are several different approaches to archieve "screen-state-scaling".
That means basically that the govenor changes if you turn the screen off and changes back to normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
App like SetCPU, which change automatically the govenor based on profiles
integrated solutions in the govenor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the govenors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass govenor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
This could be a really nice solution but it has some problems too.
Smartass most of the time is not really stable and has problems with its frequency scaling.
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the govenors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are plaing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
How to adjust the daemon
Click to expand...
Click to collapse
The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
There are 3 files for the wake state and 3 for the sleep state. For each state one file for the govenor, one for the minimal frequency and one for the maximal frequency.
You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the govenor for each state just like with SetCPU.
In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
You could also use adb shell to show the frequencies on your computer.
To get the available govenors use a similar approach:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Please make sure, you are entering the right values in the daemon's config files.

reserved #2

looks gr8!

Another new rom? Interisting...
Mdeejay rules..
Sent from my Desire HD using XDA App

Great rom !
But newest RUU for Doubleshot: Doubleshot TMOUS 1.28.531.8 (I can't deodex )

dungphp said:
Great rom !
But newest RUU for Doubleshot: Doubleshot TMOUS 1.28.531.8 (I can't deodex )
Click to expand...
Click to collapse
next release based on this RUU (i can )

This is what I am looking for, Native landscape mode. Thank you Mdeejay
Small doubt, Which format should I use for the partitions? Ext3 or Ext4?
Sent from my Desire HD

Which Radio is recommended? Multilanguage?

reserved

Weeeeee!!! Notha rom. Flashing immediatly. Which radio recomended? Which partition?

Downloading)))( I hope on this rom srs&dm will work )
egorgoblin, i think it like's on unity (automatically change your patritions to ext4)
_______________________________________________
Sorry for my bad English))

Reserved

Sick S,
I guess yeah. I really hope thow its recomended with a latest 26.10.04.03_M radio, 26.09.04.11_M2 sucked for me((

Trying this out in a few minutes Downloading now!

Holy crap, this is nice
I´ve been waiting for something like this.. Now I can use sense launcher again.
have had to use ADW to get rotating homescreen, and the 5 shortcut dock..
Flashing this right away.. Great work mate.. Cudos to you
Do you wan´t any feedback or reprots on bug´s and such??
Cheers..
EDIT: Isn´t there any MD5 ??

Tried. Indeed it's a decent ROM and seems lighter than Virtuous Unity. The only thing is that I like to change pcs density to 200. The only ROM works best is Virtuous unity. Only have very mionor gap in phone pad. No problem on unlock screen dialpad. Hope this ROM can eventually support 200 density.
Sent from my Inspire 4G using XDA Premium App

What kernel is in this?? Can we use any of the sense 3 compatible kernel´s??
Cheers..

MD5 106B94C9FA045A4BE7D20B765D2D12AB
baltazar.nilsson, i have installed unity v3 on this rom, works fine.

dungphp said:
Great rom !
But newest RUU for Doubleshot: Doubleshot TMOUS 1.28.531.8 (I can't deodex )
Click to expand...
Click to collapse
We're already all over it.

[APP] tegrak 2nd Core [ Enable Both Cores ]

ALL CREDITS TO ::::::: tegrak :::::::
**SAMSUNG GALAXY NOTE** NOW SUPPORTED
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can set the CPU cores as dynamic hotplug mode, single core mode or fully dual core mode.
This provides easy and simple way to use.
[ Features ]
*Set on boot
Change mode what you selected automatically on boot time.
Menu > Settings
[ Modes ]
*Dynamic Hotplug Mode
Default. Recently, mobile multicore CPUs turn off extra core(s) to save battery life when system is not busy and only use 1 core.
They turn on extra core(s) when system is busy. so system use all cores again.
*Single Core Mode
Use 1 core always. A extra core is shut down. It makes battery life longer but performance is decreased. [ Battery saving, Idle mode, Phone not in use ]
*Dual Core Mode
Use 2 cores always. Performance is increased but battery life is shorter than others. [Example : Zip or Rar Extraction, Photo Editing App Fast Load ]
*Available kernels
- FM Kernel 1.5
- Abyss Kernel 3.1
- Tegrak Kernel Build 31 [ XXKL7]
- Tegrak Kernel Build 31 [XXKL8]
Download ::
Android Market
See more details.
http://tegrak2x.blogspot.com/2011/11/2nd-core.html
**** Kernel Developers ****
If you add support for tegrak's 2nd core, please update or post here so that i can update the kernel support.

Also please let me know here, if the app has helped you in any way, did it make your phone fly away or ... ???

tids2k said:
Also please let me know here, if the app has helped you in any way, did it make your phone fly away or ... ???
Click to expand...
Click to collapse
My Note is flying anyway...
So, i have seen this application and i have a question...What's the meaning of this??I mean...The only reason i can find it usefull is the one core mode that it can battery.But why someone to enable 2 cores all the time??The cores is auto enable when something ''heavy'' running in our device.Why to enable it when otherwise?
If i am wrong please light me up...
Anyway, thank u @tids2k for sharing.You are our researcher...

eliashadow said:
My Note is flying anyway...
So, i have seen this application and i have a question...What's the meaning of this??I mean...The only reason i can find it usefull is the one core mode that it can battery.But why someone to enable 2 cores all the time??The cores is auto enable when something ''heavy'' running in our device.Why to enable it when otherwise?
If i am wrong please light me up...
Anyway, thank u @tids2k for sharing.You are our researcher...
Click to expand...
Click to collapse
Benchmark testing, mostly, though it also adds a little "pop" to application launching and UI performance in some situations.

Examples updated

User Comment on Android Market:
And theoretically 2 cores are more efficient than 1 due to both running at a lower clocked speed than it would with 1 core.
Click to expand...
Click to collapse
At first I was thinking "right whatever mate" - but then I started thinking ... maybe bad idea?
Are there scenarios where this might be true? I'm not sure of by what order of magnitude power consumption goes up by when increasing clocks but I seem to recall my WinMo phone Xscales had an expoential increase - specifically doubling the speed of the processor quadrupled the power consumption. This could be complete garbage btw, it was a long time ago and everything, and have no bearing at all on ARM processors.

diji1 said:
User Comment on Android Market:
At first I was thinking "right whatever mate" - but then I started thinking ... maybe bad idea?
Click to expand...
Click to collapse
The poster of that comment is simultaneous right and wrong.
If you have a multi-threaded app, it may well run faster and use less power by running two cores at a lower speed. However, for a single threaded app or task, a 2nd core is *never* going to be used, so it would just run slower.
The 2nd Core app is quite clear that running 2 cores all the time is going to hose your battery. However, if you are multitasking many apps, running just 1 core all the time will likely mean that that core has to run at a higher clockspeed all the time in order to cope with demand, and could also hose the battery.
Regards,
Dave

foxmeister said:
The poster of that comment is simultaneous right and wrong.
If you have a multi-threaded app, it may well run faster and use less power by running two cores at a lower speed. However, for a single threaded app or task, a 2nd core is *never* going to be used, so it would just run slower.
The 2nd Core app is quite clear that running 2 cores all the time is going to hose your battery. However, if you are multitasking many apps, running just 1 core all the time will likely mean that that core has to run at a higher clockspeed all the time in order to cope with demand, and could also hose the battery.
Regards,
Dave
Click to expand...
Click to collapse
So to be short, we do not need it?

tids2k said:
(...)
*Available kernels
- FM Kernel 1.5
- Abyss Kernel 3.1
- Tegrak Kernel Build 31 [ XXKL7]
- Tegrak Kernel Build 31 [XXKL8]
(...)
Click to expand...
Click to collapse
What does that mean? FM Kernel and Abyss Kernel 3.1 are not supported because of the red color?
Or are these kernels supported?
I'm just asking because of
angelom said:
Yes, but there is no module to run Tegrak overclock
Click to expand...
Click to collapse

robertberma said:
So to be short, we do not need it?
Click to expand...
Click to collapse
I gather that is the case from Dave's reply.
The thing is I hardly ever get below 50% during a days use (gotta love that Note battery!) so I'm looking forward to seeing what this does. I have the juice to consider it worthwhile.

I've been on it for a week and phone is flying fast. Battery drain is not that bad for me. I for one, love it
From the Best : Galaxy Note

Great App
My note is super fast now and battery drain is less along with juice defender...
Fantastic app...keep it up mate
Try to make the home button awake lag less with this app if you can...only request...

Thanks! !!!!

I want to purchase tegrak ultimate, but I receive this error:

Anyone know if the second core will go off when the screen is off when set in dual core mode?
Sent from my GT-N7000 using XDA App

It will remain on until you put the device in hotplug mode.
Sent from my GT-N7000 using xda premium

The device itself is working fine and great, not much of anything needed, not offense to any, but i like it the way it is , might be when we get ICS, we may have some core mod needed.

deadlyheart4u said:
The device itself is working fine and great, not much of anything needed, not offense to any, but i like it the way it is , might be when we get ICS, we may have some core mod needed.
Click to expand...
Click to collapse
Yeah...shame 2nd core doesn't work on ICS yet.

Roukie said:
Yeah...shame 2nd core doesn't work on ICS yet.
Click to expand...
Click to collapse
Damn, my ICS Note uses 1 core 1200mhz yet its way smoother than Gingerbread builds with dual core 1400mhz.
/Amazed

Is this compatible with ICS? I am on ICS Stunner.

Rom and kernel interaction

Op=noob
After the long and descriptive intro,
I wanted to know whether kernels effect the use of a phone, based on what rom is used.
In other words would one kernel have the same effect on skyrocketeer, that it would on sky ice?
I don't mean the extent of the effects (such as power saving), i mean the effect itself. As in "this kernel is smoother"
What I am looking for is a kernel to be used with sky ice, that gives more battery life with smoother scrolling than stock (if i can have both, if not, just more battery life)
This android world is hard to take in all together, back when I was a sheep, it was so easy. It was baseband and firmware. Now it seems to have roms, kernels, radios, patches...
Freedom is so complex, and the manufacturers don't help much.

I'm using sky ice with da_G's .3 over clock kernel as it never had the sod problem the rest of the kernels had. I like it far better than the stockish kernel or the faux kernel. Very smooth I use system tuner to set CPU to 918 and under clock 100mV during the day when I am just checking text and light using and when I go to using it I set it to 1.5 and voltage back to normal. So far I have no lag when clocked back up it scores 7600 on antu benchmark (no cheating it). I tend to get around
12 to 14 hours moderate to heavy use, meaning like 4 to 5 hours screen on time cruising these forums, Web browsing some gaming and phone calls hope this works for you
Sent from my SAMSUNG-SGH-I727 using XDA App

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Few screen shots still 45 percent to go with 2 1/2 hours of screen on time rain day here at work so I've been on it pretty much all morning
Sent from my SAMSUNG-SGH-I727 using XDA App

I have a question about this as well. Say I have Sky Ice right now, if install Da_G's kernel will it affect my rom or cause errors? Or does it just overwrite the old one and still work smooth? Sorry for the noob question, I figured I may as well learn something trying to get my 10 posts in.

If you flash a kernel, it will override the default one. Each kernel reacts with each from differently, although da g has the fastest but with errors on sky speed for me... so I use faux123 which comes with it.

Ah okay, yeah I guess I will stay with Faux's then. Thanks.

Thanks for all your replies,
It seems that no one really spoke about my first question:
I'll try to rephrase,
Does a powersaver (or smoother) kernel, tend to save power on all roms?
Or does it do so with some roms, and not effect others

Should do the same.
kernel=HARDware
Regardless of the ROM the kernel controls the hardware equally throughout any ROM. for example, the kernel is what communicates with the CPU and tells it, "hey slacka** get off 192MHz we need more power over here, krank it up to 800Mhz (or more depending on load)" than when the CPU load goes down the kernel tells it to calm it's nips and go back to 192 gradually decreasing until it reaches 192. ex. 800>628>420>356>192 etc. the rom in no way controls the clocks. hell, the kernel is what CWM runs on. you know the first SAMSUNG logo you see when you boot up the device? thats the equivalent to the BIOS Post, and the second screen you see before the boot animation? that's the kernel man. the kernel THEN tells the phone to boot your ROM. Badass ey? than the boot animation is a file in the ROM that the kernel renders using the kernels display drivers. while behind that boot animation the kernel is actually loading the ROMS files (which are located in the phones 2GB system partition) onto the RAM. a ROM is just a set of XMLs and PNGs and files and apps and drivers that the kernel runs.
THEREFORE, Regardless of ROM, the kernel has the same effect, and if the kernel has known issues, than the same issues too. *cough cough SOD cough*
ROM=SOFTware
which runs ON the HARDware that is dictated and enslaved by the Kernel
and here's some humor

Another factor is the build prop and what tweaks have been applied. Makes a huge different for everything from scrolling to battery life. Some prop mods have negative effects with diff kernels ect. Look in to it and play around what works best for you. Just make sure you back it up before messing just in case

M0D1441 said:
Should do the same.
kernel=HARDware
Regardless of the ROM the kernel controls the hardware equally throughout any ROM. for example, the kernel is what communicates with the CPU and tells it, "hey slacka** get off 192MHz we need more power over here, krank it up to 800Mhz (or more depending on load)" than when the CPU load goes down the kernel tells it to calm it's nips and go back to 192 gradually decreasing until it reaches 192. ex. 800>628>420>356>192 etc. the rom in no way controls the clocks. hell, the kernel is what CWM runs on. you know the first SAMSUNG logo you see when you boot up the device? thats the equivalent to the BIOS Post, and the second screen you see before the boot animation? that's the kernel man. the kernel THEN tells the phone to boot your ROM. Badass ey? than the boot animation is a file in the ROM that the kernel renders using the kernels display drivers. while behind that boot animation the kernel is actually loading the ROMS files (which are located in the phones 2GB system partition) onto the RAM. a ROM is just a set of XMLs and PNGs and files and apps and drivers that the kernel runs.
THEREFORE, Regardless of ROM, the kernel has the same effect, and if the kernel has known issues, than the same issues too. *cough cough SOD cough*
ROM=SOFTware
which runs ON the HARDware that is dictated and enslaved by the Kernel
and here's some humor
Click to expand...
Click to collapse
Wow thanks man that was put so even a simpleton like myself could understand you rock threw some thanks your way.