yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Yes I have an i747 d2att, but no matter what you install recovery the same way... if you can't get it to flash through Goo Manager for some reason, than you need to grab the .img file and flash it manually through ADB or Term Em. It's that straight forward.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I reset all APN settings and cleared data and cache in messaging. Doesn't appear to have made a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
So far im freaking loving this cm10 sounds silly but im liking the quick reply for texts from the drop menu and all the customer settings.. I notice from the lock screen that when I click to unlock I notice that i see the 2 side panels is there a setting to have that not to show up? hope that makes senses also how do I add the apps I want to the lock ring it only shows which the pre loaded apps..

Or is there a link for any mods you can do with cm10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
No Mods, just themes.

---------- Post added at 11:37 PM ---------- Previous post was at 11:32 PM ----------

Oh and tonight's and last night's Nightly has sucked... Nothing fun in them..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nostabo:
I just scanned over 4 pages of posts most of which had nothing to do with the thread topic, 'CyanogenMod 10 Nightly Builds for SGH-I747'.

PLEASE TAKE THIS OTHER STUFF ELSEWHERE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
I would click the thanks button but i reached my limit ..but thanks dude.. where can I check out themes for this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
So?? If you actually care about the flash counter, which if you're flashing custom ROMs, I don't see why you would... Just use triangle away by Chainfire, and reset the counter.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
When I agree with your post, there is a no tripping flash counter way to root (A way I did not use), but since originally rooting in July my flash counter has been at three. Triangle Away is freaking amazing though. A life saver for us flashers.

---------- Post added at 11:46 PM ---------- Previous post was at 11:43 PM ----------

Just look around the play store and just do some searching around XDA. Search "CM 10 Themes"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks dude!

Just some info to share because I notice my data speed was not as fast and I did this minor change for apns and it help so take a look if anything http://xdaforums.com/showthread.php?t=1947376
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
1/14 is up: http://jenkins.cyanogenmod.com/view/All/job/android/17881/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Where can I find the developer settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Settings -> About -> Tap Build Number About 8 times
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
OK at 1st I thought you were joking.. But yup it worked. Why do you have to do it that way
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
The Nexus 4 is the same way. I guess Google decided those Developer Options had to be hidden a bit more so you REALLY have to know where to go to get to them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
bluetooth is fixed with the latest nightly:good::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Yeah, I just noticed that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
Since we've hit the middle of the month and they seem to be ironing out most of the bugs... you guys think we'll be seeing the official "stable" 10.1 release soon?

Just a speculatory question, NOT asking for an ETA or anything... just seeing what you guys think as ones who use the nightlies on a daily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Whoa, now that's some good news. http://review.cyanogenmod.org/#/c/30276/ looks like the fix combined with http://review.cyanogenmod.org/#/c/30213/ . Going go try this out when I head into work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
I searched in Goo for the d2att version and installed it. Nothing else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
People were having this issue on the Samsung Note 10.1 due to there being this issue on specific model installs: thanks goes to 3flight.

I was unable to install CM 10.1 through both TWRP and CWM until I removed assert line from updater-script inside the zip. For some reason this script could not properly determine phone model and exited with error 7. So if this is your case - delete assert line (you can use Power Grasp on Android to get the file from archive, edit it and put it back into archive) and try again, should work on both CWM and TWRP.

Now let's get back on topic people. I like pancakes instead of waffles :p

Sent from my CM10.1 SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
Thats why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
You guys sure Bluetooth is fixed? Complete wipe here, connect to Ford Sync, no bass with music, audio gets distorted like before and speeds up. Then I disconnect Bluetooth and my screen goes black and have to reboot.

This is on latest 0114 Nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Did either of you actually test Bt audio before reporting that it's fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
On the 01/13/2012 nightly, I am noticing only one major bug:

My notification light does not work for unread text messages.

It works in the test option in the settings. The led works when charging etc. But it will not stay light when I have an unread text. It lights up until the screen turns off. Then the light turns off as well.

Anyone else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Mic on headphones work for me and I have notification toggles working, might need to full wipe again is you are having problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
OK, did you do a factory fresh install, or an upgrade install of 07/20 over 07/19? I'll probably do a full factory wipe and reinstall to test...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
did a factory install.. wipe cache...dalvik.. data..everything.. does this having any power saving mode?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] play2lose:
6 hours?! What did you go through 3 whole batteries? I was getting about 2.5 hours of on screen time with stock touchwiz. I'll be happy if I get 3 hours on screen with this one!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Whoever asked about GPS just saying turn left with no street names that's happening to me also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Just reinstalled cm-10-20120720-UNOFFICIAL-d2att with full wipe, factory reset, same problems persist... could it possibly be a gapps issue? Which one did you use, I did the jb 0717 one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Hmm any idea why my power bar in the notification drawer disappeared? Tried toggling on and off with reboots. Otherwise 7/20 build is awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oOamnesiaOo:
Only happened to me when I flashed Tiffany's circle percent battery mod. Reflashed the 7/20 build, skipped the mod and no problems since. Same hiccup?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Yep, was the problem with me also... *sigh*, sometimes it's the simple innocuous things that mess with you... worked fine with 0719. Thx for the info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Dangit, same here. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
Ya, my battery mod was based on the 7/18 build which didn't have the toggles so if u flash my mod on the newest build you'll loose the toggles. I'll re-do it tonight based on the 7/20 build and post it again if people still want it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Hell yes please!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
OK. Give me about an hour or so and I'll have it ready. Sorry for the in convience guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oOamnesiaOo:
Thanks a bunch! Always so dern quick! And of course no inconvenience here.. flashing daily anyways :)

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Side note, has anyone restored back ups? To a touchwiz ROM? Just want to make sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I have restored from the last rev of CM10 back to a Stock UCLEM nandroid back up twice with no issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Got it thanks, just a little paranoid..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
BTW:

I'm on CWM 5.8.4.5 standard(not the Touch version)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeahmann:
Picasa sync still not working for me after a full wipe.

And this is probably a problem with the various keyboard apps that haven't updated for JB but the voice language doesn't change when the keyboard language changes. The only way I can change voice language is to switch it in the notification bar. Very inconvenient if you're using multiple languages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Known issues being worked on:

* Picasa sync doesn't work (if you overwrite the Gallery with the Google version, you'll break the camera, don't do it)

If you cant read the op then don't flash the rom. You aren't even willing to read why should people help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
So it what you're saying is, the LED notification will be working properly until you turn the screen ON, or OFF ?

Its supposed to turn off once the screen is turned ON
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hartford:
I am seeing that the LED is in fact flashing for unread texts, but only for the duration that the screen is on. As soon as the screen times out and goes off, so does the LED.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
That's exactly what I am experiencing. As soon as the screen times out, the led turns off which defeats the whole purpose of the notification light lol.

Hopefully this will be fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Same here, minus the lock up. :banghead:

This is the only thing holding me back. I can hardly wait for this to be fixed, 10.1 is so much more fluid than 10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Got excited about BT fix then saw the actual test reports :(

I was on 1/13 but had horrible battery drain. Doing a wipe 3 times (including wiping system) and re-flashing 3 times has solved the issue. Over 4 hours of screen on time and still have about 5% battery life left.

I am having trouble connecting to LTE. I'm always on 3G (UMTS:3) and every once in a while lose my signal as my phone tries to connect to LTE and then reconnects to 3G. I know there's LTE signal at home because I was getting LTE with the stock TW ROM.

Can't wait for the BT fix and LTE fix in 10.1. Otherwise it's a great ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Lte works for me. Try checking out this thread:

http://xdaforums.com/showthread.php?p=33060276
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
This is the only thing I'm really waiting for. There are other minor issues, like the infrequent random reboots, and the odd home button problem.

Glad to see there's another Ford Sync user here!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Thanks, I actually did visit that thread. The *#*#4636#*#* dialer combo doesn't do anything on my phone and all of my Telus APN settings are correct. I also tried both the LH1 and LK4 i747M modems and get the same results with both. I can connect to LTE every now and then but it mostly connects to 3G and the whole signal loss/connection re-attempt is annoying.

I thought I had read somewhere that this is a known issue with all AOSP ROMs, so I'm assuming I'm not the only one experiencing this, I hope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Am I miss the option to add shortcuts to the lock screen I have found it but it only gives me the pre set ups I cant add what I want?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
It's not fixed for me, I tested as I drove in. Same issue, static, sped up, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Settings > Lock Screen > Slider Shortcuts

Drag center to location you would like. Select the empty or existing shortcut option... Profit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VirtualNobody:
Where did you come from before this flash? Stock? Sounds like you need to do a factory reset from TWRP and start over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
This our you flashed the wrong gapps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
So I take it with the nightly updates if you update can you just flash over and do you have to reflash the gapps also or when you update do you have to do a full wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
You only have to flash the nightly zip. Gapps reflash is only necessary after a factory reset, or if you just feel it's necessary (it isn't).

If you're going to consistently flash nightlies, I would look into using cyandelta. A small (5-20 mb) delta file is downloaded after each build release instead of the full ~160mb file. It can also be configured to flash other files that a nightly flash would wipe out (kernels in particular).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
This may be a known issue but I just found it.My hotspot on att isn't working.it turns on but my nexus can't connect to it anymore.Is this normal? I am not on the latest nightly but I'm not sure if the new ones even address this anyways.... Any input would be great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Do you have security enabled on it? It'll work if you leave it open. That's what I had to do the other day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Gapps reflash is only necessary if you wiped the system partition.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Me too. Saw the report from last night and couldn't wait to flash and see. Bluetooth is deffinately NOT fixed. It is worse than ever. Now there is no bass either; absolutely unlistenable.

If you are waiting on Bluetooth.... patience is key I guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
Shareef made a comment that making a call fixes the bluetooth sampler. Or at least that's how i read it. Has anyone tried to call after the audio distorts?

http://review.cyanogenmod.org/#/c/30213/

Edit: Just noticed that commit is still open :eek: Looks like Shareef is working on it though :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Will try with it open didn't think of that lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Correct: and in my opinion, it is a good idea (for stability, etc.) to wipe system, flash nightly, flash Gapps. That's what I tend to do but I don't update every single day, unless a nightly includes a major fix that I need (like I'm still holding out for the BT and LTE fixes).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Yes, noticed this too.. before (say last week) WiFi hotspot tethering would work if using OPEN security.

Since 0112 NIGHTLY even though I disabled security, WiFi hotspot tethering doesn't work anymore. Client is able to connect and obtain an IP address from host but can't really browser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Where can I go to find out if someone is working on this? If someone isn't then I'd like to take a stab at it, since it's a feature I really like to have and might as well put some effort into it since I want it, as I'm sure others do as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
To follow up on this. My notification light works properly for unread EMAILS, but not for texts. Haven't tested missed calls yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I'm having an issue where I can send mms with the stock messaging app but not any 3rd party apps. I anyone know what's up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abedrn:
1/14 is buggy, reverted back to 1/13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] icase81:
I disabled security and its working fine for me using the Jan 13 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
Already been discussed over and over earlier in the thread. MMS only works on Stock messaging app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Cool I kind of like to keep up to date with ROMs and didnt want to keep resetting up my phone. So where can I get that cyandelta and if so I want to flash the latest I can. Just flash over what I have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
You don't need cyandelta for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Anyone notice the stock keyboard being really laggy on the lastest nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
You pretty much described what happens when you flash a CM ROM:

- Backup gapps

- Format system

- Install ROM

- Restore gapps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtl171:
You can flash the latest over your install with cyan delta. The neat thing about delta is that it downloads a small file for every update onto your phone making updating a bit less time consuming. You can find it on play store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
How to log issue?

There is an issue with email notifications where the device vibrates when on silent, with the email notification set to "Vibrate, Never".

Can we log this type of issue somewhere? Last I recall, no bugs were accepted in some issue tracker unless it was a formal build. Since there's not a formal 10.1, how could we let developers know of the problem?

Thanks!

---

Well, I found this: https://jira.cyanogenmod.org/issues but I find it hard to think it's the actual bug tracking system. There are 4 issues open in this system that I'm shown. I'm instructed to search before logging an issue, but I can only look at these 4 items.

I'll try logging my issue and see what comes out of it.

---

Yeah, ok. No logging except for 'official' builds. So, back to my question. How to let developers know of a problem with nightlies? I suspect my issue here might not be well known.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Flicker is a known issue, current quick fix is to disable hardware overlays in dev options.

Please start searching the thread. I know there's a lot of posts, but these things have been discussed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Disabling the h/w overlays doesn't fix my screen flicker issues.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
The fix that task650 posted in the slimbean thread about changing some things in the build.prop seems to have helped me without having to turn off hw overlay manually every time. i'll see if I can find the post.

Here it is. There was some other thing in the build.prop that was supposed to be changed from =dyn to =gpu but I don't have the time for search for it. Just look for something that says hwaccel and dyn and change it to gpu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
My phone does this too but I don't think it's a bug. From what I can tell, the phone assumes that if you look at the notification or whatever generated it, you don't need the light to let you know it's there since you have already seen it.

Try turning off the message pop-up and you'll notice that the light for texts will stay on until you pull down the notifications bar.

Hopefully that makes sense
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
I dunno if this is a bug or if this is even the right place but I noticed under the performance tab, with the stock kernel under interactive governer, the cpu is quick to jump to max speed at first touch. On CM10, (on CM10.0.0 build) it would step up to to 1134mhz before jumping up to 15xxmhz under higher load.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It's not supposed to go straight to max, but it might spend most of its time there: LOOK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
I'm watching from within the performance settings and from within system tuner and it is definitely jumping up straight to 1512. Can you check on your phone?

---------- Post added at 07:57 PM ---------- Previous post was at 07:50 PM ----------

Actually it seems to have fixed itself after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mharmon:
Is anyone else having problems adjusting the Alarm Clock settings? I'm on CM10.1, 20130114 Yes, I have searched the thread and I have cleared data on the clock. If I'm missing something, I stand by for the inevitable beratement. :p

D/AndroidRuntime( 5728): Shutting down VM

W/dalvikvm( 5728): threadid=1: thread exiting with uncaught exception (group=0x40b0b930)

E/AndroidRuntime( 5728): FATAL EXCEPTION: main

E/AndroidRuntime( 5728): java.lang.NullPointerException

E/AndroidRuntime( 5728): at com.android.deskclock.AlarmClock$AlarmItemAdapter.getRingToneTitle(AlarmClock.java:992)

E/AndroidRuntime( 5728): at com.android.deskclock.AlarmClock$AlarmItemAdapter.bindExpandArea(AlarmClock.java:896)

E/AndroidRuntime( 5728): at com.android.deskclock.AlarmClock$AlarmItemAdapter.expandAlarm(AlarmClock.java:1021)

E/AndroidRuntime( 5728): at com.android.deskclock.AlarmClock$AlarmItemAdapter.access$1200(AlarmClock.java:417)

E/AndroidRuntime( 5728): at com.android.deskclock.AlarmClock$AlarmItemAdapter$3.onClick(AlarmClock.java:656)

E/AndroidRuntime( 5728): at android.view.View.performClick(View.java:4202)

E/AndroidRuntime( 5728): at android.view.View$PerformClick.run(View.java:17340)

E/AndroidRuntime( 5728): at android.os.Handler.handleCallback(Handler.java:725)

E/AndroidRuntime( 5728): at android.os.Handler.dispatchMessage(Handler.java:92)

E/AndroidRuntime( 5728): at android.os.Looper.loop(Looper.java:137)

E/AndroidRuntime( 5728): at android.app.ActivityThread.main(ActivityThread.java:5191)

E/AndroidRuntime( 5728): at java.lang.reflect.Method.invokeNative(Native Method)

E/AndroidRuntime( 5728): at java.lang.reflect.Method.invoke(Method.java:511)

E/AndroidRuntime( 5728): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)

E/AndroidRuntime( 5728): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562)

E/AndroidRuntime( 5728): at dalvik.system.NativeStart.main(Native Method)

W/ActivityManager( 754): Force finishing activity com.android.deskclock/.AlarmClock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I did check, and it's pretty much all over the place, but if I open an app or do something bigger than just scrolling, it jumps to max and stays there for a while (a few seconds).

---------- Post added at 11:45 PM ---------- Previous post was at 11:36 PM ----------

Did you try wiping dalvik and cache in recovery? That first exception mentions the dalvik cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mharmon:
Thanks for replying. Yes, I did that but it didn't help. Also did this:

# cd /data/data/com.android.deskclock/databases

# mv alarms.db alarms.db.bak

That didn't change anything either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I'm loving some of the changes to 10.1. Running with KT kernel as well.

Only issue I've had since upgrading from 10 to 10.1 is I either get 3G or LTE, no HSPA or HSPA+ anymore.