yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] kcrudup:
Well, now I'm not so sure- I boot up now in German, which I thought was the result of some corruption due to the "Supercharger" mods I'm testing reverting me back to the original language in the DBT (German) ROM I'm running (BTW, the "/data/system/sync" boot-hang fix was a great find- many thanks for that, it saved my butt here, too).

Now that I've seen two other people have the same problem, it's gotta be the kernel. Maybe it's a race-condition when I switch over the Frandom nodes, or a LANG issue with the version of Busybox I've included.

Can y'all do me a favor, and send me the output of "cat /proc/version" as well as the link you'd used to download the boot.img (if you remember)?
[Galaxy Note 10.1 Android Development] esgie:
Uh u misunderstood us - it's a SuperSU 1.69 issue, and its not kernel or even device related..

Nothing to worry, then. Hope u didnt spent all night looking for a non existent bug ;]
[Galaxy Note 10.1 Android Development] kcrudup:
Well, I'll be- once again, thanks, as I was going to spend a lot of what would have been wasted time on this!

There's a SuperSU 1.72 Beta on CF's page that I'm about to try out, that among other things fixes this issue.
[Galaxy Note 10.1 Android Development] kcrudup:
I've got an update that I like enough to publish. There's not many changes, though- it's still got the "frandom" stuff in it, plus I've added in some suggested changes from the Supercharger V6 thread (mostly Virtual Memory and Network Buffer changes, I didn't touch the Low-Memory Killer settings as Samsung's defaults actually work pretty well for us, as we have 2GB RAM). I've also added in preliminary support for the "fiops" scheduler that [MENTION=5129165]esgie[/MENTION] had asked for, but it's not complete yet (there's some fair-scheduling code that needs to also be cherry-picked in, but I have to update some parts of the I/O Block Layer to make those work) and I'll add it in later.

I also have to add support for the OC voltages [MENTION=5129165]esgie[/MENTION] wanted, but those will come later as well.

Here's the OC version.

Here's the non-OC version.

Development is likely to slow down, too- the 3.0.x kernel that our devices use has now been marked "End of Life" at version "101" by Linus and crew, so unless I see something compelling from upstream (which does happen) or a security issue comes up, I probably won't have anything new for a while.
[Galaxy Note 10.1 Android Development] esgie:
Great job!

However: guess I'll personally wait for finished fiops / stable voltages version, as I use Supercharger (along with zeppelinrox's network tweaking scripts) for everyday use, so those tweaks will be not a big change for me. Of course, it would be nice to get rid out of those scripting mess Supercharger makes in system, but not in the cost of repeating the nightmarish procedure of setting my voltages in first 20 secs after boot, which took 6 tries before I did it succesfully = 5 crashes of unsuccesful trials = 5 chances of messing up my data last time ;]

As you seem to use - or at least analyze - the performance scripts messing around, maybe you'll look into CrossBreeder (look for it on XDA, very easy to find...)? It's a thing that implements another method of generating entropy (worse than frandom BUT the best one which can be used without additional kernel module - at least this is what they write...), BUT also some dns caching + light ad blocking stuff which seems to be worth looking (however, as it's working on system layer it's just for your knowledge; i don't think it's a good idea to implement those in kernel or something...).

And as to the developing slowdown - it's okay, as the elements essential for performance as well as stability - which are the most important thing to final user - seems to be on place ;] well, I think we're all waiting for 4.3 stock system, so I agree that it is pointless to spend whole free time on upgrading something which will be depreciated in the nearest (hopefully, Samsung!!!!) future...
[Galaxy Note 10.1 Android Development] kcrudup:
Well, you're my current source of external QA, so let me gin one up for you specially and put it out sometime this weekend. Stay tuned ....
[Galaxy Note 10.1 Android Development] GDT:
This release doesn't work for me. Hangs my note at startup. I'm speaking of OC version. The previous one was ok.
[Galaxy Note 10.1 Android Development] aoryx:
Works fine for me

Re-download and try again
[Galaxy Note 10.1 Android Development] esgie:
If youve been reading carefully you'd know that the oc version works on some devices only, including the kernel dev's one.

For example: it is working long enough for my device (about 20-30 seconds after boot) to set different voltages by tegrak overclock app (and only this app seems to be capable of changing the voltages, as it uses its own module; voltages are blocked by default so no other app can handle it). For other's device the voltages may be too low at all to even boot. For others they seem to fit perfectly.
[Galaxy Note 10.1 Android Development] GDT:
I'll be more precise. With old releases I can use the kernel [MENTION=428455]Stock[/MENTION] settings voltages without issues. Now it locks on startup.
[Galaxy Note 10.1 Android Development] esgie:
Ok but the problem is still the same. As I said: the last oc'ed version has non-stock voltages by default plus they cannot be modified in an easy way, and they cannot be modified at all before the boot process reaches a homescreen phase. Youll have to use non-oc'ed version atm (and you can overclock it with a Tegrak Overclock app, which seems to work well however it's not the most elegant solution as you'll see) or wait till dev releases a oc'ed version with stock, near-stock or at least editable voltage table.

