yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Woohoo! Very glad to hear it, I'll promote 3.3.3 to the main post and dump the "experimental" part :D Building/testing this change for GeeWiz Media 3 at the moment. It's nice to get one right! <score!> Please let me know if it acts up again, I'm always willing to try and fix what I can.

Why thank you, hhp_221! I try to be a little more verbose than most folks, often far too much so (mainly because I suffer from a terminal case of verbal diarrhea :eek:) but also definitely for those that are interested in whatever process I'm happening down. I'm wrong a heck of a lot more often than I'm right, but so far other than trying to get this ROM to work properly in India for swapnilss, I've managed to stumble my way out of pretty much everything bad that's come up, given enough time :o If you do give it a try, be sure to let me know what you think! Believe me, you won't hurt my feelings if you don't like it, it's certainly a little "Spartan" compared to most offerings these days, I'm flattered that so many people have tried it at all given the other options available.

edit: Android 4.2 GeeWiz is still coming as well, the only remaining major problem to solve before giving you guys something legitimate to chew on is Bluetooth, and I think I'm getting closer to the solution there. It works about 50% of the time now and I even had A2DP work for about 10 seconds - lol. I did finally fix Superuser for 4.2 by compiling it myself from ChainsDD's latest code. That guy is great, he even made his keys public so source-built versions still link up with his official ones on Google Play Store. No ETA yet, but "soon" seems appropriate ...
[Fascinate Android Development] JJ5150:
DJ, do you think the Devil 3 kernels (like the one in my sig) will work on your Rom or are they simply for MTD roms?
[Fascinate Android Development] hhp_211:
Gonna b a no ... read the OP
[Fascinate Android Development] djp952:
yeah, that's indeed a big ol' no. Sorry about that. As far as I know, GeeWiz is the only Galaxy S 4.x ROM that doesn't use MTD, and as a result you'd be completely stuck with my kernel. Different rules than with GeeWiz 2.x :crying: The decision to use the stock partitioning and support Samsung RFS was the main driving factor at first, but over time the ROM baseline and the Kernel baseline became increasingly interdependent for a plethora of reasons.

But ... I do have some good news for today ... I *finally* got Bluetooth working on Android 4.2! Turns out after all this time it was the same exact stupid problem I had under 4.1 (and spent an equally ridiculous amount of time figuring out). It was just buried in a completely different place. I'm gonna take a crack at solving whatever the underlying cause is (probably need to update something in the kernel) since it's not a trivial change this time. The problem is that Bluetooth Low Power Mode cannot be enabled without it taking a dirt nap a few seconds later. Worst case is that it would work about the same as it does under 4.1 right now, and I haven't seen any complaints about BT power consumption so if I don't make any headway I'll apply the change and finally get "GeeWiz 3.5 Beta" out here for you guys. [GeeWiz 3.4 is reserved for a final Android 4.1.2-based build to roll-up all patches -- I intend to maintain both for a while since I think 4.1.2 suits 'GeeWiz Media' better than 4.2 does]

So many version numbers up there I lost track myself! LOL.
[Fascinate Android Development] Cookiemonster21:
I've got an idea, but not being a developer I'm not sure how simple this would be...

I really like the looks of touch wiz, but stock roms are awful and I love jellybeans speed. Anyway that you can make a theme for this? There's definitely no pressure, just wondering if it is remotely possible, and if its something you would even consider. Thanks anyways!
[Fascinate Android Development] djp952:
I'm not really ambitious enough to get into themeing, for this ROM I've even shied away from custom battery meters (although they can be made with an online tool that come to think of it I promised to link up and never did - doh). I don't have any problem with it, but from what little I do know there is a lot involved if you venture beyond just changing the graphics files and XML resources (lock screens, the dialer, the status bar, the launcher, etc). The Android code isn't laid out very well (just my opinion), and rather than put all the look and feel stuff into one place that could be swapped out easily, it's intermixed with base code, which is why applying themes can break ROMs they weren't designed for. In an ideal world, themeing should be easy, and it does bother me that Google hasn't addressed that yet since every single OEM does it (and most custom ROMs, too!). You would think it would save the OEMs a ton of time and money.

I try hard to never say "no" to anything, but it's doubtful that I would ever have the ambition to theme this. Stranger things have happened, though ... I change my mind all the time!! :laugh:

I really do wish Android was more modular so generic themes could be developed and then utilized by everyone without the need to worry about breaking custom code. One thing I wanted to do here, but have yet to even attempt, is to modify the system so that you could put .zip files on your SDCARD with battery meter images and have them selectable through Settings, as if they were a ringtone. Something like that could ultimately be extended to all the system graphics and resources ... kinda like an override. It wouldn't solve all the details involved with a good theme (at first?), but it would be easy for people to develop themes and if done properly wouldn't ever break anything. Maybe someday!
[Fascinate Android Development] Cookiemonster21:
Thanks so much for giving it a thought. I guess I'll start to do some looking and give it a go myself.
[Fascinate Android Development] djp952:
GeeWiz 3.4 has been uploaded and posted to the DOWNLOADS section of the first post.

GeeWiz 3.4

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

Mostly fixes the compass (GW Patch 3.3.1)

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

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

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

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

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

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

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

For the most part this is just a roll-up of the three GeeWiz 3.3.x patches, but it finally addresses the long-standing issue with the Ringtone/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 ringtone/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] Cajaks2:
Hey all,

I flashed an fascinate with this Rom with Odin and current its patched at 3.3.2. I've given the phone to a friend who has reported several problems with it.

It spontaneously shuts off. sometimes in the middle of the phone calls sometimes when its sitting on the table.

It also does not send/receive call audio when an incoming call comes in, she has to call them back to make it work.

Snapchat also fails to work on occasion but that may well be snapchat's fault.

Any ideas guys?
[Fascinate Android Development] djp952:
Shuts all the way off, or reboots? I've never seen a Fascinate actually power down, but I've certainly seen them reboot for no good reason (the latter usually as a result of something I've done - lol) Could it be a loose, or perhaps failing, battery? Safety first: make sure the battery isn't puffed out in the middle at all, it should be perfectly flat on both sides -- immediately cease using it if it's not!

I'm not really sure what else would cause it to just power off like that, "random" reboots are typically the norm for software troubles. Did you by chance turn on either of the Settings/Advanced Clock Speed options? Lock-ups are what I would commonly think of for an overclocking problem, though. Best guess is battery, sorry that I've never seen that symptom before.

As for the call issue, there was a report on GeeWiz 4 that there was no call audio when dialing from contacts as well. I haven't been able to reproduce that or this, but I will keep trying. Is it on every single incoming call? Any VoIP software installed?

But please, as silly as it sounds, please have them check the battery, if it shows any physical signs of failure it could actually be dangerous.
[Fascinate Android Development] Cajaks2:
I was thinking battery as well but there appears to be no external signs of damage. It is an older phone so the battery could certainly be failing. Every setting is stock. She claims it is on every call. At this point I think I am going to flash the gingerbread based GeeWiz this weekend and see what happens if that resolves anything.
[Fascinate Android Development] djp952:
I don't know how deep you want to dig into this since it's a friend's phone (and they probably expect to be able to use it), but if you'd like I can build a version of the audio module for this version of the ROM like I did here:

http://xdaforums.com/showpost.php?p=36748252&postcount=31

It's not hard for me to do, actually it takes about 10 minutes from start to finish, including making the rollback patch, but you'd need access to the phone to run ADB and capture the events during the course of the problem and be able to examine them.

Or ... if I made the patch and it was installed, you guys could send me a Bug Report on it as well (Settings/Developer Options/Take Bug Report). This includes a LOT of information, I cannot guarantee that nothing personal is in there, but there really shouldn't be. Heck, you could have her do that now if you want, perhaps the answer is already in there! If you do want to take a bug report, what will happen is a whole lot of nothing, or so it will seem, for about 3-5 minutes. You'll probably see a few "shell has been granted root permissions" pop-ups, but otherwise the phone makes a tone, gets real slow for a few minutes, and ultimately pops up in GMail with a draft message. By default, it will send to yourself, just forward it to ... well ... I'll PM ya. You can probably figure out my gmail address if you think REALLY HARD about it - LOL. Perhaps djp952@? :eek:

Let me know what you think, I'm happy to make the patch to enable the extra logging, but only if you want to use it. I cannot guarantee that it would reveal the issue, I'm hoping more for a clue :) I'm beginning to wonder if the "fix" I did in GeeWiz 3.3.1 to address a possible but extremely unlikely condition with in-call audio was ill-conceived for some reason. I reviewed it again and it looks OK, but I'm thinking this has to be my fault somehow ... too weird to not be!
[Fascinate Android Development] djp952:
For what it's worth, I got a report of seemingly the exact same problem with GeeWiz 4 today and while I still cannot duplicate it, I decided to just try a couple changes to the audio code for that version to see what happens:

http://xdaforums.com/showpost.php?p=36816170&postcount=34

One possible difference is that the GW 4 user noted that he can enable and disable Speakerphone mode to solve the problem without a need to call back. This is worth passing on for her to try, it still sucks but not as much, I think.

I'm hoping that user will be able to test and get back to me before the weekend, and if it's successful I will make the same change available for GeeWiz 3 as quickly as possible, even if it's "experimental" in nature. I appreciate that you have a limited window of opportunity to either fix or get rid of GeeWiz from your friend's phone, and while I'm hopeful that a resolution can be found in time, I suggest at least considering replacing GeeWiz 3 with a CyanogenMOD or AOKP-based ROM.

That may sound counter-productive for my own interests, but I'm a realist about this ... if GW doesn't work out for you, I'd much rather see you dump it for something that works for all your needs than having to deal with waiting for a problem the developer can't even find yet to be "maybe or maybe not" fixed :p

I still got no clue on the power-off issue either. I asked around a bit this afternoon, and nobody I pinged has ever seen a Fascinate just power off like that -- it's always reboots or lock-ups. Hopefully just need to replace the battery or clean the contacts or something simple like that. Crossing my fingers for ya :fingers-crossed:
[Fascinate Android Development] djp952:
edit: removed update 3.4.1 ... my phone locked up entering deep sleep after applying that. My apologies.

Thankfully nobody downloaded it before I found the issue. *phew*
[Fascinate Android Development] moparfreak426:
Re: [ROM][KERNEL][JZO54K][01.12.2013] GeeWiz 3.4

Getting this rom for a friend

Sent from an Apple killing JellyBean
[Fascinate Android Development] djp952:
Cool! Just a heads-up, while I haven't been spending much/any time working on this due to all the problems/glitches with the newer Android 4.2 version, I did want to let you know that at least one person has had problems with this ROM having muted in-call audio. if this happens, try switching to speakerphone and then back again. It wasn't a wide-spread issue with this version, but it exists.

I've been working the problem on the newer GeeWiz 4 baseline since it had far more problems relating to in-call audio. When I get that sorted out, those changes will be back-ported to this version. Hopefully more successfully than the mysterious 3.4.1 patch I posted and immediately deleted :D (It solved a problem that is extremely rare on this version, it wasn't worth the problem it ultimately caused).

I hope your friend likes it -- thanks!
[Fascinate Android Development] moparfreak426:
Re: [ROM][KERNEL][JZO54K][01.12.2013] GeeWiz 3.4

Any other bugs? Shes bone stock can i just do the odin all in one install u have posted and have everything needed?

Sent from an Apple killing JellyBean
[Fascinate Android Development] djp952:
That's the only important one I can think of, and to date only 2 people have experienced it, so chances are she won't. Just wanted to give you the heads-up there.

If she's stock, yes, just ODIN the "full wipe" and she'll be good to go! Nothing special needs to be done in advance.
[Fascinate Android Development] moparfreak426:
Re: [ROM][KERNEL][JZO54K][01.12.2013] GeeWiz 3.4

Alright.... Sorry for so many questions but one more... I think the original galaxy s is single core and does that mean it cant deep sleep? Hows battery life compared to say on stock with everything turned on?

