yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
I was finally able to restore my laptop*, and I have all the files again! I'll try to get those put up tonight. I didn't necessarily need to get it working as a computer again to get the files, it's mainly so I can do GeeWiz 2.9 without wrecking my Jelly Bean environment.

(* - Duh, it was x64 and I was trying to run it as a VM on a machine that doesn't support full virtualization. Restore to a blank VM on a real computer and it came right up - what an idiot! LOL).
[Fascinate Android Development] taz1458:
Will 2.9 be Ics or jb?
[Fascinate Android Development] djp952:
> 2.9 is a refresh of GeeWiz Gingerbread that back-ports some stuff I did for the Jelly Bean "Media" ROM/Kernel. Haven't started on it yet. The main idea is to provide extra control over the kernel and make the Fascinate Dock work the way I did it there, if possible.

> 3.0, should it exist, will be Jelly Bean. Started on it, need to integrate some serious changes from TeamHacksung/Cyanogenmod to get the 3G radio working. Not promising this will ever actually come to pass, but the lack of service to test roadblock has been overcome thanks to a timely PM I received :)
[Fascinate Android Development] djp952:
I've fixed the links to all the "Extras" on the main page. I put them in a new "GeeWiz 2.9" folder on MediaFire, so it's unlikely I will be stupid enough to delete them again on everyone. Please let me know if any are broken or the MD5s don't match, I spot-tested 5 of them and they seem OK.

To quote my favorite software at work when it crashes ... "Sorry for the inconvenient."
[Fascinate Android Development] djp952:
I finally tried this today (very addicting, thank you for that - lol). I didn't run into much lag, but I did get some. Temple Run does seem to use a lot of memory, but that didn't look like the cause, the big problem I saw was CPU usage. I was pegging near 80% on Temple Run, so any time another process wanted to do something in the background, that's when I think I saw the lag.

I can free up a couple megabytes of memory, but I don't think it's worth the risk of screwing with the systems I screwed with for Jelly Bean "Media" ROM, as it may cause problems with things that already work (camera, video recording, JPEG decoding etc). It wouldn't amount to much and I don't think it would change anything. My RAM was indeed full with Temple Run running, but not to the point where it was swapping out critical OS stuff. It took up a little more than 50% of the total RAM.

Now, I can't make their application use less CPU, but I am adding a 1.2GHz overclock setting for the (I keep saying this) "Final" Gingerbread GeeWiz that may be enough to push it back into the realm of playable. I see in their comments on Play Store that this game has problems on lots of devices, especially Galaxy S devices ;)

One interesting comment I saw was to use Airplane Mode. I tried that and it didn't change the CPU usage of the application at all, but with Airplane Mode on, there are a lot less things trying to do their work in the background, which could also free up enough resources to make it more playable.

Sorry :crying: In the end this one looks like a case where the developer of the game needs to do a better job with their code.
[Fascinate Android Development] lord dredd:
No worries mate.

Temple run is totally awesome on my n7, so thats where I play it

Regards for the awesome work.
[Fascinate Android Development] djp952:
OK gang, I've "broken ground" on 2.9 and got the apps updated and most of the applicable kernel features back-ported. Here's my plan, let me know if you are OK with this as a feature set:

Completed:

> Update applications (done)

> Back-port 1.1GHz and 1.2GHz overclock options (done)

> Back-port Interactive/InteractiveX/SmartAssV2 governors (done)

> Back-port adjustable battery SOC and recharge points (done)

> Investigate "Temple Run" lag (done; but not something I believe I can do anything about)

In Progress:

> Create application to control all available custom kernel settings, very likely to end up as part of SpareParts

> Try to add an additional lower step for auto-brightness

This may end up with a fairly quick turn-around unless I get more ambitious about it. I really want to back-port all the work I did to make the dock actually useful, but that would break, or at minimum confuse, the Samsung applications. I think that feature is best left in the AOSP world, I'm afraid. I'm kinda scared of adding undervolt support, but I do recognize that it's something pretty much everyone wants so we'll see what happens there.

Is there anything else we need to keep the ol' Fascinates cooking along on Gingerbread for a while longer? I know I missed a lot of discussion points since April, so as long as it's not completely crazy or run a risk of breaking other things, I'm game to give it a shot.
[Fascinate Android Development] djp952:
Did research on what it would take to add a step to auto-brightness. As it turns out, the crappy closed-source Samsung HAL only has 4 steps:

