EskeRahn

Sorry if my English is unclear. I meant that if the symbols not above the letters (e.g. over the digits) are only supposed to be accessible with the YellowArrow and not by Shift, it would be much more important to have those sticky, and that could be done by letting these send Meta-Left and Meta-Right. As Meta is one of the key-types sticky with Alpha. On the other hand if accessible by BOTH shift and sticky it will for qwertY only affect symbols on L and P not being accessible with sticky, BUT we are talking fourteen on the qwertZ : on Q, W, E, R , U, I, O, P, Ü , L, Ö, Ä , Y and M...

Well we expected at the least the first part see discussions on the different variants with front-over-back or back-over-front previous in this thread.

Well it was my bug confusing with irrelevant USB-debugging.. 🥴

The point is that sticky to get to symbols would be much more important than two clicks shortcuts (IMHO). Especially if they { F(x)tec } do not want shift to double to the access above the digits.

It would be better to let the yellow arrow do Meta rather than Fn. As this will allow for sticky if Full is changed to Alpha, See other thread.

It is slightly left of the speaker. Note that it got quite a delay in reacting to changes, but pressing power off and on, triggers a new read.

2.4 Works fine here too. I noticed a setting Multi/Single under connections before pressing GO I have tried both, and immediately pressing GO. The colour is different for single, otherwise the same. (a tiny bit slower in single)

I saw in the long case thread @wilhelmfitzpatrick has fitted a carbon fibre skin for a note 10, and it looked quite good.

I'm on 5GHz here. As you see it with WiFi only, does it make a difference if you pop out the SIM? (Just to narrow it down)

Unfortunately it seems like swiftkey messes with that. I know no usable workaround, sorry.

The point of a "teardown" skin over another skin is that it looks like you can peep into it.... So to improve the illusion you should be able to 'look in' everywhere. If you want that AND easy access to the screws, well then the foil would need cut outs for the screw-stickers and screw image-stickers on top of the stickers hiding the screws....

Could well be. Or perhaps the rooting mechanism is not perfected and have some odd side effects?

Tried your recipe both with and without autorotate, no problems.... A GUESS, as you have had other WiFi concerns, could it be that you are doing it while it is not completely finished negotiating with the WiFi router?

Can not do that, it request password on boot. But that things might fail if it is not finished booting, I really only see as an oddity, and not anything worth chasing, let alone use any resources fixing. But sure it ought not to happen, and if this is the only way we can reproduce the boot behaviour, the recipe might help them fix that.

We really should have two and a half foils!! One for the back, one for the under side of the display, and one for the top of the lower part behind the keyboard.... But I guess that would be slightly overkill....

Yes that is what I wrote: Android Market , http://market.android.com/ ...I know i'm old, but I'm not going to use the silly alias

@david Speedtest works fine here https://www.speedtest.net/my-result/a/5736094493

I have no idea. I do not know the app, nor how it is supposed to look. Only installed it to test this. Anyone else in here that knows? @VaZso ?

Well the standard question is of course what happens after a factory reset without install of previous? But that is a bit of overkill I guess. Maybe trying to compare the list of installed apps (enabled) could be a good starting point. And we are sure the Light Manager got notification access, right? If you uninstall and re-install it, it should clearly have a button to enable notification access.

Another possibility is some software a little too aggressively putting things to sleep when the screen goes Off?

That is the one, linked in the op. No root or anything here. After pressing Test and ok, you do press Power to turn the screen off and wait a bit, right? It does NOT show the colour when the screen is On, nether immediately after screen Off. I would say within 5 seconds.

Really odd that it works on some and not others. Only explanation when the LED works on charging is that some software are different. I assume we are on newest OTA on all, and that the notification access has been granted? And if so there really are only two possible explanations. Either we got something installed that magically make it work OR he got something installed that somehow interfere and disallow it. Could it be a program that ALSO got some notification LED action (he might not be aware of the app has), and this app somehow got an exclusive lock on the LED access???

We have seen that SOME apps controls the LED correctly, though not ALL apps. The link in the initial post of this thread works. Try this after install in the app Select the three bars and System Status, Select (e.g.) Aeroplane Mode Select a colour Select Test Click OK Click Power off, and wait a few second It should start pulsating in the selected colour.

Ah Thanks! That explains the difference! And yes silly limit, could have been a range. Let us hop they fixed that in 10 also. Setting the font to small also, does not seem to offer more options.

Try read the initial post in the thread. It was never intended as a discussion threads on apps. And as this is actually a feature request that is fixed by the app, I found it more suitable in here. That apart it did not seem to work that well on my unit, maybe it is because I fetched it from the Android Market, where it is 3.2.0, the version is slightly lower in your link 3.1.8. It does offer a lock mode I did not try, but simply turning off the display would have been enough for me. It seems a little odd that it would need more privileges to turn off the screen than to turn it on. B