yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] lizaSB:
Sometimes, if heavily used routers are not configured properly, I think that the router can run out of IPs to give. In this situation, the easiest fix is to reboot the router so that each client is forced to renew its lease. I can't remember if someone else suggested, but have you tried asking someone to reset the router before you change things on your end? I think it is possible that if there was a problem with the router, you were not the only person to notice it, but you may have been too busy flashing and troubleshooting to notice :laugh: However, your pattern of working/not working seems slightly erratic.

The only thing I could think of besides router issues was that wifi drivers since M5 are derping the phone ability to be assigned DHCP info from the router. Perhaps the reason 277 works following M5 is that router has already created a lease for your devices mac id? This seems unlikely to me though.

It seems more likely to me that you've had just a bit of bad luck with busy routers. Someone usually asks us at least once a day to reboot our router and on a normal day it's hard to find a seat inside or out. Router bumps often fix most people's problems, especially when there seems to be no logical reason why the device won't connect. I wonder if your problem will persist on r277?
[Samsung Galaxy Nexus] jcmm11:
Just tried this and yes I also got a reboot. R277,512 started terminal emulator, su, lsmod caused instant reboot. Can create kmsg if another one is needed. (AffinitySeries Rom).
[Samsung Galaxy Nexus] vrehenriqu:
I'm using franco default settings and CNA 3.6.0 ROM.

No undervolting
[Samsung Galaxy Nexus] Mayday_XL:
The r277 runs very good with my settings. :good:

r277-512GPU

Interactive/ Deadline

729-1305 Mhz

hispeed_freq @ 1036800

729 Mhz Screen Off

SR on (no etxra UV)
[Samsung Galaxy Nexus] momomok:
I seems to be getting a memory leakage... is there any way to determine if it is ROM issue or kernel issue without flashing another ROM?
[Samsung Galaxy Nexus] kunalwanvari:
my 1st nexus kernel i flashed today .. i notice my battery charge stuck at 96% since along time .. any workaround ?

using milestone 5 with cna 3.5
[Samsung Galaxy Nexus] PotatoEngine4:
I'm having the same problem
[Samsung Galaxy Nexus] osm0sis:
Your batterystats sound broken. Wait it out and fully discharge (when it dies, wait 10 min and turn it back on, repeat until it won't turn on anymore), then charge it all the way. That should fix it. We need to do this maybe once a month to keep them properly calibrated.
[Samsung Galaxy Nexus] chrisgtl:
Finally got my colour profile to stick on reboot.

Seems franco app and better-battery-stats are conflicting with each other on reboot. I get about 5 messages saying each one is granted access on reboot. I disabled better-battery-stats in SuperSu and now only get the 1 message saying franco app has gained access and my colour profile is loaded.

Not sure if this is what was causing it as I didn't change anything else but rebooted a couple times and my colours are always correct now.

Cheers.
[Samsung Galaxy Nexus] vrehenriqu:
Found the issue:

CNA ROM 3.6.0

Settings - > developer settings - > PM sleep mode: it was set to 'power collapse (best)'

Disabling this setting, the phone won't reboot after a boot.
[Samsung Galaxy Nexus] Kurre:
No problems here :eek: and my color profile is always loaded after reboot. Using SuperSU 0.96.

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] QUEDRO:
Few things noticied too:

- Data disconnection on r277, have to reboot to restore

- If I setup "Min CPU" at 729Mhz I can't set "Maximum freq for screen off" at 384 Mhz, it won't change below 729Mhz.

- Seems that default CM10 kernel has a brighter screen. I reflashed a few nightlies and definitely brighter screen at maximum. (disabled adaptive screen - same thing)
[Samsung Galaxy Nexus] bradm23:
I can't seem to shake the modem_USB_gpio_wake kernel wake lock. I posted about it last week and Franco said it sounded normal. Battery drain down to 78% in 2 hours of being unplugged, that kernel wake lock is holding my phone awake for almost 6 minutes. Sometimes a reboot will work fixing it, however some times it takes multiple reboots to fix. Any suggestions are greatly appreciated.

When this wake lock isn't here, this kernel sips battery, however something triggers this wakes and makes my drain horrible
[Samsung Galaxy Nexus] misiu99:
Hi.

Sorry for my English.

I use Deodexed Stock Jelly Bean 4.1.1 with Milestone 5. My volume is pretty low. Just buy your App but Sound Boost don't take any change. Please help. With Cyanogen Mod 10 i have really great volume.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Flash this and be happy again.