Please note that n8000s are so different between themselves that the last kcrudup's kernels before a break did work for you (as u write in the post above), but didnt for me, causing a crash on boot.

Looks like the sammy's quality control of cpus used in n10.1 is much less strict than cpus used in for example n7100 - where oc'ing the cpu from 1600 to 1900 seems to working with every single device... and the stability discussion starts when oc'ing to 2000mhz or more...
[Galaxy Note 10.1 Android Development] GDT:
I suppose that Samsung simply pushed poor quality chips which came up from quality checks into our note tabs.
[Galaxy Note 10.1 Android Development] esgie:
I'd like to discuss also the thing mentioned above as in my opinion it is not the best idea to ignore low memory killer settings and implement only low-swapiness memory management settings.

I don't know how many apps you have installed on your device. I have 300+. In such a conditions, using V6 without lowmemorykiller settings (ie. with stock settings, 72MB as the last minfree value) results in unacceptable lag, occuring since 2-3 minutes after boot; in next 5 minutes, the system becomes completly unresponsive and extremely laggy (example: the command prompt isn't showing up when turning on Terminal Emulator, etc.).

It just runs out of memory!

The only way to solve it is to reboot.

On the contrary, when the minfrees are set to higher ones (to either 1000 HP settings ie. 275 MB as the last value or MinFree Calculator ie. ~480 MB as the last minfree value) along with the V6 grouping options are on, the system is perfectly smooth for all the time (+ I am flushing caches in 1hr intervals).

My observations are leading me to a conclusion that ignoring the lmk settings and implementing the rest of V6 settings may lead to unusable system when the memory load is really high.

That is the reason why I have repacked your kernel (for my personal use), with modified init.rc containing all V6's additions and commands so I do not have any freezees problems; also the lags, which were "acceptable" even when using V6, no longer occurs when frandom entropy is on. This is the most awesome combo in my opinion.
[Galaxy Note 10.1 Android Development] kcrudup:
I see that's also a Exynos 4412 CPU; I'll go grab the official Samsung kernel for that device and see what their voltage and frequency tables look like. Perhaps that'll bridge the gap between the various Note 10.1 devices?

~250.

See I don't see that- I purposely waited over a week of testing before I'd released the V6 SC-enabled kernel, just to test for things like this.

How full is your flash? How many GB are left in /data?

Do you mind posting the values?
[Galaxy Note 10.1 Android Development] esgie:
The point is that N2 was planned to be sold - with success - in amount of xxx mln devices and N10.1 - in probably 10-100x less. This MAY be a reason why N10.1 cpu's are less stable in general.

Well, I was talking about minfree settings, but forgot about the adj priorities, which V6 also modifies in parallel - maybe patched services.jar (which I do have) plus UNSET ADJs values result in such a freezees? I don't know, coz V6 scripts turns both minfrees and adjs tweaks in a row... and dont have time to study V6 thread atm... ;[

Well, do you have services.jar patched? Maybe it's the clue - patched services.jar needs higher minfrees and non-patched services.jar do not need such a high minfrees... Dunno, have to check it out...

A lot of, 3GB+, even with two games with 800mb and 1.5GB apk, mainly because I prefer to put stuff on extSdCard (games obbs aswell - I bind them to sdcard with another script at boot...) plus I am using dalvik2cache script (which moves whole dalvik-cache to /cache)

But which values?

For minfrees, V6 script gives me two alternatives:

1000HP (recommended within the script): 8,16,200,220,240,275 (in MBs, not in mempages!)

Calculator evaluated: 8,16,363,399,436,472 (MBs)

I prefer the first one (1000HP) as it gives me an excellent experience when multitasking and very good experience when gaming

The second one (Calculator) result in more tiny-little-lags when multitasking with apps which I use in less frequent manner, related to re-loading of some lower priority apps in high mem load situations, as they are thrown out of mem by lmk faster than with previous settings. BUT this settings gives me a LITTLE better performance when gaming (and when benchmarking!).

Please also note that V6 script creates an example init.rc and some additional init.blah_blah.rc files which then u can "bake into your rom", as the script says, i.e. repack the kernel along with them. Didn't analyze it in details in the context of V6 additions, just "baked it" as is ;]

