yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] MadMatt89:
Okay, I need your help guys.

I got my seccond Nexus 7 device today, cause my first one is broken.

Because I already know a lot about flashing and doing it for a couple of years I immediately started rooting + custom recovery without problems.

Then I flashed Slim-deb-4.4.2.build.2.8.RC3-WEEKLY-2917 + this 2.6 Kernel in one run (first the firmware, then the kernel).

At the end of the flashing process for the Kernel (Aroma installer already said success) the screen turned off and the device seemed off. And now I can't get it back on. If i try to boot it normally It's stuck at the Google logo with unlocked bootloader and if I try to press vol up+down+ power nothing happens and if it's connected to the PC a strange USB connection error sounds occurs.

Can please someone help me or is this really broken?

Thanks in advance

Matt

Edit: I have it working again, I got into the bootloader by pressing power and then after it turns on immediately pressing volume down. Is this the right combination? Vol up+down+ power is for what?

Thanks
[Nexus 7 (2013) Original Android Development] dy2592:
Read all your comments about the battery stuff. Great forum
[Nexus 7 (2013) Original Android Development] schlager:
power+vol up is boot to recovery

power+vol down is boot to bootloader
[Nexus 7 (2013) Original Android Development] GSLEON3:
Vol +, Vol - & Power is for safe mode.
[Nexus 7 (2013) Original Android Development] mfelten86:
This is my first kernel so i've been taking things slow, i decided not to use the trickstermod because it seemed too complicated for what i want to do. I was editing the elementalx.conf file though, and it won't save, in es and lidroid. I changed the permissions on the file to execute but it still won't save. Does anyone have any ideas of what could be causing this? (If this is the wrong thread let me know)
[Nexus 7 (2013) Original Android Development] sam298:
Hi, loving this great kernel. Have a question. I am using Trickster's mod to change the settings, but some settings like magnetic on/off isnt there in TMod. How can I change it after I had installed the kernel? Is there any other app out there, or can i manually change by editing some files?

Currently i am thinking of reinstalling the kernel so i can see those options and change. would be nice if i dont have to reinstall.

