Related
Official APD1.5 image in Post 2
Here's the new JFv1.43 RC9 for all you UK users. Enjoy!
--- announcement for JFv1.43 Holiday
New! JFv1.43 is a bugfix release for the Holiday (ADP1.1h) version. This release fixes the issues most people were having with Latitude hanging after clicking "I agree". More info on my blog.
The links below have been updated with the new versions.
--- announcement for JFv1.42
The ADP1.1h version of JFv1.42 is out! This is based on the new ADP1.1 OTA that was put out this morning. I've also released a JFv1.42 version of RC33, that fixes the issue with adb not being enabled in recovery mode. You can find more details here
The links below have been updated with the new versions.
--- announcement for RC33
The RC33 version of JFv1.41 is here! Links are below. It is essentially the same as the RC30 version, as far as my changes are concerned. You of course get all the goodies included in RC33.
Note: RC33 contains a radio update. I chose not to include this in the RC33 update itself, because I personally don't want it re-flashing the radio every time I apply this update. Here (md5: cf8714d273fb0274574d9e3831e11fdd) is a separate update that *just* flashes the radio. You only need to install this update once (unless you happen to flash an nbh at some point in the future, in which case you should re-flash the radio afterwards).
To check if you have the new radio, go into the about phone screen in settings and check the baseband info. It should end with 1.22.14.11
note: I have no clue what the differences are in the new radio. I just assume they are good, and that it's better to use the new radio than the one from RC30.
note: (yes, I love Notes ). You shouldn't need to do a wipe if you're going from RC29 or RC30 to RC33. I've even had reports that you don't need to do a wipe going from ADP1.1 to RC33. Give it a shot if you want, and let us know if you had to wipe. Don't forget to do a nandroid backup first
note: (couldn't resist). The first/initial boot after upgrading to RC33 make take a minute or two. Just give it some time before concluding that you need to do a wipe.
------------------------
(original release annoucement for JFv1.41)
This version contains... *drumroll* multi-touch support! Thanks to lukehutch, zinx and ryebrye, this build allows android applications to receive multi-touch events. The built-in browser now supports multi-touch zooming! It also includes an "Auto-Rotate" setting that you can enable, to allow it to change screen orientation, based on the orientation of the phone. You can turn on auto-rotate in the browser settings (it's off by default).
See lukehutch's blog post for more information about the new multi-touch support, as well as a few other demo multi-touch apps he created that you can try out after installing JFv1.4. He also mentions a few issues that are present in browser, that you might run into while playing with zoom.
Other changes of note for JFv1.41 include:
a console in recovery mode. You can press alt+x to exit out of the recovery program and go directly to a console.
the ADP1 build is now based on the ADP1.1 firmware. See this thread for information about the changes in ADP1.1
the ADP1 build now includes .odex files for all of the system apks and jars. This means that you will have more space available in /data for all of your apps and caches, although less space available in /system
busybox's vi should now save files correctly, instead of saving them as blank files
One thing that I would like to point out about the ADP1.1 build is that it allows you to skip the initial google registration. This will make registering over wifi painless. You just click the "skip registration" button in the registration app, enable wifi in settings, then open the registration app again by trying to access one of the google apps (gmail, market, etc.), and then you can register over wifi.
Downloads:
ADP1.1: (md5: 076ba12c3e733805ba1c865ab48d370c)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_Holiday.zip
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: 6ecf0ea8175e1aece8a770253447b6a8)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.42/JFv1.42_RC33.zip
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 5a722ad92c9dd1081987b2ad9814111f)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_RC9.zip
http://jf.andblogs.net/2009/03/03/jfv143-rc9/
In the console in recovery mode, there are a number of "special keys" that you should be aware of:
Code:
ctrl search
caps lock menu (on the keyboard)
arrow keys call + w,a,s,d
change virtual console call + 1,2,3...0
scroll console home + w,s
page up menu (above the trackball) + w
page down menu (above the trackball) + s
home menu (above the trackball) + a
end menu (above the trackball) + d
escape back
reboot menu (above the trackball) + search + backspace
Also, you can type "reboot" to reboot, and type "recovery" to go back into the recovery program.
JFv1.41 can be installed in the usual way. Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. If you are switch between versions, e.g. from RC30 to ADP1, you must also do a wipe in recovery mode (alt+w). This will clear all your data/settings/apps, and you will have to re-register once it boots back up. If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.41 RC30, then you shouldn't have to do a wipe.
NOTE: If you are on the stock ADP1 image, you will need to upgrade to JFv1.31, then boot normally at least once, before upgrading to JFv1.41, to keep from having to perform a wipe. If you try to go from stock ADP1 -> JFv1.41 directly, you will have to do a wipe.
NOTE: If you end up with 2 Superuser whitelist apps in the app menu, you can uninstall one of them in Settings->Applications->Manage Applications. There will only be 1 that is uninstallable, so don't worry about uninstalling the wrong one.
Note: To install these updates, you need to have a recovery image that uses test keys. If any of the following are true, you most likely have a recovery image that uses test keys
you have installed my modified recovery image in the past
you have an ADP1
you currently have one of my modified firmwares installed
If this is your first time installing one of my firmwares, you may be interested in the other changes that have been made in previous versions, which are included in this version. Some of the notable features include:
Many more commands are available to use on the terminal. busybox is included, to provide standard commands like cp, grep, less, more, vi, sed, cp.. etc.
A secure way to get root access, through Koush's superuser application. To get root, open up terminal emulator and type su. A new window will open asking if you want to allow root access. Click "Yes" or "Always", and it will go back to the terminal emulator, and you'll have root access
A number of useful kernel modules that you can use. For example, ext2, cifs, and a host of others
A full phone backup utility. Boot into recovery mode with home+power, and then press alt+b to perform a backup. It stores the backup as .img files in a subfolder of the nandroid folder of your sdcard. To restore the backup, you have to have the engineering spl or hardspl installed, and then flash the images with the fastboot utility
ota updates are disabled. This is to prevent t-mobile from automatically updating your phone with a new update that removes your root access.
some applications that are missing on RC8 (the uk version) have been added. For example, the voice dialer and the amazon mp3 store.
when you connect to the phone using adb, you have root access
I've attached a full changelog vs the official builds for each version.
Here are the updated Build Environments for JFv1.41. These can be used to create an update identical to JFv1.41, or to create one modified to suit your tastes/preferences. You can find more info about the build environments over at my v1.31 post
ADP1.1: (md5: ce591333f2252d805c5eaccae332f5e7)
http://jf.odiness.com/v1.43/JFv1.43_Holiday_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: b3b0bc89c4b417b6ce6728fd9cc2c7fc)
http://jf.odiness.com/v1.42/JFv1.42_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 0d0845f85382e5689f015a2904f928a0)
http://jf.odiness.com/v1.43/JFv1.43_RC9_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/03/03/jfv143-rc9/
Official ADP1.5 image
JesusFreke’s AndBlog
The official 1.5 firmware is here finally!
When is your 1.5 coming out?
May 1, 2009
The answer is… wait for it.. wait for it..
NOW!
If only i had a nickel for every time someone asked me that over the last week or two
This build is based on the official HTC ADP1.5 image. You should install the 1.5 radio from that HTC page before using this build.
Some of the important changes/features
* I’m now including a much better Superuser app, courtesy of zinx
* I’ve rebuilt the kernel and enabled netfilter support, to allow tethering.
* You can see/download both paid and protected apps in the market
* Luke’s multitouch kernel patch and browser patch have been ported to the .27 kernel and 1.5 browser.
* Support for the “apps to sdcard” hack. There’s not a separate “apps to sdcard” build. You can use the same build whether you are doing apps to sdcard or not. Thanks to haykuro for explaining how he’s done this in his images, so I can make my builds compatible. See here for a tutorial on setting this up.
* I’m not including a recovery image in this build. I ran into some snags getting all of the recovery features to work with the 1.5 recovery image, so I’ll forgo that for now. If you don’t have a spiffy recovery image yet, I’ve packaged up the most recent recovery image from JFv1.43 as a separate update.
If you are already running a “rooted” build (ADP/mine/haykuros/the dudes/whatever), it is available for download via the jf updater app (available on the market). If you don’t see it, open up the app settings, and choose either ADP1 or “All the updates” for the “System Mod Version” setting.
Or you can always download the update.zip file below and install it yourself. If you have a G1 and this is your first time installing a community firmware, you’ll need to follow any of the multitudes of tutorials out there for rooting your phone.
You can try to upgrade without a wipe, but if you run into any problems (for example, su/Superuser doesn’t work), you’ll need to perform a wipe. If you don’t want to wipe, take a nandroid backup before upgrading, so you can revert back to the backup.
JFv1.50 ADP1.5
JFv1.50 ADP1.5 Build Environment
JFv1.50 ADP1.5 CHANGES
JFv1.43 Recovery Only
Nothin but the best from the best! Works great man!
Thanks to you and everyone else that helped make this possible.
Stericson
Awesome! Great job mate, about to install.
OMG YES!!!!
Third!! Great Job JF, LukeHutch, Zinx, RyeBrye and everyone else who helped with this. Working great for me!
superb
will give it a go in a few hours
u've got to be the top supporter of the android community.
keep it up!!
Awesome!
Couldn't wait for a new update. You delivered like a champ!
Thanks peeps!
EDIT: Just a question, do I need to format my SD again like the other post says?
hey JF
for each of your releases you have said "If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.4 RC30, then you shouldn't have to do a wipe" but every time i install one of your builds i get stuck with an infinite boot loop and have to perform a wipe. Any ideas? btw ive only used your adp builds on an adp
Great job, to you and all who contributed. Works great so far, loving the multi-touch zoom.
Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Edit2: just installed rc33 and the radio update, everything works great . Posting from it now!
yesssssssssssssssssssssssssss
do the jf rc30 1.3 themes work with the new update or we going to need to update the themes
awesome job everyone! installed and loving it. thanks for all your hard work
Manacit said:
Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Click to expand...
Click to collapse
Nobody expects the Spanish Multi-Touch Inquisition!
kron2 said:
do the jf rc30 1.3 themes work with the new update or we going to need to update the themes
Click to expand...
Click to collapse
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.
This Is Great!
thx jf and the update works great
ok so i need to resign my browser.apk before doing the template or not? thank the best release yet
JesusFreke said:
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.
Click to expand...
Click to collapse
..wow
/10char
I've searched everywhere, but I can't find any mention of this. In the past JF builds, the CIFS kernel module was included, so it was possible to mount samba shares. It doesn't appear to be in any of the 1.5 ROMs. Does anyone know if this is because of an inherent incompatibility, or if it was just left out for other reasons?
- Chris
Maybe it hasn't been compiled in the kernel as a module.
Did you tried the "find" command in order to find it?
If you can't find it at all ask the ROM Builder to compile the kernel with cifs, smbfs and nfs support so you have all the modules inside.
in the old 1.1 builds, JF compiled a bunch of useful linux kernel modules in /system/modules (actually it's a rom image loop-mounted to that folder). as the new roms are not built by JF, they obviously won't be there. however, i hope someone could compile those for the new kernel once the official build is out.
... and to answer my own question in case anyone searches on this, in JF 1.5, the author was awesome enough to once again include cifs in the cramfs image that mounts on /system/modules. Thanks, JF!
JF 1.51 Available now!! http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/#more-88
Just saw the update using the JF updater App!!
Go get it!!
thoughts and screenshots please!!
JFv1.51 CRB43 ADP http://jf.andblogs.net/wp-content/plugins/download-monitor/download.php?id=13
JFv1.51 CRB43 US http://jf.andblogs.net/wp-content/plugins/download-monitor/download.php?id=14
JFv1.51 CRB43 EU http://jf.andblogs.net/wp-content/plugins/download-monitor/download.php?id=15
Damn, I jus flashed to Haykuros new rom, lets c sm screenshots and new features
notxel21 said:
JF 1.51 Available now!!
Just saw the update using the JF updater App!!
Go get it!!
thoughts and screenshots please!!
Click to expand...
Click to collapse
I literally *JUST* installed JF 1.5 after a fresh wipe
Edit: here is his blog entry: http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/#more-88
Judging from the change logs it's just some behind the scenes changes. US version is out though.
working well for me .. will up some screens soon
Oh you know I'm going to flash this....righ after I hit the shower.
I assume this is based on the US OTA update. Are the IM apps intact? Myfaves? Does Apps2sd work? Impressions?
wonder if this is any different from JF 1.5 ADP
hmmm ill wait.
johnnylicious said:
wonder if this is any different from JF 1.5 ADP
hmmm ill wait.
Click to expand...
Click to collapse
Read the change logs.
The change logs state the differences between his update and the OTA.
uberingram said:
Son of a *****! I literally *JUST* installed JF 1.5 after a fresh wipe
Edit: here is his blog entry: http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/#more-88
Judging from the change logs it's just some behind the scenes changes. US version is out though.
Click to expand...
Click to collapse
lol i did the same now something else pops up
oh hell,
can i resist?
i read the change log but just said theres a new change in the kernals only
wonder what that means lol
So this is basically the TMO 1.5 OTA update with JFs usual mods for root and everything else? Is that correct?
Has anyone else cracked this open & noticed that framework-res.apk is no longer there? Its usually in the framework folder correct? I was gonna attemt to modify this with stericson's lock screen but its not there. Is it in a different place that maybe I overlooked??
EDIT: Nevermind
compressed /system/framework into a cramfs image at /system/framework/framework.cramfs, in order to free up enough space for everything else
Click to expand...
Click to collapse
I wonder how this will work for themes?? Can you simply extract it with 7zip or is there more to it?
What's the difference from the
JF 1.51 ADP1 and the JF 1.51 US
Lakers3408 said:
What's the difference from the
JF 1.51 ADP1 and the JF 1.51 US
Click to expand...
Click to collapse
The same differences there were in regards to ADP 1.1 and RC33.
Is there any major differences between the new ADP CRB43 and ADP CRB21?
I have JF 1.51 ADP installed on my phone works great just I miss my myfavs icon , If i install the JF 1.51 US one over the ADP one will I run into any problems or should I wipe the phone first before I throw the US one on?
hedcold said:
I have JF 1.51 ADP installed on my phone works great just I miss my myfavs icon , If i install the JF 1.51 US one over the ADP one will I run into any problems or should I wipe the phone first before I throw the US one on?
Click to expand...
Click to collapse
It's advisable to wipe if you're changing build types.
Ok thanks for the advice
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.
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.