Hope for stock Android port? Motorola One Action with Exynos 9609 - Samsung Galaxy A50 Guides, News, & Discussion

The A50 differs from the other A-series devices in terms of having an Exynos 9610 which has seen practically zero development and poor GSI compatibility. However, finally we have an Android One device with practically the same chipset.
The Motorola Action One comes with the Exynos 9609 which is the same as 9610 apart from having a 100 MHz lower clock speed. In the past, we had instances of Android One firmware being ported to similar devices, so it is possible for a capable developer to be able to create a functional port.
Of course, bugs are inevitable, especially in the areas of camera and wireless connectivity but hopefully with the right combination of blobs it might be possible to have a daily driver. Again, at this point there is nothing more to go on rather than hope, but it is great to have a sister device running stock Android.
So what do you think about future development prospects? Is there any developer with an A50 willing to have a go once the firmware for the One Action becomes available?

Nice let's Hope ?

Motorola one vision is already out since May, and it's exynos 9609 as well, running Android one.
You can check one vision forum if anyone is interested in system/vendor dump. I got it uploaded a while back.

Related

Eventual custom roms ?

Hello,
This phone looks really interesting, but I don't think Samsung will care about it after the promised 2.2 update. Furthermore its predecessor, the Galaxy, suffered from both a total lack of custom roms.
So my question is do you think there will be good custom roms for this phone for newer android versions ? Is it possible (eventual problems with drivers, etc..) ?
Thanks for your answers
Paul O'Brien @ MoDaCo has just tweeted that he has rooted his own Samsung Galaxy S, so im sure that he will produce some great things for this phone as he has done with many other android phones. I hope its soon
I'm pretty sure there will be some awesome custom ROM s. This phone will be on the top 4 US carriers and US cellular. There will be a lot of new developers coming to this forum once the device is released.
DAKIDD236 said:
This phone will be on the top 4 US carriers and US cellular.
Click to expand...
Click to collapse
I consider this more of an annoyance since there will be like 5 different rom types (4 US versions plus the Europe/Global version) because so far every version has a different hardware configuration. AT&T and T-Mobile versions have different buttons (4 instead of 3) and no front camera. The Sprint version is a totally different phone with camera flash, a keyboard, and unfortunately, only 1 GB of storage (Link). The Sprint version also has no front camera and comes with 4 buttons. No details on the Verizon version. It's inevitable that someone will flash with the wrong rom.
The Captivate for AT&T has almost identical hardware to the I9000, as well as having a front facing camera. the only thing that was rly changed on this phone from the I9000 was the body design and the extra button.
sunshine1982 said:
The Captivate for AT&T has almost identical hardware to the I9000, as well as having a front facing camera. the only thing that was rly changed on this phone from the I9000 was the body design and the extra button.
Click to expand...
Click to collapse
Hmm...i actually read that it won't have the front facing camera.
clubtech said:
Hmm...i actually read that it won't have the front facing camera.
Click to expand...
Click to collapse
Captivate will have front facing camera and Vibrant on t-mobile does not have it. Vibrant actually looks identical to the Galaxy S, but Catptivate looks totally different(i think it looks better). Captivate looks=SE X10 looks, Galaxy S/Vibrant looks=iPhone looks??
edit. both of those links are telling that they both have secondary camera, but pictures of the phones are without front cameras.
here's the Samsung Captivate and Samsung Galaxy S I9000 compared on gsmarena
http://www.gsmarena.com/compare.php3?idPhone1=3408&idPhone2=3115
Remember Samsung holds a tight lock around it's drivers. So don't expect anything to awesome with these roms. No wifi tether is obvious and all roms will be based on Samsungs current 2.1 release. It's impossible to port anything from HTC or Motorola onto a Samsung phone because of the crazy partitions and security they have on it.
Yeah that was the problem I was referring to when creating custom firmware..
I'll buy another phone I guess
I'm not an expert, but don't think that's true. As SGS is rooted and Paul is currently preparing the kitchen @Modaco it looks like the bootloader is not locked like motorola milestone. Thus there's no problem to have custom roms, or?. Froyo is secured (according to samsung) so drivers will not be a problem in near future imho.
P.S. as I see some other phones with the same/similar hardware are announced to come in the next several months so pretty much there will be drivers available..from one or another place. But this is valid concern for any android as a matter of fact...except nexus 1, which is out of my scope due to the bad HW
P.S.S Another .02c - if the functionality promised is working as charm and the remaining phone's issues are solved in the near future...is it so important to have the latest gimmick that re-starts the troubleshooting from scratch?
P.S.S.S Samsung is a better choice than HTC... Many reasons.
dlci said:
I'm not an expert, but don't think that's true. As SGS is rooted and Paul is currently preparing the kitchen @Modaco it looks like the bootloader is not locked like motorola milestone. Thus there's no problem to have custom roms, or?. Froyo is secured (according to samsung) so drivers will not be a problem in near future imho.
P.S. as I see some other phones with the same/similar hardware are announced to come in the next several months so pretty much there will be drivers available..from one or another place. But this is valid concern for any android as a matter of fact...except nexus 1, which is out of my scope due to the bad HW
P.S.S Another .02c - if the functionality promised is working as charm and the remaining phone's issues are solved in the near future...is it so important to have the latest gimmick that re-starts the troubleshooting from scratch?
P.S.S.S Samsung is a better choice than HTC... Many reasons.
Click to expand...
Click to collapse
Samsung's drivers are proprietary and encrypted. You still have to wait for them to be released in order to get anything to work on a Samsung device or else the device will have no display/sound/antenna's. The bootloader was hacked on the Behold 2 but we still had no option to flash from the phone. That means ODIN is the only way. Behold 2 was rooted and still had no wifi-tether and no choice in custom roms (it was whatever samsung released + optimizations). HTC has Samsung beat with hackability.
Ok, I understand now what you mean. Didn't know that.
Too bad with this encyption story...
edit:we wouldn't have gingerbread if samsung won't release it,is that right? No chance to get something "new" if samsung doesn't release it directly?
°Dexter° said:
Too bad with this encyption story...
edit:we wouldn't have gingerbread if samsung won't release it,is that right? No chance to get something "new" if samsung doesn't release it directly?
Click to expand...
Click to collapse
If they release it for another Samsung phone then it's possible that it could be ported but not certain. There is a 2.1 rom for the Galaxy. Eugene tried to port it to the Behold 2 and got almost everything working except for the most important thing which is sound. Wifi/BT/data/video were all there but he just couldn't get sound. We had a 1.6 rom well before the official release only because Galaxy had it first (also someone got a secret behold 2 beta a month after the Galaxy rom was released) and it's only problem was it didn't have vibrate. It's just nearly impossible to do anything without something from Samsung.
A good read if you want to understand what you're getting into when you buy a Samsung phone. http://androidforums.com/all-things-root-behold-2/63246-dev-needed-2-1-running-behold-2-a-4.html
mmmm, so, the combination of encrypted drivers and poor samsung support i.e. firmware updates, means that we wont be able to run 2.2 ROMs unless samsung releases 2.2?
and also further android versions are a no go?
already been burned by motorola with milestone and its locked bootloader, dont wanna burn again.... seems like the only option is HTC
psychoace said:
No wifi tether is obvious and all roms will be based on Samsungs current 2.1 release.
Click to expand...
Click to collapse
But there is wifi tethering. I set up a mobile AP on my UK Vodafone SGS to allow a guy in the office to activate his iPhone 4!
psychoace said:
Samsung's drivers are proprietary and encrypted. You still have to wait for them to be released in order to get anything to work on a Samsung device or else the device will have no display/sound/antenna's.
Click to expand...
Click to collapse
Are you sure about that? Recording to this thread the galaxy s source samsung released includes drivers with wlan and camera mentioned as examples:
http://forum.xda-developers.com/showthread.php?t=696863
o shi. if what you guys says here is true and there is no way to make new roms for the samsung or get new android version until samsung make them because of the DRIVERS that's a no go Galaxy for me plus tether is a Must Have for me .... damm u samsung. that was the only phone in t-mobile that I like I guess I'm gonna have to switch from carrier after all
I think we can't really compare GS with Behold 2. GS will have lot more support from Samsung. Also i have faith in Paul's work, he will come with some serious ROM's.
I wouldn't surprise if he would port Froyo to GS before Samsung. He already had fixed stalling issue, now i could feel real hummingbird humming in my GS.

