yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] andip71:
Wow, that was super fast. Thanks for the heads-up.

Will give it a try in next beta!!!

Many thanks to you, [MENTION=3332811]faux123[/MENTION]. :good::good::good:

esgie, about... it was working with previous apps, I am sure then something else was causing it.

If you want to try, I can give you any app version I ever released.

But I can assure you, nothing has changed there since I release V2 of the app many months ago that could explain it.

I still do believe, we need to find correct volting for the OC frequencies on your device.

And I agree, we should load voltages first, then applying the OC. When I am back from my business trip / holidays next week, I will change the order of settings applied a bit to accomodate this. Then we will see.

BTW - I am also running zzmoove, but I never OC. So I will give it a try soon as well. zzmoove is still on beta, so maybe something still needs to be done.

Andi
[Galaxy Note 10.1 Android Development] chandler929:
First，Thanks for the best developer.

This kernel made my N8000 Fast and smooth.

Now I'm overclocking to 1600mhz without undervoltage.

Please DO NOT Undervoltage when you want to overclock.

Undervoltage will let your machine unstable.

That's my suggest.
[Galaxy Note 10.1 Android Development] muop_92:
For my device, I have to overvoltage 25mV to get oc 1600MHz
[Galaxy Note 10.1 Android Development] esgie:
I still insist i'm right.

1. As I have written before, I KNOW what are the stable voltages for OCing my device (1325 for 1500mhz and 1388 for 1600mhz).

2. They ran and still run perfectly when applied in correct order: FIRST - the voltages (with max freq still at 1400mhz); THEN scaling, that means: max freq to 1600mhz.

3. If applied in the different order, when upscaling max freq to 1600mhz at the first step, the voltages for 1600mhz are still set at at "stock" 1300mv. This causes immediate freezee. App/script can't apply custom (correct) voltages, then, cause the system has just crashed.

4. I just confirmed that by adding init script:

echo "1388 1325 1263 1213 1175 1125 1050 988 975 963 950 938 925 900 875" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

/sbin/busybox sleep 1

echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "1600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

The voltages for 200-1400 are my UV settings, but they can be stock values aswell. The clue is in first two values. Script first sets the correct voltages without oc'ing the cpu, so when the freq is lifted up after a while, it automatically uses the proper voltages, already set a second ago. And with this little addition, everything works fine, even zzmoove, as the voltages are already set and whatever your app will oc my cpu to, it is secure coz fine voltages are already set by my script.

5. Above proves that boeffla config app FIRST sets the highest voltage possible and THEN sets a custom voltage for it, and on my device it is too late for performing the 2nd operation as the cpu has already crashed after oc'ing with too little, stock voltage.

6. Others' devices are not crashing as - I assume - they might be able to run 1600mhz@1300mv at least for a while, before the custom, stable voltages are set. My device needs at least 1338mv to run AT ALL at 1600mhz, and even a fraction of second spent in 1600@1300 causes freezee.

7. No need of prev version of your app as the script above fixes all the issues for me.

Hope now u understand the issue. The problem is in applying THE CORRECT SETTINGS IN THE WRONG ORDER.

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

correct and wrong is debatable. But anyway: It was NEVER in any version of the app different. It was ALWAYS like that, since Boeffla-Config V1.

That is something I can confirm.

But I said already, I will change the order to first set voltages, then frequencies, both for CPU and GPU in the next app version. Then your problem should be gone as well.

However, something is really weird with your tablet - this is something I will now insist in. Not having Triangle Away with its own flash kernel doing a proper job on your specific device but causing a soft brick is also not normal. But this just on a side note.

Anyways:

- you have workaround solution

- I will change the order as said

Sorted :)

Andi
[Galaxy Note 10.1 Android Development] esgie:
Thank you.

Well in this case, my tablet appears just to be very opportunist to any OC, and need very high voltage to run 1600 at all.

I must also add that there is no way to OC it to 1700mhz - which others run without problems at all..

Analyzing your script in /res took me to another point: as far as i can see some governors have hardcoded voltages inside their settings - maybe that's where the scaling overtakes the voltage table setting? And maybe thats the reason of zzmoove crashing, while other not?

