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
<hacker420[m]> <barni2000[m]> "i think c0 and c1 are switched" <- kek
<hacker420[m]> <barni2000[m]> "i have updated my branch with..." <- where
<barni2000[m]> maybe 14016 also can be used instead of 14010 becasue it is divisible but better to modify the pll driver on longterm
<hacker420[m]> yeah grabbed just the dtsi change and it seems to work fine
<hacker420[m]> <barni2000[m]> "strange thing is why msm8940 was..." <- could be because it accepted these cluster frequencies?
<barni2000[m]> yes maybe 8940 is over clockable
<hacker420[m]> or rather still within defined limits
<hacker420[m]> the phone still does some weird shit where it shuts off
<hacker420[m]> except I need to pull the battery to get it back up
<hacker420[m]> doesn't seem to wake up on battery nor starts up by plugging in power
<hacker420[m]> except at this point I have no idea if it's the kernel or some hw damage
<hacker420[m]> seems to happen only on battery
<hacker420[m]> hacker420[m]: or maybe battery degradation?
<hacker420[m]> or it wants the charging/battery driver
<hacker420[m]> <barni2000[m]> "supertuxkart works with 38-50..." <- well here even with all it's still like 20 fps
<barni2000[m]> switch adreno firmware
<hacker420[m]> to the pmos one?
<barni2000[m]> yes
<barni2000[m]> and it depends from the track
<hacker420[m]> barni2000[m]: which one did you test on?
<barni2000[m]> and you use preset 1
<barni2000[m]> i don't know the track names but if you choose the frist one that will be fine
<hacker420[m]> barni2000[m]: yes
<barni2000[m]> wait cedric has 1080p display
<hacker420[m]> yeah
<barni2000[m]> land has 720p
<barni2000[m]> so 20 fps is fine
<hacker420[m]> ahh
<hacker420[m]> but it still doesn't explain the weird shutdowns
<barni2000[m]> you still have shutdowns?
<hacker420[m]> yeah
<hacker420[m]> I have no idea why
<hacker420[m]> would need to test more under a charger
<hacker420[m]> maybe it's battery related
<barni2000[m]> try to recharge your batter from recovery
<barni2000[m]> s/batter/battery/
<hacker420[m]> should be charged already
<hacker420[m]> unless the drain is so bug
<hacker420[m]> *big
<barni2000[m]> if you catch some logs that could help a lot
<hacker420[m]> dmesg?
<hacker420[m]> Oh yeah
<hacker420[m]> it is battery
<hacker420[m]> guess the drain is just so big
<barni2000[m]> and maybe your battery is old
<hacker420[m]> well yes
<hacker420[m]> but it didn't have as much drain on androidf
<barni2000[m]> android has cpr