yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] jenzy1985:
What working and not ? Thanks for your work

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
currently i'm fighting against fu**ed up encryption of /data partition - i stuck on the UI screen "Encryption unsuccessfull" and RIL isnt working (so no GSM/mobile Data), all other is working as i can see in logcat. No more errors :)

Means: the next week i have my christmas holiday and a lot of time to fix things ... maybe AOSP 4.2 can be flashed soon and on Christmas :D
[Galaxy S III Q&A, Help & Troubleshooting] FadeFx:
Andy, are u in contact with codeworkx? It looks like Daniel has a working build as well, probably you should combine tour efforts, so the wheel has not to be invented twice...

_________________________

tapatalked from GalaxyS
[Galaxy S III Q&A, Help & Troubleshooting] fakpuppet:
Exactly, not to mention the collaborative amplification of creativity between all of you guys.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
I know all about that - codeworkx and me was writing for a few days here - he was some faster as me to publish most Exynos4 Fixes to

CM gerrit ;) Its not a challenge, i dont care about that.

BTW: some fixes are to work with CM 10.1, but some fixes aren't usable in pure AOSP because some things are different in AOSP.

This is as example the complete stagefright media framework - so if i can use my patches for graphic problems in AOSP, it dont must be

work in CM 10.1 too - CM 10.1 was re-enabling PMEM and VSYNC (even to support older devices without ION functions) and isnt using ION

at all, in my AOSP port for the i9300 i dont want to integrate old code ;)

On a some later point if all is running and working as expected we can see what patches is better - i dont have a problem to integrate

Patches from CM 10.1 to AOSP if its better code.
[Galaxy S III Q&A, Help & Troubleshooting] Mika83AC:
As long as u and the CM team are working together and share your knowledge and discoverys to fix this exynos crap, you're heros for us all :good: :D
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Gold star dude, gold star

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Here you go, a first shoot of our i9300 with Android 4.2 :) :) :)

https://plus.google.com/photos/113497568998430777435/albums/5818536448394326129
[Galaxy S III Q&A, Help & Troubleshooting] vinaybaboo:
That's reall great. But why is the internal memory showing 128MB???
[Galaxy S III Q&A, Help & Troubleshooting] Skander1998:
Bugs are expected i guess.. or maybe he is running it on a separate partition?
[Galaxy S III Q&A, Help & Troubleshooting] sharingan92:
@andy572 i think this is the problem i was telling you about caused by the new infrastructure in 4.2 so a older recovery will mess it up could you try flash it with the newer 6.0.1.9 recovery i uploaded to see if it fixes the problem

Recovery link:

http://xdaforums.com/showthread.php?p=35039672

im what Willis was talking about
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
yesterday i've tryed to flash it with 6.0.1.9, but got errors about wrong symlinks in the installer script- dunno why, on my current recovery with (some old) 5.0.x version i dont got that ... do you have a idea?
[Galaxy S III Q&A, Help & Troubleshooting] gavin-phelan:
Is it usable yet?
[Galaxy S III Q&A, Help & Troubleshooting] FCB-Fan:
If it would be useable, i'm sure that it would be running at my device, too ;)

Gesendet von meinem GT-N8000
[Galaxy S III Q&A, Help & Troubleshooting] gavin-phelan:
Lol
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Just figured out the problem: the storage is changed (dont know why). i can see a storage icon on my windows when connected and it is

the internal memory, but not with the system installed but with /data :D

OMG ... what is the problem here? Can it be the new implemented "fuse" ****?

### EDIT this are the actual mounts, but all seems ok???!!!

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
tmpfs /data tmpfs rw,nosuid,nodev,noatime,size=131072k,mode=771,uid=1000,gid=1000 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:17 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Galaxy S III Q&A, Help & Troubleshooting] sharingan92:
Did you use the recovery i uploaded or philz recovery? As philz modified 6.0.1.9 recovery may have broken some things when he was adding features and mine is just pure CWM so it might work it might not we will have to see if your OK with testing it with my recovery

