yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hardikjakharia:
I have the vbus_tuna_otg wakelock for most of my device on time, i had usb port problem, and ghost charging issue and some time later that fixed itself, but i had this problem going on.. any way to let os ignore this wakelock and let phone go to sleep

- Hardik
[Samsung Galaxy Nexus] osm0sis:
You need to read the error. Likely has nothing to do with the kernel if you properly reflashed stock.
[Samsung Galaxy Nexus] Schneewitzchen:
this strange problem happened to me the same way

the issue was solved for me by putting the "sleep 35" command to the second line of the script after #!/system/bin/sh

Give it a try, your script should look like this:
[Samsung Galaxy Nexus] aryan79:
I have spoken with another user and he told me about the "power.tuna.so" problem! I didn't know anything about this problem.

I think that the FK Updater should have a button to fix this! :rolleyes:
[Samsung Galaxy Nexus] reysonance:
This might help
[Samsung Galaxy Nexus] aryan79:
Yes, the user have teached me how to fix the problem via terminal
[Samsung Galaxy Nexus] reysonance:
Ah, good for you then. :)
[Samsung Galaxy Nexus] bat0nas:
My really non professional feeling about 4.2.2+r365: phone is a bit slower and battery life is worse than in 4.2.1.

I won't go into details. I just used same Franco kernel settings as always. No changes.
[Samsung Galaxy Nexus] ashwincr:
miracast

Is miracast enabled in r365? I am running it and can't find an option to enable wireless displays, I was hoping to test with the new f/w on the Netgear PTV3000 box.
[Samsung Galaxy Nexus] lightingcloud:
I tried your script, but still no success. I think I'm giving up and waiting for Minco v6 with new franco kernel which should have those values as default

My first attempt was a file created on PC, then I tried writing it with OfficeSuite directly on the phone, but I had no better luck. :(
[Samsung Galaxy Nexus] ortrigger:
You need to use a simple text editor instead of something that puts formatting in. Something like notepad++ in windows would work.
[Samsung Galaxy Nexus] _chanstar_:
Miracast/Wireless Display is not enabled through the kernel. It's enabled through the ROM. The ROM I use that has it enabled is Shiny (only posted about it in this thread as malaroth was looking for a stock ROM).

As of now, it still hasn't worked with the GNEX. The GNEX is missing the libstagefright_hdcp.so file. Even with the file ported from the N4; using the PTV3000 won't work as PTV3000 REQUIRES HDCP. It seems to not connect right so it'll probably be best if the PTV3000 doesn't require HDCP. The N4 works with PTV300 because it has the a H264 decoder which I assume disables HDCP.

I've read that ALLSHARE works because it does NOT REQUIRE HDCP but I haven't tested it myself or known anyone personally that has tested it. I also heard CM made some changes to their build that works.

I have a buddy I work with that is currently testing all this on his GNEX/PTV3000 and provides me with updates.
[Samsung Galaxy Nexus] shreddintyres:
Hey bud, i noticed an error in your row settings you have rp_read_quantum twice, i think the second entry should have been rp_write_quantum set to 3, otherwise i noticed my device hanging at random when it was trying to set the rp_read_quantum to both 75 and 3 at the same time

otherwise your settings seem to be working fantastically still need more time to test

- Cheers
[Samsung Galaxy Nexus] tw1tterik:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Is there a topic or something about color settings with franco's kernel.. or... which setting works best for you?
[Samsung Galaxy Nexus] Piccles:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Here:

http://xdaforums.com/showthread.php?t=1790325

Paranoid Gnex
[Samsung Galaxy Nexus] osm0sis:
Yup, I'd put the color settings at the top with the sleep 2 so that they're seamless, then the sleep 35 and the interactive and deadline tweaks. No other sleeps needed. Definitely needs to be done with the simple editor in a root explorer app to make sure he's got the correct end-of-line formatting, as was already mentioned. :)

Even better. ;)
[Samsung Galaxy Nexus] shreddintyres:
@osomosis @malaroth @thegingerbreadman @yellowdie @joaquinf @franciscofranco @anyone else ive forgot to ask

hey yall i was doing some testing of Malaroth's row scheduler tunables and i found that they werent setting properly with init.d script while fKU set properly (i understand that fKU does not set row tunables at boot hence the question about init.d)

I checked by running cat /sys/block/mmcblk0/queue/iosched/rp_read_quantum which would return 100 instead of 75 which should have been set by init.d

i got to thinking whether or not the command should look like one of the following in the init.d

option 1: echo "75" /sys/block/mmcblk0/queue/iosched/rp_read_quantum

option 2: echo 75 /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/queue/iosched/rp_read_quantum

option 3: echo "75" /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/queue/iosched/rp_read_quantum

i also understand there is a path heading like /sys/devices/virtual/somenumbericantfigureout/ that will lead to the same place but so far in my experience with init.d using the short cuts like in option 1

so far setting row tunables that malaroth provided earlier have been running great, kinda hard to tell where to change with out just randomly changing the values, any suggestions on best ways to test performance other than just feel since i want to negate any potential placebo effect.

- cheers
[Samsung Galaxy Nexus] osm0sis:
@shreddintyres: Is there a sleep 35 in the init.d you're using? That's necessary preceding iosched and governor tunables to make sure they wait long enough for the boot sequence to set the kernel defaults first, then override them with its own values. Note with the row test values though: Joaquin just recently noticed that there is a rp_read typo (it appears twice when one should be rp_write) in the ones malaroth posted previously.
[Samsung Galaxy Nexus] shreddintyres:
ah i didnt see the bit about the sleep 35 and that was actually me regarding the double rp_read_quantum ill definitely add the sleep 35 in , since i have it in the same init.d script as my color settings i should place it after the point where i have the sleep 2 for my color settings correct?

gonna edit my init d script now, thanks Osmosis
[Samsung Galaxy Nexus] reysonance:
I'm in the same boat as shreddintyres, I can't find a way to test I/O consistently. Best I can do is use the device while a benchmark app does a random write, but obviously that's not enough.
[Samsung Galaxy Nexus] osm0sis:
Ah sorry, missed you pointing that out. My bad. Good catch, by the way! :good:

What I do is I have the ones that set instantly first (read_ahead_kb 512, etc.),

then I sleep 2 and have my color settings so they set at the appropriate time to not mess up my new panel as per my settings post,

then I sleep 35 and do my iosched tunables so that they stick. :)
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Rom toolbox has a read/write benchmark that I've played with for a few but haven't seen any major differences.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] shreddintyres:
ive tried comparing values of read and write in cfbench across different test values but i there is so much inconsistency in the numbers its hard to say, i recall malaroth pointing out that theres some math involved in finding the ideal values, if there is an equation or something of the sort i can try my hand at it to see what we can figure out
[Samsung Galaxy Nexus] reysonance:
For some reason the sleep command will only work if I put it directly after !#sbin/bb/busybox, any idea? The only workaround I can find is multiple init.d script.

---------- Post added at 11:06 AM ---------- Previous post was at 11:03 AM ----------

Yeah, benchmark apps is hardly reliable and consistent, even on multiple runs the number fluctuates so much that the average is pretty much the same.
[Samsung Galaxy Nexus] osm0sis:
That's pretty peculiar. The first line should be #!/system/bin/sh to follow proper shell script formatting, so perhaps fix that up first and see how it goes.
[Samsung Galaxy Nexus] reysonance:
It's the same result with either #!/system/bin/sh and the aforementioned command.

EDIT: The #/sbin/bb/busybox came from leftover script that I wrote when I'm on Lean, it works just fine on franco so I used it.
[Samsung Galaxy Nexus] osm0sis:
Perhaps, but things can be finicky. For example, TWRP hates shell scripts with #!/system/bin/sh and requires that you put the correct recovery ramdisk path of #!/sbin/sh or it will fail; CWM doesn't care either way. Also I notice you've got !# instead of #!, for whatever that's worth. Anyway, just some food for thought; anything is worth a try when troubleshooting, in my opinion. :)

P.S. Welcome to the thread, and thanks for all the help you've already been providing to people. The very knowledgeable and thoughtful answers that you've been giving are great to see, especially when I'm busy with school and work as I am right now. ;):D
[Samsung Galaxy Nexus] reysonance:
The misplaced exclamation mark is is a typo :silly:

It's written correctly on the script.
[Samsung Galaxy Nexus] shreddintyres:
no worries, not a big deal at all :good:

now ive changed my init.d as you indicated and im still having issues it would seem as cat sys....r_r_q is returning the same values as stock

this is what i have as my init.d thus far:

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d

echo 1 > /sys/class/backlight/s6e8aa0/acl_set;
echo 5 > /sys/devices/platform/omapdss/manager0/gamma;
echo -15 > /sys/module/panel_s6e8aa0/parameters/contrast;
echo "-4 0 5" > /sys/class/misc/colorcontrol/v1_offset;

sleep 2;
echo "1750000000 1750000000 2000000000" > /sys/class/misc/colorcontrol/multiplier;

sleep 35;
echo "row" > /sys/block/mmcblk0/queue/scheduler
echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum
echo 75 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum
echo 5 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum
echo 4 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum
echo 3 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum
echo 1 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum
echo 15 > /sys/block/mmcblk0/queue/iosched/read_idle
echo 25 > /sys/block/mmcblk0/queue/iosched/read_idle_freq

i should add that i am running xylon rom and have noticed some peculiarities with it namely with regards to setting "read_adhead_kb" the shorcuts from like above didnt seem to work

how much of a difference does using quotation marks immediately after echo make
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Hey of its not too much to ask would you mind posting your script???? :p:thumbup::D
[Samsung Galaxy Nexus] shreddintyres:
look at his sig, and select the link that says something like my gn settings
[Samsung Galaxy Nexus] osm0sis:
Quotes are only really needed for complex strings with spaces, etc.. My guess is Xylon has a /etc/sysctl.conf or some other method of setting values. If it's sysctl.conf you can just delete it and then you'll have proper control, OR you could just increase the sleep time until after the ROM executes it. Deleting is definitely easier if you know which file and it doesn't affect anything else. :)

Yup. Easy enough to grab that and use it as a base to edit it like I said. :good:
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sorry thread got refreshed as I was typing
[Samsung Galaxy Nexus] georgecarstoiu:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Not sure if it is ROM or kernel related, but this is the third time this week I had to pull out the battery in order to reboot my frozen phone. It all happens while I am updating or installing an app from the play store. The phone just freezes and the only thing I could do is to pull out the battery :(.

I am using CM 10.1 nightly from the 21st with r365 on a GNex. No logs as I disabled them.

Any ideas?
[Samsung Galaxy Nexus] gpzbc:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Your problem has been reported a number of times in the past month or so. (go back a few pages). I experienced the same thing and I am pretty certain it is related to the kernel.
[Samsung Galaxy Nexus] georgecarstoiu:
I know that this was happening with a previous version of the kernel (not sure though which one) but I thought the problem got fixed. Anyway...these things happen when you are on experimental builds :)
[Samsung Galaxy Nexus] Pipusz:
Hey everyone,

