yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General (US Carriers)] chakra:
I googled it and found the proof right here. First link in google

http://www.google.com/url?sa=t&rct=...cgvf0VeX6lpv8Tl1A&sig2=EHLEJLiYlPMSt01XbgFN1g
[Galaxy S III General (US Carriers)] Chilled26:
Is this what you're talking about?

http://www.androidauthority.com/quad-core-galaxy-s3-with-more-color-options-101407/
[Galaxy S III General (US Carriers)] samueljohanson:
There is a quad core coming?? I haven't heard of it.
[Galaxy S III General (US Carriers)] vinuneuro:
The LG phone going to Sprint and ATT is going to have the Quad-core S4. I'm sure those aren't far away for the other mfrs too. Unless you're gamer it doesn't matter anymore. These processors are fast enough for everything else. Smoothness in the UI is down to OS optimization now.

---------- Post added at 01:46 PM ---------- Previous post was at 01:40 PM ----------

This is sounds like they're going to sell the Intl version in the US. Until we see LTE+Quad-core here, that won't be a big deal.
[Galaxy S III General (US Carriers)] cwalker29:
Close this thread! No proof, no links, just a guy that rush to post something he didn't fully read.
[Galaxy S III General (US Carriers)] M988:
i wonder if the quad core will drain the battery significantly more, right now the dual core LTE is decent for battery
[Galaxy S III General (US Carriers)] ExodusC:
Do people really feel the way OP does?

Something new comes out every week, it's folly to think you will always have the latest and greatest. That's just how the smartphone world works.

Notable exceptions would include shoddy business practices like the RAZR/RAZR MAXX incident, but this obviously does not fall under there.

Your best bet with Android is always to either:

A) Go with the most popular device

B) Go with a Nexus device

If you do either of those two, you can't go wrong.
[Galaxy S III General (US Carriers)] Jonbo298:
From what I got out of that article, it would be a non-LTE version of the S3 for the US for a quad core. I can't see Samsung pulling a Motorola this fast.
[Galaxy S III General (US Carriers)] uzii305:
http://www.androidauthority.com/quad-core-galaxy-s3-with-more-color-options-101407/

Yes it is the int version i guess.
[Galaxy S III General (US Carriers)] M988:
at least the devices share the same look, the previous S2 came in different sizes and shapes... with and without home button etc.. got pretty confusing
[Galaxy S III General (US Carriers)] Will of fire:
Best buy has it online only if you want to spend 800$ plus tax hey do it.
[Galaxy S III General (US Carriers)] vinuneuro:
Considering newegg is selling the Intl version unlocked for $599, BB is nuts trying to sell at that price. a non-LTE phone at that.
[Galaxy S III General (US Carriers)] M988:
i think you'd be surprised how many people would buy it from best buy... they "trust" the best buy name...
[Galaxy S III General (US Carriers)] BarryH_GEG:
Wow, three pages of discussion with basically nothing but an unclear statement to launch from. Does anyone think there's not going to be a SGS4 eventually? Or that Samsung isn't going to integrate LTE in to Exynos Quad like they've already said? If the SGS3 (all varieties) stays unchanged for six months that'll be a miracle based on the speed even better SoC's and "flagship" phones are being introduced. What's Samsung going to do once the S4 Quad with Adreno 320 starts appearing in other manufacturer's high-end phones? Enjoy your phones and worry about the future when it comes.
[Galaxy S III General (US Carriers)] hayabusa1300cc:
Damn, I'm glad I have an upgrade next month and next June. I love my s3 tho.
[Galaxy S III General (US Carriers)] JermsMalibu:
From my understanding of reading about the quad-core S4, it does have the better graphics, but it loses the radio part of the chip (what has LTE). Therefore, you can have 2 cores, decent graphics, and "power efficient LTE"; or you can have quad-core, good graphics, and a separate chip for radios and LTE (more power hungry). Also, I didn't think that chip was coming out till early next year.
[Galaxy S III General (US Carriers)] KillaHurtz:
Here's something official. Say thanks now children.......

http://www.qualcomm.com/chipsets/snapdragon
[Galaxy S III General (US Carriers)] Will of fire:
Lulz its like when the skyrocket came out
[Galaxy S III General (US Carriers)] eschelon:
There is always something better around the corner with tech. Sure, they've got quad S4s with US band LTE coming out, but we won't likely see them for 4-6 months.

