Related
Greetings,
The camera on my Note 3 is not working for video recording (taking pics works fine). I have switched a lot of roms and kernels on it, but I noticed the camera app would not record and, instead, show me a "Warning: Recording Error" followed by a force close and, usually, a reboot.
I decided to switch back to stock Lollipop to see if this would revert it, but it didn't work.
The phone specs and other info:
SM-9005
Currently on official Lollipop from Brazil (N9005VJUGBOD5_N9005ZTOGBOD4_ZTO from sammobile)
Stock kernel
These are the things I did to try and fix this, not in order:
1- Changed kernels
2- Changed roms (always wiping everything but internals on recovery before doing so)
3- Cleaned cache
4- Cleaned camera cache
5- Tried google camera app instead of the official camera app (it did not FC, but while it said it was recording, it would never save a video file of it)
6- Did a factory reset on the stock rom
7- Updated modem and bootloader with the files on the Aryamod thread
8- Tried removing the SD card completely
9- Tried reseating the SD card
10- Tried changing to internal card in the camera app
11- Changing recording resolution options
Last custom rom I had was the Omega Rom. First Lollipop rom I installed was the official (non leaked) Poland rom, and I did not use a pit file back then (as, according to the thread this was featured it, that file was meant only for users coming from the leaked lollipop rom).
This is the log from the camera bugging out in the Omega Rom:
http://pastebin.com/TkCA2KbT
I took a second one for precaution:
http://pastebin.com/1exMLTk3
This is not a hardware problem as it worked on KK. The problem persists on the official rom I just installed. Also, the SD card has a lot of space available, as does the internal memory.
Also, not sure if this is relevant, but most kernels give me a bootloop, exception being the Omega kernel and the Darkqueen. I also *may* have flashed by accident a rom based on Cyanogen at some point, but my memory is very fuzzy on this. I think that this wouldn't matter as I wipe everything before putting a new rom in, anyway (and if I did that, the new and now correct rom I put after that wouldn't leave any traces of this accident).
I have no idea what else to do to fix this.
I have exactly the same problem. I have a ZTO Note 3 with the same problem as well, sometimes the whole android crashes after I try to record it.
The whole problem began after I installed the Omega Rom, I used CM12.1 for quite some time and the camera record correctly. I am not sure if you managed to wipe the whole thing by using the TWRP, but once I did, I found out that it was a MTO problem, which I searched about and it was nothing major.
Did you manage to fix the problem?
Maybe install latest bootloader?
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Journyman16 said:
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Click to expand...
Click to collapse
white7561 said:
Maybe install latest bootloader?
Click to expand...
Click to collapse
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Leminur said:
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Click to expand...
Click to collapse
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Video not recording
Do you have a link to the kernel and has anyone else tried this? I'm also having the same problem with the video recording not working and I'm not sure what to do about it.
chickenlittlesound said:
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Click to expand...
Click to collapse
I'm having exact same problem
I'm also having this exact same problem with my N9005 Note 3. Its running Lollipop but i don't really much about roms as i bought it used from some shop. Everything works fine both cameras take pictures but video recording doesn't work at all. Also i downloaded a screen roader app and its videos are also not recorded. When i finish recording them and go to gallery it says File Corrupted. Please anyone got fix of this problem yet?
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Hi everybody,
@hayder78,
I tried to do the same to fix the issue: flash with the last firmware available for my region code (XEF - N9005XXUGBOK6) using Odin 3.11.1 and the same options (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update) but I still have the issue.
@Fenrir007
Did you manage to fix the issue using the same method?
I had the same issue with a 6.0.1 ROM (MagMa-NX UX8.5) on my Note 3 N9005. Any attempt to record video merely resulted in a "recording failed" message after about a second.
I thought I had installed a recent bootloader and modem using Odin 3.11.1, but although I did it twice I had used a "Reboot to Download" restart and for some reason that does not seem to have taken properly - although I have no idea why, all the display messages said it had worked.
So I have just done a full (remove battery and then three-finger power-up) boot into Download as advised in this thread, and then sent the same BL_N9005XXSGBQA1 and CP_N9005XXUGBOJ2 files to the phone via Odin, and now video recording works fine.
So when people say clean boot into Download, they do actually mean it. Thanks folks!
Oh, and I did NOT need to tick the "clear EFS" option, which seemed a rather risky thing to try so I was avoiding it as long as I could.
Andre
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Tzheng456 said:
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Click to expand...
Click to collapse
I had the same issue with O2. I changed kernels and the problems persisted. A also word the device and started from scratch through fastboot and the issues persisted. I ended up on hydrogen and I've never looked back. There is a flashable zip in that thread for the newest full version .11. Follow the steps wipe everything besides internal storage, flash the full v11 zip and boot the phone. After this reboot to recovery (power and volume down). Flash the gapps and super su zip if you want root. After this you should be able to add your Google account and be good to go. One thing I did was remove all Chinese apps and the stock launcher. I use trebuchet launcher from cm 12.1. Phone runs incredibly smooth now. I recently started running AK kernel as well. The oxygen version works with hydrogen. I have been averaging between 5 and 7 hours of SOT for battery with up to 8 if I'm just watching videos. Hope this helps. The ROM is a little simpler and the notifications settings are different. But you can set apps to have priority notifications and they function similar to oxygens notifications at that point. Everything is in the thread if you have any questions I'll try to help you.
Solved for me with that boot.img from Silesh.Nair:
http://forum.xda-developers.com/moto-g4-plus/help/camera-records-video-1080p2-t3517934/post70107680
________________________________________________________
XT1642, MM modem, random custom roms
Hello guys, finally I got an error where the snapdragon camera app records video only in slow motion, see Screenshot attached while checking the video on my pc.
That was never before flashing RR 5.8.0 20161208 7.1.1 build,but I don't think it has something to do with it
Temporary workaround:
I figured out it can fixed once I clear dalvik/cache in twrp, boot rom and then record video with snap app.
Open camera crashes(camera hardware is busy cause of usage from others), wasn't before...
But after closing app and waiting some time(seconds minutes) the app only records slow motion. This happens if storage is set to internal or SD card,it's always the same.
What I did already:
-wipe everything, including internal storage, several times
-clean install of cm14.1, 3 different versions including from today. RR 5.8.0 20161126, RR 20161208. Without restoring anything.
-also with @Silesh.Nair additional boot.img for builds before today
Changed sd card from 32 to 64GB
-changed sd card from fat 32 to extfat
Restoring full backup before it happens
-dirty flash several of above roms
-logged the video recording with and without this bug https://drive.google.com/folderview?id=0B4Zy8uoEfFKLbjlYOW5WcW02LXc
But still persists... :crying:
-flashing stock rom is the next step to do
So my questions are:
-anybody seen this before with MM modem?
-any other hints somebody know?
I don't want to upgrade to N soak test for firmware files unless it's the only way! Because downgrade can cause additional problems!
I opened new thread because it's complex problem I though and maybe does nothing have to do with custom roms only...
Thanks in advance!
Till now i haven't recorded anything with my phone, but as your asked, i tried first time to record video on RR-N and my problem is also different than you too, mine is single photo to complete video... Nothing got recorded... Only single photo where from video recording started.... I checked on MOTO CAMERA too.. same on both...
Will see on other ROM...
Edit: I'm also on MM baseband, if anyone on N baseband pls confirm....
__Madddy said:
Till now i haven't recorded anything with my phone, but as your asked, i tried first time to record video on RR-N and my problem is also different than you too, mine is single photo to complete video... Nothing got recorded... Only single photo where from video recording started.... I checked on MOTO CAMERA too.. same on both...
Will see on other ROM...
Edit: I'm also on MM baseband, if anyone on N baseband pls confirm....
Click to expand...
Click to collapse
Thanks for this information! I see this in my system information for baseband:
As I never flashed another baseband/modem file or M soak test I came to the conclusion, that maybe flashing the provided boot.img from @Silesh.Nair (to bring back Hotspot on RR) messed up my baseband and other firmware files like the camera.
@Silesh.Nair could it be or am I wrong?
Thanks!
strongst said:
As I never flashed another baseband/modem file or M soak test I came to the conclusion, that maybe flashing the provided boot.img from @Silesh.Nair (to bring back Hotspot on RR) messed up my baseband and other firmware files like the camera.
@Silesh.Nair could it be or am I wrong?
Thanks!
Click to expand...
Click to collapse
My baseband is same as your's, since we both haven't flashed N soak.. nothing related to messed with baseband.. I'm trying other ROM, will see...
---------- Post added at 05:16 AM ---------- Previous post was at 04:21 AM ----------
Don't know what went wrong with previous setup, now clean flashed again with and without Boot.img also flashed boot.img with CM14.1 worked fine in all cases....
As you said it's slow motion, i have something related to that,
if snap is opened first time after every boot then it's lagging, and video recorded is of lagging images.. for that, close snap and open again.. it will work..!!:good:
Edit:
It worked only for little while after wiping cache..
And then same as before...
__Madddy said:
My baseband is same as your's, since we both haven't flashed N soak.. nothing related to messed with baseband.. I'm trying other ROM, will see...
---------- Post added at 05:16 AM ---------- Previous post was at 04:21 AM ----------
Don't know what went wrong with previous setup, now clean flashed again with and without Boot.img also flashed boot.img with CM14.1 worked fine in all cases....
As you said it's slow motion, i have something related to that,
if snap is opened first time after every boot then it's lagging, and video recorded is of lagging images.. for that, close snap and open again.. it will work..!!:good:
Click to expand...
Click to collapse
I can close snap camera and open it again, but still only 2fps after recording. I need to boot recovery and wipe caches, then after reboot it only works as long as snap camera is open. When I close it once it begins again to record 2fps
Did you have the same baseband as me after flashing other roms? Maybe last thing is flashing stock MM with fastboot?
strongst said:
I can close snap camera and open it again, but still only 2fps after recording. I need to boot recovery and wipe caches, then after reboot it only works as long as snap camera is open. When I close it once it begins again to record 2fps
Did you have the same baseband as me after flashing other roms? Maybe last thing is flashing stock MM with fastboot?
Click to expand...
Click to collapse
Yes, same MarshMallow baseband..
As i mentioned my problem in first reply, it get solved by clean flashing, you should try clean flash again..
Oopsie. I have this problem too. Single image, audio has no issues.
Force closing snap doesn't fix things.
I'm on RR, N baseband, latest build. I think the boot.IMG by @Silesh.Nair is the cause here. Is it incorporated into the ROM?
Here's the log, http://pastebin.com/xg7GFvvC
Just after video was taken with Snap and then played on Google Photos.
zeomal said:
Oopsie. I have this problem too. Single image, audio has no issues.
Force closing snap doesn't fix things.
I'm on RR, N baseband, latest build. I think the boot.IMG by @Silesh.Nair is the cause here. Is it incorporated into the ROM?
Here's the log, http://pastebin.com/xg7GFvvC
Just after video was taken with Snap and then played on Google Photos.
Click to expand...
Click to collapse
Sounds weird :silly: I used latest cm14.1 build non oms, clean flash. And here's the problem too.
Actually i restored a backup of RR 20161126 build (every thing was OK on this backup) without the mentioned boot.img but the problem persists(can take some vids, then slow motion again).
http://forum.xda-developers.com/moto-g4-plus/help/help-thread-custom-roms-t3513118/post70080516
http://forum.xda-developers.com/moto-g4-plus/help/help-thread-custom-roms-t3513118/post70080516
These happen to people who flashed soak test as well
strongst said:
These happen to people who flashed soak test as well
Click to expand...
Click to collapse
Something broken from source..!
I don't think we can solve this problem without developer's help.. i don't want to mention silesh nair as his conditions he said in help thread.
I hope @rahulsnair and @vache will look into this..
Can you play the recorded videos on a computer or on another phone ?
vache said:
Can you play the recorded videos on a computer or on another phone ?
Click to expand...
Click to collapse
I haven't tried video elsewhere, but you can see attachment in OP, it's photo of computer i think... So, not working...
Video getting recorded, is also getting damage at same time..
You can check Logs in OP..
vache said:
Can you play the recorded videos on a computer or on another phone ?
Click to expand...
Click to collapse
I can play the video on smartphone or as you see on my pc. But it is only with 2fps. Sometimes I get what Maddy and others said, it's only a picture with sound. Like a corrupted file
I'm actually testing this behavior on latest Vanir aosp, but at the moment and around 30 videos recorded i can't get this error. All videos are as they should be. But I'm still testing at the moment
Ok, since nearly 24h testing with latest Vanir rom the problem mentioned in op didn't happen anymore.
Only one thing: after recording a video you should close snap camera, reopen and then play the video with link on the left side. If you play it immediately after recording, the gallery app crashes/freezes. You can also close snap camera after recording and open Gallery separately or another viewer app. No matter if video will be saved to sd or internal storage.
I know it's not a solution for the problem, but a workaround for me
Maybe some dev can compare RR/cm14.1 with Vanir and check the difference that can cause this behavior.
If I can help further, I will do it.
Try this boot image on cm.
https://drive.google.com/file/d/0B1ZbHDX3hq1yVjlQMWpELVBXYnc/view?usp=drivesdk
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
Try this boot image on cm.
https://drive.google.com/file/d/0B1ZbHDX3hq1yVjlQMWpELVBXYnc/view?usp=drivesdk
Click to expand...
Click to collapse
Works in RR, on Snap!
XT1643, 5.8.0. N modem (latest OTA).
Fails on OpenCamera.
Got some issues with video after flashing last soak on my XT1642. Phone rebooted after launching gallery app (even without trying to play a video), i was still able to shoot videos. I tried to flash many ROMs, some old ones, still same issue. Wiped and formatted almost every partition without success.
Then i decided to flash last MM full firmware, and now it's working like a charm. Dunno what appended here...
strongst said:
Ok, since nearly 24h testing with latest Vanir rom the problem mentioned in op didn't happen anymore.
Only one thing: after recording a video you should close snap camera, reopen and then play the video with link on the left side. If you play it immediately after recording, the gallery app crashes/freezes. You can also close snap camera after recording and open Gallery separately or another viewer app. No matter if video will be saved to sd or internal storage.
I know it's not a solution for the problem, but a workaround for me
Maybe some dev can compare RR/cm14.1 with Vanir and check the difference that can cause this behavior.
If I can help further, I will do it.
Click to expand...
Click to collapse
You didn't tried any other ROMs appart CM14 and RR before ?
vache said:
Got some issues with video after flashing last soak on my XT1642. Phone rebooted after launching gallery app (even without trying to play a video), i was still able to shoot videos. I tried to flash many ROMs, some old ones, still same issue. Wiped and formatted almost every partition without success.
Then i decided to flash last MM full firmware, and now it's working like a charm. Dunno what appended here...
You didn't tried any other ROMs appart CM14 and RR before ?
Click to expand...
Click to collapse
Nope, only cm14 and RR then vanir,hence still on MM firmware. But I flashed the provided boot.img in RR 7.1 thread to fix Hotspot issue on latest 7.1.1 RR and the snap bug happen first.
Actually restored backup of 20161226 RR and testing again together with Silesh.Nair's boot.img
Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...
Is working dual sim and volte
Is works dual sim and volte
Sim working fine??
What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .
thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.
shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.
After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.