yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Shetlander:
I had no problems last night and when I woke the phone first thing this morning after a long sleep there was no glitches either. This one is looking good.
[Samsung Galaxy Nexus] coleburns:
Err, don't we report bugs here? Franco clearly stated X and we reported that X didn't work as stated is all. I use his app and manually adjusted.

This does not mean we think his work is any less great than you do
[Samsung Galaxy Nexus] barryflanagan:
I agree.

By the way Franco, the bug in question is that you left out the closing "fi" in your /etc/init.d/00turtle script so it never executes

Hope this helps.

-Barry
[Samsung Galaxy Nexus] franciscofranco:
So I'm sick at home, I got even more free time while university doesn't start, so #15.1 nightly with bugfixes will drop today and possibly the app update with the renewed design and fixed OC/UV interfaces!!
[Samsung Galaxy Nexus] yyz71:
So far this kernel is awesome.

Sent from my pimped out galaxy nexus.
[Samsung Galaxy Nexus] psycho2097:
Awesome! Hope you get better soon though...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] psycho2097:
Where do I put this "fi" ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rascarlo:
so since the boot didn't get much love, here is the inverted version.

[YOUTUBE]3UuX12MLMlM[/YOUTUBE]

here is the zip (NOT flashable) http://min.us/mnlY3Zkeu#20o
[Samsung Galaxy Nexus] jrichardsMav:
noob question, do i just flash this with cwm?
[Samsung Galaxy Nexus] psycho2097:
No you dont, it says NOT FLASHABLE. u copy the bootanimation.zip file to /data/local folder
[Samsung Galaxy Nexus] rolear8:
Yes just falsh it if you mean the kernel, i always wipe cache and davilk before.
[Samsung Galaxy Nexus] psycho2097:
just a thought, but is it possible to flash a kernel by flashing the boot.img via fastboot?
[Samsung Galaxy Nexus] franciscofranco:
Yes, that's how I always flash it since I already have the sdcard bin etc on system.
[Samsung Galaxy Nexus] odin13:
wow franco...so far the francoTurtle governor works out really great...

thnx!
[Samsung Galaxy Nexus] EddieN:
Thanks a lot for giving it a go! I asked a few hundred pages back about the same issues after #9.1 but never got a response. I wonder why it's performing so badly for me.. I'll have a go with another rom but it's seriously killing me as it's worked flawlessly with scrolling and zooming once before but never again, even after full wipes (no TB restores either).

In any case thanks again for your time (and data)! At least I know it should work fine :) will go back to testing and researching
[Samsung Galaxy Nexus] psycho2097:
fastboot flash:raw boot.img or flashboot flash kernel boot.img? then i just copy he init.d scripts? n wat sdcard bin? :O **** i m missing sumthing... maybe thats y i m gettin ****ty baattery (~20ma on airplane vs ~8ma on imoseyons)
[Samsung Galaxy Nexus] franciscofranco:
What do you mean with badly? There isn't a single user with that problem, so it's something at your end =/
[Samsung Galaxy Nexus] jrichardsMav:
I was referring to the kernel.
[Samsung Galaxy Nexus] psycho2097:
@eddieN try bigxie's apex rom.
[Samsung Galaxy Nexus] minipaolo:
You missed the point.

It's not about having to set it back to 1000 (or leave it to 1200 which is good anyway), but people were just wondering if the new governor was actually working fine, as it was on different stock settings than what they expected it to be.

Nobody is complaining.

Calm down, drink something and relax.
[Samsung Galaxy Nexus] franciscofranco:
It's ok, I did some **** in the init.d script. It's now fixed in 15.1. It will always boot up as 1000mhz unless people set another governor and freq + set on boot.
[Samsung Galaxy Nexus] psycho2097:
Whoa! 5000th post!!!!