And when those quad S4 phones drop they'll announce an octo-core 2 GHz phone with 4 gigs of RAM two weeks later. K, maybe that's a stretch, but you get my point. There will ALWAYS be a better phone around the corner that is in the early stages of announcement.

The S3 is arguably the best phone you can have in your pocket right now. Enjoy it :)
[Galaxy S III General (US Carriers)] Metfanant:
thats proof of nothing...just that there are better chips in the pipeline...did anyone doubt this?...i see nothing on that page saying Samsung is releasing an S3 with a quad-core in the US...
[Galaxy S III General (US Carriers)] tcb4:
yeah ha ha, I just leave my phone and power saving mode and it seems to perform well. Sure there is a stutter occasionally, but it keeps heat down and battery life up.
[Desire Q&A, Help & Troubleshooting] omsk_transmash:
Hello. I need your advise!

Situation:

Some time ago, i was using leedroid 3.x and it was very satisfactory

However, at one day, it said like "No SD card detected" at notification bar,

and I rebooted, it just looped Leedroid booting screen

Went to recovery, reflashed, factory reset, delete data all, new SD, no SD, did everything i can, however whatever rom i put in there it just looped booting screen

I went to HTC service center they somehow they fixed my phone although they knew i rooted mine.

Question:

1. Is this a well known problem? I just went to service center and living in fear because of my ignorance? I searched some articles about brick however couldn't find matching cases with me.

2. If not, I suspect that the custom rom "moved" some vital system files on SD, therefore any rom couldn't boot. How realistic my suspicion?

3. Most importantly, how can i prevent this? my phone was practically bricked and it was a pure luck i could get service.. and this time i flash a custom rom, i dont want to live in fear..

That's all. Thanks in advance !!
[Desire Q&A, Help & Troubleshooting] eddiehk6:
1. not sure how widespread it is, but sounds like sd card malfunctioning more than phone problem, or possible USB brick.

2. you're correct. Leedroid 3.x roms move parts to sd-ext. this is why new sd or no sd wouldnt boot. sd card has to be correctly partitioned using 4ext recovery (requires s-off) or gparted. do not use minitool and/or rom manager

3. don't know, at a minimum proper partitioning as stated above. it wasn't bricked at all because you could get to recovery. you probably could have flashed RUU, s-off and rooted again using revolutionary. in future, for any troubleshooting, consult bortak's guide stickied to top of Q&A.
[Desire Q&A, Help & Troubleshooting] omsk_transmash:
Thank you! I WILL Consult FAQ in XDA if something like that happen again.

