yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

This one seems to be a bit more stable than the last couple of builds. I managed to 50+ hours between crashes.

-blaine
[AT&T Samsung Galaxy Note I717] edamigo:
Looks very good. No reboots in 72 hours.

If hardware overlays were fixed it would be perfect.

Still very solid build and I use it as a daily driver. Thank you blaine.
[AT&T Samsung Galaxy Note I717] adriandday:
Maybe it's app related, or just my phone, but I've had 4-5 crashes in 24 hours. 1 was without any user input, while sitting on my desk. Another was while trying to unlock. Previous build was more stable for me at about 1-2 crashes per day.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
I've had browser-based crashes since CM-10.1.

I think the underlying OS has been nailed down fairly well. But app designers have to design for everything 4.x, and that covers a LOT of ground, especially if they have to actually maintain Gingerbread compatibility. (Disclaimer: I still use a couple of apps designed when Gingerbread was the hot new thing.)

For the record, I don't like using "stable" to describe any build that won't go at least 24 continuous hours without crashing. Because that 24 hours is only JUST BARELY stable. Especially when there are boxes out there running Linux kernels that are 1-2 years old, without a single minute of downtime in that year, and certainly no random crashes.

This 8/4 build is the first one I've built in nearly 2 months that I could reliably get 48 hours out of. And that 48 hours is almost always ended with a browser crash; either Dolphin or Firefox.

--blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

Sorry about taking so long. I've been busier than a one-legged man at an ass-kicking contest.

The ONDEMAND governor we've been using is gone. I've been using USERSPACE instead and it seems to be working.

I didn't take a microscopically close look, but I think the changes we make to get the screen flicker to go away (a la disable hardware overlays) have been integrated into the build.prop file from stock.

Lastly, I got a new headset, so we can see if the Bluetooth problems I've been having are build related.

--blaine
[AT&T Samsung Galaxy Note I717] gathithow:
Off topic:

Is posible to fix the music player bug, the delay in music player when i choose a song and forced to close the music player? Fixing this the CM 10.2 ROM would be awesome.

I tried that fix, Frankenbiker told me that solution and worked for a couple of days, now the issue is still. The music player is working and when I want to skip a section of the song, I get a 2 seconds delay before to play again. What could be?
[AT&T Samsung Galaxy Note I717] vice86:
I"ve searched and not seeing any info on this...i keep trying to flash CM11 roms but i keep getting "radio must be newer than UCMD3" error and then installation abort. My Note has UCLC5 on it..i read it wrong and flashed to that from whatever I was at before that..thinking that was the latest because of the "5" and didn't notice it was UCLC and not UCMD.

Is there a file for me to use to get a radio newer than UCMD3 for my Note?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Searching "UCMD3" in the top level of the Note forum should return multiple results for links to downloads.

I don't believe there are any newer modems, and we had to fight to get this one.

The Note 1 is two (and about to be three) product versions obsolete. I doubt AT&T even knows it exists any more. (Okay, maybe not THAT bad, but you get the idea... ;) )

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
MP3 is a streaming file type. Decoding each bit is dependent upon the bit before it. The gap you hear is the player moving through the data stream to the new point; basically it's playing the file without converting to analog, what you hear as music.

If it just hops across the data, it "loses" the ability to decode.

-blaine

(Decompressing an MP3-based music file as data takes mere seconds, at most. Converting it to the 44.1kHz audio data, then converting to analog voltage, is what takes time.)
[AT&T Samsung Galaxy Note I717] edamigo:
I also noticed "ondemand" disappearing. But build.prop still needed to be edited to eliminate flickering. I still had to set persist.hwc.mdpcomp.enable=false. It is not a big deal. I am just curious why and if your build.prop is different.
[AT&T Samsung Galaxy Note I717] vice86:
Thanks for the info..i got a link for the UCMD3 modem but it seems pointless if the CM11 rom for the Note shows "need newer than UCMD3" if there's nothing new than that for the Note. What's the deal with that?

