Related
We now have a complete working build environment for CyanogenMod7.2 for the X1/kovsky.
Feature list:
* Phone works (SMS, calls, HSDPA, EDGE et al)
* Wifi works with open access points and WPA encryption. Signal meter is now working. (WEP does not work, you may get unexpected disconnects, and have to reconnect sometimes)
* Bluetooth works, but turning bluetooth off will drain your battery very fast. (You need to reboot stop this)
* GPS works with AGPS, but may crash your phone.
* Camera can take pictures. (No autofocus)
* Automatic adjustment of screen backlight
* About 40 hours battery life.
Issues we are working on:
* Fix bluetooth turn off bug
* Power usage
Issues that will probably not be resolved:
* FM-radio
This is based on SP3DEV/Alex's earlier work with lots of contributions from the rest of the community.
The android code is at: https://github.com/CoolrunnerII/
The kernel code is maintained by Zargloub at: https://gitorious.org/~poussevin/linux-on-qualcomm-s-msm/tp-alex-linux-xperia
If anyone feel they have the skill and interest to contribute directly to these repos please contact me and I may arrange with write permision for more people.
Precompiled releses can be found in the second post.
We have a google code page with a issue tracker.
Build instructions can be found in the google code wiki
20121001:
* First fix for wifi signal meter in wpa_supplicant. Signal level changes with distance from access point. I need feedback about absolute levels. (Should it read higher or lower?)
cm-7-20121002
20120920:
* Small change to wpa_supplicant.conf that may enable WEP access points. I can't test this at the moment, so I would like some feedback on this.
cm-7-20120920
recovery:
* with the same kernel as 20120919
* with Elibl's fixes for screen roation and font size
Mediafire: recovery.img
20120919:
* gps.kovsky.so with agps support (got some crashes when enabled with wifi)
* zargloubs latest kernel with my touchscreen fix.
* working camera
Mediafire: cm-7-20120919
20120902:
* Only change from 20120902 is libcamera.so
* Camera should work now. Using what I believe is the proprietary HTC Dream libcamera.so that has been included in all the other ROM's
cm-7-20120902 [broken]
20120831:
* First release with working GPS included
* Standard CM7.2
* Latest kernel from zargloub (without modules, if you need them you will have to flash a boot.img afterwards)
* RIL is working as far as I can tell
* Camera lib seems to be broken, but I haven't tested it all that much
* KNOWN BUG: When GPS is in use the touchscreen stops working.
* WARNING; There has been a reported boot loop caused by booting with gps enabled. I think I have fixed this bug, but havent tested the fix. If you end up in a boot loop you will have to enter recovery and flash a zip without gps.
cm-7-20120831 [broken]
Initial alfa release: cm-7-20120801
hi just for feedback: compiling recoveryimage works flawlessly for me you can see here. (i updated prebuilt_kernel, applied a patch and fixed some stuff in bootable recovery and added kovsky/recovery/recovery_ui.c)
as soon as i find a way to include wpa repo to local_manifest.xml i'll compile the whole build
furthermore we can update init files with the ones from neopeek. and i've got also some self-completed keylayout and keymap files for qwertz, qwerty and azerty on my machine that could be added (but needs more work for system integration)
for completing the environment i'm sorry i'm not yet that advanced in git and cm-source-code to help much on this i think...
(started my first environment 3 weeks ago or so)
so far...
When I compile on my system wpa compiles correctly.
What doesn't work is running "make bacon"
The error message I get is
Code:
running: imgdiff /tmp/tmpCfMuHH /tmp/tmp7uJUBN /tmp/tmpYGNi58
WARNING: failure running imgdiff:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 813, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 788, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 402, in WriteFullOTAPackage
MakeRecoveryPatch(output_zip, recovery_img, boot_img)
File "./build/tools/releasetools/ota_from_target_files", line 322, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
TypeError: 'NoneType' object is not iterable
make: *** [out/target/product/kovsky/cyanogen_kovsky-ota-eng.tob.zip] Error 1
CoolrunnerII said:
When I compile on my system wpa compiles correctly.
What doesn't work is running "make bacon"
The error message I get is
Code:
running: imgdiff /tmp/tmpCfMuHH /tmp/tmp7uJUBN /tmp/tmpYGNi58
WARNING: failure running imgdiff:
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 813, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 788, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 402, in WriteFullOTAPackage
MakeRecoveryPatch(output_zip, recovery_img, boot_img)
File "./build/tools/releasetools/ota_from_target_files", line 322, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
TypeError: 'NoneType' object is not iterable
make: *** [out/target/product/kovsky/cyanogen_kovsky-ota-eng.tob.zip] Error 1
Click to expand...
Click to collapse
here you can find interesting infos about lunch, brunch, breakfast and make bacon it looks like everything else than lunch is only for official supported devices...?
---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------
and here for flashable zip
dastin1015 said:
Or for a flashable zip:
Code:
$ make -j# otapackage
Click to expand...
Click to collapse
"make bacon" is an alias for "make otapackage"
It is an otapackage we need, so we have to figure out why it is broken.
I moved the build tools to a personal fork and removed the recovery image from the ota package python script.
"make bacon" now generates a valid looking ota zip file with upgrade-scripts and everything.
I haven't tried to flash this yet, and I am leaving town for a week tomorrow. If anyone has the guts to compile and test it I am very interested in hearing your feedback.
CoolrunnerII said:
I moved the build tools to a personal fork and removed the recovery image from the ota package python script.
"make bacon" now generates a valid looking ota zip file with upgrade-scripts and everything.
I haven't tried to flash this yet, and I am leaving town for a week tomorrow. If anyone has the guts to compile and test it I am very interested in hearing your feedback.
Click to expand...
Click to collapse
You can upload it and we will try
First zip up in second post!
Beware: it is completely untested.
Remember to use fastboot to flash boot.img after using the zip
CoolrunnerII said:
First zip up in second post!
Beware: it is completely untested.
Remember to use fastboot to flash boot.img after using the zip
Click to expand...
Click to collapse
you mean the boot.img from zargloub's post ?
Yes, i think he means this one :
june, 29th 2012
gf3ce616 http://www.file-upload.net/download-.../boot.img.html
Add commit from CoolrunnerII : "fix for the lost call bug."
Not tested.
Light_Sephiroth said:
Yes, i think he means this one :
june, 29th 2012
gf3ce616 http://www.file-upload.net/download-.../boot.img.html
Add commit from CoolrunnerII : "fix for the lost call bug."
Not tested.
Click to expand...
Click to collapse
I've tested for a while. It can make a call, send and get sms. Not test the GPS.
Camera is not work, only the preview mode.
Wake up is a little bit slow, not miss call bug.
I only tested the GPS with Test GPS and it is not working, it says that it is on, but the dot remains yellow instead of green, and it can't find any satellite.
Light_Sephiroth said:
I only tested the GPS with Test GPS and it is not working, it says that it is on, but the dot remains yellow instead of green, and it can't find any satellite.
Click to expand...
Click to collapse
yea, confirm that the gps icon doesn't come up with google navigation for screen wake up it's the same like in icedroid: untick everything in settings->cyanogenmod->display, especially screen-off animation
I have some good news:
I have working GPS on my phone now!
The problem was related to the nameing of the gps library.
I will post a rom with correct nameing early next week:
rename /system/lib/hw/gps.xdandroid.so to gps.kovsky.so and reboot to test on your phone
CoolrunnerII said:
I have some good news:
I have working GPS on my phone now!
The problem was related to the nameing of the gps library.
I will post a rom with correct nameing early next week:
rename /system/lib/hw/gps.xdandroid.so to gps.kovsky.so and reboot to test on your phone
Click to expand...
Click to collapse
Ow damn. I saw this but i didn't thought this could be the problem and didn't try it. What kind of stupid problem. But good Job crii.:thumbup:
Edit: i spent much time with trying to fix gps...
@crii: We need to have a look for the kernel modules from zargloub one's i think they still need to be implemented as the prebuilt kernel is only the zImage without modules...
Gesendet von meinem U8160 mit Tapatalk
That's true, just rename it and it works, tested with gps test and google maps navigator!
BUT there is one major problem: the touchscreen stops working when you activate gps and it will work again if you deactivate it.
Or, at least, this happens in IceDroid V8.
Does it work properly on your rom?
Light_Sephiroth said:
That's true, just rename it and it works, tested with gps test and google maps navigator!
BUT there is one major problem: the touchscreen stops working when you activate gps and it will work again if you deactivate it.
Or, at least, this happens in IceDroid V8.
Does it work properly on your rom?
Click to expand...
Click to collapse
I dont think it is the touchscreen per se, but something that lags everything down very much. I also noticed it.
I'll look into it next week.
I don't know, because you can use the phone with the buttons, with them i was able to open a MapFactor Navigator and set a route.
Maybe only the touchscreen lags.. we'll see
Light_Sephiroth said:
I don't know, because you can use the phone with the buttons, with them i was able to open a MapFactor Navigator and set a route.
Maybe only the touchscreen lags.. we'll see
Click to expand...
Click to collapse
Thats quite interesting...
If you could post logcat and dmesg logs that would be a great help
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.
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
Greetings.
So ever since (Late April?) the LineageOS 18.1 official builds for the Pixel 4a5g (bramble) stopped and are now on 19.1, I was curious to endevour into the world of building. I wasn't ready to upgrade to Android 12 yet and so I wanted to see if I could build an equivlent up-to-date unoffical "nighly" build for my device. BIG MISTAKE, haha. I had to go through many trial and error build runs having to deal with everything from out of memory (ram), out of hard drive space (200gb+!!), out of java heap space, build failed (after 12-18 hours!). Oh yea, and I'm doing this all on an AMD A-10 6800k (circa 2013?) with 16GB of ram but on a virtual machine w/ around 12GB of RAM and utilizing all 4 cores writing inside a 500gb VDI HDD vm container file with a 30gb /swap partition on Debian 11. Good times.
So anyhow, since I'm having to wait for these builds to finish, I can now qualfiy for Social Security. To those people with super-duper 8/10/16/32+ core cpu's with 32-64GB ram able to build complete roms within 40min to an hour (or 2)--I hate you.
So after all the trial and errors and LEARNING. I have finally been able to complete a build! At first I was missing vender blobs but was able to pull them with TheMuppets repo.
I followed these guides (substituting 18.1 for 19.1):
https://wiki.lineageos.org/devices/bramble/build (following just this would fail the build after a few eons with various errors)
(these 2 youtube vids helped me with creating roomservice.xml and pulling vendor blobs vs extraction via rom/firmware.zip or device).
Some of the errors during the builds (not necessessarly both as just one of these errors would stop the whole process. The errors are combined here for reference as these were obtained on a trial and error basis (Try this. fail. Try this...get little further fail, try this build suceeded with warnings, etc etc)
Code:
java.lang.OutOfMemoryError: Java heap space
ERROR:payload_generation_config.cc(200)] Sum of sizes in google_dynamic_partitions_partition_list is 4879237120, which is greater than google_dynamic_partitions_size (4873781248)
FATAL:generate_delta_main.cc(619)] Check failed: payload_config.target.ValidateDynamicPartitionMetadata().
It took around 18 hours for it to attempt to build and end with those errors, which were resolved by a couple 'export' commands I entered before re-running the build(s):
Code:
export _JAVA_OPTIONS=-Xmx2096m
or
Code:
export _JAVA_OPTIONS="-Xmx4g"
or was it
Code:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"
(my mind is a little mush so I don't rememer which one(s))
and
Code:
export WITH_GMS=true
re-ran brunch bramble and it compiled and only took about 40 minutes this time. Probally because I had ccache enabled per the build instructions.
YAY it built. But I am concerned about a couple warnings I recieved during the build process:
Should I be worried about these warnings? Can anyone advise?
Code:
depmod: WARNING: could not open modules.order at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.builtin at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.order at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_ramdisk_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.builtin at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_ramdisk_intermediates/lib/modules/0.0: No such file or directory
This is my first ever attempt at building LineageOS from source, so I'm a little proud of myself for making it this far. But any help on those warnings, if I even need to worry about it, would be appreciated. I have NOT flashed this new unoffical build yet.
Thank you!
* Logs can be provided upon request. I think there are many to choose from it seems in the /out folder.
If anyone wants to try it (and have courage I lack) here it is:
Downloads for : Google Pixel 4a 5g | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
https://www.androidfilehost.com/?w=files&flid=335433
Not sure if you have to wipe first since going from official to unoffical. I don't have encryption and staying w/i 18.1 so hopefully not. Regardless back up your phone. Flash/Install at your own risk.
Dont install this. Caused a boot loop and clearing cache didnt resolve. So reverting to backup. Oh well.
*Might actually work on a clean a wipe and reinstall of gapps.
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!