For my research in gesture recognition I need to interface with Galaxy S4 touchscreen. I would like to receive "raw" data from touchscreen driver, not Android events. I must admit I am do not know much about low-level Android, although I know a bit about Linux/BSD dev., so I am not totally clueless (I hope) I was wondering if any of Android gurus can help me to get starting by answering few questions:
1. When building custom ROM, where device drivers (touchscreen in particular) come from?
2. Are they binary or source code?
3. Anybody done some reverse-engineering of digitizer API?
In particular I am interested in touch screen proximity "hovering"/"air touch" on S4. It looks like touch screen sensor on S4 could detect finger presence even when it is not yet touching the screen. Some touch screens theoretically could do this (capacity sensors) but I am curios to see what information is sent from sensor to OS and how it could be interpreted.
Hi,
I have been wondering if there is any possibility of increasing the multitouch on my u8800. Its currently on two finger touch and i am using Blefish's CM11 rom. My TS is synaptics. Can I have like 3 to 5 finger touch???
As far as I know, Synaptics TS is hard-limited to 2 points. It could be possible in hardware, but it would involve replacing the firmware on the chip. But on Atmel TS it's possible and implemented. Atmel TS has a firmware too, but it also has configuration. Configuration allows the changing of multiple parameters, including number of points tracked.
Problem installing gapps on CM11
Hi...
I have installed CM11 and until now there are no serious problems. Almost every thing works well so far.
However I have not been able to install gaps after several attempts. Is there someone who can help me to solve this problem.
Your help would be greatly appreciated.
Thanks in advance
Like the title states I need to re-calibrate my touchscreen. I flashed the incorrect update files to the HU. I've reflashed working firmware to it and Ive got android working fine now except for the touchscreen.
Now the touch screen registers touches in the opposite area of the screen from where i touch. I can connect a mouse and use the system just fine.
I cant figure out how to open recovery as of late either.
I believe its a generic an-21 u android 4.4.2 dual core 1gb ddr3
Any help would be appreciated.
I have the same problem. I changed my settings in extra settings to [up] and that seem to make the left side operate better but not the right side.
drdipshyte said:
Like the title states I need to re-calibrate my touchscreen. I flashed the incorrect update files to the HU. I've reflashed working firmware to it and Ive got android working fine now except for the touchscreen.
Now the touch screen registers touches in the opposite area of the screen from where i touch. I can connect a mouse and use the system just fine.
I cant figure out how to open recovery as of late either.
I believe its a generic an-21 u android 4.4.2 dual core 1gb ddr3
Any help would be appreciated.
Click to expand...
Click to collapse
Same problem here... Any help?
You need change touch screen digitizer
i have a question, if i wanted to swap the logic board from an a2017u with a broken display that has hardware capacitive buttons on bottom to another a2017u which the borard doesnt work on but has software buttons is that possible would the buttons matter when swapping the boards?
Well it half worked
I went ahead and gave it a shot and surprisingly it worked right off the bat, but now I do not have a navigation bar at all even if I flash the a2017u b35 SD ota it doesn't show .. But atleast the damn thing boots now yay.! I wonder tho What makes the rom enable the on screen buttons by default ? Anyone ever been in a similar situation? Its not a major issue just a annoyance having to install an app whenever I reset or switch roms to use back and home buttons
I can't answer your questions, but it's my understanding that the A2017U and A2017G have capacitive hardware buttons, but the A2017 only has software navigation buttons, which should make its' usable on-screen real estate a tad bit bigger. A2017 screen also has Force Touch, but U/G models don't.
I'm kinda surprised that your experiment didn't work, as long as the motherboard (same as logic board?) is OK then the buttons should work on both (if there is no hardware damage), I would think.
As for what enables the buttons, well, I know from experience that the first time Google setup wizard has something to do with it. I've ran into issues in the past where I couldn't complete it (it never appears) because of removing nearly all Google components. And the ROM has something to do with it too, but I'm not sure exactly how. On ROMs where GApps aren't present by default (AOSP, LineageOS, etc) it has happened too, but coincidentally only after I flashed GApps and later manually removed them. But in all cases, the menu and back buttons no longer worked, Home worked no matter what. Not sure why all 3 buttons weren't affected. A simple clean flash of the ROM was enough to fix it in every case.
I'm not a fan of GApps anyway, I prefer the open source MicroG as a drop-in replacement for Play Services.
AnonVendetta said:
I can't answer your questions, but it's my understanding that the A2017U and A2017G have capacitive hardware buttons, but the A2017 only has software navigation buttons, which should make its' usable on-screen real estate a tad bit bigger. A2017 screen also has Force Touch, but U/G models don't.
I'm kinda surprised that your experiment didn't work, as long as the motherboard (same as logic board?) is OK then the buttons should work on both (if there is no hardware damage), I would think.
As for what enables the buttons, well, I know from experience that the first time Google setup wizard has something to do with it. I've ran into issues in the past where I couldn't complete it (it never appears) because of removing nearly all Google components. And the ROM has something to do with it too, but I'm not sure exactly how. On ROMs where GApps aren't present by default (AOSP, LineageOS, etc) it has happened too, but coincidentally only after I flashed GApps and later manually removed them. But in all cases, the menu and back buttons no longer worked, Home worked no matter what. Not sure why all 3 buttons weren't affected. A simple clean flash of the ROM was enough to fix it in every case.
I'm not a fan of GApps anyway, I prefer the open source MicroG as a drop-in replacement for Play Services.
Click to expand...
Click to collapse
so just for clarity, i took the motherboard from a clean never modified a2017u that did have hardware buttons on the display but broken screen . put it in my other a2017u that does not have hardware navigation keys. its software only but same model as other device, which i find odd because the boards were pretty much the same . i too thought it would do what you said,and just appear sometime at beginning of rom setup. well they do not show up at all and i still have yet to unlock bootloader and try a custom rom or root the device.
TLDR: so i flashed the ota package of stock b35 after i put the clean motherboard in thinking that it would make the bar appear on setup but nothing no navigation keys appear at anytime unless i install an app from playstore idk if this info is usefull to anyone but i am just going to root and install lineage to get a working bar welll hopefullly all goes well .
AnonVendetta said:
I can't answer your questions, but it's my understanding that the A2017U and A2017G have capacitive hardware buttons, but the A2017 only has software navigation buttons, which should make its' usable on-screen real estate a tad bit bigger. A2017 screen also has Force Touch, but U/G models don't.
Click to expand...
Click to collapse
not entirely right though. The first batches of A2017's didn't have capacitive buttons, then after some time they started coming with them. and the screen/digitizer are the same on all 3, they are interchangeable in fact, but the enhanced editions (which have the same model name actually) are the ones that have force touch.
In English: Many A2017's have capacitive buttons, if not most (I recall seeing reports of A2017s carrying the buttons when I bought my phone, Feb 2017). The ones with Force touch are the A2017 and A2017U Enhanced (6GB/128GB). There are also A2017 and A2017U 4/128 GB, those don't have force touch. And G's only come in 4/64, ofc no force touch.
Plus the A2017 without capacitive buttons has the exact same screen. It just has a black bar where the buttons would be. That's where the screen chip goes, you can't just get rid of that bezel without pulling an Apple.
It looks fugly... You have an empty black bar and THEN the capacitive buttons above it. It's like 2 cm of bezel
I've had a frustrating issue with my Sony X Compact for past months. Whereas before the touchscreen worked flawlessly, I'm now having trouble getting taps and swipes registered near the edge of the screen. For example, when I try to tap the first and last letters of the center row in my keyboard, it usually takes quite a few (more aggressive) taps to get them to register. If I use a light tap that would register elsewhere, nothing happens. Moreover, I sometimes have trouble swiping the Quick Settings Tile open. The weird thing is... When I do the Sony Support Touchscreen Test, I get zero issues and even with a light touch can clear the screen near the edges.
Now I've gone through the usual culprits... I've tried a bunch of different keyboards (currently using either 1C or SwiftKey). I've tried different launchers including the Sony one (currently using Nova Launcher). I've made sure I'm up-to-date in everything. I've try to adjust the Pointer Speed (Language and Keyboard menu). I've even tried a touchscreen calibration app. Nothing works. I've also booted to Safe Mode and made sure the issue persists there (it does). I haven't dropped my phone and am actually using a case and a glass protector to protect the screen (which is in mint condition). Oh and yes, I have made sure that the problem persists without the case and the screen protector.
I've done a bit of research and apparently many Sony owners have had similar issues and not just with the X Compact. Many link this issue to Oreo and I do have to agree that I didn't have any issues with the previous Android version. Apparently many have complained for months and Sony has given zero f... ixes.
Any ideas or advise? I can live with this issue for now (although typing is at times annoying) as I plan to upgrade to either XZ2 Compact (if good enough deal arrives) or to its successor next year. Should I try to revert back to previous Android version or maybe try a custom OS? I do have some warranty still left although I'm not sure if they'll take this issue seriously.