yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] rxwookie:
Keep at it... it'd be my daily driver if you get the audio path working. I agree, yank Voodoo and let the end user install it.

Don't give up brother!
[Fascinate Android Development] swapnilss:
We know it's been giving you a tough time but please don't give up so soon.
[Fascinate Android Development] djp952:
Sorry I only had a few hours to work on this recently and was getting extremely frustrated with myself :silly:

As of last night, I know what's wrong with the output audio paths (really), just working out the best way to resolve it. Now that I can see what's going on I can have a look at the input audio paths as well (speakerphone, headset mic, etc). The problems are generally related. What's happening is essentially what I first thought ... the audio paths are being closed when they shouldn't be (or perhaps more accurately "over-closed") by the HAL, and when you wake it back up by changing it (press speakerphone or remove the headset, for example), it opens up and works normally. When the phone is first booted, it works because the in-call audio gets opened, it's only after you use it once that it gets messed up.

*sigh* Getting there.
[Fascinate Android Development] AuroEdge:
Is this more stable than CM10?
[Fascinate Android Development] djp952:
Hi everyone. I seem to spend more time apologizing to you than making progress on this, but I was called away on business rather suddenly there and just got back home tonight. FWIW, I love Kansas City :)

I have not abandoned ya, I just wasn't able to do anything useful for you in the past week. Android 4.2 is out (cool), but while I am working to get that on my VZW Galaxy Nexus, they dropped support for the Nexus S, which is not necessarily a good thing for this. For now, I'm going to follow suit and keep this at Android 4.1.2 while I work on these annoying problems. When I left, my test phone was working much better for output, but I hadn't gotten to the input (microphone/speakerphone mic/headset mic) yet. My wife bought a nifty headset with a mic I can borrow to work on that part, hopefully soon.

All I can really do is apologize at this point. I want this to work, but actual "work" keeps getting in my way :crying:
[Fascinate Android Development] swapnilss:
Family comes first followed by work. We can wait. No hurry. Take your time dj. Just don't give up.
[Fascinate Android Development] rxwookie:
+1
[Fascinate Android Development] AuroEdge:
2 reasons I'd want it to have cell telephony capabilities still though: 911 calls and auto-updating time. Looking forward to your stellar work on this!
[Fascinate Android Development] AuroEdge:
It seems like the rear speaker is putting out distorted music. I don't think it was like this on the CM10 nightlies

EDIT: Maybe I was just hearing things or the volume was up too loud. I've noticed the same thing on Nexus -- CM10 audio gets distorted if volume set too high but doesn't happen on stock software
[Fascinate Android Development] djp952:
Just wanted to check in with everyone. I haven't died or given up, I've just had my rear-end kicked fixing the audio HAL for this thing and it's taken about 10x longer that it should have. I *really* have a handle on it, putting together a decent implementation has been taking longer that I have had to spend on it.

The problem with the audio is systemic due to the kernel and the (in my opinion) very crappy code Google made for the Crespo (Nexus S). I've had most things working, but never all at one time. The root of all this evil is the Samsung Fascinate audio driver, it doesn't really support "in call' audio settings and as I've learned is coded particularly poorly. The Crespo audio HAL is tragically bad, and I spent the past couple WEEKS cleaning it up but still had some issues.

Where I am now is that since I seem to have it all under control, playback and voice calls and input and everything, but haven't tied it all together, I'm writing a complete new audio HAL from the ground-up based on the Galaxy Nexus (tuna) HAL. I actually like and prefer the C++ "legacy" model the Crespo HAL used, but the less sophisticated C model is what Google chose to go forward with, so I'm taking everything I learned and moving to that model. It will take some more time, and I apologize for that, but in the end it should be one less hurdle to overcome to get Android 4.2 in play, and it will be something I can share with the dev community at large, which is always a bonus. It should be something that can be modified for use with all Galaxy S / Nexus S phones moving forward if people want to.

Fascinate is special ... almost ridiculously so, but it CAN be made to work. I just had to become a lot less stupid first. I think I'm there, but there is a whole lotta typing that needs to be done. :silly: Sorry for the lack of updates, I have spent a great deal of time trying to fix all this and it first required me to understand everything that was going on, and at 20-30 minutes a day it's taken longer than I wanted it to. Quite a bit longer.
[Fascinate Android Development] AaronCompNetSys:
I found your previous work extremely valuable, giving a good old phone useable life to rival the market. Regardless how long this one takes, I'll appreciate it for a couple years more. Keep up the great work, I hope your hard work pays off in more ways for you than just how happy it makes us :laugh:
[Fascinate Android Development] djp952:
Unbelievable, but true ...

GeeWiz 3.2.3 Patch (EDIFY Update-Zip)

- This patch addresses all known audio input and output issues, both for playback and for voice calls

- Applying this patch will wipe data on the Google Services Framework app, you will be prompted to accept Location services upon reboot

http://www.mediafire.com/file/pzeeebfzv4bdrya/geewiz-3.2.3-patch-11292012.zip

MD5: b07aff4b5825d417b9a7ead898165fd2
​

Well, that only took about a month and a half. I wrote a completely new audio HAL for the Fascinate that seems to finally be able to deal with all it's little quirks. As far as I know, just about every single possible audio related problem has been addressed, but I'm sure you guys will let me know if I missing something, right? Voice Call support behaves exactly like Gingerbread/Stock now, no more hacks involved as I figured out how to do it Samsung's way. In and of itself, that makes this effort worthwhile. Oh, and Bluetooth SCO should be OK as well, but I've only done limited testing with it.

NOTES:

- TTY is not supported, which should be OK since the ROM doesn't have TTY enabled anyway. I would love to add this support, but only if I have a reason to do so, and I will need assistance since I don't have a TTY machine.

- I've taken some liberties with audio input gain in non-call mode (I cannot control gain in-call, the RIL does that). I took a long look at how Gingerbread was doing things, but I was unable to completely mimick how that legacy HAL worked, so I kinda punted based on real-world observations over the past couple days of testing. What I ended up with is that the built-in microphone is set to a higher gain than it used to be, and a wired headset is set lower. When using the Video Camera (and when it doesn't crash - LOL), the microphone gain is completely maxxed out to grab as much audio as it can. I have a limited number of devices and gizmos around here, so if you run into non-call input being too loud or too soft, please let me know, some of it can be adjusted.

- Bluetooth AD2P (media playback) and the Fascinate dock still don't get along all that well. This isn't new, but I wasn't able to do much about it. The problem here is that if you are playing media over BT and you dock the device, you'll still get audio through the dock. Android tells me when A2DP is in use, but it doesn't tell me when it stops, so .... just don't do that.

- There is a bug/defect in the GeeWiz "Dock Settings" that I didn't discover until recently that has nothing to do with the HAL, but I wanted to mention it since it's not fixed yet. If you select the "Maximize Volume" setting, when you dock audio will maximize like it should but when you un-dock it doesn't go back to the previously set values. I'll fix this, but for now I would avoid that setting.

LONGEST. BUGFIX. EVER. Sorry about that, and I'm crossing my fingers :fingers-crossed: that this is at least good enough to tide folks over while I address some other problems. If not, hey, it's software. Software can (almost) always be fixed!!!
[Fascinate Android Development] gorm:
Giving the latest updates a spin and all seems to be working as expected. Voice, MMS and WiFi are working great. Benchmarks are the same as the latest CM Nightlies so this is very encouraging. Thanks for all your hard work:beer:
[Fascinate Android Development] swapnilss:
I'll try it out too as soon as I can.
[Fascinate Android Development] rxwookie:
Works nice for me... only problem is now I cannot choose a custom ringtone. It's one tone or silent.

Any thoughts?
[Fascinate Android Development] djp952:
Oh yeah I forgot about that bug. Unrelated but definitely confirmed. I've found that rebooting sometimes clears that up and other times just going back into settings it will work. Something goes awry with the media scanner I think its related to the same problem that causes camera to crash -- unable to access a database file. I'll look at that next ... the Maximize Volume setting is less important and only applies for folks with a dock
[Fascinate Android Development] rxwookie:
Reboot worked for me. You rock!!! Thank you.

Edit: Do you know if the add-ons for GW 2.9 work with this? Specifically looking at super circle battery.

2nd Edit: DO NOT TRY THOSE FILES from the 2.9 thread... it borked my phone bad. Let me be clear, this was not the ROM's fault, but my own for trying unsupported files. I was easily able to ODIN back to GW 3.2 and recover from there. Whew!

Thanks
[Fascinate Android Development] djp952:
Ooooo ... sorry I didn't see this in time. Yeah, those mods replace the Android framework resources, I can only imagine how upset Jelly Bean was :)

At one point, somebody had a web site where you could upload your framework-res.apk and the battery icons and it would generate you a new one. I couldn't easily find it again, but in theory it would still work for Jelly Bean ROMs, I believe the format is exactly the same as it was with Gingerbread. If we can find that site, I would LOVE to link it up so people could DIY their own battery mods!!
[Fascinate Android Development] bdotdotts:
So I have a couple questions, please.

The 3.2.3 patch... Sorry, but I'm not familiar w/ how patches work.

Is it a zip file that I can flash from CWM or does it need to be flashed from Odin?

Do I already have to be on any specific GW ROM first?

Do I have to use GW Recovery?

I'm on the latest Baked now & like it a lot, but always like to try different new stuff.

I assume I'll Odin back to stock EH03 and then flash from there, right?

Sorry if these questions have already been answered.

And thanks for all the hard work!
[Fascinate Android Development] rxwookie:
Download stock EH03 --> ODIN version (http://xdaforums.com/showthread.php?t=1526488)

Download GeeWiz 3.2 full wipe TAR --> ODIN version (1st page of this thread)

Download GeeWiz 3.2.1, 3.2.2, & 3.2.3 patches --> ZIP files (1st page of this thread)

1. You need to flash back to stock EH06 in ODIN with Re-partition using Atlas PIT file... Especially coming from Baked.

2. Boot once and setup as little as you can. Shutdown phone.

3. Flash GeeWiz 3.2 full wipe in ODIN. (Note: Do NOT re-partition this time or you'll get stuck in a Boot Loop)

4. Boot & setup phone in Jelly Bean... reboot twice without installing anything

5. Now, reboot into Recovery... it will be GeeWiz recovery but you'll pick it up quickly due to similarity to Clockwork

6. Install patches 3.2.1, 3.2.2, & 3.2.3 in order & without exiting

7. Exit after all 3 patches installed (will reboot)

8. Let it settle in... reboot once or twice more for stability

9. Enjoy buttery smooth Jelly Bean after about 4 hours to allow for settling down of Android OS
[Fascinate Android Development] scarfman4:
Are you thinking of UOT kitchen? That's what I use to make my own battery mods for Gingerbread. I haven't tried it with ICS or JellyBean roms. Here's the link:

http://uot.dakra.lt/
[Fascinate Android Development] rxwookie:
Not your fault brother. I took a chance and it didn't work out. I knew that I had ODIN to fall back on.

And yes, Jelly Bean was pretty angry at me.

I swear this phone is virtually unbrickable (permanently). I was only borked for about 10 minutes total.

.

Never used it, but I'm interested. If I get it working... will let you know.
[Fascinate Android Development] AaronCompNetSys:
Mine went very smooth and had to reboot a couple times (Wifi and Sync failures). I'm very impressed so far. Edit: duh I'm ignorant, gesture keyboard is a feature in next version of ASOP. I'm interested in it if you are :) Undervolting kernel support be great too.

Thanks again.
[Fascinate Android Development] gorm:
Cool, this works great, just have to get the colors to match :)

already have done one but green colors just not cutting it
[Fascinate Android Development] gorm:
Here's a screenshoot and the battery mod I used:D

Whats the color code for the ICS/JB Blue?

Updated a little closer to the right color
[Fascinate Android Development] AaronCompNetSys:
http://xdaforums.com/attachment.php?attachmentid=1189290&d=1341931757

Swapped out Google Now for old version above, not enough memory.
[Fascinate Android Development] gorm:
U can use Titanium Backup to delete some system apps to free up some space. I usually delete email and email exchange since I only use Gmail the play books, play magazine and the play tv . That should free up around 70MB. Just be careful.
[Fascinate Android Development] gorm:
Okay everything is working great but chrome lags very badly. Just curious if anyone else has experienced this.
[Fascinate Android Development] AaronCompNetSys:
No need for heavy apps like Ti, link.

The default browser isn't chrome, but I installed Chrome and tried it, along with Dolphin, Dolphin Mini, Opera Mini and Opera Mobile. Chrome, Dolphin and the stock browser are too heavyweight for everyday use on the Fassy, you'll need a lighter weight one to get by. Dolphin Mini works, but triggers a bug in Swype where it doesn't put in spaces between words. Opera Mobile doesn't trigger the bug, but make sure you don't use the Mini version (IMO) that tunnels all traffic through their servers, AOL style...

The default Google Search app is also to heavy weight, including the Siri competitor (Velvet) which forces on the "google voice" keyboard even when you disable it. Loading the app triggers the search app (quick serach bar), the voice keyboard, Google Now components and also the heavy weight browser at the same time, killing our poor devices. You need to delete the velvet.apk and replace it with an older search app.
[Fascinate Android Development] djp952:
Looks great!

According to some code I made a while back, the ICS blue color code (RGB) is 51,181,229. It may have changed slightly, but that should be really really close.

So no problems using UOT Kitchen? That's phenominal (for all of us, those mods are hard to maintain since every build needs a new set!). I'll run through it once myself and add the steps to the front page. Any quirks or things that didn't go right that people may need to look out for?

very very cool.
[Fascinate Android Development] AaronCompNetSys:
No need for your screenshot app either :D http://www.tech-recipes.com/rx/24374/android-ics-how-to-screen-capture/

Taken with that method on this ROM:
[Fascinate Android Development] djp952:
Lesse ... what else from today ....

I'm down with removing some apps to make extra SYSTEM room, it's very very tight and I'm worried about Android 4.2 needing some weight management when the time comes. However, looking at the apps, there isn't much I think could be removed that would be OK with everyone. Currents is an obvious choice, but that only saves a trifle of space. Google+ would be probably be next on my list followed by Maps. Really anything that can be downloaded from Google Play that doesn't require a "canned" version be present first could technically be cut. My original goal was to just use whatever Google provides with the Galaxy Nexus (or moving forward into 4.2, the Nexus 4), but do let me know if there is a consensus on big apps we can cut without making life terrible for folks. Zero free space is a nightmare for tinkerers, I know. Certainly open to suggestions, or perhaps we can compile a "safe to delete" list?

I looked at the missing ringtones problem a bit. What I think it happening is that the SD card takes a LONG time to mount on this phone, and Android even puts an error about it in the logs every boot. On mine, it seems to take almost 10 seconds sometimes (but usually around 6). I'm using a crap card right now, that probably doesn't help. But anyway ... I was looking at changes Google made in Android 4.2 regarding the media scanner and there is a change with commentary about the database getting messed up if the volumes (which should include the SD card) aren't ready yet. This may be something I can back-port, it didn't look overly complicated.

Rebooting has a way of clearing it up, but it also has a way of causing it to happen. It's kind of a crap shoot at the moment. If the back-port from 4.2 doesn't fix it, I may try adding a delay somewhere in the android boot to try and give the old Fascinate a bit more time to get itself in order :silly:

Oh, and I added the CRT screen-off animation. Next build (3.3) for that one, not really worth patching and it would change the resources which would be counter-productive to the work gorm just did today with the battery meter!!!
[Fascinate Android Development] AaronCompNetSys:
Samsung had a class 2 card in my device which I swapped out for a class 10 with the fastest IOPs I could find, link. Maybe that would help? I don't have the ringtone issue. I actually tested this card to easily out perform the flash chip that is on board the Fassy.

Androbench, sdcard: Random read: 1283 IOPS, Write 272 IOPS

Internal (RFS): read 1193 IOPS, Write 131 IOPS

Possible apps for removal: Gallery (replaced by stand alone Camera app, recommend to user something like QuickPic), Velvet (replaced by non Siri version), Google Books, Movies, Plus, YouTube.
[Fascinate Android Development] gorm:
just make sure when in the kitchen to chose galaxy s instead of mtd

---------- Post added at 04:41 AM ---------- Previous post was at 04:31 AM ----------

Make the changes that are beneficial to the success of this port: beer: I would get rid of all the play stuff except for of course the play store. We can install most from the play store if needed.
[Fascinate Android Development] rxwookie:
I'm only getting about 5 hours on a full charge with very moderate use (verifed x3 charge cycles). On standby, I run out of juice in just under 10 hours. I've got the stock, 1500 mA battery. On GeeWiz 2.9, I was getting about 8-10 hours with moderate use, 20+ hours on standby.

Primary culprit on my phone (running GeeWiz 3.2) is Android OS.

Is it just me... or is the battery life on everyone's GeeWiz 3.2 Fassy this bad?

:crying:
[Fascinate Android Development] djp952:
I've seen somewhat similar results (nowhere near 5 hours, but still way less battery time than GB). It's on my list of things to try and figure out. From my research so far, having Wifi on definitely a problem as it doesn't "deep sleep" the way it should. After that, for me, it's usually an app that seems to go nuts for no good reason. I know that there is no Fascinate-specific power HAL in place, but the open source code I've seen for Cyanogenmod really didn't do anything. It's possible that just having a power HAL in place will help, and I will see what I can do.

The weird part about the battery life for me is that A) sometimes it seems to be great and B) I'm using the Gingerbread kernel. One goal of the latter was to try and prevent exactly this since it's known to be good, but of course some serious changes had to be made and it's very possible/likely that they have negatively impacted the battery life.

