Related
I do not want it i'm perfectly fine with my phone the way it is I get great battery life my wifi tether works great and i have read up on all these forms there is no way of getting the update without losing something.Either root or wimax or something so i don't want the update yet everyday it keeps popping up how can i stop this? And is there anybody out there that is not running any rom that has got the update successfully and not lose anything preferable with unrevoked 2?
auau465121 said:
I do not want it i'm perfectly fine with my phone the way it is I get great battery life my wifi tether works great and i have read up on all these forms there is no way of getting the update without losing something.Either root or wimax or something so i don't want the update yet everyday it keeps popping up how can i stop this? And is there anybody out there that is not running any rom that has got the update successfully and not lose anything preferable with unrevoked 2?
Click to expand...
Click to collapse
This has been posted before but here's a quick rundown.
1. First, you need a root method that allows you to modify the /system directory. I prefer Toast's but I think Unrevoked2 allows this as well.
2. Download the android sdk. Open a command prompt, cd into the directory you extracted it in and type in the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.old
Reboot and tada. You'll never see a popup again.
It would Be nice to find an answer for your question too.. (never mind "chuckhriczko" answered just before me posting )
But incase you care I also got the message on my phone and my wife's phone while running ROM OMJ 1.4r.. but only got it once no repeats I installed ROM Fresh 0.5.3 on both phones yesterday and I have not been asked to do the update on either phone and I have rebooted the phones multiple times..
Take care..
P.S.
chuckhriczko
Thank you for the info..
This has been posted before but here's a quick rundown.
1. First, you need a root method that allows you to modify the /system directory. I prefer Toast's but I think Unrevoked2 allows this as well.
2. Download the android sdk. Open a command prompt, cd into the directory you extracted it in and type in the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.old
Reboot and tada. You'll never see a popup again.
Click to expand...
Click to collapse
Thanks trying now
It would Be nice to find an answer for your question too.. (never mind "chuckhriczko" answered just before me posting )
Click to expand...
Click to collapse
yeah but thanks
Maybe I'm missing something, but why can't you just go into:
System Updates -> HTC Software Update
and uncheck "Scheduled Check"
I've recently rooted my Desire Z and flashed Virtuous G-lite on it. One thing I really miss is an FM Radio app like the one of HTC Sense. I'm really searching for an app that receives FM, and not streams it over the internet.
I've searched the market but I haven't found anything, XDA forums had lots of hits but nothing that resolved my issue.Then I got a suggestion someone might be able to make an APK out of the Sense FM Radio.
So basically my question: Is there an app which alows me to receive FM Radio in the market? Or could anyone please wrap up an .apk from stock HTC Sense so I could try that out?
take a look at Spirit FM Radio
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Awesome, I like this radio more the CM's.
Sent from my T-Mobile G2 using XDA Premium App
pmcqueen said:
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
Click to expand...
Click to collapse
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Puffballofdoom said:
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Click to expand...
Click to collapse
poo. make sure permissions are correct.
I don't ever use the FM radio so I'm not really familiar with how it works or if it relies on files outside of the apk to work. I do know that it requires bluetooth & headphones (headphones are used as antenna).
let me do some digging and I'll post back if I find anything.
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Puffballofdoom said:
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Click to expand...
Click to collapse
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
adb shell
su
mount -o rw,remount /system/app
mv /sdcard/FM.apk /system/app/
chmod 644 /system/app/FM.apk
reboot
Click to expand...
Click to collapse
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Why don't you just use tune in radio? It gets a ridiculous amount of stations and doesn't need headphones for an antenna. Try it!
Sent from my HTC Vision using XDA App
Tune In streams from internet, since I have a 1GB/month datalimit I really need FM to keep my data usage under 1GB/month.
Pmcqueen: I will try that first thing in the morning!
Sent from my T-Mobile G2 using XDA App
pmcqueen said:
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Click to expand...
Click to collapse
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Puffballofdoom said:
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Click to expand...
Click to collapse
try just
mount -o rw,remount /system
(no /app, but since it is a subdirectory it will inherit the r/w access)
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Puffballofdoom said:
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Click to expand...
Click to collapse
well darn it.
mount -o remount,rw /dev/block/mtdblock3 /system
^^ should get system mounted as read/write.
if not, do you have root explorer? we can do it that way as well, it's just faster to use terminal emulator/adb if it's not being tempremental.
So back at home once again, I tried the same commands from CMD and I'm getting the same message. I really don't know what's going on, it seems like the command isn't correct because it returns the possible options. Google hasn't come up with any suggestions too..
EDIT: Lol you posted at the time I was making this post, I will try what you said. I don't have root explorer, yet, let's see if your suggestion works, else I will need to find myself a copy of that root explorer
# su
su
# mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/FM.apk /system/app/
mv /sdcard/FM.apk /system/app/
failed on '/sdcard/FM.apk' - Cross-device link
#
Seems like your suggestion worked, but then moving the FM.apk failed. Any hints on that? Google tells me something about unmounted devices, but I can't find any solutions..
try just copying it instead. I saw this come up once before and I know a [very lengthy] workaround, but since it doesn't hurt to have a backup on your sdcard in the first place, might as well just copy...
just replace "mv" in the command with "cp"
let me know if that works or not.
edit: also, try adding busybox to the beginning of your command... ie:
busybox cp /sdcard/FM.apk /system/app
or
busybox mv /sdcard/FM.apk /system/app
Thanks, the busybox command did the trick. All commands execute perfectly now, but the FM radio still ain't working. Instant FC on launch (Bluetooth turned on and headset plugged in)
i also flashed virtous g-lite, but psx4droid can not load game with this rom. so i have to back to cm now. do you use psx4droid? how about its performance? pls let me kown.thanks.
Well I got Root Explorer, it looks usefull and I have used it with pleasure already. But moving/copying the FM.apk, it still doesn't work.
Anyone any thoughts?
I didn't have a GN until this week so my only LIMITED experience was with my nephew's GN and I was not able to connect it to my Ubuntu 11.10, 11.04, 10.10 or Mint 12. I got my own this week and started the search. Here is how you do it courtesy of Shannon VanWagner
and his website Humans Enabled
Shannon's info:
https://plus.google.com/115207567016362184954/about
Thanks Shannon. Here is the what you should do: again all credit goes to Shannon VanWagner. Fire up a terminal session:
1-
Code:
sudo apt-get install libusb-dev
2- download libmtp tar.gz from http://sourceforge.net/projects/libmtp/files/libmtp/
3-cd to the directory you downloaded to: Download in this case, case sensitive
Code:
cd Downloads
4- extract the tar package
Code:
tar xvf libmtp-1.1.1.tar.gz
please make sure you check the file version, this file changes as it is updated and change it accordingly per the above website
5- cd to the newly created folder that has the extracted file:
Code:
cd libmtp-1.1.1
again don't forget to change the name if the version has changed
6- compile and install: do each step separately
Code:
./configure --prefix=/usr
Code:
make
Code:
sudo make install
7- while in the same directory in the terminal, copy the rules from there to the udev folder:
Code:
sudo cp 69-libmtp.rules /etc/udev/rules.d
8- install gMTP:
Code:
sudo apt-get install gmtp
9- open up gMTP, go to edit/prefrences and check the box for Always Show Download Path. This way when you are downloading from the phone to your computer, you are asked to choose a location. Use the Add button to upload from your Linux Box to the phone. Delete does, well, Delete a file.
Thanks so much for this. I was having all kinds of problems! Worked flawlessly!
I'm just wondering, why people still using USB cable for file transfers? There's gazillion threads here about broken USB ports and all of them are reall. I had my self that problem on SGS2 and since then i started to use Wifi Explorer. It's just safer and easier.
Don't take this as thread spoiling, i'm really thankful to everyone who shares info. l'm just trying to warn you, because USB port problem does exist even if you're extremely careful as i am.
Sent from my super Galaxy Nexus plus®
I love Wifi Explorer as well but you do run a much greater risk of a corrupted file over wifi as opposed to usb.
I didn't have to do step 2. All I did was install libusb-dev and install gMTP and it worked.
That said I hate what google did here! I can no longer play music via usb on my car deck because of this
MS. said:
I'm just wondering, why people still using USB cable for file transfers? There's gazillion threads here about broken USB ports and all of them are reall. I had my self that problem on SGS2 and since then i started to use Wifi Explorer. It's just safer and easier.
Don't take this as thread spoiling, i'm really thankful to everyone who shares info. l'm just trying to warn you, because USB port problem does exist even if you're extremely careful as i am.
Sent from my super Galaxy Nexus plus®
Click to expand...
Click to collapse
Thanks for the suggestion. I do use that especially since Amazon App store had it as the Free Paid app of the day a few months back. But you still need your wired connection for important files like radios, kernels, and roms. hate corrupted radios
Then i must be lucky, had no corrupted transfers yet (or at least i didn't notice that)
apt-get install gmtp fails.... I get the following::
Reading package list... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package gmtp
What now? I'm running 64bit Ubuntu 10.04 LTS
Hello, I wonder if can I expect a Fedora solution?
DAG425 said:
apt-get install gmtp fails.... I get the following::
Reading package list... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package gmtp
What now? I'm running 64bit Ubuntu 10.04 LTS
Click to expand...
Click to collapse
I'm sure you did sudo apt-get, right?
gMTP is in the Ubuntu software center. I guess you can get it that way too.
Yes, any time i know im gonna need sudo multiple times i just run root terminal.... Got it from package manager! Thanx!!
Anyone else noticing massive slow ups when transferring files? The only things that happens quick is to download something from the device, uploading, and deleting take forever.
Thanks man for the guide.
its working but its supposed to be so slow(connect takes so long)??
Hi I've followed your guide down to the letter but my Nexus won't mount gMTP hangs and refuses to respond. What do you suggest?
emmib said:
Hi I've followed your guide down to the letter but my Nexus won't mount gMTP hangs and refuses to respond. What do you suggest?
Click to expand...
Click to collapse
a little info may help. What version of Ubuntu are you running? Any errors?
You may also want to look in to mtpfs which is a FUSE filesystem providing access to MTP devices. It's easy to use and with correct permissions you can mount the device as a user.
I've been using it and there is a long pause mounting the device for some reason but read / write speeds are very good. When the phone is connected you simply mount it with:
mtpfs [mount point]
Lost Dog said:
You may also want to look in to mtpfs which is a FUSE filesystem providing access to MTP devices. It's easy to use and with correct permissions you can mount the device as a user.
I've been using it and there is a long pause mounting the device for some reason but read / write speeds are very good. When the phone is connected you simply mount it with:
mtpfs [mount point]
Click to expand...
Click to collapse
so you just connect the point and type the above? Do you have to specify the mount point? What do you use?
loveubuntu said:
so you just connect the point and type the above? Do you have to specify the mount point? What do you use?
Click to expand...
Click to collapse
Make a directory to mount it at (~/phone or something). Connect your phone in MTP mode then type:
mtpfs ~/phone
It's user space so you don't need to use su or sudo. You do however need to have FUSE support in your kernel. You may need some of the other dependencies but if you install mtpfs in mint it should pull those in (I'm using Mint 12).
loveubuntu said:
a little info may help. What version of Ubuntu are you running? Any errors?
Click to expand...
Click to collapse
I'm terribly sorry about that, how rude of me XD I'm not running Ubuntu, I'm running Linux Mint 12, 32-bit. My Nexus is completely stock, GSM, running 4.0.2.
I finally can transfer files between ubuntu and my galaxy Nexus. Dumb google.
It took me days to find this thread. Wow you are amazing. I have tried different tutorial that would freeze my pc. Thanks for for sharing.
I have managed to get CIFS working on stock Nexus 10.
It's quite a bit more problematic on the Nexus 10 than normal.
There are 2 main issues to deal with. Newer versions of the Linux kernel require a UNC variable to be passed to them and the current version of busybox doesn't do this. There is a patch out. I have extracted the patched busybox binary from craigacomez's AOSP Nexus 10 rom.
(Check it out here: http://forum.xda-developers.com/showthread.php?t=1998585 ). Otherwise it should work on the stock mount command if you specify the unc= mount option with the share.
The other issue is the multiuser stuff. If you execute the mount command from inside Terminal Emulator (or a script program) it looks like it mounts ok and you can 'ls' in the directory but it doesn't work for Android apps, they just see an empty directory but if you do it via a 'adb shell' it works fine in Android apps. My theory is ADB is outside of the multiuser stuff. adb actually ships on the device.
1) Unlock bootloader (fastboot oem unlock)
2) Flash recovery adb flash recovery whatever.img
3) Root device (flash CWM-SuperSU-0.98.zip)
4) Install BusyBox (from the market)
5) Copy md4.ko and cifs.ko to device. The files can go anywhere you like. In this example I will just use the root of the sdcard. Some people like them in /system/modules or /system/lib/modules
6) busybox mount -o rw,remount /
7) adb shell
8) Override /system/bin/busybox with the patched version (maybe move it first so it's backed up).
9) insmod /sdcard/md4.ko
10) insmod /sdcard/cifs.ko
11) busybox mount -t cifs -o username=MYUSER,password=MYPASS,unc=\\\\192.168.1.1\\storage //192.168.1.1/storage /data/media/0/cifs/Storage
You will need to manually preform the last 3 commands each time you reboot the device from a adb shell.
NOTE: You can probably get rid of the -o flags completely. In theory the patched version of busybox makes the UNC bit redundant. Possibly you can use the stock busybox with the UNC flag and avoid using the patched one totally. I have just included it to be sure.
Make sure you type 'busybox mount' not 'mount', by default they are different binaries. Otherwise you can remove the /system/bin/mount command and make a new one linking /system/bin/mount to /system/bin/busybox.
Possibly there is some way to get the mount working in the multiuser environment without requiring busybox. If you figure it out please tell ☺
Some threads on the issue:
http://forum.xda-developers.com/showthread.php?p=34397868#post34397868
http://forum.xda-developers.com/showthread.php?t=733490&page=6
http://www.mail-archive.com/[email protected]/msg17650.html
The modules are for 3.4.5-g4e6298b.
EDIT: I added nls_utf8.ko by request
EDIT2: Since adb comes on the device, it is possible to use it to connect to local host:
1) Install cifs modules to /system/lib/modules
2) Install Script Manager from the play store
3) Copy script to device
4) Start SManager
5) Find your script and open it.
6) Tick the su box
7) Hit save
8) Goto home sccreen
9) Add a 'SMShortcuts' widget to your home screen
10) "Add one script shortcut"
11) Choose your script
12) Optionally use this pretty icon ☺
13) Give it a nice name like "Mount Shares"
Here is a shell script...
Code:
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
EDIT3: Added usbserial.ko, option.ko and usb_wwan.ko
EDIT4: Some users have reported that the need to modify the script to get it working with their version of SU.
EDIT5: I have uploaded modules for 4.2.2, kernel 3.4.5-gaf9c307 but I haven't actually tested them myself (still on 4.2.1). Apparently the adb loophole has also been patched but it is possible to reenable it by putting a RSA key onto the device. Check out this set of instructions here.
EDIT6: I have updated to 4.2.2 on my Nexus 10 and can confirm the new modules work.
You must setup the adbkey or you will get a "device: offline" message. By default adb when adb first runs it tries to create the keys in the $HOME dir which is /data/.android, but the data directory isn't accessible by the 'shell' user.
I got it working simply by setting the HOME variable to /sdcard and restarting the adb server in the script then Android popped up a query (I have update the script above).
IMPORTANT: The Android Media scanner recursively scans folders for media to add the the database so it shows up in programs like Google Music. On large shares this can be a long process and use heaps of battery life. To prevent this add a blank file with the name ".nomedia" to the root of your mount points (or each individual share if you aren't used 1 folder for all your mounts). This will stop music showing up in programs though.
If you find that the device stops responding (the launcher might work but apps fail to load) or you get reboots (often after the previous bug) this is probably due to a bad wifi connection.
Is it posible to make a CWM flash file?
Great
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
alias_neo said:
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
Click to expand...
Click to collapse
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
craigacgomez said:
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
Click to expand...
Click to collapse
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Although I don't have nexus 10, I am having the similar mounting issue on my nexus 7 until I saw this post.
Advise about "adb shell" really helps me resolve the multiuser issue.
Thanks for sharing.
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
H3g3m0n said:
1) Unlock bootloader (adb oem unlock)
Click to expand...
Click to collapse
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
momulah said:
Is it posible to make a CWM flash file?
Click to expand...
Click to collapse
Not a high priority right now as currently you need to do the manual adb shell stuff by hand to get things mounted, a little extra setup work isn't a huge difference.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
Are you mounting in a 'adb shell' or locally in something like terminal emulator? My OTG cable won't be here for a while so I can't really test myself.
weasal said:
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
Click to expand...
Click to collapse
Posted, haven't tested it but it seemed to insmod fine.
espionage724 said:
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
Click to expand...
Click to collapse
Yeh typoed, i'll fix that now.
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
I've been working on getting OTG support natively in my AOSP based custom ROM and I have had some success... check out my ROM for details
H3g3m0n said:
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
Click to expand...
Click to collapse
Just wanted to thank H3g3m0n as I was able to successfully mount over adb. Also came up with a workaround to bypass connecting to a PC, grabbed the arm fastboot binary from this thread and installed it on my nexus 7. Used it to connect wireless adb on the 10 and ran the mount commands on the 7.
H3g3m0n said:
Posted, haven't tested it but it seemed to insmod fine.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
You might find my posts #156 and #162 at http://forum.xda-developers.com/showthread.php?t=1781411&page=17 helpful.
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
spdwiz18 said:
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Loadable_kernel_module
craigacgomez said:
http://en.wikipedia.org/wiki/Loadable_kernel_module
Click to expand...
Click to collapse
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
These modules are needed to enable support for CIFS (Windows share) mounts...
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
Basically you can setup a shared folder from a remote computer. It allows you to have files on another system accessible as if it was part of the internal storage in the device.
Just found out that Android ships with the adb binary on the device itself (after crosscompiling it myself :/, oh well the experience was useful).
It should be possible to setup a script to start the adb server, connect to the localhost and execute the mount without too much difficulty.
Ok, added a script and instructions to the front page for simple on tablet mounting.
I Received my new fire TV, inserted the SD card which was recognized and formatted by the Fire tv. Card works fine in the Amazon area, reading and writing. When i go into Kodi 15.1 it seems the card cannot be written to. It can read it fine. I go into the file manager and try to create a folder and it does not create. i have tried the substitution of the thumbnails from advancedsettings.xml and it seems that works ok, but no files are written to the sd card. as soon as i remove the substitution its able to write the the thumbnails to the internal memory
Has anyone else had this problem? 8GB is just not enough and I was hoping to at least put the thumbnail cache on the sd card
Kodi 15.1 Isengard doesn't support Lollipop's new external storage permission scheme. Upgrade to Jarvis.
Isengard 15.x/Lollipop can write to both sdcard1 and to usbotg as long as you set up a properly sandboxed area. For Kodi:
For the sdcard:
mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
For a stick:
mkdir -p mkdir -p /storage/usbotg/Android/data/org.xbmc.kodi/
Kodi writes to anything below org.xbmc.kodi w/o problems.
How to?
---------- Post added at 01:31 PM ---------- Previous post was at 12:36 PM ----------
sh-3.2$ mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
mkdir: /storage/sdcard1/Android/data/org.xbmc.kodi/: Permission denied
shrgawi said:
How to?
---------- Post added at 01:31 PM ---------- Previous post was at 12:36 PM ----------
sh-3.2$ mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
mkdir: /storage/sdcard1/Android/data/org.xbmc.kodi/: Permission denied
Click to expand...
Click to collapse
You have to adb shell into your device first.
i used the mkdir -p method and that worked...thanks
i tried the mkdir -p method and that works fine. i thought updating to fire tv os 5 yesterday might have undone as i couldnt write to the SD card from Kodi for a time. somehow managed to get it works again so all is ok witht he SD card in Kodi.
Thanks
can you please explain a step by step procedure?
i still have the problem after adb shell
shrgawi said:
can you please explain a step by step procedure?
i still have the problem after adb shell
Click to expand...
Click to collapse
This is for the FireTV/2 using adbFire:
1. Connect to your device
2. Press ADB Shell
At the prompt "[email protected]:/$"
If you have an microsd inserted into the AFTV/2:
Code:
mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
If you have an USB stick inserted into the AFTV/2:
Code:
mkdir -p /storage/usbotg/Android/data/org.xbmc.kodi/
Just to follow up, I upgraded a stock FTV1 to OS 5.0.3:
A mounted USB stick reports back as /storage/usbdisk
The shell prompt is: "[email protected]:/ $"
Kodi can't write to /storage/usbdisk
But
Code:
mkdir -p /storage/usbdisk/Android/data/org.xbmc.kodi
works and Kodi can write to anywhere under the kodi sandbox.
jocala said:
This is for the FireTV/2 using adbFire:
1. Connect to your device
2. Press ADB Shell
At the prompt "[email protected]:/$"
If you have an microsd inserted into the AFTV/2:
Code:
mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
If you have an USB stick inserted into the AFTV/2:
Code:
mkdir -p /storage/usbotg/Android/data/org.xbmc.kodi/
Click to expand...
Click to collapse
Just wondering if this still works on AFTV2 on rboxs 5.0.5 r4 prerooted rom? I'm on kodi 16.0 & have moved all my kodi data to my sdcard using the guide on aftvnews, it's all working fine except the write permissions to sdcard, is this still working?
Thanks in advance
deanr1977 said:
Just wondering if this still works on AFTV2 on rboxs 5.0.5 r4 prerooted rom? I'm on kodi 16.0 & have moved all my kodi data to my sdcard using the guide on aftvnews, it's all working fine except the write permissions to sdcard, is this still working?
Thanks in advance
Click to expand...
Click to collapse
For atv 1st gen USB drive only (would work for 2 also)
Follow instructions as described by Jocala above (use ADB Shell....... etc). NOTE: There is a difference between the command for the AFTV 1st and 2nd Gen USB (read carefully).
I believe I got this finally worked out. The key is to create the "Sandbox" as described. You need to "add" a source BUT dont open the USBdisk as you normally would. Navigate from the root/storage ... etc. Once you add the source (it will have the long address /storage/usbdisk/Android/data/org.xbmc.kodi) as it states, but you will see a second USBdisk listed in File Manager, which is the same as the other, but routed thru the sandbox you setup. This is the "sandbox". I actually save data to a NAS (over 55mb throughput, its fine), but I have a second Fire TV 1st gen that is connected to an airport extender so the "sandbox" is a must on this unit as I save game data to it for my kid.
Thanks so much to joebuddy78 and Jocala (Im doing my Basil Fawlty impression, hitting myself over the head with a branch !):good:
Help!
jocala said:
Just to follow up, I upgraded a stock FTV1 to OS 5.0.3:
A mounted USB stick reports back as /storage/usbdisk
The shell prompt is: "[email protected]:/ $"
Kodi can't write to /storage/usbdisk
But
Code:
mkdir -p /storage/usbdisk/Android/data/org.xbmc.kodi
works and Kodi can write to anywhere under the kodi sandbox.
Click to expand...
Click to collapse
jocala said:
This is for the FireTV/2 using adbFire:
1. Connect to your device
2. Press ADB Shell
At the prompt "[email protected]:/$"
If you have an microsd inserted into the AFTV/2:
Code:
mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
If you have an USB stick inserted into the AFTV/2:
Code:
mkdir -p /storage/usbotg/Android/data/org.xbmc.kodi/
Click to expand...
Click to collapse
deanr1977 said:
Just wondering if this still works on AFTV2 on rboxs 5.0.5 r4 prerooted rom? I'm on kodi 16.0 & have moved all my kodi data to my sdcard using the guide on aftvnews, it's all working fine except the write permissions to sdcard, is this still working?
Thanks in advance
Click to expand...
Click to collapse
OK, maybe I am doing something wrong. I am having issues with FireTV with my V1 Console. I’ve been searching for weeks. I can’t save to the USB memory on my FireTV box. Yes, I did update the path. in the settings. Videos act as if downloading but not. I’ve factory reset and reinstalled Kodi. Still did not work. I found this page in my research, and I saw the answers for V2, with a note about V1. I am not rooted, is that perhaps the problem? I have not even looked into that. I did log into to the console with adbfire and pasted this: mkdir -p /storage/usbdisk/Android/data/org.xbmc.kodi. I did not get an error, it just showed the next line.
I went back into Kodi, settings are still set to save to the usbdisk, but no dice. I am sure I am just doing one minor thing wrong. Can you guys help? I see a LOT of people facing this issue too, so I will share along if I can get it to work.
Thanks!
RaiderMS3 said:
OK, maybe I am doing something wrong. I am having issues with FireTV with my V1 Console. I’ve been searching for weeks. I can’t save to the USB memory on my FireTV box. Yes, I did update the path. in the settings. Videos act as if downloading but not. I’ve factory reset and reinstalled Kodi. Still did not work. I found this page in my research, and I saw the answers for V2, with a note about V1. I am not rooted, is that perhaps the problem? I have not even looked into that. I did log into to the console with adbfire and pasted this: mkdir -p /storage/usbdisk/Android/data/org.xbmc.kodi. I did not get an error, it just showed the next line.
I went back into Kodi, settings are still set to save to the usbdisk, but no dice. I am sure I am just doing one minor thing wrong. Can you guys help? I see a LOT of people facing this issue too, so I will share along if I can get it to work.
Thanks!
Click to expand...
Click to collapse
You do not need to be rooted. Make sure you are saving to the correct location when saving. Its pretty easy to confuse the internal location with the USB location (ie: /storage/emulated/O/Android/..... with the /storage/Usbdisk/.......).
Also, is this a gen 1 or gen 2 AFTV ? The command is different.
nuggyblake said:
You do not need to be rooted. Make sure you are saving to the correct location when saving. Its pretty easy to confuse the internal location with the USB location (ie: /storage/emulated/O/Android/..... with the /storage/Usbdisk/.......).
Also, is this a gen 1 or gen 2 AFTV ? The command is different.
Click to expand...
Click to collapse
I am on Gen1.
And I figured it out. I was not thinking. The MKDIR command for V1 to create the directory to save files to. mkdir -p /storage/usbdisk/Android/data/org.xbmc.kodi. I just changed the paths for the TV download in Genesis to /storage/usbdisk/Android/data/org.xbmc.kodi/files and IT WORKED for a TV show. So that fixed it!
I cant delete media content from external drive with kodi on Marshmallow
Hi Guys!This fix with adb shell work on Nvidia Shiel TV because i tried to delete media content from library but without success.I tried to delete manually from kodi file manager but i get same error.Is problem with permission?I get this "Error static bool Xfile::Cfile:elete(const Curl&) error deleting file and i get warning virtual bool Xfile::Cposix file :elete(const Curl&) can`t acces file storage nr....
muschiu35bv said:
Hi Guys!This fix with adb shell work on Nvidia Shiel TV because i tried to delete media content from library but without success.I tried to delete manually from kodi file manager but i get same error.Is problem with permission?I get this "Error static bool Xfile::Cfile:elete(const Curl&) error deleting file and i get warning virtual bool Xfile::Cposix file :elete(const Curl&) can`t acces file storage nr....
Click to expand...
Click to collapse
not sure if a question or statement, but if wondering if this will work, it might. I would follow the steps and see.
@jocala thanks so much for this, with the floppy disk storage amazon gave us this really helps!!
Addons no longer working
jocala said:
This is for the FireTV/2 using adbFire:
1. Connect to your device
2. Press ADB Shell
At the prompt "[email protected]:/$"
If you have an microsd inserted into the AFTV/2:
Code:
mkdir -p /storage/sdcard1/Android/data/org.xbmc.kodi/
If you have an USB stick inserted into the AFTV/2:
Code:
mkdir -p /storage/usbotg/Android/data/org.xbmc.kodi/
Click to expand...
Click to collapse
Hi Jocala, did this on my 2nd Gen Fire tv and then moved all Kodi data to micro sd card, some how I've messed up as most of my addons are now not functioning. Some will not gather any sources or are unresponsive , while others just show my own added file tree, movies etc when I open the addon. Have tried restoring Fire tv and even reverting back to a kodi 16.1
Any ideas how to fix this? Is it possible to revert this and if so could you please show me how?
Many thanks Swift
Hi there
Just bought my firetv yesterday from amazon - presumably firetv2. I am not too fussed about moving kodi to the sd card but would like to download to the card. Even after confirmation however, nothing is downloaded. I will try to adb shell with the path you suggested. This post was 2015, is there anything i should know that has occurred since this on the newer AFTV's or should this work as you state?
hesh
heshan said:
Hi there
Just bought my firetv yesterday from amazon - presumably firetv2. I am not too fussed about moving kodi to the sd card but would like to download to the card. Even after confirmation however, nothing is downloaded. I will try to adb shell with the path you suggested. This post was 2015, is there anything i should know that has occurred since this on the newer AFTV's or should this work as you state?
hesh
Click to expand...
Click to collapse
Im still using this for quasar to download to sd, works fine.
Sent from my ONEPLUS A3000 using Tapatalk