yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
I found a setting people have been using on Crespo to deal with Bluetooth draining the battery too much, and for *idle* with no Wifi-on , it does seem to have made a small difference. Screenie attached (clean install, Wifi off, not connected to Google Services). I would like to know what a device that isn't even signed into Google is doing waking up that often.

I'm going to see what happens if that Wifi deep idle code is put back in place. Who knows, it might even work! I doubt it's possible to attain the same battery life we had, but if I can knock off a couple offenders here and there it could make a world of difference.

The 3.3 build I've been working with is ticking me off, I'm having a recurrence of an old problem and I don't know why yet (reboot when waking from sleep). What was wrong before certainly isn't wrong now and 3.2 is working, so I must have missed a check-in somewhere. Greaaat.
[Fascinate Android Development] djp952:
I found a setting people have been using on Crespo to deal with Bluetooth draining the battery too much, and for *idle* with no Wifi-on , it does seem to have made a small difference. Screenie attached (clean install, Wifi off, not connected to Google Services). I would like to know what a device that isn't even signed into Google is doing waking up that often.

I'm going to see what happens if that Wifi deep idle code is put back in place. Who knows, it might even work! I doubt it's possible to attain the same battery life we had, but if I can knock off a couple offenders here and there it could make a world of difference.

The 3.3 build I've been working with is ticking me off, I'm having a recurrence of an old problem and I don't know why yet (reboot when waking from sleep). What was wrong before certainly isn't wrong now and 3.2 is working, so I must have missed a check-in somewhere. Greaaat.

edit: duuuuuhhhh ... it's the CRT off animation. I knew there was a reason I didn't include that! <bangs head on desk> LORD this device is fussy!!
[Fascinate Android Development] djp952:
I re-enabled "MAX" power mode in the kernel Wifi driver and so far it seems to work fine and more importantly it appears to make a HUGE difference in battery life. The idle battery drain with Wifi on was a great deal flatter than it has been. Attached screenie was my drain last night. This is the OEM battery that came with it, too, so it's old and should be dropping pretty quickly from full charge to about 85% ...

So far no missing ringtones either after a tweak there that may help. Too soon to know if that's really fixed or just hasn't broken yet.

Looks like the biggest issue holding up a 3.3 release is the video camera/gallery problems, but I won't dwell too long on those as they don't seem to be showstoppers for most people.
[Fascinate Android Development] AaronCompNetSys:
A quick note for anyone who might be switching back and forth, don't forget to run a kernel cleaning script before flashing back ;) Would have saved me hours last night if I wasn't so forgetful. Not sure if related, but I was having trouble with Nandroids not restoring system properly and had to reflash the ROM after restore.
[Fascinate Android Development] djp952:
I'm satisfied that the Wifi change doesn't cause any serious new problems, so rather than make you guys wait for 3.3 ...

GeeWiz 3.2.4 Patch (EDIFY Update-Zip)

- This patch enables extra Wifi power saving features that improves the battery life of the device when Wifi is enabled

- 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/lk19gk7bjir7cu2/geewiz-3.2.4-patch-12032012.zip

MD5: b9b5caa7917e5f6c4205eae2f6ce15f7
​

NOTE: If you run into issues, you can uninstall this one by simply re-applying the 3.2.1 patch. Both are just kernel updates.

The Bluetooth setting change also seems to be necessary for the best battery life, but that has to wait for GeeWiz 3.3 along with some other minor things that are in the queue.

Let me know how much, if any, effect this has on your battery life (hopefully in a positive way!)
[Fascinate Android Development] rxwookie:
Preliminary testing this morning shows a 5% per hour decline in battery when sitting idle with an active Wi-Fi connection on the GeeWiz 3.2.4 ROM/Kernel for me.

That's very comparable to the 3% per hour decline I get with GeeWiz 2.9. It's also a LOT better than the 20% per hour I was experiencing before the 3.2.4 Wi-Fi patch. So definitely a positive!

Test Time: 2 hr. Did not use the phone much at all, just a check in about every 20 min to see what the battery was doing.

Battery: Stock, 1500 mAh Samsung battery, 1st charged Dec 2010

My settings:

- Display Brightness: Automatic

- Display Sleep Time: 1 minute

- Number of Active Processes Allowed: Automatic/Default

