Q&A for [KERNEL][V510GPE]SleekAI.
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hi sleekmason, i am going to sell my palman and so i need to get back to stock. I know izs not necessary because the OTAs can be flashed with TWRP but the new owner is not that nerdy as he needs to be.
Can you tell me the steps to revert anything in the right order? I followed all the steps in the OT and have backups etc....
btw...you did a great job with the kernel for v510
flashed the latest kernel (v4) this morning, switched to the wheatley governor .. no anomalies, too soon to tell. I'll give you an update when I have it - thanks for your work on this.
zenrev said:
flashed the latest kernel (v4) this morning, switched to the wheatley governor .. no anomalies, too soon to tell. I'll give you an update when I have it - thanks for your work on this.
Click to expand...
Click to collapse
Was Wheately the default? It should have been. Let me know! I'm still going to add a few things.
Is there any special way to format to try to test the new exfat support? That's what has kept me from using this kernel for the longest time.
I just flashed the latest kernel, erased the SD card within the regular Storage Settings, but the card still fails to mount successfully. I will try to pop the card out and reformat via Windows in the morning to see if that has any impact.
siopaor said:
Is there any special way to format to try to test the new exfat support? That's what has kept me from using this kernel for the longest time.
I just flashed the latest kernel, erased the SD card within the regular Storage Settings, but the card still fails to mount successfully. I will try to pop the card out and reformat via Windows in the morning to see if that has any impact.
Click to expand...
Click to collapse
Why would it keep you from using my kernel? until now, there were no changes to the extension types the sdcards can use, meaning there was NO difference regarding exfat support between the stock kernel and the sleekai kernel.
The device itself will not format the card to exfat. Please let me know if your exfat formatted card works. Not having exfat myself, I am relying on you people to tell me!
sleekmason said:
Why would it keep you from using my kernel? until now, there were no changes to the extension types the sdcards can use, meaning there was NO difference regarding exfat support between the stock kernel and the sleekai kernel.
The device itself will not format the card to exfat. Please let me know if your exfat formatted card works. Not having exfat myself, I am relying on you people to tell me!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50572410&postcount=23
There was something in the old versions that conflicted with exfat formatted cards. I honestly couldn't say what the difference was, but the stock kernel worked fine. It's been a long time since I tried this kernel, but when I did everything else worked great. I just travel a lot for work so I'm always putting movies on the SD card >4GB, so fat32 wasn't an option for me. I'm on lollipop now and it's generally a little more sluggish than KK, so that's what peaked my interest in giving this kernel another shot.
I tried a quick format in Windows, but that did not make a different. I'm still unable to mount the card on the tablet. I'm trying a full format now, but that'll take a while since it's a 64GB card.
Appreciate the help.
siopaor said:
http://forum.xda-developers.com/showpost.php?p=50572410&postcount=23
There was something in the old versions that conflicted with exfat formatted cards. I honestly couldn't say what the difference was, but the stock kernel worked fine. It's been a long time since I tried this kernel, but when I did everything else worked great. I just travel a lot for work so I'm always putting movies on the SD card >4GB, so fat32 wasn't an option for me. I'm on lollipop now and it's generally a little more sluggish than KK, so that's what peaked my interest in giving this kernel another shot.
I tried a quick format in Windows, but that did not make a different. I'm still unable to mount the card on the tablet. I'm trying a full format now, but that'll take a while since it's a 64GB card.
Appreciate the help.
Click to expand...
Click to collapse
I will try to get to a Windows box and format in exfat to test and compile another kernel. Check back in a few days to see if it is resolved.
sleekmason said:
I will try to get to a Windows box and format in exfat to test and compile another kernel. Check back in a few days to see if it is resolved.
Click to expand...
Click to collapse
I certainly appreciate the effort. I did try a full format from Windows, but that didn't have any impact. It's a 64GB G.Skill card, FYI. If there is anything else I can try that might help troubleshoot the issue, let me know.
siopaor said:
I certainly appreciate the effort. I did try a full format from Windows, but that didn't have any impact. It's a 64GB G.Skill card, FYI. If there is anything else I can try that might help troubleshoot the issue, let me know.
Click to expand...
Click to collapse
Okay, updated both versions again. There was a module issue that I cant believe has nobody caught before now. .. including me!
Please let me know if this is working now, and whether you are using kitkat or lollipop.
sleekmason said:
Okay, updated both versions again. There was a module issue that I cant believe has nobody caught before now. .. including me!
Please let me know if this is working now, and whether you are using kitkat or lollipop.
Click to expand...
Click to collapse
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.
siopaor said:
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.
Click to expand...
Click to collapse
It does. I don't know anything about how twrp works though. Sounds like a mount issue. If one of the other developers knows what's happening, I would appreciate the insight.
siopaor said:
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.
Click to expand...
Click to collapse
Okay, there may be something notice for exfat after all. There is a tuxera exfat module that should be available as texfat.ko in /system/lib/module, but it is not being made(compiled) and I dont know why....
But! Here may be a solution after all. I was missing a command in the init.palman.rc for the exfat I Compiled into the kernel from Mako sources.
I still need to get a card formatted exfat when I get a chance. You could try from a terminal emulator using my kernel that should have exfat support with these commands
as root. So first do:
Code:
su
To get root access, then:
Code:
insmod /system/lib/modules/exfat_fs.ko
Code:
insmod /system/lib/modules/exfat_core.ko
to activate the modules. It is worth a try anyway.
You can get a terminal emulator app from the playstore
This would be my next step. If it works, I will put them directly into the rc file
sleekmason said:
Okay, there may be something notice for exfat after all. There is a tuxera exfat module that should be available as texfat.ko in /system/lib/module, but it is not being made(compiled) and I dont know why....
But! Here may be a solution after all. I was missing a command in the init.palman.rc for the exfat I Compiled into the kernel from Mako sources.
I still need to get a card formatted exfat when I get a chance. You could try from a terminal emulator using my kernel that should have exfat support with these commands
as root. So first do:
Code:
su
To get root access, then:
Code:
insmod /system/lib/modules/exfat_fs.ko
Code:
insmod /system/lib/modules/exfat_core.ko
to activate the modules. It is worth a try anyway.
You can get a terminal emulator app from the playstore
This would be my next step. If it works, I will put them directly into the rc file
Click to expand...
Click to collapse
I gave that a shot, but got an error on the first one. I copy/pasted with Pushbullet what you suggested. Here is the output from the terminal:
Code:
[email protected]:/ $ su
[email protected]:/ # insmod /system/lib/modules/exfat_fs.ko
insmod: init_module '/system/lib/modules/exfat_fs.ko' failed (No such file or directory)
255|[email protected]:/ # insmod /system/lib/modules/exfat_core.ko
[email protected]:/ #
I checked that directory, and it looks like the file exists, so I'm not sure what happened. The second command seemed to work fine (no positive or negative response).
EDIT: I just repeated the commands and the first one seemed to work fine now. Maybe the second one just needs to be run first? Now it gives me a message saying the File Already Exists when I re-execute. I haven't noticed anything different. I tried restarting the tablet to see if I noticed a difference, but nothing yet.
siopaor said:
I gave that a shot, but got an error on the first one. I copy/pasted with Pushbullet what you suggested. Here is the output from the terminal:
Code:
[email protected]:/ $ su
[email protected]:/ # insmod /system/lib/modules/exfat_fs.ko
insmod: init_module '/system/lib/modules/exfat_fs.ko' failed (No such file or directory)
255|[email protected]:/ # insmod /system/lib/modules/exfat_core.ko
[email protected]:/ #
I checked that directory, and it looks like the file exists, so I'm not sure what happened. The second command seemed to work fine (no positive or negative response).
EDIT: I just repeated the commands and the first one seemed to work fine now. Maybe the second one just needs to be run first? Now it gives me a message saying the File Already Exists when I re-execute. I haven't noticed anything different. I tried restarting the tablet to see if I noticed a difference, but nothing yet.
Click to expand...
Click to collapse
restarting won't help as you have to run the commands after the tablet has already started. But yes please try again running the second command first and then see if you can see any files, or mount, etc.
sleekmason said:
restarting won't help as you have to run the commands after the tablet has already started. But yes please try again running the second command first and then see if you can see any files, or mount, etc.
Click to expand...
Click to collapse
I restarted to try a clean attempt, ran the exfat_core.ko command followed by exfat_fs.ko and they appeared to go through smooth. Unfortunately, I can't get the SD card mounted still. I tried reformatting the card again and no luck. I created a 30GB partition, formatted in FAT32 and the card mounted without issue. I reformatted the partition back to exfat, but am unable to get it to mount.
Note, I'm still using the Lollipop5.0 version of the kernel, not the latest 5.2, just to clarify.
I appreciate the help and sorry I can't offer more troubleshooting help.
siopaor said:
I restarted to try a clean attempt, ran the exfat_core.ko command followed by exfat_fs.ko and they appeared to go through smooth. Unfortunately, I can't get the SD card mounted still. I tried reformatting the card again and no luck. I created a 30GB partition, formatted in FAT32 and the card mounted without issue. I reformatted the partition back to exfat, but am unable to get it to mount.
Note, I'm still using the Lollipop5.0 version of the kernel, not the latest 5.2, just to clarify.
I appreciate the help and sorry I can't offer more troubleshooting help.
Click to expand...
Click to collapse
that's okay, at least you tried. The original stock kernel has exFAT support through what I believe to be a proprietary driver that was installed during the making of the device and device tree. And in the kernel source that I download to compile a new kernel, it is not there. If I could just find that driver we would be in business. I dont know why it is missing, and maybe I just am not seeing things clearly and it is there somewhere. Ill keep looking.
@siopaor
I think we have a winner! Please give the below kernel LollipopSleekai5.7 a shot
I am very hopeful. I wound up scrapping the exfat code I found in another developers github and went straight to the source. You shouldn't need to insmod or do anything else as I wrote it into the init.palman.rc. Please let me know! Best Regards,
sleekmason said:
@siopaor
I think we have a winner! Please give the below kernel LollipopSleekai5.7 a shot
I am very hopeful. I wound up scrapping the exfat code I found in another developers github and went straight to the source. You shouldn't need to insmod or do anything else as I wrote it into the init.palman.rc. Please let me know! Best Regards,
Click to expand...
Click to collapse
I think you're right. So far, so good. I reformatted back and forth between FAT32 and exfat, copied an 8GB video file to the SD and was able to access and play it without issue. All I did was flash this new version of the kernel and everything worked just fine.
Thanks for the time you spent tracking down the solution for this, very much appreciate it.
Absolutely awesome!!!! I will be making an updated version with fsync enabled by default and other optimizations. So the next kernel out, maybe tonight, you may want to switch out with. Or, you can just keep using this one. It is most definitely good to go. KitKat version coming as well
Related
At first i got error damaged sd card (it isnt damaged i changed 3 sd cards ) then i restart the phone launched link2sd app it ask me what the type of partition (ext2/3/4/fat32) i choose ext2 error invalid argument same if i make the partition fat32 any thoughts?
are you sure it's an ext2 partition? (the 2nd partition)....there's a good tutorial on here somewhere for how to set up your mem card for link2sd. mine is ext3.
if you're not sure, you can try loading the mem card on your pc, right clock, choose properties and it will tell you which file system you are using.
in order to use link2sd effectively, you basically want your main partition to be fat32 (for storage of music/video/whatever), and then your secondary partition should be no more than 1gb and either ext3 or ext4 i think.
mine is set up with around 13gb fat 32, and 1gb ext3, stock rom, rooted, link2sd. works like a charm. look up the tutorial though, and it will tell you how to prepare your sd card before you set up link2sd.
im sure its ext2 and if i make it fat32 i get error faild to connect app bla bla read only file...
alexlarisa said:
im sure its ext2 and if i make it fat32 i get error faild to connect app bla bla read only file...
Click to expand...
Click to collapse
i'm still confused....when you say "it"....you do mean the 2nd partition, right?
you haven't formatted your entire sd card as one huge ext2 partition?
::EDIT::
just found that tutorial.....try following this guide and see if you still have problems afterwards?
http://forum.xda-developers.com/showthread.php?t=1432459&highlight=set+up+sd+card
i'd also suggest that you try different file systems/find out which is most stable for your card....depends on your card and your rom from what i can tell (although, i've also noticed that some configurations that are apparently not compatible, do work, and sometimes better than any other....just try your options, see what works best for you....same goes with most hacking/modding i think, e.g. OC'ing works really well for some guys with the exact same phone as me, but if i OC, my phone goes nuts....I guess it's tiny variations in hardware, but try your options, see what's stable, what works, and stick to that)
Gloris said:
i'm still confused....when you say "it"....you do mean the 2nd partition, right?
you haven't formatted your entire sd card as one huge ext2 partition?
::EDIT::
just found that tutorial.....try following this guide and see if you still have problems afterwards?
http://forum.xda-developers.com/showthread.php?t=1432459&highlight=set+up+sd+card
i'd also suggest that you try different file systems/find out which is most stable for your card....depends on your card and your rom from what i can tell (although, i've also noticed that some configurations that are apparently not compatible, do work, and sometimes better than any other....just try your options, see what works best for you....same goes with most hacking/modding i think, e.g. OC'ing works really well for some guys with the exact same phone as me, but if i OC, my phone goes nuts....I guess it's tiny variations in hardware, but try your options, see what's stable, what works, and stick to that)
Click to expand...
Click to collapse
yes i mean the 2nd partition most stable is fat32 but every 2 days i get an error faild to link app bla bla bla ready only file
Try this tutorial which I used and has certainly worked for me
http://forum.xda-developers.com/showthread.php?p=21119907#post21119907
i did and i have this errors :/
alexlarisa said:
i did and i have this errors :/
Click to expand...
Click to collapse
What type of SD is it? speed/size, etc.
Did you try rebuilding your mount script in Link2SD.
To me it sounds like a bad SD card. Once in a blue moon I will get the second partition not mounting but a quick boot from Link2SD fixes that.
SanDisk class 4 8gb i tryied rebuld the mount script it says invalid argument ....
alexlarisa said:
SanDisk class 4 8gb i tryied rebuld the mount script it says invalid argument ....
Click to expand...
Click to collapse
Has it ever worked for you?
yes but every 2 days i get this error and i have to wipe the partition and remake it
Have you tried doing a full wipe, wipe dalvik, clean reinstall of your ROM?
i am on stock rom s-off rooted
are you OC'd?
I had massive problems when I installed the OC kernel on the stock rom...
alexlarisa said:
i am on stock rom s-off rooted
Click to expand...
Click to collapse
Maybe try flashing a ROM that supports link2SD better (ext2/4 support).
Try something like this if you like sense - http://forum.xda-developers.com/showthread.php?t=1432259
Otherwise flash CM7 !
@Gloris no @se-nsei i am noob at flashing roms but ill give it a shot thx any way
alexlarisa said:
@Gloris no @se-nsei i am noob at flashing roms but ill give it a shot thx any way
Click to expand...
Click to collapse
we were all noobs once, and time to learn is ALWAYS...
so start by flashing recovery... then choose rom and flash it, it's really painless process... most of the times ... u can find all the guides here on the forums ...
b02, you couldn't be more right. We were all noobs until we learned and tried to go just a little bit further. Every day is a learning day. It doesn't hurt to follow some rich tutorials that we can find here, get some practice and maybe later we are "teaching" others how to do things. Nobody should be ashamed of being a noob.
OK , so this is the first time I have actually had to make a post to get an answer to a problem I am facing. Been running Civato's Flex rom for some time now and it was flashed using Team Win . But I can remember having issues finding my directory (externalsd) then, so what I did was just place it on the internal sd to get it flashed. So, now to the problem at hand. I am wanting to change roms and also do a backup, however TWRP will not allow me to place an "x" next to the external SD mount in the mount menu. Therefore I cannot do a backup due to the size limitations of my internal storage. Also how can I flash a rom which requires a full wipe if I cannot access my external sd? Obviously it can't be placed internally because of the necessary system wipe. Also the log in TWRP says failed to locate directory/sdc . Basically TWRP doesnt show the mnt/ directory to get to the external sd card, even in file explorer under the advanced menu. Any input would be awesome! Thanx!!!
fastlyfe941 said:
OK , so this is the first time I have actually had to make a post to get an answer to a problem I am facing. Been running Civato's Flex rom for some time now and it was flashed using Team Win . But I can remember having issues finding my directory (externalsd) then, so what I did was just place it on the internal sd to get it flashed. So, now to the problem at hand. I am wanting to change roms and also do a backup, however TWRP will not allow me to place an "x" next to the external SD mount in the mount menu. Therefore I cannot do a backup due to the size limitations of my internal storage. Also how can I flash a rom which requires a full wipe if I cannot access my external sd? Obviously it can't be placed internally because of the necessary system wipe. Also the log in TWRP says failed to locate directory/sdc . Basically TWRP doesnt show the mnt/ directory to get to the external sd card, even in file explorer under the advanced menu. Any input would be awesome! Thanx!!!
Click to expand...
Click to collapse
You can wipe system, totally different partition. Internal SD mounts to /data/media but using twrp or cwm data wipe won't touch internal SD, so wipe away.
As for not mounting, we won't know why without logs, but try formatting it again on your PC. Android is touchy about any kind of errors or corruption.
Tapatalked from my Galaxy S II.
pio_masaki said:
You can wipe system, totally different partition. Internal SD mounts to /data/media but using twrp or cwm data wipe won't touch internal SD, so wipe away.
As for not mounting, we won't know why without logs, but try formatting it again on your PC. Android is touchy about any kind of errors or corruption.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanx Pio, I took a leap and it worked out for the best. Regardless of the mount issues I was having I went ahead and did the full wipe, then flashed your CM9 build which by the way is now going to be my DD. Thanx for the hard work bro, and not to mention being the first to give some insight. After doing some thorough reading I came across others running into the same external sd mounting issues with TWRP. So, I figured for the time being let it go and just move on. I think I am just going to do the sd/internal swap mod, cancelling out anymore space problems with backups on my internal storage. Again, I appreciate everything you've done for my A100! Later
fastlyfe941 said:
Thanx Pio, I took a leap and it worked out for the best. Regardless of the mount issues I was having I went ahead and did the full wipe, then flashed your CM9 build which by the way is now going to be my DD. Thanx for the hard work bro, and not to mention being the first to give some insight. After doing some thorough reading I came across others running into the same external sd mounting issues with TWRP. So, I figured for the time being let it go and just move on. I think I am just going to do the sd/internal swap mod, cancelling out anymore space problems with backups on my internal storage. Again, I appreciate everything you've done for my A100! Later
Click to expand...
Click to collapse
Happy it worked out for you, however keep in mind one thing: Crossix's mount swap is only active in android, not recovery, so that won't help your space issues there.
Also, the mount swap needs a different setup in CM9 or any non Acer based ROM, it requires the use of script manager or any other script management app. If you need more info on it just ask. It's been mentioned a few times in various threads, and I'm sure a few times in the mount swap thread itself.
pio_masaki said:
Happy it worked out for you, however keep in mind one thing: Crossix's mount swap is only active in android, not recovery, so that won't help your space issues there.
Also, the mount swap needs a different setup in CM9 or any non Acer based ROM, it requires the use of script manager or any other script management app. If you need more info on it just ask. It's been mentioned a few times in various threads, and I'm sure a few times in the mount swap thread itself.
Click to expand...
Click to collapse
:good: Wow, once again thanx. I am glad that you let me know before I went ahead and tried the swap mod. So far the CM9 nightly is polished imo, Team Carbon themes also work great and look clean. I have noticed though that a lot of the other themes I have running on my Epic (CM9) come back with the improperly compiled error, even after a reboot on the system theme. Is this because they are just not meant to be ran on the tablets resolutions? Thnx a lot Pio, ur the shiz :highfive:
fastlyfe941 said:
:good: Wow, once again thanx. I am glad that you let me know before I went ahead and tried the swap mod. So far the CM9 nightly is polished imo, Team Carbon themes also work great and look clean. I have noticed though that a lot of the other themes I have running on my Epic (CM9) come back with the improperly compiled error, even after a reboot on the system theme. Is this because they are just not meant to be ran on the tablets resolutions? Thnx a lot Pio, ur the shiz :highfive:
Click to expand...
Click to collapse
Yeah it seems the more complex the theme, the less likely it works on our device, however stetsonaw has an awesome theme that works on our devices, if you blue is your thing, its linked in the OP for aoikaze. I didn't link it in this nightlies thread as it's meant for pure CM9, Aoikaze is the CM9 based ROM I released a little while ago.
Edit: Forgot to mention, it's included in Aoikaze too, its meant to be run with it, but is optional of course.
fastlyfe941 said:
OK , so this is the first time I have actually had to make a post to get an answer to a problem I am facing. Been running Civato's Flex rom for some time now and it was flashed using Team Win . But I can remember having issues finding my directory (externalsd) then, so what I did was just place it on the internal sd to get it flashed. So, now to the problem at hand. I am wanting to change roms and also do a backup, however TWRP will not allow me to place an "x" next to the external SD mount in the mount menu. Therefore I cannot do a backup due to the size limitations of my internal storage. Also how can I flash a rom which requires a full wipe if I cannot access my external sd? Obviously it can't be placed internally because of the necessary system wipe. Also the log in TWRP says failed to locate directory/sdc . Basically TWRP doesnt show the mnt/ directory to get to the external sd card, even in file explorer under the advanced menu. Any input would be awesome! Thanx!!!
Click to expand...
Click to collapse
The new version of TWRP 2.2.0 might reslove your problem with mounting to external-sd. Zeronull just updated it.
http://forum.xda-developers.com/showthread.php?t=1608152
I've been using USB OTG quite a bit lately since getting the adapter, but I've noticed that there isn't an option to unmount the usbdisk in AOKP at least. Before y'all say it, I've used all the apps that allow for mounting and unmounting the disk, but since LeanKernel supports OTG it mounts the drive to /storage/usbdisk while the apps try to mount it at /sdcard/sda1 or something similar, but the data isn't there so using the unmount option in the app is futile and pulling the usbdisk results in com.media force close and a status bar message saying something like "unexpected media removal" due to not unmounting. I've tried several terminal commands to unmount the block but none have worked so far. Any ideas? Thanks folks.
~~~~There is no spoon~~~~
shag_on_e said:
I've been using USB OTG quite a bit lately since getting the adapter, but I've noticed that there isn't an option to unmount the usbdisk in AOKP at least. Before y'all say it, I've used all the apps that allow for mounting and unmounting the disk, but since LeanKernel supports OTG it mounts the drive to /storage/usbdisk while the apps try to mount it at /sdcard/sda1 or something similar, but the data isn't there so using the unmount option in the app is futile and pulling the usbdisk results in com.media force close and a status bar message saying something like "unexpected media removal" due to not unmounting. I've tried several terminal commands to unmount the block but none have worked so far. Any ideas? Thanks folks.
~~~~There is no spoon~~~~
Click to expand...
Click to collapse
what terminal commands have you tried?
bk201doesntexist said:
what terminal commands have you tried?
Click to expand...
Click to collapse
/system/xbin/umount /storage/usbdisk and /system/bin/umount /storage/usbdisk. I'm not sure exactly where the mount point is, usually root explorer shows the block names, but it seems this is a virtual mount point or something, so I'm kinda lost.
~~~~There is no spoon~~~~
shag_on_e said:
/system/xbin/umount /storage/usbdisk and /system/bin/umount /storage/usbdisk. I'm not sure exactly where the mount point is, usually root explorer shows the block names, but it seems this is a virtual mount point or something, so I'm kinda lost.
~~~~There is no spoon~~~~
Click to expand...
Click to collapse
'mount' will tell you current mount points. to use mount/umount, you need to 'su' first.
Sent from my i9250
bk201doesntexist said:
'mount' will tell you current mount points. to use mount/umount, you need to 'su' first.
Sent from my i9250
Click to expand...
Click to collapse
Yeah I did that, but I didn't see anything about usbdisk in the mount points.
~~~~There is no spoon~~~~
shag_on_e said:
Yeah I did that, but I didn't see anything about usbdisk in the mount points.
~~~~There is no spoon~~~~
Click to expand...
Click to collapse
check dmesg for which blkid/inode the usb device is being recognized by android, then:
su
mkdir -p /storage/usbdisk2
mount -t vfat /dev/something /storage/usbdisk2
umount /storage/usbdisk2
should work if your usb device is on fat32, which it should be, afaik there isn't ntfs support yet.
bk201doesntexist said:
check dmesg for which blkid/inode the usb device is being recognized by android, then:
su
mkdir -p /storage/usbdisk2
mount -t vfat /dev/something /storage/usbdisk2
umount /storage/usbdisk2
should work if your usb device is on fat32, which it should be, afaik there isn't ntfs support yet.
Click to expand...
Click to collapse
Cool I'll try that, but some new info...with my usbdisk plugged in the "mount" command showed /dev/block/vold/8:1 as the mount point so I typed: busybox umount /dev/block/vold/8:1 and the command seemed to go through but there was no output and I still got the error message and media force close. I'll try your steps and let ya know what happens, thanks for the help man.
~~~~There is no spoon~~~~
BUMP! This issue could really use a devs attention. Stickmount does NOT work if using a kernel that supports USB-OTG, so please don't suggest it. Some of the OTG will mirror the drive to a directory on /sdcard but none will unmount the real directory which is /storage/usbdisk. Please help. I'm sure others beside myself can benefit from OTG since we are limited to storage on this device. Thanks.
~~~~There is no spoon~~~~
Hi shag_on_e,
I am experiencing the *exact* same problem as you with Imoseyon's LeanKernel (even tested the latest exp5 release). There is no way to safely unmount a usbdisk using AOKP + Imoseyon's kernel. I have already killed a 32gb micro SD (in a reader) after farting around with it all night, which I can thankfully take back.
I have also had other problems relating to writing data to that 32gb micro SD, but still not sure if that's related to LeanKernel. Android seems to be unable to read the contents of the drive, but the mount point still remains. Hoping a dev (or Imoseyon himself) gets attention of this, and I'll also post something like this in the LeanKernel thread.
Hoping we can get some reliable USB OTG usage in LeanKernel/AOKP soon!
Cheers and thanks.
Unfortunately, this is probably something that will have to be added to the rom side since that is where the user interface is. The kernel just offers support for it. And when using OTG make sure you format the drive to vfat because NTFS isn't supported yet(some apps do though, I think). But even worse I have screamed to the top of my lungs in this forum and Rootz, and others confirm the issue, but no one seems to care much about it. The feature must not be very popular, though i don't see why since we're limited to storage space on the Gnex. Who feels like transferring to pc constantly?, what if you're "On-The-Go" hence the OTG? I'm not gonna give up though...
~~~~There is no spoon~~~~
@shag_on_e, yes, thank you for persisting with this issue, as I am also surprised it's not more of a hot topic considering the GNex only has 16gb of storage, and games these days can be over 1gb themselves leaving less space for backups/media/etc.
Also, I've tried with FAT32 and NTFS, but with NTFS I was using faux123's kernel for that support, as LeanKernel doesn't have NTFS. You're right about the notification item though, I am sure it must need to exist in the ROM rather than the kernel, so maybe tugging on some AOKP coattails would help to bring attention to this.
I'll keep being an advocate for proper, full USB-OTG support too as time goes on!
scar45 said:
@shag_on_e, yes, thank you for persisting with this issue, as I am also surprised it's not more of a hot topic considering the GNex only has 16gb of storage, and games these days can be over 1gb themselves leaving less space for backups/media/etc.
Also, I've tried with FAT32 and NTFS, but with NTFS I was using faux123's kernel for that support, as LeanKernel doesn't have NTFS. You're right about the notification item though, I am sure it must need to exist in the ROM rather than the kernel, so maybe tugging on some AOKP coattails would help to bring attention to this.
I'll keep being an advocate for proper, full USB-OTG support too as time goes on!
Click to expand...
Click to collapse
I'm tugging man! Thanks for the backup! I've bumped my own thread about ten times with new discoveries on the subject in the AOKP General section, but the super-noob threads drown it out, and I get no responses. Anyway since I am die hard AOKP, I hope it supports the function first. I won't be going anywhere either way!
~~~~There is no spoon~~~~
I'm bringing this back up because I feel it's rather important due to the fact nexus devices don't have removable storage and I for one have run out of room on /storage/sdcard0 and USB-OTG is the perfect way to get around this problem. Unfortunately there is no way to properly dismount /storage/usbdisk. Typing the command "umount /mnt/usbdisk" unmounts the drive but upon removal of the flash drive com.android.media force closes. I've got to figure this out, please help!
~~~~There is no spoon~~~~
shag_on_e said:
I'm bringing this back up because I feel it's rather important due to the fact nexus devices don't have removable storage and I for one have run out of room on /storage/sdcard0 and USB-OTG is the perfect way to get around this problem. Unfortunately there is no way to properly dismount /storage/usbdisk. Typing the command "umount /mnt/usbdisk" unmounts the drive but upon removal of the flash drive com.android.media force closes. I've got to figure this out, please help!
Click to expand...
Click to collapse
Same issue here. I wish I could help. I'm on CM10, 11/19 nightly. Any info on how to properly unmount USB OTG media is appreciated!
NookMonkey said:
Same issue here. I wish I could help. I'm on CM10, 11/19 nightly. Any info on how to properly unmount USB OTG media is appreciated!
Click to expand...
Click to collapse
A workaround is to break vold.fstab by just basically editing out a few letters or words in the sources path which will give Stickmount proper control over OTG. I can't find any proper techniques so this works until we get help from someone with some real knowledge about it.
~~~~There is no spoon~~~~
Guess what guys, I thought it would be a smart idea to format my Dincs internal storage to NTFS...I needed to transfer a big file and didn't have anything on it so it seemed like a good idea. Yes I didn't have a flash drive. Anyway, it didn't turn out good. I'm not really worried about being able to use it again (I have a 32gb sd card) but I don't like broken things. I'd like to fix it, I've already done some homework but have got no results. I am currently running this for anyone interested. http://forum.xda-developers.com/showthread.php?t=2143575 Any ideas on how to get it to work again? Even my computer won't read it -___-
AdrianCO said:
Guess what guys, I thought it would be a smart idea to format my Dincs internal storage to NTFS...I needed to transfer a big file and didn't have anything on it so it seemed like a good idea. Yes I didn't have a flash drive. Anyway, it didn't turn out good. I'm not really worried about being able to use it again (I have a 32gb sd card) but I don't like broken things. I'd like to fix it, I've already done some homework but have got no results. I am currently running this for anyone interested. http://forum.xda-developers.com/showthread.php?t=2143575 Any ideas on how to get it to work again? Even my computer won't read it -___-
Click to expand...
Click to collapse
Format the internal SD with recovery?
Sent from my Galaxy Nexus using xda app-developers app
Do you have adb setup and working on your pc?
You need to be in recovery and then open an adb shell. Run the folowing hitting enter after each line.
Code:
parted /dev/block/mmcblk0p3
print
You will see a line starting with "Disk /dev/block/mmcblk0p3: ...MB"
What ever that size says at the end use in the following line.
Code:
mkpartfs fat32 0 ...MB
cmlusco said:
Do you have adb setup and working on your pc?
You need to be in recovery and then open an adb shell. Run the folowing hitting enter after each line.
Code:
parted /dev/block/mmcblk0p3
print
You will see a line starting with "Disk /dev/block/mmcblk0p3: ...MB"
What ever that size says at the end use in the following line.
Code:
mkpartfs fat32 0 ...MB
Click to expand...
Click to collapse
Sorry for the extremely late reply, I've been without internet for the longest time now. Anyways, as much I would've liked to fix it, I've upgraded my device. Thanks a lot for your comment though!:laugh:
I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.
artu72 said:
I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.
Click to expand...
Click to collapse
Same here. Just wanted to post the issue too. It used to work so it must be something new. Problems copying my music to the SD card, can'T delete files and so on.
oneofthekaramosowbrothers said:
Same here. Just wanted to post the issue too. It used to work so it must be something new. Problems copying my music to the SD card, can'T delete files and so on.
Click to expand...
Click to collapse
artu72 said:
I have just bought a new external SD. I formatted it as ext4 in CWM recovery, but I cannot write on it, neither as root (instead in FAT it is working properly). I have Cyanogenmod last nightly. By googling a bit, this seems to be a known issue on KitKat, but I have also read that it should be fixed in Cyano... some help/hint? Instead a nandroid backup from CWM worked. TIA.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.
sasank360 said:
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.
Click to expand...
Click to collapse
Thanks for the hint.
Meanwhile I formatted my SD card as FAT32 again. I ran into problems accessing the card from my Linux machine as well. Somehow everything went wrong suddenly on both my phone and PC.
sasank360 said:
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Use the app from above link. That needs root permissions. Once you grant su and follow steps it should fix that sd card write issues.
Click to expand...
Click to collapse
That app modifies the file /system/etc/permissions/platform.xml
I have already tried editing directly this file and it didn't work. Now I am using FAT32 without problems, but it is stupid that an linux-based operating system does not use natilvely a linux filesystem.