Related
I saw this link over at gsmarena.com which lead me here: http://xperiancers.com/2010/02/02/x...&utm_campaign=Feed:+Xperiancers+(Xperiancers)
Xperia X2 software support schedule
// February 2nd, 2010 // X2, X2 News
As the X2 begins to roll out globally, it’s only fair that customers know what kind of support we’ll be giving the phone in the months to come. It’s not news to say that we attracted some criticism for this on the X1 and we’re not going to go there again with the X2. So, for the record, this is what X2 customers can expect in terms of software upgrades.
In March, we’ll launch our first upgrade (MR1). It will upgrade Windows Mobile from 6.5.1 to 6.5.2 (which will improve both the stability and usability of the device), it will bring in the use of video telephony, an FM radio and it will introduce fast GPS to get a quicker fix. As well as all this, MR1 will upgrade a lot of the applications in the phone to improve speed, usability and fix any bugs we find.
The second update will go live in May and this will be a big one as it moves Windows mobile onto 6.5.3. This is a significant upgrade in terms of usability, performance, power management and the browser experience.
That’s the extent of our plans at the moment but I’ll update this post as we make any more decisions.
(ps. Before anyone asks, no it won’t ever go onto Windows Mobile 7, it won’t support the hardware.)
Click to expand...
Click to collapse
lol hope there will be an xperia with hw keys when win 7 releases
Sounds nice
wow. im very impressed with this. nice to see that theyre taking the X2 seriously and have a plan in place. looking forward to march and seeing the first update
I'm gonna get it soon.
i wish they took x1 seriously
sx1-doc said:
i wish they took x1 seriously
Click to expand...
Click to collapse
don't we all?
but as fair is fair, i don't take SE seriously any more...
at least they acknowledge their mistake and promise to do better.
Is it possible to update my x2 through online once the update is launched? Thanks
yes it should be through the sony update service since they are official updates.. you can download the update software from sony ericssons website. im sure someone will post on here when they become available. or just randomly try and update your phone every few days during march until something happens...
anothadave said:
yes it should be through the sony update service since they are official updates.. you can download the update software from sony ericssons website. im sure someone will post on here when they become available. or just randomly try and update your phone every few days during march until something happens...
Click to expand...
Click to collapse
What if something happens wrongly?
I would like to ask. Am I able to install Java programs in my X2 & use? Thanks
lostsouls said:
What if something happens wrongly?
I would like to ask. Am I able to install Java programs in my X2 & use? Thanks
Click to expand...
Click to collapse
Almost everybody does upgrade this way!
Fear not, it's a stable process.
Of course you can install Java,
in fact X2 has best Java results.
lostsouls said:
What if something happens wrongly?
I would like to ask. Am I able to install Java programs in my X2 & use? Thanks
Click to expand...
Click to collapse
lol all i meant was you just connect to the update software every few days and see if it tells you if theres an update available. if theres no update then nothing happens. even if there is a newer update you still have the option to stop before anything happens.
remember to always make sure everything important is backed up before starting an update.
its a shame that sony dont have something on their website to inform people when a new update is out. would save having to connect to the update software to check. or even if they let us register and then they could email or text us...
anothadave said:
its a shame that sony dont have something on their website to inform people when a new update is out. would save having to connect to the update software to check. or even if they let us register and then they could email or text us...
Click to expand...
Click to collapse
Well, for that there are sites like USEB or Engadget Mobile, no need for SE to do anything
Interesting ... Got my entertainment bundle without issues on PC World purchased Tab (on day of release). Got games ok ... applied movie voucher ... ordered my 16 movies ... nightmare getting onto tab (site really flaky and DRM on various films failed) and awful download experience ... 12 out of 16 failed to complete the download on more than one occasion.
When I called Samsung Apps CS .. they committed to resolving above issues and also trying to get me PC DVD copy which was promised when voucher applied. They said they had not decided whether they should be giving two copies of each film with this promotion but I explained for those that have already been told at time of voucher application, they really have no choice. Let's see what happens. Curious to know what other people's experience has been like.
Anyway ... the real puzzle was ... I asked about 2.3 and 2.4 updates.
They know nothing about the latter, but I was told 2.3 was already out in the US (Grrr) and although there was no date I could be given, we should expect it soon in the UK.
Anyone from US played with it yet ?
Paul.
So far no update to 2.3 in the US that I know of.
Sent from my SCH-I800 using XDA App
When I redeemed my voucher, all the movies I've bought so far have given me two links - one for the PC and one for mobile.
As to 2.3 for the Tab - as far as I'm aware it's not available anywhere, so I think you've been misinformed.
Regards,
Dave
Hello guys,
WP7Android apps for free here http://forum.xda-developers.com/showthread.php?p=21408342
So what's all about? !!
A innovative UI currently in development which will have 20 apps and a simple, elegant, fully customizable GUI. Available screenshots in second post.
Also a ROM[no Kang], which aims to become better then CM&MIUI and improve android overall. If you are a developer or a user who wants to help just PM me or Mr.Highway
ROM signup:https://docs.google.com/spreadsheet/viewform?formkey=dFdIN1dMSTc2eXNMM2c0TlBadHZVWVE6MQ
Apps closed beta signup:https://docs.google.com/spreadsheet/viewform?formkey=dHBnMjRaUEpRX3ZFUlZWWmxVOWxGUHc6MQ
What else can you expect from it?
All apps are planned to be the best on the market so you can expect a rich user experience with many features that will include competitor ones and original.
How many apps will the UI have?
About 20. Here is a list with most of them:
Code:
1)Dialer
2)SMS/MMS
3)Email
4)Calendar
5)People with IM and social
6)Calculator
7)Player
8)Gallery
9)Launcher
10)Browser
11)Notes,
12)Stock + Currency converter
13)Weather
14)Clock
15)News
16)File/Task manager
17)Settings
18)Lockscreen
19)Theme Engine - Desktop App
How is everything organized?
I'm leading a multinational team of 9 developers. As for the project it has 4 stages:
1)All apps with basic features in one app
2)Adding advanced features
3) Integration between all apps
4) Implementing UI
When will this be released?
Something like end of April or middle of May for beta if things go well. And final release 2-3 weeks later.
When can we test?
Some will have the chance to test early in private beta testing. All others will have to wait for public beta.
Will this be free?
Free with ads. Estimated prices in third post.
If there is anything you want to know PM or email me([email protected]).
Updates and pics/videos on second post.
Blog on third post.
If you want to support buy me a drink, hit the thanks button, vote, share on Twitter/Facebook/Google+ or Follow me on Twitter: https://twitter.com/#!/Mafteiu_Vlad
Thanks for donations to:
Sergioalvarezmac - *****
Cajl - ***
Trekfan422991 - ***
Gab1972 - **
Rainabba - *
Clixt - */2
Updates
1.0 - 23.01.2012
-Launcher design:
-Basic notes and news app finished.
-Push services and server database for users,notes and news
2.0 - 5.02.2012
-More work on new contacts
-Started work on email app
3.0 - 27.02.2012
- Finished basics of launcher
- Finished about 70% of the player
- Finished core of dialer, SMS and meteo app
- Finished about 60% of notes and 80% of news apps
- Finished about 10% of calendar
- Begun works on stocks/currency
- Begun works on file/task manager
- Begun work on calculator and gallery
4.0 - 07.04.2012
- Finished 60 % of browser
- Finished 20% of Calendar
- Finished 90% of player,weather,news and notes
- Finished 70% of File Manager
- Finished 50% of Calculator
- Finished 20% of Gallery
- Finished 100% Stocks/ Currency converter
- Finished 80% of Dialer
- Finished 100% Contacts
- Finished about 30% of internal website functions
- Begun work on Social Networks App
- Begun work on Clock App
- From next week we will continue SMS, Launcher and Lockscreen and hopefully have over 50% of IM ready
5.0 - 24/4/2012
- finished browser app
- finished 30% of SMS
- finished 50% of calendar
- finished 20% of social app
- finished 90% of dialer
- begun work on email
Begun serious work on design:
NOTE: We will have 4 default UI's:
-> WP(just style, not wp7 original look),
-> Android
-> IOS
-> Original and surprise
All the graphics are made from scratch, nothing in taken from another designs and all are vector so SkyD UI will be scalable at any DPI screen size and even on High Resolution Screens.
6.0 - 29/4/2012
Finished:
- 90% of SMS
- 70% of calendar
- 80 of file/task manager
More work on:
- Email
- Gallery
- Clock
- Social
*** Begin work on UI and themes support
!! I've seen that a lot of designers have applied to test. In order to benefit from this, we will provide tutorials for building UI's(working with xml and such). Thus our 4 official UI's will be done by our designer, and if anyone wants to provide his own he will be able to easily do so
Blog
So I've decided to keep the third post as a personal blog where I can share my thoughts about the project, your comments and what else come in my mind. So let's begin.
1)
In about a day my project got over 24 pages on Google. So many that I got bored counting . This looks really promising, never imagined this level of success. Also first page on XDA.
Managed to read a few and there are two things that were not quite right. One article said that I should change the name to metroid. I don't think so, that will mean M$ flame . Also another thing is the supposition that all team members are xda guys. Only one is(which wants no money or IR), the rest are paid devs. There is no chance that free time devs will finish this project in time. Hope I made clear some things.
Also this week meteo and new contacts will be finished. Next week IM with AIM,MSN,Yahoo,GTalk,Skype,Facebook and Jabber support will be finished. Tell me if you use others as well.
Edit: Thanks to the guy who emailed me to remind me of Facebook chat.
2)
So I thought more about the prices and there will be 2 options:
In app purchase for ads free with
Google - 2.50$
Paypal - 1.89$
Why is it cheaper with paypal?
Google fee is 30%(thievery) and it registers as payment and thus I have to pay taxes. Paypal fee is 0.33$+1% and it registers as donation. I will receive about the same amount in the end(a little less for G option)
So paypal is a better option for all of us, even if some of you hate PayPal. Hope the lower price will encourage you to use it.
Also there will be an update with pics and a video showing more of the UI most likely this weekend.
That's it for now. Stay tuned!!!
Awesome project!!! Keep it up!
Thank you!
Thanks for your efforts and hard work! This looks promising.
I will definitely be keeping my eye on this project.
Love your wp7 suite
Can't wait for win 8
Sent from my GT-I9100 using XDA App
Can't wait to use it on my Galaxy Tab!
Hi,
I can help you like beta tester. I've a Samsung Galaxy S 2 (I-9100) and a Motorola Xoom (MZ-604) wifi-only tablet.
Cheers and keep walking!
count me in as beta tester also, i have my beloved HD2 and Desire to test it on
I would love to test it on my Evo 4G. Plus, it would be a great late Birthday present (b-day is in March).
I'd also love to be a betatester with my optimus 2x
Looks really great, hope you get this fast done .... really seems to be the future UI
If you guyz can make this fluid enough, it's gonna be epic.
Hey, ill test for you on my HTC Amaze.
Got a willing motorola Droid x2 here.
Sent from my X2
Sounds very interesting, will test on HTC Sensation
A very willing Galaxy S2 beta tester
I also like beta tester on Huawei u8650 and SGS2.
ill test on mah tbolt. it needs a new look anyway
I will test on my motorola electrify
WOW!
Can't wait for this to finally release!!
Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced. I'm not the most technical of this crowd (I mean c'mon I am here at XDA!) so please forgive me and notify me of any needed corrections or clarifications.
---[Documenting] Google's Nexus 10 MALI GPU memory leak *UNRESOLVED*---
The Nexus 10, henceforth N10, is an Android tablet made by Samsung for Google. At launch in November 2012 the N10 was shipped with Android 4.2.0
*
Included in the N10 is a SOC (system-on-a-chip) from the Exynos line:
http://en.wikipedia.org/wiki/Exynos_(system_on_chip)
*
The Exynos uses a GPU made by ARM. The GPU component is the ARM Mali-T604.
http://en.wikipedia.org/wiki/Mali_(GPU)
*
Starting immediately after the N10’s launch there were reports of “random reboots”. At first not much was known about the exact cause of these reboots. The audience participating in these reports experienced varying degrees of testing results, especially as 4.2.1 and 4.2.2 updates rolled out. The majority of this discussion is captured in two threads:
https://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[1-25-false] *
and
http://forum.xda-developers.com/showthread.php?t=1998496
(*Note that the Google thread was erroneously marked ‘Answered’ after one of the OTA roll outs.)
*
The community was able to flush out that the memory/RSS use of Android’s surfaceflinger process seemed to be the victim of a memory leak, and that by monitoring the RSS value one could predict when the tablet would experience the degraded performance. Viktor.M then created this open issue report that focuses in on that:
https://code.google.com/p/android/issues/detail?id=54757
*
About that time a user named apstrand, who appears to either be an ARM developer or at the very least someone who is extremely knowledgeable in this area had found more exact and detailed info on this, and he posted it here:
https://code.google.com/p/android/issues/detail?id=52579
*
Matthew Fry began contacting Samsung, then in turn ARM, as he posted in one of the Google threads. Eventually he was able to get this response: "I can confirm that we were able to reproduce the issue in the stock Nexus 10 4.2.2 provided by Google. We were, however, unable to reproduce it with our release driver.
We will test the application again when the next release of the firmware for Nexus 10 is published."
*
From this point, knowing ARM has code that avoids the error, people began looking into working on the code themselves, and asking ARM for assistance. ARM has posted source code components for the T-6xx series of drivers here:
http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/
However ARM has also stated, “these components are not a complete driver stack. To build a functional OpenGL ES you need access to the full source code of the Mali GPU DDK, which is provided under the standard ARM commercial licence to all Mali GPU customers.” This means Samsung has an ARM DDK (Driver Development Kit), but to date has not released it/aspects of it to the public.
*
For now there appears nothing anyone can do without access to the ARM DDK.
*
EDIT/UPDATE: Since my original post here, a lot of activity happened in a short period of time. Many comments below capture this. I will add the history into this thread, but the big news is 4.3 is out for the N10 now and the community is testing. Like each time a new Android version has rolled out, community testing is "all over the place" with different people reporting different results. People who know how to measure the exact parameters on this bug are reporting it looks like it may be fixed! Its noteworthy though that there is some suspicion of other issues. Because I want to keep this first post based only on facts, I am going to wait a while and see the community results before posting an update that cant be backed up by actual data.
***
FINAL UPDATE: Ok, looks like its fixed now. I'm not saying they didn't morph it somehow to another issue, but I am saying the exact situation we were all focused on here is no longer going on w/ the 4.3 (4.3.x if you want to include the 3mb update.)
bigmatty said:
Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced.
Click to expand...
Click to collapse
Nice overview of the problem. I would add that one of the Android bugs you link to is marked as assigned, by none other than Jean-Baptiste Queru, the technical lead of the Android Open Source Project at Google. He also renamed the other issue, so it appears that Google is finally aware of the problem and working on it. Hopefully, this means a fix is forthcoming in the upcoming Android 4.3 release, but that is merely a hope on my part: I have no inside info.
bigmatty said:
Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced. I'm not the most technical of this crowd (I mean c'mon I am here at XDA!) so please forgive me and notify me of any needed corrections or clarifications.
Click to expand...
Click to collapse
Thank you, this thread was sorely needed. This seems like a really big mess-up on Google's part. Has there been a memory leak this bad before for any other device?
patsmike said:
Thank you, this thread was sorely needed. This seems like a really big mess-up on Google's part. Has there been a memory leak this bad before for any other device?
Click to expand...
Click to collapse
I don't think so. My Dad has a Nexus 7 and it doesn't have this issue at all. I really hope that 4.2.3 or 4.3 fixes this - it's making me completely lose patience with the device and I'm getting tempted to sell it. First the light leak issue and now this. Come on Google, you really are taking the piss here. I'm not sure how they could get it so wrong?!
bigmatty said:
...This means Samsung has an ARM DDK (Driver Development Kit), but to date has not released it/aspects of it to the public.
Click to expand...
Click to collapse
So this fix requires Samsung to do it.
Almost hate to say it but I really don't see it being fixed anytime soon...
I confirm that surfaceflinger is f***ed up on my Nexus 10 too.
It screws up very, very fast when connected with USB debugging and I start to code OpenGL ES 2.0-based live wallpapers.
---------- Post added at 10:04 PM ---------- Previous post was at 09:58 PM ----------
espionage724 said:
So this fix requires Samsung to do it.
Almost hate to say it but I really don't see it being fixed anytime soon...
Click to expand...
Click to collapse
Not that bad. If it was HTC, we'd be screwed forever. With Samsung, we have a tiny (well, like, really tiny ) hope that something will be done in this regard.
I have been reading that Nexus owners may get 4.3 this month - anyone think the problem may be addressed?
In this thread http://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[476-500-false] - some dude from Google acknowledges that they know it's a problem - but he hasn't said anything in 6 months.
Really hope it is sorted out - I am keeping my fingers crossed.
bruce_aisher said:
I have been reading that Nexus owners may get 4.3 this month - anyone think the problem may be addressed?
In this thread http://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[476-500-false] - some dude from Google acknowledges that they know it's a problem - but he hasn't said anything in 6 months.
Really hope it is sorted out - I am keeping my fingers crossed.
Click to expand...
Click to collapse
As a comment above suggests, the bug has been assigned by Jean Baptiste-Queru little more than a week ago. We can only hope that it was fixed and merged into 4.3.
starkilling said:
As a comment above suggests, the bug has been assigned by Jean Baptiste-Queru little more than a week ago. We can only hope that it was fixed and merged into 4.3.
Click to expand...
Click to collapse
From what I read the developer of the surface finger driver already has an in-house fix and acknowledged that they reproduced the issue with the stock ROM. Those two comments give me hope.
Sorry but I do not have a link. I also have no idea why fixed drivers have not been released considering every ROM (stock and custom) must use the same proprietary drivers. It is likely that they require Google to distribute the fix.
I really hope to see this fixed soon, the random reboots really make the tablet unreliable. I can't do much serious work on the thing since every couple of hours or so the thing resets, losing all my work.
tbosje said:
I really hope to see this fixed soon, the random reboots really make the tablet unreliable. I can't do much serious work on the thing since every couple of hours or so the thing resets, losing all my work.
Click to expand...
Click to collapse
I use RasBeanjelly and I have not had a single random reboot. No reboots on mrRobinson's AOKP as well. You do have to reboot every couple of days, though. It really depends from ROM to ROM. Stock really rebooted on me like a motherf***er though.
I saw that one of the Google staff responded to the google product support thread the other day, a sign of progress?
starkilling said:
I use RasBeanjelly and I have not had a single random reboot. No reboots on mrRobinson's AOKP as well. You do have to reboot every couple of days, though. It really depends from ROM to ROM. Stock really rebooted on me like a motherf***er though.
Click to expand...
Click to collapse
I've spent so much time customising my apps and launcher, flashing my whole unit is such a hassle. Guess I might have to though :/
tbosje said:
I saw that one of the Google staff responded to the google product support thread the other day, a sign of progress?
I've spent so much time customising my apps and launcher, flashing my whole unit is such a hassle. Guess I might have to though :/
Click to expand...
Click to collapse
You can back them up, you know.
Posted by Matthew Fry on Google Product forums earlier today :good:
Ladies and gentlemen, I have the most amazing news. Pretty much the best news I can think of.
I have finally received word back from the Mali Developers. They revisited the issue and found that the fault was indeed in the Mali drivers.
"Following previous emails, the Nexus 10 issue that you have been mentioning has been fixed in the latest versions of the Mali driver."
It is, unfortunately, Google's responsibility to release this new driver version with the next Nexus 10 factory image. We can only hope that the fact that I/O has come and gone and the recent release of the Google Edition S4 and One on 4.2.2 does not mean that JB 4.3 or KLP are a long ways out.
chinmaysk said:
Posted by Matthew Fry on Google Product forums earlier today :good:
Ladies and gentlemen, I have the most amazing news. Pretty much the best news I can think of.
I have finally received word back from the Mali Developers. They revisited the issue and found that the fault was indeed in the Mali drivers.
"Following previous emails, the Nexus 10 issue that you have been mentioning has been fixed in the latest versions of the Mali driver."
It is, unfortunately, Google's responsibility to release this new driver version with the next Nexus 10 factory image. We can only hope that the fact that I/O has come and gone and the recent release of the Google Edition S4 and One on 4.2.2 does not mean that JB 4.3 or KLP are a long ways out.
Click to expand...
Click to collapse
Link, please? I can't find it.
Edit: found it, nvm. there were lots of pages
Can one of the mods please pin this thread in the forum? It seems like every week someone comes in and asks about this issue. Once a fix is released, this thread can be unpinned.
6 Month and Samsung and Google havent resolved that.....
Hope 4.3 comes out soon
kswiss86 said:
6 Month and Samsung and Google havent resolved that.....
Hope 4.3 comes out soon
Click to expand...
Click to collapse
Well, I hope the driver didn't come out from Mali too late to make the 4.3 release.
Funny thing is I even said to myself that I'll never buy anything from Samsung again, how wrong I was thinking the Nexus 10 would be different because it's from Google.
With 4.3 out next week (possibly) I do hope Google decide to put this emergency fix in. It really gets on my nerves that this tablet just randomly reboots because I know how much potential this tablet has and I feel this is holding it back.
Sent from my Nexus 10 using xda app-developers app
Today, L04C567B396 appeared on FF, the third update in a month time with no approval for installation for the earlier B394 so far.
With this updae comes two additions and one improvement to the EMUI features plus a new June google security patch.
Again, with this update a hope of eminent EMUI 8 (Oreo) is lost at least for a couple of months if not impossible any time soon in my opinion.
Let's hope that my guess is wrong.
Tell me what do you think in the comments below.
Anyways here's the B396 changelog:
This update reduces Phone Manager's cleanup time to less than one minute, and adds more scenarios to support the one-touch split-screen feature.
[Dual windows]
Adds a button in the Recent apps cards. Touch it to split the screen. This operation is only available for apps that support the split-screen feature.
[System]
Optimizes Phone Manager's cleanup speed and scope. A single cleanup can now be completed in less than one minute.
Optimizes data usage management by allowing you to specify the start date of your data plan.
[Call]
Optimizes Quick calling by enabling speaker mode by default. Press and hold the volume down button to enable Quick calling.
[Security]
Integrates Google security patches released in Jun 2018 for improved system security.
----------------
Update 1: Honor skipped B394 to B395 and stated seeding.
Nitrowarez.
Sent from my FRD-L04 using Tapatalk
Who cares? By the time it's approved it'll be end of July possibly August. Chris (head Dev at honor USA) says they have no control over when it gets approved. We are getting Oreo, and he's getting responses from the beta group about the bootloader issue to give to the higher ups.
agraceful said:
Who cares? By the time it's approved it'll be end of July possibly August.
Click to expand...
Click to collapse
I was thinking the same.
Honor support told me we would get it 'very soon' 2 months ago and its likely another two months if they have only just started alpha/beta testing.
Not sure I agree that is 'very soon'.
Personally I'd prefer lineageos so we get future support, but haven't read the other threads to understand why dev support is limited.
Perhaps 'Chris' can release the kernel source for Oreo on the Honor 8, so others can start development in parallel with Honor, or release the camera blobs or whatever is stopping the camera's working.
I think we better stop creating new threads for each patch for specific model .,. its getting really boring.,., i myself created several threads for the patches but no charm now.., especially after oreo in tow..,
admins if we could join all the threads under patch update.,
SSyar said:
I think we better stop creating new threads for each patch for specific model .,. its getting really boring.,., i myself created several threads for the patches but no charm now.., especially after oreo in tow..,
admins if we could join all the threads under patch update.,
Click to expand...
Click to collapse
I guess I'll make it. Hopefully it works out well
xsacter said:
I guess I'll make it. Hopefully it works out well
Click to expand...
Click to collapse
Hope so?
scoobydu said:
Hope so?
Click to expand...
Click to collapse
Yea because some people might not like the idea, including admins
xsacter said:
Yea because some people might not like the idea, including admins
Click to expand...
Click to collapse
Ok.