yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] amoblox:
I was seeing the same. I went back to stock (customized) because I felt foolish pulling my battery a few times a day.
[Galaxy Note 3 Android Development] Kevin36:
Can i flash xposed installer and gravity box and what can be done to get better battery life?
[Galaxy Note 3 Android Development] Te3k:
FYI, for those with random reboots, you might need to bump your villages a bit (+25mV). Qualcomm apparently dropped the voltages by that amount across the board since NA6 sources.

That solved things for me.
[Galaxy Note 3 Android Development] siraltus:
Thanks for the info. I'll just wait until this is properly handled in CM. Between this, the broken CPU control, broken NFC, and reversed headphone channels, CM is not quite ready to be my daily driver yet.
[Galaxy Note 3 Android Development] PeterGuru:
I've also had a few random reboots. I would be in a certain app (not always the same), and adjusting the settings within that app when, suddenly, the screen would freeze for a few seconds and, then, a sudden reboot.

I'm sure it will be resolved on future releases.

Peter
[Galaxy Note 3 Android Development] Yank555:
I agree with you in principle...

But on the other hand, help is not 'really' welcome there either, when you use the source, and want to contribute, the effort to get it through is not worth the fuss, really... I, too, have limited free time just like CM's devs, and I rather spend it developing stuff I need/want than 'begging' for CM to consider it, I have it, it's publicly available, that's all there is.

OMNI / SlimROM, as counter-example, do it in a more active way, they use your stuff from your repo, that's nice, CM you need to 'impose' your stuff upon, if it's even considered. I just don't have time to waste for that, and so I think many react in the same way.

CM needs to get their feet back on the ground, they tend to take themselves for a second Google... if it's supposed to be a community project, don't shut off the community, use it instead. But "don't post bugs, don't talk about other kernels, other spin-off ROMs ..." won't get you any further either.

I consider that pushing what I do to public repos on github should be good enough as a contribution, it's out there, just like CM's stuff is, for maintainers to cherry pick. We're all at one same level here, CM is not god and other devs are just peasants, we're all (supposed to be) part of one community. If others can do it, so could / should CM.

Still, as you correctly point it out, that won't help us get a better experience on our device :(

I'm not into ROM stuff, so I can't help here... I'm still on an old nightly (hltexx 20140127) because it works perfectly for my needs and I have a kernel that does have what I expect, and I just had no time for Android stuff because of my job for several weeks...

I've just started redoing my kernel for hlte, almost everything needs redoing, so I'll focus on redoing my stuff for now...

NB: On an official CM thread what I just posted would be booh'ed upon because I talk about custom kernels (and I openly dared to criticise CM's behaviour), but how do you want progress if you don't accept to listen ? Community should be closer to a democratie than to a totalitarian state...

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta6 (3.4.84) kernel.
[Galaxy Note 3 Android Development] wilfredlams:
The truth is that we don't have any other roms that fixed up the core issues in the source and they are all cm based, so if the cm source isn't fixed up, all other aosp roms we currently have will have the same problems, another issue is that compare to most of other common phones in the market, our phone's aosp roll out is the slowest by far. It' nearly April now, the phone was release last year's September, and we are still having problems at basic issues. The dev's have a lot of time, and there isn't a single merges in gerrit the whole month and when they do, they just screw up the whole system, wow really?
[Galaxy Note 3 Android Development] Robster83:
What option is there though? CM11 isn't perfect, but most Nightlies offer quite a few changes, additions and fixes and sure it takes longer than we'd hope to fix the big issues (calling, for instance!) but fixes do come.

If there were an alternative ROM that was complete, solid, efficient, reliable, well supported and had continued ongoing development I'd move to it. But there isn't. Most are based on CM11 or are modified versions of TW, which I hate!
[Galaxy Note 3 Android Development] Yank555:
Well roll-out is way better than on the i9300, so it's all relative I guess ;)

Tbh I can't say that I have any real issue on the hltexx 20140127 nightly ...

OK, what really messed this whole thing up is Samsung, with their new bootloader, their kernel rebase, and the fact that many stay away from rooting the Note 3 because of the eFuse crap etc.

So less users = less potential devs = slower fixing issues

But what 'core' issues do you have on the Note 3 ? Other than what this new blob stuff has brought a few days ago ?

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta6 (3.4.84) kernel.
[Galaxy Note 3 Android Development] Robster83:
The main issues are the inability to make or receive phone calls on the latest Nightlies, if you roll back to an earlier one you lose function of the buttons (home and menu mainly) so you need a full reset. There is also the 'time' bug, where the phone doesn't set the time correctly on a reboot. There is a problem with searching for networks too.

