I finally got my original stock firmware back in and started over.
I rooted it and installed the CM11 for my Mediapad.
And it broke it's ability to see the flash drives.
I know the otg works because my external keyboard works perfectly.
I'm wondering if it's something with the filesystem because I noticed an app in the Rom called Externalstorageprovider.
Has anyone else had this problem?
Has anyone come across a way to fix it?
Anyone?
LunaEros said:
I finally got my original stock firmware back in and started over.
I rooted it and installed the CM11 for my Mediapad.
And it broke it's ability to see the flash drives.
I know the otg works because my external keyboard works perfectly.
I'm wondering if it's something with the filesystem because I noticed an app in the Rom called Externalstorageprovider.
Has anyone else had this problem?
Has anyone come across a way to fix it?
Click to expand...
Click to collapse
Well, i don't know exactly the problem. Why don't you try to search for custom kernel that supports OTG drives?
Sent from my SM-T311 using Tapatalk
There isn't a bunch of them for the Mediapad.
Plus it did work on an earlier version. Just that other things didn't work on that one.
I was hoping to get some ideas on what might be wrong here because I found posts where other had this problem too with there tablets.
Not just the Mediapad. Some of them were with CM11 and some were on some earlier versions on theirs.
I hope someone can give me some idea otherwise I guess I'll have to go back to the stock firmware.
ASK
is there anyone CyanogenMod for my GT-S6310 ?
Related
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old
Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...
I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.
I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???
Hi guys i have a problem, my phone always goes to auto speakerphone when i make calls and receive calls, however when i flash back to the stock ROM and radio the problem goes away but when i re rooted the phone and flash any ROM the phone goes to auto speakerphone, by the way my phone was working great this pass few months and it was rooted. Any help will be appreciated
I'm sorry that this happens to you, it seems this error is very rare.
DjManny128 said:
Hi guys i have a problem, my phone always goes to auto speakerphone when i make calls and receive calls, however when i flash back to the stock ROM and radio the problem goes away but when i re rooted the phone and flash any ROM the phone goes to auto speakerphone, by the way my phone was working great this pass few months and it was rooted. Any help will be appreciated
Click to expand...
Click to collapse
Dont know if this will help but this is a common problem with htc's. There are 2 pins in the usb port that get shorted out with gunk,rust, or whatever. I use a pick, some contact cleaner and some fine cloth to clean the pins. I also use compressed air to blow it out. This has happened to a ton of my friends evo's and both of my inspires. Its annoying as hell I know. Hope this helps, good luck
stickbo said:
Dont know if this will help but this is a common problem with htc's. There are 2 pins in the usb port that get shorted out with gunk,rust, or whatever. I use a pick, some contact cleaner and some fine cloth to clean the pins. I also use compressed air to blow it out. This has happened to a ton of my friends evo's and both of my inspires. Its annoying as hell I know. Hope this helps, good luck
Click to expand...
Click to collapse
Thanks for the answer but unfortunately it doesn't fix the problem
I also have this same issue... Works fine no problems on stock unrooted. But once I root I get this same problem.. I have had this same issue in the past but never only on a rooted phone.. I have also been on a rooted ROM for a long time and this issue popped up last week.. Now I am stuck with stock until I can figure this out.
earhog said:
I also have this same issue... Works fine no problems on stock unrooted. But once I root I get this same problem.. I have had this same issue in the past but never only on a rooted phone.. I have also been on a rooted ROM for a long time and this issue popped up last week.. Now I am stuck with stock until I can figure this out.
Click to expand...
Click to collapse
UPDATE: I have the stock ROM but rooted and it works well, however if i install another ROM the problem starts again, I install cyanogenmod and found out what is causing the problem, the car dock mode is automatically turning on, also the car dock apk from other ROMS are newer than the car dock apk from the stock ROM
I was able to disable Cardock in Virtuous Unity but still got the speaker phone issue... I guess HTC fixed this issue in the newest Inspire Rom because of all the phones returned because of it, but those fixes haven't been implemented in community roms.. That's the only explanation I can come up with.
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
DjManny128 said:
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
Click to expand...
Click to collapse
Glad you were able to find the issue. I would let the kernel Dev know about it.
DjManny128 said:
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
Click to expand...
Click to collapse
This problem it's caused by the Kernel
zelendel said:
Glad you were able to find the issue. I would let the kernel Dev know about it.
Click to expand...
Click to collapse
I hope the kernel Dev solves this problem because it is really annoying....
Good luck Kernel Dev XD
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Hope this helps
unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
original post http://forum.xda-developers.com/showthread.php?t=1212260&page=2
by the way the kernel in that post does not work with our phones!!!! DO NOT INSTALL
Okay so Im not that new with rooting androids or with using custom roms, so I'm not that much of a noob. The other day I decided since CM9 was in official nightlies I would give it a try. So I backed up my rom which was stock and rooted and I installed CM9 all through CWM recovery. Once in CM9 i notice the tablet wont connect to my phones tethering which is the only way I can get internet on it so I deciced to go back to my backup. But now on my backup the Wifi wont even turn on, anyideas why?
Hello,
I got exactly the same problem. I have installed CWM 5.5.0.4 and I tried CM9 nightly and return to Nandroid BackUp. Then no more wifi..
I tried to flash differents versions of stock kernels, but it was impossible to flash it : "Installation aborded"..
I used fastboot to install a new recovery : TWRP, but same problem : impossible to flash any kernels..
Does someone has the same problem? Or any idea to solve it?
Thank a lot !
Crystalyse
I also had another question...
is there any rom that will connect to Android tethering (ad-hoc)?
I was able to connect on stock rom rooted with cwm recovery but now every rom I tried so far wont connect to it.
Is there a way to work around this issue
I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.
KB Smoka said:
I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.
Click to expand...
Click to collapse
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.
It's a known issue with wifi not working on stock rooted nandroid backups. If you go back to stock, you will need to follow the step in this post from Xplod.
http://forum.xda-developers.com/showpost.php?p=26435786&postcount=2
meatrocket said:
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.
Click to expand...
Click to collapse
Sent from my ASUS Transformer Pad TF300T using XDA
Worked perfect....Thanks again for this.
Inc2.CM7.Condemned.Wireless.Tether.2.0.7
I've been using the Jellybro kang of CyanogenMod (10-20121120-SKANK-d2vzw). I had NFC working as recently as the 11/3 build, but when I flashed the 11/5 build NFC broke.
I tried flashing a stock JB (deodexed and rooted) rom, enabling NFC and restoring back to my nandroid, but the NFC still wasn't fixed. I've tried the NFCfix.zip and that didn't work either.
Do I need to flash stock.vzw_root66.tar in Odin and turn on NFC? Or is there a specific stock rom I should be using?
What am I doing wrong, or what else should I try? I've done my best to search the forums and figure out a solution, so figure me if there has been clearly hashed out elsewhere.
Thanks!
[edit] Solution: flash this NFC fix http://www.mediafire.com/?y6vx27cpaasqhxs
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
ddurandSGS3 said:
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
Click to expand...
Click to collapse
Let me give it a shot. Are you suggesting any TW ICS rom or specifically a stock ICS? Can you link me to the rom you use, please?
Thanks!
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
i use a stock rooted from scottt that i have saved on my laptop to fix my NFC.
ive seen people ahve success wth the zips floating around, try that first its quickest easiest
Polymira said:
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
Click to expand...
Click to collapse
Perfect! That fixed it. Thank you very much.
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
majixx11 said:
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
Click to expand...
Click to collapse
I'm having the exact same problem and seems like no one can help with this
On my S4 I9505 I can turn on S4 but then nothing happens whenever I try to scan any tag... Any ideas? I flashed different stock roms and tested 3 different batteries with visible loop antennas on them. Nothing works.
Hey guys,
So today I decided to update to a new Lollipop rom. I've been through three so far, and each have the same problem: upon first boot, the phone will try to activate itself and fail, and will never be able to connect to any data services. However, on my old 4.4.4 rom everything works fine. I've tried restoring to stock, various roms, and different recoveries, as well as editing my APN (which never saved when I tried to). I'd rather not be stuck without Lollipop for my phone's life, so can anyone help?
Thanks!
Are you on Sprint?
I am.
bingo.
youll need the sprint stuff for lollipop. i have no idea where they would be gotten. maybe you can try the old sprint "fix". search it, i bet you find it.
I'll look for it now! Appreciate the help!
Edit: I found a thread that looks promising for anyone else with the same issue as I.
http://forum.xda-developers.com/google-nexus-5/general/fix-sprint-data-to-custom-roms-t2541924
EDIT 2 IT WORKS WOOOOOOOOOOO
ffej96 said:
I'll look for it now! Appreciate the help!
Edit: I found a thread that looks promising for anyone else with the same issue as I.
http://forum.xda-developers.com/google-nexus-5/general/fix-sprint-data-to-custom-roms-t2541924
Click to expand...
Click to collapse
i was just about to post the same thread