yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] mystycs:
I figured it out apparently I needed to go into usb debugging mode.
[Fascinate Android Development] myersw:
Scarfman, thanks for the suggestion. Have never tried doing anything like this but look do able I will give it a try. --bill
[Fascinate Android Development] scarfman4:
In response to djp's battery mod question I've always like sbrissen's darker battery mod. The only thing I don't like about it is you can't see the battery percentage while charging. I'm currently using my own broken circle battery mod I made on UOT kitchen. It doesn't really match the theme but it's easier to read than Wolfkmann's. If anyone wants it let me know.
[Fascinate Android Development] mystycs:
I was charging my phone last night and for some reason I wake up to it being 75 percent is this a known issue? Also

I don't think it is calibration because I put it in another galaxy s and the battery was still 75 percent
[Fascinate Android Development] JJ5150:
Yes I love the blue horizontal battery way better than the green one. But I'm curious... didn't you have one in GW 1.1 that had the percentage in the center of the image? I can't remember since I've flashed my phone so many times... But I do remember seeing a blue horizontal battery with the percentage in the center and I could almost bet it came from your GeeWiz 1.1 Froyo roms. Is it possible to get that one working in 2.4?

Not that I'm way satisfied with this one as is. Loving it Mike... great extra. thanks again.
[Fascinate Android Development] scarfman4:
That is the one he is talking about. It's sbrissen's custom battery he made a long time ago with primary darker blue colors and easy to read numbers. It's the default one used in GeeWiz 1.1 and can easily be made for 2.4. I've made one using it myself but don't have permission from sbrissen to post it so I'll let djp see if he can.
[Fascinate Android Development] JJ5150:
Yes, I didn't know the authors to it all...and I didn't remember it being dark blue, but now that i think of it, it was darker than the one posted. That is the one I like as well. Would be great to have that one. I just didn't want to sound picky... seems like a lot of work to do this stuff. :D
[Fascinate Android Development] djp952:
No, the GW kernel should be triggering a recharge event when the battery falls to 94% after a complete charge. If for some reason a complete charge was never signaled, that could cause it I suppose.

Would you be willing to send me a LOGCAT from your device after an overnight charging session? That will show me the entire sequence of charging events, as well as the battery % and voltage. Perhaps it's not reaching 100%, which is necessary to trigger the recharge code.
[Fascinate Android Development] djp952:
By popular demand ...

GeeWiz 2.4 sbrissen Accurate Battery Meter (EDIFY update-zip):

This update replaces the AOSP batter meter and graphics with the sbrissen Froyo meter and graphics

- Compatible with GeeWiz 2.3 - 2.4.2

http://www.mediafire.com/file/84xk0a0r5lkgfv5/geewiz-2.4-sbrissenbatterymeter-01032012.zip

MD5: 14ed6dcad2d6851e775c2ff8b8823ec0

This is the accurate battery meter from GeeWiz Froyo. It's a horizontal dark blue meter, authored by sbrissen. I wasn't able to perform a great deal of testing on it, since my phone was fully charged from working on some new kernel/recovery changes, but I think it will work fine. All the power management improvements on this device in the past year actually make it difficult to test certain things quickly -- this is not necessary a bad thing :D
[Fascinate Android Development] JJ5150:
Thank you very much. looks great. I'm very happy with this ROM.:D
[Fascinate Android Development] djp952:
It was brought to my attention that the Google+ application included in GeeWiz 2.4/2.4.2 will Force Close if you attempt to use the Messenger feature. I believe I have found the problem, which is a missing .so library file in /system/lib. It's a bit late to try to message anyone else, so I tried it against myself instead. I didn't Force Close, but I did still receive an error, the logs indicating a problem with my circles (I'm not my own friend - LOL). I think this patch will resolve the problem, but I have to wait until tomorrow to find out for certain when I can IM somebody.

This has been added to the "Known Issues" section of the first post as well (note that this is NOT compatible with GeeWiz 2.3, just 2.4 and 2.4.2...)

Google+ Messenger Application Force Close due to missing .so library

Resolution: Add missing library to /system/lib; update-zip provided below

GeeWiz 2.4(.2) Google+ Messenger Force Close patch (EDIFY update-zip):

- Compatible with GeeWiz 2.4 - 2.4.2

http://www.mediafire.com/file/kmcmmhe9ctkzh63/geewiz-2.4-googlepluspatch-01032012.zip

MD5: 5f5877ab0054b1357c95438c79da9687​
[Fascinate Android Development] noxqzs:
Hello,

Let me start off by saying thank you for putting so much effort into supporting this phone.

I am in the process of reading up on all the new ROMS/KERNELS for the fascinate, and am leaning on using your latest 2.4.2. Currently I am still on a DL30 ROM running Froyo. From what I gathered, I will need to update to the latest gingerbread Verizon prior to flashing any new ROMS. My question is in regards to the recovery. Is it possible to flash CWM after updating to the latest stock firmware, and then just the Geewiz ROM/Kernel, or do you need to use your recovery for any specific option? I am impartial to either. My only requirements after updating is to have tether and non-oem battery check.

thanks again
[Fascinate Android Development] Wdustin1:
has anybody tried using this kernel with super clean. 05? any issues, also does this kernel support voodoo lag fix for do I have to enable it before flashing over the KGB kernel
[Fascinate Android Development] joebob2000:
I got the same result as the above comment; coming from a SC .05 rom I flashed the "full monty" with Odin and the atlas 2.2 pit and it dumped straight back to green GW recovery on bootup. I odined CWR 2.5 and recovered from my last backup so it's back to square 1. I wanted to try a full wipe to get rid of a few weird bugs I am still seeing (mostly random reboots when playing games or running Google nav) but it will have to wait I guess. I tried to download and Odin the "stock EH03 tar" from the other thread, but it won't pass MD5 in Odin.
[Fascinate Android Development] Badger51:
GW Green Recovery Woes--Limited Directory Display

I'm loving this ROM and want to express my thanks.

However, I do have a wrinkle ....

I noticed a couple of weeks ago that when I went to select an update.zip, using the Green GeeWiz Recovery, that I could not move down the list of sub-directories beyond the "edge" of my screen. In my case, the last sub-directory listed is DCIM and I can't scroll beyond that.

My downloads directory, for example, is below DCIM and thus I can't access any of the files located there.

Previously, when I thought ahead, I simply moved the update files to a directory that I created that would list above the "cutoff"...

Anyone else notice this issue?
[Fascinate Android Development] JJ5150:
You can download the EH03 Gingerbread Stock update from the link on the first page of this thread. Everything you need is linked from this thread. It is best to flash the GeeWiz ROM "before" CWM... because GeeWiz has its own Recovery and it will overwrite any Recovery during installation.

It is recommended to flash the EH03 Stock Rom before flashing GeeWiz. Try downloading the stock .tar again... maybe its corrupt. Make sure your Odin is updated, and uncheck Auto Reboot. You don't need the Atlas 2.2 pit file. Just straight Odin should do the trick. Also, uncheck Re-partition in Odin. Hope that helps.

I have noticed this also. Had to delete unnecessary files to shorten the list because it doesn't seem to scroll. I believe at one time in an earlier version the GeeWiz recovery did scroll, but it doesn't now. not a big deal, but it is noticeable. I'm sure we'll see a fix soon. :)
[Fascinate Android Development] joebob2000:
Out of curiosity why no PIT file or auto-reboot? This is the first time I have heard that particular advice, and I have been through a LOT of threads on the subject. I tried the same process (w/ partition and reboot ON) after successfully getting the stock EH03 in and it did the exact same thing.
[Fascinate Android Development] notoriousB:
I'm running it on SC 0.5, no issues. It does not auto convert to EXT4 you need to either do that beforehand or do it via geewiz recovery.
[Fascinate Android Development] Wolfkmann:
Looking at the posted image, forgot how nice the dark blue is (and larger).

Question : is this file just the battery, or also the whole rom?

I am currently running the geewiz 2.4.2 kernel with SC 0.5 (they seem to work well together). Will this battery mod work with this combination?

"I just want the phone to work perfectly, despite all my tinkering. "
[Fascinate Android Development] scarfman4:
I doubt it. The android policy files aren't the same in SC versus GW. The biggest difference is the power button menus. SC has Download mode added whereas GW does not. I've tried using the SC battery mod on GW and when I try to get the power button menu I get Force Close city. This also applies to using the GW battery mod to stock EH03.
[Fascinate Android Development] nitsuj17:
yeah battery mods on the respective frameworks will screw up reboot options as the strings/resources for what is called on policy is different...im lazy and make the acc battery mods in theme kitchen (in all fairness i used to do it manually and add a billion things to the framework, so i earned the break lol)

u could manually copy the images from one to the other though
[Fascinate Android Development] Wolfkmann:
I will try this if you could give a few more specifics. Then, if it works and with your permission, I could post the results for others.

