yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] wbervoets:
Had GPS reboot issues with Google Maps and Navigon with all kernels and all ROMS I've tried (Froyo or Gingerbread ROMS).

Sometimes I could navigate for an hour before it rebooted. I have found out if I don't overclock my Hero CPU then it doesn't reboot. (I haven't had a single reboot).

I'm using Elelinux-6.2.0-Hero-Speedmachine-v5 and LasVenturax 0.6.0 and smartass2 governor. Froyo is more speedy on my Hero then Gingerbread.

Also LasVenturax 0.6.0 feels faster then LasVenturax 0.6.2 for me.

Battery life - I haven't scientifically tested it but it's good enough for me. (I'm using JuiceDefender Ultra)

I haven't tried FlyKernel 13 yet.

Wim
[Hero, G2 Touch Android Development] matte3560:
Is anyone else having problems with the g-sensor? Mine stops working after a bit. I normally dont use it, but it's annoying when you actually want to use landscape.

I'm currently runing elelinux' speedmachine v5 rom, which is based on android 2.2.1. I've had this issue on other roms with this kernel aswell.
[Hero, G2 Touch Android Development] Pitel:
Broken sensors

Me too. Not only g-sensor, but also compass. Logcat gives me:

E/Sensors ( 239): Couldn't open /dev/akm8973_aot (Operation not permitted)
E/Sensors ( 239): ECS_IOCTL_APP_SET_XXX failed (Bad file number)
E/SensorService( 239): Error activating sensor 0 (Bad file number)
E/Sensors ( 239): Couldn't open /dev/akm8973_aot (Operation not permitted)
E/Sensors ( 239): ECS_IOCTL_APP_SET_XXX failed (Bad file number)
E/SensorService( 239): Error activating sensor 1 (Bad file number)
E/Sensors ( 239): Couldn't open /dev/akm8973_aot (Operation not permitted)
E/Sensors ( 239): ECS_IOCTL_APP_SET_XXX failed (Bad file number)
E/SensorService( 239): Error activating sensor 2 (Bad file number)

It always works for a while after reboot, so HW is ok.
[Hero, G2 Touch Android Development] dkelley:
lv 0.50 is ancient. 0.62 is the current build but the first post I think only has 0.50 or something like that. so scroll down that first post a long way or into the second or third post to download LV 0.62 which is a more current version.

however all of the LVs after 0.47 aren't all that stable compared to fly13. but the can be faster, at least with a gb rom they can be faster than fly.
[Hero, G2 Touch Android Development] Lirasina:
But on 2.1 roms use Fly13
[Hero, G2 Touch Android Development] J.K Nilsson:
Elelinux 2.1 Reloaded 2001-06-26 runs like a dream on Lv0.50. :cool:

J.K Nilsson
[Hero, G2 Touch Android Development] cartman333:
Whats up whit the updates Riemer :D or is this the final version?
[Hero, G2 Touch Android Development] dkelley:
I've had stability issues, sometimes with fatal results (reflash required, phone won't boot otherwise) using 5.0, 6.0. 6.2. I haven't used the latest 6.2a gb kernel though I suspect it's the same.

compared the fly 12 these lv kernels were much faster on GB sense roms.

but with fly 13 the differences in speed aren't nearly as dramatic, and fly13 is perfectly stable. however sense gb roms still can be a little faster with LV.

I personally use fly on all roms other than sense gb roms which are really only experimental toys anyhow as far as I'm concerned.

I love this rom and what it can do, but there are a couple of niggling issues still that seem to coincide with my running this rom instead of fly13.

too bad, and I do hope it can be finished, but I have a feeling the hero kernel devs are mostly gone to other platforms now.

so this might be as good as it's going to get?
[Hero, G2 Touch Android Development] riemervdzee:
For issues with the camera/rotation try to wipe dalvik cache. (you should always do this when switching from a .29 to .35 or visa versa). I could not reproduce both bugs (after running it for about 3 weeks without a reboot?)

Anyway I've decided to get this project roling a little again. I still got the hero phone for another 3 months and I decided I should get atleast a 1.0 version out ;) More info will follow.

If you got issues with the current kernel, please say so. I'll take them into the srcs review etc.
[Hero, G2 Touch Android Development] schlehdorn:
Hey riemervdzee,

SebastianFM wrote some time ago: "There is a bug in HTC kernel 2.6.35.10 display driver for Magic/Hero. When I fixed it in my kernel port for Magic, 2D scores in AnTuTu grows from 150 to 300. I must tell riemervdzee about it."

Can u PM him about this?
[Hero, G2 Touch Android Development] riemervdzee:
Thanks for the heads up :) I'll write him a pm

