yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] munchee:
Hi, I just flashed my Galaxy S3 with FrostyJB ROM v11.2.2. After the flash, SD card cannot be mounted anymore. I have a 64GB SD card in there. I then flash the kernel with stock kernel, and SD card can be mounted again.

Since this ROM is built using a custom kernel, I'm assuming the optimization is build around that kernel. So is it better to revert back to a previous version of the ROM altogether, or format the SD card with FAT32 and see if it works with the custom kernel, or it doesn't really matter having the stock kernel with this particular ROM?

Thank you for your help.
[T-Mobile, Samsung Galaxy SIII] tvinhas:
Mine is working... I suggest re-formatting your SD card from within Frosty.
[T-Mobile, Samsung Galaxy SIII] munchee:
Thanks tvinhas, but that's not the issue.

I played around more on it yesterday, and here's what I have:

FrostyJB v11.2.2 uses ktoonsez kernel, which seemed to incompatible with exFAT greater than 32GB (or perhaps just incompatible with exFAT altogether, not sure). I tried different combination and this works:

* FrostyJB ROM V11.2.2, with stock kernel

* FrostyJB ROM V11.2.2 with ktoonsez kernel, but must format SD card with FAT32

But regardless, I found another issue with this ROM version, so I decided to revert back to V11.2.1. I found that this ROM for some reason broke my USB connection. ADB and KIES won't work anymore, though windows recognizes the phone when I plugged it in and was able to read the storage. I uses KIES to sync my calendar with outlook, and I disable my KIES air. Rather than mocking around with it more, I decided to restore my nandroid.

Thanks for the help
[T-Mobile, Samsung Galaxy SIII] UALPOW:
Frosty V11.2.1 is my favorite and most stable ROM to date. I had issues with my 8gb FAT32 SD card on V11.2.2 so I went back. I was having some other issues as well but they might not have been due to the new version. I can't express enough how much I appreciate you developers taking the time to do this for the community.
[T-Mobile, Samsung Galaxy SIII] munchee:
Totally agree, this is my favorite ROM, and it is amazing. Can't thank all the people enough in spending time developing and debugging this.
[Verizon Samsung Galaxy S III] 996:
I want to use CM10.1 as a daily driver, but all of the bugs and small nicks make me go back to more developed and stable TW roms. Anyone using 10.1 as a daily? Can you give me your opinions on it? Which rom are you using? What bugs do you notice?

Thank you

996
[Verizon Samsung Galaxy S III] antiseen:
The in call volume has been fixed for me so I'm going to run it as a daily driver from now on.

Bluetooth audio is still completely broken I hear but it's not something I depend on or use without going out of my way.

Unless some other huge bug manifests, all is going pretty well.
[Verizon Samsung Galaxy S III] Div033:
So far there are two main issues that make me consider going back to TW:

1. Sometimes when I interrupt a game from loading, the entire system is laggy as hell until I reboot

2. There is a small delay when answering the phone. I don't know who can hear who during that delay, but its annoying nonetheless.

I'm waiting for the stretched image bug to be fixed on multi-window ROMs before I go back to TW though. It's definitely daily driver worthy.
[Verizon Samsung Galaxy S III] NeoMagus:
Been daily on mine since the unofficial cm10 back in August, fine here but maybe I just can't stand TW. Only little issue Ive come across that bothers me is sometimes it will think a short press on menu/home is a long press and have to reboot. Bluetooth audio is fine if you go into the build.prop and modify lpa.decode to false
[Verizon Samsung Galaxy S III] brandao.gabe:
Been using as daily driver since unofficial cm10, lost IMEI and had some pretty good scares but I have been loving it ever since. I would say the only issue for me right now is the screen flickering which can be somewhat fixed by disabling HW overlay, which does not seem to stick through a reboot.
[Verizon Samsung Galaxy S III] 996:
thank you all for the replies. I was running CM10 for a while, but I just resorted back to TW. I can't wait until all the nicks and bugs get sifted out of 10.1. Pure Google is the way to go.
[Verizon Samsung Galaxy S III] Deliquified:
Pure Google you say? Well, here ya go.

http://xdaforums.com/showthread.php?t=2066467
[Verizon Samsung Galaxy S III] Div033:
Official 1/10 nightly has flickering fixed!
[Verizon Samsung Galaxy S III] sweeds:
I've been AOSP since week one of owning my SGS3, however weak data signal / drops and spotty gps has me trying out TW.

Synergy is pretty awesome. It's not a huge adjustment once you get it configured with your custom launcher. Plus, MultiView is amazing!

Sent via SGS3 using Tapatalk
[Verizon Samsung Galaxy S III] goldsmitht:
if you are going to "wait for all the nicks and bugs get sifted out", you might always have a wait. Custom ROMs are just that, custom, and sometimes, what works for one phone won't work for another.

Just pick one that you like the features, and learn work arounds or ignore the "nicks and bugs"

Thanks to all the DEVs! I love waving my modded S3 under everyone running stock and asking why their phones can't do what mine does!

:cool:
[Verizon Samsung Galaxy S III] donebrasko:
I have synergy, how do you use multi Window
[Verizon Samsung Galaxy S III] jakereeves31:
Hold the back button and it'll pop up on the left side then just drag an app from there to the screen
[Verizon Samsung Galaxy S III] mikejr83:
Mastamoon in the official 10.1 thread has been putting out some rocking unofficial builds that contain cherry picks for most of the issues that have annoyed me. I really suggest checking out his 1/4 build (I'm on this) or his latest. He seems to have Bluetooth and call volume issues pretty close to being wrapped up.
[Verizon Samsung Galaxy S III] Obaterista93:
I ran liquid's for two weeks or so, but my flashing addiction made me try something else. Went back to AOKP 4.1 but now I'm back on stock TW that I made a few modifications to. I replaced the MMS app and keyboard with AOSP as well as the UI sounds, and I'm fairly content for now. Usually any kind of lags annoys me, but I've found JB Touchwiz to be alright ( I was an avid HTC user prior. Touchwiz is way smoother than Sense.)
[Verizon Samsung Galaxy S III] Stealth111:
I am running the CM 10.1 Official NIGHTLIES. They have been my daily driver since almost beginning of the month. My custom ringtone only rings once when someone calls, answering calls ends up with a weird delay before anyone can hear you. A couple of other small bugs, but no deal-breakers that I really see.

Sent using Tapatalk
[Verizon Samsung Galaxy S III] amotamatapia:
I like slim bean 4.2 but I am not able to find a working wifi tether for it. Most 4.2 roms I cannot get wireless tether working
[Verizon Samsung Galaxy S III] 996:
Update. Running 10.1. I dirty flashed from 10 and all my problems were solved. Pretty awesome having the latest version of android. Love it. Battery life can be better though haha
[Verizon Samsung Galaxy S III] crjjr:
I love CM, but lately it seems they have too much going on. The barely got 4.1 working, and came out with the M2 release, and then moved on to 4.2, which is CM 10.1. I prefer to stay with a dev that will tweak their ROM and stick with it until they get it right. That's why I will not use CM anymore. Unless they have hundreds of devs working constantly to keep up with the number of devices they support, they're eventually going to become a ROM that's unreliable. I hope I wrong, but with the S3 they're clearly not completing one OS before moving to another, which makes them a no go IMO.
[Verizon Samsung Galaxy S III] Amphibliam:
Battery life has been absolutely incredible for me on 10.1. 9 hours on battery all on 4G with 20 min screen on at 80%
[Verizon Samsung Galaxy S III] gseyffert:
Just flashed the DarthStalker ROM onto my S3 I've had for about 2 weeks now, it works beautifully, I've gotta say. Super fast, native WiFi hotspot/USB tethering, I would highly recommend at least checking it out.
[Verizon Samsung Galaxy S III] tducote:
got a link for this?
[Verizon Samsung Galaxy S III] 996:
I was running this is a daily until the low quality MMS's got to me. Has anyone figured out a fix for this yet?
[Verizon Samsung Galaxy S III] dpaine88:
Everything was good for me but the data drops were too annoying after a few weeks.
[Verizon Samsung Galaxy S III] droidx2.3.3:
Ive been running the latest official builds since friday. I love the speed and feel. Tge only things that made me switch back to tw were the battery life (goes from 100 to 90 in several minutes of light use and down from there.) I did get on average 6 hours plus or minus with moderate to heavy use on wifi. With 2hours screen on time. And then the low quality mms and the blue tooth music issues. Really the last 2 I can live with but the battery is a deal breaker for now. I even tried lean kernal. That made it slightly better but not much.
[Verizon Samsung Galaxy S III] jguns112:
Tried it for a couple days but I was having an issue with the phone app force closing on me. Also, the 4.2 camera is awful compared to the touchwiz one.

Really unfortunate though since it made the phone incredibly smooth, all the occasional lag in animations was gone. But I like taking pictures too much and I don't know if the 4.2 camera will ever be improved.
[Verizon Samsung Galaxy S III] :
I've come to the realisation that one must buy the phone for the operating system it comes with, not the one it might get.

I have a GNex and an S3 so I swap phones not ROMs when I go from aosp to TW. That way I'm always running a stable ROM.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Been running liquid smooth 4.2 ever since it came out as my daily driver.
[Verizon Samsung Galaxy S III] ackmanx:
Buggy but okay

I've been using Cyanogenmod 10.0.0 stable for over a month or two now on my Verizon GS3. I really love it, but I'm going to have to go back to TW in hopes of solving (some major) problems.

Reception goes in and out all day. It's working about 90% of the time where I get good signal but it will randomly lose all data access and just get analog. In the areas I didn't get great reception before, I get hardly anything now making it near useless.

Battery life took a massive hit for me. I used to end the day with 20-40% life left and now I can kill it by 8PM.

I randomly don't get calls from people sometimes, and they don't show up in the call log so I never know they called.

System UI force quits randomly and then usually weird things can happen until I restart.

Small random bugs with various apps. Phone app gets my volume stuck at max with the bar at lowest unless I turn on speaker and reduce it. Poweramp changes to next song when I press volume button sometimes. Screen doesn't turn on at all when press power button, but does on a second press.

The battery life and random app bugs I could live with, but not getting calls and getting no data on and off (sometimes requiring restart, sometimes comes back) has become a deal breaker being I've got important calls I can't be missing.

---------- Post added at 06:49 PM ---------- Previous post was at 06:36 PM ----------

Well oops, as I read through I forgot the OP was about 10.1 and not 10.0. Sorry for the off-topic post.
[Verizon Samsung Galaxy S III] ummduh:
I'm now running 10.1 nightly from 1/14 and it's been great. Call volume is a little low, and an occasional hiccup with the home key bringing up recent apps, but I haven't found any reason to force me to go back to TW.

Even did a wifi direct transfer to the wife's stock s3, using some app from the market.
[Verizon Samsung Galaxy S III] 996:
I am now back at TW. sucks I know, but MMS is way more stable with TW. not that it isn't with CM10.1, but the picture quality drops majorly when sending an MMS (with cm10.1)
[Verizon Samsung Galaxy S III] XdrummerXboy:
I am doing the same. Even though there are still some pretty big bugs, I'd still take it over stock TW.

however, the bugs I'm getting are:

- low quality MMS

- whatever the home/menu long press thing that one guy was talking about (didn't happen till I tried to replicate it just now though, it was a bad decision!)

- data drops where I have to toggle data sometimes a few times to get it working again

- needing to wait a second after answering the phone till I can actually speak.

Probably a few others, but these are the biggest, data drops trumping them all

---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------

Oh, and the UI force closing! I haven't been able to pinpoint what is triggering that though...
[Verizon Samsung Galaxy S III] Real_JESRadio:
Only AOSP ROM I have found to be daily worthy is Eclipse 3.1 4.2.1 build 4. Haven't found bugs yet. The best ROM (4.2.1) I've seen yet is sadly on the shelf for now. If KillRom had data fixed nobody could touch it.
[Verizon Samsung Galaxy S III] orangelight:
I've experienced the same issues with the weak signal and data drops on pretty much all 4.2.1 ROMs. If you turn off your LTE Radio your signal strength improves 10 fold.

Turning on LTE makes you hover ~104-108 dBm which will drop when it is too weak (FWIW I'm in a very strong LTE Market).

Other than that the CM Build have been pretty great.
[Verizon Samsung Galaxy S III] scoundral9:
I am loving the Baked Blackbean #7 ROM! It is a Fantastic AOSP 4.2 daily driver!

http://xdaforums.com/showthread.php?t=2108319
[Verizon Samsung Galaxy S III] Stealth111:
CM10.1 nighties are getting better by the day! If the stalled data was fixed, it would damn near be perfect today...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] That_Guy:
Has anyone found a ROM that does not have this issue? My 4g signal strength was cut in half when I installed CM10.1
[Verizon Samsung Galaxy S III] blackguy101:
For me the latest liquid is a daily driver. I have no issues what so ever and it has fully working mms group messaging ! (I had a small hardon when i found this out) even though it says beta 3 this should be the final product! battery life is amazing and im just a new fan of liquid because of this rom =)
[Verizon Samsung Galaxy S III] Wrngway:
When you say that bluetooth audio is fine, do you just mean it works or that it actually sounds good?

My last AOSP experinece was with liquidsmooth rc9 (4.1.2). The bluetooth would work, but I got a lot of skippage in the sound and the quality was horrible. It was all treble and no bass.
[Verizon Samsung Galaxy S III] Mean Sixteen:
This may not be the case. If you saw that your bars were showing half the strength then you probably didn't loose any actual signal. CM10.1 reports the bars different but the signal strength does not actually change. Go to "about phone" and check strength there.

Besides I believe the signal is from the radio not the rom. Could be wrong about this but I am sure about the bars.

Sent through mental telepathy...or my unlocked SGS3
[Verizon Samsung Galaxy S III] cvsolidx17:
Yeah I believe the data issues are RIL related and they have slowly but surely been working on it... Mastamoons builds could easily be used as daily drivers, SlimBean RC 1 was solid as well. If you can deal with potentially running into some of the aforementioned bugs then I'd recommend these two roms for daily drivers. Stability is there, battery life is there, once they get the data issue worked out I'm jumping ship from TW. I've heard good things about liquidrom but I haven't flashed it so I wouldn't really know.
[Verizon Samsung Galaxy S III] zerocool79346:
Been doing it since I got the phone on Tuesday with little to no issues. And incredible batter life.
[Verizon Samsung Galaxy S III] Mean Sixteen:
I've been running mastamoon's cm10.1 for a while and like it a lot. Data drops ate not so common to become annoying. Toggle airplane mode and back in business. Not too many bugs really.

And getting better all the time.

Sent through mental telepathy...or my unlocked SGS3
[Verizon Samsung Galaxy S III] xs11e:
I'm probably going back to a TW ROM, my battery life took a big hit over the Executioner ROM I was running.

NOTE: All settings are identical with any ROM I run, same apps, same usage, etc..
[Verizon Samsung Galaxy S III] landale:
I recently just went back to CM10 after a three week test of CM10.1. I have to say that so many things were fixed in those three weeks that signs are very encouraging but at least for me the weak signal issue is a deal breaker and ultimately why I had to go back to CM10. It kinda sucks as there are many things CM10.1 does better than CM10 such as making full use of the 2GB of RAM, faster GPS, and the home button more reliably turning the device on to name a few but at the end of the day if I keep losing data none of that really matters. Anyway I am confident the CM team will get this issue resolved eventually as they always seem to figure these things out.
[Verizon Samsung Galaxy S III] andybfmv96:
I am!
[Verizon Samsung Galaxy S III] tomkins0752:
I used it for a few weeks but my main issue was battery life. It would barely last 10 hours on moderate use. I used their stock kernel.
[Verizon Samsung Galaxy S III] zerocool79346:
My battery life wasn't that bad, but after switching to Lean Kernel it definitely got better.
[Verizon Samsung Galaxy S III] ddurandSGS3:
getting great performance out of AOKPs release.

15 hours with 5 screen on hours today.

running great on KT747,

the speed is phenomenal
[Verizon Samsung Galaxy S III] hunterboy2011:
I just installed CM10.1 on my Galaxy S3 but I have no option for NFC at all. Is there any easy way to get NFC with out re-installing, I tried the NFCfix.zip but that didn't seem to do crap..
[Verizon Samsung Galaxy S III] zerocool79346:
Try installing the M version and not a nightly.
[Verizon Samsung Galaxy S III] ddurandSGS3:
Do a search in the question section. No nfc problems here on 4.2.1.
[Verizon Samsung Galaxy S III] wolf_walker69:
I have yet to see it work on any CM ROM myself, 10 stable, 10.1 any of the M's. Have not tried nightly builds.
[Verizon Samsung Galaxy S III] zerocool79346:
Works fine for me, I beam things back and forth to my N7 all the time.
[Verizon Samsung Galaxy S III] Mean Sixteen:
No nfc problems here. Use wallet all the time. And nfc tags every day.

Sent through mental telepathy...or my unlocked SGS3
[Verizon Samsung Galaxy S III] andrewgk121:
For what it's worth, I'm running the monthly/milestone (M) of cm10.1 on my phone as my daily driver since it was released. I apologize if it's too lengthy, but this is my first rom away from TW so I wasn't sure about most of this stuff until I actually gave it a shot.

What works with no problems whatsoever:

Data/Communication

SMS/MMS/Group Messaging (even with iPhones)

NFC (tested with an nfc sticker, haven't used Google Wallet, but according to others it works fine)

Wifi

Tethering works via toggle (as stated in the cm forums, it only works without encryption)

Phone calls work (I never need to wait before I can talk, it seems to be instantaneous when I answer)

Lockscreen/ Homescreen /Stock Apps

Setting wallpaper

Picking custom lockscreen shortcuts works (remember to hit the save button after you configure it)

Lockscreen widgets

Alarms (turning them off works)

Long press to change tracks with screen off

Extra

Camera works, but no photosphere (there may be flashable apk's, but I haven't found one that works)

Lightflow works just fine (see quiet hours below, though)

Battery life is pretty good. I don't have much to compare it to, but at the moment it's been 6h40m on battery with 2h14m of screen time and I'm at 22%, BUT I spent a few hours in a dead zone and kept the radios on. I usually have to change to my second battery in the late evening, but my days start between 7-8 a.m.

What works but not perfectly:

Data (3G/4G) works when connected, but I have experienced data drops about three times since I first started using it. Not too bad.

Can't figure out for the life of me how to change the lockscreen image. It seems the homescreen and lockscreen are tied.

GPS locks well/fast, but sometimes it will "stick" and I'll have the GPS logo and ongoing notification for no reason. Not sure why.

Not sure where to put this, but the rom has quiet hours which do work, but the only problem I've run into is once quiet hours are over, the notification light doesn't light up anymore when using Lightflow. Not sure if it's the ROM or Lightflow.

Hope this sort of helps someone!
[Verizon Samsung Galaxy S III] Imatoasta:
They just added the option the other day (yesterday I think).

http://review.cyanogenmod.org/#/c/30508/
[Verizon Samsung Galaxy S III] dnap941:
I'm using Mastamoon's 10.1 Rom. It's pretty good actually. My only complaint is that bluetooth doesn't work correctly for my music. It simply just wont connect to my Bose bluetooth device. As far as a daily driver, it's def daily driver worthy. I can call, text, and do pretty much anything with no complaint except for bluetooth.
[Verizon Samsung Galaxy S III] rockingrubberducky:
Is it just me having horrible signal on all the 4.2 roms?:confused:
[Verizon Samsung Galaxy S III] andrewgk121:
I read somewhere that 4.2 shows signal bars differently than other versions. I went from 4.1.x to 4.2 and in an area I had almost full bars with 4g, I now have 1or 2. The real test is to go into settings > about phone > status > and check signal strength. Some users checked their signal strength before and after upgrading to 4.2 and turns out it was pretty much the same, just the bars displayed were different. Like I said though, it was just something I read from users, not devs or anything. It could be completely wrong haha.

Have you experienced slower/worse data speeds or call quality that makes you think it has gotten worse? Or is it based on bars showing?
[Verizon Samsung Galaxy S III] andrewk7750:
I was running all types of 4.2.1 roms for awhile but the signal issues were horrible, so i've swithed to a paranoid android 4.1.2 rom for now till it gets worked out.
[Verizon Samsung Galaxy S III] sivarticus85:
I'm running mastamoon's 1-31 cm 10.1 and the only issue is the pesky low cam volume. Everything else for me is prefect.
[Verizon Samsung Galaxy S III] zetsumeikuro:
Nothing huge preventing CM as a daily driver imo. Data is great, GPS is great , call volume is solid :good:. I have yet to see my screen flicker :confused:
[EVO 4G Q&A, Help & Troubleshooting] Fothic15:
So I just switched my service over to Ting Wireless. After they brought my phone over for activation, I needed to update my PRL and Profile, but was unable to do so (Error 1012). I Googled around and was advised to do a ##786# reset. It's been doing so for the past hour. Is this normal? What should I do?

I am running a Stock ROM but I am rooted.
[Windows Phone 7 Apps and Games] mikaelel:
is available in the marketplace next update adobe reader

news (quotes for marketplace)-

"Fixed bugs

Added Privacy Policy"

http://www.windowsphone.com/en-us/store/app/adobe-reader/bc4f319a-9a9a-df11-a490-00237de2db9e
[HTC One X+] daytontp:
I current use a Galaxy Nexus with 4.2.1 and was wondering how downloaded apps might look on an One X+ with Sense on it. Meaning would the menu UI of the downloaded Google GMail app or the like, would look different on a One X+ when compared to my Nexus. I played around with a One X+ at an AT&T store and was really surprised how different the OS was compared to stock, but was not sure if downloaded apps would be effected by Sense UI or not.
[HTC One X+] CirgioD:
If looking for same functionality, yes, apps do same - look same, only ui or framework is different
[Verizon Samsung Galaxy S III] luke1987:
Shapewriter was always my favorite gesture keyboard until google released 4.2 keyboard. I figured some might still favorite Shapewriter so I scaled my themed version to be compatible with xhdpi displays. If it gets some attention I will further theme it, but I suspect it is too far outdated.

GS3 Compatible Shapewriter
[Verizon Samsung Galaxy S III] luke1987:
I should have probably renamed this to JB Shapewriter...but same color scheme anyway
[Verizon Samsung Galaxy S III] hank3fan:
Hank3 kicks so much ass! +1 for your avatar.