yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] AuroEdge:
Can you explain this TouchWiz desire on ICS? I was on my Droid and saw that Enyo made a mod for TouchWiz on that platform.
[Fascinate Android Development] JJ5150:
Hey dj, I wonder if it's possible to make an add on that will get rid of the lock screen? I know that there's an app out there but it doesn't work as well is I like it too. And I figured since you've done such a good job thus far... it might be possible... just curios thx
[Fascinate Android Development] Jimi Mack:
Try this...

Go into the Dialer and enter *#83786633 then press the Home key

Go back into the phone dialer and enter *#22745927

Now a box will come up asking for the SPC code. Enter 000000

Press the Hiddenmenu Enable radio button.

Shutdown

*#7594#

This enables you to shut your phone off by long-pressing the power/lock key.

No more pop-up confirmation, it will disable the puzzle/glass unlock screen.
[Fascinate Android Development] uzumaki82:
What do you mean by wakelock?

Also, Is there an easy way to disable to accept notification when toggling GPS? Loving the ROM/kernel combo so far. TSM Res was soft booting on me.
[Fascinate Android Development] JJ5150:
Thanks, it worked. Now how can I reverse it if I need to?
[Fascinate Android Development] Jimi Mack:
Exact same thing.
[Fascinate Android Development] JJ5150:
Roger that ;)
[Fascinate Android Development] rxwookie:
Just had my first problem...

Google Navigation locks up if I initially try to get directions from within that app. Had to reboot phone twice.

Solution (for me): Launch Google Maps and wait for it to locate me. Then get directions and "Navigate". That successfully launches Navigation and the directions are good.

However, for some reason of I start out in Navigation, then choose directions, it locks up on me.

If I go through Maps (after GPS locks) I get no issues?

Thanks!

Sent from my Fascinate running GeeWiz Rom, Kernel, and Recovery
[Fascinate Android Development] scarfman4:
AFAIK this is been an ongoing issue with all TouchWiz GB Rom/kernels. Those based on EH03 seem to be better but not 100%. Doing it the way you described is so far the best solution I've seen.
[Fascinate Android Development] wowser21:
Is there a mod somewhere for a transparent notification bar? I'm having issues viewing notifications from several apps such as ScoreCenter and Google Music. I've searched around but found nothing for 2.6 ( i saw that there was an ICS theme for an older version made by notta).

Thanks.
[Fascinate Android Development] Jimi Mack:
If you can get it to download this will work.

Transparent Status Bar Pulldown

http://xdaforums.com/showthread.php?t=1350621
[Fascinate Android Development] phxshadow:
i found and downloaded gmaps 5.0 apk and have not had a problem since. Before both maps and nav froze on me with 6.2.
[Fascinate Android Development] wowser21:
Thanks. Multiupload is down so i posted in the other thread to see if anyone already has the file.

EDIT: found the file
[Fascinate Android Development] AmanteNJ:
how did you manage to install it?
[Fascinate Android Development] crakedparrot:
I feel so sad... my fav thread has fallen quite for several days.......
[Fascinate Android Development] djp952:
Geez guys I'm sorry :( I was so balls to the walls for like 6-7 months on this and just lost my interest temporarily. I am working on GW 2.7 in between some other stuff. The contract on my dev phone hasn't expired quite yet there will be at least one more iteration!

I haven't abandoned ya. Just hiding in a secure location! Lol.
[Fascinate Android Development] phxshadow:
I know its been quiet here.

---------- Post added at 08:19 AM ---------- Previous post was at 08:17 AM ----------

GW 2.7 :D Glad to see you back.
[Fascinate Android Development] scarfman4:
Well I thought being on GeeWiz solved my hot reboot problems but it's still happening. I do usually try to avoid rebooting my phone until needed, but it was only maybe a couple of days since my last one. Could it be kernel related?

