yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Ashtrix:
Experience & Suggestion on the v11 ZEN

-v11 The Prodigy X

4.2.1

XXLA2

CM 10.1 Kang -Jellybro by Euroskank

-No, SoD's for now

-Governor options plus new governor patches make it more battery efficient on 3G, also paired with a bunch of i/o options adds more features :good:,

-Only issue was , the phone lagged for a millisec on gallery app (1700 pics) .

-need more performance and smooothness :cool:
[Samsung Galaxy Nexus] kinfolk248:
dont worry, it'll drop....it'll drop..!
[Samsung Galaxy Nexus] bbedward:
Hey guys, thanks for your support.

I believe there are issues, perhaps voltage/SR related, with 192/230MHz frequencies causing sporadic reboots for some people. Looking into that, if you're having issues revert to 384, if not keep on rolling ;)

If you get odd behavior please try to shoot over a log, if you get a reboot try to send over /proc/last_kmsg .

One thing I want to address otherwise, having more cpufreq/IO governors built in to the kernel does not hinder stability or performance.

There is little-none negligible overhead from including them, so I think its best to give the users as many choices as possible ;)
[Samsung Galaxy Nexus] purian23:
Thank you bbedward, this ^^^ is our ZenSERIES Kernel Developer from Android Developer Alliance. This might be a good heads up to some of our users.! As he said, if you are able to pull logs, the one he posted above should help us greatly.!

Purian23
[Samsung Galaxy Nexus] minieod:
I'd love to are the inclusion of pegasusq and vr i/o added ... always had great results with that combo

Love the kernel
[Samsung Galaxy Nexus] crixley:
best combo of smoothness and battery life ive encountered yet. Ill be sticking to this one
[Samsung Galaxy Nexus] WoodroweBones:
I had some odd issues while running this Kernel. Initially it worked great and then a day later I tried to go to facebook in my chrome browser and the phone sort of froze up. It didnt reboot or anything but it was completely unresponsive for a while and would take a very very long time to react to any input (i.e. lets say I was typing "hello"... I would hit the H and would have to wait a while then hit the E and wait a while, etc. Eventually it would say the process has stopped responding and I could force close it and things would work again. After the first time I rebooted the phone and it booted up normally and went back about my business. It happened again shortly after (this time I was going to take a Picture and after hitting "Camera" the camera app came up but the screen was black and it became unresponsive in the same way it did the first time. At this point I rebooted into recover and wiped Cache/Dalvik and let it load up again. It didnt take long after and the same thing happened (again when opening the chrome browser). At this point I simply went back to Franco's kernel and havent had the issue since. Not sure why it happened but for the first day or so it ran great and battery life seemed really good. Not sure if I can log anything when its not responding or anything but let me know and I'll give it a shot if you think there is something I can do to help
[Samsung Galaxy Nexus] jjhiza:
Well, you mentioned wiping after you experienced problems, but did you wipe before flashing Zen? I had similar lag-related issues during testing, after dirty flashing over Trinity. It took a cache and dalvik wipe, a flash back to Trinity, and a repeat of that process with Zen, in order for things to clear up.

Like anything, a clean wipe when going to another "brand" of ROM or kernel, is a must... Otherwise you run the risk of having some kind of crossover and corruption. If you want to give Zen another try, do a clean (dalvik and cache) install first. Afterwards, you can dirty flash from one version of Zen to the next, without problems. :)
[Samsung Galaxy Nexus] WoodroweBones:
Ah ok. I thought that doing a dirty flash but then wiping cache/dalvik afterwards would essentially "clean" the install. I will definitely try that process and give the kernel another shot. I love what this dev group is doing
[Samsung Galaxy Nexus] jjhiza:
They're absolutely outstanding... No doubt about it! Between the ROM and the kernel, I'm loving the experience, and have been for quite some time. :)
[Samsung Galaxy Nexus] burntkookie:
Will this work for sprint gnex?
[Samsung Galaxy Nexus] hoesers:
Sure will, kernels are interchangeable :thumbup:
[Samsung Galaxy Nexus] purian23:
Thank you all for the wonderful feedback! We have posted in all Galaxy Nexus forums to redirect the main traffic back here for support since this is a unified kernel for all. Be on the lookout for some nice updates to come based on our current feedback :)
[Samsung Galaxy Nexus] ak:
Good work guy!
[Samsung Galaxy Nexus] WoodroweBones:
Just an update... I flashed back to this kernel (booted into Recovery then wiped cache/dalvik and flashed). By default it was on Interactive governor (thought default was supposed to be interactivex) and I actually saw almost the same issue but much less exaggerated. It would still "freeze" but not for very long. Since switching to interactivex it seems to be much better as well

