I am running a Debian Wheezy on my Note 8 via Linux Deploy, and I've managed to make it work in framebuffer mode, complete with inputs.
Now, my problem is that I am using a BT mouse and keyboard, which both disconnect after one minute of booting the distro.
I have to stop Android's graphic interface, and apparently it also somehow disconnects the BT. I noticed that it also happens when my screen goes off. I've tried every BT keep awake app, plus some from xposed (Bluetooth toolkit and Never Sleep), it just doesn't work.
Is there a hack to keep that BT alive? Maybe something via command line?
Thanks!
Related
As some TP2 or other WM device owners I've noticed that WM often seems to forget WPA passwords when using WiFi. It doesn't really matter wether you use AES or TKIP and how long your preshared key is.
In my case the symptoms look like this: After I create a WiFi connection (WPA2, AES, hidden) so that my Rhodium can use my home WiFi network, everything goes just fine. But then, after having established a connection for two or three times the troubles begin. Usually it takes about 3 or 4 seconds to establish a connection. But suddenly it takes about 10 seconds after which I get a warning that the connection could not be established. If I then go to my connection settings, I allways find them completely messed up, so that I have to select WPA2 and AES and reenter my password an so on. Well, after it happends to you for three or four times, this becomes extremely annoying.
Recently, however, I've found a kind of workaround for this problem. And here it comes: After I turn on the WiFi, I simpy wait for about four seconds. If WinMo behaves nicely, 4 seconds are pretty enough to establish a connection. If, however, I don't get connected after these 4 seconds, I IMMEDIATELY turn WiFi off, wait 2 seconds, and turn it on again. With 99% probability this second try gives me a working connection. If it doesn't, I simpy repeat the same procedure once again. So, the scheme is quite simpe:
Turn WiFi on and wait 4-5 seconds (it depends). Got connected?
Yes: O.K
No: Turn WiFi off, wait a second and turn it on again.
The main thing about this trick is not to let WinMo try to establish a connection for more than 5 or 6 seconds, otherwise it will delete your connection settings.
In my case, this workaround works perfectly. For more than two weeks I've been using my home WiFi with Touch Pro 2, establishing at least 4 or 5 connections a day and not a single time my connection settings were lost. Well, surely this thing with turning WiFi on and waiting and turning it off if you don't get connected fast enough is also a little bit annoying, but nevertheless it is much less annoying then having your connection settings all messed up every single day.
I'm not sure, whether this workaround will work with other devices or WinMo versions or even firmware versions, but may be it will help at least some of you affected by this odd problem. So you may just give it a try.
I'm using Touch Pro 2 with stock O2 Germany ROM (1.19.207.0)
Thanks for reading this long post and sorry for my bad English.
Excellent! Thank you for sharing your workaround!
I do something similar, except I turn wifi off by pressing the power button if the wifi hasn't connected in a few seconds. (By default wifi turns off when it goes into standby.)
On the odd occasions where the key does need to be entered again, I keep a copy of the wifi key "somewhere" on the device. It's a copy and paste operation after that, so it doesn't take long to re-enter the key. Luckily you can use the keyboard Ctrl-V method to paste the wifi key into the TouchFLO interface.
The other observation I've made, is that if I switch on the device by sliding out the keyboard, my Touch Pro 2 has a higher chance on getting a 'lock' onto a weak wifi signal. I'm not really sure why!
I'm glad that this workaround works not only for me
Actually, I don't use Connection Manager any more, for I've recently installed Rhodium Keyboard Controller GSM 1.3.2. Using this handy tool I remapped my Home button, so that double clicking it, turns WiFi on and and double clicking it with working WiFi turns wireless off.
I guess that Rhodium Keyboard Controller uses some advanced routine to activate WiFi, because since I use it for establishing WiFi connections, I rarely have to use my workaround, for normally I get connected on the first attempt.
see similar (but not the same) problem here
http://forum.xda-developers.com/showthread.php?t=562893
I have a really weird problem.
No matter what ROM I'm using, when I first turn my bluetooth on and connect with any device after about a minute or two the bluetooth turns itself off and if I manually turn it back on.
It's still connected to the device it was connected to and when I turn it back in it works fine but it will do this once each time I connect to any bluetooth device.
Can someone help?
I had downloaded the "auto off unpaired bluetooth" tasker profile and it had an error in it.
I've downloaded a "fixed" version and hopefully this will fix it. In any event, the phone is fine, but the tasker profile was defective.
I use bluetoothkeepalive from the Google play store. It holds the connection all the time, but I still have issues when I disconnect from my car and then reconnect again the next time..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've got a note 2, running 4.4.2, a note pro 8.4 running 4.4.2, and an asus win7 computer
i can run sidesync on the pc, connect the note via usb or wifi, and get keyboard/mouse sharing working just flawlessly
as soon as I attempt to do screen sharing, the note2 goes black (which it should) but the virtual phone just loads endlessly, and eventually times out. doesn't matter wifi or usb
if I launch sidesync on the tablet, and then the phone, the tablet see's the phone and attempts to make the connection. phone goes blank, and virtual phone just eventually times out, just like on the pc
has anyone gotten this working on the note 2? is there a specific version that works?
so, 5 minutes after the post, there's windows update notification, and the update is related to samsung USB driver update
do the update, reboot, and holy jebus, screen sharing works!
sorta
now I get connection (usb and wifi work) and I can see the screen mirrored. the phone screen does not black out, but I can't interact with it either. on the pc, I can see the mouse icon turn from spinny blue thing, to solid blue donut, but it does't interact with the phone. I can click the home, back and menu buttons on the bottom of the virtual phone, and they work, but nothing else does
bleh
any ideas?
So yeah, I flashed CyanogenMod 11 onto the OUYA, and it boots and works, however, there are two main problems that I can't work out how to fix or why they are occuring. These problems are that the WiFi is off, and cannot be turned on. Ethernet works however. The second one is that I cannot pair the controller. I put it into it's pairing mode (two middle lights flashing), however the OUYA never picks it up.
I'm not entirely a noob when it comes to flashing things but I don't know whether the boot.img in the CM zip needs to be flashed via fastboot, or if it does it automatically.
Can anyone tell me where I went wrong/how I can fix my issues?
Is this a black ouya? Wifi and bluetooth are not supported with cm11 on the black (anthracite) ouya.
I have a Samsung Tablet (android 7.0) four CCAs, all on good 5ghz wifi. Ever since the tablet was upgraded to 7.0, it's had an issue where, about half the time, once I select a device to cast to from Spotify/Pandora (either one), it disconnects the WiFi on the tablet. It will physically turn the wifi off, and it will come back on after about 20 seconds. After then it will work for a bit.
I have a LG G5 that has never had this issue. It also is running 7.0.
Could someone shed some light on what is happening when I attempt to cast? Why could it disconnect my tablet WiFi? The wifi comes from a RT-N66U, of which I've tried both old and new firmwares, but it made no difference. I've also done two factory resets on the tablet and turned off battery optimization on Spotify, pandora, and the Home app. Not sure what else to do. Finally, I've also done factory resets on all CCAs. Any input is appreciated. Thanks.