yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] esgie:
Thanks for this.

Seems this time my tablet is really sharp-smooth, rock-stable and under my full control, now.

It's great.

Too bad Tincore Keymapper (util for mapping touchscreen gestures to physical joypad moves, in result u can play every touch game with your joypad...) stopped working in its full functionality. It shouts that it can't create virtual device as kernel has no uinput support.

This wasn't happening at least on one of previous 2.2 betas.

Possible to fix?
[Galaxy Note 10.1 Android Development] andip71:
Not likely, as I have not changed ANYTHING on the input file systems at all.

Can you try to reflash one of the older betas and let me know with which beta it still is supposed to work? If you do not have the betas anymore, let me know and I can give you a link to them again.

Andi
[Galaxy Note 10.1 Android Development] zezam67:
n8020 4g

any chance this will work in note 8020 4g tab?
[Galaxy Note 10.1 Android Development] andip71:
Hi, you can find the answer e.g. in this post:

http://xdaforums.com/showpost.php?p=49959311&postcount=2252

So the answer is: If you somehow can manage to get me a n8020, then yes. Otherwise, no.

Sorry

Andi
[Galaxy Note 10.1 Android Development] zezam67:
ok,maybe in future you got that device;><)
[Galaxy Note 10.1 Android Development] kude87:
I poke my head in here every few days to stay current with the thread, and I have to say Andi is one of the best devs here. Super informative, helpful, respectful of simple questions, and is quite active in the thread. Just wanted to say thanks again for all you do for these devices, Andi!
[Galaxy Note 10.1 Android Development] ViAlexSt:
Hi, Andi! I'm very pleased that there was such a wonderful core for N8000, with a variety of settings. I just can't find anywhere information about the compatibility of core and additional system tweaks (build.prop, init.d & etc.). Is there any benefit from them if installed and configured your kernel?
[Galaxy Note 10.1 Android Development] andip71:
Well, you will not find more on these things as build.prop etc. are not kernel-related.

Of course you can still tweak your build.prop file and also use init.d scripts to set various parameters as you like. However, I am running with stock Samsung firmware and my kernel and it works just fine.

All I need are the settings in my config app Boeffla-Config V2.

Andi
[Galaxy Note 10.1 Android Development] esgie:
No failure anymore after some time.

Seems more like bug related to my su issues which i had recently.

Probably, everything's ok.

Sorry.
[Galaxy Note 10.1 Android Development] andip71:
Good to know. Everything else would have severely concerned me as I did not change anything.

Thanks for the feedback

Andi
[Galaxy Note 10.1 Android Development] muop_92:
Can I use Triangleaway with your kernel? Could it brick my note? :/
[Galaxy Note 10.1 Android Development] andip71:
Yes, you can use TriangleAway on your note.

It will however reboot into its own flash kernel if you reset the counter, I had to remove direct TriangleAway support a while ago due to instabilities.

And yes, it can brick your note - but the chances are only theoretical and very low. It writes to the bootloader partition and this is always bringing some small risk.

I used it without issues myself a few weeks ago.

Andi
[Galaxy Note 10.1 Android Development] esgie:
Well, as I was posting some time ago, I have a different experiences...

On my device, TA does not work.

It is flashing its kernel, then... not rebooting at all.

Once, it caused a brick (recovery + kernel partition damaged), had to reflash them with odin.

Just a moment ago I have repeated TA procedure, and it behaved the same way - now, I cannot boot my device, reflashing kernel again...

There is a little chance that the issue is related to my individual configuration. Important stuff:

- i use the oldest possible bootloader (to be able to use AllShare Cast with custom kernel)

- i use the mod to install market apps to /data/app, not to /mnt/asec - maybe TA cannot access its files? - however, I cannot check the opposite atm, as i have hardcoded that mod in system files' smali...

Be aware that it was working perfectly before andi removed straight TA support, I cannot confirm however if I had the mod above, yet, or not, that time...

EDIT:

Above mod and old bootloader are not the issue. Reflashed stock recovery and kernel, ran TA once again - it behaved well, resetting my flash counter and returning back to rom. So it is most probably related to kernel itself... ;?

EDIT2:

Yet another trial on Boeffla 2.3b, still no luck. TA does not reboot, and after manual reboot it's a brick. Only way to recover the device is to flash any working kernel once again, as well as recovery.

Temporary solution:

First, flash the old bootloader.

