yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Schneewitzchen:
Hello Franco first of all, this kernel is really awesome. I'm using it since nightly 23x.

Recently i get the mentioned "sdwatch error 4" error in logcat. I want to say that i was testing a little bit before i wanted to post this error.

I'm on Mincov4 now, but this happend also in stock jb with the latest nightlies! The error occurs only when the screen is off, if the screen is on and i'm doing stuff on the phone the error never showed up.

When i do a factory reset and flash Mincov4 again, the error doesn't occur at all. (Clean Mincov4, only catlog and your app installed).

So i'm flashing the latest nightly and bang the error showed up again. (Clean Mincov4, only catlog and your app installed)

So i thought ok then lets go back to milestone5 and the error should be gone, but fairly it wasn't. (I'm flashing all kernels through recovery)

I don't know whats wrong and the error isn't mentioned from any other one who is running the latest nightlies.

I attach two logcat, the first one was saved shortly after booting up, the second one lasted a little longer!
[Samsung Galaxy Nexus] djjonastybe:
Franco, adjusting OMAP GAMMA is resulting in SYNC_LOST.

In your changelog you fixed a SYNC_LOST with nightly r165.

Now I have 2 questions:

- Can you replicate the same problem with your latest nightly?

- Is there a fix for this?

I am using the latest CyanogenMod 10 nightly.
[Samsung Galaxy Nexus] schizophrenia:
I always get pages of this error "sdwatch error 4" and dont know how to fix it.

no one seems to have a clue how to fix it too
[Samsung Galaxy Nexus] Schneewitzchen:
I've found a new hint on this...when i put the usb cable in my pc the error doesn't show up. But on charger the error shows up immediately.

I think it's Kernel related because on a fesh installation with milestone 5 the error doesn't occur.
[Samsung Galaxy Nexus] PakaPakaxz:
Battery life is awesome !!!

Thanks, great kernel !:good:
[Samsung Galaxy Nexus] aleve1983:
I have problem with new low memory killer driver, after much time that i use phone (many app) my ram free is 80 mb and phone lag

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] kyokeun1234:
Franco, I got a awesome news! My battery life improved dramatically after 283r! Never EVER in my life I had more than 3:30 of screen time, but with 283r, I did! Never did my full test with 282 and 281, but I'm pretty sure they were awesome too :)
[Samsung Galaxy Nexus] lippol94:
100% Stock values?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kyokeun1234:
Always for few days to test out what Franco had given us :) I also put mine in 1.2GHz. No overclock nor underclock.
[Samsung Galaxy Nexus] osm0sis:
Oh believe me, I understand how annoying it is seeing the same things posted over and over again in this thread. ;)

Fact is the lag is slight, I'm happy to admit that, and it's not a deal breaker by any means, but it certainly has to be useful troubleshooting/code optimization/bug hunting information when a recent build like r276/7 continues to feel more responsive and fluid by comparison, especially when lmk was using lower values on those builds.

Oh and I don't use the xda app, I'm talking about the UI in general, mostly the app drawer being a little slow to get started scrolling, paging through widgets chokes more, homescreens feeling slower to switch and the hiccup in Settings when you scroll down fast after a fresh boot and it hits the accounts section being more noticeable.
[Samsung Galaxy Nexus] boki2911:
I always go back to r276 because for me he was the best yet
[Samsung Galaxy Nexus] xpking:
I used the nightly builds more than a month.

I have the below issues when my nexus upgrade to r283 from r282 now (386 GPU)..

1. the battery drains faster

2. I choose interactive in govenor, but after phone reboot, it will change to ondemand again...

any ideas how to resolve this?
[Samsung Galaxy Nexus] Kurre:
Try this in terminal:

busybox sync

echo 3 > /proc/sys/vm/drop_caches

echo 1 > /proc/sys/vm/drop_caches