EDIT: I'm switching to KGB to see if it's any better or worse. Will keep everyone posted.
[Fascinate Android Development] crakedparrot:
So anyone seen any good movies lately.... just trying to keep the thread alive. happy Saturday everyone!
[Fascinate Android Development] JJ5150:
While you were away... working on GW 2.7... I decided to kill some time and get married. hahaha

(bump) :D
[Fascinate Android Development] Jimi Mack:
What should we be expecting in 2.7... eagerly. :)
[Fascinate Android Development] phillip_viado:
how come when i odin this rom it goes to the recovery. i rebooted it and battery pull and it goes back to the recovery
[Fascinate Android Development] R187J:
r u coming from stock EH03

I had this problem then i reverted to stock and reflashed and worked like a charm

But now i am having the same problem again

and again and again

i tried reverting back to stock and havent had any such luck :((

when powering phone on it only wants to reboot into recovery and i tried ODINing in a new recovery and it just powers to the new recovery :(

i love this rom but it just doesnt wanna work with me anymore :(( fix plz lmao
[Fascinate Android Development] zanktank:
Flashed the whole package via Odin from an ED05 build 2.2.2 (i think) and EVERYTHING is smoother, less lag, less force-closes, better etc. Can't beleive I waited this long to do it. This will allow me to hang onto this phone just a bit longer.

Still having GPS issues. Tried GPS status, also tried the hidden menu through the dialpad to GPS setup.apk, however it doesn't seem to exist. Every once in awhile I get a GPS lock but it takes 2 minutes minimum. Wondering if its a hardware issue because it was happening on previous rom as well.
[Fascinate Android Development] gorm:
Make sure not to use the pit file and uncheck repartition in Odin when flashing this rom.

Opps, Meant to quote phillip
[Fascinate Android Development] phxshadow:
Try this for your gps it worked well for me. http://xdaforums.com/showthread.php?t=1442032

Mine locks quick now. Before i would have to open and close maps about 5 time to get gps to work.
[Fascinate Android Development] rxwookie:
This is occurring most likely because you have the re-partition box checked in Odin when flashing GeeWiz. The only time you re-partition is when you are going back to stock.

In other words... The boot to recovery loop most often occurs when you are flashing a custom recovery partition AND you try to re-partition all at once.

At this point (boot to recovery loop), however, you will actually need to return to stock, with the re-partition box checked so you get back to a working state... then try re-flashing GeeWiz with that box unchecked.

Let us know if that works.

Sent from my Fascinate running GeeWiz Rom, Kernel, and Recovery
[Fascinate Android Development] lord dredd:
eagerly waiting for 2.7 DJ

hoping you ll get the time soon.

regards
[Fascinate Android Development] rxwookie:
DJ

When you get a moment... can you check the ordering of shortcuts in folders?

I add the icons in the order I want, but they get automatically rearranged... I think by app date added to phone.

Thanks!

Sent from my Fascinate running GeeWiz Rom, Kernel, and Recovery
[Fascinate Android Development] JJ5150:
Make sure you Odin looks like this: [coming from Stock or GeeWiz ROMs]

(Go straight PDA) (No PIT, No Re-Partition, No Auto Reboot)

Hope that helps. :D
[Fascinate Android Development] mighty_markus12:
What govenor and speeds do you recommend? I tried smrtassv2 1200/100 and my wifes phone was acting up. Should i maybe use ondemand 1000/100?
[Fascinate Android Development] JJ5150:
I run 1200/200 ondemand default, and 400/100 sleep. seems to run great for me. Also running ADW Launder Ex... plus AniMod, and Spare parts plus set2Fast.. from the market. That combo runs smooth and fast no problems. Hope that helps.
[Fascinate Android Development] crakedparrot:
Did we ever find a solution for this? No biggie just following up.
[Fascinate Android Development] QuattroMechanic:
Im stuck on 1x, i keep losing 3g and the only way to get it back is if I turn off mobile data and turn it on??? Using this rom and kgb kernel latest of both
[Fascinate Android Development] AmanteNJ:
have you tried flashing a different modem?

Try using GW 2.6 Kernel and ROM see if that will work. I tried KGB before and gave me different results that I did not like. I am using GW 2.6 for the longest time since it was released and didn't find any problems.
[Fascinate Android Development] JJ5150:
I actually had problems with KGB also. I found that 2.6 runs better with it's own kernel. you can't overclock it, but it doesn't need it. just my $.02
[Fascinate Android Development] djp952:
Hello everyone! Sorry I've been away for so long, I really am. I have a LOT to catch up on, 26 Private Messages and countless posts here! I'd give a good excuse if I could think of one, but the reality is I just got myself involved with other things non-XDA and non-Android for a month here and did pretty much ignore everything else again :(

While I haven't caught up yet (I will!), I deleted what I had for "GeeWiz 2.7" and started over tonight. It won't be anything amazing, just a refresh. I seem to have finally gotten a proper kernel-based backlight timer to work without killing the phone every 10 minutes and updated all the canned apps. I still have to update BusyBox to 1.19.4 and add some manner of version number to the Recovery, but I intend to release 2.7 soon, I'm thinking today/tomorrow if the backlight timer kernel changes really work this time. :confused:

I want to thank everyone for keeping this thread and GeeWiz alive while I was gone. To that end, is there anyone that might want to take this over? I'm actually being serious here, when I get back into Android full-swing I really want to work with my Nexus and Android 4.0, and more importantly my contract for the Fascinate is nearing it's end, which would pretty much stop me cold, I promised my wife I wouldn't keep the second line active once the contract is up to save some $$. She wants to go iPhone for some insane reason I can't understand so her Fassy won't be long for this world either :(

I promise to finish 2.7, go through everything I've missed, and do 2.8 or 2.7.1 (whichever is appropriate based on what I read), but I'm close to being out of gas on this particular project. I have gigs and gigs of artifacts I would be able to send along and would certainly take the time to bring somebody up to speed. You would need 1) a passion for this stuff, 2) about 5-6 hours of spare time for each minor release or maybe 20-30 for a major change, 3) an ability to pay for or accept donations to pay for the bandwidth to share and most importantly to me ... 4) won't be a jerk to others. Not that anyone here IS a jerk, of course, it's just that this stuff is supposed to be fun and no matter what you do not everyone will like it, and I would hope that if I turn this over it would be to somebody that is as tolerant as possible and can be OK with getting slammed from time to time (I rate myself as "moderately tolerant", it's not THAT hard to tick me off - LOL) let me know if you're interested, but it will take me a few days to go through all the PMs I already have!

So ... 2.7 coming, but it's nothing to write home about. 2.7.1 or 2.8 coming after that to catch up on requests/concerns/issues as best I can. Looking for somebody that might want to carry the torch for 2.9 and beyond !!
[Fascinate Android Development] lord dredd:
Nice to have you back DJ :)

and its kinna sad that you wont be continuing to develop for the fascinate after 2.7 and may be 2.8 , but then those are practical reasons and personally I am happy that you developed such a great piece in GEEWIZ :)

Thanks a bunch for that again !!

also was wondering if you had the chance to have a look at that SHOWCASE GB release

[ROM] I500USFC19 [19.03.2012][Android 2.3.6]

Do you think there is anything usable in it to be included in 2.7 ?

Thanks

regards
[Fascinate Android Development] djp952:
Certainly worth a look at the Showcase stuff! I'm trying to get 2.7 out ASAP to keep things alive around here, but I'm on it (soon)

2.7 may be delayed anyway, recent versions of Google Navigation , including the new one released today completely STB (poop the bed) with missing resource exceptions and ultimately reboot the phone. Not good, have to figure that one out. Even not including it and just downloading from Market is doing the same thing!

If nobody wants to take GW, I'll keep it alive as long as I have the means to do so, I won't 100% bail out, that would be uncool. Besides, I want to have one final special ROM that disables the CDMA completely so when we're done with our Fascinates they could still be used as Wifi mobile gaming devices or media players!

I'll let you guys know on 2.7, I can't release it with this glaring of a problem. Hopefully it won't take me too long to figure out, I just have to go back to stock and start diffing things until I find the culprit
[Fascinate Android Development] mezster:
This would be much appreciated! :beer:
[Fascinate Android Development] djp952:
GeeWiz 2.7 has been posted. My apologies again for being away for 2 months, and while I know I haven't fully gone through every post/PM yet (I have a cool boot animation given to GeeWiz to share!), I wanted to make sure I got an update out to let everyone know this project hasn't been abandoned. Please check the KNOWN ISSUES below, I wish I had solutions to the problems the newer built-in apps have presented :( Having Navigation fail so miserably most of the time is frustrating at best, if it's as bad as I think it is I will be happy to provide an "extra" that back-dates Maps sufficiently. I can go back as far as what was in GeeWiz 2.3 if necessary.

The "big things" in 2.7 are the 15-second backlight timer in the kernel and opting to go with the EI20 Browser/Launcher by default for the ROM. Everything else is just incremental updates based on the latest app versions available.

I hope my recent extended absence hasn't adversely affected the quality of this release, and if I missed something please let me know and I will do my best to correct it as quickly as possible!

GeeWiz 2.7

March 29, 2012

GeeWiz 2.7 ROM - 3.29.2012

Updated BusyBox to v1.19.4

Updated Google Docs to v1.0.54

Updated Google Maps to v6.5.0

Updated Google Play Books to v1.5.4

Updated Google Play Music to v4.1.513

Updated Google Play Store to v3.5.15

Updated Google+ to v2.4.1.271037

Updated YouTube to v2.4.4

[MOD] Replace EH03 TouchWiz30Launcher with EI20 version (previously was a GeeWiz 'extra')

[MOD] Replace EH03 Browser with EI20 version (previously was a GeeWiz 'extra')

GeeWiz 2.7 Kernel - 3.29.2012

Add a 15-second touchkey backlight timeout (djp952)

GeeWiz 2.7 Recovery - 3.29.2012

Update BusyBox to v1.19.4

Add a 15-second touchkey backlight timeout (djp952)

KNOWN ISSUES

Google Maps Navigation locks up and ultimately reboots the device

This is seemingly a known problem with the Verizon Fascinate and current versions of Google Maps. I've had success with first acquiring a GPS lock with an app like "GPS Status & Toolbox" before launching Navigation, but your mileage may vary. At this time I cannot recommend using Google Maps Navigation on the Verizon Fascinate​

Google Play Store may not show any Applications under "Installed" section

Resolution: Clear Data on Google Play Store and re-launch it. I believe this to be a bug in the latest Store version and since Store auto-updates there doesn't seem to be much I can do about it at the moment. Including an older Store in the ROM and letting it update doesn't seem to make things any better.​
[Fascinate Android Development] lord dredd:
Thanks DJ that was fast :)
[Fascinate Android Development] crakedparrot:
Yahoo! I really like the 15 sec timeout, Upgraded both rom and kernel. will report back after I let it grind for awhile. So far so good.

Thanks DJ!
[Fascinate Android Development] scarfman4:
Is the 15 Sec time-out meaning the backlights wait 15 seconds after you touch them to turn off? That seems like an awful long time. Couldn't it be shorter like maybe 2 or 3 seconds?
[Fascinate Android Development] djp952:
How about I make it configurable? I can do that. I went with 15 secs as a hopeful happy medium, it's half of the stock timeout (if screen timeout is 30 of course)

Would you be OK with support to change via init.d? It would require just a single echo command in a text file. I would provide direction on the main post of course.
[Fascinate Android Development] scarfman4:
I didn't even know there was a 30 second time-out in stock. Probably because my screen goes off after 30 seconds. I'd be ok with instructions to set it manually. I was just asking because a long time ago someone made mods that defaulted it to 2 seconds and kind of miss that. Also KGB defaults it to 1500ms (1.5 seconds) but makes it configurable. Maybe put it up to a vote to see what others think?

Also is there a way to make the incall volume configurable as well?
[Fascinate Android Development] rmtobler:
really really enjoying this rom. I have been on gb miui for a long time and just recently tried out ICS, but experienced too many problems, so I decided to give up on them and go straight for stability. this rom definitely provides a nice blend of stock stability with just enough customized add-ons. THANK YOU!
[Fascinate Android Development] djp952:
I'd like to keep 15 as the default, but I was able to make what seems to be a fully functional change to configure it tonight. Check the next post for the new kernel and let me know if the directions provided are sufficient or if more detail is required.

Yes, but I have to work a little harder on that one. I forgot how I made the changes in the first place and have to remind myself which piece of code changed what :) I remember I was the guy that fixed the speakerphone microphone so at some point I was smart enough to decipher which change went to which device! LOL
[Fascinate Android Development] djp952:
A new experimental GeeWiz kernel (2.7.1) has been posted ...

