yashsingh1/xdaforums huggingface dataset:
[HD Mini Android Development] munjeni:
I think problem with: camera (jpeg), youtube (high def video) , but all working (output way), but not working (input way), is becouse we have something wrong with user space (maybe problem with permisions!), or maybe need corection for memory mapping!

I've tried to fix cammera, and I know bug is inside when camera catcing picture from jpeg task (input way not working, but output way working). Also, I know when youtube catching "high def video" (input way), something is not ok with "codecs" or "user space" or "memmory map"... maybe you have idea?

I think fixing cam bug will fix all (youtube...etc)

EDIT:

See this:

<6>[ 194.615801] adsp_pmem_add module JPEGTASK vaddr:0x41ffc000 paddr:0x26c12000 len:524288

Why len is 524288? Picture have size > 3-4M, maybe it cause problem with jpegtask verify??
[HD Mini Android Development] derefas:
about video and youtube problem in codecs

about camera problem in memory map
[HD Mini Android Development] munjeni:
I think problem is in msm_adsp.h, adsp.c, adsp.h and adsp_photon.c

something is not ok there (I think wrong in adsp_photon.c != msm_adsp.h!) becouse I see in dmesg from int adsp_video_verify_cmd() warning about "unknown video queue"... from code:

int adsp_video_verify_cmd(struct msm_adsp_module *module,
unsigned int queue_id, void *cmd_data,
size_t cmd_size)
{
switch (queue_id) {
case QDSP_mpuVDecPktQueue:
DLOG("\n");
return verify_vdec_pkt_cmd(module, cmd_data, cmd_size);
default:
printk(KERN_INFO "unknown video queue %u\n", queue_id);
return 0;
}
}

and from it I know QDSP_mpuVDecPktQueue is not used, so I think we have problem in adsp_photon.c and need to realign it like defined in msm_adsp.h!!!

I dumped something, maybe help here:

<4>[ 0.972350] adsp: module name=AUDPLAY0TASK, module id=2, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_AUDPLAY0TASK, pdev id=-1, id_to_module=e4979000
<4>[ 0.972588] adsp: module name=AUDPPTASK, module id=7, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_AUDPPTASK, pdev id=-1, id_to_module=e4979148
<4>[ 0.972741] adsp: module name=AUDRECTASK, module id=19, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_AUDRECTASK, pdev id=-1, id_to_module=e4979290
<4>[ 0.972886] adsp: module name=AUDPREPROCTASK, module id=20, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_AUDPREPROCTASK, pdev id=-1, id_to_module=e49793d8
<4>[ 0.973040] adsp: module name=VFETASK, module id=31, mod clk=vfe_clk, verify cmd=c0143330, patch event=c01437f4, pdev name=adsp_VFETASK, pdev id=-1, id_to_module=e4979520
<4>[ 0.973183] adsp: module name=QCAMTASK, module id=43, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_QCAMTASK, pdev id=-1, id_to_module=e4979668
<4>[ 0.973330] adsp: module name=JPEGTASK, module id=42, mod clk=vdc_clk, verify cmd=c0142f0c, patch event=c01432d4, pdev name=adsp_JPEGTASK, pdev id=-1, id_to_module=e49797b0
<4>[ 0.973568] adsp: module name=VIDEOTASK, module id=9, mod clk=vdc_clk, verify cmd=c01429c0, patch event=0, pdev name=adsp_VIDEOTASK, pdev id=-1, id_to_module=e49798f8
<4>[ 0.973713] adsp: module name=VDEC_LP_MODE, module id=48, mod clk=<NULL>, verify cmd=0, patch event=0, pdev name=adsp_VDEC_LP_MODE, pdev id=-1, id_to_module=e4979a40
<4>[ 0.973901] adsp: module name=VIDEOENCTASK, module id=30, mod clk=vdc_clk, verify cmd=c0142bd8, patch event=0, pdev name=adsp_VIDEOENCTASK, pdev id=-1, id_to_module=e4979b88

And yes, cammera jpegtask have problem with memory map, but video have problem in adsp!
[HD Mini Android Development] derefas:
may be ,video with another player with codecs work good
[HD Mini Android Development] derefas:
http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/blobs/htc-msm-2.6.27/arch/arm/mach-msm/pmem.c