6 lux (dark room)

5000 lux

9000 lux

15000 lux (bright sunshine)

These four values are mapped into a screen brightness from 0 to 255:

6 lux --> 32

5000 lux --> 116 (about 50%)

9000 lux --> 177

15000 lux --> 253 (100%)

So, what I could do here is remap the brightness values, but I cannot add a new one. The values Samsung chose are fairly uniform, the 5000 lux is a bit high and the 9000 a bit low, but close enough. We're stuck with 4 levels on TouchWiz ROMs.

One thing I might be able to do is have a kernel tweak that alters the data. It won't change the 4 steps in and of themselves, but it could be done in such a way to keep the screen somewhat dim or keep the screen somewhat bright. For example, let's say I have a "Bright" option. By artificially increasing the lux value across the board, the screen will tend to stay brighter. Conversely, by artificially decreasing the lux the screen will tend to stay darker.

I'll try whatever you guys want, but right now I think the best I can do is the "Brighter/Darker" option in the kernel. Regardless, I'm glad you asked since I have a better handle on how this sensor works and I can go back and smooth out the auto-brightness in the Jelly Bean version (where I can add as many steps as I want -- go AOSP!)
[Fascinate Android Development] djp952:
GeeWiz 2.9 - ANNIVERSARY EDITION

I am very pleased to announce the release of GeeWiz 2.9 for the Verizon Fascinate. This release takes place exactly one year after GeeWiz 2.0 was released back on September 27, 2011. GeeWiz 2.9 is a long overdue refresh of the baseline, and has incorporated a handful of new Kernel features that were developed for the Jelly Bean-based "GeeWiz Media 3.0".

The most notable new feature is the addition of an extra, "GW Kernel Settings". If you use the GeeWiz 2.9 Kernel, this extra will allow you to control all of the custom settings that are available in it, without needing to hack around with an init.d script or using other such means.

> The complete change-log is available in Post #3 of this thread

> Details on the new GW Kernel Settings app will become available in Post #4 of this thread when I can update it

> Downloads for GeeWiz 2.9 are available in Post #1 of this thread

As always, I would like to thank everyone that has tried GeeWiz in the past year, and I am constantly flattered by the support that still remains active to this day. I'm glad to have been part of your lives for a small time, and I hope that it has been a positive experience for you! (Oh, and if I screwed something up with this release after my 5-month hiatus, please let me know and I promise to fix it!!)

GEEWIZ 2.9

==========

- Updated Google Drive to v1.1.4.12

- Updated Gmail to v2.3.6

- Updated Google Play Books to v2.6.30

- Updated Google Play Music to v4.3.609.436083

- Updated Google Play Store to v3.8.17

- Updated Google+ to v3.1.1.32879387

- Updated Google Maps to v6.12.0

- Updated Street View to v1.8.1.0

- Updated Superuser to v3.1.3

- Updated Superuser su binary to v3.1.1

- Updated Translate to v2.5

- Updated YouTube to v4.1.23

[MOD] Add AtlasParts ("GW Kernel Settings") application to control kernel settings (extra; not mainline)

[KERNEL] Add Interactive/InteractiveX/SmartAssV2 Governors

[KERNEL] Add 1.1GHz/1.2GHz overclock support

[KERNEL] Add configurable battery SOC/Recharge point
[Fascinate Android Development] JJ5150:
woohoo :good:

can I just update the kernel with 2.8.1 or do I have to get 2.9 full wipe?
[Fascinate Android Development] djp952:
Heh, it just occurred to me that the spiffy new Kernel Settings doesn't automatically load the applied settings on boot. Oops. It does (or should) when you open it, but that's not very handy. See, I used my new code, which is integrated into Android 4.1, so it can receive a BOOT COMPLETED message. This app cannot and I have to do something different.

I'll work on that, shouldn't be too hard. Won't need a ROM/kernel update, just a new version of that application.

Please feel free to download and play with it anyway, it won't hurt anything, but when you reboot you'll need to go back in and reapply your settings (regardless of what the app tells you). For example, if you want 1.2GHz overclock, after a reboot go back in and re-select 1.2GHz overclock, even though it will report that as active.

Sorry folks. Not really a Java guy.
[Fascinate Android Development] djp952:
Turns out a normal app can receive the boot notification after all, making it rather easy to fix the GW Kernel Settings app. A new version has been uploaded to replace the original, you can flash it on top of the old one without needing to clear data on it or anything like that.

