Develop Bugs

Dolphin 8.6+ and Nexus 7

I'm having an odd and distracting issue since Dolphin 8.6 and now with 8.7 too. I always disable the Pinch Zoom Button in the settings, don't like any kind of overlay. But in the last two updates, this button shows up on my Nexus 7 even though I have the feature disabled.
If I restore back to 8.5.1 it works normally and the button is gone, but reinstalling 8.6 or later causes the button to return despite it being disabled.
I've had this happen on two of Nexus 7 tablets. But it doesn't happen on my Galaxy Nexus or Touchpad. I'm wondering if this is just me, maybe something I've inadvertently done, or if this is happening to others on the Nexus 7 as well.
Thanks.

Surely there must be one kind soul that could test this and let me know?

Random reboots

I buy my nexus 7 2 two weeks ago from US Google play store. After opening the camera 1st saw the reboot issue. Then it increases day by day. Then update all apps and OS but no change.
Then I root it, delete all Google Apps but still problem persist. Then go to CM but no solutions. Then revert back to factory image jss15q but no solution. Now during serving Internet, fb apps, or opening of any apps it reboots multiple time. Also reboots during movement of tabs in my hand or take it a flat surface it reboots automatically. I can't use this tab and I can't change this tab as I am now in Bangladesh. Pls pls
Give a solution.
Sent from my A110 using Tapatalk 2

Horrible lag after running Super Hexagon

Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device

Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way

Eregoth said:
Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way
Click to expand...
Click to collapse
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock

chiefz0r said:
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock
Click to expand...
Click to collapse
Haven't found a fix yet
It's clearly a software issue though, either with the game or the latest N7 2013 build. Maybe someone who's more skilled could check the debug log (or something) to figure out the cause.

Hey
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0

NsZebra said:
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0
Click to expand...
Click to collapse
Just tried this and it happend again (on the first try). Rebooted and triggered it again after launching the app 3 times.

Eregoth said:
Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device
Click to expand...
Click to collapse
I confirm, the only solution is to reboot... Very annoying if it happens while you break a record

Wow, I am astonished by Google. It has been over a year now and this problem STILL exists, I am having the exact same problem as described in the OP with several apps. How come this problem gets so little attention? Should be well known by now.
All those fancy design changes but who cares about actual system stability.

^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.

yosmokinman said:
^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.
Click to expand...
Click to collapse
No way apps are supposed or even able to mess with the whole system like that and this bug doesn't happen on other devices like nexus 5 with the same apps so it's obviously just the device. I mean did you even read the thread you ignorant prick? The thread creator said too that he can't reproduce it with other devices such as Nexus 4 or Nexus 7 2012.

laggyness with certain apps

I've had the zenwatch for almost 2 weeks and i will be keeping it. That being said here is a heads up, i found that using the app facer to make watch faces and using wear mini launcher together causes a good bit of lag when performing any action on the watch. to remedy this issue i downlaoded watch maker and low behold the lag went away. so if anyone is haven a lag issue check into what apps you are use to make your watch faces and also what launcher u have choosen. hope you guys find this helpfull .

So, did you uninstall wear mini launcher ?

tonyguy2000 said:
So, did you uninstall wear mini launcher ?
Click to expand...
Click to collapse
no i switched to watch maker it works better with min launcher

I've actually had this happen a number of times and I'm not sure why. It doesn't seem to have a consistent cause. Usually it'll be when I install a new app or something, but it's happened other times as well, but it doesn't happen consistently with one app or another. For me, the lag shows up as the screen basically being frozen without being able to control anything. Eventually, it will unfreeze and I'll usually see the mini-launcher screen, but even a restart with the back button won't solve the freeze.

For me, it was worse when I had Mini Launcher installed, but it still happens occasionally without it. I no longer have either Facer or Watchmaker installed, either. I'm using the Weather Watch Face, though. I wonder if it has something to do with watch faces in general?
When I was using Mini Launcher, apps would almost never launch the first time I tapped on them. It would go back to the watch face and freeze for a few seconds, and force me to go back to Mini Launch and tap again. Without Mini Launcher, this still happens occasionally from the built-in Start... item, but much less frequently.

I have all 3 installed and it doesn't seem to lag too bad. I guess I don't interact with it the same as I would with a phone so it doesn't bother me at all. Whenever I get a card it interacts with it seamlessly, that's about as much as I need it to do

xmeatizmurderx said:
I have all 3 installed and it doesn't seem to lag too bad. I guess I don't interact with it the same as I would with a phone so it doesn't bother me at all. Whenever I get a card it interacts with it seamlessly, that's about as much as I need it to do
Click to expand...
Click to collapse
Interacting with cards hasn't been a problem for me, either, it's launching an app that's not already running that seems to be the issue. Sometimes (or almost every time for me with Mini Launcher), the new app doesn't come to the foreground, and the watch appears to hang for several seconds. It then has to be launched a second time to become visible.

I've definitely seen it lag like that. Hopefully it's just a software issue with android wear being so new and updates will help fix that. It's got plenty of processor and ram torrun the tiny apps no problem

I noticed a considerable amount of lag while using mini launcher. To the point that I didn't even want to show off the watch to other people because it made it seem terrible. Major difference since uninstalling, lag free now. I also use Watch Maker and a few Play Store watchfaces with no lag issues.
Wish we could move the start menu to the first selection on the tap screen instead of the last, then I really wouldn't care about a separate launcher.

1+ for deleting mini launcher. I like the app but its so dam laggy. As far as Watch Maker app works at times for me so I deleted that as well. I was using Facer until I ran into Intellicom which seems to be very easy to use and no change in my battery life.

I think this is more of a symptom of using a single core A7 processor. I imagine all of the governors and IO schedules are set up for battery life so that probably doesn't help either. It might just be coincidence that you are running something while a background task is also running.

Touchscreen freeze

Hello !
I made the march update yesterday, and now my touchscreen freezes if I don't use it for a few seconds. To make it work again, I have to lock/unlock the phone, or to tap the screen until it works.
It's probably a software issue, because it happenned just after the update. Does someone have the same problem ?

I'm having the same problem. It's the right 3rd of the screen that becomes unresponsive. If you swipe over on the left side of the screen, you will be able to use the right side again. This is my second day with this and it's becoming incredibly annoying.

I just realised it ! For me, the only responsive part is the left 4th of the screen. I hope Google Will fix it soon. I don't want to reset my phone.

I'm not seeing this issue... how long is it taking to freeze? also what are you guys running? stock or stock rooted?

I'm running stock. If you wait 5 seconds after the scroll bar vanishes, the right side of the screen is unresponsive. If you swipe the left side, it works again. It's really a problem when I'm doing remote desktop to my computer and when I'm playing candy crush.
---------- Post added at 04:26 PM ---------- Previous post was at 04:22 PM ----------
You should post any post March update issues you are having, here. https://productforums.google.com/forum/m/#!category-topic/nexus/other-discussions/2HXGtYoPwa4

I'm running stock too. It takes aproximately 6 seconds for the touchscreen to freeze.

I just tried to reboot in safe mode : it doesn't solve the problem.

theorime2 said:
I just tried to reboot in safe mode : it doesn't solve the problem.
Click to expand...
Click to collapse
Does it happen in recovery or bootloader?

I just received the update this afternoon and I'm encountering the same issue. Quite frustrating.

I got my Nexus 5X yesterday with exactly the same issue.. Flashing any older factory image did not help. :/

I wonder if opting in to the Android N beta would have any effect. Not sure I'm ready to commit to running beta on my only phone; but I am tempted.

sfringer said:
I wonder if opting in to the Android N beta would have any effect. Not sure I'm ready to commit to running beta on my only phone; but I am tempted.
Click to expand...
Click to collapse
On my phone the problem existed on stock rom (I tried 3 drifferent versions), cm13 and N preview. I do not think that flashing any other Rom would make any difference.

mrlollog said:
On my phone the problem existed on stock rom (I tried 3 drifferent versions), cm13 and N preview. I do not think that flashing any other Rom would make any difference.
Click to expand...
Click to collapse
Appreciate the information on your experience. Hopefully this is something Google can track down and is correctable in software.

Exact same issue for me since MHC19J. This is driving me nuts.

I've tried all versions except a full CM ROM. So stock, beta, and a few different AOSP builds. I cannot reproduce any screen issues being reported here.
Is there maybe a common app that you all share? No one has mentioned whether you are rooted or not.

another day (not) in paradise
k.s.deviate said:
I've tried all versions except a full CM ROM. So stock, beta, and a few different AOSP builds. I cannot reproduce any screen issues being reported here.
Is there maybe a common app that you all share? No one has mentioned whether you are rooted or not.
Click to expand...
Click to collapse
the best example: Open Wifi Analyzer (in Listview) wait for results and the tap the "Back" Button. (not taping or swayping around during the wifi scan process).
Open Wifi-Analyzer (Listview) wait for result and tap the Backbutton. It took 34 seconds and 34 tapps on the backbutton until the screen turns off, but no reaction until i activate the screen.
Nexus 5X
Stock
Build MHC19J; OTA
No Root Access
for me it's beginnig on entering the SIM-PIN. It takes a few tries to enter my PIN.
Sometimes it's the Back-Button (Back - Menu - Switching Apps)
And it seems to be on the left side of the screen
installed Apps:
3Kundenzone
Google Admin
Android Wear
Authenticator
Autokosten Komplett Pro
Barcode Scanner+ Simple
Google Chrome
Chromecast
Docs
Downloads
Settings
ES File Explorer Pro + Theme
feedly
Fing
Google Fit
Google Photos
Android Device Manager
Gmail
Google
Google Drive
Google+
Hangouts
Google Calendar
Camera
Contacts
Google Maps
Google Messenger
MyTechnisat
Google News & Weather
Google Keep
Google Play Movies
Google Play Music
Google Play Games
Play Store
Google Presentations
Pulseway
RD Client Beta
Calc
SafeInCloud
Shazam pro
Sonos
Speedtest
Stocard
Google Streetview
Google Tables
Teamviewer
Phone
tinyCam Monitor pro
Google Translator
Google Clock
Weather Pro
WhatsApp
Wifi Analyzer
Youtube
Google Cloudprint
Google Now Launcher

k.s.deviate said:
I've tried all versions except a full CM ROM. So stock, beta, and a few different AOSP builds. I cannot reproduce any screen issues being reported here.
Is there maybe a common app that you all share? No one has mentioned whether you are rooted or not.
Click to expand...
Click to collapse
I'm running stock without root.
Reviewing the previous posters list of apps, the only things I have in common are the standard Google apps.

Stock without root.
The issue is still there even when rebooting in safe mode, so it seems to be unrelated to any installed app.
Time to RMA I guess.
Edit:
Just read this in a reddit thread:
Update: I've managed to fix my issue by reverting back to a 6.0.0 build and formatting the cache,system, and userdata using the fastboot tool during the new rom install.
Click to expand...
Click to collapse

Same issues here.. Just found that thread.. Got my phone yesterday and thought it might be a hardware issues and thinking of shipping it back.. But now..
Tried newest factory image unrooted, CM13, Bliss, DU every single ROM has it.
It also appears directly after bootloader I think, where you can lock your Phone before booting the real ROM.. It's a pain in the ass!

I have this too on my wife's phone. My 5x is fine. March update caused the right side of screen to go dead to touches after 6 seconds of non use...
So annoying ..