yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] kejar31:
I believe that BT is fixed in source.. He just hasn't compiled a new build and released it with the fix.
[Verizon Samsung Galaxy Note II] WishRyder:
I can't for the life of me get the GPS (or compass) to work on anything but Touchwiz roms. I spent hours yesterday flashing every whichway. TWRP, CWM, clean, dirty, alpha 1 to alpha 2, bouncing back and forth between various Touchwiz and CM10 roms, wiping cache, not wiping cache, formatting storage. I verified location settings were using internal GPS, toggled location services on/off, downloaded a bunch of different GPS Fix/Test/Tool apps, manually copied in various gps.conf files, fixed permissions, I even plugged my phone in, set my phone not to sleep, ran a non-stop GPS acquire utility, went to bed, woke up 8 hours later, nothing.

With all of my previous devices (and I've had quite a few), I've always been one of the lucky ones that ends up on the "Mine's working fine" side of things. If this is how the other side lives... :(

Back to Beans I guess.
[Verizon Samsung Galaxy Note II] kejar31:
here is the error from logcat on the camera issues.. Like I said I am able to reproduce the issue.. Simply use the press to focus option with the flash set to on.. after you get a lock press the shutter button.

I/ServiceManager( 1993): service 'SecTVOutService' died

I/ServiceManager( 1993): service 'media.audio_flinger' died

I/ServiceManager( 1993): service 'media.player' died

I/ServiceManager( 1993): service 'media.camera' died

I/ServiceManager( 1993): service 'media.audio_policy' died

W/Camera (29936): Camera server died!

W/Camera (29936): ICamera died

E/Camera (29936): Error 100

E/CameraErrorCallback(29936): Got camera error callback. error=100

D/AndroidRuntime(29936): Shutting down VM

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

E/AndroidRuntime(29936): FATAL EXCEPTION: main

E/AndroidRuntime(29936): java.lang.RuntimeException: Media server died.

E/AndroidRuntime(29936):	at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:32)

E/AndroidRuntime(29936):	at android.hardware.Camera$EventHandler.handleMessage(Camera.java:810)

E/AndroidRuntime(29936):	at android.os.Handler.dispatchMessage(Handler.java:99)

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

E/AndroidRuntime(29936):	at android.app.ActivityThread.main(ActivityThread.java:4931)

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

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

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

E/AndroidRuntime(29936):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)

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

D/dalvikvm( 2938): GC_FOR_ALLOC freed 1907K, 38% free 11948K/19011K, paused 50ms, total 50ms

W/AudioSystem( 2938): AudioFlinger server died!

W/AudioSystem( 2938): AudioPolicyService server died!

W/ActivityManager( 2938): Force finishing activity com.google.android.gallery3d/com.android.camera.CameraActivity

I/mediaserver(31153): ServiceManager: 0x40db2dc0

D/SecTVOutService(31153): SecTVOutService instantiate

E/ (31153): fb_open: fb[0] open failed

E/ (31153): bool android::SecHdmi::create(int, int):Failed to open default FB

E/SecTVOutService(31153): android::SecTVOutService::SecTVOutService()::mSecHdmi.create() fail

D/SecTVOutService(31153): SecTVOutService r=0

I/AudioFlinger(31153): Using default 3000 mSec as standby time.

I/CameraService(31153): CameraService started (pid=31153)

V/CameraWrapper(31153): camera_get_number_of_cameras

V/CameraWrapper(31153): check_vendor_module

D/SecCameraHardware(31153): LSIHAL int android::HAL_getNumberOfCameras()
[Verizon Samsung Galaxy Note II] illogic6:
You and me both.
[Verizon Samsung Galaxy Note II] speedfreak228:
Weirdest thing just happened..... I'm on a phone call and my phone just hangs up. So I call them back and the phone app just keeps force closing. The person on the other end could still hear me but I couldn't hang up or anything

