yashsingh1/xdaforums huggingface dataset:
[Mi 3 Original Android Development] saidinesh5:
My Mi3 only has 3G., but afaik that worked fine for me. Will look into this issue.

https://github.com/CancroSailors/droid-config-cancro/commit/3ada749c98e98edcbb1f8e9ddfdb29fd9ce277b5 This commit should hopefully fix a lot of touchscreen issues. This is also part of the next OTA update, but feel free to add this change yourself locally, till you get the update.

I am using the default config file for vibration. It can be configured here: https://github.com/CancroSailors/dr...ib/qt5/plugins/feedback/qtfeedback-cancro.ini (the corresponding file on the device is: /usr/lib/qt5/plugins/feedback/qtfeedback-cancro.ini ). Tweak the values there to your liking and share the config back here. If enough people here like those settings, we can merge them back into the source and make it available to everyone for the next release. https://github.com/CancroSailors/an...fe94c1cb25f54c84e/drivers/tspdrv/ImmVibeSPI.c is the kernel driver we are using, just in case, you need more info.

Missing contacts while syncing CardDAV account.

Anyway, still it is very useful for me. I appreciate your work, thank you very much.[/QUOTE]

Need more info to look into these issues. Some kind of backtrace would be nice to see why the crashes exist. However these do sound like bugs in the upstream, and probably are not specific to the device. For these issues, feel free to get support here: https://together.jolla.com/ and file a bugreport for the upstream.

Whenever the changes we make to the sources are tested and considered stable, I upload the new packages to : https://build.merproject.org/project/show/nemo:testing:hw:xiaomi:cancro and they will be delivered via. OTA. and installed as normal system updates. Just like any other linux distro. Just in case back up your data in SFOS. All your SFOS data stays in /data/.stowaways/sailfishos/home/nemo.

Cheers!
[Mi 3 Original Android Development] isgursoy:
Thanks for the explanation.
[Mi 3 Original Android Development] isgursoy:
I can not use trello for issues. "Only people added to the board can edit it."

-Resolution is 2MP for the front camera, and the rear cam is 8MP.
[Mi 3 Original Android Development] saidinesh5:
Oh.. my bad.

Camera resolution related configs are in here:

https://github.com/CancroSailors/dr...rse/etc/dconf/db/vendor.d/jolla-camera-hw.txt . So you can add it to the issues there.

Right now there is a bug in the camera app , that's resetting the viewfinder resolution to an odd ratio. Maybe they both are related? Try out with a 3rd party camera app from warehouse/Jolla store.
[Mi 3 Original Android Development] isgursoy:
Great, How can I donate?
[Mi 3 Original Android Development] saidinesh5:
Lol. I actually am not sure what you mean by this. If it is code/contribution - everything goes to the open github repos.

Just in case, I did update my profile info with my flattr id. heh

Cheers
[Mi 3 Original Android Development] Tomi_Ohl:
Review after one week

I've just came back to Android yesterday after a week on Sailfish. Final thoughts:

Maybe. And also it's the weakest point of the OS, in terms of user experience. It was really slow, when I was working with complex websites/multiple tabs. I've heard that they're working on a new browser engine which will come in an upcoming Sailfish release, that should solve these issues. Also, I've heard you were working on sth to quickly open links, that'll be cool too. :)

Nice to hear :good:

Currently you should reboot only if you have time, cause probably you'll have to try multiple times... :D So waiting for next release :)

Apart from Browser, one more thing bothered me, but it's not connected with the port: Sailorgram, the SF Telegram client has a strange bug, when you lose some messages... Apparently it's fixed in the source already, but no new beta came out since then.

When migrating back to Android, I've used Sailfish SMS exporter to extract my call log and messages. The command for copying the commhistory file didn't work for me, but after manually copying it to the same folder where I placed the script, it worked, and I could successfully restore them on Android. This might be useful for others too. :)
[Mi 3 Original Android Development] saidinesh5:
Wow. News certainly tranvels fast over here! Yeah that's one of the things that's keeping me busy - from merging the patches and SFDroid work. Wanted to do something for the Maemo Coding competition.