One X's future updates

Hi everybody, I'm considering buying an One X and was wondering what's the state of future updates as far as AOSP/AOKP goes.
I'm asking because I currently have Galaxy S2 which gets all the new Android releases from cm/aokp but has some problems due to the kernel source code not being published for the Samsung made Exynos chip - from what I understand it makes coding very difficult and a lot of rom coders stay away from the device and move to newer and easier phones to code for.
Does One X has a similar problem making it's life span shorter in terms of Android releases or no such problem and I should expect new Anroid releases for the next few years (not official but AOKP)?
Thanks ahead!!

[Q] One X vs One S in terms of development

Hi,
I ask here for your help because I am planning to buy a new phone in the near future, and I am currently deciding between the One S with Snapdragon S4 and the One X with Tegra 3.
I would be very, very grateful if someone could tell me which one is better from the perspective of custom ROM development. Which one has more stable and less buggy CyanogenMod or similar AOSP-based ROMs? I've been lurking here in the One S and One X sections for some time and I can see that neither of those two phones is bugless, but I don't know how severe these problems are, if it is a dealbreaker or you can live with it. Also I get the feeling that the Tegra 3 is lacking in terms of development support and Qualcomm devices are better suited for future development. Is that so or am I wrong?
Another thing which I consider is the display quality, although it is not the main one. I know that the One X has a denser screen with better color reproduction than the One S, due to being an LCD panel, but the blacks are not as deep as the AMOLED on the One S. Is there a big difference? Do the blacks shine too much at night? It would be very cool if someone could post a good photo of the One X displaying a black screen at night.
Just one more question, how does the picture quality from the Sense camera compare to picture quality from CyanogenMod? I know Sense takes better pictures because it is optimized for the hardware, but is it a big difference?
Thank you really much for your answers, I aprecciate your help.
PS.: I posted a similar question here in the One S forum, if you want to take a look.
This is what HTC says on Reddit (and that answers the part about Nvidia vs Qualcomm quite honestly):
To address an issue that’s top of mind for many folks here, we recently announced that we wouldn’t be updating the HTC One X and One X+ beyond Android 4.2. Without the support of our chip manufacturer Nvidia, it made a global update of One X and X+ devices impossible. However, in US the One X uses the Qualcomm chip and an upgrade would be possible, but we didn’t think it would be a good experience for our customer base to update the X, but not the X+. This update caused a huge stir amongst owners and we’ve heard you loud and clear, so we’re now actively exploring how we can make the jump to 4.4.
Click to expand...
Click to collapse
So, Qualcomm FTW. But one thing I can't understand is how the Nexus 7 2012 got KitKat, when it's using the Tegra 3 too. It still feels like Nvidia abandoned it on 4.1, though.
frantisek.nesveda said:
This is what HTC says on Reddit (and that answers the part about Nvidia vs Qualcomm quite honestly):
So, Qualcomm FTW. But one thing I can't understand is how the Nexus 7 2012 got KitKat, when it's using the Tegra 3 too. It still feels like Nvidia abandoned it on 4.1, though.
Click to expand...
Click to collapse
The nexus 7 has the T30L while the OneX/X+ use AP33/37. Nvidia still provides support for T30L but not for AP3x.
Sent from my One X

So is proper Nougat support is out the window...?

According to this article, Android 7.0 is dropping support for the Snapdragon 800 chip and the Adreno 330 GPU, the latter of which we unfortunately share in our 801 chip. Depending on the wording I'm not sure if this means the chipsets are "unsupported" or "will not work" on 7.0... In any case, if Qualcomm won't make new drivers for 7.0 then that means even if a Nougat ROM came for us then it might not have things like Vulkan support or could be cripplingly buggy. Although that's not a crippling loss it does stink that this might be the end of the road for this phone... I've hardly had mine for two years.
Am I right about all of this or is there still hope for decent unofficial support?
Long story short, no nougat. Qualcomm isn't updating the graphics driver anymore. The m8 is end of life at this point anyways though... ?
Hoping my shiny M8 is not old already but, to be honest, I really haven't noticed much difference /improvement since KitKat. I think it's just nice to say I have the latest Android.
Nougat will just be another 'nice to have'
Sent from my HTC One_M8 dual sim using XDA-Developers mobile app

Will OnePlus continue OP3 support??

After the release of the OP3T, OnePlus has decided to discontinue sales of the OP3 according to Android authority. http://www.androidauthority.com/oneplus-3-officially-discontinued-us-europe-729580/
Could this mean that sooner or later, they might drop the support of the OP3 due to how they have to work on updates for both phones? They have slightly different specs so that might mean they have to work on two different sets of updates right?
There is slight difference in OP3 and OP3T, basically in Soc. OP3T will obviously require different drivers etc and they definitely will not care for the older one. You know what, they have released 7 beta updated for OP3 but nothing worth noticeable is there in these updates except their try to push own bloatware. Some of the OEM have updated their devices to nougat but not Oneplus. If LG can make their device updated to nougat out of the box then why not Oneplus. If they release nougat for OP3 than it will have negative impact on sale of OP3T which they never let happen. They will be updating OP3T to nougat and OP3 will get it after few months
drnajmu said:
There is slight difference in OP3 and OP3T, basically in Soc. OP3T will obviously require different drivers etc and they definitely will not care for the older one. You know what, they have released 7 beta updated for OP3 but nothing worth noticeable is there in these updates except their try to push own bloatware. Some of the OEM have updated their devices to nougat but not Oneplus. If LG can make their device updated to nougat out of the box then why not Oneplus. If they release nougat for OP3 than it will have negative impact on sale of OP3T which they never let happen. They will be updating OP3T to nougat and OP3 will get it after few months
Click to expand...
Click to collapse
Both devices get Nougat this year. According to their stream updates will be brought out sameoutaniously. Also the OP2 and OPx will get Nougat but not this year.
Demian3112 said:
Both devices get Nougat this year. According to their stream updates will be brought out simultaneously. Also the OP2 and OPx will get Nougat but not this year.
Click to expand...
Click to collapse
The OPX will not get official Nougat as the 801 doesn't pass Google's certification as Qualcomm is not updating the drivers to support OpenGL ES 3.1.
quite disappointed on how quickly OP decided to destroy its great public image made after release of OP3...
lel, what did you guys expect from "LYING CARL" ? You can't trust a single word this guy says.
=dave= said:
lel, what did you guys expect from "LYING CARL" ? You can't trust a single word this guy says.
Click to expand...
Click to collapse
Absolutely true
Don't speculate. Wait and see.
OP are vastly smaller than LG or Samsung, there isn't simply the quantity of devices out there as OP can't manufacture that many. So they're taking advantage of the newer hardware and quickly updating to the newest CPU, rather than continuing to manufacture devices on older hardware. This is why OP3 has been discontinued.
Software-wise, again, they don't have the development team to get Nougat out to us 'RIGHT NOW', but we've been promised it by the end of the year on both devices. I've been very pleased with the amount of updates and community builds so far.
OP4 will hit probably six months from now and that maybe an incremental update again, unless we see a snapdragon 830 or something!

Categories

Resources