lcd touch screen app executer brands

A widget is a software application embedded in the Equinox device that controls and communicates with the equipment for that widget. Widgets allow for intuitive system navigation and control by users. They also provide the power for personalization, allowing users to adapt the system to their changing living environment. Equinox widgets are the very efficient means that allow integrators to program intuitive control for complex requirements.

With the shade widget, gain complete control and visibility of all automated window shading systems on the project. On the shade widget dashboard, users can quickly see which shades are open or closed and adjust the position of the current shade group. There are also up to four presets available that can be activated from this main screen. Define presets on the second or “full screen level.” These presets are shared across all profiles and are tied directly to the shade group. Edit any shade preset level on Equinox 73 or a mobile tablet.

At the full screen level, there are two view types. By default, users will see and be able to manage the individual shades of the current group. Then, swipe to see the shade overview page where users can see the status of all the shade groups and then open or close the shades in a project.

At the full screen level, there are two view types. By default, users will see and be able to manage the next instance of all scheduled events in a scrollable list. Then swipe to see the timers page for the current profile. This shows daily, weekly, monthly, and other types of timers as well as the time of the day they are scheduled to execute.

At the full screen level, lists of lights by floor and by room can be viewed; swipe side to side to see more floors or up and down to show more rooms. See what lights are on or off, turn individual, room, or floor lights on or off, and raise or lower dimmable lighting loads.

The RPi LCD can be driven in two ways: Method 1. install driver to your Raspbian OS. Method 2. use the Ready-to-use image file of which LCD driver was pre-installed.

3) Connect the TF card to the Raspberry Pi, start the Raspberry Pi. The LCD will display after booting up, and then log in to the Raspberry Pi terminal,(You may need to connect a keyboard and HDMI LCD to Pi for driver installing, or log in remotely with SSH)

1. Executing apt-get upgrade will cause the LCD to fail to work properly. In this case, you need to edit the config.txt file in the SD card and delete this sentence: dtoverlay=ads7846.

This LCD can be calibrated through the xinput-calibrator program. Note: The Raspberry Pi must be connected to the network, or else the program won"t be successfully installed.

Raspberry Pi leads out 40 GPIO pins, while the screen leads out 26 pins. When connecting, pay attention to the corresponding pins and Raspberry Pi pins.

5) Insert the TF card into the Raspberry Pi, power on the Raspberry Pi, and wait for more than 10 seconds to display normally. But the touch is abnormal at that time, and the touch needs to be calibrated as the following steps.

3. After reboot, touch will work normally under normal circumstances. But for different resistance screens, the accuracy of using the default calibration parameters may not be very suitable.

You can perform touch calibration by clicking the Raspberry Pi icon on the taskbar, selecting Preferences -> Calibrate Touchscreen, and following the displayed prompts.

4. After calibration, the following data will be displayed. If you want to save these touch values, you can replace the data in the red circle with the data in the corresponding position in 99-calibration.conf.

Power: turn on/off the back light. If you needn"t use the LCD for a long time, you can turn off the back light with this button to reduce the comsuption

The installation of xserver-xorg-input-evdev and xinput-calibrator in Ubuntu system reports an error, so the touch cannot be used normally. How to solve it?

The installation of xserver-xorg-input-evdev and xinput-calibrator in Kali system reports an error, so the touch cannot be used normally. How to solve it?

Since the first-generation Raspberry Pi released, Waveshare has been working on designing, developing, and producing various fantastic touch LCDs for the Pi. Unfortunately, there are quite a few pirated/knock-off products in the market. They"re usually some poor copies of our early hardware revisions, and comes with none support service.

Thanks for bringing this to my attention. It appears that the upgrade package overwrites the FBTFT drivers, in particular, the Raspberry Pi bootloader. This seems to solve the problem:

Hello..I tired to interface this lcd “https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/32-TOUCH-DISPLAY-RASPBERRY-PI” to my Raspberry pi model B+.I got a DVD containing image for LCD in the package.I burned it to the SD card and plugged in the display.But my lcd is completly blank.But green inidcation led (ACT LED) in board is blinking.Why my LCD is Blank ?

If you have tried using the manufacturers image and the screen doesn’t work, it could be that the screen has a hardware malfunction. If the process above doesn’t work either, I would contact the manufacturer

Is your RED (POWER) LED on? I had the same problem. Green Led was blinking and screen was white. Then I noticed RED Led is off, indicating there’s something wrong with the power. I plugged into different port and it started

Yes, it may be that the screen isn’t supported. Newer screens might not have drivers yet. I do know it is possible to make your own driver but that’s above my level of knowledge :)

My Touchscreen is now working fine.The problem was for the ribbon cable on the back side of LCD.It was not connected properly.I just tighted the cable and it worked fine.Hope it will be useful tip.

Thank you for this great tutorial. I looked everywhere for this information. I have an eleduino 3.5 version A. I was able to get it working on my Pi 2 by following your tutorial and using flexfb as the screen type. I got the other settings from the image that came with the product. I did find that the ts_calibrate didn’t recognize the screen so I installed xinput-calibrator and it worked fine.

Just got my Pi2 running Wheezy, working with the Eleduino 3.5 LCD without running the OEMs image… kinda. I didn’t want to rebuild the application environment again, so was avoiding flashing the SD.

I tried the steps in this tutorial. It’s very clear and easy to follow, thank you. But it didn’t work for me, I tried setting my device to flexfb. Only got white screen.

thank you for your great tutorial, it got me on the right way. unfortunataly i only see some boot messages on the lcd and then it turns black. maybe you could give me a hint on how to get it working entirely.

Did you check to see if your device is supported yet? The device name should be specific for your screen, as listed in the fbtft file linked to in the beginning of the post

I too have a raspberry pi 2, and a waveshare spotpear 3.2 RPi lcd (v3) and I just can’t get it to work! I suspect I have a faulty LCD, but thought I’ll try this forum for help before I sent it back.

Soon as the pi is powered, the LCD lights up all white, with a few vertical pixels coloured at one of the edges, and nothing else. I don’t think that should happen – not at least before the BOIS has started up.

Anyway, point 1, says to change to dev/fb1 – I don’t have fb1. Only fb0 appears to be there. is that a clue what could be wrong? I have enabled SPI (is there a command to tell if its enabled?) I have also ran spidev to troubleshot (though I haven’t a clue what I means)

