Develop Bugs

[ROM] FingerSense ROM by Qeexo for Nexus 6P!

Introducing FingerSense ROM for Nexus 6p!
Download Link
https://qeexo.sharefile.com/d-sd0966c93c3d41b58
Kernel source
https://github.com/qeexo-opensource/angler-kernel
Version information
FingerSense ROM for Nexus 6p v0.1 BETA
Posted on 2016-11-01
Based on AOSP NRD90M (Android 7.0.z)
Huawei Nexus 6p (Angler)
Kernel version 3.10.z
About this ROM
This ROM brings Qeexo's FingerSense technology to the Nexus 6p.
FingerSense is Qeexo's next generation touch platform that enables mobile devices to understand the difference between touchscreen inputs such as fingertip, knuckle, nail and stylus. This current ROM will allow the device to distinguish between fingertip (normal input) and knuckle.
While FingerSense is currently deployed on tens of millions of devices worldwide, we're looking for feedback from the XDA community to improve our product for future releases.
For more information on FingerSense and Qeexo, see the links below:
http://www.qeexo.com
FingerSense Intro Video
FingerSense How-To
EazLi Intro (formerly FS Launcher)
Important!
This ROM will
Update your /vendor partition. This is to update the Android Sensor hub firmware to enable FingerSense functionality, also referred to as the nanohub or contexthub by Google.
Update the touch controller firmware to enable FingerSense functionality. For reverting back to stock, see "Uninstalling" below.
Integrate FingerSense into the Android UI. See Features below.
The kernel is STOCK except for the changes required to enable FingerSense. This ROM is not compatible with any other kernels.
About Qeexo
By bringing machine intelligence to human input, Qeexo develops innovative solutions to advance the field of human-computer interaction. The company's technologies elevate the user experience of touch-enabled devices, making them more intelligent, more powerful, and easier to use. Qeexo works with the world's top mobile companies and its technology is deployed on tens of millions of devices worldwide. Spun out of Carnegie Mellon University, Qeexo is venture-backed and headquartered in Mountain View, California.
Features
With one knuckle, double knock to launch EazLi. EazLi provides easy access your apps and app shortcuts from any screen.
With two knuckles, knock once to trigger a system screenshot
With a single knuckle, draw a region for a SmartShot (cropped screenshot)
With a single knuckle, draw a "c" for quick access to the Camera (stock Camera app)
Additional letters (w, m, s, and e) are unassigned
All gestures are assignable within the Settings app, however, cropped screenshots can only be assigned to the "region" gesture.
Developers
By following our simple demo app, FingerSense can be integrated into your app however you like. Note that the above "system-wide" gestures are temporarily disabled once an app takes control of FingerSense.
https://qeexo.sharefile.com/d-s24e923778df43cc8
Installation
Disclaimer: Qeexo assumes no responsibility for damage to your device or to yourself that results from using this software.
Flash the zip with TWRP
Wipe/erase data and cache before rebooting
Install open-gapps, SuperSu, etc., if desired, as usual
If you get a warning such as "There's an internal problem with your device. Contact your manufacturer for details.", see this thread
Uninstalling
Flash a factory image package from Google. This will also restore the vendor partition.
Flash the stock touch firmware (https://qeexo.sharefile.com/d-s7576b31f21843388)
XDA:DevDB Information
FingerSense ROM by Qeexo, ROM for the Huawei Nexus 6P
Contributors
qeexo, a.vandelay
Source Code: https://github.com/qeexo-opensource/angler-kernel
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: v0.1 BETA
Beta Release Date: 2016-11-01
Created 2016-11-01
Last Updated 2016-11-01

Interesting. I'll give it a go once I'm at home. I have a warranty device on the way so I can take a gander at this. The knock features can come in handy when working on the car or in tight spaces. Can any app or function be assigned to a gesture?

Jammol said:
Interesting. I'll give it a go once I'm at home. I have a warranty device on the way so I can take a gander at this. The knock features can come in handy when working on the car or in tight spaces. Can any app or function be assigned to a gesture?
Click to expand...
Click to collapse
Yes, any app can be assigned to most of the gestures using the new "FingerSense" menu in the Settings app

I've seen Video and REALLY its awesome, I'll definitely give a try, Thanks for something DIFFERENT[emoji4]

First of, thank you so much for sharing your project with us. It's greatly appreciated.
It seems like a great innovative idea, I hope it goes forward and it's just the beginning.
I will certainly try this tomorrow and share my feedback.

Wow this is amazing . !!! :laugh::laugh::laugh:

Having a weird issue. When trying to flash the ROM and gapps, I get an instant reboot right when gapps installation begins. Tried multiple versions and packages of gapps.
Flashing ROM by itself works fine.

Jammol said:
Having a weird issue. When trying to flash the ROM and gapps, I get an instant reboot right when gapps installation begins. Tried multiple versions and packages of gapps.
Flashing ROM by itself works fine.
Click to expand...
Click to collapse
Are you using TWRP? We used the open-gapps "pico" version for Android 7.0 and it installed without any complaints.

It is FORCE Encryption enabled, So be careful....

qeexo said:
Are you using TWRP? We used the open-gapps "pico" version for Android 7.0 and it installed without any complaints.
Click to expand...
Click to collapse
Correct. Tried using Pico. I ended up having to flash ROM and Gapps at different instances for it to work.
I get the lovely "internal error with your device" message at pin and pattern entry. Vendor appears to have some sort of mismatch? I did flash NRD90M. Could it be because of the touch drivers?
I like it from what I used last night, but N gives me poor battery so I'm back to MM for now. Would be nice if it could be up to date on the latest security patch, but that'll probably be a pain.
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
mukesh22584 said:
It is FORCE Encryption enabled, So be careful....
Click to expand...
Click to collapse
Be careful with?

Jammol said:
Be careful with?
Click to expand...
Click to collapse
I think what he meant was that there are many people who are using their Custom/Stock ROMs unencrypted (due to personal preferences, TWRP support, etc.) and flashing this ROM will encrypt their device. It's more of a heads-up than anything else.

shadowstep said:
I think what he meant was that there are many people who are using their Custom/Stock ROMs unencrypted (due to personal preferences, TWRP support, etc.) and flashing this ROM will encrypt their device. It's more of a heads-up than anything else.
Click to expand...
Click to collapse
Correct [emoji106]

Jammol said:
I get the lovely "internal error with your device" message at pin and pattern entry. Vendor appears to have some sort of mismatch? I did flash NRD90M. Could it be because of the touch drivers?
Click to expand...
Click to collapse
See this thread for the "There's an internal problem with your device. Contact your manufacturer for details." error. It can be resolved. It's likely because we have repacked the vendor image to replace the firmwares.
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347

Review??

Wtf... Thanks ?????
Sent from my Pixel XL using XDA-Developers mobile app

I flashed this along with open gapps pico 7.0
getting error popus "google play services stopped". Any fixes?
Googled to resolve this. cleared data, cache, force stop, reboot. problem persists
Thanks for this unique ROM )

