Develop Bugs

NFC turn on/off app

Hi
i couldn't find any app to turn off / on NFC
like this app for airplane mode;
Airplane Mode
can u recommend an app for this?
thanks

x102x96x said:
Hi
i couldn't find any app to turn off / on NFC
like this app for airplane mode;
Airplane Mode
can u recommend an app for this?
thanks
Click to expand...
Click to collapse
The reason you don't see these is that the Android team moved the NFC enable/disable setting into the secure settings in 2.3.5. Prior to then there were a few NFC toggle widgets on the market. Now those apps would need WRITE_SECURE_SETTINGS (so you're looking at only devices with root access willing to make your app a system app or JB+ devices where you can request it from the package manager with root access).

krohnjw said:
The reason you don't see these is that the Android team moved the NFC enable/disable setting into the secure settings in 2.3.5. Prior to then there were a few NFC toggle widgets on the market. Now those apps would need WRITE_SECURE_SETTINGS (so you're looking at only devices with root access willing to make your app a system app or JB+ devices where you can request it from the package manager with root access).
Click to expand...
Click to collapse
so wht s ur solution for auto turn on NFC?! (except force keep on in "nfc task launcher" app)

x102x96x said:
so wht s ur solution for auto turn on NFC?! (except force keep on in "nfc task launcher" app)
Click to expand...
Click to collapse
I don't think that there's a solution for automatic NFC turm om. What is more, it's not really safe.

x102x96x said:
so wht s ur solution for auto turn on NFC?! (except force keep on in "nfc task launcher" app)
Click to expand...
Click to collapse
I don't auto-turn on NFC. You can create an app that does this if you just have it request WRITE_SECURE_SETTINGS and then either use root to grant that permission via the package manager or copy/move it to /system/app

krohnjw said:
I don't auto-turn on NFC. You can create an app that does this if you just have it request WRITE_SECURE_SETTINGS and then either use root to grant that permission via the package manager or copy/move it to /system/app
Click to expand...
Click to collapse
one more question;
What will happen exactly when select keep on NFC on "NFC Task Launcher" ?
it needs root access Or what happen after asking to reboot phone?
thanks

x102x96x said:
Hi
i couldn't find any app to turn off / on NFC
like this app for airplane mode;
can u recommend an app for this?
thanks
Click to expand...
Click to collapse
System settings --> more --> nfc [check/uncheck]
Or..
system settings --> system --> quick settings panel --> tiles and layout --> add --> nfc, then its on your quick settings panel.

I too would like to see a way of turning the NFC on and off without the manual prompt - like you can with bluetooth.
It appears that you cant do this because its "unsafe" and because of this reason they've also made NFC not work while the screen is off although some crafty people have realized this kind of defeats the purpose of having NFC and for some phones they've enabled NFC to work with lock screen closed (see link)
http://www.xda-developers.com/android/activate-nfc-at-any-time/
I can kind of see how its unsafe to be able to turn it on without acknowledgement - but if you could setup a rule that required Root access then this should be a reasonable stop gap? You would then be able to setup a rule in say "automateit" for example so that the NFC turns on and off during certain times or after certain rules are activated or stopped - this would then kind of make safe because you can turn the NFC off and know for sure its off after certain events have occurred.
I know this is a very debatable subject but I think its a good subject to debate.

I use shortcutter app from play store. Although you have to grant the relevant permission via adb.

Permission problem- Can't tap allow

I have got this weird problem with the Nexus 5x. When I install a new app it asks for permissions and I can't tap allow but I can tap deny. It is not a problem with the touch since I have tried in landscape and portrait mode. Everytime I have to manually go to settings and allow permission(from settings) for each app I install. I'm running marshmallow with June security patch. Very irritating. Any fix?

For me (Nexus 5) it started right after I installed android 6.0 June patch. For the moment can't find any workarounds only manually opening app settings and allowing permission

jassim007 said:
I have got this weird problem with the Nexus 5x. When I install a new app it asks for permissions and I can't tap allow but I can tap deny. It is not a problem with the touch since I have tried in landscape and portrait mode. Everytime I have to manually go to settings and allow permission(from settings) for each app I install. I'm running marshmallow with June security patch. Very irritating. Any fix?
Click to expand...
Click to collapse
do you use any app that works via overlays? for example an app that dyes your screen in the evening/at night?
such an app, to my knowledge, would trigger a security feature of android that would prevent the user from accepting, say, installation confirmation.

Broken303 said:
do you use any app that works via overlays? for example an app that dyes your screen in the evening/at night?
such an app, to my knowledge, would trigger a security feature of android that would prevent the user from accepting, say, installation confirmation.
Click to expand...
Click to collapse
Nope. I haven't used any app like that on this devwce till now. (Eg.screen filter)
EDIT: Thanks for your keyword (screen overlay)!. It is a problem called 'screen overlay' which is a common issue in marshmallow. These links gave me the solution.
https://www.youtube.com/watch?v=EBhcuP1xwrs
https://www.youtube.com/watch?v=S0S1znycHFM

I am having this same problem since latest update, its really annoying i can hit deny but not allow! How do we fix this crap! My stock phone isnt working right whats up with that?

Other kinds of overlay can be the "chat bubbles" from Facebook Messenger or Flynx tabs.
---------- Post added at 04:11 AM ---------- Previous post was at 03:43 AM ----------
Just checked the Google Nexus forum and they say that there's an app called "File Manager" from Cheetah Mobile that it's causing this issue. Check if this is what's happening to you too and remove that app.
Link https://productforums.google.com/forum/#!msg/nexus/pOwnLOlPPaU/a3zVV1QxAwAJ

lbalmaceda said:
Other kinds of overlay can be the "chat bubbles" from Facebook Messenger or Flynx tabs.
Click to expand...
Click to collapse
For me it's Lux, which also uses overlays. I have to pause it every time for things like this.

I had the same problem yesterday. As far as I know, I don't use any app that can cause the "screen overlay" problem, anyway it seems that clearing cache and dalvik solved the problem for me, at least for now..
EDIT: never mind, problem reappeared. I had to switch off all the apps in the "draw on other apps" menu..
EDIT 2: found the culprit: gravity screen.

Mine is velis auto brightness i believe

In my case it was the File Manager extension. Go to settings -> search for "draw over other apps" -> disable it for File Manager.

