yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] Waninkoko:
I have been working lately on the new Las Venturas kernel (now based on buzz-kernel) to make it boot and run properly. I took as base the last source tree pushed by riemervdzee in his git repository and luckily I have been able to "fix" it. It boots and most stuff works (bluetooth is now working for me, it didn't before), but camera is not working at all (i2c stuff problems).

Here's my fork's git repository: https://github.com/waninkoko/hero-kernel-2.6.35

And, just for testing purposes, I uploaded a testing build to receive some feedback: http://ompldr.org/vOW0xdw
[Hero, G2 Touch Android Development] ggrammer:
Always great seeing such talented individuals still hanging around the hero forums, glad to have you here. tried flashing after wiping cache and dalvik with amonra and received this error

e:missing file:

system/lib/modules/ramzswap.ko

e:verification failed

installation aborted
[Hero, G2 Touch Android Development] schlehdorn:
Flased your kernel yesterday through clockwork recovery, wiped dalvik and cache. The overall performance is way better than with the cronos evo3 kernel, but the cam doesnt work as you mentioned. Says cant connect to camera :/

the idle battery drain seems to be more. But its okay.

Thanks for your hard work. I hope to see more ;D
[Hero, G2 Touch Android Development] v0id3r:
some bug in 0.5.0 fork - in phone app speaker is always enabled /= even no checkbox in settings set.

and some lags when click numbers in phone too
[Hero, G2 Touch Android Development] rdejager:
Here is the signed version of the 0.5.0 version made by Waninkoko

Multiupload LV-0.5.0-Alpha-Signed
[Hero, G2 Touch Android Development] Waninkoko:
The install error is because I didn't sign the package.

And yeah, I also noticed the lag while typing a number and the speaker bug.
[Hero, G2 Touch Android Development] schlehdorn:
Dont have lag while typing a number using ray dialer, but can confirm speaker bug :(
[Hero, G2 Touch Android Development] v0id3r:
also Shazam (etc?) says it cannot tag error and even in any music app - sound doesnt work at all /= i'm sad, because other things are much smoother and faster with this kernel
[Hero, G2 Touch Android Development] riemervdzee:
I must say that I am really really (yes really! ;P) happy that waninkoko got it booting.

From this we can get this new rebase up to the quality of 0.4.7 in no problem.

I represent you lads a new flashable:

http://ompldr.org/vOW1pZg

md5: b2857c1e05be50f936f8d10e3952751d

qdsp got fixed, so sound sound-input etc should all work. Even camera works. It might even work better than 0.4.7!

Note that the kernel is a tad limited, headset etc doesn't work while some other things might as well. If you got any problems, please let us know!
[Hero, G2 Touch Android Development] whitealien:
rofl

testing ....
[Hero, G2 Touch Android Development] schlehdorn:
Speaker bug is gone and camera is stable for me on 5mp :)

Will testing performance and battery drain over night...
[Hero, G2 Touch Android Development] RCOO:
Nice to read this kernel is getting even more kinky... xp

I'd like to know though, the biggest differences between FlyKernel and LasVenturas kernel... And which are the advantages/disadvantages of each kernel... And yes, I'm prepared for biased opinions =p
[Hero, G2 Touch Android Development] frige:
Put 0.5 on Elelinux V3.0: camera fine, GPS fine (screen on and screen off), performance fine, phone app (incl speaker setting) fine, headset: not detected

--> so seems headset is only bug hurting me rigth now (but beeing optimistic this can be fixed)

--> battery consumption: will see next days how it compares with flykernel

:-)

frige
[Hero, G2 Touch Android Development] orrebo:
+1

The phone is really fast right now.

Much better then before.
[Hero, G2 Touch Android Development] whitealien:
Except already mentioned bugs SDcard mount to USB port does not work either. Using SalsaSense 2.5.
[Hero, G2 Touch Android Development] riemervdzee:
Thanks all. Please keep us updated on the battery.

Mine is dropping a bit quickly in my opinion, but the ROM might also take the blame on this one (salsaSense rc4).

On my previous ROM (ele speedmachine 6.2) the usb-mounting also didn't worked, while it does on SalsaSense RC4. Anyone else got this problem with other ROMs than these?
[Hero, G2 Touch Android Development] frige:
Interesting. USB mount really does not work (do only use it very rarely..).

After first connection an new USB driver was installed on PC (Windows 7) - installation

was ok. on Hero an littel android with de_de was popping up + "please select input type".

On PC i see a not mounted device.

So seems it is only mounted for debugging...

frige

