Related
Hello,
I have a very strange problem:
On my galaxy S4 I9505 android version 4.3 if there is a video player available then the app goes stuck, the apps:
- Youtube
- Facebook (app and browser)
- Browser
The videoscreen stays black and the app goes stuck for a while, the video will never play.
The other similair problem if someone call me or if I want to call someone the phone got stuck as well.
I already tried:
- wipe data and cache / factory settings
- wipe full data to install new rom in philz touch recovery
- Install new rom (4.4 and custom 5.0 lollipop)
The problem remains..
Everything else works perfect but this are 2 important thing what needs to work.
Someone have a Idea?
Important to report: I was on custom lollipop and I downgrade it with the downgrade files on this topic because 4.3 has mirrorlink support for my new car.
http://forum.xda-developers.com/showthread.php?t=2792516&highlight=downgrade
That problems appears when you try to downgrade your device. Reflash stock android 4.4.2 and your problems will be gone :highfive:
Thanks! Tried a few times to flash it back to this stock rom and 4 times failed! Used differtent versions of odin. 3.09, 3.07, 3.04 and some older one 1.85 or something.
I stopped for a half hour (Phone turned off half hour) tried it again and it worked. Very strange but it works.
Thanks very much!
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
I have an extremely persistent set of problems:
1. Unable to record video
- stock camera freezes and the phone restarts (no matter the resolution or storage)
- other camera apps (mx, open, google..) either freezes or acts like its recording but it doesn't
2. While playing some videos, the phone freezes and restarts (in 90% its instagram videos, but sometimes it plays them fine)
What i tried:
- a bunch of roms. The problems probably started with some of them.
- returned to a stock lolipop
- several custom and stock kernels
- a bunch of camera apps
Currently i'm on Audax rom v26.1 with its audax kernel.
Does anyone have idea what could i try?
Could it be a hardware problem? (other than that, camera works fine)
Thanks in advance.
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
hayder78 said:
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
Click to expand...
Click to collapse
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
jmsrajkumar said:
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
Click to expand...
Click to collapse
Hi there,
Sorry, but did not face any issue like that before.
If you have searched a lot for a solution and could not solve it, I suggest that you install this ROM:
https://forum.xda-developers.com/galaxy-note-3/development/purify-cm-13-hlte-n9005-unofficial-cm13-t3337234
This happened to me once after a terrible mistake , which is not related to my above issue. Then I installed this ROM and never looked back. Much snappier phone, lower battery usage and less heated device. I just love it. The only thing that I missed, the better camera app in the stock ROM, and the TouchWiz ability to show multiple apps at the same time.
I strongly suggest that you do a Nandroid backup then give this ROM a try. If you did not like it, you can always return to the Nandroid backup again.
You are frustrated now, like I was. Take a deep breath, and remember that we all went through such bad times with our phone, not just you. This is part of the experience of using such complicated devices. You will solve it eventually, believe me!
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.