yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!

I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.

I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.

Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
[Fascinate Android Development] djp952:
I can duplicate the Wifi issue and am looking into it. For me, it just took a REALLY long time for it to turn on, like 10 minutes. I think I know what I've done that might cause this and hope to fix it :) Getting the logs now.

edit: I think I see what the problem is, not sure why it hasn't been an issue with the "Media" version. I have to dynamically load and unload the Wifi driver to prevent bad things from happening, this isn't the usual way it's done. The OS is set up to start the Wifi "supplicant" automatically, when it probably shouldn't be. The supplicant can't load if the wifi driver isn't up yet. Sometimes it works, sometimes it doesn't, and when it doesn't Wifi will be hosed until the OS sorts it out. I have two solutions to try, the first is to see how Android behaves if I don't allow the supplicant to be started as part of the "main" service class, the second is to figure out that aforementioned bad thing and do it more properly. I'll get it. Sorry for the bug :)

Thanks for trying this guys! I never expected it to be as good as the "big" ROMs, and I wish I could do something about it being so ungodly slow for a while. It seems to pick up and work properly after all the apps have been updated and it's had a chance to do all the Google backups and whatnot that it wants to do.

One problem I saw yesterday for the first time that you might need to watch out for ... The battery TANKED in a matter of 2 hours for some reason. It looks like Google Search went off the reservation. I've also seen "GPS Status and Toolbox" destroy the battery if you don't close it all the way (long-press HOME, then swipe it away).

Oh, one cool feature we have now ... "Take Bug Report". Check in Settings/Developer options to see it. What this does is collect all kinds of logs and information about the phone and make an e-mail out of it. The default sends it to your GMail account. It's about 3MB, but it will be nice to have something everybody can use to gather logs for problem resolution rather than asking folks to hack around in ADB. So, if you run into weirdness, you can click that button, wait a while and watch scary "shell has been granted superuser permissions" pop up a lot, and you'll ultimately end up in GMail with something you can send you me or post parts of here! Great that Google added that in an accessible way finally!!
[Fascinate Android Development] djp952:
For the folks having trouble with turning Wifi on and off, I have an experimental/test patch for you. This patch will replace the GeeWiz 3.2 kernel with an updated version that changes the ramdisk/initramfs such that the wifi services are not started until Android requests them to be started. It may affect Wifi and Bluetooth Tethering, but my testing of the change here for both showed no ill-effects:

GeeWiz 3.2.1 Wifi Patch [Experimental] [EDIFY update-zip]

REMOVED: Please use official patch in the DOWNLOADS section of the main post
​

NOTE: You will be asked to re-opt-into the Google Location service on the first boot, this is normal. I clear the "Google Services Framework" app on any kernel change now to avoid the well known Jelly Bean issues with losing connection to Google Services when you alter the kernel. This may have been fixed with JZO54K, but why risk it when all you have to do is click "Agree" :)

You may have to reboot once more after installing this to clear up the Wifi on/off problems so that the Android settings are synchronized with the changes. If after a second reboot this does not solve your problem, please let me know!

Rollback: This change can be rolled back by installing the EDIFY update-zip for GeeWiz 3.2 again on top of it without wiping data. I can also package/provide a more specific rollback that only undoes the changes if necessary.

Please let me know if this solves your Wifi issues or not, so that I can either post it as a primary patch for GeeWiz 3.2 (and GW Media 3.2) or take another crack at solving it :) Thanks!!!
[Fascinate Android Development] swapnilss:
Hi!

Wiped data dalvik and cache & now I am on JellyBean. Thanks djp952. :good::good::good:

This Rom looks great and apart from the Wifi issue ( havent got time to update my phone with the patch for wifi issue as yet) which takes some time to start or sometimes just rebooted my phone altogether, everything seems to work fine. Had a problem verifying Whatsapp but used their "Verify by Call" method and now its working fine too. Battery life seems good to me as of now. Liked the inbuilt BLN.

Sadly, as i mentioned before, i lost my 1x/3g connectivity (nothing to do with this Rom) and thats Ok for a day or two till i try & figure out something to enable it again. By the way, i have always done the wipe through recovery only. Never used the factory reset option in settings menu. And that means the 1x/3g settings get wiped out the moment I wipe Data (note: wiping dalvik & cache does not affect it).

Anyways , looking forward for more developments on this rom from you.

edit... The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
[Fascinate Android Development] rxwookie:
QuickPic

We are a little off topic, but... I too have had nothing but problems with the stock Gallery application... not loading at all, not showing pictures, generally being grumpy (okay, so I get that way too sometimes), etc.

Try Quickpic (http://market.android.com/details?id=com.alensw.PicFolder) , it's a free app that is a gallery replacement (ad-free too!). Just make it the default and you should be set. If, for some reason, you don't like it... Just uninstall and revert back.

As for the Jellybean ROM... too sweet! I love having an original Galaxy S with JB running on it! I get questioned all the time what phone I have, because it's running the latest Android build and doesn't look like any out there right now.
[Fascinate Android Development] djp952:
I'll load up some huge amount of photos and have a look at Gallery. I could switch from using the Google Nexus version to the AOSP, if it shows any improvements. One bonus we could get there is that I enabled widescreen photos in the AOSP branch :) Didn't include it for various reasons, one I recall was that it would crash if you tried the "face detect" option.

I'll have a look -- maybe it can be fixed! I also have to download this "Whatsapp" that people are using ... never heard of it :) What does it do?

Thanks as always for the feedback guys! Glad it's going pretty well thus far :D
[Fascinate Android Development] djp952:
FYI for any aspiring developers, I've started making a "HOW TO" guide for building GeeWiz from scratch in Post #2:

http://xdaforums.com/showpost.php?p=33011164&postcount=2

I've gotten as far as how to make the AOSP ROM and compile the kernel. At minimum, I need to add how to make the ODIN files as well, but maybe later. Depending on level of interest, I can go into as much as anyone wants there, short of how to make actual code changes (but I could try to help offline). I think describing how to get from source to the flashable files is a good first step, I'll see how it goes from there :cowboy:
[Fascinate Android Development] JJ5150:
DJ, you should link this on the home page of GeeWiz 2.9, so more folks can get this. Also, I think you should name it JellyWiz... :D
[Fascinate Android Development] AndroidGee209:
Can I ask what this is ?
[Fascinate Android Development] JJ5150:
JellyBean for the Fascinate, with GeeWiz recovery and kernel

---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------

where can i find the compass?
[Fascinate Android Development] GizmoDroid:
The biggest problem I have had so far is with making calls. I need to do some digging to see what's causing it, but more times than not, I'll try to make a call and all I hear is silence and the caller cannot hear me.

I've figured out that if you turn on speakerphone right after dialing, it will work just fine. You can even turn speakerphone off, and it will switchback to the handset speaker and mic just fine.
[Fascinate Android Development] djp952:
Eh ... not quite yet. GW 2 has been a pretty stable setup ... after some kinks are worked out of this one! Rename is always an option especially since there is no wiz in this GeeWiz :p all youll find in the rom is the name "atlas3g" ...
[Fascinate Android Development] djp952:
Yeah I can confirm that. Drat. Looks like the audio paths arent defaulting to the proper outputs. Should be in the audio HAL. Ill see what I can do tonight my guess is its a pretty easy fix.
[Fascinate Android Development] A-L31:
http://www.rimweb.in/forums/topic/3...xy-sii-epic-4g-touch-the-mammoth/page__st__90 <<< try this for your data, hope this help
[Fascinate Android Development] djp952:
The main post has been updated with all the currently known issues. I will be checking the "3.2.1" patch code in and making that official (Wifi On/Off problems) tomorrow morning, and intend to focus on the in-call audio input/output path problems next as issues there are simply unacceptable to me. I've installed the "WhatsApp Messenger" application, but haven't set it up yet. I'm hoping it does a good amount of logging so it will tell me what it's grumpy about, but honestly as soon as it came up and complained that I was using a "Custom ROM" my hopes kinda faded a bit for that one :eek:

I've also completed the first draft of "Post #2", which describes how to build GeeWiz 3.x from source and package it the same way I've been doing it to date. If you are at all interested in modifying GeeWiz or enhancing it, please give it a read and PM/post feedback on how it can be better. I would love to be able to link to some community-developed enhancements (hint-hint).

Also FYI, I'm leaving for Vienna, Austria in 2 days and will be completely out-of-pocket for about a week (no CDMA over there). I'm really hoping to patch this up to solve the biggest issues before I go, but if I'm unable to don't think I've given up, I'll be back on it as soon as I return!! :highfive:
[Fascinate Android Development] swapnilss:
One more thing I noticed is that the status bar is functional even when the screen is locked and thus you can access the settings directly even if screen is locked.

As for the gallery issue, I have been using quickpik since a long time but the stock camera uses stock gallery and if I disabled gallery, the camera app is not visible in app drawer. Anyway this issue is being resolved in the new update hopefully.

@rxwookie..... I have already tried that but sadly it doesn't help. Need to check my name and nv settings using dfs or cdmaws.

No other issues faced so far.

Just one question, what driver do I use to connect to Pc as the fascinate driver does not work.
[Fascinate Android Development] gorm:
Also FYI, I'm leaving for Vienna, Austria in 2 days and will be completely out-of-pocket for about a week (no CDMA over there). I'm really hoping to patch this up to solve the biggest issues before I go, but if I'm unable to don't think I've given up, I'll be back on it as soon as I return!! :highfive:[/QUOTE]

Like my Momma always said "good things come to those that wait" :silly:
[Fascinate Android Development] djp952:
Lock screen: That's actually typical behavior for AOSP, weird I know. Stock builds allow you to do that as well. I'm pretty sure it can be disabled fairly easily if it's bothersome. I also think that if you use any of the more secure lock screens you can't access settings that way. I'll add this to the list, I'm not a big fan of that "feature" either. With the truly stock settings, you could also unlock by accidentally pressing the MENU key. That definitely had to go!

Camera: Gotta love AOSP here. In 4.1, the camera is actually part of the Gallery app! Disabling Gallery removes the camera. Given this, what I may do is look at how well the "legacy" AOSP camera/gallery apps work. I hadn't really considered them before, but if they solve the other problems and still work acceptably well, I'm all for it. Then, you could independently disable Gallery without losing Camera. I'm getting the feeling that the Gallery is going to be quite the challenge :)

Driver: It should be the generic Google driver, the same one the Nexus S uses now: http://developer.android.com/sdk/win-usb.html. On my Windows box, it comes up as either "Google Fascinate" or "Android UMS Composite USB Device", depending on where you look. Windows auto-installed the drivers for me with standard Microsoft ones, at least on Windows 7 x64. If that google link doesn't have what you need, let me know and we can find something for ya. Just pretend it's a Nexus S and I think you'll be good!
[Fascinate Android Development] djp952:
FYI, I also have a handle on the issue with "WhatsApp Messenger", it's related to the way I provide support for the Fascinate DBDATA volume. The database file for the application is missing and the app cannot create it. This one is absolutely my fault. I have to install/uninstall it a few times to track down what part of the install process I didn't hook into properly, but it should be fixable.
[Fascinate Android Development] djp952:
I was able to issue 2 patches today:

GeeWiz 3.2.1 Patch (EDIFY Update-Zip)

- This patch addresses issues with the Wifi toggle on/off function hanging up, necessitating a reboot of the device

- Applying this patch will wipe data on the Google Services Framework app, you will be prompted to accept Location services upon reboot

http://www.mediafire.com/file/ddyndwr8lxg67dk/geewiz-3.2.1-patch-10232012.zip

MD5: 412d034faf5d79f84a7548c6f1b4481c

GeeWiz 3.2.2 Patch (EDIFY Update-Zip)

- This patch addresses a compatibility issue with certain applications (WhatsApp Messenger, for example) that are incompatible with the way GeeWiz 3 has implemented the DBDATA volume to store SQLite database files.

- After applying this patch you must uninstall and reinstall the affected application(s), clearing data on them is insufficient to resolve the issue, they must go through the entire Android install process again.

http://www.mediafire.com/file/l5lbsg5r6dd6pyd/geewiz-3.2.2-patch-10232012.zip

MD5: 15caf7de590fe2669d2a28442e56db92
​

GeeWiz Patch 3.2.1 seems to generally fix the Wifi on/off toggle issues that some users have experienced. Anyone that has already installed the experimental version of that patch I posted yesterday does NOT need to install it again. It's the same patch, just recompiled and checked into github. The MD5 will be different than the experimental one, and you are of course free to install it again. NOTE: While testing GeeWiz Patch 3.2.2 I had a fairly similar issue with enabling Wifi, but ultimately it just toggled back to OFF and it enabled properly on the second try. This may not be as fixed as I believed it was, but I think it's definitely "better".

GeeWiz Patch 3.2.2 resolves the issue with WhatsApp Messenger, and I'm assuming at least a handful of other applications that have yet to be tested. The problem here was the way I have hacked Android to support Samsung's custom DBDATA volume. WhatsApp appears to make an assumption as to where it can store it's SQLite database, and unfortunately for it, I happen to have a symlink there to make Superuser work, so it fails and Force Closes. What I've done differently with 3.2.2 is I am now pre-creating the necessary directory on DBDATA, so these apps do not have to. You will have to completely uninstall and reinstall the affected application(s) for them to pick up the change! I'm sorry about this, but the application has to run through the updated install process to get the automatic creation of the directory to take place.

I've also now seen a problem with the Google Play store after enabling Wifi for the first time that required me to reboot to resolve it. I get the feeling that getting this ROM to work properly is going to take a bit more effort than I was initially expecting it to. All these bugs will get killed eventually. Thanks for bearing with me, folks. I have every intention to make this as perfect as I can, it's just resisting that intention thus far! To be honest with ya, I'm starting to regret this project a bit ....
[Fascinate Android Development] djp952:
LOL, I think I do about 95% of all the posting to this thread so far :)