Oh that's the nice thing about most Sailfish OS stuff. The code is all out there, for anyone to tinker with/compile. Buiding an RPM doesn't take much effort either. You upload the sources with the spec file to OBS and it creates your rpm for you - or simply setup a mer sdk and compile the package locally. Even for the little browser i was building, Sailfish didn't support a feature I needed, so I looked into the code of it's compositor and patched it to make this app work.

I think we should have a FAQ section with all these little tips from these thread. Do you know any place we could add it?
[Mi 3 Original Android Development] Tomi_Ohl:
Actually, building an Android app from source wouldn't be a problem for me, but I don't have any experiences with Sailfish. Now after reading your comment, I've Googled it and it really doesn't look difficult. Who knows, if the dev won't make a new Sailorgram build before I return to Sailfish, maybe I'll make one.

There's a general Sailfish FAQ which I found earlier, but it wasn't updated since more than a year.

For now, maybe it would be enough if you copied/linked these advices to the first or third post in this thread.
[Mi 3 Original Android Development] saidinesh5:
Just a quick update: I published the version 0.1 of the browser to OpenRepos: https://openrepos.net/content/saidinesh5/droplet-browser . Make sure to install and enable the lipstick patch before trying out the browser though ( https://coderus.openrepos.net/pm2/project/sailfishos-lipstick-enable-applets ). It is still very basic though, but takes the pain away from clicking the links in my events feed/Sailorgram. I think it will actually be useful once I set up a proxy server that sends only the article to be read, thereby cutting down the CPU and Mobile data costs. I am half way through merging Ar4er's patches. I will try to merge the remainder by the end of today and push out the OTA (can't promise) before getting super busy with real life for the next 2 weeks.
[Mi 3 Original Android Development] isgursoy:
Yes i mean $$$. By the way, browser works very well.

What about 3g fix, is there any possibility to have that patch in next ota?
[Mi 3 Original Android Development] saidinesh5:
Thank you :)

Right now the first priority is really to get SFDroid up and running. I am a little busy till the 14th with some tests in real life i need to be preparing for. So after SFDroid, I will look into the 3G issues on Mi4. (You have a Mi4W right? Is your model the same as Nokius'?)
[Mi 3 Original Android Development] isgursoy:
You are welcome. You deserve more than I can donate :)

Yes SFDroid would be great too.

Actually I don't know which Mi4 I have, it has 3GB memory and 64 GB storage, so probably yes.
[Mi 3 Original Android Development] saidinesh5:
Out of curiosity, how do you know 3G is not working? For me I see the 3G logo on my phone in the signal area.. Also,

$qdbus --system org.ofono /ril_0 org.ofono.NetworkMonitor.GetServingCellInformation

gives Technology: umts . Can anyone with an Mi4 in this thread, confirm this issue?
[Mi 3 Original Android Development] isgursoy:
I can only see 2G and it is noticeable slower to make sure that is true.

[nemo@Sailfish ~]$ qdbus --system org.ofono /ril_0 org.ofono.NetworkMonitor.GetServingCellInformation
BitErrorRate: c
CellId: 19362
LocationAreaCode: 13415
MobileCountryCode: 286
MobileNetworkCode: 03
Strength:
Technology: gsm

+ drains battery almost %10 per hour.
[Mi 3 Original Android Development] saidinesh5:
Battery drain - tough one. I am getting consistently more battery out of Sailfish OS than I was in CyanogenMod 12.1. Could you see if any background process was taking up all the CPU or something? Ar4er found this one issue where turning tethering on and off was preventing the device from going to sleep. That could be a cause for battery drain too. (Will fix it in the next build). There maybe other things that could be preventing your device from going to sleep mode. You can check the open wakelocks for that:

cat /sys/power/wake_lock

Btw. did you get 3G network in CyanogenMod on the same device?
[Mi 3 Original Android Development] isgursoy:
Power consumption is getting normal if i disable cellular internet. Yes 3G and LTE were working fine.

wake_lock output:

dsme_iphb_wakeup mce_cpu_keepalive mce_display_on
[Mi 3 Original Android Development] isgursoy:
Anyway, I won't back to android or anything looks like an os. I don't care any of them, sfos on mi4 is great and thank you very much for making it possible.
[Mi 3 Original Android Development] saidinesh5:
Btw. these wakelocks are to be checked when you expect the device to be in sleep mode.. and not when your device is connected to the the PC/charger or something.

You probably need to write some script / little app to keep track of these wakelocks. Will definitely have to optimize this.

http://ruleoftech.com/2014/debugging-sailfish-os-application-power-consumption is a useful read on this topic btw.
[Mi 3 Original Android Development] abhisek de:
Are u all continuing this project??
[Mi 3 Original Android Development] saidinesh5:
Right now my real life is a little hectic till this 14th. After that, I will be back to this project - with SFDroid (Android app support) being the priority. There is a 2.1.0 version coming up quite soon too.
[Mi 3 Original Android Development] OG SWAT RV:
Hi,

thank you for porting sailfish OS.

I use it since 3 weeks 27/7.

( Before I used the BQ Aquaris E5 HD Ubuntu edition, but they stop the development, so I choose the Mi3 with sailfish OS )

I love it. Sometimes when it is switched out, it start from alone. And rebooting sometimes take long. Once my bluetooth was on, and the screen freezes.

But I do not have more issues.

I hope you continue the porting . Cant wait for 2.1.0 version and SFDroid .

Greetings
[Mi 3 Original Android Development] saidinesh5:
Thanks a lot for your support!

The screen freezing issue should be considerably minimized with the next version, if not completely fixed. Could you add this file to your device and reboot it to see if you still have the ocassional screen issues? https://github.com/CancroSailors/droid-config-cancro/commit/3ada749c98e98edcbb1f8e9ddfdb29fd9ce277b5 .

The rebooting taking longer than usual is a boot loop that's happening because some partitions not mounting in time. I will have to look into this bit again though. Could be a systemd issue too.

And yep, I will have to look into 2.1.0 porting earlier than I thought as I have been told there were some issues with the droplet browser on it.
[Mi 3 Original Android Development] mixmoto:
Hi [MENTION=7587193]saidinesh5[/MENTION]

How proceed your good work on sailfish for cancel devices?

Thanks for your good work!!!
[Mi 3 Original Android Development] saidinesh5:
Hi,

I have compiled a 2.1 Early Access version for cancro 2 days ago. Right now testing it out and fixing bugs - So if all goes well, the 2.1 version should be available to general public once Sailfish OS 2.1 is released for general public. (We are not allowed to make a release until Jolla releases 2.1 to general public).

As for SFDroid, my packaging script ( https://gist.github.com/saidinesh5/3262c31c88776445544c8b2804ee02df ) for SFDroid was used to get a basic version up and running on Xiaomi Redmi 2. But I am working on a different approach - to get SFDroid working inside a chroot. I think it will take a little longer to get it up and running this way, but it should let us start/stop sfdroid on demand, and also let SFDroid not mess up your phone's data partition. (So far I have corrupted my phone's data a bunch of times when trying to get SFdroid up and running!).

P.S Right now I would really appreciate if the Android devs in here to help me debug the issues with SFdroid - where zygote is crashing with: F/art ( 9925): art/runtime/jni_internal.cc:769] JNI FatalError called: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
[Mi 3 Original Android Development] mixmoto:
[MENTION=7587193]saidinesh5[/MENTION] thank you! Good news! I would have the copy and paste function that SF 2.1 have! ;)
[Mi 3 Original Android Development] art_ne:
Hello, how to acscess mnt/sdcard?
[Mi 3 Original Android Development] allefarben:
THX for the great work porting sfos to the cancro.

I installed the CM12.1 without problems and it is running well on my mi4.

But when i try to install sailfishos i got these output:

Device check succeeded, mounting filesystems ...
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
Copying filesystem archive ...
Copying installation script ...
Running installation script ...
Failed to extract filesystem!
E: Error in /data/media/sailfishos-cancro-release-2.0.5.6-alpha2.zip
(Status 7)
installation aborted.
E:replace_device_node: could not delete node!
E:replace_device_node: could not delete node!
E:replace_device_node: could not delete node!

Deleting the assert-line in the updater-script doesn't change anything.

What is with this partition issue on the mi, is that the problem?

How can i check if the partitions are correct?

Thanks in advance.
[Mi 3 Original Android Development] saidinesh5:
The /sdcard of android should also be available in /data/media/0
[Mi 3 Original Android Development] saidinesh5:
$ls -l /dev/block/platform/msm_sdcc.1/by-name

lrwxrwxrwx root root 2017-03-11 23:40 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-11 23:40 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-11 23:40 bk1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-11 23:40 bk2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-11 23:40 bk3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-11 23:40 bk4 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-11 23:40 bk5 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-11 23:40 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-11 23:40 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2017-03-11 23:40 dbi -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-11 23:40 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-11 23:40 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-11 23:40 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-11 23:40 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-11 23:40 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2017-03-11 23:40 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-11 23:40 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-11 23:40 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-11 23:40 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2017-03-11 23:40 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-11 23:40 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-11 23:40 ssd -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-11 23:40 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2017-03-11 23:40 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-11 23:40 userdata -> /dev/block/mmcblk0p25

That's how the partition layout on my device looks like. Is it the same for you?
[Mi 3 Original Android Development] allefarben:
THX for your fast reply.

It looks like the same:

./adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 20 Mar 16 17:23 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Mar 16 17:23 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Mar 16 17:23 bk1 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk3 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk4 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Mar 16 17:23 bk5 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Mar 16 17:23 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Mar 16 17:23 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Mar 16 17:23 dbi -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Mar 16 17:23 fsc -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Mar 16 17:23 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Mar 16 17:23 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Mar 16 17:23 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Mar 16 17:23 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Mar 16 17:23 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Mar 16 17:23 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Mar 16 17:23 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Mar 16 17:23 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Mar 16 17:23 ssd -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Mar 16 17:23 system -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Mar 16 17:23 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Mar 16 17:23 userdata -> /dev/block/mmcblk0p25

Any idea?
[Mi 3 Original Android Development] saidinesh5:
How much free space do you have?

Are these "errors"/"warnings" okay to ignore? Could you confirm by manually trying to mount /data in recovery and see if it is actually your data partition?

#mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data

Is the zip file corrupted? e60904170317ea098736ab21f830853c is the md5 sum for the public build of 2.0.5.6.

Not sure what's causing the issue: "E:replace_device_node: could not delete node!",

P.S If too impatient to wrestle with TWRP, you can

1) manually extract the rootfs in tar.bz2 inside the zip to /data/.stowaways/sailfishos/ (as shown in the updater-unpack.sh inside the zip)

2) manually flash the hybris-boot.img to your boot partition.

#fastboot flash boot hybris-boot.img
[Mi 3 Original Android Development] saidinesh5:
It looks like this is the right path. Out of curiosity, do you have a multirom based TWRP or something? Not sure what's hiding the /dev/block/mmcblk0p25.

First back up your boot.img and then extract Sailfish to this path, and then flash hybris-boot.img

You can use https://www.androidfilehost.com/?fid=457095661767125252 image for Sailfish. It has telnet enabled at the boot time, to help you debug things. You can access telnet by : telnet 192.168.2.15 2323 or telnet 192.168.2.15 23 . The phone should give your PC an IP address in the 192.168.2.X subnet. If not, feel free to give your PC a static IP.

Good Luck!
[Mi 3 Original Android Development] iToolSoft:
Thank for your excellent job，I flashed this rom and now the Chinese input cannot work，would you fix this issue on next version？
[Mi 3 Original Android Development] saidinesh5:
Hi,

I think the Chinesse input methods were Jolla proprietary packages that are not available for the ports.

Could you try out Dolphin keyboard instead?

I think we have to sit down and port the QtVirtual Keyboard or something else for proper chinese input and even T9 input.

Cheers,

D
[JASJAR, XDA Exec, MDA Pro Software Upgrading] BryanAdams:
Dear all,

I am Looking for the cab file of HTC prog. which If i press on one button it will be closed not minimized .

could you give me the link for that ?!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] zeeshansohail:
download pBar 1.5 from http://www.freewareppc.com/utilities/pbar.shtml. You can tell what the "X" button is supposed to do ... close/minimize/open options menu. In addition, this also works as a really nice task manager!

enjoy!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Just about right:
Go to here....

http://xdaforums.com/showthread.php?t=344533
[JASJAR, XDA Exec, MDA Pro Software Upgrading] BryanAdams:
zeeshansohail,Just about right

Thanks For The Help I Truly Appreciate It :)
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
Hi,

Yesterday the developer options were still there and now they've suddenly disappeared. I tried fixing this myself by doing the following things:

- Flashing latest CM13 nightly

- Tapping on build number a lot of times (did not pop up any toasts)

- Clearing data and cache of Settings app

and the developer options still not reappeared.

I'm currently running XT1541 with CM13 with root, Xposed, Kali Kernel overlay.
[Moto G 2015 Q&A, Help & Troubleshooting] Nikos dima:
Maybe the ptoblem is the kali kernel. I also have xt1541 cm13 ,xpose,stock kernel and i dont have any problem
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
Hi, I've dirty flashed another kernel and the problem still does not go away. Thanks for your reply.
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
I don't think it's a kernel issue. Have you tried clearing data of CM Setting Storage and rebooting ?

Broadcasted from Zeta Retuculi
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
I navigated to Settings>Apps>Settings>Storage and wiped app data. The settings app crashed after doing that, don't know if that's normal. I rebooted and the dev options still do not work.
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
I was talking about another app called 'CM device storage' mate.

Broadcasted from Zeta Retuculi
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
Ohh gotcha ;)

If I click on "Clear Data" it does not prompt me if I want to clear the data like it does with other apps, nor does it actually delete the data.
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
I thought that might work for it's name. No ideas then, sorry.

Broadcasted from Zeta Retuculi
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
Update: I can access dev options now via a 3rd party app, now it says "developer options not available for this user." I've searched this on Google and tried many different things, no luck yet
[Moto G 2015 Q&A, Help & Troubleshooting] WaxysDargle:
sorry, but youre probably gonna have to clear data and cache in TWRP for a 'factory reset'
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
Yeah if I really need to, I'll consider doing a fac reset. The only problem is that there is a lot of personal data and apps from my work on my phone. Can I transfer data or something?
[Moto G 2015 Q&A, Help & Troubleshooting] WaxysDargle:
you could also do a backup, and then do a dirty re-flash of the same ROM/Gapps... key thing being BACKUP FIRST
[Moto G 2015 Q&A, Help & Troubleshooting] xDantehh:
I have tried reflashing multiple nightlies but they did not restore the dev options for me. Thanks for replying quick though!
[Zuk Z1 Q&A, Help & Troubleshooting] nomadman:
Hi,

Why does google play insists that the unti is a Sony Xperia Z1? I'm using the latest NucleaRom as of this post. I can't install some apps on the play store that I used to can when I had the original CM12.1 installed. Any hints would help.

Thanks

=====

Build Info:

product: Z1

device: Z1

model: Z1

Is the above correct?
[Zuk Z1 Q&A, Help & Troubleshooting] nomadman:
resolved the issue.
[Zuk Z1 Q&A, Help & Troubleshooting] vikas966591:
How...
[Zuk Z1 Q&A, Help & Troubleshooting] nomadman:
root, edit build.prop, change to ro.product.model=ZUK Z1
[Zuk Z1 Q&A, Help & Troubleshooting] vikas966591:
I am rooted..

Unable to edit build.prop using kernel aduitor mod.

Any other recommendation
[Zuk Z1 Q&A, Help & Troubleshooting] nomadman:
Use buildprop editor
[Zuk Z1 Q&A, Help & Troubleshooting] vikas966591:
In settings> about phone still showing z1

---------- Post added at 09:05 PM ---------- Previous post was at 09:02 PM ----------

If you don't mind, can you confirm Whats your about phone is saying