Discussion Thread for Builds by @Woivod for Land
Download Link:
Resurrection Remix - Nougat
Liquid Remix - Oreo
AEX - Oreo
Credits to the work of this ROM completely goes to @Woivod , I, in no way, take any credit or responsibility to any of His works...
I think Woivod took a break from RR and started working on AEX for now.
killeradi said:
I think Woivod took a break from RR and started working on AEX for now.
Click to expand...
Click to collapse
How is AEX different from RR... I have never tried it...
bharathulaganathan said:
How is AEX different from RR... I have never tried it...
Click to expand...
Click to collapse
I don't remember much as I used it only for half hour or so. Due to random reboot and crashes. Which I still don't know why happened. Anyway his aex build is smooth just like his RR builds, I didn't checked all the customisation but it was lil less than RR.. Performance wise I will say both are quite same.. But as I didn't used much so can't say more. ? Sorry.
killeradi said:
I don't remember much as I used it only for half hour or so. Due to random reboot and crashes. Which I still don't know why happened. Anyway his aex build is smooth just like his RR builds, I didn't checked all the customisation but it was lil less than RR.. Performance wise I will say both are quite same.. But as I didn't used much so can't say more. ? Sorry.
Click to expand...
Click to collapse
Its Ok Bro... It seems only we both are having a conversation here and others are talking about it in the official thread ?
bharathulaganathan said:
Its Ok Bro... It seems only we both are having a conversation here and others are talking about it in the official thread
Click to expand...
Click to collapse
I installed October 8th Beacon build (RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon) by Woivod.
But the kernel still remained as the lineageos kernel. As the rom was not pre-rooted, I installed SuperSu.
Now can someone tell me the steps to flash Beacon kernel on this rom? Is there any special steps to be taken such as flashing the stock boot.img from the RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon.zip file prior to flashing the kernel zip file?
stealthmaster said:
I installed October 8th Beacon build (RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon) by Woivod.
But the kernel still remained as the lineageos kernel. As the rom was not pre-rooted, I installed SuperSu.
Now can someone tell me the steps to flash Beacon kernel on this rom? Is there any special steps to be taken such as flashing the stock boot.img from the RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon.zip file prior to flashing the kernel zip file?
Click to expand...
Click to collapse
Nope, just download the kernel zip you want to flash and use twrp to flash it. And reboot.. viola you're done ?
---------- Post added at 02:49 PM ---------- Previous post was at 02:46 PM ----------
bharathulaganathan said:
Its Ok Bro... It seems only we both are having a conversation here and others are talking about it in the official thread ?
Click to expand...
Click to collapse
Yeah it looks like ? Maybe after a while people will notice this. ?
killeradi said:
Nope, just download the kernel zip you want to flash and use twrp to flash it. And reboot.. viola you're done
Click to expand...
Click to collapse
Thank you so much for your quick reply. Going to do the same
stealthmaster said:
Thank you so much for your quick reply. Going to do the same
Click to expand...
Click to collapse
You're welcome.. enjoy.. ?
I clean flash RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon.zip
But unable to boot. My phone only shows mi logo only and then switched off.
Redmi 3s
andriana936 said:
I clean flash RR-N-v5.8.5-20171008-land-Unofficial_mod_kernel_beacon.zip
But unable to boot. My phone only shows mi logo only and then switched off.
Redmi 3s
Click to expand...
Click to collapse
Do a clean flash again (turn off Your mobile and press both volume buttons and the power button to enter TWRP)... If it doesn't work try re-downloading the ROM... Even then if it doesn't work try flashing Stock MIUI and then clean flash the ROM...
How is your battery on Woivod's build? I am currently on RR-N-v5.8.5-20171008 and I have a problem with battery drain. On build RR-N-v5.8.5-20171006 was the same. The problem is that my phone doesn't go to Deep Sleep state. It is always awake, even with screen off.
The wakelock that cause such a behaviour is a Kernel Wakelock called msm_otg. I have checked that with BetterBatteryStats.
I have tried 3 different kernels: a default one v.3.18.72, customs Beacon 3.0 stable and Beacon 3.5 beta. Behaviour is always the same.
I have a screensaver and pocket detection disabled. The only way to start entering Deep Sleep state is to reboot the phone after it is charged. But it is a pain in the ...... always to remember it, have time for it and always keep an eye if phone gets Deep Sleep or not.
Doman said:
How is your battery on Woivod's build? I am currently on RR-N-v5.8.5-20171008 and I have a problem with battery drain. On build RR-N-v5.8.5-20171006 was the same. The problem is that my phone doesn't go to Deep Sleep state. It is always awake, even with screen off.
The wakelock that cause such a behaviour is a Kernel Wakelock called msm_otg. I have checked that with BetterBatteryStats.
I have tried 3 different kernels: a default one v.3.18.72, customs Beacon 3.0 stable and Beacon 3.5 beta. Behaviour is always the same.
I have a screensaver and pocket detection disabled. The only way to start entering Deep Sleep state is to reboot the phone after it is charged. But it is a pain in the ...... always to remember it, have time for it and always keep an eye if phone gets Deep Sleep or not.
Click to expand...
Click to collapse
Same issue here... Initially in both 6th and 8th build it was fine but deep doze didn't work later... May be You can try the doze app in Play Store... But battery drain in 8th with Beacon is unbearable...
I clean flashed October 8th build (with the new kernel 3.18.72) today. I feel that phone is a lot smoother now. LiveDisplay and miui camera is working fine (I will not go back to MIUI anymore ).
Previously, I had dirty flashed his Oct 8th build over Oct 5th build.
Once again thanks to Woivod for his awesome work on Redmi 3s.
Regarding the battery issue and not falling into Deep Sleep state described in post #12... I have a feeling, that installing Kernel Auditor from Google Play fixed the problem. I need some more testing to be sure, but anyone having similar issues please give it a try as well.
Doman said:
Regarding the battery issue and not falling into Deep Sleep state described in post #12... I have a feeling, that installing Kernel Auditor from Google Play fixed the problem. I need some more testing to be sure, but anyone having similar issues please give it a try as well.
Click to expand...
Click to collapse
I have this issue. I'm testing XPerience-11.1.2-20171012-NIGHTLY-land now
Doman said:
Regarding the battery issue and not falling into Deep Sleep state described in post #12... I have a feeling, that installing Kernel Auditor from Google Play fixed the problem. I need some more testing to be sure, but anyone having similar issues please give it a try as well.
Click to expand...
Click to collapse
I didnt even have kernel auditor but still had deep sleep issue...
I felt 6th Build to be the Best... Does clean flashing 8th build with Lineage Kernel feel smooth??
Im currently on Wadjm81's 16th Build... Its a lot laggy...
After the overnight charging to 100% I find that Kernel Auditor is not a solution. Still no Deep Sleep state.
I've flashed PERXEPTED-N-v3.3_20170925 kernel today. Will see what happens tomorrow morning.
@bharathulaganathan
I feel both 6th and 8th to be very smooth, don't see any difference. I even did dirt flash 8th over to 6th build and have no issues... apart from this Deep Sleep But it is not related I believe.
Related
This thread can be used for tracking the progress of CM14 for the Mt2?
Note:
https://plus.google.com/u/0/photos/photo/109932426055289104206/6329128826640065154?icm=false
Link is not opening
plus.google.com/109932426055289104206
Nougat for Ascend Mate 2 MTL203
So this post caught my eye... Is someone working on Android 7.0 for the Ascend Mate 2 or is it already out there?
SHM, a dev who brought us TWRP and a few 6.0 ROMs, is working on 7.0. Understandably, he doesn't like people asking for ETA's so he'd prefer us not to bug him.
Also, since CM officially supports our phone, won't we be getting an official CM14 as well?
shm quit development on this but released the sources
https://bitbucket.org/S-H-M/android_device_huawei_mt2
https://bitbucket.org/S-H-M/android_kernel_huawei_msm8928
Sadly
http://forum.xda-developers.com/showpost.php?p=69194744&postcount=234
ScoobSTi said:
SHM, a dev who brought us TWRP and a few 6.0 ROMs, is working on 7.0. Understandably, he doesn't like people asking for ETA's so he'd prefer us not to bug him.
Also, since CM officially supports our phone, won't we be getting an official CM14 as well?
Click to expand...
Click to collapse
i think that would be after someone submits a working build.
Unofficial CM14.1
bgcngm said:
https://android.cmphys.com/cyanogenmod-mt2/
Click to expand...
Click to collapse
MT2-User said:
Unofficial CM14.1
Click to expand...
Click to collapse
Stock Camera works. Both front and rear ones. Gallery app works.
DT2W also works!
Clean flash plus Open GApps nano package as shown.
Battery life: with profiles settings as Performance and Tasker running in the foreground.
MT2-User said:
Battery life: with profiles settings as Performance and Tasker running in the foreground.
Click to expand...
Click to collapse
Good to see the great community behind this phone is still developing... Thanks guys... May you have a Happy MT2 New Year...
MT2-User said:
Battery life: with profiles settings as Performance and Tasker running in the foreground.
Click to expand...
Click to collapse
@MT2-User what's your feel for this beta rom is it worth a try, how easy is it to go back to your cm13 back, and this new version of twrp how does it work???
Thanks for any info you can share...
nate5711 said:
@MT2-User what's your feel for this beta rom is it worth a try, how easy is it to go back to your cm13 back, and this new version of twrp how does it work???
Thanks for any info you can share...
Click to expand...
Click to collapse
@nate5711: I think this CM14.1 runs more smooth than CM13 (official). It hasn't crashed yet; previously CM13 rebooted occasionally. The battery life is very nice also: 9-10 hours SOT, similar to CM13.
I have been using TWRP by Matt (this CM14.1 Developer) for a while, so I didn't see any problem with it (the previous version is 3.0.M5-0 released on July 19; https://android.cmphys.com/twrp-mt2/). The only thing is TimeService which led to inaccurate time in TWRP, but I always named Nandroid backup myself which is much shorter while with more information. It has been fixed as Matt stated:good:
I did make a Nandroid backup of CM13 using TWRP-3.0.M5.0 and I am sure there is no problem to switch between this CM14.1 and CM13 without loss of data. I tried both clean and dirty flash of CM14.1 (over CM13), and currently I've been running the dirty-flashed one flawlessly. I tried switch between CM14.1 and CM13 with TWRP and there's no problem at all.
Sure, as I mentioned earlier, LiveDisplay night mode doesn't work. There's no CMTE either. Otherwise everything is good on my end.
Thanks to Matt for his wonderful job! :good::good::good:
BTW, Matt has his CM13-Dec 26 nightly available to us also and he said the Camera (CM13) has been fixed. TBH, I haven't tried his CM13-20161226 yet since I am very satisfied with his CM14.1-20161225.
Dirty flashed runs fine also had to re flash gapps to get it to fully boot but other then the missing theme engine it seems way smoother then the last good build of cm 13 great work matt and thanks for keeping this phone alive
Sent from my Ascend Mate 2 using Tapatalk
hopkins31 said:
Dirty flashed runs fine also had to re flash gapps to get it to fully boot but other then the missing theme engine it seems way smoother then the last good build of cm 13 great work matt and thanks for keeping this phone alive
Click to expand...
Click to collapse
Yes, arm 7.1 GApps required even for dirty flash over CM13.
Thanks for the helpful info, dl the rom and I'm very much enjoying it..
Thank you for providing the latest build. I have installed it and seems to be working fine. Need to use it for a few days to cycle the battery to know how good is the backup.
Thank You so much for the update so far is very smooth. Is anyone else having the camera randomly popping up during a phone call? I have tried to download gapps again and reflashed still having the issue. Am i missing something in the settings?
divhandyman said:
Thank You so much for the update so far is very smooth. Is anyone else having the camera randomly popping up during a phone call? I have tried to download gapps again and reflashed still having the issue. Am i missing something in the settings?
Click to expand...
Click to collapse
Disable the tap to wake setting under display will stop the camera popping up.
Hi guys,
I'm having a super slow gps fix no matter what i try
1. Flash latest or stable firmware
2. Edit gps.conf
The slow is like i takes almost 5 mins to get a 3D Fix or locked position.
But i notice this happen since nougat build. Miui official on marshmallow work extremely fast to get a fix. But whenever i use custom rom like NOS Oreo or Nougat, LOS Oreo or Nougat and also MIUI Nougat (Epicrom) Latest 9.x still have this issues
Im on Kate, official unlocked bootloader. I wonder is there any method i can try?
Any reply will be thanks:highfive:
Regards,
Darren Lim
Here attached with the Gps test. Everything in view but does get a 3D lock (No Fix)
darrenlimch said:
Hi guys,
I'm having a super slow gps fix no matter what i try
1. Flash latest or stable firmware
2. Edit gps.conf
The slow is like i takes almost 5 mins to get a 3D Fix or locked position.
But i notice this happen since nougat build. Miui official on marshmallow work extremely fast to get a fix. But whenever i use custom rom like NOS Oreo or Nougat, LOS Oreo or Nougat and also MIUI Nougat (Epicrom) Latest 9.x still have this issues
Im on Kate, official unlocked bootloader. I wonder is there any method i can try?
Any reply will be thanks:highfive:
Regards,
Darren Lim
Click to expand...
Click to collapse
Same issue here
---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------
Did you fix it
tom jp said:
Same issue here
---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------
Did you fix it
Click to expand...
Click to collapse
Yes for now. Yesterday just discovered a new method. In testing stage will release once fully tested
darrenlimch said:
Yes for now. Yesterday just discovered a new method. In testing stage will release once fully tested
Click to expand...
Click to collapse
How?
Can you tell me, I will test it too
Kinda have the same issue, so please post the fix if you find it.
tom jp said:
How?
Can you tell me, I will test it too
Click to expand...
Click to collapse
Ethelwald said:
Kinda have the same issue, so please post the fix if you find it.
Click to expand...
Click to collapse
NOS have a new update on (24th) , and the chg log mentioned there is something chg related to gps, u guys tested? Gonna release the fix soon. The reason i haven't release is because it might cost lost to imei. I try to find a method to prevent that. And need more testing. So plesde be patient ya
Just flashed lates NOS build and GPS is in fact much better, but probably need more testing.
asakurato said:
Just flashed lates NOS build and GPS is in fact much better, but probably need more testing.
Click to expand...
Click to collapse
Which build (date)
tom jp said:
Which build (date)
Click to expand...
Click to collapse
January 24 build, but About phone for some reason says January 19
Kinda fixed
darrenlimch said:
Hi guys,
I'm having a super slow gps fix no matter what i try
1. Flash latest or stable firmware
2. Edit gps.conf
The slow is like i takes almost 5 mins to get a 3D Fix or locked position.
But i notice this happen since nougat build. Miui official on marshmallow work extremely fast to get a fix. But whenever i use custom rom like NOS Oreo or Nougat, LOS Oreo or Nougat and also MIUI Nougat (Epicrom) Latest 9.x still have this issues
Im on Kate, official unlocked bootloader. I wonder is there any method i can try?
Any reply will be thanks:highfive:
Regards,
Darren Lim
Click to expand...
Click to collapse
My GPS started working properly,
I did try flashing firmwares but didn't help. I flashed full stock rom(global Dev 8.1.18) and then flashed cosmic os and now having no issues with GPS.(I also use GPS status and toolbox).
I haven't tried nos
tom jp said:
My GPS started working properly,
I did try flashing firmwares but didn't help. I flashed full stock rom(global Dev 8.1.18) and then flashed cosmic os and now having no issues with GPS.(I also use GPS status and toolbox).
I haven't tried nos
Click to expand...
Click to collapse
Yes i did know this method works., But if u dirty flash an update again ur gps will broke. So u need redo again everything from beginning. It's no a good method tho but it work ?
Dug up the Github commit, here's the dev's quote:
https://github.com/nitrogen-project...mmit/5a9e84251696bb48e8fe184784226604efdf6f6c
[haggertk]:
* During bring-up of O, GPS was exhibiting different behavior from
N -- an appropriate number of satellites would immediately lock,
but a fix would not resolve for 30-90 seconds. Digging up this
change from the L-era allows GPS to resolve a fix in a nominal
amount of time.
Click to expand...
Click to collapse
Hi guys,
Any progress on this issue? Anyone tried latest NOS maybe? I switched back from NOS Oreo to NOS Nougat because of this...
Ok guys,
Please take note this will make u lost your IMEI somehow mine is missing but i did have a backup so i can restore it anytime. Without IMEI it doesn't affect me at all.
This method is weird so, backup before you do it. Not responsible for anything happen
1) boot into FASTBOOT
2) connect to computer use ADB and key in this
fastboot flash modem NON-HLOS.BIN
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
The nonhlos.bin can be found inside a official miui rom and flashing the non hlos is not necessary.
Test your gps after that it should work. Please report back
I fixed gps problem by installing F-Droid,than GPSfix extension,selected my country and voila...When u're in house etc. or when its clody weather its hard for GPS for 3D fix. Btw Im on Cardinal latest Oreo 8.1 build and 8.1.11 miui firmware.
IrishBoy94 said:
I fixed gps problem by installing F-Droid,than GPSfix extension,selected my country and voila...When u're in house etc. or when its clody weather its hard for GPS for 3D fix. Btw Im on Cardinal latest Oreo 8.1 build and 8.1.11 miui firmware.
Click to expand...
Click to collapse
or even better just download "GPS fix" from google play and press start fix and let it for 10 mins.
jimakos98 said:
or even better just download "GPS fix" from google play and press start fix and let it for 10 mins.
Click to expand...
Click to collapse
This method doesn't work. And it only work for one days. And ppl like me have no time to wait for it to fix before moving
Some ppl lucky enough that they dont even have any bugs. I actually suspect its hardware compatibility issues. Blame xiaomi for that maybe? Hahaha
simple, use Device only as agps given problem often (depend on the agps mood?).
I also removed miui built in compass as it shown compass accuracy high to low from gps test app (suspect this causing the gps locking issue too).
now waze locking every time within few seconds.
irontech said:
simple, use Device only as agps given problem often (depend on the agps mood?).
I also removed miui built in compass as it shown compass accuracy high to low from gps test app (suspect this causing the gps locking issue too).
now waze locking every time within few seconds.
Click to expand...
Click to collapse
I assume you are talking bout miui in nougat. So you mean after u disable compass and use device only mode the gps jssues is fixed?
having the same problem with all pie roms. messenger and whatsapp keeps getting closed in the background, also doesn't give me notifications. I made them "not optimized" in battery optimization but it didn't help.
Same problem here. Running AEX 6.1. with DA kernel.
DragonTerror said:
Same problem here. Running AEX 6.1. with DA kernel.
Click to expand...
Click to collapse
yeah I am on AEX too, but its a common problem through out all roms for me.
@DragonTerror do you use Titanium Backup?
q.sadid said:
@DragonTerror do you use Titanium Backup?
Click to expand...
Click to collapse
No. Never used it...
q.sadid said:
yeah I am on AEX too, but its a common problem through out all roms for me.
Click to expand...
Click to collapse
Try dark ages kernal
Fixed same problem for me on oreo roms
bot88 said:
Try dark ages kernal
Fixed same problem for me on oreo roms
Click to expand...
Click to collapse
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
q.sadid said:
DA gives me screen ghost/burn in problems. okay I will try DA again and see if it works. thanks for the reply.
Click to expand...
Click to collapse
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
bot88 said:
As far as i know ghosting problem is related to older firmware, try to update that as well
Cheers
Click to expand...
Click to collapse
Tried DA kernel, still the same problem ?
qazi_sadid said:
Tried DA kernel, still the same problem
Click to expand...
Click to collapse
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
3. Maybe a hardware related problem
4. Restoration of apps using titanium backup
5. Wrong Wake lock blocker settings which prevent phone form waking up on critical wakelock such as gmscore wake locks, which will definitely results in delayed notifications (tested by myself)
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
DragonTerror said:
Here's my situation:
1. I placed latest global firmware I could get my hands on. I'm not sure was it beta or stable.
2. This is a GApps issue?
3. I'm pretty sure it's not since I came from Havoc 2.0 just 2 weeks ago. Before AEX 6.1 it worked normally.
4. I used Migrate to restore apps.
5. I don't use any wake lock blocker whatsoever
Click to expand...
Click to collapse
Try latest gapps, or different packages, (mini or micro)
Maybe that can help
:fingers-crossed:
bot88 said:
Then it maybe caused by several issues,
1. Old firmware
2. Malfunctioning core gapps
.............................
Maybe gms dose for magisk can also be responsible.
Click to expand...
Click to collapse
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
q.sadid said:
tried everything. tried your solution. tried this Post too : https://forum.xda-developers.com/redmi-note-5/development/rom-havocos-t3807696/post78675837
BUT nothing is working. either its the dosing system they are using in the rom is responsible for this, or the hardware of my phone. I am currrently one AEX 6.2 with DA kernel
Click to expand...
Click to collapse
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
DragonTerror said:
I'm pretty sure it's a ROM problem. Tried running without DA kernel and literally nothing changed, except my battery life which worsened a bit. Hoping for a solution or I'm going back to Havoc OS
Click to expand...
Click to collapse
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
q.sadid said:
I will go back to MIUI 10 tomorrow and see if the problem remains, it will make sure its a pie rom problem.
Click to expand...
Click to collapse
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
bot88 said:
try havoc os 2.1
latest change log suggest addition of "xiaomi doze" maybe that will help.
Click to expand...
Click to collapse
Will do tommorow if I find time for it
I will post my results.
I tried every rom pie rom but couldn't get any of them to work
I installed pixel experience (not caf) rom today on my poco F1 and the look and feel is great..but when I'm using it the touch isnt working sometimes it stucks. Only fix is to lock and unlock phone again ..then after couple minutes the issue will appear again need help
I have the same issue
If anyone knows how to fix this please help me!! Much appreciated
What version of the vendor did you flash?
It needs to be higher than 9.2.15
riseofsand said:
What version of the vendor did you flash?
It needs to be higher than 9.2.15
Click to expand...
Click to collapse
beryllium-9.4.1-9.0
I am using pixel experience CAF version and vendor 9.4.1... there is no touch issues .. try CAF version and clean flash it
This happens for me too whenever I have TWRP recovery installed, with any ROM (both stock *and* custom ones). I only get this behaviour when entering my SIM cards PIN code or when booting TWRP (I can't swipe so I must turn the screen off, wait for about 5 seconds, then turn it in again)
On PE aosp u can flash miui kernel and fix it! Idk about caf.
What touch panel do you have? check out my thread https://forum.xda-developers.com/poco-f1/help/damn-screen-freezes-t3912069
vamshikailasa said:
I am using pixel experience CAF version and vendor 9.4.1... there is no touch issues .. try CAF version and clean flash it
Click to expand...
Click to collapse
Did u use aosp version? What is the most stable ? Most battery efficient? More smooth? Can u tell me answers for each questions? Thanks alot
Mooatreides said:
On PE aosp u can flash miui kernel and fix it! Idk about caf.
What touch panel do you have? check out my thread https://forum.xda-developers.com/poco-f1/help/damn-screen-freezes-t3912069
Click to expand...
Click to collapse
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
Is it correct?
u wont face any touch issues if u use 9.3.28 kernel, only stock kernel has no issues with touch, idk if pe will boot with it or not... try it yourself, bt i am sure that 9.3.28 has the best touch drivers.
gigishan said:
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
Is it correct?
Click to expand...
Click to collapse
Well try man and see, go for aosp
U can just take the boot.img from miui also only. On PE
FINALLY!!!!
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
ITS WORKING NOW - YET I'LL LET KNOW IF THE ISSUE STILL EXISTS SOMEHOW THANK YOU EVERYONE WHO HELPED ME
gigishan said:
FINALLY!!!!
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
ITS WORKING NOW - YET I'LL LET KNOW IF THE ISSUE STILL EXISTS SOMEHOW THANK YOU EVERYONE WHO HELPED ME
Click to expand...
Click to collapse
MAZAL TOV man! enjoy the good life with no freezes lol. Its like having a tooth hurt forever and you forgot what normal was, then all of a sudden no freezing screen pain hahah!
Mooatreides said:
MAZAL TOV man! enjoy the good life with no freezes lol. Its like having a tooth hurt forever and you forgot what normal was, then all of a sudden no freezing screen pain hahah!
Click to expand...
Click to collapse
Hahaha yeah man thank u so much for the help
gigishan said:
FINALLY!!!!
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
ITS WORKING NOW - YET I'LL LET KNOW IF THE ISSUE STILL EXISTS SOMEHOW THANK YOU EVERYONE WHO HELPED ME
Click to expand...
Click to collapse
I already have PE aosp installed with 9.5.8-9.0 vendor-firmware on my Poco F1. Is it alright to flash just the MIUI kernel (kernel-beryllium_global_9.4.8-ak2.zip) and nothing else?
Or do I need to repeat the whole flashing firmware / installing PE OS thing?
Mariorio said:
I already have PE aosp installed with 9.5.8-9.0 vendor-firmware on my Poco F1. Is it alright to flash just the MIUI kernel (kernel-beryllium_global_9.4.8-ak2.zip) and nothing else?
Or do I need to repeat the whole flashing firmware / installing PE OS thing?
Click to expand...
Click to collapse
Just flash the kernal alone you will be fine
Will just leave it here. Hope someone finds it useful.
I fixed the screen freeze issue using the vendor-firmware and kernel fix on the links below:
Files:
beryllium-9.4.12-9.0-vendor-firmware.zip
kernel-beryllium_global_9.4.12-ak2.zip​
Links here.
Also, I am on Lineage OS, latest build.
Thank you for this thread!
gigishan said:
FINALLY!!!!
I flashed these :
beryllium-9.4.8-9.0-vendor-firmware.zip
kernal-beryllium_global_9.4.8-ak2.zip
ITS WORKING NOW - YET I'LL LET KNOW IF THE ISSUE STILL EXISTS SOMEHOW THANK YOU EVERYONE WHO HELPED ME
Click to expand...
Click to collapse
Same problem here since couple of weeks. Flashed these using lastest build of Nitrogen OS and everything is working fine so far! Thank you
Mooatreides said:
MAZAL TOV man! enjoy the good life with no freezes lol. Its like having a tooth hurt forever and you forgot what normal was, then all of a sudden no freezing screen pain hahah!
Click to expand...
Click to collapse
Edu Lezcano said:
Same problem here since couple of weeks. Flashed these using lastest build of Nitrogen OS and everything is working fine so far! Thank you
Click to expand...
Click to collapse
Will these vendor and kernel combo work for the latest Pixel Experience update(05082019)?
My screen seems to have a less significant problem. It only freezes for 1 or 2 seconds, even when I was holding my finger on the screen. It interrupts my swiping and sometimes doesn't recognize my taps. Any help will be appreciated.
Specific details of my phone: (vince)
Pixel Experience-21090507-1513
Pie
Kernel: 4.9.173-Perf (not sure if this is the stock kernel)
TWRP 3.2.3
I changed my rom each month. The problem started to happen when I switched from bootleggers to aosp extended. Should I roll back to miui?
Thanks again!
I have the same problem
Started with RR Rom , Havoc , AOSP Extended, Revolution Rom and going back to MIUI with the hope of any updates but the same problem and the battery it wasnt going very well .
Im using Pixel Experience but the problem its not fixed.
I tried with turning on some features on develop mode watch some videos on youtube but nothing , using even touch calibration but this is worse.
Still waiting for the problem fix
Digital Boy said:
My screen seems to have a less significant problem. It only freezes for 1 or 2 seconds, even when I was holding my finger on the screen. It interrupts my swiping and sometimes doesn't recognize my taps. Any help will be appreciated.
Specific details of my phone: (vince)
Pixel Experience-21090507-1513
Pie
Kernel: 4.9.173-Perf (not sure if this is the stock kernel)
TWRP 3.2.3
I changed my rom each month. The problem started to happen when I switched from bootleggers to aosp extended. Should I roll back to miui?
Thanks again!
Click to expand...
Click to collapse
Test a 3.18 kernel rom
Kernal problem, if problem persist after changing kernal try to change to genom kernel, it has better display support.
bot88 said:
Kernal problem, if problem persist after changing kernal try to change to genom kernel, it has better display support.
Click to expand...
Click to collapse
Sd card bug not being recognized has been fixed? Would you please send the kernel link?
Sorry for bad english.
NaassomDourado said:
Sd card bug not being recognized has been fixed? Would you please send the kernel link?
Sorry for bad english.
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-5/development/kernel-genom-kernel-t3840934
joke19 said:
Test a 3.18 kernel rom
Click to expand...
Click to collapse
I tried this. This doesn't completely resolve the problem but I recognized a good improvement in my phone. So I guess the idea is testing different kernels until my phone got fixed?
Btw thanks for helping :fingers-crossed: