Announcing Sailfish for the Sony Xperia SP
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Update 15 Feb 2016
I've uploaded a new version of SailfishOS 2.0.0.10 to the Mega folder, called sailfishos-huashan-release-2.0.0.10-1.zip. This is again based off CM-12.1, the same release as stated below. This release fixes a kernel bug which lets a lot of the Sailfish system crash. This also fixes the wlan connectivity, startup-wizard which sets the themes, on-screen keyboard not popping up, and SIM unlock never asked. I've got a fix for the backlight in the works.
Update 14 Feb 2016
A very experimental CM-12.1 based SailfishOS 2.0.0.10 build is uploaded to the Mega folder linked below.
This version is based off cm-12.1-20160212-NIGHTLY-huashan.zip. I want to stress that many things in this build are broken.
Update 05 Feb 2016
This port is heavily outdated. I do not have much spare time on my hands to continue porting but I will try to post a nightly version soon.
This version was based on Sailfish 1.1.6 and CM-11.0, but the world has moved on to Sailfish 2.0 and CM-12.1, and so must this port.
There's a photo up on imgur:
http://i.imgur.com/Vg3SZ6w.jpg
Special thanks to:
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Everyone from the SailfishOS team/community, sledges and mal- in particular.
Known issues:
Half the backlight doesnt work, this is clearly visible at the top of the screen
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Settings hangs for few seconds on first start (this seems to be related to bluetooth not being set up)
What works:
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi, GPS (does take a while to get a fix though), most of the sensors (proximity, lightsensor etc)
The half of the display backlight that does work is adjusted based on lightsensor input.
Charging, bottom ledbar basic functionality, audio works, audio via 3'5 jack also works.
Installation:
Insert default warranty void message here. Your warranty is now void
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an offical Sailfish OS build, and the Xperia SP is not the Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, search for it first on bit.ly/port-bugs, if your bug is not yet there, you can add it there or post it in this thread (I'll try to keep the xda thread and bugzilla in sync).
The Sailfish OS image does not provide recovery, and since the Xperia SP does not have a recovery partition, you need a seperate bootimage with only recovery on it to flash cm/stock/sailfishos upgrade.
The Sailfish OS image is based on a specific version of Cyanogenmod 11, which you will need to flash first.
You can find all the required files in a Mega folder: http://mega.nz/#F!7YhSTDIA!Akpjs8s3qT5_nEkN04fQ-Q
You can find a bootimage with only TWRP recovery in it called recoveryboot.img
This image can be flashed with fastboot (with phone turned off, hold vol up and plug in usb), then `fastboot flash boot recoveryboot.img`. After that reboot the phone (fastboot reboot), and it will boot into recovery. If you already have recovery from cm, then you can use that as well.
First do a full wipe (make a backup first if needed, TWRP can do this , then install CM11, the specific version you need is called: cm-11-20150712-NIGHTLY-huashan.zip
There is no need to reboot cause you wont use CM11 anyway, so just proceed and flash the Sailfish OS image, which is called: sailfishos-huashan-release-1.1.6.27-UNOFFICIAL-maikel-201508201214.zip
Flashing Sailfish OS is not as fast as flashing cm11, but it shouldn't take more than 10 minutes.
Then reboot. The first boot may take some time, during which the Sony logo is not displayed (WIP).
If the boot takes more than, lets say five minutes, try a reboot. You can power off the device by holding the power button until the LED bar turns red or the display brightness goes back to full, when the leds and display turn off the device is powered off.
If this doesn't work you can remove the back cover and press the little button in the little hole for 5 seconds, the device will vibrate thrice and the phone will be forced off.
If you want to return to your previous rom or restore a backup, use the recoveryboot.img using the commands stated at the top of this document, to boot into TWRP.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Sources
In order to comply with the GPL, the kernel sources used for this port are available here:
CM-11.0 based port: https://github.com/maikelwever/android_kernel_sony_msm8x60
CM-12.1 based port: https://github.com/maikelwever/android_kernel_sony_msm8960t
edit: make links + sailfish 2.0 notice, kernel sources, 2.0 link
You rock! Very interesting project. Sailfish is an unknown world for me (and for most of us I think), I might try this ROM out sooner or later.
Why do we need to install CM11 first? Is it based on it?
Goob job bro!!!!
But I'll try this port later since it's kinda buggy
Hope you will fix those bugs.
Tomoms said:
Why do we need to install CM11 first? Is it based on it?
Click to expand...
Click to collapse
SailfishOS uses libhybris to communicate with the hardware, which in turn is talking to the Android HAL (like hwcomposer), to avoid having to write drivers for each phone, which would be pretty much impossible due to the proprietary blobs used on almost every phone.
The libhybris build included in this SailfishOS port is based on CM11, so that's why you need that.
CM12 based SailfishOS is currently experimental, when that gets more stable I will try to make a CM12 based build.
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
boylush said:
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
Click to expand...
Click to collapse
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
maikoool said:
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
Click to expand...
Click to collapse
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Tomoms said:
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Click to expand...
Click to collapse
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
maikoool said:
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
Click to expand...
Click to collapse
man i was waiting for this thing :fingers-crossed:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
will follow this thread closely...........
finally something new and different to use.
cheers
avi.singh9993 said:
will follow this thread closely...........
finally something new and different to use.
cheers
Click to expand...
Click to collapse
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
This looks really good, if it will ever be in daily driver state this will be my go to rom
sledges said:
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
Click to expand...
Click to collapse
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Why don't you post please? DIT - doing it together!
sledges said:
Why don't you post please? DIT - doing it together!
Click to expand...
Click to collapse
well i asked my friend to post it,
many people saw it but unfortunately not much of a positive feedback.
now it's onto developer and his hardwork to develop and make it atleast daily driver. then some people will be interested in trying it
Tomoms said:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
Click to expand...
Click to collapse
I agree totally that it's the dream of a geek. I've noted all your comments and will try to fix them. Thank you very much for taking the time to test!
Spasik said:
This looks really good, if it will ever be in daily driver state this will be my go to rom
Click to expand...
Click to collapse
That's what I'm aiming for too!
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Sorry, but I couldn't care less about Facebook. I'm pretty convinced that everyone that is willing to try something like this is already on XDA anyway. Hopefully the work related part will be better possible when Android app emulation or something similar finally makes it to community Sailfish builds.
PS: I've been a bit busy with other things lately, sorry for not responding that fast. I'll try to roll a build with fixes and the latest Sailfish (1.1.7.28) asap.
This has changed the mac of my device
can I ask how's the development going?
If someone could port the only rom i would like to be ported on the SP: ColourOS, it will be AMaZING
Related
I have read a few posts in this section, but it is totally impossible for someone like me (new to smartphones, flashing and the rest) to understand anything. Would you please explain some of the terminologies used here? Some of them are: kernel, 3g, port, system.ext2, BT... and thousands more.
Thank you very much!
you don't really "need" to understand any of that.
all you need to do is to learn how to download files, learn how to extract the downloaded file, learn how to copy them to an sd card, and learn how to run a program inside windows mobile.
if you can do all that, you should be set!!!
just follow steps 1-6 (ignore step 1b - the part about system.ext2) - http://forum.xda-developers.com/showthread.php?t=951962
Well noted AkumaX. Thank you very much!
XDAndroid is a project to port Android onto older HTC phones.
There are two main parts of XDAndroid, which combine to form a complete port:
Kernel/drivers: You can find packages to run Android on old HTC phones from a variety of sources, but whatever package you use, all rely upon the kernels/drivers created by the XDAndroid team to enable the basic hardware.
Android system: The Android system forms all of the parts of the phone's interface that you can directly interact with. Once the kernel/drivers have setup the hardware, you can add on an Android system port of your choice to form a complete build. Many system ports are available, both in terms of different versions (2.1 Eclair, 2.2 Froyo, 2.3 Gingerbread, etc.) and different starting points in the case of ports written by those outside of XDAndroid.
XDAndroid releases an "official" system port you can use, which is directly ported over by the XDAndroid team from the Android Open Source Project, and is very close to stock. Many of the alternative builds you come across are modifications of the XDAndroid system, containing customizations that deviate farther from stock Android, while others have different starting points altogether, and are ports of the ROMs found on official shipping devices that have already been customized (but still use the same basic kernel/drivers found here).
Android is a framework that runs on top of Linux. In order to get Android running on our devices, first we must get Linux running on the hardware with all drivers implemented, and then, we hook Android into these drivers. Thus, broadly viewed, the XDAndroid project is divided into two parts: the kernel/drivers and the Android port.
When you look at the files in your Android directory, you'll probably see something like the following:
zImage: The Linux kernel and drivers.
modules-###: Additional drivers for the kernel. Your system will load without this, but things like wifi may not work, or you may encounter instability.
initrd.gz: Used in the Linux boot process.
system.ext2: Most of the Android framework.
rootfs.img: Additional parts of the Android framework that are customized for our devices.
data.img: This file contains what would be your internal memory on a real Android device. Whenever you install a program it goes in to here. A new empty one will be automatically created if you don't have one.
haret.exe: Reboots you from Windows into XDAndroid.
startup.txt: Commands passed to XDAndroid on bootup that are customized by the user.
ts-calibration: Contains calibration information for the touch screen. If you don't have this file, you will be prompted to calibrate your screen on startup.
AndroidApps: A folder where if you copy any apks into it, they will be automatically installed on bootup.
manekineko said:
XDAndroid is a project to port Android onto older HTC phones.
-------.
Click to expand...
Click to collapse
Good explanation manekineko!...I believe this is what op was looking for.
there is light at the end of the tunnel, it wont take much longer if the devs keep up this good work, until there can be made stable and good builds with good battery life etc. when the time is there i will create an complete noob friendly installation guide (with pics and maybe even an vid).
I'm currently trying to figure out which one to install!
manekineko said:
XDAndroid is a project to port Android onto older HTC phones.
There are two main parts of XDAndroid, which combine to form a complete port:
Kernel/drivers: You can find packages to run Android on old HTC phones from a variety of sources, but whatever package you use, all rely upon the kernels/drivers created by the XDAndroid team to enable the basic hardware.
Android system: The Android system forms all of the parts of the phone's interface that you can directly interact with. Once the kernel/drivers have setup the hardware, you can add on an Android system port of your choice to form a complete build. Many system ports are available, both in terms of different versions (2.1 Eclair, 2.2 Froyo, 2.3 Gingerbread, etc.) and different starting points in the case of ports written by those outside of XDAndroid.
XDAndroid releases an "official" system port you can use, which is directly ported over by the XDAndroid team from the Android Open Source Project, and is very close to stock. Many of the alternative builds you come across are modifications of the XDAndroid system, containing customizations that deviate farther from stock Android, while others have different starting points altogether, and are ports of the ROMs found on official shipping devices that have already been customized (but still use the same basic kernel/drivers found here).
Android is a framework that runs on top of Linux. In order to get Android running on our devices, first we must get Linux running on the hardware with all drivers implemented, and then, we hook Android into these drivers. Thus, broadly viewed, the XDAndroid project is divided into two parts: the kernel/drivers and the Android port.
When you look at the files in your Android directory, you'll probably see something like the following:
zImage: The Linux kernel and drivers.
modules-###: Additional drivers for the kernel. Your system will load without this, but things like wifi may not work, or you may encounter instability.
initrd.gz: Used in the Linux boot process.
system.ext2: Most of the Android framework.
rootfs.img: Additional parts of the Android framework that are customized for our devices.
data.img: This file contains what would be your internal memory on a real Android device. Whenever you install a program it goes in to here. A new empty one will be automatically created if you don't have one.
haret.exe: Reboots you from Windows into XDAndroid.
startup.txt: Commands passed to XDAndroid on bootup that are customized by the user.
ts-calibration: Contains calibration information for the touch screen. If you don't have this file, you will be prompted to calibrate your screen on startup.
AndroidApps: A folder where if you copy any apks into it, they will be automatically installed on bootup.
Click to expand...
Click to collapse
Thank you so much for your explanations, manekineko. I believe that I am now ready to cruise through all the threads of this section without fear.
shatred said:
there is light at the end of the tunnel, it wont take much longer if the devs keep up this good work, until there can be made stable and good builds with good battery life etc. when the time is there i will create an complete noob friendly installation guide (with pics and maybe even an vid).
Click to expand...
Click to collapse
shatred, I am eagerly waiting for two things: (i) for the developers to release the perfect Android builds (my sincere encouragements to them by the way!!!) and (ii) for your installation guide.
gueyenono said:
I'm currently trying to figure out which one to install!
Click to expand...
Click to collapse
tell me your phone type, so an rhod-100? 200? 300? etc.
and tell me what you prefer more, an good battery life and an stable running system without camera support OR less stable system, bad battery life but with camera support.
Tell me and i will help you
shatred said:
tell me your phone type, so an rhod-100? 200? 300? etc.
and tell me what you prefer more, an good battery life and an stable running system without camera support OR less stable system, bad battery life but with camera support.
Tell me and i will help you
Click to expand...
Click to collapse
Uhm... You no longer have to choose. WisTilt2 pulled the latest commits from GIT into his test kernel.
arrrghhh said:
Uhm... You no longer have to choose. WisTilt2 pulled the latest commits from GIT into his test kernel.
Click to expand...
Click to collapse
yeah but if you activate the camera libs the phone wont go into deep sleep mode right? or is that fixed already?
shatred said:
yeah but if you activate the camera libs the phone wont go into deep sleep mode right? or is that fixed already?
Click to expand...
Click to collapse
Seems I was wrong about that. It was the other way around, if the libs are disabled the phone won't sleep.
However, with FRX05 there's no need for the libs. FRX05 + GIT kernel or WisTilt2's newest kernel is all you need for cam.
arrrghhh said:
Seems I was wrong about that. It was the other way around, if the libs are disabled the phone won't sleep.
However, with FRX05 there's no need for the libs. FRX05 + GIT kernel or WisTilt2's newest kernel is all you need for cam.
Click to expand...
Click to collapse
hmm yeah about that, i tried frx05 with wistilt2 latest kernels but it doesnt work for me, i think its an problem with my user conf... can you perhaps send me your user conf from frx05?
shatred said:
hmm yeah about that, i tried frx05 with wistilt2 latest kernels but it doesnt work for me, i think its an problem with my user conf... can you perhaps send me your user conf from frx05?
Click to expand...
Click to collapse
Same for FRX04... It's in my bundle.
If you remove all of the ln -s and bind mounts, should work just fine...
This thread is for development updates, and an eventual release of testing candidates for the future of dual booting CM12 android roms on the Amazon Fire TV. At this time I am not planing on supporting the Fire TV stick since my development platform is based off USB3 booting.
There currently isn't even a stable branch in CM12 upstream so things are quite tricky right now.
I may eventually setup public nightlies once the core is stable.
IN PROGRESS FORM HERE: https://t.co/TXp9z7htDx
The goals for development are in this order:
Wifi [working]
Bluetooth [crashing]
Stable core [random resets possibly storage related]
Audio [possibly needs hacking to default to hdmi]
Recovery system [rom boots using the recovery partition currently]
Hardware Acceleration [untested]
Android TV addons [require stable core]
USB Formating and install app [apparently not everyone knows what gparted is]
Modified version of Rbox's bootloader [I'd like to add recovery to the loader then have stock and custom boot options]
Also, if you want to be ready for possible nightly testing, I highly recommend going to walmart and buying one of the playstation USB3 hubs. It's about $20 but allows you to plug in a USB3 drive and keyboard and mouse until bluetooth is working.
SETTING UP USB BOOTING:
Code:
#include <std_disclaimer.h>
/* * Your warranty is now void. *
* I am not responsible for bricked devices, dead USB drives,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these files
* before flashing them! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. */
PART ONE [Preparing the drive]:
This process will eventually be streamlined but for now I'll explain the process and how it relates to testing builds during development. Since the Fire TV only has an 8gb flash chip and has no hardware recovery trigger, it is quite the unforgiving device to develop on. The current boot method for my CM12 builds involves flashing over the recovery partition and using it as a sort of dualboot partition. The modified recovery partition then searches for ext4 partitions on and external (USB3 preferred) flash drive. Currently each build generates its own boot image to be flashed over recovery, but I'm currently in the process of exploring the possibility of following Rbox's method of loading a boot image from a system folder instead making only one flash to the actual device necessary going forward.
For USB3 booting during the development process I highly recommend using a USB3 hub for a keyboard and mouse while bluetooth pairing and control mapping is being worked on. I also recommend a USB3 drive.
1) Turn on a Linux machine or boot a Live CD
2) Open Gparted
3) Delete any partitions on the usb drive
4) Create three ext4 partitions, the first partion is system and should be about 1GB, the THIRD partition is cache, and should be about 768mb with 0mb following, you should then have the middle portion empty in the display, in this SECOND partition make your data partition fill the rest of the space.
PART TWO [Preparing the bootloader]:
WARNING this process currently involves replacing your recovery partition, remember kids dd and root is like holding a grenade, make sure you don't throw it at something you care about.
Also, if you are testing a build and it does not load using the previous bootloader, try flashing the latest one from the nightlies (and vise versa) as I am still in the process of stream lining the boot process as far as what should take place before system bring up on our device. If a different boot image loads the system with noticeably more stability let me know asap so I can track the causes of my current issues.
Code:
adb connect <STOCK FIRE TV IP>
adb push boot-<DATE>.img /sdcard
adb shell
cd /sdcard
su
dd if=boot-<DATE>.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Next I recommend side loading this apk to make rebooting into USB boot easier.
The three most recent "boot" images have been added to the downloads section, remember these should be flashed to recovery. Although they would work in boot, that would disable Rbox's loader and prevent you from loading stock OS.
PART THREE [Playing with instability]:
Great so now you have a USB3 booting image flashed to your recovery partition and you have an empty flash drive. This is where the tinkering begins. In the download section you will find a .tar.gz archive with a somewhat booting system with the aforementioned issues. Inside this archive is a system.img file which you will use dd to flash to the first partition of the flash drive you formated. After the system image is flashed you can plug your flash drive into your hub and reboot into recovery. Things will be great, wifi will show up and if you're quick enough you can complete setup and make it to the launcher. (the issue I'm currently working on is an odd timed reset that may be kernel or storage related oddly if you make it to the launcher and don't touch anything, it takes longer to reset)
If you made it this far, welcome to development. You can help by "kanging" (replacing system apk's and files with other versions to find more stable matches, or remove apks until things don't die then report back to me) Also if you make it to this point go ahead and fill out the form I mentioned earlier. Eventually any hotfix builds I do between nightly builds will be accessible to those users to play with.
Overhauling the boot system next and working on the reset debugging.
XDA:DevDB Information
TechVendetta ROM Development, ROM for the Amazon Fire TV
Contributors
TechVendetta, rbox
Source Code: https://github.com/TechV/android_device_amazon_bueller
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-01-29
Last Updated 2015-01-29
Reserved
UPDATE: I'm pretty much settled in to my new job/home now so I'm going to resume this project shortly. The first order of business is to see what sort of driver improvements we got from Amazon and whether their modifications help resolve the issues I was having. I only have the original FireTV so I'll be only testing on that. Not sure if the new one has an unlocked bootloader or recovery system so that will be up to whichever brave soul wants to test that. Hopefully tomorrow I can resync my repos and get a look at whats changed.
Reserved
Thanks for the update! Looking forward to seeing how this progresses.
Thanks for your work!
It would be nice run a CM12 build in Fire TV
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
TechVendetta said:
So far the main system seems promising, I feel like the reset issue, which is the primary major roadblock is either in the kernel, or in the storage management/selinux services. Selinux should be disabled in this build so I'm looking into the other two options right now.
Click to expand...
Click to collapse
Thank you for keeping us updated!
[email protected] said:
Thank you for keeping us updated!
Click to expand...
Click to collapse
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
aHcVolle said:
Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
Click to expand...
Click to collapse
Thats one of the goals I put up there, just unlike rboxs current loader I know a way to make it remote controlled. ;D I started a bit on it. The "friendly user release" will have a root installer app that will handle multiboot, formating flash drives, recovery options, updates etc.
Really looking forward to a CM12 Android TV ROM. It would be nice to know that Amazon would not be able to kill a rooted Fire TV when this becomes reality. Peace of Mind regarding the Fire TV would be Priceless!
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
hhairplane said:
Xposed too http://forum.xda-developers.com/showthread.php?t=3030118
Click to expand...
Click to collapse
I'm a big fan of exposed, I'll have to add that to my testing list. I get a bit more free time tonight so I'll be getting back to looking at WiFi and Bluetooth and the installer. I still have two possible routes for both installing and updating i have to consider.
Sent from my LG-VM670 using XDA Free mobile app
TechVendetta said:
I'll link this here for now, while I finish looking into the logs for bluetooth/wifi/audio before uploading a rough copy here. I think I'm going to use the individuals who filled out the form to test the installer and recovery apps I'll be doing after fixing the above three things.
:victory:| TEASERS |:victory:
Click to expand...
Click to collapse
Any luck with the video acceleration, eg for Kodi or others such as Netflix, etc? How about hdmi audio?
Thanks for the update!
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Sorry to hear that, Family is first! Although, maybe working on this will help take your mind away from that. Feel better!
TechVendetta said:
Video acceleration appears to be working, haven't got to audio. Had a death in the family this morning so i haven't had time to test my latest build.
Sent from my LG-VM670 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to hear that.
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
KLit75 said:
I recently installed CM 12 on a 2012 kfhd and wow!--it really brought that device to life! Performance/OC options are built right into the OS and another Dev made a custom kernel to oc to 1.7 ghz. But I have limited experience with CM and Android TV. Can we expect a similar UI and performance options with this? Or is it different for the set top boxes?
BTW--I think it's really great you're doing this. Lots of people are excited and it's very appreciated!!!
Click to expand...
Click to collapse
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
TechVendetta said:
I can overclock the kernel but I'm not sure if it will be necessary yet. As for the features, CM12 doesn't even have a "stable" build yet. (they call them M builds now) They are still porting customizations like that in. That rom may use some stuff pulled in by the dev from other projects like paranoid, aokp etc. I'm listening to what people are asking for and I'll be taking it into consideration once I get to tweaking release candidates.
Click to expand...
Click to collapse
Sounds great. Thinking now...an OC kernel probably isn't necessary since it's already real fast. But this rom I have works well on a relatively low end/older device. So I'm super excited about your project. Thanks again!
Hi folks.
I'm an Android firmware developer (you can see my posts here in xda) that got a yoga book yesterday. For me it works at it should (by now) but my hacker soul speak to me and said: "at least take a look to see what you can get from this device". I don't have many time, so I can't spend time doing roms or fixing things by myself, but I can share with you some info I get and help you with my knowledge if someone is interested in "play" with this device.
First of all, I'm not responsable of anything that you can break following these steps. Almost all of them are tested and with some common sense you will not break anything, and if you break anything I will try to help you to fix it (if you are polite), but this is a work in progress and hacking and the possibility of brick the device is always there.
I only have the Android version without LTE, so I only tested in my Book.
So, here we go:
1) Secret codes:
I get this codes decompiling EngineeringCode.apk with apktool. Be carefull with them:
####0000# - Display version info
####7599# - Display hardware info
####8375# - Display baseband info
####1111# - Factory test
####2222# - Display SN
####7777# - Factory Reset???
####5993# - Display internal frameWork version
####7642# - Cut the power off to reload the PMIC - This command shutdowns the device. Just press the power button to reboot.
####5236# - Display LCD name
####2834# - ES close test
####8899# - open the ums mode default for debug
####3333# - offline log
####3334# - offline modem log
####9527# - Mediaplayer setting
####78646# - RunIn test
####6020# - switch country code
####59930# - Display current country code
####8746# - Enter engineering mode
####4227# - Enter engineer test
####357# - DLP_TEST
To use these codes, open the contacts app, press the search button and enter the code in the search bar.
2) OTA Images
You can get OTA images directly from lenovo servers. Just open your browser and paste this url:
http://fus.lenovomm.com/firmware/3....WW06_BP_ROW&action=querynewfirmware&locale=en
Change device model if needed (LenovoYB1-X90F or LenovoYB1-X90L)
Change curfirmwarever to a valid OLD firmware, this way you will get the next one in age.
Change locale if needed.
With this url you will get a download url at the end of the result page. In this case: http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip
These images are not full ota images, they are diff versions. This means that we can't use them to mod the image, or recover a bricked device, but this is a first step
3) Custom images
We don't have real sources to build a custom image (the lenovo's open source files are useless), but this doesn't mean that we couldn't modify stock images to take out useless apks or get better performance.
We can get this using an Android Kitchen and a full update image for the device.
As Android kitchen you can use SuperR kitchen (https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434)
As full image, I only tested the one here (https://easy-firmware.com/index.php?a=browse&b=category&id=19521) because I can't download any newer one.
I tested uncompressing it, deodexing the apks and doing a new image. But I don't test it in the device because I need to install twrp to flash the new image and I don't have time to test. But this should work, I did it many times so if someone is interested I can give steps to do it and support for testing.
If someone can get the latest full images, send then to me and maybe I can get some time to do some tests.
PD: Probably we could use this as a base to get LineageOS 14.1 working: https://github.com/latte-dev/android_device_xiaomi_latte/tree/cm-14.1
So, if you are interested in some hacking with the Yoga Book, contact me and we could team to get the most of this device.
First of all thank you for your post, it´s really useful
if you could somehow manage to boot windows on this machine it´s by far the greatest war we have right now.
Il promise you a lunch or dinner on Lisbon whenevere you want!
joao1979 said:
First of all thank you for your post, it´s really useful
if you could somehow manage to boot windows on this machine it´s by far the greatest war we have right now.
Il promise you a lunch or dinner on Lisbon whenevere you want!
Click to expand...
Click to collapse
Sorry, my knowledge of Windows is only user level . Install it in personal computer to play games .
But I really don't know why people wants to run Windows there, it will go slowly than Android and its less touch oriented... but I suppose that this is a chat for another thread
corvus said:
Sorry, my knowledge of Windows is only user level . Install it in personal computer to play games .
But I really don't know why people wants to run Windows there, it will go slowly than Android and its less touch oriented... but I suppose that this is a chat for another thread
Click to expand...
Click to collapse
in my particular case, i´l admit that is for football manager the touch version
joao1979 said:
in my particular case, i´l admit that is for football manager the touch version
Click to expand...
Click to collapse
Have you tried running it through Crossover? It may be in its infancy but i have got a few apps running OK with it.
I have the full "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW" I can upload somewhere if anyone can suggest a good site to do so without signing up? The file is about 2.5gb
It will be great if we could get the latest version, because maybe these older versions have older files that we have updated in our tablets.
Mixing files could give unknown problems
The current TWRP is based on the new Yoga Tab 3
I am starting to think they do not do full roms for this in the same way they do for a lot of their other devices.
We know the otas are available from tabdl.ota.lenovomm.com/dls/v6/ and are named according to the 2 builds that it bridges. As easy-firmware had the december full rom under the file name B1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip I had hoped that I could work out the file path to pull it down.
There were some interesting ideas here, https://forum.xda-developers.com/android/help/how-download-stock-roms-lenovos-ota-t3109507 but it seems there is a difference between phonedl.ota and tabdl.ota
Queries to full roms that work for phones, don't seem to work for the yoga book.
Anyone with more web knowledge able to pick this up? I am not sure the files are there but I feel they should be.
Good luck
Update: the downloads seem to be hosted via CloudFront. An Amazon service, but I can not find out a way of listing the available files. The latest full rom would be
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_USR_S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip
But the Last 8 chars are random and we do not know what they are.
So we have two hopes. First work out the right query to the link from fus.lenovomm.com or two find a way of listing files available in tabdl.ota.lenovomm.com/dls/v6
Not sure I have got much further but ill keep trying when I can.
Hey, I should mention that I have some files that you may find helpful; I got them from the easy firmware website. They're all the .img files for each partition in Android (ie. boot.img, cache.img, config.img, factory.img, recovery.img, system.img) as well as: biosupdate.fv, bootloader, firmware.bin and gpt.bin. However, these of course aren't in the normal "flashable .zip ROM" format. So unless you know how to take apart these .img files they aren't very useful. If you need any more help or have any other questions about how far we've come on our own, feel free to ask. danjac also has great knowledge of our efforts.
Yes, I know how to use them, unpack, modify, etc. But what I want is the latest version, no a old version (I hav these files too). If you have them I can do some changes, debloat, etc.
Anyway, I see little interest in custom roms in this forum ( probably because it's not a device with a lot of users or the users are not the techy kind), so I prefer to help others with info than do a custom rom that only 2 or 3 people will use. Doing custom roms is a time hungry task and probably it doesnt worth the effort. Anyway this device is not full of bloatware like samsung ones, so it useable as it is.
As I said in my first post if anyone is interested I can give some hints and support to modify the full image (but only the latest one).
It's so sad that there are only a few interested owners of this tab - it's such a nice device but i fear the day lenovo decides to end their support for it. There will be no custom roms to switch to and keep the device alive - it will be a soon to be bit of old tech garbage BTW. I still use my Asus Transformer Prime because of the nice community
@NiffStipples I fully agree. This device is so powerful and its a suprise that it is invisible to the "market". In my humple opinion the normal ROMs aren't that bad besides missing updates but I would love to see all the power served through a custom rom. unfortunately programming is not my business
Stefan
Broomfundel said:
Have you tried running it through Crossover? It may be in its infancy but i have got a few apps running OK with it.
Click to expand...
Click to collapse
Interesting - is Crossover good (and does it require factory reset)?
Hi, It works well with some things and not others. Often the why and where are not obvious. It is basically "wine" the layer that allows some windows apps to run on a linux install. Tweeked to work with android. Just an install to put crossover on. Then another install (Within crossover), to put you app on crossover. If it doesn't work out of the box, there windows libraries you can switch out and dependencies you can install. (Eg: directx , .net) Even if your not technical. I would say get on the beta program and give it a try.
Hi! what do you mean by "lenovo's open source files are useless"? do you refer to this packet on lenovo's suppport site? download.lenovo.com/consumer/open_source_code/lenovo_yb1_x90f_l_osc_201608.zip
I've entered the Android YogaBook's BIOS and noticed that VT-X is enabled by default! With Limbo x86 we could get a fully working virtualized Windows or Linux, if it wasn't for... KVM. It seems like it's not enabled in Lenovo's default kernel. Could we get to recompile the kernel with this option on? i'm not a big android/ROM expert but i surfed the open_source_code folder from Lenovo and it seemed, to me, that we could rebuild the Kernel at least.
This could really change things!
morrolinux said:
Hi! what do you mean by "lenovo's open source files are useless"? do you refer to this packet on lenovo's suppport site? download.lenovo.com/consumer/open_source_code/lenovo_yb1_x90f_l_osc_201608.zip
I've entered the Android YogaBook's BIOS and noticed that VT-X is enabled by default! With Limbo x86 we could get a fully working virtualized Windows or Linux, if it wasn't for... KVM. It seems like it's not enabled in Lenovo's default kernel. Could we get to recompile the kernel with this option on? i'm not a big android/ROM expert but i surfed the open_source_code folder from Lenovo and it seemed, to me, that we could rebuild the Kernel at least.
This could really change things!
Click to expand...
Click to collapse
How did you enter the bios? Can you boot from usb?
anyone managed to use swiftkey keyboard?
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
About this project
This is not a regular ROM. Usually, ROMs are based on certain components provided by the vendor (e.g. the heavily modified kernel and certain proprietary components). In contrast, this ROM makes use of a largely unmodified mainline Linux kernel together with many open-source components. Only a tiny bit of firmware is taken from the stock ROM.
This has many advantages for security and maintainability, but also means that certain hardware features (e.g. Camera, GPS) are difficult to implement because they require significant effort and a lot of reverse engineering. Nevertheless, this ROM has reached a state where it is very much usable with the majority of functionality implemented.
(See "Development" in the GitHub README for a more technical introduction...)
New features
Android 9 (LineageOS 16.0) with latest security patches
Linux 4.19 kernel
Meltdown, Spectre, RIDL, Fallout, ... fixes
Vulkan graphics (experimental)
Less/no bloatware
Full backlight control (allows much lower brightness)
F2FS (with a compatible recovery)
Signature spoofing (allows using MicroG instead of proprietary Google Play Services)
WireGuard
Tested features
Display, Backlight control
Graphics (OpenGL etc)
Touchscreen
WiFi, Bluetooth
Audio: Speaker, Headphones, Microphone
Battery, Charging
Sensors: Accelerometer, Magnetometer
Internal Storage/External Storage (SD Card)
USB, USB-OTG
Hardware video accelerated codecs
Planned features (not working yet)
Suspend/Deep sleep states
Not planned
Camera
GPS
FAQ
How is the battery live? Screen-on time is probably similar if not longer, but there is a lot of battery drain in standby mode (even worse than on the ASUS system). I recommend that you turn off the tablet when you're not using it.
How do I obtain root access? There are various ways, but the recommended way for LineageOS is to flash addonsu. (Available below.) However, note that this will break SafetyNet. Use Magisk alternatively.
Can I use Netflix with this ROM? Yes, although you will need to build and flash the Widevine DRM addon manually (see below).
Installation
Preparation
Make sure you are running Android Lollipop (5.0).
You need an unlocked bootloader. LineageOS 16.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0. (The old "Intel" bootloader is no longer supported.)
Install TWRP
Make a full backup of the ASUS system. You may want to go back to it.
Do a full factory reset. Wipe data and cache partitions.
Install the main system using the flashable ZIP below.
If needed, install additional addons not included with the main system (see below).
Download
System image (install as ZIP in recovery): lineage-16.0-20191213-UNOFFICIAL-me176c-signed.zip
TWRP recovery image: Available in a separate thread.
Addons
There are various packages you can flash for additional functionality. Most of them are proprietary. All addons persist during LineageOS updates, so you do not need to flash them again after updating.
Google Apps (Google Play Services, Play Store, ...): Use Open GApps (x86, Android 9.0)
Fingerprint (used to pass SafetyNet/Google Play certification): Flash me176c-asus-fingerprint-signed.zip.
Magisk users: Alternatively, you can use MagiskHide Props Config with the fingerprint asus/WW_K013/K013:5.0/LRX21V/WW_K013-12.10.1.36-20151230:user/release-keys
Root: Flash addonsu-16.0-x86-me176c-signed.zip. Remove using addonsu-remove-16.0-x86-me176c-signed.zip
This will break SafetyNet. Alternatively, you can use Magisk.
Widevine DRM (used in certain streaming apps like Netflix): Flash widevine-x86-chromeos-12499.66.0_atlas.zip* [see below]
Houdini (used to run ARM apps on x86, may help if an app shows up as incompatible): Flash houdini-x86-chromeos-12499.66.0_atlas.zip* [see below]
Signature Spoofing (for use with microG): Flash me176c-signature-spoofing-signed.zip to enable signature spoofing. Grant permission with caution only.
*Houdini/Widevine: I do not provide pre-built ZIPs for those two addons. (See this post for more information.)
They can be built easily on any Linux distribution using android_vendor_google_chromeos-x86. Takes just a few minutes (depending on your download speed). No development experience or Android source code required.
If you are unable to build it, someone else may share a build with you. In that case, you can verify its integrity using the SHA-1 checksums available in the release notes.
XDA:DevDB Information
Unofficial LineageOS for ASUS MeMO Pad 7 (ME176C(X)), ROM for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: me176c-boot(strap) 0.3.0+
Based On: LineageOS
Version Information
Status: Beta
Created 2019-05-12
Last Updated 2019-12-13
Version History
LineageOS 16.0 (2019-12-13)
lambdadroid said:
Android security patch level: December 5, 2019
Updates: Linux (4.19.75 -> 4.19.89), Mesa (19.1.7 -> 19.3.0), MediaSDK (19.2.1 -> 19.3.1), …
Addons
Widevine/Houdini: Recommended version is now: 12499.66.0_atlas
Download: lineage-16.0-20191213-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-09-22)
lambdadroid said:
Android security patch level: September 5, 2019
Updates: Linux (4.19.68 -> 4.19.75), Mesa (19.1.4 -> 19.1.7)
Addons
Widevine/Houdini: Recommended version updated to 12239.92.0_nocturne
Download: lineage-16.0-20190922-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-08-19)
lambdadroid said:
Android security patch level: August 5, 2019
Use WiFi firmware from stock ROM
Add LineageOS power profiles
The default setting disables the turbo frequencies of the CPU to reduce heat (like on LineageOS 14.1).
The old behavior of LineageOS 16.0 (turbo on) can be restored by setting the power profile to "Quick".
Updates: Linux (4.19.57 -> 4.19.68), Mesa (19.1.1 -> 19.1.4), MediaSDK (2019 Q1 -> 19.2.1)
Download: lineage-16.0-20190819-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-07-07)
lambdadroid said:
Android security patch level: July 5, 2019
Updates: Linux (4.19.49 -> 4.19.57), Mesa (19.0.6 -> 19.1.1)
Download: lineage-16.0-20190707-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-06-09)
lambdadroid said:
Security Advisory
Android security patch level: June 5, 2019
Added mitigation and CPU microcode update for:
CVE-2018-12126, CVE-2018-12130, CVE-2018-12127, CVE-2019-11091
aka Zombieload, RIDL, Fallout, MDS, … so many names, sigh
Changelog
Enabled MPEG2 video codecs (including hardware acceleration)
Fixed warning: "There's an internal problem with your device. Contact your manufacturer for details."
Flashing "vfp-fix-lineage-16.0-me176c-signed.zip" is no longer necessary
Updates: Linux (4.19.42 -> 4.19.49), Mesa (19.0.4 -> 19.0.6)
Addons
CPU Microcode addon is now obsolete, since CPU microcode updates are included by default again.
Re-install me176c-boot if you have been using it.
Widevine/Houdini: Updated to 11895.118.0_nocturne
There are now simplified build instructions in BUILDING.md
Download
Installable ZIP: lineage-16.0-20190609-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
LineageOS 16.0 (2019-05-12)
lambdadroid said:
This build is a major update to LineageOS 16.0 (based on Android 9 Pie) and contains several weeks of work with significant cleanup and other major changes.
Major changes
Based on LineageOS 16.0 (Android 9 Pie)
Use Android Go build configuration to optimize for low RAM (More information)
Hardware accelerated video codecs are now open-source
The remaining proprietary components are no longer included by default and must be flashed manually if needed: (More information)
Widevine DRM (used in certain streaming apps like Netflix)
Houdini (used to run ARM apps on x86)
CPU microcode update
New installation instructions
LineageOS 16.0 requires me176c-bootstrap 0.3.0, included in me176c-boot 0.3.0.
The old ("Intel") bootloader is no longer supported.
There are many new "addons" that can be flashed for full functionality.
Please check the new installation instructions on the LineageOS 16.0 thread before installing this update.
Upgrading
Upgrading from LineageOS 14.1 may work but is untested (and largely unsupported)
Upgrading from LineageOS 16.0 test builds is not possible!
Do a factory reset before installing the new build.
Improvements
Use MAC address from stock ROM for both WiFi and Bluetooth
Put Bluetooth in low power mode while not actively in use (#37)
Fixes
Android security patch level: May 5, 2019
MTP (#33)
Green artifacts on video thumbnails in Gallery (#51)
Headset / headphones microphone detection (#19)
Other changes
Updates: Linux (4.14.72 -> 4.19.42), Mesa (18.2.1 -> 19.0.4), MediaSDK (2018 Q2.2 -> 2019 Q1), …
Download
Installable ZIP: lineage-16.0-20190512-UNOFFICIAL-me176c-signed.zip
Click to expand...
Click to collapse
Great news, I will try today at home! Thanks!!!
I have tested it today. Seems be work without any problems. Thank you.
Houdini/WidevineDRM
So far this ROM is working without any problem, The performance is usable, and the battery is OK due to hardware limitations.
I have a problem installing Houdini and Widevine DRM (I Don't have any development experience) yet i don't understand the instructions on how to make a ZIP and how and where i should put the MK files.
If you dont want to provide the flashable ZIP files that is alright, but could you atleast make a guide that we can follow?
Great Job and Thanks for making this unusable tablet usable again.
Bazgir said:
I have a problem installing Houdini and Widevine DRM (I Don't have any development experience) yet i don't understand the instructions on how to make a ZIP and how and where i should put the MK files.
If you dont want to provide the flashable ZIP files that is alright, but could you atleast make a guide that we can follow?
Click to expand...
Click to collapse
Making a step by step guide is quite difficult because it really depends on the system you are using. I'm guessing that most users will already run into trouble because it can be only built on Linux.
Creating a guide to set up a virtual machine etc., how to get into a terminal etc would require a lot of effort. This is time that I would rather spent in development. I realize this entire situation isn't ideal, but I haven't been able to come up with a better solution.
If you have a working Linux system, building should be pretty simple:
Download and unpack https://github.com/me176c-dev/android_vendor_google_chromeos-x86/archive/11647.154.0_nocturne.tar.gz
Open a terminal and run (in the extracted folder):
Code:
$ ./extract-files.sh
$ zip/build.sh
Find flashable ZIPs in zip/out.
No development experience needed.
This is also roughly what is already explained in https://github.com/me176c-dev/android_vendor_google_chromeos-x86 although the README has more background information because it is really intended for people that would like to use that project in own projects (e.g. in other ROMs).
Maybe someone else here would like to provide more detailed instructions?
Hey, Thanks for the Reply!
I have already setup the Virtual Machine and even tried "Sudo ./extract-files.sh" I'll get the messedge "https://imgur.com/a/Y1lKg5P"
It probebly fail because i don't have the OS for the chromeOS, But then again where should i put the extractions file so that the script can locate and extract the nessecary files?
Am i missing something? a file maybe? or should the script takeout the nessecery files from internet? (i have almost no clue what im talking about )
I have the ASUS K013 (ME176CX) (1GB RAM) (8GB ROM)
Thanks again!
Hello Again,
I managed to create the ZIP files, The only problem i had was that i needed the recovery files for Chromeos (Nocturne),
Ones i had the files i extracted the recovery and got the file named propretary, and build the ZIP.
The link for the "I cant provide it for you because i don't have 10 post"
For other builds: cros-update-service-appspot.com (Try to find the one called nocturne and then 73 (then eddit the url so that u get 154.0 insted of 104.1))
This was a crusial step to understand how to extract the files, u also need to put the zip in to the same directori as extract.build.sh,
I have not yet tried this, so im not sure if it will work. The SHA.1 Matches
Thanks!!
Bazgir said:
I have the ASUS K013 (ME176CX) (1GB RAM) (8GB ROM)
Click to expand...
Click to collapse
There is really a K013 with only 8 GB internal storage?
I've read this a few times, but haven't seen one before. Good to know that the ROM works fine on it.
Bazgir said:
I have already setup the Virtual Machine and even tried "Sudo ./extract-files.sh" I'll get the messedge "https://imgur.com/a/Y1lKg5P"
It probebly fail because i don't have the OS for the chromeOS, But then again where should i put the extractions file so that the script can locate and extract the nessecary files?
Am i missing something? a file maybe? or should the script takeout the nessecery files from internet? (i have almost no clue what im talking about )
Click to expand...
Click to collapse
Great! The script downloads everything for you, but it looks like you don't have "curl" installed. On Ubuntu, you can install it using "sudo apt install curl". Then it will probably download the same file you have already downloaded manually.
Bazgir said:
I managed to create the ZIP files, The only problem i had was that i needed the recovery files for Chromeos (Nocturne),
Ones i had the files i extracted the recovery and got the file named propretary, and build the ZIP.
The link for the "I cant provide it for you because i don't have 10 post"
For other builds: cros-update-service-appspot.com (Try to find the one called nocturne and then 73 (then eddit the url so that u get 154.0 insted of 104.1))
This was a crusial step to understand how to extract the files, u also need to put the zip in to the same directori as extract.build.sh,
Click to expand...
Click to collapse
You can skip this if you have "curl" installed.
Thanks for trying to build it and your feedback! I will try to make the README more clear, especially regarding additional dependencies (e.g. "curl") plus the commands to run.
I'm supprised on how the ROM turned out to be, being a x86 platform even tho it's not supported anymore, with Houdini and Widevine.
I was able to play games on the phone such as Old school runescape on the tablet (Not perfect but playable) watch videos on youtube with the sound bug :/
The battery is better but still horrible (it was like this before), Might download somekind of deepsleep app such as Greenify for that.
What magisk module i have downloaded för best possible preformance is NFS-INJECTOR in Magisk.
I don't have any major problem with the 8GB ROM even tho the emmc memory is very very bad (Read 40Mb/s and write 8-10Mb/s) Somehow when i installed old SD card which is R 20Mb/s and 10Mb/s the tablets performance increase even tho it has lover read and write speed.
Is there a way to optimize the performance for the tablet even more? The main problem is RAM and ROM, i feel like the emmc memory and the amount of ram is holding back the CPU/GPU
Thanks!
Bazgir said:
I was able to play games on the phone such as Old school runescape on the tablet (Not perfect but playable) watch videos on youtube with the sound bug :/
Click to expand...
Click to collapse
Sound bug?
Bazgir said:
I don't have any major problem with the 8GB ROM even tho the emmc memory is very very bad (Read 40Mb/s and write 8-10Mb/s) Somehow when i installed old SD card which is R 20Mb/s and 10Mb/s the tablets performance increase even tho it has lover read and write speed.
Is there a way to optimize the performance for the tablet even more? The main problem is RAM and ROM, i feel like the emmc memory and the amount of ram is holding back the CPU/GPU
Click to expand...
Click to collapse
Android and most apps raise their requirements each year as new devices are released with higher specs. Many devices come with 6GB+ RAM now.
Altogether, this tablet was already low-end when it was released. The CPU is pretty good compared to low-end ARM processors. But with ~800MB usable RAM this tablet can simply not keep up with apps that require more and more resources.
This tablet would do fine if Android and apps were continuously optimized to use less resources. However, the development actually goes into the opposite direction.
Sooner or later, this tablet will probably no longer manage to boot new Android versions at all, simply because all RAM is taken up by the system.
My point is: If you want to optimize this tablet, you need to go back in time. Not just with the OS (e.g. by downgrading to Android 4.4 KitKat), but with all apps you are using. If you go to ~2015 this tablet will likely do a much better job.
This ROM is definitely less "optimized" for this specific device, simply because it does not have most of the device-specific hacks they had for these Intel tablets back then. But this is the price for being able to keep it up to date with acceptable effort. And if you look back to ASUS's version of Lollipop, it usually didn't feel much better either even though it was technically more "optimized".
lambdadroid said:
Sound bug?
Android and most apps raise their requirements each year as new devices are released with higher specs. Many devices come with 6GB+ RAM now.
Altogether, this tablet was already low-end when it was released. The CPU is pretty good compared to low-end ARM processors. But with ~800MB usable RAM this tablet can simply not keep up with apps that require more and more resources.
This tablet would do fine if Android and apps were continuously optimized to use less resources. However, the development actually goes into the opposite direction.
Sooner or later, this tablet will probably no longer manage to boot new Android versions at all, simply because all RAM is taken up by the system.
My point is: If you want to optimize this tablet, you need to go back in time. Not just with the OS (e.g. by downgrading to Android 4.4 KitKat), but with all apps you are using. If you go to ~2015 this tablet will likely do a much better job.
This ROM is definitely less "optimized" for this specific device, simply because it does not have most of the device-specific hacks they had for these Intel tablets back then. But this is the price for being able to keep it up to date with acceptable effort. And if you look back to ASUS's version of Lollipop, it usually didn't feel much better either even though it was technically more "optimized".
Click to expand...
Click to collapse
Ignore the sound bug, I will just use headphones (small fix).
That's true, om overall pretty happy with the result nevertheless.
Thank you.
Bazgir said:
Ignore the sound bug, I will just use headphones (small fix).
Click to expand...
Click to collapse
I'm not aware of a "sound bug". If you would like to have it fixed, you will need to explain it a bit further.
Do not hesitate to report minor problems; some of them are really easy to fix and exist only because of an oversight. For all others I will decide if they are worth the effort.
lambdadroid said:
I'm not aware of a "sound bug". If you would like to have it fixed, you will need to explain it a bit further.
Do not hesitate to report minor problems; some of them are really easy to fix and exist only because of an oversight. For all others I will decide if they are worth the effort.
Click to expand...
Click to collapse
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Thanks
Bazgir said:
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Thanks
Click to expand...
Click to collapse
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.) Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: ) I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1, but it seems that the same problem still exists. Hope that these information helps to fix the bug.
Frisk Dreemurr said:
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.) Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: ) I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1, but it seems that the same problem still exists. Hope that these information helps to fix the bug.
Click to expand...
Click to collapse
Here is the link for Houdini: https://mega.nz/#!E9li3QBJ!uN_TVlPjWUu50F5j4FIk6CqapMt9_k7ix5r01GrdyVQ
Here is the link for Widevine: https://mega.nz/#!kxlWlI6Z!u5OqNzys3r1LyMq3U1UOejsxj87GR1-f6f5Bn6u12mI
Not sure if it will work for you, make sure you do a backup :good:
I´ve installed the ROM and it works great! Thanks a lot!
Bazgir said:
It's very hard to explain the sound it makes, but when ever i start a youtube video, it basicly has to encode the video and the sound, The sound syncs upp with the video and there for when the video is a bit choppy it creates those weird sounds.
This is what im talking about "https://vocaroo.com/i/s1s7rSAFCIv0"
Not sure if its a video encoding problem but looks like it.
Click to expand...
Click to collapse
Frisk Dreemurr said:
I had also encounter this problem in LineageOS 14.1 of this tablet... I have noticed that it always happen when multiple sounds are composed by the tablet itself instead of composed by one app. (When it plays notification sound when music (using music player) playing, it sounds laggy for a while, but when a game plays multiple sounds, it's fine.)
Click to expand...
Click to collapse
Weird, I've never seen (heard) this issue even though I test video playback quite often. I used to have problems with touch sounds that were usually played high pitched for some reason, but it magically went away with some later 14.1 release.
Frisk Dreemurr said:
Also, after not playing any sounds for a while, it will create a loud pop sound right when the first sound is played. (And it hurts my ear when I'm using earphones... :silly: )
Click to expand...
Click to collapse
I know about this one. Quite annoying. I suspect that it is due to some kind of energy saving. (The headphones get turned off after unused for a while.) Not sure how to avoid it...
Frisk Dreemurr said:
I haven't managed to build the Widevine and Houdini pack, so I don't know if the problem still goes the same in 16.1
Click to expand...
Click to collapse
FYI you don't need Widevine/Houdini for most apps. Listening to Music, watching normal YouTube videos works fine without it.
Widevine is mainly needed for paid video streaming (e.g. movies, ...), and Houdini for more uncommon apps and games that are not compiled for x86 (you can install it as soon as you see an app that is displayed as "incompatible" with your device).
Bazgir said:
Here is the link for Houdini: https://mega.nz/#!E9li3QBJ!uN_TVlPjWUu50F5j4FIk6CqapMt9_k7ix5r01GrdyVQ
Here is the link for Widevine: https://mega.nz/#!kxlWlI6Z!u5OqNzys3r1LyMq3U1UOejsxj87GR1-f6f5Bn6u12mI
Not sure if it will work for you, make sure you do a backup :good:
Click to expand...
Click to collapse
Thanks a lot for offering the files! :good: But it seems like it's not working on my tablet... :crying: (The SHA-1 of the files I downloaded matches the correct one.) Any ways to solve this problem?
Frisk Dreemurr said:
it seems like it's not working on my tablet... :crying: (The SHA-1 of the files I downloaded matches the correct one.) Any ways to solve this problem?
Click to expand...
Click to collapse
Weird error. Can you try flashing from internal storage/external SD card or using ADB sideload? Might be related to USB OTG.
Introduction
A new, updated version of Android for the Nintendo Switch. Now based off of Android 10 (Q) (LineageOS 17.1 with Shield TV trees) it's faster, more responsive and has many new features over the previous release, including deep sleep and an Android TV build.
Features
Android 10 based on Lineage 17.1
Significantly improved UI smoothness compared to Oreo.
OTA updates (bugfixes and new features without a reinstall).
Deep sleep that can last for weeks compared to hours in the previous version.
RSMouse support for controlling a mouse cursor with your right stick
Full Joy-Con and Pro Controller support with analog sticks and rails.
Hori Joy-Con support.
Uses Joy-Con HOS Bluetooth paring data.
Both Android TV and Android Tablet builds.
Reworked fan profiles for quieter operation.
Optimized dock support with resolution scaling.
OTG support including DisplayPort or HDMI output (no power supply necessary).
3rd party dock/hub support including DisplayPort or HDMI output.
Rewritten charging driver to properly support USB-PD.
Optimized touch screen driver.
Easier install via hekate partition tool.
Reworked, simpler, power profiles.
Much improved WiFi driver with less dropouts.
Shield TV remote app support for easy docked control.
Reboot to payload support.
Improved Bluetooth accessory support.
Auto rotation support.
Installing
Follow the tutorial here
Stay in touch
Discord:https://discord.gg/6gWvaASF72
Twitter: https://twitter.com/switchroot_org
Website: https://switchroot.org/
Sources
https://gitlab.com/switchroot/android
https://gitlab.com/switchroot
See manifest repo for build instructions.
Credits
Ave - Handling hosting of OTAs and the switchroot website. Check out her patreon!
CTCaer - Fixing a lot of things in the kernel - charging, dock, touch etc - and adding Android install support for nyx. Donate to his patreon here!
Langerhans - Figuring out the majority of stuff for deep sleep and helping massively with initial bringup.
Steel01 - Maintaining the Shield TV Lineage trees which ours are heavily based on.
Nvidia + Nintendo - ❤
Everyone else who contributed!
Reserved
Amazing! Thanks to all the devs working on this <3
Wooohoo finally here, running since Jan without issues, definetly faster than Oreo, looking forward to reflash now that it is official
Super excited about this. Long time coming!
It's a Great day for the Switch modding scene.
Thank you Switchroot team you are the best.
You guys have made my Switch a ton more useful, thanks for all the work you guys put in! ★＼(^▽^ )♪
Android 10 and Deep Sleep are great to have! Haven't tested the build yet since I won't be free until tomorrow but I'm looking forward to it!
Edit: Forgot to edit it, just chiming in to say that I've been loving it! Thank you so much devs!
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Absolutely fantastic! Thanx a lot for the release
Very exciting day, big thanks to everyone who worked so hard on this! I loved playing with the original Android release, but decided to wait for a version with the kinks worked out, looking forward to diving back in!
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
rac08241988 said:
I can't get my switch to boot into twrp. I used balina to put previous version in but would rather use twrp for familiarities. Is there a guide to installing twrp?
Just follow the guide in post
Click to expand...
Click to collapse
sashka69 said:
Hi there. I'm glad to see it is official now. Can I do a dirty flash via twrp? I have a SD card setup from an unofficial selfmade build from October. Thank you.
Click to expand...
Click to collapse
Dirty flash wont work, you need to wipe and repartition in hekate
bylaws said:
Dirty flash wont work, you need to wipe and repartition in hekate
Click to expand...
Click to collapse
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Fukurou83 said:
Hello! I'm trying to install it but I'm stuck on google voice assistant.
If I tap on "No thanks" it brings me a page back everytime.
Click to expand...
Click to collapse
The Installation Guide's 20th step is "If setup gets stuck on voice detection go back to the wifi config page in the setup and select "Skip for now"".
This should solve your issue!
Wow there it is finally!
Well done!
rac08241988 said:
I did. I unzipped hikati and rom. Just moved everything else. Sd card is class 1 64 gb formatted into fat 32 followed instructions within hikati. First time I tried it said flash successful but wouldn't boot into twrp. Now it just says flashable files not found. Imma start over from scratch see if I can get it. Must be something I missed. I'll see.
Click to expand...
Click to collapse
try redownloading, we updated the zips
bylaws said:
try redownloading, we updated the zips
Click to expand...
Click to collapse
I got it. I don't know what happened but it worked the second time I did it. Sorry for wasting people's time lol I like the improvements alot. So glad lockscreen and battery charging indicator is working properly now.
I'm simply amazed. Thank u so much for all the months of hard work @ANyOne involved!
I've got two questions:
1. If I go for the non-Android TV image, can I control the Switch in the dock with the Joy-Cons wirelessly?
2. If going for the Android TV image, would it support the Google Cast protocoll receiver-sided (meaning I could cast to it)?
Edit: Please let me add a third question:
3. Can Android access the FAT32 partition I'm using in Horizon?
Aka can I continue my SNES savegames in Android's RetroArch by pointing it's directory settings to the same folder on the FAT32 partition I'm using in Horizon's RetroArch for the savegames?
Followed the guide and been testing for a bit, this version is incredibly smooth compared to the previous one, i barely get any lag with a 64GB class 10 card