yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Two new EXPERIMENTAL kernels have been posted to the experimental/incremental section of this thread:

GeeWiz 2.1.3 (EXPERIMENTAL) Kernel - 11.14.2011

Base: SCH-I500 EH09 linux-2.6.35.7

- Fixes battery auto-recharge problem; will start charging again at 94% like Froyo (djp952)

NOTE: ALTERNATE VERSION 2.1.3a with recharge point set to 90% below

http://www.mediafire.com/?12uhw5ovvzpamm7

MD5: 3dae179f89c648c5b77eb8873b622358

GeeWiz 2.1.3a (EXPERIMENTAL) Kernel - 11.14.2011

Base: SCH-I500 EH09 linux-2.6.35.7

- Fixes battery auto-recharge problem; will start charging again at 89% (djp952)

NOTE: ALTERNATE VERSION 2.1.3 with recharge point set to 95% above

http://www.mediafire.com/?t42kaadwfarv2bb

MD5: b29f49d9f002899836bef108bf726872

CODE CHANGES: https://github.com/djp952/sch-i500-gingerbread/commit/6e57e04018aa3b17453371aa434791f3c814377b

Both of these intend to solve the same problem with slightly different recharge points. As we all have learned, the EH09 kernel will disconnect the battery from the charger when it's full, but will never reconnect it. Froyo kernels reconnected the battery at 95%, but for now I have also provided a version that should drain until the battery is under 90% (2.1.3a) as well. For those watching github, the version that was checked in is the 95% version.

I have not done extensive testing on this change, as it's not the easiest thing in the world to set up and execute, but I had good success with it last night and today, and cleaned out all the debug messages and extra logging that I had in there before building and posting it for you guys.

Feedback on this change would be greatly appreciated. Not only if it works properly, but what you think about if I should default the recharge point to 95% or 90% as well. Many thanks to AuroEdge for providing this feedback already! I'm torn myself on what's better; I like waking up with an almost full battery, but our Fascinates are aging and we could be shortening their life even more by constantly recharging them for a couple % points on the meter. Ideally, I will take the time to learn how to pass parameters from an init.d script into the kernel and that way everyone can set it to their preferred point :D For now, I'm just happy to have finally made some progress here!

edit: neat side-effect ... if you have your volume on, you'll actually hear the reconnect since the implementation tricks the phone into thinking you disconnected/reconnected the USB cable. Apps/Widgets that report battery % should also change from 100% to 95%/90% at that time; they will unfortunately still read 100% from the time of full charge until the reconnect, maybe that's something I can fix as well.
[Fascinate Android Development] mising:
I installed the 90% kernel last night and woke up this morning to 94%!!

Previously, depending on the charge present when I put it on the dock, I would wake up to anywhere from 30% to 70%. Awesome, great work!
[Fascinate Android Development] crakedparrot:
I'll jump in on this one, I have the speaker issue as well :(
[Fascinate Android Development] AuroEdge:
The speaker issue is a bit of an odd one. Let's say I am in the middle of a call and select speaker. The microphone will no longer work (or is so quiet that my voice can't be heard). However, if I am plugged into the headphone jack and then initiate a call, the microphone seems to work!

On a side note Shazam doesn't seem to work consistently. Not sure if this is related to the same issue. I'm betting you noticed something else too. When my phone fully charges off the wall charger I can disconnect the plug from the outlet and the phone doesn't notice. If I plug it back in and remove the usb cord then the screen wakes up. Note this was on the 2.1.2 kernel

EDIT: Another thought. When the phone is plugged in the kernel does NOT go into sleep mode correct? So, when the phone charges all the way up to 100% and starts discharging the battery will the lowest step be deep sleep or 100 MHz?
[Fascinate Android Development] briguyy:
Ever since flashing 2.1.3 Experimental Kernel my phone is making the sound of plugging in the charging cable to the phone every so often even though the cable is already plugged in with the phone charged...is it supposed to do that?

Thanks
[Fascinate Android Development] AuroEdge:
edit:

neat side-effect ... if you have your volume on, you'll actually hear the reconnect since the implementation tricks the phone into thinking you disconnected/reconnected the USB cable

