Related
Hi all,
I have a Find 7 QHD on Paranoid Android 4.6 BETA 4.
Got an OTA update this morning (BETA 5), installed it and I just get get black screen on boot that goes no further.
I also restored a previous backup and manually updated to latest beta with same results.
Has anyone with Find 7 had any luck with the latest PA 4.6 BETA 5? Wondering if it's something with my setup or the update itself.
Thanks in advance.
Same issue, tried from Beta 4 upgrade and clean install but both won't boot.
I can confirm that the latest update breaks PA completely (for me, anyway). Guess I'll just have to wait for the next big update.
Same thing happened to me...7a here
That sux, but I'm glad it's not just me.
Have seen many reports of this, guess I'm staying on BETA 4.
Hey, just giving a quick update to all o' y'all: The newest PA beta build boots without a hitch! I know that it's been out for some time now, but I just tried it and I seemed to have very few problems other than the processor refusing to go into its low power state (which also happens with Cyanogenmod for me, so I'm not sure what's going on there).
Anyway, happy flashing as always!
Im getting a Robin today for the first time. If i signed up on their Beta tester site will i get Nougat? Not sure how all that works. Should i just leave it stock?
If you are approved, yes the Beta is Nougat-based. If you need stability, you should stay on Stock, otherwise report the bugs you find on the Beta.
On the site due to overwheleming applications i cant update yet till they go over my app i guess
How to install mi 10t lite android 11 in Europe, when will it be available, does anybody know?
=Anderson= said:
How to install mi 10t lite android 11 in Europe, when will it be available, does anybody know?
Click to expand...
Click to collapse
Either install the global ROM (with a factory reset) or wait a couple of days - EU ROM comes with a slight delay after the global version (if there are no major issues).
_mysiak_ said:
Either install the global ROM (with a factory reset) or wait a couple of days - EU ROM comes with a slight delay after the global version (if there are no major issues).
Click to expand...
Click to collapse
Do I lose warranty if I do that?
And how do I install global rom, can u send some tutorial link
=Anderson= said:
Do I lose warranty if I do that?
And how do I install global rom, can u send some tutorial link
Click to expand...
Click to collapse
You should not lose your warranty (at least in Europe bootloader unlocking won't void it).
I would suggest you to make yourself familiar with flashing in general (adb, fastboot, tools, rom formats etc.) before you attempt something.
Recovery Android 11 EU ROM, flashing from TWRP works fine. Notification LED is finally clearly visible with the latest ROM.
https://bigota.d.miui.com/V12.0.1.0.RJSEUXM/miui_GAUGUINEEAGlobal_V12.0.1.0.RJSEUXM_15bfbef742_11.0.zip
Source: 4pda
Good news but UK still with 12.0.8.0 (QJSEUXM)...
Try Switch Region to france and you´ll get 12.0.9.0 . At least in Germany it works.
But it is only a very small Update.
Barmenchik said:
Good news but UK still with 12.0.8.0 (QJSEUXM)...
Click to expand...
Click to collapse
It was the same for me, so I just flashed recovery ROM from TWRP (at first from 12.0.8.0 to 12.0.9.0 and then to 12.0.1.0). It should work with locked bootloader and stock recovery as well (some extra steps like renaming file to "update.zip" and putting it to the root of SD card, or using ADB sideload might be necessary).
Wattsolls said:
Try Switch Region to france and you´ll get 12.0.9.0 . At least in Germany it works.
But it is only a very small Update.
Click to expand...
Click to collapse
OMG! It works for UK as well... Thank you. Now just waiting for Android 11...
Barmenchik said:
OMG! It works for UK as well... Thank you. Now just waiting for Android 11...
Click to expand...
Click to collapse
I think the A11 EEA Recovery ROM got released but you have to be a Beta tester? Something to do with pilots lol
So hopefully that means there will be a full 11 rollout soon
I thought that EU Andoid 11 version is stable, but it seems to be really only beta as mentioned on 4pda. There are some misalignments in message notifications and phone crashed quite nastily once (had to reboot it 5 times until it finally fully started). RAM usage seems to be a bit too high as well resulting in more app redraws/reloads than necessary. I hope that fixed version will be out soon.
And the very same file is out as official "beta stable" now..
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
_mysiak_ said:
And the very same file is out as official "beta stable" now..
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Do you know for how long approximately we will have to wait for Android 11 stable in Europe because Beta is now out?
=Anderson= said:
Do you know for how long approximately we will have to wait for Android 11 stable in Europe because Beta is now out?
Click to expand...
Click to collapse
From what I understood how Xiaomi does the updates:
1. at first there is internal beta
2. after successful internal testing, it goes to closed beta
3. after closed beta it goes to public beta
4. if there are no (major) issues, the very same version is released to public in batches as "stable beta" (recovery ROM)
5. if there are no (major) issues, the very same version is released to public in batches as "stable" and fastboot ROM is released as well
So I believe that what we've seen is that "public beta" V12.0.1.0.RJSEUXM became "stable beta" and will transition to "stable" in the coming weeks. However when exactly is it going to hit your phone is impossible to tell, they chose phones by country + some random parameters. Manual installation is probably the best way how to have the latest ROM version.
искам да попитам моя сензор за близост на светлина работи тук спира и го няма никъде В настройките Как да настроя това, за да поправя моля помогнете I'm sorry to write exactly This may not be the topic But I'm still with my ten lite and the sensor doesn't work andЗа съжаление there is no slider for incoming calls where to set it there are a lot of truncated functions why? Sorry I want to ask my light proximity sensor works here stops and is nowhere In the settings How to adjust this to make a fix please help
_mysiak_ said:
So I believe that what we've seen is that "public beta" V12.0.1.0.RJSEUXM became "stable beta" and will transition to "stable" in the coming weeks. However when exactly is it going to hit your phone is impossible to tell, they chose phones by country + some random parameters. Manual installation is probably the best way how to have the latest ROM version.
Click to expand...
Click to collapse
Exactly this version is now arriving on my German stock phone as an OTA update today. The phone is new and I had never participated in any beta program or anything like that. Thus it should be stable production right now. Is this true?
Did I get this right? Xiaomi is not differentiating beta-version numbers from stable version numbers? In other words: I cannot differentiate the release train between a beta and a stable channel from looking at the version number?
Thank you!
Ethan
Ethan66 said:
Exactly this version is now arriving on my German stock phone as an OTA update today. The phone is new and I had never participated in any beta program or anything like that. Thus it should be stable production right now. Is this true?
Did I get this right? Xiaomi is not differentiating beta-version numbers from stable version numbers? In other words: I cannot differentiate the release train between a beta and a stable channel from looking at the version number?
Thank you!
Ethan
Click to expand...
Click to collapse
Yes, it seems to be considered as a "stable" now.
And yes, there is no difference in the version number between beta/stable. ROM is not being re-released, it's always the same ROM with the same download link and with the same hash. Beta/stable beta/stable is just a naming convention which changes over time. There is no special beta channel in a traditional sense as you might be used to from PC/ mobile applications.
_mysiak_ said:
Yes, it seems to be considered as a "stable" now.
And yes, there is no difference in the version number between beta/stable. ROM is not being re-released, it's always the same ROM with the same download link and with the same hash. Beta/stable beta/stable is just a naming convention which changes over time. There is no special beta channel in a traditional sense as you might be used to from PC/ mobile applications.
Click to expand...
Click to collapse
Thank you, _mysiak_! This is more clear now.
What is disappointing for me is, that now, after I have thoroughly decided to install the OTA update, it has disappeared again and is no longer found by the Xiaomi updater. How strange.
Maybe there were bugs and it is set back to beta status?
You probably never know the algorithms how Xiaomi distributes updates...
Maybe they just save bandwidth right now. ;-)
Ethan66 said:
Thank you, _mysiak_! This is more clear now.
What is disappointing for me is, that now, after I have thoroughly decided to install the OTA update, it has disappeared again and is no longer found by the Xiaomi updater. How strange.
Maybe there were bugs and it is set back to beta status?
You probably never know the algorithms how Xiaomi distributes updates...
Maybe they just save bandwidth right now. ;-)
Click to expand...
Click to collapse
I've read exactly that explanation - if you don't install the update when it's received, your "slot" is released after few hours/days and offered to someone else. It is supposed to save bandwidth and prevent overload of Xiaomi servers. But I have no idea if it's really true..
So the update will shortly be arriving now as stable update via phone updater. If someone has a link when it arrives you should put it here
Hey there I tried recently the ArrowOS android 12 ROM but the ROM doesn't have the complete material you settings and for some reason my screen keeps kinda flashing sometimes with or without screen deeming option.
Does anyone knows if already ROM was released for our device that have the material you complete and be somewhat stable? ArrowOS in stability was great at least the 2 days I tried it but that lack of personalization made me go back to evolution x. Thanks to any answer in advance
never try beta release
same thing I've experienced, i just went back to arrow 11 since early android 12 has a lot of bugs. I still have my patience waiting for the official release
jewsus1337 said:
never try beta release
Click to expand...
Click to collapse
The kind of comment is really unkind bro and please don't take it bad, without testing the beta versions you won't get the stable builds, and dev will never be able to discover all the bugs without an extensive testing from the most of the involved users ... and after all, that version of Arrow 12 is really stable and smoother than Arrow 11 for me ... missing features and option is not a really big deal after all ...
kylezl said:
same thing I've experienced, i just went back to arrow 11 since early android 12 has a lot of bugs. I still have my patience waiting for the official release
Click to expand...
Click to collapse
Sorry but did not faced a single bug on the Arrow 12 rom OP mentioned
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...