Database Info

[APP][2.1+] Droid NAS - SMB server for Android

Droid NAS allows you to share folders over a Wi-Fi network, making your Android device visible as a Bonjour computer in the Finder on your Mac. Turn your phone or tablet into a wireless flash drive with a single tap!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Different profiles can be used to quickly choose which folders to share. Assign your home or office Wi-Fi networks to profiles and Droid NAS will auto-select profiles on start.
Supported systems:
- Mac OS X.
- Android: apps like ES File Explorer, Solid Explorer, GTVBox Video Player.
- Windows is NOT supported because it can't connect to SMB servers via a non-standard port.
- Linux most probably also won't work.
Recent changes:
- Added password protection.

The irony... You made a server with a Windows protocol (more or less) that don't work on Windows. xD
But what's the advantage of this over a FTP server (I'm not a Network guy)
Sent from my HTC One S using xda premium

Thanks to Bonjour protocol, Android device will appears automatically in Finder and you can work with it like you work with a flash drive. E.g. you can edit a documents directly on the device.
I've seen another SMB server on this XDA, but you need a root access to use the default port. Big question to ROM developers - can Android be modified to allow ports numbers < 1000 for apps like this?

Very nice....I transfered a 14 MB file faster than I could have went and found my USB cable. KUDDOS!!! Thanks for this app.

Will try it with total commander or sth. other on windows. Thank you any way it can be much easier to access the files of galaxy nexus since it has no mass storage mode.

- Windows is NOT supported because it can't connect to SMB servers via a non-standard port.
So why dont u use the standard port?

Mardon said:
So why dont u use the standard port?
Click to expand...
Click to collapse
It's only possible for console apps in rooted devices, will be happy if there will be some way to do it.
Version 1.0.4 adds support for custom shares, e.g. external SD card.

It could be great a version for rooted device ¡¡¡ then these users ( I`m one of thems) could enjoy enterely of this app with windows pc`s Is it so difficult to add up an option for these rooted devices? Maybe requesting some help to developer could solve this issue.
Anyway , thanks for so many efforts go on with your great app.

DesertEagle said:
It's only possible for console apps in rooted devices, will be happy if there will be some way to do it.
Version 1.0.4 adds support for custom shares, e.g. external SD card.
Click to expand...
Click to collapse
Why not smb compilation for android with root rights and gui backend?
Cheers

please SMB for windows!!!!!

DesertEagle said:
It's only possible for console apps in rooted devices, will be happy if there will be some way to do it.
Version 1.0.4 adds support for custom shares, e.g. external SD card.
Click to expand...
Click to collapse
Yeah, this is correct. I am assuming you have written this entirely in Java or using something like JLAN? If so, without changes to the Android framework it is not possible without elevating to root (via su) and running processes from the command line (as root). I tried the JLAN route and it works for non-standard ports but without running the application as the root user (not feasible atm) you can't bind ports below 1024.

"custom shares" Not from what I see!
DesertEagle said:
It's only possible for console apps in rooted devices, will be happy if there will be some way to do it.
Version 1.0.4 adds support for custom shares, e.g. external SD card.
Click to expand...
Click to collapse
I fully disagree with the ability to point to other folders NOT on the SD Card. I have an SATA drive on my Android that can't even be seen by this app. I can see and use via FTP but would love to see this app bring in sharing of ALL folders linked within the unit.

When will it be possible to share ALL folders on a device? I have a ton of data on both an SATA drive and a connected USB drive. Neither can this app see.

Is not possible to introduce a "Root Mode" that opens the server in the standard port or configures a iptables local port redirect to accept windows clients?

"Connection Failed" in finder
So this is admittedly a pretty vague issue. Until now i've been able to use the app DroidNas to transfer files with my Macbook. Randomly today, when I go to my device (Verizon HTC one) in Finder, it tells me "Connection Failed" almost immediately. They're both on the same wifi network, and as far as a I can tell I haven't changed any settings that would affect the network connectivity of my phone. I tried using a clean hosts file, in case maybe adaway was causing the problem, but no dice.
Anyone have any idea what the problem is / any troubleshooting ideas?

murtaza217 said:
So this is admittedly a pretty vague issue. Until now i've been able to use the app DroidNas to transfer files with my Macbook. Randomly today, when I go to my device (Verizon HTC one) in Finder, it tells me "Connection Failed" almost immediately. They're both on the same wifi network, and as far as a I can tell I haven't changed any settings that would affect the network connectivity of my phone. I tried using a clean hosts file, in case maybe adaway was causing the problem, but no dice.
Anyone have any idea what the problem is / any troubleshooting ideas?
Click to expand...
Click to collapse
I have the same problem still unable to fix it... too bad it was a Great app...

lbrenes said:
I have the same problem still unable to fix it... too bad it was a Great app...
Click to expand...
Click to collapse
It may be the problem with OSX Mavericks. The workaround is described in the last update:
What's New
OS X Mavericks workaround:
Press Cmd+K in Finder and enter IP address AND share:
smb://IP_ADDRESSort/Share
for example:
smb://192.168.1.2:7777/SD Card
Click to expand...
Click to collapse

leleobhz said:
Is not possible to introduce a "Root Mode" that opens the server in the standard port or configures a iptables local port redirect to accept windows clients?
Click to expand...
Click to collapse
This.

leleobhz said:
Is not possible to introduce a "Root Mode" that opens the server in the standard port or configures a iptables local port redirect to accept windows clients?
Click to expand...
Click to collapse
Same here. Then it is accessible by any client.
And does it work under Kitkat ?

Help... I installed this on my android tv box. My transfer speeds is around 2-3MB/s tops. In the same network, if I was to transfer between a mac and another mac, I get 5-10MB/s at least. Also, constantly, almost when the file is finished transferring, I get an error saying something like the file cannot be read and written.
Which android box should I get next to solve this issue? I need one that I can connect a 2TB hard disk to.
Also, what's the best workaround for 10.9 machines? SMB 2 seems to break functionality. I've tried using AFP/CDIF to no success.
Thanks!

The fastest way to transfer media to the One X (esp on Linux and OSX)

hi,
I have been really frustrated with attempts to transfer media to my phone over MTP. On Ubuntu Linux - none of the methods work very well - including mtpfs, go-mtpfs, etc.
So I figured to use the method that Apple uses (tunneling TCP over USB) by way of ADB.
So I ran a ssh server on my phone (sshdroid, but anything should work), made sure that
Code:
adb devices
showed up my device, setup a port forward on my laptop using
Code:
adb forward tcp:2222 tcp:2222
, ran filezilla and connected to localhost on port 2222 and transferred all my media.
I got a 1.2 mbps transfer rate using my 2008 laptop. I am now planning to setup rsync over ssh to sync my music.
Here lies my frustration - Apple figured out the TCP over USB method almost a decade back, adb and ssh works well beautifully. Why did Google make the decision of going with MTP, as opposed to building something around SSH - which already has solved most of the problems around file transfer, mounting drives and sync.
Really frustrating.
EDIT: forgot to add that this should work for other devices like Samsung S3, Nexus 7 , etc. - but I personally have only my HOXL to test with.
- Sandeep
P.S. a longer rant on this topic here

sandys1 said:
hi,
I have been really frustrated with attempts to transfer media to my phone over MTP. On Ubuntu Linux - none of the methods work very well - including mtpfs, go-mtpfs, etc.
So I figured to use the method that Apple uses (tunneling TCP over USB) by way of ADB.
So I ran a ssh server on my phone (sshdroid, but anything should work), made sure that
Code:
adb devices
showed up my device, setup a port forward on my laptop using
Code:
adb forward tcp:2222 tcp:2222
, ran filezilla and connected to localhost on port 2222 and transferred all my media.
I got a 1.2 mbps transfer rate using my 2008 laptop. I am now planning to setup rsync over ssh to sync my music.
Here lies my frustration - Apple figured out the TCP over USB method almost a decade back, adb and ssh works well beautifully. Why did Google make the decision of going with MTP, as opposed to building something around SSH - which already has solved most of the problems around file transfer, mounting drives and sync.
Really frustrating.
EDIT: forgot to add that this should work for other devices like Samsung S3, Nexus 7 , etc. - but I personally have only my HOXL to test with.
- Sandeep
P.S. a longer rant on this topic here
Click to expand...
Click to collapse
So you are essentially frustrated with the fact that you have the flexibility to discover your own solutions and that google facilitates this by providing you both a working file transfer method but the option to do it better? Honestly, I'm not sure that I would want to carry around not only my device but a USB stick with portable versions of a FTP client/adb for linux/windows/OS X just to be able to transfer files to/from in a pinch. Most OSs will be able to deal with an MTP device and this allows google to both not need to separate the space into space for your data/apps and allows for google to use ext file systems. There was some thought put into that decision believe it or not.

I just use FTP though my file browser.

z28james said:
So you are essentially frustrated with the fact that you have the flexibility to discover your own solutions and that google facilitates this by providing you both a working file transfer method but the option to do it better? Honestly, I'm not sure that I would want to carry around not only my device but a USB stick with portable versions of a FTP client/adb for linux/windows/OS X just to be able to transfer files to/from in a pinch. Most OSs will be able to deal with an MTP device and this allows google to both not need to separate the space into space for your data/apps and allows for google to use ext file systems. There was some thought put into that decision believe it or not.
Click to expand...
Click to collapse
Actually you misunderstood what I was trying to say. I completely understand the rationale for Google wanting to do away with MSC (yes - I have read the Dan Morrill interview as well). And I'm not proposing that you carry around ADB.
what I am fundamentally asking is the rationale to choose MTP as a protocol, when a viable and far superior alternative exists. OSes are NOT able to work with MTP effectively, because it was never intended to do what we need from our devices today.
On the other hand, most OSes already work with TCP and SSH very effectively and in an extremely highly performant way. It would have been trivial for Google to build a TCP/SSH service inside the Android core and make available client services (similar to usbmux) that would have worked seamlessly across all platforms.
I am seriously questioning the choice of MTP as a protocol, because it is not too efficient.

I don't get it, why not just mount your SD and drag and drop your files? Am I missing something here?
Sent from my HTC One X using xda premium

sandys1 said:
Actually you misunderstood what I was trying to say. I completely understand the rationale for Google wanting to do away with MSC (yes - I have read the Dan Morrill interview as well). And I'm not proposing that you carry around ADB.
what I am fundamentally asking is the rationale to choose MTP as a protocol, when a viable and far superior alternative exists. OSes are NOT able to work with MTP effectively, because it was never intended to do what we need from our devices today.
On the other hand, most OSes already work with TCP and SSH very effectively and in an extremely highly performant way. It would have been trivial for Google to build a TCP/SSH service inside the Android core and make available client services (similar to usbmux) that would have worked seamlessly across all platforms.
I am seriously questioning the choice of MTP as a protocol, because it is not too efficient.
Click to expand...
Click to collapse
I hear you. You will probably have a hard time convincing windows users that MTP is broken for them.
Sent from my Nexus 7 using Tapatalk 2

z28james said:
I hear you. You will probably have a hard time convincing windows users that MTP is broken for them.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm on windows and think mtp is horrible. That's why I just use ftp now if a rom opts for mtp (JB).

qwertyaas said:
I'm on windows and think mtp is horrible. That's why I just use ftp now if a rom opts for mtp (JB).
Click to expand...
Click to collapse
Why not just mount as disk drive and get 5MB/sec file transfers? I don't get it?

beaups said:
Why not just mount as disk drive and get 5MB/sec file transfers? I don't get it?
Click to expand...
Click to collapse
The One X does not allow you to mount your internal memory as a USB drive. Correct me if I'm wrong, but the Samsung S3 (even though it has a microsd ) does not allow the same.
The only way you can access data is through the phone using a protocol called MTP - it sort of pretends to mount your phone as a USB drive, but that's not what it is actually doing.
the USB drive mode is called MSC - the reason why Google decided to move away is written here

FTP and SFTP are good - You can do exactly that using the USB as the carrier (using my method) instead of the wireless network. So what you said does not make my proposal useless.
What I wanted to show was that there is a perfectly alternative way in which you can transfer files without using the wireless network (basically using the USB as a network). I am willing to stand my ground that that allows for a far superior (and much more omnipresent) protocol to transfer files. What you use on top of TCP-over-USB is upto you : SSH, SCP, FTP - all are viable.
Secondly, I like the fact that when I'm transferring all these files, my regular wifi/3g network is unthrottled.

sandys1 said:
The One X does not allow you to mount your internal memory as a USB drive. Correct me if I'm wrong, but the Samsung S3 (even though it has a microsd ) does not allow the same.
The only way you can access data is through the phone using a protocol called MTP - it sort of pretends to mount your phone as a USB drive, but that's not what it is actually doing.
the USB drive mode is called MSC - the reason why Google decided to move away is written here
Click to expand...
Click to collapse
We all have the the One XL which does allow for our storage to be presented as a block device. The One X might be different?

z28james said:
We all have the the One XL which does allow for our storage to be presented as a block device. The One X might be different?
Click to expand...
Click to collapse
I'm assuming you are on Windows.
What you are seeing is your computer talking to the phone over MTP and presenting it as a block device. If you are able to use your phone's storage (both main as well as the "/sdcard") while you are transferring content on your phone, then it is the MTP mode.
MTP not only brings bad performance, but it also doesnt work across all platforms and screws with fundamental things like timestamps.
Phones prior to the Galaxy Nexus used the MSC mode - a true block level mounting. There are some tradeoffs to that, which is why Google gave up on that.
The iPhone talks to the iTunes using a similar protocol to what I talked about in my OP - TCP over USB.

sandys1 said:
I'm assuming you are on Windows.
What you are seeing is your computer talking to the phone over MTP and presenting it as a block device. If you are able to use your phone's storage (both main as well as the "/sdcard") while you are transferring content on your phone, then it is the MTP mode.
MTP not only brings bad performance, but it also doesnt work across all platforms and screws with fundamental things like timestamps.
Phones prior to the Galaxy Nexus used the MSC mode - a true block level mounting. There are some tradeoffs to that, which is why Google gave up on that.
The iPhone talks to the iTunes using a similar protocol to what I talked about in my OP - TCP over USB.
Click to expand...
Click to collapse
No, I'm not seeing that at all in windows. When I plug my phone into any linux box as well it is enumerated as a "sd" device. I'm also not able to use the storage as it is mounted. The One XL divides its internal SD card into useable space and space for apps.
This is why people are not able to understand why you have posted this here and why I'm asking if the Tegra 3 One X is perhaps different.
EDIT: It looks like the SGS 3 uses MTP.

It is enumerated as a sd device, but it is not mounted as one.
Please double check - I'm on an AT&T One XL.
MTP is the only access path.
Sent from my HTC One X using xda premium

sandys1 said:
It is enumerated as a sd device, but it is not mounted as one.
Please double check - I'm on an AT&T One XL.
MTP is the only access path.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I just mounted my phone's storage on my laptop running Slackware 14.
Showed up as a SCSI attached storage disk.
fdisk shows it as a block device. In my case sdc.
sdc mounted as vfat.
No fuse, no MTP.
On windows my Nexus 7 uses MTP. My One X shows up as an actual block device. The disk manager even sees it as a block device.

z28james said:
I just mounted my phone's storage on my laptop running Slackware 14.
Showed up as a SCSI attached storage disk.
fdisk shows it as a block device. In my case sdc.
sdc mounted as vfat.
No fuse, no MTP.
On windows my Nexus 7 uses MTP. My One X shows up as an actual block device. The disk manager even sees it as a block device.
Click to expand...
Click to collapse
Oh - now I see what the confusion was. The HTC spoofs the MSC mode using a partition on a single disk. Read about it here. And these are some of the problems that may occur if you continue to use it as mass storage.
I would recommend that you transfer using MTP or over the network using FTP or through my method. I'm really unsure about the mass storage path.
However, what I talked about still stands - Google has moved away from mass storage completely and switched to MTP (HTC is doing a few tricks to make this easy for us)
MTP sucks.

One word: AirDroid.
Why even bother physically connecting your phone to USB anymore when you can use apps such as AirDroid (and many other apps) to get great speeds wirelessly regardless of platform? All you need is the App installed and any browser.

sandys1 said:
Oh - now I see what the confusion was. The HTC spoofs the MSC mode using a partition on a single disk. Read about it here. And these are some of the problems that may occur if you continue to use it as mass storage.
I would recommend that you transfer using MTP or over the network using FTP or through my method. I'm really unsure about the mass storage path.
However, what I talked about still stands - Google has moved away from mass storage completely and switched to MTP (HTC is doing a few tricks to make this easy for us)
MTP sucks.
Click to expand...
Click to collapse
Why can you not just accept the fact that htc includes an excellent usb interface. It's fast and stable in "disk drive" mode. Whether it's "spoofed", "faked" or whatever you want to call it, it works great, and across all platforms.
Actually I don't think it's spoofed at all considering I can write to it in direct disk access mode in WinHex.
Anyhow, they actually did quite a bit with the usb stack. USB tethering, USB network pass-through, and Disk-Drive mode are all HTC features that I sorely miss on my MTP SGS3.
I have not seen a single user complain about Disk Drive mode. It works great.
Nothing to see here, move along....

I hate mtp and miss mass storage mode from the hox

You can.
We can't. Truly.
This thread is for all of those users like me on Linux or OSX who are having trouble with transferring content.
I wouldn't have made this thread if it didn't affect us.
Sent from my HTC One X using xda premium

Linux on Shield

I would like to know some things about the Linux on the Shield.
1) I've heard in December of the Last Year it didn't support wifi, bluetooth and SD Cards. What is their current status now?
2) Does it supports USB Devices, like Keyboard, Mouse, Ethernet Adapter (I REALLY hope i don't need this), Printer and USB HUB?
3) Is there some kind of Driver for the Tegra 4 on the Linux?
4) How do i install Linux on the Shield?
5) Is there some way to dual boot it with Android?

Hi,
MADCastro said:
1) I've heard in December of the Last Year it didn't support wifi, bluetooth and SD Cards. What is their current status now?
Click to expand...
Click to collapse
Good news - Wifi and SD cards are now working (well, most SD cards at least) on my roth_next branch: https://github.com/linux-shield/kernel/tree/roth_next Bluetooth is still out of luck for now.
MADCastro said:
2) Does it supports USB Devices, like Keyboard, Mouse, Ethernet Adapter (I REALLY hope i don't need this), Printer and USB HUB?
Click to expand...
Click to collapse
All USB devices supported by Linux should be working with SHIELD, as long as the kernel driver for them is compiled. I have played with a keyboard, mouse, network adapter and mass storage device, all connected to a hub.
MADCastro said:
3) Is there some kind of Driver for the Tegra 4 on the Linux?
Click to expand...
Click to collapse
Not sure what you mean - Tegra 4 is supported in Linux mainline, and some of its devices as well.
MADCastro said:
4) How do i install Linux on the Shield?
Click to expand...
Click to collapse
It's a quite manual process at the moment. You might want to consider what your end goal is, and whether it is worth the trouble, knowing that there is no graphic acceleration, no way to sleep, and so on. If you really want to give it a try (it implies cross-compiling the kernel, playing with fastboot, and extracting user-spaces to SD cards), let me know and I will try to come with a documentation sometime soon.
MADCastro said:
5) Is there some way to dual boot it with Android?
Click to expand...
Click to collapse
Sort of. You can store the Linux user-space on a SD card, or even in a file on your Android data partition that will be mounted as a root loopback device.
The problem is that SHIELD's bootloader only supports booting via two means:
- Whatever kernel is on the BOOT partition
- Whatever boot image is given to it using the fastboot boot command.
This means that you can either keep the Android boot image on the BOOT partition and boot Linux using "fastboot boot" while your SHIELD is connected to your PC via USB, or the other way around. But if you want to switch the system to boot, you will need to connect your SHIELD to your PC and play with fastboot.
Let me know if this answers your questions and if you need more information. What you can do with Linux on SHIELD is still limited ; but it's a fun way to get involved in kernel hacking since many missing drivers can easily be written and general support can also be improved.

"Good news - Wifi and SD cards are now working (well, most SD cards at least) on my roth_next branch: https://github.com/linux-shield/kernel/tree/roth_next Bluetooth is still out of luck for now."
Nice! No need of a ethernet adapter.
"All USB devices supported by Linux should be working with SHIELD, as long as the kernel driver for them is compiled. I have played with a keyboard, mouse, network adapter and mass storage device, all connected to a hub."
Nice. Does there is HPLIP for ARM devices?
"Not sure what you mean - Tegra 4 is supported in Linux mainline, and some of its devices as well."
I mean 3D drivers. Which would allow specific apps to run fine.
"It's a quite manual process at the moment. You might want to consider what your end goal is, and whether it is worth the trouble, knowing that there is no graphic acceleration, no way to sleep, and so on. If you really want to give it a try (it implies cross-compiling the kernel, playing with fastboot, and extracting user-spaces to SD cards), let me know and I will try to come with a documentation sometime soon."
I want to use it as an office OS for doing things that Android can't as my desktop is dead.
"Sort of. You can store the Linux user-space on a SD card, or even in a file on your Android data partition that will be mounted as a root loopback device.
The problem is that SHIELD's bootloader only supports booting via two means:
- Whatever kernel is on the BOOT partition
- Whatever boot image is given to it using the fastboot boot command.
This means that you can either keep the Android boot image on the BOOT partition and boot Linux using "fastboot boot" while your SHIELD is connected to your PC via USB, or the other way around. But if you want to switch the system to boot, you will need to connect your SHIELD to your PC and play with fastboot.
Let me know if this answers your questions and if you need more information. What you can do with Linux on SHIELD is still limited ; but it's a fun way to get involved in kernel hacking since many missing drivers can easily be written and general support can also be improved."
So i still need a Desktop for boot it? :/
Sent from my GT-S7562L using XDA Free mobile app

