yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] malaroth:
I kid you not, my fiancées eyes really do this but you couldn't tell as well from the pic until I set the colors through init.d. I guess I'm using a lil lower than Franco... 180 192 200. -5 0 5 -24 Trinity contrast and dithering between 1.0 OMAP gamma and 1.2

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] neo-X:
from terminal how do i change to read/write file system so I can chmod?
[Samsung Galaxy Nexus] malaroth:
Edit oops I was wrong.. osm0sis to the rescue

I believe that's it... I used the GUI from TWRP to mount system then copy file to init.d then chmod 755 the file and good to go

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] osm0sis:
If you're doing it from Android Terminal Emulator / USB Debugging adb shell then just type su first so you have root. Shouldn't need to remount for that I don't think. Then use the command as I altered it in the quote. :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Hey old Gnex crew *tips hat* stumbled upon this thread in my participated after falling foul to the accidental unsubscribe slip of the hand on the N4 thread!

Seeing the release numbers here reminded me of all the development and iterations, the fun we had, but I digress. Franco is making some mad fast progress with his N4 kernel, so much so I'm beginning to think he's controlling time. ;)

Laters.

Sent from my Nexus 4
[Samsung Galaxy Nexus] malaroth:
If I don't mount system in TWRP then I can't view anything in file manager.

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] osm0sis:
Yeah if you're in recovery then you need to mount it. He was talking about remounting though, so I think he's trying to do it with Android booted.
[Samsung Galaxy Nexus] malaroth:
Ah OK. I have issues with android terminal emulator. Half the time it freezes up and won't type

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] neo-X:
Tried "su" first, still says read only file system.
[Samsung Galaxy Nexus] osm0sis:
Weird... okay. Guess I'm just used to doing it from CWM.

For the Galaxy Nexus in Terminal Emulator/USB Debugging adb shell you do it as follows:

su

mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system

chmod -R 755 /system/etc/init.d

mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
[Samsung Galaxy Nexus] neo-X:
Did it work? Refer to screenshot, I can't tell if it did anything.
[Samsung Galaxy Nexus] osm0sis:
Looks good. In Linux "no news" is good news. ;)

If you want to double check you can ls -al /system/etc and ls -al /system/etc/init.d to see if the permissions are correct. If ls -al doesn't work with USB Debugging then do busybox ls -al or ls -l instead because the Android system sh ls doesn't support the same switches.
[Samsung Galaxy Nexus] neo-X:
Sweet, how can I check the file is working for the colours? I haven't seen a difference in colours yet :S

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] osm0sis:
init.d scripts run at boot. When you reboot you'll see the colors change during the Google logo. That means it's worked, and you should see a difference. Remember to set your colors in f.Ku to match.
[Samsung Galaxy Nexus] neo-X:
Thanks! I'll try it soon and report back.

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] Wh1t3Rose:
What extension should be at the end of an int.d script? sh?
[Samsung Galaxy Nexus] osm0sis:
None. My post says that.
[Samsung Galaxy Nexus] Wh1t3Rose:
Thank You
[Samsung Galaxy Nexus] malaroth:
I'm so glad I don't have one of those devices with messed up screens or deficiencies. Then again with dad's company paying for the phone when he got it he'd send it back till he got it right :laugh: I'm kinda not wanting him to upgrade though cuz I like my rom and they don't do SGS3

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!

---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------

Ooh got a question... 4.2.1 uses a new Bluetooth stack right? Is that why half my errors in catlog are Bluetooth?

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] Zadeis:
Just got my first ever random reboot on my Galaxy Nexus after owning for over 3 months. I have the last_kmsg and I'm pretty sure the reboot is CM10.1's fault but I figured I would post it here anyway.
[Samsung Galaxy Nexus] jcmm11:
/etc is a symlink to /system/etc

This becomes important if you want to do anything in there when using the file manager built into TWRP (you have to go in via system to get the correct directory)

---------- Post added at 09:53 PM ---------- Previous post was at 09:46 PM ----------

You can shorten those remount commands. All you need is:

mount -o remount,rw /system

mount -o remount,ro /system
[Samsung Galaxy Nexus] tw1tterik:
flashed 361 two times this past week... got a feeling its sucking out my batt, flashed back to 358, all good... #xylon rom..
[Samsung Galaxy Nexus] osm0sis:
All you did was go back to the broken versions of the same interactive patches. Try r361 again, clear f.Ku data+cache and reboot so that you're running defaults, and give it a couple cycles. :)
[Samsung Galaxy Nexus] Tito2007:
For the people trying to do the init.d folder found this guide ,

