Related
I was wondering, what the process for porting ROMs?
Some new files, like the wlan.ko and add some BT lines in a init file.
What else? Can I get a direction?
I like to mess around with it, I like this stuff.. Im totally in love with this Magic phone..
We need more porting got the 32A device..
Look at this thread http://forum.xda-developers.com/showthread.php?t=530972 Amon_RA have postet a good guidline in his post http://forum.xda-developers.com/showpost.php?p=4040214&postcount=23 I did follow that guide as I made the cm-recovery-1.4-32A.img all I had to make was to edit the filenames.
If it was that easy, then we have seen more roms for the 32A
We can report the 32B that way, but not directly from G1.
ChrisB said:
If it was that easy, then we have seen more roms for the 32A
We can report the 32B that way, but not directly from G1.
Click to expand...
Click to collapse
That's not completely true, all of the g1 roms have custom kernels which mean custom modules and features that are added which will make the rom your porting limited to certain features... for example cm's kernel which is on every cm rom for the g1 has cgroup which is a module that basically optimized running tasks, squashfs which is a mount type you can use on the system, compcache which is module that you can use for swap memory which is very useful... and i'm pretty sure there is other stuff too... but this issue creates a limitation for us 32A users as far as porting roms because some roms are very unique because of certain stuff that comes with the kernel...
32Bs on the other hand are google branded phones so the g1 kernels work on them and the only thing that you change in the proccess of porting in simply renaming init.trout.rc to init.sapphire.rc from the ram disk and you don't need to change the kernel because it will work since both devices are google branded.
so yeah you can almost port every rom but just don't expect the full features and also another note when porting to 32A you have mess to around with the update-script file most of the time when not touching it you will not be able to get any command to work under the command line due to the symlinks, i would suggest using the update-script from fatal1y's hero rom 1.4 ported by skittleguy or the hofo community rom because those are the ones that i looked at to basically learn...
Good luck,
This basically untill HTC will release the kernel patches. Then you'll be able to port every single ROM to 32a.
READ FIRST - I am no longer updating my ROMs - details.
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used cyanogen's kernel from 4.0.4 (big respect to cyanogen, he's doing awesome work!)
- Now compcache ready - use this script for a big performance boost!
It has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've packaged Cyanogen's 4.1.6 BFS enabled Kernel and wlan.ko as an update.zip too (see above thread) - nandroid backup before applying!
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Changelog
2.2
Fixed SU and SD card bugs.
2.1.2
Updated busybox
Now compcache ready - use this script for a big performance boost!
2.1.1
Switch to Cyanogen's kernel
Fixed G-Sensor / Compass
Fixed sound
Unified Dream / Sapphire 32B download
2.1
Initial Release
me said:
This ROM is based on the Generic 2.73.405.5 release version of the 'new update' (together with my own optimisations) for the best possible performance! The ROM is now available in 2 versions - 'core' and 'enhanced' by popular request.
Included in both 'core' and 'enhanced' versions
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT3 partition as your second partition to use. dalvik-cache remains on device. EXT4 is NOT supported.
- Added Jbed Java
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added Custom Locale for setting non english Locales
- Added android-wifi-tether 1.52 (props to the developer, this is a great app!)
- Added WMSM
- Added busybox 1.15 - tweaked such that 'get information' in Swapper now works as desired
- Added nano 2.09 - text editor for use in shell mode
- Added terminfo and settings to boot.img to allow nano etc. use
- Added tun.ko file (untested, please report on whether this is useful)
- Added files required for Debian linux
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- Deleted Maps application - install from the Android Market to always stay up to date
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu. It will display MCR2.0 (core) or MCR2.0e (enhanced).
- Fix for HTC Peep on Vodafone now available here!
Click to expand...
Click to collapse
Yes
Fire up the stoves chefs and let the cook-off begin!!! lol
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Jonno12345 said:
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Click to expand...
Click to collapse
It is based on a newer build of Hero. So it should technically be better. May need some optimization for the G1 though.
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
modaco said:
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used the awesome 2.6.29 jac kernel (serious respect - these guys are the real heroes (pun intended)!)
- None of the 2.6.29 kernel tricks are used (yet)
- No real optimisation has been done (yet)
So, it has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Click to expand...
Click to collapse
thanks!!! 10 chars
B3astofthe3ast said:
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
Click to expand...
Click to collapse
just make sure u have the latest Radio and SPL and make a nand backup Just In Case
Anyone else having trouble flashing? Get an error, going to redownload incase it's just a bad download.
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
EDIT: Wiped dalvik-cache and it flashed .
Jonno12345 said:
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
Click to expand...
Click to collapse
You have to wipe your ext 3 and do a alt+w
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
Um first off that would be painstainkinly annoying to do and second if it was possible someone probably would have done it and third these roms are a HERO rom designed for a g1 they were once for hero now there for a g1
r_dub said:
You have to wipe your ext 3 and do a alt+w
Click to expand...
Click to collapse
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Jonno12345 said:
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Click to expand...
Click to collapse
Yeah for 1.5.1 its an absolute must
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
ccyrowski said:
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
Click to expand...
Click to collapse
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
EDIT: I'm only talking for myself and JAC, but a lot of the stuff JAC or I include in our builds we built from the source at http://android.git.kernel.org/
ccyrowski said:
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
Click to expand...
Click to collapse
Not a bad idea we could all pitch in and have all the hero devs work togeather on a fully functional G1 Hero build LOL just kidding
im gonna nandroid backup and flash... will post results
It looks like we have some known issues for me to fix tomorrow... no G-Sensor, Compass or (worringly) sound! biggrin.gif
If any chefs have come across these before and have any hints, let me know! wink.gif
P
hey i have bricked my phone i trieed to update my radio to install this rom after completing it when i rebooted my phone now i onli see a photo of a box and a arrrow cuming out of it indicating to phone i cant even power on my phone cant even go to recovery mode..............please help...
Thanks to chris-steenkamp's great find, it seems that we now can have fully working LEDs on any Hero ROM that can be made to run on Magic 32A (=means one that has a 32A kernel available or works with one of the supported kernels). The fix itself is amazingly simple and can be done like this:
1. Reboot phone into recovery (the recovery must have root and adb access - I recommend Amon_RA's great recovery)
2. Connect the phone to your PC
3. Switch to your Android SDK tools directory
4. adb shell mount -a (ignore warnings about /dev/mmcblk0p2 not mounting if you see them)
5. adb pull /system/build.prop .
6. Edit the build.prop file that you have just downloaded. Change ro.product.device from hero to sapphire. That's it!
7. adb push build.prop /system
8. adb shell sync
9. Reboot phone. You should now have working LEDs!
I've also repackaged most of the available 32A kernels with the modified build.prop file for some of the most popular Hero ROMs available. Please note that I take absolutely no credit for these kernels, I've just repackaged them to include the LED fix. All of the credit for making these kernels goes to hotweiss, modaco and redglasses.
Repackaged 32A kernels for specific ROMs with the LED fix incorporated:
TheOfficial Hofo 32A Kernel update by hotweiss for Drizzy's Hero ROM 1.5.5
TheOfficial Hofo 32A Kernel update by hotweiss for JACxHeroSki ROM 2.1
MoDaCo 2.2 32A Kernel update by modaco for MoDaCo 2.2 Hero ROM 1.5.5
MyHero 2.6.29 BFS 32A Kernel update by redglasses for MyHero 1.1.2 Hero ROM
MyHero 2.6.29 non-BFS 32A Kernel update by redglasses for MyHero 1.1.2 Hero ROM
Update for getting the trackball glow working in most likely any ROM on 32A Magic
Trackball glow fix for 32A
New! Experimental 32A kernel updates for specific ROMs with LED fix and other goodness compiled and packaged by me:
Note: Because of complaints about extreme bandwidth usage from my ISP, all files are now Rapidshare hosted only. Sorry.
Qteknology 1.6 2.6.29 BFS-303 32A 1.1 kernel update for Qteknology 1.6 and 1.7 by Qteknology
MyHero 1.1.3 2.6.29 BFS-303 32A v1.1 kernel update for MyHero 1.1.3 Hero ROM by redglasses
eViL ROM v3 2.6.29 BFS-304 32A v1.2.1 kernel update for eViL Hero v3 by eViL D:
eViL ROM v3 2.6.29 non-BFS 32A v1.2.1 kernel update for eViL Hero v3 by eViL D:
eViL ROM v3s 2.6.29 BFS-304 32A v1.2.1 kernel update for eViL Hero v3s by eViL D:
Blur Hero 1.5.7 2.6.29 BFS-303 32A v1.1 kernel update for Drizzy's Blur Hero 1.5.7 by Drizzy
T-mobile Pulse for G1 1.1c 2.6.29 BFS-303 32A v1.1 kernel update for T-mobile Pulse for G1 1.1c by diaztradeinc - VERY EXPERIMENTAL ROM, slow and many things don't work yet!
SenseHero 1.0 2.6.29 BFS-304 32A v1.2.1 kernel update for SenseHero 1.0 by ccyrowski
SenseHero 1.0 2.6.29 non-BFS 32A v1.2.1 kernel update for SenseHero 1.0 by ccyrowski
Drizzy's Final Hero 1.0 2.6.29 BFS-304 32A v1.2.1 kernel update for Drizzy's Final Hero 1.0 by kingclick
MotoBlur 1.1 2.6.29 BFS-304 32A v1.2.1 kernel update for MotoBlur 1.1 by twistedumbrella - WiFi doesn't seem to work, minimal testing, HIGHLY EXPERIMENTAL
eViL Sense 1.5 2.6.29 BFS-304 32A v1.3 kernel update for eViL Sense 1.5 by eViL D: - don't forget that this ROM doesn't have a bootscreen, it's just blank
Hero3G UnI Tattoo Donut 2.6.29 BFS-304 32A v1.3 kernel update for Hero3G UnI Tattoo Donut 1.6 by eugene373
Dwang Donut 2.6.29 BFS-310 32A v1.4D kernel update for Dwang Donut 1.12 and 1.13 by dwang
A word about "my" kernel update
Although I refer to that new kernel update as "mine", that's not really true. I'm not really a dev at all. I'm responsible for compiling the kernel, packaging the updates and for some minor tweaking and tinkering to get everything running, yes. But most of the credit for the creation of those kernel updates goes to the people who made it possible (mostly without even knowing): Cyanogen, TigerTael, hotweiss, modaco, bcrook, chris-steenkamp, Amon_RA, gboddina and countless others here at XDA. Thanks for doing the hard work and letting us go along for the ride!
The kernel in "my" updates is the latest Cyanogen 2.6.29 kernel with all the goodness that comes with it, most notably the latest BFS 304 code. As far as I can tell, there are no major problems with it and everything seems to be working fine, but please bear in mind that it's rather experimental and if you're going to try it, backup and be cautious. The kernel works just fine for me, but YMMV.
Unlike pretty much all the other G1/32B to 32A ROM ports I've seen so far, if you combine my new kernel updates with the original G1/32B ROMs, the kernel modules should be working. Which also means there's possibility for compcache, which I think is actually a first for 32A.
One more thing - those kernel packages MAY more or less work on other ROMs as well, but they're really made for the specific ROMs. If you insist on trying it with some other ROM, be sure to do nandroid backup before! The update script deletes/replaces some system files and there's no real guarantee it won't break your system on ROMs other than those they're supposed to be used with.
How to combine 32B/G1 Hero ROM with 32A kernel:
(0. Backup everything, but that should go without saying. I use Backup for Root and MyBackup Pro for user data and of course Nandroid)
1. Pick your preferred 32B/G1 Hero ROM and the corresponding kernel update from the above list, download them and place them in the root dir of your SD card
2. Start your favourite recovery (again, I use Amon_RA's) - it shouldn't matter if you have it flashed into phone or start it via fastboot.
3. Wipe (just in case) and if you use app2sd, format your ext3 partition as well
4. Flash your downloaded ROM file to the phone
5. Without restarting the phone (important!), flash your downloaded 32A kernel update
6. Restart the phone and hope that everything will work for you. Bear in mind that as usual, the first boot after flashing often takes a long time.
There's also another possibility to get LEDs working on 32A with ROMs that are not on the previous list. Some of the ROMs seem to already have the fix incorporated (that's how it was discovered). Those ROMs lack their kernel counterparts for 32A, but sometimes can be combined with other 32A kernel updates and work (for the most part).
LED-enabled ROMs that we know work on 32A when combined with one of the supported 32A kernels:
Qteknology 1.6 by Qteknology
eViL Hero v2.9.5 by eViL D:
Kernels that can be combined with LED-enabled ROMs:
TheOfficial HoFo for Drizzy's ROM by hotweiss. Known problems: multitouch doesn't work.
MyHero 2.6.29 (both BFS and non-BFS) by redglasses. Known problems: some problems with trackball glow notification.
MoDaCo 2.2 32A kernel by modaco. Known problems: compcache can't be enabled.
If you like my work, buy me a Pepsi
You mean you used QTek 32B ROM in you 32A device?
same question as pabbas, did you port the 32b rom to 32a, if so, just uplaod it, thx
What he did is flashing the 32b rom and then try to flash (one at a time) all the 32a kernels he mentioned..porting a 32b rom to 32a is all a matter of kernel substitution..
dBartoz said:
What he did is flashing the 32b rom and then try to flash (one at a time) all the 32a kernels he mentioned..porting a 32b rom to 32a is all a matter of kernel substitution..
Click to expand...
Click to collapse
So we can flash any 32B to 32A with the right kernel?
Yes, just as dBartoz says. Flashed the 32B ROM from the recovery and without leaving the recovery, flashed the 32A kernel update over it to overwrite the boot.img and wlan.ko with the 32A ones. That's pretty much all you need to do to run 32B ROM on a 32A device. Granted, you lose the ROMs customized kernel, but then again, there's still a lot to gain by doing this. I thought this is common knowledge here.
I can probably repackage the ROM and the kernel into one package and upload it, but honestly, I can't really see the point in doing that (and I would be pretty much distributing someone else's work without contributing anything).
Case_ said:
Yes, just as dBartoz says. Flashed the 32B ROM from the recovery and without leaving the recovery, flashed the 32A kernel update over it to overwrite the boot.img and wlan.ko with the 32A ones. That's pretty much all you need to do to run 32B ROM on a 32A device. Granted, you lose the ROMs customized kernel, but then again, there's still a lot to gain by doing this. I thought this is common knowledge here.
I can probably repackage the ROM and the kernel into one package and upload it, but honestly, I can't really see the point in doing that (and I would be pretty much distributing someone else's work without contributing anything).
Click to expand...
Click to collapse
thanks man,
I'm going to try it out
Case_, did you test if the bluetooth is working well with the "mix" rom for wich the led is working?
In that case this could be a (the first?) really full working hero rom for magic..
Let us know if you find any issues, as soon as I have some time I'll be checking it out too..
EDIT
Did you have to create three partitions (fat32, swap, ext) to make the rom work or is leaving only the fat32 partition ok?
You know, with 32A we don't have those lack-of-memory issues..
dBartoz said:
Case_, did you test if the bluetooth is working well with the "mix" rom for wich the led is working?
In that case this could be a (the first?) really full working hero rom for magic..
Let us know if you find any issues, as soon as I have some time I'll be checking it out too..
Click to expand...
Click to collapse
I did try camera, GPS and wifi and it all seems to be working just fine. I don't really care for bluetooth, so I did not try that just yet. I'm not even sure what the exact issues were. Will educate myself, try it (if I can) and report back ASAP.
Case_ said:
I did try camera, GPS and wifi and it all seems to be working just fine. I don't really care for bluetooth, so I did not try that just yet. I'm not even sure what the exact issues were. Will educate myself, try it (if I can) and report back ASAP.
Click to expand...
Click to collapse
Thank you very much..
It'd be great if you could report some information about battery life too..
P.S. I edited my previous post with one more question (about the partitions needed), what did you do under that POV?
Thanks again!
dBartoz said:
Thank you very much..
It'd be great if you could report some information about battery life too..
P.S. I edited my previous post with one more question (about the partitions needed), what did you do under that POV?
Thanks again!
Click to expand...
Click to collapse
So I tried the bluetooth and (unless I'm doing something wrong) it seems it's a no-go, sorry. I can pair with devices but that's pretty much it. When I tried using the headset to call, nothing really happened, the phone said the headset is connected, but the sound was still coming from the phone, not from the headset, and clicking on Bluetooth on in the call menu or pushing the headset call button didn't really do anything. That's with the HoFo Drizzy kernel. I'll try the other kernels soon (but I don't think it'll make much difference - then again who knows...)
Edit: With the MyHero kernel, the headset at least seems to work, but the only thing coming from when making a call is the white noise.
Considering the partitioning, I don't really like running app2SD on 32A (I think it actually slows the phone down quite a bit and doesn't help anything), but I also think Sense UI really needs more memory or swap to be usable in the long-term, even on 32A (and as reported by my friend with Hero, even he does have pretty much the same memory and performance issues I have with any Hero ROM without swap), so what I did was create (using parted via adb within the recovery) the usual three partition setup (only the ext2 partition was really small, like a few MB max) and then delete the ext2 partition, so there's no partition for app2SD and yet the swap partition is still identified as /dev/block/mmcblk0p3 , so the ROMs I'm trying pick it up and use it without the need to reconfigure anything. I'm currently using 64MB swap and as far as I'm concerned, the phone runs great, much better than without the swap partition, though I'll probably change the swap partition size to 32MB soon, as I think it should be sufficient.
As for the battery life, absolutely no complaints whatsoever - seems to me it's actually maybe even a bit better than with stock ROM (and that is with "always-on mobile" enabled), but I may be imagining it
Qteknology's rom use a shell script to making LEDs work. Now we have a app to do that.
Please look at this thread.
http://forum.xda-developers.com/showthread.php?t=565015
redglasses said:
Qteknology's rom use a shell script to making LEDs work. Now we have a app to do that.
Please look at this thread.
http://forum.xda-developers.com/showthread.php?t=565015
Click to expand...
Click to collapse
Yeah, I noticed some of the Hero ROMs contain the HeroLed application (and forgot to look up on it). Mainly because it's force closing at the phone startup
So, from the 32A point of view, the shell script is definitely a better alternative for now, as it's the only one working (but still only with some of the kernels). But it's great to know why this seems to be the only ROM that works, thanks for the info!
I just flashed Qteknology + HoFo for Drizzy's as you suggested.
Tried the led with handcent sms a second ago, and it works
You rock, Thanks for the helpful post
Finally a confirmation that it works for someone else as well, great! Just out of curiosity to see if it really is somehow related to SPL, what SPL do you use?
Oh, and don't thank me, I'm just "mixing" together someone else's hard work.
I'm thinking about the possibility of "splicing" this LED shell script from Qteknology ROM into other Hero ROMs, but so far I wasn't even able to locate it in the ROM or find some info about it :/
So far I have used only myhero rom's, and they worked very well. This rom works even better! Only thing I would love to see is transparent notification area (like in myhero rom).
Great work! Thanks!
Led notifications works with sms popup and missed call aplications.
The dafault one that came with the phone, which is an italian 32 by TIM.
Just got this infos from fastboot:
HBOOT-1.33.0008 (SAPP10000) | RADIO-3.22.20.17
II just noticed that multitouch aint working for me. I tried the browser and the album and it won't let me zoom that way.
Another issue is that I keep geting force close on com.HTC.core or something like that.
Ah, thehtc keyboard is pretty damn laggy on the browser.
Should i try another kernel? Which one should I try?
nubcake said:
II just noticed that multitouch aint working for me. I tried the browser and the album and it won't let me zoom that way.
Another issue is that I keep geting force close on com.HTC.core or something like that.
Ah, thehtc keyboard is pretty damn laggy on the browser.
Should i try another kernel? Which one should I try?
Click to expand...
Click to collapse
You're right, the DrizzyHoFo kernel seems to not support multitouch. Thanks, I'll mention it in the first post. Try either of the other two kernels, those work just fine here. I have no preference in them, really - the MyHero kernel has a BFS alternative available, whereas the MoDaCo kernel (which in its 32A alternative I think does NOT have BFS, though I can be wrong) should have the possibility of enabling compcache (although I need to try to work on that, there's some problems with modprobe I can perhaps work around).
No problems with force closes here, at all. Did you wipe before flashing the ROM, as you always should, and if you use ext3 for app2sd, did you format it as well? Other than that I'm afraid I can't really help you, sorry.
But there's now another ROM that has LED working on 32A - eViL Hero ROM v2.9.5. So if anyone doesn't like Qteknology for some reason, you can try this one. I'm updating the first post with my findings (I've changed it's structure a bit for now and altered the thread title as well). It's most likely that working LEDs will soon be common on most Hero ROMs even when running those on 32A - I'll try to keep updating the list in the first post for as long as I think it makes some sense.
Releasing this rom in the Sapphire / myTouch3G section as it is not compatible with the Dream (I think?)
http://forum.xda-developers.com/showthread.php?t=624411 <-- I'll be keeping this thread updated
Or see post #4 below
----------------------------------------------------------------
I've been crafting a 32B rom for a few weeks based on the AOSP Eclair branch since the 2.1 code release. So far I've managed to build the source, build a kernel from Cyanogen's source (thanks cm), and get the google apps working from the Milestone dump Maxisma posted a few weeks back (thanks Maxisma).
It works pretty well but now I'm stuck ...
1. How do I get bluetooth working? It won't turn on .. if I search the forum it just brings up a million posts about bluetooth not working on hero roms.
2. My wlan starts but I can't obtain an IP address via dhcp ... which is a bit strange ... Not sure if this is a rom problem though or a local router problem. I compiled the wlan driver after compiling the kernel and copied the wlan.ko into by lib directory.
3. Last thing is ncommander's camera driver. I've tried getting his source but I am a git newbie and have not been able to merge his code into my local Eclair repo. How do I do this? Or if it's easier can I just grab the compiled binaries from a working Eclair rom (I'm not sure which files these would be).
Thanks for any help or pointers ...
just make a bata, and add blutooth in another update, no one really uses blutooth anywase.
i know absolutely nothing about develping roms, but im just trying to provide as much help as posible.
Thanks I appreciate the reply.
Bluetooth is important to me though, I use it every day to listen to podcasts with Doggcatcher.
I think I'll go with your idea and release it as beta, just one big issue to sort first. It is rooted (ro.secure=0 in the right places) and I can get root when I am in "adb shell" but I can't get root using the superuser.apk and included 'su' binary. adb logcat gives me these errors:
Code:
D/dalvikvm( 1028): +++ not scanning '/system/lib/libwebcore.so' for 'makeExecutable' (wrong CL)
D/dalvikvm( 1028): +++ not scanning '/system/lib/libmedia_jni.so' for 'makeExecutable' (wrong CL)
D/dalvikvm( 1028): +++ not scanning '/system/lib/libexif.so' for 'makeExecutable' (wrong CL)
[ROM] "Android 2.1 for 32B" - No A2SD - Small and light
Here's an Eclair rom I built specially for the 32B Magic / myTouch3G. It is built from the Android 2.1 source that was released a few weeks ago, and has a kernel built from Cyanogen's kernel sources for Eclair (sources here).
This rom does not support A2SD. I've always found it annoying that almost all 32B roms require the ext3 and swap partition on your SD card. The Magic does not need A2SD in my opinion ... and getting rid of A2SD and swap on sd cards eliminates the slowest link in the chain. With a bit more optimisation this could be a very fast rom.
Visually this is almost completely stock, if you like nice themes and graphics for your roms I would suggest MetaMorph, and browsing the Android theme section.
This is a completely new rom to XDA, not anyone elses work rehashed.
Complete with:
- Root privilage/superuser
- Google Apps
- Big APN list
- Busybox
- Android Market working
- Support for wired/wireless tether (get the APK from here -- I'll include it with later releases)
- Support for swap partitions (swapper/droidswap ...)
This is a stable rom, everything works (apart from the snag list below) and there are no force closes.
Snag list - what doesn't work
- On first boot, make sure you select "com.android.provision.DefaultActivity". I'm working on a fix for this.
- Camera not working. Plan on putting in Ncommander's camera driver for next release.
- Bluetooth not working. <-- I need help with this. Can any devs offer advice?
- Camcorder (doesn't work on any Eclair roms)
- Not compatible for G1/Dream ... you probably wouldn't want it anyway without A2SD
Requirements
- Engineering SPL
- WIPE before installing this rom
Disclaimer
I don't really think this needs saying, but I am not responsible if you brick your device. Make sure you know what you are doing! Read >> Sapphire hacking wiki <<
Warning: HTC Magic 32b/MyTouch3G only. Not designed for G1
Download - st0kes-v1.1.zip
Thanks: bcrook for getting my build off the ground, cyanogen for cm-kernel sources, radix999, dwang for inspiration
if its for mytouch only, why is it in the G1 section...
Because originally when I posted I was just asking for some dev advice, and I figured I would get more page views in here than in Sapphire development.
Anyway like I said I'll be keeping my thread in Sapphire dev updated rather than this one.
Edit: wasn't even aware of the ROM kitchen before this.
Untested! I don't plan to provide support for these ports!
The reason I am publishing is from my recent trials of compiling my own kernel for new radio 32A Magic. I have learned a lot about what sanpei's kernel consists of and the similarities between our device and the GSM Hero. In particular, the only difference between our ROMs seems to be mainly just the kernel. Everything else is almost identical. As such I want the community to try to use a tested NR kernel, sanpei's 2.6.32.9, and apply it to some different ROMs and report back with results.
We don't need multiple threads of the same kernel on different ROMs. So I'm trying to consolidate some information here.
I can test it on my cousins phone probably this weekend as well. Hoping for some preliminary results till then.
sanpei2.6.32.9_villain_port
This is a repack of sanpei's kernel repacked via ordinary boot.img method, with init.hero.rc copied to init.sapphire.rc
Flash this after you flash Villain ROM:
http://www.villainrom.co.uk/viewtopic.php?f=44&t=680#p11789
2.1 Sense UI ROM
sanpei2.6.32.9_anykernel.zip
This is a repack of sanpei's kernel repacked via Koush Anykernel
The idea is that you can flash most ROMs from old radio using this port with some caveats.
READ THIS BEFORE YOU FLASH
You cannot use this port if:
1) You are NOT on a 6.35 series radio. This rules out any 32Bs or myTouch 1.2
2) the ROM uses squashfs anywhere (open up the update.zip of the ROM and look at /system/modules/lib and /system/
3) modules have special directory structure under /system/modules/lib (such as Cyanongenmod, which has modules under 2.6.xx.x-cyanogenmod instead of just 2.6.xx.x)
4) you use an ext4 apps2sd partition (it will simply not recognize it)
Explanations:
If the ROM uses squashfs, this kernel does not support it and you will need to fix those problems yourself.
There may be other issues involved when you use this kernel. It is recommended that you stick to the one that came with the ROM.
This rules out any Cyanogenmod because of the use of squashfs.
If missing init.sapphire.rc, copy the Hero one (if flashing a Hero ROM) using:
adb shell cp init.hero.rc init.sapphire.rc
Refer to the ROM Bible for reference:
http://forum.xda-developers.com/showthread.php?t=682243
Any new or old ROMs that already use new radio
This is just the kernel carz12 posted repacked:
http://forum.xda-developers.com/showthread.php?t=689652
Credits:
cyanogen for everything
Koush anykernel
sanpei for his version of AOSP kernel with integrated new radio support
And a lot more I might be missing
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
pellen said:
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
Click to expand...
Click to collapse
Must have hero recovery not patched recovery by cursor
Ahh...thougt cursors tweaked recovery didn't differ that much. *change recovery*
I am pretty sure the update script can also be modified. The assert statement can be removed and the rom should load fine on the Hero, Cursor and Amon Ra recoveries.
Ok, so now I've flashed VillainROM 6.1 with the sanpei2.6.32.9_villain_port and I can't say it's working especially well
First of all it doesn't ask me to enter the SIM card PIN when i boot, so the mobile connection is dead. Wifi and bluetooth is dead too. The camera flicker, and then fades to black, taking a pic resulted in reboot.
giant_rider said:
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Click to expand...
Click to collapse
I completely missed that post actually . Plus it's now closed.
But I wanted to see specifically how well Hero ROMs translate over to Magic ROMs because of what I've been reading about the similar kernels. The thing is that while I know to copy over init.sapphire.rc to resolve some conflicts, I'm not sure what else is involved in porting a ROM right now to get it to work.
I'm new to porting ROMs.
Maybe mods ought to close this one then?
With Eris ports you will be missing SIM card features.
So with 2.6.32.9 bluetooth and wifi break? I was actually expecting bluetooth to work. What works?
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
I was looking to figure out some of the incompatibility of the kernel I was compiling so I thought this might help
If the Hero ROMs worked well enough I had the idea of modifying the AnyKernel script to add cpio to recovery by updating busybox so that ROMs can be unpacked, modified and repacked all in recovery. It means unpacking the ramdisk gunzip, modifying it and repacking it, essentially adding one script to AnyKernel. But I guess they don't work that well so
xaueious said:
I'm new to porting ROMs......
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
Click to expand...
Click to collapse
A lot of the issues when porting are not related to the kernel but to the modules and lib files.
Try testing and hacking through some issues. For example, replace the wlan.ko file in the /system/lib/modules folder with one from a similar rom that is working on 32a same radio version. If you're porting Hero, then pull the wlan.ko from one of Capy's roms.
To get camera working, you'll need to replace the camera related libs in the in the /system/lib/ folder with ones from a similar rom that is working on 32a and so on.
Porting involves, at a minimum, replacing the boot.img-ramdisk and the files for stuff that is not compatible with the 32a hardware, radio version, etc.
Once you figure out these basics by experimenting with swapping out stuff with working pieces from a 32a compatible rom on the same radio version, you can then get into making updates to the files in the boot.img-ramdisk yourself, the update-script, the build.prop files, the init files in /system/etc/init.d, etc.
xaueious said:
Maybe mods ought to close this one then?
Click to expand...
Click to collapse
I think it's a good thread. Maybe some of the guys who have been porting roms will add their comments. I may be wrong but I don't there is a how to guide for porting.
anykernel is useful for a direct kernel port like cm5 to EABI1 on same rom scenarios, nice piece of coding by koush though, way many files to change, an update package would work on roms made for your device(proper assert) but most need the update script modified and at least wlan.ko changed.
testing now Flashing
how long does it take to boot?
Working:
USB
Music app (Sound ok)
Gallery 3D OK takes a while to work
Not Working:
Camara
Wifi
Bluetooth
GSM connection
Issues:
Very very long and slow boot alot of patient is required.
Slow Menu Scrolling
Freezes some times (have to take battery)
Reboots alone sometimes