this file had camera pmem calc

i think this is help with with

NOTE: need edits in devices_htc.c/.h

NOTE2: Camera Snapshot work only in Fast Burst Camera
[HD Mini Android Development] munjeni:
Ok I will try! Please see this -> http://xdaforums.com/showpost.php?p=16448252&postcount=4
[HD Mini Android Development] lucainrussia:
camera

Hi !

sorry for my English, but someone has a solution for a problem with camera in hd mini ? I try the android r134 FANTASTIC, but no photos :( some one can help me?

tanks
[HD Mini Android Development] codiak:
No reason do make doubbleposts.

As you can see in this thread, they are working on it.

Its still "under construction"
[HD Mini Android Development] derefas:
something interesting from strace

writev(3, [{"\4", 1}, {"GPhoto\0", 7}, {"Sd-card availableSize = 5673\0", 29}], 3) = 37
syscall_983042(0x43904738, 0x4390473c, 0, 0x4390473c, 0xaca8c3f4, 0x438f70cf, 0x434, 0xf0002, 0, 0x40041858, 0xcd80, 0xbe9e4700, 0, 0xbe9e43f0, 0xaca64fc7, 0xafd0ec8c, 0x8000010, 0x43904738, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0

recv(52740, 0x80, 4294966774, MSG_WAITALL|MSG_TRUNC|MSG_DONTWAIT|MSG_PROBE|MSG_FIN|MSG_NOSIGNAL|0xbe9e0000) = -1 ETIMEDOUT (Connection timed out)
[HD Mini Android Development] munjeni:
TIMEDOUT !! I don't know where is timedout, hmmm FUTEX??? Also I seen in dmesg always diferent size in bank_1 but it's defined static !!
[HD Mini Android Development] derefas:
this adress 0xbe9e0000 don't responding
[HD Mini Android Development] munjeni:
I found something! Curently error come from msm_camera.c (see dmesg.log) "msm_put_stats_buffer: NULL physical address"!!!

Two functions:

first:

static int msm_put_stats_buffer(struct msm_sync *sync, void __user *arg)
{
int rc = -EIO;

struct msm_stats_buf buf;
unsigned long pphy;
struct msm_vfe_cfg_cmd cfgcmd;

if (copy_from_user(&buf, arg,
sizeof(struct msm_stats_buf))) {
ERR_COPY_FROM_USER();
return -EFAULT;
}

CDBG("%s\n", __func__);
pphy = msm_pmem_stats_vtop_lookup(sync, buf.buffer, buf.fd);

if (pphy != 0) {
if (buf.type == STAT_AEAW)
cfgcmd.cmd_type = CMD_STATS_BUF_RELEASE;
else if (buf.type == STAT_AF)
cfgcmd.cmd_type = CMD_STATS_AF_BUF_RELEASE;
else {
pr_err("%s: invalid buf type %d\n",
__func__,
buf.type);
rc = -EINVAL;
goto put_done;
}

cfgcmd.value = (void *)&buf;
if (sync->vfefn.vfe_config) {
rc = sync->vfefn.vfe_config(&cfgcmd, &pphy);
if (rc < 0)
pr_err("%s: vfe_config error %d\n",
__func__, rc);
} else
pr_err("%s: vfe_config is NULL\n", __func__);
} else {
pr_err("%s: NULL physical address\n", __func__);
rc = -EINVAL;
}

put_done:
return rc;
}

In second function I added (see dmesg.log!) printk, and I see vaddr and buffer addr sometimes is ===, sometimes !== so it need to be fixed but hmmm where??? I not have idea :confused: , maybe you have idea:

static unsigned long msm_pmem_stats_vtop_lookup(
struct msm_sync *sync,
unsigned long buffer,
int fd)
{
struct msm_pmem_region *region;
struct hlist_node *node, *n;

hlist_for_each_entry_safe(region, node, n, &sync->pmem_stats, list) {

printk("ADSP TEST: region->info.vaddr(0x%08lx)==(0x%08lx)buffer, region->info.fd(%d)==(%d)fd, region->info.vfe_can_write(%d)==0\n",
((unsigned long)(region->info.vaddr)), buffer, region->info.fd, fd, region->info.vfe_can_write);

if (((unsigned long)(region->info.vaddr) == buffer) &&
(region->info.fd == fd) &&
region->info.vfe_can_write == 0) {
region->info.vfe_can_write = 1;
return region->paddr;
}
}

return 0;
}

As you see some memory regions is not writeable becouse region->info.vaddr !== buffer
[HD Mini Android Development] derefas:
i don't think so

i think problem in s5k4e1gx.c

{ /*Snapshot*/
0x06, /* pre_pll_clk_div REG=0x0305 */
0x00, /* pll_multiplier_msb REG=0x0306 */
0x50, /* pll_multiplier_lsb REG=0x0307 */
0x00, /* vt_sys_clk_div REG=0x30B5 */
0xB0, /* DPHY_bandctrl REG=0x30F1 */
0x00, /* read_mode REG=0x0101 */
0x0A, /* x_output_size_msb REG=0x034C */
0x30, /* x_output_size_lsb REG=0x034D */
0x07, /* y_output_size_msb REG=0x034E */
0xA8, /* y_output_size_lsb REG=0x034F */
0x01, /* x_even_inc REG=0x0381 */
0x01, /* x_odd_inc REG=0x0383 */
0x01, /* y_even_inc REG=0x0385 */
0x01, /* y_odd_inc REG=0x0387 */
0x03, /* h_binning REG=0x30A9 */
0xE8, /* v_binning REG=0x300E */
0x07, /* frame_length_lines_msb REG=0x0340 */
0xB4, /* frame_length_lines_lsb REG=0x0341 */
0x0A, /* line_length_pck_msb REG=0x0342 */
0xB2, /* line_length_pck_lsb REG=0x0343 */
0x10, /* pclk_inv; REG=0x3110 */
0x0C, /* pclk_delay; REG=0x3117 */
0x0A, /* v_h_strength; REG=0x3119 */
0xAA, /* data_pclk_strength; REG=0x311A */
0x82, /* cds_test	REG=0x300F */
0xC0, /* rst_offset1	REG=0x3013 */
0xA4, /* rmp_init	REG=0x3017 */	/*0x94*/
0x88, /* comp_bias	REG=0x301B */	/*0x71*/
0x00, /* analogue_gain_code_global_msb REG=0x0204 */
0x80, /* analogue_gain_code_global_lsb REG=0x0205 */
0x07, /* coarse_integration_time_msb REG=0x0202 */
0xA8, /* coarse_intergation_time_lsb REG=0x0203 */
1960, /* size_h */
12, /* blk_l*/
2608, /* size_w*/
130 /* blk_p*/
}
};

or may be

static int msm_divert_snapshot(struct msm_sync *sync,

in msm_camera
[HD Mini Android Development] munjeni:
Ok maybe! But as you see region->info.vaddr !== buffer ...some offsets differs there and I don't know what cause it or where I need to search:confused: Maybe haret not cleaned completely some memory regions?
[HD Mini Android Development] derefas:
i try to research diffs in leo kernel

only find time fix
[HD Mini Android Development] munjeni:
Maked some tests and I confirm we have problem in queue_id and it need to be fixed in photon_adsp.c or msm_adsp.h... see dmesg with latest kernel from munjeni release thread... I tried video and camera and got "adsp_video_verify_cmd: unknown video queue 4" and in jpeg_verify "-1" !!! So one queue step fail or maybe array of the queues (or array of the module offsets) in adsp_photon.c or msm_adsp.h need to be realigned! I think it cause audio loop and video freze in youtube becouse wrong queue (wrong module used), allso cause problem in video capture! With new memory map I got youtube to "not freze" but could not stop audio and no high def video... please see commit http://gitorious.org/2-6-32-photon/testing/commit/e3121b4083068760fc33a277e10c049a4054840d you will see QDSP_uPJpegActionCmdQueue is not used!
[HD Mini Android Development] derefas:
i think value for camera 22 - 23

because logcat have error with 22 ioctl

QDSP_uPJpegActionCmdQueue with 22 value you can find in leo source msm_adsp
[HD Mini Android Development] munjeni:
Maybe asking help from Cianogen to support our phone becouse it's related to rpc and we not have that knownledge, it is hard to fix without .pdf specification for our phone!
[HD Mini Android Development] derefas:
problem with resolution, in fast burst camera with large buffer and 1280x760 all good in android camera problem with buffer ,

the first what can be a problem : auto-focus wrong offset

the second : buffer with very high resolution too large and pmem don't have needed size

the third : problem with ioctl
[HD Mini Android Development] munjeni:
Hmmm, bufer, we see it in youtube and high def video, pmem, also seen in dmesg, but it is hard to understand where is exactly problem becouse we are amaters and not profesionals. I think we need to involve to our project some profesionals like Cianogen to support our phone, maybe asking him and donating him? I see 50% of the kernel code (50% functions and class) have disabled log mesage and we not see his execution in dmesg.log... so I think we need luck to get fix for camm and video
[HD Mini Android Development] wilcoo:
I just installed GeoGoggle. With this app you can make some (lowres.) pictures. He saves the pictures at sdcard/DCIM/Camera. Maybe this can help you devs to solve the problem....

When you already knew..... then ignore this post ;)
[HD Mini Android Development] munjeni:
I could not download it and got message: This app is incompatible with all of your devices. Searched google for other link without success:mad:
[HD Mini Android Development] wilcoo:
That's strange. Maybe you tried it with another Android than I did (I have the latest Photon release). If not then you should do a fresh/new installation, same as I did. For me it solved some problems I did not have in a previous version:D
[HD Mini Android Development] DmK75:
Strange :confused:
[HD Mini Android Development] youkid90:
maybe you should uninstall sd card first ,then you can install GeoGoggle.
[HD Mini Android Development] munjeni:
Thanks for info, camera working in geogog**e:eek: so I will try something and I know problem is not in rpc server:D
[HD Mini Android Development] munjeni:
What release you use I don't understand:)
[HD Mini Android Development] DmK75:
I think Geogoogle works because this app make simple screenshot :D

But not used camera function as usual.

-----

Yes, it's right - installed screenshot app and tested.
[HD Mini Android Development] pietje63:
Agree, same applies to barcode readers, these work as well.
[HD Mini Android Development] munjeni:
I don't know why but I see in dmesg camera use ADPPTASK, why, I not know why
[HD Mini Android Development] derefas:
for camera click sound
[HD Mini Android Development] munjeni:
yes you are right:) I changed msm_adsp.h, changed order in queue_id:

