Help S4 Random loss of Signal after Root - Galaxy S 4 Q&A, Help & Troubleshooting

HI
Ever since I Rooted my S4 and installed Carbon rom I having real random loss of network signal.
Some times hours can go by and its fine to 30 mins passing by and loss.
Can guarantee while moving in the car it will happen as you pass between cell mass.
Never happened before I rooted so can only image I have done some thing wrong, I used to have a HTC one and they was so simple to root and to stick a rom on.
The Samsung phone have more steps to them that I can only image I messed up some were along the line , any one with good knowledge care to take a look a my Samsung info screen shots and see if iv done some thing stupid.
Tried forcing 3g only or GSM make no difference tried two other roms and the same happens

Flash stock rom :highfive:

Related

Help needed identifying a problem with my network

Hello,
Im having a most frustrating problem. Im not sure if its a modem issue or a hardware issue. What I am experiencing is this:
The phone shows no bars, but sees a carrier. This happened after flashing back to a stock GB rom after using a CM9 rom. I can receive texts and calls sometimes, but its not consistant. If it shows no bars I can get a call, if it shows one or two bars i cant, but get the missed call notification. I have done factory resets, cache clears. Its really making my phone unusable. I went back to using my 3 yr old Ericsson till I can get this figured out. Im hoping that someone has some advice for me as Im out of ideas. Ive tried to flash just the modem but no luck. Went from CyanTablet to xxjvt 2.3.5, rooted it so I could get the modded recovery. The pins for the where the sim card make contact are damaged but it has worked for the last 2 months that way. I really love this phone and dont want to replace it yet.
rivman05 said:
I really love this phone and dont want to replace it yet.
Click to expand...
Click to collapse
test with a network booster to increase signal strength, free from google but if you bring phone to another location, do you get a better signal? meaning location matters, if you far from your network cell site, its more difficult
Ill try the network booster. All of my old phones pick up 5 bars, I live about 1/4 mile from the cell tower. I have tried another flash with 2.3.3, repartitioned this time. Once its back up and running Ill get back to you. Is there anything else Im missing? Well I think its dead. Ive tried all my coworkers sims in it, nothing came up. It says no service permanently now, guess its a 4" tablet.
Try another radio, i had the same problem wit JW4 radio,flashed JVT and problem solved.
Some radios are better than others in different locations, it also depends on rom used.
I tried a completely new build, flashed a new modem, then flashed xxjvu. Still nothing, going to call Samsung and see if I can get the warranty to fix it. 2.3.6 tho has 364 megs of ram and has almost 200 free, thats cool. zsjw4 has a new look to it.

