yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Chirality:
Clock speeds aside, the A5 is clearly a better SoC. The CPUs in all three are pretty much the same, dual-core Cortex A9s on a 45nm process. It comes down to the GPU. The A5 has a better GPU simply because it's pretty much the multicore version of the GPU in the OMAP4460. Between the OMAP4460 and the Exynos 4210, it's more difficult to say. The PowerVR540 and Mali400 have different strengths and weaknesses, so I won't speculate here.

I would also suggest that you modify your original post. It contains quite a bit of misinformation and clearly many people have read it and taken it to heart. That's not a good thing, and I hope you will do the responsible thing and try to reverse the misinformation that you've spread.
[Samsung Galaxy Nexus] Dmw017:
Omap vs Exynos ? The latter doesn't support HSPA+ or LTE.
[Samsung Galaxy Nexus] tylerdurdin:
This is hardly anything to do with "performance".....and not to mention that ICS is a TON more dependant on GPU renders....hardly a place it has any room to fall short.
[Samsung Galaxy Nexus] mr mystery:
Exynos will do 21Mbps, HSPA+ ;)
[Samsung Galaxy Nexus] mysterioustko:
You are correct, I mistakenly read the the 4470's bandwidth when researching the 4460 (the 4470's bandwidth was referenced in the same TI interview where they discussed the 4460).
[Samsung Galaxy Nexus] king23adrianc:
i dont know anything much about detail stuff of gpu.

but isnt the stock galaxy nexus gpu is underclocked from 384mhz to 307mhz?

and compare to GS2 with mali, i think gpu is only 200mhz.

and people saying mali is better, but is it true that with mali clocked at 200mhz still beat powervr540 clocked at 307mhz?
[Samsung Galaxy Nexus] mysterioustko:
The Mali400 is definitely a more powerful gpu. The thing is that point really doesn't matter because there isn't any software that requires that sort of horsepower. The gpu found in the galaxy nexus is more than capable of handling gaming and other gpu intensive tasks. This is simply a case of software not having caught up with the hardware yet. Those who boast about the gpu are akin to someone boasting about owning a rocket launcher for protection. Sure the rocket launcher is more powerful than a shotgun, but it really isn't needed and in the end, both the shotgun and the rocket launcher get the job done.
[Samsung Galaxy Nexus] darkhawkff:
I've read the manual for the 4460. The reason given by coolbho3000 in your linked post doesn't jive with the manual. DCC should be enabled by default, since it NEEDS to be enabled for frequencies above 1 GHz. (Page 408 of the manual, under Clock Management Functional Description, "Figure 3-50 includes the clocking adjustment scheme for DPLL_MPU. To obtain MPU_DPLL_CLK frequency higher than 1 GHz, the CLKOUTX2_M3 output is used instead of the CLKOUT_M2 output.") Knowing this, I'm not sure what coolbho3000 is doing....I'm not a software developer, but I know hardware very well. Unless TI is putting out incorrect information in their datasheets (it happens, and I've dealt with it before, but I doubt this is....), I'd wager the reason coolbho3000 is having problems is because something is fundamentally wrong. In fact, take a look at page 410. At the bottom, in Table 3-89 it even shows the frequencies and makes reference to the fact that Duty Cycle Correction (DCC) must be on in order to reach 1.2 GHz. Page 411 has more info, since the frequency is still dependent on the SYS_CLK reference, but even so, if you look through, any time the SoC is clocked at (actually) 1000 MHz or higher, DCC is enabled. I'm not entirely sure what the SYS_CLK is for the GN, but I'd wager it'd be easy to figure out what he's doing wrong with his settings once you know it. I'd be more interested in seeing if we could hit the 1843 MHz that's shown in those tables.....

/shrug

And, just for the sake of argument...

http://www.ti.com/pdfs/wtbu/OMAP4460_ES1.x_PUBLIC_TRM_vL.zip

Direct link to the document I'm referencing. Have a look yourself....
[Samsung Galaxy Nexus] Chirality:
From the stock arch/arm/mach-omap2/dpll44xx.c:

if (rate <= OMAP_1_5GHz) {
/* If DCC is enabled, disable it */
v = __raw_readl(dd->mult_div1_reg);
if (v & OMAP4460_DCC_EN_MASK) {
v &= ~OMAP4460_DCC_EN_MASK;
__raw_writel(v, dd->mult_div1_reg);
}

if (rate != dpll_rate)
clk->parent->set_rate(clk->parent, rate);
} else {
/*
* On 4460, the MPU clk for frequencies higher than 1Ghz
* is sourced from CLKOUTX2_M3, instead of CLKOUT_M2, while
* value of M3 is fixed to 1. Hence for frequencies higher
* than 1 Ghz, lock the DPLL at half the rate so the
* CLKOUTX2_M3 then matches the requested rate.
*/
if (rate != dpll_rate * 2)
clk->parent->set_rate(clk->parent, rate / 2);

v = __raw_readl(dd->mult_div1_reg);
v &= ~OMAP4460_DCC_COUNT_MAX_MASK;
v |= (5 << OMAP4460_DCC_COUNT_MAX_SHIFT);
__raw_writel(v, dd->mult_div1_reg);

v |= OMAP4460_DCC_EN_MASK;
__raw_writel(v, dd->mult_div1_reg);
}

Instead of checking for OMAP_1GHz like it should be for switching to the M3 output with DCC, the code is checking for OMAP_1_5GHz.

Here's their justification for doing it:

commit eac0b0094edb42732c4ab095357d8ca9679e94bc
Author: Nishanth Menon <nm@ti.com>
Date: Tue Sep 20 15:45:29 2011 -0500

OMAP4460: DPLL: use DCC bypass until 1.5GHz

DCC is to be bypassed untill 1.5GHz now that samples are trimmed
for DPLL operation upto 3GHz.

Change-Id: I55b7b52656e1630460d84876b994fce561d17b40
Signed-off-by: Nishanth Menon <nm@ti.com>

commit 0e8f213258af4127f7299ed897aeafc20040c7ee
Author: Colin Cross <ccross@android.com>
Date: Tue Sep 6 12:38:25 2011 -0700

ARM: omap4: dpll44xx: Don't use DCC at 1.2GHz

Transitioning from DCC on to DCC off seems to cause rare lockups.
Disable DCC for 1.2 GHz, where it is not strictly necessary.
To lock the DPLL @ 2.4 GHz DPLL trim-override needs to be used.

Based on patch by Vishwanath BS <vishwanath.bs@ti.com>.

Change-Id: I6979f2e5e0d8368c99a466215e6a1153510a6516
Signed-off-by: Colin Cross <ccross@android.com>

Looks like the manual is out of date. With the current OMAP4460 samples, DCC is no longer necessary for DPLL up to 3GHz.

Also, I think you are misreading the table. 1843MHz is one of the possible clocks of the M2 DPLL. It is not a possible clock for the MPU. With the DPLL clock at 1843MHz, the clock divider must be set so that the MPU runs at 921MHz.
[Samsung Galaxy Nexus] darkhawkff:
If that is in fact the case, then their (just released) document I linked is wrong, which does surprise me. It was revised in December 2011, so if that didn't get changed, that's really bad on TI's part. Either way, it seems it's going to be a crap shoot with this SoC's now on the GN when it comes to what the real speed is. And sadly, it puts a rather sour taste on top of a slightly sour taste for me personally. Maybe I will wait out another phone now.
[Samsung Galaxy Nexus] FirstToTheLast:
Can i just ask (and a one word answer will suffice), does it matter which is better given the margin is so small?

Cause i think if you theoretically put the three chipsets in discussion into my phone i wouldnt have a clue which is better. Or would i...?
[Samsung Galaxy Nexus] Chirality:
Looks like they put this info in an errata.

http://www.ti.com/pdfs/wtbu/SWPZ017A.pdf page 53
[Samsung Galaxy Nexus] djcr33p:
Lol, wow... just wow.
[Samsung Galaxy Nexus] Chirality:
You are still incorrectly claiming that the 4460 is more power efficient without providing any supporting evidence.
[Samsung Galaxy Nexus] Wingzer:
Exactly.

More enough over his whole "the GPU is weaker but it dm because nothing takes advantage of it" argument is moot.

I want my phone to be as future proof as possible and if you do a lot of gaming on your phone you most likely get an iPhone 4S or a Galaxy S II purely because their GPU's are much more capable.

Look at Infinity Blade 2 I would love to see that ported to Android and running on a Galaxy Nexus at the same resolution as the iPhone 4S 960x640 and see the outcome.

read: The iPhone 4S would be producing a much much higher framerate if not capped.
[Samsung Galaxy Nexus] darkhawkff:
And that right there provides the evidence needed to know they (TI) must be binning the chips. What all this really means, is there is some 'hardware' issue that keeps the chips from running at 1.5 GHz (due to DCC). Long story short, skip this phone and wait for the next Nexus for Verizon most likely (for me atleast). It's going to be a long wait, I can see that already.
[Samsung Galaxy Nexus] jaketurbo:
Where?

You've shown that a debounce issue exists and can easily be corrected. What does that have to do with the chip being unable to run at 1.5ghz?

Most chips have certain tolerance issues that can easily be corrected and this has nothing to do with clock speed.

Or were you talking about the L2 cache issue? Which was corrected in a new version of the chip quite a considerable amount of time ago?

Which also has no bearing on clock speed...

---------- Post added at 07:27 PM ---------- Previous post was at 07:20 PM ----------

Why is everyone saying the chip is in fact a 1.5ghz chip?

Just because the clock speed of the chip can theoretically be that... doesn't mean that they have high yields of chips running at that speed.

A percentage will be within tolerances to be released at 1.2ghz, some may go higher but the chip in the nexus is branded 1.2ghz.

The ones that meet the 1.5ghz tolerances will be sold as such...

I've yet to see any evidence that the chip has been clocked down.
[Samsung Galaxy Nexus] darkhawkff:
You read one post and ignore the other 5 posts me and Chirality had about the issue. You completely ignore everything, and jump to the assumption we're talking about debounce routines in hardware? Really? The chip was debuted as a 1.5 GHz chip. Ever heard of underclocking? They do that for a variety of reasons, but usually it has something to do with power saving. All phones do this actively to save power during different usage states. Seeing as how everything states 1.5 GHz for the SoC itself, but the phone is only doing 1.2 GHz, one would tend to assume they underclocked it. Needless to say, that was the conversation that Chirality and myself had. Did you bother reading half the posts with information about the spec documents and addendums? Judging by your post, you skipped it all....

BTW, thanks Chirality for pointing me to the addendum. I had seen it mentioned in the other documentation, but couldn't find it online for the life of me. TI's website is not easy in any manner to navigate.
[Samsung Galaxy Nexus] Rawat:
Spot on. Hit the nail on the head pretty much.

Well, apart from "The A5 has a better GPU simply because it's pretty much the multicore version of the GPU in the OMAP4460" - that should read OMAP4470, no?
[Samsung Galaxy Nexus] Chirality:
In terms of processing units yes, but since the OMAP4460 has the SGX540 at 300MHz and the A5 has the SGX543MP2 at 200MHz, I'd say the A5 is closer to 2x the OMAP4460 GPU performance than 2x the OMAP4470 GPU performance. The higher clock makes up for the lower parallelism to some extent.
[Samsung Galaxy Nexus] mohitrocks:
Your sources are outdated. http://www.anandtech.com/show/4686/samsung-galaxy-s-2-international-review-the-best-redefined/14 doesn't even have the 4460...

---------- Post added at 02:37 AM ---------- Previous post was at 02:31 AM ----------

I agree with Wingzer. Even though nothing utilises it yet, the Galaxy S II or the iPhone 4S is more future proof (in terms of games) than our Galaxy Nexus's are. It pains me to say it, but I may have to return my Galaxy Nexus and wait for the Samsung Galaxy S3 :(
[Samsung Galaxy Nexus] qreffie:
Where are these ridiculously awesome smartphone games that are so compelling that they'll tear me away from my 360? Where are these games that are so awesome they make me want to return my perfectly good phone with brilliant display, the best developer support, and the latest updates for software and application compatibility so that I can get maybe 10 more FPS on another phone with slightly different hardware?

There is no such thing as future proof. SGS2 is still king of the benchmarks but we all know it's going to be dethroned shortly with quad core and the SGS3. Here's something else I know, the Nexus S still runs games like a boss. No it's not going to stand up to the new kid on the block when it comes to power, but when it comes down to "will this app run?" the answer has always been yes and it got a yes before phones that were released before and after it did.
[Samsung Galaxy Nexus] jaketurbo:
??? I've not ignored anything.

Your friend Chirality used page 53 as an example of why they were "binning chips"... page 53 is about debounce.

Also your bit about

The chip can be rated from 1.2 - 1.5 ghz... in the manufacturing process, only small yield of the chips will be ok at 1.5ghz for a prolonged period of time. 1.2ghz will be achievable on most of the chips produced.

Some of the chips will run at 1.5, others probably won't... Texas instruments will just sell batches of them at 1.2ghz and do less manufacturing testing on them... as all that will be needed to confirm from a batch would be 'does it run', rather than will it run at 1.5ghz for a prolonged period of time.

The process for identifying which chips run ok at 1.5ghz and can be sold as 1.5ghz will be more expensive - longer to perform and more intricate in terms of selection of chips.

So basically you'll probably get 3 (or more )different buckets of chips filled up at the end of the production line:

1. Broken chips

2. Chips that run (1.2 ghz and above)

3. Chips that run consistently well at 1.5ghz

RTFM... it even says in the manual that your mate above attached the chip can be rated from 1.2 - 1.5ghz. Then go read some basic information on manufacturing of electronics, MRP or even manfucturing in general.
[Samsung Galaxy Nexus] Chirality:
That's page 43. You are about 10 pages off.
[Samsung Galaxy Nexus] darkhawkff:
I'll be blunt. I'll RTFM when you learn to actually read a whole thread before posting. Just a word of advice, it might help you not look so bad in the future....
[Samsung Galaxy Nexus] coolbho3000:
The fact is, though, all (or almost all) of these chips would run at 1.5 if DCC worked.
[Samsung Galaxy Nexus] Chirality:
What I'm wondering is whether the OMAP4460s were binned before the DCC issue was discovered. As you know there's the CONTROL_STD_FUSE_PROD_ID_1 register containing the SILICON_TYPE field that's independent of the value set in CONTROL_STD_FUSE_OPP_DLL_1 register for the MPU_DLL_TRIM_FREQ field. Could the 4460s be doubled binned, once according to silicon type, and again according to DPLL locking performance? The 4460s in the GN are "standard performance (1.2GHz)" rather than "high performance (1.5GHz)" for the silicon type, as well as trimmed for 2.4GHz DPLL rather than 3GHz. Could there be two things working against getting 1.5GHz OC?
[Samsung Galaxy Nexus] dario3040:
Kind of depends on how you look at it, the Mali 400MP has a little bit higher pixel processor power, while the SGX 540 is much better at geometry, I would say the Galaxy Nexus has the best GPU.

Comparing the Galaxy Nexus to the Note shows how much faster it is.
[Streak 5 Q&A, Help & Troubleshooting] 01bernie:
I replaced my screen after I broke it by following the instructions in this pdf guide: (New user, so I cant post links, sorry!) His site begins with rdtk, perhaps you have seen it.

The guide refers to a 'brown part that can flip up' when removing the digitizer cable connection but I couldn't see it. However his photos show it clearly:

(New user, cant post links, sorry!)

However I didn't find those photos until after I had reassembled it.

The Streak boots OK (so the on/off button works!) but gets to the screen where I have to enter a pin code and I then discovered that the screen is unresponsive to touch input. So I cant get past the pin code screen. The screen itself is working fine but is no longer touch responsive.

I have removed the case a couple of times, but the brown flip part is clearly missing and I wonder was it always missing or did I break it.

The cable seems a fairly loose fit so perhaps without the flip up part it is not making a good connection.

Any ideas how I can fix this predicament?

Thanks, Bernie.
[Streak 5 Q&A, Help & Troubleshooting] andy1weir@hotmail.co.uk:
Maybe try removing your new screen and comparing it with old make sure all connections are the same, also check all connections are secure just incase something aint slotted right
[Streak 5 Q&A, Help & Troubleshooting] Alexanderbooth:
The clip thing is defo there, Ive done it loads of times, the thing does go in quite tight, but maybe you ripped out the old screen without unclipping it, and in turn the old connector had broke off inside the clip, and its blocking the connection to he new screen?
[Streak 5 Q&A, Help & Troubleshooting] 01bernie:
No, the old cable is intact and there's nothing blocking the connector. I suspect I misunderstood the instructions I was following and ripped out the ribbon without unclamping the flip up brown clamp, I was trying to flip up what I thought he was referring to but now see it was just part of the cable. Thus I damaged the clamp and it's now gone. I suspect that my problem is that the ribbon cable is now not being held securely, so in a desperate bid to save this I think I will try and make a tiny wedge and wedge it on top of the cable to press it down securely onto the contacts in the connector.

If I could source a bricked Streak, I might be able to salvage the brown clips and re-use them but chances of getting one in Australia are low.
[Streak 5 Q&A, Help & Troubleshooting] illa215:
i had the same problem, just get a sturdy business card and cut it up into a little piece and use that to wedge it on top of the cable
[Streak 5 Q&A, Help & Troubleshooting] 01bernie:
Thanks illa, I will try that.
[Streak 5 Q&A, Help & Troubleshooting] taho7:
I am here to kneel before you.

I did the exact same thing due to following a guide that didn't really emphasize this very important point about the clamps.

At first I wasn't sure.I thought I had just screwed up or may be my replacement screen was bad.

Upon closer inspection I broke two of the clamps,and noticed that the one that attaches to the digitizer was just a little loose. Sure enough the biz card wedge did the trick.

Thank you ! :D
[Samsung Epic 4G Touch] undefined:
Has anyone gotten any GBA emulators working? Ive been trying and trying with gameboid but I can get NO roms to load and I really want to play pokemon on this screen, the size and AMOLED should be a much better experience than the actual system itsself
[Samsung Epic 4G Touch] richard.tufty:
GameBoid is running fine on mine, I didn't do anything special to get it running...
[Samsung Epic 4G Touch] 3meister:
Runs fine for me, but closes the rom every 10 minutes.
[Samsung Epic 4G Touch] undefined:
Perhaps its the BIOS / ROM i'm using? Could either of you send me a PM? I don't think BIOS would be appropriate to talk about in the public forum
[Samsung Galaxy Nexus] catpunt:
I had the s-wave tpu case on my evo 3d and i loved it, however on the gn it's a little loose in the middle on the edges for my liking. The evo 3d one was extremely snug and firm. Other than that gripe it's very thin, and seems just as protective, not to mention only 3 bucks on ebay.

The greatshield protector took over a week to get to me on the west coast from sf planet. Installation wasn't any more difficult than other similar products. It comes with 3 protectors which is nice. I like the finish a lot, it seems pretty thin and smooth. Though it extends nearly to the edge of the glass, it doesn't seat firmly the last millimeter or two all around. My guess is this is due to the glass contour and is why sgp chose to cut their protectors smaller, though if I had to decide, I'd go with the extra protection but it is unsightly.
[Android Q&A, Help & Troubleshooting] shankz_xperianzo:
hey ppl need a help....

evrytime i add a fb account and fbinside 2.0 and after sync it i get a contacts(social phonebook force close) msg...in the display mode...i cant add or edit any contacts...i have tried various roms like wolf n miui and cynogen mod bt the problem is still there....i tried 2 fix permissions thru xrecovery bt da problem is nt solved yet....
[Samsung Galaxy Tab Plus] dds517:
I'm interested in getting this tab, and I've checked it out at bestbuy. My only concern was the web browsing lag I noticed. I've seen this also in some reviews of the tab. The lag happens when you click on a link at it'll take a good 5 seconds before it starts to even load the link. Viewing the pages is no problem, but going from link to link seems to be sluggish. I noticed this on my original galaxy tab as well.

I also noticed that the web browser for some reason dims the backlight. I know this was an option for the original tab, and I looked for some separate brightness setting but none was found.

Any owners want to chime in?
[Samsung Galaxy Tab Plus] pakalrtb:
There are so many good alternative browser in the market that I do not bother to use the stock one any more. I recommend Miren Browser.

P_
[Samsung Galaxy Tab Plus] drksilenc:
i almost never use stock browers. also it depends on the connection speed and what you are trying to view. usually on the demo models at best buy they show all flash video. if you change that setting to on demand so you click the flash it speeds it up greatly
[Samsung Galaxy Tab Plus] dds517:
another bug i saw today... let me know if it exists. Go into any web browser and try to scroll at the very right edge of the screen in landscape. I tried this and it did not scroll. I tried this on the left side and it was no problem. I tried this after noticing the backspace on the keyboard doesn't register half the time. It seems like something is wrong with the screen on the right side. I'm wondering if the firmware update fixed this issue too.
[Galaxy Note GT-N7000 General] dt33:
For those who are interested: http://www.youtube.com/watch?v=4RgG3bl82HE
[Click General] basinizadussun:
1.maple paint is my favorite but it seems that does not saving any notes to sd card unfortunately..

2.genial writing.

any other good alternatives?
[Click General] bull500:
Colornote

Evernote
[P3400 ROM Development] arunmag:
hai friends.. i downloaded few rom from here... all wer loaded with unwanted resources. i want a clean wm 6.5 rom.. please help me with it.. i have old gene....
[P3400 ROM Development] Hakim Rahman:
tries just of Rom Wm 6.5 by karan http://xdaforums.com/showthread.php?t=540985
[P3400 ROM Development] arunmag:
thank you...

i need any official rom ported fir my gene
[P3400 ROM Development] arunmag:
ii downloaded hypercore ..

m ii able to cook my own rom...

how to get official wm6.5 rom.

can be able to port other model rom to my device....
[P3400 ROM Development] BOOTMGR:
perhaps it is impossible to port other device's but you can surely cook your own ROM.....
[Hero CDMA Q&A, Help & Troubleshooting] ericcue:
ive been trying to root my hero with clock mod recovery using regaws method but all i get when i start hero root is an error message saying

"unhandled exception"

" Length cannot be less than zero.

Parameter name: length"

can anyone help me please? id really appreciate it! thanks :)
[Hero CDMA Q&A, Help & Troubleshooting] Bierce22:
i would just try z4root its a one click app that has always worked for me when i had the hero then get rom manager free from the market to install clockworkmod.

http://www.4shared.com/android/yFnkXST9/z4root130.htm

theres a link for z4root if it hangs on applying root shell just pull your battery and try again it sometimes takes a couple tries
[Hero CDMA Q&A, Help & Troubleshooting] ericcue:
I tried looking for rom manager but its not supported on 2.1 which is what I have on my hero

sent from my synergy EVO 4g
[Hero CDMA Q&A, Help & Troubleshooting] ericcue:
kinda forgot about this thread... but still looking for a way to get clock work mod w/out having to use adb. im running 2.1 on my hero and rom manager isnt supported on 2.1. any suggestions? thanks in advance!