yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] :
Re,

Hum...Higher than 110°C is definitively a bad idea :eek: (even if it was possible).

Not necessarily a CPU temp limit at 110°C (it's the max temp before the CPU shutdown,right?) but a toggle in your app to choose the CPU temp limit would be great like in Glados but...I think it's not really your line?

Just a toggle to disable the CPU temp limit in your app since it's possible via terminal (sys/module/omap_temp_sensor/parameters/throttle_enabled),in your app it will be more conveniant.

Or a CPU temp limit at 95 or 100°C max with a toggle in your app,but not above?

And with a warning in your app,otherwise here,your mail and your G+ will be filled with messages of people who have activated the toggle (without knowing what they do) and will be surprised to see a CPU temperature to 95°C for example,if you know what I mean...:p:D

Just an idea...
[Samsung Galaxy Nexus] leelaa:
I am not sure, in morfics app, it gives multipliers and a contrast slider, it really makes the screen stand out.

Edit. The settings we have now work well, but it really does look nice with adjustable contrast, just a suggestion to another possible great feature.
[Samsung Galaxy Nexus] yalouf:
Hi, i just bought a galaxy nexus today !

Seems like an awesome phone, and i can hear that Franco kernel is the greatest even from SGS i9000 threads :))

I bought it with CM9 preinstalled, should i make a backup of original google Rom and kernel before ?

Milestone 4 or last nightly ???

I just have to flash that in recovery like on my GS1 ???

Thx !
[Samsung Galaxy Nexus] franciscofranco:
Yes I've been forgetting to add that toggle to the app. I'll add it later today ;)

I'm not sure if what I'm going to say is true (morfic or simms correct me if I am please) but I think morfic built another interface for adjusting the contrast. I can take a look, but I don't want to ruin Trinity's uniqueness picking its unique features into my kernel.
[Samsung Galaxy Nexus] :
Re,

Yeah!Thank you for your responsiveness,great!;)

So it will be a toggle to disable the CPU temp limit and the limit is 110°C before shutdown,right?

No thermal throttle,I mean not a CPU temp limit at 95°C (for example) before thermal throttling when the 95°C is reached or is there still a thermal throttling if the CPU reached the 110°C,not directly a shutdown?

I'm not sure to be clear in my explanations :confused:

We'll see by testing :p:D

;)
[Samsung Galaxy Nexus] odin13:
use the OMAP4 Gamma interface to control contrast? Just an idea ;)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] leelaa:
Does not give the same effect.
[Samsung Galaxy Nexus] pluto22:
It's happened to me about 4 times in the last month so it's not pgm. Usually it's in the morning, my phone is flashing green for a full charge (LF is set for 1hr) but I can't turn the phone on.
[Samsung Galaxy Nexus] justinjustin234:
at what frequency do you guys undervolt for the 1651mhz?
[Samsung Galaxy Nexus] marcuso:
governor-setting not reboot persistant with kernel-updater app .. ?

Hi,

I am using franco-kernel for a while already and love it, but i have an issue with the kernel-updater app:

I have not found a separate thread for the app - that´s why I post here - hope thats ok? ;-)

My Problem:

The governor-setting is not reboot-persistant for me!

No matter which governor I set - it always is back on default (ondemand for milestone and wheatly for nightly) after reboot.

Of course I ticked the setting to keep CPU-setting .. and it keeps Min/Max CPU, but loses governor-setting.

(When I use SetCPU it is fine, but I should not need that, right ? ;-)

This happens with both milestone and nightly and also when using "powermodes".

I am on Modaco IR14 Rom.

any idea ?

Marcus
[Samsung Galaxy Nexus] simms22:
whats the point of undervolting 1651? id want to run 1651 to its full potential, which undervolting would prevent. if you want to save battery life, use a slower cpu speed.
[Samsung Galaxy Nexus] franciscofranco:
Yep I understand what you mean. The default threshold is 75ºC before it starts to throttle. If one wants to play a little dangerous game a simple throttle turn off is available because I don't want to add another sysfs interface to control the temperature threshold. I think a simple turn on/off is enough for our current needs.

Please update your superuser binary or simply try to use SuperSU from Chainfire.
[Samsung Galaxy Nexus] justinjustin234:
i don't know undervolting will prevent it from running at full potential:banghead:
[Samsung Galaxy Nexus] simms22:
theres a small chance that it wouldnt prevent its full potential, it just depends on the sweetspot for voltages for your individual phone. while your phone might run 1651mhz at a wide range of voltages, there will be a particular voltage that it will run the best. thats the sweetspot you want. undervolting can also have the opposite effect, like higher battery drain, just like setting the voltage too high.