It seems all appears to be working – just the LCD is still all white with a single line of coloured pixels on edge) and nothing else. Is there a way to output, like jeff G script, of touch points?

I had the same one, I finally found a driver for it here: http://www.waveshare.net/wiki/3.2inch_RPi_LCD_(B) you will need to translate the page, but unpack the driver then run sudo ./LCD-show/LCD32-show. It should reboot and all will be good with the screen :)

Can anyone let me know if the default OS image sent with the screen works with pi2 or just Pi B/B+ as i think my screen maybe broken but can’t confirm it yet as i have not had it working at all

My system: Raspberry Pi 2 Model B with Raspian Wheezy from Febuary 2015. LCD display of Sainsmart 3.2 http://www.conrad.de/ce/de/product/1283498/Raspberry-Pi-Display-Modul-Touch-Display-81-cm-32/?ref=home&rt=home&rb=1

The LCD display shows the raspberry correctly. However, the touch screen input does not work. The mouse pointer can I move correctly with your finger, but I can not select things (function of the left mouse button).

Can someone upload SD card image that works with RBP2 ? My idea is to use Eleduino TFT as additional screen and play movies via HDMI.. is it possible?

Do not follow this article when you don’t know what kind of LCD module. In my case, I follow all of this and my raspberry pi cannot boot anymore. I will try to recover, but I think I should format my SD card and reinstall OS.

Expecting this would builtin driver module within kernel and help with avoiding mistakenly overwriting anything. But with this is cause LCD screen to go blank white and no boot activity. Also noticed on HDMI it get stuck on Initial rainbow screen and stuck on that.

Also can you someone explain what exactly happen when do rpi-update? Want to understand what this step actualy doing and help me to debug any such situation and able to help others.

Does anyone tried splash boot screen with waveshare v4 LCD and Rpi2? I tried to follow some example from https://github.com/notro/fbtft/wiki/Bootsplash but no success.

Great tutorial thanks; got an X session working great 1st time. Has anybody managed to get Kodi/XMBC working on the LCD either Kodi standalone, Raspbmc or Xbian?

After following this tut to the letter on a brand new image of Raspian, I find that the touch driver does not function. Anyone experience the same? Basically all I did was image a current copy of rasping, did a apt-get upgrade, and then did this tutorial. Then the touch driver does not work, meaning the pointer does not respond.

The reason I did this was because on a production version of my system I added the 3.2 screen and it worked great except for the x-axis. So I wanted to see if there was something in my system that was interfering or if this is another error. Now with a raw rasping the driver does not work at all. I wonder if the touch pin has changed since the kernel is using BCM pins instead of GPIO pin numbers?

I have exactly the same problem. I also installed a new version of Raspbian, and the LCD part works fine (except all the windows are way too large), but the touch part doesn’t work at all… I’m using Waveshare Spotpear 3.2″ V4.

I remember that I plugged in the screen wrongly one time, before configuring any of the GPIO pins. Can this have damaged the screen? Still it’s weird that the display part works well and the touch part not at all.

Touch actually goes through one of the SPI pins I think. Either the driver is toast with the required kernel update or the driver is using the wrong pin. It is very likely the this works well with previous raspian versions, but not with the new B+ and with the new kernel.

I am trying to use the sainsmart 2.8″ lcd sold through microcenter, using the sainsmart32_spi … seems to have the same pinouts, should I be able to get this to work? I am stuck at the white out screen on the lcd, doesn’t seem to recognize the module either.

Unfortunately I’ve tried that ( a few times actually) but the file still doesn’t exist. Thanks very much for the assistance anyway. I must be doing something wrong. My Raspian came from a Noobs installation, I’m wondering if I should try installing the OS from somewhere else. My LCD screen didn’t come with a CD or any docs so I’m completely in the dark here.

