yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] dbayub:
I was thinking that using the old YAFFS code would eliminate this problem. The next thing I was going to try was a recovery that formatted using EXT4. Isn't that what Google switched to for GB?
[Hero CDMA Android Development] s0be:
This issue there is, the old YAFFS code needs some updates to work 100% with the new kernel. This is on my 'todo' list so we can use 2.6.35 with the existing roms and recoveries.

My idea is to:

cp -a /path/to/2.6.29/fs/yaffs2 /path/to/2.6.35/fs/yaffs2o

update yaffs2_old to use a different set of Kconfig symbols (probably as easy as a sed script that replaces all references to YAFFS2(.*)\b with YAFFS2O$1)

update yaffs2_old to whatever differences exist in the VFS layer.

That should allow us to have both exist in our tree at the same time.
[Hero CDMA Android Development] s0be:
dmesg of latest commit:

http://android.pastebin.com/UWXeDVq0

It boots all the way up now.
[Hero CDMA Android Development] :
Would this be 'safe' to clone from your github and begin testing for errors to get logcats and such? Assuming it boots into a ROM. I guess I am asking 'what next'?

edit: Oh yea, congrats btw and thanks again for all the hours of work on this.
[Hero CDMA Android Development] s0be:
Wait til I fix touchscreen at least.
[Hero CDMA Android Development] :
That might be worth waiting for :cool:
[Hero CDMA Android Development] s0be:
Ok, to get the rest of the stuff working we need the i2c-msm driver to work. I've committed my attempt to the i2c-fixups branch, but it does not work yet (and may corrupt flash, etc).
[Hero CDMA Android Development] ohbuckeyeman:
Just wanted to say thanks to everyone putting so much time into this. I'm sure this will allow our Heros to be viable with GB and beyond once all of you devs put the finishing touches on it. Very impressive work...Just goes to show you what a community of dedicated users are capable of. HTC and Sprint should pay you guys once you have it done!
[Hero CDMA Android Development] davec1234:
Exactly right!

But Sprint would pay then NOT to publish their work. Gotta sell those upgrades.
[Hero CDMA Android Development] ohbuckeyeman:
It's amazing how much work gets done when devs have free time. Spring break is only half way over! Decafuct .35 edition? Lol. Thanks to s0be, Decad3nce, Jaybob and everybody else who made this happen!
[Hero CDMA Android Development] oostah:
This a great day in hero land downloading now to take it for a run THANKS
[Hero CDMA Android Development] pstevep:
What the eff!? I am way from phone for a little bit and this is what happens... Awesome work guys and thank you.. Just downloaded and rebooting to flash..

<insert witty line about your rom here>
[Hero CDMA Android Development] stayclean:
Amazing, that's all I have to say. Great job guys, flashed it 30 minutes ago and wow, this is amazingly fast when it's "warmed up", so to speak.
[Hero CDMA Android Development] zanywood:
Awesome job guys!! Its great so far warms up pretty fast! Way to go! Donating soon as I can.
[Hero CDMA Android Development] s0be:
2.6.35-AP-1 now official release candidate version.
[Hero CDMA Android Development] il Duce:
Not decafuct. Give your respect to the whole team. s0be put proper credits in the op.

sent from a series of tubes.
[Hero CDMA Android Development] il Duce:
Deca's dl booted at 768, just wanna make sure before I flash the new one in the op boots at 691???

sent from a series of tubes.
[Hero CDMA Android Development] s0be:
This was way more than a 1 or 2 man show. Decad3nce got the board files from .29 to compile on .32, which I pulled forward into the .35. Without this jumping off point, I would not have gone anywhere on the project. This was a non trivial task. Next up, there are 3-4 git trees above mine, from which I pulled maybe 60-70% of the work. There was a small amount of actual outside of heroc board file source modification I had to make, but most of it was just tweaks to the heroc board files. It really wasn't a whole lotta work for me, maybe 100 hours total or so. Don't chastise ANYONE about saying who should get credit for this. It was a team effort.

Mine will always boot at 691 default.
[Hero CDMA Android Development] il Duce:
my bad, will edit, thanks for the 691

sent from a series of tubes.
[Hero CDMA Android Development] s0be:
Chastisation removed
[Hero CDMA Android Development] ohbuckeyeman:
To anyone I offended (duce!) In my previous post, sorry. I truly appreciate the amount of cooperation and the team effort that went in to this. It's amazing what can be done by some dedicated programmers. These guys do this because they enjoy it. Probably why the quality is so high. Again, thanks to everyone who had a hand in this!
[Hero CDMA Android Development] harpstar:
Always a breath of fresh air to see the lack of ego in these forums.

Well done all.

Drop the zero, get with a Hero
[Hero CDMA Android Development] y3mita:
RC very good team work you guys!! I wiped dalvik and flashed this zip... everything so far works with the exception of the camera. It freezes when you shoot for a picture.

using AOSPCM 03/23/11 ROM.
[Hero CDMA Android Development] Decad3nce:
that shouldn't be happening.

What ROM?

Need a logcat/dmesg

While recreating the problem, run:

adb logcat > logcat.txt

then reboot and run

adb shell cat /proc/last_kmsg > last_kmsg.txt

thanks
[Hero CDMA Android Development] y3mita:
No need to...

2 reboots fixed whatever the problem was....

Pic taken: http://dl.dropbox.com/u/23809760/IMG_20110324_004849.jpg
[Hero CDMA Android Development] s0be:
Noone claims this kernel is perfect yet, hence the RC status. If you have a problem, please DO follow these steps and get us the bug info. It will really help us get this more stable.
[Hero CDMA Android Development] y3mita:
I guess I was too fast on giving out comments on the kernel. I was ready to logcat but I remembered most troubles like in any computer are solved by rebooting... did that 2 times just in case *maybe only 1 time was needed* and tried camera once again and it worked!

Then tested a few more shots and everything is flawless!

s0be great awesome incredible work!

@Deca I apologize for trigger the alarm that fast! from what I have read the camera issues this rom had have been solved mostly because of you if not just by YOU.
[Hero CDMA Android Development] Decad3nce:
next -AP release:

Integrate smartass governor
[Hero CDMA Android Development] sheagk:
I also had that issue with the camera freezing when taking a picture. I'm running CM7 Nightly #30. On first boot of the kernel (but after letting it sit and using it for a few things for a little while), camera froze when I tried to take a picture. Interestingly, the auto-rotate still worked: I could see the picture in the gallery and the settings rotating. I didn't try hitting Home; don't ask why.

Here's the logcat from that: http://pastebin.com/QsS9W0zj

I then did an adb reboot, and on the first attempt, the phone wouldn't boot at all--not even far enough to get a logcat (just 'waiting for device' with the phone sitting on my splash screen). The phone booted after a battery pull, and here's the (mislabeled) last_kmsg: http://pastebin.com/fSntVajZ