im what Willis was talking about
[Galaxy S III Q&A, Help & Troubleshooting] Raz1911:
Gud work :):good:
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Sorry, i dont know what special version it was, but i cant flash a rom with that - not AOKP 4.1, nor AOSP 4.2 ... for both the ROMs the recovery

says "symlink error" and ended with status (7). Later when i'm back from my job i'll try the recovery you posted, then i'll see if its a difference :)
[Galaxy S III Q&A, Help & Troubleshooting] adityaxavier:
Hey Andy, Try checking the values provided in the init.smdk4x12.rc.

Fuse is supposed to adhere to it.
[Galaxy S III Q&A, Help & Troubleshooting] d4c:
Brilliant, well done guys and gals :)
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Values are checked, but some mount settings seems mis-configured, i'm some confused about the new storage system:

the i9300 devices have 1 internal storage, and a SDCard slot.

in the init.smdk44212.rc file provided by CM 10.1 there is some more configured: a device called usbdisk0 and is symlinked

to /mnt/extSdCard and /mnt/sdcard1 ... i dont understand that: is it the UMS device label to show the storage without the needs of MTP?

I had a bug in the default init.rc provided by the downloaded AOSP sources too: /data/dalvik-cache directory has the right permissions

with 0771 system system but it was not allowed by some init *.c files, so i has added them :D ... seems like google is missing some

correct code in Android 4.2 :D
[Galaxy S III Q&A, Help & Troubleshooting] adityaxavier:
Hmm, well for one, usbdisk should not be symlinked to /mnt/sdcard1.

I believe the symlinks as per cm10 are accurate :-

symlink /storage/sdcard0 /sdcard

symlink /storage/sdcard0 /mnt/sdcard

symlink /storage/sdcard1 /extSdCard

symlink /storage/sdcard1 /mnt/extSdCard

symlink /storage/usbdisk0 /usbdisk0

symlink /storage/usbdisk0 /mnt/usbdisk0

and fuse settings :-

on fs

mount_all /fstab.smdk4x12

setprop ro.crypto.fuse_sdcard true

chown radio system /efs

chmod 0771 /efs

on post-fs-data

# we will remap this as /mnt/sdcard with the sdcard fuse tool

mkdir /data/media 0775 media_rw media_rw

chown media_rw media_rw /data/media

Frankly google is making huge blunders which i guess due to time crunch to release a new os out of the stable. The whole December issue was really embarrassing.
[Galaxy S III Q&A, Help & Troubleshooting] gavin-phelan:
Hope this will be released soon and cracking up having to use my galaxy nexus :P
[Galaxy S III Q&A, Help & Troubleshooting] SUer:
This is a development thread you tool and comments about how much you want something are utterly irrelevant. Give it a bloody rest will you? I'm sick of reading how much you want something.
[Galaxy S III Q&A, Help & Troubleshooting] gavin-phelan:
Pointless
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Your posts in this thread in a nutshell.

For the mods: I know this is a development thread, I just want to silence him.
[Galaxy S III Q&A, Help & Troubleshooting] FCB-Fan:
There is a 4.2.1 ROM from Daniel (codeworkx) now, so you can maybe look how he fixed some things(like GSM and Wifi) or steal some files ;)

Gesendet von meinem GT-N8000 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] SignalX:
+1

would be great if you combine something to make GSM works

really wait for your build too

thanks
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
i've read about that unofficial release, but as i wrote: for AOSP most libs/jars are useless - CM isnt AOSP :)
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
I wonder if this kings of project going to force Samsung to release source codes. Dont see it happening though
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Lol, how can you "force" them to do that? They're not obligated to

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Toss3:
Please don't turn this thread into another one about samsung not releasing sources. We already have one for that.
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Sorry ..
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Some news on Sunday:

Today i tried to figure out, why AOSP on i9300 is so very strange buggy... and found some things :D

- dalvik is configured for new devices only, but mostly the same code as in CM 10.1 running (but a view lines of comments and downward compat to ARMv6)

- system/core is almost the same but some less libs as in CM 10.1

- hardware/libhardware is pure Google, i have included Exynos4 support only

Why the Hell i get strange behaviors like mount and permission problems??? I dont understand that - i used ALL device configs and latest proprietary libs from CM 10.1???

Ok, i think the problem only can depend on libcore (android runtime) ... now i recompile the system with libcore from CM 10.1 and will see if its running well ;)
[Galaxy S III Q&A, Help & Troubleshooting] UltrasFrankfurt:
Good Luck bro, gutes Gelingen :D

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
some days later ...

device stuck on "Encryption unsuccesfull" screen message, RIL (gsm) isnt working ... seems as Google is only supporting

devices with only internal memory and RIL version 7 - i9300 is another version :(

To be some clear:

- the boot process is broken: init is mounting all things, than its calling our init.smdk4412.rc - some too late of this point as we need to do some things

in the "/system" file system before it gets in "read only" state

- internal memory cant be mounted in init.smdk4412.rc via the sdcard command - if i doing that manually with same args in adb it works nice, but without visible data

- mount point of internal memory isnt /sdcard, /sdcard0, /mnt/sdcard nor /mnt/sdcard0 - and even not in /storage/sdcard blahhh

- RIL cant find a device node, even if its all set to 0666 and "radio radio" user/group ... i only get a "permission denied" even if i'm root :D

So, if someone have a idea how to solve that things, write here - any help is welcome :)

But, i hope to find a solution for that crap - the next days i write here if i can use that sh*t of code *ggrrrrrr*
[Galaxy S III Q&A, Help & Troubleshooting] Zekene:
Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Ha ha ... CM isnt AOSP ... i sayed it many times: to get AOSP running its some more difficult than fix only two or three drivers for hardware ...

BTW:

Audio, GSM, SIM-PIN-Unlock and NFC is now working, next step is bluetooth, storage and Camera problem.

If its solved (i hope the next days) we see us with AOSP 4.2.1 here again - i'm still working on it, no panic my friends :)
[Galaxy S III Q&A, Help & Troubleshooting] digkong:
Does your build also have distortions in animations like in cm10.1..??

Is it smoother..??
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Well it will be first build, so of course there will be some bugs.

Btw does the development continue during christmas?
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
yes, it continues :)
[Galaxy S III Q&A, Help & Troubleshooting] apollag:
One of those many who are waiting. (excited):rolleyes:
[Galaxy S III Q&A, Help & Troubleshooting] salvatore94:
Great! And it seems that xploid fixed camera crashing. Maybe his fix works also on aosp roms.

What is the problem with storage? Isn't the same mountpoints of jb 4.1?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Mika83AC:
No, ramfs has changed from 4.1 to 4.2.
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Any Updates on Progress? Just interested
[Galaxy S III Q&A, Help & Troubleshooting] g0t-cheeri0s:
Umm... Read the thread. There's posts from the dev within the last 24 hours. Geez.

Edit: It seems there is quick progress being made (see post below). Apologies Mrboxfacetramp.

Sent from my 4.2 i9300
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently i try again to solve that Encryption problem on internal storage system in Android 4.2:

1) changed my recovery from Touch CWM 6.0.1.9 to CWM 6.0.2 (as used with CM 10.1) without touch, released by Koush -> problem not solved

2) Tried the CM 10.1 boot.img to test, if its my ramdisk -> problem not solved, so the problem isnt the new generated ramdisk or kernel

3) changed bouncycastle and openssl and compiling again to see, if its a internal encryption error -> outstanding, just doing that ;)
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Great progress I'm currently running the CM10.1 but if you want I can test it when you release a tester
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
A step forward now: internal storage and UMS / Mass Storage now working nice :)

https://plus.google.com/u/0/113497568998430777435/posts/GkXgMCMqgcy
[Galaxy S III Q&A, Help & Troubleshooting] SignalX:
so great,

thanks for your effort on this project

waiting for an aosp release
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Does your ROM share similar issues as CM10.1
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently i cant say a lot about the CM 10.1 issues, because both of ROM types are in early development stage.

In the next days, i hope to provide a mostly stable rom - but bugs can occure - Android is in daily development, so

lets see what we can do the next weeks or months ;)
[Galaxy S III Q&A, Help & Troubleshooting] kobz1973:
Looking forward to this
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
How far is the development from publishing?
[Galaxy S III Q&A, Help & Troubleshooting] Skander1998:
When you stop asking for ETA's.
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Okay, let me rephrace.

How's the development going?
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Read the thread ;)
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
ETA, ETA ... why some users asking almost every day for ETA?

Let me explain something for that:

Even a developer does have a RL, in some cases a family too and the development is often a hobby only for most of us.

This means, we dont develop a lot of hours and yes, we're going out and do things what others are doing too - in my case, i sit on my Notebook a few hours only,

after a RL job, mostly in the evening when my family is sleeping well ;)

So as result, i cant spend all my time to this ROM - not even i if want to do this: my girlfriend is killing me :D

To answer:

I think the next week (no, i cant say a special date) i can release a early alpha version so users can play around with Android 4.2 :)
[Galaxy S III Q&A, Help & Troubleshooting] d4c:
Totally agree with Dev. This guy has a life outside of this forum and the rom he is creating. Lay off the guy and give him a break, it will be done when it's done.
[Galaxy S III Q&A, Help & Troubleshooting] IntenseTorture:
Great Going Guys! Would love to see the 4.2 on my phone as soon as possible. I will be the first to test it once it comes out. Thanks again for all your efforts
[Galaxy S III Q&A, Help & Troubleshooting] Toss3:
Why not just install CM10.1 then in the mean time?
[Galaxy S III Q&A, Help & Troubleshooting] Meemo23:
This is what exactly all dev try to explain but people just want, want and want. Never think for a second that the Dev has a life..

Great work mate keep us updated when ever you have the time peace..
[Galaxy S III Q&A, Help & Troubleshooting] fakpuppet:
Spot on. And even of he doesn't, which is a possibility, we should at the least give a dev a chance of getting one. On the other hand if a dev has a life - a dev has a life. Though sad it's still a blatant fact. You shouldn't be jealous. His girlfriend is probably infinitely sexier than you - the user - and willing to do things for free you are not even for this ROM.

Sent from my GT-I9300
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Currently adopting several Patches to skia graphics library from 0xlab ... known from best gingerbread ROMs - ICS/JB arn't supported/developed anymore, but the

nice NEON CPU and GPU optimizations are still there and can be included in our builds :)
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Both Cameras are now working, needs minimal bugfixing :)

At last: i have to fix a strange bug: we can't make calls, but without a screen ... screen goes black and never comes back - this makes the phone unusable :(
[Galaxy S III Q&A, Help & Troubleshooting] UrbanDrawer:
Deleted
[Galaxy S III Q&A, Help & Troubleshooting] FadeFx:
Iirc 5ge black screen problem was also present in early cm10.1 development, maybe you can take a look at their sources to find a fix, i guess it has to do with proximity sensor polling, but that's just my guess...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Q&A, Help & Troubleshooting] :
I don't think its proximity sensor as on the cm forum I suggested that and even disabling the proximity didn't help

Although it still could be
[Galaxy S III Q&A, Help & Troubleshooting] Oweida:
Internal memory

Hi Andy ...

Great job.

Would you mind telling me what did you do to fix the internal storage issue ?!
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Internal/external storage can simply fixed with "vold" from cm-10.1 repo, a working init.smdk4412.rc and patches from frameworks base

to provide UMS Mass storage :)

@Black screen when calling:

its caused by a "sip" Java class - never activated, currently dunno why its active ^^

# EDIT ###

Found some Phone app fixes for Proximity sensor from JB 4.0, currently trying that to solve the last big problem before i release the first (some unstable)

version of AOSP 4.2.1 :D
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Great Work

:cowboy:
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Update to Android AOSP 4.2.1 is almost finished, today i fixed mostly phone and gsm bugs so now we can make and take calls.

Last todos before i publish the new ROM:

- fix bluetooth (if its not fixed until release date on saturday/sunday, it doesnt matter i think)

- fix video bugs

- fix audio bugs

- test the whole device functions

