Database Info

Oct 15 frmware update: Touch Cover no longer works

After today's firmware update my Touch Cover stopped working. Well, not entirely - it's Volume buttons and Touchpad still work, but that' about it. By the way, I'm on Windows 8.1 RTM.
Is anyone else experiencing this?

Yeah there's another thread in the rt general section. Only known fix is a refresh under updates section. Annoying....

Just do a refresh and you wont loose your files. It fixed it for me.
Anybody notice a difference with the new firmware, what were the details
?

malberti1993 said:
Just do a refresh and you wont loose your files. It fixed it for me.
Anybody notice a difference with the new firmware, what were the details
?
Click to expand...
Click to collapse
I don't want to do refresh and loose some settings settings. I'm patiently waiting for a fix from Microsoft.

pauliusba said:
I don't want to do refresh and loose some settings settings. I'm patiently waiting for a fix from Microsoft.
Click to expand...
Click to collapse
All my settings and apps remained in tacked. Anyone find release notes?

I'm having the same touchcover problem after the Firmware update.
I just spent some time with MS Support and we also couldn't get it to work again.
I guess I'll wait until Friday/Saturday and see if starts working again after the official update to 8.1

I got the update 2 days ago, but my touch cover still works fine. I use my surface to take notes at uni, and I didn't really notice any difference. I heard the firmware update adds support to TC2.

pauliusba said:
After today's firmware update my Touch Cover stopped working. Well, not entirely - it's Volume buttons and Touchpad still work, but that' about it. By the way, I'm on Windows 8.1 RTM.
Is anyone else experiencing this?
Click to expand...
Click to collapse
Just want to confirm that doing a system refresh fixes this. I just did it for both my RT and my daughter's RT. Its a pain in the butt but at least it fixes the problem. Took around 20mins per device.
None of my settings were messed with but remember to restart the device one last time after everything is finished, it seems to need this!

@downloaderintruder: Touch and Type Cover 2 both worked on gen1 Surfaces when I checked out the preview hardware at the Windows store a few weeks ago. Made me want to buy one, actually; in addition to the backlight and thinner design, they fixed the multiple-keys-pressed-at-once problem that plagues the gen1 covers.

fix it !
:Hi guys. I fixed mine by playing in device manager. I notice I had new section called OTHER DEVICES winch had two UNKNOWN DEVICE. What I did was select one and go to update driver, browse my computer for drivers let me pick from a listo of devices... , then look for keyboards and you will see that there a few drivers to select. Select SURFACE TOUCH COVER AUDIO DEVICE VERSION 1.0131.0 and it should work. Mine is working!!!
UPDATE. I looked more into It. First you have to do the following
1. Go the Desktop app
2. Swipe from the Right
3. Touch Settings
4. Touch Control Panel
5. Touch Device Manager
6. Open the drop down for Firmware
7. Right click on Surface Touch Cover Firmware
8. Click on Uninstall
9. Do not check the box to delete the driver
10. Click on OK
11. Right Click on Touch Configuration Settings
12. Click on Uninstall
13. Do not check the box to delete the driver
14. Click on OK
15. Open the dropdown for Keyboards
16. Right click on Surface Touch Cover Filter Device
17. Click on Uninstall
18. Do not check the box to delete the driver
19. Click on OK
Do the same for all the items in Keyboard and for the Other Devices.
20. Restart your Surface.
After that. You should see the two unknown devices again. Right click and update drivers / browse my computer for drivers / let me pick from a list.../ and select HID Keyboard device
Do that for the two unknown devices... and it should work!!!

[Q]Crazy Wallpaper Issues[Q]

This is starting to really frustrate me now!
When applying a background to my phone, weather it be from the Gallery or integrated wallpapers, sometimes it will jump around on the homescreen. For example I will be in an app, press the home button and on going to the home screen the wallpaper will momentarily zoom in then zoom back out to normal. As this is happening the phone has excessive lag.
I've tried to isolate the issue, thought it might be a bad factory reset but my sister is over this weekend and hers is the same! it doesn't happen when running any applications in particular, it's literally random but when it starts doing it it will keep doing it. Restarting the phone doesn't fix.