Flash stock kernel (and maybe recovery ... i tried with both), reboot the rom, do a reset with TA, after rebooting write back both Boeffla Kernel and your fav recovery with "dd" busybox command:

dd if=/sdcard/boot.img of=/dev/block/mmcblk0p5

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6

(assuming that ur using n8000 and youve got img files named as above in sdcard; watch out, flashing different mmcblk0pX may cause fatal damage of your device, me not rrsponsible for any damage).

This will NOT raise yor flash counter. But it WILL raise automatically on reboot, after detecting non-stock kernel, UNLESS you flash oldest bootloader before - the bootloader was posted in one of the topic's here by kcurdup.

By the way...

Previously, andi said that previous configuration (ie full integration with TA) was causing bootloop to him/someone else (but it was working for me). It seems that our devices (mine and dev's - i'm talking explictly about N8000, to be exact!) differ somehow... I cant guarantee then if the issues above will occur on ur device! However, you may try it yourself, just keep tar images of kernel and recovery, along with Odin, nearby.
[Galaxy Note 10.1 Android Development] Nightf0x_007:
My tablet was working normally on v2.1 but on 2.2 when i leave it with wifi off and low brightness and no background apps running and around 50% charge , when i wake up i find it turned off with 0% charge i dont know whether battery drains or what happens ? But on v2.1 everything was great
[Galaxy Note 10.1 Android Development] andip71:
Yes, they seem to be very different. Maybe my n8000 comes with memory chips that are working close to the limit. I do not know, have investigated for around one full day and tried almost all things I could imagine that time.

But I could not get rid of my tablet only booting once out of 10 boot attempts. For me, this is a 80% failure rate and therefore not acceptable.

However, on my n8010 I never had such an issue with this thing enabled.

Anyway, it seems to be shaky on some devices, so I rather keep it out.

(not to say if I need 10 attempts before my device boots up again, I can forget about development completely, this just causes work and delays to me)

Yes, for sure everything but not kernel related.

Usual way of going forward:

Install BetterBatteryStats from XDA, fully charge your device, let it run for an hour on its own, then check wakelocks in BBS. You will see, there is an App running crazy or a process which keeps the tablet awake all the time.

Andi
[Galaxy Note 10.1 Android Development] ViAlexSt:
And I have another problem: the PC can't detect the tablet n8000 when connected via USB-port. Option USB Charge default exhibited, 475 mAh. Charging the battery at the same time made​​. I tried to lift up to 550 mAh, but nothing changes. What can be done to remedy the situation? Everything else works amazingly wonderful.
[Galaxy Note 10.1 Android Development] andip71:
PC can't detect PC... what does it mean?

Can it not see the MTP drives, or can't you connect via adb? What do you have, which device exactly?

With that little message I can only give you the answer: "Something is wrong" More I cannot say.

But I can assure you, not a kernels problem, I just used my Tablet connected to my PC successfully.

Andi
[Galaxy Note 10.1 Android Development] ViAlexSt:
This means that PC says "Device not recognized, bla-bla-bla". It started after I set the value of the USB Charge current in 0 mAh. Then I increased the value, but with the same result. Kernel and firmware are not reinstalled. Perhaps the reason is a bad data cable, coincided with one another. :confused:
[Galaxy Note 10.1 Android Development] andip71:
You should change the setting back to 475 and reboot to be 100% sure.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] andip71:
2.3-beta2

Hi all,

I am currently uploading a new beta for you.

Version 2.3-beta2

zzmoove updated to version 0.8-beta10 (credits to ZaneZam) + Profiles reworked

Compiled with Google gcc 4.8 (instead of gcc 4.7)

su updated to version 1.93 (credits to Chainfire)

Fixed permissions in Boeffla-Config app fixing app permissions in /system/app and /data/app now

Enjoy

Andi
[Galaxy Note 10.1 Android Development] vyp54:
Hi, hi!

I've came here after getting to know your kernel from the S3 forum. Has anyone tried to flash this to n8020? Is it possible that it could work?
[Galaxy Note 10.1 Android Development] andip71:
No, it will not work. Do not even try it. It is proven already.

n8020 is too different from the rest of the n80xx family.

Andi
[Galaxy Note 10.1 Android Development] vyp54:
Aw, cr*p. Too bad.

Thanks for the info!
[Galaxy Note 10.1 Android Development] andip71:
2.3-beta3

Hi all,

small maintenance update (both n8000 and n801x versions):

Version 2.3-beta3

