yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] arco68:
You can have native USB working, but the rom needs to be built without

BOARD_USE_USB_MASS_STORAGE_SWITCH. Also look in my Tattoo board file for the USB code. This works perfect on the Tattoo.
[Hero, G2 Touch Android Development] waqasr:
Sorry for noob quesiton but I am kind of new, Will

this kernel work for Hero CDMA?
[Hero, G2 Touch Android Development] CraigHardy:
No, use one of your own like...

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

for example :)
[Hero, G2 Touch Android Development] riemervdzee:
Unfortunately no. The kernel CraigHardy posted is a bit outdated I'm afraid (pre 0.4.3).

If you can find a kernel dev for the HeroC, let him contact me so we can get that one updated.

I don't know whether jaybob is still devving?
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, I will check it out when I got some more time. Thanks for the heads up :)
[Hero, G2 Touch Android Development] waqasr:
Thank you for your generous offer.

Even though JayBob has never replied to me on forums or even in

PM because my USB headset was not working on .35 kernel so I wanted

to bring that to his attention but still I will try convey your message to him.

Regards and God bless
[Hero, G2 Touch Android Development] Pich78:
I'm using LV with Elelinux's Gingerbread 3.2.

My battery duration is improved dramatically: from 2 days with GB 3.1 + flykernel to 3 days GB 3.2 + LV.

Thanks for the great job!
[Hero, G2 Touch Android Development] erasmux:
Started testing the 0.5.0 (downloaded from first post and flashed through recovery over Floyo 1.4pre1).

On the good side, it seems very responsive, I really like it performance wise :D. Battery life, as far as I can tell from the very limited time I have been testing seems good.

The main thing I was surprised to find, is that the camera is still highly unstable for me (camera app FCs after at most a few pictures). Here is the logcat:

D/QualcommCameraHardware( 188): requested preview size 384 x 288
D/QualcommCameraHardware( 188): requested picture size 2592 x 1952
D/QualcommCameraHardware( 188): native_set_parm: fd 19, type 21, length 4
D/QualcommCameraHardware( 188): receiveRawPicture: E
I/mm-camera 7x-vfe( 188): VFE_RESET_ACK ctrl->state 10
D/mm-camera-awb( 188): awb_prepare_wb_for_snapshot r_gain 224, g_gain 141, b_gain 196
D/mm-camera-awb( 188): agw_sample_decision=7
W/AudioFlinger( 188): write blocked for 87 msecs, 5 delayed writes, thread 0xdcd0
D/dalvikvm( 609): GC_EXPLICIT freed 2406 objects / 161040 bytes in 89ms
E/QualcommCameraHardware( 188): native_get_picture: MSM_CAM_IOCTL_GET_PICTURE fd 19 error Connection timed out
E/QualcommCameraHardware( 188): getPicture failed!
D/QualcommCameraHardware( 188): snapshot_thread X

I see that some people report no problems with the camera, but that has also been the case with previous LV versions, which clearly had camera instabilities. Am I the only one still having problems with this version?

If and when I have time I will try to investigate this issue more, I am not sure if it is exactly the same issue that previous versions had.
[Hero, G2 Touch Android Development] erasmux:
zImage is just the kernel binary. You need to pack it together with a ramdisk. see a general overview here: http://android-dls.com/wiki/index.ph...ck_Boot_Images

Personally I use a command something like this:

mkbootimg --kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz --cmdline "no_console_suspend=1 console=null" -o boot.img --base 0x19200000

Then the boot.img is the image that you either fastboot or flash to the boot partition.
[Hero, G2 Touch Android Development] Psycho77:
Before someone ask a working zImage for your psfreedom thingie:

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

And the instruction in hmm Italian ?

http://www.ps3underground.net/index.php/?p=256

Im hoping that psfreedom thingie would bring more peoples to fix the .34 kernel and make the touchscreen and other goodies work. As they can use the psfreedom + their phone a the same time :)
[Hero, G2 Touch Android Development] MrNameless:
Hey, i disabled usb drivers of android to use psfreedom!
[Hero, G2 Touch Android Development] maxisma:
You don't need to build a boot.img.

Just flash the kernel via

fastboot flash zimage zImage

Case sensitive!
[Hero, G2 Touch Android Development] erasmux:
Thanks, actually didn't know that and its mighty usefull :D
[Hero, G2 Touch Android Development] Ganii:
Hm,I boot into fastboot and tried this,but i get FAILED <remote: not allow>

First I need unlocked SPL,otherwise it don`t work,right?

I`m on Froyd Villain 1.5 ROM!
[Hero, G2 Touch Android Development] pulser_g2:
Yes, you need to have an unlocked SPL for this. I can do "fastboot boot zImage" on my 004 SPL, but I think the unlocked one is the sure-fire way to do it
[Hero, G2 Touch Android Development] witysimon:
Oh, it's a new knowledge for me.
[Hero, G2 Touch Android Development] Ganii:
Ok,so for flash or fastboot zImage I need unlocked SPL!

Fastboot boot zImage don`t work for me,too!

I have HBoot 1.76.0007 and SHIP S-On!
[Hero, G2 Touch Android Development] MrPappy86:
Any update about the progress?
[Hero, G2 Touch Android Development] carpao:
I saw on the first post's link that the activity is not stopped, but I'm not able to understand what is achieved by now.

Is there some developer that can give us some news about the status of the porting?

thanks also for all the work
[Hero, G2 Touch Android Development] erasmux:
Not sure anyone is actively working on it right now.
[Hero, G2 Touch Android Development] Elemag:
I started this mainly as a proof of concept and despite it's not working, I am satisfied with the results. I stopped working on the port and all Android stuff for a while, cause I needed a lot of time to write my diploma.

Anyway, the .34 kernel port is at the point of porting "microp" driver which somehow is related to the touchscreen. However, HTC have spread microp stuff all over their "masterpiece" and after all Froyo stuff is working with the .29 kernel, it's not worth the effort of further developement. If anyone is interested in developing it, take over.

And at last, I am surprised and a bit disappointed that only two more developers helped out - Ninpo and Erasmux.
[Hero, G2 Touch Android Development] riemervdzee:
I found an atmega-microp driver at the htc 2.6.32 wildfire sources, is it of any use for the Hero?

Edit: This is really promising in my opinion. I just grabbed the 2.6.29 version of the wildfire sources, and their microp driver (microp_i2c.c) is exactly the same as the hero's.

Instead of having a file at:

kernel/drivers/i2c/chips/microp_i2c.c

It is now devided in:

kernel/arch/arm/atmega_microp_common.c

kernel/arch/arm/board-buzz-microp.c

where buzz seems to be the codeword for wildfire
[Hero, G2 Touch Android Development] r34c7:
<spam>

I cannot help in any way for the development of this kernel but i wish to make a point here. It is really really really SAD that no one is working for the port of the 2.6.34 kernel. Porting this kernel WILL mean that we can potentially use our devices in the next year (maybe) with the latest version of Android OS, since it will use this kernel...It is kind of sad to see something like this, even more disappointing than the fact that HTC left the Hero with a 2.1 OTA update and no official Froyo update for it. I am pretty damn sure that the devs in this forum HAVE the skills and know-how to make the 2.6.34 kernel work on Hero flawlessly.

I hope that we will see the development of the kernel reborn...

</spam>
[Hero, G2 Touch Android Development] davrave:
I second that :-)
[Hero, G2 Touch Android Development] riemervdzee:
Well I started to work on it a little, but it is quite time-consuming since this isn't really my matterial. Anyone else still/wanting-to working on it?
[Hero, G2 Touch Android Development] ggrammer:
I'm no dev and I won't assume to know anything about anything, but was just wondering if you have looked at the .34 legend kernel sources released by htc and if they are even of any use to the hero community?
[Hero, G2 Touch Android Development] :
He has. Both Legend, Wildfire and Sapphire.
[Hero, G2 Touch Android Development] NervGaz:
I've had a peak at it and in all honesty looked a bit of a mess. Was gonna have a poke at porting the .29 board files on their own just looking at .32/.34 compared to .29 board files from other devices as reference for any new or removed functions and realised I really don't have the time. Might try to get something done over the weekend.
[Hero, G2 Touch Android Development] f_padia:
Camera was very stable for me when using Salsasense. Even now using OMGFB camera seems very stable. I have just taken 8 pictures one after the other and it had not problems.

Probably unlikely but could it be to do with the froyo -> gb switch?
[Hero, G2 Touch Android Development] erasmux:
I doubt it. Remember these instabilities, are as said "unstable". Sometimes it works and sometimes it does not. I have also had a "run" of about 5 pictures taken without a FC but I think on the 6th it FC (and usually its more like on the first or second for me). But I know that some are effected more than other by this. Many reported very good experience with specific frequencies and such....
[Hero, G2 Touch Android Development] riemervdzee:
With 0.5.0 I've switched to a new base where I haven't had any camera problems yet. It is strange you receive FCs though? Wiped dalvik-cache?
[Hero, G2 Touch Android Development] erasmux:
Works with flykernel so I doubt its a ROM problem.... My current Floyo installation is not the cleanest, so I will wait for a clean installation before I dig further but like I said I will be very surprised if this is a ROM problem.

Just to be sure on which ROM do you find it stable?
[Hero, G2 Touch Android Development] riemervdzee:
Sorry for the short answers, got a massif hangover.

Never

had problems with running the new lv kernels with these 3:

- Elelinux 6.2 rc5

- Salsarom, latest (lv gets included standard)

- currently running with latest ele's 7.1

Only problem I had was yesterday, where auto-rotation all of the sudden didn't worked anymore. Not sure whether it is kernel or ROM related (too lazy to debug, was middle in the night).
[Hero, G2 Touch Android Development] erasmux:
Ok I think it was a false alarm:

a) I managed to get it to FC also with FlyKernel on my old unclean installation (guess it was a fluke I got 20+ shoots off with fly yesterday).

b) Installed a clean installation of Ele's GB and for now it works flawlessly.

Will continue testing this just to be sure.

Now, is it just me, or does camrecorder not work with this kernel? :S EDIT: camrecorder was a one time deal (for now), rebooted and now it works.

On an unrelated note, I think the new LV has a problem with notifications on the trackball. I will look into it, hopefully shouldn't be too hard to fix.
[Hero, G2 Touch Android Development] arcblade851:
On LV 0.5.0, the screen does not rotate after a while, as riemer stated. Not sure what causes it, but I'm on Ele's latest build so far.
[Hero, G2 Touch Android Development] erasmux:
I have been playing around with the 0.5.0 for a bit now. The only bug I found so far is with the jogball notification and I have fixed it here.

The rotation bug I have not encountered - If anyone knows how I can recreate it, I will look into it. The camera problem I had before was not kernel related - the camera does work fine for me with LV 0.5.0.

There are a few more changes I have made, those interested can look at my github - I think none of them are critical and somewhat a matter of taste.

Those interested in a precompiled version of "my" version, here it is:

Las_Venturax-0.5a.zip (generic update)

Any feedback, like always, is welcome.
[Hero, G2 Touch Android Development] schlehdorn:
Nice to see more work on this fabulous kernel from the zen-master erasmux. Will test it later today and thx for the jogball notification fix. It was annoying that it flashes 10times in a sec :)
[Hero, G2 Touch Android Development] puppyko:
Just want to thank Riemervdzee for his work and Erasmux for the .5a version.

I had tested the .5a version on Ele's Speed v4, so far everything just works, no bugs found.

Had also tested the original 0.5 version on Ele's latest GB 3.2 previously and no big issues as well.

I was hoping that the .35 kernel once works would bring our Hero to another level, may be faster response or better battery life. I've seen no difference in performance so far using .35 kernel, while some other users had in fact complained of higher battery drain using .35 kernel.

Now the question is, what advantage does the .35 kernel have over the .29 kernel? May be some new ROMs could be made available if using .35 kernel?
[Hero, G2 Touch Android Development] erasmux:
LasVenturax 0.5c posted on 2nd post of this thread.

I will be happy to hear any feedback about it.
[Hero, G2 Touch Android Development] radix1980:
Hi erasmux,

I am using the latest CM7 rom for my hero. With the default kernel it runs ok, but I installed the "Las Venturax 0.5a" kernel and it worked ok for one day. After one day it became slow, very slow, so I am back to the 2.6.29 kernel.

Does the new kernel fix this issue?

Thank you very much for your effort in this kernel...
[Hero, G2 Touch Android Development] erasmux:
There is no reason for this to happen. Generally I feel the .35 is a bit faster than the .29 one, especially after it has warmed up.

My guess is that your issue is not kernel related, but I could be wrong. Try also the new version and/or the original Las Venturas 0.5.0 from the first post. Please let us know if this problem is persistent. If you do experience a major slow down, I would suggest using a task monitor to check if any app is using your CPU heavily (personally I use and recommend OS Monitor - free from the market).
[Hero, G2 Touch Android Development] radix1980:
Ok,

I'll download the new kernel and I'll post my feedback on monday (this weekend I'll be out).

thank you very much
[Hero, G2 Touch Android Development] radix1980:
Bad news,

I had my first reboot....
[Hero, G2 Touch Android Development] erasmux:
Which kernel? What where you doing? Can you post a last_kmsg?
[Hero, G2 Touch Android Development] radix1980:
Ok,

the las venturax 0.5c,

I have no idea how I can post the kmsg...I am sorry...

Anyway, my rom is not clean...I can't remenber when I did a full wipe....so I am not the right one to post this feedback....I apologize for this....
[Hero, G2 Touch Android Development] erasmux:
If you have a spontaneous reboot it is always advisable to post a last_kmsg, we might find some clues why it happened....

To get the last_kmsg, you need to pull it from /proc/last_kmsg, for example using adb:

adb pull /proc/last_kmsg

Notice, you do this after the reboot (obviously), and it should remain there until the next spontaneous reboot, so you can usually pull it even days after :). I am not sure what happens to it when you change kernels (or ROMs).
[Hero, G2 Touch Android Development] riemervdzee:
Remember to wipe dalvik-cache after installing a kernel if you have "strange" problems!
[Hero, G2 Touch Android Development] nscxp2005:
Does anybody know if this kernel has old style app2sd support?

All the best

NSCXP2005
[Hero, G2 Touch Android Development] erasmux:
The app2sd support is ROM dependent, and this being a generic kernel will not change the behavior of your ROM. Ext 2/3/4 is supported by the kernel (this kernel support all of them).
[Hero, G2 Touch Android Development] riddick541:
I've also had a spontanius reboot with 5.0c, so I've pulled the last_kmsg for you.

I hope you can find the problem.
[Hero, G2 Touch Android Development] erasmux:
Is there anything in particular you are doing when the crash happens? Which ROM? Does it happen with LV 0.5.0? with LX 0.5a?

Thanks.

EDIT: did you by any chance use the GPS while it happend, there is very well known instability with the GPS that results in a similar last_kmsg....
[Hero, G2 Touch Android Development] riddick541:
I'm using OMFGB 1.3.1-r1-B2, and I was just booting my phone just after flashing the kernel. And when I've entered my Pin then the sudden reboot happend.

I've had no problems with version 5.0a or 5.0

Before I flash kernels I always do a dalvik and cache wipe

Edit: Gps is always on, but like I said, I was just entering my pin when the reboot happened
[Hero, G2 Touch Android Development] nscxp2005:
erasmux,

Do you know if the nightly builds of CyanogenMod have app2sd built in?

All the best,

NSCXP2005
[Hero, G2 Touch Android Development] erasmux:
One last question, was it a one time deal or did it happen more than once?

No, as far as I know no CM "offiical" build has app2sd support.

At the time I prepared FlyKernel-12a-CM7-App2SD-Compcache.zip but this was a very long time ago and not sure if it will work on recent builds. Do a nandroid backup before you test it. If it does work, you should be able to flash LV/LX over it and app2sd will remain. If you find that it doesn't work please let me know.
[Hero, G2 Touch Android Development] riddick541:
The reboot happend twice. The first time i had a hard reboot ( Hero coming on the screen), and the second time it was just the boot animation.

I don't know if that means something ?
[Hero, G2 Touch Android Development] nscxp2005:
No it does seem to work.

I just stays on the cyanogen boot logo and doesn't go any further.

Would you be able to help me keep app2sd support or would it be best setting it to install to the SD card?

Thank you for your time.

All the best,

NSCXP2005
[Hero, G2 Touch Android Development] erasmux:
I will need to look into it. I will see when I have time I will release another bundle of LV/LX with the app2sd for the updated CM7.1 nighties. But this may take me a few days....
[Hero, G2 Touch Android Development] nscxp2005:
ok, thanks.

I will use external install from Cyanogen settings for the moment.

All the best,

NSCXP2005
[Hero, G2 Touch Android Development] erasmux:
Las venturax 0.5d:
[Hero, G2 Touch Android Development] f_padia:
I'm using las venturax 0.5c with latest OMFGB build and I have had no reboots so far. I haven't used gps so I don't know if that causes instabilities but it's been ok for me

Using interactivex too
[Hero, G2 Touch Android Development] rdejager:
I found a bug with Las_Venturax 0.5D My phone is 100% charged but the led is still orange. Running Floyo 1.4 Pre1

For the rest. nothing to interesting to report :P
[Hero, G2 Touch Android Development] mar9118:
USB Tethering does not work for me, using Floyo 1.4 pre1, it was working fine with original Flykernel, hope this can be fix as Las-Venturas/Venturax is much faster :)
[Hero, G2 Touch Android Development] frige:
Using 0.5d here on Eles 3.2. Everything working fine here. Takes some days to comment on battery consumption. Use InteractiveX with 176M - 633M. Statistics show a high

percentage in 176 - which at least looks promising.

Had a walk with GPS tracking in the morning for 2h: was working stable (both in screen on and in screen off mode)

Thanks for the kernel update

frige
[Hero, G2 Touch Android Development] erasmux:
Very weird, it works fine here (also using Floyo 1.4pre1 and 0.5d - well now 0.5e, but it worked with 0.5d also).

Since I don't have a data plan, it kind of hard for me to test tethering. Here's a long shot:

EDIT: In case it still does not work, please describe exactly what problem you see - do you get an error message? Can you attach a logcat when it fails and a logcat when it works (flykernel).
[Hero, G2 Touch Android Development] puppyko:
Haha, I'm a liitle slow here, still on LX 0.5c using Ele's Speed v4 :o

No reboot problem here. Google Navigation worked fine for me. Led did turned green this morning after fully charged overnight. Did not find battery usage on LX 0.5c any better though. Not using tethering so not tested.

The only funny thing not sure is whether I was using interactiveX, becos using SetCPU, it would revert to interactive instead :(

Flashed latest LX 0.5e, now using the same SetCPU 2.1.0, I am able to set InteractiveX :)
[Hero, G2 Touch Android Development] erasmux:
Try upgrading your SetCPU to the latest version. I had a similar problem and it went away when using SetCPU 2.2.4.
[Hero, G2 Touch Android Development] Pitel:
Reboot

Was using 0.5d whole day for geocaching today. No GPS problem at all. But I tried Google Navigation on the way home (it tends to freeze pretty often, but wanted to try with this kernel) and bam, reboot (but no Hero logo)!

Using Elelinux-7.1.0-RC1-Hero-v3.2 Android 2.3.5.

last_kmsg
[Hero, G2 Touch Android Development] erasmux:
Thanks for the report. I don't see any thing about a crash in that last_kmsg. My guess is that only the ROM rebooted. Was google nav stable for you with the 0.5.0 release (by Riemer)? Let me know if the problem persists.
[Hero, G2 Touch Android Development] rdejager:
BTW it worked but after a while on 100% it was fixed. The chargeled went green after a while 100%
[Hero, G2 Touch Android Development] bamboo2005:
help

Hi Sir,it is good,but I can't download from China site.Could you pls give me another link to download?

Thanks.
[Hero, G2 Touch Android Development] mar9118:
Thanks a lot erasmux! I will check if USB tethering work with 0.5e, if not I will try to learn how to create a logcat and attach them :)
[Hero, G2 Touch Android Development] erasmux:
Let me know what you think of the new governor and if you have any problems with it.

Additionally, I have been looking into the USB tethering problem, and my current guess is that this is not a kernel problem. I currently believe that this commit is the problem: (from the device/htc/hero/BoardConfig.mk file in the CM sources)

+BOARD_USE_HTC_USB_FUNCTION_SWITCH := true

This boolean is good for the .29 kernel but for the .35 kernel this needs to be false!

I can not test this since I do not have a data plan. EDIT: Thanks to perdita for pointing out I can also test it with wifi :)

If anyone who is interested in USB tethering is building his ROM from source, please try to turn off this flag and test if USB tethering will work with the .35 kernel (note that unfortunately, this should break the usb tethering with the .29 kernel).

EDIT: The above was/is the problem, and after fixing the netd, USB tethering works fine with LX 0.5f (at least with wifi) :D I will post fixed netd versions shortly.

If the above is not enough, please try the above + using the following kernel version:

Las_Venturax-0.5f-tether-plz.zip

(there is no point in trying this version without fixing the BOARD_USE_HTC_USB_FUNCTION_SWITCH, that flags must be false also for this version)

If anyone does both of the above, and still it does not work, it would really help if I could get a logcat and dmesg log from two cases: one is the case where it works with FlyKernel and the other is the case where the ROM has been compiled without the BOARD_USE_HTC_USB_FUNCTION_SWITCH and is running the above 0.5f-tether-plz version and still it does not work.
[Hero, G2 Touch Android Development] perdita2000:
Thanks Erasmux for Uour Work, I will have a try of both... You don't need to have data plan because you can share your wireless connection to PC too.... That's what I use sometimes ... This should work too.

Perdita2000
[Hero, G2 Touch Android Development] erasmux:
Hmm, for some reason I was sure that you can only tether data. Thanks for the tip :). Let me know if you have any results using the above fix(es).
[Hero, G2 Touch Android Development] perdita2000:
Hi Erasmux,

Tried both LV kernels and none of them have usb thetering working (attached file). I attached flykernel logcat for a correct tethering usage. One thing I have notice is that when you are "logcating" with adb and you enable usb tethering, usb adb connecting looses using flykernel (as expected..) but it doesn't using LV kernels...

I noticed compiling options not working as I reported to forum, maybe we have kernel source problems on some missing header files?¿?¿?

Perdita2000