yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] BarryH_GEG:
This ad banner...

Until something more concrete appears, I'm going with this from the article...

"Of course an ad banner is hardly conclusive"

http://www.androidcentral.com/ad-ba...y-s-iii-could-feature-new-exynos-chip-and-lte

From the New Orleans event. Note the use of the word "optimized."

“Samsung Mobile is planning a U.S. version of Galaxy S III, optimized for the fastest LTE and HSPA+ networks in the U.S., which will be available in the summer of 2012. Exact timing and retail channel availability is not being announced at this time. We believe the Galaxy S III is the most anticipated product in the 20-year history of Samsung Mobile; therefore, we will continue to share information as it becomes available.” – Samsung

This could play out two ways...

1) Samsung's developed a GSM LTE-capable version of the Exynos chip and it will be used everywhere it can be. In North America that would mean Rogers, AT&T, and Sprint. Since CDMA's so limited, the VZW SGS3 would likely use the S4 chip. T-Mobile would likely get S4 also because S4 supports AWS and when faced with the same choice in the SGS2 they went Qualcomm vs. developing their own AWS radio. If Samsung was going this route, there's no reason they wouldn't have said so at the UnBoxed event.

2) LTE and AWS SGS3's will all be S4. Either because Samsung didn't have time to integrate LTE, couldn't match the S4's fantastic battery life, or that it might actually be cheaper. Samsung builds great SoC's but they have no track record (yet) in radios. There were no repercussions (other than some customer disappointment) when Samsung went this route last time. Also, when they did, they waited until right up to launch to disclose that the U.S. market wasn't getting Exynos (except the non-LTE AT&T version).

I have no idea which way it'll go (and neither do any of you). I wouldn't bet odds in Vegas based on a misplaced banner ad.
[Galaxy S III General] bbeelzebub:
If you think AT&T is going to fragment the sales/updates as far as one that is quad-core/hspa/3G and one that is Dual-Core/HSPA/LTE, you are mistaken. Ain't. Gonna. Happen.

There will be one model, one that is usable on the LTE network.
[Galaxy S III General] SlimJ87D:
Yeah sure. Too bad that's not true with the SGS2 and the SGS2 Skyrocket....
[Galaxy S III General] bbeelzebub:
That was last year. We're into the LTE (True 4G) era.

Regardless. I'll have fun watching some of you waiting on that Quad Core.
[Galaxy S III General] SlimJ87D:
Again, no evidence whatsoever that you will be getting a Exynos + 4G LTE radio with Verizon.
[Galaxy S III General] BarryH_GEG:
That U.S. introduction of the SGS2 was one of the strangest launches ever. First, it took Samsung and the U.S. carriers six months after the UK launch to bring it to the U.S. Then all but the AT&T version were totally different phones based on the Asian Celox and SGS2's in name only. If you remember the launch event, the T-Mobile version was locked in a Plexiglas box and not allowed to be touched. VZW skipped the SGS2 entirely. On top of that, two weeks after it launched, AT&T announced the SkyRocket which was a Celox variant and closer to the other U.S. carrier versions. Samsung’s in a much more powerful position than they were last go round so hopefully the phones will be less molested and the introduction better synchronized.

When the OG SGS2 launched on AT&T they hadn't even lit up their first LTE city. It would be strange for them to launch another high-end HSPA+ phone with as fast as they are growing (and pushing) their LTE network. But, based on the SGS2 launch, anything's possible.
[Galaxy S III General] SlimJ87D:
I think the transition to LTE was difficult for Samsung and satisfying their customers. Then having to design multiple variants on top of that some with the S3 and LTE radio and some without it.

It takes hours and hours of meetings, designing, quality control, etc. I could already predict all the trouble that all parties had to go through, Samsung, Sprint, T-Mobile etc. If it wasn't for our wide population, I wouldn't be surprised if Samsung said "the hell with the US" and just stuck with releasing one type, the international version for everyone else.
[Galaxy S III General] bbeelzebub:
I never claimed otherwise.

I think there is sufficient proof out that Verizon will be getting a Qualcomm S4, just like Sprint... just like AT&T..... just like T-Mobile.
[Galaxy S III General] BarryH_GEG:
Almost certain.

Likely as their CDMA/LTE like VZW.

Competely unknown.

Completely unknown but AWS is easier on S4.
[Galaxy Y GT-S5360 Themes and Apps] Andeia:
Hello people I need your help.