There are also some smaller problems, stability concerns, some functionality missing (4k video for instance) and the new blob problems.
[Galaxy Note 3 Android Development] wilfredlams:
Problem with the qualcomm time daemon and error while searching for network is the main issues which really annoy me. It's like that since day one.

Oh and the kernel fail to boot into charging mode when the phone is off, it gets stuck at the bootloader.

I am annoyed that they don't care when this was there for such a long time and they don't bother to fix it, it was like that for 3 months, if I didn't help to fix up the network_mode.xml, there will also be a problem with the preferred network mode until now, because our maintainers don't care, when Dan Pasanen, Rick C and Dave Daynard was working on the d2 and jflte to acturally get it fixed when no body bother to submit it for the hlte.

Technically, I don't think we have an ongoing maintainer for hlte because if you compare to the amount of gerrit reviews there are for the d2 and jflte, and then look at hlte, you will know why this is true.
[Galaxy Note 3 Android Development] ahkiongkc:
Have anyone tried 30? I hope the instability of calling is fixed. Ive tried 28 and when i rollback, error came out. I gotta do clean install n lost my settings and apps.
[Galaxy Note 3 Android Development] wilfredlams:
Still the same, no new merges.
[Galaxy Note 3 Android Development] pbedard:
I have a build I made with the speaker fixed and the clock issues cm don't like to play nice with other devs so I'm keeping it for private also I may have a perminant GPS fix
[Galaxy Note 3 Android Development] dtr145r:
Can you please share the crackle fix zip file?

I only found the CDMA fix...

Thanks.
[Galaxy Note 3 Android Development] pbedard:
After I make sure it doesn't break anything I dont want cm blaming me
[Galaxy Note 3 Android Development] testmonkey1:
:o Why don't your share it here on XDA at least? Those are the main issues us users are having with CM at the moment, and you've fixed them.. Woah :D
[Galaxy Note 3 Android Development] pbedard:
Cause I'm waiting on the GPL to make sure I'm in compliance I'm not using cms kernel I'm using my own

---------- Post added at 05:18 PM ---------- Previous post was at 05:13 PM ----------

Love it with no crackle

---------- Post added at 05:29 PM ---------- Previous post was at 05:18 PM ----------

I'm making a sprint only unofficial build and releasing it if anyone wants my code u need my permission I'm not posting it anywhere til the GPL gives me permission I'll have to use cms kernel I'm asking them for permission bit will be for sprint only
[Galaxy Note 3 Android Development] testmonkey1:
Oh you're on the Sprint variant? I thought the time bug was only present on the N9005?
[Galaxy Note 3 Android Development] pbedard:
This ROM is unified its across a variants
[Galaxy Note 3 Android Development] dtr145r:
You can still share it. Since it's not part of their ROM it doesn't matter.

---------- Post added at 01:55 PM ---------- Previous post was at 01:46 PM ----------

Looking forward to the sound crackle fix. :D

I have the Tmobile variant so I can text it out for you here ;)
[Galaxy Note 3 Android Development] Yank555:
Hmm ... strange, either I'm lucky, or those issues started with the 'unification' (hlte), on my old build (hltexx still, not hlte), I don't seem to have those issues (of course I have no 4k video, I consider that more a lack of feature than a bug, but that's nothing I personally use), but time is fine, network searching is normal. I've not yet tested to charge the device while off, tbh, never happens that my daily is off ;) The only 'bug' is the sound distortion when touch sounds are enabled, but also I always disable them right away, so not an annoyance.

I think I'll stick with my 'old' setup for some more, I need a working device.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta6 (3.4.84) kernel.
[Galaxy Note 3 Android Development] springer.music:
I'm using a N9005 and I haven't bumped into the infamous time bug (yet).

I recall having read somewhere that similar time bugs may be triggered by a buggy recovery. Can anyone confirm this?
[Galaxy Note 3 Android Development] testmonkey1:
No, they are not. Just reboot your phone without being connected to WiFi.
[Galaxy Note 3 Android Development] wilfredlams:
Best way to test it is disable automatic date and time and restart.
[Galaxy Note 3 Android Development] ahkiongkc:
You didn't have the time bug issue? What recovery are you using? On the other hand, I am also facing the instability issue, which it restarted by itself or hang when it goes into sleeping mode. I can still cope with the rest of the issues except for this two. Please advise me if you have any temp solutions.
[Galaxy Note 3 Android Development] springer.music:
You're very right. I rebooted in aeroplane mode and got an incorrect time.

Tested with both CWM and TWRP and the bug is there when you reboot in aeroplane mode. When in recovery mode, TWRP always shows the very same same incorrect time

I haven't experienced this bug (yet). I'm on the nightly from March 27.
[Galaxy Note 3 Android Development] testmonkey1:
The time issue is thereregardless of recovery. Upon reboot your phone resets the date/time. The most annoying part is that it's only syncing via WiFi. E.g. your phone hangs/or whatever reason you need to restart it say on the bus while traveling. The time/date won't sync over mobile data and you have to set it up manually. And you can't skip it since there are all these problema with online connectivity if you have an incorrect time/date.
[Galaxy Note 3 Android Development] springer.music:
In my case I have the incorrect time only if I'm completely disconnected from both Wi-Fi and Mobile data.

With Wi-Fi off and Mobile data on, the time is correct.

I did the following test:

- Turned off Wi-Fi in settings and then put the phone in aeroplane mode

- Rebooted the device and got the incorrect time

- Disabled aeroplane mode and kept Wi-Fi off. The time changed to the correct value as soon as the phone connected to the mobile network.
[Galaxy Note 3 Android Development] Yank555:
Well, then it's really a derp in the unified aka. hlte build, I just rebooted in airplane mode on my old hltexx nightly (20140127), no problem, time's set as it should.

JP.
[Galaxy Note 3 Android Development] Eddiemc:
Anybody tested if today's msim commits fixed the call issues?
[Galaxy Note 3 Android Development] Lafenear:
It didn't, unfortunately.

Seems like it's time for a fresh install of N27.
[Galaxy Note 3 Android Development] testmonkey1:
Correct, as far as I remember the time bug is present since the "unification" of the builds and the update to the new bootloader.

It is also only present for the N9005 variant as far as I know.

Hmm this is weird, can you confirm this on 100%? Also are you on the N9005 device?

I have done the same test myself, with results being:

wifi ON/mobile data ON: time sets itself correctly

wifi OFF/mobile data ON: time remains wrong.
[Galaxy Note 3 Android Development] springer.music:
Yep, I can confirm it.

The time is correct with WiFi OFF and mobile data ON (N9005).
[Galaxy Note 3 Android Development] cam30era:
FWIW: VZW DE (SM-N900V) here running "ancient" 0314 hlte. 4.3 bootloader, TWRP 2.7.0.0. Time bug not present, ie device boots with correct time with WiFi off.
[Galaxy Note 3 Android Development] Pino76:
Critical Bug

I don't know if this is the only way to report bugs, but I hope the developers will read it - I can't make phone calls, they are ended as soon as the number is dialled. Would you please fix it as soon as possible..

cm-11-20140331-NIGHTLY-hlte and the previous one(s)
[Galaxy Note 3 Android Development] wilfredlams:
Unfortunately, there are no maintainers for the N9905, we are screwed. Maintainers currently only care about the CDMA devices and american variants, sad news but true.
[Galaxy Note 3 Android Development] Eddiemc:
That's sad to hear.

I hoped this device would get proper cm support since being snapdragon and all, but alas.

Don't you think this will change though? Isn't cm interested in maintainers?

It's unfortunate that there's poor European support because all aosp used more or less cm stuff to work. Maybe time to try tw again..
[Galaxy Note 3 Android Development] Yank555:
Well I am on a n9005, but am still the old (JB) bootloader, and the old CM nightly 20140127 (so the

non unified build

) and as such, no time issue.

I won't jump up, I need my Note 3 to work, it's my daily phone, for business and personal stuff, so there's no going like a kamikaze for the unified build for me... ;)

... especially since

everything I need

is working on the non unified build.

JP.
[Galaxy Note 3 Android Development] ki1120:
so do I, using N9005 International.
[Galaxy Note 3 Android Development] pbedard:
If u dirty flash that's your ossue
[Galaxy Note 3 Android Development] springer.music:
The call issue on the latest hlte builds has nothing to do with dirty flashing.

He's on an N9005 which is the international GSM model.

All hlte builds published between March 28th and today, March 31, don't allow any calls on the GSM version.

From your signature I can see that you're on the Sprint version N900P which is a CDMA model.

