Related
Hello,
This article describes a good solution for OnePlus 3 : https://www.xda-developers.com/force-daydream-vr-compatibility/
I'm looking for a solution for OnePlus 6
Thanks for your help !
David
m4b-fr said:
Hello,
This article describes a good solution for OnePlus 3 : https://www.xda-developers.com/force-daydream-vr-compatibility/
I'm looking for a solution for OnePlus 6
Thanks for your help !
David
Click to expand...
Click to collapse
Hello! I don't get my OP6 till Monday or Tuesday, but I used the method in the link you provided for my Essential PH-1 and it worked fine. I've never had a OnePlus device before, so I'm not familiar with OOS. I'm hoping this method works as I like watching Plex VR with friends who don't live in the state I do.
surface13 said:
Hello! I don't get my OP6 till Monday or Tuesday, but I used the method in the link you provided for my Essential PH-1 and it worked fine. I've never had a OnePlus device before, so I'm not familiar with OOS. I'm hoping this method works as I like watching Plex VR with friends who don't live in the state I do.
Click to expand...
Click to collapse
Hello,
Thanks for your message.
I use this method with my OnePlus 3 and it works well with many applications - you can use the plug-in vr with Magisk too.
Unfortunately, i have some issues with my Op6 ...
Hope we find a solution
m4b-fr said:
Hello,
Thanks for your message.
I use this method with my OnePlus 3 and it works well with many applications - you can use the plug-in vr with Magisk too.
Unfortunately, i have some issues with my Op6 ...
Hope we find a solution
Click to expand...
Click to collapse
I tried this last night....and it worked for the most part. Until I launched Daydream, the left picture was fine, the right picture looked like a kaleidoscope. So I reverted the daydream version back 1 version and there was a large black line in the middle of the right picture. Reverted to an older one again, and one more time both with the same black line (was a pretty thick line)
So I renamed the device to OnePlus 6 from sailfish in build.prop, and removed the 2 <feature name= /> lines from the handheld_core_hardware.xml files.
I hope something works for us soon!
FYI I got this working yesterday. I had to install an old version of Daydream though - 1.10 worked. I was then able to upgrade to latest (1.15.) I didn't exactly test it thoroughly so I'm not sure if it has to be the right phase of the moon while hopping on one foot or anything, but I got "incompatible phone" errors until I used 1.10 then everything was cool. I was able to play through the tutorial and poke around a little at the menus.
EDIT: I just tried it again and right "lens" was messed up. Uninstalled and went back to 1.10 and seems like everything is working again. 1.11 isn't on apkmirror and 1.12 seems to have a bit of an updated UI, so maybe there's something to using 1.10? I'll play around some more tonight and report back.
EDIT 2: Oh haaay 1.16 was just uploaded to apkmirror last night. Will try that too.
Oh, and FWIW I'm on stock rooted Oxygen 5.1.8 with the 8/256 model.
Anyone else having any luck?
BikerFry said:
FYI I got this working yesterday. I had to install an old version of Daydream though - 1.10 worked. I was then able to upgrade to latest (1.15.) I didn't exactly test it thoroughly so I'm not sure if it has to be the right phase of the moon while hopping on one foot or anything, but I got "incompatible phone" errors until I used 1.10 then everything was cool. I was able to play through the tutorial and poke around a little at the menus.
EDIT: I just tried it again and right "lens" was messed up. Uninstalled and went back to 1.10 and seems like everything is working again. 1.11 isn't on apkmirror and 1.12 seems to have a bit of an updated UI, so maybe there's something to using 1.10? I'll play around some more tonight and report back.
EDIT 2: Oh haaay 1.16 was just uploaded to apkmirror last night. Will try that too.
Oh, and FWIW I'm on stock rooted Oxygen 5.1.8 with the 8/256 model.
Anyone else having any luck?
Click to expand...
Click to collapse
Have you gotten this to work with 1.16? I tested 1.10 and still got the "Incompatible device" error when trying to configure Daydream. I also attempted 1.08 just to see if older versions worked, then went for 1.16, getting the same results.
I'm on an OP6, OOS 5.1.8, stock rom, rooted.
I got Daydream working with current Daydream build from the app store. I installed the Magisk Module called "Daydream Enabler"
I'm on OP6 128/8 stock OOS 5.1.7 with Magisk 16.0 and MM 5.8.1
surface13 said:
I got Daydream working with current Daydream build from the app store. I installed the Magisk Module called "Daydream Enabler"
I'm on OP6 128/8 stock OOS 5.1.7 with Magisk 16.0 and MM 5.8.1
Click to expand...
Click to collapse
That worked for me, thanks! The only catch is that the module seems to break video recording in the stock camera app, causing the app the close as soon as I switch the video mode. Disabling the module and rebooting fixes the issue. Strange that they're related...
willpowerltd said:
That worked for me, thanks! The only catch is that the module seems to break video recording in the stock camera app, causing the app the close as soon as I switch the video mode. Disabling the module and rebooting fixes the issue. Strange that they're related...
Click to expand...
Click to collapse
That happened to me too. But after disabling it, restarting, enable it again, restart again, everything worked
Thanks !
but .... I still have the same problem with the camera app when module is enable...
m4b-fr said:
Thanks !
but .... I still have the same problem with the camera app when module is enable...
Click to expand...
Click to collapse
Hey, just FYI I have a the same issue. Possible that the camera app recognises a different device and breaks the functionality.
zplot said:
Have you gotten this to work with 1.16? I tested 1.10 and still got the "Incompatible device" error when trying to configure Daydream. I also attempted 1.08 just to see if older versions worked, then went for 1.16, getting the same results.
I'm on an OP6, OOS 5.1.8, stock rom, rooted.
Click to expand...
Click to collapse
Naw no luck. The magisk module is working fine though. Same results that it breaks the video recorder.
But I ran into something unexpected - That module appears to make visual voicemail on project fi work. Sort of. They show up, but won't play. Before oneplus + projectfi = no visual voicemail. I'll play with it some more when I get back stateside (I'm in Mexico at the moment.) Would be neat if it enabled network switching onto sprint! A girl can dream...
Edit: Enabling the module (which "pixelizes" your phone) made the project fi app give me the "welcome to mexico" thing which I didn't get when I entered a new country on a non-officially-supported phone, and it prompted me to download Android 9, which I declined since I'm sure it would have been the pixel's rom and bricked my oneplus.
Neat to see it enables some project fi stuff...
Any further progress on this?
no progress and i noticed that I can't access to all app in daydream store app
https://www.droid-life.com/2019/09/17/report-samsung-launching-android-10-beta-next-month/
do we need to subscribe beta program?
Probably... The details haven't been announced yet.
Any new about it
Looks like the beta is currently available in Korea, and will probably be available through the Samsung Members app later this week.
But I am from Argentine. And here don't come the beta. Any advice to get it?
Just curious, do any of you think if I change my location with a VPN I will be able to get the Beta that was already released in Korea?
I try and when I change my vpn and open samsung members the APK fails
https://forum.xda-developers.com/s10-plus/how-to/galaxy-s10-sm-g975f-official-oneui2-10-t3980879
Check this
It's currently available in the US through Samsung Members for Sprint and T-Mobile only.
One UI 2 beta adds spacing at the bottom of every app which serves no purpose. There are lot of bugs here and there but I have not noticed any app crashes as such.
I am from spain, and I have just installed the beta too.
It has some lag, screen mode seems that always is in vivid instead natural, and still sometimes the screen wake up like if you tap the power button. There are a lot to polish.
Regards
I joined the UI 2 beta but found it much more buggy than previous Samsung betas (like 8 -> 9) and quite honestly there was no discernable difference for my use case scenario. Samsung does a very good job polishing its take on Android so that the next version doesn't seem that much of an upgrade. It reminds me of iOS and macOS upgrades where you need to read up about the differences otherwise you might not realise what was new. Given that is the case I decided to withdraw from the beta program and revert to Android 9 using Odin. For me there were no advantages and many disadvantages in running UI 2 at this stage. I got display glitches like mentioned above, neither Google Pay nor Samsung Pay worked, the navigation bar kept reverting to the old on-screen icon system and UI 2 did not play well with my launcher of choice, Nova. Yes, there are 'solutions' like not using Nova and maybe doing a hard reset after upgrading, but for me it just isn't worth the hassle for no obvious return.
Beta ROM?
Anyway to force subscribe to the beta program, or just get the ROM to flash manually?
codevalley said:
Anyway to force subscribe to the beta program, or just get the ROM to flash manually?
Click to expand...
Click to collapse
Just flash the ROM through Odin and you're done. The only downside is that each time a new beta or the final release comes out, you have to flash it with the help of Odin because the OTA updates are tied to the Samsung Members app.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
BTW, what about the image quality of the S10e in Android 10 Beta 6? Did they improve it compared to Android 9 Pie?
Short version: What's the easiest/best way to make sure my (unlocked/Magisk-rooted) 7Pro does NOT upgrade to Android 10?
Long version:
New 1+ owner here after finally giving up on Google's ability to make a phone I like (I have had only Google phones since Nexus One, and just now retiring my Nexus 6) -
Before getting the 7Pro, I got/tried/returned the horrible Pixel 4XL - that I might actually have kept if Google had done a better job on the software - Android 10 and the new Assistant features. (*Shocking to me that out of the box, this brand new factory fresh phone is loaded with GAPPS that lack the features that Google advertises for the phone! Requires many updates, and still doesn't work properly.)
Since I don't want to effectively become a beta-tester for this new stuff, I really want to prevent the 1+ from updating to Android 10 and not quite sure how to make sure:
The phone came with a 9.x version, and did 1 system upgrade to 9.5.13, and it's now telling me another system upgrade is available. But, best I can tell, there is no way to know what build it is going to update to until after it's done?
Android 10 stable branch has been mostly fine. The only bug I've experienced was due to custom kernels and modules. I'd say avoid 10.3 until the wifi brain cpu issue is fixed.
relaxable said:
Short version: What's the easiest/best way to make sure my (unlocked/Magisk-rooted) 7Pro does NOT upgrade to Android 10?
Click to expand...
Click to collapse
xxxNoLimits can systemlessly debloat OPBackup if you select that as one of the available options. That will prevent auto updates.
Best as I understand, 9.5.3 was the last Pie Rom. Any further updates will be Q.
I am currently on a third party ROM. Went there since Stable OOS 10.X broke usb C audio. I enjoy OOS as its easier to maintain and manage my families phones ( we all have OP phones, I'm not biased at all lmao) but was wondering if anyone that's already gone to the open beta for android 11 tested OR could test the usb C audio functionality. Curious to see if they fixed it or if it's still broken before i blow my phone away and go to the android 11 open beta just to find it not working still.
slyyke said:
I am currently on a third party ROM. Went there since Stable OOS 10.X broke usb C audio. I enjoy OOS as its easier to maintain and manage my families phones ( we all have OP phones, I'm not biased at all lmao) but was wondering if anyone that's already gone to the open beta for android 11 tested OR could test the usb C audio functionality. Curious to see if they fixed it or if it's still broken before i blow my phone away and go to the android 11 open beta just to find it not working still.
Click to expand...
Click to collapse
I've been sticking with the betas and never had an issue with usb c on android 10. Happy to report back on android 11 as soon as we have twrp (working on 11).
Hello,
Not sure if it's the right place, but I'm getting depressed with my Xiaomi 12 behaviour. Since last update, MIUI global 13.2.4, the phone keeps killing apps, even if I set those with :
- not battery restriction
- auto startup
I tried a factory reset, I unlocked it, rooted it. It keeps killing apps. It's annoying, because I use Vivid and removed the navigation buttons. I let you imagine how I can be stuck sometimes when Vivid is killed. Yet, Vivid is locked... So MIUI regurlaty kills it, and sometimes, it even loses the accessibility autorisation.
How can I know what's killing it ? Obviousily, I'm not in Eco mode, and this behaviour also occurs in performance mode. Everything worked very fine until last update.
Sirguda said:
Hello,
Not sure if it's the right place, but I'm getting depressed with my Xiaomi 12 behaviour. Since last update, MIUI global 13.2.4, the phone keeps killing apps, even if I set those with :
- not battery restriction
- auto startup
I tried a factory reset, I unlocked it, rooted it. It keeps killing apps. It's annoying, because I use Vivid and removed the navigation buttons. I let you imagine how I can be stuck sometimes when Vivid is killed. Yet, Vivid is locked... So MIUI regurlaty kills it, and sometimes, it even loses the accessibility autorisation.
How can I know what's killing it ? Obviousily, I'm not in Eco mode, and this behaviour also occurs in performance mode. Everything worked very fine until last update.
Click to expand...
Click to collapse
Maybe a bug in the rom which is a stable beta.
The ROM is official, it's been deployed in France last week.
Sirguda said:
The ROM is official, it's been deployed in France last week.
Click to expand...
Click to collapse
And so, Xiaomi has been deploying beta roms on stable channels for a long time.
Xiaomi 12 EEAStable BetaRecoveryV13.2.4.0.TLCEUXM13.04.8 GB2022-12-01
If it worked before this update, you have the answer.
NOSS8 said:
And so, Xiaomi has been deploying beta roms on stable channels for a long time.
Xiaomi 12 EEAStable BetaRecoveryV13.2.4.0.TLCEUXM13.04.8 GB2022-12-01
If it worked before this update, you have the answer.
Click to expand...
Click to collapse
OTA update for an entire country are with beta ? If so, this is a joke. How can I report this to Xiaomi ?
Sirguda said:
OTA update for an entire country are with beta ? If so, this is a joke. How can I report this to Xiaomi ?
Click to expand...
Click to collapse
You are not the only one to have had problems following updates, the solution if it worked before, is to flash the previous rom or to use a Xiaomi EU rom.
Sometimes Xiaomi renames a Stable Beta to stable without fixing anything.
NOSS8 said:
You are not the only one to have had problems following updates, the solution if it worked before, is to flash the previous rom or to use a Xiaomi EU rom.
Sometimes Xiaomi renames a Stable Beta to stable without fixing anything.
Click to expand...
Click to collapse
Previous ROM is in Android 12. Downgrading won't be a problem ? Keeps root ? EU Roms seem far behind.
Sirguda said:
Previous ROM is in Android 12. Downgrading won't be a problem ? Keeps root ?
Click to expand...
Click to collapse
Downgrading requires a clean flash and the root is lost along with your data.
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
And disable the update.
EDIT:
I use a Xiaomi EU rom on my 12 pro and I have several apps that must remain in the background, works very well.
With a Xiaomi EU rom you will have the certified play store without root and lots of extra options.
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
bunklebeard said:
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
Click to expand...
Click to collapse
Go to this site if you need anything, the updates with beta roms on the stable channel do not date from today, many threads on this subject have been created without change since today the problem persists.
Reporting bugs via Services & Feedback hasn't changed anything either.
Note that since the redesign of their site, important threads have disappeared and even some devices.
As a reminder, it is the moderators of this site who report information, well that's just theory because in practice, nothing happens.
If you want answers from Xiaomi, tell them you want to buy a new phone because that's what they're interested in, selling.
I tell you this because at a certain time, I was active on this site, but some of my posts were deleted because I explained how to solve or work around the problem.
Sometimes by checking the hash of a beta rom and the following stable, it was the same.
The solution is to unlock the bootloader and downgrade or install a Xiaomi EU rom.
bunklebeard said:
This is happening to me also and many other people. Fun times waking up to find that your alarm clock hasn't gone off because it was killed in the background.
There doesn't seem to be a workaround yet. There's several posts on the mi.com forums regarding it:
Xiaomi Community
new.c.mi.com
People there have discussed making a bug report via the feedback app (Settings->"Services & Feedback") might garner some support for Xiaomi to fix the issue... one can only hope.
All I can say is if you're thing of updating to V13.2.4.0.TLCEUXM OTA then DONT! Teach me to apply an update without checking on it first.
Click to expand...
Click to collapse
I'm kind of relieved that's I'm not the only one with this issue. For sure I dont take a xiaomi anymore. I had doubt about MIUI, and gesture unavailable with 3rd party launcher + this killing app bug, makes me regret not have taken a Samsung S22.
" I had doubt about MIUI, and gesture una aimable with 3rd party launcher"
Xiaomi blocks this function with third-party apps (not new).
NOSS8 said:
" I had doubt about MIUI, and gesture una aimable with 3rd party launcher"
Xiaomi blocks this function with third-party apps (not new).
Click to expand...
Click to collapse
Not new, but it's a detail you have trouble knowing before buying. With Vivid Gesture, I was plainly satisfied, but this new bug is really frustrating.
Regarding "Xiaomi EU rom", how well tested is it? Do they have an issue tracker and a list of known bugs?
I've rooted and flashed community ROMs in the past only to find out they are poorly tested / have horrible QA and although superficially they work fine other aspects didn't like Bluetooth, Android Auto or certain camera modes etc.
It has been a while though since I last attempted one, maybe things have moved on since then?
Xiaomi has removed so much of the Google framework that even push notifications isn't working. Take note that the Global ROM is based on the CN variant which is known for aggressive background killing of apps.
In Xiaomi's defense, they are "freeing up" up to 800mb of your internal storage by removing most of Google's API but in the expense of all the issues encountered by Global ROM users.
So if anyone is interested, I'm trying to see if disabling com.miui.powerkeeper works round this issue of background apps being killed in V13.2.4.0.TLCEUXM .
I followed this tutorial:
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com
Will report back if I notice any improvement.
Maybe someone more knowledgable might be able to tell me if there are any downside to disabling this package?
I am suffering the exact same problem with my device since the 13.2.4 update, what i nightmare to use the device since then ! As the other users already reported, it s even killing the alarm app which prevents it to ring ! But it also impacts all app notifications, like whatsapp, outlook, etc. After being killed I don't get the new notifications for those.
I can't believe that they are pushing such an update globally, they are gonna lose a lot of customers which such a poor strategy, as this is not just a "little" bug.
I am interested in the Xiaomi.EU rom, looks like they released one 2 days ago with version number 13.2.6, but I have to investigate if we can install that over our official version on an original EU device, and if it requires a full data wipe or not.
kalhimeo said:
I am suffering the exact same problem with my device since the 13.2.4 update, what i nightmare to use the device since then ! As the other users already reported, it s even killing the alarm app which prevents it to ring ! But it also impacts all app notifications, like whatsapp, outlook, etc. After being killed I don't get the new notifications for those.
I can't believe that they are pushing such an update globally, they are gonna lose a lot of customers which such a poor strategy, as this is not just a "little" bug.
I am interested in the Xiaomi.EU rom, looks like they released one 2 days ago with version number 13.2.6, but I have to investigate if we can install that over our official version on an original EU device, and if it requires a full data wipe or not.
Click to expand...
Click to collapse
Welcome to XIAOMI.
You can check below the version of the rom proposed for the update, before performing it.
https://xiaomifirmwareupdater.com/archive/miui/cupid/
EDIT:
You can either update the rom with the update.bat file included in the Fastboot.zip folder but since it is an A13 version, it is preferable to format the data with the first install.bat file .
Obviously the bootloader must be unlocked.
Also remove the security from the lock screen and restart the system.
Hello. I have exactly the same problem. I just bought the phone, after a week I got that update and it made me completely regret that I bought it. Is there any "clean" way to return to the version of MIUI I bought the phone with?
Would a reset return me to the old version? Since i got almost nothing important in the phone, it wouldnt be a big deal.
zazajin said:
Hello. I have exactly the same problem. I just bought the phone, after a week I got that update and it made me completely regret that I bought it. Is there any "clean" way to return to the version of MIUI I bought the phone with?
Would a reset return me to the old version? Since i got almost nothing important in the phone, it wouldnt be a big deal.
Click to expand...
Click to collapse
Bootloader must be Unlocked.
https://forum.xda-developers.com/t/miui-keeps-killing-apps.4529641/post-87852189