yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] sublimaze:
High quality audio driver, playback ACG enabled (slight), and FIREqualizer enabled. There are so many options I have not even tried, but my music sounds perfect with just those 3 enabled.

That makes no sense. So you were doing fine until you flashed CM/AOKP? What recovery were you using? Is there any possibility you formatted or repartitioned something you weren't supposed to? Doing so is easier than you might think, especially with CWM's archaic UI. Use Philz Touch Recovery:

http://xdaforums.com/showthread.php?t=2552655
[Verizon Samsung Galaxy Note II] spiff72:
SlimKat was the first 4.4 based ROM that I tried (it did have signal), but I was having camera issues so I tried another 4.4 ROM (CM11 nightly) with no signal success. I think I ended up going with a 4.3 ROM just to check whether I had a working radio. I stuck with that one until this weekend, when I tried again with a 4.4 ROM. This is when my /data partition flaked out and I had to ODIN back to stock.

After re-unlocking and rooting with Casual and then ODIN-ing the 4.3 firmware last night I tried SlimKat, CM11 and AOKP. None of them had a working radio. (My test of the radio is to let it go through the first boot and I go through the initial setup without setting up google account, and check for signal. If there is none, I moved on to the next ROM). Then tried N3BULA and this one had working radio.

My typical routine when flashing ROMs is:

Wipe Data/Factory reset from CWM

Format /system

format /cache

wipe Dalvik

Flash ROM

Flash GAPPS (if needed)

(optional) wipe data/factory reset again after flashing ROM and gapps

I am using CWMR Touch (the latest version). I haven't tried or seen Philz before.
[Verizon Samsung Galaxy Note II] Mao04:
I had the same problem. The fix was:

Odin flash back to 4.1.x (make sure to flash pit file at same time).

Set up 4.1.x to make sure radio was working again.

Odin flash Bean's 4.3 firmware.

Wipe system, caches, data & data/media in recovery (I used Philz or CWM).

Flash Bean's stock 4.3 (I used deodexed) from the same thread as the firmware.

After this I had radio back and was able to flash any ROM and keep baseband.
[Verizon Samsung Galaxy Note II] sublimaze:
Those are exactly the same steps that I use to flash. Are you giving the new rom adequate time to find a cell signal? Sometimes it takes a little while to lock, especially on first boot. Are you in a fringe area? That could be compounding the problem.
[Verizon Samsung Galaxy Note II] neorecon:
I tried this v4a but can't enable it. It says to go to settings sound music control but I don't have that option. Even the DSP manager that is in the ROM seems to make no difference.
[Verizon Samsung Galaxy Note II] spiff72:
Hmmm...let me try to understand what I did differently...

When I recently Odin flashed back, I followed the directions here:

http://xdaforums.com/showthread.php?t=2040264

I chose the VRAMC3 version (the NON-alternate) so I was relocked when I was done. This only used the .pda file (no .pit file). What exactly is the PIT file doing? From a quick search it re-partitions the internal storage? One thing I should mention is that there appeared to be a different structure of partitions on my phone after I did the ODIN stuff yesterday. (Tombstones, and some other ones I didn't recognize.) They are gone now, though.

Other than the above, and the flashing of the Beans 4.3 ROM prior to the 4.4 ROMs, I basically did what you mention above.

Maybe I can try flashing Beans stock 4.3 now and trying a 4.4 again?
[Verizon Samsung Galaxy Note II] sublimaze:
If you download from the xda thread/V4A server, you must unzip it (you don't flash the zip in recovery). The V4A Play link is a regular app that installs like any other app. Whichever way you get it, after installing you will be prompted to install a special driver, and you have 3 choices. The Super High Quality is battery & CPU intensive. The High Quality is probably adequate for most users, especially if playing lossy MP3s. You must reboot after installing the driver. After rebooting, you may have to go to Settings > Sound and select V4A (instead of DSP Manager). Then open V4A from the app drawer and select your options. There are 3 main tabs: Headphone, Speaker and Bluetooth Device. Make sure you enable the main power toggle for the output(s), or you won't hear anything different.

The pit file is Partition Information Table. Anytime you go back to bone stock, you should flash the pit file during the process as well.
[Verizon Samsung Galaxy Note II] neorecon:
Okay maybe I'm draft but when I go into my settings and then sound I have no options to select v4a it DSP manager etc. I'm on slimkat 2.1
[Verizon Samsung Galaxy Note II] sublimaze:
Did you get prompted to install a special driver? Do you see V4A in the app drawer? Did you reboot after installing?
[Verizon Samsung Galaxy Note II] neorecon:
Yes to all the above. Is there a reason I have no options under sound to select? I don't even see a spot for DSP manager that came with the ROM.
[Verizon Samsung Galaxy Note II] sublimaze:
I forgot to mention that I had to install SuperSU from the Play Store in order for V4A to "take". The default superuser app that came with the ROM would not grant superuser to V4A. I do not have V4A or DSP options under Settings > Sound either, but I remember seeing those on another ROM. It doesn't matter. Once you install V4A + driver, grant superuser, and reboot, you should see V4A in the app drawer and go from there.
[Verizon Samsung Galaxy Note II] MHatter469:
For the Viper4Android, it installed fine, then asked to install drivers. I said to install drivers and it wants SU. Did you install SU also or is there a way to use the built in Superuser?

I downloaded from XDA not PlayStore.

Thanks.

Answered.
[Verizon Samsung Galaxy Note II] flyboy1100:
Thanks I tried the highest rated audio and my battery life sucks, was doing great with devil and devil tools. I will try high quality instead and see if my great battery life returns
[Verizon Samsung Galaxy Note II] Shamestick:
If you're still trying to get one, if you used Xposed framework and use the gravity box module you can use that to have a kill all received button
[Verizon Samsung Galaxy Note II] spiff72:
Well,

I tried flashing the Beans 4.3 ROM, letting it boot up (successfully verified radio functions), and then tried SlimKat. Sure enough - it worked! Radio function was verified, and I even flashed a CM nightly and got proper radio function.

So what is the deal here? Does the Beans stock 4.3 ROM install a different radio?
[Verizon Samsung Galaxy Note II] neorecon:
Supersu did the trick. Now it says it is enabled. Thanks!
[Verizon Samsung Galaxy Note II] sublimaze:
Beans ROMs do not touch the radio. It was probably corrupted by CWM when you flashed CM or AOKP. I have had similar issues with CWM, which is why I prefer TWRP. TWRP UI is light years beyond CWM too.
[Verizon Samsung Galaxy Note II] spiff72:
Hey now...I thought you recommended Philz recovery in your first reply to me! ;) I did switch to Philz BTW. I may have forgotten to mention that earlier.
[Verizon Samsung Galaxy Note II] sublimaze:
Ah...I assumed you were using CWM since gchild recommends that in OP. But I have flashed SlimKat via TWRP with no issues.
[Verizon Samsung Galaxy Note II] spiff72:
I was using CWM touch until earlier this morning after you recommended Philz. It seems to be based on the CWM version, but with tweaks. I suppose I might still get a corruption problem in the future, but for now it seems OK. Thanks for the help everyone!
[Verizon Samsung Galaxy Note II] Mao04:
Sorry I didn't answer your earlier??s. I was away.

Anyway, I'd say that Beans stock 4.3 probably has a Verizon file that AOSP 4.4 doesn't.
[Verizon Samsung Galaxy Note II] spiff72:
OK -

Another question here about this ROM...

I am trying to figure out if there is a setting I am missing somewhere that creates the following situation:

If the display times out, and i press the home button to wake the device back up, there is a slight delay, followed by a bit of haptic feedback, and then the screen comes up as if I had held down the home button to pull up the recent apps function. This only seems to happen if the home button is pressed within the "float time" between the display timing out and the device locking. If you wait long enough, it just goes to the lockscreen (as I would expect it to).

Does this happen for everyone?
[Verizon Samsung Galaxy Note II] sublimaze:
I confirmed this. It is indeed odd, and I don't recall seeing this on previous builds. Maybe you should report it to the slimroms team. But since the i605 is not officially supported, it may never get resolved...so don't hold your breath.

Edit: I tried to repeat this a few times, and I think it is the phone misinterpreting the tap as a "long" press, so it shows the recent apps. I couldn't make it happen consistently, so I am not convinced it is a rom bug.
[Verizon Samsung Galaxy Note II] Shamestick:
I have had the same thing happen to me a decent number of times, I'll try to replicate it
[Verizon Samsung Galaxy Note II] LexusBrian400:
This seemed wonderful, but it wouldn't locate my 64GB SD card. And yes it's formatted Fat32. Anyone else run in to this?
[Verizon Samsung Galaxy Note II] Mao04:
As others here have posted, GPS is not working for me while in "high accuracy". The phone finds my location, but only from WiFi and cell towers. GPS status shows 0 SATs. But as soon as I switch to "device only", I get GPS lock and GPS status shows 8 or more SATs. I have tried flashing a TW ROM then restoring and other fixes but still no go. I'm going to try comparing this to CM and other AOSP ROMs that I know are working to see if I can find missing files and such.
[Verizon Samsung Galaxy Note II] sublimaze:
That happened to me a few days ago when I was flipping ROMs. Backup everything you want onto desktop computer then use Philz Touch Recovery to partition the sdcard (Advanced > Partition /storage/sdcard1). You will be prompted for sizes, just use the largest.
[Verizon Samsung Galaxy Note II] sublimaze:
I have had no GPS issues on this ROM, but last night I was researching GPS variables and "tweaks". Some made sense, some didn't. This link was particularly interesting:

http://tinyurl.com/mecllzx

I compared the default SlimKat gps.conf with his and others, and made a couple of edits. I changed the NTP Server section to this (I deleted the "us.pool" lines entirely):

#North America

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

And I added this under AGPS server settings:

# FOR SUPL SUPPORT, set the following

SUPL_HOST=supl.google.com

SUPL_PORT=7276

I did not have GPS Status installed before the changes, but this is what GPS Status says after the changes:

This is with Google Location Setting on high accuracy, and only GPS enabled. Cell data and wifi were disabled.
[Verizon Samsung Galaxy Note II] flyboy1100:
]Without those edits and data disabled I can duplicate rise results and get a lock indoors in under 3 seconds.

The problem comes when you have data or wifi enabled, it won't ever get a lock because for some reason it seems to skip using the gps when a data/wifi signal is present.

In fact you can have data off, get a lock, reenable data and you will lose your lock and it doesn't seem to come back until data disabled
[Verizon Samsung Galaxy Note II] sublimaze:
This is with GPS, wifi and LTE enabled:
[Verizon Samsung Galaxy Note II] flyboy1100:
I will look into that this afternoon
[Verizon Samsung Galaxy Note II] Mao04:
What build and baseband are you on? I'm going to look at fused location.apk next. Clear data and cache, fix permissions, then try swapping it with CM's. Sounds like only some of us have a problem with something like corruption or a device specific issue.
[Verizon Samsung Galaxy Note II] sublimaze:
If anyone wants to test my gps.conf on their phone, pm me. Remember to make permissions rw-r--r-- and *backup* your existing gps.conf (do not delete it!)
[Verizon Samsung Galaxy Note II] drahpatel02:
Tried your configs... No success...
[Verizon Samsung Galaxy Note II] sublimaze:
Hmmm. Weird. The last time I saw so many people with GPS issues (including myself) was on the Samsung Captivate, but that was eventually determined to be a hardware fault. I hope Samsung didn't make the same mistake with the Note 2.

I suspect the problem stems from the fact that our phone is not officially supported by the devs. But it seems the GPS bug would affect everyone in this thread :confused:
[Verizon Samsung Galaxy Note II] drahpatel02:
I got GPS fix on Tw 4.3 rom, but never got on any 4.4 rom, may be cm11/aopk/slimkat.
[Verizon Samsung Galaxy Note II] sublimaze:
It still seems the bug should affect everyone with the same phone, but perhaps not. Different hardware revisions often use components from different manufacturers, and I am sure Samsung does not make every single component of their devices.

One thing that I forgot to mention earlier was the Extra Settings and LTE Positioning. I have read conflicting reports about these, so YMMV.

Open gps.conf, the bottom of the file will say:

# EXTRA SETTINGS

############################

# Enable or Disable Wiper (1=Enable, 0=Disable)

ENABLE_WIPER=0

# LTE Positioning Profile Settings

############################

# 0: Enable RRLP on LTE(Default) 1: Enable LPP_User_Plane on LTE

LPP_PROFILE=0

These supposedly affect GPS caching while other data connections are present. Change ENABLE_WIPER and LPP_PROFILE to 0 or 1, then see if you get GPS lock with wifi/cell data enabled.
[Verizon Samsung Galaxy Note II] pdinphx:
(see sublimaze already covered my solution ...)
[Verizon Samsung Galaxy Note II] DSinfinite:
Anyone get Xposed Framework to work on this ROM? I got it to work just fine on others but this time after I hit install soft and reboot it won't? Any help?
[Verizon Samsung Galaxy Note II] sublimaze:
Are you trying to use ART runtime? Xposed is not compatible with ART, but it should work with Dalvik.
[Verizon Samsung Galaxy Note II] Mao04:
One difference I noticed is that we are on different basebands, I'm on VRUEMJ9. I may try flashing back to vramc3 after I mess with the gps.conf and fused location.apk.
[Verizon Samsung Galaxy Note II] DSinfinite:
No running Dalvik?
[Verizon Samsung Galaxy Note II] sublimaze:
Did you give Xposed superuser privileges?
[Verizon Samsung Galaxy Note II] DSinfinite:
I get this after I hit reboot so it installs properly, blank on that says ok and after I hit ok it does nothing so it doesn't update etc
[Verizon Samsung Galaxy Note II] sublimaze:
Your installation is incomplete. Tap "Install/Update" (the top button) then reboot.
[Verizon Samsung Galaxy Note II] DSinfinite:
No that blank box is what I get after I hit install/update plus when I hot reboot AND soft reboot, the same blank box with an ok that doesn't do a thing
[Verizon Samsung Galaxy Note II] sublimaze:
Redownload Xposed. Reboot into recovery and wipe cache & dalvik, reboot phone, and reinstall Xposed
[Verizon Samsung Galaxy Note II] DSinfinite:
Are some modules not compatible?
[Verizon Samsung Galaxy Note II] sublimaze:
Correct. Some modules are not compatible with 4.4.x roms
[Verizon Samsung Galaxy Note II] gchild320:
Just an fyi, no eta on the next release. Shouldn't be too long. I figured out data while on a call, however I broke something else in the process. Also, slim merged something to auto detect network that is giving me problems. So keep in mind I'm working on it!
[Verizon Samsung Galaxy Note II] spiff72:
Thanks for the update gchild320...

Just curious whether you had any thoughts about this possible bug...

http://xdaforums.com/showthread.php?p=49594066

It is a relatively minor one in the grand scheme of things, but a mild annoyance nonetheless...

Great work on supporting this ROM for the GN2!

Sent from my Galaxy Note II - please pardon the typos...
[Verizon Samsung Galaxy Note II] sublimaze:
You could add a wakelock to see if that helps:

http://xdaforums.com/showthread.php?t=2208267