always doing crazy ****, you are. Strong, with you, the force is. bring on 15.1, please do. :D :D
[Samsung Galaxy Nexus] AdrianE46:
Seems to be working rather nicely, but i do have one small bug to report. When i pull the notification area down it says @@ instead of the carrier name on the bottom. Running aokp 20 and franco 15.
[Samsung Galaxy Nexus] laserprom:
Whit UV? If yes pleas write data.
[Samsung Galaxy Nexus] aron7awol:
I decided to take some time today to try to optimize my voltages...

I thought a good starting point would be the stock voltages. It turns out that the stock voltages are scaled almost perfectly linearly with frequency. Great, that means it is easy to extrapolate what stock voltage would be for 1000 MHz and 1350 MHz, 1324 mV and 1477 mV.

Here's a chart showing stock voltages (including my extrapolated values), some other "standard" voltages, and then some recommendations based on reducing stock voltages by the same percentage:

350 700 920 1000 1200 1350

Stock 1025 1203 1317 1324 1388 1477
Franco 900 1000 1100 1200 1300
Apex 850 975 1050 1175 1225
~83% of Stock 850 1000 1100 1150 1225
~81% of Stock 825 975 1075 1125 1200

I think pretty much everyone should be able to run 83% of stock and have it be completely stable. It matches up very well with the default voltages in the Apex kernel, and the middle frequencies, 700 and 1000, match up perfectly with the default voltages in the Franco kernel. I think it makes a lot of sense to scale down each voltage by the same percentage.

Personally, I'm running the ~81% of stock values.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for taking the time to do that.

In 15.1 I increased 1000mhz voltage to 1150 for stability purposes. This is what I've wrote in my commit:

Since we were already undervolting it from factory settings for the

920mhz slot, running the same voltage for the increased frequency will

most likely cause stability issues, so we increase it by 50mV which

won't impact the battery life at all as the device spends more time at

700mhz than the rest of the frequencies all together.
[Samsung Galaxy Nexus] aleve1983:
Franco When you lower the notification bar You can see at the bottom of the screen becomes brighter. So it s possible increase the display brightness!

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] stesmi:
Assuming "300" is a typo and you mean 350?

// Stefan
[Samsung Galaxy Nexus] EddieN:
UPDATE: Just wanted to give an update to say that I'm still on AOKP milestone 3 with franco 15 and tried the site again before flashing to bigxie's apex tom and it's buttery smooth.. It seems to be fluctuating. Low memory issues? Doesn't seem right.

If I could make a recording of it I would, but it's just generally laggy, unresponsive/choppy when zooming, really sluggish (i.e. i pull my finger to pan around the website and it pans ~1.5-2 sec after). Only on that site too, afaik. I haven't come across a more meatier site yet.

I realize it must be something on my end, I just don't know what. I don't really know what else to 'do' before reflashing a rom other than doing full wipe (data/dalvik/cache). Maybe I should try wiping /sdcard as well?

Anyway, I didn't want to make it seem like it was a problem with your kernel per se, I just wanted confirmation from someone else that the site indeed works fine on a GNex with your kernel so no hard feelings! :) I have no doubts in your kernel at all, but now that I know the site DOES work (and HAS worked for me before, flawlessly) it's got to be something on my end. I'm going to reflash to another rom and keep testing.

Thanks again for a great kernel and updater app, and most importantly get better! :)

Will do!
[Samsung Galaxy Nexus] aron7awol:
Yes, thanks, I fixed it.

---------- Post added at 03:40 PM ---------- Previous post was at 03:32 PM ----------

I see, thanks for the update on the current voltage status in 15.1...

Maybe you want to tweak your voltages slightly to make them scale more linearly like the stock voltages do? Take a look at the ~85% values below:

350 700 920 1000 1200 1350

Stock 1025 1203 1317 1324 1388 1477
Franco 15.1 900 1000 1150 1200 1300
~87% of Stock 900 1050 1150 1200 1275
~85% of Stock 875 1025 1125 1175 1250
~83% of Stock 850 1000 1100 1150 1225
~81% of Stock 825 975 1075 1125 1200

Those ~85% values match up well with where your voltages are at now, but they also scale linearly like the stock voltages. What do you think?

Edit: Added ~87% values, which match up even better.
[Samsung Galaxy Nexus] franciscofranco:
I think that's a reasonable suggestion. Will do.
[Samsung Galaxy Nexus] psycho2097:
Just for the heck of it, try fixing permissions in CWM. Doesnt hurt. plus delet init.d folder, clear cahe, dalvik and flash imo1.7.4. juz try.
[Samsung Galaxy Nexus] bimo2700mf:
my UV configuration

350/700/1000/1200 = 750/875/1000/1125

I've tried for few hours since my last freeze and I think now is already working fine

My last freeze problem I think because I set 975mv on 1000mhz

aokp 20 / f.k#15 l f.k turtle 700-1000
[Samsung Galaxy Nexus] aron7awol:
Yeah, I'm sure I could push my voltages even lower, but I'm really just trying to find a level where I'll get some good battery savings, but also where I can feel confident that my device will be 100% stable under every possible load it will face, at any temperature it may be at.
[Samsung Galaxy Nexus] ChongoDroid:
F.turtle is stupid fast, F.gazelle is ludicrous speed!
[Samsung Galaxy Nexus] Shetlander:
Franco

Have you seen the inverted boot image. Its very nice ;).

Also have you thought about altering the other speeds. Maybe linear (like the suggested voltage) like 350Mhz, 600Mhz, 850Mhz, 1100Mhz and 1350Mhz?
[Samsung Galaxy Nexus] grinch247:
what I would consider hard use:
[Samsung Galaxy Nexus] franciscofranco:
Nah, the rest of the frequencies are just fine. The only one that I might still consider changing is 700 to 500 or something, but it's not planned as of now, just an idea.
[Samsung Galaxy Nexus] ro_explorer:
Well, my screenshot is similar but a little different in terms of time window :-)

2h display time.

// sent from my green robot //
[Samsung Galaxy Nexus] franciscofranco:
#15.1 is out, check it out.
[Samsung Galaxy Nexus] psycho2097:
first! Man,I totally hound your forum! Lol :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] samizad:
Francisco,

A small bug in the updater app. When I did the check for kernel updates, under Status: it just says "is available" without giving the kernel nane and rev.

[EDIT]: It must have been due to the amount of hits your FTP site is getting. I tried again and it's working fine. The download speed is very slow but that is to be expected only a few minutes after your post.
[Samsung Galaxy Nexus] Puzzlegirl:
Nah, mine says "Status: 3.0.18-franco.Kernel-nightly-15.1 is available"
[Samsung Galaxy Nexus] franciscofranco:
Sorry, not for me :/
[Samsung Galaxy Nexus] lehoule:
Idea for your app : add the option to activate a notification when a new kernel is available !
[Samsung Galaxy Nexus] winner00:
Thanks for the 15.1 update! CPU Settings work great now in CM9. Thanks again!
[Samsung Galaxy Nexus] ArmanUV:
Franco,

Does the modifications you made to sd card's ext4 file system have the potential to cause problems if you switch to another kernel?

I was on 14.4 and the I flashed leankernel to check it out. Today when I tried to update from AOKP b21 to m3, cwm crashed when I selected to "install from zip". I tried flashing a different file, reflashing cwm, factory reset...nothing worked.

Finally I deleted everything off the sd card with root explorer, copied the aokp zip and it worked!

that's why I am thinking there is something wrong with my sd card partition.

What do you recommend? What about formating /sdcard with cwm?

(Another weired thing: after I deleted everything on /sdcard with root explorer, I connected my phone to my mac and opened android file transfer. All of my files were there! :eek: I opened root explorer and it correctly showed nothing in the sd card. How is that even possible?)
[Samsung Galaxy Nexus] acatabian:
hey guys

