yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] erasmux:
Ok, so if I understand you correctly, all we need to do, is to fork the CM .34 kernel, port and fix the five board-hero*.c files and everything will work :D

Seriously, I will be very very very happy if you succeed in doing this. It sounds very easy and will free up my sleep hours for something else (maybe even sleep ;)). And I am not being cynical, I really would be happy if someone finds a simpler way or for that matter any way to get the .34 kernel working on our heros well.

Do note, that for example HTC did change in the .29 for hero much more extensive changes than just the board-hero*.c files. But I am sure they did this only because they were bored and it ain't actually necessary.

Also Elemag to get it working to the point it is now, had to do more extensive changes.

Is it too bold to ask on what do you base your claim, because I am wasting a lot of time because when trying to actually do the port I do not find it be correct.

On a related note:

Elemag: where did you get the files for your two major commits: 0acc37 and 775311, many of these files are very different than the ones in .29 hero kernel?
[Hero, G2 Touch Android Development] Hacre:
Probably need the headset stuff too.

My proof is in the fact that the very similar to the Hero development MSM7200A devices work just fine on 2.6.3x. HTC/AOSP broke a lot of kernel rules with 2.6.29 that are finally being put right. The phone specific drivers should be made to work with the 2.6.34 ABI, not make parts of the 2.6.34 ABI act like the broken and non standard 2.6.29 ABI.

Yes, we can fudge it all to get something that compiles and works. If that's all you want to do, then go right ahead. However getting it right will a: encourage development from a lot more developers in the future, b: will make it easy for anyone kernel savvy to debug/improve and c: done right has an excellent chance of being permanently supported in all kernel versions going forward, as it will be accepted into the main msm-kernel tree.
[Hero, G2 Touch Android Development] erasmux:
I agree with you theoretically. First I am not sure if Elemags changes haven't already broken using this source tree for other devices. Secondly, I think that currently its a big enough challenge, at least for me, just to get it working. If and after we get it working, we can try to see if we can clean up the changes so they can enter the main CM trunk but this can be a project of it's own (again at least for me).

Well enough philosophical talk for me....
[Hero, G2 Touch Android Development] Elemag:
The first attempt at porting was based on board-hero* stuff from .29 and stock cm-kernel. Initially I made a lot of modifications, together with Hacre and we got into deeper and deeper problems. However we were both on the opinion that Sapphire is a device almost identical to the Hero and it would be probably easier to base the port on it. So the first major commit is board-sapphire* renamed to board-hero*, added the new radio, added some Hero specific things and removed some Sapphire specific ones.

The second major commit is ported display, keypad, the notoriuos not-working touchscreen and more that I don't remember.

It won't work on another device for sure.

That's exactly what I think. Even if we can't clean it up soon, a successful .34 port will give our Heroes an year more of use cause the next Android will use .34 kernel.
[Hero, G2 Touch Android Development] flipy:
What configuration are you using?

Could you upload it to github?
[Hero, G2 Touch Android Development] erasmux:
There is a link to the github on the main post.

Use the hero_defconfig.
[Hero, G2 Touch Android Development] bonesy:
Looking at Q&A RE:PSfreedom.....it needs a .34 kernel for the usb drivers.. The usb is working on this WIP so would psfreedom work? Anyone got a compiled kernel that i could try out??
[Hero, G2 Touch Android Development] erasmux:
I can send you one this evening, but what do you plan to do with kernel which the touchscreen does not work and probably many other things?
[Hero, G2 Touch Android Development] xangma:
Just use it to jailbreak the ps3 I imagine =P Not even sure you need the touchscreen
[Hero, G2 Touch Android Development] Arasthel:
It won't work at all. This kernel is 2.6.34, that's true, but it still uses the old usb drivers, not the msm72k ones.
[Hero, G2 Touch Android Development] Waerloche:
Will try to get more help

I have a connection with PPCASM who worked on PSP, Hyperscan, and N64 Applications. He is well versed in Linux Kernals and is very interested in this project as a whole. I will see if I can get him to assist on the Hero Kernal, as that is the device I have.
[Hero, G2 Touch Android Development] Waerloche:
Also I forgot to mention that in my case I am not using the Hero as a phone. Its just a spare mobile device that I have used for Wi-Fi access and to Download files for computer repair projects. So the functionality of anything unrelated to USB, SDCard, and those operations neccessary for PSJailbreaking aren't of any concern to me personally.
[Hero, G2 Touch Android Development] bonesy:
Ah ok thanks, i was gonna try it using a Magic with kernel .34.im guessing that will be the same situation
[Hero, G2 Touch Android Development] erasmux:
If someone thinks they have any use for this, here is the compiled version of what we got so far (like I said touchscreen does not work and maybe other basic stuff too):

