Related
Is it possible at all? I know there was a hacked APK out there in around July/August, but I'm wondering if I can root with the latest version of Videos and not lose access.
I like the ability to rent from my phone and toss it up on the big screen.
That's why I haven't rooted it yet! D:
Shamrock13 said:
Is it possible at all? I know there was a hacked APK out there in around July/August, but I'm wondering if I can root with the latest version of Videos and not lose access.
I like the ability to rent from my phone and toss it up on the big screen.
That's why I haven't rooted it yet! D:
Click to expand...
Click to collapse
I contemplated making an application to assist with this process of "hiding" root in order to run Google Videos. There were too many limitations which discouraged me from being able to make the application as high quality as I wanted.
This process ends up being a cat/mouse type of game and will probably continue to be. Everytime a work around is devised for bypassing the root check in the Google Videos apk, they update the apk and step up the complexity of their process.
The best work around is probably to unroot the device, then run Google Videos. And going forward, to always make sure the device is unrooted whenever Google Videos is ran.
Otherwise, I don't think there is a sure fire solution to this process. And any modified versions of Google Videos will only be temporary solutions.
If I'm completely wrong here, I'm sure somebody with better information will post up to correct but the above information is from my personal experience studying the issue over the last few months.
Hope that helps!
joeykrim said:
I contemplated making an application to assist with this process of "hiding" root in order to run Google Videos. There were too many limitations which discouraged me from being able to make the application as high quality as I wanted.
This process ends up being a cat/mouse type of game and will probably continue to be. Everytime a work around is devised for bypassing the root check in the Google Videos apk, they update the apk and step up the complexity of their process.
The best work around is probably to unroot the device, then run Google Videos. And going forward, to always make sure the device is unrooted whenever Google Videos is ran.
Otherwise, I don't think there is a sure fire solution to this process. And any modified versions of Google Videos will only be temporary solutions.
If I'm completely wrong here, I'm sure somebody with better information will post up to correct but the above information is from my personal experience studying the issue over the last few months.
Hope that helps!
Click to expand...
Click to collapse
i am rooted and can rent and watch videos just fine on the gnex.
ogdobber said:
i am rooted and can rent and watch videos just fine on the gnex.
Click to expand...
Click to collapse
Really?! D:
I might have to try rooting the phone then!
Shamrock13 said:
Really?! D:
I might have to try rooting the phone then!
Click to expand...
Click to collapse
yes, 100%.
i have to say the quality through mhl cable to tv is quite impressive as well
I didn't want to post this in the CM9 dev thread because it is not dev related.
First off..
http://www.cyanogenmod.com/blog/security-and-you
Users will be able to configure their exposure to root as:
Disabled
Enabled for ADB only
Enabled for Apps only
Enabled for both
Click to expand...
Click to collapse
So this is what I am thinking.. The CM team is not just going to come out and say "This is how we get around Google's (and other's) 'you can't use this app if your device is rooted' thing".. But if you can disable/enable root with a setting it seems to me you wont have to worry about not being able to access certain apps, or features of apps, because of root.
Example: My "Horrible Bosses" BD came with a digital copy only accessible through the Flixster app. Because of the "security risks" Flixster will only let you view/download the movie on non-rooted devices. The simple fix to this was to download OTArootkeeper (which is an awesome app), the app essentially is a switch to enable/disable root access. Turn root off, Flixster never knows the difference.
It seems to me CM has just integrated this feature into their ROM, and maybe improved upon it. Any time an app (Flixster, Google Video & even maybe Google Wallet) will not work because you are on a rooted device, just turn it off. I have even heard of some people that cannot access databases at work because of root, seams like the same thing applies here.
So what do y'all think? Does this sound like a legitimate thought? Obviously being rooted is a security risk, and CM is becoming more mainstream. But still.. Do you think I am that far off? And do you think the "feature" will function just like I have described it? Just came to get you opinions on this change.
Sounds like you've hit the nail on the head there, although I don't see why company's don't want you consuming there content if your rooted.
Jameslepable said:
Sounds like you've hit the nail on the head there, although I don't see why company's don't want you consuming there content if your rooted.
Click to expand...
Click to collapse
The MPAA/RIAA don't understand technology, that's why. Remember SOPA/PIPA?
Why does root matter? I am rooted and can rent movies from the market with no issue. Yet people say video is blocked for rooted users. It just worked for me. Maybe cause i am rooted on stock?
RogerPodacter said:
Why does root matter? I am rooted and can rent movies from the market with no issue. Yet people say video is blocked for rooted users. It just worked for me. Maybe cause i am rooted on stock?
Click to expand...
Click to collapse
Possibly, the last time I tried I got shot down. I'm not sure which of the root option(s) the Market looks for (?). Want to test, but can't find a movie I want to see just yet.
Root matters to watch videos from the market. Unroot, watch, then reroot.
Sent from my Galaxy Nexus using xda premium
OTA Rootkeeper can temporarily unroot and then reroot any ROM. Tested and works with rented movies.
Sent from my Galaxy Nexus using Tapatalk
My job has a BYOD policy that allows everyone in the company to get their email on their phones. They make you go through the Touchdown app and MobileIron.
This program reports back to them if your phone is rooted and they disconnect your account if you are...
Try as I might, I cannot figure out what BYOD stands for.
Bring your own ****?
Buy your own douche?
Maybe my mind is just warped.
adrynalyne said:
Try as I might, I cannot figure out what BYOD stands for.
Bring your own ****?
Buy your own douche?
Maybe my mind is just warped.
Click to expand...
Click to collapse
Buy your own device?
mudferret said:
Buy your own device?
Click to expand...
Click to collapse
Probably. Don't mind me, I suffer from a deranged and sick mind.
adrynalyne said:
Probably. Don't mind me, I suffer from a deranged and sick mind.
Click to expand...
Click to collapse
I think it's Bring Your Own Device.
adrynalyne said:
Try as I might, I cannot figure out what BYOD stands for.
Bring your own ****?
Buy your own douche?
Maybe my mind is just warped.
Click to expand...
Click to collapse
Bring Your Own Device
Sent from my Galaxy Nexus using Tapatalk
... possible advantage: have a phone manufacturer use CM as their firmware? yes....?
This was actually mentioned sometime earlier... a month or 2 ago... the idea was that if the ROM provided the best level of customization, root really should not be needed for the average user... but the ROM would still have the option to enable root if the user wanted too...
craigacgomez said:
This was actually mentioned sometime earlier... a month or 2 ago... the idea was that if the ROM provided the best level of customization, root really should not be needed for the average user... but the ROM would still have the option to enable root if the user wanted too...
Click to expand...
Click to collapse
That's the problem though. The average user would not know what root is and activate it and would do something to their phone that would cause problems. U.S. carriers will not like this.
I wonder if Tasker or llama could be setup to turn root off when a particular app runs?
Sent from my Galaxy Nexus using xda premium
nicholaschum said:
I think it's Bring Your Own Device.
Click to expand...
Click to collapse
This has actually become pretty popular in the workplace now and will probably continue to grow...
And to the dude who said bring your own d.ck, I sure hope you do because carrying around someone elses is just wrong.
player911 said:
Root matters to watch videos from the market. Unroot, watch, then reroot.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
But i am renting a movie right now and it plays fine. I am rooted.
Here is a video of the feature in action:
http://www.youtube.com/watch?feature=player_embedded&v=mRyE10eKzqE
Its strange to me that some people are reporting root not affecting Google Video. I haven't tried it on my Nexus, between TiVo Netflix and Redbox there is no reason for me to, but on my Atrix when Video first released I remember it saying I couldnt use the app because my device was rooted..
Those of you able to use the Google Videos app on a rooted device, what root method did you use?
Is there a possibility that Amazon might remove the ability to side load apps with future firmware auto update, if you are not rooted?
Thank you
Sure there is. There's a possibility they could do all sorts of bone-headed things to it.
wellersl said:
Sure there is. There's a possibility they could do all sorts of bone-headed things to it.
Click to expand...
Click to collapse
But of course they never would. Because then people wouldn't be able to test their apps on it. No people testing apps == no one releasing apps.
the probably couldn;t remove the Install from Unknown Sources since it;s part of the OS. But they could try to hide it. They could try to hide file managers like ES File manager from their app store as well. It;s more truble than it;s worth. But as long as you can use ADB to push and install apps to your device we will be fine.
I think the biggest thing we need is to unlock the bootloader because that will allow you to install a custom recovery like TWRP or CWM if you want full command and control of the unit.
rbox said:
But of course they never would.
Click to expand...
Click to collapse
But of course!
In your esteemed opinion, did they deliberately cause the eFuse/locked bootloader fiasco? IOW - Was that a conscious move on Amazon's part?
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
tekweezle said:
They could try to hide file managers like ES File manager from their app store as well.
Click to expand...
Click to collapse
They don't need to hide it. They've determined that it's not compatible.
Strange to me how the Amazon app store is so void of apps that *are* compatible with my Fire TV. :silly:
tekweezle said:
the probably couldn;t remove the Install from Unknown Sources since it;s part of the OS. But they could try to hide it. They could try to hide file managers like ES File manager from their app store as well. It;s more truble than it;s worth. But as long as you can use ADB to push and install apps to your device we will be fine.
I think the biggest thing we need is to unlock the bootloader because that will allow you to install a custom recovery like TWRP or CWM if you want full command and control of the unit.
Click to expand...
Click to collapse
They can do whatever they want. They have all of the source code.
wellersl said:
But of course!
In your esteemed opinion, did they deliberately cause the eFuse/locked bootloader fiasco? IOW - Was that a conscious move on Amazon's part?
Click to expand...
Click to collapse
Very much so. They went out of their way to write a program that blew the fuse.
rbox said:
Very much so. They went out of their way to write a program that blew the fuse.
Click to expand...
Click to collapse
Now see, IMO, if I fell victim to that, I'd have them in small claims court in a heartbeat. That's just plain bone-headed consumer product management. That is... if I could prove it.
Note to Amazon: How about a *special* Fire TV with *Special Offers"?
wellersl said:
Now see, IMO, if I fell victim to that, I'd have them in small claims court in a heartbeat. That's just plain bone-headed consumer product management. That is... if I could prove it.
Note to Amazon: How about a *special* Fire TV with *Special Offers"?
Click to expand...
Click to collapse
It's common practice. All the manufacturers do it. What would you sue them for? Protecting their product? They are patching vulnerabilities.
rbox said:
It's common practice. All the manufacturers do it. What would you sue them for? Protecting their product? They are patching vulnerabilities.
Click to expand...
Click to collapse
Well... it just occurred to me. They aren't actually disabling the device, are they? I keep seeing the term "brick." If, in fact, they're bricking these devices, wrong. There's absolutely nothing that came with or on my Fire TV that says I can't root it.
Else, in terms of vulnerability, I could see them locking me out of AVOD. But they should have any say over my access to Netflix.
wellersl said:
Well... it just occurred to me. They aren't actually disabling the device, are they? I keep seeing the term "brick." If, in fact, they're bricking these devices, wrong. There's absolutely nothing that came with or on my Fire TV that says I can't root it.
Else, in terms of vulnerability, I could see them locking me out of AVOD. But they should have any say over my access to Netflix.
Click to expand...
Click to collapse
All the efuse does is prevent you from booting an old bootloader. As long as you aren't doing the things we are doing, it's harmless. But if you try to go out of your way to screw around with the software and use an old bootloader, then it will be bricked because the old bootloader will not work with the fuse blown, and it doesn't boot. It has nothing to do with rooting, nor anything to do with avod or netflix...
rbox said:
... use an old bootloader, then it will be bricked because the old bootloader will not work with the fuse blown, and it doesn't boot.
Click to expand...
Click to collapse
Still trying to grasp this...
If you aren't trying to root, why else would you use an old bootloader?
rbox said:
They are patching vulnerabilities.
Click to expand...
Click to collapse
I was only using Netflix as an example. I don't see Amazon bricking their devices to patch a competitor's vulnerabilities. Though that is a strange relationship...
wellersl said:
Still trying to grasp this...
If you aren't trying to root, why else would you use an old bootloader?
I was only using Netflix as an example. I don't see Amazon bricking their devices to patch a competitor's vulnerabilities. Though that is a strange relationship...
Click to expand...
Click to collapse
You use the old bootloader so you can take advantage of the bug in the bootloader and load unsigned code. Custom kernels, custom roms, recovery, etc.
That makes no sense... they patched a vulnerability in the bootloader and then prevent you from using said vulnerable bootloader... It has nothing to do with apps.
rbox said:
You use the old bootloader so you can take advantage of the bug in the bootloader and load unsigned code. Custom kernels, custom roms, recovery, etc.
That makes no sense... they patched a vulnerability in the bootloader and then prevent you from using said vulnerable bootloader... It has nothing to do with apps.
Click to expand...
Click to collapse
Got the first point (I think).
On the second point, Amazon can obviously patch what they perceive as vulnerabilities -unrestricted-. But as soon as they've patched me out of an otherwise legitimate use of the box, they've gone too far. IMHO.
Some years back, I filed a claim against UPS and won. I'm sure they got the paperwork and had no clue what to do with it.
More recently, I filed a claim with the BBB against Roku for the crappy firmware they pushed out on the 2XS. Roku sent me a new 2XS and a new Roku 3. Just to shut me up.
wellersl said:
Got the first point (I think).
On the second point, Amazon can obviously patch what they perceive as vulnerabilities -unrestricted-. But as soon as they've patched me out of an otherwise legitimate use of the box, they've gone too far. IMHO.
Some years back, I filed a claim against UPS and won. I'm sure they got the paperwork and had no clue what to do with it.
More recently, I filed a claim with the BBB against Roku for the crappy firmware they pushed out on the 2XS. Roku sent me a new 2XS and a new Roku 3. Just to shut me up.
Click to expand...
Click to collapse
Bypassing their secure bootchain is not a legitimate use. Exploiting a vulnerability in the kernel to gain root is also not a legitimate use.
rbox said:
Bypassing their secure bootchain is not a legitimate use. Exploiting a vulnerability in the kernel to gain root is also not a legitimate use.
Click to expand...
Click to collapse
Obviously, I'm not getting my point across. But that's ok.
Peace.
rbox said:
But of course they never would. Because then people wouldn't be able to test their apps on it. No people testing apps == no one releasing apps.
Click to expand...
Click to collapse
Hi Rbox,
This make sense thank you for responding but can the developer just be released the app in amazon app store as free and then user would just download from amazon app, unless of course it is really painful process to get an app approved by amazon for a developer than i can understand or why go thru the process again with amazon if the app is already on google play store.
It seems there are quite a few folks out there who chose not to root there device as long as they can side load any apps they want, which is fine but if Amazon goal is to lock down user on there echosystem than allowing folks to side load any apps user wants this would seriously undermine there goal (Amazon app store, AFTV device, the whole amazon echosystem), this is Just my opinion.
Thank you
ashsha7877 said:
Hi Rbox,
This make sense thank you for responding but can the developer just be released the app in amazon app store as free and then user would just download from amazon app, unless of course it is really painful process to get an app approved by amazon for a developer than i can understand or why go thru the process again with amazon if the app is already on google play store.
It seems there are quite a few folks out there who chose not to root there device as long as they can side load any apps they want, which is fine but if Amazon goal is to lock down user on there echosystem than allowing folks to side load any apps user wants this would seriously undermine there goal (Amazon app store, AFTV device, the whole amazon echosystem), this is Just my opinion.
Thank you
Click to expand...
Click to collapse
It has nothing to do with releasing apps. If I make an app for the Fire TV. I'm going to test it on the Fire TV. And the way I do that is using adb install. They can't block that, or else no one would be able to test their apps.
rbox said:
It has nothing to do with releasing apps. If I make an app for the Fire TV. I'm going to test it on the Fire TV. And the way I do that is using adb install. They can't block that, or else no one would be able to test their apps.
Click to expand...
Click to collapse
Ahh, since you put it that way it make more sense. Thank you Sir!
Also it would be a pretty stupid move for Amazon to add "Install from unknown sources" in their latest firmware's if they did not wan't people to install 3'rd party android app's on it. As you do not have to "sideload" with adb anymore, you can just install a webbrowser and browse to a web site (kodi.tv for example) click on a installer .apk and it will immediately install. You can also copy the apk to the sdcard and click on it in a filebrowser and it will install.
Amazon put that option in 1 version ago. So beginning to remove sideloading via. adb and hiding apps seems pretty silly to me.
But ofcause in theory they still have the source and the rights to do what they like..
On the one hand, Amazon doesn't have to provide support for side loaded apps, which saves them money. On the other hand, some side loaded apps allow users to access premium content for free, so Amazon might claim they lose revenue, but those users probably would never have purchased premium content from Amazon in the first place and at least they made some money off the hardware. So I would say that they won't revoke side loading functionality.
Hi!
Couldn't find any threads about this from XDA-OnePlus 3 section.
Anyway I've seen that some people do have ability to watch these videos in 60 fps but mostly if a video is in 60 fps the Youtube app gives only up to 480p resolution.
Only workaround is known to be to use youtube via chrome and request desktop version, where one can choose the 60 fps option.
Does anyone here know about the YT app resolution/framing restrictions or fixes to this particular problem?
As far as I'm aware it's something that OP needs to add support for. That is all I have been able to find on Google.
http://forum.xda-developers.com/android/apps-games/app-patched-youtube-vp9-60fps-playback-t3418216
ming3r said:
http://forum.xda-developers.com/android/apps-games/app-patched-youtube-vp9-60fps-playback-t3418216
Click to expand...
Click to collapse
Root required :/
Angristan said:
Root required :/
Click to expand...
Click to collapse
And? Root doesn't void your warranty, it's easy to do, and you can use Android Pay with it if you use systemless root Enjoy!
Angristan said:
Root required :/
Click to expand...
Click to collapse
Drats, can't root because of banking apps have root checks, and while there are root cloaks. It's a hassle.
It has been said that 1+3 is now whitelisted in the Youtube app for 60fps play (hearsay from oneplus forums)
But apparently seems now that the VP9 play has to be whitelisted also, will check that.
KoalaNalle said:
Drats, can't root because of banking apps have root checks, and while there are root cloaks. It's a hassle.
It has been said that 1+3 is now whitelisted in the Youtube app for 60fps play (hearsay from oneplus forums)
But apparently seems now that the VP9 play has to be whitelisted also, will check that.
Click to expand...
Click to collapse
Aah! My banking app doesn't detect systemless root over here in the UK so I'm sound
manor7777 said:
And? Root doesn't void your warranty, it's easy to do, and you can use Android Pay with it if you use systemless root Enjoy!
Click to expand...
Click to collapse
Yes but I just received my OP3, forgot to root it, and to root you have to unlock the bootloader, which erases all the data.
Angristan said:
Yes but I just received my OP3, forgot to root it, and to root you have to unlock the bootloader, which erases all the data.
Click to expand...
Click to collapse
Same here (and I came from a Nexus 5 where I unlocked the bootloader first day!)
By the time I had added my bank app, my two-stage authenticators for steam, microsoft...etc etc I suddenly thought about that too.
But in all honesty, with OxygenOS currently I feel no need to root it (yet?) and erasing my whole device just to fix youtube and have to re-setup all of that is a massive pain in the but.
GiantAxe said:
Same here (and I came from a Nexus 5 where I unlocked the bootloader first day!)
By the time I had added my bank app, my two-stage authenticators for steam, microsoft...etc etc I suddenly thought about that too.
But in all honesty, with OxygenOS currently I feel no need to root it (yet?) and erasing my whole device just to fix youtube and have to re-setup all of that is a massive pain in the but.
Click to expand...
Click to collapse
Though slightly off topic, move your authentication to Authenticator Plus (has android wear support too) or Authy, and then even if you wipe your device, you can just re download an app and they will re-sync Authy is free, but i prefer Authenticator plus.
You can always use the OGYoutube app, but you won't be able to login unless you have Xposed installed
I've heard that it is something that Google has to do by adding OnePlus 3 in to their database and OnePlus cannot do anything about that until Google sorts it out. (People with LG G5s and HTC 10s are also having this problem)
manor7777 said:
Aah! My banking app doesn't detect systemless root over here in the UK so I'm sound
Click to expand...
Click to collapse
That's I interesting as I have been holding off rooting because I use barclays banking and also pingit. Do you know if these work and also why did you decide to root. Back in the day would have done immediately but trying to justify it now is tough when oneplus keep rolling out updates every 2 weeks ota.
ipmanwck said:
That's I interesting as I have been holding off rooting because I use barclays banking and also pingit. Do you know if these work and also why did you decide to root. Back in the day would have done immediately but trying to justify it now is tough when oneplus keep rolling out updates every 2 weeks ota.
Click to expand...
Click to collapse
Their really isn't too much of a reason. I like a few root utilities e.g to access kernel settings and that's about it. For banking, I know Halifax and lloyds work with systemless root. Like you don't even need to turn it off. Just opened the barclays app as I'm not with them and it doesnt seen to like systemless root, or more it works with systemless root but it detects the SuperSU application. If you can mask that with systemless xposed you should be sound
AlvieOP said:
I've heard that it is something that Google has to do by adding OnePlus 3 in to their database and OnePlus cannot do anything about that until Google sorts it out. (People with LG G5s and HTC 10s are also having this problem)
Click to expand...
Click to collapse
Yes the infamous whitelisting of Google Corp.
I've contacted Youtube support to specify if the OnePlus 3 truly is whitelisted for 60 fps although not expecting an answer from them. Because on the official oneplus forums, one of the users said that it 1+3 is now whitelisted (as of newest version of the YT app)
But it still doesn't work so either the user is wrongly informed, youtube support lies or VN9 - decoding must be whitelisted also. Or I'm way too far in the speculation swamp and the problem lies somewhere else.
KoalaNalle said:
Yes the infamous whitelisting of Google Corp.
I've contacted Youtube support to specify if the OnePlus 3 truly is whitelisted for 60 fps although not expecting an answer from them. Because on the official oneplus forums, one of the users said that it 1+3 is now whitelisted (as of newest version of the YT app)
But it still doesn't work so either the user is wrongly informed, youtube support lies or VN9 - decoding must be whitelisted also. Or I'm way too far in the speculation swamp and the problem lies somewhere else.
Click to expand...
Click to collapse
I'll check, but maybe it depends on which version (China / Europe / NA)
Edit : just checked, still not working at least most people still don't upload in 60FPS
AlvieOP said:
I'll check, but maybe it depends on which version (China / Europe / NA)
Edit : just checked, still not working at least most people still don't upload in 60FPS
Click to expand...
Click to collapse
It should be whitlisted by now or at least in some regions I guess?
I'm getting 1080p 60fps on the stock youtube app running OOS 3.2.2
I've had the same issues but ever since the 3.2.1 update that came out 3 weeks ago, I have been able to view 1080p60 videos. I had to clear app data and the cache a couple times but it works for me.
I watch a lot of gaming vids in 60fps so having to watch them in 480p for a while was maddening.
fusionXERO said:
It should be whitlisted by now or at least in some regions I guess?
I'm getting 1080p 60fps on the stock youtube app running OOS 3.2.2
Click to expand...
Click to collapse
I encouraged one user from OP forums to do YT app re-install and warned him that he might lose the 60 fps play, and he did lose it.
You can try it too but be warned
Seems that the app itself does not recognize the phone model or some such...
fusionXERO said:
It should be whitlisted by now or at least in some regions I guess?
I'm getting 1080p 60fps on the stock youtube app running OOS 3.2.2
Click to expand...
Click to collapse
Are you from Europe or North America? It isn't working for me here in Europe. (UK)
Just a quick question, does unlocking the bootloader on the pixel 3 disable widevine in Netflix etc like it goes in some other devices? Thanks
duracell07 said:
Just a quick question, does unlocking the bootloader on the pixel 3 disable widevine in Netflix etc like it goes in some other devices? Thanks
Click to expand...
Click to collapse
no it doesn't but there are few who have had issues.
check here... https://forum.xda-developers.com/pixel-3-xl/help/widevine-level-3-drm-stock-locked-t3923766
What I mean is you still have L1 but because certain apps detect an unlocked bootloader they won't give full hd. It definitely different with pixel 3 then?
Thank you
duracell07 said:
What I mean is you still have L1 but because certain apps detect an unlocked bootloader they won't give full hd. It definitely different with pixel 3 then?
Thank you
Click to expand...
Click to collapse
If you have L1 then nope no other app restricts you from viewing hd stuff based on DRM.
If you speaking about banking apps and stuff that's different for example gpay does restrict you from adding a card if you unlock bootloader and still has L1
Haven't heard any media streaming app which restricts.
If you have any app then i can check if the bootloader unlock messes it up or not.
Same goes for Pixel 3xl and other devices. If your device state is L1 it should be fine for media streaming apps.
Sent from my Pixel 3 using XDA-Developers Legacy app
If you could on pocophone Netflix wouldn't even show up on play store if you had bootloader unlocked and Amazon wouldn't play full hd. Banking apps worked as long as you didn't root and even with root using magisk and some other tricks you could get around it. Im just very tempted to flash a kernel to increase screen brightness, Google's clearly crippled it to try to hide the fact the battery is small but in direct sunlight its terrible
duracell07 said:
If you could on pocophone Netflix wouldn't even show up on play store if you had bootloader unlocked and Amazon wouldn't play full hd. Banking apps worked as long as you didn't root and even with root using magisk and some other tricks you could get around it. Im just very tempted to flash a kernel to increase screen brightness, Google's clearly crippled it to try to hide the fact the battery is small but in direct sunlight its terrible
Click to expand...
Click to collapse
No idea about pocophone. But all the devices I have used with bootloader unlocked worked fine with Netflix just had to hide root stuff. Pixel 3 does for sure and you could see it from the thread linked earlier.
Gpay messes up even with bootloader unlocked and no root. So I am going to leave that app as it is unless there is no other banking alternative in android world ?
Well battery is yeah could have beefed up more personally it takes me through the day I needed and lighting in sunlight with auto bright is fine for me or I am blind lol.
Sent from my Pixel 3 using XDA-Developers Legacy app