yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] zmore:
Volume ramp bug fixed

Woohoo! Tomorrow's nightly (0205) will finally fix the most annoying bug (IMO) present since the 1st cm12 nightly! -- audioflinger: Fix glitches and volume ramp issue -- Can finally stop having to toggle the volume up & down to temporarily reset the volume to normal.

Thanks Steve!
[Galaxy Note 3 Android Development] zadigre:
I can confirm it's working fine...

my brother has a S5 (klte)... and the klte CM12 build has this fix... no more volume problem...
[Galaxy Note 3 Android Development] zadigre:
answering to myself...

a2dp bluetooth is not fixed for me... I tried it this morning with Google Play Music and a streaming radio app... I can hear a few notes... but that's it. My radio app even crashed... something that never happened with CM11 or stock rom.

http://review.cyanogenmod.org/#/c/87818/

there's some talk regarding audio_policy.conf... maybe our file is missing something?
[Galaxy Note 3 Android Development] burticus:
How is the latest working for everyone?

For me everything seems to be in good working order. Preliminary of Battery Life seems bad though, but still gotta give it a bit more time for the ROM to settle in.

All in all great work dev :)
[Galaxy Note 3 Android Development] zmore:
Volume ramp is fixed, but yeah, a2dp bluetooth still won't reconnect sometimes until a reboot here as well. I can sometimes reconnect and hear 1 second of audio before "Bluetooth Share" crashes, but that's it. Have to reboot before BT works again.
[Galaxy Note 3 Android Development] burticus:
hey guys,

I have just tried to reboot to recovery and I get the boot animation for recovery and then a black screen and then my phone restarts and then it tries to boot recovery again with no luck. this process repeats indefinitely.

any recommendations?

should I re-flash recovery with odin or is there another fix?

I have been trying all day just restarting, battery pulling etc. kinda at my wits end :(

all i wanna do is flash the latest rom. never had this issue before.

ok cancel my last bat signal i just re-flashed recovery with odin and solved the problem, I just didn't wanna **** anything up so I came here first.

but then my lack of patience took over and I just went for it hahaha.

thanks anyway guys
[Galaxy Note 3 Android Development] BillGoss:
Yes, flash your recovery again using Odin.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Rocket Nine:
Anyone else having an issue of cell radio dropping out, giving no signal in places which you know should be fairly decent? Toggling airplane mode seems to fix it. I'm running the latest nightlies and have been experiencing this for a while. I have yet to have a dropped call, though, so it doesn't seem to go out while in use.
[Galaxy Note 3 Android Development] zmore:
Happened to me for the first time today, actually. Lost connectivity with both WiFi and LTE having the little exclamation point in their notification icons. Toggling Airplane mode fixed it.
[Galaxy Note 3 Android Development] arakito:
Hi,, I'm having an issue with the speaker of my note. When I listen to music or a one specific modifications sound I get a distorted version of the sound. I found a fix for this days ago but I erased the file and I can't find it anymore. Can anybody help me?
[Galaxy Note 3 Android Development] Grantius:
Did you try new modem?
[Galaxy Note 3 Android Development] zmore:
Flashed the newest sm-n900t firmware (NK3) before CM12 was released in early January, so it's not that. Was probably just a coincidence on that nightly, since I haven't had data problems since.
[Galaxy Note 3 Android Development] dusselwussel:
Hi there, having problems with the following. Address book is working normal, but the names of my contacts are not shown when dialling, reading SMS as sender information and in call log. Just see the numbers. But in fact, those numbers can be found in the address book.

Key facts: syncing with Google, but changed from self hosted address book and calendar sync back to Google. Worked before getting back, but now with Google only, behaviour as described. Already deleted the Google account on the phone and reinstalled, but did not work. I am on nightly 20150215 cm12 with hlte.

Any ideas except reinstalling everything?

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] bolderbasta:
So. By reading the thread, I believe I'm not the only one having problems with A2DP audio streaming to my car's stereo. (besides that, I LOVE CM12!)

My issue is that I have about 1 sec of audio and then nothing. Even the player (tried a few) just pauses/freezes. Eventually Bluetooth Share crashes and I have to reboot the phone to get bluetooth working again. This happens with every nightly version (including the latest one) I've tried. My device is HLTE.

I found that flashing Leankernel or Temasek's kernel solves the problem. But ofcourse it would be best to find and fix the problem in stock CM12 aswell.

Anyone willing to dive into this? [MENTION=2457777]slayher[/MENTION] or [MENTION=3632743]christer12[/MENTION] maybe?