With the 0.5 version I get a score of 286/290 @ 691 perf. So I guess either the hero isn't affected by the bug or it has been fixed already (there have been quite some changes on the display-driver since the 2.6.35.14 version). Still, maybe his fork has some other goodies we can use :)
[Hero, G2 Touch Android Development] Habarug:
Good to see you back riemer :-)

sent with love from me to you
[Hero, G2 Touch Android Development] r34c7:
Mount as disk drive through usb doesn't work in villainrom 13 and i think it's a general problem with modifications of the stock sense rom (android 2.1) in combination with 2.6.35 kernel ?

glad to see you continue developing this kernel. it is amazing! the only thing which stops me from using your kernel for everyday purposes is the usb mount problem (since i am a sense fan, and i can't stand the slowness of GB sense roms).

keep up the good work! :)
[Hero, G2 Touch Android Development] riemervdzee:
The USB-driver was quite changed between .29 and .35, yes. But the we've added the usb-mount switch to have atleast usb-mount support for sense roms.

So yeah, it should work. Wiped dalvik etc? Otherwise I'll try it out soon at the specific ROM (it did worked for me at a 2.2 sense rom earlier) USB-tether ain't supported for Sense ROMs though.
[Hero, G2 Touch Android Development] riemervdzee:
Las Venturas 1.0 RC1:

http://www.multiupload.com/HEGKP53R81

md5: b037b807e5a9131f03bc8a2d48e29966

Just a version which is getting quite stable imho, still not worthy of getting 1.0 just yet.

Still have a bit of a problem with the cpu running at 19mhz when playing music, it should ramp up a little more. Currently using the same values as Eran, so it seems the overal cpu-load is too low (which is a good thing :P).

Anyway all suggestions etc. are welcome :) I would really like to see whether GPS and the camera are stable. To get usb-tethering, the instal procedures of Eran still count.
[Hero, G2 Touch Android Development] aca89:
Thanks for this. Just tested it a little bit. Camera works fine including video recording. No lag at all using Lirasina's VLC. Could you remind me how to enable usb tether or point to solution?

Cheers
[Hero, G2 Touch Android Development] riemervdzee:
Try and see whether this fix still works for you:

http://xdaforums.com/showthread.php?p=17008727#post17008727

Otherwise convince your ROM-cooker to change:

BOARD_USE_HTC_USB_FUNCTION_SWITCH := true

to false. But then it would break tethering on .29 again.. :P
[Hero, G2 Touch Android Development] aca89:
Downloaded the cm6 patch, flashed and it works :D. Thank you very much.
[Hero, G2 Touch Android Development] riemervdzee:
Great :) let me know how the kernel works out
[Hero, G2 Touch Android Development] sabers105:
just downloaded and flashed it. using deck rom to test. camara, gps and usb-tethering are working great for me! thanks riemervdzee !
[Hero, G2 Touch Android Development] davrave:
Thanks for the update VDZEE (of the sea). Like you say, the kernel feels great But.... the music is doing funny things like stuttering. Looking forward to the final version and hoping that someone can supply a rom where the music does not stutter.
[Hero, G2 Touch Android Development] sabers105:
I use Deck rom(CM7 GB). music is normal with playerpro.:D
[Hero, G2 Touch Android Development] riemervdzee:
Could the people who have music problems test the following one out? (RC2)

http://www.multiupload.com/X7ZN85V91K

md5: 459c2bc3b5083e593b55b9479e526cdc

A temporary fix would be to increase the minimum cpu-freq
[Hero, G2 Touch Android Development] ryanraven:
Testing now will report back in the next 24 hours with results :D
[Hero, G2 Touch Android Development] CSL00:
RC2 feels smoother for me than RC1 (coming from LV 0.5), neither gave playback issues. Also phone seems not to heat up as much (my main concern with LX 0.6.2).
[Hero, G2 Touch Android Development] ggrammer:
good to see you back riemer, I flashed rc2 and this has been the most responsive lv yet. I haven't tried music at 19mhz yet but so far everything else seems to run better? I will put it through its paces and let you know. Thanks for your hard work.
[Hero, G2 Touch Android Development] Habarug:
Will give this kernel a try again :)Does it use the same smart updater as flykernel? So you can rename it to set the frequencies values?
[Hero, G2 Touch Android Development] Lirasina:
There I was ready to try this kernel. The RC2 one. But yea lost my phone.

Then I had the smart idea like any one else does. call it so you can hearr it.. Sometines you just forget if you can't do something... :S

