Related
After about 5-7 seconds of recording in 720p I was getting recording failed problems every time. It wasn't doing that before or at least not very often until recently. So I decided to update the camera firmware. I go to the camera firmware update screen by dialing *#*#34971539#*#* I selected phone to CAM FW Write and I go to update the firmware to version 2.0.3 it downloads up to 225/253 pieces then stops and says the update is a success, then it tells me to reboot. I reboot the phone with the volume down and power button, and I find out the camera firmware isn't installed properly. Now under camera info it is displaying.
[TBEC27 :
TBEC27 :
NONE]
I don't remember exactly what it said before but I know it said something different. The rear facing camera is now messed up and displaying green. This is happening with all the different camera apps that I tried on the market. I also did a factory reset, cleared the cache and wiped the data. Still I'm getting the same problem. The camera info is displaying the same thing to so I know for a fact that the factory reset didn't reset everything. Maybe someone here who has the same phone can help me out by dialing *#*#34971539#*#* and going to "Phone/CAM FW Ver Check." Tell me what it says if you don't know how to directly fix the problem. If someone here does know how to fix the problem it would be helpful though. I'm rooted and I'm currently running stock Froyo 2.2.1 if that helps.
Once I figured out how to root and flash with the Infuse, I didn't waste much time at all staying on Froyo. However, I've had video recording issues that ended up being caused by the kernel. I suppose it's possible that it could be an issue with the Froyo Community Kernel (I'm guessing/assuming that's how you rooted). Any particular reason you'd not want to just back up your apps and upgrade to Gingerbread?
ApexPredatorBoids said:
Once I figured out how to root and flash with the Infuse, I didn't waste much time at all staying on Froyo. However, I've had video recording issues that ended up being caused by the kernel. I suppose it's possible that it could be an issue with the Froyo Community Kernel (I'm guessing/assuming that's how you rooted). Any particular reason you'd not want to just back up your apps and upgrade to Gingerbread?
Click to expand...
Click to collapse
I'm rooted and on gingerbread 2.3.6 now actually. It didn't fix the camera, but I'm able to go into the camera firmware settings and it's now showing
[FWFAILED:
TBEC27 :
NONE]
Every time I try to flash the firmware now it says "firmware update failed try again." I read somewhere that you have to remove the camera before doing a camera firmware update. I opened the phone up and it doesn't look like the camera can easily be removed and put back in.
hockeyjons said:
I'm rooted and on gingerbread 2.3.6 now actually. It didn't fix the camera, but I'm able to go into the camera firmware settings and it's now showing
[FWFAILED:
TBEC27 :
NONE]
Every time I try to flash the firmware now it says "firmware update failed try again." I read somewhere that you have to remove the camera before doing a camera firmware update. I opened the phone up and it doesn't look like the camera can easily be removed and put back in.
Click to expand...
Click to collapse
I hate to keep harping on the same thing, but I'm not so sure it's a camera firmware issue, and you may be making a mountain out of a mole hill. If you happened to upgrade with Heimdall, and you're not already running one of them, it may be worth trying one of the kernels in this post, for ****s and giggles:
http://forum.xda-developers.com/showpost.php?p=23118144&postcount=2
I've never had any issue with the camera, aside from what was caused by a kernel, so aside from that advice, I've nothing else to offer. Good luck.
I am not able to understand these white/blue spots across the images. Please see the attached images and zoom in to look in the highlighted areas. It's not dust for sure as I have cleaned the lens and the photos were shot in auto mode (no change in ISO etc). IS there an issue with Nougat beta camera or is my sensor damaged?:crying:
What variant you have (L09 or L04) and which firmware you're running (B1..)?!
I am sorry for hijacking this forum, but I have an Honor V8 variant (the big sized version) with EMUI 5.0. beta. There is no xda forum on this model, hence I posted here. I am not sure if the s/w is the issue as I tried it with other camera apps as well producing the same issue
try a 3rd party camera to see if it is still there, if so try reflash stock rom.
If 3rd party apps don't work, then look if there's an update for your phone
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
yes it is probably a hardware issue, but you will have to flash stock to completely rule out a software issue. back up data using twrp
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Its a 50 50 situation, some early buyers of honor 8 had the same issue, but after an OTA it's gone.
If it's a hardware issue, return it back if you have warranty.
A friend of mine had the same issue but it was fixed after the update.
Neil6684 said:
A friend of mine had the same issue but it was fixed after the update.
Click to expand...
Click to collapse
Do you mean those spots on zooming in? I have been through 2 beta-Nougat updates, but its not yet resolved. I will factory reset over this weekend and check.
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
linom said:
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
Click to expand...
Click to collapse
It's a software issue, don't worry.
If RAW images are fines, then it's just a problem of processing when taking a JPEG photo
An update should fix this
DarkGuyver said:
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Click to expand...
Click to collapse
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
It's better for you, and when you buy a device make sure it's officially supported in your country (like honor 8) .
All the best
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
I'd contact Honor directly and ask them about the problem. Maybe they will release a software patch for it. But I have never heard the Honor 8 had this problem.
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
linom said:
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
Click to expand...
Click to collapse
Unfortunately, we don't know the exact files (libs that are responsible for image processing)
linom said:
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Click to expand...
Click to collapse
You would have to contact Honor directly for instructions on how to restore Marshmallow back onto your device. They will also be able to provide you with a link to the Marshmallow firmware for your device.
There are a few problems I've seen so far:
When taking photos on auto-timer mode they're blurry and out of focus + some specific bug with the gif-creation method.
I've no idea how to send a bug report to Samsung (if you do, do tell) and I really need an operational camera.
So, I decided to install a rom instead.
Recommendations for the roms with the best camera-related software?
Other things I hold as important are night mode and battery saver
Ps before someone brings it up:
I have experience with installing roms. I gave the original rom a try for once. I'll still go over the actual rom threads of course but if you can save a sister some time and share some knowledge, help would be much appreciated.
Thanks a lot and stay safe ya'll
I feel worst camera quality with every update! Don't know what's going on!
IS your Snapdragon or Exynos version?
may update
if you have updated to the may security update i dont think you will be able to flash roms as samsung have locked the phones ((s10e) out, i cannot root anymore and you cant factory reset! i was running stock rom with root and magisk and after flashing may release in odin with patched firmware the phone started acting very strange, flashing screen and unresponsive i had to reflash stock and all is well but no more root, twrp or magisk !! i may be wrong but that is my experience if anyone knows different please tell gutted!
update: was a bit rusty didn't realise the may update needed an updated twrp recovery, I flashed may update on April twrp!! - all fixed now on ctd1 with 104 twrp and root is well, many thanks to all the developers who make it possible, cheers! if you do flash above make sure you don't update your time zone data you will get a notification dont let it install as you will be starting over again!! switch off automatic time updates, this has been my experience! thanks all.
StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.
Thanks you very much
I will test
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Just a question, does StatiXOS have slim recents included?
Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.
Is anyone else having issues with sending a text message with this rom?
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
Double Post
Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.
chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..
The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.
SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.
My attempt to install the OOS Cam bricked my phone.... so my question is Why did my phone got bricked exactly? I want to know what I did wrong since I really want to use the OOS Camera.So I was trying to get the original stock camera app to work on my device because the other ones looks horrible. I mean I have a kind of flagship device and the photo quality looks like my old cheap Huawei phone.
First I tried with an 3.x.x version of the app installed as an normal application. It works but the quality is still bad.
This is where I got that apk: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/
On Reddit there is a post that said if you replace the Camera.apk on /system/app/Camera with the OnePlus Camera it should work.
The result? It worked and the quality seems better!....but some functions of the app like video or changing the size of the picture crash the app. Now the phone got really hot for some reason. No idea why but anyways I decided to go "creative" and I analyzed the official OxygenOS Rom(This is where I got the OOS Camera apk) to see what files where related to the OnePlus Camera app and then I pushed it through ADB to the respective directories of my phone.
These are the directories that I added with their specific files:/system/priv-app/OnePlusCameraService/
/system/system_ext/priv-app/OnePlusCamera/
/system/system-ext/priv-app/OnePlusGallery/
Then I rebooted the phone expecting to see the OnePlus Camera working in all it's glory!...The phone got stuck in the boot logo.
The phone stays on the boot logo for some seconds, then reboots again but this time in Recovery mode and says this:
Can't load Android System. Your data may be corrupt. If you continue to get this message, you might need to perform a factory data reset and erase all user data store in this device.
Click to expand...
Click to collapse
I did the factory data reset but it did not work.
Now this might seem relatively easy to fix by using adb right? Well it is the worst moment to have the usb port damaged so until I fix that I have this beautiful OnePlus Paperweight.
The last detail is I actually deleted a folder which contained the .xml config files of the OOS Cam I installed on the second try because I thought it might cause some issues with the last try. Those files were on /system/data/
The phone have the bootloader open because I use a custom ROM and this one is called "/e/" which is based on Lineage OS. I used the wireless ADB function since my usb port is damaged, it jsut works as a charge port.
Again my main motive to this post is to understand "what did I do wrong?". I don't get why Android thinks the data is corrupted. The files are the official ones and as far I know I didn't deleted any important files. I even want to try with a more modern version of the app since I use the 6.4.45. This is the one that came on my phone the moment I opened the box. I want to see if the quality of the pictures got better with a newer one.
If you read this massive dump of text...thank you!