I left the code in there that reapplies the settings when you launch the app as well, that way it can't really get out of sync with other applications that may have changed something. For example, if you use SetCPU to overclock to 1.2GHz, but GW Kernel Settings is set for 1.0GHz, when you launch the app it will be reset to 1.0GHz.

Anyway, that should be that. Always something. Every release is tainted in some way :)
[Fascinate Android Development] djp952:
Those of you that are waiting for me to release some form of Jelly Bean ROM that has voice/data .... I'm getting closer! I have voice, I have data. I also have about 500 really weird problems to solve still. And by weird I mean REALLY weird. This thing is ridiculously screwed up on all fronts, I've missed something basic here. LOL.

Screenie attached. Thank the CyanogenMod team, it's their radio interface ;)
[Fascinate Android Development] hkleiner:
Thanks for this. Rom. I Odined back to EH03 Verizon, and then applied the full Odin 2.9.

I can't get root access for anything though. What am I missing?

________________________________

Easy as 3.1415926536
[Fascinate Android Development] phxshadow:
Thanks Dj for all the development on GeeWiz. I upgraded my line and am moving on from the fassy.

Thanks for making my time with the fassy a pleasant one.
[Fascinate Android Development] JJ5150:
Dj, I loaded the new 2.9 kernel on 2.8.1 and 2.9 & lost BLM support... just a heads up.

Sent from my fabulous fascinate GeeWizing all over the place
[Fascinate Android Development] rxwookie:
Big thank you for the overclock and underclock settings!

Took me a minute to realize I also needed to seperately download the app you created... :rolleyes:

Not sure what the different governors do, though. Anyone got any help or a link to some help?

That being said, wow! notable difference in games!
[Fascinate Android Development] djp952:
Hmmm.. is Superuser able to update itself? That typically solves it if it can ... see what happens if you do this:

- Force Stop and then Clear Data on Superuser in Settings/Apps

- Go into Superuser

- Swipe to the INFO panel on the left

- Tap where it says "tap to check for updates" in the middle

- Hit the Update button when it's ready

What it should do is download a new copy of "su" and install it, prompting you for root along the way. If this doesn't happen and you see something like "cannot obtain root" in the on-screen log, let me know. We can use ADB to fix it.

Sorry about this. I haven't seen it happen on the Gingerbread GeeWiz, but I have had it happen to me a couple times on my Nexus.
[Fascinate Android Development] djp952:
Oh bummer. I wonder if something from the JellyBean kernel managed to sneak it's way in here (read: merged something I shouldn't have). I messed with BLN on that platform, I bet that's what I did. I'll check it out and get it fixed ASAP!
[Fascinate Android Development] swapnilss:
Downloaded and installed the new rom and kernel on day 1. It's much better than the earlier 2.8. The phone is benchmarking definitely better using the app to overclock to 1200 mhz. Thanks dj for all the time you put in for us. I am definitely waiting for the full tw jb rom from you.

I recently flashed the kgb kernel replacing the geewiz one. On this, I can overclock to 1440 safely by compromising little on stability. I'm using cpu tuner app and using smartass virtual governer. The phone now benchmarks much more than before.

Though for stability nothing can come close to geewiz rom and kernel.
[Fascinate Android Development] djp952:
Here's a pretty good link: http://androidforums.com/xperia-mini-all-things-root/513426-android-cpu-governors-explained.html

The ones that seem to work the best on our hardware IMO are OnDemand (the default in GW), Interactive(X) and SmartAssV2. I don't think the sleep frequency enhancements in SmartAssV2 really do much for us, since our phone has deep sleep. Well, if BLN gets working again (doh), it could actually help there since my BLN implementation holds a wakelock, and therefore burns battery.

Each governor essentially does the same thing, just differently. They all strive to balance performance against power consumption. Our hummingbird CPU is very fast at changing speeds, so something like OnDemand seems to give the most "snappy" experience while still ramping down to save battery. Interactive(X) and SmartAssV2 are variations on that theme, they will ramp up and ramp down the CPU clock at different rates, and hold clock speeds for different lengths of time. Performance and PowerSave are polar opposites, but each will hold the CPU at either the maximum or minimum speed indefinitely. Conservative is like PowerSave, but it will ramp up. I don't think you'd like Conservative :)
[Fascinate Android Development] djp952:
Oh hey, wait .... this is GW 2.x. BLN is *off* by default on this platform. Did you install BLN Control and enable it? You can also temporarily enable it to test using ADB (goes away on reboot).