Also ran into the same problem after one reboot. I hit Home, Camera exited, I did adb reboot, and again my phone is stuck on the splash screen. To test that it was the camera causing that, I did another battery pull, rebooted successfully, and then did an adb reboot without ever opening camera, and had no problems. After that reboot, my camera still freezes up, though it once unfroze after awhile (that event should be somewhere in this logcat; I think it was the first time I tried taking a picture: http://pastebin.com/rRnECaCt).

Anyway, hope that helps. Seems my camera still isn't happy.

Edit: Also, it seems that if I let my phone go to sleep, the camera will be unfrozen when it wakes up. Still no luck taking a picture though.
[Hero CDMA Android Development] Decad3nce:
QDSP flush fails

/mm-camera 7x-vfe( 111): vfe_process_QDSP_VFETASK_MSG_VFE_RESET_ACK flush pending cmd node->cmd:0
I/mm-camera 7x-vfe( 111): vfe_process_QDSP_VFETASK_MSG_VFE_RESET_ACK flush pending cmd node->cmd:0
I/mm-camera 7x-vfe( 111): vfe_process_QDSP_VFETASK_MSG_VFE_RESET_ACK flush pending cmd node->cmd:0
I/mm-camera 7x-vfe( 111): vfe_process_QDSP_VFETASK_MSG_VFE_RESET_ACK flush pending cmd node->cmd:0
I/mm-camera 7x-vfe( 111): vfe_process_QDSP_VFETASK_MSG_VFE_RESET_ACK flush pending cmd node->cmd:0

I think this may stem from the addition of auto white balance, otherwise vfe7x/qdsp might need to be repatched.

E/mm-camera 7x-vfe( 920): output2YBusOverflow = 1
E/QualcommCameraHardware( 920): native_get_picture: MSM_CAM_IOCTL_GET_PICTURE fd 13 error Connection timed out
E/QualcommCameraHardware( 920): getPicture failed!

That, and the kernel still isn't 'stable' as a whole.
[Hero CDMA Android Development] MallardDuck:
Thanks a lot for all of everyone's collective work. :D
[Hero CDMA Android Development] pstevep:
one thing for anyone who hasnt tried this before to keep in mind.. this like Decad3nce and s0be have both said isnt totally stable.. it does have a slight warm up period.. you cant just boot up and expect to be smooth and ready to go.. it may be a bit jumpy at first, and if you run into anything crazy, usually a reboot will take care of it.. if you are coming from another kernel, you should probably wipe dalvik cache before flashing, it will give you a longer boot up time, but will get rid of most dingleberries..

thanks again to everyone who has worked on this, s0be, Decad3nce, jaybob and everyone else who made this possible.. soon this kernel will rull the .29 kernel..
[Hero CDMA Android Development] dburg84:
camera freezing here. not sure if its of use...already seen one logcat about it. here is mine in case it is. looks like same error: http://pastebin.com/dg7Htu3Y

fyi camcorder works fine.
[Hero CDMA Android Development] halrulez:
Ya my cam does the same when i take a pic too. One thing this kern does that pisses me off is the touch screen. Takes a second to notice my finger is on it.

Hero for now EVO3D day it's out! Thanks devs for all the hard work on my hero.
[Hero CDMA Android Development] s0be:
What scaling governor are you using? I've had great TS performance with the interactive one. Will try to merge smartass tonight, along with a RTC/Alarm fix.
[Hero CDMA Android Development] The Fer-Shiz-Nizzle:
I don't have a log but I thought I would share my experience anyway. I am running a very old build of aospCMod from FEB 1 and using DT a2sd with dalvik-cache moved to sd-ext. I have had trouble upgrading to a more current build, and just not had the time to sit and troubleshoot, so I nandroid restore as this build has run flawless for me after some GPS fixes that were necessary at the time (swapping libgps).

I flashed the .35 kernel that Deca posted (not from the op) using Darch's GodSpeed recovery and the phone rebooted without a hitch. I did not do any camera testing.

For about a week, I've been using the new DarkTremor A2SDGUI.apk that was on the front page of XDA yesterday. One of its options is to rebuild dalvik-cache upon reboot, and I have successfully done this multiple times with the .29 kernel. But when I tried this with the .35 kernel, it hung on the splash screen. After 10 minutes I pulled the battery and booted to recovery, wiped dalvik-cache, rebooted, and still hung at the splash. I then used fastboot to flash Clockwork 3.0.0.5 recovery and formatted cache, boot, and wiped dalvik-cache, and then reflashed the .35 kernel. Upon reboot, it still hung at the splash screen.

It was late, and I was out of options, so I reflashed GodSpeed and did a fastboot erase system -w, and restored the nandroid I made prior to these events.
[Hero CDMA Android Development] s0be:
I will probably be dropping AP #1 v2 tonight. I've discovered a few 'oopsies' in my zip files (the module folder is misnamed, so tun/ramzswap don't work).

Also, ALL pre-release/test releases will be located at: http://heroc.s0be.com/HERC-2.6.35.zip, with no indications of when it changes, what has changed, or if the changes work, or can even be flashed. Now that we're into the RC cycle, I prefer to have a fixed baseline for what people are working from, so bug reports on testing versions aren't interesting. If you can't reproduce the problem with the latest RC, wait to report it until the next RC comes out and then reproduce it on that.
[Hero CDMA Android Development] pstevep:
is the one in the OP the same as the one that Deca linked??
[Hero CDMA Android Development] s0be:
Not sure what his .config was like for that, so I can't say.
[Hero CDMA Android Development] il Duce:
No it is not. At least s0be's OP version boots at 691, the deca link last night booted at 768.

sent from a series of tubes.
[Hero CDMA Android Development] pstevep:
ok.. thanks.. i am running the one Deca posted, but i will just wait til s0be posts the new one later, it cant be that much different i wouldnt think, and i dont have problems booting to 768, just cant stay there..
[Hero CDMA Android Development] Ree$e:
trying to root my sprint hero can you point me in the right direction every thread that has steps dont work...
[Hero CDMA Android Development] s0be:
It also appears that something Decad3nce has in his .config that I don't is what makes the camera work for his kernel. Will poke him about this tonight.
[Hero CDMA Android Development] pstevep:
strange that you posted the question in this thread..

try this thread.. plenty of info.. if not just search..

http://xdaforums.com/showthread.php?t=674833
[Hero CDMA Android Development] s0be:
Testing No-op+CFS+Smartass right now
[Hero CDMA Android Development] pstevep:
awesome.. i enjoy the smartass govenor..
[Hero CDMA Android Development] s0be:
https://github.com/s0be/cm-kernel/commit/a9bedb6bbcd578582b2874b9ed642d33c68f3faa
[Hero CDMA Android Development] Decad3nce:
heh, i pushed mine about 10 seconds before yours, will revert.
[Hero CDMA Android Development] s0be:
Which way did you resolve the msm_cpufreq_ondemand_max issue. I added it to Kconfig, to revert later, to keep the changes in cpufreq_smartass to a minimum on the initial commit (for easier upstream change merges)
[Hero CDMA Android Development] Decad3nce:
Didn't even look at it honestly, just threw in smartass and added to Kconfig like you did.
[Hero CDMA Android Development] pstevep:
Earlier today my mind wouldn't haven been ready to read through that, but I had to break out my visual basic today and my programing is starting to come back to me.. Thanks..

I feel like a douche for misspelling governor..

<insert witty line about your rom here>
[Hero CDMA Android Development] ch1naski:
You guys rock.

π

sent from GB hero.
[Hero CDMA Android Development] fowenati:
wholy**** camera works now?! I was waiting to try this for the longest time, WILL TEST OUT NOW ohmygoodnes sankkkyuuuu!
[Hero CDMA Android Development] halrulez:
Sorry about getting back so late. I was using performance and on demand. I know it sound really strange but on the 29 kernel with cm7 I always get way better battery life with performance. But still the best has been with smartass.

Hero for now EVO3D day it's out! Thanks devs for all the hard work on my hero.
[Hero CDMA Android Development] s0be:
Having some issues with smartass/interactive and the camera.
[Hero CDMA Android Development] rochford77:
whoot

Front page!!!!!!!
[Hero CDMA Android Development] riemervdzee:
So you know, I also blame timing issues to be the pain at the GSM version.

However with the latest changes of your side decan, and switching to on-demand, it performs quite well actually.

Always had the feel it is quite nity-picky about the cpufreq. Most stable is 633mhz here.
[Hero CDMA Android Development] Decad3nce:
If you want to try and revert the BFS patch and see how it handles w/ camera, it would be of real help.

We're not able to boot .35 without the BFS patch for some reason.
[Hero CDMA Android Development] patmanz28:
Tethering didn't work just says usb not connected. Although everything else seems to work good.keep up the good work
[Hero CDMA Android Development] andythegreenguy:
All of you guys put together is PURE awesomeness! Thanks!
[Hero CDMA Android Development] s0be:
Yeah, I actually noticed that this was going to be a problem last night while I was trying to figure out the BFS/Smartass issues. It's just a missed =y in the .config. Unfortunately, I won't be dropping anything til sunday night lately (there's a chance tomorrow, definitely not today).
[Hero CDMA Android Development] il Duce:
Hell yeah, as it should be! Kernel ports are among the most complicated and frustrating things possible in the android world, these guys are amazing! Everyone should throw a couple dollars at the cdma team, hopefully to keep them tweaking this .35 for primetime :) or MAYBE even to get the .37 kernel (which I think s0be said would be "easy") :D
[Hero CDMA Android Development] s0be:
.35 -> .37 represent many fewer core changes to the kernel than .29 -> .35 did. There was a major VFS change around .31, they began the BKL push down in .35 (I suspect this is what's currently screwing with our timings, btw), this was the time of the great CFS revolution, etc etc..36, .37, .38 have all been, for the most part, tame releases compared to what happened in .29-.35
[Hero CDMA Android Development] Chevelle1768:
Awesome work guys!!
[Hero CDMA Android Development] riemervdzee:
Not to mention we got some more experience with our phones I guess ;)

You want to make this jump though in the future?

Will test it tomorrow
[Hero CDMA Android Development] s0be:
Yeah, good point. Actually understanding the interaction of the different parts does help.

I've been sitting here contemplating whether figuring out the issues with .35 is worth it, as some of them are likely to crop up once we're on .37. On the other hand, I'm ~2 weeks from going GSM, and I'm not sure that's a realistic timetable to pull it off in. Perhaps enough coffee could help.
[Hero CDMA Android Development] y3mita:
GSM? May I ask what model are you getting?
[Hero CDMA Android Development] il Duce:
Well hopefully some other members will buy you a cup or ten *cough* DONATE! *cough* ..... Also, hopefully the current github contributors will continue the contributions. And hopefully what you leave behind will be picked up on by the 2-3 remaining kernel devs, how many are there? We shall see. No matter what the work done here so far is nothing short of miraculous, THANK YOU!
[Hero CDMA Android Development] s0be:
I'm 150lbs of man meat. Verizon bought Alltel (My Carrier) and sold me to AT&T. I have a free Aria sitting at home. It's been a glorified paper weight for a few weeks now. Not sure if I'm going to stick with it, or just switch to an impress.
[Hero CDMA Android Development] runningslow:
That happened to my parents, too. I know at least my mom has an android phone, but I don't know what model, I think it was a Moto. Bravo, maybe?

Not that any of that matters to a HeroC developer thread.
[Hero CDMA Android Development] riemervdzee:
So you know, it performs worser than with BFS. With BFS I'm able to shoot a few pictures, while with CFS only one.
[Hero CDMA Android Development] Coolaaron88:
So I tried flashing the HERC-2.6.35-sl0ppy_s0be-114 on froyo 0.9.2 aosp and I flashed it and now Im just at the HTC screen on my Hero. did I do something wrong
[Hero CDMA Android Development] s0be:
Not sure? Can you catch an adb logcat, see if it shows anything?

It's safe to re-flash the 0.9.2 rom right over this, it'll just go back to exactly where you were (no need for any wiping). Or someone else's kernel too.
[Hero CDMA Android Development] s0be:
Wait, why did you try SS114? Use AP1 in the first post.
[Hero CDMA Android Development] Coolaaron88:
Ok my bad. Will do
[Hero CDMA Android Development] s0be:
Not likely to make a difference. .35 has only received limited testing on <2.3 roms so far. I know 1 person who had tested on a 2.2 rom a while ago. Either way, adb logcat will be very interesting. Also, when you boot into recovery, do: adb shell cat /proc/last_kmsg > foo.txt and post the contents of foo.txt to android.pastebin.com and link us please.
[Hero CDMA Android Development] y3mita:
EVO3D seems to get my attention!
[Hero CDMA Android Development] pstevep:
hate seeing this thread not up towards the top.. so bump.. if you havent tried this yet.. do it;)
[Hero CDMA Android Development] S3NATOR:
Fixing to try this! Thanks!
[Hero CDMA Android Development] oostah:
I have tried it and had alot of lag and hick ups. I flashed the one dac posted. On aosp gb 3/23 going to give the one on the op a shot on the new 3/26 GB. Dose any one no if they are the same?
[Hero CDMA Android Development] pstevep:
they arent the same.. there are a few subtle differences.. im running Decad3nce posted still and i havent had too much trouble with it.. for some reason i know some people are seeing better output with using the ondemand governor, i know the camera works better with ondemand.. and the lag goes away after a little bit, its usually in the warming stages..
[Hero CDMA Android Development] oostah:
I ran it for 24hrs. That way I can see how it responds in Daly use.
[Hero CDMA Android Development] pstevep:
that was plenty of time..

