yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] coolbho3000:
The lag should not be related to the voltage. It's related to your specific chip, as we understand it right now. I'm working on a solution, but the overclocking potential of this chip isn't looking that great (even to the supposedly 4460 "stock" 1.5GHz) because of a processor erratum. If it weren't for this erratum, we would have been able to do 1.8+ easily. And the SoC demands such low voltages too. :(
[Samsung Galaxy Nexus] JohnnyTrue:
I dont know where to post. I got a problem, my phone doesnt see USB drive and external HDD but sees my mouse. Do I need to do so that my phone will see usb driver. THx
[Samsung Galaxy Nexus] sluflyer06:
I'm not sure if its in this thread or another development thread, but did you create the location that it mounts USB drives to BEFORE attempting to mount it? If not apparently it won't work until you do.
[Samsung Galaxy Nexus] mohitrocks:
Hey Francisco,

sorry if this is the wrong place to be asking this... but is it possible to run the processor at its original clock of 1.5GHz on the Galaxy Nexus? If not, could you please tell me why? This could potentially be a deciding factor for me on whether I will be keeping the Galaxy Nexus or not. Also, is the overclock of the CPU directly proportional to the overclock of the GPU? Thanks.
[Samsung Galaxy Nexus] franciscofranco:
Hey.

The best thing you can do is to read this thread: http://xdaforums.com/showthread.php?t=1380064 it contains everything you just asked me :)
[Samsung Galaxy Nexus] franciscofranco:
Anyone online that wanna hit me up @ google+ chat for a kernel test?
[Samsung Galaxy Nexus] minooch:
just added you as a friend on G+

I can try it if you want?
[Samsung Galaxy Nexus] franciscofranco:
Ok great. Invite me to the chat and we can talk.
[Samsung Galaxy Nexus] minooch:
I can't invite you to chat for some reason :/

Don't know why - usually works fine

EDIT: Might have just worked from my mobile
[Samsung Galaxy Nexus] JohnnyTrue:
one guy told me to type "mount -t vfat /dev/block/sda1 /sdcard/usbstick" interminal. I did it and got http://dl.dropbox.com/u/14939885/Screenshot_2011-12-07-18-57-20.png and there are still no folder in the phone.
[Samsung Galaxy Nexus] tholmewood:
I dislike the recent upgrade to your Kernel as on several occasions I experienced screen corruption on returning from Screen Off state. Reverted back to previous version and all is fine. Not sure if this is an issue or just that my silicon is the runt of the yield. Shame, my battery seems so much better than stock using your kernel.
[Samsung Galaxy Nexus] nic85:
lol?

tryed imo lean kernel..seems good but i return to franco's 11

and now i have 2mA in standby :confused:

so i think battery widget is not reliable?
[Samsung Galaxy Nexus] mfish123:
Sounds like your stating that the galaxy nexus does not have a current sensor, meaning that battery monitor widget mA reasons are just estimates. Is my thinking correct? Are you 100% positive that there is not a current sensor?
[Samsung Galaxy Nexus] jknisley:
Question about this: Is it number of wakelocks or time up that the wakelocks cause or both?
[Samsung Galaxy Nexus] PresPPsP:
Does your app use wifi for location awareness? The reason I ask, is maybe you're losing gps signal and then the network-based location is coarse enough to make the phone think it's somewhere else. Just another idea.
[Samsung Galaxy Nexus] Manafa:
How can I check my current bootloader version?
[Samsung Galaxy Nexus] zephiK:
Go into bootloader mode and look at the bootloader version.
[Samsung Galaxy Nexus] mfish123:
I was thinking the same exact thing. If there is not current sensor, then the data supplied by battery monitor widget cannot be deemed reliable and all we're really doing is introducing a tad more drain for the app to continually update and calculate the estimates. Hopefully someone can chime in with a definitive answer regarding the existence of a current sensor.
[Samsung Galaxy Nexus] ellesshoo:
The battery controller chip does not report current to the phone, so yes, any mA number anyone has been tossing around is just an estimate.
[Samsung Galaxy Nexus] Thracks:
I'm putting that theory to work right now. I've just removed battery monitor, and I want to see if the Android OS process stays awake far less often. If it does, then we know (at least in my case) that it was being kept awake to assist in the tabulation of estimated draw.
[Samsung Galaxy Nexus] 3c:
I can tell you it won't make a difference. On the nexus the app will wake up the device every 5 minutes (the default) for a total of 2 or 3 seconds of CPU per day.

On a HD2 it is waking up the device every minute for a total of 8 seconds and a resulting drain of 1 or 2mA in standby. :D

I get 3mA in standby with AOKP M2 and JDKernel. Used to get 5 or 7mA. :D
[Samsung Galaxy Nexus] luffyp:
About the battery

So I did some research and here's what I found:

According to Engadget, the Galaxy Nexus uses the Fuel Gauge sensor MAX17040 by Maxim.

If you read the description on their press release, MAX17040 uses its algorithm that calculates battery's relative state-of-charge (SOC) using only voltage measurement.

As a side note, because of their algorithm, you shouldn't need to calibrate the battery by running it down to zero.

So, my conclusions,

Our Galaxy Nexus doesn't have a current sensor because it doesn't need it in order to calculate the battery's state-of-charge.

"Calibrating" the battery by running it down to zero and charging to 100% is not needed and may damage your battery if you let it die too often.
[Samsung Galaxy Nexus] drawde40599:
I can't remember what the fix is its realy something simple, go over to the Samsung captivate thread and read around in there u will find fix there, if no one reply here, don't ask questions there just start looking at all the bricked threads, u may need flash back to stock with Odin but can't remember,i do no ur NOT screwed yet(:

BTW I DO NOT MEAN FLASH A CAPTIVATE ODIN FILE ONTO UR GN! just mean read over there then come find our Odin file
[Samsung Galaxy Nexus] 3c:
Way out of scope ;), but quite interesting. Though I'm not sure where you got conclusion 2 from? Indeed the Nexus doesn't have a current sensor. Have you you found the algorithm to calculate % from mV? Asking this because if you look at the mV curve, it sometimes goes up while % goes down and vice-versa! Sometimes it's flat and % goes down anyway!?