I just have a new Galaxy Y Duos (ST-62102) and while testing it I enabled the "animations" in Setting->Display->Animation. Then after disabling them I still have active the application/home button transition animation in TouchWiz.

Already searched and tried everything, also several factory resets and the animation is still on (it wasn't before I enabled the animations).

I can root it and edit some files, but don't know which setting to check and edit.
[Defy General] 2Pints:
Help..

bootmenu Recovery v5.0.6

checking MD5 sums...

followed by a long wait, then

MD5 mismatch!

this occurs each and every time, on every back up, i need to use the backup in the next few minutes help.
[Defy General] 2Pints:
ive tried wiping everything to go back to CM7, and now im stuck ont he motorola logo, ive even tried going back to the nordic sbf file, adn its still stuck, help.
[Defy General] AnTerNoZ:
witch was the last sbf u flashed before CM7? u flash with windows or with Linux? installed last driver for the defy? first, make sure that ur battery don't run out of power, or u have to make a factory cable to get juice in ur defy.

Defy mit Android 4.0.4 CM9 RockZ
[Defy General] oSandmaNo:
If you are sure your backup is good them generate a new md5 sum and replace it in nandroid.md5
[Defy General] 2Pints:
now ive got a little bit of time, ive just carried out an basic experiment with CWM recovery using two different cards..

Card 1 ( my main card) 32Gb Sandisk calss 4 ( genuine) CWM recovery fails each and every time, it creates a back up, but something goes wrong as it always neds in md5 missmatch upon restore, the card has about 8.5Gb free

Card 2: the original 2Gb card, calss unknown, marked 2GB micro SD, made in taiwan, again this created a back up fine, and the back up restored without a hitch.

So its looking like something to do with the 32GB card, although in normal use there are no problems.

following this my advice would be to check the back up works ( make a back up in CWM, then restore the back up before any major rom flashing/changing, and then save the back up to your pc.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] madshabz:
Hi Devs, just to start off I am not a dev and there am not able to solve the question below.

I am a proud owner of the Galaxy S2 4G i9210t the Australia Telstra version, we are able to flash all gingerbread roms from the i727 and they run perfect except for one little problem when we flash the gingerbread rom from i727 we lose our capacative button it completely stops to function so to get it back to work we have to restore the original boot.img from our nandroid backup and then the rom starts to function perfectly.

So I decided to try your ics roms from the i727, so obviously it has the same problem everything works except of the capacative buttons so the problem is we have to restore the boot.img from the nandroid backup, but the boot.img is from a gingerbread roms so the rom does not boot.

So the ics roms work perfectly except for that one problem and I believe the problem is somewhere in the boot.img. I hope someone can help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
you're SOL (sh1t outta luck). U need an ICS kernel for your device, and until u get one (from an ICS release) or source drops for our device and someone ports it, its not gonna happen.

so basically, no. Sorry bud.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] madshabz:
thanks buddy, what about for the gingerbread kernel can anything be done with it so that we don't have to restore original boot.img every time we flash a gingerbread rom to get the capacitive buttons working?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jarmezrocks:
Hi,

I just stumbled across this thread as I was looking for ROMs for an I9210 that I need to repair, just something that sprung to mind and that was a similar situation between the Samsung Galaxy S, Samsung Vibrant and Samsung Captivate. Although the Vibrant and Captivate were running Cortex-A8 core and the Galaxy S was running S5PC110 and yes the boot.img files were completely different, I found that the ROMs were essentially the same except for the same issue you were having. As a work around I figured out that the key mappings could be switched around to allow the back button to function correctly ;)

I know that this is dead thread and I am necro-bumping like a zombie, however if you run into this issue in the future it might be something to consider? Especially considering ROMs for I9210 stop at ICS now and I would assume that the i727 has gone on to Jellybean due to it's popularity in the US?

In the Vibrant the keys were found in /system/usr/keylayout/

The other things that were different between them were the modules them selves, in the S1 they were located in /system/lib/modules although I am fairly certain this is a symlink not an actual location but it will give you or someone else something to consider when thinking of porting any roms over in the future.

