yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] darkmage1991:
um. lol. i honestly didnt think of that, but i installed trickster mod and it says its disabled.

---------- Post added at 11:05 PM ---------- Previous post was at 10:38 PM ----------

ok i did a restore back to stock and it reads fine now... i then reinstalled cm11 and again it doesn't read, but i noticed now its saying device unrecognized... so i reads fine with stock rom but cm11 breaks that? i will try cm10 now and see if that breaks it for me also... cm10 did break it for me also...

---------- Post added at 11:35 PM ---------- Previous post was at 11:05 PM ----------

dont boither answering that last part. i just opened a thread in q&a as this seems to be part of cm11 issue not kernel. i have fixed this on my own, i booted into recovery after installing cm11 and re formated the data/cache/dalvik booted and now it works. not sure why it would. but hey i am not gonna argue with what worked :)
[Nexus 7 (2013) Original Android Development] Purplezigar:
I also noticed hiccups in games like Asphalt and Riptide with 103.1 and CM11. But otherwise this a great kernel. Thanks Tk-Glitch!
[Nexus 7 (2013) Original Android Development] skunks11111:
I know that it's a stupid question but is slimkat (from slim roms) aosp or cm based? I believe it's aosp but want to be sure...
[Nexus 7 (2013) Original Android Development] Grondinm:
AOSP
[Nexus 7 (2013) Original Android Development] Alex1911:
Kernel Bug ?!

Hey [MENTION=3847629]Tk-Glitch[/MENTION] i experience somthing strange with you Glitch-kernel 103r for AOSP.

My flo turned off unexpected and won't turn on, just the led blink 5 Times, in the meanwhile it turned on for about 10 seconds and showed it's loaded 1%+ battery, but then it turns off and it's now blinking again 5 Times.

Rom: 4.4.2 OmniROM-2013-12-24

Kernel: Glitch-kernel r103 for AOSP

CPU OC: all 4 core's to 2.0 GHz

GPU OC: maxed out 627 MHz

GPU Governour: Ondemand

EDIT:

The flo works now...wierd...

Anyone has a Idea, why this happend ? :confused:

Best Regards,

Alex1911
[Nexus 7 (2013) Original Android Development] darkmage1991:
seems to not be caused by this particular kernel. it seems to be a symptom for the n7 in general.

nexus 7 2013 will not power 5x led blink fbod death
[Nexus 7 (2013) Original Android Development] skunks11111:
The kernel seems promising, went through the aroma installer and chose stock but the device wouldn't boot... (Darkscreen)

So I had to restore from recovery and chose another kernel
[Nexus 7 (2013) Original Android Development] philosophics:
That's normal. Wait 2 minutes and then hold the power button down for 10 seconds. It will boot with glitch, don't worry.
[Nexus 7 (2013) Original Android Development] cryostasis25:
Been using this kernel and experience that when playing games like rc3, arma, riptide the upper part where the back camera is getting hot is it normal?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3939352]cryostasis25[/MENTION]

It's not the camera getting hot, it's the SoC (CPU and GPU notably), so yes this is normal, and it'll heat more the more you overclock.
[Nexus 7 (2013) Original Android Development] cryostasis25:
Oh ok thanks will underclocked my tab was a bit concerned.
[Nexus 7 (2013) Original Android Development] melander:
here is a pic of the insides of the n7 2nd gen

the upper part is where the board is located

which houses the cpu, gpu etc

heat is normal if the tablet is in use,

high cpu/gpu usage translates to heat

pic from ifixit site.
[Nexus 7 (2013) Original Android Development] darkmage1991:
did you try the cm11 version? if so you must use the 12/22 version of cm11 anything newer bootloops
[Nexus 7 (2013) Original Android Development] junowhoo:
If you don't mind me asking, But what Rom do you have sir and whats the gpu and cpu overclocked :eek:
[Nexus 7 (2013) Original Android Development] fxzy:
Anyone encountered Wifi issue using the latest v103 AOSP build?

Wifi can function properly when booting up. But after a night of idle, the connection is stopped and unable to turn on the Wifi again. That means I needa reboot to make Wifi working again.

Using the DJ KitKat AOSP build 15.
[Nexus 7 (2013) Original Android Development] animania260:
Haven't had any issues with WiFi here. Complete Stock ROM with latest Glitch AOSP.
[Nexus 7 (2013) Original Android Development] bland.life:
For the restore Aroma settings function, does it work if I update to a new CM11 version?

In CyanDelta I have the kernal flashable zip queued after the CM update.

