yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] amoblox:
To anyone with concerns about a short battery life or a crashing camera:

The good news: You need to let your phone completely discharge until it's dead and will not turn on any longer, then recharge it without unplugging it until it gets to a full 100%. Do that twice and you'll get realistic stats. Anytime I install a new ROM (or even restore to stock), my battery life is about half of what it should be for the first day or two.

The not so good news: I got around any camera issues by just committing to CameraZoomFX (you can find it in the Play store for a few bucks). No one wants to HAVE to pay for an app or even use a free app to replace a system app (like your camera) that should "just work" out of the box, but it's part of the deal with this stuff guys. You just have to bite the bullet and move forward.
[Verizon Samsung Galaxy Note II] bL33d:
Ics+ camera app still crashed and lg camera app also crashed both were kess frequent but they still required rebbots to get camera to work again
[Verizon Samsung Galaxy Note II] sbrissen:
grab a log please
[Verizon Samsung Galaxy Note II] bL33d:
Sorry ive went back to touchwiz hopefully someone else can grab a logcat for you.
[Verizon Samsung Galaxy Note II] strikeir13:
Here you go

https://docs.google.com/file/d/0B_Ftit9b1qQRd0RRczJWUnViZnM/edit?usp=docslist_api

FWIW, this happened after scanning a bunch of files with Google Drive.
[Verizon Samsung Galaxy Note II] libbycm:
Anyone had luck with Google wallet on the nighties? Tried everything but wallet won't provision after signing in. I saw something where Google might be blacklisting non supported devices now but not sure if that's confirmed or not
[Verizon Samsung Galaxy Note II] computerslayer:
Someone posted here in the not-too-distant past that because Samsung has withheld necessary materials and because this so adversely affects development, we would never see CM go beyond nightly builds for the Galaxy Note 2.

Is this essentially true?
[Verizon Samsung Galaxy Note II] bL33d:
Hope that's not true it runs so smooth on the note 2 if they get that camera issue worked out I'll run cm10 in a heart beat.
[Verizon Samsung Galaxy Note II] libbycm:
I still don't understand the camera issue.. Mine works perfectly..
[Verizon Samsung Galaxy Note II] hopesrequiem:
Yeah I never have issues either. I do switch between tw and aosp ALOT though so idk. Sometimes even 3 to 4 times in the same day haha. My name is Tim and I'm an android addict. Hahaha
[Verizon Samsung Galaxy Note II] kirch21:
Lately my phone freezes every time I try to charge it. Anyone else having this issue?
[Verizon Samsung Galaxy Note II] hopesrequiem:
Nope can't say I am
[Verizon Samsung Galaxy Note II] strikeir13:
Is anyone else able to change the IO scheduler using the built in Performance settings? I cannot.
[Verizon Samsung Galaxy Note II] libbycm:
Nm... Looks like after several months Google fixed something BC it's working fine now with the temp build.prop change and xposed installer ... So, good to go!
[Verizon Samsung Galaxy Note II] itype2slo:
Cannot get Google Wallet to provision for app purchases. Care to elaborate in how you fixed the issue? 5/24 build
[Verizon Samsung Galaxy Note II] craigbailey1986:
Just a heads up for anyone who still has volume issues... I use volume+ app and it significantly boosts the volume. I actually had to turn it down because it was so loud it started to distort the sound... Just in case anyone else needed some help with volume.... Hope it works for you too...
[Verizon Samsung Galaxy Note II] BennyJr:
That works even for incall volume?
[Verizon Samsung Galaxy Note II] Chadastrophic:
As far as the camera goes, if I tap the screen to force a focus and take a pic, the stock camera app locks up and takes a black picture.
[Verizon Samsung Galaxy Note II] sbrissen:
what build? the fix was merged for this and works for me.
[Verizon Samsung Galaxy Note II] craigbailey1986:
Works for me...
[Verizon Samsung Galaxy Note II] sbrissen:
ah thats why, don't think the fix was merged in in that build, try a nightly it should be fixed.
[Verizon Samsung Galaxy Note II] Chadastrophic:
Thanks. I appreciate all the hard work you do for us.
[Verizon Samsung Galaxy Note II] Peperm1nt:
is it normal to have only 10 GB of internal memory? with only 6 of it available? clean install
[Verizon Samsung Galaxy Note II] hopesrequiem:
Android takes about 5.5 gb so yes that's normal.
[Verizon Samsung Galaxy Note II] bL33d:
Deleted camera/gallery and installed android 4.1.2 camera/gallery seems to work better.
[Verizon Samsung Galaxy Note II] craigbailey1986:
Nevermind...
[Verizon Samsung Galaxy Note II] Peperm1nt:
Ok, where it says total 16GB, mine says 10GB

Tapin' the Talk on my GNote ii
[Verizon Samsung Galaxy Note II] illogic6:
Same here
[Verizon Samsung Galaxy Note II] tomkins0752:
If anyone is still having high Android OS issues, try this.

Go over to the development thread and download a tw ROM along with the latest Note II modem from their 4.1.2 build. Flash tw and then flash the new modem, then do a clean install of CM. Since I rooted and flashed my Note II when I first got it, it still had its original modem. Since I did this, Android OS is at about 14% instead of 30+.

My coworker brought that to my attention because he said his old Sensation would have issues on most ROMs unless he made sure to keep his radio (modem) up to date.

I hope this helps. :good:
[Verizon Samsung Galaxy Note II] nathan_barstow14:
I don't see why it's required to flash a TW ROM first for this. I updated my modem via a CWM flash as soon as it was available while still running CM10.1 and didn't have any issues. It's only been on the most recent builds (about a month or so) that I'm having Android OS issues. If someone can provide any reasoning why flashing a TW ROM first might work better than I will certainly give this a try ASAP, but I just don't see it making a difference.

For an experiment, I flashed an old build I had on my SD card still. It was sbrissens custom 4-25 build (so it was unofficial, I believe it was the one with WiFi fix before it was merged). So far, I've been watching my Android OS usage decline a little more every day and battery life has gone WAY up - basically back to normal. The problem has to be with something that has been merged into the official nightlies since this time I would think.
[Verizon Samsung Galaxy Note II] danibri82:
The camera on this thing is pretty piss poor. Any way at all to maintain the stock camera? Every picture I've taken from the back is grainy, like the sensor isn't getting light, and taking HDR is impossible without the steady hands of surgeon. Front seems equally dark and seems like it's somehow partially zoomed
[Verizon Samsung Galaxy Note II] amoblox:
At the risk of getting my head cut off, you should know that this is a problem for every AOSP build. I think the camera app just blows in general. That's why HTC, Samsung, LG, etc all have their own camera apps. I use CameraZoomFX. LGCamera seems pretty nice as well and it's free.
[Verizon Samsung Galaxy Note II] danibri82:
I understand what you're saying, I guess I'm learning I need to just be patient for TW 4.2.2.....
[Verizon Samsung Galaxy Note II] duglas:
I have an Ibolt dash mount and was working great since I got it, I just upgraded to CM10 and wiped my phone and the Ibolt audio out is not working.. According to there directions I need to go to Settings/accessory and check the 3 boxes that are Dock sound, speaker out, and desktop screen. .. But this rom does not have these check boxes..

Anyone have any idea on how to get to them or am I screwed?
[Verizon Samsung Galaxy Note II] zodduska:
I've got the same mount but haven't tried the usb line out with it, which rom did you have it working with previously?

