yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] dbrickg:
I installed it yesterday. It's running just fine. Haven't noticed any big differences. But I don't pay all that much attention to a lot of things that seem to be important to other folks. I hardly ever use my phone as a phone, to actually talk to people... what's the fun in that? It hasn't crashed or done anything else that's outstandingly egregious.

Edit: just installed the 06/27 nightly, and it's working, as well
[Verizon Samsung Galaxy Note II] amoblox:
The newest builds are really nice. I don't think we've had any issues that are stopping the progression of features. You know sometimes something new is released and it breaks something that was previously working; I don't see any of that happening. These guys seem to know what they're doing.

Huge thanks to the team
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Yeah running the 6/26 nightly as well and it's nearly perfect. Only remaining bug is the weird Android OS battery drain which last night kept my phone awake for almost 6 hours and when I woke up my battery was at 2%! Just caught it in time to plug it in before it died. Before you ask, it was at 40% when I went to bed.

This is an anomaly though and not the norm.
[Verizon Samsung Galaxy Note II] danibri82:
DSP Manager seems to be broken again.
[Verizon Samsung Galaxy Note II] jlvlawrence:
I didn't see a cm10.1 discussion thread so I'll ask this here. If have a friend with this phone, who I helped unlock/root/recovery. It seems like from the get go Android OS has been eating up a huge chunk of his battery. He keeps gps and Google location services off and I've also showed him how to use better battery stats. He sends me screenshots every few days from bbs, and it's pretty bad. I don't see anything out of the ordinary though. If feel like my Verizon gnex is getting better battery life than his note. He also gets the same results with aokp. Is this just a downside to running an aosp rom? Is it because of the lack of drivers and binaries for this phone? I assume that it is because cm posted something about it on their g+ page. I rock a nexus phone and tablet and have had no issues with cm10.1. Any advice/help would be greatly appreciated. Thanks!
[Verizon Samsung Galaxy Note II] akellar:
Check for wake locks
[Verizon Samsung Galaxy Note II] jlvlawrence:
He's sent me screen shots of BBS kernel and partial wake locks. I don't see anything out of the ordinary.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
I don't know where it happened but yeah, I'm getting ridiculous wake lock right now on 6/26. I thought it was just a one off thing but now it's constant. My battery is getting shot by Android OS way more than it ever has. Right now I've been off the charger for 7h 51m and I'm down to 50% with only 24 minutes of screen on time. Android OS is 50% of battery drain (screen is 14%) and it is showing 6 hours of Keep Wake.

This is TERRIBLE. Something is seriously messed up and it's destroying battery life on the latest nightlies.
[Verizon Samsung Galaxy Note II] dbrickg:
I didn't get this on 6/26 nor on 6/27. I seem to recall several people (myself included) getting really crappy battery life, where a simple reboot would fix the problem. Or maybe you have to reinstall the rom, or something.... but it seems like bad battery usage has always gone away for me, as suddenly as it arrived.
[Verizon Samsung Galaxy Note II] libbycm:
Does anyone know how to get service mode to launch? I see system apk in there but none of the known dialer codes I have tried seem to work. Searching has turned up Nada..
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
I've been clean installed for awhile, it's why I only change nightlies once every 4-5 days minimum. But I actually think I noticed something about this whole Android OS wake bug... the day I had SEVERE wake lock going on and my battery drained 50% in 8 hours with only like 20 minutes of screen on, I noticed that Beautiful widgets was taking up almost identical amounts of CPU time as my Android OS wake lock bug. I saw it and quickly removed the app (more on this in a second) and today my battery drain is just fine. Android OS is still numero uno but at least my battery drain looks about right for screen on and idle time. Nowhere near what it was the other day. So perhaps Android OS is just some kind of sum total of other things causing drain, in a wierd way? I don't know for sure but it certainly seemed tied to my Beautiful Widgets drain.

