yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
I know, and I dont understand why. I hope its fixed on r181 :(. Logs would be useful though.
[Samsung Galaxy Nexus] metalspring:
I didn't think you could get logs if it doesn't at least get to the bootanimation though? I know my PC won't recognize adb until a little way into the bootanimation (not boot logo)

Unless you could somehow make up a flashable logging.zip that writes the log to data/media as it's attempting to boot so someone can pull it later?
[Samsung Galaxy Nexus] franciscofranco:
dmesg log should be there on /proc/last_kmsg
[Samsung Galaxy Nexus] collin911:
Nearly every HD game does that.

Games i have tried:Gta3, 9mm, Brothers in arms 2, Real racing 2, Backstab, Shadowgun.All of these games just do the same thing they just close even without a force close dialog..
[Samsung Galaxy Nexus] drawde40599:
Try installing ur rom then the kernel from recovery in same flash ....??
[Samsung Galaxy Nexus] tibere86:
Maybe I'm among the lucky...I'm running the latest CM9 nightly with r180 with Wheatley 1344/192 GPU512 without issues. This kernel flies!
[Samsung Galaxy Nexus] PresPPsP:
Actually, the chips are made of silicon which is a semiconductor. Silicone is the rubbery stuff you make breast implants out of. Either way, i agree that neither should be ****ty. :)

Silicone DOES have some silicon in it though, hence the name similarities.
[Samsung Galaxy Nexus] smallcaps:
stuck at boot animation loop

hi all,

long time reader first time poster. i have been happily using Franco kernel with aokp milestone 5 but today when i installed #180 (512MHz) and overclocked the cpu to the newly available speed, my phone rebooted and it is now stuck at an endless loop of the boot animation screen.

i have tried to get to the bootloader by pressing power and volume down but it brings me to the odin downloading screen and i can't seem to access cwm. i did a quick search but couldn't find any posts that replicate the problem. i realize that my phone cpu probably can't handle that speed so i just want to get back into the system to downclock. any ideas how as to how i can achieve this?

thanks so much to franco and the community for their combined effort. hope to hear from someone with a possible solution. cheers!

smallcaps
[Samsung Galaxy Nexus] drawde40599:
Volume up and down + power then restore backup or hold volume down + power to get to safe mode ( I think been long time maybe Google it ) then uncheck the settings if ur settings are set from the app go to market and uninstall the app then reboot ...
[Samsung Galaxy Nexus] jeetS:
Flashed 180 an hour ago.

Using wheately and 1536 / 384 .... phones flying no issues so far. phone cannot run 512 without artifacts so I'm on 384 gpu
[Samsung Galaxy Nexus] morfic:
If nandroids fail and a factory wipe does not help, in rare cases a restore from factory images will be the required solution.

That is if reflashing rom + kernel alone wasn't enough. Then nandroid, then factory wipe, then factory image. Exceedingly escalating.

The crash plus boot loop is data corruption which can for example be caused by a combination of aggressive ext4 mount options together with disabled fsync.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] Dr Byte:
I did some digging and found the thread I was reading last year on this topic, http://xdaforums.com/showthread.php?t=1380064

The gist of it is that the chips were designed to work at 1.5GHz but needed a little "hack" to make them stable at >1GHz, DCC (Duty Cycle Correction) except that as I recall, DCC made the higher frequencies work OK at the expense of instability at lower frequencies.

Running with DCC at >1GHz and without at <1GHz as suggested by TI was fingered as causing lockups at transition.

So rather than re-engineer it they artificially capped the frequency and ran without DCC at the maximum speed they thought they could get away with. This, along with the RFI problems ("the RFI volume bug") is the principle reason it took me so long to get a GNexus. When the price dropped below a critical level I was prepared to bite even with the flaws. My old Desire wouldn't have lasted to the next Nexus.

Take particular note of the posts by "Chirality" in that thread above.

Also, an excerpt from a post by coolbho:

Basically we've got a clock generator. For frequencies under 1GHz, you're supposed to run the "MPU DPLL" at double the desired speed and an internal clock divider will bring that down by 1/2, so we're running the DPLL at 2GHz at 1GHz and 2.4GHz at 1.2GHz. For 1.5GHz we would need to run the MPU DPLL at 3GHz, which is where we run into problems - it simply doesn't want to go that high on most peoples' devices.

TI's solution to this was a feature called Duty Cycle Correction, which is needed to use the frequency without a 1/2 divider, making it so we only have to run the MPU DPLL at 1.5GHz to run the MPU at 1.5GHz. But this revision of the 4460 has a major bug where switching DCC off (to switch to lower frequencies) causes crashes. This makes DCC utterly useless, so we're kind of stuck here.
​

I haven't looked yet to see what Franco does with DCC. Other stuff going on :)

Apologies if I misrepresent the thread from my vague recollection six months later :)

Running happily on #180 here, wheatley 192-1036. Not a single glitch, and it's more than fast enough for my purposes. Too early to compare current draw in standby, but it appears no worse than OnDemand at the same frequencies. It *is* spending more time at 1036MHz though, and very little at 192.

The intriguing question is: with Franco's kernel running so efficiently, and with a stable Wheatley governor using the power-saving state while awake, will it be possible to run the phone with DCC enabled with core frequencies >1GHz at all times? For my part, it's irrelevant. I can run with one CPU off, and the other at 1GHz :)
[Samsung Galaxy Nexus] THE_KINGDOM:
I noticed a glitch with earpiece audio being extremely low volume even on maximum volume, after removing it from aux audio output connection (note: this applies to audio while on phone calls)

Earpiece audio volume is low after aux disconnect and can be resolved be putting speakerphone briefly on and then off, earpiece volume then returns to normal volume thereafter.

This has happened since milestone 4, try it out for urself.
[Samsung Galaxy Nexus] metalspring:
Oh right I remember that discussion I think...I remember worrying if the gnex would be able to be overclocked since they couldn't find a decent workaround it was either you run an over clocked kernel that couldn't go under 1GHz or a kernel with stock speed...glad they did eventually get that workaround

Off topic- I kinda wish I waited just awhile to get the gnex, i love my gnex but that sgs 3 is looking pretty darn good...oh well maybe I'll save up and buy it full retail

Also, are you planning on making kernels for the galaxy s 3 too Franco?
[Samsung Galaxy Nexus] franciscofranco:
It's fsync(), my mount options are not unsafe anymore for a few releases already ;)
[Samsung Galaxy Nexus] franciscofranco:
That's basically the BIG problem. I haven't touched the DCC on this releases though.
[Samsung Galaxy Nexus] morfic:
From your smiley i take it fsync isn't off by default anymore?
[Samsung Galaxy Nexus] monkey hung:
Anyone else getting a problem where it says "charging" when the phone is not charging?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
fsync() is deactivated since the beginning, only barrier=0 is now barrier=1.
[Samsung Galaxy Nexus] franciscofranco:
r181

* Some stability fixes when using 1.536Ghz step

* Add 1.420Ghz step for users that can't run higher
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm curious about that my data corrupted today. I figures it was the fsync thing.
[Samsung Galaxy Nexus] nikulogical:
That's liquid damage in your port.
[Samsung Galaxy Nexus] nikulogical:
Question if the phone can't handle a certain freq will it always reboot or is there a chance it'll just freeze or shut off. Om asking because I don't wanna miss any important calls by accident.
[Samsung Galaxy Nexus] morfic:
The kernel developers put it in for a very good reason, if you have too many outstanding commits to your filesystem and you crash that data is lost.

Sure on a spinning disk removing fsync calls saves on power and we do have a battery, so it's almost safe to do so.

Where this math fails is the moment we push the OC to unstable values. Then we are back to the dangerous side of not having fsync.

We all tried it, but me and my users got tired of restoring months ago, now we push speeds in excess of 1536MHz, sure, people still crash occasionally, but my nandroid is months old because crashes no longer eat my whole system.

Franco knows the extreme dangers, he chose to know better.

Before someone gets upset about one dev going into another dev's thread.....consider if warning his users of dangers is truly a bad thing.

Enable fsync for a few days and tell me what you are missing, while on the other hand you know you gain a lot of safety for your data.
[Samsung Galaxy Nexus] nikulogical:
Also does the 1.42 step use smart reflex?
[Samsung Galaxy Nexus] morfic:
Watchdog mostly bites and reboots the phones, only time i have seen a solid locked up phone is with hotplug locking it up, screen on, full power, toasty warm.
[Samsung Galaxy Nexus] hitman818:
Pretty good battery life. Wifi on the whole time.
[Samsung Galaxy Nexus] Gahh Its Lee:
Any chance of us seeing fsync back on so we can test without being paranoid about needing to reset everything? Or nandroid
[Samsung Galaxy Nexus] do0b:
only with franco's kernel where it'll self charge with no power connected and stay constant overnight.

Milestone 3, power saver mode.
[Samsung Galaxy Nexus] schizophrenia:
during the "constant stage" is the data connection off?

the data connection seems to be off when you screen captured
[Samsung Galaxy Nexus] metalspring:
Quick question Franco, I notice the changelog for the latest app update doesn't say whether you changed the wifi pm fast code...I know you said you changed it in the latest nightly kernels and the option in the app wouldn't work anymore

Did the latest app update fix this?

Also I'm curious if wifi pm fast would help wifi tethering too?
[Samsung Galaxy Nexus] timrichardson:
This kernel is the bee's knees: great battery life, great interactive performance. Thanks Franco
[Samsung Galaxy Nexus] raimondomartire:
Franco are you agree? In italian forum two great user fight on this point?

We attend official answer
[Samsung Galaxy Nexus] marc.tulley:
First of all HAPPY NEW YEAR ALL :D

Yeah, very very very happy with AOKP 11 and Franco 7.1. Over 2 days now and still on 35%. admittedly with not much screen time as new year prep work has kept me occupied : )

The standby time is whats blowing me away, did 1% again last night.

Whats on/off:

3G, Wifi on, bt email sync on (30 min). Not sure if it matters but only Google pics, contacts and browser are sync'd (not email or calendar). I've also disabled google+, google search and turned NFC off. Nexus style live wallpaper, Simi clock and System info Widget running. That is about all I can think of that is on/off from default.

NOTE AOKP 12 is out now too :)
[Samsung Galaxy Nexus] hosmsdos:
Franco your 7.1 kernel its just awesome man...great performance and the battery life just wow. Great Job!!
[Samsung Galaxy Nexus] jknisley:
It occurs to me that you're on the GSM GNex. This thread is within the GSM CDMA Development area, but it does work well on the CDMA, too. I wonder if anyone else with CDMA has any battery life numbers to share with the forums. Mine gets about 2-3% drop per hour on standby most of the time. I'm also using Exchange sync, if that matters at all.
[Samsung Galaxy Nexus] sirj00:
Hello and Happy New Year to all.

Would like to share with you some info:

Running Axiom 2.1 with Francos 7.1 it is a winning combination, made in heaven.

No fc's no errors no hiccups. Everything and I mean everything works to perfection. Battery life exceptional. Zero lag and I mean zero. One last thing.

Added this 2 mods and the phone is now in a totally different sphere.

Disable error checking. Gives a nice speed boost.

ro.kernel.android.checkjni=0

This one sets the max framerate of the system to 240 fps. (Well beyond the screen's ability to render. I did notice a nice difference in smoothness.)

windowsmgr.max_events_per_sec=240

link:http://rootzwiki.com/topic/13426-mod-buildprop-tweaks-to-improve-performance/

In closing. if this setup doesn't fit your criteria nothing will.

Have a great day.

windowsmgr.max_events_per_sec=240
[Samsung Galaxy Nexus] MultiCulti:
the idle drain is really nice ... but as soon as i use my GN ... the battery run's down :eek:

beamed in through my brain ...
[Samsung Galaxy Nexus] jameslfc5:
What's your screen on time?
[Samsung Galaxy Nexus] MultiCulti:
beamed in through my brain ...
[Samsung Galaxy Nexus] franciscofranco:
What would you expect, screen on, wifi and using apps there is no battery that handles that and doesn't waste battery ;)
[Samsung Galaxy Nexus] MultiCulti:
thaha ... franco ... wasn't a complain ... was more sarkasmus :thumbup:

listen Franco, are you thinking to include oc,uv and other stuff options in your kernel updater? ... would be a fu**** great thing :thumbup:

beamed in through my brain ...
[Samsung Galaxy Nexus] jameslfc5:
What's COLORS+ please? :)
[Samsung Galaxy Nexus] spidee:
First of all, thank you for your amazing work, this kernel is realy awesome.

Secondly, i have two quick questions. I have been using stock kernel before and there was GTA III working, now i have force close just after i open GTA III. I tried to uninstall, delete com.rockstar.gta3 directory, install it and download data again.

Have someone also this experience or it's only my problem?

And another question, have you plan to implement some patch or modification to enable NTFS for USB host?

Thank you for your response.
[Samsung Galaxy Nexus] eklipze:
Colors+ are tweaks implemented in this kernel to enhance the vibrancy of colors. Whites are more white, etc.
[Samsung Galaxy Nexus] ourakot:
bhi franco...

first i want to say that your kernel is just amazing.great battery live and great performance...but i would like to tell you the i have only one problem..so...

when i touch the screen to open application such as calendar calculatior etc the phone reacts instantly...but when i touch the screen to open the phone or the people or the messaging applications the phone opens them after 1-2 sec. i want to say i firsly touch the screen and after 1-2 sec i saw the open-animation...do you know why is this happening?or anybody else?any help is welcome.thank very much.Have a nice year.
[Samsung Galaxy Nexus] hosmsdos:
Delete the whole gta3 folder and download again
[Samsung Galaxy Nexus] franciscofranco:
Raise your minimum frequency to 700mhz.
[Samsung Galaxy Nexus] question.com:
Just purchased the kernel updater. So far so good. Had to support the Dev.
[Samsung Galaxy Nexus] ourakot:
nothing happens.the lag is still there especially with the message application...
[Samsung Galaxy Nexus] MultiCulti:
i would love to ... but my fu*** prepaid card ia empty ... will do it next week :thumbup:

franco, on the market screenshot ive seen nightly 8???? any surprise??? :D

beamed in through my brain ...
[Samsung Galaxy Nexus] do0b:
yup data connection was off.
[Samsung Galaxy Nexus] bat0nas:
Hah!!!!! :D

Nobody believed me when I posted this a month ago :P :P

http://xdaforums.com/showpost.php?p=25374628&postcount=13942

:)
[Samsung Galaxy Nexus] jeetS:
Spoke too soon. Was at 1536 and working great but after 15 mins of tower defence it froze for about 20 seconds then reboot... should I stay away from 1.5 or try again with r181?
[Samsung Galaxy Nexus] do0b:
we certainly showed them!
[Samsung Galaxy Nexus] splus:
I've been running 1536/384 CPU with stock 1400mV 1536 voltage, with on demand and interactive for last 24 hours, all kinds of use, from light to heavy stress, and no problem or reboot.

Battery seems quite good, same or just slightly worse than 1344 CPU I was running before, so I'm very happy with 180.

I'm wondering - have all who got reboots while running max 1536 CPU have been using wheatley governor?

Anyone got a reboot while using interactive or on demand?

Maybe there's some issue with wheatley governor and switching between 1536 and lower freqs?

I have an older GNex silicon, hardware revision 9 when looked in info in bootloader, which doesn't play well with higher overclocking compared to rev 10 phones, but everything still runs OK with 1536 CPU freq.

I tried Glados before, Ezekeel managed to make a 1600 CPU slot that is stable for every GNex (battery life aside, it wasn't that good for me, so I'm pleasantly surprised at a very good battery I'm getting with Franco 180 at 1536 CPU freq), so I know we can all go at least up to those speeds. Higher than that depends on a silicone in your GNex, it would work only on some phones.

Great work Franco!

If these niggles with higher CPU are solved then we'll have a killer kernel with both great speed and great battery life!
[Samsung Galaxy Nexus] nodstuff:
OK so using r181 with wheatley governor @ 729/1536mhz with stock voltages.

Up time so far is 1hr 30mins so no reboots.

Playing riptide, antutu benchmarks one after another, music and browsing and a little texting with google voice.

No problems so far, last night on r180 I would have had a reboot by now. Temperature is also down from last night, when I checked dmesg after playing riptide for a while I saw that I was throttled because the CPU hit 92C, tonight after the same amount of races, 5, I was also throttled but the temp was only 77C so I don't know what you did Francisco but it worked!!

Loving r181!

Thanks! :thumbup:
[Samsung Galaxy Nexus] dimgl:
franciscofranco: Storage tab under com.android.settings is currently broken when invoking statfs /mnt/usbdisk, causing a crash

http://pastebin.com/VZnCz9Mu

May have to do with USB mounting, will check on new nightly as soon as it is out
[Samsung Galaxy Nexus] nodstuff:
Pretty sure that's a CM9 problem.
[Samsung Galaxy Nexus] jnr21:
2 days of running r180@1,5ghz/weathley, no single issue. Battery life is about same as with r175@1,3ghz/interactive.

Just flashed r181...
[Samsung Galaxy Nexus] nikulogical:
is too many steps bad? for example, with using 1500, would 700min be better than 350min in terms of battery life?
[Samsung Galaxy Nexus] drawde40599:
Says cm9?? Last I read Franco said cm9 not supported think ur on ur own ....

---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------

700 uses more but not by much last time I tested over week time span ( 3 days 350 3 days 700) about 5% difference

---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------

Seriously?? Ur phones r charging by them selves? Its not just the icon messing up? There's actually usable power?
[Samsung Galaxy Nexus] nodstuff:
No its just the battery stats readjusting.

A phone charging itself would be on the front of every newspaper the world over, it would mean Francisco has solved the worlds energy needs and created energy out of nothing and this kernel would be worth more money than there is in the world.
[Samsung Galaxy Nexus] simms22:
i was just going to post the same. i kept reading and reading, and people kept believing that it magically charged itself. so i was going to let the truth out, but you got to it before me. thanks :)
[Samsung Galaxy Nexus] jnr21:
Sometomes after i flash new kernel (for example) battery indicator stucks for a while or increases few percents, i think it's normal.
[Samsung Galaxy Nexus] drawde40599:
they had me convinced o_O . OK no more drink for me tonight!!
[Samsung Galaxy Nexus] simms22:
sometimes, after flashing, the battery percentage is lower by more than expected. if you let the phone be, you can watch the level slowly rise, correcting itself.
[Samsung Galaxy Nexus] splus:
You can see that you had a pretty heavy usage just prior to the battery jump. It sometimes happens that after a very heavy usage the battery charge chip goes "ahead of itself" and shows a certain battery value, and then when you put the device to rest it slowly recovers (or recalibrates itself) and shows the more correct battery charge value. I think this is what happened.

