yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Yeah that Puzzle lock option shouldn't have been included until it was done. Lol. I finished it last night, it seems good now except the call answer screen is aosp still. I think notifications read the value directly and thats why you got puzzle for sms :)

I've had that screen problem too. I think it was the full battery notification... are you on charger when it happens? With full puzzle lock and no more battery popup I stopped seeing it. I'll go back to glass tonight and see if it still happens. I know the logs had details about it so it may be something I can fix!
[Fascinate Android Development] djp952:
OK, I've been running all evening with Glass Lock in place and the phone plugged in, and I haven't seen the screen wake up at all. I think it really may have been that stupid battery full notification, but do let me know if you were on battery when it was happening. Hoping to have the beta version with these changes out this week. I'm kinda slow. lol.

I've been posting some WIP stuff in post #3, but I'm having a little trouble migrating the AOSP answer/ignore screen back to Touchwiz, so I'm downloading a 2.3.4 Droid Charge ROM to see if there's any help in there. This may also give me what I need to fix the EI20 MMS as well :) The funny thing is that I don't even really like the puzzle lock and prefer the AOSP stuff ... which could be an option if this continues to be so difficult. As long as it all matches and has something besides Glass Lock (hate that one!) I'll be cool with it.
[Fascinate Android Development] AuroEdge:
It happened on battery discharge during 'non popup events'. It was random so to speak. Keep up the good work we all appreciate it!
[Fascinate Android Development] CGriffiths86:
I just installed the new rom, but the in-call volume control wont work. It stays at the same level no matter how much I raise/lower the volume.
[Fascinate Android Development] AuroEdge:
Is the GeeWiz 2.4.2 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN) supposed to install the 2.4.2 ROM? It seems to me that it clears out the partitions mentioned and installs a new modem and recovery.

If this is correct, I then have to install the EDIFY zip for the ROM?
[Fascinate Android Development] djp952:
Multiple replies follow ...

I'll build a kernel without the changes and see what happens. It's entirely possible, there were a lot of driver differences between EI20 and EH03. It would be nice to not have to hack that at all!

I'll look into this for you. Very possible that it's a problem that needs to be addressed, I only spot-tested call volume and don't believe I tried increasing/decreasing it on the test call. I'll make this my top priority.

The "Full Update" installs everything, including the ROM, so it's a one-stop shop with no need to flash anything else afterwards, except maybe any extras or other tweaks you want to apply.

You can open an ODIN .tar file to verify what parts are going to be touched. If you see factoryfs.rfs, that's the SYSTEM partition. The other files included in that TAR are: cache.rfs (CACHE partition), dbdata.rfs (DBDATA partition), modem.bin (MODEM), movinand.bin (DATA, PREINSTALL, FOTA partitions), recovery.bin (RECOVERY) and zImage (KERNEL). It should wipe out and replace everything except the bootloaders.

(In Windows, if you have WinZip it can open the .tar.md5 file as well to look at the contents if you rename it .tar instead of .tar.md5)
[Fascinate Android Development] scarfman4:
I just tested it and I can change my incall volume, both with the phone up to my ear (with the screen off) and away with the screen on. It won't lower by holding it down when next to my ear so I have to push it several times, but I can't remember if that's standard on any ROM for this phone.
[Fascinate Android Development] djp952:
OK, I did a test call to 202-762-1401 (Current time for US Eastern Time Zone audio loop) and I was able to adjust the in-call volume up and down without any problems here. I tried it when the screen was off (on-ear) and when the screen was on (off-ear). I also tried adjusting the volume with the speakerphone on, and it also worked.

A few follow-up questions for you:

1) Are you using the GeeWiz 2.4.2 kernel, or a different kernel? If it's a different one, no problem at all, just tell me what you're using and I'll be happy to install it and see if I can duplicate the problem.

2) Do you see the in-call volume slider appear on the screen when using the VOL UP/VOL DOWN buttons?

3) How about speakerphone mode ... does that seem to work any differently/better/worse? Does the microphone work in speakerphone mode?

4) Have you tried switching kernels to see it makes a difference? I'll provide a link to the GeeWiz 2.3 kernel below that you can try, but I'd also recommend taking comradesven's KGB kernel for a spin as well (link in first post of this thread). If the GW 2.3 kernel works, maybe try re-flashing GW 2.4.2 kernel as the audio code is supposed to be identical. Oh, and maybe try the stock EH03 kernel as well. Let me know if you need a way to flash that, it wouldn't take more than a few minutes to generate an update-zip for the stock kernel.

GeeWiz 2.3 Kernel (EDIFY update-zip):

http://www.mediafire.com/file/kcve8ba373ydyzb/geewiz-2.3-kernel-11302011.zip

MD5: 06b205c910530ddd63c8d973f7eb05e9

I'm sorry I can't duplicate the issue with my phone :( Unfortunately, that pretty much ties my hands at being able to try and help to resolve it. Hopefully we can find a way to make it happen for me as well so I can do something about this for you.
[Fascinate Android Development] djp952:
Ah ... yes, good test! Confirmed findings here as well. Holding the volume buttons while the screen is off does not do anything useful.

<flashes stock EH03 kernel>

The stock kernel has the same behavior. Holding the buttons down with the screen off doesn't work, you have to press them multiple times.

Thanks scarfman4!! If I ever end up with my own company, I'm totally hiring you as my lead test engineer :D You and nitsuj17 are always picking up my slack, it's greatly appreciated.
[Fascinate Android Development] AuroEdge:
Figured out my problem with the full ODIN wipe. I was using the Atlas2 pit file with the GeeWiz tarball. This would leave me at the recovery screen on boot. What I ended up doing was using the pit and stock EH03 ODIN. Then ODINed again but this time only the GW image. Worked!

I have to do this rigmarole because I go between MTD and stock file system occasionally
[Fascinate Android Development] djp952:
OK, I ran some tests against the stock kernel regarding the trickle charge and I'm not certain that it's actually working, the 100% indicator sticks there like it did before, but behind the scenes the battery voltage is still dropping off.

I charged the device to 100%, left it plugged in, and started a Netflix movie over 3G to drain. The battery got as low as 3.992V (not 100%) before I stopped it to see what would happen. The battery meter dropped immediately upon unplugging it as I expected it would. It unfortunately bounced back quite a bit in voltage, sending me to 99% so I have to execute the test again.

This time I will leave the phone plugged in and doing busywork for a number of hours to really work it down. If the battery voltage ever starts going up again then the EH03 stock kernel works. If it just keeps draining it doesn't. My expectation is that I will unplug and see a sharp drop in % as the battery is not recharging. We'll see! More on this when I'm done testing.
[Fascinate Android Development] notoriousB:
hey man I finally got around to loading the new 2.4.2 kernel, and have a minor bug to report: the kernel will not convert to voodoo. I was running stock EH03 due to the maps bugs, loaded 2.4.2 via 2.5.1.x CWM on top of it, and it booted right into android. Back to CWM, it reported voodoo was "disabled" but set to "enable" on next boot, no go. Set to disabled, re-enabled, tried everything I could think of, no conversion. Loaded KGB kernel, it converted immediately upon reboot, then I loaded 2.4.2 kernel on top of it and it's working great so far.

Just FYI. Don't want to make any more work for you, I'm up, running, no prob. I'd love to try the stock charging code in parallel with you if you'd care to share it!
[Fascinate Android Development] scarfman4:
I didn't think the GW kernels even supported voodoo lagfix, even since Froyo.
[Fascinate Android Development] notoriousB:
They certainly do, but your response just made me look through the OP and I found this:

I am not using GeeWiz Recovery, so there I go, that explains why it didn't convert!
[Fascinate Android Development] scarfman4:
Yup you have to use GW recovery and convert all volumes one at a time. The difference though is it doesn't do anything to show higher scores in Quadrant like voodoo does. I'm not technical enough with kernel code to say why not.
[Fascinate Android Development] djp952:
Voodoo Lagfix tweaks some additional parameters about the file system at boot time that causes the high Quadrant scores. I'm not preaching one way or the other, but my belief is that the real-world performance of those tweaks doesn't differ enough to notice. That's just been my experience with it, it may not be an accurate belief :D

The GW Kernel supports init.d scripts as of a couple versions ago, I think it would be pretty easy to add those tweaks at some point to see what people think using that method. Voodoo Lagfix replaces the entire init process with a series of scripts that do all the cool stuff up front before launching the standard init, so the end result might not be exactly the same.

The main reason I never went full Voodoo with this isn't really the filesystem tweaks, it's the automatic conversions and all those up-front scripts that get executed. It's all cooked into the kernel image and can't be disabled. You can stop the EXT4 conversion by putting a file on the SDCARD though. Not saying it does bad things, it's just not my cup of tea. The first time I swapped my SDCARD and then auto-converted my device to EXT4 because that file was missing on the new card really bugged me. None of the old AMEND update-zip files out at the time could handle EXT4 and I really had no clue what I was doing anyway, so it put me in an unhappy place. Coupled with the data wipe bug ClockworkMod had at the same time, I spent a good two days fighting with Force Closes and all kinds of issues. None of the issues were actually caused by Voodoo Lagfix but it still left me very sour to the concept of just up and converting somebody's device like that.

Anyway, that's why :) Sorry I don't have a "Convert Device" option in my recovery, I really should. I will also have a go at the EXT4 FS tweaks Voodoo uses to see if they can be optionally put into init.d scripts and can add information on how to do that if it works OK :D
[Fascinate Android Development] djp952:
Back to the battery charge topic :cool:

I completed another two rounds of testing and at least on my device, the stock EH03 kernel does not do any kind of trickle charge or automatic recharge. The battery meter does stick at 100%, this is from a lack of an event being generated by the kernel to tell the ROM to update it. When you unplug the phone from charger, that event is generated and the meter will update to the correct position (From 100% to 54% in the longest test).

This can be confirmed/denied for other devices by using the Spare Parts Battery Information tool. Rather than reading the %, check the voltage. 4176mV or higher is considered "full" (according to the kernel code). 3554mV is considered "dead". Everything inbetween these values gives you an approximate percentage. So, if one were to charge fully and check Spare Parts you should see a value above 4100mV. Leave the phone plugged in and do things that drain the battery. The voltage value in Spare Parts will continue to drop and will never actually start charging again, even though the % will continue to say 100%. Caution: the voltage will fluctuate up and down depending on what you're doing, so the longer test you perform the better. After the voltage gets down to say 3750mV or less, pull the phone off charger. The battery meter will suddenly drop well below 95%, 3750mV is probably somewhere around 65%, but your value may vary.

If this is not the case for your device and you can really see the voltage drop and then recharge all the way back to 4100mV or more, please let me know, I'd be interested to see if there is a way to determine how that is working since the stock kernel code doesn't appear to allow for it at all.

For GW Kernel, I will attempt to come up with a quieter way to get it to recharge. The current method I used simulates you pulling the cable out and plugging it back in if the battery falls below 95%, which causes the tone/vibrate to occur.
[Fascinate Android Development] sfobrien:
Thanks for all your testing. I too had the trickle charge issue on stock EH03 and Superclean as well. Loaded the KGB 12/12 trickle kernel and now when I unplug I'm always at 95%. Without it it would drop, the lowest I had was 70% after an all night charge with the phone off.
[Fascinate Android Development] notoriousB:
I haven't done any extensive testing like you have, but with prior EI20 based kernels w/o the trickle hack I would get what you describe - it was sitting at 100% while on the charger, but unplug and shortly thereafter it would drop to 85 or below (sometimes way below). With the stock EH03 kernel I do not have this happen, come off at 100% and it gradually decreases from there like it should. I use my phone heavily all day for work, pretty much from the moment it comes off the charger, corporate email push and multiple con calls, so if it weren't charged fully I'd know ASAP. Weird. No big deal about quieting it (to me anyway), I just disable the charger sound.

No worries about quadrant scores I could care less about benchmarks myself. The EXT4 conversion does seem to help real world performance and that's why I run it.

Thanks for all you do!
[Fascinate Android Development] AuroEdge:
1d 0h 38m 52s and at 37% battery using 2.4.2. I would have to say that the deep sleep code may have an effect. I do not use JuiceDefender and have not installed any crazy tweaks or scripts. Could it be that I don't need to carry around a charger anymore?
[Fascinate Android Development] atomD21:
I am very happy to see the EH03 based kernel finally drop! Flashed it yesterday and immediately noticed an improvement over stock. Thank you for what you do!
[Fascinate Android Development] Hymizzle:
Anyway to have a mod to remove the annoying screen capture?
[Fascinate Android Development] Shakes The AssClown:
I was thinking the same thing. My screen capture goes off like crazy.
[Fascinate Android Development] djp952:
Sure thing guys. I've been playing with Ice Cream Sandwich today, trying to get ready to be brave enough to flash my Nexus with something built by my hands <shudders in fear> but this request as well as a couple others I have received recently are pretty easy and I should be able to get them out to you soon (perhaps even tomorrow).

I've had the Screen Capture app go nuts on me a couple times as well, are you having a problem where pressing the power button all by itself is taking a capture? That's what I see from time to time. Usually just waiting for the phone to sleep again solves it for me.
[Fascinate Android Development] djp952:
GeeWiz 2.4 Remove Screen Capture Service (EDIFY update-zip):

This update removes the Screen Capture Service from the base ROM

- Compatible with GeeWiz 2.3 - 2.4.2

http://www.mediafire.com/file/srr2hti8jmaoiai/geewiz-2.4-removescreencapture-01012012.zip

MD5: 5df5aa07b68014a322496f69f5fc8559
[Fascinate Android Development] AmanteNJ:
I guess the google map bug is still there ... been freezing on me and need to do a reset just to get the phone back.
[Fascinate Android Development] scarfman4:
Whenever I have the screen capture issue I just press one of the soft keys, usually the Back key and it stops. Still it's good to have a patch to take it out. I usually rename the file thru terminal emulator instead of deleting it so I can put it back if I ever need it.

Just my $.02 worth.
[Fascinate Android Development] scarfman4:
I'm having a couple of issues that I'm not sure if it's a result of this rom, kernel or neither. First issue is I've had several times recently where data won't download; it will show the green uplink arrow but never the orange downlink arrow. Usually when this happens I either switch off data or go into airplane mode then back and it's fixed. This happened again last night so instead I waited until the morning, and it was working again for a couple of minutes then it started happening again.

The other thing is my ambient light sensor is acting flaky. My screen will go from a lower brightness to full bright for a few seconds then back again or vice-versa, sometimes repeatedly. I ended up turning off auto brightness.

Has anyone else been experiencing this with 2.4 or the 2.4.2 kernel?
[Fascinate Android Development] JJ5150:
Hey happy 2012 guys,

just want to say great work on this, and maybe possibly ask again for the froyo notification bar with the blue battery. I'd setting for just the blue battery, but i was thinking if it was possible to get even the froyo status bar also, with the bigger sdcard icon and bigger 3G bars and whathaveyou. only cuz m eyes are shot. need glasses every year it seems just to see these tiny things.

if not, no biggy.

thanks again. Mike.. great product!!!!

Also, I heard the Fascinate has a forward facing camera... and that the SuperClean 3v05 Rom enables it. Does GeeWiz do the same... Can i really use Skype and video chat on this phone? is it even possible for GeeWiz to do the same thing as SC3? Cuz I've tried SC3 and prefer GeeWiz... Just curious.
[Fascinate Android Development] scarfman4:
It just happened to me again, three hours since the last time. So I just rolled back to 2.4 kernel to see if it makes a difference.

EDIT: it didn't help my ambient sensor problem.
[Fascinate Android Development] luke949:
The fascinate does not have a front camera.
[Fascinate Android Development] JJ5150:
So this is a hoax then? shoot man.. i was all excited. :rolleyes:
[Fascinate Android Development] myersw:
Is there an accurate battery mode that shows percent left for this rom? --bill
[Fascinate Android Development] scarfman4:
No but you can extract the framework-res.apk from the Rom, upload it to UOT kitchen and make your own.

http://uot.dakra.lt/
[Fascinate Android Development] mystycs:
I odined the full wipe with the atlas pit file and it keeps going into the recovery tools even if i flashed the rom too. Why do i keep enterting the the recovery tools section how can i just go into the room? It keeps going back even if i exit it
[Fascinate Android Development] Wolfkmann:
Use this link for an accurate battery mod. It works for me with no problems.

http://xdaforums.com/showthread.php?t=1199528
[Fascinate Android Development] djp952:
Both of these are really familiar problems to me, both mine and my wife's Fascinate have had these issues from day one. I personally haven't seen the data issue since the ED05 modem came out, but my wife still does (EH03 stock). As far as the ambient light thing .. all the time! I don't think these are unique problems, per se, but they could be things that other folks have fixed and I didn't :(

No worries bud, sorry it took as long as it did, I actually made it last night but it failed miserably and I had to correct a dumb mistake:

GeeWiz 2.4 Stock Battery Meter (EDIFY update-zip):

This update replaces the AOSP batter meter and graphics with the original EH03 Froyo-style meter and graphics

- Compatible with GeeWiz 2.3 - 2.4.2

http://www.mediafire.com/file/6mzpqxxibd5g03p/geewiz-2.4-stockbatterymeter-01022012.zip

MD5: bdfa87105b319fd7a94800566ab3103e

Not yet, but I keep saying "someday". I still haven't found one I think fits the theme, but I'm resigned to just picking one and running with it. Do you guys like the sbrissen one used in GeeWiz Froyo? It's a horizontal dark blue battery meter rather than the vertical green one. Wolfkmann's link above is one a lot of people like as well :D

I've heard of this before (can't find it though, I could swear it wasn't that long ago); I believe the problem was that the partition table was still a little wack-a-do.

Are you coming from an MTD ROM (CyanogenMod/MIUI?) If so, my best suggestion right now would be to follow the directions to go back to EH03 stock, there is a link to nitsuj17's thread about that in the first post here. Once stock is working, it should be a much easier process, and one that doesn't require the .pit file.
[Fascinate Android Development] mystycs:
I came straight from stock and if i try without a pit file it doesnt work... Maybe i should try flashing the stock then doing it? Because i came off a stock that has never been tampered with.

---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------

Do i do repartition? for Odin?

---------- Post added at 12:58 AM ---------- Previous post was at 12:52 AM ----------

Fixed the issue it seems i was choosing repartition....

---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------

I installed this rom through odin but it says im running 2.3.5 on the about system status. Is this an issue?
[Fascinate Android Development] djp952:
What version of ODIN are you using? 1.3 or a newer one? I've never had to use the .pit file myself, I thought that was only necessary if the default partitions where wacked by an MTD setup. A stock phone shouldn't need repartitioning. If you need ODIN version 1.3, I have a .zip file with it and the Samsung drivers here:

http://www.mediafire.com/file/5yq8m8770f77wmq/odin-for-fascinate.zip

I definitely recommend trying the full stock EH03 ODIN and making sure that works before moving forward on anything custom. That ODIN file contains more than mine does, it also includes the bootloaders and the param.lfs files. I intentionally omit those files from mine since any mistake there can brick the device (been there, done that, hope to never do it again!)

The best part about trying full stock EH03 is that we can get a lot more people to assist with solving the problem. Takes the customization out the equation.

Oh, what recovery are you seeing? Are you getting the stock (blue text) recovery or the custom (green text) recovery? if it's blue, something's definitely not working right with ODIN. If that's the case, you could try just the GeeWiz Recovery ODIN to see if we can at least get you into a custom recovery. If you are getting the green GeeWiz recovery, we can use ADB to try and further diagnose the issue.
[Fascinate Android Development] mystycs:
I fixed it the issue was i was selecting re-paritition and using a pit file and it funked it up. Its all good now. Though im having one small issue. It says im running 2.3.5 in about system is this fine? I thought it shoudl say 2.4.2
[Fascinate Android Development] djp952:
LOL, fixed it too fast for me, previous post seems silly :) Glad it worked! :D

2.3.5 is the correct android version for EH03. You should see:

Firmware Revision: 2.3.5

Baseband Version: S:i500.04 V.EH03

Kernel Version: 2.6.35.7

Build Number: SCH-I500.EH03
[Fascinate Android Development] mystycs:
Ah okay thats strange cause the xda post said 2.4.2 haha. So then i have this rom installed and good to go i assume

---------- Post added at 02:03 AM ---------- Previous post was at 01:21 AM ----------

For some reason when i plug my phone into the USB it doesnt notice my SD card or ask my to connect to USB storage? Why is this how can i fix this?
[Fascinate Android Development] AuroEdge:
I was having the same issue on my MacBook. Sometimes the USB connect option would show up on the phone. Sometimes it wouldn't
[Fascinate Android Development] mystycs:
Yeah I have windows and I can't see my files on my phone now it doesn't ask to connect usb storage
[Fascinate Android Development] mystycs:
For some rason its not working for me. I cant see my files or anything or even have the option to connect usb