edit..

i find my sweetspot by benching the phone at highest cpu/highest cpu and finding the voltage that i get the best, most consistent scores.
[Samsung Galaxy Nexus] arzbhatia:
Franco, PLEASE integrate Contrast Options *Puppy Face*
[Samsung Galaxy Nexus] marcuso:
I am using SuperSU with latest superuser binary already!

And the app also is starting on boot properly (can see the SuperSU-prompt) but as said the governor setting does not stay.
[Samsung Galaxy Nexus] franciscofranco:
No. We already have THREE interfaces to play with the screen. Do we want to cause more confusion to the new users? No. I'm the one who gets the emails, pms, posts etc with questions, I don't have time for more "tech support". Also that contrast option it on Trinity's kernel, if I add it it will be less unique. Do we want all the kernels to look the same with the same features? No. If you want contrast option please use Trinity kernel, its a good kernel. I don't force anyone to use what I build ;)
[Samsung Galaxy Nexus] franciscofranco:
Hmm everything works for me thats for sure. I'll scout a bit with the other devs, maybe they know any solution for some users not being able to have settings persist on reboots.
[Samsung Galaxy Nexus] rogersnm:
If the voltage configuration results in a stable experience then the computational abilities of the CPU will not be enhanced by an increase in voltage. If the voltage is too low to be stable then it will affect your performance, but then that would be the least of your problems anyway.
[Samsung Galaxy Nexus] ceejay83:
i think trinity uses cm9's contrast profile settings which run from 1-10
[Samsung Galaxy Nexus] simms22:
do you have the latest busybox? you can update it via a free busybox updater in the play market. i recommend stericsons busybox updater.
[Samsung Galaxy Nexus] sotoskawasaki:
Franco, this might be a bit irrelevant but its been mention before. Whats the difference between su and supersu? Is it recomented to use supersu to avoid some problems?
[Samsung Galaxy Nexus] franciscofranco:
I don't know the difference. Theres tons of information around the web, a simple Google search will probably answer that for you. I don't touch the su implementations on the roms I use on my devices, if they come with SuperSU I use it, if it comes with Superuser I also use it. I never have problems, with busybox, without busybox... It just *works* for me, so I can't reproduce problems from my users.
[Samsung Galaxy Nexus] simms22:
you would be surprised what kind of difference +/-5mV can do sometimes, even thought you are stable at either voltage. anyways, at 1651mhz, i doubt that there is a huge range in stable voltages, so that could be a moot point.

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

it doesnt. it uses whats already built into phone.
[Samsung Galaxy Nexus] Moz007:
With 1651Mhz slot, i reach 75°C very fast and the game become very very laggy !

It would be very nice if we can adjust the limit ourselves...
[Samsung Galaxy Nexus] marcuso:
Thx ... The strange thing is that all other settings (also CPU Freqs) persist - only governor does not.

... will use SetCPU for now - that works.

anyway: the kernel itself is still great ;-)

Marcus
[Samsung Galaxy Nexus] franciscofranco:
Then disable the throttle limitation, I coded it in for a reason.
[Samsung Galaxy Nexus] andrew53517:
He is right... we do need to keep some difference between kernels, keeps competition and things fresh :)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] rogersnm:
The thing is raising the limit isn't really going to fix that problem. Increasing the throttle point will just mean the general temperature of the phone will increase and you'll still get just as much throttling. If your gaming for a long period of time you'd be better off lowering the CPU frequency to something like 1228 MHz where it can just about sit below the throttle point (for me) under constant, prolonged and extreme load.
[Samsung Galaxy Nexus] simms22:
error correction due to voltage can make a difference. Correction slows you down. Do overs are never efficient.
[Samsung Galaxy Nexus] andrew53517:
I've been running 1.6 ghz and min of 1.92 MHz since release. I just got my first random reboot. All stock voltages. Any ideas? Increase voltage slightly?

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Moz007:
Absolutely not because i don't want to risk a reboot...

Only the biggest games would be limited if we rease up the throttle.
[Samsung Galaxy Nexus] morfic:
From memory the defaults are 61C and 64C to throttle.

You throttle at 75C, be glad Franco gave you more room.

The smaller the difference between the 110C thermal shutdown temp and the top of your throttle range, the sooner your phone will fail.

75C is a good number. Gives you a little extra, is not too close to thermal shutdown to spike over and reboot your phone all the time.

Run 1.5GHz if the phone cooks.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] rogersnm:
Given the (less than) 2 year life span most people seem to keep their phones for this is much less of an issue than when compared to desktops. If you intended to keep it for five years then this might be more of a problem, but I'd imagine the smartphone market will have changed so drastically in that time you'd probably want a new phone by then anyway.

afaik the error tolerance of CPUs is so low that the CPU will tend towards giving up before the error correction makes a noticeable impact on performance.
[Samsung Galaxy Nexus] ssglackey:
Wrong :D

I meant user adjustable value from say 65-100C. Not just on/off toggle for switching thermal throttle. I am able to run at 1,65, but under heavy use phone can reach 110 and reboot. So throttling at 100 will keep the phone up, without reboot.

Edit:

If you don't want to make it user adjustable, maybe you can make three settings, "default 75C", "hardcore 100C" and "off"
[Samsung Galaxy Nexus] morfic:
I wasn't talking about accelerated aging still allowing use of the SoC well beyond the lifecycle of the actual device.

I was referring to the attempts of running as close to the failure protection shutdown as possible for prolonged periods of time.

Their are not quite the same subject.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] arzbhatia:
But there's a reason behind it. Some Galaxy Nexuses have a purple screen issue at low brightness levels. Some people report that it can be fixed through the Contrast thing! It's actually a genuine reason franco! I love your kernel and I've been on it since 6 months now! Plus I bought the Franco app too. We'd appreciate it my man :( Here is the issue - http://xdaforums.com/showthread.php?t=1520566

And another thing, I'd buy the Trinity control application but I don't have a Credit Card :(
[Samsung Galaxy Nexus] marcuso:
just wanted to add that I now also tried with a completely clean Modaco-Custom Rom IR14 (full wipe) and did not do anything else than installing kernel-updater app ... still the same thing (only governor-setting not reboot-persistant)

If this is working fine for others it might be the ROM, even if i can not imagine why that should make a difference on the app behaviour.

next step: try with another rom
[Samsung Galaxy Nexus] morfic:
Franco, just add it. If it has a nice side effect of fixing bugs especially.

I've never seen the purple, so I had no idea this nicely counteracts that.

Interesting,

Thanks.

And to you, TKT is also on androidpit.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] marcuso:
tried with CM9-nightly .. same thing :-(

(also here governor-setting from kernel-updater-app-does not persist over reboot)

to me it seems that it is really the app having the problem.

It is not ROM, SU, busybox ...

I really wonder how it can be this is working for others ?!
[Samsung Galaxy Nexus] fredryk:
Please*
[Samsung Galaxy Nexus] WitchMX:
Just testing 194, I come from Milestone 4, which gave no problems at all and my phone was flying so I had no reason to change. I have to say that I tried Trinity also, but since I flashed Rascream ROM my phone has been super fast, no matter what kernel I use.
[Samsung Galaxy Nexus] syncopy:
You can buy apps from the Play Store using a debit card. I used my VISA debit card and it worked surprisingly well. I remember I wasn't able to in the past, but it works well now. Give it a shot.

Swyped from GNex!
[Samsung Galaxy Nexus] spaceman860:
R194 using interactive gov 726/1651 has been amazing performance & battery life great job Franco :thumbup::D

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] mikeandjaimie:
Has anyone noticed there phone get stuck at a low cpu freq? I use 384/15xx and have noticed three times where my phone seems to run super slow and when I check Franco app it shows it at 192 and won't scale till I reboot. First two times I was on Wheatly, but the last time I'm pretty sure I was on interactive. Nothing specific I've known that causes it
[Samsung Galaxy Nexus] ssglackey:
Same to me, but my stuck between 192-1Ghz. Had to lower top frequency and change it back to 1,6 and maybe I changed governor, but I am not sure.
[Samsung Galaxy Nexus] joeyfong:
seems setting min 729 is better
[Samsung Galaxy Nexus] jangale_asrar:
molesarecoming:

"Franco kernel smashed games, storage, bootmanager - i switched to cm's default kernel"

+1
[Samsung Galaxy Nexus] bat0nas:
How come Franko smashed all that stuff?! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bat0nas:
btw.

I'm always using 192 as min and 729 as max. Have internal feeling that bigger frequences is not good for battery life.

And all of you are using 729 as min :)