(Elelinux 3.0, 0.5 kernel, smartass 176-576)
[Hero, G2 Touch Android Development] meisze:
The usb-mounting also didn't worked on Elelinux 7.1.0 RC1
[Hero, G2 Touch Android Development] JieeHD:
USB mounting is working fine for me, I'm not sure if it's down to luck or due to the ROM we're using. But SalsaSense has always worked very well with the .35 kernel.
[Hero, G2 Touch Android Development] f_padia:
latest kernel (0.5?) is running good with salsasense 3 for me. Felt like it booted up a bit quicker and runs a bit smoother. USB mount indeed doesnt work, but battery seems quite good. Having said that I have removed quite a lot of things which tend to run in the background so im sure that will have helped improve battery life somewhat.

Is there any chance you could add this patch to your source tree:

http://lkml.org/lkml/2009/1/29/220

it basically allows the user to make certain processes immune from the oom-killer which I think is quite useful in the RAM heavy sense 2.1 ROM. I applied it to 0.4.7 and it seemed to work ok but it would be much easier if it was applied to your source tree so I dont have to keep modding every new version :D Thanks
[Hero, G2 Touch Android Development] schlehdorn:
- Usb-mount didn't work on Cronos Ginger 2.2.4

- Performance is amazing!

Its too early to say something about battery drain. Used it the hole night to surf and read some pdfs, so battery drops in 5 hours from 100% to 61% :)
[Hero, G2 Touch Android Development] bharat_goku:
i found 1 problem using the elelinux 7.1 RC 3.0,i'm unable to recieve calls,apparently the call gets cut afta d 1st ring :(
[Hero, G2 Touch Android Development] riemervdzee:
@f_padia, Is there anything else required to get this working? or is oom values set already by android?

@bharat_goku, can't recreate it. Which kernel you got problems with? Does 0.4.7 work while the newer 0.5 for example doesn't?
[Hero, G2 Touch Android Development] f_padia:
no nothing else is needed. You can see in that link that there are a couple of new files to create and a couple to change. But as far as I know thats it.

The patch introduces a new control group whose properties can be adjusted to change the order in which the oom-killer will consider the processes to be killed.

to use the cgroup we first need to mount it somewhere (e.g. /oom-killer). within the cgroup there is a file called 'tasks' which has all the pid's of the running processes listed in it. There is another file called oom.priority and the value within this file is 1. this means that all the processes in the tasks file will be treated as equal when the oom-killer is called and the normal killing procedure will occur.

if we then make a new folder called invincible (or anything for that matter) we can then list the pids of processes we want to protect from the oom-killer in the new tasks file. Then we set the oom.priority value of /oom-killer/invincibles/oom.priority to 0. This then means any processes listed in /oom-killer/invincibles/tasks will be ignored by the oom-killer.

I have created an init.d script to do all this so all that needs to be done is the patch applied to your kernel and we should be good to go :D
[Hero, G2 Touch Android Development] JieeHD:
Do you mind sending me that script so I can have a look?
[Hero, G2 Touch Android Development] RCOO:
Ok. I understood nothing of what you said f_padia. Well, I understood part of it. Looks like a good solution to the killing of key processes on the Hero.

Thanks =P
[Hero, G2 Touch Android Development] f_padia:
sure. its terribly written since I dont know how to code, but it works!
[Hero, G2 Touch Android Development] f_padia:
hehe yeah. Im not so good at explaining things, but it makes complete sense to me. Basically when you mount the control group (cgroup) a load of files are created. One of the files is called tasks and controls which processes belong to this cgroup. The other files define the properties of these tasks with regards to the their treatment by the oom-killer. By increasing the value in the oom.priority file (also created when you mount the cgroup) you can set the order in which that particular cgroup is attacked by the oom-killer. Thus you can potentially have up to 257 different cgroups. The higher the value you put in oom.priority the earlier that group will be attacked by the oom-killer. If there are multiple processes in the group the normal heuristic based calculation will be made to decide which process to kill first.

Realistically we only need 2 groups. The first is automatically created when we first mount the cgroup this group contains all the processes except for the one(s) we want to protect. The 2nd group contains the processes we want to protect and is created when we create the invincibles folder. We place the mms process pid in the tasks file in the invincibles folder and then set oom.priority value to 0. 0 is a special value in that it means the group is completely bypassed by the oom-killer (as oppsed to values > 0 which simply determine the order in which the group is attacked).

