Re: [KERNEL][GPL] franco.Kernel - r7
Does this kernel support OTG?
Sent from my Nexus 10 using Tapatalk HD
Does this kernel support OTG?
Sent from my Nexus 10 using Tapatalk HD
Does this kernel support OTG?
Sent from my Nexus 10 using Tapatalk HD
I am on the paranoid android ROM with the Franco kernel. I can't seem to play purchased movies from the play store. I keep getting an error that it can fetch the license. When I restore the stock kernel that came with the ROM there is no problem. Has anyone else experienced this?
Hulu plus is does not work either with this kernel either. Stock kernel works fine.
Sent from my Nexus 10 using Tapatalk HD
Flashed this kernel 12 H ago, and had two freezes so far, were i had to hard reboot. Will see if i can get kmesg next time.
Weird!! Can you guys decrease Ondemand sampling rate to 10000 and see if it helps? It might be also the up_threshold. Decrease it to 90 or 85. Report back please
were not from the kernel and were instead due to a deadlock in the rest of Android... I think when a reset is triggered by watchdog you can find the information in /data/anr/traces.txt and from that you might be able to determine what caused the core Android Framework to stop responding."Last reset was system watchdog timer reset (RST_STAT=0x100000)"
Hi Franco,
I've been running R7 for a few days (since it came out) and have got several random BSOD while the tablet was in idle (sometimes with wifi on, sometimes in airplane mode).
Running factory JB 4.2.2 with SuperSU 1.09 and as of today, SuperSu 1.10 with TWRP 2.4.1.0 recovery.
BSODs happened with both versions of SuperSU as well.
Franco settings are: ondemand governor, min CPU frequency: 200, max 17000, IO Scheduler: deadline, westwood TCP congestion avoidance
attached is my kmsg
Cheers and keep up the great work!
I'm sure Franco will correct me if I am wrong, but I was under the belief that any watchdog resets:
were not from the kernel and were instead due to a deadlock in the rest of Android... I think when a reset is triggered by watchdog you can find the information in /data/anr/traces.txt and from that you might be able to determine what caused the core Android Framework to stop responding.
Geoff