yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] -aggie-:
Finally found out the answer to my question by asking in Androidforums

Alpha: for developer testing only; many inherent bugs that require other people who understand coding and such to assist with working on. Not ready for mass consumption, period. There can be different stages of useability here, but suffice it to say, that unless you know how to work under the hood (so to speak), don't touch an Alpha release.

Beta: Still in testing stage, but generally fit for public consumption as most major immediate flaws have been ironed out and just some system bugs remain with UI tweeks to be made as well. Like with Alpha, there are different stages of beta release as well, but they are all varying degrees of "generally useable but not entirely ready to be a daily driver".

RC: This stands for Release Candidate. Imagine a mother bird choosing which of her chicks to kick out of the nest first. The RC is the one she's chosen, so while it's still not fully baked in the sense that it isn't a completely air-tight product from both system and UI perspectives, it's definitely capable of being a daily driver for the avg person, as well as for the person with moderately sophisticated needs. Varying degrees of this step as well (RC2, RC3, etc), but typically when you're looking at a release candidate version of software/firmware, it's close enough to "fully baked" to where you can rely on it to work for you with consistency.
[HTC EVO 3D] yeti2242:
S3 processor

If they have same chip, is the only big difference removable battery and .1 inch bigger screen?
[HTC EVO 3D] swaze:
Basically.....and one will be here in 2 weeks and the other probably 4-5 months from now.
[HTC EVO 3D] Genjinaro:
So T-Mobile might be the only one with the original SoC this time around, given they're AWOL from the LTE bandwagon.
[HTC EVO 3D] ckoadiyn:
It isn't even a inch bigger od a screen it is 1/10 of a inch bigger
[HTC EVO 3D] No1ustad:
dah! samsung! don't do this.
[HTC EVO 3D] ckoadiyn:
Hmm ugly Samsung phone or decent HTC EVO hmm lol EVO wins
[HTC EVO 3D] NixZero:
evidently both samsung and nvidia dont have licenses for lte modems.
[HTC EVO 3D] ckoadiyn:
False the gn has LTE
[HTC EVO 3D] dylan6879:
With a ti omap processor. He's not talking about who built the phone. The exynos line and tegra don't do LTE
[HTC EVO 3D] NixZero:
wrong, the gn use a TI 4460 omap, not a samsung SOC.
[HTC EVO 3D] ckoadiyn:
Samsung still builds it so they have access to LTE radios they don't have the tech to integrate it in to their chips or license either way they could use a LTE radio.
[HTC EVO 3D] NixZero:
yeah, they could add an entire TI omap 4460 just for the lte modem...

do you think about what you write before clicking "submit reply"?

adding an external modem chip increase the building cost and motherboard complexity by several magnitudes, nobody want to do that anymore.
[HTC EVO 3D] aseercte:
S3 all day
[HTC EVO 3D] ckoadiyn:
They don't want to do it yet the new phone.by HTC has a microsim isn't that what all their other LTE phones havr and yes I do read ****
[HTC EVO 3D] bloodrain954:
The Gs3 will be available in the US in June... Learn to read.
[HTC EVO 3D] DJ1994:
Screens are the biggest difference for me. That and skin. Sense kicks touchwiz ass and the slcd 2 is better than the pen tile samoled HD screen. One of the users posted a picture of his gnexus a week ago and you can see the pen tile. Personally that would bother me so much it isn't even funny.
[HTC EVO 3D] bballer71418:
Please quote an article showing a June release date. Samsung said summer. That is a huge window. Especially with the S4 shortage that Qualcomm is experiencing a June Launch is unlikely.
[HTC EVO 3D] swaze:
LOL, thanks for showing me that you are unable to read. Because there is NOTHING stated anywhere that says ANYTHING about it being available in June. All you saw was a picture of a wall that said June, and you are making an assumption. I don't make assumptions, but I do state facts.

Fact #1. Galaxy S was announced by Sprint In June, it didn't come out until August 31st. It was announced Internationally MONTHS before.

Fact #2. Galaxy S II announced Internationally May 5th. Released on Sprint Sept 16th.

Fact #3. The Galaxy Nexus was released Internationally December 2011. It didn't come to Sprint until April 2012.

