Related
I had flashed latest RR official
Before I had flashed cm13 radios n b20 unlock zip clean wiped everything
After that flashed RR still 2% battery bug
Not only in RR every up-to-date cm13 ROM flashing getting that 2% bug continuously
Can someone point out me what the exact error am doing???
Thanks
Sent from my One Plus 3 using XDA-Developers mobile app ?
same here ,krexus with cm13 radio zip
Mukthar. said:
same here ,krexus with cm13 radio zip
Click to expand...
Click to collapse
May b it's updated kernel issue
As I told updated one only
Same ROM old builds are fine
N RR unofficial and other unofficial aokp temasek also fine
May b that problem due to kernel
Changing kernel solved my issue...
Sent from my One Plus 3 using XDA-Developers mobile app ?
abid52 said:
May b it's updated kernel issue
As I told updated one only
Same ROM old builds are fine
N RR unofficial and other unofficial aokp temasek also fine
May b that problem due to kernel
Changing kernel solved my issue...
Sent from my One Plus 3 using XDA-Developers mobile app ?
Click to expand...
Click to collapse
Which kernel did you flash, that helped to solve problem?
Post the link please
RC_Vinchenzo said:
Which kernel did you flash, that helped to solve problem?
Post the link please
Click to expand...
Click to collapse
I recommend you flash the stock mi rom , then install TWRP then radio blobs and then install the ** LASTEST **rom that you need *i know this is what you did* , but since you are getting the error , please consider it .
RC_Vinchenzo said:
Which kernel did you flash, that helped to solve problem?
Post the link please
Click to expand...
Click to collapse
Not kernel
Flashed whole old ROM back solved 2% bug
Unofficial RR has no such bug
N official RR till 20th build
N all others bfor July builds were fine to use without this bug
Sent from my One Plus 3 using XDA-Developers mobile app ?
Manoj Rocker said:
I recommend you flash the stock mi rom , then install TWRP then radio blobs and then install the ** LASTEST **rom that you need *i know this is what you did* , but since you are getting the error , please consider it .
Click to expand...
Click to collapse
I've done that for several times. Didn't work.
I've noticed that there is no battery status, when booted in recovery mode. All available screenshots of TWRP (coffee, Alca) HAVE battery status.
Only TWRP 3.0.2.M4 by TheStrix shows battery, but it's stuck at 50%
Probably the root of evil is kernel, which doesn't support some modifications of battery controller.
RC_Vinchenzo said:
I've done that for several times. Didn't work.
I've noticed that there is no battery status, when booted in recovery mode. All available screenshots of TWRP (coffee, Alca) HAVE battery status.
Only TWRP 3.0.2.M4 by TheStrix shows battery, but it's stuck at 50%
Probably the root of evil is kernel, which doesn't support some modifications of battery controller.
Click to expand...
Click to collapse
Flash stock using MiFlash tool via edl mode doing so will over right the kernel to stock . then flash any lastest rom , and dont use the rom pakage that you used earlier . There are devices with different FP scanner and camera , modules but the OS/ROM/EMMC are the same for all the devices .
RC_Vinchenzo said:
I've done that for several times. Didn't work.
I've noticed that there is no battery status, when booted in recovery mode. All available screenshots of TWRP (coffee, Alca) HAVE battery status.
Only TWRP 3.0.2.M4 by TheStrix shows battery, but it's stuck at 50%
Probably the root of evil is kernel, which doesn't support some modifications of battery controller.
Click to expand...
Click to collapse
Newly updated July build kernels have that bug
Noticed by flashing 2 to 3 ROMs of July 2nd build
Kernel of a bit old build can also flashble in latest one that can probably solve this issue
But WiFi doesn't work
Damn...
Sent from my One Plus 3 using XDA-Developers mobile app ?
Manoj Rocker said:
Flash stock using MiFlash tool via edl mode doing so will over right the kernel to stock . then flash any lastest rom , and dont use the rom pakage that you used earlier . There are devices with different FP scanner and camera , modules but the OS/ROM/EMMC are the same for all the devices .
Click to expand...
Click to collapse
Sorry, I haven't mentioned: my problem of battery stuck at -2% or 50% is actual only on custom ROMs
Stock MIUI 7.3.7 Global Stable works fine!
RC_Vinchenzo said:
Sorry, I haven't mentioned: my problem of battery stuck at -2% or 50% is actual only on custom ROMs
Stock MIUI 7.3.7 Global Stable works fine!
Click to expand...
Click to collapse
How many roms have you tried ?. If you have tried only on RR unofficial try changing the rom itself.
Manoj Rocker said:
How many roms have you tried ?. If you have tried only on RR unofficial try changing the rom itself.
Click to expand...
Click to collapse
Several CM builds of different authors, RR official, AOSP 6.0.1, AOSP 5.1.1
RC_Vinchenzo said:
Several CM builds of different authors, RR official, AOSP 6.0.1, AOSP 5.1.1
Click to expand...
Click to collapse
yeah , with cm based roms , did flash the radio files too(there are 2 , you should flash ,that is necessary) ?, if you did i dont know what happend to your device .
Manoj Rocker said:
yeah , with cm based roms , did flash the radio files too(there are 2 , you should flash ,that is necessary) ?, if you did i dont know what happend to your device .
Click to expand...
Click to collapse
Sure, I did. If you mean CM13-Radios.zip
Simple test: does your recovery show battery stats?
Mine doesn't.
RC_Vinchenzo said:
Sure, I did. If you mean CM13-Radios.zip
Simple test: does your recovery show battery stats?
Mine doesn't.
Click to expand...
Click to collapse
Which recovery u r using???
Sent from my One Plus 3 using XDA-Developers mobile app ?
abid52 said:
Which recovery u r using???
Sent from my One Plus 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
All available builds of TWRP 3.0 by alca, cofface, theStrix, Mr-r00t
RC_Vinchenzo said:
All available builds of TWRP 3.0 by alca, cofface, theStrix, Mr-r00t
Click to expand...
Click to collapse
Use alka 3.0 then flash first 8th build of unofficial RR without blobs n additional files
Just simply flash n see
Do clean flash compulsory
Sent from my One Plus 3 using XDA-Developers mobile app ?
@RC_Vinchenzo , Yeah , that's the only thing left . download twrp alka , clean wipe , flash radio blobs , flash the ROM , then gapps .
Thx!
Found old build of RR Unofficial 5.6.9 (08.06.2016) works almost properly on my device! No battery bug , but fingerprint is unavailable
Something happened to CM core, so it stopped supporting some hardware modifications.
RC_Vinchenzo said:
Thx!
Found old build of RR Unofficial 5.6.9 (08.06.2016) works almost properly on my device! No battery bug , but fingerprint is unavailable
Something happened to CM core, so it stopped supporting some hardware modifications.
Click to expand...
Click to collapse
Good to see ur bug gone [emoji12] [emoji23]
U can flash radio blobs n b20 unlock zip bfor clean wipe n flash
Let's try
U will b fixed those coming issue too
Sent from my One Plus 3 using XDA-Developers mobile app ?
Thanks to modpunk, Serenitys, and other developers, i builded cm14.1 for kor alpha and it works fine.
Great! Can you share it?
wow, it's stable for daily use?
I was looking for your thread since yesterday. any bugs? excited to try this out
---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------
josepmaria said:
Great! Can you share it?
Click to expand...
Click to collapse
you can find it on his androidfilehost profile, not sure if i'm allowed to share the link.
Did you face any bugs and does it support fingerprint unlock?
How did you do it?
Edit:
I'm going to try the latest build from androfilehost.
I hope the mic (in calling) is working and other basic functions. I have a G850k by the way.
Hello,
I Flashed this using TWRP 2.8.1.1
And flashed the Gapps for 7.1
But after restart system my phone shows samsung logo
And after that blank screen, then after some min my system started but i dont have anything on my screen while my back and recent buttons are flashing and i feel my phone fibrate please what to do did i bricked my phone?
Came from official 4.4.4 Rom
SM-G850F
kevkev0320 said:
Hello,
I Flashed this using TWRP 2.8.1.1
And flashed the Gapps for 7.1
But after restart system my phone shows samsung logo
And after that blank screen, then after some min my system started but i dont have anything on my screen while my back and recent buttons are flashing and i feel my phone fibrate please what to do did i bricked my phone?
Came from official 4.4.4 Rom
SM-G850F
Click to expand...
Click to collapse
Its a soft brick. Your model is not a korean variant he says that it is working for korean variants. For G850S/K/L only. Try to go to TWRP and flash another rom. Or use odin.
click.here said:
Its a soft brick. Your model is not a korean variant he says that it is working for korean variants. For G850S/K/L only. Try to go to TWRP and flash another rom. Or use odin.
Click to expand...
Click to collapse
okay thank you very much,
Downloaded and flashed CM.13, my phone is up and running again,
Sorry for the off-topic related post
kevkev0320 said:
Hello,
I Flashed this using TWRP 2.8.1.1
And flashed the Gapps for 7.1
But after restart system my phone shows samsung logo
And after that blank screen, then after some min my system started but i dont have anything on my screen while my back and recent buttons are flashing and i feel my phone fibrate please what to do did i bricked my phone?
Came from official 4.4.4 Rom
SM-G850F
Click to expand...
Click to collapse
kevkev0320 said:
okay thank you very much,
Downloaded and flashed CM.13, my phone is up and running again,
Sorry for the off-topic related post
Click to expand...
Click to collapse
I dont know which CM13 you are refering to but you can extract that from the official ROM if I'm not mistaken
click.here said:
I dont know which CM13 you are refering to but you can extract that from the official ROM if I'm not mistaken
Click to expand...
Click to collapse
It was an unofficial build, but my system is now running,
many thanks <3
I can confirm that CM14.1 works with my Korean variant G850k but the mic problem still persist from previous CM13 . I hope this could be fix and more power. You should create a new thread when everything seems to be functional so that we could also inform others and have they're feedbacks
kevkev0320 said:
Hello,
I Flashed this using TWRP 2.8.1.1
And flashed the Gapps for 7.1
But after restart system my phone shows samsung logo
And after that blank screen, then after some min my system started but i dont have anything on my screen while my back and recent buttons are flashing and i feel my phone fibrate please what to do did i bricked my phone?
Came from official 4.4.4 Rom
SM-G850F
Click to expand...
Click to collapse
you need to use TWRP 3.0.2, I had the same issue as you on 2.8. eventually got it booting. (im on SM-G850F)
but I had a "validity service has stopped" popup screen that just kept popping up. I reflashed, still same issue. I'm not the only one with this issue. I'm guessing it's because of the fingeprint sensor support that has been added. don't quote me on this tho
ArisRafaelli said:
you need to use TWRP 3.0.2, I had the same issue as you on 2.8. eventually got it booting. (im on SM-G850F)
but I had a "validity service has stopped" popup screen that just kept popping up. I reflashed, still same issue. I'm not the only one with this issue. I'm guessing it's because of the fingeprint sensor support that has been added. don't quote me on this tho
Click to expand...
Click to collapse
do u understand dutch? can i send u a PM?
kevkev0320 said:
do u understand dutch? can i send u a PM?
Click to expand...
Click to collapse
yes I do, go ahead.
ArisRafaelli said:
you need to use TWRP 3.0.2, I had the same issue as you on 2.8. eventually got it booting. (im on SM-G850F)
but I had a "validity service has stopped" popup screen that just kept popping up. I reflashed, still same issue. I'm not the only one with this issue. I'm guessing it's because of the fingeprint sensor support that has been added. don't quote me on this tho
Click to expand...
Click to collapse
The alternative work around for that is to keep closing the popup screen til its gone or freeze it. Does the mic (in calling) or the voice recorder works for you?
click.here said:
The alternative work around for that is to keep closing the popup screen til its gone or freeze it. Does the mic (in calling) or the voice recorder works for you?
Click to expand...
Click to collapse
i tried, it won't go away. wasn't able to test anything tbh.
ArisRafaelli said:
i tried, it won't go away. wasn't able to test anything tbh.
Click to expand...
Click to collapse
You have to close it quickly and press next until you reach the home screen. After that just enable developer settings and it will go away.
@hdh980910 we wait for your answers.
Thanks i will go to flash cm14.1 on my alpha
Thanks i will go to flash cm14.1 on my alpha
many people in develoid cafe say kt alpha has connect out phenomenon. can you fix it?
I see more and more people had problem like this, touch screen on new phones is not working at all in custom ROMs and also in OrangeFox. Nobody changed display nor play with phone internals.
DarthJabba9 said:
Do I have an ebbg display? You will already know if you do, because your touchscreen will not work on most custom ROMs, and will not have worked on any earlier version of OrangeFox. So, if you have been using any earlier release of OrangeFox, then you clearly do not have an ebbg display. You can check by installing the "Device HW Info" app from the Play Store. When you run it, check the "LCM" on the start page. If you see "ebbg" appearing anywhere in that, then you do have an ebbg display.
Click to expand...
Click to collapse
Phones manufactured 05/2018 and later can face this issue.
Manufactured date is located at sticker at the back of the phone box.
Despcription:
Seems that kernel is responsible to make touch to work. Its not easy to make ebbg display touch work in custom GPL kernels, only ROM which use prebuilt kernel that comes with the device tree is working right now.
Big thanks to DarthJabba9 who is fix that in OrangeFox recovery. https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
What is working:
Recovery:
- OrangeFox R7
- TWRP official
- RedWolf Unofficial
ROMs:
- Xiaomi roms global stable ROM 7.1, global dev beta 8.1,
- Dirty unicorns 7.1 posted here: https://forum.xda-developers.com/red...-plus-t3812630
- AOSP Extended 5.7
What is not working:
- OrangeFox 5.1, r6
- KERNEL: Dark ages Segundo, LH kernel
- Pixel experience https://forum.xda-developers.com/redmi-note-5/development/rom-pixel-experience-t3797696
- Liquid remix https://forum.xda-developers.com/redmi-note-5/development/rom-liquid-remix-t3809286
- AOSP Extended 5.6
---account closed
It's not a "feature". Xiaomi probably used a different screen for later batches of Vince. What month was your phone manufactured?
what works:
moved to main post
sigma392 said:
It's not a "feature". Xiaomi probably used a different screen for later batches of Vince. What month was your phone manufactured?
Click to expand...
Click to collapse
where I can find this, in CIT?
I found this App called Device info HW on the Appstore. When i open it on my redmi 5 plus it says: Touchscreen -> synaptics_dsx_i2c
But I'm not sure if thats what youre looking for ...
Btw my phone has the same problem too
Mine has same info in aida64 and device info hw and touch works in every rom, kernel and recovery.
jes0411 said:
Mine has same info in aida64 and device info hw and touch works in every rom, kernel and recovery.
Click to expand...
Click to collapse
can you please share what rom,kernel and recovery you using right now?
mik.y said:
can you please share what rom,kernel and recovery you using right now?
Click to expand...
Click to collapse
Recovery: orangefox r6
Rom: omnirom official
Kernel: default from the rom
I used previously resurrection remix and then havoc and used all kernel (DA, LH and Universe)
Also used TWRP and Red Wolf.
Edit:
Sorry, I missed that ebbg thing in aida64 screenshot.
I have all the same except ebbg.
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
mubeenshahid said:
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
Click to expand...
Click to collapse
sorry,you dont. we are talking about not working touch screen all the time,not just sometimes.
jes0411 said:
Recovery: orangefox r6
Rom: omnirom official
Kernel: default from the rom
I used previously resurrection remix and then havoc and used all kernel (DA, LH and Universe)
Also used TWRP and Red Wolf.
Edit:
Sorry, I missed that ebbg thing in aida64 screenshot.
I have all the same except ebbg.
Click to expand...
Click to collapse
can you please post your aida screenshot? thanks
mik.y said:
can you please post your aida screenshot? thanks
Click to expand...
Click to collapse
Here it is.
mik.y said:
where I can find this, in CIT?
Click to expand...
Click to collapse
It's located at sticker at the back of the phone and at the Box. Interesting to note that we share the same sensor yet your touch doesn't work. Mine was Manufactured last 12/2017
mubeenshahid said:
I am having same issue. Touchscreen sometimes hang during regular use. Its annoying. DotOs
Click to expand...
Click to collapse
For this, flash the baseband at the main post. If it fails, your FP sensor may be dirty. I had instances where a dirty FP causes some intermittent touch issues.
I just saw, and mine was manufactured on 06/2018
But anyways i got some progress ....
I tried installing various custom roms this afternoon, after some flashing i got one to work. It's the AOSP Extended mod for Vince. I think it worked cause the rom has a miui (Oreo 8.1) based bootloader, kernel or both ... I'm not sure what it is. The rom looks good (It's similar to the Pixel Experience). I had some bootloop problems at the beginning, but after i updated the bootloader it works fine.
Qu4k3_92 said:
I just saw, and mine was manufactured on 06/2018
But anyways i got some progress ....
I tried installing various custom roms this afternoon, after some flashing i got one to work. It's the AOSP Extended mod for Vince. I think it worked cause the rom has a miui (Oreo 8.1) based bootloader, kernel or both ... I'm not sure what it is. The rom looks good (It's similar to the Pixel Experience). I had some bootloop problems at the beginning, but after i updated the bootloader it works fine.
Click to expand...
Click to collapse
there are 4 versions, which one?
mik.y said:
there are 4 versions, which one?
Click to expand...
Click to collapse
This one, the v5.7: https://www.google.com/amp/s/forum....pment/rom-aospextended-rom-v4-6-t3752135/amp/
mik.y said:
I see more and more people had problem like this, touch screen on new phones is not working at all in custom ROMs and also in OrangeFox. Nobody changed display nor play with phone insides. Maybe some new "feature" introduced by Xaiomi? I would like to somebody help me investigate this.
Plase notice that this display is "ebbg".
what is working:
Recovery:
- TWRP official 3.2.2.0
- RedWolf Unofficial
ROMs:
Xiaomi roms global stable ROM 7.1, global dev beta 8.1,
Dirty unicorns 7.1 posted here: https://forum.xda-developers.com/red...-plus-t3812630
what is not working:
- TWRP official 3.2.2.0 + OrangeFox 5.1, r6
- Pixel experience https://forum.xda-developers.com/redmi-note-5/development/rom-pixel-experience-t3797696
Click to expand...
Click to collapse
I see the driver is not loaded in kernel
Will be fixed on next release
blacksuan19 said:
I see the driver is not loaded in kernel
Will be fixed on next release
Click to expand...
Click to collapse
in what kernell/rom?
blacksuan19 said:
I see the driver is not loaded in kernel
Will be fixed on next release
Click to expand...
Click to collapse
I saw there is a new release.... Did they fix it?
(I would try it by myself but i dont have enough connection a the moment)
I found oreo and pie roms for our ultra on androidfilehost but after flashing I am not able to get the touch working. I think its a recovery issue, but the twrp-3.1.1 uploaded by zawzaw doesn't mount my system read/write, so no luck. Can anyone test the roms please? Also is there newer version of twrp available for our device?
Here is the link
https://androidfilehost.com/?w=search&s=togari
I want to test it but mw z ultra cant get a single twrp working, is there a way to flash it without twrp?
billyliem said:
I want to test it but mw z ultra cant get a single twrp working, is there a way to flash it without twrp?
Click to expand...
Click to collapse
Have you tried 3.0.2-0? That has been working for me on my C6833.
Yes, it is not working for me
Hello does the rom working? I cant install it because i cant have TWRP working in my device
Hi,everyone! I'm builder this rom. I build a new ROM from source. Check it
I don't know what works and what doesn't.
The work of the touchscreen is depends on the kernel. Check
Rom tester
Hello
First of all thank you for your work, we really appreciate it, i have a suggestion, please make a Telegram group so we can join and test the rom and tell you the bugs and issues, thank you again
Which Kernel to use with this Rom?
raschad said:
Hi,everyone! I'm builder this rom. I build a new ROM from source. Check it
I don't know what works and what doesn't.
The work of the touchscreen is depends on the kernel. Check
Click to expand...
Click to collapse
the custom rom of the android pie will be continued ?, and I think you could do a post of your roms I think it would give a good revival in this forum and release the source code of the roms and the kernel
raschad said:
Hi,everyone! I'm builder this rom. I build a new ROM from source. Check it
I don't know what works and what doesn't.
The work of the touchscreen is depends on the kernel. Check
Click to expand...
Click to collapse
I tried the last build of your oreo version, after i had done this solution to fix the touch issue https://forum.xda-developers.com/xp...t/fix-fix-touch-roms-6-0-6-0-7-x-8-x-t3884411
I run the rom for half a day, and the touch worked fine using the solution above, i only had problem with the sim card, the rom doens't recognize it so i can't have mobile network and make calls, and i lost my imei too, another problem that i ran to was that the camera didn't worked too.
beside that i didn't have any problem, but i came back to RR 5.8.3 since i couldn't use mobile network in this rom.
I would love to at least have a custom Android rom oreo stable and functional but by the way it will take a little longer for this to happen
...
I'd tried your touch fix but got no luck on either Pie or Oreo ROM. The touch screen got no work even in the recovery.
Jaime albino said:
I tried the last build of your oreo version, after i had done this solution to fix the touch issue https://forum.xda-developers.com/xp...t/fix-fix-touch-roms-6-0-6-0-7-x-8-x-t3884411
I run the rom for half a day, and the touch worked fine using the solution above, i only had problem with the sim card, the rom doens't recognize it so i can't have mobile network and make calls, and i lost my imei too, another problem that i ran to was that the camera didn't worked too.
beside that i didn't have any problem, but i came back to RR 5.8.3 since i couldn't use mobile network in this rom.
Click to expand...
Click to collapse
phhuang said:
I'd tried your touch fix but got no luck on either Pie or Oreo ROM. The touch screen got no work even in the recovery.
Click to expand...
Click to collapse
Same Here , flashed the fix , and no touchscreen response after boot
phhuang said:
I'd tried your touch fix but got no luck on either Pie or Oreo ROM. The touch screen got no
work even in the recovery.
Click to expand...
Click to collapse
pvillasuso said:
Same Here , flashed the fix , and no touchscreen response after boot
Click to expand...
Click to collapse
i wasn't using those roms anymore because in the oreo version the camera doesn't work and mobile network too, the
9.0 version didn't work either, it's always in bootloop, but i flashed the oreo version again and the touch fix
using philz recovery and twrp and the touch worked like a charm as i said you just need to wait a few seconds, the
purpose of this fix is to fix the touch problem within the rom and not in the recovery, if your recovery doesn't
have touch is not something that this fix or i can do sorry. But i can guarantee that this fix works in this oreo
version because i tested it myself after a clean flash, please try again and tell me if it worked for you.
Hi, everyone! I'm compilled new ROM
Android 9.0 - AOSP Extended 6.1 for Togari
I dont know how working touchscreen.
Check it
DOWNLOAD
install error 7 in TWRP?
raschad said:
Hi, everyone! I'm compilled new ROM
Android 9.0 - AOSP Extended 6.1 for Togari
I dont know how working touchscreen.
Check it
DOWNLOAD
Click to expand...
Click to collapse
phhuang said:
install error 7 in TWRP?
Click to expand...
Click to collapse
Yep same to me.
Malle355 said:
Yep same to me.
Click to expand...
Click to collapse
Open on PC through WinRar and edit
META-INF/com/google/android/update-script
And delete the top 3 lines (getprop...)
raschad said:
Open on PC through WinRar and edit
META-INF/com/google/android/update-script
And delete the top 3 lines (getprop...)
Click to expand...
Click to collapse
Its booting but touch not working. Tried to flash the touch_fix.zip but not working.
someone needs to compile a new twrp recovery for us, xperia z ultra orphans
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)?