yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] th0r615:
Don't put your faith in stretchmarks. At the end of the day if one GPU scores higher then the other on smart bench but both run the games you wanna play with no problems then whats the point of having the bigger number?
[Samsung Galaxy Nexus] @rbiter:
And are you running @ 308 or 384?
[Samsung Galaxy Nexus] zephiK:
Same reason why people overclock their computers / obsessed about not getting 100+ fps. Oh the eye can't notice any difference above 30 fps but people want 250 fps anyway.

Keep in mind that the benchmark that you're using is not optimized for ICS. So its a unaccurate result. Benchmarks don't mean anything. It's real-time performance that really matters.
[Samsung Galaxy Nexus] guthrien:
Most people seem to notice the difference between say, 30 and 60fps in video. The eye is pretty capable of noticing sluggishness because it happens in contrasts, even if they can't count each frame.
[Samsung Galaxy Nexus] bash_array:
Lol. The human eye cannot discern above 30 fps. 31fps and 60fps look the same. ;)
[Samsung Galaxy Nexus] bash_array:
Correct me if I'm wrong but the gnex is software rendered not hardware so it will bench out badly. There are roms out now that force hardware rendering... the quadrant scores jump from 1500 to 2800
[Samsung Galaxy Nexus] guthrien:
Lol (?) I can't seem to find the scientific or even opinionated "proof" that people can't tell the difference. Even subjective experience tells me that people can tell the difference in displays so I don't know why it's treated as a glib fact by you. There seems to be a lot of tests and experiments out there just by doing a cursory search. Can you point me to the definitive evidence?
[Samsung Galaxy Nexus] xNEM3S1Sx:
If the image switches between black and white each frame, the image appears to flicker at frame rates slower than 30 FPS (interlaced). In other words, the flicker fusion point, where the eyes see gray instead of flickering tends to be around 60 FPS (inconsistent). However, fast moving objects may require higher frame rates to avoid judder (non-smooth, linear motion) artifacts — and the retinal fusion point can vary in different people, as in different lighting conditions. - Wikipedia

For object motion, 30 vs 60 can be a huge difference, most noticeable when turning.
[Samsung Galaxy Nexus] Zzim:
I guess that's my issue N64oid lags a lot and does not have smooth game play when in goran mountain in major's mask or just in general, but on my Galaxy S II Epic Touch 4G I get no lag at all.....none...sucks that sprints 4g and 3g blow
[Samsung Galaxy Nexus] Zzim:
Sooo would this be the same for any app or game? Its going to render using the CPU(software) and not use the GPU....? That sounds a bit strange but in this case would be the reason why it runs so slow.
[Android Q&A, Help & Troubleshooting] Rob45:
I am looking to make some money with my apps, at least to get back some of the cost in time I spent on them. And I DON'T want banners or any other annoying visuals.

This ad network is doing advertising without banners, they're doing audio ads that are supposed to be non disruptive. They're also offering high rev-share.

Anyone worked with them and can give a recommendation?

It's http://sellaring.com
[Android Q&A, Help & Troubleshooting] nadavfima:
I once thought of implementing this, but I think it's too disruptive. way more than banners.
[Vibrant General] Tynen:
I just want to make sure everyone knows that 911 does no work on roms that are based off the AOSP, and it NEVER HAS WORKED. You can read a better description on this post:

http://xdaforums.com/showthread.php?t=1385613&page=7#68

The only ROMs that 911 has worked on are ROMs based off of official releases from Samsung. I would suggest for your safety flashing back to a Samsung based ROM.
[Vibrant General] ipnekgs:
Went back to Bionix 1.3.1, at least GPS works now. (Yeah I know why it did not work in CM7, just saying that is not too bad going back to a Samsung ROM :/)
[Vibrant General] bobshute:
E911 doesn't work. 911 works, different.

E911 is if you have no sim card or have no service and can make emergency calls only.

I lived a long, long time before 911 existed and I can't remember the last time I had no service to t-mobile and had to rely on att towers for an emergency call.

I'll take my chances, thank you.
[Vibrant General] Jasonhunterx:
Ohh now I get it I thought it did not work completely now I get it now I understand how having no source code would effect that!
[Vibrant General] Nabeel10:
Does 911 calling work on MIUI?

Sent from my Vibrant
[Vibrant General] SamsungVibrant:
Kind of scary that some people are barely now finding out that their custom flashed Vibrant doesn't make 911 calls. I wonder how many other people who don't frequent the forums often still have no clue their phone doesn't make 911 calls.

It still blows my mind why a disclaimer wasn't posted in large bold font in the CM thread when the stable was released.

Anyway I still think they did the right thing to stop support. Maybe Samsung will surprise us with source or a leak soon and we can get support back.
[Vibrant General] bobshute:
according to your link:

"The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail"

What makes you think it is working on all the I9000 ports to the Vibrant and not just Official Samsung Vibrant Roms if the above statement is true? back to KB5 I guess.

I'm not saying E911 works, but why would it work on a I9000 rom with I9000 framework running on a Vibrant if it's a incompatible framework issue?
[Vibrant General] HeavyA:
As long as I have been on MIUI, I have had to call 911 a few times. Each time, it would not even connect. Luckily I had my wife's phone handy.
[Vibrant General] SamsungVibrant:
My best combo.

Well when I found out that 911 doesn't work on CM/MiUi I switched back to 2.2.

I have been back on 2.2 for a while now and my phone is actually fast without the frequent crashes and problems that came with CM/MiUi.

If you want a fast lag free experience with working 911 I suggest the following semi-stock combo.

(before any of these steps always good idea to backup your nv_data.bin so that you don't lose your imei ever)

1) Flash stock deodexed/rooted KB5, found in the development section

2) Flash the stock KB5 kernel with voodoo lagfix included in the kernel. Also in development section. Make sure you go into recovery and enable Lagfix after you flash the Kernel. Also make sure you disable Lagfix anytime you want to flash something new.

3) Touchwiz is very laggy, so use LauncherPro instead. LauncherPro found in Market.

The above combo has been fast and lag free. 911 works and the GPS works also as best as it can.
[Vibrant General] Woody:
+1 on this. I have had same experiences but with different set up. KB5 and Voodoo and am completely happy with performance, speed and stability. On Toxic D9 RC3 Bali X kernel. GPS lock 9 birds down to 10 feet.
[Vibrant General] atinm:
Actually, 911 doesn't really work either - you will get no audio during the call and will have to wait for a call back if your phone doesn't actually freeze when your call fails (which also happens sometimes during the 911 call on the Vibrant when using any code derived from our source). E911 is just an extreme case of the same issue. Our advice, go back to a Samsung derived framework for the Vibrant on the Vibrant.
[Vibrant General] atinm:
The framework is incompatible with tmo - it works fine on Galaxy S and Captivate, which is one reason it took longer to find out because we didn't actually have Vibrants to test on. I don't know of any AOSP builds that didn't start with our code (CyanogenMod), and therefore it would be safe to assume that all AOSP builds for Vibrant cannot do (E)911 calls correctly. Our suggestion is to go back to a Samsung or Samsung derived ROM that is using Samsung's framework for the Vibrant on the Vibrant.
[Vibrant General] bobshute:
Thank you atinm. I have appreciated all your work to make our Vibrant phones better. This 911 issue has people spooked. But outside of the CM team (you and coolya). Its not understood very well. I'm dumb sometimes but I can't figure out how this would not affect non vibrant stock rooms as much as aosp roms.
[Vibrant General] claucXC:
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.

