yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Domush:
Can I make calls using google voice with this ROM?

I'm interested in canceling my cell service and only using google voice as a wifi phone. Any chance of this? I don't get enough calls to warrant a cell phone, but this setup would be ideal.
[Fascinate Android Development] djp952:
Not with this ROM out of box, I'm afraid. Google Voice requires a device to be "voice capable" which this isn't. It should work fine on the 3G/Voice version of GeeWiz but that would seemingly defeat your purpose. There are instructions out there to enable Google Voice on the Nexus 7 that could potentially be used on this without needing the 3G/Voice radio working -- that may do what you're looking for.
[Fascinate Android Development] rxwookie:
+1 for flashing without battery and without SD card. The only bad flashes I've ever gotten were when I left these in.
[Fascinate Android Development] djp952:
Status Update: I have the lionshare of features ported and working with Android 4.2.1, Bluetooth being the primary holdout at the moment, but I'm rather underwhelmed overall and wanted to know where you guys stand. 4.2.x has led to a couple pretty epic hacks for things like the GPS (and the RIL for the 3G ROM). The proprietary code we can't change is showing it's age.

Android 4.2 has a spiffy new camera (doesn't actually work any better -- remember, I think the camera HAL is the main roadblock here), the very nice Quick Settings changes to the status bar and the new Dreams feature, but ... otherwise not a whole lot that seems to be of use for this ROM's target audience.

I wanted to at least get this ROM to Android 4.2 for the Dreams feature, but the main one I use, the clock, is suck-tastic compared with the Android 4.1 clock. I suppose over time cool and useful new ones will be available in the Play Store, but out of the box, this becomes a minus for me. Quick Settings are great but need tweaking, and I don't think really add a lot of value here. Perhaps moreso with the 3G version, but here ... meh. Oh, and getting Superuser to work on 4.2 is just a nightmare. Does it work? Yes. Does it work perfectly? No.

Battery life is worse so far, performance feels worse, even with the DBDATA volume working again ... is Android 4.2 going to be useful for YOU? Don't worry, I'll release something based on 4.2, I'm too close to not do that, but I'm not feeling this as a "GeeWiz Media 3.4" ... it feels more like a one-off perennial BETA "use it if you want, but let's wait for Android 4.3 or 5.0" kind of thing to me.

Your thoughts would be greatly appreciated. I happen to prefer how this worked out with Android 4.1, but if most people want to see 4.2 ... I'll do my best as always to try and make it happen with an acceptable level of quality and performance :D
[Fascinate Android Development] bmeek:
Since Android is outgrowing the Fascinate...

Clearly the latest versions of Android are outgrowing the venerable Fascinate's hardware capabilities... For your GeeWiz 3.3 Media project, I won't encourage you to keep force-fitting newer and newer versions of Android v4.2 onto the Fascinate (unless you really enjoy the challenge :). I love the way you went back to refine GeeWiz 2.x - perhaps you're about there with the GeeWiz 3.x Media release too...

In any case, thanks again for your continued attention to this old device...
[Fascinate Android Development] djp952:
LOL, I do enjoy it, otherwise I wouldn't do it :p It may sound rather selfish, but my first customer is me! Everything else is just gravy and it has been and continues to be enjoyable, for the most part. It gets frustrating at times because Google is HORRIBLE about documenting what they change and how you're even supposed to use their code, but that's what the Internet is for, right?

My concern with 4.2 is indeed as you said, "outgrowing the venerable Fascinate's hardware capabilities". Well, that, and without source code for the Samsung proprietary pieces, when they break it's a crap shoot of hacks and workarounds to make them work again. So far, nothing has become impossible. Excessively creative, perhaps, but not impossible.

With Google dropping the Nexus S and the Xoom from AOSP with 4.2, I knew it was going to be a little bit harder, that's a lot of good reference code that disappeared. But: so far, so good overall. There are challenges to deal with, but if the build I'm in the middle of right now (lord, it takes like an HOUR on my laptop I so need a new one!) makes Bluetooth work at least a little and re-fixes the SDCARD that was previously fine until I tried to copy something Google did (oops), it's actually just missing some tweaks I want to make and finding/fixing any kinks it might still have. I may even have something for people to try before Christmas! ***

All in all, I do enjoy it. I have my whiny nights where things aren't working out, and I can only spend about about 6-8 hours on it per week, but hey -- it's free, right? LOL.

Ooooo... build is almost done. Cross your fingers for me that I managed to finally figure out this new Bluetooth stack configuration :) peace. edit: Got my wish. Bluetooth is partially functional. I'd call it 75% working ... lol. Who needs A2DP anyway?

*** = For me, this would actually be a pretty quick turn-around!
[Fascinate Android Development] bmeek:
Android 4.2.1 runs well on Fascinate...

Well, whatever your motivations, I'm truly happy about your efforts!

While the challenges presented by the Samsung-pieces-without-source are above my technical pay grade, I should probably eat at least a few of my words about the latest Android versions outgrowing the fascinate hardware - the onset of this inevitable trend continues to be held at bay... For the past 36 hours of so I've been running the 12/16 build of JT's unofficial cm10.1 / Android 4.2.1. It's performing pretty dern well.

I mention this only because I'm continually so impressed by the likes of you and JT, and I guess where there's a will there's a way :). I imagine you'll get 4.2 working really well in GeeWiz.* before long (and hopefully have a good time doing so).
[Fascinate Android Development] djp952:
jt1134 is da man! Per chance is Bluetooth working well for you on that build?? Bluetooth is currently the most serious roadblock I'm encountering with 4.2, on my version it won't discover some devices, and when it's ON, it's absolutely destroying the battery ... as badly as if the screen was on the entire time (kernel changes are likely needed). If jt1134 figured that out, well, it wouldn't be first time I stole something from him - lol. In fairness, I share anything I've done that I think is important with him as well, and one of them went completely mainstream for all kinds of devices!

I spent my spare time this evening fixing dock audio on 4.2 for my build, it put up a rather epic fight but I finally beat it about an hour ago and seems to be working great again :) Currently cranking some sweet sweet old-school Chistmas tunez from Sky FM via the dock. You guys probably wouldn't like it. Lots of Bing Crosby and Johnny Mathis :good: (djp952 is circa 1972, don't blame him too much for his taste for ancient Christmas Music!!)

I'll get there ... even if I have to steal it all from JT!! :laugh: Thanks for the compliments my friend!!
[Fascinate Android Development] rxwookie:
I'm right there with you brother! I love both of those as well as good ole Dean Martin.
[Fascinate Android Development] bbrad:
4.2 seems too have better performance in my option I would never go back too 4.1.2 now lol. And as for the Christmas tunes hellz yea
[Fascinate Android Development] bmeek:
Hey there. Yes, Bluetooth is working fine. In fact, I'm working with two paired headsets... my newer headset supports both phone and media audio, and I use that to listen to news and other media while walking about. But if I put the phone in the desk or car dock while that headset is connected, the media continues to play through the headset, rather than through the dock audio port.

I could go into Bluetooth settings for this headset and uncheck the media audio selection, but it's easier to turn the headset off, then turn on my older headset that only supports the phone profile...

This all works fine. It would be cool if there was an audio prioritizing mechanism, but I'm just happy things work as well as they do :).

---------- Post added at 08:59 PM ---------- Previous post was at 08:37 PM ----------

Yep. The Jellybean optimizations continue...
[Fascinate Android Development] gorm:
Gonna load this up on the ole fassy tomorrow. Wife (god i love that woman) bought me a Galaxy Nexus for Christmas:D

Looking forward to using this as my poolside media center come this summer.

Thanks again DJP for all ur hard work:good:
[Fascinate Android Development] djp952:
FYI on a couple new known issues for v3.3 that I've added to the main post:

USB Gadgets will not work after the device has been docked

After undocking the device from the Fascinate Dock, USB Gadgets (common ones are USB Mass Storage and ADB) will no longer work. Charging is not affected. The only workaround for this issue is to power the device off and back on again, rebooting is not sufficient. The problem is an incompatibility with the USB Gadget code I ported into the GeeWiz Kernel to modernize it and the Kernel code for the dock.
​

Compass can be inaccurate

The compass device can be inaccurate, even with calibration. The problem is that the proprietary geomagneticd service is typically started before the compass sensor has been accessed for the first time, which leads to inaccurate readings. I have a fix for this, but am waiting to release a patch hoping I can roll a couple other fixes in at the same time. To work around this issue, stop and restart the 'geomagneticd' service while the application that is using the compass is active.
​

I've already fixed the compass, but would like to try and deal with the USB/Dock issue at the same time. I won't wait too long before patching the compass if the other problem is going to take me a while -- I haven't really looked into that one yet.
[Fascinate Android Development] djp952:
Since the 4.2-based build isn't ready yet (Bluetooth and Superuser problems are the remaining holdouts), I took some time to back-port a handful of changes to the GeeWiz Media 3.3 build:

GeeWiz Media 3.3.1 Patch (EDIFY Update-Zip)

- Adds ability to control Vibration Intensity to Settings/Advanced

- Mostly fixes the compass

- Disables 360 degree tablet-style rotation

- Changes description of Settings/Display/Pulse Notification Lights to simply "Notification Lights"

- Emulates a Digital dock audio device instead of an Analog dock audio device

http://www.mediafire.com/file/4wo8jk25dndsn4w/geewiz-media-3.3.1-patch-12282012.zip

MD5: 6dd9c56b83ff68521026f7140b479784
​

A couple notes ....

- I removed the part of the patch that wipes the Google Services Framework data this time around. I started doing this to solve problems with patches issued against Android 4.1.1 that changed the Kernel as for some reason that would trash all things Google until that data was wiped. I've tested it a number of times and the 4.1.2-based builds don't seem to suffer from the same issues. If after applying this patch your Wifi indicator doesn't eventually turn blue, you can't access any web sites through the browser, or Google sync is failing, manually wipe data on Google Services Framework and reboot immediately afterwards. Let me know if that happens so I can add the code back into future patches.

- The compass is "fixed", but this is the Verizon Fascinate ... therefore it's not perfect. The compass seems to have the same basic issues as the GPS on the device, the services that control them just don't work right sometimes after the device has been rebooted. This was the real underlying cause, I was starting the compass service (geomagneticd) during boot, but if it felt like being evil, the compass would just never work right. Now the service is controlled by the sensor HAL, so it will start when an app requests the compass and stop when it's done. You may still have to wait a while after the device reboots for it to be accurate and close/reopen the application using it, but at least now it won't be broken forever.
[Fascinate Android Development] djp952:
Another quick end-of-the-year patch for you guys ....

GeeWiz Media 3.3.2 Patch (EDIFY Update-Zip)

- Resolves continuing occasional issues with Wifi Toggle ON appearing to hang up

http://www.mediafire.com/file/pjse82s6vdd1s18/geewiz-media-3.3.2-patch-12312012.zip

MD5: d235a3e09d49fb0065f64243d878f0f7
​

I'm hopeful that this patch will completely resolve the occasional issues encountered when toggling Wifi ON/OFF. What I found was that Android relies upon the status of a property, 'wifi.driver.status', to determine if the kernel Wifi driver is loaded or not, and if that property is wrong for some reason, bad things will happen. I've modified Android to not trust that property and always check to see if the driver is really loaded or not, and changed it so if a request to turn Wifi ON comes in and the driver is already loaded, it will just unload/reload the driver instead of failing. While I cannot replicate whatever scenario happens to actually cause this, I'm hopeful that these mitigation steps will be successful in putting the issue to rest once and for all :cowboy:
[Fascinate Android Development] djp952:
The Wifi-Toggle Saga continues ... this could very well be the end of it!

GeeWiz Media 3.3.3 Patch (EDIFY Update-Zip)

- Alleviates kernel memory pressure that can cause additional issues with Wifi Toggle ON

http://www.mediafire.com/file/zvzbwvabqqadmv5/geewiz-media-3.3.3-patch-01022013.zip

MD5: 02ec9351dddcdfb8fe198ef8fd48f9fd
​

GeeWiz Media Patch 3.3.3 addresses a couple kernel-level wifi problems that XDA user rich_e helped me to find with the 3G-enabled version of GeeWiz. Even after "fixing" the potential Android OS wifi toggle problems with patch 3.3.2, his device was still getting memory allocation failures when enabling Wifi post-boot. What I found was that the original Gingerbread kernel had some memory pre-allocated for Wifi that had been orphaned when I updated the drivers for GeeWiz Media 3, and (re)enabling Wifi may request a block of kernel memory that cannot be satisfied under certain circumstances, also causing Wifi ON to hang.

This patch modifies the kernel such that the original pre-allocated memory for the device wifi will be utilized again as well as adds another 96KB of that pre-allocated memory to specifically address the memory issues rich_e has experienced. This greatly reduces the amount of memory required (70KB versus about 2KB) to bring Wifi back online and appears to have completely resolved the toggle issues.