---------- Post added at 11:06 AM ---------- Previous post was at 10:07 AM ----------

I have a request... one thing I have noticed with pretty much every kernel out there is that if the phone sits unused for a while it will drop Wi-Fi data (I set my Wi-Fi to be always on). What I mean by this is that its still technically connected to the Wi-Fi but no data will get through (the Wi-Fi icon will be grey when you turn the screen on as well). I have tried many different things with varying results but one thing that seems to help is to set the min CPU speed to 729. If the Min is at 384 it happens much more often.

The reason its annoying for me is that I use my phone for work email so if my phone is in my pocket or sitting beside me while I'm doing something else I wont get any email/messages until I turn my screen back on. And once I do turn my screen back on the phone very quickly starts getting data and i get flooded with messages/emails

Hopefully that explains it properly. If not let me know
[Samsung Galaxy Nexus] gm007:
Maybe you should enable wifi high performance
[Samsung Galaxy Nexus] WoodroweBones:
I am also very battery conscious so not sure what effect that might have
[Samsung Galaxy Nexus] chasew83:
anybody using on toroplus? is it working ok?
[Samsung Galaxy Nexus] WoodroweBones:
I installed Trickster Mod and that option was already on. I assume the app wouldnt turn things on and just read what is set already so it looks to me like on this kernel high performance wi-fi is already on?
[Samsung Galaxy Nexus] purian23:
Yes this is the option I would choose as well. This is more of you app controller choice vs kernel related. The kernel just supports it so you have a nice choice of options.

Yes I wouls assume it would consume a little more battery if you're always pulling signal, but it should also solve you problems. Might not even being enough to notice ;)

Perfectly well.!! Our kernle developer is building and testing this on his ToroPlus :)

Thank you all,

Purian23
[Samsung Galaxy Nexus] chasew83:
Awesome, thank you! didnt see it on the official web page, so just making sure!

edit: well,flashed with cna 3.8 and it rebooted a few times but seems to be working now. i do have kind of a noob question, though not exactly a noob lol. what exactly is "i/o scheduler"? it gives options for things like bfq, cfq, sio. what is the best one to run?
[Samsung Galaxy Nexus] jjhiza:
i/of stands for in/out, and it's used to regulate sd card reader and write (read=in, write=out) speeds and functionality. Give me a minute, and I'll copy over my post from Rootz, regarding some of the governor/scheduler pairings that I've found work best together.

------------------------------------------------------------------------------------------------------------------------------------------------------------

Ok guys...here are some of my findings, based on testing different governor/scheduler combos. Your results may vary, depending on how you use your device:

*First...do a clean flash (cache and dalvik wipe) to avoid any potential boot issues.

Interactive/sio: a trued and true combo, that's both quick and responsive, and decent on battery.

On demand/ deadline: another old combo, that many people prefer for its low battery consumption.

SavagedZen/CFQ: slightly slower than Interactive/sio, but very smooth, and provides great battery. If you don't care too much about benchmarking, and want a great all-around setup...this may be a good choice. *[Best for battery...by a LOT]

Interactivex/sio: slightly better battery than Interactive/sio, but similar overall performance. *[Fastest combo...does give micro lag at times]

Lulzactive/sio or deadline: choose a scheduler based on how you want your device to perform. Lulzactive is a mix of Interactive and Smartass, so pairing it with sio will give you faster overall performance, while deadline gives a little more smoothness and battery.

Intellidemand/deadline, sio, or CFQ: Intellidemand has some GPU scaling properties to it, that fit perfectly with JB's Project Butter code changes. Mix it with deadline for better battery, sio for speed, or CFQ for a nice balance.

*My personal setup is Intellidemand/CFQ, as I've found it to be the best for me. I get good battery, it's great for gaming (tested with Order and Chaos, Dungeon Defenders and Modern Combat), stays pretty cool, and stays stable.

***Some Tweaks {color and performance} * * *

ROM Toolbox Pro:

(Under systctl tweaks):

vm.dirty_background_ratio = 70

vm.min_free_kbytes = 4096

vm.vfs_cache_pressure = 30

vm.oom_kill_allocating_task = On

(Under SD boost): set to 4096

Franco app color tuning:

Color multipliers: 157, 144, 200

RGB Gama: -4, 0, 4

Trinity's Contrast Interface: -13

OMAP4 Gama Interface: 1.4

Disable CAB: checked

*Again...these are just what works for me. Try them and play around with them if you want. Hope this helps. ￼

Here is IMO, the best governor/scheduler resource guide in all of my internets! If you want to learn a bit more, check it out.

http://forum.xda-dev...d.php?t=1369817
[Samsung Galaxy Nexus] Craxx:
Any new kernel on horizon :D?

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] cmoG530:
ETA's are the forbidden action on this her X-DEEE-AYUH. In fact, look up.
[Samsung Galaxy Nexus] Craxx:
Yes i know... I only knock on the door :D

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] allgsmnetwork:
trick mod ???

hello all, where can I find the application for tricks?

Thanks :confused:
[Samsung Galaxy Nexus] Craxx:
Trickster app from playstore ;)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] BurnOne77:
Don't rush 12 guys, 11 is awesome, I have no complaints only grateful for this awesome 4.2.1 kernel. My phone hates 4.2.1 othwerwise.
[Samsung Galaxy Nexus] purian23:
Kernel Update!!!

Introducing

v3.0.55-ZenSERIES v12 Kernel

*Zeneractive Lives*

Fast, Smooth & Battery Friendly

Unified Kernel for Toro/Toroplus/Maguro