I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo. :(
[Vibrant General] jrafael:
why don't you call 911 yourself ?

If your call doesn't goes thru for any reason they will try to call you back, if that's the case then just answer the phone and tell them that you bought a used phone and you were testing 911 calling.

Simple as that, I did it myself and my result varied between asop roms from phone crashing and only solution was a battery pull to connecting but not audio plus new years force close party. :D
[Vibrant General] SamsungVibrant:
If 911 doesn't work in CM and MiUi do you think it would work in ported i900 Gingerbread roms? I'm not 100 percent certain but I would think NO.
[Vibrant General] claucXC:
CM7 and MIUI are AOSP and i9000 Gingerbread is international Samsung if I'm not mistaken. Hence my question.
[Vibrant General] Smokexz:
If you are like me, Cyanogen,of works great as media player for Vibrant.... happy with it, never use it as a phone anyways.

Sent from my Xoom
[Vibrant General] boystuff:
old news.. this has been pretty common knowledge for almost a year now. But good job compiling all the info together i suppose?

luckily in the 12 years i've cellular devices i've ha to dial 911 twice.

and even then you can call non emergency and get forwarded to local enforcement based on your Cell tower triangulation.

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

Most i9000 roms "are" samsung. However if you read the OP of the rom itself you are looking to flash the Dev will usually tell you what source the rom is built off of.
[Vibrant General] renardk764:
For those interested...a little info on 911.

E911 stands for enhanced 911. E911 differs from 911 in that location information is transmitted to the 911 call center. This is for landline phones attached to a physical address. For wireless call, there are two types of data transmitted. The old standard (and still in use on older cell phones and with some of the newer carriers) was call Phase 1 Wireless Data (WPH1). It was simply the location of the Cell Phone tower the cell phone radio attached itself to. The current standard is called Phase 2 wireless Data (WPH2). This provides GPS location data to the call center. Depending upon the carrier, it can be actual GPS data from the cell phone chip or GPS data triangulated via cell phone towers.

Further more, none of the AOSP ROMS (miui or CM based) that I've tested work with 911. The Cyanogenmod team did the right thing pulling their work. Genesis3 (props to Genesis3!!!!) continues to dig into the problem and I'm his canary. I have personnaly verified that Simply Honey Gingerbread 2.3.4 JVR + Modem JVS works as well as NeoBuddies ICS V7. Other than that, it's a waiting game for source or a fix.

Ken
[Vibrant General] CM Wave:
Thanks for testing. Good to know at least one ICS dev has this sorted out.
[Vibrant General] djf8:
About that.....if 911 is truly fixed on ICS than shouldn't CM9 be able to be supported?
[Vibrant General] renardk764:
Actually I think the 911 working was an accident. I'm fairly confident that no one has a complete understanding of how 911 works on the Vibrant. Genesis3 is exploring different theories with CM7 and will be investigating the ICS traces once I get them to him.
[Vibrant General] djf8:
Outstanding news.....Once CM said they wouldn't be supporting the Vibrant anymore I almost fell into a deep depression haha.

I'm glad to hear there are still people looking into the problem and that it could mean CM support might be back in the future. (or at least working kangs of it anyway)
[Vibrant General] dk_gh0st_:
I don't see why cyanogen would quit cooking Rome just for this reason. I can see them feeling responsible if anything happened but they should just put a warning on their posts. I've never had to use the E911. I agree and disagree with the CM teams decision.

One of our strengths is our lack of direction- Eric Schmidt
[Vibrant General] strictlyrude27:
Is it just audio routing that works, or also E911? Can you call 911 without a SIM? Does position information also get transmitted?
[Vibrant General] geoffcorey:
It all has to do with liability (even with all the disclaimers and warnings, things can happen) but it's also principal (sp?) Based. If something involving emergency service isn't working right, don't distribute it.

Sent from my HTC Sensation 4G
[Vibrant General] Exel:
I don't understand a lot of the Vibrant community. They want Froyo, they get it.. they want Gingerbread. No Gingerbread from Samsung/T-Mobile.. they still want it.. CyanogenMod comes around.. they get it.. they're happy, they praise CM, they find GPS not working well.. they flame CyanogenMod.. blame them for it, right? Seems like the easiest thing to do when infact, we should thank all the CM devs for bringing life to our phones. Don't expect, just accept. Be grateful for what we've been able to get.
[Vibrant General] jrafael:
+1000000000000000000
[Vibrant General] frecklefacebcb:
So the regular 911 worked on NeoBuddy's ICS v7? Will it continue working then on v8? Is this somehow related to the modem used?

Thanks.
[Vibrant General] djf8:
I have asked in a couple of threads and sent some pm's to a few of the CM teams devs asking if CM support would be reconsidered.

I only ask since 911 and e911 seem to work on all the latest ICS builds.

I haven't got any response back yet. I wonder if they're just talking among themselves about it at this point.

Sent from my SGH-T959
[Vibrant General] foxtroop11:
I really hope they do reconsider, especially since I'm talking my Vibrant over to Germany and could care less about 911 over there... I realize to many people need and should have it working in the US
[Vibrant General] fsrick:
I did not upgrade my wife's vibrant for a while. If I understand correctly, all those gingerbread roms will have gps or 911 problem, the only safe bet is to stay with froyo 2.2 rom, am I correct?
[Vibrant General] Moped_Ryder:
I would say that is correct. I ported a Samsung I9000 ROM but frankly I'm not sure if 911 will work.

Id love to see a sticky with ROMs listed if 911/E911 work on it. Only problem is getting people to call 911 (against the law?)
[Vibrant General] fsrick:
I would love to see that too. But to test if the 911 works reliably is really a problem :) .
[Vibrant General] alh.titan:
[ROM][CM9][KANG]CM9 Vibrant Build 15 1/30/12

