yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy R i9103] soori.tpt:
my samsung galaxy r gt-i9103 mobile sim not working and that not shows a signal and network problem.so help me sir
[Samsung Galaxy Nexus] blackplague1347:
About a month ago my area upgraded from EDGE to HSPA+. I finally decided to play with the speedtest.net app yesterday and I was only managing download speeds of maybe 1 or 2Mb, on a good test. This is enough for casual use, I suppose, but most people (on this board at least) seem to be getting much better speeds than that. A nearby area where the State University resides also produces similar speeds on my GNex and my previous phone (AT&T Galaxy S2).

Is this normal or do I need to change something on my phone?
[Samsung Galaxy Nexus] c0LdFire:
1-3mbps is pretty normal for me indoors with 2-3 bars of signal, with 4-5 or so outdoors with better signal. I can only pull down those crazy numbers of 10+ with HSPA+ late at night when the towers aren't as busy. I'm in a small town, but we've had HSPA+ for a good year or more now (heck, I was on Verizon when it was switched on, so I don't know exactly how long...). Maybe your network is still getting upgraded / installed and the process isn't done yet?

I'm on the T-mobile $30 plan, by the way. I've heard AT&T's HSPA+ can be significantly slower in some places, so that may be part of it?
[Samsung Galaxy Nexus] martonikaj:
if they just rolled out the towers a month ago and upgraded to HSPA+, I'm not at all surprised by those speeds.
[Samsung Galaxy Nexus] TJBunch1228:
Att's hspa is notoriously slow compared to Tmo. I see between 6 and 18 mbps on my Tmo phones and my Att phones max out at around 6, averaging around 3.

For an area that just now got hspa turned on when the rest of the country is getting LTE, those speeds you are describing seem perfectly normal.
[Samsung Galaxy Nexus] Ravynmagi:
I'm on T-Mobile and 1-2Mb is normal for me with 5 bars. If I'm extremely lucky I sometimes see 3Mb.

T-Mobile's "4G" in Phoenix is exactly the same speed as my 3G Vibrant.
[Samsung Galaxy Nexus] TJBunch1228:
True, location also plays a big role.
[Samsung Galaxy Nexus] flintdragon:
I would be happy to get 6Mb down with AT&T in Austin. Max is about 3.1Mbps which I think is crap since we know it is capable of more. Interestingly, AT&T LTE in the same areas rock!
[Samsung Galaxy Nexus] martonikaj:
Well that's also because T-Mobile has HSPA+ 42mbps deployed, and devices that can make use of it. Most AT&T devices are at best 21mbps capable, and not all of their towers are.
[Samsung Galaxy Nexus] Winesnob:
Depends on signal strength. On VZW LTE I can pull 20+ mbps in Seattle, but only 2-5 mbps in outlying areas.
[Samsung Galaxy Nexus] martonikaj:
Well, we're talking about AT&T HSPA+ in here so...
[Samsung Galaxy Nexus] Winesnob:
...so the thread title asked about 4g speeds. 4g = HSPA+ or LTE.
[Samsung Galaxy Nexus] martonikaj:
"4g" in quotes, and OP specifically is talking about AT&T.
[Samsung Galaxy Nexus] blackplague1347:
I'll have to run speedtest some more when I'm out of town and see what kind of numbers I can get. I would be interested to see what speeds a 3G phone gets in the same region as my "4G" Gnex (HSPA+ via AT&T, not LTE via Verizon).
[A7 General] 6Leinad6:
I started a blog that gives an in-deth look at the A7+ so that developers and consumers alike can check it out without actually buying the device. I've noticed that there are very few reviews or videos on the A7+, so those will be coming to the blog.

I don't mean for this to be an advertisement for my blog (it's really only temporary), it's just that I really couldn't find any info on the device, and am hoping to prevent that for future buyers. Also, if a developer sees this and says "hey! I'd like to develop for that device" then that would be awesome :).