edit: in the mean time you could try Sound then under Dock there is an Audio menu which is currently grayed out on mine (I'm guessing it's grayed out because its not currently plugged into a dock) this is PAC rom I'm on though.
[Verizon Samsung Galaxy Note II] Chadastrophic:
The GPS seems broke on the nightly shown below. It will show a lock, but the GPS has a hard time telling which direction you are going, sometimes it thinks you've turned when you haven't, or doesn't pick up when you did. A couple of times the navigation app said waiting for GPS even if the GPS lock icon was solid. The navigation app doesn't track up and the compass needle never moves.
[Verizon Samsung Galaxy Note II] Xaositek:
Ok I have a random question - was reading about the new Google Calendar version and went to check for the update on my N2. It shows as "Installed" (on device and on the web-based play store).

The current device version is listed as version 201212060 (official playstore version)

The other version on my device (came from gapps/cm?) is listed as 4.2.2-eng.jenkins.20130529.002349

Sounds like CM nightly builds include the calendar which makes the need for the playstore version perhaps unneeded? Can it be removed and allow the playstore version to "take over"?
[Verizon Samsung Galaxy Note II] amoblox:
Regarding the compass:

This is a known issue with the Note 2 (i605). The compass is screwed up even on stock. The difference is that with CM the compass doesn't register at all. On stock, it won't remain in a solid state even if you're standing still. If you revert to stock and install a compass calibration app, you can literally set the phone down on a level table and walk away from it. Then you can watch it just spin 5-10 degrees in either direction like it's absolutely lost. Samsung support reps don't really acknowledge the issue and have offered a replacement device to me.

If you're planning to play a game like Ingress, you're in for a horrific experience. On CM, you will (usually) point in one direction but the app will track your location properly. If you're stock, your needle will just wander left and right.

Regarding your Google Maps issue:

Google Maps and most other Navi apps (Waze etc) can adjust your heading based on movement; they don't require the compass as it is just another mode of tracking. If you fire up your Navi app while you're at a stop, your direction will most likely be completely off but your location will be correct. On CM you have no hope of direction until you start moving because (again) the compass is non-functional. When stock, you should get some sort of heading before you start moving.

Sorry to be the bearer of this news, but I didn't want the devs to take too much slack.
[Verizon Samsung Galaxy Note II] Chadastrophic:
Oddly I never had those issues on TW or sbrissen posted builds. Didn't start until I went to this nightly.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
I can attest to the accelerometer and magnet sensors being really freaking horrible on stock. I noticed it very early in my experience with my brand new Note 2 back in December and googling it showed that all the Note 2's have this problem. Granted it still worked, but it was horrible nonetheless.
[Verizon Samsung Galaxy Note II] tithefug:
Status of GPS on the latest Nightlies

I've been following this thread, and I don't know if I missed it, or I just plain don't remember, but what is the current status of GPS in the latest nightlies?

I am currently running the 4/25 build from sbrissen, but was wondering if the changes he made in there have been merged into the main repository.

I haven't been in a rush to update as it's fairly stable (aside from the occasional camera crash), and I play Ingress, so the GPS needs to work properly. It would also be nice to get the patch for the Android OS issue to extend my battery even further.

Thanks in advance, and keep up the great work!
[Verizon Samsung Galaxy Note II] Chadastrophic:
I was on 4/25 before I updated to the nightly shown a few posts above, I'll probably go back to 4/25 and deal with the occasional camera issue.
[Verizon Samsung Galaxy Note II] bL33d:
Hmm so u saying the latest does not have camera issues it has a sensor issue cause I could careless about the sensor I just want a non buggy camera.

Hmm just flashed and gps works perfect as always.
[Verizon Samsung Galaxy Note II] GotRoot79:
Every time I make or receive a call this happens any ideas? Just did a clean wipe from a 4.1.2 stock ROM.
[Verizon Samsung Galaxy Note II] tithefug:
I got this for the first time yesterday. I had to reboot the phone for it to start working again. I thought that Google Voice might have played a role in the crash. Are you using Google Voice to make calls, too?
[Verizon Samsung Galaxy Note II] Xaositek:
Mine is doing this also. I was using GV, but had since uninstalled. Still going on even after uninstall and a reboot.
[Verizon Samsung Galaxy Note II] GotRoot79:
Just for voicemail.

---------- Post added at 11:11 AM ---------- Previous post was at 11:03 AM ----------

Just made a phone call after i rebooted my phone and it worked
[Verizon Samsung Galaxy Note II] snoozeallday:
Mine is doing this every time I try to make a phone call. Quite useless right now.

Also, I am not a google voice user and this is a fresh install.
[Verizon Samsung Galaxy Note II] sbrissen:
there was a mass telephony merge last night, our ril class changed. Try clearing cache and dalvik. If it continues to happen try to grab a log please.
[Verizon Samsung Galaxy Note II] Slack3r:
The phone process would keep locking up constantly for me, I think it was the t0lte update that did it. Reverted to yesterdays nightly and all is well.

I wiped cache/dalvik (the updater does this automatically, right?) and still had the issue, will try to find a log.
[Verizon Samsung Galaxy Note II] sbrissen:
Anyone having issues, try this build:

http://www.androidfilehost.com/?fid=22979706399753030

I haven't made any changes but this includes everything in cm's repos up until an hour ago and it seems to be working for me.
[Verizon Samsung Galaxy Note II] tithefug:
Does this also have your GPS changes from your 4/25 build, or are we still waiting for them to get merged?

Thanks!
[Verizon Samsung Galaxy Note II] sbrissen:
gps stuff has been merged, should be working.
[Verizon Samsung Galaxy Note II] GotRoot79:
I've made about five phone calls since my reboot this morning and it's working still.
[Verizon Samsung Galaxy Note II] Chadastrophic:
I didn't have phone process issues on the last nightly screen cap I posted, but I started having them on this build. I just went back to your 4/25 build.
[Verizon Samsung Galaxy Note II] GotRoot79:
Can i ask why you keep going back to build from april?

---------- Post added at 04:25 PM ---------- Previous post was at 04:22 PM ----------
[Verizon Samsung Galaxy Note II] tithefug:
Just updated:

Google Wallet was reset (hopefully, can be fixed).

Phone/Contacts is crashing on call.

I'm going to have to revert for now. If it's not resolved by Monday, I will install the latest nightly and try to get you a logcat.

---------- Post added at 04:38 PM ---------- Previous post was at 04:26 PM ----------

I also just updated the modem from here: http://xdaforums.com/showthread.php?t=2108510, but it still crashes.
[Verizon Samsung Galaxy Note II] Chadastrophic:
This is the first time I went back to 4/25, but I went back for the GPS fix and I had very little issues.

GPS/BT are huge for me with the camera being second. Need them for my job.
[Verizon Samsung Galaxy Note II] Slack3r:
Didn't fix the issue for me unfortunately, the phone process still crashes and the radio seems to reset itself. I have log files for both roms though, will be sending them your way.
[Verizon Samsung Galaxy Note II] strikeir13:
Does anyone else experience lag when activating voice search? It definitely isn't as fast as on TW. Wondering if it's just me?
[Verizon Samsung Galaxy Note II] E30Nova:
Wait, did the cause for the Android OS thing finally get found? Is there really a patch available? I tried flashing the latest modem like someone mentioned a couple pages back and it didn't do anything. I didn't go back to touchwiz though, but I don't see how that would make it any better...
[Verizon Samsung Galaxy Note II] Naimand:
I'm on another Rom and I notice the same thing. I just tried it again after initially running it and it is still a little slow.
[Verizon Samsung Galaxy Note II] Xaositek:
Just tried the 2013-06-01 nightly, same issues.
[Verizon Samsung Galaxy Note II] Slack3r:
Same problems for me as well.
[Verizon Samsung Galaxy Note II] Slack3r:
Just did a clean flash of the latest nightly and the error when a number is dialed is exactly the same as previous builds. Specifically this fatal error:

E/AndroidRuntime( 2709): FATAL EXCEPTION: Thread-54
E/AndroidRuntime( 2709): java.lang.RuntimeException: Method called after release()
E/AndroidRuntime( 2709): at android.media.ToneGenerator.stopTone(Native Method)
E/AndroidRuntime( 2709): at com.android.phone.CallNotifier$SignalInfoTonePlayer.run(CallNotifier.java:1826)

It's probably worth noting that the call goes through as it rings very briefly at the destination before the process crashes.
[Verizon Samsung Galaxy Note II] strikeir13:
Have you tried installing a Phone.apk from another nightly? I'm gonna try that, but I'm not optimistic.
[Verizon Samsung Galaxy Note II] lostnuke:
The 5/30 build works. That's what i reverted to.
[Verizon Samsung Galaxy Note II] psouza4:
Dialer FC's on me as well, which is obviously a show-stopper. Can't have a smart phone not be phone-capable. Noticed that the domain the FAQ links to in the OP is defunct, but I see nightlies are being churned out recently so I hope this project doesn't die. Appreciate the effort and looking forward to a stable build, but currently unusable as a daily driver unfortunately.
[Verizon Samsung Galaxy Note II] lostnuke:
Nightly builds aren't really meant to be daily drivers. Release candidates & milestone builds are considered stable. With that being said, the last few nightly builds are the only ones i have ever had trouble with. All the nightlies are usually very stable and DD capable. At least for me.

I have about 37 nightly builds on my SD card that are definitely DD capable.
[Verizon Samsung Galaxy Note II] Xaositek:
Anyone tried 6/2 Nightly? I noticed the BBQ log doesn't show any new nightlies change logs, just lots stacked up in Next Nightly. Perhaps they haven't committed the changes yet?
[Verizon Samsung Galaxy Note II] psouza4:
I'm aware -- I am a recognized developer and all. There are no RC's, M builds, etc. If there are prior dailies that are working, great, but the point I was making was the available builds are a no-go and the project's websites domains are busted. It'd be a useful contribution for you to share which nightly's are stable for you (in the sense that vital applications like dialer don't force close).
[Verizon Samsung Galaxy Note II] slick_rick:
As a recognized developer, you should know a logcat to go with your dialer fc would be helpful for sbrissen. Anyways, anything before the 29th or so should be fine if tonights nightly doesn't work for you.
[Verizon Samsung Galaxy Note II] Xaositek:
6/2 still broken. Just so no one else has to try.

If anyone wants to tell me how to pull that off (the logcat) I certainly will. I have the sdk loaded and can tail the logcat stuff. Just need that?
[Verizon Samsung Galaxy Note II] psouza4:
My dialer FC logcat looks the same as Slack3r, so it was redundant data. :D

Thanks for pointing me at pre-29th.
[Verizon Samsung Galaxy Note II] Xaositek:
Did the best I could... perhaps it'll help someone. I ran logcat -d > logcat.txt and hit upload.

E/AndroidRuntime( 3144): FATAL EXCEPTION: Thread-64

E/AndroidRuntime( 3144): java.lang.RuntimeException: Method called after release()

E/AndroidRuntime( 3144):	at android.media.ToneGenerator.stopTone(Native Method)

E/AndroidRuntime( 3144):	at com.android.phone.CallNotifier$SignalInfoTonePlayer.run(CallNotifier.java:1826)
[Verizon Samsung Galaxy Note II] lostnuke:
I'm having great luck with the 5/30 build and anything earlier (as already mentioned) Good luck!
[Verizon Samsung Galaxy Note II] strikeir13:
+1, looking forward to a fix though so I can continue crackflashing!
[Verizon Samsung Galaxy Note II] Xaositek:
BBQ-Log is fixed (who knows?)

Anyone got ideas on why nightlies are broken?
[Verizon Samsung Galaxy Note II] durango99:
Sbrissen wrote the following:

http://xdaforums.com/showpost.php?p=42056540&postcount=1134
[Verizon Samsung Galaxy Note II] Xaositek:
6/3 Nightly still has issues. Just a heads up to everyone
[Verizon Samsung Galaxy Note II] sbrissen:
Can I get a radio log of the phone crashing? logcat -b radio
[Verizon Samsung Galaxy Note II] Slack3r:
I went to get a log of the 6-3 nightly and could not make the problem occur... Would have severe crashes on every build after 5-30 but this one worked for me. Here is the log anyway I guess :p

Will run this build today and see if anything odd happens.
[Verizon Samsung Galaxy Note II] lostnuke:
Clean or dirty flash?
[Verizon Samsung Galaxy Note II] Slack3r:
Dirty since I ran it though the built-in updater, but it still wipes cache/dalvik. Also, when I tested on previous builds I had the same issue on both a dirty and clean flash, haven't tried a clean flash yet with this build though.
[Verizon Samsung Galaxy Note II] amoblox:
Greetings,

I'm coming from TW 4.1.2 stock right now; flashing 6/3. I'll keep everyone posted. Is there anything else I need to do to test this besides make a call? Looks like GV may have something to do with it (I use it only for voicemail as well).

Cheers
[Verizon Samsung Galaxy Note II] fallingup:
I had the crash, here is a pastebin of the entire logcat from when i made the call

http://pastebin.com/GwTfCria

And this was a clean install of just the rom, no gapps. Wiped data as well as dalvik and cache.
[Verizon Samsung Galaxy Note II] Xaositek:
Mine was a dirty flash running through the CM Updater, just letting you know.
[Verizon Samsung Galaxy Note II] amoblox:
I had an immediate crash when trying to make a call and then my service dropped completely. I was able to get service right away again.
[Verizon Samsung Galaxy Note II] fallingup:
Thats the exact same thing that happens with mine, dont know how there is someone that it doesnt happen to.
[Verizon Samsung Galaxy Note II] amoblox:
I'm gonna head back to 5/29 until this gets ironed out.

Edit: 5/28. Phone is working as expected.
[Verizon Samsung Galaxy Note II] Chadastrophic:
I'm on 5/29 and no complaints.
[Verizon Samsung Galaxy Note II] strikeir13:
Post back if you guys get the Sleep of Death.

Also, what should I be pulling to get the log for the Sleep of Death?
[Verizon Samsung Galaxy Note II] sbrissen:
http://www.androidfilehost.com/?fid=22979706399753841 I put the old RIL back in place without reverting other changes. Please try this if you have been having issues.
[Verizon Samsung Galaxy Note II] amoblox:
Had to use my phone for work today. Went back to stock. Sorry guys. I'll keep checking up on you all.
[Verizon Samsung Galaxy Note II] Xaositek:
Success! I just flashed and was able to dial numbers without issue. I left Google Voice installed so it did prompt for usage, then dialed through my mobile number.

I was also able to receive calls without issue.
[Verizon Samsung Galaxy Note II] amoblox:
I have this as well. I was wondering if it was just a timing thing.
[Verizon Samsung Galaxy Note II] amoblox:
Yes and no (respectively). Do a Wipe/Factory Reset before flashing the ROM and GAPPS and again after flashing the ROM and GAPPS. To erase everything, you'll need to actually format your storage from recovery (which you don't need to do).

Explanation: Wipe Data/Factory Reset > This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd ext partition that you might have setup.

via http://checkrom.com/threads/clockworkmod-explained.768/
[Verizon Samsung Galaxy Note II] BlueHarford:
Re: [ROM][SCH-I605][JB][4.2.1] CyanogenMod 10.1 official nightlies

Tango and Skype mic doesn't work
[Verizon Samsung Galaxy Note II] hopesrequiem:
Re: [ROM][SCH-I605][JB][4.2.1] CyanogenMod 10.1 official nightlies

Thank you so much for explaining that buddy. I appreciate it a lot bro