#define QDSP_uPJpegActionCmdQueue 22

#define QDSP_uPJpegCfgCmdQueue 23

#define QDSP_uPJpegFTMActionCmdQueue 20

#define QDSP_uPJpegFTMCfgCmdQueue 21

and now I not have jpeg verify failed, camera shoot not working, but sd card is very very hot (42 c) and I must to remove battery. I see in dmesg adsp waiting to write :confused: Maybe permisions?

EDIT:

hmm maybe need to change offsets here also... will try:

0x168, /* QDSP_uPJpegActionCmdQueue */

0x164, /* QDSP_uPJpegCfgCmdQueue */

0x118, /* QDSP_uPJpegFTMActionCmdQueue */

0x114, /* QDSP_uPJpegFTMCfgCmdQueue */

int adsp_jpeg_verify_cmd(struct msm_adsp_module *module,
unsigned int queue_id, void *cmd_data,
size_t cmd_size)
{
switch (queue_id) {
case QDSP_uPJpegCfgCmdQueue:
printk("jpeg verify: cardsharing-x let see if QDSP_uPJpegCfgCmdQueue === queue_id=%u\n", queue_id);
return verify_jpeg_cfg_cmd(module, cmd_data, cmd_size);
case QDSP_uPJpegActionCmdQueue:
printk("jpeg verify: cardsharing-x let see if QDSP_uPJpegActionCmdQueue === queue_id=%u\n", queue_id);
return verify_jpeg_action_cmd(module, cmd_data, cmd_size);
default:
printk("jpeg verify: cardsharing-x returned -1 becouse queue_id=%u\n", queue_id);
return -1;
}
}
[HD Mini Android Development] munjeni:
Yes, I changed offsets and... Guys, camera working perfect with all resolutions!!!:D Now I go to fix video:)
[HD Mini Android Development] draltus:
Many thanks for excellent work. this is great news.
[HD Mini Android Development] DmK75:
Thanks, you are great coder :D
[HD Mini Android Development] kndlsz:
Thanks for your great works, looking forward to your vedio-fixed works.:)
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
As promised guys, there you go!, first release for you!, please download from

