Hi all, I just installed Android 4.2 and I noticed that neither StickMount nor OTG USB Helper are working. In particular, they can find the usb, but they mount an empty folder. Nexus Media Importer is working, but does not mount the usb in a folder. Any idea?
the stock kernel does not support these... you will have to wait until a kernel is released by the devs.
drx69 said:
the stock kernel does not support these... you will have to wait until a kernel is released by the devs.
Click to expand...
Click to collapse
With Android 4.1.2 and Stock Kernel it worked perfectly.
Related
The ms2 have kernel support for USB OTG?
as far as i know: no
Sethdobaloah said:
as far as i know: no
Click to expand...
Click to collapse
Maybe, there is a chance. I've recently installed USB Host Controller app and got the messages in the screenshots below.
The firmware is rooted stock Gingerbread 2.3.4 with some un-Blur modifications. Unfortunately I dont have a USB host port cable yet to run a complete test on this.
Zoli
I tested here with me, and it did not work! : (
someone already succeeded in this?
I use the 2.3.7 rom CM7 tezet!
I've been beating my head against the ground for two full days trying to get a working solution for CIFS under 4.1.2.
Anyone ACTUALLY gotten it to work? 4.1.1 JB CIFS.KO (and related) files do not appear to work. The latest franco kernel Milestone 6 doesn't seem to work.
I NEED CIFS - so I cannot upgrade to 4.1.2 until I'm sure I can get CIFS working again.
Anyone's thoughts would be appreciated.
I also do not have this working... Anyone have a fix?
the .ko files survived the update... but still not working...
EDIT: I would subscribe to this
http://forum.xda-developers.com/showthread.php?t=1781411
I already did just waiting...
SmoothROM 3.2 (4.1.2) supports proper CIFS .. I'm free!
http://forum.xda-developers.com/showthread.php?t=1899024
My current workaround: es file manager's lan support.
Since it is working in a 4.1.2 custom rom, I wonder if the CIFS.KO file was updated or ... if something was built into the ROM to support it.
I'd happily dump the CIFS.KO file if anyone here wants to see if THAT is all it would take.
Please dump the CIFS.KO file here, I'll giv it a try!
Sorry I'm kind of new to all this lingo, but do you mean the File Manager? I seem to be having that problem right now.
kevion4 said:
Sorry I'm kind of new to all this lingo, but do you mean the File Manager? I seem to be having that problem right now.
Click to expand...
Click to collapse
It is just a file browser with lots of features.
Google Play > search > "es file manager"
CIFS works fine with stock 4.1.2 and the faux123 kernel (v012b6es). It has CIFS builtin, no cifs.ko needed.
For those looking to get cifs working on a stock kernel, XDA member chrkad was able to compile the modules to work on stock rooted JB 4.1.2 JZO54K kernel 3.1.10-g009b6d1. See forum link below;
http://forum.xda-developers.com/showpost.php?p=33036537&postcount=115
OK, how 'bout 4.2, now!
jmdearras said:
OK, how 'bout 4.2, now!
Click to expand...
Click to collapse
Negative on stock, rooted 4.2; still using ES LAN support (which still works surprisingly well)
Hi,
I am using cookies & cream 1.3.1 custom rom on my Nexus 7.
Now that 4.2 is out , I'd like to pass to a 4.2 based custom rom.
However, Cookies is discontinued and everybody is talking about a Paranoid Android ROM.
I am not able to find the thread.
Where is the exact thread for this rom ?
thx
Original development forum. C&C is discontinued in name only since Aaron said he'll be merging many of its features into PA 3.0.
Sent from my Nexus 7 using Tapatalk 2
Paranoid Android 2.99 thread is here.
And this is the thread for the earlier version (2.0-2.54) of Paranoid Android that's based on Android 4.1.
thanks. But this thread is in Galaxy Nexus forum.
So I assume it's not fine for Nexus 7 , is it ?
Thanks.
n7 paranoid
try this:
http://forum.xda-developers.com/showthread.php?t=1800268
thanks. That's it
I think...
Paranoid Android runs fine on the Nexus 7. Just download and flash the grouper zip file. I'm staying on 4.1.2 because of too many issues with 4.2's emulated, fused, and symlinked directory structure, so I'm running Paranoid Android 2.54 instead of 2.99 beta 5.1.
thanks for this feedback.
when do you think it will be safe ffor moving to 4.2. ?
Maybe a month for most users.. CWM, TWRP, and Stickmount have workarounds already, I understand.
I'm reading my data from a USB flash drive, using an app that's unsupported, so i may never change to 4.2.
I'm using Stickmount. What's your app for that purpose ? What keeps you from using Stickmount anyway ?
BTw, should I update my recovery before updating to 4.2 ? (TWRP)
exglynco said:
Paranoid Android runs fine on the Nexus 7. Just download and flash the grouper zip file. I'm staying on 4.1.2 because of too many issues with 4.2's emulated, fused, and symlinked directory structure, so I'm running Paranoid Android 2.54 instead of 2.99 beta 5.1.
Click to expand...
Click to collapse
Not sure why the new file system freaks people out so much. For the most part you can just ignore all the symlinks etc. This type of file system is SOP on Linux (which is the embedded OS under android for those that don't know)
The intention of Google was for people to use /sdcard/0 for file management if you are the original/first user. That is not that hard a change from /sdcard is it?
Now that the recoveries are updated there is even less reason to avoid the file system. And perhaps the best reasons not to avoid is that this is the new file system moving forward.
For people who flash and tweak they especially need to gain an understanding rather than avoid it.
Exglynco, this is not directed directly to you. You just happened to express a dislike of the 4.2 file system.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
Ezas,
I actually upgraded to Android 4.2 the morning it went public, and went through the learning curve with all the other early adapters. I lost root, lost my CWM custom recovery and backups, and couldn't see my apps data on my flash drive for a week or more until Stickmount was patched to work with 4.2.
So, I've been through the learning curve, and rejected 4.2, because it doesn't do what I want it to do. I'm storing 10gb of backups and apps data on flash drives connected to my 8gb and 16 gb N7s. I use the orphaned Directory Bind app to bind the source directories on my flash drives to phantom target directories on my N7s in 4.1.2.
In 4.2, Directory Bind will bind the true source directory path (e.g. /mnt/shell/emulated/0/usbStorage/sdb1/xxx) to the phantom target path,(/sdcard/xxx) but my apps don't read their data properly, and Directory Bind won't accept the true target path (/mnt/shell/emulated/0/xxx).
mrmrmrmr, I do use Stickmount, but not with 4.2.
Is there any way to enable usb otg in android one phones?Natively it doesn't support.Can we make it work with any 3rd party software?
manojnagendra said:
Is there any way to enable usb otg in android one phones?Natively it doesn't support.Can we make it work with any 3rd party software?
Click to expand...
Click to collapse
there are 2 things that should matter the kernel and the software...hopefully Thunderzap kernel adds that feature !:good:
Kunal.Kene.1797 said:
there are 2 things that should matter the kernel and the software...hopefully Thunderzap kernel adds that feature !:good:
Click to expand...
Click to collapse
But I could not see anything for usb host support in thunderzap kernel.Where did you find it?
Root your device and install stick mount, it may work
Saif Suse said:
Root your device and install stick mount, it will works perfectly
Click to expand...
Click to collapse
android one doesn't support otg i've tried 16gb pendrive ..
Saif Suse said:
Root your device and install stick mount, it will works perfectly
Click to expand...
Click to collapse
I have tried and not working
Hello.
First time here. Forgive me if not right place to post.
Since android 5.0+, my support for OTG is missing. I'm on CyanogenMod.
On kitkat using CyanogenMod, I had that. Is there something I need to tweak before building to get the OTG working, or I'm missing a line in manifest? Every functionality works with my build, except the OTG.
I've done no changes or tweaks to the cm source when building. I just sync and build, but since 5.0 onwards, my OTG doesn't work.
I plug in USB pen drive or any input device and nothing happens
Thanks.
Sent from my Xperia Z2 using XDA Free mobile app
For some reason they haven't implemented it yet... I don't know why though.