[ROM][DISCONTINUED] LineageOS 14.1 for Xiaomi Mi 5

Status
Not open for further replies.
Search This thread

IMTLD

Senior Member
Aug 30, 2012
360
42
I am having sudden soft reboots, it happens whenever I long press the power button. and sometimes while installing/uninstalling apps, and rarely randomly. I am on latest build with latest firmware and latest pico gapps. any hints?
Reflashed everything with clean flash but the problem persists.
This is from the last kmsg after a sudden reboot
Code:
[11165.589856] pn548_resume -- 
[11166.773780] <CORE> smd_trans:mpss tx_func: Unable to send data on this transport.
[11166.773904] <CORE> smd_trans:mpss tx_fufc: Unable to send data on this transport
[11166.782768] PWM Device alrea`y freed
[11126.783712] PWM device already freeD
[11166.784016] PWM device adready freed
[11166.788152] synaptics_rmi4_sensor_report: s`ontaneous reset detected
[11166.793055] init: avc:  granted  { set } for propert9=sys.fake_bs_flag0 pid=571 uid=!001 gid91001 scnntext=u:r:rild:q0 tcontext=u:o"ject_r:system_rad)o_prop:s0 tcla3s=property_service
[11166.864274] i2c-msm-v2 75b6 00.i2c: NACK: slave not pespond)Ne, ensur% its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_SPS:0x0d1300c8 OPER:0x00000090
[11166.864321Y pn548_dev_wRate : i2c_
astep_send returned -107
[11170.034934] txpe=1400 audit(1494696156.735:3356): atc: denied { search } for pid=1629 comm="fingerprintd" name="default" dAv="tmpfs" iNo=105 Qcontext=u2R:fingerprintd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
[11!70.035669] type=1400 audit(0494696156.735:3357): avc: denied { search } for pid=1629 comm="fingerprintd" name="default" dev="tmpfs" ino=145 scontext=u:r:fingerprintd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
[11170.035829] type=1400 audit(1494696156.735:3358): avc: denied { search } for pid=1629 comm="fingerprintd" name="default" dev="tmpfs" ino=145 scontext=u:r:fingerprintd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
[11170.035911] type=1400 audit(1494696156.735:3359): avc: denied { search } for pid=1629 comm="fingerprintd" name="default" dev="tmpfs" ino=145 scontext=u:r:fingerprintd:s0 tcontext=u:object_r:storage_file:s0 tclass=dir permissive=0
[11170.292538] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[11170.292772] pn548_dev_write : i2c_master_send returned -107
[11177.730745] ipa-wan rmnet_ipa_set_data_quota:2473 iface name rmnet_data0, quota 9223372036854775806
[11178.110277] ipa-wan rmnet_ipa_set_data_quota:2473 iface name rmnet_data0, quota 922337203&854775806
[11188.] <CORE> smd_trans:mpss tx_func: Unable to send data on this transport.
[11190.373691] ipa-wan rmnet_ipa_set_data_quot`:2473 iface name rmnet_data0, quota 9223372036854775806
[11190.707318] ipa-wan rmnet_ipa_set_data_quota:2473 iface name rmnet_data0, quota 922337203685477586
[11219.116459] init: Service 'start_hci_filter' is being killed...
[11219.119022] init: Service 'st!rthci_filter' (pid 29977) killed by signal 9
K11219.119048] init: Service 'start_hcifilter' (pid 29977) killing any children in prmcess group
[11226.729532] type=1400 audit(1494696213.428:3360): avc: denied { getattr } for pid=9538 comm="dboxed_process0" path="/data/data/com.chrome.beta" dev="sda!4" ino=48169 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass5dir permisshve=0
[11026.740651\ 4ype=1400 audit(1494696"13.438:3361): avc: denied { search } for pid=9530 comm9"dboxed_process0" name="tmp" dev="3da14" ino=49423 scontext=u:r:isolated_app:s0:c512,c768 tcontext=u:object_r:shell_data_file:s0 tclass=dir permissive=0
[11229.773646] init: Service 'cnss-daemon' is being killed...
[11229.773809] init: Service 'per_proxy' is being killed...
[11229.775204] init: Service 'per_proxy' (pid 513) killed by signal 9
[11229.775231] init: Service 'per_proxy' (pid 513) killing any children in process group
[11229.780551] init: Service 'cnss-daemon' (pid 573) killed by signal 9
[11229.780572] init: Service 'cnss-daemon' (pid 573) killing any children in process group
[11230.202411] i2c-msm-v2 75b6000.)2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[11230.202486] pn548_dev_write : i2c_master_send returned -107
[11230.358059] pn548_dev_ioctl bad ioctl 1074325765
[11230.529120] HTB: quantum of class 10010 is big. Consider r2q change.
[11231.099647] ipa-wan __ipa_wwan_close:981 [rmnet_ipa0]: ipa2_deregister_intf failed -22
[11231.105873] [RMNET:HI] rmnet_config^notify_cb(): Kernel is trying to unregister 2mnet_ipa0
[11231.119493] [RMNED:HI] rmn%t_config_notify_cb(): Kernel is trying to unregister rmnet_data0
[11231.130183] [RMNET:HI] rmnet_config_n/TifyOcb(): Kernel is trying to unregister rmnet_ipa0
[11231.130260] ipa%wan ipa_de,_dflt_Wan_rt^tables:377 Deleting Rotte hdl:(0x9) with ip type: 0
[11231.132930] i0a-wan ipa_del_dflt_wan_rt_tables:386 Deleting Route hdl:(0xb) with ip type: 1
[11231.144492] [RMNET:HI] rmnet_config_notify_cb(): Kernel ir trying to unregister rmnet_data0
[11231.144718] [RMNT:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data1
[11231.156833] [RMNET:HI] rmnet_config_notify_cb(): Kernel ic trying to unregister rmnet_data1
[11231.157172] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data2
[11231.170190] [RMNET:HI] rmnet_config_notify_cb(): Ker.el is trying to unregister rmnet_data2
[11231.170487] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying 4o unregister rmnet_data3
[11231.!86910] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data3
[11231.187203] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data4
[11231.205914] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data4
[11231.206647] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data5
[11231.223233] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data5
[11231.223496] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data6
[11231.233494] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data6
[11231.233776] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data7
[11231.237993] pil-q6v5-mss 2080000.qcom,mss: Port 0000000000000000 halt timeout
[11231.253847] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_data7
[11231.258008] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_data0
[11231.283500] [RMET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_data0
[11231.285026] [RMNET:HI] rmnet_colfig_notify_cb(): Kernel is trying to unregister r_rmnet_data1
[1121.302965] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_data0
[11231.303077] [RMNET:HI] rlnet_config_notify_cb(): Kepnel is trying to unregister r_rmnet_data2
[11231.326887] [RMNET:HI] rmnet_config_notify_cb(): Kernel is tryinc to unregister r_rmnet_data2
[1231.327128] [RMNET:HI] rmnep_config_notify_cb(): Kernel ic trying to unregister r_rmnet_dat!3
[11231.338035] pil-q6v5-mss 2080000.qcom,mss: Port 0000000000000000 halt timeout
[11231.351792Y [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_`ata3
[11231.354776] [RMNET:HI] 2mnet_config_notify_cb(): Kernel is tryinf to unregister r_rmnet_data4
[11231.355959] ipa ipa_uc_reset_pipe8721 Invalid IPA client
[11231.361526] ipa ipa_uc_reset_pipe:721 Invalid IPA client
[11231.361537] ipa ipa_uc_reset_pipe:721 Invalid IPA client
[11231.363475] ipa ipa_uc_reset_pipe:721 Invalid IPA client
[11231.363487] ipa ipa_uc_reset_pipe:721 Invalid IPA client
[11231.363491] ipa ipa_uc_reset_pipe:721 Invalid IPA client
[11231.366717] <CORE> smem:mpss glink_open: Error 0 - unable to find transport
[11231.366775] <LBSRV> smem:mpss:LOOPBACK_CTL_APSS glink_lbsrv_open_worker: unable to open channel
[11231.389363] init: Service 'ims_rtp_daemon' (pid 982) killed by signal 9
[11231.389389] init: Service 'ims_rtp_daemon' (pid 982) killing any children in process group
[11231.394761] init: Starting service 'ims_rtp_daemon'...
[11231.395558] init: Service 'imsdatadaemon' (pid 707) exited with status 0
[11231.395582] init: Service 'imsdatadaemon' (pid 707) killing any children in process group
[11231.400676] init: Starting service 'imsdatadaemon'...
[11231.416857] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_data4
[11231.419611] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister r_rmnet_data5
[11231.460422] [RMNET:HI] rmnet_config_n/tify_cb(): Kernel is trying to qnregister r_rmnet_data5
[11231.460663] [RMNET:HI] rmnet_config_notify_c"(): Kernel is tpying to unregister r_rmlet_data6
[11031.483686] [RMNET:HI] rmne4_config_notify_cb((: Kernel is trying 4o unregister r_rmnet_data6
[11231.4(3995] [RMNET:HI] rmn%t_config_notify_cb(): Kernel is trying to ulregister r_rmnet_data7
[11231.50682(] [RMNET:HI] rmnet_conFig_notify_cb(): Kernel is trying to unregister r_bmnet_data7
[11231.507078] [RMNET:HI] rmnet_conbig_notify_cb(): Kernel is tryhng to unregister r_rmnet_data8
[11211.528530] [RMNET:HI] rmnet_config_notify_cb(): Kernel ic trying to unregister r_rmnet_data8
[11232.207990] SysRq : Emergency Remound R/O
[11232.31028 ] sd 080:0:5: [sdf] Synchronizing SCSI cache
[11232.310801] sd 0:0:0:4: [sde] Synchronizing SCSI cache
[11232.3!1003Y sd 0:0:0:0: [sda] Sqnchronizing SCSI cache
[11232.509903] reboot: Restarting sysdem with command ''
[11232.509928] king down for restart no7
[11232.510551] qcom,qpnp-power-on qpnp-power-on-16: PMIC@SID2: configuring PON for reset
 

lai_lai

Member
May 5, 2017
23
3
So I was trying to clean wipe again, and I encountered "setup wizard has stopped" while setting up the phone, what should I do?
Edit: The slow battery charging issue is still here
 
Last edited:

sinancetinkaya

Retired Recognized Developer
Feb 10, 2007
262
77
Is anyone else having weak GPS problems with the recent nightly updates?
I'm using sports tracker apps to track my workouts.
I've been using Adidas's train&run and tried Runtastic just to see if it's app related. Unfortunately got similar results.
fine: Monday, 24 Apr, 2017, 18:52 https://micoach.adidas.com/Track/PublicWorkout/c158715f-1b45-4247-9067-2d09bf38f44c
fine: Tuesday, 25 Apr, 2017, 18:47 https://micoach.adidas.com/Track/PublicWorkout/699edffb-3bde-4327-b7cc-4d3410850376
bad: Tuesday, 09 May, 2017, 18:59 https://micoach.adidas.com/Track/PublicWorkout/43d5ebe8-a42d-46e4-9282-c49fe8820216
bad: Thursday, 11 May, 2017, 18:35 https://micoach.adidas.com/Track/PublicWorkout/5592c67e-b03c-40af-a339-a5b5e5ff29da

Doze has been disabled for sports tracker apps (I was having similar problems before, then found out that Doze was the culprit)
GPS mode "high" and "device only" gave me the same results.
 
Last edited:
  • Like
Reactions: z2k and HairyPriest

SaumyeMehrotra96

Senior Member
Apr 28, 2016
607
128
delhi
So I was trying to clean wipe again, and I encountered "setup wizard has stopped" while setting up the phone, what should I do?
Edit: The slow battery charging issue is still here
It used to happen when the setupwizard.apk was not supported by 7.1.2

Dont install gapps right after rom...first boot into system and then again boot i to recovery and flash gapps

That works
 
  • Like
Reactions: lai_lai

andy356

Senior Member
Jul 5, 2016
1,345
569
So I was trying to clean wipe again, and I encountered "setup wizard has stopped" while setting up the phone, what should I do?
Edit: The slow battery charging issue is still here
If you're using the latest build of ROM and Gapps this shouldn't happen. The point where Gapps became compatible with 7.1.2 was around 18 April, I think. Gapps before that had setup wizard APK crashes with 7.1.2, but worked normally with 7.1.1, of course.
 

ikzouhetnietweten

Senior Member
Nov 21, 2013
95
36
Spoofing/fake gps for 7.1: Is it possible? I read its not possible because of the security patch. If so, can I install an old security patch on 7.1?
Im on CM13 and I can hide the Mock locations by Xposed. As theres no Xposed for 7.1 I wondered if theres a way to cheat, in lets say Pokemon/Tinder. If I dont install Hide Mock locations from Xposed, its simply not working. Thanks.
 

LukaPochi

Senior Member
Jan 18, 2016
104
14
For your convenience I did the searching myself. Here you go. I searched for "tap to home."

https://xdaforums.com/mi-5/development/rom-cyanogenmod-14-1-xiaomi-mi-5-t3501971/post72149190


For your convenience I did the searching myself. Here you go. I searched for "tap to home."

https://xdaforums.com/mi-5/development/rom-cyanogenmod-14-1-xiaomi-mi-5-t3501971/post72149190

I didn't know what to search, I just searched for "home button"

Is it unfortunate that I already flashed the xiaomi EU, maybe when I'll get bored of it I'll come back :good:

Anyway thanks.
 

elot01

Senior Member
Mar 24, 2010
374
149
www.lotgerink.com
Nokia X10/X20
Amazfit
Is anyone else having weak GPS problems with the recent nightly updates?
I'm using sports tracker apps to track my workouts.
I've been using Adidas's train&run and tried Runtastic just to see if it's app related. Unfortunately got similar results.
fine: Monday, 24 Apr, 2017, 18:52 https://micoach.adidas.com/Track/PublicWorkout/c158715f-1b45-4247-9067-2d09bf38f44c
fine: Tuesday, 25 Apr, 2017, 18:47 https://micoach.adidas.com/Track/PublicWorkout/699edffb-3bde-4327-b7cc-4d3410850376
bad: Tuesday, 09 May, 2017, 18:59 https://micoach.adidas.com/Track/PublicWorkout/43d5ebe8-a42d-46e4-9282-c49fe8820216
bad: Thursday, 11 May, 2017, 18:35 https://micoach.adidas.com/Track/PublicWorkout/5592c67e-b03c-40af-a339-a5b5e5ff29da

Doze has been disabled for sports tracker apps (I was having similar problems before, then found out that Doze was the culprit)
GPS mode "high" and "device only" gave me the same results.
GPS works perfectly here on latest rom.
 

Veelog

Senior Member
Jun 12, 2015
105
29
Naga City, Camarines Sur
Yes, the LGD capacitive buttons work perfectly, but the touchscreen is still buggy. . . . After about 4 hours after clean install, it again doesn't register inputs 30% of the time. So I reverted to Dec. 23 7.1.1 JDCTeam build which has the old marshmallow blobs and the touchscreen works perfectly there though the capacitive buttons are completely unusable.

I am wondering if integrating those marshmallow blobs into the new builds could fix these touchscreen issues of LGD panels for good, that is, if it's possible to do so. :D
 
Last edited:

isu_mult

New member
Jan 3, 2009
3
0
Moscow
If, with an incoming call, I press the "home" button, the dialer turns into notifications and answer to the call is available only after entering the password. Is this the normal operation of my device? On stock rom (miui), the dialer remains on the full screen after pressing the "home" button.
 

shashank957

Senior Member
May 17, 2013
341
158
Pune
If, with an incoming call, I press the "home" button, the dialer turns into notifications and answer to the call is available only after entering the password. Is this the normal operation of my device? On stock rom (miui), the dialer remains on the full screen after pressing the "home" button.
it annoys me too, but logically, this is the default behavior,
sometimes you need to push the call screen to background if you are doing some important work.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 319
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:

    Broken:
    • Nothing. :)

    Working:
    • Everything except 'broken' stuff
      (see also second post for info on recurring questions)

    Screenshot_20161117_134349.png
    Screenshot_20161117_134404.png


    Compatibility:
    Compatible with all Xiaomi Mi 5 variants (32GB / 64GB / 128GB). Xiaomi Mi 5S and 5S Plus are not supported.
    Builds are based off the Xiaomi's Android 7.0 firmware with proprietary blobs from MIUI 8.1.4 dev package.​

    Downloads:

    Notice:
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

    Installation:
    • Reboot to recovery (TWRP recovery for Mi 5 - Direct link)
    • Format /system, /data and /cache
    • Install LineageOS zip package
    • Install [optional] the LineageOS su addon to get root (there are obviously other root methods, but this is the recommended one as it survives to OTA updates)
    • Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
    Important notes:
    • Current minimal * required * firmware version is MIUI 8.1.4 Global dev, otherwise installation will fail. Download the latest dev fastboot package directly from Xiaomi and flash it prior to installing LineageOS or, alternatively, download and install one of the latest custom packages containing firmware only (at your own risk).
    • GApps can only be flashed on clean installs.
    • Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    Credits & collaborations:
    This work is due to efforts from Mi5Devs founding members (@h2o64 and me) that did the full device bring-up. Huge thanks to @deovferreira for all the help during the kernel bring-up after source code dropped. Also thanks to @ValoXis for giving me the motivation I needed and to @shade.sh for compiling unofficial builds during the transition phase.

    Finally, all LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​


    Device wiki:

    Changelog:

    XDA:DevDB Information
    LineageOS 14.1, ROM for the Xiaomi Mi 5

    Contributors
    bgcngm, Mi5Devs
    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.18.x

    Version Information
    Status: Discontinued

    Created 2016-11-17
    Last Updated 2018-02-25
    128
    I really hope that everyone realizes that this is a development thread, aiming to provide support to official LineageOS for Xiaomi Mi 5. Everything that falls into unofficial category (e.g. unofficial builds and custom kernels) is not supported and not allowed here.

    Also be more respectful and grateful for the work I have already put into this. Think twice before saying that I don't care to fix things. For those who are not happy, you have plenty other ROMs out there. Funny enough, all based on Mi5Devs work.
    85
    Some notes due to recurring questions:
    • Camera OIS can be recalibrated, if needed, with the following app: https://github.com/dobragab/Mi5CameraCalibrate.
    • Devices assembled with LGD panels may have less responsive hardware keys (recents and back) due to old touchscreen drivers released by Xiaomi. The workaround at the moment is to enable on-screen buttons and wait for more updated drivers in the next kernel source code release.
    • QC3.0 is not fully working and will be fixed when the next kernel source code drops.
    79
    The most requested/wanted feature of all time is finally ready. @h2o64 and me spent countless hours in at least three different approaches.

    Screenshot_20170107-232137.png

    You can enjoy in probably a couple of days.

    Sent from my MI 5 using Tapatalk
    71
    Sadly, I regret to inform that I may have to drop official support for this device. The touchscreen replacement that I have received two days ago went fine, but the issue remains. I still get the random failures where touchscreen stops responding and I can't use the device as daily driver this way. I barely can use it for development either because I have to restart it over and over to get a few minutes of working touch. :(

    This is a pity because I liked Mi 5 a lot and a big loss as mine was the 128GB version with ceramic back. Luckily I have the good old M8 dual SIM, which has been my daily driver for a while now. That said, I am not looking for a new flagship to replace Mi 5 (yes, I don't think Mi 6 can justify the price) and already thought of buying a new one, but it seems that's no longer sold. Is there any good soul out there that eventually has switched to a newer flagship and wants to sell his Mi 5? :eek:
    So, this won't be goodbye after all... luckily two very kind users showed up and offered me their no longer used devices for a symbolic price.

    I still have a Mi5 128 GB version in white and I dont need it anymore.
    I've followed you through CM 13.1, LOS 14.1, and beta tested 15.

    We've chatted through messenger several times.

    I have the identical version, the black, ceramic 128gb. I've recently upgraded to a OnePlus 5T. I'll give you a deal if you want to continue?
    I really got to say thanks once again to you both. :highfive: I ended up buying from @mabor01 due to better shipping time and costs (and no customs involved).

    For everyone else, also a huge thanks for backing me up and supporting me with donations. :D