It flashes CM then Glitch kernel.

I have Glitch kernel installed before the update.

Are the Aroma installer settings saved in another file that won't be erased on flashing ROM?
[Nexus 7 (2013) Original Android Development] gautampw:
Can someone explain what exactly this boost toggle does in mp_decision? I toggled it off and I see increased fps in my games, don't know what exactly going on, can someone explain?
[Nexus 7 (2013) Original Android Development] junowhoo:
Arr these settings good for daily use?

CPU OC: 1890 ONDEMAND

GPU OC: 545 ONDEMAND

Showp1984 msm-mpdecision
[Nexus 7 (2013) Original Android Development] Saythis:
If you don't mind that you're probably butchering your battery life go for it. Though I'd advise lowering the GPU since beyond about 490MHz provides very little if any improvement.
[Nexus 7 (2013) Original Android Development] Mrbobrowitz:
I just got my new N7 today. i went to install this kernel, seems to flash fine (all stock settings chosen in aroma) and it won't boot. It just stays on the Google screen.

Running 12/27 Nightly
[Nexus 7 (2013) Original Android Development] poondog:
Boosts the given CPUs that are online to those freqs upon touch. It leads to increased smoothness because it will boost without fail to 918MHz on two cores

did you happen to flash CM kernel on AOSP ROM or vice versa?
[Nexus 7 (2013) Original Android Development] Mrbobrowitz:
I flashed the kernel that ends in cm11 and am running the official cm nightly
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2454079]Mrbobrowitz[/MENTION]

For some reason, it seems that since 23/12 CM11 build installing my kernel leads to no boot, though I don't see any kernel change so I don't know what's wrong.. Unless the changes aren't yet publicly available. I'll search for clues.

EDIT : I think I know what's wrong. Anyone who did install the "r103" (available on XDA and Dev-host mirrors - my fault - T__T) will get no boot on CM11. I'll replace it asap with "r103.1", that does fix the problem by removing gamma settings. If you don't want to wait, just grab the r103.1 from the main download link in OP (Androtransfer).

EDIT 2 : r103 for CM11 previously available on both XDA and Dev-Host mirrors is now replaced by r103.1, that was only available on Androtransfer - Sorry for that, I was in a rush with Christmas and all.

[MENTION=4468902]Saythis[/MENTION] and [MENTION=5311831]junowhoo[/MENTION] (as it's some kind of answer for you as well)

Improvements are just as large above 490 MHz GPU unless you're hitting high temperatures leading to throttling (bad luck in this case). Throttling taken out of the equation, If you can't see improvements that's because of the apps your using. Most Android games are 30 FPS locked (or even lower) so you won't see any gain there for sure, but on 60 FPS capable titles there's a large performance gain running 600 MHz vs 500 MHz, basically giving 20% flat performance improvements if you're not CPU limited (50 FPS -> 60 FPS), thanks to the generous memory bandwidth available.

I wouldn't allow up to 627 MHz setting if I didn't verify that it is effectively interesting beforehand ;)

On the battery life side of things, it'll obviously suck noticeably more juice in games, but web-browsing/mailing/music etc. power consumption won't be affected too much (doing tasks quicker may even lead to less consumption in some cases). I'm running 2GHz CPU and 627 MHz GPU (with "Glitchy" L2/cache settings) for months and it's rare I need to charge the tab more than twice a week while using it daily for various tasks. Considering the massive performance gains versus stock clocks I prefer it that way as it's basically the battery life I was getting with stock kernel.