I wanted to let you know that I am getting closer to understanding the in-call audio path issues. I'm working on the output paths tonight (receiver vs. headphone vs. speakerphone, etc). What seems to be happening here is that the code is killing itself off prematurely, which sends the audio into standby and effectively mutes everything. When you change the path, for example by enabling the speakerphone, it will wake up and work. Input paths also seem to have some problems, I don't see it ever switching from the receiver mic to anything else under any circumstances.

It's fixable, but I don't think I can do it in the next hour or so (stranger things have happened, though). As I indicated before, I will be in Europe from tomorrow until next Wednesday, and while I was really hoping to make some progress on this problem beforehand, it's not looking that way. If I dream up some epiphany that can be coded and tested in about 30 minutes tomorrow before I leave, maybe I can post something, but please don't count on it. Sorry guys. :crying: My phone needs flashing to the Wifi-Only GeeWiz Media for the overseas trip ... there are all kinds of Angry Birds levels I need to complete on the plane!!
[Fascinate Android Development] Shakes The AssClown:
When ODIN'ing the full wipe version do you need to include a PIT file? Just wondering?
[Fascinate Android Development] gorm:
No, just make sure you are on a "Stock" GB Rom
[Fascinate Android Development] JJ5150:
or any version of GeeWiz
[Fascinate Android Development] Shakes The AssClown:
Ok thanks!! :)
[Fascinate Android Development] djp952:
Hi everyone! Just wanted to let you know that I'm back from vacation** and will be working on this again. Before I left I had a prototype for a voice call audio fix but ran out of time to test it, I'm hoping to remember what the heck I did there tonight and try it tomorrow.

** Vacation actually ended Monday, but thanks to Hurricane Sandy here in the US Northeast, getting home was a challenge, and of course when we finally got back Wednesday there was no electricity :crying: Everything is back online now, no water was in the basement, etc. Got to spend an extra day off in Frankfurt, Germany which was an unexpected pleasantry -- good beer!

While away, I was using GeeWiz Media 3.2 on the Fascinate, and found a new bug and another issue I'd like to correct.

The bug is that the ringtone/alarm/notifications don't always populate properly and as a result can lead to weirdness. I've already checked and the 3G version has the same problem as you might expect. Haven't looked at that at all yet, and at least it will default to something audible so it's not a complete loss.

The issue I'd like to try and ultimately do something about is the damn GPS. Everyone knows the GPS on this device is terrible, that's no shocker, but it doesn't seem to work AT ALL outside of North America. My assumption is because it's pulling A-GPS data for North America and the hardware is so bad it just can't deal with not having that location information for where you actually happen to be. If there is a more "world" version of the A-GPS configuration I'd like to change to that, but I may need help from folks outside the U.S. to see if it helps. So if you're in Europe, South America, Asia, Africa, Australia (or even Antarctica!), let me know, I can use your assistance when I get to that.

My wife and I had wandered far off the beaten path in Vienna, Austria and all we had was this terrible map so I confidently whipped out my Fascinate, found an open Wifi hotspot, fired up Google Maps and .... fail. Installed GPS Status, updated A-GPS and ... fail. I waited for almost 30 minutes for the GPS to find a single satellite and it couldn't. This is unacceptable. We obviously found our way back without the help of technology, but it completely defeated the purpose behind packing the Fascinate in the first place! Galaxy Tab 2 in the backpack after that, and THAT device works :victory:

For what it's worth, I highly recommend Vienna as a destination for anyone that has the means to go. It's a wonderful city full of very nice people that are very accepting of English speaking tourists. The beer kinda sucks, but the schnitzel is top-notch (they invented it after all). Budapest ... meh ... not my cup of tea. More Westernized than I was expecting it to be. Stick a Baroque palace or two in Queens, NY and save a lot on air fare.
[Fascinate Android Development] djp952:
Still working on the in-call audio issues, not much progress. I just now replaced the audio HAL with jt1134's new one, and it made zero difference (not entirely true, it made headset a tad worse, cannot control the volume at all). I'm concerned at this point that I will have to yank Voodoo Sound from the kernel and use a different version of the audio driver :crying: Nothing I do in the OS is helping, it has to be the kernel.

Oh well. Perhaps yanking Voodoo is the right thing to do, it can be downloaded from Google Play and that version is enhanced over this older cooked in one anyway. Getting all the dock audio changes I made to work again will be fun.

Sorry it's taking so long. I think the next step is to align all the audio components with CyanogenMod/jt1134's code and re-work my changes from there if the main problem gets solved. Long couple nights ahead ... :p
[Fascinate Android Development] AdelosMeansUnknown:
Just two pet peeves:

1. I'm not sure if it's just me but there is no CRT shutdown animation.

2. Instead of a plain black notification tray, would it be possible to make it gradient/opaque like the Galaxy Nexus version (as in stock OTA)?
[Fascinate Android Development] djp952:
I'm surprised you have only 2 peeves, this ROM is a hot mess and I'm pretty close to abandoning it given the shape it's in :) But regarding point #2, can you post a screen shot? My tray looks exactly the same as it does on my Galaxy Nexus, the notifications have an opaque gray background that fade in/out when you swipe them. I would be happy to try and fix it, but I don't see any difference here. (and let's face it, it's been almost a month and I can't fix in-call audio paths -- lol)
[Fascinate Android Development] AdelosMeansUnknown:
I will admit the current state of the is agonizingly buggy (although the work you've done surely makes up for it). Unfortunately, I won't be able to provide a screenshot of a Galaxy Nexus notification tray (I am no longer in possession of one). I'm looking for a ROM like Bugless Beast (exactly really). I'm sure you'll see a difference in the notification TRAY if you were to flash that ROM.