Related
Q&A for [ROM][4.4.4][Unofficial] Carbon KitKat - Togari[2014-10-18]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
NFC not functional
On my Z Ultra, the NFC service seems to use a lot of battery. I went into settings to turn it off, but upon touching, it went grey but still ticked. Leaving that screen and going back into it reveals the NFC still ticked but not grey. Having to remove NFC service to prevent battery drain. Also, even NFC being on doesn't work with tags or anything. Any suggestions? Thanks heaps
Problem with sensors
Accelerometer, light, orientation, proximity, gyroscope and magnetic sensor no longer work on latest carbon (build 33)
Is there anyone else with the same problem?
Hilmhaz said:
Accelerometer, light, orientation, proximity, gyroscope and magnetic sensor no longer work on latest carbon (build 33)
Is there anyone else with the same problem?
Click to expand...
Click to collapse
I had the same problem on LiquidSmooth built from source. A build from around 26 September worked fine, so it seems there's something later than that causing it. I tried reverting some commits related to sensors, but was unable to find the cause of the issue. Maybe @OmarEinea knows. Someone reported it in PAC's thread on the Z1 forum, too. I also had to revert the latest media-caf-new commits to even get through the build using the SaberMod toolchain. Back to earlier builds for now, but it's still awesome.
Triflot said:
I had the same problem on LiquidSmooth built from source. A build from around 26 September worked fine, so it seems there's something later than that causing it. I tried reverting some commits related to sensors, but was unable to find the cause of the issue. Maybe @OmarEinea knows. Someone reported it in PAC's thread on the Z1 forum, too. I also had to revert the latest media-caf-new commits to even get through the build using the SaberMod toolchain. Back to earlier builds for now, but it's still awesome.
Click to expand...
Click to collapse
There was a few updates from themuppets that may have broken things
blueether said:
There was a few updates from themuppets that may have broken things
Click to expand...
Click to collapse
Good call! Thanks!
This is the commit that broke sensors for me. I'll try a CM11 nightly later and try to report the issue if it's present there.
Any chance that the sensors may be fixed soon? It's pretty inconvenient atm.
341464 said:
Any chance that the sensors may be fixed soon? It's pretty inconvenient atm.
Click to expand...
Click to collapse
I'm away for the weekend so cant look into it. My only suggestion is to roll back to the backup you made befor flashing or to flash an older build (if you flash an older build you will probably need to wipe data)
blueether said:
I'm away for the weekend so cant look into it. My only suggestion is to roll back to the backup you made befor flashing or to flash an older build (if you flash an older build you will probably need to wipe data)
Click to expand...
Click to collapse
I just got this device literally 12 hours ago, so no previous backup exists. Flashed Carbon immediately I got the device and probably chose a wrong time.
I can wait though, since I had spent hours setting the device up, don't really wanna do it all over again.
341464 said:
I just got this device literally 12 hours ago, so no previous backup exists. Flashed Carbon immediately I got the device and probably chose a wrong time.
I can wait though, since I had spent hours setting the device up, don't really wanna do it all over again.
Click to expand...
Click to collapse
Carbon build 32 should be fine (problem only with bluetooth) but build 30 and earlier is recommended if Bluetooth is a must.
I did dirty flash build 32 on top of build 33 and it somehow work, but not recommended
Hilmhaz said:
Carbon build 32 should be fine (problem only with bluetooth) but build 30 and earlier is recommended if Bluetooth is a must.
I did dirty flash build 32 on top of build 33 and it somehow work, but not recommended
Click to expand...
Click to collapse
I'd rather wait for a new build, unless it isn't fixed in 2 weeks.
EDIT: Actually, wait, can't I just replace the sec_config with the older one?
EDIT 2: Yup, fixed by replacing the sec_config with the older one.
No problem now.
Is there a way I can change how "exact" or sensitive dt2w is? I can only get it to work for me every other time...I don't know if I am tapping to far from the other tap or what...I swear I am tapping in the same spot twice
KaBooMa said:
Is there a way I can change how "exact" or sensitive dt2w is? I can only get it to work for me every other time...I don't know if I am tapping to far from the other tap or what...I swear I am tapping in the same spot twice
Click to expand...
Click to collapse
You cant change the way dt2w works sorry
Thanks for the reply. I have been sitting here training lol....I think I got it figured out finally. I was just doing some weird stuff and it wasn't working.
any updates?
This rom is rip?any information about next updates?
kowkin said:
This rom is rip?any information about next updates?
Click to expand...
Click to collapse
The Carbon team have mostly moved on to LP, i'm just waiting for it to build and boot cleanly then there will be a LP lelease
I am not a big fan of the OS, i loved CM but none of the ROMs out there at the moment are any good. Is anyone else still using OOS or am I an odd man out
I'm using it because of horrible battery life on every CM baesd roms.
And I don't like how hydrogen works (app and memory management).
I am, waiting for CM13 with all working sensors
PhoenixNghi said:
I am, waiting for CM13 with all working sensors
Click to expand...
Click to collapse
Same for me! And I like to be able to disable a sim card like in Oxygen! In cm13 that option is not available.
Sent from my ONE A2003 using xda premium
I'm only still on it because of the fingerprint scanner. Once the API is complete I'm moving straight over to CM 13. I can deal with the lack of SIM card control but the fingerprint scanner is a must.
PhoenixNghi said:
I am, waiting for CM13 with all working sensors
Click to expand...
Click to collapse
This.
But I like the idea of @matitorres07 and his Sensed Hydrogen. I hope he will continue with that after final release of Hydrogen, or even maybe switches to CM
Waiting for the cyanogen build with all the sensors working...not sure when the same is expected.
Sent from my ONE A2003 using Tapatalk
I am also on Oxygen. I would maybe try CM13, once it would be official but I am happy with Oxygen OS with a different Kernel. Different kernel and a different launcher and everything is perfect
Waiting for Fingerprint Sensor support on cm13, all other "bugs", i can happily live with
jay_snake said:
Same for me! And I like to be able to disable a sim card like in Oxygen! In cm13 that option is not available.
Sent from my ONE A2003 using xda premium
Click to expand...
Click to collapse
So true... for me life is a full circle, After staying on oxygen forever, switched to Skydragon OOS and then took plunge to SD H2Os as I noted it was much more actively being used by its author. Then shifted to CM13 but not happy with all these ROMS as they buggy and have some or the other limitation... though I desperately want a stable CM13 ROM with all sensors working... hate the lack of official support for many the famous ROMS... but love my OPT
Just because I want a full working Phone, stay un OOS.
I'm on OOS coz of fingerprint scanner ...
Why should I be on other Roms without fingerprint support when I have a scanner in my phone ...
H2O marshmallow 6.0 is much faster and stable than OOS.. and it's finger print sensor work much quicker
Now that CM13 has fingerprint.. I'm no sure what else is missing from it now.. But there's just something about it.. It still feels 'clunky' to me.. My opinion and experience of course! But for now I'll stick with Oxygen... Can't wait for CM13 though!!!
ElfSt0ne said:
I am also on Oxygen. I would maybe try CM13, once it would be official but I am happy with Oxygen OS with a different Kernel. Different kernel and a different launcher and everything is perfect
Click to expand...
Click to collapse
I have this same argument Can't wait for oos with mm
See this all the time.. BS.. Oxygen and even more so with the last update. Is a solid ROM. Better battery than any cm 13 and smooth not bloted. Yep.. I said it. Oxygen is a good ROM. People are quick to jump on the hate train and 90% of them do it just because..some just don't know better.
i'm still with oxygen because of the finger print sensor
Since Grarak make fp working i have made swich
Doktor-X said:
Since Grarak make fp working i have made swich
Click to expand...
Click to collapse
I switched about a month ago. The fps is amazing on CM13, definitely up there with the phones that cost twice as much!
Thank you to all the developers that made this phone even better!!
Many are still on oxygen. Slowly shifting to CM13 now I guess. Let's see what OnePlus brings with M build soon. I'll pick the most stable one as I only have 1 phone which is this as a daily driver
Sent from my ONE A2003 using Tapatalk
Working:
RIL
Audio
Display
Bluetooth
Wifi
Sensors
Camera
Fingerprint
Broken:
VoLTE?
I will release when I want to.
o.o this one fixes the display error for internal storage space!
kgptzac said:
o.o this one fixes the display error for internal storage space!
Click to expand...
Click to collapse
you sure you were using an SD card (and the phone detects it)?
Jus sayin', I'm not gonna test it for now
P650SE said:
Yay! I have never been so excited in my entire life! BTW, how do you guys know the bug for internal storage space has been fixed, or is that just purely speculation? You kinda make it sound like there's already a download available for people who want to beta test.
Click to expand...
Click to collapse
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I suppose you're right. Neither Nougat or Oreo have brought significant changes, they have both been 'minor' updates with subtle changes to improve certain aspects of the OS. The last major update to Android was Lollipop, when the entire appearance was drastically overhauled from previous versions. I'm only excited because we just have to take what we're given, and any update to update the appearance and usability of Android after an entire year is a refreshing change! Even though Nougat was only a small update, it feels unbearable to me when switching back to Marshmallow without the new quick settings swipe-down; the one before the entire notification area appears. So even the small features can make a lot of difference to the overall experience! I'm still really looking forward to seeing the changes made in Oreo for myself when it comes to the Axon 7.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I don't get why people say this, honestly. Just because you didn't get a visual overhaul like you got from KitKat to Lollipop doesn't mean there weren't significant changes. Visually the OS is already at a level where there's no need for a major change (it has been "ready" since Lollipop, imo; Marshmallow, Nougat, and Oreo have all had small visual tweaks but have stuck to the Material language), and most of the tweaks work "under the hood." Oreo will bring Project Treble, which may just be the most significant change in Android in the last few years. It also brings improvements on the behavior of notifications and background services or apps. It's an incremental update, yes. But it's by no means a small update.
@Gases
We talked about excitement.
I mentioned the problems with the new OS updates, which brings maybe more security but also many problems to custom ROMs. Furthermore there are more problems in the first months. I don't need visual tweaks.
Project treble is mainly positive for stock ROMs. We will see, in which way custom ROMs can profit of this new feature.
Background battery eating apps are no problem on custom ROMs based on LOS, if you use the internal features or external apps. But again. It's nice to have already implemented.
Finally I am always thankful for all kind of ROMs and kernels devs provide to the community. And I was always someone who donated to say 'thank you'
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
ethanscooter said:
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
Click to expand...
Click to collapse
I am not the dev but this is probably more a promotion thread. Final builds will surely be on developement thread.
Some devs are working on oreo right now.
Let's wait and be thankful for their work.
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
OrdenKrieger said:
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
Click to expand...
Click to collapse
Does cellular data work?
ethanscooter said:
Does cellular data work?
Click to expand...
Click to collapse
Yas.
What about the speakers? Do they have the same problem as before the fix was found?
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
Probably since they just got audio to work and the ROM is very experimental.
Really looking forward to testing this when the first release is posted on the forums. I'm just hoping the camera and fingerprint sensor will be relatively simple to fix. Thanks for everything you've done so far!
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
ethanscooter said:
Probably since they just got audio to work and the ROM is very experimental.
Click to expand...
Click to collapse
Audio is working normal. Like on cm14.1 both speakers are working just fine.
yes.. you are the man!
hopefully cam and fingerprint will fixed soon.
thanks ordenkrieger and all others
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
That would be nice and all, but I think the devs want mostly everything to work for those that prefer to have a stable build and etc.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
I was just looking over in the Nexus 6 forms and to overcome the camera issue for them they had to upgrade from 7.1.2 - 8.0 and then restart the phone. So there is hope especially since the Nexus 6 is a 32-bit phone and I'm pretty sure 8.0 was supposed to be 64-bit.
I see los 16 has gone live for a few devices. Oddly enough the station klte has gotten it. I installed it on one of my s5s last night and just updated to the latest nightly. It runs excellent. But I wonder why the 6p wasn't included in this first round. Or the pixel XL. I know there are pie roms for the 6p I see them here but I also see the unoffical lineage 16 for the 6p hasn't had any progress at all thread is dead in the water. I hope that doesn't mean the 6p is being left out.
If it is can anyone tell me which one of the pie roms on xda are the most stable. The 6p is my wife's phone and she doesn't know how to deal with random issues. Los 15.1 was great for this phone I was hopping 16 would be too.
Keep it on Oreo for now. I have tried couple of Pie ROMs and they run pretty slow
Pretty sure there'll be official LOS16 for our devices. So waiting....
We just have to wait for a dev to pick it up and get it to spec for them to host it as official. I hope someone picks up the mantle as my Nexus 6P is still going strong and LineageOS 15.1 has been the best things to happen to it since I changed the battery.
stay on los 15.1/stock
current pie roms have major issues
nardow said:
stay on los 15.1/stock
current pie roms have major issues
Click to expand...
Click to collapse
Might want to specify why you have major issues, because this is misleading.
I've been on AICP 9.0 for a month and i have not had many, if any issues.
Lawlrus said:
Might want to specify why you have major issues, because this is misleading.
I've been on AICP 9.0 for a month and i have not had many, if any issues.
Click to expand...
Click to collapse
On the ROMs I tested, which were all based on Statix sources, I had these issues:
Battery life is a lot worse than stock/aosp/los;
Overall performance is worse than stock/aosp/los;
Phone gets hotter than in stock/aosp/los;
Camera doesn't work properly (sometimes it does, sometimes it doesn't);
I'm about to install AICP Pie and give it a go.
nardow said:
On the ROMs I tested, which were all based on Statix sources, I had these issues:
Battery life is a lot worse than stock/aosp/los;
Overall performance is worse than stock/aosp/los;
Phone gets hotter than in stock/aosp/los;
Camera doesn't work properly (sometimes it does, sometimes it doesn't);
I'm about to install AICP Pie and give it a go.
Click to expand...
Click to collapse
I can't really comment on those builds because im too lazy to wipe my entire phone to go to fbe, but aicp has been working great for me. Sure the battery life is worse than 8.1 which is to be expected, but I haven't thought it was too bad.
The aicp guys have done a bunch of kernel work, sadly their newest build doesn't have the most up-to-date kernel, but I ran it for a few days, and the kernel still runs well. But I feel like the next build after the 3-5 one will be even better, since they remembered to push the kernel work back in.
The only ROM I've had huge battery issues with was aosip because for some reason the small portion of the kernel has its min freq set to 1200 instead of 380 or whatever the norm is, and setting the min lower doesn't stick well.
One way I got around this was using one of the savageone's custom kernels. He put out two test kernels that have both ran well for me based off of the common used fbe source staticx, and fde which wsd based off neo's source. Both kernels run about the same for me and work on either encryption type.
Lawlrus said:
I can't really comment on those builds because im too lazy to wipe my entire phone to go to fbe, but aicp has been working great for me. Sure the battery life is worse than 8.1 which is to be expected, but I haven't thought it was too bad.
The aicp guys have done a bunch of kernel work, sadly their newest build doesn't have the most up-to-date kernel, but I ran it for a few days, and the kernel still runs well. But I feel like the next build after the 3-5 one will be even better, since they remembered to push the kernel work back in.
The only ROM I've had huge battery issues with was aosip because for some reason the small portion of the kernel has its min freq set to 1200 instead of 380 or whatever the norm is, and setting the min lower doesn't stick well.
One way I got around this was using one of the savageone's custom kernels. He put out two test kernels that have both ran well for me based off of the common used fbe source staticx, and fde which wsd based off neo's source. Both kernels run about the same for me and work on either encryption type.
Click to expand...
Click to collapse
thanks for the info on the aicp kernel. i'll wait for the next build to flash it. good to hear aicp is fde
mojorisin7178 said:
I see los 16 has gone live for a few devices. Oddly enough the station klte has gotten it. I installed it on one of my s5s last night and just updated to the latest nightly. It runs excellent. But I wonder why the 6p wasn't included in this first round. Or the pixel XL. I know there are pie roms for the 6p I see them here but I also see the unoffical lineage 16 for the 6p hasn't had any progress at all thread is dead in the water. I hope that doesn't mean the 6p is being left out.
If it is can anyone tell me which one of the pie roms on xda are the most stable. The 6p is my wife's phone and she doesn't know how to deal with random issues. Los 15.1 was great for this phone I was hopping 16 would be too.
Click to expand...
Click to collapse
It's definitely work in progress. I see a topic "angler-p" on LineageOS gerrit. So people are working on it.
https://review.lineageos.org/q/topic:angler-p
Waiting patiently with baited breath for L16 to hit N6P. It's a match made in heaven! :fingers-crossed:
Anyone have any news on this?
copong said:
Anyone have any news on this?
Click to expand...
Click to collapse
The official lineage 16 as it seems will not happen most likely, development seems to be dead.
sage of six paths said:
The official lineage 16 as it seems will not happen most likely, development seems to be dead.
Click to expand...
Click to collapse
Not true. Check the unofficial los16 thread. AndyYan is working on a new build
Sent from my Nexus 6P using XDA-Developers Legacy app
serdel_elo said:
Not true. Check the unofficial los16 thread. AndyYan is working on a new build
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
True dat, he should just change the thread name to official if his build is the official one, so people don't question about official build anymore.
And the new build is out
Sent from my Nexus 6P using XDA-Developers Legacy app
sage of six paths said:
True dat, he should just change the thread name to official if his build is the official one, so people don't question about official build anymore.
Click to expand...
Click to collapse
He isn't doing official builds. So why would they be called official?
Lawlrus said:
He isn't doing official builds. So why would they be called official?
Click to expand...
Click to collapse
Well as far as i'm concerned is it official or not, i don't really care, as long as it's good. He did say in one of his first post when he gave his first build something along the lines of this is a peek of the feature set of los 16 as it is official / feature complete. So does it make it official or not i do not know.
sage of six paths said:
Well as far as i'm concerned is it official or not, i don't really care, as long as it's good. He did say in one of his first post when he gave his first build something along the lines of this is a peek of the feature set of los 16 as it is official / feature complete. So does it make it official or not i do not know.
Click to expand...
Click to collapse
The los devs are very strict with how they run official builds, originally he had added the lock screen deals that would make it non official, since they have merged it, that would cover that, but he also messes with the kernels fstab thus making it non eligible.
I don't know all of the specifics of being a maintainer for them, but there are guidelines for the hals and blobs and **** they have to use as well.
Lawlrus said:
The los devs are very strict with how they run official builds, originally he had added the lock screen deals that would make it non official, since they have merged it, that would cover that, but he also messes with the kernels fstab thus making it non eligible.
I don't know all of the specifics of being a maintainer for them, but there are guidelines for the hals and blobs and **** they have to use as well.
Click to expand...
Click to collapse
Well i don't care all that much about that, tell it to the guy above who asked is there official rom or not lol. What i do care about is winxuser making that aosp nfc issue gone, and i'm waiting for the news form that department
darkriff said:
Keep it on Oreo for now. I have tried couple of Pie ROMs and they run pretty slow
Click to expand...
Click to collapse
agreeeed. Pie roms don't work well on the Nexus 6P. Oreo was the last stable operating system for the Nexus 6P, so of course pie roms won't work as well, and i've tried a lot of them.
To name a few: Pixel Experience, DotOS 3.0, StatixOS, AOSiP Pie Beta,[ Pie - 9.0.0_r37] AOSP , Ressurection Remix, AICP all these i've tried they all have this lagginess about them and they're not as snappy as the roms on Oreo ot stock Oreo for that matter.
And the brightness sucks on pie too.
I'm currently running LineageOS 15.1 runs like a dream on my Nexus 6P.
Not to take anything away from the developers of pie roms though, they're all doing fantastic jobs to keep our Nexus 6P's alive
hi two nights ago when i found out that the beta program has changed and i'm not ever going to get a stable build i decided to unenroll my p6 from beta program. The issue is i got the update notification immediately like i always have in the past. Except this time the phone never rebooted when i went to apply the update. so after an hour of just letting it sit I tried to power it on and got the splash screen that usually comes up when you try to boot into recovery where you have to select recovery except there was no option for recovery. And even worse there was a message at the bottom of the screen that said there is no operating system installed on this device and gabe a website to go too. my heart jumped into my throat. But i regained composure and powered off the phone and started to prepare to use the android flash tool (unsure if that was even the right step to take) but then i looked at my phone and saw that the erase ring like when you factory reset was there. so i decided not to touch it and let it do its thing. So now my phone did factory reset which i am aware that when you unenroll that is what happens but it did not install the latest stable build. Weird right? So now I am still on s3b1.220218.004 Which if im not mistaken is the newest beata build which i was on before i started. My security update says march 2022 my play system update still says february 1 and when i go to the android beta website it says that my phone is unenrolled in the beta program!!!!
So does anyone know how i get back to the stable channel now? I am lost any help would be greatly appreciated.
Thanks for being an experienced Android tester.
Your post will help people that are not sure what to do incase things go sideways.
I am on stock and from what I have learned is if you install a newer android system. You can not go back. That is why I stayed away from beta testing. Unless things changed that I don't know about, your stuck.
The only thing as a stock user is to try downloading the full factory image and do a flash-all.
vandyman said:
Thanks for being an experienced Android tester.
Your post will help people that are not sure what to do incase things go sideways.
I am on stock and from what I have learned is if you install a newer android system. You can not go back. That is why I stayed away from beta testing. Unless things changed that I don't know about, your stuck.
The only thing as a stock user is to try downloading the full factory image and do a flash-all.
Click to expand...
Click to collapse
Thank you for the answer. I did read that too but I didn't think it would apply in this situation. Oh wait I forgot the p6 hasn't gotten the latest security update yet. So your right I would be going back to February. Well hopefully since I am no longer enrolled in the beta program I will not receive anymore beta builds and either when March stable is released I will get that. And if that's is considered going back then I will have to wait till April thank you for bringing this to light. Man I wish Google would have given more of a heads up. If I knew I would not have installed this latest beta and stayed on beta 3. But I thought I was getting 12L stable. If I stayed on beta 3 and then unenrolled I would not have had a problem.
I am glad this will help others as I have received so much help on xda. In fact I learned everything I know from xda I do not work with computers I am a cook and a shellfish farmer. I see you helping alot of people so thank you for that. Keep up the good work my friend.
vandyman said:
Thanks for being an experienced Android tester.
Your post will help people that are not sure what to do incase things go sideways.
I am on stock and from what I have learned is if you install a newer android system. You can not go back. That is why I stayed away from beta testing. Unless things changed that I don't know about, your stuck.
The only thing as a stock user is to try downloading the full factory image and do a flash-all.
Click to expand...
Click to collapse
One more question. I know it might sound silly but if I'm on the latest beta which is for the next feature drop if I understand correctly then shouldn't this at least have the code for 12L stable in it? Because I don't seem to have any of the latest feature drop stuff. Also oddly enough my wife has the pixel 5a and she is on stable channel and she has all that feature drop stuff plus she also has the newest version of Google's messages app. With the catagories at the top. Shouldn't I have that by now?
Sorry for the weird question.
The March beta build was released on Wednesday so the most likely case is that your phone has "automatic system updates" turned on (default) in developer settings & that the phone had probably already updated your OS in the background (overnight) before you unenrolled. Due to the pending reboot to finish installation of the QPR3 Beta 1 (a newer build than February), it is likely that whatever controls the unenrollment/system update noted that you are on a later build & only wrote the bit to wipe your device upon reboot rather than attempting to downgrade to Feb build, because an newer update was already pending installation.
If your bootloader is unlocked you should be able to flash February build with fastboot, if not you may be able to sideload the full February OTA in recovery mode, or re-enrolling and then unenrolling again should work to go back to a stable build. You absolutely can "downgrade" if coming from a beta, or just manually flashing. (Edit: or with Android recovery tool)
RE: your second question, QPR3 Beta 1 has none of the March builds feature drop stuff in it, yet, which is why you won't have the same features as your wife's 5A.
DanielF50 said:
RE: your second question, QPR3 Beta 1 has none of the March builds feature drop stuff in it, yet, which is why you won't have the same features as your wife's 5A.
Click to expand...
Click to collapse
I'm running QPR3 Beta 1 and it seems like I have at least some of the feature drop stuff, including the new battery widget, Gboard custom stickers, and I believe the expanded stuff in At A Glance.
This build does include the March security update so I would think it would include the feature drop stuff as well.
Lughnasadh said:
I'm running QPR3 Beta 1 and it seems like I have at least some of the feature drop stuff, including the new battery widget, Gboard custom stickers, and I believe the expanded stuff in At A Glance.
This build does include the March security update so I would think it would include the feature drop stuff as well.
Click to expand...
Click to collapse
I should have been a little more specific, sorry for confusion lol.
I got the AAG widget in Beta 3 through a update on the Play Store so I assume that everyone would get this widget even outside of 12L (12.1), and believe that the Gboard stuff is also pushed by a server side update for US English? So those definitely work for most, I think.
I am only going off my experience and things I've heard online from other people though - Snap at night, live translate (of the new languages) and recorders transcription of Italian/Spanish (+assistants quick phrases) don't work for me on the QPR Beta 1. I can't say if Captions in calls work on this build though as I think that's a US only drop.
Google actually dropped the "Feature Drop" part from the Beta page too, so 100% unsure of what the QPR builds will actually entail now.
DanielF50 said:
Google actually dropped the "Feature Drop" part from the Beta page too, so 100% unsure of what the QPR builds will actually entail now.
Click to expand...
Click to collapse
Yeah, seems like the QPR Beta builds will be mostly updates to the QPRs rather than actually testing any feature drop stuff. Hopefully they'll mix in a bit of those though. I'm actually ok with that as the QPR Betas should include some non-security fixes, so that's at least something to stay ahead of the game a bit.
Lughnasadh said:
Yeah, seems like the QPR Beta builds will be mostly updates to the QPRs rather than actually testing any feature drop stuff. Hopefully they'll mix in a bit of those though. I'm actually ok with that as the QPR Betas should include some non-security fixes, so that's at least something to stay ahead of the game a bit.
Click to expand...
Click to collapse
Ok I am.actually still on the feb 1 Google play system update. Despite getting numerous updates this month each at 761 kb. For some reason I get those updates much much later than everyone else. Even my wife. It's only been with the pixel 6. All my other pixels were fine.
mojorisin7178 said:
Ok I am.actually still on the feb 1 Google play system update. Despite getting numerous updates this month each at 761 kb. For some reason I get those updates much much later than everyone else. Even my wife. It's only been with the pixel 6. All my other pixels were fine.
Click to expand...
Click to collapse
I don't think anyone's getting Play System updates very quickly at the moment - Google pushed February's update out over like 5/6 different parts, from what I can remember - mine only started showing "February 2022" when I manually updated a related system app on the 27th of Feb, so I'd expect March's Play System update to be pushed slowly over the month too.
DanielF50 said:
I don't think anyone's getting Play System updates very quickly at the moment - Google pushed February's update out over like 5/6 different parts, from what I can remember - mine only started showing "February 2022" when I manually updated a related system app on the 27th of Feb, so I'd expect March's Play System update to be pushed slowly over the month too.
Click to expand...
Click to collapse
Yeah I noticed that too. It just happened to start when I switched to Verizon from fi. I thought that maybe I was getting some Verizon parts injected into my phone. I guess it was just coincidence. What app did you update that caused it to change dates?
mojorisin7178 said:
Yeah I noticed that too. It just happened to start when I switched to Verizon from fi. I thought that maybe I was getting some Verizon parts injected into my phone. I guess it was just coincidence. What app did you update that caused it to change dates?
Click to expand...
Click to collapse
These apks from ApkMirror, once they were updated to February - https://forum.xda-developers.com/t/playstore-update-february.4399625/page-4#post-86493165
No March updates available yet though.
Well hopefully today the stable channel will get it's March update. Then hopefully I will get the ota to move me to stable channel. If not then I am going to try the android flash tool to see if I can get back on stable releases.
vandyman said:
Thanks for being an experienced Android tester.
Your post will help people that are not sure what to do incase things go sideways.
I am on stock and from what I have learned is if you install a newer android system. You can not go back. That is why I stayed away from beta testing. Unless things changed that I don't know about, your stuck.
The only thing as a stock user is to try downloading the full factory image and do a flash-all.
Click to expand...
Click to collapse
So it looks like Google might have released the stable March build. I am at work and haven't had a chance to read anything yet but I just got an update for 451mb and it says it's for the latest stable release of android 12. I just.left my phone on the way it was and didn't re enroll in the beta program. It looks.like it finally caught up for me. It's going to wipe.mymphonenagain so I'll report back after I'm all setup.
Edit: so I just looked on Google website and I do not see the March build yet. I really hope that I'm not going back to February that would not make any sense. I thought you that you can't go backwards with the builds.
so i just went through the whole proccess and it did not put me on the latest stable build im still on the same one. I guess that they did not come out with the march stable update. But the weird thing is it did the same thing it did last time. when i finished the download and restarted my phone the boot menu came up with a message that said no vaild operating system. and i could not boot into recovery or do anything at all. i just let it sit and powered it off waited a minute and powered it back on and it gave the erasing ring. then rebooted. Is that normal now? it has never done that before the last two times