"I just want the phone to work perfectly, despite all my tinkering. "
[Fascinate Android Development] scarfman4:
I've done it in the past but won't be at a place I can walk thru it until later tonight. Or I might just make one myself and PM it to you.
[Fascinate Android Development] JJ5150:
I'm actually repeating the advice given to me by dj.. the author of this ROM. I've also seen ppl post with the same problems as you're having and read similar advice to them. You don't need the pit file, and if using Odin with auto reboot and re-partition on doesn't work, it would be safe to say the opposite does work. Give it a shot.. works for me. GeeWiz is one of the easiest ROMs to work with IMO. or maybe I've been using it more than the others and I'm used to it... LOL
[Fascinate Android Development] AuroEdge:
Was the EI20 browser the one that had trouble downloading files?
[Fascinate Android Development] scarfman4:
Not sure but the way I get around that in past roms is installing Astro File Mgr. Never had a problem downloading things like zip files that stock browsers didn't like.
[Fascinate Android Development] JJ5150:
I can honestly say the EI20 browser is way faster than EH03... #justsayin'
[Fascinate Android Development] scarfman4:
To follow up the request for the sbrissen battery meter for Superclean, I've posted one in the Superclean3 thread, post #1145.
[Fascinate Android Development] djp952:
For the brave souls out here, I've posted an "experimental" build of the Kernel/Recovery. Quadrant scores should look a lot better with the kernel (although still not blazing), and I actually added a device-wide file system conversion to the recovery tools. Will wonders never cease? LOL

GEEWIZ KERNEL/RECOVERY 2.4.3 ENGINEERING BUILD

GeeWiz Kernel 2.4.3 [Engineering Build] (EDIFY update-zip)

- Add EXT4 filesystem tweak to DATA partition mount options in init.rc to improve Quadrant Scores (waldothecat)

http://www.mediafire.com/file/ebd8r78w67f9y1p/sch-i500-kernel-geewiz-2.4.3.zip

MD5: 1696c03330221629c8454a82f645f88c
​

GeeWiz Recovery 2.4.3 [Engineering Build] (EDIFY update-zip)

- Add Convert Device File System option; allows conversion of entire device between RFS and EXT4

http://www.mediafire.com/file/i2qqzrdeblike48/sch-i500-recovery-geewiz-2.4.3.zip

MD5: a5b60252a67cf484edde1a39e5b5e721
​
[Fascinate Android Development] JJ5150:
Sure... I'll bite! I'm backing up my system with OdinMaker... when that's done, I'll load'er up. I assume recovery first?
[Fascinate Android Development] JJ5150:
I tried the new kernel... seems a little noticeable difference in performance.. that's good. being the n00b that I am I dont' know what the conversion file system is for... everything looks good so far. I'll keep til I find a bug, which I haven't yet. Thanks again.

