yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hetalk:
Correct.

From what I read (a 100 page research paper on these batteries) ideally Li-ion batteries would last longer if you charge it more often. Like, if you connect it to your computer when you have that access. In such cases, battery life extender setting comes quite handy. I normally have it at 97.:good:
[Samsung Galaxy Nexus] milojoseph:
after reading i wont overcharge at night... and wont leave it to die . I will hope it budge at least..... Thx
[Samsung Galaxy Nexus] Nephilim:
Yep, from what I've researched, slightly below 100 is good, 96 to 98 is ideal.
[Samsung Galaxy Nexus] qtoo941:
Hmm i found something interesting. When i try to put targetloads to 85 it is automatically becoming 0 after clicking apply button. But few minutes ago i was browsing in ES File Manager and i decided to see what's going on in trickster data folder. I opened settings.xml and i saw that targetloads in this file are 85 but in the app itself it shows 0 :D I am confused :D
[Samsung Galaxy Nexus] Nephilim:
Lol, welcome to the party, this was discussed about a week ago. ;)

It's all good, it's an issue with what is being shown, if it's stuck on 0 it's still actually on 85 so no need to worry. :)
[Samsung Galaxy Nexus] Hetalk:
You cannot overcharge a Li-ion battery, as they come with a limiter circuit which will disconnect the power when fully charged.

I mean "Li-ion batteries made by standard companies". Non-standard(fake ones) can be overcharged and can explode when done so.
[Samsung Galaxy Nexus] Nephilim:
Yep, this is why I never understood people that did the whole bump charge aka charging the battery to full, then turning off the device and charging it awhile longer. All this does is decrease the life of the battery itself while really only giving you no more than about 10-15 minutes of additional battery on the charge.
[Samsung Galaxy Nexus] Hetalk:
Exactly.

BTW, why don't you put your icons link to your signature thread. I'm sure people will love them as much as they love your settings.

I love them. :good:
[Samsung Galaxy Nexus] Nephilim:
Thanks for your kind words. I'll consider that. For now anyone can grab them, they are sitting in my Drive Shared "Nephilim" Folder, linked on my G+. ;)

---------- Post added at 06:35 PM ---------- Previous post was at 06:27 PM ----------

After further investigating, I have noticed that even though my lockscreen reads "charged" my quicksettings battery tile reads "Charging 98%" and my Battery Settings page reads "Charged 98%".

So in short, you are not going crazy Milo, I just overlooked the fact it indeed does stop the charge at 98%, which if you read the info posted a few pages back, does not matter because the device automatically slow drains the battery to around 90% or so within 10 to 20 minutes of being off the charger.

Either way, just wanted to let you know what I found. Also, this has not had any negative effect whatsoever on my battery life. I am still getting about the same life as I have always. It will vary though because DirtyV is still technically experimental. :)
[Samsung Galaxy Nexus] pattyboi:):
f2fs....i like that...i like it alot,lol,i feel like im the only one excited for that :P
[Samsung Galaxy Nexus] dbt816:
we're getting it??? when? where? :D
[Samsung Galaxy Nexus] milojoseph:
You sure im not going crazy ARE YOU SURE....... lmfaoo thanks we need a little fun in this community
[Samsung Galaxy Nexus] pattyboi:):
lol,sarcasm bro,smitty is working on it :P no ETA,but its smitty,he always does what he says or throws his best effort possible at it,so we are in the waiting game (;
[Samsung Galaxy Nexus] iluvamk:
Neph, you do anything with Core or IVA voltages?
[Samsung Galaxy Nexus] David 617:
Thanks. Tether is critical for me. I don't have any other internet access. (Long story...)

---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------

count me in. the pro of a large increase in speed vs con of bricking my phone. just what i need for my crack-flashing addiction... lol
[Samsung Galaxy Nexus] pattyboi:):
i feel you bro,the crack flashing addiction is real,im always f5ing the thread for things to flash lol
[Samsung Galaxy Nexus] David 617:
we need help... :eek:
[Samsung Galaxy Nexus] dbt816:
Awesome :)

I really need to find more time to pitch in on the kernel stuff. There was a time in the deep, dark past where I maintained a Linux distro for a medical imaging system ;)
[Samsung Galaxy Nexus] pattyboi:):
we need lots of help... :eek:

---------- Post added at 09:00 PM ---------- Previous post was at 09:00 PM ----------

