your screenshot... is that in landscape mode? how did you do that?
i think he changed the density to trigger the tablet mode..
correct me if i am wrong
your screenshot... is that in landscape mode? how did you do that?
your screenshot... is that in landscape mode? how did you do that?
curious, why is the battery dropping like a water fall towards the 1d point?
Just flashed M2 over AOKP M4....I'm wondering how I can use this kernel since there is no trace of in settings menu....Should I get the app from the market to edit any property or I'm just too noob to see where those are actually placed?
Sent from my Galaxy Nexus using XDA
Just flashed M2 over AOKP M4....I'm wondering how I can use this kernel since there is no trace of in settings menu....Should I get the app from the market to edit any property or I'm just too noob to see where those are actually placed?
Sent from my Galaxy Nexus using XDA
Hey franco,
I have a lot of force close with your app since the last update... Still using #98... but now the app force close...
You have an idea, already cleared cache...
Thanks
Sent from my Galaxy Nexus using Tapatalk
I just started having this with the latest version too... Never a single FC before today, but now it FC's more than it opens. I was out on the bus and playing with settings and whatnot, and everytime I needed to change something in franco's app, BOOM! FC. but then it would launch fine after a couple tries.
I just started having this with the latest version too... Never a single FC before today, but now it FC's more than it opens. I was out on the bus and playing with settings and whatnot, and everytime I needed to change something in franco's app, BOOM! FC. but then it would launch fine after a couple tries.
Erm, a value between 0 and 3?
Sent from my Transformer TF101 using Tapatalk
Am I the only one having a decrease in battery life with Milestone 2? I am using the exact same configuration as M1 where I was having amazing battery life. I am running CM9 nightly 3-19. I get excessive battery drain shown in mah's. I have not installed any new programs either.
I even flashed back to a nandroid with CM9 nightly 316 with M1 and tested it. I get the usual standby drain (50mah). As soon as I reboot, clear dalvik cache, and flash M2 that goes up to and stays anywhere from 300-600 mah.
I checked for wakelocks (there are none) and the phone is entering deep sleep (which it is). No additional apps have been installed.
Does anyone have any idea as to what I might be missing?
Yup, it's the same for me...
Sent from my Galaxy Nexus using Tapatalk
Rom, kernel version, is it possibly clashing with another app (setcpu etc.)
You can't just post +1 and expect help. Francisco isn't psychic.
details people.
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
Details, details, details.
AOSP 4.0.3, kernel #98... I have cpuspy installed but nothing new... FC started after todays update of the apps... logcat are disabled... let me grab more info in logs...
Sent from my Galaxy Nexus using Tapatalk
Francisco, do you have any insight into the drastic difference in battery between Milestone 1 and Milestone 2?
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