Boeffla sound engine 1.6.6: Allow full range volumes for speaker and headphone amplifiers

Optimized some compiler and linker flags (more smoothness?)

Enjoy

Andi
[Galaxy Note 10.1 Android Development] esgie:
I have a question: are there any plans to implement f2fs filesystem support, instead of old'n'rusty ext4 ?

Just flashed the newest DerTeufel's devil kernel to my Note 2 and it seems to work significantly faster! PLUS - the process of migration was easy, fast (no more than 20 minutes, which was spent mostly on waiting for recovery to finish backup/restore) and I have not lost any data.

Now I am testing it - seems to be great. The opinions are also very positive.

(btw - it will probably also require to create a recovery with f2fs support)

Hope the answer is yes ;)

The second question: do you maybe know a way to trigger flash counter reset manually? Or at least: is it possible to enable's TA's support only by repacking your kernel's ramdisk with some changes? PLUS: is it possible that the fact I do not install busybox to /system/xbin, but to /sbin by an init.d script on every boot (so busybox applets override the stock one, so I can run them using short form, without "busybox" prefix before...), may cause that TA runs a busybox command - thinking that it is runing a toolbox one - with, for example, a wrong syntax?
[Galaxy Note 10.1 Android Development] andip71:
Sorry, bad news: As you might have seen in my S3 threads already... no immediate plans to implement this.

For argumentation, please refer to these threads so I do not need to write this again here.

Mainly the "ecosystem" is not yet around that makes it safe enough in my opinion.

Andi
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
I have a problem with a 64 GB microSDXC card from Samsung. Bigger files (only tested with PDF) get damaged after a short time period and cannot be read anymore. I have already tried to change the scheduler, reformatted the card and copy files several times but always with the same problem: after some time of reading the next page turns blank and the file is damaged.

I don't know if it is a kernel setting or a hardware problem. Maybe someone could help me?

Thanks in advance!

PS: The card works as it should in a MacBook
[Galaxy Note 10.1 Android Development] andip71:
Hm, this sounds like an incompatibility between the n80xx and your specific card.

I have a 64 GB Sandisk class 10 and all is fine, and believe me - I am using it a lot.

You cannot influence this by a hardware setting or changing schedulers etc. There must be something else wrong.

Sorry, do not know how I could help you further at the moment.

Andi
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
Okay, maybe I will try to format it in ext4 or NTFS just to make sure it is a hardware problem. It is strange because the card is new and from Samsung and also the fastest card available...
[Galaxy Note 10.1 Android Development] myaslioglu:
Great! I havent been around so long. I am happy to see a good kernel on n8000 at last..
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
Great Kernel !

ROM : ARHD 11.1

Type : GT-N8000

Kernel used : 2.2 stable

State : CPU OC 500MHz - 1500MHz & GPU OC 160 - 350 - 440 - 533MHz

AnTuTu Benchmark

Before Boeffla Kernel : 13700

Before OC : 15020

After OC : 16609

So far it's stable...will do an AnTuTu Stability test after this

Note: I've tried NTFS-3G & it's stable enough for me, why don't you enable ntfs r/w ? :)
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
Could you add the Intelliactive governor from [MENTION=3332811]faux123[/MENTION]?

It is very fast and battery efficient.
[Galaxy Note 10.1 Android Development] andip71:
This is not supported by the driver in the kernel unfortunately.

So I cannot enable it.

I want to check this first.

Any reference where faux put that in?

Thanks

Andi
[Galaxy Note 10.1 Android Development] MaluNoPeleke:
https://github.com/faux123/Nexus_5/commit/7067c4bdd043ff8fe53fef61a47f3d374e452b47

https://github.com/faux123/Nexus_5/commit/264da81ef4e87e7c961ea09cbc8a5ef2049c33d7
[Galaxy Note 10.1 Android Development] andip71:
Will check it when I am back from my business trip again.

So will check it beginning of next week.

Thanks

Andi
[Galaxy Note 10.1 Android Development] andip71:
Update: This governor does not work in 3.0.x kernels due to extensions it needs from 3.4.x kernels.

So, this is not "just" doable. Either it needs to be backported or the kernel layer needs to be lifted. Both not a quick and easy job. So will think about this further first.

Andi
[Galaxy Note 10.1 Android Development] esgie:
Last config app update (today) -> 3 freezees at boot in a row, after running the app - total reset of settings, profiles do not load (they do, but with the default settings), etc.

Edit:

Btw I use Samsung' s SDXC (or something...) 64gb card. No issues at all with it.

Maybe its related to third party software??

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
I really do not know what is wrong with your tablet.

I never have all the issues you describe... weird.

Andi
[Galaxy Note 10.1 Android Development] esgie:
Well "wrong" seems to be a bad word. It's kinda "different" morealike. When u try to fix something - it becomes faulty on my device...

It was a later revision which came with preinstalled 4.1.2 (XEO region). Maybe it's the clue?

I use zzmoove. Maybe its related to changed-order-of-frequency-something (readed about it in changelog some time ago)? Freezees appeared after launching any app with a non-trivial GUI, in a typical way for faulty cpu voltages for high freqs, even if they seemed to be set to my favs in the app.

Guess i'll reinstall the app completely, set the values i like from scratch and post if i figure something out...

Btw previously I asked you about two two things related to Triangle Away:

- is there (well, do you know...) any method of manual reset of the counter (i mean from adb/terminal/whatever/I am aware of the danger...);

- is there a way to revert changes you made related to TA (which was working before for me and not working for you) by repacking your kernel with modified ramdisk? So ill be able to make it TA friendly on my own?)

Would be glad if u help with dat.

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
Hi,

well, wrong was not meant to be bad. It is just... whenever things are working fine for the majority of the people, they do not work for you anymore. This is weird.

About your questions:

- I am not aware of any method to reset the counter via adb. Triangle Away directly does modifications to the boot loaders and data areas, nobody knows to what.

- The changes I reverted were directly in the kernel code (block driver), not in initramfs. So repacking the kernel does not work unfortunately. You would need to clone my repo and compile the kernel from scratch.

Andi
[Galaxy Note 10.1 Android Development] esgie:
Set all the settings from scratch - worked fine. But until reboot...

Reboot -> freezee after 30secs.

Reboot again -> the same.

Reboot -> lauch app before freezee -> switch to GPU tab -> I can see default GPU settings even if i set custom ones -> freeze in next few secs.

Reboot -> quick run of your app -> switch to CPU tab -> default CPU settings shown -> no freezee.

Visiting CPU tab "confirmed" default settings to the system which prevented the crash, thzt's how I understand it...

Weird.

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
It freezes because it applies settings that are not ok.

Can you flash reset zip which is placed into your boeffla-kernel-data folder in cwm please?

Then reboot...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] esgie:
Nope. Flashed the reset zip. After changing cpu settings - same history.

One correction - not exactly displaying the cpu tab but changing the cpu slider prevents further crashes (from 1400 to ie 1200 and immediately back to 1400)

Isn't the boot script FIRST setting the scaling (to 1600 in my case) and THEN the voltages?

In my case, it always resulted in a freezee as default voltahe of 1300 is absolutely wrong for my exact cpu...

And it strangely correlates with the newest changelog info...

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
So you are oc to 1600.

What if you avoid overclocking?

Btw - voltage tables are same as stock. So why do you think they are wrong?

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy Note 10.1 Android Development] esgie:
No problem when no oc, just tried that.

Stock voltages up to 1400 work fine (i undervolt them a bit for everyday use, but not atm, to be sure that i didnt mess up anything else).

1500 needs AT LEAST 1325, and 1600 needs AT LEAST 1388 on my device (values established experimentall, after a long stability tests, those are minimum). Cannot really call them stock, as the device doesnt run 1600 by default at all.

If scaling goes first, cpu crashes before changing the voltage. I was fighting with something similiar in the past..

If voltages go first, then scaling works fine as the cpu goes to a proper voltage directly.

This was discussed in the other thread with kcurdup (other kernel's dev) and seems that I am not the only one with so different voltage table than proposed by you.

Btw im sure it was all working fine before some updates in your app.

In the past, i have dealt with a problem by creating init script which first set the voltages, and then set the scaling, now i cannot find it, it's late here etc but guess the order of cpu settings appliance may be the clue...

Could you post a prev version of ur app? Ie one which handled above in a way before changes? Im a hard gamer so OCing everything is important to me (well, my car's damaged for a while and there's nothing better than some Asphalt 8 ride in a way with damn bus...)

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] faux123:
Fixed :D Have fun!

From d1953b5c91545cb0771080ea99e042f613a89e93 Mon Sep 17 00:00:00 2001
From: Paul Reioux <reioux@gmail.com>
Date: Sun, 16 Feb 2014 23:46:52 -0800
Subject: [PATCH] intelliactive: backport to Linux 3.0.x / Linux 3.1.x kernels

