yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] jordirpz:
Glitch, now with new kernel without patch for wifi, for me works fine my wifi now. Thank you very much sir

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] hagensieker:
Not sure your configuration but the same thing happened to me. Couldn't figure out what to do. Fortunately I installed kitkat and made a nandroid backup, then installed an older version of glitch then made a nandroid.

After applying glitch r62 over the other one I couldn't get wifi to work. Restored to my stock kitkat and installed r62. Works like a champ. Loving it.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3299331]timrock[/MENTION]

Now I got it. You'll need to download the latest official image (as cwm zip if you have cwm, or restore it with the toolkit if you don't), then flash the kernel. I think I have seen a patch to revert dePRIMAtor floating on the forum, you could try that before restoring if you find it. As it is now, your rom is using 4.3 wifi driver instead of stock 4.4 (that was a workaround till we got sources from Google), so you need to restore this in its normal state if you want to use latest kernels like my new one.

I hope it'll be clearer now ☺
[Nexus 7 (2013) Original Android Development] cLeAv0:
Can anyone post the patch to revert? can't seem to find it.
[Nexus 7 (2013) Original Android Development] timrock:
i went ahead and flashed the official 4.4 rom and then flashed your kernel. All went fine.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=3299331]timrock[/MENTION]

I'm happy your got it sorted :victory:
[Nexus 7 (2013) Original Android Development] :
I'm flashing glitch kernel via multirom twrp on my secondary rom but at the end of the aroma, the screen turns black and when i boot into the rom i discover the kernel hadnt been installed. What am i doing wrong?:confused:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4945966]Drunken_elk[/MENTION]

I'm not using TWRP nor multirom, let alone TWRP multirom :laugh: so I don't know what could be the problem..

Though, can you say exactly when the black screen is happening ? It may help me to fix the issue if it's on my side.

Thanks
[Nexus 7 (2013) Original Android Development] prstorero:
I'm assuming the kernel is insecure for all versions? I'm running the aosp non CAF and I can't get adb remount to work at all. Even after running adb root I still get denied permissions.

prshosting.org
[Nexus 7 (2013) Original Android Development] Grondinm:
That is an issue I have had with TWRP it is actually a known issues with TWRP and exiting aroma(I am pretty sure) I have not tried flashing a custom kernel on a secondary ROM but what steps are you using?
[Nexus 7 (2013) Original Android Development] meekrawb:
Did you turn off the screen timeout in the TWRP settings? Aroma should work properly if you do that.
[Nexus 7 (2013) Original Android Development] :
OK, actually it shuts when i press finish, i think it has something to do with aroma reboot feature, even though no file seems to be installed so there must be another problem behind

Edit: the steps are those normally used to flash mods for secondary roms advanced>multirom>select ROM>flash zip

2nd edit: btw awesome kernel, just flashed on stock and now my n7 does tasks immediately with 0 lag
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4945966]Drunken_elk[/MENTION]

It seems to be a TWRP problem as others as a few reported already. I won't make a custom recovery for Flo as I did before on other devices (some people might remember) as I don't have as much time, but I'm pretty sure it will be fixed at some point.

I'm glad you like the kernel, enjoy it ;)
[Nexus 7 (2013) Original Android Development] bland.life:
I tried the AOSP4CM kernel and it seems like the device has problem charging to 100%.

I can leave it charging overnight and it will be around 93~94%.

Switched back to the CM kernel and the device is able to charge to 100% again.
[Nexus 7 (2013) Original Android Development] Saythis:
From the original post:
[Nexus 7 (2013) Original Android Development] bland.life:
[MENTION=4468902]Saythis[/MENTION]

Does the CM-based Glitch kernel not have this battery life extender support?

Both kernels mentioned in my previous post are Glitch kernels.
[Nexus 7 (2013) Original Android Development] Saythis:
Well there's the option for it in the AROMA installer.. At least there should be. If you check it then it'll charge to 93-94%, otherwise it'll allow charging to 100%.
[Nexus 7 (2013) Original Android Development] bland.life:
I've left it at the default 93% during installation for both the AOSP4CM and CM Glitch kernels.

I'm not the trigger happy 'next' guy when it comes to installers :P
[Nexus 7 (2013) Original Android Development] PrinzEisenherz1:
What are the best settings for low battery consumption with this kernel? I use Trickser Mod app!

Thanks

Johnny
[Nexus 7 (2013) Original Android Development] coolek33:
MP decision off, intelliplug on, Eco on, screen wake control all off, TCP Westwood, harmonogram sio, buffer 1024, CPU min 270 max 1512, gov interactive... Thats my settings. 10hrs SOT.
[Nexus 7 (2013) Original Android Development] PrinzEisenherz1:
Thanks :D coolek33
[Nexus 7 (2013) Original Android Development] habylab:
To switch off mp decision, is it just the first enabled toggle in trickster, or all under mp decision? I've enabled intelliplug obviously.

Also, min freq always resets to 1ghz.
[Nexus 7 (2013) Original Android Development] coolek33:
Because MP is on. Go into MP decision and switch off first toggle.
[Nexus 7 (2013) Original Android Development] habylab:
I already mentioned that. Done that.
[Nexus 7 (2013) Original Android Development] somboons:
I am new. N7 member.How to revert to stock kernel?
[Nexus 7 (2013) Original Android Development] prstorero:
Reflash a stock ROM.

prshosting.org
[Nexus 7 (2013) Original Android Development] somboons:
How to set parameter for best performane and battery friendly?
[Nexus 7 (2013) Original Android Development] Gizoman:
Auto shutdown when sleeping

Guys I need an advice.

I am on stock 4.4 with the latest glitch kernel with default settings.

When I came home from work my tablet was powered off. I turned it on and saw an anomaly (see attached screenshot).

It seems like there was a temperature spike and the nexus auto shutdown. This was the first time something like that happened.

Should I be worried? What could be wrong and did anyone else had this kind of thing happened?

Screenshot
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
It's indeed the first toggle in the MP-Decision menu, though for the min freq it's a false reading of trickster, you can just ignore it.

[MENTION=4339680]Gizoman[/MENTION]

I've never seen something like that before.. 70C°+ for the battery would have killed it so it must be some false reading, though it's strange still as you're the first to encounter that as far as I know. It would be great if you (luckily) have a dmesg of this.
[Nexus 7 (2013) Original Android Development] somboons:
Can I use all MOD that install from the last versionr62?
[Nexus 7 (2013) Original Android Development] Gizoman:
Sorry but the log goes only 3 hours back, I was too late. Didn't even know of that log style. I will try to post dmesg next time if that happens again. Maybe there is some log style that is more time stretched that it would help you find the "problem" ?
[Nexus 7 (2013) Original Android Development] habylab:
Okay, thank you. Which do you prefer, mp or intelliplug?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
I prefer MPDEC myself as it feels snappier and faster overall and I'm still getting better battery life than stock, though the updates Faux is pushing for intelli-plug these days are interesting. It could have my preference at some point as it has been more battery friendly til now and the updates are bringing more performance and responsiveness (that's what I didn't like with it).
[Nexus 7 (2013) Original Android Development] habylab:
Interesting! Thank you, can't wait for the update then!
[Nexus 7 (2013) Original Android Development] yuyuyuyu1:
Is the file "Glitch-N7-r62.zip" for Nexus 7 (2013) "Flo" or the 2012 model?
[Nexus 7 (2013) Original Android Development] prstorero:
2013 would be flo.

prshosting.org
[Nexus 7 (2013) Original Android Development] yuyuyuyu1:
I know, so is the file "Glitch-N7-r62.zip" for the 2013 or 2012 model?
[Nexus 7 (2013) Original Android Development] Grondinm:
This kernel is only for the 2013 model none of them are for 2012(this thread is in the 2013 forum and it says flo in the tittle.....)

EDIT:

So latest CM Version V57 is very unstable for me. Cannot get antutu to finish. i OC to 1.7, GPU to 504 and L2 glitchy it will get all the way to the end almost then freeze and the tablet reboots. I did not play with UV yet but i might delv into that tomorrow. V40 works fine with those settings...

EDIT2:

Well now it's done it on r40 as well...seems to be temp related once i let it cool down it does run on r40 further testing tomorrow
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=842211]Grondinm[/MENTION]

It has something to do with floating point tests. CAF base reacts differently to them, and while it's giving more performance judging from the score, it's also harder to stabilize. From my own testing it's not so much heat related, and feels more like a current issue. Maybe some vdrop past a certain point..

Anyway the only thing that did help on my side was to tweak CPU voltage. In my case it was -50mV, and on my friend's device it was +50mV. After that every single antutu run was able to finish successfuly. Both devices were stable enough to run about anything else than antutu though.
[Nexus 7 (2013) Original Android Development] Grondinm:
is that -50mV across all freqs or only on max?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=842211]Grondinm[/MENTION]

All of them. If stability is lost at low freqs, just uV the two or three top frequencies.
[Nexus 7 (2013) Original Android Development] coolek33:
I UVed - 75mv all. But - 100 mv causes occasional reboots.
[Nexus 7 (2013) Original Android Development] Grondinm:
Sounds good. I'll do some playing around thanx for your work
[Nexus 7 (2013) Original Android Development] Nedlinin:
[MENTION=3847629]Tk-Glitch[/MENTION]

I'm looking at permanently installing my tablet into my car and have found what appears to be a few minor bugs in the kernel.

I've created a USB-Y cable and have the power coming from a wall wart. The cable then plugs into the hub on one side and the other plugs into an OTG adapter and into the tablet.

The bugs:

A) If I boot the tablet up and plug all the power into everything then plug the OTG adapter in, everything works great. However, if I plug the OTG cable in THEN boot the tablet, the tablet only seems to detect the hub but doesn't try to draw power.

B) If I plug the OTG cable in after everything is powered, things work great. dmesg of a working plug in: http://pastebin.com/jsHf726G

However, if I disconnect the power (I literally am flipping the power switch on the power strip that the hub and Y cable are plugged into..) then try to turn the power back on only the charging portion of the USB connection works. dmesg of power off then power on ~10 seconds later: http://pastebin.com/u9SFK3fB

The big thing I notice is that when plugging in the first time we get "<6>[38569.211303] The USB cable status = CHARGER_SDP" but after turning the power off then back on at the wall I get "<5>[39386.050933] smb345_charger: [usb_cable_type_detect] AC cable detect, disable wpc_pok, disable DCIN" and "<6>[39386.251220] The USB cable status = CHARGER_ACA"

If I disconnect the OTG cable from the N7 and then plug it back in ~3 seconds later it redetects everything once again and all works well.

Any thoughts? I'm hoping you'll have an idea of where to start. I'm a coder but have never touched kernel work... However, I'll be digging into this myself soon if you don't think you know the fix. Hoping you have some valuable insight!

EDIT: Also, Happy Thanksgiving :)

EDIT2: Should also say Im running r57 on CM10.2
[Nexus 7 (2013) Original Android Development] sciphonic:
After a fresh install of the 11/27 PSX rom I decided to check some benches with my tablet in the 2 ghz+ range. Appreciate your hard work man. May have been some heat soak involved but these are still the highest numbers I've seen on this tablet by far.

I'm also getting incredible standby usage. Pic attached.
[Nexus 7 (2013) Original Android Development] tritonesub:
It's also resetting to 1ghz min no matter what I do, and in CPU spy+ it does indeed seem that 1ghz is the minimum? Is there something causing it to misread like that? Just curious!
[Nexus 7 (2013) Original Android Development] russiandivxclub:
Thank you ,amazing kernel. One question if possible. Default minimum clockspeed is over 1GHz, I mean isn't it too much for idle device or I am missing something. When device is just not in use with screen off, is it using that minimum CPU setting or this is for something else. I see lowest possible setting is 162 MHz, isn't better to be as low as possible when in use, once again I am just asking because I don't understand why we need over 1GHz minimum clockspeed.

Thank you !
[Nexus 7 (2013) Original Android Development] coolek33:
No. It runs on freq that U set. Unless MP decision is on. Try to set the minimum to 270 in trickster and then close. It will stay there for a while. It resets after some time. But in info tab U can see how it runs (still 270 min). That's in my case.
[Nexus 7 (2013) Original Android Development] prstorero:
It's just a reading error with trickster. It isn't really that high for minimum.

prshosting.org
[Nexus 7 (2013) Original Android Development] leo81486:
please take a look in the video http://www.youtube.com/watch?v=CIhag1H5WCU&feature=youtu.be

i Had Flar2's kernel installed, ervything might seen to work on the video, but i forgot 1 thing .

as in the video i only unplug the power cable from the tablet, not the power source , well when i unplug the power from the power source , the tablet will be able to charge, but not able to detect the flash drive.

will u have a solution for this?

i really need it for car mount,

or maybe a coding to delay the tablet from drawing power imediately ? such a 5 seconds delay for tablet to draw power, than the flash drive can be able to get power first, than tablet draws power n charges.

thx
[Nexus 7 (2013) Original Android Development] phillysmako:
Loving the car for aosp version of this kernel hoping it continues....weather mpdec or intelliplug is used, this kernel is fast and smooth and snappy :) thanks glitch :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=1703496]Nedlinin[/MENTION]

Flar2's work did help, but the hardware is still weak. What you're encountering is most likely linked to the OTG charging hack. I did try some things after reading your post the first time but failed. I'll give it another go when I can. It should have something to do with the charger detection when the hack is enabled or something that is being reset at some point.

Thanks man.

[MENTION=5510946]leo81486[/MENTION]

You did enable the OTG charge hack right ? If you did, you must know that the power source is required in this mode, so your USB flash drive won't work without a power source. BTW I don't understand how the tablet is able to charge with the power source unplugged. My english could be at fault though.

[MENTION=5151336]phillysmako[/MENTION]

Busy days ahead still, but it'll continue for sure ;) Thanks !
[Nexus 7 (2013) Original Android Development] Nedlinin:
Glad you're also looking into it. Flar2 said he'd try and take a look at it soon.

I've also started testing a few things.. but I am a complete newbie to the Linux kernel so I don't honestly know how far I'll get..

EDIT: I'm at work now without my logs.. but, I think I found that the function static void id_pin_irq_work_function(struct work_struct *work) did not fire off after unplugging the power and then plugging it back in. This appears to be where host mode is setup/disabled.. so, I'm hoping to find a way to make it fire off properly.
[Nexus 7 (2013) Original Android Development] farmer bobathan:
Mpdecision boosts the minimum frequency to 1ghz for about a second when it detects a touch to improve responsiveness, it then goes back to 384mhz afterwards.

You can change the settings related to this behavior in trickstermod (I believe you need the donate key though).
[Nexus 7 (2013) Original Android Development] somboons:
Can I set manatic cover work with kernel?
[Nexus 7 (2013) Original Android Development] Grondinm:
Magnetic on/off works fine with this kernel. It can be disabled during installation if you so wish.
[Nexus 7 (2013) Original Android Development] somboons:
Thank
[Nexus 7 (2013) Original Android Development] cLeAv0:
Max frequency per core doesnt seam to work in aroma?
[Nexus 7 (2013) Original Android Development] KedarWolf:
4.3 Versus 4.4 Benchmarks

Hi,

When I was running a 4.3 ROM I got just over 27000 on AnTuTu Benchmark. Now with Kangs ROM on Kit Kat 4.4 using ART I'm getting just over 23000 on AnTuTu Benchmark. On a 4.3 ROM I was using ElementalX at 1.944 CPU, 538 GPU. This kernel I'm at 1.998 CPU, 600 GPU and getting the 23000. It's not the kernel though because I tried the latest ElementalX on Kangs 4.4 with my old settings stated above and only got just over 21000.

Anyone else notice KitKat with ART is much slower?

Peace. :confused:
[Nexus 7 (2013) Original Android Development] matcho13579:
Forget about benchmarks...
[Nexus 7 (2013) Original Android Development] farenteria:
From what I've read, ART will not improve speed of applications built on NDK. Benchmark apps usually are, so you most likely won't see anything great (or maybe lower) than a standard java app
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4615330]KedarWolf[/MENTION]

It's not ART. 4.4 gives lower benchmark scores (at least on antutu) than 4.3 on any device unless you're using the moto dalvik/bionic mod (ART disabled in this case).
[Nexus 7 (2013) Original Android Development] somboons:
This kernel can use in cm11 non-caf?
[Nexus 7 (2013) Original Android Development] somboons:
I have tested kernel with non-caf.working well
[Nexus 7 (2013) Original Android Development] KedarWolf:
Init.d Script Folder And Support?

Hi,

Am I correct in assuming init.d script files run from /system/etc/init.d instead of /system/init.d?

I need to know because a program that tests init.d support says it does not have it and I am using said program for init.d support instead but may not need to.

Thanks if you can let me know! :confused:
[Nexus 7 (2013) Original Android Development] matcho13579:
Yes, you're right
[Nexus 7 (2013) Original Android Development] commuterbox:
CM11 no boot

Downloaded and updated CM10.2 to CM11 no boot after installing r57, am I supposed to install non-caf kernel? Please help. Thanks
[Nexus 7 (2013) Original Android Development] TunedFish:
I flashed the r57 caf recommended, the aosp r57,and the r62 recommended for aosp and neither booted. The n57s gave me a black screen and the r62 gave me a graphical glitched screen. Just flash cm11 again (no wipe, no gapps) to revert to cm kernel or restore nandroid if you had one.
[Nexus 7 (2013) Original Android Development] bland.life:
Is Glitch currently the only CAF custom kernel for Flo?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2912951]commuterbox[/MENTION]

The CAF kernel is not yet updated for CM11. I'm on it, but I don't have much time these days so I can't say when it'll be ready.

[MENTION=3084173]bland.life[/MENTION]

DJlamontagne did make a CAF kernel along with he's CM based rom, but he did move to AOSP now, so CM and I should be the only CAF kernels publicly available indeed.
[Nexus 7 (2013) Original Android Development] jianada520:
Thanks alot for sharing kernel. I have been using your kernel for a week, and there's an issue i found. After using Glitch-N7-r62.zip, the power consumption wasn't stable on my nexus 7v2 (OS version 4.4). The battery percentage dropped about 20% and crashed when it was idling overnight.( the voltage was slightly decreased to 850). It might be caused by limiting Core max number to 1.
[Nexus 7 (2013) Original Android Development] coolek33:
I'm on it with slimkat and also using intelliplug. No issues here. 10 hrs of sot.
[Nexus 7 (2013) Original Android Development] Grondinm:
So will any version work with CM11?
[Nexus 7 (2013) Original Android Development] TunedFish:
No. Glitch doesn't have a cm11 version, yet.
[Nexus 7 (2013) Original Android Development] somboons:
http://androtransfer.com/?developer=TkGlitch&folder=N7-AOSP4CM
[Nexus 7 (2013) Original Android Development] TunedFish:
http://xdaforums.com/showthread.php?p=48219265
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Update for the AOSP kernel, with kitkat mr1 merge and Faux123 updates, along with some bonuses.

Enjoy !

10/12/2013 - AOSP update :

- Merged with kitkat mr1 starting at build r69

- Updated Intelli-plug hotplug driver, Intellidemand governor and FauxSound thanks to Faux123

- Improved network latencies

- Disable s2w/dt2w when magnetic cover is used - Thanks to flar2

- Enable sched autogroup (improves multitasking performance)

- Bugfixes

- Speed tweaks

Sorry for the CM11 compatibility delay, It would need some time I don't have yet, though it should be ready pretty soon now (at least at the end of this week).
[Nexus 7 (2013) Original Android Development] aamitabh28:
Thank u for what you do..take your time!

Thanks!
[Nexus 7 (2013) Original Android Development] PStephan88:
Why does slimport hdmi out not work with this kernel?
[Nexus 7 (2013) Original Android Development] matcho13579:
[MENTION=3847629]Tk-Glitch[/MENTION] How to make intelliplug setting to stick after reboot? I edited intelli_plug_active in sys/modules... but it won't... also I cannot see an option to turn off stock hotplug in FauxClock app..
[Nexus 7 (2013) Original Android Development] coolek33:
Then use trickster mod. It will set it when system starts.
[Nexus 7 (2013) Original Android Development] nikr123:
I don't have any slimport but I think they have been reported not to work on cm. I don't think glitch have removed the slimport functionality from the aosp kernels.
[Nexus 7 (2013) Original Android Development] heorung:
Does this kernel support android 4.4.2 yet?
[Nexus 7 (2013) Original Android Development] PStephan88:
As you see attached, slimport is working like charm on CM11 (like CM10.2) on CM's stock kernel. When using Glitch kernel, there is no sinal anymore! I really love this kernel. It provides great features, awesome performance (even "Vice City" on highest resolution runs lagfree) and is very customizable. Although my device "just" can handle a max of 2GHz CPU and 500mHz GPU... But I really need slimport for PlayMovies on TV, so I can't use Glitchy-ditchy-doo-kernel :(((

Maybe [MENTION=3847629]Tk-Glitch[/MENTION] himself knows any solution...
[Nexus 7 (2013) Original Android Development] stfudude:
I would like to know this too.

Currently I'm using tasker to enable intelliplug by running command after device booted

echo 1 > /sys/module/intelli_plug/parameters/intelli_plug_active

Edit: forgot to mention that I do have Faux clock app but I'm unable to turn on intelliplug with it. It gives a hint that mpdecision is maybe enabled so intelliplug can not turn on. With Faux clock app I can see that the cpu likes to ramp at 1026 mhz each time I touch the screen (similar behaviour with mpdecision) which might actually prove that mpdecision is indeed not turned off.
[Nexus 7 (2013) Original Android Development] matcho13579:
Script in init.d can do that too I assume

Yeah, I got the exact problem like you. No option to turn on/off the mpdecision
[Nexus 7 (2013) Original Android Development] stfudude:
I know that but maybe it will be cool if I can actually control it by Faux clock app.