yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] sohebq:
9 Million in just 2 weeks, awesome

http://www.gsmarena.com/galaxy_s_iii_gets_9_million_preorders_from_100_global_carriers-news-4264.php
[Galaxy S III General] blizzari:
RE

Well they are testing prototypes of flexible amoled screens but i dont think tha galaxy s iii will have one

SPECS

SCREEN: 1280x800 SAMOLED HD+ ?

CPU: EXYNOS 4412

GPU: MALI: T-648 ?

SIZE: 4-5 INCH

OS: TIZEN

RAM: 1-2GB?

MEMORY: 16-64GB?
[Galaxy S III General] jonny68:
I would assume (and hope) that the SGSIII would have memory to up 64GB maybe even more if they really wanna "push the boat out" as it were.
[Galaxy S III General] Scared27:
I won't get the S3 if it comes with anything but Android.
[Galaxy S III General] Amritttt:
I think its gonna be galaxy 3D
[Galaxy S III General] xenix96:
For what we need 3D..... That would be horror for me...this remember me the problems I got on Samsung 3D TV....
[Galaxy S III General] svceon:
Tizen is probably the mobile OS that might be capable of confronting Android. Still i'm with you in this one, S3 will have to be android, otherwise sales will go down. big way down.
[Galaxy S III General] Geo2160:
Samsung Galaxy = Android

Wave = Bada

The Tizen OS phone will in a place of its own.
[Galaxy S III General] rouvax:
Oh ı should sell my other kidney like i did for iphone.

Lol
[Galaxy S III General] jaykresge:
I'm going to amend a post from earlier. Here's the contenders for the possible SOC in the Galaxy SIII (and compared to the Exynos 4210 in the Galaxy SII).

Exynos 4210

CPU: Dual-core Cortex A9 @ 1.2ghz

GPU: ARM Mali 400 MP4

Process: 45nm

Status: In shipping product

Exynos 4212

CPU: Dual-core Cortex A9 @ 1.5ghz

GPU: Unconfirmed, believed to be ARM Mali 400 MP4 clocked 50% higher than in the 4210

Process: 32nm

Status: Confirmed as sampling in October 2011, should be available for shipping product around April 2012

Exynos 4412

CPU: Quad-core Cortex A9 @ 1.5ghz

GPU: Unconfirmed, believed to be ARM Mali T-604

Process: 32nm

Status: Leaks show this as a possible Samsung SOC, but no official confirmation. Unknown if sampling and when general availability might be.

Exynos 5250

CPU: Dual-core Cortex A15 @ 2.0ghz

GPU: Unconfirmed, lead candidates are ARM Mali T-604 and PowerVR SGX544

Process: 32nm

Status: Confirmed as sampling as of November 2011, should be available for shipping product around May 2012

-----------------------------------------------------------

With that said, I just cannot fathom Samsung using the 4212 in the Galaxy SIII. That would mean their flagship model would have a speed boost over the SII and nothing more. So, the lead candidates should be the 4412 or the 5250. The 5250 is their 2012 flagship SOC, whereas the 4412 is just a rumor at this point. But, for ****s and giggles, let's compare their theoretical performance.

Exynos 4412:

Cores: 4

DMIPS per clock: 2.5

DMIPS per core: 3,750

DMIPS total: 15,000

Exynos 5250:

Cores: 2

DMIPS per clock: 3.5

DMIPS per core: 7,000

DMIPS total: 14,000

So, the quad-core would encode 4 or more streams slightly faster than the dual-core, but in actual real-world usage, the dual-core would stomp the quad. This is because no program is 100% efficient as multi-threading. With each core you get diminishing returns. Each core in the 5250 is significantly faster than each core in the rumored 4412. Trust me, if you had to choose, you WANT the 5250.