Here - http://xdaforums.com/showthread.php?t=1122455

Why still dont works?, because we need your help, but ROM Manager part it's ready

1. Edit this lines on build.prop, for all ROMS that you want be recognized

ro.build.id= -> Only double number here, should correspond with rom manager format (please not GRJ22 or v1.4.5.1, that will make ROM Manager throw error)

ro.modversion= -> The same name that rom have on ROM Manager repo, no spaces Please

2. Also we need repo list, you can generate with this tool, if you need help, tell me

REPO FORMAT:

romname(should be the same from ro.modversion, with no spaces);directUrl;Changelog:, ,separed,by,commas,without,*,or,-, ,Author(not by bla, only author name);MD5;lastVersion;itsHotfix?*

*We have too hotfix repo, if itsHotfix==true, then ROM Manager, will get download link from another repo, format it's more easy, just hotfixDirectURL;MD5;NeededVersion, so if rommanager main list, have 5 roms, hotfix repo, have 5 urls, if rom dont have hotfix, you can write just null, or anything, like a placeholder :p

Please give us all the feedback you can!

please DON'T give me thumbs up if you don't give to slade first, Thanks.
[XPERIA X10 Themes and Apps] slade87:
Changelog:

First Release for Testing
[XPERIA X10 Themes and Apps] DooMLoRD:
@Slade

