Related
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
My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?
Download it on the kindle, flash the zip from inside of twrp, reboot into twrp again and you will notice the version is newer. If you have issues downloading the zip on your kindle just tell me I could temporarily host it somewhere for ya.
Sent from my Amazon Kindle Fire HD using Tapatalk
aakashba1001 said:
My laptop blew up a capacitor, i have twrp 2.6 x x i we need 2. 7 x x for cm11. Is there a way to update without a pc ?
Click to expand...
Click to collapse
you can download HashCode's TWRP Here:
http://forum.xda-developers.com/showthread.php?t=2218802
and install from your current TWRP, just as you flash a ROM.
Thanks guys
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
CM nightly build works good for me, you don't need to wiping new buld everyday, just choise one.
CM team will release a new month build every month, that build will be better than nightly build.
It takes time for the CM team to build a ROM with no bugs, so, just be patient.
I installed the 4/14 unofficial CM11 build that Hashcode posted over in development and am stunned at how well it works! I'll be sticking with this one for the interim. The TWRP upgrade is necessary, but Hashcode made it easy (see link in gatalon's post). In my case, I think it may have even fixed a long standing issue I had.
I've had my kindle HD 8.9" for over a year now, and have always been disappointed with it's performance. Even after I rooted it and put the CM10.1 build on it, it still exhibited weird sluggish, unresponsive behavior. This upgrade to TWRP 2.7 and CM11 has made all the difference in the world. All the weird sluggishness is magically gone.
It was noticeable as soon as I used TWRP 2.7 to wipe everything out. I'm half suspecting I had something wonky going on with the file system that wasn't getting addressed with the older version of recovery. I noticed 2.7 explicitly states that it's calling mkfs during the wipe process where the older version didn't. My uneducated theory is that the older version, 2.6.0.0, just deleted everything where the newer version is actually re-formatting the partitions. I could be way off base though. Just happy it's finally working like I thought a piece of hardware like this should! :victory:
aakashba1001 said:
thanks both of ya, one last question.
for the official cm11 release, the nightly mean u guys keep wiping and installing new os everyday ?
Is there any older release with no bugs ? If they did nightlies for older versions, one of them must have all bugs fixed right ?
Click to expand...
Click to collapse
No wipe is needed (normally) when updating from one CM official nightly to a subsequent one. It will even detect if the engine has changed and recompile the davlik cache as needed. Personally, I'm a big fan of wiping cache (and only cache) with each new build and I also install any update PA GApps when available ( http://forum.xda-developers.com/showthread.php?t=2397942 ).
Caveat emptor: The CM team makes ever effort to make builds backwards compatible, but always take a backup and be prepared to do a factory reset / data wipe. It very rarely is needed, but you don't want to need a backup and not have one!
If the problem hasn't already been solved, here is an alternative: fireflash. Look it up.
Sent from my Amazon Jem using Tapatalk
Hi there,
I installed PA 4.45 and it was quite buggy on my GT-I9300 (I think my Samsung Galaxy S3 is a AOSPA / legacy device).
I upgraded to PA 4.5 beta 4. Seems quite stable for me. Good job guys!
In PA OTA I see only updates for 4.6 but no update for 4.5.
My question now is (for people who have experience with PA on the GT-I9300 and PA 4.6):
Is 4.6 using more resources (since I have a legacy device, I'm concerned about performance) or the general perceived performance would be similar to 4.5?
I want to know if it's better to wait for a final 4.5 release (will there be any, or updates will come only for 4.6?) or try 4.6.
Thank you for letting me know.
I have been using PA since V4 came out on my i9300. Can say that everything up to 4.6 was amazing, but ever since flashing 4.6 beta 4 (coming from 4.5 beta 4) I have nothing but trouble. Total system freeze (low ram probably) 10 ~ 20 seconds after booting, or 5 seconds after starting the first app. Since I haven't done a clean install in a while I'm giving that a try.
If I don't forget I will post the results.
[EDIT]
Also should mention the heating problems that came with 4.6 beta 4 (but that may just be the dirty flash after all).
markheloking said:
I have been using PA since V4 came out on my i9300. Can say that everything up to 4.6 was amazing, but ever since flashing 4.6 beta 4 (coming from 4.5 beta 4) I have nothing but trouble. Total system freeze (low ram probably) 10 ~ 20 seconds after booting, or 5 seconds after starting the first app. Since I haven't done a clean install in a while I'm giving that a try.
If I don't forget I will post the results.
[EDIT]
Also should mention the heating problems that came with 4.6 beta 4 (but that may just be the dirty flash after all).
Click to expand...
Click to collapse
Thanks for sharing your experiences, I was thinking to upgrade to 4.6 beta 5, but after reading your post I'm a bit afraid...
For now I'm experiencing with 4.5 beta 4 the following problems:
Often when I set a timer, after a few minutes I get an error (dialog with error) that the clock app crashed. But the timer still works... strange. Sometimes the timer then doesn't trigger the alarm in the end.
Also I get a dialog with an error of the ui that crashed. But the system seems working well anyway: no need to restart or so, just the dialog with the error...
See screenshots in attachment...
PA 4.6beta5
I'm currently using PA 4.6beta5 on my i9300 and it's excellent!
No issue, no problem.
Never had low memory problem.
But I've a clean installation (I've wiped all before install)
I have had a LOT of trouble the past few weeks, to the point where flashing a stock rom via odin wouldn't boot and crazy stuff like that. I think it might be hardware related, but after formatting everything and reinstalling it's been working fine now. Only thing is the heating/battery drain problem. It turned out to be google+, so disabling that in apps solved the problem. Running quite smoothly for over two weeks now.
Hello all
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
Thanks
bonuzzz - my friend, thank you for the tablet. thanks for the support and help during the entire time working on 6.0.1
Schischu - thank you very much, this is realty great job on creating aosp for tab s series
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Reboot recovery
6. Flash firmware
7. Flash gapps
Known Issues
Bluetooth
Camera
Old working gapps: open_gapps-arm-6.0-micro-20160106.zip: https://drive.google.com/file/d/0B-6nm7Jks0W5TndJQ09HR0JDRTA/view?usp=sharing
Gapps - if you get "Unfortunaly, Setup Wizard has stopped" on first cm load. This is common problem.
Try find older version: 22 March or early (my link). Or you can delete Start Setup app: go back to twrp - Mount -> system, then Advanced -> File Manager -> system\priv-app\SetupWizard - select current folder and delete. Then reboot in system.
Links
6. 20160406: the April update of the Google Security systems: https://drive.google.com/file/d/0B-6nm7Jks0W5QVVwSHV5RUgxUmc/view?usp=sharing
5. 20160401: https://drive.google.com/file/d/0B-6nm7Jks0W5bWJfZjZuME9Gcms/view?usp=sharing
4. 20160331: https://drive.google.com/file/d/0B-6nm7Jks0W5VTJfdWdma1FFb0U/view?usp=sharing
3. 20160330: fix sdcard, gps: https://drive.google.com/file/d/0B-6nm7Jks0W5bVBJR3VFMXEwVWc/view?usp=sharing
2. 20160330: first cm 13.0 build: https://drive.google.com/file/d/0B-6nm7Jks0W5YUhROVNBN1dacG8/view?usp=sharing
1. 20160329: first aosp 6.0.1 build: https://drive.google.com/file/d/0B-6nm7Jks0W5NEZCMmROb2dQSHM/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 6.0
Sources
cm13.0 branch, in readme file (see device tree) all instructions for build.
CyanogenMod: https://github.com/CyanogenMod/
AOSP: https://github.com/Schischu/
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Camera issues when using the default camera app, or is it a hardware issue? I use the camera fairly often.
@Valera1978 Awesome work my friend! Congrats for one more wonderful work! You rock!
Thanks, I'm gonna try it.
Valera1978 said:
Hello all
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
That's fantastic news @Valera1978 ! Was thinking of trading this machine in because lack of development. But in the same time I love it. It's a brilliant device and it's a pity so few people has found that out. So THANKS A MILLION Valera!
Click to expand...
Click to collapse
Huray. You are awesome.
I went back to the p900, but only for a short time. My friend from the neighboring country gave me P900 for a few weeks. After 10 days of hard work, I made the first 6.0.1
Click to expand...
Click to collapse
Are you going to work more on it? Because you have it for limited time, will be there someone else to continue?
Kubas_inko_CZ said:
Huray. You are awesome.
Are you going to work more on it? Because you have it for limited time, will be there someone else to continue?
Click to expand...
Click to collapse
The p900 will be available till end of the weekend, may be the next week also.
My plan simple - push another developers to continue work with cm13. In this limited time I want:
- make stable cm13 - building right now, hope today evening will be the first results
- clean-up my device/kernel/vendor (almost done)
- try fix camera - look like this is big issue for all exynos cm13 devices, but need at least try fix
And then I really hope thompatry will continue work with cm13.
And hope my sources will help make cm for related note pro 12.1 p901 and tab pro t900/t520. At least t900/t520 use the same kernel and very similar hardware.
Buggy Setup Wizard
How can I skip the buggy Wizard? It keeps popping up error messages.
My tablet was always diferent. I wasnt able to update to official lollipop (stuck on boot animation or every proces crashed) Cm12 is laging. And now, the android 6.0.1 is stack at boot screan animation. I also bricked it with official lollipop (from cm11 to official lollipop) and unbricked it with official kitkat. I really dont understand it. I need to do more with my little android development skills (i have successfully ported cm11 to friends phone, but only thanks it have little difrences from the official cm11 for the supported device) i dont know if u understand it but it doesnt matter
No way!! I wasn't expecting this.
I don't like posting this kind of useless message but I had to write a big THANK YOU. The thank you button doesn't cover how grateful I am for bringing a 6.0 ROM to our big guy.
Does the s-pen work? I can't flash it right now.
GRellinas said:
How can I skip the buggy Wizard? It keeps popping up error messages.
Click to expand...
Click to collapse
Sorry. I forgot to thank you for your work.
Please help me solve this problem with the buggy setup wizard. It keeps coming and I can't do anything .
GRellinas said:
Sorry. I forgot to thank you for your work.
Please help me solve this problem with the buggy setup wizard. It keeps coming and I can't do anything .
Click to expand...
Click to collapse
I had the same problem. Couldn't get past it. So I did a new clean install and this time without Gapps. The rom runs fantastic. Went to apk mirror and downloaded the latest GMS and installed it. Then I went to settings to add my G account. And couldn't go thru with it cause GMS keeps crashing. Don't know why. Gonna uninstall it now and install an older GMS
---------- Post added at 08:25 PM ---------- Previous post was at 07:40 PM ----------
thools60 said:
I had the same problem. Couldn't get past it. So I did a new clean install and this time without Gapps. The rom runs fantastic. Went to apk mirror and downloaded the latest GMS and installed it. Then I went to settings to add my G account. And couldn't go thru with it cause GMS keeps crashing. Don't know why. Gonna uninstall it now and install an older GMS
Click to expand...
Click to collapse
Edit: Tried an older variant of GMS and no success. Well just have to wait. Meantime its awesome running MM on what I thought was a dead device.
Thank you for this Valeria. Really appreciate you doing this. I've encountered most of the problems previously mentioned. Installed with Gapps. No joy. Did another install without. Running OK. One thing nobody else has mentioned is I can't see my external sdcard. Tried 3 different ones. 32, 15 and 4 GB. No luck with any. As for ROM. Nice. Fast. Smooth. Cheers
Cm 13.0 build is ready. Please see first post how to solve gapps problem. Tomorrow I'll check what is wrong with gapps. And then I'll start fix small problems. Still a lot of work, but now with working cm.
Wanted to first say I'm extremely grateful for your work; I've been keeping an eye on the CM threads here for weeks because this upgrade could make the P900 work like a new tablet.
I rely on it daily for college, so I'm kind of hesitant to flash just yet. But for those of you who try this ROM, I'd be very interested to know:
1) S-Pen -- For a separate S-Pen (the one with a separate eraser in addition side button), do the extra buttons work natively in LectureNotes or similar apps or does something else (e..g, "CM S Pen Add-on") need to be installed?
2) Encryption -- Does encryption/decryption work with TWRP 3.0.0.0 (or an earlier version)? Haven't had much luck getting TWRP to decrypt 5.0.2 stock, but as long as the OS can decrypt -- and I've been able to make backups -- I haven't worried about it.
3) Multi-Window -- In CM13, how adjustable are the windows? Can you achieve a setup where 2/3 of the screen is for one app while another app gets 1/3?
4) Camera -- Is it just the stock camera app that's having trouble? Would another app (e.g., Open Camera) work?
5) Microphone -- Is the mic working okay (e.g., for an app like LectureRecordings)?
6) Screenshots -- Is there a good solution for editing screenshots? Something that supports S-Pen? Being able to quickly crop and import things into LectureNotes is very useful. Noticed a new app called "Screen'it" in the store that might eventually be a good stock replacement, but I'd like to know if anybody's got a better solution.
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
Okay... No Bluetooth. [Oops, correcton, Blue tooth *does* work.] No external sdcard. But very fast. Thanks and looking forward to usable version.
shonkin said:
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
---------- Post added 30th March 2016 at 12:33 AM ---------- Previous post was 29th March 2016 at 11:44 PM ----------
Okay... No Bluetooth. No external sdcard. But very fast. Thanks and looking forward to usable version.
Click to expand...
Click to collapse
Thank you.
Yes, you are right, something wrong with the latest gapps. On p905 with latest gapps we are geting the same start wizard problem.
I finished the firmware late at night and had no time to check the different gapps.
Today will be full test and cleanup.
Remove sertupwizard from /system/priv-app to skip wizard. You can do it with twrp file manager
There is rallye no bit different betwene android 5.1.1 (cm12.1) and android 6.0.1 (cm13). The only one i really like is multi window. But still awesome work Valera.
---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------
Can it be gaps version problem? Because i use micro and have no problem with it. (Yet)
Valera1978 said:
Thank you.
Yes, you are right, something wrong with the latest gapps. On p905 with latest gapps we are geting the same start wizard problem.
I finished the firmware late at night and had no time to check the different gapps.
Today will be full test and cleanup.
Click to expand...
Click to collapse
shonkin said:
Thanks so much for this! Just installed CM 13.0 build. Tried stock gapps 6.0 it failed. BUT....
Here is one *provisional* solution (you'll do better I'm sure) for the gapps setup wizard problem.
*Install the March 22 pico version.*
Of course, factory wipe.
Then follow the old school method and do both of these in ONE twrp session:
Flash CM 13.0 Marshmallow
Flash gapps 3/22 Pico
Wipe dalvik
Reboot
And you should be good to go!
This came up with another (older) tablet of mine, the Asus TF700t, which also returned the error when I first loaded a custom MM 6.01 version. That developer (Timduru) suggested using the March 22 Pico version of the gapps and it worked there.... and as I speak is now working on my Samsung Note Pro 12.2. I've not done anythng much with it yet, but will get back to you with anything I find.
Hope this is useful.
Blessings.
---------- Post added 30th March 2016 at 12:33 AM ---------- Previous post was 29th March 2016 at 11:44 PM ----------
Okay... No Bluetooth. No external sdcard. But very fast. Thanks and looking forward to usable version.
Click to expand...
Click to collapse
You're absolutely right. Installed open Gapps 0322 Pico and no problems with GMS. Restoring all my apps now. Tried with Pico Gapps 0330 first but no luck. Thanks for your tip ?
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...