And report if it helps (it does for me, although I haven't suffered that low account of ram..)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] shawnaye:
Haha I'm sure you understand what I mean. I was just ranting. Because I know it'll still definitely occur.

If the app drawer is lagging? Could it be due to apex or nova? Unless you're using stock, but stock isn't perfect as well right?

I'm just trying to wonder what more can Franco do with regards to these micro-stutters.

Can't really ever remember using a stock kernel.

But oh well. I guess no one will truly ever be satisfied with the software they are provided with.
[Samsung Galaxy Nexus] osm0sis:
Stock launcher, yes, and no of course it's not perfect, but little to no lag on r277 vs. lag on r283 is something you take note of. And since there aren't that many commits in between, it might help somewhat narrow down what if anything changed that could be brought forward to improve new builds. I'm very satisified with franco's work, he is a genius, I'm just trying to do my part to provide hopefully useful feedback to make sure the kernel can be the best it can be; this is a development forum, after all. ;)
[Samsung Galaxy Nexus] ChazzMatt:
r276 was very good... I notice a lot of people either going back to 276 or comparing the latest nightly to 276.

So, how about this? Declare r276 to be "Milestone 6", and then go on from there? People who want the most stable milestone would then have something they can load -- better and newer than Milestone 5.

People who want to flash nightlies for development can continue to do so, but r276 would be the new baseline?

I know we're already on r283, but that just means we're now a few steps towards Milestone 7! :D
[Samsung Galaxy Nexus] Schneewitzchen:
@ schizophrenia

I tested arround with some of franco's builds. It seems like when you install the build through recovery you'll get this error.

I installed the latest nightly on factory resetted mincov4 through autoflash on franco's app and the error doesn't show up.

@ franco

are the procedures of installing the kernel through the app and cwm different? What i recognized is that there is no dalvik wipe when doing autoflash through the app.
[Samsung Galaxy Nexus] osm0sis:
Ahh.. everyone with the sdwatch error try using the sdcard fix from the OP (under FAQ) and see if that helps. Good eye Schneewitzchen. The stock sdcard binary is only replaced when franco.Kernel is flashed from the recovery flashable zip. Also no cache wipe whatsoever (dalvik or system cache) is necessary for a kernel flash.
[Samsung Galaxy Nexus] dannejanne:
Can sound quality differ from kernel to kernel?

Tapatalked
[Samsung Galaxy Nexus] SUTHRNFRIED:
Although others have reported issues with it r277 has been what finally dragged me away from r241 in terms of stability and battery performance. Putting 283 through its paces today to see how it does. But if I'm not a fan then back to 277 for me. To your point though I do agree. But we all know Franco is a bit ocd and will not release a milestone until he feels that its perfect. I really do like that about his development. :)
[Samsung Galaxy Nexus] Hanny:
Hi franco, just updated from r281 to r283

what happened was:

downloaded 512 gpu zip from app

flash in recovery

reboot system

it just booted fine and screen turned off, i left it there for a while

i turn on the screen normally and unlock

after a second it goes to the bootanimation and boot again

then no problem so far

which is pretty much the same behavior i have seen a user reported few pages ago...

512gpu and 1420dyninteractive was perfectly stable for me and they were set on boot

last_kmsg attached so hope it helps :)

btw, r283 is definitely smoother than 281 lol, and im really sure it is brought by the LMK fix.

on the other hand r281 has made me think of wtf is wasting my ram and making my phone slow then i uninstalled LINE for smoother sake...

thanks franco for inspiring me to uninstall a memory hungry app which is mostly unused XD

EDIT: wait.... my eyes are fine right? :eek: :eek: i saw "Turn Off Logger" option before making this post and it is gone after i post?

same r283 same updater app version!
[Samsung Galaxy Nexus] RayGarden:
Just wanna to let you know that i wiped a nr of apps which i've installed using #282.

I went trying Go Launcher (and all of it's themes etc.) + a new app called "Pops" = Notifications Themes. I think one of these were causing these major lags.

After wiping those apps, cleaning the caches, i could not ignore #283 :p

I have to admit.....#283 is running Great (both performance + battery).

This result of my comment is that; Comparing different Kernels, while people using all kind of different apps and facing problems, is not that obvious.

Love your work :good:
[Samsung Galaxy Nexus] Schneewitzchen:
Could you point me to the sdcard fix i don't know where to find...pn?
[Samsung Galaxy Nexus] Hanny:
here :)

edit: lol link ****ed up because of copy and paste... this one's correct http://xdaforums.com/showpost.php?p=27515966&postcount=20011
[Samsung Galaxy Nexus] Rimher:
Right now on r283. I have to say it's pretty smooth, but 282 was a tad smoother(Plume scrolling has suffered occasional stutters).

Battery life today was pretty bad(first day after flashing, might take a couple of days to kick in): 11h with 1h 38m of screen on time and currently at 30%.

Using interactive governor with 384-1228 frequency and bfq scheduler; ROM is latest Xenon HD

Also today I lost my google connectivity on data (icons were grey instead of blue), and had to reboot to get it again.
[Samsung Galaxy Nexus] Schneewitzchen:
Oh ****, thats to easy :)

