EskeRahn

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

It is in the official Android Market too https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup

Someone posted that Shift, Alt and Meta gets sticky, So IF they change type to Alpha a fix could be to change so the yellow arrow keys to send right&left Meta rather than Fn, and obviously adjust the key-maps to reflect this. Still Ctrl would not be sticky though.

Indeed, very interesting. let me tag @Waxberry, to make sure he sees this....

Yes, I got that. My point was that it would require a hole for the earpiece, unless you slide it 1cm up during calls. On the last part I would consider to mount it in a £1 clear silicone shell, and then let that be attached to the case.

Yes the first looks like a good fit. Though aud$30 (about us$20) is a bit on the hefty side, as it is plastic and not leather. But in contrast to the other slide and flip cases mentioned earlier, this one uses adhesive, and this means no problems with the side buttons, so absolutely interesting, and at the most a hole for the secondary microphone when slid in. (and for the earpiece if mounted flipping to the right not left, unless you just slide it 1cm up during calls), The 160mm is also a good fit, as it leaves a little space for magnetic plugs for the USB (and 3.5mm if you can get

Personally I would be more interested in the opposite: Something turning Off the screen (including touch sensibility) when the proximity sensor is activated. E.g. closing a flip-case or simply putting it in a pocket.

Flip-case....

Oh! Thought it was the charging 'only' that did not work. Sorry. As @netman said, the port could be the issue. But also try to simply blow into the port. With a little luck it is merely pocket lint in the plug. Also try with good light and a magnifying glass (or a macro camera) to look into the port and see if you find anything that looks like it should not be there. But still make sure to select Aeroplane mode, so it drains slower while looking for a fix.

I accidentally had a Pro1 depleted beyond the point of turning it on in about 100h, but as the above flag was earlier set, it did start charging (charge icon only) After about a quarter of charging I booted it, and it is just now charging and powered on.

If you got swiftkey installed, it kills that feature, but it brings it as a touch button in its own bar.

First put in aeroplane mode, to prolong the stamina. Then put in in fastboot mode and from a pc execute fastboot oem off-mode-charge 1 Turn it off, and see if it charges correctly. Try different cables also, not just different adapters. (If this flag is not set, it turns the phone back on when power is applied) See also e.g. this