[CALLING DEVELOPERS] Jolla's Sailfish OS port continuity (GNU/Linux) - Xperia Z General

Hey fellows!
A screenshot of another older phone for attention: https://twitter.com/sledgeSim/status/625235917486338048
yuga's Sailfish OS port was shaping up during past months, by @oleid, but he got carried away by his studies. Now that Sailfish OS UX 2.0 is on the doorstep, is a good time to restart a port! If you're completely new: https://sailfishos.org/hadk
We also just provided LED notification support for Xperia Z, but this needs testing: https://github.com/nemomobile/mce-plugin-libhybris/pull/16
Original porter left all documentation here: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_yuga (including link to automated script) and modem hurdles: http://piratepad.net/hadk-yuga
Pop by to #sailfishos-porters and we'll guide you through if you want to make a build a new Sailfish OS version for your beloved phone, and also make those phonecalls work
Cheers!

Related

Newsmy Carpad NU3001 CM13 ROM

Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.

Discussion : Android 8.1 Oreo Related Development

It's hard to pin down the Android codename in advance thanks to Google's notorious trolling. Remember Key Lime Pie and Milkshake? This time, everyone's first guess turned out to be the right one. Google has named Android 8.0 "Oreo" after the cookies produced by Nabisco.
Most Android names are generic treats like Marshmallow and Nougat. However, this is not the first time Google has worked with a company to use a name brand. KitKat was a surprise announcement in 2013. The agreement between Google and Nestle/Hershey includes some cool limited edition KitKat candy bars, too. It is unclear if there will be similar Android-themed Oreo packaging, but Google must have some manner of agreement allowing it to use the Oreo trademark. The statue does at least look a bit more daring than other recent bugdroid mascots.
There's not much new to report on the features in Oreo—we've been playing with the developer preview for months, after all. You can expect picture-in-picture support for apps, autofill apps, faster boot times, and those god-awful new emoji. Oreo is being rolled out to AOSP today, and updates for the Pixels and recent Nexus devices are in final testing now. You can expect the OTA soon on those devices.
Google has just announced that Android 8.0 Oreo will be uploaded to the Android open Source Project today, and that updates to the newest version of the platform are currently being tested by carriers for the Google Pixel, Nexus 5X, and Nexus 6P. Google says these updates will begin rolling out in phases "soon," along with updates for the Pixel C and Nexus Player.
Google has not clarified when factory images or OTA files will be available for devices at this time.
As a reminder, Android Oreo brings a number of new features to the table, including notification dots, enhanced speed, a brand-new set of emoji , more aggressive battery life management, and [finally] OS-level autofill.
Source : Google, AndroidPolice
Android 8.1 is the next version of the OS, Google app reveals..
Android 8.0 Oreo has only been out for a couple of weeks at this point, and hasn't actually made it to every single supported Nexus and Pixel device out there yet. Not to mention how long it's going to take for it to land on any other phone or tablet.
Even so, maybe you'd like to know what the next version of the OS will be? It's Android 8.1, by the way. This has been revealed by a teardown of the latest iteration of the beta Google app. The SDK used internally by the company to build said app outright says so.
As for the name, it makes most sense for Google to keep using Oreo - it would be a shame to switch from such a well recognized brand so soon, and it's also how it did things last year with 7.0 and 7.1 both being Nougat. If you're wondering when 8.1 will hit, remember that in 2016 Android 7.1 debuted with the Pixels only a couple of months or so after 7.0 updates started going out. So we assume that this year the second-gen Pixels will be the first devices to launch running Android 8.1, when they land in October.
Source : - Google, GSMARENA
Google announces Android 8.1 developer preview, final release planned for December
Google launched the new Pixel phones with Android 8.0, which is what last year's Pixel's have been running since the update. A new version of Oreo is on the way, though, and you can try it right now. Google has launched a developer preview for Android 8.1. As usual, it's supported on recent Google devices and can be installed in two ways.
The system images are available for download now, but that requires an unlocked bootloader. The beta program with automatic OTA updates will be available as well. You can sign up now, but it looks like the switch hasn't been thrown to push out the OTAs just yet. If you want to get on the dev preview, it's compatible with the following devices. The OTA files are available for sideloading, though.
Nexus 5X
Nexus 6P
Pixel C
Pixel
Pixel XL
Pixel 2
Pixel 2 XL
The Android 8.1 preview runs from today until the OS is released, which Google expects to happen in December. Installing the preview should not affect your data, but you never know. Running a developer preview does come with some risk, so make sure you've got your data backed up. Leaving the beta program will result in a device reset as well.
Google has a developer-oriented changelog up. Here's what you can expect in the new version.
Neural networks API: The Neural Networks API (NNAPI) provides apps with hardware acceleration for on-device machine learning operations. The API supports on- device model creation, compilation, and execution.
Notifications: Apps can now only make a notification alert sound once per second. Alert sounds that exceed this rate aren't queued and are lost. This change doesn't affect other aspects of notification behavior and notification messages still post as expected.
Improved targeting for low-RAM devices
Autofill framework updates: custom descriptions that the Android System shows in the autofill save UI, specify a Validator object that your app can use to decide if the Android System should show the autofill save UI, and more.
EditText updates
Programmatic Safe Browsing actions: Devs can control whether an app reports known threats to Safe Browsing, and have the app automatically perform a particular action—such as going back to safety—each time it encounters a URL that Safe Browsing classifies as a known threat.
Video thumbnail extractor: The MediaMetadataRetriever class has a new method, getScaledFrameAtTime(), that finds a frame near a given time position and returns a bitmap with the same aspect ratio as the source frame, but scaled to fit into a rectangle of given width and height.
Shared memory API: Android 8.1 (API level 27) introduces a new SharedMemory class. This class allows you to create, map, and manage anonymous shared memory that can be used by multiple processes or apps.
WallpaperColors API: Adds support for managing wallpaper colors. This feature lets you create a WallpaperColors object from a bitmap, a drawable, or by using the first three most visually representative colors. You can also retrieve details of the first three noticeable colors of a wallpaper.
Fingerprint updates
Source - AndroidPolice, Google
DISCLAIMER
Code:
[LIST]
[*]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.
[*]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.
[/LIST]
List of Android 8.0 / 8.1 Oreo Based Beta / Alpha Rom's
Osprey
1. [ROM]AospExtended ROM V5.2 [OSPREY]
2. [ROM][osprey] Unofficial LineageOS 15.0 by Alberto97
3. [ALPHA] AOSP 8.0.0 r17 [UltraDevs] [OSPREY] [5 OCT Patch]
4. [ROM]crDroid Android 4.0 [OSPREY] [UNOFFICIAL]
5. [ROM]Xenon HD [OSPREY] [UNOFFICIAL]
6. [UNOFFICIAL][OREO]XPerience 12.0.0
7. [ROM][OSPREY]OFFICIAL]Pixel Experience [AOSP]
8. [ROM][osprey] The Android Open Source Project
9.[ROM]CosmicOS 3.0 Chronus for Osprey[UNOFFICIAL]
10.[Osprey][8.0.0][Unofficial] Ground Zero ROMs || Validus [Beta][GZOSP]
11.[Osprey][VoLTE][AOSCP]CypherOS-5.1[UNOFFICIAL]
12.[ROM]LineageOS 15.1 [OSPREY/MERLIN] [UNOFFICIAL]
13.[ROM][Osprey]ResurrectionRemix v6.0.0[UnOfficial]
Merlin
1. AospExtended 5.2 for Moto G Turbo/Merlin!! By Innfinite4evr
2.[ROM][Merlin]ResurrectionRemix v6.0.0[UnOfficial]
3.[ROM][8.0.0] crDroid Android 4.0 [OSPREY/MERLIN] [UNOFFICIAL] By althafvly
4.[ROM][Merlin]OFFICIAL]Pixel Experience [AOSP]
Official OpenGapps for Oreo 8.1 has been released but still it's in Beta​http://opengapps.org/​
TWRP
Osprey
[TWRP][osprey] TWRP for Moto G 2015
Merlin
[TWRP][merlin] TWRP for Moto G Turbo
​
Reviews For the Android 8 / 8.1 Based Alpha Rom's
LOS 15 Osprey Alpha Build
Battery Review - https://forum.xda-developers.com/showpost.php?p=73793250&postcount=381
In - Depth Review - https://forum.xda-developers.com/showpost.php?p=73928613&postcount=499
AospExtended ROM V5.0 [OSPREY] Alpha build
General Review - https://forum.xda-developers.com/showpost.php?p=74008848&postcount=37
In - Depth Review - https://forum.xda-developers.com/showpost.php?p=74097172&postcount=140
AOSP 8.0.0 r17 [UltraDevs] [OSPREY] Alpha build
General Review - https://forum.xda-developers.com/showpost.php?p=74107538&postcount=24
The Android Open Source Project 8.0
General Review - https://forum.xda-developers.com/showpost.php?p=74622199&postcount=32
Battery Review - https://forum.xda-developers.com/showpost.php?p=74640229&postcount=40
[Osprey][8.0.0][Unofficial] Ground Zero ROMs || Validus [Beta][GZOSP]
General Review - https://forum.xda-developers.com/showpost.php?p=74691620&postcount=12
Battery Review - https://forum.xda-developers.com/showpost.php?p=74692903&postcount=13
[ROM][8.1.0_r1] Pixel Experience [AOSP][OSPREY][UNOFFICIAL]
General Review - https://forum.xda-developers.com/showpost.php?p=74845271&postcount=47
rahul9999 said:
Initial manifest for official Lineage 15.0 has been Created today,
So they have started working on this
Source : - Initial manifest for Lineage 15.0
Click to expand...
Click to collapse
That's pretty cool. My guess is that the first Oreo ROM for our osprey is going to be Lineage OS 15.0.
This time arround, Lineage should be the first one, since there is no fiasco like Nougat's two major releases at once (7.0 and 7.1.1). Remember how people used to get CyanogenMod 14.0 internal sources and put them into Nougat 7.0 ROMs for the osprey? Back then I used to love BeanStalk because it was pretty much the most stable Nougat ROM for my osprey. There was a bug with video recording but I was ready to trade new features for video recording.
nicolasmart said:
That's pretty cool. My guess is that the first Oreo ROM for our osprey is going to be Lineage OS 15.0.
This time arround, Lineage should be the first one, since there is no fiasco like Nougat's two major releases at once (7.0 and 7.1.1). Remember how people used to get CyanogenMod 14.0 internal sources and put them into Nougat 7.0 ROMs for the osprey? Back then I used to love BeanStalk because it was pretty much the most stable Nougat ROM for my osprey. There was a bug with video recording but I was ready to trade new features for video recording.
Click to expand...
Click to collapse
I cant wait man. I need my cookie fix.
rahul9999 said:
Initial manifest for official Lineage 15.0 has been Created today,
So they have started working on this
Source : - Initial manifest for Lineage 15.0
Click to expand...
Click to collapse
I'm not a fan of Lineage. I think I'll stick with CAF rom. It's the best I've ever flashed and the longest I've stayed with a rom.
melp57 said:
I'm not a fan of Lineage. I think I'll stick with CAF rom. It's the best I've ever flashed and the longest I've stayed with a rom.
Click to expand...
Click to collapse
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
With the support of Great Developers we should surely get Android Oreo for our device.. Also a CAF Based Rom but it will take a time as usual... Not sure how much time take for PA..
As i can see a work for Lineage 15 is going on very well & i think this would be our first Oreo ROM..
RijuSarkar13 said:
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
Click to expand...
Click to collapse
I've tried aospa but I don't really like it. It's not that stable for me on osprey, the Qualcomm camera doesn't work and I needed another camera app, PACKAGE INSTALLER WAS MISSING!!! I WASN'T ABLE TO INSTALL APKs, even through recovery. I needed to re-install it to make package installer work. Also, it's not that customizable. Not that Default Lineage is but after installing substratum, everything is perfect.
Sticking with LOS 14.1 + Open Gapps + Kali Nethunter until Lineage 15 gets released.
nicolasmart said:
I've tried aospa but I don't really like it. It's not that stable for me on osprey, the Qualcomm camera doesn't work and I needed another camera app, PACKAGE INSTALLER WAS MISSING!!! I WASN'T ABLE TO INSTALL APKs, even through recovery. I needed to re-install it to make package installer work. Also, it's not that customizable. Not that Default Lineage is but after installing substratum, everything is perfect.
Sticking with LOS 14.1 + Open Gapps + Kali Nethunter until Lineage 15 gets released.
Click to expand...
Click to collapse
I launched so many apps with package installer...that's not roms fault...for example I installed nova Google companion from apkmirror and few other apps..not a single problem...Qualcomm camera got better in 7.2.3...though Moto z camera is always better...it has not much customisation and that is it's uniqueness...I always feel I am using a stock Moto so much improved ROM...I just love the aospa...
RijuSarkar13 said:
paranoid android is the best one.......caf roms are always better than los........though old build,you may try cosmic os....it is made by shubham singh and caf based............thats good too........but aospa 7.2.3 works like a charm..........it is my daily driver
Click to expand...
Click to collapse
The CAF rom is updated.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
rahul9999 said:
With the support of Great Developers we should surely get Android Oreo for our device.. Also a CAF Based Rom but it will take a time as usual... Not sure how much time take for PA..
As i can see a work for Lineage 15 is going on very well & i think this would be our first Oreo ROM..
Click to expand...
Click to collapse
Can't thank our Osprey Dev enough! This device is 2 yrs old and still going strong.
melp57 said:
The CAF rom is updated.
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
Can't thank our Osprey Dev enough! This device is 2 yrs old and still going strong.
Click to expand...
Click to collapse
Yes.. All credits goes to Great Dev Like @Alberto97 @ishubhamsingh @ Arcadee & Many more
melp57 said:
The CAF rom is updated..
Click to expand...
Click to collapse
which one is updated? cosmic os?
RijuSarkar13 said:
which one is updated? cosmic os?
Click to expand...
Click to collapse
Sorry, pa
...
Guy's... Thread Subject edited Related to Android Oreo development.. So instead of spamming any other active threads you can post here...
Also please bear in mind Don't ask for ETA for any Android Oreo ROM... It's against XDA Rules..
Our official Lineage Os maintainer @Alberto97 successfully booted Lineage Os 15 ROM on our device while testing..
So guys be patient development is going great & as per this source we will surely get official Lineage Os 15 ROM based on Android 8 Oreo
Poll added related to which Android Oreo Based Rom your waiting for..
rahul9999 said:
Our official Lineage Os maintainer @Alberto97 successfully booted Lineage Os 15 ROM on our device while testing..
So guys be patient development is going great & as per this source we will surely get official Lineage Os 15 ROM based on Android 8 Oreo
Click to expand...
Click to collapse
Love to get my hands on what he flashed!
EDIT: nice poll!
edit: lots of threads out there saying how to flash oreo on any phone, but the fine print says only nexi and pixili.
edit: seems like Lineage by the end of this year which is fantastic. I assume both 14.1 and 15.0 will be running side by side for quite a while.
edit: Added to my sig to help folks fine it.
edit: @rahul9999 you might put in your sig... that's a very easy way to advertise it w/o breaking xda rules or going off track!!! and when was your English ever bad!
KrisM22 said:
Love to get my hands on what he flashed!
EDIT: nice poll!
edit: lots of threads out there saying how to flash oreo on any phone, but the fine print says only nexi and pixili.
edit: seems like Lineage by the end of this year which is fantastic. I assume both 14.1 and 15.0 will be running side by side for quite a while.
edit: Added to my sig to help folks fine it.
edit: @rahul9999 you might put in your sig... that's a very easy way to advertise it w/o breaking xda rules or going off track!!! and when was your English ever bad!
Click to expand...
Click to collapse
Hehe thanks dude... will add this in my Sign sure
I Also want get my hands on what he flashed.. but we have to wait as stable build might take a time to develop... Soon LoS 15

