yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] iamikon:
Disabling fsync will dramatically speed it up. But if you encounter a crash or random reboot be prepared to lose data
[Nexus 10 Original Android Development] espionage724:
No idea on benchmarks, but when loading osu!droid for the first time (it caches all songs on storage, which I guess involves a lot of reads and writes), my Nexus 10 beat my Nexus 4 by over 5 minutes. Same kernel and ROM, fsync disabled on both.
[Nexus 10 Original Android Development] iamikon:
Ah the amazing difference between benchmarks and real world performance :)
[Nexus 10 Original Android Development] stonebear:
I find ondemand to be a bit jerky but interactive to be very smooth and responsive. I only used r10 for a short time though so can't compare properly - but r11 interactive is great for me.
[Nexus 10 Original Android Development] Hereisphilly:
I would hazard a guess that caching songs would be a sequential workload, something that this device does excel at
[Nexus 10 Original Android Development] fkrone:
Got my Nexus 10. I’m really happy with it but the colours seem very strange to me compared to my Nexus 4 with an own colour profile. Would be nice to see this possibility one day on this device :) It feels really smooth so keep going :)
[Nexus 10 Original Android Development] x3nophobia:
im sorry but does anyone experience lagging temporary? i experienced this while playing candy crush
[Nexus 10 Original Android Development] fkrone:
Got reboot on changing governor:

http://pastebin.com/4ADmksas
[Nexus 10 Original Android Development] EnIXmA:
Stick tennis and candy crush are lagging a lot on r11. Other than that the kernel is snappy, and the battery life is insane. I m on my first charge cycle, 3 days of standby and 8 hours of screen time with 26% battery still remaining. Heavy usage too, lots of songs, watched movies on flash using the stock browser and played games on it for hours. Would post screenshots tomorrow. :)
[Nexus 10 Original Android Development] skyklg:
this kernel really brought awesomeness... but is it me or my nexus is getting very hot over the right after an hour or so of usage
[Nexus 10 Original Android Development] epunk:
same here...[exaggeration] I could nearly fry an egg or make some pop corn out of it!!! [/end exaggeration] :silly:
[Nexus 10 Original Android Development] skyklg:
So it's kernel related? Or rom related?
[Nexus 10 Original Android Development] zoomy942:
More so than stock or cm kernel?
[Nexus 10 Original Android Development] skyklg:
Gonna try with trinity and then report back.
[Nexus 10 Original Android Development] EniGmA1987:
The tablet will get hot when you use it, especially for gaming, that is how electronics work. This kernel has modified thermal throttling to make it work better since the stock kernel has such terrible performance so most likely your tablet is running a bit hotter. However its temperature is still well within acceptable ranges.
[Nexus 10 Original Android Development] kaivalya97:
I have installed Paranoid Android 3.50. When I try to flash the r11 .zip file in TWRP, it gives a "failed" error. I re downloaded and tried once again but same error. Previously, I was using r8 on CM10.1 and had no issues... Can anyone help me?
[Nexus 10 Original Android Development] EniGmA1987:
Failed errors normally mean a bad download when I get them. Could be a problem with your hard drive, or the transfer to your tablet. Probably not a hosting issue since many people have downloaded it and it works fine.
[Nexus 10 Original Android Development] ChosSimbaOne:
I just had a random reboot. The tablet just froze and rebooted. I got last_kmesg. The reboot occurred while i was playing Carmageddon. Is it kernel related?

last_kmesg: https://docs.google.com/file/d/0B82yV-NzjPN4bnNITmRkaGVlV1U/edit?usp=sharing

ROM is stock
[Nexus 10 Original Android Development] hanspampel:
I think yes. Never had those reboots with other kernels in the last time. The reboots and SODs came first today. Im using r11 since few days. Didnt change a ROM or something else. Got no log, sorry.
[Nexus 10 Original Android Development] ThugosaurusRex:
What ROM are you using?
[Nexus 10 Original Android Development] 1337sause:
Holy mother of hell...how did you get that screen-on time?
[Nexus 10 Original Android Development] addicted1900:
I got even better screen-on-time when reading pdfs and underclocked to 1,2 GHz. There's no magic at all reaching 9h ;)
[Nexus 10 Original Android Development] franciscofranco:
r12:

* Cherry-picked a bunch of commits from CAF, Google and Linux Kernel which improve:

- Better battery life coming from improved handling of some critical but common in the Kernel freezer (patches from Colin Cross, Google engineer)

- Some improvements in the Workqueue layer (from CAF)