This is really cool, i'll give it a try when i have more free time after work!! Thanks for the hard work =)

Gopinath15 said:
I flashed this along with open gapps pico 7.0
getting error popus "google play services stopped". Any fixes?
Googled to resolve this. cleared data, cache, force stop, reboot. problem persists
Thanks for this unique ROM )
Click to expand...
Click to collapse
We were able to fix this by explicitly granting the location permission to google play services. Settings -> Apps -> Google Play Services -> Permissions -> (grant all)

Was interesting to see Huawei's new Mate 9 Pro feature this and "knuckle gestures" - good stuff!

qeexo said:
We were able to fix this by explicitly granting the location permission to google play services. Settings -> Apps -> Google Play Services -> Permissions -> (grant all)
Click to expand...
Click to collapse
I have switched for another rom due to this error.
shall try this again. Thanx

Lineage downloader can't connect

Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris

Joheee said:
Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris
Click to expand...
Click to collapse
S7 is no longer officially supported by lineageOS. You can search here in XDA for unofficial ROMs.
I have no big hope that a new ROM will really solve your battery issue. Most of the the success stories are a result of a clean ROM installation.

Joheee said:
Dear reader, since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version.........
Click to expand...
Click to collapse
In addition to the outstanding information that @kurtn had provided...
There's no Official LineageOS Updater Apps on the Play Store.
The reason is that they have an implemented LineageOS Updater built into the Firmware and has no need to provide any such app separately from the firmware. That would just be counterproductive to the built in Updater.
The LineageOS Updater App(s) on the Play Store is via a 3rd party developer. I'm not stating that any/all of them are either good or bad but, individuals need to know that their Unofficial and is in no way supported by the Official Lineage Team Maintainers.
Just a few (so to speak) words of advice to keep in mind. I remember asking about them (quite a while ago) and those were the types of words/thoughts by @invisiblek and @haggertk (whose a part the Official Lineage Lead Maintainers).
No lectures here... Just some friendly information for you My Friend!
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX1 Forum App on my Sanyo Juno device.

Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2

