yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] AmanteNJ:
First i have Stock rom/Kernel rooted then flashed the battery mod and got stuck with the samsung logo at boot even after clearing davlik and cache. then went to Geewiz 2.4 flashed the battery mod and got stuck again. I end up going to Geewiz 2.4.2 and flashed superclean battery mod and that worked.
[Fascinate Android Development] scarfman4:
I think it's clearing Dalvik that might be messing it up. It's not really necessary just to update the battery meter. When I make my own I use a bare minimum Edify script that doesn't clear either cache or dalvik. I clear cache manually, flash the zip and reboot and it works fine.

Also using the battery mod from Superclean will cause you Force Closes when you try to use the power button menu since they're not the same. The same applies to using it on stock Roms and using GeeWiz battery mods on stock Roms.

EDIT: Here's one that I use that uses a bare minimum script with no clearing of cache (apologies to whoever made the script). Make sure you wipe cache (not dalvik). See if it helps:

http://www.multiupload.com/AEE7RBYSSY
[Fascinate Android Development] AmanteNJ:
besides the change of menu when power button is pressed (reboot is now recovery and recovery is now download) the sc battery mod works with GW 2.4.2
[Fascinate Android Development] scarfman4:
I just tried it. Guess you're right. Either djp must have updated his code to be closer to nitsuj17's or vice versa; it used to always FC on me.

Anyway try the link I posted a couple of threads up. I made it using the same script I used in the Superclean thread to make the battery meter you're using now. That will make the shutdown menu match.
[Fascinate Android Development] AmanteNJ:
will try it thanks ...anyway to correct the menu in power button, i pulled the framework-res.apk from the original GW 2.4.2 and just replaced the one i have and then reinstall the battery mod, now the menu is what it supposed to be.
[Fascinate Android Development] JJ5150:
Not sure if you've done this already but sometimes enabling USB Debugging fixes SD issues. idk
[Fascinate Android Development] briguyy:
Is anyone running Adfree on this ROM? I installed it and downloaded and installed hosts to 127.0.0.1 and im still getting ads.

Anyone else having problems?
[Fascinate Android Development] scarfman4:
I am and it doesn't catch all ads. You just have to keep updating it so hopefully it reduces them.
[Fascinate Android Development] briguyy:
Ok, thanks.
[Fascinate Android Development] Wolfkmann:
That's why I switched from adfree to ad away

"I just want the phone to work perfectly, despite all my tinkering. "
[Fascinate Android Development] JJ5150:
ad away works better as suggested... at least for me. thanks Wolfkmann
[Fascinate Android Development] mystycs:
My phone decides to keep making that sound as if I'm plugging it in when it's charging.

I understand that the phone stops charging once it is fully charged, and starts to discharge. I don't understand why it has to make that sound once it starts charging again though.
[Fascinate Android Development] scarfman4:
It's a hack in the kernel to fix the GB problem of not automatically charging after dropping below 95% like Froyo used to. Basically it fools the phone into thinking you unplugged the cable and plugged it back in again so it will start charging again.
[Fascinate Android Development] JJ5150:
haha... mine woke me up this morning. I thought there was a bird in my room. LOL :D
[Fascinate Android Development] djp952:
Yeah, I've been working on that without too much success yet. I'm missing something that's probably pretty obvious in the driver to get it to charge again without generating that event. I'm certain it will be a "well, duh" moment at some point :)
[Fascinate Android Development] JJ5150:
Actually. I've only heard it once since I've been on this ROM... so it's not a big issue for me. At least it's way better than the stock warning to "unplug now or your phone will blow up" constant alert. LOL :D
[Fascinate Android Development] djp952:
Well, I spent a lot of time on this the past couple evenings, and I'm pretty much out of ideas to solve it. Nothing I do makes any real difference, the sound is coming from some hook in the UI that seems to detect when charging starts, not when the USB is plugged in. I completely bypassed the cable status stuff and it still happens.

What do you guys think about me finding the place in the UI where that happens and disabling it completely? Downside: no tone/vibrate when plugging in the cable. Upside: no tone/vibrate when plugging in the cable :)

Although I like the updated code I've worked on as it's more what I intended in the first place (less hack-ish), the end result is exactly the same so I see no reason to do anything other than send it to the great bit-bucket in the sky.
[Fascinate Android Development] AuroEdge:
There are plenty of other cues besides the sound for plugging in. While this method of charging is in place, I vote get rid of the sound.

To add in other lockscreens you would have to make huge modifications correct? Just curious
[Fascinate Android Development] djp952:
From what I've seen/tried, yeah, that's a bit out of my league. I could likely steal/borrow/kang from others and get something hobbled together, but my fear is that it would be a neverending abyss of bugs and general misery. I managed to figure out the settings/selection part with the old EI20-based ROM (to enable puzzle-lock), but adding additional new ones wasn't something I had any real success with.

The lockscreen in and of itself, if I recall properly, wasn't that bad; it was the various other things that go with it like the answer widgets that really dumbfounded me. I think you're pretty much stuck with choosing one widget (slide to answer v. puzzle answer v. button answer, for example) to use for the locked/unlocked call answer modes, and then it won't necessarily match the lock screen. My EI20 ROM had the AOSP answer widgets with the Puzzle Lock and it was kinda weird :D

That said, it may be possible for me to port the old sbrissen 5-lockscreen mod to EH03 if nobody has done it yet, but I fear my chances of success are less than I'd like them to be.

At least I know my limitations, right? LOL :cool:
[Fascinate Android Development] scarfman4:
Switching topics to Recovery, I've noticed that some Edify scripts that work in CWM aren't working in GWRec. A couple of examples are scripts made from the UOT kitchen and Nutsij17's GApps. Any thoughts?
[Fascinate Android Development] djp952:
I'll have to look, but the most common problem I've seen is that a lot of scripts expect there to be certain binaries in /sbin that I don't have in my ramdisk image. mount in particular.

If you can PM me a couple links, I can at least make sure that's the issue and get symlinks for the missing applications checked in under /sbin for next time.

(All my ramdisk busybox apps/links are in /xbin rather than /sbin)
[Fascinate Android Development] AmanteNJ:
Try Magiclocker from the market, it's like adding another launcher/theme but you can keep your preferred launcher and keep the lock screen. I tried the zipper and other stuff, they are pretty cool.
[Fascinate Android Development] rxwookie:
I've been running some version of the GeeWiz ROM since it was first released. First the Froyo version, now the Gingerbread version and I've loved it. I fully agree that it is a cleaned up experience. I did, however, have one major issue when I went from the GeeWiz Froyo ROM to the GeeWiz Gingerbread ROM and one minor issue. In advance, I apologize for a long-ish post, but I think it might help someone else... so here goes.

Minor Issue: Annoying Notification Sound During Charging Overnight

I solved this for myself by going to the... system/media/audio/ui/ folder and renaming the Charger_Connection.ogg file to Charger_Connection.old. I then created a half-second of silence as an OGG file, named it Charger_Connection.ogg and put it in the system/media/audio/ui/ folder. Now my phone trickle charges at night and once full, I do not hear the charger connection notice. For anyone interested, I've attached the Charger_Connection.ogg file I created to the bottom of this post. Please note, I personally used Root Explorer in my sequence so permissions would not be an issue.

Major Issue: Recovery Boot Loop

I first Odin/flashed to stock Gingerbread (per instructions) and the phone worked great. I had a successful flash to GeeWiz and the phone began it's boot sequence. Instead of going to the main screen, however it dumped me at the GeeWiz recovery console. Stumped, I rebooted and landed again at the recovery console. Several times this was repeated, all with the same outcome (I'm convinced, by the way, that the real-world definition of insanity is "repeating the same action over and over again expecting different results")

I was afraid I'd finally messed up my phone, but a simple Odin/flash back to stock Gingerbread had the phone booting just fine. So I tried GeeWiz again and got into a recovery boot loop again. I shut it down, flashed back to stock and scratched my head.

I decided to flash Clockworkmod and get to GeeWiz using a zip file thinking maybe the GeeWiz recover didn't like my phone any longer. Only problem? You guessed it, back into a (very frustrating) recovery boot loop... only this time it was Clockworkmod recovery boot loop.

I flashed back to stock and tried to figure it out. It finally occured to me that it had to be a setting in Odin. After a lot of flashing (though, luckily no bricking), I found out that the "Re-Partition" box needs to be unchecked anytime you are flashing a non-stock recovery (such as CWM or GeeWiz recovery) parition for our beloved Fascinate.

So --> (Odin) Stock Gingerbread with Re-Partition enabled to get current --> (Odin) GeeWiz Gingerbread with the Re-Partition box unchecked == Very Happy User!

Whew,

Wookie
[Fascinate Android Development] djp952:
@rxwookie: I'm glad you got it sorted out, I really don't like it when people run into problems with anything I've done ;) For what it's worth, I don't recommend that ODIN option (and have NEVER used it - not even once!) unless you are coming from an MTD ROM or something that modified the stock partitions, and even then only using the full stock. The ODIN files I post aren't 100% complete, I omit the scary bits. ODIN is a best friend and a worst enemy at times :( Thank you for not only persevering, but for posting all that information so I/we can continue to learn more about this device! As for the sound ... read on!

> I am working on an update that gets rid of the sound/vibrate at the framework level. The sound is dead, but it still vibrates and I'm investigating why. Hopefully complete recharge silence without breaking anything else is close.

edit: OK, vibrate is dead too. It helps if you actually mount SYSTEM before you update it. LOL. Good for the next release.

> I have enough app updates to probably warrant a "GeeWiz 2.5", so it's likely that once this is ready that's how it will go down. I haven't had the time to work on Recovery any more since I'm also hacking away at my Galaxy Nexus, but at minimum it would include the experimental 2.4.3 kernel/recovery modules. I still have every intention to fix/include the full device backup/restore to Recovery, and properly investigate a couple issues that have been brought to my attention. Note that GW 2.5 will no longer combine the kernel with the ROM by default anymore. I also switched from "Nexus" as a default Live Wallpaper to a static default wallpaper and added that and one other wallpaper I kanged so far as selectable static wallpapers in TouchWiz. Wallpapers are a slippery slope; I have so many of them I think are awesome but I don't want to include more than a few!

> I am way behind on PMs, I apologize to everyone. I have 11 of them to go through and I honestly haven't had the time. For anyone waiting for a reply from me, I promise to get back to you this weekend!! :cool:
[Fascinate Android Development] rxwookie:
@djp932: After the second boot loop, I had no choice because I'm stubborn that way and had to figure it out. I posted here because I would hate for anyone to mistakenly conclude that a boot loop is caused by your ROM.

I agree completely that if you are going to ODIN any custom Rom, it's best to flash to stock first. I like Odin because it's gotten me back to a working, stock state several times from unbootable states.

Thank you for all your hard work on the kernel and Rom and recovery. You jokingly called it a gently dented Yugo before in the Froyo version... I'd disagree. It may not be a Cadillac, but to me it's more like a really comfortable crew cab 4x4 that gets the job done without fuss.

I really like the file explorer mode you employ in Recovery allowing ANY zip file to be used rather than requiring it to be a specific name and place.

Hands down, GeeWiz is my favorite! Keep up the great work!

Edit: I'd like to request that you package up the cool wallpaper collection you have and provide it as an extra for those with the space!
[Fascinate Android Development] JJ5150:
I tried this and it failed, twice on stock Odin. Unchecked re-partition and all was well. I also noticed that GW 2.4 runs better for me than 2.4.2. I didn't think there was any significant change, but my phone seems to notice a difference.

The connection sound does not bother me. Lets me know everything is working. Thanks again Mike.
[Fascinate Android Development] rxwookie:
The only time you should check the re-partition box is when you changing ROM types (i.e. from MTD/CM7 back to TouchWiz based ROMS) AND when you are flashing back to completely

Stock Verizon

ROM (i.e. fully bloated, fully Bing'ed, etc). And to add to the confusion... there are now 3 versions of the stock ROM, one each for Eclair, Froyo, and Gingerbread.

I may have misspoke, I didn't mean "stock Odin", but rather "stock Verizon Gingerbread Rom". My bad!

Additionally, from my experience... if you do not use the most current PIT file (Atlas_v2.2.pit) for going to Stock Verizon Gingerbread, you will end up with a failed flash. I've also heard back from users who checked the re-partition box and mistakenly didn't specify a PIT file at all and it ended badly for them.

Regardless, I'm glad to hear you got it working.

EDIT:

As far as Odin 3 and the Fasincate goes... there are only 7 boxes/buttons to mess with in Odin (regardless if you are using Odin version 1.3, 1.7 or even 1.85).

1.) PDA - ALL of your ROM files, Kernels, Recoveries, etc should be flashed in this box. DO NOT FLASH ANYWHERE ELSE IN ODIN FOR THE FASCINATE

2.) PIT - A valid PIT file (Atlas_v2.2.pit) should be in this box ONLY if you are flashing back to Stock Verizon ROM. As soon as you put a PIT file in the box, it should automatically check the "Re-Partition" box

3.) Re-Partition - Only when you have a vaild PIT file and only when you are going to STOCK VERIZON

4.) Auto-Reboot - Always checked

5.) F. Reset Time - Always checked

6.) START - Starts your flash

7.) RESET - Clears all settings and parameters back to stock Odin

That is it! If you have a

Fascinate

... DO NOT TOUCH ANY OTHER BOX or BUTTON! You will possibly turn your phone into a paperweight that will be difficult to recover from. Other Samsung phones may use different boxes, but not the Fasincate.

Those other boxes and buttons are only to be used when specifically instructed to do so

.

You've been warned!
[Fascinate Android Development] comradesven:
Thanks for noticing this and furthering my understanding of android.
[Fascinate Android Development] JJ5150:
I never use pit with any odin flash. Most mtd roms are zip flashable and dont require odin. When I use pit I get errors and funky operation. And as I said earlier re-partition to stock fails every time.... But I'm not coming from mtd either. I just wish I can get a cm7 version that's flashable with odin. I love using odin. Much more stable than flashing zip. Imo.

Also dj recommends no pit or re-partition using GW. I have to agree. But my sdcard is not partitioned ext4 either so... Maybe thats why. Of course i'm quite n00b in this cell genre as you can tell by my join date. Thanks for your very detailed posts on this.
[Fascinate Android Development] djp952:
I can certainly do that :) It needs to be filtered somewhat, ALL of them wouldn't fit on a Fascinate - LOL. I would like to take the time to learn how to make it a generic add-on that isn't TouchWiz-specific (can't be very hard), and then maybe I shall! How does ... 50MB sound as an APK size?
[Fascinate Android Development] djp952:
Wish I could explain that one, 2.4 and 2.4.2 share the same ROM/SYSTEM image:

djp952@BREHMM-LINUX-M:~$ md5sum GeeWiz/2.4-12272011/factoryfs.rfs
[B]f63b323485e8c598a439139a86b6056a[/B] GeeWiz/2.4-12272011/factoryfs.rfs

djp952@BREHMM-LINUX-M:~$ md5sum GeeWiz/2.4.2-12292011/factoryfs.rfs
[B]f63b323485e8c598a439139a86b6056a[/B] GeeWiz/2.4.2-12292011/factoryfs.rfs

So it shouldn't be any of the apps or modifications, it must be the kernel or something external to GW?? I hope it's not the kernel, but I have rebuilt my dev machine a couple times recently for Ice Cream Sandwich and again for a problem I had, so it's entirely possible that something different is taking place. :( See how 2.5 treats you, this is rebuild #3 of the laptop since GeeWiz 2.4. Maybe I undid whatever I did to ya!
[Fascinate Android Development] scarfman4:
I think it would help to know what seems different between 2.4 and 2.4.2. Personally I'm not noticing anything.
[Fascinate Android Development] djp952:
GeeWiz 2.5 (01.22.2012) has been posted, links are in the first post of this thread.

- Unlike previous GeeWiz releases, the ROM and Kernel are now packaged separately. If you want to update both the ROM and the Kernel you will need to download/apply both of them. I apologize for any inconvenience, but it was always a little out of the ordinary to put them together like that. If you are using the EDIFY update-zip (ClockworkMod/GW Recovery) method of installation, you can flash both components (and optionally GW recovery as well) in the same session.

GeeWiz 2.5

GeeWiz 2.5 ROM - 1.22.2012

Fixed issue with Google+ messaging (missing library file)

Updated Google Maps to v6.1.1

Updated Google+ to v2.3.1.242969

Updated Google Search to v1.3.3.247963

Updated Google Translate to v2.3.1

Updated SuperUser su binary to v3.0.3.2

[MOD] services: use /system/wallpaper/default_wallpaper/default_wallpaper.jpg as default wallpaper

[MOD] services: remove charging connected sound/vibrate

[MOD] TwWallpaperChooser: Add some additional wallpapers

GeeWiz 2.5 Kernel - 1.22.2012

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

Change auto-recharge point to 98% from 95% (note: charging begins between 98% and 97%)

GeeWiz 2.5 Recovery - 1.22.2012

Add Convert File System option; allows for full-device conversion to/from RFS/EXT4

Add symbolic link /sbin/mount->/xbin/busybox; improves compatibility with non-GW update-zip packages ***

*** - The update-zips that didn't work with GW Recovery that were brought to my attention all failed because of this missing binary (/sbin/mount), but please be advised that they all also assumed the Fascinate has an RFS SYSTEM partition, which means if you have converted to EXT4 (with a Voodoo kernel or manually via GeeWiz Recovery), they still won't work. Unfortunately, there isn't anything I can do to automatically fix that in GW Recovery, it's up to the author of the update-zip to not assume SYSTEM is always RFS. Please feel free to post here with any problems you encounter or PM me, it's not that difficult to fix update-zips to work for both RFS and EXT4. I'm also happy to share/explain how I handle that for the Fascinate.
[Fascinate Android Development] darkmage1991:
maybe a easier way of doing this would be an app that directs to a photobucket album with all the needed/wanted wallpapers and the user can manually choose the wallpapers they want on there phone and save them.

just trying to give ideas.
[Fascinate Android Development] JJ5150:
I may have spoken out of place. I flash this thing so much jumping from one rom to the next, different kernels, mods, blah blah blah... that it's easy to miss something or do something wrong... which is mainly the case with me. I do use KGB-EH03-1231.0150.tar kernel which is the only one that works best for me on GW EH03... all in all my experience with GeeWiz has been far better than any other Rom i've tried and tested on my fascinate.

But, If I can recall I believe it was the touch screen gone bad... or rather the phone wouldn't respond to touch commands as normal but would recover upon reboot. I would say it would last half a day or so or when an apk is installed or removed it would act up and I'd have to reboot. Not sure if it was the kernel or Rom, but no problems with 2.4. So, 2.5 might have to wait til I have some free time. :)
[Fascinate Android Development] rxwookie:
I've been rocking 2.5 (kernel, Rom and recovery) all day and absolutely no problems.

I also noticed new wallpapers, so DJ either added some (thank you!) or I've just overlooked in previous builds (belated thank you).

Edit: I see the new wallpapers in the changelog. Maybe I should read? Thanks again.

@JJ5150:

I'd highly recommend trying out the GeeWiz kernel. You may be experiencing problems because the KGB kernel isn't based on EH03 unless it's been recently redone. It's based, I believe, on EI20 which might be the source of your frustration.

DJ's kernel is fast and clean. Combine with his Rom and you have a very fast, stable, and clean phone OS experience.

So the kernel may be your issue, though I don't know.

2nd Edit: I see the KGB kernel is now EH03 based... my bad... so not sure what to tell you.

On the other hand, my Fascinate gets to acting weird (like your description) if I don't reboot for several days.

Either way, download and flash the new version. It is awesome! If 2.4 is working for you, 2.5 will be even better.

Right now, GeeWiz is the only Rom I'll run! Thanks!
[Fascinate Android Development] JJ5150:
Sounds great... load'r up! :D

thx rxwookie... i might have time tomorrow

-------------

WOW... All I gotta say is GW 2.5 is "WOW". I ran the combo tar.md5... and The smoothness and speed is amazing! No need to OC/UV. No Need for a speed kernel... this puppy is smooth-smooth-smooth! Even running the heaviest live wallpaper, this thing runs good. Small chugs I can handle... not one choke or freeze. all apps works.

I AM IMPRESSED! BEST TW ROM ON XDA IMHO!!! Thank YOU MIKE!!!!
[Fascinate Android Development] rxwookie:
I'll second that. Best TW Rom I've ever used. I can run items that even faster phones have trouble with. Not only the Rom, but the GeeWiz kernel is definitely one overlooked gem.
[Fascinate Android Development] JJ5150:
heh... I may finally be able to retire my flash gear. woohoo
[Fascinate Android Development] djp952:
Wow, thanks guys - you flatter me :o Happy to be of service!

I often wonder if it's getting to be time to retire this effort since I've met just about all the goals I set out to meet and it's extremely unlikely that we'll ever see anything new from Samsung/Verizon again for the Fascinate, but I have to say that comments like this make it all worthwhile ;) Not just these comments in particular, of course, but all of them.

It will never do everything everyone wants, but I'm very content and satisfied with the way it's turned out and the niche it seems to fill.
[Fascinate Android Development] AuroEdge:
I guess we'll see what Samsung's supposed Value Pack will be. Sounds like something from K-Mart (nowadays, not the 90's version)
[Fascinate Android Development] AmanteNJ:
BLN Support ? :)))
[Fascinate Android Development] nitsuj17:
well since it seems the showcase (fa10) is getting 2.3.6 (i ran it and wasnt particularly impressed) when they had a 2.3.5 update as well....id imagine its possible that verizon may drop another update or two on us at some point

maybe with a few things from the i9000 value pack or something...who knows :o