Sent from an Apple killing JellyBean
[Fascinate Android Development] djp952:
Fascinate is definitely single core, deep sleep works, and battery life is pretty great IMO (previous versions were so-so from mistakes/bugs), from what I've heard it's the best there is for Jelly Bean on the Fascinate! From my experience, the biggest battery killer is Wifi, closely followed by a paired Bluetooth device and then an attached 4-pole headset (it constantly monitors for button presses). It won't be as good as stock Gingerbread was, don't get me wrong, but I think it's comparable to stock regardless of what's turned on and what's turned off. If you guys find otherwise, please let me know, maybe I can fix it.

For what it's worth, on my test device with the original battery from 2010, with wifi and bluetooth turned off and a decent 3G signal, I see something like a 6% drop overnight. I think that's about 2-3% worse than stock, but these OEM batteries are getting old, any difference could very well be from age.

If for some reason this doesn't work out for you, I highly recommend seeking out a ROM from jt1134 for the Fascinate (check "rootzwiki"). His stuff is top-notch and given that it's based on CyanogenMod rather than pure AOSP, it will have more features as well as the support of more than just one person :silly:
[Fascinate Android Development] djp952:
ROM has been retired

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 4" was able to duplicate it's feature set, and as of GeeWiz 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
[Android Q&A, Help & Troubleshooting] jmiller1x:
how do you root a LG Optimus Zip

Model number LG L75C

Carrier Straight Talk

Android version 2.3.4

Kernel version 2.6.35.7

if mor info is needed let me know what you need please and sorry im such a noob
[Android Q&A, Help & Troubleshooting] mesiahthegreat:
Bump..

I have the same phone. VS700 is another number which may help in determining root method. It's what the LG software for PC recognizes my phone as when connected through USB. It has an ERROR trying to read the SW Version though. Help!
[Android Q&A, Help & Troubleshooting] acerkumar:
Try unlockroot

http://unlockroot.com/
[Android Q&A, Help & Troubleshooting] shanuck:
What I used

I had no problems on this exact setup with Poot and installed SuperUser. :good:
[Android Q&A, Help & Troubleshooting] androidteen:
LGL75C

I have Lgl75c from straightalk and i have it rooted but i need a rom for it its uses gingerbread firmware any help?
[Android Q&A, Help & Troubleshooting] TommieIV:
LG L45C

I have the LG L45C and I cant seem to find a way to root it. This phone is several years old its running Android 2.3.4. Can somebody give me some solid instructions for rooting it?
[Motorola Photon 4G] lincthra:
I am on the Jokersax cm10. Have been for months. The wifi was working when I went to bed. I've tried rebooting. I've tried wiping my cache. I've tried reflashing my rom. I didn't change anything wifi related before bed. I've enabled and disabled airplane mode. I've disabled and reenabled wifi. This is a strange one. OH, and it will SCAN and find wifi networks (so the wifi isn't totally bad), but when I try to connect it always goes from "connecting" back to not being connected at all no matter what network I try. Also, the icon never shows up on the notification bar.
[Motorola Photon 4G] rbeavers:
The last time I had the same problem I had to reboot the WiFi router.
[Motorola Photon 4G] MIONS:
Try wipe all and reflash ithink it will work
[Motorola Photon 4G] lincthra:
Ding ding, we have a winner. I'd hoped to avoid doing a total wipe, but that fixed it. Thanks guys.
[Asus  Eee Pad Transformer Prime] neophyte06:
Hey guys,

some days ago I recieved my new Transformer Prime 32GB with Tablet Dock. I've heard from the strong hinge of the Keydock, but if I unboxed it and tried it out I was shocked that it was so loose.

I searched hours for a solution on the web but sadly I had no success

Today finally I disassembled the hinge without any informations about doing this like this:

1. switch the dock into a 90 degree position and unscrew the two torx screws on the backside

(this was the easy part)

2. there are two decals on the inner side of the dock to (partly) remove

if you remove the small one, there is only one screw underneath.

under the big stripe there are 4 - excluding the connector screws - to remove.

3. if this is done you got to use a caseopener tool or anything like that to remove the backside of the dock slot

4. finally you got to fit the four screws you can see now

5. now you should fit everything back togeather and try if it helped, for me it did

maybe some photos will come

so, what should i say as a german guy

Happy Screwing ;D
[Asus  Eee Pad Transformer Prime] tuckersmission:
Some pics or maybe a video would be sweet! My dock hinge has become gradually more and more loose over time.
[Asus  Eee Pad Transformer Prime] ian1:
Ya same
[Asus  Eee Pad Transformer Prime] schlesh436:
Yes please willing to donate
[Asus  Eee Pad Transformer Prime] neophyte06:
here are 4 fotos of the disassembling. I hope this will help you understanding what i wrote ;)

hxxp://imageshack.us/photo/my-images/210/20121019185856.jpg/

hxxp://imageshack.us/photo/my-images/248/20121019185605.jpg/

hxxp://imageshack.us/photo/my-images/853/20121019185553.jpg/

hxxp://imageshack.us/photo/my-images/9/20121019185441.jpg/

sorry i'm a new user, so i can't post any foreign links, please replace the "xx" with "tt"
[Asus  Eee Pad Transformer Prime] t-jet:
Went ahead an embedded the pictures, two of the already disappeared in the nirvana of the internet.
[Asus  Eee Pad Transformer Prime] WojtekX:
Please reupload pic.

Wysyłane z mojego Transformer Prime TF201 za pomocą Tapatalk 2
[Samsung Epic 4G Touch] jwitt418:
Ok, just came over from the Evo and flashing roms on S2 is wayyy different so please help.

1. I rooted.

2. Installed Clockwork recovery

Im on 4.0.4 and FH13

so......

Wondering if this is safe to do to install CM10

Should i flash this kernel in moblie odin http://xdaforums.com/showthread.php?t=1781939 , which is [Kernel][AOSP][ICS] Safe CWM6/TWRP

pull battery during reboot and boot into recovery and flash...

http://xdaforums.com/showthread.php?t=1810315 , which is [ROM] CM10 alpha5.3: Android 4.1.1 for Samsung Epic 4G Touch

??? is this right. If there are different files i should use please point me in the right direction

Agian, Im not a rookie to root and android, but this is way different than Ive been doing for the past 2 years. Thanks in advance for any help.
[Samsung Epic 4G Touch] MiguelHogue:
I personally just mobile Odin the el26 kernel.. Boot into recovery holding power+volume up & flash the Cm10 rom you listed

That way had never failed me

-TeaM VeNuM Like A Boss
[Samsung Epic 4G Touch] jwitt418:
I have the EL29 kernel is that safe to use?

Again I'm currently on Android 4.0.4 so will that be an issue when mobile Odin that kernel
[Samsung Epic 4G Touch] MiguelHogue:
I believe that's safe to use.. It's gb so you should be fine.. I just always do the el26

& that's not an issue.. That's why you boot straight into the recovery to flash...... Once you flash the Cm10 rom it includes the kernel so the jb build will boot

-TeaM VeNuM Like A Boss
[myTouch 3G Slide Q&A, Help & Troubleshooting] dnemeth2:
With faster launcherand better apps :)

I will give download link, when i test the ROM :)
[myTouch 3G Slide Q&A, Help & Troubleshooting] rafflars:
When will it be

jd

When will it be then
[myTouch 3G Slide Q&A, Help & Troubleshooting] MC MILK:
where's the link?
[RAZR HD Q&A, Help & Troubleshooting] tomkiley:
Anyone know if the Verizon version that was just released also supports GSM and if it's unlocked. I'm planning to use it mainly on Verizon, but would like to be able to pop a SIM card in if I travel.

From what I've read on other Verizon phones - they have to leave 4g devices unlocked as part of their winning the 700MHz spectrum.
[RAZR HD Q&A, Help & Troubleshooting] overlord727:
I am curious about this too. I am on AT&T and know that the Canadian version should be fully compatible even with LTE, but its much harder to purchase than a VZW one.