I plan on keeping track of my battery for the next 48 hours and I'll edit this post with more data once I have it. So far, it seems to be much improved. I'm also going to test the battery under load as well.

Finally, not that it matters one bit... but I've ordered the Naztech 2300 mAh battery so I can have a fresh go at this phone. I'm hoping for about 15 hours with regular use of the phone so I can make it from morning to night without charging. I know that it's possible on GeeWiz 2.9 with the extended battery... but I really like the Jelly Wiz ROM (GeeWiz 3.2.4) and also plan on keeping this phone as a Galaxy Player (GeeWiz 3.2 Media Edition)... so I need this to work!

---------EDIT-------------

Okay, so at 5 hours in relative deep sleep, I've seen it only fall off 17%. That's impressively close to the 3% fall-off with Ginger GeeWiz. I'll put it through it's paces on a game (for an hour or two) tonight and report back the results.
[Fascinate Android Development] AaronCompNetSys:
I'll do the same testing once the weekend rolls around. I use mine at work so I can't afford to have it die.

That battery... is just so... ugly! The thinness and size is why I love my Fascinate. I've went through all possibilities to avoid making it less pocket friendly. I get up to 30 hours of light use, and easily can make it 8am to 8pm with almost heavy use on Ginger GeeWiz, with the new 1500 battery. Discharge practically freezes in place on screen off and I'm easily in deep sleep for 90% of the day.

If you are still worried about battery lasting the whole day, one way is to help is to install a car dock. Charging mine in my car on way to and from work is enough usually that I never plug in my phone elsewhere.

Dashboard dock for Smart Phone

Get snipped! Dock charging
[Fascinate Android Development] djp952:
woohoo! Great news rxwookie! I'm glad it's heading in the right direction finally :) :) :)