I will test on a nandroid backup and report back!
[Samsung Galaxy Nexus] nuwan32:
For losing connection to Google services just try turning airplane mode on and off
[Samsung Galaxy Nexus] sleepsus:
franciscofranco, I suggest you come up with a standard test suite to prove/burn in/soak your kernels. These subjective, eyeball observations are ridiculous as you have proven yourself with your no changelog experiments.
[Samsung Galaxy Nexus] Rimher:
I did try that =) Didn't work though; tried switching mobile data altogether off and back on again, but no results. The only choice was a reboot
[Samsung Galaxy Nexus] yellowdie:
He has people who do the original testing (like minooch), then he puts them up for everyone to test. Feedback from across the board is just as valuable because not everyone uses the same stock setup, so you want to test it in a variety of environments. Don't worry yourself, Boss Man knows what he's doing. :cowboy:
[Samsung Galaxy Nexus] Schneewitzchen:
Thanks guys! After applying the sdcard fix the error is gone!

@ schizophrenia

Try this fix!
[Samsung Galaxy Nexus] osm0sis:
Glad to help! :) Not sure why franco still includes that sdcard binary in the zip.. seems to cause more problems than it fixes. I always remove it from my local copies of the zips.
[Samsung Galaxy Nexus] nswenson:
Franco Kernel Updater - RGB Gamma settings won't stick

I appreciate all the hard work that has gone into the kernels and supporting app. With the last JB kernel, #283 combined with the latest linaro CM10 build I have near flawless performance. The only issue I'm having is with the Updater App RGB Gamma settings retention. My preference is for 0, 0, 0 RGB Gamma, but with each reboot it goes back to some default value with -4, 0, -5, or something similar.
[Samsung Galaxy Nexus] RayGarden:
Screencast App not working on Tegra 3 Device (like Gnex)

@franciscofranco

---->>>>> off-topic

Hi Francisco,

I just read a comment from someone who was explaining why anyone is capable to make "Screencast" work on a Tegra 2/3 Devices (like Gnex).

Now in this comment (see below), the person was referring to the Kernel. As you are the Kernel Whizkid here, maybe you understand the problem and maybe can solve this? Or you acknowledge the problem and confirm that there is no way to find a solution here.

**********************************************************************************************************************************************************************

The OMAP4 has built in hardware DRM which makes the framebuffer inaccessible from software running in user space. The challenge to fix

Screencast for the GNex means breaking the hardware protection on the framebuffer (read: very difficult). We even hired OMAP consultants and

they all threw their hands up in the air. Without HEAVY kernel modifications, Screencasting on the GNex is impossible.

**********************************************************************************************************************************************************************

Never asked, Allways missed. So maybe you have a challenge?

Thanks
[Samsung Galaxy Nexus] yellowdie:
Umm...Gnexs don't have Tegra 3s... :rolleyes:
[Samsung Galaxy Nexus] viscocesco:
Google relased 4.2 version!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] dyepnoodle:
Nexus 7 is getting Android 4.1.2 now. its being rolled out as of this time.

http://www.androidpolice.com/2012/1...id-4-1-2-update-being-released-to-aosp-today/
[Samsung Galaxy Nexus] Insunity:
Do you mean 4.1.2?
[Samsung Galaxy Nexus] Rimher:
Yeah, I think that's what he meant ;)
[Samsung Galaxy Nexus] viscocesco:
Yes sorry 4.1.2 is the new version released.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] SUTHRNFRIED:
So I've read a handful of folks experiencing excessive batt drain with 283. You can put me on that list as well. I've changed nothing about how I use my phone and im at 54% in just 7 hrs. I've gone as far as adjusting my interactive setting to 729 hispeed freq with no positive results. I'll give it one more cycle and another full day tomorrow to see the results. But I've got a feeling I may be restoring my 277.
[Samsung Galaxy Nexus] danba:
Apparently, a DIY USB DAC is working with a Galaxy Nexus running on your kernel & AOKP and AlsaMixer available on Google Play Store.

http://translate.google.fr/translat...12/10/androidgalaxys3usb-dac-galaxynexus.html

http://devlog.grim3lt.org/2012/10/androidgalaxys3usb-dac-galaxynexus.html

However the sound is choppy.

The AlsaMixer is likely set up to 48kHz, and his music got ripped at 44.1.

The immediate solution should be to re-rip the music at 48.

The long-term solution should be to find a way to set up the AlsaMixer to 44.1kHz.