> adb shell

# cd /sys/class/misc/backlightnotification

# cat enabled

If you get back "0", BLN is disabled. To temp-enable ...

# echo 1 > enabled

# cat enabled

Now should come back with "1"

Regardless, I'll flash GW 2.9 tonight and have a look for ya! :fingers-crossed: I could also add the basic on/off toggle to the kernel settings application, I didn't do that because I didn't want to step on neldar's (he who wrote the BLN driver in GW) feet.
[Fascinate Android Development] QuattroMechanic:
any idea where i can find the REVISED** Eh03 radio or modem?
[Fascinate Android Development] scarfman4:
What is the "revised" modem?
[Fascinate Android Development] lolreconlol:
I'm getting sick of JB, I'm gonna try this.
[Fascinate Android Development] scarfman4:
Can't blame you. For all the progress JB has made it still has a ways to go. I keep going back and forth between GeeWiz and AOKP M6 ICS depending on what I want at the time.
[Fascinate Android Development] QuattroMechanic:
No root!! Help
[Fascinate Android Development] Crawshayi:
What don't you guys like about JB? Not being critical here, just curious. Personally I think JB is miles ahead of previous android versions. I understand with certain roms there will be bugs and glitches to deal with, but I'm mainly on CM10 with rock solid stability
[Fascinate Android Development] djp952:
That makes two ... wth did I do wrong? I still can't replicate this one, but it is a newer version of Superuser/su in there. Might have to patch to revert back to what was in 2.8.1. Latest isn't always greatest!

EDIT: suggestion deleted, I think I know what I did wrong .. hold tight folks, if I'm right I can fix it with a patch tonight for ya
[Fascinate Android Development] QuattroMechanic:
I have faith in ya bro, Btw when I flashed the 2.9 rom and kernel then everything was set up I noticed that if I'm using the 3g network I have internet but not when I'm using wifi. Even with dolphin browser no luck but its fine with opera??? So anyways I odin'd back to stock eh03 and odin'd the 2.9 package everything is way snappier and works. But still no root :(
[Fascinate Android Development] djp952:
Folks having trouble with Superuser/root access on GeeWiz 2.9 ... would you mind testing this patch?

GeeWiz 2.9 Superuser Patch

- Reinstalls Superuser and the su binary with the permissions required by the newer versions

- NOTE: Will clear data on Superuser, any saved settings will be lost

http://www.mediafire.com/file/uhzjddr5ya9zdd0/geewiz-2.9-superuser-patch-10062012.zip

MD5: 480fa47cc45026fcd9657294c304f9fe
​

I think the problem was the GROUP permission of the su binary. The owner/group should be set to ROOT:ROOT, I had left it the way it was in earlier versions, which is ROOT:SHELL. Superuser itself was reporting the permissions as incorrect, the user/group was red in the info panel. This will turn it green, clear data on it, and hopefully solve the problems!

Please let me know. If this works I can generate a GeeWiz 2.9.1 this weekend that incorporates the new permissions.
[Fascinate Android Development] djp952:
I swear this is the most peculiar device ever created by man. You should see the silliness I've been running into trying to get a 3g-enabled Jelly Bean set up for this thing. About 25% of the time after flashing, it won't even boot. Flash the EXACT SAME THING and it's fine. About 50% of the time I have ridiculous settings after wiping data .. wipe data again, no worries.

Sending you a PM about the possible root fix above ... <crosses fingers>
[Fascinate Android Development] scarfman4:
I have nothing against it; I just haven't had a good experience with it yet. I've tried out CM10 myself starting with the 9/30 nightly. It ran great and some of the bugs in ICS were gone. I then tried using the built-in CM update to load 10/1 nightly. I then lost my Google account to sync with and couldn't readd it. So I factory reset and reloaded 10/1 nightly again. My wife called me a couple of hours later and the call was so choppy I couldn't understand a word she was saying and I was in an area with strong signal. I found another place where I had strong signal, called her back and it was just as bad. I quickly flashed back to CM9 and called her back (still in the same location) and the call was fine. So I've been reluctant to try CM10 again.

I've been wanting to try out AOKP JB build 4 but with the reports of issues with the ringtones I'm waiting until they get farther along with it. Maybe when they hit Milestone 1 I'll give it a shot.

Just my 2¢ worth.
[Fascinate Android Development] QuattroMechanic:
Yea its a bugger, I just lost internet browser again on wifi, everything else gets internet though like xda and Facebook etc...
[Fascinate Android Development] djp952:
What kind of ringtone issues do they have? Just today I fixed the ringtone problems with my "GeeWiz 3.0" Jelly Bean project, maybe it's the same problem? My ROM wasn't playing the ringtone AT ALL. nothing, nada, zilch, zip. The issue was the "HAL" (Hardware Abstraction Layer) for audio, it came from the Nexus S and was set up for special audio playback modes that the Fascinate doesn't have.

If the problem was absolutely no ringtone at all, but it would still vibrate and give you the answer screen, the changes I made may help them and I can contact them about it. Hey, some stuff from GeeWiz Media 3.x has made it's way into Cyanogenmod <proud father> now thanks to jt1134's help, if I can assist with the ringtone issue for AOKP, I could probably die happy tomorrow. LOL :)
[Fascinate Android Development] djp952:
That's just weird. I got absolutely nuthin' there :) Here at djp952's house, there is a jerk across the street that likes to use the non-approved Wifi Channels and has some type of amplified antenna. He ends up killing EVERYONE ELSE in the process. Last year I built myself a nice high-gain 2.4GHz antenna and nuked the **** out of him for a month since he was messing with my Roku, and YOU DON'T MESS WITH MY HD MOVIES!! It subsided for a while, but he's seemingly back and I have to kick his RF butt once again.

