Database Develop

[BUILD] **Complete FroYo Bundle** FRX07.1 - Maintenance Release

Figured you TOPA folk needed your own thread... At least to track TOPA-specific issues!
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.

stinebd's Changelog:​
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse

Layman's Changelog​
(As in, the changelog I wrote )​
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup

Caveats:​
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
After booting, TOPA seems to have a crippling issue where if the first call is inbound, the phone reboots. So I guess after booting make an outbound call and everything is fine? Someone please confirm...
That audio routing thread is in the RHOD section, and I've only tested it on a RHOD - but AFAIK it should work on other devices. Let me know.

Whew, here you go TOPA folk!
I figured you guys needed a thread for this, if only to track issues that are TOPA-specific. Let me know what I need to add in the caveat section for TOPA! Also let me know if ts-calibration file is good or not .
Also, if you guys already have FRX07 running/working... there's nothing new here. Mainly using this thread as a place for newbie's to go and you experienced folk to help me track issues again for new users!

I have a small problem,when I run haret it comes to animated logo and then my phone go to rebote?

Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...

kujrv1 said:
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
Click to expand...
Click to collapse
Yes,that's right...

And solution...?

Use the latest kernel and rootfs, not the ones bundled with frx07.

kujrv1 said:
And solution...?
Click to expand...
Click to collapse
kujrv1 said:
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
Click to expand...
Click to collapse
hb5 said:
I have a small problem,when I run haret it comes to animated logo and then my phone go to rebote?
Click to expand...
Click to collapse
Sorry guys grab the latest kernel. I just put that in the caveat list, thanks.

I put the last kernel and i have the same issue. Reboot on Animated logo

I too have the reboot issue on animated start screen. Latest kernel used.
Any suggestions??

last three kernels didn't work on my topa100
it runs haret and then reboot the device

Will you guy's please make an effort and read other posts on this topic instead of clogging up the forum.
Everything you need to know has been posted already, multiple times.

Zaknahhas said:
last three kernels didn't work on my topa100
it runs haret and then reboot the device
Click to expand...
Click to collapse
gtti148 said:
I too have the reboot issue on animated start screen. Latest kernel used.
Any suggestions??
Click to expand...
Click to collapse
kujrv1 said:
I put the last kernel and i have the same issue. Reboot on Animated logo
Click to expand...
Click to collapse
Wait...
zooster said:
Use the latest kernel and rootfs, not the ones bundled with frx07.
Click to expand...
Click to collapse
Seems to make me think it's working on the newest rootfs and kernel - is this not true?

arrrghhh said:
Seems to make me think it's working on the newest rootfs and kernel - is this not true?
Click to expand...
Click to collapse
I've been switching my TOPA to FRX07 + .27 + rootfs (all selfbuilt) yesterday, and it boots up fine since the latest kernel fix.
So anything reported not working with latest autobuild kernel implies user error for me if it resets during bootanimation.
arrrghhh, thanks for taking care of the topa threads! So I can concentrate on not getting anything done for .35
Michael

arrrghhh said:
Wait...
Seems to make me think it's working on the newest rootfs and kernel - is this not true?
Click to expand...
Click to collapse
Topaz can boot with last kernel, with htc-msm-linux @ 20110718_223029 it doesn't.

zooster said:
Topaz can boot with last kernel, with htc-msm-linux @ 20110718_223029 it doesn't.
Click to expand...
Click to collapse
20110718_223029 is the latest kernel tho... are you saying emwe is lying? .
emwe - perhaps you should be like us heathens and try to run the pre-compiled binaries? I know, blasphemy...

Hi to all, is 2 day frx7 work in my topaz all work bt, wifi, 3g, lokscreen, rotate screen (no good) photo, opera, sms, gps an battery when is 10% work 6 hour, is speed. i like use android. thanks

[CLOSED][DISCONTINUED][STABLE][ROM] CyanogenMod 12.1 for SM-G530W/T/T1 | SM-G530FZ

