yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] gravedigger76:
[MENTION=3847629]Tk-Glitch[/MENTION]

Have 2 quick questions if I can

I'm wondering if this is a small bug or as designed

I'm on CM11 with 121xp kernel

When setting up my kernel through aroma I picked battery life extender and set it to balanced 93%

I see it in my settings conf

Its in 99glitch init.d script

When I look at the glitch kernel log I'm not seeing that this setting is applied.

Does it just not echo it into the log file?

Here are my settings.conf 99glitch script and kernel log zipped up if you wanted to have a look?

https://copy.com/RKv8vZWryQJ2bKl

Second question

Since I'm on nightlies of CM I use cyandelta to flash delta updates

I have added glitch kernel to 'install after'

It goes like this:

Delta is downloaded

Reboots into recovery

Flashes ROM

Starts aroma for glitch

Now -

I go through initial screens and then say no to full install

What happens is that some settings like double tap and sweep are working but... I don't see settings.conf anywhere and settings like battery extender is not set.

Of course if I pick in aroma full install I see settings.conf and I presume all settings are applied (with exception of question 1 that I dont see I the log)

What I'm presuming is flashing update of the rom wipes away one of the comic files and by saying no to full install it doesn't bring it back... But then why are the other settings are applied like dt2w and swipe.

Where is that setting coming from if not from settings.conf?

I do not have any kernel control apps running like trickster or anything like that,

Thank you much. And let me know if there is any other logs or anything you need.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Right, it doesn't echo it to the log file indeed. I may add that at some point (as I have things to add in aroma it seems :p), though this log was more of a debugging tool for the scripts than anything else. Nothing reads from the log, so nothing to worry about.

Anything that wipes the settings.conf file (the location most likely, not the file itself) will kill the advanced options. I don't know if Cyandelta is always wiping /etc/* or if it's only in case something got updated in there, I may want to check that.. Anyway I was thinking about another way to keep user settings, as a system wipe will always kill it. Since all my variants settings are compatible with each other it would be nice to be able to keep them no matter what (atm, a partial installation in aroma will just not overwrite your previous settings.conf, but no backup is done). An auto-backup to the internal SD card may do it..

About the DT2W/S2S, default settings are hardcoded into the kernel itself. It does look like you're using the same settings as what's set by default :)

My pleasure. I don't think I need anything else, I'm pretty sure I've been able to understand your well explained problems, and I hope my answers will be clear enough (with my poor english).

I'll work on this as soon as I'm satisfied with the state of the two other problems I'm occupied with (a GPU downclocking related bug in the CM compatible variant and a rare cache corruption issue in the AOSP base).

All the best
[Nexus 7 (2013) Original Android Development] cryostasis25:
Dunno if this is a bug or not. Running cm11 nightlies using nexus media importer. Heres what happens im on stock kernel of cm11 when i plug my otg cable the led on the fd lights up and im able to transfer files using nexus media importer.

After i flashed the kernel i selected otg + otg charge then after restarted I connected the otg the led does not light up and it is not detected. Restarted the tablet while the otg is connected it would work and led lights up. I remember i reported this but dunno if it was on bruce cm11 build or on this kernel. Hope someone can help i think im just selecting a wrong option.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3939352]cryostasis25[/MENTION]

If you select OTG + OTG charge hack, you NEED to use an externally powered OTG cable. If it works as you want on stock kernel, then you should not enable the OTG charge hack, unless you want to charge the tab while plugging some other devices with an Y cable.
[Nexus 7 (2013) Original Android Development] marsaltito:
With latest caf kernel i experience blackscreen ,screen is off and must reboot(long pres power button) , default cm kernel is ok .
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
When does it blackscreen ? At boot ? On high load (gaming) ? On sleep ?

If it's on high load, it'll be fixed in next update.

BTW latest "CAF" kernel isn't CAF anymore. It's an AOSP based kernel made compatible with CAF roms. I'll obviously have to polish it so it works completely nice.
[Nexus 7 (2013) Original Android Development] marsaltito:
most time when wake from sleep , and sometimes while just simple browsing (delfin browser)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=1301700]marsaltito[/MENTION]

Overclock ? Undervolt ?

