Related
Hello guys,
As I said in the title, face unlock doesn't work for me in android 5.0 LRX21O. It didn't work in preview versions also.
I have read several reviews on this feature, watched several videos, but i have never managed not once to unlock the device this way. I think i have registered almost 20 conditions for face matching, in different light condition, but the result is the same, it doesn't unlock the phone this way.
How is your experience with this feature?
Workinbg fine her ei don't see any proble mat all
probably your face is not compatible with this feature.
I had no problems here
ricardollreis said:
probably your face is not compatible with this feature.
I had no problems here
Click to expand...
Click to collapse
Lol.
Probably, that's the only face I have unfortunately.. But seriously, it worked in KitKat.
Well, gonna ask a friend to set up this with his face and see how this will turn out.
it doesn't work for me either! I've tried to improve the matching also. It worked better when it first came out on the Galaxy Nexus.
I flashed the image via Mac and each partiton one at a time. I'm wondering if you did a full wipe including the user data? I didn't so I'm going to try that next maybe, or maybe wipe a particular folder in the system data to try again. I haven't bothered to root the phone yet I was going to do that at some point in the next few days.
It works for me if the room has good light conditions
neinfricatu said:
Hello guys,
As I said in the title, face unlock doesn't work for me in android 5.0 LRX21O. It didn't work in preview versions also.
I have read several reviews on this feature, watched several videos, but i have never managed not once to unlock the device this way. I think i have registered almost 20 conditions for face matching, in different light condition, but the result is the same, it doesn't unlock the phone this way.
How is your experience with this feature?
Click to expand...
Click to collapse
you might be expecting it to open to your homescreen like it used to. it doesn't do that. it simply (and very subtley) just unlocks the lock icon at the bottom which then allows you to swipe up without having to enter your pin or pattern.
IG-88.thx said:
you might be expecting it to open to your homescreen like it used to. it doesn't do that. it simply (and very subtley) just unlocks the lock icon at the bottom which then allows you to swipe up without having to enter your pin or pattern.
Click to expand...
Click to collapse
nop, i know how it works.
i have discovered what the problem was. i was locking the screen with an app and not by power button, so for a reason i do not know, the face unlock doesn't work if you lock the device this way.
First I run on stock sony lollipop firmware
1."Camera is temporarily unavailable due to high temperature. Please wait for your device to cool down before you can use the camera".
Well this would be reasonable if it only appear for 10-15 minutes of camera use
But it appear in 1-2 minutes in normal resolution
2.In manual camera mode there's pink tint on the camera
No pink tint in auto mode
3.Weird speaker cracking sound on top speaker
Oh also I live in Thailand and this is the model that have quick charge 2.0
And most temperature would probably be around 35 Celsius
If those problem can be fixed by installing new custom roms
I would be glad to do so but I would like to know what is the pre requirement you should do before installing new roms since from what I search there is DRM stuff which I don't understand yet (coming from Samsung here)
Did you try a hard reset?
Or use Sony PC companion to repair..ie reinstall rom.
skyhot004 said:
First I run on stock sony lollipop firmware
1."Camera is temporarily unavailable due to high temperature. Please wait for your device to cool down before you can use the camera".
Well this would be reasonable if it only appear for 10-15 minutes of camera use
But it appear in 1-2 minutes in normal resolution
2.In manual camera mode there's pink tint on the camera
No pink tint in auto mode
3.Weird speaker cracking sound on top speaker
Oh also I live in Thailand and this is the model that have quick charge 2.0
And most temperature would probably be around 35 Celsius
If those problem can be fixed by installing new custom roms
I would be glad to do so but I would like to know what is the pre requirement you should do before installing new roms since from what I search there is DRM stuff which I don't understand yet (coming from Samsung here)
Click to expand...
Click to collapse
DRM Keys ( Data Management Rights ) -They make features like X-Reality and Post-image processing for the Camera to work, basically Sony's Signature , unlocking your bootloader removes them and that also means the features I mentioned won't work. Most users back them up in the case they want to relock their bootloader and return the DRM Keys
------
The only pre-requirements are:
- A Rooted Z3 with custom recovery, either CWM, Philz or TWRP although most come with 2 like XZDR Dual recovery
- Unlocked bootloader depending on the ROM you want to install, if you want non-sony Roms like CM, AOKP or Slimrom then you need to unlock it
I can't guarantee installing a custom Rom would fix all your problems as the speaker problem you're mentioning seems more like a hardware problem than a software problem.
Good luck!
I have all these problems too, i haven't found a way to fix it but you can find my topic for disabling that temperature alert but temperature will rise up to 70 Celsius while recording.
This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:
Updates and Notes
Reserved
Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.
@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here
Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:
@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:
Hey guys
So i had this problem a while back, it also attaches to video playback errors (YouTube app mainly) and the camera app
So I had this issue a while back, I was unlocked, rooted, Xposed - the lot and i was able to find a fix that got them all working correct again (think it was DRM patch but truly don't recall)
Anyway, I decided to go legit again, use Android Pay and mobile banking etc and I'm now unrooted, twrp is gone and used flashtool to lock my bootloader, but in doing so the error has eventually come back (all 3) but in the process of trying various fixes I have found one cause when I load this one game (it happens after a length of time that I've not been able to determine yet, but loading this game will trigger it 100% even moments after a fresh boot)
Im running stock 7.0
Kernel: 3.10.84-perf-g1016077 [email protected] #1
Build Number: 32.3.A.2.33
I remember when I was first rooting I had flashed some different kernel but was all so long ago i have all but forgotten what I did :/
Painkiller1985 said:
Hey guys
So i had this problem a while back, it also attaches to video playback errors (YouTube app mainly) and the camera app
So I had this issue a while back, I was unlocked, rooted, Xposed - the lot and i was able to find a fix that got them all working correct again (think it was DRM patch but truly don't recall)
Anyway, I decided to go legit again, use Android Pay and mobile banking etc and I'm now unrooted, twrp is gone and used flashtool to lock my bootloader, but in doing so the error has eventually come back (all 3) but in the process of trying various fixes I have found one cause when I load this one game (it happens after a length of time that I've not been able to determine yet, but loading this game will trigger it 100% even moments after a fresh boot)
Im running stock 7.0
Kernel: 3.10.84-perf-g1016077 [email protected] #1
Build Number: 32.3.A.2.33
I remember when I was first rooting I had flashed some different kernel but was all so long ago i have all but forgotten what I did :/
Click to expand...
Click to collapse
Fill out the details please, you're not even mentioning the game in your rant (or spilling out your thoughts)
Lol, my apologies, I didn't mean to rant, the game I mentioned was township
I will eventually get the YouTube black video, fingerprint hardware and camera in use glitches sooner or later even if I don't open the game, it's just a sure fire way to trigger it
I also tend to get the YouTube glitch as soon as the fingerprint glitch appears
Is there any other details you need?
What are the glitches that you mentioned? ''get the YouTube black video''?
There's another threat in this box suggesting that flashing a patched kernel fixed most of your problems. Be sure to check it out and be more specific on your ''glitches''.
https://forum.xda-developers.com/xperia-z5/help/fingerprint-scanner-video-recording-t3630726
Sorry, the main glitches I encounter (that all happen at the same time) is the fingerprint scanner stops functioning, the camera functionality stops (no pictures or video, app acts like it's being used by another process) and any video playback is just a black screen, but I still have audio playback and control over skipping through to various times
Will this be an issue flashing onto nougat? I didn't see mention of anything past mm
Painkiller1985 said:
Sorry, the main glitches I encounter (that all happen at the same time) is the fingerprint scanner stops functioning, the camera functionality stops (no pictures or video, app acts like it's being used by another process) and any video playback is just a black screen, but I still have audio playback and control over skipping through to various times
Click to expand...
Click to collapse
Try flashing a patched kernel.
I'd suggest a factory reset (if you haven't unlocked your bootloader) or a full swipe (including system) in twrp (if you have unlocked your bootloader) and reflash the newest build.
If the problems still persist, i think it's best to have your phone checked for hardware problems.
And no, it's not a Nougat problem.
Good luck with your phone.
So I bought the BLUE Qiku 360 N5s and found how to Root it from GizChina.it BUT for some reason whenever I flash the root developer rom (TO ROOT PHONE) that they provided, my phones camera gets messed up. Now heres the weird thing, I bought my girlfriend the same phone but in BLACK and followed there instructions and her camera works fine. Only my phone for some unknown reason doesn't work the the freaking developer rom. Its frustrating because I want to get rid of all the CHINESE bloatware with the custom rom they provided (which works) BUT I need TWRP to flash it and I need to ROOT my phone before I can install TWRP. Some please send me some guidance cause I'm stressed and desperate!!!! THANK YOU
Verified Rootable
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.
Zyraelindir said:
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.
Click to expand...
Click to collapse
Can you please tell me what you used to root it? Thats the only problem, after flashing the devrom the rear camera stops working and the front camera works but is grainy and all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well. Also I can't login to snapchat with this phone. I think its because the phone has a built in screen recorder so snapchat won't let me login. Can you help me with that as well? Thank you!!!
raymondchiu said:
all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well.
Click to expand...
Click to collapse
I unlocked the bootloader via fastboot after flashing Giz China's dev-rom. The only real roadblock to rooting it is having the developer software to bypass 360's proprietary bootloader restrictions. Once the dev-rom is flashed, you should be able to utilize all of the adb and fastboot resources as you would for a non-Chinese phone.
Now that you've described your camera problems a bit more, I have to say that it sounds like a compatibility issue. I can't be certain without testing it, but the dev-rom has a lot less bells and whistles than the stock rom, so it's quite possible that the dev-rom is missing the necessary files for running all of the extra camera filters. The dev-rom is just a temporary fix to allow you to alter the bootloader, and isn't ideal for daily use.
I recommend you try reflashing it so that you can get root access, or if you already have root access then simply flash a custom rom to replace it, and then see if your camera is still having the same issues. Don't forget that you'll need to flash SuperSU or Magisk or whatever SU app you're familiar with after flashing the rom. Also, if you try reflashing the dev-rom with 360's software, I recommend doing so via a Windows7 installation. I initially tried it via multiple Windows 10 machines and it failed horribly in all of them. It worked in a matter of minutes in each Windows7 machine though. Go figure.
GizChina also has a custom rom for the 360 n5s, not sure if you're aware of it or not. You can find it here:
ttps://rom.gizchina.it/360-n5s/
You might need to utilize Google translate if you can't read Italian .
Let me know if that helps or if you have more questions.
Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.
raymondchiu said:
Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.
Click to expand...
Click to collapse
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.
Zyraelindir said:
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.
Click to expand...
Click to collapse
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.
raymondchiu said:
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.
Click to expand...
Click to collapse
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.
Okay what about the snapchat problem where it doesn't let you login because of the built in screen recording feature in the phone?
Zyraelindir said:
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.
Click to expand...
Click to collapse
I've also noticed that the black phones kernal version is 3.10.84 while the blue phones kernal version is 3.10.84-perf (also the snapchat problem on both blue and black n5s)