Anyway, many thanks for having a look into this !I have not found a link to the code in that thread, but I expect the rom not to work when you need a different TWRP.
Anyway, many thanks for having a look into this !I have not found a link to the code in that thread, but I expect the rom not to work when you need a different TWRP.
Merhaba,
[USER = 9583233] LumenReaper [/ USER]!
Çalışmanız için teşekkürler, efendim!
Söyleyin lütfen - Android 11.0'da yapılan Lineage OS 18.1?
Bu konunun ilk başlığında bununla ilgili bir kelime yok.
Cevabınız evet ise, bunun için Google Apps paketini nerede bulabilirim?
Sormak, çünkü https://opengapps.org/ adresinde Android 11 için hiçbir şey yok
teşekkür ederim
Interestingly, these problems occur on my tablet in lineage 17.1 .I've clean flashed Lineage OS 18.1 and I could see the internal storage now.
But however, I came across a 2 issues:
- The tablet sometimes turns off itself
- The tablet turns off itself and boots to TWRP randomly.
Because of these issues I've rolled back to Lineage OS 17.1 and I'll wait until Lineage OS 18.1 is really stable enough to use it daily.
Thank you very much, I'm glad you like it. I also only have the one tablet that serves as a production and development device. Everything possible stays on the SD card, so a clean flash is not too much work. Didn't know you could build it via Docker. Sounds interesting, but I'll stick with my VM.Great work Lumenreaper! (now I need to find the courage to install it on the only operational tablet that I own )
I did manage to build it myself using Docker & the docker lineeage-ci-cd image (see https://github.com/lineageos4microg/docker-lineage-cicd )
Mindthegapps is also still quite well-known.
Honestly, you're not making it easy for me to help you. I don't know which version of the tablet you have, but I have a screenshot of an error message in a language I don't understand. A log (adb logcat) would be helpful.Installed with a little error after every booting
View attachment 5300717
With a successful build, you are already well on your way. Have you compared the size of your zip file with mine? It should be similar, but not exactly the same size. If the size difference is significant, maybe you are still missing files?I succeeded to build the rom on my own and flashed it with the most recent TWRP 3.5.2
The tablet does not boot but falls back to recovery immediately. Currently restoring backup which is lineage 17.1 unfortunately.
Will try again the next days.
I have used Magisk with 17.1, but not yet with 18.1. Are we talking about using the power button to turn off the screen or shut down the device?I love the rom, but after using it for a while, the power button does not turn off the tablet and the tablet freezes. I am using magisk. I wonder if this question has anything to do with magisk.
Thank you LumenReaper
Glad to hear the internal memory is working for you now.I've clean flashed Lineage OS 18.1 and I could see the internal storage now.
But however, I came across a 2 issues:
- The tablet sometimes turns off itself
- The tablet turns off itself and boots to TWRP randomly.
Because of these issues I've rolled back to Lineage OS 17.1 and I'll wait until Lineage OS 18.1 is really stable enough to use it daily.
That will be interesting. After all, you two describe exactly opposite behaviour for 18.1. Personally, I had no such problems under 17.1 or in the last two weeks with 18.1.Interestingly, these problems occur on my tablet in lineage 17.1 .
What is the twrp version you installed lineage 18.1 and 17.1 on?
6] init: Control message: Could not find 'android.hardware.radio@1.4::IRadio/slot1' for ctl.interface_start from pid: 443 (/system/bin/hwservicemanager)
[ 116.534513] init: starting service 'vendor.camera-provider-2-4'...
[ 116.542324] init: starting service 'qti_gnss_service'...
[ 116.543826] libprocessgroup: Failed to open /dev/cpuset/camera-daemon/tasks: No such file or directory: No such file or directory
init: Control message: Could not find 'android.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint/default' for ctl.interface_start from pid: 443 (/system/bin/hwservicemanager)
05-07 10:19:19.269 1098 1098 D RILD : RIL_Init rilInit completed
05-07 10:19:19.269 1098 1098 I RILC : SIM_COUNT: 1
05-07 10:19:19.269 1098 1098 E RILC : RIL_register: RIL version 15
05-07 10:19:19.269 1098 1098 I RILC : s_registerCalled flag set, 1
05-07 10:19:19.269 1098 1098 D RILC : registerService: starting android::hardware::radio::V1_1::IRadio slot1
05-07 10:19:19.270 1098 1098 I RILC : RILHIDL called registerService
05-07 10:19:19.270 1098 1098 D RILD : RIL_Init RIL_register completed
05-07 10:19:19.270 1098 1299 E RILC : radioStateChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.270 1098 1098 D RILD : RIL_register_socket started
05-07 10:19:19.276 1098 1098 D RIL_UIM_SOCKET: Adding socket with id: 0
05-07 10:19:19.276 1098 1098 I RILC : RIL_register_socket: calling registerService
05-07 10:19:19.276 1098 1098 D RIL_SAP : registerService: starting ISap slot1 for slotId 0
05-07 10:19:19.277 1098 1098 D RIL_SAP : registerService: started ISap slot1 status 0
05-07 10:19:19.277 1098 1098 D RILD : RIL_register_socket completed
05-07 10:19:19.343 1098 1299 E RILC : oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL
05-07 10:19:19.429 1098 1299 E RILC : oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL
05-07 10:19:19.431 1098 1299 E RILC : currentSignalStrengthInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.431 1098 1299 E RILC : networkStateChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.446 1098 1299 E RILC : radioStateChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.447 1098 1391 E RILC : cdmaPrlChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.448 1098 1391 E RILC : oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL
05-07 10:19:19.450 1098 1391 E RILC : simStatusChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.450 1098 1391 E RILC : voiceRadioTechChangedInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.450 1098 1391 E RILC : currentSignalStrengthInd: radioService[0]->mRadioIndication == NULL
05-07 10:19:19.452 1098 1391 E RILC : oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL
05-07 10:19:19.457 1098 1391 V libsettings: [Command.cpp: 207] [rild(1098,1391)] getRegistry: > getRegistry: remote
05-07 10:19:19.458 1098 1391 V libsettings: [Command.cpp: 212] [rild(1098,1391)] getRegistry: < getRegistry:
05-07 10:19:19.458 1098 1391 E RILQ : [settings.cc: 75] [rild(1098,1391)] settingsd_client_update_iccid_card: Unable to find command update_carrier in registry remote
Honestly, you're not making it easy for me to help you. I don't know which version of the tablet you have, but I have a screenshot of an error message in a language I don't understand. A log (adb logcat) would be helpful.
Other than that, all I can say is that I've been using LineageOS 18.1 on my tablet (X704F) without Gapps for two weeks now and I don't get any error messages. Therefore, your error message tends not to come from my rom.
I've clean flashed Lineage OS 18.1 and I could see the internal storage now.
But however, I came across a 2 issues:
- The tablet sometimes turns off itself
- The tablet turns off itself and boots to TWRP randomly.
Because of these issues I've rolled back to Lineage OS 17.1 and I'll wait until Lineage OS 18.1 is really stable enough to use it daily.
This rom is for the Tab 10 Plus only.Is this a version of this or android 10 that works for the regular tab4 10 model tb-x304f ?
Congratulations on the successful build. Thank you for the logs.Build the rom again and now I am able to boot.
Attached you find the logs...
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
This rom is for the Tab 10 Plus only.
Congratulations on the successful build. Thank you for the logs.
If you have the time and interest, feel free to work on the current bugs. The code for the fingerprint and camera must be adapted, as it does not compile. This also means that the logs for fingerprint and camera are currently uninteresting because the code cannot be built yet, but this is the first step. If you're interested, more info by PM.
@Nuclear Blast Thank you very much for the information on the exact tablet you have. Please don't take offence, but your speculations about what the cause could be are not helpful.
As already mentioned, I need a log. The command for this is called logcat. If you don't know how to do this, which is not a problem, you can find many tutorials on the term online.
Please also note that I do not offer any assistance for further modifications to the rom like 3rd party kernels. This is also stated in the initial post.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.