Just want to compare to others as of what I may have found. After rooting my watch and installing the custom rom from janjan I was still getting the random lag. I decided to try my hand at removing a few apps just in case it could be one of the of those. I removed a few apps installed by my phone as I don't use them but the lag was still there. Lastly I removed the zenwatch manager (the app used for some custom watch faces and a few features that are not all that super useful). After removing this I have not noticed any more random slow downs. Will report back after a few more days but I think that this may solve the random lag issue.
Only beware; you'll lose the upper and lower button functionality.
re: disabling zenwatch manager
nicolahinssen said:
Only beware; you'll lose the upper and lower button functionality.
Click to expand...
Click to collapse
That's the first thing I thought of too but after disabling zenwatch manager
by freezing it on my S7 Edge phone both of the programmable buttons still
worked fine and remain programmable.
I even checked to see if I can still re-assign the top and bottom buttons and
found that I could just like before I froze zenwatch manager.
After freezing zenwatch manager I still have the zenwatch manager icon in my watch along
with all the other apps but when clicking on it it tells me to install zenwatch manager so I
know that after freezing it it no longer is functioning on my watch.
So far I can tell the difference before&after freezing/disabling zenwatch manager and I have
found that I can feel and see the difference and it is true that without zenwatch manager the
watch is noticeably faster and quicker without any lag or stuttering.
My zenwatch 3 also suffered from a lot of random lag, stuttering and unresponsiveness
before I froze/disabled zenwatch manager. My watch is not rooted and I am not using twrp.
It's 100% stock waiting patiently for the Android Wear 2.0 update.
@texanman is right about zenwatch manager.
Have a great day!
I had switch to an old iphone, while I'm waiting for my new one to come and paired the watch. Now the watch is flying, no lag at all, everythings is super smooth. So weird...
I'll try this when I switch back to android. Should I install Zenwatch Manager and then disabling it ? Or is it working too if I just not install it ?
re: zenwatch Manager
Habaddon said:
I had switch to an old iphone, while I'm waiting for my new one to come and paired the watch. Now the watch is flying, no lag at all, everythings is super smooth. So weird...
I'll try this when I switch back to android. Should I install Zenwatch Manager and then disabling it ? Or is it working too if I just not install it ?
Click to expand...
Click to collapse
Zenwatch Manager has never been a requirement, it's an optional add-on.
It can be installed before or after setting up the watch, it does not matter.
Good luck, have a great day!
Misterjunky said:
Zenwatch Manager has never been a requirement, it's an optional add-on.
It can be installed before or after setting up the watch, it does not matter.
Good luck, have a great day!
Click to expand...
Click to collapse
Ok I tried it, is the remap button app linked to zenwatch manager ? It wasn't appearing until I installed it. So I uninstall it after and reboot, now it feel snapier than before on android, thx
re: zenwatch manager
Habaddon said:
Ok I tried it, is the remap button app linked to zenwatch manager ? It wasn't appearing until I installed it. So I uninstall it after and reboot, now it feel snapier than before on android, thx
Click to expand...
Click to collapse
You are right, zenwatch manager did contain the required firmware patch for the remap buttons
and the first time we installed the updated zenwatch manager it flashed the firmware patch to
the watch's firmware get the two remap'able buttons to work.
Once zenwatch manager flashed the remap button patch there is no more
need for zenwatch manager for that purpose.
Android Wear 2.0 will not need zenwatch manager for the firmware patch
because the new v2.0 firmware will already have the remap feature in it.
Good luck, have a great day!
Misterjunky said:
You are right, zenwatch manager did contain the required firmware patch for the remap buttons
and the first time we installed the updated zenwatch manager it flashed the firmware patch to
the watch's firmware get the two remap'able buttons to work.
Once zenwatch manager flashed the remap button patch there is no more
need for zenwatch manager for that purpose.
Android Wear 2.0 will not need zenwatch manager for the firmware patch
because the new v2.0 firmware will already have the remap feature in it.
Good luck, have a great day!
Click to expand...
Click to collapse
We have to wait and actually see what Asus did to 2.0. I would not jump to conclusion just yet, even if it is highly possible the stock remapping function could be there.
And the zw manager is not needed for remapping to work. First time you push any button the button remap app will show up
re: rooting
texanman said:
Just want to compare to others as of what I may have found. After rooting my watch and installing the custom rom from janjan I was still getting the random lag. I decided to try my hand at removing a few apps just in case it could be one of the of those. I removed a few apps installed by my phone as I don't use them but the lag was still there. Lastly I removed the zenwatch manager (the app used for some custom watch faces and a few features that are not all that super useful). After removing this I have not noticed any more random slow downs. Will report back after a few more days but I think that this may solve the random lag issue.
Click to expand...
Click to collapse
I already booted and installed twrp recovery, so far all the rooting instructions that I have
read all say that after rooting we will still not get a writeable /system which means it will
not be possible to edit the build--prop file or any other file which is located in /system .
How did you root your watch? - Did you use any of the methods outlined here in this
xda zenwatch 3 forum? - If you have used any of the methods here in this forum did
you check if /system is read and writable ?
Thanks in advance.
Just a note...
I disabled the ASUS Manager but was still laggy.
Used "Advanced settings" app to clear all data in ASUS Manager
Lagginess FINALLY gone
Hopefully it will stay that way
Any way to apply this fix to AW 2.0? I mean i did what @WaxysDargle did but i still see stutters and lag (especially when using play music).
thagabe said:
Any way to apply this fix to AW 2.0? I mean i did what @WaxysDargle did but i still see stutters and lag (especially when using play music).
Click to expand...
Click to collapse
i did this on 2.0.
make sure to disable the app, force stop it and then clear all the data. you may need to force stop and clear data a couple of times
I also found that adjusting the animation scale from 1x to 0.5X or none helps. this is under the developer options settings.
WaxysDargle said:
i did this on 2.0.
make sure to disable the app, force stop it and then clear all the data. you may need to force stop and clear data a couple of times
Click to expand...
Click to collapse
so disabling the app also disables the watchfaces and the "dock mode" face, right? at least this did for me. I'm fine using watchmaker, but would like to keep the night time dock screen.
is there a way to enable this after disabling the app?
thanks!
jco23 said:
so disabling the app also disables the watchfaces and the "dock mode" face, right? at least this did for me. I'm fine using watchmaker, but would like to keep the night time dock screen.
is there a way to enable this after disabling the app?
thanks!
Click to expand...
Click to collapse
i believe this is the case for me too. i actually lost all of my watch faces.
i have no idea if what you are asking is possible, but i seriously doubt it. you might be able to find an APK somehwere and sideload it for the watchface only.
personally, i forgot all about the watch faces when the laginess vanished. watch was unusable out of the box.
Do you all recommend disabling the Zen Manager app on your phone or on your watch (or both)?
Hoping to get better performance.
Thanks!
jpzsports said:
Do you all recommend disabling the Zen Manager app on your phone or on your watch (or both)?
Hoping to get better performance.
Thanks!
Click to expand...
Click to collapse
from my understanding, the ZM app on the phone is NOT required.
as I mentioned earlier, I tried disabling the app on the watch, but did not see any difference.
i'm going to try some other settings adjustments (including disabling the fitness app) to see if that helps.
also trying to disable "smart reply" and just keep "ok google" enabled.
I tried all of these things and none of them had a significant impact on the watch's responsiveness or speed.
The thing that finally fixed my lag was editing build.prop and changing debug.composition.type to gpu in the two places it appears. I also changed ro.core_ctl_min_cpu from 2 to 4, removed zenfit from /system/apps, and disabled Zenwatch Manager from the watch (couldn't find an apk for it on the filesystem). The gpu parameter fixed the lag - it's just about completely gone and the UI is about as smooth as my Moto 360 v2, and I think the min CPU setting is responsible for significantly speeding up actions like launching assistant.
I've been meaning to post a writeup but haven't had the time. Two threads that were extremely helpful are this one and this one (linked to from the first). The only downside to following these instructions is I get a warning about the OS not being validated because dm-verify is turned off. Not sure if I can turn it back on with a modified build.prop, but I'm not concerned because I finally have a smooth, properly functioning watch.
saturnspike said:
I tried all of these things and none of them had a significant impact on the watch's responsiveness or speed.
The thing that finally fixed my lag was editing build.prop and changing debug.composition.type to gpu in the two places it appears. I also changed ro.core_ctl_min_cpu from 2 to 4, removed zenfit from /system/apps, and disabled Zenwatch Manager from the watch (couldn't find an apk for it on the filesystem). The gpu parameter fixed the lag - it's just about completely gone and the UI is about as smooth as my Moto 360 v2, and I think the min CPU setting is responsible for significantly speeding up actions like launching assistant.
I've been meaning to post a writeup but haven't had the time. Two threads that were extremely helpful are this one and this one (linked to from the first). The only downside to following these instructions is I get a warning about the OS not being validated because dm-verify is turned off. Not sure if I can turn it back on with a modified build.prop, but I'm not concerned because I finally have a smooth, properly functioning watch.
Click to expand...
Click to collapse
Editing the build.prop on the phone or watch? And if so, I presume you have rooted the watch?
Sent from my XT1254 using XDA-Developers Legacy app
I didn't root. Fundamentally all you need to do is get the watch booted into twrp one time so you can mount /system, adb pull build.prop, make the edits I mentioned, then adb push it back and reboot.
Related
If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.
just to clairfy...mine is laggy all the time. I am probably wrong considering it is 830am but it said s-health and private mode only...does that mean that module will only fix the lag
when using s-health?
installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...
RomBox said:
installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...
Click to expand...
Click to collapse
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?
are you using ART or DALVIK as your runtime?
Shtihi said:
are you using ART or DALVIK as your runtime?
Click to expand...
Click to collapse
You can't use Xposed with ART yet.
Batfink33 said:
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?
Click to expand...
Click to collapse
disabled S Health use TB and installed xposed back, so far no lag noticed...
Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!
prophet42 said:
Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!
Click to expand...
Click to collapse
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY
asia559571 said:
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY
Click to expand...
Click to collapse
First think I did out the box =)
Along with removing touchwiz, switching off certain google now features (such as "OK Google" detection), and removing flipboard.
Always slowed the animations down since the days of the Galaxy S 3. S Voice and health are the first things I remove since the S5.
It helps a little, but unfortuntely the lag is still there (well unless I leave it a split second for it to load).
But that's something I can live with. Thanks anyway. Anyone who doesn't done it, it will help.
Although one interesting side effect is the accessability options mess up, so now the calculator talks to me lol.
But hopefully that will be addressed soon. There are other threads on that subject.
Wanam xposed module already has these functions built in. Been using it since day 1. No need for a separate module guys
badwolf94 said:
If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.
Click to expand...
Click to collapse
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk
Rayan said:
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
Yeah this pretty much, the thread was made back when Note 4 first came out and their wasn't any custom ROMS available. All of the ROMS to-date have the necessary fixes enabled.
I have both private mode and S Health running without any problems or lag. Running Firekat v. 8, Xposed. Disabling secure storage in Xposed is the key.
sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
I wish it was as simple as editing the Build.prop file... But no, for some reason DynamicKat's Secure Storage does not work for me even though it comes with the required settings on build.prop
No matter what I throw at it, paches, fixes, editing build.prop, disabling SHealth, xposed modules, etc, it simply refuses to work.
But the good thing is that at least on Firekat it does work flawlessly as I've mentioned before.
Cheers!
wipe cache and data of s health in app settings, you will have it running again, I have no lags
Hi guys, so i just rooted my T-mobile galaxy note 4 yesterday using the guideline. However, i have been experienced some problems with the phone:
1. Increase lagging when using Go keyboard, GoSMS,launch app, sometime freeze when flip through stock launcher...
2. Softcard is not working, so i install Xposed framework and download RootCloak. I dont know if this can intefere with the system?also no longer using update software in setting.
3. The stock camera occasionally failed to launch,or if it does launch, all i see is a black screen, and i can't figure out the reason?
Please help,any suggestion at all to what maybe the cause of all this?
PS: If i want to unroot and go back to stock T-mobile rom before how can i do it? And is it possible to un trip Knox?
Thanks!
re: issues
BADBOY1412 said:
Hi guys, so i just rooted my T-mobile galaxy note 4 yesterday using the guideline. However, i have been experienced some problems with the phone:
1. Increase lagging when using Go keyboard, GoSMS,launch app, sometime freeze when flip through stock launcher...
2. Softcard is not working, so i install Xposed framework and download RootCloak. I dont know if this can intefere with the system?also no longer using update software in setting.
3. The stock camera occasionally failed to launch,or if it does launch, all i see is a black screen, and i can't figure out the reason?
Please help,any suggestion at all to what maybe the cause of all this?
PS: If i want to unroot and go back to stock T-mobile rom before how can i do it? And is it possible to un trip Knox?
Thanks!
Click to expand...
Click to collapse
With all of those play store apps you have installed it's a wonder
that you don't have even more issues than you are already having.
Uninstall the Go keyboard and all the Go applications then reboot
your phone so you can find out whether they are to blame for your
lagging and freezing. Be sure to make the stock keyboard as default.
None of the play store apps have yet been updated for our new phones
so many of them are not fully compatible yet and some of them do not
play nice with some of the default apps which comes with our phones.
Especially the xposed and it's modules can and sometimes do interfere
with the normal operation of our new phones and some of it's apps.
The developers of xposed will hopefully start updating it soon so it will
be a lot more compatible with our phones and will no longer have issues.
I am fairly confident that if you uninstall xposed framework and it's modules
then reboot the phone you will no longer have those issues you mentioned.
And no, you cannot un-trip knox...........
Good luck!
BADBOY1412 said:
Hi guys, so i just rooted my T-mobile galaxy note 4 yesterday using the guideline. However, i have been experienced some problems with the phone:
1. Increase lagging when using Go keyboard, GoSMS,launch app, sometime freeze when flip through stock launcher...
2. Softcard is not working, so i install Xposed framework and download RootCloak. I dont know if this can intefere with the system?also no longer using update software in setting.
3. The stock camera occasionally failed to launch,or if it does launch, all i see is a black screen, and i can't figure out the reason?
Please help,any suggestion at all to what maybe the cause of all this?
PS: If i want to unroot and go back to stock T-mobile rom before how can i do it? And is it possible to un trip Knox?
Thanks!
Click to expand...
Click to collapse
Go products run so much in background they not worth using. Instant lag.
NOTE 4
Misterjunky said:
With all of those play store apps you have installed it's a wonder
that you don't have even more issues than you are already having.
Uninstall the Go keyboard and all the Go applications then reboot
your phone so you can find out whether they are to blame for your
lagging and freezing. Be sure to make the stock keyboard as default.
None of the play store apps have yet been updated for our new phones
so many of them are not fully compatible yet and some of them do not
play nice with some of the default apps which comes with our phones.
Especially the xposed and it's modules can and sometimes do interfere
with the normal operation of our new phones and some of it's apps.
The developers of xposed will hopefully start updating it soon so it will
be a lot more compatible with our phones and will no longer have issues.
I am fairly confident that if you uninstall xposed framework and it's modules
then reboot the phone you will no longer have those issues you mentioned.
And no, you cannot un-trip knox...........
Good luck!
Click to expand...
Click to collapse
In all honesty this lag issue is a wide spread issue, not sure if it's a phone batch issue or what but I took mine back to tmobile and even they say people have called to exchange device due to extreme lag where the phone will be un responsive, the camera won't work, switching between apps can to 10 to 30 seconds to switch, and I'm sure most these are normal users. In terms of performance the note 3 ran circles around the note 4 so far until we can a debloated custom rim, I think we're finally seeing that bloat ware be phone experience killers. Just to see the difference I had over 400 apps, xposed mods, etc installed on my note3, everything handled smooth even while trying to make it crash running a tweaked rom.
Sent from my SM-N910T using Tapatalk
Try a benchmark test a few times. I think that ***** slaps the cpu and wakes it up. Seriously, it helped on my phone.
BTW. My geekbench score was lower than an 801 snapdragon.
so i install Xposed framework and download RootCloak.
Click to expand...
Click to collapse
Wasn't there a problem with Xposed slowing things down and breaking things?
dkb218 said:
Wasn't there a problem with Xposed slowing things down and breaking things?
Click to expand...
Click to collapse
yes, but no. I think it was more of a root problem since root broke S health which made our phones lag like a mother. I really havent noticed any lag with exception of the task manager since having it though.
Misterjunky said:
With all of those play store apps you have installed it's a wonder
that you don't have even more issues than you are already having.
Uninstall the Go keyboard and all the Go applications then reboot
your phone so you can find out whether they are to blame for your
lagging and freezing. Be sure to make the stock keyboard as default.
None of the play store apps have yet been updated for our new phones
so many of them are not fully compatible yet and some of them do not
play nice with some of the default apps which comes with our phones.
Especially the xposed and it's modules can and sometimes do interfere
with the normal operation of our new phones and some of it's apps.
The developers of xposed will hopefully start updating it soon so it will
be a lot more compatible with our phones and will no longer have issues.
I am fairly confident that if you uninstall xposed framework and it's modules
then reboot the phone you will no longer have those issues you mentioned.
And no, you cannot un-trip knox...........
Good luck!
Click to expand...
Click to collapse
I tried,lagging still happen and more frequently when im using sammy stock launcher touch wizz. I did delete xposed and all module, factory reset everything but lagging still happen, please any know how i can get the stock un root rom, this lagging is super annoying
dkb218 said:
Wasn't there a problem with Xposed slowing things down and breaking things?
Click to expand...
Click to collapse
No, its work fine, the lagging happened b4 i installing xposed
knarfies said:
yes, but no. I think it was more of a root problem since root broke S health which made our phones lag like a mother. I really havent noticed any lag with exception of the task manager since having it though.
Click to expand...
Click to collapse
Will uninstall Shealth get rid of the problem?
BADBOY1412 said:
Will uninstall Shealth get rid of the problem?
Click to expand...
Click to collapse
I would used xposed and use wanam. Use it to use the secure storage fix. Clear s health cache and data and reboot. This will fix the lag.
I have installed the stable OOS 4.0 Nougat build and activated Daydream with a small hack ( https://forums.oneplus.net/threads/...ream-vr-fully-running-on-op3-oxygenos.479505/ ) but while it seems to work on the OnePlus 3 it does not seem to work on the OnePlus 3T properly. YouTube VR crashes after a few seconds as well as the Daydream app.
http://vulkan.gpuinfo.org/displayreport.php?id=987
What is missing?
MaluNoPeleke said:
I have installed the stable OOS 4.0 Nougat build and activated Daydream with a small hack (... ) but while it seems to work on the OnePlus 3 it does not seem to work on the OnePlus 3T properly. YouTube VR crashes after a few seconds as well as the Daydream app.
...
What is missing?
Click to expand...
Click to collapse
It seems, that I have the same issue with my Oneplus 3t. The Daydream app itself is working properly, but when the "VR-View" should start, it crashes. Thanks for any help.
MaluNoPeleke said:
I have installed the stable OOS 4.0 Nougat build and activated Daydream with a small hack ( https://forums.oneplus.net/threads/...ream-vr-fully-running-on-op3-oxygenos.479505/ ) but while it seems to work on the OnePlus 3 it does not seem to work on the OnePlus 3T properly. YouTube VR crashes after a few seconds as well as the Daydream app.
http://vulkan.gpuinfo.org/displayreport.php?id=987
What is missing?
Click to expand...
Click to collapse
I haven't experienced any issues with YouTube VR or the Daydream app. The only issue that I've seen is getting Google Play Movies to run....audio plays, but no visuals? I'm using the Daydream headset, so maybe that is why I haven't seen the issues you are having. Have you recalibrated your sensors in the menu after pressing *#808#
I've not had any problems with the daydream app either. No crashes, no warnings when I use the daydream headset. Only headache I've got is play store doesn't recognize my phone as daydream compatible so I end up having to side load everything...
Ok... I was wrong. Daydream tells me it's not compatible too. Grrr
simpsojp said:
Ok... I was wrong. Daydream tells me it's not compatible too. Grrr
Click to expand...
Click to collapse
After you modify "handheld_core_hardware.xml" you need to restart. The Daydream App will then work fine and show up in your Playstore installed apps. Also the Daydream Keyboard and Google VR services will be available to you.
Yeah. That wasn't working.
I uninstalled everything, rebooted, then reinstalled everything, cleared play store cache and data, rebooted, and seems to be working again...
I heard you need QHD for daydream?
Shatter their dreams! and haunt their nightmares !
Any tips on getting the daydream to work on the 3T? I flashed the Magisk module and the daydream app, keyboard and vr services all show in the play store. When I push the headset button in the daydream app it gives instructions in inserting the phone and then the app crashes to the home screen. The controller is paired also. Tried clearing data on all the apps and rebooting. Do any of the daydream apps have to be moved to /system/app?
Got it going using resurrection remix ROM and a couple of extra lines of XML.
larsdennert said:
Got it going using resurrection remix ROM and a couple of extra lines of XML.
Click to expand...
Click to collapse
By
larsdennert said:
couple of extra lines of XML
Click to expand...
Click to collapse
you mean the couple of lines already known, or some extra lines besides that? If the latter, please share it with us or point to a link.
On my 3t the
Code:
<feature name="android.software.vr.mode" />
was already enabled in the XML, theoretically we only need to add the
Code:
<feature name="android.hardware.vr.high_performance" />
. I added both lines anyways, it cannot hurt. But nothing shows up as compatible in the app store even after multiple reboots. I know I can side load, but how is it possible that it works for some and doesn't work for others? This should be deterministic! I like Monte Carlo algorithm, but in this case I don't like stochasticity.
IMHO the 1920x1080 resolution is a huge help for the GPU and CPU while running VR or any 3D apps (even 2D apps). The Pixel XL has to sweat 1.77 times as much as the 3t, no wonder why people report that it's burning hot. Not to mention that Daydream is not optimal for heat dissipation IMHO.
Resurection Remix rom
Modify /system/etc/permissions/handheld_core_hardware.xml with the lines you posted. (As always make sure your root editor applies proper file permissions when editing a system file)
They may be commented out and already there.
Side load VR Services, Daydream and Daydream Keyboard from www.apkmirror.com
Clear data on Play Store and Play Services. Can't remember if there was another apk to clear and then reboot.
Some games crash but if the daydream intro setup works you should be good. If daydream crashes then go into its settings and tap on the build repeatedly to enable dev options and turn off the intro instructions. Shouldn't be needed.
Please everyone interested in daydream on LOS vote for this bug https://jira.lineageos.org/projects/BUGBASH/issues/BUGBASH-284?filter=allopenissues
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.
Hello guys. I just intalled official pie update that came yesterday on my phone via OTA.
However I forgot to uninstall goodlock 2018 (im from EU and therefore its not officialy available) I had navstar (I added different buttons) and task changer turned on.
After installing Pie, these features are no longer available on my phone (in good lock app they appear blocked and I cant update them).
BUT since they were not turned off, now im stuck with them and I cant turn it off (the buttons from navstar are still there even after uninstal). I tried uninstalling but they still apear.
The result is that its now crashing with Pie ONE UI and experience home keeps crashing. I have temporarily added different launcher and its works, but if I go back to home experience, it starts lagging and crashing again.
What can I do? Can I officialy revert back to oreo, remove goodlock and then install pie again? Or is there other way to do it?
I have once heard that you must never uninstall goodlock features without turning them off first because they cause problems afterwards and it seems this is the case here.
Would appreciate any help here, the phone with default home experience launcher is useless because of crashing.
you could try a factory reset....
PorscheCarrera said:
Hello guys. I just intalled official pie update that came yesterday on my phone via OTA.
However I forgot to uninstall goodlock 2018 (im from EU and therefore its not officialy available) I had navstar (I added different buttons) and task changer turned on.
After installing Pie, these features are no longer available on my phone (in good lock app they appear blocked and I cant update them).
BUT since they were not turned off, now im stuck with them and I cant turn it off (the buttons from navstar are still there even after uninstal). I tried uninstalling but they still apear.
The result is that its now crashing with Pie ONE UI and experience home keeps crashing. I have temporarily added different launcher and its works, but if I go back to home experience, it starts lagging and crashing again.
What can I do? Can I officialy revert back to oreo, remove goodlock and then install pie again? Or is there other way to do it?
I have once heard that you must never uninstall goodlock features without turning them off first because they cause problems afterwards and it seems this is the case here.
Would appreciate any help here, the phone with default home experience launcher is useless because of crashing.
Click to expand...
Click to collapse
I had good lock too with nearly all mods being used and switched on, after update, other than my phone looking like crap, it's not caused any actual issues like you describe.
I don't use navstar though and I use ruthless launcher so maybe that's why.
Have you uninstalled each individual module? Rather than just the good lock app itself?
If so your only options are either wait for good lock to be updated, or a factory reset, I say a reset is always best after a major version update anyway, although I can't be arsed doing that myself yet
Well it seems that deleting Home Experience data fixed the issue. Thanks for the replies though.
On side note I realy dislike new recent apps. Task changer in good lock was miles miles better. If you watched something in youtube and went into recent apps it kept playing in background, here it leaves any app and scrolling isnt nearly as smooth. Hopefuly they add it back for pie because right now I sort of regret upgrading.
After my update on AT&T yesterday, I have persistent handles on left and right as well as the edge handle that is usable in the upper left. Anyone know how to get rid of these? I tried turning off edge panels and they still show. Also I have tried the transparency trick, no good there either. Is this a known "upgrade" or a known issue? Thanks in advance.
Disable One Hand Operation + for those handles
Do any of you know how to get multi window to work? It seems to be gone.
beta546 said:
I had good lock too with nearly all mods being used and switched on, after update, other than my phone looking like crap, it's not caused any actual issues like you describe.
I don't use navstar though and I use ruthless launcher so maybe that's why.
Have you uninstalled each individual module? Rather than just the good lock app itself?
If so your only options are either wait for good lock to be updated, or a factory reset, I say a reset is always best after a major version update anyway, although I can't be arsed doing that myself yet
Click to expand...
Click to collapse
What is ruthless launcher?
cushcalc said:
What is ruthless launcher?
Click to expand...
Click to collapse
Well...it's a launcher, called ruthless haha. Just Google it and you'll find the XDA page, it's a branch off from the original rootless launcher, basically it's a pixel launcher but with lots of extra settings.
I am on the us carrier AT&T. I am using the snapdragon model. I took the OTA yesterday and I left goodlock 2018 installed and all the addons enabled.
I am not getting any of the issues you described. The good lock app just shows all the mods as "disconnected". One hand operation and edge lighting are still working.
raul6 said:
Disable One Hand Operation + for those handles
Click to expand...
Click to collapse
Thanks mate, been scratching my head trying to get rid of those 2 bars. They were about the same height as the keyboard and pressing near a bar made it freeze for a few seconds. Cheers
Im on S8 exynos pie Beta 3. Task changer is not working. Even with badlock. Is this working for anyone of you?