About uninstalling apps, it crashes Settings.apk EVERY time I uninstall an app. I thought it was just BW bugging out, but then I tried a totally unrelated app and yep all of them crash the phone. Can anyone else confirm?
[Verizon Samsung Galaxy Note II] dbrickg:
Nope, nothing like that here. I just tried uninstalling a couple of apps, one from Settings / Apps and one just by long pressing the icon and sliding it to the "uninstall" icon. Neither one crashed my phone.
[Verizon Samsung Galaxy Note II] scook9:
Are the notes on page 1 of this thread - like things that are broken - accurate to the current builds? I ask because 145 pages is a lot to read through.....
[Verizon Samsung Galaxy Note II] strikeir13:
GPS is great for me, others have had trouble. Haven't tested BT Voice Search but there is some Voice Search lag. Can't speak to 5ghz wifi as I don't have a way to test.
[Verizon Samsung Galaxy Note II] danibri82:
audio output for phone calls is stupidly low on this one..
[Verizon Samsung Galaxy Note II] BennyJr:
You can adjust it, in device settings.
[Verizon Samsung Galaxy Note II] Zlatty:
For whatever reason, I still cannot get wifi to connect. Quite annoying.

Sent from my Note II
[Verizon Samsung Galaxy Note II] cam30era:
Voice commands via Bluetooth are nonfunctional. This appears to be the case on all ROMs based on AOSP 4.2.x
[Verizon Samsung Galaxy Note II] dbrickg:
Not sure which is "this one". But I now have 20130629 and phone audio seems to be excellent. Likewise with 20130626, which is the last one I had installed.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Well this is beat. I have been dirty flashing nightlies just fine but then this struck me as odd that someone else wasn't experiencing the problem. So I did a total wipe and installed clean and waddya know. Problem solved.

Well no more dirty flashing for me. Gonna have to figure out some ways to minimize downtime every time I update to a new nightly. Gonna probably just install weekly for now.
[Verizon Samsung Galaxy Note II] jason1332:
Man, the 28 nightly ate my battery alive. Going back to 27.
[Verizon Samsung Galaxy Note II] iflip:
Do I flash 2.3.3.2 in recovery?
[Verizon Samsung Galaxy Note II] dbrickg:
I'm not sure what you mean by "dirty flashing." Do you, at least, clear the dalvik cache? I always do that, and clear cache, but have never done a total wipe, not since I first installed cm10.1, and I've never had any trouble with the play store. If you just clear the caches, you won't have to restore all your apps.

---------- Post added at 09:44 AM ---------- Previous post was at 09:37 AM ----------

It's not necessarily the 28 nightly's fault. I've seen numerous posts in this thread saying that battery life sucks on some particular nightly, but it turns out, almost always, to be some quirk that goes away with a reboot.

---------- Post added at 09:55 AM ---------- Previous post was at 09:44 AM ----------

It suddenly occurred to me that you might be using a headset. My phone conversations seem plenty loud on the built-in earpiece speaker, but I haven't tried with a headset. There are some weird audio things going on, at least for me, when I try to output sound via the audio-out plug. Maybe related to the "safe headset volume" setting, and maybe related to the kernel I'm using. But the built-in speaker and earpiece speaker seem to be quite loud enough.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
I wipe cache and dalvik cache every single time I dirty flashed. That's what a dirty flash is. Leave system and data, and wipe caches. I'm confirming right now that it caused a bug in the settings apk when uninstalling various unrelated apps. I would get a force close every single time.

If you're not getting errors thats great and I am jealous. But I got an error and won't be dirty flashing ever again.
[Verizon Samsung Galaxy Note II] libbycm:
When you dirty flash are you wiping system part before flashing? If so are you reflashing gapps zip afterwards? I ask because sometimes would format system before loading new nightly and forget to flash gapps again and then would get a bunch of FC's when it booted back up until I reflashed gapps package.
[Verizon Samsung Galaxy Note II] dbrickg:
Yes, that's what I thought "dirty flashing" was. But I get the impression that some people are doing a "really dirty flash," not even clearing dalvic. But maybe they are, and don't bother to mention it, since everybody knows to do that. I also always reflash gapps, but some people are, I'm pretty sure, saying that they don't do that.
[Verizon Samsung Galaxy Note II] strikeir13:
Anyone else experiencing low in call volume? It's a little low and it's at the maximum recommended 80%
[Verizon Samsung Galaxy Note II] sbrissen:
try voluming down then up again while incall, it forces it to reread the setting.
[Verizon Samsung Galaxy Note II] dbrickg:
Yes, quite quiet... and Settings / Advanced / Audio / In-Call Audio Volumes was set to 100%. I tried sbrissen's trick of voluming down then up again while incall, and volume did weird things: actually went up for a split-second when I first hit the volume down button, then back down... sometimes it seems to be ok, but mostly it's just too quiet. Seems like there've been other users reporting low volume for in-call audio. When I first saw that, I tried, and mine seemed fine, but now it's gone all quiet.

