yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] Case_:
Added BFS303 kernel packages for MyHero 1.1.3 and eViL ROM 2.9.8.2. Both are compcache-ready as always. On eViL ROM the compcache is activated automaticaly - the ROM does that and I didn't see any reasons to change it (you can of course disable it if you don't care for compcache).
[myTouch 3G, Magic Android Development] daeshawn:
wow

I dont if its me or what but i flashed the bfs 303 kernal for myhero 1.1.3 and dayaaaaam my hero seems super fast..but the keyboard seems a little laggy..
[myTouch 3G, Magic Android Development] solgems:
Thanks! will try out the evil rom+ kernel later (:
[myTouch 3G, Magic Android Development] walie:
Sorry for the noob question, but is compcache necessary for 32a Magics?

If so, do i just have to format my SD card with an ext3 partition and the kernal takes care of the rest?
[myTouch 3G, Magic Android Development] mgear356:
Using evil with your kernel.. seems like the incall volume is louder than usual even at min volume ... anyone facing this?
[myTouch 3G, Magic Android Development] Case_:
Necessary? No, certainly not. But in my experience having some kind of swap helps Sense UI tremendously, even on 32A, so why not have the option of using compcache.

And compcache has nothing to do with ext3 partition (which I personally advise you NOT to create because I find that App2SD slows 32A down quite a lot, at least in some situations). If you want to set up compcache, search for compcache and/or userinit.sh.

Doesn't the ROM have some kind of volume hack? I think it does, check the thread about the ROM and ask there... I don't think kernel could affect volume.
[myTouch 3G, Magic Android Development] maxisma:
got the leds fully fixed for 32Bs too, will be included in my next Heor 1.7.1
[myTouch 3G, Magic Android Development] rgbc:
I've been pushing audiopara4.csv from the rogers rom to the last few eVil builds due to low Mic volume, you can test the Mic volume with voice search. Mic volume fix: xdaforums.com/showthread.php?t=549837. Just noticing that the kb is very laggy with the eVil 2.9.9 rom and Case_'s kernel, going to check out the non-bfs myhero kernel to see if this sparks up the kb.
[myTouch 3G, Magic Android Development] Case_:
So chris-steenkamp's fix works on 32B as well? Finally some confirmation, I'm surprised nobody tried that sooner (I even asked people to do so on our local forum and nobody did).
[myTouch 3G, Magic Android Development] Case_:
I'm not noticing any unusual lag except what I've seen on any ROM with any kernel (ie. when the phone is running low on memory and/or is busy with something), weird. I do use Task Panel to kill unneded tasks frequently, though, to keep free memory as high as possible. Also, the eViL ROM has compcache activated automaticaly with swappiness at 80, so you might want to experiment with that - it may be slowing some things down.

That said, I'll certainly experiment a bit with BFS vs non-BFS when I'll have more time to do that.
[myTouch 3G, Magic Android Development] rgbc:
Just rebooted with the non-bfs kernel and the kb response seems more immediate. Will test for the day. I had just did a clean install of 3.9.9 installed apps and rebooted before bed so low mem shouldn't have been an issue. You may want to check out Tue Mic volume though as most folks won't tell you it is low when you are talking with them, you can tell by the accuracy of the voice search and by looking at the waveform.
[myTouch 3G, Magic Android Development] Case_:
I know about the fix you linked, but...I don't know, I still think that's up to the ROM developer to include or not include it. I could of course just add it to the kernel update package, but I think that's an issue with ROM, not with kernel, which is what this thread is ultimately about (beyond the LED fix). I'm not trying to create custom ROM here, I'm just providing customized kernel packages to run them. I'll think about this.
[myTouch 3G, Magic Android Development] JStar1033:
question for those people with 32a on Rogers, is the sms time stamp still -4hrs?
[myTouch 3G, Magic Android Development] Case_:
Added kernel packages for eViL ROM 2.9.9 (appliable to all three variants, kernel and ramdisk is the same in all of them) and Drizzy's Blur Hero 1.5.7. The package for Qteknology 1.6 can be used for Qteknology 1.7, nothing has changed as far as init files go.

As before, eViL ROM gives you automatic compcache with my kernel package. Note that both eViL 2.9.9 and especially Drizzy's Blur Hero took a LONG time to start the first time - with Drizzy's Blur, I even thought the phone froze on me (while showing the message "Unlocking SIM card"), but eventually it caught up.

I don't think this is something kernel can fix/cause.
[myTouch 3G, Magic Android Development] rasco11:
Hi Case_,

first of all thks for ur kernel...

I've previously tried myhero 1.1.2 non-bfs LED fixed kernel and it works like a charm!

however I upgraded my ROM to myhero 1.1.3 and used the new kernel from ur first post

now LED/trackball notification doesn't work at all..anyone can confirm that?

thanks
[myTouch 3G, Magic Android Development] solgems:
thanks for the hard work for the new kernels!
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
so fast

Qteknology 1.7 and your Qtecnology kernel is the fastest hero Rom I have run on my 32a magic. Thanks, keep up the great work.
[myTouch 3G, Magic Android Development] rasco11:
Now even if i WIPE and downgraded my rom to myhero 1.1.2 and applied myhero32A_nonBFS_LEDfix_MyHero112.zip from the 1st post of this thread,

unfortunately both LED & trackball blink (when miss call)

no longer

work, I wonder why :confused::confused::confused:

please help me............many thanks!!!! :o
[myTouch 3G, Magic Android Development] Case_:
Other than the usual wipe+format ext2/3 if you're using app2sd I'm afraid I can't help you. There's been a few (three 'til now I think) reports of the fix not working for some reason, but never someone for whom it was working before. Tried once again MyHero 1.1.3 with the kernel update when you posted the first message and sorry, was unable to duplicate...
[myTouch 3G, Magic Android Development] lorenzo.themax92:
need kernel port for 32a, for the new qtek 1.7 :D

when you can do it??

thanks :)
[myTouch 3G, Magic Android Development] Case_:
It's the same as for 1.6. See the first post and/or one of my previous posts.
[myTouch 3G, Magic Android Development] Daneshm90:
Yo case, ne chance u can list 32a kernels available for donut ?
[myTouch 3G, Magic Android Development] lorenzo.themax92:
ok thanks :) i flash qtek 1.7 with your kernel, is normal that i see in the info rom of my htc magic 32a the version is 2.73.405.5, instead the 2.73.405.38 ? in this site http://xdaforums.com/showthread.php?t=540745, the qtek 1.7 show the version is 2.73.405.38 ..
[myTouch 3G, Magic Android Development] darkonpt:
Just use the kernel in the Myhero page , it´s working for 1.1.3 , i tried to use this kernel (myhero bfs303) , but no signal for SMS after a wile, it doesn't play the sound , just blink and vibrate, for that i restore the myhero 1.1.3 kernel, and the led´s work .
[myTouch 3G, Magic Android Development] Case_:
For the adventurous, I've added the Pulse Beta for G1 1.1c kernel package. Note that this ROM is not very usable in its current state, the home screen is very slow and many things don't work properly or at all. Still, it's interesting to have a preview of what's to come.
[myTouch 3G, Magic Android Development] maxisma:
hey I fixed the LEDs in my 32B ROM 1.7.1 completely..
[myTouch 3G, Magic Android Development] mgear356:
hey how about the trackball?
[myTouch 3G, Magic Android Development] maxisma:
Trackball light does work too.
[myTouch 3G, Magic Android Development] Krzysiec:
How did U managed to work trackball ? Maybe U can share with us ?
[myTouch 3G, Magic Android Development] lpasq:
do you think you can be more specific? what did you do and what is the full functionality now?

