Database Info

[Backtrack5]Evo Guide (Sense)

Since msullivan's guide is generalized for all devices I thought I would tailor one specific for our Evo's.
I take no credit for any of this except for what is my own personal experience. 99% of the following has been taken from the original thread HERE
I have not tested this on an AOSP rom nor gingerbread for that matter. If anyone has confirmed it working I will add to the list. Supposedly CM7 cannot find the image file, if that's the case the resolve should be: In Android the "real" location is often /mnt/sdcard, and then the /sdcard mountpoint is added for simplicity. So yeah, my guess would be that Cyanogen doesn't have the /sdcard mount. You can fix your issue by opening the file "bt" in a Unix-compatible text editor (such as Notepad++, or an editor on the phone itself), and replace all instances of "/sdcard" with "/mnt/sdcard".
Working so far:
Froyo Sense (MynsWarmTPTRls5)
Evo Deck (gingerbread) 1.2f
CM7 (gingerbread) Thanks DoManOfFuture
WARNING: THIS IS NOT FOR THE FAINT OF HEART
UPDATE: My goal was to create a version of BackTrack 5 for ARM that was easy to use and install. As of this time, that IS NOT the case! The versions posted here are **probably not** going to work straight out of the box. If you know what you are doing in a Linux environment, you'll probably be able to get it working.
Because of this, the project is currently completely unsupported. You are free to dive in, but you are doing so with no support for me, and I'm not liable for any damage that might be done to your device's ROM.
I encourage you to pass this up unless you know what you are getting yourself into!
If you were referred here from the XDA-Developers.com article...
Hi there! Let's get one thing on the record here... this is *not* a native client! This is the chroot + VNC method that we'd been using to get Ubuntu running with Android for a while. The article makes it sound like that's the case, but sadly it's not. However, with the chroot + VNC method we can really run BackTrack 5 on an Android device, and it really does work. This takes some technical skills, and isn't for the non-Linux experienced user.
Requires a rooted device!
BackTrack 5 installation guides are making their way around this forum. I've tried to synthesize it all, but I've also added my own touches to help with usability and features, along with a workaround for the "ioctl LOOP_SET_FD failed" error message some people have been getting.
In theory this build is nearly universal, so if you have an Android device it should work. I've put it all in one zip file that you can download directly from my website, no hassles or wait timers.
If you are interested have a look, feel free to re-post. Credit goes to the BackTrack team and xda member anantshri (he's got skills, give him props guys), who built the base image file.
If you like what you see help me out, hosting is expensive!
http://www.mattslifebytes.com/donate
(alternatively, you can show interest in the products and services featured on my website, if you know what I mean )
Click to expand...
Click to collapse
Instructions:
BusyBox-
First things first you'll want some of the prerequisites one being Busybox. I'm currently running Myn's Rls5 Rom. All I had to do was go to the market and install "BusyBox Installer." Open that and install the latest version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Terminal Emulator-
If you do not have one go to the market and install "Android Terminal Emulator"
VNC-
You'll also need a VNC client. Go to the market and find a suitable VNC Client. "android-vnc-viewer" is a good one.
Starting Backtrack5-
After you have the zip downloaded you'll want to unzip it and place the "bt5" folder on the root of your SD Card.
-Next open your terminal emulator and type “su” <enter>, “cd /sdcard/bt5″ <enter>
-Now enter “sh bt” <enter> (in the future to start BT5 skip the line above and come straight to this command)
-enter "y" when it asks you if you want to start with VNCserver.
Note: I had already ran this before which is why your screen may look different
-Now all you need to do is open your VNC client and connect with the following info:
127.0.0.1:5901 pw: root
When you are finished go back to terminal emulator and type "exit"
Click to expand...
Click to collapse
DOWNLOAD:
Direct HTTP Links:
http://brilldoctor.co.cc/Files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
http://www.shenye.co.uk/files/BackTrack5ForARM-MattsLifeBytesEditionv2.zip
Mirrors:
http://www.megaupload.com/?d=M6YCKZLR
[/LIST]

Thanks
I'm running CM7, and am a very competent linux user so I'll give this a shot. I'll post back with the results. Doesn't seem complicated, well getting it running at least, maybe the build process was, but I'll get back with the results none the less.
Update: Works like a charm.

Updated compatibility list. If anyone is running a different rom and these instructions worked for you let me know so I can add it in. Thanks!

Just thought I'd mention, using your guide, this is running perfectly on my Nexus S running 2.3.4 (rooted, deodexed and zipaligned). I have the UI up in the VNC viewer and also can SSH in from my mac too.

Running BT5 on a Nexus S (9023i) with CM7 nightly 88 no problem. It is not very quick, but hey, it works.
Install was not to difficult at all, just download, unzip, run "sh bt", and connect with VNC

so i got it to work on ava-z3 but when in backtrack i tried to run console commands and it didn't work maybe i did something wrong or its just not supported for the phone may be someone can help if they can i was trying to crack my own wep and i have done it many times on my computer but when i tried it on the phone it didn't even recognized basic commands i get it you can run backtrack 5 but what are you able to do with your phone can annyone explain and advice me ?

*rubbing hands together* downloading now. Hope it works on the n1
Sent from my Nexus One using XDA Premium App

Just so you guys know you cannot crack WEP with this. This method CANNOT have direct access to your wifi card therefore it cannot support a lot of the methods used to crack, etc..
This is backtrack5 running on top of your android rom.
Just thought I'd make that clear to those thinking they have a mobile cracking OS That's what netbooks are for lol!

[TWRP][UNOFFICIAL] TWRP 3.7.0 for DOOGEE N20

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Requirements:
1-A PC with adb and fastboot installed.
2-Bootloader unlocked.
Instructions:
1-Install adb and fastboot on your PC.
2-Go to fastboot mode.
3-Download the twrp from the link below and transfer it to your PC.
4-Connect the device to the PC, and if everything is working type the command below.
fastboot devices
If everything is working a series of numbers will appear.
Now to install TWRP type the command below.
fastboot flash recovery TWRP-3.7.0-Doogee-N20.img
Ready, TWRP installed!
Now press Power + volume buttons up until restart, and select recovery mode.
Version Information
ROM OS Version: 9.0 Pie
Status: Stable
Based On: TWRP
Current Stable Version: 3.7.0
Bugs: data decryption is not working
Downloads: Here​

- Fixing error message "failed to mount '/usbotg' (No such device)"

Hey, I just wanted to say thank you. Me and a couple of friends that have this device are very grateful. And also, you know if this device have any custom kernel available?

kennymaroliveira said:
Hey, I just wanted to say thank you. Me and a couple of friends that have this device are very grateful. And also, you know if this device have any custom kernel available?
Click to expand...
Click to collapse
Unfortunately not

Deleted

-Updated to version 3.6.2
-Added fix in recovery.fstab
-Fixed the status bar

First of all, thank you for this port, good work my friend!
I'm having 2 problems with GSI on this phone:
1. Battery showing 2900mAh instead of 4350mAh on when you check the battery with any app like Ampere for example, and indeed lasting proportionally less than stock rom.
I tested with LeOS, from Q, R & S, CrDroid P, Q & R and PixelDust Q (what i'm using now), both with N20 and Y9Plus vendors, same problem...
2. Neither rom respect the notch, some old games seems to bug because of this, namely Void Pyramid and AM2R, no scaling correctly, at the moment i'm using wm on terminal to reduce my resolution to 1080x2120 to fix this, but is not optimal.
I'd like to ask if you know some way of fixing these bugs or at least a clue.
Thanks again, have a good day/night!!

Deleted

BionicKnight said:
First of all, thank you for this port, good work my friend!
I'm having 2 problems with GSI on this phone:
1. Battery showing 2900mAh instead of 4350mAh on when you check the battery with any app like Ampere for example, and indeed lasting proportionally less than stock rom.
I tested with LeOS, from Q, R & S, CrDroid P, Q & R and PixelDust Q (what i'm using now), both with N20 and Y9Plus vendors, same problem...
2. Neither rom respect the notch, some old games seems to bug because of this, namely Void Pyramid and AM2R, no scaling correctly, at the moment i'm using wm on terminal to reduce my resolution to 1080x2120 to fix this, but is not optimal.
I'd like to ask if you know some way of fixing these bugs or at least a clue.
Thanks again, have a good day/night!!
Click to expand...
Click to collapse
Hello, and thank you.
The battery capacity issue is caused by lack of overlay, you can install the zip file attached below, it will fix it (magisk module)
About the notch, I won't be able to help, until I can fix it in some games, but I don't have the files anymore

AtS17 said:
Hello, and thank you.
The battery capacity issue is caused by lack of overlay, you can install the zip file attached below, it will fix it (magisk module)
About the notch, I won't be able to help, until I can fix it in some games, but I don't have the files anymore
Click to expand...
Click to collapse
Thank you so much, long live AtS!!!!!

Sony Z3 Plus D6653

Hi I've unlocked the bootloader, what's the next step to root & flash twrp?

Hey there, what rom are you hoping to run? I'm on the D6603 and there hasn't been a new twrp for over a year (muppets release).
I'm running Lineage 18.1-20211230 rom & recovery for about an hour now.
Magisk would not install via flash for me, despite claiming success.
Digging around the issues threads I found the 'canary' or debug file works fine.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Specific issue (worth a read, you might face this again and you could always edit the boot_patch.sh yourself)
Magisk 21.2 cannot be installed on Sony Z1c with Android 10 Lineage 17.1 · Issue #3636 · topjohnwu/Magisk
Description The last Magisk version that could be correct installed was 20.4. All versions after 20.4 fail (from the first canaries to 21.2 magisk-debug_6d88d8ad). 1.1 Flashing magisk-debug_6d88d8a...
github.com
Good luck

Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
[MagiskInit] Support init.real on some Sony devices
Click to expand...
Click to collapse

z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others)
Click to expand...
Click to collapse

ns404art said:
do you have a contact i can call?
Click to expand...
Click to collapse
Not sure what you mean by this. Posting a quick answer. I'll edit it with more:
Magisk can be downloaded from; https://github.com/topjohnwu/Magisk
It is the ONLY place you should get it from!
Edit:
If you were hoping for a one-to-one, I'd rather type it out, just in case anyone else should come looking.
To be honest, you haven't provided enough information about your phone model or your desired goals for me to give you a straightforward answer.
I have experience with the D6603 only. I've been using lineage for about a year with different recoveries and, in my opinion, for the path of least resistance you should probably use a recovery and rom from the same project. (When I had twrp as recovery, OTA updates would fail, but not say so. It was only when commenting on a reddit thread, I thought I'd add my version number and discovered I'd gone months on the same rom. Manually flashing the latest rom broke stuff in all sorts of ways. So...)
Probably best to treat it as a rolling release and stay up to date or else lock-in to one you're happy with.
If using lineage, check update news first, if 'planned for next release' includes rollback of features just added - probably skip that update.
Gaining root was the last step for me. I have no experience of rooting SONY rom.
(My desired goal was to cut out google and play store).
Rooting was just;
1) Download Magisk
2) Rename .apk to .zip (DO NOT zip IT UP)
3) adb sideload, ignore checksum failure and choose install anyway.
The recent Magisk update has made it easier though. I was able to patch the boot file from within the app, so you possibly don't need to sideload anymore.
Right, that's a wall already. If you need more please include details such as;
Phone model :Sony Z3 Plus D6653 (2nd edit - oops just saw this)
Desired goal
Desired rom
/Edit

z3-puzzled said:
Just in case anyone finds this thread, Magisk has been updated to 24.0 with (amongst others);
Click to expand...
Click to collapse

I've unlocked the bootloader, what steps should I take to root and I'm planning to install a carbon rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I would follow the lineage install guide and change filenames where appropriate.
https://wiki.lineageos.org/devices/z3/install
If you intend to push on with twrp as recovery. see;
TWRP 3.3.1-Z3 Build 2020-02-12
This is the latest TWRP 3.3.1 build by The Muppets. This TWRP supports Android 8-10 for now. ROM recommended: LineageOS 16.0, LineageOS 17.1 and CarbonRom 8.0 Download: TWRP 3.3.1-Z3 or Mirror How to install: First of all you MUST flash...
forum.xda-developers.com
Which recommends, amongst others; Carbon 8. So old version
You could try latest lineage recovery & Carbon 9.
Your best bet is to ask within the Carbon thread;
https://forum.xda-developers.com/t/11-official-carbonrom-cr-9-0-enchilada.4313373
good luck

[ROM][OFFICIAL][discovery][12] LineageOS 19

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/discovery/install
Downloads :
https://download.lineageos.org/discovery
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

I'm gonna try to flash this today,
any gapps recommendation perhaps please?

also second question, does this rom recieves OTA updates?

maxis123 said:
I'm gonna try to flash this today,
any gapps recommendation perhaps please?
Click to expand...
Click to collapse
No.
maxis123 said:
also second question, does this rom recieves OTA updates?
Click to expand...
Click to collapse
No.

installed and rom is nice everything is fine, except.. Can't get connection to Internet, tryed reseting APNs, writing them on my own, can't get connection to Internet no way...

please ignore post above, turns out it was only my sim card issue..

Ty i will test it this weekend.

Awesome ROM, flawless!
Thanks for keeping this old phone alive.
But i hate the look of Android12...

michaaa62 said:
But i hate the look of Android12...
Click to expand...
Click to collapse
Yes, same here... I am building Android 11 (last amazing version IMO) for my Xperia 5 at the moment, I dont know how to port LineageOS 18.1 but I am building a SODP AOSP ROM atm.

May I ask if the system cannot be updated, have you deleted anything to keep the data?

I am facing issue with SIM2. only one sim is detected at a time.. Any help?

drakost said:
I am facing issue with SIM2. only one sim is detected at a time.. Any help?
Click to expand...
Click to collapse
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot

LuK1337 said:
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot
Click to expand...
Click to collapse
It worked! You are a life saver
Is it a temporary fix or permanent?

drakost said:
It worked! You are a life saver
Is it a temporary fix or permanent?
Click to expand...
Click to collapse
Permanent, now that you confirmed that my patch works.

