G
Ovviously I did it!!!uff...it's really annoying,it sucks my battery...
Sent from my Galaxy Nexus using XDA
I had it too on old MSI a/b/g router, but after replacing it with a new one a/b/g/n grade, issue is gone.
Sent from my Galaxy Nexus using XDA
....seriously,never had a problem with any phone with this router.....only gn...
Sent from my Galaxy Nexus using XDA
soon to be 2000mah just gotta find a genuine seller....
Sent from my Galaxy Nexus using xda premium
Franco, what radio and bootloader do you suggest I use for Europe (Greece)?? Which ones are you running?
Sent from my Galaxy Nexus using XDA
I couldn't have said it better myself!! I used a car battery sitting on my bench to charge this phone the other day with cord I built from old Nokia charger ; )I doubt there are a lot of us who actually follow all the best practices for Lithium-ion batteries. They do say that full discharges are bad for the battery, but the same people say that using battery in the heat is bad as well. Even using it at room temperature will deteriorate the battery, let alone using it on a hot day in sunlight. OH NOoos can't bring my phone to the beach now, its going to hurt my battery. They also say that we should always use the original charger, I've owned oem micro usb chargers ... are they good for my battery, probably not, they probably trickle past the recommended volts. Am I not going charge my phone because I don't have the original charger with me... nope, my battery needs charging I'll plug it in to anything that give me more power. They say don't fully discharge your battery because it stresses it, they also say that using lots of power and draining your battery fast also stresses the battery. Does that mean I'm not going to play anymore games because it stresses my battery? Am I no longer going to run benchmarks? Anyways, I can continue, but am not, my point is that lots of things aren't good for the battery. whatever... lucky us, we can remove our batteries and new ones aren't very expensive these days.
I had fantastic results yesterday with 165 using stock settings, today I went back to full power mode and its not been as friendly to battery as 999 and 162 were on same setting , personally I think I'm going to stick with 999 and 162 ( can't decide witch is better ) but they r working " better " for me
Thanks for ur time Franco, this kernel is by far the best on any of my phones!
Well going by the changelog u can c that there not; )Pretty sure 999 and 162 are the exact same just with different names. Fwiw
Sent from my Galaxy Nexus using Tapatalk 2
Thanks, Franco, cannot wait 166...I'm gonna release r166 in about 15 minutes. I got some confirmations from Greg White (the sdcard binary hack author) that raising the wi-fi voltage back to stock 2.0V it fixed all the signal problems he was having. Just gotta prepare everything for release, stay tuned.
Franco, haven't the wifi voltages been your own custom voltages for a while now? Why all of the sudden do you think this is happening?
Latency - Download - Upload
cubic:
1st run: 15ms - 10,75Mbps - 7,82Mbps
2nd run: 14ms - 10,84Mbps - 8,06Mbps
reno:
1st run: 13ms - 15,51Mbps - 6,73Mbps
2nd run: 13ms - 14,73Mbps - 8,51Mbps
bic:
1st run: 12ms - 10,38Mbps - 8,61Mbps
2nd run: 13ms - 10,78Mbps - 8,62Mbps
westwood:
1st run: 11ms - 17,65Mbps - 8,30Mbps
2nd run: 13ms - 13,28Mbps - 8,29Mbps
highspeed:
1st run: 13ms - 10,76Mbps - 7,94Mbps
2nd run: 16ms - 14,42Mbps - 8,52Mbps
hybla:
1st run: 14ms - 11,19Mbps - 7,44Mbps
2nd run: 14ms - 13,47Mbps - 7,56Mbps
htcp:
1st run: 14ms - 13,24Mbps - 7,03Mbps
2nd run: 15ms - 10,85Mbps - 8,00Mbps
vegas:
1st run: 14ms - 8,49Mbps - 6,62Mbps
2nd run: 14ms - 12,00Mbps - 7,07Mbps
veno:
1st run: 13ms - 9,58Mbps - 8,13Mbps
2nd run: 13ms - 8,50Mbps - 7,64Mbps
scalable:
1st run: 18ms - 12,01Mbps - 8,73Mbps
2nd run: 14ms - 13,96Mbps - 8,23Mbps
lp:
1st run: 14ms - 14,90Mbps - 8,68Mbps
2nd run: 14ms - 13,44Mbps - 8,72Mbps
yeah:
1st run: 14ms - 13,37Mbps - 8,28Mbps
2nd run: 17ms - 13,89Mbps - 8,14Mbps
illinois:
1st run: 13ms - 12,93Mbps - 8,24Mbps
2nd run: 16ms - 13,97Mbps - 6,46Mbps
Just woken up and feel like my head is going to explode already this last 5 pages is crazy
I got these from that thread:
so it makes much sense, to make the min_sample_time as low as possible (?), but how low? what's the most appropriate sample time for battery and performance?
for the timer_rate, franco suggested 30k to consider the CPUs latency. What has it to do with the cpu's latency?
he also said min_sample_time doesn't have to be in multiple of timer_rate.
in my case, all my timers are in 20k, which works fine as of now. But i must be missing some things, because I just saw somebody post these values, and no detailed explanation for having them.
So to make the short hand easier, we kept it in that order and just said: 20000/50/40000/20000 became 20k/50/40k/20k became 2/5/4/2. Make sense?above_hispeed_delay: 20000
go_hispeed_load: 50
min_sample_time: 40000
timer_rate: 20000
-above_hispeed_delay: Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load.
-go_hispeed_load: The CPU load at which to ramp to the intermediate "hi speed".
-min_sample_time: The minimum amount of time to spend at a frequency before we can ramp down.
-timer_rate: Sample rate for reevaluating cpu load when the system is not idle.
So Google's default is 10/5/6/2. Lower numbers are all better for performance except min_sample_time (there higher is faster). So our goal is to find a sweet spot.-above_hispeed_delay: higher = better battery, lower = better performance. (100k is default)
-go_hispeed_load:.......higher = better battery, lower = better performance. (50 is default)
-min_sample_time:......lower = better battery, higher = better performance. (60k is default)
-timer_rate:.................higher = better battery, lower = better performance. (20k is default)
Device: Galaxy Nexus
Max Frequency: 1305 MHz
Min Frequency: 384 MHz
Governor: interactive
Governor Tunables: a_h_d 15000 / g_h_l 95 / h_f 729600 Hz / m_s_t 45000 / t_r 15000 / i_b_f 1036800 Hz / t_l 85 / t_s 80000 / b_d 1000000
IO Scheduler: row
IO Scheduler Tunables: h_r_q 100 / r_r_q 75 / h_s_q 5 / r_s_q 4 / r_w_q 4 / l_r_q 3 / l_s_q 2 / r_i 15 / r_i_f 25
Read Ahead Buffer: 512; NR Requests: 512
TCP Congestion Avoidance Algorithm: westwood
Screen Off Max Frequency: 537 MHz
Color Multipliers: 230 235 340
RGB Gamma: -4 0 5
Trinity Contrast: -22; OMAP4 Gamma: 4; CAB: Disabled
Sent from franco.Kernel updater app:
https://play.google.com/store/apps/details?id=com.franco.kernel
mpu_voltages:
1804mhz: 1425 mV
1728mhz: 1375 mV
1612mhz: 1325 mV
1536mhz: 1275 mV
1420mhz: 1225 mV
1305mhz: 1175 mV
1228mhz: 1125 mV
1036mhz: 1075 mV
729mhz: 925 mV
537mhz: 825 mV
384mhz: 775 mV
192mhz: 725 mV
iva_voltages:
430mhz: 1125 mV
332mhz: 1025 mV
266mhz: 925 mV
133mhz: 825 mV
core_voltages:
512mhz: 1050 mV
384mhz: 975 mV
153mhz: 800 mV