yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] Bornin:
Something like this: http://paste2.org/p/1199488
[Hero, G2 Touch Android Development] riemervdzee:
Could anyone test Cronos GB with the flykernel and see it has the same WiFi problem?

It looks like it starts just perfectly, but the attachement to the OS ain't done or something :-/

I'll look at it when I got the time. Got examweek this week, so I actually have to spend some time at studdying hehe ;)
[Hero, G2 Touch Android Development] bluepinkpanther:
On Cronos GB is small problem with wifi after first boot. Reboot few times and check.
[Hero, G2 Touch Android Development] rdejager:
riemer Ill try when I got a little more time, thanks for the help so far already :D:D
[Hero, G2 Touch Android Development] chemical1979:
Just to understand - how can a disabled vsync increase anything?

In contrary I would guess that if the chip is able to deliver more fps than the display it will calculate them (without being able to display them), thus burning more energy from the battery than required (while being idle in the other case with enabled vsync).

As a second thing this may cause tearing on high fps running games,..?

It can speed up the graphics if the fps limit of the graphics chip was lower then the display fps, but ... was this really the case?

Anyway, thanks for your work. I'm not as active as others in the forums, but following development closely.

Thanks

Roland

PS: It will perhaps "accelerate" benchmarks which count the fps, but that does not necessarily change a thing in real life.
[Hero, G2 Touch Android Development] riemervdzee:
As a general remark: Vsync always delays things a little. Unless you have 3 draw buffers, the back-buffer can't always be written to. As with using this technique there are a few moments when the display driver can offer data to the display, and therefor even might stale any writes to the backbuffer. Also the FPS which gets calculated (on the cpu) is capped to a max, I believe at 60 frames per sec. So it would never just "burn" battery or CPU cycles as you imply.

For tearing, I never noticed it on 15inch in earlier times. Now I got my 21inch I see it sometimes, however it only occurs when framerates changes with high ammounts (from 60 suddenly to 20 and then back to 60). I think you'll hardly notice it on a small screen. Btw, the hero got no crt monitor screen ;)

However you should consider it as a "stripped vsync" for now, as I found the definition coming up in a few files as well. Disabling it totally, yields in a non booting kernel.

However a quite large part has been removed, and it increased the overal speed. I cannot tell the exact changes between the two versions. For except it runs better. I could go deeper into it ofc. But we got over like 300 files of these buggers we need to fight against, and we all want a working .35 kernel fast.

Just in case I delivered a "wtf" feeling ;) At the moment the vsync (where it can be found) is almost identical to the one found in the .29 kernel. Where it doesn't, is an improvement over the .29 kernel (implemented at the .35 by google).

I can prove it in numbers (neocore) but also in feel (both Elemag and I found it working way smoother. Just like some of the testers). Just take the flashables for a spin, or unroll the commit at github if you still are troubled :)
[Hero, G2 Touch Android Development] johanson24:
Hey Riemer,

first of all, thanks for your awesome work. I never thought that we got a .35 for our Hero's,... ;o)

I have here a Cronos GB with flykernel 12a running and WIFI works perfect.

If you need a logcat or dmesg write it, i will post it then.

Good luck for your exam ;o)

Johanson
[Hero, G2 Touch Android Development] riemervdzee:
Cheers, just needed a confirmation :) I'll check it out
[Hero, G2 Touch Android Development] thantos2024:
Well have done a bit experimenting and its definatly the cronos kernel that has the wifi issue not this one. Have tested with flykernel .35 kernel and cronos evo all on fresh install of 0.0.8 and i only get wifi issues after flashing cronos evo kernel.

How I tested:-

0.0.8 - .35 kernel, wifi works

0.0.8 - .35 - flykernel, wifi works

0.0.8 - .35 - cronos, wifi fails

0.0.8 - .35 - flykernel - cronos, wifi fails

0.0.8 - flykernel wifi works

0.0.8 - flykernel - cronos wifi fails

0.0.8 - flykernel - .35 - wifi works

0.0.8 - flykernel - .35 - cronos wifi fails

0.0.8 - cronos wifi fails
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, it makes no sense. Others report they got no WiFi with this kernel?

Only reasonable conclusion is that the /system/ is full.
[Hero, G2 Touch Android Development] hi_robb:
I think I might know what the general cause of the WiFi issue with Freeyos GB rom and kernel is.

