yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] dkelley:
bt audio is fine when talking into my bt earpiece too - just got a call from my wife and forgot I had bt on and was wearing earpiece :-)

I'm not convinced bt audio is as loud, either in my ear or picking up my voice, but I have a crappy earpiece so it's really hard to say for sure.

anyway, bt is working so really good news there :-)
[Hero, G2 Touch Android Development] s0be:
Very nice work. I'll be taking a crack at getting heroc to boot while decad3nce deals with some non phone stuff.
[Hero, G2 Touch Android Development] vido.ardes:
I'm actually running Android 2.3.1 with a 2.6.35.10 kernel as my daily driver... whoda thought it? This is fantastic work, the latest flashable is really usable (not as quick as a custom .29, but it gets better with every release!)

I am more than willing to test if you need anyone for the bluetooth fixes
[Hero, G2 Touch Android Development] petsasj:
This is going fantastic! Great job Riemer and Ele.

Does the GPIO setting now affect the accelerometer as well? Or is it still in the same condition? Did you try to look into the nexus one for that?
[Hero, G2 Touch Android Development] sibbor:
So I've been running this kernel for a few hours now, and here's what I have to say:

BT: the headset (3xxPlantronics)

Connects & pairs well.

The audio quality is great in both the microphone and the speaker. Called my voicemail and recorded a new message ;-).

The headset button I push to say "Call X" doesn't trigger any function.

The first time I made a call the sound came from both the phone's speaker as well as the headset for ONE second.

Ain't there supposed to be a headset icon in the bar? There's none, although the BT icon shows a device is connected.

Turning the headset off does NOT disconnect it in the phone. Not sure how it's supposed to be, but I don't think you should manually have to longpress the headset and select "Disconnect" within the BT settings, no? Perhaps I didn't wait long enough.

BT: the WiiMote

Pairs and connects successfully.

Tested the WiiMote together with an emulator (SNESoid) to try to see if it listens correctly for all the bindings. Result? 100% working.

Performance

The kernel is a little bit slower than the previous FlyKernel I was using (wierd... ;-)). Haven't benchmarked it, but at first I was able to multitask pretty well - jumping back and fourth between apps - now it's just too sluggish.

SNESoid so slow, almost not at playable FPS. The sound is also cracking way too much! This has been the case in a lot of ROMs/kernel combinations I've tested before though. Just saying!

Side note: I've had no issues with the phone connectivity (WiFi etc.) as I've seen reported.

Summary: awesome work! Keep it up.

Yeah, thumbs up!

EDIT: since you're the kernel code-monkey perhaps you'd like to check the kernel lagfix (for emulators) out. I'm not aware of what it affects, so just saying - zodttd (creator of the PSX emulator) made a few changes in the kernel code to get it smooth: http://xdaforums.com/showthread.php?t=889503

Since it was a kernel thing, I just wanted to let you know - not a request (or is it?). Don't know if this kernel patching will also work for our Heros.
[Hero, G2 Touch Android Development] ZeppeMan:
So basically everything is working now with the .35 kernel? It still needs speed optimizations?
[Hero, G2 Touch Android Development] gavtaylor:
no, there are still a few things left on riemervdzee list, but the guys have done great so far.
[Hero, G2 Touch Android Development] ZeppeMan:
I see, thx for the link :)
[Hero, G2 Touch Android Development] riemervdzee:
I'll take a look at the gray-ish screen. I think it might be something to look at aye.

Keep in mind that there is still some debugging set. Could be why the boot is a bit long. But it seems the kernel doesn't take advantage of all hardware just yet, I'll run some tests on the .29 one.

And to all, you need to wait to get things started up a little. It stresses the phone out much at start.

Yeah it ain't as fast as the .29 just yet. Especially neocore scores are low (23fps now, while I got 33 on .29). Ofc hope to get it just as fast one day.

Don't know why you lost phone connection, the kernel doesn't get much involved in that I believe. If there are more reports I'll check it out.

Thanks of the detailed report :) As stated by bornin, speed is a tad slow yes. It got better now, and with the BFS patch the UI is a lot smoother as well. But still.... ;) It almost seem we lack some force.

edit:

Btw, don't think this kernel will be the magical holy grail for a working camera. Probably we will go to a .29 interface anyway. As on the ROM side we have a closed library involved which uses the .29 one. To get it working for GB we will have to get the other "normal" libraries to work with the closed library and somekind of camera interface in the kernel. How this will end, no idea ;)

But I think the main advantages are that we can use newer stuff in the kernel. For example we already use a newer version of the usb-driver, newer yaffs. Can put the htc board files more up to par of the other devices. Maybe it'll be more usefull for 2.4 who knows :P

