Database Users

[ROM][A500 & A501] Android 4.4.4 (OmniROM unofficial)

Freshly built Android 4.4.4 ROM based on Omnirom KitKat !
The Team 'IconiaHD' is proud to present a new ROM for your Acer A500 or A501 tablet.
This small team is composed of:
- HenrikE: A200 owner, responsible for an unofficial CM-10.2 build for the A200
- Doume: A200 owner, experienced linux developer
- macia10: A501 owner, tester
{
"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"
}
This is essentially the same rom as we published for the A200 here: http://forum.xda-developers.com/showthread.php?t=2693179 and here: http://www.acertabletforum.com/forum/acer-a200-roms/10043-rom-a200-omnirom-kitkat-4-4-2-a.html
We have now modified our sources to support also the A500!
Why Omnirom, and not Cyanogenmod ?
Google , through AOSP repository, has dropped support for the Tegra 2 platform. The Tegra 2 does not support the 'neon' instruction set, and more importantly relies on a set of old (ICS) proprietary hardware libraries. AOSP has dropped support for both non-neon devices and the older hardware libraries.
Cyanogenmod has decided to follow AOSP on this and has dropped Tegra 2 support since CM-10.2. With CM-10.2 the differences were not yet very big and could be overcome. But with CM-11 it has become an unreasonably large effort to add Tegra 2 support.
Only Omnirom, for now, has included the forward-ported code in its repository to support machines like Acer A500
How to install
Recovery
To flash this rom, it's necessary to have a recent recovery (at least CWM 6.0.4.4 or TWRP 2.6.3.1) having Selinux capabilities.
Otherwise the flash operation fails with status 0 or status 7. There are also some problems installing GApps with Thor's recovery v.1.8.1.
We recommend using CWM 6.0.4.5 by nelsontky: http://forum.xda-developers.com/showthread.php?t=2583710
Flashing
Boot in recovery mode to flash the KitKat Rom.
First, don't forget to execute a 'Wipe Data/Factory reset'
Flash the KitKat Rom
Flash the Minimal Gapps
Do a 'wipe cache partition'
Flash the SuperSU zip file if you need it
Flash the Netflix fix if you need it
And reboot System !
Be patient on first boot... There's a lot of background work to do, before coming to the 'Welcome' screen. Don't worry if you are stuck with a black screen for several minutes. Next boot will be much faster.
After first configuration, it's recommended to reboot the tablet to avoid some unstabilities after 1st boot.
Enjoy KitKat !
Downloads
Download build 8, 2015-02-10, from here:
NOTE: This is an untested build! If you try it, please report back on how it runs! The A501 version probably has the same stability problems as earlier builds, but please feel free to test it. It's at least possible that some update of the OmniROM sources has helped.
A500: omni-4.4.4-20150210-a500-IconiaHD.zip
A501: omni-4.4.4-20150210-a501-IconiaHD.zip
(Build 7 was for A200 only)
Download build 6, 2014-07-14, from here:
Primary A500: omni-4.4.4-20140714-a500-IconiaHD.zip MD5: c5fcabf327c390f5c4ef5495edda616c
Mirror A500: omni-4.4.4-20140714-a500-IconiaHD.zip
- fixed Plex video streaming (reverted to 4.4.2 version of Http Live Streaming)
- sync with OmniROM repos
- network location works
This build is A500 only since the issues with the A501 version are not yet solved.
Download build 5, 2014-06-23, from here:
Primary A500: omni-4.4.4-20140623-a500-IconiaHD.zip MD5: 7d6b17f7dc9027371a56f04b9377efe9
Mirror A500: omni-4.4.4-20140623-a500-IconiaHD.zip
- updated to Android 4.4.4
- sync with OmniROM repos
- permanent Netflix fix from Asus TF101 included
Unfortunately we can't release the A501 version yet because we are struggling with serious stability problems related to the 3g driver.
Download build 4, 2014-04-29, from here:
Updated! If you downloaded build 4 with an older date, please download again!
Primary A500: omni-4.4.2-20140429-a500-IconiaHD.zip
Mirror A500: omni-4.4.2-20140429-a500-IconiaHD.zip
Primary A501: omni-4.4.2-20140429-a501-IconiaHD.zip MD5: 898feec518b2fb60e1a551208f318a7f
Mirror A501: omni-4.4.2-20140429-a501-IconiaHD.zip
Changelog
- First release for A501, includes MBM HAL to support GPS and 3g
- Fixed network location provider
- Fixed boot animation
- Removed apps Movie Studio, Voice Dialer, OpenDelta
- Sync with OmniROM repos
Download build 3, 2014-04-04, from here:
omni-4.4.2-20140404-a500-IconiaHD.zip
Changelog
- First release for A500
Build 1&2 were for A200 only.
GApps are here:
http://forum.xda-developers.com/showthread.php?t=2397942
For the A200 the Pico package is the only one that is small enough so we generally recommend that. The A500 has more space in the system partition and should be able to use the larger packages as well.
SuperSU is here: (needed only if you wish to have a full rooted access)
SuperSU is needed for root, get the latest CWM flashable zip from here:
[2014.02.06] SuperSU v1.93 - xda-developers
Netflix fix for builds 1-4 (not needed for build 5) is here: netflixfix.zip
Flash in recovery. It will just copy this simple script to init.d. It is run during boot and changes a setting in the Netflix configuration to use a player backend that works with the Tegra 2. This is a workaround for a bug in Netflix that makes it choose a video player backend that is incompatible with the Tegra 2. The config file is created the first time Netflix is started, so the very first time you start Netflix it will force close. After that, reboot, and then Netflix should work.
Remember : in all cases, it's a good idea to make a backup before installing!
We're not responsible, in any way, if you brick your tablet!
Big thanks to:
- the Omnirom team
- pjsports for the A500 JB kernel and device tree
- nelsontky for building the recovery
- and everyone else that has been working on the Iconia A500 / A200!
The kernel, and the device tree are available at GitHub: IconiaHD Github

