yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] Elemag:
adb is working really fine for me (using latest CM6 build), but the high load average is causing serious lag. If you're patient enough your device will eventually reboot into whatever you want. The kernel is very, very stable and can recover from the extremely high load of almost 12, and it is quite responsive even at that point. I'd expect it to hang forever, but that's not the issue

However, after spending a lot of time on it, I don't seem to understand what is causing the high load. A very early starting process, for sure, but as of now I only have a list of things that DON'T trigger it...

My recommendation is to test that kernel, as it is at least 95% functional and it surely is better starting point for Gingerbread than the .29 was for Froyo.
[Hero, G2 Touch Android Development] petsasj:
Is it that usable? I thought it was around 70% and didn't want to cause any issues so I didn't try it so far.

I will flash it a bit later as well, then.
[Hero, G2 Touch Android Development] dkelley:
I'm about to test it on cronos gb

update: it's not the massive fail I expected considering I didn't wipe anything and threw it onto a gb I've been using for 24 hours already. it's at the 2nd boot animation now which is certainly better than anticipated.

of course you know why I'm really doing this - I want to see if angry birds lite runs now LoL.

update 2: wow, the kernel's running with gingerbread on my hero. how bizarre is this? phone info: android version 2.3.1. kernel version 2.6.35-9.

seriously bizarre to see - I never thought the day would come.

I'll start trying things out but immediate impression is that yes, it works and isn't broken in any obvious ways just yet (keeping in mind the parts of gb that don't work yet etc).

update 3: intended use (angry birds lite 1.3.5 beta 2) = fail with same FC as in cronos kernel. meh... didn't expect it to be any different.

update 4: bluetooth doesn't turn on with thsi kernel (probably a known thing, but I'll note anything I find).

update 5: wifi works great. also no obviuos big slowdowns etc in use although keyboard seems less responsive now, although still quite usable. I could have had that before though without knowing for sure.

ok, back to fly12a now since I need working bluetooth (and yes it works again with fly).

but it was much better than I expected. I do get the subtle feeling that fly results in more responsive UI but I can't say for sure as I didn't really measure or make any intentional memorable mental notes about it. WAIT, yes I did, the keyboard thing. same app, same situation, the keyboard IS quite a bit faster to respond and do it's screen updates in flykernel on gb than with the 35 kernel. (sorry for bad news, although maybe it's just debugging code in your kernel at the moment, right?)
[Hero, G2 Touch Android Development] docertabum:
I tried that combination of Cronos GB @ .35 as well and additionaly I had wake-up issues. Is it possible to change frequency over 614MHz?
[Hero, G2 Touch Android Development] dkelley:
it won't be the 614 speed that's the issue, it'll be the lower speed that you want to increase. but it may not be a simple clock speed issue.
[Hero, G2 Touch Android Development] docertabum:
yes, ofc. I meant it the way that I always run my ROMs @710MHz and I couldn't change it with SetCPU... :(
[Hero, G2 Touch Android Development] riemervdzee:
Always love your detailed reports :) WiFi works straight out of the box aye, while I'm keeping getting issues to get bluetooth to work. Might have another go at it this eve, as I get a bit sick of the HTC masterpiece, the microp_i2c driver.

Speed will be optimized ofc. But I hope you can understand it isn't our first priority at first ;) also, there are some debugging logs/checks going on ofc.

It will be in the future :)
[Hero, G2 Touch Android Development] petsasj:
I just flashed this along with the Cronos Gingerbread 0.0.6 ROM.

As dkelley said, i never thought i'd see in the About phone details that my kernel would ever be 2.6.35.9. Its a bit of a shock.

Mind you my report is not exact, as i am not using a fully functional 2.2 rom, but an experimental 2.3 rom. My report is as follows:

1) Smoothness is ok-ish, not great, but not bad either. Disabling all animations helps out loads by the way.

2) There is a small delay when calling your phone. I'd say 2 beeps (sorry this might sound silly but it's the only measure i have! i hope you understand what i mean by beep :P) Sound comes a bit earlier, then screen. But with time this eventually gets better, just thought you should know.

3) As mentioned, the keyboard's quite a bit laggy =/ If you can type fast (which i'm not particularly good at) you can type in all the text, then it all appears at once after a while :D

4) Bluetooth doesn't turn on, but you already know that :P

5) I believe tethering works, going to check in a minute with my laptop.

6) battery levels look ok-ish for me, don't know what you mean not reporting correctly. When i installed the rom i was at 85% battery, now that i have a usb connection, it reports 79% and going up (81% by the end of my report)

7) Well Camera doesn't work, neither for you, nor the rom, so double fail :P

8) Audio jack doesn't work

9) I am not getting that usb recharging issue you and erasmux reported a few days ago, don't know if it's resolved or not, just thought you should know

10) Reboot into Recovery works absolutely fine with me. 3rd time this works. Reboot to bootloader as well.

11) LED's and lightsensors of course don't work

12) Rotation doesn't work neither for the ROM nor the kernel (BMA150 is used in Nexus One, maybe have a look?)

Overall i am quite satisfied with this. Speed is a bit of bummer at the mo with the lagginess in transitions and stuff. But apart that i think its 80% functional.

Camera was broken in the beggining of froyo as well, but Cyanogen fixed it for the Hero, Magic and G1, perhaps have a look at his solution, if you haven't already?

Thank you so much for your work so far. It's been amazing! Please go on :)
[Hero, G2 Touch Android Development] riemervdzee:
@petsasj, thanks for the report :)

Elemag found some issues regarding the speed. We fixed a few of them already, and its running nicer every day but we could always use more help ;)

Could you please test whether WiFi tethering is working with the native app? Would be great if it works straight out of the box :) (means we have one plus over the current .29 kernels, hehe).

I've been working on the microp_i2c driver whole day, bit of documenting though seen the mess of it. Think its safe enough to enable the green/red leds as default, but the lightsensor and trackball led causes some null pointer issues. Unfortunately I don't think it'll work for Android 2.3 though. Anyway when this driver is (partially?) working, we can get the bma150 and H2W (audiojack) to work as these rely on this lil bugger.
[Hero, G2 Touch Android Development] petsasj:
I didn't have the USB drivers installed yesterday, but i will install them today and i will test the kernel on Floyo 1.2.0 to check everything.

I will post in about 6 hours my results :)
[Hero, G2 Touch Android Development] petsasj:
Riemervdzee one last thing before i actually deploy my laptop, something i've been curious about.

It's about Bluetooth. There's a bit of a dark area as to what chipset the htc hero uses for bluetooth. Others say its the brf6300, but in the latest fix by radug, which is a sticky, for AOSP roms, the brf6350 libs were used. Now, if that's the case, I know for a fact that the brf6350 has an FM receiver.

Here's the proof: http://focus.ti.com/pdfs/wtbu/ti_bluelink_6_brf6350.pdf

What do you think?

edit: Here's the link for the BRF6300 as well.
[Hero, G2 Touch Android Development] Dr34mc4tch3r:
New OpenGL

Awesome to see this getting ported to our old but respected hero. I did a tiny bit of research and concluded that our qualcomm chip is capable of running opengl 1.1 whilst now running 1.0. As a non-coder, I ask how hard is this to implement in the kernel if it is even possible.

Greetz and good luck guys

en.wikipedia. org/ wiki/MSM7600A is where I read about openg ESl 1.1)
[Hero, G2 Touch Android Development] petsasj:
The Hero uses the MSM7200A chip, not the 7600A.

And the OpenGL ES 1.1 is ROM-related, not kernel - related. Have a look at the CMDA thread to learn how to do it.

Here: http://xdaforums.com/showthread.php?t=899801
[Hero, G2 Touch Android Development] vido.ardes:
As far as I know the BRF6350 supports Bluetooth 2.1 where as the hero only supports Bluetooth 2.0 so I would assume we have the BRF6300. I have a full service manual for the hero and it doesn't mention it so without pulling the phone apart and looking I don't think we can know for sure
[Hero, G2 Touch Android Development] petsasj:
Just an update, tethering works! (IF i have done it correctly that is :P)
[Hero, G2 Touch Android Development] dkelley:
go you guys make regular flashable signed builds and if so where do we download them, or do you just provide new links in this thread as you go along somewhere?

I haven' seen a link to a new build since the one I tried a few days ago but I know you're all working very hard on this.
[Hero, G2 Touch Android Development] riemervdzee:
Well, why wouldn't they take advantages of all the things brf6350 has to offer? Don't think that HTC is thát evil ;) But if you got any leads that it is indeed a brf6350 chipset, I'm always interested to hear.

Great! :)

How I do it is creating a kernel/zImage and use fastboot to run it. I already got the modules etc. flashed. It wouldn't be a big effort to get a flashable out of it though.

However haven't had much progress the last few days. Been bashing at the microp driver, but it keeps rebooting when he doesn't like you. Maybe I or Elemag will post one later, to keep you flashing-addicts happy ;) Only advantages of the current status and the former flashable is; that it wakes up better, and has a bit larger cpufrequency table.
[Hero, G2 Touch Android Development] kiljacken:
Just checked the firmware folder of floyo, and it contains firmware for BOTH brf6300 and brf6350?!?

That's kinda strange isn't it??

Going to look further into it tomorrow..

-- Kiljacken
[Hero, G2 Touch Android Development] riemervdzee:
New flashable for you junkies:

http://www.riemervanderzee.com/download/hero35-003.zip

Changes from last flashable:

- Green, red, and jogball led should work (lightsensor still is an arse though)

- updated to linux kernel version 2.6.35.10

- Some drivers go better in suspend (framebuffer and akm(some-numbers)), the large wake-ups are gone

- Different cpufrequency table. Not really happy about it, as interactive hangs @ 35xmhz sometimes. But we are getting there.
[Hero, G2 Touch Android Development] Elemag:
I will make flashable kernels on major updates.

As for the bluetooth, your rom should contain both firmware files for it to work as you expect.
[Hero, G2 Touch Android Development] petsasj:
Small bump ^^

Was wondering how things go? I am checking frequently your github riemervdzee, how's progress going? :)

Need anything new tested out?
[Hero, G2 Touch Android Development] riemervdzee:
Not much progress I'm afraid, tried to port the h2w code yesterday/today but no luck yet. It'll hang when you plug a jack into it :P Same happens if we use the lightsensor code. Elemag is suspicious that the debugger is faulty.

Made a few changes to the microp driver as well, doesn't hang any more when having a 35-jack device. So we are getting there step by step, problem is that I got no clue which route to take next hehe ;)

Debugging is hard when the whole system gets crazy. E-mailed kernelzilla about it, maybe he has something useful to say about it.
[Hero, G2 Touch Android Development] petsasj:
Hoping for the best! Good luck. If there's anything i can assist with (testing or something else) let me know.
[Hero, G2 Touch Android Development] Elemag:
Latest build:

http://www.multiupload.com/0O8QX94NEX
[Hero, G2 Touch Android Development] :
I flashed the one riemervdzee posted earlier. All working fine, except my PC can't detect my phone; no USB connection/no USB debugging connection that is.

Once I flashed back FlyKernel, the USB connections are back.
[Hero, G2 Touch Android Development] riemervdzee:
Ah yes, I forgot about that one. Thanks for remembering me, I should write a list with all non-working things hehe ;)

I'll see what I can do, believe it got broke somewhere. Seems things don't reach userspace no more, as adb and charger just work.
[Hero, G2 Touch Android Development] docertabum:
does it affects apps2sd as well? thx
[Hero, G2 Touch Android Development] riemervdzee:
It shouldn't, as by "userspace" I actually meant the android one. The linux scripts should function properly, as things get mounted as specified. Not to mention that it is just the sd-card thingie who gets not notified in android, same counts for the debugging thingie. While both just work internally.

Anyway reverted two earlier commits taken from the CM-kernel, which causes the problem. Now it works again. Leaves us with what somewhat older code, which makes updating a bit harder in the future. But I prefer to have things working ofc ;)

New build:

http://www.multiupload.com/4CK3CG0Q68
[Hero, G2 Touch Android Development] petsasj:
Any luck with kernelzilla?

So far, just to outline what's not working:

- Camera not working (is this perhaps a rom fault?)

- Lightsensor

- Bluetooth

Is that it? :P
[Hero, G2 Touch Android Development] riemervdzee:
Nope, haven't heard from him yet.

I started to track all non-working hardware at a wiki page:

https://github.com/riemervdzee/cm-kernel/wiki/Non-working-Hardware

Let me know if anything is incomplete
[Hero, G2 Touch Android Development] Ian_4614:
any idea why app called 'calltrack' is not working with this rom ??
[Hero, G2 Touch Android Development] riemervdzee:
First it is a kernel ;) Second, are you sure it works with other kernels? If so, please post dmesg and logcat logs. Can't really imagine it is a problem with the kernel, as it uses stuff more related to the rom.
[Hero, G2 Touch Android Development] dkelley:
haha just saw this - thanks from a flashing junkie :D
[Hero, G2 Touch Android Development] imachine:
Great job guys!

But maybe you can cooperate with CyanogenMod - they have made an attempt at bumping the kernel, perhaphs with more people it will come forward faster?

Try here :

https://github.com/loxK/android_device_htc_hero/issues#issue/11

Also, Gingerbread could use a more recent kernel -