jaaystott said:
This is starting to really frustrate me now!
When applying a background to my phone, weather it be from the Gallery or integrated wallpapers, sometimes it will jump around on the homescreen. For example I will be in an app, press the home button and on going to the home screen the wallpaper will momentarily zoom in then zoom back out to normal. As this is happening the phone has excessive lag.
I've tried to isolate the issue, thought it might be a bad factory reset but my sister is over this weekend and hers is the same! it doesn't happen when running any applications in particular, it's literally random but when it starts doing it it will keep doing it. Restarting the phone doesn't fix.
Click to expand...
Click to collapse
What ROM and wallpaper?
Sent from my EVO using Tapatalk

numel007 said:
What ROM and wallpaper?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
My bad, should have mentioned. Both of us are 100% stock, just checked my mums is doing it too. Any wallpaper, it doesn't matter.

jaaystott said:
My bad, should have mentioned. Both of us are 100% stock, just checked my mums is doing it too. Any wallpaper, it doesn't matter.
Click to expand...
Click to collapse
Weird. I'm on stock and everything is fine... Try downloading a different launcher for now and see if it still happens. Doesn't have to be permanent, this is just for testing purposes.

numel007 said:
Weird. I'm on stock and everything is fine... Try downloading a different launcher for now and see if it still happens. Doesn't have to be permanent, this is just for testing purposes.
Click to expand...
Click to collapse
Already tried that too and it doesn't do it. I will try and get a video of it, just depends if they will let me borrow one of their phones.

jaaystott said:
Already tried that too and it doesn't do it. I will try and get a video of it, just depends if they will let me borrow one of their phones.
Click to expand...
Click to collapse
Get a logcat too if you can. I probably won't be able to read it, but hopefully somebody with more experience will wander by.
Sent from my EVO using Tapatalk

numel007 said:
Get a logcat too if you can. I probably won't be able to read it, but hopefully somebody with more experience will wander by.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I should know this but been out of the game for a long time, how do I go about getting a logcat? Managed to get a video of it, just transferring it to my phone now.
I heard someone else mentioning they were having these issues, they put it down to an update with google Search, however google Search has since been updated and the issues are persisting.

jaaystott said:
I should know this but been out of the game for a long time, how do I go about getting a logcat? Managed to get a video of it, just transferring it to my phone now.
I heard someone else mentioning they were having these issues, they put it down to an update with google Search, however google Search has since been updated and the issues are persisting.
Click to expand...
Click to collapse
It's all good. First you'll need adb to be installed. I usually run adb on ubuntu, so I'm not experienced with windows commands.
On ubuntu. open terminal, connect phone, make sure usb debugging is enabled. You'll probably recieve a warning about an RSA fingerprint, which you will accept. Then in terminal, do
sudo su
adb start-server
now cd into whatever directory you want to store your logcat in
Once in the directory, run "adb logcat -v long > wallpaper.txt"
Reporduce the problem
Kill the logcat
Open the text file that was created
Either upload the file or pastebin it and post the link
Done!

numel007 said:
It's all good. First you'll need adb to be installed. I usually run adb on ubuntu, so I'm not experienced with windows commands.
On ubuntu. open terminal, connect phone, make sure usb debugging is enabled. You'll probably receive a warning about an RSA fingerprint, which you will accept. Then in terminal, do
sudo su
adb start-server
now cd into whatever directory you want to store your logcat in
Once in the directory, run "adb logcat -v long > wallpaper.txt"
Reporduce the problem
Kill the logcat
Open the text file that was created
Either upload the file or pastebin it and post the link
Done!
Click to expand...
Click to collapse
Doesn't that require root? Not 100% how to do that though, I used to be pretty good with ADB but unfortunately that was back in the Desire days and I've not really been into rooting since I got my HOX last year I change devices too much. Anyway, here is the video documenting the issue.
http://youtu.be/pBeNpwP5TFQ