I noticed you forked aye, I'll send you a message on github. Really hope you can get it working. The more people working on it, the better heh? win-win situation :)

Hehe nice, hows the battery life for you? it drops a bit hard here (man, this kernel is full of exiting challenges :P)

Unfortunally, nope. It seems the whole device doesn't get called. I'll be running some tests at .29 for now to see how it interacts with the ROM.

Thanks a lot for the detailed report. Really like them, gives me some ideas hehe ;) It could be that the bt headset not working alright is due some bluetooth settings @ the driver. Will have a later look at it. First I want to get some other HW working properly.

For the emulator. The code the lad proposed is unfortunally for arm7 processors, while we got an arm6. And well... my assembly skills really lack too much to get it working myself. However is there a kernel which does work properly?

Anyway thanks for all the support so far lads :)
[Hero, G2 Touch Android Development] riemervdzee:
Note that the kernel still has some issues.

Besides some Hardware not working found at: https://github.com/riemervdzee/cm-kernel/wiki/Non-working-Hardware

The battery dies quite fast as well. Also the kernel does not like getting turned off brutally, although the android rom should take care of that (if below 5%, turn off). However I got a nasty report that there was some corruption going on.

I always end up with time-resets (using the battery-pull technique, when I got another hang at H2W), which are luckily ain't that bad.

Also, speed ain't up to par with the .29 kernel ones.

Just a little warning ;)
[Hero, G2 Touch Android Development] vido.ardes:
Can't really comment on battery life as I have had it docked to the computer all day, but I left it over night and although it was low when I woke up in te morning, it was only half full when I went to bed. I will disconnect it tonight and let it run flat, which should give us an idea of general performance.

General performance is hard to gauge for me, as I ran flykernel @ 19MHz / 768MHz for so long I am not sure if it is the drop MHz's that is causing the lag or not. I linpacks quite a bit lower, I hit an average on 4.0 MFLOPS on this but I was consistently punching above 5.1 MFLOPS on flykernel12a.

On the topic of stability, again it is hard to gauge as I am running an Alpha of Gingerbread, except the fact that it takes ages to become responsive once it has first booted, I haven't had any force closes or random reboots, not found any software that hasn't worked and ignoring the camera issue I haven't had any hardware problems either (hence using it as my daily driver).

So far it is impressive, and i can;t wait for performance optimisations, but I appreciate you want to work out the bugs before doing too much polishing. Assuming it doesn't get worse, the performance is good enough for day to day use for me, and I haven't got a reason not to use it :D
[Hero, G2 Touch Android Development] dkelley:
my cheapo chinese blutone or wahtever it's called earpiece's button to Call X works perfectly with this kernel.
[Hero, G2 Touch Android Development] Gawis:
tested it on Floyo 1.2 and bluetooth works great with my Mégane built-in bluetooth set

I tried both calls and music over A2DP

wifi works fine and 3G also

boot animation was noticabally choppier than with .29 kernel

also SD check seemed to take longer

I also experienced the color issue, looked more greyisch, blueisch

switched to .29 for now but will surely test other .35 releases

thanks for all your hard effort!
[Hero, G2 Touch Android Development] vido.ardes:
Quick battery update

Running CG v0.0.8

Unplugged at 8:30 am, currently 2:30pm

Usage:

Sent / reccived 30 -40 emails

Made 2 x 5 minute phone calls, received 1 x 5 minute phone call

Twitter & Facebook update every 15min

Location (GPS) and weather for fancy widget update every 30min

Google Sync to 2 accounts for contacts, email, calendar & reader

Played a cheeky 10 minute game of Tetris while in meeting

Battery loss: 25% (75% Remaining)
[Hero, G2 Touch Android Development] riemervdzee:
# Played a cheeky 10 minute game of Tetris while in meeting

lol. Thanks for the update :) I've been working on some microp driver stuff. Think I reimplemented the gpios even better now, however still no luck with the 35 jack. It seems like after the interrupt, it goes nuts. Might post a new flashable soon, it implements BFS to get the ui experience a bit smoother, some configurations and this gpio thingie (which is a little tiny bitty faster). Also bma150 is enabled again, although it doesn't work, it might save some batterylife (the driver tells the device to do nothing, when suspended, correctly)
[Hero, G2 Touch Android Development] vido.ardes:
Yeah, well while the battery life isn't as great as some of the more optimised .29 kernels, it is certainly acceptable, not to forget I am running it on an imcomplete alpha GB rom, it might be much better on 2.2. Looking forward to BFS, hopefully improve the scrolling speed a bit (biggest noticeable slowdown).