The symptoms are exactly as described. On boot up of the phone, WiFi refuses to start. Sometimes a restart fixes it, sometimes not. However, I also found that even just switching Wifi on and off would sometimes cause the issue to happen.

So I done a bit of investigation and found the following...

It would appear that every so often, when wifi is being turned on or off (boot, shutdown, or user initiated), the wifi regulatory channels option gets reset from it's default of 13 (or 14), to 11.

If your wifi router is set to broadcast / receive on a high channel, the hero won't connect to it then.

You can verify the issue is this by going into your phones 'wifi settings', pressing the 'menu' button, then opening the 'advanced' option which appears. Finally click on 'Regulatory Domains' and check what it's set to.

It will be 11.

To fix just set it to 13 or 14.

Most home routers tend to pick a lower channel automatically and only use the higher channels if set manually. This might explain why it's only some people who have found the problem?

11 channels are also what the Yanks use, could this be a hangover of something ported from some CDMA code?

Dave
[Hero, G2 Touch Android Development] mljjlm:
When I had the WiFi-issue (on CG 0.0.8) it just wouldn't turn on. In the logcat it said that the tiwlan0 (the wifi-device in the hero i assume) wasn't found :) - had nothing to do with this kernel btw.
[Hero, G2 Touch Android Development] dkelley:
yea it's more than the number of channels - it's wifi stuff in the phone being corrupted or something like that I think. maybe flashing feeyos kernel over this one has some incompatibility in the wifi stuff cuz it invariably results in "error" or "fout" or "fail" or wahtever showing in wifi when you try to turn it on. And this is not a standard android wifi error message - it's a pretty extreme one, like your phone's telling you that something is broken in wifi, not just that it can't connect.

it's still a guess as to why this is happening, but it unfortunately means that it's not too easy to try this .35 kernel in gb since it's nearly impossible to go back to .29 fully working without a full reflash of the rom (which ain't fun with gb's current install flashing dance party).
[Hero, G2 Touch Android Development] riemervdzee:
I'm starting to think the "problem" is quite small. There is some (.35) junk left over when another kernel gets installed over this one I guess. I'll check out how the Cronos kernel gets installed
[Hero, G2 Touch Android Development] hi_robb:
Ah ok guys,

Well it looks like there's also some sort of bug with channels resetting in the Cronos GB release.

I just seen people mention the rom and wifi problems and thought I'd share my findings. I shall fully read the posts next time ;-)

Dave.
[Hero, G2 Touch Android Development] dkelley:
not to worry - every bit of information that's meant to be helpful is always a good thing :-)
[Hero, G2 Touch Android Development] sylvaindaltair:
Cam

some improvement have been made on the cam side on the tread "CM 7.0.0 RC0 (Pre-Alpha - Gingerbread) - TESTERS NEEDED" of cyanogenmod.
[Hero, G2 Touch Android Development] riemervdzee:
Sorry if I sounded a bit grumpy, guess I don't like studying too much. No, exactly like dKelley stated, every input is welcome. Throw anything in you like, maybe even your assumptions of what is going wrong etc. They are always inspirational :)
[Hero, G2 Touch Android Development] riemervdzee:
New flashable:http://www.multiupload.com/DD0PTD9G1W

mirror: http://94.23.152.245/xda/rmr/rmr35-017.zip

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

Version: rmr35-017 (16 was a fail...).

Changes compared to the last one:

- Boots up at 633mhz instead of 691mhz. Just for safety.

- uses the standard htc qdsp5_comp. Better and faster support for media. I find sound-handling much smoother now. Unfortunately, camera is totally dead after implementing this.

- Uses only 7 separate modules instead of 24. Some are included into the kernel right away, and some were removed. Hopefully this solves the "going back to another kernel" problem a little.

If you have flashed a previous version of this kernel, they are probably still there. You can remove them manually by cd'ing to /system/lib/modules/. Then remove all "*.ko" modules, then reboot into recovery and re-flash the kernel (so it copies the modules the kernel currently uses back to that position again).

If people find this hard, I think I can make an update.zip which removes the junk. You'll still have to re-flash the preferred kernel ofc.

Nothing much special I'm afraid. I've been playing with the frequency table a lot lately. But it reboots sometimes when getting out of suspend (been using flykernel's table for example).
[Hero, G2 Touch Android Development] Wupper:
Mirror for the latest flashable: here :).
[Hero, G2 Touch Android Development] hi_robb:
You didn't sound grumpy, in fact you had no sound at all, is this a bug in the forum :-)