Having used many different phones, I noticed very quickly how precise the Nexus was. First phone that shutdowns at 0% on first run, compared to others shutting down at 5 or 3% initially!

Can you post the link to the referenced materials?
[Samsung Galaxy Nexus] mfish123:
Thanks for clearing this up. I think we still have enough tools by looking at our run times in Android settings and utilizing betterbatterystats and cpu spy to see what's going on.

---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------

Cool - I'm interested to see your results. Now that I know that we don't have a current sensor I'm also going to disable the battery monitor widget too and see if that helps.
[Samsung Galaxy Nexus] 3c:
This fact was confirmed by Samsung engineers. To compare the Galaxy S2 has one, but it's disabled (at least from a user/app perspective)!

Nevertheless the estimation is very accurate when % fluctuates and needs more time when it's steady. But I always manage to find the lowest consumption in standby, hence the screenshot I posted a few pages back.
[Samsung Galaxy Nexus] mfish123:
Nice....I finally retired my HD2 after almost 2 years to come over to the GNex on Verizon. That was fun phone with Hyperdroid running on it. Sorry for the OT post but I had to say something.
[Samsung Galaxy Nexus] PeterGuru:
Yes, it does ...

Yes, it uses Wifi for location awareness; however, GPS is not involved in this case. I don't use it and have it disabled within the app.

As long as there's a Wifi signal, the WORK profile should not change while I'm within the Wifi signal's field of use.

I've been doing a bit more testing and it seems the problem may be solved. Perhaps it was an issue with an earlier kernel. I don't know right now. At this point, with Hotplug Enabled, everything seems to be working.

Peter
[Samsung Galaxy Nexus] Thracks:
Update: After removing Battery Monitor, Android OS is now a distant third to phone idle and the display. It looks like it was, in fact, keeping the OS alive. I think I've solved the weirdo drain for my phone.
[Samsung Galaxy Nexus] mfish123:
100% - 90% drain

I've seen plenty of people posting slow battery drain while in deep sleep from 100% - 90%. In my case, my drain is always much quicker from 100% - 90% and I've seen other posting by various other users confirming the same behavior.

I have heard that once you hit 100%, if you leave your phone on the charger, it actually stops accepting a charge and starts discharging but leaves your battery meter at 100%. So if you take it off the charger after its been sitting there @ 100% for a few hours you may actually be closer to 90% so to compensate the battery shows a fast drain down to 90%, when taken off the charge,r to quickly get back to an accurate reading. Not sure if this is true or not.

I've taken my phone off the charger a few minutes after hitting 100% to try and avoid that situation and that doesn't seem to slow the initial 100% - 90% drain. I've almost used the battery calibration app upon installs of ROM updates, to calibrate, once it hits 100%, but based on these last few posts it sounds like that is unnecessary.

Is there anything I can do to have my drain from 100% - 90%, drain at the same rate as any other battery percentage range, assuming all other factors are equal and that I don't have rogue apps or underlying problems causing wake locks?
[Samsung Galaxy Nexus] akalias1981:
Hi Francisco, when you say you have tight app control do you mean with regards to installation or just making sure nothing is running when you want to idle? Everyone shuns task killers but I can't think of a better way to ensure decent idle than to use a kill all widget just before putting the phone down for the night.
[Samsung Galaxy Nexus] 15israellai:
A big congratulations to Apple. Finally they got it. Now what are they doing next?

And congrats to Google for having always avoided that shape.

Transmitted from my Nexus Prime
[Samsung Galaxy Nexus] despard:
**** crapple. Only **** loves their crap...
[Samsung Galaxy Nexus] KJW979:
No, but who knows maybe some day they'll realize what awesome kernels Franco makes and try to patent something he does in his kernels, far fetched I know but.....
[Samsung Galaxy Nexus] Kurre:
Hmm I have read some doc about these changes after GB, but can't recall where I could find it now :) but anyway, since these adj values ain't read from the build.prop, hacking services.jar is the only certain way to do it.

Also IIRC, those priorities might not stick for a long time since they tend to fall back to priorities defined by OOM groupings. So constant checking/adjusting might be necessary (this I can't recall so clearly).

In my SGS days, there was bunch of people trying to get that kind of scripts working, but there was always some kind of problems and eventually they all gave up :(

These things could be investigated by digging processes list/OOM groupings list etc via some app, like Auto Memory Manager..just to make sure that things are working correctly :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Raijin:
Nothing to do for me then... people that use another launchers apart from the list, please report it.

Regards,
[Samsung Galaxy Nexus] Krayvon:
!

i'm using 192/793 ondemand and i have had 0 issues,

a decent benchmark result and crazzzzy good battery life. i'm gonna try to see if i can get 10 hour screen lol
[Samsung Galaxy Nexus] sqjzb:
hello Franco.

Hello ..

I realized that pc doesnt recognize my phone in normal boot mode.

Am using dark paranoid 2.521 toro, with franco kernel r298.

Ofc the fast charge is off, nd the cable + usb port of the pc is fine.

Funny thing is that my pc can recognize my phone in fastboot mode. This tells me my phone's usb port aint broke either.

Yet whenever I turn my phone on, wont charge and pc wont detect it.

I tried to change the governor from interactive to ondemand, along with the IO scheduler from deadline to noob, yet nothing happened.

Can anybody please help me?

Is this just happening to me?

is there a special option on the franco kernel app to alive my phone on pc?
[Samsung Galaxy Nexus] The Gingerbread Man:
You need adb and mtp interface driver installed http://xdaforums.com/showthread.php?t=1379875

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sqjzb:
forgot to add that usb charging off from the portable battery pack ain't working either. it works with normal stock Gnex. but not mine until I turn it off.. lol
[Samsung Galaxy Nexus] CADude:
AOSP 4.2 seems to come with kernel 3.4 and I'm excited to see what Franco makes of this.
[Samsung Galaxy Nexus] gautam_nexus:
any screenshots to confirm?
[Samsung Galaxy Nexus] androidkid311:
Looooooool!! I'm pretty sure your phone will lag a bit lol
[Samsung Galaxy Nexus] aimcr7:
Look at general section, there are some screenshots of 4.2 on Nexus4 and it comes with 3.4 kernel, i assumed GN may get 3.4 too.
[Samsung Galaxy Nexus] OMFGNuts:
I somewhat think franco will buy nexus4 and forget 'bout us, and we're not getting any awesome franco's-magic-kernel :D:D

/p.s - hope not
[Samsung Galaxy Nexus] Kurre:
Nah, I have faith in Franco and I believe that he'll continue producing great kernels for us until he thinks that there isn't anything more to improve ;) fingers crossed :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] veitograf:
hey guys,