GEEWIZ EXPERIMENTAL KERNEL 2.7.1 (March 30, 2012)

GeeWiz Kernel 2.7.1 adds the ability to configure the touchkey backlight timeout value to any length of time between 500ms (.5 seconds) and 30000ms (30 seconds). This can be done with an init.d script by echoing the number of milliseconds you want to set the timeout to into /sys/class/sec/t_key/backlight_timeout

GeeWiz 2.7.1 Kernel (EDIFY Update-Zip)

http://www.mediafire.com/file/xkwwgc8x69ghm5l/geewiz-2.7.1-kernel.zip

MD5: e4931219b1bf247909c039bde562ddc4
​

HOW TO CONFIGURE TOUCHKEY BACKLIGHT TIMEOUT (GW KERNEL 2.7.1+)

Mount the SYSTEM volume as read/write [mount -o remount,rw /dev/block/stl9 /system]

Create the directory /system/etc/init.d if it does not already exist [mkdir /system/etc/init.d]

Create a text file called 'touchkey_timeout' in /system/etc/init.d with the following contents (modify the last line to set the timeout value in milliseconds [1000ms = 1s], example sets to 2 seconds:

#!/system/bin/sh
#
# touchkey_timeout
#
# Configures the GeeWiz kernel touchkey backlight timeout value.
# The kernel defaults to 15000 milliseconds (15 seconds), but this
# value can be set as low as 500 milliseconds (.5 seconds) or as
# high as 30000 milliseconds (30 seconds)
#
# The device attribute to change is:
#	/sys/class/sec/t_key/backlight_timeout
#

# Example: Set timeout to 2000 milliseconds (2 seconds)
echo 2000 > /sys/class/sec/t_key/backlight_timeout

Set the permissions on this new file to 0755 [chmod /system/etc/init.d/touchkey_timeout 0755]

Test the change by running /system/xbin/run-parts /system/etc/init.d, then press a touchkey on the device (even if the backlight is currently on) and time how long it takes for the touchkey backlight to timeout. They should turn off relatively close to the amount of time you set in the script.

Reboot the device
[Fascinate Android Development] djp952:
Thank YOU for trying it out and sticking around while I was Missing in Action for almost 2 months :cool: I'm always flattered when I get such positive feedback like this ...

There is so much to still catch up on from my hiatus, I've left more than a few people hanging here and I feel very bad about it. I also feel bad that I'm not smart enough to understand what needs to be done to the Fascinate GPS to make Google Navigation work properly again, but I am getting back up to speed slowly but surely, and maybe that's something that can still be fixed. (I need to secretly lurk about here on XDA and perhaps invade rootzwiki to see if anyone has figured out what's going on there)
[Fascinate Android Development] speedingcheetah:
there is agps patch....I have never gotten a accurate GPS lock,no matter the kernel or rom, until I flashed the .agps Google specific build patch someone posted here on xda...not sure if this would help or is even related to ur problem or not, but thought I would mention it. I would post a link...but I am on my phone...won't be home till tommorow.
[Fascinate Android Development] djp952:
I think I found the thread you're referring to and I downloaded both his 2.x and 3.x versions to try out today. Thanks!

