Hi guys, experiencing massive deep sleep issues with my phone since a while and tried to figure out why this happens.
Every time when I use my device into my car (BT connected and USB connecte for android auto), when I leave the car, the phone never goes to sleep anymore until I reboot the device.
This problem occures on different roms OOS 3.2.4, 3.5.2 and CM13. What solves this issue for me was activating usb debugging, after long tests and modifications. I nearly have tested this with a complete clean install on OOS 3.5.2 to be sure that no apps doing the wakelocks.... But it seems to be the usb connection without debugging activated. Can somebody veryfy this if this is a general bug into Firmware or recovery of OP3?
Related
Hi, I have reflashed my ROM I dont know how many times. Yesterday I tried to connect via activesync on a new ROM and it wouldnt connect. These are some of the things that happened:
Device orange charging light flashes a few times then goes off [never seen THAT before]
Activesyc menu comes up on device but activesync doesnt connect
Get 'this device can perform faster' message on desktop
Sometimes get USB devce not recognized on desktop
SOmetimes device orange charging light it stays on if I plug direct into PC but still doesnt activesync
I have tried to connect as DISK DRIVE but I dont see the device on my PC.
Have tried different ROMS, 6.5, 6.51, sense 2.1 and 2.5 but all have same issue. Have also tried connecting to other computers. same issue.
Have played around with USB to PC menu options (enable / diable faster data sync etc) but doesnt make a difference.
Anyone had this problems? Thoughts?
Have you tried diselecting "ask me 1st about usb connection type when I connect the device to the pc" under USB to PC settings
It worked for me
This is the exact problem I am facing!
I tried everything - as diskdrive, activesync (with/without speedup), etc.
On many ROMs, even the original one (WM6.1)
Can't connect - every PC gives an 'unknown device' and on some ROMs I cannot charge via USB, only via mains...
I also tried without the question on connection.
Just some thoughts:
Do you have corruptions on screen sometimes? (Some graphical glitches)
Any .CAB files you cannot install?
Did you try to reflash the same ROM more than once?
tried to connect without card in the device and in flight mode? (Uses less power)
With me it started after a ROM flash from Miri... (I don't blame him!!)
The Hard SPL did not give me any problem, the radio was not flashed, just the OS. But reverting did not help.
I certainly hope you will find a solution, since I have the exact same problem!!
Do you stil know what ROM you flashed when this problem occured?
I reverted to original ROM 6.1 AND 6.5 which included everything - boot, radio, os, stardup image. But it did not change!
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
ekerbuddyeker said:
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
Click to expand...
Click to collapse
And how did you figured it out? Did you return the device to the shop?
I have this exact same issue except I am on AthineOS... I thought it was my PC until I read these posts. No OS updates or any other machine updates were performed except on my device. Any clues as to a fix?
Somehow I don't think this is just hardware.
I did drop my device once, but that was even before first flash. After that it still worked.
So, some weeks later I HSPLed without any problem. After that the device still worked.
Then, after investigating which ROM to use I flashed the ROM a few days later.
Right after the first flash it all still worked. So, had to flash another and from that moment on the device cannot be reckognised by any PC.
I still think it has something to do with the flashing. I think the device does not give correct feedback when it receives some commands from PC (eg. the command to reply the device type/number)
Does anyone know a program which can check the USB port for the HTC Touch Pro 2? Just to test wheather the connector pins are ok?
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
crazythunder said:
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
Click to expand...
Click to collapse
These are the first things done. And this was already written in here.
It happens with many PCs, including some on which the device never connected to.
Also tried different cables, ports, etc.
Also disabled the fast transfer etc. etc.
Even tried several other ROMs, inclusding original Dutch 6.1 and Dutch 6.5
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
waynehead05 said:
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
Click to expand...
Click to collapse
Some questions, to verify this is due to flashing or is a fault in the design of the device...
- Where did you get the device?
- Have you flashed the device?
- Did you accidentally drop the device?
hi just to say had a completely orignal o2 xda orbit 1 flashed with new rom everything worked perfect before now active sync plays up i can sometimes connect but get usb device not reconigsed then click cross then pull out usb then reinsert then active sync connects works fully functional then after 5 min it disconects this is driving me mad as use active sync for a fast internet connection on my pda as my wifi is crap
Okay so I finally fixed my USB issues that a lot of other people have been suffering from - no thanks to XDA forums (just kidding you guys keep me motivated to play with my android phone
Upon plugging in my phone - I would constantly get disconnected after a second or two. I searched and searched and found a bunch of users who suffer from the same problem but none of us have found a fix yet. Here is the fix:
1) Go to a ROM that you did NOT have this problem on. (For myself and several others it was usually a rom update that screwed everything up
2) Go into your windows network connections and highlight the HTC remote NDIS based Device and right click -> properties.
3) Click on the install button
4) Select protocol off the menu
5) Choose the Microsoft drivers
Bravo - you are now fixed. For whatever reason when the phone tries to connect USB it also attempts to connect via the NIC card which leads to all kinds of problems. This solved ALL of my USB issues including needing to reboot my computer after unplugging my USB. Hope this works for you guys.
I will definitely try this as soon as I get home! Thanks!
Sent from my PC36100 using XDA App
I just plugged my cable into the back usb ports..
I had the same problem after flashing a few ROMs. I fixed it by updating to the latest radio version (2.15.00.07.28). No problems since.
*fixed*
I also began to have same exact problem after Flashing Stock rom then rooting again.
Pluggin into a backport USB did the trick
My radio was SO old (1.39.00.04.26)
Updated to newest radio (atm 2.15.00.09.01)
That solved my problem, i can again plug the device into any usb port. (i know this thread is kinda old, just wanna leave some info for someone like me google searching)
So i just updated my Zenfone 2 ze551ml and wanted to root the phone. But everytime I enable the USB debugging, it gets enabled for 5 seconds and gets disabled immediately. Doesn't matter if I am connected via USB or not, just keeps getting disabled for no reason.
Twice it has rebooted while enabling the USB debugging, so something is amiss.
Any suggestions on what should be done? I cannot root my phone/install custom rom/recovery without it. This problem started with the last major update, and the new 24mb update did not solve it.
Hello, i got a OPO 5T on OOS 4.7.6 stock kernel rooted and magisk is installed with only a couple of modules ( emoji one and google contacts & dialer enabler) installed.
The problem is, in developer tools, i set the toggle to USB debug on, but after a second goes off by itself. I already searched over the forum here and on OP forum, still can't figure out why USB debug wont stay ON. Either connected to pc or not the toggle will go on and then off.
PS: I can connect to adb in TWRP recovery , so it depends on the rom side.
What could have happened ? im out of ideas and im not likely to go to the format everything route.
Hi everyone!
i installed redmi k40 rom on poco f3 and have been using it for a while now, suddenly i noticed weird vibration sound and hoping that it would be fixed i rebooted my device. After that i havent been able to power my phone 5 hours and then it turned on. But the next time it didnt turn on. Now neither recovery nor fastboot working , its not even charging.
so i decided to do some trick in EDL mode but my phone is detectected as unknown usb device when connected to pc.
Can i revive my phone?
Any help woud be appreciated
Suggesting you flash stock firmware
ive been able to power it and immediately flashed stock miui. During the process it worked fine. After a few hours of using i hear the weird vibration and haptic feedback sound again. im afraid it will deadboot again. so ill try not to shut it down
habib2312102 said:
Hi everyone!
i installed redmi k40 rom on poco f3 and have been using it for a while now, suddenly i noticed weird vibration sound and hoping that it would be fixed i rebooted my device. After that i havent been able to power my phone 5 hours and then it turned on. But the next time it didnt turn on. Now neither recovery nor fastboot working , its not even charging.
so i decided to do some trick in EDL mode but my phone is detectected as unknown usb device when connected to pc.
Can i revive my phone?
Any help woud be appreciated
Click to expand...
Click to collapse
This is Windows 10/11 bugs on recognizing USB ports. Try to re-install all USB related drivers with Test mode ON and Driver Signatures Enforcement OFF.
LinhBT said:
This is Windows 10/11 bugs on recognizing USB ports. Try to re-install all USB related drivers with Test mode ON and Driver Signatures Enforcement OFF.
Click to expand...
Click to collapse
Disabling driver signature verification helped lots of the time.... Personally I suggest Android geeks should use linux
LinhBT said:
This is Windows 10/11 bugs on recognizing USB ports. Try to re-install all USB related drivers with Test mode ON and Driver Signatures Enforcement OFF.
Click to expand...
Click to collapse
There's no need to disable Driver Signature Verification as the drivers are already signed using appropriate certificates.
Always use USB 2.0 ports on your computer and once the drivers are installed just restart your computer.
Driver Signature Verification is off. Using windows 11. Still it sees it as unknown usb device. Also i noticed that when the phone gets warm during mi turbo charging it powers on. This is how i turned it on last time. AFter charging it was warm and when i held the power button it worked
habib2312102 said:
Driver Signature Verification is off. Using windows 11. Still it sees it as unknown usb device. Also i noticed that when the phone gets warm during mi turbo charging it powers on. This is how i turned it on last time. AFter charging it was warm and when i held the power button it worked
Click to expand...
Click to collapse
Please update all your windows PC drivers using iobit driver booster software then install the Qualcomm 9008 drivers
Restart your computer and make sure you use USB 2.0 port as 3.0 port seems to cause issues with edl mode.
Hi,
Windows not recognizing FASTBOOT, as mentioned above it is a Windows thing,
i found the solution on XDA after much head scratching and numerous usb leads,
Buy a cheapy USB HUB, plug the hub into a spare usb slot into your PC and plug your phone into it,
Problem Solved "NO MORE ISSUES"
is the phone stuck in edl mode?
Thanks for the advice
i guess my phone has hardware issue. i heated my phone and tried to turn it on and it worked. After some tome when it got cooler Fast charge stopped working and the vibration became weird again
habib2312102 said:
Thanks for the advice
i guess my phone has hardware issue. i heated my phone and tried to turn it on and it worked. After some tome when it got cooler Fast charge stopped working and the vibration became weird again
Click to expand...
Click to collapse
I brought my F3 in the UK and it came with 24 months warrantee, i still have 4 months left, do you any warranty
unfortunately i dont
Sorry,
I may have jumped the gun a bit, have you tried a USB HUB, is there any life showing on your pc, i replied to a post months ago regarding "NO FASTBOOT" or "RECOVERY" just a black screen but the F3 was still detected by a PC,
have you tried the "Temporary Recovery" program that i put together, there is a option to check your fastboot connection, amongst other goodies,
My F3 is ROCK SOLID,
I do from time to time have strange noises from the vibration motor, but only when in TWRP Recovery,
I hope you sort it.