the only time i ever really run into anything weird as far as lag or TS issues is when my battery drops below 20%.. if i get a phone call under 20% while doing anything else, my phone goes crazy...
[Hero CDMA Android Development] oostah:
Downloading the one from the op now. It has been said to give it 20min to warm up is this still the same.
[Hero CDMA Android Development] pstevep:
its never taken me 20 minutes to warm up.. at most 5 minutes for me.. i have told people to wait longer because some people dont wait until the phone has completed loaded to try and do things and it causes FCs or wait dialogs..
[Hero CDMA Android Development] aoaleman:
This kernel kicks so much ass. Thanks for all your hard work s0be and others who contributed! :D
[Hero CDMA Android Development] oostah:
I understand that I just got it all setup 3/26 AOSP GB. had trouble with apps downloading from market. I did a fresh install GB rom gapps kernel. used titanium to install most apps. It being a fresh install it was loading apps before the kernel ever got settled in. Everything is going good. I did run fix permissions. Seams to help.
[Hero CDMA Android Development] silberj:
I am using this kernel on AOSPCmod 3/26, and it is running fantastic. I flashed all other stuff (gapps, data2ext, theme (cyan skulls FTW)), etc, and flashed the kernel last. I let it sit awhile before trying to do anything, since I had noticed it took a bit, but after around 10 minutes, all was good to go.
[Hero CDMA Android Development] oostah:
I have the same setup except for the skull. I will try and flash the kernel last with the next GB update. see if that helps. Flashing the kernel after gapps then flashing other things that need rebooting maybe what is making the lag freaze and reboot that I'm getting.
[Hero CDMA Android Development] silberj:
My normal process to flash is

1. Rom, reboot

2. data2ext, reboot

3. run commands to enable data2ext, reboot recovery

4. gapps, reboot,

If everything is ok, then I flash my theme, reboot, a custom font (comfortaa!) reboot, and then the AP#1 kernel.
[Hero CDMA Android Development] pstevep:
yeah i always flash my kernel last.. no matter what i am installing.. it just seems to work better for me.. but again i dont use firerats or anything, im not even using a theme right now.. but when i am kernel always goes last.. and i always find that wiping dalvik before you flash the kernel helps a lot, especially if you are booting up with the stock kernel then booting back to recovery to flash the new kernel...

btw... i am using Decad3nce's version of the kernel right now, and with the latest aospcmod, my battery is amazing, and i have had no glitches with camera or anything.. but i did switch to ondemand governor.. i can not wait til this thing is totally stable.. its beautiful..
[Hero CDMA Android Development] silberj:
I should have noted that I am using the smartass govenor, with autokiller set at optimum.
[Hero CDMA Android Development] pstevep:
on s0be's .35 kernel???????