• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

Lineage OS XT907_JBBL

ilichva

Senior Member
Dec 19, 2010
170
164
0
Last edited:

aggressivepixels

Senior Member
May 24, 2015
78
16
0
20
Maracay
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
 

ilichva

Senior Member
Dec 19, 2010
170
164
0
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
 
  • Like
Reactions: DiamondJohn

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
I just found this thread. When I flashed this ROM, I installed Magisk for root and haven't noticed anything negative, but have found benefits (e.g. installing/running Viper, work around for failing init.d etc). It also appears to be the choice on other devices, in newer ROMs .
@ilichva is there any specific reason you suggested SuperSU? or is it just that you haven't personally tested Magisk?

Originally I was kind of worried that the vanilla style of Lineage OS would bug me (as I am used to ROM's with a lot of customisations). However, I have Magisk (the apparent latest way to root), V4A, a Linux Swap Partition and have Xposed the...err...heck! out of the ROM (8 Xposed modules), including "Settings Editor" which enables you to add things to the settings menu that makes the additions (eg Viper) appear like they are actually part of the ROM.:good:
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
No...i didn't use init d or any script
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.

I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
 

dedik46

Senior Member
Sep 25, 2014
175
29
0
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.

I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
I've never try to use any script on init.d and i don't know if init.d is working or not, maybe i will try to use magisk for the next update..
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
I've never try to use any script on init.d and i don't know if init.d is working or not
And that's what I was checking. init.d does not work in this lineage ROM, nor in another devices (Nexus 5) lineage based ROM; ie Resurection Remix on N5. I am really surprised how little attention this artifact is getting.

maybe i will try to use magisk for the next update..
Although not an issue for me, it has extra features such as allowing some apps that wont run on rooted phones, to have su hidden from them. I like the fact that is has pre-built modules to support extra's such as V4A. I also liked the fact that it has its own init.d functionality that I use since the ROM's init.d does not work. And it appears to be the direction newer custom ROM's are heading for root.

Really, your already thinking about the next build? I am more thinking about the method/steps I did wrong or could of done better from the flash of the last build.
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
Wifi issue is not only our device

Some people have noted an issue with Wifi. I too have had the issue with the wifi loosing its connection and not automatically re-connecting. even though the Wifi is available and well within range.

I looked into it a little further (created a quick app that logged numerous broadcast messages, and logged them to a file), and as part of that I also tested the "pass" situation on my spare Nexus 5 phone, also connected top my Wifi. However, it too failed! it was however better in that it didn't randomly loose the wifi.

With the N5, if I was connected to Wifi (very strong signal), went into settings, turned off the wifi. When I turned the wifi back on, it did NOT automatically re-connect.

The N5 is running a MM Resurrection Remix (one of the latest builds, based on Lineage I think)

So, It would appear that this wifi issue is not specific to our devices. I am not sure if thats a good or bad thing.:confused:

Anyway, I have my logging test app running, and like a watched kettle, it hasn't lost its Wifi connection :mad:
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:

It has happened to me randomly once before, and then it just came back randomly as well :confused: a few days later.

I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
4,482
3,531
113
Sydney
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:

It has happened to me randomly once before, and then it just came back randomly as well :confused: a few days later.

I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
I got the recents working again. :D
I tried turning all my xposed modules off (including a couple that affected the navbar), but it was still failing.:(

Then I noticed that for the first minute or so it would work every boot, but then eventually stop. So I thought it was some installed app/config that only started later in the boot sequence. This "app" must have root to do such damage, so I went down that path. Thought it might be Magisk (since I appear to be one of the only on it). So I uninstalled Magisk, and flashed SuperSU. Still failed.:mad:

Anyway, I got it working again by turning off Super User access to all apps individually (after a restore back to my original starting point), then turning it back on (with a few reboots between). I couldn't identify exactly which caused it, but now it all works :highfive:, and I have a technique to hopefully correct it in the future.:good:
 
  • Like
Reactions: dedik46