Database Info

[KERNEL]Toast-godmode OC .29 kernel for DamageControl/based roms

Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.
This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.
UPDATE
6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.
Click to expand...
Click to collapse
I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.
Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.
*View attachment damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.
This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.
ALWAYS MAKE A NANDROID BEFORE FLASHING.
You Do Not Need A Partition On Your Sdcard For Overclocking
THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.
If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.

So does this mean we can get the real AOSP dialer on Damaged's ROM?

mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.

you rock
10 char

Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.

If anyone wants to know how to do this, follow this guide starting at Step 8.
Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.
PM me if you need help.

mattshaver said:
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
I dont mind, ask anything here. Its how we learn
But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.
To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.
EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.

i'm running ic3rom and in the process testing it out

jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.

ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help

I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)

schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.

schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.

Jus10o said:
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#

Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App

mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.

jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?

Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try

Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache

jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.

Collin_ph Battery Tweak RC1 for Cyanogen / Darch Froyo roms (possibly others)

UPDATE 8/24! Please go to the site and download the latest version RC1b which corrects 2 small bugs people have reported. It now sets the proper permissions on batt-diag so it runs, and it changes the way the program tries to SU so that you can choose to not have the program attempt to run SU if your rom has trouble running su from terminal;
---Original Below---
I decided to create a new forum for the latest battery tweak as so much has changed since the initial versions.
To get things started, I'll just say that collin_ph battery tweak is a collection of scripts designed to make the hero (for now) last longer on battery, run faster, and run better. The tweak includes CPU management, Battery Management, Disk Performance Boost, Scheduler Boost, LED Fix, Audio Quality boost and other features to improve the usability of your Hero.
Instructions: Go to http://www.primoweb.com/froyo to download the latest version and get the documentation.
Boot into recovery and flash the zip file.
After reboot, you may run batt-cfg from shell or terminal (Note, that the scripts will all request root access, so there's no longer a need to su before running them).
to run batt-cfg
go to terminal in the phone or use adb shell from your PC
once there, type
batt-cfg
It will pull up a menu of choices. For further info, see http://www.primoweb.com/froyo
You can load a 691 mhz default (most Cyanogen kernels now only support up to 691 mhz anyway), or, if you have an uncapped kernel, you can choose a 768 mhz setting. Note: Both settings actually run at 691 when on battery and only run higher when plugged in.
The basics of how the battery is extended is that this tweak causes your phone to scale down (to lower frequencies) faster and to scale up slower. In stock configuration, the cpu scales up when only under 70% load -- while part of this tweak causes it not to scale until it's at 95% load, avoiding unnecessary scaling and battery drain. A second (and arguably more important) feature, is that as the battery drains, it lowers the maxumum CPU frequency. So when you have 1% battery left, you may be running at 468mhz instead of 691. Another plus is that the phone runs in a "higher performance" mode while charging via AC, and another mode to make sure the phone is actually charging when connected bia USB, in addition to the settings mentioned above when the phone is on battery.The best part is that almost every parameter in the system is adjustable through terminal or adb shell using a program called batt-cfg -- just run it and you'll be presented with a menu of options.
I'm constantly updating the documentation, so please check back often as I'll update this thread until there's a final 3.0 version. We're already working on a 4.0 which will be available on the market. We'll post more info there as it happens at www.tweaktool.com
COMPATIBILITY NOTES:
This tweak only works with clockable kernels. A lot of ROMS have reclockable or overclockable kernels which should work. I recommend Froyo roms, but I have heard of the tweak running with 2.1 releases. The main incompatibility seems to be with the service startup-- on some roms, the service doesn't automatically start up.
to verify if your rom is compatible and that the tweak is working, reboot.
Then go to terminal or adb shell and type:
pidof batt.sh
if it returns a number, then the service is running. If not, you'll have to start it manually every time the phone reboots by going to terminal or adb shell and typing
batt-cfg
then choose the option to save and exit. This will manually start or restart the service. Note: if your rom does not start the service automatically, you'll have to do the above batt-cfg procedure after EVERY boot or battery tweak will not run.
If you're a ROM developer, you'll can probably make your ROM compatible by adjusting your rom (ramdisk) to call (import) /system/etc/init.local.rc from init.rc -- assuming your ROM has an overclockable kernel like fresh, darch, or others.
ROMS based on unclockable kernels like Damage Control, won't work without a kernel upgrade and may still not start the service automatically upon reboot.
Thanks to Decad3nce for testing and improving several parts of the battery tweak.

So to flash this tweak and have it working on the latest Froyo nightly, do we need to flash overclockfix.zip ??
I had to flash this fix almost with ever nightly, coz the frequency list would not show up when i need to customize tweak settings.

I was reading the documentation and saw the CFS tweaks are disabled by default. Will this correct the GPS issue that was on beta 10?
Froyo Hero to the rescue

Thank you for all your work on this, got 12 hrs on 50% today with beta 10 and Decad3nse #8, 768 pre-set, most time I've ever gotten outa my Hero. Flashed your RC1 (with Darch's RC1) about 45mn ago and used custom settings to jack-up the max to 768 across the board, min.s and intervals stock. Thank you for explaining the 768 pre-set is really 691! Gonna sit on what I've got for a day and then try w/ Darch's "fix" kernel. Hope I can keep the max on batt @ 768 'cause it seems to make my Hero more responsive/less laggy.

I was not able to use the batt-diag in adb shell. I'll report back tomorrow how the tests go.

What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?

it made my hero laggy!!!

ToxicToastKatz said:
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
Click to expand...
Click to collapse
Follow the uninstall steps form the documentation
How do I uninstall it?
adb shell
batt-rm.sh
Follow the prompts and the tweak will be uninstalled.
Click to expand...
Click to collapse
Then flash the new version, this is how I have been doing it.

Excellent tweak! Used it through Beta and now enjoying the RC. Well done!

wow.. the way things are going i don't think i am going to jump into a evo... i am loving my hero so much.... thank you for all your hard work..

OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand

8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"

imb951 said:
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
Click to expand...
Click to collapse
Thanks for the notes on batt-diag. I'll look into it and release a fix this evening. Thanks.

Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.

I'm getting the same root problem with 8/22 nightly.
Sent from my HERO200 using XDA App

Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.

collin_ph said:
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
Click to expand...
Click to collapse
I'm using my red dawn rom with a modded ramdisk to allow for the battery tweak. The beta 10 worked and even the rc1 asked for su and I said allow the the whoami just kept going and going. I uninstalled via ur instructions on ur site and flashed again and same results

RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.

zachslavin said:
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
Click to expand...
Click to collapse
Were you doing the updates through ADB or terminal? When would it hard lock up.. during save changes?

CFS Tweaks and Decad3nce Kernel
I understand from reading the Kernel info, that the CFS on this tweak needs to be disabled first....did you make CFS tweaks on by default? Arent we supposed to flash the kernel first, then disable cfs tweaks and reboot? Im confused as to the order in which things are flashed. WIPE, ROM, GSHITZ, BLACKMOD, KERNEL#7, COLLINS RC1. Then go to term EMU and disable CFS, then save then go back into batt-cfg and choose option 1 768 and save and exit then reboot. Woudl that be correct?

[KERNEL] Sense 2.6.32.24+BFS+HAVS+USB HOST+UVOC+CIFS+NFS+NTFS+TUN

Hello,
I have compiled my own version of the bravo froyo kernel, I have mixed the work of kingklick for the incredible and the work of snq- as the 2.2b-sdfix kernel, changing some defaults voltages and add the Sven Killg's usb-host support. I have also added NFS, tun/openvpn, NTFS, UTF-8 and some usb devices I need. This kernel supports HAVS, that is Hybrid AVS that adjust the CPU voltage based the hardware feedback. In my desire is working quite fine, have no time for battery testing but it seems good. More feedback is welcome!
I am still waiting for an USB OTG Cable, so I cannot test the USB-Host part, it should work without problem following the instructions at http://sven.killig.de/android/N1/2.2/usb_host/ but if you find any problem, report it here.
Changelog:
-gg1:
GPU Fix from snq- and change versioning scheme.
v0.3:
Major change, based on official bravo and mix several patches from different sources. Now the kernel version is 2.6.32.24 and includes lots of changes. BFS, HAVS and more from the kingklick incredible kernel.
v0.2:
Remove usb sound support and add tun.ko for openvpn.
v0.1
I have put back IPv6 support, only 100Kb more and Google Googles works again :-D
Of course thanks to snq-, kingklick, LeeDroid, Sven, Koush and everybody here doing such a great job!

Next step should be a kind of toggle for the usb host mode, something userfriendly...
Any chance for something like this?

Diamondback2010 said:
Next step should be a kind of toggle for the usb host mode, something userfriendly...
Any chance for something like this?
Click to expand...
Click to collapse
The problem is that as far as I know once you have the ehci-ucd module loaded the usb mode change, even if you unload it. Doing an app to load unload all the usb-modules should be trivial, once I get the usb-otg cable I'll try it. Maybe I will code some kind of no-gui just a menu switch-on switch-off app, but doing it blindly would not be very easy :-D
Regards,

with ipv6 removed, google goggles will no longer work. any reason why you removed it? just curious.

Does it work.in hd Rom ?

I flashed it, and it works fine (the usual stuff, that is).
I also went to the linked website, and followed the instructions (though some of it made not much sense).
Then i plugged it into my computer over usb and selected mount as storage, and it mounted - so it didnt work?
Which instructions are the ones we need to follow?
Josh.

w.0.o.t said:
with ipv6 removed, google goggles will no longer work. any reason why you removed it? just curious.
Click to expand...
Click to collapse
Trying to save some bytes, I've put it back as it is only 100Kb more :-D

fllash said:
I flashed it, and it works fine (the usual stuff, that is).
I also went to the linked website, and followed the instructions (though some of it made not much sense).
Then i plugged it into my computer over usb and selected mount as storage, and it mounted - so it didnt work?
Which instructions are the ones we need to follow?
Josh.
Click to expand...
Click to collapse
The instructions about usb host-mode you need a OTG cable and a powered usb hub and then using conectbot or adb through wireless you need to manually load the needed modules, they are all at /system/lib/modules. The minimum is usbcore.ko and ehci-hcd.ko but you will need others to do usefull things. I think that we will need to kill some htc process because it seems that it is accessing the usb in slave mode. Once I'll get the OTG cable I'll try to get further, but right now the usb-host is just supported in the kernel, nothing else.
Regards

kahuna0k said:
Trying to save some bytes, I've put it back as it is only 100Kb more :-D
Click to expand...
Click to collapse
thanks very much. i'm flashing the new one in a minute.

Hy , thanks for u'r work, one more thing can u add support for open-vpn? i flashed u'r kernel but openvpn aint working anymore
thanks

tun module not work,please check

miyu-hitori said:
tun module not work,please check
Click to expand...
Click to collapse
littlej said:
Hy , thanks for u'r work, one more thing can u add support for open-vpn? i flashed u'r kernel but openvpn aint working anymore
thanks
Click to expand...
Click to collapse
new version with tun.ko included

Thank you for very good kernel, but WiFi n?

New version including the snq- gpu fix

kahuna0k said:
New version including the snq- gpu fix
Click to expand...
Click to collapse
so this has BFS scheduler? and does it include the SD read ahead fix?

Hmmm...
I've flashed the kernel but I got an error message when I tried to execute insmod ... ehci-hcd.ko, for the usbcore.ko was ok...
The error says something like "Device or resource busy".
Using Modaco R9 with Sub501 mods (CIFS, Undervolt, CFQ IO Scheduler, Custom governor), baked directly from the Modaco online kitchen.
I really need a help to solve this.
Thank you all!

a question: is bluetooth hid working with this kernel ??

Thanks for this, I LOVE a good kernel for my phone! This feels really nice, not sure if it'll beat out Ziggy's as my favourite but after a few hours I'm loving it!
I'll check back with battery life stats after a day at work

Skilling said:
Hmmm...
I've flashed the kernel but I got an error message when I tried to execute insmod ... ehci-hcd.ko, for the usbcore.ko was ok...
The error says something like "Device or resource busy".
Using Modaco R9 with Sub501 mods (CIFS, Undervolt, CFQ IO Scheduler, Custom governor), baked directly from the Modaco online kitchen.
I really need a help to solve this.
Thank you all!
Click to expand...
Click to collapse
I have the same problem. Please help!!!

[App BETA][Updated 10.17.11]viperMOD Voltage Control (post only if you are a tester!)

This is going to be the thread for everyone to post in when they are testing the app, regardless of device. Please only post in this thread if you are a tester to minimize on clutter.
Ok guys, I have a test version of the app ready and I need some testers! This app was put together by Smurph82 (Ben), me (Derek), and another friend of mine (Will) with Ben doing the majority of the coding. If Smurph82 asks you anything, ANSWER HIM! He is the guy who will get this fixed! Please bear with us as we get the bugs worked out and get this to be the best voltage control app out there!
Some things don't work and I need help figuring out what else isn't working. I'm looking for 2-3 testers for devices I don't officially support right now. (check the list in my sig of officially supported devices and make sure you're applying to beta test for a device not listed there) All testers will get the paid version of the app when done, assuming you provide me with feedback of this app. Here are a few rules...
0.) You must be on a HAVS/SVS kernel (exceptions Nexus S/NS4G with mathkid or Netarchy kernel). If you don't know what this means, please do not send me a request to beta test. You must also be on a ROM that supports init.d (99% of ROMs)
1.) If you are selected to be a tester, you WILL NOT send this app to anyone else and you will use it only on your personal devices.
2.) If you are not selected to be a tester, please don't blow up my PMs or thread complaining about it.
3.) You will provide me with some feedback about the app, what works and what doesn't, what should be implemented and/or taken out. I don't think this is an unreasonable request.
4.) To be an official beta tester, your submissions will BY PM ONLY. This information needs to be sent to me or I will ignore your PM. I don't have time to respond and ask for the information that I need. Please don't post in this thread for wanting to test, this thread is for the testers to post their results and collaborate with one another. Please include this with your beta testing submission:
Device:
ROM:
Kernel:
Please also keep replying with our whole conversation so I can reference it.
5.) I may be going to bed soon so if you get nothing from me tonight, I will hit you up tomorrow.
Thanks guys, I look forward to working with all of my beta testers!!
Known Issues:
[*]Landscape in 2nd tab doesn't scroll
Some voltages presets need to be implemented
Links are too small
[*]Netarchy kernel detection shows UNKNOWN
Shouldn't show init.d button if one doesn't exist
[*]App looks in the wrong place for SVS kernel voltages
Cannot save init.d file

