Database Info

Help, building cm9 from sources

Hello, I have some problems while building cm9 from sources.
When I do
Code:
brunch galaxysl
I get the following:
Code:
Repository for galaxysl not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/galaxysl/cm.mk]]: "device/*/galaxysl/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_galaxysl'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
(seems like its not officialy supported by CM team)
I've tried this:
Manually downloaded files as .zip from here:
Code:
https://github.com/teamhacksung/android_device_samsung_galaxysl
and extracted here: /device/samsung/galaxysl/
Then downloaded files from here:
Code:
https://github.com/teamhacksung/android_vendor_samsung_galaxysl
and extracted here /vendor/samsung/galaxysl/
Then compiled with no errors, the output files were something like this:
Code:
cm-9-20120717-UNOFFICIAL-galaxysl.zip
and
Code:
cm_galaxysl-ota-eng.xxxx.zip
They have both different sizes (every file has different size inside .zip), if someone could tellme the difference it will be apreciated.
Tried flashing both of them, and the phone doesnt boot up, just black screen on.
CWM 6.0 works just fine.
Could someone guideme or give me any tip to make it work?
Thanks in advance.

frapeti said:
Hello, I have some problems while building cm9 from sources.
When I do
Code:
brunch galaxysl
I get the following:
Code:
Repository for galaxysl not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/galaxysl/cm.mk]]: "device/*/galaxysl/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_galaxysl'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
(seems like its not officialy supported by CM team)
I've tried this:
Manually downloaded files as .zip from here:
Code:
https://github.com/teamhacksung/android_device_samsung_galaxysl
and extracted here: /device/samsung/galaxysl/
Then downloaded files from here:
Code:
https://github.com/teamhacksung/android_vendor_samsung_galaxysl
and extracted here /vendor/samsung/galaxysl/
Then compiled with no errors, the output files were something like this:
Code:
cm-9-20120717-UNOFFICIAL-galaxysl.zip
and
Code:
cm_galaxysl-ota-eng.xxxx.zip
They have both different sizes (every file has different size inside .zip), if someone could tellme the difference it will be apreciated.
Tried flashing both of them, and the phone doesnt boot up, just black screen on.
CWM 6.0 works just fine.
Could someone guideme or give me any tip to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You need to download the kernel too.
Download android_kernel_samsung_latona.
And build it separately and then build cm9.
In the evening, I will post the local_manifest.xml, copy it to the .repo folder. this will downlod the device/vendor and kernel for galaxysl automatically. Any changes by teamhacksung will also be synced automatically.
meanwhile you can refer to cm7 local_manifest.xml.
You need to make changes to it to as it is for gb.
Check this out: http://pastebin.com/Xig7BtHV

ganeshbiyer said:
You need to download the kernel too.
Download android_kernel_samsung_latona.
And build it separately and then build cm9.
In the evening, I will post the local_manifest.xml, copy it to the .repo folder. this will downlod the device/vendor and kernel for galaxysl automatically. Any changes by teamhacksung will also be synced automatically.
meanwhile you can refer to cm7 local_manifest.xml.
You need to make changes to it to as it is for gb.
Click to expand...
Click to collapse
Thanks you very much I'll sure try this tonight

Why dont u try building cm10 from sources like that on galaxy s i9000...
Thanks
Sent from my GT-I9300 using xda app-developers app