---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------

So, this trick sort-of works, but mostly it doesn't. With volume all the way up, I can hear ok in a fairly quiet room, but in a noisy environment, it'd be really hard to hear.

---------- Post added at 06:54 AM ---------- Previous post was at 06:46 AM ----------

Agreed. When I first saw your post, I said my volume was fine. But starting yesterday, it got too quiet.

The only thing I can think of that might (maybe even probably) have affected it was a new kernel. I upgraded the "matrix" kernel to it's latest incarnation, the "plasma" kernel, and switched from voodoo audio to AndreiLux's Wolfson Sound Control, which is built-in to the kernel. This seems like the likely culprit. But nonetheless, even before that change, the volume was ok, but *just* ok. Seems like you should be able to turn it up to where it's *too* loud, if you want. As it is now, it's just barely tolerable at best.

PS: just reread this, and it sounds like I'm complaining, which is not what I meant to do... just wanted to get as much information as possible out there.
[Verizon Samsung Galaxy Note II] danibri82:
As far as volume this is what I see...

Speakerphone is too quiet, almost unusable.

Handset volume is tolerable, as long as there isn't too much ambient noise.

Phone call with headphones in is far too quiet.

Music plays well through speaker, headphones and Bluetooth to SYNC.

DSP is working again. Kinda. It seems the headphone settings control everything.

When connected to my Mustang over Bluetooth the Bluetooth in DSP did nothing but headphones in DSP did make a difference.

The additional volume controls don't do a thing. They don't work.
[Verizon Samsung Galaxy Note II] dbrickg:
Just reflashed yesterday's rom, without the kernel, and the earpiece volume was still too quiet.

---------- Post added at 07:29 AM ---------- Previous post was at 07:27 AM ----------

Thanks for the detailed analysis. I haven't had time to check all of those bits, but earpiece is definitely too quiet. I have everything in DSP disabled. Settings / Advanced / Audio / In-call Audio Volumes is at 80%
[Verizon Samsung Galaxy Note II] eBoody:
After several restarts my battery has been awesome. Ill attach some photos.

for the screenshot at the home screen, theres a widget up top that says 3 things; 1: the average rate of discharge, 2: how many hours i have left till discharge, and 3: the percentage of charge lost in how many hours.

Those are some good numbers im seeing there, and thats after sleeping with a youtube video playing for 4 hours, and i was not plugged in.

I want to thank the team for this ROM

I just wish the volume thing will get sorted out soon =/
[Verizon Samsung Galaxy Note II] dbrickg:
There's a bit of a thread on this in the Plasma (was Matrix) kernel thread saying that setting the In-Call Audio Volumes to 60% works best.

See: http://xdaforums.com/showpost.php?p=43186241&postcount=175:

and a couple of posts later:
[Verizon Samsung Galaxy Note II] strikeir13:
Wow, it's kinda ridiculous how much louder 60% is than 90%... For anyone having low volume issues, try resetting to defaults, then set to 60% in call volume. Haven't tested the other volumes.
[Verizon Samsung Galaxy Note II] shangrila500:
After I saw the post about 60% after my initial post saying don't go higher than 90% I tested 60% and I most definitely get louder volume on VRB and Plasma 1.65 with 90% and can actually boost it just as loud as I ever have been able to. I of course had my Plasma settings for audio tweaked to my liking.

It most definitely is a ROM issue as opposed to a kernel issue. Hopefully our talented devs will be able to figure it out soon but if not in happy tweaking with my settings and running a different kernel.

---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------

What's really crazy is when you go to 100% and its as low as if you had set it to 10%.

For me on VRB 90% is definitely louder but on CM 60% may be the loudest.
[Verizon Samsung Galaxy Note II] eBoody:
Hey bud, I've been looking around and I can't figure out how to get Wolfson sound engine controls... I might be completely missing something. For the earpiece the sound is totally fine, but for speaker phone it's not. Could you direct me as to how to get Wolfson controls?

Thanks for posting your Audio controls for STweaks in the plasma Kernel thread by the way im trying them out now

Edit: Omg, Shangrila! Youre awesome. Your STweaks Audio settings totally worked! The Speakerphone and Ringer volumes are totally loud now! thank you thank you thank you. for the record, on the cm10.1, Plasma Kernel, 7/02 nightly, advanced settings->audio controls -> in call volumes set at 60% with your Stweaks profile.