See the pattern. Ok thanks.
[Kindle Fire Q&A, Help & Troubleshooting] aarons510:
I have experimented with different ROMs and two versions of TWRP, and have installed the fff bootloader. (I have two working cracked-glass KF's that I picked up cheap in addition to a like-new one, so I can try different ROMs, etc., at the same time.)

I had presumed until recently that the kernel was a part of the ROM that was locked in by the ROM developer. It appears, though, judging by the two lengthy threads about a kernel 3.0, that users can install different combinations of kernel and ROM.

Can somebody explain, or point to an explanation of, the relationship between a kernel and a ROM and how one installs a desired combination of the two? Can one install a new kernel over an existing ROM, install the kernel and then a ROM, or is it necessary to do something else, such as editing a .zip file before installing it?

I realize that if I were to read a few hundred messages in a few threads, I might come up with the answers myself, but I might also transition from being a still-coherent old guy to one with senile dementia before I got to that point. Aside from my personal needs, though, it seems that an explanation of this matter deserves to be someplace where it can be easily found.
[Kindle Fire Q&A, Help & Troubleshooting] nchevaux:
The kernel is the main component of the operating system (ROM). The kernel is essentially the middle man between the applications and the processing being executed at a hardware level. Basically the kernel is the communicator between software and hardware.

With that said, ROM developers will use a specific kernel with their ROM. You are not locked in to use the kernel which came with "x" ROM. A new kernel can be installed. You want to make certain if you are using an ICS ROM you parallel it with an ICS kernel. If you flash an incompatible kernel that could be a problem. Some kernels work better with some ROMS. Different combinations produce different bugs. It's just a matter of tinkering until you find the combination which suits you best. Hash's latest 3.0 kernel (http://xdaforums.com/showthread.php?t=1591850) is popular and seems to be mostly stable with the ICS ROMS for the KF.

Installing a kernel is just like flashing a ROM although you don't need to wipe anything. Just boot in to recovery and select the kernel you've downloaded.
[Kindle Fire Q&A, Help & Troubleshooting] aarons510:
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.

Also:

? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?

? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
[Kindle Fire Q&A, Help & Troubleshooting] linktohack:
1. boot.img

2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.

Gửi từ Kindle Lửa của tôi qua Tapatalk 2
[Kindle Fire Q&A, Help & Troubleshooting] aarons510:
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.

I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.

So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
[Kindle Fire Q&A, Help & Troubleshooting] Dasanko:
I think he meant to tell you that the kernel is usually distributed as boot.img in the ROM zips.

The kernel is installed along with whatever ROM you install. Let's say you pick MadeUpRom and it features kernel #8 with it. You'd have to flash kernel #11 after installing said ROM.

Kernels are installed to the boot partition, which is separate from the ROM's /system partition. Installing a new kernel will overwrite the existing one. For the dalvik, read this to understand it better: http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
[Kindle Fire Q&A, Help & Troubleshooting] linktohack:
In Android world, a kernel is an image contains a Linux kernel and a ramdisk which is named *boot.img* and will be *write* (byte copy) to the boot partition.

A complete ROM is a singed zip file contains at least /system files and a kernel. When you flash a ROM, it will unpack and *copy* file of /system to the system partition (that's why we wipe the system partiton aka. factory reset before we flash a new ROM) then *write* boot.img to boot partition.

Usually, a kernel needs external modules, offen reside at /system/lib/modules, so developer create an *uncomplete* ROM, which contains only kernel and these external files. This flashable kernel looks like a ROM, but it's really small size compare to complete ROM.

Like I said above, files in /system/bin/ and /system/xbin/ is not related to kernel (boot.img). They are just binaries, compiled to use system calls that kernel (and modules) offer.

--- Dev only ---

System calls is not binaries, they are CPU interupt instructions. Your programs need to be compiled to call them.

In linux, system calls are called through interupt *0x80*
[HTC One S] 6370:
As title states, I saw a post some were asking if the 5 gig data plan includes tethering. I just got of the phone with t mobile and it dose. Just for anyone who was wandering.

Sent from my HTC One S
[HTC One S] GuestX0019:
are you rooted

i tried it with a rooted one s and didn't work

will try my Tether App
[HTC One S] 6370:
No i have stock phone. To be clear though. I do not own a laptop :( so I can't test it. I'm just relaying what the T-Mobile dude told me. But when I connect my usb to the desktop and select USB tether I don't get any blocks or messages so I would conclude that the USB tethering is permitted.

Sent from my HTC One S
[HTC One S] GuestX0019:
maybe because i am rooted

my tether app works though
[HTC One S] 6370:
Okay, I think I know...first install the HTC sync driver.... Then make sure that works. And I bet the tether well work then. It did for me I tested on the desktop. Good luck.

Sent from my HTC One S
[HTC One S] GuestX0019:
Already installed but not recognizing phone. It did recognize phone when first installed. Has given me some some adb issues. Will probaly uninstall it.
[HTC One S] 6370:
Well at least you can get it to work with another tether app. And plus since tethering is included in the 5 gigs plan they shouldn't bother you about tethering. I don't think they care what app you use anyway.

Sent from my HTC One S
[HTC One S] GuestX0019:
They did with my nexus one.

Hopefully they won't bother me with this phone.
[HTC One S] Smokem_I:
The guy at Tmobile said I needed to pay 5 dollars a month for the data plan that included tethering. He said it was needed for the phone... I always root my devices so I tether either way but I said okay and got the phone. Since I was paying for it I decided to try it out and it's actually not bad. You activate it through the wifi hotspots in the app drawer. I'm on a EU rom now so I'm not sure what it's called on Tmobile US rom... Anyways it works perfectly and is able to tether up to 8 devices but I would assume you're data couldn't handle that much lol. Goes to show how good Tmobile thinks their HSPA is.... It is pretty nice having the option tethering multiple devices. I'm happy paying 5 bucks for that feature ;)

Oh I almost forgot it works perfectly rooted or unrooted... I tried it before rooting and it works just the same now.
[HTC One S] 6370:
I know when I get a laptop ill tether the poo out of this phone. And I dare them to say anything to me...lol

Sent from my HTC One S
[HTC One S] baseballfanz:
Hey rugmankc, what tether app are you using?

Didn't have to worry about this with CM7 on the N1.:D

Thanks
[HTC One S] jacewt:
The 5 gig plan includes tethering. I am not rooted and upgraded to that plan for the purpose of tethering and it includes it. At first it did not work, I called and said, I was told this plan included tethering, the lady was very nice and enabled it. Told me to turn the phone off and reboot and then it would work. It did. I haven't done anything else and the native app works great.
[HTC One S] ickedmel:
I have the 5gig plan didn't know this was included thanks
[HTC One S] glacierguy:
Me either... Is it the same for 10gb? I just changed my plan when got the one s
[HTC One S] jacewt:
I think if the 5 does, so should the 10 gb, I think at one point it was advertised as having tethering, just call and act like you were told this was the case. I thought I was going to have to threaten things but they did it without argument.

I just looked at their webpage and all their new plans seem to include it. It doesn't hurt to call.
[HTC One S] GuestX0019:
It is a paid app. But cheaper than 10.00 twice a year on vacation. No pc available atm and in 2g only area and spent last nite in ER. So, didn't read anything on the tmo free tether with 5gb plan which I have.

http://tether.com/android/windows
[Samsung Galaxy Nexus] blackhand1001:
The softkey glow animation causes unnecessary lag on pretty much every device other than the transformer prime in my experience and even there its not perfect. I don't get why this animation was added in ICS. I wasn't part of honeycomb. My rom I use on my nexus has it off by default (winner00's cm9 kang) but its fraustrating that stock this phone even has this animation. It causes so much extra lag that the phone doesn't need and the animation looks like crap most of the time anyway. The most obvious times I see this lag are when hitting the back button from the app drawer, and hitting the back button with the notification draw open. With the animation its unsmooth on both things. With the animation off or removed both of those animations are 60fps. Google removed the menu selection fade in 4.04, I think its time that they remove this one as well, or at least make it standard in all cm9 roms as my friends touchpad still has this animation. AOKP has an option to remove it but in my experience that rom has some weird lag issues when closing the app drawer anyway.

The problem with this being standard turned on is the stock roms for many devices like the Asus Tranformer tf101 have this glowing animation and it causes lag. Its a bad precedent to set.
[Samsung Galaxy Nexus] propain4444:
Does it really matter what the default option is? You know there's an option to turn it off, so use it. I personally like the animation, running on AOKP and it's glass smooth all the time.

The point of a custom rom is to give you extra options and performance... not to completely alter the way the phone behaves (unless you're going to MIUI, but if you're doing that you know that you're going to get drastic changes). When i install a custom ROM, i expect that all the defaults will have my phone working just as it did when it was on stock - from there, i can customize to my liking.
[Samsung Galaxy Nexus] earlyberd:
I remember when the Nexus One came out, and shortly after that Google decided to implement Live Wallpapers. Every time you enabled a live wallpaper the home screen lagged, and to top it off it would eat your battery life to keep it running. Then a year later the next generation of phones came out and live wallpapers were no longer a problem.

Google always implements unnecessary eye candy that bogs down your phone. It's a way to show people the difference that it makes to upgrade your hardware every one or two years, because you can pretty much guarantee that this year's new phones will have absolutely no difficulty running little touches like this, whereas last year's phones will chug.

Most consumers don't care if it's laggy. They see the glowing buttons and think it's the best thing since sliced bread, since neither the iPhone nor WP7 have it. Then once the next Nexus comes out they'll see even more button effects and spend even more money on it.

Don't get butthurt just because you're not the target audience.
[Samsung Galaxy Nexus] blackhand1001:
The problem is, unlike live wallpapers, unless your rom added an option to turn this off, there is no way to do so. There is no way to turn this option off on the stock rom and many builds of cm9 don't have an option either. If you haven't tried winner00's cm9 if your on the verizon nexus, try it. The difference is hugely noticeable. AOKP in my experience seems to have lag in the app drawer even with the glow animaton off regardless of which launcher you use.
[Samsung Galaxy Nexus] zolah:
Agreed. The choppy animation drives me crazy. I'm 100% stock and proud but I might go back to the dark side and flash a custom rom because of this.

Surely this is easily fixable for Google and they are aware of the problem.
[Samsung Galaxy Nexus] rock7632:
No lag at all for me running Apex rom
[Samsung Galaxy Nexus] GuestK0097:
Lol. I'm on 4.0.4 IMM76I and the animation is completely fluid. Why do you even care about the key glow? I don't even look at the keys when using the phone :p
[Samsung Galaxy Nexus] blackhand1001:
I want the glow gone lol.

Heres a comparison video of cm9 kang(winner00) which doesn't have the glow and official cm9 build 5-7 that has the glow.

http://www.youtube.com/watch?v=4Y7HwdKmvtk&feature=youtube_gdata
[Samsung Galaxy Nexus] thenamesian:
i don't agree with anything you said. most consumers do care if it's laggy; that's why the get the iphone. people don't "ooh and ahh" about glowing buttons -- this is not the year 2000.

finally, there is no way in hell that the purpose of google adding "unnecessary eye candy" is to show how much better hardware is getting when the next generation of devices is released.

quit your trolling, pal -- your long-winded response really proved nothing.
[Samsung Galaxy Nexus] adrynalyne:
Sheeple do not get the iPhone due to Android lag...
[Samsung Galaxy Nexus] malibu_23:
i watched ur video, and i see no performance difference in the two. looks/sounds like u just being anal...like 90% of xda. quit crying. u own the best phone out...enjoy it or mod the hell outta it, but dont be mad...
[Samsung Galaxy Nexus] xHausx:
If you would like something changed you may submit your ideas to Android's gerrit for review.

Thread Closed.
[Android Q&A, Help & Troubleshooting] sims34:
So i was searching the SGSII forums, and i was wondering what does these "ext4,ext3" do. I saw Ext4 on my friend's Galaxy Mini. Does this increase performance or something? Please explain :D
[Android Q&A, Help & Troubleshooting] imheroldman:
These refer to a partition on your sd card the numbers denote the type. Some rom's are not compatible with ext 3 or 4, standard is 2. You will want to make sure your rom is compatible, usually gingerbread supports 3 and ICS supports 4. This does aid in how smooth apps to sd is if you use it.
[Android Q&A, Help & Troubleshooting] superalphajellybean:
Ext4 would be the quickest whereas some samsungs have a much slower rfs but it can be changed the ext4
[Android Q&A, Help & Troubleshooting] sims34:
Well i have Official ICS on my phone, will ext4 work? And where i can get it?

Will it increase the I/O performance or something?

Thanks for the answers btw :D
[Android Q&A, Help & Troubleshooting] Ryuinferno:
Well, you will have to format your sd card into the format you want...but usually your phone should auto format the sd card or internal that suits it best...for me, my ROM is based on ext4, so my whole internal memory is ext 4...but sd card is still in FAT 32..sd card usually work bests in FAT 32...which is safer and guaranteed to work for most phones...frankly speaking, I don't really feel the difference...but should be faster...;)
[Kindle Fire Q&A, Help & Troubleshooting] cryplock:
I downloaded the kindle fire utility 0.9.5

I have rooted the device.

I download the new version of fff 1.4a .bin and dropped it in the recovery folder of the KFU. I noticed it was installing the old orange triangle version.

After i did that got the the new version of twrp 2.1.1 .bin and dropped that in the same folder.

I run install twrp it goes through the process. screen on kindle shows the new interface and version 2.1.1 i looked around the menus and stuff ill reboot. New fff logo shows up i hold the button to go into twrp and it loads up version 2.0.0.

I even went as far as logging in to my kindle then rebooting from there.. and still loads up 2.0.0

Why isnt the twrp 2.1.1 version not staying?? At least the fff 1.4a installed and is staying.
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
http://xdaforums.com/showpost.php?p=24748001&postcount=1317

TWRP 2.1.1 has the 2.1.0 problems fixed, but the above still applies. You can either edit the KFU run.bat file with the right fastboot command or get it in fastboot mode and flash it yourself.

For fastboot commands...

http://xdaforums.com/showpost.php?p=23747804&postcount=3
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
TWRP 2.0 is installed differently from TWRP 2.1. TWRP 2.0 comes packaged with FFF 1.2 and are installed simultaneously using the "fastboot boot" command. TWRP 2.1 doesn't come with FFF and is installed with "fastboot flash recvovery".

I haven't used KFU so I'm not sure which command or version it is using but I am pretty sure they aren't interchangeable.

In your case, I would get FireFireFire 1.4 and flash it in recovery. It will make changing your bootmode a lot easier. Then get TWRP 2.1 and install it manually.

Assuming you know how to set up your command environment and issue fastboot commands...

fastboot flash recovery /path/to/recovery.img

...replace "/path/to" with the actual path to your recovery.img

Report back if you need help or encounter any errors.

[Edit:] Damn you kinfauns! You beat me again. :)
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
Yeah, but he liked your answer better and you got the thanks. I guess he didn't want to read and you served it up better... C'est la vie.

However, I take comfort in being able to correct you and tell you that TWRP 2.0.0 has FFF 1.0. :p

You can tell it's 1.0 because it won't do "oem format"
[Kindle Fire Q&A, Help & Troubleshooting] cryplock:
Thanks

I ended up just making a few changes in the run.bat file so that it would install 2.1.1 now. Just makes life easier. Thank you both for pointing me in the right direction at what to look at. :D Actually I clicked thanks on both of you.
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
OH! cryplock changed his mind and gave me some love too! ;)
[Samsung Galaxy Nexus] mkeller96:
Okay so I have the sprint GNEX and I'm sitting here with full 3g and its taking like 2min to load anything on the internet and I also can't download anything it fails.

I ran a speed test and I'm getting 0.99 mbps download and only 0.03mbps upload? Is this normal.

Please help I feel like it was a lot faster when I got it with only like 2bars of 3g

I attached a picture bellow as you can see I have full 3g but ****ty results

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mkeller96:
Someone help me please

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] propain4444:
Are you inside a brick or metal building? Go outside and try again. If it continues, contact sprint.