Sorry, I'm very new to all this.

So does anyone know if [ROM][CM9][KANG]CM9 Vibrant Build 15 1/30/12 has the 911 working?

Thanks,
[Android General] xoltrix2000:
Interesting article, in my opinion I think it's true.

http://www.pcmag.com/article2/0,2817,2397729,00.asp
[Android General] gflare:
Wow, that's an excellent article, and it seems to be very true.
[Android General] xoltrix2000:
Haha I sensed the sarcasm! Ofcourse it's true, what I meant was I should have known this about the vendors and their "promises".
[Android General] paszczi:
I think that the updates are currently the most problematic thing in Android eco-system. Carriers just don't give a sh*** - have an old phone, come to us and buy one, have a long contract, well that's too bad. I just wish smartphone vendors would release all the drivers for their devices and let the community handle all the updates.
[Android General] zelendel:
Well it is not just the phone manufacturer as they would need to get the OK from others as well. They don't use their own hardware for things like radio, bt, screen ect.
[Android General] hyperspace290:
Does this really surprise anyone? The carriers and the manufacturers both make money from abandoning old phones and selling new ones. The only way that Android is going to have a consistant upgrade schedule is if someone who doesn't profit (Google?) makes the ground rules. If the manufacturers want to licence it then they need to follow the rules. If they use the AOSP code then they have to release code under its terms.
[Android General] jim93:
people need to call out google and push them to be competent
[Android General] GazaIan:
I'm at the point where I'm just completely Nexus, I dont even want to get near another OEM and their bloat, custom frameworks, etc... Go the way of the Nexus. Its a great thing to do.
[Android General] zelendel:
And do what? They have no control over it once they sign the contract and if they don't carriers don't carry the phone. Then it goes the way of the Nexus 1.
[Android General] wire103:
Oh come on, things are way better now than ever. Have you seen the near endless list of devices getting ICS?

I still remember when phones never even got an update in their lifetime.

But you can always buy smart and get the updates from the hard core XDA developers who never seem to fail to deliver.

Lars
[Android General] zelendel:
Just because the OEM says it will be releasing it at least in the US it is still the carriers call. Take a look at the inspire. HTC released a new buld for the device but ATT refuses to release one for the inspire
[Android General] gfsincere:
Nexus phones seem to be the way to go.

Sent from my Galaxy Nexus
[Android General] mistermentality:
Can't Americans download open versions like europe?

Dave
[Android General] zelendel:
No the The US versions have some minor diffs that the Euro versions do not. We dont get updates from the OEMs. Carriers control it all. ITs either carrier or custom rom ported for our devices
[Android General] HaloMediaz:
My phone never got Froyo over the air. It didn't even get a 2.2.1 update. As for GB we had to port it from the i9000 (i have a vibrant).Same with ICS. It really sucks, because batterylife is not as great as it could be. Android will probably never be released to all devices at once and my understanding is that the "GOOGLE" line of phones gets full support for atleast 2 years.
[Android General] mrolp:
As for now, who wants upgrades should buy Google Nexus phones (not Motorola).

I take my hat off to Sony, they are excellent (but not perfect because of Xperia Play).
[Samsung Galaxy Nexus] lilRikki:
I'm getting "<App name> could not be downloaded due to an error" when I try to install and/or upgrade apps (any app) from the Android Market on my device and then the app gets stuck in the "Downloading..." section under "My Apps" but doesn't appear to be downloading and I can't stop it (or any of the other ones that have queued up there). However, I am able to download them from the browser based market to my device.

I have tried on both the network and wifi. I have tried clearing the cache of the Android Market app and clearing data from my Download Manager. I have also tried a Factory Reset. All a no-go.

Anyone else having this issue?
[Samsung Galaxy Nexus] braingravyuk:
I had a similar issue when I first got my Nexus though a factory reset fixed it.. Perhaps try running adb logcat and see if anything interesting turns up there?
[Samsung Galaxy Nexus] DarthPiggie:
I am also having this issue here...I don't know what to do; numerous factory resets did not help at all.

System:

Stock with CWR and ROOT

---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------

Here is the Logcat snippet:

E/Volley ( 5413): [318] BasicNetwork.performRequest: Unexpected response code 5
09 for https://android.clients.google.com/vending/api/ApiRequest
D/MetricsUtils( 1125): [PrefetchHelper.syncPhoto ******************* in:86627 ou
t:180 time:279]
E/Finsky ( 5413): [1] 1.onErrorResponse: Error when attempting direct download
of asset [com.google.android.apps.maps]. Error=[com.android.volley.ServerError]
D/dalvikvm( 5413): GC_CONCURRENT freed 1949K, 9% free 24873K/27271K, paused 3ms+
12ms
I/dalvikvm( 5413): Jit: resizing JitTable from 8192 to 16384
D/MetricsUtils( 1125): [PrefetchHelper.syncPhoto ******************* in:66354 ou
t:180 time:270]
D/Finsky ( 5413): [1] DetailsDataBasedFragment.rebindViews: Page [class=Details
Fragment] loaded in [167346 ms] (partial? false)
I/WindowManager( 177): createSurface Window{418f8f88 com.android.vending/com.an
droid.vending.AssetBrowserActivity paused=false}: DRAW NOW PENDING
D/dalvikvm( 5413): GC_FOR_ALLOC freed 1191K, 9% free 24931K/27271K, paused 60ms
I/dalvikvm-heap( 5413): Grow heap (frag case) to 24.454MB for 39618-byte allocat
ion
[Samsung Galaxy Nexus] braingravyuk:
Just had a look back on a previous thread with people having similar problem: http://xdaforums.com/showthread.php?t=1353161

One of the people fixed it by clearing the proxy setting on the APN settings for the carrier, maybe give that a try.
[Samsung Galaxy Nexus] DarthPiggie:
I doubt that is the isssue;

It happens to me on WiFi and on 3G/4G

Besides: I am on Verizon, that fix wouldn't apply =\

Thanks though, maybe it'll help someone else.
[Samsung Galaxy Nexus] lilRikki:
Booted into recovery and wiped the Dalvik cache, still not working.
[Samsung Galaxy Nexus] DarthPiggie:
Still having issues on both Droid X and GNex;

Logcat is throwing Unexpected response code 509 from server.

Factory resets did nothing.

---------- Post added at 10:04 PM ---------- Previous post was at 09:11 PM ----------

Looks like I found my problem:

According to this page

http://100pulse.com/http-statuscode/509.jsp

The problem is that I was downloading too much today from the market. There must be a quota on how much one can download in a 24-hour period.

I'll wait until tomorrow to try again.

First day excitement must have gotten the best of me, lol. I was downloading like crazy. I had over 200 apps downloaded. Then I unlocked the bootloader, which wiped data. All of those apps had to be redownloaded again! lol
[Samsung Galaxy Nexus] lilRikki:
Good find!

I am now able to download without issues and, given that I started getting the error roughly 24 hours ago, I'm guessing that this was probably my problem.

Thanks!
[Samsung Galaxy Nexus] diomark:
I factory restored 3 times before running into this thread. Will wait until tomorrow now :)
[Samsung Galaxy Nexus] DarthPiggie:
Yea I think Google shoukd do a better job of communicating limitations like that. One shouldnt have to dig so deely.

Just out of curiosity, how much were you guys downloading? I was having too much fun with LTE.

EDIT:

Here is some more information, or at least more specific info.

http://docs.cpanel.net/twiki/bin/view/AllDocumentation/CpanelDocs/HTTPCodes#509 Bandwidth Limit Exceeded
[Samsung Galaxy Nexus] lilRikki:
I had a massive amount of apps on my Droid X (I got pretty lazy towards the end and stopped uninstalling stuff I didn't use) so I think my issues hit when the market tried to download all of them at once.

Do you think this is a cap in place by Google or by Verizon?
[Samsung Galaxy Nexus] Grant H:
Why in the holy heck could you possibly have 200 (different) apps? I just dont understand this.
[Samsung Galaxy Nexus] DarthPiggie:
Yea it's definitely a cap placed by Google. Just like that, my apps started installing again =D

I'm happy now!
[Samsung Galaxy Nexus] DarthPiggie:
Well.... there was a ten cent promo; I just took advantage =)

Also have a number of games and other tools. It's a smartphone. To each their own!
[Samsung Galaxy Nexus] lilRikki:
I did the same thing..... :p
[Samsung Galaxy Nexus] dubeyy:
I was getting this error yesterday and today as well.

No idea why - I don't download very many apps (I have 3 pages total). Finally got it to work by enabling wifi at my house. Go figure. Wouldn't work on my office wifi either.