After I get the Bluetooth change out to you guys, I did look into one more thing that can be done this morning ... a power HAL. Gingerbread has one, so perhaps with some creativity there we can eek even more juice out of this thing. The basic gist is that Android will tell me when certain things happen ... things like "screen is off", "screen is on", etc (admittedly I haven't really looked at the full list). So, if we're still seeing an adverse amount of drain when idle, like when it's waking up to do things in the background, I believe the power HAL can be used to dial down the CPU and keep it down (for example, instead of something like 1.0GHz/200Mhz perhaps with the screen off it should be more like 400Mhz/200Mhz). I imagine there are more extreme things that can be done as well, but the CPU is probably the next best place to visit. We'll see!

I'm so happy this had a positive result! :cyclops: I'll keep at it (I'm slow as hell, but hey -- still way faster than Samsung ever was -- lol)
[Fascinate Android Development] rxwookie:
Detailed Results on Battery Life with GeeWiz 3.2.4

Results: 93% discharge over almost 12 hrs (97% to 4%)

- With deep sleep and light use at work for job related functions (40%)

- Moderate use at gym (as my music player) for 1.5 hours (15%)

- About an hour of gaming with Angry Birds & Helodroid 3D (29%)

- Otherwise in deep sleep (9%)

As far as splitting that out into usable numbers... here's what I found:

- Deep sleep: avg 3% loss per hour

- Light use: avg 5-6% loss per hour

- Moderate use: avg 10% loss per hour

- Heavy use: avg 25-30% loss per hour
[Fascinate Android Development] djp952:
GeeWiz 3.3 has been posted to the main page:

GeeWiz 3.3 ROM/Kernel (EDIFY Update-Zip)

http://www.mediafire.com/file/8o814dcbq2471kq/geewiz-3.3-syskernel-20121205.zip

MD5: 7699cd316a694eae8b672ffa6572d24c

GeeWiz 3.3 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)

This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot

http://www.mediafire.com/file/p0a2481ddd7hf7n/geewiz-3.3-fullwipe-20121205.tar.md5

MD5: 45ea8cec4b00f49fddad94b69e008fee
​

Verison 3.3 is mostly a roll-up of the four patches released against version 3.2, but there were some additional minor changes that were in the queue that made it into this release. One thing that didn't make it was the CRT screen off electron beam animation, sorry about that. When enabled, it caused random reboots on resume from sleep. Maybe someday I can fix that, but it's loooow on the list.

Changes:

[3.2.1] Fixed problem where enabling/disabling Wifi would appear to hang and necessitate a reboot of the device

[3.2.2] Fixed an incompatibility with some applications (WhatsApp Messenger, for example) that are incompatible with the way GeeWiz 3 has implemented the DBDATA volume to store SQLite database files

[3.2.3] Completely new audio HAL (Hardware Abstraction Layer) to resolve various voice-call audio issues

[3.2.4] Enabled enhanced power saving features of the Wifi driver to improve battery life when device is idle and Wifi is ON

Disables an internal Bluetooth setting that was incorrect and causing a small amount of extra battery drain, even with Bluetooth OFF

Removes an ill-conceived file system tweak that was actually hurting performance and may have been the root cause for semi-random empty Ringtone/Notification/Alarm lists in Settings/Sound.

Removes "Maximize Volume" setting from Settings/Dock. This option was unnecessary on the 3G-enabled ROM as Android was already taking care of it, and it ultimately caused media volumes to remain maxxed out after undocking the device

Sets Wifi ON by default after a data wipe; this resolves an issue where Wifi could not be turned on until the device has been rebooted at least once after a wipe.

It's mentioned on the main page, but you can upgrade GeeWiz 3.2.x in-place to 3.3 without wiping data. Just install the EDIFY update-zip version using your favorite recovery, sit back and wait while the "Android is upgrading" process takes place, and you're done. No muss, no fuss.

As always, please let me know if you run into problems and I'll do my best to resolve them for ya. The folks out here are great as well and are always willing to jump in and help ... ask away!

Enjoy! :highfive:
[Fascinate Android Development] djp952:
Hmmm... I may have undersold the battery savings attained by changing that Bluetooth setting. Combined with the Wifi power savings, I was quite surprised when I checked the phone this morning. Check out the drain curve from my phone last night (Wifi On, Bluetooth OFF, just sitting on my desk for 8 hours) ... and this is with the original battery! djp952 is pleased. If I can reduce the amount of time it wakes itself up to do .. whatever it's doing ... I think this would be pretty darn close to Gingerbread.
[Fascinate Android Development] rxwookie:
Impressive. That's what I'm talking about!
[Fascinate Android Development] gorm:
Reworked the battery mod for the new Framework. Colors are close:fingers-crossed:
[Fascinate Android Development] djp952:
Like! As promised, I've added this to the DOWNLOADS section of the first post. If you have a name you'd like to give it (unless you actually like "Battery Meter by gorm" - lol), let me know and I'll update it. If you would prefer not to have it linked there, I can remove it. Totally up to you my friend.

THANKS :good:
[Fascinate Android Development] gorm:
Thanks, you can name it whatever. Doesn't matter to me. Just trying to help:)
[Fascinate Android Development] bmeek:
I had been running the cm10 nightlies and finally decided to try this out.

The op simply stated that one must to return to stock to flash this, so I thought I would try installing from mtd/cm10 to GeeWiz 3.3 in one step...

From odin v1.85 I selected atlas.pit, GBbootloader.tar and GeeWiz3.3.tar and flashed all three at the same time.

Worked a charm! On first boot it formatted to ext4 as advertised, and proceeded to the configuration process.

Performance is great. One of my more challenging activities for most Rom/kernel combos is to load up the NPR News app's playlist with a number of stories to stream via 3G, start them playing back via a Bluetooth headset, power-down the screen and pocket the phone for a long walk while hearing the news...

You see, the NPR News app isn't very good at playlist transitions while the phone is otherwise idle. It will often stop playing altogether, or pause for a long time when a story ends before skipping a track or starting to play a track in the middle. GW3.3 got through 4 stories perfectly. I continued the same process in the car dock for several more stories (with the charger disconnected and screen off), when it suddenly rebooted between tracks. Weird.

Not too worried about the reboot as I was doing a bunch of stressful stuff (switching from bt audio to dock audio, etc.). Also, I had over-clocked to 1.1gHz and set the governor to interactive...

Oh - I went to backup my configuration ala nandroid and found myself wishing that gw recovery had the same kind of 1-step backup and restore - is there an easier method? As a creature of habit, I'm wondering if there's a compatible version of cwm recovery that someone might point me to?

Anyway, this is good stuff. Thanks so much for all the hard work!
[Fascinate Android Development] scarfman4:
I decided to give this a try. Looks very good and simple to work with, and the phone ability is load and clear. Only three things that I'm wondering if are possible to include in future versions:

1. I really miss the toggles in the notification bar. They don't have to be customizable like in AOKP and CM releases, but at least the basics (wifi, bluetooth, gps, & auto rotate) would be nice.

2. I miss the ability to swipe the status bar to adjust brightness levels when auto-brightness is turned off.

3. The background of the settings screen has a lot of lines in it. Is this because of the different graphic drivers in the kernel?

Anyway I'm not criticizing the work, and I'm really glad to see you haven't abandoned development on this phone that won't die. :)
[Fascinate Android Development] djp952:
Thanks! I really appreciate the kind words!

