General June 14, 2023 - Beta 3.1 UPB3.230519.014 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah] - Google Pixel 7 Pro

Android 14 Beta program for the Pixel 7 Pro [Cheetah]​
Download links in the middle of the OP.
Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback. Android 14 Developer Preview 1 is an early baseline build that's still in active development, so the Android system and apps running on it might not always work as expected.
Click to expand...
Click to collapse
{
"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"
}
Note to anyone who flashes a Developer Preview or Beta OTA without having the capability to unlock your bootloader - you'll be stuck in the Developer Preview and Beta program until it goes final - in the case of Android 14, somewhere between August and October 2023. There is absolutely nothing that can be done about this without being able to unlock the bootloader. And even with an unlocked bootloader, you'll have to perform a complete wipe when going back to Stable.
June 14, 2023:
Beta 3.1:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing preview system images for Pixel devices.
developer.android.com
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
Get Android 14 | Android Developers
Get Android 14 on your eligible device.
developer.android.com
Android 14 Preview | Android Developers
How the Android 14 Preview works, the timeline, and what is included.
developer.android.com

We'll be glad if someone provide screenshots pf new features and changes

Dr.Pepper said:
We'll be glad if someone provide screenshots pf new features and changes
Click to expand...
Click to collapse
No screenshots, but adding this to the OP now:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com

roirraW edor ehT said:
No screenshots, but adding this to the OP now:
Release notes | Android Developers
Release notes and known issues for the latest Android 14 builds.
developer.android.com
Click to expand...
Click to collapse
This message was for someone who will install DP)
Right now i dont have access to PC and cant install on my P7 DP)
Will patinetly waiting for SS!)

I'll be flashing this as soon as I get home from work

I just flashed it without wiping, coming from A13 February stable build. Boots up fine and just started looking around. All my apps that I've opened so far work fine.
I'm going to try and root it soon, I'll let you know how that goes.

Rooted fine for me. Coming from A13 Feb stable build.
Device will NOT pass Device Integrity within Play Integrity at all now on USNF 2.3.1 Diplax mod, BUT works intermittantly on USNF 2.4.0. Will now have to try with GooglePay. Seems like the Play Security Update of February may have something to do with it?

Added the following (LONG!):
Android Developers Blog
News and insights on the Android platform, developer tools, and events.
android-developers.googleblog.com

pogo-airsupport said:
Rooted fine for me. Coming from A13 Feb stable build.
Device will NOT pass Device Integrity within Play Integrity at all now on USNF 2.3.1 Diplax mod, BUT works on USNF 2.4.0. Will now have to try with GooglePay
Click to expand...
Click to collapse
I was just about to send you a reply asking what version of USNF you're on, but then I saw my quote of your post was different (edited) from your original post.

SIM manager seems extremely unstable.
And yes, T-Mobile n25 is still missing.

No way to flash without wipe on a locked bootloader, right?

gpvecchi said:
No way to flash without wipe on a locked bootloader, right?
Click to expand...
Click to collapse
Only download and flash only for the DP builds unfortunately, so correct

gpvecchi said:
No way to flash without wipe on a locked bootloader, right?
Click to expand...
Click to collapse
And you probably don't want to unless you can unlock your bootloader when you choose, because with a locked bootloader, you would be stuck in this Android 14 Developer Preview and then Beta until it goes Final somewhere between August and October 2023.

I'm seeing a full compliment of 32-bit libraries inside the system image and inside the APEXs, so Google is still shipping with multilib for the time being.
I haven't tested the preview with my forks of Magisk that provide 32-bit support to see if they work, but in theory it should work fine.
Now I'm questioning why Google is still doing multilib and if their plans are at some point in the preview process to make all libraries 64-bit only, or if the Pixel 7 is just going to have this half-way transition to 64-bit only for the rest of it's Android releases.

Should update that warning to a
roirraW edor ehT said:
And you probably don't want to unless you can unlock your bootloader when you choose, because with a locked bootloader, you would be stuck in this Android 14 Developer Preview and then Beta until it goes Final somewhere between August and October 2023.
Click to expand...
Click to collapse
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.