It could be either SOC, but the hopeful side of me is saying the Exynos 5250 is the chip in the Galaxy SIII. OMAP5 will be out in the second half of 2012 and uses the same technology as the Exynos 5250. So, if the Galaxy SIII gets the 4412 instead, it will be the first time the Galaxy S series has been outclassed by another shipping product in the same calendar year.
[Galaxy S III General] nat510:
Exynos 5250 is great :cool:
[Galaxy S III General] Xerovius:
Why 32nm instead of 28 for the 5250? :confused:
[Galaxy S III General] Sayo1337:
To be fair the picture of the proposed GS3 looks more like an ipod touch 3rd gen+. I switched from an iPhone to a GS2 and I love it more than my iPhone. Tbh I think Samsung has it spot on with the style of the GS2. But in regards to the quad core processor I am actually amazed if they have managed to create one as the proposed specs would be near the specs of my comp. (pretty far but not too far). Its going to be interesting to see what can be achieved with such a device and what improvements can bet bestowed upon them through the developers of XDA. I look forward to it but would rather it be styyled like the GS2
[Galaxy S III General] Poker gypsy:
Can't wait for the gs3 and get rid of the crap sony arc
[Galaxy S III General] Sayo1337:
Well said poker lol
[Galaxy S III General] Poker gypsy:
Yea you wont believe all the crap the sony lovers are giving me lol
[Galaxy S III General] microline:
I totally agree with you mate, GS2 is perfect size just pump up battery and that it.

br
[Galaxy S III General] Sayo1337:
I've been following mugen power on twitter. They sell higher watt batteries for loads of phones and offer a 7% discount if u follow them on twitter that should help with battery life if you buy a better battery
[Galaxy S III General] st3chn0:
how can this not be real... just like it happened with the tablets they got the dual core CPUs first... for example take the transformer prime tablet it comes with a quad core so soon enough probably in the release of s3 it will have a 4core.... and all of you that are concerned with battery is bug like tegra 3 there will probably be a 5th core running at low power so the aos bug won't be that much of a problem
[Galaxy S III General] Sayo1337:
I'm just saying its hustling incredible how technology is growing or shrinking in this case in terms of the cpu as its basically a computer
[Galaxy S III General] notoriouspk:
I hope gs3 gets a big battery bump , just like droid razr maxx with its 3300 mah keeping it 9 mm and weighing at 145 g .... We will find out in Feb
[Galaxy S III General] B3311:
Android, HD 4,5" screen or bigger, decent sound chip. Whatever CPU setup as long as it's not inferior to the SGS2 (a la Nexus)

Do that then I'm in, price isn't a worry. One caveat - 64GB minimum and if not, a microSD slot. Otherwise it's a Nexus, no?
[Galaxy S III General] notoriouspk:
Since recently announced galaxy tab 7.7 Lte for verizon comes with super amoled plus hd display its safe to assume gs3 will come with super amoled plus hd display ,4.5 inch screen , rumors say 1.5 RAM....n I am hoping for 32 gb n 64 gb versions processor would be good enough ( since tegra 3 is here ) cortex A15 2.5 ghz dual core..battery needs to be bumped just like moto razr maxx 3300 mah .

12 mp with a good censor....Did i miss something :-)
[Galaxy S III General] Intratech:
Assassin core!
[Galaxy S III General] cokeman2:
i like to see 16mp camera (maybe wide-lens )as all the competition are going for 12's now . it make it stand out be ahead of its time .... no 3d unless its revolutionary causes no eye strain.....
[Galaxy S III General] st3chn0:
well there is the tech that's soon being released on TVs... apparently that causes little eye strain
[Galaxy S III General] dfi2k5:
Take a look here: http://www.youtube.com/watch?v=NxJloZ1Rq0E

at minute 7:12, you'll have a surprise!!!
[Galaxy S III General] Intratech:
Fwap fwap fwap!!!!
[Galaxy S III General] monster75:
wow! Is it the S3? I think there will be some issues to find a back cover which doesn't mount on the display...

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

I hope display will be a SA Plus HD and not just a SA HD...
[Galaxy S III General] Gnarfsan:
It doesn't look like anything else I have seen. And the size matches :-)
[Galaxy S III General] monster75:
IMHO the best would be a 32nm (2GHz?) dual core CPU with 2 GB Ram and a SAP HD display.
[Galaxy S III General] jonny68:
Yeah i haven't seen anything like this before that Samsug has released maybe it's a teaser they have leaked hoping (or rather knowing) someone would spot it:D

I'm very happy with my SGSII and i shall not be purchasing anything else until the Galaxy S3 is released.
[Galaxy S III General] odevans:
As I stand, I say that I'll be sticking with my gsii, as I don't need anything better, because this phone fits the bill. But, I know damn-well that my mind will change, the moment I see someone with a gsiii!
[Galaxy S III General] newgargamel:
time to start saving for this baby :)
[Galaxy S III General] cokeman2:
the pic looks wow (from the previous page ) dont think theres any other samsung product/ph like this .....screen looks like 4.7" as there hardly no bezel and they made screen wider.and not much bigger than the sgs 2 ...
[Galaxy S III General] bgstcola:
It has a physical home button. I thought that ICS phones were supposed to have on screen buttons only?

Btw, I hope they keep the megapixels down. More megapixels means worse low-light performance.
[Galaxy S III General] KaliKot:
It's not required to have softkeys. Even the new Huawei phones with ICS still use physical buttons
[Galaxy S III General] systemcrasher:
There's been few leaks from Korea and it states that SIII will have:

Quad Core Exynos @ 2Ghz

2Gb RAM

And quite possibly:

3D Screen and connection to 3D TVs. The leaks didn't mention anything about 3D Camera though.

Also, Australia is likely be the first country that the phone is released after WMC in Barcelona.
[Galaxy S III General] CA3iR0:
It's not real, just a CGI. So it can be a CGI of the SGS3, or just a CGI showing how to control the camera.
[Android General] pokerfake:
Samsung just officially announced that there will be no ICS update for various android based phone from Samsung EXCEPT GS2, GS2 LTE, GS2 HD, Galaxy Note, Galaxy Tab 10.1, Galaxy Tab 8.9.

Samsung also said that GS1 specially optimized for Gingerbread, so they can not update GS1 to ICS.
[Android General] daleski75:
Just saw that so looks like anyone with a phone older than 2011 will have to resort to XDA for ICS which I think is disgraceful.

The Galaxy S is pretty much just a Nexus S without the NFC so no idea why Samsung won't at least update that one as well.

I am so happy I got rid of my Galaxy S2 and got a Galaxy Nexus.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] papertreeprophet:
I just got my skyrocket, having faithfully used my Nexus One since it came out for att. While I don't doubt I will eventually hop on CM again once it's officially out for the skyrocket, for now though I have to get rid of the bloatware and get back the ability to tether my tablet.

I was wondering what was the best of the methods for just getting root, superuser, and busybox, without putting on cwm or anything else?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] the2rrell:
if your on 2.3.5 use this.

http://xdaforums.com/showthread.php?t=1321582
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sm625614:
You can use super one click and the flash cwm via rom manager selecting tmobile sgs 2 as your device
[Wildfire Q&A, Help & Troubleshooting] arkoze:
Hi guys,

I've done a fair share of searching but it seems nobody is having the same issues :(

Basically, I thought i'd try out these new tweaks I found, the V6 Supercharger and the 3G Turbocharger from zeppelinrox - The V6 installed fine and was running smoothly but when i installed the faster version of the 3G turbocharger sent my phone into a bootloop (it eventually came back on to my relief). My HTC Wildfire is now thrown into a bootloop every time i enable mobile data. WIFI works fine.

I have reflashed my ROM, wiped data and dalvik cache, but when i flash the G_apps, the phone goes into the boot loop - and thats after a full wipe and reboot (i have now restored a backup - but the issue is still apparant)

Another thing worth mentioning is my local.prop file is empty and i'm not sure if this should contain any script.

Any help appreciated. Phone Spec below.

Thanks

Phone Model: HTC Wildfire Buzz

Android Version : 2.3.7

Rom: Cyangoen Mod-7.1.0.1-Buzz

Kernal: 2.6.35.14-nFinity arco@tuxbox #1

Radio: 3.35.15.31

Baseband: 13.45.55.24U_3.35.15.31

Hboot: 6.01.1002

S-OFF

V6 Supercharger - Unsupercharged

3G Turbo Charger - Uncharged
[Wildfire Q&A, Help & Troubleshooting] 3xeno:
This was caused by the 3G / V6 Script:

http://xdaforums.com/showthread.php?t=1015532&page=200

Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
[Wildfire Q&A, Help & Troubleshooting] arkoze:
Fix for bootloop after 3g turbocharger script install

FIX:

Ran an RUU for wildfire.

- Downloaded (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24_ 3.35.15.19_release_141106_signed) from android forums.

- Connected phone to PC and ran RUU

- This downgraded phone OS to eclair (android 2.1)

- Let it do the bizniss

- Had to re-root with unrevoked 3

- Re-Flashed CM7 and gApps

All ok

