yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] 0LDST4R:
Is anyone able to play NFS no Limits on our Z3C with Android 10? I tried both, CR and LOS 17.1 - no success. I tried nearly everything, game installs fine from Playstore or sideload, Google Play connects correctly, all required data is downloaded trough the game. Game starts, you can do everything, buy parts and so on. The problems start when you'll look into your garage. The cars don't load complete, game crashes without message, but NOT allways. Same happens when you'll start a race, in 1 of about 6 or 7 tries the race is loaded and you can drive, means you need many tries to get into the race, otherwise game crashes again.

I tried:

* with root

* with hiding the game by magisk hide

* without hiding the game by magisk hide

* without root

* with extsd inserted

* without extsd inserted

* with extsd inserted and data in intsd OR extsd

* in dev options tried the various gaming modes

* installed an older apk ( apk mirror ) and updated trough Playstore

* changed i/o scheduler and values

* changed cpu governor and values

* disabled zram/swap

* enlarged zram/swap

* took the game data and cache files from Android 9

* changed graphic settings with the "NLGFX tool"

* killed other apps before starting the game

* limited cpu frequency to prevent an overheating problem

I think that's all i've tried. How i wrote above, sometimes the race is loaded, but in most cases not. When you fortunately could drive a race it's impossible to race a second race. In very rare cases the race loads, but the graphics are ( i'd say ) half broken, your hud is visible, a few lights are visible, but the rest isn't there, no car, no buildings, no streets, no mountains, 95 % black screen.

I think there's a problem with the cached files, the game isn't able to load these data into the race OR the garage, OR the modshop to show these graphics. I'm out of ideas now, it's making me crazy because i don't find a working solution. It makes no difference if i'm on CR or LOS 17.1, any help or tips are welcome.
[Xperia Z3 Compact Original Android Development] Jimmy2k3:
Yo rom works great so far. Just installed today. Except for some reason I cant pull down my status bar when phone is unlocked in vertical mode. When the phone is locked pulling down status bar works. Anyone got a fix for that? I did a format before upgrading from Los 16.
[Xperia Z3 Compact Original Android Development] mister_r:
Hi all,

just switched over to this ROM from LOS 17.1.

Major props to you guys, my last two issues (GPS and echo during calls) are now finally resolved. That means my Z3C is my daily driver again.

Thank you so, so much :)
[Xperia Z3 Compact Original Android Development] mrmartischmi:
Dear guys,

thanks for you effort in building this ROM.

Did a clean install and everything worked fine, except main camera.

Selfie cam worked fine, but main camera did not, only showed black picture.

Tried with built in cam software and OpenCamera as well - same result.

Flashed LOS17.1 - everything worked fine as well as both cameras, no problems here.

Best regards.
[Xperia Z3 Compact Original Android Development] casouzaj:
Dirty flashed today´s build over the 0527 one. No problems with the back camera here, in any of those releases.
[Xperia Z3 Compact Original Android Development] mrmartischmi:
I dont have a clue...

Its a D5803, I made full wipes and format, like I made with LOS17.

So far, LOS17.1 works like a charm, no echo in calls or GPS probs here.

Regards
[Xperia Z3 Compact Original Android Development] fotofaningo:
No deep sleep after blootooth enabled

