yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] MallardDuck:
s0be, i think you're going to blow up the hero scene again. with deca and you working together there's been a lot of progress recently and i want to thank both of you. i really love my hero and you guys keep it feeling young.
[Hero CDMA Android Development] jmkarnai01:
AND HOW!!!!!
[Hero CDMA Android Development] s0be:
More commits

More Progress

http://android.pastebin.com/rqm0Vn1p
[Hero CDMA Android Development] andythegreenguy:
You guys are pure AWESOME!
[Hero CDMA Android Development] MallardDuck:
S0be, i was wondering your opinion, once this kernel is completed and we get GB running smoothly, will the supposed 2.4 GB update break everything that is already working or just maybe the new stuff will have to be worked in properly?
[Hero CDMA Android Development] s0be:
no clue

http://android.pastebin.com/SSRM5MKB
[Hero CDMA Android Development] oostah:
Dang sobe making progress good work man. Thanks!!!!!!!!!!!"!
[Hero CDMA Android Development] s0be:
http://android.pastebin.com/qKr6wEtY

Some more progress, looks like just the smd and i2c errors are left to fix
[Hero CDMA Android Development] laie1472:
Looking forward to this. And wow you work like super man lol but thank for the time and hard work.

Root-Hack-Mod-Always™
[Hero CDMA Android Development] kurigowa:
Just curious, will you guys be running AOSP's GB or will this kernel allow for a less tweaked version of GB? Thanks! Great Job!
[Hero CDMA Android Development] dbayub:
The smd stuff is because it used to call both v1 and v2 alloc, and as long as one succeeded, it was OK. Now it's ifdef'd to use different code depending on if CONFIG_MSM_SMD_PKG3 is set or not. Looks like the package 4 code is what works on heroc. With that change, the smd code works.

[ 3.684967] smd_alloc_channel() cid=01 size=08192 'SMD_DIAG'

[ 3.686340] smd_alloc_channel() cid=02 size=08192 'SMD_RPCCALL'

etc. Then it's the i2c failures:

[ 3.841674] msm_i2c msm_i2c.0: Error during data xfer 1e (-5)

[ 3.852203] msm_i2c msm_i2c.0: error, status 63c8

and oops:

[ 4.861785] Internal error: Oops: 80000005 [#1] PREEMPT

[ 4.863433] last sysfs file:

[ 4.864318] Modules linked in:

[ 4.866058] CPU: 0 Not tainted (2.6.35.10-cyanogenmod #11)

[ 4.867706] PC is at 0x0

[ 4.868682] LR is at microp_i2c_probe+0xb70/0x1438

[ 4.869598] pc : [<00000000>] lr : [<c0217e64>] psr: 60000013

[ 4.869659] sp : cc219e10 ip : cc219d10 fp : cc219e74

[ 4.872100] r10: c040eef4 r9 : 00000000 r8 : 00000005

[ 4.873748] r7 : cc255da0 r6 : c040ea10 r5 : cc255d80 r4 : cc48a760

[ 4.874694] r3 : c040ea2c r2 : 00000002 r1 : cc219ce0 r0 : cc219e3c

[ 4.876342] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[Hero CDMA Android Development] il Duce:
Just dl'd, I figure if I donated I should test. I'll report tomorrow.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] s0be:
No clue about that... flashed fine with ClockworkMod Recovery. Will make a change for ya... Will you test #45-amonra?
[Hero CDMA Android Development] radrian92:
#45 is working really well. Haven't encounter any bugs nor any reboots! Thanks sobe!
[Hero CDMA Android Development] s0be:
Just had this happen to me. Will look into it next time it happens (and it's not 4AM, and I'm not drunk)
[Hero CDMA Android Development] il Duce:
so far so good... TS seems less responsive on scrolling. Crazy how far this has come, nice work. Seems as fast as .29 after it warms up. Weird but after I flashed it some of my apps werent there, i dont even know how that could be related, but... I hope your Aria never shows up.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] pstevep:
Thats understandable...
[Hero CDMA Android Development] cteneyck:
Hey Sobe. Does your get hub reflect all your work up to #44?
[Hero CDMA Android Development] zanywood:
Yeah had problems with certain apps not showing up also but no biggie.
[Hero CDMA Android Development] cteneyck:
Also i take it you are not gonna backport the headset detection from the .29 kernel

NVM: did you have it turned off in the config on purpose?

NVM: I see the errors
[Hero CDMA Android Development] roundaway:
flashed the CW recovery on the aospCMod OP

kernel flashed

tun.ko works! just need to play with the OpenVPN Settings and should be back in service