http://xdaforums.com/showthread.php?t=1442032

edit: Sorry to say that didn't fix the issue with Google Navigation :( But, I can still include this aGPS config rather than ccampos784's if you guys want me to. It seemed to perform about the same for me. I've seen that really just launching "GPS Status and Toolbox", whether I can get a lock or not, seems to make everything work. It must be doing some manner of initialization or reset when you launch it that fixes whatever is wrong.
[Fascinate Android Development] rmtobler:
It's been so long since I've used Google Navigation, I forgot the problem even existed. Even though going through Google Maps takes a few more clicks to get navigation directions, I think the functionality is a little better. Especially the ability to pull up previously searched addresses after typing in 1 or 2 characters.
[Fascinate Android Development] djp952:
Yet another experimental kernel update!

GEEWIZ EXPERIMENTAL KERNEL 2.7.2 (March 30, 2012)

GeeWiz Kernel 2.7.2 adds the ability to configure the in-call volume boost levels. This can be done with an init.d script (see HOW TO CONFIGURE IN-CALL VOLUME BOOST below). In addition, the default in-call boost for the handset receiver was reduced from 12dB down to 6dB since the general feedback has been that it's too loud

GeeWiz 2.7.2 Kernel (EDIFY Update-Zip)

http://www.mediafire.com/file/99ch13m5u73gc2n/geewiz-2.7.2-kernel.zip