for anyone else looking for Shangrila's settings his post is here: http://xdaforums.com/showpost.php?p=43206731&postcount=183
[Verizon Samsung Galaxy Note II] shangrila500:
No problem, is everything working now? You got Wolfson online?
[Verizon Samsung Galaxy Note II] libbycm:
I can't be only one with this question :D
[Verizon Samsung Galaxy Note II] shangrila500:
AFAIK service codes only work on TW, there may be a few that work for AOSP but they will not be the same ones that work on TW.
[Verizon Samsung Galaxy Note II] eBoody:
I didnt have find to wolfson. I actually dont have voodoo or Wolfson. but when i unchecked voodoo and checked wolfson, all of the volume controls took effect. If im not mistaken the note 2 has a wolfson sound chip. perhaps you dont need the app to control the audio settings in Stweaks since youre telling Stweaks to change the settings that are built in?
[Verizon Samsung Galaxy Note II] strikeir13:
So just had a call where the 60% setting was almost too loud... Awesome :) though maybe that should make 60% the upper limit and not what it is now?
[Verizon Samsung Galaxy Note II] shangrila500:
Well the way I understand it is the controls for the sound is built into the kernel, hence why you have to have a kernel with Voodoo implemented before you can use Voodoo sound control, so......

And yes we have a Wolfson chip but the actual drivers and such for the chip have to be built into the kernel.

---------- Post added at 10:56 PM ---------- Previous post was at 10:54 PM ----------

Well 60% is just setting it up at its loudest, kind of like when you are on TW and you have the volume up all the way, so you can still adjust it with the volume keys while in a call. I would leave it asst 60 and just adjust it in call to whatever you need that way if you get a call you can barely hear you can jack it up.
[Verizon Samsung Galaxy Note II] johnwaynegacy:
It has been a long while since I flashed a rom, and my phone is getting kind of sluggish. Is this rom still filled with bugs, or is it good to go? It doesn't look like the OP has been updated in a while, and I don't feel like sifting through the thread.
[Verizon Samsung Galaxy Note II] lostnuke:
Good to go
[Verizon Samsung Galaxy Note II] miketoasty:
Go to: http://get.cm/?device=i605

Get the latest nightly, and enjoy what felt like a brand new phone to me coming from TW.
[Verizon Samsung Galaxy Note II] strikeir13:
What I meant was since 60% is actually the loudest, it should be set in the ROM as 100%. I'm not sure what the sliders are adjusting, but apparently whatever they are adjusting does not correlate with the volume so much...
[Verizon Samsung Galaxy Note II] whojabacod:
What is up w the compression on mms sending w this ?
[Verizon Samsung Galaxy Note II] eBoody:
the nightlies are updated every day if im not mistaken...the post is irellevant. there are links to the nightlies and the change-logs in the OP, and thats what gets updated. There are some bugs, as it is a nightly of a ROM that wasnt intended to work with our chipset (CPU). However, after doing the GPS fix in the OP, flashing Plasma Kernel, and after setting up stweaks for some sound settings, it works pretty flawlessly as far as i can tell. you should read the last page or two of posts to understand what i mean. im loving this rom though.

---------- Post added at 07:00 PM ---------- Previous post was at 06:52 PM ----------

i literally just sent a pic, and the quality was terrible >_>
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Anyone in here using the Photosphere camera and noticing how FUBAR our accelerometer and magnetic sensors are? What I mean is let's say I start off doing one "row" at a time of the photosphere. I'll put my phone eye level and rotate around the camera lens (meaning the phone is in the same spot, I rotate my body) and do a full 360. By the time I've done 360 degrees and am back looking straight forward, the camera is showing shift slightly behind my correct rotation. It's as if the sensors aren't even close to accurate. This makes taking Photospheres nearly impossible and I wonder if it's hardware or what. Perhaps this is why Google is hesitant to get Photosphere out on more phones because the magnetic sensors are just junk and not accurate enough to maintain 1:1 rotation?
[Verizon Samsung Galaxy Note II] Seamonkey79:
I'm not sure what goes on with it, but every now and then I've run into that even on a TW based ROM. I've somewhat aleviated the issue by rolling the phone over a few times and waving it around like a little kid with a toy and that makes it work pretty well for a bit, but it has cost me some great panoramics, sadly.
[Verizon Samsung Galaxy Note II] eBoody:
im going nuts trying to theme the framework-res.apk....

Does anyone know if theres something about CM that doesnt allow you to use a modified framwork-res.apk?

I used apktool to decompile, changed some png's,recompiled and signed it. but everytime i try to push it to my device i get stuck at the boot animation.

i tried using the adb shell, i tried using a file explorer (in windows and in the device itself) and i tried using ninjamorph, but none of them work.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Glad I'm not the only one and yeah, had a couple nice spheres ruined because the phone is just flat out off. Say I do 360 degree rotation, the phone thinks it's only done about 330 degrees. As you would imagine, this totally ruins any chance of getting a proper panoramic or photosphere :/

I have totally wiped and gone back to TouchWiz for now, will try it out on here and see how it goes. Got a feeling it won't be any better. Curse you Samsung for shoddy magnetic sensors!
[Verizon Samsung Galaxy Note II] amoblox:
Let's keep the volume issue in our sights. Once that is ironed out, we can move on to Photosphere. Not everyone uses Photosphere but everyone uses the volume.
[Verizon Samsung Galaxy Note II] eBoody:
Shangrila solved the issue for me. Flash plasma kernel, install stweaks, go to advanced settings to audio to in-call and set them to 60, open stweaks , check Wolfson, then turn up the knobs that Shangrila posted. In fact, I had to turn it down a bit because it was so loud! Good luck!
[Verizon Samsung Galaxy Note II] strikeir13:
Also, photosphere isn't currently intended for our phones. There could be some calibration or something needed to make it perform right. The volume is intended for our phones...
[Verizon Samsung Galaxy Note II] shangrila500:
I can tell using the sliders, after adjusting the Audio under Device Options up to 60 and using Plasma with Stweaks to bump it up a little louder. Mine will actually decrease to the point that there is barely any sound coming from the speakers. Before I did all that adjusting it did nothing.

---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------

For those of you using, Photosphere which one are you using? Are you using the older one or the newest one that was leaked from the GPE ROM that is rumored to be the 4.3 camera?

Also have you tried the Photosphere stitching fix that was released not too long ago?

http://www.mediafire.com/download/re3leray6hku81w/PhotosphereGS4GEfixed.zip
[Verizon Samsung Galaxy Note II] BennyJr:
We shouldn't have to flash a separate kernel for the sound to be good.
[Verizon Samsung Galaxy Note II] shangrila500:
You don't *have* to it just helps make it louder, and considering this is a nightly and not everything is perfect since they are trying to build something blindly, since Sammy won't release the code we need, it is something that is going to happen. Hell, even the stock kernel isn't perfect and people flash other TW kernels to fix issues.

Its a nightly, when you flash it you flash with the understanding that not everything will be perfect and you may have you change certain things or deal with it until its fixed. So deal with it.
[Verizon Samsung Galaxy Note II] sbrissen:
when the audio goes extremely low it means its passed the max volume, I ran into that when initially doing the adjustments. The nature of the adjustments, I've found its necessary to volume down/ volume up for it to re-read the levels. For incall you may need to s do the adjustments while in a call and again volume up/down. I'm still on vaca for another few days but will look at volume when I get back.
[Verizon Samsung Galaxy Note II] amoblox:
That's great for you, but it's not a resolution; it's a bandage that most users do not want to use.
[Verizon Samsung Galaxy Note II] eBoody:
well then dont flash a nightly. I dont understand what you expected.
[Verizon Samsung Galaxy Note II] amoblox:
No one said anything about it being a deal breaker. Relax.
[Verizon Samsung Galaxy Note II] eBoody:
Im relaxed..

im just saying, when you point out that its not a resolution, id have to disagree based on the context.

Same goes for your saying that its not a solution for "most users". It depends on the context.

if you meant its not a solution for most smartphone users, id agree with you.

but since were in a ROM forum talking about flashing roms, and flashing kernels, and the population of these forums is that of people who arent afraid of settings, the context of "Most user's" turns into 'most-XDA-forum users'. In which case it would indeed be a solution. And it is.
[Verizon Samsung Galaxy Note II] amoblox:
Thanks for voicing your opinion.
[Verizon Samsung Galaxy Note II] eBoody:
Likewise
[Verizon Samsung Galaxy Note II] computerslayer:
Anyone else having an issue with the dialpad not doing anything during some calls? On a clean install of the July 6th release, I can consistently reproduce this issue just by dialing my voicemail. Anyone else able to reproduce this?