Related
Hi guys id love input on this one if anyone's got anything as it baffles and frustrates me...
I have a SM-N9005,
im signed upto galaxynote3root.com
my note 3 ran to perfection once rooted and updated to 4.4.2 va the polish rom that came out since im in UK and couldn't wait for the update hehe - still ran to perfection -
I then flashed a ROM from galaxynote3root.com (I now HATE that zedomax guy since he has not input or suggestions on the matter despite a courteously written email etc) it was "infamous ROM" (which is supposed to be for SM-N9005 but when installed all T-Mobile bloatware is on it and then model displayed in the about settings page says "SM-N900T") flashed it and installed trickster MOD, (didn't check or even think that the GPS didn't work at that point) I then set the voltage to offset -25 as instructed by zedomax for better battery life etc... anyway, my note 3 couldn't really handle the change in voltages so I went back to stock (or what I thought was stock since I didn't check the default voltages before changing and I don't know what they are) after deciding... I actually hated the ROM and flash all the way back to stock
GPS NO LONGER works - ill explain exact symptoms etc
GPS icon flashes - notification displays "searching for GPS" and........... that's it.. forever.... never locks...... and whilst using the GPS and using google maps in this state it constantly says "GPS signal lost" - and that is literally it. I have flashed at least 5 different stock ROMS from different countries/carriers etc - nothing always exactly the same
NOW... here's the weird part!!!????
Once I flash the Infamous ROM back onto the phone - THE GPS works....... no idea how - but I feel that it doesn't QUIET work as well as it did before (takes a little longer to lock but still around 10 seconds) and the locator on google maps seems to drift a LITTLE where as before it would be perfection no drifting no nothing.
Does this rom use something else or some change in the conf files to supposedly make the GPS "better" but actually makes it worse!!?? lol
Being a techy myself and constantly plying with tech from waaaayyyy back this really frustrated me as clearly it cant be a hardware issue since it works on one ROM but not on stock (unless as I said the infamous ROM utilises a different method to lock GPS... which is NOT better and I don't like btw)
I sent the phone into O2 for repairs and since the knox and counters were tripped they sent back unrepaired stating they cant fix as the engineers found there had been "unauthorised rework" done on it
it has to be software right!!!???? but if that was true.... the stock ROM SHOULD work.... but they ALLL don't.. makes NO sense.
If anyone has any suggestions or input at all I would greatly appreciate.. potentially more!!
I would like to figure this one out too I'm on the Verizon note 3 SM-N900V stock 4.4.2 and the GPS sucks! It was perfect on 4.3 so I know it is definitely a software issue. This is the best phone I've ever had and the worst GPS. Hope we can find a fix because I rely on Google Maps a lot.
Sent from my SM-N900V using Tapatalk
I had issues with my gps not locking after a rom update, I fixed it by downloading gps test from play store and clearing "agps data" in settings.
Give it a go it worked for me. Good luck
Sent from my SM-T320 using Tapatalk
Did you a factory reset?
Sent from my SM-N9005 using XDA Free mobile app
No. Just a reboot after I had used the app. As I said my gps would never lock even outside but after using g the app it's quick to lock. I got the tip from a forum but may not help you.
Sent from my SM-T320 using Tapatalk
cjacobs611 said:
I would like to figure this one out too I'm on the Verizon note 3 SM-N900V stock 4.4.2 and the GPS sucks! It was perfect on 4.3 so I know it is definitely a software issue. This is the best phone I've ever had and the worst GPS. Hope we can find a fix because I rely on Google Maps a lot.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
but for me.. not just GPS sucks... gps does not work categorically anytime ever lol... ONLNY on that infamous ROM I told you about..
hopefully otherwise ill have to do an insurance job on it! lol I definitely agree.... best phone ive ever had... did have the best GPS.. but I feel I may have done something to GPS chip whilst undervolting... but I say that then I remember... but no.. the GPS still works on that particular rom so it cant be that the GPS chip is fried... unless... like I said, that infamous ROM makes the GPS work in a different way.. I just don't know enough about it.... what I do know is that it DOES NOT make sense! lol
gingerdude said:
I had issues with my gps not locking after a rom update, I fixed it by downloading gps test from play store and clearing "agps data" in settings.
Give it a go it worked for me. Good luck
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
perhaps I didn't explain myself... its not because of the ROM update.... the GPS and everything was working to perfection on 4.3 and 4.4.2... it only stopped once id flashed the infamous ROM and then back tot he stock 4.4.2 roms.... now the only way to get GPS working is by flashing and using the infamous ROM
many thanks for your input though dude much appreciated
Egorych said:
Did you a factory reset?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
my friend.. all I can say is... lol... factory reset... lol.... umm yes... I did one....2....3..4,5,6,7,8,9 etc of those followed by 5,6,7,8 different stock roms etc (as stated in my original post)
so yeah... did that.. doesn't work
thanks for your suggestion though kind sir!!
What happened here is the same thing that happens when everyone installs the s5 port and when they revert to their stock rom they f*** up their GPS, since they initially installed a wrong firmware for their phone. Easiest way to solve this is to install that infamous ROM again and turn on your GPS. Then in recovery dirty flash stock note 3 rom (dirty flash... i mean don't do any wipes what so ever) and reboot. You might be able to boot it or basically go into bootloop. Then afterwhich do a factory reset in recovery again. Once booted up you should have your GPS back. There is another method here about flashing n9005 wifi/nfc and stuff files. I just can't find it. But do a search it will come out.
try this
go to recovery
full wipe ..(partition system , data, cache ) ..system partition needs to be wiped
if you are using philz then do a new rom wipe which also wipes system partition
reboot to download mode and odin flash stock samsung note 3 rom ( do it twice to make it 200% sure ..lol)
download gps status and reset ur agps data and download new data from the app
And apparently service centers have to prove that your rooting/flashing 'broke' the phone.
Maybe a grey area but apparently European legislation says so?
So threaten O2 with this?
Try GPS Status and in tools check/update agps.
tyre777 said:
What happened here is the same thing that happens when everyone installs the s5 port and when they revert to their stock rom they f*** up their GPS, since they initially installed a wrong firmware for their phone. Easiest way to solve this is to install that infamous ROM again and turn on your GPS. Then in recovery dirty flash stock note 3 rom (dirty flash... i mean don't do any wipes what so ever) and reboot. You might be able to boot it or basically go into bootloop. Then afterwhich do a factory reset in recovery again. Once booted up you should have your GPS back. There is another method here about flashing n9005 wifi/nfc and stuff files. I just can't find it. But do a search it will come out.
Click to expand...
Click to collapse
sounds good.. but one thing... to flash stock roms I use odin... that's not a recovery flash.... what do you mean exactly? are you able to obtain and flash stock ROMS via recovery in zip form instead of .tar via odin now?
xinfinityoO said:
try this
go to recovery
full wipe ..(partition system , data, cache ) ..system partition needs to be wiped
if you are using philz then do a new rom wipe which also wipes system partition
reboot to download mode and odin flash stock samsung note 3 rom ( do it twice to make it 200% sure ..lol)
download gps status and reset ur agps data and download new data from the app
Click to expand...
Click to collapse
ive already tried this... in about 50 different variations as well.... all full wipes :'(
http://forum.xda-developers.com/showthread.php?t=2751849. Read 3 last pages, i wrote there how i did fix my gps on same kind of situation.
Lähetetty minun SM-N9005 laitteesta Tapatalkilla
massive thanks to all of you guys i really do appreciate your responses i have managed to fix this problem completely thank the lord i love my note 3 what i did was basically install Philz recovery and use all of the wipe functions on there including one I hadnt seen before on other recoveries which was "format boot" so big thankyou to xfinity for the philz tip I also turned on my gps and left it on before rebooting to commence rebuild which could have possibly had a positive effect so that tip was from tyre777 so again huge thanks to you as well kind sir!!! happy days case closed.. thanks all!
fletchy88 said:
massive thanks to all of you guys i really do appreciate your responses i have managed to fix this problem completely thank the lord i love my note 3 what i did was basically install Philz recovery and use all of the wipe functions on there including one I hadnt seen before on other recoveries which was "format boot" so big thankyou to xfinity for the philz tip I also turned on my gps and left it on before rebooting to commence rebuild which could have possibly had a positive effect so that tip was from tyre777 so again huge thanks to you as well kind sir!!! happy days case closed.. thanks all!
Click to expand...
Click to collapse
cn u please post step by step instructions..
one of my mates having similar problems and he cant fix it..
thanks
xinfinityoO said:
cn u please post step by step instructions..
one of my mates having similar problems and he cant fix it..
thanks
Click to expand...
Click to collapse
I most certainly will xfinityoO ill get to it tonight, once again many thanks for you guys reponses, i was expecting to get nothing so big help!
p.s if there is a way i can give something back id be glad... is there any rating system on xda like on other forums whereby i can mark your profiles with something that indicated your level of knowledge... are you following me?
EDIT: Just seen the Thanks button system lol Thanks goes out to XfinityoO and tyre777
Just hit the thanks button..dats all mate..we are here to help each otherr
Sent from my SM-N9005 using Tapatalk
fletchy88 said:
Hi guys id love input on this one if anyone's got anything as it baffles and frustrates me...
I have a SM-N9005,
im signed upto galaxynote3root.com
my note 3 ran to perfection once rooted and updated to 4.4.2 va the polish rom that came out since im in UK and couldn't wait for the update hehe - still ran to perfection -
I then flashed a ROM from galaxynote3root.com (I now HATE that zedomax guy since he has not input or suggestions on the matter despite a courteously written email etc) it was "infamous ROM" (which is supposed to be for SM-N9005 but when installed all T-Mobile bloatware is on it and then model displayed in the about settings page says "SM-N900T") flashed it and installed trickster MOD, (didn't check or even think that the GPS didn't work at that point) I then set the voltage to offset -25 as instructed by zedomax for better battery life etc... anyway, my note 3 couldn't really handle the change in voltages so I went back to stock (or what I thought was stock since I didn't check the default voltages before changing and I don't know what they are) after deciding... I actually hated the ROM and flash all the way back to stock
GPS NO LONGER works - ill explain exact symptoms etc
GPS icon flashes - notification displays "searching for GPS" and........... that's it.. forever.... never locks...... and whilst using the GPS and using google maps in this state it constantly says "GPS signal lost" - and that is literally it. I have flashed at least 5 different stock ROMS from different countries/carriers etc - nothing always exactly the same
NOW... here's the weird part!!!????
Once I flash the Infamous ROM back onto the phone - THE GPS works....... no idea how - but I feel that it doesn't QUIET work as well as it did before (takes a little longer to lock but still around 10 seconds) and the locator on google maps seems to drift a LITTLE where as before it would be perfection no drifting no nothing.
Does this rom use something else or some change in the conf files to supposedly make the GPS "better" but actually makes it worse!!?? lol
Being a techy myself and constantly plying with tech from waaaayyyy back this really frustrated me as clearly it cant be a hardware issue since it works on one ROM but not on stock (unless as I said the infamous ROM utilises a different method to lock GPS... which is NOT better and I don't like btw)
I sent the phone into O2 for repairs and since the knox and counters were tripped they sent back unrepaired stating they cant fix as the engineers found there had been "unauthorised rework" done on it
it has to be software right!!!???? but if that was true.... the stock ROM SHOULD work.... but they ALLL don't.. makes NO sense.
If anyone has any suggestions or input at all I would greatly appreciate.. potentially more!!
Click to expand...
Click to collapse
Enter root folder and open up etc>gps.conf using text editor and change LPP_PROFILE to 3 instead of 0.
fletchy88 said:
I most certainly will xfinityoO ill get to it tonight, once again many thanks for you guys reponses, i was expecting to get nothing so big help!
p.s if there is a way i can give something back id be glad... is there any rating system on xda like on other forums whereby i can mark your profiles with something that indicated your level of knowledge... are you following me?
EDIT: Just seen the Thanks button system lol Thanks goes out to XfinityoO and tyre777
Click to expand...
Click to collapse
Where's the step by step?
I was on xdabbeb's ROM, and I decided to install Cloudy's G3 rom. I didn't like it, so I decided to clean flash xdabbeb's ROM from scratch. After installing it, I noticed that knockon didn't work but knock off worked fine. I clean flashed it again, it still didn't work. Then I clean flashed Mahdi's July 9th build, and knockon works perfectly fine. Then I flashed Cloudy's G3 ROM again and knockon worked. Then I flashed xdabbeb's ROM and knockon didn't work.
How do I fix this? I want to go on xdabbeb's ROM but knockon won't work anymore on his ROM. I think Cloudy's ROM has messed it up. It's definitely not a hardware issue.
Enter the service menu for your model:
3845#*XXX#
Where XXX is your model, for example I have D802 so I type:
3845#*802#
Go on Settings, and hit "Update Touch Firmware".
Wait a second, and see if it works.
Im sort of experiencing the same issue. I kdz'd to full stock re-rooted, ran a few aosp roms, then flashed cloudyflex and now knockon only works with stock based roms.... If you knock 5 times will yours wake? Mine will after the 5th tap, but that gets annoying pretty fast. And I cannot access the service menu in any aosp roms anymore either. It just inputs my code (being a d801) and never goes into the menu, but it works fine in the stock based roms.
Because the service menu is available and is part of stock ROMs only.
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
AspenSTi said:
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Not sure what you on about but I've been on stock, Mahdi, Paranoid Android and now Cloudy G3 and my knock code works and I can enter service menu.
curiouscow said:
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Click to expand...
Click to collapse
I've tried a few different Kernels while on aosp, all giving me the same results. I'm now on a clean flash of cloudy g3 and will try again tonight to see if it changes anything with an aosp rom. If not I'll go back to full stock just to see what changes and when.
Sent from my VS980 4G using Tapatalk
Fixed it for myself. I kdz'd back to 20a and now knock-on works as it used to. I don't use knock code so I'm not missing anything as of yet... Just thought I'd pass the info along.
I have very strange problem. I had in my hands two S5 and I decided to sell mine and keep the other because it was newer. So I decided to root the other the same way I did mine and install the same Rom. Everything goes fine but on the other Fingerprint scanner doesn't work, however it is functional because on the other Rom it works. The only difference between devices was that mine was rooted on 4.2 and this one on 5.0. Maybe that's why. Otherwise I.have no clue what to do. I guess stick with my old S5.
If you are using a stock based rom rooting should not effect fingerprint scanner.
anubius said:
I have very strange problem. I had in my hands two S5 and I decided to sell mine and keep the other because it was newer. So I decided to root the other the same way I did mine and install the same Rom. Everything goes fine but on the other Fingerprint scanner doesn't work, however it is functional because on the other Rom it works. The only difference between devices was that mine was rooted on 4.2 and this one on 5.0. Maybe that's why. Otherwise I.have no clue what to do. I guess stick with my old S5.
Click to expand...
Click to collapse
Are you rooted on a stock firmware? We need more details as to how you configured your device after rooting. Fingerprint scanner shouldn't be affected as long as you're using a TouchWiz-based ROM or a stock firmware which is rooted.
Sent from my SM-G900F using XDA Forums
Vineen said:
Are you rooted on a stock firmware? We need more details as to how you configured your device after rooting. Fingerprint scanner shouldn't be affected as long as you're using a TouchWiz-based ROM or a stock firmware which is rooted.
So here is update. Basically only one Rom doesn't have the fingerprint working. It is XStore Rom. I can't figure out why on the other S5 it works, however on this that I want to keep it doesn't work. So far I've tried multiple other TouchWiz ROms and on all of them the scanner works. I would stop here but I got used to XStore Rom and would like to keep it. I think I should ask on the Rom forum, however it is closed since developer probably left.
Click to expand...
Click to collapse
It must be the problem with the previous firmware that the Android OS is 5.0. As the firmware upgrades, the bootloader upgrades too and O don't know the rom you tried to install but if there is a major update gap (like 4.x to 5.x), the bootloader doesn't match so that fingerprint does not work. I heard that fingerprint function is concerned with bootloader from the Darthrom dev.
anubius said:
Vineen said:
Are you rooted on a stock firmware? We need more details as to how you configured your device after rooting. Fingerprint scanner shouldn't be affected as long as you're using a TouchWiz-based ROM or a stock firmware which is rooted.
So here is update. Basically only one Rom doesn't have the fingerprint working. It is XStore Rom. I can't figure out why on the other S5 it works, however on this that I want to keep it doesn't work. So far I've tried multiple other TouchWiz ROms and on all of them the scanner works. I would stop here but I got used to XStore Rom and would like to keep it. I think I should ask on the Rom forum, however it is closed since developer probably left.
Click to expand...
Click to collapse
You mean XtreStoLite? It is super debloated so you have to flash the fingerprint scanner flashable zip to make it work.
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
Hi, i really have big problem.
my phone has random reboots after trying to turn the screen on when its locked.
I can use the lockscreen around 30 times until i get a reboot. The screen doesnt even turn on. The phone vibrates and reboots.
On Lollipop everything worked fine,no random reboots or else.
I've got the newest BL and modem,otherwise i wouldnt have the chance to use the rom correctly.
I'm currently using Alexandrs rom , v3.2.
Can anyone help me?
Greets
Does this also happens on stock rom?
tapatalked
For me it works great with the same rom.
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
...
007gamer said:
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
Click to expand...
Click to collapse
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
pepe100 said:
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
I still have this problem with twrp 3.0.2.2 test2 and last alexndr rom CPD7
I've also this problem with stock CPD7 rom an no modding.
I still have this problem on cpe2 any fix??? Thanx
Hi,
I also have the problem. There is one thing that looks like related: It only happens if you have the fingerprint reader enabled for unlocking. Is this the same for others?
I also tried latest CPEA ROM by alexandr -> no change. I did not update TWRP because this should be unrelated to lockscreen.
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
igorescu04 said:
For me it works great with the same rom.
Click to expand...
Click to collapse
Do you have fingerprint unlocking enabled? For me it only happens when it is enabled (e.g., when I am not at home). At home my phone unlocks automatically and I can unlock it as often as I want. When I need to use the fingerprint reader it reboots every 10 to 30 times.
I had random reboots on my device after updating from kitkat to marshmallow (stock, no root, over ota)
I didn't wipe after updating (I would suggest to wipe as the first step)
I came back to kitkat because I didn't like the new marshmallow ui (especially the white settings menu!) and because of the reboots. however after reverting to kk I don't have any reboots anymore. so i would suggest just to wipe everything and if it doesn't work go back to kitkat
Sent from my SM-G900F using XDA-Developers mobile app
It is a mm bug so we have to wait for a fix from Samsung
I am now trying CPF3 ROM (by Alexndr)
I have the same problem with 6.01 update
I made full wipe
&no solution
Abo_Moaaz said:
I have the same problem with 6.01 update
I made full wipe
&no solution
Click to expand...
Click to collapse
Which ROM version?
lets send samsung some emails about this problem, maybe they'll fix these bugs soon.
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
cheaterel said:
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
Click to expand...
Click to collapse
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
thetaphi said:
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
Click to expand...
Click to collapse
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
cheaterel said:
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
Click to expand...
Click to collapse
Stock firmware on unbranded fone is no option for me, because it does not have enabled VOLTE in Germany. The one with right CSC is still on Android 5.
I just tested stock ROM for a day, but gave up after doing a loop of "lock - unlock - fingerprint - lock- unlock - fingerprint - ...". Very easy to reproduce, you just need to do it about 20 times. So it has nothing to do with Alexndr.
The firmware version you mentioned is the same kernel and changelist as the recent Alexndr one.
Interestingly the reboots were slightly different with CPF3: Instead of just rebooting with only the button lights on but dark screen, in CPF3 it woke up partially, but screen stayed black, button lights on. But it did not reboot. To make it reboot you had to try to wake it up again. Before that it was rebooting after 2 seconds automatically.
So, I had a day 1 v20 that began randomly rebooting back in december. Thought it was a hardware issue and finally got around to replacing it the other day. Now, after getting the replacement v20 set up on a custom rom (AICP) I'm seeing random reboots again. I've tried every single custom rom available for the h918 and they all experience reboots. When i've asked about the issue in the threads it seems as if I'm the only one. It appears to be a custom-rom only problem that apparently no one else is experiencing? The kernel panics are being caused by the modem, and it started happening when I upgraded to the 10j base. This replacement also came with 10j. Am I just super unlucky with two duds or is there really something going on here?
TLDR; Anyone else with a h918 with 10j bootloader/modem running custom roms and seeing random reboots?
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Biff627 said:
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Click to expand...
Click to collapse
Have always left kernel stock.
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Biff627 said:
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Click to expand...
Click to collapse
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
trobertson said:
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
Click to expand...
Click to collapse
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Biff627 said:
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Click to expand...
Click to collapse
The phone came with stock 10j.. flashing this wouldn't change anything.
trobertson said:
The phone came with stock 10j.. flashing this wouldn't change anything.
Click to expand...
Click to collapse
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Biff627 said:
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Click to expand...
Click to collapse
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
trobertson said:
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
Click to expand...
Click to collapse
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Biff627 said:
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Click to expand...
Click to collapse
Aicp, rr, cm-remix, stock Lineage.
trobertson said:
Aicp, rr, cm-remix, stock Lineage.
Click to expand...
Click to collapse
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Biff627 said:
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Click to expand...
Click to collapse
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j as most custom ROM users are still running 10d firmware
trobertson said:
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j
Click to expand...
Click to collapse
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Biff627 said:
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Click to expand...
Click to collapse
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
trobertson said:
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
Click to expand...
Click to collapse
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Biff627 said:
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Click to expand...
Click to collapse
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
trobertson said:
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
Click to expand...
Click to collapse
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
Not a Samsung fan. Especially with KNOX. I buy phones first based on the chances of development producing workable custom ROMs and second based on hardware features.
Back to the main topic: I just managed to flash the 10i modem alone so we'll see what happens. I'm working on extracting the 10d modem as well.
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
UPDATE: Flashing the 10i modem made no difference, still having random reboots (although they seem less frequent), I will try the 10d modem once I find a way to extract it from the TOT files posted on this forum.