for me...i have the following:

solid orange LED = charging

solid green LED = full charge

blinking red LED = low battery level

blinking orange LED = SMS notification

one time/single flash trackball = email notification

one time/single flash trackball = vmail notification

continue flash trackball = incoming call
[myTouch 3G, Magic Android Development] GyD:
For me, the trackball issue seems to be a kernel issues.

How to test trackball:

- put the phone in sleep mode

- call your phone with another and don't touch it.

- if the tracball glow every ±10s yes it work, if not it don't work.
[myTouch 3G, Magic Android Development] Case_:
I don't think it's kernel related, since I think I did test this with my kernel and some of the ROMs and I think that on some of them it did work fine and on some of them it did not. The reason I say "I think" is because I did so much ROM+kernel combining and testing in the last days/weeks that I'm not really sure if I can trust my memory. But I THINK that trackball glow did work right with Qteknology ROM and didn't work with MyHero, for example.
[myTouch 3G, Magic Android Development] rasco11:
you're correct, exactly my case the continuous flash of trackball for missed call doesn't work, even I did wipe/factory reset to myhero 1.1.3 (fresh!), it does not work. however(weird enough), LED does blink in green for email and charging (orange/green if fully charged), but not for sms notification -- LED just refuse to blink!:mad::mad:

anyone(with working LED and trackball) mind to share their default.prop so I can have a good look at it for troubleshooting purpose?

as always, thanks for your great help:)
[myTouch 3G, Magic Android Development] Case_:
Hmm, MyHero ROM seems to be missing some of the sapphire files in /system/lib/hw that Qteknology has. If anyone is willing to try in the meantime (I REALLY have to go to bed now), try downloading the following (very small) file (containing the whole dir from Qteknology ROM):

http://www.edgeoftheworld.cz/files/android/trackball_testfix.zip

You can either just unpack it and push those few files to the appropriate location on the phone or you can just flash it from recovery as usual (without wiping), your choice. It should be safe to do without breaking your system even if it does not fix anything, but...you know the drill. Better backup than be sorry ;)

Let's see if it does fix the trackball issues.
[myTouch 3G, Magic Android Development] NguyenHuu:
just to let you guys know, i am on myhero rom 1.1.3 and my trackball lights up fine even with those missing files that are present in Qtek's rom. it blinks like it should with incoming SMS, and it blinkings fine with incoming calls.
[myTouch 3G, Magic Android Development] Krzysiec:
But i`m sure it`s not blinking as a reminder (in 5 minutes after incoimng calls or SMS in some period time) ... as it should ;)
[myTouch 3G, Magic Android Development] NguyenHuu:
ah i see, i never noticed that.
[myTouch 3G, Magic Android Development] Krzysiec:
I don`t know how it is in this ROM but trackball should work like that ;)
[myTouch 3G, Magic Android Development] rasco11:
that's what I'm going after actually, it was working on my myhero 1.1.2 with Case_'s kernel patch but after upgraded to 1.1.3, none of them work as a reminder after incoming calls or sms.........:confused:
[myTouch 3G, Magic Android Development] rasco11:
yes, trackball will glow every 10 sec (for missed call) and LED blinks in green every 2 sec (it works like this after the kernel-fix), but now these are non-working for me....too bad.

I wonder should i stick with 1.1.3....
[myTouch 3G, Magic Android Development] Krzysiec:
Can U please tell me what exactly fix are U talking about (exact link) ? ;) I didn`t found any solution for trackball and leds before ... TIA !
[myTouch 3G, Magic Android Development] rasco11:
Refer to first post of this thread for specific kernel for corresponding ROM with LEDfix, however it does not work for me with myhero 1.1.3, it workED for me with myhero 1.1.2, even I tried to downgrade to 1.1.2 now still it won't work anymore.... I'm also looking for the root cause of it, but to no avail.
[myTouch 3G, Magic Android Development] NguyenHuu:
after just tested a call and left it as a miss call. my trackball glows / "pulsates" every say 5-10 seconds only when the screen is on. then it goes to sleep and then it stops glowing. is this what you guys experience?
[myTouch 3G, Magic Android Development] GyD:
i din't test with screen on (because the pulse is not usefull when screen is on lol)
[myTouch 3G, Magic Android Development] Case_:
Updated "my" kernel packages with package for eViL Hero v3. Note that if you want to flash Blur/Pulse animations updates, you obviously have to flash it in this order without restarting:

1. ROM

2. Blur/Pulse animations update

3. 32A Kernel package
[myTouch 3G, Magic Android Development] dBartoz:
Great!

I think I'll check this out..

I'm a little bothered from having to create the swap and ext3 partitions though; do you know if this is going to work with the fat32 partition only (on 32a off course)?

EDIT

I tried and it seems to work with fat32 only..
[myTouch 3G, Magic Android Development] dBartoz:
Up for this useful thread..

Does anyone know if it is possible to port the latest MoDaCo roms (2.8 should be the latest one) to sapphire 32a?

Are there any working kernels to accomplish that?
[myTouch 3G, Magic Android Development] Case_:
You mean porting his ROM for Hero to 32A? Is it even worth trying with all the other Hero ROMs we've got nowadays? But I can try, sure (not that it means much).

I was thinking more of trying Drizzy's final Hero today, there's some quite positive feedback about it. Spent some time with Qteknology Tattoo ROM and enomther's TheOfficial Donut as well, but they still wouldn't run reliably on 32A for me, there are some issues with these (and, in case of Donut, obviously kernel related - camera does weird things). I'm still quite busy, though, so I can't spend the time I'd like on this - hence the lack of updates recently.
[myTouch 3G, Magic Android Development] lesjaw:
i'm using drizzy final hero with your Myhero 113 kernel pacth, it seems everything is working..(don't test BT)..

