yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nikulogical:
Did you try the wifi pm fast option, its seems to be working for me *knock on wood*
[Samsung Galaxy Nexus] farazafs:
Guys ,

what is the file which i need to download ?

Milestone 3: http://minooch.com/franciscofranco/Galaxy Nexus/

Nightlies: http://minooch.com/franciscofranco/G...xus/nightlies/

franco.Kernel updater app: https://market.android.com/details?id=com.franco.kernel

franco.Kernel updater app from AndroidPit: http://www.androidpit.com/en/android...Kernel-updater

??? i am on AOKP rom
[Samsung Galaxy Nexus] moe6:
Buy the franco.Kernel updater app: https://market.android.com/details?id=com.franco.kernel it will make things easier for you to understand if you couldn't from 1st post.

Both Stable (Milestone) and Nightlies are there, flash whichever you prefer but I think most here are on Nightly's. The updater app makes it easy to keep updating it as often as you want (or as often as Franco is nerding out on his kernels :D)
[Samsung Galaxy Nexus] farazafs:
Thanks a bunch Buddy ! that helped a lot
[Samsung Galaxy Nexus] hitman818:
I have noticed that stock kernels run better than the new version kernels like 3.0.32. Iuse templebrun to check the performance and smoothness. Francos 3.0.8 runs far smoother than the newer kernels. I dont know if its just franco kernel, but these new kernel seem buggy.
[Samsung Galaxy Nexus] The Gingerbread Man:
2 nights have passed where I have had no data drop over night (or during the day). Coming to think of it since I updated my rom to paranoidandroid 1.1 I haven't had a single data issue. Perhaps coinsidence I don't know, 175 and pa 0.9 did data drop but 175 and pa 1.1 i had no issues, maybe something else rather than just kernel is to blame for this issues, something to do with roms. I am using the same xxla2 radio and matching ril. can't wait for m4 now :)

Sent with a shake
[Samsung Galaxy Nexus] Dr Byte:
This is designed behaviour, controlled by the "Advanced" area of Wifi Settings.

Settings -> Wifi -> "..." ((menu button)) -> Advanced.

Then "Keep Wifi on during Sleep" - "Always/Only when plugged in/Never."

"Never" will time out and disconnect.

No, that's completely different. It controls which "low power" power-management mode Wifi goes into when the screen is off. PM_FAST gives near-normal speed and packet response, but PM_MAX sacrifices latency for the (empty) promise of more battery life in most cases. I've measured no improvement with PM_MAX but if you are streaming or downloading with the screen off (I don't) you will probably notice a distinct change (stuttering, slow throughput.)

This is Kernel-specific, but the "Wifi Sleep mode" above is a ROM feature, present on all that I know of back to Gingerbread and probably Froyo and beyond. The behaviour should also be similar if not identical in each ROM apart from the fact that in GB, it was "Wifi Policy: Sleep Never" whereas now it's "Keep Wifi Alive: Always" (which is the same thing, expressed differently.)

Put your Wifi Policy on ALWAYS AWAKE and your Wifi power management mode as "FAST" and leave it that way.

tl;dr: It's a ROM thing, not kernel. It's designed that way, but you can control it. PM_FAST is something else, and IS in the kernel.
[Samsung Galaxy Nexus] navodwickra:
+1

I had the same experience (regardless of advance wifi settings) at home it used to cut off wifi when screen off but at office had no problem at all. So I set a static IP at home and it never happened again :D
[Samsung Galaxy Nexus] Treatcon:
Phone has been running great and had my first signal and data drop this morning on 175. Had it on the wall charger and when I unlocked the phone I lost all signal. I noticed something today that was different from any and every other day... my GPS was on. I normally don't have it turned on since I don't use GPS hardly at all, but I left it on from using Google Maps yesterday.

To those that don't have have problems with signal and data drops... is your GPS on?
[Samsung Galaxy Nexus] rogersnm:
I just thought I'd throw in my two cents: I haven't used GPS for over 2 weeks and I haven't had any signal or data drops.
[Samsung Galaxy Nexus] ssglackey:
Sure, but it was helpful only during downloads. Without continuous data stream wifi was disconnecting while screen was off. Now I have a new router (old one was over 6y old) and issue is gone.
[Samsung Galaxy Nexus] joeyfong:
try update the su library
[Samsung Galaxy Nexus] SubyWill:
175 has been great so far! Thanks for the amazing work Franco!
[Samsung Galaxy Nexus] Moz007:
Now waiting for ~1.5Ghz step and will be perfect ! :)
[Samsung Galaxy Nexus] kompressorgpl:
1.5Ghz dont be a little to much?
[Samsung Galaxy Nexus] A2Eric:
I'm new to flashing kernels...does it affect the color of the screen and you have to adjust after flashing a new kernel? Or can I just flash and it will still look like stock. I'm lazy and don't want to have to adjust the color to have it look like it does now.
[Samsung Galaxy Nexus] sing1gnis:
I've been having this issue since r16X. I have tried a few other kernels (Trinity, Glados) the past few days and didn't have any issues. So, yesterday afternoon I did a clean rom install and r175 and it's been fine since.

Let's hope it sticks this time.
[Samsung Galaxy Nexus] rogersnm:
Flashing the kernel doesn't effect the colour of the screen but it gives you the option of tweaking it if you so desire. If you like how it looks now then you can just flash the new kernel and not touch the colour settings.
[Samsung Galaxy Nexus] sing1gnis:
Depends. Some kernels apply color settings, some don't. I believe franco left everything stock though.
[Samsung Galaxy Nexus] franciscofranco:
Nice to see r175 being awesomely received. I would still like to deploy a last r176 with wheatley governor from Ezekeel since many users requested it and a routine change on screen on/off functions (make then cleaner). But I would like to see users reaction on this. Do you want me to declare r175 Milestone 4 and release a separate nightly r176 or release r176 now and Milestone later?
[Samsung Galaxy Nexus] a5pe4:
R176 with this wheatley gov everyone has been talking about
[Samsung Galaxy Nexus] rogersnm:
176 first would be good - it would be nice to see wheatley included in M4 :D
[Samsung Galaxy Nexus] blackdub370:
Milestone4: r175 + 1.5Ghz step = the best kernel

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Cutting-TM:
Since we know that 175 is stable with great performance and great battery life I would declare it to milestone 4. We dont know which error comes with the new govenor...
[Samsung Galaxy Nexus] spaceman860:
M4 then nightly so you don't get people asking for 512 gpu m4

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] grognaz:
+1
[Samsung Galaxy Nexus] xorob0:
175--->M4

New 176 with weather governor Will be perfect for me. Add à 1.5ghz slot Will be cool.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] ZiCoN:
I also have to agree with this....

There shouldn't actually be any errors implementing the governor, but if there are some people might start whining.....
[Samsung Galaxy Nexus] tcchuin:
R176 then milestone 4:-D
[Samsung Galaxy Nexus] bat0nas:
Whats so special about that Weather governor?

What governor is most popular currently in r175? Somehow I dont see any difference. Or the difference is minor.
[Samsung Galaxy Nexus] audibalso:
I love how u didn't include call time when talking about battery life for a phone. :) I think there once was a time when the 2 benchmarks were call and standby time.
[Samsung Galaxy Nexus] spaceman860:
That was before smart phones LOL

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] marshy73:
+1 for me! :p
[Samsung Galaxy Nexus] ramm8313:
This work on Cyanogenmod 9???
[Samsung Galaxy Nexus] nikulogical:
Well I'll say this. My settings are and have always been on always on but the wifi pm fast fixed my problem for me.
[Samsung Galaxy Nexus] Theshawty:
Works beautifully, but any problems that arise won't be helped.
[Samsung Galaxy Nexus] franciscofranco:
M4 then r176 it is.
[Samsung Galaxy Nexus] randommmm:
Franco, would you please explain what is the different between flash your kernel in Recover to flash it by your Updater.

