One of the largest problems currently facing Google's Android operating system is the great degree of fragmentation due to the many different products that manufacturers and carriers have brought to the market. As it stands now, there are four different versions of Android software on various handsets: 1.5, 1.6, 2.0, and 2.1. The reason for this can be attributed to the inevitable differences in hardware, third party software (such as HTC's Sense UI), and the carrier or manufacturer's capacity to update their products.
Currently released Android phones ordered by their supported Android version so far include the following:
* 1.5: HTC Hero, T-Mobile Pulse, LG GW620, Motorola Cliq, Motorola Backflip, Samsung Behold, Samsung i7500, Samsung Moment
* 1.6: HTC Dream, HTC Magic, HTC Tattoo, Motorola Devour, Sony Ericsson Xperia X10
* 2.0: Motorola XT800
* 2.1: Google Nexus One, HTC Legend, HTC Desire, Motorola Droid, Samsung i5700
This large degree of platform fragmentation finds users and developers unable to take advantage of newer features and bug fixes that the latest release holds. For example, users without Android 2.0 or higher are left without Exchange support and new UI improvements, among other things. Taking note of these critical problems, Google will tackle the issue head on by taking their software into their own hands for their next Android release.
Named "Froyo", Google's next Android version will be detached of the usual set of first party applications and core components that currently populate the OS. Instead of bundling those applications with the operating system, Google will instead make them available through the Android Market for download. This is currently how updates to Google Maps are handled on Android.
This new approach will apply to both Android applications and system components. So for example, if Google brings a new update to the virtual keyboard or email application, all one would have to do is download the update directly from the Market as it instantly becomes available. No longer would users have to wait for their carrier or manufacturer to make it available for download.
Also reported is that Google is finishing up most of the core work required for Android and will soon be shifting development to consumer features and applications. Developers should be getting finalized APIs and frameworks as Froyo arrives, so they can instead focus on making applications faster and easier with greatly matured tools for the OS.
Source - http://www.neowin.net/news/google039s-solution-to-android-fragmentation-coming-in-039froyo039
not my artical just found it orig web page
androidandmeDOTcom/2010/04/news/android-2-2-is-coming-what-features-do-you-want/
replace dot = .
Android 2.2 is coming. What features do you want?
By Taylor Wimberly on Apr 20267
The majority of Android phones are still running an outdated firmware, but that hasn’t slowed Google from advancing their mobile operating system. Everyone knows the next version of Android (codenamed Froyo) is on the way and the rumors (1, 2) are beginning to pick up that the Nexus One will receive it soon.
Based on the data from our analytics reports it appears Google has already begun testing on their next firmware – Android 2.2. Google engineers have routinely given codenames to future builds of Android (Eclair, Froyo, Gingerbread, etc.), but they don’t receive a point release till they are finalized and nearing distribution.
We have shared this reporting data before and people are always quick to point out that it can be easily faked, but I have spoke with additional sources familiar with the matter who confirmed Android 2.2 is currently being tested.
The feature set for Android 2.2 was frozen long ago, but it remains mostly unknown. Google decided last year that they would no longer publish public roadmaps for future versions of Android. Based on the information we can gather, it appears Android 2.2 will mainly focus on performance enhancements.
Some of the rumored features for Android 2.2 include:
•JIT compiler
•Free additional RAM
•OpenGL ES 2.0 enhancements
•Flash 10.1 support
•Fixed problem with “crazy screen” / Resolution of cross multitouch
•Activation of Color Trackball
•Enable FM radio
Some of these features are plausible and others we have no clue.
The JIT compiler has already been confirmed by Google and we expect to find out new details during Google I/O. Android engineers will be leading a discussion that informs devs how to test and tune their apps to work with the new compiler.
Additional free RAM should come thanks to the new Linux kernel being used in Froyo. Google is moving from 2.6.29 to the newer 2.6.32 which makes it possible to address the extra RAM. This has already been done in custom ROMs like CyanogenMod so expect this feature for sure.
I’m no expert on OpenGL, but it has long been rumored that Froyo (or a future build) will add new APIs to the Android NDK which will let Java devs have full access to the OpenGL ES 2.0 library.
Flash 10.1 is coming in the first half of the year. It is entirely possible it could be tied to a future Android firmware and be included with an OTA update.
We have already addressed the HTC touch sensor issues. It sounds like a future software update could be used to clean this up a little.
Multicolor trackball notifications are definitely coming. Android hackers like ChainsDD have already unlocked this feature for users of custom ROMs. Google advertised the multicolor trackball during its launch of the Nexus One, but the feature was cut from the final Android 2.1 build.
When it comes to the FM radio, I have no idea. Other HTC phones on a similar Snapdragon platform (Desire and Incredible) include the FM radio so it’s not out of the question that the N1 has it too.
I spoke with Google’s Eric Tseng during CES and he told me there were many secrets left in the Nexus One that we would discover later.
When is it Android 2.2 coming out?
Circle May 19th on your calendar. This is the opening day of Google I/O and I’m anticipating the release of Android 2.2 (and maybe the Flash 10.1 beta) will be tied to this event. Google has provided every developer attending the event a free Droid or Nexus One, so it is possible to see a simultaneous release on both devices.
I’m really curious how first generation devices are going to play with this release. We are expecting most phones to receive Android 2.1 this month, so it will be interesting to see how Froyo fits in. Some of the Android engineers have been talking about Froyo on the Google boards and it is unclear if the HTC Dream and Magic will be able to support it since they only have 192 MB of RAM.
p.s. if in wrong spot please move it im a tootal newb
I hope e this is try, and can run in our beautifful HD2.
...because i can't leave without Copy\Past feature in a smarthone SO....until that, i'm on Android scene.
http://www.winrumors.com/rumor-windows-phone-7-update-on-february-7/
Windows Phone 7 update on February 7
54 minutes ago...
Microsoft may be gearing up to release its first Windows Phone 7 update on February 7 according to reports.
LiveSide has tracked a number of French sites that suggest Microsoft will release its first Windows Phone 7 update on February 7. There’s no proof that the date is accurate and the timing is odd given that Microsoft chief Steve Ballmer will be in Barcelona on February 14 for the Mobile World Congress. Whether or not the date is accurate, WinRumors can confirm that Microsoft has Released to Manufacturing (RTM) its first update codenamed “NoDo”.
Microsoft’s first update will improve application start-up and resume times and introduce the important copy and paste feature. Microsoft posted a support article earlier this week that details the update process for Windows Phone 7 devices. The support article has led many to believe that the update is due imminently.
Microsoft revealed earlier this week that it has now shipped 2 million devices to carriers. Microsoft previously revealed that the company had shipped 1.5 million Windows Phone 7 units between the October launch and December. Research firm IDC and application platform Appcelerator recently surveyed over 2,000 developersto work out their intent for 2011. Developer interest for Windows Phone 7 rose 8 points to 36% ‘very interested’ according to the results. IDC says the interest was “due to a better-than-expected launch.” Survey respondents also said that “Windows Phone’s improved UI was a critical factor for the increase.”
Microsoft also revealed there are now 24,000 registered Windows Phone developers and over 6,500 applications in the marketplace. Microsoft’s customer satisfaction rates on Windows Phone handsets are at 93% according to the company. Microsoft is believed to be planning to unveil a second bigger update in February at the Mobile World Congress show in Barcelona, Spain. Microsoft’s second update will introduce enhanced developer controls for applications and updated Silverlight components.
Joe Belfiore, who oversees Windows Phone Program Management, and is responsible for the design and software product definition of forthcoming generations of Windows phones will keynote MIX11 this year. Belfiore is expected to layout a roadmap for the future of Windows Phone 7 and detail Microsoft’s second Windows Phone 7 update. Microsoft is also working on a major overhaul of the Windows Phone 7 browser. In a job posting, listed in November, the software maker promises a “major overhaul of standard support and new approaches to make significant advances in performance, power consumption and bandwidth utilization.” Microsoft may be ready to detail its future Internet Explorer mobile plans at MIX in April too. Microsoft is believed to be planning Flash and HTML5 support for Windows Phone 7.
Click to expand...
Click to collapse
Lets wait, and see if Microsoft wants ot not, more embassatores for WP7s.....
From what i'm reading it seems to me that microsoft won't block htc hd2 phones, they want developers to go to windows phone 7, they want ratings to go up.
So to me is they won't block access for htc hd2's.
After the update...
Microsoft, does NOT want hackers and independent developers modifying their OS. The HTC HD2 will be excluded from the update. If Microsoft wanted this and other devices like it on the new OS, they would lighten up on their restrictions. After all THEY are the ones that control it.
The WP7 update will close the bug that allows the Chevron tool to work. Our only hope is that someone will hack the update to work. It's going to be much harder this time, as MS had some help and insight from the Chevron guys! Time will tell us for sure.
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
I appreciate your train of thought, and love the optimism
Is there something like a kudos button here?
neugroove said:
I appreciate your train of thought, and love the optimism
Is there something like a kudos button here?
Click to expand...
Click to collapse
No, But he just said it
MS will surely shut down that bug on their os and no longer hd2 with wp7 ,but for surely they will hack into it , MS answered me that porting WP7 to HD2 WAS NOT ILEIGAL
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
I wish I shared your optimism and hope you are correct, but from what I can understand, the update will effectively push out a new ROM having backed up the old one first.
Whatever black magic the DFT guys did to hack the ROM to work on HD2 would surely be undone? I therefore believe we won't get the update unless and until the DFT hack it.
There could be stuff below the ROM level that won't be affected and it could be this stuff that DFT tweaked - not knowing the architecture of WP7 I couldn't comment.
Being a pessimist, it just feels too good to be true that a update would work without any issue - hope I'm wrong though. This could be how MS propose to close the HD2 loophole. It would even work quite well for MS. Having had a taste of WP7, how many of us might go out and buy a WP7 phone having had an extended trial and then being cut off from our dealer...
Gustopher said:
I wish I shared your optimism and hope you are correct, but from what I can understand, the update will effectively push out a new ROM having backed up the old one first.
Whatever black magic the DFT guys did to hack the ROM to work on HD2 would surely be undone? I therefore believe we won't get the update unless and until the DFT hack it.
There could be stuff below the ROM level that won't be affected and it could be this stuff that DFT tweaked - not knowing the architecture of WP7 I couldn't comment.
Being a pessimist, it just feels too good to be true that a update would work without any issue - hope I'm wrong though. This could be how MS propose to close the HD2 loophole. It would even work quite well for MS. Having had a taste of WP7, how many of us might go out and buy a WP7 phone having had an extended trial and then being cut off from our dealer...
Click to expand...
Click to collapse
Yeah right, I wouldn't buy the same hardware again, I would consider if at least any of the wp7 phones get the Desire HD hardware, but none of them has it. If the update stop us from wp7 then I'll stick with android and wait for the next major hardware upgrade then I will look for another phone.
Voluntary update?
My understanding is that the update will not mandatory.
You can choose to update you system or not. So our HD27's will still work once the update is released - we just wont have the new features or be able to run apps that use the new featrues.
I thinks the chances of the update working are fair to good. From what I have gathered the biggest problem the DFT team had was getting magldr and the WP7 OS to play well together from NAND.
I may be wrong - but I like the "glass half full approach".....
I don't think you could update the hd2 , and if I was DFT I had prevented it from updating to (just to be sure that there are after a update no 14000 bricks)
i wouldn't be surprised if the HD2 could flawelessly get the update. Since it is an MS update, none of the hardware specific software/drivers will be affected. Otherwise, MS has to push updates for specific devices and that is not what they are planning to do. But who'll know? I am sure to be the first to try that out and if I will brick my device, than so be it. I don't think the HD2 can be bricked beyond repairing. With all the great tutorials, first aid guides here on XDA, I think it is safe to try it.
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
They can detect it from IMEI, first 8 digits state the manufacturer and model. There are DBs on the net to verify IMEI against phone maker and model. e.g. imei-number.com/tac-list
MerLinh said:
Yeah right, I wouldn't buy the same hardware again, I would consider if at least any of the wp7 phones get the Desire HD hardware, but none of them has it. If the update stop us from wp7 then I'll stick with android and wait for the next major hardware upgrade then I will look for another phone.
Click to expand...
Click to collapse
Fair point. Until DFT WP7 I was at a loss though; WM6.5.5 is dying through lack of new stuff, I didn't fancy WP7 and having had a play with Android it just irritates me - I know it can be changed but the default colour scheme and design looks like it was done by a class of 7 year olds with a box of crayons (NB: my opinion, apologies Android-lovers).
So at least I know now that I could go out and buy a WP7 device, but you are quite correct that the launch phones are a disappointing bunch, with nothing one whit better than my HD2.
I have a hunch that something sexy must be coming as WP7 slowly gathers momentum, so I'll hang onto my money for now.
What to do if the update breaks the HD2(7) though...
(Accepting that it may well be optional and might well not break it even then)
hyellow said:
i wouldn't be surprised if the HD2 could flawelessly get the update. Since it is an MS update, none of the hardware specific software/drivers will be affected. Otherwise, MS has to push updates for specific devices and that is not what they are planning to do. But who'll know? I am sure to be the first to try that out and if I will brick my device, than so be it. I don't think the HD2 can be bricked beyond repairing. With all the great tutorials, first aid guides here on XDA, I think it is safe to try it.
Click to expand...
Click to collapse
Huh, I wouldn´t count on that. I can definitely imagine the updater could be able to detect the phone you are using (many of us showing "HD7") and upload specific drivers, too - the original WP7 devices did receive some updates already. To make the updates user friendly, they maybe include those brand/operator specific files and drivers, who knows. And replacing the DFT/Leo70 driver material with original HD7 versions might maybe brick the system...
galatei said:
They can detect it from IMEI, first 8 digits state the manufacturer and model. There are DBs on the net to verify IMEI against phone maker and model. e.g. imei-number.com/tac-list
Click to expand...
Click to collapse
Now that seems to be a bit far stretched... but who knows... modern times, no?
At least, it would kind of confirm my thoughts above...
It could be that we may get the update and install it OTA,but in absence of any immediate DFT or Chevron Development efforts we could very well get stuck with WP7 on our HD2s !!!.
I'm pretty sure we won't be able to update our phones successfully with MS's update... we'll probably have to wait until DFT releases an update to flash manually. But unless DFT pre-hacks the registry to make it show up as a HD7, we will have problems doing anything with it until a new way to unlock it is discovered. We'll have to wait and see what happens, but we will probably be stuck without updates for a while I think.
the only update i am looking forward to is massively improved battery life, this has to be from DFT.
haksam said:
the only update i am looking forward to is massively improved battery life, this has to be from DFT.
Click to expand...
Click to collapse
Really? How can you live without Copy \ Past feature? I use WP7s for 3 days, and was very annoying without that feature.
And I miss, only copy /past but too, more share options and multitasking.... I like very much the UI, but I need quickly this features added.
Sent by my HD2 Gingerbread device
benjaminries said:
I actually don't understand how Microsoft could exclude the HD2 from the update, given the current architecture. Their own Marketplace servers think the HD2 is an HD7... if they could detect the difference, they would have blocked us already.
We know that Microsoft has designed the WP7 to have complete and total seperation between the OEM and carrier's device-specific modules on the one hand, and the vanilla OS on the other. Microsoft's updates are exclusively for the latter portion of the OS, which is why they can push out a single update package to all unlocked devices *directly*.
In short, my money is on the first update working just fine for the HD2, breaking very little in the process. It isn't a question of what Microsoft secretly wants. This is about HTC building the HD7 out of almost all the same hardware as the HD2, and any small differences were easily patched up by DFT.
I might add that since Microsoft has triumphantly announced that NoDo will break ChevronWP7, wouldn't you expect them to also announce that they had closed an HD2 loophole?
Click to expand...
Click to collapse
actually, think about it, there is one single blindingly obvious difference thats so easy to detect they could get a 10 year old to locate them.
How many buttons do you have on your HD2? i wouldnt be sure there was no way of knowing. even if we take that out you'll still have some kind of unique signature on the cracked OS that we have all used, it would be near on impossible to hide the fact its an HD2 and not an HD7 if they really wanted to find out.
Hello all
I ask everyone who has a device from Samsung company not to close the tab and read to the end of this post.
I'll start with the prehistory. My first Android-tablet was Samsung Galaxy Tab 7.7. I was incredibly happy because it was a unique device. Screen, build quality, metal, processor and capacious battery. I could not get enough of. I bought it for $ 721. it was in June of last year, I must say he has a birthday coming up.
And just a month later I got an update ice cream sandwich. It was the best firmware, and no matter what that summer, Google released a jelly bean.
Time passed, and Samsung is not going to renew our wonderful tablet to the latest version of android. I was waiting for. My patience ran out in March 2013.
March 7 I began to send in the forums with the topic of the samsung galaxy tab 7.7 messages with calls about the attack of the official pages of Samsung in social networks messages such as "We want Jelly Bean for Galaxy Tab 7.7!!!".
We are bombarded official page Samsung USA, Samsung and Thailand. I want to believe that they have heard our cries and dissatisfaction. And 29 days ago, Samsung launched the upgrade to Jelly Bean for Thailand. And that's it. certainly present in the firmware English language, but what about those who live in the countries of the CIS? Those who know neither Thai nor English language. The same China and Japan!
29 days have passed. and no region except Thailand did not get updated until now. I wrote about this in support of Samsung, the country where I live (Ukraine), but I was told that there is no information about the update, and until.
So my dear friends, and just those who are indifferent to our problem, and in general the problem of updating all Samsung devices, I urge you to attack samsunga page on facebook and other social networks. I think it will suit us more than the banner of
"I hate samsung for that instead of an update for my device, it produces a copy of it with a modified design !!!."
official Samsung Support page on Facebook
official Samsung Thailand page
Samsung Mobile Thailand
I will be grateful for the repost of this topic in any topics on xda/social networks
Thanks All
OK. You have taken the trouble to write this and I have taken the trouble to read it.
My own criticism of Samsung lies in the slowness of the update to the latest versions of Android in the first instance. But Samsung are not alone in this regard, that is not an excuse as such but it is a reality of owning an Android device. That is, outside of a Nexus, I hasten to add to ward off those of a pedantic disposition.
Secondly that this tardy update is exacerbated by the long drawn out releases for each territory's firmware. This was an overall nine month process in the case of Ice Cream Sandwich v4.0.4.
Nonetheless, Samsung did come through and now has released the initial firmwares for Jelly Bean 4.1.2 with, presumably, the remaining territories to follow in due course.
To repeat this fact for emphasis, Samsung has released JB for our devices. I should know, I am running the Singapore version on my Netherlands Tab.
Looking at the state of Android fragmentation generally, I have to content myself with gratitude and applaud Samsung for not forgetting about us. However late in the day this might be. In my opinion it is churlish to whinge in the manner of your post. Lack of patience is a personal failing and so is an inflated sense of personal entitlement. Why look to transfer these personal shortcomings as being Samsung's responsibility?
As for your slogan "I hate samsung for that instead of an update for my device, it produces a copy of it with a modified design !!!." Sorry but I don't understand it, it is doesn't make sense to me and certainly I will not hate Samsung. I would respectfully suggest that you reconsider this effort and phrase your concerns in more positive, constructive and helpful sentiments. Attacking, hating and bombarding are not tactics that I would ever employ.
So there is no way that I will be party to such a petition. Other opinions may vary of course.
Still waiting for ANY kind of official JB support for the P6810 model. Although I blame them, don't hate them for it though.
Sent from my GT-I9500 using xda premium
I can only say this.. ..
Patience is virtue.. ..
I waited 3-4 months for JB after it first came out.... Now after its available for P6800... amazingly I'm still on ICS...
If you so desperately need JB and don't understand Thai or English, have this resource pages translated in Google.
You'll find instructions to upgrade via Mobile ODIN, using the Thai or Singapore versions.
Then, do the same to download and activate the specific language you need.
I am already running JB with the SIngapore version and Portuguese language pack on a device bought in the Netherlands.
It is not cool to point out Samsung tardiness, while not doing all you can do to solve your problem.
I should also point out that, if you want to be a tech enthusiasts as we all are and a "must have the latest" kind of enthusiast, as you seem to be, you really should find a way of learning English, or you'll be continuously frustrated.
Just a thought...
XK
The USA has another reason: Most 7.7 are locked to Verizon. I felt fortunate to receive ICS. Samsung will point to Verizon and say it's up to Verizon and Verizon will say...
XDAKhan said:
If you so desperately need JB and don't understand Thai or English, have this resource pages translated in Google.
You'll find instructions to upgrade via Mobile ODIN, using the Thai or Singapore versions.
Then, do the same to download and activate the specific language you need.
I am already running JB with the SIngapore version and Portuguese language pack on a device bought in the Netherlands.
It is not cool to point out Samsung tardiness, while not doing all you can do to solve your problem.
I should also point out that, if you want to be a tech enthusiasts as we all are and a "must have the latest" kind of enthusiast, as you seem to be, you really should find a way of learning English, or you'll be continuously frustrated.
Just a thought...
XK
Click to expand...
Click to collapse
The problem is, people shouldnt have to do all this to get jb for their mobile devices.
It's not just a Samsung problem. Sony too is dragging their feet with the updates. The real issue is android. Instead of a different version for each region, it should be a universal update. And a language pack should be available for download via google play.
I can see why Samsung decided to test out tizen. Although it would be a lot easier to stick with windows....
And samsung should stick to making devices.
vbx said:
The problem is, people shouldnt have to do all this to get jb for their mobile devices.
It's not just a Samsung problem. Sony too is dragging their feet with the updates. The real issue is android. Instead of a different version for each region, it should be a universal update. And a language pack should be available for download via google play.
I can see why Samsung decided to test out tizen. Although it would be a lot easier to stick with windows....
And samsung should stick to making devices.
Click to expand...
Click to collapse
Agreed.
Mentioned nearly the same thing in past threads, although I still believe is fully Samsung. Not too difficult for THEM to compile P6810 JB firmware after (Asia) already releasing it for its brother. Maybe they over comitt themselves with too great a range of products, and those products that sell volume have much greater priority?
As you said, language packs are the way to go
Sent from my GT-I9500 using xda premium
vbx said:
The problem is, people shouldnt have to do all this to get jb for their mobile devices.
It's not just a Samsung problem. Sony too is dragging their feet with the updates. The real issue is android. Instead of a different version for each region, it should be a universal update. And a language pack should be available for download via google play.
I can see why Samsung decided to test out tizen. Although it would be a lot easier to stick with windows....
And samsung should stick to making devices.
Click to expand...
Click to collapse
And please tell me, what reason is there on Android's code that forbids a single universal update?
All firmware versions work with all devices (of the same model obviously). You can use a modem for any region. You can enable languages that aren't enabled by default. Android allows all that.
The problem isn't Android. It's the manufacturers' internal organization, the specific contracts with local operators, and the required tests by local regulation agencies that limit official availability.
Researchers at Bluebox Security have revealed a disturbing flaw in Android's security model, which the group claims may affect up to 99 percent of Android devices in existence. According to Bluebox, this vulnerability has existed since Android 1.6 (Donut), which gives malicious app developers the ability to modify the code of a legitimate APK, all without breaking its cryptographic signature -- thereby allowing the installation to go unnoticed. To pull off the exploit, a rotten app developer would first need to trick an unknowing user into installing the malicious update, but hackers could theoretically gain full control of a user's phone if the "update" posed as a system file from the manufacturer.
Bluebox claims that it notified Google of the exploit in February. According to CIO, Bluebox CTO Jeff Forristal has named the Galaxy S 4 as the only device that's currently immune to the exploit -- which suggests that a security patch may already exist. Forristal further claims that Google is working on an update for its Nexus devices. In response to our inquiry, Google told us that it currently has no comment. We certainly hope that device manufacturers do the responsible thing and distribute timely security patches to resolve this issue. Absent that, you can protect yourself by installing updates through the Play Store and Android's built-in system update utility.
Source:
http://www.engadget.com/2013/07/04/bluebox-reveals-android-security-vulnerability/
They ust read this here and on an Australian news website, news.com.au, they recommend;
So what can I do about this?
- Do not allow apps from unkown sources. To do this go to Settings, Security and untick "allow unknown sources".
- Well, the news isn't good. Until further notice, news.com.au recommends that you don't download any non-Google apps.
- Bluebox has recommended that users update their operating system to the latest version.
- Also, if you have any apps which store your personal information such as credit card or PayPal information (like eBay, Amazon or Etsy), you should remove this information immediately.
- Remove any personal information from your phone (do you have your credit card pin stored in your notes? Get rid of it)
Crap advice for majority of users I feel.
Most users will have 'unknown sources' off by default but they advise not download any non Google app even from the play market as mentioned elsewhere in article.
They say to update your phone, how easy is that to do when carriers and manufacturers don't release up to date firmware for phones..
That is fine for people like us that flash new Roms all the time but for normal folk it's not a viable solution.
I don't really think the threat is so great, going by those that report such though we all had better stop using android..
I am more concerned with apps using other apps permissions/data flaw
and google play update/install protocall being not encrypted/catchable and falsifyable.
Regarding what is stated in article, this was known almost day 1 which is why from beginning android said dont install non market stuff. And it has also been known crapware has entered market.
So all in all, its an obvious article.
Sent from my GT-N7000 using Tapatalk 2
I totally agree baz77, this has been know for a very long time now. There are also quite a few apps in Play that are "crapware".
The issue has been fixed on Google's side and CyanogenMod (08/07 nightly and yesterday's security release CM10.1.1.)
Now, it is up to the OEMs to follow
I guess I got it wrong, it is a separate issue, glad the pros getting it fixed, they need to be applauded! Salute!
Sent from my GT-N7000 using Tapatalk 2