did you notice what radixx has post about kernel implementation patch?
[myTouch 3G, Magic Android Development] :
This is the link to be exact:

http://xdaforums.com/showthread.php?t=574561

I wonder what positive impact will it inject to 32A rom? fully utilized 288MB RAM?? :eek:

that would be awesome.:D
[myTouch 3G, Magic Android Development] Case_:
This has nothing to do with more available memory (we're using it pretty much all as it is, it's not that simple with those 288MB). The only positive impact this patch can have is that you no longer need to alter your kernel sources to build a kernel for 32A, you do it all nondestructively with one kernel config option, so it should be now easy for kernel builders who previously worked for 32B/G1 only to include 32A version of their kernel as well (or vice versa, of course). Which means we should/could see the finetuned custom kernels from G1/32B appear for 32A as well, provided that the kernel builders will bother to do a second compile. And that in turn means we should/could see 32A "ports" of ROMs appear with all the features they have on 32B/G1, therefore rendering this thread and my attempts at porting pretty much obsolete ;)
[myTouch 3G, Magic Android Development] dBartoz:
Yeah, I meant that..

I'm really missing the possibility to perform the g-sensor calibration (impossible to achieve with all the roms I tried) and I read somewhere in the forum that the calibration actually works with the latest MoDaCo roms on 32b..

So maybe that could be worth porting..
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
this works in the evil v3 hero rom, running the myhero 1.1.2 32a bfs kernel on the first page of this thread.
[myTouch 3G, Magic Android Development] Case_:
There's also kernel package specific for eViL v3 there as well...
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
when using that kernel my phone would sometimes not "wake up" when I would push a button. the keys would light up and then nothing. would need to pull the battery. So far I have not had this happen with the myhero kernel port that you did.
[myTouch 3G, Magic Android Development] Case_:
When you say "myhero kernel port that you did", do you mean the package under "Repackaged 32A kernels" or under "Experimental 32A kernel packages"? Just to be sure we're talking about the same kernel - I'm using my own kernel (= "Experimental") with MyHero 1.1.3 and I do not see any problems like this, and the kernel in evil v3 package is the same (although MyHero doesn't use compcache by default, eViL Hero does, so maybe there's some kind of problem with it - Cyanogen himself said he'll probably stop using compcache because it is buggy).
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
The issue occurs when I use your Evil and MyHero experimental kernels.....if I go to the repackaged myhero kernels either bfs or non bfs I don't have this issue. And I've only had this issue with the Evil Rom.

On the main page of Evil's Hero Rom there is a line talking about how someone helped him fix and issue with the phone not waking up, but doesnt say what they did but I'm guessing its to do with the kernel.
[myTouch 3G, Magic Android Development] dBartoz:
Are you sure it really works?

If I am not mistaken, I already tried that combination and I got the UI saying the calibration was correctly carried out, but in fact the sensor had excactly the same offset as before trying to calibrate (looked like the new settings were actually not saved)..

Sorry for asking you to, but could you please double check if the sensor calibration actually works, not only the GUI?

Thanks!
[myTouch 3G, Magic Android Development] Case_:
I've updated my kernel with Cyanogen's BFS304, tweaked a few kernel settings and bumped its version to 1.2 and added the kernel packages for Drizzy's Final Hero 1.0 and SenseHero 1.0 (compcache by default). I've also updated the package for eViL Hero 3 with my 1.2 kernel, so you may try it to see if the wake problems are resolved by any chance (but I didn't do anything specific to fix it yet, it's just that maybe some of the changes could have an effect on this).

Also, the 1.2 kernel is compiled using the new EBI1 patch by Zinx - works like a charm!

I'll try to update the other packages as well soon. Maybe it's me, but this 1.2 BFS304 kernel seems a bit more responsive to me (especially with Drizzy's Final Hero, I'm actually impressed by how responsive it is together). Also, I'm finally playing with non-BFS kernel as well, so there might be an option between BFS and non-BFS soon (if I see any improvements over BFS kernel)

I've tried to get the MoDaCo Hero ROM working on 32A, but it doesn't fit into system partition withou modding, and I'm not sure I want to try to squeeze it there (time issues again). We'll see.
[myTouch 3G, Magic Android Development] ichijin:
nevermind...
[myTouch 3G, Magic Android Development] :
Thanks Case_, it's nice to see this thread is still alive, hooray!!!

looks like all other ROM 'cookers' are working pretty fast and tireless lately as I can see the updates coming in more frequent manner than before.

thank you so much I'll be trying the evil300 with bfs304 in a short while ;)
[myTouch 3G, Magic Android Development] cadetnudt:
The Sense Hero going without G-Sensor……
[myTouch 3G, Magic Android Development] dBartoz:
I'll be checking out this stuff and let you know if the g-sensor issue gets fixed..

Thanks for your work!
[myTouch 3G, Magic Android Development] Case_:
Ooops...looks like I somehow missed compiling sensors drivers into 1.2. Will fix ASAP, this affects all of the packages with 1.2 kernel.

Sorry about that! And thanks for reporting.
[myTouch 3G, Magic Android Development] :
oops....I just flashed evil300 v1.2 bfs304 and saw this :(

can u use a different name(eg. _fixsense) when it's updated so I don't get the same kernel again? thanks :D
[myTouch 3G, Magic Android Development] Case_:
I've just uploaded the fixed packages. They're marked (and named) as 1.2.1, so there should be no confusion, I hope.

Again, I apologise for my stupid mistake.
[myTouch 3G, Magic Android Development] cadetnudt:
Warmest hug for you!!
[myTouch 3G, Magic Android Development] cadetnudt:
...G-sensor Still not working....
[myTouch 3G, Magic Android Development] Case_:
Please, be more specific. What ROM? What kernel package? I've just tried Sense Hero with 1.2.1 package and G-sensor most definitely works for me now (switching landscape/portrait works now - not on home screen, of course - and also Google Sky Map works just fine).
[myTouch 3G, Magic Android Development] cadetnudt:
Sense Hero with 1.2.1 package，maybe I should try more……thanks you very much for your patients..:-)
[myTouch 3G, Magic Android Development] cadetnudt:
It works.Thanks for your great job!!
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
Just wanted to let you know that the combo of SenseHero 1.0 by ccyrowski and your SenseHero 1.0 2.6.29 BFS-304 32A v1.2.1 kernel are running great. I gave up on the evil rom for now as i kept having that issue with it not waking up. I did take the lock screen from it though as I hated the stock hero one. lol. Thanks for all your great work.
[myTouch 3G, Magic Android Development] Case_:
There's not much great work going on, really (well, at least not by me, I just compile and package, for the most part), but you're (all) welcome anyway ;) I'm glad it's useful for someone.

