Related
I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.
danifunker said:
I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.
Click to expand...
Click to collapse
cool beans...im on pa_ca as well...but sticking on HC for now to crack the darn sbk.
they must be planning future updates as your image version still looks like it could be a release candidate. :-D
glad to hear theres several builds being pushed tho!
Sent from my SGH-I897 using xda premium
I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?
on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine
rising power said:
I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?
Click to expand...
Click to collapse
I've the same problem, not italian language and "PA_CA" Build.. WHY ??
i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((
ptesmoke said:
on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine
Click to expand...
Click to collapse
Hehe cool, when it comes to phones, I need a keyboard, so I actually picked up a bell Moto xt860 and unlocked it. I might be stuck with this one for a while since I hear keyboard android phones don't sell as well as blackberries up here. We will see what happens to RIM...
My other goal is not to sign another contract again, and I have a really sweet deal with Rogers now also...
Sent from my XT860 running ICS
devitos said:
i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((
Click to expand...
Click to collapse
It really looks like PA_CA is geared towards Canada, with only English, French and Chineese (simplified and traditional). I don't know another way of pulling another language, unless you can grab them from the WW 014 package somehow... let me look at it
Sent from my XT860 running ICS
I am very interested - how Canada firmware got in Russia)))
acer have a bug in service
Isn't possible flash directly Acer_A100_AV041_1.014.00_COM_GEN1 ? (to gets languages)
This is the third post today I have read someone say that the build 14 is not official. I have myself and numerous other people received this update OTA from Acer. Unless Acer is beta testing on our devices, you can't call it anything but official. It is the exact same rom ZN posted.
devitos said:
I am very interested - how Canada firmware got in Russia)))
acer have a bug in service
Click to expand...
Click to collapse
I've just buyed my own one here in spain and it comes with the PA_CA firmware as well
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.
Invalid_GR said:
Hello everyone I did a quick search and couldn't find anything.I would like to know who handles the updates for the CM version of the phone. Is it Oppo or the CM team? Will there be OTA updates or do we have to manually download and install?
Thanks in advance.
Click to expand...
Click to collapse
Software should be coming out tomorrow, can't wait.
Cyanogenmod does have their new CM Installer software for Windows and Android. If you're not familiar with fastboot, installing recoveries, and all that....it may be the easier way to go....in fact, I'm curious to try it myself.
http://www.tomshardware.com/news/oppo-n1-cyanogenmod,25495.html
I am more interested to see how this will work not only for the N1 but for future CM phones.
Imo if they want to go official they should provide the stable versions OTA to begin with.
Harfainx said:
CM will handle the CM version. Oppo will supply updates to their software, but CM will handle the actual ROM itself.
Right now there's only one build released. I have a new build that I'm checking out now, but it's still on 10.2. We should see CM11 very soon, and I predict that it will come with the official Google software built in, so there won't be a need to flash gapps. I might be wrong about that, but I think that's how it will work.
I'll post the link for the update very soon in the correct section.
Click to expand...
Click to collapse
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Only the released version of 10.2 has been approved by Google.
Entropy512 said:
I'm fairly certain that CM11 won't have included gapps until an official "stable" release occurs.
Click to expand...
Click to collapse
I'm talking about the official build of CM11. Steve Kondik has informed me that the build is almost ready to roll. They're just waiting on a few last details... Which I assume is the inclusion of gapps.
Sent from my HTCONE using Tapatalk
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Flash with stock recovery?
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
You will not be able to flash this with the stock recovery. I imagine once it goes stable CM will push out an official update that will work on the stock recovery setup.
Until then, TWRP works great: http://forum.xda-developers.com/showthread.php?t=2537080
dryll said:
Is there a way to flash a nightly build with the sotck recovery? If not how to change the recovery? Thx
Click to expand...
Click to collapse
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Harfainx said:
I bet I could make that happen. Probably just a reverse of what I do to make it flash in TWRP instead of stock. I bet I could add the first line back in and have it flash properly.
Click to expand...
Click to collapse
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
mcteague said:
Flashify works great for installing TWRP, just backup your stock recovery first, that way you can flash it back before rebooting recovery and flashing colour OS. 27th Nightly is available.
Click to expand...
Click to collapse
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Harfainx said:
I meant flash nightlies in stock recovery. I have TWRP on mine, but I bounce back and forth for testing.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Entropy512 said:
I'm 90% certain stock recovery will not flash nightlies, as it will only flash ZIPs signed with specific signing keys.
Unless CM is signing their nightly ZIPs with the same key as their "official" releases, which is highly unlikely.
Click to expand...
Click to collapse
Correct. Currently since they're coming direct from CM as nightlies, they aren't final stable versions. Those will be released like the other two were, and I'm sure will be built to flash in the N1 Stock Recovery.
Location not working
location still not working on latest nightly (130214).
anyone has any idea on how to fix it? the 240114 nightly is not longer on the getCM servers.
Anyone on M6? Thoughts?
I went straight from CM10.2 (CM edition N1) to 11 M6, so I don't know how battery life compares with Omni or other ROMs... would love to hear from those of you that have tried other ROMs and can compare with M6.
With M6, I am getting ~4% battery drain over 7 hours overnight (2G network on only).
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Hi,
I am trying to install Cyanogend mod. N1 a OPPO
The steps are simple, but not working,
I've tried: (http://download.cyanogenmod.com/?device=n1&type=snapshot)
** Cm-11-20140804-SNAPSHOT-M9-n1
cm-11-20140805-NIGHTLY-N1
cm-11-20140124-EXPERIMENTAL-n1.zip
They all show the same error.
"Installation failed"
I downloaded the. zip for wifi, ethernet MAC, WINDOWS ........ and still shows the same error.
:crying:
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Sorry to bump a 3 year old thread for such an unrelated reason, but you have PMs disabled, and, well, CM11 is not that appealing anymore so I'm confident not many people are gonna read this anyway [any mods reading this, please spare my soul :silly: ]
That said, I just wanted to ask you why you rated my porting of LAOS 15 Trebuchet so poorly, since you didn't leave any comment; if it's some bug, crash or other error i can look into it.
BTW you can answer me on the app's thread if you wish (https://forum.xda-developers.com/android/apps-games/app-lineageos-15-trebuchet-laucher-rom-t3667436)
ThommmF said:
They are released officially und http://download.cyanogenmod.com/?device=n1 :victory:
With the lastest "cm-11-20140126-NIGHTLY-n1.zip" I get no location data - wich makes the N1 unusable for Maps, Foursquare, Ingress aso..
Switches back to "cm-11-20140124-NIGHTLY-n1.zip" everything works fine again.
Click to expand...
Click to collapse
Thank you for leaving your feedback, here are some answers to your points:
- (update mechanism) i actually caught a nasty bug in XDA Labs web console which prevents me from uploading new builds there (and I also deleted all previous reviews in the attempt to reupload the app ??); (i already filed a bug report and managed to get the dev's attention so I hope it gets fixed soon)
- (open source) being a porting, the app mostly shares the original staging/trebuchet15.1 source code, with only a handful edits for fixing crashes due to compatibility errors (and is built with gradle plugin 2.3.3 instead of 3.0.1)
- (very buggy) it inherits all current staging/trebuchet15.1 bugs, not that much from my tests, but yes, there are some
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Update has landed. Found links on teammt site few moments ago.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v133897/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L24_hw_usa/update_full_BND-L24_hw_usa.zip
http://update.hicloud.com:8180/TDS/...97/f1/full/public/update_data_full_public.zip
MD5 verified numbers ( from my working downloads)
Code:
e75a21769f049430840ea900b11600c4 c:\android\honor_7x\l24-oreo\update.zip
73414b5383e5fb3391e77a13c17dca53 c:\android\honor_7x\l24-oreo\update_data_full_public.zip
122f0e91d77fba6e399300926d1ef289 c:\android\honor_7x\l24-oreo\update_full_bnd-l24_hw_usa.zip
So can I just flash those update files with TWRP and be good to go?
I don't know if that's the stable or not, I've had that version for over a week now.
My update says C567?
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
johncro13 said:
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
Click to expand...
Click to collapse
Why would it be available if it's not official? I don't get that lol. The app is a little funky.
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
mparma13 said:
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
Click to expand...
Click to collapse
I'd say weeks, but that is just a hunch based on my experience with the rollout of the previous two patches... Once again, it would have been nice when Honor USA announced it that they didn't just say "Coming April 30" but instead were a bit more honest about how the release was being pushed out.
They shoyld have said that it will be around a certain week or something cause the frustrating lag is killing me badly and i even have a Oneplus 5t...but still is the worst lag i have seen in since 2013
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
mrmazak said:
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
Click to expand...
Click to collapse
How did you install it?
allrockedout said:
How did you install it?
Click to expand...
Click to collapse
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
mrmazak said:
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
Click to expand...
Click to collapse
Ok thanks I'm on stock bootloader still locked I'll just wait for official update
yeah....
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Looks like they crapped the bed on the update....
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this hype about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
pcaseiro said:
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this the about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
Click to expand...
Click to collapse
Well some group is getting it(probably beta testers), because it is on firmware finder
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
allrockedout said:
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
Click to expand...
Click to collapse
Then why would they be so set on the 1st, shouldn't they have said the 2nd? Lol
Anyone receive official update yet?
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...