My Note 3 took an 8 floor plunge the other day so i'm stuck with the Note again...feels like a dinosaur after being used to Note 3 phone speed.
[AT&T Samsung Galaxy Note I717] edamigo:
It says UCMD3 or newer. You just need to flash UCMD3. After that you will be able to install CM11 from this thread.
[AT&T Samsung Galaxy Note I717] gathithow:
Yeah my device cannot "decode" in "real time" so I get the famous delay. However this bug appears only in my device or is aspecific ROM issue??

I'm testing your lastest CM 11 I haven't found any issue, only I feel so bad for my battery. With CM 10.2 I get about 36 hours without plug to the wall.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

Sorry for taking so long. Still uber-busy.

The only change I made to the build.prop is for my GPS function and DPI setting. No changes required for flickering or no wallpaper on this build. Didn't notice a lot new/dramatic otherwise. I think they're FINALLY into the "nailing down bugs" stage, and out of the "look at this cool new feature!!!" stage. I'm still having regular browser crashes that take out the entire phone, and the occasional (but less common) Bluetooth crash. Given my similar experience with a near-pure AOSP Go-Phone, I think the reverse-engineered bluetooth driver is the root cause in both cases (Broadcomm drivers are not open-source, and CM doesn't have or can't get rights to the OEM in this case).

Additionally, my Note was damaged for nearly two weeks. I did get it fixed, but.....

"Note" that this is sort of a "fair warning" that these builds won't keep coming forever. I'm waiting for pricing on the new Note-4, and whether or not root is achieved. Unless there's no root forthcoming, I'll probably jump at that point.

-blaine
[AT&T Samsung Galaxy Note I717] beenkenobee:
d/l link broken.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
DevHost is having issues. It took three tries to upload. Give it a few hours and try again.

-blaine
[AT&T Samsung Galaxy Note I717] rsalib:
Still no luck. Noon PST. Were you successful uploading it?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Try this:

This should work until Dev-Host gets its act together.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
There's a new M release available last week. Anyone want a build from that branch? There's also a new bugtracker app apparently. It might help get some of the bugs fixed that I'm not qualified to fix....

-blaine
[AT&T Samsung Galaxy Note I717] rsalib:
If you do a M release, it would have to be separated from the nightlies. The M release isn't as far along as the nightlies, but it is more stable. I don't mind the nightlies. I just know for sure people are going to get them mixed up and support will go bonkers.

Your call, you are the OP.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up. Will be testing this one today. Wanted to get the Dev-Host link out there so we could test THAT, too..

Edit:

First impressions: My GPS functionality has tanked. Only sees GLONASS sats. Won't lock at all. It did this the other day, but when we had a geomagnetic storm; I attributed it to the storm (geomagnetic solar storms wreak havoc on GPS signals). I tried the trick of gently prying up the GPS antenna contacts, to no avail.

Edit2: Apparently I didn't pry the contacts up enough, again... shimmed them up with the fix on page 12 of the GPS fix thread (on page two of the general forum).

If you try to revert to an earlier build, it throws up on itself with "com.process.acore" and the phone application throwing up all over themselves, continuously, making the phone more or less unusable.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
I'm mostly gauging interest. There would be a not-inconsiderable amount of work involved in even setting up the M-release build tree, but the build itself wouldn't be any more difficult than the nightly builds.

-blaine
[AT&T Samsung Galaxy Note I717] rsalib:
I've been using this GPS fix: http://www.xda-developers.com/android/gps-lock-faster-xdatv/

I hope it helps. It obviously will not fix your hardware issue if that is what is wrong, but when you have a data connection it helps a bit.

Side Question: Has anyone noticed their MMS or Group Messaging stop working while wifi is connected?
[AT&T Samsung Galaxy Note I717] AdShea:
There might be something else wrong with this build as I couldn't dirty flash it over the 20140830 build.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
If you haven't flashed the 9/15 build first, you might try that and see if there is an issue with out-of-sequence flashing. In CM's long history, it's not unheard of...

