yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] drewski_1:
It will wipe the partition(s) you do f2fs on. Internal SDCard is part of /data so will be wiped so back that up
[Nexus 10 Original Android Development] fischwrap:
Groovy. Thanks. And thank God for USB otg! I successfully formatted and installed the ROM from my USB drive. Now to set this puppy up!

---------- Post added at 11:06 PM ---------- Previous post was at 10:16 PM ----------

Well... Not going so well lol. Stuck at the Google splash screen for some minutes. Hopefully she boots
[Nexus 10 Original Android Development] tathagatab:
I'm using the April 18 kernel on the latest Chroma ROM (5.1.1) without issues.
[Nexus 10 Original Android Development] vesati:
Probably a stupid question, but can I flash this kernel over the stock 5.1.0 ROM?

Has anyone tried that already?
[Nexus 10 Original Android Development] leninke:
I use it with Purity. It's AOSP based, so you can flash it also.
[Nexus 10 Original Android Development] tavocabe:
Hello everyone.

Is there a safe way to overclock GPU? I remember this being discussed and khaon considered but never heard about it after that. Sometimes I get stutters in the UI even though I'm running at 2.1Ghz and using F2FS, maybe I'm just so used to my N5 everything else seems a bit slow.
[Nexus 10 Original Android Development] OmniSlyfer:
Hi guys, after a week of use it's time for a complete feedback about this ROM (build 18/04/2015), installed after a clean flash.

1. Let's start with ROM performances: outstanding. I don't know if it is the new toolchain or what, but the overall experience is fantastic, everything is very smooth, without lags of things like that. Nice job!

2. Continue with the biggest problem i had with this 18/04 build: the impossibility of surfing the internet with the browser. I've flashed the ROM twice, tried different gapps and different browser: nothing to do. Whenever I try to search something on google, the browser (and other browsers i've tried) simply fails to load the pages. The loading bar stops halfway, and no matter how much time i can w8,, no browser will never load a single page. Maybe is it a System Webview problem? Because I can use Play store for example or play games that require internet connection. I also had got this problem with 4/04 build. Now i've flashed bach 27/03 build and everything is fine.

3. I saw that the Rom has lost a lot of nice features compared with March builds:

- It's no more possible to reduce navbar height

- It's impossible to change or delete quick pulldown options

- It's impossible to change quicksettings tiles and position

4. I've also noticed that there are option related to Mobile data connectivity... But our N10 hasn't got a SIM slot at all, so what's the sense of these options?

I saw that a new build is online... Have u fixed some of these problems i've foud?

PS: i'll make a donation after the end of exams session ;)
[Nexus 10 Original Android Development] coalee:
The new build (04-27)?.. I cannot wait to try out. Is it RRO compatible?
[Nexus 10 Original Android Development] Khaon:
1. It is not only tied to the toolchain used but also because of the aim to take the advantages of option you can pass to the compiler. The goal is to take the most advantage of the nexus 10 architectures. UBERTC is basically GCC's upstream patched with google's patch and few linaro's.

2.By default, the android build engine is not really optimized and kinda generic(which is understable due to the sh*tload of devices that are built with it).

The downsize of trying to be more specific and enable more optimization is that some part of the code may succeffully compile but are broken and do not behave as it should : like with UI libs that leads to crashes when opening an app. Also your utilisation(your software yo use, etc.) may lead to FCs while I will never experiment any hehe... Was it 270/03 or you wanted to say 27/04?

3. Interesting, I do not use those so couldn't notice that :P. I will look over that

4. Yeah someone has cherry-pick a cm12 commit that make appear mobile connection. Do this appear also on cm12 nightlies?

Yes it is rro compatible (layers 2.1)! I haven't taken the time yet to upgrade the changelog, but basically, it is only fixes, no new real features.

I am currently working on building with new GCC 5.1. I am running on my nexus 10 a GCC 5.1 build. Seems fine, will most likely upload it and a regular gcc 4.9 build in the few hours. They will integrate heads up notifications customization ( ported by @freak_97)
[Nexus 10 Original Android Development] Khaon:
Here is a quick changelog for the kernel:

f2fs upgraded to the upstream branch

few cherry-pick from 3.4.107 upstream and others devs (credits to them!):

SELinux: ss: Fix policy write for ioctl operations

seccomp: Replace BUG(!spin_is_locked()) with assert_spin_lock

nf: IDLETIMER: Adds the uid field in the msg

drbd: merge_bvec_fn: properly remap bvm->bi_bdev

writeback: fix a subtle race condition in I_DIRTY clearing

writeback: Move I_DIRTY_PAGES handling

