Related
1- Hello guys, I have an T-Mobile USA HD2. I love it but it freezes like crazy, 2-3 times a day if not more. I ran Task 29 to delete every possible trail of previous roms followed by a hard reset but nothing. It will still freeze.
2- I also have a lot of signal problems. Its constantly changing from 3G to Edge on the same location. I know that is not normal so I spoke to T-Mobile and they changed the SIM card but it will still change the signal back and forth. I re-flashed couple of radios but nothing, I only accomplished to drain more battery.
3- BSB Tweaks is an awesome app but there are issues with the Rotation Option. If I enable Rotation to the "Start" -> "home screen" the photo album and music will be affected because the already come with landscape support. I tried to disable the landscape support for these using a registry editor but did not find a way.
Is there any solutions for these problems? Any help will be very much appreciated, not only from be but as well from others with the same or similar problems. Thanks in advance to all of you.
Note: I noticed the recently released TMUSA HD2s come with a yellow reset button. I bought my back on March when they sold out Nation wide with in the firs 4 hours and it comes with a RED reset button. This might explain a lot. If you know something please share. Thanks!
I would like to know if there is help for freezing issue.
I also did Task 29, flashed few different radios, few different roms incoluding stock, and it still happens. If my phone freezes I have to try for 20 minutes to restart it, as it hangs everywhere starting with bootloader, to manila.
Any help would be GREATLY appreciated!
I had a similar issue as well and it turned out to be a cab file I had installed that was not compatible for my ROM. I had to go through and isolate which cab it was by using the date it was added and when I noticed the issues.
When your phones freeze....does it do it radomly or while trying to access or carry out anything specific. Your problem could be caused by any number of reasons but giving as much detail regarding your problem keeps you from getting so frustrated trying all sorts of fixes. Out of curiosity what ROM's are you both currently running?
I am currently using Elegancia ROM from August 23. Before I was using Energy ROM. I tried newest, stock Rom for T-Mobile HD2 but it didn't solve the issue.
I tried reinstalling HSPL, but it didn't help either.
The problem started after I put Ubuntu 0.2 on my sd card. I was playing with it for a little and it suddenly rebooted my HD2. I though, OK, no big deal, it's just in infant stage.
So I booted Windows again (energy rom with 2.12 radio) but it hanged while Sense was loading. I wasn't able to get it back to life after few reboots so I did a hard reset (vol up/down power on) It worked fine.
My problem mostly happens when I run android and when it reboots for some reason I can't get back to windows. It hangs, sometimes it hangs on bootloader before it even shows me radio and data version!! sometimes it goes past bootloader and hangs right after sense launches, and sometimes it is perfectly fine.
It also seems that when I just use WinMo it is fine, I can power down, and soft reset without major issues. But after running android I get that issues, especially when Android crushes.
I am thinking that android may be corrupting some WinMo files, but how is that possible? Android doesn't have access to NAND so technically it shouldn't prevent WinMo from booting on bootloader level.
Please let me know if you need me to explain more.
Thanks for your help
KML
PS. I don't have any custom cabs installed at this point. I have super fresh and clean installation of elegancia rom
Yeah...Android may be the culprit. I have shyed away from trying it because I have talked to quite a few people (not on XDA) that have tried it on the HD2 and they have the same issues. The Android OS really makes the HD2 unstable. I personally am going to hold off on the Android bandwagon until a little more time passes, after all WinMo works just fine for me. Try just running on WinMo and see what happens. Based on what you have said, it runs fine as long as you are not using Android
yeah, it's is good idea to stay away for some time. But Android development needs testers. If no one is willing to test than there will be no improvement.
What I can't understand is that even after I do hard reset I still get freezes.
kml.krk said:
yeah, it's is good idea to stay away for some time. But Android development needs testers. If no one is willing to test than there will be no improvement.
What I can't understand is that even after I do hard reset I still get freezes.
Click to expand...
Click to collapse
Yeah I agree with you on Android development needing testers. I do rely on my phone a lot for work purposes and I can't always afford to have the phone freezing up constantly.
Are you hard re-setting with the Android OS still installed?
Technically it is still installed but it is only present on the SD Card, and not anywhere else so it shouldn't matter. Next time I get freeze I will try to remove SD Card before hard resetting.
I tried booting few times with SD Card taken out, but it didn't help.
KML
I have the same issue...i'm using energy rom and i noticed that lately its freezing like hell...at least twice a day...!! NRGZ already notice the freezing issue and is trying to solve it...but it still crashes. I'm constantly changing the rom as he updates...and right now i'm running the August 25.
Sometimes it crashes while being turned off...and i need to take the battery off to restart.
I had the same issue,all i did loaded a diff rom and formatted my sim card problem solved
I did format my SD Card many times. Did not help. I used recommended FAT32.
Yesterday my phone froze when I was trying to add program shortcut to Sense... silly.
I rebooted phone, it booted fine, but hang as soon as I went to check my TXT messages. Rebooted again and it is working fine until now.
I currently have Elegancia ROM with 2.12.50 radio, have not been using android for couple of days, but it is still there on my SD Card.
It is getting a bit frustrating. I wonder what else I can try to make it stop freezing.
KML
My phone rebooted again yesterday.
I couldn't boot to windows for the next 20 minutes... I tried about 10 times before it worked. 2 or 3 times it booted windows and froze as soon as I clicked on one of sense tabs.
I haven't played with Android for past week and the freezing problem is still an issue. I even removed andorid form my SD Card.
When all this happened I was just using skyfire to browse internet.
I am hopeless at this point. I have no idea what else I could try to make it stop rebooting and freeezing.
Any ideas?? I would greatly appreciate any help.
PS. I recently found a thread about a tool that searches for corrupt files on Android devices after clean flash, is there something similar available for WinMo?
Here is the thread I am talking about:
http://www.xda-developers.com/android/fixflash-rom-flash-verify-and-repair-tool/
screen doesn't respond to touch
I just started having this issue today. I have used darkstones most recent build from the 18th. it has worked perfectly till today. I use energy roms. i just installed a older rom today still have the same problem. this problem appears weither in droid or winmo. All the hard keys still function and the phone can receive calls. Thanks for any help you may be to lend.
my phone just froze again.
All I did was take it out of my pocket and unlock screen, and there it is: FREEZEEEEEEEEEEEEEEEEE
Funny thing is that Android doesn't freeze for me... it crashes sometimes, but never freezes. It is only WinMo that freezes on me or doesn't boot. Android always boots.
I really wish the NAND was accessible so I could flash Android to NAND and forget about WinMo
kml.krk said:
I really wish the NAND was accessible so I could flash Android to NAND and forget about WinMo
Click to expand...
Click to collapse
you, me and 17,000+ HD2 owners are all wishing for that exact thing
Your issue with the freezing/rebooting is stumping me too. You've flashed different ROM's, including stock, done hard resets, checked the battery pins, reformatted the SD card and even tried running the phone without the SD card inserted...do I have all that right? The fact that it doesn't show the symptoms when running Android just makes it that much more mysterious. I'd say it all points to a hardware issue, but if it doesn't act that way when you're in Android, that (probably) shoots that theory out of the water. But, at the same time, running task 29 and reflashing different ROM's should also have eliminated any possible software-based causes, so....
the only thing that comes to my mind is micro SIM card. I did an upgrade on my ATT account to get iPhone (traded for HD2) and those fu...ers at ATT wouldn't let me keep my regular sized SIM card. I had to use my old SIM card and cut it's inside to place micro sim in it. I used a regular sied SIM to hold micro SIM in place.
I don't think however that this is a problem because I believe my phone froze few times before I did that SIM card swap besides, I have no issues with phone calls or reception both in Android or WinMo.
I am clueless at this point.
I just got another Android version and will try it to see how it works. If I have any problems I will try using my wive's SIM card to see if it helps with freezing and WinMo booting.
KML
EDIT: ANDROID just rebooted itself. 2 minutes after clean installation. geee, I am leaning towards Hardware being the issue.
What I did is:
1. open browser
2. go to google
3. search for speedtest
4. open speedtest.net
and Android rebooted itself and now my phone can't go past Tmobile bootloader logo (pink square with 'stick together' letters)
I will put different SIM inside now and try everything again
kml.krk said:
the only thing that comes to my mind is micro SIM card. I did an upgrade on my ATT account to get iPhone (traded for HD2) and those fu...ers at ATT wouldn't let me keep my regular sized SIM card. I had to use my old SIM card and cut it's inside to place micro sim in it. I used a regular sied SIM to hold micro SIM in place.
I don't think however that this is a problem because I believe my phone froze few times before I did that SIM card swap besides, I have no issues with phone calls or reception both in Android or WinMo.
I am clueless at this point.
I just got another Android version and will try it to see how it works. If I have any problems I will try using my wive's SIM card to see if it helps with freezing and WinMo booting.
KML
Click to expand...
Click to collapse
Good call, that's about the only other thing to try. However....have you tried running WM with sense disabled, to see if it still has the freezing/rebooting issues? That might at least narrow the problem down to something sense-related (which is easily the most common cause of any software-related issue on this phone)
sirphunkee said:
Good call, that's about the only other thing to try. However....have you tried running WM with sense disabled, to see if it still has the freezing/rebooting issues? That might at least narrow the problem down to something sense-related (which is easily the most common cause of any software-related issue on this phone)
Click to expand...
Click to collapse
I have NOT tried that but I will. The problem is that I often can't get past bootloader logo...
I modified my post above so please read it (I mentioned Android crashing)
thanks for all your suggestions
I just tried different SIM card. Phone booted fine to WinMo, and froze as soon as I clicked on Messaging tab in sense.
I will try to disable Sense for now.
I disabled Sense, rebooted WinMo launched Android repeated operation of trying to get to speedtest. Site launched, but phone rebooted after a while.
I am getting to conclusion that some software including flash causes my phone to reboot and then I can't get it to boot again..
Right now my phone is stuck again on bootloader. I already tried rebooting twice.
What I noticed is that every time my phone freezes it gets a little warmer in the lower left corner
What hardware is located in that area?
I've noticed my N1 would reboot randomly since a couple weeks ago. It's gotten progressively worse and not reboots at least once per hour.
- I've uninstalled any apps that were installed within the past 2 weeks.
- Original OTA T-Mobile Rom (non-rooted)
- Just use 3g(no wifi)
- Tried uninstalling other apps that maintain connection state.
- Shut down running services to a minimum.
It seems like others are having issues as well.
google.com/support/forum/p/Google+Mobile/thread?tid=3f6f936e159bccc2&hl=en&fid=3f6f936e159bccc20004aacd32fa9189
Anyone here having issues too?
no issues here, same OTA as you.
have you tried giving her a factory data reset?
I have also started getting this problem. I have done a factory data reset and the problem still persist. I tried swapping back the original sd card and no dice. I wonder if my ram is just going bad. I had that problem with my first N1. This would be my third N1 and it's now out of warranty so I'm boned.
It might just be a coincidence, but this has been happening since the new market rolled out to my phone. The market would force close a lot. This happened even after the reset and uninstalling the market update and letting it reinstall.
I'm running stock 2.3.4 not rooted on t-mobile.
Same issue here. It is very random. I have wiped till the phones raw with no luck.
Sent from my Nexus One using XDA Premium App
I am having the same issue. I am rooted running cm7. The problem started about 2 weeks ago and while it has not been getting worse and the phone is still useable, it is definitely really annoying. I have wiped the phone but not the SD card and the problem persists. Will probably try going back to stock and unrooting but that doesn't seem like that's going to help at all. Seems to me that this must be a hardware thing. I called HTC and was told to hard reset and then add apps every few days to see if the problem recurs :-\
mrgilmorean said:
I am having the same issue. I am rooted running cm7. The problem started about 2 weeks ago and while it has not been getting worse and the phone is still useable, it is definitely really annoying. I have wiped the phone but not the SD card and the problem persists. Will probably try going back to stock and unrooting but that doesn't seem like that's going to help at all. Seems to me that this must be a hardware thing. I called HTC and was told to hard reset and then add apps every few days to see if the problem recurs :-\
Click to expand...
Click to collapse
Same here with cm7 nightly. switched to fit's latest build and have not had a reboot for over 24 hrs.
EDIT: I jinx myself, right after I hit submit on this post it rebooted on me.
i'm on cm 6.1.0 stable and have been getting this lately as well.
This just started for me two days ago as well. It will reboot itself at least ten times per day. I have read on another forum that getting a new sim card could be the solution so hopefully I will have time to make it to my Tmobile store tomorrow to get a new one.
After being plagued with random reboots for months. Even complete wipes, sdcard format, different rom n kernels didn't help.
Then I replaced the 16gb microsd with a new 4gb and have not had a single reboot since.
I suggest u all try it out.
Sent from my Nexus One using XDA App
Me too
Mine started doing this too! Weird. I don't think it's an SD card issue. That doesn't explain why so many people are experiencing it at once. I wonder if it's a Tmobile network issue of some kind.
My Nexus One just started with this same issue. You should definitely keep the SD card in mind when it comes to the rebooting but my card turned out to be fine.
The one thing that I WOULD test is: take your SIM card out for a while and see if it reboots. Mine stayed booted for the whole night while I was sleeping, and I just swapped SIM's earlier today. So far everything seems to be working just fine.
(Less important info)
I have had that SIM since 2006 so it is very likely that the older sims can cause issues at that point for the new phones. The only reason I even thought of it was the lack of any error messages in the last_kmesg debug.
Assuming our reboots all have the same cause, I don't think it's a SIM card issue. My SIM is pretty new (about 18 months) and I have been able to stop the constant rebooting by switching off both 3G and WiFi except when I need them. It's not the ideal solution because I now have to manually turn on WiFi or 3G whenever I want to do anything data-intensive but it beats having the phone rebooting all the time for me.
It has been almost 3 days now since I went to mostly 2G and it hasn't crashed/rebooted once yet (crossing fingers). Prior to this, the longest uptime was 22 hours.
if you format card use sdformatter, not phone
wipe system also
I got my new SiM card midday today and there have been no more reboots since. I have been using the same SIM card since 2007ish and the T-Mobile rep said he could tell in his computer system after he looked up my phone number, it showed on his screen (the new one looks identical physically). He said it was an old 2G card, and gave me a card he called a 3G card - he said they've only been giving them out and coming with new phones for the last six months or so. I don't know how much truth there is to that salesman's explanation but that's what he said. I'll report back in a few days if my reboot problem is truly solved or not but so far so good.
I too am having random reboots as others describe (since about 2 weeks)
I have been flashing CM7 nightlies consistently for months before (and since)
I have tried reformatting (SDFormatter) and re-partitioning (4096/0 then 2048/0) still no luck. Next tried retrograding to back to Nightly 161 (no luck) then to CM7 RC1 (gapps 20110613) still no luck.
T-Mobile (USA) SIM card is about 18 months old (same age as N1 purchased within 5 minutes of original release .... ok I'm a fanboy
Sure would like to figure this one out ........ this N1's gotta last until Nexus Prime's available
Could the recent reboot problem be related to google pushing the out the new market? That's when my problems started.
hahajoker said:
Could the recent reboot problem be related to google pushing the out the new market? That's when my problems started.
Click to expand...
Click to collapse
I uninstalled, then Titanium Backup "froze," the Market Update(r) since the reboots started. No improved results, but I will try it again (in case you are on to something).
By the way, here's a thread about the problem on Google Mobile Help. Might help if we banded together or at least are aware of each other's existence: http://www.google.com/support/forum...c2&hl=en&fid=3f6f936e159bccc20004ab2f835ecbbc
Ahh, glad to see a thread here as well.
As I mentioned on the Google Help thread, here's what we're seeing on bugreport, some of the time, on LAST KMSG:
[ 2503.447845] ARM9 has CRASHED
[ 2503.448303] smem: DIAG '[WCDMA] 04:23:42 FATAL: IST0 (mdsptask.c:00476) (1)
[ 2503.448333] '
[ 2503.449371]
[ 2503.449737] Restarting Linux version 2.6.35.7-59463-g52630a3 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Tue Mar 29 11:49:12 PDT 2011
[ 2503.449829]
The discussion here with an Android Framework engineer implies it might be radio issues:
http://groups.google.com/group/android-platform/browse_thread/thread/5551c0ebe7910777?pli=1
Last night I changed SIM card with an old fully-depleted prepard card and had 13 hours of no reboots (I am looking at Settings>About Phone>Status>Up Time for that data).
Plugged in the old SIM card this morning and am waiting for a reboot (none yet after 1:23:00).
Anyone notice the following commit on next CM7 nightly version?
"LGEStarRIL: Fix state trackers (android_frameworks_base)" ?
Comments say it deals with telephony. Any chance it is related to this issue?
Edit - went to Tmo and replaced my SIM card (I was told it was an "old one"). Let's see if that makes random reboots go away ! (almost 3 hours up time as I write this)
Ok, so typically my Google-fu is on point but I'm at a loss for finding relevant posts for my particular issue.
The issue is getting cellular data to work on the Galaxy S5 (Sprint edition), whilst using the Straight Talk carrier, while also on CM13 (snapshot). The phone was originally on Sprint, my wife just got the new Note 7 (lol - at time of the post is the day after the major announcement they'd be recalling all Note 7's), it was paid in full and as far as I can tell it is unlocked. I promptly put a new recovery on it and finished it off with CM.
I'm gonna take a moment to say something irrelevant. Oh. My. God. has rooting/custom ROM/bootloading improved over the years. Maybe it's the fact I finally have a device that was popular enough to have a real big community that worked on it, or what, but everything went SO much smoother than any experiences I've had putting custom roms on devices (then again, the fact that my other devices were always Verizon phones or Chinese tablets probably has something to do with it too). The only hiccup was recompiling an updated executable through a *nix shell. Anyways, back to the point.
I have LTE data working on stock ROM (backed it up before flashing to CM). When I switch to CM, I get working voice/text, but without all the data stuffs. What I suspect the issue may be is that the CM release that works with my phone (k1tespr) is trying to find the Sprint data network and use it. Everything works the way it should on Stock, and I've reinstalled CM multiple times now after verifying that LTE/Voice/Text works on stock, but still running into this wall when I go to use CM.
Hopefully because of the popularity of this device, and the popularity of Straight Talk BYOP's, someone figured this out!
Side Note: In the CM Cell data settings, when I go to "Select Carrier" at the bottom, it errors out, briefly rebooting the cell data settings. The error is "com.android.phone has stopped working". Looks/feels like a CM bug.
Hi,
I'm using an Oneplus 2 since 2015. About 6 months ago or so, I started to work with nicesoni_ash's unofficial Resurrection Remix ROM. (I had a version from july, 5.8.3) I loved it since the beginning but since two weeks, my simcard started showing problems. I had network drops every so often, but I could live with that. But now my whole simcard fails and everytime I grab my phone, I have to enter my PIN before I can use my fingerprint scanner. The phone has to search for a network which can take up to 5 minutes and when it finally has a connection, it drops whenever I try to make a call or something. All in all, it's horrible.
I've tried to flash OOS3.5.8., tried to update to a newer ROM (5.8.4), tried to update to the newest ROM and my latest attempt has been to flash a completely different ROM, Cosmic OS2.1. But even with my newest ROM, my simcard fails every. single. time.
The OP2 is a duosim phone, so i have a second sim running to check whether it was my simcard. The second one has less problems, but I almost never use that one. But even then, it fails every so often.
Do any of you know what could be the problem? I really can't figure it out anymore...
Thanks in advance!
Sounds like a Hardware failure to me... did you try both SIM slots? Otherwise search google for how to clean your internal sim pins/ try to add some layers (like 1 or 2) of tape to the sim (obviously not to the side where the connectors are) so there is a bit more pressure to the pins (= better contact between sim/pins)
(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.