I read through the thread a couple of times, because I'd like to use init script at startup, however, I can't get it to work. I have exactly 0 knowledge in these kind of stuff, so I tried to come up with something useful based on yours. Obviously, there is a fcukage somewhere. Nothing sticks and the colors adjust themselves when I enter my PIN (I guess that's normal). My other dilemma is the useage of semi colons.

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d

echo 1 > /sys/class/backlight/s6e8aa0/acl_set
echo 0 > /sys/devices/platform/omapdss/manager0/gamma
echo -24 > /sys/module/panel_s6e8aa0/parameters/contrast
echo "0 0 0" > /sys/class/misc/colorcontrol/v1_offset
#sleep 2
echo "1100000000 1100000000 1700000000" > /sys/class/misc/colorcontrol/multiplier

#sleep35
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 15000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 98 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold

echo "deadline" > /sys/block/mmcblk0/queue/scheduler
echo 1 > /sys/block/mmcblk0/queue/iosched/fifo_batch
echo 1 > /sys/block/mmcblk0/queue/iosched/front_merges
echo 6 > /sys/block/mmcblk0/queue/iosched/writes_starved
echo 3500 > /sys/block/mmcblk0/queue/iosched/write_expire
echo 351 > /sys/block/mmcblk0/queue/iosched/read_expire

I created this with Notepad++, I'm on RasbeanJelly + Franco's r364 (yup, still 4.2.1) and I have TWRP.
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Check on notepad++ if it's in UNIX format. If I remember on windows it writes in Dos one.

When you save it you must be sure that's a Unix text file.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] reysonance:
The color change means you have another app controlling your color, like trickster or f.ku, disable them, or set it to the exact same setting as your init.d script, and it should be fine.

Those apps could also be the reason your values not sticking, try to disable them first, worth a try. As for the formatting, personally I use this, it saves text files as UNIX by default. Notepad++ saves file as DOS AFAIK.
[Samsung Galaxy Nexus] Pipusz:
Thanks. The format was indeed in Dos, but not anymore. :laugh:

Thank you, too. Apparentely, f.ku interfered with it, although I used the exact same values before - or at least I thought I did. But now it works. Good old freezing by Titanium Backup.
[Samsung Galaxy Nexus] lightingcloud:
It finally worked, thanks a lot! This is the file, if someone want to use it. I'll stick with these settings for the weekend, then I'll try row scheduler.
[Samsung Galaxy Nexus] siealex:
R364. Earlier versions worked fine.
[Samsung Galaxy Nexus] georgecarstoiu:
Strangely enough I don't remember r364 giving me any issues. Anyway, other than this issue, everything is really snappy :)
[Samsung Galaxy Nexus] Ronaldo Forenucci:
What's the current "magic number" for read_ahead_kb for GNex (and N7 if we have any dual owners)? Interactive/Deadline.

Thanks!

RF
[Samsung Galaxy Nexus] reysonance:
When it comes to SD readahead, every device is different, mine for example play nicely with lower values like 128/256, for some is 2048. Just try a bunch of values and decide what's best.
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

R364 froze three times in two days...
[Samsung Galaxy Nexus] cucisan:
AW:

for me r364 froze quite often when taking a picture which r361 did not (sry no logs)

testing r365 on 4.2.2 now... lets see if that happens again and if i can get useful logs

(always using default values except color settings)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] reysonance:
Freezes that requires a battery pull won't generate a log anyway, only warm reboots if I recalled correctly.

Could be wrong though, but mine does not generate a log if it's a complete freeze.
[Samsung Galaxy Nexus] ashwincr:
I have a GNEX and a PTV3000 and can test if needed. Let me know if I can help.
[Samsung Galaxy Nexus] joaquinf:
Hi there! sorry for the lack of posts recently but this week has been crazy busy at work. We are in the middle of the international re-accreditation process where i work and i'm part of the lead team so i have zero spare time ATM.

shreddintyres i told to a secret group of people on a secret place :p your findings (typo on row tuneables) so maybe that's why os thought it was actually me who had found the typo. Anyways here are the two working init.d scripts i'm using atm:

RABS to 512

ROW scheduler

For anyone interested, you can follow the instructions posted here with the corresponding file
[Samsung Galaxy Nexus] siealex:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Try to read logcat via adb after freeze... my phone was accessible via adb even if it was frozen.
[Samsung Galaxy Nexus] shreddintyres:
Thanks, i just want to be clear I wasnt in any way upset or anything of the sort :). Honestly i simply thought it was a simple mistake. :good:

the init.d scripts look exactly like the ones i have, im going to have to take a look and see if i can find that sys.conf file that Osmosis mentioned earlier, looks like its purely the fault of the rom im running. Thanks for the info as always :)
[Samsung Galaxy Nexus] osm0sis:
We found 512 to generally perform better for the majority of devices, so that'll likely be rolling out as the default at some point, but do play around and see what feels best for your device. Hopefully the option for that will make it's way to f.Ku at some point in the near future as well. :)

Nah my mistake entirely, I reread and joaquinf clearly said that it was someone in the thread who reported the typo. ..But Joaquin, dude! The first rule of Franco Club is you don't talk about Franco Club! :p

sysctl.conf should be under /system/etc/, or search the thread here since we talked about it awhile back and a number of people found it and tested out deleting it. :good:
[Samsung Galaxy Nexus] yellowdie:
Don't worry, Os, we'll take it out on him later tonight. We will make darn sure he never forgets the rules again. :evilgrin: :biggerevilgrin:
[Samsung Galaxy Nexus] cucisan:
thats what i meant.. thanks for confirmation that this could be working

