yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] drawde40599:
Just run the command of whatever your changing in terminal.
[Nexus 5 Original Android Development] jfim88:
Delete

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] ralpheboyo:
How cool... Albeit I can't seem to get it to work... But blame that on my terminal skills....
[Nexus 5 Original Android Development] sherlock5545:
If you have Root Explorer or something similar, press and hold on it > Open with > Linux Script Handler > Execute.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Cris7ianO:
I try to interpret these scores. Does this mean reverting to 128 KB will bring the best performance? :what:

Sent from my Nexus 5
[Nexus 5 Original Android Development] ralpheboyo:
Yep.. Running 128 and all of a sudden my phone is so liquid smooth.....

Use solid explorer and only options I have are (see image )

Will try running script with android. Tuner alternatively try to find an app.....
[Nexus 5 Original Android Development] hooliganx:
[MENTION=4708115]sherlock5545[/MENTION]

that's it! thanks man! I totally forgot how do this. only do it one time and... forgot.

thanks!!

[MENTION=264345]ralpheboyo[/MENTION]

I use Root Explorer and follow those steps that [MENTION=4708115]sherlock5545[/MENTION] said.

1. in elementalx.conf change what I want. save. 2. in 99elementalx (init.d folder), hold it, open with / Linux script handler / execute. done!

try change s2w for dt2w and will see changes. done! :D :thumbup:

thanks guys! very good informations!

ps: thanks [MENTION=264345]ralpheboyo[/MENTION] to show how 128 is better than 256 or 512 or.... in read ahead. ;)

now we know why [MENTION=4684315]flar2[/MENTION] make this options.

N5*SlimKat.5.0.(4.4.2)*El-X.1.0

*ART*TWRP.2.7.0*radio.1.16
[Nexus 5 Original Android Development] ralpheboyo:
... Solid explorer has a really nice ui.....

Root explorer on the other hand is packed with features wow..

[MENTION=3530612]Shelrock5545[/MENTION][MENTION=992878]hooliganx[/MENTION]

Thxs guys.....
[Nexus 5 Original Android Development] AhmedFaiz:
V1.00 flying here. Hoping we are heading for new horizon with this kind of performance! Thanks for making my device run better. ?

Nexus 5/PA 4.4 RC 2/ElementalX v1.00
[Nexus 5 Original Android Development] toxicpaulution:
I need that cat photo please ;3
[Nexus 5 Original Android Development] floepie:
Huh? You can do this test a million different ways with different test sizes and cache sizes and get vastly different results. Besides, you're showing only a test for a cache of 256 with a 100MB file size. How often do you use such a large file? And furthermore, you're arguing for the use of a cache of 128 when your screenshot shows a cache of 256. Really confused as to your reasoning with this. Here's a screenie of something I did in a couple seconds.
[Nexus 5 Original Android Development] ralpheboyo:
..... Was playing around with all different settings/setups .... 128 provided the best results for me with my setup... I have reverted to 128.... Can understand why the screen shot can be confusing... Suggest you also play around and see what works best for you...
[Nexus 5 Original Android Development] trawel:
Will v1.00 work fine on VanirAOSP? (actually Atom from the same developer)
[Nexus 5 Original Android Development] floepie:
But, your screenshot doesn't show anything. In fact, you have it set to a cache size of 256 in your own screenshot. Are you comparing speeds at various cache sizes, i.e. 128, 256, 512, etc.? Are you also varying test sizes, or did you hold that constant at 100MB (which isn't very real world at all BTW). I'm just a little suspect here with your methodology. Playing around shouldn't mean much to anyone here unless you indicate how you came up with your conclusion. I can let one variable float and get vastly different results at different cache sizes. I hope you also realize that the graphs at the bottom of that page don't reflect speeds at different cache sizes. They reflect speeds only at *one* cache size AND at *one* test size.

For instance, start with a test size of 10MB. Then compare the speeds at 128, 256, 512 in the drop down cache menu. I find that a cache size at 128 results in a much *poorer* performance.
[Nexus 5 Original Android Development] ralpheboyo:
Absolutely... As I said I ran the test with various parameters... The smaller the cache size during the test will produce better results with the higher r/r ahead ( obviously).. Once again play around and see what works best for you ....and if you have not yet tried 128 try it and let us know how it feels for you...

