yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] BrianLefevre:
I just held the power button down for a full minute, and nothing happened.

The battery can't be removed without disassembling the whole tablet... is that pretty much my only option at this point?

The command prompt still says < Waiting for Device > with the flashing cursor.
[Android Q&A, Help & Troubleshooting] shimp208:
At this point I would recommend closing the command prompt window, and downloading the latest version of fastboot from the Android SDK. Then after you have done that with your device still in fastboot mode try running your original command again.
[Android Q&A, Help & Troubleshooting] BrianLefevre:
That worked, I am back up and running and finally rooted! Thank you very much for the help!
[Android Q&A, Help & Troubleshooting] shimp208:
No problem man always glad to help people out glad you were finally able to get your device rooted.
[Android Q&A, Help & Troubleshooting] BrianLefevre:
Looks like I spoke too soon. There appears to be an issue with the root.

I have been a member for more than 10 hours, so I can link to the tutorial I was using now: http://www.forum.lepanlife.com/thread-390.html

I am on Step 20, where it tells me to update SuperUser. When I do it, I get these messages. Does this mean my root didn't take? I'm not getting any help on that forum, so I really appreciate the help here!
[Android Q&A, Help & Troubleshooting] shimp208:
It would appear that you were not able to gain root access judging by the error messages the Superuser app is returning. But to make sure I would recommend downloading Root Checker Basic and seeing if that says you do or do not have root access. If that does not work I would recommend taking a look at this tutorial here for a simpler way to root your Le Pan II Tablet. Note if you are going to follow the tutorial I posted a link to first run the following command from ADB:

rm /system/bin/su

This way you can start out on a clean slate for the procedure. If the tutorial procedure in the link I posted still doesn't work let me know and I will walk you through a possible solution to root your tablet using a known procedure.
[Android Q&A, Help & Troubleshooting] BrianLefevre:
I ran the superuser update again, and now it says Okay to "Gaining Root Access", but it still says Fail to "Remounting /system as rw".

The app you linked didn't work on my device, but another Root Checker app says I do have root access. Any ideas?
[Verizon Samsung Galaxy Note II] shangrila500:
While browsing a bit last night I luckily stumbled across a recovery flashable zip that fixed all my GPS issues on AOSP. I had previously tried all the other fixes that have been posted thus far and none worked on the 20130601 VRB nightly, the previous VRB nightlies, any of the PA releases, or any of the other various AOSP ROMs.

In the post it states that this will work with any of the t0lte phones, the VZW Note 2 is the t0ltevzw for those of you who have only heard of it referred to as the i605, so I gave it a shot and lo and behold my GPS locked within 5 seconds where it previously wouldn't even pick up any satellites.

So those of you having the same problem try flashing this:

http://rootzwiki.com/topic/40116-42...de-hello-halo-0604/page__st__490#entry1184057

Here is a link to it in my Dropbox for those of you who would rather not use Rootz:

http://db.tt/PnvlFhgy

The way I flash it and the way I have always gotten it to work is to open Maps first, click the GPS shape to get it to find you, wait until it says "Unable to locate", reboot directly into recovery, flash this fix WITHOUT WIPING ANYTHING, reboot and open Maps, profit. When you are testing Maps after you flashed the fix make sure you are outside to give it the best possible chance to find satellites. If it still locks show but you are getting a lock try using FasterGPS from the Play Store to change your GPS.conf, to do so open the app, grant it superuser privileges, and select the correct continent and region under NTP Server. It should be North America for the continent and United States for the region unless you are using the i605 out of country, if you are using it out of country then select the appropriate continent and region.

I didn't create this nor in any way, shape, form, or fashion take any credit for this fix, the credits go to alba on Rootz. The only thing I have done is post it here so hopefully the people with GPS issues will see it and finally be able to use it.

EDIT:

For those of you that flash this please leave a comment starting if it did or did not work and what ROM and kernel you're using. If you haven't flashed a kernel then just put something like "using kennel that came with ROM." This way maybe we can see which ROMs it works with and which it doesn't so hopefully we can troubleshoot it and get your GPS working.

Also if the fix doesn't work download GPS Status or GPS Toolbox from the Play Store and see if your phone is even seeing the satellites. If it is it will show you something along the lines of either 0/0 or 0/x# of satellites. I have included some screenshots to show you how to find the number of satellites in GPS Status.
[Verizon Samsung Galaxy Note II] torr310:
Thank you for the post. I wish I saw it earlier when I was on Jedi Rom, but I switched back to MeanBean immediately because I have to have GPS working properly.

Hope this thread help others though.
[Verizon Samsung Galaxy Note II] shangrila500:
If you still have your nandroid you can always go back! Heck you could still go back!
[Verizon Samsung Galaxy Note II] izman12:
I just did a cache wipe and dalvik wipe about 3 times and gps started working
[Verizon Samsung Galaxy Note II] shangrila500:
That and the other suggestions don't work for some of us.
[Verizon Samsung Galaxy Note II] SirVilhelm:
This files actually killed my GPS completely. The GPS icon no longer shows up at all when I open maps and GPSStatus now force closes. Fun
[Verizon Samsung Galaxy Note II] shangrila500:
How did you flash it and on what ROM? No one else has ever experienced this thus far, the worst is that it didn't help and that was only 2 people.

And there is only one file, not files.
[Verizon Samsung Galaxy Note II] droidstyle:
The best way to fix gps is go back to touchwiz..:p
[Verizon Samsung Galaxy Note II] shangrila500:
And for those of us that that doesn't work for?

I prefer VRB as opposed to TW and using this I have full functionality. TW has a few nice features but is highly overrated in my opinion.
[Verizon Samsung Galaxy Note II] droidstyle:
chillax...just messin around bro! :good:
[Verizon Samsung Galaxy Note II] shangrila500:
I wasn't meaning to come across rude, I respect you and everything you do for the community.

I'm sorry if I can across with an attitude.
[Verizon Samsung Galaxy Note II] droidstyle:
No worries :)
[Verizon Samsung Galaxy Note II] thejudgement223:
didn't work for me
[Verizon Samsung Galaxy Note II] shangrila500:
What ROM were you on? Did you launch Maps before you flashed it? The only way it works for me is if I launch Maps, let it say it can't find me (when in all reality the GPS wont even search), reboot, flash, profit.

Also try it without the WiFi and Wireless Networks selected under Location Access..
[Verizon Samsung Galaxy Note II] kickenwing13:
Good stuff man Thank you
[Verizon Samsung Galaxy Note II] shangrila500:
No problem, did it work for you?
[Verizon Samsung Galaxy Note II] rlt9999:
Worked like a charm for me on XenonHD rom. Couldn't get any lock B4 and now works fine.

Thanks dude!
[Nexus 7 General] ace-user:
Hi guys, i got a nexus 7 around september last year..everything was great until i started getting ghost touches here and there...the tablet would start acting on it's own, swiping around home screens, randomly opening apps and stuff.. so i rang up Asus and ask for a replacement unit...the new unit seems to be fine but yesterday there ghost touches were back again.. then i noticed that the moisture on the screen is actually the one causing the random touches... i downloaded multitouch test from the play store, and put a few small drops of water on a certain part of the screen, and the app actually detects touches on that part of the screen... i think somehow the drops of water are putting pressure on the screen and causing the screen to detect the pressure as touches? is this a manufacture flaw by Asus? it's really bugging me and i hope I'm not the only one experiencing this...
[Nexus 7 General] graydiggy:
Its not pressure, nor is it a defect. It happens on all capacitive screens like the N7. What is water? It's is a great conductor. Your fingers do the same thing.
[Nexus 7 General] ace-user:
why isn't the gnex affected?
[Nexus 7 General] why always me:
May due to a better digitizer on the gnex as the Nexus 7 came with a lower cost.

In digitizer there is something like a noise management system and seem like the higher cost products has a better management for example I has never has a problem with a moisture on the iPad screen but I do has with my N7.
[Nexus 7 General] ace-user:
the weird thing is that ever time i won't face this problem for the first few months..but once i encountered it the first time, i keep getting the ghost touches almost everyday...seems like the digitizer is getting worst day by day...
[Nexus 7 General] veeman:
Pure water is a horrid conductor.
[Nexus 7 General] graydiggy:
Distilled water is a bad conductor. But tap water and non-distilled bottled water are great conductors.
[Nexus 7 General] veeman:
Yes, I know this. It's not the water itself that is conductive, it's the minerals and stuff in the water.
[Nexus 7 General] chismay:
i may be missing something here......dont put water on your nexus?
[Nexus 7 General] graydiggy:
Putting drops of water on the screen won't hurt the unit. Well... As long as you don't let it into the bezel.
[Nexus 7 General] ace-user:
glad to know that I'm not the only one having ghost touches..
[Nexus 7 General] ace-user:
is there any fix for this? cause everytime i come out from an air-conditioned room, my n7 will start to have ghost touches due to the moisture..it's kinda bugging me a lot..
[Nexus 7 General] graydiggy:
Try replacing the screen. That is about all you can do.
[Nexus 7 General] Darth:
Stop using it in the tub....steam becomes water. ;)

