yashsingh1/xdaforums huggingface dataset:
[Captivate General] bobapunk:
Can you get to the market?

I had a similar problem the other day and luckily, a notification popped up indicating that I had updates for aps available. I got the to the market from the notification pull down menu. Once there, I DL'd "Launcher Pro" and "Home Switcher". Once they were both installed, I launched "Home Switcher" from the pull down notification menu and switched my default launcher to "Launcher Pro".

If you can get to the market, this might work for you too.
[Captivate General] newter55:
You can use adb to install another launcher or create a cwm zip file to flash in recovery which will copy the apk. Also, as the other poster stated, getting into the market you could dl another. Not sure if using the market website on your computer would work as I haven't used the feature but it may.
[Captivate General] modest_mandroid:
Yeah, what those guys said, try going to http://market.android.com on your computer and see if you can push some other launcher to your phone. If you can't and everything else fails, and you want to try repairing your rom without losing your data, you can download the cwm flashable zip of the rom you're running and edit the update script in META-INF to not format the data partition, then reflash the rom. Pretty sure that'd work on any 2.2 based rom, not sure how well that'd go over on CM7.
[Captivate General] E_man5112:
Thanks for the responses. The web market would probably have worked as well. I ended up remembering I had swipe pad enabled, and just changed a box to settings. Was just coming to update the post. Wish android had a feature that would, if an app launched and closed x number of times, it would stop launching it/clear it from defaults.
[Hero CDMA Q&A, Help & Troubleshooting] Bierce22:
Hey so I finally figured out how to bridge my conectiob from my phone-computer-ps3 using an eithernet cable but for somereason when playing mw2 online my download never seems to go above 60kbs and it starts lagging really bad I must be missing something here because when I do Normal browsing on my computer I can get around 800-950kbs thanks to kifnos build but it gets no wear near that while playing online is there something I can do on the computer side to speed it up or on the app itself I'm running asop 9.9.2 kifnos build. .8 and win7 Prem64bit also I use wireless tether pre 11
[Hero CDMA Q&A, Help & Troubleshooting] oohaylima:
Ah man. There's a guy on here who has asked a similar question. He's looking into it. Let me see if I can find his thread.
[Atrix 4G General] theark1:
Just got the motorola atrix, and i recently dropped it in a sink,but it wasn't filled up with water. It seems fine, but every so often it shuts off, and I can't turn it on without removing the battery and putting it back in. Should I get it exchanged?
[Atrix 4G General] shamdawg:
Yes, you should exchange it.
[LG Optimus 2x] DocRambone:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP990/AVIPDW/1.0/EN_LG-P990_SVC_ENG_110216.pdf

from this very nice post:

http://www.optimus2x.net/index.php?topic=393.0

A real gold mine :D
[LG Optimus 2x] xmoo:
Thank you very much!
[LG Optimus 2x] eqzgkxokwa:
Is that a 2x p990 manual or a su660 manual?
[LG Optimus 2x] xmoo:
If you'd take a look you would have seen that it is the p990 version.
[LG Optimus 2x] Puskash:
New, valid links

Originally posted link is broken. But since this is a crucial stuff, I've searched and found these:

http://uploaded.net/file/jilg8fg2

or

http://freakshare.com/files/b5wghl77/EN_LG-P990_SVC_ENG_110216.pdf.html
[Galaxy S I9000 Q&A, Help & Troubleshooting] tizaktizak:
i just bought a sandisk 16gb micro sd card...

is there any file system that i can format the card to so the phone can read files larger then 4gb from it??

pls dont ask "why do you need to..."
[Galaxy S I9000 Q&A, Help & Troubleshooting] tizaktizak:
Anyone pls...
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
Find out if the phone can read exfat files . Format your card to exfat .

jje
[Epic 4G Q&A, Help & Troubleshooting] imtjnotu:
Have to take m phone to the sprint store ad need it badly(speaker is broken)
[Epic 4G Q&A, Help & Troubleshooting] dustinmatthews87:
Wrong section, Ill help anyways.

http://xdaforums.com/showthread.php?t=853209
[Epic 4G Q&A, Help & Troubleshooting] NEXUS 4G:
Question. Y would u want a rooted version if ur going to the store.
[Epic 4G Q&A, Help & Troubleshooting] imtjnotu:
I need the .zip to flash not odin...don't have a computer...who has the zip to flash thew clockwork
[EVO Shift 4G General] rhodiggah:
Saw this on twitter if you haven't already. Speedy (Evo Shift) has been merge with CM7...

