Develop Bugs

[Q] Unable to get Wifi Tether to work

** O.K. So I went back and downloaded the PRE 8 wifi tether installer from google code and it worked like a charm. In the event anyone else encounters the same issue I had, then this might lead you in the right direction.**
I used REGAW's guide to root my OTA Froyo'ed EVO. I installed the Wifi tether app, and all super user permissions are in place. The tether shows up on my laptops available wireless networks, but I'm unable to get connection to the internet once connected to the Evo access point. Is there a particular radio, kernal or some kind of special setup I'm overlooking. I searched these forums thoroughly and didn't find anything, so forgive me if there's a posting somewhere I might have missed. Any help is appreciated.
Just to note I'm using the wireless tether app from the android marketplace.

why cant people post info when they ask a REALLY vague question like this
-which rom did you flash
-which wifi tether app are you using.
there really is only one to be using - 'wifi tether for root users' is the name.
-does your laptop actually connect?
-how do you know its connected (yes this is a trick question to see if you even know what you're doing)

With the very limited info given , pre 7 should be the one to try and try access control. As is documented in many threads for Wifi tether. I have never taken the one from the market always went ot site dirct. We'll see if we get more info of rom, kenal????

kd6duu said:
With the very limited info given , pre 7 should be the one to try and try access control. As is documented in many threads for Wifi tether. I have never taken the one from the market always went ot site dirct. We'll see if we get more info of rom, kenal????
Click to expand...
Click to collapse
newer builds are nice but frankly i use the one from the market and it works fine.
especially on a stock rooted rom.

I didn't post more info as I suddenly decided to try the pre8 install and it worked. So don't worry your pretty little head now there buddy. To anyone else who posted w/out the 'tude, thanks anyhow. I'd be happy to post my specific details for anyone who might need them. Thanks again!

I'm having the same problem.
I did the 2.2 OTA, unlocked by the guide and flashed Unrevoked-Forever. When in the stock 2.1 build (rooted) Wireless for root works great. As soon as I flash a 2.2 ROM (so far I have tried VirusXrom, Fresh, EVO.Zone, a plain 2.2 ROM, BakedSnack, AVA, and a few others) wireless for root stops functioning correctly. My laptop and desktop can see the AP, just not connect to it. This is the case for ROMs that ship with WFR and versions downloaded from the market.
If I flash back to my nandroid save of 2.1, WFR from the market works great.
I have also tried Kings #6 kernel and updated to the latest radio/wimax versions. I thought that I might be losing root some how, but if I open a terminal and type su I get dropped to the proper # prompt.
Any ideas?

Try going to code.google.com and then to the android wireless tether section. Hit the download tab and download the pre8 build of the tether. I used Android Sideload Wonder Machine to push the .apk to the phone, and after that my devices (laptop, psp, other mobile phones) connect to my EVO Android Tether access point w/out problem.

Sweet. That seems to have worked. I guess I just needed pre-pre8 versions are just, for some reson, incompatable with some aspect of our configurations.
Posting over my tether for proof-positive.

Awesome! Glad to hear that worked for u! Have fun..
Sent from my PC36100 using XDA App

[Q] G2 not being seen by PC

Hey guys,
I tried getting some help for this over at the Nook Color threads because it all started *after* i rooted my NC, but no one's been able to explain to me what Ive done wrong or whats happened...
So here's the sitch.
o I have ADB installed, but it only activates in device manager when the nook is plugged in, not the G2
o When the NC get usb'd to the PC, it fully registers and gives me access to the SD card on it
o .... where as the G2 just sits there and says "yay im getting power!"
o ,,,, BUT if i plug it into a HUB rather than directly into a usb port on the mobo or front, the PC (win7 x64 ult) seems to see it but doesnt know how to properly assign a driver to it and gives it UNKNOWN
o also i checked the usb-adb ini file, and it lists all my other devices in the hardware cues BUT the G2, which means it hasnt properly registered since then or never had a proper profile to begin with in the PC. It even has my older mt3G listed which I havent plugged in since all this started.
Ive tried multiple driver types, but literately, NOTHING has worked. Its like the G2 isnt even properly registering in the computer when connected. I tried a factory reset, but still no luck. Is there anything beyond a soft fact reset for an unrooted phone? I mean, i need COLD AS STONE back to day 1 reset.
Please help, I really want to root this :'<
and no, the only way now to access my sd card is to turn the thing off and use a reader. Like i said, it literately is NOT seeing it :<

Wrong section. Ask in the Q&A, not the DEV section.

Try installing HTC Sync, even though it doesnt work with the G2 because its sense based, it will install the proper drivers for you. This worked for me.
Heres the link:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1058&news_id=804
Another method would be install pdanet on you phone fron the Market, then install pdanet for your computer from here and it should install the drivers when you plug your phone in with pdanet app running:
http://www.junefabrics.com/android/

I tried the Sense link, but I couldnt find the download option for it.... anyways, heres a more precise description of the issue
When I go and install PDA Net, it loads up the drivers, but the computer literately is not even registering that a DEVICE has been plugged in via USB. I dont even get the USB connect prompt on the phone!
That's what Im saying, something is up. I need to take the cable with me and try this on another computer now that I think about it to rule out that something isnt damaged on the phone...

What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.

KCRic said:
What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.
Click to expand...
Click to collapse
But thats the whole thing, im not using a ROM, its just the stock OS build. if i was using a ROM, id have tried removing it and reloading it, but this is on a phone that isnt even rooted yet... actually... should I try going temp root again and see if that fixes anything?
Whats the best way to do that now since I keep reading Vision got pulled away because it was damaging phones or something?

Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?

Has it seen the g2 before? if so, get usbdeview, find the drivers in there that would be used for the g2, delete those. Snag PDANet and download that, plug the phone back in and see what ya get. You will get the pop ups again about the new software being loaded since it will have to find and reload drivers for the phone and PDANet will have the drivers you need.

K41N2358 said:
Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?
Click to expand...
Click to collapse
Like the guy above me said, DL or re-DL the drivers (though none should be needed if you're using it as a storage drive, the comp sees it as a usb drive). Is it charging your phone when you plug it in? It's rare, but the USB cable may be bad.
The only other thing I can think of is that something went wrong and the phone isn't releasing the mount to the sdcard, in which case you should try rooting and using a different ROM or a stock rom and it should help.

Well thats the whole thing, the computer doesnt even see the USB part of it. Thats been my whole issue. The computer doesnt see the phone or the usb drive part. It straight does not see the phone at *all*! Doesnt even show up in Dev Manager, but yet it gets power. I even went and got a new micro USB cable, fresh, and still nothing.
im getting to 86 the os and reload Win7, im like super uber pissed over all this because i cant figure it out. I dont even know whats wrong >_<!

Just for kicks (because I had this exact thing happen to another phone of mine - the slide) you're rooted, which means you have clockwork right?
Reboot into recovery and go to the 'mounts' part and select 'mount usb'. Do that with it plugged into your computer and let me know if the phone shows up then. That's the only way I could put it in mass storage mode. I flashed something other than cyanogen's rom and BAM, it worked like it was supposed to (Linux did mount cyanogen though - weird).
If you want to go back to 0 day with your G2, search 'PC10img' and download it. DO NOT FLASH IT YET, you could really screw up your phone since you have s-off. Go to the wiki and scroll to the bottom, it tells you how to get s-on. Once you can verify that you have s-on, proceed to flashing the pc10img.
Wiki

Okay, so, Im way better now. Apparently I managed to get s-off and root ability via
http://forum.xda-developers.com/showthread.php?t=837315
when i reloaded and got rooting ability, somehow, I now have a detectable sd card again.
I dont know how, I dont know why, I just know that Im going to throw CM6.1.1 onto this thing and be rocking it hard
Thanks again for all your help guys, it was awesome to know XDA really helps out its followers
EDIT:
Okay... so now Im mixed. I have a rooted phone, with CM6.1.1, but still doesnt properly recognize when plugged into the PC.
oh well, I already called TMobile and their sending me a new phone under warranty. Its gotta just be a busted port in some way for detection. I dunno. >_<
But still, thanks a lot guys. Means a lot

[Q] Upgraded to Leedroid v4 and cannot connect to pc

Hi,
I've searched all over and cannot finf an answer to my problem??? I have just upgraded to Leedroid v4 and everything works beautifully except I can no longer connect to my pc. It is recognized in device manager but the phone doesn't come up with splash asking how I want to connect it, and so I can't use it as a disk drive. The phone still charges though? I have tried ticking and unticking the ask and usb debugging options.
I don't really want to flash back to an older rom but if that the only way ill have to, can anybody help please????????/

I'm sorry, there is no way in hell you have searched all over. It's one of the most known bugs in the version 4 beta from Lee. It's on pretty much every page in the dedicated thread.
This is what you do. Either download Auto mount from Market OR change kernel to Unity's or Lord's. Both those kernels have fixed the USB connection problem.

Thanks for that. I searched the term not connecting to pc on this forum and google and didn't realise it was a mounting thing!

Np mate. You are most welcome.

i Too was looking for the same thing. Thanks a lot mate

The kernel was updated by Lee, you can try the new one from his thread (see my sig). New rom version should come this week.
Sent from Desire HD using XDA app.

USB cable charges the phone, but doesn't connect to PC

Hi.
I've been using my HOX for about 2 weeks and it's currently running ViperX 1.0.1 with the latest Faux 004 Beta 7 kernel. The problem I have is that, when I connect my HOX to the computer via an Micro-USB cable (either the one that came with the phone, or another Micro-USB cable) the phone just starts to charge and it doesn't prompt what type of connection I want to use (Only charge, file transfer etc).
The setting that it should ask for a connection type is turned on, standard connection is set to "Only charge" at the moment (but I have tried every other option also), and USB debugging is turned on as well.
The computer doesn't recognize storage device either, and HTC sync can't find the phone. I've tried to restart both the phone and computer, re-install HTC sync, clear Cache and Dalvik, uninstalling the backup app I'm usually using and also SystemTuner by 3C, but without any better results.
This is the first time I experience this problem. It started to behave like this yesterday. Everyday before that, it all worked as intended :/ The only thing I remember that I've done is to update Faux kernel to Beta 7 (from Beta 6) and installing SystemTuner which I didn't have installed before.
I have tried three Micro-USB cables, several USB ports on my computer and also other computers. So it's something with the phone I suppose.
I read somewhere about another person having this problem and someone told him it could be because "fast charge" is enabled in the kernel. But from what I've understood, the Faux kernel I'm using doesn't support fast charge option.
I'll be very glad for every help possible to resolve this issue, thanks!

Settings - connect to pc
Have you checked that "ask me" is on? Otherwise it uses the default mode which is usually "only charge"...
Edit: oww you tried that already... I don't know then... Maybe you should test it with the older kernel

Pudex said:
Settings - connect to pc
Have you checked that "ask me" is on? Otherwise it uses the default mode which is usually "only charge"...
Edit: oww you tried that already... I don't know then... Maybe you should test it with the older kernel
Click to expand...
Click to collapse
Thanks for the reply. Ye, I've had that one enabled all the time. I guess I should try using the older kernel and see if it works, then I know what caused it at least
I will do that and come back here and tell you all how it goes! Since I can't transfer the file over from the computer to phone, I have to download the file directly from the phone, so it takes a little longer.

Okay, so I have now installed the "old" kernel that I used before and that I know worked (Faux 004 beta 6) but it still doesn't work, so I guess it's not anything associated with the kernel.
Any more ideas what I should try? I guess I could try restoring a previous backup from when I knew it worked, but I will probably only do that if there's not any other way to fix it - as a last resort.

Your phones usb connector could be broken or just dirty...

I tried to search even more about other people having this problem but couldn't find any real solution to it. So I did a Nandroid restore to a date when I knew it worked, and now it all works fine again!
Not sure what I did to make it not work, but if it happen again, I will try to remember what caused it
Pudex said:
Your phones usb connector could be broken or just dirty...
Click to expand...
Click to collapse
Works after a nandroid restore. But ye, I guess that could be a reason some other time in case it suddenly stops working.
Thanks both of you for trying to help at least! I will edit the main post if this ever happen to me anymore time and I know what's causing it/how to fix it!

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.

xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.

epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.

I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.

Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.

Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone

Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!

Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.

xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?

epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.