As for a CWM recovery, pretty much anything recent out there for Fascinate should work just dandy. The latest official one I see (http://www.clockworkmod.com/rommanager) is 3.0.0.8. At worst, I think it might try to convert the SYSTEM volume to EXT4, which is perfectly fine and supported by the GW kernel, I just couldn't do it automatically as part of the ODIN since people may not have an SDCARD installed. CWM is a much more feature-rich tool and I highly recommend installing it rather than my recovery especially for full device backup and restore. [My recovery code has a full backup/restore and it's disabled; probably because of some fatal flaw I never fixed - lol]

If you have another crash, I'd be happy to try and investigate it as well. The Android "bug report" feature is enabled on this ROM, so we may be able to get the root cause if you run it immediately after the phone reboots (not always, but it's worth a shot). You can either go into Settings/Developer Options and click "Take bug report". Pressing VOLUP + VOLDOWN at the same time is also supposed to do it, but it doesn't always work. Regardless, it will churn for a while and pop up a bunch of "shell has been granted root access" messages and ultimately set up a draft e-mail in GMail. You can send it to me (djp952@gmail.com) if you'd like. Can't promise I can figure it out, and I know you said it's not a big deal, but if ever becomes one please let me know :highfive:
[Fascinate Android Development] djp952:
No negative criticism taken ... I appreciate the feedback!

1. Me too! I've started working on Android 4.2 for the Fascinate which changes that particular game quite a bit, but if for some reason 4.2 becomes a complete bust I'll certainly try to port those features into 4.1 for everyone. The 4.2 quick settings still bugs me with certain things not being toggles (Wifi primarily), so even if 4.2 works out I have a vested personal interest in doing these things.

2. Same answer as above, and should be generally in the same code to steal from somebody (thank you team Cyanogenmod - lol) if 4.2 isn't going to happen.

3. I'm not sure what the deal is with that, actually. I know a lot of Galaxy S 4.0+ ROMs suffer from that same deficiency, it's been a complaint I've seen a lot. It looks to me like the color depth of the gradient is being converted, much like you'd see on a lower-end HDTV. The graphics subsystem is a bit hacked, borrowing a lot of pieces from the Nexus S and other stuff that I managed to cherry-pick and get working together. It bothers me a little as well, but the only place it seems to exist is with the settings background gradient so I never spent any time looking into it. I'll probably forget, but if I don't I'll check out where Cyanogenmod and AOKP are on this and see if they have a solution that would apply. I suppose the gradient could also just be replaced with something that works better for this.

I'm very glad to see you over here, scarfman4! I'm also glad you didn't try this before now, the 3.2.x "beta" versions were pretty rough for a while there :D
[Fascinate Android Development] gorm:
Here's another battery mod that was requested. This one has blue, orange and red colors i think. Not had my coffee this morning:p

Thanks to Scarfman for the UOT kitchen link

FYI, This battery meter for some reason is only showing up to 98%.
[Fascinate Android Development] JJ5150:
Thanks a million gorm!

Sent from my fascinatingly fascinating fascinate
[Fascinate Android Development] Shakes The AssClown:
I have 1.85...which pit are you doing? the one that came with 1.85 or the one that comes with the stock package. How are you doing the bootloaders...you putting that file in the bootloaders section or the PDA section???
[Fascinate Android Development] bmeek:
direct from cm10 to GeeWiz3.3 via Odin

I don't exactly recall where I got the PIT file, but it did not come with Odin 1.85 (probably the same file referenced by adrynalyne way back when...). It's the same PIT file I use when going back to the stock EH03 ROM).