Batik(TWRP)Treble-non Treble Alpha-02-kenzo

BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
why alpha? when can we expect a stable build?
shawon11 said:
why alpha? when can we expect a stable build?
Click to expand...
Click to collapse
Sorry bro but this is not my work I am just sharing good TWRP:good:
Azizbagwan said:
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
Click to expand...
Click to collapse
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
robbayani said:
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
Click to expand...
Click to collapse
Project Treble is the Answer
The reason manufacturers have such a hard time pushing out prompt updates is because of all the work that has to go into getting the operating system to communicate with the hardware.
Traditionally, it worked something like this: the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software–technically referred to as vendor implementation—also had to get updated. That’s a lot of work.
So, starting with Android 8.x (Oreo), Google separated the two. That means the Android OS itself can be updated without having to touch the vendor implementation. That, in turn, can be updated by itself if needed.
To put that in full context, before an update can be pushed out to an Android 7.x (or earlier) device, not only does the Android OS code have to be updated, but so does the low-level hardware code, which is generally maintained by the chip maker. So, for example, if Samsung wants to push an update to one of its phones, it has to wait for Qualcomm (or whoever made the chip) to update its code to work with the new Samsung code. That’s a lot of wheels turning at once, and each one is dependent on the other.
With Android 8.x and beyond, it won’t be like this anymore. Since the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
This should dramatically speed up the update process—in theory, at least. Updating devices will still be in the manufacturer’s hands, and since the first Oreo devices outside of the Google-maintained Pixel line are just now rolling out, we haven’t yet had a chance to fully see this in practice. Hopefully, it actually makes a significant change to the speed in which updates are written and pushed out.
Will My Device Benefit from Project Treble?
Now that’s the million dollar question, right? Unfortunately, the answer isn’t so simple (surely you didn’t expect it to be). That said, here are some facts:
If your device never gets updated to Oreo, it will never get Project Treble. No way around that. Sorry.
If your device does get updated to Oreo, it’s still not required to support Treble—that’s up to the manufacturer.
If you buy a new phone that runs Oreo out of the box, it is required to support Treble out of the box.
In short: Treble support on updated systems is still up to the manufacturers, but new Oreo devices will be required to support Treble moving forward.
So, for example, the Pixel 2 already supports Project Treble. The forthcoming Galaxy S9 will also support Treble out of the box. Google also updated the Pixel 1 to support Treble, but it’s unfortunately it looks like Samsung left it out of the Oreo build for the Galaxy S8.
If you’re curious about your own device, Android Police has a running list of all devices that will get Treble support, as well as a which ones will get updated to Oreo without Treble.
Android OS updates have been a constant point of contention for many years now, so it’s good to see Google finally addressing the issue. With any luck, this will put all Android devices closer to parity with Apple in terms of device updates.