(because I can't post links yet, add the .com to the end)

6leinad6.wordpress.
[A7 General] xdadooder:
Thanks, man. Really useful. Looks like 1saleaday put it up for sale again for $90 and I'm thinking about getting it. I think it will come up in the future so this is a great resource. Very detailed information.

Could you do some videos? I am wondering about the pinch to zoom. I heard it was horrible when it came out but then they released a firmware to make it better. Have their been releases after that to improve pinch to zoom?

I also heard you mention bugs/shortcomings in another thread. Could you talk about those as well on your page?
[A7 General] 6Leinad6:
I know, they put it up for 90 two days after I bought it -.-, but get it! You get the case as well.

They are coming!

That was the A7, NOT the A7+. This is exactly why I started the blog- so many people confuse the two :)

The A7 had "1 + 1" input, which is NOT true multitouch.

The A7+ has 4 points multi-touch.

Are you referring to the ROMs? Because ALL the custom ROMs by Dexter have some pretty major bugs (depending on how you look at them). Videos and posts will be written about the ROMs after I finish checking out the stock firmware.
[T-Mobile, Samsung Galaxy SIII] anterus:
The thread is now closed. Please see author's original thread for LeanKernel at: http://xdaforums.com/showthread.php?p=40068554
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
Bout time. Thanks for this
[T-Mobile, Samsung Galaxy SIII] anterus:
reserved for future use

...
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
Booted up. Seems very smooth. Been using imoseyons work for a long time. Glad to see the lean kernel on this phone. Thanks again

Uh oh. Wifi won't stay connected
[T-Mobile, Samsung Galaxy SIII] pedroisweird:
hahaha mikeyinid was wayy too fast. woohoo!! great work! gonna try it by the end of the day :)
[T-Mobile, Samsung Galaxy SIII] Imoseyon:
Hi folks,

Just wanted to pop in and say a quick hello. As you know i don't have a ATT/TMO S3, so I'll rely on you guys to send your bug reports and feedback to anterus, who will in turn get in touch with me. Enjoy...
[T-Mobile, Samsung Galaxy SIII] anterus:
Wi-Fi password needs to be entered again for this to work.
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
We will. Glad to see your awesome kernel hacks on a phone I own again :)

---------- Post added at 12:55 PM ---------- Previous post was at 12:35 PM ----------

Ok. So are you saying you know it's derpy in 0.2?

It works for me, just fluctuates between full bars and none then shuts off and comes back on.
[T-Mobile, Samsung Galaxy SIII] deeznutz1977:
Awesome, thanks
[T-Mobile, Samsung Galaxy SIII] jm0nki3:
Is anyone else having a issue getting to oc to 1.9 mine i have rom toolbox and setcpu and the both stay at 1.51
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
I'm not only having wifi issues but data issues as well. And I tried what you said, forgot the network and re entered the password. Still won't stay connected.

---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------

Lol. One more thing. I'm using the cm cpu controls and it keeps switching to 1.9 by itself.
[T-Mobile, Samsung Galaxy SIII] anterus:
Mikey, which CM10 build are you using? Can you try cm-10-20120820-NIGHTLY-d2tmo.zip ? I'm not experiencing issues with this version.
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
I am on an 8/20 build but there were 2. Not sure if there was any difference in the 2. To be fair I'm at work and our router here kinda sucks. But I've always been able to keep a connection. And I've never lost data like that. I'm gonna stay on the kernel and see if it's just some weird randomness that I am having the issue. If I keep having the issue ill grab a logcat and pass it along.
[T-Mobile, Samsung Galaxy SIII] bigxie:
Good to see you here imoseyon.

What's the thermal throttling set to? I see a lot of thermal "alarms" in my logcat while running benches at 1.9GHz, at temps in the mid 50's (celsius), and it throttling back down to 1.1GHz. Happens a lot on Vellamo, and it actually makes the score at 1.9GHz lower than at 1.5GHz.

Perhaps the threshold can be safely increased?
[T-Mobile, Samsung Galaxy SIII] ManOnTheMoon:
Wait this can work on d2att? How about on the nightlies (8/21)?

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[T-Mobile, Samsung Galaxy SIII] mbernusg:
Newest .2.1 working well so far.. thank you

sent from my real Gs move in silence like lasagna
[T-Mobile, Samsung Galaxy SIII] mikeyinid:
It will work. I just flashed a d2att kernel on my d2tmo and it works fine.
[T-Mobile, Samsung Galaxy SIII] ManOnTheMoon:
Well here goes nothing.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[T-Mobile, Samsung Galaxy SIII] anterus:
it should work on d2att CM10 nightlies
[T-Mobile, Samsung Galaxy SIII] ManOnTheMoon:
Seems to be working fine.... Will test more.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[T-Mobile, Samsung Galaxy SIII] jaytxvo:
What new lean kernel? The one on rootz wiki... That's for Verizon? Safe to flash?
[T-Mobile, Samsung Galaxy SIII] mike216:
No look two three pages back to find the one for us
[T-Mobile, Samsung Galaxy SIII] IRIE4IPIER:
No matter what app I use, or the built in performance settings, this kernel always defaults to 702 MHz, I will set it min and max the way I want it, go check 5 minutes later, and the min/max is SRT to 702 MHz. Why is this? Bugs the hell outta me because I notice when it happens while playing Nova 3 or MC3 because they become laggier than hell, until I fix the max, but it just reverts by itself. I'm on aokp build 1.
[T-Mobile, Samsung Galaxy SIII] Johnny424:
this kernel has been running great on my at&t s3..using sense last night no problems..everything smooth here
[T-Mobile, Samsung Galaxy SIII] mike216:
I bet it doesn't happen on CM. Try a later AOKP or CM rom. I'm about 99.9% sure it's your rom. No one else is having this issue

That build is really old. Search in goome.

Search BROWSE ALL FILES/DEV/WHITEHAWKZ and you'll see much newer builds for AOKP
[T-Mobile, Samsung Galaxy SIII] Custodian:
I laughed extremely hard. Good laugh before bed! Good Night
[T-Mobile, Samsung Galaxy SIII] mike216:
You think he's looking at where the cpu is in real time?
[T-Mobile, Samsung Galaxy SIII] jaytxvo:
Okay, just to be 100 percent sure, I looked two or three pages back and people are reporting this updated kernel, v08 is working on tmo g3 even tho its in the Verizon section on rootz wiki. Safe to flash?
[T-Mobile, Samsung Galaxy SIII] mike216:
Safe to flash on CM10 or AOKP jelly bean

Make sure you download the zip provided. Don't go to rootzwiki and download the one there
[T-Mobile, Samsung Galaxy SIII] jaytxvo:
Thanks Mike, I feel so stupid... I completely did not see the link provided until you pointed it out. Haha
[T-Mobile, Samsung Galaxy SIII] mike216:
Your very welcome and you absolutely shouldn't feel stupid. There's to many no everything people here that make people like you feel they should apologize. No need to that's what we're here for
[T-Mobile, Samsung Galaxy SIII] Warrior1975:
Well said Mike. We were all noobs at one time, hell some of us still are. So much to learn. I'm very grateful when someone takes the time out to help me...even when I ask stupid questions, which is more often than not.

¶0w3®3d b¥ @OK¶™...GS3
[T-Mobile, Samsung Galaxy SIII] Swimguy14:
hahahaha he was laughing because the person asked why he's having a bug with aokp preview build 1.

Edit:never mind
[T-Mobile, Samsung Galaxy SIII] IRIE4IPIER:
http://www.youtube.com/watch?v=IWINtUCshxY&feature=youtube_gdata_player
[T-Mobile, Samsung Galaxy SIII] danielrod:
No just wipe cache and dalvik and you should be good.
[T-Mobile, Samsung Galaxy SIII] scriller:
say what again

http://www.youtube.com/watch?v=UPHuE5pDlEs&feature=related
[T-Mobile, Samsung Galaxy SIII] Custodian:
Yes.... Wasn't trying to be rude lllolol..

Sent from my SPH-L710
[T-Mobile, Samsung Galaxy SIII] :
Does this kernel fix the echo issue during calls for CM10 on SGSIII for AT&T?
[T-Mobile, Samsung Galaxy SIII] Custodian:
My woman couldn't squirt, until she flashed this kernel. Now she's fuqing up my bed spreads.

Sent from my SPH-L710
[T-Mobile, Samsung Galaxy SIII] Franky_V:
Thank you for keeping this updated!

Btw, your link to the 0.9.1 change log goes to the touchwiz thread xD

Sent from my Galaxy S III
[T-Mobile, Samsung Galaxy SIII] anterus:
This is expected, core changes are the same :)
[T-Mobile, Samsung Galaxy SIII] Davidion:
Ooooh, just wanted to report that using 9.1 with the latest Paranoid Android 8/28 build results in nasty crashes during boot. Had to switch back to 2.1.

Going to see if any of the versions in between works.
[T-Mobile, Samsung Galaxy SIII] Swimguy14:
When i flashed v.9 this morning my phone ran extremely hot when not even being used. It was deep sleeping. Flashed .9.1 and as above poster said, i was unable to boot. Yes i wiped caches and also tried flashing it with a fresh cm10 install(+aokp) and never managed to get past the boot anim.

Going to try again with a new download and see if it works..this kernel is the best
[T-Mobile, Samsung Galaxy SIII] tgamble160:
I'm on the latest cm10 nightly and 9.1 is working great for me. Booted fine seems even faster than before very smooth. This is by far the best kernel for our gs3s in my opinion thank you great work

sent via galaxy s3 on cm10 @ dual core 1.9ghz
[T-Mobile, Samsung Galaxy SIII] mike216:
+1 really enjoying this kernel and have been.

Edit. I got pushed into a bootloop but before that my browser kept crashing?
[T-Mobile, Samsung Galaxy SIII] tgamble160:
I didn't have any real problems but my phone got super hot. So hot I kinda got scared seems like it is just running full throttle for me. Very fast but very hot. Don't know anything about kernel developement. But it seems like if there was a performance setting that's where its stuck even in system tuner both cores full tilt 1.9 and I had force both cores online disabled and ondemand governor

sent via galaxy s3 on cm10 @ dual core 1.9ghz
[T-Mobile, Samsung Galaxy SIII] scriller:
It seems this kernel is "source specific" to certain cm10 builds. PA needs to be updated to the latest cm build base.

I'm also running PA waiting for thebz1 to update his ROM to the latest source
[T-Mobile, Samsung Galaxy SIII] Pete7ate:
Thank selfless contribution.
[T-Mobile, Samsung Galaxy SIII] Swimguy14:
Oo what?
[T-Mobile, Samsung Galaxy SIII] ManOnTheMoon:
Flashed this under the new nightly 9/5 and phone wouldn't boot.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[T-Mobile, Samsung Galaxy SIII] mike216:
9-5 you must be from the future at this point in time 2:59 am eastern time. Why would you if you could, wait until imosey updates the kernel with the no flicker fix
[T-Mobile, Samsung Galaxy SIII] ManOnTheMoon:
Sorry I'm on d2att. Been using this kernel for a while. Your right ill wait.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[T-Mobile, Samsung Galaxy SIII] :
People that call me are experiencing a large delay where they cannot hear my voice after I answer the call. I'm using a SGSIII on AT&T with CM10 nightly installed and this kernel flashed. Is this a CM issue or kernel issue (so I know where to take my inquiry properly)?
[T-Mobile, Samsung Galaxy SIII] nory82688:
Almost positive its a CM10 issue
[T-Mobile, Samsung Galaxy SIII] lferrin:
Lean kernel is the truth!!! Best battery life and performance on CM10 hands down.
[T-Mobile, Samsung Galaxy SIII] Johnny424:
this kernel is most deff. legit. great kernel and and great developer as well. best battery life and i love that damn fast charge :D
[T-Mobile, Samsung Galaxy SIII] isikh:
No matter what I do, when I flash these recent lean kernels on the recent CM10 builds, I've been getting constant app crashes/reboots, no matter how I install. Anybody know why? I know I'm not the only one.
[T-Mobile, Samsung Galaxy SIII] superstargoddess:
Did you wipe cache and dalvik? I always do that and some people say to fix permissions but I don't.
[T-Mobile, Samsung Galaxy SIII] aristo2jzgte:
Damn! You always runs into all sorts of problems! I think there is something wrong with your phone! Get it checked out!!!
[T-Mobile, Samsung Galaxy SIII] mike216:
I had problems also trying to boot on CM 9/5 build. The last two haven't been good on my phone.
[T-Mobile, Samsung Galaxy SIII] aristo2jzgte:
Works perfectly here!!
[T-Mobile, Samsung Galaxy SIII] isikh:
All phones are different! Processors are all different - I don't think it's messed up necessarily. But Good news everyone (for now) !

So here's what I did. I would get all my issues, with constant app crashes, etc, but this time I tried something new. I flashed the kernel after wiping dalvik/cache as usual, then I wiped cache/dalvik again & fixed permissions. Then, I rebooted, let it update apps, etc, IE: do what it needs to do after you wipe the caches, and then I let it sit for 10 mins. I then rebooted got all the force closes again, for various google apps, gmail, calender, etc, as well as apps like twitter, but i let it clear out unchecked my processor options under performance, ran a fix permissions via ROM Manager. Rebooted and it looked alright. I rebooted again & fixed permissions via recovery & now it looks alright, for now! Finally! (Right now it's bootlooping because the min I set is too low for my processor, but that's on me. I'll let you know if it changes)

What are your settings for optimal battery life? This KTweaker app is new to me, and I don't get all the options! xD I keep getting it to force close because I'm not sure what I want to click settings wise! I prefer optimal battery life, while having good speed, but battery life is imperative! I use the phone quite a bit, and can't have it dying after 8 hours/1-2 hours of screen on time. :P

---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------

Well, I mean not to sound like an ass at all, but I've been around for a while, I already know to do that ;)

EDIT: PLEASE Read:

I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://xdaforums.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
[T-Mobile, Samsung Galaxy SIII] superstargoddess:
Sorry about that, posting from tapatalk so I wasn't able to see how many posts you had to see how long you had been around. :)
[T-Mobile, Samsung Galaxy SIII] zoth:
Thanks for the Awesome kernel Sir.
[T-Mobile, Samsung Galaxy SIII] Murmur95:
Using AOKP (whitehawkx sept 1st) and the phone seems really glitchy with the new 0.10

-The drop down notification bar does not show up and makes all the icons blurred/glitched

-The unlock button does not always work

-If the nav bar works some icons can get glitched out in there.
[T-Mobile, Samsung Galaxy SIII] sarni84:
did u read the op........ at all?

builds from 9/5 and later are compatible with v10

9/05/12: Beta 0.10.0 (ec0623c816b964378a78f1cf308f4d20) - merged latest ramdisk from cm10, merged more cm and codeaurora code, enabled CFS. Note this version may not boot on AOSP builds earlier than 0905.
[T-Mobile, Samsung Galaxy SIII] Kennii:
Didn't work for me and im on 9-5 aokp whitehawkx
[T-Mobile, Samsung Galaxy SIII] ipnekgs:
Working great on CM10 9/6 nightly
[T-Mobile, Samsung Galaxy SIII] :
My phone is ****ed, I need help ASAP please...

I've got a SGSIII on AT&T and I wanted to flash the latest CM10 nightly. So I flashed CM10, then I re-flashed this kernel (0.9 beta) then I flashed gapps. After that, my phone shows the SGSIII boot screen, then proceeds to the CM10 boot animation, but freezes and self-reboots 1-2 seconds into the CM10 boot animation, it does this endlessly.