hope you were able to rehydrate :)
[Hero CDMA Android Development] pstevep:
so in fear of jinxing myself.. i actually feel like i am seeing slightly better battery life with this kernel.. i have been using it all weekend, and since i have gotten the hang of it not sleeping at first, i am running pretty well battery wise.. maybe its just the honeymoon period though..
[Hero CDMA Android Development] s0be:
I think github matches 45, might be missing the tun.ko .config change, but other than that, I try to keep it pretty up to date.
[Hero CDMA Android Development] s0be:
I have not even played with h2w much. I had bigger fish to fry. Probably try to get it fixed tomorrow. Now that everything I use in the kernel works, I just need to fix these rough edges.
[Hero CDMA Android Development] s0be:
The aria is already here. Just waiting for a text from AT&T telling me to activate it.
[Hero CDMA Android Development] roundaway:
just read on google that at&t network is down and won't be back until further notice. heroc is the best
[Hero CDMA Android Development] cybertimber2007:
I wonder if one shouldn't wipe cache between kernels. Like davik or something.

Anyway, I gave it a shot. He's my observations

- In launcherpro, I noticed the animations were a heck of a lot smoother, even though my CPU speed is the same (691mhz, max mine can take)

- Camera, as expected, works only for a second and then stops.

- IPv6 working :) (confirmed in browser and with Network Info II)

- Battery charging - it seemed to be charging very rapidly... and also got rather warm. Dunno if there is a concern there?

- Headset: as expected, even though a headphone is plugged in, music was routed to the phone speaker. I don't have a true headset (speaker+mic), so I couldn't test that.

- GPS lock seemed good. Didn't use it long, but long enough to get a position lock on maps.

- Couldn't find the stock wireless tether, but I used the wireless tether app from the market and it seemed to work :)

Oddly, GPS status disappeared from my application's list. When I clicked the icon I had (launcherpro dock), it said "The requested activity could not be launched". As soon as I flashed deca's back, it was back in my apps list.

I must say, s0be, you did some amazing work, and it's nice :)
[Hero CDMA Android Development] s0be:
sl0ppy_s0be #47 - 691000 boot, 768000 max

devicemapper/crypt to make vold happy
[Hero CDMA Android Development] s0be:
Try #47, I didn't realize Vold required devicemapper/crypt support for some apps. This might fix them
[Hero CDMA Android Development] cybertimber2007:
Trying it now.

FYI, I did find out you should wipe davik-cache between kernel flashes. Found it in another thread. Trying that along with my update.
[Hero CDMA Android Development] il Duce:
s0be, you're the ****. Now that you have your aria, are you still gonna dev .35 for herc? hope so, because unless the CM team or aosp or jasonm picks up where you left off, we'll have what was *almost* the single most beneficial development since initial root of heroc, rather than, well, you get it, I love you...
[Hero CDMA Android Development] s0be:
I will get the kernel stable and feature complete, but am not going to do any performance tweaking. When I finish up, I'll leave an outline of what could be done to do a .37 port quickly.
[Hero CDMA Android Development] s0be:
BTW, does this mean that this fixed the missing apps problem for you?
[Hero CDMA Android Development] il Duce:
well, I did download it, haven't flashed yet (at work), I'll give it a go later and let you know.

EDIT: yes, just flashed and all my apps were there.
[Hero CDMA Android Development] halrulez:
So I have Ben using this now for a few hours. Most is going well. I am having allot of touch screen lag.
[Hero CDMA Android Development] pstevep:
This kernel has to warm up before it works really well and usually needs 1 or 2 reboots to hit the sweet spot.. Kind of like women..

<insert witty line about your rom here>
[Hero CDMA Android Development] cybertimber2007:
Yea I didn't have that issue. Touchscreen was responsive and fine after the first boot.
[Hero CDMA Android Development] il Duce:
the only missing "features" are camera and headset right, other than whatever bugfixes you're doing? Do you know if darchstar, decad3nce, jaybob413, or aosp intends to use this, like have you spoken with any of them about it? Also, you said .37 port "quickly" - like whoa.
[Hero CDMA Android Development] s0be:
Yep, just camera and headset detection at this point.

Well, as far as bugfixes go, I don't know of any that are needed, but if they come up, I'll do them.

On the use the .35 kernel front, no clue. I know decad3nce said he might be able to look at the camera after some tests (as in, college) this week.