Known issues:
All builds
Noise in audio playback, caused by a too low default minimum CPU frequency. Solved by increasing minimum frequency to 312 MHz.
-In Settings / About tablet, tap build number 7 times until you get a message "you are now a developer". This enables the performance menu.
-In settings / Performance, increase minimum cpu frequency to 312 MHz. Also tick "set on boot" to make it permanent.
Build 6
General
-Default sound recorder app is included but the icon does not show up
-A501 version is unusable because of random reboots
Incompatible apps
-?
Notes
-XBMC should work if you install this version: http://www.mediafire.com/download/0cg8j1dg994gdu6/xbmcapp-armeabi-v7a-debug-2013-09-06.apk (found by user SDBerndt at acertabletforum, thanks!)
Build 5
General
-Default sound recorder app is included but the icon does not show up
-A501 version is unusable because of random reboots
Incompatible apps
-?
Notes
-XBMC should work if you install this version: http://www.mediafire.com/download/0cg8j1dg994gdu6/xbmcapp-armeabi-v7a-debug-2013-09-06.apk (found by user SDBerndt at acertabletforum, thanks!)
Build 4
General
-Default sound recorder app is included but the icon does not show up
Incompatible apps
-?
Notes
-XBMC should work if you install this version: http://www.mediafire.com/download/0cg8j1dg994gdu6/xbmcapp-armeabi-v7a-debug-2013-09-06.apk (found by user SDBerndt at acertabletforum, thanks!)
-Netflix needs a workaround to run, see first post
Build 3
General
-Network Location Provider does not work
-Default sound recorder app is included but the icon does not show up
-The boot animation stops after few seconds, instead of looping until boot is completed
Incompatible apps
-Movie Studio (built in)
Notes
-XBMC should work if you install this version: http://www.mediafire.com/download/0cg8j1dg994gdu6/xbmcapp-armeabi-v7a-debug-2013-09-06.apk (found by user SDBerndt at acertabletforum, thanks!)
-Netflix needs a workaround to run, see first post
Build 2
A200 only
Build 1
A200 only

I'd really prefer to see someone port a clean working copy of CyanogenMod 11 to this device, personally. the TegraOwners team already has a working port of OmniRom on the A500, which is a little laggy, but otherwise fully functional(including netflix, sound recorder, etc.)

kronflux said:
I'd really prefer to see someone port a clean working copy of CyanogenMod 11 to this device, personally. the TegraOwners team already has a working port of OmniRom on the A500, which is a little laggy, but otherwise fully functional(including netflix, sound recorder, etc.)
Click to expand...
Click to collapse
Well then why not try doing it yourself?
The main idea with this rom is to provide an open source alternative for the A500. Not everyone appreciates the closed source policy at the "other forum".