I'm willing and able to perform tests and provide logs! (just tell me which ones you want)
[Galaxy Note 3 Android Development] zadigre:
this problem is also affecting other devices like the S5 (my brother has one... and same problem). It's the bluetooth stack dealing with a2dp that has a problem...

that said, there's also an other excellent kernel working on CM12... made from Samsung sources + a few modifications... not based on CM like most kernel.

http://xdaforums.com/galaxy-note-3/development/arter97-kernel-galaxy-note-3-t3028148

running great. fluid. stable. excellent battery... and a2dp is working fine.
[Galaxy Note 3 Android Development] Bobanovicz:
In the latest nightly when I receive a call, the proximity sensor works before I answer. Is there any option to turn off this feature?

And AudioFX doesn't work. Turn on and turn off do nothing.
[Galaxy Note 3 Android Development] Alexis46:
Hey guys, I just wanted to ask, how is the battery life for you? I think it is not as good as on stock! But I know from my earlier experience in CM that it has pretty good batterry life.. SOmetimes better than stock Roms! Is battery life good for you?

Sorry if this question was asked before but I couldnt read all 280 pages here :D:D:D

Have a good day! :)
[Galaxy Note 3 Android Development] Grantius:
I flashed CM11 the day I got the phone, but as far as I know it's worse than stock.

I use a Zerolemon battery though, so I get about 16 hours screen on time anyway :)
[Galaxy Note 3 Android Development] zadigre:
battery is worst than stock most of the time...

but if you install a custom kernel (ex http://xdaforums.com/galaxy-note-3/development/arter97-kernel-galaxy-note-3-t3028148), you are likely to get battery like as good or better than stock.
[Galaxy Note 3 Android Development] xavihernandez:
Well it really depends on your use.

But I think the common screen on time on Lollipop AOSP ROMs is ~6 hours (some get more, some get less, but it is the average stat I read around)

On TouchWiz ROMs (custom ones I assume), it seems to be approximatively the same Screen on time (~6 hours). But I have already seen around people with 10h+ Screen on time on custom TouchWiz. It is not most of people though.
[Galaxy Note 3 Android Development] Alexis46:
Just flashed the arter97 kernel and am gonna check the battery life!
[Galaxy Note 3 Android Development] xavihernandez:
I have flashed it yesterday, so far so good. Still have to play with it to have better feedback.
[Galaxy Note 3 Android Development] bolderbasta:
Well, coincidence? I noticed that the last 2 nightlies have a couple of bluetooth fixes. Flashed the latest and guess what: been using A2DP for a few hours now without issue! :)
[Galaxy Note 3 Android Development] dusselwussel:
No ideas?

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] zmore:
[IMG="Nuke it from orbit. It's the only way to be sure."]http://clearcrypt.org/img/ripley.jpg[/IMG]
[Galaxy Note 3 Android Development] dusselwussel:
You mean clean install?
[Galaxy Note 3 Android Development] arakito:
I try to update to the last build and I get this

Does anyone has any slight idea?
[Galaxy Note 3 Android Development] zadigre:
You need to download/install the hltetmo build and not the HLTE
[Galaxy Note 3 Android Development] zadigre:
Hello Everyone,

how do we un-pin a screen/app that has been pinned?

when an app is pinned, if I press one of the button, it says to hold back and overview buttons to un-pin. I've tried all combinations and nothing works... the only thing that works is a reboo. Anyone has been successful using this feature?
[Galaxy Note 3 Android Development] BillGoss:
It works if you have the on-screen navigation keys enabled. I guess it doesn't work on the hardware navigation keys yet.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] PlutoDelic:
Any snapshot nearby?
[Galaxy Note 3 Android Development] istperson:
Messaging crashes

Messaging crashes if I select a message thread or tap the new message button:

com.android.mms.ui.ComposeMessageActivity}: java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
02-23 14:46:12.235 E/AndroidRuntime(21158):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1296)
02-23 14:46:12.235 E/AndroidRuntime(21158):	at android.os.Handler.dispatchMessage(Handler.java:102)
02-23 14:46:12.235 E/AndroidRuntime(21158):	at com.android.mms.ui.ComposeMessageActivity.onCreate(ComposeMessageActivity.java:2007)

It's been modified a lot latelly. I've built it synced to this change id:

http://review.cyanogenmod.org/#q,I59c9938ed90a1597395e3c77a26741ef4e44c822,n,z
[Galaxy Note 3 Android Development] dusselwussel:
Just wanted to clean install the latest nightly, but i cant boot into cwm .. Only get a black screen. Pressing the home button just restarts normally. HELP. Recovery seems to be broken by the latest nightly.

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] BillGoss:
Flash recovery again using Odin.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] navdra:
Llama - Location Profiles app is force closing in last few CM12 builds (20150219 is last 'good' one).

So, something in cm-12-20150220-NIGHTLY-hlte changes must have broke it:

cm-12-20150220-NIGHTLY-hlte.zip

Don't enable ADB by default on userdebug builds (android_build)

Settings: fix Vibrate on touch preference not working (android_packages_apps_Settings)

Add back lift to wake preference (android_packages_apps_Settings)

SetupWizard: Pass accent color to CaptivePortalLogin (android_packages_apps_SetupWizard)

CaptivePortalLogin: Allow overriding of progress color (android_frameworks_base)

Fix comment block in Settings declaration, breaks checkapi (android_frameworks_base)

SetupWizard: Add captive portal check (android_packages_apps_SetupWizard)

CaptivePortalLogin: Add functionality for SetupWizard (android_frameworks_base)

Settings: properly remove voicewakeup preference (android_packages_apps_Settings)

Properly remove NFC payment preference (android_packages_apps_Settings)

Fix Profiles settings screen padding (android_packages_apps_Settings)

Per conversation notification settings/ringtones (android_packages_apps_Mms-caf)

Mms: Port custom notification vibrations (android_packages_apps_Mms-caf)

Enable Buttons and Status Bar settings Multi-user enabled (android_frameworks_base)

Add MultiUser support for additional Settings (android_packages_apps_Settings)

Any ideas?
[Galaxy Note 3 Android Development] dusselwussel:
Reflashed TWRP. Works. Heimdall does not work for me, but Odin does.

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] BillGoss:
Llama works ok for me on 0221.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] navdra:
I'm trying every new build since 0219 and with every one Llama force closes when it tries to change profile (or I try to change it manually).

I also found someone mentioning the same problem here:

http://xdaforums.com/showpost.php?p=58985449&postcount=2082

:confused:
[Galaxy Note 3 Android Development] BillGoss:
After replying to you, Llama started to FC and restart over and over again (on 0221). I then switched to Temasek's v7.9 and Llama did the same thing there as well.

So, yes, there's something odd going on with the latest CM12 and Llama.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] istperson:
0221 started to FC when I select a thread in messaging or I want to write anew one. Anyone else? I might want to try to delete all application data for the App.
[Galaxy Note 3 Android Development] prusiu:
it works for me
[Galaxy Note 3 Android Development] istperson:
Well, I backed up the data, cleared all data and cache, and it started working again. Restored the data, and it FC-s again. So I cleared it again. Unfortunately I lost my templates, and there's no way to save and restore them :(
[Galaxy Note 3 Android Development] BillGoss:
See this post and the one quoted in it for solution. http://xdaforums.com/showthread.php?p=59085374

Sent from my SM-N9005
[Galaxy Note 3 Android Development] wilfredlams:
Just wondering, anyone had the problem of /storage/sdcard0/ not mounted? Instead I need to go to /storage/emulated/0/ to access my internal storage. Thanks.
[Galaxy Note 3 Android Development] navdra:
This looks like a solution to me:

http://review.cyanogenmod.org/#/c/89922/

Settings: Don't attempt to forward writes from System -> Secure.

This breaks 3rd party apps since they can't get access to

WRITE_SECURE_SETTINGS.

It's merged and will be included in next nightly.
[Galaxy Note 3 Android Development] btvolta:
I tried out today's build but couldn't find where to enable navigation bar so I restored temasek.

Sent from my SM-N900T using Xparent BlueTapatalk 2
[Galaxy Note 3 Android Development] BillGoss:
All you have to do is add this to /system/build.prop and reboot.

# enable soft navigation keys

qemu.hw.mainkeys=0

Sent from my SM-N9005
[Galaxy Note 3 Android Development] btvolta:
Yeah I've done that before and didn't think of it. Thanks

Sent from my SM-N900T using Xparent BlueTapatalk 2
[Galaxy Note 3 Android Development] dbanzon:
Hey guys im still using cm11 snapshot version and Im planning on moving on to cm12. Can you suggest which is the most stable cm12 nightly for daily use?
[Galaxy Note 3 Android Development] Grantius:
I'm using the latest with no issue, you should be able to dirty flash it over your CM11.