Btw OdinMarker is junkware... either the backups failed during Odin, or it failed to recover once restored... boot loops for a $1.50. Back to the search for the perfect backup. :(
[Fascinate Android Development] djp952:
Conversion is used to change the file system between the stock RFS and EXT4 file systems. RFS works OK for the most part, but EXT4 is definitely better. It's what Voodoo-based kernels use. The only real catch to EXT4 is that you can't use a stock kernel against it, you'll just SAMSUNG logo loop since it won't be able to read the data. Many update-zips also don't work right against EXT4. My update-zips have a tool I made in them that can work with either RFS or EXT4, so no worries there.

I'd say if you're happy with the performance of your phone, leave well enough alone. This is for the guys coming from Voodoo kernels that wanted an easier way to convert the file system.

As for backup, I am working on a full device backup/restore for the GW Recovery. Backup was pretty much already done and works fine, going back through my notes I disabled it because ... I have no corresponding device-wide restore yet. The problem I ran into was logistical, there needs to be a way for the recovery to know it was a full device backup before it would show it, and there is a need to handle missing volume backups in some graceful manner. I'm looking at that next, but I don't have much time for the next few days in which to do so.

You can use GW Recovery to make backups, if you'd like. It's a little manual, but I think it works just dandy if you don't mind doing each volume individually.

BACKUP:

> Manage Volumes / Backup Volumes

> You want to back up SYSTEM, CACHE, DBDATA and DATA

> You have a choice of backup methods, choose the last one "YAFFS2", it's the fastest and what "nandroid" backups use.

RESTORE:

> Manage Volumes / Restore Volumes

> Navigate to the backup/volume directory in the UI

> The UI will filter the files so you only see ones for that volume, choose by date

> You want to restore SYSTEM, CACHE, DBDATA and DATA

> As long as you chose YAFFS2 for the backup (.yimg.gz files), your file system will not be converted on restore, it will be whatever it was before.

A full device backup option does a little more, in that it also backs up a couple folders on the SDCARD (Android and .android_secure), but they are typically OK to just leave alone.

The other 2 volumes you see, FOTA and PREINSTALL are pretty much worthless on a custom ROM, so you don't need to do anything with those when backing up or restoring. They are typically just empty wasted space. (FOTA is for Free-Over-The-Air updates, PREINSTALL is where Samsung threw things like the Tetris and Madden demo bloatware).

Sorry you spent $ on a tool that didn't work. I wouldn't personally recommend ODIN as a backup/restore tool, but I would be curious to see how that person manages to generate an ODIN-compatible file for the DATA volume (called movinand.bin). Perhaps he didn't, since it didn't work for you? :D

PS - I see a light blue Ice Cream Sandwich-y version of GeeWiz Recovery on my Galaxy Nexus screen ... bwa-ha-ha ... very cool. I promise to complete full device backup and restore for you guys first, I've just been tinkering with how to build workable things for my new phone! I think I like the green better anyway - LOL.
[Fascinate Android Development] JJ5150:
Very helpful info... thanks for taking the time to explain it. I'm backing up my system now. yay!

I did like the idea of OdinMaker.. it supposed to make a .tar.md5 backup file... but I did a system and kernel only... and a full device backup. the system/kernel restore boot looped on me, and the full device failed in Odin. glad it was only a buck and a half (refunded). live and learn... and I'm definitely learning a lot from this thread. koodos
[Fascinate Android Development] AuroEdge:
Would it be possible to remove the low battery constraints for the camera and video player?
[Fascinate Android Development] scarfman4:
There's an add on in the Superclean3 thread that has this.
[Fascinate Android Development] nitsuj17:
just for the camera, i didnt do the vid player :o
[Fascinate Android Development] JJ5150:
Lately I've been experimenting with KANGS CM7.2.0... but I still have my backup of GeeWiz... If I flash back to GW Recovery... can i simply restore my backup over the current CM7 Rom? Or do i have to Flash back to stock EH03, or GeeWiz 2.4.2 before Restoring? Curious. Just in case this CM7 doesn't work out, I'd like to go back to GW with less hassle as possible. ;)
[Fascinate Android Development] djp952:
Since CM7 builds are MTD, you'll have to flash all the way back to stock EH03 first, using whatever directions they provide. I believe you have to fix the partition tables using ODIN and the EH03 full stock reflashes the boot loaders as well. I've never tried it myself. After you're on EH03 you would need to then flash the recovery and kernel of your choosing, make sure it boots, then finally go into recovery and restore the 4 volumes (SYSTEM/DATA/DBDATA/CACHE).

What do you think of CyanogenMod on the Fascinate? OT, I know, just wondering. Don't think I'll ever jump myself, but I'm thinking about it on the Nexus. Building my own setup from full source is becoming more of a hassle than hacking existing ROMs was! Getting there, though!
[Fascinate Android Development] JJ5150:
I love KANGS verions CM7.2.0... I'm running v01042012... since then he's updated (today is a matter of fact), but not much has changed. Now I've tried Org. CM7.1 stable and nightly 112. Both of which just leave me wanting more. KANGS verion has a lot of extra options to tweak the **** outta it. I just love it.

I even flashed Glitch v13.1 kernel... but I don't see a big different... in fact, my Glitch kernel choked a few times on me. so I reflashed and going with the stock kernel... and it runs better IMO... (ssshhh... don't repeat that too loud, the Glitcherz will disown me LOL)

The reason I like CM7.2.0 is 1) you can change locksreens. 2) volumes and sound treaks with profile options. 3) Themes... so far I have about 10-12 themes.

I encourage you to try KANGS version... with this new link to an updated GAPPS file. Good luck brother...
[Fascinate Android Development] AmanteNJ:
i tried installing GeeWiz 2.4 sbrissen Accurate Battery Meter (EDIFY update-zip): with your recovery and with CWM and i am getting stuck at the samsung logo boot. any suggestions?
[Fascinate Android Development] scarfman4:
Did you wipe cache before installing it? Also are you using CWM or GeeWiz Recovery?

