Related
Hi...
I´m a moto g4 plus user and really liked this device but that mine present any hardware problems and i had to use another device, in this case a Note 4 Verizon, stock rom lollipop works fine, and stock marshmallow but i really liked a clean system whithout propietary apps (Like Samsung) turned to Nougat, used a Emotion but have some errors and turned to Resurrection, in nougat have some problems with camera but works...
I tried a many camera apps but no liked, i really loved a moto camera, snap camera in this rom works very fine, but dont have a burst mode, tested a htc camera works fine but failed after, i tried many ports that others devices but not worked fine.
Test a Moto Camera official and give a "unsupported device", but remember see this apk, not flashable no risk if not works only uninstall, i download a installed and surprised me, it works very fine...
I use the same camera apk in my moto g4 plus and loved, in this case in Note 4 not works a slowmotion but i can live with these...
Maybe any developer fix the error to work 100%
Works in marshmallow
Post
https://forum.xda-developers.com/moto-g4-plus/themes/moto-camera-6-0-78-1-apk-t3639222
Download APK
https://drive.google.com/file/d/0BzN_CG03Ba9WR0lIVHNsQ1BQd0k/view
Thanks to @Aby lad and @diegomartinezlovey
Flashed an Oreo rom the other day and I don't know if it's just me but a lot of my paid apps keep FC, my favourite launcher, Next Pro doesn't work, others like camera FV, actually non of my camera apps work, even the stock camera, can't even open up a browser. Re-flashed the ROM again today but still the same, off back to nougat.
Compatibility issues and or mux'ed up install. I wonder if anyone has started an Oreo compatibility thread . . .
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
Update: Issue has been solved; however, don't ask me how. I simply don't know; all I know is all is working fine now!
Thread is going to be closed.
I'm pinging my post that I've made in a specific ROM thread here three days ago, because I haven't received any response (besides 5 thanks ).
*******************************
Two weeks ago, I purchased a used SM-G955F to become my daily used device. However, it came with stock Pie on a BL v5 i.e. I immediately knew that it will be impossible to downgrade to Oreo or even better to Nougat. For personal reasons, I rather use Nougat and all of our devices are currently running Resurrection Remix Nougat. But anyhow, no reason to lock back and I tried to make the best out of the current situation. And initially, it looked very promising. I discovered this great ROM, for which I'm very grateful to Stricted. So the current configuration of my SM-G955F is as follows:
lineage-16.0-20190922-UNOFFICIAL-dream2lte, unchanged kernel, rooted with Magisk v20.0
Magisk module as shown in screenshots but including EdXposed
as all of our devices, GApps free running with microG (powered by NanoDroid v22.4), signature spoofing patched by SmaliPatcher
Two EdXposed modules as shown in screenshot
Firewall (AFWall+), Adaway and XPrivacyLua not (yet) enabled
ROM is working really well, no issues except the below described ones but definitely no issues with root, Magisk, signature spoofing or EdXposed.
I'm not using and never will use anything of Google (only exception is the Google Play Store modified by Setialpha), Facebook etc. i.e. no Whatsapp, Google contacts or calendar etc. As messenger I use Conversations, a Jabber/XMPP client; in order to synchronise my contacts and calendar DAVx⁵.
And here are the issues that don't allow me to become the SM-G955F my daily used device:
Conversations doesn't connect to my existing Jabber account with the notification "server not found" (same applies when I try to create a new jabber account) but I can assure the server is working as I see on my other devices.
About the same applies to DAVx⁵, which is unable to connect to my email provider (posteo.de) for the synchronisation of contacts and calendar.
As far as I know the first one uses ports 8443 and 8843, the latter ports 5222 and 5269.
And I believe, very important: After I initially had the issues on LOS, I reverted back to stock Pie (i.e. bloated with all Google things and services as well as a lot of Samsung crap) but both issues are also existing on stock. First, I can clearly state they are not LOS issues or ones of this wonderful ROM.
However, as initially stated I've always been on (maximum) Nougat and don't know what Google additionally implemented or changed on the way via Oreo to Pie.
Can it be that the above mentioned ports are blocked?
Any means (e.g. via ADB) to open these ports?
Or any other idea that would allow me to become the SM-G955F with this LOS 16.0 my daily driver.
I'm happy and ready to provide any further information and logs...
try to completely disable af firewall by removing root permission and unchecking xposed and freezing it and then reboot and then try again ...sonetimes you block stuff in af that actually includes other dependencies under a general description like "system" ** only an example
also sometimes if you restore af firewall rules it might seem like you are allowing connections but af is blocking in background ...
KevMetal said:
try to completely disable af firewall by removing root permission and unchecking xposed and freezing it and then reboot and then try again ...sonetimes you block stuff in af that actually includes other dependencies under a general description like "system" ** only an example
also sometimes if you restore af firewall rules it might seem like you are allowing connections but af is blocking in background ...
Click to expand...
Click to collapse
Thanks for the advice but see what I also stated above:
...
And I believe, very important: After I initially had the issues on LOS, I reverted back to stock Pie (i.e. bloated with all Google things and services as well as a lot of Samsung crap) but both issues are also existing on stock. First, I can clearly state they are not LOS issues or ones of this wonderful ROM.
...
Click to expand...
Click to collapse
During the attempt with stock Pie no firewall or Xposed was installed. The issue must be somewhere else. By the way, on the Samsung SM-G935F that I just set up a few days ago with lineage-15.1-20191016-UNOFFICIAL-microG-signed-hero2lte, everything is working as advertised. That device is currently my daily playground.
Westfalenpfeil said:
Thanks for the advice but see what I also stated above:
During the attempt with stock Pie no firewall or Xposed was installed. The issue must be somewhere else. By the way, on the Samsung SM-G935F that I just set up a few days ago with lineage-15.1-20191016-UNOFFICIAL-microG-signed-hero2lte, everything is working as advertised. That device is currently my daily playground.
Click to expand...
Click to collapse
ok i understand . im also using a Samsung S7 as my daily driver. its still a good device despite its age .
is it possible that you have flashed a custom kernel along the way and when you returned to stock , you didnt return to stock kernel and that it is messing with the ip tables ..
have you tried looking into flashing kernel ?
KevMetal said:
ok i understand . im also using a Samsung S7 as my daily driver. its still a good device despite its age .
is it possible that you have flashed a custom kernel along the way and when you returned to stock , you didnt return to stock kernel and that it is messing with the ip tables ..
have you tried looking into flashing kernel ?
Click to expand...
Click to collapse
No custom kernel has been flashed yet. And currently no time available to dig deeper and/or to search for suitable ROM's and kernel. The S8+ sits on its case. I'll update this thread if situation changes.
Anyhow, I appreciate the advices and ideas.
Thread closed as per request of OP
Moving away from main thread to avoid spam
Original Question:
Hi,
first of all, thanks a lot for your effort bringing lineage to the pixel 4a.
I've got a problem with the main (front 12.2 MP) camera (please see attached logcat).
When opening the default camera app (as well as with my test with google camera) the screen stays black and I can't take pictures. I'm on build number lineage_sunfish-userdebug 11 RQ2A.210505.003 b609c3a431, but had this problem with the previous build as well (I was able to take pictures a few builds back, though).
Does anyone else have issues with the camera not working or is it just me?
Thanks a lot and let me know, if there's any further info I can provide that would be helpful for troubleshooting.
Thanks and regards,
C
second log from main thread
Original text:
Hey again
I clean installed the 20210527 build (and corresponding recovery) today and first thing I did was trying the camera... The org.lineage.snap is slow to non-responsive, the screen stays black and ultimately the camera app crashes...
The attached log shows multiple errors (as far as a noob like me can tell ).
If I'm the only person affected by this, is there anyone who could help me troubleshoot the issue... different hardware in Europe... or hardware failure... false stock firmware (though 100% sure it was on 11).
Thanks again and regards,
C
(If there's a better place for bug reports, kindly let me know )
reply to post
Hey @mangokm40
thanks for your feedback. I neither have magisk nor any custom kernel installed.
I basically came from stock android 11 and followed the installation instructions .
As per this lineage wiki I installed mindthegapps according to the instructions.
Do you or anybody have any other idea? As I seem to be the only one affected, I guess a bug report wouldn't be in order, would it
Thanks again, appreciate your support
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
sk8223 said:
Chris, stop using the stock/default app and use a Gcam port: https://www.celsoazevedo.com/files/android/google-camera/dev-cstark27/
Like PXMod (cstark's PXv4.5: PXv4.5_GoogleCamera_7.2.014.apk (cstark27, 2020-09-04, pixel)
I think you'll find the same and more features than the stock app, and it's a lot more stable. No issues taking front camera pics (you can also enable HDR+ for the front camera).
Click to expand...
Click to collapse
thanks for the input, but i fear, that won't help in my case... I already tried the gcam mod of this post, which didn't work either
there might be darker forces at work with my pixel 4a...
nonetheless, I'll try your version asap and come back with the result.
thanks for your time and effort
I have the same issue. The rear cam stopped working. Upgrading to the latest 18.1 build did not help. I guess an update for "carrier services and device personalization apps" from play is causing this, as this are the only changes i noticed on my p4a.
hey guys,
sorry for the delay, but finally closing the loop on this one.
thanks to @razorloves , who looked a the logs and confirmed my suspicion, that an actual hardware issue might be the issue, I rolled back to stock and was able to confirm, that the camera issue had nothing to do with LOS 18.1 .
the same problem occured with stock, so I returned and exchanged the phone.
new phone with official LOS 18.1 has been working smoothly for two weeks now, including both cameras
so again, thanks @razorloves for your support and of course thanks @PeterCxy for a great rom.
cheers,
C