Database Develop

[PLEASE HELP] Lenovo K3 Note (K50-T5)

Hello to all guys , I just got this fantastic Lenovo phablet , but I do not like the translation and Vibe UI , I want to find a pure Android rom . I know that almost certainly there are devices that have the Lenovo compatible roms . Can anyone help me out ? :crying::crying::crying:

I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!

I'm pretty sure as this phone is, new rooting and roms are still being developed. Be patience.. or learn to make one yourself
To those who find this thread do be careful! I've already seen posts about people who have bricked this phone trying to root it.

Got the same phone. Liking the layout etc. Not the official VIBE UI rom.
It's set to English, but still finding Chinese icons/text everywhere.
Since I don't speak/read Chinese; issue...
Also sometimes laggy, due to lots of processes/apps running in the background, which can not be deleted or stopped.
Looking forward to when the community embraces this phone, and stock Android ROMS will be available on short term.
It's a (edit: potential!) flag-ship killer, in my eyes...

Hi,
I am trying to port cm12 to this device. It is the first time I am doing although I have previously created custom ROMs by editing system.img, so I am a noob.
I managed to get a stock rom: K50-T5_USR_ST1516_5.654.1_1504152228_MP6V3_CN.rar.
I have slightly modified build/tools/device/mkvendor.sh to be able to work with mediatek files which have a 512 bytes extra header.
I've triedt to create a recovery but I am not sure if it will work as I have some errors in the output
./build/tools/device/mkrecoveryzip.sh /home/vagrant/android/system/out/target/product/aio_otfp /home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/etc’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/sbin’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/recovery/root/res’: No such file or directory
cp: cannot stat ‘/home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/system/bin/updater’: No such file or directory
zip -ry /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/unsigned.zip . -x *\[* *\[\[*
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/updater-script (deflated 51%)
Error: Unable to access jarfile /home/vagrant/android/system//home/vagrant/android/system/out/host/linux-x86/framework/signapk.jar
Recovery FakeFlash is now available at /home/vagrant/android/system//home/vagrant/android/system/out/target/product/aio_otfp/utilities/update.zip
Click to expand...
Click to collapse
Should I copy anything from boot or recovery's ramdisk?
You can find attached the information I've been able to collect (info.txt and build.prop.txt) and build.log which was in a folder in the stock ROM.
Thanks

One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app

got it in cheinese
can you send a link to an english site?

AOSP
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully

LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
-yes
-yes
-only play store but that what important
-maybe later
This ROM is pretty laggy and the ram is mostly full, and the worse part is that it can't play any video or jifs. For now I will recomand not to install this ROM until it will be modify correctly. Link from megahttps://mega.co.nz/#!3UcAkaaK!uEtthUPkeD1q7T4Nyn0MFtpLe9AtwQf-lOwqtz5RU-I

Lenovo K3 Note T50-T5 multilang firmware
This is Lenovo K3 Note T50-T5 multilang firmware: kimmobile "dot" com/tin-tuc/rom-tieng-viet-lenovo-k3-note-k50-t5-lenovo-k3-note-k50-t5-multilang-firmware-id2674

System Update Problem
Hello,
When I go to the the About Phone settings I do not have the option to check for updates on my phone.
Please can you help?
Thank you,
Awais

AOSP based 5.0 build for the K3 Note
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.

headuck said:
Nanj at a Chinese forum had released an AOSP based 5.0 build for the K3 Note
http://bbs.ydss.cn/thread-551335-1-1.html (in Chinese but with captures)
The download link:
http://pan.baidu.com/s/1hqAdrrY
No gapps are included. The build functions ok. Camera, phone / data, and wifi seem to work. However please note that there is an undesirable apk, posed as a system component, at /system/app/SystemServer/SystemServer.apk. It sends frequent packets back to 622b6.romdu.com in China, similar to the issue in another post for a different rom -
http://forum.xda-developers.com/showpost.php?p=55315205&postcount=54
The ROM also comes with a Chinese version of the Opera browser, Oupeng, which also sends analytics packets in the background.
With the two programs removed suspicious packets are no longer obvious from logcat.
Click to expand...
Click to collapse
Does notification led work?

LeetjeDanhoff said:
I got some questions
-is it multilanguage
-is it Android 5.0
-gapps included?
-can someone post some screens
Yours faithfully
Click to expand...
Click to collapse
https://youtu.be/Wf4kkRq0ork review video on the K3 Note

cccho said:
One Chinese port AOSP to K3-Note.
Its can be daily use and without any bug now. If somebody need it. Just try it.
http://pan.baidu.com/share/link?shareid=2842642895&uk=2251472345
Sent from my Lenovo K50-t5 using XDA Free mobile app
Click to expand...
Click to collapse
does it come with gapps?

narithlot said:
does it come with gapps?
Click to expand...
Click to collapse
Sadly, no... But you can flash it with CWM

revert to stock ROM
Lataman said:
I have the same problem, I just changed to new version of VibeUI and had some problems with google apps HELP!
Click to expand...
Click to collapse
you can revert to stock ROM
if you have stock Recovery(Not CWM)
then flash this whith stock recovery
this is official stock chinese/english ROM
https://mega.co.nz/#!MwAxGACR!CNyHABuPxbMpHTHRAhbYJWl_IO4z7jAz8szgIMGt_jQ
instuctions:
make sure you have stock recoveyr
then put this ROM on external memory card
rename the zip file to update.zip
then go to stock recovery select update

New VIBE UI
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.

What is the significance of this ROM string? I see that "ST" prob means (stable).
Know what "CC", "WCA2" and "WCA8" means in these I found below?
Do you know where is the (official) location to find the latest English language ROM?
My proximity sensor is not working and I'm wondering if moving to a diff ROM will fix that.
VIBEUI_V2.5_1520_7.128.1_CC_K50-T5_WCA2.zip (Android 5.0)
VIBEUI_V2.5_11520_5.827.1_ST_K50_T5 (Android 5.0) <------ the one my phone came with; multi-language
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5_WCA8.zip (???)
VIBEUI_V2.8_1526_7.80.1_CC_K50-T5.zip (VIBE 2.8, Android 5.1)
BurntCircuitz said:
There has been a new update released by Lenovo.
VIBEUI_V2.5_1524_5.955.1_ST_K50-T5
I have not updated as of yet, for the reason being I am very dissatisfied with the VIBEUI. I currently run 1522, despite the obvious and numerous complications of using the Asian based firmware. I have had to replace the dialer and sms, mms apps as well as install a font manager, even so I am still unable to get 4G working. I would much prefer a pure Android rom and for the past month have been considering beginning a project to build a new Lollipop rom supporting the 67xx MTK chipsets. It would be my first attempt at doing so since all my previous phones have been LG, HTC and NEXUS devices which have always proved easy enough to manipulate and customize.
If anyone out there has experience in building custom roms, especially for devices using the newer 64bit Mediatek chipset, please feel free to contact me. I would appreciate any help offered in this endeavor and I know there are many other MTK device owners out there that are just waiting for someone, or a group of someones', to pioneer a solution for those of us in the western hemisphere using these MTK devices. I am constantly on the look out for new information and projects pertaining to this, additionally I have a dedicated computer with all the SDKs needed to begin the project.
PM me if you are interested in helping kick start this project. Thanks.
Click to expand...
Click to collapse

Here where you can find the Rooting and Custom ROMs
https://www.reddit.com/r/lenovok3note/wiki/index
https://www.youtube.com/watch?v=g4PQqRXSUa4
https://www.youtube.com/watch?v=wCwMQkX-1sw

ZTE Nubia Z9 Mini (NX511j) - Cam driver for international Version

Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so​
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml​
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.

Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app

Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-

Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.

Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.

kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.

falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.

kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:

Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.

[XZ][F8331/2] AOSP Pie builds [Stable] [Updates]

New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17

Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!​
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!

---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread​
---

In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.

Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.

An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.

Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.

viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.​
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332​

The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned

General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.

Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.

local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers

Finally a new build is out!

I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.

V 12.15
Charging working fine. But i have problem with camera, photos are very dark.

Sometimes touch screen not working and i need to switch the screen and on again.

ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w

oem v4 is out

DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/

ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick

information please

This is not so much a note 9 question but i am in the note 9 port of the forum and it deals with the android system.
I am trying to learn a few things about android OS. I would like to make a rom and know there are some good tuts on xda.
I happen to be a hands on learner. By that i mean i like to learn by doing so tuts are good but dont pinpoint my want.
I have a android streaming box. It is from what i have read a china clone with a rockchip 3328 chipset and a 8723 wifi chip. It seems the company i bought it from put out their firmware but its very buggy and there is no twrp for it but it dose have root. But not supersu. If i install supersu the binaries are out dated and if you update them it will bot boot.
Ok anyways my question is can i open the system img and change the launcher because no launcher seems to work just by downloading from the store. and edit the systemui and framework-res because it seems somewhere the notification bar and the nav bar are gone on the ui. I then would pack it up again and install like normal firmware.
What pratfalls will i encounter and if there is any write ups on something like this please let me know.
Lastly and it may be way beyond the scope of this post. What is the process of mak8ng or rebuilding twrp to work with my device i would really like to give that a go too.
Thanks for any input.

[SM-T700] [KLIMTWIFI] All-in-one mirror of files for the Galaxy Tab S 8.4 Wi-Fi

Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.

CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...

prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror

CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.

prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.

CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?

prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews

CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..

prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!

CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...

prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.

Thank you kindly!

lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!

CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!

Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.

CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!

These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna

I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks