Is anybody else having problems with the USB Mass Storage on CM 7.0.0?
Some times I need to tap like 4-5 times on the Turn on USB Storage button to turn it on. If I restart the phone, it works after 2 tries.
No OC, Baseband 13.55.55.24H, Kernel 2.6.32.36 nFinity... any tips?
Never happened to me before this post, but, it just happened. <Damn>
USB Mass Storage didnt turn on no matter how many times I tapped on it. The screen would turn off and I would have to tap again, and, if I prevented the screen from turning off, the 'wait' animation would loop endlessly.
A reboot fixed it though. Looks to be one off for me, after I moved some apps to the SD, CM 7.0.2 Stable
I had the same kind of behaviour on CM stable 7.0.3. Always managed to get connected after some tries though, so no issue for me.
Now I'm running nightly #76 and didn't notice this issue anymore. Can be coincidence...
Related
So guys, I've searched but haven't found this yet.
I'm running Syndicate Frozen 1.0.1 with Twilight. Just started today, but whenever I go to mass storage mode my phone stops responding and the vibrate randomly starts and stops until I pull the battery and reboot. The phone works fine otherwise.
This just started today so I have no idea why this is happening. Is there something I can do in recovery to fix it?
TIA!
Hey all, so I'm wondering if anyone else is having this issue:
I put my phone in disk drive, mode, after a restart it works fine at this point. I toggle wifi on, it disconnects from the computer and asks which type of connection again, turn it on and off again, usb teathering seems to do the same thing.
Sometiemes, but not always, it will disconnect every time I pull down the app drawer, which is really weird.
I've tried this on 2 different kernels, on 2 different roms, on 2 different radios, nothing's made a difference.
So has this happened to anyone else?
Also. I can't turn off USB debugging, this is on coredroid, just is ion atomatically when it's in charge only, even if it's unticked.
Curious that noone else is getting this, the only rom I'm not getting this on that I've tried is Virtuous Affinity now, tried their kernel on other roms and still happened though...
Really can't figure out what's causing this, doesn't seem to be because of any rom, kernel, radio, ril or anything else I could think of... I noticed it was mentioned in the RCmix thread, and was blamed on the kernel.. But that wasn't it for me...
Just curious what was causing this...
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Tipika said:
This problem it's becoming more and more frequent - it was once a month, then once a week - now almost daily
The mt3gs starts to vibrate very fast for 5 seconds, black screen with no interaction possibility, and then reboots.
Ever happened to anyone?
I'm running CM 7.2
Click to expand...
Click to collapse
Cant say Ive had the exact same issue, but have had similar. Could be a number of things. Some ROMs have problems with phones rebooting when WiFi is turned on. Not sure about CM7 though. I would recommend making a nandroid backup, and reflash your ROM. If it stops happening, it is likely an app or something corrupted causing it. If it continues, go back to a stock ROM and see how it acts. If it stops now, then it was probably something wrong with the ROM. If it continues, it may be a hardware problem that cant really be fixed. (try a different SD card too.)
Yes, sometimes when i turn on wifi, the phone reboots, but it is a different behaviour - the "wifi reboot" it's a system crash, so the screen suddenly turns in the mt3gs boot logo.
When this happen, it is starts to vibrate a lot (for example, it happened at 4am, it woke me up, even if it was far from my ear), then "dies" for a few seconds (doesn't respond to any button press), and then reboots
very strange...
Hi guys I updated cyanogenmod to the latest nightly and trebuchet disappeared. I had a backup of it but since I had it reinstalled the "ok google" command doesn't work anymore (it does work with the Google now launcher, localization italian) and the goggle now / cm panel is not showing anymore even if the search panel option is checked. Any clue about it?
Then I have a question: I'm running cm11 on my note 2 t0lte. Whenever my battery runs off and I plug in my phone to recharge it there is no possibility whatsoever that I can turn the phone back on by pressing the power button. When the phone is charging there is a big battery icon on the screen that stays always on and keeps staying on even if I unplug it. The only way I can get my phone to restart is to reboot it from recovery or by entering download mode. Is anyone else experiencing the same issue? I've been struggling with it since CM11 came out and it's pretty annoying. Thanks!
Davide
Hi to all,
my beloved tablet suffers of screen problems, infact randomly the screen turns black and i have to restart to make it working again. However, durig this issue the tablet seems to work propely, infact if i connect to the PC, it recongnises the tablet properly and I can access the internal storage and also sdcard , if i try to change the volume I can hear the regolation signal.
Furthermore, also the power button seems to work properly, if I press it once the brightness power off, if I press it again the brightness turns on, but without image.
I would try to use some apps like visor to see if the tablet really continues to work but everytime i forget i have not the pc or with me.
Now I have cm12.1, the same build since a lot of time, and I read something that blames the kernel for this issue, but I'm not sure about it because for a long time I had not problems.
There is a way to solve this problem?
Thanks in advance
Same problem
Hi did you ever solve your problem because I have the same thing happening with similar conditions.Just seems to randomly not show any android but the screen is just lite.thanks Stuart
Sorry bro, I don't have it anymore, I would suggest you to try to go back to latest stock firmware and check if you can solve