PS hey, one of stock FW updates half-a-year ago came with the PIT update (mainly for enlarging the system partition, as all the samsung apps couldn't fit on it). I have never installed it by OTA. Maybe that's making the difference when comes to TA usability? Maybe bootloader related partitions sizes were slightly modified, too? Maybe you have done it OR your device came with it already? That may explain i'm a minority also - maybe most of current users bought n8000s in the later period, when iit became cheaper?

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
Governors take care about frequency scaling, but not voltages.

Where do you think you have seen voltages in governor settings?

Andi
[Galaxy Note 10.1 Android Development] esgie:
Ur right - Nowhere (i mispelled, i meant frequencies, not voltages, sprry). BUT if they scale the freq BEFORE voltages are applied from the setting not related to governor - it will cause a crash too, basing on the same mechanism i described above.

The ultimate solution is to set voltages BEFORE any other cpu settings!!!

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
Next version of the app, so in 1-2 weeks latest.

Just for you :)
[Galaxy Note 10.1 Android Development] esgie:
Hope not only for me ;]

No hurry as the workaround works fine.

Btw did u read my notice 2 posts ago about my idea why ta not working? How can we compare the bootloader partition size? My mmcblk0p1 is 4194304 bytes (obtained by output of dd if=/dev/block/mmcblk0p1 of=/sdcard/bootloader.img)

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
The bootloader partition size is most probably the same, however maybe you have a bootloader installed that breaks the whole thing.

I even downgraded my bootloader to a very old version a while ago to make sure the count stays on 0 after downgrade.

But as I am currently on a business trip, I have no access to the data until next week.

Andi
[Galaxy Note 10.1 Android Development] esgie:
My second idea: i use init script to extract busybox symlinks not to xbin (as most users do), but /sbin, every reboot, on-the-fly, mostly to override short forms of commands (so i can use "chmod", not annoying "busybox chmod", to summon busybox applet chmod and not toolbox one), withot manipulating the real filesystem.

Maybe TA uses short versions when performing operations leading to kernel flash, and there is some inconsinsesty between the syntax of some command which is leading to failure? Stock kernel doesnt have /sbin/busybox file, my script fails and all the commands are on their "stock" place so TA works again...

Then it will be completely my "fault" that TA doesnt work for me.

Dont have my PC with me in order to recover from possible failure, so ill check that one tomorrow...

Sounds reliable however.

Wysłane z mojego GT-N8000 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] andip71:
esgie, interesting theory. Please let me know about the outcome.

And... you have a PM in 2 minutes with a link to a boeffla-config test version.

Good night

Andi
[Galaxy Note 10.1 Android Development] esgie:
...and good morning ;)

Will check everything today and feedback, but probably not before 5pm CET.

Thanks.

EDIT:

Found some time... Deleted my voltages init script, installed test app (THANKS FOR THAT ONCE AGAIN!!!), rebooted with zzmoove/battery yank (which is my preferred config - thx for advice u gave me some time ago, btw) - tablet seems to be stable as hell, settings seems to stick, OC working fine as it reaches 1600 MHz according to in-built, brief stats included in your app. Looks like a good job.

Thus, I cannot reboot for the 2nd time now to confirm 100%, seems that all works fine as the freezee occured every time, without exceptions, before.

Will look into the TA issue in a minute and report back.

EDIT2:

Deleted another init script, for installing bbox on-the-fly to /sbin - Triangle Away WORKED FINE!!!

It was fault of my modification, then. I'll make further investigations of the config which will suit best for me, however...

I need to announce then that Triangle Away is working fine with your kernel.

I also need to say sorry for misleading some users here,

Amen.

All the issues seem to be cleared out so you'll finally get rid of my whining :)

Thank you once again.

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

unfortunately I have to inform you, I will have to disappear for personal reasons for probably a few weeks.

In short: My private car got stolen in front of my house yesterday. Today I was supposed to go on a holiday trip with my car.

You can probably imagine I have to do a lot of things over the next few weeks with police, insurances, banks etc. to get this somehow sorted.

This will take lots of time and I expect to not be able to spend much time on kernel stuff therefore.

Thanks for your understanding

Andi
[Galaxy Note 10.1 Android Development] esgie:
Feel really sorry for the described circumstances.

Hope you'll deal with the troubles asap.
[Galaxy Note 10.1 Android Development] vitoski:
Andi I hope they will get that bastard and get your car back. That sucks people are doing this things. Take your time and don't worry about XDA. N8xx works awesome with your kernel as of now!

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
I'm really sorry for the unfortunate event.

I hope it's get sorted quickly & the bloody thief get caught soon.
[Galaxy Note 10.1 Android Development] andip71:
Ok, still in the process of sorting out paperwork with insurance, bank, police, car registration office etc.

But at least back to a point where I can start reading the threads again.

Andi
[Galaxy Note 10.1 Android Development] muop_92:
Why I can not read a ntfs usb by otg? I have turned ntfs module on
[Galaxy Note 10.1 Android Development] andip71:
Because it is not enough the kernel supports it. Also the rom needs to support it (in order to autmatically mount it). However, Samsung firmwares do not do that.

So, you need an additional app like Chainfire's "Stick mount". This app recognizes a plugged in NTFS formatted volume when the kernel supports it, and mounts it.

Please be aware: The NTFS kernel module only supports reading, not writing. Just to already answer your probable next question :)

Andi
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
CMIIW, but if android is using the same kernel as Linux, then it should have NTFS support/driver long time ago.

The only missing part is NTFS-3G.

I manage to use ntfs3g for android & mount r/w any NTSF HDD manually on my N8000

I even tried an NTFS formatted microSD + auto mount script.
[Galaxy Note 10.1 Android Development] andip71:
But we are talking different things.

I have enabled the kernel NTFS (read-only) driver as a loadable module in the kernel.

NTFS-3G is a fuse (file system in user space) driver, nothing to do with the kernel.

Of course, this module can be used instead and even provides RW access potentially. But do not ask me how, I never used it so far.

Andi
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
Even Linux is still using Fuse NTFS-3G driver.

Still you've given us a great kernel & thanx for that :D

I hope your thievery problem fixed soon, coz I can't wait to try 2.3 :D

THANK YOU AGAIN :D
[Galaxy Note 10.1 Android Development] esgie:
https://play.google.com/store/apps/details?id=com.paragon.mounter&hl=pl

This app deals with NTFS very well.

Supports automounting, write-support enabled driver (it's some kind of universal driver, probably fuse based, didnt investigate on that...), out-of-the-box, NTFS support is no longer a problem at all after installing it.
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
There are several apps that do the same,but isn't it nicer if all kernel supported NTFS R/W without using any 3rd party apps ;)

Actually I have ntfs3g file,but to make it auto mount I should compile it into the kernel.

And even though I am an IT literate, I've never compile/edit a kernel before :D
[Galaxy Note 10.1 Android Development] andip71:
2.3-beta4

Hi all,

I am currently uploading the new beta version for you.

Version 2.3-beta4

28.02.2014

Updated zzmoove governor to version 0.8 RC1

Implemented new governor "intelliactive" (credits to Faux123)

Updated BFQ scheduler to version v7r2

Enjoy

Andi
[Galaxy Note 10.1 Android Development] muop_92:
I have been trying new version for 3 days, significantly smoother :) thank you
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
Hi Andi,

I encounter a strange behavior using 2.2 that I just realized.

I'm using ARHD 11.1 ROM & before I use your kernel I encounter no problem at all.

When I flashed your 2.2 kernel my internal storage is around 2 GB free & I'm installing new apps.

Recently I'm almost out of internal storage, 1.5GB left & a "Hang" occurred twice (may be due to OC).

Then I found something odd happened.

Several of my apps are lost during reboot.

Tried to reinstall lost apps but after reboot they all gone again.

The language also revert to polsky (or something like that).

I revert the OC then reboot, clean cache from recovery, but the apps keep missing after reboot.

All of the apps that I had before flashing your kernel is intact, but only a few apps that I install after flashing your kernel is keep missing after reboot.

What happened here??
[Galaxy Note 10.1 Android Development] andip71:
I think it is the well-known issue with broken zipalign script that comes with the rom and leaving apps with improper permissions.

Try the following:

- install latest 2.3 beta of the kernel (this is really important!!!)

- remove a script from init.d when it has the term "zipalign" in it

- in boeffla-config, choose fix permissions function

- reboot

Could be, after that the apps are back.

Would also not be bad to wipe the dalvik cache once after having done that.

Andi
[Galaxy Note 10.1 Android Development] d4rkkn16ht:
I flashed 2.3 Beta4 & fix permission + reboot

...And everything back to normal

The Zipalign script log shows no problem at all.

How can that be ???

May be the OC & OV is causing all that. Now no OC/&OV.

But thanx anyway coz it's all good now ;)
[Galaxy Note 10.1 Android Development] andip71:
Well, as I said... many times the fix permission scripts do not do their job properly, and then it leaves some apps in a wrong status.

Why... I never investigated the scripts in detail. I do not use them as a rule of thumb.

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
hello guys, Im looking for information, if the N8010 will support usb otg ethernet..

Somewhere I have found that its related to kernel, does your kernel support it? Or what should I do?

Thanx in advance.
[Galaxy Note 10.1 Android Development] andip71:
Pffffffffff... I honestly do not know. I do not have OTG Ethernet equipment, and I have not enabled anything for it specifically.

So first question is: Does the stock kernel support it? If yes, then Boeffla also has it. If not, I would need to investigate on it first.

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
OK, thanx for such as fast response. I'll check that out and then I'll be back here.

Thank you.

//UPDATE//

Btw, I searched google, and Ive found that stock kernel shouldnt support it (see here) aslo, there is mentioned how to implement it...
[Galaxy Note 10.1 Android Development] andip71:
... which is only how you enable it in the rom dialogs. Nothing about any required kernel configuration however.

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
Yeah, u're right. But Ive found another info how to set this up - eg, how to implement driver to own kernel with. Maybe it's little bit familiar for you, but for me it's totaly out of my focus :(
[Galaxy Note 10.1 Android Development] andip71:
Well, that is looking rather simple now.

I can try to build a test kernel for you if you want, as I do not have the hardware as I said.

Then you could play and try and test...

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
That would be wonderful! I really appreciate this!

It's not so hurry, I'll be at least one month out of my home, so if you can do it about 1 month, it will be great, and please use the kernel driver for AX88772B.

Then I'll test.

Thanx again buddy :good::good::good:
[Galaxy Note 10.1 Android Development] andip71:
Well, could have sent you a test kernel in 30 minutes if you had time :)

What I need for sure is: What kernel do you need? The n8000 or n801x one?

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
Wow, that's so FAST :)

Unfortunately I dont have my N8010 with me, so I can test it later. But I'll let you know how I tested it.

So the device is GT-N8010.
[Galaxy Note 10.1 Android Development] andip71:
Ok, then please let's do it like that: Once you have time and the device and are ready to test, please ping me again and I will build it for you.

Cheers

Andi
[Galaxy Note 10.1 Android Development] djsmeegy:
Great! I'll ping you definitely!
[Galaxy Note 10.1 Android Development] Rongogo:
I can test it to on n8000, i am on your latest jb beta.

Ps. The fix permissions works wel, and i prefer to start with a clean init.d folder, after flashing the kernel. (It's in your app, great)

Some other custom rom tweaks, that are installed with a clean install from a custom rom, can conflict some times.

Rongogo
[Galaxy Note 10.1 Android Development] andip71:
Will come back on this to you. I ordered an USB-Ethernet adapter with Amazon a few minutes ago (can use it on my Rikomagic system as well afterwards). So I can give it a try maybe even before the end of this week and let you know...

Tx

Andi
[Galaxy Note 10.1 Android Development] Rongogo:
Edit previous post.

OTG Works on mij n8000

128Gb usb

<6>[ 3547.810486] c0 otg px_usb_otg_en : 1

<6>[ 3547.810555] c0 usb_switch_set_path: 0 current_path before changing

<6>[ 3547.810661] c0 usb_apply_path: current gpio before changing : sel0:1 sel1:1 sel_cp:0

<6>[ 3547.810775] c0 usb_apply_path: target path 10000

<6>[ 3547.810849] c0 usb_apply_path: 10000 safeout2 off

<6>[ 3547.810927] c0 pmic_safeout2: onoff:0 No change in safeout2

<6>[ 3547.811009] c0 usb_apply_path: send "usb_sel" sysfs_notify

<6>[ 3547.813166] c0 Board : smdk_accessory_power (2,1) on

<6>[ 3548.055465] c0 usb 1-1: new high speed USB device number 11 using s5p-ehci

<6>[ 3548.259548] c3 usb 1-1: New USB device found, idVendor=154b, idProduct=fa05

<6>[ 3548.259743] c3 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

<6>[ 3548.259943] c3 usb 1-1: Product: USB 2.0 FD

<6>[ 3548.260063] c3 usb 1-1: Manufacturer: PNY Technologies

<6>[ 3548.260278] c3 usb 1-1: SerialNumber: AU33071FC0000023

<6>[ 3548.265939] c0 scsi2 : usb-storage 1-1:1.0

<6>[ 3548.315220] c0 host_notifier: start usbhostd notify

<6>[ 3548.315337] c0 host_notifier: host_notifier_enable_irq

<6>[ 3548.315503] c0 currentlimit_irq_thread gpio : 222, value : 1

<6>[ 3548.315636] c0 host_notify: ndev name=usb_otg: from state=2 -> to state=1

<6>[ 3548.316864] c0 [ ACCESSORY (acc_accessory_uevent,272) ] ACCESSORY=OTG : STATE=online

<5>[ 3549.268755] c0 scsi 2:0:0:0: Direct-Access PNY USB 2.0 FD 8.07 PQ: 0 ANSI: 4

<5>[ 3549.277483] c0 sd 2:0:0:0: Attached scsi generic sg0 type 0

<5>[ 3549.277791] c3 sd 2:0:0:0: [sda] 249999360 512-byte logical blocks: (127 GB/119 GiB)

<5>[ 3549.279251] c3 sd 2:0:0:0: [sda] Write Protect is off

<7>[ 3549.279417] c3 sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00

<5>[ 3549.281116] c3 sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

Rongogo
[Galaxy Note 10.1 Android Development] andip71:
Errm, yes, OTG via USB works as such. I see you connected a memory device, i.e. an USB stick. This is not new.

But the question was: Does USB OTG of an Ethernet adapter work as well? So you can connect to your network via a cable solution? This is what we will find out...

Andi
[Galaxy Note 10.1 Android Development] Rongogo:
Im not so fast :)

<6>[ 4545.490242] c0 [ ACCESSORY (acc_get_accessory_id,163) ] ACCESSORY_ID ADC value = 2729

<6>[ 4545.490332] c0 [ ACCESSORY (acc_dwork_accessory_detect,639) ] Accessory attached

<6>[ 4545.490410] c0 otg px_usb_otg_en : 1

<6>[ 4545.490457] c0 usb_switch_set_path: 0 current_path before changing

<6>[ 4545.490525] c0 usb_apply_path: current gpio before changing : sel0:1 sel1:1 sel_cp:0

<6>[ 4545.490606] c0 usb_apply_path: target path 10000

<6>[ 4545.490656] c0 usb_apply_path: 10000 safeout2 off

<6>[ 4545.490705] c0 pmic_safeout2: onoff:0 No change in safeout2

<6>[ 4545.490762] c0 usb_apply_path: send "usb_sel" sysfs_notify

<6>[ 4545.492876] c0 Board : smdk_accessory_power (2,1) on

<6>[ 4545.735256] c0 usb 1-1: new high speed USB device number 17 using s5p-ehci

<6>[ 4545.867948] c0 usb 1-1: New USB device found, idVendor=0bda, idProduct=8171

<6>[ 4545.868024] c0 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

<6>[ 4545.868078] c0 usb 1-1: Product: RTL8188S WLAN Adapter

<6>[ 4545.868115] c0 usb 1-1: Manufacturer: Manufacturer Realtek

<6>[ 4545.868155] c0 usb 1-1: SerialNumber: 00e04c000001

<6>[ 4545.995207] c0 host_notifier: start usbhostd notify

<6>[ 4545.995238] c0 host_notifier: host_notifier_enable_irq

<6>[ 4545.995290] c0 currentlimit_irq_thread gpio : 222, value : 1

<6>[ 4545.995323] c0 host_notify: ndev name=usb_otg: from state=2 -> to state=1

<6>[ 4546.005281] c0 [ ACCESSORY (acc_accessory_uevent,272) ] ACCESSORY=OTG : STATE=online

<6>[ 4546.960085] c0 mif: link_pm_irq_handler: gpio [HWK] get [0]

<6>[ 4546.961501] c0 mif: link_pm_irq_handler: gpio [HWK] get [1]

<6>[ 4547.010191] c0 mif: usb_port_resume: 1283, 4

<6>[ 4547.010942] c3 mif: IPC-RX(16): 7f 0e 00 00 0b 00 ff 09 07 01 03 ff 02 00 05 7e

<3>[ 4547.105281] c0 [HOTPLUG IN] check_up 1400000>=500000 && 265>200

<3>[ 4547.105365] c0 CPU_UP 1

<4>[ 4547.114324] c1 CPU1: Booted secondary processor

<6>[ 4547.114430] c1 notifier_call_chain : NOTIFY BAD tick_notify

<6>[ 4547.115195] c1 Switched to NOHz mode on CPU #1

<6>[ 4548.380251] c3 Atmel MXT1664S 3-004a: P: id[0]

<6>[ 4548.477293] c3 Atmel MXT1664S 3-004a: R: id[0] M[0]

<6>[ 4549.005143] c3 Atmel MXT1664S 3-004a: P: id[0]

<6>[ 4549.085633] c3 Atmel MXT1664S 3-004a: R: id[0] M[0]

<6>[ 4549.526062] c0 mif: link_pm_irq_handler: gpio [HWK] get [0]

<6>[ 4549.527587] c0 mif: link_pm_irq_handler: gpio [HWK] get [1]

<6>[ 4549.575288] c0 mif: usb_port_resume: 1283, 4

<6>[ 4549.576582] c3 mif: IPC-RX(13): 7f 0b 00 00 08 00 ff 09 07 06 03 64 7e

<6>[ 4550.014236] c3 Atmel MXT1664S 3-004a: P: id[0]

Rongogo
[Galaxy Note 10.1 Android Development] andip71:
Product: RTL8188S WLAN Adapter

So, you connected a WLAN adapter via USB OTG? Did it work?

Andi