Thank you. So if r35 is good, then will that be our last release for awhile until Google decides to push something out? Not complaining, just curious.
Probably not. We'll see
The battery life on 34 is really unparalleled. Even the latent drain overnight is something as well. Only problem that I had (notice tense there) was redraws. All fine until I got one and then after that they were every time I backed out off an app. I wiped cache and a simple reboot here and there, but once I got one it was a cascading effect until I either rebooted or cleared cache.
Sucks because 34 is really a fluid kernel (aside from the auto-brightness which I don't use and BT which I use very sparingly). No UV at all and just using stock kernel settings. Had to go back to 32 for the time being. Even tried to put Apex in memory and still redraws. Sadpanda.jpg
Redraws on the browser or on other apps?
@franciscofranco, any thoughts on what might be causing the bluetooth le disconnects? (primarily seen with those who have Pebble smart watches)
Yes I have a couple ideas!
@franciscofranco New release of android? that can take quite a while or what? or are u not sharing something?(A)
I don't know anything, I'm just guessing.
Yeah, I just got my Pebble and this issue has caused my to stop using the kernel for the time being. I get zero disconnects using the stock Slim kernel and Faux, so it seems that it points to something in this kernel.
@franciscofranco, I know you've said in the past that you don't touch the BT stuff for your kernel, so I have to imagine it's something else inadvertently causing the issue. Is it possible one of the CAF power management merges is putting the BT in a low power state or something? Maybe it's not compatible with BT LE and therefore it doesn't think there's enough activity to keep the connection fully active? But then as soon as it drops, the watch speaks up again and BT is powered back up? The disconnects seem to happen during longer periods of inactivity, which is what's leading me to my rambling hypothesis. I'll load up r34 again and see if I can get a log of the disconnect. Tzfardaya, you should too.
I have an idea why that is happening.
@franciscofranco On the latest FKU beta, I can't seem to set the download path. I've tried long pressing everything I can think of, and nothing seems to be sticking. Can anyone else confirm this?
In the update I got a couple hours ago,
App Settings -> ZIPs download path -> (short click at flashing bar.... File Manager!!)
Yay! Even though app says use long press.
edit: ack! spoke too soon. Can't get it to pick a directory.
edit again: Pick a file in the directory. Long press on the name that comes up to delete the name of the file. The directory remains. Note that the directory is used correctly, but doesn't show up next time.
Yes that feature is broken for now. I started to work on it then I didn't finish it on time for the beta. I'll get it finished and release production v11.4 soon!
Great! However do you think to look into the audio problems? (glitches or headphones that stop working), your kernel is really great....i know that i can reboot when i have the audio problem but it really bothers me when i need to listen music only for 10 minutes or so!
I was in a 6 hour (3h each way) train trip this weekend. Through the trip I listened to music with my Apple earbuds (I like them for travelling, way better than to use my AKG K550) and while my connection was always being lost, migrating to and from Wi-Fi I haven't got a SINGLE audio problem and I tested with all audio volumes. I simply cannot reproduce! Not saying that there isn't an issue, but I've tried everything and I can't reproduce!
Latest beta fku version, anyone else finding their min CPU speed has increased on its own for no reason? Iv caught min at 1036mhz twice now.
Sent from my Nexus 5 using Tapatalk
?
I have no clue, I use my app all the time and I never saw such a thing happening. Can you reproduce it again and give me a heads up on how to reproduce?
@franciscofranco - Hey Franco. You've probably heard this a dozen times already, but would you please implement frandom support in your r35 release? Virtually every newest AOSP rom nightly has switched to frandom, and it has pretty much rendered your r34 kernel null, void, and useless.>< It's causing many people to jump ship and flash Elemental .32 like hot cakes. = (
sent from the back of a prancing, magical unicorn.
You do know that those random number generators are almost not used at all? There was a post sometime from a Google employee showing that barely nothing on Android uses /dev/random and all the derivates.
Bring me conclusive tests that using frandom gives you any real world benefits (which I doubt you'll find) and I'll consider it. Besides frandom is not upstreamed, which also raises my eyebrow.
I'm using this kernel for a week by now, and I'm absolutely satisfied with the battery life.
On the other hand, my phone is overheating , when I play some bigger games like Asphalt 8, it even reboots itself sometimes.
Can I fix this issue somehow?
I've played games like Beach Buggy (pretty demanding) for hours and my device never gets hotter than 75C. You can decrease the thermal threshold to 65ºC or something. I cannot reproduce and I've ran my devices against Stability Tests all the time to test the throttle code.
My phone is reboots while transfering large file via Airdroid (4.5GB file) on 5GHz band.3 times rebooted.Can someone reproduce the test if this is a kernel problem?
Logs?
For those of you with sound clipping or distortion the following was posted over at SlimKat with some secondary verified results:
"Install Viper4Android, open app then install its driver at Super Quality, reboot. Then delete DSPManager.apk [... snip ....] May need to reboot again but Viper should be your default EQ now.
I can confirm there is no more audio clipping at high volumes. DSP Manager just does not work well with the Nexus 5. Viper is much more tweakable anyway."
Goodluck.
Good info!
Hey
@franciscofranco.
You may be unaware of the com.android.phone force close issue some people are seeing recently... (see the exchange quoted below or
here in the Vanir thread)
Thanks for the awesome work as always!
-omni
Thanks, I'll add the jar to the bootclasspath.
Slight OT, is this happening to anyone else?
Sent from my Nexus 5 using xda app-developers app
Whoa! Never seen that before even when my apps are all broken on my local tests.