. Apps/Widgets that report battery % should also change from 100% to 95%/90% at that time; they will unfortunately still read 100% from the time of full charge until the reconnect, maybe that's something I can fix as well.
[Fascinate Android Development] djp952:
I have the same speakerphone issue as you guys and am looking into a fix. I think it's probably related to the changes made for the in-call volume, but I'll poke around and see if anyone else had this and managed to fix it. Those changes were above my head to begin with, I'm not real confident I can fix this one on my own. :o

edit: I confirmed this is a problem with the in-call volume fix; flashing my original 2.1 kernel fixed it. I think I see why, but have to run some tests.
[Fascinate Android Development] AmanteNJ:
Loving this ROM/Kernel for a couple of weeks. My phone started acting weird and lag like a robot dance so i decided to go back to stock and maybe go back to 1.1.1, now i cant use my non OEM battery cause other kernel doesn't support it unlike Geewiz. I also needed that speaker phone feature so bad while driving but an earphone should be able to fix it

I am going to wait it out until i flash another ROM/Kernel.
[Fascinate Android Development] djp952:
Sorry :( I haven't had any lag issues myself in the past month or so running GeeWiz 2.1 ROM, and I couldn't even begin to guess as to why that happened. If there are any specifics you can give me, I would be happy to try to replicate the problem and see if there is anything I can do to fix it. If not, I totally understand, it's both frustrating and annoying to run into these kind of problems.

Flashing back to stock, you should be able to use the Froyo 1.x GeeWiz kernel (and I think just about any ED05-based kernel) if you'd like to try that to alleviate the OEM battery problem. The GeeWiz 1.x kernel has no dependency on the ROM other than assuming it's ED05-based and should work OK for you with stock. It could be worth a try to see if it fits your needs, and flash back the ED05 kernel if not. I'm 99.99% sure nothing bad would happen just trying the stock ROM/GeeWiz kernel combination (gotta have that .01% just in case!)

I apologize for not having a lot of time lately to work on things like the speakerphone issue. I hope to do better for you guys again soon.

Thanks for giving it a try, I am truly sorry it didn't work out for you :(
[Fascinate Android Development] djp952:
New experimental KERNEL has been posted:

GeeWiz 2.1.4 (EXPERIMENTAL) Kernel - 11.15.2011

Base: SCH-I500 EH09 linux-2.6.35.7

- Attempts to fix problem with speakerphone microphone not working; please let me know if this affects other in-call volume fixes

- NOTE: This is a 95% auto-recharge kernel like v2.1.3. I'm still trying to figure out if 95% or 90% is better and 95% is what I checked in.

http://www.mediafire.com/file/vataxfeunm5gfiq/geewiz-2.1.4-kernel-11152011.zip

MD5: 7ec368ad4ad6eacc1bb9587c33d38481

A quick set of tests seems to indicate to me that the speakerphone-mode microphone works again and this didn't impact the other in-call volume mods to the EH09 kernel. I really need some feedback from you guys to know if that is the case or not. All I know right now is that when I call my "real" phone from my "dev" phone I can hear myself talk on speakerphone mode again :) I won't actually check this code change into GitHub until I get some feedback.

edit: this seems to work pretty well, and I did tweak it a bit and check the change into GitHub just now (+1dB from uploaded 2.1.4 kernel above). There aren't a lot of people I can call at 11:00pm other than myself, so I do still need some feedback to make sure this didn't wreck any of the other in-call volume mod changes. I hope this can become the "2.2 kernel" along with the necessary updates to the ROM built-in apps and I can post a useful update package again. :D Based on download counts from mediafire, I am leaning towards the "90%" auto-recharge version of the kernel for v2.2, as that seems to be the vastly more popular option. If you have arguments to favor 95% over 90%, please reply to this thread. I want to baseline the option that makes the most people happy. My personal preference is trending towards the 90% version as well. Thanks!!
[Fascinate Android Development] AmanteNJ:
Lol no need to say sorry ... the lag might be from apps and not the kernel. Next time i will just download the apps again instead of restoring it from TB probably that is where i am getting all the lag. Most of the time when i try to puzzle unlock, after moving the puzzle it will stay there for a 2-3 seconds before going to the home screen. Some instances where the screen will be black and only the soft keys will light up. Never happened with Geewiz 1.1.1

Glad to know that you have a fix for the speaker phone
[Fascinate Android Development] AuroEdge:
There's got to be a way to emulate the restore app function from AOSP. Maybe even an app that downloads a list of apps you've saved
[Fascinate Android Development] laureanop:
+1 for 95%. Highers is betters

tsm res1.2, TKSGB 11-14, lag fix
[Fascinate Android Development] djp952:
Not familiar with this application. If it's part of the available source (not everything is), I'd be happy to look into it. I can fire up the emulator and have a look, would you mind telling me how you get into this application (is it a separate app, is it part of Settings, etc)? Never really played with straight AOSP much :)
[Fascinate Android Development] djp952:
Question for the folks having Force Closes reboot the phone ... what applications are you using that are doing this? I haven't seen this myself and installed the Development tools apk tonight which has a few different types of force closes you can simulate and none of them caused the device to reboot.

Is this a prevalent issue for everyone, or is it only happening to a few of you guys/gals? Is the application crashing a root application (the dev tools aren't, maybe that's why it doesn't reboot)?
[Fascinate Android Development] Wolfkmann:
Is anyone else having this problem? When I reboot my phone it locks up halfway through the reboot. I have to press and hold the power button and volume up button simultaneously to reboot the reboot.
[Fascinate Android Development] AuroEdge:
It's a part of the settings under privacy I believe. There's an option to restore apps and an option to store backups on Google's servers. I think
[Fascinate Android Development] mising:
This is what I use:

https://market.android.com/details?...GwsMSwyLDEsImNvbS5wdW5zb2Z0d2FyZS5iYWNrdXAiXQ..

or another app I have not tried yet:

https://market.android.com/details?...m5ldC56ZW1uYS5hbmRyb2lkLmFwcGxpc3RiYWNrdXAiXQ..

Both of these create a list with links to the market to re-download individually or in a batch.
[Fascinate Android Development] AuroEdge:
App List Backup is exactly what I need. I'm almost surprised something like this hasn't made its way into a ROM since Titanium Backup is not recommended to the masses
[Fascinate Android Development] AuroEdge:
djp952 are you excited about EH03?
[Fascinate Android Development] crakedparrot:
Has anyone figured out how to stop the screen from randomly turning on, or why it is happening?
[Fascinate Android Development] sendan:
The new gingerbread leak seems to fix it.

Sent from my Samsung Fascinate
[Fascinate Android Development] djp952:
That as well as looking at the EI20 kernel source, which is available. Probably nothing much changed there, but ANY fixes are good fixes!

I have a feeling I'm going to be spending all my free time this weekend diffing a great deal of code :D

edit: EH03 feels like taking a small step backwards, but it is a lot more "right" for what I've been trying to do here all along. Well, provided the old blue battery status bar icons get replaced, anyway. It would be a good bit of work to redo everything from ED05 to EH03 again, and of course there's all that nasty bing/vzw integration that we all love so much. I'll have to think about it ... ideally, we can marry all the good stuff from both, but if they are as far apart in code as they seem to be on the surface, that may be a tall order.

As far as the EI20 kernel, it seems to address issues with the video recording functions and has a different/new modem interface. The former seems like an easy decision to include, the latter worries me a bit - I'll have to see what they did that was so different, I'm concerned it's yet another way to try and thwart us, but then again it could solve all our problems with having to swap MEIDs all the time! We'll see!!

Dunno. Please feel free to let me know what you guys would prefer. EH03 based = more work but likely more stable in the long run. EI20 based = less work but will likely continue to be glitchy since it was hacked into working in the first place :)
[Fascinate Android Development] bmeek:
here's my vote for "less glitchy" :-).

I've kept trying various gb roms and kept going back to ed05 geewiz for stability's sake... if ed05 didn't have the annoying habit of turning on the backlights with every screen touch, I would be lurking here far less...