As far as I can see here, the CDMA version should be fixed by now, whereas the GSM version has not been fixed (yet).
[Galaxy Note 3 Android Development] Pino76:
Hi, yes I have the N9005 International as well. I don't know which build screwed the phone function but I restored my phone to cm-11-20140323-NIGHTLY-hlte and it's working again..
[Galaxy Note 3 Android Development] springer.music:
The latest version with working calls on N9005 is cm-11-20140327-NIGHTLY-hlte
[Galaxy Note 3 Android Development] kenzolo:
someone has identified which commit caused the call bug?
[Galaxy Note 3 Android Development] cam30era:
This comment posted by Hashcode (3/28) on the VZW CM11 thread:

"PSA: Avoid the next nightly or 2. Some of the RIL blobs were updated to 4.4.2 NB4 files and they are currently incompatible w/ our RIL firmware.

Looking into keeping some of these updated files separate for GSM devices only."
[Galaxy Note 3 Android Development] rooooooooney:
i have NC2 Bootloader

Can i Install CM on My 9005? :(
[Galaxy Note 3 Android Development] springer.music:
Yes, you can.

If you install it now, just download the nightly release from March 27 here:

http://download.cyanogenmod.org/get/jenkins/63355/cm-11-20140327-NIGHTLY-hlte.zip

I would not recommend downloading/installing any of the nightlies from March 28-31 as calling does not work on the GSM variants.
[Galaxy Note 3 Android Development] jisoo:
Reverting this one and the other hlte commits which came after this restores things back to a working state: https://github.com/TheMuppets/prop...mit/3d18a0472408b7053c3aac1b0f4ba2b77ed3cfb8
[Galaxy Note 3 Android Development] pbedard:
Confirmed working on the new c5d bootloader
[Galaxy Note 3 Android Development] ahkiongkc:
CM-11-20140327 works pretty fine compared to 31. I face the same issue as yours when i install 28/29 - the calls ended as soon as i press call button. I have to make several attempt then only it got through. When i rollback to 27, i got errors and errors flooding my screen. I did a clean install of 27 in the end.... Sad
[Galaxy Note 3 Android Development] apascual89:
Hey why all the continued hate on cm in this thread ( [MENTION=2792898]pbedard[/MENTION] not directed @ you, just the general direction of this thread)? We're all using their source. Or at least parts of it like their device trees, kernels, etc. Why don't you just submit your fixes to gerrit and see what happens. That's the spirit and definition of open source after all.

It has been questioned in this thread why people don't submit back to the original code to make it better, I would say this is the perfect opportunity to do just that. If you can fix the only "minor" bugs then by all means submit your fixes.

Just my opinion in the matter.
[Galaxy Note 3 Android Development] christer12:
You only need to revert the to last commits

This one:

https://github.com/TheMuppets/propr...mmit/4054e0ecd6f4525b42efae03e482ee680911db2b

and:

https://github.com/TheMuppets/propr...mmit/1d61d08413780ecaf0ebb1c21d58e75f553583f8
[Galaxy Note 3 Android Development] apascual89:
Agreed and confirmed
[Galaxy Note 3 Android Development] wilfredlams:
It's the new NB6 sources
[Galaxy Note 3 Android Development] christer12:
Have you seen the new memory layout? More free memory.

CM is working on a kernel update that's coming soon. :D
[Galaxy Note 3 Android Development] Whosdaman:
How about phone calls? Seems like that should be a priority over everything
[Galaxy Note 3 Android Development] christer12:
Just have to wait patiently. =)
[Galaxy Note 3 Android Development] ahkiongkc:
Yeah priority should be given to the call's bug but i don't see any discussion over it being initiated as yet.
[Galaxy Note 3 Android Development] :
Did anyone experience variety in button vibrations too?

I'm not sure if this can be ROM-based, to me it sounds more like it's hardware based.

It's hard to explain, but sometimes the small vibrations from keyboard typing and hardware button pressing will change slighty. The normal vibration is small and very friendly, but sometimes it changes to more brutal vibration. It's not always, it's very random.

So did anyone else experience difference in the way the phone vibrates? I haven't gone back to STOCK ROM to see if it helps.

I'm running Temaseks v59, I couldn't find a more fitting place to post though. Thanks.
[Galaxy Note 3 Android Development] ahkiongkc:
Let's build up a list of current known issues that every each of you is facing.

1) random reboot (everyday)

2) screen hang when it goes into sleep (sometimes)