EDIT 10th Dec:

Don't have time to post another theorem, so quickly: mainly, you took the right path but I was also right (but just a little); the main reason of extreme lags when running not-fully supercharged Supercharger are not-set minfrees and adjs - BUT only when running patched services.jar. On the other hand, when services.jar is not patched, the stock values seems to be ok (however, my experiences with patched services.jar AND minfrees+adjs are a little better...).

So, as the kernel doesn't come with patch to services.jar, there is no point in tweaking minfrees. And if someone decides to patch services.jar, he will probably also set his minfrees with v6 script, so it's not a problem too...

Btw changed the launcher recently, to Google Experience form KiteKat btw (leaving the TW framework additions, so it doesn't conflict with the TW specific apps which still runs perfectly). Seems that the system is even more smooth...
[Galaxy Note 10.1 Android Development] stederlee:
Kernel for android 7 (CM14)

Thank you so much for your kind share. But right now I am runnning CM14 on N8000, and the current kernels on your post don't work well with it. Is there any solutions?
[Galaxy Note 10.1 Android Development] JJEgan:
Last post was 2013 .

OP not active since 2012 .

Looks like you are going to get no answer .
[Galaxy Note 10.1 Android Development] timrock7:
it was a long shot yeah, but i would also like to see a kernel for atleast 4.4.2 for gnabo rom if not anything else
[Galaxy Note 10.1 Android Development] tmaurice:
N8013 kernel loaded. No problems installing. SPen good. Using Nova launcher - extremely snappy. Did not change governor (default is pegasusq). Cleared background tasks before each run. Benchmarks so far:

Linpack - average 190

Quadrant - average 6100

RL Bench (SQL) - average 18.2

Antutu - average 13900

Wifi - when out of range of 5Ghz, automatically switched to 2.4Ghz. No problems with hitting top speeds on either. Signal range for 5Ghz seems a little shorter than before, but not drastically.

Seems stable. Wouldn't be surprised if this can be OC'd higher.

Will use throughout the day and report any problems.
[Galaxy Note 10.1 Android Development] gwbard:
thanks for report tmaurice :)

what ROM are you on? I'm running CM10, and just looking around to see if there's any good reason NOT to give this a try...
[Galaxy Note 10.1 Android Development] pwch:
Everything is fine on N8010 (sales in China , N8010ZCALG7) but still needs to keep eyes on it

BTW: N8010-CHN supports 5GHZ WLAN by flashing "N8013 - JellyICS RoM", but UNAVAILABLE in OFFICAL firmware. Sadly both JellyICS and Urban HD are unstable for N8010.
[Galaxy Note 10.1 Android Development] mitchellvii:
Did you overclock to 1600? I tried using Setcpu and got FC. Seems stable at 1500. I have it set at performance / cfq. What do you have?

** OK best quadrant scores came at 1500 performance bfq. 1600 will not hold. Top quad 5601 running stock firmware plus kernel.
[Galaxy Note 10.1 Android Development] gwbard:
here's a pretty good reference post about the governors & i/o schedulers:

http://xdaforums.com/showthread.php?t=1369817

I wouldn't ever run it on 'performance' (except for playing a game, temporarily)

that will kill your battery in no time
[Galaxy Note 10.1 Android Development] tmaurice:
Running stock ROM.
[Galaxy Note 10.1 Android Development] mitchellvii:
Yes but I have always thought that constantly changing CPU speeds might wear out battery just as fast. Like constantly stepping on the gas and brake instead of just cruising at high speed. Plus I run like no Widgets at all so my battery lasts a long long time.
[Galaxy Note 10.1 Android Development] tmaurice:
Using System Tuner Pro. Pushed CPU up to 1600 on all cores, no problems. Opened up SD cache to 6144 (like I did on my Infinity to help alleviate some of the I/O problems on that device) and left that scheduler on cfq. Did not touch voltage.
[Galaxy Note 10.1 Android Development] mitchellvii:
Can't hold over 1500. You probably just have a better binned CPU than I. However increasing my SD cache did increase my quad scores to 5650.

** Changing my I/O manager to bfq increased my quad score to 5750. Significant.
[Galaxy Note 10.1 Android Development] gwbard:
just as I suspected -- CM10 does not like this kernel at all :/

oh well
[Galaxy Note 10.1 Android Development] mitchellvii:
Every time my tablet goes to sleep I have to stop and restart wifi to get signal upon waking.
[Galaxy Note 10.1 Android Development] tmaurice:
I had a bit of the same problem for the first couple of hours. I rebooted a couple of times, then went in and changed the advanced network setting in Keep Wi-Fi on during sleep from the default of 'Always' to 'Only When Plugged In', rebooted, then switched it back to Always.