http://xdaforums.com/showthread.php?t=1748803
[Samsung Galaxy Nexus] misiu99:
Yes, sure. But what with Kernel sound Boost? I pay 3 euros for that. Sure is not really much, this kernel ist Really great but this App not really work.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
The kernel sound hacks only affects the headphones.

For the ROM, you need to apply the fix I posted.
[Samsung Galaxy Nexus] IAmAN00bie:
CM has their default color multipliers at 400,400,400 if you want that back.
[Samsung Galaxy Nexus] misiu99:
Thank you.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] momomok:
CNA 3.6.5?
[Samsung Galaxy Nexus] osm0sis:
1) You probably only have to toggle Airplane mode at most. I'd suggest doing a full wipe and trying a different ROM.

2) That's by design, it's max for screen off. You shouldn't set it lower than 729MHz anyway as doing so interferes with the race-to-idle, keeping your phone awake longer.

3) CM jacks up the multipliers. 400s across the board, which is technically bad for screen burn-in.
[Samsung Galaxy Nexus] Crackking:
@Franco or someone else who can answer this question:

I'm missing the file adj in /sys/module/lowmemorykiller/parameters/...

Did Franco delete it or something else? I reflashed 277 and it's still missing, in milestone5 it's there...

Is there a reason for this mystery? :)
[Samsung Galaxy Nexus] haydonxda:
Kernel 277, stock JB with the exception of the kernel.

I have no problem.
[Samsung Galaxy Nexus] !crazy:
Same here. Stock + frano's kernel no reboot.
[Samsung Galaxy Nexus] ciprianruse88:
hy guys,

i've just switched from my gs2 and i want to ask you all because i'm new to nexus,what is the best aosp/aokp rom to use with this kernel?.on gs2 i've used slim ics with siyah kernel but here things are diffrent and i really want to pe up to date.please!
[Samsung Galaxy Nexus] Tarun95:
Minco + franco. Or best is stock + Franco
[Samsung Galaxy Nexus] osm0sis:
Stock with Franco flies! Idle drain for me is 0.6/hr. Just stunning!
[Samsung Galaxy Nexus] ciprianruse88:
i see you have tocuch recovery.can you give me a link for downloading it and the steps to install because i have the stock recovery installed from rom manager and i saw that some roms require touch recovery.thanks
[Samsung Galaxy Nexus] Tarun95:
Download galaxy nexus toolkit and flash the touch recovery. Stay away from cm/aokp if u want perfect stability and speed
[Samsung Galaxy Nexus] yellowdie:
Hey Franco, does the final release of the Linux 3.6 kernel effect us at all? I know we're on 3.0.43, but you mentioned taking wifi drivers from 3.3 and 3.4. So I didn't know if the 3.6 would be something of value to us. I wasn't sure if the new "hybrid sleep" is just for Linux itself or if it could apply to Android. Thoughts? :)
[Samsung Galaxy Nexus] renaud:
Wifi drivers for this chipset are not really part of the official Linux kernel. And the implementation of android changed quite much as from 3.4.
[Samsung Galaxy Nexus] osm0sis:
My sig is full of links for a reason. ;)
[Samsung Galaxy Nexus] PotatoEngine4:
Yes
[Samsung Galaxy Nexus] franciscofranco:
Those Wi-Fi drivers come from Google's modified 3.4 Kernel, it doesn't com from the main Linux Kernel. That hybrid sleep is just to suspend the whole system into an image and to ram in case the device (being a computer or whatever) loses power when its hibernated and the system can restart from the image.
[Samsung Galaxy Nexus] milesmarrero:
Welcome. I love paranoid android, its a very smooth rom, and the tablet mode frees up so much real-estate. Some other roms I enjoy though are rasbean and codename android. CNA is probably the most customizable rom in terms of system ui etc. However, pure speed has to go to rasbean, but the ui of it and lack of customizability make me stick with the Dark Paranoid Android rom. Trying to throw out some good ones ;D
[Samsung Galaxy Nexus] Coolgoly:
Hi guys,I'm not sure on milestone5 gpu clock.Is it 307Mhz or 384?Is running very well here on stock JB @ 1,4Ghz,rocksolid with undervolt and good battery life.

Thanks.
[Samsung Galaxy Nexus] The Gingerbread Man:
M5 is 384 gpu

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Cool, good to know. Is there anything we can glean or cherry pick from 3.6 or is it a totally unrelated beast?
[Samsung Galaxy Nexus] TheMan0790:
So I thought my constant wifi data pulling was related to my home router. Seems like its not the case. On multiple routers I am seeing my wifi pull down data constantly. I have wiped the phone and reflashed cm10 and this kernel and I have checked for any apps trying to pull in data. Is this is a kernel or ROM issue? Can anyone explain why this is happening? (I am running the latest Franco nightly kernel)
[Samsung Galaxy Nexus] Pkt_Lnt:
Go to Settings > Apps > Running and you will get some idea. BetterBatteryStats under the Network Stat will show you what is accessing wifi.
[Samsung Galaxy Nexus] TheMan0790:
Still not entirely obvious...wouldn't this same problem be present when on data? I don't see this at all on 3G, but once WiFi is switched on the problem is prevalent.
[Samsung Galaxy Nexus] livintall:
After reading a little on TCP protocols I decided to give Illinois a shot and ran it side by side with a couple other protocols and consistently got much better speeds up and down on wifi, 3g, and 4g. This read is very interesting.

en.wikipedia.org/wiki/Tcp_illinois
[Samsung Galaxy Nexus] Pkt_Lnt:
Mine is obvious. Been on wifi only, have not touched the browser or music, but they are getting data. Google seems to always share no matter what. I see what is using data just why.

Galaxy Nexus / Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Random shot in the dark: Do you have location services on? Try turning it all off in the system settings (like my screen shot) and see if that shuts them up. Just throwin' it out there. =)
[Samsung Galaxy Nexus] ChazzMatt:
Yeah, I wonder why DD-WRT uses "Vegas" as the default? :confused: When I saw the test results from Franco, I immediately went to my DD-WRT router and changed it to Westwood!

I've been running DD-WRT for a couple of years now and even hooked at least a dozen friends & family up with DD-WRT on refurbed Linksys WRT160n v3 routers. But I really had no idea about these TCP congestion avoidance algorithms.. I just assumed if DD-WRT was using "Vegas" as default, it must be good.

When Franco updates the kernel app to allow the GUI to change the TCP congestion avoidance algorithm on my phone, I'm changing from default Cubic back to Westwood+. ;)

(I know I can do it through terminal commands, but I'll just wait for the GUI.)
[Samsung Galaxy Nexus] lsv-1:
Hello guys, I've been using trickster mod app because the franco.kernel updater suddenly stopped saving my settings upon reboot, and now after updating trickster mod the same thing happened, I just uninstalled both apps, cleared caches, fixed perms but the same thing happens, can someone please help out to fix this issue? Is there a file that doesn't get deleted when uninstalling the franco app? What could be the cause of the issue? I'm using stock odexed JRO03C fw.

thank you.
[Samsung Galaxy Nexus] TheMan0790:
Turned them all off...problem remains.
[Samsung Galaxy Nexus] gm007:
Go to data usage and check which app is pulling data.
[Samsung Galaxy Nexus] osm0sis:
I think Vegas probably is good. As are Illinois, Veno and Westwood+, all of which seem like good candidates. Throughput isn't everything, and I think a lot of it will come down to real world feel, since we're really talking about latency and congestion. Each algorithm is designed with a different type of network in mind, some long distance, some wireless, some "wide", so it'll be interesting to see if we can figure out which one works best for cellular and wifi both. I'm looking forward to the new Updater version so we can really get a lot of peoples opinions on the different ones. :)

You've got a rogue app or three. You might have to start uninstalling and see when it stops. :(
[Samsung Galaxy Nexus] k_nivesout:
Why would it be necessary to do this monthly? Also, deeply discharging Li-ion batteries is not an advisable thing to do, assuming you want your battery to last for a while that is.
[Samsung Galaxy Nexus] osm0sis:
Because for the rest of the month you're charging it from 10% or 40% or 85%. Once a month it's recommended to discharge it all the way down to make sure the battery remains calibrated. It is what it is.

My earlier post in the thread sums up my reading on the subject so far and also why you should never wipe your batterystats:
[Samsung Galaxy Nexus] Pkt_Lnt:
Plus all modern, quality Li-Ion batteries have a built in cut-off circuit that you cannot discharge them past the safe point.
[Samsung Galaxy Nexus] drawde40599:
your supersu is updated?

If u read back few pages , guy had similar issue and recommendation was update your ROM. Personally If i was u and didn't want to update i would do full wipe ( format system, ( it won't erase SD) ) and try agn.
[Samsung Galaxy Nexus] TheMan0790:
Update to my problem...I've tried multiple ROMs, multiple routers, multiple kernels and even uninstalled most of my downloaded apps that I believed could be causing me problems...all to no avail. I literally have no clue how to proceed with this...
[Samsung Galaxy Nexus] k_nivesout:
What I'm saying is that I don't see why this would need to be repeated. It shouldn't matter what the depth of discharge is at any point after the initial "calibration" (unless somehow the files storing the battery info are deleted). Why once a month? Who is recommending that this be done? I guess I just don't really understand how the phone and/or battery un-calibrates itself on a monthly basis.

There's also the issue of li-ion battery health. It's a verifiable fact that the deeper the battery is discharged, the shorter its lifespan becomes. I can understand the premise behind an initial calibration, although with devices being as smart as they are now, I have my doubts about this being necessary (I also would need to research this further to determine the necessity). I just think that people should be aware that by calibrating the battery in this way, they are decreasing its overall lifespan and capacity. Of course due to their nature, li-ion batteries lose capacity over time, but you're greatly speeding up the process the more you run the battery down.

If you can point me in the direction of any further sources/info on the subject, I'd be interested in checking it out. I found this particular link helpful and informative regarding li-ion batteries: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

---------- Post added at 07:09 PM ---------- Previous post was at 06:55 PM ----------

My initial point had nothing to do with safety. Of course (ideally) the battery isn't going to physically fail if the phone turns off due to low battery. However, the poster with which I was having the discussion was advocating not only running the battery down to the point at which the phone shuts off, but to continue turning on the device to run the battery down to the point at which it won't even power on the phone.

From a battery safety standpoint, this isn't a good practice (although like you said, there are protections in place that should prevent a catastrophic battery failure, but things can and will go wrong). From a battery health standpoint, it's not good either. As I said before, the deeper you're discharging you battery, the more you're stressing it and prematurely reducing its capacity and lifetime.
[Samsung Galaxy Nexus] momomok:
reverting to r276 seems to be a temporary solution for me... :)
[Samsung Galaxy Nexus] :
Battery does get out of calibration but the system has "checkpoints" at different percentages. These checkpoints are setup at different intervals depending on the hardware. Let's say there is a checkpoint at 90, 75, 60, etc when the battery reaches one of those numbers, you get a true reading. All other percentages in between those points are estimated. That's why if you let your phone sleep for a half days, then suddenly you start watching movies, playing games etc you will see your stats take a nosedive. Percentages displayed are an estimate of whatever charge is remaining on the battery.

I read the above information from a credible source a while ago. I apologize for not using proper terms or not sounding technical. I can update the post once I find the link for this information.

You shouldn't need to calibrate your battery ever. Just use your phone normally man.

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

There is one of the links. Read and don't believe wiping stats on CWM recovery will make some magic happen. There is a reason why that option is not available on TWRP recovery...
[Samsung Galaxy Nexus] osm0sis:
While I agree that charging to full capacity and fully discharging can reduce life in the long run (the reasoning behind BLX), the key words are still "in the long run". The time you notice any effects to your battery is on the order of years, to the point that you'll be moving on to a new device before you ever run into battery problems. That's the reason Franco changed the BLX default back to 100. Of course, as Pkt mentioned, these are modern batteries so there's no danger of physically damaging the battery from polarity reversal in a deep discharge, and there is no "memory". That said, the battery stats can get wonky and need occasional recalibration if you want an accurate reading. This is especially obvious with people who swap batteries on a regular basis, but can happen even in single battery setups just due to the fact that we don't discharge them, eg. a person whose phone is always at 25% every night when they plug it in. As for monthly, I read that somewhere, but I'm sure you could probably do it every few months, or even once a year if you want. I believe the other piece was that even though these are modern lithiums, it is still good for battery health to fully discharge them once in a while.
[Samsung Galaxy Nexus] :
Old wives tales above.
[Samsung Galaxy Nexus] osm0sis:
Yeah, sorry. I was painting in broad strokes there. I explained it better in my last post.
[Samsung Galaxy Nexus] :
Hey no problem man. I use to believe that as well.
[Samsung Galaxy Nexus] Savant:
An old fellow atrix user ... sorry for ot.
[Samsung Galaxy Nexus] franciscofranco:
Just a heads-up: TCP congestion avoidance algorithm option to change it from the the app is working just fine, hoping to release it in a few hours ;)
[Samsung Galaxy Nexus] Wynnded:
Awesome! Now maybe these guys will stop talking about batteries in a kernel thread....;)
[Samsung Galaxy Nexus] franciscofranco:
Yes, I hope so, growing tired of those posts.
[Samsung Galaxy Nexus] Hungry Man:
Anything from the 3.6 kernel look worth patching in?
[Samsung Galaxy Nexus] Wynnded:
That was answered just three pages ago....come on gang, if you don't have time to read back a little, you don't have time to post. PLEASE?:D
[Samsung Galaxy Nexus] Culex316:
Awesome! Now if only there were a kernel forum thread congestion avoidance algorithm available.....
[Samsung Galaxy Nexus] osm0sis:
Sorry Franco, I was just trying to help the poster with the oddly flatlining battery issue and got derailed... :eek:

:laugh:
[Samsung Galaxy Nexus] LibertyMonger:
All this battery calibration jazz is all rumors. We all been using batteries all our lives, they really haven't changed or progressed much since I can remember, we never had to calibrate flashlight batteries! Lmao. They are batteries, we just use them til they die and then replace them lol. I been trying everything I been told in these forums about our batteries and calibrating never seems to make any difference whatsoever. Besides, it seems our carrier or manufacturer would be telling us this as well. Old wives tales is right! Lol sorry my 2 cents ain't worth much!
[Samsung Galaxy Nexus] franciscofranco:
Not that. I really dislike this type of posts:

"amg brah wuts best settings fur bettary lifes, give plz, danke you" because its a big "**** you" in my face for all the time I spend explaining every change I do in the kernel + a big "**** you" in all the users that come here to help daily :)
[Samsung Galaxy Nexus] k_nivesout:
Welp, back to the friendly thread where people don't get jumped on for an OT post or two.. Just trying to get some useful (I thought) info out there.

Oh, and I'm not exactly seeing how those complaint posts are anything other than thread "congestion". Hypocritical much?

Laterz.
[Samsung Galaxy Nexus] simms22:
are you guys using pgm?
[Samsung Galaxy Nexus] franciscofranco:
PGM usually does that?
[Samsung Galaxy Nexus] simms22:
i count 8 stars in place of letters, thats unlike you. why so few? :eek:
[Samsung Galaxy Nexus] simms22:
funny how many times i read those symptoms, its one of the last things in a last_kmsg before the device reboots.
[Samsung Galaxy Nexus] franciscofranco:
Hmmm its 6am and I thought I had more stars in the post...****, I'll try better tomorrow :) I don't know whats my star record actually, gotta start counting.
[Samsung Galaxy Nexus] franciscofranco:
Ok finished for today, so before I go to bed heres v6.9 changelog:

6.9

Common:

* Faster app opening time

* Add detection for SuperSu and give a one time warning if you're using Superuser

* Add TCP Congestion Avoidance algorithm swapping interface (One X support on this one is disabled because it needs an update in the kernel)

* Bug fixes

Galaxy Nexus:

* Change Interactive Governor Control way of handling input_boost_freq and hispeed_freq

Galaxy SIII:

* Add JellyBean kernels detection/download

* Add input_touch_booster interface

Email me if a problem arises.

Should be up as soon as Google refreshes their servers!
[Samsung Galaxy Nexus] osm0sis:
Franco, while you're around..

I did some searching on this and am still coming up empty handed. All I can seem to find are other custom Android kernels that have algorithms implemented, nothing on stock. Does stock JB kernel use Cubic, or does it not use an algorithm at all?
[Samsung Galaxy Nexus] franciscofranco:
Stock kernel comes with the feature entirely disabled. After we enable it Cubic is the default.

See y'all tomorrow.
[Samsung Galaxy Nexus] RoscoeDpG:
NICE! cant wait to try it out! but last few hrs my market crashes on any app install :confused: anyone else have this prob tonight
[Samsung Galaxy Nexus] J-Hop2o6:
No issues with my phone using PGM
[Samsung Galaxy Nexus] simms22:
I'm not saying its a problem with pgm. its possible that, on first boot, people are trying to use pgm to wake the device before its granted su, causing a panic.
[Samsung Galaxy Nexus] Pkt_Lnt:
Yes, I got that once, learned my lesson, now I give it a few minutes, about five, after boot before I touch it and let all apps get su access first. :good:
[Samsung Galaxy Nexus] nuwan32:
uhh franco, im runing SuperSU, but it just told me i dont have supersu running so i might get problems... etc.
[Samsung Galaxy Nexus] Culex316:
Bug report!

Franco, with this new app update, I get a Force Close whenever I open the app and switch to the CPU speed/governor control tab.

I'm running your latest nightly with stock 4.1.1. Jelly Bean and I have SuperSU installed and it grants it permissions normally (app did not force close before)

Here is a copy of the logcat:

https://docs.google.com/open?id=0B9DcPJCiP10ndDFWM0haVTZaRUU

Work your way from the bottom of the file upwards