yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] chrisexv6:
Going to the OTB .13 kernel fixed my in call audio. Good enough for now, Im sure JT will figure out whats up with the stock kernel.
[Fascinate Android Development] chrisexv6:
Talking to myself here a little, but figured Id throw it out there:

has anyone tried flashing the ROM, flashing OTB kernel to fix the audio, then flash *just JTs kernel* from the ROM itself? Im wondering if the "fix" would somehow remain at that point.

Im not sure whats different between OTB and JTs kernel, aside from voltage control and over/underclocking. Anyone know?
[Fascinate Android Development] FDro:
Anyone else notice that screen responsiveness has suffered? I'm on 7/04
[Fascinate Android Development] ssewk2x:
Great! I will attempt this .. Eventually. Sadly, my company is sending me on travel for 2 weeks and I'm not sure I will have access to odin in the event something goes haywire.

OT, the jerks are also making me miss my 1 year wedding anniversary...anyone know of a place hiring embedded software engineers in MI?
[Fascinate Android Development] dhouston10:
I'm currently on EF 3.6. I am considering flashing this rom (knowing all the work it would take to go back to ef). But appearance is a major factor for me in roms. Any screenshots?
[Fascinate Android Development] ssewk2x:
Rochester, about an hour north of Detroit.
[Fascinate Android Development] nunyazz:
http://www.cyanogenmod.com/
[Fascinate Android Development] D_Steve595:
I don't understand how someone thinks they can possibly know how a rom runs from a screenshot.
[Fascinate Android Development] solido888:
He just said appearance is a major factor for him, what is the big deal? He did not say, by looking at screenshots, he will be able to determine how well the rom runs.
[Fascinate Android Development] Grimis:
Swiping to clear message notifications..... how? ;)

Fascinate CM7 or MIUI depending on the mood!
[Fascinate Android Development] bobthesalesclerk:
Been running build 8 w/ blue steel theme(sick!) For a day now and everything is awesome. Only problem is I cant run any live wallpaper with it or I get tonnnns of lag. As soon as I switch to a reg wallpaper the lag is gone but tw ran better with a live wallpaper. This build is solid and my in call is much better.

Alpha Tappa Lambda
[Fascinate Android Development] garywojdan81:
Hi-ho neighbor. Know it well, my 2 oldest were born at Crittendon. We're originally from Warren, now up in Grayling.
[Fascinate Android Development] chrisexv6:
Did you come from a previous version? I had zero audio after going from CommRom 2.0 to build 7 then to build 8. Added OTB kernel and got in call audio back but its really quiet apparently
[Fascinate Android Development] poetics:
I have this problem too since going to build 8. does OTB fix it?
[Fascinate Android Development] dhouston10:
Well that someone has a name. I wasn't asking how the rom runs based on the screenshot. I am curious at how it looks.
[Fascinate Android Development] chrisexv6:
Kinda.....I got audio back with it but the volume is very low even with it maxed out
[Fascinate Android Development] CxanDroid:
It looks pretty stock, however, it has a theme engine, so it can look lots of different ways with a few clicks.

Sent from my gimped Fascinate
[Fascinate Android Development] poetics:
Thanks. I just switched to OTB now, but haven't had a call yet to test it on. Everything else runs super smooth.
[Fascinate Android Development] D_Steve595:
But you can theme it any possible way you want..
[Fascinate Android Development] CHANGiism:
Alright guys, I forked libaudio from build 7 and pushed it to build 8 to make the mic work in apps. This will get rid of the issue with apps not getting your voice input. I'm not sure if this gets rid of the fix that JT put in to address the call volume adjustment. Someone can test it out for me. You can flash Build 7 but that will get rid of the recent CM mainline codes. It's up to you guys. Only thing that changed from JT's build 8 is build 7's audio fix.

I'm not taking any credit for this. According to JT's github, he already got the fix pushed and will upload it here soon. I don't care if you guys go ahead and push the libaudio yourself, download this, or wait for JT's build 9. I'm going to take the link off when Build 9 comes along.

This WILL NOT fix your voice end not getting heard on the other end. That is in the kernel end and I want to give Nemesis a credit. Flash Nemesis's kernel to fix that issue.

LINK REMOVED.
[Fascinate Android Development] nunyazz:
JT has fixed the audio issues, should be updating shortly