That's my point of view as a user, as dev, as tester and as hardware passionate.
[Nexus 7 (2013) Original Android Development] junowhoo:
Got another question guys? I so far love the performance from this kernel but i've noticed my charging status was the same as last night... At 85%? My flo says its charging but it wont go up any higher
[Nexus 7 (2013) Original Android Development] Purplezigar:
You lowered the max voltage for charging. When you went through the aroma installed there was one point where you could choose 4.3v, 4.2v, 4.1v, 4.0v. You must've chosen 4.1v because your only charging to 85%. I'm at 4.2v and I charge to 93%. This is meant to improve the battery longevity. So instead of the battery lasting, say, 300 charges, at 4.2v it will last about 600. At the setting your at it would last about 3x, or 900. (Those aren't the real charging cycle numbers, just used for an example.) It you want to charge back to 100%, just reflash the kernel and choose and different voltage. It will tell you approximately what percentage it will charge to on that page when it asks you.
[Nexus 7 (2013) Original Android Development] junowhoo:
Thank you purpleziger :D, so if you chose 4.1v and your battery goes up to 85%, it'll last longer
[Nexus 7 (2013) Original Android Development] darkmage1991:
anything newer than cm11 12/22 bootloops at the google logo flash cm11 build 12/22 than the kernel again
[Nexus 7 (2013) Original Android Development] junowhoo:
Hey TkGlitch, if you don't mind me asking what are the best settings to put in aroma launcher when your looking for daily use performance and battery life.. Thanks again for this awesome kernel
[Nexus 7 (2013) Original Android Development] hello247:
first kernel i've tried on my new n7. very pleased :)

using 2.0GHz CPU with 627 MHz GPU :D

Time to play and test this N7

Awesome work [MENTION=3847629]Tk-Glitch[/MENTION]
[Nexus 7 (2013) Original Android Development] Purplezigar:
The battery won't last longer in the day, but it will last more cycles. I would go with 4.2v. 93% is high enough to last all day or more, and it should double the cycles the battery is good for.
[Nexus 7 (2013) Original Android Development] hello247:
I've also set the battery extender settings to 4.2v and the n7 doesn't charge above 92 percent. Is that the intended behaviour?

I expected it to not charge above 93 percent. Any ideas?
[Nexus 7 (2013) Original Android Development] Purplezigar:
Yes that is what it should do. The person that made the tweak said about 93%. Mine has sometimes gotten to 94%, while others like you may get to 92%. There's nothing wrong if it only gets to 92%.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Supposedly, most balanced settings are the ones suggested by default in the installer as they are what I think is the best for most users. There's one exception though. All the S2W/S2S/DT2W functions will eat more battery for a varying usefulness, depending on the user, so this part is up to you.
[Nexus 7 (2013) Original Android Development] junowhoo:
Thanks TK-Glitch... I'm actually overclocking at 1720Mhz, Gpu to 545, with the Battery Xtender to 4.2 and i'm having the most AMAZING Battery life and performance anyone can ever ask for:D... On Antutu, My Flo is better than the SG4!! I cant believe that lol!! Keep up the good work
[Nexus 7 (2013) Original Android Development] Fr33L4nc3r:
First of all, thanks for your work.

I'm looking for a CAF kernel with DT2W and yours seems the most appropriate ;)

One technical question though (maybe naïve) : using a smart cover (screen turning on/off), I would only use DT2W if my cover is not on the screen (ie screen timed out because of inactivity). Would there be a way to "disable" DT2W when cover is on the screen (tablet not in use) to avoid the touchscreen listening battery drain. Are the in-build magnet sending any useful info ?
[Nexus 7 (2013) Original Android Development] BAleR:
Video freezes with cm11 version of this kernel, on harmony rom, i think its from the overclock delvik option, but maybe i just overclocked to high. I know its not the rom though.
[Nexus 7 (2013) Original Android Development] sciphonic:
Just a fantastic kernel. I don't have everything quite maxed out but I'm just a hair off of 29,000 in Antutu. The best part is that I can dial it down to 1.7 GHz CPU and 320 MHz GPU my tablet is still smooth as silk but with amazing battery life. I only have to turn the GPU up to 450 to run San Andreas perfectly. My only request would be a 400 MHz GPU step. The heat from the GPU even at 450 is a bit much.

Amazing work and I'll definitely be sticking with Glitch.
[Nexus 7 (2013) Original Android Development] BAleR:
What rom are you running? And what was your cpu speed at the time of the test?
[Nexus 7 (2013) Original Android Development] sciphonic:
The most recent Sinless ROM. Actually the first time I've tried it but I'm liking it a lot. Has a slight speed advantage over CleanRom. Still just biding my time until we get a 4.4 version of Carbon.

My CPU was at 2.1 and my GPU was at 504. Performance gov for both while running the benchmark. At those speeds I get over 13k in Quadrant too haha.
[Nexus 7 (2013) Original Android Development] vince2008:
I have not set my CPU past 1.998 with tk-glitch kernel yet, happy with stock ROM for now.
[Nexus 7 (2013) Original Android Development] BAleR:
Harmonyrom

First 2 cpu's at 1.944 2nd 2 at 1.8 gpu at 545, but had isseues with video playback for some reason.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I don't have a lid to try but Flar2 released a patch I did include in my tree : https://github.com/Tk-Glitch/Glitch_Flo_AOSP/commit/00244c23c1c05a5ee20ed6b0916a168ab709e860

So it should already be in effect ;)