Bliss OS - Pie for PCs (LTS)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
team bliss is pleased to present to you
bliss rom based on Android 9 Pie​
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Notice
- READ: The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible. We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
- Please do not ask for ETA's;
- We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts;
- We encourage users to contribute towards this project, and we're openly accepting applications for others to join Team Bliss
First, a little bit about this project...
Starting in Android Pie, Bliss OS will be taking a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, we have reworked a good majority of the commits from Android-x86 Project and Bliss OS's Oreo release, and packaged it up so that it can work a bit more dynamically. The result was something we could integrate into a single source, along side normal device builds. This is much like our Treble builds that use PHH's Treble methods, and Intel's Project Celadon's EFI builds. Both of which are also buildable directly from the BlissRoms-x86 source: https://github.com/BlissRoms-x86/manifest
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well. For now though, you can stay tuned to this thread for updates on all that.
ROM Porting Details:
Like we mentioned already, things this round will be done a bit differently using the patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, https://github.com/Android-PC and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
https://github.com/Android-PC/platform_build/commit/eda2e16b0018c5554f98acaa708f8200a171f206
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so
We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.
AIO Thread​
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
BlissRoms-x86
https://github.com/BlissRoms-x86
Bliss' Android-PC Project
https://github.com/Android-PC
Open Gapps Project
!!CONSIDER THESE AS DEVELOPMENT BUILDS FOR NOW!!
These are not to be considered stable in any way shape or form. Please continue at your own risk. Developers and experienced users suggested
This release is a work in progress, and will take community effort in order to iron out all the bugs.
There are no IPTS builds for the Surface devices yet, and there won't be until I am able to fix my SurfaceBook. Sorry :'(
Read the documentation first:
https://docs.blissos.org
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with available installation options before attempting to install the OS.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Download the ISO file
Use Rufus or similar to burn to USB drive
Disable Secure Boot, Bitlocker, and any other boot security
Boot into the USB drive.
Run Bliss OS in Live mode to test things out, if all is well, continue to next step
Boot into the USB drive, and choose Bliss OS Install
Pick your poison, but please do this with caution, making sure to fully understand what you are doing.
These are beta builds, so please take that into consideration when reporting issues. We want all the info possible
Packages Manager sometimes crashes the system. This will require you to wait, then open a terminal and use $ su && svc wifi disable , and when it comes back, $ su && svc wifi enable
Screenshots aren't working yet
Video playback does not work right as of yet
Sound issues on many machines still
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using Bliss! And have as always: #StayBlissful​
XDA:DevDB Information
Bliss OS - Pie for PCs (development Beta Preview), ROM for the ROM Central
Contributors
electrikjesus, ElfinJNoty
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: x86 Arch
Version Information
Status: Beta
Current Beta Version: 20181018
Beta Release Date: 2018-10-18
Created 2018-10-19
Last Updated 2019-07-23
The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates
Build Types Explained:
Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux)
-gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
Q: OK, So I have a BlahBlah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io
Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Does not work on Asus t101ha (cherrytrail)
wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable
electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?
electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.
electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install
Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?