If you just want to use your SHIELD as an office device, your needs may be better served by one of the many "Linux on Android" apps, e.g:
https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid
This will allow you to run a Linux desktop alongside with Android, without rebooting, without recompiling kernels, and without requiring a desktop PC.
Graphics will be slow as death, but that should be enough for LibreOffice & pals.
Network will work using the Android stack, USB devices such as keyboards and mouse should work fine too.

Jetson TK1 Development Pack
Have either of you looked at the Jetson TK1 Development Pack and the Linux4Android drive image that comes along with it? Its based off of Ubuntu 14.04 - and i believe has acceleration - so if it were to be flashed, it 'should' work - since its meant to work on the TK1 dev kit - no garuntees though

Can we please get a documentation writeup?
Very interested in your development process. I'm a new developer, and this is my main device.

[GUIDE] [POGOPLUG] $20 Cheaper than Pi NAS

Problem:
I wanted a NAS server (with data redundancy) at my house without having to run a whole PC. I bought a Pogoplug Series 4 (<$20 on amazon.com), set it up, and moved everything. In the process, I found that the pogoplug (with its default firmware) did not play well with moving my pictures from my phone to the device, and I lost about a year's worth of memories. I looked to the raspberry pi. simple enough, but needed an additional USB hub (under powered and not enough USB ports), and the video output was unnecessary (as I would setting it up as a headless server). So, while playing with the pi, I looked back to my dusty Pogoplug.
Solution:
Hack the pogoplug to operate just as I would have with the raspberry pi. You can install the OS on an SD card now (thanks to the Devs for that), it has two USB 3.0 ports (which is not necessary since this particular model only has an 800Mhz processor), an additional port on top with a hard drive dock (which I wont use often), and you will only see one power cord, and the cords going to the drives, taking up about a "Rubik's Cube" worth of space (OK, a little more, but not much).
Pros: 3 powered USB ports (2 x USB3.0, 1 x USB2.0), small form factor, OS on SD card, Low power consumption
Cons: 800 Mhz Arm processor (though, the rPi is only 700 Mhz), which is the transfer speed bottleneck. Fast enough for me though, and most home use scenarios. Also, no video output, but thats actually a for my scenario. SSH only.
Materials:
1: Pogoplug Series 4 - Don't pay more than $20
2: 2 x External Hard Drives - I bought two new 1TB USB 3.0 portable drives to replace my two old 1TB clunky ones.
3: SD card - I recommend 8GB or larger. I personally used a 16GB microSD w/ adapter because it's just what I had laying around from an old cell phone.
4) Optional - Wireless LAN Adapter - I recomend the EDIMAX EW7811Un because it fits under the cover when used on the top USB2.0 port, it uses the RTL8188CUS chipset, and it's ridiculously cheap. You'll have to load the realtek firmware to get it to work on pogoplug (apt-get update && install firmware-realtek).
Instructions:
1: The following instructions were copied from the following site (Hack the Pogoplug (v4/debian)). I figured it would help to have the info all in one place. This is an excellent tutorial for hacking the Pogoplug Series 4. Very easy to follow.
2: Optional - Install wireless adapter and connect via WiFi (I did this so I wasn't tethered to a router)
3: Setup Rsync via SSH - Since you will be running as the root user, you will omit the "sudo " from your commands. Be sure that when you enter "apt-get install rsync", you replace it with "apt-get install rsync cron" if you do not, then "crontab -e" will not work.
4: Optional - Install DLNA client to stream to game console, chromecast, etc (I used miniDLNA, seems to work pretty good.)
Final Product:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thoughts:
1: I tried following this link to install lsyncd for using with the Pogoplug. It worked, but I didnt want to accidently delete a file and have it delete instantly from the backup. So I just stick with RSYNC.
2: Now that I see the Pogoplug Pro has two 800 Mhz processors, I may research this same type of setup on that device. But I do like having the OS on an SD card. I would have to use a USB flash drive if I switched. I had already committed to the Pogoplug Series 4.
3: I understand that the costs incurred total over $20 when you factor in the SD card, External Hard Drives, and optional wireless adapter. This is simply a comparison to the "$35 Raspberry Pi NAS" reference. It is assumed that you likely already have hard drives that you currently save your info to, and likely some sort of SD card laying around. Also keep in mind, the Pogoplug already has a case for the circuit board.
Update 2014-11-12 - Do not use wicd-curses:
After some time with this Pogoplug, I ran into and issue where the Pogoplug freezes through simple tasks. It seems to be that I have reached the limit of the RAM memory. I tried adding SWAP, but the system doesn't seem to utilize it when activated. I believe it may be linked to my wireless application (wicd-curses). I uninstalled wicd-curses, using a LAN connection, and everything seems to work fine. My swap is even behaving properly. Now I just need to figure out how to get wifi to work properly with my configuration.
Credits and Thanks go out to:
Qui Hong, How-To Geek, and Ben Perove.

Thank you for posting this. I never would have found the qnology blog otherwise. I still need to get some hard drives to complete my setup, but I've got my Pogo all set.
To anyone wondering, arch is actually much easier to use on the pogo than Debian (IMHO), and the qnology blog includes both sets of inductions, so you can chose which you follow.

iXNyNe said:
Thank you for posting this. I never would have found the qnology blog otherwise. I still need to get some hard drives to complete my setup, but I've got my Pogo all set.
To anyone wondering, arch is actually much easier to use on the pogo than Debian (IMHO), and the qnology blog includes both sets of inductions, so you can chose which you follow.
Click to expand...
Click to collapse
As a follow up; I ended up switching to Debian because arch just isn't as stable in my experience. Pacman is definitely simpler and easier than apt (and I have used Ubuntu for many years). Systemd is way better than init.d, so I upgraded to Debian Jessie. Systemd on wheezy didn't seem as well put together as it is on Jessie.
Anyway good luck all.

Debian is definitely a better choice considering the huge variety of packages

Thanks.
Great guide.:good:

Thanks for the write up. I'm not sure if anyone will notice this post but I'll try anyways.
What kind of speeds are you getting with the Pogoplug NAS? According to this article (http://www.storagereview.com/pogoplug_series_4_review) the default pogo plug has a disadvantage of a transfer speed of 45 MB/s. Honestly that would be an amazing improvement as right now I'm getting about 3.5 MB/s with the pogo plug running Debian and Samba. This is on wireless or wired network.
Are there any way to improve speeds?

Guitarman19853 said:
Thanks for the write up. I'm not sure if anyone will notice this post but I'll try anyways.
What kind of speeds are you getting with the Pogoplug NAS? According to this article (http://www.storagereview.com/pogoplug_series_4_review) the default pogo plug has a disadvantage of a transfer speed of 45 MB/s. Honestly that would be an amazing improvement as right now I'm getting about 3.5 MB/s with the pogo plug running Debian and Samba. This is on wireless or wired network.
Are there any way to improve speeds?
Click to expand...
Click to collapse
The performance I got was abysmal. 45 MB/s would be surprising. I like playing around with the pogo, it's a great little headless project piece of equipment, but I can't get justifiable speeds for production use.
It worked better as a web server then a NAS.
Sent from my XT1060 using Tapatalk

Im thinking about doing this with a pogoplug V2 but had a question. Do the HDDs go to sleep after some time and wake up when needed or are they constantly on?

If you are running debian you can use hd-idle to send your hdds to sleep. It works well and is easy to configure
Sent from my Nexus 5 using Tapatalk

[PORT] [CALCULATOR] - Android on the TI nSpire CX

Android running on the TI nSpire CX Graphing Calculator
About:
The nSpire CX is a color-screen graphing calculator produced my Texas Instruments powered by an 150Mhz ARM-based SoC and 64MB of RAM. Unlike previous calculator models from TI, users, by default, are unable to create native homebrew applications for the device. Luckily, however, the TI community found a way to "jailbreak" the nSpire CX and CX CAS, allowing third-party developers to create apps for their calculators. One of the most notable community contributions, started by tangrs, was a port of Linux to the device, giving users and tinkerers full access to GNU userspace. This is my attempt to contribute back to the community, by porting Android userspace to the nSpire CX and CX CAS model calculators.
TL;DR
You can now run Android on a graphing calculator
Why?
Nowadays. there seems to be a misconception that Android can only run on fast smartphones. The latest Android release at the time of writing is Lollipop, a release Google claims can run on smartphones "with as little as 512MB of ram." Certainly a good start, But I was convinced *some* version of Android could run on *extremely* low end hardware. So, after a bit of searching, I found the best suitable Android release to run on the lowest-end Linux capable hardware I could think of: my calculator. That release is the obsolete, but venerable, Android Donut (1.6). After a bit of porting work, I managed to get a full Android stack up and running on my calculator and slowly began to iron out the major bugs. I've been playing with it for a while now and figured it was finally *decent* enough to release to the general public. However, it should be noted that a lot of functionality is still missing, partially due to bugs, and partially due to the age of Android 1.6. However, I do believe it has exceeded it's goal as a PoC port to help me learn more about what is involved porting Android to legacy hardware. As it turns out, it's even rather usable.
Status:
* Working:
Android Core
Most Android 1.6 Apps
Terminal Emulator
Keyboard
* Buggy:
Wifi (warning, extremely broken and may kill your cat. External dongle needed)
Bluetooth (Not actually sure whether this works or not as I don't have a BT dongle)
USB
* Not Working:
Touchpad (Using the touchpad dtb seems to break a lot of stuff like PMIC, so I disabled it _for now_)
Battery Status (Status is emulated using test_battery kernel driver)
FAQ:
* Q: Why are you using 1.6?! That's like, really old!
A: Android 1.6 was the only feasible version of Android version I could run with an 150Mhz ARM processor and less than 64MB of usable RAM
* Q: What do I need to run android on my nSpire CX (CAS)?
A: The bare minimum is (1) Calculator running OS 3.9 or less and (1) Mini-USB-OTG cable
* Q: What's the point of this?
A: I have no idea, but it sure makes me laugh when I think about it
* Q: Will this help students cheat by putting this on their calculator?
A: I very much doubt it
* Q: Can you run a calculator emulator on Android on the Calculator?!?!
A: Yes, yes you can
* How's performance?
A: Surprisingly, pretty decent, considering... I can even play some 2D games on it
* Can you port Android to *my* calculator? It's a (insert calculator using a z80 here)
A: No
* Will this. Run Crysis?
A: Good luck
* Where's the sources?
A: See the bottom of this post.
Installing nDroid on your calculator:
Prerequisites:
1) USB thumb drive, 1GB or greater
1) TI nSpire CX or CX CAS running OS 3.9 (Important! [It seems OS 3.6 breaks it, I'm using v3.9.1.38] (Thanks ViiperzRecon))
1) USB-OTG cable that fits the nSpire CX (mini-usb to host-usb)
Recommended) A powered USB hub (Without it your calculator might not have enough power to write to the USB drive and CRASH)
1) Computer running Linux or BSD
Step 1: Jailbreak your calculator
I won't explain how to do this are there are already an abundance of articles on how to do this. Take a look at http://ndless.me for details.
Step 2: Format the USB drive correctly
(It should already be known that doing this will destroy any and all data on the thumb drive)
Open up the partitioner of your choice (my favorite is gparted), and create the following partitions as described:
Partition 1: (System partition) ext4 (> 100MB recommended)
Partition 2: (Userdata partition) ext4 (> 500MB recommended)
Partition 3 (optional): (Cache partition) ext4 (> 50MB recommended)
Partition 4 (optional): (SD card partition) FAT (> 100MB recommended)
Example image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3: Download files
Boot.img.tns [LINK]
System.tar.gz [LINK]
nspire-cx.dtb.tns [LINK]
nDroidLoader.tns [LINK]
startndroid.ll2.tns [LINK]
Step 4: Install TiLP and create directories
You should have already installed this when jailbreaking your calculator in step 1, if not, install it now if you're using Linux, or use the TI software if you're using Windows now.
When you launch TiLP, connect your calculator and create a directory called "Android". Copy over nspire-cx.tns, Boot.img.tns, nDroidLoad.tns, and startndroid.ll2.tns. After that, download ndless.cfg.tns in ndless/, open it with a text editor, and add the following line:
ext.ll2=ndroidloader
Step 5: Extract system to USB drive
Now that the USB drive has been partitioned, mount the first partition somewhere on your computer and place System.tar.gz in the root directory of said partition. Open up a terminal in that location and type:
sudo tar -xpf System.tar.gz
rm System.tar.gz
After that, you should have some shiny new files and directories on your USB drive!
Step 6: Starting it up
After the files have synced to the USB drive, remove it and place it in the USB-OTG cable. When that's done, plug the small end of the cord into the top of the nSpire CX. Open "documents" on the device, click on the Android folder, and then click on startndroid.ll2.tns. A window should appear and shortly after you should see a framebuffer console. Congratulations, you should now be running Android on your nSpire!
Step 7: Boot up and finish
After about 10 minutes or so (boot ups are shorter on subsequent launches), you should be greeted with the stock 1.6 launcher. Feel free to hack away on your new Android-powered calculator. [NOTE: Until the touchpad is working, the "/" button is up, the "x^2" button is down, the "e^x" button is left, the "10^x button is right, "menu" is menu, "doc" is home, "esc" is back, and "save" is power].
Video:
Unofficial Reddit thread:
https://www.reddit.com/r/Android/comments/3awptt
XDA:DevDB Information
nDroid, ROM for all devices (see above for details)
Contributors
joshumax
Source Code: https://github.com/nDroidProject
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Testing
Current Beta Version: nDroid-1.6
Created 2015-06-26
Last Updated 2015-12-02

I was surprised when I saw Linux on this thing. (Okay Doom was impressive too.) But Android! This is amazing! I hope you get the touchpad working, then this will be even more amazing than it already is. Thank you for making this! Keep up the good work.

something similar on a Nook Simple Touch?
I know very little about programing but am good with hardware, any chance your skills could be applicable to getting a NST running android (well)
I currently have 2 and find them great for unobtrusive access to data, but as it sits it only is selectively usable.
A killer app for me would be the ability to be able to use it for live navigation (with a standard android app) think hiking, or dash mounted on a motorcycle.
So far I rooted it (several times) and have been able to get individual pieces to work following USB otg, fast refresh, various stand alone functions, but it never works together.
wish list'
OTG+fast refresh option working seamlessly
bluetooth somehow without OTG
a root option with pre-installed play store, USB OTG, fast refresh, and and usual option i'm forgetting
any help would be appreciated

overclocking?
Since it is possible to overclock your ti-nspire cx/cas, do you think it would be possible to run higher versions of android on it?

strubelz said:
Since it is possible to overclock your ti-nspire cx/cas, do you think it would be possible to run higher versions of android on it?
Click to expand...
Click to collapse
The constraint really isn't the clock speed, but instead how little RAM it has. No matter how high you overclock it, whether it's 300 Mhz or 3000 Mhz, it will still only have ~60MB of usable memory. While I _might_ be able to get Eclair running, I doubt I'd be able to get something like KitKat or Lollipop running on it in any usable state.

Awesome! Great work
Plus it's running 4.0 Kernel!

Holy ****! I am testing this right now!

Henriquefeira said:
Holy ****! I am testing this right now!
Click to expand...
Click to collapse
Great! Let me know if you run into any major bugs while running it!

Henriquefeira said:
Holy ****! I am testing this right now!
Click to expand...
Click to collapse
joshumax said:
Great! Let me know if you run into any major bugs while running it!
Click to expand...
Click to collapse
Some bugs: random reboots, a bit of lag, sistem ui crashing and just stoped working on my calculator so any advice in reinstalling the original firmware?

Henriquefeira said:
Some bugs: random reboots, a bit of lag, sistem ui crashing and just stoped working on my calculator so any advice in reinstalling the original firmware?
Click to expand...
Click to collapse
Can you write logcat data to a file and upload it somewhere before it reboots? Also, nDroid shouldn't have done anything to the original firmware and should go away after a reboot or reset button press...can you specify exactly what happened to the calculator firmware after loading nDroid?

joshumax said:
Can you write logcat data to a file and upload it somewhere before it reboots? Also, nDroid shouldn't have done anything to the original firmware and should go away after a reboot or reset button press...can you specify exactly what happened to the calculator firmware after loading nDroid?
Click to expand...
Click to collapse
Sorry for the delayed answer, but now it okay

Doesn't seem to work, throws errors like some error -110 and keeps saying it can't enumerate the USB device.

gnmmarechal said:
Doesn't seem to work, throws errors like some error -110 and keeps saying it can't enumerate the USB device.
Click to expand...
Click to collapse
Can you please attach a dump of the kernel log and/or a screenshot of the boot process up to this point?

joshumax said:
Can you please attach a dump of the kernel log and/or a screenshot of the boot process up to this point?
Click to expand...
Click to collapse
I've formatted my drive since then, but I'll try again and record it.

Well... it seems now that I got another Mini USB OTG adapter, it still doesn't work. I'm on a 3.1 CX right now. I'll try on my 4.2 as well... Last time it didn't work, and I've since then updated it from 3.9 to 4.2... Here's hoping it works somehow.
On 3.1, it goes Kernel Panic - not syncing: VFS:Unable to mount root fs on unknown-block(1,0)
4.2 goes Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b
The 3.1 one is dualbooting 3.1 and 3.1 CAS. It's a model D, by the way. The other is a more recent model T, with 4.2 and Ndless.

Could this Work in OS 4.5?
Could the nDroid loader work on Nspire OS 4.5?

pattex16 said:
Could the nDroid loader work on Nspire OS 4.5?
Click to expand...
Click to collapse
Yes, it works fine on 4.5 (I tested -- or, currently am testing it myself). Though, if you press any button other than "esc" or "enter", the launcher crashes. Maybe it's fixable with a reboot.
Also, why would you bump a two year old thread?

@joshumax
I know this is a very old thread, but can you go back to this project one more time. A swap partition would fix everything, just like how it does on the HTC HD2. Sure it will be slow, but it would result in way better compatibility with apps. 192MB should be enough.
Also, is the official wireless adapter good enough for wifi, as buggy as it may be? Can it, at least, show the Google homepage?
The touchpad with mouse compatibility would be quite nice, but d-pad only is good enough too.
Like, if you have time or want to do this, it would be srsly more than appreciated by the whole community.
Overclocking, especially around 300MHz (maybe on Android is a bit more stable than on the Nspire OS) would help a lot. And the AHB overclocked too.
Instead of using an USB stick, a tiny SD Card adapter would probably work just fine, especially if the SD is rated as (10)U1. Why? Because it would slot quite nicely on the hole of the Wifi Adapter. It would look like it was intended to be like that. I know the SD speed will be slowed down by the USB speed, but it doesn't hurt to have a faster SD anyway.
Android 9 GO would be really cool to see running on this.

Myrmeko said:
@joshumax
I know this is a very old thread, but can you go back to this project one more time. A swap partition would fix everything, just like how it does on the HTC HD2. Sure it will be slow, but it would result in way better compatibility with apps. 192MB should be enough.
Also, is the official wireless adapter good enough for wifi, as buggy as it may be? Can it, at least, show the Google homepage?
The touchpad with mouse compatibility would be quite nice, but d-pad only is good enough too.
Like, if you have time or want to do this, it would be srsly more than appreciated by the whole community.
Overclocking, especially around 300MHz (maybe on Android is a bit more stable than on the Nspire OS) would help a lot. And the AHB overclocked too.
Instead of using an USB stick, a tiny SD Card adapter would probably work just fine, especially if the SD is rated as (10)U1. Why? Because it would slot quite nicely on the hole of the Wifi Adapter. It would look like it was intended to be like that. I know the SD speed will be slowed down by the USB speed, but it doesn't hurt to have a faster SD anyway.
Android 9 GO would be really cool to see running on this.
Click to expand...
Click to collapse
Joshumax hasn't been online on XDA since 2016.
It's very unlikely the official wireless adapter is ever going to work with Linux on the Nspire, much less Android, as it would require difficult amounts of reverse engineering and drivers written from the ground up. I'm not even sure it has the potential to work as a traditional wireless adapter at all.
Overclocking your calculator to 300MHz is probably going to kill it; I think around 196MHz is the highest "safe" overclock value. The stability of overclocking isn't dependant on the software, it's dependant on the hardware; overclocking using Android instead of the TI-Nspire OS wouldn't make a difference.
Using an SD card instead of a USB drive wouldn't be faster, as the miniUSB port on the Nspire is limited to USB 1.1 speeds, if I recall correctly.
The minimum RAM requirement from Android GO was 512MB, last I checked. This is quite a bit higher than the TI-Nspire CX's 64MB, and I doubt it would run well on a 132MHz (or 196MHz) processor. Does Android still even support ARM9 CPUs?

What can it run?
Hi,
Which android apps it can't run?
Can it run all the built-in apps?
Can I download apk files?
Thank you a lot.