Database Users

[REF] Kernel source for GT-i9000B (froyo) is now available on opensource.samsung.com

Kernel source for GT-i9000B is now available on opensource.samsung.com.
Search for i9000 and it will display the file "GT-I9000B_Latin_OpenSource_Froyo.zip".
That file incorporates only the files which differ from i9000.

neldar said:
Kernel source for GT-i9000B is now available on opensource.samsung.com.
Search for i9000 and it will display the file "GT-I9000B_Latin_OpenSource_Froyo.zip".
That file incorporates only the files which differ from i9000.
Click to expand...
Click to collapse
Thanks neldar !
I'll check that out, as you do
PS : lame on them publishing an archive containing just the changes. they really need to apply the same method they learn Working with the kernel with Google.
Also, i guess we will never get the source for their Eclair kernel..

It is a BIG NEWS for i9000b users, becouse, until today we haven´t any custom ROM. With this, it willl change soon, thanks neldar, and thanks supercurio for cheking it,

so, you can get the whole package for the i9000/i9000t, and this, and get a complete source for the i9000b's kernel ?
(i ask this because of supercurios comment about the way its being published, and how its lame)

wow finally

Great news, thank you.

supercurio said:
Also, i guess we will never get the source for their Eclair kernel..
Click to expand...
Click to collapse
i asked samsung about it some weeks ago and they toldme:
that they made a mistake not posting it but developers were working with froyo and would release the sources for mid december
so, i think you are right.
note: i builded 2 kernels with this code, if anyone is interested, i have it runing on my mobile right now.

luismanson said:
i asked samsung about it some weeks ago and they toldme:
that they made a mistake not posting it but developers were working with froyo and would release the sources for mid december
so, i think you are right.
note: i builded 2 kernels with this code, if anyone is interested, i have it runing on my mobile right now.
Click to expand...
Click to collapse
can you post details of the compilation process?
thanks

obalado said:
can you post details of the compilation process?
thanks
Click to expand...
Click to collapse
README.TXT:
Code:
How to build:
< Platform >
The Platform is the same as that of the European version.
Get GT-I9000 open source.
: GT-I9000_OpenSource_Froyo_update_JPM.zip
Unzip it, then you will see the file GT-I9000_Platform.tar.gz which includes the Android source code.
< Kernel >
1. Get GT-I9000 open source code:
- GT-I9000_OpenSource_Froyo_update_JPM.zip
Unzip it, then you will see the file GT-I9000_Kernel.tar.gz which includes the kernel source code.
2. Overwrite GT-I9000B Kernel open source code from the Latin American version to Europea kernel open source code.
3. move into the Kernel/ directory
4. Execute 'make aries_latinb_defconfig'.
5. Execute 'make' or 'make -j<n>' where '<n>' is the number of multiple jobs to be invoked simultaneously.
6. If the kernel is built successfully, you will find following files from the top directory:
arch/arm/boot/zImage
net/netfilter/xt_TCPMSS.ko
drivers/onedram_svn/modemctl/modemctl.ko
drivers/onedram_svn/onedram/onedram.ko
drivers/onedram_svn/svnet/svnet.ko
drivers/bluetooth/bthid/bthid.ko
drivers/net/wireless/bcm4329/dhd.ko
drivers/scsi/scsi_wait_scan.ko
drivers/samsung/fm_si4709/Si4709_driver.ko
drivers/samsung/vibetonz/vibrator.ko

I9000B i sold out at all stores here in Brazil.
I think that there are so much people getting happy enogh to donate for custom roms, possibly now!
and i'm one of them.

well, i did a custom kernel

luismanson said:
well, i did a custom kernel
Click to expand...
Click to collapse
so why aren't we testing it yet?

because almost no one cares?
i find amazing things in xda but to get a post replied or some help....
here it is: http://forum.xda-developers.com/showthread.php?t=878721
be careful, A2DP has problems (no bluetooth audio)

Any chance we can get a 2.2.1 ROM and Voodoo now? Please guys, help us out.

nothing yet?

[Kernel][Linaro] Stock KK kernel for Falcon

This is a near stock falcon 4.4.4 kernel built with the latest Linaro toolchain (Linaro GCC 4.9-2014.12) for all of those who prefer stock kernels and absolutely need those 10 extra points in Antutu
Differences from stock are just a few Cortex-A7 optimizations, F2FS patches from mainline 3.18 and linaro toolchain.
All credit goes to @bedalus, who started his kernel thread for Peregrine, fixed all the small bugs that made compiling with newer Linaro toolchains impossible and cherry picked all those F2FS patches.
Sources and tools used:
MotorolaMobilityLLC/kernel-msm
MotorolaMobilityLLC/vendor-qcom-opensource-wlan-prima
bedalus' patches
Christopher83's Linaro Toolchain
My repo, where all sources are merged
Changelog:
falcon_stock_4.4.4_linaro_4.9.3.zip
- stock kernel
- added necessary patches to make it compile with linaro
- some Cortex-A7 optimizations
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
The zip can be flashed with TWRP or CWM. Not flashable through fastboot.

Thanks @knizmi. I think stock users will appreciate this

Anyone tested? How the battery?
Wysłane z MOTO G

Dizzyrul3z said:
Anyone tested? How the battery?
Click to expand...
Click to collapse
This is the stock kernel, so the batttery is as good as with stock kernel (you really can´t make it much better in any way). These screenshots are taken after some 7 hours of sleep.

Works pretty good on XT1031. Nice work! Any chance you could make a build with the kexec hardboot patch to use it with multirom?

I immediately noticed a performance improvement after flashing this kernel. Thanks!

Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
This is my preferred way to grab commits. Did you add my repo as a remote?

Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app

