yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jhearrtot:
franco, this would be my first post on your thread.

i just flashed r290 with 512gpu and i gotta say this thing flies faster than M6!

thanks for your incredible kernel! i am hoping that you return back and continue with your kernel for galaxy note so my gf's phone would have the same awesomeness on her phone
[Samsung Galaxy Nexus] Wynnded:
Sadly it's their device(s) that suffer and die due to their lack of attention to the obvious.
[Samsung Galaxy Nexus] Cobra78:
I'm on Stock 4.1.2 with Milestone6, and form i is smoother and more battery friendly than stock kernel, teel wich settings you use.
[Samsung Galaxy Nexus] ChazzMatt:
Some people like me keep them enabled for tactile feedback. It's the only thing that keeps me sane with touchscreen typing. :) If it causes battery strain, so be it.
[Samsung Galaxy Nexus] IAmAN00bie:
#30000 GET. Oh and nice work Franco.

edit: FAIL
[Samsung Galaxy Nexus] franciscofranco:
Lol ****ing hell 30k posts... keep it coming :)
[Samsung Galaxy Nexus] willl03:
Franco whatever you did to memory somewhere between r276 and M6 / r290 dosnt work well, I get occasional launcher redraws and background apps are killed way too agressively i.e. my clock widget time gets stuck until I open the app, many times a day. Never had this problem in the past. When I apply the v6 supercharger I'm unable reach 100% anymore, the OOM values cant get applied, so i guess they are now fixed inside the kernel and too agressive.

Before you blame the supercharger, the same thing happens on a clean install w/o it. Tested

Thats unfortunate cause the smoothness and battery of M6 / r290 is awesome. Back to r276 and it's all good: no more occasional redraws and stuck widgets.
[Samsung Galaxy Nexus] TEK112:
Are you sure the ROM you are using isn't set to purge assests or the mem free minimum is too low?
[Samsung Galaxy Nexus] willl03:
I'm on CM10 nightlies, purge assets is off and running the exact same setup I get this problem on M6 / r290 and not on r276, using the v6 supercharger or not
[Samsung Galaxy Nexus] franciscofranco:
Try to decrease the minfree values, mine's might be too aggressive for your type of usage.
[Samsung Galaxy Nexus] TEK112:
I would avoid the supercharge script altogether. It was great with lesser phones, but it creates too much overhead for no real gain.

I agree with Franco, try adjusting the min mem free.
[Samsung Galaxy Nexus] creeve4:
What are the default minfree values for the stock kernel?
[Samsung Galaxy Nexus] franciscofranco:
Good question. Download Memory Manager from JRummy and try his presets until you find something that you like.
[Samsung Galaxy Nexus] shooter365:
Stock settings. Stock Android with stock Franco Kernel :eek:

Gesendet von meinem Stock Jelly Bean GN
[Samsung Galaxy Nexus] Tommebaas:
Thanks for the battery life.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Controvrsy046:
[/QUOTE]

What's your home screen setup? I like the wallpaper and what looks like a missed call widget on the bottom left?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thuynh022:
I'm kind of scared to flash 290. M6 is giving me incredible battery life.
[Samsung Galaxy Nexus] kyokeun1234:
Then don't.

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] jhericurls:
Loving you work Franco, any chance of a faster rotate version? Everything is so quick apart from the rotate :(
[Samsung Galaxy Nexus] beekay201:
jit enabled aosp+yaffs2

I would like to see that :)
[Samsung Galaxy Nexus] monkey hung:
Are you going to add the auto brightness patch in your next update?
[Samsung Galaxy Nexus] DebauchedSloth:
Would love to see benchmarks. Not sure it makes that much sense, since yaffs2 is designed for low-level nand flash and this device has emmc, which manages wear-leveling, bad blocks, etc. internally.

Would be particularly interesting to see multithreaded benchmarks, since we do have two cores here and I bet ext4 scales better.
[Samsung Galaxy Nexus] MontAlbert:
anyone else having this issue?
[Samsung Galaxy Nexus] DebauchedSloth:
Sounds to me as if you've lost root, for whatever reason.
[Samsung Galaxy Nexus] MontAlbert:
yeah i thought maybe that had done it but then i could access root apps no worries...
[Samsung Galaxy Nexus] bigxie:
The reason is because the kernel is not 'insecure', i.e. when you adb shell, it does not jump directly to root.
[Samsung Galaxy Nexus] MontAlbert:
I thought that may be the case but didnt see it mentioned anywhere...

