No new build of Windows 10 Mobile was released this past week, but we did learn that build 10080 would likely not be released to slow ring testers due to numerous bugs and complaints. Typically, Microsoft will release a build to the fast ring and then release it to the slow ring a week or two later with a few fixes in tow. In this case, it looks like slow ring participants will likely get a newer build of Windows 10 Mobile. Again, Aul said 10080 "isn't likely" to be released, but there is still a chance that Microsoft may roll it out .
Sunday, 24 May 2015
Windows Mobile 10 update process, build 10080 for slow ring testers
By AnonymousLumia, Microsoft, Windows 10 mobiles, Windows Phone
Windows 10 Mobile update process.
“Microsoft will continue to work closely with mobile operators on testing to meet and exceed quality bars. The input of mobile operators is invaluable to the testing process. Microsoft will use their input, as well as input from the millions of Windows Insiders, to decide when to send out mobile updates to Windows 10 devices.”
No new build of Windows 10 Mobile was released this past week, but we did learn that build 10080 would likely not be released to slow ring testers due to numerous bugs and complaints. Typically, Microsoft will release a build to the fast ring and then release it to the slow ring a week or two later with a few fixes in tow. In this case, it looks like slow ring participants will likely get a newer build of Windows 10 Mobile. Again, Aul said 10080 "isn't likely" to be released, but there is still a chance that Microsoft may roll it out .
Android's factory reset leaves personal information behind million devices
Most important data, such as user credentials, can be easily recovered from an Android handset after performing a factory reset, according to a University of Cambridge report. The feature, which is claimed to "erase all data" from the device and is especially recommended come resale time, will not work as advertised on up to million Android handsets.
A factory reset will not properly wipe the data partition, where "credentials and other sensitive data are stored", on up to 500 million handsets, while on a further 130 million devices it will not properly clean the user-accessible storage. Even worse, relying on encryption to secure sensitive data does not help.
When encryption is turned on, the report says, it is still possible to recover the encryption key, which allows recoverable data to be decrypted. The security researchers claim that they "could recover Google credentials on all devices" -- 21 popular Android smartphones, made by five different vendors, running Android versions ranging from 2.3 Gingerbread to 4.3 Jelly Bean were used for the purpose of the study.
According to Google's own data, those distributions power 50.2 percent of all Android devices that are currently in use. Those include tablets, of course, but, fundamentally, Android is the same across all devices that run it -- so, the factory reset security problems should not be limited to Android smartphones.
The report says that, among other things, an attacker could exploit the weakness of the Android factory reset to access Google accounts and backed up data linked to them -- the latter includes contacts, calendar entries, Drive files, Wi-Fi credentials and more; basically, what is selected to be synced with your Google account is at risk.
Part of the blame lies with vendors, for not delivering drivers and updates that effectively fix the problem, and the other part lies with Google, which has not implemented "support for proper deletion of the internal and external SD card in all OS versions". One of the problems pointed out is that factory reset is not consistently implemented -- triggering it from Android allows the user to also use it for the microSD card, but this option is not provided when using the feature via recovery mode.
Vendors are apparently aware that a factory reset might not work as expected, with HTC revealing on its One (M8) help page that "A factory reset may not permanently erase all data from your phone, including personal information".
There are issues even on Android 4.4 KitKat, which, in the Android Open Source Project flavor, supports full disk encryption (FDE), like every Android release after, and including, version 4.0 Ice Cream Sandwich. FDE is said to be "more appropriate" for users, but it has to be turned on from the get-go to be effective. Enabling it before the factory reset, like with other distributions, may also make sensitive data easily recoverable. The problem is not all smartphones support FDE, nor FDE for the aforementioned data partition.
Saturday, 16 May 2015
Microsoft shares What happen if you upgrade a non-genuine Windows to Windows 10
Many users have a same confusion about what happens if they upgrade a non-genuine version of Windows to Windows 10. Today according to Terry Myerson 's post, if you are using a non-genuine version of Windows and you want to upgrade to Windows 10 then, there will be a watermark placed on your desktop. Microsoft has not yet shown the non-genuine watermark in Windows 10. However, in other versions of Windows, it appears in the bottom right corner and says "This is not a genuine copy of Windows". If you buy a Windows machine that displays this message, you should return it.
He also added in his post that the Microsoft will be offering “attractive” Windows 10 offers to non-genuine Windows users.
One area Microsoft has not yet clarified is if you are part of the Insider program and upgraded a non-genuine build to the new OS, if you will still see this watermark.
Source: Microsoft via NEOWIN
Thursday, 14 May 2015
Windows Phone 8.0 devices won't be able to be unlocked for development purposes anymore
If you are a Windows Phone app developer and want to continue testing your apps on Windows Phone 8.0, you might want to take heed of an email Microsoft is sending to app developers today. After 7 p.m. Pacific time today, Windows Phone 8.0 devices won't be able to be unlocked for development purposes anymore.
Here's the text of what Microsoft is sending to app developers:
Source : windowscentral
Here's the text of what Microsoft is sending to app developers:
This shows that Microsoft is making developers distance themselves from making apps that support the older Windows Phone 8.0 in favor of the current Windows Phone 8.1 OS. Microsoft has already announced that all Windows 10 devices will have access to a "developer unlock" mode in its settings.The Windows Phone 8.0 certificate that validates developer unlocks will expire today May 13, 7pm, Pacific Daylight time. We recommend that you re-unlock your Windows Phone 8.0 test devices prior to today 7pm, to continue testing for another 24 months.After today, no Windows Phone 8.0 device will be able to be developer unlocked, and you will have three options to continue testing Windows Phone 8.0 packages: – Update the phone to Windows Phone 8.1 and unlock it for developer testing – Submit apps as beta through the Windows Dev Center and test with Windows Phone 8.0 devices – Test Windows Phone 8.0 apps via the Windows Phone emulatorAny Windows Phone 8.0 device currently unlocked will continue to be unlocked and work as a test device until its certificate expires. To maximize the time available to test with this device, please lock then unlock the device before May 13, 2015 7pm PDT.Note that this change has no impact on apps available in the Windows Phone Store, has no impact on Windows Phone 8.1 devices, nor will it impact customers with Windows Phone 8.x devices.
Source : windowscentral