I need some help here.
Every time I pull out my OTG cable from my Nexus 7, the screen hangs and then proceeds to reboot. It's very annoying. This happens with my Xbox 360 controller and my USB flash drive
When I was on 4.1.x, this never happened to me.
I'm using PA beta 6 and Trinity Kernel
Does anyone have a solution?
bump
Are you using stickmount? If so you should pull down the notification bar and touch stickmount to unmount the storage before unplugging. Also not all custom kernels and roms support all features. On stock, rooted it works perfectly.
Sent from my Nexus 7 using xda app-developers app
It's never a good idea to remove peripherals from Linux systems without unmounting them first.
I'm not the lowest of the low, but I am the slowest of the slow. 49.6 mpg avg for 38k miles in non-hybrid Scion xB
Related
So basically this is a wireless controller and when I use it, it freezes at some games, for instance, shadowgun. Could you help me with this
ALSO my nexus just made a pop noise when I booted it up, this is a ROOTed device.
sasdsa
Why does my nexus 7 screen doesn't turn on when I'm copying a file to USB stick through otg cable?
Which app are you using to transfer files ? , I am using stick mount which works very well and transfers files in background and I am able to use device,
Sent from my Nexus 7 using xda app-developers app
naman14 said:
Which app are you using to transfer files ? , I am using stick mount which works very well and transfers files in background and I am able to use device,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have used stickmount, USB otg helper and also native otg in custom roms. while transferring files by solid explorer or root explorer once I turn off screen I can't turn it on again until the transfer is complete
I've noticed this too.
I'm not sure if is completely blocked out (until completion), or just horrendously slow responding to interrupts generated by screen touches/button presses. I seem to remember waking the screen up - after a huge delay - on a multi-minute data transfer.
While it is annoying, it really doesn't surprise me much; most modern OS'es seem like their UIs slow down to a crawl under heavy I/O pressure between slow mass storage devices.
I suppose one cruddy workaround is to turn off the screen timeout ahead of the long copy operation...
bftb0 said:
While it is annoying, it really doesn't surprise me much; most modern OS'es seem like their UIs slow down to a crawl under heavy I/O pressure between slow mass storage devices.
I suppose one cruddy workaround is to turn off the screen timeout ahead of the long copy operation...
Click to expand...
Click to collapse
If it we're so then it would slow down even when the screen was on instead becoming unresponsive the instant screen was turned off
Souron29 said:
If it we're so then it would slow down even when the screen was on instead becoming unresponsive the instant screen was turned off
Click to expand...
Click to collapse
Yeah ... maybe. I'm not sure. In the past, I experienced difficulty in waking other android devices that had low OC minimum frequencies that would otherwise behave just fine so long as the screen stayed on. I don't know if interrupts start to stack up, or what, but I suspect that the rate governor behavior affects this, and I wouldn't be at all surprised to find out that a screen-off condition figures into the hueristics used by some rate governors or even kernel PM (power management) code. But that's speculation - I don't know.
I guess you could look at this as a feature rather than a bug - if you are performing a long copy, tapping on the power button tells you if it is done!
I am using file manager HD which works well in copying , although there is a 1-2 second delay in unlocking screen when copying, but still it works fine
Sent from my Nexus 7 using xda app-developers app
Hello everyone,
I know the name of my issue have discussed and maybe have done solving in many topic, but I believe that my problem is different.
I referred the topic Nexus 7 not recognised when connected via PC which was nearly identical to my problem. Not only my nexus 4 is not recognized by PC, but my battery life is decreased also. Through the topic, I realized that I used a car charger, and it caused my problem. Other comments said that there's a "safety switch" of some sort, written into the os, that "shuts down" the ability to communicate through usb after using these car chargers? I think it is because the car charger is unstable. Therefore, I tried to flash the stock rom and factory image to make sure every file system in my phone back the initial state, but it didn't work.
(P/S: I'm temporarily using the AirDroid to transfer file from computer to my phone, so I can flash the rom)
I have used my friend's nexus 4 to connect my PC and it worked. I think the drivers when my friend's nexus connected to my PC would be the same as the drivers for my nexus, but then when I connected my nexus to my computer, no thing happened, no notification, just only charging. I believe my cable is still fine because it worked fine with my nexus and my friend's nexus.
As I mentioned above, the battery life is reduced without any reasons. In the topic I referred, there was no one have the same problem with me. I exchanged mine with my friend's Nexus and tried to use it in one day. I checked email, listened to music, surfed web, and the battery was still over 40% before I went to sleep at night. However, my nexus is the opposite. I start using my phone after unplugging from cable in the beginning of the day, I don't do anything in a whole day, but the battery is only 10-20% at the late day. I'm very upset because the battery is not so long. I have a plan to replace the battery, but before that I want to ask you guy about my problem. Is it the system problem or the hardware mistake? Can I solve my problem without replace the new parts?
P/S: I'm a newbie, so if I have do anything wrong, please tell me. if you need any detail about my problem, I will give as much as I can. And if there is a post have the same problem as mine, please let me know and I'm sorry because of my careless when searching in forums. Thank you for spending your time to notice my topic.
Use AirDroid, thank me later!! Since you are a new to flashing, learn first by reading and watching YouTube video on how to root your device (if interested) then flash Franco Kernel (increase battery life tremendously)
Sent from my Nexus 4 using xda app-developers app
I've connected a 128GB SanDisk Glide USB drive to my Nexus Player and formatted it as internal storage. This worked fine, and I was able to install several apps to it and run them with no problems.
However, when the player is left for a while, it invariably gives an error message saying the drive has been disconnected, and the apps are no longer available. Removing and reinserting the drive brings them back, until a little while later when the same thing happens again. This problem doesn't seem to occur when apps on the drive are being used.
Has anyone else experienced this? I'm wondering if it might be an issue with a power-saving feature. Moving to an externally-powered USB hub hasn't helped.
I had similar problem, i spent days troubleshooting it with no luck till i got a premium $$ usb drive...problem fixed. Can't tell if that's the root cause though.
Sent from my Nexus 5 using Tapatalk
Definitely seems to vary by device - a MicroSD in a genric card reader failed in the same way, but an 8GB Verbatim Pinstripe drive seems to be working fine. I'm going to pick up a larger-capacity Verbatim drive and see how that copes - will post an update here, as it may be useful for others to know which drives behave and which don't.
I recently got a HDMI Micro converter so that I could plug my Nexus 10 into my TV.
Sound and video is fine (changed resolution to 1920x1080), but every game and even most menus are very laggy.
It's almost as if everything is rendered twice!
Games that normally run on high or medium barely run on lowest (Asphalt 8 for example).
But the second I unplug the HDMI cable, everything is back to normal.
I've tried everything I can think of to fix the issue, but I haven't found a solution yet.
Has anyone had this problem and found a solution, or does anyone have any suggestions on what to do?