EDIT:
I didn't read Ganesh's post well enough and I din't see his attachment at first. This post is pretty much the same .
EDIT 2:
I should see better, but I think that cm-9-***-UNOFFICIAL-galaxysl.zip has all the apk with all the images optimized for size. If you take a look at the last messages in your terminal you'll see a lot of lines that start with "Optimizing ****...".
____
I usually put this local_manifest.xml inside .repo/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="ics" />
<project name="teamhacksung/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="ics" />
<project name="teamhacksung/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="ics-samsung-2.6.35.7" />
<project name="alfrix/buildscripts" path="buildscripts" remote="github" revision="ics">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
</manifest>
and then run
Code:
repo sync
Everything is done automatically, all the sources are in the right place and everything is ready to be built.
As you can see I'm using alfrix's builscripts instead of the teamhacksung ones. That's because he already adapted them to work with our phone (well, codeworkx recently changed build.sh and made it a little bit more universal). So I can simply run
Code:
./build.sh galaxysl
NOTE:
By default the kernel is not built from kernel/samsung/latona, the prebuilt one in device/samsung/galaxysl/kernel is used (you'll see a warning during the building process). This kernel is old if I'm not wrong, it doesn't have all the latest changes.
I usually build it separately and then replace it and the modules inside device/samsung/galaxysl/.
(remember that if you don't set up git correctly, the next time you'll do a repo sync you'll "loose" your changes)

I am getting this warning message:
while compiling cm9, i am getting the following warning
BFD: /media/Data/cm9/system/out/target/product/galaxysl/repack.d/ota/system/lib/storage.ko: warning: sh_link not set for section `.ARM.exidx'
what is this regarding?
Can any one enlighten me?

Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again

frapeti said:
Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again
Click to expand...
Click to collapse
To compile the kernel you go to the kernel/samsung/latona folder and run the ./build.sh and then build the ROM.
Regarding the WIFI, I have the same problem. I was able to build it, but the wifi seems not to work.

ganeshbiyer said:
To compile the kernel you go to the kernel/samsung/latona folder and run the ./build.sh and then build the ROM.
Regarding the WIFI, I have the same problem. I was able to build it, but the wifi seems not to work.
Click to expand...
Click to collapse
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there

frapeti said:
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there
Click to expand...
Click to collapse
I think you are using Alfrix kernel.
The default kernel for galaxysl from teamhacksung git does not use linaro.

frapeti said:
Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again
Click to expand...
Click to collapse
Regarding wifi issue I talked with dhiru.
He says to use dhcpcd from cm7.

frapeti said:
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there
Click to expand...
Click to collapse
I guess you are building alfrix's kernel
He switched to linaro. You need to download the toolchain separately if you want to use it.
EDIT 2:
... oh, I didn't see ganesh's post this time too...
ganeshbiyer said:
Regarding wifi issue I talked with dhiru.
He says to use dhcpcd from cm7.
Click to expand...
Click to collapse
I too had troubles with wifi at first, but I think in my case the problem was my router. It always gives me problems, I can't even keep my phone with the screen off and wifi on. It keeps the connection active with the router, but that's it, if I try to ping something out of my net, I get no response. (stock roms too)
Anyway, I was able to enstablish a connection with a static IP and now it works with DHCP too, but I didn't use dhcpd from CM7, weird.
EDIT:
Did more tests, it seems I have problems in getting the IP. Thanks for the headsup!
ganeshbiyer said:
I am getting this warning message:
while compiling cm9, i am getting the following warning
BFD: /media/Data/cm9/system/out/target/product/galaxysl/repack.d/ota/system/lib/storage.ko: warning: sh_link not set for section `.ARM.exidx'
what is this regarding?
Can any one enlighten me?
Click to expand...
Click to collapse
I had always got those warnings. You get them when you strip the modules.

Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7

nice
ganeshbiyer said:
Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7
Click to expand...
Click to collapse
nicee I hope I can make it work as yours, cheers. :highfive:
So the connection works but DHCP doesnt.
I'll try that and see what happens
Wich files did you copy from cm7 to add dhcp? / wich repo?
ganeshbiyer said:
I think you are using Alfrix kernel.
The default kernel for galaxysl from teamhacksung git does not use linaro.
Click to expand...
Click to collapse
loSconosciuto said:
I guess you are building alfrix's kernel
He switched to linaro. You need to download the toolchain separately if you want to use it.
Click to expand...
Click to collapse
Yes, I've moded the local_manifest.xml a little I'll try with the default kernel for now
There are some issues that I've found related to the cpu governors, i.e on-demand makes the battery last longer but seems like it makes the connection down or just cloud notifications down while certain amount of time with screen off. With conservative governor works just fine.

modded default.xml for cm7
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="korg"
fetch="git://android.git.kernel.org/"
review="review.source.android.com" />
<remote name="github"
fetch=".."
review="review.cyanogenmod.com" />
<default revision="gb-release-7.2"
remote="github" />
<project path="external/dhcpcd" name="CyanogenMod/android_external_dhcpcd" />
</manifest>

frapeti said:
There are some issues that I've found related to the cpu governors, i.e on-demand makes the battery last longer but seems like it makes the connection down or just cloud notifications down while certain amount of time with screen off. With conservative governor works just fine.
Click to expand...
Click to collapse
FYI dhiru's kernel has all the governors, waleedq included them when he took UC kernel sources.
Basically, after
Code:
make latona_galaxysl_defconfig
run (or edit build.sh)
Code:
make menuconfig
and under "CPU Power Management --->" do all the changes you want.

Worked like a charm thx u all!
Flawlessly built and running with the latest updates.
When I finish with exams I will look closer to that source stuff

hi friend seeing screen shot of cm9 compiled by u it looks u have got wifi icon in stautsbar working

+1 this. Is it static or working? (I saw a fake wifi signal workaround so i would rather confirm before celebrating).
Cheers. Congrats for successful compilation though

santoshsadani009 said:
+1 this. Is it static or working? (I saw a fake wifi signal workaround so i would rather confirm before celebrating).
Cheers. Congrats for successful compilation though
Click to expand...
Click to collapse
androman1507 said:
hi friend seeing screen shot of cm9 compiled by u it looks u have got wifi icon in stautsbar working
Click to expand...
Click to collapse
He posted the workaround in the "Theme and Apps" subforum, so I think it's fake
ganeshbiyer said:
Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7
Click to expand...
Click to collapse
I can see that CWM is under heavy developement and with your version (or maybe 6.0.6) I couldn't mount /emmc or /sdcard because of a missing trailing slash (koush fixed it now) and now CWM 6.0.0.9 erase my /system partition when I try to start a backup and I think it does something to /efs too (of course I have a backup of everything ), but I'm not sure if the problem is CWM or I did something wrong.
So, be carefull with this new recovery (anyway I like the new background :laugh
EDIT:
Ok, now I'm sure: /system, /efs and probably /sdcard (=external sd in CWM) are erased when you start a backup.
EDIT 2:
And gapps is missing after an update, it never happened. I think this is related to it.

3.4 kernel bring-up

By KitKat update for xt897/asanti being canceled, we're missing at least:
updated bootladers (sbl1,sbl2,sbl3 and appsboot), updated trustzone (not sure if that is an issue at this point), updated modem firmware.
Fortunately, at least the device tree for asanti seems to be ready and working fine, apart from not being handled by JB bootloader.
As a base, I'm using https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0 that has been updated by dhacker for support of KitKat updated Razr HD/M.
To circumvent dt not being handled, I'm using appended dtb:
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
Device tree partition check revealed that my device is p2 or p2b revision (https://github.com/MotorolaMobility...razrm/arch/arm/boot/dts/msm8960-asanti-p2.dts and https://github.com/MotorolaMobility...azrm/arch/arm/boot/dts/msm8960-asanti-p2b.dts are identical), so I'm using msm8960-asanti-p2.dtb appended to zImage.
Next issue is that bootloader is supposed to add dynamic data on runtime in addition to static ones loaded from dtb.
To get the display working, I've added:
Code:
chosen {
/* mipi_mot_cmd_auo_qhd_430 */
mmi,panel_name = [6d6970695f6d6f745f636d645f61756f5f7168645f34333000];
};
to msm8960-asanti-p2.dts.
That's where I'm currently. The next step is to add additional entries we're missing there (e.g. "mmi,mbmprotocol" etc.).
Regarding bootloaders, I see another issue - memory configuration.
There's failing shared mem allocation in mmi_unit_info_init:
https://github.com/CyanogenMod/andr...ob/cm-11.0/arch/arm/mach-msm/board-mmi.c#L433
That memory block is supposed to be reserved by sbl3, as indicated by https://github.com/MotorolaMobilityLLC/kernel-msm/commit/585b70b3fcd1af84edcb8748d1fdf190b32784af
Also, this commit https://github.com/MotorolaMobilityLLC/kernel-msm/commit/e3b9a040ca408d217a873df7994b9452ece04d16 indicates that Moto has done some tests also with older modem firmware, at least at some point...

If you need any logs or whatever from something not a Q, hit me up. Maybe something from my Atrix HD will help you out, I dunno -- AHD is stuck with JB until Q3 this year, so we're interested in this too.

Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)

mrvek said:
Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2778330

mrvek said:
Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)
Click to expand...
Click to collapse
1 - yes, I'm pretty sure that test builds for asanti exist somewhere in moto labs from the time before 4.4 upgrade for Photon Q cancellation, with updated bootloader images and stuff, that we will unfortunately never see (I'm not very good in social hacking, so I don't expect myself to be able to get access to that internal stuff).
I also noticed this commit - https://github.com/MotorolaMobilityLLC/kernel-msm/commit/14e5887c3db194ec1a8aa6145910f7c7b64f95dc - they did not have enough asanti p2 hw revision devices for testing, so they needed some fixes to be able to test on an older p1 revision of the hardware...
VijayKumar Gn surely wasted some of his time on 4.4 bring-up for asanti before it got cancelled...
2 - It depends on the level of stupidity Even some very bright ideas may appear stupid at first sight, but can get proved to be great in the end.
At this point, I'm still not able get the BP going, it goes to crash and restart loop as soon as it's brought out of reset by the PIL (peripheral image loader).
I've pushed the kernel commits I use so far here in cm-11.0-3.4kJBbl branch:
https://github.com/nadlabak/android_kernel_motorola_msm8960dt-common/commits/cm-11.0-3.4kJBbl
It should go with something like this kernel setting in BoardConfig.mk:
Code:
# Inline kernel building
TARGET_KERNEL_SOURCE := kernel/motorola/msm8960dt-common
TARGET_KERNEL_CONFIG := msm8960_mmi_defconfig
TARGET_KERNEL_VARIANT_CONFIG := msm8960_mmi_xt897_defconfig
TARGET_KERNEL_SELINUX_CONFIG := msm8960_mmi_selinux_defconfig
BOARD_KERNEL_IMAGE_NAME := zImage-dtb
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache androidboot.selinux=permissive androidboot.modelno=XT897 product=asanti_c androidboot.device=asanti_c androidboot.secure_hardware=1
BOARD_KERNEL_BASE := 0x80200000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02200000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12884901888

OK, good news, I've got the BP running fine now, under 3.4 kernel.

Just a little off-topic:
Do we have some indicators to differentiate between p1 and p2 devices?

kabaldan said:
OK, good news, I've got the BP running fine now, under 3.4 kernel.
Click to expand...
Click to collapse
AAAAAAAAAAAAAMAAAAAAAAZINNNNNNGGGGGGGGGGGG
cant wait for some first beta/test/kernel for a try ! thanks very good news very !

Loader009 said:
Just a little off-topic:
Do we have some indicators to differentiate between p1 and p2 devices?
Click to expand...
Click to collapse
You can check e.g. /proc/device-tree/[email protected]/[email protected] on your device.
If it contains [email protected], your device is P2.
If [email protected] is missing, but [email protected] and [email protected] are there, your device is P1.
It would be useful for me to know if there's actually a P1 device running CM11 out there somewhere.

Ok, P2 also here.
Is it possible that P1 devices are prototypes?
Someone here had a prototype, I wouldn't wonder if it was a P1 device.

@kabaldan this would work also with xt925 with JB bl.. Because Motorola will not release kk for us until Q3
If you need logs or something for xt925 count with me..
Sent from my RAZR HD using Forum Fiend v1.2.8.

kabaldan said:
You can check e.g. /proc/device-tree/[email protected]/[email protected] on your device.
If it contains [email protected], your device is P2.
If [email protected] is missing, but [email protected] and [email protected] are there, your device is P1.
It would be useful for me to know if there's actually a P1 device running CM11 out there somewhere.
Click to expand...
Click to collapse
...my photon is one of first and it is P2

p2 here too

P2 too...

Just to give a 3.4 kernel on Q current status report:
It's not stable yet. Occasionally, there's a kernel panic, usually when going to suspend state.
Will need to figure out the cause.
Otherwise, everything is basically working: radio, gps, nfc, wlan (while using the new wcnss firmware), bt, audio, camera, usb...

can this commit may help for our kernel-panic problem .?
https://github.com/edoko/Air_Kernel-NOTE/commit/5cd3f27ce5373fa3e84b7916480cebaa4ebc9df1

Kernel 3.4 working?
http://review.cyanogenmod.org/#/c/67589/

gehstock said:
Kernel 3.4 working?
http://review.cyanogenmod.org/#/c/67589/
Click to expand...
Click to collapse
If the Atrix HD is not running a 3.4 kernel yet, then no, it does not work. Be patient until something is announced.

@stargo , @Skrilax_CZ , @mrvek , @arrrghhh and others:
Sorry for the delay. I've been too busy at work and home again (surprise!).
Anyway, I've finally managed to push my current local mess to razrqcom, reusing the old xt897 and msm8960-common repos for tentative 3.4 kernel on JB firmware builds.
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="razrqcom-dev-team/android_device_motorola_xt897" path="device/motorola/xt897" remote="github" revision="cm-11.0-3.4" />
<project name="razrqcom-dev-team/android_device_motorola_msm8960-common" path="device/motorola/msm8960-common" remote="github" revision="cm-11.0-3.4" />
<project name="razrqcom-dev-team/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-11.0-3.4" />
</manifest>
The main issues remain the same:
- while the modem subsystem can occasionally work stable for tens of minutes, it can also get being restarted by watchdog bite in matter of minutes or even seconds (=too often).
- occasional kernel panic (NULL pointer dereference) at process_one_work coming immediately after hitting this warning https://github.com/CyanogenMod/andr...t-common/blob/cm-11.0/kernel/workqueue.c#L550

No worries, I'm extremely busy lately too with practically no time for this stuff. I'm in China atm. And it's very hot in here (real feel: 44° C).

[5.x] External Storage as Internal

Hi guys, i'm working on it
I use External SD as internal in lollipop, the question is if there are any risks doing that!!!
http://source.android.com/devices/storage/config.html#android_5_x_and_earlier
storage list xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<StorageList
xmlns:android="http://schemas.android.com/apk/res/android">
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_internal" android:emulated="true" android:mtpReserve="100" />
<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
</StorageList>
Check that please and tell me if there is any risk using it, if not, i'll upload it soon!!
If you want to use it in AOSP 5.1.1 last build
Try and report
Download and flash it
XDA:DevDB Information
[5.x] External Storage as Internal , ROM for the Moto E
Contributors
ivan290
ROM OS Version: Lollipop
Version Information
Status: Alpha
Created 2015-11-10
Last Updated 2015-11-10

the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")

brundark said:
the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")
Click to expand...
Click to collapse
Could you upload a logcat?

So if I flash this on top of my present ROM, Do I get access to external SD as internal storage?

brundark said:
the phone does not turn, I see only a black screen with a white line to the center
(like "updating applications")
Click to expand...
Click to collapse
To fix it you only have to wait until the android starts to "omptimize apps"

Is this working??? Or needs more work to be done??

Exactly what does this do?
Does it work without any issues?
Can we install heavy space consuming games?

confused.
where is the method?

Thread closed - members are advised to exercise caution with this.

[ROM] Unofficial LineageOS 16.0 PQ3A.190801.002] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22

many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj

new update is in the op.
just small changes and updated security patch level.

Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt

Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt

Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.

lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).

Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...

lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt

Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.

Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.

lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt

Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239

lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt

Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.

lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt

Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.

@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.

lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo

slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.

[DEV][WIP] brcmfmac wifi driver & qcwcn libs for MSM8974-based devices like Sony Shinano

The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac

As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?

I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.

nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.

Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?

Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!

TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.

Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK

.sorry erroneous post

New builds​Feedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.

Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.

Mr.Tom_Tom said:
New builds​Feedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?

netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.

Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.

Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything

navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!

Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?

navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi

Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now

navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.