- Better calculation of dirty pages on the Kernel Virtual Memory Manager (from Linux Kernel)

- Enabled NFS by user request
[Nexus 10 Original Android Development] zoomy942:
Those changes are effective no matter the governor?
[Nexus 10 Original Android Development] franciscofranco:
Yes.
[Nexus 10 Original Android Development] zoomy942:
Awesome. Thank you. I'm using the defaults. Nothing changed so ondemand and deadline. Works great.

---------- Post added at 04:27 AM ---------- Previous post was at 04:25 AM ----------

Try r12. Ondemand is very smooth now.
[Nexus 10 Original Android Development] patsmike:
I'm not sure why but r12 feels much smoother than r11. Maybe just placebo though
[Nexus 10 Original Android Development] ThugosaurusRex:
I'm feeling this as well
[Nexus 10 Original Android Development] franciscofranco:
Its probably the improvements on the Virtual Memory layer which improves how the Kernel calculates the dirty pages (only 3 or 4 commits) and the Workqueue layer improvements that I picked from CAF.
[Nexus 10 Original Android Development] situman:
Not to exaggerate but the difference between r12 and r11 is night and day. On Interactive/Deadline. No lag at all. All the minor microstutters are gone.
[Nexus 10 Original Android Development] G-Bus:
Downloading thru the Franco App is extremely slow right now...
[Nexus 10 Original Android Development] x3nophobia:
same here :silly:
[Nexus 10 Original Android Development] stonebear:
You are right. :)

I am now gonna try interactive.
[Nexus 10 Original Android Development] paratox:
hey franco, thanks for the new release! you are the man! :)

would it be possible to include cifs.co, nls_utf8.ko and md4.co? this would be great! :)
[Nexus 10 Original Android Development] franciscofranco:
CIFS nope. What is the rest?
[Nexus 10 Original Android Development] rrand:
I've been trying to get Franco.Kernel to work with bluetooth sound for months now. I don't know what's wrong. I'm running the latest version of ParanoidAndroid. I haven't seen anyone else with this exact issue but me. Whenever I play sound through Bluetooth it skips pretty bad. Like 10 times per song. If I go back to stock kernel the sound works fine. Very smooth. This is not just when I'm using a music player. If I'm listening to YouTube in my browser it happens as well. Unlike another person in this thread, it happens with the screen on or off. It doesn't matter.

Has anyone heard of this before? I've even done a factory reset. Any other solution to this?

Thanks in advance.

Solution found:

The sound only skips when using a Bluetooth audio device in ParanoidAndroid (and using franco.Kernel) while having rotation locked. (Locked on the tile menu, not in the launcher settings.) I always have rotation locked, thus I have always experienced this issue.
[Nexus 10 Original Android Development] Kolyk:
NFS does not work:rolleyes:
[Nexus 10 Original Android Development] Ok_Kaleidoscope5109:
He had fsync disabled on both the N4 and N10. And plus I don't think caching songs on storage is a good indication of random writes.

The difference between fsync on and off on the N10 is like 0.7 MB/sec versus like 70 MB/sec or something with Fsync off. I realize that you told me of the risks of turning off fsync, but my question is more a basic level question. If all other tablets do so well in random writes, is it because they also have fsync off?

I hate benchmarks too, but 0.7 MB/sec random writes is pretty darn slow. I do have 21GB of data on my Nexus 10, and I'm wondering if that's causing me some slowdowns. It shouldn't be that bad though. I'm maintaining the "keep 20% free" rule on SSDs. I'm just trying to figure out why my device feels EXTREMELY sluggish sometimes.
[Nexus 10 Original Android Development] paratox:
why no cifs? :(

the rest are needed for mounting CIFS and utf-8 charset.
[Nexus 10 Original Android Development] Hereisphilly:
I agree, interactive is perfect!

Tbh though, so is ondemand, I can't decide between the two, they are both so smooth!
[Nexus 10 Original Android Development] stonebear:
Yea they are both great now. :)
[Nexus 10 Original Android Development] 1337sause:
I can testify to the validity of that statement :)

I could notice a slight jitter on the multitask button of the navigation bar while switching between apps before r12. Now, I can't notice a thing. It's smooth as butter!

Great work! This is exactly why I purchased a Nexus!
[Nexus 10 Original Android Development] rrand:
I can't believe I've just stumbled across the special circumstances of this bug by mere chance. Now who should I report this to?