(though at that time I didn't know about XDA T.T)

(not to mention i am struggling with so many acronyms and jargons going around here..)

And please if you can clear up one more thing for me..

So if the leedroid and/or any future custom rom i want to install, move some system file to SD card, and the SD card goes wrong,

same boot-looping happens, then

Go to recovery

Flash RUU (<- i searched and i think RUU means offical stock rom.. )

- This process restore system files and therefore go back to the state before rooting, so the phone can boot however it is not rooted

Root again since the phone is now a reborn virgin

Flash new custom room or whatever

Is this the logic behind reviving process? Did i understand correctly? I read the sticky article at the beginning of the forum, but i could not understand the full meaning behind troubleshooting process written there..

Thank you in advance!
[Desire Q&A, Help & Troubleshooting] eddiehk6:
yes the jargon takes some time to learn...the first thing to remember in any situation is that google is always your friend :good:

the troubleshooting guide has saved many people, takes time to understand it all. it's easy to panic when the phone is not booting ;)

RUU should be your last resort, because you lose all your data. keep your contacts backed up to google, and have a recent nandroid backup saved on your PC just in case. but yes RUU is a stock unrooted firmware for you to start fresh.

in your case i would have:

- made a nandroid backup in recovery

- backed up the sd card to PC

- reformatted and repartitioned the sd card (4ext or gparted)

- restored nandroid

not all roms move system files to sd card, check each rom's requirements in the first post (hboot, sd-ext partition size), or search the thread.
[HTC Wildfire S] GuestD2295:
Hi.

Yesterday I donwloaded MIUI 3.2 and was very much happy with it until I found out I cannot connect to my wireless. In fact my SSID is not even listed. The only ones I see are the ones with TKIP encryprion, but as much as I know/read wireless n + TKIP is a no-go. Tried to setup a connection manually with no luck.

I have no problems connecting to my wireless with CM9 alpha5, Hensemod7 and MIUI v4.

Searching forums did not give any desirable results.

My setup:

Wireless: TP-LINK 1043ND w/ stock firmware; wireless b/g/n; WPA2/PSK+AES

Phone: HTC Wildfire S A510e; S-ON; unlocked bootloader (htcdev)

Any help/info would be appreciated.

TIA
[HTC Wildfire S] GuestD2295:
SOLVED

The problem was wifi channel.

Some time ago I've set up my router to channel #13 whitch according to Wifi Analyzer was least crowded one.

Using CM9 alpha5, Hensemod7 and MIUI v4. ROMs this was not an issue. Switching to channel #1 solved my problem.

Hope this helps someone.
[HTC Flyer, EVO View 4G] Dwars:
hi

i'm planing to buy one of those...galaxy tab 7 or HTC flyer...

wts ur idea?which one is better?

thanks
[HTC Flyer, EVO View 4G] jprednik:
SG TAB 7 has working ICS already wheil Flyer well we all know how it is...

Hardware wise... do the math...

I wouldnt change Flyer for Tab regardles OS.
[HTC Flyer, EVO View 4G] Cor-master:
Neither. Get a Nexus 7, unless you have to have an SD slot. The Tab is a good value for the money, but the nexus 7 makes it look like a ripoff lol.

But if your wanting best bang for the buck with an SD, and a rear camera, than yeah get the Gtab2

EDIT: Wait what tab are you talking about? Samsung has 3 7 inch tabs. The orignal Galaxy Tab, the Galaxy Tab 7.0 plus, and the new Galaxy tab 2 7.0. Because if you're talking the original Gtab, than the Flyer is worlds ahead of that oversized Galaxy S1 phone.
[Galaxy S III Q&A, Help & Troubleshooting] andriis:
Hi!

Got my S3 few days ago, and already in first evening noticed annoying black spots in bottom of screen. At first thought that I broken it, but searching found many threads about this issue.

As i understand practically everyone has them, there's just difference in quantity.

I took picture of my screen displaying black screen in dark:

i.imgur.com/QYZEI.jpg (add http, as i cant submit links, i'm new here:)

What do you think? Guy at shop said that this is normal amoled issue.

I wouldn't mind about little spots, as i cant really see them, but those lines on right are really visible when watching videos in dark, even in not complete darkness, and is really annoying.
[Galaxy S III Q&A, Help & Troubleshooting] ph3nom:
I would say exchange it. I have this issue too but only visible when I'm in very dark environment lighting. And it only visible when im running gray background too. I have 2 ink mark visible to eyes and 3 very small one which have to squint my eyes.

-----------------------
[Galaxy S III Q&A, Help & Troubleshooting] B3311:
I think you'd be lucky if they changed it. I've seen much worse - mine, for example. Unless you always use your phone in the dark I wouldn't worry IIWY.
[Galaxy S III Q&A, Help & Troubleshooting] andriis:
Saw some pictures with muck less spots, so i thought that mine has lot.

I guess the I'll have to live with it.

Although this doesn't seem normal if you take into account price tag of this phone.
[Galaxy S III Q&A, Help & Troubleshooting] circuit89:
This seems to be common issue with phones using the amoled display. As long as it doesnt cause problems during normal usage of the phone, it will most likely not get replaced. There is a very high possibility that the replacement will also have the same issue.
[Galaxy S III Q&A, Help & Troubleshooting] Swagtabulous:
Yours are fine, I've seen worse from my friends S3.

I would rather having this problem over black crush/pixelation. Driving me crazy. Hopefully it'll be fixed by software update since screen filter app's able to solve it.
[Galaxy S III Q&A, Help & Troubleshooting] defdef2050:
Black Spots on S3

I use S3 for 8 months and black spots on the screen increases ....
[Nexus 7 General] shorit:
hello

i had also order for our site blogtech.in to get review:good: specs wise so good enough
[Nexus 7 General] morell2:
Processed through USPS Sort Facility

July 18, 2012, 3:19 am

KEARNY, NJ 07032

is now on NJ want to get that now

thanks!
[Nexus 7 General] gsrrr:
http://xdaforums.com/showthread.php?t=1765567

:confused:
[Nexus 7 General] sgt. slaughter:
as noted there is a thread for this already...
[Android Software/Hacking General [Developers Only]] kuisma:
I've integrated GNU/Linux Debian with Android in a way I've not seen anyone done before. By running Android in a chroot environment below a GNU/Linux Debian installation, I've got the best of both worlds.

This solution is primary intended for the experienced GNU/Linux hacker or app developer wanting full control over the Android device using a standard GNU/Linux environment.

For the novice wanting to run GNU/Linux for the fun of it, there are other less powerful solutions I'd recommend before this one. ​

A detailed HOWTO at http://whiteboard.ping.se/Android/Debian

Features

Full GNU/Linux Debian (or Debian based such as Ubuntu) installation with lots of apt-get:able packages

Full control of the Android environment from Debian

Simultaneous use of Debian as well as Android

Access the Android file system from your workstation desktop via ssh/sftp

No need to unmount/remount the SDcard accessing it via ssh/sftp

Android system untouched and unaware of any modifications

Android root file system no longer volatile, edits are kept between reboots

Critical file systems kept on SDcard for easy access in case of major f**k up

Graphic X11 Windows user interface, both client and server, local and remote, native, over SSH or VNC

Manage your Android device as any other GNU/Linux system

Architecture

Running X11 with Gnome via VNC on the ASUS Transformer
[Android Software/Hacking General [Developers Only]] fluxist:
Interesting work. Does the Android environment take much of a performance hit running under debian?

fluxist
[Android Software/Hacking General [Developers Only]] kuisma:
No performance impact. Running in chroot does not impair the performance, but the boot may take a second or two longer with the extra init scripts. If you move the /system and/or /data partition(s) to the sdcard, the speed of the memory card may affect the performance, but benchmarking a class 10 card and you'll get about the same disk-I/O performance as using the internal nand partitions, take or give. My tests revealed some operations actually was faster to the sdcard compared to the nand - but other slower (e.g. random vs sequential, large blocks vs small etc). Myself I moved /system to the sdcard for safety and /data for more app space, increasing it from 400MB to 4GB on my Xperia. :). Only keep in mind Android doesn't like more than four partitions on the sdcard in total.

The ssh server will of course consume some ram (less than 1MB rss for openssh-server, ~300kB for dropbear), but the ease of removing bloatware in this setup more than makes up for this, resulting in a faster phone than before.
[Android Software/Hacking General [Developers Only]] themac:
Great job man.

Just 3 questions :

1) What's the difference with this project ? Linux on Android Project

2) Your solution has Audio and GPU Acceleration ?