system freezing and UI freezing can be two different things.. imho
[Samsung Galaxy Nexus] shreddintyres:
I just wanted to apologize to everyone for cluttering this thread, it would seem the entire reason i have been unable to get my init.d script to work appears to be because i had forgotten the all important semicolons (FACEPALM)
[Samsung Galaxy Nexus] osm0sis:
Interesting. They shouldn't be necessary, I just include them as a habit/safety. So I'm thinking you might have some incorrect end-of-line formatting (needs to be just LF, linefeed, for Linux/Unix, but is just CR, carriage return, in Mac/BSD and is both CR/LF in DOS/Windows), since the semicolons would likely make that work because it would signify the end of each command instead where the LF normally would.

I'm personally a big fan of Notepad2, not insane with display options (which I don't need) like Notepad++ but sensible and easy to use. Just click the CR+LF in the status bar so that it's just LF and then you're good to go.
[Samsung Galaxy Nexus] Angelakaro:
I really hope that milestone (or,maybe,newer builds) will have GPU clock set to 384 mhz or 307 mhz. I said it too many times... i think is the only contradictory thing of this great kernel,the only thing to finally bring away instability and heat issues. Francisco,will you consider? I hope so..currently i'm not using your kernel (since 4.2.2) because i want to test a little more how is full stock experience,and i have to say that is really good,almost lagfree but not comparable to this kernel. I'm flashing it just now to see what's changed, but i really hope my request will be take into consideration. Sorry if i'm annoying,regards
[Samsung Galaxy Nexus] osm0sis:
No. This has been answered many times. 512 is stable for ALL GN devices on f.K since Francisco stopped SR calibration on certain parts of CORE. You know how I know? There aren't any artifacts anymore like there were when it wasn't stable. All the arguments by people who want less than 512 seem to be based on incorrect information or are by people who don't understand how it works. There are no heat issues caused by 512. It is only the max and the GPU will still run at 384 or 307 and lower if you aren't running any intensive operations or apps, but having 512 as the max still improves the overall smoothness even when it's not running at it since it has the option to go there for a split second if it needs to. It runs slightly warmer and uses slightly more battery but, again, only when it's at the max of 512, so for normal usage the battery difference is negligible, and for intensive gaming (where you would see more drain) you'd want 512 anyway for the performance. You should be sorry, I'm sick of explaining this.
[Samsung Galaxy Nexus] Angelakaro:
In fact i didn't expect any answer,it was just a little suggestion,even if it was repeated so many times. Thanks anyway. But still i can't understand why to have such a high clock on gpu. I mean, apps and ui are buttery smooth since jelly bean 4.1, even with stock kernel. Franco kernel, especially with latest interactive patches, brought even more smoothness and responsiveness,and we all are happy. However, i don't think gpu is used almost all the time at 307/384 mhz for average usage: i remember that,for example, pulling down notification bar causes gpu to immediately jump to 512 mhz (used a older franco kernel app to test it,new update doesn't show anymore gpu clock in device monitoring so we can't reproduce it easily). Maybe you don't play heavy games on your mobile, but people like me that likes playing knows that after a while thermal throttle become very annoying (and also some game developers sucks in optimizing newest games). Disabling thermal throttle means that in a couple of minutes galaxy nexus can fry eggs with bacon, just for a quick launch if you're hungry (while playing,of course). But,if we can have 384 mhz or 307 mhz and,maybe, disable thermal throttle and underclocking cpu to 1 ghz, i think that most games will run perfectly and device won't get too hot. If you don't agree,or if you think i'm just a retarded that doesn't know how to read and doesn't know that this has been already asked hundred of times,simply ignore my post. I think we must take into consideration my suggestion, most gamers will agree
[Samsung Galaxy Nexus] osm0sis:
I do game and I disagree based on my knowledge of how it works and my experience with it, but you're entitled to your opinion.
[Samsung Galaxy Nexus] Angelakaro:
And do you leave thermal throttle enabled without having annoying slowdowns? (i mean in games like nfs mw or mc4)

I named these two games just to give an example
[Samsung Galaxy Nexus] joaquinf:
EDIT: 4th RULE: Only two guys to a fight :p