I tried the 3 button combination to boot into CWM, but my phone just doesn't come on when I hold down all 3 buttons. I also tried pushing both volume up/down buttons while plugging in to get download mode, but nothing happens there either (battery charging symbol appears for a brief moment, then black screen, after plugging in USB).

Please help! How can I fix this?
[T-Mobile, Samsung Galaxy SIII] Swiftks:
No need to hold power button. As soon as it turns on, just hold the home button and volume. After you see blue text, release and it should boot into CWM. If not, try getting into download mode and you can always odin.

Next time, give the rom a full boot before you flash the kernel.

Sent from my SGS III
[T-Mobile, Samsung Galaxy SIII] gen10:
Try posting this in the Q&A section you might get more responses. As for your problem I have no idea if you cant boot into those. I know for tmobile you hold volume up then power then home button and once the s3 logo flashes you let go of the power. Try that if not post on the q&a section

Good luck I know how you fell ive bricked my phone too.
[T-Mobile, Samsung Galaxy SIII] :
Thanks I was able to boot into clockwork with your advice! Whew, I thought I was doomed!

Just so I know for the future -- do I need to reflash the kernel after I update CM10 to a new nightly? I'm assuming that the CM10 nightly will re-install its stock kernel over this one.
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
That's correct. A nightly will reinstall the CM kernel.
[T-Mobile, Samsung Galaxy SIII] mike216:
Don't flash this kernel after the rom. Let your rom boot then flash lean. I find it absolutely necessary to fix permissions. I've had to or else I got reboots and force closes.
[T-Mobile, Samsung Galaxy SIII] ipnekgs:
I do it this way every time and never had issues.

Backup apps ( I never backup system apps or settings)

Go to CWR

Wipe system, data, cache, and dalvik.

Flash nightly

Flash gapps

Flash kernel

Reboot

Let it be for 5 mins

Reboot
[T-Mobile, Samsung Galaxy SIII] Murmur95:
Updated to 09/05 and still was broken

AOSP != AOKP
[T-Mobile, Samsung Galaxy SIII] phonepersonality:
Well you really shouldn't do it that way.

After you flash GAPPS you should reboot and 'let it be' as you put it :)

And then reboot into recovery and flash your kernel.

It's always a good practice to ascertain that the ROM you installed can boot up successfully as was intended and there are no inherent issues with it, prior to making kernel changes to the phone.

It makes for better troubleshooting and happy flashing :)
[T-Mobile, Samsung Galaxy SIII] anterus:
Make sure that you go to settings -> developer options and enable Android debugging. I believe the way how CM10 nightlies are built requires debugging mode being on. This should make your phone as cool as beer :)

Order matters, if ROM on your phone doesn't have recent CM10 [e.g. more than 10 nightly builds away]:

- back up your stuff

- download latest CM10 nightly build here , you can also see the changelog for each build

- wipe off your data, format system and cache partitions

- flash CM10 followed by GApps, allow the phone to boot

- get back into recovery, wipe cache/dalvik again, and flash kernel

- allow the phone to boot again, ensure that you have android debugging and use network-provided time enabled

Check CM10 changelog, and compare it to what made it to AOKP. I'd still recommend the most recent CM10 nightly - it's the most stable combination with this Kernel.
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
I just flash nightlies over nightlies and kernels over kernels.......... Am I the only one that does this without issue?
[T-Mobile, Samsung Galaxy SIII] Johnny424:
newest kernel working great with newest cm nightly. thanks for your work Imosey :)
[T-Mobile, Samsung Galaxy SIII] Custodian:
I don't get it.

Sent from my SPH-L710 using Xparent SkyBlue Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I've never full wiped, except for when I started using the CM10 previews last month (came from stock). Only issue I had was Google Goggles stopped working once. Uninstall/reinstall fixed it.