Do you really need all that performance?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
I use that when I'm at work, its fine, no lag etc the phone performs surprisingly well. I use it with lazy governor for my own power save mode

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] imreezm:
Hey, same here man!
[Samsung Galaxy Nexus] Theshawty:
I have only bought apps on Play using my VISA debit card. The thing with debit cards is that they can be used as credit cards, but the money doesn't withdraw from a credit amount, it withdraws from your bank account after a reservation has been made.
[Samsung Galaxy Nexus] neopbm:
With this kernel, the CPU is overclocked. Is it possible to go back to original values ?

Thanks
[Samsung Galaxy Nexus] Theshawty:
Depending on the ROM you use, there might be some sort of "performance" menu wherein you can change the clock frequencies and governors, etc.

Or you could buy Francisco's app from Play.
[Samsung Galaxy Nexus] :
Hi,

You mean stock CPU freq?

In Francisco's kernel there is not 350Mhz/1.2Ghz freq but the closest is 384Mhz/1.22Ghz...

It's hard coded in the kernel so you can't change by yourself the available slots except by compiling yourself...

Or use the stock kernel :D

Or I did not understand the question :p
[Samsung Galaxy Nexus] neopbm:
Thanks for the info !

(C'est bien ce que je cherchais à faire, retourner aux valeurs d'origines.)
[Samsung Galaxy Nexus] chrisgtl:
Now using rascream rom with this latest nightly kernel.

Very impressed indeed! Not one tiny amount of lag to be seen and only lost 5%battery in 5 hours.

Brilliant combination of rom and kernel.

Keep up the good work.
[Samsung Galaxy Nexus] spaceman860:
I still believe that but I had a reboot this morning :( here is last kmsg http://db.tt/it1DDpmd

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] yahyoh:
hmm really!!!!!! :silly::silly:
[Samsung Galaxy Nexus] Antob125:
Does Force GPU rendering hurt the battery or the phone in any way?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
No.
[Samsung Galaxy Nexus] Theshawty:
Nope. Some would ever say it gives a smoother experience. It's just that some apps won't work particularly well with that option ticked.
[Samsung Galaxy Nexus] franciscofranco:
I found out with BLX settings don't work on the app, I gave it the wrong path... instead of writing ...class... I wrote ...clas... sigh.
[Samsung Galaxy Nexus] koax88:
Thats why its always charging to 100%,what a relief..:D
[Samsung Galaxy Nexus] rogersnm:
The BLX charging limit is set to 96% in the kernel by default, regardless of whether or not you touch the setting in the app.
[Samsung Galaxy Nexus] franciscofranco:
Users weren't able to change the values in the app for a long time, but I was convinced it was working fine. I've been working on the app for the last 36 hours non stop and when I was reviewing some code I noticed the ****. I also have to change the kernel interface because I set it to 96 its impossible to increase to 100 if I want to. I expect all this be up and running by the end of the day.
[Samsung Galaxy Nexus] mullemulle86:
I am on aokp b39 and with kernel194 my gps isnt working. I switched the Kernel to Milestone 4 and it worked...
[Samsung Galaxy Nexus] andrew53517:
Reflash 194

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] mullemulle86:
Ok just flashed aokp b40 and kernel 194 and gps works fine
[Samsung Galaxy Nexus] franciscofranco:
franco.Kernel updater app 5.3

5.3:

Common:

* Huge security hole fixed. It's absolutely mandatory to update to this version to prevent a future security problem

Galaxy Nexus:

* Add thermal throttle toggle. Will only show up if the kernel supports it

* Fixed BLX bug - now its working as it should. Wont accept higher values than 96 because it needs a kernel fix to make it working with >96 values

* Lots of fixes across the board that won't be noticeable to the average end user but it smoothes the experience
[Samsung Galaxy Nexus] franciscofranco:
It's just a security fix in the app, nothing related to the system as a whole.
[Samsung Galaxy Nexus] derPianist:
Ok. Thank you for the very fast answer!