3) Are you planning a "really easy noob-aware stupid-free ONE CLICK" Tool ? :)

Thanks !

TheMac
[Android Software/Hacking General [Developers Only]] kuisma:
The difference is who's on top. In my solution, the Debian/Ubuntu is on top, owning the Android installation. This way you can use Debian/Ubuntu to access, manage, change anything in the Android world, and the Android world don't even need to be aware of Debian/Ubuntu, and does not need to be rooted or anything. E.g. you can edit the init.rc file from Debian/Ubuntu, save it as any ordinary file, and the next time Android boots, it's still there, your changes included. Or remove bloat-ware, or get file access via ssh/sftp to the entire file system, etc. This is not possible using the other solutions.

No. Yes. Well, no. All (local) access to the Debian/Ubuntu uses Android as a front end, and Android still owns all the devices (screen, input methods, audio device etc). If you've got a remote terminal access supporting sound, sure. But I don't think VNC does. I'll answer "no" on this question. :)

I don't know if I would be doing the world a favour doing this. Today it requires knowledge in GNU/Linux to install, and a user without knowledge enough can do lots of damage really quick, because of the power to make changes in the Android environment this solution gives. The installation complexity is kind of a safe-guard, I'd say.

Also I find this solution more suitable for the hacker wanting control of his Android, not the person only wants to run GNU/Linux. If all you want to do is run Debian/Ubuntu, I guess the Android-on-top-solution is better. More safe, anyhow.

Since the installation requires a new boot image, it would look more like a custom ROM than a OneClick App anyway. Different images for different phones etc.

You're welcome!

tl;dr

This GNU/Linux integration is:

Good for the GNU/Linux hacker wanting full control of his Android device.

Bad for the mortal user wanting to run GNU/Linux just for fun.
[Android Software/Hacking General [Developers Only]] rodrigolopezpeker:
Enviado desde mi GT-N7000 usando Tapatalk 2
[Android Software/Hacking General [Developers Only]] weasel5i2:
Confirmed working on a T-Mobile variant Samsung Galaxy S II (SGH-T989)!!

Took me a while to get the proper hardware-specific configuration, but I was able to do it. ^_^

I had to use some of the info here (http://xdaforums.com/showthread.php?t=1516051) - reason: "the default ramdisk offset is 0x01000000 while our phone needs 0x01400000."

To turn on framebuffer logging (where you see the kernel text scrolling by during initial boot) add this to the kernel cmdline:

console=tty0,115200 fbcon=rotate:1 fbcon=font:VGA8x8

(from http://xdaforums.com/showthread.php?t=829817)

Here's my command line after re-gzipping the modified initramfs:

./mkbootimg-sg2x --kernel boot.img-kernel --ramdisk ramdisk.gz --cmdline "console=tty0,115200 fbcon=rotate:0 fbcon=font:VGA8x16 androidboot.hardware=qcom msm_watchdog.appsbark=0 msm_watchdog.enable=1 loglevel=4" -o boot.img.new --base 0x40400000 --pagesize 2048

--Weasel5i2
[Android Software/Hacking General [Developers Only]] kuisma:
Neat! Added it the the list of verified devices, linking your post.

Yes, baseaddress and command line parameters can be a bit tricky, but they all are included in the boot.img. Myself I wrote a small hack to reverse the doings of mkbootimg.

This tool can be found in this thread.
[Android Software/Hacking General [Developers Only]] basha.ram:
I also follow the same thread default ramdisk offset 0x01000000 while our phone needs 0x01400000.

But I'd like to know where or how to set ramdisk offset( to 0x01400000). Is it hard coded some where?.

And how could we know that each hardware requires different ramdisk offset.
[Android Software/Hacking General [Developers Only]] kuisma:
"base" is the address of the beginning of ram memory your device's board is using, i.e. the hardware design. By supplying this information to mkbootimg, it knows how to layout and where to load the kernel, root ramdisk etc.

I've written quite a lot about how to find out this address, including a tool extrating it from your original boot.img

http://whiteboard.ping.se/Android/Debian#base

http://whiteboard.ping.se/Android/Unmkbootimg
[Android Software/Hacking General [Developers Only]] basha.ram:
Okay, reboot loop

steps:

1. Obtain base address from unmkbootimg

2. repack with mkbootimg

./mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "androidboot.hardware=qcom msm_watchdog.appsbark=0 msm_watchdog.enable=1 loglevel=4" -o newBoot.img --base 0x40400000

3. make a tar of new boot img

4. flash via ODIN -> successful

5. device restart-> reboot in a loop.

No Idea what went wrong.. can't even dump logs
[Android Software/Hacking General [Developers Only]] kuisma:
You get a boot loop when init terminates. The easiest way to see why, is to follow weasel5i2s example and enable frambuffer logging.

Also look for the file /android/log/boot.log at the SDcard and see if you have any clue there. If this file is non-existent, init terminated before stage two was launched.

As a last resort, after double checking all mount points, execute access (see "Common mistakes" in my HOWTO), and if you are not able to enable logging, you can clock the time it takes for the device to reboot. Then insert a "busybox sleep 30" in the init script and see if the boot loops take 30s longer time. If so, you know everything worked well up to this point, and you can move the sleep forward etc, until you've isolated exactly where it fails.
[Android Software/Hacking General [Developers Only]] basha.ram:
I see in weasel5i2 post using customized version of mkbootimg ( mkbootimg-sg2x ) and reason stated as "the default ramdisk offset is 0x01000000 while our phone needs 0x01400000."

how do we find that phone needs 0x01400000 as ramdisk offset.

---------- Post added at 04:40 PM ---------- Previous post was at 04:29 PM ----------

Could you please post your .config file enabled with framebuffer logging.. I followed the link in your post but I still see a back screen.
[Android Software/Hacking General [Developers Only]] kuisma:
Ah, you used the vanilla mkbootimg? Let's just take weasel5i2's word for it, ok? ;)

In mkbootimg.c you'll find a line;

Change it to

... compile, and you've got weasel5i2's customised mkbootimg-sg2x.
[Android Software/Hacking General [Developers Only]] basha.ram:
Thanks again,

That did the trick, my phone is up and running with custom-built kernel but the ramdisk offset value as 0x01400000 still remains a question?. I've no idea why or on what basis I need to change ramdisk offset.

Do you have any idea on how to find the correct offset value for individual phones.. in fact it was stated under weasel5i2's post which is pointing to anther post in xda.