Develop Bugs

Which do you think should be the numbering of LineageOS?

Now we have a reboot. This LineageOS must start in which number?
1.0 according with its birth?
7.1 according android's version?
14.1 according previous CM's version?
I personally prefer 7.1

lfuentes said:
Now we have a reboot. This LineageOS must start in which number?
1.0 according with its birth?
7.1 according android's version?
14.1 according previous CM's version?
I personally prefer 7.1
Click to expand...
Click to collapse
14.1 would be better, as it is new version of cyanogen

I vote for Android version numbers but with more characters, not necessarily numbers, to signify LOS revisions. So 7.1.1A, 7.1.1B, etc (of course preceded by 7.1.1 Beta 1 and 7.1.1 RC1).
My only other idea is to not use numbers at all. Start with the same letter than the current Android version is, and choose some other word (not necessarily a confection, but could be). So just example LineageOS Nerd, and then Nerd-A, etc.

Best keep it as the CM naming. Otherwise its pointless changing of things just for the sake of it. Its worked just fine for the past 6 years.

Same as CM!

i prefer 7.1 same as android version

1.0, to mark the difference with cm and aosp : it has to be a new start

LM6x for Lineage Marshmallow and Android version
LN7x for Lineage Nougat and Android version and so on.

Please just use the android version numbers and put the build number behind it, like that:
LinOS7.1v32 for example

Same as Android version it's based on.
So right not is should be 7.1
This way, its easy to understand its new-ness.
When anybody is co.paring it with Stock Android released by Google.

CyanogenMod version numbers correspond to android versions (N is 14th letter of alphabet, M is 13th etc), no reason to change it.

I vote to go with the Android version for clarification. For instance new people to flashing will need to download GAPPS.
I'm sorry, but who in the heck is going to know that cm14 refers to a letter in the alphabet. And what letter is 14.1?
Who the heck that is new to flashing is going to know that 14.1 refers to 7.1.
Let's stop trying to build on what does not make sense, follow Androids version numbering from Google which will mean everyone will know what the next version will be call, no debates period.
There is no sense in going out of the way. Start with 7.1 and keep it in sync to what Google releases. Don't make things more complicated then they have to be.

I do find the Cyanogenmod numbering a bit confusing. I'd rather have it follow the Android system.

I think they should use the android version numbers and put the build number behind it... LOS 7.1.1V2, LOS 7.1.1V3, LOS 7.1.1V4 and so on...

cato1986 said:
I vote to go with the Android version for clarification. For instance new people to flashing will need to download GAPPS.
I'm sorry, but who in the heck is going to know that cm14 refers to a letter in the alphabet. And what letter is 14.1?
Who the heck that is new to flashing is going to know that 14.1 refers to 7.1.
Let's stop trying to build on what does not make sense, follow Androids version numbering from Google which will mean everyone will know what the next version will be call, no debates period.
There is no sense in going out of the way. Start with 7.1 and keep it in sync to what Google releases. Don't make things more complicated then they have to be.
Click to expand...
Click to collapse
New people would hopefully see the big [7.1.1] tag next to the title. Instead of [CM14.1] [7.1.1] its [LAOS14.1] [[7.1.1]. Even if they don't see it there its always at the bottom of the post. I mean newbies who can't find out the version number probably haven't even got past the unlock bootloader / TWRP stage yet.

Im all for 1.0 it would be ballsy.
---------- Post added at 12:55 PM ---------- Previous post was at 12:50 PM ----------
Im using CM since my 1st Android device (HTC Magic) and had no idea of this... Not that practical, I guess.
I mean, even now that I know it is not that easy to think what Android verion is, lets say, CM11... (Im singing the alphabet song conting in my fingers and then I have to make the dessert-to-Android numbering conversion later on).
Its just like the imperial system!
Myrtana said:
CyanogenMod version numbers correspond to android versions (N is 14th letter of alphabet, M is 13th etc), no reason to change it.
Click to expand...
Click to collapse

LineageOS 7.1

The Ubuntu system sounds cooler
For those of you who don't know, if a build of Ubuntu was released on October 10th, it's version number would be 10.10 (YY.MM)

Same as CM.

I agree
aIeck said:
I do find the Cyanogenmod numbering a bit confusing. I'd rather have it follow the Android system.
Click to expand...
Click to collapse
I totally agree. Keeping it in line is more simple. Although I love how people like to say if you can't figure out what version of Android a ROM uses you must be to stupid to get past a boot locker.
Seriously not everyone learns everything at once, let's make this as clear for newbies. Just because the rest of you know the history of CM and others want to start at 1.0 because it is a new project doesn't mean we should. Matching with Android versioning will keep everyone in the same page.
As good example, Ubuntu thought about the user experience by making things just work out of the box vs some more advance learning curve distros.... Because of this Ubuntu is one of the most popular distributions. It looked at everyone instead of just those who had been using Linux for years.
Make it easy for new users to adopt, make it plain out bold and obvious that it is in line with Android versioning.

Huawei W1 Android Wear Preview 5 to General release

OK so I am a complete beginner with Android. I've had my W1 for nearly a year.
When Android Wear 2.0 reached Preview 5 I decided to take the leap and load it onto my watch.
All is working fine and has been fine for some time.
My question is Huawei have advertised and confirmed that the Full release of Android wear 2.0 is coming end of March. If that is the case, do I need to downgrade my watch to the previous version of Android Wear to receive the update or will i receive the update anyway?
Any help or advice appreciated.

I think you have to flash a new image when it is out, or downgrade to receive it via ota

There are many questions in various threads about this.
Many users are making wild ass guesses, but they have nothing reliable to base those on.
tl;dr We will not know until it ACTUALLY releases!

Based on my experience reading the updater scripts of OTAs in other android devices, there is always a firmware designated as the "target" firmware for the OTA to update. If the firmware installed on the device does not match the target, the OTA aborts. The target firmware in this case will undoubtedly be the latest official release, so I think there is a high probability that the OTA will fail (or just not show up) if you have DP5 installed.

Miui vs android versions

Hi guys I know android version matters but I had a doubt that . Does miui does the job or is android version very necessary cause I use custom ROM havoc os for now but I want a stable software and if I install miui 10 will I miss something and miui too has some features and I quite miss it on custom ROM .
But I wanted to know that weather custom ROM is safe to use for a longer time as I don't want to lose data and not interested in changing ROM frequently and as miui gets on updated every now and then is there any difference or it's just the same

I was a long time android user and if I found a rom that did what I needed and was stable I did not continuously update unless I had bugs.
Usually the new features or fixes are minimal unless going between android versions - marshmellow to oreo for instance..
I am now using Miui, other then the screen layout it is pretty much the same. not seeing anything different in my day today usage other then I have started using gestures and full screen (so no navigation bar at the bottom but still have the status bar at the top).
There ARE a couple of things I need to resolve - ads in the file manager (will look to stop that, or see if a 3rd party manager removes them). but give them a go and see what works for you..

Build BUC1 has blocked the downgrade to Android 10

I upgraded my tablet to BUC1 a few days ago via Odin. Recently I was thinking about downgrading to ATK3 to see if GSIs behave better with Android Q vendors, only to find out that it's not possible anymore.
Starting from BUC1 build, the SW REV value has been incremented to 2 from 1 which effectively blocked the possibility of downgrading to anything earlier. The previous build BUBB is the last one to have a SW REV value of 1.
As a result, if you're on BUA8 or BUBB and are still considering about going back to Android 10, do not upgrade any further. Once you upgrade past BUC1, there's no way back.

Hi, just got a new S7+ Tab. How can I tell if I am BUA8 or BUBB?

poincare said:
Hi, just got a new S7+ Tab. How can I tell if I am BUA8 or BUBB?
Click to expand...
Click to collapse
The about section should tell you which build you're on.

LSS4181 said:
I upgraded my tablet to BUC1 a few days ago via Odin. Recently I was thinking about downgrading to ATK3 to see if GSIs behave better with Android Q vendors, only to find out that it's not possible anymore.
Starting from BUC1 build, the SW REV value has been incremented to 2 from 1 which effectively blocked the possibility of downgrading to anything earlier. The previous build BUBB is the last one to have a SW REV value of 1.
As a result, if you're on BUA8 or BUBB and are still considering about going back to Android 10, do not upgrade any further. Once you upgrade past BUC1, there's no way back.
Click to expand...
Click to collapse
Not sure why you would want to go back.

pastorbob62 said:
Not sure why you would want to go back.
Click to expand...
Click to collapse
GSI does not work well with Android 11 vendor, namely Magisk.
As a result, you need to flash Android 10 vendor which is no longer straightforward past BUC1/BUC6 due to SW REV increment.
On the other hand, some apps and stuffs don't work as well as with Android 10 that some might prefer staying at 10.

LSS4181 said:
GSI does not work well with Android 11 vendor, namely Magisk.
As a result, you need to flash Android 10 vendor which is no longer straightforward past BUC1/BUC6 due to SW REV increment.
On the other hand, some apps and stuffs don't work as well as with Android 10 that some might prefer staying at 10.
Click to expand...
Click to collapse
I see. Personally, I haven't seen any issues with Magisk or any other apps. But I am on rooted and debloated stock BUF5. I know from experience that custom roms can be a quite different experience. However, I haven't seen anything offered for this tablet that appeals to me and my current setup works great all around. On the other hand, my Moto G7 plus is vastly improved on a custom ROM. Better battery life and performance. UI is much better as well.

Question Pixel 6 pro android 13 Beta 2.1.

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...