Thursday 17 January 2013

Samsung rolls-out more updates to fix the Exynos issue =


Last month, folks over at XDA developers discovered a serious flaw with the kernel used by Samsung’s Exynos chipsets which exposed the devices powered by these processors to some malicious Apps and enabled the RAM on these devices to be accessed easily. After the flaw was discovered, Samsung announced that the company would release a fix as soon as possible.
As promised, the Korean smartphone maker had started rolling out the updates to fix the issue a couple of backs, for Galaxy S3 users in the UK and now they have started to roll-out updates in the US as well. Samsung has sent a over-the-air update to T-Mobile’s Galaxy Note 2 users which according the to the company, improves security and provides bug fixes.
Meanwhile, another major carrier in the US- Sprint has also announced on it’s forums that it will release an update for it’s Galaxy S2 Epic Touch 4G within the next 30 days which will fix the Exynos issue and would also include Sprint’s Connections Optimizer.
Though, the update has still reached only a limited number of users compared to the number of people affected by this bug. There is no announcement yet about the update for international version of the Galaxy Note 2 as well as for the Verizon and AT&T Galaxy Note 2 users in the US.
As we had said in our report last month, the bug which was discovered affects the devices powered by Samsung’s Exynos 4210 and 4412 processors. The devices which are powered by these processors include- International version of Samsung Galaxy S3, International Galaxy S2, Galaxy Note 10.1, Galaxy Note 1, Note 2 and the Samsung Galaxy Camera.
Till Samsung releases the security updates for all the devices, we recommend the users to be cautious whenever they’re installing any App on their device and if possible, stick to the trusted applications till the fix arrives.


Read more: Samsung rolls-out more updates to fix the Exynos issue - iGyaan.in http://igyaan.in/2013/01/35689/samsung-fix-exynos-issue/#ixzz2IEZYtkOV

No comments:

Post a Comment