Looks like an issue with CAF base as it doesn't happen on AOSP. Also happening on my Galaxy S4 only when running CM11. I wasn't able to track down the issue, so let's hope someone will find what's wrong at some point.
[Nexus 7 (2013) Original Android Development] BAleR:
Ya, i just saw someone just posted the same issue in harmony roms thread, im sure itll get sorted out. Thanks for the heads up.
[Nexus 7 (2013) Original Android Development] gnotelover97:
Do you run San Andreas on the highest settings?? How is the FPS. My Nexus 7 lags like hell on stock ROM and kernel. Can you upload a video running SA.
[Nexus 7 (2013) Original Android Development] superleeds27:
Tapped out keeps randomly force closing. Attached log
[Nexus 7 (2013) Original Android Development] IAmReflex:
What gamma settings are you guys using? I'm using fauxclock
[Nexus 7 (2013) Original Android Development] nokiagye:
The kernel don't have gamma
[Nexus 7 (2013) Original Android Development] hello247:
my device reboots when i doing a benchmark for fun. it reboots when doing the cpu float part. am i right to assume this is due to me overclocking the L2 cache to the max to glitchy configuration?
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
This is going to sound completely ignorant but I need to know before I proceed and every time I try to open the search function, tapatalk is FCing.. I'm assuming that AOKP is AOSP based, correct? I don't want to flash the AOSP version and then find out that AOKP is CM based. Any help is greatly appreciated.
[Nexus 7 (2013) Original Android Development] farenteria:
It should be. It stopped being caf-based on 4.3
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Lol, I'm using 4.3 for the tablet ui features..
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
The AOSP kernel does. The CAF kernel doesn't as it breaks boot on it.

From my testing it's happening on CAF base mostly (can't remember ever having that on AOSP base), and there's two things that may fix it while sticking to your L2/cache settings.

- First one is to change CPU voltage (in my case I did need to undervolt all freqs -75mV, but you may need to add some voltage).

- Second one if it didn't work is to lower your CPU overclock one step.

Though Antutu's CPU float test was the only thing unstable for me and nothing else ever crashed on me, even much heavier (but different) CPU loads. It just feels like CAF base is still very buggy.

Here's the error :

Fatal signal 11 (SIGSEGV) at 0x00000004 (code=1), thread 6936 (Thread-640)

It means the process tried to access an invalid memory zone (one it doesn't have the authorization to access, or one that is just corrupted).

It's either a game bug (if it's cracked, could be a malware) or an overclocking instability, and in this last scenario it would most likely be unstable RAM or bus (from L2/cache OC).

If you didn't OC then it's the game (or the crack).
[Nexus 7 (2013) Original Android Development] hello247:
I'm using the aosp based kernel, I'll give your suggestions a go and see.

EDIT: I tried reinstalling the kernel but this time using my decision (stock) instead of msm_mpdecision and wiped cache and benchmarks runs now at 1.7ghz to 2.0ghz. Strange but I'm happy.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Nice :)
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Just wanted to post this so everyone can see it: if you are using a 4.3 AOKP ROM or AOKP based ROM you need to install the AOSP version. When you reboot you will see a major distortion and pixelation of your background and it may seem like the kernel is incompatible, its not. Reset your wallpaper and use Trickster Mod to set all the pertinent settings and you'll be good to go. I tried a few variations of settings and versions thinking they were incompatible because of the wallpaper issue before realizing it was the wallpaper and not the kernel. Have yet to reboot to see if the issue arises upon each reboot, but even if it does, resetting the wallpaper will fix it.
[Nexus 7 (2013) Original Android Development] timbohenry:
Hey there. Just got the n7 today and rooted it right away. I'm planning to flash this kernel tomorrow, primarily to save charge cycles over the stock kernel. I'm curious about differences in performance compared to stock, but I'm not planning to game a lot. What i want is rather a long battery life and stability. Could you suggest settings that give me extended battery life and equal or marginally more power?