TIA
[Nexus 7 (2013) Original Android Development] imna357:
As always freaking GREAT KERNEL from flar2, been using his kernel with nexus 5 too... don't get me wrong I got a paid app from Franco and Trinity and trickster, but this guy is AWESOME... been using his kernel images at of my paid APP:sly:
[Nexus 7 (2013) Original Android Development] gppsoft:
Hello. Possible to change the color temperature at the bottom of the screen? I have yellow tint on bottom screen :(. Thx.
[Nexus 7 (2013) Original Android Development] ObiDanKenobi:
There is an elementalx.conf file that holds these settings, you can change that, you need root and the system mounted RW though. It is always simpler to flash it again and choose in Aroma.
[Nexus 7 (2013) Original Android Development] DAGASH:
can any one share a video to explain how to install ElemetalX properly for nexus 7 2013 wifi version , i am looking for ( 3g usb modem function ) .
[Nexus 7 (2013) Original Android Development] quickstang:
What do you mean by install it properly? Flash the zip in recovery, wait for the installer to pop up, click the I agree deal & then go through each screen & customize it the way you want. Then click yes at the end that you want to install & then your device will reboot.

Pretty plain and simple.

Sent from my Moto X
[Nexus 7 (2013) Original Android Development] deathblade:
Quick question will this kernel work with omnirom one do I have to find one that is for cm or the like
[Nexus 7 (2013) Original Android Development] quickstang:
I'm using it on omnirom

Sent from my Moto X
[Nexus 7 (2013) Original Android Development] MadMatt89:
I could not find the option for ntfs support while installing. Is this not supported anymore or how can I turn it on? I just tried to connect a hard drive which used to work earlier on another device with an older version of this kernel and it didn't work.

Thanks
[Nexus 7 (2013) Original Android Development] leo81486:
so wondering if Flar2 found a way to solve the OTG host n charge ?

thx
[Nexus 7 (2013) Original Android Development] genocide_ru:
Not sure if it is, but so far I noticed this issue:

Flashed latest version 2.6, no undervolt, overclocked a little CPU and GPU for games.

Selected ElementalX governor.

Now Play Music starts to hickup right after I turn off screen. Or if I do not touch screen when it is "On" for a few seconds.

Looks like Cpu freq for Play Music sets to 384 and it is not enough, probably, I can see it with CPU Spy app.

Can someone confirm or advice something to investigate this issue?

I'm quite new to this kernel settings stuff, and if I am stupidly wrong with my thoughts, then sorry ;)

PS: digged a little deeper:

Switched back to Ondemand, Play Music stopped to hickup with Screen On even it I do not touch it.

But it still hickups every minute or so when screen is Off, even with 1026 set by governor on screen off.

PS2: reflashed kernel to make sure I have no Undervolt.

ElementalX governor - music plays with hickups with Screen On/Off, uses 364 freq

Stock governor - music play with hickups only when screen is off, uses 1026 freq

Do I miss something?
[Nexus 7 (2013) Original Android Development] just lou:
I found that when using the ElementalX governor, the CPU rarely goes above 384 even when I'm trying to watch HD video. It's definitely great for battery life, but it causes some performance issues for me. It sounds like you need to stick with Ondemand, and turn off the option that limits the CPU speed when the screen is off.
[Nexus 7 (2013) Original Android Development] genocide_ru:
I tried few settings, even when screen-off freq is 1026 music is still choppy. While with stock kernel on the same freq it is ok.

So, looks like it is not frequency related, it is issue from another settings.
[Nexus 7 (2013) Original Android Development] MadMatt89:
anyone knows something about the ntfs support? Can I still get it somehow?
[Nexus 7 (2013) Original Android Development] ObiDanKenobi:
If you search some pages back you will see that there is support. You use StickMount and you will get readonly support. If you want to write also you have to disable selinux.
[Nexus 7 (2013) Original Android Development] MadMatt89:
And how do I disable that? What's the drawback of disabling this?
[Nexus 7 (2013) Original Android Development] ObiDanKenobi:
set selinux=0

The drawback is that you loose some security. Anyhow you can enable it after you are done with your stick.

set selinux=1
[Nexus 7 (2013) Original Android Development] Inverted.:
latest version of the kernal seems to brick my rom

running cyanogen mod 11 snapshot 3

didnt really change any of the settings other then over clock to 2.0

tried flashing twice
[Nexus 7 (2013) Original Android Development] MadMatt89:
Ah in a terminal emulator?
[Nexus 7 (2013) Original Android Development] nikr123:
You don't have to disable selinux totally you just have to put it in permissive mode.

This is from a file:

# enforcing - SELinux security policy is enforced.

# permissive - SELinux prints warnings instead of enforcing.

# disabled - No SELinux policy is loaded.

That shows the difference. You can install a app like https://play.google.com/store/apps/details?id=com.mrbimc.selinux or you can put it in permissive mode manually by getting su in a terminal and then do "setenforce 0" to turn it to permissive. You can re-enable it by entering "setenforce 1" if you feel like doing so.
[Nexus 7 (2013) Original Android Development] gabo_lope:
Cyanogenmod and roms based on it are not compatible with this kernel, since CM uses CAF on qualcomm devices, their sources are different than AOSP.

If you want a custom kernel try flashing glitch or any other CAF-based kernel
[Nexus 7 (2013) Original Android Development] Inverted.:
Wish I had known that before I flashed it and went through the Hassel.

Thanks
[Nexus 7 (2013) Original Android Development] M1cha84:
I am using the 2.6 Kernel and the Magnetic On/Off function seems buggy. Even if I turn it off, the display will still go off and on when I open and close my case.
[Nexus 7 (2013) Original Android Development] En Kee:
Everything is working well here.
[Nexus 7 (2013) Original Android Development] combatdeity:
Any chance of getting this patch added to the kernel?
[Nexus 7 (2013) Original Android Development] punkJD:
What will the battery extender exactly do?

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Original Android Development] cujo6801:
Not much in the real world.

You see your battery has a certain life span from 3 to 4 years

Depending on how many times you charge

what this does is limits the amount that can be charged to full or more specifically not to full... Lol

in theory making the battery last longer

but by that time you'll have a new device

Sent from the "DOG" pound
[Nexus 7 (2013) Original Android Development] Titchener17:
Yea got 3 devices out to post a normal sentence. Will let it be

---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
[Nexus 7 (2013) Original Android Development] punkJD:
Oh, OK. I thought it might increase battery life. If that's only that, then it's nota of much interest

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Original Android Development] Dan1234567890:
well, you must take in consideration that after 300-500 cycles (cca a year of usage, depending of your habits) your battery could drop to 80% of full capacity. If you use Battery life extender, i.e. on 94%, this drop in capacity would happen after 600-1.000 cycles. You can read more here if you are interested:

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