EDIT: a reboot has seemed to fix it for now
[Verizon Samsung Galaxy Note II] kejar31:
It is strange.. While I am not having an issue getting CM or and AOSP gps to lock I am not getting an issue with Clean ROM :( and it worked before I installed CM :(

Oh well I think CM is working good enough to be a daily driver as of now so I am good.. Just a few quirky issues to work out :) I bet sbrissen will have it ll worked out soon enough
[Verizon Samsung Galaxy Note II] WishRyder:
On a side note...I just flashed the latest PAC-man rom that came out today, and the GPS worked right from the get-go. Magnetometer still wasn't working, so no compass/heading, but it's a step in the right direction anyways.
[Verizon Samsung Galaxy Note II] kejar31:
Okay I want to make anouther point here.. I went ahead and reinstalled the Clean Rom, then installed the 4.2 camera app. And after repeating the proccess I got the same FC so this may be a point with one of the props being used for the cam.
[Verizon Samsung Galaxy Note II] illogic6:
Were you connected to WiFi at the time? I can get a lock on WiFi on all of the AOSP ROMs. It's when WiFi isn't available that I have the problem.

Edit: Apparently, having WiFi toggled on without being connected to anything is enough to get accuracy down to 50 meters. With WiFi off, I haven't seen anything better than 2000 meters.
[Verizon Samsung Galaxy Note II] WishRyder:
Nope. Wifi wasn't on. Not sure why, but it worked. I still went back to Beans though. I can't do broken compass either.
[Verizon Samsung Galaxy Note II] illogic6:
I got a fix using Paranoid Android today while running this app! I'm excited!

https://play.google.com/store/apps/details?id=com.androidlab.gpsfix

Really only took a minute or two to fix. Wonder if it'll work again after a reboot...

Edit: This is the first time I've had an AOSP rom installed for more than an hour or so. I wonder if it takes some time to kick in or something.

Edit2: *Sigh* After a reboot, it seems I am unable to reproduce these results. (or at least it isn't happening in less than 15 minutes) I wonder what the hell I did last time.

Edit3: I've flashed back and forth and screwed around with the gps.conf file a bit. Suddenly I find that I can: 1) Wipe system and data. 2) Flash Paranoid Android (Which I assume is roughly the equivalent of this thread's ROM) 3) Boot into System, log in to Play store, download Google Maps and get a 6 meter fix sitting indoors at my desk. I don't know what I did but it works now. It makes no sense to me at all, but I'm happy. This is now my daily driver.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Just want to clarify something.

That "lock" you're getting with Wifi enabled is not a lock at all. It's an alternate location service. This is part of the Google Location Services that you have enabled in your Settings->Location menu. The order of location priority goes like this:

Cellphone towers - 2000 meters average accuracy

WiFi signals - 20 - 60 meters average accuracy

GPS signal - 1-10 meters average accuracy.

And just so you know, if GPS is working you will have an icon in the top left part of your notification menu. If there is no dot icon blinking, then GPS flat out isn't working and you'll never get a lock.
[Verizon Samsung Galaxy Note II] illogic6:
I am aware of this. The only reason I mentioned it was to make sure the other people claiming it worked weren't reporting false positives.

This is what a GPS lock looks like. I get them pretty much instantaneously now. Still not sure what I'm doing different now, if anything. http://i.imgur.com/ofqdh.png

(I realize I have WiFi toggled on in that screenshot. It's working toggled off as well.)
[Verizon Samsung Galaxy Note II] slick_rick:
Bought time this got moved. Nothing more original than CM :)
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
What's the distinction? I'm curious why split the ROM and kernel section into two sub-forums and what anyone would gain from this.
[Verizon Samsung Galaxy Note II] johnwaynegacy:
First off, I have been running cyanogenmod since 5.7. I have had my hands on quite a few devices. The Note 2 is by far the best. But, that is a problem for me in a way. Though I have not tried cm10, I used cm9 as my daily driver since its release. What does cm10 have to offer me that is improved over a touchwiz rom? The phone is so powerful that nothing slows it down, and battery life ( at least for me ) is not an issue. It has all kinds of features and eyecandy. I can enable or disable my proximity switch, I love that idea. I don't remember that being in any cm rom I have ever tried. But, back to the question. Seeing as I have yet to try cm 10. What is better about this, on this phone? :confused:
[Verizon Samsung Galaxy Note II] kwkw480:
You'll find out when key lime pie is released while the verizon note 2 will be waiting. 6+ months for the upgrade :)
[Verizon Samsung Galaxy Note II] sway20:
Why ask? If you've run cm before you know what it has. Cm10 has the same thing as cm10.1 just with the updated 4.2.1 features and maybe a few more tweaks. If you like tw and find it has everything then stay with that. I love having the tw features on this phone personally, but I'll never shy away from aosp or cm/aokp/paranoid roms.

tappin from the Note II
[Verizon Samsung Galaxy Note II] jrollette:
Bluetooth Signal Strength dependent on WIFI Tether

OK,

I am using slick_rick's ALPHA2 Paranoid ROM, based off of sbrissen's CM10 ROM. I am posting here because since my guess is that this would relate to the base CM build. I hope this information is useful.

Bluetooth audio was cutting out on me constantly with my phone in my pocket. However, I noticed that BT Audio was working great at work. Then I realized that the only difference is that I have WIFI Tethering enabled at work So, I enabled WIFI tether and the the Bluetooth audio immediately stopped cutting out.

I installed the "Bluetooth Finder" app on another phone, with the phones about 6 feet apart:

With WIFI Tether OFF, BT signal strength was about -93dbm and dropped completely to 0 at times

With WIFI Tether ON, BT signal strength was about -60dbm consistently

I tried the same test with just normal WIFI, but BT signal strength stayed the same. WIFI Tether was the only thing that improved the BT signal.

This behavior is repeatable and persists through reboots and reflashing, wiping cache).

Thanks for all your work on this ROM!
[Verizon Samsung Galaxy Note II] speedfreak228:
Does anyone have a flashable zip for Bluetooth fix?
[Verizon Samsung Galaxy Note II] slick_rick:
What? Its already fixed in the alpha3 build.
[Verizon Samsung Galaxy Note II] speedfreak228:
I didn't even realize alpha 3 was up. Thanks :o
[Verizon Samsung Galaxy Note II] jwadejr9:
This may have been answered or maybe I'm just ignorant as to the reason, but why is this cm10 and not 10.1 since cm has pretty much fully merged over to 10.1? Sorry if the answer is obvious or it has already been discussed. Top notch work BTW, sbrissen. Great ROM!!!
[Verizon Samsung Galaxy Note II] slick_rick:
Because CM10.1 is a whole different ballpark. Brings its own problems and is pretty unstable at the moment. CM10 on the other hand works pretty well.
[Verizon Samsung Galaxy Note II] jdiegmueller:
GPS on CM10

Firstly, amazing job getting CM10 going so quickly on this device. Thank you sbrissen & others.

Based on my usage pattern(s), the only issue I've had so far (and this has been true of ALPHA2 and ALPHA3) has been that the GPS doesn't work. As opposed to some who say they get a lock and then lose it, I have not gotten a lock yet on CM10 at any point.

Based on some comments/suggestions in this thread and on rootzwiki, I tried the following:

* Flashed back to a TouchWiz ROM,

* Fired up GPSTest Plus and got a lock (accuracy was indicated to be 10 feet)

* While GPS was locked, rebooted in to Recovery and did a wipe+flash of ALPHA3,

* Re-installed GPSTest Plus and this time get no lock, no GPS satellites in view (0), no GPS satellites in use (0), etc.

* Tried using the GPSTest Plus "Clear AGPS" and "Update AGPS" buttons in GPSTest Plus to no avail

Under "Location access", I do have "Use Internal GPS" selected for GPS Source (I believe it is blank/unselected, initially, after a flash of CM10).

Last night (on ALPHA2), I tried letting GPSTest Plus run overnight while sitting on a windowsill but still had the same results: no GPS at all even after 6 hours.

Thoughts? I'm happy to wipe, experiment, re-flash, etc.

Thanks all,

-jd
[Verizon Samsung Galaxy Note II] FrankyFiggz27:
i have 1 thing u can try..i was going to try this myself later but im in class right now and will be for another 3 hours. wana boot this baby up so bad, but can't deal with no gps. i get lost too often. here's the link - http://xdaforums.com/showthread.php?t=1247683. please report back. Also, btw I noticed that if I ran GPSTest before installing Maps, i would get locks. then once maps was installed, no mas. clearing data in maps might help temporarily though. or just getting it going then installing maps after.
[Verizon Samsung Galaxy Note II] JustusIV:
Does any know if this has the DRM files required by HULU?
[Verizon Samsung Galaxy Note II] jdedeaux:
I hate to ask this question sounding picky but I am curious if the occasional garbled call issue is still present in ALPHA3? I hear a reboot fixes it but has that been haxed yet?
[Verizon Samsung Galaxy Note II] jdiegmueller:
I reviewed the thread you referred me to, which led to trying a few things:

* /etc/gps.conf modifications

* /etc/gps.conf modifications: Part 2 (IPs instead of FQDNs)

* /etc/gps.conf modifications: Part 3 (IPs but with modifications by me eliminating the invalid IPs and inserting my home NTP server)

* build.prop modification

* Uninstalling Maps

All led to the same result: GPSTest Plus with nothing but 0s and no signs of life.