Thanks for the support!
[Nexus 7 (2013) Original Android Development] SickBeast:
I feel somewhat silly saying this but I am only able to hit 1.7ghz with full stability. I left everything else on "balanced". It's noticeably faster but I was hoping for 2ghz.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
I am at 2106 and running smooth as silk. Max 2106 min 384 set to interactive. My benchmark went up by 4k too ;)
[Nexus 7 (2013) Original Android Development] SickBeast:
What rom are you on and what settings did you use?
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
I'm running a milestone version of AOKP 4.3 I've messed with all the settings so much I would have to check them all to give you my exact configuration
[Nexus 7 (2013) Original Android Development] SickBeast:
Perhaps it's because I'm on stock kitkat with art enabled.
[Nexus 7 (2013) Original Android Development] SwoRNLeaDejZ:
Could be the culprit... As soon as there is a KitKat ROM that has tablet UI I'm going back, but that's a deal breaker for me.
[Nexus 7 (2013) Original Android Development] hello247:
try underclock ur max freq to 1.5ghz. And underclock to 320 as you wouldn't be gaming. Turn off s2w and d2w too.

Maybe undervolt too but be warned you may experience instability if u undervolt too much.
[Nexus 7 (2013) Original Android Development] matcho13579:
I don't think so, I can change gamma in FauxClock app while running Glitch kernel
[Nexus 7 (2013) Original Android Development] SickBeast:
I have to say that I really appreciate the op and I think that this kernel is fantastic. I just think it's counter intuitive to name this kernel "glitch". I don't want any glitches on my tablet lol.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4097733]SickBeast[/MENTION]

Well that's the point, It's a joke :P

Though it is not totally without reason. The kernel can be stable and fast and all, it's still a work in progress and I'm not fully satisfied with it, plus I did make some very experimental things in the past (i9000 users will know what I mean) and I really want to do such things again on the N7 at some point.

Also, my kernels are always offering many personalization options aimed at power users, so this name may stop not enough confident/experimented users from using them.

I'm happy you like my work. Thanks man.
[Nexus 7 (2013) Original Android Development] SickBeast:
lol

I have yet to experience any glitches. Thanks again. :)
[Nexus 7 (2013) Original Android Development] hello247:
Anyone see any difference using the stock mpdecision vs using the msm_mpdecision?

They seem pretty identical to me.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3563924]hello247[/MENTION]

Showp1984's msm_mpdecision is trying to mimic stock mpdecision (so it's made to be close/identical in some ways) but at the kernel level, when Qualcomm's implementation is binary based (you know, this file in system/bin/...).

An in-kernel implementation improves global performances of the hotplug driver while lowering power consumption. That's why I'm suggesting it as default in the installer.

Now, as it's faster to make decisions, the CPU could have a hard time following the rythm at a given overclock and may be less stable than with the slower, Qualcomm's binary way of hotplugging cores. Most users shouldn't feel a difference in a bad way as I did use a few tricks to help the chip to keep up, though, as I've learnt with you there are exceptions.

Now that I know about that, I'll try to make it a bit more relaxed, yet faster than Qualcomm's implementation..

That should be glitchy enough to be releaseable :p
[Nexus 7 (2013) Original Android Development] nokiagye:
The faux app with glitch.. this is not gamma
[Nexus 7 (2013) Original Android Development] nokiagye:
The faux with faux kernel

This is the gamma the second
[Nexus 7 (2013) Original Android Development] bcvictory:
I'm pretty sure faux has not open sourced the gamma controls. Only the basic colours.
[Nexus 7 (2013) Original Android Development] nokiagye:
No I find the source somewhere on net
[Nexus 7 (2013) Original Android Development] bcvictory:
Post the link?
[Nexus 7 (2013) Original Android Development] hello247:
I found out my n7 discharged from 50 to zero percent overnight. I was certain i had no applications running. When i switch it on it flashed white led. So i decided to charge it fully and luckily it powered back up.

Could this is happened because of the battery extender 4.2 applied?

Anyone experience this?

I'm thinking of charging my battery fly to recalibrate it.
[Nexus 7 (2013) Original Android Development] nokiagye:
OK I search

---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------

Here you go http://xdaforums.com/showthread.php?t=2108175
[Nexus 7 (2013) Original Android Development] bcvictory:
For nexus 4. Not nexus 7..
[Nexus 7 (2013) Original Android Development] nokiagye:
Where say that is only for 4 ? it's a patch I think is universal... I don't know maby..
[Nexus 7 (2013) Original Android Development] matcho13579:
What? You're making kernels for i9000? I'd love to see Glitch kernel on my i9000 :)
[Nexus 7 (2013) Original Android Development] tibere86:
Been running the r103 AOSP version with helicopter88's Openmaster build using default Ondemand and show's mpdecision. Was bored and decided to switch to SmartMax. Why isn't this governor default!? It's a great balance between performance and a much improved battery life due to it utilizing lower frequencies. I've fallen back in love with your kernel and wanted to say thanks again for your work.