yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 7175:
Running 4.2.2 fancy r6 on liquidjb v2.1 rc1 with 4.2.2 gpu binaries. Ondemandplus is running great and scales really well from 192-1228 with up-threshold set to 95. Very stable too, I'm running with all voltage UV'd. :)

With fancy and almost every kernel I've tried, it seems like setting gpu max frequency to 384 gets better battery life than 307. I'm guessing it's related to some other settings, load, and gpu governor, but was wandering if anyone has a good explanation for this.
[Samsung Galaxy Nexus] bigknowz:
Last_kmsg

Installed after wipe cache and dalvik. Let kernel settle for 30 minutes or so and then rebooted phone. Had a dirty reboot after that. Here is the last_kmsg. Hope it helps.
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

This ROM gives killllllller battery. Anyone do any tweaking or use as stock

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

Sorry for a dumb question but 95 up vs stock 80 is that for more battery or to be a tad more responsive
[Samsung Galaxy Nexus] pcphobic:
Good idea.

So far so good on mine. I left everything at stock settings as what boype intended it to be.
[Samsung Galaxy Nexus] zoomy942:
Agreed. To spot a trend.

Toro. Cm nightly. Stock setting except 1.4 OC.

Not a single SOD ever on any version.

---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------

Good idea. Maybe some of those reporting constant SOD can test this idea and report back.
[Samsung Galaxy Nexus] CCaaNN:
I think boype also thinks like that and thats why he is asking which governor people use. But there is not enough data to claim that.

For me pre35-2 works awesome without any sods with ondemandplus. And i didnt face with any sods from r33 to r35-2 with ondemandplus.

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] abhishek93:
i get this when i enter "no such file or directory."

su

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

.
[Samsung Galaxy Nexus] mixtapes08:
Read my note..

-3StarsAndaSun
[Samsung Galaxy Nexus] abhishek93:
yes mate i got you i m doing this after an sod... :confused:
[Samsung Galaxy Nexus] BOY_:
And... Switching to interactive governor. My liquid smooth toro sod'ed within 30 min of flashing.
[Samsung Galaxy Nexus] mixtapes08:
Try it again when it happens

-3StarsAndaSun
[Samsung Galaxy Nexus] parkson:
To my knowledge it is not possible to retrieve last_kmseg after SOD because user is required to pull battery. Can only be retrieved if phone reboots. Someone correct me if incorrect
[Samsung Galaxy Nexus] mixtapes08:
Your right... But that's totally different story than having an sod.

-3StarsAndaSun
[Samsung Galaxy Nexus] flybass:
To help diagnose the issue. I had sod on pre 35-01 (so far not on r34) with the ondemandplus governor. I've been using aospal (toro) with fancy kernel for about a month.

Sod pretty much immediately after flashing pre35-02. Back on r34 and waiting to see if I get SOD.
[Samsung Galaxy Nexus] mpokwsths:
I don't understand why many people use the OndemandPlus gov. It is much better than ondemand but it still cannot match the flexibility of interactive. Interactive governor is perfect for our device. It can be tailored towards performance or battery preservation.

You want battery?

Hispeed freq 729 and above_hispeed_delay 50000, boostpulse_duration 20000

You want performance?

Hispeed freq 729 (although the 806 mhz step was much better...) and above_hispeed_delay 15000, boostpulse_duration 50000

Simple as that.
[Samsung Galaxy Nexus] abhishek93:
yeaa i am trying from past 2 sod.. i m not able to get last_kmsg...
[Samsung Galaxy Nexus] Sounava:
Hi can you tell the truth trickster settings you use for this cancel?

I was currently using bfq with rab 512 and interactive tunables which Osmosis suggested in his signature (although that was for Franco).

I would want more battery life. Also sometimes my phone freezes for some seconds say while launching whatsapp and trying to type something.
[Samsung Galaxy Nexus] jesssiii:
Had to battery pull, so there would be no file available, right?

GNex Toro
[Samsung Galaxy Nexus] creeve4:
SOD with r34 last night while I was sleeping, alarm didn't go off this morning.

I had none while running pre34-01
[Samsung Galaxy Nexus] zoomy942:
Which governor?
[Samsung Galaxy Nexus] RevengeFNF:
Got my first SOD today with r34. Its was my first since i use Fancy Kernel.
[Samsung Galaxy Nexus] jsage:
Hi boype, here's what I've got:

Toroplus

CM10.1 nightlies

r34 Extended

OnDemandPlus

No over/underclocking

No over/undervolting

No Trickster Mods

No change from kernel settings as they come from boype

I'll reflash r34 and retrieve a log for you after the next SOD.

Thanks boype!

I've always used stock settings, magnus. I've been running fancy since April, and I never had an SOD until pre34.

Have a great day,

John
[Samsung Galaxy Nexus] bunnahabhain:
Ok now try again with stock values, but change governor to interactive. And clean cashe of the kernel app you're using.

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] yaatzek:
Sod here too. No lastkmsg, std version, stock settings, only max changed to 1.3
[Samsung Galaxy Nexus] RevengeFNF:
Maguro

CM10.1 nightlies

r34 Extended

OnDemandPlus

No over/underclocking

Undervolting - But i did the same undervolt on all fancy releases.

Trickster Mods - Undervolt and Color.

No change from kernel settings as they come from boype
[Samsung Galaxy Nexus] mpokwsths:
So, it looks like OndemandPlus is the problem. Is there a single case of SOD with interactive?
[Samsung Galaxy Nexus] flybass:
As one who experienced SOD's with pre35 (both versions) and Ondemandplus, I'm going to load up pre35-02 and use interactive governor to test this theory.
[Samsung Galaxy Nexus] namtombout:
It's not odp. People with sod should try a clean install of everything.

Yesterday franco said that mpc is broken in the 3.0 branch so users with sod should try setting that to 0.

I'm sure it's evident to boype that some users have had sod's on the previous few builds. Wait for a fix or flash an older kernel that's stable for you.

U.O.E.N.O
[Samsung Galaxy Nexus] boype:
I pretty much think it's the ondemandplus patches. I'll double check what I did there today or tomorrow. Funny thing is this: I dropped the memory mapping optimizations, as you recall. They're probably working just fine and ondemandplus is the cause ;) We'll find out soon enough.

Meanwhile: zcache combined with the LZO compression update really has some magic to it in my opinion. Good stuff :good::good:
[Samsung Galaxy Nexus] nitsua98:
Ondemandplus is not the problem. I'm not getting any Sod's here with ondemand+
[Samsung Galaxy Nexus] boype:
Me neither, but we cannot exclude the possibility that it is the cause. So far, all reported SODs were with ondemandplus. Plus I recently changed some things with the governor. We'll find out!

[edit] I have added a note to the OP about the issue.
[Samsung Galaxy Nexus] Starsream88:
[MENTION=4615478]boype[/MENTION]

So you will put back the memory mapping optimizations on next version ? :thumbup:
[Samsung Galaxy Nexus] zoomy942:
Oh man I hope so. :):)
[Samsung Galaxy Nexus] boype:
I understood it this way: He has encountered SOD on ondemandplus and is now switching to interactive. Or am I mistaken?

Definitly worth a shot, right? :good:
[Samsung Galaxy Nexus] BOY_:
You are correct sir. taken out of context, I can see the confusion though :).
[Samsung Galaxy Nexus] CommanderDuplex:
SOD with Interactive after ~20-30min in Idle but the LED notification works pretty good ^^

Edit:

using R35_2
[Samsung Galaxy Nexus] zoomy942:
YEAH!!!!!!!!
[Samsung Galaxy Nexus] Rufufu:
Which ROM?
[Samsung Galaxy Nexus] boype:
Bummer for my theory :x
[Samsung Galaxy Nexus] Rufufu:
And what is your opinion on the idea that multi-core power saving is not working on 3.0 branch?
[Samsung Galaxy Nexus] boype:
Where has this been posted?! I didn't catch it
[Samsung Galaxy Nexus] Rufufu:
Here :

http://xdaforums.com/showpost.php?p=43413853&postcount=3605

I'm searching the franco's post, you will see, it is franco style !

here it is :

http://xdaforums.com/showpost.php?p=43395874&postcount=42546
[Samsung Galaxy Nexus] CommanderDuplex:
use the Purity 5.7.1
[Samsung Galaxy Nexus] boype:
Well franco has a great deal of expertise, when he says something, you'd better listen. However, I'm not satisfied with his claim that it's broken in 3.0 kernel. While it might be possible, I'd like to see some elaboration on that.

In any case, even if it is broken, it does not do any harm :) But if there's really evidence that it's not working, I might as well remove it.
[Samsung Galaxy Nexus] boype:
pre35-03 up

Hi again,

I have just done a quick build with two reverts in order to find the SOD cause. So, this especially goes to the folks reporting them.

http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-pre35-03-ext.zip

Best regards
[Samsung Galaxy Nexus] zoomy942:
Memory opts put back?
[Samsung Galaxy Nexus] yaatzek:
Thanks for that, flashing right away, will report when I notice something.
[Samsung Galaxy Nexus] jesssiii:
I had just one SOD on pre 35-01 using Sorceress ROM, mostly default kernel settings. I flashed pre 35-02 right after and changed the power saving from 2 to 0 since it's been reported broken. No SOD as yet :thumbup:

I'm very impressed with this version's performance! After only a few hours, can't comment on battery.

BTW, i also removed the initd files for fstrim and z-cache before flashing 02.

Galaxy Nexus Toro (VZW)
[Samsung Galaxy Nexus] boype:
Not yet. I first want to find the SOD cause before introducing new experimental stuff.
[Samsung Galaxy Nexus] flybass:
So far no SOD's for me on pre35-02 using the interactive governor. I don't want to speak too soon, but I had an SOD pretty much immediately after flashing both pre35-01 and pre35-02 (with odplus)
[Samsung Galaxy Nexus] yaatzek:
It doesn't boot :(
[Samsung Galaxy Nexus] Hexo07:
I change the governor settings to interactive and get a SOD.

(I hope SOD means: Black Screen).

I tesed r35 r2....

I have to remove the battery to reanimate my gnex. After a SOD i lose a lot of battery (see screenshot).

As ROM i use Purity 5.7.... i will change the ROM and go back to R33. For me the most stable.
[Samsung Galaxy Nexus] shawnaye:
Hey boype, like I said earlier, the pre 35-02 makes my phone feel awesome.

But I just faced my first sod on completely stock settings.

Hope to hear some good news from you, in the mean time, I'll try switching to interactive and see if it does anything.
[Samsung Galaxy Nexus] Starsream88:
Really strange !!! Never had sod's using fancy kernel, i'm using r35 pre02 and no problem at all !

My DD rom is rootbox latest nightly, interactive governor.
[Samsung Galaxy Nexus] yaatzek:
This isn't strange. Every one of us has different rom, different apps, even different chips etc... so it is normal in the way i observe it from 3 year android perspective that even the same devices differ, especially when it comes to kernels, and that's why for some of us it works and is stable and for others not, like me :)
[Samsung Galaxy Nexus] dmillerzx:
I can confirm this also, tried doing a fresh rom install with the latest test kernel. Just sits at the splash screen. Has anyone successfully booted Pre r35-003?
[Samsung Galaxy Nexus] jsage:
Hi boype, thanks for the test version. Unfortunately for me it would not boot - stayed on the bootloader screen for 15 minutes before I rebooted to recovery and reflashed r34.
[Samsung Galaxy Nexus] 0vermind:
Glad I'm not the only one, I've been running pre34-03 since Saturday, and it was super fast and smooth but freezes a lot. I got a couple of SODs and screen freezes on apps where the phone locked up with screen on and had to pull battery. Actually slept in twice now and missed my alarm cause the phone was froze up. /:

I hope you'll eventually be able to put the memory settings back, cause I thought those were so cool! Definitely noticed a performance boost with those. I'm going to flash pre35-02 since it looks like pre35-03 isn't booting for some people. Since the phone is freezing up, any logcats or last_kmsgs that will help?

Kernel Settings: Using trickster. Stock with color adjustments, been messing around with governor, going back and forth between interactive and ondemandplus. This morning my phone locked up and when I checked which governor I was on, I was using ondemandplus, but I almost positive I've had SOD on interactive, but can't be sure so I'm going to leave it on today and see what happens.

ROM: Slimrom

Apps: Not an app, as I have not installed any new apps, and have not had these freezing issues on other kernels
[Samsung Galaxy Nexus] jesssiii:
Ditto.

Back to pre02, which has been great, no SOD. I changed the power thingy to zero. Are you saying even if it's not working, that it's not a cause for SOD?

Galaxy Nexus Toro (VZW)
[Samsung Galaxy Nexus] Blackcrx:
Never had a SOD with fancy either. I'm wondering if it could be ROM or app related.

I think SOD ppl should start posting ROM and kernel settings from now on

I've had a couple of instagram lock ups but I think that's app related since I had these with other kernels also.

Test1 runs awesome for me but I'll try test3 anyways. Awesome work boype

I've also always used interactive and MCP set to zero
[Samsung Galaxy Nexus] Gil Smash:
Test 3 does not work.
[Samsung Galaxy Nexus] Blackcrx:
I read that earlier too, just wanted to try it for myself. Haha

I can also confirm that test3 won't pass google logo, back to test 1
[Samsung Galaxy Nexus] Gil Smash:
Haha well that's one way to do it.
[Samsung Galaxy Nexus] gizmoid:
SOD on next:

ROM: Purity 5.7.1

Kernel: (r34)

Governor: ondemandplus or interactive

It`s all stock except WIFI High Perfomance - ON and Color Profile - trick.
[Samsung Galaxy Nexus] Sounava:
Sod on r34. Interactive governor. XenonHD v11.1 ROM.

My first Sod with Fancy kernel.

I will be happy to provide any more information if needed.
[Samsung Galaxy Nexus] lesp4ul:
Rom: AOSPAL 9.1

Kernel: r34-std

Mod: Crossbreed

Never had SoD till i flashed 34 yesterday and only occured 1 time (stock settings, ondemandplus, custom color via trickstermod).

r35pre3 didn't boot at all :)
[Samsung Galaxy Nexus] jjjameson:
R35 pre-2 got 2 reboots today. Then i installed r34 and the battery life is terrible. In two hours of standby battery drained %40 which is not normal for my phone.

Now reverting back to pre34-5 which i was getting really good results.
[Samsung Galaxy Nexus] lesp4ul:
Edit
[Samsung Galaxy Nexus] paarthdesai:
sod on every build after r33 :(.. and zcache is no good for me either

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] ali4ek:
SOD or CM 10.1 final + r34. SIO Plus + Hyper.

Back to r33 - works fine.
[Samsung Galaxy Nexus] stevensoaj:
[MENTION=4615478]boype[/MENTION], I can't boot at all with pre35-03. It never get's past the Google logo. I thought it was my init.d script at first, so I reflashed r33 and removed it, then flashed pre35-03 again, but still no luck. Just get's stuck at the Google Logo.
[Samsung Galaxy Nexus] Gil Smash:
Yep that has already been addressed.
[Samsung Galaxy Nexus] boype:
pre35-03 re-up

Sorry for the defective file... I re-uploaded and tested it. works good.
[Samsung Galaxy Nexus] Blackcrx:
That's the difference between testers and users.

Testers will try for them self and prove or disprove claims. Users just follow the crowd.
[Samsung Galaxy Nexus] abhishek93:
Don't knw it might help or not but i noticed that before a SOD battery percentage remains at one or two number like mine was 71-72 for about half an hour though i was using it with wifi on, and after that as it goes to sleep than the phn keep on sleeping like a snoar lax :P
[Samsung Galaxy Nexus] mixtapes08:
What did you reverted this time?

-3StarsAndaSun
[Samsung Galaxy Nexus] stevensoaj:
Bleh. Sorry. Didn't notice others had already posted. I swear I read all the posts! Fail.
[Samsung Galaxy Nexus] zoomy942:
I'm on r34 pre 3. Last build with memory optimization
[Samsung Galaxy Nexus] klobkelosh:
Had the oddest boot immediately after installing the fixed version of pre 35-3 on top of today's cm nightly. After the app optimizing, phone was not responsive. I thought it was a SOD but when I looked real carefully at the screen I could see a very faint very slowly moving boot animation. Did a battery pull and rebooted. All and fine except my wallpaper reverted to the ROM default.

Not saying it was the kernel. Just odd.
[Samsung Galaxy Nexus] mpokwsths:
One observation:

Latest Fancy versions seems to be picky with ROMs.

With pre35-02 I had random reboots and crashes with SaberMod (Linaro/GCC 4.9). Switched to SuperNova 3 (Google toolchain) and until now not a single problem.

So, a theory: Try non-Linaro Roms and report back. Maybe later on, boype will compile his kernel with Linaro toolchain again.
[Samsung Galaxy Nexus] thomstrack:
I had a SOD in r34. Stock settings only "min" changed to 384mhz.
[Samsung Galaxy Nexus] flybass:
Ok - SOD with pre35-02, Interactive governor ,AOSPAL (linaro).
[Samsung Galaxy Nexus] jesssiii:
My SOD was with the pre01, haven't had problems with 02 so I'm staying here.

Galaxy Nexus Toro (VZW)
[Samsung Galaxy Nexus] Bl4ck3urn:
No SOD on r34. Default settings except my own color settings.
[Samsung Galaxy Nexus] androidmichael:
Same with me.
[Samsung Galaxy Nexus] sajty:
I am still waiting for first SoD, never faced this issue with Fancy.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TheMysteriousOne:
I am on Atom ROM which is linaro and have never had a SoD with fancy.

In fact, here are my battery stats with pre35-1 on stock battery.
[Samsung Galaxy Nexus] stevensoaj:
He reuploaded the file and now I'm not having any issues. Pre35-03 is performing admirably so far. :thumbup:
[Samsung Galaxy Nexus] creeve4:
Ondemandplus. All stock kernel settings
[Samsung Galaxy Nexus] smtom:
Toro

Pre 35–02, SOD when charging.

sio plus, 1036/384 no oc or uv or anything else, Interactive.

Liquid Smooth daily 2.5.

Went back to 34-01.
[Samsung Galaxy Nexus] Riekr:
One sod today latest cm10.1 nightly, bfq ondemandplus, 307 GPU, android color profile and cab. All the rest is stock.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] n2rjt:
SOD R35test3 stock ROM default settings plus PGM, Maguro. Networked via WiFi.

Phone sleeping, on vibrate, unplugged.

Phone vibrated a notification and LED started a slow pulse. I think it was email.

Phone didn't respond to power button or PGM swipe. I tried for two minutes. LED was still pulsing.. Doesn't that indicate that the kernel was still alive at some level?

Edit test3, not test2.
[Samsung Galaxy Nexus] chikimonke:
In past experiences, if PGM is loaded, and you got an SOD, then remove PGM and see if it happens again. I personally found that the instability that it causes isn't worth it.
[Samsung Galaxy Nexus] Nemed:
I got a sod on pre35-03...phone doesn't wake up after screen off. Ondemandplus/sioplus 192/1228, rab 512, gpu 512, undervolt -75 for each step (never had a problem before with these voltages). I noticed sone random ui lag too...
[Samsung Galaxy Nexus] phishn:
I went the opposite way. Linaro atom 622 worked perfectly fine pre 35 release 2. Then went to liquidsmooth 2.8 and experienced 2 sods. Same kernel settings, same installed apps on both. Only real difference is that I had privacy guard enabled on liquidsmooth for both sods. Could be coincidental but I disabled it for now.
[Samsung Galaxy Nexus] Hoochie_Coochie:
Sod on 35test3, was charging at the time

All stock kernel settings nothing changed

On jellybro latest
[Samsung Galaxy Nexus] creeve4:
My SOD on r34 was also while charging at night.

All stock kernel settings
[Samsung Galaxy Nexus] Gil Smash:
Build 35 test 3 no SOD. Great considering my phone was freezing constantly before.

Edit: atom rom and stock kernel settings
[Samsung Galaxy Nexus] KeithLing1115:
I could have sworn I read somewhere that the phone was built to use interactive governor so you will see the best performance on interactive. If it's true why don't we default to interactive. Personally I always get the best performance with interactive.

Also anyone on Sorceress when using crystal ball with floating windows activated getting kicked out of the app you're using when the floating Window pops up? It used to work and not sure what's happening.
[Samsung Galaxy Nexus] TheMan0790:
Pre 35 Test 3 has been awesome for me on CM 10.1 nightlies. Running on SioPlus/OnDemandPlus.
[Samsung Galaxy Nexus] n2rjt:
Same thing happened again without PGM.
[Samsung Galaxy Nexus] phishn:
Interesting. I had zero sod issues on atom. Are you on Toro?
[Samsung Galaxy Nexus] BOY_:
So far so good after 7 hrs on test03 (no whammies)
[Samsung Galaxy Nexus] jsage:
Hi boype,

I've been running pre35-3 for about 8 hours now, no SOD. I've tried waking after 15 minutes, 30 minutes, one hour, etc - no issues. Previously I could only go about 3 hours without an SOD.

Toroplus

CM10.1 nightlies

pre35-3

OnDemandPlus

No over/underclocking

No over/undervolting

No Trickster mods

All kernel & performance settings as you designed them ;)

Thanks!

John
[Samsung Galaxy Nexus] Gil Smash:
Yup
[Samsung Galaxy Nexus] zoomy942:
Still on 34 3 for men optz and no sod
[Samsung Galaxy Nexus] szale9001:
Couple of SODs on pre35-3. Interactive governor with the Franco Team tunables, 1344 max freq,trinity colors and CAB on. All else default. Interestingly enough, pre35-01 was fine. Not sure if its coincidence but I was SOD free. The SODs seem random but at least 1-2 of them happened during or after charging. I know a couple of others mentioned a correlation to charging so I figured it might be relevant.

Also, I tried to cat the /proc/last_kmsg and it said that the file didn't exist. I guess logging is deactivated?
[Samsung Galaxy Nexus] n2rjt:
Pulling the battery means we lose that file. But for me anyway the kernel is alive enough to blink the LED so can we think of a way to diagnose or reboot without pulling the battery?

Edit: Pre35test3 w/ interactive and PGM has been perfect for several hours.
[Samsung Galaxy Nexus] jeffcavicchi:
All SODs for me seem to have been charging related as well - not sure what that means, though. Haven't gotten one on pre35–03 yet though - will see in the morning.

I have been changing to force fast charge, 1442 max frequency, 512 gpu, all other settings stock.
[Samsung Galaxy Nexus] szale9001:
Next time I'll try adb and see what's up.
[Samsung Galaxy Nexus] clnzx2:
I have used every version up to 35-02 and had no issues. Toro running latest Axiom. Stock settings.
[Samsung Galaxy Nexus] pcphobic:
No issues from me on pre35-02.

Stock kernel settings.

LiquidSmooth ver.2.5

Magoro.

Now testing pre35-03
[Samsung Galaxy Nexus] un.droid:
pre 35-02 running like a beast for a day. only 2 issues ive encountered so far: first, after playing audio thru bluetooh for about 30 minutes audio breaks. second issue, sod in the night. had to pull battery out in the morning. other than that, very smooth and very responsive. btw, all settings are stock running on latest PA.
[Samsung Galaxy Nexus] motorazrv3:
What is instability? Pgm? I had never any problem with pgm. Working like a charm!

Flashed 35 pre 02 last night. Set up pgm and used trickster to set rab to 512, max screen on to 384, min screen off to 192, multi core to 0. Rest unchanged.

Using purity 5.7 as my daily driver.

When I went to sleep I put my phone on charger and set my alarm.

This morning my phone rung normal. It was still alive, no sod. No problems so far. At the moment I am at work. Let's see what will happen. I expect nothing abnormal because I never had any sod using any combination of fancy kernel and purity rom.

Hope we can solve this sod together.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta

---------- Post added at 07:25 AM ---------- Previous post was at 07:00 AM ----------

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] Hexo07:
I am back on R33 with Purity 5.7.1 and everything is running smoothly and fast.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2