[B]ZenSERIES_v12[/B]
- Updated to v3.0.55
- Rebased the whole kernel tree to clean up
- Updated bcmdhd+ipv4 with some upstream fixes/wakelock related
- Disabled merging on deadline and no-op
- Added in some more TCP congestion schedulers (cubic still default)
- Some misc. updates - More SoD Actions taken
- Replaced interactiveX with "Zeneractive." (documentation: http://pastebin.com/UrkEke8k)
- Interactive-based governor with "live" CPU hot plugging.
- Behavior on Zeneractive with Great Battery:
- If CPU load is <= unplug_load[cpu] for a given CPU for time = unplug_delay, that CPU will be removed (if online)
- If CPU load is > unplug_load[cpu] for a given CPU for time = insert_delay, that CPU will be inserted (if offline)
- Tunables: unplug_load_cpu1 (default: 25%), unplug_load_cpu2 (default: 60%), unplug_load_cpu3
- Zeneractive (default : 75%), unplug_delay (default: 5s), insert_delay (default: 30ms)

ZenSERIES Kernel v12 4.2

ZenSERIES Kernel v12 4.1

Main Download

Enjoy!

See OP for further information!

Thank you

Android Developer Alliance
[Samsung Galaxy Nexus] nitsua98:
EPIC!

---------- Post added at 09:18 PM ---------- Previous post was at 08:36 PM ----------

Hey guys, I need help. I'm trying to write an init.d script and I need to know what would be a safe %age for unplug_load_cpu1. Would 30% or 35% be ok? (trying to conserve battery here)

---------- Post added at 09:35 PM ---------- Previous post was at 09:18 PM ----------

Ok, I really need help :( I can't figure this out.

Right now I have:

#!/system/xbin/busybox sh

echo "10000" > /sys/devices/system/cpu/cpufreq/zeneractive/min_sample_time

echo "729600" > /sys/devices/system/cpu/cpufreq/zeneractive/hispeed_freq

echo "100" > /sys/devices/system/cpu/cpufreq/zeneractive/go_hispeed_load

echo "50000" > /sys/devices/system/cpu/cpufreq/zeneractive/above_hispeed_delay

echo "50000" > /sys/devices/system/cpu/cpufreq/zeneractive/timer_rate

echo "0" > /sys/devices/system/cpu/cpufreq/zeneractive/unplug_delay

echo "100" > /sys/devices/system/cpu/cpufreq/zeneractive/insert_delay

echo "33" > /sys/devices/system/cpu/cpufreq/zeneractive/unplug_load_cpu1

Can anybody help?
[Samsung Galaxy Nexus] MrCeez:
Will v12 allow WiFi tether on 4.2?
[Samsung Galaxy Nexus] Savant:
Yes it will . They are using the old kernel drivers because then you can connect to wep and use tether.
[Samsung Galaxy Nexus] scarmon25:
Just flashed the new kernel to try something new. Seems pretty smooth so far. Gonna run it for a few days and see. Using it with Trickstermod.
[Samsung Galaxy Nexus] kinfolk248:
real question, honestly in your professional developing option, do you find it adventitious to move to v12 if v11 is running ok, is v12 worth the risk? I see the new gov and all buttttt.........is that kinda the same as what trickster does with the hispeed delay and hispeed cpu speed?
[Samsung Galaxy Nexus] scarmon25:
Using MMuzzys Vanilla build and this kernel and tether works fine for me.
[Samsung Galaxy Nexus] sonicfreak360:
What's the risk? And with nandroid, you don't have any excuses! Go flash and report back yourself!
[Samsung Galaxy Nexus] anthonyp326:
So far so good..but don't know how to have Wi-Fi turn off when in sleep
[Samsung Galaxy Nexus] cmoG530:
All is well with this bad boy so far. No SOD's and battery and performance are as expected. Great work! :thumbup::)

d",b.Sent From My God Given G-Nexus.d,"b
[Samsung Galaxy Nexus] sajty:
Pretty fast first SoD. Stock settings, only min frequency lowered to 236MHz. Android 4.2.1.
[Samsung Galaxy Nexus] Ashtrix:
Just flashed v12 over cm10.1 skank 1012 , boots faster , no starting apps loop :good: !!

will report later about the stability :D
[Samsung Galaxy Nexus] gianton:
v12 running great so far on AOKP latest nightly, with zeneractive/zen at 384/1420MHz max screen off 576MHz.

I will report back for battery life in a couple of days. Thanks for your hard work devs!
[Samsung Galaxy Nexus] Craxx:
Thx for great new release ;)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] mixtapes08:
Does pgm works with this kernel?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] in1400:
Yes, it works great with the V12. :good:
[Samsung Galaxy Nexus] Ashtrix:
420 Metal on Vellamo all stock ,except color:good: !!
[Samsung Galaxy Nexus] purian23:
Wow, even I had to quote my own team member here for the best reply ever! Well done :)
[Samsung Galaxy Nexus] GCbard:
kernel is very smooth! But I have had three SODs today with xylon v11 as my rom. Any suggestions?
[Samsung Galaxy Nexus] jdec529:
What settings are you using. Im running with latest rasbean, just changed color settings and governor to zeneractive with a180 min. Been running very good on my end. No SOD, and no lag. Battery seems really good so far.
[Samsung Galaxy Nexus] gianton:
Same here, running rock stable and very smooth with zeneractive/zen at 384/1420MHz max screen off 576MHz.
[Samsung Galaxy Nexus] GCbard:
Stock governer with max freq to 1600. screen off freq is 536. I also changed the color settings. WiFi performance on, color adapt = off, fsync = off, high perf sound - on
[Samsung Galaxy Nexus] giorgis91:
Can't download it. Can anyone provide a link?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] billouetaudrey:
It have for 4.2 if you want...

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

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] TheMorpheus:
Yes... It's very very smooth!!