Have a nice day/afternoon/evening :)
[Galaxy S III Q&A, Help & Troubleshooting] :
I've been patiently watching this thread, and can't wait to try out your hard work. Well done mate, looking forward to the release :)
[Galaxy S III Q&A, Help & Troubleshooting] onurerler:
+1
[Galaxy S III Q&A, Help & Troubleshooting] erto90:
Let me understand : camera is fine also using flash +touch to focus?
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Touch to focus is working without patches, seems CM has a bug in a modification :/

- Video recording and panorama feature is crashing the camera app, needs to be fixed.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Does someone know about that MP4 things? Specially: why a camera recorded movie can be green colored and distored?

I dont know if its a color conversion issue or a really software issue (e.g. needs another driver or so?)
[Galaxy S III Q&A, Help & Troubleshooting] erto90:
I mean, in cyanogen touch to focus is ok,but if you use touch to focus with flash enabled..it crash at first attemp..

Is herr "solved"?
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
Have you tried using the CM Gerrit and see if that helps and then work from there. I know this is meant to be aosp but you can see if that works.

:cowboy:
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
can you point me to a commit in gerrit please?
[Galaxy S III Q&A, Help & Troubleshooting] TheUnkn0wn:
https://github.com/CyanogenMod/android_packages_apps_Camera/

or

http://review.cyanogenmod.org/
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Here ya go: first release is ready to test :)

### ATTENTION ### WARNING ### PLEASE READ BEFORE INSTALL

This ROM isnt ready for daily use. Do not expect a fully working smartphone when flashed this software.

Known bugs/issues:

- NO SMS/MMS can be received or send (RIL isnt fully patched at the moment of this release)

- NO movie can be recorded (recorded movies have distorted green frames only, sound works)

- NO movies can be played: so Youtube apps and others arent fully working (OMX needs patched, nothing found to fix that currently)

- Bluetooth and NFC isnt working for now, needs to be fixed

- JB compatible apps can have lags when scroll through list views, better use apps for JB - they have new implemented code and working fine

- NO code is optimized, so you can have lags or crashes at all around your device

/********************************************************************************************************

*

* !!!!! DO NEVER INSTALL GAPPS FROM CM-10.1 ---- ITS NOT WORKING WITH AOSP !!!!! (needed GApps are included with this rom)

*

********************************************************************************************************/

All other should work fine :D

### INSTALLATION ###

1) Install the ~~~latest~~~ recovery (i use the CWM 6.0.1.2 at this time), install it with ROMManager (free market version is enough)

2) Flash the downloaded ZIP file

3) Wipe ALLLLLLL - Dont use Backups, its not working at all - please reinstall your things as needed!

4) reboot your phone

5) Enjoy the first AOSP alpha version on your device :)

Download:

i9300-AOSP-JOP40D-rc0.zip

Please, do not share this URL - its a testing version only and not stable.

You can post here for mirrors, thats OK :)

Have nice X-MAS days, get a lot of nice gifts and, at last: we see us here again with a mostly fixed and better

ROM and a new opened message board thread the next time - i cant say when, i think after the X-MAS days :)

Greets from Munich, Germany

Andy
[Galaxy S III Q&A, Help & Troubleshooting] rock4hell:
downloading
[Galaxy S III Q&A, Help & Troubleshooting] Tenacious:
Thanks Andy.

Happy Xmas to you to.
[Galaxy S III Q&A, Help & Troubleshooting] andy572:
Youtube working fine in next release :)
[Galaxy S III Q&A, Help & Troubleshooting] Mrboxfacetramp13:
If only the messaging was stable then I would probably try this.
[Galaxy S III Q&A, Help & Troubleshooting] d4c:
Good work Andy, keep up the good work and have a good Christmas yourself. May try this rom in the future when it is stable enough. In the mean time how can I help you? Donation etc?
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
So.. Someone died or something?

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
No......someone just needs to read the thread ;)
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Never said Andy died, but there used to be lots of other people chattin n whatever.. Maybe i just something in this awfully big thread

Skickat från min GT-I9300 via Tapatalk 2