Joheee said:
Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2
Click to expand...
Click to collapse
Oh, looks like ivan does a good job. I think it is a good idea to install his rom.
But be aware: whatever it is, that eats your battery, it can come back.
Edit: be aware: from the threads it looks like 15.1 and 16.0 are not SELinux enforcing. So the gain of security is not as high as one would expect from security patch level. So you can try a factory reset of 14.1 as well.

Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).

Joheee said:
Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).
Click to expand...
Click to collapse
Download the zip files for rom (and GApps if needed) boot into twrp wipe system, data and caches (not internal: there are your pictures and downliads etc)
Install: navigate to downloads folder select the zip file and hipe it works.
If not: ask in the thread you linked.

How to use lineage downloader app
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....

[email protected] said:
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....
Click to expand...
Click to collapse
Don't use that app. Use the procedures described in wiki.lineageOS.org

General XDA Article: Android 13 Beta 2.1 is here with bug fixes

NEW:
TL;DR:
Android Flash Tool
flash.android.com
OR
Pixel 6 Proraven-tpbb.220414.018-factory-87c865df.zip87c865dff79bd5e4b3a239ac710a64178b8380173d50d2e9d93eb9edb0e9e76e
Android 13 Beta 2.1 is here with bug fixes
Android 13 Beta 2.1 is here with bug fixes and not much else. You can install it on your eligible Google Pixel smartphone now.
www.xda-developers.com
May 26, 2022 1:26pm Comment Adam Conway
Android 13 Beta 2.1 is here with bug fixes​Android 13 is edging closer and closer, and we’ve already seen a lot of what’s to come with the next platform release. We’ve seen the company adding new features with each build, and some highlights include the photo picker API and more granular media files permissions. Most recently we saw Android 13 Beta 2 drop during this year’s Google I/O which set the groundwork for a more predictive back gesture, but the company is already out with Beta 2.1, packing in a few software fixes for users who are currently testing out the betas.
When will Android 13 release?​
{
"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"
}
For Android updates, Google typically reveals a “platform stability” milestone so that developers can know when Google intends on delivering the final SDK/NDK APIs, along with final internal APIs and app-facing system behaviors. Google intends on reaching platform stability in June 2022, with several weeks at minimum planned before the official release. Android 12 hit platform stability in August of 2021 and the final version was released in October of that year. Google has released more details about the release timeline that you can check out.
Android 13 Beta 2.1 bug fixes​These fixes are as follows:
Fixed an issue where typing in the search bar resulted in a blank list of suggestions.
Fixed an issue where devices would crash and restart when turning on hotspot.
Fixed an issue where a continuous call dialing sound could be heard in the background during a phone call.
Fixed an issue where devices would crash and restart after disconnecting from Android Auto.
If you’re someone who’s using one of these betas, then you should think about installing Beta 2.1 that just came out. Note though that the known issues list that Google published for Beta 2 applies here, it just seems to be the case that Google deemed these ones to be a higher priority and fixed them in between beta releases.
All in all, it’s a pretty minor release, and it’s good to see Google ironing out bugs in between releases. Beta builds are designed to be used by users who want to try out the next version of Android, so while you shouldn’t use it on your daily driver, I’m sure plenty of users do. As a result, some of these are pretty problematic bugs that could have caused problems for people.
How to download and install Android 13 Beta 2.1 on your Google Pixel device​You can easily download Android Developer Beta 2.1, and be sure to check out our guide on how to install Android 13 if you’re unsure of how to do so.
Google is officially releasing this beta update for the Pixel 6 Pro, Pixel 6, Pixel 5a 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4 XL, or Pixel 4. You can use the 64-bit system images with the Android Emulator in Android Studio, and you can also use a GSI too.
Click to expand...
Click to collapse
OLD:
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
February 14, 2022 7:00am Skanda Hazarika
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM​If you are familiar with Windows 11, you have almost certainly heard of Windows Subsystem of Android. Microsoft constructed its Android compatibly layer on the foundation of Windows Subsystem for Linux, which is based on the company’s Hyper-V virtualization platform. Google took a similar approach while designing the Linux app functionality in Chrome OS, but they relied on the Kernel-based Virtual Machine (KVM) of the Linux kernel as the hypervisor. Due to the fact that Android is built on top of the Linux kernel, the question may arise: Wouldn’t it be technically possible to utilize KVM to run a virtual machine with another OS on any Android device? Well, if you have a Google Pixel 6/6 Pro and you are willing to flash the first Developer Preview build of Android 13, you can certainly achieve that feat.
Click to expand...
Click to collapse
https://twitter.com/i/web/status/1492712401262710784
What’s the secret sauce in Android 13 for the Google Pixel 6? According to XDA Senior Member kdrag0n, in the Android 13 bootloader and firmware for the Tensor platform, Google added the ability to expose the Exception Level 2 hypervisor privilege level to the kernel for its protected KVM feature (pKVM). While pKVM is optional and meant to be enabled on a per-VM basis, one can easily exploit the full KVM functionality on non-protected VMs. This is the reason why the developer could boot multiple Linux distributions and run them nearly at native speed. We knew that Google had plans to ship pKVM with Android 13, and even though this is only the first Preview build of next major release of Android, the current implementation looks quite stable.
Keep in mind that at this stage, direct KVM access on Android 13 requires root access. Having said that, a non-root implementation is possible by writing a VM management app and request a special permission to run a native service in a MicroDroid VM. There exist a number of such virtualization monitor like Google’s own crosvm, QEMU, or Firecracker, so an Android port of them should fill the void. Imagine running Windows 11 on your Android smartphone without messing with the underlying partitions, thanks to Android’s native virtualization support.
Best of all? It can run DOOM!
Click to expand...
Click to collapse
https://twitter.com/i/web/status/1493088558676017152