Is there a chance of getting it "insecure" so we can use adb?
[Samsung Galaxy Nexus] Dmw017:
hey if we flash another kernel do we need to push back /system/lib/egl/libGlES_android.so or is it always beneficial to delete it no matter what kernel you're running?
[Samsung Galaxy Nexus] mrBira:
Hello guys! Im requesting a cwm flashable zip that will also delete that file. Or is this already in the thread and i missed it? Please add it to first post.
[Samsung Galaxy Nexus] The Gingerbread Man:
From OP Delete /system/lib/egl/libGlES_android.so and reboot. It's very important! be sure to back to it in case you want it later or keep a recovery back up before you try it. You need root explorer or file manager with root permission to do it
[Samsung Galaxy Nexus] The Gingerbread Man:
Dude its really not hard, even I can find and delete it or rename. All the knowledge you need is search market for root explorer, press mount rw, allow root, navigate to the file using the path shown and press delete or add .bak to the end. Then flash the kernal in cwm and boot.

The install script does not automaticly delete this file in case users want it backed up not deleted. Honestly man this really isnt hard.
[Samsung Galaxy Nexus] franciscofranco:
When I back home from univetsity I will add coolbho's uv interface to this kernel
[Samsung Galaxy Nexus] franciscofranco:
Update is up.
[Samsung Galaxy Nexus] rabhw:
I am one of the people that had the slowness/stuttering issue with a revision from 2 or 3 versions ago (1.4ghz issue), I see that even the latest kernel still ramps up to that frequency.

Has the stuttering been resolved? Or should people that have devices that stutter @ 1.4ghz just avoid this kernel for now?
[Samsung Galaxy Nexus] Shetlander:
Ive just flashed the latest kernel and now I have no network signal at all.

NEVER MIND - Rebooted the phone again and all seems to be working fine now.
[Samsung Galaxy Nexus] bigxie:
Francisco,

Will you consider creating a UV only kernel (i.e. max freq is 1.2GHz) with all the other changes intact?

I find that even though the 1.4GHz kernel supposedly boots at 1.2GHz, the boot animation is still laggy and the stuff doesn't smooth out until my SetCPU profile kicks in (much much later in the boot up process).
[Samsung Galaxy Nexus] franciscofranco:
Yes definitely, I'm considering that :)
[Samsung Galaxy Nexus] samizad:
Can I just remove or disable to Google Talk app and avoid having to start/stop the camera each time I reboot?
[Samsung Galaxy Nexus] daandman:
Ah fair enough, so turning it on is for better idle battery then? I don't understand lots of the stuff, so forgive my ignorance.
[Samsung Galaxy Nexus] fronc:
Can't find the app on the market (Axiom 2.3 has market incompatibility), and was hoping someone could help me enable hotplug manually. I tried the terminal instructions listed a few pages back, but got a "can't write" error. Someone want to give me a quick lesson on how to not be a hotplug n00b?

Thanks in advance!
[Samsung Galaxy Nexus] daandman:
You probably just need to change the folder to r/w in root explorer first. You can also just navigate to the folder, open the file with a text editor & change the 0 to a 1.
[Samsung Galaxy Nexus] chamonix:
That's the right one
[Samsung Galaxy Nexus] Redflea:
Running Widget Locker with 11 with no issues...maybe you just need to clear data on WL, and set it up again.
[Samsung Galaxy Nexus] Redflea:
Accidental.....
[Samsung Galaxy Nexus] atoyu:
I got no camera with this kernel in aokp build 15, anyone hv this problem?
[Samsung Galaxy Nexus] PeterGuru:
Screenshot Problem ...

Hello!

My Screenshot features does not seem to work. I'm using Nightly 11; however, I think I had the same problem with N10.

When I make the selection to take a screenshot, there's the appropriate sound, and then a note saying that the screenshot was taken and the file is saved. However, when I open the file, it's always BLACK.

Any ideas?

Peter
[Samsung Galaxy Nexus] ro_explorer:
Both issues must be rom related because I never encountered any of these and I'm using both the camera and the screen shot facility.
[Samsung Galaxy Nexus] PeterGuru:
Using AOKP Build 14

I'm using AOKP Build 14 ROM. Anyone else with these problems on this ROM? It's a very popular ROM.

Peter

Addendum: Solved! I have no idea what happened earlier when I tried the Screenshot feature and got BLACK images, but now it seems to work.
[Samsung Galaxy Nexus] s2d4:
no, its you.
[Samsung Galaxy Nexus] definator:
i am running on aokp14 wiht franco11 now. not a single problem with your issues
[Samsung Galaxy Nexus] FormelLMS:
If "read" the last 50 pages, but seems that I can't find it.