Edit: If you want to port ROMs, you need to go back to the closest possible denominator and work backwards. What I mean is that you download two standard firmware packages for I727 and I9210 both in Gingerbread 2.3.6 and then diff the both packages against each other. From the files that differ, if you cannot simply trade them in/out because of significant changes in Android versions then you can resort to decompiling the files that differ from each device and then proceed to diff the decompiled code. It's not impossible it's just very difficult and time consuming. I have managed to port ROMs from I9100(Galaxy S2) to I9000(Galaxy S), I9020(Nexus S) to I9000(Galaxy S), I897(Captivate) to I9000(Galaxy S) and T959(Vibrant) to I9000(Galaxy S).

James
[HTC Amaze 4G] rachelm920:
Does anyone know where I can pull the background to the sense 3.6 clock? I have the numbers in fusion.apk but it seems the black portion and white portion is not there.
[HTC EVO 3D] grd_42:
On NocturnalsXi36 Sense3.6ICS v102 ROM there was a "Media Sync" option in "Connect to PC" (see attachment). However in version 104 It is no longer available and I can't find it in any other ROMs, and can't find any info on it. Is there a way to to get his back by taking some files from v102 and replacing them in v104, or any another way?

Thanks in advance.
[Xperia Play Android Development] Atarii:
This add-ons are installed at your own risk. Please make a nandroid backup before flashing anything.

[ SuperCharger ]

I've modified the services files to fix the OOM Priorities for ICS ROMs. This will allow you to install the SuperCharger script and get it to 100% without any additional work. :)

Full credit goes zeppelinrox for his awesome SuperCharger script.

This add-on does not include the SuperCharger script. Go to here to get the latest ICS versions. Copy it to your sdcard and follow the instructions to install and set-up.

The currently recommended versions are:

V6_SuperCharger_for_Android-Update9_RC8.2.sh

3GTurboCharger_Installer_Update_3_RC8.sh

KickAssKernelizer_Tweaks_Installer_Update_3_RC8.sh

Downloads:

CM9 FXP119: CM9-FXP119-SuperCharger

CM9 FXP121: CM9-FXP121-SuperCharger

AOKP 1.1: AOKP-1.1-SuperCharger

AOKP 1.2: AOKP-1.2-SuperCharger

PlAyOSP 1.42: PlAyOSP-1.42-SuperCharger

[ Auto-brightness Toggle ]

This will enable the auto-brightness toggle in the Display section of Settings.

Experimental add-on.

Recent changes in CM9 means that this may no longer function. This will also not work with Keiran's kernel. Leaving it up for users to test.

Downloads:

CM9 FXP119: CM9-FXP119-Auto-brightness

If you intend to use any parts of this in your own work, please contact via PM first
[Xperia Play Android Development] solomon4400:
Thanks for sharing atarii but can this mod also be used on playosp? Just asking cuz u only mentioned cm9 and aokp
[Xperia Play Android Development] Fat_boy555:
Thanks for the addons and mods..
[Xperia Play Android Development] Atarii:
The available ones won't work currently with PlAySOP, but I'll add an update that will work with it soon :)
[Xperia Play Android Development] fma16:
Does the Auto-Brightness toggle works with AOKPlay? :)
[Xperia Play Android Development] solomon4400:
Aaa thanks dude appreciate it playosp is the most fav
[Xperia Play Android Development] Atarii:
I've updated post #1 with the SuperCharged Services ready for the latest version of PlAyOSP (1.42) :)
[Xperia Play Android Development] solomon4400:
thankyou atarii for quick response and update really really appreciate it!!!!:D:D
[Xperia Play Android Development] fma16:
Hey, can you tell me what I have to do with your files? I don't understand. :)
[Xperia Play Android Development] d_zen:
1. Download the zip for your rom

2. Install in CWM

3. Boot into android

4. Download Script manager Ads from the market

5. Get the v6/3g Supercharger/Kernelizer/whatever scripts from here

6. Install using the instructions in this post
[Xperia Play Android Development] fma16:
Thanks! It worked! :)
[Xperia Play Android Development] netizenmt:
Can you modify the Supercharge file for AOKP 1.2 please? The 1.1 version just causes a bootloop.
[Xperia Play Android Development] Atarii:
Yes sure, I'll upload it tonight :)
[Xperia Play Android Development] xRegrets:
Worked for me on 1.2 though.
[Xperia Play Android Development] Android Is ReadyTo Play.:
Which option is the best for playosp ?
[Xperia Play Android Development] Atarii:
Just uploaded FXP121 SuperCharger and AOSP 1.2 SuperCharger add-ons post #1 :)
[Xperia Play Android Development] illuminerdi:
WiFi Afterburner doesn't work