I odined the eh03 leak and flashed sc3 over that last night (leaving the stock eh03 kernel and modem in place), and so far I'm feeling good about the operational stability. as you say, it aligns with your original goals for geewiz.

regarding the backlights, once one of them is pressed, they seem to stay on until the screen goes off. but on the bright side [sic], they stay off after the screen is unlocked until one of the backlight keys are pressed again (makes reading news and kindle content in the dark tolerable :-).

anyway, I look forward to your eh03 enhancements. thanks for all you do...
[Fascinate Android Development] atomD21:
DJP, FWIW, I think EH03 and GW are a great match. EH03 is completely stable on a lot of people's phones (more than EH09 or EI20 were...), and in the long run would save you some work trying to shoehorn things in. As for Bing, it is there but so easy to ditch entirely. With root, you delete it and the search button is mapped to Google, and the browser lets you choose Google as the search engine now. Much less intrusive than before. All that said, thanks for your hard work for the Fassy! GW1.2 was my daily driver for a loooong time and is the most stable Rom I had ever used. Your efforts are appreciated!
[Fascinate Android Development] djp952:
GeeWiz 2.2 has been posted.

This update is a rollup of all the "experimental" kernel changes made to 2.1, includes a merge from the official Samsung EI20 kernel and has an application update to the ROM (see changelog for details).

Unfortunately, testing of the ODIN-based "fullwipe" and "kernel/rom" packages failed, so links to those have not been posted until I can determine the issue and resolve it. I apologize for the inconvenience. I hope to have those links up in the next 24 hours. Links to ODIN kernel-only and recovery-only have been provided as they passed my testing.

GeeWiz 2.2 is likely to be to the last ACG EI20-based package I put out, since a Verizon-specific leak (EH03) has emerged. I also have a long-standing promise to the Froyo guys to update that GeeWiz that I have to take care of before I come back to Gingerbread. Promises are promises.

I will post back when the missing ODIN files have been fixed and posted.

Thanks again to all of you for your support and feedback with this ROM/Kernel development effort!! :D
[Fascinate Android Development] djp952:
The issues with the GeeWiz 2.2 ODIN-based files that include the SYSTEM volume appear to have been resolved, and links have been posted to the first post in this thread. Thanks for your patience, I try to test everything I post to a reasonable extent and those ODIN files that included the SYSTEM volume just weren't working right at first.

Please let me know if you run into any issues installing, especially with the ODIN files, and I will do my best to support and/or fix any problems you encounter :D
[Fascinate Android Development] Wolfkmann:
Just flashed the 2.2 rom/kernel can't get google maps navigation to do anything but force close. Tried flashing the gpsd permissions fix.zip but didn't seem to help. I am losing track of what I read where, does this update fix the random wakeup, or the trickle charge issue?
[Fascinate Android Development] djp952:
I believe the problem with Maps/Navigation stems from upgrading it via a ROM flash. I don't have any problems here, but I also wipe my dev phone quite often, including the SDCARD, and numerous times while testing ROMs. The Maps/Nav issue has come up before, much like the Adobe Flash issues (which I no longer feel bad about removing since it's a dead product now!). What has worked for others would be to clear data/cache on Maps, then remove the APK using a root file explorer or ADB shell. Install from the Market and see if that makes a difference.

I try to keep a decent list of changes in the first few posts, but I did have a lot of test kernels floating around between 2.1 and 2.2. Nothing in 2.2 solves the random wakeup (sorry!), but trickle charge should work for you ... based on what became an overwhelming ratio of downloads, I went with the 95% recharge point. The same trick I had is still there, it will act like you unplugged and replugged the charger, so you'll get a tone/vibrate when it kicks off the charger again. Still looking for a safe way to avoid that annoyance without messing up it actually working :)