http://twitter.com/#!/_jt1134_/status/89797856210329600
[Fascinate Android Development] FDro:
Eagerly awaiting
[Fascinate Android Development] nunyazz:
Thanks JT, it's like magic!:D
[Fascinate Android Development] CHANGiism:
That was quick :)
[Fascinate Android Development] Mystique:
Wife can hear me on the phone..

#winning

Thanks jt

Sent from my CM7 with EC09; Thanks to jt1134.
[Fascinate Android Development] mmtoman:
I'm thinking about buying a fascinate. How does cm7 on this compare to cm7 on an og incredible.

Anyone here have that before?

Thanks
[Fascinate Android Development] scottzirra:
Question and possible feature request. Can the ability to set custom boot animations be added to the kernel? From my google fu I found: How to change your boot animation.

Which suggests the kernel must support it.

I have replaced the existing bootanimation.zip in the appropriate place: /system/media but rather than updating my boot animation it went to a basic blue android text boot animation. Weird that I lost the boot animation from cm7, which tells me I replaced the right file, but it did not play the zip i put in.

If I am doing this wrong for this version of CM7, can anyone shed some light?
[Fascinate Android Development] garywojdan81:
Just flashed build9 directly over 8 with a cache/dalvik wipe & tested in-call audio adjust (it's louder), mic functions on calls, voice search/dial & soundhound. And, as always, it seems smooth & snappy. Thanks JT!
[Fascinate Android Development] nunyazz:
Place your zip file in /data/local

instead.
[Fascinate Android Development] spyd3r05:
Any chance on a way to oust the update to miui that fixed audio here
[Fascinate Android Development] ssewk2x:
So, can we flash this directly, or should we still flash the july 4 build to start. This is if, like myself, we're coming from comm rom 2.x.

Thanks!
[Fascinate Android Development] CHANGiism:
I haven't tried it yet so I'm not sure, but since you are coming from TW rom, you need to flash JT's fixed CWM either way. After that, wipe data and cache, and try flashing Build 9. If it works, profit. If it doesn't work and gives you assert error, flash Build 7 and just flash Build 9 on top of it. Let us know how it goes.
[Fascinate Android Development] sarkozy:
Odd, that sends me into a bootloop. For the last two builds I've simply flashed the new ROM over the old, without wiping anything. Not sure why wiping the caches wrecked the install for me.
[Fascinate Android Development] Macguyver:
I was on EF for over a month after getting tired of com roms quirks. EF was ok but I've been on build 7 of CM for 4 days now and its the best rom over ever tried. More than doubled my battery life and runs flawlessly with the stock kernel for me. You wont regret it.
[Fascinate Android Development] chrisexv6:
I flashed this right over build 8, after wiping cache and dalvik. Worked great. I was on the OTB kernel before....in call audio worked then and it works now. Seems a little louder on build 9 than on build 8 w/OTB, but I think it could stand to be louder still.

Other than that (and the proximity sensor not lighting up the screen after I move the phone away from my face), this one is solid for me.
[Fascinate Android Development] chrisexv6:
What did Tom ever do to you!!!??? :)

Autocorrect FTL.
[Fascinate Android Development] CHANGiism:
I like EC09 radio on CM7 because I feel it's more stable, better reception, and better speed over EB01 and ED01/04 but the GPS really does not want to lock on. I feel like EB01 gives way better GPS lock, but I can be wrong. Can anyone confirm my observings?
[Fascinate Android Development] Macguyver:
He he he, I just saw that and fixed it lol
[Fascinate Android Development] Macguyver:
I'm running EC09 and mine locks in about 3-4 seconds. Not sure about EB01 but I know ED01/04 didn't lock worth a crap half the time on EF or CR. So take from that what you will.
[Fascinate Android Development] scottzirra:
GPS Aids is in the Market and works fantastic for our phones. It takes some playing with the settings and enabling everything to override the initial setup, but it definitely makes a massive difference.
[Fascinate Android Development] jjcas15:
Anyone mind posting a screen shot... Curious to see what it looks like? Might flash this later... Thanks.
[Fascinate Android Development] joshriccio:
anyone flash build 9 over build 7 without problems?
[Fascinate Android Development] uslacson1:
No problem encountered.
[Fascinate Android Development] JoeProcopio:
sorry for asking a question that i'm sure has been asked before many times over, but can't find

since we had to flash 7/04 with the fixed CWM, but CM7 loads CWM4.x, if we flash 7/09 over 7/04, can it be done in CWM 4.x?

also, if i wanted to do full wipe, what recovery should i use? reboot/recovery brings me to 4, is that cool to use to wipe everything and flash 7/09? (as well as term emulator reboot/recovery does)
[Fascinate Android Development] AuroEdge:
Some 'bugs' I am experiencing:

*Latitude uses a lot more battery than on TouchWiz. Maps is active for a long time in the background

*News & Weather does not sync as often as it should

*Streaming media crashes out after a non specific amount of time. Apps include Pandora, Qriocity, and Netflix

*Data icon is present but does not seem to be transferring from time to time

It seems that the last bug might be causing the problems. Sometimes the data icon will disappear but most of the time it's there. Even when it is there I still seem to have connectivity issues. Happens on ED04 and EC09 radios. Using latest CM7 version
[Fascinate Android Development] xceebeex:
So for flashing this the first time do I have to do the repartition thing with the pit file? Or is that only done if I want to go back to something other than CM7?
[Fascinate Android Development] Junkboy0:
I would suggest reflashing the rom and double check to see if it helps.
[Fascinate Android Development] RegnierD:
It's your lucky day, sir, since I made the same switch about two weeks ago.

It's certainly a different experience. Working with Odin is something to get used to, even though it's actually kinda simple once you get used to it.

You can kiss hboot goodbye, since that's why we use Odin. It makes the initial rooting process and flashing of the recovery image a bit of a pain compared to how easy it was on the DInc, but it's still relatively easy overall.

With the progress that I've seen made in the past couple of weeks, I'd say JT will push us right into official CM support here relatively soon.

The Ext4 formatting is very very nice, and makes flashing/everything feel super snappy. Overclocking seems to be more stable at higher frequencies than on the DInc, probably due to the slightly better processor, and that's definitely a plus. Coupling these CM releases with Nemesis2All's kernel makes this phone a beast.

I find myself accidentally hitting Menu instead of Home quite often, and I definitely miss the optical trackpad a lot.

The screen is where the beauty is really at though. It's massive (in a good way), and it just gorgeous. I find it slightly easier to type with the on-screen keyboard, and I can now crank out paragraphs at what feels like light speed compared to what I could do on my DInc. The colors pop perfectly and it's way easier to see in bright light than before.

Overall, I'm amazed at what this phone can do, and though the lack of a bootloader is slightly inconvenient, there's no way I could ever go back to my Incredible, though I will certainly miss it, as it was my first Android phone. I learned a lot from it, but I feel like it prepared me for playing with the big kids on this device.

The bugs I've encountered are minimal (limited to very rare lag, and MMS not working, and low in-call volume, which I think was just fixed but check the OP for confirmation in that one)

Sorry for the full review there, but I thought too much information was better than not enough.

I do miss Pons Asinorem's dry humor though... :/
[Fascinate Android Development] mrtonee:
only if you want to go away from the new cm7 you do that just dl jt cm7 and the gapps to your sd card and flash away.....
[Fascinate Android Development] mrtonee:
to answer your first question that is correct just do the 2 wipes (cache and dalvik) not the data, the 2 question that is correct........
[Fascinate Android Development] Mystique:
Random gapps question..

I know the OP has gapps from June $something..

Will flashing newer gapps work or break anything? I understand that there is no newer version at this time..

Just curious..

Sent from my CM7 with EC09; Thanks to jt1134.
[Fascinate Android Development] kwinders:
I just crossed my fingers, wiped cache and dalvik and after the typical long first boot...profit. I was nervous cause the last couple times I wiped between flashing I got the boot loop. This time was fine, smooth.

1 odd thing is I lost Swype. No big deal, I'll just reinstall.

Thanks JT, said it many times, you are awesome!!!!!!
[Fascinate Android Development] JoeProcopio:
ty....happy flashing...
[Fascinate Android Development] xceebeex:
Thanks, that is what I thought but I just wanted to make sure. I think I might give this a try later.
[Fascinate Android Development] ssewk2x:
This worked! Thank you so much :)

I should note that I tried to take a shortcut and ended up reverting all the way back to DI01 stock (yuck!). From there I flashed the EXT4 format all zip file and then installed comm rom 2.0. Once that booted up and did its thing, I odined the ec09 radio, JT's fixed recovery, and went from there with your instructions.

My phone is currently restoring my apps and running the CM7 build posted today.

