Database Info

[PATCH] CM Kernels 10MB-RH and NON-RH for King's SenseHybrid 2.3

Hey all, this is a patch that will change out the kernel for King's SenseHybrid 2.3. I use this rom pretty much daily. It is a cupcake based hero, just this update speeds up the performance a bit.
Instructions:
-Wipe everything!
-Install King's 2.3 SenseHybrid (Please follow his directions.)
http://forum.xda-developers.com/showthread.php?t=563294&highlight=SenseHybrid
- Flash this update immediately after flashing King's rom
- Reboot and enjoy!
ChangeLog:
Updates user.conf (if you don't like it, change it )
Virtual mem settings adjusted
proc_cpu_en=0 # to save battery life
Updates Kernel to CM 4.2.15.1
Removes:
Meebo
HeroLED
AKNotepad
teeter
Adds:
Free Advanced Task Manager (Useful)
****I just posted a 10MB ram hack version in the thread below. It uses CM 4.2.14.1 with CFS instead.****
If you like it, then great! I've been experimenting with using different kernels on different people's roms. I'm new to it, but if anyone has any tips, they are greatly appreciated.
Red.
PS. PLEASE DO NOT ASK ABOUT BT! IF YOU HAVE READ ANYTHING ON THIS SITE CONCERNING HERO ROMS ON A G1/DREAM THEN YOU WOULD KNOW BETTER AND WOULDN'T RISK BEING FLAMED.

Sounds good I was going to flash the sensehybrid soon anyways so this sounds perfect.

Wait a few minutes..
If you can hold off a bit, I am also making a 10MB ram hack version with CM 4.2.14.1 CFS. Just testing now.
Red.

CM 4.2.14.1 10MB Ram Hack with CFS
Here is another one that you can flash immediately after flashing king's 2.3. This uses the 4.2.14.1 CM kernel and the CFS 10MB ram hack. I absolutely hate BFS on G1/Dreams! Anyways, this one should run faster. I would also look into the thread that has been posted recently about speeding up hero roms and change the line in your init.rc to keep rosie in memory. just copy the init.rc onto your sdcard and edit it with notepad++ (windows program, it is great!) and then copy it back to your root over the existing init.rc and reboot. (if this is complicated, then don't try it.)
Otherwise, Enjoy!!

will this work without an ext/swap partition?

Without ext partition...
Honestly, if you are using the Death SPL and you are running this with my ram hack, you should be ok. Unfortunately, the compcache on King's earlier roms are usually broken. I tried pushing ramzswap from the CM kernel and still no luck, but then again, I'm not as savy as some of the other dev's out there. You will just have to edit the user.conf after you finish flashing the two, you want to do the following:
First, before flashing you want to pull the user.conf from the system/bin/ directory in king's zip file. edit the user.conf using notepad++ in windows and change the linuxswap=1 to 0 so that it turns it off. then copy that file to your sdcard.
immediately after flashing the two files,
-go to console from the recovery and type the following
mv /sdcard/user.conf /system/bin/
reboot
this will disable the linuxswap and then you will be able to run the rom. But again it would be better with a swap partition.
Hope this helps.
Red.

would prefer the WG kernel but okay thanks

protomanez said:
would prefer the WG kernel but okay thanks
Click to expand...
Click to collapse
Same here, WG is great. I tried the RH CFS patch, but I got an error while flashing it. Had to restore from switchrom.

where's the wg-kernel patch for 1.5 hero roms?
Also, does multitouch still work with THIS patch?

boot loop...

?
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.

Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.

Snacky-cakes
domex2k said:
Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.
Click to expand...
Click to collapse
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.

redd12345 said:
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.
Click to expand...
Click to collapse
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.

sync fix
domex2k said:
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.
Click to expand...
Click to collapse
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.

redd12345 said:
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.
Click to expand...
Click to collapse
Great i will give that i try Thank you

Suggestion
domex2k said:
Great i will give that i try Thank you
Click to expand...
Click to collapse
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.

redd12345 said:
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.
Click to expand...
Click to collapse
Thanks for the link. I will give it a try, because some reason when used the other 2 cm patches the camera and camcorder will FC and so i then just flashed this rom solo and it did not fc

multitouch?

redd12345 said:
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.
Click to expand...
Click to collapse
Sorry for being vague. I had everything right except ext3 instead of ext4. I'm looking for some directions on how to upgrade. If you have any please let me know, thanks.

[PATCH] WG Kernel with RamHack for King's 2.3

Hey all, there were requests for Wes' Kernel and the 10MB ramhack, so I thought I would try to entertain them. This will change out king's kernel in SenseHybrid 2.3 for Wes' 10MB RamHack kernel. This will also run 32MB of compcache on boot up, Swap partition is still required for A2SD. If you want to run a swap partition, I recommend EXT4 and to use Notepad++ (windows program for editing linux files) to change your /system/bin/user.conf
Now the fun part.
Instructions:
-Wipe everything! (This ONLY works from a fresh install!!!)
-Install King's 2.3 SenseHybrid (Please follow his directions.)
http://forum.xda-developers.com/showthread.php?t=563294
- Flash this update immediately after flashing King's rom (Do NOT reboot before you flash this patch!)
- Reboot and enjoy!
NOTE: PLEASE GIVE THIS SOME TIME TO BOOT AND TO SYNC. ALSO, DO NOT START SWIPING RIGHT AWAY AS THE PROGRAMS TAKE TIME TO LOAD. JUST LET IT SIT FOR A BIT AND BE PATIENT... Then it's pretty quick.
ChangeLog:
Updates user.conf (if you don't like it, change it )
Virtual mem settings adjusted
proc_cpu_en=0 # to save battery life
Updates Kernel to WG RamHack from latest Donut rom
Removes LinuxSwap in exchange for 32MB Compcache
Removes:
Meebo
HeroLED
AKNotepad
teeter
Adds:
Free Advanced Task Manager (Useful)
If you like it, then great! I've been experimenting with using different kernels on different people's roms. I'm new to it, but if anyone has any tips, they are greatly appreciated.
Red. (Testing out FireRat's 30MB ideas next... I just don't have a PHD in "Freakin' Awesome," so it's gonna take some time.)
PS. PLEASE DO NOT ASK ABOUT BT! IF YOU HAVE READ ANYTHING ON THIS SITE CONCERNING HERO ROMS ON A G1/DREAM THEN YOU WOULD KNOW BETTER AND WOULDN'T RISK BEING FLAMED.

Saved for any updates.
Reserving space.

The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense

G1ForFun said:
The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense
Click to expand...
Click to collapse
Didn't vega make a WG kernel already though for eris/legend?

Thanks.
G1ForFun said:
The link to the SenseHybrid thread doesn't work.
Also, you should try to work on hero 2.1 (new - DroidEris Legend ect) instead of hero 1.5 (old).
Correct Link
http://forum.xda-developers.com/showthread.php?t=563294&highlight=Sense
Click to expand...
Click to collapse
I updated the link in the initial post. Thank you. Other than that, I think there are plenty of good Dev's that are working on the 2.1 field. I am really new to this and do not have anywhere near the experience that they do. This was a request from another post that I had earlier. I like the 1.5 hero because of the almost full functionality (minus BT.) 2.1 is a great platform, but until the drivers are released, it is frustrating. I was beside myself when they were reverse engineered for the Camera app to be enabled. People here work really hard on these roms. In any event, I hope people will make use of this.
Red.

redd12345 said:
I updated the link in the initial post. Thank you. Other than that, I think there are plenty of good Dev's that are working on the 2.1 field. I am really new to this and do not have anywhere near the experience that they do. This was a request from another post that I had earlier. I like the 1.5 hero because of the almost full functionality (minus BT.) 2.1 is a great platform, but until the drivers are released, it is frustrating. I was beside myself when they were reverse engineered for the Camera app to be enabled. People here work really hard on these roms. In any event, I hope people will make use of this.
Red.
Click to expand...
Click to collapse
Well props to you on your work, I know people still use 1.5 sense I was just making a suggestion.

Lol.
G1ForFun said:
Well props to you on your work, I know people still use 1.5 sense I was just making a suggestion.
Click to expand...
Click to collapse
I'll get there someday. Everyone might be on a different phone by then, but I'll be in the game for a while. Thanks again!
Red.

I just flash_image'd the boot.img on my installation... What are the differences in doing that over flashing the entire zip?

xjjjay said:
I just flash_image'd the boot.img on my installation... What are the differences in doing that over flashing the entire zip?
Click to expand...
Click to collapse
Wifi, Adv. Task manager, swap, compcache, and their modified user.conf so not much

JAguirre1231 said:
Wifi, Adv. Task manager, swap, compcache, and their modified user.conf so not much
Click to expand...
Click to collapse
crap didn't notice wifi was broken -_-
Too lazy to sift through all the other changes this patch makes in order to get wg kernel... 2.3 is fast enough

Now that im using this kernel, when ppl call me their name/picture doesnt show up... its as if i dont have their number, when i really do. it even asks me if i want to store their number after the call... so for whatever reason it isnt recognizing my contacts when they call. it does recognize them when i get a text.

Issue?
chabsie said:
Now that im using this kernel, when ppl call me their name/picture doesnt show up... its as if i dont have their number, when i really do. it even asks me if i want to store their number after the call... so for whatever reason it isnt recognizing my contacts when they call. it does recognize them when i get a text.
Click to expand...
Click to collapse
I didn't have this issue when I ran trials, but I will try to reload. Are you using EXT4 partition? You may also want to try to re-sync your information in Settings/Data Syncronization. Also, I just want to make sure that you installed this patch from a fresh wipe and didn't flash it over the other patches that I made (I noticed you tried the CM ones as well.)
Let me know if either of these work or help.
Red.

yes im using ext4 and yes i flashed it over a fresh wipe. when i make a call, the contact is recognized as it should, its just incoming calls that dont work.
i just resynced contacts and that didnt make a difference for me.
side question: ive seen it mentioned in other threads that you should wipe davlik cache, battery stats, and rotate settings in addition to the factory reset wipe and repartitioning. how do you wipe those first 3?

chabsie said:
yes im using ext4 and yes i flashed it over a fresh wipe. when i make a call, the contact is recognized as it should, its just incoming calls that dont work.
i just resynced contacts and that didnt make a difference for me.
side question: ive seen it mentioned in other threads that you should wipe davlik cache, battery stats, and rotate settings in addition to the factory reset wipe and repartitioning. how do you wipe those first 3?
Click to expand...
Click to collapse
If you download Amon_ra's recovery and flash it, when you are in recovery mode, there will be an option under wipe. Still looking into camera issue.
Red.

I have problem with cam after flashing kernel.
Am i the only one whit this?

feenty said:
I have problem with cam after flashing kernel.
Am i the only one whit this?
Click to expand...
Click to collapse
No, you are not the only one with this issue. I flashed it two times after wipe. But the camera still broken.

[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.

[HELP] AOSP Froyo + HTC 2.6.29 kernel = no touch screen?

OK, here is the latest update. Instead of using kernel extracted from Rogers stock ROM, I compiled HTC kernel source downloaded from developer.htc.com.
To make touch screen work, one has to update sapphire_defconfig. Only one configuration has to be changed -- that is, to make the following unset.
#CONFIG_TOUCHSCREEN_CONCATENATE_REPORT=y
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Hopefully, the above information is useful. Wifi is fine. But, camera is not working.
==================================
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.

the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider

sharpt71 said:
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.
Click to expand...
Click to collapse
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
In regards to the 3.5mm headphone jack version (also known as Fender or 1.2) it has slightly different hardware drivers that require the patch made by Voxluna. Most developers include this in their roms by default however if you are using any other source then odds are that they won't include the patch thus creating your problem.

capychimp said:
the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider
Click to expand...
Click to collapse
Since HTC source code was just released, will you please point me to the right files/folders so that I can find out the reasons why .29 does NOT work with Froyo?
I had once compiled AOSP Froyo with HTC kernel .27 by following instructions on http://www.lingnu.com/en/howto/72-android-aosp-htc-32a.html. Although camera (and maybe other devices) did not work, touch screen worked fine. Due to this experience and the limited reading of android architecture, I thought I could simply replace the kernel without affecting other layers. Hmm, to use layers design, why didn't google keep APIs intact?

Binary100100 said:
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
Click to expand...
Click to collapse
Sorry for not making this clean in the first place. Mine is a 32A which is running Rogers stock rom with root (made by capychimp) + chinese support + htc_cime (cooked by myself).
Ciompilation involved roughly the follwings:
1. AOSP froyo branch 2.2_r1
2. Comppilation of Froyo by following http://xy0811.spaces.live.com/blog/cns!F8AECD2A067A6B17!1526.entry?wa=wsignin1.0&sa=474748515 (which is similar to dferreira's howto)
3. unziped capy's Rogers_21_capychimp.zip instead of signed-google_ion-ota-14721.zip.
4. extracted kernel and wlan.ko from the boot.img in Rogers_21_capychimp.zip

the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.

carz12 said:
the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.
Click to expand...
Click to collapse
Thanks for the info. I just updated the current status at the 1st post.
From what I did, I kind of wondering whether or not the not-working camera problem is related to "configurations" because camera works on 2.1. But, I am not a kernel guy and will not be one.

sharpt71 said:
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Click to expand...
Click to collapse
A screenshot of software information is attached. Oh, sdcard cannot be mounted unless it has no ext/swap partitions.

nice on the touch screen, will come in handy thx will try it on my wildfire port

New Purchase, best stable upgrade?

Hey all, buying an XT720 today.
Looking to get it up from 2.1
What is the most stable update at the moment?
I have done CM 6.1 on a HTC Dream, was pretty happy with it.. would like to get up to 2.3 on this..
Suggestions? I am using Wind Mobile in Canada for this phone if it makes a difference.
James

Hi
Their are choices cm6 is very stable
I would try flfalcon cm7.
Their are J.Y.Daddy cm7 these were made for the motorio to use these you would need to apply bootfix.
J.Y.Daddy even ported miui ics 4.01.
You need check out the development page.
Sent from my XT720 using xda premium

I also have a list of most of the ROMs and their +/-'s. Ill find the link and post it. I'm mobile now so can't find it that way.

Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works

Here is a somewhat dated list but a list nonetheless and here is the thread it came from.
http://forum.xda-developers.com/showthread.php?t=1298208
Woodrube said:
There are a host or ROMs for this phone right now and it is quite hard to narrow down to "The Best". Each as their own +/-'s and while one might be a monster in speed, it might have poor muti-tasking or bad camera. Here are some of the ROMs we have and some of the +/-'s they have (not all, just some +/-'s).
In no particular order other than the top came out first and bottom is the latest.
2.1 Stock - Came with the phone. You can falsh via RSDlite the sbf file for your region.
2.1 Stock~ESB (Eclair Strikes Back) - Same as above, but has aorking app2ext, camera, FM Radio. Still it is 2.1
Dexters 2.2 with MZ patch - First successful attempt to port 2.2 to our phones. All features of 2.2 but camera is sketch and FM radio doesn't work (unless you apply FJfalcon radio patch but then it is still loud), media button doesn't work.
Kahlpower's V2/3/4 - Optimized version of Dexters. Same issues as above but is more stable and generally was the choice as a "home" ROM for many users. I have my wife on this one as we speak. Low maintenance, a good everyday driver. Has App2ext/ Link2sd, native Froyo App2sd.
Cincinnati Bell's "official" 2.2 - More or less a glorified version of Dexters 2.2 but I think the Mioz7AE found a "listening" script that may or may not send info back to developer. I would stay away from this one. Plenty more to choose from.
Wanhu 2.2 (also Wanhu's Kahl's Optimized) - Korean port of 2.2. FM radio and camera does work. Number formatting is off. App2ext works fine as does native Froyo app2sd.
XDA Special/ Hellmonger Edition - This was moveing really well and then Hellmonger's phone crapped out on him and his carrier gave him an HTC Penache, so no more support for this one. But is DOES work and worth a try.
CM6 - our developer Mioze7Ae's masterpiece (for now until he moves on to something else) All the features of CM6, including themer. Has App2ext and Link2sd.
WIPs
Brianlili's Brovo 2.2 - This one is almost done, jsut a few little thing to finish it off.
JYDaddy's CM7 (nightly/ HoNo/ iceandfire...)
FJfalcon's CM7.1 (make massive progress daily on this one as it is being built from source).
Like I said there are +/-'s to each but the are all spelled out for you in the OP of each thread. Plus, unlike other phone forums, we actually answer your questions and dont respond with, "search".
Good luck and remember to always BACK UP.
Click to expand...
Click to collapse

S7icky said:
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Click to expand...
Click to collapse
Where is this Bravo??
Also I have rooted..
but I have not found a good guide on Openrecovery. (EDIT) got this done, went through ADB shell.
I unzip the the openrecovery to the sd card.. gives me openrecovery.zip a directory and an images directory.
SO then to flash a new rom I just put the .zip file in the updates directory.. and bingo bongo?
Going to try Cyanogenmod 7.1 first.. not sure where to find the brovo? bravo? mentioned.
James

Custom Recovery is here
http://forum.xda-developers.com/showthread.php?t=1242259
Bravo is here
http://forum.xda-developers.com/showthread.php?t=1332410
All ROMs and Mods are in the Dev thread.

I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games

AllGamer said:
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
Click to expand...
Click to collapse
I might give this a try next.. I have bravo tweeked out.. and I like it for the most part.. but there are somethings that dont seem to work as well as my G1.
I will just save my current phone in nand and then I can just reload it all back in - correct??
James

Yes
10chars

this one fjfalcon's CM7 , http://forum.xda-developers.com/showthread.php?t=1350453

Nandroid and battery
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1

Well if its Rooted, then you should have Open Recovery on it.
When you boot the phone hold VOL up and it will boot in OR...
or when you power off.. it should give you the option to reboot into RECOVERY.
There are lots of threads on here about OR .. but if you follow the menus you should be fine.. on an XT720 you push the camera button (big one) to accept a selection in the OR menu.
You can back up - which will save EVERYTHING.. a Nandroid backup is the best thing to store away somewhere should you mess up your phone.
YES you will have to loose everything when switching from 2.1 to (anything else)
If you are just updating to a newer build of something you put on.. then no.
You do the RESET and clear caches etc.. in OR.
Do a search its all on here .. usually the first page of whatever rom you want to TRY.
Have fun.
James

Thanks for the reply, time to install some rom's

Hilarious...after wading thru a few hundred pages of replies on this phone and the various roms, I completely missed your thread here James which is about as close to what I'm trying to accomplish as imaginable..
I posted some of my saga over here: http://forum.xda-developers.com/showthread.php?t=1399242
Do you mind me asking James/BikerBob...how did you make out? Anything I should know (if you have a sec read my long winded post lol!)
Did you have 3G/Wifi switching issues with stock, or maybe you didn't bother testing that / noticed it..before rooting I mean..
thnks!
(don't know if mods merge threads in this forum but mine is probably a candidate! sorry!)

racer321 said:
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Click to expand...
Click to collapse
No, kernal(maybe driver) can't support 5% or 1% percentage battery level.

OK, so I decided that changing the SD card to a class 10 might help app usage ..
I copied the old sd card to the new one.. and if I try and get into OR .. I get the exclimation mark in triangle instead of the OR logo.
What do I need to do to get back into OR? do I need to RE-Root?
James

If you don't have it already, grab Mioze's modded OR for the xt720 & follow the instructions. If that's all you did was to switch sdcards there should be no need to redo everything.

Sorry, never mind the OR issue, my bad.
I have played with this too much.. lol.. get things mixed up..
I had the OpenRecovery.zip from one version mixed with the directory of the other..
Jezz

OR runs from the files on the sdcard (the openrecovery folder & openrecovery.zip) if something is corrupted (or missing) you wont be able to boot into OR.