---------- Post added at 11:46 PM ---------- Previous post was at 11:37 PM ----------

Found it :D

and what works with the smart updater, well this one does not have it but flash fly13 with the set speeds and then flash LV 1.0 RC2. it will save the flykernel speeds and use those on LV :D

Atleast for me XD
[Hero, G2 Touch Android Development] saj222:
Cool! Nice find.
[Hero, G2 Touch Android Development] harut56:
Does this kernel support swap?I mean native linux swap patrition e.g. if I'll format some patrition of my SD card into swap will it be recognised without using other apps?
[Hero, G2 Touch Android Development] ChosSimbaOne:
Link for RC2 is not working any more any1 got the RC2 how can upload it?
[Hero, G2 Touch Android Development] CSL00:
http://www.mediafire.com/?6whh3b3u51f1l9b There you go.
[Hero, G2 Touch Android Development] dmestriner:
Just flashed this kernel because I was getting fed up with lag in flykernel13. This one seems more responsive so far! We'll see how it goes after a while of use :)
[Hero, G2 Touch Android Development] riemervdzee:
I finally got some time again for deving the next week. Since the OneX sources ain't out yet I decided to play a bit again with the Hero kernel. Are there still people who use it btw? ;)

Cheers, R
[Hero, G2 Touch Android Development] :
yes, thank you
[Hero, G2 Touch Android Development] troublecro:
knock yourself out,we're still using it ;)
[Hero, G2 Touch Android Development] riemervdzee:
Hehe nice, what are the real problems so far with it? I noticed a decrease of stability(speed mostly) after a certain uptime. Probably due the memory allocator. Gonna see if we can get more io power in general as well
[Hero, G2 Touch Android Development] nickholtus:
maybe an idea to update to the latest 2.6.35 sources??

will increase speed and fix some bugs
[Hero, G2 Touch Android Development] riemervdzee:
Will have a look at it aye. First some more basics and trying to get uart debugging going. If the last one works, I might try 2.6.38 again (it should give me earlier debug, but don't pin me down on it.. :P).

Cheers, R
[Hero, G2 Touch Android Development] lolo7291:
As for me, there is no compcache or swap or any stuff like that in the last kernels and I think our hero would rock better using it.

In fact any last ROM needs a lot of ram, thus multitasking needs more ram thanks to swap or compcache that is not implemented in the kernel

By the way, there is only one kernel working fine for Sense 3.5 ROMS, I don't remember which one but it's used one .sense as an example
[Hero, G2 Touch Android Development] ggrammer:
That would make you my new hero.
[Hero, G2 Touch Android Development] riemervdzee:
Better would be to base everything on the .34 kernel posted in the first post. Elemag made a good attempt at porting the board files to it basing on a sapphire kernel.

Anyway I think I'm going to play a little with a newer driver for the i2c busses on a normal .29 kernel found in the .32 legend kernel released by HTC (as a proof of concept). After that it might be interesting to get it working on this .34 kernel.
[Hero, G2 Touch Android Development] NervGaz:
It was the port from the sapphire board files that looked a bit messy to me which is why I was gonna have a poke at the .29 board files. If nothing else just to get a better grasp of exactly what needed sorting. We'll see what happens, real life takes up a lot of time.
[Hero, G2 Touch Android Development] riemervdzee:
Anyone still bashing his keyboard against this kernel?

Tried a simple combination of CM kernel 2.6.35 kernel and Elemags port found here: (removed rep. sorry lads)

However no luck yet. Same problems. It was kinda a test to rule out errors in the i2c layer (just guessing stuff here).

Anyway I'm kinda getting clueless what might be the problem. Could it be that the irq is set wrong or so? (mapped wrongly in board-hero.h ?).

Edit: kinda new to linux kernels anyway, so don't start bashing when doing something wrong hehe ;)
[Hero, G2 Touch Android Development] Hacre:
No it's a HTC can't write drivers for toffee issue combined with ABIs changed so much between .29 and .3x coupled with the HTC can't write drivers for toffee issue that meant you're pretty much stuck with re-writing the Hero drivers from scratch, or at the very least trying to port drivers from similar phones, which none of us could be bothered to do on a completely outmoded hardware platform.

Knock yourself out. :)
[Hero, G2 Touch Android Development] riemervdzee:
Yeah most stuff is... crap, microp_i2c takes the cake though.

Anyway I'm stuck to this phone for another one year and four months, so basically I kinda want to do something about it. And learning linux-kernel in the progress, what else is greater than this ;)