sorry, I sort of worded my post a little harshly and it came out wrong.
I'm actually plenty happy to see an alternative to their roms, and to see that someone is working on the A500 at all.
I meant to say that although it's nice to see, I would personally rather see someone try to port it(even if it's a failed attempt, and post their results so others can try and help out), even though it's a lot of work and a lot harder than AOSP at the moment.
Unfortunately I don't have the knowledge or skills to get any rom working on any device. I've even tried compiling roms before, and failed. Maybe someday!

kronflux said:
sorry, I sort of worded my post a little harshly and it came out wrong.
I'm actually plenty happy to see an alternative to their roms, and to see that someone is working on the A500 at all.
I meant to say that although it's nice to see, I would personally rather see someone try to port it(even if it's a failed attempt, and post their results so others can try and help out), even though it's a lot of work and a lot harder than AOSP at the moment.
Unfortunately I don't have the knowledge or skills to get any rom working on any device. I've even tried compiling roms before, and failed. Maybe someday!
Click to expand...
Click to collapse
Ok no problem. We actually did try to build CM first. But we could never get it to display the user interface because of the missing support for our graphics libraries. When we realized how big the effort would be to get it working, and that support was already available in OmniROM, we switched. I don't know about Thor, but I'm guessing his reason for switching to omni were similar.
Our sources for cm11 are on github, in branch "cm11" and only in the a200 device tree. It's a fair bit behind the OmniROM version now though. It would be better to take the omnirom branch and modify it back to CM format. The differences between CM and Omni device trees are not very big.
Edit: I should add that the challenging part would be to modify the CM android_frameworks_av and android_frameworks_native packages to add support for the tegra2 libraries. There alse seems to be a quite new bug in the CM build system that makes it compile in neon instructions even when it shouldn't.

Prefer anything over CM, thanks! I'll have to reroot since I upgraded to the latest version of ICS. I'll report back any issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Henrik & the team, many thanks for your efforts. I never thought Kitkat would ever reach the shores of the A500. I thought all Rom support had all but ended.
Sent from my HTC One X using Tapatalk

Nice work, I thought for sure that we would never see 4.4 on an A500. I have it flashed and running. I tried Netflix and it force closes. Also the video recording doesn't work.

Robert417919 said:
Nice work, I thought for sure that we would never see 4.4 on an A500. I have it flashed and running. I tried Netflix and it force closes. Also the video recording doesn't work.
Click to expand...
Click to collapse
Thanks for the report! Which app did you use to test video recording?

I used the stock app.

Wow KK! Time to dig out my old A500

Is this overclocked?
Sent from my LG-P769 using xda app-developers app

kennyb6 said:
Is this overclocked?
Click to expand...
Click to collapse
Yes, overclocking is included. You just have to enable it in the developer options.

I found a workaround for Netflix here: https://github.com/CyanogenMod/android_device_hardkernel_odroidu2/blob/cm-10.2/conf/98netflix
It seems to work also on this rom, it displays the interface now instead of just closing. But nobody in the team has a Netflix account so we haven't been able to get further than that. I made a simple flashable zip to install the fix. Simply flash it in the recovery. It will just copy one file, and not touch anything else. The download link is in the first post.

Flashed and it worked. I was able to stream and all good. Awesome!
HenrikE said:
I found a workaround for Netflix here: https://github.com/CyanogenMod/android_device_hardkernel_odroidu2/blob/cm-10.2/conf/98netflix
It seems to work also on this rom, it displays the interface now instead of just closing. But nobody in the team has a Netflix account so we haven't been able to get further than that. I made a simple flashable zip to install the fix. Simply flash it in the recovery. It will just copy one file, and not touch anything else. The download link is in the first post.
Click to expand...
Click to collapse

USB Device Not Recognized
Hey everyone,
Sorry if this is a dumb question... I just picked up an A500 tonight, and can't get the USB drivers to work. Specifically, when I plug in the cable I get "USB Device Not Recognized". As a result, I can't get into boot loader mode, etc. I downloaded the Acer driivers, the Universal Android Drivers, etc, and it does the same for all of them. Any ideas?
Thanks!
Mandy

Dalvik_Cache said:
Hey everyone,
Sorry if this is a dumb question... I just picked up an A500 tonight, and can't get the USB drivers to work. Specifically, when I plug in the cable I get "USB Device Not Recognized". As a result, I can't get into boot loader mode, etc. I downloaded the Acer driivers, the Universal Android Drivers, etc, and it does the same for all of them. Any ideas?
Thanks!
Mandy
Click to expand...
Click to collapse
Maybe a faulty usb cable?