slide2wake: Fix re-enable issue when pluggin in while screen is off

input: evdev: Move wake_lock_destroy call

VFS: Make more complete truncate operation available to CacheFiles

Merge remote-tracking branch 'common/android-3.4' into khaon-new

SELinux: use deletion-safe iterator to free list

subsystem: CPU FREQUENCY DRIVERS- Set cpu_load calculation on current frequency

gpu:mali:dvfs:reworked stock dvfs table

arm:midguard:fixed bus frequency for 533 mhz

kernel: add support for gcc 5

arm:midgard:decreased up threshold for gpu governor

vfs: check if f_count is 0 or negative

hrtimer: Prevent remote enqueue of leftmost timers

hrtimer: Prevent all reprogramming if hang detected

hrtimer: Set expiry time before switch_hrtimer_base()

sched/fair: Improve the ->group_imb logic

sched/fair: Revert sched-domain iteration breakage

sched/fair: Propagate 'struct lb_env' usage into find_busiest_group

sched/fair: Add some serialization to the sched_domain load-balance walk

sched/fair: Let minimally loaded cpu balance the group

sched: Change rq->nr_running to unsigned int

sched/fair: Implement fast idling of CPUs when the system is partially loaded

sched: Fix inaccurate accounting for real-time task

sched: Micro-optimize the smart wake-affine logic

sched: Implement smarter wake-affine logic

sched/idle: Avoid spurious wakeup IPIs

sched/__wake_up_sync_key(): Fix nr_exclusive tasks which lead to WF_SYNC clearing

gpu: made the gpu driver aware of input interactions: while interacting with the screen the gpu freq is set to 350 if current freq is lower than that for 150 ms. The interval to update the latest input interaction is 300 ms.

gpu:made the frequency scaling algorithm simpler

I have ported double tap to wake however I just need to fix something crucial ... The current driver is not aware when screen is on/off.. :D

I will add two steps to gpu's freq max probably 720mhz and one between the range of 533 and 720.
[Nexus 10 Original Android Development] ilciumbia:
Excellent Khaon, thank you so much!

Any news about battery gauge being stuck during discharge?...

Sent from my Nexus 10
[Nexus 10 Original Android Development] OmniSlyfer:
1. And I think you've successfully reached the goal ;)

