Related
Hi,
i have new magic.
the (automatic) screen rotation doesnt work.
i have read that this could be a problem of non-root.
however i want to root my magic and could get different roms.
if i turn the magic to the left the display doent change.
trying apps like bubbles, sensor test, sensor debug, acelerator log, etc.
shows me that these apps realize a smooth rotate of the magic in all three axes.
i try the dice app. while shaking the magic with strong, i get a rotation.
but the rotation only stops when i decativate the automatic rotation (and enabling it again to test further)
does anybody know if theres a chance to edit some files with calibration data etc for the screen rotation ?
some other hints ?
i have also tried the 8-movement but no change.
i'm wondering that the apps (see above) shows a movement in all axes but the rotation doesnt work.
plz help
strange but now it works
i am sorry but now it works.
i used again the wipe rotate settings from RA Recovery 1.52G
and i start the Bubble apps and after turning it in 3 dimensional movements
i realize that bubble show the spirit level with different views.
in the past there was only one spirit-level view and the degrees (could be shown via bubble settings) doesnt reach 30 degrees in the past.
now after the wipe rotate setting and directly 3d-movements (like a 8 in 3 dimensions) the should have trained the accelerator in a new manner i have never seen before.
now screen rotations work.
believe me there is a chance to train the calibration.
( i know that calibration with the 8-movement-method was already described but i try this hundred times without a change)
Hi. I'm unsure if this is covered elsewhere. If so, please disregard.
After getting the OTA 3.2 upgrade (unrooted; obviously), I noticed a bug. If I had any applications that weren't set as the default app for a specific piece of functionality, then the option to choose which app to use no longer appears.
For example, prior to 3.2, if I clicked on a bookmark, I was prompted whether to use the default browser or Opera. I didn't set either to use as a default because I may use one or the other depending on the situation at the time since both treat pages differently.
Another example of this shows up when clicking on either the ASUS weather widget or the weather info on Beautiful Widgets. Again, clicking on the forecast for either of these will call up a browser page but since I didn't have a default one selected, the screen dims, but no option to choose a browser appears.
This isn't limited to the browser. I'm getting the same "dim screen, no option to choose" with other programs that had no default option set, such as movies. Prior to 3.2, clicking on an MP4 movie asked me if I wanted to view in the gallery or PowerAMP. Now.. ..nothing. Dim screen. Clicking anywhere or hitting 'back' returns to the screen without the file being played.
It seems any attempt to launch any file or in-app link that points to a link or file that is unassigned results with the same "dim screen" road block.
Anyone else experiencing this? or am I the only lucky one getting this frustrating bug?
Edit: Possible temporary fix...
Quick afterthought. It may be possible with some apps to set "use as default" for a specific file type in the app settings and this may fix this issue for myself and any others. Personally, I don't want to do this. I like being able to choose on the fly and would like this bug fixed. Still, if it's going to be weeks until a fix arrives, I may need to use this workaround (if it is even possible for all my affected associations) so I'm not standing still till a patch comes.
UPDATE:
While I can't be sure this fixed the problem, I undocked the tablet and removed both a 16GB MicroSD (from the unit) and a 16 GB SD (from the dock) and then re-inserted both memory cards and the tablet into the dock. After that, my links called up the association window again. I 'believe' it was reseating the tablet into the dock that corrected the issue, but ejecting and putting the memory cards may have been the answer. Note to self: check results after 'each' step.
Just tested this on mine and no I do not have this issue, I still get all the prompts for what to open stuff in be in links or videos from file managers etc
I just noticed this problem too. Very annoying, reverting to previous firmware...
I got this bug too. I tried the above solution as suggested but no luck. Then i tried another one from one of the threads here. It works!
http://forum.xda-developers.com/showpost.php?p=16100385&postcount=4
Hell, my bookmarks don't even open at all.
There is no pinch-to-zoom either.
Edit: tried the above & it did work how strange. I have auto rotate turned off.
Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.
Removing the dock and putting it back on seem to have solved the problem. Thanks for the tip!
OK I did some more tests: upon a reboot with the dock on, the problem was back. With the tablet in the "stuck" state, I removed the dock and the selection screen magically appeared.
I had this very same problem. No dock or SD here... Did the portrait - landscape rotation cycle and everything is solved now.
Regards.
This makes for a workaround, and I'm thankful for that, but I think the underlying problem is that while in Landscape mode, the OS won't go through the process of asking for a choice of browser, and you can't make the rotation with the keyboard attached. I went through the removal and rotation, and that was fine until I reattached the keyboard and was back where I started.
I had to remove it a second time, and this time assigned a default browser, then subsequently was able to operate properly with the keyboard back on. This problem is going to confuse the heck out of casual users, and ASUS will need to fix it pronto.
JoTeC said:
Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.
Click to expand...
Click to collapse
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.
nego_0 said:
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.
Click to expand...
Click to collapse
Unfortunally this was the first problem I noticed. It happens all over again when you shut the unit off and restart with the dock plugged it. I guess with this official thread maybe someone from Asus will notice it? Not holding my breath. Wonder if full factory datat reset will help. I've found when updating android on my phone tht helps wierd problems but don't want to have to go through all the re-setting up and downloading of my programs.
What a hassel. I guess when they officially begin supporting 3.2 over the phone line I can get them to resolve? Not holding my breath for that either.
I've been thinking about this further and think I might at least be able to point to the culprit (granted, in a 'shoot an arrow into the air' and you're bound to hit something manner).
Recently, ASUS made a change to the way the tablet behaves when docked. Specifically, in the way the auto-rotate functions while docked. Prior to this change, you could view your screen in portrait mode (even if docked) by turning the entire tablet + keyboard 90° or more. After the change, the screen locks at landscape oriented with the tablet in place. Flip it around now and it stays oriented (even upside-down).
With some applications, display boxes are written to start in a specific orientation which will then flip based on the current viewing angle. Since Android was (first and foremost) a phone OS (that uses portrait as it's main orientation), it may start most pieces of functionality such as display of the "choose desired app" dialog box in portrait mode but rotates it based on a call to the current device orientation status. However, I'm wondering if the OS can't reconcile that it is in landscape mode because auto-rotate has been turned off with the change ASUS made when the tablet is docked (making it specifically an auto-rotate issue), or if this change is blocking the dialog in another fashion due to the way ASUS programmed this functionality to communicate with the OS (making this a 'ASUS isn't playing well with Google' issue).
In short, this may be a bug relating to either a "auto-rotate / forced orientation" toggle, or a bug with the ASUS "lock orientation while docked" functionality.
It could also be related to the new "default size / zoom to view" 3.2 functionality mixed with a locked viewing angle.
Thoughts?
Edit: Just did a test. Rebooted the tablet (while docked) and the bug occurred; as expected. I lifted the tablet out of the dock but didn't change the orientation. I just simply lifted it up, then set it back into the dock. When I launched an html link, it now works. I know that some users (without docks) are able to fix this by simply changing orientation after booting. The process of unseating, then reseating may be providing a similar function as changing the orientation does with a dock-less tablet.
Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.
CalvinH said:
Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.
Click to expand...
Click to collapse
It is bit ridculous that the bug comes back aftrer a reboot. I guess with 3.2 we are supposed to reboot?
I'm not 100% sure about this but don't Android apps actually shut down and restart instantly when the orientation is changed?... so doing this restarts the Launcher?
And the same happens when removing and inserting into the dock? launcher restarts...
Try this... reboot in one orientation and test and try the other.. i.e. Boot in Portrait and see if the bug is there then change to landscape to see if that fixed it... then boot in landscape and test..
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
mrhomiec said:
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
My Advice, try the re-calibration thing, lay it flat on a desk and calibrate it.
Ensure the lock is enabled, and then try again.
If this doesn't help, I read somewhere a while back that this works, but I don't get how:
lay the phone flat on a table, spin it 3 times. Put it on it's side, spin it 3 times. Hold it up on one end, spin it 3 times.
Weird but works (APPARANTLY)!
cool, thank you for the info, but i think i'm missing something. how do i calibrate it?
i have screen rotate locked/disabled on a flat surface. then i tried to unlock/enable it (while still on a flat surface), and it still doesn't rotate.
mrhomiec said:
cool, thank you for the info, but i think i'm missing something. how do i calibrate it?
i have screen rotate locked/disabled on a flat surface. then i tried to unlock/enable it (while still on a flat surface), and it still doesn't rotate.
Click to expand...
Click to collapse
No you need to re-calibrate the gyro sensor, Im not with my tab so I can't quite remember where it is. Go to settings, and just have a look round, untill you can find the calibration of the gyro sensor.
No worries btw, glad to help
i still think i'm totally missing something. i can't find anything in the settings to re-calibrate it.
however, i did setup Z - Device Test and within the accelerometer and gyroscope testing shows that movement is being detected.
ok, something is totally messed up.
i just flashed Cyanogenmod monthly-2, did a full wipe cache and dalvik, and factory reset from CWM.
and my screen is still not rotating.
i'm totally clueless now.
I am on CM10 grouper latest build my home screen wont rotate, the apps and settings rotate only the home screen and apps drawer wont rotate.
Any ideas anyone?
Edit: Got it to work, I was using Nova launcher and by default its not enabled. Nova Launcher- Look and Feel - enable auto rotate. You need to enable both in system settings and nova settings. Silly of me :-\
mrhomiec said:
ok, something is totally messed up.
i just flashed Cyanogenmod monthly-2, did a full wipe cache and dalvik, and factory reset from CWM.
and my screen is still not rotating.
i'm totally clueless now.
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=1929790 it seems you need to extract some stock files to get it to work.
Guhrasoh said:
Read here: http://forum.xda-developers.com/showthread.php?t=1929790 it seems you need to extract some stock files to get it to work.
Click to expand...
Click to collapse
thank you for the link. i download a binary file from here..
https://developers.google.com/android/nexus/drivers#grouper
but i have no idea what to do with it.
on a side note, i'm wondering why this all of a sudden stopped working tho? AOKP's build 4 was doing it before the release of 4.1.2, but then just stopped. i don't understand why i need to manually do something that was working from the beginning. especially within apps. i can't get the screen to rotate in Chrome, GMail, Reader, Twitter, etc. i can care less about the home screen rotation.
[UPDATE]
so i was downloading different apps- mainly games trying to test out the rotation to see if that is buggy too, and i came across this app...
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsInphdXNhbi56ZGV2aWNldGVzdCJd
with this, i was able to test the Gyroscope and Accelerometer sensors and i noticed the blue axis (z-axis?) was not moving at all.
i then gave a few door knocks on the back plate, and all of a sudden the z-axis jumps to the correct view.
somehow it got stuck in place, but it seems to be working now. very odd. i've never dropped it. don't know how this could have happened.
mrhomiec said:
<edited>....somehow it got stuck in place, but it seems to be working now. very odd. i've never dropped it. don't know how this could have happened.
Click to expand...
Click to collapse
Well first of all stop banging on it, it has nothing to do with that. I've noticed there was something either added or removed from AOSP that causes this after the 4.1.2 update last week. Most people who are compiling locally probably noticed this... any others that have it working are just proof of the excessive kanging nowadays... since they're all probably a kang of AOKP or CM (who of which I'm sure identified it and corrected it in their git).
I haven't had time to look into it yet but I'd assume its related to Launcher2.apk. Look in Launcher2 in the AndroidManifest.xml and see if there's a line with something like:
android:screenOrientation="nosensor"
Click to expand...
Click to collapse
...you want that to be set to either "sensor" or "user"... I cant recall right now.
Did you try editing the build.prop file yet? If it is in fact related to the sensors then I dont think this will correct it anyway, but it's worth a shot. Go to your /system dir and mount is r/w, edit build.prop by adding this to the very end, on its own line:
launcher.force_enable_rotation=true
Click to expand...
Click to collapse
...save that, close it, then reboot and see what ya got. If it doesn't work then you know its Launcher2 not enabling the sensors. I'll post again once I look at it and fix it.
mrhomiec said:
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
Do you have "auto rotate" in 'settings/accessability' , checked?
Posted via my Amiga 3000, EVO 3D , or Nexus 7
oOo B0XeR oOo said:
Well first of all stop banging on it, it has nothing to do with that. I've noticed there was something either added or removed from AOSP that causes this after the 4.1.2 update last week. Most people who are compiling locally probably noticed this... any others that have it working are just proof of the excessive kanging nowadays... since they're all probably a kang of AOKP or CM (who of which I'm sure identified it and corrected it in their git).
I haven't had time to look into it yet but I'd assume its related to Launcher2.apk. Look in Launcher2 in the AndroidManifest.xml and see if there's a line with something like:
...you want that to be set to either "sensor" or "user"... I cant recall right now.
Did you try editing the build.prop file yet? If it is in fact related to the sensors then I dont think this will correct it anyway, but it's worth a shot. Go to your /system dir and mount is r/w, edit build.prop by adding this to the very end, on its own line:
...save that, close it, then reboot and see what ya got. If it doesn't work then you know its Launcher2 not enabling the sensors. I'll post again once I look at it and fix it.
Click to expand...
Click to collapse
thanks for all the info.
i'm not the type to mess with the files. but as i mentioned, i wasn't on 4.1.2 yet when this started happening. AOKP build 4 was based on 4.1 or 4.1.1. and would it be possible for a file to make the z-axis jarred in one direction? then when placing some force to the back of the device jump it back in place?
i haven't had any issues since then. i am now able to rotate the screen at will.
Originally Posted by mrhomiec
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
Do you have "auto rotate" in 'settings/accessability' , checked?
Posted via my Amiga 3000, EVO 3D , or Nexus 7
Click to expand...
Click to collapse
I'm having this problem now too. Just in the last 2 days.
I have a completely stock 2013 N7. It gets stuck in an orientation, and locked there. I have checked all the settings, and auto rotate is on.
I downloaded the Android Sensor Box, and something is fishy with the orientation hardware. One axis of the sensor is locked to one side and won't move.
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
The softkeys are enabled within the framework.
Sent from my Nexus 4 using Tapatalk 4
Help
manojsap said:
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
Click to expand...
Click to collapse
same issue here even i try a factory reset
I flash the stock rom again and no clue of what to do
The exact same issue here, started behaving quirky since 4.3 and went bat**** crazy after the update second 4.3 ota (1.8mb patch google released recently). i used developer options to show the on screen touch blobs as well and it registers touches in the nav bar area, it just will not work in portriat (or rather that section of the screen) It is extremely frustrating.
I even went as far as to use adb and fastboot to restore my phone to stock 4.3 which would remove all files and place a stock 4.3 directly from dev.google but still It doesn't work.
The same issue
Im having this exact issue just a few days after i install a new update i hope that its a software issue :crying: and if is not warranty will cover it?
Navigation Bar issue
Same problem here , wont respond on portrait mode.
I did try to downgrade my android version to 4.2.2 (from 4.3) after the factory reset did not work, that did not work either.
Any ideas? could use some help
I have the same problem, I tried to restore the 4.3, the 4.2, but the problem remains, I also tried the cyanogenmod and 4.4, but it still does not work the navbar in portrait mode ..
No one knows a solution to the problem? You may have a hardware problem? Who takes care of the navbar?
Having the same issue here. Works in Landscape but not portrait. It went spastic this morning randomnly opening the clock and pullin the bar down itself. Show touches showed it registering touches all around the nav bar then suddenly it stopped. I cant use the bar now at all in portrait but the random touches are gone. I downloaded a touch detector and it shows all the way up to where the nav bar would be then deadzone, but fine in landscape again
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
sorschumi said:
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
Click to expand...
Click to collapse
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Same issue here
Tried lot of things still not working .........
pls someone find the solution.......
skycoresaunish said:
Tried lot of things still not working .........
pls someone find the solution.......
Click to expand...
Click to collapse
I think it's a hardware problem. Mine just went bad as well.
I have this problem now, too. Google now NAVRING still works to open Google Now from the middle nav button, which is why I do not understand why they nav bars do not work at seemingly the bottom of the screen. It just seems like that part of the screen has died, though some times it randomly works....... what the hell is this?
Huawei ascend mate navbar problem
I have same problem. And not only that my landscape control also got messed up After factory reset.
Also when I try to scroll down the web page in landscape mode it dosent work on the same area. So does this mean screen is screen is not registering my touch.
Some times the middle button start acting funny. It operates by itself even the internet is off. Like virus or some thing I did checked with antivirus nothing found. After activating show touch option it is shows Google shortcut is always pressed.
Dont know how to fix. Dont know the reason pls. Help. Xda.
Do you use dt2w? For me, after enabling that feature this would happen after a while. The borders of the screen would become unresponsive. I disabled dt2w, rebooted and it was fine again.
Sent from my Nexus 4 using XDA Free mobile app
Hi to everyone!
I have the same problem since some days with the nav bar on stock 4.4.2. Factory reset + rom flash via fastboot + CM 11 innstallation did not help at all. I'll bring my Nexus 4 today back to the retailer for reparation / replacing.
I'll inform you guys about the report of service center but it can take up to 45 days.
Thanks. This works for me
haris0032 said:
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Click to expand...
Click to collapse
Hi, I was facing the same issue on my mako. It just started without any notice. Being a flashaholic I thought it could be due to something I installed. Tried a lot of differnt ROMS including stock but no luck. Read somewhere about the "Show touch" function in the developer options and found that almost 7.5mm of the bottom of screen was not responding to touch. I then installed the stock 4.4.3 ROM, rooted it and installed gravity box. In Gravity I changed the navigation bar height to 120% and selected "keep at bottom" for landscape. I am now able to use the phone. I wish some custom ROMS start implementing 52dp height option so we could use these directly. I tried using gravity with Mahdi ROM but there is some conflict and I cant see the recents button. Also, the NB reverts to original and it needs to be enabled again manually
But thanks anyways. I dont want to buy a new phone for the next 6 months and this will work well for me.
Cheers
Hi Everyone,
Recently my phone was updated to Android v7 and since then I noticed that the icons for the cursor in text boxes and system dialog boxes have got messed up.
I read on Android central, one user posted that uninstalling Kaspersky fixed the issue, although in my case I don't have Kaspersky, so I can't go about uninstalling all apps, got a hell lot of them!
1drv.ms/i/s!AigR1NGUKZ2stFWGsf_bkkIg_WEa
1drv.ms/i/s!AigR1NGUKZ2stFa4-NP8jEiQCuMs
1drv.ms/i/s!AigR1NGUKZ2stFRZcp6bHn6VE_JE
It's frustrating everytime i see this... Please help me...
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
jivenene said:
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
Click to expand...
Click to collapse
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
jivenene said:
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
Click to expand...
Click to collapse
I have those glitches as well apart from what i posted.
I read online its because of some app messing things up. I seriously don't want to reset and start testing this out one app at a time. It will take at least a few days to get back up to speed.
Thanks :crying: