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.
Related
Anyone have directions on doing this?
Directions?!
1: Use Google
2: Use YouTube yeah it might be fora slightly related Device, and not exactly the same one you have. But the principals exactly the same!
3: Use Google and use the Device Codename 'Picasowifi' that should get you to the CyanogenMod Page.
There you will see a list of *.zip Files, of which you'll only need to pick One. Though they all seem to be for CM12.1 (i.e. Lollipop), though.
So it looks like your kinda SOL on Marshmallow at the moment. But, as long as CM12.1 works, and it should!
And your continuing to get the newest Security Updates as you should. Then there isn't much different between the Two.
You have a marshmallow based rom in other forum (Tab Pro original Android development). Also there is an instruction how to flash it.
I'm not asking for an ETA, as I know that's against the rules on xda.
However, I'm unable to find any info anywhere about the reasons why Oreo hasn't arrived. It was released in August, and over three months is a long time in custom ROM world.
I'm guessing it's being worked on but there are complications, but with the lack of updates being posted by the powers that be, it's hard to know. Can someone in the know tell me?
As far as i know it was the quick succession of Android 8.1 which let several custom rom developers drop Android 8 developement and jump directly onto the 8.1 train.
Schwarzie2k said:
As far as i know it was the quick succession of Android 8.1 which let several custom rom developers drop Android 8 developement and jump directly onto the 8.1 train.
Click to expand...
Click to collapse
Let's hope 8.2 isn't released soon then.
I think many people would appreciate a blog post on the LineageOS website advising how things are progressing and what the challenges have been.
the blog post from December touched on the progress of Oreo and on skipping 8.0 to go straight to 8.1. (it's below the changelog text):
https://www.lineageos.org/Changelog-15/
However now that Android 8.1 has been released, we’re anticipating moving straight to the 15.1 branch where we’ll merge all our work done for 15.0 and finish the porting effort.
Click to expand...
Click to collapse
Also, a very recent news (January 1) here on XDA talks about an alpha build being available for the OnePlus 5:
https://www.xda-developers.com/lineageos-15-1-android-8-1-oneplus-5/
(I'm assuming that's from the official maintainer to have been worthy of a news).
So things seem to move into place.
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
djdelarosa25 said:
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
Click to expand...
Click to collapse
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Systemlessly said:
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Click to expand...
Click to collapse
Sweet, thanks a lot man! I'm going to flash it right now.
Sadly, the flash failed It appears that it doesn't support the Oreo bootloader
djdelarosa25 said:
Sadly, the flash failed It appears that it doesn't the Oreo bootloader
Click to expand...
Click to collapse
What is the error?
Did you flash the official or soak test 8.0 rom before?
Systemlessly said:
What is the error?
Did you flash the official or soak test 8.0 rom before?
Click to expand...
Click to collapse
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
djdelarosa25 said:
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
Click to expand...
Click to collapse
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Systemlessly said:
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Click to expand...
Click to collapse
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
djdelarosa25 said:
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
Click to expand...
Click to collapse
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Systemlessly said:
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Click to expand...
Click to collapse
Holy cr*p, thanks so much, man! :laugh:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
talktosam said:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
Click to expand...
Click to collapse
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
djdelarosa25 said:
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
Click to expand...
Click to collapse
u ask any way to get LOS 15.1? any hope? how can i contact him?
talktosam said:
u ask any way to get LOS 15.1? any hope? how can i contact him?
Click to expand...
Click to collapse
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
djdelarosa25 said:
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
Click to expand...
Click to collapse
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Please see the post above you.
https://forum.xda-developers.com/showpost.php?p=76379057&postcount=16
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Lineage 14.1 is Nougat based and it will not flash as it will display bootloader error while flashing in twrp. Wait for Lineage 15 or as djdelarosa25 said [/COLOR]
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
wait till 2nd may
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Systemlessly said:
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
Click to expand...
Click to collapse
Yeah, thanks for helping me, man! The dev was really cool - replies, debugs, and compiles really quickly as well. Talk about pro.
Manish355 said:
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Click to expand...
Click to collapse
I already asked him if it was in the works and he said don't ask for ETAs. I asked him again today and told him I wasn't asking for a date, just a confirmation if LOS 15 is in the works. We'll see what he says.
EDIT: So it counts as an ETA then. He said we'll just see it come out (so I guess it is in the works). But I wouldn't worry that much, the dev works really fast.
and yeah, I like a ROM that was made for the MZP as well. As much as I like Alberto's ROM, a ROM built from scratch > a port (though LOS 14.1 is Alberto's work as well). It's a pity he quit development of it.
hi guys,
i have a question about android. can i switch my rom to rolling release? thank you for your reply.
Need some more information here...
Unless I missed something idk what rolling release means?
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
hajking said:
"In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications. This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version."
sorry i dont know enough word to explain in english so i copied a bit and pasted. if you use a linux distro like arch linux, you just update packages like when you get play store updates and never get major updates like on ubuntu.
Click to expand...
Click to collapse
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
AWESOME1092387456 said:
Just install the alpha and beta version of the rom/firmware you would like for frequent updates.
But sadly it doesn't work like that on mobile, you get a huge update once a year and patches every month (if you are on "stable")
Click to expand...
Click to collapse
yeah im on latest miui tr and i get update every week but there must be a way i think.
hajking said:
yeah im on latest miui tr and i get update every week but there must be a way i think.
Click to expand...
Click to collapse
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
thanx dude
AWESOME1092387456 said:
if our devices supported Project Treble we would be able to receive system-less updates, which are possible due to treble's A/B partition scheme (as far as i konw but i am not entirely sure)
Click to expand...
Click to collapse
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
ccelik97 said:
Firstly, what's that "system-less" but still the updating of the "system"? Learn before talking and know what you're saying (no personal offense, btw).
Then again you're wrong as mi 6 doesn't have that a/b partition scheme (even though it's not that hard to repartition the device storage to have two boot and system partitions, you'll need to have or compile a new kernel that supports that partition and booting scheme - and we don't have that yet).
Treble will only let you to update your system without touching the separated vendor partition.
Click to expand...
Click to collapse
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
AWESOME1092387456 said:
What i meant is we could update the phone without needing to do a full restart and i said "IF OUR DEVICE SUPPORTED PROJECT TREBLE" didn't you read the "IF"? And with "system-less" i meant mostly bugfixes that can be installed without the need of restarting the whole device as that particular service would for example shutdown and then start again and in this way we could receive security patches and minor stability updates, not full android releases or another version of miui (from v9 to v10) these kinds of upsates should still need to be performed through recovery, please next time read a response carefully before responding and i personally stated that i am not that sure either at the end of my response so don't just look for some keywords and then go bashing others for no reason.
Click to expand...
Click to collapse
Sorry my bad on that "if" part you're right.
But still, that's not a "system-less" solution but a "recovery-less" updating way as with the a/b partitioning what we get is not having to use anything other than the currently running system to apply the updates (and the ability to roll back to that very currently running system, is something goes wrong with the new)
I see that on the OnePlus forum it mentions a roll out udpate for Android 10, but I still have not seen this on my phone.
https://forums.oneplus.com/threads/oxygenos-10-0-0-for-the-oneplus-5-and-5t.1231626/
Has anyone seen this update yet on their phone, or know anything about this?
THANKS
OnePlus... They didn't announce anything since their first release of Android 10 in May. In August FAQ OP5 isn't even mentioned anymore.
DoR3M3 said:
I see that on the OnePlus forum it mentions a roll out udpate for Android 10, but I still have not seen this on my phone.
https://forums.oneplus.com/threads/oxygenos-10-0-0-for-the-oneplus-5-and-5t.1231626/
Has anyone seen this update yet on their phone, or know anything about this?
THANKS
Click to expand...
Click to collapse
perhaps following thread helps
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
Guys, even if you download the 9.0.11 build from https://www.oneplus.in/support/softwareupgrade/details?code=PM1574156155944 and flash it, you shall see the OOS 10 update from system update. If not from system update then download the oxygen updater from play store.
Ok guys...
I'm just trying to figure out why I don't just get an update for it to the phone?
I thought by now everywhere in the world the update would be pushed to the phone already?
Are there still people not getting the update through the phone still OTA?
THANKS
Bite the bullet and manually update. I know it's a PITA; but, if there's no OTA for your phone and you want to upgrade to A10, just go for it. You'll be better off with a fresh install anyway.
Same situation in here. Waiting for Android 10 since May (when stable release rollout was announced).
Edit: I found way too many people talking about bugs on Android 10 (battery drain, fingerprint sensor delay, call recording bug). I'm not sure, but maybe staying on OOS 9.0.11 is the right call.
If someone in here is already on OOS 10, please comment on that. Thanks
r3bite said:
Same situation in here. Waiting for Android 10 since May (when stable release rollout was announced).
Edit: I found way too many people talking about bugs on Android 10 (battery drain, fingerprint sensor delay, call recording bug). I'm not sure, but maybe staying on OOS 9.0.11 is the right call.
If someone in here is already on OOS 10, please comment on that. Thanks
Click to expand...
Click to collapse
Im on OOS 10, blu_spark kernel and very happy, if there are any bugs (there probably are), I don't notice them...
I had someone give me a reply on another post on XDA that 10.1 is coming OTA to the phone, so I'll hold out for now, I'm in no hurry...
Thanks
rori~ said:
Im on OOS 10, blu_spark kernel and very happy, if there are any bugs (there probably are), I don't notice them...
Click to expand...
Click to collapse
that's nice to hear, maybe I'll download Oxygen Updater and try it out
DoR3M3 said:
I had someone give me a reply on another post on XDA that 10.1 is coming OTA to the phone, so I'll hold out for now, I'm in no hurry...
Thanks
Click to expand...
Click to collapse
Hydrogen OS 10.0.1
Update log】
system
• Fix the problem of weak GPS positioning signal
• Fixed the problem of no sound in certain videos on Youku
• Fix the problem that the alarm does not ring when the device is off
• Fix the problem that fingerprint recognition cannot be used under certain circumstances
• Update Android security patch to 2020.06
wallet
• Added Wallet App, integrated bus/access card entrance into Wallet App, making operation more convenient
• Added WeChat payment method for bus card recharge
camera
• Electronic anti-shake function has been added to bring you a more stable shooting experience
rohithksaj said:
Hydrogen OS 10.0.1
Click to expand...
Click to collapse
You Quote and don't really say anything, what are you saying?
By the way Hydrogen OS is suppose to be 11, as of last week according to this article;
https://www.gsmarena.com/oneplus_to_introduce_hydrogen_os_11_on_august_10-news-44563.php
So what, Hydrogen is now going to be our new OS? I know this is what they did in China, now the rest of the world too?
DoR3M3 said:
You Quote and don't really say anything, what are you saying?
By the way Hydrogen OS is suppose to be 11, as of last week according to this article;
https://www.gsmarena.com/oneplus_to_introduce_hydrogen_os_11_on_august_10-news-44563.php
So what, Hydrogen is now going to be our new OS? I know this is what they did in China, now the rest of the world too?
Click to expand...
Click to collapse
Nah man . That's the release notes for the hydrogen os for 5t .
So the new oxygen os will be having same release notes .
5t won't receive 11 , officially not in china nor in the rest of the world .
rohithksaj said:
Nah man . That's the release notes for the hydrogen os for 5t .
So the new oxygen os will be having same release notes .
5t won't receive 11 , officially not in china nor in the rest of the world .
Click to expand...
Click to collapse
I'm not sure why you replied then with a quote from what I said, I'm not concerened about Release Notes, just trying to figure out what's going on with an update date for the 5T to Android 10 is all...
DoR3M3 said:
I'm not sure why you replied then with a quote from what I said, I'm not concerened about Release Notes, just trying to figure out what's going on with an update date for the 5T to Android 10 is all...
Click to expand...
Click to collapse
Why did I quote that because to make sure you that 10.0.1
will be releasing soon and these are the release notes .
This device is done man .
OnePlus only provides 2 years of software development
rohithksaj said:
Why did I quote that because to make sure you that 10.0.1
will be releasing soon and these are the release notes .
This device is done man .
OnePlus only provides 2 years of software development
Click to expand...
Click to collapse
Ok thanks
I suggest looking in the official OP5/T Android 10 announcement thread. Over 400 pages of complaints and questions and OP doesn't give a ****. The thread is like a disaster area. The first Android 10 update was pulled because of that many bugs. Shortly after they pushed the update again with some hotfixes but with the same version number and without announcement. Then they pulled it again.
Maybe in the next 1-2 weeks there will be an update with some fixes and a more recent security patch. Hopefully not only June like in hydrogen OS but I don't expect much to be honest. I'm almost done with OP
btw I installed OOS 10.0.0 and rooted (to install dotfix + Gcam) and I'm pretty happy with it.
also, google pay stopped working after root. I guess I'll live without it since dotfix is really worth it IMHO.
bussi1805 said:
I suggest looking in the official OP5/T Android 10 announcement thread. Over 400 pages of complaints and questions and OP doesn't give a ****. The thread is like a disaster area. The first Android 10 update was pulled because of that many bugs. Shortly after they pushed the update again with some hotfixes but with the same version number and without announcement. Then they pulled it again.
Maybe in the next 1-2 weeks there will be an update with some fixes and a more recent security patch. Hopefully not only June like in hydrogen OS but I don't expect much to be honest. I'm almost done with OP
Click to expand...
Click to collapse
What OP doesn't give a bleep?