This DIY USB DAC is also working with a stock Galaxy S III.
[Samsung Galaxy Nexus] Fenvarien:
I made a quite good experience with battery life and r283! I used my phone with the new kernel very intense today, browser, mails, PDFs, music and some gaming. 80% WiFi, 20 mobile data and autobrightness. (230/1305; Interactive Gov. @ stock settings)

Good performance and great battery life, thank you Franco for this fine kernel release :)

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] nuwan32:
its weird that its been the opposite for me. 283 seems to have gotten rid of all my drains. maybe try restarting ur phone if u havent already?
[Samsung Galaxy Nexus] bradm23:
+1 on the drains with 283. Seems in use the phone just dive dombs worst than previous builds. Got 1 hour screen time with 283, vs 3 hours with 282. All setting the same, I do not mess with controls in app.
[Samsung Galaxy Nexus] yellowdie:
I am on r283(384) and I just played a 3D game at 100% brightness for 75 minutes and it drained by battery about 40%. That's freakin' impressive. That means if I played a game and ran the full charge, I could get probably 3 hours at 100% brightness. That's crazy awesome. Just sayin'...

:):D:laugh::good:
[Samsung Galaxy Nexus] Empty Hand:
WTF is wrong with my phone. I'm at 2 hours of screen time, 6 hours total and have 8% battery left - and this is a good cycle for me. I get similar results with different roms, including MiNCO and AOKP. I always run Franco Kernel (currently r283 and trying wheatley since others said it's better for battery life). The only app I run that should be using battery is Exchange set to push notifications. How do you all get close to or more than a full day?!?
[Samsung Galaxy Nexus] nuwan32:
Don't have a **** load of apps running in the background or widgets and turn airplane mode on when you have no signal
[Samsung Galaxy Nexus] cmoG530:
Everyone's device is different. It's tedious, but it pays to test all and give them all two-three days. For my device, Trinity is the only kernel that gives me the best battery life and I have it clocked to 1300.

×*Don't Stress Too Much Over Android. Just Get A Device That You Like & Make Sure That It Has Good Development*×
[Samsung Galaxy Nexus] TEK112:
You and me both. However, I attribute a lot of my issues to being in a poor service area most of the day.
[Samsung Galaxy Nexus] Bram77:
283 seems very good. Both performance and battery wise.
[Samsung Galaxy Nexus] CADude:
I'm interested in seeing what Franco does with the new kernel in 4.1.2.
[Samsung Galaxy Nexus] The Gingerbread Man:
I expect its infact role reversal time, Google catch up to Francos level of speed ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
We already have 4.1.2 Tuna kernel changes in here for a long time, its just two commits as far as I could see from the detailed changelog.
[Samsung Galaxy Nexus] franciscofranco:
My GN is at 58% left with 2h screen on time, auto-brightness and all stock settings that I release this kernel with. Don't know whats wrong with your device, but mine's great.
[Samsung Galaxy Nexus] sk8oldschool74:
I'm testing this comment.... :D
[Samsung Galaxy Nexus] gaich:
4.1.2 changelog
[Samsung Galaxy Nexus] IgnorantNerd:
Ok I'm going try this again with your settings. I gave up on R283 but I'm gonna give it another shot and give it a longer testing period. Hopefully it goes better than last time
[Samsung Galaxy Nexus] nuwan32:
You need to go through 1 or 2 battery cycles before the kernel actually sets in, or that's how it feels like
[Samsung Galaxy Nexus] jeetS:
Franco, once again great kernel. This is the nicest of the past few weeks and great battery life as always!

keep up the good work
[Samsung Galaxy Nexus] twilightrevenant:
Takes up too much space to post it here, but mV from battery widget is fine here. While I set it to 5min reporting, it only changed every forty minute or so. I don't know what you mean by bounce by if you mean that it goes up sometimes, the occassiknally, yes. I don't think its related to this kernel as I've seen this before in other builds. If you read the calibration thread, you'll see that these data are not very reliable.
[Samsung Galaxy Nexus] jknisley:
Replying to myself, it looks good with locaiton services off. It looks like if I run maps, then get out of maps and turn off the device, it doesn't register the "Where the hell am I?" wakelocks. So even with map itself running (but not foreground), and the LS tick turned off, it seems that battery life is significantly more conserved.

