Related
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
I am about to buy this phone because it is just so damn good for it's very low price tag, however one thing is bugging me about it. I came here to find that there are no Marshmallow ROMs for it yet and the main reason for me wanting to upgrade my phone in the first place is so that I will be able to run the latest Android ROM's without performance problems. I am currently on CyanogenMod 13 on my old Samsung Galaxy S3 and I like it, but it is slow. The Redmi Note 2 doesn't even have CyanogenMod support.
Is this because Xiaomi are going to release an official MIUI based on Marshmallow? I don't want to buy this phone if it means I am going to be stuck on MIUI or on an older version of Android. I am a bit perplexed because this phone sold a lot so why hasn't anyone made Marshmallow for it yet?
Do you think that development is going to pick up for this device or is this device a bad option if you want to run the latest Google Android (not MIUI)?
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
verbage said:
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
Click to expand...
Click to collapse
Thanks for the explanation. It seems really unfortunate that they haven't released the source. I guess I should either buy the more expensive Mi4 (which I believe the source is released for) or I can just wait it out and see if the source code get's released for the RN2. It seems strange to me that they wouldn't release Marshmallow-based MIUI for such a popular, fairly new phone. I think they will release it. If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
M will deffo be released for RN2. Main reason we still dont have it is:
a) first "official" device with M is supposed to be mi5
b) MTK prolly didnt polish 6.0 yet
Major companies that use X10 (eg Sony & HTC) didnt realse M for their devices either, at least as far as i know, however they are planned. So yeah M will arrive eventually, which is great, but that doesnt mean custom roms will get any better. And knowing xiaomi, and their kernel release policies, this is pretty much 100%. Pretty sure they still havent released any kernel source for their older MTK powered devices.
I think I'm going to buy the Mi4 rather because its kernel is open. I want to know that I'll be able to get android roms of any new releases. It's a real shame because the Redmi Note 2 is cheaper and a more superior device, but I have read that Mediatek are scumbags when it comes to releasing kernels because they want to force you to buy a new device when your OS becomes outdated which goes against the open source licence of Linux. Oh well, I guess that's business.
rimpy said:
If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
Click to expand...
Click to collapse
If they release MM-MIUI for the RN2, unless they release the source code, this will still mean that roms are cooked/repacked, or built from source, but probably imperfectly due to lack of source. Though MIUI is based on Android, I don't think there are free and open MIUI repositories where one could grab the necessary source code for the RN2.
At this point, like everyone said, it is very unlikely that Xiaomi will ever release the source code for the RN2. Without it, custom ROMs will never be proper, and it's the reason there are no MM builds yet.
However, even though MIUI is horrible and God knows that I hate it, it's quite usable. A version of the Xposed framework that works on the latest MIUI builds has been released a couple of days ago, and with it you can get most of the functionality a custom ROM provides. It's not perfect, and I'd prefer AOSP, but it is, IMO, the best this phone has to offer at the moment.
I only got mine about three months ago, and while there were many times I came to regret my purchase, every other phone in this price range and slightly above has inferior hardware. With that said, if you want a phone running AOSP or something very close to it, you'd be better off getting a Nexus or a device that is officially supported by CM.
Thanks all. I was just about to buy the RN2 but I am glad I posted here first. I've learnt a lot and I don't think I would be happy with a phone that has a closed source kernel. The Mi4 has a smaller screen, no SD slot, slower, and costs more, but its kernel source is released and it is supported by CM13. Still very good value for money so that's gonna be my next phone.
It actually isnt slower. Benchmarks only. If you run them side by side with either MIUI or CM youll see than Mi4 is actually much faster than RN2, so yeah, its a better option if you have the money
https://www.dropbox.com/s/bgce2efur8tq1ot/Screenshot_2017-05-13-17-13-44.png?dl=0 She said it was not compatible yet it got the wifi alliance http://www.wi-fi.org/content/search-page?keys=SM-A310F :confused: I think it's true because only the a5 2016 and a7 2016 got it but the a3 2016 hasn't?:crying:
Based on the existence of the certificate the update exists and is/was already under testing.
The only possible reason not to release it if they f*cked up the optimization of touchwiz for nougat like they did before a few times, resulting in failure to release updates to below flagship devices (like S4 mini).
The A36 is marketed as an ultra mid range device, so if it happens again despite their promises they could probably say goodbye to mid range buyers for once.
Let me explain: power users know Android. They (we) know that with every major update it's more and more optimized and less demanding on hardware, but Samsung seems to have a trouble following that trend with tw. They almost do the opposite, while people demand updates, and it's also in the interest of Google, so they have already warned manufacturers to do their best on the matter, specially Samsung after their past neglections. This topic has a great influence on our preferences and despite the other fields Samsung devices excelling in our eyes, it could change the situation. Now, most simple users choose devices based on our opinions. They ask us for advices. If I prefer Samsung devices, 100-150 people around me will prefer Samsung too based on my opinion; but if I prefer another brand instead, they will buy their devices instead. Now imagine how the numbers come with a lot more power users exisiting in the world, not just me.
The nougat update for A36 (having the broadest market amongst other A and J series devices thanks to it's handy size, yet powerful hw and quality housing) is a big opportunity to show us they have changed their attitude towards mid-range users, something people and Google are waiting for a long time, so they know it would be a disaster for them to back out from it in the final moments. I hope they won't.
I hope they release it but it explains why a7 and a5 2016 got nougat before the a3
link is broken
...if I get Nougat on my A3 2016...I won't ever enter this forum again.
Spreading negative information like this by pointing broken links as source is 3rd grade child stupidity.
It's not my fault if it doesn't work I saw it myself
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
arif8912 said:
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
Click to expand...
Click to collapse
These support guys don't know what they are saying... "I'm afraid it's not compatible" => there is no such thing. If they make a compatible build than it is compatible, simple as that. Also, when I've asked them, I got the response that IT IS GOOGLE WHO MAKES THE UPDATES, THEN THE CARRIERS REVIEW IT AND RELEASE IT. Yes, this is how it should be ideally if there would be a flexible hardware abstraction layer, but sadly it is Samsung who has to build the update after Google releases the source, and before carriers can deploy it... When I had to rate the conversation I wrote them that their support department has no access to proper information even about HOW updates work which is very troubling for conscious users who chose Samsung because of Android (+their quality hardware) and expect them to properly provide updates for their ultra mid range devices too, not just for their overpriced flagships.
http://www.samsung.com/tr/support/newsalert/100061 A3 2016 update got delayed to 29th may-2nd june
No LG Android 10 for any V30, so stop asking
https://www.xda-developers.com/lg-ux-9-0-android-10-update-schedule/
I said this before, explained WHY multiple times -- and now it's official.
No V30, including V30S, is getting LG Android 10 update. V30 launched with Nougat and has all the OS updates (Oreo and Pie) it's going to get.
V30S doesn't have Treble so that proves it was never a new phone LAUNCHED on Oreo. V30S was just a V30+ with more RAM, updated to Oreo at the factory before release., prior to all the other V30 then getting Oreo a couple of months later. V30S was basically a V30+ with more RAM, released as a marketing gimmick to try to compete with the 2018 Snapdragon 845 Samsung Galaxy S9/S9+. Was still a Snapdragon 835 V30 "Joan" phone, which runs same V30 firmware. (Samsung had exclusive rights to Snapdragon 845 for a few months.
IF it was a new phone LAUNCHED on Oreo, V30S would have required Treble. If it was new phone LAUNCHED on Oreo, then it would be eligible for two OS updates -- Pie and Android 10. But since V30S didn't have Treble, it was NOT a new phone.
Later LG released actual Snapdragon 845 phones: G7, V35, V40. Those all had Oreo and had Treble -- proving they were indeed new phones.)
V30/V30+/V30S still should get some more security updates and fixes. But no Android 10.
__________
P.S. Stop calling Android 10 "Q". Its no longer beta.
"L", "M", "N", "O", "P", "Q" were the beta letters before release and Google officially named them. I could go all the way back to beta "C" which became "Cupcake" -- but you get the point.
L became Lollipop (Android 5, 2014)
M became Marshmallow (Android 6, 2015)
N became Nougat (Android 7, 2016)
O became Oreo (Android 8, 2017)
P became Pie (Android 9, 2018)
Q simply became Android 10, 2019
Deal with it. Google decided not to use sweet snack/dessert name anymore, so they only went with the version number instead. There was always a version number behind the dessert name.
No one calls "Oreo" and "Pie" as "O" or "P", since they are not beta anymore. No one asks "Do we have a new 'P' KDZ yet?" nor "Which is better 'O' or 'P''? Everyone calls them "OREO" and "PIE". Well, "Q" isn't beta anymore either... It's "Android 10".
Here's the Oreo official statue at Google Headquarters:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's the counterpart Android 10 statue:
Ho noes~
Frankly, I'm not sure I'd trust LG to put out a stable version of it anyway. Doesn't Pie OTA still have the silly lag issue fixed with LG's backup thing?
Shame. really wanted that desktop mode.
still - seems rather strange... what about the SD845 V35? it should get android 10 no? yet it is not listed.
also please note that the road-map is just for 2020, so maybe the V30S + V35 are planned for 2021?
wonder if we will be able to port some features to our v30's, as i really like this phone
Septfox said:
Ho noes~
Frankly, I'm not sure I'd trust LG to put out a stable version of it anyway. Doesn't Pie OTA still have the silly lag issue fixed with LG's backup thing?
Click to expand...
Click to collapse
Yeah, Pie on some variants is still wonky. Like US998, and Sprint LS998 still doesn't have it. Also AME H939DS doesn't have it yet.
Orof said:
Shame. really wanted that desktop mode.
still - seems rather strange... what about the SD845 V35? it should get android 10 no? yet it is not listed.
also please note that the road-map is just for 2020, so maybe the V30S + V35 are planned for 2021?
Click to expand...
Click to collapse
Uhmm, no. Android 10 was released in 2019. No OEM is going to still be pushing updates for it in 2021.
It's possible V35 still may get it as this was ITALY LG list, and V35 was not released in Europe. Was released to North and South America.
LG Italia has stated that the Android 10 update will be available for nine phones.
Click to expand...
Click to collapse
But V30 was released in Europe and the H930G was specifically released in Italy. Their V30+ was even eligible for the official LG Bootloader Unlock Code -- which we don't need thanks to WTF exploit.
ChazzMatt said:
Uhmm, no. Android 10 was released in 2019. No OEM is going to still be pushing updates for it in 2021.
It's possible V35 still may get it as this was ITALY LG list, and V35 was not released in Europe. Was released to North and South America.
But V30 was released in Europe and the H930G was specifically released in Italy. Their V30+ was even eligible for the official LG Bootloader Unlock Code -- which we don't need thanks to WTF exploit.
Click to expand...
Click to collapse
So was the v30s ever released in italy? If not, that might also be the reason it is not listed there even though it only got one major update...
I don't know... Better ask lg directly i guess
Fully expected. After years with LG, moving to S20+ anyway.
Orof said:
So was the v30s ever released in italy? If not, that might also be the reason it is not listed there even though it only got one major update...
I don't know... Better ask lg directly i guess
Click to expand...
Click to collapse
V30s was not released in Europe either but it also got two OS updates: Oreo and Pie.
Is considered the V30 variant which LAUNCHED with Nougat.
It was merely V30+ updated to Oreo and 2GB RAM added prior being sold to the public. V30S is still a JOAN phone, which "launched" with Nougat. If someone doesn't know what that means, it means it's a V30 and runs V30 firmware. It's even in the model number V30S
V30S was merely a re-modeled house not a brand new house. It was a marketing gimmick, not an actual new phone.
But I'm repeating myself...if it was a new phone with OREO it would have had TREBLE. It doesn't, so that irrefutablly proves it was not a new phone!
Any website that says otherwise really has no clue what they are talking about. They never actually owned a V30S and they probably don't understand that all new Android phones with Oreo (or later) REQUIRE Treble.
ChazzMatt said:
I said this before, explained WHY multiple times -- and now it's official.
No V30, including V30S, is getting LG Android 10 update. V30 launched with Nougat and has all the OS updates (Oreo and Pie) it's going to get.
V30S doesn't have Treble so that proves it was never a new phone LAUNCHED on Oreo. It was merely a V30+ with more RAM released as a marketing gimmick to try to compete with the 2018 Snapdragon 845 Samsung Galaxy S9/S9+. Was still a Snapdragon 835 V30 "Joan" phone, which runs same V30 firmware. (Samsung had exclusive rights to Snapdragon 845 for a few months. Later LG released actual Snapdragon 845 phones.)
We still should get some more security updates and fixes. But no Android 10.
Click to expand...
Click to collapse
Dear Brian Kwon,
You are tasked with turning around LG's failing mobile divison. The task will be difficult, but there is good news. LG makes flagship phones with phenomenal hardware. The problems at LG are self-inflicted and can be fixed. You might take a moment of your time to browse threads like this one on xda for a sense of the problems. Three of them are software support, communication, and execution. There are a a few simple things for you to do. 1) Flagship phones like the V and G series should ship with current versions of Android. 2) LG should standby their committments to release updates. 3) LG should be transparent with customers, stonewalling is unacceptable.
The V30 flagship is a great example of LG's problems. For clarification I am referring to the open market V30. It was released with Android 7 even though 8.1 was the current release. There have been a few security updates but no Pie. My wife's Sony XZ2 Compact has been on Pie for 18 months. Part of the appeal of Android is running AoSP roms. It would be refreshing to know in advance which models LG will allow bootloader unlock and rooting. Even better, just offer the option. It is also unacceptable that the software stack for use on Verizon is broken, i.e. no VoWIFI or Visual VoiceMail.
These issues are a toxic combination for anyone laying out USD800 or more to keep for two to four years. You should think of fixing these problems as building and maintaining a relationship with your customers and distributors. Their safisfaction is your success.
The lack of loyalty and transactioanl behavior of LG hits home when it comes time to buy a new phone. I have a couple of V30s', and they weren't cheap. The hardware is holding up well and that is great. I'll be in the market for a new device in a 18 months or so. It shouldn't be for access to security updates or current Android. It should be for new hardware and the capabilities new hardware creates like longer battery life, 5G, speed and so on.
For these reasons, I am not considering an LG model like a V50 in the future and I am sure I am not alone. I hope you change my mind.
Thank you,
cmrntnnr
It's time to move onto a newer phone. I don't keep phones after 2 years anyway. V30 came out in 2017. I got mine in May 2018. Battery health is down to 89%. Processor will soon be 3 generations old. 4GB RAM is mid-range spec. Gonna look for LG G8 (not X) deals.
HKSpeed said:
It's time to move onto a newer phone. I don't keep phones after 2 years anyway. V30 came out in 2017. I got mine in May 2018. Battery health is down to 89%. Processor will soon be 3 generations old. 4GB RAM is mid-range spec. Gonna look for LG G8 (not X) deals.
Click to expand...
Click to collapse
Thanks, nobody cares.
ldeveraux said:
Thanks, nobody cares.
Click to expand...
Click to collapse
you're welcome. nobody cares about your post either.
Lol
cmrntnnr said:
Dear Brian Kwon,
Click to expand...
Click to collapse
[snip]
What email address did you send this to? I'd like to do the same (with some edits so that it's not just a plain copy/paste) to let him know the same thing from me... if oyu don't mind.
Sorry, I don't have an address. The letter format seemed like a good way to express my frustration and hope. Maybe it will be conveyed to him by some LG staff monitoring xda, I amuse myself....
schwinn8 said:
[snip]
What email address did you send this to? I'd like to do the same (with some edits so that it's not just a plain copy/paste) to let him know the same thing from me... if oyu don't mind.
Click to expand...
Click to collapse
HKSpeed said:
It's time to move onto a newer phone. I don't keep phones after 2 years anyway. V30 came out in 2017. I got mine in May 2018. Battery health is down to 89%. Processor will soon be 3 generations old. 4GB RAM is mid-range spec. Gonna look for LG G8 (not X) deals.
Click to expand...
Click to collapse
Mate gone are the days where in terms of performance and most features update made a difference V30's Display,SD835 and Most features are still upto par aside from gesture gimmick you are opting for
I recently came back from SD845/6gb Ram to SD835/4gb and the difference is not that dramatic as it would have been from 835 to 820 or 820 to 810 also keeping in mind the thermals of those older chips only that aside from performance was frustrating
SD835 in my experience to date is Snapdragon's one of the most stable and long lasting chips I can even point you to some tech youtubers despite of having budget and devices laying around using SD835's
Infact given the phones I have used I would say buying a 835 Pixel 2XL is better than going for a G8 (but thats just personal preference including UI features and all ) but there was this feel about Pixel 2XL given its higher price tag I always felt its well worth it in terms of that build ,polished UI and implemented features and yeah GCAM and its Night Sight
Sent from my LG-US998 using Tapatalk
cmrntnnr said:
Sorry, I don't have an address. The letter format seemed like a good way to express my frustration and hope. Maybe it will be conveyed to him by some LG staff monitoring xda, I amuse myself....
Click to expand...
Click to collapse
Mailing address is fine... I amuse myself that way as well
I do not even want Pie lol Forget 10, Here are my reasons and people should know what they are upgrading for and why.
The best question is do you really need it just because it's latest OS ? Have a look at this Windows 10 change at higher ups and one can correlate how Win10 is a disaster their priorities changed to a SaaS model there is no more RTM release like 7 and 8.1 and get 10 years of updates it's SAC - 6 months and then 18 Months later it's EOL, there are automatic driver updates it creates a lot of issues and so many BSODs, auto update the damn BIOS patches (Intel Meltdown and Spectre), well I run a Haswell 4710MQ processor with a sockted GPU MXM chipset and If I installed latest patches it will ruin the performance. And SGX bug makes the Undervolting not possible, meaning no control, they are forcing those updates into the Windows Update packages and BIOS. Just hit that forum and see how many issues are there with Win10, see the latest Win10 feature - modern standby causing havoc.
Then we have the worst of the Android 10 issues, the TWRP itself is hard to work on, here's Pixel 3a's TWRP thread and see the last page, unless you flash a custom kernel with Fastboot and Magisk the TWRP won't work for Android 10. And on top the damn Filesystem issues - Pixel 2 got A/B filesystem and bam you can't flash properly and (read this very informative) then you get the Pixel 3 logical partitioning system along with the dynamic fused partitions, then you have Android 10 + Pixel 4 mega lockdown, Huawei style EROFS clone of Read only Ext4 partition system, exactly like how Huawei's puppet masters wanted at their homeland. Edit : here's the LZ Play backdoor, that XDA portal never published.
Do you think google will stop there ? Remember when A/B system came it was rejoiced for that Treble, devs are great but that Treble with GSI being generic doesn't add anything to the OS customizations, maybe some ROMs can be flashed with Magisk, but what about our custom Mods like the Anxious mod etc, and then A/B was enforced with 8.x released devices with CTS for Safety Net. I think they will enforce all this dynamic partitions with Android 10 and up and eventually the modding will further wither away which is already less, less than 0.5% of whole Android devices owners root and run Custom stuff.
Do you really want Android 10 ? What feature is it ? don't say multitasking or the gestures lol. Both are inferior to Oreo, simple fact - A phone has 16:9 or 18:9 or the 19:5:9 or the latest S20s worst 21:9 tall ratios, all are Vertical, so a vertical card stack like from Lollipop, Marshmallow, Oreo had the same stacks, making you see all the multitasked apps in one single shot and decide and scroll flick is fast and quick switching as well. Now see the Horizontal iPhone X style, even iPhone 8 had stacked design. With X they changed it, you can see only 1 card on Android on iOS you can see at-least 2. Google blatantly copied it and ruined it badly. Then you have Clipboard API restriction, more more APIs blacklisted, and list goes on and on, Youtubers and all mainstream blogs even Android Police just parrot 24/7 updates updates, what about the features ? Why not a removable battery, or 3.5mm jack without compromise, SD slot for reliability, if they are emphasized, these ridiculous 1 year lifecycle of HW refresh and OS refresh will stop and create breathing room for better devices and more support and less e-waste too.
Then you have the Scoped Storage on Android 10 (Issue Tracker) in the SDK, on a Pixel phone, Pixel recorder (Massively inferior to what LG offers - HiFi DAC routed, Audio with Karaoke input option a.k.a Studio Mode with separate files option for input included, Bit-rate selection, Storage selection, Multiple formats, Time-series graph & Peak meter per channel which are LIVE, Lossless recording, Tags, Timer, Sample Rate, Limiter, Low Freq Cut off, High Gain for higher sensitivity damn it this is a phone or a dedicated recorder ? ) the recording files cannot be seen in any app. YOU CAN'T see the files the app recorded. Period, why ? Google wants to force us into iOS style sharing bs, on iOS you must share the file to another app to view it 1:1 exact sandboxed bs copied over to Android and it will break millions of phones with Android R or 11 whatever they want to call it, since Android 12 will force the latest SDK-1 format which PlayStore mandates. Here's a latest reddit post on it, good points are discussed there. And in case you missed the XDA article by FX app dev (I recommend that app heavily, it's a must have, using since GB-KK) and the in-depth analysis Blog for the whole disaster which even mentions on how Google wants more subscription based direction and how to approach this.
Tell me again who wants Android 10 again now ? Nougat 7 is LTS release it is like KK 4.4 which will be running for at-least 4 more years. So get the damn battery replaced by LG OEM officially restore the Oreo final backup with Magisk and enjoy the best of what you can get right now. Yes security updates are needed but most of the time the malware comes from unwanted apps on your phone which you are responsible, same for PC too, it doesn't need an AV and get robbed by the AV companies instead if you take little care and grow your knowledge with basics you retain the control / power in your hands, if more people don't want that's what will happen. Look at iPhone users, they cannot live without that ecosystem unhealthy Apple
Security through Obscurity is never real, thanks for reading hope it did help something
On a side note, is the latest Magisk working without issues on our LG Oreo 20h Stock ?, I'm running old 19.3 and 7.3.4 manager ?
Great post... I've said the same thing for a while - why do I want Pie? It really doesn't give us anything really new (other than numerous bugs, apparently). Any new "feature" you want can be easily added if you REALLY want it, but it's not that big of a deal for most people. This isn't an iPhone (which requires OS updates to gain functionality)... Google has been pulling that into the apps directly, so you don't need a specific OS (GENERALLY speaking)... to get a feature...
To answer your last question, yes you can run the latest Magisk. I think the only limitation is that it cannot be installed with TWRP at initial startup, for some reason. However, once it's installed and you're in the OS, you can update without issue. I'm on VS996 win 20.3 and 7.5.1 without issue.
Security updates V30/V30+
I didn't realise some V30's still weren't on Pie, my V30+ has been on it since September. Battery life is better and they have improved audio playback with .dxd audio files. I'm still stuck on the September security patch though. Has LG given up on V30 security too?
I'd like to get to as close to vanilla as possible. Not a fan of Samsung's ui or bloat. I'm coming from the tab s1 which had some pretty good roms. There are none for this device and it's almost 6 months old. I would make one myself but lack the necessary skills
Most of the newer top end Samsung Tablets get very little developer support since they cost so much. Happens with every new tablet having people asking where the developer support is for it. Samsung newer UI much nicer and any vanilla roms would take away most of the functionality that makes the tablets great. Apparently the S5e has some dev support.
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Markeee said:
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Click to expand...
Click to collapse
Not everyone gets the update at the same time (don't know how they handle when and who should receive the update). I only got a November update a few days ago (though some claimed to have already gotten it) and it offered few improvements. The tablet still feels the same as usual.
As one must choose between custom ROMs and Knox (especially warranty), I'm currently at a loss myself, and for the time being I haven't heard of anyone trying (or succeeded in) booting a GSI on S7/S7+ probably because of this, although it's theoretically possible (again thanks to Treble). At least we now have TWRP... it might be better if one day custom kernels become available.
So far this is the only tablet I know that can offer 120Hz display. My current phone (Razer Phone 2 which is also 120Hz-capable) still doesn't have a specialized ROM but I can already run GSIs on it with adequate performance. For new devices, going for GSI might be easier, but performance-wise it still has a way to go compared to specialized ROMs.
Think it has to do with the fact that snapdragon is locked on samsung