yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Schedulers do make a difference. Try them out and see how they feel! :)

I was on bfq but found it resulted in more dropped frames in a game I was playing; experimenting, I found that deadline resulted in the least.

Franco also mentioned he'd enable cfq soon since someone reported it was good for the transition to slow scrolling (hopefully fixing the jitter in the browser at 192MHz min? :D), but maybe he's saving that, screen off min, scheduler tunables, (vibration control?), etc. for the next batch of nightlies after M7.
[Samsung Galaxy Nexus] alexdemonumber3:
I only ever had random reboots trying to **** with r342. Franco's kernels will treat you fine if you don't try to outsmart him and set stuff to crazy settings. About to flash r344, too excited :) don't UV people, its not really that effective and just causes instability

sent from my galaxy nexus

hit that thanks button if I helped you
[Samsung Galaxy Nexus] malaroth:
Thank you Franco! Hopefully this DOES go milestone.... on a side note... AYBABTU! you have no chance to survive, make your time. Ah ha ha ha ha (I love that you included that when you flash it!)

JBSourcery 4.0 + Franco nightlies! Sourcerized to the max! Keep the magic alive.

---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------

We all hope so! Noop does not work well with my device and I have noticed a difference with deadline and bfq. Like you said with games osm0sis, I swap to deadline and tend to otherwise (if I remember to switch back) use bfq.

JBSourcery 4.0 + Franco nightlies! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] unclekeith:
What is the GPU clocked at on r344?
[Samsung Galaxy Nexus] bradm23:
I was the one who reported smooth slow scrolling with cfq. Was really hoping that it was included in 344, but I'll be patient. It is what Google uses as a stock i/o so we will see how it plays with Franco's mods
[Samsung Galaxy Nexus] syncopy:
Going forward, it's gonna be 512 GPU on all the kernels, by default.
[Samsung Galaxy Nexus] allgsmnetwork:
The changelog kernel r344 ?and settings?
[Samsung Galaxy Nexus] Angelakaro:
I don't understand why the gpu is OCed to 512...it causes terrible heating in games and maybe is going to drain battery quickly since gpu speed jumps to max as soon as you put your finger on the screen because of the project butter. Sorry if I ask,but why don't simply put a toggle to change gpu clock? I know this kernel is still a beta and 4.2 bring instability and bugs,but a "forced" GPU overclock won't fix anything. Sorry again if i'm being rude,i don't want to hurt anyone.
[Samsung Galaxy Nexus] osm0sis:
GPU doesn't jump because of project butter. CPU does, and it only jumps to what you set input_boost_freq to. It runs a little hotter while gaming but the voltage isn't such a big deal that it's going to kill your battery much faster.

All in all, Franco worked hard to make 512 stable for every device, the performance gains are worth any slight difference in battery cost, and it's less for Franco to maintain given how divided his time is. It's a win-win, whether you want to accept it or not. ;)

---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------

I got a random reboot (direct to bootanimation) while trying to update to r344.

Here's the bottom of my last_kmsg:

[16095.053466] wl_bss_connect_done succeeded with 00:18:f8:5d:0c:70
[16121.241058] max17040 4-0036: online = 1 vcell = 3908750 soc = 91 status = 2 health = 1 temp = 330 charger status = 0
[16181.251525] max17040 4-0036: online = 1 vcell = 3993750 soc = 90 status = 2 health = 1 temp = 330 charger status = 0
[16241.280731] max17040 4-0036: online = 1 vcell = 3943750 soc = 90 status = 2 health = 1 temp = 340 charger status = 0
[16249.381530] [MODEM_IF] xmm6260_off()
[16249.629333] PVR: PVRSRVDriverShutdown(pDevice=c78c1000)
[16249.629516] PVR: SysSystemPrePowerState: Entering state D3
[16249.629821] PVR: Uninstalling device LISR on IRQ 53 with cookie c794a800
[16249.630004] PVR: DisableSystemClocks: Disabling System Clocks
[16249.651702] omap_temp_sensor_enable:get sync failed
[16249.654907] omap_temp_sensor_enable:get sync failed
[16249.659942] omap_temp_sensor_enable:get sync failed
[16249.667327] omap_temp_sensor_enable:get sync failed
[16249.675170] omap_temp_sensor_enable:get sync failed
[16249.677001] Disabling non-boot CPUs ...
[16249.679046] omap_temp_sensor_enable:get sync failed
[16249.679443] CPU1: shutdown
[16249.680969] Restarting system.
[16249.681152]
[16249.681304] Restarting Linux version 3.0.53-franco.Kernel-nightly (francisco@francisco) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #342 SMP PREEMPT Sun Dec 2 20:39:39 PST 2012
[16249.681335]