Can I request and extended CPU freq. table, as my hero is stable at 19MHZ all the way up to 760MHz and I'd love to abuse that :D
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, with the latest gpio fix I made and enabling bma again rotating seems to work again :)

So bma150/akm8973 works whohoo.

Unfortunally... It makes the system a bit laggier as well, as it keeps spitting events :P the process akmd is at 1% constantly (I guess it is obvious).

I'll see how I can polish it up a little again.
[Hero, G2 Touch Android Development] riemervdzee:
New flashable: http://www.multiupload.com/SA5R71ORSW

Changes:

- bma150 works in combination with akm9873. Rotation, compass and all g-sensor stuff should work normally. Unfortunally it uses some cpu. this is due the microp_i2c driver changes today :)

- Is now bootable without the found gpio_expander I mentioned earlier. It inspired me to patch up the microp_i2c driver. Less code to run, bit faster. And fixes bma.

- Some configs to make it a bit faster

- Applied the Brain **** Sceduler patch and now using it as default. Should make the UI feel a bit faster.

Well unfortunately I didn't fixed the jackplug yet (kinda my goal for today). But the gpio thingie is nice and especially that it got bma working along the way, is quite nice. It is only a bit sad it lacks speed. I noticed that the original .29 got some extra memory code. Maybe that is it, or maybe they just relocated it at the .35 kernel (sigh... :P).

And l0st.prophet, I'll come up with a nicer frequency table soon. Don't like it either, and it sucks up battery as well.

Edit: hmm. all of the sudden bma doesn't work anymore. I'm getting messy I think ;)

Edit2: Re-uploaded. It is due some experimental lightsensor code I was trying and removed before uploading. It seems to be involved with the bma150 though. (will have to investigate), reimplemented it and bma works again.
[Hero, G2 Touch Android Development] ggrammer:
not messy just awesome...fricking awesome.

this thread is awesome to follow, some cool stuff in here...too bad I'm not S.M.R.T enough to help out.
[Hero, G2 Touch Android Development] dkelley:
Riemer,

Did you forget to extend the NIC with the SSID so the BIGHT pulls FOREPEAK over the HOLODECK'S virtual BLACK HOLE while the NANOMITES create a new TRUSS ROD to retain tension behind the SHIFT SOLENOIDS and SPRAGS?

when I forget to do that I find my cpu never sleeps well too.
[Hero, G2 Touch Android Development] riemervdzee:
My CPU is very good at sleeping, unfortunally it never wakes up. And when it does, the dishes are already cleaned. (I do hope ggrammer now understands that your post is boggus? :P)

Have a good weekend man ;)
[Hero, G2 Touch Android Development] ggrammer:
what dkelley was making that up? I am thoroughly depressed now.

:p

Last night I was thinking I should really make an attempt to try to learn C, but then I got lazy and saw a pretty light and forgot what I was doing for awhile. lol.
[Hero, G2 Touch Android Development] kiljacken:
Don't mess around kid!! GET THOSE HYPERDRIVES WORKING!!! CHARGE THE ION CANNONS!! FULL THRUST ON THE SUBLIGHT ENGINES!!!

Dang.. Now our only hope is the very unstable quantum teleporter...

You have DOOMED us all!!
[Hero, G2 Touch Android Development] dkelley:
cheers dude. :)
[Hero, G2 Touch Android Development] dkelley:
OMG I have that problem too
[Hero, G2 Touch Android Development] vido.ardes:
Flashed latest version.

Good news: noticably quicker :D

Bad news: kinetic scrolling broke :(

That is all
[Hero, G2 Touch Android Development] thantos2024:
Definately quicker, good job on the sensors. Not having any issues with scrolling myself, except for it lagging on first boot.
[Hero, G2 Touch Android Development] flzyup:
I compiled it from elemag's branch yesterday. Almost everything work except camera and headset. The good news is that whatever you touch the shot btn in camera, it'll not freezen.
[Hero, G2 Touch Android Development] riemervdzee:
Hmm, I hardly touched the touchscreen code (read, not). Maybe it is due the lack of frames/sec?

Keep in mind that the lightsensor is still ain't working. Not sure whether I made that impression
[Hero, G2 Touch Android Development] rdejager:
The progress on this went fast, nice work guys :D

When the audio jacks are fixed, I am def going for a second try on this :D

The first was well a no go, never went past my splashscreen. :P

looking forward to the progress.

Succes :D
[Hero, G2 Touch Android Development] riemervdzee:
Lol, cyan just created a .37 branch.

Anyway have been working on htc's masterpiece again today, the microp driver. Narrowed a bit down where the problem lies, but no fix yet :-/ Both the lightsensor and jack-headset rely on it. Seems to be a nasty bugger actually.

@rdejager, you mean the hero splash screen or ROM? Which recovery are you using to flash?
[Hero, G2 Touch Android Development] riemervdzee:
Well found the biggest mistake in the microp driver from HTC I guess (read longer log)

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

So that fixes everything I guess :) Hopefully there aren't anymore mistakes in that evil non-zealous driver.