http://androidforums.com/boost-mobile-warp-all-things-root/545149-enable-init-d-support.html

Scroll down till you see this post ..JUST UNZIP the file.
[Samsung Galaxy Nexus] malaroth:
=-O I'm a senior member :P broke 100 thanks though I think most was just people agreeing

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] Sik-1:
Pimp my ROM on the market is way easier
[Samsung Galaxy Nexus] malaroth:
This also has a GUI option to change or add to your init.d script... with that said...

If you don't know what you're changing don't do it !!

https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] galakanokis:
This is good advice from os, definitely clear the defaults in the app before or just after you flash the kernel.

Battery life is quite good on 361. This past week I have averaged 15hrs with almost 4hrs of screen time. Wifi or data always on with sync. Fast, smooth with great battery life. Absolutely zero issues here.

G
[Samsung Galaxy Nexus] twistedumbrella:
http://xdaforums.com/showthread.php?p=36361117 <- less dangerous
[Samsung Galaxy Nexus] cschmitt:
Today I got 1d16h30m with 3h20m screen on time. Running r361 on CM10.1, wifi, data, sync always on. Interactive, deadline, 384-1228 MHz, auto-brightness on.
[Samsung Galaxy Nexus] malaroth:
I haven't really done anything but add the color settings to init.d and delete trickster mod but I'm noticing less battery drain with screen on. Weird. I'm pretty hard on my battery so unless I'm chilling at home reading I don't get much more than 10 hours with 3 screen on but I've also noticed my idle drain is almost nonexistent. Kudos to Franco (and Todd Poyner) for the amazing results!

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] mohaimed:
which rom? what settings?
[Samsung Galaxy Nexus] tw1tterik:
So, before flashing kernel (with franco's-app) I should set cpu back to default? Cuz that's the only thing I change. Please correct me if I misunderstood...
[Samsung Galaxy Nexus] joaquinf:
Before flashing kernel go to settings > apps > downloaded > Franco kernel updater and clear data
[Samsung Galaxy Nexus] Khrushy:
That awkward moment when you realise all the weird things your phone has been doing for two days are due to SuperSU bugging out and nothing getting root.

/facepalm
[Samsung Galaxy Nexus] malaroth:
Ouch! I check supersu every so often cuz it resets the "show toast notifications" sometimes and that bugs me. I also check TWRP install openrecovery script periodically to make sure there's not a new one.

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] malaroth:
One other thing that I think helped my battery life is in jrummy's romtoolbox you can disable receivers that can cause wakelocks. Half of them are junk to begin with so if you disable them they're not gonna be turning apps on... it's in the startup manager

JBSourcery 4.1 Franco 361 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Same thing can be done with Gemini App Manager.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] peikojose:
Can you expand a little more ?
[Samsung Galaxy Nexus] gaich:
I think osmosis`s post is more clear for us.:silly:
[Samsung Galaxy Nexus] bigbiceps:
How much screen on time are you getting with xylon Franco combination??
[Samsung Galaxy Nexus] Khrushy:
I usually just avoid problems like this by being an obsessive ROM-flash monkey. I'm on the AOKP nightlies, so I probably update once every 3 or 4 days, and usually do it clean every 2 or 3 updates.

This time though it's been like 5 weeks of dirty flashes. I was pretty much asking for something to break.

Thanks for the thought about apps checking for wake locks though, not a bad idea.

Sorry for the OT posts guys :-p
[Samsung Galaxy Nexus] peikojose:
Can you explain a little more?
[Samsung Galaxy Nexus] AbhishekS:
I apologies in advance if this question has been answered before.

Is there any version for 4.2 supporting PGM?
[Samsung Galaxy Nexus] kissme99:
I really want to try this "tweak" with color settings which was described by osmosis. I read the instruction in his post, but I don't know what I am doing wrong, because it doesn't work for me (I should see the difference on the Google logo, but it has still the same yellowed color)

So, I created a 900colorsettings.txt file, pasted in to the my phone, then I ran Root Explorer app, system/etc and I didn't have there any init.d file, so I created a folder and renamed it to the init.d (someone on this forum wrote that) and there I pasted the 900colorsettings.txt file. I removed the .txt extension and in Terminal Emulator I typed:

su

mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system

chmod -R 755 /system/etc/init.d

mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system

Then I rebooted my phone. After some secs I saw the change in colors (kind of jump from stock to mine color settings)

What I am doing wrong? Please, don't say I am noob.

Thanks!
[Samsung Galaxy Nexus] neo-X:
I believe you also need the same settings in Franco Kernel Updater for it to work properly. That's what osmosis said

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] kissme99:
I know it and I set the same settings.
[Samsung Galaxy Nexus] siealex:
What is Wheatley and how does it work?
[Samsung Galaxy Nexus] neo-X:
Your post is kinda confusing because you first said it didn't change colour but then you said you saw Google change colour. That means it worked.

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] mrm43:
Look here:

http://xdaforums.com/showthread.php?p=36653270
[Samsung Galaxy Nexus] kissme99:
I wrote the colors changed, but they did it some secs after the phone booted (after PIN code), but it should change on the Google logo.
[Samsung Galaxy Nexus] tetrakinitis:
Give the init.d folder 755 permissions, put the 900colorsettings inside and give 777 permissions (all ticked!). Clear data in the f.Ku ( to see if it works) and reboot.I'm doing this with ES file explorer. For me it works!

My presets is 280_292_350, 3_0_9, -24, gamma 5, cab on_1. The best for me! Real white, not blue. For everyone wants to try it.

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] The Gingerbread Man:
The folder init.d needs the permissions set as well as the file, it is easier to do with a root file manager

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
all the franco kernel support pgm.. i have used pgm on all of them with no issues
[Samsung Galaxy Nexus] shawnaye:
Here's hoping the release of 4.2.2 will fix or perhaps introduce new stuff that Franco can provide us with.

As stable as r361 is for me, I'm still facing the wifi disconnection issue that somehow can't be solved.
[Samsung Galaxy Nexus] osm0sis:
My best guess is that you made the txt file by cut+paste instead of downloading my attachment. That, or edited it in Windows and removed the linefeed characters. Or the permissions are still wrong somehow.
[Samsung Galaxy Nexus] smileyanz:
Don't know if gsm is dif but I have no WiFi dropping off or anything what so ever. This is my fav paranoid ROM and franco kernel combination and must say absolutely loving it
[Samsung Galaxy Nexus] tw1tterik:
View attachment 1641681

View attachment 1641683
[Samsung Galaxy Nexus] ÜBER™:
Anybody else getting lockups and random reboots on 361? Tried to get a last_kmsg but for whatever reason it was missing. I'm using the same voltages I've always used without issues. Only thing I've changed is to the row IO and the fact that Franco removed SR. So what's up? I'll get the kmsg next time for better investigation.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Hmm see if you still get the freezes with deadline?
[Samsung Galaxy Nexus] xphone1:
What is the right configuration for play at modern combat 4 without any lags?

Thank you

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] joaquinf:
You need to mod the apk to decrease the graphics details and texture. Follow the instructions posted here using game modder v1.0c and the corresponding mod pack for MC4 then patch the apk with graphics mode zero and enjoy.
[Samsung Galaxy Nexus] Angelakaro:
I play mc4 with no lag without modding the apk

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] nuwan32:
Yea works for me also. The only game that gave me a problem with Franco was nfs most wanted
[Samsung Galaxy Nexus] franciscofranco:
Hey guys&gals! How is everything going around here? I was in CES for the last 7 days, I returned home yesterday :) Is there any problems that need fixing or can I label r361 as milestone? Maybe add the old Sound Control back and let users choose if they want boost or not, at least having a choice is good. What do you'all think?
[Samsung Galaxy Nexus] Sveke:
Sounds good to me. I used 361 the whole time you were gone on numerous ROMs and it was rock solid the whole time.
[Samsung Galaxy Nexus] neo-X:
R361 is very stable. That would be great!!! Thanks Franco!

Galaxy Nexus MiNCO
[Samsung Galaxy Nexus] smileyanz:
I'm using your power saver and must say its spot on, had no sods and surprisingly no lagging when I'm browsing and taking things steady!! The balanced option is my favourite one I use and more then enough for heavy usage. I easily get through the day using these two option's. Honest it merits a milestone Franco!!! Big thanks :thumbup::thumbup:
[Samsung Galaxy Nexus] siealex:
Wheatley often sticks at 1305 for ten seconds or even more at 1..2% load. Is it correct?
[Samsung Galaxy Nexus] aimcr7:
Sounds great, maybe try to bring back SR ;)
[Samsung Galaxy Nexus] osm0sis:
Hey welcome back Franco! I think it's good to go! If you put a warning stating the bugs in the volume boost somewhere then that'd definitely be reasonable. I saw a couple logs with that omap sync error while you were away but they seem pretty rare now. Only other things are I'd personally love to have screen off min in there but I get it if you're a bit short on time. UV would be nice too but I also understand if you want to continue holding off on that one. :good: :)

Edit: Also, congrats on the N10 support! :D
[Samsung Galaxy Nexus] aimcr7:
+1 totally agree with you
[Samsung Galaxy Nexus] Khrushy:
361 is solid IMO. Great performance improvement and I (personally) love RoW. :good:

If you do add the volume boost back in then pretty please make it optional, not compulsory - I already listen with low volume, and the hardcoded boost makes the jumps between volume levels too large for it to be pleasurable.

As Os said, adding voltages back in would be nice too, but at the same time, if you wanted to keep the milestone truly stable, then you could leave voltages hardcoded and add the ability to change them back into a nightly later.

Cheers
[Samsung Galaxy Nexus] siealex:
UV also must be here... but it must be foolproof. If the system hangs up after UV, voltages must be auto reset to original values.
[Samsung Galaxy Nexus] osm0sis:
It already works that way if you aren't dumb enough to put Set on boot for unstable values. Even if you are, there is 10 seconds after boot before the voltages are set for you to get in and disable them. If that isn't long enough for you then there is my Emergency Reset Zip. Hopefully Franco can get around to linking that in the OP soon. :good:
[Samsung Galaxy Nexus] Khrushy:
And what magical system for idiot-proofing would you suggest that can detect what a reboot caused by UV'ing looks like, as opposed to a ROM, hardware or user error reboot?

Edit: It appears Os gave the non-sarcastic answer. Probably better to pay attention to that one.
[Samsung Galaxy Nexus] franciscofranco:
Yeah I can add that screen off thingy ;)
[Samsung Galaxy Nexus] creeve4:
As others have said, 361 has been rock solid for me, no issues at all!

What is the consensus concerning input_boost? Is performance much different with it disabled? Will you be bringing it back Franco?
[Samsung Galaxy Nexus] galakanokis:
361 is great, definitely milestone worthy. I like Krushy's idea about hardcoding the voltages on milestones, sounds like an excellent idea.

Would love to see the usually goodies back in, UV etc and I'm for the volume boost selection as I typically listen with the volume very low.

Great work and I hope you enjoyed CES, haven't been in 15 years. Might hit NAB in April of I can swing it.

G
[Samsung Galaxy Nexus] aimcr7:
You cant have hardcoded voltage and enable UV at the same time :banghead:
[Samsung Galaxy Nexus] Khizar:
if the voltages are hardcoded, then how will you UV them?
[Samsung Galaxy Nexus] galakanokis:
Sorry, read Krushy's post which I referenced, meant to add in the nightlies or test releases for the goodies. The gist of it was there...

G
[Samsung Galaxy Nexus] jackie_jagger:
Did you guys see this? Turns out one of the developer on rootzwiki has got hands on Android 4.2.2 and this is his quote about it:

Link
[Samsung Galaxy Nexus] TheQuarterMile:
Sorry if this question is a repeat but I wanted to know if games like Modern Combat 4 and all play smoothly on r361? cause of the 512Mhz gpu clock. They seem to work fine on the stock kernel.
[Samsung Galaxy Nexus] amith007:
Am using Franco r361.. is this kernal clocked at 1.2ghz by default??? which is the best way to overlock my device with this kernal??? setCPU a good option??
[Samsung Galaxy Nexus] gaich:
As I said earlier, my opinion is that 361 is what the milestone should be like - hardcoded frequences for better stability, leaving the opportunity to play with voltages in nightlies.
[Samsung Galaxy Nexus] aimcr7:
Use franco kernel updater, search it on playstore
[Samsung Galaxy Nexus] alexdemonumber3:
Getting stupidly good battery life here. Everything enabled and at 48% after 14 with 2 1/2 hours screen on.

Bixie stock 4.2.1 with Franco r361 slightly undervolted, over clocked to 1300 with 384 min.
[Samsung Galaxy Nexus] amith007:
Am also in the same config... bixe+ franco r361... are u facing any deep sleep issues??? at times my phone takes 2s to turn the screen on when i press the power button.. :(
[Samsung Galaxy Nexus] Angelakaro:
Give a look at my signature to check my settings,mc4 is the smoothest game that my phone ever run

However,r361 for me is perfect,it may be the first great milestone!

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] supernova_00:
r361 is definitely milestone worry! I'm ready for more changes, my phone's uptime is way too long since we haven't had an update in a week.
[Samsung Galaxy Nexus] The Gingerbread Man:
IMO call 361 m7 will the set voltages. 362 should have the sound mod you described and changeable UV with the screen off min cpu speed added :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] grotesque02:
361 is fast, but in 9 hours in wifi and no use my battery go down 15%.
[Samsung Galaxy Nexus] whitedragonz83:
Sounds like app settings. I can easily hit 1%/hr roughly with a lot enabled unless I have a rogue app.
[Samsung Galaxy Nexus] smileyanz:
Can't b kernel related , think perhaps you have an hungry app somewhere etc. no way WiFi would do that. 4g would if u abused it !!! Running games for prolonged period's would do it but that would b heavy usage!! Leaving screen on without auto brightness also would make a big dent in it!!
[Samsung Galaxy Nexus] timbck2:
Buy Franco's kernel updater app, you'll get everything you need to tune the kernel and support continued development at the same time.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] -star-:
You could try to find the draining app with better battery stats and CPU spy. And your screen of frequency should very low.

Sent from my Nexus 7
[Samsung Galaxy Nexus] peterlemonjello:
Yep, and it works great with #361. Battery life is great. This is the smoothest 4.2.x ROM I've run.
[Samsung Galaxy Nexus] Hans QC:
R361 is the stuff milestones are made of.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] jhearrtot:
very well said sir. :highfive:
[Samsung Galaxy Nexus] AdrienC:
Franco, one issue:

*If I set on colors the green and blue to -255, and leave red on 0, when I try to come back to edit the values, the app force closes.

A tip:

*ship a default color profile, so if someone does this doesn't need to clear app to defaults to manage to edit colors. Now after getting stuck, I saved myself a default before messing with sliders and David my 'night' profile.

Desirables;

*that this FC issue gets fixed, as sometime I want to just increase blue to read something from the UI, I need to get back to full bright and whites for a second and get blind.

*the ability to shortcut the color profiles from a launcher icon or widget, for quick activation as in old CM7 days.

If someone wondered why I do this?

To reduce eye strain, maintain night vision and mess a bit less with my sleep cycle.

From http://en.m.wikipedia.org/wiki/Night_vision

"In biological night vision, molecules of rhodopsin in the rods of the eye undergo a change in shape as they absorb light. Rhodopsin is the chemical that allows night-vision, and is extremely sensitive to light. Exposed to a spectrum of light, the pigment immediately bleaches, and it takes about 30 minutes to regenerate fully, but most of the adaptation occurs within the first five or ten minutes in the dark. Rhodopsin in the human rods is less sensitive to the longer red wavelengths of light, so traditionally many people use *red light* to help preserve night vision as it only slowly depletes the eye's rhodopsin stores in the rods and instead is viewed by the cones. However the US submarine force ceased using red lighting for night adaptation after studies found little significant advantage of using low level red over low level white lighting.[3]"

Ps: I still find red more comfortable than a weak white.
[Samsung Galaxy Nexus] lightosx:
Hello everyone, I just wanted to introduce myself as I've been following this thread since r1xx and have been a faithful franco devotee ever since. Unfortunately my timing was bad and I didn't collect my 10 posts until today, now that I have a n4 and have passed my gnexus to a friend. However, even though I don't have the gnexus in my possession anymore, I still read this thread every day as l love seeing all the changes and improvements being done to the device that made me love android.

I truly can't wait for osm0sis, yellowdie and everyone else whose posts I've been reading daily for the past year to get the n4 and experience the amazing things franco is doing with that kernel. Also knowing all the great things you guys would contribute to the kernel to make it that much better.

To stay a bit on topic, r361 definitely sounds worthy of a milestone. I agree with the min freq for screen off being added, would be great for idle drain. Anyways, thanks to those who read this. I'll be posting around here a bit more now and not just lurking.
[Samsung Galaxy Nexus] nikulogical:
Random post but who was here since the beginning? Remember when '#13.1' was the greatest kernel ever?

Sent from my Paranoid Maguro powered by AK