I can't seem to get the 3G script to properly initialize Wifi Afterburn - even immediatley after I run it it says Afterburn is disabled, and after reboot and rerunning the script it reports that it still isn't done.

Is this a known issue, or just a bug in this rom?

I'm running AOKP at the moment, v1.2

Also the Supercharger script fails with an Arithmetic error when attempting to auto apply supercharger values, so I had to manually set them.
[Xperia Play Android Development] solomon4400:
atarii can we use aokp 1.2 supercharge file on aokp 1.3 rom?
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
Okay guys,

I've tried the v6 supercharger and it didn't really help me too much. Even though I believe that modifies these files, I was curious if maybe tweaking them further would do anything.

Just got done reading this thread:

http://xdaforums.com/showthread.php?t=622666

Decided to try messing with these values. The file in question is "lowmemorykiller" located (from the root dir) at sys/module/lowmemorykiller/parameters. You'll obviously need root and a file manager that has root and editing capabilites.

Opening this file will display 6 numbers seperated by commas. Each one of these refers to a minimum amount of memory assigned to different types of programs, processes etc before the memory manager will automatically close them.

My default numbers were:

7746,9720,11694,13742,15715,24709.

If you read the post in the link above, it will explain what each of these memory limits references. Don't change anything until you've:

A. Backed up your original file!

B. Understand exactly what you're doing (read the link above!).

For those that want to help me with this, try changing all of your values to the ones listed below. When you're done, the file should simply look like this:

2048,4096,5376,9984,11776,13312

Save these and see if it helps at all. I've noticed a bit better multitasking doing this. Most things like the browser or games are still loaded in memory when navigating back to them. I've noticed a few oddities, but overall I think its a slight improvement. Some apps still reload, but dont completely restart (such as the xda app). If nothing else, this is something we can start tweaking to find the perfect values for.

I AM NO DEVELOPER. That being said, I try to help myself and others as best as I can. Hopefully together we can all figure this out :)

Something to note: like the author stated in the other post, these values will probably be reset to the default values upon a reboot. This could theoretically be fixed by running an init.d script.

Dunno if this is anything or not, but I got tired of reading about the multitasking problems and wanted to at least see if there was anything we could do on our own.

PS this MIGHT be in the wrong subforum. Apologies if so mods!

EDIT: Use the autokiller app in the play store. Should make this 1000 times easier. Thanks for the (obvious) idea Tikerz! I should have known there was an app for this :o Make sure to check the "run on boot" option under preferences to preserve your changes!

EDIT #2: Found the default minfree numbers for both versions of the one X, as well as the stock ICS numbers:

STOCK ONE X AT&T:

7746, 9720, 11694, 13742, 15715, 24709

STOCK ONE X TEGRA:

8192, 10240, 12288, 14336, 16384, 20480

STOCK ICS 4.0.4 VALUES:

8099, 10132, 12165, 14213, 16245, 20295