I'll say one thing, CM7 doesnt need a v6 or a 3G super/turbocharger. It works fine without them. The minfree values are set at an ok level and I always have HSDPA signal. Its not worth the effort.
[Wildfire Q&A, Help & Troubleshooting] eventcom:
Yeah after carefully tweaking this and that - all one change after the other and testing a lot before going on - I've been pretty much satisfied with my old buzz. Until I decided to give that 3G Supercharger a try (because of 3G didn't ever work really good - the only thing I was not completely satisfied with)...

It turned out that there hasn't been any improvement from my perspective so I just reverted the settings and went on.

It took me 2 weeks to find out where the bootloops suddenly came from (1 day to narrow down the prob had to do with switching on data and at least 10 days for the 2g/3g part).

Is there anybody who can explain more specific a) what causes this behaviour and b) what would be necessary to eliminate the cause (and probably avoid it in the future)

I won't get misunderstood but just "do an RUU update" sounds a bit like the standard no.1 suggestion "format and re-install" in all those amateur winsucks forums... :D

Thanks for the hint but even after reading all the related posts several times I don't feel enlighted somehow (besides the information that I don't need any super charge scripts with CM - which I'm half the way to be convinced of :rolleyes:)
[Wildfire Q&A, Help & Troubleshooting] eventcom:
noone? I just want to find out what exactly is the problem (to avoid it in the future) and I'm really curious why a complete wipe doesn't help. The Supercharger scripts just tweak values in config files (correct me if I'm wrong) - so if the problem is caused by the script(s): why can't it be solved by simply revert those changes (or replace the files by the default ones)?
[Wildfire Q&A, Help & Troubleshooting] st3v3droid:
Fix for bootloop after 3g turbocharger script install

eventcom

Did you find anything more about this problem?

I have the boot loop after using 3g/4g optimizer from the market, but I can get partial network use if I enable only 2g and not 3g. Better than nothing while I see if it can be fixed without a RUU.

Just wondering if a RADIO flash may solve the problem.

Regards.

Phone Model: HTC Wildfire Buzz

Android Version : 2.2.1

Rom: Stock

Kernel: 2.6.32.21-HCDRjacob-ga91e73b-dirtyroot@HDCR #1

Radio: 3.35.20.10

Baseband: 13.55.55.24U_3.35.20.10

Hboot: 6.01.1002

S-OFF
[Wildfire Q&A, Help & Troubleshooting] eventcom:
nope unfortunately not, but it seems, that the problem still occurs - see in this thread or here in that one - I've given it another try to flash radio again - with no help. The information about changed values in build.prop isn't new to me (as I did expect something like that) - what I don't know is which values exactly and how to overwrite them (if too many) when flashing a new rom...
[Wildfire Q&A, Help & Troubleshooting] eventcom:
So I went a bit deeper into the build.prop and made a simple diff against the build.prop of October 2011 (has been an earlier nightly and that problem definitely didn't occur at that time).

The only differences were those:

This looks like a simple addition for identification

+++ ro.cm.device=buzz

Perhaps that's a better guess (looks like this had been added sort of randomly anyway? - qualifies):

+++ # For PDP overlap problem
+++ ro.ril.avoid.pdp.overlap=1

That shouldn't harm anything:

+++ # update the acoustic table for Buzz NEL lab testing
+++ ro.ril.update.acoustic.table=1

My own changes which didn't cause any trouble before:

--- dalvik.vm.heapsize=24m
+++ dalvik.vm.heapsize=32m
+++ ro.compcache.default=0

That shouldn't have to do with the problem, too:

+++ persist.sys.rotationanimation=false
+++ persist.sys.scrollingcache=2

but that one probably?:

+++ # Lock dirty_ratio to 20 when USB is mounted for improved transfer speed
+++ ro.vold.umsdirtyratio=20

So I simply commented out the stuff I guessed to be responsible (no. 2 and 6) and restarted - no success. Reboots again when turning on 3G:rolleyes:
[Wildfire Q&A, Help & Troubleshooting] Doddster:
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.

Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)

Any ideas?
[Wildfire Q&A, Help & Troubleshooting] eventcom:
that sounds exactly like LucidSomnia's report in the thread I've used to continue with my experiences. I can't tell if my solution (if it was any and not by accident) will help you but it shouldn't hurt to give it a try...
[Wildfire Q&A, Help & Troubleshooting] Doddster:
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.

I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.

P.S The camera works occasionally, I get viewfinder but no way of taking picture and if I install the 3rd party app Line camera I can take pictures with no viewfinder.
[Wildfire Q&A, Help & Troubleshooting] eventcom:
As you can see in my posts (in three threads) I've done a lot of stuff, too, what did the trick in the end (if it was not just by accident) was

Total/full/mega wipe (except SD card)

mounts & storage / boot, cache, system, data, sd-ext

advanced / dalvik-cache

main menu / wipe all (factory reset)

flash a fresh ROM

flash a different radio (older one in my case)

Boot

after that just the same procedure

mounts & storage / boot, cache, system, data, sd-ext

advanced / dalvik-cache

main menu / wipe all (factory reset)

flash a fresh ROM

flash a different radio (newest in my case)

It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).

But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.

If that's the case with you I'd give my method a try and if that doesn't work I'd do an RUU (the safe flash variant first of course).
[Wildfire Q&A, Help & Troubleshooting] Doddster:
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)

Steps followed:

(In recovery)

Wipe Cache,

Factory Reset.

Flashed CM7

Flashed Radio (3.35.19.25) using CMrecovery 2.5.0.7

Thanks eventcom :)

**Dunno if I'm gonna have the balls to install CM9 again after all this :P
[Wildfire Q&A, Help & Troubleshooting] eventcom:
glad to hear that it helped :D

I'm not really sure about what exactly caused the problem (at my side at least) - but even if CM9 on the Wildfire is highly experimental this particular problem doesn't look to me that it has to do with the ROM. I slightly remember a few people having this problem after flashing a different ROM but in most cases this could be solved by a simple restore. Did you also use some tweaks - like a different kernel, RAM scripts or something similar?
[Wildfire Q&A, Help & Troubleshooting] Doddster:
nope, nothing different from what was included on the CM7 and CM9 builds. :/

It's frustrating as ICS actually runs ok on the wildfire, it's only till it hits the radio or camera hurdles it lets itself down lol

I'm getting another phone soon so I will be using my Wildfire for development and I'll put all my effort into helping us wildfire'ers run ICS with no hassle.
[Wildfire Q&A, Help & Troubleshooting] Slymobi:
Im gonna stick my neck out here, all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects

1.overclocking too high.

2. V6 supercharger scripts.

3. Cm9

Could be coincidence or could be the reason!

Forum fishing.... Who's biting!
[Wildfire Q&A, Help & Troubleshooting] Doddster:
CM9 in my case, it's defo something to do with the radio.

I have no probs running max clock on CPU and I haven't touched other scripts
[Wildfire Q&A, Help & Troubleshooting] Slymobi:
Have you ever had the problem with the radio outside of cm9?

Ive never tried cm9 nor had issue with any of my radios but have had bootloops when i tried the v6 scripts back in my early days.

Forum fishing.... Who's biting!
[Wildfire Q&A, Help & Troubleshooting] eventcom:
Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.

Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
[Wildfire Q&A, Help & Troubleshooting] Doddster:
Nope, never any problems with my radio pre CM9. Problem occurred straight after the flashing, overclocking wouldn't have been the problem as the flash was fresh and CPU settings were at default.

CM7.2 running stable thus far, ICS is nice but as someone said previously, flashing twice a day isn't an option especially as its for my only phone at the moment :D
[Wildfire Q&A, Help & Troubleshooting] eventcom:
haha, you probably can read my thoughts: that's exactly what I've been about to ask you :p

and now we're really getting somewhere... do you strip things out?

--- EDIT --- any special reason to keep the 264 min with your processor and not to go at 176?
[Wildfire Q&A, Help & Troubleshooting] eventcom:
nice. Can you give some information what can be dropped without issues? I'd like to do some tests but after my latest experiences I want to do that sloowwwly and not without a strategy LOL. (BTW being too lazy did cost me some additional work again today while flashing the Sympfinity kernel).

I see, well I'm still testing and 176 might be too low for me, too. Regarding the Battery: I'm rarely away from a charger longer than 4-6 hrs. No idea if going down from 710 (adjusted again) to 633 would do much. I'll probably test that, too. (On the other hand I'm also not sure if more speed makes the phone really snappier...

I'd also like to know if you're satisfied with the LeWaOs ROM? But I better should ask that in the respective thread...
[Wildfire Q&A, Help & Troubleshooting] Slymobi:
Yes im satisfied with lewa, its a very good rom.

Forum fishing.... Who's biting!