Hey everyone,
So I've been trying to "modernize" my phone, since I'm under the impression that I can get another 2-3 years out of it. So far I have:
-Running 7.1.1 stock rooted w/Franco kernel
-Hacked to include Pixel launcher (works great)
-Hacked to include Assistant (works great)
-Hacked to run Daydream (works great(ish)) -These tutorials are all available online and are pretty simple if you kinda know what you're doing
I bought a Daydream headset and have been playing with the apps. Some seem to work fine, and some won't run, some won't install. This seems like pretty fresh territory, so I haven't found much help online.
I know our phone supposedly doesn't meet the intended hardware specs (thermal characteristics, and GPU speed?), but it sure seems capable enough to me.
-Home screen and remote - works no problem.
-Playstore - works no problem.
-Netflix VR - works no problem.
-Arts & Culture - works no problem.
-Asteroids - This is pretty awesome. It's a demo of an animated episode (not the old game). It has 3D sound, which I wasn't expecting since the Netflix VR app didn't have it.
-Youtube VR - won't install (sideload). A little research, and it sounds like this app won't run on our phone's architecture. As far as I know, I can't force it to run. I'm very interested in getting this to work though.
-NextVR - Launches to blank screen.
-Hello Mars - works no problem. Lacking content it seems.
-JauntVR - works no problem.
-Littlestar - opens to non-side-by-side screen.
-InceptionVR - opens to non-side-by-side screen.
-Etc.. haven't tried very many yet.
For some of these, I wonder... I have my phone "posing" as a Pixel XL. I wonder if it would make a difference if I changed it to Pixel regular instead.
Anyhow, there must be others out there who are interested in exploring Daydream on our Nexus 6. Please share your experiences/expertise or point to relevant threads I may have missed!
Unfortunately I am in the same situation as you are, but I am just as interested in getting it resolved. The Daydream UI and the apps that are working actually work very well. What I found is the apps that are opening single screen are doing so because of our device info. I can go into the build.prop and edit the ro.product.device to marlin instead of shamu the app will open in a side by side screen. The only problem is that my phone reboots after running for a few minutes (even if I am not in daydream). I emailed the app developer of "AFFECTED:The Manor" and he said they will adjust the app requirements in their next update, but we can't expect everyone to be so helpful. We need to come up with a way to edit the build.prop info without causing rebooting. Keep me posted and I will do the same ...
Very cool, glad I'm not alone here.
I did notice that Netflix seemed to have picked out that my device was a Shamu, but luckily at least that app doesn't care.
FYI it looks like a bunch more apps just got added to the in-Daydream app-store. Going to try a few of those, and also trying to get google photos working.
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
zelendel said:
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
Click to expand...
Click to collapse
Yes good point. I personally am prepared for the worst, but yeah, disclaimer to others...
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
needleyepoke said:
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
Click to expand...
Click to collapse
Get what to work?
stev067 said:
Get what to work?
Click to expand...
Click to collapse
The daydream app... Isn't that what this forum is about?
needleyepoke said:
The daydream app... Isn't that what this forum is about?
Click to expand...
Click to collapse
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
stev067 said:
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
Click to expand...
Click to collapse
I'll go back and check my steps.. Thanks
stev067 said:
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Click to expand...
Click to collapse
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
adbFreedom said:
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
Click to expand...
Click to collapse
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
stev067 said:
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
Click to expand...
Click to collapse
Yea, I had tried all combinations one at a time and all at once and my device would always reboot. I found during the trial and error that only the ro.product.device was what the app was reading, but could not stop the rebooting.
Related
Just an FYI, I installed it and a bunch of stuff I couldn't find in the market before is there. ( I doubt it though )
http://www.megaupload.com/?d=P3SVF3IE
https://sites.google.com/site/droidlife24/home/Vending_2_2_11.apk?attredirects=0&d=1
Let me know what you think, I've had problems, so use at your own risk ( I should have put this earlier, I hope it didn't hurt anyone, as always back up first )
* I have been having wifi issues since this update. When it comes out of sleep the wifi wont connect automatically
might be jumping the gun trying market fix.
sixvoltsystem said:
might be jumping the gun trying market fix.
Click to expand...
Click to collapse
What do you mean? Did it not work?
Jim
sixvoltsystem said:
Just an FYI, I installed it and a bunch of stuff I couldn't find in the market before is there.
http://www.megaupload.com/?d=P3SVF3IE
https://sites.google.com/site/droidlife24/home/Vending_2_2_11.apk?attredirects=0&d=1
Let me know what you think
Click to expand...
Click to collapse
Cool.. Just loaded it on vegan beta 5.1. Seems to work just fine. Don't know if I see any more stuff, but never really had a problem finding things with the other ones.
I do notice that the appearance seems crisper. Like maybe they are using a higher quality. Or, maybe not.
Still the same for me. Stars still truncated. Missing apps still missing.
The new apk is about 600 MBA larger than earlier one.
Jim
Just for fun I went ahead and did the market fix again. Didn't need to but I saw the earlier post and was curious. I never could get it to open after the first reboot. Had to reboot again. Then once it started working I have noticed more of the "android.process.acore" errors, and server errors then with the older one. I will be rolling back to a previous version myself since this doesn't seem to really make anything better.
I wonder if there should be an updated GoogleServicesFramework with this?
Jim
jimcpl said:
I wonder if there should be an updated GoogleServicesFramework with this?
Jim
Click to expand...
Click to collapse
Kind of wonder that myself. Did you notice any difference in the look? Like a higher res look for the fonts? Or was I just seeing things? That would sort of make sense for the size difference of the file I guess..
And I thought I was doing good. LoL dag nabbit
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
sixvoltsystem said:
And I thought I was doing good. LoL dag nabbit
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
You did fine! Never know if it is cool or not until you try....
Sprdtyf350 said:
Kind of wonder that myself. Did you notice any difference in the look? Like a higher res look for the fonts? Or was I just seeing things? That would sort of make sense for the size difference of the file I guess..
Click to expand...
Click to collapse
It might be, but it's really hard to discern.
Jim
P.s. I went back also.
Sprdtyf350 said:
You did fine! Never know if it is cool or not until you try....
Click to expand...
Click to collapse
Ditto...
Jim
Works for me
I'm running vegan 5.1 with pershoots latest kernel and here are my findings thus far. I backed up market with titanium and installed the update, immediately opened market. Everything looks to be there, I searched for a few things and installed one or two. I looked for adw and couldn't find it, I did see its themes but not the app. Rebooted, loaded up market no fc's, until I tried to roll back to previous version to look for adw because I am almost certain it was there before. Interestingly I did see appbrain which I've never been able to get before. Never tried market fix, and did not notice any image improvement. Anyone know for certain what to look for to see if it actually improves previous market? I'm going to try and fix my market now and will report back if anyone's interested.
I installed via the apk (there is also an update.zip available) and all working well. No reboot or clearing Google Services Framework required.
I had previously preformed the well documented market fixes but could never quite get the entire market. Everything appears to show up now.
I'm not sure it is complete I can't find a few things. But then again I found a bunch of things I couldn't find before either. Catch 22 yet again.
anyone else having a problem with 'Media Volume' not working after this update? The rocker doesn't work, I tried to go in the settings (I had to unmute and turn the system sound back up - no dice), I even tried to play a video and turn up the sound using the software controls within that program....nothing works.
How do I revert back? Where is the old .apk located?
....also had to turn my wi-fi on with each reboot, which is new.
Running Vegan5.1
I think it would be most helpful if you guys actually listed the names of the titles of the apps that you either DO or DO NOT see once you have tried this. Just might help in the troubleshooting aspect. For what its worth.
ckelly,
search xda for market or vending.apk and you will find many versions to play with
Volume corrected on reboot #2.
Wi-Fi still needs to be manually connected..
@sixvolt
Since this appears to not improve things, you must have had even less apps show up than we did and this update brought you to par with the rest of us. Everything is relative
Hi,
Im just curious how to track down the reason for reboots with stock ROM and stock kernel, not rooted. I had one random reboot yesterday (when watching trailers in the IMDB app) after almost a week I own N7. I know that one reboot in a week is nothing, but its my new toy and Id like to know how to track down the reason for that in case it happens again.
I found out some threads about this and generally it says I should use LogCat - but I dont know how to use it. So I please ask for help! For now, I started Stability Test (CPU+GPU) and wait ...
Happy New Year, Y'all !!!
EDIT: Ghardashyan a bit lower mentioned hes been having reboots when watching youtube videos. Anybody else having this kind of behavior? Also, I had my reboot when watching trailers in the IMDB app - its playing via youtube, right?
The ONLY reboot I have ever seen, is when the default lockscreen widget gets updated by the marketplace. It's guaranteed to reboot on 4.2. It does it every time on both my Nexus 4 and my Nexus 7.
You will only ever see it, if you remove the default android 4.2 lockscreen time widget and put something else there from the marketplace, and only when that widget gets a marketplace file update.
Perhaps you are seeing this? Do you have auto-update apps enabled???
CrazyPeter said:
The ONLY reboot I have ever seen, is when the default lockscreen widget gets updated by the marketplace. It's guaranteed to reboot on 4.2. It does it every time on both my Nexus 4 and my Nexus 7.
You will only ever see it, if you remove the default android 4.2 lockscreen time widget and put something else there from the marketplace, and only when that widget gets a marketplace file update.
Perhaps you are seeing this? Do you have auto-update apps enabled???
Click to expand...
Click to collapse
I dont have auto-update enabled. I added another time/weather widget to the lockscreen but I dont think it got updated yesterday ... I will remove it and hope it wont reboot again. I sure think it was some app as the stability test goes for 2 hours without problem.
michalurban said:
I dont have auto-update enabled. I added another time/weather widget to the lockscreen but I dont think it got updated yesterday ... I will remove it and hope it wont reboot again. I sure think it was some app as the stability test goes for 2 hours without problem.
Click to expand...
Click to collapse
Its to do with location based services, HD Widgets is a major culprit and stated they were talking to Google to try and resolve the issue, it is also as stated before mainly because of the new lockscreen widgets, which HD Widgets also provide, so the stock widget could also cause the same issue?
Mine have pretty much stopped with the last update of HD Widgets, but it does still occur.
Wilks3y said:
Its to do with location based services, HD Widgets is a major culprit and stated they were talking to Google to try and resolve the issue, it is also as stated before mainly because of the new lockscreen widgets, which HD Widgets also provide, so the stock widget could also cause the same issue?
Mine have pretty much stopped with the last update of HD Widgets, but it does still occur.
Click to expand...
Click to collapse
Just for your information, I dont use HD Widgets
Since you're on stock rom and kernel, I think the best way would be to reset your device and keep track of what applications are installed, one at a time.
My guess is that one of the installed apps are causing it..
Sent from my Nexus 7 using Tapatalk HD
ajhn said:
Since you're on stock rom and kernel, I think the best way would be to reset your device and keep track of what applications are installed, one at a time.
My guess is that one of the installed apps are causing it..
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I know that, but as it was one reboot only in less than a week, it could take months to track the app down ... :laugh: Im about to restart the device myself and then use alogrec to continually record stuff.
EDIT: Alogrec is not recording a thing, so I rooted my phone. In case of restart, I believe it should be enough to save last_kmsg. Am I right?
michalurban said:
Hi,
Im just curious how to track down the reason for reboots with stock ROM and stock kernel, not rooted. I had one random reboot yesterday (when watching trailers in the IMDB app) after almost a week I own N7. I know that one reboot in a week is nothing, but its my new toy and Id like to know how to track down the reason for that in case it happens again.
I found out some threads about this and generally it says I should use LogCat - but I dont know how to use it. So I please ask for help! For now, I started Stability Test (CPU+GPU) and wait ...
Happy New Year, Y'all !!!
Click to expand...
Click to collapse
I get some occasional reboot when watching Youtube videos... Leaved the stability test for 2 hours, no reboots.
ghardashyan said:
I get some occasional reboot when watching Youtube videos... Leaved the stability test for 2 hours, no reboots.
Click to expand...
Click to collapse
I had my reboot when watching IMDB trailers - which also are on youtube, am I right??
BTW Is your problem repeatable? Eg. is there any time watching youtube that quarantees reboot? Id like to check that ... And are you using the youtube app?
REALLY?
Check out the thread 4.2 Random reboots instead of making new threads.
Sent from my GT-I9100
Correlation does not equal causation and it seems some are eager to go barking up the wrong tree. As has been stated here, as well as confirmed by Google, it is a bug at the OS level. It has nothing to do, per say, with HD Widgets, YouTube, or any individual app. It affects all products running 4.2 and 4.2.1.
Until Google fixes the issue, there are only two guaranteed workarounds- disable location services or downgrade to 4.1.2.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Correlation does not equal causation and it seems some are eager to go barking up the wrong tree. As has been stated here, as well as confirmed by Google, it is a bug at the OS level. It has nothing to do, per say, with HD Widgets, YouTube, or any individual app. It affects all products running 4.2 and 4.2.1.
Until Google fixes the issue, there are only two guaranteed workarounds- disable location services or downgrade to 4.1.2.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, never heard of that. How do I disable Location Services? Should I just turn off the Location access menu? Or is it a service under running services? In that case, which one?
michalurban said:
Thanks, never heard of that. How do I disable Location Services? Should I just turn off the Location access menu? Or is it a service under running services? In that case, which one?
Click to expand...
Click to collapse
Settings › Location. Bear in mind that the tradeoff is that, among other things, Google Now will no longer be functional.
For me, the reboots haven't been annoying enough to warrant disabling it on mine just yet.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Settings › Location. Bear in mind that the tradeoff is that, among other things, Google Now will no longer be functional.
For me, the reboots haven't been annoying enough to warrant disabling it on mine just yet.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Great, thanks. :good: I disabled that for now and will turn it on only when I need navigation. I dont use Google Now anyway.
BTW, when Google finds a solution for this, should I expect a full system upgrade?
Just experienced my first random reboot while streaming a flash video on Firefox Beta..
Random reboots are annoying me as well with my stock unrooted n7
Mostly though its during wifi/network activity not just in one app, have had reboots while in youtube, ebay, chrome etc. I have also seen it reboot while in standby
All started from 4.2
Would be interested to know if these reboots are reported back to google?
Sent from my Nexus 7 using xda premium
My Nexus 7 has 38 days uptime, only thing "special" I've done is I've disabled lockscreen widgets:
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard
Stock 4.2.1, rooted.
Unofficial, no warranty, express or implied. Not final, nothing to do with the CM people, not backed by them, not made by them, may cause corruption of innocent kittens if used irresponsibly. I am posting this only because the main CM sources are not perfect right now for building for Qualcomm devices just yet, and need some tweaks in new branches.
CM 10.2 Android 4.3 built for, and working on Pollux_Windy, once again thanks to Sony using such nice, open-source-friendly devices.
Working:
WiFi
Compass + sensors
Sound
Bluetooth
Front + Rear Camera
External SD (including ExFAT)
Not Working:
GPS
This is for the Pollux_Windy (SGP311) Wifi ONLY tablet. It should work on the SGP312 (32 GB wifi only) as well, but will NOT work on the Pollux (with LTE).
http://goo.im/devs/pulser/TabletZSGP311/CM10.2/cm-10.2-20130810-UNOFFICIAL-pollux_windy.zip
Tried to flash this but i'm getting an error about device build prop not matching requirements. I had a 312 rom on first, and flashed a 311 stock rom, but still get the error. My device is 311 by default.
Do i need to edit my build.prop? Even though my device shows as SGP311?
EDIT: Ah nevermind, i had the stock bootloader still installed. Doh!
If anyone needs Gapps I found them here:
http://forum.xda-developers.com/showthread.php?t=2378992
Sent from my SGP311 using xda app-developers app
Updated to 30 July build - includes the new Focal camera app. Yes, it has a few bugs with tablets and orientation. It's known.
Is root possible yet? I tried the supersu zip that was attached in op, but still needs the binary according to the supersu app. Do we need to adb push the binary?
Edit: Nevermind, just tried the latest supersu and works fine.
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
cjdalessio said:
I can't get a restricted user to work for the life of me. All kinds of processes are force stopping and I couldn't pick trebuchet from the list on setup either, though I did manage to work around that with Apex eventually, though Apex kept crashing too.
I assume apps might have to support this (or at least launchers?) But core processes?
I did dirty flash so it's possible that has something to do with it.
Still digging around. I'll clean flash later to retry restricted users too.
C
Click to expand...
Click to collapse
Restricted profiles are not tested or a priority right now in CM I believe.
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
andymg350 said:
Got this working on my xtz SGP311 seems really quick so far recovery plays nice, only real issues I've encountered is that the screen flickers black every now and then using the aosp browser and MX player pro doesn't work as android 4.3 isn't supported yet which has nothing to do with the rom.
WiFi and GPS seem to working used google maps to find a location and navigate there had no issues with those yet.
Definitely something different over the Sony ui and less cluttered just need the sony remote
Gonna have a play with it and see how I get on with it lots of options to play with hehe
Sent from my SGP311 using XDA Premium HD app
Click to expand...
Click to collapse
Check out the project by @Apache14 that brings infrared remote control support to non Sony ROMs!
Are you sure gps is working? I don't think it should be in this ROM...
I had a go at the open source IR by apache but had no luck getting it to work, but I'm not sure if I installed it right.
I'll have another play with GPS today as I've got more time and let you know I could have jumped the gun on this one lol. I quickly downloaded an app called GPS test and although it says the GPS is on it doesn't show anything else like coordinates or location I'll keep playing for now though.
Sent from my SGP311 using XDA Premium HD app
Updated 3rd August
Updated 7th August.
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
zylstrajs said:
Thanks a lot for throwing this together... everything seems to be working great, I'm impressed by focal.
I'm still struggling with is the absence of tablet UI (trying to hit the home softkey in landscape is impossible, so I've been forced to full!screen, which is working well), but it's a small price to pay for the jump from Sony's 4.1.2 to a functional 4.3 Rom.
Click to expand...
Click to collapse
Interesting. Out of interest, how do you use your tablet ? I'm just trying to work out if there is any link or difference - personally I thought the same, that tablet was good, until I used my Nexus 10... Then I was "sold" - tablet UI was sub-optimal. I tend to use the tablet with 2 hands - one holding it, another free across the top for use. I find keeping navigation to the centre more logical personally, and more ergonomic. It also keeps the notification tray at the top, consistent with the phone. At other times, I use the tablet as a "monitor" and type with a Bluetooth keyboard, where I do not interact with the touchscreen much (except at arm's length), and find phablet UI quite convenient. Moreso than I felt with tablet UI.
It's intriguing though. I am sure I can look at readding it some time, but I'm fairly busy so it will take a while. I noticed Sony seem to be moving to phablet UI for 4.2 as well though...
I hold mine on the sides and mostly interact with my thumbs, thus central on screen controls are hard to reach. But, to each his own. I also use Thumb Keyboard exclusively on my tablets, much more natural than trying to type with one hand holding with the other.
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
andymg350 said:
so yeah i finally got around to testing the GPS navigation and it just says "Searching for GPS" the whole time so confirmed its not working.
i also found a issue with the swipe to type on the AOSP keyboard as soon as i tried to use swiping it force closed the keyboard, not a big issue just thought id mention it.
i noticed you've done a couple of updates as well whats the best way to update the rom just flash as usual using the file in op?
Click to expand...
Click to collapse
Just like with CM nightlies, just flash the latest update right over whatever you have.
In rare cases other changes will be needed, maintainers will usually let you know in these cases.
I'm investigating GPS on 10.1 on the windy - it's proving to be a bit of a headscratcher, although it has many of the hallmarks of the same problem we had with the modem on mint (Xperia T) months ago. Unfortunately, we can't use the same fix/workaround we used on mint.
pulser, may want to check the CM10.1 thread for my SMD debugging patch, might give some useful info - although what I need to do is get a build environment together for stock kernels so I can apply that patch to .370 for comparison.
i hate to sound like a noob but i am still learning lol is it safe to just flash the updates with cwm or is it best to do it with the flash tool?
it seems like gps has got a lot of people scratching their heads at the moment but im sure with so many looking into it there is sure to be a solution soon
Edit: its OK I went ahead and flashed the update using cwm and it worked, I'm to impatient to wait lol but at least I've learned something
Updated to 10th August build
Will you continue to tweak now that official nightlies are out?
The problem
Hi, I've been experiencing significant interface stuttering whenever an application has been granted accessibility permissions.
Video of the problem
Here is a video demonstrating the issue, read below for technical information: https://www.youtube.com/watch?v=wFVKCx5zVmQ
Facts about the problem
Ok so here's what I know so far:
It doesn't matter which service you grant access to, it will lag the same. I've tried LMT, Swipe Navigation, LastPass, TalkBack, and a few more I can't even remember at the moment.
It doesn't matter what ROM or Kernel you are on. I've tried Euphoria with LK and Hydra, rooted stock with stock kernel and LK, and Benzo with whatever the default Benzo kernel is. Doesn't make a single difference.
It does not only affect Relay for Reddit comment collapsing. It also affect Google Newsstand's mini/big card transition, news source transitions, Google Now transitions, basically anywhere there is an animation in the OS I can notice the stuttering.
Anyone else experience this? Any ideas? It is driving me crazy.
I'm not experiencing that
I've used custom roms/kernels almost all of them in the development forum lol
I wonder if maybe it's a particular accessibility itself? I feel like since its needing to be authorized in accessibility that it might be conflicting with something else, who knows?
People usually try booting the phone into safe mode and seeing if maybes its a third party app?
Thats my 2 cents! Hopefully it helps
It has nothing to do with a specific accesibility from what I can feel, stuttering occurs regardless of the app.
I have full wiped several times to test and can't find a solution.
Does anyone else experience this or have any ideas?
Can anybody duplicate this?
Should I RMA?
ggmask said:
Can anybody duplicate this?
Should I RMA?
Click to expand...
Click to collapse
adjust your governor/scheduler. me, i like using ondemand/deadline.
simms22 said:
adjust your governor/scheduler. me, i like using ondemand/deadline.
Click to expand...
Click to collapse
I've done this when using LK/Hydra, but I am not running stock kernel. None of the adjustments made any noticeable difference unfortunately
I really hate to bump this but the video only has 16 views and I'd love someone else to confirm or deny the same behavior when granting an app accessibility permissions.
If this is common behavior I won't RMA, but if no one else can recreate this I'm going to.
Oh, another thing I noticed: you don't have to test it in an app like Relay for Reddit, you can also do it in the Chrome browser on a site that has a lot of information. What I've noticed is that, when accessibility is granted to any app, visiting XDA forums becomes almost unusable. It takes FOREVER to scroll and when I can scroll it is extremely choppy. Disable the accessibility permission? Completely solves the problem.
You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.
Here is the Swipe Navigation developer saying it is definitely a thing in Lollipop with accessibility settings. (screenshot from Play Store comments on Swipe Navigation app). I wish someone could figure this out - I guess we have to wait for Google to do that?
I am using PieControl Pro and I do believe it makes the animations in the Play story stutter when I open a page and use the back button to go back to the app overview. The Play store was never completely smooth no matter what, but when I disable accessibility for PieControl Pro, it becomes a little better. So yeah, accessibility does seem to affect UI performance. I'm on stock Android 5.1 with Franco Kernel.
wbarnes4393 said:
You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.
Click to expand...
Click to collapse
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.
Im using swipe navigation and I'm noticing stutter as well. Wonder why this happens. Took me a while to figure it out.
Would you mind pointing me to the Google page where you reported this? I would like to star it as well, and follow their updates.
As a follow up, today I decided to tinker around and install pie again. Since the Nova app drawer animation is what I always notice stuttering first, I decided to just turn Nova animations off. Then, I went into Android settings, developer options, and reduced the three animation settings to 0.5x. I may just be seeing what I want to see, but the UI hasn't seemed to stutter with Pie enabled in accessibility (yet). Going to try this for a day or two.
I've gotten the same issues with Lastpass.
Lastpass even states on their site that it's a lollipop issue.
https://lastpass.com/support.php?cmd=showfaq&id=8166
ggmask said:
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.
Click to expand...
Click to collapse
Sorry if this counts as bringing up an old thread, although it's not THAT old
Anyway, I've come here just to corroborate all your findings and confirm that I am also experiencing this ugly bug. A few days ago I installed Greenify which, among other things, asked to enable Accessibility features for it. Thinking nothing of it I did as requested. Next day I start noticing some UI lagginess and choppiness, which was especially noticeable to me in Relay for Reddit since I use it a lot (too much for my own good in fact) and I distinctly remember it had very smooth scrolling between comments just a few days ago. In the mean time, I completely forget I've granted Greenify accessibility control so I went on a mission trying to fix this inexplainable, sudden UI choppiness, by trying to flash a different kernel, trying different governors, dirty flashing my ROM, trying all the other tweaks, and finally doing a factory reset and flashing the stock ROM all over again (luckly I did make a nandroid). Nothing helped. I was at my wits end when I tried searching the app's subreddit for anyone experiencing the same issue and found a comments saying accessibility features were to blame. I felt stupid for not researching it before. However, this bug is very insidious as it just creeps up on you, with no reason. I also don't know how can accessibility features affect UI smoothness this way.
Yes, hopefully will be fixed in M maybe? I haven't checked around to see if those who have installed M preview have checked to see if the bug has been fixed there. Fingers crossed.....
Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092
wbarnes4393 said:
Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092
Click to expand...
Click to collapse
Still isnt fixed ) But my lag rather appears when tapping on any app icon, then it highlights, then go lag, then opening animation starts.
Post this over on reddit and see if you can bring a bit more attention to the issue.
Cine Shot (Partial Motion Still Photos) working on LG V30 - APP link & Instructions.
Hey all, been a while since I've had any new discoveries because I have been busy with a move across the country, but I think this one was worth waiting for :good:
This post is a tough one to categorize, as its an "app" and its a "mod" but I also needed to include a little guide to help you all get it working. So I went with the Apps and Mods section, but if an Admin thinks this should go in the Guides section, I am totally cool with that.
Pre Install Notes:
This has been tested on my Rooted & Frankensteined LG V30 ThinQ LS-L998 on Sprint running US99827a software Security Patch Jan 1.19.
I do not know if this will work on non rooted devices simply because I haven't been able to test it on one. I do believe that this will work the same on a non-root V30 but I'll wait for confirmation from one of you... SOOOO if you have a non rooted device and you try this out, please let us know if its working.
Thank Yous:
A big thanks to @trouble. for requesting the G8 stock system apps in the G8 section & thanks to @iknow786 for originally providing the files which I used to make the link to the cineshot app below. If I did not happen across that thread we wouldn't have this new trick, so thank you both. Also a big thanks to all of the awesome folks that have kept the V30 development alive and kicking this long into the devices lifecycle. Very cool to see so many talented people still doing things for this community every single day. I cant begin to list everyone, but if you are active in here, you know who the folks are that have been grinding away at this all this time.
Ok so lets get you CineShooting!
Step 1) Go to the following link...
https://docs.google.com/uc?export=download&id=1Pxy8B1k19Q8ALiHc1FeYUHb3c8y4DnJI
Steo 1a) Download, and install the CineShot apk.
(Im hosting this on one of my drives, so if anyone has issues with the download, now or months from now, PM me and I'll fix it. If its a while from now and you just write "dead link" in this thread I prob won't see it, so that's why I am recommending a PM. )
(Since I have not yet figured out how to integrate this new app into our camera app, you will need to launch the CineShot main process using one of the programs I will mention in step 2. I am including some screenshots for those new to this. Hopefully this post will be updated in the future with how to integrate the cineshot capabilities into the regular camera section, but for now this is what we have)
Step 2) Once you have installed the CineShot apk to your device you will need a shortcut maker program to access it.
Personally I am partial to Shortcut Master, https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite&hl=en but other apps like "QuicksShortcutMaker" https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut&hl=en_US (tested and works) should word as well. So if you don't already have one, download one of those two or your own favorite.
Step 2a) Open your shortcut program and find CineShot by either scrolling to it or searching "Cine" or "CineShot". No matter which program you used you should see at least one option under the CineShot app ending with the words ".MainActivity ". Go ahead and favorite or create shortcut for this process, as you'll want to have a quick way to get back to CineShot mode. Now go ahead and click that option and your device should launch into cineshot mode.
Cine Shot Mode - How-To:
Pretty basic stuff here. Point and shoot at whatever you want (objects should be moving in your frame otherwise your just taking a normal picture). It will record 3 seconds. After it stabilizes your "video" it will then show you options to draw with your finger on the moving parts of the images that you still want to move. Do this, and then save. You now have a cineshot image with partial movement of the image.
That's it. Pretty easy stuff. If you followed the very simple steps you should be able to record using either your front or back camera, and cineshot should be fully working, or at least as fully as it can on our devices. Enjoy.
I don't have any fun stuff nearby to post a good example of a cool Cine Shot Pic, so if you guys and gals take any, please share so people can see what the fuss is about.
And as always, feel free to share the love with a click on that "Thanks" button if this post helped you out
*** Reserved for future post - updates ***
Side Note: From that same cache of G8 apks, I was able to get the My Avatar app partially working using the same steps as above but with that specific APK obviously. Unfortunately, while it will take my picture, it will not spit out an avatar, so some sort of framework or back end stuff is not enabled. Anyone that has access to the newer devices with this, if you can find the additional necessary files, we could prob get this working too.
Anyone interested in checking out the G8 stock apps in the original thread I mentioned above can find that thread here: https://forum.xda-developers.com/lg-g8/themes/lg-g8-preinstalled-apps-t3904050
Other apps that I got to install from the g8 are these: Humanavatar (My Avatar) LGContentsettings (Wallpaper and Theme. Not sure what this updates though) and an update to the Tasks app.
Be cautious installing things you don't know anything about. As always, its your phone, so beware, and there are no guarantees yada yada yada.
It doesn't integrate with the camera because only camera apps built for pie onwards have that functionality. Once enabled in camera config files it crashes the camera app immediately.
TotallyAnxious said:
It doesn't integrate with the camera because only camera apps built for pie onwards have that functionality. Once enabled in camera config files it crashes the camera app immediately.
Click to expand...
Click to collapse
Any idea why it crashes it? I mean other than it wasnt meant to work. Since the actual mode is functional I wonder if anything is actually missing in the Oreos framework/camera that needs to be there.
JonnyTrulove said:
Any idea why it crashes it? I mean other than it wasnt meant to work. Since the actual mode is functional I wonder if anything is actually missing in the Oreos framework/camera that needs to be there.
Click to expand...
Click to collapse
The app doesn't have the shortcut built in. Only camera apps built for pie or newer have it. It's not framework. It's just the camera app.
TotallyAnxious said:
The app doesn't have the shortcut built in. Only camera apps built for pie or newer have it. It's not framework. It's just the camera app.
Click to expand...
Click to collapse
Gotcha. That makes sense.
I'm glad you commented, as I was going to message you to ask your opinion on the My Avatar creation feature I mentioned after the original post. I can get it to snap a pic of my face, and it recognize I'm a person and takes the pic, but when it goes to process and spit out an Avatar it fails.
Since you're a good bit more advanced than I am, maybe you had an idea about what's keeping it from working.
JonnyTrulove said:
Gotcha. That makes sense.
I'm glad you commented, as I was going to message you to ask your opinion on the My Avatar creation feature I mentioned after the original post. I can get it to snap a pic of my face, and it recognize I'm a person and takes the pic, but when it goes to process and spit out an Avatar it fails.
Since you're a good bit more advanced than I am, maybe you had an idea about what's keeping it from working.
Click to expand...
Click to collapse
It'll likely be working on Pie. I've made a list things I'm not going to attempt till we get pie.
How did u install humanavatar? Is it good? Like ios
Works on V20D non rooted...
Appreciate it
trouble. said:
How did u install humanavatar? Is it good? Like ios
Click to expand...
Click to collapse
It installs normally but won't actually produce an Avatar. It trys to process the pic and then it fails.
JonnyTrulove said:
It installs normally but won't actually produce an Avatar. It trys to process the pic and then it fails.
Click to expand...
Click to collapse
Yep Same here
This is cool! Thanks!
Sent from my LG-US998 using Tapatalk
iIf you use Nova Launcher you can make a shortcut natively by making a new widget and choosing "activities".
Sent from my LG-LS998 using XDA Labs
APK file
There is a chance we can use modular downloadable camera modes using the same technique
Food mode, 360 panorama, square mode, ar, avatar, etc
We need to get those APK from LG g7/v40 oreo