Alright, I've run into one problem right off the bat but I think it will be easy to solve.
It says:
"File at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs was not found
My frequency tables are at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
I know it will work, I've been using the vipermod terminal script to change my voltages, it just can't find my frequency tables it seems.
EDIT: i messed up the file path for my tables (left out the /cp0) fixed now.

I am also getting the same issue of:
File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: HTC EVO 4G
KERNEL: TIAMAT 3.3.7

Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read

File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: NEXUS ONE
KERNEL: IR 2.6.38.8_AVS-CM7_CFS_20110813_1517

Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!

yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.

-viperboy- said:
Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!
Click to expand...
Click to collapse
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..

ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.

Jake33108 said:
yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.
Click to expand...
Click to collapse
Please explain a little bit further. It sees its an SVS kernel, then what happens? Can't create the voltages?
saryu said:
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..
Click to expand...
Click to collapse
OK, no Netarchy/mathkid kernels show up as unknown. Thanks for the info.
ropodope said:
ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.
Click to expand...
Click to collapse
Well, it shouldn't install one for the user, it should just error. We don't want to set a bad voltage that is too low for your phone or anything!
The links are an easy fix, thanks for the input.
And as far as setting too low of a voltage, that's because it doesn't write the init.d file yet. You could still end up with the same problem as the script if you set a voltage too low and saved it. And it shouldn't have changed anything like that at all. Could you explain how it changed your CPU settings??

Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Just out of curiosity does this require root privileges maybe? Because I never got a SU request for it.

Jake33108 said:
Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Click to expand...
Click to collapse
Ok, small oversight on that. Thanks much!

naf007 said:
Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read
Click to expand...
Click to collapse
If the app does not detect the HAVS file correctly it will not allow you to update as it would be have not files.

I know that viperBoy requested your specs for being a beta tester
but please provide me with your phone, ROM, and Kernel in your post so I can
better understand your problem. This was built on an Evo 4g, CM7, Tiamat 4.0.*. Thanks.
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs is the path that I knew development on my platform. I am working on this.

Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Click to expand...
Click to collapse
It does detect that its a SVS on the main page
I deleted my file that I created with the script and tried to generate a new one but no change
HTC DESIRE
MIUI 1.8.12 DEXT XPART
Stock Kernel SVS [email protected] 2.6.37

I don't have an example of the /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
can someone please post me one thanks. Sorry the svs had not been implentment due to the fact that I only have one phone.

I'm restoring a backup right now, I'll post mine in just a second.

sure. i set the voltages too low on purpose in order to cause my phone to lock so that i would have to do a battery pull because i was curious to see if my kernel voltage defaults would be restored on reboot....and they were. i think that is great. i then reset them using the app to where i knew my phone would handle them. after doing so i took a look at my custom cpu settings which i have set to retain on reboot. when i did they were completely changed from 128/499 smartass to 245/998 (stock settings) along with the governor being changed to interactive. i just thought that was weird.
also the tapatalk app is not allowing me to reply to this thread. it keeps saying "failed to connect to forum. please check with the forum administrator if this problem persists". i have to reply from my laptop.
ropodope
499mhz is the new 998mhz.

Here's my file. All of my build info is in my sig.

Jake33108 said:
Here's my file. All of my build info is in my sig.
Click to expand...
Click to collapse
Thanks I will be working on this.

[KERNEL] Chacha kernel 2.6.35.14 by Tokafondo.

Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.

tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Click to expand...
Click to collapse
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?

mohabmoka said:
very very good mate ! , but how can i flash it? from fastboot or ? , and what about swap tested? on stock rom?
Click to expand...
Click to collapse
Yes, you will have to flash it by using fastboot:
(remember to have a cwm backup just in case you want to reflash your original boot partition)
Code:
fastboot flash boot bootv6initd.img
Swap partition goes as second partition of SD card. Swapper2 will work to format it as 'swap' type.

hm, happy to see still chacha development is active....did anyone tested it?

eager
ajeevlal said:
hm, happy to see still chacha development is active....did anyone tested it?
Click to expand...
Click to collapse
I'm eager to try it but I just love your port man, I will get a new phone in march so I will have the time to test more things on my chacha

hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)

nice
ajeevlal said:
hm i tried to build kitkat but it didnt work and it needs more knowledge than what i have.... and if we can keep the kernal up to date, may be some issues in custom rom might get fixed (HOPE)
Click to expand...
Click to collapse
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom

swashie said:
keep it up mate, kitkat cannot beat you! j/k Jelly Bean is already an amazing rom
Click to expand...
Click to collapse
you could do it man !!

tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!

kronflux said:
tokafondo, I haven't really taken a look at your kernel yet, but I recommend you take a look at the OWL project kernel, as well as Luzifer1984's forks. Might help you gain some insights into rom features and functionality for the future.
honestly, I'm really surprised nobody has forked OWL project's stuff and compiled all of it for the ChaCha yet. They even have an updated ClockworkMod, which if compiled correctly, should work with our device.
Seems their 10.1 roms are also stable, and most if not all features of the device work.
here's the link to their kernel: https://github.com/JDevs/OWL-Predator-KERNEL
and here's Luzifer's github page: https://github.com/Luzifer1984?tab=repositories
there's also Adlx's stuff, which has been very successful so far: https://github.com/adumont/htc-kernel-msm7227/
I'd really love to see a decent, fully stable, feature rich kernel with great battery life for the ChaCha.
As I said, I haven't tried yours out yet, but will definitely give it a look in the next few days!
Click to expand...
Click to collapse
Thanks. I'm not that into the trying to port or get things to be done in ChaCha for fun. I don't see the benefit of having the latest version of Android working just because I could be done. 2.3.5 and Sense does the trick and allows me to work with my phone.
I would like to have some external reports of success or failure with my kernel. I did it for myself but though others could also benefit from it -- if there is a benefit at all.

kernel tested - no WiFi
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.

johan111 said:
I have tested your kernel and found WiFi error. This prevents WiFi activation. I tried with this ROM http://forum.xda-developers.com/showthread.php?t=1644087 and with this one http://forum.xda-developers.com/showthread.php?t=1690088.
Click to expand...
Click to collapse
My mistake!!! :silly:
You have to copy the modules included in the attached zip file to
Code:
/system/lib/modules
you should be able to connect to wifi after that.

I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
Click to expand...
Click to collapse
i cant file called sysinit in system/bin !! or i must create it and type the code inside it?

It's a text file you should create. Type in the code, set owner and permissions and you are done.

Custom Kernel Not Supporting on Chacha with Stock Rom (Rooted with Busybox)
tokafondo said:
Hello all. This is my own custom kernel.
I tailored it to work on stock roms.
I updated the sources (as my knowledge allows me to do it) up to 2.6.35.14.
I put there SWAP support (via a second partition on your SD card). You can enable it with Swapper2.
I also put init.d support. You *must* follow the step number 2 detailed in this guide: http://forum.xda-developers.com/showthread.php?t=2287540, as I already did step 1 for you.
EXT4 and NTFS support is there, too, in the case that you have a sdcard formatted in that file systems, but I haven't tested the NTFS features.
HTC Performance locks is disabled: you can underclock down to 19,2 khz if you want to.
Also, there are SmartAssV2 as default governor and Simple I/O as scheduler.
I hope I will soon be able to put undervolting there, or more CPU clocks for more choices of clock settings.
Comments, please, and enjoy!!
Edit:
You have to copy the files inside modules.zip to
Code:
/system/lib/modules
. Thanks to johan111 for pointing to this.
Click to expand...
Click to collapse
The moment I install the provided zip, and reboots, the phone becomes un-stable and the screen flickers constantly with the icons.
Android :2.3.3
Stock Chacha Sense 2.1 based on India: 1.20.720.1
Kernel: 2.6.35.
Any help !!