[Q&A] [CM ROM [hlte/universal] OFFICIAL CyanogenMod Builds (Nightlies) Maintainer Th - Galaxy Note 3 Q&A, Help & Troubleshooting

[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

Related

[Q&A] AOSP for Galaxy S4 LTE-A : CM, AOSB, Carbon, LS, MoKee, SlimKat, Temasek, crDr

[Q&A] AOSP for Galaxy S4 LTE-A : CM, AOSB, Carbon, LS, MoKee, SlimKat, Temasek, crDr
Q&A for AOSP for Galaxy S4 LTE-A : CM, AOSB, Carbon, LS, MoKee, SlimKat, Temasek, crDroid
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 AOSP for Galaxy S4 LTE-A : CM, AOSB, Carbon, LS, MoKee, SlimKat, Temasek, crDroid. 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!
mezo91 said:
any help?
Click to expand...
Click to collapse
What i did was in this order:
0. wiped everything on my i9506 with TWRP (not needed) x3 factory reset is enough
1. DeHAWK AutoRoot. for GT-I9506 4.4.2 - XXUCNG3. you can find the link in his post with ODIN 3.07 inc. in the link. ( DeHAWK http://forum.xda-developers.com/showthread.php?t=2597058 )
2. TWRP 2.8.0.0 touch recovery with ODIN 3.09 ( http://forum.xda-developers.com/gal...recovery-twrp-2-8-0-0-touch-recovery-t2887037 )
3. download all needed zips to SDCARD(ROM, kernel and Gapps and PATCH for I9506) ROM Kernel and PATCH can be found on arter97 website ( his post http://forum.xda-developers.com/showthread.php?t=2691639 ) I use Gapps from ( http://forum.xda-developers.com/showthread.php?t=2397942 ) NANO MODULAR PACKAGE
4. the use TWRP and install ( add zip from card in this order ROM, KERNEL, GAPPS, AND PATCH ) and reboot
My only problem is BT keeps POP with warnings now and then and 4 to 5 times on reboot
Cashano
@Cashano, so you are on dehawks pre-rooted rom?
Arter97 patch & kernel is for arter97's roms, so not surprised at your combination is not working.
Those are intended to use with arter97 roms, good luck at it's working so far on your case.
You should try that dehawk without arter97 stuff, or try arter97's roms with it.
I habe LiquidSmooth running with 3.1 Kernel and geht sometimes UI Fc's.. tried factory wipe and flashed everything again, but no luck. Maybe a Rom Issue? Will try to change to Temasek Rom with the 3.2 Kernel..
Sent from my GT-I9506 using XDA Free mobile app
kernel use
@arter97 I have made a port of Paranoid android 4.4.4 that uses your kernel and I want to know if it's okay if I release it with a link to your thread for kernel download?
Suggestion doubletap2wake & swipe2wake to the kernel
Hey Arter97, I'm using Temasek rom with your arter97 kernel for my Galaxy S4 LTE-A. It works perfectly and it's awesome.
Just my suggestion, it would be best if it is possible to add doubletap2wake & swipe2wake into your kernel.
It's alright, if it is not possible.
Thanks! Keep up the great work! =)
Hello,
Your work for this phone is amazing. Temasek + your kernel are the perfect team. Only one issue: can't be flashoolic anymore... Don't leave us, please, TW is so boring. Thanks again
Rom Installation
Hello Respected Developer,
I have few questions about installation on my shv-e330s.
2. Put ROM, kernel and Gapps on you SD card
I want to to install CM 11 which one i download so i don't have any restart/reboot issues.
4. Flash ROM, kernel and Gapps in order
Where to get kernal for CM?
Kernel is not included! Make sure to download and install kernel specifically made for CyanogenMod.
Where i can get this one?
5. If you're an i9506 user, flash the fix file from here
Do i need to do this i have shv-e330s.
Thank you And Regards.
Zeedesign said:
Hello Respected Developer,
I have few questions about installation on my shv-e330s.
2. Put ROM, kernel and Gapps on you SD card
I want to to install CM 11 which one i download so i don't have any restart/reboot issues.
4. Flash ROM, kernel and Gapps in order
Where to get kernal for CM?
Kernel is not included! Make sure to download and install kernel specifically made for CyanogenMod.
Where i can get this one?
5. If you're an i9506 user, flash the fix file from here
Do i need to do this i have shv-e330s.
Thank you And Regards.
Click to expand...
Click to collapse
2. Pretty much any.
4. http://www.arter97.com/s4_cm.htm
/* Downloads */
5. No
Boot Loop
HI All,
My phone is e330k 4.4.2 with CWM, wipe data, wipe cache, wipe davik, install zip (cm, kernel), restart and got boot loop at cm12 logo.
Anyone has the same problem?
Quy
Hey guys,
How has your performance been on these roms? I've been running the latest Temasek-build there and it does seem bit lower than expected. Compared to the latest stock OTA NJ-build, the Temasek v162 actually decreases my AnTuTu points from 42K to 39K. Also battery life dropped by approx 25% (previously I had screen on times of 4+h, now 3h). I'm still following how it turns out in the long run but have you had better or worse battery and overall performance with these roms compared to stock?
Also is arter97 recovery and kernel and patch all mandatory with all of these AOSP roms provided here?
Finally would like to point huge thank you to arter97 - without you we would have barely any rom options for our phone. Hopefully you are able and willing to keep it up and us updated from time to time. Thank you!
P.S. Why is this force to Q/A section in use. Even though I mainly read the forums doesn't mean I'm noob enough not to be able to post serious comments or anything else than questions. Just wondering, lol.
enkku said:
Hey guys,
How has your performance been on these roms? I've been running the latest Temasek-build there and it does seem bit lower than expected. Compared to the latest stock OTA NJ-build, the Temasek v162 actually decreases my AnTuTu points from 42K to 39K. Also battery life dropped by approx 25% (previously I had screen on times of 4+h, now 3h). I'm still following how it turns out in the long run but have you had better or worse battery and overall performance with these roms compared to stock?
Also is arter97 recovery and kernel and patch all mandatory with all of these AOSP roms provided here?
Finally would like to point huge thank you to arter97 - without you we would have barely any rom options for our phone. Hopefully you are able and willing to keep it up and us updated from time to time. Thank you!
P.S. Why is this force to Q/A section in use. Even though I mainly read the forums doesn't mean I'm noob enough not to be able to post serious comments or anything else than questions. Just wondering, lol.
Click to expand...
Click to collapse
Performance: I have slightly better score on antutu on CM than TW.
Check what extra features you use.
AnTuTu scores are not prefect measurements for Rom speed& functionality.
Battery consumption is less on CM, on road using only 3G and Bluetooth on car for watching movies etc i have always nearly 4h SOT, at home on WiFi always over 6h SOT, combined use gives around 5h SOT.
Kernel + patch = mandatory
Recovery with 4.4 bootloader suggested, and nearly mandatory if going to LP.
Under 10 posts and here you are.
{
"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"
}
Thanks for the quick and informative reply!
Your stats sound pretty good to me and something I definitely want to achieve. And as you said too, performance is not the problem here anyways probably, but the battery is pretty important. I'm running no background apps, playing few online games and running with 3g most of the SOT, though the connection is sometimes pretty bad which may cause extra battery load.
Anyways I would gladly hear which CM version you're successfully using?
The 'official' CM builds for i9506 seem to have some reboot issues according to the comments, and that sure is something I'd like to avoid (I got enough of that on my more flashoholic days ). And as I just want a pure CM experience I got no need for the custom versions like Temaseks (which is great otherwise and I used it on my S3) for now atleast.
So please, if you don't mind, I would gladly hear more about your CM version and setup you used to get those values.
Thank you.
@enkku, I'm on Temasek CM11 v162 (by arter97) now, same stats when was on "stock"CM by arter97.
Biggest changes are just TRDS ON and ThyrusHOLO KITKAT black/dark theme installed, all automatic synchronizing disabled.
Small tweaking on brightness values, getting brightness lower.
Basically I have 24/7 WiFi on, automatic open WiFi polling is off. Too lazy to switch it off coz it's not draining my battery, thanks to arter97's brilliant work on kernel. So my WiFi connects only to my home WiFi, nowhere else even it's activated all the time.
Good morning,
Same config here with gapps frozen and apps always killed after use. Brightness 30%, 9 h LTE and wifi/day : 6-7 h SOT.
Hi, is it possible to make the 4k camera from note4 work with aosb 1.3.7? thank you so much!:good:
@ode_ good points you made there, thanks for your reply.
I just did a full day run and my battery barely lasted the whole day: I only got 2h 40min screen on time? What could possibly be wrong? I disables all syncs, no wlan or location active at any point, brightness at lowest and 3g on only when I need it. Still I get battery life that's only a third of you guys? I don't run any background apps, only few messenger apps, most of them hibernated with greenify.
I added screenshots of my battery life and BBS stats as attachment. As you can see, my idle/deep sleep battery consumption is normal, but whenever I start using my phone the battery drops really fast. When using my phone I mostly chat, play some online games really briefly (3-20min at once) or just browse the web.
Would gladly hear some ideas to make me battery life better/normal.
Edit: Android system seems to have used a little battery this time, but it still only shows 30min cpu time amd 3min keep awake so can't be solely it causing the extra drain.
Thank you.
@enkku, go and check:
Settings-performance-profile balanced
Enabled per app profiles
Settings-performance-processor governor arteractive
No multicore powersaving
Settings-performance-io scheduler fiops
And even those shows currently right values change one time to some other and go back using screen left upper corner arrow.
I'm betting at you have profile performance now running.
Plus you run your software's on white theme, that eats battery really fast on Amoled screen. Invest on thyrusholo dark and switch TRDS on.
Edit: don't forget to switch on adaptive backlight.
@ode_ thanks again, great suggestions!
Anyways I think most of those are the default values, and I haven't touched them, but I still re-activated them all as you suggested (and no, didn't have any performance settings activated, I thought so too at the beginnkng coz the battery drain was so fast while using the phone). Also turned on adaptive backlight, got rid of my lollipop (white) theme and disabled dynamic status bar. Also hibernated fb messenger and disables my single zooper widget. But even after all the things you suggested and I listed here, there seems to be absolutely no difference. I'm amazed how can I have this poor battery life with absolutely nothing running in background: even compared to stock Samsung TW with billion bloatware like step counter running all the time, I have a bit worse battery life I think.
What could I do more to try solve this issue? Try looking into battery drain with some other software? Installing another rom? Going back to stock? Going back to shop to whine that my battery's bad? Lol, just kidding, but seriously, this phone is literally one and half week old now and yet I have so poor battery times? What am I doing wrong?
Again, todays data as attachments. Also counted that while playing for example, I lose 1% of battery every 1min 30sec. While browsing, this number is a bit better, more like 2min-2.5min per %.
Thanks guys, you're really providing me great help and support here!
@enkku, wipe cache and Dalvik cache, copy your pictures out from phone and back of you need them, just to make sure at there is no broken files and some looping on media scan/file system.
Cache wiping helps on some cases, I had once similar type battery drain and it ended just by wiping caches.

[HELP] thread for custom ROMs

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 here​The 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.

[ROM] Custom ROM for MTK6580 Smartwatch (X5 Air / LEM5 Pro)

There has been quite a bit of development on the full smartwatch front recently; notably the OpenWatch project that is in full swing and pretty much covered all the main manufactures and variants that are available.
Hopefully a new OS will be available shortly; however in the meantime Id like to offer this ported Resurrection Remix to the community as I have been asked a number of times to release it for testing.
I have been using this for about a fortnight now and so far am very pleased with the results. Battery life has been tripled with hibernation, and root access provides more potential.
Please note that the UI has not been optimized for round screens however anything awkward can be done via PC and a screen cast app. Im using Vysor.
Installation:
Install .zip via TWPR in the usual fashion. Factory reset wipe is recommended.
As always please process a full backup of your existing software inc. all partitions you have available (NVRAM etc) before flashing so you have a safe return point.
Details:
Resurrection Remix ROM 5.5.9 for MTK6580
Android Version: 5.1.1
Kernel: 3.10.72+
Ported for: Finox X5 AIR / LEMFO LEM5 Pro
Known Bugs:
Bluetooth - file transferring is 50/50
Display not optimised
No clock engine - please use Ricktops Universal Launcher to regain this function.
Palm brightness - use home button to turn screen on and off.
Suggestions:
Please allow 5+ minutes for OS for intial loading after flash.
Kernel editor - reduce max CPU frequency to 600Mhz
Install Xposed framework for Lollipop 5.1.1
Greenify (and enable framework in Xposed)
Change DPI to 200 - play around with this to see what suits you best
Enable expanded desktop for all apps
Use Battery Saving Mode and Airplane Mode when possible.
Once you have set up everything do a further backup to save you setting everything up again.
All credits to the Resurrection Team for their ROM. I have not altered any aspect of the original, simply ported this over to my device.
This should work on any 5.1.1 smartwatch if properly ported using your stock files. Please see ported folder in download link to see which file I have corrected. Replacing these files with your own stock resources should work.
Download Link: http://bit.ly/2vjWHue
{
"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"
}
@migueldbr
Here is the ported Resurrection ROM for the Thor Pro - I honestly have no idea if this will work as I cant test it, but in theory it should?
You mentioned that you have a full backup already, I would suggest copying the BACKUP folder from the TWRP folder on your SD card to your PC so you can transfer it back in the event you need to do a full wipe if this bootloops. If you are using SPFT then chances are you will return back to stock recovery unless you modify the stock fw. From experience, its easier to just do a fresh flash when these thing dont work.
If you see the RR logo, wait a good 5-10 minutes for it to load. If it doesnt, chances are the port failed. In which case Im sorry.
Id also grab the Universal Launcher from an apk mirror so you can get the watch functions back and also using Vysor to set it up makes it much easier. Suggestions are in post above.
With regards to the connect phone app, it should work - Im using watchdroid to ping notifications over and it works with no issues.
Good luck! And let us know how you get on. Fortune favours the bold.
Download Link:
DELETED
NB. Stock ROM was version Thor_Pro_XY_C5_X300_v1.5_20180619
CerebralFlex said:
@migueldbr
Here is the ported Resurrection ROM for the Thor Pro - I honestly have no idea if this will work as I cant test it, but in theory it should?
You mentioned that you have a full backup already, I would suggest copying the BACKUP folder from the TWRP folder on your SD card to your PC so you can transfer it back in the event you need to do a full wipe if this bootloops. If you are using SPFT then chances are you will return back to stock recovery unless you modify the stock fw. From experience, its easier to just do a fresh flash when these thing dont work.
If you see the RR logo, wait a good 5-10 minutes for it to load. If it doesnt, chances are the port failed. In which case Im sorry.
Id also grab the Universal Launcher from an apk mirror so you can get the watch functions back and also using Vysor to set it up makes it much easier. Suggestions are in post above.
With regards to the connect phone app, it should work - Im using watchdroid to ping notifications over and it works with no issues.
Good luck! And let us know how you get on. Fortune favours the bold.
Download Link:
http://bit.ly/2p1uCnN
NB. Stock ROM was version Thor_Pro_XY_C5_X300_v1.5_20180619
Click to expand...
Click to collapse
Awesome man, thanks a lot! I will test it tomorrow because it is 23:30 here in Portugal so its late. But tomorrow once I get back from work I will test it. Btw does it include the "connect phone" app to be able to use with wiiwatch? Or do I have to install later as system app or something?
migueldbr said:
Awesome man, thanks a lot! I will test it tomorrow because it is 23:30 here in Portugal so its late. But tomorrow once I get back from work I will test it. Btw does it include the "connect phone" app to be able to use with wiiwatch? Or do I have to install later as system app or something?
Click to expand...
Click to collapse
I hope it works for you; would open it up for more people to hopefully improve it.
Im sorry Im not familiar with connect phone or wiiwatch? If its a app that came with the watch you could maybe look for it on the manufactors website? However WiiWatch - Watch Assistant is available on the app store (or an apk mirror) if this is what you mean? Could try that.
Keep us posted.
CerebralFlex said:
I hope it works for you; would open it up for more people to hopefully improve it.
Im sorry Im not familiar with connect phone or wiiwatch? If its a app that came with the watch you could maybe look for it on the manufactors website? However WiiWatch - Watch Assistant is available on the app store (or an apk mirror) if this is what you mean? Could try that.
Keep us posted.
Click to expand...
Click to collapse
The connect phone app comes pre installed on the stock rom and that's what makes it able for the wiiwatch app to find the phone...and I have no other alternative because I have an iPhone:/. Anyway I will try the rom!
It didn't work...some errors like "error 7" and some "symlinks missing". I think I am going to sell it because it simply does not work properly with the iphone, it causes major battery drain on my phone because of the wiiwatch app to connect=/
But thanks a lot for your help!
migueldbr said:
It didn't work...some errors like "error 7" and some "symlinks missing". I think I am going to sell it because it simply does not work properly with the iphone, it causes major battery drain on my phone because of the wiiwatch app to connect=/
But thanks a lot for your help!
Click to expand...
Click to collapse
Damn error 7 - i removed the asserts from the updater script - so it could be a number of other things.
Im sorry it didnt work mate. I would be up for trouble shooting it with you but would be so hard pin pointing the problem without a device to test it on here. Best just wait for OpenWatch to be released, or as you said sell it. I wonder what the delivery would be from Portugal to UK? : )
I appreciate you giving it a shot, ill remove the link so no-one else tries.
All the best.
CerebralFlex said:
Damn error 7 - i removed the asserts from the updater script - so it could be a number of other things.
Im sorry it didnt work mate. I would be up for trouble shooting it with you but would be so hard pin pointing the problem without a device to test it on here. Best just wait for OpenWatch to be released, or as you said sell it. I wonder what the delivery would be from Portugal to UK? : )
I appreciate you giving it a shot, ill remove the link so no-one else tries.
All the best.
Click to expand...
Click to collapse
I am now waiting for the battery to run out because I don't know the combination to boot into twrp xD. Also, unlike cellphones, forcing the power button doesn't turn it off, it just keeps rebooting. Thanks a lot for your help. I contacted zeblaze and they said they would look into the issues. First they sent me a firmware to try (which was older than the one you based the rom on, which was the same that came with my watch lol). Zeblaze seems to be very unorganized, even their site does not have firmware available to download...its a shame really, I wish i had bought a lemfo or kingwear!
migueldbr said:
I am now waiting for the battery to run out because I don't know the combination to boot into twrp xD. Also, unlike cellphones, forcing the power button doesn't turn it off, it just keeps rebooting. Thanks a lot for your help. I contacted zeblaze and they said they would look into the issues. First they sent me a firmware to try (which was older than the one you based the rom on, which was the same that came with my watch lol). Zeblaze seems to be very unorganized, even their site does not have firmware available to download...its a shame really, I wish i had bought a lemfo or kingwear!
Click to expand...
Click to collapse
If you want to speed it up remove the backplate and follow the battery ribbon to the motherboard. If you use something pointy but rounded you can just pop the contact up (disconnecting the battery) then push it back on. But you will most likely need to reflash with SPFT unless you have a way of booting into TWRP from power off.
It is ashame they arent more on the ball with updates etc, ive heard this alot with zeblaze. definetely go LEMFO or KW next - ive been told these have a very secure future and support is now officially by the RASC community from what I know.
Yeah that’s bad they don’t want to support the Thor pro is a really good budget device with big screen and outside readable, we still have the original firmware and not updated, yeah I have an IPhone to and the Bluetooth connection is not so good but it works the Bluetooth calling works too good and I have to install an app Volume booster because is so low and for the position of the hardware is really bad this device has potential. I am waiting for my Lemfo LemX
Good work on the port. Im trying to get RR on my Microwear H2 (1gb 16gb) I have a working TWRP recovery. Could you point me in the direction of the port guide you followed for your watch so i can try and port it myself. Thanks
Also, have you managed to port any higher versions of android for your watch? I am aware of the Openwatch project, which brought me to your post.
EDIT: Just read the last few lines of your 1st post. Will have a go as you have suggested. Thanks
CerebralFlex said:
There has been quite a bit of development on the full smartwatch front recently; notably the OpenWatch project that is in full swing and pretty much covered all the main manufactures and variants that are available.
Hopefully a new OS will be available shortly; however in the meantime Id like to offer this ported Resurrection Remix to the community as I have been asked a number of times to release it for testing.
I have been using this for about a fortnight now and so far am very pleased with the results. Battery life has been tripled with hibernation, and root access provides more potential.
Please note that the UI has not been optimized for round screens however anything awkward can be done via PC and a screen cast app. Im using Vysor.
Installation:
Install .zip via TWPR in the usual fashion. Factory reset wipe is recommended.
As always please process a full backup of your existing software inc. all partitions you have available (NVRAM etc) before flashing so you have a safe return point.
Details:
Resurrection Remix ROM 5.5.9 for MTK6580
Android Version: 5.1.1
Kernel: 3.10.72+
Ported for: Finox X5 AIR / LEMFO LEM5 Pro
Known Bugs:
Bluetooth - file transferring is 50/50
Display not optimised
No clock engine - please use Ricktops Universal Launcher to regain this function.
Palm brightness - use home button to turn screen on and off.
Suggestions:
Please allow 5+ minutes for OS for intial loading after flash.
Kernel editor - reduce max CPU frequency to 600Mhz
Install Xposed framework for Lollipop 5.1.1
Greenify (and enable framework in Xposed)
Change DPI to 200 - play around with this to see what suits you best
Enable expanded desktop for all apps
Use Battery Saving Mode and Airplane Mode when possible.
Once you have set up everything do a further backup to save you setting everything up again.
All credits to the Resurrection Team for their ROM. I have not altered any aspect of the original, simply ported this over to my device.
This should work on any 5.1.1 smartwatch if properly ported using your stock files. Please see ported folder in download link to see which file I have corrected. Replacing these files with your own stock resources should work.
Download Link: http://bit.ly/2vjWHue
View attachment 4600459 View attachment 4600460 View attachment 4600461 View attachment 4600462
Click to expand...
Click to collapse
Sir,
Can i requst a custom rom for Mango Galicia phone? i found no custom rom in corner of internet fot this phone.
The device is mtk-6580.
Looks like the link is dead, any chance in re-uploading it ? =E
I just bought this Smartwatch and with an rom as option, it would make my day =)

What is this crDroid mystery build?

TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
{
"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"
}
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?
install telegram and contact dev
Totesnochill said:
TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
View attachment 5552979
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?
Click to expand...
Click to collapse
yeah I know AaronPhilips101, it's on the gprime group on telegram. i don't know if he built something else but yeah it's weird that he didn't create any thread for that
I remember one day he asked me to use my source trees, probably to build this rom. so it should be safe I think.
Well on how to build a rom there is a good starting guide here https://itexpert120.github.io/blog/building-android/
Gabboxl said:
yeah I know AaronPhilips101, it's on the gprime group on telegram. i don't know if he built something else but yeah it's weird that he didn't create any thread for that
I remember one day he asked me to use my source trees, probably to build this rom. so it should be safe I think.
Well on how to build a rom there is a good starting guide here https://itexpert120.github.io/blog/building-android/
Click to expand...
Click to collapse
The Android build how-to article is especially interesting. Thanks a lot for the tips! Just one more question pls - what is that gprime telegram group you've mentioned? Is it public or invite-only?
Totesnochill said:
The Android build how-to article is especially interesting. Thanks a lot for the tips! Just one more question pls - what is that gprime telegram group you've mentioned? Is it public or invite-only?
Click to expand...
Click to collapse
No problem, if you have any questions just ask : )
You can join the group at @grandprimedev. it's a little dead as of now, I think the gprime community had its time already haha ; )
Gabboxl said:
You can join the group at @grandprimedev.
Click to expand...
Click to collapse
Thanks again! I'll check it out.
Gabboxl:
it's a little dead as of now, I think the gprime community had its time already haha ; )
Click to expand...
Click to collapse
Hahah, makes sense. Still, worth checking out. Gprimes were resilient little phones. Mine still stubbornly works no matter how much abuse (and water damage) it has been subjected to over the years. Guess just like the phone, the community around it still refuses to fully die out XD.
Totesnochill said:
TLDR: Found some crDROID build that works flawlessly. Tho couldnt find this rom listed on any credible sources (such as XDA). Naturally suspicious. But do want. Anyone else used this rom or saw any info on it? Details below:
- I've been looking for a LineageOS 17.1 build for my phone, G530FZ Galaxy Grand Prime (or "gprimeltexx") to switch to from LineageOS 18 due to slowdowns and short battery life on newer version.
- Followed >THIS< link on >THAT< XDA thread, which landed me on androidfilehost.com.
- While LOS17.1 rom was downloading, I've decided to use the site search to look for "gprimeltexx".
- This is the result:
Spoiler: Screenshot
View attachment 5552979
- Unexpectedly, the crDroid 7.11 (Android 11) build for g530FZ (highlighted) showed up in the search.
- It is weird, since previously I've searched high and low for crDroid build for g530FZ that is newer than 2018 (xda thread) to no avail.
- Scouring the google and duckduckgo for variations of "crDroid 7.11 grand prime" yielded no results EXCEPT this androidfilehost file. Searching for the highlighted rom filename shows ONLY this androidfilehost link in the results.
- Since my phone was long wiped anyway, I've decided to download and flash this crDroid rom via TWRP.
- Surprisingly, it did flash, and after about 5 min of initialization I was prompted to go through regular Android initial setup (language, etc)
- Even more surprises: despite running Android 11 (which has always been slow on the prehistoric Grand Prime), this crDroid rom runs very fast even with all the fancy animations (which mercilessly lagged the device on lineageos 18)
I am tempted to use this rom as my main phone os. HOWEVER, given that it came from a totally random source and has no info on it on XDA, I am naturally hesitant. Could anyone could clarify the following please:
Does this ROM come from XDA or some other credible sources? I've searched on it myself couldnt find anything, but maybe I've missed something that you know.
Any way to check whether this rom sends/receives sus data?
Developer of the ROM is listed as "AaronPhilips101". Does that ring a bell?
the mere existence of this crDroid rom (and other unofficial versions) indicates it can be built on G530FZ. Are there any tutorials on how to build it from source for this particular device (g530FZ)?
Click to expand...
Click to collapse
Hello there, Sorry for the late reply
1. Yes the rom is completely safe to use and i built it using Gabriel's trees which you can find here https://github.com/Gabboxl/local_manifests
2. I mainly built this for my personal use so that's why I didn't bother creating an XDA thread for it .

[OFFICIAL] LineageOS 20 for the Nokia 6.1 (2018)/6.1 Plus

{
"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?

Categories

Resources