Related
Im sure you all know that CM7 has a buggy camera, but i didnt think it would be this ridiculous 0.0. Every time i take a picture, i have to switch to video camera, then back to camera to take the next picture... If i download another camera app, i get a "Forced Close". CM7 is by far one of the best roms ive had so if it means no camera, so be it... But if there is a fix, id really like to be able to use it
Please let me know
Thanks!
I read your post opened up the camera, took three consecutive pictures, switched to gallery and viewed them.
So it works for me. Have you tried reflash or have you installed the latest update?
CM7
yeah, just flashed the update for today and everything seems fine :S. Im not sure why that happened though, happy its fixed
Exclamation ICS camera framerate issue?
I just recently installed the ICS[RC1] build on my captivate, I love it but I just noticed some quite serious issues and I am surprised to know that they haven't been mentioned yet, may be no one else had these but anyway here they are:
1. The camera frame-rate while recording a video is extremely slow compared to the rest of the ROMS which are not ICS based. I verified this a couple o times and it really is very slow, not only in 720p but also in 480p. Also, I cannot pause a video while recording it. I mean it can only be stopped and NOT paused. Now, I don't know if you can do this in the real ICS but i think it is quite an important feature which should be there.
2. The flash player doesn't work properly. In opera, dolphin, boat or any other browser while viewing in desktop mode. I can watch a video but I Cannot go full screen, the whole browser hangs and I have to restart it.
Someone please check if he/she is having these issues or not, I love everything about this ICS port but these things really bother me. Also, these issues were also present in the teamhacksung build[10]
While extremely stable, this build is still not a Full release. There are still Bugs to work out. Be patient.
http://forum.xda-developers.com/showpost.php?p=19680256&postcount=2
What does not work:
Camera (video recording)
Phone encryption
Click to expand...
Click to collapse
I'm not sure about your second point because I have not tried Flash yet.
same problem
i have the same problem with the laggy video recording with RC1 and those bugs mentioned (camera and encryption) were resolved in RC1 but something is still wrong with the camera and i don`t know what...
Glad to know that i am not the only one!
Here is a fix for the video recording not working. This fix works on my Stock Global ROM for the Helium. It may work on CM13 based roms but there may be bugs. This works on the 64/128gb Chinese Helium and the 32gb Chinese Hydrogen.
Helium:
https://drive.google.com/file/d/0B5I_q70mNuR4Vk1xOXQyZ3pfUkE/view?usp=sharing
Hydrogen:
https://drive.google.com/file/d/0B5I_q70mNuR4ZmlKOGx6Qjlid1k/view?usp=sharing
Thanks for trying. Just reporting... On CM13 third edition hydrogen fix doesn't work.The very first time it recorded video with no sound, then on second attempt it recorded just the first frame and no sound. Reboot doesn't help.
nijel8 said:
Thanks for trying. Just reporting... On CM13 third edition hydrogen fix doesn't work.The very first time it recorded video with no sound, then on second attempt it recorded just the first frame and no sound. Reboot doesn't help.
Click to expand...
Click to collapse
Try it on Resurrection Remix and let me know if it works on there. I don't have a Hydrogen so I can't test. There are also so many more options in Resurrection Remix that I don't even want to use plain CM13.
I try it in 2. Edition of CM13. Video work, but i have no Sound.
Tried it right now. RR V2 : Video works but playback seems to be 4x faster than normal. And no Sound.
I really hope you find the problem. It's simple the best phone I eher had.
I hope too, you can fix this. Big Thanks for your help and work.
Worked once twice in Remix. Now it only captures stills with sounds.
RR Mi Max Pro 128GB
Great job, working a treat - thank you.
I have researched/experimented with the video recording bug and I am pretty sure this is the problem.
That is exactly what happens on CM13 based ROMs on Mi Max. I have replicated it by rebooting with usb connected and recording works... dies after usb disconnect and device wakes from deep sleep. I even did dirty remux of brocken recording on my PC and it proved all video frames were there but with incorrect duration.
So looks like we have to wait and hope Xiaomi to fix the device firmware/kernel? part that causes the deep sleep problem on CM(very unlikely) or release source code.
As you probably know the list of all vendor files pulled from miui to build CM is based on the official CM device tree for Note 3 Pro(kenzo) which has very similar hardware... They even pull many of those files for kenzo from Mi Max miui base( android_device_xiaomi_kenzo/proprietary-files.txt). I compared the camera firmwares for both and it is exactly the same bit-by-bit. And yet kenzo CM13 don't have that problem. So it must be some other firmware part or kernel issue.
Also wondering why as far as I know miui doesn't have that problem using same firmware/kernel!? Must be something in the camera app or framework or something...
nijel8 said:
I have researched/experimented with the video recording bug and I am pretty sure this is the problem.
That is exactly what happens on CM13 based ROMs on Mi Max. I have replicated it by rebooting with usb connected and recording works... dies after usb disconnect and device wakes from deep sleep. I even did dirty remux of brocken recording on my PC and it proved all video frames were there but with incorrect duration.
So looks like we have to wait and hope Xiaomi to fix the device firmware/kernel? part that causes the deep sleep problem on CM(very unlikely) or release source code.
As you probably know the list of all vendor files pulled from miui to build CM is based on the official CM device tree for Note 3 Pro(kenzo) which has very similar hardware... They even pull many of those files for kenzo from Mi Max miui base( android_device_xiaomi_kenzo/proprietary-files.txt). I compared the camera firmwares for both and it is exactly the same bit-by-bit. And yet kenzo CM13 don't have that problem. So it must be some other firmware part or kernel issue.
Also wondering why as far as I know miui doesn't have that problem using same firmware/kernel!? Must be something in the camera app or framework or something...
If I have time I will try to build xposed module to intercept the video and fix the first frame duration as dirty/temporary fix(as explained in the link).
EDIT: Ok... As prove of concept build xposed module for testing. It fixes recorded videos but needs some tuning... The first few audio samples are cut off in the repair process and audio gets out of sync. Have to figure out how to fix that...
Just install the attached apk, enable the module in xposed installer and reboot. That's it. Just record as usual. Works with CM and RR(not tested) build-in Camera apps only(for now...).
Click to expand...
Click to collapse
Seems to work on CM13 (3rd version) on my Hydrogen but only if the recorded videos are saved in internal storage (the camera apps non responsive if saving to sdcard). Thanks for putting this fix out, really appreciated.
cmk7128 said:
Seems to work on CM13 (3rd version) on my Hydrogen but only if the recorded videos are saved in internal storage (the camera apps non responsive if saving to sdcard). Thanks for putting this fix out, really appreciated.
Click to expand...
Click to collapse
I should've not called it a fix, it's just a dirty hack... I still can't find a way to sync audio/video properly. That sdcard problem is probably related to much lower write speeds.
nijel8 said:
I should've not called it a fix, it's just a dirty hack... I still can't find a way to sync audio/video properly. That sdcard problem is probably related to much lower write speeds.
Click to expand...
Click to collapse
Thanks for the explanation. Hopefully there will be a permanent fix to the video recording problem in due course. For now, your hack will come in handy.
Let's get back on-topic here thanks guys...
You may want to look at CPUAwake code. with CPUAwake enabled there is no problem with camera after deep sleep and overnight battery drain is still the same (0-1%). It will be great to make "dirty hack" independent from any app (xposed , cpuawake) as a piece of code (somewhere in boot.img inits?). Thank you. as for "no sound" in my patches/builds(some stock miui audio-related files files) I have no problem with it but in some cameras "mono" should be choosen as an audio source. or it could be only "mono" - never tried them separate.
zelipukin said:
You may want to look at CPUAwake code. with CPUAwake enabled there is no problem with camera after deep sleep and overnight battery drain is still the same (0-1%). It will be great to make "dirty hack" independent from any app (xposed , cpuawake) as a piece of code (somewhere in boot.img inits?). Thank you. as for "no sound" in my patches/builds(some stock miui audio-related files files) I have no problem with it but in some cameras "mono" should be choosen as an audio source. or it could be only "mono" - never tried them separate.
Click to expand...
Click to collapse
Yep, my initial test confirms CPUAwake keeps video recording working after device wake up... Thank you for your discovery:good:
I tried a similar idea initiating wakelock before recording but it didn't work...
Is CPUAwake open source? Can't find any code...
I think if we open the hood (UI) there is a single line that tells to the system something like: "system, dont do this !"
somewhere in smalis. cant find it. even worse - dont understand smalis
zelipukin said:
I think if we open the hood (UI) there is a single line that tells to the system something like: "system, dont do this !"
somewhere in smalis. cant find it. even worse - dont understand smalis
Click to expand...
Click to collapse
I actually examined CPUAwake code and it uses android native wake lock acquire() call so nothing special there. And it doesn't release the wake lock till disabled. Don't like that... Trying to find better solution... We'll see...
Let me know if this fixes video recording on CM based ROMs...
Add these two lines to /system/build.prop:
Code:
media.camera.ts.monotonic=0
#[STRIKE]persist.camera.HAL3.enabled=true[/STRIKE]
... and do full reboot(not just soft). USB disconnected... Test video recording, if it works leave device with screen off for 5 minutes, test recording again. It should work(fixed)...
EDIT: I should've mentioned it will only work if video recording was working for you after fresh reboot but brakes when device wakes up from deep sleep... This means all early CM based ROMs are out... they didn't have any video recording working at all or no sound...
EDIT 2: Second line is not needed. Only first line keeps video recording working after deep sleep...
ajsmsg78 said:
Here is a fix for the video recording not working. This fix works on my Stock Global ROM for the Helium. It may work on CM13 based roms but there may be bugs. This works on the 64/128gb Chinese Helium and the 32gb Chinese Hydrogen.
Helium:
https://drive.google.com/file/d/0B5I_q70mNuR4Vk1xOXQyZ3pfUkE/view?usp=sharing
Hydrogen:
https://drive.google.com/file/d/0B5I_q70mNuR4ZmlKOGx6Qjlid1k/view?usp=sharing
Click to expand...
Click to collapse
Deleted
Found the fix in the rr mods folder
Thanks!
Skalexs said:
Deleted
Found the fix in the rr mods folder
Thanks!
Click to expand...
Click to collapse
Could you please help me with a link to that mode?
Ok, the rear camera doesn't open. I can't switch to it in the camera app or snapchat etc. Flash doesn't work either, and if I do the "V" gesture for flash when the phone is locked, it restarts. I have:
* Cleared cache/data
* Disabled and re-enabled the app.
* Dirty flashed OOS 4.1.7 multiple times and have also flashed Franko's Kernel which I normally use (currently running stock kernel though).
* Google camera app multiple times. (had this before too, then I deleted it after this camera problem arose)
Not sure if relevant but TWRP has been giving me some error I haven't been able to fix for some time, and can't delete the file that it says it can't open (through twrp itself or cmd+adb) . Relevant SS attached.
Thanks.
You may want to try to flash the phone using the unbrick tutorial. Make sure you have a backup of internal memory
Hmm, I haven't tried that. I just did a clean install with no success. I deleted everything except USB OTG from TWRP. This has become much harder to fix than it should be . I didn't even do anything to set it off, I was in snapchat and took a pic and then it stopped and the rear camera/flash haven't worked since.
Just to update, I just tried a clean install of NLOS Lineage OS and the rear camera/flash still didn't work. Also, if I try to take any type of video with front camera the phone says "Low memory, adjust the picture resolution or delete some files" even though there's only 3.3 GB of space used.
Also, after a clean flash and wipe of everything the error reported by TWRP no longer exists. So that wasn't what was causing the problem.
Just used the unbrick tutorial. It worked perfectly however the problem still persists and remains unchanged. Anyone have any other ideas?
After some deep diving through forums I decided to use the phone's inbuilt hardware tests, in particular *#808#, as the camera test given by dialing *#*#34971539#*#* doesn't work. Firstly, the flash works through the hardware test (although quick settings still doesn't). The "foolproof camera test" gives BackCamera PASS and FrontCamera Fail. This makes sense as when I go to the individual tests the "backcamera" shows the front camera image, while the "frontcamera" just says "cannot open camera". The PDAF/Cam_EEPROM info test says "FAIL Qualcomm", which I believe is the camera firmware not working. The storage test says "sdcard is unavailable" which I assume is why the camera isn't allowing me to record any video through the selfie camera and says "Low memory".
In summary, how do I fix the camera firmware problem and the sd card error?
RMA your phone, hardware fault.
Ok Thanks.
So there is no way to update/fix the firmware problem?
luusid said:
Ok Thanks.
So there is no way to update/fix the firmware problem?
Click to expand...
Click to collapse
No.
P.S. "Thanks" button is for thanking, by the way. Use it in the future on this forum, whenever somebody helps you.
Im having the same problem on my one plus 3...did u find any solutions??? if yes plz lemme know.
I haven't found a solution.i replaced both The front and back camera and even played with old/new cameras in different configuration (old front + new back / new front+old back / no front + new or old back and so on) varying the result from "Back camera pass/Front camera fail to both Fail ) .the funny thing Is that if you just remove back camera and do the diagnostic menu *#808# > foolproof camera test it still says back camera pass
I have the same problem... And my camera before of this beta worked awesome... Beta 24 **** our phones...
Experiencing the same problem with the front (away) facing camera and the flashlight.
Same Problem for me since the latest official Beta. Ich tried resetting and reflashing the Phone with the last official stable rom. Did not help.
I think I solved this. I let the phone cool down then i powered it off. I let it cool down a bit again and then booted it back up. The camera and FL work.
It seems that this happends when the phone gets heated, at least in my case.
I have the same problem, camera was working fine yesterday. Foolproof camera test shows front camera fail. But the front camera works
Hello
I bought Asus Rog 3 (android 12) after replacing the screen. He has this problem:
- Only the front camera works, when I try to switch to the rear camera, the camera freezes for a moment and switches back to the front camera.
However, if I turn on the google camera in the options, the rear camera works normally.
- Doesn't read fingerprints. Scanner turns on but does not scan any lines.
I thought android 12 broke and I uploaded android 11 from Asus and it's the same. After a while, it updated itself again to android 12.
I have no idea how the fault could be.
Anyone have any advice on this problem?
Are you sure the device re-assembled properly? I've replaced the display in my ROG 3 before, all worked out very smoothly. Nothing special involved beyond making sure motherboard, fingerprint reader, cameras and everything else are all connected back together correctly...
Andrologic said:
Are you sure the device re-assembled properly? I've replaced the display in my ROG 3 before, all worked out very smoothly. Nothing special involved beyond making sure motherboard, fingerprint reader, cameras and everything else are all connected back together correctly...
Click to expand...
Click to collapse
Thanks for the answer.
I was also wondering about it, to be honest, but since the rear camera works in the "google camera" mode and the white line scanner also, but it does not scan the line, the problem is probably in the software.
In fastbootd mode it displays something like this, I do not know if it is correct because it is my first Rog 3
I don't want to open it while it's possible. Therefore, I am asking if any of my honorable colleagues had this or a similar problem.
IrCio36 said:
Thanks for the answer.
I was also wondering about it, to be honest, but since the rear camera works in the "google camera" mode and the white line scanner also, but it does not scan the line, the problem is probably in the software.
In fastbootd mode it displays something like this, I do not know if it is correct because it is my first Rog 3
I don't want to open it while it's possible. Therefore, I am asking if any of my honorable colleagues had this or a similar problem.
Click to expand...
Click to collapse
The screenshot doesn't tell much. However, you won't be able to RAW flash this device from there. Check that your have correct Fastboot access from the bootloader (without navigating to above). Then do a RAW flash to one of the A10 or A11 versions that works.
Andrologic said:
The screenshot doesn't tell much. However, you won't be able to RAW flash this device from there. Check that your have correct Fastboot access from the bootloader (without navigating to above). Then do a RAW flash to one of the A10 or A11 versions that works.
Click to expand...
Click to collapse
Why should I flash in RAW format? What will this change?
Menu, które wkleiłem, to podmenu fastboot.
I downgraded the software from the Asus website to:
- Android 10 (front / rear camera is working properly, fingerprint scanner is not working)
- Android 11 (rear camera not working, fingerprint scanner not working)
- Android 12 (rear camera not working, fingerprint scanner not working)
I don't know where the problem is. I have already written to Asus about this. We'll see what they write back.
I checked the phone's serial numbers on the Asus website and everything is correct.
The phone was not unlocked and rooted. FOTA is working properly.
Just got the latest version dated 01.08.2022
The problem remained.
Hello
As I wrote above.
Asus spoke very quickly. The phone was sent to service in RMA mode. I don't know what they did, but very fast and everything works as it is supposed to.
I contacted the previous owner and it turned out that the screen was replaced on the Asus service. Guarantee until the end of October
And I was so tempted to open it
It's good that I did not do it because it is a little 16/512GB baby girl
Topic to be closed.
Regards
IrCio36 said:
Hello
As I wrote above.
Asus spoke very quickly. The phone was sent to service in RMA mode. I don't know what they did, but very fast and everything works as it is supposed to.
I contacted the previous owner and it turned out that the screen was replaced on the Asus service. Guarantee until the end of October
And I was so tempted to open it
It's good that I did not do it because it is a little 16/512GB baby girl
Topic to be closed.
Regards
Click to expand...
Click to collapse
I am having similar issue my fingerprint was not working after screen replacement but now after few months my front came stopped working it was working three days back on android 10 and 11 i updated firmware from 10 to 11 to 12 and than degraded from 12 to 11 to 10 but issue still exists my front came and whatsapp video call not working back came is working but when i try to switch to front it freezes and screen turns black until cache clears