Signed-off-by: Paul Reioux <reioux@gmail.com>
---
drivers/cpufreq/cpufreq_intelliactive.c | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/drivers/cpufreq/cpufreq_intelliactive.c b/drivers/cpufreq/cpufreq_intelliactive.c
index 90f8f90..fddfc29 100644
--- a/drivers/cpufreq/cpufreq_intelliactive.c
+++ b/drivers/cpufreq/cpufreq_intelliactive.c
@@ -149,26 +149,26 @@ struct cpufreq_governor cpufreq_gov_intelliactive = {
};

static inline cputime64_t get_cpu_idle_time_jiffy(unsigned int cpu,
-	cputime64_t *wall)
+	cputime64_t *wall)
{
-	u64 idle_time;
-	u64 cur_wall_time;
-	u64 busy_time;
+	cputime64_t idle_time;
+	cputime64_t cur_wall_time;
+	cputime64_t busy_time;

cur_wall_time = jiffies64_to_cputime64(get_jiffies_64());
+	busy_time = cputime64_add(kstat_cpu(cpu).cpustat.user,
+	kstat_cpu(cpu).cpustat.system);

-	busy_time = kcpustat_cpu(cpu).cpustat[CPUTIME_USER];
-	busy_time += kcpustat_cpu(cpu).cpustat[CPUTIME_SYSTEM];
-	busy_time += kcpustat_cpu(cpu).cpustat[CPUTIME_IRQ];
-	busy_time += kcpustat_cpu(cpu).cpustat[CPUTIME_SOFTIRQ];
-	busy_time += kcpustat_cpu(cpu).cpustat[CPUTIME_STEAL];
-	busy_time += kcpustat_cpu(cpu).cpustat[CPUTIME_NICE];
+	busy_time = cputime64_add(busy_time, kstat_cpu(cpu).cpustat.irq);
+	busy_time = cputime64_add(busy_time, kstat_cpu(cpu).cpustat.softirq);
+	busy_time = cputime64_add(busy_time, kstat_cpu(cpu).cpustat.steal);
+	busy_time = cputime64_add(busy_time, kstat_cpu(cpu).cpustat.nice);

-	idle_time = cur_wall_time - busy_time;
+	idle_time = cputime64_sub(cur_wall_time, busy_time);
if (wall)
-	*wall = jiffies_to_usecs(cur_wall_time);
+	*wall = (cputime64_t)jiffies_to_usecs(cur_wall_time);

-	return jiffies_to_usecs(idle_time);
+	return (cputime64_t)jiffies_to_usecs(idle_time);
}

static inline cputime64_t get_cpu_idle_time(unsigned int cpu,
--
1.8.5.2
[Galaxy Note 10.1 Android Development] tcchuin:
Then don't oc. Not all chips are created equal. If might not be caused by updated app but deteriorated chip
[Galaxy Note 10.1 Android Development] esgie:
[MENTION=1439803]tcchuin[/MENTION]

It was working before app update, as well as on other custom kernels, and even with stock kernel + tegrak overclock util, so "don't oc" is not a satysfying help, especially that i think i know what the solution is (ie. Changing the order of applying voltage values and global voltage scaling).

Do not really understand your "advice", then; I have written:

- it was always working before app update;

- i was oc'ing the device many times before (to be exact: since 2012!);

- it's a problem related to applying voltages-scaling in the improper order (I suppose...);

- i am a heavy gamer and wish to oc everything possible...

...and your precious advice is: "so do not oc". Thank you very much for this, it's really what I wanted to hear!!!

If you don't have to say anything smart, better say nothing... or if you think you have something to say, read the discussion first. thanks, amen.

Plus: settings seem to stick and not causing anny crash even if oc'ed when choosing pegasusqplus governor. The problem is related to zzmoove, i think.

EDIT:

works aswell with pegasusq (regular); seems that my crash is zzmoove exclusive; too bad, as it's my fav.

Andi, any chances to find a workaround?

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
UPDATE:

Run very stable after AnTuTu stability test @ 1500MHz no spiking temp.

AnTuTu Benchmark : 16609

Soft reboot after an unfinished AnTuTu stability test @ 1600MHz.

AnTuTu Benchmark : 18796

Great JOB & Thank you so much....btw we have a similar name :p

NOTE: thinking of the upcoming KK update...will you make a kernel for KK too for us?