how can i enable hotplug manually? i dont have a credit card so i unfortuantely cant buy anything off market.

thanks for helping
[Samsung Galaxy Nexus] dyndragon:
Regarding NFC...since it was mentioned in this thread before, just checking my thinking here.

Even if I wipe /system and /data and start fresh, I can't get NFC to work in the CM9 kang nor Apex ROM, franco.kernel or default kernel of the ROM. If I load a stock 4.0.2 image, NFC works fine--that is, I can use any NFC app to read my tags.

Can the kernel affect NFC functionality? If I dis/enable the NFC option in settings, logcat shows some output and no errors or warnings, and Google Wallet can activate properly. Any thoughts?
[Samsung Galaxy Nexus] johantheolive:
First post...

To disable: echo 0 > /sys/module/dsscomp/parameters/hotplug_enabled

To enable: echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------

As for the file issue, that's because of how the phone handles MTP. It creates a cache of the files that updates infrequently. I believe you can download an app that will force it to refresh or if you reboot it'll refresh.
[Samsung Galaxy Nexus] bimo2700mf:
Got this answer from

http://goo.gl/NK5JM

DISCLAIMER: LIKE ALL ROOT ACCESS TYPE ACTIVITY, THIS CAN MESS YOUR PHONE UP. MAKE SURE TO NANDROID AND I DISCLAIM ALL LIABILITY FOR ANYTHING YOU DO TO YOUR PHONE (also, this is only for LTE GNEX and I only tried this on my own phone running AOKP 21 and FRANCO 13.1)

1. create a text file (in windows you can right click in a folder and select new --> text document) containing the following two commands:

#!/system/bin/sh echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

2. after saving this file, remove the .txt extension. name the file whatever you want, but make sure it has no extension. my file is name "hotplug" - no dot anything.

3. copy the file to this directory on your phone using root explorer (you will probably have to mount as r/w first): /system/etc/init.d

4. long press the file on your phone in the init.d directory and select permissions (again you'll have to be mounted as r/w). make sure the permissions are checked for "read" 'write" and "execute" for all three owner group and others. leave the special permissions blank.

When you look at the file (in the directory, not its contents) after doing this it should say rwxrwxrwx next to it in small letters. also viewable by long pressing on it and selecting properties.

5. reboot.

6. check if your script worked by going to /sys/module/dsscomp/parameters/ and long press on hotplug_enabled and select view as text at the bottom. hopefully, it says 1.

7. profit
[Samsung Galaxy Nexus] johantheolive:
I've seen this when attempting to check for an update and there is no internet connection.
[Samsung Galaxy Nexus] MountainX:
As for ext4, that is a file system and it is not affected by deleting files with Root Explorer. Even if you delete every file, the formatting and file system of the partition will not change.
[Samsung Galaxy Nexus] rabhw:
How are you guys setting the voltage for 1000mhz? I'm assuming not using franco's app, since the app only seems to have UV slots for 1350/1200/920/700/350.

Would that be something you consider adding to the app in the future franco? Especially since turtle is the default.
[Samsung Galaxy Nexus] bimo2700mf:
Use set CPU
[Samsung Galaxy Nexus] franciscofranco:
Yes, I'm working in the app as we speak, that is already being fixed. I hope to push the app update today depending on my coding speed.
[Samsung Galaxy Nexus] yeeson:
Great god！

CM9 of Color Gamma Tuning can use?
[Samsung Galaxy Nexus] bradm23:
Franco,

What where the voltages of 15 vs 15.1?

I notice a little judder while scrolling in the browser that wasn't there with 15. I am guess it might be from lower voltages?
[Samsung Galaxy Nexus] minooch:
OR...

Support Francisco & buy his app - As it has ALL the functions you need

https://market.android.com/details?id=com.franco.kernel
[Samsung Galaxy Nexus] AzzaD:
+1

10char
[Samsung Galaxy Nexus] kin24173493:
just flashed #15.1. smooth as silk. great job Francisco thank you.
[Samsung Galaxy Nexus] AzzaD:
does Cleaner.sh execute itself on install or do we have to do it ourselves?
[Samsung Galaxy Nexus] ccfly888:
just flashed #15.1 and AOKP Milestone 3.

Everything runs smooth.

Tried Cifs manager, getting mount error: cannot access needed shared library

Has anyone else experienced this problem?
[Samsung Galaxy Nexus] ArmanUV:
I know that. I'm just saying that since the problem was resolved by deleting everything off /sdcard then it obviousely has something to do with it. If franco made a change to the ext4 file system (according to the change log) then wouldn't flashing a different kernel cause problems?

If that's not the case then I don't understand how my problem was solved by wiping /sdcard. Before that I deleted /sdcard/clockworkmod and that didn't solve the problem. So what could?

Oh and franco what do you think about dividing the releases into a stable and experimental branch? A lot of us rather flash new releases every couple of weeks rather than every few days. This way both people who want the cutting edge release and people who prefer better stability benefit.

I know it is more work for you but I hope you consider it :o
[Samsung Galaxy Nexus] nrgaway:
+1

It has become so much work trying to keep up with frequent updates, and I personally prefer known stable releases over experimental since there have been so many versions with problems. I am still on AOKP Milestone 2 for same reason and will consider switching to 3 once I hear its stable enough.

Edit. Once an experimental release it considered stable; just rename it with no changes to stable.
[Samsung Galaxy Nexus] wallendiaz:
Hi franco,

Im using the kernel version #15.1, with eagleblood ROM 1.9, and I feel the touch response is not the same like with the kernel #15, with #15 is better for me.
[Samsung Galaxy Nexus] drewtang:
I would recommend, for people having issues, I've been flashing faux's reset kernel in between updates, and have been having no issues whatsoever.

@Franco, gotta say I'm impressed with the updates, running the turtle governor at 1ghz, and my phone still feels quite smooth, nicely done sir.
[Samsung Galaxy Nexus] MountainX:
I looked through your github repo and the usbserial drivers are all listed as being included in your kernel. For example, look under drivers/usb/serial and you'll see cp210x.c, which is the exact driver I am looking for. (This driver allows connecting to USB GPS devices, personal weather stations, measuring instruments, Arduinos, etc.)

Since the driver is part of your kernel source, how can I enable it? Thanks.

References:

http://www.etheus.net/CP210x_Linux_Driver

https://code.google.com/p/usb-serial-for-android/
[Samsung Galaxy Nexus] kilian7th:
Thanks for your work Franco, will try15.1 today ...

Best regards ...
[Samsung Galaxy Nexus] franciscofranco:
Executed during flash automatically.

I'll think about it once the app update is finished ;)

I'll look at that tomorrow.
[Samsung Galaxy Nexus] MountainX:
Thank you!!!
[Samsung Galaxy Nexus] danielvc:
15.x really rocks my Nexus again, thanks for your updates (and loving your app too!)
[Samsung Galaxy Nexus] stesmi:
Regarding versioning : I think the easiest way for users would be to either have two branches OR just simply:

Next release is 15.2, this is the beta, next is 15.3, also beta, next is 15.4, also beta. When you see 15.4 is stable, release 16, which is a stable release. Then add 16.1 which is beta, 16.2 beta, etc, when 16.x is stable => release 17, etc.

That way people that don't want to update all the time grab the without-dot version and those that like flashing everything in sight can grab the dot-releases.

And yes, I do mean that 15.4 (ie the LAST 15.x) should be identical to 16, bar the version number. Don't change a thing in them. People that run the dot-versions will then just skip 16 as it doesn't actually change anything and wait for 16.1 (or they will, at their own discretion, update to 16 just to have the latest number).

What do you think?

Oh and I've said it before: Love what you're doing. Keep it up (me and my wife both bought the app to show how much we care).

Also: Me and my wife were both some of the problem-users of 14.x with nothing working (didn't try 14.4 though), 13.1 worked fine and 15 is stable for us both. Great job!

// Stefan
[Samsung Galaxy Nexus] rye&ginger:
Stefan makes a good sugestion. Im not one to try kernels that often, Id prefer 'stable' releases also.
[Samsung Galaxy Nexus] stesmi:
Ok, 15.1 is bootlooping for me. I can still get into CWM so I'm good but ...

Going to try to set an init.d to set voltages to standard to see if that helps.

EDIT: Tried going back to 15 and that locked up on the boot animation and bootloops after that. So I went back to 13.1 and everything works. I went in and removed the turtle, overclock and undervolt scripts manually. I then upgraded to 15 again and it works, it's set to 700-1200 on Turtle. Changed max to 1000 and went to CWM and installed 15.1. It works now.

EDIT2: Changed to Gazelle with 700-1350 and running StabilityTest right now. SO far 2 successful runs (it's temp throttling me though) and stable so far. I'm going to run at least 10 runs before I'm slightly more sure it works.

EDIT3: 5 stable runs later and I'm going with the one that changes frequencies all the time. So far 2 successful and counting.

EDIT4: Ok, 5 Scaling Tests later and it just seems stable. So Thumbs Up! I could suggest you also delete the undervolt script in cleaner.sh cause maybe that's what was causing it. I mean, I really didn't do anything else than I wrote above to make it bootloop and then work again.

// Stefan
[Samsung Galaxy Nexus] d3rutat:
15.1 working great for me using francoturtle and default freq/volt. Thank you Franco!
[Samsung Galaxy Nexus] laserprom:
exelent idea Stefan
[Samsung Galaxy Nexus] 3c:
Running 15.1, simply great!

Thanks Franco for this last update!

I'm very happy with recent changes:

- bootanim removal (though I didn't complain, it takes a minute to put back the one i use)

- CPU voltage interface fix (no more 10/15 seconds lag)!

- hot_plug work well for me.

- No GPU OC, was never interested in this and didn't find any improvements in it!

A few suggestions, if I may that might be of interest:

- hot_plug option 2: all the time, not just screen-off, so CPU1 goes offline when not needed.

- Min CPU default to 350Mhz

- or min CPU freq during screen off should not be reset to 700Mhz (it seem to reset itself to 700, might be the hotplug option doing that?), so whatever we use as the minimum will be used during screen off.

Overall, you have a great kernel, getting better along the way. Great work, keep it up! :)
[Samsung Galaxy Nexus] opensourcefan:
On 15.1 with AOKP 20 and my phone has never run better. This is an excellent combo and turtle is amazing. Battery life is ridiculously good.
[Samsung Galaxy Nexus] d3rutat:
I tend to disagree with this suggestion. I think it would only uselessly complicate the life of franco, since it would effectively double the support requests he would have to answer. I say uselessly because:

1. most of the nightly releases so far have been stable

2. seeing if a release is stable or not is just a matter of waiting a couple of minutes until somebody else tries it first

3. even if the general conclusion is that a specific release works, it can still backfail for you

4. worst case scenario, you should already have nand backups in case something goes wrong
[Samsung Galaxy Nexus] minipaolo:
GREAT!

M3 + franco 15.1 works extremely well. :cool:

Just a little thing (never happened before): WiFi and 3G bars went grey since when I flashed 15.1. I'm not having any issue as it seems to work normally anyway.. I just don't know why it doesnt go blue anymore! :confused:
[Samsung Galaxy Nexus] danielvc:
Exactly. And if you find a release stable (like 15.0), then you stick with that unless you hear good things about it here. I only had problems with 14.x, so I really had only stable releases :-)

---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------

Check my posts in the Milestone-topic. I've had the same problem, reboot and a bit of tweaking with power control fixed it ;)