Hi,
As the title stated, I have Redmi Note 3 SD with LineageOS installed. My phone suddenly dies at 40% when I put it on standby. Sometimes when I open camera app, it dies at 50%. I've tried many ROM including ViperOS, RR, but I haven't tried with MIUI yet mainly because I don't really like MIUI.
Have any of you guys get same experience as mine? What you guys do about it?
I'm planning to replace the battery because I thought it was the battery problem. But if you guys have any suggestions that would be great!
Thanks!
Update the IOS problem will be solved with new 11.2.1 version.
Just kidding
I would replace the Battery to fix issues like this if you the only one related to a specific Rom.
If you search trough the los thread you will see that some people had the same issue. I am not sure how they fixed it but i think some of the custom kernels had a patch to deal with this issue. I cant remember which one ( agni or radon) so you should search trough and/or ask those kernel developers.
This problem solved by changing kernel to francokernel. Thanks!
bradhawk said:
This problem solved by changing kernel to francokernel. Thanks!
Click to expand...
Click to collapse
try Nitrogen OS
Related
Hi to everyone,
I tried several kind of Rom 4.4.2 CM and AOSP and in all of this kind of rom i found a problem with camera that goes in FC.
The first time after install it seems work well but then some second of use goes in fc, starts to crash and device restart and this happens Always camera comes open.
I search and tried some apperently Fix but without success.
thanks
Flashing this might help you.. http://www.mediafire.com/?795s91e1b548gxa
thanks
for link.
I tried but doesn't work. I tried an orginal rom based on AOSP and on this seems work.
Now I must install a 4.1.2 to have an efficent device.
I've been on SlimSaber (SlimKat unofficial by fusionjack) and never once had this issue in quite a few months. However I've also tried 4.4 pac, beanstalk, spirit rom and probably others that I've forgotten without this problem.
To ask the obvious, you do install these roms with a full wipe right? The other thing, are you using the official aosp camera that comes with the rom? Or another app that uses the camera (e.g snapchat, instagram for example? There's a bug with the nexus 5 in which the camera will sometimes crash when using it with a third party app. I guess it's possible for this bug to filter down to our device... As I don't use any such apps I can't comment on my own experience with that. But google that issue to read more, you'll find plenty on forums about it.
Sent from a galaxy far, far away
Hi,
and thanks for the reply.
I tried OMNI rom that is based on AOSP and now la SOKP.
For now only the Omni has been the better with the camera, but this rom doesn't have the same setting of a Slim.
SOKP goes like other AOSP rom. When camera is active for some moment seems work well so moving device to see and touch the screen on photosphere it goes in FC and reboot.
Some days ago, i do this test drag the Omni rom camera on Slim. result app in fault like all rom.
Can anyone explain me why happen if android, base rom are the same?
Hello there..!!
I just got a XT1521, as a secondary device. Its currently on stock Android 6.0 with baseband M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS_CUST
I want to make it just like the Pixel. I do know where to get the required files, and don't need any help regarding that.
All I wanna know is :-
1. What's the procedure to unlock bootloader on this device? Unlocked successfully
2. Which recovery should I use? I used Squid2's TWRP v3.0.2-r1
3. Which ROM can be used as a daily driver? (need 7.0+ to get Google Assistant working). My preferences are good battery life (if not extreme) but the performance should be smooth without any lags, unlike the stock M. Also, wifi, OTG support and other features should be working properly.
Flash Seraph08's CM14.1, its totally smooth with wifi, otg and everything working. Also, I've managed to install Google Assistant successfully
4. What's this adoptable storage thing that people are having problem with..?
Didn't faced this problem myself. Maybe because Im not using ext sd card.
5. Should I flash a custom kernel too? If yes, which one and why?
Didn't found any need to do so, stock CM kernel works just fine for me.
Thanks to you for reading through all of this and please be kind enough to answer. :silly:
Heres the link for pixel experience by faserf
http://forum.xda-developers.com/android/apps-games/google-pixel-experience-launcher-dialer-t3478907
2. Twrp recovery by squid2
3.CM14.1 by seraph08 (reubenPCA is the thread operator)
Here's the link-http://forum.xda-developers.com/moto-e-2015/orig-development/rom-cyanogenmod-14-1-t3492794
4. I faced no such issue in cm14.1.
5.nope you don't need any kernel, cz the stock one performs excellent.
ASKdroid said:
CM14.1 by seraph08
Click to expand...
Click to collapse
First of all, thanks bro for the reply.
Have you tried the CypherOS 3.1.3?? That seems good too but is having wifi problem, though in the latest version only.
Everything works fine in the CM14.1 you suggested, right? Even the wifi / tethering, VoLTE and OTG..?
VOLTE is still not available in any ROMs as far as i know, and for everything else works also i had tried cypheros 3.1.3 but i had some issue with that lyk the music would play on loudspeaker even if my headphones were connected(it also showed in the status bar , the headset icon after i connected my headphones) so yes i found cm14.1 better than cypheros in terms of performance
ASKdroid said:
VOLTE is still not available in any ROMs as far as i know, and for everything else works also i had tried cypheros 3.1.3 but i had some issue with that lyk the music would play on loudspeaker even if my headphones were connected(it also showed in the status bar , the headset icon after i connected my headphones) so yes i found cm14.1 better than cypheros in terms of performance
Click to expand...
Click to collapse
Thanks mate..!! I appreciate your reply. BTW, stock Marshmallow does support VoLTE, but since its my secondary device, I can live without that.
Yeah stock mm firmware supports VOLTE but then my phone would lag a lot on stock, so it's really difficult to stay on stock and that on jio half the calls wouldn't be placed due to interconnectivity issues, so i used stock for hardly 2-3 days.
As you know in the title of this thread, I, like many people using Marshmallow-based ROMs for G7102, am having some problem with the regularly dropping issue of Wi-Fi. Checking all the info and logs of the Wi-Fi, I notice some very strange behavior
1/ In DHCP mode: Scan constantly even when connected to a network, after few scanning, the phone started to disconnect and begin re-handshake with the network
2/ In Static mode: After changing to the Static mode with an appropriate profile (tested profile on another device), the phone connected to that Wi-Fi then said that there is no connection (even the profile is correct and tested), after that disconnect and re-connect constantly, turn into Wi-loop
All of this happened even when the phone is in onscreen, sleep happened to be a little bit more intense with the DHCP mode problem. Wi-Fi, even in an intense usage, will drop. That's really a nightmare for a normal user, let alone an MOBA gamer and streaming-enthusiast. This happened to me with all Marshmallow for G7102 ROM (XOSP, AOSP, CM) - now I'm using XOSP.
I hope that we could find a solution to this problem or, at least, discuss this problem together.
Btw, I found someone said that Rio Kernel should fix the problem, but I don't see the link to the kernel. Can anyone upload it here for me to test it?
Your ROM Name & Version ?
Kevin Saiza said:
Your ROM Name & Version ?
Click to expand...
Click to collapse
It's XOSP-6.3-UNOFFICIAL-20160712-ms013g based on 3.4.0 Cyannogenmod Kernel, running on Android 6.0.1
You can find it HERE
wiFi drops in grand 2 6.0.1
Iam also having this problem iam using RR remix
Please someone give me fix of this
parroted.dev said:
Btw, I found someone said that Rio Kernel should fix the problem, but I don't see the link to the kernel. Can anyone upload it here for me to test it?
Click to expand...
Click to collapse
The Rio kernel doesn't work in marshmallow based rom I tried that.
mahmmoud1231 said:
The Rio kernel doesn't work in marshmallow based rom I tried that.
Click to expand...
Click to collapse
I can't talk for sure that the problem lie on the kernel (cuz I also knew that Rio kernel just run for older Android version, but some of the post's replies talk about it like a cure for the problem)
But I have a theory that the problem related to the IP mechanism, cause based on the inconstant behavior of WiFi (Static and DHCP problem).
Have any idea?
parroted.dev said:
I can't talk for sure that the problem lie on the kernel (cuz I also knew that Rio kernel just run for older Android version, but some of the post's replies talk about it like a cure for the problem)
But I have a theory that the problem related to the IP mechanism, cause based on the inconstant behavior of WiFi (Static and DHCP problem).
Have any idea?
Click to expand...
Click to collapse
Sorry no I don't have any idea but if you want the Rio kernel to test it. You can get the link from a
video on YouTube :Note 7 ROM on Grand 2 | Noble ROM 2.1 REVIEW And
the link is in the description or in the comments below.
Good luck.
mahmmoud1231 said:
Sorry no I don't have any idea but if you want the Rio kernel to test it. You can get the link from a
video on YouTube :Note 7 ROM on Grand 2 | Noble ROM 2.1 REVIEW And
the link is in the description or in the comments below.
Good luck.
Click to expand...
Click to collapse
Thanks, I will test it asap.
Device:
Redmi Note 3 Pro, Snapdragon, 2GB RAM, 16GB Internal.
Currently on ViperOS Coral with stock kernel. (latest version of magisk is installed)
Hey community (and hopefully devs)!
As the title suggests, (I think) I broke my vibration motor. Basically, I flashed two custom kernels on top of each other. I really don't have any more info about that, like which ROM or kernels I used. I know, there were warnings everywhere, I've seen them.
Anyway, all I'm asking is if there's any flashable zip or maybe edit of the build.prop to fix this issue.
I've tried RR, LineageOS, NOS, ViperOS, CosmicOS, AOSPA, AOSP Nougat and AOSP Oreo with Radon, Agni, ElementalX and Infected for kernels. All of them were at the latest version at that time. The firmwares used were (and still are) miuifirmware_kenzo_7.7.6 and miui_HMNote3ProGlobal_7.7.20_Firmware. Alongside those ROMs and kernels, I've used Kernel Aduitor. Having tried all of those, vibration had not worked fully. Sometimes, rarely, there was a gentle vibration when I pressed a button or letter, that's all. Though that gives me hope it can be fixed.
I really do need that vibration to work, it's how I used my alarms to wake up. Just sound doesn't cut it. School year's about to start and this being my final year, I want to go all in. But, I can do nothing if I'm asleep.
Please, for the love of me, provide sings useful feedback. I do need to fix it, and service centers aren't an option.
Thank you all.
PS0: I know it'll sound crazy, but if any dev reads this and wants to fix this issue, as I'm not the only one who faces it, please, at least send a message out leave a reply here. Any logs or other feedback, I'll be more than happy to try and provide!
PS1: I have not yet searched on MIUI forums. I do dislike all MIUI themed stuff.
:good::good::good::good:
Flash miui fastboot rom
Flash miui using miflash, it should get everything back to normal.
alright mates. i will try flashing the stock rom. i'll keep you posted for any difference.
0kanenas0 said:
alright mates. i will try flashing the stock rom. i'll keep you posted for any difference.
Click to expand...
Click to collapse
Any updates? Did it work?
---------- Post added at 01:33 AM ---------- Previous post was at 01:32 AM ----------
0kanenas0 said:
Device:
Redmi Note 3 Pro, Snapdragon, 2GB RAM, 16GB Internal.
Currently on ViperOS Coral with stock kernel. (latest version of magisk is installed)
Hey community (and hopefully devs)!
As the title suggests, (I think) I broke my vibration motor. Basically, I flashed two custom kernels on top of each other. I really don't have any more info about that, like which ROM or kernels I used. I know, there were warnings everywhere, I've seen them.
Anyway, all I'm asking is if there's any flashable zip or maybe edit of the build.prop to fix this issue.
I've tried RR, LineageOS, NOS, ViperOS, CosmicOS, AOSPA, AOSP Nougat and AOSP Oreo with Radon, Agni, ElementalX and Infected for kernels. All of them were at the latest version at that time. The firmwares used were (and still are) miuifirmware_kenzo_7.7.6 and miui_HMNote3ProGlobal_7.7.20_Firmware. Alongside those ROMs and kernels, I've used Kernel Aduitor. Having tried all of those, vibration had not worked fully. Sometimes, rarely, there was a gentle vibration when I pressed a button or letter, that's all. Though that gives me hope it can be fixed.
I really do need that vibration to work, it's how I used my alarms to wake up. Just sound doesn't cut it. School year's about to start and this being my final year, I want to go all in. But, I can do nothing if I'm asleep.
Please, for the love of me, provide sings useful feedback. I do need to fix it, and service centers aren't an option.
Thank you all.
PS0: I know it'll sound crazy, but if any dev reads this and wants to fix this issue, as I'm not the only one who faces it, please, at least send a message out leave a reply here. Any logs or other feedback, I'll be more than happy to try and provide!
PS1: I have not yet searched on MIUI forums. I do dislike all MIUI themed stuff.
:good::good::good::good:
Click to expand...
Click to collapse
I was on Viper 3.0 as well. Flashed ElementalX, then dirty flashed ROM, Flashed agni, dirty flashed ROM again and got this very problem.
Did you manage to fix it?
I did not flashlight the stock MIUI ROM, thus I do not know if that'd be a possible fix for this issue.
(I cannot stand anything premade, that I did not get to mess around. That's the reason why I didn't flash it.)
So I don't know how my vibration came back this morning but I lost it after a few hours.
This happened all of a sudden a few weeks after I lost the vibration under similar circumstances as stated in the OP.
This is quite surprising since it worked without any problems - it wasn't weak or inconsistent for the few hours I had it running today.
Could anyone please explain.
Hey there! I had the same problem. Problem arose when I was on CosmicOS on stock kernel. I don't have any service centres nearby so on the suggestion of my friend, I switched to NOS and the vibration motor started working after 2 days. Wierd, and I don't know whether CosmicOS was the problem but NOS has fixed it.
rkmadotra said:
Flash miui fastboot rom
Click to expand...
Click to collapse
ROM flash nahi ho rahi hai
Why with miui with my modem wi-fi is fixed while with all the built roms it keeps being unstable? are bugs of the lineage 14 and 15 ? Do you know how to answer this question?
baggino said:
Why with miui with my modem wi-fi is fixed while with all the built roms it keeps being unstable? are bugs of the lineage 14 and 15 ? Do you know how to answer this question?
Click to expand...
Click to collapse
I think the wifi settings in system\etc are not correct.
It happened to me.
Disconnect at every 5-10 min.
And i discover that on the LOS based rom i m not sure about AOSP because i m not using the notification are delayed.
Around 10 min after the message are send if the phone are in deep sleep around 10 min the notification delay a loot.
I found a fix but really dissapoint about custom rom development.
I don like the Miui stock rom but whit thats bugs .
So we need a pure stable aosp rom witch some config change and PA theme engine so i don need to download every week new build and start fixing the bugs after that.
I read in one plus forum the some users have the same problem but after flashing frimware the problem was solve.
So the next question is which frimware package we have to flash to fix the wifi dissconect.
I tried AndroidOne and wifi is stable. I would like to understand where to intervene to solve the problem with other lineage constructions 14.1 and 15. Maybe I have to change the Kernel? do I need to intervene in the Build.prop file?