Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Curren Status
Working in 3.x
Wifi
Audio
Camera + Movie recording
Telephone calls / SMS
GSM Data
GPS
NFC
Encrypted /data
OMX video (HW accelerated playback)
Automatic display brightness
No screen on delay
A Video of the 4.4 Port can be seen at http://www.youtube.com/watch?v=zrc89NJfF0o (thanks to mestanr)
Known issues
Selecting a Mobile network manually will cause the 'Please wait...' dialog to stay even after the phone registered to the network. Just hit the 'home' button to make the dialog vanish.
Syncing the Calendar with google may not work on a fresh 4.4 installation. Reboot your phone 2 times and it should be fine. (Seems to be a gapps issue, there is nothing i can do about it )
Notes
The two famous CM-Bugs (2 second screen on delay / Loudspeaker issue) are (so far) not present
Do not spam the thread with 'bug reports' et al: Send me a patch! The sources are at: https://github.com/adrian-bl-yuga?tab=repositories
Download Android 4.4 for Yuga
NOTE: DEVELOPMENT ON XDA STOPPED - FOR UP-TO-DATE BUILDS PLEASE GO TO http://www.blinkenlights.ch/ccms/android/yuga.html[/COLOR]
Version 3.2 from 5. Nov. 2013 (download)
Again - New gapps package: http://android.eqmx.net/android/xperia/gapps_44_yuga_3.tgz. (Place it on /sdcard/ before flashing the update)
Nexus5-Style lockscreen
Include Launcher3 (AOSP Version of the new KitKat launcher)
Fixed fused location provider (for google-now and other stuff. Note that this will only work after google maps has been installed)
Version 3.1 from 3. Nov. 2013 (download)
New gapps package: http://android.eqmx.net/android/xperia/gapps_44_yuga_2.tgz. (Place it on /sdcard/ before flashing the update)
Fixed sensors (Orientation, Proximity, etc)
Stock gallery can now set the Wallpaper (Cropping is still broken, blame google)
Upgraded Kernel to 3.4.67, also includes fix for CVE-2013-2597
Support for USB-Mass storage / USB-OTG
Version 3.0 from 2. Nov. 2013 (download)
First release based on Android 4.4 - note that you must wipe your phone (eg: flashing userdata.img) before upgrading!
All Hardware (camera, audio, etc) seems to work OK, but there are still a few quirks (eg: shaky gapps package, sdcard issus). You should wait for 3.1 (and stay with 2.7) if you need a stable phone
Download Android 4.3 for Yuga
Version 2.7 from 12. Oct. 2013 (download)
Kernel upgraded to Version 3.4.65
Upgraded to Android 4.3.1 (JLS36I)
Grant write permission to external sd-card to applications
Changelog for older releases:
Version 2.6 from 21. Sept. 2013 (download)
Kernel upgraded to Version 3.4.62
Upgraded to Android 4.3_r3.1 (JLS36G)
Version 2.5 from 30. Aug. 2013 (download)
Kernel upgraded to Version 3.4.59
Fixed 'H-Icon-Missing' bug
Updated builtin APN list
Increased the max tab count in the stock browser to 64 (from 16)
Version 2.4 from 24. Aug. 2013 (download)
Upgraded to Android 4.3_r2.2 (JSS15Q)
New 'auto install' gapps package
Use pool.ntp.org by default
Keep screen off during USB Unplug
Version 2.3 from 7. Aug. 2013 (download)
Enabled 4G/LTE by default
Fixed compass and gyro sensor
Backported PR_{SET,GET}_NO_NEW_PRIVS feature to Linux 3.4
Version 2.2 from 1. Aug. 2013 (download)
Enabled additional scene modes + exposure in stock camera
Fixed AOSP Voice dialer
Enabled SE-Linux in kernel config
Builtin CWM recovery (press a volume button while the white LED is fading out)
Version 2.1 from 27. Jul. 2013 (download)
Enabled Bluetooth tethering
Added Nexus boot animation
Enabled UINPUT in kernel config (support for bt keyboards/mice)
Version 2.0 from 26. Jul. 2013 (download)
First build based on Android 4.3. Everything seems to work OK so far, but you should probably stick with 1.5 (4.2.2) for now if you really depend on your phone (the release only had a few hours of testing so far)
You are STRONGLY advised to do a full wipe if you are coming from 4.2.2 (fastboot flash userdata userdata.img)
You also need to update your gapps package to 'gapps.yuga43_shaky.tgz'. This gapps build is still based on 4.2.2 but was patched to not crash on 4.3
Version 1.5 from 18. Jul. 2013 (download)
This is the last (and most stable) release based on 4.2.2
Security: Fixed the 2 'master key' bugs
Option to finetune the screen brightness in Settings -> Xperia Z Settings
Installation / Upgrade
Extract the archive (unzip pabx_aosp_yuga*.zip)
adb reboot-bootloader
fastboot flash boot boot.img ; fastboot flash system system.img
If this is an initial installation, also run: fastboot flash userdata userdata.img # NOTE: THIS WILL WIPE YOUR /data - only do this on first-install
fastboot reboot
Please note that the system.img file does NOT include gapps - you can either install them manually or use my handy .tgz file to do it automatically:
Download my gapps package for Android 4.3 from http://android.eqmx.net/android/xperia/gapps_43_yuga_1.tgz
Download my gapps package for Android 4.4 from http://android.eqmx.net/android/xperia/gapps_44_yuga_3.tgz
Run 'adb push gapps_4?_yuga_1.tgz /sdcard/'
adb reboot
Your phone will now reboot twice: 1x to install gapps and 1x to finish the installation.
The gapps package is based on the 20130813 release from goo.im. And no: There is no need to upgrade the .tgz after a new gapps release as all included applications will update themselfes via google play.
Building from source
Everything you need is on github at: https://github.com/adrian-bl-yuga/device-sony-c6603
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.3_r2.x
# copy-n-paste the local-manifest from: https://github.com/adrian-bl-yuga/device-sony-c6603
$ repo sync
# Download the v3 blobs from sony and extract them
$ ( cd kernel/sony/k253 && ./_build.sh )
$ lunch full_c6603-userdebug
$ make -j 8
installed, working great (not so smooth like CM or other roms).
How about the Loudspeaker？
xingkongyuyi said:
How about the Loudspeaker？
Click to expand...
Click to collapse
when calling? its working.
How do you install gapps without a recovery? Through adb somehow? Instructions?
Changing the animations to .5 instead of 1x and forcing 2d animations made it much faster.
Thanks!
Edit: tried to do fastboot flash zip gapps.zip, and it succesfully flashed, but it didn't work.
Edit again: Never mind, the command wasn't allowed, I guess it didn't work.
Last edit: Manually installing .APK's resulted in quitting as soon as opened. I kind of suck..
Sebba513 said:
How do you install gapps without a recovery? Through adb somehow? Instructions?
Changing the animations to .5 instead of 1x and forcing 2d animations made it much faster.
Thanks!
Edit: tried to do fastboot flash zip gapps.zip, and it succesfully flashed, but it didn't work.
Edit again: Never mind, the command wasn't allowed, I guess it didn't work.
Last edit: Manually installing .APK's resulted in quitting as soon as opened. I kind of suck..
Click to expand...
Click to collapse
Convert the gapps into a tgz, push it to /sdcard. Then run adb shell and do:
mount -o remount,rw /system
cd /
tar -xvf /sdcard/gapps.tgz
...and reboot
I know that the gpu is somewhat laggy. Anyway: there are more serious bugs - this is just an early release.
Will test this as soon as I get my tablet Z will make my xperia Z a testing device
Sent from my C6603 using voldemort's nose
gr8,..less bug means nearly perfect...
What's the camera quality like? Same as the sony firmware that comes with the phone? or more like CM10.1?
Edit: Nevermind; gonna try it myself. always better idea.
---------- Post added at 08:57 PM ---------- Previous post was at 08:32 PM ----------
Also thanks for the effort put into this, been waiting since you posted in that other guy's thread for this
Lemagex said:
What's the camera quality like? Same as the sony firmware that comes with the phone? or more like CM10.1
Click to expand...
Click to collapse
No Idea: My phone was running Stock for less than 5 minutes
But i'm using the blobs from the 1.253 release - so the quality should be the same as in the latest stock release.
Btw: I'll be on holiday for about 10 days, so don't expect any releases/updates in the next few days.
It's the same as 5MP on the stock release, attempting to root and failing. if i figure that then atleast i can get a recovery up with XZRecovery.apk
pabx said:
I'm using the blobs from the 1.253 release - so the quality should be the same as in the latest stock release.
Click to expand...
Click to collapse
It's equal to 5MP on stock rom. Looking nice so far.
Lemagex said:
It's the same as 5MP on the stock release, attempting to root and failing. if i figure that then atleast i can get a recovery up with XZRecovery.apk
Click to expand...
Click to collapse
There is no need to root it:
run 'adb shell' and you'll have a root shell (the build was compiled with ro.secure=0)
pabx said:
There is no need to root it:
run 'adb shell' and you'll have a root shell (the build was compiled with ro.secure=0)
Click to expand...
Click to collapse
yeah but i still need superuser prompts for managing some apps with root for now it'll do fine
Coming from your AOSP build for the One X, I was holding out on a possible upgrade to the Xperia Z.
I might just have found a compelling reason to upgrade after all!
G23 Mr Gimp said:
Coming from your AOSP build for the One X, I was holding out on a possible upgrade to the Xperia Z.
I might just have found a compelling reason to upgrade after all!
Click to expand...
Click to collapse
You took the words right out of my mouth..... I too used to run pabx's rom on my One X.
I am really looking forward to the development of this ROM. Good to see you on the XZ scene pabx!
Nice rom, hope to see a new version soon, getting another Z (probably) so I can help out developers in this forum on testing
Sent from my C6603 using voldemort's nose
Ok, i've uploaded a new Build (1.0) - it still has some quirks but it is VERY useable: All Hardware is working.
I still need to fine-tune some stuff (power HAL and governor) but version 1.0 is already 'production ready'
Big thanks for your hard work. I`ve tested your previous version about 1 hour, but was not satisfied with youtube. Also complained about the missing recovery for flashing the gapps. Don`t get me wrong. I love Linux, adb and the command line, but flashing the gapps is so comfortable. Will test your new version soon, but for now I will stay with CM-10.1 where I`m complaining about the 2 seconds delay after you hit the power button
pabx said:
Ok, i've uploaded a new Build (1.0) - it still has some quirks but it is VERY useable: All Hardware is working.
I still need to fine-tune some stuff (power HAL and governor) but version 1.0 is already 'production ready'
Click to expand...
Click to collapse
what is powerhal?
*THE TOOL IS UPDATED HERE, HOPEFULLY WILL FIX WHATEVER PROBLEM YOU HAD, WHATEVER! *
Hello and welcome ! , I wanna play a game :silly:
This tool made specially for noobs & lazy guys , as some of us hate working with any command prompt -and ADB/fastboot are command prompts- so they avoid using it , even if they needed to!
now forget that , this tool is the simplest Graphical user interface ADB,
which will grab popular ADB & Fastboot commands in simple combobox to use
Features..!
My tool is featured in XDA-Portal . Tab Here
Main Features
this tool is written in java, which mean the simplicity , the smallest size and the fastest functions!
this tool depends on your PC , it does nothing on it's own , that makes it very small (about 45 kb!) but powerful
Currently this tool is my only active project , so i'm working on updating it ASAP :good:
Features for human being (to use)
my tool does the most popular/important pure ADB & fastboot operations ,
these operations are :
Check if Device connected properly (adb devices).
Android Logcat.
Install a specific APK file(Android Application).
Uninstall apk <package> .
pull a file from your Android Device to your PC.
push a file from your PC to your Android Device.
Look at tasks running in your Android device.
Check your Android Device Memory usage.
Check your Android Device storage usage.
Kill all background processes.
Normal Reboot.
Reboot to recovery mode
Reboot to Download mode (for Samsung Devices).
Reboot to bootloader mode.
Reboot to Fastboot mode.
Unlock Patterns/passowords with two methods
Flash Update.zip.
Flash recovery.img.
Flash boot.img.
Wipe (System,data & cache) before restoring nandroid backup.
Flash system.img.
Flash data.img.
Flash cache.img.
My tool UI is very simple and easy to use , it's just about 300 x 450 JFrame
Requirements..!
You need JRE (the JAVA Runtime Environment ) to run the Tool , you can get it from here .
ADB / Fastboot in your PC (are you kidding?! :cyclops: ).
USB Debugging enabled in your Android Device.
a Human brain which can read the 'How To' in this Thread.
How to & Downloads..!
Download the "ADB For noobs STABLE V3.0.jar" FROM HERE (or in Downloads Tab up) ,
open the downloaded file and set your ADB directory and click Set Data button (you must do that at least once), to make the tool know where's your ADB to use it.
Select the desired operation , and add required directories , then tab Activate , and that's it ! , isn't it Simple ?! :good:
use Reset button to reset text fields
Screenshots...!
the Final release (3.0) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Old Version (2.5) :
Older Version (2.0) :
Even older Version (1.7) :
Or see the Screenshots Tab up.
How to help ?....
at first thanks for clicking "Click To Show Content" Button , that means you really want to help me :fingers-crossed:
Testing is the best method to help me.
you faced problem while using my tool ? let me know in the comments.
You have Suggestions ? .. PM Me with your suggestions .
you miss some adb/fastboot functions ? , feel free to request :good: .
DON'T FORGET TO CLICK MY
BUTTON .
Changelog...!
Code:
* 29 - 01 - 2015
the final release (3.0)
-fix : a few problems in the UI .. and a simple touch to the code.
-added : unlock patterns/passwords with 2 methods.
Note : no need to say that this update is just to leave that project sleep in peace , it just fixes some mistakes that I couldn't fix them because I didn't had enough time.
* 15 - 06 - 2014
release (v2.5)
-this version will give you the UI that you deserve ,look and feel is better and more simple than before.
-many pure ADB operations optimized.
-setting my data is more reliable (i'v optimized the code to get rid of these (Apk_dir.txt , P_dir.txt ....etc).
-reset button added (to reset text fields).
-the problem of (confirm dialog) that repeat the operations fixed.
-check updates button added (will open this thread's link).
-now all operation that returns output like (logCat , adb Devices.....etc) will store their logs in .text files.
-tool size reduced from 60 kb to 38 kb , lol .
* 10 - 06 - 2014
the third release (v2.0) :
-this version has several UI optimizations to make things 80% easier than before.
-many code problems solved , problems with some operations solved.
-storing all data in one folder ("Data") to make the look unique.
* 05 - 06 - 2014
the second release (v1.7) :
-code optimization , fixed 2 tools problems.
-now the adb / fastboot command prompt will close immediately after finishing an operation, except in memory/storage usage and logcat.
-new adb & fastboot options are added :
-Kill all background processes.
-Reboot to recovery mode.
-Reboot to Download mode (for Samsung Devices).
-Reboot to bootloader mode.
-Reboot to Fastboot mode.
-Flash Update.zip.
-Flash recovery.img.
-Flash boot.img.
-Wipe (System,data & cache) before restoring nandroid backup.
-Flash system.img.
-Flash data.img.
-Flash cache.img.
-the tool will create folder called patch to store all my .bat scripts in it.
* 03 - 06 - 2014
the initial release (v1.0) .
Credits...!
My Friend @kermage .... thanks for helping and Suggestions :good: :fingers-crossed:
My Friend Yusuf Badr ... thanks for Testing :good: :fingers-crossed:
XDA:DevDB Information
ADB for noobs (GUI ADB/Fastboot), Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2015-01-29
Current Beta Version: 1.7
Beta Release Date: 2014-06-03
Created 2014-06-03
Last Updated 2015-01-28
Reserved
supposed to be reserved for unknown thing , who cares!
apple pie
DON'T FORGET TO CLICK MY
BUTTON .
Amazing work
Nicely done :good: :good: keep it up
Up!
Good job! :good:
But maybe on the next update, try to make it really for noobs & lazy guys; a 1 tool, installation/settings in the first run.
kermage said:
Good job! :good:
But maybe on the next update, try to make it really for noobs & lazy guys; a 1 tool, installation/settings in the first run.
Click to expand...
Click to collapse
i understand that you mean Setup window at first run .. but this will make the app for windows only , also you just need to run the 1st tool just once , then you can just delete it , but i'll try my best to make it easier , btw , before a day from making this thread , it was so dummy and you should add your adb dir every time to run it , as this pic : http://i.imgur.com/xbwtquz.jpg
btw , what about it's operations , you find any thing bad ? thx very much for your help and report
EDIT: Oh , i think i got an idea .. next update will solve this , also will have more operations , may be fastboot commands too
Mohamed Hashem said:
i understand that you mean Setup window at first run .. but this will make the app for windows only , also you just need to run the 1st tool just once , then you can just delete it , but i'll try my best to make it easier , btw , before a day from making this thread , it was so dummy and you should add your adb dir every time to run it , as this pic : http://i.imgur.com/xbwtquz.jpg
btw , what about it's operations , you find any thing bad ? thx very much for your help and report
EDIT: Oh , i think i got an idea .. next update will solve this , also will have more operations , may be fastboot commands too
Click to expand...
Click to collapse
No need for setup window, use java ini/properties file instead.
new update is out , check the changelog and Screenshot :good:
Now that the Gear has moved from Android to Tizen we need a modded version to work with SDB instead of ADB.
Mohamed Hashem said:
new update is out , check the changelog and Screenshot :good:
Click to expand...
Click to collapse
Are you missing a DLL file from your Java Program? I'm getting Java errors stating it can't find the main class of the file. I'm running Windows 7 32-Bit and Java 6 Standard Edition installed.
how can i use it to flash twrp or cwm img file to my phone??
Would be perfect if it had a feature to batch install apks.
jman1234 said:
Would be perfect if it had a feature to batch install apks.
Click to expand...
Click to collapse
sorry didn't understand that .. i mean it had "install apk" option , but what do you mean with batch install apk ?
mashnino said:
how can i use it to flash twrp or cwm img file to my phone??
Click to expand...
Click to collapse
just add the file you want to flash in the 1st text box called "select file to install / flash / push and then select the option from combo box
rootdefyxt320 said:
Are you missing a DLL file from your Java Program? I'm getting Java errors stating it can't find the main class of the file. I'm running Windows 7 32-Bit and Java 6 Standard Edition installed.
Click to expand...
Click to collapse
no it's just fine with me and others :\ , upgrade to higher Jre or redownload
Guys , new update is coming today or tomorrow , will make things much easier :good:
Mohamed Hashem said:
...
Click to expand...
Click to collapse
great job :good::good::good:
long time no see
naheel azawy said:
great job :good::good::good:
long time no see
Click to expand...
Click to collapse
wallahi enta m4 3arf ana far7an 2d eh eny shoftk
NakedFaerie said:
Now that the Gear has moved from Android to Tizen we need a modded version to work with SDB instead of ADB.
Click to expand...
Click to collapse
the problem is that i don't have any Tizen based device , so , even if i made it support SDB i wouldn't be able to test it lol
Very useful thanks bro. And one thing I pressed thanks button on first post just kidding .
Sent from my LG-P500 using XDA Premium 4 mobile app
Good work there @Mohamed Hashem.. surely will help newbies (Y)
Mohamed Hashem said:
sorry didn't understand that .. i mean it had "install apk" option , but what do you mean with batch install apk ?
Click to expand...
Click to collapse
by batch install, he means to select multiple APKs and install them together without having to select one after another and wait for it to install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
How it is a GSI?
First of all, I should mention ubports GSI definition is different from android, but both are generic.
ubports root file system was always generic and works for most cases, but devs were porting halium system image to add device-specific (HALs and configs) support to ubports Android container.
But after project treble which introduced in android 8, all device-specific parts of android system image moved to vendor partition and we can use "Generic system images" over one vendor partition.
In halium version 9, we use this adventure and have a totally generic system image + root file system.
Requirements:
The only Requirement of booting this GSI is having Halium patched kernel.
Keep in mind having android 9 firmware installed on the device as GSI base is mandatory (GSI can be used on android 8.0 and 8.1 vendors but experimental and not supported yet)
How to install?
1. Boot TWRP and FORMAT data
2. Flash vendor image and halium-boot.img (Halium-boot.img confirmed working on DRG and PL2, B2N needs testing)
3. Flash GSI installer zip
4. Reboot
Note: if the device is stuck on the splash screen on boot, simply force reboot using the power/volume button combo meant for your device
Download:
GSI - built by @mrcyjanek (download ONLY target.zip)
Vendor images
Halium-boot
Whats suppose to work?
Bluetooth
Camera
Cellular Radio
Mobile Data
GPS
Graphics
Sensors
Sound
In-call Audio
Touch
Wifi
Vibration
Anbox
Media Playback
Known bugs?
Random (but rare) BSOD + reboots
no way to unlock using Fingerprint
Touching Fingerprint sensor can reduce media volume
oh and of course VoLTE
Camera (on B2N)
Supports:
Halium telegram group
UBports telegram group
UBports Porting telegram group
ErfanGSIs telegram group
Report Bugs:
Explain your bug in proper support telegram groups (from above)
Please don't ask about spoon-feeding or helping on building kernel or device specific builds.
Please don't ask about picking/reverting commits or any basic git commands.
bug reports without logs will be ignored
logs we need are: android logcat, kernel log, syslog
kernel log:
Code:
dmesg
syslog:
Code:
cat /var/log/syslog
logcat:
Code:
sudo -s
LD_LIBRARY_PATH=/system/lib64 lxc-attach -e -n android -- /system/bin/logcat
Taken with all due respect from Erfan's Thread
Appendix:
Anbox installation guide (by SevralTi on Github)
Code:
sudo mount -o rw,remount /
sudo apt update && sudo apt install -y anbox-ubuntu-touch android-tools-adb
mkdir ~/anbox-data
wget http://cdimage.ubports.com/anbox-images/android-armhf-64binder.img -O ~/anbox-data/android.img
touch ~/anbox-data/.enable
sudo chmod -R o+wrx /home/phablet/anbox-data/data
sudo start -q anbox-container
reboot, wait 2 minutes the reboot again
To symlink anbox files to system:
ln -s ~/anbox-data/data/media/0/Documents ~/Documents/android
ln -s ~/anbox-data/data/media/0/Pictures ~/Pictures/android
ln -s ~/anbox-data/data/media/0/Music ~/Music/android
ln -s ~/anbox-data/data/media/0/Movies ~/Videos/android
To make the QS panel occupy the whole screen, install UT Tweak Tool from the Open Store and increase device display scaling
Libertine containers can't be created from the settings app for now. To create a container, pass the command "TMPDIR=/tmp" in the terminal and follow documentation here
IMPORTANT
I take NO credit for the UBPorts community. All that I've simply done is patch our kernel to make it compatible.
Default password is "phablet" (without the quotes)
If you like my work, consider buying me a coffee and join our telegram groups
Cheers,
Sid
I would like to offer a special thanks to a bunch of people who've been with me through this ridiculous journey of mine:
@Sahil_Sonar - for all the help and advice he's given
@krushndayshmookh - for being a generally sweet guy and looking out for me
@CarbonGTR and @Nikhilkumar038 - for being solid friends and motivators throughout my struggle
@Catharsis007 - for being best boi
@ArcherTanu - for being extremely helpful
The UBPorts community
EVERYONE who's worked on the LOS sdm660 Kernel
and a special unnamed best friend who helped me power through the last couple of months.
Cheers,
Sid
Wonderful Work!! GBU!!
Pru
Updated #1 with a new GSI link that doesn't have the reduced storage bug
Awesome work!!! (though I can't try it out--I have a PL2)
Vedanth Padmaraman said:
Awesome work!!! (though I can't try it out--I have a PL2)
Click to expand...
Click to collapse
You can! Our kernel sources are unified and known to work on all 3 devices, DRG, PL2, and B2N
I've listed the bugs specific to DRG only because I own only a DRG, but in theory, you should be able to flash this on PL2 or B2N as well
Ok! Installing it soon
It works on the PL2, encountered nothing broken so far :good:. I received an SMS, downloaded some stuff, etc (but haven't tried calling yet). Once in while it does hang with a black screen while booting, but simply holding Vol. up + Power to force-restart does the trick, like mentioned in the OP. Set up whatsapp successfully on Anbox, but graphics on any anbox app are jerky and laggy at times, in a manner similar to that of the anbox installation on my Linux Mint, so this doesn't seem to be an issue pertaining to this GSI/Halium port. Still, would be nice to have an improvement
Updated kernel to fix media playback. Download from link in OP
Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.
SamandaR1112 said:
Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.
Click to expand...
Click to collapse
It isn't Android, it isn't exactly Ubuntu Desktop either. Canonical was working on Ubuntu Touch/Ubuntu Phone until 2017, and after they dropped the project, the UBports community was born and carried it forward. I'm not sure about HarmonyOS
#1 updated with halium-boot.img (confirmed working on DRG and PL2, B2N needs testing), new flashing method added
Which flashing method is prefered? Anybody who can tell a little on how it is in use? (Does it feel snappy or any lags)
Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...
n00bDroid said:
Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...
Click to expand...
Click to collapse
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.
Vedanth Padmaraman said:
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.
Click to expand...
Click to collapse
Immidiately after my post I made the same realization that vendor.img = vendor partition. So I did that, and it still didn't work.. But then again, I actually flashed B2N-0-354H-00WW-boot.img because I hadn't seen the halium-boot
So I went again. Now according to recipe. Then reboot system..I've been stuck on the "AndroidOne" logo for 15 minutes....after a forced reboot I see the Ubuntu Touch logo!!! thank you!
Camera isn't working. Any tips?
i did not thank you @Sid127 ! That's done !
Sorry for the recent inactivity
n00bDroid said:
Camera isn't working. Any tips?
Click to expand...
Click to collapse
I notice you're on B2N... System logs would be helpful from when you're trying to use the camera. That'd be the dmesg. Without that, I can't be of much help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
This is an unofficial port of Project Sakura for PCs running x86 CPUs by using patches provided by Android-Generic project.
Made with Android-Generic v2.0 - Android for PCs & GSI devices
More detail : https://android-generic.github.io/
Code:
* Your warranty is now..... I don't know this is PCs ¯\_(ツ)_/¯
* It's very important to read the instructions and understand what you are doing. So please, READ !
* I am not responsible if you accidentally wiped your data on your hard drives or making your main OS like Windows unable to boot.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration."
Currently the best method I recommend to use is to dual-boot with a Linux distro, using its Grub2 bootloader to load the OS.You can check out BlissOS wiki or SupremeGamers wiki for the instruction.
Manual Install on Linux - Documentation
docs.blissos.org
Linux
Android-x86 is just a highly modified Linux. As a result, it has lot of similarities with Linux.
wiki.supreme-gamers.com
Alternatively, If you want to install using Windows
Advanced Android-x86 Installer - Knowledgebase
knowledgebase.blissos.org
Windows
Due to how Android-x86 is structured, it can be installed in any system.
wiki.supreme-gamers.com
For .rpm
Howto install Android X86 RPM images
I DON'T RECOMMEND TO FLASH ISO ON USB BECAUSE THE BOOTABLE INSTALLER IS HAVING PROBLEM.
Click Here
-Android-x86 Project
-BlissLabs (with works like BlissOS and Android-Generic)
-Lineage OS
-AOSP
-Superior OS
-AOSiP
-DerpFest
-Pixel Experience
-Extended UI
-Havoc OS
-CrDroid ROM
Project Sakura Source
The kernel source which I use for the build : https://github.com/hmtheboy154/Darkmatter-kernel
ProjectSakura-x86 Source which include all the changes for x86 will be available soon
ProjectSakura-x86 source : https://github.com/supremegamers/android/tree/sakura/11-x86/
Project Sakura's Telegram Group (if you want to feedback about the ROM)
BlissOS/ AG (x86/ x86_64) Telegram Group (if you need help installing or feedback about the PC builds)
This is a x86_64 build so please make sure your CPU support 64bit and SSE4.2
About bugs : Unlike Custom ROMs on phones where people can just put "You tell me", PC builds do have problem..... a lot.
- Not all the hardware will work perfectly or even supported (*cough Nvidia GPUs ).
- Screen Recording is not working yet (gbm_gralloc limitation)
- FaceUnlock is not working (and don't even hope it work)
- Bluetooth might not working yet.
- SwiftShader is broken so you can't boot with Software Rendering.
- For user using AMD GPUs (or APUs), there's graphic bugs when you have to choose default apps like for default launcher or default browser. Here's an explanation by Mauro Rossi - one of the member of Android-x86 Project :
A long standing issue is "the tiling artifacts" happening with gbm_gralloc at ResoverActivity window when SW write buffer used, one example is the launcher selector at first boot and another is visible with Chicken Invaders advertisements windows on SW write buffer
Intel i915 and i965 were not affected, while r300, r600, radeonsi and nouveau are all affected,
iris and crocus expected to not be affected, but I need to check.
Click to expand...
Click to collapse
So if you are seeing this (or worse) then it's the one I'm talking about.
(Iris and crocus actually not affected btw)
Update : Iris got reported to be affected, and there are some cases of crocus too. So I will mark this as a bug for both AMDGPUs and Intel iGPUs in general. If you want to read more about the bug, you can read this post by Mauro for more info
Project Sakura-x86 for PCs
Maintainer: HMTheBoy154
Build Type: Unofficial
ROM OS Version: 11.0 r40
ROM Kernel: Linux 5.10.61
ROM Firmware Required: Included in the build
Based On: LineageOS 18.1
Version Information
Status: Alpha
Current Stable Version: 5.R
SELinux Status : Permissive
Release Date: 2021-09-06
This is the first initial build which include FOSS pack from BlissOS. FOSS pack provide some FOSS application and also microG as the GMS replacement. Also here's what I put into the build :
- Mesa 21.2.1, libdrm 2.4.107 and LLVM12.0.1
- alsa-utils and alsa-lib are on version 1.2.5.1 with alsamixer tool
- My customized Kernel 5.10.61 which include patches from GoogleLTS (kernel/common android13-5.10 branch), xanmod and Android-x86 (More detail)
- AOSP SystemWebView got replaced with Bromite SystemWebView (big thanks to them for providing x86_64 builds)
- Using FakeStore 0.1.0 instead of 0.0.2 provided by FOSS package.
- Adding Open Camera since the stock Camera app is broken.
Here are some screenshot :
where is the famous xda bugs description " bugs ? You tell me "
Ni8 said:
where is the famous xda bugs description " bugs ? You tell me "
Click to expand...
Click to collapse
Pro :3
For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'
I installed it in my realme c2 and its working very fine.
New builds have been uploaded, here are the new changes :
- Upstream to September Security patch
- Update Mesa to 21.2.2
- Fixed broken Bluetooth (require restarting bluetooth app)
- Adding thermal-daemon from Project Celadon
- Adding Thermal HAL from Project Celadon
- Pull houdini and Widevine from ChromeOS 92 recovery file for hatch
- Now comes with both GMS and FOSS build
For bluetooth, just restart `com.android.bluetooth` by using `pm disable` then `pm enable` and then it will work if your card already recognized by Android-x86 before. I tested with a fake CSR card and it's running as expected.
By the way, I applied for ProjectSakura maintainer, both for PCs and Oneplus Nord So expect a new OFFICIAL build soon.
cjeu100 said:
For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'
Click to expand...
Click to collapse
NOPE! even with root is a read only filesys.
And the SED command returns formatting error as well.
Pleas share proper in depth steps if you might. thanks
joshyakadamien said:
NOPE! even with root is a read only filesys.
Click to expand...
Click to collapse
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?
joshyakadamien said:
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?
Click to expand...
Click to collapse
Only in Android 11, you need to mount as r/w again, ro by default unlike previous versions of Android x86.
Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Veselchak787 said:
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Click to expand...
Click to collapse
Hello my Russian friend from 4pda.
We are also waiting for the update
One more question: how I can download files using build in this rom internet browser?
Veselchak787 said:
Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I just tested from the latest beta build I have here (haven't release it yet) and I do have the same problem, still don't know why, maybe I will take a look at it soon
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.
kamazok said:
Hello my Russian friend from 4pda.
We are also waiting for the update
Click to expand...
Click to collapse
I'm still planning for the new update tho, aiming for BoringDroid in the next version so we might have 4 Desktop Mode to choose. So I am waiting for utzcoz to fix it on newer security patch.
by the way, this thing is on 4PDA ???
We
HMTheBoy154 said:
this thing is on 4PDA ???
Click to expand...
Click to collapse
We are disсuss differen variants of Android x86.
Android OS на x86 - 4PDA
Android OS на x86, [androidPC]
4pda.to
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I'm rocking this on a HP Elitepad 1000 G2 with nice batt times
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.
Click to expand...
Click to collapse
Brave is stable for. ex.
cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, did the trick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS-19.1 microG For Moto Z (griffin)
With the rise of Big Tech and the encroachment of government into our lives , I felt more of a desire to move away from Google and the like.
Moto Z (griffin) was built with microG and LineageOS source and is fully functional.
What it is. It's LineageOS with all of Google's closed-source binaries removed and replaced with microG. I.e. no Play services or GAPPS. UnifiedNLP is used as the networking location provider instead of Google's NLP. Aurora Store and F-Droid is installed by default and provides an alternative app store. However, with the Aurora Store, you cannot install all Google Play Store apps such as buy apps.
Other information
Google Play Store Alternative If you want to have full access to normal Android Play Store apps, After opening Aurora Store, select the appropriate option. usually option number 1 is the most commonly used with this ROM, unless changed by the user. After setup, you will have access to all apps as usual. Some apps require Play Services and cannot be used.
After installation - Open the microG app --> self-check sections should be successful. Location Services - By default, LocalGsmNlpBackend, which uses the NominatimGeocoderBackend, and NominatimNlpBackend, which uses Mapquest's Noninatim service, are disabled. Open the microG app --> location modules and enable the modules you want. Then restart the device.
It is strongly recommended not to install NikGapps as this ROM contains a replacement for NikGapps these are microG
What's working:
Boot
RIL
Camera
Fingerprint Sensor
WiFi
Bluetooth
Audio
Video Playback
NFC
Sensors
Touch
Flash
Moto gestures
Network monitor
Secure boot
What's not working:
Encryption
SELinux
You tell me.
Installation instructions
Upgrade to Stock Oreo Firmware if not done already!
- Download the ROM from the website. (see download link below)
- Install a compatible Recovery
- Perform a backup of your current ROM (Optional)
- Wipe data & cache partitions and FORMAT DATA from TWRP of your device (required when coming from stock!).
- Flash ROM.
- Flash magisk (if needed)
- Reboot
instructions (if coming from another ROM or Android version )
Secure your data (recommended)
Removes custom encryption pins/passwords (recommended)
CLEAN FLASH
- Download the ROM from the website. (see download link below)
- Reboot to TWRP
- Create backup (optional)
- Wipe system, data, cache
- Flash the ROM
- Flash magisk (if needed)
- Reboot
DIRTYFLASH
1) via OTA
2) Manual method
- Download the ROM from the website.
- Reboot to TWRP
- Flash the ROM
- Flash magisk (if needed)
- Reboot
Official update
monthly
except for important bug fixes from Device maintainer .
Changelog
Spoiler: Klick
Date -25/06/2023
=================
Changelog 25.06.2023
- Synced with LineageOS sources
- June 2023 Merged Security Update
Changelog microG
- Update FakeStore 0.2.0
Date -15/05/2023
=================
Changelog 15.05.2023
- Synced with LineageOS sources
- Merged May 2023 Security update
Changelog microG
-----
Date -26/04/2023
=================
Changelog 26.04.2023
- Synced with LineageOS sources
- Merged April 2023 Security update
Changelog microG
- Update AuroraStore 4.2.1
- Update FDroid to 1.16.3
Date -24/03/2023
=================
- Synced with LineageOS sources
- Merged March 2023 Security update
Date -09/03/2023
=================
- Initial release
- with February 2023 Security update
Download Rom
Moto Z (griffin)
https://los-legacy.de/19.1/griffin
Source code Kernel
android_kernel_motorola_msm8996
Source code partner_gms / microG
android_vendor_partner_gms
Source code Rom construction :
docker-lineage-cicd
Source code system
https://github.com/LineageOS
for german support
LineageOS 19.1 (A12) [microG][OTA] für Moto Z (griffin) - Los-Legacy
LineageOS 19.1 (A12) microG für Moto Z (griffin) Mit dem Aufstieg von Big Tech und das Eindringen der Regierung in unser Leben, fühlte ich mehr von einem Wunsch, weg von Google und dergleichen zu bewegen. Motorola Z (griffin) wurde mit microG und…
forum.los-legacy.de
ROM Manufacturer:
Exodusnick
Device Maintainer:
SirRGB
thank you for testing the rom
SirRGB
Other information
All my roms are created with a signed private key.
If you want to use the Lineageos recovery,
However, I don't know how the Lineageos recovery works as I have never used it on my other devices as I only use twrp.
Everyone is responsible for their own actions. Neither Team Xda, nor I, the creator of the theme, will take responsibility for any damage to your device caused by any Flash attempts.
This Rom consists purely of MicroG and has no Gapps or nikgapps.
I have here a few screenshots original from Moto Z (griffin).
@Exodusnick Does VOLTE work in this ROM ?
Edit: I mean I can't make calls with either of these following ROMs if I set Preferred network type = LTE
Odd Solutions Downloads
updater.oddsolutions.us
[ROM][12.1] LineageOS 19.1 for griffin [UNOFFICIAL][18 Feb]
* Your warranty is now void. * /* * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
When I set the Preferred network type = LTE/WCDMA calls start working.
You can test it to see if Volte is working
Go to dialer and enter this code
*#*#4636#*#*
Go to phone information
Default is set to
GSM/WCDMA/LTE/(PRL)
top right on ...
Ims service jams
@Exodusnick If I set the preferred network type to GSM/WCDMA/LTE (PRL), the phone call is done in WCDMA/H+ mode.
Data over LTE is working fine on the Moto Z. I found some information about enabling VoLTE on Android:
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
[Guide] Easy method to Enable Volte (with root) on Tmobile and maybe other networks on Android 11 and maybe 10
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around. Then once you do that, follow these directions, What I did was manually entered all of these setprop commands below, on the...
forum.xda-developers.com
> setprop persist.vendor.dbg.ims_volte_enable 1
> setprop persist.vendor.dbg.volte_avail_ovr 1
> setprop persist.vendor.dbg.vt_avail_ovr 1
> setprop persist.vendor.dbg.wfc_avail_ovr 1
The Moto Z has these following properties, but is missing the persist.vendor.dbg.ims_volte_enable one:
> $ getprop | grep -i -e volte -e _avail
> [persist.dbg.volte_avail_ovr]: [1]
> [persist.dbg.vt_avail_ovr]: [1]
> [persist.dbg.wfc_avail_ovr]: [1]
> [sys.user.0.ce_available]: [true]
Could that be the problem that persist.vendor.dbg.ims_volte_enable is not shown in getprop? I haven't rooted the phone.
Best regards,
Aki
ok is not shown ?!
android_device_motorola_griffin/properties.mk at lineage-19.1 · griffin-experimental/android_device_motorola_griffin
Device trees for Moto Z to build misc roms. Contribute to griffin-experimental/android_device_motorola_griffin development by creating an account on GitHub.
github.com
will be added in the next update
persist.vendor.dbg.ims_volte_enable 1
Thank you for this built Exodusnick! I haven't installed it yet as my main use for this beloved Moto Z is with the Moto Mods. Can you please confirm if it has been tested and is working with the camera mod and the beamer mod?
Thanks
Vuche said:
Can you please confirm if it has been tested and is working with the camera mod and the beamer mod?
Thanks
Click to expand...
Click to collapse
I can not confirm if moto mods work,
Test my rom and let me know if it works or not . You can also ask @SirRGB he is Device Maintainer
and he has tested the rom.
I dont have any moto mods, but I expect the battery pack and only that to work.
Ok, thank you Guys!
I'll will try later this month and will let you know.
..
@Exodusnick I just tested this ROM on my Moto Z and unfortunately it looks like VoLTE is still not working. The phone ends the call immediately when I press the green call button.
Thanks for the info
I will undo it and delete this current build.
I have no idea how to get Volte to work.
@akikoo you can go back to the first build without problems
possible that it is wrong and that it must be so
persist.dbg.ims_volte_enable=1 \
and not persist.vendor.dbg.ims_volte_enable=1 \
persist.dbg.volte_avail_ovr=1 \
persist.dbg.vt_avail_ovr=1 \
persist.dbg.wfc_avail_ovr=1 \
plus this
persist.radio.calls.on.ims=1
@akikoo I will create a test build
Exodusnick said:
possible that it is wrong and that it must be so
persist.dbg.ims_volte_enable=1 \
and not persist.vendor.dbg.ims_volte_enable=1 \
persist.dbg.volte_avail_ovr=1 \
persist.dbg.vt_avail_ovr=1 \
persist.dbg.wfc_avail_ovr=1 \
plus this
persist.radio.calls.on.ims=1
@akikoo I will create a test build
Click to expand...
Click to collapse
And under the thread concerning VoLTE for the LG Velvet (that I use as my main phone at the moment), you have to create a directory in the phone in order to have it working. And even so I discovered that it doesn't work with my "old" sim card, although it does work with another more recent sim on the same network.
I don't think it works, because under LineageOS 18.1 officially you can't find the entry
persist.vendor.dbg.ims_volte_enable=1 \ or persist.dbg.ims_volte_enable=1 \
android_device_motorola_griffin/properties.mk at lineage-18.1 · LineageOS/android_device_motorola_griffin
Contribute to LineageOS/android_device_motorola_griffin development by creating an account on GitHub.
github.com
it is simply not supported by lineageos.
@Exodusnick I was hopeful VoLTE would work with your ROM as *#*#4636#*#* / Phone information showed these settings:
voice service = in service
voice network type = LTE
volte provisioned switch was in enabled position
Best regards,
Aki
Yes, but your call would be interrupted
So something is missing maybe this
persist.radio.calls.on.ims=1
@akikoo I will create a test build
is your sim card activated for volte?