This is a dev thread for Cyanogenmod 12 for golfu. I finally got the time to update repos and push all my work on CM12 to HtcLegacy.
Three repositories are relevant for golfu:
kernel
device tree
vendor tree
Sync the repository
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/HtcLegacy/local_manifest/cm-12.0/local_manifest.xml
repo sync
apply patches
Code:
chmod 775 patches.sh
./patches.sh
and build
Code:
source build/envsetup.sh
brunch -jx cm_golfu-userdebug
ROM builds and boots sucessfully. However, there are bugs:
- no bootanimation
- RIL is not working - linker has permission problems with libhtc_ril.so, not sure what can be done about that and how it is working for pico
- Camera not working
- Bluetooth turns on, but not working
- Headphones do not work
and ROM will reboot after a while. Any contribution is welcome, as my time to work on device is limited. Thanks to KirmaniArslan for his work on common tree, which helped alot.
h1gh1 said:
- RIL is not working - linker has permission problems with libhtc_ril.so, not sure what can be done about that and how it is working for pico
Click to expand...
Click to collapse
Is SELinux permissive in pico build?
Have you tried to use "androidboot.write_protect=0" before "androidboot.selinux=permissive" like in MotoG Permissive SELinux?
kodirovshchik said:
Is SELinux permissive in pico build?
Have you tried to use "androidboot.write_protect=0" before "androidboot.selinux=permissive" like in MotoG Permissive SELinux?
Click to expand...
Click to collapse
Not really sure what mode it is in on pico, KirmaniArslan was not clear on that. An interesting switch...
h1gh1 said:
Not really sure what mode it is in on pico, KirmaniArslan was not clear on that. An interesting switch...
Click to expand...
Click to collapse
Well... if he has terminal in his current build "getenforce" will return SElinux mode. And if we can trust this two guys from galaxyace thread, CM12 can be switched to permissive mode.
upd: one more question. here is some fixed SElinux policies for motog i was thinking maybe we missed something. but i cant find them. where is our policies for selinux?
kodirovshchik said:
Well... if he has terminal in his current build "getenforce" will return SElinux mode. And if we can trust this two guys from galaxyace thread, CM12 can be switched to permissive mode.
upd: one more question. here is some fixed SElinux policies for motog i was thinking maybe we missed something. but i cant find them. where is our policies for selinux?
Click to expand...
Click to collapse
SELinux policies are defined in .mk files - we use qualcomm predefined policies.
here my boot everything works except wifi and bt.
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
So glad for you. If you found a way to fix something, github links are up.
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
Great ! I've tested it, and it's truth !
But like @h1gh1 meant : It will be better if you share your work on github
boot.img for cm12 golfu
zvox said:
here my boot everything works except wifi and bt.
Click to expand...
Click to collapse
thanks, i have tested the boot.img works well
Now, someone please help fix the rest Bugs
i had no sim card detected like in the images in the attachment
LINCOLINE1 said:
thanks, i have tested the boot.img works well
Now, someone please help fix the rest Bugs
i had no sim card detected like in the images in the attachment
Click to expand...
Click to collapse
RIL is not working. It's not working in my build, not sure about this boot.img, but if you flashed it, it has the same problem. SDCard and Wifi are working, as I said. But I am going to ask politely not to put any downloads here - all the development is public, and if someone wants to contribute, he can fork or create a pull request. Uploading boot.img with almost no information makes no sense to me.
h1gh1 said:
RIL is not working. It's not working in my build, not sure about this boot.img, but if you flashed it, it has the same problem. SDCard and Wifi are working, as I said. But I am going to ask politely not to put any downloads here - all the development is public, and if someone wants to contribute, he can fork or create a pull request. Uploading boot.img with almost no information makes no sense to me.
Click to expand...
Click to collapse
I agree
(RIL works fine for me with this particular boot.img)
i used ION kernel for my first build.
zvox said:
i used ION kernel for my first build.
Click to expand...
Click to collapse
That is not much info. Link to the source?
ION pico kernel
high1/android_kernel_htc_pico
zvox said:
ION pico kernel
high1/android_kernel_htc_pico
Click to expand...
Click to collapse
As I suspected, enforcing SELinux is the problem...
h1gh1 said:
As I suspected, enforcing SELinux is the problem...
Click to expand...
Click to collapse
Did you have the time to try my fix ?
Narudgi said:
Did you have the time to try my fix ?
Click to expand...
Click to collapse
No, but I found a proper fix later.
https://github.com/psndna88/AGNI-pureSTOCK/commit/3c530c181086a1caaafb57f86c5480c895c598b7
h1gh1 said:
No, but I found a proper fix later.
https://github.com/psndna88/AGNI-pureSTOCK/commit/3c530c181086a1caaafb57f86c5480c895c598b7
Click to expand...
Click to collapse
It will be better with that
i have done a new build. ( ION kernel like always )
everything works except bt
enforcing SELinux doesnt work ( and wifi gone )
Related
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
acerbix said:
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
Click to expand...
Click to collapse
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
+1 it's a good one and is one of my references too.
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
+1. Great recommendation. Just used it to complete my first build.
Sent from my MB860 using XDA App
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
acerbix said:
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
Click to expand...
Click to collapse
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info - trying it now.
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
acerbix said:
Thanks so much for the info - trying it now.
Click to expand...
Click to collapse
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
ghost_og said:
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
Click to expand...
Click to collapse
Oh okay - I thought I must be doing something stupid so I PM'd you last night rather than post here. So we all can get trackpad working in the kang but not device setting/lock/unlock
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
I tried replacing default.xml in .repo with the one in Atrix dev git repository, and then pulling down the code. That lead to multiple build failure, so I am assuming hte changes in the atrix dev github are not synced with the changes upstream coz vanilla cyanogenmod builds fine.
I am not even getting the "Device Settings" option that shows up in the weekly build, though the trackpad works fine. I'll try looking at the Settings.apk code to see if there is something I am missing.
cmkoj: Do you have a local_manifest.xml that works and gives you a good build? Open to sharing that?
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Right now, I'd settle for one that works for building. I manually overlay files, so that will definitely be easier
t.s.eliot said:
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
Click to expand...
Click to collapse
Lets know if you get it working I'm building too [clobber build just for the heck of it - will keep you posted]
Thanks a ton, cmkoj for all the help/pointers!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
ghost_og said:
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
Click to expand...
Click to collapse
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
acerbix said:
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
Click to expand...
Click to collapse
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
ghost_og said:
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
Click to expand...
Click to collapse
ye i forgot to mention that one lol, i thought its in the fingerprint build though. for my use i manually git cloned the vendor_motorola repo into /working_dir/vendor/ but havent had any luck. regarding the kernel afaik if you put the additional repos into your local_manifest.xml it should use the kernel from there (if one is available). but i dont really think the kernel is needed to be changed, since on my builds i had the authentec.truesuite (or whatever the process for fp is called) running, only the fp unlock/device option were missing (there is a Fingerprintsomething.apk in the vendor repo of atrix dev team that i have had pulled in and built with but it didnt work, so yes im slowly giving up (second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
as for the local_manifest.xml it should look like this http://pastebin.com/ccvVi2k9 for building the gb (that is with nav functioning fp but no unlock) if you want to get unlock to work you need to probably put in the other ones aswell (just by copying the <project path="device/motorola/olympus"
name="Atrix-Dev-Team/android_device_motorola_olympus.git"
remote="gh"
revision="gingerbread"/>
part and changing the name to appropriate and teh revision in all to fingerprint)
thanks go to fattire from the nook color forums who thought me how to make and edit these local_manifest.xml files and i used his file as a template for mine aswell.
i have to admit it im slowly sick of not being able to build one with working fp =/
Guys, see here for what directories to be pulled from atrix-dev-team github vs what to be kept in original CM7:
https://github.com/Atrix-Dev-Team/android/blob/gingerbread/default.xml
crnkoj said:
(second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
Click to expand...
Click to collapse
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
Another workaround is to add the following remote definition:
Code:
<remote name="github-https"
fetch="https://github.com/" />
Then change the project definition to:
Code:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https"/>
Once things are back to normal, you can remove the additional remote, and restore the original manifest.
Click to expand...
Click to collapse
It was provided in the comments section here.
ghost_og said:
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
It was provided in the comments section here.
Click to expand...
Click to collapse
yes thanks, lol, i knew about the fix and had the first part of it done with changing to https, but forgot about the second part, idiot i...
anyhow i resynced and am building now on the other pc with this local manifest http://paste.pocoo.org/show/534837/
THIS THREAD IS WIP & FOR DEVELOPERS ONLY !
Technical information with sources & binaries is in post #2. It includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems with logs.
Click to expand...
Click to collapse
What is kexec?--------------------------------------------------------------------------------------------------------
kexec or kernel execution is a module/mechanism of the kernel that allows live/hot booting of a new/custom kernel "over" the currently running kernel. For more info, read the useful threads/links bellow.
kexec could be used to load a custom kernel into memory & yes, we'll then be able to install AOSP ROMs or in general run a custom kernel compatible with our device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updates:--------------------------------------------------------------------------------------------------------
[09/01/2014]:
kexec module has been successfully patched & loaded/inserted into both NC2 & NC4 stock kernels. Now, I'm working on compiling/loading a guest kernel & fixing possible problems/bugs.
Click to expand...
Click to collapse
[08/31/2014]:
Two versions of HLTEVZW KK kernel have been compiled from source: one uses the default configurations & the 2nd adds custom capabilities & kexec boot options. Moreover, kexec-tools & module have been cross-compiled. Now, I'm working on patches for kexec module & guest kernel (the hardest part).
Click to expand...
Click to collapse
[08/01/2014]:
I've successfully flashed a custom kernel on my device. This trips knox flag & isn't 100% related to kexec, but it has the same objective (loading custom kernel on the locked-bootloader devices). However, the bootloader makes security check & blocks the installed kernel with the "unauthorized software by VZW" warning. Then, I tried to patch the bootloader to remove this security check, but my device was HARD BRICKED. Now, I've created a General thread for how to recover from a HARD BRICK. This is promising info for testing bootloader exploits.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Status
--------------------------------------------------------------------------------------------------------
Supported NC2 & NC4 kernels
Working kexec-tools
Loaded kexec module
WIP kexec/guest kernel
Click to expand...
Click to collapse
Thanks to / Credits:
--------------------------------------------------------------------------------------------------------
@sextape - for the leaked NC2 firmware
@Hashcode - for his great work on kernel/recovery
...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
XDA:DevDB Information
KEXEC, Kernel for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr, CalcProgrammer1, ryanbg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-07-11
Last Updated 2015-02-15
Technical Information
This post is reserved for technical information with sources & binaries. This includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems.
Kernel Building:
--------------------------------------------------------------------------------------------------------
The first step for building working kexec-module & tools is to cross-compile the kernel from source with the correct configurations. I won't describe how to build a kernel from source, but you may find this thread very useful.
I've used two different sources for the NC4/NC2 HLTE_VZW KK kernels. The 1st one is a part of SM-N900V_NA_KK_Opensource.zip released by Samsung for N900V NC4 kernel while the 2nd is available on @Hashcode's Github profile with 3 branches: hltevzw-kk-nc2 branch is modified for N900V NC2 kernel + 15 commits for compiling kexec as a module & other kexec patches.
The instructions provided by Samsung to build the NC4 kernel are to update CROSS_COMPILE toolchain environment variable in the Makefile & build with the default configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
make
However, I've patched the sources & used menuconfig interface to customize kernel configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig menuconfig
make
(menuconfig is added in the second line)
The default output is the kernel image (arch/arm/boot/zImage) & modules (drivers/*/*.ko). The kexec-module(s) will be built if you patched the sources & configured it as a module.
You may then use dtbTool to generate device tree dt.img & mkbootimg to pack the kernel in boot.img.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Module:
--------------------------------------------------------------------------------------------------------
There're many different flavors of kexec-mod sources. @delewer in this thread uses a standalone kexec-mod source MOD'd for Sony Xperia Z1 to be cross-compiled against the precompiled kernel source while @Hashcode in his sources on Github patches the kernel source to cross-compile kexec-mod with the kernel. Some modules may or may not use/port the hardboot patches. The output for kexec module/drivers have different names (the standalone kexec-mod source generates kexec_load.ko & procfs_rw.ko while the kernel source patched by @Hashcode generates 3 modules: arm_kexec.ko, msm_kexec.ko & kexec.ko).
To test if the cross-compiled modules are loadable & have the correct kernel headers, use insmod in terminal emulator (or a safe point with terminal like Safestrap) to insert the module into the kernel (assuming you've kexec.ko in /system/lib/modules/):
Code:
insmod /system/lib/modules/kexec.ko
Then, use lsmod to list & show the status of loaded modules:
Code:
lsmod
Alternatively, you may check if system call of the kernel includes kexec functions using:
Code:
cat /proc/kallsyms | grep kexec
The kexec-modules I've compiled are loadable & have been successfully inserted into both NC4 & NC2 kernels.
I'm using my own sources for kexec-module based on others & I'll share the sources with binaries & modules after making some required tests.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Tools:
--------------------------------------------------------------------------------------------------------
I'm using the latest version of kexec-tools from here (currently, kexec-tools-2.0.8.tar.gz) cross-compiled for arm with custom configurations. Three binaries are generated including kexec (directly boot into a new kernel) & kdump (display kernel trace data). For more info, check the manpage of each binary & kexec/kexec-tools manuals/guides.
To test your kexec-tools cross-compiled binaries for arm,
Code:
kexec --help
assuming that they're in your PATH (e.g., /system/xbin) with executable permissions (e.g., 755).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hijack Script:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Required Patches:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Current Problems/Logs:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Sent from my SM-G900V using Tapatalk
jr_718 said:
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
amebiasis said:
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
Click to expand...
Click to collapse
I've tested several binaries for the same kernel version, but none works for now. I'll compile from source & see. However, please keep this this thread for devs discussions only until we release working kexec & guest kernel.
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
bmwh0r3 said:
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
Click to expand...
Click to collapse
Note 4 is useless until it gets root & custom ROMs. For me, it'll be better ONLY IF we can break its security & unlock bootloader!
What about surge & ryanbg and e.v.a. I been following them and they both have a good idea on how things work well I think they are good for the job
Just a thought I had when unlocking my spare RAZR hd, but the kernels on the Razr and my note 3 are 3.4.97 and 3.4.0. Is the exploit part of the kernel or is there a reason I'm a user and not a Dev? If it is, motopacalypse.apk is what unlocked my RAZR. I'm just trying to learn so please don't think I'm a moron. I just don't know the coding aspect of android at all.
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
tpike said:
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
Click to expand...
Click to collapse
There is #Galaxy-Note-3 on Freenode but it's really quiet in there most of the time.
Many forum lurkers like me have been anxiously waiting for this breakthrough! Don't give up! I also believe in donating to hardworking devs like you guys! Good luck...
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Feche said:
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Click to expand...
Click to collapse
Who was devs on kexec on defy?
ironfisted said:
Who was devs on kexec on defy?
Click to expand...
Click to collapse
Not sure
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Good luck! Lots of us are waiting for this!
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Keep it up man, I understand the hard work involved in doing something like this, but it will definitely pay of in the end!!! Thank you for your hard work and dedication, you got a lot of people counting on you
Sent from my BajaRom "L" Themed Note 3
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I see. Let me know if you'd like to contribute to this thread. I'll update it soon with more details about the required patches & the preliminary results of my tests ––after releasing a new version of JasmineROM.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I was told by a defy dev that we would have better luck contacting hp touch pad kernel devs. I guess their kernel is more like ours I guess. Idk. I never tried contacting dev from their yet
Here is my build of lollipop for the T800. it's useable in so far as being able to see what it's like.
It has been posted in here because it is not ready for prime time and I figured others might want to have a look. It has bugs and doesn't fully work so might not be suitable for daily use, but you decide
How to Install
Download zip to phone
Reboot to recovery
Flash CM12 zip
Flash gapps
Reboot
The first reboot may take a while so be patient.
Known Issues
Some slight graphical issues
Camera gives an error after each picture, just reopen to use use again.
Hardware keys aren't disabled if you use on-screen keys (but they are dimmed)
Video/Movies/Youtube won't play
Download Link
lonespeaker version (10th Dec) -- https://mega.co.nz/#!4ckg0BwB!AhpucIfXJ6P-Y1z7mxQgKkWzHVg4dEhkwiVEUvM3gyA
barracuda7 version -- http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
You can use any gapps but I use these ones -- https://s.basketbuild.com/gapps
Source Code
My CM12 Repo -- https://github.com/lonespeaker?tab=repositories
CyanogenMod -- https://github.com/CyanogenMod
Thanks and Credits
Thanks to @crpalmer (https://github.com/crpalmer) for the picassowifi files without whom this would not be possible.
Thanks to @Barracuda77777 (https://github.com/barracuda7), @eousphoros (https://github.com/eousphoros) for providing help and fixes here and on github.
// end
Changelog
Thanks to @Barracuda77777 - Post #22 contains an alternative version that he is working on.
http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
10th Dec
Camera is now working! But.... there is an error after you take a picture, so you need to reopen the camera app to take another picture, but at least you can take a picture!
Updated to CM12 sources 10th Dec 15:00 GMT.
7th Dec
Recents button now works. If you enable onscreen buttons, then the hardware buttons still work, albeit with the backlight on them turned off.
The sdcard seems to work, I had to reformat mine to get it recognised.
Wifi is now working thanks to barracuda7
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Awesome job buddy!
hhairplane said:
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Click to expand...
Click to collapse
T700 got it first check original development. Great work lone speaker on getting lollipop to the t800.
Looking forward to it !!! Great job !
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
lonespeaker said:
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
Click to expand...
Click to collapse
I fixed WIFI, Uploading now
Barracuda77777 said:
I fixed WIFI, Uploading now
Click to expand...
Click to collapse
excellent, how did you do it?
This is looking great! Awesome work. I realise its a very early build but hows the speed of it?
lonespeaker said:
excellent, how did you do it?
Click to expand...
Click to collapse
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
lonespeaker said:
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
Click to expand...
Click to collapse
do you mind if I post my rom in this thread?
Barracuda77777 said:
do you mind if I post my rom in this thread?
Click to expand...
Click to collapse
No not at all, go for it
i
lonespeaker said:
No not at all, go for it
Click to expand...
Click to collapse
thank you
here is the build with WIFI working:
cm-12-20141206-UNOFFICIAL-chagallwifi.zip
here is the link to the vendor files
Also, like lonespeaker, l have borrowed heavily from @crpalmer to get this rom up and going, please thank him and also if you wish to donate to him that would be great, without him there would have been no LP rom yet
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
Always the blobs. Some day maybe we will get source for some of this stuff.
Would a build be possible for 805 as well?
Which gapps should I use...can you point me to it? Thanks
naomile said:
Which gapps should I use...can you point me to it? Thanks
Click to expand...
Click to collapse
Im pretty sure you need to use the lollipop gapps since cm12 is lollipop. http://highonandroid.com/android-apps/download-android-5-0-lollipop-gapps/
This is very promising . fun to give it a go. Thankyou for you hard work guys. As said in the OP not ready for daily driver yet. One thing I noticed as I could at the moment its all about smoothing out the bugs. The recents apps button doesn't work. (Although I did select in options to double press home button to bring up recent apps to get around it. On screen buttons disabled
This is for all the Permissive S2 Marshmallow kernels. Further builds of kernels will go in their own threads.
Make sure to thank @ashyx and @jafangie if you use their kernels.
Permissive_Marshmallow_S2_Kernels
This will work on the 815/710/715/810 MM. So far
You flash this at your own risk. We are not responsible for anything that happens!!! There's the discaimer.
Install instructions:
You MUST HAVE ROOT and TWRP installed to flash this!!
This is for Marshmallow only
Flash kernel then wipe cache and dalvic
Reboot and profit!!
Changelog
815 Permissive Kernel - Stock with init.d support
710 Permissive Kernel - Stock with init.d support
715 Permissive Kernel - Stock with init.d support
810 Permissive Kernel - Stock with init.d support
______________________________
Downloads:
815_Permissive_initd_Kernel engine95
710_Permissive_initd_Kernel engine95
715_Permissive_initd_Kernel jafangie Thank here
810_Permissive_initd_Kernel engine95
XDA:DevDB Information
[KERNELS]Permissive_MM - 815/710/715/810 so far, Kernel for the Samsung Galaxy Tab S2
Contributors
engine95, ashyx, jafangie
Source Code: https://github.com/engine95/exynos5433-MM-NNKernel.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-05-08
Created 2016-05-08
Last Updated 2016-05-26
extra info
In a rooted explorer, you will need to delete /system/app/SecurityLogAgent. Or you will get a nagging warning.
I think whenever I reboot to recovery the permissive will be gone
Is it possible ?
I see the red line says "recovery is not seandroid enforcing" and apps that needs permissive won't work any more
But about shows permissive
weird ha ?
So I flashed kernel again and apps work ok.
papampi said:
I think whenever I reboot to recovery the permissive will be gone
Is it possible ?
I see the red line says "recovery is not seandroid enforcing" and apps that needs permissive won't work any more
But about shows permissive
weird ha ?
So I flashed kernel again and apps work ok.
Click to expand...
Click to collapse
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Sent from my LGLS990 using XDA-Developers mobile app
engine95 said:
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Click to expand...
Click to collapse
Dang so the issue I have had with es was broken root all this time I didn't know, I don't have that issue now but, that would have been nice to know a while ago...lol.
Josephigloe said:
Dang so the issue I have had with es was broken root all this time I didn't know, I don't have that issue now but, that would have been nice to know a while ago...lol.
Click to expand...
Click to collapse
The maker of the app needs to stop using hard-coded paths for root detection.
Most have corrected this. If you have an app that doesn't I urge you to contact the author or use a different app.
As said the Seandroid warning is nothing but a flag and wont affect anything in any way.
engine95 said:
The latest TWRP has fixed that warning. For recovery.
As for the kernel, it will show "Kernel is not seandroid". That's just wording and doesn't affect anything.
Why you would lose permissive can't happen. But your root could be broken if you flashed 2.65 and higher. Some apps still look for root in /system. So check and see if your app still has root. I'm betting that's the cause of it.
Edit. SU will say you have root. But if you actually use root for the app, it'll say no root. Estrong file explorer is a prime example.
Sent from my LGLS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
@Engine95, Hi my friend!
You're so lucky, take a look here http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t710 .
Concerning T715 I asked for sources to Samsung last Saturday... They just reply to me that they are now in the process of reviewing my inquiry.
Jaf
jafangie said:
@Engine95, Hi my friend!
You're so lucky, take a look here http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t710 .
Concerning T715 I asked for sources to Samsung last Saturday... They just reply to me that they are now in the process of reviewing my inquiry.
Jaf
Click to expand...
Click to collapse
The 815 source came out in 2 days after I requested it. I was in shock.
I requested 710 a week ago, so you made good time.
I have a feeling 710 source will be tied with the 810. So the 810 MM will probably need to release before I get source.
At least you got it and can move forward now. [emoji3]
Major edit: My bad. I just assumed. Wow
Maybe I should request your source. I'm on a roll. Maybe I should bet it all on black. Lol
Edit #2: Too funny. I just now got the notification from Samsung.
Sent from my LGLS990 using XDA-Developers mobile app
To the 815 users of this kernel. I have 2 questions.
1. Is wifi dropping on reboot? Meaning do you have to sign in each time you reboot? If you do, let me know so I can fix it. I'm taking things one step at a time because I don't know how Marshmallow runs yet.
2. Do you have the nagging security notice? If so, you need to delete /system/app/SecurityLogAgent, in a rooted explorer.
710 users, I have a permissive kernel about done. It was built using 815 source. So I'm gonna need this kernel flogged to death to make sure all is right. I just used the 710 MM defconfig.
Edit: This is in the OP now also. 710-MM-Permissive-Kernel
@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?
rumrunner4000 said:
@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?
Click to expand...
Click to collapse
Try a different server. I just dl'd from the Georgia one and it worked fine.
Sent from my LGLS990 using XDA-Developers mobile app
Update download available now.
@engine95, please create kernel for T810:
http://www.sammobile.com/firmwares/download/71178/T810XXU2CPD9_T810DBT2CPD9_DBT/
Model SM-T810
Model name Galaxy Tab S2
Country Germany
Version Android 6.0.1
Changelist 7767647
Build date Mon, 25 Apr 2016 11:01:57 +0000
Product code DBT
PDA T810XXU2CPD9
CSC T810DBT2CPD9
kutaxov said:
@engine95, please create kernel for T810:
http://www.sammobile.com/firmwares/download/71178/T810XXU2CPD9_T810DBT2CPD9_DBT/
ModelSM-T810
Model nameGalaxy Tab S2
CountryGermany
VersionAndroid 6.0.1
Changelist7767647
Build dateMon, 25 Apr 2016 11:01:57 +0000
Product codeDBT
PDAT810XXU2CPD9
CSCT810DBT2CPD9
Click to expand...
Click to collapse
I need to request source. Then wait til Samsung will release it.
But ya, you'll get one.
Sent from my LGLS990 using XDA-Developers mobile app
rumrunner4000 said:
@engine95
will not let me download from link above or in OP -error on android filehost for 710-MM-Permissive -Kernel unexpected response from server?
Click to expand...
Click to collapse
Worked for me.
engine95 said:
I need to request source. Then wait til Samsung will release it.
Click to expand...
Click to collapse
Hi engine95,
I am stil trying to build from T815_MM my T715_MM!
But I have one issue.
What I do :
1) Update Cross-Compiler
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
2) Edit the base kernel Makefile to set up my cross compiler.
3) Build the kernel
$ export CROSS_COMPILE=/home/ja/android/arm-eabi-4.8/bin/arm-eabi-
$ export ARCH=arm
$ make exynos5433-gts28lte_defconfig
$ make ARCH=arm -j5
No eror, I have my Zimage
4) Make the new image
$ umkbootimg boot.img
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --output boot.img
My boot.img doesn't boot at all... I try your T815_MM it boots and bootloop (I think it is normal way )
What I am missing, is there one step more on MM?
Any idea? It was exactly what I did for T715_LL and everything is going well!
In advance thank a lot.
jafangie said:
Hi engine95,
I am stil trying to build from T815_MM my T715_MM!
But I have one issue.
What I do :
1) Update Cross-Compiler
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
2) Edit the base kernel Makefile to set up my cross compiler.
3) Build the kernel
$ export CROSS_COMPILE=/home/ja/android/arm-eabi-4.8/bin/arm-eabi-
$ export ARCH=arm
$ make exynos5433-gts28lte_defconfig
$ make ARCH=arm -j5
No eror, I have my Zimage
4) Make the new image
$ umkbootimg boot.img
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --output boot.img
My boot.img doesn't boot at all... I try your T815_MM it boots and bootloop (I think it is normal way )
What I am missing, is there one step more on MM?
Any idea? It was exactly what I did for T715_LL and everything is going well!
In advance thank a lot.
Click to expand...
Click to collapse
It could be a few things. And I'm guessing you're building a "Permissive" kernel.
Just in case, my git is here. https://github.com/engine95/exynos5433-MM-NNKernel.git It uses 815 source.
I didn't see that you did: "make menuconfig" when building your zimage.
Edit: Just save it. You don't need to make any changes there.
As for the ramdisk, use it from the 715 MM kernel.
In "default.prop" add this line. "ro.securestorage.support=false".
Above "# BOOTIMAGE_BUILD_PROPERTIES" I think we have to have this in now, not just for WIFI" I think I needed this to get it to boot. But I'm not positive.
Another problem could be the "defconfig". I tried "L" and it didn't work. I needed to wait for source so I could get it for "M". But this could have been my problem when I first built. Trying to figure things out.
SU might be another issue. I think I used a clean boot.img from the .tar. Don't root it.
Thing is, my ROM has SU built in /system, instead of systemless root. So I'm not sure what that's going to do to you.
When I build 710 or 810 using same source, the zImage does build differently. So they aren’t interchangeable. That was probably the bootloop when you tried that with 815 on 715.
Let me know how it goes. We'll get it figured out.
Please, T810 ?
cedric3 said:
Please, T810 ?
Click to expand...
Click to collapse
Request Opensource Samsung for T810 6.0.1 kernel source, more demand will mean faster source code, which results in a permissive kernel (root )
cedric3 said:
Please, T810 ?
Click to expand...
Click to collapse
I'm cleaning a huge mess I had, from when MM first popped up. I had files scattered across 7 OS's. Testing some different Linux distro's for myself.
Besides that, I've been trying to get a ROM figured out. I either get an unmountable system, or I break wifi and ext SD. 710 isn't a problem because I have that.
Samsung still hasn't posted source for the MM 810. I was waiting for it so I can pull the 810 defconfig.
I'll get you one shortly.
Edit: I've requested 810 source already. Almost a week ago.
Funny, but I'm having an easier time building kernels than Roms now that MM is out.
Sent from my LGLS990 using XDA-Developers mobile app
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!