You can often see that the battery value continues to go up even when the phone has been taken off the charger, after letting it charge for some time.
[Samsung Galaxy Nexus] morfic:
Also a strong drain/heavy usage will cause the voltage to drop far lower than it would be in resting.

You remove the heavy consumer and the battery voltage recovers.
[Samsung Galaxy Nexus] franciscofranco:
You just ruined the magical word of self-charging for everyone =(
[Samsung Galaxy Nexus] simms22:
how about a kernel that charges the phone through the bodies natural motions.. maybe ill ask ezekeel about that ;)
[Samsung Galaxy Nexus] giugiu:
... And Santa Claus doesn't exist as well. Sorry folks! ;-)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] nodstuff:
No need. Stick solar panels over our flash!
[Samsung Galaxy Nexus] Think420:
we've had devices that can generate energy out of "nothing" for quite a while...

the real problem is that it is more profitable to sell fossil fuels than for everyone to have free energy

just google "nikola tesla zero point energy"

(sorry I know I went off topic, but people should really know this stuff)
[Samsung Galaxy Nexus] schizophrenia:
OT: once you get self sustaining energy, you'll get assassinated.

back on topic:

running from when franco released 181 until now (3 hours?)

a lot of benchmarking using Nenamark2, Quadrant, Antutu and some Angrybird, Rmaps, etc etc

never had a reboot so far

on 1536 (stock voltage)/192 ondemand, AOKP b38

no comments on battery life yet though

anyone has UV successfully for 1536?

Magician franco..
[Samsung Galaxy Nexus] dimgl:
Removed.
[Samsung Galaxy Nexus] monkey hung:
Removed
[Samsung Galaxy Nexus] Diger36:
I had a reboot with on demand and 1536 yesterday. See a few pages back.
[Samsung Galaxy Nexus] 15israellai:
You're right, I forgot it's originally supposed to be 1.5.

I just remember overclocking my phone which then rebooted. Most probably I did a 1.65 and maybe I undervolted it. Stupid me in the past.

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] The Gingerbread Man:
181 won't boot up for me either, last night the very helpful rogersnm found me some links so can get adb set up on my PC (recently got a newer one) and then gave me a command or two to get this kmsg or what ever it is. Later today I'll attempt to get these logs and hopefully all of us can enjoy the latest and greatest from Franco's kitchen.

Sent with a shake
[Samsung Galaxy Nexus] marjaN_:
can't get running GTA 3 with AOKP b38 + franco 180, tryed 2-4 times (uninstall, download again data)...

anyone has solution? :)

Sent from SGN using XDA
[Samsung Galaxy Nexus] johno168:
I hardly played it so i unintsalled. Reinstalled from playstore then the data downloaded and it was fine.
[Samsung Galaxy Nexus] jnr21:
If you have sdcard binary that came with franco kernel, try original one (comes with aokp). Grap sdcard file from aokp cwm zip (found in /system/bin) and put it in your phone (/system/bin) and set permissions to rwxr-xr-x.

I'm not sure if this a right solution, can someone confirm it?
[Samsung Galaxy Nexus] zjmdp:
r181, 384/1536 stable for 5 hours， 1275mv for 1536mhz
[Samsung Galaxy Nexus] jnr21:
Does weathley using only min and max frquencies?
[Samsung Galaxy Nexus] nodstuff:
1275mv!!!! Daaammmmnnnnn!!!! That's some serious undervolting!!!
[Samsung Galaxy Nexus] schizophrenia:
tried to be just like you 1275mv and the second I clicked apply it rebooted.

showed no mercy to me

is that a trap?!? haaa
[Samsung Galaxy Nexus] jnr21:
I can't see the point...

You can already set screen-off-max-freq, why don't you want to allow cpu go under 729mhz when screen is on?