[Q] Please help :( i9505 Constant random reboot issues..

Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
leijonasisu said:
Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
Click to expand...
Click to collapse
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
I wouldn't worry mate it sounds to me like a definite battery issue
Sent from my GT-I9505
similar problem
leijonasisu said:
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
Click to expand...
Click to collapse
Hi leijonasisu,
I've stumbled across your post after having experienced more or less the same issues as you. After trying many custom ROMs in the last few weeks, the phone has barely been useable for more than a few minutes until it randomly reboots. At which time, I must start over with the whole flashing process. My question is, did getting a new battery resolve your issue? Or did you just trade the device back in?
many thanks
kingzain900 said:
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Click to expand...
Click to collapse
Looks like it's better to restore to Samsung stock firmware first then start again from there,
But this will upgrade the the Knox bootloader also.
Stock firmware can be downloaded here, www.sammobile.com/firmwares
I fixed this ages ago. It was a battery issue, I'd bit my bottom dollar that it would be a battery issue for anyone else too, I've read a lot of stuff online about people who have gotten bad batteries with theirs. Swapped to 2 third-party and apparently larger batteries and never had an issue and never looked back.
Sorry for not replying back much sooner but I forgot about the thread.
Try another battery and if within a day or two you get no reboots then toss the bad battery and enjoy your phone! The thing is the battery (due to voltage issues) can make it look like it's the OSes fault when in actual fact it's just a faulty battery and voltage issues.
same problem here.. s4 randomly reboot..
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Opuske said:
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Click to expand...
Click to collapse
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
spamtrash said:
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
Click to expand...
Click to collapse
hi thx for the answer.
Could infact be knox issue as i am now back on stock rom without root or anything and im not having any issues now.
But i would like to have a custom rom and root again .
So how would i go from here to there without having random crashes / reboots on custom rom ?
Opuske said:
So how would i go from here to there without having random crashes / reboots on custom rom ?
Click to expand...
Click to collapse
Only one option then: read the ROM-specific threads, loo for feedback posts. If ROM would cause random reboots, you can be certain that it will be written there.
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Have you disabled everything related to knox and deknoxified your phone?
Do press thanks if my posts are helpful
Sent from my Stock Deodexed i9500 :')
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Uninstall everything realiting to Knox with Titanium backup and be Happy
Sent from my Galaxy S4 using Tapatalk
i9505 S4 sussed out the randomsoft rebooting
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
satelliteone said:
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
Click to expand...
Click to collapse
Interesting will have to give this a go, also the battery option.
For months I was running on Lollipop custom ROM, the developer did an upgrade and then the SIM card removed error started. I went back to the old version was keep getting the SIM Card removed error. A few days ago went back to Original ROM for NZ 4.4.2 and I still get the SIM Card error and now the phone just reboots randomly.

problem sending mms/sms

Im a long time reader first time poster... i first want to thank everyone here for finding the time and patience to help others by sharing your knowledge ideas and expertise, This is by far the best resource for trustworthy information for Android on the Web. I've been able to help my loved ones and myself by using information i found here through the years and so for that I sincerely thank all of you.
Now onto the issue at hand. .
I have a cricket wireless Samsung sgh-i337z 4.4.2 i337ztuuboa3 I first
Soft rooted with kingoroot, but later i was able to full root using towel root.
No issues until about maybe a month ago when messages i was sending sometimes wouldn't go through until 3 or 4 tries. Its getting progressively worse, to where now have trouble sending emails occasionally also. Keeping the messaging cache cleared is the only way I've found to send them, still not until the 2nd or 3rd or 4th try. . Installed a different messaging app, same thing. It's not a weak signal thing, I've deleted all unneeded stored messages, and I'm not sure what to do next. it's starting to make me crazy. I send a text it goes thru, send another then go about my business, wonder why I never got a response till I pick up my phone an hour later and see that damn failed notification again. It's maddening i tell you! Could it be a network problem because I haven't updated past kitkat? Or is there something else I'm not seeing? I wanted to ask before jumping in trying to update to lollipop, as I am still unable to connect and use adb and I'm guessing updating and keeping root probably won't be like a click 1 and done thing on top of it also wiping my phone, seems like fun all around. I'm open to any feedback and appreciate any help/ advice given....
Thanks so much for all you do and I hope you have a great day!
Well mate, I don't think its a problem to do with you not being on Kitkat, but have you considered factory resetting or talking to your carrier?
I had that problem regularly on my i337 running Hyperdrive RLS 19 which was Android KitKat 4.4.2 but created from a ROM that was originally on Verizon's CDMA network. I found that when I was on Wi-Fi, most of the time my MMS would send about 50% of the time and regular texts would send about 90% of the time. When I shut off wi-fi and used AT&T's network exclusively they sent with a much greater reliability, MMS closer to 90% and normal texts around 100%. My guess is that, since Cricket is switching to AT&T's GSM infrastructure from years of being on a CDMA (Verizon) there is some issue in the hand-off from a CDMA rom that doesn't translate right to the GSM network. What that might be, I couldn't say because I just don't have the background or knowledge (and good luck explaining that to a Cricket rep), but I think I'm right as the the cause at least. That being said, if there is a newer ROM that can be flashed on your phone, or even the same one over with the modems, I'd do it to see if it would fix the issue. I finally flashed my i337 to a stock GSM ROM and it resolved the problem.

LG V20 H910 Difficulty's Please Help Me

Hello Everyone,
Right, I'm just going to give a quick intro to the situation TLDR below.
So I've been on android for a long time, ever since I got rid of my Nokia brick but my girlfriend has been apple since her first phone, so of course, I've been singing androids praises to her about the battery life, rooting and other such android brilliance, then a few months back she said fine but she had a few features she wanted mainly a big screen, removable battery, fingerprint scanner, and a good camera so after looking at loads of phones we settled on the lgv20, and then my headaches with the phone started.
TLDRGot my girlfriend who has been on apple her whole life onto android, didn't work out so great and now I'm looking for some help.
So the current state of the phone is
it's a H910 that was updated to oreo with a H920 kdx then dirtysanterd, then flashed with a rootable oreo rom and rooted with magisk manager, forgive me if I missed anything I did all this a while ago so it's not fresh in my mind and I'm pretty tired right now so il probable edit this later.
But the issues are weird and unlike anything, I have dealt with before so call on the knowledge of any LG v20 gurus for help, the first problem was present out of the box but did seem to get worse after all the flashing and rooting ect, the phone will turn off seemingly at random and won't turn back on until plugged in, and it will also do this if you try to take a photo with flash but not if you use the flash as a torch.
Now the second issue is due to being in the UK and the LG v20 being a US phone and was the reason I started messing with ROMs and rooting, the signal is terrible, I did check to see if this would be an issue before getting the phone and it seemed to be fine for others, but after having this issue and looking a bit deeper I have seen some people having the same issue with signal and having success flashing a modified modem, but I'm worried that it might not work and may make the signal worse, but if anyone has had success getting signal in the UK please let me know how.
Finally, there are just a few annoying things like some pretty heavy slowdown at times and some general glitchiness with apps freezing and crashing, so if there are any good ways to make the phone a bit more optimized and stable while keeping root that would be nice.
Thanks to anyone who reads this, and thank you to anyone who takes the time to share any knowledge and ideas
A lot of stuff there.
Flash issue sounds like a hardware problem but it could be software gone wrong.
Same for signal problem.
I would flash back stock Nougat *US996 KDZ (usa version) to see if the problems go away. Do not root and trial it for a few days.
This will also change the modem which might help signal issue. There is guide to cross flashing variants on this forum and youtube. Search *LGUP patched V20*.
So try this first is my advise.
*is best clean stock rom without network restrictions or bloat

Running Paranoid OS on 6T , Android auto issues in car

(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Wingman626 said:
(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Click to expand...
Click to collapse
Just msm it and run the latest Oxygen OS. There is a MSM tool thread that will assist you and, also a Oxygen OS thread too. This will solve what you mentioned are your issues
Wingman626 said:
(i tried posting this thread this morning but the post did not post successfully because of the image verification thing. if this post was reposted, please let me know)
hello and thank you for taking the time to read my first post. been having an issue with my new phone and i havent the faintest idea on how to diagnose or fix my problem. i am in no ways a developer or knowledgeable in programming what so ever, but i have delved in "script kiddie" roots and customs roms with my older phones trying to breathe new life into those devices as an excuse to not have to buy an older phone, but eventually my samsung note 5 kicked the bucket and wasnt able to keep up with the amount of apps and multitasking i do for work. a friend of mine recommended that i buy a one plus 6t as its not only one of the latest phones (okay not the latest, but still fairly new) , but it was also cheap as hell on ebay for about 250$ for a used one with some slight burn-in in the display (the ghost image suggests this unit was a display model, but its a handy phone and i dont care at all).
Anyways, long story short; friend is a big tech guy and recommend that id root the phone and install a custom ROM (A.K.A paranoid OS) for greater usability and security. since he was way more knowledgeable with this phone than i was in the 2-3 days of owning it; i decided to let him go ahead and do it for me.
the phone runs amazing, and ive used it for work for a few weeks now and it has lived up to my expectations and more... except for 2 issues.
the main issue that this thread is focused on is android auto. on my friends phone, it works great! hooks up and connects every time he plugs in the cable, audio smooth, gps and other features i never knew existed with my old phone. my 6t on the other hand, works when it wants to.
it never connects to the radio and tells me that it cant connect through notifications. after some experimenting, i found out that it does connect; you just have to go to "USB Preferences" in the phone, plug the phone in, see the options light up under ""usb controlled by"", then tap on a different option (even though it wont switch) and tap it again multiple times until the phone connects.
once it does connect, it works great. until you start listening to music. the music cuts out every now and then. sometimes for 1 second, 3 seconds, or 30 seconds. its very random. other stuff that happens is that the UI on the radio flickers constantly or disappears and the resolution looks cut off or looks wonky on different sides of the radio. sometimes its one or the other. i told my friend about it, and he tried clearing caches, force stopping the app, even completely removing the google play service plugin and reinstalling it, but still nothing. after he tried it, i had phone hooked up to the radio for work, it worked fine for a few hours until everything froze and my phone went completely black and a bunch of colorful letters on my screen pop up that say "CRASH DUMP". phone reboots just fine and works fine but the issues before the crash still happen.
the second issue is that my fingerprint sensor detects fingers but cant read anything, but thats the least of my concerns and i dont care if it doesnt work.
my friend has no idea what else to do and i am kind of disappointment but i still want this to work. although i have no idea where to start or what to do.
if your willing to help an inexperienced dude get his phone working, that would be greatly appreciated. other than that, i hope you have a good day
EDIT:: just a quick add on to say that ive tried different USB-c cables and this radio is notn aftermarket. im using stock radio on my 2019 nissan altima
Click to expand...
Click to collapse
scorpio76r said:
Just msm it and run the latest Oxygen OS. There is a MSM tool thread that will assist you and, also a Oxygen OS thread too. This will solve what you mentioned are your issues
Click to expand...
Click to collapse
I totally agree flash the stock Rom
OOS is amazing. Rooting is easy if you decide you need it.
Sent from my ONEPLUS A6010 using Tapatalk
Does your friend have the the same phone? It is very common that custom ROM works flawlessly on one model but full of issues on the other, even they are from same manufacturer. The stability of a custom ROM depends on how many active user use the rom. Most of one plus users used oxygen. So not so many people could give you answer.
BTW, I would never advise someone to use custom ROM if they don't know how to flash by themselves.

Categories

Resources