yashsingh1/xdaforums huggingface dataset:
[Sony Xperia T, TL, TX, V] kmad86:
Ok so we purchased this phone a while back and I believe it was the demo phone at a Sams Club. Anyways, we were having some problems with it not responding to a wake from sleep so I wanted to do a factory reset. Now, it asks for a password that I have no idea what it is. I called up and they gave me their store number that they usually use as a password but it was a nogo. On a Galaxy S III it's like VOlume Up and Power then you can wipe data, but this phone I can't get to that menu. Any idea how I can fix this?
[Nexus 7 (2013) Q&A] dclutter1:
Is there a mod to add data transfer speed the taskbar on cm 10 roms? I had a cm based rom on my phone that had this and I loved it. I don't really want to rom surf on my N7 right now so I was wondering if there's a mod to add this functionality to a standard cm rom.
[Nexus 7 (2013) Q&A] Username invalid:
https://play.google.com/store/apps/details?id=info.kfsoft.android.TrafficIndicator
[Nexus 7 (2013) Q&A] n7of9:
Network Monitor Mini, free and paid

edit...lol, it's what the dude above me linked to

mind melded via N4
[Nexus 7 (2013) Q&A] LoVeRice:
Not a mod but a simple app can do this easily: https://play.google.com/store/apps/details?id=com.internet.speed.meter.lite
[Nexus 7 (2013) Q&A] dclutter1:
Thanks for the suggestions guys. I was hoping to find it in mod form, though, because I'd like to have the reading in the status bar, in matching color, right next to the wifi. Silly, I know, but I'm peculiar about layout and aesthetics :P
[Nexus 7 (2013) Q&A] n7of9:
the Pro version of Network Monitor Mini allows all of those things, as well as custom font
[Nexus 7 (2013) Q&A] dclutter1:
It still doesn't quite suite my fancy.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] xaw2:
Hello. Is it possible to get my tablet shipped out or brought to a serves station to get the tablet reset and root removed? Its batt is draining very fast and freezes up on stock ROM. Anyone please help?

Gt-n8010
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] xaw2:
also when it freezes I can't hold down power button to reboot. It has to drain batt.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] kkretch:
Have you tried a factory reset in settings or have you tried an app like Reboot Widget for Root User https://play.google.com/store/apps/details?id=com.francescoaurino.rebootwidget, google play say it will work with my note 10.1

Features

This WIDGET reboot your smartphone in the faster way.

Reboot mode:

- Reboot: your smartphone will be reboot

- Recovery: your smartphone will be reboot in recovery mode

- Fastboot: your smartphone will be reboot in fastboot mode

- Download: your smartphone will be reboot in download mode

This app requires root permission.

.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] xaw2:
Its back to normal now but it will probably happen again. Yes I did do a factory reset. All it did was screw it up a bit no reset at all. I hit retore in settings and it went into boot loader thing, it ran a script thing and rebooted. It booted up with no restore and some features that where removed after the update. But its still updated.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ayeros:
Hi all just a quick question.

I courently run KengaBean GE 4.3 (Version 2.2) and i have a i337m (canadian version of S4 but i was wondering witch Kernel i should take as i dont realy know the diffence on 2 i choosed

If i dont want to overclock and get the most stable and near stock GE 4.3 kernel witch one i should use

KT 4.3 TW kernel or Faux123 Kernel ?

Ty for your opinion
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] FourPointedFreak:
I much prefer KT 4.3 TW because I know it much better than any other. It's trusted. My close circle of friends running this kernel and I all prefer it.
[Nexus 4 Q&A, Help & Troubleshooting] warrenkb:
Am I the only one who has still not received the JWR66Y ota yet?

I did side load my 4.3 update to JWR66V. Am I now off the OTA path? I am currently stock and unrooted.
[Nexus 4 Q&A, Help & Troubleshooting] gee2012:
The OTA is rolled out in batches, you`ll get it sooner or later. Or flash the factory image in manualy in fastboot mode, you`ll have to unlock the bootloader first though.
[Nexus 4 Q&A, Help & Troubleshooting] rpaloalto:
I still did not receive one either, so your not alone. Just hang on a few more days, or you can just flash it.
[Nexus 4 Q&A, Help & Troubleshooting] gotzaDroid:
Yeah.... Just got it and it totally screwed up my phone... Nothing opens, everything just force closes. I power cycled the phone and now it won't even get past the lock screen.
[Nexus 4 Q&A, Help & Troubleshooting] exb0:
Gawd damn. Why is everyone so god damned impatient about OTA updates? I dont remember GN forums having this problem >.>
[Nexus 4 Q&A, Help & Troubleshooting] evilp8ntballer7:
Just use this thread and flash the rom: http://xdaforums.com/showthread.php?t=2419141
[HTC Sensation] yasir4abbas:
Ii have an HTC sensation h boot 1.27.000 s-on....

I want to root my sensation without s-off....can any one guide me how can I use any ROM but mostly cm10.1

Which recovery to use and Plz give the link to that recovery(heard ext4 recovery)
[HTC Sensation] rzr86:
this is what you need

http://xdaforums.com/showthread.php?t=1631861
[HTC Sensation] yasir4abbas:
I can use this method for most roms with firm wire 3.32...their is one confusion I have is kernel and firmware different from each other?

direct q can I install team venom 4+ rom with this method?
[HTC Sensation] rzr86:
kernel and firmware are different things

of course you can install venom 4+ rom

look in my signature;)
[HTC Sensation] Far_SighT:
Read this: http://xdaforums.com/showpost.php?p=35388166&postcount=2.

This should clear everything up!
[MDA III, XDA III, PDA2k, 9090 General] georgegd1:
I am just really bored, and was wondering, does anyone know of any decent free software for the XDA 2s??? any comments would be appreciated
[MDA III, XDA III, PDA2k, 9090 General] cruisin-thru:
http://www.freecabs.de/
[MDA III, XDA III, PDA2k, 9090 General] irblinx:
http://www.pocketpcsoft.net/

http://www.pocketpcfreewares.com/
[MDA III, XDA III, PDA2k, 9090 General] nomadman:
If your that bored, why don't you help some devs test there beta apps?
[MDA III, XDA III, PDA2k, 9090 General] Rick GM:
Plenty to play with here; http://pdafresh.freeweb.hu/main1.htm
[MDA III, XDA III, PDA2k, 9090 General] HDuser:
For problems with boredom and the BA, try buying a BT headset.

Seems to work for most off us.

(please then only post your soloutions not your problems).
[Android Q&A, Help & Troubleshooting] RazerRazer04:
Hello,

I use CM 10.2 on my HTC ONE X and I really enjoy it. However I have a problem regarding group messaging:

I am in a few group messages, mainly consisting of iPhone users, and all they group text are shown as individual threads. If I want to answer into the group message, I cannot do it. I am using FB Messenger for my SMS/MMS, but I looked at the default Messaging app and all the messages are grouped into individual threads also.

I did some research, but I only found some workarounds using apps like goSMS, but I want to use either FB Messenger or the stock one. I found some websites that claim that this issue was fixed with Android 4.2.2, but it doesn't appear to be.

Thank you :confused::fingers-crossed:
[LG Optimus G (International)] nadrojcote:
As the title suggests, I am on stock rom, rooted and bootloader unlocked. I am wondering if there is a custom kernel that works with the stock rom that will allow me to undervolt. I am looking for something with Faux123 like settings. I would really like to have this functionality but prefer to keep the stock 4.1.2 rom.
[LG Optimus G (International)] nadrojcote:
I just installed this kernel and everything seems to be working, only thing I have left to test is MHL.

http://xdaforums.com/showthread.php?t=2200614&highlight=971
[Galaxy S 4 Q&A, Help & Troubleshooting] Andr0id7:
My i9505 has no csc anyone can help me please.??
[Nexus 7 (2013) General] sfhub:
I noticed some folks had perfectly functioning tablets except for the GPS issue and were concerned upgrading to JSS15Q might introduce multi-touch or other issues.

They might currently be on JWR66N or JSS15J and just want the GPS fix and nothing else.

I put together a fix that will accomplish just that.

It has been tested on JWR66N and JSS15J.

I will warn you that I've made my best effort to make sure this doesn't cause additional issues, but you always take a risk when making changes to an otherwise working system, although in this case, I consider it small.

If you are already running custom recovery, ignore the instructions below, just flash as any other update.zip

You need your bootloader to be unlocked.

You need to one-time load TWRP (or CWM) into memory but do NOT need to overwrite your existing stock recovery.

You do NOT need to be rooted.

Downloads

download TWRP custom recovery

rename to twrp.img and place in your adb (platform-tools) directory

copy update-GPS-lock-fix.zip to your tablet's virtual sdcard

Within command prompt in your adb (platform-tools) directory

adb reboot bootloader

fastboot boot twrp.img

Within TWRP

install update-GPS-lock-fix.zip

reboot (do not choose to install SuperSU unless you want it)
[Nexus 7 (2013) General] OJ in Compton:
I am willing to give it a try in a day or two if you don't get enough people to test this, I'd do it now but I upgraded to JSS15Q already so I'll have to reflash the previous version and I have some assignments to finish first.

Sort of off topic, but as someone who had very good touchscreen response on JSS15J and now has minor issues on JSS15Q, is there any way for me to extract and apply the touchscreen settings from JSS15J update into anything in the future? This is assuming that Google uses the touchscreen settings from JSS15Q in future updates since they appear to consider them a "fix".

Anyway, thanks a lot for creating this patch for us.
[Nexus 7 (2013) General] sfhub:
I don't know if the touchscreen firmware is flashed onto the tablet by the kernel persistently or loaded everytime it starts, but the touchscreen firmware is contained in the kernel.

Theoretically you may be able to get JSS15J touchscreen behavior by using the JSS15J kernel with your JSS15Q ROM.

However, if the touchscreen firmware is flashed directly into hardware and the versions can only go up, then you are stuck with the JSS15Q touchscreen firmware.

So basically try flashing the JSS15J kernel and see if the touchscreen behavior changes.
[Nexus 7 (2013) General] chrolmesq:
If my device is rooted, can I just flash it normally?
[Nexus 7 (2013) General] hyperxguy:
It works

Hello sfhub ...

I'm in a unique situation here. I'm on Slimbean beta3 which is based on JSS15Q and the fixes should be in place. However, something

is lost in translation and the GPS issue is still there. So I applied your fixes and (so far) it appears to fix the GPS issue.

I don't know what you did there, can you explain ? Did you just just pull the google fixes off their release ?

Thanks.
[Nexus 7 (2013) General] sfhub:
Yes.
[Nexus 7 (2013) General] sfhub:
I extracted the GPS firmware and made it available to previous releases.

It should theoretically work with any ROM as long as it is based on stock.
[Nexus 7 (2013) General] Tony_YYZ:
You extracted the GPS firmware from JSS15Q?
[Nexus 7 (2013) General] sfhub:
This fix appears to be working well.

Removed testing from title.

Given that the JSS15Q touchscreen firmware is a one-way street, no going back, there may be more interest in this solution to the GPS issue, especially if your touch screen in working acceptably well on JWR66N or JSS15J.
[Nexus 7 (2013) General] hyperxguy:
Navigated a couple of long trips today and worked like a charm.

Thanks.

Such a clever idea !
[Nexus 7 (2013) General] ytymf:
it does work
[Nexus 7 (2013) General] berardi:
argh, so the fix worked perfectly, GPS finally works for me!! thank you!

But I am getting spammed with "Bluetooth Share has stopped" messages so the system is unusable. I will reflash the original CM, apparently bluetooth is broken by the fix.

Any ideas?

EDIT: False alarm, it had nothing to do with this fix. It was entirely related to a Bluetooth Audio "Fix".
[Nexus 7 (2013) General] sfhub:
Wow, so we broke the berardi black cloud curse? Something good happened to your Nexii? That is really something! :)
[Nexus 7 (2013) General] berardi:
Yes hahaha finally have a working unit GPS and all.. Thank you very much for the GPS fix!!!
[Nexus 7 (2013) General] Chasroach:
I rooted my N7 and kept the stock ROM. I ran the OTA update, no problems, and it fixes the GPS issue. Still on JSS15J.

Sent from my Nexus 7 2 FHD Flo (razor)
[Nexus 7 (2013) General] Muikkuman:
So the GPS issue is a software issue? Not a hardware issue?
[Nexus 7 (2013) General] sfhub:
For most people their GPS issue can be resolved in firmware (software).
[Nexus 7 (2013) General] Muikkuman:
I just tried GPS outside and had 11/20 connected.
[Nexus 7 (2013) General] sfhub:
Sorry, are you saying you had no GPS issues prior or are you saying you installed the GPS fix and now have no issues?

If latter, to help others, what OS were you running?
[Nexus 7 (2013) General] Muikkuman:
I thought I had GPS issue but I had several satellites connected when I tried to get a fix. I'm fully stock no modification's.
[Nexus 7 (2013) General] sfhub:
You should check which version of the software you have in settings->about tablet.

If you have JSS15Q then you already have the fix.

If not, then you may find out that you eventually lose ability to lock. The GPS issue is not that you can't lock at all, it is that you lose lock over time and then cannot get it back until you reboot. It can take anywhere from 5 minutes to 90 minutes to lose lock and it usually happens only when you are using multiple GPS apps. If all you use is Google Maps then it might not happen. Google Navigation and Google Maps would be considered separate apps. Throw in some screen standby's while GPS running to increases the chances of hitting the bug.
[Nexus 7 (2013) General] Muikkuman:
Yes I have JSS15Q. Thanks for explaining it.
[Nexus 7 (2013) General] EatingPie:
Anyone tried this with CyanogenMod 10.2?

-Pie
[Nexus 7 (2013) General] sfhub:
Yes, that is why it says CM10.2 in the title.

http://xdaforums.com/showthread.php?p=45088545#post45088545
[Nexus 7 (2013) General] berardi:
Yep, working great here... I am finally a happy camper!
[Nexus 7 (2013) General] maple4star:
Problem loading TWRP

Hi all,

Just having some problems with TWRP. Was not wanting to necessarily flash permanently with TWRP and hoping to follow this exactly. Bootloader is unlocked, goes into fastboot mode fine, but then when I type this:

Fastboot boot twrp.img I get the following message.

"cannot load 'twrp.img': No Error

Any suggestions or am I just being dumb and missing something here.

Thanks! Was really looking forward to this solving (hopefully) my gps issues as everything else has been working great on my N7 2013 (JWR66N)
[Nexus 7 (2013) General] sfhub:
Did you download twrp? Did you rename it to twrp.img? I just called it that for convenience, you can sub whatever name you used. Did you place it in your adb directory?
[Nexus 7 (2013) General] maple4star:
Ok, first, sorry for the lack of info, but yes to all of the above. But I managed to get it working and used TWRP to flash the gps firmware successfully. For some reason it didn't like being in the adb directory, so I just copied it to c: drive and linked to it there.

That said, it unfortunately hasn't seemed to fix my problems. No gps icon, no gps satellite locks or anything, no matter how many times I reboot. I guess I either try some of the other mentioned work-arounds, or try upgrading to JSS15J and hope that the touch screen still works well... unless anyone found a solution to this problem after trying this fix.

Thanks though for your work though!
[Nexus 7 (2013) General] sfhub:
This actually isn't specifically to fix a GPS that never comes on. That might be a different problem (or it could be the same).

This is to fix the problem where your GPS works but then after time you lose lock and it won't come back.

Regarding your issue, have you tried a factory reset after using the GPS fix in this post?

Also have you tried a factory image restore? It is possible you have corrupted /system image due the eMMC corruption problem along with past updates.
[Nexus 7 (2013) General] maple4star:
Tbh, I didn't know that the GPS wasn't even coming on, since my first concern was the screen and that was fine, then just noticed gps wasn't working since last night and thought it had just lost signal....

I did try a factory reset after trying the GPS fix but no go... still keeps looking for GPS location when trying various test apps....

I haven't tried a factory image restore... I mean I haven't really done anything to it except for unlocking the boot loader, and then installing the GPS fix from here... but if you think it's worth trying a factory image restore, perhaps I can give that a shot...
[Nexus 7 (2013) General] sfhub:
I would do a factory restore and download GPSTestPlus from the play store, clear AGPS data, then reboot.

Finally, turn on WiFi GPS location the first time and hopefully you get GPS. Then you should be able to turn it off and still get GPS. That is how I got one unit unstuck, but no guarantees.

BTW are you using profiles?

This persons posted something I did not know about how profiles are working w/r/t gps:

http://xdaforums.com/showthread.php?p=45241250#post45241250
[Nexus 7 (2013) General] maple4star:
By factory restore, you mean restore the original OTA, which for me would be version JWR66N? If so I've only seen the JWR66N/dev-keys -> JWR66N.zip versions? Thing is I tried getting into the stock recovery mode, but it seems to just get stuck at the dead android guy with the exclamation mark... I guess the question is, should I restore the file (link below), and should I use the adb sideload to do it?

Or should I just try updating to JSS15Q?

If what you suggested doesn't work I might as well update to 15Q, and if that messes up more stuff, just exchange it to Bestbuy, though I'd hate to get stuck with a messed up screen one... I can live without GPS until a more thought out update comes out.....

Thanks for all your help sfhub, greatly appreciate the effort to sort this out...

http://xdaforums.com/showthread.php?t=2380113
[Nexus 7 (2013) General] sfhub:
I was going to suggest you just do the factory image for JSS1Q here:

http://xdaforums.com/showthread.php?p=44888268#post44888268

flash factory image

download gpstestplus

clear agps

reboot

You can resolve any screen issues in this thread:

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] afremont:
I've been using this firmware with the kernel and ROM that I built. The GPS works basically, but there are some subtle issues such as the little notification sat icon from GPS Status not always showing and the $GPGSV sentences not coming out until lock is acheived. Also, Maps won't zoom down until it gets a GPS fix even though the Wifi location stuff is turned on. It's like it refuses to use the Wifi information no matter what. Again, this is with my first attempt at building the whole mess from scratch and probably have done some things wrong here or there. I think I am running the equivalent of a JSS15J kernel on a JSS15Q Android system. Could be an isolated incident due to my setup, but I just wanted to mention it.

Here is a screen cap of my About screen:
[Nexus 7 (2013) General] maple4star:
Thanks sfhub.... I will probably give that a shot in the next couple of days and let you know how it goes....

As to your screen workarounds, I have been reading your conversation with lespaulman67 who originally sounded like he had my same problem, issues with GPS...(though he also then had a corrupt eMMC problem), would it help (or does it matter), to install something like boot-ts10-lock.img before flashing with the factory JSS15Q (as he did), to protect my working touch screen, or does it really matter? would it essentially be the same as loading ts10 after the fact IF there was a instigated problem with the touch screen after upgrading to JSS15Q?

as an aside, is there any way to tell if the tablet did indeed correctly update from the JWR66N dev keys to the JWR66N release keys? Unfortunately this is my girlfriends tablet and she was anxious to use it and fired it when I wasn't watching it exactly, and she said it did seem to download an update out of the box and then reboot, so I'm assuming it completed the update, but I'm not entirely sure. Upon reading the forum on people who've had issues updating through the OTA they mentioned that their tablet didn't have the stock wallpaper (yellow/pink/green/blue slashes) and I've also confirmed this to be the case with mine.... Just wondering if it's worth trying the update-repair-JWR66N.zip to see if it helps with anything... or should I just F*it and go straight to JSS15Q.... I guess I have nothing to loose by trying it...?

On a second note, since I first tried to fix the GPS using your method, but only came across your mention now that TWRP (2.6.0.0) 2.6.1.0 will cause an upgrade to your touchscreen software to (JSS15J) JSS15Q levels, and while my GPS is still not working but the touchscreen still works fine, would that imply that loading the factory image to JSS15Q might not affect the touch screen after all, or is that too simple of an assumption? Anyway, maybe it's a piece of info to keep in mind, and perhaps you want to make a note of that on the first page of the GPS fix....?)

Again, if you think of anything else I'll keep checking this thread, otherwise thanks for all your help and I will check back with the situation perhaps by Thursday...
[Nexus 7 (2013) General] sfhub:
For peace of mind and sanity, some people like to do TS10 first, so they can verify everything is working as it should, and have that locked in place before doing any upgrade. The other way around, doing the upgrade first, will just result in a little anxiety if your touchscreen starts having the documented issues and then you have to go back and figure out which one of the fixes to use. Both will work though.

Easiest way without upgrading is to sideload the JWR66N-devkeys to JWR66N-release keys OTA update. It won't make any changes but will SHA1 check all your files (well not really all of them, because it is a smaller update, but most of them, and most importantly the ones it tried to modify the first time around which are the ones that are potentially corrupted)

From a time-efficiency standpoint, lock in TS10 and do the upgrade to JSS15Q.

From the standpoint of learning new things along the way, you can try the update/repair JWR66N route.

Yeah, sorry about not mentioning TWRP. At first I actually didn't realize that was happening myself until an associate recently complained that rooting messed up his touchscreen and I investigated what was going on.

If you used TWRP 2.6.0.0 you'll be at JSS15J level touchscreen software. If you went to JSS15J there would be no difference, however going to JSS15Q is a different story. Going in that patch, some people have new issues, some do not, some have issues fixed.
[Nexus 7 (2013) General] sfhub:
It is an issue with the particular setup on your tablet as it doesn't work that way on stock (with GPS fix) on other tablets.

The GPS messages come up right away on stock. We know this because people get satellite signal level messages prior to lock full lock when (at least) 4 satellites come in view.

I would guess it is the ROM. Did you apply the GPS fix before or after your self-built ROM was installed?