If you don't want to edit smali, this app may work:

https://play.google.com/store/apps/details?id=eu.thedarken.wl
[Verizon Samsung Galaxy Note II] gchild320:
I don't know that I'd call it a bug...you're likely catching your device when it's going into a deep sleep...and your device is registering it as a long press...hence the haptic feedback and recents menu opening.
[Verizon Samsung Galaxy Note II] flyboy1100:
I might of missed it, but WiFi tether doesn't work?
[Verizon Samsung Galaxy Note II] sublimaze:
Are you talking about portable WiFi hotspot? That works fine, I used it yesterday.

I have not tested USB or BT tethering.
[Verizon Samsung Galaxy Note II] flyboy1100:
I just tried it and it won't stay on. Might be because I'm in the plane, and data connection isn't the most stable? It turns off within 3 seconds of trying to turn it on
[Verizon Samsung Galaxy Note II] sublimaze:
I just tested it, it works. Try it again when you get off the plane.
[Verizon Samsung Galaxy Note II] neorecon:
Any idea why non invasive call notification was removed and are you able to add it back to our unofficial version? I loved that feature.
[Verizon Samsung Galaxy Note II] flyboy1100:
nope, won't start, just immediately turns back off.

when the new version is released I will try a fresh install
[Verizon Samsung Galaxy Note II] sublimaze:
David Sanchez posted in slimroms G+ community thread: " The non-intrusive call screen was removed because it was broken. Use the incoming call in background option instead."
[Verizon Samsung Galaxy Note II] flyboy1100:
Worked fine on my end. Oh well
[Verizon Samsung Galaxy Note II] sublimaze:
It worked for me too, and I liked the feature. It probably didn't work on some "official" devices, so the devs nuked it in favor of a more stable development tree.

Ask the devs if they plan to offer it again in a future release. If enough people want it, they probably will :fingers-crossed:
[Verizon Samsung Galaxy Note II] travisn000:
If you want to build your own, gchild has his i605 stuff on github: https://github.com/gchild320 ..IIRC you just have to add his i605 directory to a slimkat t0lte git sync, and also add the i605 device to the vendorsetup.sh file.

It's probably a good idea to wait a few days though, as he mentioned earlier today he is working on squashing a few bugs for the next release.
[Verizon Samsung Galaxy Note II] flyboy1100:
New update, my WiFi doesn't work either. It was working this morning. Argh
[Verizon Samsung Galaxy Note II] gchild320:
That's a good start, however you'll also need to add t0ltecdma to samsung vendors. On top of that, I've made some updates to the device tree since then, but they're pretty minor based on what has been removed from Slim trees...ie torch settings.
[Verizon Samsung Galaxy Note II] sublimaze:
Your WiFi tether worked this morning but it doesn't work now? Have you installed any new mods? Do you have a rom backup that has working WiFi tether?
[Verizon Samsung Galaxy Note II] akellar:
Wouldn't they need to update your device tree for 4.4? The dependencies all point to 4.3.
[Verizon Samsung Galaxy Note II] gchild320:
No my i605 tree for slim is 4.4, the branch is "master." Most all the other things (including t0lte folders) on my github are forks for building 4.8+ GCC with -O3 flags, and that was for 4.3.

To use my stuff (which I proudly take little credit for, mostly CM and Slim work) to build your own slim versions, just lunch t0lte in your slim folder, then clone in t0ltecdma into vendor/samsung, and copy my i605 tree into device/samsung. I uploaded my device tree pretty lazily, otherwise I'd say clone it in too...you'd have to move it around once you cloned it, or just download the zip and place it appropriately.
[Verizon Samsung Galaxy Note II] flyboy1100:
Not my tether, my actual WiFi isn't working either. I should have a backup from last week.

Nothing new installed, so I don't understand why either would have quit. Tether probably worked before too since the problem is falling on actual wifi

