Related
[Q&A] [CM ROM [hlte/universal] OFFICIAL CyanogenMod Builds (Nightlies) Maintainer Th
Q&A for [CM ROM [hlte/universal] OFFICIAL CyanogenMod Builds (Nightlies) Maintainer Thread
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM ROM [hlte/universal] OFFICIAL CyanogenMod Builds (Nightlies) Maintainer Thread. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
zmore said:
Zero random reboots. Most impressive.
The only real annoying bug I've run into on each nightly so far is with Bluetooth A2DP audio: the volume doesn't change consistently across the slider, and, seemingly randomly the bt volume will start ramping up by itself and I have to toggle the vol butons up/down to make it quiet again. (I saw some BT fixes in the 0108 nightly changelog, but the bug remains)
Click to expand...
Click to collapse
And I can't pair my wearable, so bluetooth needs a bit of fixing. Also the battery drain is 40% Miscellanous, so it's quite high.
But all in all, I'm sticking to it, totally usable as a daily driver.
Nightly 20150110, bluetooth works fine, wearable connects, thanks.
I'll check the battery drain and report the miscellaneous value later today.
Also it must be a Lolliipop issue, but if I toggle Location on/off it will always turn on high accuracy mode and not the previous mode. Also if GPS is on, it wakes up the phone even in Airplane mode.
Battery drain
Here's the battery drain since this morning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notification question
If I want to disable the "heads up" (or what we call that) notifications, how, and where can I do that? Does somebody know this? I'm not refer to the sounds. That notification popup on the top of the screen, when I get a call, a message, etc. I want to use Heads Up, from play store. I can install it, but in that case, I have double notifications. Who can help me please?
CM 12 clean & dirty flash = broken cellular connection
Hi,
So i am currently on temasek unofficial 12 v3.4 because it is the only build that allows cell connection to work. Ive tried to dirty flash and clean flash, several times, CM 12 hltespr but it breaks my cell connection.
I have a Galaxy Note 3 on Sprint and have been running some form of cyanogemod since early in 11. Jumped to temasek build due to the official not being available.
Can anyone tell me if i am missing a step or maybe missing some kind of fix? Ive searched the threads up and down to no avail.
Any help would be greatly appreciated! thanks in advance.
incall UI CM12
Dear all,
I am facing a little bug in Dialing app, the contact photo doesn't appear while I am in calling screen, While the photo is exist in contact app.
I am on 19/01/2015 nightly hlte. I need some help to fix this.
I appreciate your attention.
Thanks
Audio problem
Since flashing cm12 for hlte (using my sm-n9005) I have had no audio output what so ever, it dosen't seem to matter what I flash now audio is non functional, tried downgrading to cm11 again but no luck, running the nightly builds of cm12 hoping to find some way to fix sound.
Cm11 hlte Links Broken/deleted ? Can't Download Any ?
HELP HELP HELP nightlies for CM 11 have been deleted, disabled or are broken on the main download page of Cyanogenmod. I always get "404 not found" or "Traceback" errors. I do not want to be forced to use CM 12 as I much prefer CM 11 right now. If possible can some one please upload the last/latest CM 11 nightly, (2015/01/05), or if some one can direct me to a link were I can download it. PLEASE any help is appreciated.
Thank You
Kind Regards,
Using the latest nightly, still no sound at all
Still no matter what I do or flash since I flashed cyanogenmod 12 I can't get audio to work on anything, no other roms fix it, and nothing I have tried helps.
I have flashed stock, I have wiped data, I have repartitioned to see if it was keeping any kind of bad data, I have no idea what else to try, heres more logcat
I am hoping someone can see something I am missing.
lilfenfen said:
Still no matter what I do or flash since I flashed cyanogenmod 12 I can't get audio to work on anything, no other roms fix it, and nothing I have tried helps.
I have flashed stock, I have wiped data, I have repartitioned to see if it was keeping any kind of bad data, I have no idea what else to try, heres more logcat
I am hoping someone can see something I am missing.
Click to expand...
Click to collapse
Maybe it's a hardware problem.
The phone has never even so much as been bumped so I don't really think is hardware. Flashing a ROM update shouldn't be able to damage anything like that.
/jenkins/99147/cm-12-20150127-NIGHTLY-hlte.zip: unavailable
selecting the download link results in either:
1) error 404: not found
2) being re-directed to cyanogenmod installer, not supported by my Note3 (hlte - sm-n9005)
Can anyone help?
Hello
can anyone help me please ? I think I am the only one who cant move his apps to the external SD card ? because I looked everywhere and couldn't find the fix for it, O got
an error when I try to move any app "couldn't move app not enough storage space" while I got 50GB free on my external and even I changed the SD card with no luck.
thanks
Hi,
since i am on the latest cm12 nightlies for a few weeks, my Mobile-Data connection does not disconnect, when i connect to a random Wifi-network, as you can see in the image below.
If i manually disconnect the Mobile-Data, i am immediately connected to Wifi without any problem.
The switch "avoid bad internet connections" is off, also the "agressive handover from wifi to mobile data" in the developer options.
[EDIT / solved] found out this was a bug in the firewall
Self Reboot
From last few nightlies I'm getting random reboot, does it happens to someone else? How can help to investigate on? Syslog? If yes what should I search to be posted?
More of them happen while I'm on Whatsapp, once accours while in GCalendar, other totaly itself while in standby...
Thank you
SM-N9005, CM12 20150206, TWRP 2.4.8.0
SIM card Problem
Hey guys,
I'm a beginner here but i need to explain this to somewhere.
I have a problem with my SIM card. My dad can call me, I can send and receive sms but i can't call anyone and I can't access to internet, to 3G or even H+.
It's like my phone doesn't detect this card. He says I dont have any SIM card therefore it's like if i couldn't recieve any call but i can do it.
I started having this problem with the first nightly like 2 months ago and since then I have this problem.
Note 3 HLTE SM-9005. With CM12 nightly
Any solutions?
Thanks
Do you checked if you tried the right version?
Are you sure to have the 9005 (hlte)?
Which carrier do you have?
have you flashed Stock lollipop including modem before going to Cyanogenmod12?
Ironstrix said:
Do you checked if you tried the right version?
Are you sure to have the 9005 (hlte)?
Which carrier do you have?
have you flashed Stock lollipop including modem before going to Cyanogenmod12?
Click to expand...
Click to collapse
Yes, I always downloaded the same download with CM11. HLTE / SM-9005. Qualcomm.
I've been updating every day but never happens nothing .
Everything works perfectly but only THAT thing works wrong since I switch to CM12.
I'm from Spain and my carrier is Movistar. That doesn't care.
I only tried to flash CM11, nothing more. I don't want to re-flash again a ROM and delete everything in my phone. (Maybe that could be a solution...)
I would backup my data, flash stockrom and see if the issue persist. The only thing you could try before flashing a new rom, is a different kernel.
Arter97 kernel is very stable (http://forum.xda-developers.com/galaxy-note-3/development/arter97-kernel-galaxy-note-3-t3028148)
Maybe its just an issue due to dirty flashing. They say no need for fullwipe, but strange things can happen
2 months without outgoing calls and internet.. i would go crazy ôO
Hello everyone.
This is a
HELP thread
for asking questions regarding custom ROMs and the issues that you might have with them for this device. Before you post, please read the FAQs at the bottom, and then proceed to ask your question.
Note - the members may or may not provide you a step by step solution, and will provide you links, please check those links carefully, and if you still do not understand, ask your question again.
If the community notices real issues (which are different from the usual "Does this work, does this not?" questions), it will be forwarded to the respective ROM thread (or we'll request you to forward).
Help us in keeping the custom ROM threads clean and help the developers to focus on important issues.
Device Specific Information
Codename athene in development circles. Here, we often use G4 and G4 Plus interchangeably with athene. That's why ROM titles have the word ATHENE in them. Don't be confused.
Device names according to manufacturer - XT16xx. The xx in the end changes as per region. For instance the Indian version is XT1643.
For more information regarding the device, and the availability of ROMs, etc, go to this [INDEX] thread.
Yes, the INDEX thread is mine, I'm not self promoting, I'm linking this because the older one has not been updated in a long time, and no amount of messages to moderators seems to have any effect. If you wouldn't mind, please send a message to the moderator to make this the sticky INDEX thread to help Moto G4 Plus users.
Note: this information is out of date.
Common bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use. You can also (although the developer still won't accept bug reports) rename the fingerprints to add more (credits @mason2smart). Also, try this as mentioned by @__Maddy.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings > Display > Display Size) to the default one.
Video playback issues. Please use this thread by @strongst for providing logs and other details. The only OS that doesn't seem to be affected by this is Vanir.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage. Credits @smitharro, here.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
VoLTE issues. Follow the instructions on this thread, if that doesn't help we need logs, or we really can't help.
Mobile data intermittently stops working. See this post.
CyanMod/RR bugs
Camera issues. Update in next build.
CypherOS bugs
Video Recording doesn't work. Use Footej/Cameringo Lite for now.
External SD read error in inbuilt file manager. Use another file manager.
LOGS
(and why we keep asking for it.)
Imagine you make a cake. And you give it to a person, who says he doesn't like it. And then leaves. You have no idea what went wrong with your food, why that person doesn't like it, what that person would see as an improvement in your cake. You eventually go mad as more people keep saying they don't like your cake, and leave without further information.
This is exactly what happens when you state your bug (that the developer cannot easily reproduce) and then leave it at that. The developer cannot figure out what went wrong. So, to find out what could possibly have gone wrong, (s)he requires a log. The log tells the developer what all errors have occurred, and what could be done to possibly fix them.
Logs are also known as logcat (and other types). Find a helpful tutorial on how to take logs here.
Best way to present logs is to either upload the file to a hosting site, or paste the contents on pastebin, or hastebin, and share the link here.
How to report issues hereThe aim of this thread is to become a source for all members to ask questions on issues they face in all ROMs. So report your bug after specifying the ROM, and the build date. For instance, if I am using CyanMod from Silesh.Nair, which he uploaded for use on 21st April 2016, then I start my issue as
CyanMod 20160421
and we'll help you sort out your issues as much as we can, and if we are stumped, the developers will help you out.
Okay, last one, stop.
Solution For Single FP over MM baseband
If anyone don't want to Flash Nougat Soak or Modem, follow this procedure ( I'm using 5 FP over MM baseband )
** Firstly you will need Fresh start **
On fresh start complete setup wizard process, DON'T add security and FP when asked..
After seting up device go to
settings > security
Add your preferable unlocking option,
Now for FP,
Add your 1st FP, it will get successfully enrolled,
And now you have 4 FP left to add..
** Follow common procedure for remaining 4 FP **
Now add next FP ( add one FP only)
Obviously you will get "Enrollment Error" on any next FP..
After every Enrollment Error Close Setting app completely ( Force stop is preferable, or better do reboot)
Now open Setting again and do same...
*** Note ***
Don't add next FP directly without closing Setting app otherwise you will get "GHOST FP"
You will be not able to remove those FP unless getting Fresh Start again...!!
Count how many FP you have added, i haven't tried adding 6th FP, so better to count 5 FP only..
__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
Much appreciated. Please do.
When I disconnect from WiFi after extended use on CM 14 my phone tells me I'm offline. I have to reboot to use network even though it was still connected... On xt1644...
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
__Madddy said:
I have solution for Fingerprint over MM baseband if anyone dont want to update to nougat soak or modem,
Will edit this post with it, let me correct my english... Lol...
Click to expand...
Click to collapse
If you rename each fingerprint after adding then you can add more than one
zeomal said:
Common Custom ROM bugs
Fingerprint enrollment issues. Flash Nougat to resolve this. No, you have to flash, if you don't want to, please do not post bug reports. Follow this guide by @rahulsnair to update your phone to Nougat soak test. We have a soak test because the release version has not yet been captured for us to use.
Camera/Video recording issues. Use the built in camera, NOT Moto Camera (the camera you had on stock ROM) as your camera. You can also use any other recording app (Cameringo, Motorola Camera, Google Camera all work just fine). And yes, Motorola Camera is different from Moto Camera. Camera issues are being sorted out by the CyanogenMod team (and will reflect on all ROMs that are based on CM), and only once those issues are sorted can the developers for this device sort any issues with ATHENE out. Note that for Moto Camera to work, you need to set the DPI (Settings → Display → Display Size) to the default one.
Unable to share images/screenshots from gallery or filemanager. Sort this one out by formatting your internal storage.
Chop-Chop/ Torch issues. Do a reboot. It should work then.
Click to expand...
Click to collapse
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.
zeomal said:
I'm no expert, but to the best of my knowledge, these will be upstream bugs, so devs will have to wait for CyanogenMod team to fix them, before they can implement the fix.
Click to expand...
Click to collapse
In 20161117 It's Work Perfectly
@mason2smart updated my post with long procedure, will try your suggestion and add to my post...?
Sent from my Moto G4 Plus using XDA-Developers mobile app
swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
Click to expand...
Click to collapse
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?
mason2smart said:
If you rename each fingerprint after adding then you can add more than one
Click to expand...
Click to collapse
Tried and had issue that i described in my post "GHOST FP" ...!
For that procedure i described for remaining FP must be followed...?
swarupgolui said:
Hello I'm Using CyanMod 14.1/20161204 And Model Is XT1643, Rom Work Smoothly, Only Found 2 Small Issue...
(1) Can't Change Dialer Colour, Check The Screenshot Link
https://drive.google.com/open?id=0B1MeY85PNSircTZHX29YRFRudFk
https://drive.google.com/open?id=0B1MeY85PNSirNmJkN1pkUURUSms
(2) Can't Switch to 2G Network
https://drive.google.com/open?id=0B1MeY85PNSirZkFCcFJ5U0pwZW8
Thanks.....
Click to expand...
Click to collapse
About your second question: I can't reproduce that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you sure you're on the latest (N) baseband?
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)
smitharro said:
About your second question: I can't reproduce that.
Are you sure you're on the latest (N) baseband?
Click to expand...
Click to collapse
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.
velosa said:
N baseband does not work with custom roms. At least not for me.I installed soak test N and I stopped being able to make calls when I installed the roms. I suppose they only work with the MM baseband.
Click to expand...
Click to collapse
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Sent from my XT1642 using Tapatalk on CyanogenMod 14.1 (dualboot)
Silesh.Nair said:
https://github.com/sileshn/android_frameworks_base/commit/70e87cfd06759768d451a8057522faba3922e415
2g issue, i'll take a look. Maybe some change from me botched it.
Is 2g working on other roms or is it a problem only on CyanMOD?
Click to expand...
Click to collapse
I'm Only Use Cm14.1 , Not Try other roms
smitharro said:
Well then you supposed wrong! Moreover it's a NEED for a proper use of all functions of all 7.1 custom roms!
Click to expand...
Click to collapse
You are right, but I install everything as it should be and even when I restart the device not to the sign of the sim card.I'll try again and see if it's some mistake I made.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link:
https://xiaomi.eu/community/threads/7-9-14.41552/
Latest version for Mi Pad 2 can be downloaded from here https://www.androidfilehost.com/?w=files&flid=213123 (MIUI 9) for global* version or from MIUI http://en.miui.com/download-296.html (MIUI 8) for Chinese version.
*Mi pad 2 doesn't really have global version, .EU version comes with pre-installed google services and removed Chinese bloatware.
This is a bad news for Mi Pad 2 owners because they do not have any solid custom ROM support for their device, which is due to lack of propitiatory Intel Atom's source code. So even if developers tried hard to deliver custom ROM they simply cannot. So unlike Mi Pad 1 even if Xiaomi EoL'd the support in a similar way last week, they can still get custom ROMs and patch support as long as developers delivers them. But for Mi Pad 2 it is simply not possible.
Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me
The reason why Xiaomi.eu has dropped support for Mi tablets can be found here "Sorry guys, we have no more free time to take care of tablets and debug them.. " (https://xiaomi.eu/community/threads/is-the-mi-pad-3-is-still-being-updated.41551/#post-386099).
Furthermore, if you paid attention to what @tank0412 wrote, you would know that Lenovo has a Nougat update scheduled and that opens the door for Android N development for the Atom series. Lastly, if you really want Mi Pad 2 development, I suggest you donate a Mi Pad 2 to @KonstaT over at Modaco (http://www.modaco.com/forums/forum/445-other-devices/) - he's the brain behind all Atom custom rom development.
Palm Trees said:
Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me.
Click to expand...
Click to collapse
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.
udaan said:
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.
Click to expand...
Click to collapse
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues
Palm Trees said:
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues
Click to expand...
Click to collapse
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.
udaan said:
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.
Click to expand...
Click to collapse
I asked you for a link, because I couldn't find any information confirming Xiaomi will stop releasing more updates for Mi Pad 2. Spreading fake news is never good. Mi Pad 2 hasn't been EOL'd. Only by Xiaomi.eu, but not by others.
Livedten actually points out that it doesn't matter if you use Xiaomi.eu, Multirom.me, etc. MIRU mod should be compatible with all of them.
multirom_MIPAD2_7.9.14_v5.1_b10.zip can be found here https://multirom.me/index.php?m=app&a=view&id=11&app=roms
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.
Palm Trees said:
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.
Click to expand...
Click to collapse
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp
Palm Trees said:
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp
Click to expand...
Click to collapse
So do I just flash it over to MIUI9?
udaan said:
So do I just flash it over to MIUI9?
Click to expand...
Click to collapse
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.
Palm Trees said:
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.
Click to expand...
Click to collapse
btw, will they release the full ROM in future like .EU folks?
udaan said:
btw, will they release the full ROM in future like .EU folks?
Click to expand...
Click to collapse
Probably, yeah. But beware, you might have to download the firmware zip many times, if you decide to use the MIUI 9 firmware from multirom.me, always run 'test archive' with e.g. 7zip. If no errors show, you're ready to flash, if errors show, you have to re-download. I think it's because of a server issue. I use Ninja Download Manager to succesfully download the .zip. MIRU mod downloads perfectly, since it's hosted elsewhere.
After a few tests I managed to flash MIUI9 with MIRU Mod. You must flash both multirom_MIPAD2_7.9.14_v5.1_b10.zip + MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip at the same time in order to get it to work.
https://androidfilehost.com/?fid=817550096634797955
is there any working download link for the latest multirom and miru mod package?
cant find it anywhere anymore.
i found a yandex folder "MIUI_9_BACKUP" containing:
MI_mod_08.02.2018_для_MIPAD2_UNIVERSAL.zip with 144.2MB
MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip with 336.2MB
But without any instructions or anything and dont know what to do with it
So... I had the Mi pad 2 laying in my house running on MIUI 9 and one day I got curious and tried to unlock its bootloader.
I didn't remember my password and the recovery phone no. is discontinued now. and I couldn't change it or sign out.
So like an idiot, I factory reset it. And now it's asking for a password for the last mi id.
can anyone help me? Will and edl flash do the work?
THANKS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Changelog :
March security patch(Android-9.00 r34)
Upstream kernel to 4.9.162 use Genom
Use MIUI camera as default
Add QC ril service blobs
Improve stability
Network monitor
Enable WiFi calling
CAF WiFi implemented
Enforced selinux
Fingerprint act like button fix
Live Display fix
More realistic padding
Fix fmradio
Update LOS newer source
And minor changes
LineageOS issue:
You can tell in comments
Instructions :
Download and Use Orangefox latest recovery. (Recommended)
Download the latest build GApps (if needed)
Reboot to recovery
Flash the latest build GApps (if needed)
Reboot
If on setup wizard system ui fc, just bypass it.
Downloads :
LineageOS-16.0-2019-03-01~3.18.136Kernel
LineageOS-16.0-2019-03-14~4.9.162Kernel
Sources :
Device tree :https://github.com/wufixx/android_device_xiaomi_vince
Kernel :https://github.com/Vince-Beast/kernel_xiaomi_msm8953
Vendor :https://github.com/Vince-Beast/vendor_xiaomi
Thanks to :
Vince-Beast Github
rama982
LineageOS
If you like Genom Kernel, stay tune on their channel~GenomKernel Channel
Last update: 2019-03-14
Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?
msssm said:
Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?
Click to expand...
Click to collapse
What are you talking about? This entire forum is for Vince not for whyred. Xiaomi made a big mess with phone names indeed...
But I assume this ROM is for Vince... If not, it should be removed and thread closed.
Sent from my Note 5 / 5 Plus using XDA Labs
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
msssm said:
Hi, this is the first topic about Treble in this forum. Does that mean the Note 5 Plus (vince) is Treble supported but the Note 5 (whyred) not yet?
PS.: here I already found a Treble project for the whyred. So which is the correct master forum for the whyred? This one here is mixing Redmi Note 5 (whyred) with the 5 Plus, while the other is for Redmi Note 5 Pro but also covering the whyred?
Click to expand...
Click to collapse
Anyway, Vince is not treble originally, but thanks to MIUI partition scheme its perfectly treble compatible and most Pie ROMs ARE treble.
Sent from my Note 5 / 5 Plus using XDA Labs
Yes, the Xiaomi Codenames are a bit messy. I understand now that it was a confusion about my Redmi Note 5 global, which actually is a whyred and not a vince, as vince is only Redmi Note 5 and 5 Plus (this forum) but not the Redmi Note 5 global. The Redmi Note 5 glbal actually is equal to the Redmi Note 5 Pro (whyred). This was not clear from all the Codename threads from Xiaomi forums. Please correct if I'm wrong.
Beside that, both the whyred and the evince seem to have Treble projects meanwhile, while there are still native custom roms maintained. Treble for me is a big step for the future not having custom roms per device but GSI only, with Treble /vendor projects per device, mostly stripped from the stock images. But as far as there is a native rom maintained I would rather go for that. All the Treble still sounds under development and inofficial. Or would you say the opposite?
Treble is indeed something positive. But its not the panacea you think.
MIUI is not treble but uses a partition scheme that can be converted to treble if you flash a vendor on it. This is what most pie ROMs do. Of course, you can have an A only treble support, no A/B.
Unfortunately, a GSI does not work out of the box most of the times. So its always a SGSI (semi-SGI). Hopes to flash any SGI and having it work perfectly are very slim.
Treble does not offer you a free pass to try any ROM you like, just a simpler way for manufacturers to implement android on their phones.
Sent from my Note 5 / 5 Plus using XDA Labs
been using for a week. no problem so far. great rom
very nice rom for me but i have a small bug. when it comes to screen fit. i mean the edge of the screen is curve but the layout was simply straight. not a big deal but nice rom!
Great ROM, thanks dev!
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
use orangefox recovery
niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
Use orangefox and clean flash
JR Bautista said:
use orangefox recovery
Click to expand...
Click to collapse
I am using Orange fox.
niels_kievits said:
I am using Orange fox.
Click to expand...
Click to collapse
I don't wipe the vendor. working perfectly for me
niels_kievits said:
I clean flashed this rom and latest GAPPS and once outside the house, the Phone apk seems to keep force-closing and eventually makes the phone reboot to recovery.
Does anyone know a way to combat this? I tried clearing the apps data but the same thing keep happening.
Click to expand...
Click to collapse
Same here. It seems to be a common problem of all ROMs using mdeejay device trees. Only for certain vince versions tho. The Only ROM that works for me is Pixel Experience CAF Version. I hope this will get fixed at some point. I really like Lineage! Sadly reboot of the phone happens within maybe half a minute after first boot, so taking logs is impossible.
Does it charges the battery to 100%?
Djeypi said:
Does it charges the battery to 100%?
Click to expand...
Click to collapse
Yes it does.
If your battery does not charge to 100%, it's a known defect and you should SEARCH xda forums for the solution. There is one.
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
Yes it does.
If your battery does not charge to 100%, it's a known defect and you should SEARCH xda forums for the solution. There is one.
Click to expand...
Click to collapse
I already tried cleaning battery stats, calibration and even unplugged the battery and fingerprint sensor.
Still charges to 82%. If I recharge it in recovery mode, only then, it reaches 100%.
When I Flash a MIUI rom, it functions normally.
Thanks for the reply and for helping!
Djeypi said:
I already tried cleaning battery stats, calibration and even unplugged the battery and fingerprint sensor.
Still charges to 82%. If I recharge it in recovery mode, only then, it reaches 100%.
When I Flash a MIUI rom, it functions normally.
Thanks for the reply and for helping!
Click to expand...
Click to collapse
1. Open the back cover of your phone carefully (/watch?v=TuK5LYgPuKA)
2. Unplug your battery for about 5 - 10 mins
3. Re-plug the battery and re-attach back cover
4. Test if it will charge to 100%
yirmex said:
1. Open the back cover of your phone carefully (/watch?v=TuK5LYgPuKA)
2. Unplug your battery for about 5 - 10 mins
3. Re-plug the battery and re-attach back cover
4. Test if it will charge to 100%
Click to expand...
Click to collapse
Yes... I've done that twice... Waited 15 minutes the first time, 30minutes on the second time. The problem persists.
I have just flashed this ROM.
Charged to 100%.
Will be with it for a few days... Will Tell how it is then!
Thanks for helping!
TMooV said:
Same here. It seems to be a common problem of all ROMs using mdeejay device trees. Only for certain vince versions tho. The Only ROM that works for me is Pixel Experience CAF Version. I hope this will get fixed at some point. I really like Lineage! Sadly reboot of the phone happens within maybe half a minute after first boot, so taking logs is impossible.
Click to expand...
Click to collapse
I found the fix (well, workaround) for this, at least for me: If you disable the "Enhanced 4G LTE mode" in Settings > Network & Internet > Mobile Network, it works just fine without losing 4g/lte connectivity speeds (as far as I can tell now).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nokia 6.1 (2018)/6.1 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Nokia 6.1 (2018)/6.1 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Nokia 6.1 (2018)
PL2 - Official builds
PL2 - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
Nokia 6.1 Plus
DRG - Official builds
DRG - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_nokia_sdm660
Is this rom based on Android 13?
ardwivedi16 said:
Is this rom based on Android 13?
Click to expand...
Click to collapse
yes
very excited waiting
worked my phone, yesterday i tried clean flash but not boot, and today i tried update with sideload and worked
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
kazekiri said:
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
Click to expand...
Click to collapse
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
backspace123// said:
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
Click to expand...
Click to collapse
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
kazekiri said:
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
Click to expand...
Click to collapse
on my device worked, i tried update using lineageos19.1 official
schwedenespresso said:
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Click to expand...
Click to collapse
Hello, regarding the camera, it is quite likely that it is the kernel as such, in fact, in previous versions, LOS 18.1, 17.1, the flash worked from the camera application, but now it does not work, at the time it was published Official LineageOS for this device, the flash has never worked correctly as such (other applications were not able to take the picture with the flash on the camera due to failure in its execution) as if it did with the manufacturer's version, it is possible that the manufacturer has kept some hidden details at the code level or that the driver has not been fully released on the devices so that the developers themselves have difficulties to achieve a 100% functional version (without errors so to speak), the only solution to this problem is install a custom kernel, it seems some users with knowledge in programming found a way to solve the problem with the flash in the camera + the zoom failure as such, I have not found out if the developer would have adapted the kernel for the versions of android 13 for this specific device than if it is available for versions prior to the unofficial LOS 20 available.
Best regards
Hello everyone, for all those who have problems with their recovery (nothing is displayed, but it feels like it works internally), I will leave you a post that I made months ago, the recovery options should be the same for the latest versions, hopefully It is useful for you, remember that the installation process of LineageOS can last more than 4 minutes.
LineageOS recovery instructions for use build 2022-08-30 -When starting the recovery, 4 options will be presented, which are these.
Reboot system now.
Apply update
2.1)For this step I recommend selecting the first option with the power button of the device, which is by ADB
3)Factory Reset
3.1)Format data/factory reset
4. Advance
4.1) advanced options, with this image it will serve to guide you in how many clicks you have to press to access the option with the power button of the device to access one of these options.
Best regards
backspace123// said:
on my device worked, i tried update using lineageos19.1 official
View attachment 5763487
Click to expand...
Click to collapse
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
kazekiri said:
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
Click to expand...
Click to collapse
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
npjohnson said:
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
Click to expand...
Click to collapse
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
kazekiri said:
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
Click to expand...
Click to collapse
Figured it out - next build should work. give it like, 4 hours.
npjohnson said:
Figured it out - next build should work. give it like, 4 hours.
Click to expand...
Click to collapse
Yep. Whatever you did worked! Booted on my DRG. Haven't tested everything yet, but so far seems great.
Thanks! You are one dedicated dev!
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
I have the same camera issue, any solution for DRG?
kazekiri said:
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
Click to expand...
Click to collapse
Weird, works on PL2. got logs?