yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] J.K Nilsson:
The files on Megaupload and Rapidshere was bad when I tried to install them. The file from zSHARE did install.

J.K Nilsson
[Hero, G2 Touch Android Development] HannoSLM:
dear riemervdzee,

i am pleased to inform you that the speed is improved dramaticaly with this kernel date 17.05.11. I have almost no lags, performance is smooth and responsive. The only problem is that the camera still does not work. It opens, but when i click to take the photo it freezes with wildhero 1.0

thanks again
[Hero, G2 Touch Android Development] Thomasssss:
yep same here but thx for your work
[Hero, G2 Touch Android Development] erasmux:
The camera problem is no specific to this ROM but a general problem with the new kernel. If I am not mistaken it is the only thing that stands before retiring the good old fly-kernel. I am actually trying to look into this problem right now, maybe I can find something Riemer missed, but this is a tough one :(.

It is known that it works or doesn't work depending the frequency. To work on this problem I lock the CPU at 518Mhz (i.e performance 518) and to date I have yet to get it to take a picture at this frequency :D. From this I assume that using higher frequencies should work. I know its a very lame workaround, but I assume something like performance 614 should take pictures reliably (which you need to change back right after finishing with the camera or your battery will be eaten alive). I really don't want to spend time on finding a workaround, I want a real solution....
[Hero, G2 Touch Android Development] riemervdzee:
The camera is the only problem which keeps this kernel from going 1.x, instead I still name it 0.x and call it "beta" (although I've been running it for months).

I think I've spend more than 50% of the time I put into this kernel to get the camera working, but it is really a frustrating piece of shi.. eh code ;)

If you got any clues: please shoot, Eran ;) Any other general tweaks are always welcome ofc. But atm the kernel is quite potential
[Hero, G2 Touch Android Development] dkelley:
hahahahha :-D
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, you should interpret it like: please shoot, Eran. Not as in kill him... :P (will correct, haha)

edit: If you want to shoot someone in the more physical way of the word, I'd suggest some random HTC Dev ;)
[Hero, G2 Touch Android Development] riemervdzee:
Latest build still has a sleeping problem in the headset code :(

For now the fix: if the battery is draining a bit too fast, reboot again. Or flash flykernel if you really need the battery to be holding out.
[Hero, G2 Touch Android Development] Wupper:
Isn't it possible to make a built without the headset being enabled?

Or doesn't it bring any improvements?
[Hero, G2 Touch Android Development] riemervdzee:
Unfortunately I use it every day :) I like to have my builds in sync with the ones I give you lads, for debugging etc.

Anyhowz, a new day a new build:

http://www.multiupload.com/L9FMQI1DVR

http://www.riemervanderzee.com/download/kernel_19-05-2011.zip (as last resort, don't stress my server too much :P)

md5: b47f80131916d8313c85d2effce36871

Might have fixed the headset irq wakeup problem, it now disables it when it has received it until it is handled instead of just looping it. Not sure whether this is a 100% fix, will have to watch the results a bit longer for that.
[Hero, G2 Touch Android Development] keyra74:
flashing right now, anything to do to give you results ?
[Hero, G2 Touch Android Development] riemervdzee:
Yup, just use it. Post me results of how long you can do with the battery etc. and stuff like that :)

Also I need people to test the bluetooth functionality, to see whether I screwed it up or not :P
[Hero, G2 Touch Android Development] J.K Nilsson:
How come that the CVM recovery so often says that the ZIP is bad? I need to try download it from different sites before it is OK.

I get E:Can't open /sdcard/Kernels/kernel_19-05-2011.zip

(bad)

J.K Nilsson
[Hero, G2 Touch Android Development] J.K Nilsson:
Now I tried al five different download sites and CVM recovery says all are bad. What do I do now?

J.K Nilsson
[Hero, G2 Touch Android Development] riemervdzee:
Could you try this one instead?

http://www.riemervanderzee.com/download/kernel_19-05-2011.zip
[Hero, G2 Touch Android Development] J.K Nilsson:
Yes, that one worked. Starting up now, keep fingers crossed. :)

J.K Nilsson
[Hero, G2 Touch Android Development] shantur:
Working fine....

I think it works faster when the phone is not connected to ADB via USB.

If this is an issue, it would be related to Rom or Kernel?

Is there any way by which we can test the sleeping of phone?

-Rathore
[Hero, G2 Touch Android Development] Wupper:
Try stressing mine :p.

stress here
[Hero, G2 Touch Android Development] ChosSimbaOne:
Will do :) nice kernel, but i am experience that egen i reboot My phone All my widgets on widgetlocker is deleted? This does not happend with herokernel
[Hero, G2 Touch Android Development] riemervdzee:
I noticed aye, the usb-driver is a bit unstable. sometimes it reconnects as well, will have a look later on. To test the sleeping: see whether the battery drains a lot or not (easy, but long way :P) Another way is taking a look at the dmesg, to see whether there a lot of events with WAKELOCK bla bla keeping the device from suspending or even waking it up. But that's a bit more advanced :)

Could you get me a logcat when booting? There is somekind of problem which lets all apps crash when booting, thats why the kernel requires a bit more time to get settled down. This one is quite high in my todo list aye.
[Hero, G2 Touch Android Development] f_padia:
In setCPU there is an option to set the sampling rate and frequency jump threshold when using certain governors. Is there anyway to have different settings for screen off and screen on? I would like to reduce the sampling rate and increase threshold when screen is off to see if it has any positive effect on battery life/ negative effect on performance.

Anybody have any idea about how to do this?
[Hero, G2 Touch Android Development] erasmux:
As far as I know, except smartass and HTC's original perflock (which isn't really a governor), governors are not aware of the screen state so its not possible.

In smartass, I use similar code to that of HTC's perflock so that it does track the screen on/off state. Although the only thing that is changes between the on/off states is the min/max speeds. By default smartass will not go below 518Mhz when awake (awake_min_freq parameter) to ensure responsiveness because from my testing the power gained by lowering the frequency below 518Mhz is negligible to the power drained by the screen being on. On the other hand, when screen is off, the power taken by the CPU is a major player in the standby battery life, so the screen off max frequency is limited by default to 352Mhz (sleep_max_freq). All the smartass parameters are of course under:

/sys/devices/system/cpu/cpu0/cpufreq/smartass

I am afraid I never got around to properly document them, but you can try to understand what they do from the code. Note that their initial values are not arbitrary and that I spent days using different usage scenarios and benchmarks in order to reach values which I believe are optimal for the Hero. If you make a drastic change to any of them I probably have a scenario in which you degrade performance (speed or battery) considerably.

Now if only I could get the camera to work on LV....
[Hero, G2 Touch Android Development] f_padia:
Thanks for the info. I understand mostly what you are saying unfortunately I dont know C so I cant follow your code easily but I think I get the gist of it... but I think you misunderstood me.

SetCPU can set the threshold and sampling rates somehow. Therefore, the governor itself doesnt need any knowledge of the screen state, only the app/kernel needs to set the appropriate parameters according to the screen state. If we know how setcpu sets the parameters then I presume it'd just need some code in the kernel to set the appropriate parameters when the screen is turned on/off. Not sure it'd make much difference but its just a thought.

Also with regards to smartass governor I have noticed that even when the phone is idle the counters for max freq. and 518 (min when screen is on) go up at almost equal rates. which makes me think that the phone is making many unnecessary frequency jumps. I guess the number of jumps depends on the threshold you have set in the governor (50% cpu load?) and how the phone calculates cpu load. As a test I set the ramp threshold to 100% on the ondemand governor and saw that only the min freq. counter went up when the phone was idle (with screen on of course) if i touch the screen then the max counter also goes up. This makes more sense to me that fewer jumps are made and as I have not noticed any drop in performance as a result of setting this value I personally think its a sensible thing to change.

Having said all of that as you say the power used by the screen swamps the small change in power draw due to cpu jumps and stuff but its just some observations i've made... food for thought perhaps :D
[Hero, G2 Touch Android Development] erasmux:
First obviously all I said was regarding the current code in the kernel. If you rewrite the code you can do anything. Furthermore, at least in theory, since SetCPU has profiles, it can change these thresholds every time the screen on/off changes. I do not know if the current SetCPU implementation supports this but obviously you can also do this at the application level (if the proper code is written by someone).

Regarding the smartass SetCPU counters, if your CPU is really idle it will spend all the time only at the min frequency (i.e. 518Mhz with screen on). Your testing is biased because:

