yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] mygadgetgeek.com:
This thread is getting silly why can't people just wait I'm on new bootloader I new once updated i couldn't go back im am so grateful for the work all developers do I been jailbreak in my phones since iPhone 1 HTC hd2 the work these people do is great just wish people would stop all this crap bootloader be done when it's done new cm build the same I'm sorry for the rant I don't normally worry what's being said but I check this thread to see how it's coming on not for all this rubbish

Hit thanks if I helped mygadgetgeek.com
[Galaxy Note 3 Android Development] jetbruceli:
Haha we all rant and comment so this thread keeps on top of the thread section. Plus it keeps everyone looking just see if something pops up.

I actually check the cm device download more often than this place though.

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] Cyenominerva:
I wonder if someone will know the answer to this. If the Note 3 is an officially supported CM device why is there no discussion forum on CM forums?
[Galaxy Note 3 Android Development] jetbruceli:
Hopefully due to the release of m3 builds ours will be included soon.

http://www.androidpolice.com/2014/02/10/cynaogenmod-11-m3-builds-are-rolling-out-now/

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] maxgohan:
hey guys,

trying to figure out how I can add more pages to my homescreen,

thoughts? :dunno:
[Galaxy Note 3 Android Development] jaythenut:
to ad more just pull a app or widget to the right side to make a new screen
[Galaxy Note 3 Android Development] rubino90:
Not for note 3 :/ i think not arrived
[Galaxy Note 3 Android Development] Lenniitsch:
Sry for the (dump?) question but does somebody know why the nightlys has stopped? On the changelog site (click) is just an list of changes for the next nightly. So I'm not asking for when the next nightly comes, just why they have stopped ;)
[Galaxy Note 3 Android Development] jetbruceli:
Just read throughout here and here's a hint** boot

Loader

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] toker_X1:
[MENTION=675653]nowy57[/MENTION] - Can you please update OP and state theres currently no nightly due to you know what.......

Also, can a moderater please delete the last 25 pages or so, as its all rubbish and useless information.
[Galaxy Note 3 Android Development] jetbruceli:
What???

There very useful information there buddy. Hopefully it will give a hint to what's going on. If they delete it then it will start all over.

The OP just made a thread to dedicate a place to talk about cm. It's not an official thread by someone from CM.

All anyone needs to know is they are working on it and when it's available they will let us know ok??

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] toker_X1:
unfortnately thats not the case, the last 20/25 or pages its all ...

1) When is the next CM nightly out

2) When is CM available for 4.4.2 bootloader

3) Why has CM nightly stop.

if this was on the OP then we would get less dumb questions on this thread

I have not seen anything useful like someone reporting a bug or have a work round...or a tweak

Its been the same questions / answers / angry xda members flaming newbies for asking the same question since 31 Jan!
[Galaxy Note 3 Android Development] jetbruceli:
That's because like I said this isn't a thread from the maintainers of cm like there is normally.

In fact some devs are avoiding making threads about their work simply because of the crap that is posted throughout their threads.

A cm Dev thread will say please only post issues and logs but still there will be a ton posted about dumb stuff like where is Google play and can I still use my touch whiz apps!!

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] jaythenut:
very true:silly:
[Galaxy Note 3 Android Development] toker_X1:
LOL, very true.
[Galaxy Note 3 Android Development] radicalisto:
Are you back on the N3 now? or still using the N5?
[Galaxy Note 3 Android Development] toker_X1:
Yeah went back to N3 when CM11 nightly was released

I got another replacement last month via insurance (i accidently lost mine whilst skiing hoping to get one with better build and it worked! :D )