Great Support. When can we expect the Update in Google Play?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
Users that bought from AndroidPit don't update your app, it will say that its not licensed. I didn't know that AndroidPit uses a different licensing method. I'll see what I can do.
[Samsung Galaxy Nexus] joeyfong:
Just updated before I check your post :(
[Samsung Galaxy Nexus] franciscofranco:
I'm working on the fix.
[Samsung Galaxy Nexus] joeyfong:
It is okay, we can wait.
[Samsung Galaxy Nexus] rogersnm:
Thanks for all your work Franco.
[Samsung Galaxy Nexus] Dragooon123:
Is the GPU on nightly 194 @ 512Mhz?
[Samsung Galaxy Nexus] rogersnm:
As always there are two builds of r194, one with the 384 MHz GPU and one with the 512 MHz GPU.

384GPU: http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/gpu_384mhz/franco.Kernel-r194.zip

512GPU: http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/franco.Kernel-r194.zip
[Samsung Galaxy Nexus] Dragooon123:
Ahh, I thought Franco kernel didn't overclock GPU. Thanks :)
[Samsung Galaxy Nexus] mazubo:
You can use a prepaid credit card. Google "vanilla MasterCard." Hopefully that works!
[Samsung Galaxy Nexus] CommanderDuplex:
Why not a function like Glados ?

will the plastic burn with 110°c :silly: ?!

Lets Test :laugh:

Edit:

Looks that the "turn off" function doesn't work well... i most case the CPU will thorttle @~80°c ??
[Samsung Galaxy Nexus] franciscofranco:
Because this is not Glados ;)

I need help, anyone that has bought the app on AndroidPit throw me a PM please, I need to test if my fix works.
[Samsung Galaxy Nexus] franciscofranco:
Doesnt work well like what? It says it will disable the thermal throttle, nothing more.
[Samsung Galaxy Nexus] simms22:
if the cpu temp is rising, chances are that it wont stop at the exact thermal throttle temp. it could possibly hit up to 10C over before dropping.
[Samsung Galaxy Nexus] marcuso:
tried with other ROMS (full wipe everytime) - and also new version of kernel-updater app, but it still does not work ?!...

Can someone confirm that this is working ?

(just set a governor that is not the default and see if it survives reboot ?!)

All other settings are applied correctly (also CPU Freqs) - only governor is always default after reboot.

My test show that it is either the app that is not working or the hardware (unlikely of course ;-)

Or what else can it be - if i tried different roms, did fullwipes etc ... any idea welcome.
[Samsung Galaxy Nexus] bat0nas:
Hi. My phone started restarting. I didnt have restarts for a few months. And today it restarted 5-6times. Few of them - without a requirement to enter a pin after the phone booted completely.

It restarted with 181 and 194. SR - on. So undervolting is not a problem.

Any ideas?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
New version for androidpit, should work now :)﻿
[Samsung Galaxy Nexus] franciscofranco:
Try the newest 5.3 plz.
[Samsung Galaxy Nexus] RayGarden:
After installation. The shortcut dissapeared (did not happen before). I thought...OMG. But when scrolling through apps, i gladly fount it . Opened the app and it seems to working fine. No popup that it is not licensed.

So many thanks.
[Samsung Galaxy Nexus] marcuso:
As i wrote i already tried that ... same thing (also powermodes are not set on boot - but CPU-freqs are ?).

But i just saw in market comments that i am not alone ... somehow that makes me feel better as i really began to wonder whats wring with my phone ;-)

@franco - if you get this sorted i am willing to donate something ;-)

Marcus
[Samsung Galaxy Nexus] franciscofranco:
It's not a point of getting it sorted or not. My BootReceiver.java class checks for the options in the SharedPreferences interface. If the options met certain conditions it will set the saved values with a shell command.

For example if (cpuBoot) Root.exec("echo 1228000 > /sys/devices/system/cpu/cpu0/scaling_min_freq");

That cpuBoot is a boolean that checks if the set cpu on boot checkbox is ticked. It's as simple as this. I wonder how it works on my device and not on yours. I'm currently using Rascream if that matters.

I really don't know how to do it differently, this is how most applications work on set stuff through reboots. Maybe add busybox bin to assets and use busybox directly from the app? Dunno really, it's hard to fix something that works on my device.
[Samsung Galaxy Nexus] marcuso:
well .. i understand that it really SHOULD work - and CPU-Frequencies for example are set correctly on my device as well, but you can believe me - i really tried everything i could imagine to find out where the issue comes from but whatever i do .. the governor-setting is not set - and as i am obviously not the only one - there must be certain conditions where something in your app is not working. ... i have not yet tried Rascream, but with a few other ROMS - maybe i will try with that as well - just to be sure.

Don´t get me wrong: i believe you are doing great work - but this is really driving me crazy .. of course i can continue to use SetCPU now (which works perfectly) - but i just don´t understand .. ;-)
[Samsung Galaxy Nexus] franciscofranco:
I believe you, I just don't know what else to do. I'll wait if someone has a better idea since I posted how my implementation works.