maybe you can build a distro to diagnose me and davids crackflash addiction ;)
[Samsung Galaxy Nexus] Nephilim:
Nope, too risky when so many members use my settings. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
Doubtful... being an addict myself :silly:
[Samsung Galaxy Nexus] bsmitty83:
Its sooo close ...lol you might not like the sdcsrd wipe that has to go along with it .. Im getting some help on this by another dev for the missing piece if I can't figure it out so I'm confident
[Samsung Galaxy Nexus] metalspring:
speaking of crack flashers, I might have 3 test kernels

All made with my custom cross compile toolchain optimized for the gnex and dirtyv

One version is exactly the same as the 02-10 build bsmitty did

the second will have the extra cflags for -Ofast, extra graphite and link time optimization cflags

And the 3rd is my custom build, with some low level debugging cut out, a few extra cflag changes in source to allow it to be as optimized for the gnex as possible, plus lots of governors, I/O schedulers, and TCP congestion settings removed, plus smartreflex v3 (like the smitty versions of dirtyv have)

All will be combined with [MENTION=4544860]osm0sis[/MENTION] ramdisk

If Smitty doesn mind me posting them for people to test lol
[Samsung Galaxy Nexus] pattyboi:):
dude,sdcard wipe vs major performance increase,,,we both know that answer ;) gods speed and best luck my friend :)

---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------

ill gladly test for you bruh,sounds awesome to get my fix ;)
[Samsung Galaxy Nexus] bsmitty83:
I feel you I went a year with my nexus hotspot as my only WiFi so that's one of the reasons I'm doing it

And as far as f2fs goes , I'm only gonna format data and cache as f2fs

Im not messing with any other partitions .......yet :p
[Samsung Galaxy Nexus] bsmitty83:
Haha go ahead bro , no permission needed ,

The people r gonna love us tonight , I'm whipping up some new ones ATM , working on smartass permissions
[Samsung Galaxy Nexus] pattyboi:):
praise the kernel gods [MENTION=4608636]bsmitty83[/MENTION] & [MENTION=4328678]metalspring[/MENTION] ;)
[Samsung Galaxy Nexus] metalspring:
Here they are

Only toolchain changed-

Dirtyv-2-10-ramdisk-test

Toolchain changed, plus higher cflags

Dirtyv-2-10-cflag-test

My custom build-

Dirtyv-2-10-custom

Btw [MENTION=4608636]bsmitty83[/MENTION] one thing I changed in my custom build that might help keep things optimized for the gnex is here-

https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV2/arch/arm/vfp/Makefile

I changed msoft-float to -mfloat-abi=softfp since according to this, soft float disables -mfpu= for that part of code (which we use -mfpu=neon for the gnex obviously)

But -mfloat-abi=softfp is basically hard float acting as soft float but still allows -mfpu= options to work
[Samsung Galaxy Nexus] dbt816:
Oh come on, we *really* need /system as f2fs ;) lol

I'm definitely in for testing!
[Samsung Galaxy Nexus] bsmitty83:
Got smartass tunables to stick .....so far
[Samsung Galaxy Nexus] Sik-1:
Lol no I think you guys are taking it wrongly of what blx tries to do.

Reports claim you should charge your battery when It hits around 15% to about 96% to fully charge the batteries used in our phones.

What blx does is it stops the battery from charging over the limit set, hence it doesn't go past 98%. If it were say lowered to 96% then the phone wouldn't be charged past such and so on and forth

I think I got it somewhat explained lol

Oh and all this is done to extend the batteries life itself, I have never tested if it has an effect on daily usage
[Samsung Galaxy Nexus] Kustaa:
Hey guys, yeah, I'm lazy I know, but I don't want to set neph's settings again because of flashing stock to know these values :silly:

Can you tell me the DirtyV 2/10 stock frequencies? Thanks!
[Samsung Galaxy Nexus] osm0sis:
I think the other thing about BLX is that by the time you'd see an effect on the battery from full charging and discharging you'd already be moved onto a new device. 3 or 4 years or so.
[Samsung Galaxy Nexus] chongns:
[MENTION=4328678]metalspring[/MENTION], a doubt to your kernel, your stock omnimetal dirtyv, the interactive target load can be set, but the [MENTION=1533050]bsmitty[/MENTION] version not able to set, and now on your custom version also not able to set. Can you push the change for this to bsmitty?

And, your custom version dirtry v test kernel, the s.reflex was disable, would like to have it enable.

Thanks

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cujo6801:
Testify my brother

sent from the DOG pound
[Samsung Galaxy Nexus] bsmitty83:
Op updated ,

ramdisk thanks to [MENTION=1143630]osmosis[/MENTION]

3.0 wifi drivers

smartass v2 tunables should stick

let me know how it works
[Samsung Galaxy Nexus] DevVorteX:
Can't enable Wi-Fi on dirtyv-r.
[Samsung Galaxy Nexus] bsmitty83:
OK I was afraid of that sorry I'll have to fix .. It'll probably be like that on all 3
[Samsung Galaxy Nexus] bluerez79:
Same on the dirty-rsr. WiFi just keeps trying to turn on

But after about a minute it never did.
[Samsung Galaxy Nexus] DevVorteX:
It's cool, just flashed back 2/8, so I should have that with ramdisk since I didn't reflash rom.

Patiently awaiting the update fix though, 2/8 seems so long ago, lol
[Samsung Galaxy Nexus] lazydognet:
I get errors when trying flash any the the DirtyV kernels that have Ramdisk.... Is that a common issue or just me.

I'm on the latest Vanir and using Philz Touch 6

I've never had a problem flashing any previous ROMs or kernels before this.

Thanks for any insight to my issue.

LDN
[Samsung Galaxy Nexus] Seraz007:
i always set it at -10 with Neph's settings...

Haven't had any problems
[Samsung Galaxy Nexus] osm0sis:
The only other person who had a problem discovered it was due to a corrupt download. Did you try to download again?

Also, people - and this isn't only directed at you - be more specific than just "I get errors" since that's worse than useless information. ;)

Please, take a minute, actually read the entire error ("Status 7" is just as meaningless), write it down if you need to and let us know what it said. We don't have any errors flashing them or they wouldn't be uploaded in the first place. I even tested with both TWRP and CWM with my zips.

Again, not solely intended for you since I know you meant well, it's just happening too much lately and it's a huge pet peeve for anyone trying to develop something to receive such vague claims of things not working and be expected to fix it. :)
[Samsung Galaxy Nexus] swarlesbarkely:
Whenever I hit the download link I see "softcore" in the url and always think I'm being redirected to porn.. Is that the dirty part of dirty v?
[Samsung Galaxy Nexus] clnzx2:
Lol softcore was a .com startup I created a few years ago for web developers that I gave up on. Since I still had the domain and server I am letting bsmitty use it.

---------- Post added at 06:06 AM ---------- Previous post was at 05:55 AM ----------

I noticed metalsprings custom build has touch boost... Nice!
[Samsung Galaxy Nexus] lazydognet:
I understand....I was really just trying to see if any others had issues installing the ramdisk version in general. In my experiences, it's rare to be the only one with a problem (usually, I always seem to find others who experience similar issues).

Since it doesn't appear to be a common problem, I'd appreciate any suggestions.

I have tried multiple downloads with the same results.

The first part of the error states

Assert failed: getprop (*ro. product. device*) == "maguro" || getprop (*ro. product. device*) ==.....and it continues

Later it states

Error in /data/media/0/rom/dirtyv-rsr-2.13.14.zip

This last error does sound like a corrupted zip, but again, I'm I have tried multiple downloads.

Any thoughts?

More information.......

I did a fresh install of Vanir and had no issues flashing the latest DirtyV with Ramdisk.

LDN
[Samsung Galaxy Nexus] swarlesbarkely:
Still having issues setting smartass tunables..just flashed over 2/10 and wiped both caches.

Would a logcat help?
[Samsung Galaxy Nexus] sajty:
Me too.
[Samsung Galaxy Nexus] pianistaPL:
You mean of course tissue? :cool:
[Samsung Galaxy Nexus] qtoo941:
[MENTION=4328678]metalspring[/MENTION] i flashed your custom kernel and i cannot enable smart reflex thingies in trickster. Every time i set them on and apply the settings just seconds later they become off by itself :D

