yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rmcsc:
I have experienced numerous force closes and freezes on 157. I was trying to access the "SD card" both times using different apps file managers, so it was probably that, too.
[Samsung Galaxy Nexus] digweed4me:
great battery on nightly156 running 512gpu

cpu min =192

cpu max=1228

governer interactive
[Samsung Galaxy Nexus] mistermojorizin:
i haven't flashed 157 yet, but the few days I've been running 156, been seeing a lot of "managewakelock: partial" in better batt stats.

anyone know what that is? i've been trying to google it, but not getting definite answers.
[Samsung Galaxy Nexus] The Nexus Project:
What are the pros/cons of Squlite Defrag?

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] ks3rv3rg:
Flashed r157 this evening. Set to my normal settings.

1036/192 ondemand/hotplug/sqlite on

384 gpu

Had a hot reboot in the middle of typing a response on tapatalk. Changed gov from ondemand to interactive and havent had an issue. I've never experienced one on any other build. R156 that's included with liquid 1.4rc1 ran fine at the same settings.
[Samsung Galaxy Nexus] drtrmiller:
r157 MUCKED UP MY PHONE

r157 mucked up my phone. Rebooted within 2-3 minutes of auto-flashing kernel, then rebooted before the phone finished booting a second time, then ALL my apps were FC'ing and I couldn't even auto-flash M3 back. . .

Flashed a stable kernel version, and still, EVERYTHING on my phone is corrupted to the CORE. . .so I guess I'll have to do a FULL WIPE because EVERY app on my phone force closes upon opening. . .

NEVER had a problem before r157 and have been using Franco kernels since the beginning of the year.

1344/192 interactive/hotplug/sqlite on

384 gpu
[Samsung Galaxy Nexus] Metallice:
Did you have 192mhz set on boot when you flashed?
[Samsung Galaxy Nexus] ks3rv3rg:
To add to my previous post, I hot rebooted on interactive gov as well minutes after posting that.

That has all taken place on gpu 384

Ive flashed gpu512 and set to he settings in my previous post. We'll see how it goes.
[Samsung Galaxy Nexus] drtrmiller:
I believe so? All my settings were deleted when I flashed an older nightly so I could use the phone.

But everything booted up normally, just a few minutes after the apps and homescreens were loading and being drawn it rebooted. Now, nothing works.
[Samsung Galaxy Nexus] Metallice:
That was the problem. In this new build the SmartReflex voltages for the 192mhz slot is calculated seperate from the 384mhz slot instead of piggybacking. Your phone couldn't handle the voltages SR was calculating 192mhz slot and because you had it enabled at boot...

The data corruption is a result of having fsync disabled and the multiple hard resets. Sorry.
[Samsung Galaxy Nexus] nklenchik:
I had a hot reboot on 157 too. It happened on 192mhz, ondemand, but everything's running smoothly now.
[Samsung Galaxy Nexus] nodstuff:
Having 192mhz min CPU with the new lower voltages and hotplug mod on at the same time is gonna be trouble seeing that some people are getting instability with 192 and hotplugging thrown into the mix isn't gonna make it any better.

I've had the same thing happen to me before, its a pain in the ass.

My problem was caused by a rom but it caused the same problems.

Derp. Already been said....

On another note, no problems here, 157 is working fine at 192 for me @ 710mv

Hotplug mod off. Hotplug may be a common denominator in this problem.
[Samsung Galaxy Nexus] Cutting-TM:
Just had a bsod with 157@ 192 MHz, dynamic hotplug enabled with lazy governor. But a phone call arrived me without problems.
[Samsung Galaxy Nexus] PresPPsP:
With 156 I ran 192min with lazy gov with no problems. With 157, i get SOD on 192 and require a battery pull. Bumped it up to 384mhz and it seems to work. My phone does not appear to like 192 with SR. Can i tweak sr to calibrate it up a little?
[Samsung Galaxy Nexus] nodstuff:
Hotplug mod on or off?
[Samsung Galaxy Nexus] jcmm11:
I run with hot plug off at the moment. Still got a hot reboot (see previous post). It's not the hot plug. Just the lower voltage at 192.
[Samsung Galaxy Nexus] schizophrenia:
a min frequency question

