Develop Bugs

NFC Good for Anything? [ Android Pay on the Fire Phone ]

So the fire phone supposedly has an NFC chip in there... is it good for anything? Does it work? With Amazon wallet gone, and no lollipop version... it seems we can't really use the NFC for anything?

Would be interested in hearing whether Google Pay works on the stock Fire OS. If anyone gets the update, please post your experiences. Google Pay should be rolling out to Google Wallet users soon.

java007 said:
Would be interested in hearing whether Google Pay works on the stock Fire OS. If anyone gets the update, please post your experiences. Google Pay should be rolling out to Google Wallet users soon.
Click to expand...
Click to collapse
For the U.S. volunteers: Requirements for Android Pay, at least Play services 8.1.13 (or higher, ofc.)
Root users: If you get "Android Pay cannot be used" ➜ unroot ➜ activate Android Pay ➜ re-root.
Amazon's definition of NFC: No fun! Capiche!? ... I'll see myself out.

Edit: by the way I've been using it since I got the phone around May 15, nothing about "google pay rolling out" or "google wallet update needed", just downloaded it 4 months ago and been using it since..
Wait, what the hell? I don't understand what you guys want? of course the NFC chip works, like every other NFC chip elsewhere, what are you guys trying to do? It works perfect for me on 4.6.1 and 4.6.3.
I use it for google pay here and there, mostly just to brag about it or when I just want break the monotony of pulling my debit card out of my wallet, picture below... and of course it only works on places where they accept tap to pay, else I use my Google wallet card, yet again I feel like Im not a zombie with a BoA card...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Java007 was curious about Android Pay in particular, the chip works ofc. (unless you're using a custom ROM ^^).
pressingonalways is rather new to the forum I think, look at his post history, that will put things into perspective.
I use SlimKat, so no NFC for me, which is ok. We still use old coins and paper bills, like peasants.

How'd you get google pay on your device? Is this stock or custom rom? Did you sideload google app store and then just get google pay? I thought google pay required lollipop or some newer version of android than fire OS's version?
And yes, Bingo, I am certainly very new.. Thanks.
Jose-MXL said:
Edit: by the way I've been using it since I got the phone around May 15, nothing about "google pay rolling out" or "google wallet update needed", just downloaded it 4 months ago and been using it since..
Wait, what the hell? I don't understand what you guys want? of course the NFC chip works, like every other NFC chip elsewhere, what are you guys trying to do? It works perfect for me on 4.6.1 and 4.6.3.
I use it for google pay here and there, mostly just to brag about it or when I just want break the monotony of pulling my debit card out of my wallet, picture below... and of course it only works on places where they accept tap to pay, else I use my Google wallet card, yet again I feel like Im not a zombie with a BoA card...
Click to expand...
Click to collapse

pressingonalways said:
How'd you get google pay on your device? Is this stock or custom rom? Did you sideload google app store and then just get google pay? I thought google pay required lollipop or some newer version of android than fire OS's version?
Click to expand...
Click to collapse
Jose-MXL was using Google Wallet since May, since Android Pay just got released.
Since NFC is not working on CM11 / SlimKat, only Fire OS users will be able to test / use Android Pay.
Android Pay works with all NFC-enabled Android devices running 4.4+. Forcing Android L as minimum OS version wouldn't be smart at this time, just think about the market share 4.4 vs 5.x
Read my previous post about sources and requirements for Android Pay.

True, true, true, Bingo said it all...
Just sideload Google (the 4 apks) and download google wallet or google pay, whatever is available to you, go to a Panera or Walgreens and try it out.
Bingo Bronson said:
Jose-MXL was using Google Wallet since May, since Google Pay just got released.
Since NFC is not working on CM11 / SlimKat, only Fire OS users will be able to test / use Google Pay.
Google Pay works with all NFC-enabled Android devices running 4.4+. Forcing Android L as minimum OS version wouldn't be smart at this time, just think about the market share 4.4 vs 5.x
Read my previous post about sources and requirements for Google Pay.
Click to expand...
Click to collapse

cool... I didn't know Google Wallet worked for all the older phones. I was able to install google wallet with no issue... I can't install google pay because the only version of Play services that will work on my phone is 7.0.99. Can't get to the 8.x version without all the services stop working.
Sent from my TF700T using Tapatalk

Bingo Bronson said:
For the U.S. volunteers: Requirements for Google Pay, at least Play services 8.1.13 (or higher, ofc.)
Root users: If you get "Android Pay cannot be used" ➜ unroot ➜ activate Android Pay ➜ re-root.
Amazon's definition of NFC: No fun! Capiche!? ... I'll see myself out.
Click to expand...
Click to collapse
Hi BB,
thanks for your advice. However, it does not work.
"Google is unable to verify that your device or the software running on it is Android compatible"
I am running 4.6.3 stock firmware.
Any other suggestions?
thx

Thanks for confirming that Android Pay works on stock Fire OS Jose-MXL. That might be a factor to consider for those weighing the advantages/disadvantages of installing a custom ROM.

kaaskop said:
I am running 4.6.3 stock firmware. Any other suggestions?
Click to expand...
Click to collapse
I think you're the first one who tried it and actually reported back ^^.
I don't know if changing entries in the build.prop would be enough to get it working.
Some people (including me) edited the build.prop for testing purposes, but poking the Fire Phone too much won't end well:
cdudeman said:
I tried editing more lines of the build.prop and my phone didn't come back up after rebooting so I had to restore...
Click to expand...
Click to collapse
I don't know if Safestrap would be of help here, then we could create a flashable ZIP with the default build.prop, hm...

Alright guys here is my stuff:
Google Play Store 5.8.8
Google Play Services 7.8.99
Google Services Framework 4.0.4
Google Account Manager 4.0.3
I got this by installing the older version of the google apks, if I'm correct those came frome here:
http://forum.xda-developers.com/fire-phone/general/fire-phone-how-to-install-google-play-t2977237
Let the apks update for a while since they are old, that is what got me a working google pay and wallet, that is all I can do for you guys, I think the problem is you are installing a newer version of the apks and those are a headache...

Jose-MXL said:
Alright guys here is my stuff:
Google Play Store 5.8.8
Google Play Services 7.8.99
Google Services Framework 4.0.4
Google Account Manager 4.0.3
I got this by installing the older version of the google apks, if I'm correct those came frome here:
http://forum.xda-developers.com/fire-phone/general/fire-phone-how-to-install-google-play-t2977237
Let the apks update for a while since they are old, that is what got me a working google pay and wallet, that is all I can do for you guys, I think the problem is you are installing a newer version of the apks and those are a headache...
Click to expand...
Click to collapse
I think it isn't working for the majority of people because they are on fire OS 4.6.4. I have heard of several reports of users like you being able to get Google Play Services newer than 7.0.99 working on 4.6.3. I wonder what broke in between versions!
Sent from my TF700T using Tapatalk

Jose-MXL said:
Alright guys here is my stuff:
Google Play Store 5.8.8
Google Play Services 7.8.99
Google Services Framework 4.0.4
Google Account Manager 4.0.3
I got this by installing the older version of the google apks, if I'm correct those came frome here:
http://forum.xda-developers.com/fire-phone/general/fire-phone-how-to-install-google-play-t2977237
Let the apks update for a while since they are old, that is what got me a working google pay and wallet, that is all I can do for you guys, I think the problem is you are installing a newer version of the apks and those are a headache...
Click to expand...
Click to collapse
We are all talking about Android Pay, right? There is no such thing as Google Pay, that I know of.
Here is the link to get Android Pay, now. Install Google Wallet and set it up, first, before installing Android Pay.
http://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-102576552-android-apk-download/
I'm going to uninstall GApps and reinstall with those mentioned above. If I get it working, I'll try to then update to latest Services so I can get my Google Now alerts working again.

Running the latest Play Store update on 4.6.3. Android Pay displays "Google is unable to verify that your device or the software running on it is Android compatible". I also ran SafetyNet Helper and get "CTS profile match: false".

Perez92 said:
Running the latest Play Store update on 4.6.3. Android Pay displays "Google is unable to verify that your device or the software running on it is Android compatible". I also ran SafetyNet Helper and get "CTS profile match: false".
Click to expand...
Click to collapse
I'm seeing the same thing. Too bad it goes all the way through setting up payment first...
For reference:
Fire OS 4.6.3, GSM Unlocked
Google Play Services 8.1.15
Google Services Framework 4.4.4
Google Account Manager 4.0.3
Android Pay 1.0.103131485

jwernerny said:
I'm seeing the same thing. Too bad it goes all the way through setting up payment first...
For reference:
Fire OS 4.6.3, GSM Unlocked
Google Play Services 8.1.15
Google Services Framework 4.4.4
Google Account Manager 4.0.3
Android Pay 1.0.103131485
Click to expand...
Click to collapse
Maybe I just realized why my NFC pay is working and everyone else isn't, my applications are not updated so I don't have 2 separate apps for Google Wallet and Android Pay, I just have wallet installed and there is where I go to do NFC payments, it's a single app, not 2 separate ones.

Jose-MXL said:
Maybe I just realized why my NFC pay is working and everyone else isn't, my applications are not updated so I don't have 2 separate apps for Google Wallet and Android Pay, I just have wallet installed and there is where I go to do NFC payments, it's a single app, not 2 separate ones.
Click to expand...
Click to collapse
Yes. There are three apps. Google Wallet (Old), which combines the money transfer and tap-and-pay options. Now, these features are separated into two apps Google Wallet (New), which has money transfer but no tap-and-pay, and Android Pay, which is now the tap-and-pay.
I can confirm that two days ago, my Google Wallet (Old) worked to pay at a register. But, now Google has completed the roll out of Android Pay and my Google Wallet (Old) tap-to-pay directs me to install Android Pay. Can you confirm your Google Wallet (old) tap-to-pay is working today?

ClevelandESQ said:
Yes. There are three apps. Google Wallet (Old), which combines the money transfer and tap-and-pay options. Now, these features are separated into two apps Google Wallet (New), which has money transfer but no tap-and-pay, and Android Pay, which is now the tap-and-pay.
I can confirm that two days ago, my Google Wallet (Old) worked to pay at a register. But, now Google has completed the roll out of Android Pay and my Google Wallet (Old) tap-to-pay directs me to install Android Pay. Can you confirm your Google Wallet (old) tap-to-pay is working today?
Click to expand...
Click to collapse
hmmmmmmm if you wait me to go to a Panera tomorrow?

[Q] How to disable Samsung OTA?

If you'd like to disable Samsung OTAs on your Verizon Note 7, you need Package Disabler Pro version 6.4 or earlier.
You can download version 6.3 from this link: https://onedrive.live.com/?authkey=!AIfDkz0V-XIn4XE&id=E344C7F7F1FE86C3!1923&cid=E344C7F7F1FE86C3
But, you must first purchase the license from the Play Store.
Once you have version 6.4 or earlier up and runnng, disable the following packages.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot creds: dasdman
ENJOY your illegal Note 7! XD

Maybe system updates SDM? Not sure though.

Spike96 said:
I'm keeping my Note 7, at least until Samsung conducts its full investigation. There's simply no other phone that is this good.
So how do I disable Samsung from messing with my battery life?
I just installed Package Disabler Pro, and have disabled only one package so far:
Anything else that needs to be disabled?
Much thanks.
Click to expand...
Click to collapse
What happens after they complete their investigation?
Sent from my HTC6545LVW using Tapatalk

dottat said:
What happens after they complete their investigation?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Not really the point of this thread, but obviously the more information Samsung can find out about these fires, the more information we as consumers have to make a good decision on how to proceed. The Samsung engineers have been unable to replicate these fires in the labs so far, and if you ask me, that's a good sign in telling how low of a chance these phones have of actually catching fire.
Samsung will keep investigating until it has found the root cause. When it does, this thing busts wide open. We'll know exactly how safe the Galaxy Note 7 really is, and a relaunch is even possible.
BUT, I don't want to get into a whole thing about what Samsung may or may not find in it's investigation on this thread. This thread is solely about disabling Samsung OTAs so keeping the phone in a working condition and with max battery life is possible.

The two system updates need to be froze.

Spiteful Monkey said:
The two system updates need to be froze.
Click to expand...
Click to collapse
Thank you. Just disabled both of them. Hopefully that's it
Sent from my SM-N930V using Tapatalk

le0.br4zuc4 said:
Thank you. Just disabled both of them. Hopefully that's it
Click to expand...
Click to collapse
Don't forget policy updates as well

Rootuser3.0 said:
Don't forget policy updates as well
Click to expand...
Click to collapse
Thanks
Sent from my SM-N930V using Tapatalk

I think it is just the two system updates. That is all I ever disabled and I never got an OTA pushed to me. In fact when I go to settings to see if there is an update available, settings force closes. Unless they try to force an update via another way those two should be the only ones needing disabling.

Disable all these...

dasdman said:
Disable all these...
Click to expand...
Click to collapse
I'm going to use your screenshot to update the OP if that's OK.

dasdman said:
Disable all these...
Click to expand...
Click to collapse
Yes this is what I did as well thanks

Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!

flanky79 said:
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
Click to expand...
Click to collapse
Don't you worry about using Gear VR. Its "fixed" by Oclulus. As soon as you'll connect it with VR, it will force you to update. And when you do, your Note 7 will be useless for Gear VR. I recommend freezing anything that says VR in package disabler, except for Gear VR service and see.
BTW, I am in search for apks associated with Gear VR. Specifically, Oculus home, Oculus Appmanager , Oculus system activities and most importantly, Oculus VR drivers. I was never able to use Gear VR because my phone arrived after the Oculus ban. Therefore, I couldn't driver anything from Oculus and I don't have the VR drivers and I can't find them. on internet I know i can't use Oculus for my VR needs, but if I have the drivers, I would like to use the Buttons and Touchpad for 3rd party VR apps such as Cardboard.
If you're able to upload those OLD (read non toxic) APKs I mentioned, it will be greatly appreciated...

Bump.
Apparently, if you've already downloaded the OTA, you can still stop it from being installed by disabling the four packages in the OP.
Unfortunately, if you've installed the OTA... it might be a lost cause.

flanky79 said:
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Pls help... Thanks!
Click to expand...
Click to collapse
Someone please answer this guy because I'm exactly the same. I blocked those two but the notification for the update is still there. If I force close "system updates" all then it goes away for a second... But comes right back.
I just spent a lot of money ordering a new screen as my first recall phone seemed to crack about 3 times very easily. But replaced it myself and it is just like new. Just need to freeze and block any updates until a phone comes out that is acceptable on Verizon.
I'll also note that the internal battery of this phone has a date on it that is pre-first-recall. I suspect Samsung never actually changed the battery of these phones and simply updated it with a green battery icon.
Please assist.

Bump.
Ummmm, well, I'm a newb again apparently... I haven't rooted a phone since my SGS3, and thought it couldn't be too hard...
Yeah, I should have done more reading...
I'm pretty sure I bricked it... Can't access Verizon software repair tool either, as it has apparently been shut down since yesterday.
If anyone has any advice on how I can repair this, even if I have to do the new downdate...
Please help!
I'll check back tomorrow after my EGR Thermo exam...

JAWyered said:
Someone please answer this guy because I'm exactly the same. I blocked those two but the notification for the update is still there. If I force close "system updates" all then it goes away for a second... But comes right back.
I just spent a lot of money ordering a new screen as my first recall phone seemed to crack about 3 times very easily. But replaced it myself and it is just like new. Just need to freeze and block any updates until a phone comes out that is acceptable on Verizon.
I'll also note that the internal battery of this phone has a date on it that is pre-first-recall. I suspect Samsung never actually changed the battery of these phones and simply updated it with a green battery icon.
Please assist.
Click to expand...
Click to collapse
You have to find a older version of package disabler version 6.3 should have additional options you can check to disable. If the update is already downloaded you can get rid of the update notification for at least for 24hrs by doing long pressing the notification and un check everything then a combination of force stop then clearing cache and selecting manage storage.
Sent from my SM-N930V using XDA-Developers mobile app

?????
i did not see
com.sec.android.soagent or
com.samsung.sdm
only seen
com.policydm and com.samsung.sdm.sdmviewe
i bought both package disabler pro's n still couldnt find com.sec.android.soagent or com.samsung.sdm, my system update is ready to install and im wondering how to get rid of the notification or update all together

It's rather easy to fix this. Most of you have purchased a disabler app, either package disabler pro or ez disabler from the Play store, therefore you have a valid license but downloaded the gimped recently updated version from the play store. Search Google or xda to find a safe apk of the previous release of the disabler apk. Uninstall version downloaded from the play store and install old version (turn off auto updates in Play store before installing apk). Voila, you have a non-gimped disabler app and are now able to see those missing packages.

Shield Experience Upgrade 6.3

The wait begins for the developer image

OK, please don't kill me since I'm new to this.
I just got a Shield and rooted it. How do I upgrade to 6.3 without bricking it or losing my data?

i would say to wait for the developer images to be available before upgrading.

DanteXXL said:
OK, please don't kill me since I'm new to this.
I just got a Shield and rooted it. How do I upgrade to 6.3 without bricking it or losing my data?
Click to expand...
Click to collapse
yes wait for the developer image that way you can just flash it over current build without data loss

Well, installed the update on my unrooted Shield , showing in the changelog that finally Tidal can stream music in hi-fi res. Nevertheless nothing has changed, in the Tidal app (Android Tv, obtained from the Play Store and registered with my payied account ) in the settings it shows Hi-fi quality, but I get Pcm 48kbps, 2 channel music. Nothing more.
At the contrary in my Marantz Avr, the same service active through the Heos App, gives me 320kbps AAC 2channels, at least.
What is the reason for this? Is there a setting I should adapt, to have the same quality as in my Avr on the Shield?
Thanks for your interest
Alessandro

jionny said:
yes wait for the developer image that way you can just flash it over current build without data loss
Click to expand...
Click to collapse
And how do I flash the dev image once it is out? ?

DanteXXL said:
And how do I flash the dev image once it is out?
Click to expand...
Click to collapse
flashfire

vn800art said:
Well, installed the update on my unrooted Shield , showing in the changelog that finally Tidal can stream music in hi-fi res. Nevertheless nothing has changed, in the Tidal app (Android Tv, obtained from the Play Store and registered with my payied account ) in the settings it shows Hi-fi quality, but I get Pcm 48kbps, 2 channel music. Nothing more.
At the contrary in my Marantz Avr, the same service active through the Heos App, gives me 320kbps AAC 2channels, at least.
What is the reason for this? Is there a setting I should adapt, to have the same quality as in my Avr on the Shield?
Thanks for your interest
Alessandro
Click to expand...
Click to collapse
I am curious to know if there was any performance hits from the Meltdown and Spectre exploit mitigation outlined in 6.3.

F3NDER said:
I am curious to know if there was any performance hits from the Meltdown and Spectre exploit mitigation outlined in 6.3.
Click to expand...
Click to collapse
There is no need for a "Meltdown" fix, just "Spectre" has been fixed.
New Features and Apps to Try on SHIELD
-PLEX: Automatically remove DVR recorded shows
-VLC: Adds 360 video and PIP functionality
-New Apps: Sirius XM, Tidal
[US Only]
-NEST: View your Nest Cameras on SHIELD using Google Assistant. Say “Show me my front door camera”
-Smart Home: Control over 1000 devices with Google Assistant
-New Apps: Cartoon Network, VH1, and Lego TV
[EU]
-New Apps: Eurosport
[Germany Only]
-New Apps: TV NOW PLUS
[Spain Only]
-New Apps: Moviestar+
Additional Enhancements
• The latest monthly Android security updates including mitigations for “Spectre” (not known to be vulnerable to “Meltdown”). See NVIDIA Product Security Page for more details:
• Improves reporting for low battery status for SHIELD Accessories
• Adds new USB compatibility mode for users with attached USB storage/accessories to improve Bluetooth/wireless performance (Settings > System).
• Support for playback of YUV 8 bit BT 2020 videos
• Adds developer option for rooted systems to always prefer full system upgrades - recommend for rooted systems
• SHIELD controller (2017) upgrade to version 1.18
• SHIELD remote (2017) upgrade to version 1.28
• SHIELD remote w/ headphone jack upgrade to version 1.22
- Firmware update for SHIELD remote (rechargeable) to resolve recharging issues. If update fails, connect remote to charging cable and hold Home + Back + Voice Search buttons until LED flashes (~20 seconds)
• Latest accessory firmware versions:
-SHIELD controller (2017): v1.18
-SHIELD controller (2015): v1.96/99/3.71/0.32
-SHIELD remote (2017): v1.28
-SHIELD remote (rechargeable): v.1.22
http://support-shield.nvidia.com/android-tv-release-notes/6.3/
Click to expand...
Click to collapse
Source
According to this 2 Users answered:
Absolutely nobody cares about this, and you're not wrong. But. The hit comes from having to disable some forms of branch prediction / speculative execution when context switching between user and supervisor modes of the processor. This manifests as "around disk and network I/O" but other compute workloads could also be slowed depending on the amount of context switching.
Streaming media really doesn't cause many context switches so that's most likely safe (there could be another process running that could cause slowdowns.)
You can benchmark your context switches with a bunch of different tools. I'm a Linux guy and I don't have any windows boxes at hand so I'm not sure what you'd use there, but I'm sure there's something. Once you have a benchmark you can probably determine the likelihood of having problems with your given workload.
Click to expand...
Click to collapse
Source
The performance hit comes from Meltdown, not Spectre.
Most ARM-based chips are not vulnerable to Meltdown with the only exception seemingly being Apples ARM designs, as well as potentially the unreleased Snapdragon 845 and Samsung's new Exynos.
So if Nvidia's fix is exactly that from the January security bulletin then there's essentially no performance hit.
Spectre is a pretty bad exploit though because essentially the exploit can't be easily fixed so it's mostly just reducing the potential for exploits. Further mitigations may be necessary in the future both in hardware and software.
Click to expand...
Click to collapse
Source
So it seems there shouldn't be any noticeable performance issues. But didn't update myself yet.

jionny said:
The wait begins for the developer image
Click to expand...
Click to collapse
Here we go again...
It seems to be the last time because this new firmware implement an option for rooted (dev) firmware to perform a FULL upgrade from now on via OTA.

sammarbella said:
Here we go again...
It seems to be the last time because this new firmware implement an option for rooted (dev) firmware to perform a FULL upgrade from now on via OTA.
Click to expand...
Click to collapse
and keep all settings? that would be great

jionny said:
and keep all settings? that would be great
Click to expand...
Click to collapse
It should but IDK we will see...:
• Adds developer option for rooted systems to always prefer full system upgrades - recommend for rooted systems
Click to expand...
Click to collapse
https://forums.geforce.com/default/...-tv-released-1-31-2018-/post/5283150/#5283150

How long is the wait usually for the dev images to appear?

ghostyroasty said:
How long is the wait usually for the dev images to appear?
Click to expand...
Click to collapse
Depends on Nvidia if I remember right 6,2 was post in like 3-5 days but 6.1 took 2-3 weeks

Interestingly, updating my non-rooted 16GB Shield to 6.3 resulted in a weird bug.
Now if I use Gamestream, my second xbox 360 controller is no longer recognised as a controller, instead it's recognised as a keyboard and mouse.
This is when using multiple 360 controllers via the wireless dongle.

If I downgrade/flash the 6.2 developer image, will it update to the 6.3 dev image, or will it be the consumer version?

sammarbella said:
Here we go again...
It seems to be the last time because this new firmware implement an option for rooted (dev) firmware to perform a FULL upgrade from now on via OTA.
Click to expand...
Click to collapse
I can confirm that I guinea pigged the 6.3 update from a rooted 2017 Darcy expecting it to fail. To my surprise, it validated and installed without a problem. Lost root but you only have to temp boot into TWRP to flash SuperSU or Magisk and you're back in business. Hope this helps people.

Rooted 16gb 2017.
Inadvertently clicked to apply the 6.3 update.
update installed and rebooted.
Now on 6.3, lost root.
I thought that the OTA would not install on a rooted device ??

markdb77 said:
Rooted 16gb 2017.
Inadvertently clicked to apply the 6.3 update.
update installed and rebooted.
Now on 6.3, lost root.
I thought that the OTA would not install on a rooted device ??
Click to expand...
Click to collapse
read post 11&12

jionny said:
read post 11&12
Click to expand...
Click to collapse
Perhaps I'm reading post 11&12 incorrectly but I wasn't running a developer image of 6.2 when I updated to 6.3. It did however, download and install a full system image due to the size being over a gigabyte. There is now an option in developer options entitled "provide full system upgrades" (always install full system images instead of incremental images). That option really has nothing to do with rooted devices specifically but perhaps that's how this was possible. Anyhow, glad it worked. Lost root but that was easily flashed back and it was a simpler method of updating rather than flashing the factory image then flashing root.

Question Issues Keeping Background Apps Running

Anyone else having issues with keeping apps running in the background? I have a couple apps (one for doorbell camera and one for outdoor security cameras) that will only stay active for a short time and provide notifications on my phone when motion was detected. I can open one of the apps after not getting any notifications for a long period and then I will get all the notifications that never came through.
I have done all the normal steps of making sure the battery optimization was turned off for these apps and turning off all data restrictions with no luck. I had several go around with TCL support and exhausted their possible solutions. The same doorbell app worked fine on my old Pixel so I am pretty sure it isn't the apps.
Any help is appreciated. Thanks.

Hammer4000 said:
Anyone else having issues with keeping apps running in the background? I have a couple apps (one for doorbell camera and one for outdoor security cameras) that will only stay active for a short time and provide notifications on my phone when motion was detected. I can open one of the apps after not getting any notifications for a long period and then I will get all the notifications that never came through.
I have done all the normal steps of making sure the battery optimization was turned off for these apps and turning off all data restrictions with no luck. I had several go around with TCL support and exhausted their possible solutions. The same doorbell app worked fine on my old Pixel so I am pretty sure it isn't the apps.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Same me.
I ve solved flashed android 12 beta

play4win said:
Same me.
I ve solved flashed android 12 beta
Click to expand...
Click to collapse
I wondered about that. Have you experienced any major issues with the Android 12 beta? I may have to give that a try. Thanks!

Hammer4000 said:
I wondered about that. Have you experienced any major issues with the Android 12 beta? I may have to give that a try. Thanks!
Click to expand...
Click to collapse
I tried the beta 3, but my phone was not listed with the CU regulatory Number, whatever that is. I cant go back to 11 and I dont know if ill be able to go forward. But it did solve the notification issues.

Welcome to XDA
Power management destroyer of worlds
Developer options>standby apps
All buckets should show as active otherwise power management is enabled!
You can't change that setting here. If you can change a bucket state and get it to take (close Developer options/reopen) then again power management has been enabled.

Jamesblondca said:
I tried the beta 3, but my phone was not listed with the CU regulatory Number, whatever that is. I cant go back to 11 and I dont know if ill be able to go forward. But it did solve the notification issues.
Click to expand...
Click to collapse
Mine was Listed in CU, but actually i can t go back to android 11

play4win said:
Mine was Listed in CU, but actually i can t go back to android 11
Click to expand...
Click to collapse
Hopefully we can go forward eventually.

Mobile upgrade
www.tcl.com

Hammer4000 said:
Anyone else having issues with keeping apps running in the background? I have a couple apps (one for doorbell camera and one for outdoor security cameras) that will only stay active for a short time and provide notifications on my phone when motion was detected. I can open one of the apps after not getting any notifications for a long period and then I will get all the notifications that never came through.
I have done all the normal steps of making sure the battery optimization was turned off for these apps and turning off all data restrictions with no luck. I had several go around with TCL support and exhausted their possible solutions. The same doorbell app worked fine on my old Pixel so I am pretty sure it isn't the apps.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
One method I think is working without upgrading to Android 12 is to disable the "Smart Manager" app via adb
You can download sdk platform-tools and run command
adb shell
pm disable-user com.tct.onetouchbooster
You do lose out on accessing some battery options, though, since it's integrated into the app, but I don't mind it. Hope it helps

I have an unlocked T810S that I'm using here in the USA with Cricket Wireless (an AT&T MVNO). My phone has Android 11, and the notification issues are driving me crazy. I don't yet see any updates for Android 12, so who knows when I can get that.
I saw what @rickywangca did, and did something similar. From my Linux box:
Code:
adb shell
pm uninstall -k --user 0 com.tct.onetouchbooster
And that uninstalled the "Smart Manager" application. I'm happy to have that thing gone, but I still have notification issues that I can't figure out.
For the apps in question, I added them to do "do not optimize" battery list, but that didn't seem to help. One app is configured to give me a daily notification, but I almost never receive it. I actually got the notification one day and was surprised.
Any other tips or ideas on dealing with the notification issue? Do I need to clear something else out related to the onetouchbooster "Smart Manager"?

jrevans said:
I have an unlocked T810S that I'm using here in the USA with Cricket Wireless (an AT&T MVNO). My phone has Android 11, and the notification issues are driving me crazy. I don't yet see any updates for Android 12, so who knows when I can get that.
I saw what @rickywangca did, and did something similar. From my Linux box:
Code:
adb shell
pm uninstall -k --user 0 com.tct.onetouchbooster
And that uninstalled the "Smart Manager" application. I'm happy to have that thing gone, but I still have notification issues that I can't figure out.
For the apps in question, I added them to do "do not optimize" battery list, but that didn't seem to help. One app is configured to give me a daily notification, but I almost never receive it. I actually got the notification one day and was surprised.
Any other tips or ideas on dealing with the notification issue? Do I need to clear something else out related to the onetouchbooster "Smart Manager"?
Click to expand...
Click to collapse
Is global power management active?
Developer options>standby apps, all buckets should show as active otherwise global power management is active. It will cause erratic behaviors. It's not needed or desirable, it never did work well. It can not be disable here though.
Example: how its controls appear on a Samsung N10+ in Device Care, battery, it's usually a little buried but it's there. You'll find something similar to this. It's part of the core Android system.
These settings will cause trouble...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jamesblondca said:
I tried the beta 3, but my phone was not listed with the CU regulatory Number, whatever that is. I cant go back to 11 and I dont know if ill be able to go forward. But it did solve the notification issues.
Click to expand...
Click to collapse
play4win said:
Mine was Listed in CU, but actually i can t go back to android 11
Click to expand...
Click to collapse
hi Jamesblondca, play4win,
-did you upgrade to beta 12 using tpst frame tool explained in this forum?
-what was your phone model t810h or t810s
-what is your opinion about andoid 12 beta, like battery drain, any unexpected issues, faulty features etc.

blackhawk said:
Is global power management active?
Developer options>standby apps, all buckets should show as active otherwise global power management is active. It will cause erratic behaviors. It's not needed or desirable, it never did work well. It can not be disable here though.
Example: how its controls appear on a Samsung N10+ in Device Care, battery, it's usually a little buried but it's there. You'll find something similar to this. It's part of the core Android system.
These settings will cause trouble...
View attachment 5705721
Click to expand...
Click to collapse
This T810S TCL 20 Pro 5G is an awesome phone, but the lack of notifications drives me crazy.
I looked at my Developer Options, trying to see something similar to what you have on that Samsung, and I see these, which appear to be inactive.
"Adaptive notification priority"
"Adaptive notification ranking"
But when I go to my Inactive Apps list, I see a variety of different "App standby state" values. It appears that I can change some of them here to have the different values of:
"ACTIVE", "WORKING_SET", "FREQUENT", "RARE", "RESTRICTED".
Which value should I choose if I want the app to stay active and send me notifications?
Here's a screen grab of what I see:
Oh how badly I just want to receive notifications from my applications, to make my phone fully functional. I get notifications from certain apps like gmail, telegram and facebook, but not from apps that I want like the LG ThinQ app, and Lightning Pro.

jrevans said:
This T810S TCL 20 Pro 5G is an awesome phone, but the lack of notifications drives me crazy.
I looked at my Developer Options, trying to see something similar to what you have on that Samsung, and I see these, which appear to be inactive.
"Adaptive notification priority"
"Adaptive notification ranking"
View attachment 5849973
But when I go to my Inactive Apps list, I see a variety of different "App standby state" values. It appears that I can change some of them here to have the different values of:
"ACTIVE", "WORKING_SET", "FREQUENT", "RARE", "RESTRICTED".
Which value should I choose if I want the app to stay active and send me notifications?
Here's a screen grab of what I see:
View attachment 5849991
Oh how badly I just want to receive notifications from my applications, to make my phone fully functional. I get notifications from certain apps like gmail, telegram and facebook, but not from apps that I want like the LG ThinQ app, and Lightning Pro.
Click to expand...
Click to collapse
In general...
Power management with the bucket states and all of that is a native Android service. Part of battery management. You can't disable in Developer options but you can tell if it's active there. You can use it to verify that you have disabled though.
Samsung modifies their UI heavily. The settings they use may be similar to other brands, Pixels being the "purest" version of Android. In Pixels the controls for that are in battery care in settings, I think (I never owned a Pixel). Terms like Adaptive battery or Battery saver may be the ones thst switch it on/off. Verity it then with the Standby Apps status.
There is a way to set exceptions to Adaptive battery and that may work too. I never used it or if I did it failed to work properly in one way or another... it's been years. I ended up turning the whole mess off and using other methods to increase my SOT.
The best way to learn how your Android works is to play with it. Go through all the settings and play with them when you have time. Like a game, it's sort of fun. Do Google searches for specific issues; it doesn't have to be that specific model or even brand. Androids are similar across Android flavors and OS versions to a greater or lesser extent. Learn by reading about them. That's all I do and eventually track down the issue. The more you do this, the better and faster you get at it. Find/get the tools you need to better understand what's happening like a logging firewall, battery trackers etc.
I see you have social media and sales apps installed. I never do this. If I need to access them I login to them through Brave browser only.
They tend to consume excessive battery and are multi vector security threats*. They can also cause problems by changing hidden user settings which could have global consequences. You are what you load. At the very least not having any trashware makes troubleshooting easier and yields a better running Android. Disabling the questionable app when not in use is another option I sometimes use if I really need it.
*Just because it's on Playstore doesn't mean it's safe. Any app that updates outside of Playstore could download a trojan payload to what appeared to be a safe app. Any app that has internet access is a potential security threat. I firewall block all that don't absolutely need it and don't update any unless there's a good reason to.

General Switching from OxygenOS C.38 (EU) to ColorOS C.41 (CN), and back to OOS12 (EU C.44) 😂

As some of you might have noticed, the update for Chinese ColorOS 12 numbered C.41 has been released for OnePlus 9 and 9 Pro (link to Techibee's article with the DL links). While I was pretty patient about waiting for an official OxygenOS 12 update for EU users (don't know to what amount of time it would have led to wait for), the complains about how halfly-baked the last OOS updates were and the fact that we can switch from one release to another without a lot of issues convinced me to give a try to the fully assumed ColorOS 12 for my OnePlus 9 Pro.
As far as I can tell, the update proceeded without any unwanted side effects, even if, as it's a Chinese version, it came with a lot of apps that I will surely never need or use. I didn't loose any datas in the process and after the quick setup of ColorOS (it is still detected as a new OS by the phone, and it will act like a nearly brand new one at the first boot following the update, even if everything is back in place after ignoring those steps).
For the differences I noticed:​
Changes that are a little bothering (to me):
A lot of Chinese bloatwares (some cannot be uninstalled, HeyTap's App Market and Themes Market, even through ADB, because they are tide to some ColorOS required functions)
A whole new HeyTap environment that I will have to get accustomed to, but I think that I'll stick with Google for now
Breeno, the voice assistant (not very fond of voice assistants, so not going to use it)
Omojis (still to be tested, as I'm unable to register myself yet, but it reminds me a lot about Apple's Memoji feature)
Very aggressive battery management (some apps, even if allowed to run in the back, are force-closed by ColorOS, I still have to find a way to correct or lessen that behavior)
Click to expand...
Click to collapse
What I liked so far:
Easy transition so far, the phone feels the same in term of performances
RAM booster (from 3 to 7Gb can be used from your phone memory to help your phone managing bigger apps)
The game panel, that is giving quite a bunch of options for people playing a lot on their phone (I'm not really used to play heavy games on my phone, but still delighted that it's given to the users)
FaceID unlock working great (I'm still waiting for it on my girlfriend's Pixel 6...)
Being able to install back the debloated apps (yes, still bloatwares, but it is an interesting option and could help correcting some users errors)
Highly customizable UI from the start (I'm a Nova Launcher/Kustom user, but I still gave a try to the stock UI and it was pretty good)
Wireless charging a little more efficient ( personal feeling here, might just be my imagination or the aggressive battery management at work, and it requires some further testing)
Click to expand...
Click to collapse
In conclusion, I would say that I'm still looking for the perfect OS experience with my OnePlus 9 Pro, but when it comes to Android 12 official ROMs, ColorOS 12 gave me the best experience so far. I'm still experimenting it as my daily driver, so I might come across new elements (either good or bad), but I hope that it will reassure a little people that are hesitating doing the transition between the two OS.
Edit:
Found the reason why accessibility was automatically disabled for one of my apps, ColorOS isn't allowing you to lock for background run more than just a few selected apps and will prevent you to add more if you don't deactivate some of the old ones beforehand.
Edit 2:​
Spoiler: Debloated apps
com.heytap.music​
com.heytap.vip​
com.heytap.browser​
com.finshell.wallet​
com.heytap.speechassist​
com.coloros.directui​
com.coloros.calendar​
com.heytap.cloud​
com.oplus.synergy​
com.oplus.pay​
com.colorsos.gallery3d​
com.coloros.ocrscanner​
com.coloros.weather.service​
com.android.mms​
com.android.contacts​
com.coloros.filemanager​
com.redteamobile.roaming​
Edit 3:
Update to C.44 installing. Seems to fix a black screen issue for incoming calls.
Edit 4:
From new observations I was able to make since I installed ColorOS 12, the way it handles authorizations is a little different from OxygenOS. The number of apps alowed to run in the background is very limited (7) and most apps will need a manual authorizations setup to work properly.
Edit 5:
Throttling detected in some game apps, locked at 30fps... Quite strange for an OS that is providing "pro gaming in-game panel".
Edit 6:
Back to OxygenOS 12, but EU C.44 as they finally released it ().
The few days on ColorOS 12 were nice, but I ended up being frustrated by how the OS is actually fine-tuned in term of GPU and CPU performances in some apps.
I hope OPPO and OnePlus will successfully find a way to balance things and that an EU (or at least a not too heavy chinese services relied) version will be really released in the coming months, because it's promising and offers many features that I still enjoyed.

How to remove or uninstall or disable or hide app market coloros 12 ?

brmbjn said:
How to remove or uninstall or disable or hide app market coloros 12 ?
Click to expand...
Click to collapse
Replied here: https://forum.xda-developers.com/t/...d-12-on-oneplus-9-9-pro.4367117/post-86282121

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Does android auto work by chance?

lukehong9 said:
Does android auto work by chance?
Click to expand...
Click to collapse
I don't have the chance to have a car that supports it, so I cannot tell if it is.

Just dirty flashed over OOS C 38?

30adi said:
Just dirty flashed over OOS C 38?
Click to expand...
Click to collapse
As said, I did a local update from the Local Update app provided since the Android 12 update.

Is autofill working?

rogerinnyc said:
Is autofill working?
Click to expand...
Click to collapse
Could you elaborate your question?
If you're taking about the word prediction used on keyboards, then yes, it works.

Sorry not to be clear. I mean Chrome autofill in apps and your browser, where your login and password are entered automatically.

30adi said:
Just dirty flashed over OOS C 38?
Click to expand...
Click to collapse
i am dirty from oos c.40 to cos c.41 and then get ota cos c.44
work well

rogerinnyc said:
Is autofill working?
Click to expand...
Click to collapse
Looks like you have the same issue.？

rogerinnyc said:
Sorry not to be clear. I mean Chrome autofill in apps and your browser, where your login and password are entered automatically.
Click to expand...
Click to collapse
ColorOS use its own solution for that, but you can use Google's and it works quite well so far.

Any method of installing the Google play store and play services?

fernoct said:
Any method of installing the Google play store and play services?
Click to expand...
Click to collapse
It comes with it, so no need to proceed to a manual install.

Jaxom84 said:
It comes with it, so no need to proceed to a manual install.
Click to expand...
Click to collapse
Then may be I have installed a wrong version as instructed in a Youtube video. No play services was there and there were many Chinese apps and letters (I have selected English US). Do you have the link to the latest ColorOS with play services?

fernoct said:
Then may be I have installed a wrong version as instructed in a Youtube video. No play services was there and there were many Chinese apps and letters (I have selected English US). Do you have the link to the latest ColorOS with play services?
Click to expand...
Click to collapse
Take a look at the link in my first post, I know they also hosted the C.44.

Jaxom84 said:
Take a look at the link in my first post, I know they also hosted the C.44.
Click to expand...
Click to collapse
Yes, I got it, thanks. I have done a factory reset after installing it in the morning and may be that's the reason there weren't any Google play services. I'm confused..

fernoct said:
Yes, I got it, thanks. I have done a factory reset after installing it in the morning and may be that's the reason there weren't any Google play services. I'm confused..
Click to expand...
Click to collapse
It must explain why, you're right. As I update from a Google based version (A12 C.38 EU), it was already in my phone and didn't have to perform a factory reset.