This probably doesnt make it any more clear but its actually quite a simple thing if you could see how it works.
[Hero, G2 Touch Android Development] JieeHD:
Yeah like f_padia says it is a complex explanation but when you see the script in action its quite simple. I had wrote a script today that should do what yours does, although yours is probably better :p I didn't spend much time on it.
[Hero, G2 Touch Android Development] bharat_goku:
0.4.7 works fine,it was with 25th july kernel u made which gave me this problem.......should hav made a logcat my apoloogies......shifted to salsasense RC4 now :( apologies :(
[Hero, G2 Touch Android Development] frige:
After 1.5 days now with v0.5: battery for me is very similar to flykernel (+-5%). Very stable for me - near to be best all day kernel :-)

frige
[Hero, G2 Touch Android Development] riemervdzee:
@f_padia:

https://github.com/riemervdzee/hero-kernel-2.6.35/commit/17d06242dda2831f1c09b85e19e107d46c0490b1

Could you check if I applied the patch correctly? had some bumps getting mm/oom_kill.c to work, seems ok to me though.
[Hero, G2 Touch Android Development] f_padia:
Thanks for that. with regards to checking it i'd say you're the expert mate so I trust you! in my novice opinion, however, it all looks good.

I also had troubles with oom_kill.c. Was it to do with the missing *g pointer? If it was I dealt with it slightly differently to you. But im sure your method will be better. Did you get chance to go through it and see what its all about because I/we are having a little trouble with it at the moment?
[Hero, G2 Touch Android Development] orrebo:
Is there any update coming soon?

So headset and mounting will work.

Other than that so is this kernel the best I have tried :)
[Hero, G2 Touch Android Development] riemervdzee:
Quite soon yes. Currently trying out some usb-code, if that works/fails I'll probably release a new version.

Headset is working though. But sometimes the buttons won't (same behaviour to be found at 0.4.7).

edit: got usb partially working. Takes quite some time to get mounted tho
[Hero, G2 Touch Android Development] riemervdzee:
A new version is available for you to download!

Check out the opening post for the download links.

Changes of last Version 0.5.0:

Switched to a new base maintained by Arco for the HTC Buzz/Wildfire-S. Thanks to Waninkoko to get it booted! New base is working quite nice as everybody can see. Camera is rock-solid thanks to this! :)

Headset is back to working-state. Buttons might fail once in a while

USB might not be as stable as we want. Atm it is experimental. But it mounts now though :) (edit: require testers on this one btw)

As this is a whole new repository, I need quite some test reports on this. Please post any findings! I'm especially interested whether usb mounting works, same counts for usb-tethering. Please include which ROM you are using when posting any information.

Many thanks in advance!
[Hero, G2 Touch Android Development] Habarug:
You just had to update it strait after I had flashed 0.4.7, right !?!?! :P
[Hero, G2 Touch Android Development] riemervdzee:
Hehe sorry man. 0.5.0 is really better tho :) You should really test this one out.
[Hero, G2 Touch Android Development] Habarug:
Of course :-) I will post some feedback from how it works with Speedmachine in a while :-)
[Hero, G2 Touch Android Development] whitealien:
Many thanks m8. Going to test it right away. Wondering how this kernel reacts with older builds, like Froyo or stock Sense.
[Hero, G2 Touch Android Development] frige:
Flashed 0,5 on Elelinux3.5 (light) - seems working fine

USB mount working fine (Windows 7 PC) - did install a new driver. But working fine and mounting same as with flykernel (few seconds - think this is PC time...)

Headset detection working fine

Wifi working fine (do not use tethereing, just direct access point connection)

acclerators (abduction) working fine

GPS: test tomorrow (no reception indoor)

Will observe battery consumption next days

:-)

frige
[Hero, G2 Touch Android Development] Matri}{:
What governor is better to use in this kernel - smartass or ondemand?
[Hero, G2 Touch Android Development] orrebo:
Thanks m8.

Will flash it right now :)
[Hero, G2 Touch Android Development] RCOO:
Working perfectly here... Haven't tried USB mounting, but that is the least. Leave love the speed.

Battery usage is still under test...
[Hero, G2 Touch Android Development] orrebo:
Tried mounting on the computer with linux mint debian edition and it works well.

Even headset/headphones work :)
[Hero, G2 Touch Android Development] perdita2000:
USB mount works for me too. And 5mp camera is working fine..... and pptp VPN...tested on TESLA RC6.03.

USB tethering doesn't work....

Many Thanks to everyone involved in this project and Good Work!!!

Perdita2000
[Hero, G2 Touch Android Development] davrave:
This works perfectly for me on Elelelinux 7.1 - 2.3.5 Rom. Wiped cache and Dalvik cache and restored system Rom. Can someone tell me what differences there are with this kernel and the default kernel on the rom?
[Hero, G2 Touch Android Development] Habarug:
Everything works with Elelinux Speddmachine :) USB seem to mount faster than Flykernel. At least wired headset work, haven't tried bluetooth. Probably a tad faster than Flykernel and I haven't experienced any instability ;) thanks for awesme work :D
[Hero, G2 Touch Android Development] whitealien:
Version 0.5 is amazing!!! Benchmarks shows overall performance increase by 10-15% either 2D, 3D, RAM or IO tests. I used Antutu benchmark app from market.

The only thing I noticed is that battery charge time is a lot longer, but I can't be 100% sure after only 1 day of testing.

Great work, thanks Riemer
[Hero, G2 Touch Android Development] f_padia:
0.5 is very good indeed. Only thing I noticed is that the phone gets pretty hot when in a call. Dont remember it getting hot in the past. Dont know if this has anything to do with the kernel but thought its worth mentioning.
[Hero, G2 Touch Android Development] schlehdorn:
Usb mount works on cronos ginger 2.2.4 but after unmounting my hero freezed.

And i noticed few more fc's and have to click wait. Lil' bit annoying.

The performance is amazing and i love that there is no input lag on keyboard :)
[Hero, G2 Touch Android Development] troublecro:
Uhm,can i flash it on existing ROM or I have to reflash it both with full wipe?

Regards
[Hero, G2 Touch Android Development] JieeHD:
You can flash it over your existing without any wipes at all (:
[Hero, G2 Touch Android Development] nscxp2005:
riemervdzee,

Does this kernel have the old style app2sd support?

All the best,

NSCXP2005
[Hero, G2 Touch Android Development] riemervdzee:
The current smartass implementation differs than the one found in 0.4.7/flykernel. It varies depending on your own demands?

Haven't looked much at the battery-driver yet. Seems to be quite similar to 0.4.7's though. Should give the same results. Will check it out, thanks.

Hmm, will check it out. I sometimes noticed mobile-internet got dropped in a call. Maybe related. Will check it out.

Hows the patch coming along btw?

Try wiping dalvik-cache and reboot. Could you check if this removes the problems you have?

I prefer dalvik-cache wipes when coming from a 2.6.29 kernel installation to be very honest.

This is ROM dependant. The kernel hardly has any influence at this, I'm sorry. Ext2/3/4 should be supported though.
[Hero, G2 Touch Android Development] schlehdorn:
Okay dalvik-cache wipe solved usb-mount freeze. Curious, cause i wiped dalvik-cache before flashing the new kernel. I blame clockworkmod-recovery for it :D
[Hero, G2 Touch Android Development] Brakelseboer:
Does this kernel supports a higher frequency than 528MHz?
[Hero, G2 Touch Android Development] Habarug:
Of course. I'm running 710 MHz :)
[Hero, G2 Touch Android Development] Brakelseboer:
Flashed 0.5.0. When I open SetCPU the max. frequency I can select is 528...
[Hero, G2 Touch Android Development] schlehdorn:
press menu in setcpu -> device selection and then autodetect
[Hero, G2 Touch Android Development] Brakelseboer:
How stupid of me. That did the trick. Thanks!
[Hero, G2 Touch Android Development] f_padia:
the heating issue I mentioned may actually be due to charging not calling. My phone has been on charge for a couple of hours but its still only @ 70% and the temp has gone up to 40oC. Is this normal? My phone was on charge when I noticed it last but because I was also in a call I assumed it was due to the phone call.

Anyway it feels warmer than normal for charging. Maybe the charge voltage is set too high? is there a way to change this in the kernel?
[Hero, G2 Touch Android Development] orrebo:
It use to get hot for me during phone calls.
[Hero, G2 Touch Android Development] bluepinkpanther:
Great kernel. Works well with leatest elelinux gingerbread. It will work with rcmix 2.2b? It's Android 2.1 with sense.
[Hero, G2 Touch Android Development] CSL00:
Should work, but in my experience (villainrom 12 and 13, elelinux's 2.1 sense rom and tegro) some apps and bluetooth won't work. Other than that performance is unmatched with this kernel (ui, browsing, camera, whatever app/feature works)
[Hero, G2 Touch Android Development] troublecro:
In elelinux 2.3.5 you can choose all values....
[Hero, G2 Touch Android Development] Cortiis:
Using Cronos Gingers X 2.3.3, everything seem to be working.

1) Camera, no blinks :-)

2) USB mount, flawless

3) WiFi tethering, works for me, using Wireless Tether for Root users.

4) Everything WiFi, GPS, Mobile data, Bluetooth, etc seem to work fine.

The only thing I noted are that the notifications are a bit laggy, like I get the bubble flash for an incoming BT transfer but it takes around a second to come in the pull down menu. I will test the behavior more and report back.
[Hero, G2 Touch Android Development] dkelley:
running 0.5.0 with ele's Special Edition froyo (NOT gb...) and it's working wonderfully.

it feels a lot like my other favorite kernel, fly 11c. fly 12 has issues for me when playing games and using touchscreen in some other apps. fly 11c doesn't, so I always flash that on roms that are performing badly.

however this kernel has at least as good responsiveness as 11c, possibly better. it FEELS better to me, although this is entirely subjective and might be wishful thinking.

I honestly think it's at least as fast as 11c though which IS an improvement over 0.4.7.

camera seems solid. haven't tried bluetooth or wifi tethering yet (which I know worked with 11c in this rom).
[Hero, G2 Touch Android Development] riemervdzee:
You should know USB has standarized the voltage usages. I do believe the wall-connector uses a higher ampere value though. It also charges faster due to this.

Maybe the phone was bussy with something else as well, just things stacking up etc...

Will check the phone warming up when calling tho.

It should work normally aye. Make sure to wipe dalvik-cache though. So hopefully you don't have the issues mentioned above.

Good to see the cam is working aye :)

Could be that bluetooth is a bit slower with this kernel? Haven't checked it much as I don't have any BT devices myself.

Good good, basically I hope this will replace flykernel in the end. As the .29 usb-stack is a bit hellish to work with.

Don't know much about the speed. Some say it is quite quicker, but tbh I haven't touched .29 for ages :P Only know that -due the newer mdp code/overlay/graphics-stuff- that some apps work a lot quicker as .29 supported it very poorly.

Any chance you can check BT tho? WiFi tether via a market-app should work. Not sure about the standard app.
[Hero, G2 Touch Android Development] ggrammer:
I use bluetooth in my mazda3 and it works great for music and calls with this kernel, the only trouble I have and I think it is more the car then the phone but if the car is started and then I enable BT on my phone the controls don't work but the music and calls still do, if I have BT enabled on my phone then start the car everything works fine. I would try my BT headset and report back but am gone to europe on vacation tomorrow.
[Hero, G2 Touch Android Development] f_padia:
well... not great. Im pretty sure its implemented correctly, and everything is set up right but it doesnt seem to work. This is probably because Androids task management is a bit different to standard Linux as people who know much more about Android had indicated (namely Ninpo and Erasmux). In the end I resorted to hacking activity manager in service.jar just as CM did. I think this method is working correctly now, but only proper testing will tell.
[Hero, G2 Touch Android Development] perdita2000:
This kernel is best tried since flykernel 11c (almost 12) but I need usb tethering, have tried to complie myself but there are many difference from flykernel source on USB tree, many changes from .29 to .35. Good work.

Many Thanks for your work riemervdzee and everyone playing around ;))

Perdita2000
[Hero, G2 Touch Android Development] Dark Emotion:
Can you explain why is the flykernel better?
[Hero, G2 Touch Android Development] perdita2000:
ummmh... haven't say that... but USB tether works... But In fact I haven't say flykernel is better?¿?¿...

Perdita2000
[Hero, G2 Touch Android Development] Dark Emotion:
You are right, I have read it wrong...sry
[Hero, G2 Touch Android Development] perdita2000:
;)

Perdita2000
[Hero, G2 Touch Android Development] riemervdzee:
Yep, usb-tethering is kinda high on my todo list now. Currently tracked it down to the following error from Android (logcat):

D/NetSharing_USB( 228): Can't open "/sys/devices/platform/msm_hsusb/usb_function_switch", would open by Daemon.

I/NetSharing_USB( 228): enableEthernetSharing@186=0

D/NetSharing_USB( 228): open /sys/devices/platform/msm_hsusb/usb_function_switch fail.

"usb_function_switch" in the named folder doesn't exist :-/
[Hero, G2 Touch Android Development] perdita2000:
Msm_hsusb is not defined on config file. I enable it with make config, but can't compile now because missing functions and definitions on USB tree libraries.....

Perdita2000
[Hero, G2 Touch Android Development] riemervdzee:
I don't see this definition tbh?
[Hero, G2 Touch Android Development] whitealien:
ro.ril.enable.dtm (Dual Transfer Mode) Only set this to 1 if your network allows simultaneous transfer of Circuit switched (CS) voice and Packet switched (PS) data over the same radio channel (ARFCN)
[Hero, G2 Touch Android Development] perdita2000:
Use menu config and enable USB modem..This will enable it on config, and then try to compile ....

Perdita2000