Next time I do a test I certainly will provide the parameters for people to have more transparency....
[Nexus 5 Original Android Development] floepie:
Well, I find it strange that I can't replicate your results at all. At some file sizes, a cache of 512 performs vastly superior to the other smaller cache sizes. Furthermore, there is significant variance between successive tests, even with variables held constant.
[Nexus 5 Original Android Development] ralpheboyo:
.... Just out of curiosity what rom are you running...
[Nexus 5 Original Android Development] Cris7ianO:
Btw whats the app u are using?? ^^

Sent from my Nexus 5
[Nexus 5 Original Android Development] ralpheboyo:
Free version

https://play.google.com/store/apps/details?id=ccc71.at.free

Paid

https://play.google.com/store/apps/details?id=ccc71.at
[Nexus 5 Original Android Development] wispp:
1.0 is running great ! Thx

Odesláno z mého Nexus 5 pomocí Tapatalk
[Nexus 5 Original Android Development] ArcMage:
Trip report:

Just flashed the latest Carbon nightly and the 1.00 AOSP kernel via the Aroma installer.

I used all default settings, with the following exceptions:

Stock thermal throttling

Undervolt to 750 mV

Screen-only touchwake with various gesture settings.

USB fast charge

Exfat support

On boot, I got continual android.process.media force-closes.

Reflashed the rom and flashed 0.45 aroma installer without the undervolt or exfat support, and it's now running fine.

Dunno if it's something to do with the 4.4.4 release, or with the exfat support, or with Carbon breaking something.
[Nexus 5 Original Android Development] itasoulas:
I don't get that on nexus 5 but have it on nexus 7 2013 with latest ElementalX. Are you using gravitybox and set the 30 volume steps on? Maybe this causing it. I also noticed that i get this when I reboot the device. If I power off and then on again, fc message does not appear.
[Nexus 5 Original Android Development] ArcMage:
Well, I reflashed 1.0 without the EXFAT support and it stopped giving me ****. The error seems to relate to the phone thinking that media storage was corrupted; the recommended fix under normal circumstances is to wipe it, but I think I've got the issue spotted here.

I'm not totally sure what I want EXFAT for anyways, so I doubt I'll miss it.
[Nexus 5 Original Android Development] ralpheboyo:
.... You aware carbon is cm based last time I checked... And you flashed ASOP.... Not ideal....
[Nexus 5 Original Android Development] ChazzMatt:
Carbon is AOSP.

First sentence in the op.

http://xdaforums.com/google-nexus-5/development/rom-carbonrom-kitkat-t2632141
[Nexus 5 Original Android Development] ralpheboyo:
Wow.. Don't use carbon but was under the impression they moved to cm a while back...
[Nexus 5 Original Android Development] GtrCraft:
They have cm features but they never used cm as a base
[Nexus 5 Original Android Development] ArcMage:
As above, Carbon is AOSP, but more to the point it functions quite happily with either the AOSP or CAF builds.

The AOSP build is 'correct' however.

In any case, foregoing EXFAT fixed the issue for now.
[Nexus 5 Original Android Development] ChazzMatt:
Yeah, all ROM teams cherry pick features from other ROM teams. Even those who "create" many new features themselves. ;)

For me, AOSP base is very important, so I keep track of a few ROMs that are AOSP-based and have the features I like -- like Mahdi, Carbon, C-ROM, Xenon-HD, etc. This isn't the place to discuss ROMs, but it's nice to have choices.
[Nexus 5 Original Android Development] Cris7ianO:
Took the app and run few tests with different schedulers. And my conclusion is: these benchmarks are really inconsistent xD I can run the test ten times and I get ten totally different scores... Doesn't matter tested a bit and for me row with 2048 seems pretty good... But in the end I think the difference is negligible.

Sent from my Nexus 5
[Nexus 5 Original Android Development] szucsgf:
There is so much variance in results even given the same parameters that is hard to say one value is superior to others. But it's interesting that you like row 2048; I used the same app and tested about 20 times and found that combination to most frequently give high benchmarks, so I'm using row 2048 too. Coincidence?

I wasn't very scientific (none of us were) but the methodology to test would be simple enough: run the benchmark over and over, record results, and see which configurations have the highest average score.
[Nexus 5 Original Android Development] ralpheboyo:
... Good to see you guys playing and tweaking away and sharing findings... 128 provided such a fluid experience I stuck with it compared to the previous 512.. Obviously I think there are also quite a few variables at play here that one really needs to jump through the hoops to see what handles best for each of our individual devices....
[Nexus 5 Original Android Development] peecs121:
I did tons of tests myself and found that 2048 runs the best on my phone as well. I've been on it for a month or so now with no problems

Nexus 5 (4.4.4) running Carbon/ElementalX 1.0
[Nexus 5 Original Android Development] trawel:
What about VanirAOSP (actually a bit modified version of it - Atom). Can I flash elementalx stock version (is it AOSP based ROM)?
[Nexus 5 Original Android Development] 1ManWolfePack:
So if we want to revert back to the stock kernel (assuming I'm on stock) is it as cut and dry as restoring the boot.IMG from a backup? Seems pretty straightforward, but I just came from an M8 and it involved more than that. I've been flashing kernels since the OG Droid and the M8 rollback was new to me.

Anybody pickup what I'm trying to throw down? And btw, no plans to flash back now, just curious in case I ever want to. Just got this phone a week ago and I wasn't having the best battery life. However, version 1.0 is solving that problem. Well done.

Thanks.
[Nexus 5 Original Android Development] walpurgisnacht30:
You can dirty flash your rom
[Nexus 5 Original Android Development] 1ManWolfePack:
I don't have a ROM, homie. I run stock.
[Nexus 5 Original Android Development] walpurgisnacht30:
Did you read the op?
[Nexus 5 Original Android Development] -DroidIsDNA-:
This kernel, specifically version 1.0, works well with the pure white stock 4.4.4. Thanks for the great work, dev. UV -35, 300-1958, all very stable.
[Nexus 5 Original Android Development] 1ManWolfePack:
I read every OP. This one is a mile long (no complaints - I like thoroughness) so I'll skim it again.

Also, to add - if you would have read my entire post, you wouldn't have told me to dirty flash my ROM, as you would have read I was on stock.

Either way, no worries, I'll read again.

EDIT: just reread OP. Didn't answer my question.
[Nexus 5 Original Android Development] drawde40599:
Yes .

its also good idea to have stock ROM downloaded to your phone JIC . http://xdaforums.com/google-nexus-5/development/rom-android-4-4-3-ktu84m-rooted-busybox-t2557523
[Nexus 5 Original Android Development] Frankie73:
Yeah, Vanir is AOSP based. So regular EX should work fine with Vanir.
[Nexus 5 Original Android Development] 1ManWolfePack:
Good call, but I'm on 4.4.4, so I'll do a search for that.
[Nexus 5 Original Android Development] drawde40599:
That is 4.4.4 ;)
[Nexus 5 Original Android Development] 1ManWolfePack:
You're correct!

(Damn deceiving link names) ?
[Nexus 5 Original Android Development] Co.Tibi:
[MENTION=4684315]flar2[/MENTION] Thank you for your last version. v1.00 fixed the issue mentioned above. Whatever you did don't change it. Thanks again for the wonderful work.
[Nexus 5 Original Android Development] RJQXCV:
Flar started fresh? Awww s**t I can't wait for the cm version. ?
[Nexus 5 Original Android Development] Faxx4840:
Compatible with Miui ROM ? Thx

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] hooliganx:
have 2 versions: AOSP and CM.

go to the thread where you download or follow the ROM and see your version.

come back and download the right version.

;)

is so much easy know the version of ROM in a ROM thread :thumbup:

N5*SlimKat.5.0.(4.4.2)*El-X.1.0

*ART*TWRP.2.7.0*radio.1.16
[Nexus 5 Original Android Development] micr0g:
You'll have problems with mpdecision.
[Nexus 5 Original Android Development] magnamentis:
yup, funny indeed

count me one more row2048 same reason :)
[Nexus 5 Original Android Development] hooliganx:
WOW!!! :D

this is the first post... "short" that I see [MENTION=5372360]magnamentis[/MENTION] do!

congrats!

:D :thumbup: (only joking man ;))

N5*SlimKat.5.0.(4.4.2)*El-X.1.0

*ART*TWRP.2.7.0*radio.1.16
[Nexus 5 Original Android Development] Tylog:
Lol yes, I am shocked ?

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] trawel:
How much does it affect normal usage? Will it affect battery usage? I have everything set to default. To be honest I have no idea what mpdecision is, that's why I'm asking.
[Nexus 5 Original Android Development] szucsgf:
Mpdecision (MPD) is a CPU hotplug algorithm used by stock Google kernel and ElementalX. It's responsible for much of the smoothness you experience. Its main feature is a touch boost. When you touch the screen it boosts your min CPU frequency from 300MHz to 1267MHz temporarily such that your CPU will scale only between 1267 and max. This lasts for 3 seconds, after which your min CPU frequency reverts back to 300. This makes your experience very smooth while you're interacting with the device (e.g. Multitasking or gaming) and keeps it battery friendly when you're not interacting (e.g. reading).
[Nexus 5 Original Android Development] drawde40599:
Really ? OK lemme try this
[Nexus 5 Original Android Development] techinv:
Wakes gestures and s2s not working on ver 1.

I did have this working on ver 0.45.

Busybox is installed.

Any help would be appreciated.
[Nexus 5 Original Android Development] bobby janow:
Which version of busy box do you have?
[Nexus 5 Original Android Development] techinv:
v1.20.2
[Nexus 5 Original Android Development] bobby janow:
You need 1.22.1
[Nexus 5 Original Android Development] miesa:
My second usb stick works now too! Thanks flar!
[Nexus 5 Original Android Development] pcphobic:
Idle drain on ElementalX ver.1.00

Just wanna say that the idle drain on ElementalX ver.1.00

is very good. I was on 3G the whole time.
[Nexus 5 Original Android Development] techinv:
That doesn't seem to be available in the BusyBox installer app that I have.

Can you let me know another way to get this?
[Nexus 5 Original Android Development] DoesntPostAThing:
Last I checked Vanir used CAF, so you should use the CM version. Although I'm not sure if the CM version is made specifically for CM with optimization/compatibility for CM only commits, or just CAF in general. What I do know though is that if you use the AOSP version on a CAF ROM things aren't going to be too pretty. Also, I only know about Vanir, not 100% sure about Atom, best to ask in that thread. I've only used AOSP ROMs myself.
[Nexus 5 Original Android Development] drawde40599:
Custom Roms should have bbox and no further action needed stock u should be using this https://play.google.com/store/apps/details?id=stericson.busybox . if u use Titanium backup be sure to disable there version .
[Nexus 5 Original Android Development] techinv:
Thank you.

I installed the stericson busybox installer, and was able to get 1.22.1 version of busybox, but.....

No change in wake gestures (rebooted after install of busybox, disabled/reenabled wake gesture module and rebooted again)

The wake gestures app on my device (from the OP) continues to say that my device does not support kernel level wake gestures or they are currently disabled.

My elementalx.conf has

WG=1

SWEEPTOWAKE=1

DT2W=0

S2S=2
[Nexus 5 Original Android Development] drawde40599:
Sorry I don't use that xposed mod for gestures I just use regular double tap ,so I don't no anything about it , but there are lots of guys here that do that should eventually give u some ideas or that thread that's linked in OP may be able to help . but I no it works there are many that use it
[Nexus 5 Original Android Development] letmedanz:
Have zero issues here..

All functions working as advertised...

What kernel were you on before?

Usually busy box ? causes issues in certain devices...

Also what rom are you on? Version 1 is only for aosp roms
[Nexus 5 Original Android Development] techinv:
Franco r54

ROM is stock 4.4.4

I dirty flashed Elemental, maybe I need to try a clean flash?
[Nexus 5 Original Android Development] Tylog:
Only flash stock kernel, then ElementalX Kernel, this should solve your issues

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] BabboDemonio:
You should flash the stock /system not the stock kernel..
[Nexus 5 Original Android Development] Tylog:
No, he does not have to. Not even that is usually necessary.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] hooliganx:
Oi!

sorry for the delay... ;)

N5*SlimKat.5.0.(4.4.2)*El-X.1.0

*ART*TWRP.2.7.0*radio.1.16

---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------

@ralpheboyo

man, how can you be so quick!?

hahahaahahahahaha...

I barely answered and you already thanked me! :D :thumbup:

N5*SlimKat.5.0.(4.4.2)*El-X.1.0

*ART*TWRP.2.7.0*radio.1.16
[Nexus 5 Original Android Development] deck82:
I also can't get wake gestures to work on stock 4.4.4 with Elemental v 1. Was working fine on 4.4.3 and v.44. What other Xposed mods do u have? I feel like it is possibly XGELs that's causing an issue as that's the only new module I'm using. I've flashed the kernel 4 times now trying to get it to work with no success.
[Nexus 5 Original Android Development] GtrCraft:
first flash stock kernel and then ElementalX
[Nexus 5 Original Android Development] techinv:
Worked for me, basically. I decided to do a complete wipe before flashing stock kernel and then Elemental.
[Nexus 5 Original Android Development] deck82:
Worked for me as well! Thanks
[Nexus 5 Original Android Development] Tylog:
That's what I say two times on the last page ;)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] GtrCraft:
The full wipe was not neccesary though :p
[Nexus 5 Original Android Development] deck82:
Correct, I just dirty flashed the stock ROM again and let the phone boot with the stock kernel this time. It seems my issue was from flashing Elemental in the same recovery session that I upgraded to 4.4.4.
[Nexus 5 Original Android Development] miguepereira77:
Hey guys! Does any one know or can u point me to the way to change screen color profile without the need of an apk, I want to set "vomer balanced" and forget, don't want to have faux, or fk or wathever just for this. I've buy them all though

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] GtrCraft:
I always flash them after each other. No boot between
[Nexus 5 Original Android Development] Nucleonic:
I have Elemental set for the default time limit of 15 mins. I'm noticing that when the time elapses, the screen wakes up and closes. Is that normal?
[Nexus 5 Original Android Development] GtrCraft:
Yes, it is normal. It turns off the touch sensor on the screen
[Nexus 5 Original Android Development] vin4yak:
I remember flar saying that he will need to look at the complete spec sheet to find the probable fix for the battery drain whilst dt2w features are enabled...