I notice a situation: flash your kernel in Recovery make something irreversible changes to the system.

A simple test is Fifa 2012 by EA sports. Every other kernel of gnex available can play it, and flash your kernel by your updater won't break it too.

But those roms initial with you kernel, as well as after flashing your kernel in Recovery, the game will hang at the EA sports copyright showing screen. That is not the end, the strange part is you will never play Fifa 2012 in this system even flash back to other kernels and wipe everything ( cache, factory reset ), not until a fully reflash the rom.
[Samsung Galaxy Nexus] bigeyes0x0:
Flashing from recovery also flashes the sdcard mod in CWM zip, which I find causing more troubles than benefits so I always delete "the ****" when I install franco's kernel.
[Samsung Galaxy Nexus] Flukester69:
I still have a problem of gray bars and a few instances of data drop. When I turn off wifi when they are both gray the data goes blue, when I re-enable the wifi they both flicker and go blue. I have logcat for this if you care to look at it however from what I researched it appears the error I am seeing is logged with Google. Some multi cast error unsupported. I might try another kernel for the time being because for whatever reason I won't have this problem.
[Samsung Galaxy Nexus] randommmm:
Can't agree more.. I did a simple on screen test through a few kernels, showing that there are not so much different between each kernel at screen-on battery consumption.

It's quite simple: full charge, then do literally SAME things:

1. 20 mins Fifa 2012 (same team same setting every time)

2. 25 mins video playback (same one every time)

3. 60 mins ebook reading (not same book, but just TXT, won't make any differece )

and here is the statistic data:

Faux123 | Glados | Imosenyo | Franco

Start: 100% | 100% | 100% | 100%

Fifa: 93% | 93% | 92% | 92%

Video: 83% | 84% | 83% | 83%

Ebook: 71% | 70% | 71% | 72%

Almost the same in 3 different situation, since the battery figure is not very accurate anyway, I would rather say they are the same.
[Samsung Galaxy Nexus] Flukester69:
I don't even bother with battery stats they are all the same for me. I know just by regular use of my phone day in and day out. Changing voltages up or down also does not make any significant difference.
[Samsung Galaxy Nexus] hki_peter:
it should work on all 4.0.3 / 4.0.4 rom
[Samsung Galaxy Nexus] niallmcg:
It doesn't make a huge difference to battery life but it definitely does something.... I mainly do it to stop my phone overheating
[Samsung Galaxy Nexus] jcmm11:
I'll add a +1 to this. 175 is definitely milestone quality. Go with it then start to tinker again
[Samsung Galaxy Nexus] randommmm:
do you mean delete the /system/bin/sdcard ?

How do you know that flash by Updater won't flash sdcard mod?
[Samsung Galaxy Nexus] nikulogical:
175 should def be the next milestone. I'd love to see what Franco can do though in terms on implementing and tweaking wheatley.
[Samsung Galaxy Nexus] Antob125:
So can someone explain Wheatley gov? Can't find any info on it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bigeyes0x0:
I wonder what's this directory is for http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/appfiles/

I bet my money on that app Updater only flash the boot.img and does not include sdcard binary.

BTW I didn't mean to delete the sdcard binary on your ROM I meant delete it in CWM franco's kernel zip. For your ROM sdcard, you should restore it instead, read my PM.
[Samsung Galaxy Nexus] randommmm:
wheatley is an original gov by ezekeel, which raised an interesting thing named "C4 state", in CPU Spy, yon will see with Wheatley, most of the time, CPU run at the maxium speed slot when screen on. ( a lot like Performance gov )

unlike other gov around, try to run lower speed as possible, wheatly try to finish the job ASAP, then the CPU can rest, even when the screen is on! ( awesome, at least that is how it sound like :) )

the detail cover from here...

http://rootzwiki.com/topic/14685-28-may-glados-v134/page__st__30

then Ezkeel make a table about how Wheatly does in some representative situations (mp3, games, 3g/wifi web browsing etc.)

http://rootzwiki.com/topic/14685-28-may-glados-v134/page__st__50#entry394599

thanks, that explains, I'll test later to confirm it
[Samsung Galaxy Nexus] rogersnm:
I can confirm this, I just did an MD5 hash comparison of the sdcard file on my phone, the sdcard file in the franco kernel zip and the sdcard file in the aokp m5 zip.

I've only ever installed/updated the kernel via the franco kernel updater app as I got boot loops when I tried to flash it via CWM and ended up formatting & reflashing the ROM.

The sdcard file in /system/bin on my phone matches the sdcard file in the original aokp zip and not the sdcard file in the franco zip, indicating the sdcard file present in the franco kernel CWM zip is not installed by the updater app.

For reference; AOKP sdcard MD5: 2a2c0819bd90fe41f02b205812382bd7

Franco Kernel sdcard MD5: b237a8238683539391a32591197cc4ef

(Generated with FCIV in Windows and "MD5 Checker" from the play store)
[Samsung Galaxy Nexus] randommmm:
so one of the long-term Franco compatible issue reason is clear, since the difference between Updater and flash with CWM, no wonder why some people encounter it, some not.

Whether Franco will stick with his own sdcard or not, I think users should got a warning since it's irreversible unless ones backup its original sdscard before flash
[Samsung Galaxy Nexus] franciscofranco:
Interesting idea.
[Samsung Galaxy Nexus] Flukester69:
I don't, there is still data drop issue its better than it was but its not resolved in my eyes so on milestone release for some I guess they will have to live with the data drop. I love franco kernel but I am tired of data drops and I don't feel like going back 20 builds for resolution. Went to Walmart today and from time I left home to time I came back I had no data on 175. No voltage tweaking nothing. Stock 384 with 384MHz min and 1445MHz max interactive. Rebooted phone and instantly came back.
[Samsung Galaxy Nexus] maddie:
Having the same issue here, data loss is still a problem for me on 175, and have to either toggle airplane mode on and off or a reboot to get data back. Really annoying.. so I am falling back to Milestone 3 for now.
[Samsung Galaxy Nexus] rogersnm:
Well it does seem to do what it says on the tin, I pushed the sdcard file via adb and updated the permissions and here is a before and after:

Might be worth adding it to the updater app
[Samsung Galaxy Nexus] cchhat01:
Franco,

Does this mean that you will release an M4 (which will be the equivalent of r175 with the stock gpu speed)

OR

is r175 = M4 and that there will be NO separate M4 release?

Thanks.
[Samsung Galaxy Nexus] sotoskawasaki:
Guys, please excuse my ignorance but what is that sdcard binary and what does it do?
[Samsung Galaxy Nexus] rogersnm:
Here's some quotes :)
[Samsung Galaxy Nexus] sotoskawasaki:
Thank you very much for your reply. It was very informative. One last question. Is that binary included with kernels or custom roms?
[Samsung Galaxy Nexus] rogersnm:
It's included with some kernels - it is included in the franco kernel zips however it isn't applied if you install the kernel via Franco's Kernel Updater app.

That said, if your first install was via CWM recovery, you should now be using the modified sdcard binary regardless of whether you now update via the app. If you want to check download "MD5 Checker" from the market, select the file "/system/bin/sdcard" in the app and then post the MD5 hash generated by the app here.
[Samsung Galaxy Nexus] franciscofranco:
Faux quote is wrong. My kernel has high IO performance because of fsync() calls disabled and proper mounted partitions. Greg's hacked sdcard binary only decreases the overhead caused by Google's strange implementation.
[Samsung Galaxy Nexus] rogersnm:
Ok sorry for quoting an incorrect statement, I modified my post appropriately.
[Samsung Galaxy Nexus] MultiCulti:
best since i got my GN :thumbup:

about 20 minutes screen on ...

beamed in through my brain ...
[Samsung Galaxy Nexus] marc.tulley:
Cracked it Franco , well done. Screen-off efficiency it better than stock for me! Went to bed at 65% woke up over 10 hours later and it was 64%!

Note this graph starts at 78% because I flashed AOKP (Bigxie was using about 1% per hour so I gave AOKP a go).

Uploaded with ImageShack.us[/IMG]

Its good to know I can sleep over somewhere, forget my charger and still have an alarm wake me up instead of waking up late to a black brick!

Still awaiting a 1.35 OC ; ) (Sounding like a broken record sorry lol)

Have a good new year
[Samsung Galaxy Nexus] JcMalta:
1.71 is the best!

Franco

MANY thanks for all the work you have done on this kernel... 1.71 seems like a real winner - 28 hours since last charge with "normal usage", WiFi and 2 Google syncs always active and STILL 57% left.

I donated a couple of weeks ago, but promise I will again when you feel you are "finished" with development....

All the best, Happy New Year!

----------------

Samsung Galaxy Nexus GSM, Kernel: Franco V7.1, ROM: bigxie #5, Radio: XXKK6
[Samsung Galaxy Nexus] luffyp:
Can I ask anyone who has good battery life, do you still have high cpu usage/wake time from Android OS?
[Samsung Galaxy Nexus] JcMalta:
How did you establish Bigxie was consuming 1% per hour?

Would you recommend moving over to AOKP after your experience with it?

I will probably give Paul's ROM a try again when he goes full 4.0.3 ( I have Kitchen access) ... but in the meantime, the simplest, fastest/most efficient ROM is what I am looking for.

I have been very happy with Bigxie so far but better alternatives are always good!
[Samsung Galaxy Nexus] scomodo:
Is there a way to flash only the stock kernel? (To avoid a full backup)
[Samsung Galaxy Nexus] nicandris:
After flashing 7.1 i get this error. i noticed franco saying that usb was fixed, but i never had problems, now i do!
[Samsung Galaxy Nexus] marc.tulley:
Firstly don't get me wrong, Bigxie has done a great job but with my curiosity, no changes to his ROM in about a week and repeated mentions of AOKP I thought I would give it a go. (I did also like the extra settings AOKP offered).

I established the 1%/h based on the time I had franco 7.1 running (most of yesterday daytime)

It wouldn't be responsible of me to suggest a ROM that I have only used for about 4 waking hours but definitely so far so good :) With flashing so easy in CWM why not give it a go :) I think NFC isn't working properly on it yet but that doesn't make a difference to me.
[Samsung Galaxy Nexus] JcMalta:
@marc.tulley

I'm doing a full backup now ..... going to give it a try .......

Many thanks for your prompt reply!
[Samsung Galaxy Nexus] nmesisca:
nfc

hello franco,

just wanted to report that with #7.1 its not possible to turn on NFC anymore.

it was working fine with #6..

thanks again none the less,

N
[Samsung Galaxy Nexus] robto:
Working fine for me : ?
[Samsung Galaxy Nexus] Luckyman79uk:
My NFC works fine with 7.1
[Samsung Galaxy Nexus] robto:
Start thinking I did somwthing wrong.... NFC is working fine for me too with nightly 7.1.

I am using AOKP rom. Previous kernel was the one included in AOKP.

Guys, sorry for this silly question: did you wipe dalvick cache?
[Samsung Galaxy Nexus] nmesisca:
thats really strange.

I am using Modacos Ir8, and have been using it with #6 and #7.1 .. NFC was working fine with #6, but now I cant enable it.. and yes, wiped cache and dalvik cache when i flashed the new kernel..

:confused:

N
[Samsung Galaxy Nexus] Mnemoch:
NFC and MTP to my Win7 PC both work fine...
[Samsung Galaxy Nexus] RonnieRuff:
Secure Element issue?

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] nmesisca:
nfc logcat

