Dear xda members and administrators,
since one month my left or right earphone ( doesn't work anymore when I plug it in my asus eee pad tf101. Yes i did test my earphones at other devices and they worked correctly on those devices.
My question is how can I fix this!? because its really annoying when only one earphone works;P
I also saw these USB soundcards and since I have a keyboard with full USB ports I was wonderingen if a usb soundcard like:
http://dx.com/p/external-5-1-channel-usb-2-0-optical-fiber-sound-card-audio-adapter-48213
or
http://dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475
would work on the asus eee pad transformer. In the reviews they say it is a plug and play device and it works on LInux and as we all know Android is based on linux.
Well I hope you peeps can give me some advice!!
Yours,
Kasper
kaspertje100 said:
Dear xda members and administrators,
since one month my left or right earphone ( doesn't work anymore when I plug it in my asus eee pad tf101. Yes i did test my earphones at other devices and they worked correctly on those devices.
My question is how can I fix this!? because its really annoying when only one earphone works;P
I also saw these USB soundcards and since I have a keyboard with full USB ports I was wonderingen if a usb soundcard like:
http://dx.com/p/external-5-1-channel-usb-2-0-optical-fiber-sound-card-audio-adapter-48213
or
http://dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475
would work on the asus eee pad transformer. In the reviews they say it is a plug and play device and it works on LInux and as we all know Android is based on linux.
Well I hope you peeps can give me some advice!!
Yours,
Kasper
Click to expand...
Click to collapse
Have you tried either of the following?
Compressed air in 2 short bursts into the outlet?
Using a DRY swab (not a cotton bud) gently insert into the outlet, but DO NOT TWIST.
(NOTE) :
You did not state if you are using stock ROM or custom ROM, so I will assume Stock. Back up your system using TWRP recovery, wipe all cache and then factory reinstall from start. After rebooting try to listen to some music or such and see what that does. If it works then try recovering the system back to what you had backed up and try again to see if the issue is still present.
(NOTE 2) :
To install TWRP recovery if you have not already, download goomanger from the play store and install the recovery from the settings (3 vertical dots). TWRP plays a bit better with the TF101 then CWM does.
MasterDecker said:
Have you tried either of the following?
Compressed air in 2 short bursts into the outlet?
Using a DRY swab (not a cotton bud) gently insert into the outlet, but DO NOT TWIST.
(NOTE) :
You did not state if you are using stock ROM or custom ROM, so I will assume Stock. Back up your system using TWRP recovery, wipe all cache and then factory reinstall from start. After rebooting try to listen to some music or such and see what that does. If it works then try recovering the system back to what you had backed up and try again to see if the issue is still present.
(NOTE 2) :
To install TWRP recovery if you have not already, download goomanger from the play store and install the recovery from the settings (3 vertical dots). TWRP plays a bit better with the TF101 then CWM does.
Click to expand...
Click to collapse
Thanks for fast respondong. Ye I tried to clean it with a dry swap but didn't work. I am on Custom ROM CYANOGENMOD 10 by rayman. But I had this problem when I was at stock rom, revolver rom, liquid smooth, revolution HD and now cyanogenmod 10 by rayman. So this didn't make a difference. I think it might be something with the hardware since a friend of mine stood on my tablet for a few seconds with his full weight xD. But since the build quality of asus is pretty nice my tablet still works xd.
I will try to get TWRP.
Just installed TWRP recovery didn't work:S Someone other ideas or someone who have experience with a USB soundcard?
kaspertje100 said:
Thanks for fast respondong. Ye I tried to clean it with a dry swap but didn't work. I am on Custom ROM CYANOGENMOD 10 by rayman. But I had this problem when I was at stock rom, revolver rom, liquid smooth, revolution HD and now cyanogenmod 10 by rayman. So this didn't make a difference. I think it might be something with the hardware since a friend of mine stood on my tablet for a few seconds with his full weight xD. But since the build quality of asus is pretty nice my tablet still works xd.
I will try to get TWRP.
Click to expand...
Click to collapse
That was information that was really needed. Now it is sounding more like a broken input. Your more then likely going to need to do a tear down and see if the jack can be repaired easily. If not take it to a repair shop and they can usually fix it for under $30.00
MasterDecker said:
That was information that was really needed. Now it is sounding more like a broken input. Your more then likely going to need to do a tear down and see if the jack can be repaired easily. If not take it to a repair shop and they can usually fix it for under $30.00
Click to expand...
Click to collapse
Thanks, anyone idea of USB soundcard is ging towork?
I would highly doubt it.
Sent from my Transformer TF101 using xda app-developers app
Related
Hello Everyone,
Being the proud owner of a transformer (B80, only downside to it really) I love its usb functionality. One recent problem however, it only sees (as in elicits any response) if I reboot with the usb inside, or plug it in short after reboot.
It worked before, and I already tried a full reset (still recovering all my non market apps and docs). Is there anyway to update/repair drivers that might fix it? Maybe reinstall honeycomb all together (if thats even possible)?
I tried searching for a solution, but both google and xda turned up nothing (though that might be due to my searching, 'usb not working' contains so many generic terms...).
Any help would be sosososososo massively appreciated, I really like using usb's and am not fond of reboots.
Thanks in advance,
Mentor
What do you plug in into the USB?
its already known problem
Its began after 3.2.1 HC patch, if you can install 3.2 HC rom, it will work again, otherwise its required full restart.... or couple of restarts......asus is aware to that problem....
Aah, that settles that then... Any idea about when a fixing patch comes out?
@Dave a regular usb (different types).
Thank you both for your responses
The newest firmware update that started rolling out yesterday fixes this problem.
I have same problem
what update! when will it come to uk.
Sent from my Transformer TF101 using xda premium
I never had this error, so cannot help more.
Dave a regular usb (different types).
Click to expand...
Click to collapse
Well if you connect a scanner or printer of course it won't work.
Hi guys(this is my first android device so i might get my lingo wrong ),
Just got myself a TF101, its a B40(second-hand, was originally purchased around July here in Aus), played with it for a day or so, was trying to work out how to root it, tried the nachoroot ABD method but couldn't get it to work. Was able to push files across but it failed to create local.prop.
Decided i'd root it via nvflash when i got back and copied come TV shows onto the microSD via its windows MTP driver. Went away camping for a couple of days and so rigged a direct charge cable from my a cig' socket supplied from my second battery(so doesn't have issues of fluctuations while the car is starting or anything). Essentially just supplying +~12V to USB pin 1 and - to USB pin 4, was fused with a 5A fuse as i couldn't find something smaller that would fit. This worked well.
Got back today and the first thing i did was plug it into my PC, now i'm getting "USB device not recognised" - "Windows has stopped this device because it has reported problems. (Code 43)".
I've tried this in 1 desktop and 2 laptops testing all USB ports both the laptops had fresh driver installs, the desktop have had bits and pieces installed but i tried to remove them and start a-fresh. Charging via the wall adapter works fine directly to the tablet or with the dock.
I've done both a cold reboot and a data wipe, neither of which had any effect. The tablet is current running the latest stock firmware(WW 8.6.5.21).
Idea's? Could it be the cable? Do we have a pin out for the proprietary end?
I have the EXACT same problem as you, i have a B60 tf101, was working fine this morning tried to root it via adb, 10 minutes lateri was getting code 43 on windows, tried everthing including factory data reset, software update, ive tried plugging it into 5 desktops, all on windows 7, no luck. Im thinking its a hardware error, should i RMA or is there a fix? Thanks
This might help you determine the Pin out
http://forum.xda-developers.com/showthread.php?t=1102049&highlight=diy
But i have never heard of this error before. If possible try another cable if a friend has a tf101 ect.
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1277849&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
We're not alone
blickmanic said:
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1277849&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
http://forum.xda-developers.com/showthread.php?t=1299867&highlight=unknown+device
We're not alone
Click to expand...
Click to collapse
It's good to see that atleast it's not just me. Your situation sounds very similiar to what's happened with my TF.
I'm going to give the "downgrade" to 8.6.6.19 a shot as outlined here http://forum.xda-developers.com/showthread.php?t=1417006
Okay, let me know how you get on. I'll let you know if I find a fix
Nup, doesn't have any effect on the problem. The upgrade works fine, but the USB still refuses to connect.
Novae said:
Nup, doesn't have any effect on the problem. The upgrade works fine, but the USB still refuses to connect.
Click to expand...
Click to collapse
Dammit, do you think we should RMA or just wait till ics?
blickmanic said:
Dammit, do you think we should RMA or just wait till ics?
Click to expand...
Click to collapse
I'm really not sure, i have a feeling that ICS won't help either. Have you tried another cable?
Novae said:
I'm really not sure, i have a feeling that ICS won't help either. Have you tried another cable?
Click to expand...
Click to collapse
Nope I haven't tried another cable yet, I've got one on order though. Let's narrow our problem down, are you using a genuine asus cable? I'm not and I think it may be my aftermarket cable...
blickmanic said:
Nope I haven't tried another cable yet, I've got one on order though. Let's narrow our problem down, are you using a genuine asus cable? I'm not and I think it may be my aftermarket cable...
Click to expand...
Click to collapse
I'm using a geniune cable. Does your TF still charge via the cable when plugged into the wall pack? Mine does.
Now that i am able to root my device with Razerclaw because i dropped down to 8.6.6.19 i was thinking i might give that a shot and install CWM, then flash a custom ROM to see if that helped.
My only concern was being unable to unroot/re-stock it for RMA if that ends up being what's required. I found this guide: http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Can anyone confirm that those instructions will work for a B40 @ 8.6.6.19 or possibly custom ROM, to return to 8.6.5.21?
Novae said:
I'm using a geniune cable. Does your TF still charge via the cable when plugged into the wall pack? Mine does.
Now that i am able to root my device with Razerclaw because i dropped down to 8.6.6.19 i was thinking i might give that a shot and install CWM, then flash a custom ROM to see if that helped.
My only concern was being unable to unroot/re-stock it for RMA if that ends up being what's required. I found this guide: http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Can anyone confirm that those instructions will work for a B40 @ 8.6.6.19 or possibly custom ROM, to return to 8.6.5.21?
Click to expand...
Click to collapse
Couldn't we just re upgrade to a stock rom?
blickmanic said:
Couldn't we just re upgrade to a stock rom?
Click to expand...
Click to collapse
i think the problem is that the asus recovery application see`s 8.6.6.x as higher versioned than 8.6.5.x so it wont flash in the opposite direction.
Novae said:
i think the problem is that the asus recovery application see`s 8.6.6.x as higher versioned than 8.6.5.x so it wont flash in the opposite direction.
Click to expand...
Click to collapse
hmm, do you think it'll help?..
Novae said:
i think the problem is that the asus recovery application see`s 8.6.6.x as higher versioned than 8.6.5.x so it wont flash in the opposite direction.
Click to expand...
Click to collapse
do you have a dock?
blickmanic said:
do you have a dock?
Click to expand...
Click to collapse
Yes. The moving between versions i dont think will help with our USB issue as i think it almost has to be hardware in some way, either the cable or something internal.
Novae said:
Yes. The moving between versions i dont think will help with our USB issue as i think it almost has to be hardware in some way, either the cable or something internal.
Click to expand...
Click to collapse
Does your transformer work fine on the dock? Try docking the transformer then connecting it to USB through the dock.
I've requested an RMA, UPS is going to pick it up tomorrow and send it off to the Czech republic service centre, I'll let you know how it goes.
blickmanic said:
Nope I haven't tried another cable yet, I've got one on order though. Let's narrow our problem down, are you using a genuine asus cable? I'm not and I think it may be my aftermarket cable...
Click to expand...
Click to collapse
blickmanic said:
Does your transformer work fine on the dock? Try docking the transformer then connecting it to USB through the dock.
I've requested an RMA, UPS is going to pick it up tomorrow and send it off to the Czech republic service centre, I'll let you know how it goes.
Click to expand...
Click to collapse
Nope, i've tried from both the dock and directly to the transformer both result in the same thing "unknown usb device" PID_0000&VID_0000.
Let me know how it goes, i'm going to order a new cable before i attempt to RMA mine.
Novae said:
Nope, i've tried from both the dock and directly to the transformer both result in the same thing "unknown usb device" PID_0000&VID_0000.
Let me know how it goes, i'm going to order a new cable before i attempt to RMA mine.
Click to expand...
Click to collapse
Will post RMA details here. http://forum.xda-developers.com/showthread.php?t=1476886
Since Asus ICS update was a gigantic failure for me (Youtube HD videos broken, reboots, etc) I decided to 'downgrade' back to honeycomb. However that DID NOT fix the rebooting problem. And sometimes it doesn't even reboot, it hangs on the bootscreen and does nothing, and sometimes it bootloops or just doesn't wake up from sleep. Just to note I am using the Revolver ROM for honeycomb (fully updated) AND I did not have these problems with the rom before I tried ICS.
Has anyone had similar issues? If so how did you fix it?
Please, my transformer is becoming more and more useless
How did you downgrade to HC? Did you also downgrade the kernel and bootloader?
sent from my transformer
gee one said:
How did you downgrade to HC? Did you also downgrade the kernel and bootloader?
sent from my transformer
Click to expand...
Click to collapse
I rooted my device and used an app that installed CWM.. Kernel is downgraded when flashing revolver and I did install an overclocking kernel from revolver parts. Bootloader I don't know.
Perhaps you should try updating the bootloader? It's just a theory, but I doubt it will make you Tf any worse.
sent from my cyanogen(mod) vision
I've got the exact same issue after the downgrading to revolver rom HC. How do you update the bootloader?
Also, I noticed that no problems occur when the device is charging, kind of wierd
Sent from my Transformer TF101 using xda premium
Hope someone can tell how to update the bootloader. I was going to do the same thing with an tf101 because of all the reboots but if it dont help I rather wait to see how's it going..
The issue is that something goes wrong when the tablet goes in to "deep sleep". This is the same thing that is happening in ICS.
Now, I've found a temporary 'fix' for this issue. The fix is that you don't allow it to go in to deep sleep.
There is a program called WakeLock (It's on google play, my account is not allowed to post links :/) that lets you do just that.. Open up WakeLock and check the PARTIAL_WAKE_LOCK radio button and then tap the Aquire/Release Lock checkbox. Now you're set! The tablet should not reboot.
This has worked fine for me as a solution and my tablet has been running all day without problems. There IS a downside though, your tablet WILL consume more battery power since it doesn't go in to deep sleep.
As a countermeasure to that I used setcpu and a screen off profile that downclocks the CPU to around 200-300MHz and after a full day I'm at 50% battery life (13 hrs on battery), not amazing but acceptable (my usage consisted of having wifi on at all times and watching 3 episodes of community and light web browsing).
Hope this helps!
Flashstock said:
The issue is that something goes wrong when the tablet goes in to "deep sleep". This is the same thing that is happening in ICS.
Now, I've found a temporary 'fix' for this issue. The fix is that you don't allow it to go in to deep sleep.
There is a program called WakeLock (It's on google play, my account is not allowed to post links :/) that lets you do just that.. Open up WakeLock and check the PARTIAL_WAKE_LOCK radio button and then tap the Aquire/Release Lock checkbox. Now you're set! The tablet should not reboot.
This has worked fine for me as a solution and my tablet has been running all day without problems. There IS a downside though, your tablet WILL consume more battery power since it doesn't go in to deep sleep.
As a countermeasure to that I used setcpu and a screen off profile that downclocks the CPU to around 200-300MHz and after a full day I'm at 50% battery life (13 hrs on battery), not amazing but acceptable (my usage consisted of having wifi on at all times and watching 3 episodes of community and light web browsing).
Hope this helps!
Click to expand...
Click to collapse
The tf101 I want to downgrade don't have that deep sleep issue.. It reboots when it's in use, often repeatedly.. And often stuck on bootanimation (eee pad screen).. So maybe I should try anyway..
Sent from my LG-P990 using XDA
axepted said:
Hope someone can tell how to update the bootloader. I was going to do the same thing with an tf101 because of all the reboots but if it dont help I rather wait to see how's it going..
Click to expand...
Click to collapse
In the stock firmware on the ASUS site or in the OTA updates, there will be a blob file. The bootloader can be extracted from there with the blob tools (search in the dev section).
I'd make a flashable version, but I suspect that you have a WW TF.
Ok, now this is crazy.... I thought that I was going nuts when after a complete wipe (using SuperWipe script) and re-installation of Honeycomb from scratch, I too still had the reboots!!!
How can that be? The reboots were NOT there before I installed ICS!
Is it possible that Asus updated the firmware in a specific integerated device during the ICS update that is casuing these issues or something? I don't know how else to explain people having the same issues even after reverting back to Honeycomb!
Anyone have any thoughts on this?
I do remember hearing that the bootloader was updated with ICS - would that normally get reverted back to the "old" bootloader when doing a full wipe with SuperWipe script and re-installing Revolver (Honeycomb verison) from scratch?
Hmm, maybe the best thing to try would be to try the old bootloader with new ICS? Maybe that will stop the random reboots with ICS too!
Thanks!
No, most roms don't touch the bootloader. The stock roms and the OTAs will flash it. Although I'm not sure how much it could do once the rom was booted. I've noticed a few bad flashes lately, but they are usually resovled by flashing again with a full charge, overnight, plugged into the wall, not the USB port. Give that a try first.
gee one said:
In the stock firmware on the ASUS site or in the OTA updates, there will be a blob file. The bootloader can be extracted from there with the blob tools (search in the dev section).
I'd make a flashable version, but I suspect that you have a WW TF.
Click to expand...
Click to collapse
The one I'm going to downgrade is a US version... So if that helps, make a flashable version :thumbup:
Sent from my LG-P990 using XDA
If there is anyway someone could package the old Honeycomb bootloader, i'd be willing to try it! I have been unable to find a way to get back to stock Honeycomb (in order to re-write the bootloader). I'm assuming that I'd need an NVFLASH version of stock honeycomb firmware to get there from here?
thanks for any help offered!
Sent from my Transformer TF101 using Tapatalk
Two days ago I disabled the apps "Android keyboard" and "polaris" . Since I use Swype on the tablet and quick office, figured it couldn't hurt to try. Usually I'd been waking up to a frozen tablet or stuck on reboot screen. Two days now no freezes. Not sure if it has rebooted while asleep, but I use it every night for several hours, and since I did that I've had no problems. Maybe just lucky two days. Someone may want to investigate that further. Wifi is set to turn off when screen does. Hope this helps someone.
Sent from my Transformer TF101 using xda premium
jtrosky said:
If there is anyway someone could package the old Honeycomb bootloader, i'd be willing to try it! I have been unable to find a way to get back to stock Honeycomb (in order to re-write the bootloader). I'm assuming that I'd need an NVFLASH version of stock honeycomb firmware to get there from here?
thanks for any help offered!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
What version tf do you have? US WW etc? Is your serial number nvflash compatible?
The other problem will be the system updates, but I think you can just delete dmclient?
sent from my transformer
i have a us transformer with the exact same problems. I went from Revolver HC to revolver ICS back to Revolver HC and the ICS reboot issue is persisting. I thought it was just me, glad to see (for my sanity's sake, not your torture) that it's not just me. I know on my old Captivate, if you used a GB bootloader with certain Froyo ROMs there was bad effects. It is possible it plays into it somehow. I never flashed an official ICS update, but since the customs are based off of ICS official it is possible something was changed. I have tried different Kernels, different Daemon settings etc, and the longest i could go was 2 days with no reboot. Mine does the same thing tho - sometimes it reboots. other times it just hangs on the ASUS screen until it kills the battery. It doesn't do it while plugged in. I have super wiped, re-flashed, restored old nandroid backs ups, you name it i have tried. Any help here is much appreciated as i have started using my kindle Fire as my primary tablet because i am becoming so frustrated with the TF. It has rebooted once while in use while playing a game. The rest is while off. Once li clicked the screen off to put it down to get a drink and it rebooted. Its quite maddening at this point,
I was eventually able to downgrade my bootloader to the version that came with 8.6.5.6 (its the version I had laying around). So, I am now running the 8.6.5.6 bootloader with Revolver ICS - we'll see what happens.
First night was encouraging - over 5 hours of deep sleep last night an no issues... I'll keep an eye on it and report back.
It just makes NO sense how the reboot problem is now present even on Honeycomb, where is wasn't as issue beofore!
I now wondering if ICS either updated some firmware on some device in the TF (wifi chip, bluetooth chip, etc) or that the bootloader might be the difference....
So I now have a Honeycomb bootloader (verify bootloader version by looking at text on sceen after holding vol down + power) and ICS OS. Time will tell....
Can anyone else explain how the reboot problem could cause the issues on honeycomb as well???
Thanks!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
I was eventually able to downgrade my bootloader to the version that came with 8.6.5.6 (its the version I had laying around). So, I am now running the 8.6.5.6 bootloader with Revolver ICS - we'll see what happens.
First night was encouraging - over 5 hours of deep sleep last night an no issues... I'll keep an eye on it and report back.
It just makes NO sense how the reboot problem is now present even on Honeycomb, where is wasn't as issue beofore!
I now wondering if ICS either updated some firmware on some device in the TF (wifi chip, bluetooth chip, etc) or that the bootloader might be the difference....
So I now have a Honeycomb bootloader (verify bootloader version by looking at text on sceen after holding vol down + power) and ICS OS. Time will tell....
Can anyone else explain how the reboot problem could cause the issues on honeycomb as well???
Thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Give us an update on this later
FYI - Still going strong with ICS (Revolver) running old Honeycomb bootloader (8.6.5.6).... I don't know, but I have a good feeling about this (of course, I've had that "good feeling" about 20 times now without any success)!
I'll keep you posted!
Sent from my Transformer TF101 using Tapatalk
jtrosky said:
FYI - Still going strong with ICS (Revolver) running old Honeycomb bootloader (8.6.5.6).... I don't know, but I have a good feeling about this (of course, I've had that "good feeling" about 20 times now without any success)!
I'll keep you posted!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Nice! How long have you been running it now?
Sent from my LG-P990 using XDA
I can't seem to anyone else who has this problem. My TF700 is working great. However, today I decided to bite the bullet and install CleanRom. After unlocking, I realized that my computer can no longer see the tablet via USB. It is not an unrecognized device, just nothing happens when I plug it in.
I have tried two different cables on 3 computers, so I believe the problem is with the tablet itself. It charges just fine and when I plug the cable into the computer or unplug, the screen comes on (just like when you plug in the charger), so something is getting recognized.
I don't see any physical damage to the port, it looks fine.
Anyone else ever seen this?
Thanks,
Chris
So it was working previously?
Thats OK said:
So it was working previously?
Click to expand...
Click to collapse
It was, not sure how long ago though. I know it was when I first got it. I'm guessing it is a hardware problem, but not sure what to do about it. I honesly don't care all that much about it, but I would love to get TWRP on it so I can flash roms. I haven't seen a way to get TWRP on it without the USB or GooManager, but I can't run GooManager because I don't have root yet.
Still trying to search to see if there is a way to get root without USB, but I haven't found anything....
-Chris
Chris,
See if downloading and installing PC Suite from Asus helps.
That might get the drivers working again.
Are your PCs win7?
Just a thought. I am not running clean rom but when u connect to ur pc try going to settings, storage, and and hit the 3 little dots on the top right. It should show some usb connection tab.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
rail205 said:
Just a thought. I am not running clean rom but when u connect to ur pc try going to settings, storage, and and hit the 3 little dots on the top right. It should show some usb connection tab.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
Click to expand...
Click to collapse
Thanks, I'll try the software install, but since the computer doesn't even tell me I have an urecognized device (nothing in device manager), I'm not sure that it is. I also already rolled back to stock ICS and also tried the storage settings to no avail.
I unfortunately think I have a hardware problem. I guess I'm stuck at trying to get it repaired, or just live without the USB connection....which I guess ultimately means no customizations. I can still flash back to the stock Jelly Bean using the factory bootloader and rom from the Asus site, so I may have to live with that.
Could be the cable. Sadly, replacing it is ridiculously hard.
ShadowLea said:
Could be the cable. Sadly, replacing it is ridiculously hard.
Click to expand...
Click to collapse
I wish it were. I have a second charger/cable and already tried both cables on different PCs. Uggh.
Connect the tablet to a PC running Linux and run lsusb to see if the tablet is recognized (the vendor ID is 0B05) - just to sidestep any possible Windows driver issues.
Hello,
I'm having trouble with the camera of my TF700. When i try to open the camera, the camera still show up but with the black screen. After waiting for a while, it got frozen and i got a message "Gallery isn't responding. Do you want to close it". When i close it and reopen it, it shows the message "Camera error: Can't connect to the camera"
My gallery is still working fine. I still can be able to access to the picture on my SD card.
My Infinity is rooted and ROM CROMi-Xenogenesis 4.5
I did the factory reset, cold boot, wipe cache, fix permission. None is working.
I installed Skype to see whether the video is working. It's NOT. I tried 3rd party camera apps. They dont work either.
I'm lost and do not know how to fix this problem. If anybody knows any method that i can try out to fix this, i would really appreciate it
Thanks
koolvn said:
Hello,
I'm having trouble with the camera of my TF700. When i try to open the camera, the camera still show up but with the black screen. After waiting for a while, it got frozen and i got a message "Gallery isn't responding. Do you want to close it". When i close it and reopen it, it shows the message "Camera error: Can't connect to the camera"
My gallery is still working fine. I still can be able to access to the picture on my SD card.
My Infinity is rooted and ROM CROMi-Xenogenesis 4.5
I did the factory reset, cold boot, wipe cache, fix permission. None is working.
I installed Skype to see whether the video is working. It's NOT. I tried 3rd party camera apps. They dont work either.
I'm lost and do not know how to fix this problem. If anybody knows any method that i can try out to fix this, i would really appreciate it
Thanks
Click to expand...
Click to collapse
Did your camera work before rooting and/or installing CROMIX? Did it ever work on CROMIX? If its not the ROM it sounds like broken camera hardware. If so you'll have to send it back to Asus for repair. Unfortunately you are unlocked and have voided your warranty hence the only reason I'm still locked for the warranty period.
elfaure said:
Did your camera work before rooting and/or installing CROMIX? Did it ever work on CROMIX? If its not the ROM it sounds like broken camera hardware. If so you'll have to send it back to Asus for repair. Unfortunately you are unlocked and have voided your warranty hence the only reason I'm still locked for the warranty period.
Click to expand...
Click to collapse
I got this from a friend. It work once when i did the factory reset. After that time, it didnot work. Thus, i was thinking if i root it and use different Custom rom it might fix the problem.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
koolvn said:
I got this from a friend. It work once when i did the factory reset. After that time, it didnot work. Thus, i was thinking if i root it and use different Custom rom it might fix the problem.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sounds like you need to do a full wipe. If it ever worked doing a factory reset then its not a hardware problem its a software problem. But you said "it worked once". I assume you mean that it opened and took some pictures, but only once or did it work for awhile? Are you saying when you opened it a second time like that same day and every time after that it never worked again? If that's the case it still sounds like a hardware failure but possibly something else corrupted your camera software shortly after your factory reset. I would do a nandroid backup (Online Nandroid Backup rocks) then a full wipe then a nandroid restore. I would suggest you also get some other inputs on this problem as I am far from an expert and don't want to steer you in the wrong direction.
elfaure said:
Sounds like you need to do a full wipe. If it ever worked doing a factory reset then its not a hardware problem its a software problem. But you said "it worked once". I assume you mean that it opened and took some pictures, but only once or did it work for awhile? Are you saying when you opened it a second time like that same day and every time after that it never worked again? If that's the case it still sounds like a hardware failure but possibly something else corrupted your camera software shortly after your factory reset. I would do a nandroid backup (Online Nandroid Backup rocks) then a full wipe then a nandroid restore. I would suggest you also get some other inputs on this problem as I am far from an expert and don't want to steer you in the wrong direction.
Click to expand...
Click to collapse
Its exactly what u said. It work once. I took some pictures with it. I closed it and reopen it shortly after in the same day and the problem starts. At that time my device not even rooted. How do u do a full wipe. I used CWM to wipe but it doesnt go away. Im suspecting its the hardware problem however there is no way for me to be sure. If its the hardware problem, would replacing the camera will solve the problem? I cant send it to asus. Not much of the option here
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
koolvn said:
Its exactly what u said. It work once. I took some pictures with it. I closed it and reopen it shortly after in the same day and the problem starts. At that time my device not even rooted. How do u do a full wipe. I used CWM to wipe but it doesnt go away. Im suspecting its the hardware problem however there is no way for me to be sure. If its the hardware problem, would replacing the camera will solve the problem? I cant send it to asus. Not much of the option here
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
If you already wiped from recovery then that's the one. And you did a factory reset. And the problem occurred before you rooted and on the same day it once worked. I'd say its hardware. But it could be anything from a bad controller chip to a bad shutter motor to a loose or bad ribbon cable. You'd have to trouble shoot the all aspects of the camera hardware platform to fix the problem. You could take it apart to see if you saw something obvious like a loose ribbon, but its not as easy as just swapping out the camera itself.
Asus does non warranty repairs, they are just costly. You certainly can send it back to Asus. That's what I would recommend.
elfaure said:
If you already wiped from recovery then that's the one. And you did a factory reset. And the problem occurred before you rooted and on the same day it once worked. I'd say its hardware. But it could be anything from a bad controller chip to a bad shutter motor to a loose or bad ribbon cable. You'd have to trouble shoot the all aspects of the camera hardware platform to fix the problem. You could take it apart to see if you saw something obvious like a loose ribbon, but its not as easy as just swapping out the camera itself.
Asus does non warranty repairs, they are just costly. You certainly can send it back to Asus. That's what I would recommend.
Click to expand...
Click to collapse
I sort of figure out my problem but still have no cure for it. I downgrade it back to ICS and the camera once again works for a bit and when i tried to open and use it again in the same day, it said the firmware need to be updated. However, asus firmware update failed. I cannot update the camera firmware. I went through the upgrade again to lastest jellybean from asus website. It still shows that the camera firmware need to be updated.
I notice that during the time i flash back and forth, the camera firmware did not change at all. It shows TF700T-FFFFFFF. I think it's the camera firmware problem
However, i could not find a way to update the firmware manually. Any thought on this one?
Thanks