Back to Maps, I will do what I suggested above, then backup my DATA volume. Reinstall Maps from Market and back DATA up again to see if it's doing something different with permissions or files on DATA when it's installed outside of the ROM. I tried that with Adobe and it didn't pan out, but I would like to be able to at least explain why some people have issues and others don't.
[Fascinate Android Development] briguyy:
As far as the google maps navigation goes i had the same problem but i fixed it by shutting down the phone removing battery and charger, letting phone sit for 3 minutes then put battery back in boot up and then everything worked fine. Hope this works for you as well.
[Fascinate Android Development] Wolfkmann:
Thanks, but unfortunately this didn't work. I am also now getting random reboots. I flashed the new version rather than odin, because I don't have the spare time to reinstall everything. I am liking the trickle charge fix, but not at the cost of random reboots and no GPS. I am afraid I may have to flash back to the earlier version.
[Fascinate Android Development] djp952:
Sorry your experience hasn't been very postive :( I wish I could duplicate your issues here and provide some sort of fix for you. I'm a little concerned that flashing back to the previous version will yield the same results since I can't account for the problem being with the ROM/Kernel.

You can use the updated kernel with the previous ROM if you'd like to, that way you get the trickle charge feature. I would flash back to how you had it first and make sure everything is working right again first, then try flashing the updated kernel (link in the first couple posts somewhere for just the kernel). If that ends up causing you problems, just let me know the 2.1 kernel is still on mediafire and can be flashed separately as well.

I hate Google Maps! I wish I knew what the hell it's problem is. Flash I get, there was a library file that should have been included in the ROM (I think, it seems to work on the EH03 ROM I'm building), Maps is just being bothersome. Maybe I can use the PREINSTALL volume like VzW did in the 2.x software rather than cooking it into the SYSTEM. :confused:
[Fascinate Android Development] tiger505:
Thanks for the great ROM and all the hard work. Flashed with kernel and so far very impressed. High Quadrant score (not sure if that really matters) and all my 100+ programs all function after TB. I'm not sure what is going on with maps however. Google Nav is one the main features of the phone for me and it's very important to my work. I thought maybe I had it fixed this time but sure enough my Fasc froze after about 10 minutes guiding me through the traffic. Could not even do the power off thing, had to remove battery and reboot...dang. I'm finding this to be the case with all the newer ROM's and trying various kernels combinations. I wish there were a fix. By the way my GPS locks in 2 to 5 seconds so that's not the problem. I know you and other ROM servants are trying to figure this out. I so do not want to have to get a Razr or Nexus as the fasc is one great phone.

Again thanks for all the work. I could not find the donate button as I'd like to buy you a latte or 2. :)
[Fascinate Android Development] djp952:
Thanks!! No donations here my friend, this is all pro bono :) It lets me still sleep at night even when things don't work right! LOL.

My current inkling is that the problem may stem from us "fixing" the multitouch issue with the newer Samsung ROMs. We've all been adding a certain permission file that Samsung appears to have forgotten, which is what allows you to rotate the maps in Google Maps without resorting to the semi-lame method used by non-distinct multitouch devices. That said, I don't think that Samsung really "forgot" this file and continues to do so after so long, and they changed the touchscreen driver in Gingerbread (was "Melfas", now "Cypress"), so it's plausible that Samsung is indeed smarter than the rest of us and did it on purpose.

If you want to try life without that file to see what happens, use a root explorer of some kind and move out the /system/etc/permission/android.hardware.touchscreen.multitouch.distinct.xml file to somewhere and reboot. You will have to use a different gesture to rotate in Google Maps, but I'm very curious to find out if this solves the screen/freezing issues. The non-distinct gesture is to swipe two side-by-side fingers horizontally left or right rather than rotating two fingers around the screen.

I've been working on an EH03 GeeWiz variant the past couple days, and I'm sad to say that Google Maps still screws with it, whether it's cooked in or installed from the Market. Stock kernel / custom kernel doesn't matter, bad things will ultimately happen. I haven't tried removing the file mentioned above yet, but I think I will tomorrow even if just to satisfy my own curiosity!
[Fascinate Android Development] Wolfkmann:
I renamed the above mentioned file by adding .old to the end of the file name, no change. Maps still locks followed by a reboot.
[Fascinate Android Development] AuroEdge:
I tell you what djp the users here sure are happy that you are releasing what you do. You make great stuff and if something isn't quite right you acknowledge it. We're not entitled to your efforts but please keep doing what you're doing