Related
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
CM11 ISSUES:
-Video recording lags in reduced luminosity.
-The phone heats too much when playing/watch videos for long time and so on.
-Volume during call is too low.
-Ocasionally freezes & crashes.
-Some graphical issues when the phone freezes.
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
STOCK ISSUES:
-Video blinks in low light(from what I've read it focuses wrong on the light source and starts blinking).
-The proximity sensor remains on after a missed call.
-Multi touch doesn't work as well as on CM11.
-Some weird freezes during call ( the screen remains off / freezes and you can't end the call / sometimes even answer )
-Camera doesn't have as much detail as in CM11 ( if you zoom in,the image doesn't clarify).
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
CM11 FIXES:
-Lag in video recording can be reduced by lowering the exposure.In medium to low light " - 1 " works pretty good and in very low to low light " - 2 " .However,when you use " - 2 " ,the recorded video will be very dark.Still haven't found a solution for this.
-About heating problem,you might want to try @Shivam Kuchhal 's kernel.He reported that his phone doesn't get heat up more than normal.
-About volume during call,it's been solved partially in newer releases by editing snd_soc_msm file.However,if the value is too high,the phne volume will also be too high and the speaker will produce distorsioned sound.However,I see they found a resonable value and both,the volume during call & speaker is about fine.
-For headset buttons not working,you must edit Generic.kl file.Here's a short tutorial to help you:
Go to: system/usr/keylayout/Generic.kl and change as below
key 226 HEADSETHOOK
key 256 BUTTON_1
change to
key 226 BUTTON_1
key 256 HEADSETHOOK
STOCK FIXES:
-For proximity sensor and weird freezes during a call use this tutorial .Haven't tested it personally,but people reported it works even on latest .17 fw.
-For Mac issue [ works for cm11 as well ]
1)Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
That's all for now,continue to post bugs&fixes and most important:
HELP EACHOTHER
Marius Cristian said:
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
Click to expand...
Click to collapse
Proximity fix not working!!!
More Kitkat Bugs List:-
1. Headset buttons
2. Camera experiencing crashes randomly, sometimes cause overexposure and being unstable at flash mode
3. Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone.
4. Call bugs(e.g. distortion etc.)
5. Lag when using the video camera
6. battery draining faster then on stock rom. (was improved on early nightly releases....now its back again)
7. GPS not working again (for some it does...others it doesnt....again...wasnt there on first nightlies)(Mostly Happens In CM11)
8. Camera quality is much,much worse then on stock rom
9 . Phone may left hanging and screen wont turn on for several seconds...
10. Some apps are unsupported on playstore...
CM11 bugs
CM11:
1. Switch to HDR mode and within 3 snaps camera app will FC.
2. Headset buttons.. I have to manually edit that Generic.kl after every nightly update.
3. As mentioned above, graphical glitch after updates.
Some of bugs that u mentioned @David pro has been fixed by users, but device maintainer didn't merged it for some reason in official builds. So, get started:
1. These buttons can be fixed, someone(I don't remember who, Sorry) has created a modified Generic.kl. You can find that file somewhere on this forum.
2. Camera quality is medium, but videos are very poor..
3. Still exist
4. @up
5. As I said, videos are bad
6. Caused by Google Play Services, 1st method is use xposed Framework and one of its add-ons, 2nd is just disable Services from Settings>Apps(i'm using second one, because I just don't like Xposed)
7.GPS is working fine, at least for me. No fix needed
8.Yep, on stock it is better.
9.It's caused by "Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone."
10.Well, some of them are only for one platform or type of devices,eg. Tegra 4 games.
No heating issues noticed so far(I use my kernel obviously) and yeah the camera and video quality isn't anything worth praising. Also the hwcomposer issue happens only one time after every boot, after that its all fine.
I normally use AOSPA.
Actually,I think the cm11 camera takes better photos than stock,but it can be buggy sometimes :silly:
About GPS,it's working fine for me too.
About video camera being laggy...I think it's because our phone lacks drivers update.It's hard to believe the video camera will ever be 100% fixed.
I'm sorry I'm kinda busy those days and I don't have time to administrate this thread.I'll edit the main post as soon as I can with solution you guys posted.But it's true,there are things which can't be fixed.Until I come back, HELP EACHOTHER
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
vishalaestro said:
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
Click to expand...
Click to collapse
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Marius Cristian said:
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Click to expand...
Click to collapse
another BUG with the stock ROM
1)walkman app flickers in the widget lockscreen
2)poor memory management need to restart the phone daily else the phone lags like a hell
3)camera app didn't respond ,it doesn't even the focus sometimes ,clearing the app data solves this problem temporarily and i think it was not present with the .12 update ,so if anybody could extract the camera app from the .12 update similar to the phone app freeze issue the problem might be solved.
3)walkman app or any other music player makes music to stutter when the same song is played more than one time provided if the songs are stored in memory card also i know that my sdcard doesn't have any problem because it worked fine with galaxy s3.my sd card is sandisk ultra class 10 32 gb
4)battery drain heavy when wifi is switched on compared to previous android 4.1.2
note:i have not rooted my phone or modded my firmware .all i run is the apps taken from the playstore.i have done a factory reset for more than 4 times.
CM11 / Stock (using custom kernel) bug:
Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
Solution:
Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
solution for Play Services battery drain in CM11
CM11 issues
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
Nfc icon not in statusbar is on all cyanogenmod/aosp based rom
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
@underd0g
Nice fix for WiFi-Mac interference problem. :good:
Marius Cristian said:
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
Click to expand...
Click to collapse
guys please try to solve the issues with stock ROM because they are the stable ones and the bugs are easily repairable if the bugs are reached to right hands.so pls first concentrate on stock ROM
I've been playing around with 4.4 video recording..what i think is the lags occurs when we record in low lights related with the kernel..i'm testing with snapcam as its has auto flash when recording in low lights..First result is same as stock..but in snapcam it has touch to focus when recording..after touch,the recording will get a bit darker when it refocus and walla..no lags..
What i found is, the camera will automatically reduced the exposure to -1 for avoiding the lags even it is on default setting..
When moving the camera in low lights,the recording will lags again after few second..that is with continuous focus..set to normal or auto..no lags..so our stock cam using continuous focus for recording..
Back to the kernel thing..from what i see from the recording is same like this when i'm playing with cnt rom to to get wifi and overclock working.
Ok,so I went back to stock.I'm amazed by the battery life,it lasted 2 days and I used the phone a lot ( especially for calls ).
However,after using the fix for freezes during call and so on,I still have experienced this morning an issue.While I was talking to someone,someone else called and the phone was beeping but the screen was frozen.I had to press the power button to lock the device then unlock it to get the screen to show who's calling and to give me the possibility to answer the call.What do you think I should do?For now I'll wipe phone app data,but I'm also waiting if someone knows a good,another solution to post.
Anyone know a way to remove the automatic shutdown?
My phone shuts down if it reaches 25%
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.1.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
bakmanhans said:
I just want to let you know I finally made the ROM jump from MaximusHD to CyanogenMod 12.1 and it went superb!
Before starting this I thought I would be busy the whole evening (or more than one) so I prepared for the worst. I still use this phone on a daily basis. I got another HTC oldy as a backup just in case. My HTC One S isn't recognized on my PCs anymore since jumping in the swimming pool with it last summer so I had an extra handicap not being able to upload from PC to device.
I updated TWRP to the latest. Cleared storage. Rebooted in MaximusHD again ignoring the setup wizard as much as possible. Once booted I opened the web browser and downloaded the CM12.1 05DEC Unofficial ROM and TK GApps mini directly to my device. (All links available in the specific thread here on XDA) Booted in recovery again and flashed CM12.1 and TK GApps. All my apps and settings were uploaded/installed when the device booted CM12.2.
After boot all I had to do is change my Mobile 3G APN setting.
After one hour of work I couldn't believe it went so quick! And easy! The experience of CM12.1 on this 3 year old phone is unbelievable. I thought I would experience more lag and slow responses but... none of that. I can't notice any difference in speed comparing with the MaximusHD ROM.
I hope this stimulates others to make the update.
Click to expand...
Click to collapse
I've been tempted by the idea of jumping the MaximusHD rom ship for a while too. Are you happy with the camera performance? One of the reasons I'm reluctant to go the non-Sense rom way is the lack of the full hardware access to the camera on those roms.
I just jumped the ship three days ago. I didn't use the camera besides taking 3 pictures for test purposes. I'm a long time Camera ZOOM FX user so the app installed itself again. I replaced the CM12 camera app in the drawer with it.
I need more user experience time with the camera to tell you it lacks in any way.
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
bakmanhans said:
What, besides performance (speed) issues, will affect the camera not being able to have full hardware access?
Click to expand...
Click to collapse
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
twotimer said:
A couple of things I remember were missing from non-Sense camera apps are the ability to shoot slow motion video (lower res but higher fps) and the HDR mode for photos.
Not that these two produced any usable results though .
Click to expand...
Click to collapse
I can't find slow motion video. I never saw it in the MaximusHD ROM either. ZOOM FX cam does have the HDR option, just like with MaximusHD. But seriously, it's nothing more than a gimmick. Do you ever use it?
twotimer said:
I believe the other parameters like photo/video resolution are adjustable with the stock CM camera and ZOOM FX apps, right?
Click to expand...
Click to collapse
With stock CM camera I don't see these options. This cam app is really minimal. Some say you need to set resolution by entering the hamburger menu upper-left but I don't have the menu. App version is 2.0.002.
With ZOOM FX Premium all resolutions settings are there.
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
bakmanhans said:
When booting my phone this morning I noticed that there is still one MaximusHD ROM leftover. I guess it's not really part of the ROM. It's the boot screen. The first screen you see when cold booting your phone. It's a screen with HTC logo and the development warning text in red underneath it. Can I easily get rid of it?
Click to expand...
Click to collapse
It's not part of the ROM, it's rather a part of the bootloader itself. You can change it by flashing a modified bootloader version:
http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
Just read the thread on how to do that and find the one that fits your HBOOT version.
Coming from MaximusHD my hboot is at version 2.16... I don't see any download for that.
I've been using 20151223 UNOFFICIAL for some time now without the camera/flashlight issue. I've been using the camera more than once during the holidays.
Only trouble I have is getting cellular (3G) back online after flight modus. It's not possible. I have to restart the device every time. Anybody else experiencing this?
No, working great here on 2015-12-23 Unofficial HBOOT 2.16 from Flyer. When going out of plane mode, it takes around 15 seconds to get H icon (for HSDPA, 3G if you prefer). It may be a problem with the SIM card or advanced operator settings.
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)
so i recently read a article that since android pie a couple of xperia devices including the XZP Dont get affected anymore by unlocking the bootloader.
is this true? if so does anything still get affected?
kinda looking for a rom thats a bit fresh or maybe a rom that allows the use of the 120hz display (if possible yet)
not worth it, just sell the phone and get oneplus 6 insted
Not sure "not affected" would be the way to put it; basically the camera works if you didn't backup your TA partition. If you want video enhancements and the clear audio stuff you will still need to backup you TA partition. There are well documented ways of doing all that and it doesn't take too long, just follow the guide and backup/restore your TA partition and you don't have to worry about it. That being said, you still need a modified kernel to make sure the video/audio enhancements work, basically you just need one that hides the fact that your bootloader is unlocked.
From what I heard from others, from what I read from Sony itself and what I have experienced. Unlocking on pie does nothing to degrade camera quality nor does it effect image enhancement nor does it effect sound quality. If u want OTA updates and having everything automated for u, stay stock. If you want complete control of your device and u want to mod it but u would have to update manually here and there go rooted. As for 120hz a few 8.0 roms had it working back in the day, but as for pie I haven't seen anything. And as for the one plus phone. If u like modding it would be a great phone to get but nothing about the one plus appeals to me. I'm Sony man to the core.
The image enhancing did not seem to work for me before I restored my TA partition and flashes a kernel that hides bootloader unlock. It was working for you without doing any of that?