A lot of small oopses. Not really a problem, but shows that they are not as prepared as Microsoft or Apple.
Google are different from those 2. Microsoft are about "the experience" these days, Apple are designers and marketers - for both it's key that shit looks exactly how they want it to and that it works exactly how they want it to. Google are developers, they've always had these little woopsies
BTW, all the animations they finally brought to Android are very Windows Phone-like. So Microsoft's "experience" on mobile is doing something right. Let's not forget, they were also the first ones to have a flat interface.
Actually I dislike a lot of the animations in both WP and the ones shown here. They make everything slow. On iOS, they are a lot less pervasive and more tasteful.
Really? The ones on iOS 7 are slow as shit unless you tick the Reduce Motion option (although I honestly haven't really checked to see what it's like in 7.1 now with the option on/off). That's exactly what a lot of people hated about iOS 7 - a lot of useless animations. Keep in mind that the animations as shown in the Material video are exaggerated, they're not that slow (the ones that already are there).
There's a new Battery Saver mode, which can tune down the CPU, turn off the phone's radio and as a result extend its power autonomy. On the Nexus 5, for example, this should earns you 90 minutes additional usage time.
Root is, without a doubt, the (un)holy grail of the Android world. Those wonderful permissions that allow you as the user to pretty much do as you please with your device are certainly a major delight, and really one of the top reasons why Android devices have gained as much popularity as they have–not just among end users but among developers as well. There is yet another aspect of the OS that keeps people coming back for more, and that is the fresh, constant stream of updates and new OS versions. However, these two can hardly coexist with one another. Normally, whenever a new update for … well… anything comes out, it does so with features, bug fixes, and plugged holes. The latter are the ones that are normally required to obtain things such as root level access on our devices. This means that if you update, for the most part, you can kiss root goodbye. Granted, there are apps that will help root survive even an OTA upgrade but still companies making these OS and devices always are on the look out to ensure that the holes and exploits are plugged.
The latest and greatest installment of our beloved Android OS is Lollipop (Android 5), which is something that has been on pretty much everyone’s mouth in the tech world for the last week or so as it became available in the latest and most functional Developer Preview. The latest Lollipop installment is build version LPX13D, and aside from being one step closer to the final release, this one also brings the kiss of death for root, which pretty much is the case with all updates as we mentioned earlier. No biggie, right? We simply root again and be done with it, right? Or we simply use a root survival app and we keep going, right?? Nah, not exactly. There are several changes in device security, prompted in part by people and companies seeking the security and sanctuary of their precious data and nude pics. So, with that in mind, Google came to the rescue.
A Senior Recognized Developer and Senior Moderator Chainfire has been warning us of all the upcoming changes in the Android world for quite some time now, especially since the newer Jelly Bean and KitKat updates hit the shelves. Well, so far, we can officially say that he has been dead on target on everything he has said regarding the increased security on new versions of Android. The newest Lollipop update, LPX13D, seems to break root, like most updates do. However, it seems to do more than just break it because with the correct combination of factors, a device can become unrootable. Chainfire goes on to explain that the reason why root gets “broken” is mainly because the script required to grant root is no longer allowed to run at boot time from init.d, but rather it is forced to run from a SELinux dedicated context instead. This, apparently, is a new requirement for all apps and services running at boot.
The solution that Chainfire provides is to enable root at kernel level. In other words, you need a custom kernel in order to obtain root. However, many times, you need root in order to flash a custom kernel. Fine, some of you might say that by flashing via custom recovery, that the kernel can be flashed with ease. What if the bootloader is locked? Better yet, what if the bootloader cannot be unlocked? Yup, you got yourself a stock device forever (or until someone gets past the security measures). Essentially, Google is giving manufacturers a golden opportunity to put root access to rest for good. They will not do it to their devices, as the Nexus line has an unlockable bootloader, but no one can guarantee the case will be the same for other manufacturers.
The question then becomes, would the OEMs be willing to close off the devices for good, particularly considering that a large chunk of the sales come from word of mouth? Once Lollipop starts rolling out in its final form, it will be mighty interesting to see which OEMs go in what direction. One thing is for sure, these are trying times for people who enjoy their devices because of the freedom they have with root level access. Once you face the crossroad, which direction will you take?
Root is, without a doubt, the (un)holy grail of the Android world. Those wonderful permissions that allow you as the user to pretty much do as you please with your device are certainly a major delight, and really one of the top reasons why Android devices have gained as much popularity as they have–not just among end users but among developers as well. There is yet another aspect of the OS that keeps people coming back for more, and that is the fresh, constant stream of updates and new OS versions. However, these two can hardly coexist with one another. Normally, whenever a new update for … well… anything comes out, it does so with features, bug fixes, and plugged holes. The latter are the ones that are normally required to obtain things such as root level access on our devices. This means that if you update, for the most part, you can kiss root goodbye. Granted, there are apps that will help root survive even an OTA upgrade but still companies making these OS and devices always are on the look out to ensure that the holes and exploits are plugged.
The latest and greatest installment of our beloved Android OS is Lollipop (Android 5), which is something that has been on pretty much everyone’s mouth in the tech world for the last week or so as it became available in the latest and most functional Developer Preview. The latest Lollipop installment is build version LPX13D, and aside from being one step closer to the final release, this one also brings the kiss of death for root, which pretty much is the case with all updates as we mentioned earlier. No biggie, right? We simply root again and be done with it, right? Or we simply use a root survival app and we keep going, right?? Nah, not exactly. There are several changes in device security, prompted in part by people and companies seeking the security and sanctuary of their precious data and nude pics. So, with that in mind, Google came to the rescue.
A Senior Recognized Developer and Senior Moderator Chainfire has been warning us of all the upcoming changes in the Android world for quite some time now, especially since the newer Jelly Bean and KitKat updates hit the shelves. Well, so far, we can officially say that he has been dead on target on everything he has said regarding the increased security on new versions of Android. The newest Lollipop update, LPX13D, seems to break root, like most updates do. However, it seems to do more than just break it because with the correct combination of factors, a device can become unrootable. Chainfire goes on to explain that the reason why root gets “broken” is mainly because the script required to grant root is no longer allowed to run at boot time from init.d, but rather it is forced to run from a SELinux dedicated context instead. This, apparently, is a new requirement for all apps and services running at boot.
The solution that Chainfire provides is to enable root at kernel level. In other words, you need a custom kernel in order to obtain root. However, many times, you need root in order to flash a custom kernel. Fine, some of you might say that by flashing via custom recovery, that the kernel can be flashed with ease. What if the bootloader is locked? Better yet, what if the bootloader cannot be unlocked? Yup, you got yourself a stock device forever (or until someone gets past the security measures). Essentially, Google is giving manufacturers a golden opportunity to put root access to rest for good. They will not do it to their devices, as the Nexus line has an unlockable bootloader, but no one can guarantee the case will be the same for other manufacturers.
The question then becomes, would the OEMs be willing to close off the devices for good, particularly considering that a large chunk of the sales come from word of mouth? Once Lollipop starts rolling out in its final form, it will be mighty interesting to see which OEMs go in what direction. One thing is for sure, these are trying times for people who enjoy their devices because of the freedom they have with root level access. Once you face the crossroad, which direction will you take?
Well if companies are going to be cunts, this might be the end of customizing android as we know it
Yeap that sounds like really bad news. Another reason to stay with my excellent Nexus5 and its unlocked bootloader. The only difference for me is that I never flashed a custom kernel and I probably will have to do so when Lollipop is released in a couple of weeks. As long as I get to stay on stock android and rooted at the same time, all will be fine
Sony are already cunts and their phones come with locked boot loader with no ability to unlock it all, at least here is US. I think the international version gets official tool to unlock but that's mostly in Europe.
I got the MOTO G LTE and it's an amazing little phone. I don't game on mobile so everything this thing does is faster than my damn Nexus tablet. I made it almost 48 hours on normal usage without having to plug the phone in. At about 43 hours I was at 22% battery.
I got the MOTO G LTE and it's an amazing little phone. I don't game on mobile so everything this thing does is faster than my damn Nexus tablet. I made it almost 48 hours on normal usage without having to plug the phone in. At about 43 hours I was at 22% battery.
Nice! Tell us about Android L, how does it run in your new phone?
I got the MOTO G LTE and it's an amazing little phone. I don't game on mobile so everything this thing does is faster than my damn Nexus tablet. I made it almost 48 hours on normal usage without having to plug the phone in. At about 43 hours I was at 22% battery.
if you mean nexus 7 '12 with tegra then yeah snapdragon 400+adreno 305 should be snappier
Root is, without a doubt, the (un)holy grail of the Android world. Those wonderful permissions that allow you as the user to pretty much do as you please with your device are certainly a major delight, and really one of the top reasons why Android devices have gained as much popularity as they have–not just among end users but among developers as well. There is yet another aspect of the OS that keeps people coming back for more, and that is the fresh, constant stream of updates and new OS versions. However, these two can hardly coexist with one another. Normally, whenever a new update for … well… anything comes out, it does so with features, bug fixes, and plugged holes. The latter are the ones that are normally required to obtain things such as root level access on our devices. This means that if you update, for the most part, you can kiss root goodbye. Granted, there are apps that will help root survive even an OTA upgrade but still companies making these OS and devices always are on the look out to ensure that the holes and exploits are plugged.
The latest and greatest installment of our beloved Android OS is Lollipop (Android 5), which is something that has been on pretty much everyone’s mouth in the tech world for the last week or so as it became available in the latest and most functional Developer Preview. The latest Lollipop installment is build version LPX13D, and aside from being one step closer to the final release, this one also brings the kiss of death for root, which pretty much is the case with all updates as we mentioned earlier. No biggie, right? We simply root again and be done with it, right? Or we simply use a root survival app and we keep going, right?? Nah, not exactly. There are several changes in device security, prompted in part by people and companies seeking the security and sanctuary of their precious data and nude pics. So, with that in mind, Google came to the rescue.
A Senior Recognized Developer and Senior Moderator Chainfire has been warning us of all the upcoming changes in the Android world for quite some time now, especially since the newer Jelly Bean and KitKat updates hit the shelves. Well, so far, we can officially say that he has been dead on target on everything he has said regarding the increased security on new versions of Android. The newest Lollipop update, LPX13D, seems to break root, like most updates do. However, it seems to do more than just break it because with the correct combination of factors, a device can become unrootable. Chainfire goes on to explain that the reason why root gets “broken” is mainly because the script required to grant root is no longer allowed to run at boot time from init.d, but rather it is forced to run from a SELinux dedicated context instead. This, apparently, is a new requirement for all apps and services running at boot.
The solution that Chainfire provides is to enable root at kernel level. In other words, you need a custom kernel in order to obtain root. However, many times, you need root in order to flash a custom kernel. Fine, some of you might say that by flashing via custom recovery, that the kernel can be flashed with ease. What if the bootloader is locked? Better yet, what if the bootloader cannot be unlocked? Yup, you got yourself a stock device forever (or until someone gets past the security measures). Essentially, Google is giving manufacturers a golden opportunity to put root access to rest for good. They will not do it to their devices, as the Nexus line has an unlockable bootloader, but no one can guarantee the case will be the same for other manufacturers.
The question then becomes, would the OEMs be willing to close off the devices for good, particularly considering that a large chunk of the sales come from word of mouth? Once Lollipop starts rolling out in its final form, it will be mighty interesting to see which OEMs go in what direction. One thing is for sure, these are trying times for people who enjoy their devices because of the freedom they have with root level access. Once you face the crossroad, which direction will you take?
Well if companies are going to be cunts, this might be the end of customizing android as we know it
Yeap that sounds like really bad news. Another reason to stay with my excellent Nexus5 and its unlocked bootloader. The only difference for me is that I never flashed a custom kernel and I probably will have to do so when Lollipop is released in a couple of weeks. As long as I get to stay on stock android and rooted at the same time, all will be fine
they lock it for two reasons ... Piracy ... there are tons of sites that you can normally get a apk+data+obb ... no p2p or torrents or some private servers ... simple HTTP sites , heck even on Facebook or YT or other ... community sites
the second reason is Reverse Engineering on the Fly... you can turn demos into full versions ... unlock Pro versions in your LITE by simple one click apps like Lucky Patcher ... even free in game stuff fucking up theirs micro transactions ...
not speaking about unlocking phones hidden potential , overclocking , playing games from other consoles or running software that is Brand Locked like all TERGA games ...that can run with the same graphical bells and whistles on non-Tegra devices... simple put , Rooting turns your Phone into a Computer and gives you the Adim rights to YOU ... then to SONY or SAMSUNG or other phone company
Simple put they new LOLI version will have DRM ... DRM the SONY PS3 kind
There's a new Battery Saver mode, which can tune down the CPU, turn off the phone's radio and as a result extend its power autonomy. On the Nexus 5, for example, this should earns you 90 minutes additional usage time.
i ve had this on my cyanogenmod for ages, didnt know that vanilla android only got it now.
i can separately change the cpu settings for every app, also in regards to battery level and other factors it can auto-tune according to my rules.
in depth features like these are only few of the reasons why ios is only usable with jailbreak and cydia apps and without it a complete joke.
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
A Senior Recognized Developer and Senior Moderator Chainfire has been warning us of all the upcoming changes in the Android world for quite some time now, especially since the newer Jelly Bean and KitKat updates hit the shelves. Well, so far, we can officially say that he has been dead on target on everything he has said regarding the increased security on new versions of Android. The newest Lollipop update, LPX13D, seems to break root, like most updates do. However, it seems to do more than just break it because with the correct combination of factors, a device can become unrootable. Chainfire goes on to explain that the reason why root gets “broken” is mainly because the script required to grant root is no longer allowed to run at boot time from init.d, but rather it is forced to run from a SELinux dedicated context instead. This, apparently, is a new requirement for all apps and services running at boot.
