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.
Related
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...
This is Android 1.6 (donut) release for ADP1, rooted and modified
Current version
HTML:
3.0
- updated frameworks and apks from official framework and SDK.
- Supported languages: Czech, German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Russian
- added some parts of text to speech and accessibility
- Full package update (no wipe required)
I suggest to cleanup /system/sd/dalvik-cache (might work without, but it's better to do that).
http://ftp.wsisiz.edu.pl/pub/G1/android1.6-akirah.3.0.zip
Past versions
HTML:
2.1 - upgraded kernel to 2.6.29.6-bfs300-mkk2
see 2.0
2.0 - apps2sd
cm kernel 2.6.29 from 4.1.11.1
all donut goodies
compcache enabled by default
terminal, pdfreader, htc ime, and few things that I've forget to mention
What it requires:
HTML:
root
Radio 2.22.19_26I
Sdcard with FAT32/EXT2 or EXT3 or EXT4/
Recovery image that can flash ROMS not signed with release-keys
Installation
HTML:
Backup
Wipe
* You might need to format your linux partition
Flash
Downloads
ANDROID1.6 Akirah.3.0
Upgrade from 2.0 to 2.1
ANDROID1.6 Akirah.2.1
ANDROID1.6 Akirah.2.0
Click to expand...
Click to collapse
Themes
Minus theme by david1171 for v.2x
Blur theme by Brandenk - for v2.x
Click to expand...
Click to collapse
Theme template by david1171
Click to expand...
Click to collapse
Thanks for that. It looks good.
Q: Is there a way to remove app2sd?
3.0 for some reason doesn't work. It keeps telling me no data connection. 2.0 and now 2.1 do work however. Any ideas?
excellent ROM,
been from 2.0 upto 2.1 and now 3.0
only thing is that i don't see "secondary SD memory" in settings?
formated using SDParted script Swap=32Mb, EXT4=512Mb, rest FAT32 (8Gb class 6)
Internal Phone Storage stays 280~290Mb, so i presume Apps2SD is working ?
cheers
DT
Magic 32B (originally Vodafone UK, now AKIRAH 3.0 in Jakarta)
i hope someone can port to 32A for us...
very simple ROM but with some nice goodies. Keeps it simple and efficient.
Question, w/ compcache enabled at start, should I customize my own userconf / unserinit.sh to set swap size, and whether to use linux or backing swap?
What are the default settings?
Default is just 24Meg of compcache. Of course you can put user.conf and userinit.sh on /system/sd and it will take values from there.
hi, i have a problem: i did wipe and i flashed this ROM from recovery, but the boot stops at the screen "android"...
i had a 4.0.4 cyanogen with 3 partitions: fat32, ext2 and swap...
how can i solve this problem?
thanks
question about micro (magic 32B)
Hello,
first of all, thanks for your work, and all your current updates.
Second, I have not tried what I am going to ask, but anyway here it is.
Since Cyanogen found out the way to create "dual" roms for the dream and magic everyone has been doing them that way, but in all of them I have always had problems with the microphone sensitivity when in a call.
There is a little fix (pushing the audio files from an original 32B to the rom), wich works perfectly.
Now the question: Is this the normal procedure? no one has noticed this error before? can this still be done in Donut (I think the location of the files is the same)? Is this just a problem only I am having?
(ok, maybe more than one question )
The fix refered is the following:
adb push AudioPreProcess.csv /system/etc
adb push AudioPara4.csv /system/etc
adb push AudioFilter.csv /system/etc
Thanks for all
Is there any way of getting the Hero email client working in Donut?? Mass delete functions are seriously needed on my device.
cheers
leigh
bunglehaze said:
Is there any way of getting the Hero email client working in Donut?? Mass delete functions are seriously needed on my device.
cheers
leigh
Click to expand...
Click to collapse
Would be great to have whole SENSE UI on Donut Small question ADP1 means ? I`m using MAgic 32A ... Would it be compatible ? I`m newbie with Android... Thanks for reply
To be honest I am not really that bothered with the senseUI having played with pretty much all the hero builds, speed and stability is more important to me but androids inbuilt email client is about the worst one I have ever tried, the hero version is slightly more usable though.
I am surprised that there are not more email client apps in the market, all I can find on there is k9.
Also while I am here, will the blur theme work on 3.0?? I quite liked that one and it has been overwritten.
leigh
To be honest I am not really that bothered with the senseUI having played with pretty much all the hero builds, speed and stability is more important to me but androids inbuilt email client is about the worst one I have ever tried, the hero version is slightly more usable though.
I am surprised that there are not more email client apps in the market, all I can find on there is k9.
Also while I am here, will the blur theme work on 3.0?? I quite liked that one and it has been overwritten.
leigh
NguyenHuu said:
i hope someone can port to 32A for us...
Click to expand...
Click to collapse
Krzysiec said:
Would be great to have whole SENSE UI on Donut Small question ADP1 means ? I`m using MAgic 32A ... Would it be compatible ? I`m newbie with Android... Thanks for reply
Click to expand...
Click to collapse
For 32A users:
I haven't tested this yet, but if someone wants to give this a try, it should work.
Download: http://briancrook.ca/magic/akirah-3.0-32a-port-signed.zip
md5: 4f431ae885633518e0ee804470125ef8
Push this and the full ROM from the front page to your sdcard. Reboot into a recovery that allows you to flash a .zip that isn't only named "update.zip" (like Amon_RAs RAv1.2.1). Apply the ROM from the first page, them apply this patch. It will change the kernel to a 32A compliant one with BFS 300 (thanks to Radix999 for keeping on top of the BFS/kernel situation).
veneirt said:
hi, i have a problem: i did wipe and i flashed this ROM from recovery, but the boot stops at the screen "android"...
i had a 4.0.4 cyanogen with 3 partitions: fat32, ext2 and swap...
how can i solve this problem?
thanks
Click to expand...
Click to collapse
Whenever you go from Cupcake to a Donut to a Hero ROM or visa versa you have to wipe your ext3 partition as well or it boot loops. The easiest way to do this is to upgrade to Amon_RA's recovery and it gives you the option without having to go into console.
So wipe the phone, wipe the ext3 and repair ext partition, then flash the ROM.
Amon RA's Recovery
I know the recovery says Dream but I have it on my 32B with no issues, as well as several other people.
Anyone know if MyFaves works with this? I don't want to install it then have it FC.
up and running since 8 AM with only a single issue, but I think thats BFS300 related bc I experienced the same issues on the hero builds using it.
edited user-conf so Im running 192 MB backing swap, 80 swappiness, and 100% good compress.
Only thing I want now is a dark theme, but seeing how stable and reliable this build it, its only a matter of time before it picks up the momentum to attract theme makers.
am i correct in sayin this is better than cyanogens recovery image and will work with all the same things as cyanogens recovery does ??
UpGrad3 said:
am i correct in sayin this is better than cyanogens recovery image and will work with all the same things as cyanogens recovery does ??
Click to expand...
Click to collapse
you are confused. this is a rom not a recovery image. did you post in the wrong thread or something?
Beautiful rom, but I've some problems:
- gps starts, but never give me my position.
- the bar on the top of the screen (the bar that contains notification, icons, clock...) suddenly disappeared
thank you (and excuse me form my bad English )
Hi all,
I need to compile a Magic 32A compatible wlan.ko module for a Hero ROM that I'm using on my phone.
ROM: MoDaCo MCR 2.9
Kernel version: 2.6.27-mck-teknologist-1.8
Everything boots fine, but the kernel module wlan.ko doesn't work for the 32A Magic.
I tried replacing the wlan.ko with a version from 2.6.27-HoFo-V12 (HoFo 3.07), but it quickly gives me an error:
Code:
wlan: version magic '2.6.27-HoFo-V12 preempt mod_unload ARMv6 '
should be '2.6.27-mck-teknologist-1.8 preempt mod_unload ARMv6 '
I assume that there's no way to change the version of wlan.ko without recompiling it...
It's not an option to use the HoFo kernel because there are modules in the teknologist kernel that the ROM needs.
I'm pretty much stuck here. I'm not a developer by any means. I'm capable of installing Ubuntu and downloading the kernel source from HTC, but after that I'm stuck...
Would anyone be able to help me build a wlan.ko kernel module for Magic 32A that has the same version as 2.6.27-mck-teknologist-1.8?
Any help or direction would be great.
Thanks!
Well, I just learned what a toolchain is, and I'm downloading one...
I have the kernel config from the MoDaCo ROM, so that's all good to go. Now once I have this 'toolchain' thing, I think I'll be ready to compile.
maybe...
EDIT: I'm so completely lost here... I have the toolchain and the kernel source and kernel config, all in the right places, and all I get are error messages.
OK, so I compiled a wlan.ko, but it makes my phone reboot every time I try to load it, so I can't even check the logcat or dmesg.
cursordroid said:
OK, so I compiled a wlan.ko, but it makes my phone reboot every time I try to load it, so I can't even check the logcat or dmesg.
Click to expand...
Click to collapse
Maybe you should try installing wlan.ko and boot.img from another ROM made for the 32A?
Check this out and feel free to contact me via gtalk.
http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
Thanks for the offer to help, but I think this is a lost cause...
The wifi isn't the only thing that's broken when running a Hero ROM on 32A with the new radio. The camera doesn't work, the bluetooth is shaky at best, there are random reboots. It's a huge step back from the 32A Sense ROMs that are available now. It's like before when Hero ROMs were ported to 32B, then to 32A and nothing worked.
So what I've got here now is a 32A Sapphire with radio 6.35.07.29 and SPL 1.76.2007 that can't run any normal ROMs. I have learned a lot though and I'll be sure to try this again when the 2.0 Sense UI ROMs are released for the Hero.
This is a port for the SuperD 1.9.3 ROM. The kernel port overwrites the boot.img file and may impact some of the performance gains by WG (a dev would have to comment). It seems really fast to me
It's fast and stable.
Everything is working except the camera.
I take no credit for this work other than for posting updated kernel ports for the 32A new radios.
I don't take credit for the port because it was made with arctu's MAGIC Port tool which is getting better and better.
So what do I get credit for? Not much, other than for liking this ROM and trying to bring it to all of you who are using the new radios
DONATE!
If you like arctu's work and feel that he should continue maintaining it, donate to him: through the MAGIC Port page
If you think that the kernel DEVS should be appreciated more, donate to THEM: Cyanogen, OpenEclair Team, Cursordroid, Sanpei, Superatmel, PaY87, etc.
Now for some links.....
Here is the original post / thread for the ROM:
[ROM] Super D 1.9.3 with [Official] WG-Kernel v3-beta(10mb RHack) -- Need Feedback!
You will need 2 files; (1) the ROM, (2) the 32a port.
(1) Download the current 32b / Dream [ROM] Super D 1.9.3 with [Official] WG-Kernel v3-beta(10mb RHack) -- Need Feedback! here
(2) Download the 32a port for the NEW RADIOs:
EBI1_SuperD193-blk-WGKv3beta_32A_SP_NR_Port_signed to use Sanpei's kernel for the new radios everything except camera seems to be working
Instructions:
The port is for the Magic 32a with the new radio.
I am not responsible if you brick your phone.
As far as I know everyone who has followed these instructions has loaded the ROM successfully without problems.
You need new radio 6.35.10.18, SPL 1.76.2007 and recovery-RA-Magic32A-6.35-v1.5.2 to get this to load on your 32a Magic.
If you do not know how to update / change your radio, SPL and recovery don't proceed or go learn how here at Cursor's post.
1. Download the ROM from link above.
2. Download the 32a new radio port from the links above.
3. Wipe data/factory reset
4. Wipe Dalvik-cache
5. Wipe SD:ext partition
6. Flash ROM.
7. Flash port.
8. Reboot.
Everything except camera seems to work on this ported ROM.
is this JIT enabled?
soooo... no camera? how long till it will work then?
OP. If you build a kernel port and flash it it will replace WG Kernel completely. So you will not be running wg-kernel at all once this is flashed. So you should rename your title to avoid devs scoffing at this thread. I'm not a dev either. I think you made a mistake.
xaueious said:
OP. If you build a kernel port and flash it it will replace WG Kernel completely. So you will not be running wg-kernel at all once this is flashed. So you should rename your title to avoid devs scoffing at this thread. I'm not a dev either.
Click to expand...
Click to collapse
I am happy to change the title, but I believe the port I used replaces only one file in the whole kernel, no?
[PORT][32A][New Radio]Super D 1.9.3 HTC-CCR-Kernel for Test[01/03/10]
boot.img is a ramdisk. Treat it as an entire partition (which it is).
Care to try this one too?
Description:
Super D Port Using HTC-CCR-Kernel
Please start from a nonramhack version of Super D to avoid any potential problems:
http://forum.xda-developers.com/showthread.php?t=613809
Port Mirrors:
http://drop.io/xau_SuperD1_9_3_ebi1_HTC_CCR
http://www.megaupload.com/?d=QD18KI33
Details:
Built kernel from http://github.com/cursordroid/HTC-CCR-Kernel by Cursordroid
Base on boot.img from Super D 1.9.3
Includes 3G build.prop tweak and Sapphire audio patch from the one in this thread
I just built this, so I'm not sure if it will work. I don't have a 32A Magic so I can't really test.
I am not a dev. I just know enough to use github and run some Linux commands. This might not work at all. Anyways I want to see if this works.
This file is going to be pretty much the same as the Magic port tool's CCR output, except the port tool is using an older .config.
Warning: you should have swap and compcache problems. Just don't use them.
This post was an accident. Move on.
hi guys!
I wondered if this port is only for the ramhack's version of superd,because i have the old radio but the new roms are almost all for new radio!
i "hate" the ramhack because the slowdown problem in 3d games is very nasty!
there is a port for the version of the superd without ramhack!
i'm sorry for my bad english an thanks for the answer!
I just tried the CCR port and it fails to flash from recovery. Says something wrong with the boot.img, then verification failed.
Oh well!
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.