How to fake gyro values on an Android device - Android Q&A, Help & Troubleshooting

Hello everyone,
I'm attempting to manipulate the gyro values on my Android device that's currently running LineageOS 18.1. After verifying the device, I had assumed there would be specific files in the /dev/input directory where I could send the desired value to. Upon executing the command "getevent -l", I received the following output:
```
add device 1: /dev/input/event8
name: "uinput-fpc"
add device 2: /dev/input/event7
name: "sdm660-snd-card Button Jack"
add device 3: /dev/input/event6
name: "sdm660-snd-card Headset Jack"
add device 4: /dev/input/event3
name: "uinput-goodix"
add device 5: /dev/input/event1
name: "ant_check-input"
add device 6: /dev/input/event2
name: "synaptics_dsx"
add device 7: /dev/input/event5
name: "gpio-keys"
add device 8: /dev/input/event4
name: "hall-switch-input"
add device 9: /dev/input/event0
name: "qpnp_pon"
```
Unfortunately, none of these inputs appear to be connected to the gyro. However, I did manage to uncover the name of the gyro, which is BMI120. Despite this, I was unable to locate anything relevant in the kernel : https://github.dev/LineageOS/android_kernel_xiaomi_sdm660
If anyone could point me in the right direction on how to make these changes, I would greatly appreciate it.
Thank you.

Related

TUTORIAL:how to have sliding sound keyboard

hi guys,recently I have succeeded,to have a sliding sound keyboard,on nike...
i know that Phoenix ROM have this option inside,and i like this,but usually,i'm using Lilly ROM,and so i was going to study Phoenix ROM's registry configuration.
my device is so customized
ROM : Lilly 1.2 ita
HSPL : 1.22
Radio: 1.65.28.25
all you need is PhmRegedit or similar program
1) go to HKEY_LOCAL_MACHINE/Software/HTC/SlidingSound
2) add this 2 DWORD
value name:ActiveSlidingSound /value data:1
value name:SlidingSoundEffect / value data:1
3) add 3 new keys named "0" "1" and "2"
4) inside "0" key you must be create this 3 string value
value name: Default / value data: Star Trek Door
value name: in / value data: 0_in.wav
value name: out / value data: 0_out.wav
inside "1" key you must be create this 3 string value
value name: Default / value data: Light Sabre
value name: in / value data: 1_in.wav
value name: out / value data: 1_out.wav
inside "2" key you must be create this 3 string value
value name: Default / value data: Transformer
value name: in / value data: 0_in.wav
value name: out / value data: 0_out.wav
5) now you must to put in windows the pack at the link below
http://www.mediafire.com/download.php?43nhmmtyjzd
6) soft reset
this is Phoenix configuration,just copied,and trying to change sound i can say that it work with this values:
ActiveSlidingSound :1
SlidingSoundEffect :1
and changing sound with
ActiveSlidingSound :2
SlidingSoundEffect :2
dont' work with this values:
ActiveSlidingSound :0
SlidingSoundEffect :0
ActiveSlidingSound :1
SlidingSoundEffect :0
many thanks to rling and this wonderful ROM....without Phoenix i can't discover all this....
http://forum.xda-developers.com/showthread.php?t=366681&highlight=sliding+sound

[Q] MTP installation on debian doesn't work