Also i saw that smartassv2 has now tunable values. I am waiting for [MENTION=2853378]Nephilim[/MENTION] to share us his tunables for smartassv2 :)
[Samsung Galaxy Nexus] chainrulez:
That's EXACTLY what I wanted to say!!! damn ... :laugh:
[Samsung Galaxy Nexus] bsmitty83:
So I figured out why WiFi is out , it was something In my config file , so expect an update some time today
[Samsung Galaxy Nexus] metalspring:
That's because it's smart reflex version 3 only (unlike the version in the regular dirtyv kernels). Version 3 is always on and not tunable, I use that version in the builds I run since it works best for me (512 GPU speed is actually usable for me on v3 but not the other version)
[Samsung Galaxy Nexus] dbt816:
Do you have the latest CWM or TWRP recovery flashed? It has been a while, but it seems like I have seen that "assert" error because I was on an old CWM.
[Samsung Galaxy Nexus] bsmitty83:
I snuck a new dirtyV bigmem in the op , WiFi should work ,and its [MENTION=1143630]osmosis[/MENTION]' awesome anykernel v1.5 install so I added the ramdisk governor permissions too so smartassv2 should be tunable . haven't tested it yet doing it all remotely .
[Samsung Galaxy Nexus] heXacode:
Do you use an emulator at all for testing?
[Samsung Galaxy Nexus] bsmitty83:
No just my nexus , but I'm away from home and don't have a way to test ATM ,
[Samsung Galaxy Nexus] heXacode:
Ah OK. Just thought I'd suggest it to help you out in a way. Using team viewer, jump, or different SSH you can have an emulator set up and test within that remotely when away from home and can't test on your phone. Its a nifty idea I tested a year ago.
[Samsung Galaxy Nexus] bsmitty83:
I didn't know you could set up an emulator to test kernels , I thought you could only do that for apps and ROMs ?
[Samsung Galaxy Nexus] heXacode:
You should be able to test kernels. I wrote a huge guide (outdated now) on using the emulator and I only covered a very small proportion of what all you can do with it. The rest of what you could do was left out since it was just a how-to get it started up, push and pull apk's, adjusting memory space for testing, etc.

2 options for testing...

Build and compile your kernel and copy it to the prebuilt kernel folder

or...

Start emulator with kernel option set and type into command...

emulator -kernel

path/to/zImage (this line you need to type in where your compiled kernel is located before starting the emulator)

There are guides that will give you directions to replace Google source kernel with your own source.
[Samsung Galaxy Nexus] Punkiderma:
Just wanted to report after some usage:

I'm using latest osmosis release, with his ramdisk. I've got a few reboots during calls, but I think it's due to my phone not working correctly with Nephilim settings, too low for me :l

However, everything is really, REALLY silky smooth.

I'm using 920000 as max freq, without lags. SmartassV2, fiops.

Battery seems nomal: 1 day of usage (reading on 3g mostly), 2 hrs screen on and still 19% left (NOTE that I use BLX set to 89, but I'm thinking to revert it to 100 or 98 after reading that is not so useful).

Never used SuperRam before this one, and now I don't know if I'll switch back to normal or bigmem. Never used 1080p, videos came out too big for the 16 of the Gnex IMHO.

With all these releases the thing starts to be a little confusing XD

Correct me if I'm wrong:

bsmitty83

-base of the others

-now have osmosis ramdisk

osmosis

-own ramdisk

-other tweaks listed in this post

metalspring

-osmosis ramdisk

-differences in toolchain used, specially optimized for gnex

right?
[Samsung Galaxy Nexus] Nephilim:
Sorry to hear about the reboot issues, unfortunately I cannot guarantee positive results if you are using different cpu frequencies and governors than what my settings have posted. Some devices do not handle extreme undervolting well though, this is why I state that in red text at the bottom of each kernel settings section. ;)

As for the 1080p thing, I find it humorous when people say things like "I want to use SuperRam but I really need to watch my 1080p videos, well that's kind of strange seeing as the Galaxy Nexus can only render video in a maximum of 720p resolution for playback. :p

All these people filling their devices with 7gb 1080p videos to watch are pretty much just wasting time and space.

P.S. the 1080p reference was not directed at you, I just find it humorous. I know you were speaking about video recording. :D
[Samsung Galaxy Nexus] Punkiderma:
Yeah it's true XD

Just wanted to clarify that I was not pointing at you and your settings, I know that every phone reacts differently because of chip-makers' tolerances, I think my Gnex can't go low as your with voltages unfortunately :)

By the way, just flashed metalspring's custom version, let's see :)
[Samsung Galaxy Nexus] metalspring:
I agree on the 1080p thing. Its just silly to worry about not having 1080p videos, because 1) we only have a 720p resolution on our phones (as you mentioned) and 2) even if you wanted 1080p to have better quality when viewing your videos on a pc, its still pointless for about 99% of people since I believe 720p and 1080p are virtually indistinguishable unless you are viewing on a screen bigger than 25 inches or so (which most people dont have pc monitors that big lol)
[Samsung Galaxy Nexus] Kustaa:
And could you tell me what's the differences between using one or another ramdisks? Thanks
[Samsung Galaxy Nexus] Punkiderma:
I think the ramdisk is the same for all, osmosis' one.

And unfortunately I know nothing about differences between these kernels, I know nothing about developing XD

I just try and see :D