I know a lot of users do recommend min 729 as it puts the phone to sleep faster by finishing tasks faster. But a lot of users play musics with the phone which will keep the phone awake for quite a long time. in this case, would a lower min CPU (e.g. 192 or 384) be more battery efficient than higher min CPU (e.g. 729)?
[Samsung Galaxy Nexus] Metallice:
Yes. Very much so.
[Samsung Galaxy Nexus] The Gingerbread Man:
Nightly 157 192-1344 interactive, generic hot plug on, smart reflex on. No issues with my phone, been on charge all night and used it since the moment I woke up. All going good here
[Samsung Galaxy Nexus] drtrmiller:
Just did a full wipe and flash of the latest AOKP M5 and Franco r157, and my GN LTE can NOT handle 192 @ 710mv with or without the hotplug option. Two speaker pops and hot reboots within minutes of each other, with the "Set on Boot" option unchecked.
[Samsung Galaxy Nexus] jhericurls:
I'm getings loads of hot reboots with Ondemand, switched to Lazy ands seems ok for now.

Running 192-1228Mhz, Hotplug off.

Edit: Lazy reboots too, moved back to 156.
[Samsung Galaxy Nexus] mcdull:
on nightly 157.

192-1344

ondemand

generic hotplug off

all good for the last hour (charging)
[Samsung Galaxy Nexus] ChosSimbaOne:
Had reboot with 157(GPU 384) probally 192 mhz mode that did it. My SmartReflex voltage for 192 mhz is 710 mv.

192 mhz ran fine in 156.
[Samsung Galaxy Nexus] Tommebaas:
Which one do i need for gsm nexus?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
Either one.

512mhz may run on your phone but if it doesn't then they the 384mhz version.
[Samsung Galaxy Nexus] AzzaD:
yeah 157 had hot reboots for me too, went back to 156 - couldn't pinpoint the issue, might've been 192MHz
[Samsung Galaxy Nexus] alteredmass:
I'm running 192 and generic hot plug on and im not having any problems [Nightly 157]
[Samsung Galaxy Nexus] Treatcon:
Running 157 all morning here with 729-1228 interactive. Everything else is at default values. No problems at all with wifi, 3G/H network, blahh blahhh. Running pretty responsive and smooth.
[Samsung Galaxy Nexus] franciscofranco:
I give up, no one knows how to read. I said in the changelog that 192mhz had lower voltage.
[Samsung Galaxy Nexus] siuba:
i m running r157 now, hang one time black screen in idle mode, need to take out battery to reboot, i think cos of 192MHz 710mV too low problem?

btw, UV problem, i did apply but still saved = current, even SR on or off! is it normal? i m using franco.kernel since M2 til now, there's nothing can set for UV, thanks
[Samsung Galaxy Nexus] joeyfong:
Running min 729 too, seems save more battery

---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------

Things is like that, people only will complain when hang up
[Samsung Galaxy Nexus] siuba:
that's report! not complain! if no one tell it out? how u know that lower voltage is not stable??
[Samsung Galaxy Nexus] MS.:
And only then they MIGHT read the change log :-D

729-1344MHz, interactive governor, generic hotplug. No problems at all.
[Samsung Galaxy Nexus] jcmm11:
Right we know that. (or at least I do) And it appears that the lower voltage doesn't agree with a lot (not all) of the phones out there. If people didn't complain/report about the hot boots etc you'd assume that the lower voltage was stable across the board.

Anyway maybe try 750 instead of 700? I'd guess that would help at least some of the problem phones.
[Samsung Galaxy Nexus] franciscofranco:
Yes gonna try something around 750.
[Samsung Galaxy Nexus] qballe:
I am getting crazy battery life on #154, 729-1228 ( interactive ) , I can confirm ( with my usage pattern ) I have a better battery life with 729 as min freq ( I am so surprised but HAPPY :D )

