yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] nitrous²:
I'm using official CM 12.1 nightly's again after I decided to quit using custom ROM's for a while. Anyway. I thought the distorted/crackling sound issue was fixed? It's still there, the same since CM12 first appeared on the Note 3. Start audio playback with touch/lock sounds activated and press random items in OS.

Update:

The audio_policy flashable zip below contains the audio_policy file from latest official stock TW ROM and solves the crackling issues. I've replaced the audio_policy file in the .zip [MENTION=5326034]tyre777[/MENTION] had created with the latest one from BOD6 FW. So thanks to him. However if you use his version, you might get cut off notification sounds. With the latest audio_policy file I've attached below, that doesn't happen anymore.
[Galaxy Note 3 Android Development] fefuzzo:
I have a problem: i can't use stock e-mail app with exchange account because the exchange app force close and i can't sync email...any fix??
[Galaxy Note 3 Android Development] celderic:
Could you upload the latest audio_policy file from cm12.1 please?

So i can compare it with the one you posted, to figure out what is causing this problem.
[Galaxy Note 3 Android Development] bjanha:
Is there ANY 5.1.1 roms not based on CM? I really need emergency call to work. I feels a little ridiculous claiming that "my smartphone cannot dial emergency numbers" if something happens to my kids. I tried CM (obviously), Tema, Slim, Euphoria with no luck.
[Galaxy Note 3 Android Development] Pehpe:
Try Broken 2.3 by [MENTION=2734070]encho[/MENTION], based on AOSP. And please give a short feedback if it works.

http://xdaforums.com/galaxy-note-3/development/rom-broken-os-t3055479
[Galaxy Note 3 Android Development] zmore:
Awww... I was expecting more flashaholics to be raving about how fast the "Android is Upgrading..." bootup optimization stage is now in 0227 (and going forward) now that it uses all 4 (or more) cpu cores instead of just the 1 thread since the inception of CM. Ziiiiippy.

This'll save me ~18+ hours per year in bootup time that I no longer have to spend doing other boring things IRL. (~3mins shaved off 300 apks on Note3 * 365 nightlies / 60).

:highfive: CM
[Galaxy Note 3 Android Development] gakio12:
I finally got CM to compile; I LOVE that optimization stage now. It was already on 18 of 236 by the time it appeared on screen :D
[Galaxy Note 3 Android Development] LillieBennett:
Happens to me as well but no matter which rom. Power off, plug in charger and it boots. Unplug charger and screen wakes. Seen it with other phones too.

SM-N900V DE
[Galaxy Note 3 Android Development] testmonkey1:
Anyone?
[Galaxy Note 3 Android Development] jamesmuking5:
Anybody having very bad crackling sound with the speaker when playing any kind of sounds?
[Galaxy Note 3 Android Development] thools60:
Yep. Me to. Especially speaker phone.
[Galaxy Note 3 Android Development] PeterGuru:
Bad crackling sounds here, too ...

Same here ... especially though the speakers when the volume is high.

Peter
[Galaxy Note 3 Android Development] Streykatorato:
I have 4.3 bootloader. if i flash this rom.. will i be able to go back to 4.3 stock then? When kitkat official arrives for my note 3. could i restore my 4.3 backup? If im on samsung kk rom i cant downgrade to 4.3 but if im on stock 4.3 and upgrade to cm11.. can i downgrade to 4.3 again?.. read between the lines.. im tired.. :P
[Galaxy Note 3 Android Development] Sandzak385:
NO YOU CAN NOT DOWNGRADE
[Galaxy Note 3 Android Development] donatien97:
But the strange thing is that this didn't happen with the HTLETMO T-Mobile build from 1/30. It seems to happen with the newer HTLE builds as well as with other ROMs that I suspect are built off these newer builds (Temasek & SlimKat).

I love CM as a ROM and I'm using it as my daily, but I like to be able to turn the phone off and charge it.

Can anyone recommend how I can submit this issue as a bug?

Thanks!
[Galaxy Note 3 Android Development] sauron82:
Turn off touch sounds.

Click thanks if I helped you.
[Galaxy Note 3 Android Development] PeterGuru:
Touch sounds ARE already off ...

Thank you for this suggestion; however, it's not the problem. I have always had Touch Sounds off, yet I'm NOW getting the crackling noise, which did not exist with earlier builds.