First hour of playing with the update, everything seems pretty smooth. Scrolling especially.
Device is still warm, but that's expected with the optimization and updating going on behind the scenes.
GooglePay is going to be a write off for the time being, until root and modules are a bit more optimized. The update does seem to break it more consistently, so reproducing the error will at least be easier.
All apps still seem to work.
I went from a g5300n radio to the bundled g5300g radio. I had been using the QPR2.1 radio with the stable builds for better reception. Took about 1-2 minutes for g5300g to lock on to 5G, but since then has had stable signal.
Notable bugs:
1. Central clock widget time is NOT centered.
2. Device battery widget will not show % or name when shrunk under a certain size
3. LSPOSED menu is BROKEN

The https://developer.android.com/about/versions/14/overview has already changed with some minor corrections.
It did say:
What's included in the Android 14 Preview?​...
SDK & NDK tools​...
SDK, NDK, and tools for Android 14
...
For more inforamtion, see Get Android 14.
Click to expand...
Click to collapse
Now it says:
What's included in the Android 14 Preview?​...
SDK & tools​...
SDK and tools for Android 14
...
For more information, see Get Android 14.
Click to expand...
Click to collapse

LLStarks said:
Should update that warning to a
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.
Click to expand...
Click to collapse
I'll consider it, thank you. There's really nothing we can do to support anyone who does and can't unlock their bootloader, anyway.
I might go for several flashy, annoying danger GIFs instead.

LLStarks said:
Should update that warning to a
Should update that first post warning to a big red DO NOT FLASH for locked bootloaders. We should refuse to support anyone that does and then complains.
Not putting up with a repeat of 13 DP1.
Click to expand...
Click to collapse
Okay, I've modified the warnings. If that's not enough heads up, then I give up.

https://twitter.com/i/web/status/1623382609056129025

Related

[GUIDE] How to install Internal Android 10 Build for Nokia 9 PureView

If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
Alright.
AOP-513D-0-00WW-B03 (V5.13D_B03) here is same to the official release. So if you have installed this build, just enjoy it.
You will get later updates like regular Nokia 9 Devices.
To those who are still running 5xxx builds older than 513D B03, please download packages here.
Click to expand...
Click to collapse
To users who have installed this internal build, please share your experience report here if you're willing to, thanks.
Now I think Android 10 for Nokia 9 is stable enough and will be released to public soon, so I think it's time to post it here.
If HMD will push Android 10 officially, you can install it under ADB sideload easily and link will be posted here.
Internal build version: AOP-513B-0-00WW-B01
It will be updated from: AOP-427F-0-00WW-B01, which is released October 2019 Security Update.
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than AOP-427F-0-00WW-B01, update to 427F before proceed.
FYI, 427F is October 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
2. Install AOP-513A-0-00WW-B01-427F-0-00WW-B01-update.zip with adb sideload under recovery.
3. Reboot to normal OS and recovery again - it's not over yet.
4. Install AOP-513B-0-00WW-B01-513A-0-00WW-B01-update.zip with adb sideload under recovery.
5. Reboot your phone.
That's it.
If Android 10 official update pushed publicly, link will be updated here.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer. I've uploaded stock boot image here if you have unlocked bootloader. There's no "Flashing is not rooted for fused device" issue under 5xxx build.
You can check overall experiences here (prototype, though): https://www.youtube.com/watch?v=v6ScYgISGFg
Download link:
To prevent throttle error, I didn't upload them to Google Drive or other cloud storages. Sorry for inconvenience.
https://www.androidfilehost.com/?w=files&flid=300249
Just installed on my Nokia 9 TA-1087, works perfectly. No bugs found so far. So far so good. Animations really smooth, camera launch is significantly faster than Android 9. The dark mode is not fully dark but that was expected. Overall excellent experience. Definitely worth the update.
{
"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"
}
Any tutorial for hpw to do that? And if something goes wrong how to flash stock pie again? Thnx
Ok done. Flashed... All working very well without bugs.
Battery life seems better on 10. There is no night mode on camera i hope add it to next updates...
can we use it in TA-1087?
Mod edit - Translated by Google Translate:
427F full package download address please provide trouble, thanks
*********************
427F全量包下载地址麻烦提供下,感谢啦
and the most serious.. do. we need to unlock bootloader?
Sent from my Nokia 9 using Tapatalk
ktlk21 said:
and the most serious.. do. we need to unlock bootloader?
Sent from my Nokia 9 using Tapatalk
Click to expand...
Click to collapse
No need to unlock bootloader or root
and when we want to go back to stable channel? what happens?
Sent from my Nokia 9 using Tapatalk
Google pay works but can't add new cards as it says it's been rooted or altered in some way. I know it's not rooted but will we not get the proper update now as a result of doing this?
I installed the internal build 10 update on my TA-1082 (US) last night (about 20 hours ago) and it's been working/behaving extremely stable.
Feels noticeably faster than 9.
Thanks to OP for making it available:good:
Hi there! Is the device certified or not after installing this software version? I'm thinking, if not, maybe the mobile banking apps won't work on it
I installed it a while ago and it seems pretty stable and fast, the face recognition doesn't work as well tho. Also its a shame when you switch the dark theme on it doesn't make the boot dark as well, like the pixels. Everything else is working great! Thanks for sharing the build :good:
PS: I didn't have to root or anything, I just downloaded the two builds and updated using the stock recovery via adb sideload, it works on a non rooted fully stock phone, which is awesome
Any idea if there is possibility to revert back to stock ROM? I found only nb0 firmwares that seems is not able to flash to Nokia 9 with Nokia flash took.
Thanks.
Thank you! I am on it now...
---------- Post added at 05:31 PM ---------- Previous post was at 05:27 PM ----------
How can I flash it into the recovery? If I boot on the recovery via adb I have "No Command" menu... what should I flash before?
Thanks!!!
sev7en said:
How can I flash it into the recovery? If I boot on the recovery via adb I have "No Command" menu...
Thanks!!!
Click to expand...
Click to collapse
Check out steps in this article-
https://www.techmesto.com/recovery-and-download-mode-in-nokia/
graphreak said:
Check out steps in this article-
https://www.techmesto.com/recovery-and-download-mode-in-nokia/
Click to expand...
Click to collapse
Thank you, I guess my model is not compatible as when I sideload I get that error:
"Package is for product AOP_sprout but expeced fih_sdm845"
I have the single sim edition available from UAE.
There is any OTA for that?
Cheers,
sev7en said:
Thank you, I guess my model is not compatible as when I sideload I get that error:
"Package is for product AOP_sprout but expeced fih_sdm845"
I have the single sim edition available from UAE.
There is any OTA for that?
Cheers,
Click to expand...
Click to collapse
Not aware of any OTA available for UAE model.
It is the Nokia 9 Pureview? What's the Model Number?
Mine is a single SIM too but, for US/North America with Model number TA-1082.
graphreak said:
Not aware of any OTA available for UAE model.
It is the Nokia 9 Pureview? What's the Model Number?
Mine is a single SIM too but, for US/North America with Model number TA-1082.
Click to expand...
Click to collapse
Hello,
my model is TA-1082, single sim. I purchased it in Dubai... but when I flash for the OTA upgrade, it shows the message as above. Why?
EDIT: My build number is: 00WW_4_27D_SP02
Feedback of issues I have gotten so far:
- Phone freezes when playing videos.
- Network connectivity drops to nothing randomly.
- Google Pay doesn't work without internet.
Feedback on improvements:
- Phone faster and more responsive.
- Better battery life after a week.
Is anyone having these issues or is it just me, and also how do we return to stock rom in case something goes bad? I haven't unlocked the bootloader or rooted the phone so I'm unaware on how to do this just in case.

MARS_SOMs V220313 - Pixel Expierence Android 12+ GSI Patches

MARS SOM
{
"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"
}
The first so called SOM
Systemless-On-Memory
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 12 GSI (Pixel Expierence)
[Preferred ARM64 A/B VNDKLITE]
Downloads:
Dev Ice Technologies
WELCOME
sites.google.com
Non GSI related Bugs:
Report them if You found one!
Donations:
paypal.me/miustone​
Instructions can be found in the README on GitHub: https://github.com/Miustone/MARS_SOM
since gestures dont work does this mean we have to use the 3 button layout? Also, thank you for your work mate! Im pumped to try out the ROM
eqbirvin said:
since gestures dont work does this mean we have to use the 3 button layout? Also, thank you for your work mate! Im pumped to try out the ROM
Click to expand...
Click to collapse
Right. I can also recommend Fluid Navigations Gestures from the Play Store. Hope to fix this soon... Sorry for that!
Hope You will enjoy it anyways
Gestures worked for me on the .25 update! But I had to set the pixel launcher as default home manually! However, I just clean flashed and everything to update to the .51 update and the SOM causes bootloops on the .51. Did you get it running on .51 or just .25 so far?
Miustone said:
Right. I can also recommend Fluid Navigations Gestures from the Play Store. Hope to fix this soon... Sorry for that!
Hope You will enjoy it anyways
Click to expand...
Click to collapse
Thanks for putting this together! I'm not familiar with Gcam (Been a while since I last rooted) but does using this "SOM" mean if I install it I can use Gcam? Or does other development have to be done?
eqbirvin said:
Gestures worked for me on the .25 update! But I had to set the pixel launcher as default home manually! However, I just clean flashed and everything to update to the .51 update and the SOM causes bootloops on the .51. Did you get it running on .51 or just .25 so far?
Click to expand...
Click to collapse
Well, Bootloops shouldn't happen with newer Firmwares. Sounds Like SONY has changed Something bigger... I need to take a look
TripodKnight said:
Thanks for putting this together! I'm not familiar with Gcam (Been a while since I last rooted) but does using this "SOM" mean if I install it I can use Gcam? Or does other development have to be done?
Click to expand...
Click to collapse
You're Welcome! Actually am i struggling with GCAM Support. I have much Expierence with Camera related Things but SONY really screwed it Up since the 2019 Xperias (Maybe already on the 2018s which i havent used). 2021 could be anyways the Year i can fix it with Android 11. Fingers crossed!
Btw. actually will GCam Ports never be able to deliver a truely benefit over the SONY Cam since porting the APK only means bypasses and Tricks to make it Work (different to what i am doing). Just Take a look on the Pixel Expierence which is actually on the 2019 Xperias allowing to use any GCam Ports. Sadly i haven't found the Reason for this yet. Maybe i missed some libs or so. We'll See
Miustone said:
Instructions can be found in the README on GitHub: https://github.com/Miustone/MARS_SOM
Click to expand...
Click to collapse
Thank you so much for making this, I thought we would never see a ROM for our phone.
I want to try it but I have a few questions about this, if you don't mind and find the time. Is this kind of rom common for all devices? The same files are used on xperia and pixel phones for example? Changing the "fingerprint" of the device means that it will be recognized as a pixel device (build.prop etc)? Will that cause issues with the sony exclusive apps that are not supported on other devices?
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
palamosteliaro said:
Thank you so much for making this, I thought we would never see a ROM for our phone.
I want to try it but I have a few questions about this, if you don't mind and find the time. Is this kind of rom common for all devices? The same files are used on xperia and pixel phones for example? Changing the "fingerprint" of the device means that it will be recognized as a pixel device (build.prop etc)? Will that cause issues with the sony exclusive apps that are not supported on other devices?
Click to expand...
Click to collapse
All Apps should Work fine so far. But You will notice that there are almost No SONY Apps left.
My ROMs are only working on the 2019 and 2020 Xperia Flagships, other Devices would need different Configs from Me, but Yes. I'm using non edited Pixel Firmwares for My ROMs, means You will use original Pixel 4 XL or 5 Files on Android 10-11. I'm the only one on XDA who works Like that as far as i know... Hope You will like it too Have fun!
SeriousFlash said:
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
Click to expand...
Click to collapse
High hopes for Android 11! Since i have still the Xperia 5 do i need to wait some longer... But i'm prepared for it Pixel 5 Firmwares are already Explored from Me
SeriousFlash said:
Gestures only work with default launcher, it is a known android limitation. When I installed nova launcher I was greated with a pop up about this. Android 11 should fix it.
Click to expand...
Click to collapse
Any indication that'll happen for sure? Sony plans to upgrade to 11?
hovikg said:
Any indication that'll happen for sure? Sony plans to upgrade to 11?
Click to expand...
Click to collapse
Yes. Release Dates are also known. The 2019 Xperia Lineups gets Android 11 starting the next Month. 2020 Xperias are already receiving it
Sony sure taking their time with that a11 update.
When I flashing it on android 11, it mentioned that api version is too high. Dear Atuthor I keenly need your update.
Miustone said:
Yes. Release Dates are also known. The 2019 Xperia Lineups gets Android 11 starting the next Month. 2020 Xperias are already receiving it
Click to expand...
Click to collapse
Still no update February 19th!
My 3 year old Pixel got 12, but still no 11 on the Sony ...
So, everyone should be on Android 11 now right!? Someone here who runs it with Magisk 22.0?
Android 11 Updates are out on GitHub! Will push a ready-to-use Version on My Website next!
I would love to try but patched boot.img on A11 still brings a bootloop on my 5II (XQ-AS52).
Hmm, even with the latest Magisk 22.0 Beta? @T3chDelicious
Miustone said:
Hmm, even with the latest Magisk 22.0 Beta? @T3chDelicious
Click to expand...
Click to collapse
I will try again when the new update is available in European market (58.1.A.5.55) which is hopefully this night since I must re-unlock bootloader anyway and make a fresh install of firmware. Then I will patch boot.img with Magisk Beta or Canary when Beta fails.
I will let you know.
T3chDelicious said:
I will try again when the new update is available in European market (58.1.A.5.55) which is hopefully this night since I must re-unlock bootloader anyway and make a fresh install of firmware. Then I will patch boot.img with Magisk Beta or Canary when Beta fails.
I will let you know.
Click to expand...
Click to collapse
Did the same yesterday with the Beta. The Magisk Changelog looks promising...
Thanks in advance for keeping me updated!

[OFFICIAL] LineageOS 19.1 for the Razer Phone

{
"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"
}
Razer Phone
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Razer Phone.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
cheryl - Official builds​
cheryl - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs (won't fix):
- Can't switch FPS to 60 (can only switch between 90 and 120)
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps. - GApps are included in my unofficial builds​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_razer_msm8998
Flashing your unofficial build now.
I take it coming from 18.1 official requires a clean flash?
Thanks so much for keeping these devices alive it really means a lot to me.
Rox598 said:
Flashing your unofficial build now.
I take it coming from 18.1 official requires a clean flash?
Thanks so much for keeping these devices alive it really means a lot to me.
Click to expand...
Click to collapse
if going to unofficial yeah, but officials coming probably this week.
npjohnson said:
if going to unofficial yeah, but officials coming probably this week.
Click to expand...
Click to collapse
Think I'll stick with unofficial for a while since it passes safetynet without root.
Fwiw the at a glance widget doesn't show the weather for me and I had to disable the Android system intelligence as it kept telling me it had stopped not sure if the intelligence controls that widget.
Rox598 said:
Think I'll stick with unofficial for a while since it passes safetynet without root.
Fwiw the at a glance widget doesn't show the weather for me and I had to disable the Android system intelligence as it kept telling me it had stopped not sure if the intelligence controls that widget.
Click to expand...
Click to collapse
android system intelligence is fixed - next build just went live which fixes it.
At a glance is expected - we don't have the tie ins for it.
npjohnson said:
android system intelligence is fixed - next build just went live which fixes it.
At a glance is expected - we don't have the tie ins for it.
Click to expand...
Click to collapse
Ah brill I just saw it and downloading now. Shame about at a glance I'll just use the old one.
Oh and theres a message on boot about an internal error?
Rox598 said:
Ah brill I just saw it and downloading now. Shame about at a glance I'll just use the old one.
Oh and theres a message on boot about an internal error?
Click to expand...
Click to collapse
fixed too.
npjohnson said:
fixed too.
Click to expand...
Click to collapse
You're a wizard thanks!
Official builds running on Saturday night.
I'm currently on 18.1 official and just got an OTA notice about this build (19). Currently using OpenGapps micro for Android 11, should I wait for that to update before i download the new 19 ROM or is it okay to switch to MindTheGapps? The test builds for OpenGapps don't work for SDK32 according to the OpenGapps thread, so I would need to switch to get Gapps.
Just an FYI I moved over to official builds since they released today seems you can't manually pick the Material You colour from the wallpaper and style menu.
I *think* it was there on the unofficial build.
Front Camera Not Working
Yep this weeke update didn't fix the front camera either
The screen size of the app don't macht my phone screen, please check attached pics.
Only the nova settings screens is ok, the rest are positoned on the upper left side of the screen. But only at graphic level. The interface level (touchs) is recognized at full screen. It makes the phone almost unusable.
It works fine with lineageos 18.1.
I don't know if it is a configuration issue or another problem.
Any idea?
Thanks in advance
Are the above issues (front camera and screen size) are still problematic in the most recent builds?
-SKYLINE- said:
Are the above issues (front camera and screen size) are still problematic in the most recent builds?
Click to expand...
Click to collapse
From my side, yes. The screen problem is yet present with the last version installed. See attached pic.
Regards
saenanme said:
From my side, yes. The screen problem is yet present with the last version installed. See attached pic.
Regards
Click to expand...
Click to collapse
pls try unofficial - we may have fixed it.
npjohnson said:
pls try unofficial - we may have fixed it.
Click to expand...
Click to collapse
Where can I download it?
Thanks
npjohnson said:
pls try unofficial - we may have fixed it.
Click to expand...
Click to collapse
If I were to go from LOS17.1 official to your unofficial, do I need to do a complete wipe?
Also, when you say it passes safetynet by default, does that mean banking apps work fine? Thanks!
-SKYLINE- said:
If I were to go from LOS17.1 official to your unofficial, do I need to do a complete wipe?
Also, when you say it passes safetynet by default, does that mean banking apps work fine? Thanks!
Click to expand...
Click to collapse
Yes and probably.

Question What's the most "updated" version? QPR1 or Sep. OTA?

As title says
What's the current version with most "fixes"?
I'm aware that QPR has August security updates (I don't mind), but does it also fix something that the September OTA doesn't?
Thanks!
The "latest" is usually gonna be there QPR beta, but remember: it's still a beta and could always have have issues.
Here's what I'm on (Pixel 6 Pro).
{
"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"
}
NuclearBastard said:
As title says
What's the current version with most "fixes"?
I'm aware that QPR has August security updates (I don't mind), but does it also fix something that the September OTA doesn't?
Thanks!
Click to expand...
Click to collapse
QPR1 Beta 1 is the latest with the August security update. The Sept update wasn't available upon release although it is now. Next version should include all security patches. But more than the FPR, which is now flawless, the network connectivity is incredible. Instant reconnect, no drops and better in places I never had it before. So hang in there we'll get the new update soon.
And P6 and P6P had the update by the time it was released which you can see in the screenie above.
bobby janow said:
QPR1 Beta 1 is the latest with the August security update. The Sept update wasn't available upon release although it is now. Next version should include all security patches. But more than the FPR, which is now flawless, the network connectivity is incredible. Instant reconnect, no drops and better in places I never had it before. So hang in there we'll get the new update soon.
And P6 and P6P had the update by the time it was released which you can see in the screenie above.
Click to expand...
Click to collapse
Awesome, thanks!
The phone will be in my hands only next week, just wondered whether I should enroll to betas or keep the official OTAs.
NuclearBastard said:
Awesome, thanks!
The phone will be in my hands only next week, just wondered whether I should enroll to betas or keep the official OTAs.
Click to expand...
Click to collapse
That's a good question which I can't answer for you. I heard the Sept update fixed the FPR but I'm not sure about the connectivity. The beta fixes both but it's a risk since it is a beta. I don't do betas since my bootloader is locked but this time I did and I don't regret it. I'd try the official to start and see how it responds for you. You can always join in but opting out requires a full wipe, i.e factory reset.
bobby janow said:
That's a good question which I can't answer for you. I heard the Sept update fixed the FPR but I'm not sure about the connectivity. The beta fixes both but it's a risk since it is a beta. I don't do betas since my bootloader is locked but this time I did and I don't regret it. I'd try the official to start and see how it responds for you. You can always join in but opting out requires a full wipe, i.e factory reset.
Click to expand...
Click to collapse
Hmm. When you say its locked, is it by choice or is google blocking the oem unlock? Some people say even in android 13 the option is grey.
Mine is fine though
n0lan said:
Hmm. When you say its locked, is it by choice or is google blocking the oem unlock? Some people say even in android 13 the option is grey.
Mine is fine though
Click to expand...
Click to collapse
I won't have a phone that cannot be bl unlocked, so it's by choice. Although, any time I install a beta or even a sideload update I will flip the OEM unlock switch just so I can recover if anything goes awry. Most often I'll flip it back for security purposes but not when I'm running a beta.
bobby janow said:
That's a good question which I can't answer for you. I heard the Sept update fixed the FPR but I'm not sure about the connectivity. The beta fixes both but it's a risk since it is a beta. I don't do betas since my bootloader is locked but this time I did and I don't regret it. I'd try the official to start and see how it responds for you. You can always join in but opting out requires a full wipe, i.e factory reset.
Click to expand...
Click to collapse
After enrolling to beta program, are users still getting official OTAs as they are released between beta versions? Or is it just beta route until a wipe?
Edit-
Oh, OK apparently it more straightforward than I thought! Taken from Google's beta program page:
"During the beta program’s release cycle, there will be stable releases to the public (the official platform release followed by Quarterly Platform Releases (QPRs)). When you apply the stable release update for the version you’re beta testing, you can opt out without a data wipe for a limited time until you apply the next beta update."
Apparently you can enroll to beta, download and install QPRs, and every time there's an official OTA in between you can update to it and then you're basically out of beta until you flash the next QPR.
That is, if I understand it correctly
NuclearBastard said:
After enrolling to beta program, are users still getting official OTAs as they are released between beta versions? Or is it just beta route until a wipe?
Edit-
Oh, OK apparently it more straightforward than I thought! Taken from Google's beta program page:
"During the beta program’s release cycle, there will be stable releases to the public (the official platform release followed by Quarterly Platform Releases (QPRs)). When you apply the stable release update for the version you’re beta testing, you can opt out without a data wipe for a limited time until you apply the next beta update."
Apparently you can enroll to beta, download and install QPRs, and every time there's an official OTA in between you can update to it and then you're basically out of beta until you flash the next QPR.
That is, if I understand it correctly
Click to expand...
Click to collapse
That's not what they mean. If you are on a beta build you can't just decide to take a monthly update. You can only take the next QPR1 update which will be Beta 2. When the beta program ends, and only when it ends, you will be upgraded to the latest stable build. So for instance you are on the beta 13 but the stable build is A12. Then the stable A13 drops and all beta users are offered that with no wipe. Enrolling in a beta such as QPR1 will not wipe the device due to enrollment. But flashing the build ,I presume from the below line, will wipe. Confusing so someone might want to jump in on this to clarify. This is the line you were looking for:
Warning: Flashing to a beta build from a production build—or going back to a production build from a beta build—requires a full device reset that removes all user data on the device. Make sure to back up the data from your Pixel first.
Here's the deal. You enroll in the QPR Beta program (currently on QPR1 Beta 1). When the stable release of QPR1 is released (probably sometime in December) and you apply that release (it will be offered to Beta users as well), you can then unenroll without having to wipe for a short time period preceding the next beta release (QPR2 Beta 1) that same month. If you unenroll before the stable release of QPR1, you will have to wipe.
Btw, the monthly security updates are included in the beta builds.
Oh, and the A13 QPR Beta program is due to run "through March 2023". Originally it was supposed to run until June 2023 but they changed it, maybe because they will probably release the 1st Android 14 Developer Preview in April 2023 and didn't want to have two "Beta" programs running at the same time.

[OFFICIAL] LineageOS 20 for the Razer Phone

{
"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"
}
Razer Phone
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Razer Phone.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
cheryl - Official builds​
cheryl - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs (won't fix):
- Can't switch FPS to 60 (can only switch between 90 and 120)
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps. - GApps are included in my unofficial builds​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_razer_msm8998
npjohnson said:
Razer Phone
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Razer Phone.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
cheryl - Official builds - Potentially coming soon!​
cheryl - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs (won't fix):
- Can't switch FPS to 60 (can only switch between 90 and 120)
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps. - GApps are included in my unofficial builds​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_razer_msm8998
Click to expand...
Click to collapse
Hi npjohnson, thanks for your great efforts to make Razer phone still relevant after all these years. Really appreciate it. But the link still has no files listed. Will wait for your further update. Thanks again for your continuous work.
@wanwije
Yes, same trouble here. The link shows, but it says the file is 0.00MB and when I click onto it it downloads an empty ZIP achieve. I guess, maybe we should just wait and try again tomorrow. Many thanks to all the developers still working on this device.
P650SE said:
@wanwije
Yes, same trouble here. The link shows, but it says the file is 0.00MB and when I click onto it it downloads an empty ZIP achieve. I guess, maybe we should just wait and try again tomorrow. Many thanks to all the developers still working on this device.
Click to expand...
Click to collapse
builds are running tonight.
Hi npjohnson, thanks again for the update, just a heads up that the your unofficial recovery shows github 404 and the main zip just says not found in the top left.
TenseRaptor said:
Hi npjohnson, thanks again for the update, just a heads up that the your unofficial recovery shows github 404 and the main zip just says not found in the top left. Also wanted to ask if the front cam bug was fixed in this update or not, just curious.
Click to expand...
Click to collapse
it is not. Working on it.
And the links should work now.
the links still do not seem to work.
The main zip is saying not found in top left
recovery is giving 404
am i clicking the wrong ones? matter of fact not of them work anymore, not even the 19.1
TenseRaptor said:
the links still do not seem to work.
The main zip is saying not found in top left
recovery is giving 404
am i clicking the wrong ones? matter of fact not of them work anymore, not even the 19.1
Click to expand...
Click to collapse
Same here. The subsequent link returns an unknown error occurred.
wanwije said:
Same here. The subsequent link returns an unknown error occurred.
Click to expand...
Click to collapse
yes before it actually showed the previous versions like 19.1 but now goes right to the error page
https://updater.oddsolutions.us/#/error
TenseRaptor said:
yes before it actually showed the previous versions like 19.1 but now goes right to the error page
https://updater.oddsolutions.us/#/error
Click to expand...
Click to collapse
aware - November builds are publishing tonight, and I needed the space on the server.
is it possible to use the lineageOS 20 recovery image to flash lineageOs 18? cuz if i lost the recovery for 18.1 and cant find it online (need the unofficial one)
TenseRaptor said:
is it possible to use the lineageOS 20 recovery image to flash lineageOs 18? cuz if i lost the recovery for 18.1 and cant find it online (need the unofficial one)
Click to expand...
Click to collapse
maybe? Probably not.
does this verson still have the camera bug where it the front cam does not work? just wanted to know if i should update cuz its my main phone
yoyomomo21 said:
does this verson still have the camera bug where it the front cam does not work? just wanted to know if i should update cuz its my main phone
Click to expand...
Click to collapse
Support wise it is the exact same as 19.1.
I have installed 20.0, aside from these two issues:
1. Front camera not working
2. Flash light not working (QS button is blurred out with the message "Camera in use")
the LOS is working fine.
I like the smoothness of the LOS and the fact that it makes my Razer phone see the light of day at this time, is a Godsend!!
Thanks to the developers.
wanwije said:
I have installed 20.0, aside from these two issues:
1. Front camera not working
2. Flash light not working (QS button is blurred out with the message "Camera in use")
the LOS is working fine.
I like the smoothness of the LOS and the fact that it makes my Razer phone see the light of day at this time, is a Godsend!!
Thanks to the developers.
Click to expand...
Click to collapse
Working on camera nonsense for what it's worth - not sure what is broken tbh.
Front camera not working.
YangYang1889 said:
Front camera not working.
Click to expand...
Click to collapse
yup, version 19.0 and higher the front cam does not work. the devs trying to fix it right now as stated in the post above on Nov 13
YangYang1889 said:
Front camera not working.
Click to expand...
Click to collapse
known, see OP.
The last version the camera worked was 18.1, im not trying to be rude or stupid, just dont know anything about developing a rom, but wont it be easier to compare the camera code of 18.1 and 20 to find the major differences.

Categories

Resources