No errors detected
Boot info:
Last reset was warm software reset (PRM_RSTST=0x2)

omap_temp_sensor_enable:get sync failed seems like a common theme with the random reboots and SODs that aren't caused by PGM.
[Samsung Galaxy Nexus] NateK:
I keep getting an MD5 mismatch when trying to flash r344 through Franco's app. Anyone else having similar trouble?
[Samsung Galaxy Nexus] malaroth:
I vociferously do NOT accept it. You can't make me :P

JBSourcery 4.0 + Franco nightlies! Sourcerized to the max! Keep the magic alive.

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

Nope. I downloaded the zip just to have but then auto flashed It using fku no problems.

JBSourcery 4.0 + Franco nightlies! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] NateK:
Well, a reboot fixed it - no more MD5 mismatch
[Samsung Galaxy Nexus] afraaa:
Woooow ... I can not believe this franco battery dont drop .. And i thought my battery has problem .. 344 kernel is beyond good beyond awesomeeee uu are amazing man wooow woooooow

Stable awesome performance . tested on high end games .

And i donno how i should thank u franco u made me insane
[Samsung Galaxy Nexus] osm0sis:
It's been like half a day.. tell me you're being sarcastic. :p
[Samsung Galaxy Nexus] duduzinho15:
my phone don't like r444 :S i've tried install with auto flash through fku, .in recovery always getting reboot :S i'm on xenon RC 3, any sugestions for help me ?? in r442 everthing was normally
[Samsung Galaxy Nexus] whitedragonz83:
Did you have voltages/governor controls/frequencies "set on boot" checked?

If so, uncheck and try again.
[Samsung Galaxy Nexus] duduzinho15:
now i'm stuck in google logo
[Samsung Galaxy Nexus] aR_ChRiS:
You know, sometimes it's better to backup your rom before you flash something just in case you screw up something...
[Samsung Galaxy Nexus] calinoii:
My nexus is running verry slugish since I flashed r300 384gpu...i'm on cna 3.8.0 ,using interactive/deadline 325/1228.I have lags even when i scrool through homescreens or drawer pages...what should I do?
[Samsung Galaxy Nexus] franciscofranco:
I dunno what they did with that sensor thing. Can you describe me exactly what led you to the random reboot? Thanks.
[Samsung Galaxy Nexus] _chanstar_:
I had a series of random reboots on r344 but it was my fault.

After default settings, I changed the following:

--CPU Settings to Min 192 and Max 1420

--Gov Control to hispeed_freq 1036 and input_boost_freq 729

--Voltages for 537MHz to 875mV, 384MHz to 775mV, and 192MHz to 735mV

With these changes, all are fine and smooth.

Once I decided to play with the Max CPU Freq to 1804, that was when it froze around 30 sec after and started to bootloop with a few SODs.

I flashed back to Stock Kernel and now back on r344 with the same settings EXCEPT Max CPU Freq is 1420 and all is gravy.

So basically it went crazy with Max CPU Freq at 1804. It was also fine with 1536. Don't feel like testing anything above 1536......scared.
[Samsung Galaxy Nexus] osm0sis:
I've had it happen a couple different times in the JB4.2 series. No obvious pattern so I'm not sure it's reproducible. This time I was downloading r344 in the app to update via autoflash and the app was getting updated via Play Store at the same time. Then bam, back to the boot animation.
[Samsung Galaxy Nexus] MaLiXs:
can i simply change the volt table (UV_mV_table) on each cpu to undervolt... instead of change each volt in the app each time i flash an update ?

it realy fast to edit via my pc !

it could be a way to backup and restore voltage if it not change
[Samsung Galaxy Nexus] grognaz:
Had the same problem and had to remove Franco kernel.

Is it always like that for you or does it take some time like 1-2days till it starts to lag? And if so, does a reboot help?

On my device a reboot helps for 1-2 days then it's back to CPU spiking and lagging:(
[Samsung Galaxy Nexus] calinoii:
It's ok now,I reflashed the rom and kernel and now it's fine. It was the first time when I had that problem...I just flashed the kernel and after switching the gov to on demand and back to interactive it started going wild...
[Samsung Galaxy Nexus] nuwan32:
i actually reported this as it happened to me a couple times. and its random. i dont get a hot boot after every update, but for some update of fku as soon as it installs the app, boom, hot boot. its weird. and fku is the only app that this happens for. im guessing it has something to do with voltages/frequencies.
[Samsung Galaxy Nexus] Khrushy:
lol! Auto-updating the app while flashing the kernel. I'm sure there's a way to introduced more moving parts into that picture, but I can't think of one right now. :P

344 has been running smoothly here since the initial hiccups were fixed. Good stuff Franco.
[Samsung Galaxy Nexus] Atento:
Just one question (maybe an off topic): Is r300 considered stable? Will have any update for 4.1?

Thank you for your hard work.
[Samsung Galaxy Nexus] osm0sis:
Haha yeah, I started the autoflash in f.Ku and then Play Store started its autoupdate and I was like "meh.. we'll see how this plays out." :p

Also woot, 1337 Thanks right now. ;)

Edit: AWW THANKS FOR RUINING IT MALAROTH. :laugh:
[Samsung Galaxy Nexus] malaroth:
I woke up and swapped batteries. On reboot f.Ku updated and I was like "oh please let this not be an Urdu language update" I think I disturbed my neighbors with my whoop of joy. Ever since it's been awesomeness cubed. And ty osm0sis for the point in the right direction. Voltages working nicely

JBSourcery 4.0 4.2.1 preview5 + Franco 344! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] Shadow-Nexus:
Hey os are you still using the settings you posted a while ago or have you changed them?
[Samsung Galaxy Nexus] malaroth:
:laugh: sorry the significance didn't click till I read it a second time

JBSourcery 4.0 4.2.1 preview5 + Franco 344! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] osm0sis:
Thought of that but the table doesn't accept edits like you'd think. It outputs nice like a table but to write to it the format is different.

Check my sysfs commands post for how it actually works:

(/sys/class/misc/customvoltage/mpu_voltages is linked the same as UV_mV_table so you can use either and they'll work the same)

Yes. r300 is rock solid and basically the final unofficial milestone for JB4.1.x-based builds; just like r196 was the final build for ICS and it was an excellent, unofficial milestone. And no, 4.2 is the future.

Yeah bro, my settings don't nevah change.

If I ever adjust the voltages or something I'll go back and update my settings post.
[Samsung Galaxy Nexus] malaroth:
Terribly off topic but.... I think I caught osm0sis at supper

JBSourcery 4.0 4.2.1 preview5 + Franco 344! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] cchhat01:
Camera Sensor bug still present?

Hi francisco,

I've been following this thread and would like to thank you for your hard work in making a very lean kernel which sports a good battery saving/conservative governor.

I do have one question for you which stems from you original post regarding the camera sensor being left open by the gtalk app on bootup, causing battery drain.

Can you tell me if this bug was resolved as through one of your kernel builds or if this is something that isn't controlled by the kernel at all and needs to be fixed by through rom/software update.

Please let me know.

Thanks,

cchhat01
[Samsung Galaxy Nexus] Thracks:
Try "echo 1 >>" with two brackets.
[Samsung Galaxy Nexus] duRin90:
Getting sleep of death in random occurrences. Will investigate more about it and will report my findings here.

I bet it's connected with hotplug tho. Long shot.
[Samsung Galaxy Nexus] loudaccord:
delete

10char
[Samsung Galaxy Nexus] EddyOS:
ETA on next release at all?
[Samsung Galaxy Nexus] Booker-T:
I have read the logcat and I cannot see there is a step running script in init.d

I doubt the function is not running correct.

Besides, I think you need to remount /sys

so add follow code first

mount -o remount sysfs /sys
[Samsung Galaxy Nexus] sishgupta:
Franco juuuust said don't ask for an ETA. But as a rule of thumb never ask for an ETA. Its rude. This is not Franco's job this is something he does because he loves it and he wants to give to the community.
[Samsung Galaxy Nexus] :
The double ">>" is used to append to a file, so this won't change anything. Tried it and had no effect.

Thanks, but this does not work either. It seems like the script is not executed at boot time, because if I run it manually when I am in the OS it works.

I use Bigxie build 9 and this bootloader if this is important.

Sorry for annoying you all, I am just interested in how the init.d stuff works.

And thanks to everyone that tries to help :)
[Samsung Galaxy Nexus] EddyOS:
1. Didn't see he'd said not to ask

2. Was asking because it's not really a 'nightly' if it's days between updates ;)

#12 still going strong btw :D
[Samsung Galaxy Nexus] Booker-T:
YES, I am doubting the init.d is not working but I don't know whether it is function of kernel or rom
[Samsung Galaxy Nexus] odin13:
nightly as in experimental...like cyanogen nightly's ;)

the man is not a robot, you can't expect franco to cough up a kernel every night...i suppose he's got a life too :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] EddyOS:
Cyanogen is meant to be each night ;)
[Samsung Galaxy Nexus] meilstone:
I have the same problem. mentioned it a few pages before. seems like there is a small problem with init.d because my old script does not work anymore after updating the kernel even though ive changed the script. I have changed it now manually through root explorer. only a temporary solution. but maybe franco will find time to take a look at it.
[Samsung Galaxy Nexus] odin13:
'is meant' is the keyphrase here ;)

but above all...cyanogen 'nightlies' are experimental as is franco's kernel...

and now...back on topic! :)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] eiabea:
Sorry for asking again, cause i know you don't like catlog, but i would really like to use your kernel and debug my apps :-D

Could you please release a version with catlog enabled? :-)
[Samsung Galaxy Nexus] esoomenona:
To the person asking about the init.d script for enabling hotplug: did you reboot after setting the script?
[Samsung Galaxy Nexus] franciscofranco:
What? Logcat is enabled and it works just fine.

For the people with init.d problems, it works just fine for me.
[Samsung Galaxy Nexus] :
Sure :) as mentioned earlier, the script works just fine when executing it manually, but it seams as it is not executed on boot. What I noticed: if I look at the properties of the file (/sys/module/dsscomp/parameters/hotplug_enabled) the timestamp is the one of the boot, but there is still a 0 in it. Are those files generated somehow when booting? Perhaps they are overwritten AFTER the init.d scripts were run?

Very strange :confused:
[Samsung Galaxy Nexus] ttlycnfuzd:
What you need to make sure of is two things -

A - that your rom is set up to run init.d scripts.

B - that your rom has logcats enabled.

There were issued with some roms that the init.d scripts were not running properly (at least some for the CDMA GNex). Also, some rom creators like to disable logging to free up resources and to make the rom seem faster.
[Samsung Galaxy Nexus] Dave778:
+1

Was this issue ever resolved?
[Samsung Galaxy Nexus] MaLiXs:
oh ... i'll never put that in init !!!! but I can just past a shell command on the shell... and store this line somewhere in a Txt that could be a nice way to apply voltage faster than use the app
[Samsung Galaxy Nexus] osm0sis:
Oh hell no, I'd never recommend UVing via init.d. I was suggesting you could use them as shell commands like you said. :good: :)

You could apply them with the command, then go in and tick Apply on boot. See if that works.
[Samsung Galaxy Nexus] MaLiXs:
My english is not perfect :D I can mad some mistake !

it is the right command to use ( with my voltage for sure) or it something else ?
[Samsung Galaxy Nexus] osm0sis:
Wrong! Search the thread for "Peruvian llama" :p

Yup. Correct. MPU = CPU in phone/device terms.
[Samsung Galaxy Nexus] malaroth:
:laugh: LOL I thought that looked familiar... been years since I had winamp

Edit** but I didn't conveniently have a llama pic on my phone. That mini donkey was taken out where I just moved from in west Texas

JBSourcery 4.0 4.2.1 preview5 + Franco 344! Sourcerized to the max! Keep the magic alive.
[Samsung Galaxy Nexus] afraaa:
No SOD on 344 ..no lag .no over heating when set cpu under 1.4 and 1.4 itself. and battery mmmmm .. my lovely part .

I am on aosp r6 .

Feels I bought new phone . i wanna thank u again guys . and u specially you Franco for your hard work .
[Samsung Galaxy Nexus] franciscofranco:
Seeing nice posts I guess r344 will hit Milestone pretty soon if no big issue arises :)
[Samsung Galaxy Nexus] allgsmnetwork:
I put the r344 into Xylon ROM 11since yesterday no reboot tested max 1.6 ghz I reduced all CPU voltages of -25 to me it seems more stable than 342 less heat an average temperature of 25 ° with wifi or 3g + data but with antutu benckmark points have been reduced by about 300 points and over 1.4 ghz scores are lower for example, even at 1.6GHz instead of the GPU is good, not bad :good:

---------- Post added at 07:00 AM ---------- Previous post was at 06:37 AM ----------

In Italy they did promotions on galaxy nexus to 269 euro and are the latest productions and have the serial S/N C8 and C9 (you can see behind the battery) have some problems with the sensors not all though you go to Fortune do not know if any of you have this serial :confused:
[Samsung Galaxy Nexus] KGrinols:
I'm not sure if it's by design, but just in case it isn't, I thought I would mention that r344 combined with the Xylon ROM, locks you out of using the 'Advanced' section of the 'System Settings' where you can manipulate the colors, where r342 did/does not. I tried flashing in a few different orders, and ways, but all of them with r344 resulted in a 'greyed out' screen, and going back to r342 corrects the issue.

ScreenShot for reference.
[Samsung Galaxy Nexus] 5pace:
I am using your settings, believe me they are working badass. My question is; have you disabled SR for the CPU, IVA, CORE or not? Currently I have disabled it for CPU only as I am not sure about others.

Secondly, your settings say:

I read somewhere that anything beyond 200 is waste (even CM Nexus' settings says that). And yeah no offence against your color settings :p.

While my color settings are:

EDIT: I was able to grab the info about those colors tuning (attached).
[Samsung Galaxy Nexus] aimcr7:
Its already mentioned, that franco would not implement CM advance settings.

Use F.ku or TricksterMod. :)
[Samsung Galaxy Nexus] KGrinols:
That's not what I meant. The Xylon Rom implements the CM Advance settings. But installing r344 actually removes/restricts that access.
[Samsung Galaxy Nexus] mohaimed:
very high battery drain on r344. i went to sleep with 64%.after 12 hours of sleep i wake up with 39%. all turned off.i am currently on xenonhd rc3
[Samsung Galaxy Nexus] calinoii:
Hey,I have an issue with the r300 kernel...I'm on cna 3.8.0 , interactive gov and the frequencies act like crazy...from 384 to 500 to 700 to 900 and to 1200 mhz verry fast,in like 1-2 seconds...that's why my phone is verry sluggish,what can I do? Please help
[Samsung Galaxy Nexus] franciscofranco:
I dunno, I don't use any type of CM colors on my kernel.

