https://developers.google.com/android/images
No change log yet, but still 9.0
Installed, no issues. Haven't rooted again yet though. The only thing I see so far is after boot, once you unlock it says "Pixel Booting." (or starting?)
---------- Post added at 12:39 PM ---------- Previous post was at 12:36 PM ----------
Bulletin is up: https://source.android.com/security/bulletin/pixel/2019-03-01
Just updated using the OTA via ADB sideload, rooted, and all is well.
Pixel 3 XL updates
Improved startup and responsiveness of the camera app
Improved recovery in the instance of OTA failure
Improved storage performance
Improved Bluetooth reliability
Improved playback of encrypted media in some video apps
Woohoo
Performance back to normal after the laggy February update!
Hopefully battery life is better again. Feb definitely made mine worse.
"There are no Pixel security patches in the March 2019 Pixel Update Bulletin."
Am I reading this right? I don't think I have ever seen an update without security patches.
Golf c said:
"There are no Pixel security patches in the March 2019 Pixel Update Bulletin."
Am I reading this right? I don't think I have ever seen an update without security patches.
Click to expand...
Click to collapse
There is, here is the chagelog
Improved startup and responsiveness of the camera app
Improved recovery in the instance of OTA failure
Improved storage performance
Improved Bluetooth reliability
Improved playback of encrypted media in some video apps
Jiggs82 said:
There is, here is the chagelog
Improved startup and responsiveness of the camera app
Improved recovery in the instance of OTA failure
Improved storage performance
Improved Bluetooth reliability
Improved playback of encrypted media in some video apps
Click to expand...
Click to collapse
Nothing to do with security
Golf c said:
Nothing to do with security[/QUOTE
https://source.android.com/security/bulletin/2019-03-01
https://source.android.com/security/bulletin/pixel/2019-03-01.html
Click to expand...
Click to collapse
Updated and re-rooted the wife's Pixel 3 today. Magisk 18.1 with TWRP 3.2.3-0 (.img only). ElementalX 1.05 with EX Kernel Manager direct flash. All worked normally. Couldn't do my 3XL this month since I am on dotOS. I did have to clear cache and app data (hide with Magisk of course) to get Play Store to re-certify the device which then showed a Google Pay update. Even though they claim no security fixes, clearly there are some.
Soo, I used the latest TWRP, the one ending in 4, the whole time I was in TWRP my phone vibrated lol. Anyone else have this happen? Everything still worked, but yeah, that was weird.
Jiggs82 said:
Golf c said:
Nothing to do with security[/QUOTE
https://source.android.com/security/bulletin/2019-03-01
https://source.android.com/security/bulletin/pixel/2019-03-01.html
Click to expand...
Click to collapse
Thanks. I knew I was reading it wrong
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
gettinwicked said:
Soo, I used the latest TWRP, the one ending in 4, the whole time I was in TWRP my phone vibrated lol. Anyone else have this happen? Everything still worked, but yeah, that was weird.
Click to expand...
Click to collapse
Yes, alot of us. I reverted back to previous twrp.
Click to expand...
Click to collapse
Golf c said:
"There are no Pixel security patches in the March 2019 Pixel Update Bulletin."
Am I reading this right? I don't think I have ever seen an update without security patches.
Click to expand...
Click to collapse
Apparently you missed the February update...
nomisunrider said:
Apparently you missed the February update...
Click to expand...
Click to collapse
Doubtful. I may not be able to read, but I miss no updates for 8 years
---------- Post added at 01:33 AM ---------- Previous post was at 01:33 AM ----------
Bootloader and radio changed again this month
Golf c said:
Doubtful. I may not be able to read, but I miss no updates for 8 years
---------- Post added at 01:33 AM ---------- Previous post was at 01:33 AM ----------
Bootloader and radio changed again this month
Click to expand...
Click to collapse
Hopefully the radio is better, as the feb one was garbage for me, failing to obtain 4G at times, dropping calls, bad call quality
I'm rooted with Magisk 18 and have a twrp recover 3.2 installed. Can I install this via OTA? I assume the root access will be root. What else do I need to do, besides reflashing Magisk zip?
walle4893 said:
I'm rooted with Magisk 18 and have a twrp recover 3.2 installed. Can I install this via OTA? I assume the root access will be root. What else do I need to do, besides reflashing Magisk zip?
Click to expand...
Click to collapse
If you're rooted, you can't take an OTA. You'll either have to flash the image, using the flash all bat, or ADB sideload the OTA. Either way you'll have to re-root after. If you flash the image you'll need to edit out the -w in order to keep your data. If you sideload the OTA you don't need to do anything to keep your data. It will install without wiping.
Hmmmm...Battery life really good today with the new OTA. Installed yesterday and today it seems much better.
gettinwicked said:
Hopefully battery life is better again. Feb definitely made mine worse.
Click to expand...
Click to collapse
Likewise, both battery and performance.
Related
Hello everyone,
here resurrection remix with treble support. This build have:
- GAPPS inside
- Night Light, Auto-Brightness, Ambient Display & more
- Aptx Hd driver
- Lte working
- No audio problem
Link
GAPPS VERSIONS
https://www.androidfilehost.com/?fid=674106145207484591 v.02
https://www.androidfilehost.com/?fid=674106145207484438 v.01
NO GAPPS
https://www.androidfilehost.com/?fid=890278863836283078
Installation
fastboot flash system_a system-arm64-ab.img
or if you want flash no gapps version
fastboot flash system_a system-arm64-nogapps.img
if you want format your userdate also add fastboot erase userdata or use twrp
CREDITS
@phhusson, @linuxct, @TheCrazyLex, @MishaalRahman
raimondomartire said:
Hello everyone,
here resurrection remix with treble support. This build have:
- GAPPS inside
- Night Light, Auto-Brightness, Ambient Display & more
- Aptx Hd driver
- Lte working
- No audio problem
Link
https://www.androidfilehost.com/?fid=674106145207484438
Installation
fastboot flash system_a system-arm64-ab.img
if you want format your userdate also add fastboot erase userdata or use twrp
CREDITS
@phhusson, @linuxct, @TheCrazyLex, @MishaalRahman
Click to expand...
Click to collapse
Will I be able to change the refresh rate? If not, is 120hz set to default and using the variable refresh rate feature?
Thanks in advance. I'm really happy to see people working in custom ROMs
el4nimal said:
Will I be able to change the refresh rate? If not, is 120hz set to default and using the variable refresh rate feature?
Thanks in advance. I'm really happy to see people working in custom ROMs
Click to expand...
Click to collapse
No for now I don't add this option in settings. I don't have a lot of times so update rom when possible.
raimondomartire said:
No for now I don't add this option in settings. I don't have a lot of times so update rom when possible.
Click to expand...
Click to collapse
Is there any file I can modify in order to change it? I just want to set my display to 120hz
el4nimal said:
Is there any file I can modify in order to change it? I just want to set my display to 120hz
Click to expand...
Click to collapse
Your display on all treble roms is always on 120 Hz. You can't switch to 60 or 90. So I must add an option on settings like stock rom
Thanks a lot for your work in putting this together!
How would we get root? I'm trying to use the LOS add-on, but root-checker says I don't have root.
BakaSenpai said:
How would we get root? I'm trying to use the LOS add-on, but root-checker says I don't have root.
Click to expand...
Click to collapse
On this rom you can install magisk manager or, better for me, install in twrp magisk 11.4 zip file
I'm uploading now two new builds. RR sources on this project give same media encoder problems. Now I don't find errors
New builds with GApps
https://www.androidfilehost.com/?fid=818070582850511202
Without Gapps
https://www.androidfilehost.com/?fid=962187416754478323
Does this have any call blocking that uses a wildcard and does this have protected apps feature?
Anyone having issues where apps are stuck on 'Download Pending' in Google Play?
---------- Post added 2nd May 2018 at 12:21 AM ---------- Previous post was 1st May 2018 at 11:36 PM ----------
From the looks of it - the NoGapps version doesn't have LTE working
If You have installed magisk flash Google framework module and in this way you'll solve all problems. For no gapps ver i'll look inside
In 10 minutes from now 2 new builds:
changelogs
- new su daemon
- I hope to solve playstore hang
GAPPS
https://www.androidfilehost.com/?fid=674106145207484591
NO Gapps
https://www.androidfilehost.com/?fid=890278863836283078
raimondomartire, I appreciate your help! I wanted to let you know that for some reason my Bluetooth microphone doesn't work. When I am on a call it only goes through speakers, even if I toggle handset\bluetooth, and the volume doesn't do anything. I had to completely disconnect for it to go through handset. Any thoughts?
Does anybody know if the version with Gapps has the same problem with the GSI version where it'll cause the phone to crash and reboot?
EDIT: It may of been an issue with the the beta Oreo firmware. I updated to the release Oreo firmware and all seems good so far. I had one hard crash during the setup process but that's it.
EDIT 2: The hard crash issue does appear to still be there, but happens far less frequently. It'll crash usually once a day and sometimes it'll crash and get stuck in download mode.
EDIT 3: The crashing issues seems to be the same as before. I've had it crash 7 or 8 times today.
ThatGuy94 said:
Does anybody know if the version with Gapps has the same problem with the GSI version where it'll cause the phone to crash and reboot?
Click to expand...
Click to collapse
Mine hasn't done that. I'm running v02.
Is anyone experiencing where if you restart your phone, it goes into the bootloader? O_O
BakaSenpai said:
Is anyone experiencing where if you restart your phone, it goes into the bootloader? O_O
Click to expand...
Click to collapse
That's a known issue. Easiest way is to either shutdown instead of reboot or connect to pc and use fastboot set_active a
BakaSenpai said:
Is anyone experiencing where if you restart your phone, it goes into the bootloader? O_O
Click to expand...
Click to collapse
Thankfully NO! Don't know what I usually mess up but this rom is doing fine. I do believe it has something to do with how you install. Try doing everything with fastboot, avoid using twrp. Also power off and reboot will both get you stuck in download mode. I will not do either if I am not by a PC to fix it. I also have my old one + one with me to put my sim in if needed.
BakaSenpai said:
Anyone having issues where apps are stuck on 'Download Pending' in Google Play?
---------- Post added 2nd May 2018 at 12:21 AM ---------- Previous post was 1st May 2018 at 11:36 PM ----------
From the looks of it - the NoGapps version doesn't have LTE working
Click to expand...
Click to collapse
If you have that issue, go to settings and force stop the Play Store. Once you reopen it, it should begin to download your apps like normal.
So the wave of the Oct. Security Update for the H918 is out. This new version is completely safe to update since this is still ARB 1 (See attached pictures).
Is it strictly security, or are there any UI/UX bugfix or additions?
nfc problem
bro , your nfc working ? i dont know why my nfc wont turn enable.. im using lg h918 v20 upgrade to oreo but the nfc wont enable.. when i click enable they turn disable quickly.. any solution ?
Ak7J4 said:
So the wave of the Oct. Security Update for the H918 is out. This new version is completely safe to update since this is still ARB 1 (See attached pictures).
Click to expand...
Click to collapse
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
pvaldeben said:
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
Click to expand...
Click to collapse
If you accept, the phone will go into a bootloop since the stock recovery has been replaced by twrp. So don't accept the update. Reflashing the ROM would stop the bootloops if you just so happen to accept it.
Mnementh666 said:
Is it strictly security, or are there any UI/UX bugfix or additions?
Click to expand...
Click to collapse
To me I believe its just strictly security tbh since I haven't noticed anything else. I will see if performance has been improved or not
Ak7J4 said:
To me I believe its just strictly security tbh since I haven't noticed anything else. I will see if performance has been improved or not
Click to expand...
Click to collapse
Cool. I won't stress it then. Thanks
pvaldeben said:
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
Click to expand...
Click to collapse
Actually I did accept it when I first saw the notification then when I realized I was rooted (about 4 years without root) the phone booted in to TWRP and I freaked out ... so I moved the slider to see TWRP was asking to enter some sort of password or key for it to continue. but then I saw the cancel button and I cancened and it took me back to the main TWRP screen where I just rebooted the system without issues.
The only reason I rooted was because OREO battery life was 10 % per hour weather I touched or did not touch the phone. I thought this security patch might have battery optimizations.
But thanks for your replay, I'm going to stay away from this system update since I'm rooted not. I guess I got luck and not bricking my phone.
20G Security Update Changelog
FYI
Software versions & updates: LG V20
Android Security Bulletin—October 2018
OP6 8GB/ 256Gb Avengers Edition with OOS 9.0.2 build A6000_22_181026 rooted
Since a few days strange behavior:
I load the device over night.in the morning the device is stuck in the boot loader screen.only way to get out is too long press power and then restart.
I have not changed settings after last update.anyone an idea?
i guess you mean charging?
whizeguy said:
i guess you mean charging?
Click to expand...
Click to collapse
Sure, charging
ihobahobby said:
OP6 8GB/ 256Gb Avengers Edition with OOS 9.0.2 build A6000_22_181026 rooted
Since a few days strange behavior:
I load the device over night.in the morning the device is stuck in the boot loader screen.only way to get out is too long press power and then restart.
I have not changed settings after last update.anyone an idea?
Click to expand...
Click to collapse
its in 9.0.2 and OB6, a bug that only occures on custom kernels. OB7 however fixed the bug
byReqz said:
its in 9.0.2 and OB6, a bug that only occures on custom kernels. OB7 however fixed the bug
Click to expand...
Click to collapse
Isn't it a magisk issue?
---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------
ihobahobby said:
OP6 8GB/ 256Gb Avengers Edition with OOS 9.0.2 build A6000_22_181026 rooted
Since a few days strange behavior:
I load the device over night.in the morning the device is stuck in the boot loader screen.only way to get out is too long press power and then restart.
I have not changed settings after last update.anyone an idea?
Click to expand...
Click to collapse
It's a know magisk issue, while charging with your phone off it will boot to the bootloader screen. You will have to wait for an update.
yldlj said:
Isn't it a magisk issue?
---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------
It's a know magisk issue, while charging with your phone off it will boot to the bootloader screen. You will have to wait for an update.
Click to expand...
Click to collapse
Could be a ROM issue, I'm rooted under stock and i have yet to see this happen under 9.0.2.
Flashed back to OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9 official latest OTA and the issue remains.
My kernel is: 4.9.106-perf+#1FriOct26 00:05:17 CST 2018. And which kernel woud you advise to use?
some changelog. I have quite new versions. only bug and opitimze and update patches.
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
What about security patch level? January or February 2019?
Do you participate in Android One Beta Program?
yes, they belong to the beta program. updates February.
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
Can you give a ota dump?
maxweber1981 said:
yes, they belong to the beta program. updates February.
Click to expand...
Click to collapse
Did you by chance test the WiFi speed with and without Bluetooth enabled? How about the Bluetooth audio codecs?
hope all google camera apps' focus instability problem is solved. broken since pie arrived. (if someone is betatester and can report, please do so)
maxweber1981 said:
some changelog. I have quite new versions. only bug and opitimze and update patches.
Click to expand...
Click to collapse
Could you provide screenshot showing baseband/modem version?
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Boot.img https://drive.google.com/file/d/1IAVSuYmOgzAw4G3HjNokjf-emIwk3xMD/view?usp=drivesdk
Patched boot https://drive.google.com/file/d/1t-G-TrEr3rYWnutSBDRIBy5RomaXapzP/view?usp=drivesdk
Images version
:laugh:
Any instructions how to update with Magisk installed? - anyone has already tried?
Is there a change log for this build?
Sent from my Phh-Treble vanilla using Tapatalk
maxweber1981 said:
yes, they belong to the beta program. updates February.
Click to expand...
Click to collapse
how to enroll beta program?
Friends give a link to the OTA-image 10.0.4.0
Is that issue fixed?
https://forum.xda-developers.com/mi-a2-lite/help/weird-wifi-issue-apps-updating-to-t3885216
What are the new features?
Thank you so much
Mattania said:
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Boot.img https://drive.google.com/file/d/1IAVSuYmOgzAw4G3HjNokjf-emIwk3xMD/view?usp=drivesdk
Patched boot https://drive.google.com/file/d/1t-G-TrEr3rYWnutSBDRIBy5RomaXapzP/view?usp=drivesdk
Click to expand...
Click to collapse
thanks for you boot patched
I'm not on the beta program and I just got the update tonight.
No change log or any message telling what was the update beside saying it was a security update.
The battery percent indicator has been removed from the accu-settings?
Please, run from it
I got that update on OTA (the 10.0.4 version), and now I have a crippled phone. Low brightness, poor battery life, troubles with WiFi networks above 2.4Ghz (now I miss my 5Ghz WiFi on my modem), and some apps doesn't even work fine. Also, finger scanner got slow, and I have troubles with mobile network. I'm afraid of finding more failures as I use it.
So, if someone is reading this and get the notification, please scrap it and don't install the updates unless you hate your phone.
ugn01 said:
I got that update on OTA (the 10.0.4 version), and now I have a crippled phone. Low brightness, poor battery life, troubles with WiFi networks above 2.4Ghz (now I miss my 5Ghz WiFi on my modem), and some apps doesn't even work fine. Also, finger scanner got slow, and I have troubles with mobile network. I'm afraid of finding more failures as I use it.
So, if someone is reading this and get the notification, please scrap it and don't install the updates unless you hate your phone.
Click to expand...
Click to collapse
You need to do two things: change slots and wipe dalvik.
Code:
fastboot set_active a
1. Change slots can be done with fastboot or twrp
2. Wipe dalvik can only be done with twrp that can decrypt your internal storage...
If you are really lucky, changing slots will be enough.
Background: Daisy has two slots. In every slot there are all the partitions, the phone needs to boot - so you have some kind of backup.
Only data is not double. Normally you are on slot a. When you get an update, it will be installed to slot b and after that it changes to b to boot the new partitions.
I changed the slots after updating to 10.0.3.0 and wondered, why my phone was again 10.0.2.0... So, if you are lucky, you can just change slots with fastboot.
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Thanks it works great
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
AwkwardUberHero said:
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
Click to expand...
Click to collapse
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Thank you so much for the link to this!
I reported it as an issue right after I saw it, but had not heard back.
I appreciate you linking me.
This fixed my problem with face unlock. Thanks so much ?
What does this do exactly? My wife's face unlock works but she has a constant notification to re-enroll. I told her if she did that it most likely wouldn't work unless she factory resets. Honestly the notification being there annoys me more than her but she refuses to factory reset. I would just try it and see if it was my phone but I'll be sleeping in the backyard if I screw hers up for any length of time....lol
Worked perfectly on my phone! Spreading the word! Thanks for the module!
https://twitter.com/kingbri_aahs/status/1258148276513189888
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Hey man thanks, I tried it. It didn't work for me. I wish you nothing but the best of luck with this fix bro. It's really needed. I miss my camera lol
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
This worked for me, Pixel 4 not XL
On may factory image
Thanks
TechOut said:
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
Click to expand...
Click to collapse
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
It's working for me aswell on May version. Could you explain where Is the problem? What does this module?
tmoore3496 said:
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
Click to expand...
Click to collapse
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Okay there seems to be a lot of confusion from people in this thread so while I am not the OP I will try to clear things up.
Some people are having face unlock issues that can first be observed when setting the device up after flashing April and/or May images. During set up, it will say something along the lines of "Could not enroll face ID" or "Hardware not available" if dirty flashing one of the updates.
Some of us are having this issue even if we never upgraded to the Android R Developer Preview 3 or 4.
Others of us are having the issue after trying the DP 3/4 then rolling back to Android 10, April or May update.
The last monthly update that did not have Face Unlock issues for any of the above affected is March.
This module is created to help fix that and get Face Unlock working again and it is a Magisk Module that requires root to install.
However, a small few are still having issues even after trying this module (from my understanding).
You do not need this module if your face unlock works on April/May updates because this seems to be a kernel related issue that only affect some for a weird reason that I am too lazy to research right now. I'm sure this will be updated in the coming months.
So if you're Face Unlock doesn't work on April or May update, try this module. If it still doesn't work, you can use the March update and Face Unlock will work. There are no feature changes between now and March update. The March update include the auto dark mode, and the other feature drops from that month. Both April and May are only security patches and very minor fixes. While it is not the latest security patch you still have all the latest features.
Awesome!
Worked perfect on my pixel 4 xl. Flashed dev preview and got the enrollment error. Thanks for your module! working like a charm on May update
fuadtaufiq said:
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Click to expand...
Click to collapse
yeah April, May update breaks it, but magisk module fixes it. Temporary fix until Google fixes it.
anyone tried this on Jun update...
i will try, no need to wait
will report back...
---------- Post added at 04:14 PM ---------- Previous post was at 04:03 PM ----------
Adnansaeedhamed said:
anyone tried this on Jun update...
i will try, no need to wait
will report back...
Click to expand...
Click to collapse
i can confirm this working perfectly with me in Jun update
Hi! This happened to me today:
I installed the Android 11 Public Beta 1 today from June Android 10 version. I have an unlocked 4 XL. I flashed (trough fastboot) the June update and my facial recognition got broken. I did factory reset it but nothing was fixing it. I went back to Android 11 Public Beta 1 and it worked. Then I downloaded and flashed January Android 10 version and it is working right now. Will update if after setting it up and updating it to last update will still work.
basically what this does is patches sepolicy and adds the files required for face unlock. If you run a dmesg when trying to enroll there is something blocking the process from finding the files(likely sepolicy)