Potentially it is any app the draws over app. Just go into app permissions and write down every non google app that asks for draw over other app permission. Then disable all of them to see if the problem goes away. Then reenable one by one until the problem comes back.
In MTC19Z they no longer have the Allow permission that can't be tapped. Instead they have a warning that it won't continue until you disable the app that is drawing over screen (but they don't tell you which app that is). It is slightly less confusing, but equally annoying to have to figure out which app that is, then to turn off the offending app each time, then re-enable it.

Facebook Messenger bubbles are overlay

I don't think it's overlay
If it was an overlay it would be over the whole screen, but I can actually press the "Deny" button.
Anyway I disabled Twilight, the only app I have with overlay - no results
BTW, if your Nexus rolled off of it's 18 months support - it's time to install a custom ROM before the planned obsolescence machine kicked in

dmt0 said:
If it was an overlay it would be over the whole screen, but I can actually press the "Deny" button.
Anyway I disabled Twilight, the only app I have with overlay - no results
BTW, if your Nexus rolled off of it's 18 months support - it's time to install a custom ROM before the planned obsolescence machine kicked in
Click to expand...
Click to collapse
What you describe is exactly the behavior with overlay after june update. I don't think it is the overlay per se, but a bug in the warning mechanism blocking your button.
In july update they changed to a promot that links you to the overlay permission page.

i am also having the same problem..using honor 8...can't click on allow permission..

Guide: How to get past the notification issue in EUI

First of all, this thread is not for ranting about the issue. This is about finding a solution. So, please save your rants for other threads.
Many users are reporting notification problems using their LeEco Le Pro 3. I actually refuse to call it a problem. EUI is very aggressive about the memory and power management. And these options are by default turned on. There are few tools available that can allow apps to run more freely in the background. I absolutely hate that stock android doesn't provide any such tool to limit wakelocks or control apps running in the background. So, for every android phones I have used in the past, I used Greenify, Amplify, AppOps to gain those controls.
Now obviously we don't want all of the apps to get limited. A smartphone is about connectivity, and timely syncing is essential for some of the apps. Below are some of the steps that can be taken to get more control of the apps running in the background.
1. Notification Management
Go to Settings>Notification management
Set as 'Important notice' for all the apps you need more frequent notification from.
{
"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"
}
2. Disable Auto Cleaning
EUI automatically cleans up app from memory. Disable it for the apps which you need to run in the background.
Go to Phone Manager > Power saving management > App protection
Disable auto cleaning for the necessary apps. I recommend having it enabled for your launcher, if you are using a 3rd party one.
This can also be accessed from the recents menu. Pull down on the desired apps to keep it in memory. This is sometimes useful, because for whatever reason, not all the apps are listed on the previous menu.
2. Sleep Mode Clean up.
Go to Phone Manager > Power saving management
a. Disable Lock-screen cleanup. (This works like the greenify app, once the screen goes off, the background apps get killed)
b. Disable Ultra-long standby during sleep. (Phone basically goes to power-saving mode at night)
Chose depending on what you need. I am keeping the Ultra-long standby on, but Lock-screen clean up off.
3. Wakelock Limit
This works like the Amplify app, but unfortunately we don't have control on which wakelocks to block.
Go to Phone Manager > Power saving management > Align wake up
Disable the options you prefer. They are self-explanatory. I have both of them on, but not having any sync issues with the apps I care about.
4. Auto Launch Limit
Self Explanatory. I used to access this option form AppOps module. Manages which apps can wake up the device from sleep. Enable for apps needed.
Go to Phone Manager > Privacy safety > Manage Auto Launch
5. Background resource control
Dial *#*#46360000#*#* and uncheck 'Enable background resource control'.​
Of course all these steps are gonna take a toll on the battery to some extent. Play with the settings as you wish. Every people has different needs. Choose whatever works best for you. Feel free to share your observations and recommendations. I shall update this thread accordingly.
LeEco's latest update actually disabled most of these battery saving features by default. All apps are allowed to run in the background and wake by themselves. So, you may want to do the opposite now. Block wakelock and restrict background operation for the apps you do not want.

Looking forward to trying this, thanks for sharing!

It's impressive they added all these battery saving features into the rom. I really like this phone alot.
Sent from my LEX727 using Tapatalk

DxTcmix said:
It's impressive they added all these battery saving features into the rom. I really like this phone alot.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
If the above does not work, which they did not for me, another member discovered a thread from the India forums mentioning a bug in EUI software causing the notification issue. A fix that appears to be working for me so far is:
Dial *#*#46360000#*#* and disable “Enable background resource control”.​

payton8292 said:
If the above does not work, which they did not for me, another member discovered a thread from the India forums mentioning a bug in EUI software causing the notification issue. A fix that appears to be working for me so far is:
Dial *#*#46360000#*#* and disable â??Enable background resource controlâ?.​
Click to expand...
Click to collapse
Holy **** I think that did it, including the pesky Nine email client issue that none of the other settings helped.
I still had to add Nine to allow auto-launch but I think it's working. Going to continue testing .
I wonder how the guys at Indian Forum discovered this.

payton8292 said:
If the above does not work, which they did not for me, another member discovered a thread from the India forums mentioning a bug in EUI software causing the notification issue. A fix that appears to be working for me so far is:
Dial *#*#46360000#*#* and disable â??Enable background resource controlâ?.​
Click to expand...
Click to collapse
nice, I shall add that to the first post.
Sent from my LeEco Le Pro3 using XDA Labs

Seems to have worked for me too! I get gmails on time, one of the biggest offenders. Also Google's clock wouldn't wake fit alarms before. Does now so far.
Sent from my LEX727 using XDA-Developers mobile app

New update fixed everything for me. Didn't have to change anything in settings...
Sent from my LEX727 using Tapatalk

ceo.mtcl said:
New update fixed everything for me. Didn't have to change anything in settings...
Click to expand...
Click to collapse
exactly. The new update changed the default values for the system. :good:
Now, you may want to do the opposite for some of the apps to stop them running in the background
Sent from my LeEco Le Pro3 using XDA Labs

Would you know where are the APN settings in this phone? I'm not getting T-Mobile MMS.
Sent from my LEX727 using Tapatalk

ceo.mtcl said:
Would you know where are the APN settings in this phone? I'm not getting T-Mobile MMS.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
Settings/Mobile Networks/Sim Card INformation- Clicl on your phone number and a new menu with APN will appear.

Hi!
I am on a LEX720, with current 5.8.018S (build id WAXCNFN5801811012S).
I tried all the steps from OP and this makes notifications much more reliable (as the apps continue to run in the background and won't be killed). But google cloud messaging is still not working correctly (and the steps in the OP don't fix this).
I tested like this:
I made sure that the application (I tested with the "Signal" app) is definitely not running (i.e. manually killed it over adb).
Then I sent a message to my device and monitored if the Google Play Services are receiving a notification on the device and in fact, yes it does.
BUT: The target app get's NOT started (and so I won't see the message until I open the messaging app later myself).
When I look into logcat I see that Play Services received the C2DM (cloud-to-device-message) but did not deliver the intent (which should cause the relevant app to be started, if it is not running yet):
Code:
11-16 15:33:34.688 W/GCM-DMM (31553): broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=org.thoughtcrime.securesms (has extras) }
This behaviour is the same for me for all apps which use Google cloud notification (WhatsApp, Threema, Signal, etc..).
It can also easily be tested with this app here: Push Notification Tester
Everything works fine as long as the app is open. But if you request a notification in 20 seconds, and then in the meantime kill the app (by swiping it away in the recent apps screen), you won't get any notification. Just the warning message in logcat (just filter for "W/GCM-DMM").
Can anybody else confirm this?

androcheck said:
Hi!
I am on a LEX720, with current 5.8.018S (build id WAXCNFN5801811012S).
I tried all the steps from OP and this makes notifications much more reliable (as the apps continue to run in the background and won't be killed). But google cloud messaging is still not working correctly (and the steps in the OP don't fix this).
I tested like this:
I made sure that the application (I tested with the "Signal" app) is definitely not running (i.e. manually killed it over adb).
Then I sent a message to my device and monitored if the Google Play Services are receiving a notification on the device and in fact, yes it does.
BUT: The target app get's NOT started (and so I won't see the message until I open the messaging app later myself).
When I look into logcat I see that Play Services received the C2DM (cloud-to-device-message) but did not deliver the intent (which should cause the relevant app to be started, if it is not running yet):
Code:
11-16 15:33:34.688 W/GCM-DMM (31553): broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=org.thoughtcrime.securesms (has extras) }
This behaviour is the same for me for all apps which use Google cloud notification (WhatsApp, Threema, Signal, etc..).
It can also easily be tested with this app here: Push Notification Tester
Everything works fine as long as the app is open. But if you request a notification in 20 seconds, and then in the meantime kill the app (by swiping it away in the recent apps screen), you won't get any notification. Just the warning message in logcat (just filter for "W/GCM-DMM").
Can anybody else confirm this?
Click to expand...
Click to collapse
Have you tried this?: Dial *#*#46360000#*#* and disable “Enable background resource control”
That's the only thing that's made my notifications finally from within apps (aside from also enabling notifications in settings, priority notifications, not 'cleaning' apps etc. I don't use what'sapp though. But before that, google clock wouldn't wake it for alarms or timers... now it does. I also wasn't getting push notifications for Voxer messages or in the Amazon Flex driver's app that I use for work. They all work fine now after disabling that background resource control crap. They need to remove that as being on by default immediately!!!

benjmiester said:
Have you tried this?: Dial *#*#46360000#*#* and disable “Enable background resource control”
Click to expand...
Click to collapse
Yes, I have disabled this setting. Nevertheless push notifications don't work as expected.
As soon as the app which should receive the push notification is no longer running in the background, the notification will not be shown. This affects every app which uses Google's push notification service.
Here is a short demonstration video how it normally should work (shown on a Nexus 6): https://goo.gl/photos/zV6D4dKm7hufnTTi6
(The app in the video is the Push Notification Tester app I've mentioned before.)
As you can see in the video normally notifications will be received, even if the target app process is not even running. Google Play Services takes care to send an Intent which starts the app so that it can handle the incoming notification.
Unfortunately this seems not work on my LePro 3.
Does this work for anybody else?

androcheck said:
Yes, I have disabled this setting. Nevertheless push notifications don't work as expected.
As soon as the app which should receive the push notification is no longer running in the background, the notification will not be shown. This affects every app which uses Google's push notification service.
Here is a short demonstration video how it normally should work (shown on a Nexus 6): https://goo.gl/photos/zV6D4dKm7hufnTTi6
(The app in the video is the Push Notification Tester app I've mentioned before.)
As you can see in the video normally notifications will be received, even if the target app process is not even running. Google Play Services takes care to send an Intent which starts the app so that it can handle the incoming notification.
Unfortunately this seems not work on my LePro 3.
Does this work for anybody else?
Click to expand...
Click to collapse
I cannot seem to recreate that issue. I set the notification delay to 10 seconds, started the test notification, swiped up on the app to remove it from memory and about 4 seconds later I got my test notification.
However, if I put the timer to 30 seconds and start the test notification and then go to the app details and force stop it, I never get my notification, I am not sure if this is by design though.

Adminkiller said:
I cannot seem to recreate that issue. I set the notification delay to 10 seconds, started the test notification, swiped up on the app to remove it from memory and about 4 seconds later I got my test notification.
However, if I put the timer to 30 seconds and start the test notification and then go to the app details and force stop it, I never get my notification, I am not sure if this is by design though.
Click to expand...
Click to collapse
I am getting notification even if I set it to 5 mins, and remove the app from memory. Doesn't make sense, why it would be different....

androcheck, did you reboot after disabling background resource control?
Also make sure autostart is on for relevant app

It's working (I am stupid)!
meangreenie said:
Also make sure autostart is on for relevant app
Click to expand...
Click to collapse
Thank you for the hint. I am stupid, I really forgot to allow auto-start for the test app (I know it was mentioned in the OP and I have read it, no idea why I forgot it). If I enable the test-app in "Phone Manager" -> "Privacy Safety" -> "Manage auto launch" everything works as expected and notifications are displayed even if the app process has been killed in the meantime.
Thank you all for the feedback!
I did a few more tests and I unambiguously could verify that the
"Manage auto launch" permission is directly related with Google Push Notifications working or not.
Now that I think about it, it also makes sense this way. If you don't allow auto-launch for an app, this doesn't just mean, that it can't launch automatically at boot time, but also means that it cannot be launched automatically via a Push Message from the app publisher (if the app is not running yet). Hence push notifications will not work after the app has ended.
Adminkiller said:
However, if I put the timer to 30 seconds and start the test notification and then go to the app details and force stop it, I never get my notification, I am not sure if this is by design though.
Click to expand...
Click to collapse
AFAIK, this is by design. If you use force-stop from Settings, then nothing in this app will run again automatically. This includes the BroadcastReceiver which receives the Push Notification Intents. Only after one of the app components is started again manually (e.g. by manually launching the app again) the app will receive Broadcasts again.

OP, you're missing a step in step 3, it's phone manager > power savings management > Align wakeup

voidcomp said:
OP, you're missing a step in step 3, it's phone manager > power savings management > Align wakeup
Click to expand...
Click to collapse
LeEco actually moved it in the latest update. I guess I shall update it here too.

eu 8.12.13 - Lockscreen notifications

9.1.3 seems to pretty flawless so far. But there is one issue. Most apps don't get lock-screen notifications. Does anybody else have this issue too?
You can test this with the open source app (no ads) Radiodroid2. It is not possible to get a lock-screen notification for that app, despite tweaking all kind of settings. But it works fine on Nokia, Motorola, Nexus, Pixel devices for example.
---
Just to make sure this is not a config issue ... I wiped my device and reinstalled everything:
- Reset to China beta 8.12.27
- Flashed TWRP
- Wiped data, dalvik, and cache
- Flashed eu 9.1.3
- Flashed Magisk

check advanced setting in lock screen settings for on lock screen setting and notification settings per app like screenshot.

AOWL said:
check advanced setting in lock screen settings for on lock screen setting and notification settings per app like screenshot.
Click to expand...
Click to collapse
Thank you. I actually had tried that, but it only works for some applications (the minority unfortunately).
Could you please try the app RadioDroid 2?
https://play.google.com/store/apps/details?id=net.programmierecke.radiodroid2&hl=en_US
(It is an open source radio app without ads ....)
I should be able to pause music on the lockscreen (like on all the other phones before), but I am not able to figure it out.
I hope you can do it.

Youre right. You have to go to the app's notification settings, then disable and again enable "Show notifications"... Every Time when you start the app..

Mikromama said:
Youre right. You have to go to the app's notification settings, then disable and again enable "Show notifications"... Every Time when you start the app..
Click to expand...
Click to collapse
Thanks for confirming this bug!

Keep open in background

Is there a way to have this support more than 3 apps? It's ridiculous there's a limit with the amount of ram on this phone

That's a GREAT question, and I'd love to know the answer too. I haven't found one yet though. RAM isn't an issue on this phone. Maybe they worry too many locked in memory will affect battery life too much?

Where did you learn this is the limit? I've gone days without opening an app before and when I go back to it it's right where I left off.
You could perhaps go to the battery saving menu and disable the battery saving for any apps you want to remain running. This may cause some serious background battery usage though, but It may be worth trying out. Also, try running the high performance mode. I've run that mode a lot and never noticed it causing much battery drain over the standard optimised mode.

Coming from Oneplus and using it for a long time I can tell you, the Note 10+ is probably one of the best multitasking phones I've used (including Note 9). Chrome on this hardly ever closes in the background and find it always running and available with all the tabs open. Oneplus phones can hardly keep anything in memory / background loaded for more than 5 mins but but Oneplus phones feel sooooo much more responsive and snappy comparatively otherwise.

The default for background apps is set to, "standard." Which allows more than 3 background apps.
Go into Device Care - > Battery - > App power management
Some apps may have been automatically added to sleep or deep sleep.
You can add or remove apps as needed.
Sent from my SM-N976V using Tapatalk

imucarmen said:
Where did you learn this is the limit?
Click to expand...
Click to collapse
After you add three to "Keep open for quick launching" the option becomes greyed out.
You're right, it's generally not an issue where apps get closed down in the background anyway, but I normally have 4 or 5 that I always wanted 'pinned' to my recents list. Not a big deal, I just found the limit strange, given the phone's capabiities and hardware.

Henaway said:
After you add three to "Keep open for quick launching" the option becomes greyed out.
You're right, it's generally not an issue where apps get closed down in the background anyway, but I normally have 4 or 5 that I always wanted 'pinned' to my recents list. Not a big deal, I just found the limit strange, given the phone's capabiities and hardware.
Click to expand...
Click to collapse
How do you get " keep open for quick launching “ , I only get lock app instead , I'm running one ui 2.1 june security patch ” picture attached ”
Anyway you can bypass this using good lock app from galaxy store and use the module multistar and toggle on ”long live apps”

My task manager

hoss_n2 said:
How do you get " keep open for quick launching “ , I only get lock app instead , I'm running one ui 2.1 june security patch ” picture attached ”
Anyway you can bypass this using good lock app from galaxy store and use the module multistar and toggle on ”long live apps”
Click to expand...
Click to collapse
I'm also on One UI 2.1, June security patch. Screenshot of my menu option is attached. Maybe it's different between countries/regions/models? Mine is the Canadian N975W.
Edit: attachments aren't working, here's a link to the screenshot: https://1drv.ms/u/s!AqdgaMVMg2EMirgLXMqey1V1d0Gsdg?e=RGdVeX

I have three settings :
Put apps to sleep
Put apps to deep sleep
Apps that are not put to sleep.
I can add as many as i want in here.
There's an option to Goodlock's Task Changer to keep an app open which is a setting you don't have anywhere else in the system.
But i don't have that long live app in Multistar on my end.

Sorry for digging this up but do all of your apps appear in the "Apps that never sleep" list of apps?
I'm missing quite a few of my apps, aProfiles and Philips Hue for a start...
Anyone has noticed that before? Thnx