Afterwards, I recommend using Cyandelta for updates as they will be in the 20mb range rather than 300mb
[Galaxy Note 3 Android Development] Gandicela:
Under Settings/Buttons, any Backlight changes isn't working. Especially disabling backlight, it remains under 5 seconds. It's true for both, 27 & 28 Feb nightly.
[Galaxy Note 3 Android Development] istperson:
I've just built the cm12, and the Settings/Sounds/Vibrator intensity crashes with

03-07 11:58:25.863 W/PackageManager(1957): Failure retrieving resources for com.android.settings: Resource ID #0x0

Last Change-Id: http://review.cyanogenmod.org/#q,I5f92e15de4aabde732e7cb89fd02432f32e8f329,n,z
[Galaxy Note 3 Android Development] Schrotty35:
Work cm12 with latest lollipop bootloader or need kitkat boodloader?
[Galaxy Note 3 Android Development] Ooo_Pepi:
I tested it with lp bootloader and works fine, with kitkat bootloader works fine too.

I tested it with lollipop bootloader and CM11, it works fine too.
[Galaxy Note 3 Android Development] Super-Veloce:
Do you think CM12 based on Android 5.1 will come soon?
[Galaxy Note 3 Android Development] BillGoss:
Yes.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Bobanovicz:
Is it the behaviour, when proximity senzor works BEFORE pick-up the call, a feature? Or it's only my issue?

Anybody with the same experience please?
[Galaxy Note 3 Android Development] BillGoss:
I'd say it's only your issue.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Bobanovicz:
Really? This is the same after the hard reset.
[Galaxy Note 3 Android Development] Grantius:
Anyone know when we'll see the official 12.1 release? I'm on temaseks build but I'd like to see if mainline fixes an issue I have
[Galaxy Note 3 Android Development] celderic:
Everything seems to work okay with the latest official cm12 builds, after a full wipe the settings app always force closes a few times during the initial setup screen. Does anybody know why?
[Galaxy Note 3 Android Development] Journyman16:
[MENTION=225651]op[/MENTION] - you might want to edit the PA-GApss link in the 1st post. The original is closed but it is now being maintained at http://xdaforums.com/android/software/reborn-gapps-5-t3074660
[Galaxy Note 3 Android Development] ps000000:
I hope the MX Player fix the issue in CM12.1 ROM soon. :good::good::good:
[Galaxy Note 3 Android Development] celderic:
What issue?
[Galaxy Note 3 Android Development] Faiz Malkani:
Keep it civil, gents. Next time will be more than just a thread clean
[Galaxy Note 3 Android Development] ps000000:
Edited.
[Galaxy Note 3 Android Development] zeko.elgohary:
i like it

Thanks man but i havr 2 questions and the first may be stupid question :D

1-What is the meaning of nightlies sorry but really I don't understand what is the Nightlies

2-what about the battery life :)

Thanks man again and sorry if my English not good enough :)
[Galaxy Note 3 Android Development] BillGoss:
1. Google would have pointed you to this: http://www.cyanogenmod.org/about

2. It varies depending on individual usage. Generally ok, but better with arter97's kernel.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] anarchy2cruo:
Will this proper to ask this here. If not just clean it up.

I read there is fix for notification and ringtone volume link in 15april updates. However the issue still there. The ringtone and notification couldn't unlink still. Is there anything I missed? Was it fixed for u guys?
[Galaxy Note 3 Android Development] AndyYan:
Surprised to see no one asking about this at all... CM12.1 builds have rolled out in batches during the past few days, but the regular hlte isn't included in the batch (while hltespr and hltetmo are). I checked Jenkins on the day CM12.1 started rolling out, and cm_hlte-userdebug is marked as "broken since 2015-04-17" or something like that - it failed to build. What's stopping it from being built/released, and can we expect something?
[Galaxy Note 3 Android Development] celderic:
The latest 16th build is working very well for me. Here is the only bug i have found that is worth mentioning, in the music app.

Sometimes the album cover gets hidden behind this.

Instead of looking like this.
[Galaxy Note 3 Android Development] jisoo:
The device repo for hlte has not been updated to 12.1 so far. I'm not aware of any other breakage, as it builds and runs fine if you just update the branch and build yourself.

Maybe the device maintainer has been busy with other stuff?
[Galaxy Note 3 Android Development] dusselwussel:
Wondering, too. Looking forward to the next nightly..

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] DeadPicsel:
I was wondering why there hasn't been any nightlies for cm 12.1. There shouldn't be a problem with the build as Temasek has managed to build latest nightlies.
[Galaxy Note 3 Android Development] Grantius:
there is for the other Note 3 variants
[Galaxy Note 3 Android Development] DeadPicsel:
Well I don't mind building unofficial nightlies for hlte, if people want them
[Galaxy Note 3 Android Development] dusselwussel:
May hlte will no longer be supported?