I have just found a way to get this file on my system! Apparently its part of the fbturbo installation. I found it here http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=45746&start=75 (under experimental enhanced x driver (rpifb).. Sorry if this is obvious to everyone but I am SUCH a noob at this!!

I have the waveshare 3.5 and what to use it only as a secondary screen by putting measurement data with a c program on the screen. Is there any solution?

Ok, what am I doing wrong. I am using a fresh install of the newest raspbian, on a Pi 2. After doing the first two steps and rebooting I get the rainbow screen, then the boot up process, and then my screen just goes black with a flashing cursor in the top left. I am not able to enter any commands or anything…like the pi is halting just after boot up. Any thoughts/suggestions would be greatly appreciated. Thanks.

Well figured out that step 1 was causing my problems. I’m guessing it is shutting off my hdmi feed and trying to switch it over to the SPI, am I guessing right? If so, not sure how I’m suppose to complete the rest of the steps if my hdmi output gets turned off before the LCD is actually set up to work…that sounds kind of smartass-like, which is not my intention, just looking for some clarification on what is going on in that first step as I am fairly new to this stuff. Thanks.

Anyway, I was able to do the rest of the steps with no problem. LCD didn’t work, but I am using a Waveshare 3.5, which doesn’t look to be supported yet. Mostly I am trying to play around and see if I can get it working somehow. Anyone found a way to do this yet?

Here is a link to an updated image from waveshare. Upon install it got the display up and running, but I still do not have touch functionality. I’ve been playing around with it, but it has been to no avail…hopefully someone better at this stuff from me can get the touch working.

I am having an issue with getting the GUI back. Every time I use startx my pi just sits there for about two minutes saying “No protocol specified”, and then it just gives up. I went through this tutorial about four times now and am not certain why it is doing this. I have the exact same LCD as is in the tutotial (WaveShare 3.2b). any help would be great.

Hi I am making a project for school,using the raspberry pi b+ and waveshare spotpare 3.2b. Everything works except the touch input doesn’t work. Any help would be appreciated very much.

Thanks for the tutorial. It works, but I get the boot/command line stuff on the HDMI monitor and the LCD only comes on when I do startx. Is there a way to get everything to appear on the LCD screen?

I am trying to get this same screen to work with the image of RetroPie 2.6 and it won’t work. I have followed all the steps and nothing, please help I an kinda a noob.

I have a Tontec 7 inch touchscreen with a Raspberry Pi 2 B. After following the instructions the touch screen is functioning but not properly… The only are that works is the upper left (and only a small area of that). I tried changing the width and height in the modules but it didnt change anything. Also the xy seems to be reversed, I changed the swap_xy to 1 but again no change on the screen.

Now the OS freezes at the emulation station loading screen, and if I connect my lcd it gives me a lot of error messages which I can only see on the 3.2 inch screen.

hi i have the same screen with a raspberry pi 2 im trying to run retro pie but it wont show ..however it shows all the commands …but i cant get it to show the gui …if u guys can make an image or something please i have been in this pain for two weeks already thank you

Damn.. I thought I was kickin ass haha. I am using the SainSmart 3.2″.. the backlight is lit up and the pi was booting and everything just fine but on the final reboot it gets hung and says “nonblocking pool is initialized” ?? No idea what that means. But it’s def just frozen at this point.. on my main screen, and just the backlight is on the SainSmart.

This was an excellent tutorial. I have gotten an output to the screen, but no touchscreen usage . I have the Waveshare SpotPear 3.2 Inch LCD V4 screen, but using Raspberry PI 2 with wheezy. Any ideas?

Thanks a lot for this article. Very clear and easy . I am new in pi’s world and my 3.2″ screen is working fine. I rotate 90 º and works. I can use mouse and so on.Not problems.

I filed the steps to calibrate the screen but it did not work.I think because it did not find the TFT pin, because I think the touch problem is the assigned pin to control it changed.

I actually used the driver from here http://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) , from a new wheezy build, did nothing except enable SPI in config, install driver, and change mmcblk0p2 to mmcblk0p6 in cmdline.txt and it all worked, no drama.

Hi I managed to set up my touch screen ok but I now have the issue that everything desktop fits fine but the windows I open are all huge and I can’t remember how to change the size and cannot see the option in desktop preferences any idea what I have to do and is it at all possible to install kodi to run through the raspbian is as this would be a lot my useful than having to keep swapping os on every boot up many thanks in advanced hope you can help me

Advice to all who have the drivers from the (touch)screen manufacturer and cannot obtain those otherwise: you can skip everything and go to the update steps skipping the kernel and kernel modules update (as mentioned by the author) so that you don’t override the preinstalled drivers. I have a Waveshare 3.5″ RPi v3 (not the 3.2″ supported by notro’s drivers) and actually managed without any problems to get notro’s drivers make it work. However I am still reading about the xinput and xinput-calibrator to figure out how to include it as a kernel module so that I can compile my own kernel and add it there.

i have raspberry pi 2 with 3.2 inch rpi lcd v4 waveshare spotpear.i have done as per your instructions.the display is working but touch screen not working.error shows waveshare32b module not found as well as touch screen module not found messages.

Unfortunately I have lost the Touch facility on my Waveshare 3.5″ LCD Touchscreen? Can you offer any reasons as to why? I copied the Raspbian image to my Raspberry Pi from the Waveshare website first of all. The Touchscreen displays but is not reactive with any touch

Hi great article thanks. I am trying to get a waveshare 7 inch LCD with capacitive touch running it works with the suppled image but if you upgrade it breaks the capacitive touch. I have a sense-hat and GPS which require the latest kernel and RASPIAN image and the install program for the screen replaces the /lib/modules directory and the kernel with older ones. I need to be able to install the touch drivers into a new clean OS can anyone give me some pointers? Thanks

I should add that the screen is plugged into the HDMI port and always works. The capacitive touch is driven from the USB port which also supplies power.

For anyone who have those unbranded cheap TFT touch modules and cannot get it to work with this guide, I had success on my 3.5″ with the following steps: http://pastebin.com/89qmFbPB

So I have the original image that came with my screen and it works fine with the LCD but my problem is that I want to use my LCD screen with other distros (at this time I am trying to use it with Kali Linux with TFT support by default https://www.offensive-security.com/kali-linux-vmware-arm-image-download/) What do I have to do to transfer the needed files from the original image that WORKS with the screen and use them with another image?

I originally bought this bundle http://www.amazon.com/gp/product/B013E0IJUK?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00 with an RPi LCD V3 and no extra documentation on the specifics on the chipset. I tried with the bftft drivers but since I have no idea what to call this screen I just suppose it isn’t supported.

After 4 lost days I just decided to get another screen, a Waveshare 3.2 (just like the one on this tutorial), I’ll follow these steps and see if it work for me.

I’ve followed your instructions and am only getting a white screen stil. I am using the Osoyoo 3.5 inch touchscreen from Amazon. http://www.amazon.com/gp/product/B013E0IJVE?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

I’m not sure if the Jessie kernel is compatible – can anyone please confirm or not ?? Adafruit states that their setup for TFT screens are Wheezy only ; is this a different setup ??

I am using the same LCD and followed your tutorial. Have your tested the guide lately? Are you certain that it works? I see the boot messages on console but I get white screen as GUI starts.

After I rebooted in step 3, my raspberry pi won’t boot up again. It goes thru the process of booting and the text scrolls down and every thing says “ok”. Then instead of going to GUI it just guys to a black screen on my monitor with a blinking underscore in the top left corner. Anyway to get around this? or should I start over with a fresh disk image??

That is what happens to mine also.. So long story short —> THIS SITE NEEDS TO BE UPDATED OR SHUT DOWN <— There are a hundred people on here that have all lost everything on the pi drive, and spent all day (or more) working thru this tutorial 4 or 5 (dozen) times and nothing. Just have to reinstall the os over again and again.

I have tried to set up waveshare 32b on my Pi B using the latest Raspian download. I learned a lot in the process using Windows Putty, Nano etc. I have repeated the setup process several times from scratch and included the corrections for possible overwriting. My Waveshare SpotPear 3.2 inch RPi LCD V4 just shows a white screen. Any suggestions?

I’d suggest that you use the included installation disk to make a clean install on another SD card to see if the screen itself works fine or not, then try to repeat the process of installation after upgrading

There was no disk included. I asked for drivers and was given a download link to the image file. After down loading this I tried it and still got just a white screen. The HDMI monitor locks partway though the boot. I can still log in to pi using putty from my PC.

This process worked for me except for two things. The screen only shows 25* of any page so the most important buttons are inaccessible, and now the Wifi does not work and cannot be activated where it worked fine before the reboot. Any suggestions?

Hi, I am using raspberry pi 2 with raspbian jessie installed. I the waveshare spotpear 3.2 v4. The above instructions are not working. and after completing the steps there was no display from hdmi or lcd. One things to notify is.: the etc/modules files only had i2c-dev and not snd-bcm2835.

I am trying to get this to work with Retro Pie 3.3.1 and the Waveshare3.2″ v4 but I only get the terminal on the lcd and emulation station starts on hdmi. to get it working with retro pie i just replaced startx with emulationstation. how do i get this to work?

Sir, Your post has very useful to me. i am using Tinylcd. but i cant get display. i am performing all the steps in your post. i cant get touch controller information from the product website and also i am using RASPberryPi B+ model. could u please give me best solution to my work. Than you.

Hi, what if you dont know the make of your screen, i purchased via Ebay, and it is unbranded, the contact speaks barely any English and keeps linking me to a custom kernal download.

I completed all steps except for the last one (I want it to boot to console). However, when I reboot, it never completes the boot process. I start in recovery mode and check the cmdline.txt file and it is exactly how it appears on this page. I copied the kernel info as well, but I am not sure if it correct as I cannot get to it to check. Any suggestions? I might just reinstall the OS and start over…

i installed android OS in raspberry pi 2. can i use same LCD touch screen set up for android installed raspberry pi 2 which you are used for raspbian.

Is it normal the white back light during the whole process of initializing (I suspect that during the transportation trere is a deffect)? The problem is that I missed the step #1 and I performed it at the end. Unfortunately I don’t have any monitor available right now – neither “normal”, neither LCD :))))). Is it possible turning back the system or the only option is reinstallation of the Raspbian?

I’m trying to use an original Raspberry Pi model B with a cheap 3.5 inch 320×480 LCD which allegedly was manufactured to work with the Pi and has the correct fittings to fit over the GPIO pins. The operating system is the latest, downloaded yesterday and installed with NOOBS. I can’t get past step 2 of this guidance. When I reboot after using raspi-config I can see text generated as the Pi boots, then the HDMI fed screen goes blank apart from a flashing cursor in the top left hand corner. The LCD just remains white with nothing else on it. I have missed out step 1 and rebooted after step 2 and the screen functions as I would expect. Does anyone have any ideas please?

now when it seem WaveShare release their own custom image or sources, same thing happens kernel panic. unfortunately this time around doing the same trick doesn’t save the day !

Thanks for the great tutorial. I do have a question. Once you install the drivers for the lcd are you effectively disabiling the hdmi port or is it still available to use and will the pi function with both displays. I have a pi 3

once you install the drivers it replaces the kernel by disabling hdmi output and enables it for LCD. i don’t think we have a solution to get em both working at the same time. ( you are encouraged to search for it )

Thanks for the guide, have been doing this with my son but once we leave raspi config and reboot all we get is a black screen with a flashing white horizontal line (dash). Can you help? I have looked in the comments at the end of the article but no one else appears to have this issue.

I have a raspberry pi 2 with waveshare screenn 3.5 inches. Isn’t it the same instructions. But it isnt working, all i get is a white screen, and the red led on the pi is on. The green LED isnot working.

My Rpi3 gets “ERROR: could not insert ‘spi_bcm2708’: No such device” after I enable SPI in the raspi-config.My Rpi3 is freezing on the rainbow screen after I reboot at the end of step 3. I’ve tried adding boot_delay=1 to config.txt.

if any interested, now i have a raspian image working on raspberry 3 with Waveshare 3.5, also with sdr support for dongles and FreqShow working perfectly on touch

I tried following your tutorial but I got stuck right at the first step… I enter sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf the whole screen is blank except for the command list at the bottom…

I’d like to find the driver software for my 7″ LCD with touch (official Pi unit) so that I can use it in buildroot. I wanted to make sure this kernel is the one before I started digging further.

Every time I reboot after step 3 I get the rainbow screen of death (lost the kernel) and have to reimage my card and start over. Anybody had this happen and have a solution?

I started through your tutorial and completed step 3 and rebooted. After the Raspberry screen and some of the boot text on my HDMI monitor, I now have a black HDMI monitor and a white screen on my LCD. Does this mean that the bootloader was overwritten or something else is wrong? How am I supposed to enter in the proposed fixes to the bootloader, when I can’t get the RPi to boot? Do I have to interrupt the boot process at some point to reinstall the bootloader or what?

Its a script. Download and instead of running sudo ./LCD4-show run cat ./LCD4-show to simply display what it does without actually running it. The commands are fairly simple modifying a few files. I actually saved the LCD-show.tar.gz on my own server for faster future download but also for backup as it saved me tons of hours (if that’s a measuring unit for time :) )

I used this link though (smaller file ~ 50 KB, fast download) http://www.waveshare.com/w/upload/4/4b/LCD-show-161112.tar.gz and replaced LCD4-show with LCD32-show in the last line.

I’m using RasPi Zero with latest (as of last week) Jessie Raspbian. Did you run the script? If it didn’t work and you have modified other files in the process of making it work, I would recommend installing a fresh installed image on a new card and running the script. Can you suspect the screen being faulty or got “burned” in the process?

i bought a 3.5 inch tft lcd screen from banggood. and i have installed raspian jessie, the latest version, in my sd card. but when i power on my Pi, only a white backlit screen comes. there are no images or graphics whatsoever.

Of course. Raspbian Jessie does not come with the drivers needed to talk to the screen. See my previous comment (September 22, 2016 at 11:54 am) and follow it.

I have done every thing right but the only major problem is that the screen is still white and my raspberrypi freezes after a line of code when booting up and I cant get in with SSH

Will your system work with my SainSmart 2.8″ 2.8 inch TFT LCD 240×320 Arduino DUE MEGA2560 R3 Raspberry Pi ? I would like to know before not be able to back out. Thanks, Lee

I know I will end up regretting this, but how do I change fb0 to fb1? I’m on the screen that has all the info, but no way to change it. Am I looking for a file? I have had my screen for MONTHS and I can’t do anything with my pi or the screen. I am >< close to smashing both. COMPLETE WASTE OF MONEY so far!!

hello. I really appreciate your blog post. I have a raspberry pi 3 B. I have been unable to get my waveshare 3.2 screen to work.I am at a complete loss for what to do. I do step 2 I change fb0 to fb1 and then follow your directions I don’t get the prompt to reboot; however, I do it manually with sudo reboot. that works fine then I complete step three and that works just fine; however once I reboot from getting those drivers and when I attempt to reboot it is unsuccessful and then my whole raspberry pi will not restart. then when I power it back on it will just shut back off. I then have to redo noobs onto a new SD card I would GREATLY appreciate anyones help

I ‘m actually using a LCD Waveshare3.2” , I followed your steps to setup the lcd touchscreen for my rpi and it work but I have a problem with the resolution because if I open a repertory I do not see the whole contents on the screen .

hi! thank you for this post…. I was wondering if all the raspberry pi’s gpio are being held by this screen or do we have any of those availables for use??

it worked. but the resolution is for bigger screens. i got the menubar small, but the rest appears too big , and out of screen. the wastebasket icon is 1/6 of my 3.2″ screen. wich HAS the resolution capability too display the whole desktop. But i’m a PI newby and dunno how to adjust the screen resolution on this display. anybody?

hey Thanks for this good post …I have capacitive touchscreen which i brought from the link below..can you guide how i can configure the kernel modules…It will be very helpful for me…Thanks

hey Thanks for this good post …I have capacitive touchscreen which i brought from the link below..can you guide how i can configure the kernel modules…It will be very helpful for me…Thanks

I did a 5inch LCD for my raspberry pi. I dont use the touchscreen so i didnt have to install any drivers. It works out of the box but doesnt cover the whole screen unless you open the terminal and do:

HI I have my RPI running Pi Presents on a view sonic TD2230 Touchscreen. It all works fine, touching the click areas can navigate you thru my presentation, The problem arises when you use multitouch gestures like you would on a iPhone. Pinch or expand etc… and then all touch ability goes away. I can still control the presentation via a mouse, but I don’t get touch control back until I either relaunch Pi Presents, or if I unplug and plug the usb cable going to the touchscreen.

Could you provide me with a os image of open elec that you already built for the waveshare spotpear v4 3.2 inch touchscreen,because I cannot make sense of your website’s instructions?

In the case of the WaveShare driver, their setup script from their “LCD_show” repository will copy a device-tree overlay to /boot/overlays/ that provides most of the module config etc via boot-time device-tree patch.

​​​Google has dropped the support for "less secure apps" and no longer supports the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password.

From now on an "App Password" is required when sending emails from iX panels that are configured to use Gmail"s SMTP servers. Please notice that 2 step verification is required in order to create an app password.

To get the NS ( namespace ) settings in IX developer correctly, the easiest way is to browse the Phoenix server from IX developer, by clicking the small down arrow at the right side of the "ADD" button in Tags, and select "Add tags from OPC server" . Then the nemespaces are set automaticly. Otherwise you can see them in the screenshot below:

When utilizing TFT LCD HMI panels in applications where a fixed or partially fixed image remains displayed on the screen for extended periods of time, users may experience a phenomenon referred to by the LCD industry as Image Sticking. Image Sticking - sometimes also called "image retention" or "ghosting"- is a phenomenon where a faint outline of a previously displayed image remains visible on the screen when the image is changed.

Direct Replacement Path (EXTER panels) - A direct mechanical drop-in hardware replacement is available for most E1000 products. The replacement products use your existing E-Designer applications after a simple project conversion to Information Designersoftware, a service offered by Beijer Technical Support

Add the specific Security groups that you need to use in your project. These may be the same as the domain groups or may be mapped in the script later (see "ADJUST HERE" in LoginScreen script).

NB: Even though the help file suggests another key combination, please note that Ctrl-Alt-Shift-F toggles Full screen mode on / off best, so you Restore from Fullscreen mode with this key combination! vncviewer.exe_patch.zip contains a patched vncviewer.exe

The script extract the number part 0,1,2 etc to a global tag, to be used as a page index in the PDF viewer object.  Finally the Popup screen is opened.

Custom Welcome screen is supported on X2 base v2 and X2 pro/marine/control/extreme. Currently only X2 base v2 and X2 extreme support customization using this .cfg file and this require the latest versions of the system programs (X2 base V2 v1.02 b280 | X2 extreme v2.1 b430).

This application note is part 2 of our 2 part TFT LCD screen series. Part 1 discusses configuring the screen resolution of a TFT with a Raspberry Pi. Part 2 discusses calibrating the touch screen of a TFT. Click here to read part 1.

After the display is setup with the Raspberry Pi you may want to calibrate the touch feature for accuracy. The display used in this example is a 7” TFT with capacitive touch (E70RA-HW520-C). This is a continuation of a previous application with the same display. The touch feature is auto enabled upon download of the Raspbian software; however, it may be inconsistent with actual motion. Calibrating the touch feature of a display can be done in just a few simple steps.

Next, we find the program that calibrates the display. There are a few options of programs that calibrate the touch setting, the one I will be using is called ts_lib. We can install this through the Terminal. Root privileges will need to be enabled to install the program that is used. Enable super user mode by entering:

This will install a configuration file for the touch screen. Before the test we need to specify which device we’re using and where it is located. The display is located at “event0” as verified in the previous step. This could be a different value for you depending on the setup so be sure to refer to the results of step one. Enter the following commands to define the display variables.

Now we can run the calibration test. To do this enter the ts_calibrate command in the Terminal. You will need to be in super user mode for the calibration test to run. A screen will pop up asking you to touch five different points on the screen, try to touch them as accurately as possible. After the test is finished a list of the results will be displayed in the Terminal.

The touch screen should now be configured to a precise setting. This is just a brief overview of how to calibrate the capacitive touch feature of a display. For further calibration settings you can visit the “ts.config” file. You can open this file from Terminal by entering:

Buyers and others who are developing systems that incorporate FocusLCDs products (collectively, “Designers”) understand and agree that Designers remain responsible for using their independent analysis, evaluation and judgment in designing their applications and that Designers have full and exclusive responsibility to assure the safety of Designers" applications and compliance of their applications (and of all FocusLCDs products used in or for Designers’ applications) with all applicable regulations, laws and other applicable requirements.

Designer agrees that prior to using or distributing any applications that include FocusLCDs products, Designer will thoroughly test such applications and the functionality of such FocusLCDs products as used in such applications.

I"ve moved up 3 phone models since using this, an A21, A42, now a Samsung Z Fold 4. This app still works wonderfully! I don"t get noticeable lag, however after running this I notice a differece. I tap (or swipe) with one finger, but crazy fast with a light touch. I run this once a month or so, then it always feels better, smoother, and even quicker. I wouldn"t say this is a "last resort" app, but a great maintenance app. Kudos! Been using a while now, very happy! (only a 5 second ad at end too!)

Searching for the best TFT LCD module manufacturers in India? Well, that is admittedly a daunting task. With the growing number of TFT LCD display suppliers and manufacturers, it’s truly hard to pick which ones are reputable and which ones are not.

STONE Technologies is a proud manufacturer of superior quality TFT LCD modules and LCD screens. The company also provides intelligent HMI solutions that perfectly fit in with its excellent hardware offerings.

STONE TFT LCD modules come with a microcontroller unit that has a 1GHz Cortex-A8 CPU. Such a module can easily be transformed into an HMI screen. Simple hexadecimal instructions can be used to control the module through the UART port. Furthermore, you can seamlessly develop STONE TFT LCD color user interface modules and add touch control, features to it.

Becoming a reputable TFT LCD manufacturer is no piece of cake. It requires a company to pay attention to detail, have excellent manufacturing processes, the right TFT display technology, and a consumer’s mindset.

Hence, we’ve rounded up 7 famous and reputable Indian LCD module manufacturers. These companies all produce quality display and screen-related products such as:

Videocon Industries Ltd is a well-known Indian manufacturer of TFT display modules, color TVs, home appliances, and consumer electronics. Videocon is a large company based in Mumbai, India.

Videocon is popular for its high-quality products. Videocon manufactures an LCD display screen for LCD TV sets. A lot of Indians trust Videocon’s television sets.

Videocon assembles and manufactures their TFT LCD module products in world-class factories. The company’s main factories are in India. However, they also have manufacturing plants in Mainland China, Mexico, Poland, and Italy.

All of Videocon’s TFT LCD display products passed strict quality control checks. Testing is done throughout the entire manufacturing and assembly process. Furthermore, quality checks are done from the raw materials phase until the products’ release.

Videocon’s TFT display screens and TVs are affordable of good quality. The company knows how to manufacture quality TV sets at pocket-friendly prices since it is a pioneer in the Indian color TV industry.

Videocon’s mobile phone range is equipped with the latest touch LCD display technology. Smartphones are assembled in the company’s TFT touch screen factory. Hence, customers are ensured of high-performance mobile phones with a crisp touch screen LCD display.

To sum it up, Videocon Industries Limited is a strong TFT LCD display manufacturer. The company’s quality manufacturing plants, good end-products, and affordable prices make it among the famous TF LCD manufacturers in India.

Teronix is an Indian electronics company based in New Delhi. It specializes in TV sets with LED and LCD screen module technology. The company also offers a range of smart mobiles and power banks.

Teronix has been in the electronics industry since 2017. But the company has proven that it has what it takes to be a reputable LCD manufacturer in India. Teronix has risen to popularity among Indian consumers because of the following qualities:

The company’s products are all high-quality and durable. Teronix sees to it that its range of smart LCD and LED TVs, along with their other products, reach their customers in good condition, and perform at their best all the time.

Teronix knows that good quality LCD module and other electronic parts are the cores of high-performance products. Hence, their assembly and product research units are stocked with the latest technology to produce the best possible products. Furthermore, Teronix’s research and assembly hubs are strategically located in Delhi.

The company started manufacturing televisions and telecom equipment in the 1980s. BPL joined forces with Japanese company Sanyo in 2006 to strengthen BPL’s consumer electronics brand, including TF-LCD display products and color televisions. The joint venture ended in 2007, leaving BPL to focus on its healthcare equipment sector.

1.  BPL takes pride in its superior-quality television sets. The TVs are made with combinations of TFT-LCD display and LED output. The products are manufactured by third-party TFT LCD suppliers. Then, the TV parts are assembled at a plant in Baddi, Himachal Pradesh.

2. BPL also takes the lead when it comes to medical display equipment. BPL uses different combinations of TFT display, VGA output, LED, and touch LCD display to manufacture the following devices:

3. The company upholds strict quality standards in all TFT LCD display products. This is achieved through quality tests at all stages of production and assembly. Even the third-party suppliers providing the raw materials for TFT-LCD modules are required to run through tests to ensure quality.

In a nutshell, BPL continues to be an industry leader in India’s consumer electronics and medical equipment industries. BPL provides households and health facilities with top-notch TFT-LCD display module sets used in televisions and health monitoring equipment. And in recent years, BPL has clearly shown no signs of slowing down.

Dixon Technologies Limited is a long-standing company providing consumer electronics, LED and LCD TVs, light fixtures, appliances, mobile phones, and CCTV systems. The company was founded in 1993 with its current headquarters in New Delhi and Uttar Pradesh.

Dixon’s creed is providing consumers with world-class products at affordable prices. Consequently, the company is among the top TFT LCD manufacturers in India because:

Dixon is proud to create its products in local factories. For instance, the company has an LCD display module factoryin Tirupati, Andhra Pradesh. Furthermore, the company also operates three facilities in Uttarakhand and three more in Noida, Uttar Pradesh.

Reasonable prices also make Dixon’s LCD module products and TVs appealing to the public. Couple that with features that are on par with the world’s best TV sets. Dixon believes that quality shouldn’t be sacrificed at the expense of affordability.

In conclusion, Dixon Technologies (India) Limited is among India’s famous TFT LCD manufacturers simply because it provides original, feature-packed, high-quality, and pocket-friendly products to both tech companies and end-consumers.

Oriole Electronics is an electronics company based in Mumbai. It was established in 1972 and is among the famous long-standing TFT LCD manufacturers in India.

Oriole’s strongest quality lies in its extensive experience in the TFT LCD and electronics industry. The company’s experience puts them at an edge against many younger industry competitors. All these thanks to several insights and expertise the company collected since 1972.

Another Oriole advantage is its in-house Research and Development team. Oriole’s R&D team conceptualizes products for its customers. They also formulate quality control guidelines that are strictly implemented during the production and testing phases. All these things are done to ensure the highest quality of Oriole’s TFT, LCD modules, and other product ranges.

Speaking of quality, Oriole is also ISO 9001:2008 certified. This credential ultimately proves the company’s utmost dedication to quality processes. Also, this ensures consistent operations of Oriole’s TFT LCD display factory network throughout India.

RandServ proudly provides and even encourages custom manufacturing services. The company responds to unique client needs by creating LCD display modules and designs according to customer requirements. RandServ lets clients specify custom shapes, display sizes, and interactive touch support integration.

Another good point of RandServ is its superior-quality product range. The company may be new to the industry, but its products are made with world-class technology and attention to detail. RandServ’s electronic, TFT, LCD, and LED technologies make their end-products among the most long-lasting and robust electronic/digital products in the Indian market today.

Businesses across several industries tend to neglect ethical business practices. But not RandServ. The company takes pride in its clean business practices and integrity. Commitment to ethical standards enabled RandServ to steadily grow as a reputable LCD screen manufacturer.

In conclusion, RandServ Systems deserves a spot in our 7 famous TFT LCD manufacturers list mainly because of three things – cutting-edge LCD and digital products, customized client services, and high regard for ethical business practices.

Royal Display India is a reputable TFT display supplier and manufacturer based in Mumbai. Royal Display is relatively new, being in the business since 2003. But the company didn’t let their newness stop them from growing into a successful LCD display supplier and manufacturer.

Another considerable advantage of Royal Display is its spacious manufacturing and warehousing units. Both are located in Maharashtra. The manufacturing unit boasts of specialized techniques used to produce modules for TFT, LCD, and OLED. Meanwhile, the warehouse unit is large enough to accommodate bulk orders from clients.

To wind this up, Royal Display is a young yet quality manufacturer for LCD modules and other related display screens in India. The company continues to grow with its plethora of quality display products coupled with many satisfied clients.

To conclude, Teronix is a young but reputable and promising LCD manufacturer in India. Lots of satisfied customers flock to them because of their dedication to high-quality products and top-notch manufacturing technologies.

To conclude this post, we’ve rounded up 7 Famous TFT LCD Manufacturers in India. Some of them are industry pioneers, while some are novices. However, we’re sure all these reputable companies will be a good source of products for all your display module needs.

STONE provides a full range of 3.5 inches to 15.1 inches of small and medium-size standard quasi TFT LCD module, LCD display, TFT display module, display industry, industrial LCD screen, under the sunlight visually highlight TFT LCD display, industrial custom TFT screen, TFT LCD screen-wide temperature, industrial TFT LCD screen, touch screen industry. The TFT LCD module is very suitable for industrial control equipment, medical instruments, POS system, electronic consumer products, vehicles, and other products.

The Halo, the Halo Touch, and the Control4 SR-260 remotes are the perfect hand-held interfaces to the whole home. Controls audio and video equipment, as well as lights and scenes, media browsing, voice control, and more. These beautiful remotes feel good in the hand, have an intuitive button layout perfect for one-handed operation, and are highly customizable.

Halo and Halo Touch come packaged in an elegantly understated form that elevates any space, and is perfect for any customer, from tech-lovers to the novice.

Evolution of the Everyday RemoteFull color 2.8" non-touch LCD screen provides a graphical display of devices, media, favorites, automations and menu options that are selected from, and controlled by the complete set of hard, backlit buttons below

Halo’s Voice is unlike any other, offering dynamic access to either Siri or Xfinity, the two most requested voice assistants. Halo and Halo Touch finally allows you to put all of their other remotes away by offering total control over your smart home.When using the Apple TV, push-to-talk for Siri Remote

Ghost touch is another deadly screen problem you can experience on Android. It could even be more frustrating and unreal, compared to a physically broken screen. If your touchscreen is automatically operating itself - maybe random touches or some parts of the screen, you"re not alone. Hopefully, this article will guide you on how to fix this embarrassing "Android ghost touch" problem and you can control your phone again.

You probably have experienced it when you charge your phone. It occurs when your phone operates itself and responding to some touches you"re not actually. It could be a random touch, a part of the screen, or some parts of the screen becomes frozen.

We"re about to show you how to fix the Android ghost touch problem. But do you know what caused it? Android ghost Touch is usually not a software problem. If you"re experiencing it, it"s arguably a problem from the hardware - perhaps the screen itself.

This is by far the most reported cause of ghost touch on Android. If you notice your phone started tapping itself when you plug in your charger, then the charger is perhaps at fault. Perhaps the charger is not compatible with your device, or it"s a poorly made charger.

Though, this problem is rarely caused by a software issue. Still, a wrong code in the software may freeze some parts of your screen or makes it start random touches.

For the screen to function properly, the phone needs to be in a temperate environment. You may experience a ghost touch if the device is freezing or overeating. Now, the ghost touch reaction might not be aggressive, but it will affect some part of the screen.

You might also encounter ghost touch on your Android phone if you have a bad screen guard - mainly if it"s not attached firmly to the screen, or if there are particles between the screen and the protector.

First, if you only experience ghost touch on your phone while charging it, the best thing you could do is get another charger that is compatible with your phone. If you still have the charger bundled with your phone, we recommend you use it instead. Otherwise, simply get a new charger from a reputable company or your brand"s official store.

The screen relies on the contact between your finger and the touchpad to execute any action. This also applies when the screen has foreign particles - maybe from dirty fingers or dust from the environment. In this case, keep your phone screen clean to get rid of Android ghost touch problem.

It"s easy to do, just turn off the screen, get clean wipes (or soft cloth), then gently wipe over the screen. Do not scratch the screen with sharp objects.

To fix/avoid ghost touches on your Android phone, you also need to keep the phone in normal temperature and always remember to take breaks between screen usages, especially when the phone gets hot. Also, endeavor not to use the phone under hot temperatures - under direct sunlight, etc.

This still matters. If your screen couldn"t heal from ghost touch, it could be a call to replace the screen. Perhaps the screen is getting weak, water got inside it, or it was replaced with a bad screen component. All you need to do is find a competent engineer around you and fix the screen - usually the official service centre for your phone.

Finally, if your screen couldn"t heal from ghost touch, the last thing you can do is take it to a repairer to fix the screen for you. It might not even be caused by the screen, but once it"s a hardware issue, it should be fixed by a professional technician.

If you own a TECNO, Infinix, or itel smartphone, you could easily fix ghost touch by bringing your phone down to Carlcare. We"re the official service provider for these brands, and we"re experts in diagnosing and fixing any issue you might come through on these devices.

This project description is now obsolete as the latest nymea Raspberry Pi image has the UI for the touch screen directly integrated. All it takes is to download the nymea image and flash it to the Raspberry Pi with a screen and the setup as described below will work out of the box.

For a while now I"m using nymea as my smart home solution with nymea:core on a Raspberry Pi and nymea:app on my phone. Initially I wanted to wall-mount a phone or tablet but results weren"t that great. Phones are built for a pocket and that causes a lot of small fiddly issues when used in a different context. One example is waking up the screen: Phones typically have a hardware button on the side to turn on the screen which gets a real challenge to do if the thing sticks on a wall. Next thing is that mobile operating systems don"t like apps running all the time in kiosk mode, yes, Android has a feature to lock an app to foreground but there are still cases where it wouldn"t do the right thing. There"s more such issues I"ve encountered while trying. While it would probably be possible to get an Android device to cater for the use case it seemed a lot of fiddling against the OS. So eventually I decided to look for an alternative and ended up with a Raspberry Pi with a 7" touchscreen panel.

In my place I use a Raspberry Pi with nymea:core which is placed to cover the most part of my home (including balcony) with Bluetooth so sensors are within a reachable distance. The control panel however, should be placed in a different location where it can easily be reached and used. For this reason, I now have 2 Raspberry Pis set up, one for the core and one for the touch panel frontend. If you want to build this too, it can be created just the same with nymea:core running on the same Raspberry Pi as nymea:app. To ease up this article I"m going to continue with describing a single-RPi system. If you"d like to connect multiple touch panels to the same nymea:core or prefer such a distributed as I have, just follow the :core or :app steps on different Raspberry Pis and repeat as appropriate.

For connected things I mostly use Philips Hue light bulbs (also some others, but that"s a whole new hackster topic :) ), have some Xiaomi Flower Care sensors for preventing my lemon tree from drying out, connected my Kodi media center to it (to dim down lights while I watch a movie) and included a bunch of online services in the setup, like push notifications, weather services and what not. Given this article focuses on the touchscreen control panel I won"t go into details on my general nymea setup but rather continue with setting up the display. Here are some few screenshots to give some insight:

Assembling the Raspberry Pi and display in that particular case as I have is not hard, but somewhat fiddly. Turns out if you first mount the Raspberry Pi on the back of the display and then try to put it into the casing it"s gonna get very tricky to fit it in without using too much force. Instead I figured out that it"s much easier to first just plug the cables, then place the RPi in the casing at its final position and lastly plug the display in. Then tighten all the screws. However, note that with this casing it is not possible to add/remove the SD card once it"s mounted. So I would recommend to first set up the basic system on the SD card using the Raspberry Pi without the casing, perhaps even using a regular monitor on the HDMI port if you have one at hand. The 7" touch panel should do too, however, put it on the desk next to the Raspberry Pi for now. Once you are confident the system on the SD card works good enough and can be accessed through SSH (more on that later) it"s time to put the case together.

Download the nymea:core image from thenymea wiki. Preparing the SD card depends a bit on your OS but there are plenty of instructions out there on how to write an SD card image. I for one tend to useddas described in the nymea wiki right below the download links, but if you prefer something more user friendly and available on all major operating systems,Etchershould work fine too.When done, insert the SD card in the Raspberry Pi and boot it up. If you want to use an ethernet cable just plug one in now. If you want to use WiFi, you can install nymea:app on your iOS or Android phone and set up WiFi credentials from there without having to plug a keyboard to the Raspberry Pi. Use the "Wireless setup" menu entry in the app"s loading screen for that.

The nymea:core image for the Raspberry Pi only has the nymea:core preinstalled. At this point it should already work from your phone. You can play around a bit and check things out. However, we"re interested in running the app on the touch panel, aren"t we? :)There is anymea:app desktop snap package available in the Ubuntu Core Snap store.It is built as a GNU/Linux desktop app but as there are armhf builds available it will also install on a Raspberry Pi. However, it will only install a start menu entry by default. We need to do some tweaking to actually start it in kiosk mode without the need of an entire desktop.The nymea:core image comes with SSH preinstalled and enabled. Use nymea:app on your phone to discover the Raspberry Pi in your network and obtain the IP address. Once found, log in the Raspberry Pi using SSH (replace192.168.0.100with the IP of your Raspberry Pi):$ ssh nymea@192.168.0.100

By default, the Raspberry Pi touchscreen in this casing is rotated upside down. You can fix that with adding the following line to/boot/config.txtlcd_rotate=2

nymea:app is written in Qt with QtQuick2 which makes heavy use of OpenGL (ES2). For some reason, that is not enabled by default in the Raspberry Pi images so graphics performance is somewhat bad with nymea:app. To fix this, runsudo raspi-config

go toAdvanced Options→GL Driverand select theGL (Fake KMS)driver. I didn"t have great success with the non-fake KMS driver... In theory it should work I think but the fake KMS certainly is good enough. Alternatively you can just edit/boot/config.txtagain and append this line at the end:dtoverlay=vc4-fkms-v3d

By default, the X11 server used will paint a mouse cursor whenever you touch the screen. Given we use a touchscreen that doesn"t make much sense. To hide that, open/etc/lightdm/lightdm.confagain and edit the following line (removing the#and appending the-nocursorat the end):xserver-command=X -nocursor

By default, the Raspberry Pi will just blank the screen when idle. This makes sense with regular monitors, but again, doesn"t make much sense with this touchscreen model. We want the screen to turn off completely when in idle instead of being lit and just painting it black. The screen"s power can be turned on and off with a sysfs file, namely/sys/class/backlight/rpi_backlight/bl_power. We can manually turn it on and off with writing0or1into this file. In order to do so automatically when the screen would blank/unblank, let"s install xscreensaver and wrap its execution in a script that hooks into the appropriate places:$ sudo apt-get install xscreensaver

Edit ~/.config/openbox/autostart again and insert this line at the beginning in order to invoke xscreensaver along with nymea:app./usr/local/bin/xscreensaver-wrapper.sh &

What could be more irritating than your Android phone touch screen not working? The phone becomes literally useless, and you cannot perform the immediate necessary tasks. However, an Android phone screen not responding to touch is surprisingly a common issue.

Before taking your phone to the service center, you can try and fix the phone yourself. Wondering how? Don"t worry, in this post, we will illustrate how to fix Android phone touch screen not working.

There are mainly two reasons for your phone and tablet touch screen not working. Either the touch screen might have been damaged, or the device has technical issues.

If you drop your phone and get stuck against any object, the touch screen"s connectivity can get damaged. Sometimes, only a part of the touch screen can get damaged and unresponsive.

When a technical glitch such as the phone getting hanged, the touch screen becomes un