Now testing battery life!
[Samsung Galaxy Nexus] giorgis91:
The version that I need ;) But Gdrive says that I need your permission! Thx
[Samsung Galaxy Nexus] billouetaudrey:
Oh

Edit : now ?

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

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] giorgis91:
Downloading! Thanks
[Samsung Galaxy Nexus] billouetaudrey:
;)

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] bbedward:
Updated the download links, our website is undergoing some construction but the forums are still online.

Thanks
[Samsung Galaxy Nexus] bunnahabhain:
I am using this Kernel on CM10 and it is running very, VERY good! No probs whatsoever
[Samsung Galaxy Nexus] gm007:
1600 is too high,try 12xx and see if you still have sod.
[Samsung Galaxy Nexus] bbedward:
I believe SoD may be related to low voltage calibration on 192/230/576MHz due to SR or something like it.

Although it does seem to only affect a minimum amount of people. I may seek a few frequent SoDers for a test build.
[Samsung Galaxy Nexus] sajty:
Yes,it will be probably due to low voltage.Because of fast SoD on v12 i had to change kernel.Now i am using Air Kernel - sakuractive governor.Its even more aggressive with hotplugging than zeneraktive,but i run it with no problems.However,there is quite big diffrence in voltage between Air and Zen...
[Samsung Galaxy Nexus] gianton:
Just had a SOD too, I was running zeneractive/zen at 384/1420MHz max screen off 576MHz. I'm running now 384/1305MHz max screen off 729MHz, will report back if it's OK.
[Samsung Galaxy Nexus] Craxx:
I can test if you want. I get sod in the morning after getting a phone call.

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] billouetaudrey:
One Day with call etc... And no sod... Default settings...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] TheMorpheus:
I had one too... Phone was in standby, I wasn't able to wake it up!
[Samsung Galaxy Nexus] GCbard:
it is funny though. The sods stopped after i used an already inputted color profile. The SODs happened several times in a row after setting a custom color profile that I came up with. Could that be the issue?
[Samsung Galaxy Nexus] bbedward:
Your color profile may have been causing the display to draw more power, therefore maybe an undercalibrated 192/230/576 (576 did not have its own fuse OPP declaration) voltage led to the SOD.

I also replaced ezekeel's color control with the more direct voodoo port CM uses. I believe they both work the same, I only chose the latter because it seems well maintained.
[Samsung Galaxy Nexus] justme1988:
I love the kernel, specially the colors! They seem to be way more vibrant then in any of the other kernels!!
[Samsung Galaxy Nexus] F1tty:
Fkn pure awesome ;)

Thx 4 IT!
[Samsung Galaxy Nexus] lsv-1:
I'm on stock odexed 4.2.1, installed v12 last night, tested it for a few minutes and then put the phone on charger, this morning SOD :(

Sent from my Nexus Prime JB 4.2
[Samsung Galaxy Nexus] Sik-1:
Dis is killing me lol, I shall start fresh and report back
[Samsung Galaxy Nexus] nitsua98:
Thanks @bbedward! You're the man! And you too, @purian23 for this awesome kernel! I'll be running this on all my ro!ms
[Samsung Galaxy Nexus] bbedward:
Those with SoD issues, here's a public test build. Report back if you have success or no success:

https://dl.dropbox.com/s/7cusobtf1k6jyol/v3.0.55-ZenSERIES_v13_beta1.zip?dl=1

Includes:

- https://github.com/AndroidDeveloper...mmit/3b3e4ec0b7f1aee5a5d8bb7279433efc380fd59f

- https://github.com/AndroidDeveloper...mmit/35f14a8dc2e8fd536ac9b1d9c2e5903c7380ec43

- https://github.com/AndroidDeveloper...mmit/5561531c8779a15e6b8c1cdc52caeb01cf488aa6

- https://github.com/AndroidDeveloper...mmit/29f0572ca7b2d20802b53c98d30e4272f3693027

- https://github.com/AndroidDeveloper...mmit/043d4c539364b293ca55603f83ecbbd6c5d8ec89