jaaystott said:
Doesn't that require root? Not 100% how to do that though, I used to be pretty good with ADB but unfortunately that was back in the Desire days and I've not really been into rooting since I got my HOX last year I change devices too much. Anyway, here is the video documenting the issue.
http://youtu.be/pBeNpwP5TFQ
Click to expand...
Click to collapse
And you said your entire family is experiencing this? Ok go to about phone and tap Build Number a bunch of times. Should activate dev settings. Just see if you can get adb to work at all. I'm not certain whether it requires root or not. It confuses me that your family all has this problem, but it hasn't been reported by the rest of the Nexus 5 users around the world...

numel007 said:
And you said your entire family is experiencing this? Ok go to about phone and tap Build Number a bunch of times. Should activate dev settings. Just see if you can get adb to work at all. I'm not certain whether it requires root or not. It confuses me that your family all has this problem, but it hasn't been reported by the rest of the Nexus 5 users around the world...
Click to expand...
Click to collapse
Well I have to go out right now but I will try when I get back in. I'll do a Google Search and see if i can find how to.

You could try wiping data for your Home launcher. Just go to Settings/ Apps then swipe to " All" tab and open Google Search. Wipe its data and it will reset your launcher to default. See if it still persists.

I'd say it's because the launcher wasn't designed to have many additional screens as shown.
Looks like it's redrawing the launcher after leaving and returning to it.
Try getting rid of the extra home screens and retest.
WR
Sent from my Nexus 5

you are not the only one who has this issue..Even my nexus 5 does this..
ROM-Dirty Unicorns
Kernel-Franko r35

lordvoldemort said:
you are not the only one who has this issue..Even my nexus 5 does this..
ROM-Dirty Unicorns
Kernel-Franko r35
Click to expand...
Click to collapse
Happens on stock or on DU too?

WarRaven said:
I'd say it's because the launcher wasn't designed to have many additional screens as shown.
Looks like it's redrawing the launcher after leaving and returning to it.
Try getting rid of the extra home screens and retest.
WR
Sent from my Nexus 5
Click to expand...
Click to collapse
Not true. I've read reviews where people have tried upto 20-30pages with no issue.

bushako said:
Not true. I've read reviews where people have tried upto 20-30pages with no issue.
Click to expand...
Click to collapse
Ok.. was an idea is all.
WR
Sent from my Nexus 5

WarRaven said:
Ok.. was an idea is all.
WR
Sent from my Nexus 5
Click to expand...
Click to collapse
that's alright, I was just stating what I had read else where.?

My phone phone was doing this, but I figured out that it was an issue with how you zoom or place the wallpaper when applying it. When I applied with zedge, it was causing problems. Are you using a 3rd party app to find and apply wallpapers? Try switching by long-pressing a blank area on your home screen, and hitting wallpaper.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 02:07 PM ---------- Previous post was at 02:02 PM ----------
I actually just managed to replicate it. To fix it, try this... First select one of the stock wallpapers that came with the phone, using the stock method I mentioned above. Then test, your problem should be 100 percent gone. Then go to change your wallpaper back to the one you want, but do NOT select it from where it is on the bottom bar. Hit 'pick image' and then choose the wallpaper you want. Before you hit the check mark in the upper left hand corner, make sure the wallpaper is centered and fully zoomed out. That should fix it.
Sent from my Nexus 5 using xda app-developers app

Android Wear Pip-boy

For those who don't know what I am talking about.
http://fallout.wikia.com/wiki/Pip-Boy_3000_Mark_IV
https://www.google.ca/?gfe_rd=cr&ei=w69nVveEIeWM8QfYjIsQ&gws_rd=ssl#q=fallout+4+game
https://play.google.com/store/apps/details?id=com.bethsoft.falloutcompanionapp&hl=en
This is an android app that allows you to use your phone as pip-boy. It actually syncs with your game, so all information is real-time and, yes, it works on our android wear devices!