Thanks anyway. Hope that anyone can explain it again.

If not, ok....
[Samsung Galaxy Nexus] d-iivil:
Would have bought the app, but market says it's not compatible. Using latest Romanb's rom. Maybe you can extend your apps compability to 4.0.1 so users with roman's rom can also buy the app and support you?
[Samsung Galaxy Nexus] zurchpet:
IMO BatteryStats and Wakelocks have nothing todo with random reboots.

better to capture right after the reboot the /proc/last_kmsg with:

adb pull /proc/last_kmsg last_kmsg.txt

this pulls it to the current directory.

then get the last 300 lines and paste it to pastebin.com and provide the link to it here. Usually this file has more information on WHY the kernel rebooted.

Just my opinion. It is Francos thread so his rules apply.
[Samsung Galaxy Nexus] jknisley:
I was wondering that myself. I tried freezing Google Talk, but I'm still getting wakelocks for Google Talk communication listed in BetterBatteryStats. *le sigh*

---------- Post added at 01:55 AM ---------- Previous post was at 01:37 AM ----------

So we've been focusing mainly on performance and battery life, which are terrific, but there's been a bit of a pervasive bug in the GNex builds, and I'm not sure if it's kernel, ROM, or hardware, but since Franco here is so brilliant, and there's some chance that it might be the audio drivers... Well, I thought I'd ask.

When using a wired headset with this device, it echos. A lot. The person on the other side always thinks that they're on a crappy speakerphone. Sometimes, the headset can be unplugged and plugged back in and it improves, sometimes it improves over time (honestly, though, I'm not sure if it's just the other guy gets used to the sound of his own voice). It's fantastically annoying, and I'm wondering if maybe it's a problem with the kernel sound driver, or if I should be going over to the ROM thread and seeing if that guy can figure it out.

Bugrep is here: http://code.google.com/p/android/issues/detail?id=23482

Thanks for the look.
[Samsung Galaxy Nexus] kabauterman:
some feedback to Nightly #11:

Performance a lot better then #10

Idle Battery drain seems to be a lot better then anything I've compared so far
[Samsung Galaxy Nexus] ChongoDroid:
+1 so far so good. I got to it late so only time will tell about battery but I already notice an improvement in performance.
[Samsung Galaxy Nexus] MontAlbert:
not sure what is the cause but since installing this kernel tonight i have had 2 occurances of being unable to wake the phone.... had to do a battery pull and boot it up from there... i have hotplug enabled also... what is causing it? How do i find out? turned hotplug off to see if that was causing it.

I am using it on AOKP build 15.
[Samsung Galaxy Nexus] Kurre:
It would be kind to mention extended battery.. :rolleyes: because otherwise it'll just give users false expectations.. :) but anyway battery life with the latest version is great :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] wavedashdoc:
What apps do you use? Cause 6 hours, I've never heard of. Do you have everything disabled?
[Samsung Galaxy Nexus] J-Hop2o6:
Check Google Maps Location Tracking in its settings. Disable it if its enabled. Then watch the difference.
[Samsung Galaxy Nexus] jonstrong:
Also - assuming you're got BetterBatteryStats installed (or something comparable), as well as wake locks, look at partial wake locks and processes. Additionally: look at CPU activity: if you don't see a majority of the time (70% or more) spent in deep sleep, then something is definitely up and running when it shouldn't be (are you syncing various apps in the background? checking weather way too often? etc?)

The info should be there if you use some tools to take a look at what's going on...
[Samsung Galaxy Nexus] willl03:
Clock + toggles widgets is an old version of Widgetsoid

Phone widget is Last Call Widget

Calendar is Agenda Widget

The wallpaper is made using images + photoshop templates from a guy named nordpolecamper or something similar, he has a thread here in XDA with great wallpaper packs. I'll upload it when I arrive at home

GL
[Samsung Galaxy Nexus] loudaccord:
I never even noticed that it was on.... good call.
[Samsung Galaxy Nexus] RoscoeDpG:
ya after first few roms i stumbled on that setting and a day later my batt had few hours more of usage. Amazing how something like that can kill batt so fast
[Samsung Galaxy Nexus] jonstrong:
Does that have any impact when you're actively using an app that needs currently location in real time, e.g., Maps / Navigation? Or is this just updating your location in the background when Navigation is turned off? (in which case they probably use it for things like Google+ check ins, etc).
[Samsung Galaxy Nexus] superbobup:
No clue about tracking, but one big thing is setting "update my location" to manual rather than auto. This way it doesn't check you in to latitude automatically. If you like latitude/ auto-check ins, you should consider ALTitude as it offers better granularity on the latitude updates.

