Has anybody tested the bluetooth on the 7.8" version? I'm wondering if it is possible to pair a rooted gl3 with a bluetooth keyboard.
Yes, I've paired a keyboard.
The stock Settings.apk doesn't have direct access to the Bluetooth settings.
You can activate them over ADB as in here: https://forum.xda-developers.com/showpost.php?p=80852717&postcount=57
Code:
adb shell am start -n com.android.settings/.bluetooth.BluetoothSettings
I will eventually patch Settings to give direct access, but I've got a bunch of other stuff on my plate right now.
Related
Morning all,
So here is the deal. Buddy of mine broke his phone last night, I gave him one of my spares and he is keeping that. I took his broken S4.
The screen si dead and the digitizer does not work
Had CWM flashed on it but stock rom when I gave him the S4 initially
I tried every possible way to get usb debugging working without the screen. edited the build.prop and default.prop
change the settings.db no luck
using adb in recovery i was able to flash cyanogenmod 10 as i read it had usb debugging enabled by default
well after the flash and booting the device (using an MHL) i still cant access an adb shell. I'm guessing i have to go through the setup process of cy mod before it kicks on maybe.
so i'm stuck here. now what I was hoping, and I know its a long shot. Could someone maybe make a nandroid of a stock rom, any rom that is rooted. but with vnc or other remote software installed and setup so I can flash and access this device.
I was also going to try to find a TV with CEC support as I heard the MHL will pass them through
If I can convince someone to upload a nandroid for me (I'll provide hosting) anyone have any ideas on controlling this thing remotely. I just need to be able to install arliberator, pair it with my cars deck via Bluetooth and i'll be good to go.
-pete
More thoughts. Having usb debugging enabled is clutch. Just realized, it wont be on my wifi so vnc wont work to well. I know droid vnc and do usb using adb. so maybe thats my best bet
making some progress
Copied the wifi settings from wpa+supplicant.conf from my brothers phone
so the S4 witht he broken screen now connects to my wifi
I installed the droid vnc apk using recovery
also installed it on another phone, setup the way I want
copied the settings folder from the /data/data frolder and copied it to the S4
chmod the folder and files to 777 and set 776 on "androidvncserver" file not sure about that step
cant get vnc to connect. but making progress
made a bit more progress
downloaded fastdroid vnc
pushed it to /data/ in recovery using adb
set 777 as i didt feel like dealing with permissions
made a super simple script to load it and placed in /data/local called userinit.sh or something like that
so it started and I was able to make a vnc connection, but it was all black and didnt accept mouse or key inputs.
i assume this is because it is no longer maintained and is many years aold
tried to do the same with droid vnc server and starting the androidvncserver file.
unfortunatly it never accepted a connection and i'm not even sure if the file starts
need more work
anyone willing to save me all the trouble and get me a nandroid with usb debugging enabled? pretty please! :crying:
Final update. Working
so I ended up placing androidvncserver in /data/
chmod 777 /data/androidvncserver
placed my wpa_supplicant.conf in /data/misc/wifi
chown system.wifi wpa_supplicant.conf
made a userinit.sh and pushed to /data/local/userinit.sh
chmod 777 /data/local/userinit.sh
reboot
connected to wifi, accepted the vnc connection and mouse movement. still a black screen but with the MHL and the mouse. I was able to get ARliberator installed and connected to my appradio2 and configured everything there
done
Hello,
I am trying to get my Logitech Webcam to work with my N7 rooted stock ROM 4.4.2. So far, I have utilized the information from this thread:
http://forum.xda-developers.com/showthread.php?t=2092216
I did everything correctly through Terminal inputting the text show from the thread I linked, which is:
su
ls -l /dev/video0
chmod 666 /dev/video0
Opened up SimpleWebCam, and the app says my camera is not supported. I am using a Logitech HD Pro Webcam C910, and that webcam has been verified to be working properly.
I did a bit of research and found that DashCam would also solve my problem. I installed the DashCam app and the app still does not recognize my webcam.
Is 4.4.2 just giving everyone problems with this stuff? I'm not sure what else I can do or should be doing. Help?!
Thanks! =)
--Dan
Hello,
I am trying to get my Logitech Webcam to work with my N7 rooted stock ROM 4.4.2. So far, I have utilized the information from this thread:
http://forum.xda-developers.com/show....php?t=2092216
I did everything correctly through Terminal inputting the text show from the thread I linked, which is:
su
ls -l /dev/video0
chmod 666 /dev/video0
Opened up SimpleWebCam, and the app says my camera is not supported. I am using a Logitech HD Pro Webcam C910, and that webcam has been verified to be working properly.
I did a bit of research and found that DashCam would also solve my problem. I installed the DashCam app and the app still does not recognize my webcam.
Is 4.4.2 just giving everyone problems with this stuff? I'm not sure what else I can do or should be doing. Help?!
Thanks! =)
--Dan
Hello,
I bought few month ago a Azottu (allwinner T8 core) head unit and I'm trying to link it with my laptop using ADB.
The problem is the HU is USB Host, as well as the Laptop. So using USB for ADB is not possible.
I tried to make the link using Wifi; the HU is connected to the wifi and via the laptop I try to connect (using the ip of HU)
But that's not working.
Does someone manage to connect to a HU using ADB and Wifi ?
Of course the HU is on development mode (7890) and the USB debug is activated ([email protected])
Hope to your light and help. Thank you
install a terminal app on your unit and type in the following line:
setprop persist.adb.tcp.port 5555
Then reboot the device and you should be able to connect via adb over WiFi
realzoulou said:
install a terminal app on your unit and type in the following line:
setprop persist.adb.tcp.port 5555
Then reboot the device and you should be able to connect via adb over WiFi
Click to expand...
Click to collapse
Thank you, works better.
Now with
adb devices -l
List of devices attached
192.168.1.118:5555 unauthorized transport_id:2
But the device is unauthorized
So I tried to remove all the keys generated by adb on my laptop, and revoke the authorization on the HU (with a reboot for both) to resynchronize the pairing without success...
I tried to generate a new key with the adb keygen command, and then copy the public key (.pub) on the HU (adb push or cp from sdcard to /data/misc/adb/adb_keys) without success as well
Do you have any other idea ?
Thank you
To see "unauthorized" when using adb over WiFi with a head unit never happened to me so far. So I have no advice, sorry
Is adb not able to connect over even see these Joying FYT Airmont units with Oreo on it?
The head unit has a switch to allow debug over usb but when I connect a usb to my laptop I don't get the dialogue screen on the head unit asking if I want to connect to this device and the laptop cannot see the unit at all.
I figured maybe it needed device specific drivers in Windows so figuring Joying hasn't made any I found universal usb drivers for it. Nothing.
I got an app called Naptime or something that's supposed to be able to put the unit in full doze. It's designed to work on rooted devices but also says that can be worked around by using adb to give certain permissions. I can't do that if I can't even connect adb to the damn thing.
Also, is rooting these using that Magisk method result in the same type of full root the normal way on other devices? It isn't limited compared to the normal way is it?
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
Click to expand...
Click to collapse
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
rigattoni said:
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
Click to expand...
Click to collapse
These commands require root
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
Click to expand...
Click to collapse
Maybe I'm doing something wrong then. The developer options are enabled and I have it set for unlocked bootloader but my laptop can't see it whether I'm connected through the OTG usb port or the standard one and the HU doesn't give the popup dialogue asking if I want to allow the connection like my tablet and phone did. Maybe they changed something with these particular units with the new UI?
I did notice on another thread someone that had a FYT Joying Airmont with 8.1 and they said something about the 3 dot menu on the top right for "USB Connection" that brings up two options both in Chinese an his only worked on the lower option. I did try that too but still nothing. IDK. Maybe I had something else set wrong when I tried that lower option that made it not work in all my effort yesterday to get adb to see it and connect.