Will post a new flashable soon, with working headset (on the jack) and lightsensor :)

Only left on the todo list:

- Get speed (lots of it)

- Camera
[Hero, G2 Touch Android Development] treesurf:
Well done sir!
[Hero, G2 Touch Android Development] EnsconcE:
This really rocks guys, i was following the development from a distance. This good news :) ! Keep up the good work
[Hero, G2 Touch Android Development] riemervdzee:
New flashable:

http://94.23.152.245/xda/rmr/rmr35-015.zip (thanks to Wupper!)

http://www.multiupload.com/43Q8P72MDN

What should work:

- headset via jack. Could anyone test whether the buttons on headsets and microphone work?

- lightsensor
[Hero, G2 Touch Android Development] Wupper:
I've dropped the kernel on my server: here

(ik zal de volgende flashables ook op m'n server gooien mocht je willen :) )
[Hero, G2 Touch Android Development] rionline:
damn, it is getting hot! :D
[Hero, G2 Touch Android Development] k0rner:
Buttons and microphone on stock Hero headset work for me.
[Hero, G2 Touch Android Development] sotux:
Tested it with stock HTC Sense 2.1. The wake up issue seems still exists (lock screen color mess. I use setcpu to set the min freq @352Mhz) Tried camera and it exited(I know it hasn't finished yet,just a try), but the music player couldn't output sound anymore after used camera. The music player crashed, seems couldn't recover.

The whole speed is ok. It's amazing.Thank you for your great work.
[Hero, G2 Touch Android Development] brat.haneq:
http://www.sowa.eu.org/bieganie/xdakernel/rmr35-015.zip

Quick mirror, on my google apps domain page.

Cheers!

brat.haneq
[Hero, G2 Touch Android Development] petsasj:
Oh my gosh! Thanks so much Riemer! This is FANTASTIC news, seriously.
[Hero, G2 Touch Android Development] mljjlm:
I'm using it on a Sense 2.2 rom (ChocolateFroyo), I do not have wake-up-issues but I recognize the color-mess (the screen are getting a bit blueish and there are horizontal lines on the screen, not bad though) - The camera is not quitting on 2.2 sense, but it shows some weird stuff, and freezes eventually.. I'm able to quit the camera-app and the music app still works. Heads up! Good stuff guys! :)
[Hero, G2 Touch Android Development] vatvedt:
Awesome work! Hoping the camera issue is fixable. Would be great with .35 kernel and GB fully working on the Hero. Who would have thought :D
[Hero, G2 Touch Android Development] vido.ardes:
Thanks for the update Riemer, my first impressions:

The performance is improved over the last release although scrolling appears to be the most noticeable slowdown

Only performed basic tests, but headset with inline controls appears to work as expected

Although the auto-brightness setting doesn't appear to work, testing software shows the light sensor registering different values so it looks like the sensor is working (auto-brightness may be a bug of the ROM rather than the kernel)
[Hero, G2 Touch Android Development] sotux:
Yes, I means the color-mess . :)

Is it an early suspend initial problem?
[Hero, G2 Touch Android Development] thantos2024:
Nice job, tried on a froyo rom, headset controls worked fine for me, camera preview looks good, was able to play round with all settings fine, once you've nailed out the loop that seems to be happening so it will actually take a pick, can see this being the kernal of choice for all future rom dev.

Oh, just tried and video recording seems to be working fine, it'd just trips up when you try and take a still, not at my comp to pull a log, but will see if Android System Info logs show any specific errors

Don't know if this is useful but ASI log shows the following errors,

E/mm-camera 7x-vfe (713)

output2YBusOverflow = 1

E/mm-camera 7x-vfe (713)

WB-EXPStatBusOverflow=1

E/mm-camera-af (713)

Lens move failed.

E/mm-camera-af

