yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] surfwaimea:
I've tried some new 1.6 ROMs and SuperD seemed very good to me.

I miss the trackball glowing, so I'm still on CaSense (1.2 now ;)).

Do you know NotifyLight (thread)? Unfortunately only works if the screen is on :(
[myTouch 3G, Magic Android Development] nubcake:
A reboot fixed the force close. Now its fine.

So far which Rom+kernel option is the best ?

I'm tempted to try the myhero with bfs patch but I read that its actually slower than the no-bfs one. What would you advice ?
[myTouch 3G, Magic Android Development] TheMorpheus:
I've tried MyHero 1.1.1 with BFS kernel and it is slower than no-BFS one; I suggest you not to try it, you'll waste your time!
[myTouch 3G, Magic Android Development] pagubg:
I don't understand what to do to get leds working?!

I have 32A Magic, with MyHero 1.1.2 (latest) without BFS (because it laggy). My leds are not working. Just the green one when phone is charged. This is not useful for me and i can not tell "My leds working" :) Led do not work with any programs which are trying to flash my led.

BTW:

I have Engineering SPL 1.33.2005
[myTouch 3G, Magic Android Development] :
I have the 2005 eng SPL.

I am using Redglasses non-bfs 2.6.29 kernel, repackaged with the ramdisk for Evil's Hero.

Led's working fine.
[myTouch 3G, Magic Android Development] GyD:
Qtek with Hofo: LED OK, Trackball OK, Multitouch NotOK

Qtek with Redglasses non-bfs 2.6.2: LED OK, Trackball NotOK, Multitouch OK

Qtek with Modaco: LED OK, Trackball OK, Multitouch OK :)
[myTouch 3G, Magic Android Development] Case_:
I've updated the first post to include a basic guide. I'm not sure what ROM you're using from what you mention, but if you use MyHero ROM, the LEDs don't work (yet). You have to use one of the confirmed ROMs (as of now, there are two, see the first post).

Can you elaborate a bit more on what is wrong with the trackball on Qtek+redglasses kernel?

I thought that repackaging the kernels in such a way might be "cleaner" way to do it, but didn't have time to try that just yet.

I wonder what the problem of the person with the engineering SPL was that his LEDs (reportedly) didn't work at all. Apart from the SPL, our phones seemed to be exactly the same.
[myTouch 3G, Magic Android Development] pagubg:
Perfect, Thanks! :) Now i understand what to do.

edit:

So i have installed evil hero for 32B devices + myhero kernel-WITHOUT-bfs-2.6.29 nad leds are really working :)
[myTouch 3G, Magic Android Development] TheMorpheus:
I have the same rom and kernel and it works!!!

@Case_

Great work man!!
[myTouch 3G, Magic Android Development] nubcake:
Is the trackball working?

Anyway, im on qtek + modaco and both the led and the trackball are working great :)
[myTouch 3G, Magic Android Development] dsincl12:
Same here everything works great! Only thing I'm having issues with is getting a call when listening to music with a usb->3.5mm jack, the microphone doesn't seem to work so I have to unplug it before answering a call.

I don't know if it's me or the phone though :)
[myTouch 3G, Magic Android Development] Case_:
I've tried the Qtek ROM with non-BFS 2.6.29 kernel to see what exactly doesn't work with the trackball and I really can't find anything wrong. Trackball works fine here and glows just fine as well when it's supposed to. So I'm not sure what GyD meant by "trackball not OK" :/
[myTouch 3G, Magic Android Development] GyD:
The trackball glow fine when receiving a phone call but, if you miss the call the trackball don't glow every ±10s.

For my test, i put the phone in sleep mode and call my phone with another and don't touch it.

I've the same bug with the myHero rom.
[myTouch 3G, Magic Android Development] nubcake:
Just an update.

Im on Qtek + modaco and both the led and the trackball are working fine for me.

Too bad that performances aren't good actually. Every 3D app that i tried lags badly :|

Maybe ill try the combo qtek + myhero later...
[myTouch 3G, Magic Android Development] Case_:
Try seting up swap partition like I mentioned in one of the previous posts. I find that Sense UI simply needs some kind of swap, even on 32A. I'm not having any problems with lag (well, sometimes it lags a bit, but even less than the vanilla 32A ROM did, actually).
[myTouch 3G, Magic Android Development] nubcake:
Sense UI was working fine, while every 3D game/app that i have kept lagging.

Which rom are you using actually_

Anyway, i flashed qtek + myhero no-bfs kernel, and now they are working smooth. No lag at all. :D

Edit:

Right, im experiencing the same problem :|

So, basically theres not a working combo yet

Hofo = no multitouch