Another thing I noticed is manually killing (hold back to kill) Maps is the only way to end the process...otherwise it just keeps running even if you "back" out of it or swipe it away
[Samsung Galaxy Nexus] jonstrong:
I really don't care about latitude, being automatically checked in or offered a chance to check in when it recognizes my location.... if that's all that suffers, I can deal with losing this.

I'll have to try navigation with this turned off. If it works, this could turn out to be a nice tweak thanks.

Re: maps staying resident: I've watched the little GPS / location icon appear in my status bar when I open Maps, and after I back out of Maps the GPS icon disappears in about 1 or 2 seconds. Also - looking under Process in Better Battery Stats, I can see Maps, but it uses next to nothing when it's not actively open. It does take up about 8MB of working memory, but it doesn't seem to be chewing up CPU / battery.
[Samsung Galaxy Nexus] CaspaTheGhost:
What accounts are pushing or pulling?

I get too many emails coming through for it to be that quiet, but impressive indeed is r290!

View attachment 1409816

View attachment 1409820

Travesty, each and every time.

Sure it used to be referred to as signing into latitude, seems more obscure the way it is now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bigfnjoe96:
Anyone having an issue with their color profile resetting to Franco on reboots?

I have a personal profile I use, but when ever I reboot my phone the profile resets

Is this normal or is this ROM specific.

Thanks

Sent from my Galaxy Nexus running Milestone 6
[Samsung Galaxy Nexus] CaspaTheGhost:
Everything will work fine, its just logging out of latitude.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] superbobup:
Navigation works fine for me with "manual" location setting, location reporting disabled and location history enabled (works with it disabled though)

As for Maps running...I'm just concerned about the overhead when it tries to cache on WiFi and tries to keep track of location (I use network location 24/7) so I'm not sure about it chewing up CPU/battery since I always FC it
[Samsung Galaxy Nexus] J-Hop2o6:
I believe a recent Google Maps update had it enabled. I found out my battery life with screen off was draining higher than normal was because of Google Maps Latitude Location Update was enabled by default. SMH Google.

Nav will work just fine without it on. Its just to track where you traveled though out the day. Don't go to Process, go to Alarms in BBS, it will show Maps has high wakeups. When I turned off Latitude Auto Update my battery life was back to normal 1% per 1 or 2 hours instead of 2% per hour.

Yea thats weird it still works. Wonder whats the difference. And Maps will always be in the background for A-GPS. Its a network thing. So don't worry about overhead or it chewing up CPU/Battery. The only one thats a concern is GMaps Latitude Auto Updater enabled.
[Samsung Galaxy Nexus] Leegalaxy:
OT-

I would have to think that Google Now is affected by this. I personally love the cards popping up whenever I'm near a streetcar stop or when I'm traveling. Without GPS, I would imagine these cards will cease to populate based on location. If you are really interested in conserving battery, I would say this is the last thing to disable.
[Samsung Galaxy Nexus] jonstrong:
That would be a pity. Google Now is pretty cool, although it's actual value seems pretty limited so far. If turning off GPS tracking extends battery life significantly (1 hours? 2 hours?) though, that would probably be worth the trade off. Any experience with actual differences in battery life throughout a typical day? (I know everyone's experience will be different - just curious for relative / qualitative experiences).
[Samsung Galaxy Nexus] SIGUEL:
Amazing battery life. CNA 3.6.6/Franco M6

SKYNET
[Samsung Galaxy Nexus] thegtfusion:
I like r290 very much. Awesome battery life. But 1 problem!! Running interactive with deadline at max 1228mhz. But the phone is getting really really hot during the charge. (I mean it literally stops charging becauss its too hot, and still plugged in. If i type *#*#4636*#*# and go to battery, then the battery status is defined at : overheat, not charging.) This does not happen on trinity. Same settings. Weird..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] superbobup:
Location setting = updating where you are to the Latitude service so, for example, friends can see you

Location History = keeping a log of where you allowed your location to be viewed, for example where you check in or where you updated your location

neither of these should affect navigation as it's just saving/updating data but doesn't do anything to routing

Maps shouldn't always be in the background for AGPS services, because mobile network location should be handled by a separate service under Google Service (I think). If it needed Maps to utilize coarse location, uninstalling Maps should break this functionality which I don't think it does :D

So for some reason Maps wants to keep track of my location in the BG when navigation/maps process isn't active, which I think should cause some substantial overhead.

Franco, sorry for bringing up this off-topic discussion, hope you don't mind much :o:)

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

Google Now uses WiFi/mobile, not GPS :)

