Search results

Yup! Behind the scene I've been testing a new build. But I'm on holiday right know so i have to do the development while the gf is not looking. :D As always, (free) time is the limiting factor here. I'm also bandwidth impaired right now otherwise I'd have shared this build with all of you.

Just wanted to let everybody know that I'm still alive. It's just that I can't spend too much time on the port right now, because I've been neglecting my gf enough lately and she deserves some more attention :P When I have the time to spend I want to focus on these things: - Merge in all the...

Just wanted to let everybody know that I'm still alive. It's just that I can't spend too much time on the port right now, because I've been neglecting my gf enough lately and she deserves some more attention :P

Good news - I have a workaround Bad news - It's a workaround My guess is - CyanogenMod changed something in the way the device is set up on first boot which brakes our note 4. I haven't figured out what exactly it is, but I saw that the makefs binary was changed so go figure. I don't have the...

So - I seem to be able to reproduce the issue now. Weirdly though, when I flashed a new ramdisk to enable unsecured ADB debugging the device booted. The good news is - I can reproduce it. So I can finally get to the core of the issue. when I flash the original ramdisk back the device still...

Did you install any gapps? And if so - which?

boot loop as in stuck on boot animation? Or as in rebooting the entire time? How exactly do you fully wipe? Which recovery did you use? Can you pull a logcat during bootup?

Thanks. I'll add them to the devb.

Gekkehenkie11 and fattire have been looking at it recently. It might be added soon. Might be. :)

Thanks for the feedback and support. There is still enough to solve. But is getting better and better :)

The major issues right now are thermal and battery issues. Sometimes the device can soft reboot. But it doesn't get warm enough to damage the device.

New build: 2014-12-29 build Changes: Reverted some thermal limit values. They restricted NAND access and made the device too sluggish too boot sometimes. This will solve the issues people had with the previous build. These thermal problem will have to be adressed via another way. Merged in...

I try to pull from CyanogenMod's repo's as often as possible. So this is using the bleeding edge. AOSP 5.0.2

I believe I know what is causing the issues with the latest build. The boardconfig changed, and I was behind pulling from some repo's. To fix it I have to nuke my build environment and rebuild everything again. This usually takes 6 hours which means it will finish when I'm in bed. Expect a new...

Hey Gekkehenkie, That latest blob file that has been more compatible for some of the devices - where do the blobs originate from?

Thanks for the suggestion. I'll add this later.

For the people having issues flashing the latest build, this is the previous one from the 25th: https://mega.co.nz/#!D0FEFQ6Y!fihYU8Lu-jQl7Fr7SqnBOv5SIUrX0dSUY1sbqZXbdto Give that one a shot and let me know if this makes any difference. Yes.

Bootloops only happen if you don't wipe your device before flashing.

This latest build contains changes to make the Samsung smart cover function. Which makes the device turn on in my pocket. This is an issue that needs to be addressed soon. Welcome to the world of alpha builds :)

New build available! I've created a ROM thread. Please use this new thread for ROM questions, and focus in this current thread on R&D work only! http://forum.xda-developers.com/note-4/snapdragon-dev/unofficial-cm-12-0-910f-note-4-trltexx-t2987412

[ROM][N910F] Unofficial CM-12.0 for 910F Note 4. (trltexx) CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone. #include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices...

Last night I had a reboot during a titanium backup batch. That was caused by overheating. Should be fixed in the next build due to lower thermal limit values.

Samsung kernel source seems to be missing some thermal limit values, that the Shamu source (also Snapdragon 805) does have. So we put those values in place for our device as well (example; https://github.com/jaapp/android_kernel_samsung_trltexx/commit/314dcbb69e2c522be6ca6ec7846f5c8b56742281)...

Only thing is that I'd expect to have the same trouble on my device as well.. since I now use Slayher his common proprietary blobs exclusively

Do these blobs fix the issue? https://mega.co.nz/#!HYQhwDxC!BKFcKucAWmg46bdD06HA7rDaeuN7xS_gAoJG1mXEcz0 Just flash it after you flash my build.

Pretty weird. The only issue I have is the camera becoming unavailable and reduced battery life. Are these reboots reproducible? Or are they completely random? How often do you have them? Is it during screen on?

the build form the 17th? That's gekkehenkies build correct? He was using the N910T kernel. My build is based on the N910F kernel. Nope not true.

The last couple of days have been very busy for me, so it has been hard to keep up with this thread. I see some people have issues with reboots - I don't experience those. Are your sure that you are using the build from the 25th and you have a N910F and not another phone? Right now I'm merging...

Have you tried philz touch? Thats what i use.

New build: https://mega.co.nz/#!D0FEFQ6Y!fihYU8Lu-jQl7Fr7SqnBOv5SIUrX0dSUY1sbqZXbdto It should no longer burn a hole in your pocket or hands. And the blank banking apps / lastpass / drm video etc. issue is resolved. Have fun! You can dirty flash this as long as your previous rom was CM 12 as well.

Sorry that you are having problems. But I always test the roms I release so I know they are correct. tomorrow I'll release a new build - if that one fails you as well please let me know.

blank banking apps / lastpass / DRM video issue will be solved in the next build :) Thanks Slayher!

Allen his fix is in the next build :) https://github.com/jaapp/android_kernel_samsung_trltexx/commit/abe9b4751d7ce661ff2bf40362898653162313dc

Really eager to hear about it! ---------- Post added at 02:35 PM ---------- Previous post was at 02:18 PM ---------- yes, that is a known issue. Fattire / slayher fixed it already. Next time I see them online on IRC i'll try to find out how they did it :)

There is really no reason to fear overheating due to charging. I leave mine plugged in all night, it doesn't break a sweat. It's high CPU usage during screen on time that is heating the device. edit: The device can get warm when fast charging, but this is normal behaviour. Stock does this as well.

That seems like a nice temporary solution. Will give it a try.

The latest build has a new feature. It doubles as a pocket warmer :D ....

I have no idea dude :D Try it out and let me know if your phone starts smoking. It's definitely not exynos compatible.

New build: https://mega.co.nz/#!z5MyBJwY!2w29ioFtJEVuCjE-DpMxHXbxIpxNbI5UKlD1PlsXJkE Now with a working vibrator and perhaps a better RIL :) Merry Christmas!!! :laugh: Made possible by Slayher, Fattire and Gekkehenkie11, and you! ---------- Post added at 05:25 PM ---------- Previous post...

fattire - Could you show me how you fixed the blank banking apps problem? I can't find any commit that relates to it. In the N901T build changelog it is listed that build 2014-12-20 fixes the issue.

Strange, It shows the right location+carrier for me. ---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ---------- Banking apps don't seem to work. I think I saw a commit about that somewhere... ---------- Post added at 01:50 PM ---------- Previous post was at 01:33 PM...

I'll be eyeballing your repo's and pick it up asap :) ---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ---------- We need the build number, otherwise it's unclear what version you are using. But keep these messages coming. In the short term I'll be focussing on...

Sounds pretty normal to me?

YES! Finally a guide how to extract those system.dat files! http://www.xda-developers.com/android/easily-extract-lollipop-dat-files/ ---------- Post added at 09:14 AM ---------- Previous post was at 09:14 AM ---------- Thansk! I'll apply that now and rebuild.

So there still are some changes in Gekkehenkie11 build and mine. Primarily the vibrator stuff. I believe these changes are cause by Gekkehenkie shuffling blobs around. His are based around Slayher his t-mobile blobs, and then he has been manually replacing them on his phone with ano dev his...

Haha - I hadn't pulled your commit yet so the next release of mine will introduce an even funnier cursor :laugh: :p

Just look here and pick a bundle that suits you: http://forum.xda-developers.com/showthread.php?t=2397942

the newest build: https://mega.co.nz/#!61d3QArJ!pdoA6VFaoO7pilOU2swwlBvROjn4cDyyirbT18Wnl6M with working camera :) . No need to wipe your device if you come from my previous buid. Still no working viberator. I'll look at that next.

something is wrong with a binary I use E/HAL ( 328): dlopen failed: could not load library "libqc-opt.so" needed by "camera.vendor.apq8084.so"; caused by cannot locate symbol "utext_openUChars_51" referenced by "libqc-opt.so"... I guess I need another libqc-opt.so (or...

The s-pen works. It shows a funny cursor :) You need to have this in your roomservice.xml for it to work I believe: <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" /> ---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM...