Related
Using these instructions you will be able to run your phone as an X11 client.
Terminology:
X Server: An X "server" is the display server. It shows the screen that you would see on a remote client.
Basically, this will allow you to run applications on your phone and use your computer monitor and keyboard as the screen/input. This is very useful if you do any development on your phone.
Install Debian on your phone. http://forum.xda-developers.com/forumdisplay.php?f=448
Install Xming Mesa and Xming Portable Putty. http://www.straightrunning.com/XmingNotes/
Start up xming.
Install openssh-server on your phone under Debian: "apt-get install openssh-server".
Set up a Putty connection to your phone. Make sure you have X11 forwarding enabled. Save the settings.
On your phone enable X11Forwarding in your /etc/ssh/sshd_config
Restart your SSH server: "/etc/initd/ssh restart"
Disconnect from Putty and reconnect to your phone with the saved settings.
X should now be working.
I've attached an image of me running emacs, xclock, and xterm on my phone.
That's really neat, though it almost seems like a waste. I mean is there really enough space to get full gtk/qt enviroment? Wouldn't it make more sense to just use screen and vim, or in your case emacs? Though perhaps my thinking is to limited, I guess things accomplished here would translate over to the next android phone. Anyways, I likey. Keep up the work, it is appreciated.
dissonance said:
That's really neat, though it almost seems like a waste. I mean is there really enough space to get full gtk/qt enviroment? Wouldn't it make more sense to just use screen and vim, or in your case emacs? Though perhaps my thinking is to limited, I guess things accomplished here would translate over to the next android phone. Anyways, I likey. Keep up the work, it is appreciated.
Click to expand...
Click to collapse
I have a 16GB sd card. There is plenty of space.
Depending on the speed of the phone, i'd do it. I know ts limited to 300 something mhz if the full 500 was used itd make a good server of some kind. saw a g1 for £185 as much as a small linux pc and it could use 3g as a backup internet connection or something. either way its a great proof of concept. ill try it out when i get home!
Please confirm i uderstand right. This is method to run X applications on phone but viewing their GUI on PC? Right?
hmepas said:
Please confirm i uderstand right. This is method to run X applications on phone but viewing their GUI on PC? Right?
Click to expand...
Click to collapse
That's correct
So it's helpful if you are on a computer with adb and the USB driver for Android installed but you want to use X apps on it, but its not helpful for using X apps directly on your phone and being able to use them on the go...
native android xserver using opengl / gles ?
What about running an XServer on the device, do you know about some opengl / gles X server that can be ported to NDK ? any other tracks are welcome too
Regards
Connected the Xoom 2, to a windows 7 machine.
Insists on letting installing 'Motocast' which I let it...what a complete pile of shi*.
I want to 'sync' a 700MB .avi video, over usb cable, to the device...estimated time? 30 minutes!!! I swear this complete toss of software is insisting to re-encode the entire file to some bullsh*t format of their choice. Is there an option to turn this off and transfer it natively?
Secondly, thankfully, it also installs native 'portable' device drivers, allowing Windows 7 file explorer to browse the device. Great, so I copy the same .avi file and paste it to the device...'Do you want to copy xyz.avi? Your device might not be able to play this file' I am prompted...'yes' I click. Just as it finishes copying (after about 4 minutes...much better) it bombs out, notifying me that because the device cannot play this file it is cancelling the transfer...wtf?!?!
The only interim solution i've found is renaming the extension '.avi' to something like '.proprietrysoftwarecansuckmyballs', copying it, then renaming it back to '.avi' once transfer has completed solves this.
So can anyone offer any 'clean' solutions to my file transfer woes? If theres no improvement, this device will be getting returned next week, which is a shame as the tablet is a great bit of kit, its just a shame the software blows.
Look for "Wi-Fi File Explorer" in the market.
This looks like it only transfers over wifi?
I need to transfer over usb cable.
Had this problem myself, looks like it doesn't come with the drivers. After a bit of searching, I found that the standard driver package works:
http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.53_Driver_5.2.0.exe
Installed that, unplug the USB cable and put it back in - should work fine!
tr00st said:
Had this problem myself, looks like it doesn't come with the drivers. After a bit of searching, I found that the standard driver package works:
http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.53_Driver_5.2.0.exe
Installed that, unplug the USB cable and put it back in - should work fine!
Click to expand...
Click to collapse
Hey thanks man, that worked a treat.
Just for clarification, does you still prompt you that the device may not support playback of the file, but then successfully transfer it (whereby it would previously error at the last second)?
No idea - haven't had that particular part of the issue myself - the main thing I had was the slowness...
I am a linux user ... i will only have the option to upload files via wifi network ?
I have a Xoom 2 ME and the only way to copy a large movie file to the device was adb.
adb push foo.txt /sdcard/foo.txt
Click to expand...
Click to collapse
That's the only usb-way i come up with. I'am on snow leopard and Google's Android File Copy tool does not work.
elster said:
I have a Xoom 2 ME and the only way to copy a large movie file to the device was adb.
That's the only usb-way i come up with. I'am on snow leopard and Google's Android File Copy tool does not work.
Click to expand...
Click to collapse
I guess the same way will work to linux too . Xoom2 has only one partition on the disk ? that the reason not to be able to mount it as a normal usb ? If you root the device is the anyway to great a small 2 Gb for ex partition to use it for easy transfer ?
Off topic about xoom 2 ME . How good the screen and and the battery life are ?
Useless tablet ?
In fact it's worst!
As a Linux User I hoped being able to use MTP... But I tried mtpfs and mtp-tools on several distributions without any luck.
But what is worse is that FTP server applications won't work too! I tried SwiFTP, FTPServer, and some other: the servers are not reachable. It appears that not even a single ping can reach the tablet. I think Motorala have put some kind of firewall in it (maybe it has something to do with the netflix HD certification?).
For me this tablet is actually useless. If I can't find a way to transfer some files on it without using MotoCast today or tomorrow, I will bring it back to the supplier...
OldBeurt said:
In fact it's worst!
As a Linux User I hoped being able to use MTP... But I tried mtpfs and mtp-tools on several distributions without any luck.
But what is worse is that FTP server applications won't work too! I tried SwiFTP, FTPServer, and some other: the servers are not reachable. It appears that not even a single ping can reach the tablet. I think Motorala have put some kind of firewall in it (maybe it has something to do with the netflix HD certification?).
For me this tablet is actually useless. If I can't find a way to transfer some files on it without using MotoCast today or tomorrow, I will bring it back to the supplier...
Click to expand...
Click to collapse
You probably hit it on the head about the Netflix certification. I would think about returning it, man.
a solution ?
Thanks to a French forum (frandroid, in the Xoom 2 topic... sorry I can't send links here), I tested a solution to the transfer problem: It is possible to use (on the computer) a server to share the files such as a samba server.
It works fine. But it's not as easy to browse, select, copy and paste file with explorers on the tablet than it is on computers (several windows, keyboard shortcuts such as Ctrl-c/v, and so on).
But it's now possible to exchange files with the Xoom 2ME without going through a cloud or using Windows/motoCast.
mdcykkk9 said:
Off topic about xoom 2 ME . How good the screen and and the battery life are ?
Click to expand...
Click to collapse
Sorry for answering so late.
The screen is quite good.
The battery life is terrible compared to my ipad2. Charging needs a lot of time and is very slow. I guess it's because of mini usb only.
Currently i'am using the device as a Kindle Fire replacement, because off the lightweight (KF is heavier and bulky). The books i usually read have more weight than the device itself.
I like it for that.
But i may not be a good adviser because my device is a prototype. It is not smooth and the speakers are terrible.
I think 8,2" is the perfect size for me. The weight is so much better than any other tablet i had.
OldBeurt said:
In fact it's worst!
As a Linux User I hoped being able to use MTP... But I tried mtpfs and mtp-tools on several distributions without any luck.
But what is worse is that FTP server applications won't work too! I tried SwiFTP, FTPServer, and some other: the servers are not reachable. It appears that not even a single ping can reach the tablet. I think Motorala have put some kind of firewall in it (maybe it has something to do with the netflix HD certification?).
For me this tablet is actually useless. If I can't find a way to transfer some files on it without using MotoCast today or tomorrow, I will bring it back to the supplier...
Click to expand...
Click to collapse
Try using a terminal on the Xoom 2 and ping the computer you're trying to connect to, while pinging your Xoom 2 from that computer at the same time. It's like you have to force them to see each other before they can start connecting in future.
I used fileexpert to see and download files with smb shared folder on Ubuntu Linux without a problem.
Sent from my XOOM 2 ME using Tapatalk
Must try for Android Addicts
Managing your Android phone or tablet does not mean that you have to establish a physical connection – providing you have a copy of AirDroid installed. With this app in place on your Android device, all you then need is a web browser; it does not matter which web browser you use or whether you are running OS X, Linux or Windows. Launch the app and you will be provided with both a URL and an IP address that you can use to establish a remote connection along with a pass code for security.
Once this has been entered you’ll be presented with a virtual desktop for your device. This is not an emulator, so you will not be working with a representation of your phone or tablet, but you will be able to browse through its contents and even make use of various features. You can quickly see how much space you have left available both on internal storage and your memory card and you can see how this space is taken up by different types of file.
There is a great file browser that can be used to view the contents of your device, but also enables you download files to your computer or upload them to your phone or tablet. Drag and drop support is a great feature and you can also install and uninstall apps with ease, including setting up batch operations to help get things completed more quickly.
Other great features include a shared clipboard that can be used to copy and paste text between computer and Android. You can also view your call logs, control your ringtone settings and control your music from your computer. If your device is rooted, you have a handy screenshot tool on your hands, but there’s plenty to keep you busy even if you haven’t take this step.
Verdict:
A superb way of managing your Android device and transferring files in both directions.
PlayStore Link: http://goo.gl/zr3XP
Credits: Mark Wilson
AirDroid remove ApMobile?
alejandromsa said:
Must try for Android Addicts
I have AirDroid and ApMobile on a Galaxy Note GT-N7000. The N7000 is unlocked and has Android vers 4.0.4. AirDroid says it can 'remove' ApMobile but this is contrary to other links.
Is it safe to do this, please? Thanks for help.
roj
Click to expand...
Click to collapse
useful utility if you have android tv device
i've android device which connects to TV and this app is very helpul for transfering files which i can view on my tv now.
No other words than AWESOME APP
unubtanium said:
No other words than AWESOME APP
Click to expand...
Click to collapse
+ 1
It's life, simplified!!
Been using this for well over a year
p51d007 said:
Been using this for well over a year
Click to expand...
Click to collapse
Just wondering if there are many vulnerabilities though. Lots of app permissions that might not be necessary..
I used it since a year now, very useful app, writing sms with a keyboard ^^
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
Not sure if I'm posting in the correct channel, if not, just let me know the right place to ask. Thank you.
I have an HP 11 Stream (ah117wm) laptop which has an embedded HD (32GB) and a Realtek wifi/BT m.2 card (rtl8822be); to which I installed Bliss OS 14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cross-hd.iso.
As expected, the majority of things work fine, aside from the Wi-Fi/BT (can't enable either) as it seems no drivers are loaded for the hardware. I'm familiar with rooting phones and using Linux, but I'm new to android on pc's. My question is, how can I manually install/instruct the OS to said drivers? Would it be better to compile an android x86_64-Bliss os image for my device instead of using a currently available iso from their site to include the proper drivers for my hardware?
I haven't been able to find any post/forum with anyone using this particular laptop for Bliss OS. I can use the "[ROOT] alogcat" app to provide info. I also noted not all apps can gain root access amongst them are the Magisk app (can't identify the OS .img for direct patching), FX file browser can't access root dir access, and the default file manager doesn't see usb pen-drives (FX file browser does).
Any and all help you can provide is extremely welcome and appreciated as this OS flows fantastically on this device. Even Bliss os 15-android 12 runs butter smooth, albeit the same hardware issues.
hugoBOSS1981 said:
Not sure if I'm posting in the correct channel, if not, just let me know the right place to ask. Thank you.
I have an HP 11 Stream (ah117wm) laptop which has an embedded HD (32GB) and a Realtek wifi/BT m.2 card (rtl8822be); to which I installed Bliss OS 14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cross-hd.iso.
As expected, the majority of things work fine, aside from the Wi-Fi/BT (can't enable either) as it seems no drivers are loaded for the hardware. I'm familiar with rooting phones and using Linux, but I'm new to android on pc's. My question is, how can I manually install/instruct the OS to said drivers? Would it be better to compile an android x86_64-Bliss os image for my device instead of using a currently available iso from their site to include the proper drivers for my hardware?
I haven't been able to find any post/forum with anyone using this particular laptop for Bliss OS. I can use the "[ROOT] alogcat" app to provide info. I also noted not all apps can gain root access amongst them are the Magisk app (can't identify the OS .img for direct patching), FX file browser can't access root dir access, and the default file manager doesn't see usb pen-drives (FX file browser does).
Any and all help you can provide is extremely welcome and appreciated as this OS flows fantastically on this device. Even Bliss os 15-android 12 runs butter smooth, albeit the same hardware issues.
Click to expand...
Click to collapse
UPDATE:
So I scrapped the 14.3 OS for 11.14 OS because the Wi-Fi /BT works. The downside is that the built-in updater menu doesn't connect to any servers to find updates. There are also issues with the microG suite replacement for Google Play Services, which causes limitations on which apps you can use, even if can install them. The included Aurora Store/Aurora Droid apps help update things out the box once you have internet access via Wi-Fi or in case you have a usb to ethernet adapter to get hardwired into your modem/gateway should you have issues getting wifi/BT to work. Some apps can't access play services to restore purchases such as Flipaclip as its tied to the platform (OS) store you bought it on, not your email like most apps are.