yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Thank you :D

Hmm, I wrote that you should use nstools for tunables, what do you mean exacly?

Well, overvolting is essential. I can go even up to 1,72ghz :) I am thinking of putting suggested voltages when overclocking in OP :)

I highly recommend 1,2ghz with 125% liveoc, 1375 arm voltage and 1150 internal voltage.

Vice city is smooth? really?

It is no problem because android1234567 did so, so I would have to simply cherry-pick his commits. But personally I always thought that on our player it is more like just showing that it is possible. Does anyone really use it ?

Thank you, sure, I love feedback. I have to change 1300mhz frequency which doesn't like liveoc and andd higher than 1400 probably :)

Exacly, isnt it what I have said that we have to use nstools? Including it in settings would require settings.apk modification, maybe in future. You should try liveoc to see if you really can't overclok your gpu. With a small value like 110&.

And people, how do you feel about minimum brightness, is it lower? Use rootdim ofc

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
Mmm ok. But I have a question. Wich frequency steps have I to overvolt? Or just the Max Arm and Int volt? :confused: And yeah vice city is very near to be perfectly smooth :) But on the other hand, AnTuTu benchmark does not give good marks...

Now, I'm not using OTG because I have to find the cables to connect (I don't dare to make cables for myself). But I want to use it someday... :silly: And yeah, suggested voltages in OP will be very useful. Thanks man.

Ah, I've noticed that when I was playing vice city suddenly sound in game (not in game menu) crashes. It's strange
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Antutu is poor benchmark not giving stable results. But I get 5200 constantly while on 1,5ghz.

You have to overvolt those frequency steps which you liveOC ;)
[Samsung Galaxy Player 4.0, 5.0] txordi:
With 1200 1.25 and your voltages (1375 arm and 1150 int) I have reboots all time... Wich steps do you OC? Maybe is because I have INTL galaxy player
[Samsung Galaxy Player 4.0, 5.0] KOala888:
no, version have nothing to do with it.

Think logically, you overvolt only that frequency so you should liveoc only that too!

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
I just set live oc to 110% and it crashed immediately. I really don't think my player likes that stuff :p

But I love being able to oc to 1.4ghz either way!

So a big thx to you.
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
Oops, didn't see that :p
[Samsung Galaxy Player 4.0, 5.0] KOala888:
really weird, did you overvolted arm and int? it shouldn't be like that

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Yes, but I don't know how much I have to overvolt them. I tried with 50 more per frequency.

Now I will try with some more.

Without liveoc and max 1.4ghz I get some crashes as well, but less than with 1.2ghz and 110% liveoc.

Maybe 1.2ghz is my player's vulnerable frequency.

Right now, I am testing liveoc on 800-1100 by 105% and leaving 1200 and 1300 untouched by liveoc but overvolted as well.

I must say, this makes the device a lot more responsive than without any liveoc'ing.

Soon I should know if it's stable or not.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Every device is different an yours seems to be a lot different so it is really hard to guess.

Well, if 1,4gHz give you crashes you may try to undervolt int voltage :)

It should be the same for every frequency, I have no idea why other devs increase those. I will fix it.

So experiment and post here your results :)

I plan to add 1500 and 1600 frequencies too. Also I have to change 1100 and 1300, weird but it seems that odd frequencies lagg and are unstable while using liveoc :)

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Mine cost only 120 bucks when it was just on the market. Maybe it's a refurbished one or it's just too old.

I don't quite understand though, why it's so much more responsive with that little liveoc. Seems like 800mhz love being overclocked.

And why should I undervolt 1.4 GHz? Shouldn't I overvolt it to be more stable?

Thanks for all your help and I'm glad you decided to make this new version of your kernel ;)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Well, we can guess that your problem is connected to gpu frequency or which is also possible to voltage given to it. So then lowering 1,4ghz int voltage should do the thing :)

Thank you :)

I like it too, I always liked to have a choice as far as option has any sense. That is why I won't add more IO schedulers or senseless governors.

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
[MENTION=3215043]KOala888[/MENTION]

How did you find out that the int voltage is for the GPU/bus?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Hmm I guess I have read it somewhere :)

Probably tk-glitch's thread or derteufels, I don't remember.

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
Were you able to OC the GPU more by increasing the int voltage?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Havent tried yet. Stupid thing because I have holiday and I almost stopped gaming on my player.

As for me 1200mhz with 126% liveoc works perfectly. But 1000mhz and 800mhz with 126% are fine too. I will replace 1300 which is weird with other frequency and try to get ~1660 with 250 gpu which could be a killer. Anyway, significantly higher cpufreq with 250 gpu :)

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
I'll try it now :) 1375MHz CPU with 275MHz GPU
[Samsung Galaxy Player 4.0, 5.0] KOala888:
You should also try liveocing different frequencies :)