Reset lens failed
[Hero, G2 Touch Android Development] petsasj:
I am currently trying some wipe battery stats so i cannot reboot my phone just yet (even though i'm desperate to try this out :P).

Did all micro2p problems get solved? Aka lightsensor AND LED notifications + trackball notifications?
[Hero, G2 Touch Android Development] thantos2024:
Led's and trackball appear to be working fine to me, am using latest build with ele's 6.2 RC0 and so far the only thing that doesn't seem to work is taking photos, although camcorder does work fine. Once that's fixed it'll just need optimizing for speed. All credit to the dev's for this, they have brought this kernel a long way in a short space of time.
[Hero, G2 Touch Android Development] Gawis:
This is indeed running fine

Gonna keep this for a while to see how it goes

Did experience 2 reboots while navigating with Copilot and a call comes in (memory issues?)
[Hero, G2 Touch Android Development] rdejager:
I tried 2 flashables as of late, and both the same problem. It wont go past the boot screen. So cant test it really, after 30 min still at the spashscreen.

Tried it on Elelinux 6.2.0 and Cronos GB 0.0.8

Both no go :(
[Hero, G2 Touch Android Development] riemervdzee:
Just wake-up issues concerning the cpu frequencies. I kinda think it is a minor thing, but I'll take a look at it today.

I deliver the .35 interface to the camera libraries, while most roms use the .29 interface (bit mixed with .32 for froyo). To be honnest I find it surprising there is something viewable ;)

It should aye. No problems here :)

Yeah most stuff works, what I really like. However the speed issues is something which bothers me a little. Luckily the HeroC also almost got their .35 kernel booting. Hopefully we both s0be and I can make some nice running kernels for both hero versions :)

It is still in debug mode, so it reboots as something bad happened (it is a feature! :P). Could you please pull /proc/last_kmsg for me after it happens again? this contains the dmesg after rebooting.

Which recovery you use? I got the newest yaffs2 driver running in this kernel. However it requires the ROM and kernel to be flashed with the new driver as well. Amon_ra 1.7.0.1 supports this new yaffs2 driver (hurray!).
[Hero, G2 Touch Android Development] thantos2024:
Well have only tried camera and camcorder on 2.2 so far, but could swear preview and video look better with this v's standard kernel, but could just be my imagination.
[Hero, G2 Touch Android Development] mljjlm:
Does this mean that the camera-driver is actually working, but the camera doesn't work due to ROMs not having the .35-interface implemented?
[Hero, G2 Touch Android Development] thantos2024:
Hmm, I guess the only way to know would be for someone to try compiling a rom with the .35 interface and see what happens.
[Hero, G2 Touch Android Development] riemervdzee:
Well it ain't really that simple to say "it is the ROMs fault". This ain't really my territory. However keep in mind that the kernel and the ROM have to work together to get any hardware working at all.

I think the biggest problem with the camera is the closed source library, which seems to control the whole bugger. I believe it was already a bugger to get it working for Froyo, while it supported the legacy (eclair) a bit in someway. However It seems that GB only supports froyo cam-stuff a little.

Probably nothing ;) A lot of the camera control is defined in userspace libraries.
[Hero, G2 Touch Android Development] Bornin:
Right, as you probably read already on Cronos board this kernel seems to have ruined my WIFI.

Actually I don't remember it being broke while I was running this Kernel. I think it was the moment I flashed Feeyo's EVO for GB Kernel that broke it.

I dumped a logcat for you here http://paste2.org/p/1198932

I personally can't do **** with that logcat blabla but what I did notice was this: "levelup.beautifulwidgets/.WifiWidget"

I never installed that widget so, what's it doing with my phone?

Cheers,

72
[Hero, G2 Touch Android Development] riemervdzee:
Could you flash it again in amon_ra, copy the log to sd (option somewhere in recovery) and see if the copying really went ok?

I suspect the /system/ being full.

Also, maybe "adb shell dmesg" prints something more useful.

Edit: I'll see how I can modify things a little to make the kernel-package smaller in the future.
[Hero, G2 Touch Android Development] rdejager:
I use that recovery, I hate CW. Looks to well not nice.
[Hero, G2 Touch Android Development] riemervdzee:
@rdejager,

hmm strange. If you got the newest one, it should work like expected. Can you get into adb shell when booting? maybe get me an dmesg?

@borning

Hmm, copying goes ok it seems. Could you get me a dmesg when trying to open/close the WiFi?
[Hero, G2 Touch Android Development] thantos2024:
Ive just tried flashing the cronos gb kernel onto a fresh 0.0.8 install and my wifi broke so think this is a cronos kernel fault rather than a .35 kernel fault, tried as i recalled having a similar experiance when i'd tried a flykernel and wanted to compare to the cronos one.