But yeah, maybe you are right... it is quite a mess. But still, got any pointers where we might start looking? TS is kinda important, and well we'll just forget about the leds at first...
[Hero, G2 Touch Android Development] Hacre:
The general consensus when a few of us looked at it, was keep the board-hero header stuff and try to port the already included trout/sapph drivers to those specifications from 2.6.34, or 35 or even 36 now, depending on what's available in the aosp tree.

Or at least use board-hero.h as a template. A lot of it is so scarily similar. Funny you should mention the i2c stuff, since that's what finished me off, after we got most of the board-* stuff working. For that, I have no pointers I'm afraid

Just remember to use lots of kernel debugging and code some reboot to hboot loops in (I forget where, but there's some code in the pm.c iirc that should give you a hint on reboot codes), make use of kern_last log etc.

Apologies if that stuff isn't entirely accurate, it's been months. Good luck. :)
[Hero, G2 Touch Android Development] erasmux:
At the time, I also tryed quite a bit to get the touchscreen driver working - don't recall much but at the bottom line didn't make much progress. I assume there is some way to get it working, but this one is a tough one.

A better place to start might be cyanogen's experimental kernel, I think they already did some of the porting necessary for similar devices there. Yet another place to look are kernels for other similar devices - mostly the magic which is very close to the hero and has newer kernels working for it (at least the 2.6.32). You can also look at the heroc forums, where they also have some ongoing efforts to run newer kernels on the heroc.

In the long term, I also hope to find some more time to invest in this.

Please update us if you make any progress, one way or another.
[Hero, G2 Touch Android Development] riemervdzee:
You mean the already ported .34 ones right? Just to get things straight hehe ;)

That the drivers aren't working are a bit ockward I think, as the mahimahi phone uses the same drivers also. However I guess they work for some magical reason.

The driver bails out at the first i2c transaction takes place. Is there a way to tell for sure that the gpio stuff works properly in the current .34 board files?

I was thinking of getting another kernel first and build stuff for it aye. But yet again... This one is soo close :) Heroc one is based again on this .34 port though. Not sure whether it is working, will contact the initial starter of it.
[Hero, G2 Touch Android Development] Hacre:
Mahimahi doesn't even remotely use the same board files, mahimahi is the Nexus One.
[Hero, G2 Touch Android Development] riemervdzee:
My excuses, I meant that they use the same touchscreen drivers I believe. That these still work at the .34 ('n up) for the Nexus One while all-of-the-sudden breaks for the hero, is kind of the mysterie for me.
[Hero, G2 Touch Android Development] Hacre:
Oh, the synaptics driver, yes, they're the same and it shouldn't be that one that's causing problems.

If memory serves there are three drivers overall that deal with the touchscreen, one of the board-hero files (or possibly more than one of them), an i2c driver and the synaptics one. The synaptics one should be fine.
[Hero, G2 Touch Android Development] riemervdzee:
I see, I kinda got confused when you mentioned porting drivers to the .34 spec.

I first did try to check out the board files some weeks ago aye, as they differ the most of the original ones. Especially the header file?

Don't think the I2C sub-system is to blame as well. I believe HTC has not changed it too much in their sources, and my .35 experiment was with this intention as well.

Anyhow... I found something interesting after you mentioned the hero board files again :)

I never got the synaptics driver running however I do now with this commit:

https://github.com/riemervdzee/cm-kernel/commit/229017fdcfdcf8387a8b5e9e7a5a7786be2ff56c

I think the touchscreen now finally wakes up properly, and everybody gets happy with that I suppose.

Before I always got something like this:

http://pastebin.com/BJhwfKrG (just ctrl + f on "msm_i2c msm_i2c.0: error, status c8") so I2C transactions failed.

However this is the full log of my fork atm:

http://pastebin.com/910vmfA7 (ctrl + f on "synaptics_ts_probe: Start touchscreen")

As you can see the driver now fully loads. However still no working touchscreen. Could it be that the irq given to the I2C driver is also invalid?

Especially seen that "HERO_GPIO_TP_EN" had the wrong value (which is in somekind of banking mechanism now?) gives me bit of the creeps. How can we guarantee that every other definition is right in the current .34 one?

Edit: Well freaking good news, I got the touchscreen working! :D The irq is indeed set wrongly, I for now hardcoded it in this commit:

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

Will come up with a cleaner solution soon, first some sleep ;) Although this is a nice finding, it kinda proves the current board headerfile can be unjust.
[Hero, G2 Touch Android Development] petsasj:
That is awesome news mate.

Really excellent work. Thanks for your effort
[Hero, G2 Touch Android Development] ggrammer:
Huge props go out to riemervdzee!