LuK1337 said:
Permanent, now that you confirmed that my patch works.
Click to expand...
Click to collapse
It stopped working again after the restart... The same issue persists!

drakost said:
It stopped working again after the restart... The same issue persists!
Click to expand...
Click to collapse
Ehh, restart again? idk.

LuK1337 said:
Ehh, restart again? idk.
Click to expand...
Click to collapse
SIm 2 works and Sim1 doesn't.

Might be a bit late. Everything works now.. Took a few restart to fix this. But everything is fine now.
Thank you for the ROM. Amazing work!

first of all thanks for god job
plz i want ask you about crash of dvb finder and other apps on Lineage 19.1 how to fix that plz?

I was trying to sideload days ago from 16 to 19, but first boot never came out, it was just stuck on logo no matter how long I waited.. Any fix for that please?
also second question, long ago when 19 first became available and I tryed clean flash it and it booted, I had annoyance wich wasn't possible to turn off back then, it was when unlocking device with fingerprint it was vibrating everytime, so I'm inteteresed does 19 nowdays still vibrates when doing fingerprint unock ?? if does, can it be turned off somehow?
Thanks!
<3

[ROM][OFFICIAL][kirin][12] LineageOS 19

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/kirin/install
Downloads :
https://download.lineageos.org/kirin
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

How is it working? Is it stable? What's not working?

I'm using this and so far I didn't experience anything that don't work. However, it only works with NikGApps, if you want Google Play Services. And there are no OTA updates.
I also experienced problems with the manual update from the recovery. It broke my phone every time I tried. A factory reset needs after every update but it also erases all the data and the NikGApps.

Been using this ROM for weeks and so far it's been 99% functional. The only issue I had was for some reason the SMS permission for Google App Services did not turn on for a while until I finished setting other apps up. I'm afraid I don't know what made the permission turn on properly in the end sorry! Although it could well be the GApp distro had issues and not the custom ROM itself.
As for stability though, it's very stable. I'm using the l3113 model. Highly recommend to others! Good work OP, I've made a donation as a token of appreciation.

0

Message edited due to bad Google translation (sorry for the inconvenience).

Message edited due to bad Google translation (sorry for the inconvenience):
Hi, thanks for your great work, @LuK1337. I installed the ROM on March 27 on my i4113 and it works GREAT.
1. Today I saw that there is a new update on Android File Host, but the OTA update is not available, can it be installed without problems using Lineage Recovery?
2. What new changes will there be in this ROM on April 2-6? I had several problems to unlock, install TWRP, etc., on Xperia; So I don't know if it's worth me to update. (In my opinion, the Xperia is difficult to modify, not like a Xiaomi).
3. When will OTA updates be available? (If it will be available).
Thank you very much.

@LuK1337

更新完成后读不出sim卡 换卡也无效：哭：

Does the calls recording (both sides) work?

Hello thanks a lot for your work! I just tested the 20220426 build and everything works really well except one thing: I don't have mobile data on my french SIM card (Orange provider).
The latest 18.1 build from 20220412 works really well (so that's what I'm using right now) so I think there is something wrong on the 19 build.

Thank you. If I try to make a signed build on Debian 11 I get the following error:
Code:
signing: com.android.adbd.apex container (packages/modules/adb/apex/com.android.adbd)
: com.android.adbd.apex payload (packages/modules/adb/apex/com.android.adbd.pem)
Traceback (most recent call last):
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/internal/stdlib/runpy.py", line 72, in _run_code
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/__main__.py", line 12, in <module>
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/internal/stdlib/runpy.py", line 72, in _run_code
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/sign_target_files_apks.py", line 1420, in <module>
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/sign_target_files_apks.py", line 1401, in main
File "/home/user/android/19/out/soong/host/linux-x86/bin/sign_target_files_apks/sign_target_files_apks.py", line 577, in ProcessTargetFiles
KeyError: 'avb_avbtool'
Disabling APEX as described here results in boot loop.
Building and signing for another device works just fine.

double post.

Since Upgrad to v19 there is a big problem.... Regular Wifi Disconnetion and Reconnection each couple of seconds.
Wasnt the case with lineage 18
Edit: after a very long time (2 days or so), suddenly the sim cards get recognized / are active again. also wifi working more stabel. strange behavoiur.

Ermann123 said:
Since Upgrad to v19 there is a big problem.... Regular Wifi Disconnetion and Reconnection each couple of seconds.
Wasnt the case with lineage 18
Edit: after a very long time (2 days or so), suddenly the sim cards get recognized / are active again. also wifi working more stabel. strange behavoiur.
Click to expand...
Click to collapse
The problem still persists with new Rom updates.

Edit:
As the phone with 19.1 is extremly lagging, I went back to the latest 18.1 build, and with this: no lagging, and the sim cards are recognized and connected immediately.

Nice rom! Thank You!

Update: seems everything working correct except sound inside video recorder in camera, it did not record sound correctly! Hope it get fixed soon.

diyod said:
I don't have mobile data on my french SIM card (Orange provider).
Click to expand...
Click to collapse
I think you would have to set your APN settings in the phone to the ones provided by Orange. This is easily done in the Settings app (inside the "Network and internet" submenu).
munjeni said:
Update: seems everything working correct except sound inside video recorder in camera, it did not record sound correctly! Hope it get fixed soon.
Click to expand...
Click to collapse
Is the problem present in alternative camera applications (from F-Droid or Google Play) also?
By the way, this is a great ROM & lots of thanks to @LuK1337 !

Have a Sony Xperia 10 (I3123). After installing latest build for Kirin, I have data connection, but can not make calls. After dialing number, phone attempts to call, and then drops immediately without call being made. Have checked APN numerous times and settings are correct. IMS registration will not complete. Have tried on both GSM and CDMA networks. Both work on Stock Firmware. Have I missed something?