Sent from my Speedy Knight Evo Shifted PG06100 through the XDA app
[EVO Shift 4G General] pengkha:
any issues with it so far?
[EVO Shift 4G General] epitaphromance:
They havent added us a thread in thier forums yet :( patience

Sent from the pot.
[EVO Shift 4G General] rhodiggah:
Here are a couple of pics from my ****y...CM7.

Sent from my Speedy Knight Evo Shifted PG06100 through the XDA app
[EVO Shift 4G General] riggsandroid:
You called your phone a ****ty. :D
[EVO Shift 4G General] rhodiggah:
Stoopid predictive texting haha... that was hilariuos.
[EVO Shift 4G General] toastcfh:
http://mirror.teamdouche.net/?device=speedy
[EVO Shift 4G General] androiddummy:
So is the headset fully functional in this version?
[EVO Shift 4G General] rhodiggah:
thanks to TOASTCFH n friends, the nightlies are up n going...
[EVO Shift 4G General] epitaphromance:
Not see a nightly in rommanager...yet.

Sent from the pot.
[EVO Shift 4G General] edgemaster191:
so awesome :) i know what i'll be doing at work today :-D
[Android Software/Hacking General [Developers Only]] mino.cruiser:
I purchased the tablet Flytouch3 and found some big flaws, I would like the expert advice of Android 2.2 devices

The tablet has the following problems also confirmed by other users:

1) Do not support any 3G internet-key, unlike older models that support such as Huawei E1750 and some other usb-key .....

2) the maximum volume of the speakers and factory set so low that it must be to listen in silence .... for example my phone looks like a home theater in comparison to 2000 watts

3) The manufacturer claims such as 4GB of memory reserved for the operating system 2 gb and 512 mb of ram .... but if I run a check with any software will not detect the 4 GB of memory do the 512 ram

4) The wifi reception is not the best ....

Do you see that problems can be solved with a firmware update or advise me to sell the tablet?

I thank in advance all those who want to help me ....

Greetings from Italy
[Android Software/Hacking General [Developers Only]] TrueYears:
I am interesting in this as well as I am about to a cheap tablet and dont wish to spend over 500 in one
[HTC Inspire 4G] Imaano:
Does anyone know any other apps that can take screen shots with a rooted phone besides PicMe and ShootMe?
[HTC Inspire 4G] kgeissler:
http://www.androidcentral.com/taking-screenshots-without-root
[HTC Inspire 4G] harolds:
Shootme in market.
[HTC Inspire 4G] bella92108:
I like Screen Shot It, available in the market, but like anything its all about personal preference. I had issues with Shootme, but many love it.

Try em all, pick your favorite. :-)
[HTC Inspire 4G] kirk123:
Yes, I agree with Bella. Screen Shot It is really good. Has the option to save as JPEG or PNG. Really easy to use also.
[HTC Inspire 4G] bella92108:
The only downside is it buries the images, which I can't for the life of me find a way to point the save-to directory elsewhere. But small price to pay for a solid app in my opinion.
[HTC Inspire 4G] kirk123:
Yes, this is true. It does allow you to crop, share or save the screenshot after its done. Share option is handy if you want to post it on facebook, flickr, email, mms.....

Edit: Also, the screenshot images show up in gallery so this way you don't have to go digging for the images.
[HTC Inspire 4G] mudknot2005:
I use dropcap2

App
[HTC Inspire 4G] eric70634:
I use an app called screenshot...its free...shake to screenshot option which I like
[HTC Inspire 4G] Twenty4:
Same one I use, works very well.
[Epic 4G Android Development] codest3r:
Brilliant! Great job! :)

Sent from my Epic 4G on XDA App
[Epic 4G Android Development] feefeeboomboom:
odd i have never had this "bug" on EB13 or at all.
[Epic 4G Android Development] aleph23:
Mkasick, Samsung really should be paying you.

Thanks for this and all the other slack you've picked up for them.

I'm going to reboot and see if TWS is affecting me today. If so, I'll install and report back.

EDIT: ok, here's what happened.

renamed /system/framework/framework.jar to framework.jar.bak

Copied your framework.jar in it's place.

Rebooted. This took an exceptionally long time.

Turns out this cooked my sd card. The directory structure is full of strange ASCII characters. I now have 14 gigs free where I used to have 8.

So I've reverted back to my backup framework.jar for now. Future testing will take place with the sd card removed! :)
[Epic 4G Android Development] mkasick:
Right, I should've mentioned it before, but since this replaces framework's classes.dex, it will force most of the dalvik cache to rebuild, so the first boot after applying probably will take a while. It's also not a bad idea to explicitly clear the cache too before rebooting.

Yikes, oh dear. I don't think the patch should do that, unless it tickles another bug that "fries" SD cards. Presumably if you reformat the card it'll be fine, but my apologies for not warning about the data loss.

Aside from the SD card issue, did it manage to boot fine? Or did you stop mid-way through?
[Epic 4G Android Development] snowmanwithahat:
I actually have experienced on the ACS EB13 rom a real TWS issue where it cycles the radio connectivity (I'm in a good coverage area) and it truly does have a signal only about 50% of the time. I don't think you've experienced quite the same thing as me when you've experienced the TWS bug apparently.

It does seem to have a real impact on battery life, I have not yet tried your patch, but I definitely appreciate the fact that you're taking a look at this, that's awesome! :D
[Epic 4G Android Development] jbadboy2007:
You are doing some pretty awesome stuff. Keep up the good work.
[Epic 4G Android Development] iamchocho:
I'm in vienna austria all week so I won't be able to test for obvious reasons but many many thanks for looking into this issue. Its good to know that we have you looking into the difficult issues that samsung can't seem to ever fix.

Keep up the geat work, looking forward to having one more annoying samsung bug squashed thanks to you.
[Epic 4G Android Development] aleph23:
It did boot fine.

Some of my apps wouldn't open, so I didn't continue the test. No, not just the sd card apps. But probably apps with sd-dependant files.
[Epic 4G Android Development] k0nane:
You say "smali", I say "in the next SRF release". ;)
[Epic 4G Android Development] djbacon06:
this is probably the best news I've heard all week. This TWS bug has been driving me up the wall, because it is pretty much the only problem I have.

I believe I will wait to test this until ec05 officially rolls out, maybe (doubtful) they addressed this in the new build. But either way, mkasick, THANK YOU for your work. I am so glad developers are looking into this problem :D:D:D:D
[Epic 4G Android Development] mattallica76:
This has been successfully incorporated into Bonsai 4.0.0 and seems to be working.
[Epic 4G Android Development] musclehead84:
Mkasick you are a beast. Nuff said

Sent From My Evo Killer!
[Epic 4G Android Development] mkasick:
So, for the record, the actual bug is in Google-written AOSP code. Due to the "racey" nature of the bug, it's not surprising that only Samsung radios tickle it. That's not really their fault though, so they get a bit of a pass on this one.

That said, I would encourage Samsung to release all of their AOSP core framework modifications in subsequent platform source releases. This bug was relatively easy to find since it's in AOSP. Had it actually been in Samsung-modified code, it would've taken a lot longer and a lot more staring at baksmali output.

I understand keeping TouchWiz proprietary, that's fine. But even though Samsung isn't obligated via license to release platform modifications, there's no good reason not to and it would be a sign of goodwill towards community.

Edit: I should mention that the bug appears to be fixed in Gingerbread (AOSP) as a product of a bunch of the BatteryStats code being rewritten.
[Epic 4G Android Development] mkasick:
Cool, thanks!
[Epic 4G Android Development] dr_gibberish:
Hate to be a nay-sayer but I installed Bonsai 4.0 this morning and just looked and my TWS was 96%!!

However, what was not clear to me was whether the battery was draining. Normally the TWS bug has absolutely been connected to poor battery life for me. This time, however, it was not so clear, as I am 10 hours running and still at 50% battery left. (Though it was plugged into the computer for a few minutes this morning while I Odin'd and copied the ROM over.)

Anyhow, I just rebooted (first time since installing bonsai this morning) and will not toggle airplane mode or update PRL and see if the TWS bug is still there. I'm hopeful it will work after a reboot...

EDIT: So it worked no better after reboot. Let it sit for an hour and was again above 90% and this in an area where I have decent signal. Toggled airplane mode and it began dropping and is now at 65%. The battery issue is just harder to tell. I always feel like there are so many variables that I just cant judge. My subjective sense - battery life is generally better in Bonsai 4.0 but has been even better since I did the airplane mode toggle. Especially when the phone is just off and idle.
[Epic 4G Android Development] xxmastermindxx:
You're definitely right about it being fixed in Gingerbread. I had been running CM7 from the day our team released it and my TWS never went above 5% or so. I'm back on Syndicate and my TWS will randomly remain at 50-51% until I airplane toggle.

Anyway though, thanks for your excellent contributions to the community! :)
[Epic 4G Android Development] dps33:
Where and how can you see what TWS is or at?
[Epic 4G Android Development] KennyG123:
Settings. About Phone. Battery use. Cell standby.
[Epic 4G Android Development] KennyG123:
Mine was at 90% on Bonsai 4 as well.
[Epic 4G Android Development] mattallica76:
My TWS peaked at 8% today, but is down to 2% now. I've never noticed a correlation between TWS and battery life though.
[Epic 4G Android Development] dr_gibberish:
I should also note my upgrade process as that may be related to why I still have it on Bonsai 4.0 -

1 - Started on Bonsai 3.01 and had the TWS bug badly

2 - Odined the EC05 modem this morning (which did not wipe Bonsai or any of my apps and data)

3 - Installed Bonsai 4.0 through CWM 3.06 (Went flawlessly FYI, but perhaps this carries over something related to the TWS bug?)

Unfortunatley, I cant afford to really start from stock right now. Just dont have enough time to mess with it this week. Did anyone who still has the bug go back to stock?
[Epic 4G Android Development] robl45:
i switched from bonsai 3.0.1 to acs 1.0.2 tonight, never had the issue with bonsai but i have it with acs. do i just flash this zip in clockwork?
[Epic 4G Android Development] mkasick:
When this happens, can you report your "Time on" for "Cell standby" and the "[time] since unplugged" values (the latter on the main "Battery use" screen)?

90%+ TWS is new. It shouldn't be an artifact of the patch, although I'll take another look. Hopefully it's not a legitimate problem with the EC05 modem.
[Epic 4G Android Development] mkasick:
No, it's not a flashable zip. It's probably easiest to wait until the next SyndicateROM Frozen release.
[Epic 4G Android Development] dr_gibberish:
Glad to do this next time. Maybe I will reboot in the morning, not toggle airplane mode and report back. FYI, I am actually in a crappy service area most mornings so I always assumed these high readings were a combo of the 50% TWS bug and 40+% "real" time without service. That said, I dont think I generally had numbers this high before...
[Epic 4G Android Development] gmorf33:
i regularly have 76% TWS at work, but that's because i'm in a basement with 0-1 bars of signal all day long. On the weekends the highest i usually see it is 4%. This all seems like normal behavior to me, no bugs. So those noting high TWS due to the bug, make sure you actually have a good signal where you're at. You can check your signal strength in Settings > About Phone > Status. I'm currently at -105 dB which is terrible. Higher is better (obviously)
[Epic 4G Android Development] abrognlie:
I normally have 4-5 bars at my house, but when the TWS bug kicks in it will set at 50% for no good reason. I would imagine most people experiencing the TWS bug have similar circumstances, otherwise they would chalk it up to an actual bad signal like you.
[Epic 4G Android Development] mkasick:
In an amusing irony, actually being without service for even a brief time resolves the TWS bug until the next reboot, much like airplane mode does. One of the requirements for suffering from it for an extended length of time is keeping the phone in a "poor" or better (-100+ dBm) service area throughout.

Also, here's how signal strength (in dBm) maps to strength bins:

GREAT: -75 and above

GOOD: -85 to -74

MODERATE: -95 to -84

POOR: -100 to -94

NONE_OR_UNKNOWN: -101 and below

I don't know what the lower-bound signal-strength threshold is for the radio cutting out, but if you do have service and you have a "Signal strength" (Settings -> About phone -> Status) of -101 dBm or less, it will count as TWS even though you do technically have signal.

That's just how it works.
[Epic 4G Android Development] Poryhack:
I swear I have experienced the TWS bug several times on my Epic running CM7 alpha which is Gingerbread based. Are you sure the bug is resolved in Gingerbread?
[Epic 4G Android Development] mkasick:
In determining whether I should've filed a bug report, I briefly looked through the AOSP base framework git repository to see if the bug was still present in the latest commits, and saw that the relevant code had largely been rewritten prior to Gingerbread's release.

As far as I could tell, the specific bug this patch fixes is not present in Gingerbread. I didn't check the code exhaustively however, so it's possible that a bug with the same manifestation was introduced elsewhere.
[Epic 4G Android Development] KennyG123:
Reinstalled Bonsai 4.0.0 and used Mammon's clock restore instead of am/pm restore, did not change any boot ani's and on the 5th reboot so far and TWS bug is still gone! Nice job!!!!!!!
[Epic 4G Android Development] poit:
I hate to ask this of someone who already works his butt off for this forum, but any chance you could compile this code fix into the stock EC05 kernel? (Like you did with the camera FC bug and EB13) I'm on the stock EC05 ROM right now, and still get hit with TWS regularly. I would be good test bed for the code change. :D