The trick to the .37 port will be the same as how I added the amp driver[1] for heroc to .35. You just copy the driver from 2.6.35/drivers/..../foo.c to 2.6.37/arch/arm/mach-msm/board-heroc-foo.c, edit 2.6.37/arch/arm/mach-msm/Makefile and add the obj-$(CONFIG_MACH_HEROC) += board-heroc-foo.o and maybe have to change a few CONFIG symbols or api files. a good 85-90% of the port can be done this way (and pretty much ANY driver that the .37 version doesn't work for us)

[1] https://github.com/s0be/cm-kernel/commit/e146f853e6e7a72e274e847ef4bc337a88d3e411
[Hero CDMA Android Development] 24601:
Dude, if you want those naked cheerleaders knocking on your door, you gotta stop talking like this ;)
[Hero CDMA Android Development] s0be:
You can give me ****....

when you start to party like this: http://heroc.s0be.com/allhallowseve.jpg
[Hero CDMA Android Development] pstevep:
you drinking root beer???;)
[Hero CDMA Android Development] METHOD1911:
Lol

Hijacked aospCMod Darkhorse GB Hero
[Hero CDMA Android Development] runningslow:
Put your shirt back on, white boy!
[Hero CDMA Android Development] MallardDuck:
S0be, all I have to say is that I appreciate your contrabution and that you're a maven of your craft.

Edit:

Does anyone have any adivce on what to set the governor to if i want to avoid pandora skipping?
[Hero CDMA Android Development] s0be:
Not tested pandora, or really any interactive programs like that, but there is still a lot of debugging code enabled in these builds. This has a pretty decent performance hit (not actually measured/observed what this percentage is, but I'd say it costs you 2-3% of your performance all the time, with spikes into the 15-20% range) I'd suggest raising your min speed above the 19.2mhz default.
[Hero CDMA Android Development] 24601:
Well played, sir . . . well played, indeed.

Raise your minimum cpu settings to 352. If that doesn't do it, try 518.
[Hero CDMA Android Development] jlengvarsky:
also check to see if compach settings are working this is what always caused mine to pis me off.
[Hero CDMA Android Development] pstevep:
i would agree with the spikes into the 15-20%, i have been running this since this weekend.. and it has been running great but there are times just randomly it gets really sluggish.. so i cant imagine what it would be like running full speed..

thanks a ton for this s0be.. now if only i could learn this kernel stuff so i could try to carry on once you move on to the aria for good..
[Hero CDMA Android Development] s0be:
see if #56 has as bad of problems. It certainly warms up faster.
[Hero CDMA Android Development] s0be:
Just make sure you nandroid, this did not run well for me.
[Hero CDMA Android Development] il Duce:
I don't get it are you saying 56 is worse? lol

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] pstevep:
soo yeah.. ton faster.. if thats a sneak peek at what it will be like finished, then it will be awesome.. like you said though its not friendly.. i liken it to a crackhead, warmed up real quick acted cool, then got all jittery on me and then eventually crapped out.. i had to pull battery and flash #47 to get it stable again.. the camera also looked like it was closer to working, it came up quicker this time and i actually saw a couple images, but it would let me take a picture and then just stayed locked on the last image it saw.. and before it crapped out on me i noticed that it locked the phone awake at %100.. and the battery was real warm..

but thanks for it.. i will try playing with it more once i am not at work and can actually plug it in and see how it goes..
[Hero CDMA Android Development] pstevep:
its faster, much faster... but it hits a wall after a while.. so worse in its own right..
[Hero CDMA Android Development] il Duce:
I concur with the crackhead statement. If this thing can get stable in its warmup phase speed, oh my god. Tame the beast s0be!

sent from a series of tubes
[Hero CDMA Android Development] s0be:
Try 57... I haven't seen any crackhead behavior on it.
[Hero CDMA Android Development] il Duce:
I'll run it today.

sent from a series of tubes
[Hero CDMA Android Development] il Duce:
sent from a series of tubes
[Hero CDMA Android Development] pstevep:
Downloading now will flash in a minute and play with it for a while..

<insert witty line about your rom here>
[Hero CDMA Android Development] il Duce:
I lied. The 3/10 aospCM build got all weird on me, had to nand back. I'll try to run it this wknd.
[Hero CDMA Android Development] s0be:
Nope. Been too busy working on my CNC machine. Now that I'm happy with my ability to get it running, I'll probably kick H2W (2/3 Wire Headset detection) working tomorrow.
[Hero CDMA Android Development] pstevep:
so far so good on 57, lost all of the jitter from the other one, and i didnt have the wake lock with this one either (yet at least).. i actually feel like this kernel runs smoother with aospcmod than the stock one does.. the only thing that i have noticed more on this one is there seems to be a good bit of wake lag, that i didnt have before.. and a couple of the games arent as smooth, but i figure that will come together once the kernel becomes more stable..