Edit: tether and wifi work on my backup
[Verizon Samsung Galaxy Note II] flyboy1100:
Just tried to modify my GPS.conf and GPS still only works when network location stuff or data is turned off.

Edit: changed the lte location setting in gps.conf from 0 to 1 (pretty much disabled it if i understand it).

I was playing with this on my flight tonight, everytime I had lte it wouldn't lock, but with 3g/1x/no data it would lock instantly. This is what made me think to change that setting. I will post it when I get home

Almost instant lock now in high accuracy mode.
[Verizon Samsung Galaxy Note II] flyboy1100:
#North America
NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 4

# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0

# supl version 1.0
SUPL_VER=0x10000

# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0

# GPS Capabilities bit mask
# SCHEDULING = 1
# MSB = 2
# MSA = 4
# ULP = 0x20
# ON_DEMAND_TIME = 0x10 // yunu.lee
# default = MSA | MSB | SCHEDULING | ULP
CAPABILITIES=0x16

# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000

################################
##### AGPS server settings #####
################################

# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276

################################
# Sensor Settings
################################

# Needs to be set explicitly based on sensor
# There is no default value.
GYRO_BIAS_RANDOM_WALK=0.00001

# Sensor Sampling Rate Parameters for Low-Data Rate Filter (should be greater than 0)
SENSOR_ACCEL_BATCHES_PER_SEC=3
SENSOR_ACCEL_SAMPLES_PER_BATCH=5
SENSOR_GYRO_BATCHES_PER_SEC=3
SENSOR_GYRO_SAMPLES_PER_BATCH=5
# Sensor Sampling Rate Parameters for High-Data Rate Filter (should be greater than 0)
SENSOR_ACCEL_BATCHES_PER_SEC_HIGH=4
SENSOR_ACCEL_SAMPLES_PER_BATCH_HIGH=25
SENSOR_GYRO_BATCHES_PER_SEC_HIGH=4
SENSOR_GYRO_SAMPLES_PER_BATCH_HIGH=25

# INS Filter Mode (0=Enable, 1=Disable)
SENSOR_ALGORITHM_CONFIG_MASK=1

# Sensor Control Mode (0=AUTO, 1=FORCE_ON)
SENSOR_CONTROL_MODE=0

# Enable or Disable Sensors for GPS use (0=Enable, 1=Disable)
SENSOR_USAGE=0

# Choose GSIFF sensor provider (1=DSPS, 2=Android NDK)
SENSOR_PROVIDER=2

################################
# Indoor Positioning Settings
################################
# 0: QUIPC disabled, 1: QUIPC enabled, 2: forced QUIPC only
QUIPC_ENABLED = 0

################################
# EXTRA SETTINGS
################################
# Enable or Disable Wiper (1=Enable, 0=Disable)
ENABLE_WIPER=0
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1

####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default) 1: Enable LPP_User_Plane on LTE
LPP_PROFILE = 1

Maps and coilot get instant lock with this setup
[Verizon Samsung Galaxy Note II] gchild320:
OK guys I have figured out my problems and fingers crossed will have 2.4 upped tomorrow.
[Verizon Samsung Galaxy Note II] sublimaze:
Awesome :cool:

Put backups of that file on your sdcard, Dropbox, desktop/laptop, and everywhere else you can think of.
[Verizon Samsung Galaxy Note II] gchild320:
A few quick notes on beta 2.4.

Voice + Data simultaneously is working.

Any connectivity issues should be resolved.

Advanced reboot has been moved to "security."
[Verizon Samsung Galaxy Note II] sublimaze:
Thanks for fixing the connectivity issues. That has been a sticking point for many people.
[Verizon Samsung Galaxy Note II] flyboy1100:
Worked beautifully this morning while using gps to stay on road in zero visibility!

---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------

Must still be uploading?

Thanks!
[Verizon Samsung Galaxy Note II] drahpatel02:
Great.... You rocks.. Waiting for 2.4..