Database Develop

[Q] Help with GPS N7000 with Android Kit Kat

My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.

dexterdroid said:
My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.
Click to expand...
Click to collapse
CM 11: GPS working fine here.

I am using latest frantisheq cm11 built and gps working fine.
Sent from my GT-N7000 using XDA Premium 4 mobile app

Strange, I've formatted the Note, put the rom Slimsaber and Cyanogenmod 10.2 and gps still not working. I am using GPS Test and Sygic for try to capture the satellites but nothing happens.
Would know tell me a way to check if the gps is actually connected, and if there is any way to fix this?
Thank you for the help of the two.

dexterdroid said:
Strange, I've formatted the Note, put the rom Slimsaber and Cyanogenmod 10.2 and gps still not working. I am using GPS Test and Sygic for try to capture the satellites but nothing happens.
Would know tell me a way to check if the gps is actually connected, and if there is any way to fix this?
Thank you for the help of the two.
Click to expand...
Click to collapse
Try install a stock Samsung rom and check GPS.

I have the same problem for a while. I am using SllimSaber.
I have formatted and reflashed KK several times nothing changed.
Now i will try stock rom as suggested.

I have installed AryaV7 nothing has changed, no GPS signal at all
Any ideas?

nehiryeli said:
I have installed AryaV7 nothing has changed, no GPS signal at all
Any ideas?
Click to expand...
Click to collapse
Does your phone's GPS indicator blink? Maybe your phone's GPS is broken? Have you tried aps named "GPS Test", from google play?

Did you tried to use the app GPSData to download latest AGPS info?
Also you can try to modify gps.conf/gps.xml to choose different time/supl server, that is greatly helpful for fixing GPS.

Try reflashing rom (clean install) - In case there is nothing wrong with your GPS hardware everything should work just fine

I have modified gps config data with Faster Gps. Results did not change.
I have also used AndroiTS Gps test,Gps data, Gps status, Gps essentials none of them was able to catch a satellite.
I have clean install Slim Saber but the result is the same.
I am started thinking that it is not software related.

It could be a hardware issue....
Folks,
Like you I spent days editing gps.conf, installing apps, reflashing ROMS, all to no avail.
There seems to be no magic bullet and what works for one may not work for another, but I eventually stumbled across http://forum.xda-developers.com/showthread.php?t=1973727.
As you will see it requires opening the case and 'tweaking' two contact points. To my surprise it worked for me - although not perfectly. I get about 10 satellite fixes and 6, maybe 7 locks. ('GPS Test' is an excellent freebie to tell you what locks/fixes you are getting.) But a big step in the right direction. There are a few images in the thread that describe the issue/ remedy.
Top (well, average) tips:
1. If you haven't taken a case off before:
a. don't try it just before setting off to a dinner party. It is a bit of a pig and requires some grunt, swearing and patience - but it can be done! There are a few YouTube videos that help explain the process.
b. you will require a size 000 cross-head (Phillips) screwdriver. Go out and buy one if necessary (if you can find somewhere that sells them - I use the one from my spectacles repair kit which just happens to fit; not perfect but does the job - http://www.poundland.co.uk/spectacle-repair-kit. If you try with too big a head you risk stripping the screw heads and that is ......... well, not recommended.
2. Once you have completed the job test your N7000 (with GPS Test) before putting the 9 screws back in. Mine works better with no screws! You may find different.
As I say above this may work for you and may not, so the usual health warning, proceed if you wish.
You can find similar issues on Samsung smartphones, eg http://gs3.wonderhowto.com/how-to/s...-gps-problems-your-samsung-galaxy-s3-0145332/.
Good luck :laugh:
FT

Thank you very much.
Works like charm!!! :good:
The problem was in antenna.

dexterdroid said:
My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.
Click to expand...
Click to collapse
Did you solve the problem? I have the same trouble that have arisen after updating to kitkat.I tried everything to solve it, without success (clean installation, downgrading to stock rom, editing the gps.conf file, reinstalling google maps, modem changes, hardware check ect.).
I switched to Lollipop but problem remain unsolved.
Regards

I'm glad I found this thread; I too have tried all possible solutions that may have worked for others (edit gps.config, reflash stock ROM, go back to GB, tighten the screws, bend the antenna contacts and so on), and none have helped. At all.
Now, I read somewhere that what is most likely causing the problem (completely dead gps, gps status apk shows zero satellites) is a corrupted EFS partition. This is a partition that usually is not touched by factory resets, ROM changes and so on. It also contains information that you cannot afford to loose (imei and so on).
So, I managed to backup this partition using KTools. Now, the problem is how do I get a clean, EFS partition? Is there a way to reflash this partition from a hidden backup thru odin? Or some other way?
Any help would be vastly appreciated!
Regards.

[Q&A] [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13

[Q&A] [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13
Q&A for [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]
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 [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]. 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!

I too had some problem with last R13 update:
- Contacts in SIM are no longer seen, so they can't be transferred to phone,
- Found WI-FI and mobile network turned off, may airplane mode have been set on by itself?
Now went back to R11

Brightness issue
Hello, loving the ROM so far!
Only thing I dont know how to solve is max brightness after I reboot the phone (I have set mine to minimum).
It gets back to minimum after the screen turns off or after I manually set it off.
I tried factory reset, didnt help.
Thanks for the help!

upgrade new rom
Hi,
last week i installed this version
20140910 Release 12 on my samsung galaxy s plus
followed all steps from the openings post of this thread:
http://forum.xda-developers.com/showthread.php?t=2579431
I used CWM.
My question is with steps should i take if i want to upgrade to
20141011 Release 13 [EOL]?
Thanks a lot

First you have to update TWRP to 2.8.0.0. from there you can flash R13 and reboot.
Gesendet von meinem Nexus 5 mit Tapatalk 2

Installing CM11 rel11, serial disappeared - best way to restore?
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!

Project dead?
I have tried to download R13 files. All downloads hosted by devhost failed because the files seem to be unavailable. Tested with Chrome and Dolphin on i9300 and i9001.
Can you or someone who has already downloaded the files please provide an additional mirror?
And why is R13 EOL if there is no clue of a newer Version? Have you stopped the development completely or are you preparing for Lollipop?

I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?

Yes I share the same problem, as said in post 21 oct 2014 at 07:30 PM.
I can't use the contacts because they can't be read in the SIM and can't be exported to the thelepone memory.
Tried with wiping, cleaning, etc., but I had to step back to a previous release (R11) very well working.
Looking at the lenght of the files I could see that R11 is 210.888 KB, R12 is 211.708, and R13 is decreased to 189.921.
Something lost

deduud1 said:
I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?
Click to expand...
Click to collapse
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...

smitharro said:
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...
Click to expand...
Click to collapse
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro

deduud1 said:
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro
Click to expand...
Click to collapse
I don't think the language settings of your interferes with the signal of your provider. I always use English with Kpn..

Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks

callegan said:
Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks
Click to expand...
Click to collapse
I tried to copy one of my old contacts from the Sim to the phone with 'Sim contacts'. It works perfect! The contact is visible in in 'contacts' after this operation! It isn't visible when it's only on the Sim card however... Sorry but I'm afraid I can't give you a solution for this, other than just use Android phones...

Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello

callegan said:
Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello
Click to expand...
Click to collapse
Glad it finally worked out for you! I used the Needom Studio app. That one worked fine for me. Don't know why it didn't work for you. Most important: your problem is (somewhat) solved, although it's just a workaround. The Rom still doesn't read the sim-contacts 'by itself'. For me, personally, that's not an issue. Hope the rom will be made 'perfect' before it reaches it's real EOL... On the other hand, nothing in life is absolutely perfect! remember: this rom is brought to us absolutely with no charge by people who volunteer to do this development, just because they like doing this.

Still confused
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
chronosynclastic said:
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!
Click to expand...
Click to collapse

chronosynclastic said:
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
Click to expand...
Click to collapse
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!

Thank you for your reply!
My IMEI number remained well, however I learned that both IMEI and serial (S/N) is needed to have a phone (e.g. to connect to carrier) instead of having a tablet.
For example here is said: "IMEI is showing now but still no calls and sms. I also noticed that the serial number is not the same as the one written at the back of the phone. I have read that restoring EFS solves this problem".
There is also some magic ("azira patch") to S3 that states the same. It operates by bypassing serial check, but since it is old (2013) and originally for S3, I'd rather stuck restoring my /efs partition.
Backing up /efs is written down everywhere. Restoring it... well. Mostly external tools are mentioned, that don't support i9001.
Even further, suppose restoring /efs and /persist is the solution for my problem, I think I know how to do that. At least by dd. What I don't know is that the structure of these partitions is fix or may change between Android versions. And of course: if I rewrite them to original, will my device boot again?
Considering these, any idea if I'm off track, or not?
smitharro said:
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!
Click to expand...
Click to collapse

I never touched my /efs partition nor will I ever! My phone is running fine without the serial number displaying in the rom! I can make phone calls, send text messages and I have mobile data! So you really don't have to restore the serial number. Possibly it's still there and still used by the provider, but is the settings app simply not reading it... Sorry I can't help you more. I'm not a developer, just a user...

[Q] "Not registered on network" error. *PLEASE HELP*

Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.

Always a good idea to check your APN settings if you are in a known coverage area with a new ROM. Been my problem 90 percent of the time
Sent from my SM-N910T using Tapatalk

Applejackson said:
Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.
Click to expand...
Click to collapse
Funny you mention this as I run the same ROM and have had this occur to me whilst traveling around my area and in and out of T-Mobile "Dead Spots" which seem to be many...
Even called T-Mobile to report and best they could tell me is go into "More Networks-Mobile Networks-Network operators" and select - Select automatically.
A real PITA when you driving down the road and need to call out or re-connect your call with someone.
Note: I've had numerous issues on different ROMS similar to this so I pretty much blame T-Mobile and their service in my area unless someone else can chime in, I would be curious...

Applejackson said:
Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.
Click to expand...
Click to collapse
I had a similar problem on DK, except that it was unmounting my sim card completely & I had to reboot to get it working again. Happened every hour or so, very frustrating. I tried a different rom & the issue went away, so it's definitely something funky with DK which makes me sad cause that's my favorite rom.
I just reflashed it last night though & I took the precaution of completely reflashing ANK4 through Odin and redoing root & TWRP too, then flashing DK like normal. So far, so good(and it seems to have fixed the battery life issues I was having as well, yay), so you might try that method & see if it helps for you too. But be sure to back up your internal storage first cause odin WILL wipe it. Learned this the hard way, bye-bye all my pictures & titanium backups :/
Files I used can be found here.. BOC4 is for LP, so you should be fine with ANK4.

Mobile Network /Cell standby drain with every rom

Im writing this because my battery life got really bad, and please don't start saying it's a ROM, Google or some apps I've installed issue, because I got this problem with basically every rom, starting from stable, dev MIUI ti LOS15.1.
As you can see from the pictures I get "Mobile network standby drain" in every rom, (In MIUI is called Cell standby)
So i thought It was a firmware issue and I changed, reflashed It and formatted a lot or times but no luck.
So at this point I thought that was an Android way to tell me my battery is diying, but I don't really understand, I also got an android wearable device but this problem persisted even before I bought it.
I've also attached a bugreport
2h of screen are also good for what I got usually, other days I can reach the end of the day 20% with 1h and 30 of screen.

Seems like I solved in LOS15.1 by flashing the latest firmware from the latest dev package from xiaomi, replacing the files on the firmware flashable zip which some guy posted, but not updated it.

lukypuie said:
Seems like I solved in LOS15.1 by flashing the latest firmware from the latest dev package from xiaomi, replacing the files on the firmware flashable zip which some guy posted, but not updated it.
Click to expand...
Click to collapse
So, did it help? Please be specific what exactly did you do.

Set the principal SIM(The SIM that you use mobile data) to 4G Network mode and the secondary SIM to GSM or 2G mode.

ROG Phone 2

Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.

What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.

This is a boot image issue

Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution

He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.