COULD SOME DEV PLEASE HELP!!!:fingers-crossed:
I'm Sure floating touch can be ported to any android device by setting the screen sensitivity very high so that a way on the screen gets interpreted into a touch
.
.
This floating touch mod/port for the galaxy sl I9003 and galaxy 3(not galaxy s 3 just galaxy 3 I5800) thread states that floating touch can be enabled on most android devices , if someone(THATS WHERE THE DEV'S COME IN THE PICTURE) could find out for us which is the file that is responsible for the screen sensitivity
.
.
.
Heres the link to
the app that provides a gui for changing the sensitivity
http://forum.xda-developers.com/showthread.php?t=1932339
.
.Link to the actual thread from which the above thread/ app was created
http://forum.xda-developers.com/showthread.php?t=1915158
.
.
link to "how to tweak touch screen"
http://forum.xda-developers.com/showthread.php?t=1587553
.
.
link to thread that says any device can have floating touch!!(yipee but as i read , it turns into a frown cause it states all devices if the correct file can be dertermined )
http://www.xda-developers.com/android/floating-touch-on-the-samsung-galaxy-sl-i9003/
Deleted
I think glove mode can be ported but not the floating touch in browser cuz other devices cant make a difference between floating and touching...
Sent from my MT27i using xda app-developers app
Floating touch can't be ported to other devices, unless they use a similar touchscreen. You can have the 'floating' effect everywhere by setting the sensitivity to a very high value, but you won't be able to distinguish hover events and touch events that way.
What if we dont need to differentiate
Why do we need to differentiate at all??
at an earlier stage, we could make the phone to respond to floats as touches, so that the fingerprint is not a menace any more
PS im a noob , thats why i need some one to help me find out the correct touchscreen file to be modded:fingers-crossed:
arjun921 said:
Why do we need to differentiate at all??
at an earlier stage, we could make the phone to respond to floats as touches, so that the fingerprint is not a menace any more
PS im a noob , thats why i need some one to help me find out the correct touchscreen file to be modded:fingers-crossed:
Click to expand...
Click to collapse
It's not a single file anyway. Also, you just haven't tried that. It'll register random touches EVERYWHERE.
Maybe Maybe not , i aint so experienced...
K900 said:
It's not a single file anyway. Also, you just haven't tried that. It'll register random touches EVERYWHERE.
Click to expand...
Click to collapse
its just one file actually(maybe as per the thread which says to mod only one file), btw i even tried but couldnt find the path cause i got confused of which directory ahead...
.
.
. Please buddy Help me!!
Even if i get random touches, atleast it will be a start...
i dont mind giving the whole credit (whosoever if he/she helps ) but atleast lets try?:angel:
.
P.s. Check out all links for sure to have a better idea of what we actually are talking about(no offence intended but just in case you are an experienced developer still, please check)
A must try is the app which does the job...
Also till what i know is that the touch screen driver-file-to-be-modded lies in /sys/class/touch/switch/set_touchscreen/ for the galaxy s I9003
BUT for XPERIA U, i aint sure. I think it lies in /sys/class/input/
arjun921 said:
its just one file actually(maybe as per the thread which says to mod only one file), btw i even tried but couldnt find the path cause i got confused of which directory ahead...
.
.
. Please buddy Help me!!
Even if i get random touches, atleast it will be a start...
i dont mind giving the whole credit (whosoever if he/she helps ) but atleast lets try?:angel:
.
P.s. Check out all links for sure to have a better idea of what we actually are talking about(no offence intended but just in case you are an experienced developer still, please check)
A must try is the app which does the job...
Also till what i know is that the touch screen driver-file-to-be-modded lies in /sys/class/touch/switch/set_touchscreen/ for the galaxy s I9003
BUT for XPERIA U, i aint sure. I think it lies in /sys/class/input/
Click to expand...
Click to collapse
The Xperia U has a different touchscreen, which might or might not have manual sensitivity adjustment. I'm pretty sure it does not.
K900 said:
The Xperia U has a different touchscreen, which might or might not have manual sensitivity adjustment. I'm pretty sure it does not.
Click to expand...
Click to collapse
dude, galaxy 3 and Xperia U has the same touch sensing technology
so why cant we mod !?
is it that you just dont want this feature to be ported to anyother device, but rather stay on the device with which it actually came??
arjun921 said:
dude, galaxy 3 and Xperia U has the same touch sensing technology
so why cant we mod !?
is it that you just dont want this feature to be ported to anyother device, but rather stay on the device with which it actually came??
Click to expand...
Click to collapse
I'm pretty sure the sensor on the Galaxy 3 is not the same. It's the same vendor, but not the same model. I might be able to help you if you post the output of "find /sys/" in adb shell.
K900 said:
I'm pretty sure the sensor on the Galaxy 3 is not the same. It's the same vendor, but not the same model. I might be able to help you if you post the output of "find /sys/" in adb shell.
Click to expand...
Click to collapse
do one thing ,
please go through those threads, try installing that app,
check out the sys partiton, and then comment
if not interested, then please stop replying
:silly:
arjun921 said:
do one thing ,
please go through those threads, try installing that app,
check out the sys partiton, and then comment
if not interested, then please stop replying
:silly:
Click to expand...
Click to collapse
The app doesn't work, because it's intended for a different device with a different digitizer. The /sys file responsible is also relocated because a different device with a different digitizer needs a different kernel module, and the /sys files are created by that.
I might be able to help you if you post the output of "find /sys/" in adb shell.
Click to expand...
Click to collapse
It can't be done n stop insulting senior members by telling em to stop posting if they ain't interested, if dey weren't they would even reply
This is the problem with noobs they dun noe **** abt the devices and they expect magic/miracles from modders with features that device can't Hv due to hardware restrictions!!!
So if u think it can be done and you can do it and senior members/modders cant then I got jus 3 words foe u
"DO IT URSELF"
(Next tym pls do watch ur attitude and ur mouth before running it on senior members like K900 k)
Sent from my Xperia Sola using xda premium
I'm sorry, but I intended NO harm
I didn't even know what senior member means until you said it
I'm sorry K900
Thanks for the feedback
If you guys haven't noticed, this is my first thread here....
Sent from my ST25i using xda app-developers app
I don't know how to use adb btw
Sorry, but if you have time then could you please tell me what to do?
If you don't own the phone, I'll try to follow the instructions if you can help me:-o
Sent from my ST25i using xda app-developers app
I got adb installed, lemme try to find the path
Sent from my ST25i using xda app-developers app
arjun921 said:
I don't know how to use adb btw
Sorry, but if you have time then could you please tell me what to do?
If you don't own the phone, I'll try to follow the instructions if you can help me:-o
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Btw here's the link which will provide you with all the adb stuff go through it
http://forum.xda-developers.com/showthread.php?t=1474956
Sent from my Xperia Sola using xda premium
Thanks!!
soulhackereborn said:
Btw here's the link which will provide you with all the adb stuff go through it
http://forum.xda-developers.com/showthread.php?t=1474956
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Thanks man:good:
Got this
K900 said:
The app doesn't work, because it's intended for a different device with a different digitizer. The /sys file responsible is also relocated because a different device with a different digitizer needs a different kernel module, and the /sys files are created by that.
Click to expand...
Click to collapse
This is what i got on "adb find /sys/
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd C:\adb
C:\adb>adb find /sys/
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\adb>
do adb shell
then find /sys
TUTORIAL ON ADB AND LOGCAT : JDMC : Just doing my contribution.
This is part of TeamAscend, so if you are going to post this Tutorial on other forums please credit me, visit our website : I AM AWESOME!
Hello this is just to teach newbie users on how to install adb and get it working, I will also teach you how to use logcat to help devs with particular issues, okay lets get into it, I will try to be as formal and understandable is I can, I'm still a 15 year old so bare with my written language, not that its bad but we Kiwi's use weird slangs...
Setting up ADB
1. Okay first of all we need to enable Android debugging.
1a. To do so, head into Settings > development and check android debugging, If you're on CM10 + you will need to set Developer Options to "ON" then select Android Debugging.
2. Get a usb adapter and connect it to your pc and connect your device. Let it install drivers "If it's the first time.
3. Download "SDK Tools". and install it to your desktop for now, you can move it later when you want.
4. Now create a new folder on the desktop and copy all SDK contents into it so its neat and tidy.
5. Open "SDK Manager" and un-check everything except "Android SDK Platform-Tools" and click install packages, wait till it's done then close the window, now you should be in the folder that contains the SDK Tools etc... if you see the "platform-tools" folder you're good to go.
6. Now open the "platform-tools" folder and copy the destination output at the top.
7. Now we need to set the new destination to CMD, click the start button type "cmd".
8. When it opens type "cd" obviously without the ", now hit space and click paste now your command should look something like this...
"cd C:\Users\Your PC name\Desktop\the folder that contains the sdk tools name\platform-tools" here's mine : "cd C:\Users\Lenovo\Desktop\ADB\platform-tools". Now hit enter, your target folder will change.
9. Once its done type " adb devices", make sure your phone is connected! now hit enter and it'll show your device, now you know ADB Is up and running! If doesn't show your device continue to the next step, if it does continue from step "11".
10. Download the HTC drivers and install it, plug your phone again and wait for it to install all components, if MTP fails to install just ignore it. (If your storage is on MTP), now repeat the procedure from "7" again.
11. Now lets Logcat, Now there are 2 different approaches to the logcat, I will be showing you how to do both in this tutorial. Neither one is more correct than the other, it is 100% personal preference. Feel free to try both and see where you get.
LOGCAT PROCEDURE
Doing logcat from inside the CMD window.
1. Make sure your phone is plugged in and debugging is on, now repeat procedure "7" to set target folder if it isn't already done. ie : cd _____________________________ <-- your folder destination.
2. Type "adb logcat" without the " and hit enter. It will then print a list of random writing, whether you understand or not, it doesn't matter, it's not for your use .
3. To save the logcat for devs to use, once the logcat is running, please RECREATE the bug/issue you are having. so that it logs the error into it, now to stop the logcat hit "ctrl" + "C".
4. Once this is done please RIGHT CLICK choose "Select All" then press "Enter" on your keyboard this will copy the entire log to the clipboard. You can then paste it into a .txt file to upload and show to devs.
Doing logcat to text file.
1. Now repeat procedure "7" to set target folder if it isn't already done, make sure your phone is plugged in and usb debugging mode is enabled. Once this is done we are going to type the following command "adb logcat > logcat.txt" without the ", this should initiate the logcat, it will appear as though nothing is happening, this is correct!!! So don't worry.
2. Once the logcat is running, please RECREATE the bug/issue you are having. To stop the logcat on your keyboard press "ctrl" + "C".
3. Now you've done logging, note the logcat.txt file will be located in the platform-tools folder, just open it and you will see logcat.txt, upload it for the dev and he/she will investigate.
More ADB Commands for various logcats Thanks to "Tcpaulh" from Modaco.
External adb folder, just needed thanks man : Download
1. radio logcat for Wifi issues.
adb logcat -b radio > radiolog.txt
2. kernel logs.
adb shell
su
cat /proc/kmsg > /sdcard/kmsg.txt
exit
adb pull /sdcard/kmsg.txt
3. kernel message buffer (on request).
adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt
This was a tutorial I wrote up for my old device, users found it easier to understand then most, I cleaned this one up a bit which should be suitable for the Desire X, note, I may ask allot of question like a noob on the Q & A but HTC is so confusing.
Hopefully, users start using this so we can help out our devs, our sweet sweet devs, so they can whip u some magic.
If this helped, hit the thanks meter, no need for donations.
Hi guys
I have recently just started to learn about adb logcat and i just have a few questions hopefully you guys can help me with
1. the log buffer size 'adb logcat -g' determines how much data is stored. therefore the more i use the handset, the quciker i will loose data in the log from earlier event - thats what I believe is happening?
2. I have used 'adb logcat -b event' and 'adb logcat -b main' - are these reading the logs stored in /dev/log/ ? and if so, what is the difference?
3. When the phone is powered off, all log content is lost - so it appears?
Q&A for [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
[Request Linux GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
Click to expand...
Click to collapse
Code:
http://forum.xda-developers.com/showthread.php?t=2141817
If no one has asked for a Linux Guide - I will now ...
If the Linux Guide does exist...please pass the link...
imstanz said:
If no one has asked for a Linux Guide - I will now ...
Click to expand...
Click to collapse
You didn't specify the type of your distribution , so I make a quick set of instructions applicable for most Linux distribution with minor modification for Debian based etc etc ...
Downloading special linux SDK, Eclipse , setting sdk/tools directory to linux's $PATH with echo and export command is not required for this method to gain the basic functions of adb.
- Download the attachment and extract it inside your Desktop.
- Open terminal and change your directory to desktop :
Code:
[email protected]_name:~$ cd Desktop
Go to ADB_install and copy my file into /bin , then give it proper permissions>>
Code:
[email protected]_name:~/Desktop$ cd ADB_install
Code:
[email protected]_name:~/Desktop/ADB_install$ sudo cp adb /usr/bin
Type your password when is needed after sudo command
Code:
[email protected]_name:~/Desktop/ADB_install$ sudo chmod +x /usr/bin/adb
Phone settings > developer > USB Debugging ticked .
Connect your phone via your usb cable and type in linux terminal :
Code:
[email protected]_name:~$sudo adb devices
after initial services being established you should see something like :
i,e:
Code:
List of devices attached
0123456789ABCDEF device
ADB installed end of the story ,,
Still got issue try Disconnect and reconnect your device and also needed to run below commands on terminal for start/kill the process
adb kill-server
and afterwards
adb start-server
Hope I did help You
My Device is not Showing in CMD
Hey My Device is not Showing in CMD. When I Type "adb devices", it says: List of Connected Devices or something Like this and below of this line.. there is nothing, no Device name, or serial Number. My Device is Micromax Canvas A74. Running on 4.2 Jellybean and I want block Installing Adware on my Smartphone causing unwanted downloads and popups.
Please Help Me.
Hey guys,
Can someone with a working Kenzo give me the folders that have something about wifi, bluetooth and radio?
maybe is something missing on my phone and wifi/bt doesn't turn on.
folders that i know have something about wifi:
/data/misc/wifi
/etc/wifi
/persist
/sys/devices/soc.0/a000000.qcom,wcnss-wlan
if anybody knows more folders please tell me, i appreciate it
hed190 said:
Hey guys,
Can someone with a working Kenzo give me the folders that have something about wifi, bluetooth and radio?
maybe is something missing on my phone and wifi/bt doesn't turn on.
folders that i know have something about wifi:
/data/misc/wifi
/etc/wifi
/persist
/sys/devices/soc.0/a000000.qcom,wcnss-wlan
if anybody knows more folders please tell me, i appreciate it
Click to expand...
Click to collapse
WiFi/BT will not work if these files are missing from 'persist' root folder:
Code:
WCNSS_qcom_wlan_nv.bin
.bt_nv.bin
Anyway, you can always check the log for error messages while you turn on WiFi/BT:
Code:
adb logcat -v time > log.txt
- end with ctrl-c
- to get the radio logs only: adb logcat -b radio
k23m said:
WiFi/BT will not work if these files are missing from 'persist' root folder:
Code:
WCNSS_qcom_wlan_nv.bin
.bt_nv.bin
Anyway, you can always check the log for error messages while you turn on WiFi/BT:
Code:
adb logcat -v time > log.txt
- end with ctrl-c
- to get the radio logs only: adb logcat -b radio
Click to expand...
Click to collapse
Hey, thanks for the reply.
I have those files there...
i created a thread with an entire logcat and asking for help but no one replied... it is frustating
Thanks