Since a lot of people having issues with recent updates, I will share last stable release.
I do not possess any other variants.
Google Drive
Related
I've asked a number of questions about what the Alpha 2 is for this thread:
http://forum.xda-developers.com/showthread.php?t=1581065
I guess the question was answered (Thanks), but I'm very confused as to what an Alpha is and what an RC is. The latest title of this thread states "RC3 not Alpha." For those of us new to these ROMS, how are we supposed to make heads or tails of what is being presented. I asked a number of times, if RC2 was Alpha 2, and just got circular answers or "No." I finally found a link myself, which someone responded was the right one for Alpha 2, but I'm still confused as to what RC1, 2, 3, etc. has to do with Alpha 2, 3, 4. Can anyone explain this?
Finally found out the answer to my question by asking in Androidforums
Alpha: for developer testing only; many inherent bugs that require other people who understand coding and such to assist with working on. Not ready for mass consumption, period. There can be different stages of useability here, but suffice it to say, that unless you know how to work under the hood (so to speak), don't touch an Alpha release.
Beta: Still in testing stage, but generally fit for public consumption as most major immediate flaws have been ironed out and just some system bugs remain with UI tweeks to be made as well. Like with Alpha, there are different stages of beta release as well, but they are all varying degrees of "generally useable but not entirely ready to be a daily driver".
RC: This stands for Release Candidate. Imagine a mother bird choosing which of her chicks to kick out of the nest first. The RC is the one she's chosen, so while it's still not fully baked in the sense that it isn't a completely air-tight product from both system and UI perspectives, it's definitely capable of being a daily driver for the avg person, as well as for the person with moderately sophisticated needs. Varying degrees of this step as well (RC2, RC3, etc), but typically when you're looking at a release candidate version of software/firmware, it's close enough to "fully baked" to where you can rely on it to work for you with consistency.
Since I have released my game to production, I released about 10 small updates and one major update. Now I am working on a major update that will bring more levels, graphics and music. I can release the major update in few small updates or wait until I have done everything. What are the advantages and drawbacks of many small updates vs. few big updates? Any external factors? (E.g. some countries have plans with unlimited data etc, but maybe people only update on wifi)
kulisgames said:
Since I have released my game to production, I released about 10 small updates and one major update. Now I am working on a major update that will bring more levels, graphics and music. I can release the major update in few small updates or wait until I have done everything. What are the advantages and drawbacks of many small updates vs. few big updates? Any external factors? (E.g. some countries have plans with unlimited data etc, but maybe people only update on wifi)
Click to expand...
Click to collapse
I strongly suggests to do just few big updates for few reasons:
The users will get less annoyed by Google Play update notification
You reduce fragmentation that maybe cause you some issues.
You maybe do a better testing and avoid pushing unstable version on the market
I update my game often because of the feedback I receive... I think a lot of updates are ok if the downloads and download rate are low .. Once it begins to pick up I don't think a new update should be released too often...
I have been releasing updates because of partnerships, adding new levels and modes, and fixing bugs pointed out by various users. My game is now seeing a higher download rate and at the same time I am not planning a new update anytime soon. Next update will be to add more levels if game continues to grow or fix bugs for my users.
Summary: It depends on the status of your app.
A lot of download and high download rate = Few large Updates
Small number of downloads = Either one is fine depending on the app's need
As Huawei Mate 10 pro was shipped with Android 8 last year I believe Mate 10 Pro also was a part of the Project Treble initiative. If that is so, is it correct to assume that we will soon see an OTA update for Android 9 to the Huawei Mate 10 Pro? And if so, does anyone know anything about the timeline? Like when can we expect to receive Android 9?
Project Treble is a major re-architecture in the way Android works. In essence, it separates the Android operating system (the Android 'framework') from the vendor Hardware Abstraction Layers ('HALs') that allow for the OS to work with the device's hardware
Click to expand...
Click to collapse
There have been a few OTA updates including safety patches until August 2019. So that is all good, but when I look in the "About Phone" in settings I am still on Android 8. As I am running this Mate 10 unrooted with a stock ROM I am really looking forward to Android 9 update, and have been checking frequently for new updates without luck.
Anyone knows more about this? Any set date or rumors about an upcoming update to Android 9 for the Mate 10 (pro)?
Currently there is Public beta going on if you are lucky for it to be available.
Date unknown. Probably sometime after the Mate 20 released.
Im in the same boat. Waiting for updates to alot of promised features
that are still lacking in the Mate 10. If Huawei released Android 8.1 for people outside of
China we would already have them.
Instead they are quick to release PUBG and GPU turbo fixes cause we would rather have that than updates for
Camera and Slow Mo 960fps etc.
Second beta was just released. Will update on Friday.
Information from the official Huawei forum in Serbia says that rollout of the official EMUI 9.0 for Mate10 Pro will start on December 14th.
So the Emui is equal to the Android version as in when Huawei update/bump their EMUI to 9.0 that means they will also bump the core to android 9?
Ok, probably just me that have read to much into the Project Treble an the separation of HAL. Since I first read about the HAL last year I kind of figured that the mobile devices that shipped with Android 8 would get a really timely bump to Android 9, like within weeks only after the android bump. So in my mind I kind of expected the roll out of new Android to be almost close to equal to the end of beta for Android 9.
On a semi related question, iirc the back story of the Project Treble was that Google wanted to address the fact that manufacturers did not commit to keep their Android devices updated, and that most of the manufacturers has a short life span of updates. Which combined lead to ie some bad press regarding vulnerability for many older Android devices, along with a less desirable user experiences with aging Android devices. Not to mention the lack of abilities to take advantage of all the newer software improvements that follows each Android update each fall. There have been a couple of Google initiatives prior to Project Treble, without hardly any traction and without Google being able to force manufacturers to stay committed.
So with the Project Treble Google did from what I can remember,make it mandatory for join the Project Treble for those who shipped their devices with Android 8. In my mind that translated to all kinds of things. Like Google putting down minimum requirements for number of updates manufacturers had to commit to, the speed of which they release updates etc.
However, did Google in fact put any of those requirements into Project Treble? Can we in fact look forward to having ie set number of supported updates from manufacturers in the future? Or will the big brands still be able to ignore their customer base rapidly and push forward with new models and focus their energy towards people updating their devices and buying the next year model rather then keeping their previous model with less overall waste, less economic impact and a more sustainable hardware update factor?
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
avatar_ro said:
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
Click to expand...
Click to collapse
Yeah but not the final version we need the beta at least ?
punkerEVO said:
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
Click to expand...
Click to collapse
Well if Google didn't take any steps to enforce manufacturers to actually keep updating they should keep their mouth shut about it later when we will see as usual that android devices are lagging behind in version numbers.
I really thought Google went balls in and was brave last last year with Project Treble and put down some new ground rules for their OEM's. But now it seems treble is just as weak hearted as the previous attempts from Google. Well I guess the solution is custom ROM's.
Manufacturers will never keep updating unless they are pressured to do so, they will always chase the sale of the next device and try to maximize profit rather then committing to last years hardware is up to date. So I guess project treble was a nice idea but google lacked the balls to actually lay down the law and demand dedication. Spineless. And to think they once lived by the catchphrase "don't be evil".
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
:laugh:
hondasoma said:
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
Click to expand...
Click to collapse
Beta test in Europe is already opened. 101 per country
Greetings,
I'm posting this on the General as the forum associated with this mobile device is pretty much dead ATM. It falls very much more in the category of "I need help figuring out how to do this Android Global thing" rather then a very specific issue with a device.
The long and the short of it is the Samsung Galaxy On5 SM-G550T/1 was a fairly short lived phone in the US. It's a barebones phone that has a lot of features of design choices of the Galaxy S5 and S6 while having very minimal accessory hardware (which as an altimeter and advanced GPS systems).
This phone, however, has seen *A LOT* of popularity in Easter EU, Middle Eastern or Indian markets and thus there is a TON of Rom development still active for this phone.
The SM-G550FY has significant differences with the Sound Drivers, Camera Drivers, Bluetooth Drivers and Modem Drivers that makes the ROMs, in general, compatible enough to be installed, but not compatible enough to have the Sound or Camera work and has varying levels of Modem and Bluetooth viability; more often then not, they work though.
Someone finally dropped a hint that most these drivers are in the /system/lib folder requiring CHMOD of 740 to work; but no one to the best of my knowledge has actually gotten this "workaround" to work. This was something that was completely foreign (no pun intended) to many of us who have posted in that forum. I've had zero success with this, but it seems to have gotten me looking in new directions for fixes.
So my questions are a few fold that I hope the XDA greater community can help with:
#1.) Is there a way to import the correct drivers that are verified working in the same version of Android from another rom?
#2.) Are drivers for different versions of Android the same (IE 6.0 and 7.0 since those are the ROMs being regularly released) or are we reliant on Samsung to release a properly working set of 7.0 drivers to get Android 7.0 working on the US/CA variants of the phone?
#3.) I'm looking for good resources to learn how to build an installer for a ROM to try to build and release a patcher to make SM-G550FY roms compatible with SM-G550T/1 Roms. What resources could you suggest to get myself better up to speed to doing this.
#4.) I'm also looking for good resources to learn how to build ROMs perhaps based on Lineage for my model of the phone. Where would I go to learn more about that?
Thanks for any help you guys can provide.
I am genuinely dissapointed in how little development the mediatek variant has gotten since the past 5 years.
I remember back when there was only one AOSP ROM in the MTK development forum, while the snapdragon variant was churning out new ROMs every minute. The last time I checked was 2018, and it had gained a few more ROMs but they were riddled with bugs.
Today, nearly 4 years later, I come back to the MTK development forum expecting to see lots of Android 10 ROMs, maybe even Android 11 ROMs, and if not, then Android 9 ROMs at the very least.
Still no ROMs.
It's exactly like how I remembered. Completely barren, like a ghost town. Not even updates to the old ROMs. How come? I'm pretty sure it's not that hard? Helios X20 should be no problem for ROM development. Man, even during a time like the pandemic there is still no development.
This is truly sad. The MTK variant is much more faster than the SD265 variant so I am dissapointed to see so little development for it. I hope to see that maybe 2022 someone will finally develop new ROMs for the people who still have the phone.