Unofficial CM13.0 910F/G - NEW
- Thread starter agsola
- Start date
-
- Tags
- 910f cm13 cyanogenmod note 4
I am confused, which build have new kernel changes?? agsola's build or jef_00's build??
Sent from my SM-N910G using Tapatalk
Just to let you guys know if AudioFX isnt functioning for now or you dont like the equalizer or so, perhaps you might wanna try this: http://xdaforums.com/google-nexus-5/themes-apps/equalizer-dsp-manager-lollipop-versions-t3106546
Its DSP Manager and it's compatible with CM13 too
Give it a try and let me know if theres any problem
Enjoy
Its DSP Manager and it's compatible with CM13 too
Give it a try and let me know if theres any problem
Enjoy
Mine.
What I don't know is whether @jef_00's build is completely using the same sources as I am, or just some of them. So maybe there are a few other little differences.
@agsola Things are looking good using your latest build (cm-13.0-20160122-UNOFFICIAL-trltexx) and open_gapps-arm-6.0-micro-20160123 , full factory reset, bootloader/modem COJ3. Seems to be approaching what I experience with 12.1 and the 5.1.1 emotion kernel. nice
i don't use bluetooth or the camera, so have no comments on those.... very little battery drain overnight which is the biggest concern for me since i use my phone as an alarm clock and don't want it to die in the middle of the night... is there anything i can test? is there anything I should be looking for with the 2 core kernel option?
i don't use bluetooth or the camera, so have no comments on those.... very little battery drain overnight which is the biggest concern for me since i use my phone as an alarm clock and don't want it to die in the middle of the night... is there anything i can test? is there anything I should be looking for with the 2 core kernel option?
Last edited:
basically is there any worse battery usage Is there any better performance that you notice?
20160122
I thought I'd share my experience with agsola's 20160122 (two cores online enabled) so far, though it's too early to draw any kind of conclusion from it.
I've been running this since yesterday morning and left the phone off charge overnight. It lost 10% battery over 8 hours. I don't think this is more than normal, but if it is, it is only very marginally more. At any rate, I don't have a comparison against the same build without the two cores online, so it's anecdotal at best. I think general performance is slightly better, but again, could be a bit of placebo playing in.
@agsola: From what I can see the changes for enabling two cores online is not in your repo, is that right? I built your repo locally yesterday morning so if not it should be an exact match apart from those changes. I'm newbie at building CM though and I haven't tried this build myself yet. I will try to flash it later to check overnight usage for a more direct comparison.
I thought I'd share my experience with agsola's 20160122 (two cores online enabled) so far, though it's too early to draw any kind of conclusion from it.
I've been running this since yesterday morning and left the phone off charge overnight. It lost 10% battery over 8 hours. I don't think this is more than normal, but if it is, it is only very marginally more. At any rate, I don't have a comparison against the same build without the two cores online, so it's anecdotal at best. I think general performance is slightly better, but again, could be a bit of placebo playing in.
@agsola: From what I can see the changes for enabling two cores online is not in your repo, is that right? I built your repo locally yesterday morning so if not it should be an exact match apart from those changes. I'm newbie at building CM though and I haven't tried this build myself yet. I will try to flash it later to check overnight usage for a more direct comparison.
can you think of some reproducible test (application I can run for a set amount of time) I can do on 12.1 and 13? it's all rather subjective otherwise. for instance it seems that duolingo drains the battery a bit faster in 13 compared to 12.1 but i can't be 100% sure. idle overnight seems great though.
edit, btw, i never have sync enabled.
Last edited:
trltetmo
for anyone who requested this is a trltetmo build with the last commits from fattire but without always cpu 2 online
https://mega.nz/#!nZoBGLwY!OQ04pDbqjNy5TwPd0AtyqkwdvrOXsoOYBPC0L-XNO7I
i dont have a trltetmo so i cant test.. but it should work
for anyone who requested this is a trltetmo build with the last commits from fattire but without always cpu 2 online
https://mega.nz/#!nZoBGLwY!OQ04pDbqjNy5TwPd0AtyqkwdvrOXsoOYBPC0L-XNO7I
i dont have a trltetmo so i cant test.. but it should work
Very odd, sometimes when i power off (not restart) form the power menu i get a warning that there's an upcoming alarm and the alarmclock starts ringing. i just powered off with the phone charging and now it's stuck with the charging graphic and won't boot, had to remove the battery. probably because i'm not using the recommended bootloader i guess.
...and the issue with date/time at startup/shutdown - the coreect date/time wouldnt be stored in mobile. When i restart to TWRP i've got a date around january the 1st. and time about 1 o'clock
running on 21/01 build, games sometimes get stuck on freezed image, fix is to go to multitasking and return to the game
I also get this. But only sometimes while playing "need for speed - no limits".
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
66I'VE GOT NO TIME AT ALL RIGHT NOW DUE TO PERSONAL MATTERS. IF ANYONE FEELS LIKE BEING ABLE TO TAKE THIS OVER, PLEASE, SEND ME A PM.
This is a follow up from this (http://xdaforums.com/note-4/snapdragon-dev/unofficial-cm13-0-910f-g-t3243386/post63707846).
Quite a few people asked for test driving CM13.0/Marshmallow. However since a lot of stuff was broken, we felt it didnt make much sense to put a flashable ROM out there. But a lot of progress has been made and the basic functionality (more or less) seems to work now, so I thought let's open a thread where people can dump their unofficial Cm13.0 versions for others to try.
If you want a stable version, use the official Cm12.1: http://xdaforums.com/note-4/orig-development/official-cm12-910f-910g-t3046965
This thread will be active untill we feel it's stable enough to make it official.
Notes:
Bootloader and Modem:
Make sure you are (at least) on COI3 bootloader and modem.
I recommend that you install COJ3 and COL2, since the blobs used in the latest builds are from them. To do so, install these two files:
CP_N910F_COJ3.tar --> you can find it here: https://www.androidfilehost.com/?w=files&flid=41392
BL_N910F_COL2_agsola.tar --> I didn't find it anywhere, so I packaged it and upload it here: https://mega.nz/#!JtY1gb5Y!h2AKBC_j-kHiokh9EnnS-QV00-RWszqbq95dr2s8fCI (it works on my mobile, 910F)
See the post below for instructions about how to install it.
Installation instructions: (compiled for trltexx).
1) You'll probably want to backup your existing installation with TWRP
2) Do a full factory reset
3) Flash this ROM: https://goo.gl/VKHILd (date: 2016-04-11) -- older builds below.
4) Flash gapps from opengapps: http://opengapps.org (choose 6.0 and ARM)
Update from previous build:
1) Flash ROM.
2) Restart.
Working:
- Mostly everything, including fast charging and fingerprint (though a bit buggy yet, it takes a bit to get a fingerprint added (see http://xdaforums.com/showpost.php?p=65391708&postcount=1113)).
If you want to build it yourself, @fattire wrote this wonderful tutorial: https://wiki.cyanogenmod.org/index....ild_CM_Marshmallow_for_trlte_WORK_IN_PROGRESS
Other notes:
* You guys might want to try the Marshmallow multi window mode ! Enable it in the developer options. Once enabled, go to the recent apps and press the symbol next to the X for windows you want.
* You'll probably want to enable MTP over USB by default, also in developer options
* Enable root also, again, via developer options.
Known bugs/problems
* I've seen some battery drains, not sure if they still persist, I expect they do.
* Camera a bit buggy
* Display lights up dimmed for a few seconds and goes of then. Seems to be CM13 related. Press power twice fixes the problem.
* Probably a lot more
What do we need to get out of nightly?? (by fattire)
* Most importantly, selinux must be enabled/working before this can become an official nightly. You'll notice in the settings the ROM is still running in permissive mode. It took slayher a few days to make sure everything was good selinux-wise in 12.1-- has anyone tried "setenforce 1" in a root shell to see what happens? And what happens if you take permissive out of the kernel command line? I haven't tried it yet. I'm guessing there are no selinux experts in the crowd... which I'm certainly not.... anyone want to step up and learn how all those .te files work and be willing to tweak them if necessary?-- done by @fattire
* Another thing I haven't tried-- has anyone tried to make an emergency call with the phone locked? I don't recommend anyone trying to call 911 randomly, but this seems like something someone should verify as working as well.-- tested by agsola, works.
* I am thinking that the standard across devices seems to be to move the RIL file to the -common from the device flavor directory, as @ZION959 has already done. I can do this as well but I don't want to break the xx builds... anyone have any thoughts on this?-- done
* Can anyone think of any other obstacles to a nightly build? Well, the latest source would need to be uploaded to gerrit (Review.cyanogenmod.com) for the various devices. This is something anyone can do by the way...
KEEP IN MIND THAT THIS IS STILL HIGHLY EXPERIMENTAL AND NOT MEANT TO BE A DAILY DRIVER FOR THE AVERAGE USER AT THIS POINT
XDA:DevDB Information
Unofficial CM13.0 910F/G, ROM for the Samsung Galaxy Note 4
Contributors
agsola, fattire, gekkehenkie11, slather, jef_00 (any other??)
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Beta
Created 2015-12-28
Last Updated 2016-05-2022I pushed some new stuff.
Okay, some new changes, both to the kernel and the device tree. This is all subject to further testing.
KERNEL
- Include the kernel exploit fix mentioned in my last message above.
- updated the wacom touchscreen/panel drivers for no particular reason from a newer kernel than what we have and what samsung uses.
This is on top of the cpuset support added on the 14th. I still want to bring the kernel up to date w/caf.. @ZION959 was working on that I think.
- You can now play with the blink patterns and LED notification colors in settings. Not sure if they'll be the RIGHT colors (which might require some tweaking to the liblights hal if anyone wants to play with it), but you can do it anyway.
- You can turn the charging light on/off and set the color too.
- I turned on Volte support, which I think will require heavy tweaks to our RIL to actually do anything, so this is pretty useless I THINK. But what the hell, i figured I may as well turn "config_device_volte_available" on and see what happens. Maybe someone can test it and see if it works. But probably it won't.
- Long-hold the home button for the app's menu (if it exists)
- Double-click the home button for the app's search (if it exists)
- More hardware buttons can be used to wake up the device.
- Enable the stylus gesture menu. For some reason tho it doesn't work. Not sure why, but this is the reason I updated the wacom drivers in the kernel, and unfortunately it didn't help. I wrote a little more in the commit description.
- Build the snap camera. This worked on an earlier build, but strangely my most recent build didn't build, but maybe that was something CM changed. Cuz it worked before I'm leaving it and we can fix it if needed.
- changes to vold to be more like some other devices I've seen that may address some issues people were having. It may not.
- Enable samsung doze and turn on framework doze support. If I understand it correctly, this will mean you kinda need gapps or else when your device goes to sleep it won't necessarily get some notifications it would otherwise (that come in via google cloud messaging).
- Enable cpusets which allows Android to prioritize groups of activities in groups.
- Some more tweaks to selinux policies.
- Minor other things. You can review the commit list to see what they are.
Last night I left the phone unplugged and when I woke up the power consumption had barely moved. Your results may vary tho. Builders, have at it and let me know if anything broke.21Modems, bootloader, images...
To download the right bootloader and modem, see this post:
http://xdaforums.com/note-4/general/snapdragon-note4-modem-bootloader-t3273816
(by Mussels84)
For 910G users, a compatible 5.1.1 modem is hosted here:
http://www.mediafire.com/download/he7mvjg9axmen3q/N910G_BOH4_Bootloader_Modem_5_1_1.rarBOH4 modems + bootloader in a single file.
If you need latest official version lollipop version (to get files and help with dev):
http://xdaforums.com/note-4/general/910f-official-lolipop-germany-dbt-t302950821
Yes I am working together with @Pafcholini on CM14.1 for our note 4. We have still 2 bigger issues. Fingerprint and camera are not functional. But we try to get this fixed. Only problem is that our free time is limited at the moment. So stay tuned. Maybe we can keep this device up to date for another year.
Kind regards
Crimsonthunder20Older builds links
https://goo.gl/HVN7fb (date: 2016-04-24 - New Marshmallow kernel, Bluetooth not working)
https://goo.gl/VKHILd (date: 2016-04-11)
https://goo.gl/aJvQdf (date: 2016-03-20)
https://goo.gl/ToqL1j (date: 2016-03-19)
https://goo.gl/0jn9Cq (date: 2016-03-09)
https://goo.gl/0Umf17 (date: 2016-03-06)
https://goo.gl/pnk3iy (date: 2016-02-28)
https://goo.gl/EiOH0n (date: 2016-02-27)
https://goo.gl/mF95rF (date: 2016-02-22)
https://goo.gl/7HpNSC (date: 2016-02-21) fingerprint working SELInux enforced
https://goo.gl/N9AvQ6 (date: 2016-02-18) fingerprint working, but with some drawbacks (see http://xdaforums.com/showpost.php?p=65391708&postcount=1113)
https://goo.gl/XNRqPe (date: 2016-02-13)
https://goo.gl/Hpz4nD (date: 2016-02-12)
https://goo.gl/kAsgQS (date: 2016-02-10)
https://goo.gl/14IkzH (date: 2016-02-07)
https://goo.gl/KZBD6k (date: 2016-02-02)
https://goo.gl/NVbMgh (date: 2016-01-25)
https://goo.gl/WbsqNf (date: 2016-01-23)
https://goo.gl/JHZGwO (date: 2016-01-22)
https://goo.gl/ogzh10 (date: 2016-01-21)
https://goo.gl/gvTvDg (date: 2016-01-19)
https://goo.gl/eLeAOt (date: 2016-01-17)
https://goo.gl/3kuqkb (date: 2016-01-16)
https://mega.nz/#!RkxUzZZC!s4C8pZQnIgv9iyAFwckMT0kaBzQvbvjsRIj0y7D7Cl0 (date: 2016-01-15)
https://mega.nz/#!lhJWDCSa!4cgUZocbE30fHLG5KzLyaeDUHSfIwIHTadiUk_Tg47k (date: 2016-01-12)
https://mega.nz/#!QsZGyJDb!TaXz8tEFM4YjquE0DNtDLPlpuuRhasHMJMA5VjnbTEU (date: 2016-01-07, CPUSETs now should work)
https://mega.nz/#!U9JQxRJL!YR_9G3Zv4m_-RXF2jSebAn0pH8wTovB3PJIue-J9Df8 (date: 2016-01-06, SELinux Enforced, SD fix?? --> includes this commit: http://review.cyanogenmod.org/#/c/126220/)
https://mega.nz/#!l9AnFBTR!HN8gGchJbXgg_sOO2MybO9vV7um7BnZtK_Ld7QI2MNY (date: 2016-01-05, SELinux Enforced, no SD fix??)
https://mega.nz/#!VlBhEa4R!TistCKpTPcgoJGM15AwvFYmzaY_CRs57Gt_CzW1jxaY (date: 2016-01-03, SELinux Enforced)
https://mega.nz/#!MgZ3hILJ!lwRWApA85gan2lfxhN7T9OlgHyAxeMD3_rnJIx02vPo (date: 2016-01-01, SELinux Enforced, blobs updated to COJ3 modem)
https://mega.nz/#!NlZyWKYJ!1-MD3sX2C48ojqKdXSr9WvwKjHI7phfYS3UDN6LOMNQ (date: 2015-12-31, SELinux Enforced)
https://mega.nz/#!opBQHQJK!WnmhGiF-2_Y6GjjirXqqcE5XA-QoQC5aV8IzZ_4n_-8 (date: 2015-12-29) - SELinux permissive.