The sound only skips when using a Bluetooth audio device in ParanoidAndroid (and using franco.Kernel) while having rotation locked. (Locked on the tile menu, not in the launcher settings.) I always have rotation locked, thus I have always experienced this issue. Strange.
[Nexus 10 Original Android Development] 1337sause:
I can verify the Bluetooth skipping on stock ROM with Franco kernel. Just tried Bluetooth playback with my jambox.
[Nexus 10 Original Android Development] espionage724:
Interactive gives me pretty erratic FPS (I've seen dips to 30 FPS at times) in Beats, Advanced Rhythm Game, worse than Ondemand and Performance :/
[Nexus 10 Original Android Development] Hereisphilly:
Ah I haven't gamed on it recently, I'm on about ui performance
[Nexus 10 Original Android Development] IRKONIK:
My Nexus 10 on ParanoidAndroid 3.56 dies while the screen is off, meaning that it can't wake up again.

Had the same issue with my S3, it's because the max CPU speed while screen off is too low.

Please fix this :)

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Nexus 10 Original Android Development] rrand:
You're right. I just remembered this issue went on even before I changed ROMs.
[Nexus 10 Original Android Development] alan sh:
Me too. I didn't know why. I guess we could use a tool to increase the min CPU.

Alan
[Nexus 10 Original Android Development] Endless7:
Nice:good:
[Nexus 10 Original Android Development] notegalaxy:
Thermal throttle stuff is working great. Mine still gets the odd lag on need for speed. Would appreciate the ability to under volt. Also a request for pegasusq or other hot plugging ones would be awesome. Bought your app to support. Thanks for the great work so far.

Edit - just checked my CPU speed during the game. I had about 2 minutes at 1700 before thermal throttle then 25 mins at 1000. My device is useless!
[Nexus 10 Original Android Development] SpecRek9:
So good to finally see you work your magic on this device, this is the third android Dev I own and the third one running your kernel as well :)
[Nexus 10 Original Android Development] espionage724:
You can make a flashable zip yourself I believe (I recall someone requesting this on the N7 thread a while back and getting a similar response). Could also use the app too to flash.
[Nexus 10 Original Android Development] franciscofranco:
Why would we want useless governors here? Just because they have cool names doesnt mean they are useful.

Undervolting is not an option for now.
[Nexus 10 Original Android Development] franciscofranco:
Just go to fastboot and flash it like it says in the OP.
[Nexus 10 Original Android Development] duarian:
So hot plugging governors really are useless? I've read mixed reviews and in the Iogical sense...cutting one fire off when its not needed seems like a good idea. However that's on paper, I'm not sure of results in the real world.
[Nexus 10 Original Android Development] espionage724:
It had barely any affect on battery life (based on what others say anyway; didn't try it personally), and on KTManta, initially it caused some users issues with audio playback even. I remember it also being somewhat of an issue on the Nexus 7. Not having hotplug is also one less thing the device needs to "think" about :p
[Nexus 10 Original Android Development] kampfbestie:
I know what to do but im many times not at home and don/t have a laptop to flash

I have a Problem tested timescapes 2560 with MX player and have much stottering any als with The Problem
[Nexus 10 Original Android Development] freshlysqueezed:
https://play.google.com/store/apps/details?id=com.into.stability&hl=en

Just adding more info:

When running the classic stability test on the r2 kernel, after about a minute or two, I noticed that is still throttles pretty easily, just as before with the stock kernel. On the stock kernel it will jump between 1700 to 1400. On the r2 kernel, it will jump between 1700 to 1000.

Thanks for developing on the n10, appreciate all the hard work. :thumbup:
[Nexus 10 Original Android Development] jm6001:
Bought your app! Hopefully you will have a break through with the display calibration... You will end up making a lot of money that way :fingers-crossed::highfive::laugh::victory:
[Nexus 10 Original Android Development] jhankg:
Classic Stability Test still brings on throttling very quickly using r2.
[Nexus 10 Original Android Development] franciscofranco:
Hotplug in a dual core is useless. It just "sounds cool"... I don't do cool stuff, I do stuff that works.

I can't control how fast the device gets hot. I think the problem about the so called "lag" when throttling is that the thermal driver shoots IRQs which stands for interrupt request. So it keeps requesting for interrupts all the time until the temperature goes below the threshold. I don't know how useful IRQs are in that context, and I'm not sure they are even needed. I've been thinking and I think I have a solution workable after I leave work today.
[Nexus 10 Original Android Development] franciscofranco:
Like I said above I can't control how fast the device gets, we're all bound to physical hardware.
[Nexus 10 Original Android Development] freshlysqueezed:
Most of us don't believe that our CPU's are getting that hot within 1 minute and that either the temp is calculated by an algorithm or is being throttled for battery efficiency as described by the anandtech article.
[Nexus 10 Original Android Development] notegalaxy:
My impression was that hot plugging was useful even on dual core - obviously may be wrong. And also that the processor architecture seemed to respond badly to interactive-again may be wrong, just what I read from other threads. My under volt request is simply because we can make the device less hot by lowering voltages on a case by case basis, proven effective in other kernels. Thanks for info and I didn't mean to insult with my requests, was simply going on what others say.
[Nexus 10 Original Android Development] droidroidz:
Franco any chance of upping source? Thx
[Nexus 10 Original Android Development] franciscofranco:
Undervolt might make sense now since the device seems to get hotter than I suspected in the first place. Interactive governor works just fine, and hotplugging this cpu is useless no matter what other users might say so ;)

Yes it might be the algorithm or something like that. I will look into that later today - it really seem that the temperature reporting is erratic.

It just finished uploading, took like 2 hours :(
[Nexus 10 Original Android Development] droidroidz:
Thanks for upping )

which defconfig is being used for compile? Cant find your custom
[Nexus 10 Original Android Development] Hereisphilly:
Just bought your app, the kernel restore function sounds really useful when I'm a serial cm nightly flasher!

Can't wait to see what you can do to this tablet!
[Nexus 10 Original Android Development] IRKONIK:
But only if it does not get overwritten by the kernel. I'll try setcpu ASAP. Problem is: Setcpu allows the higher clockspeed, but I guess it can not force it.

Hey Franco, any chance of getting a tool to set the turned off screen max CPU clock individually? Would be awesome! Either an app or maybe via aroma installer? :)

Also I am glad that I am not the only one.

Cheers, and big ups to Franco for doing such a good job for our N10. So much faster and smoother!

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Nexus 10 Original Android Development] alan sh:
I'm going to try a different kernel till this gets fixed and then come back.

Alan
[Nexus 10 Original Android Development] axionman:
Same thing here

I switched to KTmanta kernel meanwhile

Waiting for the next franco release, luckyly, it will be fixed
[Nexus 10 Original Android Development] EniGmA1987:
Did Franco even adjust the max MHz when screen off from default? Because ROM's set the max speed to 800MHz when screen is off all by themselves and then back to 1700MHz when the screen comes on.
[Nexus 10 Original Android Development] iamikon:
Yeah i don't think that's the issue because on kt i have it set to like 500 for screen off but i was getting sods on r12 as well. Couldn't debug as i needed the tablet right then. One of you guys should grab a kmesg so he can actually try to figure out the problem otherwise it's really just complaining.
[Nexus 10 Original Android Development] situman:
No problems here with latest kernal and carbon.
[Nexus 10 Original Android Development] freedool:
No problem on my N10 here too !

Last Alpha ParanoidAndroid 3.56 and Franco r12.
[Nexus 10 Original Android Development] Kuchma777:
Is there a way to change clock speed when touching the screen?
[Nexus 10 Original Android Development] EniGmA1987:
Like Boostpulse?
[Nexus 10 Original Android Development] JiiJii:
I have the same issue. You said that bluetooth works with stock kernel? Where did you get it?

I tried with stock rom and kernel and the stutter was there. I've been searching solution for this for weeks and newer found a combination that works with bluetooth audio.
[Nexus 10 Original Android Development] rrand:
I never had a problem when I was using stock kernel. I had the stuttering issue with stock ROM and Franco kernel only. I'm using Paranoid Android now and the only workaround I found was to not lock screen rotation. But I only tried that with PA. Maybe it'll work on stock too?
[Nexus 10 Original Android Development] JiiJii:
I'm using Buttered rom and Franco kernel. I've tried Slim rom and KTmanta. Newer found a good combination.
[Nexus 10 Original Android Development] stiggy2012:
I too ran into the bluetooth skipping issue. I think it might be a CPU time related, as it seems to be worse when playing flac files. Re-flashing to stock kernel fixed the issue. Its a shame, as in general I found the kernel to be a considerable improvement in speed over stock.

Thanks for the great kernel Franco, as soon as this issue is fixed I'll be straight back! :good:
[Nexus 10 Original Android Development] Kuchma777:
I mean. I use tablet whole day. And since it hits 1700 every time I touch the screen, I have insane amount of battery drainage.
[Nexus 10 Original Android Development] JiiJii:
Where did you download the stock kernel? Is there a CWM-zip?
[Nexus 10 Original Android Development] stiggy2012:
Not that I know of. Download the stock 4.2.2 ROM from Google. Unzip, and then unzip the zip inside. You will see boot.IMG, this is the stock kernel. You can flash this using fast boot by using the command 'fastboot flash boot boot.img'. voila!
[Nexus 10 Original Android Development] JiiJii:
Thanks!
[Nexus 10 Original Android Development] EniGmA1987:
Why does your CPU jump to 1.7GHz with boostpulse? That doesn't seem right. Unless Franco changed the default from 1GHz to make things smoother.
[Nexus 10 Original Android Development] Hatman41:
there is definitely something wrong with version r12 I installed it and when I went to bed the batt was at 80% when I woke up and my Nexus 10 was deader than a doornail. I then re-flashed the ROM using the stock kernel my device has lasted 2 days without recharging it. I am using the AOKP Buttered ROM.
[Nexus 10 Original Android Development] espionage724:
I notice my clock tends to go up to 1.7GHz as well sometimes when I touch the screen (monitoring with System Monitor Lite). Other times it might jump from 200MHz to 400MHz, or some other random value up to 700MHz. Never saw it go to 1.0GHz.
[Nexus 10 Original Android Development] EniGmA1987:
Maybe 700MHz is the default toughboost pulse. I am used to the KTManta kernel and it uses 1GHz as the default.
[Nexus 10 Original Android Development] snowboarda42:
Getting 1700mhz whenever I touch the screen too, using cool tool to monitor
[Nexus 10 Original Android Development] stonebear:
Mine doesn't.
[Nexus 10 Original Android Development] rrand:
What is your CPU governor set to?
[Nexus 10 Original Android Development] David 617:
First off a huge thank you to Fransisco Franco for taking the time to support Manta. Your work on Toro is amazing.

I just encountered this bug also. I charged my tablet yesterday and it was about 70% full. But today when I tried to wake it it was dead. I'd take a guess that the device somehow woke up and then hung, causing the cpu to eat up the battery. (I'll try to post a log later.)

Once again, thank you for all your hard work and dedication, both on this device and on Toro.

Edit: here are the logs -

kmsg- http://db.tt/d3vJpZK9

dmsg- http://db.tt/iOgnYM8D
[Nexus 10 Original Android Development] eRadicant:
I've also been experience sleep of deaths on R12, reverted to R11
[Nexus 10 Original Android Development] stonebear:
I had SOD wit 12 too but it was when it was first released and I didn't get a log, sorry.
[Nexus 10 Original Android Development] BabyHuey:
Looks like the cause is the freezer commits. Ktoonsez cherry picked one and i get sod's sometimes. Every single one was reverted by a guy who cherry picks from franco. Not tryin to criticize just trying to help.

https://github.com/kiteman44/android_kernel_acer_a700/commits/jellybean?page=1
[Nexus 10 Original Android Development] rubene66:
I just set the min frequency to 300 no more problems for me
[Nexus 10 Original Android Development] Hereisphilly:
I've never had a SOD with r12, ran it when 1st released with aokp buttered manta, and now on cm.

What are people doing to cause it to trigger?
[Nexus 10 Original Android Development] elgar:
I had a SOD once the other day. Had to reboot.
[Nexus 10 Original Android Development] stonebear:
erm...nothing....it just happens. :)

edit

What I mean is, it happens when the device is asleep so you can't "do" anything to trigger it. If you could do something the device would be awake, not asleep.
[Nexus 10 Original Android Development] Hereisphilly:
Whoops, kinda worded it wrong, I meant to say is there a particular state/event or app running that seems to be problematic, i.e., playing music, underclocked, left for long periods of time etc.
[Nexus 10 Original Android Development] stonebear:
I just edited my previous answer. :)

The only event I could think of as a variable might be the length of time left asleep?

Mine wasn't underclocked when it happened, everything was stock.

edit

I have wifi set to always on.
[Nexus 10 Original Android Development] Hereisphilly:
That was my thought, the length of time left asleep

Mine is never turned off, but i leave it at home while I'm out at work for ~8 hours at a time, and then when i sleep, so again ~8 hours

It is hooked up to wifi, so the steady stream of emails might be enough to keep it awake
[Nexus 10 Original Android Development] alan sh:
I think it's when it is really asleep. I have it turning off wifi when sleeping and not powered, and that is when I get the SoD.

Alan
[Nexus 10 Original Android Development] bigdwg71:
I have gone back to r10 which doesn't seem to have the SOD issue. I experienced it with r11 and r12, however.