Hello Guys!
I'm from India and as we were waiting long for VoLTE support, I was one amongst to jump onto H2OS.
Now everyone knows that -
1. On H2oS, there are frequent network drops.
2. On CM14.1 , there are frequent random reboots.
I do know that there are too many threads which state the solutions for above problems but the solutions contradict each other.
1. some say enable only band 3, others say enable band 3,5 and 40.
2. some say install network signal guru on H2os and then flash CM14.1 normally. rest say install the app directly on CM14.1.
I've been trying all solutions for a week now and haven't found any permanent solution.
I would like inputs, especially from people who use 2 sims (1 jio sim). and have flashed H2OS.
Is anyone having a stable phone after flashing H2OS? ; ALSO
Any Idea when updated OOS would come out? (I expect it to be a permanent solution).
PS - For some reason, reverting back to OOS also gives me random reboots and so does CM13.0 do. Please help !
tbiwalkar said:
Hello Guys!
I'm from India and as we were waiting long for VoLTE support, I was one amongst to jump onto H2OS.
Now everyone knows that -
1. On H2oS, there are frequent network drops.
2. On CM14.1 , there are frequent random reboots.
I do know that there are too many threads which state the solutions for above problems but the solutions contradict each other.
1. some say enable only band 3, others say enable band 3,5 and 40.
2. some say install network signal guru on H2os and then flash CM14.1 normally. rest say install the app directly on CM14.1.
I've been trying all solutions for a week now and haven't found any permanent solution.
I would like inputs, especially from people who use 2 sims (1 jio sim). and have flashed H2OS.
Is anyone having a stable phone after flashing H2OS? ; ALSO
Any Idea when updated OOS would come out? (I expect it to be a permanent solution).
PS - For some reason, reverting back to OOS also gives me random reboots and so does CM13.0 do. Please help !
Click to expand...
Click to collapse
I have Jio in slot 1 and Vodafone in slot 2.
I am on H2OS VoLTE version.
just install network signal guru app.
there in RAT Locking I selected LTE and in BAND Locking I selected band 3,5 and 40.
Also in sim card settings, I have kept 2G/3G/4G(Automatic) as preferred network type.
Also I have disabled "aggressive doze and app hibernation" in battery settings as well.
And in app settings I have disabled app-auto launch prevent option.
In last 4 days I didn't got any network drops.
Also battery life is better than OOS even after disabling aggressive doze option.
On CM14.1, I am getting random reboots even after using network signal guru app. so be on H2OS until Oneplus releases new OOS update. And I feel H2OS is better than CM14.1 because of its camera and battery life.
Aniket_IITM said:
I have Jio in slot 1 and Vodafone in slot 2.
I am on H2OS VoLTE version.
just install network signal guru app.
there in RAT Locking I selected LTE and in BAND Locking I selected band 3,5 and 40.
Also in sim card settings, I have kept 2G/3G/4G(Automatic) as preferred network type.
Also I have disabled "aggressive doze and app hibernation" in battery settings as well.
And in app settings I have disabled app-auto launch prevent option.
In last 4 days I didn't got any network drops.
Also battery life is better than OOS even after disabling aggressive doze option.
On CM14.1, I am getting random reboots even after using network signal guru app. so be on H2OS until Oneplus releases new OOS update. And I feel H2OS is better than CM14.1 because of its camera and battery life.
Click to expand...
Click to collapse
Hello and thanks for the reply @Aniket_IITM.
Will definitely try it. meanwhile let me know if u get a solution for CM14.1.
tbiwalkar said:
Hello and thanks for the reply @Aniket_IITM.
Will definitely try it. meanwhile let me know if u get a solution for CM14.1.
Click to expand...
Click to collapse
I try all possible solutions and at last I come on conclusion that everything and all trick is useless till HOS didn't come with either new update or OS adapt HOS modem.
Right now I using RR 7.1.1 latest build with HOS modem with single sim I.e. Jio
VoLTE working perfectly no reboot no signal drop and good battery.
So my suggestion is either use single jio sim or wait for stable build of HOS. Doing tricks and flashing lots of ROM is neither a solution nor give stability.
sajidmkhan said:
I try all possible solutions and at last I come on conclusion that everything and all trick is useless till HOS didn't come with either new update or OS adapt HOS modem.
Right now I using RR 7.1.1 latest build with HOS modem with single sim I.e. Jio
VoLTE working perfectly no reboot no signal drop and good battery.
So my suggestion is either use single jio sim or wait for stable build of HOS. Doing tricks and flashing lots of ROM is neither a solution nor give stability.
Click to expand...
Click to collapse
Attached
sajidmkhan said:
I try all possible solutions and at last I come on conclusion that everything and all trick is useless till HOS didn't come with either new update or OS adapt HOS modem.
Right now I using RR 7.1.1 latest build with HOS modem with single sim I.e. Jio
VoLTE working perfectly no reboot no signal drop and good battery.
So my suggestion is either use single jio sim or wait for stable build of HOS. Doing tricks and flashing lots of ROM is neither a solution nor give stability.
Click to expand...
Click to collapse
1. So, on single sim, do i still need to use network signal guru app?
2. In the pic that you uploaded, i see a few network drops. are they major ones?
Network Signal Guru works both on H2OS and CM14.1(RR 7.1) for me...Just lock bands 3 and 5..no random reboots .just a few network drops..these have the frequency of like once in an hour ...and it gone in a minute ...Happy with this...but sure a permanent fix is better..Which will be out before end of 2016...
aaronblaze said:
Network Signal Guru works both on H2OS and CM14.1(RR 7.1) for me...Just lock bands 3 and 5..no random reboots .just a few network drops..these have the frequency of like once in an hour ...and it gone in a minute ...Happy with this...but sure a permanent fix is better..Which will be out before end of 2016...
Click to expand...
Click to collapse
Hello @aaronblaze. any source of this news (new build before 2016)?. Im toh afraid that oneplus would stop support
Also a quick question. are u using only one sim? cause everyone is facing reboots on dual sim
tbiwalkar said:
Hello @aaronblaze. any source of this news (new build before 2016)?. Im toh afraid that oneplus would stop support
Also a quick question. are u using only one sim? cause everyone is facing reboots on dual sim
Click to expand...
Click to collapse
I am using dual sim and I m sure reboots can be stopped by using Network signal guru on Cm14.1 as well as H2OS (its stabilizes network drops here as there were no reboots on H2 OS in the first place)...Well the source is from Oneplus forums ..Everyone knows that Oneplus said it will give an VoLTE update for OxygenOS for OP2 in this quarter..(ie before end of 2016)..
I am using one Jio sim and one vodafone sim in my oneplus 2 on h2os.i had clean flashed h2os after wiping oxygen 3.1.
i had no reboots and no network drops since 6th december.i had not used and software to achieve this stable situation.
H2os on my oneplus 2 is as similar as open beta 8 naugat on my oneplus 3.
tbiwalkar said:
1. So, on single sim, do i still need to use network signal guru app?
2. In the pic that you uploaded, i see a few network drops. are they major ones?
Click to expand...
Click to collapse
No need of any app or setting. Just one jio sim.
Network drop in image is when I reboot cell. Check carefully its power off status so network drop.
I've had similar problems but I found the solution to be quite easy... though it might now work for everybody. I first did factory reset in TWRP, wiped everything except internal storage. Then I flashed official H2OS version 2.5.1 I believe. Restarted phone (it took like 10 full minutes). Went thru initial setup. Rebooted into TWRP. Factory reset, then wipe everything except internal storage. Clean flashed AICP ROM running android 7.1. Wiped cache. Rebooted. Now my phone works 100% no random reboots and VOLTE works as well.
Qbuiwonder said:
I've had similar problems but I found the solution to be quite easy... though it might now work for everybody. I first did factory reset in TWRP, wiped everything except internal storage. Then I flashed official H2OS version 2.5.1 I believe. Restarted phone (it took like 10 full minutes). Went thru initial setup. Rebooted into TWRP. Factory reset, then wipe everything except internal storage. Clean flashed AICP ROM running android 7.1. Wiped cache. Rebooted. Now my phone works 100% no random reboots and VOLTE works as well.
Click to expand...
Click to collapse
Single simmed or dual? also which sim do you use for VoLTE?
tbiwalkar said:
Hello Guys!
I'm from India and as we were waiting long for VoLTE support, I was one amongst to jump onto H2OS.
Now everyone knows that -
1. On H2oS, there are frequent network drops.
2. On CM14.1 , there are frequent random reboots.
I do know that there are too many threads which state the solutions for above problems but the solutions contradict each other.
1. some say enable only band 3, others say enable band 3,5 and 40.
2. some say install network signal guru on H2os and then flash CM14.1 normally. rest say install the app directly on CM14.1.
I've been trying all solutions for a week now and haven't found any permanent solution.
I would like inputs, especially from people who use 2 sims (1 jio sim). and have flashed H2OS.
Is anyone having a stable phone after flashing H2OS? ; ALSO
Any Idea when updated OOS would come out? (I expect it to be a permanent solution).
PS - For some reason, reverting back to OOS also gives me random reboots and so does CM13.0 do. Please help !
Click to expand...
Click to collapse
same issue tried everything but nothing helps . please let me know when you get a perfect solution for it
rrbjerry said:
same issue tried everything but nothing helps . please let me know when you get a perfect solution for it
Click to expand...
Click to collapse
after hundreds of attempts with all the Custom ROMs including CM14, AICP. Slim, RR I finally am having no problem with Grarak's 1312 build of CM14.1. I selected bands3, 5 & 4o through Network Signal Guru when in H2OS and then Clean flashed this CM 14.1 ROM of Grarak. After a couple of random reboots immediately after installing, the ROM remains steady with no random reboots, full HD capability and no perceptiblesignal drops for the past 19 hours . (touchwood) :fingers-crossed:
suchiqaz said:
after hundreds of attempts with all the Custom ROMs including CM14, AICP. Slim, RR I finally am having no problem with Grarak's 1312 build of CM14.1. I selected bands3, 5 & 4o through Network Signal Guru when in H2OS and then Clean flashed this CM 14.1 ROM of Grarak. After a couple of random reboots immediately after installing, the ROM remains steady with no random reboots, full HD capability and no perceptiblesignal drops for the past 19 hours . (touchwood) :fingers-crossed:
Click to expand...
Click to collapse
I guess this is it...
Just a correction band locking doesn't stick after a reboot..let alone after a clean flash...So Network signal Guru hasn't helped u arrive at this fix...I had read in the changelog of the official CM 14.1 saying some improvement/fix related to Jio network..
So I guess the latest nightly ,ie, 13/12/2016 is the solution for random reboots...Rejoice!...Thanks to @Grarak for ur hardwork...
And it would be kind if anyone who tries this build gives a review about it..
Still no luck
aaronblaze said:
I guess this is it...
Just a correction band locking doesn't stick after a reboot..let alone after a clean flash...So Network signal Guru hasn't helped u arrive at this fix...I had read in the changelog of the official CM 14.1 saying some improvement/fix related to Jio network..
So I guess the latest nightly ,ie, 13/12/2016 is the solution for random reboots...Rejoice!...Thanks to @Grarak for ur hardwork...
And it would be kind if anyone who tries this build gives a review about it..
Click to expand...
Click to collapse
i tried clean flashing cm 14.1 13/12 still trapped with insane random reboots hope someone finds a solution for it can't hold with h2os.
GUYS , I FOUND A SOLUTION! Few hours on RR, no reboots or network drops!
Firstly I flashed latest RR Rom (13th dec). then gapps and OP2 camera.
Secondly I found out that the phone randomly rebooted for me when it switched to Band 40 (I'm in Mumbai, India). Hence I selected band 3 and 5 using network guru app. I never expected the solution to work as it always failed on Cyanogenmod. but it worked on RR . I'm really glad.
PS- I was really pissed before few hours and would love to help anyone who is still in this mess and is having problems regarding RR installation. If u need any help, just put a mail on [email protected] or find me on Facebook @ https://www.facebook.com/tbiwalkar .
tbiwalkar said:
GUYS , I FOUND A SOLUTION! Few hours on RR, no reboots or network drops!
Firstly I flashed latest RR Rom (13th dec). then gapps and OP2 camera.
Secondly I found out that the phone randomly rebooted for me when it switched to Band 40 (I'm in Mumbai, India). Hence I selected band 3 and 5 using network guru app. I never expected the solution to work as it always failed on Cyanogenmod. but it worked on RR . I'm really glad.
PS- I was really pissed before few hours and would love to help anyone who is still in this mess and is having problems regarding RR installation. If u need any help, just put a mail on [email protected] or find me on Facebook @ https://www.facebook.com/tbiwalkar .
Click to expand...
Click to collapse
Does this solution worked for anybody else.? Please share the experience, weather it worked or failed. I am not doubting tbiwalkar but I had a stable Slim Nougat for a full day and Grarak 1312 build stable for another full day but eventually they both started rebooting randomly with all my old problems came back like a bad coin.
suchiqaz said:
Does this solution worked for anybody else.? Please share the experience, weather it worked or failed. I am not doubting tbiwalkar but I had a stable Slim Nougat for a full day and Grarak 1312 build stable for another full day but eventually they both started rebooting randomly with all my old problems came back like a bad coin.
Click to expand...
Click to collapse
No problem till date bro. still if you want , wait for someone else to try and comment
Related
sorry for bad english
whether this is the OTA official update but as usual update is like custom update or rom and worst update till today.
it have too much bugs which i and one of my collegue faced are-:
1-App themer crashing as click it crashes i did factory reset but not success found problem on two yureka mobile with 5.1.1.
2-Battery drain like hell worst situtation then previous rom need to charge 5-6 time in 8 hours cant use for watching movie withoutcharging. old solution uses but not works
3-none app locking software working even with enabling with usase aceess
4-mobile hangs on setting if you click two times any setting by mistakes then self reboot
5-camera gives much redness while clicks with flash.
still using i think ROM is not stable will report more bugs
please suggest
I am a user of a OnePlus two and recently I was using Raj gopi's resurrection remix as my daily driver but after the update to Nougat version I experienced various issues in network compatibility( I have two sim cards idea and Jio and in my phone only the sim preferred for mobile data works and the other one does not connect) this is a major problem as I can't use both sims, to solve this I downgraded to resurrection marshmallow version, it didn't solve it so I again installed Nougat and as on today I am using oxygen 3.5.6 (fresh and clean)
Kindly provide a workaround for my problem. Any response would be much appreciated...
PSI kind of think I messed up with the EFS partition and now I am using 1+ recovery and my phone does not seem to be recognised in fastboot devices although it is detected in adb devices)
GandharvSachdeva said:
I am a user of a OnePlus two and recently I was using Raj gopi's resurrection remix as my daily driver but after the update to Nougat version I experienced various issues in network compatibility( I have two sim cards idea and Jio and in my phone only the sim preferred for mobile data works and the other one does not connect) this is a major problem as I can't use both sims, to solve this I downgraded to resurrection marshmallow version, it didn't solve it so I again installed Nougat and as on today I am using oxygen 3.5.6 (fresh and clean)
Kindly provide a workaround for my problem. Any response would be much appreciated...
PSI kind of think I messed up with the EFS partition and now I am using 1+ recovery and my phone does not seem to be recognised in fastboot devices although it is detected in adb devices)
Click to expand...
Click to collapse
Oh hell it starts again.
Please can you learn how to use search function on this forum and not create your own thread ?
Thanks.
casual_kikoo said:
Oh hell it starts again.
Please can you learn how to use search function on this forum and not create your own thread ?
Thanks.
Click to expand...
Click to collapse
Sorry, but I am new on XDA I will search to resolve my issue and will close this thread.
Thank you for your reply
I haven't found found any relevant posts on this topic so my quest for answers is still on...
I tried now lineage, xenon hd and resurrection. In every 7.1.2 ROM I am unable to get the network based location.
Unfortunately the only way I I know to read this battery saving location is by using tasker(which need to work for me)
Google maps is working without GPS. But I think just because near WiFi.
Can anyone check to read the network based location with tasker in a 7.1.2. ROM?
I already checked my APN settings,my sim card and the android right policies for tasker.... No luck at all
It seems that you have similar problem like me and others:
"Network Location Provider" doesn't work with up-to-date Google Play Services
Location not correct when indoors
Thanks for the links. And indeed, it seems like the same problem.
What surprises me is that this bug dont appeal to this community here. For me it is an important feature of google service which we cant use with our OP2.
Furthermore i dont understand why this bug seems to be a bug according to our device.
For me it is ja software bug with no relation to our hardware?
I hope this error gets more pushed soon
mr_krabbs said:
...Furthermore i dont understand why this bug seems to be a bug according to our device.
For me it is ja software bug with no relation to our hardware?..
Click to expand...
Click to collapse
For me, this is also a big problem, because I often need to see geotags in my picture where I made this or that photo. But geotags are not recorded in photos, but if they are recorded, then only one place even if I have already passed 2 kilometers.
There are two solutions - to put Google-camera, but there is very dark video in case of insufficient illumination, the second - to put another ROM. I tried almost all the firmware and only two did not have problems:
Resurrection Remix M [5.7.4]
LineageOS 13.0
But one more problem because of which I will soon change my OP2 is a poor autonomy.
mr_krabbs said:
I tried now lineage, xenon hd and resurrection. In every 7.1.2 ROM I am unable to get the network based location.
Unfortunately the only way I I know to read this battery saving location is by using tasker(which need to work for me)
Google maps is working without GPS. But I think just because near WiFi.
Can anyone check to read the network based location with tasker in a 7.1.2. ROM?
I already checked my APN settings,my sim card and the android right policies for tasker.... No luck at all
Click to expand...
Click to collapse
Just flash latest stock firmware , I.e. 3.6.0 for op2 solved my problem hope it does yours
veeranna said:
Just flash latest stock firmware , I.e. 3.6.0 for op2 solved my problem hope it does yours
Click to expand...
Click to collapse
Thanks. As far as i know the 3.6.0 updates is based on Android 6.0.1. and therefore no android 7.1.x
However you are right, it seems to be the only fix for now. No Android 7 With this feature.
I am just wondering why
mr_krabbs said:
Thanks. As far as i know the 3.6.0 updates is based on Android 6.0.1. and therefore no android 7.1.x
However you are right, it seems to be the only fix for now. No Android 7 With this feature.
I am just wondering why
Click to expand...
Click to collapse
Just flash firmware file not whole rom. Then flash your desired ROM and Gapps
[Q] firmware flash
veeranna said:
Just flash firmware file not whole rom. Then flash your desired ROM and Gapps
Click to expand...
Click to collapse
i am struggling with how to flash a firmware
my source for the firmware is:
https://www.androidfilehost.com/?w=files&flid=53150
when i flash the firmware 3.6.0 in twrp my sim card isnt recognized anymore
if i use the app "[root] FlashFire" i can see i have a new version of baseband but still no luck with the network based location
How do u flash your firmware?
Edit: I did a clean flash
1. firmware
2. latest aospExtended rom
3.gapps
4. magisk and root
i have a new baseband now. but for me my network location is always in the middle of germany. It is not even close to my postion =)
mr_krabbs said:
i am struggling with how to flash a firmware
my source for the firmware is:
https://www.androidfilehost.com/?w=files&flid=53150
when i flash the firmware 3.6.0 in twrp my sim card isnt recognized anymore
if i use the app "[root] FlashFire" i can see i have a new version of baseband but still no luck with the network based location
How do u flash your firmware?
Edit: I did a clean flash
1. firmware
2. latest aospExtended rom
3.gapps
4. magisk and root
i have a new baseband now. but for me my network location is always in the middle of germany. It is not even close to my postion =)
Click to expand...
Click to collapse
Clean installed
Flashed firmware and then RR ROM and gapps wipe cache dalvik cache that's it and one thing don't flash magisk with RR rom had terrible delay in first boot u can flash anytime after first boot this is what I have done and I'm from India and no network issue volte working fine
Hey folks,
Just got an h910 v10l from aliexpress (quite cheap, looked brand new, see note below)
Rooted it, installed full v10r from the forum (and also super rom on v10v, very happy with it except for a slowness issue, see note below)
I tried various lineageos roms (14.1 official, 14.1 x86cpu, 15.1 second screen by phr00t, 15.1 unofficial no second screen) but they all gave me a crash
(kernel panic, see image attached below : it says "Kernel panic - not syncing: susbsy-restart: Resetting the SoC - modem crashed")
when I go to an area with no phone signal ...
... can anyone help me ?? maybe there is an alternative kernel that would work ?????
(not having this issue with the stock(?) v10l kernel that came with the phone or the mk2000 kernels that are in the v10r or the super rom)
Thanks folks for any help !!!
Additional Notes :
1) I have some doubts if my phone is a real h910 as lgup said "unknown model" (but in the "connexion" it said "h910") and so didn't want to start ... maybe someone could help me with that ??
2) my super rom is very nice but it's kind of slow when installing an app ... looks like it's slow when writing to the mass storage ... otherwise it's fast ... in comparison the lineageos roms I tried were always super fast :good:... I think I am going to write more on that ... in the mean time maybe someone could help me with that ?? thanks
Edit 07/09/2018, answer from https://forum.xda-developers.com/showpost.php?p=77549768&postcount=2081 :
"I've also had the modem crashing quite often, and it happened more frequently over time. At last I didn't know what to to, so I thought why not use KDZWriter to reflash the modem? Well for me that worked, but after three months I started getting these panics again, so just used KDZWriter and it worked again."
=> the problem is that I don't really know where I could get a working modem software (I believe my modem firmware is at least from the v10r rom I installed ...) any help on this maybe ??? thanks !
Edit 07/09/2018-2, from https://forum.xda-developers.com/showpost.php?p=76877050&postcount=1092 :
"eh, somehow i fixed the kernel crashing by flashing modem.img file from Alpha Rom 2.0 package (i think it's 10U based) "
(adityajiwap has an h910 also )
Edit 23/09/2018 : here is the firmware from adityajiwap : https://forum.xda-developers.com/v2...5-1-lg-v20-t3775689/post77597800#post77597800
I tested it on RR and it was working but I was disappointed by my screen colors (kind of yellowish/brownish/darkish hue) and went back to Alpha ROM (I didn t know that I could use KCAL color settings with Gamma Kernel at that time) before I had time to test it in some place with no signal ...
Edit 9/10/2018 : similar issue on reddit : https://www.reddit.com/r/lgv20/comments/9i7igk/issues_running_resurrectionremix_on_h910/
pierro78 said:
Hey folks,
Just got an h910 v10l from aliexpress (quite cheap, looked brand new, see note below)
Rooted it, installed full v10r from the forum (and also super rom on v10v, very happy with it except for a slowness issue, see note below)
I tried various lineageos roms (14.1 official, 14.1 x86cpu, 15.1 second screen by phr00t, 15.1 unofficial no second screen) but they all gave me a crash
(kernel panic, see image attached below : it says "Kernel panic - not syncing: susbsy-restart: Resetting the SoC - modem crashed")
when I go to an area with no phone signal ...
... can anyone help me ?? maybe there is alternative kernel that would work ?????
(not having this issue with the stock(?) v10l kernel that came with the phone or the mk2000 kernels that are in the v10r or the super rom)
Thanks folks for any help !!!
Additional Notes :
1) I have some doubts if my phone is a real h910 as lgup said "unknown model" (but in the "connexion" it said "h910") and so didn't want to start ... maybe someone could help me with that ??
2) my super rom is very nice but it's kind of slow when installing an app ... looks like it's slow when writing to the mass storage ... otherwise it's fast ... in comparison the lineageos roms I tried were always super fast :good:... I think I am going to write more on that ... in the mean time maybe someone could help me with that ?? thanks
Click to expand...
Click to collapse
Your problem started when you flashed los, so you should discuss your problems in the lineage threads and not all over the v20 forums in multiple posts
Sent from my LG-H910 using XDA Labs
I can confirm this happens on my AT&T V20 h910 with any of the latest LOS ROMs (RR, RR SS, LOS, and LOS SS) and gamma kernel builds. It only happens in areas where coverage is poor in LTE and I see the status bar switching between LTE band 12 and 4 as the LTE flashes from LTE <-> LTE+. I can confirm it is LTE bands 12 and 4 as LTE discovery shows alternating bands before the kernel panic and modem crash. This only happens with LTE, as using network mode GSM/WCDMA auto (2G/3G) shows no crashes until LTE is enabled.
This appears to have happened sometime after the September builds, but can't say for sure as I was running flashed US99610f firmware, and went back to H91510e -> dirtysanta -> H91010r in hopes of fixing the IR blaster (just needed to set anymote to "use alernate IR commands" smh). I couldn't go back to using US99610f as it kept bootlooping after "Android System Android is Updating" notification. This panic doesn't happen on US99610f or H91510e or H91520a. I made my own H91010v firmware zip from dumps and it didn't help with the modem crashes. Using a H91020h stock oreo ROM let me unable to use fingerprints so I didn't test any further.
Now I have flashed the modem in this recommended zip 4 times through fastboot to make sure it sticks:
https://forum.xda-developers.com/showpost.php?p=77597800&postcount=2107
adityajiwap said:
hey, this one works for me: https://drive.google.com/file/d/1WQrBl6CGgysg0FqAF-emZRdUTlZv_LQA/view?usp=sharing
you can try flashing it with fastboot.
i've tried the second screen build but i reverted back to stock since i'm facing some performance issues, didn't notice anything wrong with battery life tho.
Click to expand...
Click to collapse
From the looks, the modem seems to come from a VS995 variant as the Baseband Version is "-00053-M8996FAAAANAZM-1.121063.1" cut off due to length, likely "MPSS.TH.2.0.1.c3-00053-M8996FAAAANAZM-1.121063.1". A google search led me to a gsmhosting log mentioning it as VS995 firmware VS9951AA (LG.com shows this as from February 2018).
AT&T never seems to have released version MPSS.TH.2.0.1.c3-00053 at all with any update.
H910 10l-10m: MPSS.TH.2.0.1.c3-00011-M8996FAAAANAZM-1
H910 10p-10u: MPSS.TH.2.0.1.c3-00045-M8996FAAAANAZM-1
H910 10v: MPSS.TH.2.0.1.c3-00045-M8996FAAAANAZM-1.145041.1.149166.1
H910 20g: MPSS.TH.2.0.1.c3-00058-M8996FAAAANAZM-1.155473.1.156374.2
H910 20h: MPSS.TH.2.0.1.c3-00058-M8996FAAAANAZM-1.156374.2.165514.1
I will report back on my findings with this issue... it usually crashes for me daily as I frequently lose LTE coverage, and this seems to trigger the modem crash & kernel panic.
patato21 said:
I will report back on my findings with this issue... it usually crashes for me daily as I frequently lose LTE coverage, and this seems to trigger the modem crash & kernel panic.
Click to expand...
Click to collapse
Thank you very much patato21 for the very informative post !!
Is your phone running OK now with the "recommanded" zip firmware file ????
I am still on Alpha Rom 3.0 and I am "itching" to go Resurrection Remix Second Screen with Gamma Kernel but I still haven't dared because of this modem crash issue ...
Thank you again if you can answer
pierro78 said:
Is your phone running OK now with the "recommanded" zip firmware file ????
Click to expand...
Click to collapse
Yes, my phone is now running fine without bootloops whenever I lose LTE coverage. Now it properly falls back to 3G, 2G, Emergency Calls Only, or No Service. I forgot to test if LTE bands 12 or 17 work, they might not since this appears to be a Verizon VS995 modem. You can try testing with LTE Discovery and using the crowd-source option, and look back at the logs after a while.
There is a problem with pie ROMs!
All of Pie ROMs are getting failed to connect to the mobile data.
MIUI, oreo, nougat roms are fine.
here is the logcat file attached.
* Problem Still exist 2020 April 7 *
PeymanRZ said:
There is a problem with pie roms!
I was on LOS 8.1 then i flashed Nichcream's Pie rom then i found it out LTE data is not working till i switch to WCDMA only, once data turns on i switch back to LTE ! then it fixes until reboot or airplane mode. very strange!
All 7.1 | 8.1 | MIUI roms are ok even MIUI Pie port. but AOSP or LOS Pie roms.
Is there any modem partition problem? or hardware? I'm advanced user fell free to explain more.
Thanks.
Click to expand...
Click to collapse
I have same problem but it's more complicated for me. For sim1 i use OrtelMobile (Germany) and for sim2 Vodafone (Greece). Sim2 (Vodafone) it's working perfectly (LTE) in roaming and no roaming. Sim1 (OrtelMobile) have to do the trick that you describes. In miui roms works both sims perfect. No tricks needed.
ivaitsis1974 said:
I have same problem but it's more complicated for me. For sim1 i use OrtelMobile (Germany) and for sim2 Vodafone (Greece). Sim2 (Vodafone) it's working perfectly (LTE) in roaming and no roaming. Sim1 (OrtelMobile) have to do the trick that you describes. In miui roms works both sims perfect. No tricks needed.
Click to expand...
Click to collapse
Maybe it's stock android problem form google's side! MIUI is ok for both sims but mine is 2gb ram and can't handle new miui ports.
PeymanRZ said:
There is a problem with pie roms!
I was on LOS 8.1 then i flashed Nichcream's Pie rom then i found it out LTE data is not working till i switch to WCDMA only, once data turns on i switch back to LTE ! then it fixes until reboot or airplane mode. very strange!
All 7.1 | 8.1 | MIUI roms are ok even MIUI Pie port. but AOSP or LOS Pie roms.
Is there any modem partition problem? or hardware? I'm advanced user fell free to explain more.
Thanks.
Click to expand...
Click to collapse
I think I have the same problem : I have tried a lot of Pie roms and modem was not connecting at all.
I did reflash MIUI 10 and everything was OK. Then reflash Pie roms ... same story, modem was not connecting at all.
Did you find a solution ?
xyomguix said:
I think I have the same problem : I have tried a lot of Pie roms and modem was not connecting at all.
I did reflash MIUI 10 and everything was OK. Then reflash Pie roms ... same story, modem was not connecting at all.
Did you find a solution ?
Click to expand...
Click to collapse
Still doing mentioned trick couldn't find any solution
I've been facing the same issue for months, I'm using LOS 16 and sometimes if my Wi-Fi is on for longer periods of time, my Mobile data will turn off and I won't be able to turn it back on. I've learnt to just deal with it I guess ¯\_(ツ)_/¯
@ivaitsis1974 @xyomguix @adnaanbheda
Read the first op edit, and fix hour's.
Fixed! Waiting for other users to report if it's global fix.
@ivaitsis1974
@xyomguix
@adnaanbheda
Read the first op edit, and fix your's.
It worked! But after flashing the latest LineageOS, sometimes, I can't hear the other person's voice but I can hear the ring on LTE. Have you faced this issue? @PeymanRZ
Sometimes, yes! I have to redial to hear the call voice. But not always and frequently. I think it's lineage os bug, as it still has dark video and discoloration front camera in gcam.
@adnaanbheda
Update: The problem still exists. I'm asking for developers to check out this problem.
Logcat attached.
Mine too, how to fix this problem?
I also had this problem, with all ROMs I used in Android 10 and 9,
Some parameters given by the operator does not seems to works
If someone still use this phone in france with Bouygues Telecom, the default parameters are wrong, even if you go on their website, use this instead, it works:
APN: mmsbouygtel.com
MMSC http://mms.bouyguestelecom.fr/mms/wapenc
MMC 208
MNC 20
Authent: PAP
APN Type default,mms,xcap
APN Protocol IPv6
Roaming APN protocol: IPv4
MVNO Type Nothing
All other params to Not specified
If it could help for other operators, the default configuration, APN Type was not the same and Auth method was set to nothing
I'm not sure but this could occurs if your operator use different APN for MMS and Internet, it's the case for me, the default APN is just corresponding to the MMS settings, so data is not compatible with this one, you need to manually edit it or add a new APN with internet settings
yoda1490 said:
I also had this problem, with all ROMs I used in Android 10 and 9,
Some parameters given by the operator does not seems to works [...]
Click to expand...
Click to collapse
This also happens to me (with Bouygues Telecom) on every Android 10 ROM. Changing APN Protocol from IPv4 to IPv6 makes 4G data work, but obviously prevents apps from using native IPv4 over LTE, which causes some issues (like Brawl Stars being completely unplayable due to lag).
The default APN settings work flawlessly on my other phone (with LineageOS), which means that Bouygues' default APN settings are not fundamentally wrong.
EDIT: I've dug back in ROM threads to test older ROMs, and found out that the same bug seems to happen with the crDroidAndroid 8.1.0 20180307 ROM, which is an Oreo ROM. Had to go all the way back to Nougat to make IPv4 LTE work...
EDIT 2: So things are getting stranger: after reflashing MIUI, official AospExtended, HavocOS and unofficial LineageOS seem to make IPv4 LTE work flawlessly, but I first discovered the bug on the same ROM with the same version! My bug might actually be carrier-related...