Related
So I've been playing around with my SL101, and finally got a version of ubuntu working (kindof) enough to do some playing and whatnot.
Currently using the TF101 image from lilstevie (unzipped to /sdcard/ubuntu.img ) and ubuntu-mountloop.zip from here (which I flash from recovery because i can't apx mode because of SBK's not found for my device).
I'm just running into a few issues:
Onboard keyboard not recognized (any release) (on boot it looks for a dock and doesn't find one, but the SL101 technically doesn't have one)
Intermittent stalling inside ubuntu
Touch isn't what I wish it would be like (no swipe, no longpress for menu, etc)
WiFi only works in one version I've tested: lilstevie's
We need development on the SL101, or at least some kind of guide helping semi-advanced users inject the needed modules/drivers to load things specific to the SL101! (onboard keyboad, remove secondary battery indicator, etc)
I'd really love to get all the kinks out and have a stable ubuntu dualboot (be it, pseudo dualboot, still none the less)
Now, I was asking around a couple of days ago in #android and #android-root on freenode, and found out, for "ubuntu for phones" (which we should see a version hit for the galaxy nexus near the end of this month) they're actually using android drivers, so I'm wondering if anyone's played with this at all, i.e. loading ubuntu with android's drivers and having everything work out of the box...
http://www.theregister.co.uk/2013/01/02/canonical_announces_ubuntu_for_phones/ said:
Because it uses the same device drivers as Android, Ubuntu for phones will be able to run on a wide variety of hardware, ranging from entry-level devices with single-core processors to advanced "superphones" based on multi-core ARM and Intel chips.
Click to expand...
Click to collapse
Topic in #ubuntu-phone on freenode said:
Source code and image should arrive end of Feb '13
Click to expand...
Click to collapse
Hi Devs!
I'm wondering why not more people here working to get android lollipop working on our beloved tablets
I started to read a little bit into the topic and found quick easy solutions on the web to get ordenary android-x86 images boot very well.
Draco wrote an How-To that is easy and works also perfect with the Surface-Pro
https://groups.google.com/forum/#!topic/android-x86/D85Jq02cLrE
I modified the UEFI files to work better with a out of the box intallation of the Surface and put it together with Android 5.0.2 test builds.
Collect everything I've uploaded in a Folder:
https://drive.google.com/folderview...V3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
working
multitouch screen
sound
internal Wifi from SP2 (88W8797)
Bluetooth
Type Cover 2 (on installation also)
Touch Cover 2 (on installation also)
Inclinometer (= rotation sensor)
Ambient light sensor
Front Cam (tested with open Camera)
Rear Cam (tested with open Camera)
OpenGL (tested with Antutu)
Issues so far
Accelerometer [HID-SENSOR-200073.0]
Gyroscope [HID-SENSOR-200076.0]
Magnetometer [HID-SENSOR-200076.0]
MS Pen not working
YouTube Videos not working (only low resolutions, working over chromecast)
...
Are there more people interrested in getting latest Android working better on our Surface Pro?
I can support and provide with modified files and my modified How-To if someone like to join.
Remix OS link:
Remix OS with working WiFi
Bliss-x86 link:
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
regards
Sandman01
bootmanager, gapp[EXT4], WIFI [firmwar+module], Type/Touch Cover 2
How-To
Here to download a Testbuild for Android 5.0.2 from Google Groups from rgb
https://groups.google.com/forum/#!topic/android-x86/3xClAbl5D_w
Info:
If an microSD card is inserted the boot process will fail, because the microSD replaces the SSD to be the hd0 device.
Solution: change the grub.cfg entry from hd0 to hd1 and also do the mod in the loopback cfg
[EDIT]: sinc latest UEFI Firmware update, booting from microSD isn't working anymore
gapps can be used from any place, just copy the contens of the .zip file to there correct places.
atm I use a small gapps package from paranoidandroid (PA)
http://d-h.st/o72
WiFi: (not required any more on available builds)
I compiled a build on my Ubuntu intallation and extract the files for you, hope copy the files works also on the downloadable iso.
Please give me feedback if the files are working for you.
usb8797_uapsta.bin replaced in /lib/firmware/mrvl/
mrvl folder replaced in /lib/modules/3.10.58-android-x86+/kernel/drivers/net/wireless
Touch/Type Cover 2: (not required any more on available builds)
hid folder replaced in /lib/modules/3.10.58-android-x86+/kernel/drivers/
Genymotion is a good choice
snailx said:
Genymotion is a good choice
Click to expand...
Click to collapse
Genymotin is only a emulator as far as I see!
I'm one of the users who want to run an os natively like i did with osx.
sandman01 said:
Genymotin is only a emulator as far as I see!
I'm one of the users who want to run an os natively like i did with osx.
Click to expand...
Click to collapse
Hi,
I'm very interested in this!
Could u pls post a tutorial of installing OSX on surface pro 3 ?
I have only installed Max OS 10.9 in VMware, but it's not smooth verywell.
Does WiFi work well within your OSX install ed on the Disk ?
Hi!
For OSX Yosemite go to
http://www.insanelymac.com
I'm on the SP2 and WIFi only per external USB Stick sorry
I hope similar tho the SP2 kex Files for SP3 are available
For me OSX with the use of touchscreens is not very comfortable.
Is like Win7 to small buttons
Also at Android I only get WIFI working via external USB Stick atm.
Sent from my D6503 using XDA Free mobile app
Thanks a lot, I'll try it.. someday..
Solution for gapps found by the guys from google groups.
Use a EXT4 Partition on the USB-Drive/SSD to get gapps working like a charm.
Post 2 with HOW-TO updated
Surface Pro 3
I can verify that this does not work on the Surface Pro 3. The touchscreen doesn't work, the type cover doesn't work and the pen doesn't work, so I can't even choose my language on the first screen.
epic118 said:
I can verify that this does not work on the Surface Pro 3. The touchscreen doesn't work, the type cover doesn't work and the pen doesn't work, so I can't even choose my language on the first screen.
Click to expand...
Click to collapse
I'm sorry for that, if you have time, can you also test a available Android 4.4.4 installation if olso there touchscreen is not working?
I correct the title and update the OP that everyone sees that on SP3 ther are more problems.
Touchscreen is working on SP2 but Type Cover 2 did not so I also need an external USB keyboard for analysing things in console (ALT+F1)
regards
Sandman01
sandman01 said:
I'm sorry for that, if you have time, can you also test a available Android 4.4.4 installation if olso there touchscreen is not working?
I correct the title and update the OP that everyone sees that on SP3 ther are more problems.
Touchscreen is working on SP2 but Type Cover 2 did not so I also need an external USB keyboard for analysing things in console (ALT+F1)
regards
Sandman01
Click to expand...
Click to collapse
Sure, I've got time!
I'm just going to try installing 4.4.4 and seeing if it works.
I'd like to see Lollipop for my RT
calikevin said:
I'd like to see Lollipop for my RT
Click to expand...
Click to collapse
Haha, I understand you, but I have to mention that I'm a noob.
As far as I understand, creating/porting the drivers/firmware/kernel modules for the surface rt will be much more difficult than starting from an existing project like android-x86.
At the moment I split my SSD into more partitiones, installed the third OS (Ubuntu 14.10), get the complete code from git repository and try to set up the build environment to learn more about things are working together.
Also on Ubuntu the WIFI (USB version of MARVELL 88W8797) wont work out of the box but after replacing the firmware from git.marvell.com I get it up working.
Unfortunately this is not working on Android that easy.
The kernel modul for WIFI is loaded (mwifiex.ko) but no additional network interface is showing (mlan0 should be created)
sandman01 said:
Are there more people interrested in getting latest Android working better on our Surface Pro?
I can support and provide with modified files and my modified How-To if someone like to join.
Click to expand...
Click to collapse
Haha, so glad I found this thread. First things first, is your avatar a paragliding or skydiving canopy? If so, end cells look fantastic and very nice acrobatics with your leg straight up...how did you manage that?
I spent all evening and well into the morning finally getting 4.4-r2 running successfully on my SP2 using Draco's guide. Very nice work there from him.
It's unbelievable how smooth the Android experience is natively. When people recommend the emulators they just don't understand until they experience it themselves.
I have the Type Cover 1, and it's fully functional, but bluetooth and WiFi do not work. I have an Edimax EW-7811Un which does work, but the internet speeds are unusable; it maxes out at .25 Mbps. Is there something I need to do or is there another WiFi dongle which works better? Which one do you use?
Do you know of any combo WiFi/BT dongles that work?
If I can solve the WiFi issue (don't really care about having a small dongle plugged in for android), I will be one happy camper.
One more question: I read the 4.4-r1 had some drivers or something that 4.4-r2 didn't. However, I couldn't get it to boot from USB (it would hang on the android screen). With that said, I just replaced the files within the 4.4-r2 files with the 4.4-r1 on the USB. Do I have to rebuild the thumb drive or can I just replace files?
I will try the Lollipop build later. Good to find someone else doing this! Too bad we're both newbs lol.
dimex said:
Haha, so glad I found this thread. First things first, is your avatar a paragliding or skydiving canopy? If so, end cells look fantastic and very nice acrobatics with your leg straight up...how did you manage that?
I spent all evening and well into the morning finally getting 4.4-r2 running successfully on my SP2 using Draco's guide. Very nice work there from him.
It's unbelievable how smooth the Android experience is natively. When people recommend the emulators they just don't understand until they experience it themselves.
I have the Type Cover 1, and it's fully functional, but bluetooth and WiFi do not work. I have an Edimax EW-7811Un which does work, but the internet speeds are unusable; it maxes out at .25 Mbps. Is there something I need to do or is there another WiFi dongle which works better? Which one do you use?
Do you know of any combo WiFi/BT dongles that work?
If I can solve the WiFi issue (don't really care about having a small dongle plugged in for android), I will be one happy camper.
One more question: I read the 4.4-r1 had some drivers or something that 4.4-r2 didn't. However, I couldn't get it to boot from USB (it would hang on the android screen). With that said, I just replaced the files within the 4.4-r2 files with the 4.4-r1 on the USB. Do I have to rebuild the thumb drive or can I just replace files?
I will try the Lollipop build later. Good to find someone else doing this! Too bad we're both newbs lol.
Click to expand...
Click to collapse
Hi there!
I got 4.4-r2 working on my SP3 and about the internet issue you can use usb tethering with your Android phone
Both LTE and Wifi work and I get the same speed as my phone
dimex said:
Haha, so glad I found this thread. First things first, is your avatar a paragliding or skydiving canopy? If so, end cells look fantastic and very nice acrobatics with your leg straight up...how did you manage that?
Click to expand...
Click to collapse
Thats a paragliding canopy, and what you can see is the basic you have to manage when you want to fly acrobatic style.
Its a full stall where the canopy is not flying forward any more an the pilot is falling backwards untill the body stabilized under the backflying canopy
At the moment I use a USB2.0 HUB to connect the USB-Drive and the WLAN Stick at the same time. because after the last firmware Upgrade of my SP2 the Tablet do not boot any more from the microSD card. ?!?
The WLAN Stick is a original Samsung WIS12ABGNX for my Samsung TV/BD Player I used to test what can be done with them.
on Win8.1 I got a Speed of approx. 8-9MByte/sec (internal Marvell Wifi)
on Android 5.0.2 I got 4-5MByte/sec (external Samsung Wifi)
on Sony Xperia Z2 5.0.2 (unofficial) I got 2-3MByte/sec (internal ... Wifi)
when copy a file between my NAS (100MBit Network LAN structure)
so there is room for improvement, but first I really like to get more familiar with building Android from source by my self and try to get the internal Wifi working.
Also on Ubuntu 14.10 WiFi is working but not very stable but it does. (with including the firmware from git.marvell.com)
shasen1235 said:
Hi there!
I got 4.4-r2 working on my SP3 and about the internet issue you can use usb tethering with your Android phone
Both LTE and Wifi work and I get the same speed as my phone
Click to expand...
Click to collapse
I'd rather get a small nano USB WiFi dongle and "set it and forget it." I don't want to have to carry around the SP2 and my phone with a USB cable just to use the internet.
sandman01 said:
Thats a paragliding canopy, and what you can see is the basic you have to manage when you want to fly acrobatic style.
Its a full stall where the canopy is not flying forward any more an the pilot is falling backwards untill the body stabilized under the backflying canopy
Click to expand...
Click to collapse
Ya, the image was blurry, I was pretty sure that was a paragliding wing. I was a competitive high-performance canopy pilot (swooper) but have been out of the sport for a number of years. Some of the canopies now have radically different designs and the different wings between skydiving/paragliding/etc are merging now to make some cool stuff. Made a few paragliding flights, but never got into it.
sandman01 said:
after the last firmware Upgrade of my SP2 the Tablet do not boot any more from the microSD card. ?!?
Click to expand...
Click to collapse
You were able to boot android directly from a microSD and keep the SSD untouched (didn't even think of that)? Did the upgrade affect the partitions at all? Maybe the set root=(hd0,gpt#) and root=/dev/sda# changed, but I'm sure you already looked at that.
sandman01 said:
on Win8.1 I got a Speed of approx. 8-9MByte/sec (internal Marvell Wifi)
on Android 5.0.2 I got 4-5MByte/sec (external Samsung Wifi)
on Sony Xperia Z2 5.0.2 (unofficial) I got 2-3MByte/sec (internal ... Wifi)
when copy a file between my NAS (100MBit Network LAN structure)
Click to expand...
Click to collapse
Ok, I just want to make sure we're on the same page here. So on Android you were getting 5 MBps (40 Mbps)? That's super fast, unless you meant 5 Mbits, which is still faster than what I'm getting. Right now, I'm getting 0.25 Mbps (0.03125 MBps) which is unusable. I have another WiFi dongle arriving today, so maybe that will help. If it doesn't, why am I getting such slow speeds?
dimex said:
Ok, I just want to make sure we're on the same page here. So on Android you were getting 5 MBps (40 Mbps)? That's super fast, unless you meant 5 Mbits, which is still faster than what I'm getting. Right now, I'm getting 0.25 Mbps (0.03125 MBps) which is unusable. I have another WiFi dongle arriving today, so maybe that will help. If it doesn't, why am I getting such slow speeds?
Click to expand...
Click to collapse
Hi!
I did a 2nd x-check
Defenetly can receiver a 260MB file Form my NAS with ~3,2 Megabyte (~2min) per second and transmit the same file with ~4,5 Megabyte per second back to my NAS with the external Samsung USB WiFi stick
I would say its also possible to installiert Android to the microSD on a EXT4 partition and boot it via Grub.
Yes its all about the (hd0,gpt2) and /dev/sda2 or similar.
Just try it and if the numbers are not correct Boot into Grub and adapt the setting by pressing "e" and thest the setting with "F10"
Well I just tried the TP-Link TL-WN725N and it did not work at all.
Tried within 4.4-r1 that's installed to SP2's SSD and Lollipop booting from USB. WiFi just hangs at turning on and doesn't recognize the dongle.
Why am I getting such slow speeds on the other dongle? And do you know of any specific nano WiFi dongles that work well for this application? I tried searching on Google and in the Android-x86 group but came up empty.
I just want WiFi!!!! :crying:
Hi sorry for my english,there is a guide for install android on surface pro 1 ?
I think is same of surface pro 2, thanks.......
----
Thanx for your hard work jon4248 I'm hoping this will fix my non responsive touch screen......and a torrent link would be awesome to help my low bandwidth and constant drop outs.
angusc said:
Thanx for your hard work jon4248 I'm hoping this will fix my non responsive touch screen......and a torrent link would be awesome to help my low bandwidth and constant drop outs.
Click to expand...
Click to collapse
I've had reports from other people that it doesn't resolve that issue. I've never had that issue, but I've read that the only way to fix is to completely drain the surface 2 battery, until nothing comes in the screen and let it sit for a while, then fully charge it.
torrent attached, I maybe the only seed but I have fibre so it should be fast.
Thanx man!
I managed to download the file and flashed it successfully to my surface. As you said above, it did NOT fix my touch screen issues
I will try the drain battery totally and see what happens. I will report back if any success.
Thanx again for your work.
No success with battery draining.....I read other forum and Windows support page suggesting it's a known issue due to software updates and a fix will be release but don't know when.....very annoying as a tablet without touch is like a chocolate fire guard......totally useless!
EDIT: after a recent update I got touch screen function back again! Now I switched off further updates.
Added "update 3"
Updated to today. Enjoy!
Jon4248 said:
Updated to today. Enjoy!
Click to expand...
Click to collapse
If it's okay with you Jon4248, I Integrated some drivers from the original surface pro with your zip I can upload a copy here when I work out the kinks.
If any one has the new driver and firmware set for the original surface could you give me the link? If not i'm pretty sure I have them around here somewhere.
The wim file won't work on Surface pro, as it's Windows RT. You’ll have to build one from scratch using sysprep.
Jon4248 said:
The wim file won't work on Surface pro, as it's Windows RT. You’ll have to build one from scratch using sysprep.
Click to expand...
Click to collapse
I Haven't got around to using sysprep yet, but I managed to install a Frankenstein version of sorts made out of a bunch of different builds of RT I procured. There is no EFI or Boot directories on the main windows partition, but I far as I can tell Secure Boot is still enabled, also I could of Swore I also had a MBR partition but now it's showing as GPT since I let windows update, but that could of just been disk management acting up.
Any idea if this is any use to the community? if you want I could post some screens. Also I installed windows by booting to the recovery flash drive starting dos then running diskpart. Under diskpart I then procedded to clean the main disk- Scary, huh?. Next I went and ran setup.exe in the resources directory so it might install more like a build of windows on a x86 platform.
Hello.
Microsoft is working on an ARM version of Windows 10. It is already possible to get this working on a Raspberry PI 2.
According to this article:
https://www.modmy.com/developers-successfully-run-windows-10-surface-rt
someobdy managed to get Windows 10 partially working on a Surface RT. Is there any update on this? Considering Microsoft has an ARM version of Windows 10, what are the issues in getting this working?
kephax said:
Hello.
Microsoft is working on an ARM version of Windows 10. It is already possible to get this working on a Raspberry PI 2.
According to this article:
https://www.modmy.com/developers-successfully-run-windows-10-surface-rt
someobdy managed to get Windows 10 partially working on a Surface RT. Is there any update on this? Considering Microsoft has an ARM version of Windows 10, what are the issues in getting this working?
Click to expand...
Click to collapse
Windows 10 on ARM is exclusively for ARM64 devices. The version that runs on the raspberry pi 2 is Windows 10 IoT. Win10 iot can run on the surface tablet, but due to lack of apps, it is practically useless.
There is any news about win10 on arm on Surface rt ?
Lord-THX said:
There is any news about win10 on arm on Surface rt ?
Click to expand...
Click to collapse
No
Thanks
https://m.ithome.com/html/469731.htm
Here ^^^^
wangxiaohu said:
Here ^^^^
Click to expand...
Click to collapse
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
I can't download your Surface 2 English WIM from that site, can you tell me if there is there a mirror? Failing that a tip on how you got nvpep working would be interesting
Thanks!
wangxiaohu,
I managed to get your Surface 2 WIM, works great aside from the expected Bluetooth issue. Use the Uart16550tegra driver from Surface RT on Surface 2, once this is installed the Bluetooth will work.
Thanks to Ranomez for the tip
_CNR_ said:
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
Click to expand...
Click to collapse
Just spotted where I went wrong. I've been using sdbus.sys and sdstor.sys from a factory Surface 2 RT8.1 install, using these got me to desktop but I could never get nvpep to work without a BSOD on boot. Just noticed the sdbus.sys from the Chinese WIM is older than the one I took from my Surface 2 RT8.1 install.
sdbus 9.3.9600.16497 bad, 9.3.9600.16384 good. Combo of any nvpep and sdbus 9.3.9600.16497 under 15035 will break it.
wangxiaohu said:
https://m.ithome.com/html/469731.htm
Here ^^^^
Click to expand...
Click to collapse
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
domboy said:
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
Click to expand...
Click to collapse
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
domboy said:
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
Click to expand...
Click to collapse
_CNR_ said:
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
I can't download your Surface 2 English WIM from that site, can you tell me if there is there a mirror? Failing that a tip on how you got nvpep working would be interesting
Thanks!
Click to expand...
Click to collapse
Yes it works... There are some caveats not stated in the instruction.
wangxiaohu said:
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
Click to expand...
Click to collapse
That's really cool! I had no idea there was a build of Windows 10 ARM Edition that would run on the Surface RT/2. Thanks for posting the link to those instructions!
I suspect you're correct about no newer builds. Though considering my old Surface RT is still running RT 8.0 for the jailbreak, any version of 10 would be a lot newer. Am I correct in assuming all the open-source apps compiled for RT (since they're ARM32) would also run on this build of Windows 10? I'm going to have to try this when I get some time.
domboy said:
That's really cool! I had no idea there was a build of Windows 10 ARM Edition that would run on the Surface RT/2. Thanks for posting the link to those instructions!
I suspect you're correct about no newer builds. Though considering my old Surface RT is still running RT 8.0 for the jailbreak, any version of 10 would be a lot newer. Am I correct in assuming all the open-source apps compiled for RT (since they're ARM32) would also run on this build of Windows 10? I'm going to have to try this when I get some time.
Click to expand...
Click to collapse
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
wangxiaohu said:
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
Click to expand...
Click to collapse
I appreciate the warning! I am not surprised to hear that it is slow, otherwise Microsoft might have actually released it officially. I probably will wait to try this until I have no other use for the device (once the Netflix app stops working). Still, it's neat to see it is actually possible.
wangxiaohu said:
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
Click to expand...
Click to collapse
There are apparently newer ARM32 builds but its very unlikely we will ever get to see them and as it stands I think we are lucky to have 15035.
wangxiaohu said:
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
Click to expand...
Click to collapse
My nvpep troubles:
I found where I was going wrong with my WIM (thanks to your WIM) and what was causing nvpep to trigger a BSOD on boot. I don't understand the underlying cause but I was using sdbus 9.3.9600.16497 from my Surface 2 RT8.1 install (Surface2_BMR_20.2.19.0 recovery media), once I switched to sdbus 9.3.9600.16384 everything was fine.
Once that was sorted I was able to make my own working WIM and I've been playing with making it work as well as possible on my Surface 2:
Error on first boot:
Before allowing 15035 to boot for the first time create a new directory (\EFI\Microsoft\Recovery) and create an empty BCD store there.
Camera fix:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform]
"EnableFrameServerMode"=dword:00000000
Bluetooth fix:
Use the Uart16550tegra driver from Surface RT on Surface 2, once this is installed the Bluetooth will work.
Edge Tweaking:
Edge can be made a little better from about:flags - enable canary and allow high memory usage. This is not my tip but it seems to help, only real issue I have with Edge at the moment is YouTube but I've been told to give myTube a try.
Build Expired Nag Window:
Delete File \Windows\System32\LicensingUI.exe
Apps Working:
So far managed to get working the following MS apps: Onedrive, Remote Desktop, Skype, Photos, Camera, Scan, Films & TV, Mail & Calendar. Oh, and also an old version of Maps that still works - GPS is good. Third party apps tried so far - Team Viewer & VLC.
Pictures: https://imgur.com/a/ujnLlFI
List of apps that that seem to work on Windows 10 15035 so far - newer versions may work but would require manifest mods:
Code:
Microsoft.DesktopAppInstaller_2019.1019.1.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsStore_11811.1001.2713.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftSkyDrive_17.30.3.0_neutral_~_8wekyb3d8bbwe
Microsoft.RemoteDesktop_10.1.1107.0_neutral_~_8wekyb3d8bbwe
Microsoft.SkypeApp_12.1815.210.1000_neutral_~_kzf8qxf38zg5c
Microsoft.Windows.Photos_2017.35063.44410.1000_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCamera_2017.727.40.2000_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsScan_2014.523.326.3026_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneVideo_2019.18052.10711.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCommunicationsApps_16005.11001.20116.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.WindowsMaps_4.1509.50912.0
TeamViewer.31414B719FA93_15.0.100.0_neutral_~_89446h4zmeyyt
VideoLAN.VLC_3.2.1.0_neutral_~_paz6r1rewnh0a
Not exactly current in some cases but they still seem to function.
These I have installed but not used. It would be a surprise if the wireless display worked (I don't have the adapter) and I'm not a telegram user but will sign up to test later.
Code:
Microsoft.SurfaceWirelessDisplayAdapter_3.4.137.1000_neutral_~_8wekyb3d8bbwe
38833FF26BA1D.UnigramPreview_3.6.2286.0_neutral_~_g9c9v27vpyspw
I'm not really a big app user so I've just been adding stuff to make 15035 feel a little less empty
There is this version of Maps:
Code:
Microsoft.WindowsMaps_2017.1003.1829.0_neutral
Should work on 15035 but it requires 15063 as a minimum to install and I have not looked into what's required to modify the manifest, repack and sign yet. For the moment I've focused on what will work without too much trouble.
Qiangong2 said:
No
Click to expand...
Click to collapse
@Qiangong2
Are you going to try this? Need your feedback.
k4955 said:
@Qiangong2
Are you going to try this? Need your feedback.
Click to expand...
Click to collapse
I tried but the install was so glitchy that I reverted back to RT 8.1.
Qiangong2 said:
I tried but the install was so glitchy that I reverted back to RT 8.1.
Click to expand...
Click to collapse
Once installed its not bad, I've got a dual boot setup on my Surface 2 just to be on the safe side though.
It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Thanks for setting up a distinct thread. Things were getting confusing!
john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right
Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.
john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now
Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.
Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom
Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!
Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.
Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.
Before I flash this Rom: Why do I habe to wipe internal storage?
danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom