yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Controvrsy046:
It says that the latest CM10 Nightly's have SQLite: Enable fdatasync for SQLite. Franco's kernel's have Fsync enabled. Can I turn off Fsync in Franco's app now that CM10 has fdatasync enabled for SQLite?

Any help would be much appreciated as it says fdatasync is better for performance than Fsync in Franco's Kernel App.
[Samsung Galaxy Nexus] franciscofranco:
fsync() system call is a function that is called everytime there is a file access (read or write) and flushes the changes to prevent data loss on power outage or random crash. Its a low level operation. Sqlite is a relational and small database (similar to MySQL) and works in a higher layer than the kernel so in the end if you disable fdatasync you only disable fsync for SQlite operations. If you disable fsync() in the kernel you'll ultimately disable any type of sync (even i you leave fdatasync enabled). Sorry for the big and fancy wording here, but its how I know how to explain.
[Samsung Galaxy Nexus] Controvrsy046:
fsync() system call is a function that is called everytime there is a file access (read or write) and flushes the changes to prevent data loss on power outage or random crash. Its a low level operation. Sqlite is a relational and small database (similar to MySQL) and works in a higher layer than the kernel so in the end if you disable fdatasync you only disable fsync for SQlite operations. If you disable fsync() in the kernel you'll ultimately disable any type of sync (even i you leave fdatasync enabled). Sorry for the big and fancy wording here, but its how I know how to explain.

So basically leave fsync in your kernel enabled and those two sync features will work side by side?
[Samsung Galaxy Nexus] nikulogical:
Latest nightly has given me better wifi signal. In my home network at least.
[Samsung Galaxy Nexus] franciscofranco:
Yes. Disable fsync -> you will lose any file syncs. Disable fdatasync -> you will only lose database file sync but keep the file systems sync.
[Samsung Galaxy Nexus] franciscofranco:
My 3G data reliabilty is much better in this r246, its perfect for me, 0 drops or hangs.
[Samsung Galaxy Nexus] nnnnr14:
What about 4g?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] nikulogical:
The real Nexus doesn't have 4G ;)
[Samsung Galaxy Nexus] franciscofranco:
I dont have 4G on my GSM Nexus... who needs that anyway.
[Samsung Galaxy Nexus] RevengeFNF:
I wasn't able to flash r246 with franco kernel updater. It was alwasy at 0.

I flashed it manualy.
[Samsung Galaxy Nexus] Flukester69:
I wasn't able to the first time. It was 0 for a bit then I think my thumb hit screen and soon after it FC'd. Tried again and it flashed right away. Maybe server was being hammered or something.

Brought to you from my Galaxy Nexus using Tapatalk.
[Samsung Galaxy Nexus] hasnol143:
Hey can you tell me where i can find the file to do this?
[Samsung Galaxy Nexus] franciscofranco:
/system/build.prop ...
[Samsung Galaxy Nexus] Flukester69:
I hope you are not being serious. LOL!
[Samsung Galaxy Nexus] nnnnr14:
Well... mine says nexus and it has 4g lte connection so I'm good.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] hasnol143:
Is this the part i have to change, it was the only thing about calls mentioned: " # Ril sends only one RIL_UNSOL_CALL_RING, so set call_ring.multiple to false

ro.telephony.call_ring.multiple=0"

It took me a while to find because i had to mount the root files
[Samsung Galaxy Nexus] Mircoron:
Sorry but in build.prop i did not find call steps,

what can i do?
[Samsung Galaxy Nexus] superbobup:
Edit: too slow...
[Samsung Galaxy Nexus] franciscofranco:
Im being serious. Having 4G means your device will have two radios, which equals much less battery life and more warmer device. 3G with 21 Mb/s is just enough.
[Samsung Galaxy Nexus] bruciato:
After flashing r246 in minco v4 camera stopped working....There s a FIX for this?
[Samsung Galaxy Nexus] Langduscher:
Works fine here? (Bamf & MiNCO)
[Samsung Galaxy Nexus] Flukester69:
My battery lasts the day :)

Brought to you from my Galaxy Nexus using Tapatalk.
[Samsung Galaxy Nexus] slvrarrow:
Signal on radio seems much more stable for me too Francisco. What changes have achieved this? Great stuff
[Samsung Galaxy Nexus] nnnnr14:
I can confirm this as well. It acts like the radio in my old droid razr :p

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] franciscofranco:
I merely merged patches from android-omap-3.0 branch and did some reverts. Works awesomely good, best signal I have had with this device.
[Samsung Galaxy Nexus] nikulogical:
Are we supposed to reboot our devices everyday or something? I feel like it slows down if I don't reboot for 3-4 days, this happens with all custom kernels.
[Samsung Galaxy Nexus] M3drvr:
And mine lasts 2 days. Although I do use my phone a lot less since I got the Nexus 7. Nevertheless I get 2 days with around 2 hours screen time.
[Samsung Galaxy Nexus] billykxda:
Are we talking wifi reception or 3G/4G reception?
[Samsung Galaxy Nexus] nnnnr14:
4g

I got 99 problems but bamf ROMs ain't one! -nnnnr12

---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------

Some how the Franco app reverted me back to #241 or the system info didn't update.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] kashix:
Life is good on m5, trinity color, contrast. Best of both worlds. Your work is unprecedented!
[Samsung Galaxy Nexus] LibertyMonger:
Agreed! I have had absolutely no issues since M5, great work Bud! I have noticed since the first nightly after AOKP build 1 my battery seems to be draining more quickly but that is from the ROM I am sure. Thanks for your work buddy!
[Samsung Galaxy Nexus] fredryk:
No problems with n246 that I can detect so far. I could be imagining it, but I think I'm getting a slightly better wifi signal in a few places.
[Samsung Galaxy Nexus] prembox:
Yes, GNex is crappy at WiFi reception and all.......typically I found Android devices don't match up other platforms...at least I can say for a WP7 phone (Omnia W) I used to test at home and compared it with the WiFi reception of 4...yeah 4(2 highend and 2 midrange) different Android devices!!! at about 15 feet from my router...the Omnia scored all bars and the 4 droids had 2 and below...with GNex getting just one bar but after 246 I'm getting 2 bars...that's some improvement there...isn't it?

---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------

As a practice since my i9000 days....everytime I charge my device full....I just wipe Dalvik, Cache Partition n Battery Stats....like a ritual to keep the device from getting stressed... :cyclops:
[Samsung Galaxy Nexus] Exostenza:
FYI

Several developers working on the AOSP said specifically to never delete your battery stats as the more information you have about your device the better reporting you are going to have. They said that if anything deleting the stats could be a detriment to your battery life and most definitely will never help. I used to delete my battery stats all the time until I read the article containing this information.

Now I never delete my battery stats and my battery has been superb on my gnex.
[Samsung Galaxy Nexus] cornbread0715:
Wifi

My God I also dont know what he did but the WiFi is much much better. I am getting 1 more bar than I used to and its more stable. So I agree with you on this one.
[Samsung Galaxy Nexus] Exostenza:
Just wondering why the battery life extender defaults to 100 instead of 96 like it used to.
[Samsung Galaxy Nexus] prembox:
You mean it comes to 100 by default after a reboot even after you manually set to 96 before reboot???
[Samsung Galaxy Nexus] The Gingerbread Man:
Its hard for me to judge gsm signal as I have had full bars since I updated to jellybean. My WiFi signal at home seems to be 1 bar less than previous builds (now showing 4/5 instead of 5/5) but perhaps its a truer reading, the speed might be slightly increased even. I shall have to test with an app some point and share.

Great work though and lovely to have the 512 gpu back :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] superbobup:
You can get a good measure of your signal strength by going to settings-> about phone and looking at the dBm. The higher value the better. As for speed...that's hard to tell but a rough estimate can be gathered from the speedtest app

BTW, I feel like I've been responsive to your most recent posts GBMan. Hope it's not weird o.o I've just had downtime lately and you've been posting in my subscribed threads :D
[Samsung Galaxy Nexus] Exostenza:
I mean the setting the program starts us out with used to be 96 and now it is 100. I am wondering why Franco changed that as I want to know if I should change it to 96 like it was before or leave it be.
[Samsung Galaxy Nexus] CADude:
I noticed that too. Might wanna put it back to 96 by default to keep those batteries healthy.
[Samsung Galaxy Nexus] superbobup:
The amount of time you keep your phone will probably be much shorter than the time it takes for your battery to die out :p
[Samsung Galaxy Nexus] The Gingerbread Man:
Okey dokie, I always thought lower numbers were best with dBm but I actually dont know anything regarding the readings haha I appreciate your help and its not weird, there's times when I post loads, other times not so much. Its nice to have someone giving me advice for a change :D;)

Sent from my Galaxy Nexus

---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------

Replacement are cheap enough online too :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kurre:
Well those dBm values are negative ones..like from -55...-115. So better signal has higher value (-55 vs. -115) and lower (bigger negative value) is the worse one :)
[Samsung Galaxy Nexus] CADude:
Doesn't mean that a feature that should be at default should just be ignored.
[Samsung Galaxy Nexus] Kappa Lamda:
Several hot reboots(jumps to bootanimation and after boot asks for SIM pin) for me with 246. Went back to 241 which is stable for the same settings. I have undervolted CPU freq on both version if this is useful!
[Samsung Galaxy Nexus] Hungry Man:
Can someone explain what each setting does for interactive gov't control?

I've searched online and can only find small amounts of information on only a few of the settings, definitely not all of them.
[Samsung Galaxy Nexus] arhung:
+1
[Samsung Galaxy Nexus] gm007:
I don't know if this can help you

https://github.com/android/kernel_common/blob/android-2.6.39/Documentation/cpu-freq/governors.txt
[Samsung Galaxy Nexus] RevengeFNF:
You are saying that Stock Kernel only charges till 96%?

When i used the Stock JB with Stock Kernel, the phone alwasy charged till 100%. At least for me.
[Samsung Galaxy Nexus] Hungry Man:
Missing some info still.
[Samsung Galaxy Nexus] franciscofranco:
Stock kernel charges to 100%.
[Samsung Galaxy Nexus] Hungry Man:
ex: above_hispeed_delay. No information ont hat that I've found.

boost also doesn't seem to have info.
[Samsung Galaxy Nexus] franciscofranco:
above_hispeed_delay I dont know, but that boost option when enabled I think it makes interactive a bit more aggressive.
[Samsung Galaxy Nexus] LibertyMonger:
I just had an instance where my text messages wouldn't send until I rebooted. Running AOKP
[Samsung Galaxy Nexus] franciscofranco:
Thats not kernel related at all. Check your area service and your rom, radio etc.
[Samsung Galaxy Nexus] chugger93:
Input boost will automatically jump the phone to the hispeed_freq when you touch the screen to help prevent lag.

This means it jumps to 700 or whatever you set it to when you touch the screen and then goes up or down from there. This helps balance battery with performance.

I personally keep my hispeed freq at 729 default, but set my input_boost to 1.
[Samsung Galaxy Nexus] djjonastybe:
I compared hotplug and interactive governor with eachother. It looks like interactive is still the best governor we have for power savings. hotplug gives me one day of battery life while interactive may give me 2
[Samsung Galaxy Nexus] chugger93:
i agree
[Samsung Galaxy Nexus] djjonastybe:
Post a bug report in AOKP forums.

Install aLogcat on your Nexus. Send a text message and send the log after the message has been sent. This way they MAY fix it faster for you.
[Samsung Galaxy Nexus] bunnycool:
Hi..i switched to 1804 .. tried to benchmark in antutu .. during the test phone crashed..and was realli hot..really scared..what to do :( just bought the gnex
[Samsung Galaxy Nexus] ih8sense:
Couple really quick questions:

1. This is compatible with CDMA phones? (ie, Sprint)

2. Can I simply flash the .zip for milestone 5 via CWM, or must this be baked into a rom?

Thanks so much! :)
[Samsung Galaxy Nexus] franciscofranco:
Its really hard to understand what happened there really... overclocking much above stock speed what were you expecting?
[Samsung Galaxy Nexus] benkxda:
Yes, of course it's getting hot. For benchmarking you should set the governor to performance and try to cool the Galaxy Nexus at the back, especially near to the cam/LED.

But you have to set the correct governor and speed for normal usage. Use the "battery hot" trigger to set a slower profile/governor/cpu clock to avoid temperature probs. My settings: 40°C -> Powersave @230 MHz - cools down the device fast enough.

---------- Post added at 06:34 PM ---------- Previous post was at 06:30 PM ----------

1. I am not sure, but I guess it works even wirh CDMA - best Kernel should work for this as well :)

2. Yes, just flash it in CWM, I never had a problem doing this.

And I wanna thank Francisco Franco for that kernel. Soon, the Nexus 7 will be mine and I am very delighted, that there is a kernel from you available. So this one will also get your kernel. :)
[Samsung Galaxy Nexus] haxor:
Whenever Nexus getting hot then why it more hot at near cam/led ?
[Samsung Galaxy Nexus] TEK112:
That is where the multi-processor chip is located. Look at ifixit and you will see the processor/gpu located there.
[Samsung Galaxy Nexus] J-Hop2o6:
Stick with 1.5GHz for max OC.

---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------

/s? I hope you're not serious.
[Samsung Galaxy Nexus] bunnycool:
Thanx man..to scared to anything else nw
[Samsung Galaxy Nexus] J-Hop2o6:
Don't be scared, just READ READ READ (research) and experiment. It makes more sense with time and research.
[Samsung Galaxy Nexus] Marreboy:
First of all thanks again to Franco for this great kernel.

Some feedback from me on 246 which I have been running today. Seems to be very battery efficient on 3g. Noticeable difference compared to milestone 5. 3g speed also seems very good. But I also noticed that it from time to time takes very long to engage data transfer, which gives some apps issues and I get errors about no data connection available. Also tested with speed test app and pretty consistently see it having issues engaging the data upload test.

Did not experience these issues with any of the previous nightlies or milestone 5.

Saying that I still think I will keep 246 until 247 or higher becomes available. This is because of the excellent battery efficiency with 3g.

Tapatalked from my Nexus 7
[Samsung Galaxy Nexus] Exostenza:
Since you guys are talking about OCing I was wondering that considering my experience is buttery smooth @ 1.3ghz what incentive would I have to OC any higher? Are you guys doing it for show or is there some practical purpose that you use it for?

Seems to me like it's just wasted battery life for the most part...
[Samsung Galaxy Nexus] benkxda:
Honestly, yes, 1,8 GHz is just for beating SGS3 @Sunspider ;)

Mine Gnex is running atm with max. 1,3 GHz, which is smooth enough for my every day usage.
[Samsung Galaxy Nexus] chugger93:
Oc'ing is useless from what I've tested. Not that I've tested much, but my nexus clearly hangs out around the 384 and 729 frequency even though she has 1036 to work with. Going much higher, and you won't see many hours put into that frequency. Test it out yourself with cpuspy.

Minus well conserve that battery. My phone is still snappy with 729/1036. Although previously I was running 384/1036, but I'm trying the 729 route to further test battery results
[Samsung Galaxy Nexus] superbobup:
Some people OC because they notice it is smoother. Some do it for higher benchmarks. Some people UC for better battery or because they don't notice the smoothness. The only "right" clock speed is the clock speed that is right for you :p:eek:
[Samsung Galaxy Nexus] Felixpau86:
Just a quick review. For me 246 has been running fantastic. Wifi improved. Battery improved by at least 10-20%. Great work. Thanks Francisco.
[Samsung Galaxy Nexus] chugger93:
so just to pick everyone's brain who's undervolting here: What are some of your lowest values you've gotten by with (without random boots)?

My 1036 freq is 940, 729 is 925, 384 is 820

I havnt tested going any lower than those yet.
[Samsung Galaxy Nexus] J-Hop2o6:
I'm running OnDemand @ 1.5 to prevent any slowdowns, stutters. And to fly thru most tasks like multitasking and installations/updates. The biggest battery drainer is the screen. The SoC hit the battery pretty small compared to the screen. So even if I downclocked, it wont make a noticeable difference in battery life. Try 1.5 max for a day, then try 1.0 for a day then post the "difference".

---------- Post added at 11:40 AM ---------- Previous post was at 11:36 AM ----------

I don't UV often, but here's mines:

1.5GHz = 1300mV

1.4 = 1250

1.3 = 1225

1.2 = 1200

1.0 = 1150

729 = 1100

384MHz = 900mV

That's about the best I can do.

EDIT: Had to raise a few. Kept getting lock ups with use with the old values. EDIT2: Even with these new values I get lock ups. The best for me is to just use the default mV since I never have a problem with it.
[Samsung Galaxy Nexus] supernova_00:
MiNCO rom (Minooch and Franco's ROM) has a test build for TORO devices. Works perfect for me with no issues whatsoever and seems like great battery life compared to the Viscious ROM I was using. http://xdaforums.com/showthread.php?t=1855272

Didn't see this mentioned here so wanted to get the word out.
[Samsung Galaxy Nexus] franciscofranco:
Yeah just stick to smartreflex calibration, works wonders.
[Samsung Galaxy Nexus] Exostenza:
I've been off of Franco.Kernel since jb released to try trinity so I have been out of the loop for a little. I am wondering g what happened to the option in the application that enables single core mode when the screen is off?
[Samsung Galaxy Nexus] franciscofranco:
Removed it, I dont want to mess with the cores anymore.
[Samsung Galaxy Nexus] nuwan32:
It actually helps to oc a little higher. I dunno to me it feels snappier when loading games and such. The stock clock of this chip is 1.5GHz anyway so that's what I run it at and you should be fine with that. Doesn't get too hot either
[Samsung Galaxy Nexus] Hungry Man:
Had Wifi/data icons turn grey and cut out for a minute today. Came back after. This has happened consistently across ROMs. Not sure if it's a kernel thing.

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

I overclock to 1.7ghz with the 512mhz GPU. The phone only clocks up when it needs to anyways and it's load based so I'll only hit 1.7ghz when my phone would actually need to hit it. This only happens when playing games or browsing a heavy site, sometimes the phone will clock to 1.7ghz briefly and then clock back down sequentially until it's 720mhz again/ 384mhz. My battery life is great and my performance is great so it works for me.

Because of undervolting my 1.7ghz uses only 80mV more than the default Franco voltage of 1.2ghz, meaning I'm still saving battery even when overclocking.
[Samsung Galaxy Nexus] RayGarden:
Jr6 (JRO03D / 4.1.1) - MoDaCo

Jr6 (JRO03D / 4.1.1) - Paul o Brien's MoDaCo ROM

Available in Kitchen

Prebake 29th

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

For those who are interested.

Cheers
[Samsung Galaxy Nexus] arhung:
I really don't know how some people's phone battery life can stay for one day or even more:confused:
[Samsung Galaxy Nexus] josip-k:
Question,why dont you have an option to change GPU frequencies,like glaDOS?it could be cool,like if you want to play some game you can change the frequency right away and change it back imediately after finishing.?

Galaxy Nexus,CodeNameAndroid©
[Samsung Galaxy Nexus] benkxda:
Don't be always online and switch off Bluetooth and GPS sometimes. My device works about 2 days (1750 mAh "battery") without a power outlet :)
[Samsung Galaxy Nexus] franciscofranco:
Because it doesn't work as good as a pre-set GPU speed. I tried that road before and lots of people that ran 512GPU couldn't run it anymore using a toggle.
[Samsung Galaxy Nexus] josip-k:
Wow thanks for the quick answer :) so how does it work on glados but not on yours?

Google™

Galaxy Nexus,CodeNameAndroid©Franco.kernel®
[Samsung Galaxy Nexus] J-Hop2o6:
I always wondered this. But I guess its not possible to change it On-The-Fly like it with the CPU. That's why there's two files. But I would like to hear the technical part on my its not possible to change the GPU frequency On-The-Fly like you can with the CPU.

EDIT: I see Franco's simple explanation. But why does it have problems unlike the CPU?

Those ppl barely use their phone. But I think the max possible screen on time for our phone is 5 hrs.
[Samsung Galaxy Nexus] jcpq:
This kernel run fine in CM10?
[Samsung Galaxy Nexus] josip-k:
Yes

Google™

Galaxy Nexus,CodeNameAndroid©Franco.kernel®
[Samsung Galaxy Nexus] Hungry Man:
I use my phone quite often for browsing, IMing, texting, and watching Netflix. Battery life is fine. IDK why it seems to vary so much.
[Samsung Galaxy Nexus] yalouf:
Running Paranoid Android With Milestone 5@1.5ghz interactive ! Phone is smoother than 1.0ghz but CPU Spy tells me that 1.5ghz is reach only 1% of the time, mostly 384 and 729mhz. Mostly Wifi Surfing, 3g with good reception however ( that makes a huge difference)

And this is including 2 hours of listening podcasts...

This kernel is a blast !

I hope the same Franco kernel will come for Nexus 7 and CM10 because my tab stays mostly at 1.3 ghz with the same use...

Keep up the good Work :)
[Samsung Galaxy Nexus] aeroseek:
What would cause my battery to stop charging even though it was plugged in?

I was driving home using gps and had the GN plugged in (fast charge enabled, BLX=100, battery level 78%). Initially all was ok and it was charging but after maybe 2% increase, the battery status said "not charging".

True, it was pretty warm to the touch. Was it some kind of thermal protection kicking in?

I'm on minco v4 using #246. Also observed this behavior on m5.
[Samsung Galaxy Nexus] superbobup:
Maybe a bad connection? Does it work at home on a diff cable? Try checking your pins

Also it may be due to thermal protection...I think the S3 prevents charging if the temperature is too high
[Samsung Galaxy Nexus] J-Hop2o6:
Try without Fast Charge
[Samsung Galaxy Nexus] digver:
Arrg. I'm good at math and know that, but, every time I get tripped up by ignoring the negative sign! I've started looking more at the ASU number and don't have to think about it.
[Samsung Galaxy Nexus] aeroseek:
As i remember without fast charge the batt actually discharges

while using gps. Will give it another go.

I use same cable in car and at home. Home is fine, of course gps is off.
[Samsung Galaxy Nexus] timbck2:
Edit: nm, I don't know what I was thinking.
[Samsung Galaxy Nexus] superbobup:
It really sounds like a heat issue since it only happens with GPS and in some hot situations :D

Does it only happen with this kernel or others?