a) Smartass (and interactive which to some extent smartass uses the same ideas brought by interactive) are very very sensitive to any load increase and will jump very fast to a higher frequency. This is why they are much more responsive than ondemand. So comparing to ondemand is not a fair comparison, as for small loads (meaning short, there are no "small" loads just short ones) ondemand will not react.

b) From the above explanation you can understand that you need a very light ROM. Just for example, if you have the SetCPU counters screen open, no matter how light your ROM is , just the action of updating these counters alone, will cause the frequency to jump. Another similar example is using adb to check the current frequency - you will always see it at the max frequency because just the request made by adb is enough to cause it to jump to the max frequency.

The correct way to test this, is to use a ROM as light as possible and with as little background apps as possible. Change screen timeout to a high value, note the current SetCPU counter values, leave it at the home screen (or some static non-changing screen) for some time (say 10 minutes) and then check the change in the SetCPU counters. Assuming your ROM is light enough the majority of the time will be spent at the min frequency (518Mhz).
[Hero, G2 Touch Android Development] f_padia:
which brings me back to my original question! does anybody know how to achieve this?!

I dont know how you quantify 'much more responsive' but I personally cant feel much difference in response with either smartass or ondemand. Perhaps my eye isnt as well trained as yours! or maybe im just used to a rather sluggish Hero. I'm sure you're right but I just cant feel much difference.

What kind of processes are considered short loads?

This was my second point. From a users point of view does the phone really need to jump up to a higher frequency just to count and display a value? wouldnt it better if it just stayed at the lower frequency and did the calculation a fraction of a second slower?

Again dont take any of this as criticism or anything I appreciate the hard work you put in to developing smartass but im just thinking if its as good as it could be ;)
[Hero, G2 Touch Android Development] genocida:
adb dont work for me too
[Hero, G2 Touch Android Development] erasmux:
Can you test usb with this boot img:

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

(it has no PS3 jail thingy, just clean elemag github build)
[Hero, G2 Touch Android Development] genocida:
with you boot.img the adb work
[Hero, G2 Touch Android Development] genocida:
But with you boot.img

# insmod psfreedom.ko

insmod psfreedom.ko

insmod: init_module 'psfreedom.ko' failed (Exec format error)
[Hero, G2 Touch Android Development] erasmux:
like I said its "my" build is a clean build of elemag's github it does not have the psfreedom module!

But this proves that the usb not working is a problem with MrNameless's build.

MrNameless: Did you use the hero_defconfig from the current github sources as the base for your kernel? Using it should solve the usb problem.
[Hero, G2 Touch Android Development] genocida:
It's a Froyo Cronos 1.1 issue

With a 2.1 Rom, the adb dont work but the screen YES!

Ps3freedom done!
[Hero, G2 Touch Android Development] mr.bang:
now i have my own .34 running on hero with touchscreen sound and adb enabled

i'm am on my own 2.1 custom rom

but in the settings-info-software-kernel i have a bad name maybe caused by flykernel's ramdisk
[Hero, G2 Touch Android Development] erasmux:
how did you enable the touchscreen?

can you please share you changes?

BTW flykernel, does not have a ramdisk, the flykernel updates keep the ramdisk from that was previously installed....
[Hero, G2 Touch Android Development] mr.bang:
why under settings-info-software-kernel still reamains "2.6.29flykernel 10a BFS" ?? wtf? lol
[Hero, G2 Touch Android Development] erasmux:
that means you are using the flykernel and not the 2.6.34 kernel, thats why the touchscreen works....
[Hero, G2 Touch Android Development] mr.bang:
lol here is 4:20 and maybe i'm cunfused.. but just few mins ago i type:

cm-kernel# make clean && make -j4

so i build boot.img with ramdisk from my own rom.

fastboot boot ./boot.img

end.
[Hero, G2 Touch Android Development] ratul_jain1991:
sending zimage <2031kb>... FAILED <remote: not allow>

showing this error when phone is in bootloader mode and in cmd i typed

'fastboot flash zimage zImage'

help

pls some explain how to fastboot zimage in a noob friendly way :p
[Hero, G2 Touch Android Development] witysimon:
zImage is only the kernel, you still need ramdisk to make ramdisk image.
[Hero, G2 Touch Android Development] genocida:
You need unlock the spl with modaco solution
[Hero, G2 Touch Android Development] ratul_jain1991:
thanks

but i used recovery mode meathod n it installed successfully