Point is ... could this be coincidental? I swear I didn't change anything related to Wifi in GW 2.9 :) It was more of an "app refresh" than anything else....
[Fascinate Android Development] QuattroMechanic:
Maybe the browser? Any ideas
[Fascinate Android Development] djp952:
Oh, I almost forgot ... BLN.

I couldn't find any problems with BLN in GeeWiz 2.9. I'm hoping that the problems people have had are because the note that BLN is *disabled* by default in GeeWiz 2.x was lost somewhere about 40-45 pages ago :)

In GeeWiz 2.x, you need to download "BLN Control" (Free version works; paid version has cool "blink" option) from the Google Play Store to enable BLN. I didn't write the kernel driver that I used in GW 2.x, and it's only fair that I push people to neldar's (BLN author) apps to control it.
[Fascinate Android Development] QuattroMechanic:
I did a factory reset and haven't reinstalled any apps and wifi in the browser is working. ALSO the su zip did not fix the root issue
[Fascinate Android Development] djp952:
If you go into Superuser and swipe to the info page to the left, are all the indicators where it says "su binary 3.1.1 (17)" green underneath?

Also, what do you get if you "tap to check for updates" and try to Update it? Does it hang at "Gaining Root Access"? That's the point where it should prompt you, or if it's gone through once already pop up the "blah has been granted root permissions" toast message.

This is just weird. I guess I'll redo the not-so-fix with the old files and see if that helps. Damn.
[Fascinate Android Development] QuattroMechanic:
Still no luck on root but I have a Q. When the phone is about to die (dead batt.) And shut off if I turn it back on it says 40% ???? I wiped batt stats 2 times last week on full charges and still occurring
[Fascinate Android Development] djp952:
The battery on the Fascinate is a little "whack" on how it works. It doesn't do anything with the battery stats, that's a misconception. The initial report as to how much battery life there is comes from a hardware "State of Charge" value that I don't believe is controlled by the kernel at all. Back when I added the auto-recharge I spent DAYS messing with things like voltage and whatnot and it just fought me until I caved and used the reported SOC value. It's not entirely accurate as to the values it reports, especially after a reboot, and I think you'd find that the 40% you see isn't real and the battery will drop like a rock at some point.

I'm still trying to figure out the root thing.
[Fascinate Android Development] rxwookie:
Not being difficult, but have you done the following?

1. ODIN back to stock (Verizon's Latest GB Build)

2. ODIN the latest GeeWiz build (kernel, Rom, and Recovery)

3. Flash the Superuser update

Also, did you boot to the bloated, stock and let it settle in for a few minutes before continuing on work the process?

After both ODIN flashes, you definitely need the new superuser update. It fixes a critical permission.

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

As a last resort, you can (after ODIN to stock)

1. ODIN to full-wipe 2.8 and verify you have root access

2. Flash the 2.9 update through the Recovery followed by the superuser update (again in recovery)

3. Reboot

I just tried those specific steps and it worked for me.

Let us know if you get it working or not.

Thanks!