If Patch 3.3.3 causes you problems, please let me know and I can generate/post a "rollback" artiact to restore the previous GeeWiz Media 3 kernel (v3.3.1) and get your device back up and running as quicly as possible)
[Fascinate Android Development] djp952:
GeeWiz Media 3.4 has been uploaded and posted to the DOWNLOADS section of the first post.

GeeWiz Media 3.4

Adds ability to control Vibration Intensity to Settings/Advanced (GW Patch 3.3.1)

Mostly fixes the compass (GWM Patch 3.3.1)

Disables 360 degree tablet-style rotation (GWM Patch 3.3.1)

Changes description of Settings/Display/Pulse Notification Lights to simply "Notification Lights" (GWM Patch 3.3.1)

Emulates a Digital dock audio device instead of an Analog dock audio device (GWM Patch 3.3.1)

Addresses a potential race condition with voice call audio in the audio HAL (GWM Patch 3.3.1)

Resolves continuing occasional issues with Wifi Toggle ON appearing to hang up (GWM Patch 3.3.2)

Alleviates kernel memory pressure when Wifi is toggled ON by using pre-allocated memory buffers (GWM Patch 3.3.3)

Resolves ongoing issues with Notification/Alarm tones appearing in Settings as well as Force Close and database corruption issues with certain Google Apps (Music/Gallery/Google+) (New -- GWM 3.4)

For the most part this is just a roll-up of the three GeeWiz Media 3.3.x patches, but it finally addresses the long-standing issue with the Notification/Alarm tones disappearing from Settings, and in conjunction certain Force Close issues with Google Apps (Music/Gallery/Google+) that access the Android media databases.

If you continue to have problems with Settings not showing all the notification/alarm tones after this update (and giving the system a few minutes to re-scan the internal media), please let me know!
[Fascinate Android Development] djp952:
This ROM has been retired as of March 5, 2013 and I will request that the thread be closed by a moderator.

I had promised to keep this ROM version alive until the newer Android 4.2-based "GeeWiz Media 4" was able to duplicate it's feature set, and as of GeeWiz Media 4.3, I believe that feature set has finally been matched and/or exceeded. Regardless, I allowed this version to slip for far too long and any attempt to bring it up to date is not justified based on the download counts (close to zero for the past 45 days).

GeeWiz / GeeWiz Media 4.x thread: http://xdaforums.com/showthread.php?t=2088224

Thank you so much for using/enjoying my ROM, and I hope that you will consider updating to the more current version! Long live the Verizon Fascinate!!

Regards,

djp952
[Asus Transformer TF700] Noodile:
I got my tablet on Wednesday. Its completely stock. No root. Nothing. And in the last 24 hours. It crashed twice. It only crashed when I opened Instagram.. the tab would go to rotate. Give a blank white screen with one black line in it. Freeze for like A minute. Then reboot. Any one have /the same issue
[Asus Transformer TF700] garrettl:
random crashes

I also get random crashes similar to what you describe, but in other apps. (It's a solid color screen with just a line below it. It's usually white, but once in a while it's near-black or a solid color.) It seems to be just a few apps that are causing it... and if I avoid those, I can use the tablet for hours on end without really any problems.

I'm guessing it's a video driver issue. (Hopefully it's fixed in Jelly Bean? JB does come with a new kernel and new video driver, so the problem *might* just disappear.)
[Galaxy S III Q&A, Help & Troubleshooting] FallenAngelX:
Hey, this is my first post here so i hope i did this right :p

Basically, just want a rom that is faster than stock, and has all features working

In the past when i tried roms such as cynagen mod the camera wasnt working at full res or other issues came up, is this still the case?

Anything you guys reccomend in particular?

Cheers
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
RULES.

All kinds of Best Rom/Kernel/etc threads are unwelcome, read, research and make your own mind up, as the question is very subjective.

Use the rom INDEX and decide for yourself .

jje
[Galaxy S III Q&A, Help & Troubleshooting] FallenAngelX:
Thank you for the response, i read the rules and noticed that.How ever my question isnt as bland as "best rom" or "fastest rom"

Its precise in the sense i specifically mention that i want all features to work, and be faster than stock. As far as i can tell thats objective not subjective

I will how ever check out the rom index

Thanks
[Galaxy S III Q&A, Help & Troubleshooting] ph10m:
As jje said, there is far too much about roms to define what you're looking for. It might sound simple but you'll simply have to research and try out some of the most used ones.
[Galaxy S III Q&A, Help & Troubleshooting] Acidpunk:
Well from what I've seen there are tons of bloat removed default samsung roms, I know people like the Android Revolution roms as well as Foxhound and Wanamlite.

I mean those three kind of suit your needs as to my knowledge they are based on stock roms, Although CyanogenMod does have the camera working fine I suggest you try one of the new nightly builds :p
[Galaxy S III Q&A, Help & Troubleshooting] haranbh:
BOOM! Closed. :cyclops:
[Galaxy S III Q&A, Help & Troubleshooting] chrisd1a1:
Thread closed. Try them and see
[Samsung Epic 4G Touch] demolasko:
im getting an error when trying to flash zips on my e4gt

"formatting cashe

format() excepts 4 args, got 3

E:error in /sdcard/whateverzipipick.zip

(status 7)

installation aborted"

happens when flashing calk's FORMAT ALL as well and i know that file worked as i used it many many times .. any ideas?
[Samsung Epic 4G Touch] patrao_n:
Mobile Odin the el26 kernel with cwm5 then flash from that recivery

sent from my BAD A$$ Epic touch
[Samsung Epic 4G Touch] MoHoGalore:
Also, I'd like to know the recovery that you're using to get the Status 7. Sounds like you're using Rouge. Hopefully you know to not use those anymore.
[Samsung Epic 4G Touch] demolasko:
im using the safe cwm recovery from chris41g .. ive used this recovery no problems flashing before and i also reflashed the recovery.zip to no avail.
[Samsung Epic 4G Touch] MoHoGalore:
What were you trying to flash, besides getting that on the format all script? Cause I'm curious.
[Samsung Epic 4G Touch] demolasko:
i tried to flash:

supernova 2.0 rom

the format all (i know that file worked i used it ALOT never deleted or moved it)

the el29 modem

i tried the modem a couple weeks ago and it gave me that error but didnt think anything of it till i tried flashing a rom today

thats all i know of so far
[Samsung Epic 4G Touch] MoHoGalore:
As patrao_n said, use el26 cwm or an Agat kernel/recovery and try. Let us know how it goes..

Since you can't flash, use Odin or mobile odin to get to one of those recoveries.
[Samsung Epic 4G Touch] demolasko:
I will definitely try that when I get home. I can flash recovery with no problem I was able to reflash my current recovery without any issue but I still have the same error when trying to flash my ROM
[Samsung Epic 4G Touch] patrao_n:
You said you wrre able to flash your recovery again. Are you only flashing a recovery or are you flashing a kernel?

sent from my BAD A$$ Epic touch
[Samsung Epic 4G Touch] demolasko:
i got it here when he released the "safe" one

http://xdaforums.com/showthread.php?t=1760299 which brought me here http://aosp.chris41g.org/post/2012/07/08/ClockworkMOD-5-Safe-Recoveries-for-TouchWiz-and-AOSP.aspx

it says its a recovery kernel im assuming its just the recovery and not the actual kernel but i could be wrong.
[Samsung Epic 4G Touch] MoHoGalore:
With this phone the kernel and recovery are together, unlike other phones.

Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
[Samsung Epic 4G Touch] demolasko:
thats what i figured though i am used to HTC devices ;)

im getting all the files i need now to odin to the el26 kernel (never used odin/m-odin before) ..as for el26 is there a specific "safe" one i should use? if so can someone link it?
[Samsung Epic 4G Touch] demolasko:
well odin to el26 did the trick .. not sure why the recovery i have been using since the "safe" ICS recoveries came out stopped working all of a sudden

thanks for your help all!!
[Samsung Epic 4G Touch] MoHoGalore:
Good deal. :thumbup:

Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
[Asus  Eee Pad Transformer Prime] Bryan000:
Hey guys,

Just bought a prime online and it's already starting to give me problems; specifically, it doesn't seem to want to charge the dock/tablet.

Is this the standard charger everyone has? Searched Google and I see only the more rectangular one

Any help would be appreciated
[Asus  Eee Pad Transformer Prime] Moothead2:
That's the Nexus 7 charger. Did you buy it new or second hand?
[Asus  Eee Pad Transformer Prime] Bryan000:
Haha. Awesome.

And I got it 2nd hand off ebay

I'm not guessing that's why it's not charging fully? Aka barely charges only when turned on and never charges the dock
[Asus  Eee Pad Transformer Prime] Moothead2:
Yeah, they have different Amp and Voltage values which likely means your Prime isn't getting sufficient power from the adapter charge the tablet and dock. Drop the seller a message explaining you received the wrong charger adapter.

Good luck.