Also are you running the EI20 enhancement pack or the boot animations? If so does the Samsung logo turn blue and blurry then sharp and white? If so then it's probably stuck because Dalvik cache was wiped during the update. I've seen this many times after wiping dalvik.

If so just hold down the Volume Up and power button for at least 4 seconds. This will force it to reboot (same as a battery pull). It should boot up fine.
[Fascinate Android Development] djp952:
Are you using GeeWiz 2.4(.2) or some other ROM as your base image?

Have you applied any updates to the GeeWiz ROM that weren't posted by me? Not that it's necesarily a bad thing to do, it's just that the battery meter is in a core android framework module (framework-res.apk) that can cause serious havok if it doesn't match everything else. If so, no worries, try flashing whatever you had before and then boot into recovery and do a dalvik-cache wipe.

If you happened to have USB Debugging turned on before the failed update, it's very likely that you can use ADB to get to the device and grab a logcat as well, which should indicate the exception that's occurring. If you can, try to 'adb shell' to the device while it's booting repeatedly until it works and then execute 'logcat' as quickly as possible. When the device bootloops, you'll be disconnected, but the output will still be in the Command Prompt (Windows) or Terminal (Linux), and you can copy/paste that out to see if we can find an exception message in there.

I think the worst case here is that you need to re-flash the entire SYSTEM ROM, GeeWiz or otherwise, that should get everything back in sync for you and probably won't force any kind of user data wipe/reset. If it's not a GeeWiz ROM, you should still wipe the Dalvik cache after installing it, as far as I know I'm still the only person that automatically wipes the Dalvik in all the update-zips :) [Kinda mean to do, but it prevents a lot of issues - lol]

edit: try scarfman4's suggestions above ^^^ first !
[Fascinate Android Development] JJ5150:
GW Recovery

Mike... can your GW recovery partition my sdcard to ext4? or do I have to use CWM4 or minitool?
[Fascinate Android Development] djp952:
Nope, only VFAT. To be honest, the thought never occurred to me. I'd be interested to know if that has any real impact on the overall performance of the device. The only thing I really do with my SDCARD other than backup/restore is store about 10GB of music on it :D

Possible compatibility issues with stock-based ROMs aside, it wouldn't be difficult at all to add the abiliity to format/mount the SDCARD as EXT4 in GW Recovery, but it's kinda outside the scope of what I try to accomplish and best left to the advanced setups since I'm pretty sure that it wouldn't be compatible with the ROM anymore. Not that you suggested adding it, just thinking out loud!
[Fascinate Android Development] JJ5150:
You mean partition to ext4 wouldn't be compatible with GW ROM?

I heard it speeds up the performance... from several sources... just trying to figure out if it will work on all the Roms I bounce around with. Hmm... maybe I should leave well enough alone. If it ain't broke why fix it right? :-P
[Fascinate Android Development] JJ5150:
Anyway... as much as I love the look, feel, and options with CM7.2.0... it still has a few issues that GW does not. If only there were customs themes for GW...

once again... back to GeeWiz. Always faithful. :D
[Fascinate Android Development] Badger51:
SD Card not recognized on stock phone

I got a new phone, running stock, when my screen cracked.

I was previously running Gee Wiz 2.4.2

The new phone doesn't recognize my SD card....does Gee Wiz use a different format?

If so, short of rooting....which I will probably do anyway....

Is there a way for the stock phone to recognize and read my SD card?

thanks
[Fascinate Android Development] scarfman4:
How's the 2.4.3 kernel been testing? I've been debating on switching to it but 2.4.2 has been stable so far.
[Fascinate Android Development] djp952:
Nope, no funny business with the SDCARD, it's always been stock VFAT. Even the GW Recovery doesn't support anything but VFAT.

Do you have a microSD->SD adapter that you could use to plug it into a Windows PC to see if it comes up? Perhaps the replacement phone has some SD funkiness to it. Dumb question: did you insert it all the way until it clicks? (I said it was a dumb question, don't be mad!)
[Fascinate Android Development] djp952:
No problems here, and I haven't heard of any. I do have 2 unread PMs, though ... waiting until after dinner to read those in case they are bad news!
[Fascinate Android Development] Badger51:
No worries, no offense taken...pulled plenty of "dumb" moves in my life..

Not sure I have a micro SD adapter...but will look..

The micro SD card still works fine in the old phone, I can read files on the phone.

But on the new phone, the Mount SD card menu item is greyed out. At times, the phone appears to read the card when booting, but later tells me no SD card is installed.

Hunting for an adapter......