Peter
[Galaxy Note 3 Android Development] gakio12:
If you flash CM11 from a 4.3 touchwiz install, YES, you can go back to stock 4.3. Once you install the 4.4.2 TouchWiz OTA, NO, you cannot go back to 4.3. CM11 DOES NOT install the 4.4.2 bootloader. In fact, if you want to keep your 4.3 bootloader but still get the 4.4.2 touchwiz, you can flash a custom ROM of touchwiz, most of them have the bootloader taken out.
[Galaxy Note 3 Android Development] PeterGuru:
BSOD Fixed?

Has anyone determined yet if the Black Screen Of Death is still present with CM20140228? I'm currently using Tamesek's kernel, which doesn't appear to cause this problem; however, I'd prefer to keep everything CM, including the kernel.

The only other issue I'm having at the moment is crackling noise through the speakers at full volume. Yes, in case some of you are wondering, I'm quite aware of the "disable Touch Sounds" fix, but it does not solve the problem THIS time. I always have the Touch Sounds unchecked, but now the crackling is there.

Thanks,

Peter

---------- Post added at 06:53 PM ---------- Previous post was at 06:37 PM ----------

I flashed 20140228, and the Black Screen of Death appears to be fixed. :)

Peter

Addendum: The crackling sound also appears to be fixed, so the only logical conclusion is that it must have been something in Tamesek's kernel.
[Galaxy Note 3 Android Development] pippilangkous:
temasek is perfekt kernel..it has a super!!!battery life

and the sound you hear if noone besides +the disable touch+ has this issue, itmight be a bad flash,did you reboot after flashing?/dirty flash??..reflash the rom might help

ok you fixed it....never heard in temasek thread aboutthis sound

but again you got rit of it;)
[Galaxy Note 3 Android Development] testmonkey1:
I'm pretty sure that temasek is using FauxSound in his kernels, so the crackling sound might be due to FauxSound increasing too much the volume levels. Just a wild guess though.
[Galaxy Note 3 Android Development] sauron82:
I'm running the latest CM official nightly and Temasek's kernel. No crackling, even at full volume. Did it happen with every sound it played at full volume? My first thought is the speaker is just distorting because the source material is recorded to loud (a real possibility), or that the speaker is blown (but if it's not crackling anymore then your speaker's fine). And if it's mp3s you're listening to, all mp3s crackle a little lol. Most people just don't notice. FLAC FTW!

I'd try reflashing Temasek's kernel with a clean rom install, no dirty flashing. Full wipe, rom & gapps, boot, kernel, boot. CM official kernel isn't that great. If you're happy with your battery then CM kernel is fine, but Temasek's kernel is insane for battery.
[Galaxy Note 3 Android Development] ki1120:
May I know how I can choose to use LTE/WCDMA only, without GSM?

I installed the latest nightly, and switched to English (United Status), but I found there isn't such an option - must be with GSM.

Thanks.
[Galaxy Note 3 Android Development] wilfredlams:
They haven't implement it in https://github.com/CyanogenMod/andr...ervices/Telephony/res/values/network_mode.xml. Was wondering did you get the problem of getting a huge list on the preferred network mode when not running the phone in english?
[Galaxy Note 3 Android Development] testmonkey1:
Don't know about him but I did for sure. When I was using English (UK) as my language I had at least a couple of more options than with English (US). FC on the UK one though. Don't really even remember the options, there isn't even a LTE in my area
[Galaxy Note 3 Android Development] nitrous²:
Sorry it took so long. I've attached the audio_policy.conf file from today's nighlty (20150609-N9005_hlte).

Update:

Weird. With today's nightly, using BOD6 audio_policy.conf doesn't solve the distorted/crackling sound issue anymore. It did on 20150606 Nightly.

Based on this and this commit, it should be fixed as it says that it's been merged to git repository :confused:

Update 2:

Up until this morning I could just replace the existing audio_policy and set the correct permissions to resolve the audio distortion. Didn't work that way anymore after today's nightly. I went ahead and just replaced the contents, the actual code of hlte CM's audio_policy with hlte BOD6's audio_policy. Did the trick. I don't understand what's happening. Im off on reddit now...

Update 3:

Nvm. The file manager I was using (FX Explorer) somehow failed to set the correct permissions. Did the same with Solid Explorer Beta and all went fine on nightly of June 11th.
[Galaxy Note 3 Android Development] thecdc:
Hi nitrous, I flashed your zip on the previous site. And the audio quality is better and i don't have any distortion when i hear musik With the phone speaker.

I flashed this zip on the aosp liquidsmooth rom. Thanks

Gesendet von meinem hlte mit Tapatalk
[Galaxy Note 3 Android Development] Journyman16:
I gave it a try, BrokenOS... same result as all other AOSP and CM ROMs - Dial Emergency hangs with 'Dialing' flashing slowly and attempting to hang up has 'Hanging Up' also flashing slowly - have to reboot to get phone working again.
[Galaxy Note 3 Android Development] bjanha:
Thanks for testing it. I cannot believe how low priority and little interest this really serious bug has got.
[Galaxy Note 3 Android Development] nitrous²:
Have you guys reported on CM's Jira? It's a very critical issue. https://jira.cyanogenmod.org/secure/Dashboard.jspa
[Galaxy Note 3 Android Development] Bobanovicz:
Is here anybody, whom the equaliser (Audio FX) works? (hlte)
[Galaxy Note 3 Android Development] Journyman16:
Yep - some time back at CM ROMs will not allow emergency calls. No response so far.
[Galaxy Note 3 Android Development] nitrous²:
Let me post this on G+!
[Galaxy Note 3 Android Development] Gandicela:
I'm on hlte myself, for sometime now I know it didn't work. I never tried anymore with the latest nightly (I'm running cm-12.1-20150611-NIGHTLY-hlte) as i removed it using bloatware removal script. As a replacement I got Dolby Atmos 6.3 working good.
[Galaxy Note 3 Android Development] zmore:
911 = FAIL

You know, I read some people commenting over the past few days that dialing 911 didn't work on CyanogenMod, and I was skeptical. I figured it was probably just some anti-CM trolling, but it turns out to be true.

I've never had to call 911 in my life, but earlier today a neighbor asked me to because the ambulance he called for was 30 minutes late, but it FAILED. When I dialed I heard nothing, and it never connected. A minute later I tried to hang up and call again but hanging up was also "hung".

I've been using CM since 2010, and have never had a big reason NOT to use it, but this is a pretty big bug that could potentially get someone killed. I've always had local police and a fire numbers in my contacts so it's not that a big deal to me, but I can no longer recommend others to ditch their stock roms for CM until I know this is fixed.

(FWIW: Was running the latest 20150612 nightly, and other calls worked, just not 911.)
[Galaxy Note 3 Android Development] mircury:
Yup, my story is here. Could have gotten us killed. In my opinion there needs to be a disclaimer somewhere in the rom notifying the user of no emergency calls until it is fixed. I can see someone at least trying to sue cm over this.

Vote for the issue here.
[Galaxy Note 3 Android Development] Journyman16:
Please do - I've tried a number of places and only result has been to increase the countries where it is an issue. :(
[Galaxy Note 3 Android Development] nitrous²:
Did. Apparently a malfunctioning emergency system is not something I may complain about, according to some people's interpretation of CyanogenMod's policy. While in theory this might be true, I still f*ckin' expect something as simple as an emergency system to work and at least be pushed out after proper testing!

Update:

The issue on Jira is now assigned to Abhisek Devkota and has got the Major issue status. Good.
[Galaxy Note 3 Android Development] zmore:
Done and done.
[Galaxy Note 3 Android Development] supergen007:
Hi, Google Keep is not working for me (FC) on stock cm12.1 while it works perfect on both TW and Temasek builds. Did somebody had this problem and knows how to solve this?
[Galaxy Note 3 Android Development] nitrous²:
What Gapps version do you use? It happened to me once on PA 5.1.x and Slim 5.1 Gapps. It never did on CM 5.1 Gapps, since it's not included and you have to download it manually from the PlayStore.
[Galaxy Note 3 Android Development] Journyman16:
Hey thanks for that - I had kinda given up checking. :D

I know the frustration - there are two serious sides to it - one is that people can DIE because of it but also, it could be illegal for CM and other devs to actually produce ROMs that nuke the emergency call ability, given it is actually the Law in many places for phones to be able to call Emergency even without SIM or password. And I don't mean illegal in the sense we are playing with our phones I mean illegal as in criminal statutes.

I did try to find out if there are other phones affected but got no responses on that. le sigh... It would be passing strange if ONLY Note 3's had the problem though.
[Galaxy Note 3 Android Development] nitrous²:
Had to delete the post because the comment section got outta control. It's incredible how they stick to their principle "it's a nightly, it's meant to have broken things in it". Some actual contributors and devs joined the discussion and led it to the point where one would think they ignore the fact that it's an immensly cirtical issue by insisting that the user has to expect bugs! Jesus Christ, we expect theming to be broken, or camera having bad quality or sound being distorted but not an emergency call function! We need the right to expect a safety system, an emergency call system to be working at all times on all ROM issues, be it nightly, monthly or stable! I don't find this to be an excuse.
[Galaxy Note 3 Android Development] celderic:
As i said in my previous posts, i had this problem with the i9100 (galaxy s2) in cm9 and cm10.. and an unofficial build of cm10.1, If i remember correctly cm7.2 also didn't work for emergency calls.

It was the end of 2013 when i stopped using my s2 i think, but until then aosp roms wouldn't allow emergency calls for me.
[Galaxy Note 3 Android Development] nitrous²:
And then there was this guy who said he'd contribute to RIL and would actually write code for CM and what not. He said why I'm using CyanogenMod on a critical device since most of it's drivers had to be reverse engineered. If I want a working device I'd be better off using one that requiers less "hacky stuff to be made to get it working"....he was referring to Nexus devices. Too bad the Nexus 5 and the int. Qualcomm Note 3 share the same SoC....and I didn't know camera, audio and various sensor's drivers etc. have something to do with the emrgency call system or modem/3g module.

And guess what, it doesn't work on the Nexus 5 too. I had the chance to test it with CyanogenMod 12.1.

And this and similar cases made me critical towards Developers. Just because they simply assume you to be a full on retard.
[Galaxy Note 3 Android Development] Journyman16:
I wondered about the Nexus - I asked on the Nexus 6 forum if they could try it and see... So if it isn't working there I gues it ain't working from Google - could be lawsuits coming up for them if someone dies because they can't get E-calls.

---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------

LOL - just checked the forum - 48 people looked at the thread and not a single reply. For some strange reason it seems most people don't understand the issue... ? Dafuq? :D
[Galaxy Note 3 Android Development] Yank555:
In that case :

1) why don't you fix it ? (this is a developers forum afterall, you are allowed to actually contribute)