.......Log ?
[Nexus 7 (2013) Original Android Development] xI mEzMeRiZe Ix:
Is there anything I need to do before flashing this kernel if I'm coming from franco.Kernel on Flo? On my Gnex, I always remember having to fastboot flash system.img and boot.img when switching kernels because of changes Franco made with his kernel, but I don't know if that's necessary on Flo.
[Nexus 7 (2013) Original Android Development] marsaltito:
Im ready for more info+ log if that happens again .

I just reinstalled kernel with all aroma default options ex. Intelli-plug hotplug driver by Faux123 .
[Nexus 7 (2013) Original Android Development] matcho13579:
AFAIK no, I was using franco kernel too in the past until I found this kernel, there was no need to flash anything than kernel and I doubt it changed somehow
[Nexus 7 (2013) Original Android Development] farenteria:
It's recommended to dirty flash the ROM to make sure any optimizations made in previous kernel don't conflict with new kernel.
[Nexus 7 (2013) Original Android Development] animania260:
Yes you should re-flash stock boot.IMG and let it boot once when coming from Franco. His ramdisk changes can cause issues.
[Nexus 7 (2013) Original Android Development] poondog:
Shouldn't flash stock, flash the one from your rom
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Anyone know if PA is CAF or AOSP based? I think it is AOSP based just want to be sure..
[Nexus 7 (2013) Original Android Development] animania260:
They switched to AOSP while ago I believe.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
You are correct indeed :) thanks for the reply. For some reason, on PA I can't set the min frequency correctly. I think something inside the ROM is overriding no frills and trickster mod which is super irritating... And no I'm not using both of those apps at the same time but they are independently being overridden.. Lame.
[Nexus 7 (2013) Original Android Development] poondog:
You set it in aroma as something different? Try reflash kernel and select the min freq as the one you want
[Nexus 7 (2013) Original Android Development] :
I've actually been having problems with the min frequency sticking. I've set it to 162 Mhz but it keeps on reverting to 918 (which I believe is the touch boost freq?).

I've checked trickster mod and it shows that 918 has been used for 44% ( 2 hrs ) of the time while 162 only 4% (10 min) and with 2 hrs of deep sleep.

Am I missing something or is this normal?

Let me know if you need any logs and such!

This is a mighty fine kernel though and I'm very impressed :)
[Nexus 7 (2013) Original Android Development] poondog:
Mine did this too for a bit. Turns out that it occurred when I was on smartmax gov. Would only use 918 (boost) and 1512 (max) You using a gov other than ondemand?
[Nexus 7 (2013) Original Android Development] :
Yeah I was on smartmax, and thought it may be the governor so I changed to intellidemand to see if it resolved the problem. No luck though.

Is ondemand the only one that behaves "properly"? What was your solution?
[Nexus 7 (2013) Original Android Development] poondog:
I switched to ondemand. Solved it for me

It seems, according to show-p1984's git that the only real supported gov with msm-mpdecision is ondemand. Smartmax has its own boost values etc and may be interfering
[Nexus 7 (2013) Original Android Development] :
Thanks for the info! Makes sense to me.

[MENTION=3847629]Tk-Glitch[/MENTION] thoughts on this? Probably would be a good idea to note in the OP for others :beer:
[Nexus 7 (2013) Original Android Development] poondog:
Fixed the issue? That's why some developers don't include extra governors that are not made for this particular setup
[Nexus 7 (2013) Original Android Development] mus1mus:
Anybody here noticed performance drop fro 118-121 compared to 103?

Not a big issue. Though I noticed a very small difference from the 3 kernels. Used to top 29K+ on Antutu at 1836. Now dropping to 28 at the same clocks.

Also noticed the tab to be slightly hotter on the latest builds compared to 103 at idle/sleep..

This is no issue reporting as it might just be me having these. But anyway, 118-121 were smoother than 103 by a bit too. :confused:
[Nexus 7 (2013) Original Android Development] xI mEzMeRiZe Ix:
Well I'm on stock, so I'll be flashing the stock system.img
[Nexus 7 (2013) Original Android Development] matcho13579:
I'm using intellidemand and it's running fine
[Nexus 7 (2013) Original Android Development] yzweixy1029:
121 XP kernel‘s lag

Dear devs...I'm back again...

last time I reported the "Bzzzzzzzzzz" sound problem...and in your 118-121 kernels,this issue was perfectly solved...Quite thank you~~