http://www.megaupload.com/?d=E2ZOHQF5

Note that this is not an update zip, hopefully those who have any use for it know what to do with a boot.img file. Note the boot.img was prepared with the ramdisk from Froyd.
[Hero, G2 Touch Android Development] Waerloche:
Thank you for posting this - I have been waiting all day as nobody in the psfreedom irc seems to have a clue as to what is up and what is down. (in reference to htc hero). It seems that the focus is on writing drivers for Iphone OS.
[Hero, G2 Touch Android Development] Waerloche:
ok maybe im too stupid to be helping on this project - but i cannot get the img file to mount or open in any shape or form (MagicISO, & WinImage)
[Hero, G2 Touch Android Development] blackplatypus:
actually the 2.6.34 at least in this state does not work for the ps3jailbreak because it is still relying on msm_hsusb as you can see in the mach-msm/htc* files, probably adjusting the psfreedom code to the msm_hsusb (if that is even possible) is the fastest way for psfreedom to work.
[Hero, G2 Touch Android Development] :
Hehe yeah. The boot.img is flashed on the hero in an update.zip or via some commands in fastboot (I think) or adb. As far as I know it's the core of the kernel or whatever to say (I don't know may be completely wrong :p) and the files that comes along with it are modules used as "help" files to the core? Also I think there is needed some special commands in the update-script to flash such an image :) Again I might be completely off but I'm just assuming and I have never read about this :D
[Hero, G2 Touch Android Development] Waerloche:
I want to help with editing this stuff or at least getting us somewhere better than we are now. Do we have any source files that I can browse through to do some comparative analysing with?
[Hero, G2 Touch Android Development] SwatMaster:
Cheers Riemer! :)

Will try it after my Java exam :P

Sent from my >>Cronos<< Hero
[Hero, G2 Touch Android Development] brat.haneq:
@riemervdzee

Hi there

I flashed brand new Elelinux-7.0.0-RC0-Hero-v0.7, and after initial boot I flashed Your kernel. So far - so good.

I'm unsure what features are kernel related, and which are rom related, so I'll probably mix some things ;)

So far:

- loading LEd (green + red) Works (although I believe that with Floyo the led was a bit more intensinve)

- keybacklight Works

- WIFI/Mobile data Works

- GPS Works (I launched google maps, fix was very quick, haven't used any navigation though)

- I'm using build-in cyanogen mod frequency thingie, set up for 352 - 576 ON DEMAND. I hope it works ;) Should I install set CPU to monitor the frequency ?

- general speed - yeah, could use some improvement (especially with scrolling in app drawer - I'm using adw.launcher from the market. But overclocking to 691 helps A LOT)

- video recording Works

- photos Don't work. Preview is there, but after You try to capture the photo - it freezes with preview on the screen. It's responding to home key, so You don't have to do anythign drastic such as pulling the battery.

For now I'll use it as a daily ROM, so if You need to test something - let me know ;)

PS. Yeah, I know that a LOT of people will ask - 1.3.5 patched angry birds works!;D

PS2. LINPACK with settings as above - 3,276, 3,332.

PS3. Linkack with 691/691 performance - 3,738, 3,818.

So not a big improvement in Mflops, quite big improvment in smoothness of scrolling.

EDIT:

Calls Work, just had a short conversation ;) Also receiving calls - work.

Trackball notifications Work (missed calls, SMS notification).

Edit2:

- battery at 61%. 7 hours, 30 mins since I unpluged. wifi off, mobile data - off. aprox. 6 mins of talk time, 2 sms sent, 2 received. But I'm calibrating the battery, so the result can be better tomorrow.
[Hero, G2 Touch Android Development] Dr34mc4tch3r:
Ok, here are some results using cm7 nightly #20 with max652min352 cause min264 gave wakeup problems. Flashed with armonra 1.7.0.1 after wiping cache and dalvik cache.

- no red light blinky led when battery is running low

- wake up problems overall

- sometimes doesnt wake up at all and needs battery removal

- wifi 3g and gps working but navigation isn't working but might be rom related cause I didnt test it before flashing the kernel.

- video recording works fine, photo not but thats old news as photos were a problem since the first custom kernels AND roms.

- I find scroling actually not that sluggish in LP app drawer.

- Games are slow

- linpack +- 3.7 where first +- 4.6

- quadrant +- 220 when first +- 365

- battery uses 19% < 1 hour!

All things first tested with fly 12a before flashing. But i think this kernel has the potential.

Hope i helped and good luck riemer
[Hero, G2 Touch Android Development] elelinux:
Up and running :D come back with test results,awesome Reimer :D
[Hero, G2 Touch Android Development] brat.haneq:
I have red led saying plug charger.

unfortunately it means, that batery is in red, so less than 24 hours of uptime.

But great work anyway !:)

