yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Just wanted to chime in on the Jelly Bean version status (which I have been playing with instead of doing what I'm supposed to be doing again - LOL). For the past week or so, I've had this seemingly insurmountable issue with it and I'm going to shelf it again for a bit. The problem I'm having is that the device will reboot on resume and I cannot for the life of me get any clue as to why. I think the radio is rebooting it since neither the kernel nor android are telling me squat. It was working fairly well, too, so I'm kinda bummed. There were other problems still, but I'm not sure why I would spend any time on them if the phone won't stay on for more than 2 minutes without rebooting :silly:

So, for now, a couple things have been fixed/changed that will work their way into that not-so-popular "GeeWiz Media" setup I have, and I will try to carve out more time to continue to look at this Gingerbread version of the setup :cowboy:

I know a few people were really looking forward to it, even if it wasn't fancy. You never know, I might learn some new trick that allows me to diagnose what the heck is going on!

edit (10/10): it seems that it may be the service I was using. Even GW Media is rebooting now for no reason, so I've cleared the EFS on the thing and so far so good. Perhaps the EFS was corrupt from trying to activate off of the stock ROM or something. ????
[Fascinate Android Development] hkleiner:
Just left it at 2.8. Didn't feel like messing with it more, since it's just my son's play phone.

Thanks though.

________________________________

Easy as 3.1415926536
[Fascinate Android Development] djp952:
For those having issues with Superuser/root, can you provide the following for me?

> Clear Data on Superuser

> Attach with ADB

> From ADB: logcat -c

(This clears the log to make it smaller)

> On the Device, do something that would require root and doesn't work

> From ADB: logcat > /sdcard/logcat.txt

This will appear to hang, it's just waiting. Give it 5-10 seconds and then press CTRL+C to stop it

Attach or PM me the /sdcard/logcat.txt file. Suggest attaching it so others can help if I'm not around when you post it :)

Thanks!
[Fascinate Android Development] djp952:
Good news from the Jelly Bean world ... it took almost 2 weeks, but I have finally found the root cause of the nasty reboot issue with that ROM and it's been fixed. Development is back on! Still much to do, but hopefully I will have SMS/MMS receive fixed tonight. The short list for a public beta is 1) In-call volume ramp is all kinds of messed up 2) Wifi tethering doesn't work 3) Wifi doesn't work at all unless you reboot ... um ... there is a laundry list a mile long, but I think those are the three things that I think NEED to be fixed before making it public. Oh wait, a fourth ... I want to make the "fullwipe" do EXT4 by default rather than RFS, it makes such a huge difference on this setup. I won't automatically enforce EXT4 for SYSTEM or at all for update-zips, that would still be left as an exercise for the reader :) PS - it's already been upgraded to the latest Android 4.1.2, as has GeeWiz Media (not uploaded yet).

No logcats about the GeeWiz 2.9 Superuser problems yet ... I really need those!!

edit: cool, just received an SMS for the first time. God Bless Cyanogenmod and their 100% public code to steal, er, "leverage". MMS still hopelessly broken, but it's not bed time quite yet.
[Fascinate Android Development] Bayside:
I ran into the root problem after I used Edify to install the 2.9 System and 2.9 Kernel files. I was previously on 2.8.1 which was installed via Odin. The SU patch was installed from Edify after I discovered the problem, but it did NOT resolve the issue.

This morning I took the time to start from scratch and try to get the logcats requested. Unfortunately, I cannot duplicate the problem now. Nice for me,but not to help troubleshoot the problem. Here are my steps to get to where I am now:

1. Used Odin and the Atlas 2.2 pit to restore my phone to stock EH03.

2. Booted into stock EH03 and let the phone do its thing to start up the system, etc.

3. Once it was working fully, I shut it down and came up in Download mode to sync with Odin again.

4. Used Odin and no pit file to install GW 2.9

5. Booted into GW 2.9 and let it run its setup.

6. When setup was complete, I booted to recovery to install the SU patch.

7. Rebooted the phone to run Titanium Backup to test root access.

8. No joy. Titanium Backup hung right at the root access request command.

9. Triggered the phone's USB Debug to "on" and shutdown the phone.

10. Turn back on the phone and went to Manage Applications to do the Clear Data just for Superuser.

11. Plugged in my phone into my PC via usb and activated ADB for the logcat data.

12. Activated Titanium Backup and this time it sailed through the SU request. No hang.

13. Tried various other tasks with no issues. Root access appears to be working correctly.