3) phone call drop once number pressed (only on ver.28 and above)

4) time error when restart

5) mobile network selection

Please correct me if I'm wrong.

---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------

No problem with mine but i don't think is hardware issue.
[Galaxy Note 3 Android Development] :
I really hope it's not. It just seems odd, that it should vibrate differently, doesn't it?

I'm afraid that it's an hardware issue, because I dropped it from like ~20cm yesterday to my carpet. I have done that a few times before though with no issues at all, but I only just noticed it after that slight drop. It's a small but insanely annoying thing. I just really hope it's not an hardware issue.

Do you think a little drop like that could be the reason?
[Galaxy Note 3 Android Development] ahkiongkc:
If it's really a hardware issue then it won't be vibrating hard and soft at some point of time. Why don't you give other ROM a try and see if that give you the same result. The vibrator itself cost US$20 from my experience.
[Galaxy Note 3 Android Development] :
That makes sense. Thank you. I will flash STOCK 4.4.2 asap and see if it changes anything. I will report back with my results.
[Galaxy Note 3 Android Development] :
It seems to be an HW issue. It happens in TWRP too.

Oh sigh.
[Galaxy Note 3 Android Development] xavihernandez:
4.4.3 Update

What should be fixed for CyanogenMod ROM thanks to 4.4.3 update:

- data drops

- bluetooth incompatibilities

- random reboots

- battery drain du to camera

I think I have already seen those 4 bugs around CM11 forums.
[Galaxy Note 3 Android Development] wctliu:
Hi, can you help me to add the N9008 support? and add the Td-scdma support?

thanks a lot

the SM-N9008 is the note3 in China,the product.name is hltezm.used the cpu Qualcomm® Snapdragon™ 800. it can flash all of the N9005's samsung rom.and it support the GSM,WCDMA TD-SCDMA

here is two path,the path 1 can add N9008's support ,the path 2 can add the TD-SCDMA support.

View attachment 2662600

View attachment 2662601
[Galaxy Note 3 Android Development] Bill Gates:
Cannot make call

On the 1st April version I encountered bad problem: Can't make a call. Previous was 27 March and calling works.
[Galaxy Note 3 Android Development] wilfredlams:
If this is for adding support to cyanogenmod, you will need to submit that to gerrit for review at review.cyanogenmod.org if you know where this file should belong.:)
[Galaxy Note 3 Android Development] sauron82:
And NFC. Only works on N9005.

Click thanks if I helped you
[Galaxy Note 3 Android Development] FranticOgre:
Just wanted to post about the call drop once number pressed but it seems others have this problem too.
[Galaxy Note 3 Android Development] GHolbrook4:
It's a known issue, do a fresh install of the 3/27 nightly until it's resolved.
[Galaxy Note 3 Android Development] Mechayoshi:
So does anyone know what would be the most stable nightly for the n900p? I wanna try this but I need at least basic functions working.
[Galaxy Note 3 Android Development] pbedard:
There is no stable yet
[Galaxy Note 3 Android Development] dtr145r:
most stable nightly is 3-27.
[Galaxy Note 3 Android Development] Mechayoshi:
I guess I'll just hold off until it's pass the nightly phase. Any idea on how long this will be?
[Galaxy Note 3 Android Development] sauron82:
I'm starting to doubt it'll happen at all. So many other devices are up to milestones and snapshots. CM11 work started at after KitKat launched (obviously) and the Note 3 launched before KitKat, so it's not like other devices have a head-start on CM development. The only conclusion I can reach is that CM has forgotten/doesn't care about the Note 3, which is a shame, 'cause it's gram-for-gram the best phone on the market right now.

Click thanks if I helped you
[Galaxy Note 3 Android Development] Mechayoshi:
That stinks I mean, isn't this supposed to be one of the more popular phablets? Possibility are endless.
[Galaxy Note 3 Android Development] dhufford81:
All of you *****ing.... This is a work in progress (beta). I suggest looking up what that means if you don't understand. Cyanogenmod doesn't owe you anything, and your entitlement is laughable. If I was a cm dev and I read any one of the cm threads I'd make all of my work private and tell most of you to piss off. If you want it to work so bad but you have to come here and bash devs/maintainers for not doing it the way you want, learn to code. Stop commenting bull**** and learn to code.
[Galaxy Note 3 Android Development] Mechayoshi:
No need to take things personally, I'll be patient.:/

Unless you're talking to someone else (which I think is the cases considering I haven't complained about anything)