You`re rom works very fine, I'm using it since may! Thank you!

I've only one issue (using actual build from 20200617).

After I enable bluetooth the phone isn't going into deep sleep nomore, because of kernel wakelocks 'BTLowPower'. Also after disable bluetooth. Only restart the phone helps. Any tips?
[Xperia Z3 Compact Original Android Development] 0LDST4R:
Known bug since stock KK and LP in various devices, i noticed this in LOS 16 too. Nothing you can do, even SONY did not fixed this ( or care ;) ) You can google for it, you'll find some results...
[Xperia Z3 Compact Original Android Development] oimaraf:
Can't find the option to enable/ disable pixels of the display anymore!?

Could someone give me a hint?
[Xperia Z3 Compact Original Android Development] Myself5:
It's been removed for the Z3C in the latest update. It was never supposed to show there as it is useless on LCD screen and only profits from the way OLED screens display true black.
[Xperia Z3 Compact Original Android Development] oimaraf:
Thanks, but how can I disable it now?
[Xperia Z3 Compact Original Android Development] Myself5:
Either by using ADB:

adb shell settings put system smart_pixels_enable 0

or by using a shell emulator on the phone itself:

settings put system smart_pixels_enable 0
[Xperia Z3 Compact Original Android Development] oimaraf:
Thanks for you help, Christian,

this works with power saving disabled.

But I have forgotten to mention that I have smart_pixels enabled in power saving mode and I want to deactivate it for this mode.

Found the solution:

adb shell settings put system smart_pixels_on_power_save 0
[Xperia Z3 Compact Original Android Development] Italianhanno:
After installing todays build CARBON-CR-8.0-PAX-WEEKLY-z3c-20200624-0205

I get a Bootloop. Instead of showing rhe Lockscreen it boots back to TWRP.

Went back to CARBON-CR-8.0-PAX-WEEKLY-z3c-20200617-1000.
[Xperia Z3 Compact Original Android Development] corbeau56:
Same for me.

Greetings Form Germany.
[Xperia Z3 Compact Original Android Development] pawloland:
https://twitter.com/carbonrom/status/1275737484685606913?s=09
[Xperia Z3 Compact Original Android Development] deimidis:
Hello, thanks for this release. I'm very happy with CarbonRom in my z3c. Which is the best way to upgrade version? I tried several ways, but I always end having to wipe everything and starting from zero again. My current steps:

1- Download update via configuration in the phone

2- click on flash rom

3- Phone start on twrp flash build, restart on recovery again

4- stay there until wipe everything and install the Rom via sideload

What I'm making wrong?

Thanks!
[Xperia Z3 Compact Original Android Development] pawloland:
There are two things that might cause that. First and most possible one is that you have downloaded second latest build that has troubles booting up, but possibly has the same name AFAIK as latest one (see second post above this one). You may also have wrong twrp, so make sure you are using the one attached to this post.
[Xperia Z3 Compact Original Android Development] deimidis:
Thanks for your answer. I thought was the second option, because this happened with every version I tried. But after flash this twrp, I still have this problem trying to flash the new version. What other thing I need to try?

Thanks

---------- Post added at 03:39 PM ---------- Previous post was at 02:47 PM ----------

Solved, was that I had to install opengapps again. Now it worked
[Xperia Z3 Compact Original Android Development] gotoguy:
was it for for weekly update, install new one in twrp and also flash opengapps afterwards? without deleting anything?
[Xperia Z3 Compact Original Android Development] 0LDST4R:
Still no chance to get in the race with NFS No Limits. Game starts, you can do everything in the menu, but if you wanna drive a race the game fc without message. In LOS 16.0 it works fine. Any tips are helpfull, please read my earlier post what i tried to get in the race.

Greetz,

0LDST4R
[Xperia Z3 Compact Original Android Development] REISSUE:
Hello,

I can't install carbon rom pax or lineage 16. Twrp is saying error E3004: This package is for device: z3c; this device is aries.

However its a Z3 Compact mobile. I don't understand. Carbon Rom 6.1 noct is working.

Twrp version may be a bit older.

Can someone help me? Thy
[Xperia Z3 Compact Original Android Development] pawloland:
You helped yourself. You have wrong twrp.
[Xperia Z3 Compact Original Android Development] REISSUE:
Ah Okay

Thank you.

Is the update worth it?
[Xperia Z3 Compact Original Android Development] nikapos:
any ideas on how to port the fm radio app from another AOSP based rom? (titanium backup certainly didnt work... :) )
[Xperia Z3 Compact Original Android Development] xavier_843:
boot loop after weekly update

I have two Z3C and was for a long time a happy user of carbon rom 6.1 without any problems ever (despite horrible sound quality in phone calls).

End of August, both phones were entirely wiped and upgraded to carbon rom 8.0 and both were fine - but with the first weekly update one of the phones ended up in a boot loop. I wiped it again and installed the fresh version and all was fine until the next update. This week same procedure.

The second phone instead updated three times without problems. With the latest update today, also the second phone is affected and in a boot loop.

Can anyone confirm this and/or point me to a solution?
[Xperia Z3 Compact Original Android Development] Flitzepiepe:
boot loop after weekly update

Same for me. Happened with weekly update CARBON-CR-8.0-PAX-WEEKLY-z3c-20200902-0925.zip and the new one CARBON-CR-8.0-PAX-WEEKLY-z3c-20200909-0245.zip, too.

After installing updates, normally I have to reboot from TWRP. With both weekly updates the phone starts to reboot automatically and hangs before entering the SIM code.
[Xperia Z3 Compact Original Android Development] Myself5:
The automatic reboot would be expected. When the system reboots to twrp and automatically starts a flash via scripts (as it would do with an CarbonDelta update) it will also automatically reboot once installation is done.

Can you guys tell me which twrp version you use? I'll look into the issue asap.
[Xperia Z3 Compact Original Android Development] Flitzepiepe:
boot loop after weekly update

Hi Myself5,

my TWRP Version is 3.3.1-0.

I reinstalled CARBON-CR-8.0-PAX-WEEKLY-z3c-20200826-0627.zip and I have to reboot from TWRP. But after installing Carbonrom also Magisk is installed. Might that be the reason for the required manual rebooting?
[Xperia Z3 Compact Original Android Development] xavier_843:
Thanks for your support!

Both of my z3c have TWRP 3.3.1-0 and reliably do not stop the CarbonROM boot animation as soon as I install the latest update.

After wiping SYSTEM partition and installing 20200826-0627 and open_gapps-10.0-pico-20200831 everything is fine (until the next update).

---------- Post added at 01:13 PM ---------- Previous post was at 01:10 PM ----------

BTW: With the one that started making trouble with the two previous updates, I also tried wiping all partitions and wiping all partitions plus a new SDcard.
[Xperia Z3 Compact Original Android Development] Flitzepiepe:
boot loop after weekly update

Same issue with the last weekly update CARBON-CR-8.0-PAX-WEEKLY-z3c-20200916-1548.zip.

Tried it also on my second z3c where lineageOS 17.1 was installed. Did a factory reset and tried to install the weekly update mentioned above. Installation CarbonROM and Magisk seemed to be successfull, then I had to reboot but the simlock unlock screen is not reached and the phone shuts automatically down after a while.

As mentioned in a previous post I am running TWRP 3.3.1.
[Xperia Z3 Compact Original Android Development] xavier_843:
After ending up with two phones being unable to update, I installed NeoAdrians Lineage official build on that phone.

The TWRP recovery was not able to flash that image, so I flashed Lineage recovery replacing TWRP in recovery partition.

It today did the second update in a row without any problems.
[Xperia Z3 Compact Original Android Development] Flitzepiepe:
I could installed LineageOS 17.1 with twrp-3.3.1-z3c-20200212.img. I did it as described in the LineageOS Wiki.
[Xperia Z3 Compact Original Android Development] Flitzepiepe:
boot loop after weekly update

After having problems with all weekly updates since CARBON-CR-8.0-PAX-WEEKLY-z3c-20200826-0627.zip I could install the newest one. As described earlier the updates installed but the simlock screen was not reached after booting and the phone shut dwon after a while. Now I remembered that some apps do not run after an update due to conflicts with my installed substratum theme version (e.g. Whatsapp). So I deactivated my substratum theme completely. Now I could install the newest weekly udpate and the simlock screen is reached and everything works fine again! So the problem is solved and has nothing to do with the weekly udpates but with the substratum theme. I apologize for the trouble caused!
[Xperia Z3 Compact Original Android Development] Myself5:
Thanks for clearing it up after your found the cause and glad that you can finally enjoy Carbon. Now we only need to figure out what causes the issues for [MENTION=11102495]xavier_843[/MENTION]
[Xperia Z3 Compact Original Android Development] xavier_843:
stupid me - I did two changes at a time and now the second phone successfully updated to CR-8.0-PAX-WEEKLY-z3c-20201007-0512

A post in the z3c LOS thread mentioned that update problems were caused by opengapps.

I installed the same version of opengapps on the carbonrom phone as on the LOS phone, then wanted to install a update that previously failed but instead the new carbonrom update installed and phone booted and did not end in the usual boot loop.

btw: both phones show errors when writing ZIPs (e.g. carbonrom updates, opengapps) - "E:Unable to decrypt FBE device" - but work w/o problems.
[Xperia Z3 Compact Original Android Development] xavier_843:
again in a boot-loop

It is me again. After successful update last week, today's update brought back the boot-loop. This time the SONY logo only.

Wiping SYSTEM and installing previous version also ended up in a boot-loop - but with the CR logo.

Wiping SYSTEM and installing last know good version before previous version (26/08) also ended up in a boot-loop with the CR logo.

Only way out was wiping SYSTEM and restoring the backup I made with the previous version. Now phone runs w/o probs.

Any ideas?
[Xperia Z3 Compact Original Android Development] xavier_843:
It is time for a new feedback: versions from week before last week and this week were updating fine. All other versions (since 21/10) ended up in a infinite boot loop (SONY logo).

The only thing I changed was switching "safe mode" to "off" in CarbonROMs update settings.
[Xperia Z3 Compact Original Android Development] m0d:
I recently updated ROM and in setup it asks if you want to restore apps and data from backup.

This is an amazing feature, but which backups are supported? twrp?

Thank you
[Xperia Z3 Compact Original Android Development] ascendant512:
The only backup restore feature I saw when setting it up was the one that is built in to Android. I briefly checked to see if it supported the "transfer from another phone" option and it seemed to just exit out or crash. I expect it would work if you backed up to your Google account the way Android prompts you in the backup settings.

In other news, has anyone got device encryption working on this ROM? I upgraded from CarbonROM 5.1 (Android 7) with my device encrypted, and it failed to boot (after typing in the passcode, it rebooted to recovery automatically). That was disappointing, but not catastrophic. I formatted my /data to switch back from encrypted to unencrypted and "reinstalled" and it worked, but then when I turned on device encryption it only rebooted to a SONY logo. I tried a couple times and left it overnight, but it would only work after that if I did the power reset and reformatted /data to "unencrypt." The behavior was the same with a fresh /data + enable encryption: prompt for passcode, then reboot to recovery. I don't know what logs would be useful to provide, since there are so many reboots involved.
[Xperia Z3 Compact Original Android Development] Andrei001:
tell me what could be the problem with the wrong thing, the wifi wrote connected without access to the Internet, although your home network on another device works
[Xperia Z3 Compact Original Android Development] Samare:
Did you check with BetterBatteryStats (https://xdaforums.com/t/app-2-2-05-oct-v2-4-betterbatterystats.1179809/)?

I noticed heavy battery drain (the phone was getting hot, zero deep sleep) on every Android 9 et 10 roms.

I checked with BetterBatteryStats on the microG LineageOS 17.1 (Android 10) version and found out the culprit was the process media.extractor.

It turns out that happens because of some corrupt or unsupported media file on the microsd card or the internal storage. After removing the card, no more battery drain, so I have to check the files (the filesystem is ok).

Anyway, it seems like a bug in media.extractor.

Here's how I worked around it: https://xdaforums.com/t/official-lineageos-17-1-for-z3c.4160347/post-84723935
[Xperia Z3 Compact Original Android Development] f0k:
A few days ago I updated to CARBON-CR-8.0-PAX-RELEASE-z3c-20210220-0416 via CarbonDelta. Rebooting got stuck and then automatically rebooted to TWRP. When trying to reboot to the system, it again gets stuck and reboots to TWRP. I tried flashing 20210220-0416 and 20210127-2325 from within TWRP 3.3.1-0 (without wiping anything), but the result is the same.

Any suggestion on how to proceed from here? The previous update went fine. What changed in between is that I added an SD card as adoptable storage. I bought the phone second-hand with CarbonROM preinstalled, so I'm not too familiar with the installation process. Shall I wipe the system partition first or is it overwritten anyway? What will I lose when I do so? (I know now that I could have done a backup with TWRP before updating, but I didn't know before and wasn't particularly scared about updating.)

Side question: Is there a way to obtain the full kernel log to figure out what went wrong on booting? In /proc/last_kmsg I only find the end of the log file. I'm not sure if this is helpful: last_kmsg

Thanks for supporting this device and thanks in advance for any advice!
[Xperia Z3 Compact Original Android Development] Samare:
First do a nandroid backup in TWRP:

Enable compression and disable space checking (make sure the backup succeeds though - you can move files from your SD card to your computer from TWRP to make space). Space checking doesn't take into account compression.

Select the SD card (Select Storage) and backup Boot, Data, EFS and System:

It's even safer to copy the TWRP folder with the backup to your computer.

Wipe Dalvik + Cache:
[Xperia Z3 Compact Original Android Development] f0k:
Thank you for the nice guide! I had already tried that and got some error regarding formatting the cache. This time it went through fine:

E:Unable to decrypt FBE device
Updating partition details...
...done
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping Cache & Dalvik...
Cleaned: /data/dalvik-cache
-- Dalvik Cache Directories Wipe Complete!
Formatting Cache using mke2fs...
Done.
Updating partition details...
...done

Unfortunately, this didn't help anything. It's still getting stuck on booting and then resorting to reboot into TWRP.

Q1: Does it make any difference to wipe the system partition before flashing, or is the system partition overwritten with an image anyway?

Q2: Is there any way to obtain a full kernel message log, not just the part in /proc/last_kmsg?

Any other idea what to try? I'd like to avoid doing a factory reset, as I don't have a recent backup of everything. (I have an older backup of my apps, and a nandroid backup done after the failed update.) Thanks a lot in advance!
[Xperia Z3 Compact Original Android Development] Samare:
Q1: It shouldn't because most ROMs wipe it when installed. But you can try it anyway. If it still doesn't work, try wiping Data to make sure that ROM does work. Just make sure to not wipe Internal storage since the nandroid backup doesn't include it (folders like Pictures, ...).

Q2: Here's a list: https://android.stackexchange.com/questions/14430/how-can-i-view-and-examine-the-android-log

I'd start with adb logcat since your last_kmsg shows that adbd is started.

One thing to check is that you didn't let TWRP install its app after flashing the ROM (if it did in your version). I got a boot loop after that and had to remove the app using the File manager inside TWRP.
[Xperia Z3 Compact Original Android Development] f0k:
Thank you! I had already tried that, but adb is stuck at "- waiting for device -". Good spot that adbd is already running! Presumably it's not working because there's no UI for me to confirm debugging access on the phone. I never ticked the "always accept" box.

I was thinking of something to place in init.rc as suggested here: https://stackoverflow.com/a/25533212/12436673

That is, I've appended the following to my init.rc:

# write log to cache
service persistentLogging /system/bin/logcat -r 1024 -n 9 -v threadTime -b all -f /cache/logs/log
user system
group system log
disabled

on post-fs
mkdir /cache/logs 0775 system log
start persistentLogging

On rebooting, it creates /cache/logs with the correct permissions (so the mkdir command went fine), but it remains empty... Comparing with the manual, the logcat command looks completely fine: https://developer.android.com/studio/command-line/logcat.

Doesn't seem so, it's not in /data/app.

What I noticed is that the device issues a short click sound every few seconds while it's trying to boot. I hope it's not a hardware issue that wasn't linked to the update, but just came up because of the reboot.

Good idea. I'll try that when I'm brave enough.
[Xperia Z3 Compact Original Android Development] f0k:
Turns out it just required adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys, as explained on https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd#enable-adb-22-rsa-verification.

Now looking for the needle in my haystack...
[Xperia Z3 Compact Original Android Development] f0k:
Thanks a lot for the needle! If you send me your paypal address as a private message, I'll pay you a beer (or a piece of cake).

I'm not actually sure if I need GApps, and I'm wondering how it worked before. I found that com.google.android.gms was installed in /data/app. Following the error message and the documentation about allowlisting, I crafted a privapp-permissions-google.xml file and placed it in /data/etc/permissions (as the documentation said that it has to live in the same partition). That didn't change anything (maybe it would need to be placed in /system/etc/permissions anyway). I then simply moved away the app from /data/app to /data/tmp, rebooted and now everything's good.
[Xperia Z3 Compact Original Android Development] Samare:
Nice!

Indeed, if you didn't have it, no need to install it now. I thought it would have fixed the permission problem, but who knows.

No need, I'm happy to help!
[Xperia Z3 Compact Original Android Development] Piospi:
Hello.

I think I found a bug. Yesterday I downloaded the latest version of CARBON-CR-8.0-PAX-RELEASE-z3c-20210420-1310.zip and Open GApps pico + nano.

This is what my installation looked like:

1. Full wipe

2. Installation ROM

3. Wipe cache+dalvik

4. Installation Open Gapps Nano

5. Wipe cache+dalvik

I can't select the sound for alarm, SMS and calls. Just android.process.media crashes and the same goes for Open Gapps Pico.

I have tried installing the system and packages many times, but every time I try to select the ringtone the program crashes. Anyone had such a problem?
[Xperia Z3 Compact Original Android Development] ascendant512:
Bought new in box D5803, unlocked bootloader, flashed:

twrp-3.3.1-0.4-z3c.img

CARBON-CR-8.0-PAX-RELEASE-z3c-20210520-0416.zip

open_gapps-arm-10.0-nano-20210605.zip

Touched "encrypt phone" and it rebooted twice. Some difference in behavior from the above post is it shows the SONY logo instead of a black screen for the 1st and second boots. Manually reset phone and it booted the third time, encrypted
[Xperia Z3 Compact Original Android Development] hrsh45:
how should i install Magisk?

on Carbon 6.1 i had no problem flashing Magisk 21.4.

but when i tried Carbon 10 / 11, tried flashing several different versions of Magisk, the Magisk Manager app still say Magisk "Install: N/A",

i tried patching with boot.img but still same result :(