modaco = low performance

myhero = no trackball
[myTouch 3G, Magic Android Development] Case_:
Yes, confirming the lagging in 3D apps with modaco's kernel :/

Personally, I can miss trackball glow, though, so I'm at the MyHero kernel now. I'll try to figure out something.
[myTouch 3G, Magic Android Development] FrAsErTaG:
Ive tried and tested the roms mentioned by the OP

I have an original SPL provided with my HTC 32A (Three Australia)

My results are the same as op's

But I have reverted back to Amon's Ion rom its just so damn fast compared to this hero stuff!!
[myTouch 3G, Magic Android Development] TheMorpheus:
I agree, I had the exactly same experience and for me MyHero kernel is the smoothest out of three
[myTouch 3G, Magic Android Development] chris-steenkamp:
Possible Fix?!?!

I downloaded ther eVil ROM and have been mucking around with different kernel configurations to get the LEDs working.

While unpacking and re-packing kernels, I noticed the default.prop file within the ramdisk itself but a few of the different kernels had extra content as opposed to just the usual

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1

This file highly resembles the build.prop file that can be found under the /system directory.

I think the kernels that don't support the LEDs are the ones which have the extra information in their default.prop files.

Upon comparing a working and non-working build.prop if found that the one with which the LEDS worked had the following

ro.product.device=sapphire

while the ones that didn't work had this

ro.product.device=hero

.

I was running the eVil rom at the time and I had my LEDs working so I decided to replace the ro.product.device property from sapphire to hero. When I rebooted, the LEDs no longer worked :) success!!

I then reverted back to the original just to check and everything was working fine.

I the restored my previous MyHero v1.1.2 backup (which did not have working LEDs) and changed the ro.product.device property from hero to sapphire. Reboot -> Voila!! working LEDs!!!!

I think the kernels that don't work properly have set this property already in the default.prop file and, as the property is read-only, it can not be set again when the system reads the build.prop file :)

Hopefully this helps...

:cool:
[myTouch 3G, Magic Android Development] Case_:
Wow, great work!

I've tried looking at the default.prop file in jachofo kernel, which only has green led working with Qteknology and MyHero ROM, and it contains the usual four lines, no ro.product.device line there.

Then I flashed MyHero 1.1.2 ROM with MyHero 32A kernel update - only green LED working, as usual. Changed the ro.product.device in build.prop, rebooted...and indeed, LEDs were working!

So while it seems that the ro.product.device set to sapphire instead of hero is one of the key things to get LEDs working in Hero ROM on 32A (and possibly 32B and G1 as well?), there's something else in the kernel preventing the LEDs working with some kernels, ie. jachofo, since it has the same default.prop file as the working kernels and yet the leds don't work with it, even with ro.product.device set to sapphire in build.prop.

Nevertheless, amazing find!
[myTouch 3G, Magic Android Development] mgear356:
hey can u make a update.zip so that i can patch to get working LEDs on mhero 1.1.2?
[myTouch 3G, Magic Android Development] Theros:
It's very simple to fix this without having to download an entire update.zip!

I connected my phone to my PC, and used adb pull to get build.prop off the device. Edit in a text editor as mentioned, and then push it to the device, reboot, and the LED should work properly! My trackball still flashes when I get calls or texts but it doesn't keep flashing, even though the LED at the top of my device does work.

adb remount
adb pull /system/build.prop c:/android-sdk
adb push c:/android-sdk/build.prop /system/
adb shell
reboot
[myTouch 3G, Magic Android Development] Case_:
Anyway, if you don't want to use adb and edit the file yourself, here's a tiny ZIP update that you can apply from recovery and it'll overwrite the file in phone with the modified one. Note that this is only for MyHero 1.1.2.

http://www.edgeoftheworld.cz/files/android/myhero/MyHero_v112_LED_update.zip
[myTouch 3G, Magic Android Development] nubcake:
Done the fix through adb, leds are working great.

Thanks guys
[myTouch 3G, Magic Android Development] enek:
LEDs fully working in MyHero 1.1.2 (32A)

I was able to get the LEDs fully working using this fix:

http://xdaforums.com/showpost.php?p=4632456&postcount=776

Basically just replacing one line in /system/build.prop
[myTouch 3G, Magic Android Development] Case_:
enek: You do realise that you're posting that in the thread that your post with the fix is linking to, right? ;)

Anyway. I've changed the first post once again. Now you can find repackaged kernel updates there for some of the most popular Hero ROMs. Those updates include the LED fix for those that are not confident enough to modify the build.prop file themselves.
[myTouch 3G, Magic Android Development] enek:
I do realize that now. :(

So many threads so little time. Sorry for the confusion.
[myTouch 3G, Magic Android Development] lptqd:
My hanset is Sapphire(HTC G2 32A HBOOT-1.33.0009 S-ON ),I pull the build.prop and edit the build.prop and push it to Sapphire,but the Led is no working.How can I do let my Led working?

system:myhero1.1.2 without BFS
[myTouch 3G, Magic Android Development] mgear356:
Thanks it works! But the rate if blinking remains the same even if I change it to fast

Hmm something to pounder on. ..
[myTouch 3G, Magic Android Development] than33:
OK. I've done it. It is very easy to do.

After changing 'hero' to 'sapphire' I realized that some options are looking/working different. For example there is no 'automatic brightness' option (which never worked). Also brightness of screen is working much better. I mean You can choose much more darker screen then before (You have more steps of brigtness).

I think that ROM has many informations about Sapphir, but it need to know it is actually working under Sapphire. Because, before change, ROM was 'thinking' it is working under Hero many things could work not as good as should.

So... This change is NECESSARY for every Hero on Magic user.

P.S. I'm using MyHero 1.1.2.
[myTouch 3G, Magic Android Development] doctoren:
I tried MyHero 1.1.2 with the LED fix 2.29 BFS kernel and orange charging LED works now. Continious trackball glow on receiving a message does not work in my case.
[myTouch 3G, Magic Android Development] Reignzone:
Any chance for 32B compatibility?

Can we expect to see this wonderful discovery being used for 32B motherboards? I would almost assume the process listed previously could enable the LEDs...without the flashing of a 32A kernel that is.

Has anyone else that has a 32B device been eager to give this a shot? :D

Reports or findings would be much appreciated. Great work guys.
[myTouch 3G, Magic Android Development] TheMorpheus:
Great work guys!!

Now LED's working with every kernel (after fix default.prop file) What about the trackball? Why is it working just with Qtek + MoDaCo 2.2 32A kernel?
[myTouch 3G, Magic Android Development] platinumyahoo:
JACxHeroSki 2.1 TheOfficial Hofo 32A kernel update worked good but the MT was not working.

Using Qteknology 1.6 with MoDaCo 2.2 32A kernel update worked amazingly.. very fast, MT, LED and wifi all working.. :)

Now im flashing JACxHeroSki 2.2 with TheOfficial Hofo 32A kernel update and seeing how that goes.. will update u soon..

UPDATE: MT still not working in JACxHeroSki 2.2... gonna try using the MoDaCo 2.2 32A kernel update..

UPDATE2: JACxHeroSki 2.2 + MoDaCo 2.2 Multi-touch + Wifi working!
[myTouch 3G, Magic Android Development] timmy1980:
This is amazing! Thanks for the great find. So... After I applied the hofo for drizzy kernel on drizzy's 1.5.7 my bluetooth hands free behaved differently than before. As we all know BT handsfree doesn't yet work on hero builds. After applying this fix I could still connect to my parrot handsfree but it said that my phone had no network even though it did and also it could not access my phonebook, when I placed a call it just routed to the phones earpiece. Previously it would route to the parrot handsfree and report the signal correctly and sync my phonebook but I would get no audio. Could this update to fix LEDs hold the key to working BT also?!?!

Big thanks again for this.. Just keeps getting better and better!

Sorry if this has been mentioned before.
[myTouch 3G, Magic Android Development] Case_:
As for multitouch, I suspect that those HoFo kernels simply don't have it enabled in them. I'd love to try building my own kernel with all the features I'd like to see on Hero 32A working (ie. compcache), but right now, I don't have enough time for that :( I've already spent way too much time on this...

As I've mentioned in a different thread, I was never able to change the rate of blinking properly (in the apps that support it) even on vanilla 32A ROM, so I'm guessing there's something else to it.

I've already asked people on our local forum to try this yesterday, but it seems no one is eager enough to try...:(
[myTouch 3G, Magic Android Development] Case_:
Just tested this again. The trackball seems to be working with any ROM, as long as you can combine it with the MoDaCo 2.2 32A kernel. Too bad it has problems with 3D and other graphically intensive apps, otherwise this kernel would be close to perfect :(
[myTouch 3G, Magic Android Development] solgems:
change the prop file and adb pushed it...

the LED WORKS!!! download chomp sms and test it, all colors worked perfectly (:

thnx for the great discovery. i wonder if there are some other variables that we can modify to get the trackball to work perfectly too, dis is too odd
[myTouch 3G, Magic Android Development] mgear356:
well said! I wish for the trackball to work for miss call..
[myTouch 3G, Magic Android Development] ichijin:
Do any of these combinations fix the timestamp issue?
[myTouch 3G, Magic Android Development] binchen2002:
Thanks for your great post. I'm using myhero 1.1.2 and after I install the 'patch' the led works great.

B.T.W. I did not use the recovery mode to make the change. I just use the below steps. Just for your reference

1. connect the phone to the pc

2. copy the build.prop file out and make the update as per your description

3. in the SDK tools folder use the below command

adb remount

adb push d:\build.prop /system/

(here the d:\build.prop is the path on my PC)

4. restart the phone and it works

let me know if I did anything not proper. Thanks.
[myTouch 3G, Magic Android Development] Case_:
You should thank chris-steenkamp for finding the fix, not me! :)

Yes, the way you do it should be fine. I just prefer changing the system partition while the phone is not running (for no particular reason, I just feel better doing it via recovery), so I wrote the guide that way.
[myTouch 3G, Magic Android Development] daeshawn:
ok so i'm actually using MyHero 1.1.1 as i had to many issue with 1.1.2..can i say its safe to say that the kernal on the front page should in theory work with 1.1.1?
[myTouch 3G, Magic Android Development] Case_:
If you mean the MyHero update with LED fix, then yes, in theory it should. I haven't touched the kernel. And if it doesn't work for any reason, the only thing to do to get it working again should be to reflash the original 1.1.1 32A kernel update by redglasses.
[myTouch 3G, Magic Android Development] daeshawn:
hey thank already flashed and it works fine..thanks u made my magic. Complete for me!!! (I dont use. Bluetooth lol)
[myTouch 3G, Magic Android Development] Case_:
(I've removed the post as not to confuse anyone, sorry.)
[myTouch 3G, Magic Android Development] OPTiCO:
MT isn't working for me with the two BFS300-kernels.
[myTouch 3G, Magic Android Development] Case_:
Damn! I swear I DID try that and it did work. Oh well...:( Back to square one I guess. Sorry, then... Embarassing :(
[myTouch 3G, Magic Android Development] OPTiCO:
np :p On the bright side tho, they're really fast ;)
[myTouch 3G, Magic Android Development] Case_:
Okay, so once again for the first time, the new kernel update is up. Let's hope it'll stay up a bit longer this time (and please, don't tell me multitouch isn't working, I checked! :D ).

As I've mentioned in the first post, compcache should be available if you want to try it. There should hopefully be no problems setting it up manually via modprobe and rzscontrol. As for automatic userinit.sh setup of compcache, I'm not really sure if that will work right now. I'll look into it, though, as soon as I can, and I'll also try to make more of these "porting packages" for other ROMs.
[myTouch 3G, Magic Android Development] Daneshm90:
Hey, so flashed the new bfs 32a kernel patch u put up...likin the speed alot....mt works fine...sweet dude !!! Oh n im on evil's latest hero...just thought i shud post tht ;)
[myTouch 3G, Magic Android Development] Case_:
Yeah, it's quite possible it will more or less work with other ROMs as well, but it's "tailored" for Qtek 1.6. Be REALLY sure to do nandroid backup before you try it on another ROM, as the update script is a bit more complicated this time (to make modules/compcache work) and deletes/replaces some files in system directories. And of course the ramdisk/init.rc is from Qtek 1.6 as well.
[myTouch 3G, Magic Android Development] Daneshm90:
Oh damn lol...then i guess i shud b happy it worked when i flashed on evil's rom :D
[myTouch 3G, Magic Android Development] Daneshm90:
Hhmm k one wierd thing...none of the task managers work with this kernel...if i close any app doesnt matter wht....it restarts rosie (i c the htc screen again)...:(
[myTouch 3G, Magic Android Development] Daneshm90:
Hmm k i narrowed it down to Mail...if i close tht it restarts i guess cuz i have the mail widget...false alert i guess lol
[myTouch 3G, Magic Android Development] solgems:
@Daneshm90 which evil are u using? 2.9.7? any FC or wierd things so far?

@case_ this thread is the best 32A thread! haha (the forum is flooded by 32B),
[myTouch 3G, Magic Android Development] Case_:
That's one of the reasons behind why I'm messing around with creating "my own" kernel compiles and such - I was jealous, and there's not that much going on for 32A in comparison to 32B :)

As for eViL's Hero ROM, there's a new experimental 32A kernel for it somewhat hidden in the first post of TigerTael's thread, made by TigerTael himself, and it's (of course) very nice. Even though it's currently for 2.9.5.
[myTouch 3G, Magic Android Development] rgbc:
O

Hi Case_, thanks for all your work on this, your led thread inspired me to start mixing roms/kernels. Regarding the eVil roms, I've used TT's and the MyHero kernels and found them to be equally stable but the MyHero 2.6.29 nonBFS appears quickest to me, you can really notice the difference when windows load, sliding down the unlock screen...BTW just got back from a trip to Czech & Austria, spent 6 days in Praha, great city, really nice country. Cheers, Rob
[myTouch 3G, Magic Android Development] Daneshm90:
Hey, have u tried the new one he posted ? 32a with bfs 300 ?? how does tht speed compare to the myhero u found to be quickest ?? im lookin for best kernel combo 2 :D
[myTouch 3G, Magic Android Development] rgbc:
Hi Daneshm90,

I tried out Case_'s kernel with eViL HeRo 2.9.7 and found it very similar to TT's kernel, stable and quick but just not as snappy in terms of interface loading as the MyHero 2.6.29 nonBFS kernel, which I think is a BFS issue rather than a who is building the kernel issue, still it is great to have so many great kernel/rom options to test and to see so much enthusiasm around improving android, which is by far my favourite of the mobile phone OS.

Here is a good read on BFS: http://ck.kolivas.org/patches/bfs/bfs-faq.txt

Cheers,

Rob
[myTouch 3G, Magic Android Development] skittleguy:
Seems like the best place to ask is here: are all the 32A Hero roms still plagued by that stupid -4 hour timestamp bug?
[myTouch 3G, Magic Android Development] Daneshm90:
Yea, i switched to myhero's kernel on evil's rom.....much smoother....in general bfs seems to slow things down...maybe thing's will change as its evolved.
[myTouch 3G, Magic Android Development] Daneshm90:
Has neone tried running this clock at stock speeds ? im curious how it runs....
[myTouch 3G, Magic Android Development] rgbc:
It does unfortunately but I've made my peace with this bug long ago :)

The speed of the Hero roms are significantly improved though, worth a nandroid backup to checkout if you haven't tried one recently.
[myTouch 3G, Magic Android Development] NguyenHuu:
i did some search and came upon a thread on xda from july that addressed this issue. not sure if it worked since hte project stopped back in August. a user created this app http://code.google.com/p/smsfixtimes/

maybe try it if you havent and report if it works?
[myTouch 3G, Magic Android Development] Case_:
I'm awfully busy this week, but at least I've updated my Qteknology kernel pack to BFS303, finally implemented squashfs, tried a few different options and polished some issues. Again, the kernel pack supports compcache, but if you want it, you have to set it up manually, Qteknology doesn't do that for you.

I wanted to upload BFS303 kernel pack for MyHero 1.1.3 as well, but while testing it I've found out that there are some issues with multitouch (=I couldn't get it working with my kernel config for some reason). As I've said, I don't have much time right now, so no MyHero BFS303 for now. I'll try to look into it and/or upload kernel pack for another ROM (eViL is next, I guess).
[myTouch 3G, Magic Android Development] mgear356:
can anyone post a minor for Case32A_v11_BFS_Qtek16.zip @ 4share or mediafire?

cant d/l from rapid..
[myTouch 3G, Magic Android Development] Case_:
I will upload it somewhere else. Check back in a few minutes.

Edit: Link changed.
[myTouch 3G, Magic Android Development] mgear356:
Ah I used your kernel with Latest evil rom.. works fine
[myTouch 3G, Magic Android Development] Case_:
Hopefully I'll post eViL ROM specific package later today.
[myTouch 3G, Magic Android Development] Lorennz:
Blur Rom from Drizzy

Did anyone experience unusual battery life with Drizzy's Blur Hero Rom? I see extremely better battery life on Blur V1.5.7 that never had on any other ROMS.

Only drawback is I have seen so far in this ROM that getting the Market Enabler work properly. It seems working fine but I can not see paid applications in Market. I updated it to the latest version too.

On the other hand I have another Magic runs on CyanogenMod 4.1.11.1 that has no problem at all on Market with the same version of Market Enabler.

:confused:
[myTouch 3G, Magic Android Development] kencix:
hello all

flashed my magic with myhero 1.1.3.. (led fix included)

trackball is working, and led when charging..

is there a fix for notify leds?

kenci
[myTouch 3G, Magic Android Development] Case_:
I think that issues with ROMs should probably be discussed in the corresponding ROM's thread...(although I'm not really sure how mixing kernels comes into this)

Again, I think this belongs more to the MyHero thread as MyHero 1.1.3 has LED fix and 32A support "out of the box". But unless I'm mistaken, I think Hero in default config doesn't use the notification LEDs the same way Magic does - I believe that SMS and mail in particular only blink trackball, not LED like on Magic.