Hello,
I've compiled the latest version of libmtp (1.1.2) and installed properly. It seems that the device is recognized but still without the ability to connect to it. Here is the log. I got two different outputs. So I'll post both of them:
1.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 12
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
2.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 13
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
I've read about a samsung-proprietary mtp protocol which would not work with libmtp. I hope those rumors are wrong, aren't they?
I'd really appreciate any help. I've been working on it for a couple of days and it starts really anoying me.
regards, hornby
I have the same issue. I am trying to connect my Linux Mint Debian machine to my SGS2 running CM9 nightly. Debian can see the device but communication is a nogo.
Here is mtp-detect:
Code:
~ $ mtp-detect
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
ignoring usb_claim_interface = -110Android device detected, assigning default bug flags
USB low-level info:
Using kernel interface "usbfs"
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 6860
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 9
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus
Vendor id: 0x6860
Device flags: 0x08008106
Device info:
Manufacturer: samsung
Model: GT-I9100
Device version: 1.0
Serial number: ????????
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Unknown (95c1)
95c2: Unknown (95c2)
95c3: Unknown (95c3)
95c4: Unknown (95c4)
95c5: Unknown (95c5)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
3001: Association/Directory
3004: Text
3005: HTML
3008: MS Wave
3009: MP3
300b: MPEG
3801: JPEG
3802: TIFF EP
3807: GIF
3808: JFIF
380b: PNG
380d: TIFF
b901: WMA
b902: OGG
b903: AAC
b982: MP4
b983: MP2
b984: 3GP
ba05: Abstract Audio Video Playlist
ba10: WPL Playlist
ba11: M3U Playlist
ba14: PLS Playlist
ba82: XMLDocument
b906: FLAC
Storage Devices:
StorageID: 0x00010001
StorageType: 0x0003 fixed RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 12332314624
FreeSpaceInBytes: 6137163776
FreeSpaceInObjects: 1073741824
StorageDescription: Internal Storage
VolumeIdentifier: (null)
Special directories:
Default music folder: 0x0000001a
Default playlist folder: 0xffffffff
Default picture folder: 0x0000001f
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: (NULL)
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
Text file
HTML file
RIFF WAVE file
ISO MPEG-1 Audio Layer 3
MPEG video stream
JPEG file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
Microsoft Windows Media Audio
Ogg container format
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
ISO MPEG-1 Audio Layer 2
Abstract Playlist file
XML file
Free Lossless Audio Codec (FLAC)
ERROR: Could not close session!
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
OK.

[Q] CM10 for allwinner13 tablet

I posting in reference to this thread
http://forum.xda-developers.com/showthread.php?t=2343531
I couldnt reply in there so here is my question:
- I installed the CM10 rom and JB G-apps but the touch screen does not work I tried the following patches but none work. Also when I apply the patches for touchscreen, CM10 does not load. it just shows black screen after the android logo.
I tried the following patches for touchscreen:
- gt811
- goodix811
- gs1680
The following is the information I got from my tablet:
add device 1: /dev/input/event4
name: "ecompass_data"
add device 2: /dev/input/event3
name: "gsl1680"
add device 3: /dev/input/event2
name: "gt811"
add device 4: /dev/input/event0
name: "sun4i-keyboard"
could not get driver version for /dev/input/mice, Not a typewriter
add device 5: /dev/input/event1
name: "axp20-supplyer"
if any1 has any info regarding solving this problem let me know
thanks
the screen is not black anymore but the touch screen is not working. let me know how to fix the touch screen issues. I have full backup of my stock rom so let me know how can I use my use moduels and icd files to make touch screen work in Cm10

Archos 101 g9 8gb & Huawei modem E173u-1[No driver found]

Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus

How to disable Android camera device by using bus id?

While looking at /system/lib/modules I could not find a kernel module for the camera of my device. Although even if I were to find it, modprobe doesn't exist in my system for which I would not be able to disable it.
When I look at the directory /sys/bus/media/devices I get the following output:
Code:
/sys/bus/media/devices/media0
/sys/bus/media/devices/media1
/sys/bus/media/devices/media2
/sys/bus/media/devices/media3
All symbolic links to ../../../devices/soc/... For example, media0 is a symbolic link to
/sys/devices/soc/1b0c000.qcom,cci/1b0c000.qcom,cci:qcom,[email protected]
Inside that directory is a driver directory which has an unbind file . According to [link posting not allowed to new users], I should be able to unbind the driver from the device. However, I don't know how to find the bus id of the device.
How can I find the bus id to disable the device? And after found, would the echo to the unbind file do the desired action?

Categories

Resources