So, I apologize that I could not generate a logcat for you. My only guess is that the combination of fresh install from Odin, SU patch install AND the Clear Data on Superuser is required to allow for proper root access on GW 2.9.

..B..
[Fascinate Android Development] A-L31:
Sorry cannot get the log cat

As soon i flash the superuser update/patch the super user works fine without clearing the data. in superuser there's no red word. i'm using super su and remove superuser :D. Conclusion : i think the patch is working

Report : The Gallery App just blank and then force close. "Application Gallery (in process.com.cooliris.media) is not responding.

Edit : i clearing the app through app management no go. but i clear the data with titanium backup and then open its open ......
[Fascinate Android Development] djp952:
http://xdaforums.com/showthread.php?t=1945448

Jelly Bean GeeWiz!

Hopefully it doesn't suck :)
[Fascinate Android Development] Kaptinkrunk:
Huh does data work? I always love trying new things

Fascinating AOKP Jelly Bean Build 5 Devil 1.7.5...
[Fascinate Android Development] djp952:
Of course data works -- I totally stole it from Cyanogenmod! - LOL GeeWiz 3 (3G) is having it's share of growing pains right now, which was to be expected I think, but I am working through them. It's not nearly as stable as GeeWiz 2.x has been, but I was at least smart enough to call it "Beta".

It doesn't (yet?) hold a candle to AOKP or Cyanogenmod, but I think it's off to a pretty decent start. There are more bugs/defects than I was expecting, but I am trying to work them as efficiently as I can. If you need something that works 100% properly, now is not the time for "teh GeeWiz 3". Hopefully I can rescind that statement in the very near future :silly:

edit: Making a 3G-enabled Jelly Bean ROM was never my original intention, but I wanted to try and make it happen for all of you guys that have been using GW 2 for so long and have been so nice to me along the way. The entire project may ultimately fall on its face, but at minimum I will know I gave it my best shot :)
[Fascinate Android Development] Kaptinkrunk:
Much appreciated I'll prolly play with it but testing has been a pain lately lol

Fascinating AOKP Jelly Bean Oct 22...
[Fascinate Android Development] livinsacrfice:
Enjoying the rom on my showcase.

Regarding tethering:

-default tether app: doesn't work (works as router, but 3g is disabled while running the hotspot)

-foxfi: works well.

-wireless tether for root users: having trouble getting right setting to do master mode (i like their keepalive function--more reliable for playing video games from tether)

also, is there a way to hide the clock and battery icon from notification bar? i know tsm parts can do it, or manual editing of systemui, but I don't have any experience editing that.
[Fascinate Android Development] scarfman4:
I know this thread isn't monitored much anymore, but the link for the Kernel App is no longer valid. Anyone have a mirror?
[Fascinate Android Development] rxwookie:
Sent you a pm. I'll also try to get it uploaded to a mirror sometime in the next 24 hours.
[Fascinate Android Development] scarfman4:
OK my bad. The OP has the one dated 9/28 but post 3 has the one dated 9/27, which is the one that doesn't work.

I'm downloading the 9/28 version now. Thanks.
[Fascinate Android Development] scarfman4:
Since I hosed my phone trying out one of the new 4.2 ROMs, I decided to roll back to GeeWiz for a while. I had the same problem with 2.9 breaking root and the patch not helping.

I rolled back to 2.8.1 with the 2.9 kernel and it works fine. I updated Superuser to version 3.1.3 from the playstore, and it still works fine. However I noticed that updating Superuser didn't update su binary; it still had version 3.0.3.2 built in.

I then tried to update through the Superuser app to the latest binary 3.1.1 like GW 2.9 has, and every time it fails. Here's what the su binary updater shows:

Downloading mainfest... okay!

Parsing manifest... okay!

Latest version = 3.1.1

Checking installed version = 3.0.3.2

Unpacking sutools... okay!

Checking current install path... /system/xbin/su

Downloading new binary... okay!

Gaining root access... okay!

Remounting /system as rw... okay!

Copying su to /system... okay!

Changing su file mode to 06755... okay!

Making sure new su works... fail!

This happens every time.

Could it be the su binary 3.1.1 that is preloaded in GW 2.9 is what's breaking root? Can we make a patch for GW 2.9 that can be flashed to return su binary back to 3.0.3.2?
[Fascinate Android Development] rxwookie:
Try ODIN back to 2.8.1.and verify root access. Then flash 2.9 in recovery, and finally apply the fix/patch. Check root access.

That's what worked for me.
[Fascinate Android Development] scarfman4:
Makes sense, but the reason I was throwing this out is to try to fix 2.9 without having to dirty flash from 2.8.1.

Also until this is figured out, shouldn't the ODIN for full 2.9 be taken down and replaced with the full 2.8.1 ODIN? then anyone who wants to try it can try your method.
[Fascinate Android Development] rxwookie:
I dunno. It seems like most people have success just ODIN'ing 2.9. Lost root seems to be a hit and miss thing.

I agree though, it would be nice to have an upload off 2.8.1 on that page just to be safe.
[Fascinate Android Development] scarfman4:
I did an ODIN directly from unrooted EH03 using the full wipe complete package and root was broken. I wonder if it's only breaking if the phone didn't have root prior to installing 2.9.

I'll play around with different combinations tonight.
[Fascinate Android Development] scarfman4:
OK after some trial and error here's what I've tested with, all using GW 2.8 recovery and 2.9 kernel:

TEST 1: factory reset 2.8.1 through GW recovery, flashed GW 2.9 system through recovery, rebooted, root still broken, rebooted, cleared cache & dalvik & flashed 2.9 superuser patch, rebooted & root still broken

TEST 2: factory reset thru GW recovery, flashed back to 2.8.1 system, rebooted, then rebooted into recovery, flashed 2.9 without factory reset, rebooted, root still broken, flashed 2.9 superuser patch, rebooted & root still broken

TEST 3: shut down & connected via ODIN, tried to flash GW 2.9 system only (not full package so didn't wipe), rebooted, root still broke, flashed 2.9 superuser patch, root still broke

TEST 4: made my own GW 2.9 superuser patch which is identical to djp952's patch but the su binary file reverts to the previous version 3.0.3.2 from GW 2.8.1, rebooted & root now works!

So I think my theory that su binary 3.1.1 is breaking root stands. It must not like Gingerbread (or at least Samsung's crappy version, lol). I don't have a clue why for some users like rxwookie it will work correctly and others (like me) it won't.

If anyone wants to give my updated SuperUser patch a try, which I named "geewiz-2.9-superuser-patch-11262012.zip", you can download it here:

http://db.tt/5jirUhvw

If this fixes root for anyone please post so we can ask djp952 to make it available from the OP. Thanks.
[Fascinate Android Development] rxwookie:
I know you're not doubting me... but just so you can see, here are two screen shots showing the ROM version and the successful Superuser 3.1.1.

I have no idea why it works this way for me and not for you.

Thank you for uploading your patch so others who are stuck can get root back. I downloaded myself just in case something happens and I lose root on a ROM flash.
[Fascinate Android Development] scarfman4:
I'm curious. What theme are you using to change your colors on your About screens?
[Fascinate Android Development] rxwookie:
Sorry, that would be my screen shot utility screwing up the colors (roll-eyes). I WISH I could change the colors to orange... that would be sweet.

The only custom interface I'm running is Holo Launcher (free edition) which mimics android 4.0 interface... but with a few extra options.

Sorry again for the confusion. I just didn't have the time to re-color it to the original blue last night.
[Fascinate Android Development] eggyjla74:
The patch "geewiz-2.9-superuser-patch-11262012.zip" can only be patched using GW Recovery? I tried with CwM and the install failed.
[Fascinate Android Development] neozen21:
That's the first thing I checked... All animatins in Spare parts and Settings are all turned on. Still no CRT-off animation...

And I know config_animateScreenLights is set to false.. I pulled my framework-res.apk and decompiled it to check...

Any ideas?

---------- Post added at 08:48 AM ---------- Previous post was at 08:45 AM ----------

I had this issue too. All you need to do to fix it is to delete the FlashPlayer.apk from /system/app/ then download it again from Android Market. That worked for me...
[Fascinate Android Development] QuattroMechanic:
I had this issue too. All you need to do to fix it is to delete the FlashPlayer.apk from /system/app/ then download it again from Android Market. That worked for me...[/QUOTE]

Worked!
[Fascinate Android Development] QuattroMechanic:
I'm confused, I scored a 946 on quadrant???? Seems very lagy. Geewiz 2.0 10/12. Tksgb 10/10.
[Fascinate Android Development] mzrdisi:
I think this is a known issue across all eh09 releases.

It's hit and miss too. Doesn't happen all the time
[Fascinate Android Development] QuattroMechanic:
Yesterday it was like 1800 or more
[Fascinate Android Development] nitsuj17:
rfs always scored in the 950-1100 range on quadrant (not that it matters)

surprisingly 2.3.5 didnt bring a dramatic increase in performance...perhaps the official vzw builds will

the droid charge (again fwiw) with one of the more recent gb leaks (theyve had like 10 geez) rfs performance jumped from 1000-1200 to 1500+
[Fascinate Android Development] sendan:
I just applied CRT-off animation to my own framework-res and it works fine...check permissions maybe? Otherwise I could give you a flashable zip...

And make sure transition speeds in Spare Parts are all normal.
[Fascinate Android Development] djp952:
Howdy all ... sorry I was away from my PC all day. Lots of responses!!

The link in the first post looks OK to me, I tried it from a few different computers. I do occasionally remove older versions from mediafire, though. Let me know if your problems persist, I can upload it somewhere else temporarily and give you a link.

Absolutely. I'm finishing my testing on "2.1" (tired of calling it beta, regardless of remaining flaws), and I intend to upload a separate kernel this time. The 2.1 kernel also has a built-in busybox installed to /xbin as well as including a recovery system, should you flash it as recovery.bin :D

Are you using a stock Samsung battery or an aftermarket one? I didn't really look to see if the EH09 USCC kernel has the stupid OEM battery code in it, but if it does that would prevent aftermarket batteries from charging, even in OFF (LPM) mode. Could you try comradesven's TKSGB kernel linked to in the first post and see if that makes a difference? If so, I will contact him and will request use of his battery mod. Let me know.

I'm going to just remove FlashPlayer.apk from the 2.1 ROM in light of all the problems until we can collectively work out why it doesn't work for everyone. It would also allow people to install older versions than 11 if they want, which would be good I think.

GeeWiz won't blow your mind when you look at benchmarks. This GB version is even slower than the Froyo one as well, which is mildly annoying. 946 actually sounds about right to me if you're running RFS. I would think the TKSGB kernel would help, but the real trick to killing Quadrant is voodoo lagfix. I will be posting a recovery with 2.1 that will allow you to convert to EXT4 if you want, but my kernel doesn't currently add the lagfix tweaks. TKSGB in conjunction with EXT4 may yield results more to your satisfaction. The ROM itself doesn't have a lot to do with the benchmarks, your performance will likely come from the kernel.

Yup! I found that you have to have "Window Animations" set to Normal to see the CRT animation. "Transition Animations" can still be set to Fast, and that's something I recommend. It makes everything feel more snappy!

.....

I think that's touching on most of the stuff I missed today as best I can. I'm still readying 2.1, I had a couple problems on my real phone last night that I cannot duplicate but still wanted to take another couple runs through my surprise feature (not really a surprise if you read this whole post, it's up there!) to make sure all the things I left in it won't do anything bad. Check for updated apps, remove FlashPlayer.apk, make the ODIN files, etc. It's only 8:30 I might be able to make it happen ... lol. It won't be perfect, but there are an infinite amount of version numbers available!! :D
[Fascinate Android Development] QuattroMechanic:
just flashed the tksgb 10/12 and my quadrant score is 1653 !!!!

its fast and looks great, I am satisfied

Oh, does the "Shot vxix" work well with my setup? Geewiz 10/12 TKSGB 10/12
[Fascinate Android Development] QuattroMechanic:
Ok I flashed "Shot vxix" anyway because I'm a risk taker and it seems that my phone is taking it well, Quadrant score is up to 1770.
[Fascinate Android Development] mzrdisi:
In an attempt to fix the Google Maps issue, regarding multi touch. I flashed the fix permissions zip from the PW thread and it worked, but you loose root.
[Fascinate Android Development] djp952:
Wait another hour or so ... fixed without losing Root in 2.1 :D
[Fascinate Android Development] mzrdisi:
I await for amazing things. Or I'll pass out in bed and wake up to amazing things
[Fascinate Android Development] djp952:
GeeWiz 2.1 has been posted.

While it's not perfect and still has a few to-dos, I've been running GeeWiz 2 on my "real" phone for a few days now and feel that it was ready to taken out of BETA status. Unlike the Froyo GeeWiz "1.0", this is still somewhat of a work in progress that will undoubtedly have updates made to it.

Notable changes from 2.0 BETA to 2.1:

- Adobe Flash Player APK was removed due to numerous reports of problems; please download Flash from the Android Market

- CRT screen-off animation has been enabled (thank you nitsuj17) ... you will have to set "Window Animations" to "Normal" in SpareParts to use it

- Google Maps multitouch permissions have been fixed

- The kernel now properly supports EXT4 volumes; the bug it had was fixed

... and the big reveal ...

- GeeWiz Recovery has been introduced and included by default as part of the "full" ODIN package to ensure that people coming from ED05 stock have a valid upgrade path without ClockworkMod. It has been scaled back from my private version to only the options/commands that are known to work, but I will continue to update it and continue to add all of the things I took out back into it.

I will be updating the second post of this thread with information about this new feature

and what it is capable of doing as time allows, but I think it's all pretty self-explanatory for advanced users out of the box. The main benefit of it over CWM right now is the "Manage Volumes" menu, where you can backup/restore individual volumes AND convert them to EXT4 or RFS. I was never a fan of the way CWM/Voodoo handled this, I prefer to know what's happening to my device and didn't want any kind of automatic conversion.

GeeWiz Recovery is a completely optional thing, if you don't like it or it's too limited right now, you are free to flash whatever RECOVERY volume you want! ClockworkMod is a much more advanced tool than GeeWiz Recovery, I highly recommend it.

Thank you all for your support and feedback thus far with this "GeeWiz Gingerbread" effort of mine. It's truly appreciated, and I hope to be able to continue to fix/adjust things so that everyone that wants to use it will be happy with it :D This was not as easy as Froyo, and there are undoubtedly still remaining problems that need to be solved.
[Fascinate Android Development] shag_on_e:
You are definitely a creative developer. If this is the beginning I'm stoked to see more. Thank you.

~~~~There is no spoon~~~~
[Fascinate Android Development] lord dredd:
All i can say is Simply awesome work with the latest update, and so many options in the main post to choose from, hats off to you.

Thanks aton mate.

God bless

Regards
[Fascinate Android Development] AuroEdge:
In response to my previous post, I am using a stock Samsung OEM battery. To my knowledge trickle charging is when the phone discharges from 100%-95%, while plugged in, then charges back to 100%. My phone charges to 100% then enters a discharge mode until the phone is unplugged and plugged back in
[Fascinate Android Development] briguyy:
Ive tried all the GB roms and i like this one the most..mainly because for some eason it gives me the best GPS performance. Also im running the stock kernal and im just fine with it...ive tried all of imoseyons and TKSGB but i dont notice any better performance with them. Thanks for the good work!
[Fascinate Android Development] pdubsfc:
Can I flash this in CWM right over PWGB? Thanks!
[Fascinate Android Development] comradesven:
In response to a question about trickle charging you said:

The OEM battery code (hilarously named "VZW_AUTH_CHECK") is present. With SirGatez's patch for Froyo as a model I figured out how to simply bypass the check. Third-party batteries charge fine on TKSGB. However the trickle charging problem keeps being brought up and I've even heard that it is endemic to all Touchwiz GB ROMs. One of the things I've been meaning to do is get trickle charging back, even if it's worse for your battery or whatever. The charge bug happens to me too, on both official and third-party batteries, on EH09 with my kernel. Not all the time like some people are complaining about. That's the other thing I've heard about it. This is one hard bug to reproduce and the proper Galaxy S owners have been dealing with it for some time now apparently *shrug*

That said, I l0l'd a bit, not gonna lie, when you said you might "request" use of my work. It's Linux, for goodness' sake :p

Kudos on the
[Fascinate Android Development] scarfman4:
It would probably work best in GW recovery. I didn't write the install script; i just updated djp952's previous patch.
[Fascinate Android Development] djp952:
scarfman, do you still want to put the patch on the main page? With your permission, I can mirror it on mediafire and link it up. THANK YOU for finding a solution that should work for everyone. The newer su binary has actually caused me problems on my Galaxy Nexus (albeit different ones), too.

I love Superuser and ChainsDD's work, but it may be time to consider switching to that other knock-off version. I figure the least we can do is wait until he makes the 3.2 binary official (I haven't checked in a few days, but it was still a test/beta version last I checked)

Sorry to anyone that has been PMing me, I fell behind ... again ... was killing myself working on the GW 3 audio issues (fixed!). As usual, I probably have some important stuff in there, perhaps even this very topic! lol. I'm bad about that. When I feel my lack of progress may disappoint I seem to just shy away from communication. I'll try to improve upon that!