ROM Information
ROM Target Device: Samsung Galaxy Grand Prime SM-G530W | SM-G530T | SM-G530T1 | SM-G530FZ
ROM Status: Stable
ROM OS: CyanogenMod 12.1
Maintainers: [ vince2678 ]
[*] Project GitHub Repositories: https://github.com/vince2678
Build Tracking & Download
CyanogenMod (CM-12.1): http://grandprime.ddns.net/jenkins/job/CM_Builds/
TWRP Builds:: http://grandprime.ddns.net/jenkins/job/TWRP_Builds/
You can track builds via RSS: http://grandprime.ddns.net/jenkins/job/CM_Builds/rssLatest
All the builds from above are testing builds, and as such, are likely to be extremely unstable or
unusable.
Nightly and Stable Builds: http://grandprime.ddns.net/builds/
Instructions
To flash an the ROM, you can either:
Download a zip archive from above and flash it from recovery by sideloading the zip (using adb sideload) or by
just copying it to the device (using adb push or MTP file transfer) and installing it. Instructions are below under
Zip Instructions.
Download a tar.md5.xz archive which can be flashed via ODIN. Instructions are below at ODIN Instructions.
After CM-12.1 is installed, flash either the GApps package linked above, or download openGApps, but only
the micro version, otherwise there will be app conflicts between the CM apps and the GApps.
After flashing an image successfully, simply check for updates from System->About to update thereafter.
Device Names
Verify your device codename before downloading any firmwares or recovery images!
SM-G530W - gprimeltecan
SM-G530T - gprimeltetmo
SM-G530T1 - gprimeltemtr
SM-G530FZ - gprimeltexx
Note
Do NOT ask for help/post issues if you:
Code:
[LIST]
[*] Have flashed mods (Xposed, etc);
[*] Didn't read the OP;
[*] Didn't follow intructions to the word.
[/LIST]
And most of all, I'm not taking feature or device requests.
Disclaimer
I'm not willing to help anyone who damages their device because they didn't take the time to read any instructions I may have written
up, and I'm not willing to do any hand-holding when it comes to flashing custom firmwares. I assume beforehand that you know what terms
such as "Odin" and "recovery" mean in this context and the basics of flashing firmwares using Odin and custom recoveries.
These packages are distributed in the hope that they will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I'm not responsible for any bricked devices, etc, etc, as a result of flashing these images. It is assumed that by downloading one of
these images you possess the prerequisite knowledge required to flash such firmware image.
Zip Instructions
[*] Download and install a TWRP recovery file for your device if you are on stock recovery. You will have to flash the recovery
.tar file for your device using ODIN (see ODIN Install below) or by using one of several applications from the Play Store such as
Rashr (will require a rooted phone).
[*] Download a recent .zip file from the links above for your device.
[*] Reboot into recovery mode [Press Power+Volume Up+Home].
[*] Wipe your data and cache partition (equivalent to doing a Factory Reset) if you are coming from a stock ROM.
[*] Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a
device, click Install on TWRP on your phone and locate the zip file in the phone, or:
[*] Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter
sideload mode. Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right
Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
Code:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type
adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
[*] Download and flash GApps in the same way (optional).
ODIN Instructions
The flashable images are hosted at the link above.
The directory contains tar.md5.xz archives. The tar.md5.xz archives are named according to the date the image was built, e.g
cm_gprimeltecan-ddmmyyyy.tar.md5.xz and can be uncompressed to yield the flashable .tar.md5 archive.
Each ODIN flashable .tar.md5 contains the boot image, recovery image, and system image for flashing.
Installation
[*] Enable Developer Mode on your phone and unlock the bootloader from the settings, if not done already.
[*] Download a recent compressed flashable image above.
[*] Reboot into Download Mode [Press Power+Volume Down+Home].
[*] Extract the tar.md5.xz archive with 7zip or `xz -d cm_gprimeltecan-ddmmyyyy.tar.md5.xz` if under Linux or Cygwin to get a flashable
tar.md5 file.
[*] Flash the tar.md5 archive using ODIN by clicking AP and selecting the .tar.md5 file you just
extracted. If the file was corrupted during download, the installation will fail. You will need to redownload the file in this
case.
[*] You will need to wipe your data and cache partitions afterwards (equivalent to a Factory Reset) if you are coming from a
stock ROM, which can be done by rebooting into recovery [Power+Volume Up+Home].
[*]
Download and flash GApps (optional).
TL;DR: https://www.youtube.com/watch?v=fbabglAX5Ho
Changelog
01/11/2016
* [ fixed ] NFC is now working.
* [ note ] This batch will be the last build(s) for CM-12.1.
30/10/2016
* [ G530FZ ] Changed kernel source
* [ G530FZ ] Rear and front camera should be working as @kentone said.
12/09/2016
* [ G530FZ ] Enabled LTE
* [ G530FZ ] InputDisabler should now be working fine.
* [ G530FZ ] Fixed up camera code in kernel. If rear camera still does not work, then this is an issue in
the proprietary files.
08/09/2016
* Added a few more frequencies to the cpufreq kernel table (overclock to 1209MHz, and addition of 1152MHz).
Please don't request for me to add anything higher; the CPU is rated maximum for 1209MHz (even with nitrogen cooling, and so on), so it is
impossible to go past this.
* Added the "Particle" charging animation from the stock ROM. Off-mode charging should be working proper as well.
* Fixed Viper4Android (module was not named properly when copied to system).
* Updated InputDisabler code (the software that turns your touch screen off when you call).
* Tuned Kernel Samepage Merging to be less agressive with memory page merging. This should fix the responsiveness issues that popped up
in the last builds.
* ZRAM is available for all devices (fixed at 512MB), but only enabled by default for the G530FZ. There's a post somewhere on how to
enable it in the thread.
* Patched the update zips from today's builds with an old updater binary (zip updates should work again). I removed the zips from
Jenkins so they're only available from the /builds/ directory on the root of the web server.
* Added a few more screenshots.
* Any other changes in the log are more concerned with refactoring of code in the device trees, etc.
05/09/2016
* Added new build server [Bilbo]
* Added Viper4Android as the default equaliser.
* In-call audio now working.
* TWRP is now the default recovery [in the ODIN images]
* [ G530FZ ] Fixed zram properties, added other low-memory tweaks
* Enabled dex pre-optimisation [= Faster app startup, lower memory usage, quicker boots]
* I dunno what else, you check and see.
01/09/2016
* [ G530W ] The sleep of death issue should be gone on the latest successful build, and the device should be
going into deep sleep properly. I have yet to resolve this for the other devices (probably in a few days).
31/08/2016
* Fixed InputDisabler
* Added qcom powerHAL (might hopefully fix sleep issue)
+ Various other fixes ( file access permissions, kernel tweaks)
29/08/2016
* Initial work on cpu undervolting.
28/08/2016
* Fixed MTP support in TWRP (if you use TWRP, reinstall it).
* TWRP now shows proper disk free space information.
* adb sideload now works in TWRP (may need to kill adb server and start as root to do so).
* Added new device (SM-G530T1).
* Added VoLTE support to SM-G530FZ (Still no in-call audio ).
* Added darkness cpufreq driver (from Mokee kernel) to kernel.
* Enabled ZRAM by default in SM-G530FZ.
* Trebuchet and System UI should be working properly now (ostensibly it requires hardware rendering,
which is disabled on low-ram devices by default).
+ There may be other minor fixes I missed here.
25/08/2016
* MTP is now working (properly)
25/08/2016
* MTP is kinda working (I'm investigating)
* Modem is now fully working on G530FZ (calling, audio, data).
* All sensors (gyro, magnetic, proximity) working on G530FZ.
19/08/2016
* Fixed WiFi tethering
* Fixed issue with WiFi and bluetooth MAC addresses (were not set properly at boot).
* Added Samsung Doze app
+ Several other minor fixes and tweaks
14/08/2016
* Kernel is now built entirely from source
* WiFi should be working again on all builds
12/08/2016
* TWRP recovery is now available (I will not bother servicing any issues regarding this if it doesn't work for you, it is included here
purely for the purpose of providing a different recovery to those that want one.)
* There do not seem to be any more sleep-of-death issues (this seems to have ended the last build).
* Over-The-Air updates are now possible, simply check for updates from System->About (after flashing this image).
03/08/2016
* Recents button is now working (thanks @Has.007 !).
* I'm not going to be uploading any new images because I'm currently working on getting the kernel to build from
source, and (I'm occupied with exams and schoolwork in general), so no new images are going to be pushed until this works properly (I had
to cobble this one together from a failed build on the custom kernel).
31/07/2016
* Added a few tweaks concerning CPU frequency scaling so there should be power savings from that as well as lowered device temperatures.
* Kernel Adiutor frequency scaling now works properly.
30/07/2016
* The previous update was buggy and kept crashing, I pulled that one and uploaded a new one which should hopefully fix that.
29/07/2016
* Minor tweaks
25/07/2016
* Both front and rear camera work as expected now.
* Trebuchet now displays the lock screen image properly.
* Trebuchet now displays full windows in the Recent Apps switcher.
* GPS is working
24/07/2016
* WIP - I had uploaded an image but I pulled it because filesystem mounting was broken in this build.
* I have pushed a new image, but something broke in the build which is preventing the sdcard from being mounted at boot by Vold (an
explicit entry had to be put in the fstab). I will be reverting changes and looking for a fix so there might be no build for the next few
days.
* Mobile data is now working in this build, but phone calls can still neither be placed nor received.
* System detects SIM card properly.
* GPS is not working.
* Rear camera works properly with the default camera app, however the front camera does not work with the default application and trying
to switch to it will cause the app to crash and refuse to open.
* Recents button is still not working (I had thought I fixed it but apparently it isn't working).
23/07/2016
* Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
* Screen brightness controls working
22/07/2016
* Limited mobile connectivity [ sending/receiving texts ].
Currently the system does not show the mobile connection as
active, but texts can still be sent and received.
* Fixed troublesome cgroups problem, meaning:
Apps can now be installed on the device; and
Apps no longer crash.
* Minimal camera capability - camera image is distorted, and only back camera works.
21/07/2016
* Wifi connectivity now available. [module has to be manually loaded - use adb shell su modprobe wlan ]
* Bluetooth is now working.
* GPS is working.
* Audio is working (microphone, speaker)
* Multimedia playback working
* Sensors are working (magnetic, rotation/gyro,proximity)
21/07/2016
* Initial image created.
Known Issues
======================================================================================================================================================================================
All devices
Format: [PRIORITY] Issue.
[LOW] FM Radio app is not working
======================================================================================================================================================================================
Click to expand...
Click to collapse
Issue Reporting
You can report issues with the ROM here on this forum.
Contribute
If you are familiar with Makefiles and the Linux shell, (optionally Java, C, C++) you can contribute directly to the
project by collaborating on working on the device and vendor trees.
You can also just download the ROM and report any issues and submit logcats.
Kudos
@Xenotoad for the extra build server [Bilbo].
ViPER520 and zhuhang for the awesome equaliser (Viper4Android).
@zim555 for the audio fix, and various other bits from his device sources.
@baran0119 who did some work on the G530FZ and on whose work the source is based on.
Screenshots
​

Here's the logcat for the kernel adiutor frequency issue. Let me know if there's anything else you need.

i'm new here but..
yesterday I installed this rom on my SM-G530W and I'm so happy with it. The front camera on default camera app is working perfectly fine. All that I desperately want fixed soon is data and calling :crying:

joe_5579 said:
yesterday I installed this rom on my SM-G530W and I'm so happy with it. The front camera on default camera app is working perfectly fine. All that I desperately want fixed soon is data and calling :crying:
Click to expand...
Click to collapse
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?

vince2678 said:
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?
Click to expand...
Click to collapse
It's working now glad its working. Thank you btw for this rom once again. Question: If you were to fix an issue, would i have to just update my cyanogenmod to get the issue fixed?

joe_5579 said:
It's working now glad its working. Thank you btw for this rom once again. Question: If you were to fix an issue, would i have to just update my cyanogenmod to get the issue fixed?
Click to expand...
Click to collapse
You mean update via the System Settings? This ROM is not officially supported by Cyanogenmod, so there are no Over-The-Air updates, but you can just come here and check to see if I have fixed anything else, and download the ROM and flash it. That would indeed fix the issue.

vince2678 said:
You mean update via the System Settings? This ROM is not officially supported by Cyanogenmod, so there are no Over-The-Air updates, but you can just come here and check to see if I have fixed anything else, and download the ROM and flash it. That would indeed fix the issue.
Click to expand...
Click to collapse
Thanks

vince2678 said:
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?
Click to expand...
Click to collapse
Hey @vince2678
I'm getting hot to flash this! Does this mean phone calling is working as well? Does sms messaging work as well?
I'm keeping an eye on your issue log but don't see (or recognize) an entry for this issue.
And I have been watching your repos and see that you have been busy!
Also, I've tried to build your ROM and I'm getting the error below. Is this as simple as adding another remove-project entry in the manifest?
+ make otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.6.4-301.fc24.x86_64-x86_64-with-fedora-24-Twenty_Four
HOST_BUILD_TYPE=release
BUILD_ID=LMY49J
OUT_DIR=/home/android/out
============================================
Checking build tools versions...
"ebtables is disabled on this build"
find: ‘dummy’: No such file or directory
build/core/base_rules.mk:154: *** platform_testing/tests/jank/webview: MODULE.TARGET.APPS.UbWebViewJankTests already defined by frameworks/webview/chromium/tests/UbWebViewJankTests. Stop.​

Zippy Dufus said:
Hey @vince2678
I'm getting hot to flash this! Does this mean phone calling is working as well? Does sms messaging work as well?
Click to expand...
Click to collapse
Hey @Zippy Dufus, SMS messaging has been working for a while, and mobile data has been working since the last two uploaded builds as well. Right now, the only troublesome aspect on the radio is the telephony, which isn't working as expected, but I am investigating the issue, and I *might* have a fix by tomorrow or the end of the weekend.
[/QUOTE]
I'm keeping an eye on your issue log but don't see (or recognize) an entry for this issue.
Click to expand...
Click to collapse
All issues RIL or telephony related on the Issues page are concerning this, so don't worry, I'm definitely looking into it.
One major problem in getting things to work is that most of the proprietary binaries or libraries on the stock ROM from qcom or Samsung are simply undocumented and as such it is difficult to understand what exactly needs to be fixed to get the telephony aspect of RIL to work fully.
And I have been watching your repos and see that you have been busy!
Also, I've tried to build your ROM and I'm getting the error below. Is this as simple as adding another remove-project entry in the manifest?
+ make otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.6.4-301.fc24.x86_64-x86_64-with-fedora-24-Twenty_Four
HOST_BUILD_TYPE=release
BUILD_ID=LMY49J
OUT_DIR=/home/android/out
============================================
Checking build tools versions...
"ebtables is disabled on this build"
find: ‘dummy’: No such file or directory
build/core/base_rules.mk:154: *** platform_testing/tests/jank/webview: MODULE.TARGET.APPS.UbWebViewJankTests already defined by frameworks/webview/chromium/tests/UbWebViewJankTests. Stop.​
Click to expand...
Click to collapse
I don't get this issue under my build. It looks like you have duplicate declarations for some tests in your build directory, could you try erasing all the code in your build directory and re-initialising it as follows:
Code:
cd /path/to/build/directory
rm ./*
repo -j sync
Making sure not to erase the .repo hidden directory in the build directory.
PS: I hadn't noticed this before, but it looks like you might have forgotten to do a . build/envsetup.sh && lunch cm_gprimeltecan_userdebug before running make -j otapackage, try that first, and if it doesn't work, then try resetting your build directory.

Is camera have bug with manual focus with flash or not?

snthe said:
Is camera have bug with manual focus with flash or not?
Click to expand...
Click to collapse
Hi snthe,
The cameras seem to be working correctly, if you have any issues, could you detail them more fully so that I can understand the problem?
Thanks.

vince2678 said:
Hi snthe,
The cameras seem to be working correctly, if you have any issues, could you detail them more fully so that I can understand the problem?
Thanks.
Click to expand...
Click to collapse
thx for your reply bro,but i not use your variant. I use 530H.
I ask that to u because on our cm12.1 camera when set to 8mp and use flash screen flickering.. This is the thread http://forum.xda-developers.com/gra...ailybuild-cm12-1-galaxy-grand-prime-t3345897/
Maybe u can help us to fix that if u not encountered that bug on yours

snthe said:
thx for your reply bro,but i not use your variant. I use 530H.
I ask that to u because on our cm12.1 camera when set to 8mp and use flash screen flickering.. This is the thread http://forum.xda-developers.com/gra...ailybuild-cm12-1-galaxy-grand-prime-t3345897/
Maybe u can help us to fix that if u not encountered that bug on yours
Click to expand...
Click to collapse
Hi,
Sorry, I don't think I can help, to fix such an issue I'd have to have the device to work with. You should ask one of the devs on the ROM to look for a solution to that.

settings>buttons>home button>double tap for recently used apps (until recents button is fixed)

Please try flashing this nd see if the Recent Key works.
I warn you to take a full backup before flashing.

Hello guys i've got a FZ Too and i'll help you to test this rom ! Thanks for porting this cyanorom on our grand prime !

This ROM is correct for daily usage ? :/

Okay so, i wanna dial *611 to top up my plan, but calls cannot be placed (i'm aware of the problem already) help?

MiQuenDroid said:
This ROM is correct for daily usage ? :/
Click to expand...
Click to collapse
Not quite, or rather, that depends on what and how you use it daily.
But, the short answer: Not yet (almost? ).

joe_5579 said:
Okay so, i wanna dial *611 to top up my plan, but calls cannot be placed (i'm aware of the problem already) help?
Click to expand...
Click to collapse
As of the image(s) from 03/08/2016, calls can now be made and received, BUT *audio* calls cannot be placed or received because the audio is not being routed correctly for some reason. Dialling USSR codes should still work fine.

[ROM][LINK] Sailfish OS Droid 4 maserati

I DID NOT MAKE THIS ROM!!!!!! - A developer by the name of TheKit made this rom, so do not give me any credit for this rom, give it all to them.
I am simply linking it because I love this phone, I love Sailfish OS on it, and I think a lot of people would enjoy Sailfish OS on it as well and just don't know it is available.
Q: "What is Sailfish OS and why should I use it?"
A: Sailfish OS is a great OS for many reasons. Having used multiple android roms I can attest to the fact that:
1. It has MUCH better battery life (however it has a weird battery read bug, see issues below)
2. It is MUCH faster and generally more stable when it comes to the things that work (your calls won't drop, your system won't lock up due to lack of ram, etc.)
3. It has a great gesture driven UI that is a joy to use and very gorgeous to look at. No more of this all white bull**** Google has been forcing down our throats since 2014
Q: "How good is the battery life?
A: After a day of playing cave story at work and reading discord and listening to music, I am at about 30-40% end of day (I start at 8:30AM, stop at 4:00PM)
Okay now that the Q/A segment is over, lets get to the real meat
ISSUES
1. Battery Read is wonky, it only goes in 10% increments until it reaches 20%, then it starts going in 5% increments
2. If you use the 2.1.3.7 build keyboard backlight is broken, but it works fine on the 2.1.0.11 build
3. Bluetooth is wonky, I was able to play audio through speakers in the 2.1.3.7 build...
4. FM Radio is broken too
5. As the maemo-talk thread says, CDMA is untested, and like on Photon Q, most likely does not work. GSM works great though! :good:
6. The old 2.1.0.11 build has a slew of issues compared to the new 2.1.3.7 build. These include data not working out of box, wifi requiring a reboot to work, and auto rotation not working in a majority of apps by default. Consult this thread and the maemo talk thread for more help, and if you want rotation anywhere, install patchmanager 2.0 and auto rotate anywhere from warehouse for sailfish os.
Alien Dalvik install tutorial
I did not make this and do not know who did. the developer claims someone threw a brick at them with an sd card attached. The sdcard contained links to these files in the form of a text file names "monkeyAIDS.txt"
https://drive.google.com/file/d/1mS6di1jYfVeDoFBjcANS6SmfkhGyEKoa/view - AD Jolla C (different from the Turing phone rpm, this is built for 3.1.x kernels)
http://sfos.scanf.su/maserati/alien-patched.tar.gz
So extract both files to your ~/ (home) directory and type in the following:
devel-su
[insert root password you set in settings]
zypper in [alien dalvik rpm]
rsync -a /home/nemo/alien/ /opt/alien/
ln -s /vendor /opt/alien/system/vendor
reboot
OPTIONAL: fix for the default 320PPI value
devel-su
[insert root password]
vim /opt/alien/system/build.prop
change ro.sf.lcd.density to the value of your choosing (Droid 4 is 256)
Keyboard Backlight Fix, works on 2.1.0.11, don't know about 2.1.3.7 -- Thank you @moodroid for this legendary patch!
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then do 'pkcon install mce' and 'systemctl restart mce'.
Download Links
Here is the thread with the Download Link to the 2.1.0.11 build
https://talk.maemo.org/showthread.php?t=99031&page=9
If you don't mind a lack of keyboard backlight and want a more up to date build, grab the new and fabulous leaked 2.1.3.7 Build:
https://drive.google.com/file/d/1k3MOCrMvbFb114Omf0MzSvnQ7wBkTiWH/view?usp=sharing
Basically if you are fed up with how ****ty the latest Lineage OS builds are and just want to try something new, give this a try. Why not? What have you got to lose. All in all great work by TheKit and I am very happy with the port as it is and I think you will be too.

Hi,
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks

moodroid said:
Hi,
On 2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks
Click to expand...
Click to collapse
dude you are a legend!
I would add that to the OP but you are first comment so anyone viewing the op will see this. I will definitely tell TheKit about this (then again, he gave you the 2.1.3.7 build so you can just tell them yourself)

Greetings,
I've been playing around with SailfishOS on my Droid 4 in the past few days, and I have a few questions about the whole thing. TheKit publicly shared a 2.1.3.7 build for the Droid 4 on his thread at Maemo, is that the one you are talking about or is it a different build? As someone mentioned this specific build seems to have issues with wifi, and I have the same problem. I can't post links, but the download link to the build I mentioned is on page 12.
The 2.1.0.11 build seems to work fairly well, however I wasn't able to install Alien Dalvik. After the installation the "Android Support" button does show up in the settings app, however nothing happens when I click the start button. I also attempted installing an apk both via the GUI (by clicking on it in the downloads) and via the command line by using "apkd-install", but it doesn't seem to work. Full log of the installation process attached.

I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).

NIKKOS said:
I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).
Click to expand...
Click to collapse
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again

moodroid said:
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again
Click to expand...
Click to collapse
No worries.
If anyone is wondering how to change the SailfishOS UI scale (I find the default one to be way too big) here's how I did it via the terminal:
Code:
devel-su
rm /etc/dconf/db/vendor.d/locks/silica-configs.txt
dconf write /desktop/sailfish/silica/theme_pixel_ratio value
I believe the default value should be around 1.1; you can also reset the value to stock with:
Code:
dconf reset /desktop/sailfish/silica/theme_pixel_ratio
or read the value with:
Code:
dconf read /desktop/sailfish/silica/theme_pixel_ratio
Not exactly droid 4 related, but thought I'd share.

Okay, I got the backlight to turn on!
Type the following in the terminal:
Code:
devel-su
echo 255 >/sys/class/leds/keyboard-backlight/brightness
It seems to properly react to some triggers like standby after being turned on but not to others like sliding the keyboard in and out (which means it will always stay on if the screen is on, regardless if it's been slided in or out). My assumption is that the keyboard sliding trigger got broken in some way, as I believe that's the way the backlight is being turned on. The events which trigger the backlight seem to be stored in the file /sys/class/leds/keyboard-backlight/trigger, so I assume that would be a good starting point to attempt fixing this.
The keyboard backlight intensity can also be changed, just change the 255 to a different value (it goes from 0 to 255).
Note: this change is not permanent, it will need to be applied again at reboot. Writing a script which executes the above commands at boot should be trivial though, and I will include instructions when I get it done myself.
EDIT:
Here's how to make the change permanent. Following these instructions you will create a Systemd service which will turn the backlight on when active and off when inactive; it will automatically run at boot and it can also be controlled like any other Systemd service (i.e. using systemctl via the terminal)
Type the following commands through the terminal:
Code:
devel-su
cd /etc/systemd/system
touch keyboard-backlight.service
chmod 744 keyboard-backlight.service
You will now need to edit the keyboard-backlight.service file with a text editor (either vim or nano will do, vim comes preinstalled, nano does not). Depending on your preferred text editor, type the following:
Code:
vim keyboard-backlight.service
or
Code:
nano keyboard-backlight.service
Now write the following to the file and save it:
Code:
[Unit]
Description=XT894 keyboard backlight service
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo 255 >/sys/class/leds/keyboard-backlight/brightness"
ExecStop=/bin/sh -c "echo 0 >/sys/class/leds/keyboard-backlight/brightness"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Now type the following to enable the service:
Code:
systemctl enable keyboard-backlight.service
That's it. You can now control the service by using the following:
Code:
systemctl start keyboard-backlight //This will turn the backlight on
systemctl stop keyboard-backlight //This will turn the backlight off
systemctl status keyboard-backlight //This will display the service status

Can anyone share the google drive file from the first post? Is there an alternative link available? Or could you PM me a google drive link? Thanks!

Can anyone suggest the best/correct ROM-slot size for TWRP?
Is it still like for CM/LOS:
800MB for system
10MB for cache
and rest for data as one likes?

[ROM][UNOFFICIAL][12][S]LineageOS 19.0 for z5c (suzuran)[ALPHA]

Hi all:
Here is a LineageOS 19.0 ALPHA ROM for Z5 compact (suzuran).
Download 2022-03-12
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 February 2022
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.6.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
Working:
Audio
Bluetooth
Fingerprint
FM-Radio (maybe it needs a few restarts before it's working)
German App AusweisApp2 (needs extended length NFC data; default in LineageOS 19.0)
LiveDisplay
Location services (see screenshot)
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
SMS
Sounds
WiFi
Please tell me...
Please keep in mind: This is an early ALPHA version and in permanent development status.
These things are NOT working (or badly working):
Camera
Encryption
Payment
Streaming (mirroring)
Maybe some more things are not working.
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

The SIM card recognition works now; please stay tuned.

Currently I'm fighting with a crash loop while trying to enter SIM PIN.
Seems this is going to be a longer fight...

Berni-0815 said:
Currently I'm fighting with a crash loop while trying to enter SIM PIN.
Seems this is going to be a longer fight...
Click to expand...
Click to collapse
Hello Berni
For a short time, I tried rom with a spare device.
I also installed NikGapps.
First, it doesn't recognize the sim.
I tried rebooting several times, but it doesn't recognize it.
Also, I can't move the app icon.
The safety net was fine with Magisk.
Please do its best.　

I haven't uploaded my latest changes because they are too unstable!

norabitox said:
I can't move the app icon
Click to expand...
Click to collapse
That's not a bug, that's a feature!
Long-press on an empty part of the screen and tab on "Home settings" and switch the first switch ("Lock layout") to the "on" position.
The logic behind this feature is reverse, so don't wonder.

Berni-0815 said:
That's not a bug, that's a feature!
Click to expand...
Click to collapse
Is that so
Thank you

New version out; see 1st post.
Now working:
Phone calls
SMS
WiFi
FM-Radio (maybe it needs a few restarts before it's working)
LiveDisplay
Offline charging
Notification LED

I could flash your android 12 version. recovery is changed to stock recovery, I reflashed twrp.
Welcome Screen was flickered, after 2 reboots I could create my profile on my z5 compact.
I had a lot of crashed on homescreen.
Call and sms are working.

Weird! I don't have any crashes! Could you please grab and send LOGs?

good work, does gapps work?

Thanks will try out this rom after awhile

Please don't forget: This is a very early ALPHA version! Don't expect any miracle!
And if possible, grab LOGs and search them for fatal errors (" F " <- a blank, a capital letter F and a blank) and for messages like "dlopen failed: cannot locate symbol".
I'm using "grep" for that:
Git:
grep " F " logcat > logcat.fatal
grep "dlopen failed: cannot locate symbol" logcat > logcat.symbol
...or like that...

Hi! Could you port this rom on sony Z5 premium?

I'm only building for suzuran (Z5 compact E5803, E5823)!
Please ask @Joel16 for further assistance.
He's the maintainer for Z5 premium.

Berni-0815 said:
I'm only building for suzuran (Z5 compact E5803, E5823)!
Please ask @Joel16 for further assistance.
He's the maintainer for Z5 premium.
Click to expand...
Click to collapse
Ok THX!

arpias said:
Ok THX!
Click to expand...
Click to collapse
Just an FYI until it gets into more of a 'beta' phase I won't be building android 19 for Z5P.

Joel16 said:
Just an FYI until it gets into more of a 'beta' phase I won't be building android 19 for Z5P.
Click to expand...
Click to collapse
Ok Joel, i'll wait for it, THX in advance!

New version out; see 1st post.
Android security patch level: 5 January 2022
Stability improvements: Removed IMS and VoLTE stuff due to too much weird errors.

New version out; see 1st post.
Sensors now working

[ROM][UNOFFICIAL][BETA][13][T]LineageOS 20.0 for z5c (suzuran)

Hi all:
Here is a LineageOS 20.0 BETA ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-26
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 13 (T)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Enforced SELinux support
Fingerprint (sometimes crashes)
GApps (tested: MindTheGApps)
German App AusweisApp2
GPS
LiveDisplay
Location services
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
WiFi
...please tell me...
These things are NOT (or badly) working:
Bluetooth
Camera
Encryption
FM-Radio (removed; causes crashes of bluetooth!)
Headset
Network Traffic Monitoring
Payment
Streaming (mirroring)
Torch
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Please keep in mind, that this is a BETA version and there are some things not or not fully working. The ROM feels a little bit sluggish too! Please don't expect miracles...
...but it WORKS!
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

Hello! Can you made this rom for z5 premium?

No! There is a maintainer for z5p, please ask him.

Berni-0815 said:
No! There is a maintainer for z5p, please ask him.
Click to expand...
Click to collapse
Okay, thx!

Awesome, thanks for the constant support to z5c!

New version (Halloween edition!) out; see 1st post.
No crashes any more; therefore I've bumped this version to BETA state
Bluetooth crashes no longer. A connection can be established, but it disconnects again immediately after connection; dunno why!
FM-Radio removed; it caused crashes of bluetooth
GApps are working! I've tested MindTheGApps

Oh! I've forgotten: Signature spoofing is now working!

Haven`t tested your new release on my old Xperia Z5C yet, but I installed unofficial LOS 20.0 in my Xperia XZ2, by @dtrunk90, and with his ROM, bluetooth A2DP/AVRCP profiles work pretty fine. Don`t know if the kernel plays a critical part on this matter. For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it. Thanks for giving our old little beast a new life, anyway!

casouzaj said:
Haven`t tested your new release on my old Xperia Z5C yet, but I installed unofficial LOS 20.0 in my Xperia XZ2, by @dtrunk90, and with his ROM, bluetooth A2DP/AVRCP profiles work pretty fine. Don`t know if the kernel plays a critical part on this matter. For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it. Thanks for giving our old little beast a new life, anyway!
Click to expand...
Click to collapse
Not sure if this helps but check the comments in https://review.lineageos.org/c/LineageOS/android_device_sony_tama-common/+/339303
For some reason switching BtAudio to AIDL breaks a2dp offload for some devices.

I've tried to reactivate a2dp. Unsuccessfully. It's now realized as a module and that's not the same as before.
casouzaj said:
For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it.
Click to expand...
Click to collapse
Feel free to port the kernel to 4.9 or anything else. We won't, because this really is a pain in the ass and could end in total frustration...

New version out; see 1st post.
Android security patch level: 5 November 2022

Los20 with MindTheGApps shows unreproducible random crashes. Until now I dunno why and I'm working on it.
But I think, it's not at my side and has to do with the (so my idea) early beta build of MindTheGApps...

I've tested on my Z5c with "NikGapps-go" yedterday and it work very well (store, mail, galery, map) without any crash.
MMS working after manual configuration of the APN (SFR).
The ROM is very smooth, more faster than lineage 19. Nice job!

Berni-0815 said:
it's not at my side and has to do with the (so my idea) early beta build of MindTheGApps
Click to expand...
Click to collapse
I've seen a lot of java illegal exception error messages; so, yes, its a problem at MindTheGApps' side.

Gadoin said:
I've tested on my Z5c with "NikGapps-go"
Click to expand...
Click to collapse
What are the differences between "core" and "go"? What does "go" exactly mean?

Berni-0815 said:
What are the differences between "core" and "go"? What does "go" exactly mean?
Click to expand...
Click to collapse
"go" apps are for low-end devices.
Apps run into navigator.

Navigator? Is that a kind of browser?

Oops i'm sorry for my english, i mean browser.
"go" apps runs into default browser.

Hm, our Z5C is now rather low-end, compared to today's flagships
So the Go version might be just the right thing. Sadly, I didn't get it to work on 19, and I'm still a bit afraid to switch to 20

NikGApps (I've installed the "core" flavour!) are working flawlessly indeed. Much better than MindTheGApps!