[ROM] [7.1.2] Mik-el Android for Takee 1

Device and Project Presentation
In 2015 the Chinese company EStar launches on the market the Takee 1. An octa-core smartphone with an astonishing Holographic 3D technology developed by the german Seereal.
Despite the cutting-edge hardware, a low price and the big innovations in the field of 3D and AirTouch... the phone does not receive the big success it deserved, Estar closes down and the last official software update dates back to 2015, leaving the whole system stuck to Android 4.2.
But today, 5 years after the last update and the closure of the company, I continue what the far-sighted EStar was doing, studying 3D technologies and releasing a new Android 7 Software Update.
I had to face many difficulties but...
making an Android 7 ROM from just an Android 4.2 base is now possible!
Let's go guys!
Presentation Image
https://imgur.com/Be7YKsg
Other screenshots
https://imgur.com/a/RRyUNL7
Youtube video
The last ROM is v. 3.0
Everything works except the Cameras. 3D partially works.
Changelog (click to show history of working/not working components)
v2.0
Magisk improvements
v1.2
Bluetooth Now Working
Full Holographic 3D and AirTouch support - in Development
v1.1
Usability
WiFi module - Working
Phone module - Working
Audio - Working
Camera - Working (you have to apply a fix)
Fm radio - Working
USB debugging - Working
Bluetooth - Not working but I'm working on a fix!
v1.0
First release that can boot, no need to download it.
Theming
Transition from RidonOS to Mik-el Android:
Removed most of the references to RidonOS and Micromax 311
Mik-el bootscreen (boots faster)
Mik-el wallpaper
Apps
Replaced Ridon launcher with a lighweight Open Source Pixel Launcher
Removed Old Google apps, size of the Rom reduced
Added F-Droid, Open Source alternative to Google play store
Added an Open Source alternative to Youtube
Added 52kb app to exchange files on wifi between smartphone and PC
Added OpenCamera, best android camera app (and it's Open Source)
Added High-quality Audio recorder with noise reduction
System and Performance
Enabled USB Debugging by default
Adjusted dpi value: screen is more readable and system is more reactive!
First step to port the Bit Cauldron 3D Audio Technology included in the Takee stock Rom: Removed loudsound patch to avoid possible future conflicts
Mik-el fixes to extend the life of your device
system warns you when you reach high temperatures
system doesn't write on the phone memory over and over again (The original Takee 1 stock rom is based on Android 4.2 and trimming was introduced starting from Android 4.3 only)
you can install apps directly on external SD card - starting from v. 1.2
Support me:
Telegram Channel here
Instagram here
Youtube here
Paypal here
XDA:DevDB Information
Mik-el Android 7 for EStar Takee 1
Contributors
Mik-el
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.67
Version Information
Status: Stable with some bugs
Created 2019-11-02
Last Updated 2021-10-16
TWRP by Mik-el - Download and Instructions
To flash an Android 7 Rom You must use an updated TWRP custom recovery!
I made a new TWRP for Takee 1 and I released 2 versions
TWRP 3.1.1. here
TWRP 3.1.1 with OTG support here
Instructions and Screenshots are included in the previous links.
Rom Download
Free Download, Virus Free (just use "slow download")
v 1.1-------------> here
v 1.2-------------> here
v 2.0-------------> here (10th March 2021)
v 2.0.1 Bundle*---> here (9th April 2021)
v 3.0 (3D) and Bundle*--->here (16th October 2021)
* = Bundle includes= ROM + Optional Stuff among: Google Apps, SuperSU root and Magisk!
Google Apps
Google Apps 2021. Most lightweight version possible. We love privacy, so they're optional.
I made a flashable .zip to install them from TWRP recovery but it seems not working for me, you can test it and let me know.
Magisk or Root? What do you want?
I want Magisk = Rom 2.0.1 is pre-patched for Magisk (boot.img). After booting the ROM just install the Magisk Canary apk. (Apk included in the 2.0.1 bundle you have just downloaded).
I want Root =before installing the 2.0.1 ROM, take the "boot_unrooted.img" file inside the 2.0.1 Bundle you just downloaded. rename this file in "boot.img" and replace it inside the .zip file of the ROM. Now you can flash the ROM and then flash SuperSU through recovery
Rom Integrity Infos
Code:
Name: Mik-el_Android_for_Takee_v1.1.zip
Date: 27/12/2020
Size: 602 MB (631,352,946 bytes)
--------
SHA-1: 260999abe54d3ae473272a4002cc9cef2ea93e60
MD5: c2fb20469f11a2f6c16c0479a8c157f6
CRC32: 8436c496
General Advices about Takee 1
Don't use the original charger, probably you have a good one but it gave problems to most of the users
Don't try to flash this rom with SP Flash tool, you can't, follow the instruction I'm providing here
Instructions to flash the ROM:
Backup 3D calibration files or you'll lose the 3D effect forever. Internal and External storage -> "Android" folder -> "HolographyProfile" file and "matrix" file. To know more about 3D calibration, read this! Also, backup your important data, as always;
Boot your Stock Rom and check if you still have these (or other) Air Touch games in your phone storage.
Fruit Ninja (it looks like this)
Sector Strike (it looks like this)
This game (it looks like this)
This other game (it looks like this)
Shadow Snake (it looks like this)
Tunnel Trouble (it looks like this)
If the answer is YES, go to step 3. Otherwise, go to step 4.
Spoiler: YES, I still have Air Touch Games
These Air Touch games can't be downloaded anymore! The Takee 1 3D store is offline! Now you can help the Takee community preserving these games for the future. You just need 1 minute. Download the ApkExtractor app (2.4 MB), save the games on your external SD card and upload them somewhere on the web! Then, you can flash the new Rom.
Download and Install the updated TWRP custom recovery made by me, if you haven't done it yet:
TWRP 3.1.1. here
TWRP 3.1.1 with OTG support here
Download my Rom, it's a .zip file;
Copy the Rom file on your MicroSD;
Once you have installed the recovery you can boot into it;
"Wipe" -> "Swipe to Factory Reset";
"Install" -> select the .zip file for the Rom -> "Swipe to flash"
"Reboot" -> "System"
A tip to Improve Rom Performance
Use the Rom for a few minutes and see how it performs. After that, open the fstrim app included in the Rom and use it to trim the internal storage of you device. This will be the first trim you'll phone has received in 6 years, since 2015 ! It took me 3 trims in a row to fully trim my /data partition. Now see how much more responsive the phone has become!
How to solve Camera Bug for ROM version 1.1
Open the "Reboot Manager" app and do a quick/warm reboot, now your cameras work!
Spoiler: Click here for an Alternative Method
Go to Settings
Go to developer options
Activate "extended reboot menu"
When you want to use the camera:
Long press power button and select "reboot" - you will be asked, which type of reboot you want to do
Select "warm reboot"
Camera is now working!
Definitive solution
Will be solved in the next release.
Help me with testing and support me to get an invincible Rom!
Next updates
Full 3D and Airtouch Support
Camera ready at boot without warm reboot
"Mik-el Rom Updater" to update the system with one touch
Bluetooth Fix
whatever you want!
Support me
Leave a 5 stars review and a positive review using the panel on XDA.
Use these links to support me:
Telegram Channel here
Instagram here
Youtube here
Paypal here
Credits
Mik-el
a big hug to @io2345 for:
helping me with testing and fixes
donating 10 euros for the development
for exchanging almost 150 mails with me to bring this project to life!
@YuriRM
for having collected information and having made a detailed list of Hardware specs from phones similar to the Takee 1
for his continuous effort to bring back interest in this device on XDA and Telegram
@kano3d
for donating 4 euros for generic 3D development
other members of the Takee 1 community (@giotogo, @Talwarmirza, @snapss , @Hunter_07)
an unknown artist for the Mik-el Android wallpaper
Reserved for future Updates.
P.S. Ignore the very next posts below: intially the community and I were talking about other things (problems faced during development), and NOW that the Rom is ready I updated this same thread, to don't make a new one. Now, Enjoy
ROM for Holographic 3D smartphone
Thanks! This ROM will bring a fresh air and new lease of life to EStar TAKEE 1, the first ever Holographic 3D smartphone launched in 2015 at an affordable price ($100-150). Nobody will need to buy an extremely expensive RED Hydrogen One at $1200.
The 3D community will rejoice!
The amazing resources of PHEREO are available to all lovers of 3D Stereo Images and Photos.
http://phereo.com/
Select an image and click Wiggle... if you do not have a smartphone with 3D display.
My advice is to install the PhereoRoll3D app too!
https://github.com/JackDesBwa/PhereoRoll3D
NewPipe - to download 3D videos from YouTube
https://github.com/TeamNewPipe/NewPipe/
INVIDIOUS - to download 3D videos from YouTube, VEVO, etc.
https://www.invidio.us/
Plenty of resources for 3D lovers that justify buying a device with 3D display.
interesting. this phone is still good.....
Anyone with ViperOS development experience?
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
More than ViperOS developers we need someone that has experience with rom porting.
I made more than 7 releases for this ROM and @io2345 tested them all!
We solved the failed installation problem, now we just need to solve the bootloop.
The porting process is OK, the updater-script file is OK, file permissions are OK...
I don't know where the problem could be!
Next time I'll use another porting guide. (there are only 2 guides and one didn't work since now)
Instead of ViperOS I'll also use a LineageOS rom as port rom.
Let's see what I can get.
(Stay tuned subscribing to this thread and collaborating with us, cheers)
Greek & Indian ROM ports by Jpower7 (A310 kernel) and blacklisted.rock (A311 kernel)
My suggestion is to try other 3.4.67 ports for EStar Takee 1.
ROM ports by Jpower73 (A310 kernel) - Greece
He maintains working links for his ROMs. Therefore, you can also ask his help.
(Android Ice Cold Project) for Coolpad F1/MmxA310-Α311/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/android-ice-cold-project-coolpad-f1-t3802656
HTC SENSE 10 for Coolpad F1-A310-Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/htc-sense-10-coolpad-f1-a310-canvas-t3952369
Poly Os for Coolpad F1/Micromax Canvas Nitro A310/Himax Polymer Octa by Jpower73
https://forum.xda-developers.com/a310/development/poly-os-coolpad-f1-micromax-canvas-t3801223
ROM ports by blacklisted.rock (A311 kernel) - India
The developer does not use his device anymore. His phone is over 5 years old and the battery is malfunctioning.
[BUGLESS][7.1.2]Ridon OS for A310/A311/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/bugless-ridon-os-a310-a311-coolpad-f1-t3779279
[ROM][FINAL]Resurrection Remix OS 5.8.5 V4.0 for A311/A310/Coolpad F1/Himax Polymer by blacklisted.rock
https://forum.xda-developers.com/a310/development/rom-resurrection-remix-os-5-8-5-v4-0-t3786640
But you can look for other ROMs here
https://forum.xda-developers.com/a310/development
List of TAKEE 1 clones for parts by YuriRM
https://forum.xda-developers.com/showpost.php?p=74386084&postcount=1199
EStar Takee 1 - list of components
http://deviceinfohw.ru/devices/inde...=cpu0&brand=brand0&filter=takee&submit=Search
HIMAX POLYMER - 10 shared components with EStar Takee 1
Back CAMERA and Front CAMERA (sunny_imx135_mipi_raw and ov5648_mipi_raw), LENS, ALSPS, one part in two of CHARGER (fan5405), PMIC, WIFI and two parts in four of OTHERS (kd_camera_hw and dummy_eeprom) and RAM.
http://deviceinfohw.ru/devices/item.php?item=1083
Micromax A311 \ A315 \ A316 - just 1 shared component with EStar Takee 1
Back CAMERA
http://deviceinfohw.ru/devices/item.php?item=4999 (A315)
http://deviceinfohw.ru/devices/item.php?item=3526 (A316)
There is no data for Micromax A311 and A310
http://deviceinfohw.ru/devices/inde...m0&brand=brand0&filter=Micromax&submit=Search
I have requested to upload the list of components of Micromax A311 and A310 to the Device Info HW database
Android 4.4.2 KitKat kernel - BQ Aquaris E5 FHD
Official source code for BQ Aquaris E5 FHD
https://github.com/bq/aquaris-E5FHD
Have you acquired knowledge enough for including specific drivers of EStar Takee 1 into this Android 4.4.2 KitKat kernel of BQ Aquaris E5 FHD?
You will get a much better kernel (3.4.67) than luckasfb.
Instructions
Building custom kernels for Android devices
https://source.android.com/setup/build/building-kernels
SavageMessiahZine - Russian forum of Android kernels and assembly instructions
Development of kernels and firmware for devices on the MTK platform � | Self-compiled kernel from source � | Instructions for building ANDROID from sources. � | Theme on assembling the source code MTK on china-iphone | Build TWRP for Qualcomm platform �
https://www.savagemessiahzine.com/forum/index.php?showtopic=583114
Guidance from LordArcadius (GitHub and Telegram) and nathanchance (XDA)
Compiling Android Kernel for your own device #67
https://github.com/ILUGD/talks/issues/67
XDA Reference guide:- https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Help and support Telegram group:- http://t.me/LinuxKernelChat
Upstreaming guide:- https://forum.xda-developers.com/an...rence-how-to-upstream-android-kernel-t3626913
Toolchain:-
GCC 4.9 for 64 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
GCC 4.9 for 32 bit:- https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/
My Telegram username:- @LordArcadius
GPIO pin numbers in the Circuit Board of EStar Takee 1
I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.
@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.
This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.
It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.
Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361
The video below shows how to open a device and find the Circuit Board ID number.
However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.
How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA
How to fix a bootloop after installing a Custom ROM like Viper OS
io2345 said:
Anyone with ViperOS development experience?
Click to expand...
Click to collapse
@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?
Have you watched this video by the clever german guy, Christoph Zahradnik ?
His Viper ROM is used in this explanation... Viper SC2_5.2.1.zip ?
How to fix a bootloop after installing a Custom ROM like Viper OS (07/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=cgYXy2XC1SM
Below find what happened on the previous day.
HTC Sensation (Snapdragon S3) and Viper ROM - installing a Custom ROM and entering a bootloop (06/03/2015)
By Christoph Zahradnik
https://www.youtube.com/watch?v=-Snab4bsnzQ
YuriRM said:
I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.
Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.
However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.
That info is included in the kernel source code of BQ Aquaris E5 FHD.
@giotogo can you find this information inside your EStar Takee 1 device, please?
Circuit Board ID number
GPIO pin numbers of camera sensors in the Circuit Board
Take detailed photos of internal components
Take detailed photos of internal numbers printed in the motherboard.
This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.
It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.
Bug in power for cameras GPIO pins in codegen - EStar Takee 1
https://forum.xda-developers.com/showpost.php?p=79024675&postcount=1361
The video below shows how to open a device and find the Circuit Board ID number.
However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.
How to Find and download Firmware file for chinese tablets
https://www.youtube.com/watch?v=XZqLoxpbUSA
Click to expand...
Click to collapse
Here is photos. i hope, you find what you want
https://ibb.co/3Nc72LG
https://ibb.co/NZpGbPm
https://ibb.co/Sf2bnL6
https://ibb.co/ygg1jWq
https://ibb.co/0sRmXKy
https://ibb.co/vqRcg8P
YuriRM said:
@io2345 how are you doing? It has been a long time since we last talked.
I may have found a solution for the bootloop of the Viper ROM ported by @Mik-el.
Can you test this method, please?
Yurim, I'll try my best to get it done the next weeks. Currently time is a rare factor...
As far as I know, the device of Mik-el is working now (more or less). So it might be a good idea to let him try this method himself.
Click to expand...
Click to collapse
Found the time today and tried the method via fastboot. Sadly to say, it doesn't change anything. Phone keeps bootlooping.
@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards
@io2345 @giotogo
I'm chatting with @blacklisted.rock on telegram. He said he'll send me a better porting guide.
Me and @YuriRM have already chosen a new and better rom to use as port rom.
The failed installation/ updater-binary errors were already solved in my last viperOS port.
Hopefully this time we'll get a booting Android 7 rom.
Regards
{Mod edit: Quoted post has been deleted}
why you need this damned phone?
Hi everyone, I am also the owner of takee1.
I haven't used it for a long time, but when I saw that someone was doing something to bring it back to life, it gave me hope.
I would be interested in updating it with a more current rom, since 4.2 is no longer compatible with anything!
I hope it will be possible soon.
These Chinese continually churn out new models, but never firmware updates!....shamefull!
June 2020 Updates: Rom ported! Now we need a recovery!
June 2020 Updates: Rom ported! Now we need a recovery!
Guys, I've really faced a lot of problems when trying to port this rom:
1) I had to wait 5 months to receive a working battery from China, thank you Corona Virus...
2) university... XD
3) porting guides on the web suck, I had to contact many people and study many articles and video guides... until I had to make my own porting guide...
4) some tools to extract boot.img files extract .img files, but with a wrong structure!! (and I discovered this just recently!)
5) I had to change the port rom, now I'm not using a ViperOS rom, but a RidonOS rom from a Micromax device much more similar to Takee 1 (more than 90%of the hardware is identical)
6) I want to thank you @io2345 for helping me to test over 10 roms!! We had to exchange almost 100 mails to bring you a new and updated Rom!!
Anyway after all this FREE effort I think that I finally got a working Rom !! (correctly ported!!)
But we dhave another problem now...
We discovered that the custom recovery we use on Takee 1 (twrp 2.8.0.0. developed by @luckasfb ) is too old to support Android 7! We need a new custom recovery, probably a twrp 3.0 or above.
I've already researched new material and guides on the web. I found a guide that seems to clearly explain how to port a custom recovery to any device.
The process is simple, it consist in the extraction of the recovery from an Android kitchen in Linux, the rest is about replacing files.
Is this the end, or not?
Anyway the process is long and boring...
I'm quite busy with exams, life a few other projects...
I don't know if continuing this project is convenient for me at this point...
If someone wants to help me and @io2345 please leave a message hereunder, I'll leave you links and infos about the recovery porting.
Cheers!
A reward of 20 euro is awaiting your delivery of a fully working Android 7 ROM + custom recovery.
I expect @io2345 to reward you as well:
Regarding TWRP-3.1 custom recoveries for EStar Takee 1, I did some porting attemps from 5-19 November 2017.
https://forum.xda-developers.com/showpost.php?p=74410087&postcount=1201
https://forum.xda-developers.com/showpost.php?p=74434705&postcount=1202
https://forum.xda-developers.com/showpost.php?p=74482513&postcount=1203
https://forum.xda-developers.com/showpost.php?p=74488944&postcount=1205
https://forum.xda-developers.com/showpost.php?p=74540282&postcount=1206
https://forum.xda-developers.com/showpost.php?p=74564282&postcount=1207
TWRP for BQ Aquaris E5FHD
https://twrp.me/bq/bqaquarise5fhd.html
Current version
twrp-3.4.0-0-vegetafhd.img

Categories

Resources