Sent from my CM12 hlte
[Galaxy Note 3 Android Development] BillGoss:
I decided to try cm-12.1-20150422-NIGHTLY-hltetmo on my N9005 just to see what happens. I haven't found anything wrong or broken so far.

The only change I had to make was to remove the assert statement from the install script.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Santa-Claus_16:
I confirm!

In updater-script change the first line to the:

assert(getprop("ro.product.device") == "hltexx" || getprop("ro.build.product") == "hltexx" || getprop("ro.product.device") == "SM-N9005" || getprop("ro.build.product") == "SM-N9005" || getprop("ro.product.device") == "hlte" || getprop("ro.build.product") == "hlte" || getprop("ro.product.device") == "hlteskt" || getprop("ro.build.product") == "hlteskt" || getprop("ro.product.device") == "hltektt" || getprop("ro.build.product") == "hltektt" || getprop("ro.product.device") == "SM-N900S" || getprop("ro.build.product") == "SM-N900S" || getprop("ro.product.device") == "SM-N900K" || getprop("ro.build.product") == "SM-N900K" || abort("This package is for device: hltexx,SM-N9005,hlte,hlteskt,hltektt,SM-N900S,SM-N900K; this device is " + getprop("ro.product.device") + "."););
[Galaxy Note 3 Android Development] andrew.mackew:
Thanks! I will try that.

But I wonder what the heck HLTE has no more updates? Could please someone start to build unofficial until everything gets on the rails again?
[Galaxy Note 3 Android Development] BillGoss:
Didn't you read post #2862?

Sent from my SM-N9005
[Galaxy Note 3 Android Development] andrew.mackew:
Yes I did. He said he don't mind.. but didn't post a new thread so far.

Just say something doesn't mean too much until you get something solid. Just my 2 cents..

But [MENTION=5073087]bu44er[/MENTION] it'll be very welcomed for sure!
[Galaxy Note 3 Android Development] prusiu:
Branch cm12.1 was created two hours ago for hlte.
[Galaxy Note 3 Android Development] Santa-Claus_16:
Now a couple of million years and will go nightly builds...
[Galaxy Note 3 Android Development] istperson:
I'll try to build it tonight.
[Galaxy Note 3 Android Development] negativman:
What is the reason for the delay? How long to wait? Who knows?
[Galaxy Note 3 Android Development] prusiu:
The next nigthly should be for hlte...
[Galaxy Note 3 Android Development] negativman:
In what sense? There is some precedence?
[Galaxy Note 3 Android Development] prusiu:
Branch was created so nigthly can start now. I hope that this will be.
[Galaxy Note 3 Android Development] hene193:
Since no one else is saying this. Instead they are just complaining....

Thank you sir. And thanks for the maintainer.
[Galaxy Note 3 Android Development] istperson:
No luck yet, the sync has stalled constantly, a lot of people must have been trying to build it. Maybe tomorrow...
[Galaxy Note 3 Android Development] BillGoss:
Hlte CM12.1 is up! ?

Sent from my SM-N9005
[Galaxy Note 3 Android Development] AndyYan:
Comfirmed, without a bang.

http://download.cyanogenmod.org/?device=hlte

http://download.cyanogenmod.org/get/jenkins/108329/cm-12.1-20150426-NIGHTLY-hlte.zip

In other news, I've been trying to build on my own according to the official CM guide (only modified the branch to cm-12.1) but keeps bumping into this mysterious error:

$ breakfast hlte
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/qcom-common/qcom-common.mk" does not exist. Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-12.1
Checking branch info
CyanogenMod/android_device_samsung_hlte already exists
Syncing repository to retrieve project.
fatal: duplicate path device/qcom/common in /home/crossgate/cm-build/.repo/manifest.xml
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/hlte/cm.mk]]: "device/samsung/qcom-common/qcom-common.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?

And after that, any "repo sync" action will also return:

$ repo sync
fatal: duplicate path device/qcom/common in /home/crossgate/cm-build/.repo/manifest.xml

If I delete .repo/local_manifests/roomservice.xml, repo sync will go normally, but to build I have to do "breakfast hlte", which will generate roomservice.xml and subsequently give me these errors again. Anyone know what to do?
[Galaxy Note 3 Android Development] Schrotty35:
How run the new CM12.1, any errors, all working?