YAY!
[Fascinate Android Development] xceebeex:
Can I flash directly with Build 9 or do I have to flash a different version first (I am currently on ComRom)? And do I have to install the Nexus S drivers once on CM7?
[Fascinate Android Development] obsidianchao:
Can I flash straight to 9? I'm on 6.
[Fascinate Android Development] AlgorithmX:
Yes and yes, make sure to wipe all 3.
[Fascinate Android Development] kuronosan:
Just an FYI, as I haven't read enough to see if anyone pointed it out: If you flash the new build without wiping cache/dalvik and you are coming from a previous build, you will lose 3G data.

Make sure to wipe cache/dalvik if you are experiencing this problem.
[Fascinate Android Development] xceebeex:
I just tried and I am getting the assert failed error.
[Fascinate Android Development] djk21108:
I think he means wipe cache and dalvik. Wiping data is a bad thing as it will make you lose CWM.
[Fascinate Android Development] AlgorithmX:
Flash cwr from op then flash rom
[Fascinate Android Development] akellar:
False
[Fascinate Android Development] BlackHoleSlam:
so all i need to do is wipe and flash this correct do i need a new modem i am on the official froyo ED01
[Fascinate Android Development] Headcase8911:
I believe that modem is fine, wipe the big three and flash, it's going back that is odin. That's why I'm waiting until I've got no reason to go back to flash this.
[Fascinate Android Development] BlackHoleSlam:
kk makes sense i am a little hesitant since i see people are having problems with gapps not transferring over
[Fascinate Android Development] cpark_12:
Must be hit or miss. All mine did fine. I'm having zero problems with this build

Swyped via Tapatalk
[Fascinate Android Development] D_Steve595:
Been running great for over a day now. With previous builds I've had this issue where after a reboot, everything gets f'ed up and crashes and doesn't work properly until I wipe data.

Here goes nothing.
[Fascinate Android Development] wideopn11:
Running smooth, I tried ED01 and now on ED04. Both work fine for me. OTB kernel is running smooth also so far.
[Fascinate Android Development] Headcase8911:
Let me know how she blows slam!
[Fascinate Android Development] mmuk223:
Under call settings is a keep screen awake setting to help with that problem.... forgot about that.
[Fascinate Android Development] jt1134:
There's nothing wrong with gapps. Gmail/maps/etc are not included with gingerbread gapps. Sign into market and you'll get prompted to download them.
[Fascinate Android Development] jerkules:
Are you talking about for when the phone won't wake or ring for a phone call or are you talking about when the phone won't wake after call completion?
[Fascinate Android Development] akaine2001:
thats the problem... i don't have market either. or i would have...

and there is a problem with the data on Cricket. I can't get any connection... same as all the other cm7 builds... i think it's something vzw in there where it needn't be. so i have to go back anyways since i can't get 3g on cm7 for some reason.
[Fascinate Android Development] shanky0506:
Has anyone seen any problems with non-Launhcer Pro widgets not coming back for Launcher Pro Plus after a reboot? Every time I reboot I have to replace my widgets.
[Fascinate Android Development] tmlhodge:
No that looks like a shankY0506 problem
[Fascinate Android Development] jt1134:
Market wont show without a data connection. You have no data connection due to cricket. I think I see where the problem is.
[Fascinate Android Development] BlackHoleSlam:
Everything is working beautifully now last question anyone know why I can't get my Google music to sync
[Fascinate Android Development] wideopn11:
Try uninstall and re-install, that happened to me a couple days ago where the settings didn't show in the menu to sync gmail account.
[Fascinate Android Development] QuasiTD:
I just got hit with this issue midcall. Phone locked, and after a boot modem baseband shows as unknown. Can't *228 since it doesn't see a radio. Guess i have some Odin work ahead.
[Fascinate Android Development] akaine2001:
I was trying to go back to com rom 2.0 for now and something is fubar'd in my phone. Odin and download mode work, but the odin packages aren't booting into android. Recovery takes, and flashes files, but even that doesn't work. Going to try stock 2.1...

Originally. I put phone in download mode from cm7 (phone off). Flashed ED01 and atlas_v2.2.pit .

This should have put me at ED01 i thought but whatever=/ Instantly after this, I installed CWM and the recovery booted when it restarted.

Reading through the guides (again) to make sure i was doing things right confirmed my steps I thought. Maybe it was late (2am-5am)... but this morning, I tried everything... any suggestions?

I'm not getting Samsung logo upon start, just boots straight into blue samsung recovery from the ed01 tar. I'm :confused: frustrated with this. Any help greatly appreciated
[Fascinate Android Development] hecantbreathe:
Use http://adbdev.com/danknub/atlas_v2.2.pit and http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5 in odin at the same time and check repartition.
[Fascinate Android Development] Headcase8911:
Battery pull/re-boot may do.
[Fascinate Android Development] djk21108:
But, I don't think you need to wipe data in order to go from build 7-8 to 9.
[Fascinate Android Development] xceebeex:
I pushed it via ODIN before trying to install build 9. Would wiping data get rid of that CWM?
[Fascinate Android Development] jt1134:
wow

I don't do incremental upgrades. In other words, doesn't matter what ROM you're on, flash the newest ROM

CWM is inside the kernel, has nothing to do with /data

If you get asserts errors in recovery, flash the cwm files attached to the first post (and re-read the first post next time ;))
[Fascinate Android Development] xceebeex:
Not sure what I did differently from what the first post said. I pushed the cwm files in the first post via ODIN. Rebooted in to recovery and tried flashing build 9 (after wiping data/cache/dalvik) and got the assert errors. I will try booting in to recovery and flash the zip instead and see if that yields different results, but I am not sure how that would be any different.

EDIT: Just tried booting in to recovery and flash the fixed cwm and then tried to install build 9 and it still does not work.
[Fascinate Android Development] Codiusprime:
I am having this exact issue right now, it's really annoying. Really. Annoying.

Hmm, mine gets to "checking state of BML/MTD." Man, this sucks :-(
[Fascinate Android Development] mrtonee:
did you flash the gapps??
[Fascinate Android Development] mrtonee:
what are u pushing via odin???
[Fascinate Android Development] Codiusprime:
Are we supposed to flash the gapps first?
[Fascinate Android Development] mrtonee:
no you flash cm7 first than flash the gapps...........
[Fascinate Android Development] Codiusprime:
Ok.

Just started over from scratch.

Odin to Eclair with the atlas 2.2 pit file and re partition checked.

I am booting up now. Then I am going to OTA to Froyo, then root it. Then I will Odin the CWM attached to the OP. Then boot into CWM then flash Cyan then flash Gapps and it should work correct?
[Fascinate Android Development] xceebeex:
The assert error is happening before flash cm7 (well, while attempting to flash). I flashed the fixed cwm via ODIN the first time (the tar file) and then the second time I just tried to flash the zip while in CWM and neither time worked.
[Fascinate Android Development] mrtonee:
once you are rooted you just have to flash the cm7 and the gapps.......
[Fascinate Android Development] mrtonee:
what are u coming from froyo and you are rooted??
[Fascinate Android Development] xceebeex:
Coming from ComRom, so yes I am rooted and on Froyo.
[Fascinate Android Development] mrtonee:
all you need to do is do the 3 big wipes than flash cm7 and than the gapps...
[Fascinate Android Development] xceebeex:
I know you are trying to help, but that is what I have been doing and I am getting the assert error.
[Fascinate Android Development] mrtonee:
i am sorry i am clueless.......... how about trying dont odin the fix just do the 3 wipes and than flash cm7 and the gapps............
[Fascinate Android Development] Kaze105:
Did you flash the fixed CWM in the first post?
[Fascinate Android Development] xceebeex:
Yup, first time I tried to ODIN it and that didn't work so then I tried flashing the zip.
[Fascinate Android Development] scottzirra:
The files in the zip were apparently not the right size for the screen, I have tried several other ones since and they all work great. It could just be me believing in voodoo magic but i seemed to have the best success with putting the bootanimation.zip file into /data/local and then also adding it into the latest CM7 in place of the CM7 animation located in /system/media. I then zipped it back up and flashed the 7/9 build via recovery. Worked great.
[Fascinate Android Development] nunyazz:
I answered your original post a couple pages back. You just need the zip file in

/data/local
[Fascinate Android Development] garywojdan81:
I had this same error 2 days ago when I bricked while trying to fix something. The only thing I did that broke the bootloop/assert fail cycle was to reflash a froyo rom(miuiwiz) and nem's otb1.3 voodoo kernel. It put my cwm back to 3.0.2.8 but it booted up & I was able to successfully flash the 7/4 cm7 build, boot then flash gapps. For whatever reason, flashing the separate kernel did it for me.
[Fascinate Android Development] xceebeex:
I wonder if it was the separate kernel or the 7/4 build itself? It looks like someone else had to flash the 7/4 build before going to the next build as well. Maybe I should just try flashing the 7/4 build first to see if that works. I just don't want to get stuck where I have to repartition and all that stuff if something goes wrong.