2. Nope, I was talking about 26/03 build (it wasn't 27 sry), that is your last build with Sabermod compiler. This annoying problem started to appear with 04/04 build when you've changed compiler. I haven't tried 27/04 yet, i think I'll w8 for your next build... Maybe i was only unlucky, but it is strange considering how much times i've re-flashed rom, gapps etc...

3. yes they are, and probably other old features that I can't remember are missing

4. Don't know, I love your roms so I never tried cm12 :D

Another little thing: Runtime is still broken. I know the rom is very smooth and fast, but I hate to see a score of 300 in antutu benchamark XD
[Nexus 10 Original Android Development] coalee:
Khaon,

As you already been using OptiPop rom then would it be possible to use UBER-L kernel as well? I am personally own Nexus 5 and been using OptiPop rom & Uber-L kernel for a while now.

Cheers
[Nexus 10 Original Android Development] Khaon:
No, not really, as you said uber kernel is design for nexus 5 which is qcom hardware. Here we have samsung(with its exynos arch)
[Nexus 10 Original Android Development] ericp2:
optimizing on reboot?

Hi, i am running kernel from may 1st and optipop from april 27. I have noticed a strange behaviour on apps updates from playstore. It seems as if the app optimisation processus has something wrong with it. On reboot i get the 'optimizing apps' dialog on the apps that were updated, but somehow the playstore notifies me again on the same updates? Anybody else has seen this behaviour?
[Nexus 10 Original Android Development] stiggy2012:
Hi Khaon, firstly thanks for the work you're doing on the N10. Much appreciated. :good:

I noticed there is a new kernel in your Google Drive. What's new? Seems to be running fine on my N10, though I can't OC the CPU above 1.9Ghz without an instant crash!

EDIT: Holy cow, DTTW works! This is freaking awesome, thanks again!!

SECOND EDIT: DTTW works really well waking the tablet from standby, but double taps when the screen is already on will cause the tablet to go back to sleep again, which is a bit of a problem when trying to type! :eek:
[Nexus 10 Original Android Development] xrayk:
Re: DTTW

How did you select the DTTW function?
[Nexus 10 Original Android Development] Khaon:
Hehe we have enabled generic art flags to make optimized everything

Hehe from the experimental folder, it has d2w enabled by default. I am working on that. Beside that i have added 612 and 667 mhz freq step to the gpu. however 533 remains default max freq.

I was wondering would it be better to have a d2w/s or just d2w ? If we do a d2w/s well i would restrict the area in a particular portion of the screen (one of the corners)
[Nexus 10 Original Android Development] stiggy2012:
Personally, just d2w is fine. The screen will timeout after 30 seconds inactivity anyway!
[Nexus 10 Original Android Development] leninke:
Hi [MENTION=4577448]Khaon[/MENTION], first thanks for this amazing rom and kernel. How can I activate dt2w and the higher freq steps to the GPU? Thanks in advance.
[Nexus 10 Original Android Development] fischwrap:
Is it possible to disable the d2s? It makes typing very frustrating! Love the d2w though! Excellent work
[Nexus 10 Original Android Development] glockman4519:
What app do you recommended for kernel control? I didn't see anything posted in this thread or I would not have asked. Thank you much.

"Chance Favors the Prepared"
[Nexus 10 Original Android Development] tobitege:
I can recommend either "Kernel Adiutor" (no typo!) or TricksterMod, both on Play.
[Nexus 10 Original Android Development] tavocabe:
DTW setting doesn't show in trickster nor adiutor. Can't find GPU frequencies neither. Using kernel in testing folder.
[Nexus 10 Original Android Development] leninke:
Same problem here.
[Nexus 10 Original Android Development] Khaon:
Just to clarify things.

Any software that gives you control for kernel tweaking works on a "hardcoded" basis.

Here is an example with Kernel audiutor sources.

As you can see on this link kernel audiutor does only recognizes the path for hardcoded paths(which is the same for any other softwares like trickster or w/E).

For our device the path to the value is different.

=====================

about double tap to wake its gonna be most likely full yworking in one or two days MAX. so jut keep with stable builds.

There are only two solution to integrate our d2w or gpu overcloking in kernel audiutor or any other software.

Workaround like

making a sysfs entry with a known path(like for nexus 4 etc.)

Add to kernel audiutor the path for our device.

IMHO the second solution is my prefered. I will send a commit with GPU and D2W support for nexus 10.

The first solution would be more generic and universal but honestly I DONT LIKE workarounds.
[Nexus 10 Original Android Development] Khaon:
Ok DT2W seems working.

I have uploaded it in the testing folder

On this build DT2W is enabled by default. Here are the interresting sysfs entry path :

/sys/devices/platform/s3c2440-i2c.3/i2c-3/3-004a/slide2wake

1 to enable, 0 to disable

/sys/devices/platform/mali.0/dvfs_upper_lock

just override current text with you prefered frequency, you can overclock up to 667Mhz with 533 MHz default freq.

You need a root explorer to edit those file.

You can also use Aero Kernel that allow you to set up custom sysfs entry paths.

Also I have opened for kernel audiutor a pull request with those path for dt2w support. I guess in the next days it will be included.
[Nexus 10 Original Android Development] ricco333:
kernel in the testing folder bootloops, at least for me, at the Google screen, flashed back to 05/09 and everything working again.

awesome work, thanks

Erik
[Nexus 10 Original Android Development] Khaon:
I have uploaded a new version, this time the sysfs entry is located at

sys/android_touch/doubletap2wake
[Nexus 10 Original Android Development] Michael1101:
I flashed your newest kernel. So far so good. Everything is smooth. Dt2w only works for me for about 10 sec after screen is off. After that it doesn't work anymore.
[Nexus 10 Original Android Development] Khaon:
I think you might be using the former implementation I did. Try flashing the latest kernel I just uploaded on g drive.
[Nexus 10 Original Android Development] tavocabe:
For some reason I can't save the file, tried with different root explorers with root permissions. I copied it to the internal storage and was able to save it but when trying to move it back it says I have no free space left. Also I set up the entry en Aero but the value is not sticking
[Nexus 10 Original Android Development] Khaon:
You just have to edit the whole file to 667 for example. You might Have reboot with the 720
[Nexus 10 Original Android Development] tavocabe:
Thanks, I was able to save the file now, but how can I see the GPU frequencies? Aero shows them as unavailable. Also, the value resets on every reboot. What do you mean with reboot with the 720? Great work you are doing here Khaon
[Nexus 10 Original Android Development] tathagatab:
[MENTION=4577448]Khaon[/MENTION]

Just updated kernel adiutor, and it's showing waking controls :)

No GPU controls yet.

Hey, what about fastcharge? Pls don't forget fastcharge!

Thanks & cheers.
[Nexus 10 Original Android Development] ThatFrigginAzn:
Khaon, could you add support for swap ram or zram?
[Nexus 10 Original Android Development] stiggy2012:
Amazing work Khaon, d2w is working OK so far, but I think it could do with being a little more sensitive. Not sure yet though, it's still early days. Is there anything exposed under /sys so that I can tweak the sensitivity myself?

I've also been experimenting with dvfs_upper_limit (and dvfs_under_limit!), and found that for some reason I can't set the limit to 677Mhz. Running "echo 677 > /sys/devices/platform/mali.0/dvfs_upper_lock" as root from a terminal window returns $?=1 and catting the file afterwards shows no effect. Setting to 612Mhz instead works absolutely fine however! Personally I'm setting both dvfs_upper_limit and under_limit to 612 currently, and it makes the tablet MUCH smoother.

Thanks again for your work, it is much appreciated! :good: I'll send you over a few beer tokens once I've been paid myself, you definitely deserve it.
[Nexus 10 Original Android Development] tathagatab:
I tried this too, and yes, it's an improvement. But I have no idea what I did - could you explain? And how do I make the setting stick across reboots?

Thanks.
[Nexus 10 Original Android Development] stiggy2012:
"echo 612 > /sys/devices/platform/mali.0/dvfs_upper_lock" - Sets the upper GPU frequency limit to 612Mhz, increased from the stock 533Mhz.

"echo 612 > /sys/devices/platform/mali.0/dvfs_under_lock" - Sets the lower GPU frequency limit to 612Mhz, effectively locking the GPU at 612Mhz all the time.

You can also run "cat /sys/devices/platform/mali.0/clock" to see the current clockrate if you're interested.

I'm trying to figure out how to apply it at boot myself! I placed a script in /system/etc/init.d, but it doesn't seem to run at boot currently. I'm sure I'm missing something obvious, but Android development isn't something I'm very knowledgeable on. It's not a PATH issue, and permissions on the script are correct. Any ideas anyone?
[Nexus 10 Original Android Development] leninke:
I think it is possible to do with tasker
[Nexus 10 Original Android Development] Sage:
i take it F2FS is optionally with this? :)
[Nexus 10 Original Android Development] tathagatab:
Yes. You have to format your partitions to f2fs if you want to use it. Otherwise this behaves just like a normal kernel.
[Nexus 10 Original Android Development] Khaon:
I have uploaded a new build on gdrive. Few enhancement for dt2w when device entering in deep sleep mode.

GPU's voltage control is live. No apps that I know of has support for a defined freq table. So to edit current value you will have to edit the file at

/sys/devices/platform/mali.0/asv with any text editor that has root permission

[COLOR=Red]EACH VOLTAGE STEP MUST BE A MULTIPLE OF 25 !!![/COLOR]

I will look if i can submit to kernel audiutor support for that until that the easiest way is to use a simple init.d script that set your value up on boot
[Nexus 10 Original Android Development] Michael1101:
I don't see the new build. Last build from 5/12.
[Nexus 10 Original Android Development] Khaon:
Tonight or tomorrow I all have access o my computer. Will upload then
[Nexus 10 Original Android Development] Khaon:
it's up.

I have asked kernel audiutor dev to add add gpu voltage control based on the cpu voltage implementation...

I guess if the dev accept to do that it would be really easy for him.

If he doesn't, I'll try to make a patchset and pull request it to the kernel audiutor project( as its open source!)
[Nexus 10 Original Android Development] withoutme5:
Works with cm?
[Nexus 10 Original Android Development] Khaon:
Should be flawlessly. It dumps your current kernel to rebuild with underlying ramfdisk
[Nexus 10 Original Android Development] tathagatab:
I faced a number of problems with the May 18 kernel, like random lags & freezes, screen blanking, reboots etc. Went back to the May 1st kernel and everything seems better. Anyone else experience this?
[Nexus 10 Original Android Development] Khaon:
Hm interesting can you tell me the kernel version ? 3.4.107 or .67 ?? I am in exams and won't be able to fix anyway this before few days. No comp access.
[Nexus 10 Original Android Development] drewski_1:
5/18 kernel s 3.4.107

