Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
CyanogenMod 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). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions:
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
What's important: if you use xposed - pls disable it and try it again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download Links:
CyanogenMod:
Nightly:
Download: http://download.cyanogenmod.org/?device=aries
Google Apps addon:
Use 4.4 gapps:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
Sourcecode:
ROM: https://github.com/CyanogenMod
Devicetree: https://github.com/CyanogenMod/android_device_xiaomi_aries
Kernel: https://github.com/CyanogenMod/android_kernel_xiaomi_aries
GENERAL COMMENT AND REQUEST:
We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"
Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).
We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.
Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-09-15
Last Updated 2014-09-15
Troubleshooting/ FAQs
I am reading FAQs, am I ok?
You're the best , but I'm not sure how you'll fell after you've read these things...
How can I enable Developer/ Performances Settings?
Go to Settings>Info>Click several times on build
How can I enable 4 way reboot (Recovery, System, soft, Bootloader) ?
Enable developer options, then go to Settings>Developer and enable Advanced Reboot
Why there's no HDR on camera?
Cyanogenmod does not provide closed source software, like drivers for HDR, you need to install Miui camera, or another camera from playstore
Why is there no Play Store or <insert gapp here>?
Since there are 2 system partitions they're small, and kk needs about 800mb to have a rom + gapps. There are 2 things u can do: First: install this gapps package this. Second way: use the repartition script of XiaomiTool to extend them.
Why is performances profile resetted every boot?
You need to enable Settings>performances>CPU>Set on boot
Why the phone doesn't fly if I enable airplane mode?
It's a WIP (work in progress) feature, now it works only if you throw it at 11,2 km/s² toward the space. It looks like there's no fix for this (yet).*
How can I enable adb root?
Go to Settings>Developer>Root access> Apps and Adb
How can I hide apps from trebuchet (launcher)?
Click Menu>Protected Apps> Set a "password"> Hide them
How can I charge my phone?
It looks like the xiaomi charger isn't enough powerful to charge the phone with cm. Here's your fix: buy a small nuclear reactor (you can find a cheap one on amazon or ebay I think), place the phone between the uranium fuel rods, power the reactor on and let the phone charging for about an half hour. It will be charged and it won't discharge again anymore.*
(I'm running art, it's very good and i feel better running it) This app FC... What can i do?
Switch to dalvik
Today I updated the phone and it's in a bootloop now...
Nice to get know you're enjoying art, switch back to dalvik flashing this
Bugs
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_aries
[DEV] How to build
http://wiki.cyanogenmod.org/w/Build_for_aries
Two Releases: Nightlies and Stable/Monthly
Nightlies and Monthlies are very different. YOU CAN NOT UPDATE FROM A NIGHTLY TO A MONTHLY WITHOUT A WIPE /DATA. Why? Simple, M releases uses a different branch and it's much older than the previous Nightly avaible, so this may cause bootloops.
So you can update from a Monthly to newer Nightly, but you cannot update from a Nightly to a Monthly. If you choose unstable branch (aka Nightlies) you shouldn't update via ota to Stable branch (aka Monthly), you need to wipe /data.
Other Info
http://wiki.cyanogenmod.org/w/Aries_Info
I'll be building Slim (and maybe Omni) for this soon, so I was wondering which vendor repo do you use?
Great I use themuppets https://github.com/TheMuppets/proprietary_vendor_xiaomi
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
SkaldfraNorden said:
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
Click to expand...
Click to collapse
yes
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
isaacbh said:
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
Click to expand...
Click to collapse
Sdcard format is not working well on cwm cuz of tdb. U have to flash a fastboot package and or flash a stock miui with miflash.
Tdb doesn't affect performances at all.
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Good to see we're moving to XDA!
m11kkaa said:
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Click to expand...
Click to collapse
Another scenario in which this bug showed for me was this. Maybe this is useful to track the issue.
I installed CWM 6.0.5.0, and then WIUI (4.7.18) based on KK.
After formatting the sdcard from within WIUI, even without rebooting, at that point the internal sdcard couldn't be written any longer from within WIUI.
I'm using this ROM and i'm really impressed.
One thing though is that my battery is going down much faster than on miui.
Any tips?
Check if you have wakelocks and freeze with greenify
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
you either have to flash a very small gapps package or resize your system partition(s)
thienquang07 said:
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
Click to expand...
Click to collapse
Read FAQs
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Mavamaarten said:
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Click to expand...
Click to collapse
Disable "sound on touch"
linuxxxx said:
Disable "sound on touch"
Click to expand...
Click to collapse
Oh god. I'm glad the fix is that simple. Thanks a bunch, I really didn't think of that.
I even disabled the "Okay Google" hotword because according to some googling the issue was connected to that.
Video camera records video maximum 10 minutes. Could it be changed to unlimited?
And also sound quality is very poor in recorded videos. I looked through spectrums and it appears that they are cut above 8000Hz. Seems like on some stage signal is being sampled with 16000 Hz sample rate and, judging by some bubbling and other artefacts, it is made without prior antialiasing filtering. Output format acc 48000 Hz.
I am not the author of this ROM, I just share it for you!
Unofficial MIUI 8 builds for Huawei Honor 6 by Ry09iu from China.
You can go to see Ry09iu Blog to find new Builds: http://r-rom.com/2016/11/29/huawei_miui8_release/
UPDATE LOGS
Fix when connect to PC, it does not show the notification about the connect ways.
Fix when connect to PC with some software(which can manage your phone), it does hot restart.
Fix when you did not give some apps Position or other permissions, it does restart.
Fix when you open some apps, it does restart.
Fix when you open Theme Manager, it does force crash.
Fix sometimes it shows dark screen or you could not use status bar.(If still, try to open Power saving mode)
Fix every time you boot phone, it shows "SD card: click into the file manager"
Fix on the phone cover from the sensor screen flicker problems will happen
Fix phone click recording function prompts the device being used
Fix Xposed cannot use problem, has been integrated in the Settings - advanced Settings - Xposed framework option, please do not brush Xposed framework into any other version
Add desktop icon custom function layout, can be used with proper DPI values( MIUI Settings - advanced Settings)
Remove the ROOT administrative authority authorized application tedious confirmed many times
Remove MIUI system protection on the application of the parts of the system, users to delete Mi Market/System Update can boot your phone normally.
Optimizing the time into the boot speed for the first time, although still very long, but shorter than before
I am not the author of this ROM, I just share it for you!
HOW TO INSTALL MIUI 8?
1. Unlock your bootloader
2. Upgrade your phone to EMUI 4.0
3. Flash TWRP
4. Download this ROM
5. Download Google Apps if you need(Well, I write an app to download OpenGApps:http://coolapk.com/apk/com.jakting.opengapps)
6. Wipe
7. Flash ROM and GApps if you need
8. Reboot and Enjoy
I am not the author of this ROM, I just share it for you!
Ry09iu said that it will be the final build for Honor6 MIUI8.
Get MIUI 8
[7.2.26] https://mega.nz/#F!ds0jXS7S!zeQdMLeaSf5DGWE9nsrvaw (Uploaded by @fazi2015 )
http://pan.plyz.net/s/?u=1192430225&p=miui_hwH60_7.2.26_8t5j4ad29r_6.0.zip
[6.12.12] http://pan.plyz.net/s/?u=1192430225&p=miui_hwH60_6.12.12_plfiass0h8_6.0.zip
XDA:DevDB Information
MIUI8(Shared), ROM for the Honor 6, Honor 6 Plus
Contributors
hjthjthjt, ry09iu
ROM OS Version: 6.0.x Marshmallow
Based On: MIUI
Version Information
Status: Alpha
Created 2017-01-23
Last Updated 2017-03-18
Nice rom but sim bug makes it unable to make calls and hence this rom needs work to render it for daily usage. Looking forward to use it...
nishant1695 said:
Nice rom but sim bug makes it unable to make calls and hence this rom needs work to render it for daily usage. Looking forward to use it...
Click to expand...
Click to collapse
You can make a call or send sms normally.
It just shows that "it has no signal", but working normally!:laugh:
hjthjthjt said:
You can make a call or send sms normally.
It just shows that "it has no signal", but working normally!:laugh:
Click to expand...
Click to collapse
I'm sorry i might have been mistaken... But i tried for like 30 minutes but was unable to place a call.
How long have you been using this rom? How's the performance, battery life etc.? Are there any other bugs we should be aware of?
nishant1695 said:
I'm sorry i might have been mistaken... But i tried for like 30 minutes but was unable to place a call.
How long have you been using this rom? How's the performance, battery life etc.? Are there any other bugs we should be aware of?
Click to expand...
Click to collapse
I am now with EMUI because I could not flash xposed on MIUI8 now.(I could use phone without xposed:silly
But other Chinese users said that these bugs will not influence your daily use.
Wow, this is like a dream come true. Do you think this ROM will be updated to fix the bugs (especially random reboots)? I'm looking forward to use it but I would prefer if there was a little bit more stable version for daily usage. Oh and by the way, what happened? Custom ROM based on Android 6.0 for Honor 6? Did Huawei finally release ALL the sources?
As for the SIM icon - I read on his blog that this problem happens only for the Sim Card #1. I think (but I'm not sure) than in MIUI you can actually mark SIM cards as #1 or #2 in settings. Maybe this bug could be "fixed" by simply changing the settings and marking SIM card as #2?
finnenhawke said:
Wow, this is like a dream come true. Do you think this ROM will be updated to fix the bugs (especially random reboots)? I'm looking forward to use it but I would prefer if there was a little bit more stable version for daily usage. Oh and by the way, what happened? Custom ROM based on Android 6.0 for Honor 6? Did Huawei finally release ALL the sources?
As for the SIM icon - I read on his blog that this problem happens only for the Sim Card #1. I think (but I'm not sure) than in MIUI you can actually mark SIM cards as #1 or #2 in settings. Maybe this bug could be "fixed" by simply changing the settings and marking SIM card as #2?
Click to expand...
Click to collapse
right now, nothing is a big issue, other than signal display.. unless it's perfectly usable.. and signal issues are quite common in miui ports.. honor 5x had it too. but solved eventually
finnenhawke said:
Wow, this is like a dream come true. Do you think this ROM will be updated to fix the bugs (especially random reboots)? I'm looking forward to use it but I would prefer if there was a little bit more stable version for daily usage. Oh and by the way, what happened? Custom ROM based on Android 6.0 for Honor 6? Did Huawei finally release ALL the sources?
As for the SIM icon - I read on his blog that this problem happens only for the Sim Card #1. I think (but I'm not sure) than in MIUI you can actually mark SIM cards as #1 or #2 in settings. Maybe this bug could be "fixed" by simply changing the settings and marking SIM card as #2?
Click to expand...
Click to collapse
6.12.12 is the first built for Honor 6. Since Ry09iu has been made so many ROMs for H60, like FIUI, Mokee, Flyme4, Flyme5, MIUI6,MIUI7, IUNI OS, BaiduOS, Tencent TOS, and so on!
So I think He will not give up ..
The way to build MIUI8 for honor 6 is that MIUI has put out patchrom, which help developers to make roms easily.
(So it is possible to make a CM13.0(Well, now called Lineage OS) on the same way, But no one did it...)
As for the SIM icon...Well, some Honor 6 supports TWO SIM CARDS.
Thanks for your answers. I installed it right now (on top of official B860 with TWRP 3.0.2). Unfortunately I seem to have a problem with my IMEI and Baseband. Every few seconds pop-up window appears, telling me that my Device ID is unknown and it couldn't find IMEI, therefore some Mi Account options like MiCloud will be unavailable. In my Settings > About Phone it says that Baseband is also "Unknown". I'm doing another Wipe Data / Factory Reset and we'll see how it goes. Other than that the ROM seems to work OK, however there are some chinese apps.
EDIT
Nope, it's even worse now. After doing a wipe in TWRP, phone boots up and shows the starting configuration screen. I choose language, press Next and it shows up the message that there is no SIM card. I press "Skip" and phone instantly reboots. It's the same every time.
EDIT2
OK, I figured what was the problem at the first time - I flashed OpenGAPPS just after I flashed MIUI, which was not a good idea, I guess, and caused the issue described above. I formatted everything in TWRP and reinstalled MIUI only (no GAPPS). System started and had the original MIUI configuration (before it was different, probably due to the openGapps). There are, however, some bugs.
First of all, the configuration can't be finished in my language (Polish). At the step where you can choose to enable or disable "Find my phone" option it would just kind of hang (you can't finish that step). When I pressed "Next" it would just slide back to the same screen over and over again. I couldn't get past that step. However when I switched the language to English in first step, the configuration went fine. So if you have troubles and you use other language than Chinese / English, then I recommend you finish the first-time setup in English and later on switch the language to the desired one in the settings.
Problem with SIM card is quite annoying. Device doesn't recognize SIM card (even though it might actually work) and the icon is flashing all the time at the status bar. Because of that Mobile Data switch doesn't work. By default Mobile Data is enabled all the time and you can't turn it off with the switch nor with the settings (settings crash when you try to go to anything SIM related). The only way to switch on/off mobile data is by connecting the device with USB cable and using ADB commands:
adb shell
svc data disable <- disables Mobile Data
adb shell
svc data enable <- enables Mobile Data
There's also plenty of chinese apps (some chinese store + chinese VOD). The browser also has some chinese texts + some options have chinese left-overs (Mi Account Settings). The performance itself is quite good and it's a good start. However for daily usage it, in my opinion, needs a bit more polishing. Would be nice if we had someone here that could make a port for Western countries like the modified KangVIP (removing chinese apps, repairing western languages and so on). Unfortunately I don't have that kind of skill so the only thing that I can do is to report bugs I noticed
finnenhawke said:
Thanks for your answers. I installed it right now (on top of official B860 with TWRP 3.0.2). Unfortunately I seem to have a problem with my IMEI and Baseband. Every few seconds pop-up window appears, telling me that my Device ID is unknown and it couldn't find IMEI, therefore some Mi Account options like MiCloud will be unavailable. In my Settings > About Phone it says that Baseband is also "Unknown". I'm doing another Wipe Data / Factory Reset and we'll see how it goes. Other than that the ROM seems to work OK, however there are some chinese apps.
EDIT
Nope, it's even worse now. After doing a wipe in TWRP, phone boots up and shows the starting configuration screen. I choose language, press Next and it shows up the message that there is no SIM card. I press "Skip" and phone instantly reboots. It's the same every time.
EDIT2
OK, I figured what was the problem at the first time - I flashed OpenGAPPS just after I flashed MIUI, which was not a good idea, I guess, and caused the issue described above. I formatted everything in TWRP and reinstalled MIUI only (no GAPPS). System started and had the original MIUI configuration (before it was different, probably due to the openGapps). There are, however, some bugs.
First of all, the configuration can't be finished in my language (Polish). At the step where you can choose to enable or disable "Find my phone" option it would just kind of hang (you can't finish that step). When I pressed "Next" it would just slide back to the same screen over and over again. I couldn't get past that step. However when I switched the language to English in first step, the configuration went fine. So if you have troubles and you use other language than Chinese / English, then I recommend you finish the first-time setup in English and later on switch the language to the desired one in the settings.
Problem with SIM card is quite annoying. Device doesn't recognize SIM card (even though it might actually work) and the icon is flashing all the time at the status bar. Because of that Mobile Data switch doesn't work. By default Mobile Data is enabled all the time and you can't turn it off with the switch nor with the settings (settings crash when you try to go to anything SIM related). The only way to switch on/off mobile data is by connecting the device with USB cable and using ADB commands:
adb shell
svc data disable <- disables Mobile Data
adb shell
svc data enable <- enables Mobile Data
There's also plenty of chinese apps (some chinese store + chinese VOD). The browser also has some chinese texts + some options have chinese left-overs (Mi Account Settings). The performance itself is quite good and it's a good start. However for daily usage it, in my opinion, needs a bit more polishing. Would be nice if we had someone here that could make a port for Western countries like the modified KangVIP (removing chinese apps, repairing western languages and so on). Unfortunately I don't have that kind of skill so the only thing that I can do is to report bugs I noticed
Click to expand...
Click to collapse
THANKS FOR YOUR TEST!!!
I will try to report bugs you found to Ry09iu
(if He will listen to me. Some developers In China did not like answer users' questions because there are too many users trying to report their questions.)
In My test, I flash OpenGApps at the same time and it can start Into system. So I think it is not a bug or just OpenGApps's bug.
hjthjthjt said:
THANKS FOR YOUR TEST!!!
I will try to report bugs you found to Ry09iu
(if He will listen to me. Some developers In China did not like answer users' questions because there are too many users trying to report their questions.)
In My test, I flash OpenGApps at the same time and it can start Into system. So I think it is not a bug or just OpenGApps's bug.
Click to expand...
Click to collapse
Yeah, I normally do that on other phones too. I can flash CM13 and then flash OpenGapps just after that and it works perfectly fine. However for some reason it didn't work too good on my Honor 6 with this MIUI ROM (I'm using H60-L04 btw). Maybe there was some error during installation, hard to say. However whenever I started my phone it would show up "No SIM Card" screen immedietaly on top of MIUI Configuration. When I pressed "Skip" my phone automatically restarted. Weird - that probably would fix itself automatically after SIM Card bug is fixed in MIUI.
finnenhawke said:
Yeah, I normally do that on other phones too. I can flash CM13 and then flash OpenGapps just after that and it works perfectly fine. However for some reason it didn't work too good on my Honor 6 with this MIUI ROM (I'm using H60-L04 btw). Maybe there was some error during installation, hard to say. However whenever I started my phone it would show up "No SIM Card" screen immedietaly on top of MIUI Configuration. When I pressed "Skip" my phone automatically restarted. Weird - that probably would fix itself automatically after SIM Card bug is fixed in MIUI.
Click to expand...
Click to collapse
I use H60-L01 and OpenGApps seems works normally.
I uploaded it to mega all of you now easily download it miui8(7.2.26)
https://mega.nz/#F!ds0jXS7S!zeQdMLeaSf5DGWE9nsrvaw
fazi2015 said:
I uploaded it to mega all of you now easily download it miui8(7.2.26)
https://mega.nz/#F!ds0jXS7S!zeQdMLeaSf5DGWE9nsrvaw
Click to expand...
Click to collapse
Bro do u experience battery drainage?
@hjthjthjt could you request Ry09iu to fix the sim card bug in the next update?
omeir7 said:
Bro do u experience battery drainage?
Click to expand...
Click to collapse
Yes and some other bugs it's not for daily drive...
there are still bug?
wiizard91 said:
there are still bug?
Click to expand...
Click to collapse
yes but in development forum I create a post to request developer to fix it you also have to do so if you want it in stable conduction the developer of this rom is belong to China no other claim it but @Ale who can fix the bugs we have to request hin...
How do you go back to stock EMUI from this MIUI 8 ROM?
I have the Indian H60-L04 model, and I would like to know how to go back from this MIUI 8 ROM to the normal EMUI ROM.
Thanks for any help!
pranayshah said:
I have the Indian H60-L04 model, and I would like to know how to go back from this MIUI 8 ROM to the normal EMUI ROM.
Thanks for any help!
Click to expand...
Click to collapse
simply wipe all and flash rom..
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
jtk_de said:
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
Click to expand...
Click to collapse
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Re:
lba810701 said:
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Click to expand...
Click to collapse
To install, as with the Sony AOSP ROM, your bootloader must have been unlocked. After installation via fastboot root access can be enabled in the developer options.
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Re:
lba810701 said:
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Click to expand...
Click to collapse
Thank you for testing. You're right there's some more issues. I was able to unlock the phone with the fingerprint sensor once but I guess this should work a little bit more smoothly. Face camera image is vertically flipped. Normal phone operation seems to be OK, battery runtime also. Didn't examine core load nor install Google apps so I can't say anything about it. All in all it looks quite usable but needs a little bit of fine tuning
Flashed your ROM yesterday (coming from an unofficial cm14.1 build) and till now everything runs smooth. I didn't flash recovery.img since I already had twrp flashed and flashing opengapps was also successful. Fingerprint sensor is working too. The camera quality is bad, but that's what I have with every custom ROM.
Issues I found out so far:
- registering the fingerprint sensor for purchases in the play store doesn't work, play store closes upon trying to set it up
- the volume when calling can't be changed
Maybe there's something else but I'm really satisfied. I hope you keep on updating the rom jtk_de
can you give us a short update on this?
Still Progressing?
Is this still being developed?
The thread seems to have been continued here: https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504/
jtk_de said:
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Click to expand...
Click to collapse
@jtk_de
Is there currently any place where can I find the source code?
The reason I ask this question is that SonyLOS (github.com/SonyLOS) has been removed.
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.
Code:
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
Welcome to COSP, your new future Android Operating System.
Our goal is to have an Pixel-like android ROM that isn't spying on you and uses as few system space as possible. Also, we provide the option to go completely without GApps using MicroG support.
Why us?
We are focusing on stability and performance, having an debloated ROM is essential for that. Also, we want Users to decide what kind of Store they want to use, either F-Droid or the Play Store.
Also, we take User requests serious. To suggest something, contact us on telegram.
Features:
1) All systemUI tuning elements
2) An handy Network indicator
3) Charging Information
4) Lawnchair and Quickstep as default
5) Quick Settings mods
6) Signature spoofing
7) OP gestures
8) Navbar tuner
9) Rootless Substratum (with fixes to theme system correctly)
10) Screenshot/screenrecord tile
11) Advanced power menu
12) Double tap to sleep on statusbar
13) Option to disable quick settings/power menu on secure lockscreen
OTA Updating for official devices enables Users to get the newest version with ease.
DOWNLOADS:
https://mirror.codebucket.de/cosp/santoni/COSP-190507-OFFICIAL-santoni.zip
Sources:
ROM Source: https://github.com/cosp-project/
Kernel Source code: https://github.com/HarukeyUA/android_kernel_xiaomi_santoni
Device Tree: Coming Soon
ChangeLog:-07-05-2019
COSP Changelog
From April to May patch
New:
+ May security patch merged
+ replaced Lawnchair with Launcher3 from @aosiP
+ App Ops/Privacy Guard
+ Agressive Battery from @aosiP
+ Accent picker from @PixelExperience
+ seperate ringtone for second sim
+ translations: russian, italian, simplified chinese
+ font picker
+ more steps for font size
+ search bar hiding in launcher
+ switch for fingerprint authentication vibration
+ switch for inverting navbar layout
+ button on FC dialog for sending crash info to dogbin
Fixed:
* QS padding on statusbar
* crash on security settings
* LTE+ icon
* app swithching on OP gestures
* sepolicy
Removed:
- "press power on lock screen for torch" (it wasn't working anyway)
Download:
https://mirror.codebucket.de/cosp/santoni/COSP-190507-OFFICIAL-santoni.zip
Hi, I'm testing this rom for a week, and ... the rom is basically have too lag even to move apps from day to day like twitter, facebook, google chrome and firefox also go very slow too,
regards
folderx said:
Hi, I'm testing this rom for a week, and ... the rom is basically have too lag even to move apps from day to day like twitter, facebook, google chrome and firefox also go very slow too,
regards
Click to expand...
Click to collapse
No bug i found. change kernel and check
i am also using this rom for a week or so. clean flashed. even formatted the storage before installation. so far this is one of the best roms i have ever used on santoni. and i can say that i have used almost every one of them. great battery life, great performance.
Sorry for the inconvenience, it was not the fault of the rom, it was because I had activated the option of digital well-being, I deactivated it and now it works great
Cosp Official June Update
Changelog:
+ June security patch merged
+ More modes for location tile
+ Captive portal switch (Settings -> Network & Internet)
+ "More info" on permission dialog, thx to @GrapheneOS
+ Incall vibration options (COSP Settings -> Miscellaneous)
Changed:
* DNS.watch by default everywhere
* moved PrivacyGuard (COSP Settings -> Miscellaneous)
* moved Reading Mode (COSP Settings -> Miscellaneous)
* volte icon
* some permissions changes by @GrapheneOS
Fixes:
* fixed AgressiveBattery auto enable
* fixes in PrivacyGuard
* minor SurfaceFlinger fixes (hopefully fix color correction)
* minor Settings fixes
* minor LatinIME fixes
Download:
https://mirror.codebucket.de/cosp/santoni/COSP-190604-OFFICIAL-santoni.zip
I did the latest OTA-Update and now my device stuck in a bootloop at the Mi-branding. No success getting into recovery (was Orangefox), so I flashed a new one with fastboot. I restored my last backup, which was working before, but it gave me the same result - bootloop! Anyone experiences the same or any idea where to search or how to fix this? I used Magisk by the way...
gorillus said:
I did the latest OTA-Update and now my device stuck in a bootloop at the Mi-branding. No success getting into recovery (was Orangefox), so I flashed a new one with fastboot. I restored my last backup, which was working before, but it gave me the same result - bootloop! Anyone experiences the same or any idea where to search or how to fix this? I used Magisk by the way...
Click to expand...
Click to collapse
Hi. Had this problem with clean flash too. Its not your fault Sir. I dont know if Bikram already had time to change link here. But its fixed for sure.
I downloaded and flashed this update last night :
https://sourceforge.net/projects/bi...Pie/COSP-190604-OFFICIAL-santoni.zip/download
Rom boots and work as it should!
Wifi is not working in latest update, please help
Bhanu_p_mishra said:
Wifi is not working in latest update, please help
Click to expand...
Click to collapse
How did you flash Sir? I did clean flash and Wifi works.
Samuitan said:
How did you flash Sir? I did clean flash and Wifi works.
Click to expand...
Click to collapse
I also clean flashed it, though used migrator to restore apps, perhaps this is the reason for that
---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------
Bhanu_p_mishra said:
I also clean flashed it, though used migrator to restore apps, perhaps this is the reason for that
Click to expand...
Click to collapse
By the way which kernel do you used with this build
Bhanu_p_mishra said:
I also clean flashed it, though used migrator to restore apps, perhaps this is the reason for that
Click to expand...
Click to collapse
You mean Migrate? I use it also to restore Userapps. I think thats not the reason .
What do you wipe for clean flash?
I wipe everything except Internal and SD Card.
Then Flash Rom and Gapps. Reboot and do Google Stuff.
After that go back to Recovery and flash Magisk and Migrate Backup zip.
Have no Problems . Try it!
Samuitan said:
You mean Migrate? I use it also to restore Userapps. I think thats not the reason .
What do you wipe for clean flash?
I wipe everything except Internal and SD Card.
Then Flash Rom and Gapps. Reboot and do Google Stuff.
After that go back to Recovery and flash Magisk and Migrate Backup zip.
Have no Problems . Try it!
Click to expand...
Click to collapse
I actually unable to understand the steps to use migrator, could you please suggest me the actual steps that you used to use migrate for rom migration purpose.
Bhanu_p_mishra said:
I actually unable to understand the steps to use migrator, could you please suggest me the actual steps that you used to use migrate for rom migration purpose.
Click to expand...
Click to collapse
Im confused. You said you use Migrate? Then you made a backup or not? What steps exactly make you headache?
I posted once my restore steps in Migrate Thread. Scroll down.
Read a little bit there too for understanding how it works.
And what about Wifi? Works now?
Samuitan said:
Im confused. You said you use Migrate? Then you made a backup or not? What steps exactly make you headache?
I posted once my restore steps in Migrate Thread. Scroll down.
Read a little bit there too for understanding how it works.
And what about Wifi? Works now?
Click to expand...
Click to collapse
I am actually using migrator which is a magisk module(not currently supported) which is different from the migrate app that you quoted, not knowing earlier about this, thanks for your post, going to try clean flash with migrate app and then see how WiFi works
Bhanu_p_mishra said:
I am actually using migrator which is a magisk module(not currently supported) which is different from the migrate app that you quoted, not knowing earlier about this, thanks for your post, going to try clean flash with migrate app and then see how WiFi works
Click to expand...
Click to collapse
You're Welcome.
Ok.. just a misunderstanding lol. Dont know about Magisk Module. I dont use any.
Yes try Migrate. Its really good. I often flash different Roms.
Please give feedback if everything works then
I would like to try this ROM too.
Does the menu translated into Romanian?
McJohn.br said:
I would like to try this ROM too.
Does the menu translated into Romanian?
Click to expand...
Click to collapse
Seems so..
Edit: Sorry wrong Rom..Thats Derpfest lol.
Samuitan said:
Seems so..
Edit: Sorry wrong Rom..Thats Derpfest lol.
Click to expand...
Click to collapse
Attached image cannot be seen!
What was that about ?