i just tried the latest nightly (r298-384GPU) on my paranoid nexus and now doubletwist doesnt want to work anymore:(

here is what i tried already:

-with/without wiping cache/dalvik after flashing the kernel.

-restored backup with titanium

-cleared app data

all of it doesnt seem to work for me. what else can i try, i really love doubletwist.
[Samsung Galaxy Nexus] doomed151:
Hey Franco, there's something bugging me. Did you somehow forget to submit 7.1.6 to AndroidPIT? It's been a few days and I'm still not getting it.
[Samsung Galaxy Nexus] osm0sis:
If I understand Franco's script correctly, I think he avoids having to recheck by changing the permissions to lock the file.
[Samsung Galaxy Nexus] marcocsh:
With r298, I am now one of the 3-hrs club:D

My settings: 192-1305, screen off max 537, interactive.

Stock governor settings.
[Samsung Galaxy Nexus] aimcr7:
You should look at this one :p

I am on 4hours club :cool:
[Samsung Galaxy Nexus] ciprianruse88:
no more r300?
[Samsung Galaxy Nexus] Kurre:
Ah, that's probably right, I think I missed that one :) thanks for correcting me :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] supernova_00:
I had my phone in my outside coat pocket in -45 F weather last year for 12 hours (working outside in Alaska) and had no problems. Now this summer when I had my phone in my pants pocket in 105 F weather, the phone rebooted like a SOB
[Samsung Galaxy Nexus] Shadow-Nexus:
Bro just wait

Franco said "soon" so just play the patience game with everyone else
[Samsung Galaxy Nexus] mixtapes08:
That's a bad strategy if that happen considering the fact that many gnex users bought his app.. I think he will continue support of this device... .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Coming soon. Patience will definitely pay off. Trust me. :)

And the N4 is getting kernel 3.4, but I don't think GN ever will. As far as keeping up with this, Franco has said he will shift his primary focus to the N4, but will keep this one alive still. Meaning what will probably happen is he'll do the work on the N4 and if it applies to the GN then it'll get ported/added in. Like he does with the N7 kernel kinda. :)
[Samsung Galaxy Nexus] SpecRek9:
I think more people will buy the N4 (including me) for having Franco's Kernel && support than for having the device itself :P

btw, what will include r300, more updates to audio drivers?

Cheers.
[Samsung Galaxy Nexus] Admiral2145:
When the note 2 drops on VZW... I'll be done with Nexus series.... Note 2 does far more than any other tablet or phone out. Hopefully Franco will show us some love on that new device.
[Samsung Galaxy Nexus] phishn:
The single core issue I have experienced happens when the phone soft boots after freezing up. Now to figure out what's causing the freeze that initiates the soft boot.
[Samsung Galaxy Nexus] Leegalaxy:
Actually, in our super secret gnex forum, Franco said he will support the kernel for everyone but @OMFGNuts. Sorry;)
[Samsung Galaxy Nexus] bigmase521:
The best battery life I've ever gotten!

r298 is THE single best thing to ever happen to my GNex, so for that, I thank you Franco!!

Running AOKP JB Milestone 1; Trickster Mod; 192-1305, screen off max 537; dyninteractive.

Mostly idle time w/ not much screen usage, but OH.MY.GOD.! Just battery-sipping goodness! :victory:

One question, anyone else getting high Maps usage like I am? :confused:
[Samsung Galaxy Nexus] Langduscher:
Turn off location services and Google Now & remove Maps: and be even more amazed :good:
[Samsung Galaxy Nexus] bigmase521:
I thought about this but.. I use Google Now, and I use Maps for Nav when needed. It just strikes me as odd since I haven't used either in the last day of those stats and the Maps usage is so high. I've been using Google Now since release and never had Maps battery drain like this :confused:
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Anybody using Battery Widget Reborn? Pro? It gives a discharge delta per 1%. Right now I'm at 29 minutes per 1%. At home, WiFi always connected. Interactive/Ondemand 192-1228, 537 Screen Off, 537 hi_speed freg, r298. Just wondering what others who use this app are seeing.

RF
[Samsung Galaxy Nexus] _chanstar_:
When you mention Google Now, are you referring to the actual cards and personal assistant? OR just the Google Voice Search as some confuses the two. With Google Now off, you can still perform voice searches.

As for Maps, you should disable all location settings in Latitude if not used, and refer to http://xdaforums.com/showpost.php?p=29420959&postcount=7059 for the rest.
[Samsung Galaxy Nexus] bigmase521:
Both. I definitely use the cards for traffic, sports scores etc. AND voice searches. So for that to work I have to leave the location services on. I just want to know about the increased battery usage in the latest iteration of Maps. It was never this bad with previous versions w/ location services turned on all the time.
[Samsung Galaxy Nexus] kitecarl:
If you're not using Maps all the time, I would just freeze the app in Titanium Backup and defrost only when needed. This has helped battery life for me
[Samsung Galaxy Nexus] whitedragonz83:
I found times it just went nuts and cleared it with a reboot of the phone.
[Samsung Galaxy Nexus] bigmase521:
Thanks for the tips. I just hope Google figures it out soon b/c like someone said earlier, it makes me wonder what battery life COULD be like w/o that drain. I'll keep an eye on it but obviously my idle battery life is still stellar. Thanks Franco! :good:
[Samsung Galaxy Nexus] dracon6ai:
Get Rom Toolbox Pro and disable all the receivers on Google Maps. Google Now will work like normal and maps wake locks will drop dramatically. I use Google Now with everything enabled and love it.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] superbobup:
Try setting Latitude to "manual" if it's on automatic. This helps quite a bit, but still lets you have Maps + Location Services for your purposes
[Samsung Galaxy Nexus] _chanstar_:
Check Latitude location settings. When I flashed the GAPP package for 4.2, the Maps portion re-enabled a location setting in Latitude.
[Samsung Galaxy Nexus] notreally:
I contacted doubletwist about this a few weeks ago and this was their reply:

It seems like their dev never got around to it. Shame I actually used the app daily and liked it enough to pay for it. Haven't been able to use it since I started using custom kernels...

Switched over to the Walkman app ripped from the Xperias. No issues other than the fact it ignores saving playlists or favorites.
[Samsung Galaxy Nexus] franciscofranco:
SQite is a SQL lib in the Android rom, its not related to the kernel, so I doubt that kernels make that app to break.
[Samsung Galaxy Nexus] nuwan32:
Lol what... Bluetooth was never even on.any idea why this might happen?
[Samsung Galaxy Nexus] franciscofranco:
No idea, thats not kernel related at all.
[Samsung Galaxy Nexus] amf100:
I just use the Autostarts app. You can control when/if an spp or service starts on its own.
[Samsung Galaxy Nexus] bradstewart:
I'm having an annoying issue with r298, when charging my phone overnight it seems to fall asleep and won't wake up again. The notification light will be flashing if a text has arrived but the screen won't turn on and I have to pull the battery.

I'm running CM10 and have done a couple of clean flashes. This also happened with Xenon.
[Samsung Galaxy Nexus] franciscofranco:
Weird... what are your settings, freqs, uv, governor etc etc?
[Samsung Galaxy Nexus] SupWiz17:
My battery stats are showing the same thing now. Did you just update to the latest paranoid android?
[Samsung Galaxy Nexus] Shadow-Nexus:
Yeah I got it when I updated to PA 2.54
[Samsung Galaxy Nexus] aeroseek:
Awesome with awesome sauce.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
After almost 2 weeks of mostly full time developing I just released franco.Kernel updater v8.0, a complete re-write from scratch of the application:

8.0

* Application 100% coded from scratch

* New design and organisation

* All interfaces have been polished and improved from their initial debut

* Voltages are finally able to be set on boot

* Built to be able to be translated in other languages in the future

* Better code, better superuser calls, better usage of threading, more secure

Thanks Osmosis, Yellowdie and minooch for the testing since the re-write beginning.

We are humans, bugs slip, so if you hit one, please email me.

Wait a little bit for Google to refresh their servers, until then the update won't show.

Please share this post as much as you can, I need lots of feedback. I already have a very much exciting list of upcoming features so the more feedback I get now the better those new ideas will become.

https://play.google.com/store/apps/details?id=com.franco.kernel
[Samsung Galaxy Nexus] johno86:
Please share your settings, CPU, UV, GOV, GOV Control, etc

I can't seem to get more than 2.5 hrs on-screen of moderate usage (youtube, browsing, music, texting, calls)

Which franco. kernel are you flashed on?

AWESOME! Will test it out right now.

*edit

Will test it out as soon as it refreshes to 8.0
[Samsung Galaxy Nexus] Raijin:
Thank you Franco :)
[Samsung Galaxy Nexus] yellowdie:
Let the fun being!!
[Samsung Galaxy Nexus] Shadow-Nexus:
Now we wait for r300 to be complete and the real fun will begin!
[Samsung Galaxy Nexus] neo-X:
Franco you are a legend!!!! This is why I love android!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
It's coming. :D

By the way everyone, when he says "full time," he actually means it. It's 6am his time right now (1am for me). This guy never sleeps. I get new apks from him at ALL hours of the day. Lol. Please make sure to show your love and support for all the blood, sweat and awesomeness that has been poured into this app and kernel.

:) :D :laugh: :good:
[Samsung Galaxy Nexus] Blackcrx:
Can't wait for the new FKU to show up on Google play.

I decided to try some different settings while I waited for r300. Not sure if its been reported but r298 ondemand does not allow changing of the sampling rate. Its always stuck at 30000
[Samsung Galaxy Nexus] Empty Hand:
FKU is up! Looks great! On Power Modes, there is a "None", that force closes the app when selected. I don't have a reason to select that, but just a heads up.
[Samsung Galaxy Nexus] bunnahabhain:
delete
[Samsung Galaxy Nexus] gianton:
Next nightly.
[Samsung Galaxy Nexus] joeyfong:
AndroidPIT pls