Just tried 1000 with 130%, ui worked but it nenamark freezed. I will play with it when my battery won't be like 5% and when I will have some time :)

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Ok, I sort of followed your advice and lowered INT voltage for 1.4 GHz, then I tried to OC frequencies from 800-1400 by 108%, but of course it crashed. :( So I left 1.4GHz voltage lower anyway and liveoc for 800-1200 at 108% and so far it's stable. I've already saved that preset, so I can go back to it, when further tuning goes south. I'm using rather weird voltages right now, so I would never be able to remember them otherwise. :)

ARM

1400mhz - 1350mv

1300mhz - 1400mv

1200mhz - 1375mv

1100mhz - 1350mv

1000mhz - 1325mv

800mhz - 1275mv

INT

1400mhz - 1125mv

1300mhz - 1125mv

1200mhz - 1175mv

1100mhz - 1175mv

1000mhz - 1150mv

800mhz - 1150mv

These voltages probably don't make any sense, but I'm not gonna touch them, until system crashes, or somebody tells me otherwise :)

Btw: Sometimes my system just hangs, then freezes, then reboots, and other times, like when I first activated liveoc but forgot to overvolt, it just reboots instantaneously.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Weird. But it only shows that you have device with very poor quality chipset ;)

Nobody can do accually anything with it. You can just experiment and find optimal frequencies, maqybe just even without liveoc
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Yeah, looks like it. Just froze again, while reading an eBook and adjusting brightness. I will have to continue experimenting.

Is there any way I can find out which frequency causes the crash?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
disabling one after another starting from 1,4?

Or dmseg/logat such a things

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Is there any way to test stability? Like a stress test or something?

The ones I've tried ran through, even though my system proved not to be stable later on.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Personally I have never done it with any apk

I would say the easiest way would be benchmarking which should stress phone to its 100%
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Delete please. Spoke too soon.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Your bus must be really poor quality. but have you tried 1400 with 1000 int voltage?

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Right now, I am trying your recommended settings for 1200mhz.

It ran through 2 antutu benchmarks without crashing. I know it will crash soon, though ;p just want to be sure before I give up.

Afterwards I am going to try setting int to 1000mv, thanks for your constant help!
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Which one? No problem. I have no idea why other devs increased int voltage, it is fixed for the next version. I also replaced 1300 with 1320 which shouldn't behave weird with liveoc. I want to change compiler to theoretically better one too.For now no idea what else could I add/change :) For me works quite well

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
1375mv at 1200mhz, but with 115% liveoc instead of the125% you were using.

3rd antutu just ran through. 1200 in 3d graphics and 4600 in total score. I'd love to be optimistic now, but the crash will crush me then :p
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Good luck :)

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
Ok guys, the best I've reached is 1400 with 114% (arm 1375mv, int 1200mv). Only overclocking the last frequence, 1400.

One thing I notice very often. If you're charging the device and then you disconnect it, the device reboots suddenly.
[Samsung Galaxy Player 4.0, 5.0] txordi:
I don't know if it's only me but google search with voice dont works. It crashes every time. Without oc too.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Hmm I havent met the problem with charging, I usually charge it over night :)

I tried even now, voice search in google now works for me without any problem :)

Although it is kind of useless feature

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
I use it when i get up in the morning and I'm too lazy to write XD. But yeah, it's useless 100%
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
I don't find it to be useless. But painfully slow...

It tells me if it's gonna rain and sets my alarms for me. Well, in other words it's sort of useless :p but I like the idea of it.

My oc didn't crash yet, BTW.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Idea is nice, but it is still more practical to do it manually :)

And it doesn't work too well on crowded streets I guess.

About weather, I trust only advanced meteographs :D

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
Im catalan is absolutely useless XD. I have fixed it clearing data of the app. Maybe a backup error ;)
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
Koala is this the final thread? I saw that you started quite a lot of threads. :)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
For 4.2.2 it is second, but yes it is final thread :)

But not kernel, I still plan to do some things

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Don't know if it's kernel related or not, but I'll post it here, because same kernel - same results (in theory):

Is WIFI reception very poor on our device, or is it just mine? I have a Sony Ericsson Live With Walkman, which easily outshines my player in regards of WIFI. I get almost full speed with the cell phone whereas my player either doesn't get constant signal or downloads at 5KBps when the router isn't too near.

Are there any 3rd party fixes that I could apply? Or do I have to change the WIFI region maybe? Problem is, I live in Chile and there's no such region to choose.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I would say it is our device fault :) Even my old samsung spica was better in those terms, and nokia e52 is much better.