But i did update to KK when I got my replacement and now stuck with TW :(

I still use the N5 when roaming as its easier to access SIM
[Galaxy Note 3 Android Development] neoKushan:
I see you're complaining about the amount of rubbish posts for the last few pages. I hope you realise the irony here.

For the love of Christ, people - not everyone has the time, patience or ability to trawl through pages and pages of posts to find what should be a simple answer. If it's not in the OP, give them some leeway because not everyone is down with how these forums work. Yes, it's annoying, but it's part of the territory.

Furthermore, if the repeated questions are bothering you? DON'T MOAN ABOUT IT - believe it or not, your posts *****ing about it are just as annoying and unhelpful as the questions themselves. Either answer the question, direct them somewhere that answers it for you or IGNORE IT.

Ideally, if questions are being asked again and again, kindly ask the OP (or a moderator) to add it to the first post.

For the sake of clarity, though:

* Nightlies are currently broken due to merging of new files from Samsung that deal with the new bootloader, among other things. There is no ETA on this being fixed, but it will be fixed soon enough.

* If you're on the new bootloader, you can't use an AOSP ROM, or even a JB ROM (touchwiz or not) until the merging is complete. Deal with it.

* Using CM (or ANY AOSP based ROM) will mean no use of S-pen and other Touchwiz/Samsung specific features. You may be able to replace lost functionality with some aftermarket apps, but don't expect Miracles.
[Galaxy Note 3 Android Development] toker_X1:
Your reply = My point exactly!

Same questions / same answers

For the record I have asked OP to be updated and mod to do a clean

Also you dont have to read every page. There is an invention called 'search'.
[Galaxy Note 3 Android Development] GigabitEthernet:
Here's what I propose: as soon as there is an update, I will post it here.

---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------

Currently, there are no updates, as soon as CyanogenMod releases a new nightly, I will post it here.

You cannot install the current nightlies (30th January and before) on the 4.4.2 bootloader - it will not work. You cannot downgrade the bootloader - Samsung made that impossible.
[Galaxy Note 3 Android Development] kryz70fr:
usb audio is supported ?

you can revert to 4.3 with nandroid backup and old bootloader if any problem ?
[Galaxy Note 3 Android Development] Ninkul:
How's the stability and battery on this one? Keen to flash but just want to get an idea of how the ROM is before doing so.
[Galaxy Note 3 Android Development] dan.kels.r:
Can't answer the audio question but this rom uses the old bootloader. It does not flash one with the rom. If you already upgraded to the 4.4 bootloader then you can't run this rom. Flash then and you can revert back to TW 4.3 ROMs
[Galaxy Note 3 Android Development] ouankou:
Very sorry, reply to the wrong post.
[Galaxy Note 3 Android Development] swani:
Is there any news to this yet?

Tried to search for some answers but couldn't find :/
[Galaxy Note 3 Android Development] Berget:
i tryed to flash the nightly today, i only get Status 7 "this package is for "hltexx" devices; this is a "hlte" with CWM ( twrp aswell, no luck there)

i tried to flash the new bootloader and use the latest CWM no luck there...

my old rom whas Teamsek's...

what i have read here now, the cm rom is not working with the new bootloader? can i downgrade?

what to do?
[Galaxy Note 3 Android Development] Darietto:
for what i know so far, since you installed the new bootloader you can only flash the samsung 4.4.2 rom atm
[Galaxy Note 3 Android Development] piit79:
There is some confusion with device naming - hence the message "this package is for "hltexx" devices; this is a "hlte". I was getting it with TWRP 2.6.3.7. It was "fixed" (or rather "worked around") by using latest official CWM 6.0.4.6 - I can now flash the nightlies normally.

However, if you really flashed the new 4.4 bootloader you will be stuck with the leaked 4.4 stock ROM until a solution is found to support the new bootloader... You should still be able to flash the CM11, it will just not boot.
[Galaxy Note 3 Android Development] Berget:
i tried to flash the 6.0.4.6 on the older bootloader, just got stuck at the samsung logo..

i am using the leaked 4.4.2 bootloader now (with 6.0.4.6) *SAD FACE* and i have tried to flash the CM11 rom, still geting the same error.

EDIT: Are there any Devs working on a fix?
[Galaxy Note 3 Android Development] 3lastic:
Bootloader version

I am sorry but how do i get the bootloader version?

doesn't say nothing when i boot up in Bootloader,

I searched the QA but can't find it anywhere.

Appreciate the help.
[Galaxy Note 3 Android Development] Darietto:
settings-->general-->device info
[Galaxy Note 3 Android Development] 3lastic:
hehe

Sorry man !! Can't find nothing there.

I come from Sony World, havn't got hang off the Samsung yet, but is bootloader connected to the buildnumber?

So basically if i am using the Stock Polish 4.4.2 then i can't install CM?
[Galaxy Note 3 Android Development] Darietto:
correct
[Galaxy Note 3 Android Development] majorsquirrel:
On 01/20 is anyone else having an issue with their capacitive buttons no longer working? I've tried rebooting, reflashing and rebooting again. Nothing's changed. The buttons don't work at all, it's like they aren't even there. Strangely, when I hold down the left key, google now pops up, but that's all it does.
[Galaxy Note 3 Android Development] Ooo_Pepi:
Today I tested it, with no problem installed version of january 20th.

Touch controls work without any problem.

Thank you.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Abdulrahman91:
Were you on KitKat ? or JB ?
[Galaxy Note 3 Android Development] iRoNX:
The camera quality is very bad. The usual problem of AOSP.

Even with third-party cameras.
[Galaxy Note 3 Android Development] Yank555:
??

It's the same hardware, the base image is the same, the only difference are Samsung's fancy filters, and as a hobby photographer I can tell you those are not that good anyway, just flashy and shiny but of rather bad quality...

I use Snap (camera, filming, lockscreen cam) and ProCapture (for Panoramas, way way better than Sammy's Panorama function).

This "AOSP camera has worse image quality" is an ongoing myth.

Yes, base AOSP camera

APP

is pretty naked, has no functions, but it has no impact on hardware image quality.

Both attached pictures are panoramas I took last year with my i9300 on CM10.2 with ProCapture, one is a wine cellar with very low light. And the camera of the n9005 is at least as good as the one of the i9300.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.8-beta3 kernel.
[Galaxy Note 3 Android Development] neoKushan:
Anyone know if they've fixed the hlte/hltexx issue on the nightlies yet? I don't want to start flashing ROMs if I can't use something like CyanDelta to easily update to the next nightly, given the current state of CM on the Note3.

EDIT: Just checked the latest nightly and this is still the first line in the updater script:

assert(getprop("ro.product.device") == "hltexx" || getprop("ro.build.product") == "hltexx" || abort("This package is for \"hltexx\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

Guessing that's not correct, if I knew how to submit changes to the CM guys, I'd fix it myself.
[Galaxy Note 3 Android Development] jetbruceli:
Yeah I think the issue is this thread isnt maintain by one of the cm members. So all the input isn't going anywhere.

Normally in a cm Dev thread they want us to talk about how to improve on it.

sent from my iPhone 6s 64gb 5.7inch Super Oled screen and spen
[Galaxy Note 3 Android Development] sauron82:
Unless you're in Canada. N900W8 has an unlocked bootloader.
[Galaxy Note 3 Android Development] ki1120:
does anyone encounter periodically freeze of the device when idle?

I just bought my device and flashed the latest nightly 3 days ago, everything works fine except the device hangs about 2 times a day, at which I have to soft reset my device to get it work again.

I run it with CM official kernel.
[Galaxy Note 3 Android Development] Yank555:
Never happened to me, so I would say, not normal...

JP.
[Galaxy Note 3 Android Development] wyd4:
Does anyone know if this works with the new bootloader?

Hahaha. Just kidding.

So how are we all this evening?
[Galaxy Note 3 Android Development] jaythenut:
funny guy lol :D
[Galaxy Note 3 Android Development] johanveld:
For me its morning :good:

But a why are thare not any changes to http://review.cyanogenmod.org/#/q/p...device_samsung_hlte-common+branch:cm-11.0,n,z

At first i coud follow what the devs did but the last days i cant see any comment/changes the made.

Or is this a stupid question?

sorry for my english
[Galaxy Note 3 Android Development] jisoo:
I think (and please correct me if I'm wrong) they are trying to put together a good system to support the different bootloaders and radios from a unified build, but the code is not quite ready to be released yet
[Galaxy Note 3 Android Development] zap117:
the return?

soo does the "blue" mean its about to happen ? and all the suns ? http://jenkins.cyanogenmod.com/
[Galaxy Note 3 Android Development] skadude66:
Nope.. Need to take a look here: http://jenkins.cyanogenmod.com/job/android/ around 7am EST or so, and the HTLEXX build starts around then, you can see if it'll build or fail (has failed since 01-30-2014). I think this is the key commit that we need to see merged: http://review.cyanogenmod.org/#/c/58815/
[Galaxy Note 3 Android Development] jisoo:
I wish there was a way to get some clarity on this without bugging the devs. I would anyway do my own build but it's difficult to figure out which commits are needed for the kk bootloader...
[Galaxy Note 3 Android Development] skadude66:
Haha, yeah I know what you mean. Too complicated for me to understand! I wonder where they're at with the commits, wonder if they hit a wall or something.
[Galaxy Note 3 Android Development] jisoo:
There was an update from Steve Kondik	(cyanogen himself) saying "Just finishing up the last bit of stuff (new GPS) and the new branches should be ready to go." I know we shouldn't put our hopes up just yet, but I can't help myself from hoping the new nightlies (with kk bootloader support) are not too far away now.

The devs are doing an amazing job, and really can't be thanked enough for their efforts.
[Galaxy Note 3 Android Development] ki1120:
will the version of baseband and bootloader affect the usability of current CM11?

I am on MJ7, but I found there is always some bug regarding the stability.

Should I upgrade to ML3?

Thanks.
[Galaxy Note 3 Android Development] jisoo:
No one really knows the answer to that, I guess. I would suggest wait and see until the new builds start arriving and then checking again.
[Galaxy Note 3 Android Development] ki1120:
may I know what's the baseband you're using?

Thanks.
[Galaxy Note 3 Android Development] ouankou:
Since the code is different in each region, check the Android version of your ML3 firmware first.

If you would like to use CM11 right now, do not touch any official Samsung 4.4 rom. You can upgrade your firmware to the latest 4.3 version with odin if you want. Then flash the custom recovery and CM11 related rom. Currently there is no available CM11 rom for the new official 4.4 firmware.
[Galaxy Note 3 Android Development] jisoo:
N900KKKUENAC (it's one of the Korean variants). I don't think the baseband matters, though.
[Galaxy Note 3 Android Development] Drizzy xS:
Where did you see this update from steve?
[Galaxy Note 3 Android Development] jisoo:
Last comment here: http://review.cyanogenmod.org/#/c/58815/
[Galaxy Note 3 Android Development] Drizzy xS:
Ah good old Steve looks like we're close ?
[Galaxy Note 3 Android Development] Clone1B:
All looking nice so far, but my phone seems to be running a lot warmer now. Slightly worried it might affect battery life by a lot
[Galaxy Note 3 Android Development] skadude66:
Ah that's great news!!
[Galaxy Note 3 Android Development] PeterGuru:
Idea for change ...

I have an idea, although, it's easy for me to say because I'm in Canada, and don't have to worry about the dreaded AT&T.

How about we completely STOP developing for AT&T products. Yes, simply stop. Perhaps, when that happens, and people move away from buying AT&T phone products, AT&T may finally stop all the silliness with locked bootloaders. Like many American companies, they believe so deeply that they are the be-all and end-all of the universe, that they are above and beyond the intellectual capacity of their minions (customers).

It's an unfortunate side effect of American culture, the idea that THEY are the best at everything, when the opposite is often the case.

Just stop developing for AT&T. Period! End of story.

Just sayin'

Peter

Addendum: AT&T reminds me of Apple, with their staunch, dictatorial rules. While I admit that Apple produces, perhaps, the best computer and cell phone products in the world, I have never, and will never, buy their products ... entirely because of their self-serving attitude towards their customers. To me, Apple, and AT&T to a slightly lesser degree, is the North Korea of the business world: They tell you what you want, when you will have it, how you will use it, and insist that you do exactly what they say ... otherwise, you can starve to death.

Addendum 2: Yes, as you can see from my signature, I've gone back to stock. I began getting an increasing number of glitches with CM11-20140130, and I simply can't afford the time to fix the problems myself. So, even for me, the whole AT&T locked bootloader issue has a negative affect on my daily life, and my phone is incredibly important to my business. So, back to Samsung for now. At least I know it works.
[Galaxy Note 3 Android Development] jetbruceli:
The bootloader is locked on the international one. Well at least it prevents us downgrading. So it's not just at&t

dont forget the thanks button if I helped out!!
[Galaxy Note 3 Android Development] neoKushan:
If we stop, it's like admitting to them that we're content with their practices. It's like admitting defeat. Only by challenging their stupid behaviour can we ever hope to change it.

This is what hacking is truly all about.
[Galaxy Note 3 Android Development] PeterGuru:
Good point!

Good point!

Boycotts can also work. Sadly, though, very few of us will ever boycott anything, regardless of the circumstances.

Peter
[Galaxy Note 3 Android Development] radicalisto:
Very true, mainly because so many companies have the monopoly that people cannot afford to boycott. I've only ever seen one successful boycott in my life and it's still upheld in Liverpool 20 years later. It was a boycott of the UK Newspaper THE SUN. If you fancy a read, (off topic I know) it's HERE
[Galaxy Note 3 Android Development] neoKushan:
Boycotts certainly can work, but AT&T seem to have a pretty good stranglehold in a pretty crappy market (In the US). It'll take more than boycotting to change the whole industry. For now, though, we don't relent! :D

EDIT: Can confirm what radicalisto said, I lived in Liverpool for years and not a single shop there will sell The Sun.
[Galaxy Note 3 Android Development] Yank555:
There's also one small detail we may be missing here ... for a

development

boycott.

How many of actual users do root their device ?

A tiny percentage (maybe a growing one, I don't know, I'm too deep into it to be objective), but likely small enough that they wouldn't really even notice if only "rooting" users stopped buying their stuff.

That's like pesting in general against for example Samsung (and I do that ... a lot these days ... if I think about it), but we are an itsy tiny group of users, so selling like 60 million devices or 59 million devices to comsumers, but gain a government contract about a big amount of additional devices because of sth. like Knox stuff at the price of potentially loosing some of these "pesty" 1 million "rooting" users, commercially speaking, they will and should go for the government contract, even if that's not where I'd like to see them go, that's what pays their salaries.

So we are pretty much at their merci, all of them, and we will have to flock from one brand to the next, sticking with whoever is dev friendlier at the given moment.

And that for now sure is not Samsung... but who is ... except Nexus devices (if these don't die out on us in the next few years as some rumors say) ?

JP.
[Galaxy Note 3 Android Development] jaythenut:
Or ever one can start buying htc that might **** them up lol that's what my next phone is going to be had enough of Samsung
[Galaxy Note 3 Android Development] radicalisto:
Had the HTC One, the odd time I regret switching to the Note 3.. but screen size won it for me.

[MENTION=2033478]Yank555[/MENTION] your points are pretty much 100% accurate, we the rooters/devs/modders are a teeny tiny minority. Will Samsung become a victim of their own success like HTC did? Apple appear to be dropping (a little) HTC obviously struggling, Samsung getting way too big for their boots, who else is left? -- As for your Nexus comment, I too myself have wondered if and when Google will get bored of subsidising the Nexus line.. and want to move on (but they did sell Motorola to Lenovo, but I suspect the Motorola acquisition was just for Patents)
[Galaxy Note 3 Android Development] Moonystorm:
My Note was my first upgrade after the Gnex, what kept me from the N5 pretty much just the battery, ram, and Memory.

What pulled me was the notes huge screen (which feels small after a week.) and the stylus which is brilliant for drawing. I'm overall happy, but ashamed for not reading the deal about the new bootloader in time, Well, my bad. I'm a patient Guy. Think, if HTC did the next nexus! I'd get one. Otherwise i might Jump onto the LG boat, who knows... Its up to us users, what exactly we choose.
[Galaxy Note 3 Android Development] ReNeH99:
i also changed from samsung to htc (note 1 -> htc one), and i was p***ed of from the s-off things more than from samsung knox.. and that damn buildquality.. i had 4 htc ones, everyone had a bad buildquality. then i gived up and bought the note 3.
[Galaxy Note 3 Android Development] Moonystorm:
My Roomate got a ONE in silver at BASE on contract, and it still works fine and looks brilliant, but it might be a Bad batch of Units you had.

The one is by now Outdated too, When i had to get a new Phone my teacher told me to stay away from the One due to its outdated hardware,

He actually kept me from the Nexus 5 too, and said i should get an G2 because its basically an unstripped N5, But all after all, the note is a fine device. Brilliant Hardware.

-Moon
[Galaxy Note 3 Android Development] Yank555:
I'd say now they found a buyer for Moto while keeping the interesting patents makes this one pretty obvious ;)

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu AOSP v0.91-beta3 kernel.
[Galaxy Note 3 Android Development] ram9200:
Check my probam thread on sprint there is a unified build there and yes it works on kk bootloader

http://d-h.st/IZs

here you go

dont know how well it works!
[Galaxy Note 3 Android Development] radicalisto:
:good: - I'm just looking at it myself now! :highfive:
[Galaxy Note 3 Android Development] GigabitEthernet:
Sorry, probably a stupid question, but I assume this won't work on the N9005?
[Galaxy Note 3 Android Development] radicalisto:
Hmm -- Noob Q from me, we cannot adapt this for the N9005 correct? have to wait for it to be patched in properly, OR can we edit it slightly to work? -- Not 100% on CM dev stuff so wouldn't want to hazard a guess.
[Galaxy Note 3 Android Development] ram9200:
you dont't have an exynos model right? should work if you have qcom (hltexx)