Edit....reread the OP and I guess it's not a kernel thing. Nevermind
[Epic 4G Android Development] Poryhack:
I wasn't 100% sure of myself before but I've just experienced it again. After 1 day I'm at 54% TWS.
[Epic 4G Android Development] mkasick:
I can post a stock EC05+fix framework.odex, but it'll have to wait until the EB13-to-EC05 update hits since making the odex requires running EC05 on my phone.

What's your signal strength?

Also, CM7 uses the new Gingerbread battery stats with the fancy graphs right? Or is it the old Froyo one?
[Epic 4G Android Development] Poryhack:
Not sure if this is quite what you were looking for, but my signal strength is good. Certainly not poor enough to cause that much TWS.

And yeah, it uses the gingerbread battery stats.
[Epic 4G Android Development] poit:
I think that would be awesome, and it would also go a long way towards a final confirmation of this bug fix. I'm assuming this would just require swapping a few files in the framework dir.
[Epic 4G Android Development] squshy 7:
Mkasick, I really admire you and your troubleshooting skills :) I'm amazed by the fact that whenever I see your name credited in someones ROM, all your fixes have a (kernel) tag...I wanna see what you could do cooking up your own kernel ;) Ever give any thought to that?
[Epic 4G Android Development] XtaC318:
Has this bug been reported across all Galaxy S devices with touchwiz running?
[Epic 4G Android Development] mkasick:
Specifically, is your "Signal strength" as reported in Settings -> About phone -> Status (at least, that's where it is in EB13/EC05, not sure about CM7) in the -70s dBm, -80s, etc.?

You're probably right, and there's something still up with Gingerbread. I'll poke at the CM7 source tree when I have a chance and see what I can figure out.

To help, when you do have TWS, can you report your "Time on" for Cell standby, as well as the time "since unplugged" on the main "Battery use" screen?

Thanks!

I have thought about it, and I think I've concluded that the skills useful for maintaining a kernel, ROM, etc., aren't exactly the same as those for troubleshooting problems in unfamiliar code. In recent times, it seems the latter is the type of work I gravitate towards, both here and in other projects.

So while I'm glad to contribute fixes, I'm not sure I would do any better, or frankly even nearly as good of a job maintaining a kernel/ROM as other folks around here, who do a wonderful job as it is.

I'm not aware of it. Although, it wouldn't surprise me that the behavior of other devices (i.e., with GSM radios) incidentally don't provide the conditions necessary for this bug to trigger.
[Epic 4G Android Development] poit:
This bug has been reported on MANY CDMA android devices. If you do a google search on Time Without Signal you will see reports on many Sprint and Verison android devices. It's too bad that the folks on this forum don't seem to get that and keep blaming Samsung and Sprint for this, because it should be put squarely in Google and AOSP's lap.
[Epic 4G Android Development] djbacon06:
I just wanted to say thanks again. The fix has been incorporated in the latest ACS ROM and is 100% working! I am so happy, thank you mkasick!!
[Epic 4G Android Development] poit:
Bump.....:D:D:D:D:D:D:D:D:D:D:D:D:D:D:D:D:D
[Epic 4G Android Development] twolostminds:
I still blame both Sprint and Samsung as well as Google.

Sprint for allowing this bug to persist across several hardware platforms.

Samsung for ignoring all requests to address this bug (and that includes SamsungJohn)

and

Google for poor QC allowing this to persist over multiple software releases.
[Epic 4G Android Development] poit:
Then you should also blame LG, HTC, Motorola, and all the other Android manufactures, as well as all the other carriers.
[Epic 4G Android Development] mkasick:
OK, I updated the OP with links to flashable "update.zip"s containing this bug fix, along with the ringer volume control vibrate & silent modification, since they both modify the same framework file. Use "deodex" for deodexed ROMs, "odex" for stock, and keep Odin+tar or a backup handy just in case. If you want the forum-attachment version, it's in the ringer mod thread.

I'm not advertising this terribly heavy since the fix has already been incorporated into ROMs and it's probably best to use one of those. But for those who want a (nearly) standalone fix, there you go.
[Epic 4G Android Development] poit:
Awesome. I'm going to try this on my stock EC05/Genocide 0.5a setup right now.

Thanks!
[Epic 4G Android Development] Poryhack:
I'm back after experiencing the TWS bug again. I switched to SRF briefly but even with that factored in this bug seems to happen far less in gingerbread.

That said, I noticed the bug shortly before sending a text and in the time I took to start composing this post the TWS has dropped from 54% to 46%. Purely guesswork here but I think sending the text triggered a fix. That said I don't know if these numbers are of use (as I couldn't get them recorded while the bug was still present) but I will report them anyway.

-93 dBm

1h 3m since unplugged

1h 3m cell standby on