macia10 said:
Maybe a faulty usb cable?
Click to expand...
Click to collapse
The for the idea. I've tried a few. I just tried a new PC too. Think maybe it's the tablet...
Sent from my A500 using Tapatalk

Dalvik_Cache said:
The for the idea. I've tried a few. I just tried a new PC too. Think maybe it's the tablet...
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Please try to download those drivers and try:
http://global-download.acer.com/GDF...NIA A&Step3=A500&OS=ALL&LC=en&BC=ACER&SC=PA_6
And on what rom are you currently?

[ROM][7.1.2][OFFICIAL] Team OctOS Oct-N [WEEKLIES][cancro]

{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-N.​
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -​
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.2
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Donate to OctOS Development (PayPal)
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
Oct OS, ROM for the Xiaomi Mi 3
Contributors
aniket.lamba, manfromgta
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A custom recovery (TWRP preferrable),ROM and Gapps zip file,knowledge on how to flash zip files.
Based On: Lineage
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2017-04-29

OctOS 6.0.1
Team OctOs presents Oct-M.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -​
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes
Q: What code is Oct-M based on?
A: Starting with Oct-M, we've rebased OctOs on Aosp code.
Q: What happened to CM?
A: Octos was originally formed as an AOSP source rom. We have returned to those roots.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file, and grab your favourite gapps package
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
* Weekly Builds
* Release Builds
* Gapps 6.0 Mini
​
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock kernel.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
A Special thanks to @audahadi for his device sources.
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Follow Us at the various websites below!
Kernel source - https://github.com/kernel-hut/android_kernel_xiaomi_cancro
Device - https://github.com/audahadi/android_device_xiaomi_cancro
Vendor - https://github.com/audahadi/proprietary_vendor_xiaomi

Bugs/Issues
[*]You tell me

Some ss
Rom is great for now.. all basic things works .. that is for now xD

Trying this rom for a few hours, I observed the followings:
The rom is smooth and rather fast.
Almost everything works properly.
Xposed works on this rom without any problem.
Battery life is reasonable.
Thank you so much, aniket.lamba.:good:

@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers

rajib4 said:
@aniket.lamba hi bro, I have a query.
But before that thanks a ton for the wonderful work you have done with this ROM :thumbup: Your Metallium ROM was my favorite LP ROM and I used it as my daily driver from the time it got released and never had to look at any other ROM after that as it was rock stable and super fast
Now for the query, was going through a post by John Cannon Jr on TeamOct G+ community where he mentioned that for non-nexus devices CM will be the base going forward. So for cancro-marshmallow will you continue the AOSP base or will change the base to CM in future? Asking this as there are lot of CM based ROMs available for cancro-marshmallow but not many AOSP based.
Cheers
Click to expand...
Click to collapse
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.

marko94 said:
Some ss
Rom is great for now.. all basic things works .. that is for now xD
Click to expand...
Click to collapse
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
aniket.lamba said:
Initially it'll be CM based.As the ROM development progresses further,we might shift to the AOSP base.
Click to expand...
Click to collapse
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.

Me_Ashish_ said:
Are there CM themes? The app drawer shows it is, ur settings screenshot (might have missed), doesn't show that. Also the ROM is AOSP based.
No slow charging bug?
---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------
"might shift", does that mean it is CM based right now. The FAQ question and the 'based on' posted on the op shows AOSP atleast.
Click to expand...
Click to collapse
For the initial stage it is CM based,this build which I've posted is an initial build (considering it still has issues) so we chose CM base as we draw more support of non-nexus devices,we'll shift the base to AOSP.I'll change the thread title so the users won't have a problem figuring out.

I have a doubt...does ambient display has a BUG or it's not working just for me.

nirjharmistry said:
I have a doubt...does ambient display has a BUG or it's not working just for me.
Click to expand...
Click to collapse
Never heard of someone who got Ambient Display working anytime. It just shows the, doesn't supports though.

Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all

Me_Ashish_ said:
Is it only me or the ROM doesn't support extended partition?
I tried flashing twice, but after installing GAPPS. Xposed doesn't get installed due to no space.
Also the maximum CPU frequency doesn't change at all
Click to expand...
Click to collapse
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk

diongdyh said:
Apparently you're not on extended partition. Your system is only 660mb instead of 1.2gb which means you're on stock partition. Did u flash MIUI recently? It might've reverted your partition to stock.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.

Me_Ashish_ said:
That's not the case. Some ROMs work at stock even though you are on extended partition. Though I knew it's not my phone I still anyways re flashed extended partition ZIP leading in same result.
BTW installing MIUI or any other ROM via recovery doesn't make you loose ur extended partition.
Click to expand...
Click to collapse
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk

diongdyh said:
If you've flashed the extended partition and it's still in 660mb means that you've failed. I know only flashing miui through fastboot gets you to stock partition. The point is you're on stock partition.
Sent from my MI 4 using Tapatalk
Click to expand...
Click to collapse
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.

Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
Ooh did u mean that after flashing this ROM your system partition got reset to default (660mb)?
Cuz in the screenshot you attached it shows that you only have 660mb.
Sent from my MI 4 using Tapatalk

Me_Ashish_ said:
Nope. I'm on extended partition since months. You haven't come across that kind of ROMs I mentioned it looks like. And I can't remember the exact name of few ROMs which had that issue right now.
And for the record after that ROM I installed CM12.1 without installing any repartition ZIPs and I had a 1.2G system size.
Click to expand...
Click to collapse
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD

marko94 said:
yeah,same happened to me.. I am also on extended , but after flashing this rom , my partition go back to stock.. easy fix for that, go to recovery, backup rom, restore rom,reboot and now all is fine xD
Click to expand...
Click to collapse
I too faced the same issue and with other ROMs too. There is an easy fix. If you are using twrp, go to Wipe->advanced Wipe Select "System" and click "repair or Change File system" below. Then Select "Resize". The issue will now be fixed.
If you are flashing ROM and Gapps, do the above step after flashing ROM before installing the Gapps.

Is this rom cm based or aosp based?

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 ?

Paranoid Android Ruby Beta 4 - Mi A3

{
"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"
}
We are very excited to announce the Beta of Paranoid Android Ruby, based on Android 11.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
As we are growing on our list of supported devices in each release, we require of a stronger build environment so we can speed up the compilation process for releases. Based on the actual Quartz 4 list, we support over 30 devices, which takes between 2 and 3 days for all the builds to be completed without counting possible compilation issues or rebuild needs, based on our current specs.
We kindly ask all of you that are in position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate here
Changelogs
Code:
Official Ruby Beta 3.
Device-specific issues
1. You tell!
Note: Custom kernels are NOT supported unless the kernel says it supports PA and GMS is included. Please be on the latest Android 11 update released by Xiaomi. Incase if you have issues with Sensors/persist, please reflash stock 11 from fastboot.
Requirements
My preferred logging format is:
adb logcat -b all -d *:E > logcat-err.log
adb logcat -b all -d > logcat.log
adb shell dmesg > dmesg.log
Then you can upload them to https://del.dog and send me the link for each one.
Download - Beta 4.
Instructions
Note - you need to be on Stock 11 firmware.
Download the latest fastboot zip we released (hint: it has an -image appended to zip name) with Beta 4 tag.
Reboot to fastboot
Flash the fastboot zip with "fastboot update pa-ruby-4-laurel_sprout-20210506-beta-signed-image.zip"
Reboot to recovery and format data.
Reboot to system.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android, ROM for the Mi A3
Contributors
ZVNexus, xboxfanj, Vishalcj17
Source Code: https://github.com/AOSPA/android_kernel_xiaomi_laurel_sprout
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
ROM Firmware Required: Latest Stock Firmware
Based On: CAF
Version Information
Status: Alpha
Current Beta Version: Ruby Beta 4
Beta Release Date: 2021-02-25
Created 2020-11-23
Last Updated 2021-05-07

Paranoid Android Ruby Beta 4 is out!
This build is Production/User and is Enforcing.
This vendor is based off CAF tag :- 'LA.UM.9.11.r1-03200-NICOBAR.0'', and has been updated completely to R. The usage of stock vendor/blobs is only for camera and not anything else.
Device sided Changelog:-
Kernel optimisations.
Changes to frequency tables.
Fixed DT2W on AOD.
Updated brightness overlays.
Updated vendor to LA.UM.9.11.r1-03200-NICOBAR.0.
Improved Google Camera Performance.
Fixed Frequencies stuck at high with GPS.
Optimisation to battery backup.
Fixed overheating fully.
Android Auto and Screen Recording fixed.
Now for this Beta update, you have to be on Stock 11/updated to stock 11.
No support for stock 10 firmware from my side starting from this build.
Also please don't try to install any kind of custom recovery. Also that, please don't try installing Old Alpha release after installing beta because that was based up on Stock 10 firmware.
If you want magisk, please patch the boot image (inside pa fastboot zip).
You can dirty flash, but if you face bugs, please clean flash and format data.
All of my work is uploaded and open in github.com/AOSPA and github.com/ThankYouMario. Feel Free to use it the way you can.
You can also track it in our Gerrit.
Hope you like it. Cheers.
#StayParanoid
Support my work by clicking on the thanks button!

Excellent Vishal Nice work many thanks

Screenshots please

Rajendran Rasa said:
Screenshots please
Click to expand...
Click to collapse

Excellent work Vishal bro.
Ekdom jakkkas

NOTE: If you want magisk, get the one from the Telegram support group. We don't know if official magisk works perfectly or not for now.
REVIEW-
Performance: It's fluid AF. The rom never hicks up, all animations hold their framerate, and the UI is snappy and responsive. I don't game, but I'm sure this will handle gaming well enough.
Battery: Solid. Not Spectacular or anything, but good. Expect around 7~8 hrs of SOT if you're an average user who doesn't game. Standby drain is also minimal.
Stability: Had no glitches or bugs so far (except for the ones mentioned already). It's reliable. Had no force reboots, or issues that made me want to restart the device.
FOD and Faceun*ock: FOD is accurate and snappy. I've seen faster, but this ain't no slouch. Faceun*ock is blitzing fast! Try it. It's fantastic!!
Overall I think this is a very good A11 ROM for our device. Definitely Daily-Driver material. There is no customization and many additional features, but for those looking for a close to stock experience, look no further.
The dev is very talented and kind. He regularly pushes updates and listens to the community. I Highly recommend joining the TGM group to stay on top of all the happy haps. Love you CJ, keep the cool stuff coming bro!

Good and best rom...

Do Beta versions of PA have OTA updates or do we need to manually flash updates every time until the release builds come out ?

Alright I flashed the ROM and just finished setting everything up. For now these are the bugs/issues I've encountered:
The device takes forever to reboot
USB file transfer doesn't seem to work
Device is unencrypted by default (this may be intentional since it's a pre-release)
Other minor UI bugs
Wide-Angle lens doesn't work in GCam (Urnyx05 2.5 in my case)
On the other side I'm happy to see that:
The device is Play Protect Certified
SafetyNet passes
Widevine Level is L1
Bluetooth Issues from Quartz seem to be fixed
I will come back in a few days with a more detailed report

Muda42 said:
Alright I flashed the ROM and just finished setting everything up. For now these are the bugs/issues I've encountered:
The device takes forever to reboot
USB file transfer doesn't seem to work
Device is unencrypted by default (this may be intentional since it's a pre-release)
Other minor UI bugs
Wide-Angle lens doesn't work in GCam (Urnyx05 2.5 in my case)
On the other side I'm happy to see that:
The device is Play Protect Certified
SafetyNet passes
Widevine Level is L1
Bluetooth Issues from Quartz seem to be fixed
I will come back in a few days with a more detailed report
Click to expand...
Click to collapse
Hi. Thank you For the feedback.
For USB, i use CAF HALS which need some driver changes, i can help you with that.
Code:
1. Plug In your Device
2. Click Start and Search for Device Manager.
3. Search for Android Devices/ADB(Usually at the top of the devices)
4. Uninstall Any ADB drivers installed.
5. Re-insert your phone after uninstall
Encryption is disabled until and unless Xiaomi release stock R (i am dependent on their modem and ICE changes). Wide-angle is something ill look into, thanks!

Sairagav said:
NOTE: If you want magisk, get the one from the Telegram support group. We don't know if official magisk works perfectly or not for now.
REVIEW-
Performance: It's fluid AF. The rom never hicks up, all animations hold their framerate, and the UI is snappy and responsive. I don't game, but I'm sure this will handle gaming well enough.
Battery: Solid. Not Spectacular or anything, but good. Expect around 7~8 hrs of SOT if you're an average user who doesn't game. Standby drain is also minimal.
Stability: Had no glitches or bugs so far (except for the ones mentioned already). It's reliable. Had no force reboots, or issues that made me want to restart the device.
FOD and Faceun*ock: FOD is accurate and snappy. I've seen faster, but this ain't no slouch. Faceun*ock is blitzing fast! Try it. It's fantastic!!
Overall I think this is a very good A11 ROM for our device. Definitely Daily-Driver material. There is no customization and many additional features, but for those looking for a close to stock experience, look no further.
The dev is very talented and kind. He regularly pushes updates and listens to the community. I Highly recommend joining the TGM group to stay on top of all the happy haps. Love you CJ, keep the cool stuff coming bro!
Click to expand...
Click to collapse
Thanks for the review! Will try my best to make the experience better for you.

Will the fingerprint work with the screen off?

Onurnymr10 said:
Will the fingerprint work with the screen off?
Click to expand...
Click to collapse
We didn't add the support yet. You might see than in future builds.

Excellent rom...Just loved using it...Keep up the Good Vishal and all behind this..We desperately need these roms.

The rom it's work perfecly, really smooth when open apps, you must install this rom!
Best rom I have ever flashed, ROMs ui like stock battery backup is also awesome thanks to Developer.
I love you 3000 @Vishalcj17 .

great rom @Vishalcj17
smooth and stable no problem so far other than those mentioned in this thread and support group which you already answered to!!
battery backup is good
performance is great, no lags or glitches
looking forward for future releases
keep up the good work and #stayparanoid

friend, do you know what is to use a rom great, fluid, stable and has good battery life with always on display active all the time?. it's really cool to me the best rom by far in every way

Is it necessary to format internal storage?

[ROM][13.0][TOCO][OFFICIAL] Project Elixir 3.x

{
"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"
}
Project Elixir for the Xiaomi Mi Note 10 Lite [toco]
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."​
Project Elixir is another aftermarket AOSP ROM which basically offers minimal UI enhancement & close to Stock Android ROM with great performance, security and stability. Most of the OEMs' these days will provide slow and untimely updates, but we don't do that here. We closely follow Google to bring the latest updates to our users, and even prolong support for devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience while using Project Elixir will be butter smooth without compromising the quality of the Android experience. In short, it's perfectly balanced between Great Performance, Security, stability, minimal UI & awesome features including pixel goodies So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy Project Elixir on your respective devices!​
- Saurav - Founder / lead Developer
- Nishant - Co-lead Developer / Team
- Probir - Developer / Team
- Mayur - Developer / Team
- And Also Our Hardworking Maintainers​
// Checkout the latest changes you get //
Spoiler: Click Here to see
Latest Changelog: https://projectelixiros.com/changelog
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
// A screenshot is worth of thousand words //
Spoiler: Click Here to see
Latest Screenshots : https://projectelixiros.com/gallery
NOTE : In Project Elixir you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- > OFFICIAL Download Server < ---------
NOTE: Please keep in mind that these are Gapps Builds and there is no vanilla build of this rom available.
--------- > Visit Our OFFICIAL Website < --------- ​
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH (Moving From A12 to A13)
- Download the latest build
- Take a backup for safe side
- Boot to Recovery
- Format Data by typing yes
- Flash the latest build
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work? or Any Bug ?
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS​
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Proton AOSP
- Arrow OS
XDA Banner and Template Credit goes to Amaan
- Others, I may have forgot to mention​
- Android OS version: 13.0
- Security patch: October 2022
- Build author/Device Maintainer : @AndroidHQ254
- DEVICE: Xiaomi Mi Note 10 Lite
- DEVICE CODENAME: toco
---- Sources and Documentation ----
-- ROM Source Code --
-- Kernel Source --
-- Documentation & Maintainership --​
-- OFFICIAL Website and Telegram Support --
-- Visit our OFFICIAL Website --
-- Device Update Telegram Channel --
-- Support/Discussion Telegram Group --​
// Giving a little can HELP a lot //
- As you know build is free but building ROM needs server and in order to maintain the source, we need High-End Servers that are generally very expensive and need to be renewed every single month and as a student its quite difficult. To meet with our technical expenses, a cup of coffee, and the efforts of the developers we need your monetary support!
- Do consider donating or buying me a coffee on Paypal or join us on Patreon for sustainable support and rewards if you want to appreciate our work.
- Thank you for your support !
​

Nice

i don't know if this is a bug, but under screen fingerprint reader does not work when the screen is off

everything works so well, this rom is much better than miui hahaha, awesome work!

Hi to all. Are the banking apps works normally ?
Or do we need any hacks for security checks ?
Thanks

John Crush said:
everything works so well, this rom is much better than miui hahaha, awesome work!
Click to expand...
Click to collapse
Hi. What recovery did you use to flash this ROM please ?
Ps: I'm from stock Miui 13.02

teknocorse said:
Hi. What recovery did you use to flash this ROM please ?
Ps: I'm from stock Miui 13.02
Click to expand...
Click to collapse
Hi, I followed the installation guide on the official website:
Project Elixir
projectelixiros.com
So I used this twrp version:
[RECOVERY][3.6.2_12][TOCO][UNOFFICIAL] Stable TWRP for Android 13 AOSP Roms
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our...
forum.xda-developers.com
And I installed the "MIUI V13.0.2.0 Firmware" in the global version, even though my phone is from Europe

John Crush said:
Hi, I followed the installation guide on the official website:
Project Elixir
projectelixiros.com
So I used this twrp version:
[RECOVERY][3.6.2_12][TOCO][UNOFFICIAL] Stable TWRP for Android 13 AOSP Roms
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our...
forum.xda-developers.com
And I installed the "MIUI V13.0.2.0 Firmware" in the global version, even though my phone is from Europe
Click to expand...
Click to collapse
Thank you !

John Crush said:
everything works so well, this rom is much better than miui hahaha, awesome work!
Click to expand...
Click to collapse
Thanks. Glad you are enjoying

teknocorse said:
Hi to all. Are the banking apps works normally ?
Or do we need any hacks for security checks ?
Thanks
Click to expand...
Click to collapse
SafetyNet passes out of the box without root

i flash it i follow procedure but keep on rebooting and back to recovery mode

Hey, I installed this ROM with TWRP but the camera app doesn't work. Am i doing something wrong? I installed by clean flash method.

lucy42 said:
Hey, I installed this ROM with TWRP but the camera app doesn't work. Am i doing something wrong? I installed by clean flash method.
Click to expand...
Click to collapse
In addition, only the native camera app crashes. Like, if i open the google lens app camera actually opens. But, the native camera app comes with the ROM crashes. @AndroidHQ254

lucy42 said:
In addition, only the native camera app crashes. Like, if i open the google lens app camera actually opens. But, the native camera app comes with the ROM crashes. @AndroidHQ254
Click to expand...
Click to collapse
I ported the BSG's GCam 8.1 with the config files designated to Mi Note 10 Lite and fixed this problem.

lucy42 said:
I ported the BSG's GCam 8.1 with the config files designated to Mi Note 10 Lite and fixed this problem.
Click to expand...
Click to collapse
extremely confusing... where to get the configs? and which file to download exactly? im given like 6 different options and none seem intuitive.
"
Download:​
MGC_8.1.101_A9_GV2b_snap.apk (org.codeaurora.snapcam) #
MGC_8.1.101_A9_GV2b_MGC.apk (com.android.mgc) #
MGC_8.1.101_A9_GV2b_ENG.apk (com.google.android.GoogleCameraEng) #
MGC_8.1.101_A9_GV2b_ruler.apk (com.samsung.android.ruler) #
MGC_8.1.101_A9_GV2b_scan3d.apk (com.samsung.android.scan3d) #
MGC_8.1.101_A9_GV2b_qcamera3.apk (org.codeaurora.qcamera3) #"
EDIT ok i got help here - any of these are fine, except the ones for Samsung, as they are esentially the same thing.

Fingerprint scanner doesnt work when in sleep, doesnt wake phone. need to hit power button then scan finger.
also, wifi button doesnt seem to toggle in the quick drop down menu. Visually.
Edit - wifi button works, just had to reboot system. maybe phone brain fart.

Any plans for a vanilla build at some point?

Idaho1911 said:
Any plans for a vanilla build at some point?
Click to expand...
Click to collapse
no

eishey said:
i flash it i follow procedure but keep on rebooting and back to recovery mode
Click to expand...
Click to collapse
Ensure you use the recommended Android 13 recoveries

maxlieb said:
Double tap to wake does not work after ~5 seconds after screen off (after the always on display dims down)
* Might be related to a broken screen replacement.
* I DID verify that the problem is a software problem - flashed xiaomi.eu rom and it DOES work there.
* I'm NOT at all sure it worked even with original screen (screen was fully functional, just a few cracks in the glass)
Update:
Tried derpfest and project elixir, same problem.
also found this on pixel-experience github issue tracker...
exactly the same issue - AOD becomes too dim and tap to wake stops working.
seems it's a known problem.
Click to expand...
Click to collapse
Quoting myself from the thread for Evolution rom... same problem with Elixir and DerpFest.