However,another problem comes,when I updated my rom from CM11-0114-nightly to 0115 nightly,the stock rom has the "Bzzzzzzz" sound ,so I flashed the Glitch kernel...And no more the annoying sound...

But sometimes when I slide my lanuch page(Nova) ,it lags! And it is quite frequent...

Here is the video...but the video is only 30fps...so the lag is not very obvious...

http://player.youku.com/player.php/sid/XNjYzMzMzOTgw/v.swf
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Mine is doing it regardless of which gov I choose. I use performance or ondemand for benchmarks and stay on conservative otherwise and the problems persist.
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
Video quality is really crappy, we can't see anything obvious here.

Try with Allcast or Rec.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5392006]SwoRNLeaDejZ[/MENTION]
[MENTION=5163087]Protomartyr[/MENTION]

That's a known issue on the CM compatible variant. It does look like it's fixed in my last dev build, so you'll get your fix in the next update.

Though, for the few thinking they have an issue here when they only looked at the min freq in TricksterMod or CM performance settings, you should go read the FAQ in OP.

On this kernel you should NEVER try to set min/max frequencies from anything else than /etc/settings.conf (for min freq only) or Aroma installer, as it will interfere with the way it's applied already.

[MENTION=5559267]mus1mus[/MENTION]

Running CM ? Could be the result of the AOSP base versus CAF base, though you should compare the detailed scores to see what dropped exactly. About the heat at idle/sleep, if it's not completely equal to ambient temp, there's an issue.

[MENTION=5265482]yzweixy1029[/MENTION]

That's a known issue on the CM compatible variant. I'm working hard with testers to find the cause of this problem. I'll do my best to fix it. Though if it helps while you're waiting for the fix, I'm not able to reproduce this with the Google Experience Launcher. You may want to try that.

--------------------------

To everyone : I'm a bit tired of CM problems guys.. If I'm not able to fix the random performance drop on this crap I'll most likely just stop releasing CM compatible kernels soon (one or two more releases). It's a pain for me and I have zero support from my community so I don't see the point in suffering for nothing, as I'm not even using this poor rom, and won't use it ever again if it stays CAF based, especially on a Nexus device. Moving away from AOSP in favor of this buggy mess was a good move to kill custom kernel development. I understand why most independent developers drop support. Thanks CM.
[Nexus 7 (2013) Original Android Development] farenteria:
It must take a lot of work to maintain different versions of the kernel. However, there's a build out of CM (I think in the regular Android Development section here) that others have mentioned which doesn't use CAF. This should make it easier for everyone, and thanks for your awesome kernels
[Nexus 7 (2013) Original Android Development] yzweixy1029:
Quite thank you for your hardwork in the flo kernel. Your kernel really really enhanced our experience.Thanks

You mentioned that you will stop releasing CM compatible kernels soon. I understand how you must feel. But my English is poor and I still don't know the difference between CAF and AOSP...Okay I will figure it out by myself later...And I just want to ask that what rom you will still provide support...The stock rom?

Whatever thanks again~
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5265482]yzweixy1029[/MENTION]

If I effectively stop supporting CAF roms, my AOSP kernel is still compatible with all non-CAF roms, meaning stock rom indeed as well as AOKP, all AOSP roms, or even the few unofficial AOSP based CM roms around. In the end I think only official CM and maybe slimrom will be incompatible.
[Nexus 7 (2013) Original Android Development] Porobu:
Slimkat uses AOSP

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] :
My bad,I forgot to mention that I was using the latest AOSP Glitch kernel and Purity, with configuration done via aroma.

This fix applies to the AOSP one as well?
[Nexus 7 (2013) Original Android Development] SynnyG:
I think in the future there will be no more custom kernel for CM, this team is going to do shiit and also... Shiiit. I will switch to PA as soon as they will integrate hybrid engine and halo. Pa is based on AOSP that's true ?
[Nexus 7 (2013) Original Android Development] oadam11:
Yes. PA is based on aosp

Sent from my Nexus 7 2013
[Nexus 7 (2013) Original Android Development] gravedigger76:
There is even an almost nightly CM11 with AOSP kernel for those that want to stick with CM. I think CM team didn't do justice moving away on nexus devices to CAF. Not the best choice.