I'll try to see what the problem with eViL ROM sometime not waking up is, if/when time permits.
[myTouch 3G, Magic Android Development] :
UP

the 32A kernel for senserom1.0 works perfectly with its rom, many thanks to Case_!!!!!!!!!

but it's not as slick as I experienced with Hero3G v0.7 + evil300 I wonder why or it is just my *illusion*..
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
any chance you could create a bfs 240 kernel for both the senserom and the evil rom?? all the reading I've been doing is saying that its alot more stable and may get rid of the not waking from sleep on the evil rom.

thanks
[myTouch 3G, Magic Android Development] Case_:
A chance for kernel package for these ROMs without any BFS at all is quite high, I've got the "BFS-less" kernel compiled already and I'm testing it these past few days to see if it's worth creating another set of porting packages. For BFS 240, not so much. Right now I'm trying to get the new official Sense UI dump working with my kernel and my preferred setup, so all of the little free time I have goes into that.

Did you try disabling compcache on those ROMs to see if it isn't caused by it? Both eViL ROM and Sense Hero use compcache by default. As I've said, I've been using my kernel with MyHero 1.1.3 (no compcache by default) for days and didn't encounter this problem at all, so it seems to me that unless it's caused by something in the ROM itself, it probably should be compcache related.
[myTouch 3G, Magic Android Development] HuMpS 97 DoHc:
I did try disabling it on the evil rom and still had issues. haven't had the issue yet with the sense hero rom though. The part i'm really dissapointed about right now is the fact that the official sense ui dump is out and made for 32a and yet there isn't a single rom for it yet without having to install a patched 32b version and then patching it back to 32a, seems strange to me :S oh well. i'll keep using the sense hero for now.
[myTouch 3G, Magic Android Development] Case_:
Well, as I've just found out while trying to get the official Sense dump running and figure out the differences between eugene373's Official Sense UI ROM for 32B with update for 32A, his 32A update uses my kernel package anyway ;) Why oh why didn't I notice this sooner, could've saved me a lot of time figuring how to run that dump on my own...oh well.

So if you use his ROM with his 32A update, you pretty much get the ROM I would make if I did get the Sense dump running. It might be weird to flash the 32B variant of 32A ROM and then reflash it back with 32A update, but the result is the same as if you'd just flash 32A version directly.