Here's a shot of the files used:

Here's the Odin3 screen and the various selections:

I suspect it's unnecessary to include the bootloader file, since it's the same bootloader I use with the cm10 nightlies. However, it seems this bootloader gets downgraded when I flash CI500_VZW_EH03_GB_CM.tar.md5, and I seem to recall mention of the GB bootloader being required, so I included that too...
[Fascinate Android Development] mezster:
Correct me if I am wrong, but doesn't the bootloader file need to go in PDA slot since it is a .tar file?
[Fascinate Android Development] djp952:
Merci beaucoup! Added link to main post. You keep this up and you're going to need your own Battery Meter thread! LOL. It's greatly appreciated gorm, I can't even begin to describe how helpful this is.

It may only show to 98% because once the battery tops off, it actually stops charging and starts draining again. By default GW will kick the charger back on at 98%, so when you unplug it could be 98%, 99% or 100%. The MOD itself is probably just fine!
[Fascinate Android Development] gorm:
Thanks, I adjusted both battery mods to a slightly smaller size. They both fit better on the status bar :)
[Fascinate Android Development] gorm:
ok, last one i promise;) At least until another UPDATE :good:
[Fascinate Android Development] halcut:
How can I go back to GeeWiz 2.9?. Can I just ODIN the full package on top of this? Would EXT4 formatting on this ROM cause any issues going back?
[Fascinate Android Development] scarfman4:
I would say wipe all three (data, cache & dalvik), then flash both 2.9 ROM & kernel from GW recovery. That should not have problem with EXT4. If that doesn't work then I'd be on the safe side and ODIN back to stock EH03, boot up all the way then ODIN the full 2.9.
[Fascinate Android Development] djp952:
Yup, just replace the ROM and kernel with the older ones, wipe data and back to 2.9. Both 2.x and 3.x support EXT4 for all volumes and both use the stock partitions/volumes so you can go back and forth as often as you'd like (with the data wipe, of course!)

halcut, if you don't mind me asking, was there anything deficient about this ROM that is causing you to go back? I only ask in case it's something I can improve upon, or a defect/bug that I don't know about that might require resolving.
[Fascinate Android Development] halcut:
djp952 - Thanks for that info. Just to be safe I ODINed back to stock and then to full 2.9.

I have been using your gingerbread based Geewiz since its first release and have found it to be the most stable ROM for my fascinate. Hence I was really excited to finally move to ICS/Jellybean ROM as this was coming from you but I found 3.3 to be lagging overall. It's not as smooth as 2.9 or its prior versions. When I touch on any application icon to open, I noticed a lag for fraction of a second before the app opens. Even switching between apps, browsing and scrolling up/down a webpage, clicking a link on a webpage has a delay.

Let me know if you have any suggestions I can gladly try.
[Fascinate Android Development] djp952:
Fair enough, and I appreciate the feedback. It's definitely not as fast as Gingerbread or as responsive as a current dual-core beastie and the honest truth is it never will be. I think other ROMs/kernels have slightly better performance here and there but still not enough to make it as responsive as GB was .. hardware designed for Eclair running Jelly Bean! :silly:

Thanks for giving it a try -- it means a lot to me! I don't think it's ever going to be notably better performance-wise. Newer revs of Android will just continue to eat away at the CPU/GPU cycles we have so at least from me this is probably as good as it will get.
[Fascinate Android Development] AaronCompNetSys:
Here is my stats from a vigorous use yesterday. Seems pretty good. I went all out on killing the fat apps, even deleting the launcher2 (you lose the screenshot ability when its not running) and combined with the aggressive memory settings, its running pretty snappy. I generally have more free ram than I had on ginger without the aggressive settings.

Some tasker settings are not working right, as well as the IBM Lotus Traveler app is crashing, I'll look into that later. Otherwise its pretty stable, I'll use it at work and see how it goes.
[Fascinate Android Development] ekowanz:
Got here cause i need an odin file for clean install. Then try the rom. Its great rom. Definitely will give it a try.

First notice is, i got the vibration is very strong, is there a setting to soften it? Then there's not an option for change the battery and clock like the other jb rom. But hey there's optional file i could flash for the battery.

Thx for maintain this rom.