2) why don't you run stock firmware ?

Just saying...

Nagging and whining has made me critical towards "such users" a very very veeeery long time ago :D

JP.

PS: Why don't many test this ... easy, over here if you dial 112 (it's not 911) for no reason, you're looking for problems.

PPS: And no, I'm no CM friend, at all.
[Galaxy Note 3 Android Development] nitrous²:
1- I'm sure I would if I could.

2- I don't like the sound it makes when I touch the screen....*spitsinspittoon

Let me make this clear. I was never the guy who'd talk like this if it weren't dev's and so called dev's acting up and developing a god-complex because the less smart user thinks he can do black magic. Have you seen the guys over at Dirty Unicorns, Franco Kernel or Paranoid Android in their forums and community's? Woe betide you, if you ask or say something non-conform. I saw it many times on Google+ communitys how a demigod publicly denounced someone and motivated others to do it too. I said it many times in the communitys and forums that it's wrong to do that. I got banned. I think it's the result of users "not-like-me" who made friendly personalitys into narcissistic, arrogant "I can do whatever I want"-dev. Just like in the ancient times with god's and mystic creatures.

I'm not willing to pay respect to someone and his work if he can't pay the littlest of respect towards others. Would you?

And I'm not saying everyone is like this. There are awesome guys like Temasek and I remember you being a friendly and humble person too since a couple years.

I hope I'm wrong with my opinion towards developers. I seriously do and I'm sorry I see things the way I do now. The discussions in the last couple day's underlined my argument. I made a friendly reminder and asked why a non-working emergency call function is low priority= #instaflame. I don't need that.

Sincerely
[Galaxy Note 3 Android Development] Yank555:
I do agree with you, but on one point, it's not devs, it's persons, there are reasonable persons and there are morons.

Now persons can be devs and can be users.

Those two are very different categories, not linked one with the other, so in this matter we end up with 4 types of persons ;)

I won't even comment on DU, I've been done with that Cruz guy since he bashed arter and temask for pointing out DU kanged Temasek's kernel and removed the reference to Temasek, that's just not cool, and even less, when DU won't stop bashing whenever someone else behaves that way (which IS wrong, but you just sh*t the f*ck up when you are the same and don't play holier than the pope, or you apologize to Temasek, he did neither).

CM's been known to be pretty nosy, since forever, no bug reports on nightlies etc.etc.

But I also can't accept outbursts of users calling devs names because they don't do what users want. Users cannot expect devs to 'execute every wish', they do what they do because they feel like it, no obligation implied/supplied.