( http://xdaforums.com/showthread.php?t=2545197)
[Nexus 7 (2013) Original Android Development] ezas:
Let me put something positive here. One of the things I love about this kernel is how clearly the tweaks are enumerated in Aroma. Things like where the check boxes are flagged with stock - improved - balanced - fast - extreme, etc. Really a nice little extra touch you have added.

Looking forward to the coming update. Your work is really appreciated.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Thanks, that's good news :)

There's a little fix for AOSP as well regarding some stuck frequencies in some special cases, though the problem is different. You may want to check in the first tab of TricksterMod to make sure it's going back to your min freq at some point (without touching the screen, as it'll trigger input boost as you said) because if it doesn't, there's something else going on for sure. You may also want to try with input boost disabled. Also if it's not too much to ask, I'd like you to PM me with your results. Thank you.

[MENTION=3496777]ezas[/MENTION]

Thank you. I hope you'll like it even more after the overhaul I'm planning.
[Nexus 7 (2013) Original Android Development] crazyyyk:
Sometimes, when I install this kernel from TWRP settings.conf file is empty. Why is it happen? I had exactly same problem with elementalx kernel. I think problem is with aroma installer...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Did you disable screen timeout ? I mean, do you reboot the device normally after the flash, or by forcing it ?

I didn't get that in about 50 flashes, so it seems strange. What TWRP version are you using ?

Thanks.
[Nexus 7 (2013) Original Android Development] crazyyyk:
I use TWRP 2.6.3.1

My device shutdown automatically after I hit finish in aroma installer, after that I should turn it on by long press power button.

Where can I disable screen timeout? In TWRP settings? I didn't change any settings in TWRP.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Then it may be the problem. Yes it's in TWRP settings in "screen" menu. It's a box to uncheck.
[Nexus 7 (2013) Original Android Development] crazyyyk:
I will try it when the next version will be released.
[Nexus 7 (2013) Original Android Development] mus1mus:
All good mate. Did a full wipe. I meant clean everything and the issue was gone.

Still learning each parameter the kernel has to offer by the way.

And yeah, running Sinless ROM for Deb.
[Nexus 7 (2013) Original Android Development] marsaltito:
it happens to me on twrp 2.6.3.0 with screen 'off' in settings
[Nexus 7 (2013) Original Android Development] matcho13579:
Yeah, exactly the same thing happened to me yesterday, using TWRP 2.6.3.0, settings.conf and glitch script in init.d were empty after I flashed it
[Nexus 7 (2013) Original Android Development] marsaltito:
i have settings.conf and 99glitch files and NOT empty( they are ok ) , just after aroma black screen and must hold power to restart/start
[Nexus 7 (2013) Original Android Development] ezas:
This is my experience. I would need to long press to reboot, but the install was always successful.
[Nexus 7 (2013) Original Android Development] kingston73:
If I am on elementalX and want to try this is there anything special I need to do? Or the opposite, on this and wasn't too go back to elemental?
[Nexus 7 (2013) Original Android Development] jordirpz:
[MENTION=5068754]jordirpz[/MENTION] Tonight my led was on and my tablet has been sleeping like a baby with wifi enabled. Try to look for wakelocks, I'll do some testing on my other device.

Please Glitch, can you tell me how or where i look for wakelocks?

Sorry for my snoob question.

Thanks for all.

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] thunderger:
[MENTION=227267]glitch[/MENTION]:

Thank you for adding ntfs and exfat support. Now, my N7 is my new media player with miracast and "beta airplay" support. :)

I noticed that read ahead buffer set to 2048 instead auf 1024 gives me a better score. Now, I've set up my N7 values like my N4 values and both are very quick.

Perhaps you can port your kernel to N4 because there is no nice 4.3 CM kernel so I've to use 4.2.2 (CM10.1)... ;)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
You can use an app like wakelock detector =)
[Nexus 7 (2013) Original Android Development] sageDieu:
Better Battery Stats is also a good one, you can find it on xda for free.

Wakelocks will give you kernel or partial Wakelocks and they will list separately in your app. If you get a kernel wakelock then you want to show that to glitch/post in that thread so we can figure out if there's a problem with the kernel. For partial wakelocks they will usually point to an app like Facebook or something that is keeping the phone awake, and then you can kill or remove that app.
[Nexus 7 (2013) Original Android Development] jordirpz:
Thank in advance.

But if glitch tell me post ago that his n7 sleep same a baby, i think that the problem is a someone app that i have installed in my n7. Really?

Now i installed wakelock detector, and i ll see and coments results.

Enviado desde mi GT-I8160 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] sageDieu:
yeah if it isn't a common problem for all of us it is most likely that you have an app causing it. let us know what the results are after it sits for a while.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Remember it's using CM source as base (that isn't AOSP base anymore) and I'm NOT testing this kernel on AOSP based roms.

We do not know yet what kind of problems it could possibly generate on a non-CM based rom.
[Nexus 7 (2013) Original Android Development] El Nino1977:
I use your kernel on pa, works like a charm and sleeps like a baby.
[Nexus 7 (2013) Original Android Development] jordirpz:
Is tapatalk?

And is strange,because in my phone use tapatalk, and deep sleep work.

Enviado desde mi Nexus 7 usando Tapatalk 2
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's over nine thousand.

/troll
[Nexus 7 (2013) Original Android Development] killflaker:
Can you make test whit 3dmark and post screenshot?

You make this whit your actual setting? (1.9ghz 600mhz)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Sure :

(And yes it's 1.9GHz CPU / 600 MHz GPU indeed)
[Nexus 7 (2013) Original Android Development] Crwolv:
No worries man,was just trying to help ,some mods hate it. :)
[Nexus 7 (2013) Original Android Development] angieri918:
Works flawlessly on vanir! Favorite kernel so far! Great job Glitch
[Nexus 7 (2013) Original Android Development] Crwolv:
AWESOME!!!! CHEERS TO A GREAT GUY

---------- Post added at 02:51 AM ---------- Previous post was at 02:50 AM ----------

4096 works awesome for me,just letting ya know
[Nexus 7 (2013) Original Android Development] menissalt:
Tried both Vanir as well as CM 10.2 plain and followed you wipe and fix permissions instructions, never had a successful boot. It either loops or gets stuck on "optimizing apps" at boot and then boot loops.I've tried every step in between 1700 and up on both roms (took a really long time) but still couldn't get anything.

Also, every time I finish with the aroma installer when it tries to goes back to twrp the screen turns off and won't turn back on (sometimes if I wait a few minutes I can turn the screen back on and unlock twrp but normally I have to force it off).

You think maybe we can get a no aroma installer and just let us set everything up in Trickster?

::EDIT::

Interesting, after a factory reset in Vanir it's working.. now to test this with a higher clock.
[Nexus 7 (2013) Original Android Development] killflaker:
Thanks!

Wow, great score. Gpu overclock run good. Not too hot?

Good job :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Not at all. The two tabs I'm testing stuff on aren't suffering from thermal problem/throttling, but the best overclocker of the two (friend's one) even if it can use 2.2 GHz CPU and 627 MHz GPU at all times without throttling and much lower voltages is hotter than mine at same freqs/higher volts.

Some will have great overclockers with low temps, others with high temps, others will OC like crap with high temps even at stock or can't OC but very low temps..

One word : Lottery.
[Nexus 7 (2013) Original Android Development] nklenchik:
This is crazy, I haven't used a glitch kernel since my Samsung Fascinate days! Glad to see it on the nexus 7

Sent from my Galaxy S4 using Taptalk 4
[Nexus 7 (2013) Original Android Development] melander:
just dirty flash the kernel, it is fine

tried wiping cache and dalvik but did not see any difference there

so when i switch between elemental and glitch, i just dirty flash

even updating to a newer version, i just do the same.
[Nexus 7 (2013) Original Android Development] crazyyyk:
In aroma, by default, min freq for CPU is set to 384, BUT when I choose min voltage for CPU it set voltage for 160 MHz, not for 384! Is it normal?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5393801]crazyyyk[/MENTION]

Yes. I need to change that a bit, but it is normal.
[Nexus 7 (2013) Original Android Development] commuterbox:
To those having problems setting min frequency to stay you guys need to go inside mp decision control settings and change boost freq CPU 0 to the min frequency you like apply then viola it settings stay. Hope this helps that what I did

Sent from my Nexus 7 CM11