Hello. I used to have cm13+radon kernel. For some time after, I flashed a newer version of cm13, then when speaking on the phone, I experience call drops. I call someone, it accepts the call, but after some seconds (sometimes it's 2 secs and sometimes it's 30 secs) the call drops. But
Then I flashed an older version of cm13 + flashed radon again. But same thing! Then I flashed the rom again (no custom kernel this time) and no problem with calls. Fast forward, yesterday I flashed RR 5.8.0 + agni kernel+cam libs. Same thing happened again. I tried some cm14 firmware, but nothing changed. (actually I bricked the phone.)
Anyway now I am on RR 5.7.4 (nougat roms are buggy without kernels) and no custom kernel. What might be the problem? I can't flash custom kernels.
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
goofball2k said:
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
Click to expand...
Click to collapse
Without flashing kernel, there wont be a problem i guess because, right now I dont have the issue. (rr 5.7.4 no custom kernel). It shouldnt be kernel end, because i havent heard anyone beside me experiences this.
Related
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Hi all.
Generally speaking, I know how to flash ROMs, kernels, and my device bootloader is unlocked, TWRP Recovery in place, and I have a Nexus 5. The problem I have is trying to flash a custom kernel on AOKP ROMs or the few ROMs based on AOKP. After flashing, where normally I would reboot and start up the system fine, with AOKP it just hangs after it powers on where it says "Google" and does nothing more. And frankly, I can't figure out why AOKP, am I not wiping something correctly. Typically I would guess to wipe Dalvik and cache but from my most recent recollection, that still did not help. Yes, yes, there is not anything wrong with AOKPs kernels, but I am both obsessive over this new kernel in particular, and also I want to find the answer why or how to fix for my own personal knowledge. Does anyone have any suggestions? I try to Google search it but I'm not finding anything. *Worth noting here, this also has happened flashing a kernel on a couple Cyanogen based ROMs, but then other Cyanogen based ROMs do fine with custom kernels, so what gives? Any knowledge is appreciated!*
This is bugging the life of me because I love the AOKP Roms, but is it I can't have my cake and eat it to?
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.