Users have a simple democratic way to vote, use a different ROM/kernel/app. While many devs seem to need a userbase, not all do ... I do what I do for myself, to learn stuff, and if someone else has use for it, good, it's nice, if not, good as well, I have what I want on my device and I will go on doing what I do for myself.

And I don't accept any donations, as I don't want anyone to think I'd be owing anything to anyone, even if a donation should be an appreciation for a work done and never for any work ahead.

So to get back to the topic at hand, if 911 won't work and it's important for you to work, CM doesn't give a ..., switch to stock ROM, there doesn't seem to be an alternative for the hlte :(

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0a kernel.
[Galaxy Note 3 Android Development] nitrous²:
I actually though about adding a line similar ot this to my post but forgot it. I totally agree with that. Maybe I should. Otherwise my post borders on racism xD

Understood a long time ago, hence I'm on Stock ROM again.

Sincerely
[Galaxy Note 3 Android Development] Oeps:
Hello,

Have a Note - N9005

Installed Nightly 12.1-20150614-NIGHTLY-hlte, kernel 3.4.0-g7db381d

twrp-2.8.6.1

Prior to this installation I was running stock Samsung Lollipop but did't like the stability of Wifi and BT (and all the Samsung crap sw :)

Happy to run CM12.1 again on this phone except one feature is not working (or I do not know how-to).

I want to encrypt the internal storage but after selecting encryption the phone boots and stays at the animated CM logo forever (left it for 90 minutes). Pull out battery and phone boots again fine and is not encrypted.

Before I rooted and installed CM12.1 I decrypted my phone in the Stock rom.

Then I formatted /data with twrp to ext2 and then again to ext4 so no residues of previous encryption should be there.

Any hints on how to get Encryption working with cm12.1? or does is not work at all? I couldn't find recent information about CM12.1 and (non working) encryption.

Any other 5.1.x ROM's that have encryption working?

(I need to have encryption because the business SW I use demands it).

Thanks!
[Galaxy Note 3 Android Development] jisoo:
I've been trying to encrypt as well. I've also tried different nightlies, as well as various other AOSP ROMs, but it does seem that encryption is broken in 5.1.
[Galaxy Note 3 Android Development] Oeps:
Thanks for the reply, Did you install another ROM which works with encryption? Which?

I prefer 5.x (except 5.0) because of the Smart Lock with my Pebble but going back to KitKat is an option if encryption would work.
[Galaxy Note 3 Android Development] Yank555:
http://review.cyanogenmod.org/#/c/101138/3

As it looks, purely hlte issue.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0a kernel.
[Galaxy Note 3 Android Development] jisoo:
I haven't been able to find a working version, unfortunately. Encryption on CM did work before January, but I can't find any download links which still work.
[Galaxy Note 3 Android Development] istperson:
This fix is for 12.0, but I didn't find the appropriate code in 12.1. So it's not trivial to port it.
[Galaxy Note 3 Android Development] MattyBoy4444:
The fix is in the latest nightly. I tested it and it called 911. Though they didn't seem to have my location except from closest tower.
[Galaxy Note 3 Android Development] navdra:
I'd like to revert to cm-12-20150416-NIGHTLY-hlte but can't find anywhere.

I decided that Xposed framework and other minor instability issues are not worth for trouble.

Could someone pls msg me if still have latest CM12 (cm-12-20150416-NIGHTLY-hlte.zip) backed up somewhere
[Galaxy Note 3 Android Development] Gandicela:
5th from the bottom of the list. https://download.cyanogenmod.org/?device=hlte
[Galaxy Note 3 Android Development] navdra:
I should have mention. This link is down. And I searched all over the Internet and can't find it anywhere.
[Galaxy Note 3 Android Development] nitrous²:
I started using CM again with the nightly of 12th April 2015 and since then I noticed this minor bug that when I choose to show the battery percentage within the battery icon the percentage would disappear after a while. It does work on the lockscreen and for a short time whenever a new theme is applied and sometimes sporadically. Can someone confirm this?
[Galaxy Note 3 Android Development] celderic:
Latest 25th nightly, says emergency calls only although i have full LTE and calls work fine.

View attachment 3379321

Edit-

Correction, after rebooting it was back to normal.. I went to an area with 'emergency calls only' and came back to a place with signal and noticed the text didn't update.

Hopefully this helps.

Edit2- i should probably add what modem i am running, as i guess it sends the OS something telling it i only have access to 'emergency calls only' ? Or does android do it through the signal strength?

But i am on the XXUGBOD3 Modem. With the latest bootloader.