Dave.

P.S I've actually found a solution to the issue with the Cronos 0.0.8 GB losing WiFi due to resetting the channels now.

I edited the build.prop file and there's a line in there regarding Wifi Channels, it was blank. I put =13 on the end, saved build.prop then restarted. I haven't had any issues logging in to my Wireless LAN since.

He's released 0.0.9 now, I don't know if this little bug still resides in the new version. I'm about to flash to find out.
[Hero, G2 Touch Android Development] vatvedt:
I'm guessing it does. 0.0.9 is just a repack with all the patches after 0.0.8 included. (Except camera fix though)
[Hero, G2 Touch Android Development] Cortiis:
Giving it a shot right away. This was bugging me for long. Thanks a lot.
[Hero, G2 Touch Android Development] rdejager:
I just think you fixed my boot problem, Gonna try this one now :D

Edit:

Ok booted and it works with my house call system, that is a big plus for me :D

So far so good. audio works fine, Well great, and about the screen speed, nope not so great, but not that I care, I must say, Awesome work :D.
[Hero, G2 Touch Android Development] riemervdzee:
Nice it works out for you :) always thought this was the problem for you, luckily it is ;)
[Hero, G2 Touch Android Development] vorcigernix:
cam

read here: http://forum.cyanogenmod.com/topic/...alpha-gingerbread-testers-needed/page__st__40

SteelBytes have a new module, will be worth try against this kernel.
[Hero, G2 Touch Android Development] mljjlm:
Doesn't work with this kernel on Cronos Ginger 0.0.9 beta ;)
[Hero, G2 Touch Android Development] vorcigernix:
shame..it does not load or what?
[Hero, G2 Touch Android Development] mljjlm:
Black screen and a very laggy phone.. and if I tried to launch the camera app again, it told me to reboot ;)
[Hero, G2 Touch Android Development] riemervdzee:
Camera is totally broken on the kernel side after adding qdsp5_comp. I'll be looking at it the comming few days :)
[Hero, G2 Touch Android Development] riemervdzee:
To keep you lads informated:

4 days ago I tracked down some annoyances in the mmc part (sd-card/WiFi). Updated here and there, and some lagspikes are gone now. Unfortunally when plugging in a usb linked at the computer, you won't receive a mount-as-usb-disk notifaction and the debugging one. While adb just works perfectly. the mounting as usbdisk is annoying though, gonna see look at it later.

After that vsync conversation I had another go at it. Yesterday I reverted the mentioned file to the .35 one used by CM, and patched our hero-specific panel driver so it matches it. and there is no speed drop anymore as before. Also removed some unnecesary checks at the panel-driver making it a little faster.

Today I've been working on the camera. While getting the preview to work again was a fairly easy job, getting a picture isn't. Although I've been able to make 3 pictures, while around 21 failed. I have a hard time getting it stable atm. Maybe tomorrow more :)
[Hero, G2 Touch Android Development] swatsbiz:
Sounds impressive progress, keep it up.

If it's unstable but working I'm sure you've broken the back of the thing and we'll have the latest kernel up and running perfectly soon.

Well done!
[Hero, G2 Touch Android Development] gavtaylor:
really appreciate you keeping us informed on where your up to, cheers fella :-)
[Hero, G2 Touch Android Development] petsasj:
Great job riemer, thanks for keeping us posted. All the best!
[Hero, G2 Touch Android Development] J0s3f:
Any chance to get rVoix or another Call-Recorder that directly records the call (and not the oter person only through the mic in handsfree-mode) to work with this kernel?
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, it doesn't already? In flykernel it does work right? he ported the .34 version I believe, so it should work in this .35 kernel. I'll take a better gaze at it soon
[Hero, G2 Touch Android Development] thantos2024:
Nice to hear its coming along, looking forward to testing your next release, ty for all you hard work.
[Hero, G2 Touch Android Development] pulser_g2:
Thread owner changed from Elemag to Riemervdzee
[Hero, G2 Touch Android Development] riemervdzee:
Cheers pulser

To celebrate it, there is a new flashable for you lads available ;)

Version 0.1.8:

* Camera is almost in a working state. You can create pictures the first time you open a camera app. After closing and reopening, it is failing and might cause battery drain (requires reboot).

edit: it seems it is always failing in the uploaded build... It really requires more work edit2: it works sometimes...

* mmc drivers are updated, however mounting the sd as usb-storage is not working any more

I will now try to co-ordinate things as much as possible in the Opening Post, the download can be found there as well. More text/lay-out etc will be added tomorrow I guess, first some sleep time ;)
[Hero, G2 Touch Android Development] dkelley:
hahaha edit1: it doesn't work edit2: it works edit3: it works sometimes edit4: godamit wtf LoL

I feel for you riemervdzee... that must be really frustrating.

congrats on the new build though - I'll hold off until you've slept and had some in-sleep insights and creative brilliance as usual.

cheers
[Hero, G2 Touch Android Development] oostah:
Is this kernel for the cdma hero?
[Hero, G2 Touch Android Development] kiljacken:
No, it's for the GSM Hero :)
[Hero, G2 Touch Android Development] oostah:
Ok thanks they are working on .35 for the cdma its not this far yet.?
[Hero, G2 Touch Android Development] riemervdzee:
S0be, the lad who is working on the cmda port of this, has problems of getting it stable. Although this kernel suffers the same problem, it almost doesn't occur at all. Been running this kernel for well... since the start, and only got it once so far. No one else complained about it as well :) While he gets it quite often I'm afraid.

I think when things are getting stable, I think he will get most of the hardware working quite quickly.
[Hero, G2 Touch Android Development] elelinux:
Has unfortunately not had time to follow the thread all the time,is there support for ext 2-3-4 ? ,time for me to start testing soon this kernel is really interesting for GB.

Edit : Can download your source and compile it myself but are lazy by my nature :D
[Hero, G2 Touch Android Development] Wupper:
Is the kernel posted in the op the latest one?
[Hero, G2 Touch Android Development] lynx2k50:
Yeah it is.

Go 4 the cam mate! You've done it almost!
[Hero, G2 Touch Android Development] Wupper:
Also mirrored on my server :). here
[Hero, G2 Touch Android Development] riemervdzee:
Filesystems:

- ext4. ext4 is used for ext3 and ext2, to save space. However I still recommend ext2 partitions, as they are suitable enough and faster (unless you do some data2sd or so)

- Fuse

- fat and vfat (no ntfs or ms-dos fat)

- yaffs1 and yaffs2. Note that yaffs2 is a newer version than used in .29 kernels and require the ROM and kernel to be flashed with amon_ra 1.7.0.1 (which also supports it). Otherwise you'll probably get a Hero screen or even reboot into recovery ;)

- Squash

- NFS

- SunRPC (as module)

- Cifs

IPv4 and IPv6 are used as well. Not sure how it affects the android ROM, but sounded like a good idea as we run out of the first ones.

Still... the kernel is quite slow as compared with flykernel for example. Having a slow ROM at it, would be quite a killing for the user I suppose

edit: thanks wupper :)
[Hero, G2 Touch Android Development] elelinux:
Thanks for your quickly reply :D
[Hero, G2 Touch Android Development] riemervdzee:
I got the camera much stabler today. Gonna test it a little this evening and hopefully everything works fine now.

Then maybe some cleaning up here and there and I'll post a new flashable again :)
[Hero, G2 Touch Android Development] lynx2k50:
Whaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaat? You have got the camera working????
[Hero, G2 Touch Android Development] riemervdzee:
Sometimes it does, sometimes it doesn't... It starts to annoy the hell out of me.

Think I will never use the camera again after all this, hehe
[Hero, G2 Touch Android Development] lynx2k50:
Ha great mate. Its unbelieveble that you have come so far. Wah fantastic.

Dont know what to say. When you get the camera really stable is any hardware missing?
[Hero, G2 Touch Android Development] dkelley:
If I remember correctly, ipv6 is required for certain apps to run. goggles maybe, not sure if I'm remembering right. but I suspect it's a good idea.

erasmux went through hell with users for not having it in early versions of fly, I think, again not sure about my memory.
[Hero, G2 Touch Android Development] swatsbiz:
Hey Don,

Yeah Goggles needs ipv6, and it was one of the only ones, but I guess we'll see more apps using ipv6 this year as we start running out of the v4 ones.
[Hero, G2 Touch Android Development] riemervdzee:
Pff, I had a lot of failing builds the last few days. Even taking one didn't worked...

Finally I found out that I was using on-demand gov. while I always used performance before. It seems the camera requires a stable frequency overtime with the help of performance-locking...

I've heard that before tbh, but seems I forgot about it.

Will implement it today. Unfortunally I removed a lot of code as well as I thought it might not be working (as it kept giving me black screens), so I'll have to redo some stuff again.

Agh... sometimes things are so easy in the end.
[Hero, G2 Touch Android Development] rdejager:
I see you got the first post :D

Nice, Good to track updates.

To bad the USB mount broke on the last one.

Your progress is going fast.

Looking forward to your new build.
[Hero, G2 Touch Android Development] thantos2024:
Been running for a couple of days and is looking good, video definatly seems better on this kernel compared to .29, just needs issue with still photos fixing and some speed optimization. Other than that perfectly stable with elelinux 2.3. Looking forward to trying your next update.
[Hero, G2 Touch Android Development] riemervdzee:
Nice to hear it works out good for you :)

Unfortunally I haven't had much progress lately. Kinda stuck with camera and optimalisations... Think I will collect some data and send it to other people for some pointers.

Think I got the problem bout the usb/debug notifications though. But that's all lately :-/
[Hero, G2 Touch Android Development] Nx6:
Yeah, that kind of sucks. :) Porting 2.6.35 to the Hero is really impressive, but as you say it will be a hard sell if the performance drops. Do you know why it's slower?
[Hero, G2 Touch Android Development] SwatMaster:
Hey man, any update? :)
[Hero, G2 Touch Android Development] riemervdzee:
Not much I'm afraid. I think I'll try to fork the .37 and re-commit (and recheck them) the changes I made. Maybe I can get some inspiration from it.

But atm, I can really use some help if anyone is still out there hehe ;)
[Hero, G2 Touch Android Development] dkelley:
how about emotional support?
[Hero, G2 Touch Android Development] takuhii:
This kernel is look pretty good. I'm not a DEV, but I am curious to know. If a ROM has the camera working, then you flash this Kernel over the top, would that then stop the camera from working?

Probably a stupid question I know...
[Hero, G2 Touch Android Development] kiljacken:
The camera would work in the first picture you take, and then it'll break until you reboot :)

-- Kiljacken
[Hero, G2 Touch Android Development] SwatMaster:
I have no knowledge of C programming and kernels, otherwise I would love to help ya :(

Maybe by the end of summer I would be helpful, but now I only know only Java...
[Hero, G2 Touch Android Development] thantos2024:
Same problem here, no programming skills although am reading up so maybe this time next year ill be of some help lol. However and happy to test builds and post up logcats if of any real help to you.
[Hero, G2 Touch Android Development] riemervdzee:
I'll be working on it again the next few days. Currently added quite some debugging info at the microp driver, as the HeroCMDA version got stability problems with the current impl.

Hope he can gets it stable and most of the stuff working, so he can find some time to look at the speed issues as well.

Got the idea it has something to do with the backlight though, as it is playing some funny tricks with us.

Currently testing some stability problems with the cpufreq. I really want to use the ones from Erasmux' flykernel. However when I use them, it reboots at waking up... :P Currently playing with that a little.

Edit: probably I will upload a new build soon :)
[Hero, G2 Touch Android Development] riemervdzee:
A new version is available from the start post :)

Version 0.1.9

Improved stability when going from wake to sleep and visa versa

Took CPUfrequencies table from Erasmux' flykernel. Due the improved stability these don't hang anymore hopefully

Better battery live when asleep. Should be now the same as .29 when the phone is sleeping.

Could use some testers to see whether the cpu frequencies now are stable. I haven't had a reboot yet after the stability changes though. If you have a reboot (when trying to unlock seems a common one), please post your cpu profiles settings.

Enjoy
[Hero, G2 Touch Android Development] Wupper:
Mirrored here
[Hero, G2 Touch Android Development] Dr34mc4tch3r:
Awesome work riemer. I can test tomorrow. Do you have any preference which rom i'm gonna test it with? Im runnin cm7 nightlys by default.
[Hero, G2 Touch Android Development] riemervdzee:
Cheers, added at TS. You are quick btw ;)

Not really :) Since you are using GB, could you please test video-recording on it? Photos are too unstable unfortunally. I'm still using Froyo here. Thanks a lot in advance :)
[Hero, G2 Touch Android Development] Hacre:
Well by specific drivers, I'm referring to board-hero*.c. There shouldn't be anything else in the Hero hardware that can't be served just fine by the 2.6.34 drivers, since the hardware is mostly identical to the G1.