did u get my p.m.?
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
So guys, nobody will do the repo list?, if you're not interested tell us, we even made a tool :rolleyes:, now we can't do this without your help
[XPERIA X10 Themes and Apps] ImS0Raw:
I will look into it, let's see!

EDIT:

Is this what you need? Also did I do it right?
[XPERIA X10 Themes and Apps] DooMLoRD:
@D4

any word from Slade?
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
He's still on exams, but he said me he readed your PM, and will take a look on vacations :)
[XPERIA X10 Themes and Apps] Mr. Clown:
Moved to themes and Apps.
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
More like this

http://notepad.cc/share/Zyml1AwVmi

Please be sure that name on Build.prop have to be this same "CM_TW_V008", and where's version ? :D

No offense, have you checked first post specs, version it's not a String, it's a double number :) (so instead of XPERIA TW V008 should be 8.0? )
[XPERIA X10 Themes and Apps] ImS0Raw:
A bit hard for me to understand your first post ;)
[XPERIA X10 Themes and Apps] DooMLoRD:
@D4, Slade

u guys should make it more intuitive... its really confusing... if possible remove so many strict restrictions on naming/version numbering...
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
You guys can understand android world, busybox commands, im sure you can get it ;), just check example here http://rommanager.de/rommanager/repository/approved/repo.list
[XPERIA X10 Themes and Apps] DooMLoRD:
dude i am just suggesting so that it becomes slightly easier to get it working... every rom dev has different naming/numbering style... u cant control that... what u can do is to make ur program work with all possible styles...

also i am not sure many devs will appreciate making changes to build.prop...

anyways... it was just a suggestion...
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
Wow you see what you're saying .. making it compatible with ALL possible styles. That's insane :/, as you said, every ROM dev has different style, so will be impossible to get all the ways, so that's why we make unifications :D, we have unified chargemon, easy-to identify roms, etc. It's just hard, think on this, ROM manager checks doubles from some rom, but how can we check the version, on a ROM, called GRJ22, and the same name on all versions?, how would ROM manager recognize that there's a new version?. it's not so hard for devs, just change 2 things on build.prop, im sure you do it all time for some tweaking or testing :)
[XPERIA X10 Themes and Apps] rtblittlebrown:
I dont think a unified chargemon is possible as diffrent ones are used between 2.1 ,2.2 ,2.3, and miui roms also using a custom kernel or not makes it even more complicated
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
It's not needed unified chargemon that's just an example, i just need devs to mod a little bit build.prop, it's not hard ;)
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
Sorry for double post, but this is nice idea:

Just got a idea, about making your chargemon unified, i mean, the basic part of chargemon, inside it, and the kernel addons, and all that things, inside a external .sh on system\bin folder, so ROM Manager, can easily detect / mod chargemon, and your kernel dont get affected ;)
[XPERIA X10 Themes and Apps] DooMLoRD:
dude if we work on my kernel manager idea we dont need to worry abt chargemon at ALL! we will use our own chargemon/recovery pack!

lets start it please!

x10 needs a Kernel Manager app!!!
[XPERIA X10 Themes and Apps] D4rKn3sSyS:
I got it, but calm down bro, world's not getting over XD, slade's still not on vacations, im sorry but we cant do anything without him.

For other side, my idea it's cool, you guys take a coffee, and talk about it ;)
[Galaxy S II Q&A, Help & Troubleshooting] motylosza:
My gallery or all share app do not see any pictures or movies on my phone. I have a 10 avi movies on my phone but when i want to use all share app its showing me no movies at all. same is with photos. its showing only mp3 on music but also only a few. when i open the gallery app there is no photos. When i make a photo for example and go to gallery the photo is there but next day gallery is empty. i have to open all my videos and pictures using explorer. i am using batista 70 rom and i am very hapy wih this rom just i have no idea why my files are not seen by system apps. Help please.
[Galaxy S II Q&A, Help & Troubleshooting] sicopat:
Try to do a wipe cache partiton in Recovery Mode then go to advanced and do wype dalvik cache. Then reboot (you won't loose anything)

If not enough : in parameters > Applications > manage applications > Gallery, appshare : delete files and clear cache (you won't loose anything).

And say us if it's better now
[Galaxy S II Q&A, Help & Troubleshooting] motylosza:
Thank You for an answer. I just try all of this that You write about and nothing changed. I dont know is it important but every time I turn on my phone i have a monit 'process android.phone.com force close' twice and there is no signal on my phone but after a minut signal back to normal. Maybe i should just try to format partition in recovery mode?
[Galaxy S II Q&A, Help & Troubleshooting] bamthwok:
I had very similar problem that's how I stumbled into this thread. I could solve my headache as I just had to remember that I had disabled "media scanner", therefore no pictures and videos will be loaded to the gallery!

Please make sure that you have not disabled "media scanner"
[Samsung Galaxy S (4G Model)] jglm:
so i got a 2g data plan a now i ran over 2g so now my internet slow as hell is there any way that i could make it faster until i pay the bill ?
[Samsung Galaxy S (4G Model)] Exodian:
Use wifi whenever you can. The 2gb cap is bulls#@t. I ran over my first month so started using wifi at my house and work or wherever I could get a signal and have been fine since.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Consider upgrading to their 5 or 10 gig plan... I had been sent a notice that I was approaching my "throttling" point, was on the 5 gig plan, called t-mobile and was told that there was a new rate plan that gave me 10 gigs of data. I did have to extend my contract but that didn't bother me because I only had my plan a couple of months. With the new plan, my wife still has 5 gigs and the total bill only increased ~$5 because the unlimited talk/text/web portion of my plan went down $20.
[Samsung Galaxy S (4G Model)] Exodian:
I'm a have to look into this myself. A 5gig plan would be nice. Thanks.
[Samsung Galaxy S (4G Model)] jglm:
Thank yall i will upgrade my plan i wish their was a way to make 2g fast since i ran over 2g.
[Galaxy S II General] BarryH_GEG:
+1

I think people have much different expectations.
[Galaxy S II General] JJEgan:
Yes oh wise one i shall indeed pay lip service to your well informed ramblings and bow down before you the fount of all knowledge .

What time is the next meeting of the flat earth society pray do tell .

http://www.youtube.com/watch?v=JmvCpR45LKA

jje
[Galaxy S II General] Sp1tfire:
Rofl, not another yellow-tint type thread :o
[Galaxy S II General] JJEgan:
Well the guy has done some serious research on 4 phones out of the 5 million or is it 55 million sold .

He sees a problem on four so by definition you have been told YOU and the millions of others have a problem don't argue its a scientific test .

jje