cheers!

brat.haneq
[Hero, G2 Touch Android Development] brat.haneq:
I am getting google talk authentication fail.. but all Google synchro works.. could be ROM related, though
[Hero, G2 Touch Android Development] riemervdzee:
Thanks for the reports so far lads :) Keep them coming.

I've done some tests yesterday for camera and speed, however no luck :-/

Getting an idea of where the problem is at though, will investigate it later. Got the next week off, so I can focus on this one more.
[Hero, G2 Touch Android Development] brat.haneq:
I flashed 0.7, in order to return to previous kernel. I dont have Google talk errors now, so it is most likely kernel related.
[Hero, G2 Touch Android Development] riemervdzee:
Works here on Elelinux 6.2.0 RC0.

Could you get me a logcat/dmesg output when trying to open the app, when you test out the kernel again(if ever)?

Also if you got real issues, I prefer to have them at: https://github.com/riemervdzee/cm-kernel/issues

To keep the things here a bit clean ;)
[Hero, G2 Touch Android Development] brat.haneq:
hi there !

Don't think that I'm finished with testing, just needed camera working this week ;)

Regarding the google talk - I noticed that the icon of wifi signal, or H icon haven't changed color when using Your kernel..And after few minutes of being connected to the internet I got a notification that I there was a problem with google talk. I haven't launcherd the app, just got a notification.

Do You need specific ROM we should test the kernel with? Perhaps this would improve bug raports, as they are easier to recreate.

Cheers

brat.haneq
[Hero, G2 Touch Android Development] petsasj:
Hey riemer,

Hate to bump this up, but perhaps i'm too drunk to care atm :P

Unfortunately, it seems like devving for the 2.6.35 kernel has come to a halt. It's quite a shame, after all this work you've put into it.

I was getting concerned seeing you have no activity last few days. Please let me know if i (and others i'm sure) can provide something to help further development of the kernel.

I hope you're doing OK IRL.
[Hero, G2 Touch Android Development] Hacre:
*Looks at thread title*

*Looks at today's date*

So how quickly do YOU think this should happen then?
[Hero, G2 Touch Android Development] ggrammer:
What these things don't happen in a couple of weeks?

well now I am distressed

depressed

sad

sleepy

dopey

and doc...

wait what were we talking about again?

ps. hey Nin have you been giving a hand to reimer? cause if so then on behalf of the remaining hero community thank you, your releases were always like christmas.

If not then thanks anyways for the work you put in on the hero
[Hero, G2 Touch Android Development] petsasj:
I actually took a look at riemer's github and saw his latest activity was 2 weeks ago. Thought I'd give some moral support.

I don't see anything wrong with that. And certainly I didn't demand anything.
[Hero, G2 Touch Android Development] swatsbiz:
Maybe need to choose your words better then?
[Hero, G2 Touch Android Development] petsasj:
Jesus. What's so wrong about asking how something is turning out? You're all attacking me as if i flamed or demanded anything.

Re-read my posts and rephrase them to your liking.

If you look hard enough, you'll see my cunning plan to take over the world, as well.
[Hero, G2 Touch Android Development] riemervdzee:
Just so you all know, I'm ok ;) Thing is, I've been too busy with other things.

And when I find the time to work on this project, it seems every attempt I do is failing.

I hardly got any pointers left where the problems might be, as mentioned in the issues list:

https://github.com/riemervdzee/cm-kernel/issues

And it seems my debugging a kernel skills are lacking quite much.

And come on people, it is Sunday. At least be good today ;)
[Hero, G2 Touch Android Development] Hacre:
I haven't. I had some goes at porting early on but the sad truth is HTC's "code" for their drivers is largely terrible, the old 2.6.29 kernel structure they use breaks almost every kernel guideline there is and the fact that a Hero was no longer a phone I even used it all just became far too much :effort:.

Working on the Hero ROM side was fun though.
[Hero, G2 Touch Android Development] rdejager:
Yea its sunday indeed a good day, except for the weather here XD. Man its crap :P
[Hero, G2 Touch Android Development] ggrammer:
hey reimer, we all appreciate the work you put in and I think you've done a tremendous job. I was just reading some of the issues on your github and I was wondering with the battery drain issue what are the main power usages in your battery usage under about phone?

there should be some way to determine how much extra power is being drawn and hopefully find a specific feature with that same power draw.
[Hero, G2 Touch Android Development] Hacre:
This won't show the kernel power management not operating correctly or cpufreq not doing its job properly. Which are probably to blame.
[Hero, G2 Touch Android Development] dkelley:
hey Hacre,

good to see you :-)

how's your new phone working out?

sad about this kernel but good to see some clear common sense in this thread.

cheers

Don
[Hero, G2 Touch Android Development] mr.bang:
Hi folks i'm working on camera and cpufreq maybe next week i could pull source on my github.. with current source the camera app crashes but camera still working using debug tool in /system/bin/ . The camera driver sucks but if anyone helps me maybe we take no long time to get camera working
[Hero, G2 Touch Android Development] riemervdzee:
Just so you all know, yesterday I had an uptime of 26 hours with 42% batt left. Although I don't trust my battery stats for a penny, it is quite decent.

What I meant with that issue is that there is a higher-than-normal power-usage when the screen is powered on. However I don't really consider it as critical for now. More of as an annoyance ;)

The camera and speed are one of my biggest pains atm.

@mr. bang. Good to see you are working on it :) Quite a honour actually, hehe. I will contact you on github tomorrow.

I got a trick where I can get the camera working for a little while, maybe it is of any interest. It has to do with those GPIOs. I request them at init, and remove them at exit. Then re-use the same all of the driver. It then works for quite a while actually, but then just stalls after some time. No clue why.
[Hero, G2 Touch Android Development] ggrammer:
That sounds promising...how did the last half of that battery cycle go?

Good to hear Mr.Bang is on the case...we are lucky to have such talented folks who still have heros...by all intents and purposes this phone "should" be long dead. Great job to all of you!
[Hero, G2 Touch Android Development] Hacre:
I can only think of incorrect CPU clocking or bad brightness control on the display as an explanation for abnormal battery use while screen on. Might be worth looking there.
[Hero, G2 Touch Android Development] ggrammer:
your probably not too interested in the hero much anymore but it is reassuring that you check in every now and again. I really do miss your release notes :D
[Hero, G2 Touch Android Development] riemervdzee:
Just pushed a small update of the lcd driver. Not sure whether this will make any difference (think not).

Anyway after investigating a little deeper in that directory, I found something:

https://github.com/riemervdzee/cm-kernel/commit/fb8904a444121465fd02acecfcfb9285e41414b4

Reverted it from the main, as it messes up the colours badly. However it gives a nice speedboost. Still not up to par to the .29 kernel (getting 37fps), but 33.5 fps on neocore ain't bad.

Linpack is still around 4.3 mflops though. Guess there is something eating cpu cycles.

Scores are at 691 mhz, performance governor
[Hero, G2 Touch Android Development] ggrammer:
are you running the kernel overclocked?

those numbers are really good actually the only time I got close to 5Mflops with linpack is when I cranked up to 710Mhz and had some other tweaks like data2sd.
[Hero, G2 Touch Android Development] riemervdzee:
Yes, I got all scores running at 691 mhz performance governor. Sorry, should've added that :)
[Hero, G2 Touch Android Development] mr.bang:
Hey guys still working hard on camera driver ! Think there are problem with i2c driver and i discovered that this kernel miss an include/i2c-msm.h HTC header, that is in legend-2.6.35 and discovered error in mach/system.h ! Near to the solution! Yep! The camera problem include no focus-autofocus issue!
[Hero, G2 Touch Android Development] riemervdzee:
Ok, the mdp changes from legend have been re-added in a nicer way.

Also I noticed I now have to set the RGB values for the panel, now the screen ain't garbled up any more :)

I'm quite happy with this you know. Now everything feels much smoother... Still not up to par with flykernel for example, but still. :)

I will be off until Monday though, so I won't post a new build soon or work on things.

edit:

lol, we posted almost at the same time.

Nice! Could you start pushing the changes so far a little? I'm really interested and want to take a look at it (to see what I missed, haha)
[Hero, G2 Touch Android Development] mr.bang:
Ok i will push it! Need 15 mins;)
[Hero, G2 Touch Android Development] ggrammer:
You guys both rock!

Along with everybody else who has contributed to this work.
[Hero, G2 Touch Android Development] mr.bang:
changes pushed on my github experimental repository! check it! now while taking photo camera preview shouldn't stucks on screen but app crashes with code -512 error, maybe it is caused by bad i2c driver or maybe by minor errors on kernel porting process. Not so bad news i think. now i have an error to work on and to fix up.
[Hero, G2 Touch Android Development] DonNaWaF:
cant wait to see full working 2.2 sense in hero ..
[Hero, G2 Touch Android Development] riemervdzee:
I'm unsure how this would help Android 2.2 sense, as I think the problems are more at the ROM side.

------------------------------------------

Anyway to keep you all updated: the camera is a ***** ;) I finally found out why earlier versions was so unstable though. There is a difference if you flash the kernel to the phone then boot, and when you fastboot the kernel.

When fastbooting, it works the first time until the camera is closed. I guess some clocking thingie or so? :-/
[Hero, G2 Touch Android Development] riemervdzee:
Version 0.2.0 is out!

After exactly one month I decided I should upload a new build for you all ;) Especially seen there are some nice changes. The kernel works out quite neatly for me now :)

Change-log

Changes of last version:

Renamed the kernel to Las_Venturas. Meaning good fortunes or similar in Spanish, it is also a city in San Andreas (/advert). Version numbering is also in the kernel string nowadays.

Speed increase! whoho, wrecked out the screen-blitter from the legend .32 sources. Seems to be a lot faster, might be even faster than the .29 one(the blitter that is)? Still, we lack a few speed increases at the .35 kernel to cope with the .29 one. However it is quite nicely :)

Camera works kinda... I can take one picture, then I need a reboot hehe. After failing, you still can preview things and make camera recordings though.

USB works again

Full log:

https://github.com/riemervdzee/cm-kernel/wiki/Changelog

For download, see Opening Post. Enjoy!
[Hero, G2 Touch Android Development] bluepinkpanther:
Great news ;)
[Hero, G2 Touch Android Development] kiljacken:
You R awesome br0!!
[Hero, G2 Touch Android Development] Dr34mc4tch3r:
I have been wondering what the .35 kernel brings to the Hero. I'm noobish when it comes to kernel. I know that the drivers are updated, but does that also boost performance or compatibility? And is it so that we need a newer kernel in order to get along we the development of android in general? I will try this this week ;)

cheers!
[Hero, G2 Touch Android Development] riemervdzee:
Mostly functionality/compatibility. While some newer drivers are a bit faster than the ones found at the .29, it seems the original htc kernel has some optimalisations for the Hero we haven't implemented yet. In general the .29 is still faster.

I hope in the future newer Roms can be easier ported with the .35 kernel though, as interfaces change quite quickly the latest few android versions. However I ain't a ROM builder (need a 64 bit system to build android nowadays), maybe ask those lads a little ;) I've heard that a villain dev has some issues with getting Sense 2.2 Rom to work on the hero with the .29 kernel. No idea whether this kernel might be a solution.
[Hero, G2 Touch Android Development] arcblade851:
Riemer, I just want to say thank you for doing so much for the Hero scene. What some devs thought would be impossible, you are making happen.
[Hero, G2 Touch Android Development] Wupper:
Great work Riemer! I´ve also mirrored the radio: here :).
[Hero, G2 Touch Android Development] riemervdzee:
I guess I got a lot of spare time ;-) Unfortunally I've found yet another speed increase today :P Shouldn't have released it that quickly I guess hehe. Boot times are specifically shorter now, it has been cut down to 1/3th of the original times... I'll check out it further tomorrow, maybe a new build soon.

Thanks! it has been added to the first post again :)
[Hero, G2 Touch Android Development] keyra74:
not bad, i'll keep it installed on my elelinux 1.4 for a while since it runs without slowing me too much