making some progress on this kernel as he is learning about linux kernels.

two thumbs up.

:)
[Hero, G2 Touch Android Development] brat.haneq:
Keep up the great work!:) i believe that most of us are holding breath waiting for .34. Please continue Your "magic" ;)
[Hero, G2 Touch Android Development] lost101:
Dear Santa,

Please will you leave a 2.6.34 kernel for hero in my stocking this year.

All the best,

Lost101 :)
[Hero, G2 Touch Android Development] Crypto_ahash:
You are the man Riemer! :)
[Hero, G2 Touch Android Development] rionline:
haha...i am getting excited ;)
[Hero, G2 Touch Android Development] TsunKit:
You've given us Hero owners hope!

love for riemervdzee
[Hero, G2 Touch Android Development] riemervdzee:
There are compcache and zram modules included. They need to be loaded on ROM/userspace level though. Maybe Erasmux got some tutorial about it. Otherwise I'll try to dig a little.

Cheers, R
[Hero, G2 Touch Android Development] gkillerx:
Great to see some improments in this kernel! Only problem for me was the speed with this one. Like you mentioned, after some time the speed is really bad.
[Hero, G2 Touch Android Development] nickholtus:
to enable zram in rom:

how to enable ZRAM?

Code:

su

mkswap /dev/block/zram0

swapon /dev/block/zram0

u can create a init.d script to auto-enable it
[Hero, G2 Touch Android Development] gkillerx:
after running mkswap I get:

mkswap: Can't open '/dev/block/zram0': No such file or directory.

checked in /dev/block/ and only the folder vold is present. Is it save to just add a new folder?
[Hero, G2 Touch Android Development] riemervdzee:
Probably the module needs to be loaded first. Can't recall the mod name straight away, but you can load modules with the cmd modprobe. Am at work now, will check it soon. Might be "modprobe zram" though

Cheers, R
[Hero, G2 Touch Android Development] nickholtus:
i get error module "zram" not found

i think it isn't fully added.

i will try to add it by myself

EDIT: ok, i have edited defconfig to CONFIG_ZRAM=y (first it was CONFIG_ZRAM=m)

maybe that will aneble it.

compiling now
[Hero, G2 Touch Android Development] riemervdzee:
Probably zram isn't the full name.. :)

Cheers, R
[Hero, G2 Touch Android Development] nickholtus:
ok, it is adding zram files to the kernel.

it is the 2 time i compile it (first time without editing defconfig) 1 time it didn't say anything about zram now after editing defconfig it is adding zram files

---------- Post added at 02:41 PM ---------- Previous post was at 02:21 PM ----------

damn, sd card broke.

i can't test new kernel now.

i will upload it.

can anyone try:

if it boots.

if zram works:

try this;

modprobe zram (in terminal emulator)

su

mkswap /dev/block/zram0

swapon /dev/block/zram0

edit:

here is the kernel: http://www.mediafire.com/?vb0ne971am16rt0
[Hero, G2 Touch Android Development] riemervdzee:
Is this one built from the last sources btw? I cherry-picked some htc desire fixes, but it might break some things like camera (need some testers! :)).
[Hero, G2 Touch Android Development] nickholtus:
yep, compiled with last sources

edit: can i just push zimage to /boot??
[Hero, G2 Touch Android Development] Gawis:
Great to see you are picking this one up again :-)

My aunt is currently using my Hero and is very happy with it.

I did notice that CM7 for Hero seems to be demanding for the phone.

Perhaps this kernel can change it.

Sent from my SGSII CM9 with Tapatalk 2
[Hero, G2 Touch Android Development] riemervdzee:
Bit of a 2.6.35 ICS build, happy flashing :)

Las Venturas 1.0.0 RC3:

http://www.mediafire.com/?1cxp7310q4p6e66

md5sum: adee25ead8c10d9a74686a1f8cf2b284

Could really use some testers:

- Stability of the camera for Android 2.3.x or earlier

- Internet connection in general for Android 2.3.x or earlier or the 4.0.x versions. State which one which you are using please

Cheers :)
[Hero, G2 Touch Android Development] nickholtus:
offtopic: can i flash a kernel without a sd card? mine just broke so i can't test my own kernel:P
[Hero, G2 Touch Android Development] riemervdzee:
An option might be to flash to /boot via fastboot (pack it in a ramdisk?), not sure if you need an engineering bootloader though.
[Hero, G2 Touch Android Development] gkillerx:
This can also be used on 2.1 ?
[Hero, G2 Touch Android Development] riemervdzee:
Sure, note the "or earlier" part ;) have fun