http://forum.cyanogenmod.com/topic/13144-cm-700-rc0-pre-alpha-gingerbread-testers-needed/

Cheers!
[Hero, G2 Touch Android Development] tristan202:
This may be a daft question, but what roms does this work with? I have tried flashing it, currently running cm6.1 nightly build 198. Upon boot, it suddenly reboots into recovery. What am I doing wrong?
[Hero, G2 Touch Android Development] riemervdzee:
Thanks for the heads up, posted a message but then I noticed it is 6 months old :P

Anyway, every hero ROM could use a higher kernel number I suppose ;)

The ones I post should work with all ROMs (uses Koush any-kernel method, which creates a boot.img based on your current). I think Elemag posted a flash which is based on cyan boot.img.

However it could be that you need a ROM which is flashed with Amon_Ra 1.7.0.1. For a newer yaffs driver supported. As Erasmux pointed that one out earlier this thread.

Or maybe your phone can't handle 691? It boots at that speed, don't really like this though. Might get changed in the future.

Its a bit odd it reboots in recovery though.
[Hero, G2 Touch Android Development] tristan202:
I actually had Amon Ra 1.6, but just updated to 1.7.0.1. Will try again. I know it isn't an issue with 691, as my phone can run at 710.

EDIT: Still the same issue with updated Amon Ra. I tried running a logcat, but it isn't booting for long enough to get anything.
[Hero, G2 Touch Android Development] riemervdzee:
The sentence is a bit cryptic, you actually need the current Rom (not kernel) flashed with amon-ra 1.7.0.1. or did you tested that out this fast already? :P

Edit: Tbh can't say it is worth the change right away. Although the kernel is really stable, it lacks some speed and not all HW is working.
[Hero, G2 Touch Android Development] tristan202:
I misunderstood you. The rom isn't flashed with 1.7.0.1, just the .35 kernel. Not sure I want to wipe and reflash to test a kernel right now. But thanks for the info.
[Hero, G2 Touch Android Development] riemervdzee:
Changes since last build:

- turned out vsync, should give a nice speed boost. Elemag found this one out :)

- found out why our normal board files never booted. It was the cpld stuff, we always used the sapphires values on the .34/.35 builds until now. We now use a htc specific gpio-expander. Removes some speed hick-ups greatly as well. Thanks to Feeyo

Overall it is getting a fast kernel. Sometimes it spikes a bit, but we can tweak those away (bfs, io-sceduler, maybe some other).

I have some ideas about blue-tooth today. Which I will fight against this eve (need some testers if I get it running though, if...)

Anyway I will post a new flashable this eve, so you lads can get as enthusiastic as I am right now ;)

edit:

Maybe with this gpio-expander fix the cmda Hero will also run on this kernel. Contacted Decad3nce already about it. Would be nice to have some more devs at this little bugger ofc ;)
[Hero, G2 Touch Android Development] dkelley:
pardon my french but holy **** that's exciting!
[Hero, G2 Touch Android Development] thantos2024:
Nice to see things moving along, thanks to the devs for there hard work, I think this kernel with GB is going to help keep our poor heros going for a while yet.
[Hero, G2 Touch Android Development] imachine:
Well, I just sold it mine today and traded it for a Desire, so I reckon that is the way to go, but amazing job anyway guys :)
[Hero, G2 Touch Android Development] dkelley:
when you get bored of your desire, PM me and I'll trade you my hero for it
[Hero, G2 Touch Android Development] shields398:
anyone no were i can find a flashable update for the latest amon recovery?. cheers!.
[Hero, G2 Touch Android Development] thantos2024:
Easiest way is to use the clockwork rom manger on market.
[Hero, G2 Touch Android Development] shields398:
cheers mate!
[Hero, G2 Touch Android Development] riemervdzee:
New flashable:

http://www.multiupload.com/3LBTGUH538

Got bluetooth working and is included in this build :) the mentioned speed ups -of course- as well.

I also added more BT end-points than the normal .29 based ones.

Let me know how it works out, or if you can connect to anything at all using bluetooth ;)

I hardly can test it as I got no bluetooth stuff around here hehe
[Hero, G2 Touch Android Development] kiljacken:
You guys are awesome!!
[Hero, G2 Touch Android Development] sibbor:
Ah, hello there ;-)! Will give it a test soon. Just gonna do a couple of more assignments... examination time soon (again).

Btw, any recommended ROM to test with this kernel? (Running Feeyo's 0.0.8 beta Gingerbread ROM)

EDIT: I've got WiiMotes (Nintendo Wii controllers), a Plantronics headset and a Sony PS3 headset to test BT functionality with.
[Hero, G2 Touch Android Development] riemervdzee:
Really, let me know how it works out :)

As for the ROM, the kernel-flashable is using Koush anykernel method. It should be Ok for all ROMs.
[Hero, G2 Touch Android Development] imachine:
;) I know the HERO is a super cool device, and I will most likely miss the call/hangup buttons ;)

But other than that, there is nothing to really keep me hanging much - I added about 100$ to the desire, so I think it's not a bad deal :)

I'll be with the HERO fans by heart tho ;)
[Hero, G2 Touch Android Development] dkelley:
well said :-)

desire is like the hero mark 2 - and uber powerful. nice buy!

I hope the desire's rom community becomes as faithful, warm hearted and long lasting as the hero's has become recently. It certainly looks active based on the xda forum.
[Hero, G2 Touch Android Development] riemervdzee:
Yeah it is a nice device. My brother also gots it. Maybe thats why I started getting custom roms, I wanted to be faster hehe
[Hero, G2 Touch Android Development] dkelley:
desire is one of the few running gb really well as an alternative rom, isn't it? some nice phones can't even run froyo (samsung - I love those phones but LMAO about froyo upgrade issues).

So if your intent is to try and get us as close to desire's GB capabilities on the hero, you will have friends here forever.
[Hero, G2 Touch Android Development] riemervdzee:
Still got a 13 month contract till I can pick another phone :)

Now you know why I like Feeyo that much, he is screwed with a long-ever-lasting contract as well :P
[Hero, G2 Touch Android Development] Bornin:
And God bless you both for that :p

Nice job with the Kernel Riemertje ;) about to flash it.
[Hero, G2 Touch Android Development] vatvedt:
Here in Norway, it's against the law for the phone company to have a phone-contract running for more than 12 months. So when (or if) you buy a phone with a contract, it's for 12 months max. :)

I never buy them with a contract though. The phones cost about the same. It's just not spread over 12 months. :D

Oh, and GREAT work on the kernel! Even though I've bought a Desire HD, I'm still hanging on to the Hero as secondary. For now.. :) Can't really let it go that easy for some reason. I want to know how far you guys can take it. :)
[Hero, G2 Touch Android Development] dkelley:
same here - technically another couple of years at least on this phone but will obviously be upgrading before then :-)
[Hero, G2 Touch Android Development] dkelley:
this sounds crazy, but I swear that after flashign this kernel on feeyo's gb rom the display has a very subtle greyishness to it.

I know I know, but is there any chance that it's changing how things could be displayed such as contrast or brightness parameters? maybe it's as simple as it was really bright in his kernel and isn't as bright in this one, both using auto-brightness settings.

thats likely what happened, but it's worth mentioning just in case.

anyway, after the very slow very long initial boot and launch of all widgets etc, as it gradually sped up more and more, it's now almost as fast as with the .29 kernel. screen updates in fast moving things like LP horizontal scroll bouncing (and particular with the app drawer vertical scrolling in LP) is lower framerate than with .29 kernel, but it's WAY better than it used to be.

overall very cool. I'm running down to get my bt earpiece now to see how it works.
[Hero, G2 Touch Android Development] Bornin:
lost phone connection

It's slow

what's with all the governors?

Cheers,

72
[Hero, G2 Touch Android Development] dkelley:
phone connection's perfect for me.

after setting things up fully after flashign this kernel and giving my phone a good 15 minutes of gradual workout until it was "freed up" in the ui, it's got quite fast screen updates now. It's getting faster the more I'm using it which is pretty cool :-). certainly as good as many of the other roms out there with other kernels I've used aside from the slightly slow screen updates.

The screen framerate is fast enough to live with if, for example, this ends up giving us camera or other cool features in the gb rom at some point :-)

I'm being really picky here by the way, it's very good any many wouldn't notice if it wasn't for the gb rom being so fast with the .29 kernel.

my cheap generic chinese bt earpiece works perfectly so far although I've only checked voicemail with it, not actually spoken into it for others to hear etc.

Connection to bt was perfect, as fast as in any other rom/kernel combo. :-)

bootup wasn't as slow after the first reboot but still not as fast as with the .29 kernel just yet.

great Work!!
[Hero, G2 Touch Android Development] dkelley:
wifi signal was zero though for entire time after I enabled wifi, but disabling and reenabling wifi has given me wifi signal now. Odd...
[Hero, G2 Touch Android Development] dkelley:
camera is just as white blank as with .29 kernel in gb rom by the way. I'm sure this is known, but was worth a try.