Related
I have one of these stereo receivers in my car: http://www.amazon.com/BlackBerry-60-1699-01-RM-Bluetooth-Stereo-Gateway/dp/B001FFRN18
My Nexus S connects to it no problem the first time, but I can rarely ever get it to reconnect again until I reboot the phone. I've tried different ROMs with varying success but haven't had it connect consistently yet. Anyone have any thoughts on what I'm doing wrong or what I could try? Maybe the issue is specific to this brand of receiver and there's one out there that works better?
mapin0518 said:
I have one of these stereo receivers in my car: http://www.amazon.com/BlackBerry-60-1699-01-RM-Bluetooth-Stereo-Gateway/dp/B001FFRN18
My Nexus S connects to it no problem the first time, but I can rarely ever get it to reconnect again until I reboot the phone. I've tried different ROMs with varying success but haven't had it connect consistently yet. Anyone have any thoughts on what I'm doing wrong or what I could try? Maybe the issue is specific to this brand of receiver and there's one out there that works better?
Click to expand...
Click to collapse
FYI: Found another user on another thread with same problem using same blackberry gateway device. I'm gonna try a different brand device to see if problem persists.
I have the official Samsung USB Connection kit. Both connectors work fine immedeately after boot, but once the device has 'slept' they do not work anymore. I get a notification that the USB Connector is connected, but whatever I insert nothing happens. LEDs (on USB sticks, mice, ...) do not light up which seems to indicate that no power is applied to the port.
I'm running stock Android, rooted. Booting into safe mode makes no difference.
Any ideas what's going on?
You're not the only one, except that in my case USB sticks do light up. IMHO Samsung seriously botched up the automounter in their last update. I wonder how long it's going to take them this time to get their act together and produce a bugfix.
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
SpicyKiwi said:
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
Click to expand...
Click to collapse
Good luck with that. I contacted Samsung support Benelux and was told it was because Amazon Germany had installed "German software" on my tablet.
Trust me, that is NOT the case...
karel jansens said:
IMHO Samsung seriously botched up the automounter in their last update.
Click to expand...
Click to collapse
I'm not sure it's the automounter. Keyboards and mice show the same problems.
sciurius said:
I'm not sure it's the automounter. Keyboards and mice show the same problems.
Click to expand...
Click to collapse
You might be right, I haven't tried one of those yet. Of course, that would mean Samsung botched up the entire USB subsystem of our Note, which is kinda even worse.
Seriously, is anything done about this usb c**kup, or what? I bought my Note, expecting it to replace my venerable Archos 101 which, incidentally, had excellent usb connectivity three blooming years ago and on Android 2.1, only to find out that not only did I have to buy motherloving adapters for the Note, but on top of that that they don't even work properly.
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
sciurius said:
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
Click to expand...
Click to collapse
Quick question, has anyone has the adapter problems while on Android 4.1.1? I tried my adapters on a shop showroom model of the Note 10.1 and they worked perfectly, but only afterwards I noticed that Note was running 4.1.1, while mine is up to date with 4.1.2.
I'm just trying to avoid having to send back a piece of equipment that, despite everything, I can barely miss.
One of the USB OTG tools (forgot which one) had a table of functioning USB host versus Android releases and last time I looked the number of 4.1.2 devices that hat USB problems was significantly higher than the 4.1.1 devices. So I have all reason to believe it is a software problem, introduced in 4.1.2.
EDIT: The tool is USB Host Diagnostics from ChainFire.
So, is there an easy way to go back to 4.1.1 on the BigNote? Mine came with 4.1.2 installed anyway and something tells me that, if I ask Amazon to downgrade for me, I'll be answered with a deafening silence, probably with a "Duh?" In there somewhere.
On second thought, scratch the easy part; is there any way to downgrade a BigNote without losing any of Samsung's added value (yes, I happen to consider most os what they added actually valuable).
Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730
OK, will do. Thanks!
try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hello everyone.
my device is actually a G play mini but we all know it's just a rebranded honor 4c ( in my case CHC U23)
my problem is wifi/bluetooth don't "see" any networks. However, mobile 3g works fine
Don't know when problem started because the phone was handed down to me.
I've done a lot of research and I will post my findings.
- This seems to be a common problem with Honor 4C/GPlaymini/P8lite. I've tried any all all stock and custom roms from all the models above and problem persists so I'm possitive it's hardware related.
- From searching youtube the solution seems to be to replace or "reball" the wifi IC. my first finding is that the part number is:
HI1101 ( I had to apply hot air to a metal shield in order to remove it and see that) it's under the shield 'between' the Kirin620 and the headphone jack. This is the same IC chip as p8 lite
- a motherboard replacement costs about the same as a new phone so not worth it IMO however the wifi chip is easily findable and reasonably cheap on ebay or alixpress and I would give it a try. (I'm a beginner but wanting to learn)
My question if anyone has any experience is:
1) In youtube videos the wifi/bluetooth switch was greyed out and then the fix was to replace IC. Since I could use the switch but phone just didn't "see" any networks (even next to the router) does that mean the problem lies elsewhere and I'm just risking to brick the phone?
2) assuming wifi IC is fine, my other idea is the RF cable/ribbon/connection is damaged (which makes sense) but I can't for the life of me find where such internal cable is either by myself or in dissasemble videos (of which there are very few for our 4C) But interestingly on ali and ebay such a part exists (won't post links but honor 4c wifi connector is easy to find)
Does anyone know where such a connection is located or if it's just a mistake from the sellers? Are there boards that don't have those white rf cables to connect internal external antennas? Where is even RF antenna on the 4C?
I will update this if I attempt repairs but it will take a long time for any parts to reach my country.
Any other input on the wifi/bluetooth issues is appreciated. Also perhaps share your story if you have a similar problem. Specially if you solved it.
Sorry if I'm not posting in the right place, but this is as close as I could get for my not-so-popular model.
alderus said:
Hello everyone.
my device is actually a G play mini but we all know it's just a rebranded honor 4c ( in my case CHC U23)
my problem is wifi/bluetooth don't "see" any networks. However, mobile 3g works fine
.
Click to expand...
Click to collapse
Hei Alderus,
Did you manage to solve the problem?
I have the same issue with the WIFI/BT (they're grey).
Please let me know if you have any updates.
Thanks!
fixed your issue?
alderus said:
Hello everyone.
my device is actually a G play mini but we all know it's just a rebranded honor 4c ( in my case CHC U23)
my problem is wifi/bluetooth don't "see" any networks. However, mobile 3g works fine
Don't know when problem started because the phone was handed down to me.
I've done a lot of research and I will post my findings.
- This seems to be a common problem with Honor 4C/GPlaymini/P8lite. I've tried any all all stock and custom roms from all the models above and problem persists so I'm possitive it's hardware related.
- From searching youtube the solution seems to be to replace or "reball" the wifi IC. my first finding is that the part number is:
HI1101 ( I had to apply hot air to a metal shield in order to remove it and see that) it's under the shield 'between' the Kirin620 and the headphone jack. This is the same IC chip as p8 lite
- a motherboard replacement costs about the same as a new phone so not worth it IMO however the wifi chip is easily findable and reasonably cheap on ebay or alixpress and I would give it a try. (I'm a beginner but wanting to learn)
My question if anyone has any experience is:
1) In youtube videos the wifi/bluetooth switch was greyed out and then the fix was to replace IC. Since I could use the switch but phone just didn't "see" any networks (even next to the router) does that mean the problem lies elsewhere and I'm just risking to brick the phone?
2) assuming wifi IC is fine, my other idea is the RF cable/ribbon/connection is damaged (which makes sense) but I can't for the life of me find where such internal cable is either by myself or in dissasemble videos (of which there are very few for our 4C) But interestingly on ali and ebay such a part exists (won't post links but honor 4c wifi connector is easy to find)
Does anyone know where such a connection is located or if it's just a mistake from the sellers? Are there boards that don't have those white rf cables to connect internal external antennas? Where is even RF antenna on the 4C?
I will update this if I attempt repairs but it will take a long time for any parts to reach my country.
Any other input on the wifi/bluetooth issues is appreciated. Also perhaps share your story if you have a similar problem. Specially if you solved it.
Sorry if I'm not posting in the right place, but this is as close as I could get for my not-so-popular model.
Click to expand...
Click to collapse
woops. I should have posted long time ago. Anyways the update is I solved my problem (or it got solved by itself)
I had a business trip during summer, I still didn't had the replacement modem. Anyway, I remember it was blazingly hot and kept the phone in my pocket and then... I was very surprised to see wifi was detecting networks when back in the hotel!
I was running Lineage android 6.0. Didn't do any hardware or software changes, just went to a different city by plane it was hot and it started to work! there's is the funny catch that it never seems to work on the wifi I originally used it in back in my city(I moved from there but went back and found that I could see the network but it never really connected)
Other than that wifi has been working normally in any other home/office I've been to. I have no idea what really happened, but definitely I will never buy another huawei phone.
sorry if this doesn't help anyone in the same boat...
Suddenly OTG and Gear VR are not working on my S8 plus. no water, drop or anything. I have the device for only 2 weeks. No OTG device works (tried with genuine type c to usb adapter). It used to work like two days ago. I did factory reset and reinstalled firmware using smart switch. In addition, Gear VR is not being recognised anymore. PC connection and data transfer using the cable work ok. I believe OTG uses different pins. May it be a hardware issue? I remember getting some high-powered device connected before it stops working at all (using just a simple mouse). I tried everything.
I saw that a number of people have the issue on samsung support website. I hope it is not a known issue and samsung just does not state it officially (like the S7 edge pink line).
Please help or let me know if you have the issue too.
Arismfg said:
Please help or let me know if you have the issue too.
Click to expand...
Click to collapse
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
cam30era said:
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
Click to expand...
Click to collapse
thank you for your reply. I have already checked the thread above. However, no working solution. Is there anyone who managed to figure out if it is a software or hardware issue? I wonder why it is stated as solved. I dont think the guy with the issue fixed it
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
povotron said:
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
Click to expand...
Click to collapse
Thanks for the reply. Does this also have to do with OTG devices not recognised? Do you have this issue too? What is strange is that Gear VR used to work. At least for a while on my unlocked S8 plus. I cannot understand how this may block the OTG devices. Is there something left in the settings that may block OTG?
By the way, I hope you are not referring to the network issue. My Gear VR is not recognised at all.
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
povotron said:
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
Click to expand...
Click to collapse
Well I gave my phone to the official samsung service and waiting for their reply. I don't think I installed any updates before and after the issue appeared (at least not firmware updates but not sure about oculus or other apps) . By the way it is not the adaptor that has the issue. I tried many others on my phone. And the adaptor works with a friend's S8 (not plus). Only one works (well not really). It iss an OTG type-c to micro usb (bought from ebay) which comes up with a notification that high powered device was connected but then nothing happens whatever option I choose. And it is not a high powered device because it used to work. I tried even a mouse with its own battery. But if it was a phone update, I think a factory reset should fix it? It did not for me.
Do you think of taking your phone to the official service too?
A full factory reset also didn't work for me. From other forums it seems that other people who have taken them in for service receive a replacement phone. Some people however then mentioned that they encountered the same issue a few months later with the replacement. I would take mine to Samsung but it's a grey import and Samsung refuse to touch them even though it's the same model sold locally. If it's definitely a hardware fault I'll consider sending it away but it would be an international service which would leave me without a phone for quite some time.
Yes, you are right. Some people saw the issue after a few months of getting the replacement phone or even after restoring their google account and settings (without being able to get it fixed by factory reset). This is what actually scares me the most because it looks like hardware issue of the phone in general. It looks like a well known issue which samsung does not officially accept. SiImilar to the pink line on S7 edge I had before. Anyway, as charging and connection to pc still work, I can give my phone and get a new model later cheaper. The last two samsung flagships came with issues that (the most important) samsung does not accept officially. Maybe it is time to change brand (always android though).
I got my phone back from samsung service. They did not replace my phone but they replaced both the logic board and the type-c board. As expected, it works again with OTG devices and Gear VR as it is like a new phone after replacing all that. Installed all apps again one by one (not restored from backup) and everything still works. Hope it stays like that. So hardware issue? Looks like it.
I know this is an old thread, but I replaced just the USB board and it didn't fix anything. So maybe it's a motherboard issue?