I'm still having occasional disconnects on 5Ghz, so I think it's a problem with the kernel. Also not getting the speed I should on 2.4Ghz, so I may try tweaking the build.prop later.
[Galaxy Note 10.1 Android Development] tmaurice:
Well, been using this for two days now. Going to go back to stock kernel. There are too many problems with inconsistent wifi signal, both on 2.4 and 5Ghz. The extra boost from the OC up to 1.6 is really nice.
[Galaxy Note 10.1 Android Development] kaipro:
Can it be uswd with leak jelly bean?
[Galaxy Note 10.1 Android Development] bryanvo:
After flash it on my n8013 got problem with my wifi. The wifi was not good, it in and out all the time.
[Galaxy Note 10.1 Android Development] jamesheryanto:
+1
[Galaxy Note 10.1 Android Development] mirek190:
I have problems with wifi as well on my note 8010 .

I noticed that on LGC was fine but on LH2 ( newest ) wifi is very unstable with this kernel.
[Galaxy Note 10.1 Android Development] nickwarn:
Has devoloping stopped on this kernel? Would be a shame
[Galaxy Note 10.1 Android Development] brieuwers:
Check update.
[Galaxy Note 10.1 Android Development] nickwarn:
guess this is only for Sammy ICS and wont work on JB OTA?
[Galaxy Note 10.1 Android Development] mitchellvii:
Looks nice. I sure wish we could get some 8013 development.

Any idea what was causing the wifi disconnect problems?
[Galaxy Note 10.1 Android Development] brieuwers:
Im still running on ICS and did not test the kernel on JB.

I dont know if this kernel works on JB or not.

Maybe someone can give it a try en report.
[Galaxy Note 10.1 Android Development] brieuwers:
I really dont know what is causing the wifi problems.

It kind a hard to develop a kernel for a device I do not own.

Kernel developping needs testing and thats where the problem is when I dont have the right device.
[Galaxy Note 10.1 Android Development] mitchellvii:
Have you changed this kernel in some way to no longer support 8013 or are you simply stating that you no longer support it because of the existing wifi issues?

Also, on your prior iteration of this kernel, I wasn't able to overclock above 1.5 without it freezing up. Have you done something to improve this so it can work better at higher levels?

Thanks :)

---------- Post added at 02:51 PM ---------- Previous post was at 02:36 PM ----------

Huh, Gave it a try on my 8013 anyway.

SetCPU at 1704 seems stable running at Performance. Tried 1600 and crashed. Who knows?

Anyway, just turned in a Quadrant Score of 6308. Pretty frickin impressive. ;)
[Galaxy Note 10.1 Android Development] brieuwers:
I dont know what it is with your device. I got my first freeze ever running at 1800mhz.

So I stopped supporting other devices then N8000 because I cant test the kernel before launch.

Im running 1704mhz for 10 days now without any problems.

Working on 1800mhz right now but its not stable and gave me my first freeze ever on the note 10.1.
[Galaxy Note 10.1 Android Development] mitchellvii:
See my above post. Stable at 1704. Just didn't like 1600 for some odd reason. So far wifi seems stable. Who knows?

P.S., I made a post in the General Section pointing people here. You should be getting some more traffic.

Great work!
[Galaxy Note 10.1 Android Development] Mister_Mxyzptlk:
Boy do I have one funky device now.... a GT-N8013 ODIN-flashed with GT-N8010 firmware and running a custom OC'd GT-N8000 kernel. I wonder what Samsung would say if I sent it in for repair.... even with the flash counter at zero and showing official binary?
[Galaxy Note 10.1 Android Development] mitchellvii:
Damn this tablet is fast now. Notice it most of all when typing in forums online. No lag. I'm happy :)

---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------

Ah I see why this is stable at 1704 but it wasn't at 1600. You nudged the voltage up to 1425 mv from 1300 at 1704.
[Galaxy Note 10.1 Android Development] DJsCrIBbLe:
Cool it works on 8013 sucks 8013 was dropped from issues
[Galaxy Note 10.1 Android Development] mitchellvii:
Well have mine set at 1.7 performance with cfq scheduler in SetCPU and haven't have a single wifi disconnect yet.

Perhaps the increased voltage to 1425 mv is helping? Maybe overclocking above 1.4 at 1300 mv was causing wifi to crash? So maybe it was never a driver issue at all, just a lack of power?
[Galaxy Note 10.1 Android Development] lm that guy:
Hmm im no dev but that makes sense
[Galaxy Note 10.1 Android Development] DJsCrIBbLe:
I dont think a voltage or clock would cause wifi or 3g say on a phone or tablet crash...

Usually data related stuff is its own thing in a kernel ?

Also i dont want to use the n8000 kernel because it might contain stuff that doesnt pertain to my device 8013... Being the kernel is the middle man between software and hardware. .thats where issueals might arise
[Galaxy Note 10.1 Android Development] mitchellvii:
All I can give is imperical evidence. Wifi sucked and i increased voltage now its perfect, draw your own conclusions.
[Galaxy Note 10.1 Android Development] lm that guy:
Id like to test this theory out with a 8013 kernel. Im willing to test before an official launch if the dev is ok with it.
[Galaxy Note 10.1 Android Development] mitchellvii:
Was running at 1704 for hours perfectly then things started getting a little funky and crashed a few times. Tried backing off to 1600 and reset voltage to 1425 mv. This used to lock things up but at 1425 things seem solid.

I wonder how high we can go safely with the voltage?
[Galaxy Note 10.1 Android Development] mitchellvii:
Went back to 1704. Seems fine.

Best quad score yet 6538.
[Galaxy Note 10.1 Android Development] lm that guy:
http://db.tt/IXs8lxy2 highest ive gotten on stock kernel was 5490 so thats insanely fast
[Galaxy Note 10.1 Android Development] nickwarn:
Tried it on JB OTA, didn't boot. It didn't even go in to Samsung boot screen, after the first splash screen saying Samsung Galaxy Note 10.1 it just goes black. To bad,I wanted to try this but I'm not going back to ICS. Keep up the good work OP.

Skickat från min GT-N8000 via Tapatalk 2
[Galaxy Note 10.1 Android Development] mitchellvii:
Wow you like living dangerously :) Luckily you didn't hard brick that thing.
[Galaxy Note 10.1 Android Development] Mister_Mxyzptlk:
Did some investigating. This is anecdotal, but I tried this kernel on my device running an ODIN-flashed stock 8013 ROM, and had zero WiFi issues. However, when running an ODIN-flashed stock 8010 ROM, this kernel made wifi go haywire... which is a good movie by the way.
[Galaxy Note 10.1 Android Development] mitchellvii:
People, don't make a habit of flashing ICS kernels on JB builds.

1) Probably won't work anyway.

2) Could brick your fancy new toy.
[Galaxy Note 10.1 Android Development] davp:
I know not recommended, but tried this on n8010 for a short while. Here's what worked

1704Mhz. :)

Bluetooth mouse/kbd

Wifi

Gps

I tried external otg usb with fat32, seemed to loop mounting/unmounting

Maybe some of the wifi issues others have had are related to different rom versions, I've got stock xwalg4 with some bloat removed..

Thanks for your efforts!
[Galaxy Note 10.1 Android Development] mitchellvii:
This kernel is funny. It works perfectly for me for many hours then it suddenly starts getting hinky and acting weird.

Anyway, just back to regular old 8013 kernel for now. That was fun but for some reason after about 8 hours use if gets crazy on me. Who knows?
[Galaxy Note 10.1 Android Development] bigdaddywong83:
This kernels great
[Galaxy Note 10.1 Android Development] bigdaddywong83:
It's been past 8hrs since I've put this kernel on...reporting back that it's working real sweet to me.
[Galaxy Note 10.1 Android Development] rcanal:
WiFi Problem

I have the same Wifi problem.

It goes and comes.

Everything is working alright, except for the WiFi. It's kind of annoying.

Any solution?

:eek:
[Galaxy Note 10.1 Android Development] brieuwers:
After updating my tab to xwali4 I had Wi-Fi problems to.

Had to build new kernel and now it seems stable.

I will upload a version 2 of the kernel.

This could solve some Wi-Fi problems.
[Galaxy Note 10.1 Android Development] brieuwers:
XDA seems to have some problems right now.

Editing and uploading new kernel wont work.

I will try again later.
[Galaxy Note 10.1 Android Development] BUBA0071:
Great News. Looking forward to the new kernel. Just what i need, Galaxy note 10.1 xda forum is finally heating up.
[Galaxy Note 10.1 Android Development] brieuwers:
Updated new kernel
[Galaxy Note 10.1 Android Development] Haldi4803:
Downloaded the new Kernel on my 8010! flashed via High on Android recovery.

works fine it Seems. couldnt find Any Problems with my Home WiFi, iR still working.

overclocked And underclocked 25-1704 Seems stable. gonna Test undervolt tomorrow.

how comes 1704mhz Is the Maximum? Is There Any Chance we will get higher clocks Or Is this because Kernel goes up to 1704mhz at Boot?