[MENTION=4328678]metalspring[/MENTION] is normal that on your kernel build all voltages are by default set to 0? I mean, I think they're not really 0, or my phone would hang immediatly, but trickster shows that
[Samsung Galaxy Nexus] Nephilim:
Good call, I have a 42' lcd 1080p television for my monitor and the difference is still pretty much nothing. Now in my livingroom on the 57' it makes a difference. I think that not only screen size matters but more so the refresh rate and type of set. (led, plasma etc) if you only have a 60hz refresh rate 720p is alway going to be fine. 120hz and 47' or above is when 1080p starts to make a difference.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] AJ Bryant:
So the solution was to remove the Touch Wake feature from the kernel? That was the main reason I chose this kernel.
[Samsung Galaxy Nexus] Nephilim:
If that was the only reason you picked the amazing kernel I feel bad for you. No offense meant but this kernel has so many great qualities it's sad to think that the only thing that matters is the touchwake option.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] scarcry:
Indeed. These kernels are the best thing for our beloved gnexus since sliced bread lol

Sent from my LiquidSmooth KitKat maguro
[Samsung Galaxy Nexus] juju2011:
You lucky ass mofo mine has to work a double today :( so it valentines with my two daughters lol... still hoping for a surprise visit tho
[Samsung Galaxy Nexus] michierusama:
My valentine is tomorrow lol
[Samsung Galaxy Nexus] juju2011:
Lol and my friends said i was crazy for using a 46 inch TV solely for a comp monitor.. And yah not much of diff between 720p and 1080p at all on cells my mega plays back 1080p this 720p and if put them side by side abd play same vid you see absolutely no diff they look the exact same sr ftw
[Samsung Galaxy Nexus] michierusama:
Also movies weight less. And look good and play good with hw+ and sw acceleration.
[Samsung Galaxy Nexus] juju2011:
Lol mine was technically yesterday but am greedy what can I say hahah
[Samsung Galaxy Nexus] Nephilim:
Some people use Dual Monitor, I prefer just one big ass screen lol.

Yea, when it comes to resolution the screen size is what makes a giant difference. When on a 47+ inch Television/Monitor there are far more pixels visible so when you are watching something in a lower resolution you can see the difference due to how easy it is for the naked eye to notice every single little pixel. On a 5 or even 10 inch screen the pixels are so small you cannot see a noticable difference. Videophiles may contest this but they are just being anal with literally no justifiable evidence to back up their claims. The only thing a HD screen on a Tablet or Smartphone really benefits us in is text viewing, sure it makes for a cleaner screen but if you have your colors and brightness optimized the only thing 720p or 1080p is truly helping with is how easily we can read small font. (well and it also helps drain the hell out of our battery faster too lol)
[Samsung Galaxy Nexus] michierusama:
And pictures details. More crisp.
[Samsung Galaxy Nexus] DevVorteX:
Quick question.

I've tried the superRam version before, but I swear I couldn't watch anything on youtube. Is that a common problem. Is there some setting in youtube to say "I don't want 1080"? I get pretty darn good performance on the non-SR version, but just like anyone probably watching this thread, I obviously want MORE.
[Samsung Galaxy Nexus] GilGameshn1:
This... :thumbup:

Sent From My GNex
[Samsung Galaxy Nexus] osm0sis:
This. More an issue with failing getprops in the older TWRP though. Basically that's a device check to make sure you are using one of the 3 GN variants, so naturally it shouldn't fail. Upgrade your recovery to the latest and you should be fine.

Gotta be smartass. It's really acting weird. Next time post a last_kmsg though, to be helpful.
[Samsung Galaxy Nexus] metalspring:
1080p not working on superram refers to video recording, however superram can also cause issues with video playback on some apps (which is probably why YouTube doesn't work for you). It's a hit or miss type of issue
[Samsung Galaxy Nexus] DevVorteX:
That's not fair. I want super ram and youtube :(. I actually barely watch youtube, but when I do, it's usually to show something to my wife, when it doesn't work, she give me a look, along with a lecture as to why I'm not allowed to mess with nor touch her phone..
[Samsung Galaxy Nexus] michierusama:
Bhahaha. This is funny. Sorry...
[Samsung Galaxy Nexus] bsmitty83:
You can try pulling mpo's mediaprofiles.XML out of v10 zip , this disables all 1080 pback or recording .
[Samsung Galaxy Nexus] juju2011:
[MENTION=5354353]DevVorteX[/MENTION] I feel your pain gf watches me on xda all day and when I bring up rooting her s3 I just get a look and her phone moved out of my reach hahah also don't think she likes the fact I've also fried the CPU on 3 notes in 3 months lmao fiddling with settings gotta love that lecture
[Samsung Galaxy Nexus] michierusama:
Hahaha this is more funny!!!