Related
i tink that LG was waiting for cooking a stock rom based on android 2.4 (instead of the 2.3 promised) because of their similarities, in fact the gpu accelerations for 2D, rumored for the 2.4, can only help our P500 performance.
i hope this, and you?
Ps: i tink that a P500 at 150$ with 2.4 in the very next month can bring android for many doubtful people..
I'm not really keeping my hopes up. I bet the last official update we'll receive is Gingerbread. Most companies focus on their flagship phones, and despite the O1's popularity, I don't think it'll receive much.
Also, IMHO, Google is going too fast. Manufacturers are having a hard time catching up and stuff.
But if you ask me, I'm contented with Froyo. Unless, of course, there's a really badass killer feature available only to future releases.
And I think this should be in the General category
kpbotbot- It's more like manufacturers use the differente Android os'es for marketing uses . Look at samsung , they're waiting to release the native 2.3 devices and bearly then will they release gingerbread for their current flagship : Galaxy S . It's a dirty world .
Yeah. Here's a super thank-able screenshot I took weeks ago
LG and Samsung seem like very different companies. The Optimus line is a very good buy for most carriers. It will convert a lot of users to the Android world like me. LG seems to catter to their users too.
The manufacturers should understand Android devices should follow Googles releases. It seems like most manufacturers just barely make the software and communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Sent from my VM670 using XDA App
why would companies spend money and time in the software when
communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Click to expand...
Click to collapse
@orlox - Imagine buying a phone that doesn't come with an operating system.
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
ccdreadcc said:
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
Click to expand...
Click to collapse
I like the idea!
Post delivered via piece of paper tied to a brick... sorry 'bout the window! XD
The reason I chose this phone is because, for me, it's a small portable computer. If only every bit of hardware of this phone had a corresponding device driver (that we can get hold of), I think there's nothing stopping us from using a full Linux desktop, or other operating systems capable of running on the ARM architecture.
Not so relevant note: Some say the bootloader is locked. True?
kpbotbot said:
The reason I chose this phone is because, for me, it's a small portable computer.
Click to expand...
Click to collapse
So true!
I am very satisfied with my first Android experience, in spite of all the bugs and hardware limitations of this cheap phone. Almost anything I needed but couldn't do before on my "dumb" phone became possible with this micro computer. So I don't really care if it's running Eclair, Froyo, Gingerbread, Ice Cream or Milk & Toast & Honey.
You would care if it was running Cupcake.
P.S There really is a possibility for us to get 2.4 on our phones. It is still called Gingerbread but it will support Honeycomb apps.
Sent from my LG-P500 using XDA App
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
kpbotbot said:
Yeah. Here's a super thank-able screenshot I took weeks ago
Click to expand...
Click to collapse
This makes perfect sense from the carrier's perspective. If people had to pay to upgrade to the next version the carriers might have more incentive; as it is now they aren't seeing any more money so why bother investing time on something that could blow up in their face.
andy572 said:
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
Click to expand...
Click to collapse
Yeah , bro , but you're one man fighting against the tides . It's bound that LG has at least a reminder of 5 man cell team working on getting gingerbread out . And besides they have other ways of getting info and ironing out bugs faster then you can .
Sad that they didn't place on the internet a god damn ETA by now .... thus I guess may or june might a realistic launch date
Oh and to be on-topic with the thread , I guess we'll see 2.4 by CM7 if any of the legendary devs still take interest in this phone ofc
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
sarfaraz1989 said:
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
Click to expand...
Click to collapse
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
andy572 said:
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
Click to expand...
Click to collapse
if everything's open then it is unlikely they make money. Then they close down and there won't be any phone.
Sent from my LG-P500 using XDA App
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
sarfaraz1989 said:
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
Click to expand...
Click to collapse
Seems like you have not worked in and managed any technology firms before.
I'm sincerely hoping your dream come true where you will own a successful openmoko company develop cutting edge technology with over 100 staff and offer your sw and hw for free with no claims to patent rights. All the best!
Sent from my LG-P500 using XDA App
http://www.samfirmware.com/apps/blog/show/8144470-will-samsung-aquire-miui-
Came across this on samfirmware:
Jeshter2000 on August 19 said:
Will Samsung Aquire MIUI ?
Specific details on how Samsung plans to bolster their software department are still developing, but we have a good idea on where they may begin.
For starters, Samsung recently hired Steve Kondik, the lead developer behind CyanogenMod, as a software engineer. If anyone has a great relationship with the community, along with the talent and skills to really shape a software department, it would be Steve. As a standalone community-driven ROM, CyanogenMod has made a tremendous impact on Android. Steve was recently quoted saying CyanogenMod would be kept separate from his new work with Samsung. But nonetheless, his talent will be applied to improving Samsung’s software.
As great as CyanogenMod is, Samsung has been known to provide a certain level of flare not usually found in CyanogenMod. The team behind CM leaves that to you and a built-in theme engine, among other customization options. There is, however, one company who does provide that flare with a ton of customization to boot: MIUI.
Although the folks behind MIUI (Xiaomi) have just released the first MIUI-branded MI-ONE phone, the company has been in partnership talks since April of this year. The two largest companies rumored for the partnership were Motorola and Samsung. Motorola’s fate has been sealed by Google’s acquisition of their Mobility division, which leaves Samsung ready, willing and able.
Could Samsung partner up with Xiaomi and start manufacturing phones with MIUI as the default UI? Could they secretly be working to bring out the world’s first CyanogenMod device? What do you think Samsung should do to improve their software department?
Click to expand...
Click to collapse
Do you think we'll ever get MIUI? (if we get CM7 at all )
This is talking about new phones.
I don't believe they will roll out that to mid-range phones. Our only hope is in xda developers
Yeah, we'll get both. This phone hasnt been out long. Give it time.
Sent from my GT-S5830 using XDA Premium App
Hi everyone,
I'm a writer for LockerGnome.com and currently putting together an article exploring Google's new Android strategy. I'm looking for some opinions, particularly from developers, about what Google's new strategy portends for ROM development.
In a nutshell, here's Google's new strategy for Android: It will be giving multiple mobile-device makers early access to new releases of Android and to sell those devices directly to consumers. (Search "site:wsj.com google" for the Wall Street Journal's report. Hopefully you'll be able to access the link I've provided, but if not: Essentially, Google will be offering consumers more phones to purchase with a "vanilla Android" experience; they will then be able to take these phones to the cellular carrier of their choice. A researcher quoted in the article believes that Google is moving toward a more iOS-like experience, with less variance among devices.
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Please let me know if I can use any of your comments in my article, and let me also know how you would like to be attributed if I use your comment(s). (Private message me, if you'd like, with a link to one of your online profiles or a website that you run, or some such thing.)
Thanks!
I'm a writer for LockerGnome and
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
nonione said:
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
Click to expand...
Click to collapse
Thanks for your comments. So with the introduction of more "Vanilla" Android devices, you believe the "flashaholic" community will continue to grow? Won't the majority of consumers who purchase the unlocked Android devices no longer have a reason to flash their devices? It's obvious that "flashaholics" enjoy optimizing and overclocking their phones (even at the expense of other things, such as battery life) -- but don't you think most consumers would prefer not to void their warranty (and would generally opt for better battery duration rather than a speed boost)?
You can use anything. Please attribute me as "lalop".
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
charssun said:
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Click to expand...
Click to collapse
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
---
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development. Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
http://t.co/9rTNXkvM
Here are some of my thoughts on the matter.
I am more excited about this than I have been for any other Android news ever! I am ready to get out of the continuous contacts and upgrade dates, especially the high prices for service.
As far as development goes, some of the best development has been done on Nexus devices, except of course the hd2... What will be good for manufacturers is that they will receive earlier updates for android allowing them to tweak their proprietary versions sooner allowing quicker updates!
For custom rom's you will see a lot of activity.
Sent from my PC36100 using xda premium
thebobp said:
You can use anything. Please attribute me as "lalop".
Click to expand...
Click to collapse
Thank you for taking the time to post your comments; my own response to yours is below.
thebobp said:
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
Click to expand...
Click to collapse
I was vague in my description of what was mentioned about device variance in the article. Here's exactly what the writer of the article stated:
Rajeev Chand, head of research at Rutberg & Co., said Android has become a kind of "Wild West" in which app developers have struggled to make sure apps are compatible with hundreds of different Android-powered devices. Both device makers and carriers have left their imprint on devices, meaning the "customer experience is highly variant", he said.
Mr. Chand said Google's shift appears to be a move "to create a more standardized experience for consumers and app developers," similar to that of Apple.
Click to expand...
Click to collapse
Does that fit what you're asserting?
thebobp said:
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
Click to expand...
Click to collapse
The term Vanilla is how the CyanogenMod "look" is described at http://www.cyanogenmod.com/about. I should have recognized that there is a world of difference between aesthetics and performance. Thanks for pointing that out.
thebobp said:
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
Click to expand...
Click to collapse
I don't have any experience with iOS devices; is there a similar incentive to modify iPhones and iPads purchased directly from Apple?
thebobp said:
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development.
Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Click to expand...
Click to collapse
One thing to note: Google will be working with "as many as five manufacturers at a time to create a portfolio of 'Nexus' lead devices that include smartphones and tablets." To me, this doesn't necessarily imply just give devices -- there could be a few devices from each manufacturer.
thebobp said:
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
Click to expand...
Click to collapse
Thanks again for your views. If I use your comments I'll be sure to attribute them to "lalop"; is there also a URL you are associated with that I may link to? If you prefer privacy, that's perfectly understandable. Also: Are you a developer?
ION vs PMEM
What is the difference?
Google is your friend - http://lwn.net/Articles/480055/
In the case of the Rezound specifically, ION is generally faster and less laggy, but has a purple tinted camera, and no working front camera (for now).
To quote shrike (I hope that's alright)
Originally Posted by shrike1978 View Post
ION is the new unified memory management architecture that Google is advancing. Prior to ION, every SoC manufacturer had their own way of doing memory management. Qualcomm's was pmem, Nvidia's was nvram, etc. It made it's debut as an option in ICS and is preferred in JB. Being unified also means that it is a good candidate for integration into the Linux kernel mainline, which would mean that Android would no longer require it's own separate branch of Linux.
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
noo_too_droid said:
To quote shrike (I hope that's alright)
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
Click to expand...
Click to collapse
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
It makes stuff awesomer
wildstang83 said:
It makes stuff awesomer
Click to expand...
Click to collapse
An answer i can understand.....thx!
Dcnovicky said:
An answer i can understand.....thx!
Click to expand...
Click to collapse
Ha, anytime my friend
Sent from my ADR6425LVW using Tapatalk 2
brenuga said:
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
Click to expand...
Click to collapse
I'll hit that thanks button just for that essay you typed
Sent from my ADR6425LVW using xda app-developers app
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