i am however using this as my daily kernel with aospcmod.. thanks again:cool:
[Hero CDMA Android Development] s0be:
Battery life seems to be **** with this kernel. Oh well.
[Hero CDMA Android Development] pstevep:
i was going to add that as well, but i was afraid it was due to my travel today.. so it must not be then...
[Hero CDMA Android Development] zanywood:
Its a little jittery but plenty fast I've been running 768mhz and no lapses yet. Camera loads quick but stops. Still trying more things. Great job s0be!!!
[Hero CDMA Android Development] pstevep:
are you running 57 or 47?
[Hero CDMA Android Development] s0be:
sl0ppy_s0be #101 - 691000 boot, 768000 max

Now with working headset.
[Hero CDMA Android Development] pstevep:
101 is more stable so its safe to assume it has the de bugging stuff in it?

<insert witty line about your rom here>
[Hero CDMA Android Development] zanywood:
Wants it warms up it is super slick!! Just took about 20 minutes to warm up. So far no bugs. Only prob is warming up.
[Hero CDMA Android Development] pstevep:
I will stick with 57 then for a while.. I don't really need my headset jack to work right now, and I prefer the lack of warm up that 57 provides..thanks for the info.. And s0be you are the man..

<insert witty line about your rom here>
[Hero CDMA Android Development] Stonent:
Is AT&T making you give your Heroc back, or are you just saying devving will be harder with the phone deactivated?

As I drool over the possibilities of .35 in my Eris.
[Hero CDMA Android Development] zanywood:
Everybodys phone is different though"" how mine reacts might be different than urs.
[Hero CDMA Android Development] il Duce:
just grabbed 101, making nandroid, will run this tomorrow, thanks s0be!

well, it's tomorrow, and .35 is running VERY well so far. see below :)
[Hero CDMA Android Development] il Duce:
I call BS, 20 minute warmup my ass, this thing is smokin, ramped up as fast as any other kernel I've run. Are you REALLY running s0be's kernels, your comments seem contradictory. WIFI locked on and held for a while now. Other than the camera freezing everything seems pretty nice. s0be - this is WITHOUT performance tweaks? Holy crap this is gonna be a beast !!! One of the "drawbacks" I have noticed using .35 so far (most of the recent releases anyway) has been the TS seems to want to be touched longer/harder (TWSS) to achieve scroll - anybody else get that? Well, whatever, this is really nice, s0be (and helpers) are doing a great job with this!

DONATE!
[Hero CDMA Android Development] zanywood:
Im just reporting how my phone is reacting!! It runs awesome after about twenty minutes, I haven't exactly timed it but on my phone it acts funny until it warms up and in my case it takes a while to warm up. What do I benefit from lying? Just reporting how it reacts to my phone. Yours obviously reacts different.
[Hero CDMA Android Development] s0be:
None of the above? I just don't want to keep devving for a phone I don't use. Once my aria is activated, I hope to have this all done so I can just move on to the Aria kernel.

He's not lying. My phone does this some of the time.
[Hero CDMA Android Development] zanywood:
As far as wifi after I rebooted it is holding much better. Ive had network problems in my area for awhile.
[Hero CDMA Android Development] zanywood:
Thank you s0be. I got nothing to benefit from lying!
[Hero CDMA Android Development] oostah:
so are you saying when i flash the kernel i should let it sit for 20min before i do any thing. the other kernel was like that for me if i tried to do any thing it would hang then get fc. i rebooted a couple times and is settled in.
[Hero CDMA Android Development] zanywood:
Well the first time I flashed it just was acting funny for what seemed like a long time. Set cpu and autokiller took a long to to get superuser permission. Than they started warming. Up but still had a few lags and fc's so I rebooted and after all superuser permission's were granted and I did a few texts, now its running like a champ!!
[Hero CDMA Android Development] zanywood:
But im probably lying so I will get a free evo!!
[Hero CDMA Android Development] oostah:
cool thanks for the reply thats the way they went for me before. i like the heads up before hand. i no its not me then.:D
[Hero CDMA Android Development] zanywood:
After two reboots it seems to load considerable better. Still loads a little slow but not near twenty minutes like first flash. Actually running real smooth. Got a lot of tests to do tomorrow though. I need to get this dust out from behind screen. Its driving me crazy. Good night my fellow androidians! !!!!!!!!!!
[Hero CDMA Android Development] s0be:
If everyone reboots a few times, everyone will run into this eventually. There is 'something' that is racey, which can, on occasion, deadlock and have to timeout and restart. If this happens a few times, it can take the phone a long time to settle in.

Putting together another 'crazy' release right now.
[Hero CDMA Android Development] s0be:
#106 is up, it's probably unstable, eats babies, and probably doesn't recycle.
[Hero CDMA Android Development] zanywood:
Lmfao!! Ill pop it in the oven right away. Thank you s0be!!!!
[Hero CDMA Android Development] zanywood:
Has anyone seen little johnny and sally Mae? They were just here a minute ago???
[Hero CDMA Android Development] zanywood:
So far so good. It warmed up very fast. Par for the course! ! Me personally I don't have any camera yet so if anyone else has one great but. I don't and im not making that up"!"" Well its 5:00 am. Do you no were ur children r?
[Hero CDMA Android Development] pstevep:
Yeah with the more stable kernel I notice that the ts needs to be touched longer its one of the reasons I prefer the less stable one.. I'm getting ready to flash 106 I will let you know if it really is totally crazy, I found 57 to be pretty stable so hopefully 106 will be as well with the improvements..

<insert witty line about your rom here>
[Hero CDMA Android Development] il Duce:
Zany calm down. Thanks for the junkie kernel, gonna try it soon.

sent from a series of tubes
[Hero CDMA Android Development] pstevep:
I'm getting some weirdness here on 106.. Its like its getting the wake lock but in spare parts its telling me that my "running" is at 502% which is really weird. My clock seems to be picking up time somewhere which I think is part if the cause.. I have rebooted 3 times and it has happened all 3 times.. I'm going to ride it out for a little while and see what happens..

<insert witty line about your rom here>
[Hero CDMA Android Development] il Duce:
none of my percentages were over 100. I never really look in there so I couldn't tell you if the values were abnormal. I will say restoring apps with TB took way way longer than the current kernel. Also, I dunno if it's just my phone, but the "crazy" kernel didn't agree with it much.
[Hero CDMA Android Development] s0be:
Just uploaded a steamy pile #107, for you guys who are running 106. It's untested so far, so I did not update the original post, but I bet you can figure out the link. I normally flash and run any new kernel I upload for a half hour or so, but don't have time to test this one (well, I'll be testing it, but AFK).

Good luck!
[Hero CDMA Android Development] pstevep:
Running 107 now.. So far so good, no hiccups yet..

<insert witty line about your rom here>
[Hero CDMA Android Development] pstevep:
I've never really used spare parts except for seeing what is eating my battery... So far for me the less stable kernel works better for me..

<insert witty line about your rom here>
[Hero CDMA Android Development] riemervdzee:
I've just commited some new code from code-aurora forums, which decreases boot-times quite a lot. I also think this addresses the slow IO operations (in your case TB). Hopefully S0be will implement it soon at the CMDA one, could you compare the TB test a little for me?
[Hero CDMA Android Development] il Duce:
sure, it wasnt dreadfully slow, just noticeably slower than .29. Thanks for all the work you've done on the gsm version, without that we wouldn't be where we are now :)

sent from a series of tubes
[Hero CDMA Android Development] zanywood:
Sorry I got excited. Drunk a little to much.
[Hero CDMA Android Development] cjdalessio:
Some observations running 101 on the 3/8 aosp/CM7 build:

* first boot hard-locked at initial HTC logo, pulled battery after 30 minutes. Subsequently booted up fine.

* 90-seconds after the lock screen came up, I unlocked and went to try music - started up *very* choppy, volume control horribly lagged. Headphone detect works. :) Cleaned up after a minute

* 5 minutes in, CPU load still 90-95% and the occasional skip in music.

* 10 minutes in not all icons on my home-screen had loaded (GooMap and GooVoice - plain app shortcuts not widgets) - both are installed to SD so I went looking, and found NO apps installed to SD were showing up. I did see spew in logcat about Kindle so it's just dog slow.

* 15 minutes in, seems stuff is finally finishing loading.

I see riemervdzee has posted about a commit for I/O, and I think that I/O is the problem here on startup sucking.

Going to keep watching.
[Hero CDMA Android Development] s0be:
Pulled, pushed, and available in #109. Run testing now.
[Hero CDMA Android Development] cjdalessio:
Got 109, about to try. :)

Camera (on 101) seems to drop the hardware acquisition (after actually picking up an image, but very under-exposed) and is subsequently unable to pick it back up due to being "in use"

WTF is bouncycastle.jar?! weird stuff. :) (crypto I see) 109 booting clean so far, first time... not to lock screen yet.

Fully booted, behavior seems about the same after boot as 101 as far as how long it takes apps installed to SD to show up.
[Hero CDMA Android Development] s0be:
Notice post 1 still lists camera as broken. I'll call it an RC, renumber starting at 1, and give it a classy name once it's feature complete. I haven't looked at it at all, although decad3nce might almost have it working.