roirraW edor ehT said:
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
Click to expand...
Click to collapse
Wondrous times we live in - now that our phones have more RAM than our laptops, they can become actually useful^^

roirraW edor ehT said:
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
https://twitter.com/i/web/status/1492712401262710784
https://twitter.com/i/web/status/1493088558676017152
Click to expand...
Click to collapse
Does anyone have instructions on how to do this for a non-rooted pixel 6 pro ? Please? Unfortunately I'm stuck with the Verizon version and even though it's finally unlocked and I'm using it on another carrier, I'm still not able to root (but yes I am on android tiramasu dp1) thank you!

mrindependent said:
Does anyone have instructions on how to do this for a non-rooted pixel 6 pro ? Please? Unfortunately I'm stuck with the Verizon version and even though it's finally unlocked and I'm using it on another carrier, I'm still not able to root (but yes I am on android tiramasu dp1) thank you!
Click to expand...
Click to collapse
The article already answered your question
"Keep in mind that at this stage, direct KVM access on Android 13 requires root access."
Click to expand...
Click to collapse

mrindependent said:
Does anyone have instructions on how to do this for a non-rooted pixel 6 pro ? Please? Unfortunately I'm stuck with the Verizon version and even though it's finally unlocked and I'm using it on another carrier, I'm still not able to root (but yes I am on android tiramasu dp1) thank you!
Click to expand...
Click to collapse
And the article also says:
Having said that, a non-root implementation is possible by writing a VM management app and request a special permission to run a native service in a MicroDroid VM. There exist a number of such virtualization monitor like Google’s own crosvm, QEMU, or Firecracker, so an Android port of them should fill the void.
Click to expand...
Click to collapse
So if you write one or port one, then it should be possible on a non-rooted device.

I was directed here from the Pixel6Pro thread.
I am now trying to boot Windows OS from various virtual tools in an Android13 + rooted + enabled KVM environment.
As for booting Windows, I believe it will be with Qemu, but I have not been able to successfully boot with Qemu, which is put in via pkg install from Termux.
Has anyone successfully tried booting Windows OS using KVM?
I would like some tips on getting Windows to work.
Also, we are able to boot Ubuntu using cloud-hypervisor, but the network connection from the guest to the outside is not working properly. Any advice on this as well?
～～
Translated with www.DeepL.com/Translator

I haven't tried yet. I haven't tried booting Linux distros either. I'm still trying to wrap my head around the kind of kernel, both host and guest, that's required to even do this if stock isn't suitable. I was able to set the flag on my bootloader though.
Last I heard is that kdrag0n wants to put together a guide once the solution is more mature.

@jok_jok_a
Please provide any help publicly and do not ask users to contact you via other means.

TL;DR:
Android Flash Tool
flash.android.com
OR
Pixel 6 Proraven-tpbb.220414.018-factory-87c865df.zip87c865dff79bd5e4b3a239ac710a64178b8380173d50d2e9d93eb9edb0e9e76e
Android 13 Beta 2.1 is here with bug fixes
Android 13 Beta 2.1 is here with bug fixes and not much else. You can install it on your eligible Google Pixel smartphone now.
www.xda-developers.com
May 26, 2022 1:26pm Comment Adam Conway
Android 13 Beta 2.1 is here with bug fixes​Android 13 is edging closer and closer, and we’ve already seen a lot of what’s to come with the next platform release. We’ve seen the company adding new features with each build, and some highlights include the photo picker API and more granular media files permissions. Most recently we saw Android 13 Beta 2 drop during this year’s Google I/O which set the groundwork for a more predictive back gesture, but the company is already out with Beta 2.1, packing in a few software fixes for users who are currently testing out the betas.
When will Android 13 release?​
For Android updates, Google typically reveals a “platform stability” milestone so that developers can know when Google intends on delivering the final SDK/NDK APIs, along with final internal APIs and app-facing system behaviors. Google intends on reaching platform stability in June 2022, with several weeks at minimum planned before the official release. Android 12 hit platform stability in August of 2021 and the final version was released in October of that year. Google has released more details about the release timeline that you can check out.
Android 13 Beta 2.1 bug fixes​These fixes are as follows:
Fixed an issue where typing in the search bar resulted in a blank list of suggestions.
Fixed an issue where devices would crash and restart when turning on hotspot.
Fixed an issue where a continuous call dialing sound could be heard in the background during a phone call.
Fixed an issue where devices would crash and restart after disconnecting from Android Auto.
If you’re someone who’s using one of these betas, then you should think about installing Beta 2.1 that just came out. Note though that the known issues list that Google published for Beta 2 applies here, it just seems to be the case that Google deemed these ones to be a higher priority and fixed them in between beta releases.
All in all, it’s a pretty minor release, and it’s good to see Google ironing out bugs in between releases. Beta builds are designed to be used by users who want to try out the next version of Android, so while you shouldn’t use it on your daily driver, I’m sure plenty of users do. As a result, some of these are pretty problematic bugs that could have caused problems for people.
How to download and install Android 13 Beta 2.1 on your Google Pixel device​You can easily download Android Developer Beta 2.1, and be sure to check out our guide on how to install Android 13 if you’re unsure of how to do so.
Google is officially releasing this beta update for the Pixel 6 Pro, Pixel 6, Pixel 5a 5G, Pixel 5, Pixel 4a (5G), Pixel 4a, Pixel 4 XL, or Pixel 4. You can use the 64-bit system images with the Android Emulator in Android Studio, and you can also use a GSI too.
Click to expand...
Click to collapse

Tensor 2 spotted?
https://www.volza.com/exports-south-korea/south-korea-export-data-of-s5p9855
PARTS >> SPARE PARTS FOC DEVELOPMENT CHIP WHITE CHAPELPRO S5P9855 TEST BOARDSWITH SPARE PARTS / ACCESSORIES / COMPONENT FOR R&D PURPOSE
Click to expand...
Click to collapse

Anyone else having issues getting the factory image to flash? It says it flashes successfully, but then the phone just reboots back into the bootloader. If I hit Start from the bootloader, it just boots right back into it. I've downloaded the factory image multiple times just in case the download was bad.

blackroseMD1 said:
Anyone else having issues getting the factory image to flash? It says it flashes successfully, but then the phone just reboots back into the bootloader. If I hit Start from the bootloader, it just boots right back into it. I've downloaded the factory image multiple times just in case the download was bad.
Click to expand...
Click to collapse
Are you using the latest Platform Tools (not updated in a couple of months, so I would guess yes). I haven't flashed 13 at all, by the way. It might be worth you trying https://flash.android.com/preview/tm-beta2.1 instead. It wouldn't be the first time that using the flash site solves a problem that flashing a factory image didn't solve - or had problems with.

roirraW edor ehT said:
Are you using the latest Platform Tools (not updated in a couple of months, so I would guess yes). I haven't flashed 13 at all, by the way. It might be worth you trying https://flash.android.com/preview/tm-beta2.1 instead. It wouldn't be the first time that using the flash site solves a problem that flashing a factory image didn't solve - or had problems with.
Click to expand...
Click to collapse
Platform Tools might be the issue. I haven't updated them in a while.
Android Flash Tool did successfully install the build. Thanks for the suggestion.

Question ONEPLUS 9 PRO OXYGEN OS 12 UPDATE FOR LE2120

Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?

Sheikhoo007 said:
Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?
Click to expand...
Click to collapse
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.

Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.

Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
Which bugs are you facing?

Yup, and i've been using it for a month now.

I updated to A12 in Dec when the first OTA was pushed. I had too many issues even after the first 2 patches, downgraded back to OOS11 and never been happier.
I'm waiting for 10pro to launch so I can update to OOS12 then

Time of Awakening said:
Which bugs are you facing?
Click to expand...
Click to collapse
I played around so much, that I don´t remember everything now. Some apps didn´t work. I think, but I´m not sure, I had problems with Viper4Android. Or it was Youtube vanced. Sorry, I really forgot.
Certain setting options had been missing for me or were no longer where you would have expected them to be. I also missed the local upgrade, but that problem has been solved in the meantime (I was not well informed). I was also not happy with the UI, but that is not a bug but a matter of taste.
In sum, not so dramatic, but my evaluation has coincided with those of other forum members. Does not mean that I am right. I'm happy to be corrected.
How is the general satisfaction with A12 here?

A few months back when they started pushing Android 12 I was eager to try it and so I used "Oxygen Updater" from the play store to download a full stable version of android 12 but i accidentally downloaded the Indian version. I had so many bugs on it, but then I used the same app (oxygen updater) to switch to the EU version and my phone worked perfectly with no bugs or anything. I have now switched to Pixel Experience rom and wifi is not working so I may go back to Oxygen 12. But yeah if you have bugs on Oxygen 12 then use Oxygen Updater and download a new version to flash and your bugs may vanish.
Enjoy

I was curious about A12 and gave it a second try after cleaning up everything.
Does Viper4Android work? Just trying with a fix but not sure if it will work.
The next thing is that file manger doesn´t appear in Magisk, when u want to install a module from internal storage.
At least Youtube Vanced is working now.
BTW, post above is ColorOS 12

mrcrazy11 said:
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.
Click to expand...
Click to collapse
Another question: how to us the "OnePlus 9/9Pro Rollback APK". It´s a zip file. Unpacking shows now apk file. Flashing through kernel manager of course not possible. Sorry, don´t find a way to install.
Second try of A12 was not satisfying. When I use the MSM Tool I´ve to re-root again....
Edit: renamed the file to apk at the end. Did it once without success, don´t know why. Now it works

Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.

mrcrazy11 said:
Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.
Click to expand...
Click to collapse
Thanks, my problem was that I didn´t know that I have to rename the files. Many thanks!

Personally, I'm pretty satisfied with the C44 update for OxygenOS 12, stable and smooth, as intended. But yes, the first updates were messy.
For having given a try to ColorOS 12 too, OxygenOS 12 gave me a better experience on the OnePlus 9 Pro: less throttling in games and less bloated.
If we get a ColorsOS C44 EU (which should be far more debloated than its Chinese counterpart) that isn't making games throttle, then I'll surely jump into the wagon, but for now, OxygenOS 12 remains the better option if you want an Android 12 official experience for your phone.

CalyxOS - Secure, de-Googlefied

I recently managed to bollux up my 2XL, particularly the ability to install Recovery, TWRP or any other. After trying to install a series of ROMS, I found CalyxOS at https://calyxos.org/ CalxyOS is an interesting, security-focues de-Googlefied ROM that does not require or permit a Recovery installation, nor have I been able to root it. It's installed via use of a batch file run while booted to bootloader. CalxyOS comes with a lot a FOSS software, as well as the ability to use Google services if you want them (I do). I found that the best way to get some Google items installed at the system level was to use the Aroma version of Open Gaaps 11 https://opengapps.org/ and select the minimum of what I wanted, and then using the Aroma installer delete all the included stuff I did not want to make sufficient room for the installation. There is not enough room even to install Pico gaaps if you don't do it this way. I'm using this as a 2nd phone, mostly for tracking mileage in my car, so it has a Google Fi data chip, only. I booted TWRP from my computer and tried to install Magisk, unsuccessfully. Anyway, I at least have a working phone again!

From the CalxyOS website, it looks like only Pixel 3 and up are getting updates.

calyxos rapes my battery and lacks many basic android features, touts itself as secure while not taking amny extra steps to do so, beyond that of which every non-stock rom does
wheres the hardened or at least changable webview
the app isolation?
frequent security updates?
the list goes on, this rom seems just like an excuse to sell a overpriced product, a door to door scam that reminds me of purism or apple

2022-02-11
CalyxOS 2.14.0 - Android 11, February 2022 Security update is now available for the Pixel 2, 2 XL and Mi A2.
Sadly, we will no longer be able to provide OS updates for the Pixel 2, and Pixel 2 XL. The Xiaomi Mi A2 should get Android 12 at a later date, if everything goes well.
Pixel 2, Pixel 2 XL​
This is the final CalyxOS update for these devices. Google stopped updating the Pixel 2 series as of December 2020.
Up till now, we extended these phones useful lifetimes by patching the open source components: AOSP and the Linux kernel. Linux kernel 4.4 was a long-term support kernel, but has stopped receiving updates this month. ( see https://en.wikipedia.org/wiki/Linux_kernel_version_history )
Unfortunately due to the kernel dependency, it is also not feasible to have Android 12 fully working on these devices. There are various community efforts, but there’s no fully working port as far we know.
As such, we have decided to stop updating these devices. Applications such as Chromium and microG will still continue recieving updates.
Click to expand...
Click to collapse
Like Graphene, i will not spect any upgrade anymore, even microG ........