So tomorrow, a test with LTE on to see what my battery life is. I don't need to be one of those freaks that goes for 2 days between charges, but lasting a whole day would be nice, and this shows promise. Coincidentally, this is what I meant on this (and another) thread about how battery life discussions aren't meaningless. This is a big thing that's endemic to all of the ICS builds. Also, just saying that Google Maps is a battery vampire doesn't exactly mean "Turn off location services; it'll help a lot." Maybe I should just start a battery life forum discussion on my findings thus far and how Franco's kernel has been such a big help in performance, stability, and battery life in addition to this. And certainly, hearing the very clear suggestions from someone as knowledgeable as the kernel developers could only add to the helpfulness.

Sorry that this is a bit off topic, but I thought it might help all the other VZW people running around, testing this kernel, trying to figure out why they have an enormous battery drain. This is a *fantastic* kernel, and I don't think that the drain from the LTE or GMap's constant updating should be held against it, so I want them to have a fair test of it.

BTW, the above was in no way a dig on Franco. I love this kernel. It's the fastest my phone ever ran, and it was definitely getting better than stock battery life, even with the enormous drain I was seeing. Just glad that my phone is a viable tool for me, at this point.

I'm definitely looking forward to the future builds and all of the improvements that they'll bring.
[Samsung Galaxy Nexus] zurchpet:
Just had a unwanted reboot

Minding my business I just saw my Galaxy Nexus reboot.

I captured /proc/last_kmsg for you to inspect @ http://pastebin.com/0YRMMCXX
[Samsung Galaxy Nexus] Thracks:
I think people are genuinely on to something with disabled location services. My battery consumption has been low, as I've said in other posts, but it has frequently spiked into the 70-110mA/5min range for long periods of time with no obvious culprit: CPU spy shows extended periods of deep sleep, BetterBatteryStats shows no runaway processes, yet Battery Monitor Widget shows a consistently increased drain.

So on a lark I disabled Google maps (thank you, ICS) and disabled all location services. Wouldn't you know that I'm locked at 2mA/5min in sleep.

The genuinely unfortunate thing about all of this is that I don't believe it's an issue the mighty Franco is responsible for fixing. :(
[Samsung Galaxy Nexus] chamonix:
Sorry for the OT.

LocationManagerService is a little bit more complicated: an app registers a listener and can define what precision it wants and how often it wants to be notified. Androids LocationService then 'informs' the listeners based on the requirements they have set.

Typical Listeners would be maps itself, latitude, g+, gplaces, weather widgets

Within maps latitude is a known drainer because of its poor design when it comes to energy footprint, maps has a few settings about caching that impact the drain too (there have been changes / fixes since lately)

My advises when it comes to maps:

- clear cache/data

- check cache settings to be only wifi

- do not use Latitude as a location updater. If you use Latitude at all set it to manual and use a 3rd party updater

- never leave gps location provider on

With those settings and a 3rd party updater the drain coming from location services can be neglected on both my sgs2 and my gn
[Samsung Galaxy Nexus] sishgupta:
Hmm. Disappointing.

I really enjoy the location services feature of the phone.

I'm somewhere in between my battery life is good enough with it on and being willing to toggle it on/off when I need it.
[Samsung Galaxy Nexus] tristan202:
Brilliant kernel. Any chance you could build cifs as a module, so the ones of us needing it can add it ourselves?
[Samsung Galaxy Nexus] franciscofranco:
Aye. More news later today on the kernel/app.
[Samsung Galaxy Nexus] MSgtSimon:
Francisco, nice job man. Running the nightly #10 on TeamKangs AOKP build 14. Doing about 1% per hour with your default settings. As they say: Epic Win.
[Samsung Galaxy Nexus] nic85:
flashed in foxhound 0.3 rom..perfect :D
[Samsung Galaxy Nexus] Elganja:
i feel like i am going crazy... but idle time of course is just amazing, no other kernel comes close to it...

but I feel like actual usage time (web browsing, etc...) the battery drops quick (almost 1% every 2 minutes).

Is that about average? I can't honestly remember with Apex 5 kernel that I was using before, but I don't think it was falling this fast...
[Samsung Galaxy Nexus] definator:
dont know any others, but for me its the same, even with about 10% screen bright
[Samsung Galaxy Nexus] Elganja:
k, that is fine, I just want to make sure I wasn't going crazy and other people saw the same
[Samsung Galaxy Nexus] mfish123:
Attached are some battery monitor widget screen shots. Hope these help.
[Samsung Galaxy Nexus] definator:
it is not a real problem for me, coz most of the time my phone is in deep sleep. but for users that more often use their phone it can be annoying :)

only things i am doing with this phone is phoning and whatsapp... sometimes surfing... but thats all

camera shooting i like too ;)

if i just stay overnight with wlan on, i use up to 2-3% for 8 hrs