I also need to point out, hopefully without it sounding like a cop-out, that our batteries are OLD now and unless they've been replaced are likely near the end of their useful lifecycle at this point. I 100% agree that something's definitely amiss and GB is notably better (regardless of the battery age and I do hope to find something to help that after the bugs are cleaned up), but we can't completely ignore the age of the phone/battery here. I'm not saying everyone should run out and get a new battery, far from it, but a 2+ year old LiON cell phone battery is not going to work nearly as well as it once did. I'm seriously not trying to blame the problem on age, but it may ultimately boil down to Android 4.x simply needing more juice and OEM batteries from 2010 may not be up to the task :p
[Fascinate Android Development] djp952:
I also finally had the "eureka" moment with the Dock Settings / Maximize Volume issue tonight. At some point between when I started this and Android 4.1.2, Google fixed this on their own. When you dock, certain audio settings are AUTOMATICALLY maximized (primarily Music) now. The code I wrote doesn't expect that, so what's happening is:

> DOCK: Android OS maximizes some volumes

> DOCK: AtlasParts3g (GeeWiz) starts up and reads the current volume values

> UNDOCK: Android OS restores volumes

> UNDOCK: AtlasParts3g successfully restores what it thinks are the proper volumes, but Android already maximized them before AtlasParts3g came in, so the OS-restored volumes are now overwritten with bad values.

The solution here is pretty simple ... remove the code that's trying to do what Android does. I believe this to only affect the 3G-enabled version since the Wifi-only version works differently and will still need that service/setting.

This is another one that is not likely to be patched but will instead appear in GeeWiz 3.3. If my phone would stop rebooting for no reason on today's "3.3" build, that would speed this up - lol. Damn you Google and your inability to log important things we need to know :cowboy:
[Fascinate Android Development] rxwookie:
I think the WiFi not sleeping is the culprit for me. I always leave it on to minimize data use because I'm around so many hot-spots. That correlates with the prime user of my battery being "Android OS" during the first 4 hours of testing.

I did switch back to 2.9 and the battery life is better, so that seems to be it... at least for me.

.

I completely agree... my battery is the OEM 1500 mA one and it's probably going bad quick. I'll probably go ahead and drop $30 to get the 2200 mA Naztech extended battery soon. I plan on keeping the Fassy for awhile.

Thanks!
[Fascinate Android Development] AaronCompNetSys:
Today I've had problems with both Google backup service and alarm service preventing normal sleep. I disabled the clock app which seems to help with alarm partial locks, and turned off the backup option (also a problem I had in Gingerbread). The gallery app auto launching is just killing my performance, so I disabled it and installed a miui camera app I had that was ported to Fassy. Setting the dev option to limit background processes works great and frees tons of mem, but the setting randomly resets itself to "standard" after a reboot :confused: Had a couple random reboots in there so I'm recharging to start fresh to see if it will deep sleep better.

I have a brand new 1500 OEM battery, tested with Ginger GeeWiz to 30 hours, I would hope I can get close to the same out of it.

I also played with my sister's Fassy today (she wants the Jelly), she's running Ginger GeeWiz, and I forgot how snappy and smooth it was. Maybe JB is just to much for this little guy.

Update: I'm seeing the same with battery as rxwookie. I changed the built in mem settings to AutoKiller's aggressive profile and memory management seems better.