MD5: 2ebbd2ac77c90431cf82911ccdcdf6a1
​

HOW TO CONFIGURE IN-CALL VOLUME BOOST (GW KERNEL 2.7.2+)

Mount the SYSTEM volume as read/write [mount -o remount,rw /dev/block/stl9 /system]

Create the directory /system/etc/init.d if it does not already exist [mkdir /system/etc/init.d]

Create a text file called 'incall_volume_boost' in /system/etc/init.d with the following contents

The boost levels can be set by modifying the echo commands in the script

#!/system/bin/sh
#
# incall_volume_boost
#
# Configures the GeeWiz kernel in-call volume boost levels
#
# The levels are defined as:
#
#	0	- +0dB
#	1	- +6dB
#	2	- +12dB
#	3	- +18dB
#
# There are four configurable level device attributes:
#
#	Handset: /sys/class/misc/incall_boost/incall_boost_rcv
#	Speaker: /sys/class/misc/incall_boost/incall_boost_spk
#	Headphones: /sys/class/misc/incall_boost/incall_boost_hp
#	Bluetooth: /sys/class/misc/incall_boost/incall_boost_bt

# Default boost for handset receiver is +6dB (1)
echo 1 > /sys/class/misc/incall_boost/incall_boost_rcv

# Default boost for speaker is +0dB (0)
echo 0 > /sys/class/misc/incall_boost/incall_boost_spk

# Default boost for headphones is +0dB (0)
echo 0 > /sys/class/misc/incall_boost/incall_boost_hp

# Default boost for bluetooth is +0dB (0)
echo 0 > /sys/class/misc/incall_boost/incall_boost_bt

Set the permissions on this new file to 0755 [chmod /system/etc/init.d/incall_volume_boost 0755]

Reboot the device
[Fascinate Android Development] QuattroMechanic:
Anyway you could set it up to use terminal, callboost enable. Then set each setting like that other kernel I can't seem to recall?