this is what I get in logcat when I try to enable NFC..

D/NFC JNI ( 491): Start Initialization

E/NFC JNI ( 491): phLibNfc_Mgt_ConfigureDriver() returned 0x0106[NFCSTATUS_INVALID_DEVICE]

E/NFC JNI ( 491): phLibNfc_Mgt_Initialize() returned 0x0001[NFCSTATUS_INVALID_PARAMETER]

E/NFC_uart( 491): open(/sys/devices/platform/nfc-power/nfc_power) for write failed: Permission denied (13)

D/NFC JNI ( 491): Download new Firmware

E/NFC JNI ( 491): phLibNfc_Mgt_IoCtl() (download) returned 0x0001[NFCSTATUS_INVALID_PARAMETER]

W/NFC JNI ( 491): Firmware update FAILED

:confused:
[Samsung Galaxy Nexus] robto:
Not sure if it is a good idea but I would try to compare #6 vs #7.1 zip files: if there is any addicional file in #6 not included in #7.1, delete that file with root explorer. Just a quick test.
[Samsung Galaxy Nexus] nmesisca:
they are way too different to do that I m afraid..
[Samsung Galaxy Nexus] StuMcBill:
Yep, another can't turn NFC on.

Running modaco pre ir8 and nightly 7.1. The tick appears in the box and dissappears straight away .

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] jnr21:
So i need to flash franco kernel via cwm first and later updates can be auto-flashed?
[Samsung Galaxy Nexus] rogersnm:
Yes if you want the modified sdcard binary - alternatively you can push the file via adb.
[Samsung Galaxy Nexus] sotoskawasaki:
You have been very helpful tonight. Thanks. I always flash the kernel with cwm (do not own the app) so I do have the modified version of the binary. I will check the md5sum tho...
[Samsung Galaxy Nexus] Luuthian:
So, going by all I've read in the last few weeks here, we're not going to see any many more improvements for battery life in terms of screen time, are we? And by that I mean, say, playing a game for four hours or watching a movie. It seems as if the only performance improvements available now are for idling and light users who just want to text or use the internet briefly.
[Samsung Galaxy Nexus] deepayanneogi:
What if I flash another kernel on top of Franco's ? Like I have his kernel app installed and decided to install Lean . so will it anyway affect my /sdcard contents ?
[Samsung Galaxy Nexus] SubyWill:
Loving 175! So smooth and good battery life!
[Samsung Galaxy Nexus] rogersnm:
Once you flash franco's kernel via CWM it will overwrite the sdcard binary and, unless any future kernels kernel you install contain another sdcard (either further modified or [i can't see why] stock) binary, franco's binary will persist across different kernels. If you flash a different rom then it will overwrite the sdcard binary on your phone with the sdcard binary that comes with that rom.

It's important to note that we're talking about the sdcard binary, not the contents of /sdcard.
[Samsung Galaxy Nexus] franciscofranco:
You know the answer for that question.
[Samsung Galaxy Nexus] krex:
Maybe it would be worth to test and revise this modified sdcard bin again.... I did some test 3-4 weeks ago and I didn't get any big difference in benchmarks, but instead much more annoying error messages in logcat. From that time I always download manually the nightly and flash with cwm after deleting binary.
[Samsung Galaxy Nexus] franciscofranco:
But the sdcard binary is not there to improve benchmarks... the logcat error messages are not a problem as well. But I'll ask Greg to comment, give me a sec.
[Samsung Galaxy Nexus] rogersnm:
It doesn't yield a noticeable performance increase when just using the sd card or just using the cpu, as in most benchmark programs. However if a program has high CPU usage and then wants to interact with the sdcard, it does increase performance. It should also increase battery life due to less power draw whilst reading from/writing to the sdcard partition.
[Samsung Galaxy Nexus] franciscofranco:
Thank you, that should cover it.