Do you have to side load it to the watch? I have it on my phone, but there is no option to open it on my zenwatch 2.

barcodejames said:
Do you have to side load it to the watch? I have it on my phone, but there is no option to open it on my zenwatch 2.
Click to expand...
Click to collapse
Yup, you need to extract apk and sideload it. Also, notice how it cuts off 40% of the app and clicking on the buttons is really hard as they are so small. So, its only good for showing off to your fallout 4 fan friends. Although, using the map for fast travel on the watch is not that bad.
[Added]
However, if you are really determined to have it showing fully, you can try playing with DPI values.

I figured it out. It keeps randomly closing for me though, and the left and right half of the screen are cut off. I'm new to sideloading apps to my wear device, so now I need to figure out how to remove it from my watch

barcodejames said:
I figured it out. It keeps randomly closing for me though, and the left and right half of the screen are cut off. I'm new to sideloading apps to my wear device, so now I need to figure out how to remove it from my watch
Click to expand...
Click to collapse
I tried some of the methods posted on the net, but none seem to work. What you can try is to load TWRP recovery into your watch and just delete folder that contains works like falloutcompanionapp inside /data/app/. Or if you already rooted your watch, you can just access that folder without recovery.

barcodejames said:
I figured it out. It keeps randomly closing for me though, and the left and right half of the screen are cut off. I'm new to sideloading apps to my wear device, so now I need to figure out how to remove it from my watch
Click to expand...
Click to collapse
Code:
adb shell
pm list packages -3
Copy+paste the packagename you want, then
Code:
pm uninstall <packagename>
exit

Let me guess.... the watch has to be rooted to sideload it?

GuyInDogSuit said:
Let me guess.... the watch has to be rooted to sideload it?
Click to expand...
Click to collapse
Don't guess - just try.

ranf said:
Don't guess - just try.
Click to expand...
Click to collapse
I did some research, and it turns out I don't have to be rooted. Don't even need that special CAT5/USB cable that the Moto 360 requires. Just Sven's toolkit.

That's right, you don't need a root to sideload apps. You just need to activate the adb mode in developer settings. Its best to use adb over USB since Bluetooth is so painfully slow.

Possible Temporary Solution For Notifications Delay ! - No Root Needed

Hi! I own a Mate 8 and like many others, have this big problem with notifications, especially with emails.
After having tried several firmwares, nothing has changed.
True, the phone has a large autonomy, but .... Who wants a device that lasts 48 hours on, if not fulfill its basic mission?
This I discovered, is not my discovery.
I think I have read all the threads in XDA concerning the issue, and I see that we are all lost in the fog.
Someone (I apologize because I do not remember the thread, or the owner) suggested that with a simple adb command, you could disable Doze, and then, all notifications would arrive immediately.
And it is true !
It is true, though not a definitive solution, because when you turn off the device, the solution is again lose ....
But consider that the method is super simple, and I see it as a possible solution until some brilliant mind, the kind that many see in this forum, to develop an app that automatically run at startup, and not to depend on a PC every time you start the phone.
I would like someone else try this, I've done in my device (AL-10 firmware version B168), and is a radical change in functionality.
I work in sales online, and for me it is vital receive emails instantly.
The steps are simple and absolutely reversible:
NO NEED TO BE ROOT FOR THIS
1- Android SDK installed on the PC
2-Enable "USB debugging" in developer Options
2- Connect the device to the PC with the screen off (I'm not sure if relevant)
3- Go to the installation folder of Android sdk, and then enter in the "Platform tools"
4- Button Shift + right mouse button, and then click on: "open command window here"
5- write "adb devices" to verify that the phone has been detected
6- if it has been detected (the serial number of the device should appear on the command screen), and then, write this new command:
adb shell dumpsys deviceidle disable
...then, enter.
Should appear a response such as "idle mode disable" as confirmation.
This command turn off Doze, so the device is "always on alert".
The theory indicates that autonomy should now be affected markedly...
But in my experience it is not so.
As I said, it is a temporary patch... When you turn off the device and turn it on again, these changes are lost (Which also makes reversible)
Maybe someone here, can give us some glimmer of hope with an app that simply run this command automatically (do not know if it is possible without root).
All I can say, based on my experience, is that this works perfectly and do not depend on updates from Huawei ... wich probably never come.
In my case, I never turn off the device except in very unusual conditions. It may depend on this temporary solution until someone give us a hand!

i tryed this solution ( my mate rooted) and app tasker but issues not solved... i don't know why...

Unreal988 said:
i tryed this solution ( my mate rooted) and app tasker but issues not solved... i don't know why...
Click to expand...
Click to collapse
My Mate is not root, is a NXT-AL10 untouched, 4Gb ram version, and at least in my case, this patch is perfectly functional.
I have tried several times in an attempt to get it to work after restarting the phone, and that is why I can assure you it works, at least in mine (if not turn off the phone) ..
By the way, just I discovered that if I write:
adb shell dumpsys deviceidle
all applications that Doze have in the whitelist, shown on the screen of the PC.
Perhaps some expert knows how to use this information specific to this model.

i tryed many times, but after 30 minutes all notidication are stopped. whatsapp is in white list, but issues not solved.

I've been running my phone for about a week with the dumpsys command and can confirm it's resolved all of my notification issues and I still get 2 days battery life with a fair amount of us. I've not noticed additional battery drain running this command.

I'm the one who found it, by simply analyzing how Doze worked on the phone.
It would be possible to make an app that automatically runs the command upon startup, of course.
You could use something like this:
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=en
But root is necessary to adjust the settings unless you plug in a computer with ADB.
I don't have the phone working anymore (it's bricked) so I can't do much, sorry.

This solution don't work in my case. After a few hours, notifications fail. The only way to get notifications is restart the phone.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk

daniville said:
This solution don't work in my case. After a few hours, notifications fail. The only way to get notifications is restart the phone.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Click to expand...
Click to collapse
exactly, same problem for me

I seen someone install greenify and using the app setting white list to avoid the doze issue. Anyone can confirm? No root needed

What helped for me was going into Apps, then Advanced, then Ignore Battery Optimizations and select the apps you want. They will stay open and you should get notifications.

Do you think there is any possibility to execute the command from the phone itself?
Thx

lmerega said:
Do you think there is any possibility to execute the command from the phone itself?
Thx
Click to expand...
Click to collapse
Yes, but only with root.

duraaraa said:
Yes, but only with root.
Click to expand...
Click to collapse
how?

johnweber7375 said:
how?
Click to expand...
Click to collapse
Hi,
with an app like Terminal Emulator or others...

ajsmsg78 said:
What helped for me was going into Apps, then Advanced, then Ignore Battery Optimizations and select the apps you want. They will stay open and you should get notifications.
Click to expand...
Click to collapse
This is oneof the first steps we all have done.... Nothing the problem still there....and i cant imagine that there is someone with mate 8 that his device hasn't this problem....the most of them just hasn't notice... If you dont use mail app and exchange then is possible not to notice that the notification isn't coming to time

PNF doesn't help?

johnweber7375 said:
how?
Click to expand...
Click to collapse
open teminal and digit
su (and allow permission in popup)
dumpsys deviceidle disable

Unreal988 said:
open teminal and digit
su (and allow permission in popup)
dumpsys deviceidle disable
Click to expand...
Click to collapse
Thank you for your writing, but i wrote at another thread, disabling doze didnt solve my notification problems..
HUAWEI NXT-AL10 cihazımdan Tapatalk kullanılarak gönderildi

exactly, in my case issues not solved

Same issue, don't work for me.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk

notification fix

OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.

sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.

I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.

Thanks for the tip

Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk

Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.

Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.

precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.

If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.

Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968

I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.

Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.

This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?

Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.

Like this

sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.

And also the setting here

sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.

Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.

Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.