- https://github.com/AndroidDeveloper...mmit/f91a2c08f775d10d32cb7531aeb4a68217c1a3ae

- https://github.com/AndroidDeveloper...mmit/f91a2c08f775d10d32cb7531aeb4a68217c1a3ae

- https://github.com/AndroidDeveloper...mmit/3c821c9c73d61a7f1fad980e64bacbe7d5888c9e

- https://github.com/AndroidDeveloper...mmit/5085cde38934077ca881d74567af8d8ccb7d490f

- https://github.com/AndroidDeveloper...mmit/cebdf8a38279c995ca98054ffcbce6a4ac81c97a

- https://github.com/AndroidDeveloper...mmit/73af7ddc81a0246ab37283e50414a5d52d63c01c

- https://github.com/AndroidDeveloper...mmit/83515a0e36f3883a68287fb97ccdaa9ec80397a3 *

This is for 4.2

Thanks
[Samsung Galaxy Nexus] cmoG530:
You can change the colors on all kernels.

That said, this kernel (v12) is still golden. PGM is active and still no SOD.
[Samsung Galaxy Nexus] Braneless:
Interesting... I've had three SOD yesterday and today, although I've never had any with the previous versions. Running v12 with AOKP 4.2.1. Will try the test build and see if there are any changes.
[Samsung Galaxy Nexus] Jose Viegas:
Same here, had to change kernel because of that (stock parameters)
[Samsung Galaxy Nexus] nitsua98:
I've never had a sod with any kernel... Wtflol?
[Samsung Galaxy Nexus] Braneless:
I haven't either, until v12. V13 has huge increases in voltage, so we'll see how that works. Just flashed a few minutes ago.
[Samsung Galaxy Nexus] Braneless:
Just got my first SOD with v13. Question for those of you with this issue: are you using PGM? My latest refusal to wake up resulted from trying to wake the phone with PGM - the screen semi-lit then froze, necessitating a battery pull.

376/1302, 576 max screen off, preset voltages, zenteractive gov.

I've disabled PGM, so we'll see if it happens again.
[Samsung Galaxy Nexus] nitsua98:
Noon question: what is pgm and how do you enable/disable it?

Sent from my jellified A500
[Samsung Galaxy Nexus] f100cleveland:
Two straight SOD's with latest v13.

No WiFi

Stock colors

Stock clocking and gov/scheduler

On chrome browser both times.

Been good for like 3 hours now.
[Samsung Galaxy Nexus] Savant:
Its an app that can control the screen turning on or off by gestures. https://play.google.com/store/apps/details?id=net.ponury.pgm2free

---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------

Its lately been screen of death because 4.2 having issues and its being recognized by Google that its a bug. Hopefully they release the update soon because it plagues many users.
[Samsung Galaxy Nexus] gm007:
SOD is sleep of death, did you mean freezing and reboot?
[Samsung Galaxy Nexus] Aerobreaker:
a apps from bponury, play store available
[Samsung Galaxy Nexus] anthonyp326:
Same here set at 384 then no problem..
[Samsung Galaxy Nexus] gparmar76:
Kernel is working good but I can't get 1.536ghz speed to work...using Rasbean 12/8 and CFQ scheduler...I tried a bunch of different settings but 1536 just isn't working for me...oh I'm using V12 by the way.
[Samsung Galaxy Nexus] wizard83:
I have v12 from yesterday, no sods. All kernel parameters are stock. I don't use pgm.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sajty:
Testers, try to raise screen off max frequency to 720 MHz. As dev said, 590 can be problematic.
[Samsung Galaxy Nexus] yosula:
With b13 without change any settings

This is very smooth than v12

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] gianton:
I've had 3 SODs with v13b running default settings and have PGM installed. The screen had a whitish color when I had the SOD.
[Samsung Galaxy Nexus] gm007:
Could be the gpu voltage?

Did you guys tried the 307 freq?
[Samsung Galaxy Nexus] billouetaudrey:
With v12,yesterday 0 sod, this morning 2 sod... Really strange...

Envoyé depuis mon Galaxy Nexus avec Tapatalk