And even then, only certain cards use it. If you only use the sports card, the only thing it should automatically update is the score which is probably just a web search :D
[Samsung Galaxy Nexus] marcocsh:
I use minco v4 and I have the same problem!
[Samsung Galaxy Nexus] Leegalaxy:
Guys? I'm running r290 on stock 4.1.1. How the hell did this happen???
[Samsung Galaxy Nexus] thegtfusion:
You will get the prompts and etc. In will also download. But in recovery, when jt is supposed to install, it will fail.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Leegalaxy:
Just curious. Do you speak from experience?
[Samsung Galaxy Nexus] joaquinf:
Same thing happened on a friend's Gnex running ARHD. However, as stated above the installation failed to install on recovery (i wasn't expecting it to install succesfulyl, though. I was just curious)
[Samsung Galaxy Nexus] EVERED78:
which 1 do i use with 4.1.2
[Samsung Galaxy Nexus] kyokeun1234:
Both milestone and latest nightly works with it

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] joaquinf:
See?? that's why i was looking forward to your thoughts about this :cyclops:. Thanks for the detailed answer and the details about the update script from the kernel flashable zip files
[Samsung Galaxy Nexus] marcocsh:
Guys,

Is the mipi_link wakelock kernel related? How can I get rid of it?
[Samsung Galaxy Nexus] thuynh022:
I like to live on the edge. I already flashed 290
[Samsung Galaxy Nexus] shreddintyres:
its app related as i understand it from the betterbatterystats page its related to the camera, and apps that require the camera, for some reason gtalk seems to contribute to it

atleast thats what i understand from reading the page, some one more educated in the matter could likely give a better explanation
[Samsung Galaxy Nexus] superbobup:
I think it's camera related. I think we had the issue way back at the beginning of ICS of opening/closing camera because gtalk would want it for video chatting. Maybe try that
[Samsung Galaxy Nexus] marcocsh:
Ya I saw some said it maybe related to gtalk and google+ but I don't have them. I also heard a workaround of running the camera app after boot and then closing it using the back button. I tried but the wakelock is still there. So I don't know what else I can do.:eek:
[Samsung Galaxy Nexus] wallendiaz:
Hi guys, I would like to know if someone can tell me the difference between the governors of franco kernel, because I don't know the difference. :confused::confused:
[Samsung Galaxy Nexus] EDNYLaw:
http://xdaforums.com/showthread.php?p=19846276

And dyninteractive is interactive that dynamically adjusts its settings on its own.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] joaquinf:
Hi!

Read this

EDIT: oops .. too slow, i'd better go back practising Z-Type :p (nice lil game from my HTC Sensation old days)

Bookmarked! thanks for that awesome link
[Samsung Galaxy Nexus] josip-k:
R283,the kernel with the greatest battery life ever. :)
[Samsung Galaxy Nexus] AutomaticFailure27:
Anyone else having severe deep sleep battery drain with m6 / r290. I'm running CNA 3.6.6 and have very limited awake time. It usually happens when on wifi and in about 7 hours I lose ~ 25 - 30% battery easily. Looking at everything from CPUspy to BetterBatteryStats to Autostarts... I can't figure out anything. I have switched back to r284 and everything seems fine. So confused :confused:
[Samsung Galaxy Nexus] osm0sis:
Not sure why r284 would seem to help unless it's just the reboot. In 9 hours last night when I was asleep my phone drained 0.4%/hr with r290. So there's got to be something going on at your end.. try some of the stuff from my recently published book. Should help. ;):laugh:
[Samsung Galaxy Nexus] AutomaticFailure27:
Yeah, that sure is some book :laugh:

I have Tasker set to turn off autosync during midnight and 8am, Gmail push notifications (like a whole 3 emails over night) Friendcaster, Tweedle, G+, and any other application, have no push notifications nor timed syncs. The first flash of m6 gave me over a day of battery easily, but since that initial day, it has just been killing. I tried reboot after reboot, even flashing to r290.... nothing. I started to think it was CNA since they haven't updated to the new 4.1.2 stuff...

I'll give it another shot just for s***s and giggles.