Develop Bugs

[Q] Battery drainage because of mobile data

Hi Guys,
I am new to this forum and got a small question. My girlfriend has an Oppo Find 7a. You guys probably know that the stock ROM is ColorOS. In my opinion it's crappy as hell, lots of bugs and issues, so I decided to flash Dirty Unicorns 5.02 on it. I did that yesterday and all is working fine so far, except that the battery drained from 100% to 64% last night (in 8 hours). See the photos attached. According to the photos it seems clear that the issue is the mobile data usage. I've checked the settings and it seems mobile data loses connection, connects again and loses connection everytime. Probably this is the cause of the battery drainage. Somewhere on this forum I read something about flashing Alucard 1.1a kernel on it to fix this issue. I want to try this in the evening, but does anyone know the correct type of this kernel as I found different alucard 1.1a download links?

Can someone please help me out with this? Yesterday evening I just flashed the Alucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?

GRDD_ said:
Can someone please help me out with this? Yesterday evening I just flashed the Elucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?
Click to expand...
Click to collapse
before flashing DU did you flash proper modem and trustzone firmware?

treacherous_hawk said:
before flashing DU did you flash proper modem and trustzone firmware?
Click to expand...
Click to collapse
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?

GRDD_ said:
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?
Click to expand...
Click to collapse
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
https://plus.google.com/+BoskoTrkulja/posts/CENAM1a7Zob
you can get the modem and tz firmware here:
https://www.androidfilehost.com/?fid=95916177934529695

Sir, have my thanks! You are my hero of today. Thanks a bunch. I'm going to try this

treacherous_hawk said:
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
you can get the modem and tz firmware here:
Click to expand...
Click to collapse
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?

GRDD_ said:
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?
Click to expand...
Click to collapse
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
Alright, I will do it in that order then. Thanks again. Much appreciated.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?

GRDD_ said:
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?
Click to expand...
Click to collapse
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.

treacherous_hawk said:
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.
Click to expand...
Click to collapse
I will give the battery thing some time to settle down then. About the data connection issue; This was not an issue on coloros, but I will check apn and try another sim. Thanks again!

I've changed the APN settings, as they stood on some kind of roaming setting. It's now been set to live.vodafone and seems to be functioning better already . If I still run into some issues I'll let it know. Thanks for helping me out

GPS is not working after flashing Lineage 14.1

GPS is not working after flashing Lineage 14.1
I tried (GPS Status) but still says "Looking for GPS location..." and nothing happened.
Also, I wiped cache and dalvik many times.
Device : HTC One M8

Now, I tried "Venom Roms" and the same issue nothing fixed!
Is some file missing when I rooted or Rom?
Any help will be appreciated..

GPS is working now
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

mhb3000 said:
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?

Gara91 said:
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?
Click to expand...
Click to collapse
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.

GeoFisher said:
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.
Click to expand...
Click to collapse
I do have a gps lock now on the lineage os...i just followed the steps from guy above... My mistake was when i install a lineage os i allways do the bootloder unlock, then immediately i flash twrp and than a full phone wipe (system, data, cache, internal memory). This time i relocked the bootloader, installed the ruu, then unlocked the bootloder again, after that i let the stock system to fully boot... I go through the first set up and after all that i flashed the twrp, and installed the lineage os but this time without a system wipe, just data, cache and internal memory (internal memory is not a must, but i love when i install a new rom to get totally fresh and clean install).
I don't have a clue why this works but it worked for me and maybe it can work for you...
My HTC M8 is European model but it doesn't matter, because if you do all this step with the stock ruu (Verizon ruu in your case) the files for the gps will be there... Good luck..
Edit: I am using the Navigon Europe and my gps locks instantly like on the stock android 6.0.

Hello, I've got an almost the same issue with GPS, it seems, the "assisted" function isn't work correctly. When I switch on the GPS, I have to wait 3-5 minutes to start working. After a few minutes there is no any issue with that, but a little bit annoying if I want to navigate from an unknown place and I have to drive "blind" for 5 minutes. I use the latest nightly build on my M8. I've started use the previous unofficial build, but currently I always upgrade to the latest nightly. Any idea?
Thanks in advance!

This fixed the GPS for me.
I'm was on LOS nightly 14.1-20170413 when i removed # in gps.conf. (use total commander app)
When phone start bootloop, i use the right quickpulldown to GPS and only 1 touch to disable. In current nightly, it's 2 touchs to disable GPS so have to be even faster before the bootloop or otherwise tap the airplane mode instead to stop bootloop. Also make sure you have screen lock = off or swipe.
now restore # in gps.conf and GPS is working.
/system/blobs/
This might help.
https://www.reddit.com/r/LineageOS/comments/5z8zju/gps_not_great_on_htc_m8/

Hi,
I recently went into the same issue with GPS on my m8. It was not working at all. I spent couple of days trying to flash different stock roms, RUU, factory reset, editting gps.conf file, even the solution described here: https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999. Nothing helped. No matter what I did, I couldn't get GPS working. I mean there was no signal at all.
Finally I wiped MISC partition and it solved the issue. It turned out that some wrong data was held on misc partition that stopped GPS from functioning correctly. One important notice - I was on stock firmware when I wiped MISC partition. Stock firmware managed to reinitialize it properly. If you are on custom FW, I am not sure it will work. You can try and if it will not work, it mean you should be on stock FW.
And just few commands for those who don't know how to do it:
With fastboot:
Code:
fastboot erase misc
If the above gives you "not allowed" error you can do it through adb:
Code:
su -
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Obviously you should be rooted or you can do the same through TWRP shell.
Hope it will help someone.

sim card not working oreo/noughat

hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue

Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.

I will try again

Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying

Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.

any update in the same boat

I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it

Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build

UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.

Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again

This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.

hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too

SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger

parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.

Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!

​
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?

NoXXX said:
​I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)

Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo

Phone stops/crashes/restarts when enabling MTP

So I just tried out some pie roms earlier and when I finally settled on a specific rom, i migrated my files, fixed some settings etc. And when I decided that I was done, I just wanted to transfer some backup files to and from my phone in case I'd need to revert to my prior setup. Weirdly enough, when I pressed the file transfer option on my phone, it would stop or even restart to the bootloader or recovery then I'd have to boot my phone again. I tried it a couple more times and I even lost some data. I then decided to restore a nandroid backup of my oreo rom thinking it was a rom problem but the data partition couldn't be read in bluspark twrp. So, I just did another clean flash of the pie rom (format data, decrypted and all that) and same thing except for the data loss part. Im pretty sure nothing went wrong with flashing as everything works fine on the actual rom but as soon as I select the MTP option, the phone just restarts. Now Im on the said pie rom and everything's working fine but I can't attempt to transfer any files as I'll just run into the same problem. Any help would be appreciated. Thanks!

XT1789-04 Restore Baseband

I am trying to revive my old z2 force t-mo edition. It basically crashed after an OTA and lost baseband and IMEI and i threw in in a drawer for months.
I tried flashing newest firmware-nothing, i tried unlocking bootloader and flashing second new firmware-nothing. The device does turn on--just no data, no wifi etc. I'm not too familiar with blankflashing, is this something i can even do with a device that turns on? Will that even work? Moto assistant says they are "unable to verify a match" when i pick repair device and select XT1789-04. Does anyone else have anything else to try? I have not rooted, have not installed pie firmware or anything. Long story short, im now in need of a working phone so i just want to get this working again!

Same boat as you! Have tried everything on here. What's a blank flash?

Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops

Dany XP said:
Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops
Click to expand...
Click to collapse
Had the same issue with baseband unknown/no wifi/no LTE, the 27.1.7 flashall fixed it for me