Sent from my cell phone telephone....
[Nexus 7 General] sheemon:
Noise management has an important software/microcode component. I do not see the N7 as being low quality but input and signal management are far from optimal - IMHO.
[Nexus 7 General] graydiggy:
Steam is water... It is water vapor.
[Nexus 7 General] ace-user:
this is actually my second unit..i send to Asus for a replacement unit like 2 or 3 months ago because of the same problem..everything was fine with the new unit until now..Asus really need to work on their quality control..
[Nexus 7 General] Keion:
It's a conspiracy. The NSA is remote-controlling your Nexus devices.

Be warned, and be careful.
[Nexus 7 General] nicetaco:
How did you get asus to give you a new unit? I still can't get them to remove a scratch on the screen.
[Nexus 7 General] Rirere:
I'm admittedly not fully convinced it's not an environmental problem on your end. It gets pretty humid over here, but moving in and out of climate-controlled conditions has yet to cause moisture to appear on my screen. Are you sure you don't have any dust/grit etc. on your screen? That can help water coalesce/probably improves conductivity of any moisture that does appear.

Unless you documented that the scratch was there as soon as it came out of the box, I can't see any customer service department making it easy to exchange a device for a scratch (because no offense, but it's almost always the user's fault, so they're going ot be pretty skeptical no matter what you say).
[JAM, MDA Compact, S100 General] di7riks:
Hi everyone!

New to this forum but got my Qtek S100 a couple of weeks ago and found an irritating bug in it..

When I use my SonyEricsson HBH-300 Bluetooth headset everything is fine until I've talked for ~7 minutes.. after that the other party doesn't hear me while I still can hear the other party.. Sometimes my mic never comes back during that call but sometimes it's back after about half a minute or so.. the funny thing is that if it comes back it goes away againg in about 14 minutes.. and perhaps 21, 28 and so on.. haven't really made that long calls with that headset because of the bug..

The headset works fine with other phones, at least SE Z1010, SE P900, Nokia 6630 etc..

And the S100 works fine with my Bluetooth GPS..

Has anyone experienced anything similar?

Have you got other bluetooth headsets, do they work for long ( +7 minutes) calls?

Cheers

/Rikard, Sweden
[JAM, MDA Compact, S100 General] katsj:
That also happened to me in the beggining after erasing the handsfree from my devices and paired it once more its running fine since then!
[JAM, MDA Compact, S100 General] Guest:
HI!

di7 riks.....I am using a Motorola HS810 Bluetooth handsfree with my O2 XDA II Mini and the same 7 minute problem is happening to me also. Initially it was 12 minutes but now it is down to 7. I can hear the other party but they can't and then I have to disconnect and dial again.

think I will do as katsj did...try pairing teh device again.

U
[JAM, MDA Compact, S100 General] Guest:
This is a known issue. Apparently, what is happening is that the device is going to sleep, and bringing down part of the bluetooth with it. The quick'n'dirty solution is to set your device to never power off, and just turn it off manually. Hopefully this will be fixed in the next round of ROM updates :?
[JAM, MDA Compact, S100 General] atsois:
I have an "almost" similar problem: I answer the call with the HBH-300 and talk for about 10 seconds after which I can hear nothing (the other part hears nothing also). If I close the handsfree from the MDA Compact then I can continue talking from the MDA (the call is not ended).

If I close the call and make a new call I get the same problem. But if I switch off the HBH-300 headset and switch it on again then the problem stops and in the following calls I can talk using the HBH-300.

This problem appeared only twice in the 15 days that I am using the MDA.

Obviously the phone did not power off in 10 secs (it was on when I had the problems) so the "sleep issue" mentioned previously could not have created the problem. Only the backlight goes off in 10 seconds. Do you think that the backlight might cause problems to the bluetooth?! :shock:
[JAM, MDA Compact, S100 General] Guest:
I am facing both problems described here. Does anyone know of a solution?
[JAM, MDA Compact, S100 General] gratefuled:
This is a known issue, but unfortunately it is not stated on Club IMate as a known issue.

This is concerning, because I assume i-Mate Techs are not working on this issue.

Over at Howards Forums Bengalboy states if you press the devices call button twice the headset incoming audio gets reactivated. I have yet to test it, because my caller hangs up before I get the device out of the case to press the call button twice.

One of these days I will beat the clock.

1.5 years ok, way back in Oct-03 I remeber many of us scrambling about all the MS Stack issues on the MDA II/XDA II, etc, and eventually tools were developed to help the issues.

I get rid of the PDA2K, because of all it's issues. Now the PDA2K has a better ROM and a new fix for the Broadcom stack.

Oh the misery.
[JAM, MDA Compact, S100 General] ujj75:
I pressed the power switch on and also pressed the call button twice...I dont know which worked but my call did not get disconnected after the 7th minute... :D

Ujj
[JAM, MDA Compact, S100 General] espenleknes:
BT headset cutting out

I have the same problem - BT headset cutting out after a limited period of time, ~10 seconds.
[JAM, MDA Compact, S100 General] Bman:
Same problem here, when using bluetooth headset people can't hear me after 8 minutes, pressing the green talk button twice restores the connection.

Second problem: phone does not answer call automagic with bluetooth headset. (jabra BT 200)

Third problem: no voice dialing and no possibility to hear who is calling.

Are these MS Bugs or HTC Bugs?

_________________

T-mobile compact

ROM version 1.01.00 WWE

ROM date 10/21/04

Radio version 1.00.10

Protocol version 1337.36

ExtROM version 1.01.124 WWE
[JAM, MDA Compact, S100 General] bamse:
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
[JAM, MDA Compact, S100 General] espenleknes:
This is interesting - I'm running rom 1.06.00 WWE and extRom 1.06.115. I noticed that they have a extRoom 1.06.116 there, is that the one you are running?
[JAM, MDA Compact, S100 General] bamse:
Yes, 1.06.116 it is.

It adds another issue though, making GPRS unable to reconnect after a phone call or USB Active Sync.
[JAM, MDA Compact, S100 General] mikehayes:
Hit the power button to reactivate - not the Green call button.
[JAM, MDA Compact, S100 General] ozsmac:
I also have this problem, when the device goes back to sleep my bluetooth headset microphone no longer works. I can still hear the other caller, however i need to hit the power button (Red one on the side) to get working again.

No need to disconnect the caller.
[Ouya General] synplex:
So when I got my Ouya first thing i Installed was Astro File Manager (which isnt very Gamepad friendly). With Astro I installed, Dead Trigger THD, Sonic Ep.2 THD, Riptide GP THD, Amazon app store, GBA.Emu, and File Manger HD. None of the THD Games work. I got them from my Asus Transformer Prime. The THD apks worked on my Prime but not on my OUYA (most wont even start up, Riptide freezes at title). The Amazon app store and GBA.emu work great, but File Manager wont even start up either.

I mentioning this apps/games because others on XDA/Ouya Forums seem to have them working.

What versions are you using and did you install them differently??

Please let me know. Thanks
[Ouya General] synplex:
Also are any Gameloft games working on the Ouya?
[Ouya General] Melon_Bread:
Open Source File Explorer (Game Pad Friendly): http://xdaforums.com/showthread.php?p=39772628

For emulation Retro Arch: https://play.google.com/store/apps/details?id=org.retroarch&hl=en

As for THD or Gameloft games I doubt any of those will be working anytime soon with out any heavy modification
[Ouya General] synplex:
Actually they're dozen of posts/threads where people have most THD (Tegra HD) games working. Ouya being a tegra 3 device should allow the ones that have controller mapping abilities and that aren't connect to the play store work.

I'm just asking if those people can share what versions of the game apk their using.

Thx
[HTC Wildfire S] J. Terrell:
hi everyone. i was wondering if anyone knows how to find the MIN number on a metro pcs wfs. ive been searching everywhere with no luck.

i appologize if this is a noob question.
[HTC Wildfire S] booogermonkey:
Yeah, koff[emoji12] [emoji81] [emoji81] [emoji81] [emoji81]
[Android Q&A, Help & Troubleshooting] phillyd32:
I received a Pipo Max M9 tablet today. Most things seem to work well, but the snapchat app says the tablet is incompatible. Netflix videos are very messed up, though streaming videos and YouTube works fine. Finally, the camera is messed up. I believe this to be a hardware fault but I thought I'd ask. Both the front and rear facing cameras take a multicolored, static image. The rear facing cam's image slightly resembles what the pic should be, but the front facing is completely wrong.

I am running the 4.2.2 install that came with it, but I have done a software reset. Choosing the stock or the pipo launcher changed nothing with these problems.
[Android Q&A, Help & Troubleshooting] PipoM9Pro:
Go to freaktaps forum and get the RileyRom for your m9... Big world of difference... I jumped over 500 more with the Autu benchmark test.... See in my signature the score....

Dispatcher: Pipo Max M9 Pro Quad Core / RileyRom USA / Autu. 19474
[Verizon Samsung Galaxy S III] Andytio:
Hi guys, this is my first post in this forum and I would like to apologize if this question has already been asked.

Basically I have a verizon GSIII (SCH-I535) that I stupidly flashed with a GT-i9300 kernel. I know I should have been more careful but it is done now, something to learn from. Now the phone is solid dead, won't turn on at all, will not go into recovery or download mode. It's dead.

what is the possible solution for this situation? jtag repair? at the moment I'm out of country and could not send my phone to verizon.

Thanks!
[Verizon Samsung Galaxy S III] jd1639:
If it's totally dead and you can't get into download and odin doesn't recognize it, then jtag is your only option.
[Verizon Samsung Galaxy S III] bbqsfire:
Yes jtag would be your only option.
[Verizon Samsung Galaxy S III] hallstevenson:
The wrong kernel shouldn't cause this. At the power-on stage or recovery / download mode, the kernel you installed does not come into play yet.
[Verizon Samsung Galaxy S III] jmxc23:
Actually it can but it is pretty rare but he isn't the first person that this happened to. I recall a few other people who had the same problem.
[Sprint HTC EVO 4G LTE] malamalaful:
I am looking to finally s-off my evo, finally. But i have read that the FacePalm method does not work with build 3.16 but it does for 3.15. How do I know what version i have? I am HTCDev unlocked and im running a PACMAN rom. i have HBOOT 2.09 and radio 1.12.11.1119.
[Sprint HTC EVO 4G LTE] Magnum_Enforcer:
You can use Facepalm:cool:
[Sprint HTC EVO 4G LTE] malamalaful:
Thanks man! FINALLY I CAN S-OFF IVE BEEN WAITING SO LONG!
[Sprint HTC EVO 4G LTE] Magnum_Enforcer:
Your build should be 3.15.651.16, by the way.
[Sprint HTC EVO 4G LTE] decayer177:
3.16.651.3 should be your build number, if you're on the latest firmware.
[Sprint HTC EVO 4G LTE] Magnum_Enforcer:
He's not on the latest firmware. The latest firmware baseband ends in 1210, which his does not.
[T-Mobile, Samsung Galaxy SIII] hundredhead:
My phone is stuck booting into TWRP recovery, no matter what I do. My screen is also broken so I can't touch anything in it, and the otg mouse doesn't work, and the volume button doesn't work. Any suggestions?
[T-Mobile, Samsung Galaxy SIII] hundredhead:
Any help at all? I really need this fixed ASAP.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Use adb to reboot download mode. Then odin flash the stock firmware.
[T-Mobile, Samsung Galaxy SIII] hundredhead:
Thank you so much! You honestly saved me. I can't believe it was that simple!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Right on!

Glad it worked!

Good luck with the rest!
[Nexus 4 Q&A, Help & Troubleshooting] Mohsyn Kaleem:
hey, i was listening to some song and suddenly my phone turned off and red notification light appeared :( can you please tell me how to fix it as i have tried everything to reset it :( Please help me
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
You have to open the back cover and remove the two screws on the battery and place them back on. Reboot and it should be back on.

You can just plug in the phone for a couple of hours and see if it'll power back on.
[Nexus 4 Q&A, Help & Troubleshooting] exb0:
Plug it in to the WALL CHARGER for awhile , try to turn it on. If it doesn't, well you've got to do what mr scream4cheese suggested. Or just RMA it.
[Nexus 4 Q&A, Help & Troubleshooting] jutezak:
Or try to use a wireless charger for a moment... it charges the battery directly, bypassing the CPU and red led circuits.
[Nexus 4 Q&A, Help & Troubleshooting] techienilay:
Red Light , not going off !

I removed the back cover , checked the voltage it was around 3.7V , i reconnected the terminals , still the red light aint going off

What should i do ?
[Nexus 4 Q&A, Help & Troubleshooting] yev.gavrikov:
http://xdaforums.com/showthread.php?t=2250454