Related
I've always been more of an Arch than Ubuntu person (how do you know if someone uses ArchLinux? Don't worry, they'll tell you)
This requires you to be unlocked and on the JB bootloader. I disclaim all responsibility if it somehow turns your tablet into a pile of ashes...
What works:
Dual boot with Android.
Internal storage and MicroSD Card
X11, with compositing
Audio
Mouse and keyboard on the dock, as well as dock hotplugging.
Touchscreen
Playing videos (full 1080P works great.) using Xfce's media player
Sensors (Light, compass, accelerometer, gyro). These are all exposed under sysfs.
Charging / Dock charging. This appears to be managed by the kernel.
USB gadget (as a RNDIS device for network access via USB)
CPU frequency scaling / Tegra LP core. The LP core is automatically used you can see its status in /sys/kernel/cluster/active (when that file reads LP) and its use is simply what the current CPU1 use appears to be.
WiFi, with NetworkManager
3G, on the TF300TG model, with NetworkManager
Battery (and dock) status in Xfce
USB port on the dock
Some sensible key remapping (Back -> Escape, Search -> Alt, Home -> Super)
What doesn't work:
Bluetooth
Two finger scrolling with the mouse
Rebooting from Linux (have to do a sync then hard power off)
Basic framebuffer console - to get dual boot working I had to remove the FB console
Using "standard" xv (as in, mplayer -vo xv). Untested really, use gstreamer.
Cameras
Current priorities:
Get Bluetooth working
Get two finger scrolling working.
Get rebooting working
Anything else is untested. Currently, I'm using the TF300TG's kernel source at https://github.com/cb22/tf300tg_jb_kernel - which is just the standard source from ASUS with a patch or two.
Dual booting:
At the moment, my "hybrid" initramfs checks for a file ".boot_linux" on the internal SD card (/data/media/.boot_linux or /storage/sdcard0/.boot_linux - same thing). If it exists, it boots Linux, otherwise, Android starts up. It wouldn't be difficult at all to make a simple Android app with a "Reboot into Linux" button, and vice versa one for Linux with "Reboot into Android"
Important note:
Currently, the provided kernel / initramfs is built for the TF300TG. It does seem to work fine on the TF300T however.
Downloads:
Kernel + Initramfs blob: https://rapidshare.com/files/2827313479/hybridkernel.blob
RootFS with Xfce: https://rapidshare.com/files/201953815/linux.tar.gz
Installation:
Flash the blob to staging using fastboot.
Untar the rootfs to /data/linux/. The easiest way to do this is probably to copy it across to the Transformer via adb or MTP, then run
Code:
$ su
# mkdir /data/linux
# tar -xzvf /storage/sdcard0/linux.tar.gz -C /data/linux
Issues:
Apparently permissions aren't set properly when untar-ing. This can be "fixed" by a chmod 755, apparently. As soon as I can, I'll make a better way of installing this (update.zip style)
Credits:
This work is based off the Arch Linux ARM distribution
Sounds good, I think would be nice together with a dual boot kernel :good:
AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.
Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.
if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:
Valantur said:
AWESOME! This is what I've been looking for. Thanks for kick starting this, I'm flashing the recovery right away. I suppose I'll start playing around with the .config and see where that takes me.
C'mon people! lets get this done so we can then try out dualboot options and bring some GNU/Linux flavor to the Transformer Pad.
Click to expand...
Click to collapse
That's the aim! It would be really nice to have Android for tablet mode, and GNU/Linux for dock mode.
Nekromantik said:
Good work. Im waiting for a working Ubuntu so I can install Blackbuntu.
Shame Im on ICS bootloader as I would have tried it.
The Prime Ubuntu project aint had any updates recently sadly.
Click to expand...
Click to collapse
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
-angel* said:
if you get this working, would you then maybe get the win8 tablet version also working? Loving linux, but Win8 on tablets even a bit better :good:
Click to expand...
Click to collapse
Highly unlikely, sorry, and definitely not my field of expertise!
yeah nP - was just a think if they would have similar kernels...
Video looks very good, but as you say in the first post, nothing for ppl who don't know how to flash it and as I need the tablet for school I'd need dual boot at all... :/
But get on your working, really nice, but unfortunately I don't know anything about developing such things, so I can't help you...
This is awesome i'm gonna have to read up on this to see how it works! great work! Always wanted something like this.
cb22 said:
You can always use NVflash to backup your bootloader and such, then freely flash away. That's what I did (I'm on the TF300TG, and no one has uploaded their JB dlpkgfile *hint* *hint* and it's not available on ASUS's site yet) so I simply restored using NVflash to get my ICS with 3G back for when I'm not dev'ing.
Also - the ideas port over to any GNU/Linux system fairly easily once figured out - getting Ubuntu running wouldn't be much more effort. I'm using Arch to start since I understand it better (and prefer it)
Click to expand...
Click to collapse
Yeah.
Might try when I get some spare time.
Great initiative! I'd personally prefer a native debian distro over Arch but I figure once you've laid the groundwork the road's paved for more distro's.
Finally, a real reason to unlock the tab. When this works and it's dual boot, I will be unlocking and installing this.
Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!
Would it be possible to get it dualboot with an external HDD's? Because you can only get external SD's only up to 64gb (as I know and not all of them work) and external HDD's usually have a bit more storage
I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks
spenat said:
Amazing! I just hope that it will be possible to dualboot with normal android installed. If so, it would be absolutely perfect. Keep going, buddy!
Click to expand...
Click to collapse
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
Valantur said:
I've been playing around with this today, and I was wondering if you could upload a barebones arch system (without KDE) but with any other improvements you might have been working on.
Thanks
Click to expand...
Click to collapse
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.
Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?
aachour said:
Hello,
Can you use the package manager and install other DM the same way we would on a X86pc?
Click to expand...
Click to collapse
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.
cb22 said:
That's what I've been working on! I have a kernel that supports full features of both Android and Arch (well sorta - no FB console, so no boot messages or such) and an initramfs that allows you to select (at the moment its hard coded, but I'll make a simple interface to select which one to boot, as well as things like telling Android to reboot into Linux, or vice versa). In terms of implementation, essentially it's just an initramfs chain loader.
I shall - I've gotten WiFi working (works great with NetworkManager even) - I just have a very busy week with varsity work, I'll try and put the latest stuff online over the weekend.
Click to expand...
Click to collapse
This project looks awesome. i have a tf300t and intermediate arch linux experience( have made multiple working setups, compiled drivers etc, and would love to do anything i can to help this project, let me know if there is anything i can do
yeah! always looked for linux on this tablet! keep up the development guys
Valantur said:
I guess you could, once you get wifi working. We are waiting for cb22 to upload a new kernel+rootfs with a working wifi interface.
Click to expand...
Click to collapse
Unfortunately I didn't have time over the weekend to get things tidied up and uploaded - I start writing exams soon so things are a bit hectic on my side (coupled with the fact that I actually use my TF for varsity). I'll try to sort things out as soon as I can
Are there any Kernels or Custom Roms for the WFS that have the code for making the WFS act as a HID device (keyboard)
There are details of the code @ github.com/pelya/android-keyboard-gadget
This Phone is not now my Daily driver and I am looking to repurpose it to something useful. What I would like to do is use my WFS as a password vault that can enter passwords to my PC using this kernel update and some APKS like play.google.com/store/apps/details?id=remote.hid.keyboard.client and keypass or similar to make my WFS in to a password Vault that can automatically enter details in to the relevant fields in a web page.
I know there are issues with security of shared memory and clip board but I intend to delete most if not all other Apps. There is no SIM in the phone and the Wi-Fi and BT will be turned off unless I can get it to work as a BT keyboard as well to enter the credentials in to the browser on my Android phone or my IPad.
I have boot loader unlocked S-on, CWM recovery installed and currently running Olivers Marvellous CM10, as just upgraded CWM to V6.0.5.3 I able to try Olivers CM11 build next weekend.
Last time I coded in anger was 1992 writing Pascal on a Vax so doing these mods myself is a bit beyond me
Thanks for any Help.
I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img
MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments
Thanks Steel01!
I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).
Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...
I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!
Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance
Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse
I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers
This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility
Hello,
I just tried to install Remix OS 2.0.205 64-bit UEFI boot on my brand new Samsung Galaxy Tab Pro S. The procedure went well and I could boot ok. Unfortunately the touch screen and the wireless are both not working. Rest seems to be ok, but without wireless, there is not much I can do...
Hello....we're you ever able to get this running on your tabpro s? I'm contemplating buying a tabpro.
Sent from my SM-P905V using XDA-Developers mobile app
I just bought this tablet and I would like to know too. I feel like remix on this would be amazing...
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
How can this be sorted out as I would love to have this on my Tabpro S!
mrDmola said:
Hey, I've confirmed that Remix OS 3.0 does boot on my Galaxy Tab Pro S and the touch screen does work along with the keyboard! Wi-Fi, screen brightness control, and the touchpad is not working though.
Click to expand...
Click to collapse
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I'm going to install it on my Tabpro S tonight and will report back.
Biggenz said:
I'm going to install it on my Tabpro S tonight and will report back.
Click to expand...
Click to collapse
EDIT2: or these methods also from the xda remix 3.0 threads
In /system/build.prop change ro.remixos.box=true to false (should give brithness icon on the bottom)
or
Use Fn+left or right key combination
or
Edit: try this https://play.google.com/store/apps/details?id=com.curvefish.widgets.brightnesslevelGreat!
it was mentioned on another xda remix 3.0 thread.
looking forward to it Im waiting for my usb adapter but might consider the partition method if brightness can be lowerd via a work around to save battery or fixed.
I installed it last night and can confirm what mrDmola said. Everything works fine apart from wifi and screen brightness. For me the keyboard and track pad DID work. Such a shame as it's a brilliant OS.
Are there any developers who can sort this out for some beer money?
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
nielo360 said:
I'd donate if someone was willing to fix WiFi and brightness as its an excellent device for dual booting. Currently I use splashtop windows store version to stream ami duo os android from my desktop. It works flawlessly lag free with most games and touch screen works well with splashtop. I'd prefer remix however as a native os.
Click to expand...
Click to collapse
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Biggenz said:
I tried installing Android-x86 but that doesn't even boot. I just get a black screen and my Tabpro S becomes unresponsive. I couldn't switch it back on and nearly got worried. A soft reset sorted it out.
Then I also tried Phoenix OS which works fine on my PC, but same again on the Tabpro, it won't boot. Just goes black screen and then nothing.
Nielo have you tried Phoenix OS by any chance? If not could you try to install it and let me know your findings please?
Click to expand...
Click to collapse
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
nielo360 said:
I haven't tried that OS, I will try remix os if I can find a wifi fix. I'm still waiting for my Samsung usb adapter to boot via usb
Click to expand...
Click to collapse
Phoenix OS is very similar but I prefer Remix OS.
Why is it so hard for someone to tell us how to fix this problem?
nielo360 said:
Hi I too have a tabpro s, and want to install remix os or stock android. My question is have you install on a partition? or usb stick? if on a partition does it automatically give you an option to boot into windows/ remix? or is there a separate method.
Speaking of brightness is there an option to set the brightness before booting? some laptops had this feature.
last question is installing remix the same as installing a stock marshmallow rom?
Click to expand...
Click to collapse
I installed on a partition It automatically gave me the option to boot into windows or remix OS. I had to change the boot settings in my bios first before I was able to do any of this though
Without wifi most games wont work so trying it would not be useful, but its good to see the touchscreen working. 2.0 had issues with touchscreens
WiFi drivers needed
Hey, I just installed the latest version of 3.0 as of 12th october 2016
Touch screen WORKS! (Unlike Surface Pro 4)
Touch pad now works
Keyboard works
*But the deal breaker remains Wifi*
Tab Pro S uses a Qualcomm wifi chip and obviously there are no drivers for it installed in the build of Android x86 that Remix OS are using.
Can't we just add these ourselves? Or do the drivers simply not exist for Android on x86?
Other quibbles but not as problematic...
No bluetooth
No screen brightness control
No battery info or charge levels
All again just driver issues.
It really would be wonderful to get this working as there are no other premium Android tablets on the market with a faster chipset than an iPad Pro and an AMOLED screen for 750 euros
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Great job thanks for your work on the issues looking forward to working wifi!
Is Remix OS better in terms of battery life?
My ProS doesnt last long with screen switched off, unless I shutdown windows.
commanderspike said:
Hey guys I have been making some progress with a rooted custom build of Remix OS.
The WiFi adapter chipset in the Tab Pro S is the Qualcomm QCA6174. The Linux drivers which come packaged with the Remix OS kernel as it stands do not work.
There are the same QCA6174 issues with Linux based OS - https://bbs.archlinux.org/viewtopic.php?id=204871
Following from that research I downloaded a few different versions of the QCA6174 driver from Github and it appears the filenames need to be a certain way for it to be picked up by Remix OS / Android x86 (see guide below).
The result is I can now get the WiFi hardware to be detected OK by Remix OS and it switches on, starts searching for access points... However we are not quite there yet. It does not actually detect any SSIDs or connect to the internet. So I need to figure out from the error logs why that is.
Bluetooth seems to now work as well - was able to show a list of discoverable devices and pair with my phone, but not pick up a LTE personal hotspot for the internet.
Seems something basic to do with TCP/IP or Ethernet connectivity is broken?
By the way all this needs root access to Remix OS. I used this guide to root - http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
Also I had to install a custom version of Remix OS with the bloatware removed and a more powerful File Manager along with Super User app pre-installed. I used this version based on Jide's v3.0.202 -
http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
You also need to edit a file on the EFI partition in Windows before rebooting to get proper root access. To add the REMOUNT_RW=1 flag to the kernel you are going to be editing the grub.cfg file in the /BOOT directory of your EFI partition and this won't be mounted in Explorer. To mount this using the guide I linked to above in Windows 10 it is important to run the command prompt as an administrator (right click, run as...) even if you are logged in as admin. By default it will run in user mode and you won't get permission to access the EFI partition at all.
So in summary -
1. In Windows install the custom version of Remix OS from here:
2. You do NOT need to install it on a separate partition, put it on C:/ drive
3. Do not reboot Windows after the installer finishes, instead run the Command Prompt (right click, run as admin)
4. Type command and enter - taskkill /im explorer.exe /f
5. Type command and enter - mountvol X: /s
6. Type command and enter - explorer.exe
7: Type command and enter X: and then cd to directory boot/grub
8: Edit the grub.cfg file in X:/boot/grub (command prompt - notepad grub.cfg) - please note DOS edit command removed from Windows 10 so it will open in Notepad
9. Add the line REMOUNT_RW=1 in the kernel commands, the line should look like this -
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
10. Reboot
11. At dual boot option screen select Remix OS and it will finalise installation, before booting to Remix OS desktop
12. Run Super User app, ignore message about it needing to search for an update
13. At the desktop run cyanogenmod File Manager (not the Mac OS style Remix OS one as it has no root access) and go to the root /system folder, grant full read/write privileges in Super User app when prompted
14. You will need to copy the QCA6174 driver files from a USB drive. These files you should download from here on a machine with internet access:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0
In Remix OS these belong in the following folder:
/system/lib/firmware/ath10k/QCA6174/hw3.0/
In the driver package downloaded from github the file "firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1" needs to be renamed firmware-4.bin
Make sure files are named as follows:
firmware-4.bin
board-2.bin
board.bin
15. Reboot and the WiFi hardware will now switch on in Remix OS and begin searching for access points, bluetooth should detect nearby devices.
Other stuff which I found currently works:
Touchscreen (it does not on Surface Pro 4 so big reason to use Tab Pro S!!)
Trackpad
Keyboard
Audio, with reservations (system sounds audible like tapping in calculator app, but MP3 media audio didn't work in bundled player)
To do:
Final fixes to WiFi
Screen brightness control
Battery charge level and standby (it can only tell if connected to A/C, no battery polling levels detected)
Further check audio and app compatibility once WiFi is working
Click to expand...
Click to collapse
Great work! Hope we will see the wifi working soon. I bought the tab pro s to replace my ipad pro, now it basically sit in dust, was thinking about selling it until I see this post.
Here' s my general experience with Remix OS (v 3.0.206) on my Asus T100. Not surprisingly, it's much the same to my Android x86 experience.
First, a big thanks to the team members at Jide and Anroid x86! And now on to my experience...
The install to my hard drive didn't proceed smoothly. I'm not sure it was because I already had Android x86 installed or because I have my Z drive mapped to my LAN and the install program tries (and fails) to mount my EFI partition there in order to install grub. To get past the failed install, I manually modified my EFI partition to add a menu item for Remix OS alongside Android x86.
After resolving the installation woes, Remix booted fairly quickly and the setup option worked fine. The OS works pretty well and seems to allow all my Android apps to run. I haven't installed and tried them all yet though.
Not all the hardware works. Here's what works and doesn't:
Working
Touchscreen - works
WiFi - 2.4 and 5 GHz both work. WiFi seems to stop working and can't be re-enabled if the tablet sleeps.
Track pad - works, but can't be disabled using the keyboard function key
Keyboard function key volume up and down
Keyboard function key brightness up and down
Dock USB
GPS
Suspend. (The notification light did not go out, so it wasn't fully suspended.) I didn't fully test suspend, so it may or may not be working properly.
Battery icon
External speakers
Accessing my dock hard drive
Not working
Auto brightness
Camera. It doesn't work at all.
HDMI Out. Video displayed does not fully fill width of screen. Audio still comes out of the T100. Booting will not complete if HDMI is connected; it stalls at the command line.
Notification/camera on light - stuck permanently on.
Auto rotate (and no manual rotate either)
Keyboard function key volume mute
Keyboard function key to disable/enable the track pad
Esc key doesn't always behave as the back key.
After putting the tablet into the keyboard dock, Remix launches its File Manager *every time*. It's annoying.
Not tested
Bluetooth
I had freezing issues with a previous Release Candidate of Remix, so this version is usable by comparison. However, with so many non-working items, Remix on the T100 is just passable and not quite ready for a daily driver for me. v 3.0.206 fixed an issue with not being able to use WiFi after it was turned off (and back). If auto-rotate was working, I'd consider using it as a daily driver...
Can you please share your installation procedure?
awyeong said:
Can you please share your installation procedure?
Click to expand...
Click to collapse
Hi, I must have missed the notification of your reply...
I purposefully omitted the installation procedure because it was a pain, I started with android-x86, and I don't really recall the exact steps. Are you having a specific issue?
Hi,
I also have a T100ha & was thinking about putting Remix on it. Actually i was debating buying a Chuwi hibook pro 2 to play with (windows 10 + remix). But its really identical to the T100HA I already have in terms of hardware specs (or at least close).
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
RichTJ99 said:
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
Click to expand...
Click to collapse
You don't need to create a new partition or resize an existing partition. It gets installed on your C Drive, most of it being installed in C:/RemixOS or whereever you choose. Your MBR will be modified to allow it to boot to WIndows or Remix.
Remix does not "run on top of" WIndows 10, like an emulator or VM. It is installed on the same hard drive, but is booted separately. But that reminds me...if you power on your tablet, it will boot straight to Windows. In order to boot to Remix, you have to a) hold power/Volume down to get to grub where you can select Remix, or b) Use Advanced Startup within Windows 10 to boot to Remix. It would be better if the Grub menu was presented on boot without the button mashing. Thanks, Microsoft/Asus!
You can/should try out a USB install to test it out. You can see what works/doesn't work for yourself and judge whether you want to install it to your hard drive or not. I still have it installed, but only use it occassionally.
So this isnt like Bluestacks which runs within windows? What I dont like about Bluestacks is the resources it uses even when its not running. The T100HA has very limited ones.
I see a number of posts on reddit with people trying to figure out how to install this on the T100HA.
Because I am a little fuzzy - Can you live install the ISO on a USB drive (like Ubuntu) for testing?
Anything not working for you on Remix?
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
RichTJ99 said:
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
Click to expand...
Click to collapse
This is the part that I don't exactly remember what I did to get it working.
You've probably disabled Secure Boot in Windows (required). I used Rufus to make my USB stick. I had problems when I made it with LiLi. So, if you didn't use Rufus, give it a whirl. Try the resident mode too.
Also, I think I used the Android-x86 USB install and copied the RemixOS files over top of it. Alternatively, go to http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and follow Step 1 only... First Steps: Prepairing for the Ubuntu Install
I'm stuck on logo...can you put your grub.cfg file here?
or al least the remix os entry...in other PCs, changing parameter I solve that...but now I can't in my asus T100taf...thanks.