:good:
[Nexus 7 (2013) Original Android Development] yanpol87:
DVB-T

Hi!

Where can I find the DVB-T modules for ElementalX-N7-2.6?? Or how can I compile them if I need?

Regards!
[Nexus 7 (2013) Original Android Development] sapphire_pro:
Hi,

I searched the thread but could not find a clear answer for the question:

Can I use the elementalX Kernel 2.6 together with a current nightly release of Cyanogenmod?

If no, why is this combination possible with Nexus 5?

Regards

sapphire_pro
[Nexus 7 (2013) Original Android Development] flar2:
I never got around to compiling them for 2.6. If you download my source code and enable your dvb module in .config you will get a working module.

I haven't worked on this kernel for a few weeks (seems to be running great!) but I'll try to remember to build the dvb modules when I come back to it.

No, this doesn't work with latest cm. You have to use bruce's non caf version.

For Nexus 5, I wanted to test some stuff out on cm, so I made a cm branch of the kernel and released it. I may do the same for the Nexus 7 if I have time.
[Nexus 7 (2013) Original Android Development] uzzoo:
For which Rome is ElementalX-N7-2.6.zip suitable?

Only original Rom or Custom Rom (eg Slim-deb-4.4.2.build.3-OFFICIAL-3077, omni-4.4.2-20140113-deb-HOME MADE)

greetings uzzoo
[Nexus 7 (2013) Original Android Development] GialanG:
All AOSP based roms, such as Slim, Omni, Mahdi, Purity...
[Nexus 7 (2013) Original Android Development] uzzoo:
Thank you I will test the same
[Nexus 7 (2013) Original Android Development] sizzlers:
Personally i prefer glitch for gaming since i can UV the gpu and the smartmax governor is really a gem.Elemental may be good but not for gaming as battery drops way to fast .
[Nexus 7 (2013) Original Android Development] sapphire_pro:
Great info!

A question for that: Is it the same way flashing the ROM (bruce non caf version of CM11) + elementalX Kernel via TWRP or do I have to change settings etc.?

Kind regards

sapphire_pro
[Nexus 7 (2013) Original Android Development] GialanG:
Yes, it's the same. Flash non-CAF rom then EleX and you'll be fine.
[Nexus 7 (2013) Original Android Development] sapphire_pro:
Great, thanks!
[Nexus 7 (2013) Original Android Development] Nekromantik:
Does this work on Omni ROM?

I flashed it and gets stuck on Google boot logo.
[Nexus 7 (2013) Original Android Development] Larz2.2:
Yes. I have used it since Omni arrived for the deb/LTE.
[Nexus 7 (2013) Original Android Development] schlager:
[MENTION=4684315]flar2[/MENTION] did you have a chance to check out this issue?
[Nexus 7 (2013) Original Android Development] thisguysayswht:
went around the track, saw some good stuff, but this is something else....

#!/bin/bash
while :
do
echo "awesome"
sleep 0
done

Thanks flar2, Someone should give you a medal. Superbly exquisite kernel. Really glad you decided to start this.
[Nexus 7 (2013) Original Android Development] punkJD:
By overclocking to 1.7GHz will the processor life be reduced?

Or there any risk in overclocking this amount of GHz?

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Original Android Development] jugster:
Yes, the life will be reduced.

Yes, there is risk associated with overclocking.

Will something happen to you? Probably not.

Let this answer guide you and everybody else that ask that question.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] just lou:
It's highly unlikely you'll reduce the life of your CPU by over clocking only at 1.7GHz. It's only a small O/C, and the CPU in the N7 is pretty much just an underclocked Snapdragon 600 anyway. If you start pushing it over 2 GHz though, then there is some risk.
[Nexus 7 (2013) Original Android Development] jugster:
Overclocking reduces life of CPUs. Period. By a significant amount, probably not. But please do not say it doesn't. That is just plain wrong.

There is always risk with overclocking. Again, probably not by a significant amount.

Also, not all phones/tablets are created alike. Some are better overclockers, some are worse.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] just lou:
The risk is minimal if done within reason.
[Nexus 7 (2013) Original Android Development] jugster:
Indeed.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] crashercarlton:
I would like to point out however that i have always kept mine @ 2.0GHz with Elemental X Kernel and other than being a flashaholic of roms, i rarely use mine for any gaming at all, just web browsing and youtube (which youtube can make it hot). Point is, i now have the faded red area (when screen is dark) where the cpu has burned in the screen like many others. Some have had this with stock speeds, so be careful and if overclocking, try to undervolt as much as possible to keep my issue from happening to you.
[Nexus 7 (2013) Original Android Development] mus1mus:
1. Life Expectancy of a component is not always dependent on Overclocking. Plain fact is that, Life Expectancy is a result of Usage. Use it once a month and you'll probably be using it for more than a decade on normal conditions.

Use it 24/7 and you'll get not more than 3 years off it.

2. Overclocking a CPU will not directly mean you will reduce it's expected life span. There are things an Overclocker can do to overclock a CPU that will not affect it's Life Span.

the word must be bold since not everyone who overclocks is an overclocker!! :laugh: :laugh: :laugh:

3. Life expectancy is no longer a factor in today's electronics market. PERIOD!

A CPU can only last up to a couple of years to be competitive. Even if you are not a properly informed Computer guy, you will not have a problem prolonging your CPU life. The question is, will you still be using your Haswell i5-4670K Overclocked to 4.8 GHz after a couple of years when a couple of Intel CPU generations have already past that make your todays' GEM nothing but a dust eater? It's no longer competitive, you'll just give it away.

Those 3 conditions will also apply to your tablet. Do I still need to reiterate? How long do you plan to use yoyr tablet anyway? 2years? 3 years?

:good:

The correct word would be Degradation ;)

Within the market life of your tablet, will it still produce the results it posted 1-2 years ago after you have overclocked it hard?

---------- Post added at 10:48 AM ---------- Previous post was at 10:35 AM ----------

Ouch!!!

Will just try to point out, maybe this would help.

GPU is the one largely the culprit for overheating in my TAB. At stock 400 MHz, it can produce heat higher than it's CPU at prolonged use.

I am currently clocking my TAB using the other Kernel at 1998 MHz on the CPU with the lowest Freq at 162MHz UV to 775mV. GPU is at 320 with 150mV UV on all steps . I can go all day benching, with temps not exceeding 50 Degrees Celcius.

Can I play games with my settings?

YES , Real Racing, Asphalt can't even stutter it even at MAX Visuals.
[Nexus 7 (2013) Original Android Development] antonholmstedt:
Edit: problem solved.
[Nexus 7 (2013) Original Android Development] En Kee:
My HTC Desire HD is overclocked since the day one... 4 years ago. From 1ghz to 1.5ghz and it's still perfectly working. And you have to admit, who keeps his device 4 years?

And I don't talk about my computers...
[Nexus 7 (2013) Original Android Development] jugster:
I agree entirely. You probably won't even notice the effect even after 10 years. I am just saying that the effect is not zero. Close to zero, but not actual zero.

/J
[Nexus 7 (2013) Original Android Development] akaempf:
Quick question... Does this kernel support slimport on Nexus 7 2013... I am using SlimBean rom...

Thanks in advance and love this kernel on my Nexus 5...
[Nexus 7 (2013) Original Android Development] GSLEON3:
The Nexus 7 BARELY supports SlimPort. It's buggy as hell compared to every other device I've had or have, but yes, it works with this kernel as well as any other.
[Nexus 7 (2013) Original Android Development] antonholmstedt:
For some reason the init.d script doesn't seem to run during start for me since the date stamp in the log file isn't updated. Is it something I have to do to enable it? Running stock android.

Have two init.d scripts in that folder, 99elementalx and 99SuperSUDeamon.

When I download Universal init.d app from play store and execute the script manually after startup it applies the settings but after every reboot I have to do it again. Elementalx script has file permission 777 set.

I previously had Trickster mod installed, can that be interfering in some way even after I've reflashed the kernel?
[Nexus 7 (2013) Original Android Development] flar2:
Do you have busybox installed and up to date?
[Nexus 7 (2013) Original Android Development] antonholmstedt:
Yes I have, but previously had Trickster mod installed so that might be interfering even after reflashing the kernel. Reflashed the kernel again, wiped cache and installed trickster again and now it is working, though all entries in the log file is double. Suppose that is due to trickster but since it's the same values at the moment it doesn't bother me.

Thanks for a great kernel by the way, will donate! :)

Edit: Uninstalled Trickster but the entries in the log still shows twice but since earlier its the same values so it doesn't really matter.
[Nexus 7 (2013) Original Android Development] EL Sa7eR:
Hey guys , how does this work with ART ?
[Nexus 7 (2013) Original Android Development] Onraad:
ElementalX 2.6 works fine here with latest DJLKang
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
[MENTION=4684315]flar2[/MENTION] Could you take a look at the errors i got while compiling your kernel from source? http://textuploader.com/1uq2

I'm using the default gcc 4.6.

This is what I did.

make clean

export ARCH=arm

export SUBARCH=arm

export PATH=$PATH:~/android/toolchain/arm-linux-androideabi-4.6/bin

export CROSS_COMPILE=arm-linux-androideabi-

make elementalx_defconfig

make -j4
[Nexus 7 (2013) Original Android Development] flar2:
Try compiling with -Os instead of -O3 by selecting the "optimize for size" config option.

Or use gcc 4.7 or 4.8 (will probably introduce some other compilation errors, but they should be easy to fix)
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
thanks. I tried again, with gcc 4.7 and then, with linaro 4.8 and I still get the same set of errors.

lib/bitmap.c: In function 'bitmap_scnprintf':

lib/bitmap.c:401:1: internal compiler error: output_operand: invalid shift operand

Please submit a full bug report,

with preprocessed source if appropriate.

See <http://source.android.com/source/report-bugs.html> for instructions.

{standard input}: Assembler messages:

{standard input}:4831: Warning: end of file not at end of a line; newline inserted

{standard input}:5061: Error: undefined local label `.L1049'

{standard input}:5073: Error: undefined local label `.L1049'

{standard input}:5077: Error: undefined local label `.L1049'

make[1]: *** [lib/bitmap.o] Error 1

make[1]: *** Waiting for unfinished jobs....

make: *** [lib] Error 2
[Nexus 7 (2013) Original Android Development] flar2:
Did you try -Os ?

lib/bitmap.c is unchanged from the original google source, so it should compile with 4.6 and optimized for size. I think I used linaro 4.8.1 to compile this.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Could you elaborate please? I'm completely new to this. Just compiled stock google kernel successfully and then went for yours. Btw, this is what I found in your defconfig:

# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

CONFIG_SYSCTL=y

CONFIG_ANON_INODES=y

CONFIG_PANIC_TIMEOUT=5

CONFIG_EXPERT=y

CONFIG_UID16=y

where do I change O3 to Os ?

thanks.
[Nexus 7 (2013) Original Android Development] flar2:
Change it like this:

CONFIG_CC_OPTIMIZE_FOR_SIZE=y
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Ah, thanks man! I replaced the entire chunk under # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set and it passed that. However, a new set of errors.

fs/cifs/cifssmb.c: In function 'CIFSSMBUnixSetFileInfo':

fs/cifs/cifssmb.c:5609:25: warning: array subscript is above array bounds [-Warray-bounds]

error, forbidden warning: cifssmb.c:5609

make[2]: *** [fs/cifs/cifssmb.o] Error 1

make[1]: *** [fs/cifs] Error 2

make: *** [fs] Error 2
[Nexus 7 (2013) Original Android Development] flar2:
For this, you could either revert my CIFS commit (my commit downgrades CIFS to an earlier version) or add this to fs/cifs/Makefile

ccflags-y := -Wno-array-bounds
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
thanks a ton man! I wanted to stay close to elX, so I added that line to fs/cifs/Makefile and it worked. A few more questions please.

1) what is this change "# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set" and why didnt it work earlier when the value "Was not set"?

2) what do I do to build it with O3, like you do?

3) I compiled this using 2 commits for compatibility with CM roms. If I replace the elx.zImage with the new zImage in one of your aroma zips and flash it like I flash eX usually, will the configured settings work?

4) May I share this CM compatible eX in a thread, Credits and a link back to original thread go without saying.

again,thank you. Really appreciate your help.

I tried many kernels since I switched to a CM based rom, but I just couldn't live without elementalx, so I tried compiling it for cm, and now it works. :D
[Nexus 7 (2013) Original Android Development] flar2:
1. there are build optimization levels like Os O2 and O3. Os is the default, and makes the compiled kernel smaller in size. O3 has more code optimizations, which make the kernel bigger

2. to build with 03, you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and then fix all the compilation errors and warnings that result. The exact errors will depend on the toolchain you use, but the vast majority are just complaints that variables aren't initialized (so you set them to 0 or NULL)

3.I think so. What are the commits you added?

4. Of course, the source is open and anyone can use it.