Yes, theres a small **** on r344. I will fix it soon.
[Samsung Galaxy Nexus] calinoii:
Can someone answer me?
[Samsung Galaxy Nexus] grognaz:
Let me know if it comes back after a day or so:what:
[Samsung Galaxy Nexus] calinoii:
I posted again in page 3254..same probl again

---------- Post added at 10:57 AM ---------- Previous post was at 10:52 AM ----------

This is my problem
[Samsung Galaxy Nexus] newman_kg:
same here, stock 4.2.1, back on 342
[Samsung Galaxy Nexus] knightmedz:
+1 on the battery issue. Didn't get this on 342. I got 3% / hour drain after installing 344. Used to be .4% / hour. All stock takju 4.2.1 except kernel and recovery.
[Samsung Galaxy Nexus] sergini:
Todas I had an unresponsive screen after a call, I had to pull out battery. Franco 344 default with xylon. Is this a known bug?
[Samsung Galaxy Nexus] kecinzer:
I can confirm battery drain. Usualy I have 3-4% over night (all data off), today I had 12%. At first I had suspicion to Maps apps, but now it's clear.
[Samsung Galaxy Nexus] calinoii:
Does anyone have any ideas what's wrong?
[Samsung Galaxy Nexus] reflexr:
Same here:(

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] jdec529:
344 does have higher battery drain, but it very smooth. Thanks for the great kernel

Gnex with Rasbean and Franco
[Samsung Galaxy Nexus] allgsmnetwork:
My using/battery with xylon 11 + kernel 344

How do you think the battery life???25% of battery remains :good:

-90 % 2g / 10% 3g +data

- settings 1.3gz /1.4 ghz little test 1.5 after 1.5ghz instable

- much benchmark quadrant/antutu before my reboot and after,my screnshoot valid on 80% battery after reboot

- wifi

- call

- 3g+data

- foto

- other
[Samsung Galaxy Nexus] spupuz:
same here sometimes the screen seems to be "untouchable" i wait some min or i remove the battery :/
[Samsung Galaxy Nexus] calinoii:
That doesn't work for me...
[Samsung Galaxy Nexus] thegtfusion:
Osm0sis?? Is this your persusian llama? :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] allgsmnetwork:
@ franciscofranco,info voltage

@ franciscofranco,

I reduced all voltage CPU - 25 is ok? i have not problem...is possible seem for core/GPU ?i used r344 the best for me...:cool:

Thanks :good:
[Samsung Galaxy Nexus] whitedragonz83:
Most of the frequencies under 1300 will undervolt a lot more then -25 due to Smart Reflex. You probably didn't change anything with that undervolting. Maybe on the 192 or 384 frequency. Watch the device monitor in his app to see the true frequencies to see how Smart Reflex changes villages from Francos high values.
[Samsung Galaxy Nexus] alexdemonumber3:
Definitely only drained from 100% to 94% overnight for me, 6 hours. 1%/hour is awesome. Running r344 like a champpppp. Oh that's stock battery too, my extended one will be even better :)
[Samsung Galaxy Nexus] mpokwsths:
Idle consumption of 1%/hour is absolutely not awesome...
[Samsung Galaxy Nexus] whitedragonz83:
I reverted back to r342. Overnight consumption nearly doubled and screen on time was decreased also. Smoothness felt good. Not sure from the CPU stats if it just spent more time at higher frequencies, or what.
[Samsung Galaxy Nexus] shreddintyres:
first off stop posting every few minutes, people have other things to do and arent always going to be able to help, that said most have moved on to 4.2.1.

you probably need to adjust your governor settings. are you using stock governor settings, any uv/oc

weeks back when i was on aokp jb m1 with r300 i had no issues using it stock just oc'd to 1300, most likely its some setting or something to do with your particular rom setup
[Samsung Galaxy Nexus] alfiemenace:
Can we use the updater up to downgrade also? :)

Stock ROM, custom user.
[Samsung Galaxy Nexus] calinoii:
Sorry for postingbso often. Yes,I'm using stock gov settings...i'm using it with cna for like a month and never had this issue:-/