tnx franco, TNX , I will send you a lot of nespresso "Roma" capsules for help you during development :D

sorry for my english
[Samsung Galaxy Nexus] joeyfong:
If it is report why franco said gave up????
[Samsung Galaxy Nexus] Metallice:
Unfortunately if it breaks 192 for for 5% of people, with Franco's user base that's still a WHOLE LOT of people complaining... while people without issues won't bother posting... and as a result problems seem more widespread than they are.(heat issues etc.)

Raising the vdd min (aka min possible SR voltage) is probably the best bet. The unique fuse opp still allows everyone to custom undervolt to much lower values than previously possible so its probably best to keep it.
[Samsung Galaxy Nexus] Emilius:
r157 384gpu 8 hours over night and 8% down. 192 working good with 750mV, no more reboots. back to 121 lol
[Samsung Galaxy Nexus] franktitude:
My phone crashed right away after I switched to 192mhz in the app.
[Samsung Galaxy Nexus] moe6:
:facepalm:
[Samsung Galaxy Nexus] franciscofranco:
I thought SR was smarter and calibrated itself to prevent device crash, I guess I was wrong...its frustrating. Its also frustrating seeing people enjoying r121 more, which means the OMAP patches from 4.0.4 are also a big pile of **** because I cant find any patch that I introduced that could break idle battery life for some users. I got 3% drain for 9h tonight anyway.
[Samsung Galaxy Nexus] barrist:
no issues yet with 157 with 192 interactive.. no hotplug..

haven't really done much 'cept moderate usage though.
[Samsung Galaxy Nexus] coolzjai:
Simply to acknowledge here that:

1/. R157 GPU384, Min384, Max1228, On Demand Governor running just fine.

2/. Personally see no big differences compare to previous build r156.

3/. I stay tune with franco apps default settings, and i get:-

4:xx hour screen time

9:xx hour idle

4/. Thanks ^^
[Samsung Galaxy Nexus] dpaine88:
Can the kernel override the min/max freq settings when it needs to?

I'm running 729mhz min to 1228mhz maximum.

Yet, CPU Spy shows slight activity in the 1344 and 384 slots.
[Samsung Galaxy Nexus] Sveke:
I've seen this as well.
[Samsung Galaxy Nexus] stellaryt:
Which rom？

With April and May's nightly I just could keep 3 hours screen time with heavy use.

Long time no see 4 hours screen on with my phone:)
[Samsung Galaxy Nexus] siuba:
sorry for chinese word! really piss off with this reply

ching你係唔係要打橫黎講, 明明個kernel有問題人地report佢聽.. 又唔聽人講覺得係我地自己問題, 佢唔give up有咩做.. 我地唔出聲佢有鬼得改咩
[Samsung Galaxy Nexus] qballe:
imho 144 and 154 are far better than 121 !!

we are discussing about at least 10% battery difference , so :

let the new patch improving stability and performance, nobody stay 24+ Hours away from a battery charger. :p
[Samsung Galaxy Nexus] coolzjai:
I guess you forgotten to do a 'reset timer' after u update the min/max speed?

And for your reference, those middle-range cpu freq usually seldom get use by apps in a constant way, 1344mhz usually when u wake up from idle to do some heavy stuff, or like you start up an apps that need a lot of cpu resource to load data. After all the used-cpu-freq will just drop to 384/729.

My stats usually on Idle>384>729
[Samsung Galaxy Nexus] dpaine88:
Nope this is off a fresh reset of the stats. Ive noticed this many many times but only just now thought of asking about it.
[Samsung Galaxy Nexus] Metallice:
Yeah its not as smart as we all had assumed. There is still quite a bit of variance in voltages for the 192 slot which suggests that smartreflex IS working though... just too aggressively. The same EXACT issue occurs when trying to use smart reflex on 1.5/1.65ghz. For some people smart reflex calibrated voltages for these frequencies are just too low, while for others they are perfect.

If I had to wager a guess on what's going on, it would be that smart reflex would be working perfectly fine if our chips were spec'd to work at these frequencies. For example, we have the "standard" version of the OMAP4460 that isn't supposed to run at 1500mhz. The "high perf" version, on the other hand, is. I would BET that if we all had the "high perf" omap4460 the SR calibrated voltages for 1.5ghz of around 1300-1400 would be more than sufficient for all. Since we don't, I would bet that in order to run these non-standard frequencies "some" phones require more voltage to make it happen. Smart Reflex, obviously, doesn't account for this, resulting in calibrated voltages too low for these phones.

I believe something similar is probably happening with 192mhz.

I'm going to see if I can make sysfs toggles to allow users to enable/disable calbrations for certain frequencies. You can disable SR for certain freqs in smartreflex1p5.c and I'm going to see if this can be made toggle-able.
[Samsung Galaxy Nexus] coolzjai:
translate: "bro, u r just saying something that is unreasonable, i report this because it is the kernel issue, and pissed off that after make such report, ppl think that this is our problem. What else can Franco do if we dont make such complain and report?"

ok... first **** OFF AND GET LOST!! :D

his 'gave up' words in the previous post, purely mean "i have written it so clear, and people are not bother to read it, and further more come and complain for error"

get it?

if not, then write this in your candy ass way.

logs: your mama was a girl.

you complain: why mamma doesnt have angry bird o.0

Edit:

And sorry for my Ruddie attitude, i just simply don't like blaming for nothing.
[Samsung Galaxy Nexus] tcchuin:
It's a known issue ,which smartreflex may UV too much ,resulting instability with 192mhz.

I can understand what you're talking ,but I hope you can understand mine too .
[Samsung Galaxy Nexus] Metallice:
Yeah that sucks. What's worse is its probably only one patch that's causing people issues, while the rest are benefitial. So if you revert them all you lose all the positives as well as the bad patch, and going one by one to find the bad patch could take forever. :( Its just a bad situation to be in... sorry.

(although I do have to admit that while screen on life is consistent, I do get "marginally" better idle drain with 121. Not worth reverting though.)

By the way, I know since then you disabled RCU priority boosting. Did you ever re-enable it? Just a thought.
[Samsung Galaxy Nexus] coolzjai:
am trying now, see if can get what you have observed. Didnt realized this issue before.
[Samsung Galaxy Nexus] franciscofranco:
That makes a lot of sense...I haven't actually thought about that before. Ring a bell if you find anything, I'll be at the computer for the next hours.
[Samsung Galaxy Nexus] franciscofranco:
No I didn't, do you have it enabled on your build?
[Samsung Galaxy Nexus] meilstone:
Feedback#157

changed back to #156 got high idle drain and bad screen on time. battery was to 50% down after surfing 50 minutes. #156 gave me 2h+ at same usage. Im using ondemand and min freq is 3xx mhz.

keep up ur good work. good to go back to a very good kernel nightly. hope you can find the mistake!

cheers
[Samsung Galaxy Nexus] Metallice:
I don't believe so. For the most part I've been using the same /proc/config.gz that you're using so RCU priority boosting has been disabled too. I'm going to reenable it in my next build and see how battery life goes. Who knows? Haha maybe the battery difference from 121 is that simple?
[Samsung Galaxy Nexus] Metallice:
Oh and to people happy with 157...

If you're like most people and you're 192mhz slot is working great on 157, write down the voltage SR is calibrating to so you can set it manually in future builds :)
[Samsung Galaxy Nexus] Serious_Beans:
157 is AMAZING 2% overnight drain with everything on...overnight as in 8hrs. Running ARHD 4.0.1
[Samsung Galaxy Nexus] franciscofranco:
Thank you, welcome to the -5% drain overnight club :)
[Samsung Galaxy Nexus] Gahh Its Lee:
I got my first sod in a long long while last night. Not a huge deal just reporting back. Running great so far super snappy 192-1344 on demand I love this kernel
[Samsung Galaxy Nexus] relax24:
The first franco kernel I used, think it was 121, had 1% drain overnight (8hrs sleep), but on GSM only.

I find wifi increases my drain. Blood wlan_rx_wake. Can't get rid of it.
[Samsung Galaxy Nexus] franciscofranco:
Yeah, probably caused by the extreme low voltage for the 192mhz. I'm closing down the r158 patch window soon for a fast release and it comes with 800mV VDDMIN limit to prevent this kind of crap. I've reverted an OMAP patch that borked the unvervolting interface so users that want to undervolt 192mhz OPP by extreme values can do it, while it stays stable for the rest of the users that don't want to undervolt and want a stable experience.
[Samsung Galaxy Nexus] :
Cant wait for a new Milestone but M3 runs really great for me

Taptalked by GNexus
[Samsung Galaxy Nexus] Hanny:
franco, 192mhz is working good for me for some uptime :) SR calibrated it 710mV.

no crashes nor reboots nor whatever app crashes etc, i think im one of the lucky users.

gonna sleep now and will report back whether long idle will give any SOD or etc for me

by the way, i have a noob question - i have understood that you said in the next releases you gonna push the VDDMIN to 800mV. but for the lucky ones like me, can undervolt to extreme values by ourselves.

however if i still want to enjoy SR (not manual UV) in other frequencies than 192, what should i do? should i just write down the voltages SR calibrates for me right now, and set them manually later on, together with the 192mhz UV :rolleyes:

thank you for your time and work!! =D
[Samsung Galaxy Nexus] Emilius:
I am so looking forward to this.

One other thing I would like to ask. People with good battery life over the night are they on 4.0.3 or 4.0.4 rom. Maybe 4.0.4 dues something extra but if you have r121 kernel there is no kernel suport for it. From other side you can have latest kernel but if you are on 4.0.3 rom that is again same situation. I am for example on 4.0.4 rom. Do you see where I am heeding?
[Samsung Galaxy Nexus] franciscofranco:
Do you have my app? If you do you can change the voltage individually for each OPP so if you want lower voltage for 192mhz you can set it and the other frequencies will be left untouched.
[Samsung Galaxy Nexus] giugiu:
My experience: yes. When I listen yo music (spotify) I use 192 min 1036max Hotplug and lazy governor.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Flukester69:
192mhz is a little retarded no??? I run my phone min 700/729 or 1344/135 and even setting lowest to 384mhz makes zero difference on battery usage. I only use 700mhz as a minimum because it gets rid of the allapps lag or screen lag. Does nobody have a F'ing charger? I got one at home, in car and at my office desk. I gave up on the battery life crap a long time ago. No matter what kernel I use it works out the same. If I want more battery I'll go buy a bigger battery.
[Samsung Galaxy Nexus] franciscofranco:
I don't like the low frequencies, but there are some users that like it, so why not add it?
[Samsung Galaxy Nexus] Hanny:
thanks for ur quick reply! yea, i have it

but upon my knowledge, i need to disable SR to use manual undervolting in your app do i? cause i mean, while i will be lowering the OPP of 192mhz, i want SR to calibrate the voltages for me such as 1240mV for 1344mhz instead of the default 1380mV for 1344mhz if i disable SR :rolleyes:
[Samsung Galaxy Nexus] franciscofranco:
Not sure I understood, but if you want to use your custom values (for example higher voltage than what SR calibrates to) you need SR disabled. If you want custom values below SR calibrated values you don't need to disable it.
[Samsung Galaxy Nexus] Hanny:
oh i see! therefore simply turn on SR and lower the voltage from 820 to 710 in the UV interface will be fine for me :) thank you!
[Samsung Galaxy Nexus] franciscofranco:
Exactly :) 192mhz will calibrate to 810mV by default if I'm not mistaken, then all the way to 710mV if you want, or even further if your device likes it.
[Samsung Galaxy Nexus] PresPPsP:
Hot plug off.
[Samsung Galaxy Nexus] Diger36:
+1. R154 is my personal milestone to which I keep getting back to. Thanks Franco.
[Samsung Galaxy Nexus] franciscofranco:
r158

* A bunch of reverts for stability improvements

* Increase VDDMIN limit from 700mV to 800mV to increase stability for the 192mhz MPU slot

* Custom voltage interface works again

* Small fixes upon the bunch of reverted patches
[Samsung Galaxy Nexus] CaspaTheGhost:
There's definitely a group of us that run 729min, but each to their own. It wouldn't be feasible to remove the lower slots, hey that's why we have Franco's app or similar, so we can make our own choice.

I haven't seen a measurable difference in battery life between 384 and 729, whereas I have seen a noticeable difference in performance - people do need to bear in mind that this can put down to my own personal usage pattern though.

Been running r157 for an hour or so now and all good, but it would be with a 729 min!

All phones were not created equally and each users usage is different, everyone needs to remember that (so asking someones settings doesn't guarantee shiiite!)

My phone awaits 158 like 'crack to the dope fiend!' (and its here so no clucking!)
[Samsung Galaxy Nexus] rmcsc:
Oy, Franco! I'm having a slight problem when opening your app today. It simply freezes and forces reboot of the phone. Has anyone else said anything about this or has my app gone bonkers?

I wiped the phone clean last night, re-installed AOKP M5. Installed 157 nightly and fixed the color and gamma settings from within the app, so it was working.
[Samsung Galaxy Nexus] axne1:
Still following this thread!

Keep Pushing out the projects Franco.

Ps I stay at 729 clock all day. ;)

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] dwang:
can somebody remind me how to check the smartreflex calibrated voltages?
[Samsung Galaxy Nexus] diggmc:
Hi

I noticed 157 spontaneously rebooted twice on me, but I wasn't trying to use Franco's app.

Edited: s/156/157/
[Samsung Galaxy Nexus] dwang:
Noticed that blx doesn't seem to work. Using franco app to set blx values doesn't work.

Doing

echo 100 > /sys/class/misc/batterylifeextender/charging_limit

as superuser doesn't change the value either. Its stuck at 96.

In addition, even though blx is set to 96 and can't be changed, the battery always charges to 100. I think there is something wrong with the implementation. Maybe a mispatched couple of lines?
[Samsung Galaxy Nexus] tcchuin:
I managed to get core uv under 300...

and to ensure that the voltage thingy is actually working, i changed all of the voltage to 50++, and my device rebooted instantly..

but is it true that our device can run and this low voltage??
[Samsung Galaxy Nexus] Sveke:
Flashed 158, mpu voltage stopping at 810mv @ 192, smooth sailing, no reboots.

Thanks Franco.
[Samsung Galaxy Nexus] giugiu:
Anyone noticed heat issues with r158 192mhz (800 mv) Sr on? Even when it's idling with screen off. No reboots tho and no wakelocks..

Flashed back 157 just to test. Now I have same issue.

It seems my gnex doesn't like 192 anymore.

I'll test it better tonight..

Ciao and thank you

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
I dont even reach 40C while benchmarking.
[Samsung Galaxy Nexus] franciscofranco:
Thanks, I will take a look.
[Samsung Galaxy Nexus] krex:
+1 here. R154 is still stable point...
[Samsung Galaxy Nexus] krex:
Hm, I thought so far the answer is...
[Samsung Galaxy Nexus] Hanny:
flashed r158, everythings working together with UV710 and SR on.

had one data drop during screen on (completely no signal) and it recovered itself in 1 minute, probably just my carrier was ****ting in the midnight

oh and while i saw someone said blx not working, i would also like to point out that the dalvikcache to /cache option isnt working as it should because ive tried that option one day ago. after enabling it and manual reboot phone (even for 2 times), /cache partition still shows like 400mb free while my ~200mb dalvik cache is still staying in /data partition. therefore i just unticked that :) no big deal for me, franco you may look at it at your very seriously free time :p

thank you!!
[Samsung Galaxy Nexus] dwang:
Is there a way to do custom voltage for only 192 and Smart reflex for the rest?

In r157 I could do 720 mV@192, but in r158, 192 calcibrates to 810mV.