ChanServ changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
<M0xCAFEBABE[m]> uh, the touchscreen is still processing touches when the display is turned off...
<M0xCAFEBABE[m]> is that normal on mainline or can be made to turn off automatically when the display is off?
<barni2000[m]> they are not connected so it is normal
<barni2000[m]> but downstream you also have double tap feature
<M0xCAFEBABE[m]> barni2000[m]: the touchscreen enters low power mode for that
<barni2000[m]> mainline driver is much simpler than dowsntream so not all feature implemented
<barni2000[m]> have you enabled this CONFIG_CFI_PERMISSIVE ?
<barni2000[m]> i wonder which driver caused the issues
<M0xCAFEBABE[m]> not yet
<barni2000[m]> how long is compiling the twrp from scratch or los recovery?
<M0xCAFEBABE[m]> on my Intel Xeon E5 v2, first build takes 30+ minutes, second build takes 10+ minutes
<M0xCAFEBABE[m]> why do you want to ask that tho?
<barni2000[m]> i am thinking about to build twrp
<barni2000[m]> but i only have 6300u which is not very powerfull
<barni2000[m]> and i have a PC with ryzen but xeon is more powerfull from that
<M0xCAFEBABE[m]> TWRP is the past thing, nowadays basically nobody in android community cares about TWRP anymore
<barni2000[m]> what is replacing it?
<M0xCAFEBABE[m]> LineageOS based recovery
<barni2000[m]> but LoS recovery is featureless
<barni2000[m]> i am annoyed from key control
<M0xCAFEBABE[m]> but TWRP recovery doesn't support modern devices/things well
<barni2000[m]> i cannot put display in sleep
<barni2000[m]> I was using Orangefox anyway, but it have very small community
<M0xCAFEBABE[m]> all those GUI recoveries are based on TWRP
<barni2000[m]> LoS recovery also gui recovery
<M0xCAFEBABE[m]> * all those fancy GUI recoveries
<barni2000[m]> another issue not all device have LoS recovery
<M0xCAFEBABE[m]> lol... LOS recovery comes with LOS ROM, and is much easier to bringup than TWRP, it's more like not everyone are uploading LOS recovery yet
<M0xCAFEBABE[m]> 99% custom ROMs uses LOS recovery as base too
<M0xCAFEBABE[m]> * 99% custom ROMs cherry-picks all the LOS recovery stuff
<M0xCAFEBABE[m]> * and 99% custom ROMs cherry-picks all the LOS recovery stuff
<barni2000[m]> i am also annoyed by random builds, i more like "offical" builds
<barni2000[m]> LoS recovery would be fine if it was separate project from LoS
<barni2000[m]> so you can be find and support them without a LoS rom\
<barni2000[m]> * so you can be find and support them without a LoS rom
<f_> barni2000[m]: LOS recovery is fine
<barni2000[m]> as i said my issue the build and i cannot disable the display only time out sleep it
<barni2000[m]> another topic, it seems i cannot bring up msm8937 atm :(, somehow dpm is not creating the interface like on 8917 i don't know how to fix it yet, so in next release i will enable modem on riva, rolex and maybe on ugglite
<barni2000[m]> maybe i should cherry-pick ipa and enable modem on santoni and ugg
Watyhn[m] has joined #msm8937-mainline