These numbers are far too close to be the culprit, but there are at least two other files (that I've found) that control multitasking, as well as certain things at the kernel level. Gonna see what I can dig up...
[AT&T, Rogers HTC One X, Telstra One XL] Tikerz:
To make it easier, try AutoKiller from the Play Store. I don't have a One X, but am curious to know if changing the lowmemkiller values would fix the multi-tasking issues on a rooted One X.
[AT&T, Rogers HTC One X, Telstra One XL] Hunt3r.j2:
1. Those values will make it incredibly easy to run out of memory and you risk having more OS crashes by doing so.

2. V6 supercharger probably needs special mods in order to work right on ICS.
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
any suggestions as to what some better values would be? Like I said, I'm just experimenting until someone who knows more might chime in. I plan on continuously tweaking these just to see how it affects things

EDIT: Trying the "system default" memory settings inside Autokiller seems to be working pretty well so far. Gonna keep messing with it.
[AT&T, Rogers HTC One X, Telstra One XL] craig0r:
I've got mine set to 8, 16, 21, 39, 46, 52 in AutoKiller. Or 2048,4096,5376, 9984, 11776, 13312 in pages. Multitasking is slightly better, but still far from perfect. I had originally set it to 8, 16, 21, 20,22,24, which yielded a much greater improvement to the multitasking abilities of the phone, however app performance suffered in some games.
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
Yeah that's what I'm currently running too. Seems to help a bit at least. Looks like it's finding a balance between multitasking and available ram I guess... Thanks for the input.
[AT&T, Rogers HTC One X, Telstra One XL] ytwytw:
try use titanium backup to disable sense apps,

use a third-party launcher (nova launcher)

use system tuneup to adjust auto-kill memory level

it should help :)
[AT&T, Rogers HTC One X, Telstra One XL] Tikerz:
What was the default HTC setting on the One X?
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
Well I posted my original numbers in the first post, but those might have been modified from running the v6 supercharger script. If nobody gets back to you ill factory restore and let ya know when I'm home later
[AT&T, Rogers HTC One X, Telstra One XL] kravguy:
I'm about to redo supercharger as well since I loaded 1.82. Fyi, I came across an app called no bloat that'll let you freeze or uninstall system apps and also back them up automatically when you uninstall. Other real nice thing is that it remembers these apps and creates a blacklist of apps so that if you factory reset, it's a one click to uninstall all of them again. I use to use tb for things like freezing and uninstalling but this has been really helpful.
[AT&T, Rogers HTC One X, Telstra One XL] kravguy:
Fyi, default values for 1.82 are 7746,9720,11694,13742,15715,24709
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
Thanks for confirming those for us.
[AT&T, Rogers HTC One X, Telstra One XL] htcvarona:
What are the best values to put mine at?
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
I dunno if there are any "best" values. Just something to experiment with to see if it helps you. Try downloading the app autokiller from the play store and setting the values to the "system default" setting from within the app. These aren't actually the settings currently on your phone and they seem to help a few people at least a bit. Let us know if it helps you.
[AT&T, Rogers HTC One X, Telstra One XL] wesc011:
im rooted and using autokiller but my settings wont stick through a reboot. have "set on boot" checked and evrything
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
Forgive me for asking the obvious, but you've granted the autokiller app superuser privileges? The modified settings stick through a reboot just fine for me...

Maybe try uninstalling and re installing the app? Sorry man, I'm just having trouble reproducing this.

EDIT: have you gone in with a file explorer and checked the values manually?
[AT&T, Rogers HTC One X, Telstra One XL] wesc011:
they're fine right now, but i ran the supercharger to set on boot so i'm assuming that changes them every reboot. might just get rid of the supercharger script as i haven't noticed much improvement
[AT&T, Rogers HTC One X, Telstra One XL] Loneeagle14:
ah there ya go. Give that a try. I'll bet that'll be what it was. Let me know if this helps at all. This was just random (wishful) thinking, and mostly just something to mess around with to see. You might benefit from trying different values too
[Android Apps and Games] QBANIN:
Hi,

Because many unofficial ICS builds mount external SD card as /emmc which is not always accessible by media-scanning programs, I made a small app dedicated for Galaxy Note which (I think) can be useful for non-note user. If you want give it a try follow this link http://xdaforums.com/showthread.php?t=1652079 :)

Regards

QBANIN
[Captivate Q&A, Help & Troubleshooting] matwheeler:
Hello all,

Well to start I will let you know that my phone was in the phone + ! + compscreen mode and could not get out of it without constructing a jig. Once out of that mode via the jig and back into the true Download mode, I utilized that Samsung Captivate Total Stock UCKB2 one-click to put my phone back to stock. My intention is to flash to a rom (Haven't really decided 100% on one due to reading about a couple while researching the forums for a fix to my initial problem), however now I have a new issue....I think. I've flashed in the past and utilized Odin3 to flash Cog and Serendipity. Now, since I've used Heimdall I'm not sure what I need to do. I cannot get my phone to be recognized on my computer for Heimdall nor Odin. I've used Win7 desktop and laptop, and I've used my Macbook pro with Heimdall, and none of them see the phone. In addition, my phone works for phone calls and Wifi. No carrier data.

Think if I could flash a new rom, then most of the other issues might fix themselves.

So, any assistance would be greatly appreciated. Thanks in advance.

Martin
[Captivate Q&A, Help & Troubleshooting] mrhaley30705:
Reinstall your Samsung drivers. Heimdall's zadig driver over rides the Samsung driver.
[Captivate Q&A, Help & Troubleshooting] matwheeler:
Damn

I hate when you waste hours upon hours doing something, ask for help, get help/suggestion(that you have already done before), then return to do it again and it works. Thanks, I think I'm going to go give myself a black eye.

regards:rolleyes: