Related
As a Vogue owner, I use mine for GPS in the car, as well as being my media player, and also (obviously) as a phone.
This usage finds me frequently rotating the screen to the right, and turning on BT when I get in the car. Then when I get out, I have to undo those changes. It's a number of clicks to do this each time, and becoming something of a hassle.
I'm thinking of writing an application to automate the process. I wanted to get some feedback before I start.
1. Is anyone else interested in a project like this? (Note that this is just the beginning, additional functionality could be added, feel free to brainstorm!)
2. Is anyone who is interested in this project willing to beta-test this software?
Thanks for your input!
Shidell
Hm. I guess nobody else uses a screen flip & BT regularly as they enter/exit their vehicles? Or perhaps I'm uninformed on a better of way of doing so?
Comments/thoughts, anyone?
I would love to have a one button access to this too. On my Dream I have the power control widget. And although there is something similar for WinMo 6.5, its doesnt do the screen flip. Only Bluetooth.
I am not a developer, but I dont mind putting my Vogue up as a guinea pig!
bt
what do you use bt for? the external gps or to your stereo or monitor? My gps is internal myslf.
But otherwise yes I use mine for the exact same purpose, I would also like to output the video to my stereo monitor for larger view, audio is already working but I havent found anyway to output video either. I dont think you can on the touch vogue.
i keep BT on all the time (not discoverable though), and i used AEbutton Plus to set my camera button to rotate the screen when i hold it down.
mrono said:
i keep BT on all the time (not discoverable though), and i used AEbutton Plus to set my camera button to rotate the screen when i hold it down.
Click to expand...
Click to collapse
That would be cool, I'd be willing to beta-test for you.
mapping the camera button to screen rotate is a work around but it's just that.......a work around. I use my camera function alot as well, this would be a neat app.
Glad to see there's some interest! I figured I wasn't alone. I was also using AEButton to map a flip, but then found I would flip, turn on BT, etc. Anyhow, on to the beta.
This is simply a proof of concept to prove it works functionally. This *should* work on all Vogues (and probably most other model phones), but again, this is still a beta.
Please note that there is no installer (.cab) package right now, nor any icon, and no application settings. When you launch the application, it will determine your screen's current orientation and flip it, and it will also determine your BT's current setting and flip it. That's all this will do in it's current state.
What I need from you:
What model phone do you have (assuming Vogue?)
Did the functionality work as I described? Any problems?
How would you change/improve this application?
I am considering adding a first-run type setup to determine how you want to run the flip--IE just turn on BT (as a shortcut), etc. Ideas?
Note: As it stands right now, V15 of NFSFAN's ROM using M2D will not "flip" orientation. Titanium is fine, but M2D doesn't like the "flip" and the screen will revert to standard orientation, even though the application runs as normal and will enable/disable BT.
Simply unzip this package and place it on your phone's memory--local, SD card, it doesn't matter. Make sure you include the .exe and the .dll. Then you can run the application by clicking it. Note that you can click and hold on the app. to send a shortcut to "Programs", to make it convenient to launch.
http://www.easy-share.com/1907580543/Vehicle_Flip.zip
Thanks!
1. I copied the zip to my documents, unzipped it, made a shortcut
2. Pressed start, selected the (non-existant!!) icon
It works!!!!
I was able to flip screen orientation back and forth.
1. Manila
It also worked for me with Manila. The actual Manila doesn't like being in landscape, but it did not revert, and I used the start menu to launch TomTom and it stayed in landscape. Orientation did flip as you stated when exiting TomTom. When selecting the application again to turn off bluetooth it did, but ther orientation flipped portrait-landscape-portrait while bluetooth turned off
2. Titanium
Worked very well
I usually use 2 things in my car (at the same time), audio manager and TomTom, I launch each separately, have TT displayed, press the red home key, then use task manager to flip to audiomanager to switch a song if I want, then back to TomTom. I was able to do all of this and the screen stayed in landscape the whole time.
Not working with Manila isn't a big deal for me, M2D never has behaved well in Landscape, but some prgrams do (audiomanager, phone canvas). I also prefer the stand alone audio manager screen for in the car because the buttons are more finger friendly than the music tab on M2D.
I would make an icon for this program, and that's about it. Sometimes simplicity is the best.
My info is in my sig. You should preview and link this thread to the dev and hacking section. You'd get more notice and feedback.
Greeat Job!!!
I just have the camera button mapped to rotate screen; and if you hold down the camera button for a while, it opens the camera. Makes rotating the screen fast and easy.
Okay I think I found another bug in the HTC sms program which I discovered today and wanted to see if its just me or anyone else. The other is hoping someone has a fix for a signal problem, and a solution for the third. I have the HTC EU Official ROM WinMo 6.5 with sense 2.1, and the phone is HardSPL.
1) I noticed today a bug in the HTC SMS program (I know who hasnt), but this doesnt seem to fall under anything I've read so far. Here the problem, When you click the contact icon on the slider bar it brings you to the flip contacts, when you click the contacts picture you go into their "profile" when you click the second sms icon here you can txt back and forth, now what I noticed is if you txt thru there when someone responds to a txt, the tone set (be it the default, or custom) doesnt ring completely. It rings for like a 1/4 of a second. I noticed this as I was txting a friend. Has anyone else have this or encountered this? This is completely different then not being notified of an incoming txt, but runs along the same possible reason why we dont get one.
2) I use a bluetooth 85% of the time, I have one major issue. I saw a possible fix, but I dont remember where or what site, but I dont know if its for this issue either. I normally keep my phone on my belt clip on the right side and the bluetooth on the right ear, but if I decide to move the earpiece to my left ear, the signal seems to get weak, and I start hearing crackling until; I move the earpiece back, or move the phone to the same side. Is there a cab or registry edit that improves the signal strength for this? I have two bluetooths, sony erricson and a Jabra V250, both have the same symptom.
3) Everytime I get a call or make a call, when I am talking the proximity sensor kicks in, which is fine, but everytime I move the phone away from my ear, thescreen isnt at the dialpad but at the black notification screen. I understand that if there was a txt, missed call event then thats fine, but when none of these exist its annoying. Is this by design or is this just something thats going to annoy me to hell and back?
Bumpy Bumpy...
Anyone?
Also I found I think another bug, I dont know if its been mentioned, if it has sorry, but has anyone realized that when the phone is on and at standby and the screen goes black that the volume keys still adjust the volume? I normally keep my phone in a leather case on my belt, and notice that when I bend down the buttons if hit will adjust the volume up or down, I ran into this by accident while bending down all of a sudden my phone vibrated briefly checked the phone and saw the volume was all the way down, thought maybe the screen was up and thats why it happened after the second time I tested it and sure enough you can adjust the volume. I know for a fact the Fuze never did that. Anyone else have this issue?
AngelDeath said:
Bumpy Bumpy...
Anyone?
Also I found I think another bug, I dont know if its been mentioned, if it has sorry, but has anyone realized that when the phone is on and at standby and the screen goes black that the volume keys still adjust the volume? I normally keep my phone in a leather case on my belt, and notice that when I bend down the buttons if hit will adjust the volume up or down, I ran into this by accident while bending down all of a sudden my phone vibrated briefly checked the phone and saw the volume was all the way down, thought maybe the screen was up and thats why it happened after the second time I tested it and sure enough you can adjust the volume. I know for a fact the Fuze never did that. Anyone else have this issue?
Click to expand...
Click to collapse
I don't know that this is related to your symptoms above, but several TP2 owners (myself included) have experienced the fact that this model seems to be particularly sensitive to cases with stronger magnets in the clasp...the magnets are just strong enough to trigger the magnetic switches in the phone that register when you slide open the keyboard, or remove the stylus. It drove me nuts for a while trying to figure out why my phone seemed to keep randomly turning itself on in the case, especially right when I was first sliding it in/out. I had thought it was because there were hardware buttons still active even when the screen was dark, but some thorough experimenting/testing proved the issue was due to the magnets....a conclusion that was confirmed by several other users once I actually bothered to go looking online for a solution (....after I'd spent hours figuring it out for myself lol). So, it might be the cause of your screen coming on and then the volume buttons are just the first ones that get pressed by your particular case and/or posture.
Unforutuately, I doubt there's any possible connection between that and your other issues...
I know there isnt any connection with the other issues, I just didnt want to make another post and have XDA shoot me for it.
Also I know about the magnet interference I read up on that long ago, but thats not my issue. I thought that was it, but I can do the same thing while holding the phone in my hands. So the magnet in the holder does not apply. I can have the home screen up, hit the power button to blackout the screen and then hold the volume down key and it will lower the volume cause by holding it down the phone will vibrate, when I turn the screen on, the volume is all the way down.
AngelDeath said:
1) I noticed today a bug in the HTC SMS program (I know who hasnt), but this doesnt seem to fall under anything I've read so far. Here the problem, When you click the contact icon on the slider bar it brings you to the flip contacts, when you click the contacts picture you go into their "profile" when you click the second sms icon here you can txt back and forth, now what I noticed is if you txt thru there when someone responds to a txt, the tone set (be it the default, or custom) doesnt ring completely. It rings for like a 1/4 of a second. I noticed this as I was txting a friend. Has anyone else have this or encountered this? This is completely different then not being notified of an incoming txt, but runs along the same possible reason why we dont get one.
Click to expand...
Click to collapse
You get a shortened notification if the phone thinks you are looking at the screen when the message comes in. It would be nice if this could be turned off, but that is why.
The Pro2 isn't necessary 100% at fault with the Bluetooth problem. It can be a combination with your handsfree earpiece too.
Every Jabra unit I own has always exhibited this problem with every HTC phone I have. The first time I bought a Jabra I remember reading in the manual about their recommendation to keep the phone and earpiece on the same side of the body to avoid "interference" (referring to the body??). And if I'm listening to music through A2DP, and I move the phone to the other side of the body, the music cuts out too.
I also have an old Sony Ericsson HBH-660 and it doesn't have this problem if I wear it on the other side of the body, so it's appears both HTC phones and Jabras emit a weaker bluetooth signal.
Mesquire said:
The Pro2 isn't necessary 100% at fault with the Bluetooth problem. It can be a combination with your handsfree earpiece too.
Every Jabra unit I own has always exhibited this problem with every HTC phone I have. The first time I bought a Jabra I remember reading in the manual about their recommendation to keep the phone and earpiece on the same side of the body to avoid "interference" (referring to the body??). And if I'm listening to music through A2DP, and I move the phone to the other side of the body, the music cuts out too.
I also have an old Sony Ericsson HBH-660 and it doesn't have this problem if I wear it on the other side of the body, so it's appears both HTC phones and Jabras emit a weaker bluetooth signal.
Click to expand...
Click to collapse
My Sony Erricson is a HBH-GV435 And both the Jabra and the Erricson exhibit this behavior. I dont know where I read it, but I think there is a registry edit about improving the signal, unless it was something else and I read wrong, was hoping someone knew what I was talking about.
Zylograth,
I wouldnt want it turned off, if anything it should ring normally. And I think that maybe in connection to the possibility of the SMS alerts not coming in when the screen is off. I think its related somehow. But do you know where this shortened tone noticification is located?
But now what about the other behaviors? Anyone else have them?
The noticification screen is really starting to bug me with I move the phone away from my ear.
NOTIFICATION BAR scrolling down without touching it: Static Electr & Capacitive Scrns
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
the only time I've had that happen to me is when I use a cheap charger I've got and yeah the screen just skitses out. I am using a hero tho but this is the first time I've seen anyone else encounter this so I thought il'd churp in.
I had something similar only once.
The notification bar went mad. It was flicking up and down constantly without me touching the phone at all.
I had to pull the battery to fix the problem.
Hasn't happened since.
Fon22
Happened to me also when loading a ROM in Nesoid.
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
quicksite said:
So I'm not sensing any concerns re; any defect... but still wondering, since I don't know the physics of capacitive screens... Is static electricity the culprit? Never happened once on my GSM HERO... so something is at play here.. or is it an intermittent defect that rarely shows up?
Click to expand...
Click to collapse
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Brilliant, Alex... You got right inside my head and answered exactly what i was trying to ask.... the physics of the system.
I'm okay with little glitches here and there, and I am sure I will learn to avoid proximity issues that tend to trigger these mis-fires... just as I learned to adjust my tap-key behavior in typing on the on-screen keyboard on capacitive screen vs all the resistive screens I had used before on Windows Mobile, where fingernails could & would engage the resistive screen -- vs learning that the bottom surface of the finger has to make contact on the keys on capacitive screen... (sorry i am USA and we still resist the world's metric standard, so i don't know the equivalent distance in cm,)... but it's over a 1/4-inch of an upward shift in the position of one's fingers above the capacitive screen from the tip of the fingernail.
But once you train your senses to activate the keys sensors properly, the finger impact behaviors of resistive screens goes away after a while (at least for me)
(oh, btw, I ordered the new HTC capacitive stylus which is a couple of months old now, but is an official DESIRE accessory, so that will be an interesting experience... the thing i miss most about the resistive screen and stylus was being able to scribble notes really fast, way faster than i could ever type -- and draw pretty detailed images or maps and directuions for people. so it will be interesting to see the granularity of control the capacitive stylus will give)
So thanks very much for giving me the exact level of detail I can process as a lay person.. and for assuring me, as the rest of you have as well, that this apparently comes with the territory of this phone -- and therefore should not be seen as a defect. Because i sure as hell didn't want to go shipping this phone back. I can live with an occasional spazzoid misread of intended impact spot on screen...
And, fnally, this was funny -- re the different degree of touch we all consider "normal" --
The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
thanks!
Alex_w said:
The capacitive touch screens work by detecting a disturbance in the EM field on the glass surface. There's a few ways to do it, I think the way mobile phones are doing this is to put a field of their own over the glass and detect fingers on the surface based on what levels of the field they'd expect to see at different points around the screen, and doing some comparisons on what levels are actually detected.
Please someone correct me if I'm wrong BTW.
I've noticed this notification bar problem today and yesterday. Lucky I at least saw how I caused it. My finger was to close to the top right of the screen because of the way I was holding the handset. That combined with the lacklustre multi-touch support on this handset made the phone detect it as a finger swipe that rapidly moved downwards.
I've always had similar problems with capacitative and inductive touch technologies. I don't actually need to touch the desires screen to activate a touch. The worsted was the Zen Micro with the touch controls. I could activate that thing from about 10-15mm away. The touch on-off-dimming lamps too. I usually cycle those through all their light levels with a single touch. Where as my brother actually struggles to activate those, really has to press his hand down hard on them.
Click to expand...
Click to collapse
I was thinking it is softwarerelated. The bar remains halfway the screen, is in the layer below the active app, and jumps to front upon touching the screen.
I have the Problem, too. And that since Monday. I went mad since yesterday evening so i tried to go back to stock, unroot and all.
But the problem is still there.
How can i fix it? Or is my Phone damaged?!
The Notification Bar scrolls down without touching the display and then freezes the phone. so i must lock the phone and relock it and then i can use the phone but after a short time the same problem came back!!
So I reckon you're an undertaker for a living?
Sent from my HTC Desire using Tapatalk 2
erklat said:
So I reckon you're an undertaker for a living?
Click to expand...
Click to collapse
Sorry but i don't understand what you mean
The problem makes me crazy because i have now the stock rom because i thougt it was an issue due a custom rom or a kernel or something.
If you can help me please do that, this problem robs me to sleep
But i havent the Desire. I Have the HTC EVO 3D GSM
19Marc89 said:
Sorry but i don't understand what you mean
Click to expand...
Click to collapse
lol digging up the dead
Sent from my HTC Desire
Sorry but I do not understand the background of your information which is in context with my problem of the notification bar.
@19Marc89 He meant that you responded to a an old (dead) post. Listen, I'm trying to recondition an old Motorola Milestone (Droid) with a crazy touchscreen problem, whose cause I believe I've narrowed down to static electricity - can you do me a favor and try stroking the glass side of the phone lengthwise in one direction down your sleeve, preferably if you have a wool sweater on? Call me crazy, but this works for me, at least temporarily. I posted more here:
http://forum.xda-developers.com/showthread.php?t=1041943&page=5
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
quicksite said:
I would like to know if anyone else has experienced this at least once. I didn't post here as a thread til I got confirmation from one other DESIRE user that this has happened to him as well.
I don't know the exact triggers or even the exact scenarios, but this has happened several times to me already:
I am using the phone in horizontal mode and tapping menu items or inputting text, and my finger is nowhere even close to the Notification Bar at top of screen -- and yet suddenly the Notification Bar will auto-scroll down, interrupting what I was doing. Repeated times. It would happen again, with no accidental slippage of my finger or anything. My finger would be nowhere near the bar.
I am wondering if there is any kind of static electricity effect with capacitive screens that can set off a menu action.
So I am asking the experts here. Is that possible? Is it anything that was reported with the Nexus One?
RELATED (1): After this happened a few time in ONE SESSION using the phone -- it happened to be while uploading videos to YouTube, I wanted to test to see if I moved my finger close to the Notification Bar would this perhaps trigger this auto-scroll-down. So I moved my finger just slightly above the surface of the glass at the Notification Bar, and it didn't make it scroll down, but on this occasion, it set off a kind of jumpiness whereby the notification bar was rapidly shifting up and down a few pixels, as though it was receiving input. Has anyone seen this happen? I have not yet been able to get this to repeat from that session of using the phone a few days ago. I was lying down on my bed, and I'm pretty sure sheets produce a lot of static electricity, so this is my layman's question. Is there some causal effect here?
RELATED (2): A variation on this problem would be where I am actually trying to select a menu choice, and instead of my finger-press activating the menu item, instead the menu item jumps up slightly, and does not get selected.
This, again, happened when I was in ALBUM MODE, watched a video in horizontal display, then tapped-and-held the video to bring up the context menu that includes various SHARE options. One of those options is YouTube (the last item of the menu). I would try to select "YouTube" but the menu jumped upwards slightly, and wouldn't get selected.
I have been able to reproduce this one (Related 2) today, days later, in totally different environment .
So, a bunch of questions:
1. Is there such a thing as a static electricity effect that confuses the screen?
2. Are there other kinds of known screen-response problems that could be at play here?
3. Is this something that sounds like "it's defective so return it", or is this a somewhat common experience, sporadically?
Click to expand...
Click to collapse
REPLY :
install gravitybox. go to >statusbar tweaks>disable peek. click it. problem solved!
I know I am many years late but did you somehow manage to solve this problem?
What a difference a day makes. Yesterday my rad new Xtrons Android headunit was working almost* fine and today, after following conventional wisdom and letting my 15yo nephew pimp it, it's in all sorts of...well fckd.
Keen on some help from the collective wisdom. Before anyone helpfully suggests a factory reset... well, that's been done, sooo many times. When your nephew CHANGES the factory settings, it becomes a cycle of hell.
Unit is an Xtrons PB86MTVP. 8" HD, Android 6.0' Octa-Core 64bit 32GB.
Current main problem is that the touch screen inputs are reverse and diagonally opposed. What the hell do I mean by that? If I want to type on the qwerty keyboard or simply tap an icon, I have to use my cunning and hit an area or button diagonal and opposite for it to work. If I can get past this issue then maybe I can move to the next one which is that the unit doesnt power on/off with the ignition.
To be clear, things tried (multiple times in some cases) include
Reset via reset button
reset via software app section
undoing car battery
pulling unit back out and disconnecting
turning on and off again
swearing
So, who can help? got a silver bullet?
TIA
Joe
You could go to settings start right down the line set your home screen back and you should have a setting there for different keyboards also that should get yoy back to normal
Sent from my LG-TP260 using Tapatalk
djkeylenux said:
You could go to settings start right down the line set your home screen back and you should have a setting there for different keyboards also that should get yoy back to normal
Sent from my LG-TP260 using Tapatalk
Click to expand...
Click to collapse
thanks for the reply djkeylenux. I've got the right keyboard though, thats not the problem. the problem is the touch input on the screen, no matter which screen I'm on.
Well beside calibrate witch I thing you tried you could also go to developer options take a kook at running process see if there's something running causing the problem,
I think you lost the MCU settings.
Go to settings and then into Factory Settings menu. Password is 126.
Then in keys tab re-calibrate the screen. During calibration you will first see a "+1" in one of the corners. Tap it with your finger. Then in opposite corner "+2" will appear. Tap it too. Then accept and apply ypir settings and the unit will reboot. The touchscreen will work correctly then
In the same screen you can also re-configure the touch buttons and physical buttons of yoir device.
It looks like someone potentially did an MCU upgrade/flash. If there was no backup of the settings then you lost it all. Which also means you might have lost bluetooth connectivity as the bt module type on first page of factory setting might be wrong too. Also canbus and other things might be affected. I recpmmend to check out the discussion threads on MTCD devices here. Someone with the same unit might tell you the right settings.
Hint: If you have trouble tapping the icons with non-calibrated screen. Try connecting a standard USB mouse to any of the USB ports.
Thid weird issue started today in the morning, first I noticed that the clock widget had changed size, and that the led me know ring around the cam hole was out of place, but, when trying to write in whatsapp, I no longer could make the keyboard to appear by taping the wrinting field, in fact, nothing located in the bottom worked, what is odd, the bottom gestures worked, as I hid the nav bar since day one, tried everything, changed dpi, changed keyboards, retired the screen protector, wiped cache, to no avail, reluctantly, I updated to android 10, but no luck, after digging more, I found a work around, I changed the resolution from quad hd to full hd, now all is normal, but, this is just a work around, not a real solution, somebody have an idea of what would be the reason for this?
Did you have your phone linked to windows, your computer online and the phone screen displayed at that time? In this case, if you chose to use your computer's hardware keyboard in Your phone settings on your computer, then, when trying to write something in whatsapp, the virtual keyboard on your phone is not displayed or it is partially displayed. In my case, using the AI Type keyboard, only the top row of the keyboard was displayed because the app thought I'm using my computer's keyboard.
Sent from my SM-N975F using Tapatalk
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
winol said:
Thanks for your reply, but no, in fact I have never used the phone in that way, something else caused the issue
Click to expand...
Click to collapse
Was your phone charging at the time by any chance?
I found the solution!
I had the exact same problem with my note 10 plus, the gestures worked, and I tested the bottom part of the screen to make sure everything was working and it was, but the buttons in apps like instagram at the very bottom of the screen still were unresponsive most of the time. The solution is to ho to your settings, switch the navigation bar to the other gesture variant and then back to you preffered one and it should work. It worked for me.
Thanks man, I just found what triggers the issue, as odd as it seems, changing resolutions from qhd to fhd id what causes the issue, odd, because I used a bixby routine to save power at nights, by setting medium power saving, which among other things, lowered the screen resolution to fhd, when the routine ended, it should reverse to qhd, and that precisely triggered the issue, I used this routine for months, until, out of the blue, it started to cause this problem