Since the complete documentation is leaked, is there anything you could do about it?? [MENTION=4684315]flar2[/MENTION] Not sure whether this is the same one which was leaked previously though and whether or not it will be useful.

http://xdaforums.com/google-nexus-5/general/service-manual-d821-t2791303
[Nexus 5 Original Android Development] absoluterebirth:
I flashed the 4.4.4 factory image and then flashed this kernel. As this kernel uses the same ramdisk as the kernel your phone comes work, can I just delete the init.d files created by ElementalX and then flash the stock 4.4.4 kernel by using fastboot flash boot to return to stock? Nothing else should be necessary, correct?
[Nexus 5 Original Android Development] drawde40599:
Your going to most likely going to need to ask devs of those apps , its not as easy as just changing few setting. Doesn't Franco's stand alone color control app work ? That's a pretty simple lightweight app . but I no what u mean about installing a whole kernel control app for one thing , I hate that 2 ;P

---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------

They will delete themselves . only thing should be left is backup on SD card
[Nexus 5 Original Android Development] miguepereira77:
Yeah I can try fk or faux standalone apps for display. Thanks for your answer I wrongly thought it was going to be more simple

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] drawde40599:
If u can find the path to all that color stuff if may not be that bad ,but I just don't think that's something most people would no unless u were involved in building those "hacks" . hopefully someone pops up and knows for u tho
[Nexus 5 Original Android Development] Co.Tibi:
[MENTION=4684315]flar2[/MENTION] do you also develop for N4? I'd prefer to have this kernel on N4 also. If not, does anyone know a similar kernel for the N4? Sorry for the OT
[Nexus 5 Original Android Development] sam.balia1012:
franco kernel, but be careful to flash the correct version, aosp vs CAF

depending on what rom u using,
[Nexus 5 Original Android Development] chubby65:
Semaphore kernel for the Nexus 4 is an amazing kernel

I used to use it together with purity rom

An awesome combo
[Nexus 5 Original Android Development] HumpDdumpD:
So I'm not asking for any kind of ETA here, but are there plans to bring the cm11 kernel to v1.0? This kernel rocks for making Bluetooth solid on cm11. As well as better colors.
[Nexus 5 Original Android Development] drawde40599:
First he will release a test build for asop(1.0 build ATM ), then once the bugs are caught and flar2 is happy with it a CM build will come and OP will be updated .

This is how its been since he started CM/CAF builds so going by history I would GUESS this week we SHOULD see one .

For now 45 is running Beautiful :)
[Nexus 5 Original Android Development] szucsgf:
+1 for Semaphore kernel. That was my favourite on the N4. I can't say it's the most similar to ElementalX, but I highly recommend it.
[Nexus 5 Original Android Development] chubby65:
For me semaphore was the smoothest but kernel and rom is really down to personal choice
[Nexus 5 Original Android Development] letmedanz:
Not at all..

using XGELs & Elemental like forever.. no problems...

most problems will arise if you come from Franco & don't flash stock kernel..

if you still having problems, dirty flash your rom (or just the stock kernel if you on stock rom), reboot once & then install elemental.
[Nexus 5 Original Android Development] wigginst:
I also use xgels with no issues with this kernel.
[Nexus 5 Original Android Development] floepie:
Stock 4.4.4.
[Nexus 5 Original Android Development] ralpheboyo:
Ok... Did you continue to twinker around with the r/r settings.... What were your findings...
[Nexus 5 Original Android Development] floepie:
A bit, but as someone else mentioned, results are far from consistent, even performing successive tests with the same parameters. At some file sizes, 1024 performs the best, while at other sizes, 256 is the best.