bedalus said:
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
Click to expand...
Click to collapse
Thanks a bunch, this should really make merging those patches easy!
bedalus said:
This is my preferred way to grab commits. Did you add my repo as a remote?
Click to expand...
Click to collapse
I have added your repo as a remote now. I was fighting with git last week quite a bit (never used that devil's tool before), but now I think I am getting used to it. For my first build I've just "patched" those files with gedit...

syrkles said:
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up, but compiling someone else's sources doesn't make me a dev

New version uploaded.
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
Thanks @bedalus.

amarc78 said:
Any chance you could make a build with the kexec hardboot patch to use it with multirom?
Click to expand...
Click to collapse
Sorry, the aim of this is to stay as close to stock as possible and only add optimizations/update drivers.

knizmi said:
For my first build I've just "patched" those files with gedit...
Click to expand...
Click to collapse
If you've got my repo as a remote you should be able to see my commits with
Code:
git log -- bedalus/moggy
depending on what you named your remote.
Once you see what commits you want, copy their hashes (the long string of letters/numbers) then
Code:
git cherry-pick *hash*
If there's a problem with the cherry-pick you can fix it manually with
Code:
git mergetool
or abort with [git cherry-pick --abort[/code]
I've installed meld as my mergetool. I'm using a debian derivative so I did
Code:
sudo apt-get install meld
That's a pretty comprehensive quick-start guide to cherry-picking from any remotes you've fetched.

Cannot downgrade to default stock.
can you make a zip with libs to go back.

everb00b said:
Cannot downgrade to default stock.
can you make a zip with libs to go back.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=2649763

That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.

amarc78 said:
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
Click to expand...
Click to collapse
You mean in the thread I've posted. I've thought that too at the beginning, but they are there separately, look for Stock Kernel Modules: [XT1032] - 4.4.2 | 4.4.3 | 4.4.4 | 4.4.4 (GPE) | 5.0.1 (GPE) | [XT1033] (Dual-SIM) - 4.4.4. You just have to flash two zips instead of one.

Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Edit: never mind. They look the same.

amarc78 said:
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Click to expand...
Click to collapse
Not sure, you can try. If there is a problem you can always reflash stock /system, backup those modules and perhaps send them to @lost101

bedalus said:
If you've got my repo as a remote you should be able to see my commits
Click to expand...
Click to collapse
Thank you for the info again. You are very helpful.
Do I understand it correctly that I need to fetch your repo before I can start cherry-picking? Searching around the internet , it looks like it. I may give it a try one day, but for now I will stick with git am, which seems like the perfect tool to pick single commits from many repos.

CyanogenMod for Pixel v1

FIRST TEST BUILD OUT
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_google_seedmtk
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : [url]https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout[/URL]
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_seedmtk-2ndgen
NOTE TO TESTERS : Please try getting logcats for me since it is IMPOSSIBLE to do anything without even knowing why something is broken

MSF Jarvis said:
Since the MTK variants in the second gen Android One devices have steadfastly been ignored for development, I have taken it upon me to ensure that there is no dearth of top-of-the-line trees for any brave person wanting to build for this device. Here are my sources :
Device Tree : https://github.com/MSF-Jarvis/android_device_mediatek_sprout
Common Tree (necessary) : https://github.com/MSF-Jarvis/android_device_google_sprout-common
Kernel Source (untested) : https://github.com/MSF-Jarvis/android_kernel_mediatek_sprout
Vendor Tree : https://github.com/MSF-Jarvis/proprietary_vendor_google_sprout-2ndgen
I am currently negotiating for a server with one of my dear friends, and will commence builds as soon as I can wrangle one out from him
Everyone is welcome to help me out with this project. I tried getting @DHARMESH17 onto it but apparently it seems he's not very interested or dedicated to the cause.
And oh, almost forgot, here's a local manifest to prevent manually cloning things : https://github.com/TeamRedux/local_manifests/tree/cm-13.0-sprout
Click to expand...
Click to collapse
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom

DHARMESH17 said:
Bro I am completely interested in it but because of some barriers I was unable to continue the project but now I am completely feee and start development on rom
Click to expand...
Click to collapse
I would like some proof of your ability with ROM compiling before I let you in on my server.

Ashiron said:
Give me full details.
Start to end.
100% success result
??
Click to expand...
Click to collapse
Details as in??

The kernel source has been imported to my Github and I have also set-up Continuous Integration on it through Travis-CI, build progress can be tracked here.
I would like to thank @akhilnarang whose ThugLife scripts have been used to compile the kernel inside the CI. I couldn't include your name in the commits, but the original copyright notice has been retained in the spirit of open source.

I have been informed through Google Plus that @DHARMESH17 has been in the hospital for some time now, and @faddat is currently in China, so the project has been put on hold for now.

Work will begin tomorrow

You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot

akhilnarang said:
You can get the stock source to boot on pixel?
A friend of mine has tried, it dosen't boot
Click to expand...
Click to collapse
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution

MSF Jarvis said:
Kernel source? Of course not, I believe it's specific to the first gen sprout devices, as I found out earlier this day. I guess I'll have to end up messing with the device tree and see if I can sneak in a prebuilt kernel somewhere inside. One query though, since you've made an appearance, if I use a custombootimg.mk for userdebug builds, will it prepare the boot.img as per the recipe given there? Because as TWRP maintainer for the htc pico, I have to force it to use LZMA compression for the ramdisk to make it fit, and for that I set a ifeq into the boardconfig to use the customrecoveryimg.mk I put in the device tree, if build variant is eng. If it will work on boot.img and userdebug, then I may very well be able to fool CM's build system and use a prebuilt kernel.
If I'm not making myself clear, please do hop on to #team-redux on freenode and we'll discuss it at length and hopefully arrive at a solution
Click to expand...
Click to collapse
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM

akhilnarang said:
No need of fooling any system, you can happily use a prebuilt kernel as it is to build CM
Click to expand...
Click to collapse
Go ahead and try

MSF Jarvis said:
Go ahead and try
Click to expand...
Click to collapse
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app

akhilnarang said:
I have, and I often use a prebuilt kernel, no issues. What do you get?
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )

I have got a server now, and will commence builds tomorrow. Stay tuned!

MSF Jarvis said:
AOSP based ROMs are a different story, CyanogenMod raises this exception when you try using a prebuilt kernel :
```
Using a prebuilt kernel is deprecated and not allowed
Please add your kernel source to your BoardConfig.mk
```
Or something to that tune, been months since I ran a compile for any ROM(Server's late in coming, @faddat is a busy man )
Click to expand...
Click to collapse
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app

akhilnarang said:
It still builds, as long as you've specified the PRODUCT_COPY_FILE properly
Anyway, why did you base your trees on the old cm-12.1 trees of Varun
If you're trying cm-13.0 then base on the latest cm-13.0 from CyanogenMod GitHub
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)

MSF Jarvis said:
I realised that earlier today, so I rebased my updates onto the snapshot trees and pushed it to my Github. The local manifest has been updated with the new branch as well.
About the prebuilt kernel, you use PRODUCT_COPY_FILES for copying the zImage ?? @thewisenerd once mentioned its a terribly ****ty idea, but you're more updated regarding building and ****, so I'll take your word. Just a quick query, what'll be the out location of the kernel? ($OUT/kernel ??)
Click to expand...
Click to collapse
Yep
Code:
PRODUCT_COPY_FILES := $(LOCAL_PATH)/kernel:kernel
Sent from my Nexus 5X using XDA-Developers mobile app

@akhilnarang, you free some night? I'll be needing help as far as I can see.
Anyways, ever had a problem with cts/apps/ctsVerifier throwing exceptions? My build refuses to start! Not to mention that repo is also being very hard on me, not syncing projects, throwing exceptions while unpacking and ****. Gonna rebase to nightly level, currently on snapshot 1.

Official TWRP now available : http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364

MSF Jarvis said:
I would like some proof of your ability with ROM compiling before I let you in on my server.
Click to expand...
Click to collapse
Bro still want proof LoL ??

Lineage OS 13 for *KKBL*

There's an unofficial build of Lineage OS 13 for KKBL available in the Razr HD section. As far as I know, this is the first build of Android 6.x or above that has been released on KKBL (which means 3.4.x kernel). So, two questions.
How many and what changes are required to get this working on XT907?
Has anyone already attempted this (and would like to provide feedback)?

@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...

rahimali said:
@DiamondJohn, do you have any input on this? Would be interesting to try this out. Any idea what changes are required? Must be minor (screen density only?) I'm hoping at least...
Click to expand...
Click to collapse
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907

DiamondJohn said:
I'm, no crack dev, but the first thing I would look into are the differences in the device proprietary files, if they appear to be pretty similar devices.
XT925 = https://github.com/LineageOS/android_device_motorola_xt925/blob/cm-14.1/device-proprietary-files.txt
XT907 = https://github.com/LineageOS/android_device_motorola_xt907/blob/cm-14.1/device-proprietary-files.txt
For example, a big part of the "porting" of an xt897 ROM to an xt907 is held in the above info (and the relative locations of the actual binary files used with the same name). Its a starting point. I think someone converted a XT907 ROM to their xt925 using my above suggestion; but not perfectly.
When I first started building for my XT905 (ie a 907) I noted that there was already a device tree for the 907, but from memory, I think its for KKBL (im JBBL)
https://github.com/LineageOS/android_device_motorola_xt907
Click to expand...
Click to collapse
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
although i wouldn't know what to do with it since i'm no dev. you think you could somehow port the xt92x build to xt90x / msm_moto8960 devices?

rahimali said:
what about this one?
https://github.com/LineageOS/android_device_motorola_moto_msm8960
Click to expand...
Click to collapse
I have assumed that the source and the dest are both msm8960 devices, bo9th on the same level/ver of bootloader, and therefore this reads as a shared code path traversed by both devices, so its already taken care of (in both). You are looking for DIFFERENCES in the code path.
PS: the other thing you will need to modify is the "updater-script" (in particular the first line) and the build.props (it doesn't normally flash from the zip without extra instructions, even though "its there"). I have personally changed the first line of the updater script and then copied the firmware files and an updated build.prop within TWRP before my first boot for quick checks. Just use the set permissions to 755 for safety on each file as well (for testing)

I have been trying to build crDroid for xt907_JBBL, but have been having issues. Today I thought of upgrading to the KKBL, which made me then search and not find, a suitable TWRP (ie >= v3.x)
is there a xt907_KKBL TWRP >=3.x? or would I have to build one?

DiamondJohn said:
is there a xt907_KKBL TWRP >=3.x?
Click to expand...
Click to collapse
No. The last is 2.8.6

Shmaks said:
No. The last is 2.8.6
Click to expand...
Click to collapse
Can that flash Nougat ROM's?

DiamondJohn said:
Can that flash Nougat ROM's?
Click to expand...
Click to collapse
Who knows. The last custom rom for kkbl is cm12 and 2.8.6 flash it, so there is no way to check

Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716

DiamondJohn said:
Could you try the following sand let me know if it works?
https://forum.xda-developers.com/dr...p-twrp-xt907-kkbl-experimental-build-t3652716
Click to expand...
Click to collapse
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?

Shmaks said:
Maybe i will try later today. But, what reason? Do you planning build nougat (or cm13) rom kkbl for XT907?
Click to expand...
Click to collapse
I am trying to build crDroid v3.6 (ie 7.1.2), however for my JBBL its having numerous FC's I do have a zip file which would enable me to upgrade to KKBL which would make it interesting to see if a KKBL version is more stable. IF I could also SAFELY go back to JBBL I had a Moto X and accidently (by accepting an OTA) downgraded my bootloader and that caused a hard brick on the device, so I am a little cautious to say the least, as it is my daily.
I am also just downloading the device tree for an xt907 KKBL on my build machine and see if it can build a LineageOS 13. I'll let you know how it goes, and probably paste up a link for others to test if it succeeds to build since my device is JBBL
=============== edit =============
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL

DiamondJohn said:
IF I could also SAFELY go back to JBBL
Click to expand...
Click to collapse
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
DiamondJohn said:
Correction, I am testing a Lineage OS 14.1 (ie Nougat) build of xt907 KKBL
Click to expand...
Click to collapse
Cool, hope for a successful experience

Shmaks said:
For safely moving between kkbl-jbbl and backward i used flashbacks for along time:
https://androidfilehost.com/?fid=24533100289589621
https://www.androidfilehost.com/?fid=385035244224404260 (flash it in twrp, then firmware or custom rom on jbbl (kkbl) based)
Never had problems with them.
Click to expand...
Click to collapse
Thanks, the links I found for these zips were all dead or required registration.
Shmaks said:
Cool, hope for a successful experience
Click to expand...
Click to collapse
Its at 4 % .., step 1512 of 34456 ... 5% and I'm off to bed, its late here. The big problem is uploading it to a host, its normally an over night job or at least a a few hours. So it may be two nights before its up somewhere to download IF it succeeds in da build.
9%....
11%...

DiamondJohn said:
Thanks, the links I found for these zips were all dead or required registration.
Click to expand...
Click to collapse
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a

@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...

DiamondJohn said:
11%...
Click to expand...
Click to collapse
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Shmaks said:
other (working) link https://www.dropbox.com/sh/791ixp14rqlzigo/AAAlNvQS3DGwzXv1AIeY0Fm2a
Click to expand...
Click to collapse
rahimali said:
@DiamondJohn, I have the flashbacks to JBBL and KKBL available as well, lemme know if you want but the AFH links posted earlier work just fine as well.
Click to expand...
Click to collapse
No need, because I have a an xt905, it has Australian frequencies, which means Australian specific modem. These zips were only for me to confirm the steps I plan to take when flashing manually using fastboot, from an Australian specific (ie xt905) Image file. so, one example is enough. Thanks anyway.
rahimali said:
Sorry I'm also on JBBL otherwise I would help you test your recovery. TWRP 2.8.x not compatible with Nougat?
Click to expand...
Click to collapse
I don't know. I know on previous version of Android, new versions of ROM zip files took advantages of features not in older TWRP images, and TWRP 2.8.x is getting old.
There is little drive in me building, uploading and posting a KKBL ROM post, if no-one else is testing it for me ie save me the hassle of flashing KKBL only to find TWRP &/OR ROM does not work. Yes, its all about me
rahimali said:
Edit :: Do you think the XT907 has the horsepower to handle Nougat? I'd say the best best for this phone would be any flavor of MM but no higher. I'm on MoKeE Nougat JBBL and it seems to work well enough...
Click to expand...
Click to collapse
More than enough. I have built a nougat ResurectionRemix and a crDroid (available HERE for testing; JBBL only) and it felt just as snappy as Marshmallow. Also, on my daily, I am running LOS13.0 with the Nougat Kernel, overclocked to 1.98GHz. ie we can also get a small/tiny boost easily with OC; the feature is built into the kernel but simply switched off in the LOS official builds.

DiamondJohn said:
100%
It built successfully!:highfive: to be clear, I now have a LOS 14.1 (ie Nougat) ROM zip for an xt907 KKBL file, sitting on my disk. I will upload it (hours....) and post it up for someone (on KKBL) ...anyone... to try.
Click to expand...
Click to collapse
Can't wait

Shmaks said:
Can't wait
Click to expand...
Click to collapse
have you tried TWRP for KKBL? And you may be waiting for a dud however upload is at 53%

DiamondJohn said:
have you tried TWRP for KKBL?
Click to expand...
Click to collapse
Yes, it works!

[Q] when we get android 8 for our nexus 4?

hi friends,
do you know, our nexus 4s get android Oreo by nitrogen or lineage or other roms? if yes, I know stable android Oreo version will release mid august, when we get custom rom?

we can't know this

When it comes fyi: asking for an ETA is kinda rude on xda
wait till October or November probably for a decently stable ROM

Excitedly expect first android Oreo Rom for nexus 4 on september 17

and first 32bit snapdragon android oreo port, fully work
https://forum.xda-developers.com/showpost.php?p=73494285&postcount=1356
so, now we have very big chance for our nexus 4...

and first nexus 5 android oreo port, booting and wifi working now, one similiar devices too
https://forum.xda-developers.com/showpost.php?p=73538437&postcount=6286

for now has boot problem but after all the first nexus 4 oreo
https://forum.xda-developers.com/showpost.php?p=73594437&postcount=231

I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.

good news
thanks for good news,
and maybe co-operation accelerates this work
equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse

If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here

equlog said:
If anyone wants to try Oreo in our lovely mako.
Original thread: Android 8.0 Mako
Download: here
Click to expand...
Click to collapse
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?

Can you share the device and kernel tree?

equlog said:
I have compiled android 8 and I managed to get it booting(lots of changes on kernel and device tree). Need a lot of work but mako probably will get a fully fuctional android 8 rom.
Click to expand...
Click to collapse
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?

ariesgodofwar said:
Nice! At work and don't have my N4 to try it, but interested to hear how it is running, so I can try out when I get home. Is it mostly functional?
Click to expand...
Click to collapse
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Renandelfanti said:
Can you share the device and kernel tree?
Click to expand...
Click to collapse
Sure, i'll upload to github later.
TheSt33v said:
Just for my own curiosity, how do you know what changes need to be made to the device and kernel tree? Do you use officially supported device/kernel trees as a reference, or is there a guideline posted somewhere?
Click to expand...
Click to collapse
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .

equlog said:
Really I haven't tested too much, busy at work... also my n4 have the touch screen broken and doesn't works very good lol.. but almost nothing works.
Its just to try out.
Sure, i'll upload to github later.
The kernel is the used one in 7.1.2 and I added the Binder changes... the device tree is fixed by trying to booting and fixing the errors showed in last_kmsg .
Click to expand...
Click to collapse
Yes, I also flashed this and it boots. As you said, nothing works... But it is not less that it boots :laugh:
I've been trying since the source of O is released and could not boot it. Your work gives all mako users hope to see a working O build :good: Thanks for the work!
Nitin

I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?

I've flashed from mako 7.12, kind of like upgrade from 7.12

Sources up.
I used the vendor blobs from TheMuppets.
https://github.com/MakOreo
---------- Post added at 01:42 AM ---------- Previous post was at 01:24 AM ----------
Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
:good:
I dont have too much free time, but I always follow the status of my devices. I Hope to see a fully working O rom asap.

Ziyan said:
I as well got a semi-working O build, but was a bit short on time to work on it. Could we collaborate somewhere? Perhaps a hangouts group?
Click to expand...
Click to collapse
That's a good idea... What do you say @equlog?
Thanks a lot for sharing the sources :good:
Nitin

as good as we hoped