i'm seeing similar freezes and blank screens. i assumed it was some Super Alpha Xposed module acting up (like Gravity Box which just pushed a 5.1 compatible version), but will try rolling back the Kernel to see what happens.
[Nexus 10 Original Android Development] leninke:
I have the same kernel version, with Khaon's Rom, without Xposed. The only issue what I have is that, the battery percentage stick at 100%, when I reconnect from the charger. I don't have any reboots or sod. Gpu is overclocked to 667Mhz as well. By 720Mhz reboots almost immediately. That's strange a bit, with Ktoonsez's kernel I could overclock to 720Mhz. Further the kernel and the Rom just awesome :laugh:
[Nexus 10 Original Android Development] tavocabe:
Couldn't get the tablet to boot with any of the new versions (5/26 and 5/26 linaro), flashed back 5/18 and it booted fine. :D
[Nexus 10 Original Android Development] 2Kings:
26/5 didnt boot for me neither, no wiping
[Nexus 10 Original Android Development] b1g.p0ppa:
05-25 kernel did boot successfully for me. I re-installed [MENTION=4577448]Khaon[/MENTION]'s 5-11 optipop ROM. banks 5-24 gapps and supersu 2.46 as well. Cleared cache and dalvik also. Booted up just fine.

Looks as though Khaon has removed the 05-25 kernel from gdrive.
[Nexus 10 Original Android Development] Koopa777:
Same here. Using 5-25 on makeleg's Cm12.1. Boots and runs fine. I have noticed an occasional graphical glitch that might be related to the kernel, but other than that it's running fine.
[Nexus 10 Original Android Development] Khaon:
Yeah I broke my usb cable so I was uploading on the drive.

Current builds bring enhancements to dt2w and gpu controls.

Now you can edit for each gpu freq steps the down and up threshold, the gpu boost pulse duration, the boost freq value, min and max freq(from 100 to 720Mhz) and the voltage applied on each freq steps. That way it will give a better control over the gpu as our device starts to be hold.

There are two issues with current kernels builds :

1/ sometime kernel seems to fail booting

2/ doubletap driver goes in suspend mode sometime.

3/ 720mhz for the gpu makes my device reboots on default parameters(didnt try with higher voltage but this was not occuring on ktmanta!)

left to do:

maybe give the possibilty to define for the user the cache speed applied when X cpu freq OR y gpu freq is running. When your gpu's lock is at 400 mhz or more your gpu bus is set at 800mhz. The same occurs when your cpu freq is at 1100Mhz.

Anyway I will upload latest stable kernel build along with a new optipop rom build in the next few hours.
[Nexus 10 Original Android Development] ericp2:
home button not working and other issues

Hi Khaon,

i have installed the rom update from may 27. since then, i am seeing the following issues:

- home button does not do anything anymore.

- pull down from top of status only shows one row, no control buttons (wifi, etc), or settings.

- when waking up from sleep, i do not get the screen lock. if i set a pattern, i do get a screen lock though.

it is as if the file system may be corrupted? i am using f2fs for data.

any ideas? i would like to avoid to have to do a full wipe and reformat if possible... note i have tried to revert to previous kernel/rom, but nothing changes.

exact current versions:

kernel 3.4.107-khaon-kernel 18/05/2015

rom: optipop_manta_userdebug 20150526.235154

any help appreciated!
[Nexus 10 Original Android Development] Khaon:
You must do a full wipe(factory reset) to fix ROM issues.

Try flashing the latest kernel i put on standalone it behaves better
[Nexus 10 Original Android Development] ericp2:
Hi, bizarrly, even with factory reset, problems were still there. i realized i had forgotten to flash gapps again , and it's only then that the problems went away. Note also that battery discharging percentage seems to have improved as well, it was only going in large steps before. Also, but this is probably subjective, it seems that the tablet is running even better than before....

I have used the same kernel (not the one you suggested).

Anyways, this may help others with a variety of bizarre issues.... do a factory reset to start afresh!
[Nexus 10 Original Android Development] tavocabe:
I don't know what's wrong with my tablet but I couldn't get the new rom along with the new kernel to boot. Same error I got last time with the 5/26 kernel, boot-loops at the Google splash screen. Had to flash back to 5/18 kernel 5/11 rom. Also is anyone getting "Google Play Services stopped working" error? I think it started happening when the app updated to 7.5.71 version.
[Nexus 10 Original Android Development] ilciumbia:
Yes, I am! I tried clearing the GPS data and cache and it solves it for a while, but after some time the error tends to come back...

Sent from my Nexus 5
[Nexus 10 Original Android Development] tobitege:
Why is noone posting a logcat to help the OP? Also state which gapps you're using and if you tried others.

Examples:

http://fitsnugly.euroskank.com/?rom=banks&device=gapps

http://xdaforums.com/android/software/tk-gapps-t3116347
[Nexus 10 Original Android Development] tavocabe:
Is it possible to grab a logcat when you are bootlooping on the Google splash screen? Maybe a dmseg? I don't really know but I'll check it out. Also I don't think it's a rom or kernel issue, (GPS error) as it was working perfectly until last update.