-blaine
[AT&T Samsung Galaxy Note I717] mcernuto:
Is there a fix for the screen not turning on? Also I've been having issues with having no sound on either end on calls and have to reboot to fix??
[AT&T Samsung Galaxy Note I717] AdShea:
In the past changing to the ondemand cpufreq governor worked, but that's been removed from recent builds. I've had good luck changing to conservative (it's in the performance menu under settings), it sometimes still takes two presses but it does come on consitstently now.
[AT&T Samsung Galaxy Note I717] mcernuto:
is there anyone else having problems with no sound on calls? i am finding that after a few phone calls there is no sound on either end of the call and i have to reboot the phone to get it working again??
[AT&T Samsung Galaxy Note I717] AdShea:
I had that problem with the new hangouts trying to aswer the call as well (I use Google Voice) but I never had a reboot fix it.
[AT&T Samsung Galaxy Note I717] adriandday:
I seem to have had this issue as well. I'm not sure if it's consistent as I don't normally use VOIP. A reboot did resolve it.
[AT&T Samsung Galaxy Note I717] beenkenobee:
is this one based on m11?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Not specifically.

It's built after the 9/30/14 M-code branch, so it will have most of the fixes.

But it's still built on the nightlies main code branch.

-blaine
[AT&T Samsung Galaxy Note I717] adriandday:
I've been running it for 24 hours. Still not able to video chat with Google Hangout, but other than that, seems good. Thanks!

Adrian
[AT&T Samsung Galaxy Note I717] Sloogle_Flugelmann:
Is the speakerphone echo problem still occurring in the newer builds? Or did they fix that?
[AT&T Samsung Galaxy Note I717] adriandday:
Yes, it's still a problem.
[AT&T Samsung Galaxy Note I717] rsalib:
Dev Host is the devil. haha

Do you have a mirror?

Thank you in advance
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Working on this end... shows two folks have downloaded...

-blaine
[AT&T Samsung Galaxy Note I717] gathithow:
Hello, are you saying this is the end of this project? In a fact this device is forgotten and old but I have one and works perfect for me. I was thinking about a new project to bring Lollipop to the i717. What do you think?
[AT&T Samsung Galaxy Note I717] CGRAHAM10:
I would love to see Lolipop for the i717.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
That decision won't be made by me.

We'll just have to see what happens, whether or not we get any love "from on high."

-blaine
[AT&T Samsung Galaxy Note I717] JamieD81:
*drop kicks his note across the room*

Nope power button is still being a dink. hahaha
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

Saw a bunch of camera and Bluetooth commits that hit two days after the last build. Thought there were enough of them to warrant another build a little sooner than normal.

-blaine
[AT&T Samsung Galaxy Note I717] beenkenobee:
last two versions of this has busted the pc drivers.

pc will no longer connect to the phone thru usb.

listed as 'android' on device manager but no new drivers are found to get the connection back.

only solution so far is to load a different rom.

wierd
[AT&T Samsung Galaxy Note I717] jlpatte2:
So I'm guessing that now that I finally moved on to a note 3, that Bluetooth finally got fixed in the 4.4.4 note 1 builds...Just my luck! Gonna have to give it a try on my old note!

Sent from my awesome Note 3 n900a!
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Not really. "Broken differently" is more like it.

I doubt there's ever going to change in any meaningful way. Samsung used a proprietary, closed-source bluetooth chip, and as such any implementation by CM will, by necessity, remain problematic.

Does anyone else have problems with bluetooth terminating a call with a reboot instead of a hangup?

-blaine
[AT&T Samsung Galaxy Note I717] adriandday:
Unless I misunderstand the issue, you can still plug your phone into your computer and access files through Settings -> Storage -> ... button (top right) -> USB computer connection -> MTP check box.
[AT&T Samsung Galaxy Note I717] beenkenobee:
nope.

access is lost regardless of setting.

the pc will see the phone (it's listed as 'android' in device manager) but no acces to the phone.

load any other rom (touchwiz or cm11 based) and access is back.
[AT&T Samsung Galaxy Note I717] adriandday:
It still works on mine and I'm using the latest build from Frankenbiker connecting to a Windows 7 pro SP1 64-bit OS laptop.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

A bunch more camera commits. And a couple of tiny bits in the MSM8660 kernel tree.

Edit: one of those tiny bits in the kernel tree corrected some incorrect results from RIL queries (that is, the kernel talking to the radio).

I have no recent hard data, and its been several months since I've been in Knoxville, but I'm getting some PHENOMENAL transfer speeds; download of 20Mbit and upload of 10Mbit. I don't recall EVER getting speeds this high, even on the stock ROM. The upload of the latest build took all of 30 seconds, versus the normal 3-5 minutes.

-blaine
[AT&T Samsung Galaxy Note I717] gathithow:
Can you re-upload the file to another hosting because DevHost isn't working.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Remember, if Dev-Host is throwing fits, give it a few hours to a day and try again.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
For the record, CyanogenMod says to not look forward to regular nightlies until after the first of the month.

Given that our device is very much UNofficial, I'd not be looking to see anything for us possibly as late as Christmas.

(The inability to download 20GB of source code while on the road notwithstanding......... :D )

-blaine
[AT&T Samsung Galaxy Note I717] TeamAndroid14:
Cm 12

Will CM 12 be implemented on the device ?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

Sorry about the big gap. I built one about midmonth, and forgot to upload. It had some issues, though, so you didn't miss much. I did notice some things got moved around in the settings menus, though.

No word yet on CM12. The official word is that there won't be any "official" builds till around Christmas, possibly New Years.

They're still having some issues getting a build to finish at all, over with the Skyrocket guys, much less anything stable enough to be used as a daily driver.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Anyone else noticing an increase in reboots?

Mine rebooted three times today. I'm wondering if it's my own settings, or something deeper in the ROM?

-blaine
[AT&T Samsung Galaxy Note I717] nelson.gollarza:
Sql
[AT&T Samsung Galaxy Note I717] gathithow:
Is possible to see a Lollipop rom for the i717 until 2015?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Has anyone noticed an increase in data consumption in the last couple of months on my builds?

My own data usage has increased by 75% or so (from 4 GB/mo to 7+GB/mo), and I'm trying to figure out if its a ROM problem, an app problem, or a user problem.

-blaine
[AT&T Samsung Galaxy Note I717] adriandday:
I haven't noticed any significant data increase. I typically only monitor cellular data and it's remained consistent for me. I just had a peek at WiFi data and it was about what I would have expected. Combined about 3GB.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up.

Might be a little cleaner this time. I happened to discover that I was a couple of versions behind in the build tools. While those builds didn't generate any (out of the ordinary) errors, not using the latest build tools may have been what was introducing all the problems I was seeing in my phone.

Edit: maybe all I needed was a good wipe.......... :silly:

As a last-gasp attempt to fix things before breaking down and buying a new phone, I wiped everything (to the point of bricking the phone) and started from scratch. So far, so good.

A "Factory reset" clears personal data, but it doesn't clean up the /system and /data partitions. After a while, they get so full of crap that the phone just can't function any more. Dirty flashing is fine for a month or two, (or six!!) but eventually you need to clean house, so to speak.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Incidentally, I did get CM12 source code downloaded. Don't expect anything soon. The build issues are more than I can deal with in just a few minutes per day, meaning the problems are not trivial.

-blaine
[AT&T Samsung Galaxy Note I717] Refrigerate:
As far as data consumption, it does seem like I've been using around 25% more for the last couple of months. I had assumed it was due to changes in Gapps, because I don't think my usage patterns have changed much. I also don't think it's specific to your build because I've installed a couple of other roms this month - looking for something steadier and failing to find it - and the data rate seems about the same.

I'm having trouble getting the more recent builds to run reliably for me without getting lag-build-up and reboots. I did a format of the internal sdcard when I installed the 20141206 build (formatted each partition separately in clockworkmod), and installed as few apps as I could, but no better results. Uber kernel won't run anymore either. Those builds must not be compatible anymore.

I'll try again with the new build you posted. I'm now wondering if it's the Gapps I'm running. Historically I always used the latest PA Gapps Mini Modular package from Tkruzze, but I should probably be sticking with the ones you link to.

Which Google Apps package to you find most stable with the latest builds? Do you avoid applying Play Store updates as well?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
I was having MASSIVE lag/reboot problems. After the full wipe, things seem to be settled down a lot, with the exception of a head-scratching refusal to download apps.... not at all sure what's going on there. And what used to take up only half the 2GB of user RAM, now takes up 1.8 GB... No idea what's going on.

Note that the latest version of CWM-Touch was NOT formatting nor wiping my phone, even though it said it was. I had to jump through some hoops to get it truly wiped. You may have to downgrade your CWM to get it to work right.

I've never had much luck with the stripped-down versions of GApps. And all the play store (and other google app) updates happen without my even knowing when. The only one I care about really is Maps; the last 6.x version has always been better for me, personally, than the newer ones.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Note to all:

If Dev-host is giving you fits and making you try to install a "download manager"

DO NOT DOWNLOAD THE FILE!!!

I've submitted a support ticket to see what's going on.

-blaine
[AT&T Samsung Galaxy Note I717] gathithow:
Thank you for post a warning, I don't know why Devhost does that.

What do you think? An app test or Malware?

Can you choose another honting?
[AT&T Samsung Galaxy Note I717] Refrigerate:
It still looks like a working link is available at the Dev-Host site. As they've been doing for a while, they just try to confuse you about which link will send you the actual file:

Clicking the top, "Download" box sends you to an Xtendmedia site to jump through hoops. Don't know if it eventually gives you the download or not.

Clicking the lower, "Download Now" image links to a download of the ROM zip file, as normal.

Unless there's something else hiding in that .zip file, that's what I'm seeing.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
The size of the ROM is 221 MB.

If the filesize it asks you to save is anything else, the link has been compromised.

-blaine
[AT&T Samsung Galaxy Note I717] Refrigerate:
I've been up and running on the 20141222 build for a couple of days now with no reboots or any real lag build-up. I used the same sdcard format process and the same GApps package as I did with the last build, so as far as I can tell it's really just a more stable release.

I thought an sdcard format failure might have been causing me issues after hearing your experience, but it turns out it was working fine. I fired up ADB for the first time in a couple of years to confirm that the partitions were being cleared, and no problem there. I'm still using the touch version of ClockworkMod Recovery v6.0.4.3. I'm sure that's old enough that any current formatting problems weren't introduced yet.

So far battery seems to be draining a bit faster than in past, but if I can cope with a couple of charges a day, I'm sure I'll stick with it. I really prefer how clean this ROM is compared to the other CM flavours floating around.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Good to hear it's working for you.

If your battery is more than a year old, spend the $6 for the 2750 mAH RavPower replacement. It's worth it.

-blaine
[AT&T Samsung Galaxy Note I717] TeamAndroid14:
Will you be updating cm 11 to cm 12 ?
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Not any time soon. Getting CM12 to compile for a non-supported device is a non-trivial task that I currently don't have sufficient time for.

Note that there are no nightlies for ANY device currently.

Jumping from Ice Cream Sandwich to Jelly Bean to Kit Kat wasn't really much of a jump. They all shared the same 4.x.x version base (and the same 3.x.x kernel).

Lollipop goes to 5.x.x, and that means a jump in kernel version (3.x.x to 4.x.x) and, like the GB to ICS kernel jump, that's not trivial.

They're having to re-write the code from the ground up.

-blaine
[AT&T Samsung Galaxy Note I717] JamieD81:
No such kernel bump as Linux is still building on the 3.x.x kernel version, even the Nexus 6 is behind on 3.10.x when 3.17.x is newest.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Say what???

So all this brouhaha is nothing more than complicated window dressing??

*rolls eyes*

All this for a security model that very few of us here on XDA neither need nor want (or so I've always presumed)....

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
New build up

This will be the last build for a while. They've officially gone to once-weekly builds on CM11, and the changelog for the Skyrocket hasn't had anything more than APN updates in nearly a month.

I'll do another build when they announce another M build.

-blaine
[AT&T Samsung Galaxy Note I717] beenkenobee:
the link is hosed.

edit: never mind...clicking on the forum link the second time worked.

the first time, the d/l link was an .exe file...second time, it was the correct .zip file ...odd.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Yeah, apparently they're trying to monetize their download process... :(

In any case, it looks like I goofed on that build. The kernel compile date is still 01/02.

I'll try to get a fresh build this weekend.

-blaine
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Here's a fresh build.

-blaine