As for me, the closer to the router am I, the better the speed is.

Well I had never played woth wifi regions, maybe this could help :) I can add more of them I think. Also I will see if I can do anything to make wifi work better

No 3rd party apk can solve it, probably, at least no one not using root permissions

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Hollow_Ninja:
Is it dangerous to raise INT voltage to the max?
[Samsung Galaxy Player 4.0, 5.0] iurnait:
I believe that the wifi region code only affects the channels that you can connect to. For example, we cant use channels 12-14 in the US but you can in Europe or Japan
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Can be, but you device probably won't handle it, it will just reboot. 1425 should be maximum, and it should be enough for even 1,7ghz. I have to decrease max voltages.

Can be so :)

Here it is enabled that device detects wifis with low signal, so you people can have some connectivity problems with them.

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Guys! RC2 changelog :D

*3.0.82

*Build with A8 cortex optimized toolchain

*Some optimization for flags - feels smoother

*Finally found my dream governor - intellidemand, seems to be perfect for my idea of the kernel

*Update zip contains script turning off our keys backlight! From now with the minimum brightness mod you can enjoy using player at night :)

*LiveOC is abandoned! Frequencies steps are like:

CPU - GPU

15-0 - 250

1440 - 240

1380 - 230

1320 - 220

1260 - 210

1200 - 200

1000 - 200

800 - 200

400 - 200

*Overclock frequencies voltages are most probably too low, will fix it in R2 -you have to tell me too

*problems with 1500? not sure though - you have to tell me too

Downloads:

usa:

http://www40.zippyshare.com/v/22592051/file.html

intl:

http://www64.zippyshare.com/v/25726657/file.html

Big thanks to android1234567 for helping me with some stuff
[Samsung Galaxy Player 4.0, 5.0] pspfreak1:
Can you make the auto killer less aggressive? I'm not using your kernel because my keyboard would keep getting killed.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Well it is stock 3.8 lowmemorykiller :)

Never herd of such a problem, are you sure that it is kernel's fault?

You can also use apk like minfree

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
Well... For me 1500 and 1440 so much unstable. I'm having to flash one time and another all (rom+kernel+gapps) because I don't know why, but I can not move from boot animation... What could problem be? I've made a clean install and every time I'm flashing kernel I wipe dalvik cache. I'm using YP-G70CW INTL (I don't know if CW it's significative or not XD) and PAC-MAN rom. And a final question. Why do you removed liveOC?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
1500 is unstable for me too, don't use it for now. As for 1440 it can be voltage, try to increase it.

Make sure that you have unticked in nstools the thing that keeps your current settings after reboot, then it can not make device bootloop. You can also try to get to the download mode and then reboot.

I just thought that without liveoc it would be stable and wouldn't require so much work from a user. But now, I think of reverting it...

Just experimenting and so on :) But liveoc gives more personalisation.

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
I had unticked this, but I don't know why it gives me problems... I'm talking without knowing but I think that every device accepts different OC and voltages so I think that liveoc gives more opportunities to have all the power inside our galaxy players! Maybe this is wrong. Which voltage do you have? The default kernel. 1440 only gived me a reboot when I was restoring with Titanium. Have you included init.d scripts (except for the capacitive buttons)?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I use stock, my device tolerates very well low voltages :)

But, does titanium work or 4.2.2 here, or on PAC, isn't it the titanium causing problem?

No, only the one turning keys backlight off. Why do you ask?

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
With your r1 titanium didn't gave me problems. I've connected with download mode and after it wasn't still moving from boot animation :S I'll have to reflash everithing to give an opportunity to this rc2 :D My questions about init.d scripts were only for curiosity ;) It's that I want to learn about this developing stuff... Do you know any good guide? :)
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
If you accept votes, I vote for LiveOC, too :P

I can run 1,2GHz with 115% liveoc, which effectively means 1380MHz and overclocked GPU. Without LiveOC my device probably wouldn't be overclockable to more than 1,2GHz.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Always have a cwm backup :)

Best way is to lear by practic IMO, knowledge of C and java would be helpful too. But I know nothing I have done something, mostly by copy&paste but still. And now I undestand C more.

Okay, R2 will have the liveoc :)

I really like intellidemand :D

Seems like my battery is worn out, also the whole device is a litlle 'used', anf its performance isn't too good. I think it is time to upgrade :)

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
I don't know why but your rc2 is very laggy for me. I've had to return to r1...
[Samsung Galaxy Player 4.0, 5.0] KOala888:
pretty sure that's not my fault :)

I will make R2 with liveoc when I will have some time. Maybe tuesday

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
I'm sure not ;)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
ok, I will upload r2 WITH liveoc probably tommorow

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] KOala888:
So here is R2, same as RC2 but has liveoc ;)

I will update changelog later

intl:

http://www75.zippyshare.com/v/80499514/file.html

usa:

http://www55.zippyshare.com/v/12234338/file.html
[Samsung Galaxy Player 4.0, 5.0] txordi:
Wich are the GPU frequency steps?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
frequencies are same as in r1, only 1300 was replaced with 1320. Gpu is always at 200 :)

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] txordi:
Ok. Perfect! :)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
How is it for you guys?

Wysłane z mojego YP-G70 za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
Uou. Sooo much better with liveOC. Improves a lot performance from r1. For me the best 3.x.x kernel nowadays. I'm running it with PAC-MAN rom and it's going so good. I think that it's better with liveOC because every device tolerates different overclockings furthermore in gpu. Very good kernel Koala ;)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Thanks for an opinion :)

it seems like we have fewer users here or almost noone is interested in kernels :x

No idea what else could I add but I will check it. Probably a LITTLE bit more agressive lmk, sometimes it runs of of ram.

As for me works great for every day use. Our device isn't too good for gaming anyway. Finally I can use device when it is 3a.m. and that key backlight doesn't make my eyes burn :D

Wysłane z mojego YP-G70 za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
Well. I can play perfectly real racing 3! Not gta vice city, but it's so well. What rom are you using? I think with CM 10.1 would be really really fast.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Pac-man :)

I remember than real racing always hanged after X minutes. Gta III is playable, without sound and not on maximum details but still. Shadowgun deadzone was too. Max payne works very well

Wysłane z mojego YP-G70 za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
I've set up minfree and oom values to medium with pimp my rom and now i've more than 200mb free with configuration and xda app opened. It's a large amount of ram. For me rr3 works xfect always.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I highly recommend not using apps like pimp my rom :)

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
Are animations a little laggy for you? Just a little. Overall performance is better for me but i'm noticing a little laggy animations. Could be because any tweak in pimp my rom.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Nope, an should be better because of new toolchains and optimization.

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
I've only just installed your new version, but so far it feels faster than the previous one. (R1)

Vice city is playable on low details, but it's got its lags here and there.

Overall: great work of course! What would we do without you

:)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
We have to deal with it that newer games will nevet be fully playable :)

Thank you for feedback!

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
Would it be possible to add a screen rgb, gamma tuning interface?

The screen is blueish now.
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
I'm pretty sure the screen on the SGP5 is nowhere near advanced enough for that
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Well I would love to.

I haven't touched anything related to display of colours so it can't be kenel's fault :)

Exacly, same here.

At least I haven't seen any kernel for device with tft that allowed to mess with that stuff.

Maybe I could hardcode some changes.

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
It is possible on Nexus 4 which is also TFT, that'd why I asked.;)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Nexus 4 is IPS and is only available because google left the code to do so. :p
[Samsung Galaxy Player 4.0, 5.0] txordi:
I think that with GB wi-fi went me better. I've to be very near of the router to have a decent connection. I don't know if it's a question of volting or drivers or some stuff but something doesn't go fine at all I think. With your kernel and with all the other 3.0 kernels too. Has anybody noticed this? Maybe it is only my impression, but I readed something similar before.

Edit: Powering of the wi-fi battery saver, deleting the init.d script generetad by pim my rom and restarting wifi and the device i get better connection. Not so much, but it's noticeable ;)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
well its IPS :)

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
I think that a little more strict lowmemory killer would be good. I think I have too much apps running in the background for our 440mb of ram...

Enviat des del meu YP-g70 utilitzant Tapatalk 4 Beta
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
In the very bottom of the developer options in settings let you decide how many apps are staying in the background.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
yeah, I will do something with it, I feel lagginess when too much apks are in background

Wysłane z mojego Nexus S za pomocą Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] txordi:
But I think it's only for user apps, not system apps. Could be?

Enviat des del meu YP-g70 utilitzant Tapatalk 4 Beta
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Minfree manager moderate settings are working pretty well for me on remics jb ROM. Because if lmk is set too strict, apps keep restarting all the time, which slows down everything.
[Samsung Galaxy Player 4.0, 5.0] alanwyl:
It says background process, I'm not really sure.
[Samsung Galaxy Player 4.0, 5.0] txordi:
Only a very little and useless thing. In your updater-script at the first line, i think you can change rc2 for r2, for not giving confussions ;)

Enviat des del meu YP-g70 utilitzant Tapatalk 4 Beta