-jd
[Verizon Samsung Galaxy Note II] FrankyFiggz27:
Fu*k
[Verizon Samsung Galaxy Note II] kwkw480:
Does anyone know of a way to increase the in call speaker phone volume? It currently is extremely low. Also is the mute button working for anyone? I'm not complaining because I understand this is an alpha. I'm only curious. Thanks
[Verizon Samsung Galaxy Note II] jmill75:
I would like to know this also. Only thing keeping me from running this full time
[Verizon Samsung Galaxy Note II] kejar31:
Yes
[Verizon Samsung Galaxy Note II] jdedeaux:
ill take that as yes it is still present ,lol -i asked too many questions in one sentence
[Verizon Samsung Galaxy Note II] jacob4duke:
Im not sure if this is an issue for anyone else but my SDcard does not come up as a media or anything for that matter on my computer and was wondering if there is a fix for this?
[Verizon Samsung Galaxy Note II] kejar31:
Lol yes it makes the loud noise in your ears sometimes while trying to make calls still... Sucks too but it seems to be a problem with all 7105 based notes as my coworkers att one does it with CM as well
[Verizon Samsung Galaxy Note II] Breezer23:
I'm really enjoying Alpha 3! Only real issue for me is battery life just being mediocre at best.

Thanks for all the updates!
[Verizon Samsung Galaxy Note II] scott_65:
Hey guys, I've been lurking around waiting for the kinks to get worked out of this ROM. I just bought my note II a few days ago and love it. I got mixed up earlier and accidentally read some of the posts for sprint instead of verizon's note II so I'm not sure if anyone on verizon is having any LOS problems. If so, it may not be due to this rom, because I'm running completely unmodified and am having some issues with sms's not going through until after several tries. Just thought I would throw that out there in case it helps someone

And thanks to the devs taking time to work on this for everyone else's benefit. Can't wait to run this thing daily!
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Yeah I was having issues on stock 4.1.1 TouchWiz with sending SMS at times. Sometimes it would only work sending it to certain people, other times it would crap out entirely and I wouldn't be able to send any texts at all.

So I don't believe that's a ROM problem at all.
[Verizon Samsung Galaxy Note II] Gottoon:
I think there might be a bug in the over the air activation (OTAA) software. No keypad opens to select the options while on the call.

After the flash I am not getting as strong 4G/3G coverage in my sparse (barly works at all) coverage area at work. Had some issues with it showing roaming as well. Figured a PRL update was in order but can't complete one. :(

Anyone know of another way to get this to update?

Gottoon
[Verizon Samsung Galaxy Note II] tithefug:
I think *22891 and *22892 (I forget the difference) will automatically enter the activation menu without pressing the keypad. Report back if it doesn't.
[Verizon Samsung Galaxy Note II] Gottoon:
thanks... the *22891 started the activation but it failed almost instantly stating it can't be programmed and to call my service provider. *22892 was some AT&T service that was no longer working. Tried it a few times without luck in the strong service area at home.

Any more suggestions?
[Verizon Samsung Galaxy Note II] basedboii:
i cant wait for this rom to be stable!!!
[Verizon Samsung Galaxy Note II] JustusIV:
Why does the external sd card go to /storage/sdcard0 or 1(forgot which one) but the touchwiz is /storage/extSdCard.

Breaks things for me trying to switch back and forth. Every time I have gone AOSP I nandroid back because I don't want to deal with it.
[Verizon Samsung Galaxy Note II] nnnnr14:
Probably has a sd swap embedded somewhere in the rom, I'm not 100% sure about that but that's what it does.
[Verizon Samsung Galaxy Note II] krayzee:
it's something to do with Multi-user support going forward i believe.
[Verizon Samsung Galaxy Note II] Gottoon:
The external one is sdcard1 the internal is sdcard0.

I believe it is mounted this way in touchwiz as well as the extscard name. This should help with development as time goes on because it will be uniform structure for all devices no matter the manufacturer.

At least this something I have seen on the newer phones. Have not read up on this anywhere yet.
[Verizon Samsung Galaxy Note II] DaRkL3AD3R:
Mmmmm nope I can confirm for TouchWiz 4.1.1 the actual SD card is /storage/extSDcard/ not one of the /sdcard0/ etc.

Wonder whats up with that. Maybe Sammy just lagged on making the change for the Note 2. Hope this doesn't cause any problems in the future :(
[Verizon Samsung Galaxy Note II] fallingup:
NEVER, EVER, EVER, DIAL *228 OR ANY *228 VARIANT ON AN LTE DEVICE ON VERIZON!!

It will burn your sim card. it is unnecessary on it as well.
[Verizon Samsung Galaxy Note II] nnnnr14:
It won't burn your SIM card... Lol
[Verizon Samsung Galaxy Note II] fallingup:
The chance is there for it to. The way that VZW implemented sim cards was half baked, and it does cause issues. I know it caused issues at least up to the GS3.

Its still not something that you need to be doing with a sim card.
[Verizon Samsung Galaxy Note II] sbergman27:
Severely reduced Bluetooth Audio range?

One thing I've notice since I flashed Alpha3 over the Samsung factory image is dramatically reduced Bluetooth audio range. I have to keep the phone in the shirt pocket closest to the ear my bluetooth device is in. And even then reception is very spotty. It's nice that BT audio streaming works in Alpha3. But is anyone else noticing this range problem?

Thanks,

Steve Bergman
[Verizon Samsung Galaxy Note II] jacob4duke:
I'm not trying to rush at all but i was just wondering if we will see cm10.1 in the near future?
[Verizon Samsung Galaxy Note II] slick_rick:
Yes. Sbrissen is working on it :)
[Verizon Samsung Galaxy Note II] jacob4duke:
OMG that is soooo sweet to hear...or read i guess:confused:

but yea i cant wait :laugh::laugh::laugh:
[Verizon Samsung Galaxy Note II] sbergman27:
My understanding is that the only major todo preventing an alpha 1 release is the lack of in-call audio. There's some debate as to whether that should be a considered a show-stopper for a phone OS, which is, I think, an interesting reflection on our community. ;)

See sbrissen's Twitter feed for details.
[Verizon Samsung Galaxy Note II] Breezer23:
Hahahahaa!
[Verizon Samsung Galaxy Note II] Arikara:
I had 10.1 on my S3 loved it! I will wait!
[Verizon Samsung Galaxy Note II] jacob4duke:
Yea my friend has 10.1 on his s3 and i always need to play with it
[Verizon Samsung Galaxy Note II] Forge64:
No audio on Alpha3

Been lurking, no posts. I've previously been on an SGS2 with CM and quite happy. Got a Note 2 recently, had no problems unlocking, putting on a recovery, flashing this rom. However, I have no in-call audio. I can be heard, but I can't hear. I didn't see it in the notes, and my camera and GPS seem to be working fine, so I'm confused. Can anyone point me at where I've messed up? Thanks!

(I did see that CM 10.1 has a problem like mine, but I'm definitely on CM 10.0 Alpha3 from this thread)

Great work so far! I have hope that the Note2 will become more popular in the AOSP/AOKP world, since Verizon doesn't have a Nexus 4 coming.
[Verizon Samsung Galaxy Note II] sbergman27:
In-call audio problem

There is a known in-call audio quality problem which can happen sometimes. (Happened to me once. Static on the line.) A reboot is supposed to fix that. I guess that could be related. Does a reboot help?

-Steve
[Verizon Samsung Galaxy Note II] GTvert90:
How's data on this? I'm assuming there are ril issues like other aosp romed lte phones?
[Verizon Samsung Galaxy Note II] th0r615:
never had any problems since the thunderbolt with AOSP ROMs... my Galaxy Nexus was fine and the data on here has been fine.
[Verizon Samsung Galaxy Note II] GTvert90:
The nexus was different.
[Verizon Samsung Galaxy Note II] sbergman27:
No data problems here. Verizon sch-i605 (of course) in Oklahoma City using LTE 4G. Also 802.11n. Bluetooth works. But my streaming audio range is quite limited. It's unclear whether that is related to the ROM.

-Steve
[Verizon Samsung Galaxy Note II] sbrissen:
For those with gps issues can you try swapping the gps.conf in /system/etc with this one http://www.androidfilehost.com/?fid=9390275921635704923

Let me know the results.

Thanks
[Verizon Samsung Galaxy Note II] Ohh_Trenton:
As much as i want to try this theme so bad....the only thing holding me back is Spen controls. ;/ Grrr
[Verizon Samsung Galaxy Note II] sbergman27:
You mean this 'ROM'? S-pen hover functionality works. (I've tested in both stock browser and Chrome.) And S-pen gestures both work and are fully configurable in 'Settings'. (i.e. press the pen-button and gesture to bring up the note-taker, go back a page, etc.)

The only thing I miss is that feature where the phone screams if I walk off without the pen. Absent minded am I.

-Steve
[Verizon Samsung Galaxy Note II] Ohh_Trenton:
Haha yeah my bad, ROM. I have a massive headache & didn't thoroughly think before I typed this. So what about the screenshot with the s-pen?
[Verizon Samsung Galaxy Note II] gammaxgoblin:
It's the appropriate kernel built into this rom ....coming from stock with perseus?
[Verizon Samsung Galaxy Note II] sbergman27:
Screenshot is not a configurable target for S-pen gestures. However, in the settings menu for the Power Button Menu you can enable 'Screenshot'. That way you just long-press the power button and press 'Screenshot' to get a screenshot. It's a regular feature of CyanogenMod.

-Steve