will try it on ps3 tonight and will post results

thx for this awesomesause developement :)
[Hero, G2 Touch Android Development] OttarA:
Please don't post the results in this thread, as it has nothing to do with PS3 hacking at all.

This is a [DEV] thread for Developers making a .34 kernel for our hero, not a OMG i can hack my PS3 now thread :rolleyes:
[Hero, G2 Touch Android Development] erasmux:
Not that I like it, but this thread has long lost its way from it's original ".34 kernel development" subject. I have given up on even wanting the forums and threads in XDA to have any logic to them, I just go with whatever random way it flows....
[Hero, G2 Touch Android Development] riemervdzee:
What is the current status of the microp driver? Thinking of kicking in and get some work done (and hopefully contribute/do something right hehe)
[Hero, G2 Touch Android Development] erasmux:
touchscreen not working, that should bring you up to speed :)

updated source on elemag's github (see first post).
[Hero, G2 Touch Android Development] pinn___________:
Sorry, I know it's not quite the right place to discuss this, but it seems the only place anyone is.

I'm in the same boat as you anyway. I have flashed the custome recovery and am now trying to send the zImage in bootloader.

Can I not flash this via recovery as per usual?

Thanks

By the way touch screen etc all working fine on latest Froyd Villain and latest recovery.
[Hero, G2 Touch Android Development] f_padia:
Perhaps you could put some counter into the governor and only ramp up if the load stays high for more than 2 counts (or more depending on the length of 1 count). this way short loads will be done at lower freqs but long loads will get the higher freq. How long is a single count? if its of the order of ms then 1 or 2 extra probably wont be noticeable in responsiveness?

To be honest my day-to-day usage of the phone varies too much to make any meaning conclusions on whether the battery life is improved. i THINK it is but then that may be psychological. Logically though I wouldve thought making fewer jumps and spending longer time at lower freq should improve battery life.

Also another thought I had was that if the phone behaves the same when screen if off (i.e. jumping up to higher freq for short loads) then it will spend a lot of time at 352 even if you set the min freq to 176. In this case you could set the min counter required for freq jump to be higher so it is less sensitive to short loads. When the screen is turned on the governor is set to jump to max freq so it shouuldnt affect the response of turning on the screen?
[Hero, G2 Touch Android Development] erasmux:
I generally remember this is in the order of tens of ms (say around 50ms), I was also quite amazed that one can notice this difference. But I guess if the delay by ondemand is a couple of such cycles than you reach about 1/4th or maybe more of a second and the end result is that people definitely do notice this. Again, use ondemand if you find it better. It definitively is an excellent governor.

Like I said I played with this quite a lot with many scenarios and settings. I don't have the numbers right now, because been using the phone for development in the last couple of hours, but generally I think it spends most of the time at the 176Mhz for me, but it definitively spends some time also at 352Mhz also when supposedly idle (the numbers don't lie, if it was totally idle it would ramp up the frequency). Notice another scenario to test is to play music when screen off. I don't remember how ondemand 176Mhz behaves, but I am certain at least for conservative 176Mhz it would skip once in a while in this scenario. When I lowered the parameters of smartass to spend more time at the lower frequencies music would skip for me when screen is off.

All in all, I think the standby life of FlyKernel-12a is amazing. With Floyo 1.2.0 I would get more than 7 days out of it without recharging if I barely used the phone, under my normal relatively low usage I would get around 5-6 days. If you find any settings which improve the screen on battery usage I would be happy to hear about it.
[Hero, G2 Touch Android Development] riemervdzee:
A new experimental build for you lads:

http://94.23.152.245/xda/rmr/kernel_21-05-2011.zip (thanks to wupper!)

http://www.multiupload.com/PC3Z6Z0FK0

- Bluetooth fix is still included, working nice :) still requires some testers with actual bluetooth stuff.

- Headset battery problem is gone, but there might be problems with the buttons of headsets (as in, they don't respond).

- Fixes restart-of-apps problem when entering the pin-code. However battery-sucking might be active again after special things like calling, sending an sms, or other radio related stuff (currently testing).

Please post your findings, tests for battery-live is also welcome! Testers for headsets + with button-presses are welcome, as well as some testers for bluetooth devices (I don't have any). Thanks in advance!

If things go well, this probably will be called 0.4.6 soon :)
[Hero, G2 Touch Android Development] Wupper:
mirrored here.

And i'm going to grab my parrot bluetooth headset :).
[Hero, G2 Touch Android Development] Wupper:
Bluetooth hands free tested with:

-Latest LV

-Elelinux 7.1.0 V2.4

-Parrot Minikit

I was able to:

-Sent contacts

-Add voice recognition to the contacts

-Start a call from the minikit

-Start a call from the Hero and redirect it to the minikit

-Change the volume during a call on the Hero

-Change the volume during a call with the scroll wheel so android would lower the volume.

Not working:

-*emptyness*
[Hero, G2 Touch Android Development] riemervdzee:
Excellent, great :) thanks a bunch for testing
[Hero, G2 Touch Android Development] ChosSimbaOne:
sure, but how is this done the in a an easy way? Never needed a logcat before? Will just check with the new build if this problem has disappeared :-)
[Hero, G2 Touch Android Development] riemervdzee:
Unfortunately I've thrown away the commit for the following bug:

- Fixes restart-of-apps problem when entering the pin-code. However battery-sucking might be active again after special things like calling, sending an sms, or other radio related stuff (currently testing).

As it destroyed the cam-functionality utterly for me? Pushed a inbetween version though, where the cam seems a bit more like average again.
[Hero, G2 Touch Android Development] keyra74:
looks like yeah, camera worked for first pic but nothing more, had to reboot
[Hero, G2 Touch Android Development] ChosSimbaOne:
How do i do a logcat? The problem still presist in the newest build :/
[Hero, G2 Touch Android Development] f_padia:
Does anyone know if 'tickless idle' has been implemented in the android kernel? Sounds like it could be useful to improve the phones idle battery life.
[Hero, G2 Touch Android Development] ChosSimbaOne:
yes i do :-)
[Hero, G2 Touch Android Development] JieeHD:
Well just open the folder containing the sdk, there should be a folder called tools, open that. Then double click a file named ddms.

Or alternatively open a cmd prompt and navigate to your sdk folder, and then to folder called platform-tools, and then type adb, you'll get a whole a bunch of commands but that one your after is adb debug. Type that and hit return and it'll start a log for you.

That's all using windows, if you're using a different OS I can't help.
[Hero, G2 Touch Android Development] ChosSimbaOne:
Thanks, i am using windows. THe dms command does it provide the log in text file or something?

When should make the log? straigh after boot or?
[Hero, G2 Touch Android Development] JieeHD:
Once you open ddms, It will bring up a new window with the logcat, plug your device in and when it appears in adb, click on it and it will start logcat. At this point it will not save a log, to save a log you must click device at the top and click run logcat this will output a log which you can save. All you have to ddo is click save when you have recorded what you want to logcat.
[Hero, G2 Touch Android Development] riemervdzee:
Version 0.4.6 is out!

Grab it from the first post, let me know what you think about it :)

Changes of last Version 0.4.6:

Fixes bluetooth and h2w interrupts who woke up the whole system before. better battery live.

Some fixes to SMD again. Things are a bit more stable when unlocking with the pincode, but not perfect yet.

The Wildfire S .35 kernel sources are out, which I'm currently checking out whether something useful can be found. Hopefully the USB code can be fixed by taking their version of it. Maybe other fixes as well like yaffs, or sd-card mounting. Camera unfortunately not yet :( already have taken a look at it, but it the problem is really hard to fix.
[Hero, G2 Touch Android Development] f_padia:
Hi Riemer, do you think the tickless idle i mentioned a couple of posts up could be implemented in the kernel? see http://www.lesswatts.org/projects/tickless/
[Hero, G2 Touch Android Development] riemervdzee:
Must have missed the post, sorry. But I'll take a closer look at it, thanks :)
[Hero, G2 Touch Android Development] ChosSimbaOne:
thanks right away :-)
[Hero, G2 Touch Android Development] CSL00:
Apart from the 3MP max resolution there isn't much to fix, it's the fastest i've seen the Hero's camera perform. Using WildHero 1.1 .
[Hero, G2 Touch Android Development] erasmux:
Well getting the camera not to crash would be nice.
[Hero, G2 Touch Android Development] jcah73:
The kernel is very fast, but the alarm not work.

I use elelinux 2.4 and venturas 4.6

with kernel_21-05-2011.zip work very well but is not as fast as 4.6

Thanks for your work