Related
New sprint rom?? http://forum.ppcgeeks.com/showthread.php?t=10293&page=3
http://download.america.htc.com/RUU_...PL106_Ship.exe
It's been confirmed. That is the new official ROM for Sprint. It fixes the Bluetooth issues among others. No Rev. A or GPS of course, but that was expected.
question is, is this really "better" than the alltel rom that has been available for a long time already over at PPCgeeks...
The alltel rom fixed the BT and alarm problem as well. I'm excited to see that Sprint finally caught up, but I'm wondering if this is better than the setup I currently have.
Well I for one am happy and upset.. I would like to see REV A , as I need the faster upload speeds for sending big files from my 4gb micro sd.
I havent tried the Alltel rom, but the new sprint rom fixes the keyboard lag + wm6 responsiveness problems.
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
kmartburrito said:
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
Click to expand...
Click to collapse
i took the plunge yesterday, i skipped out on all the sprint customization and everything turned out ok....haven't tested bluetooth yet but everything you said seems to be on point...
kmartburrito said:
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
Click to expand...
Click to collapse
Just to clarify this is part. A hard reset will completely erase any carrier customizations there is absolutely no reason for installing extrom, hard resetting then skipping. Just start out with the hard reset, skip customizations and you'll be good to go.
Although there are still the other bugs with the update =)
Just installed it a while ago, skipped the sprint customizations, everything seems to be running good and actually noticeably quicker than before. New startup screen is cool too, no problems thus far =)
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Seems to only happen to some people though. I have had my phone on pretty much straight since the rom update.
there seems to be a major bluetooth issue where the BT just shuts off periodically.. Not sure how,but they found a way to make bluetooth even worse!
I can't carry on a conversation without BT shutting off on me.. (or use the gps without it shutting off/etc..)
-mark
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
GoodThings2Life said:
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
Click to expand...
Click to collapse
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
wsparvis said:
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
Click to expand...
Click to collapse
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
No, "most" users are not experiencing better results. I've been using this ROM with poor results, as have many others. Read this thread for many sad tales of woe:
http://forum.ppcgeeks.com/showthread.php?t=10302
Basically, the new ROM does fix a bunch of things, but breaks others, so I would not recommend installing this ROM.
1) Locks up when changing from Sprint to roaming. You can test this by manually switching from Sprint to roaming and back a few times, you WILL get a phone lockup.
2) BT turns off randomly for many users.
3) Turn on BT, let unit sit for a few minutes until it goes to sleep, turn unit back on, dpad no longer works. I have seen this myself many times.
Don't install this update --- use the Alltel ROM or wait for another update.
GoodThings2Life said:
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
Click to expand...
Click to collapse
1) You're incorrect in stating that most users have no problems, etc. Some do, some don't. Read the posts at ppcgeeks, pdaphonehome, BAW, hofo. I am not at all alone in having problems.
2) I downgraded 2 days ago, and my Mogul runs fine again - just exactly like it did for the 1st 3 months I had it. It's not my hardware! It's a bad ROM release.
Not everyone uses the phone in the same way at all. So of course some people will not see the same problems that others do.
If you never use Bluetooth and never roam, then this ROM will work for you. Otherwise, it will cause problems. For me, Bluetooth works much better in 2.09, and I rarely if ever see lockups as I have with 2.16. So, I'm going with 2.09 for now. The alarm problem IS fixed in 2.16 but I never use alarms on my phone so it's not an issue for me. Freezes when roaming ARE a problem.
cbunting said:
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Click to expand...
Click to collapse
is colonels rom built on the alltel core rom? if so it may be our best bet as of now.
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
Hi,
my i9305 behaves a bit strange recently, and I wonder if it's a hardware flaw or a software porblem
As you can see in my sig I'm up to date with OmniROM nightlies, and as my phone refuses to charge the battery properly (a problem with the usb jack I'd say) I think it may be both
Now, here's my problem: I'm trying to back up all my apps in order to move most of the stuff to my new mobile, but during backup it happens to reboot after a while.
I tried to make a logcat (attached), but honestly speaking I don't have a clue what to look for, as I'm no coder.
Can anyone take a look and maybe hint me to what may be the problem? I'm totally lost
husky69 said:
Hi,
my i9305 behaves a bit strange recently, and I wonder if it's a hardware flaw or a software porblem
As you can see in my sig I'm up to date with OmniROM nightlies, and as my phone refuses to charge the battery properly (a problem with the usb jack I'd say) I think it may be both
Now, here's my problem: I'm trying to back up all my apps in order to move most of the stuff to my new mobile, but during backup it happens to reboot after a while.
I tried to make a logcat (attached), but honestly speaking I don't have a clue what to look for, as I'm no coder.
Can anyone take a look and maybe hint me to what may be the problem? I'm totally lost
Click to expand...
Click to collapse
soft reboot (bootanimation) or hard reboot (back to bootloader)?
Since you're running a modified configuration (changed kernel) - no clue what's going on. I'm going to assume the problem is the modified kernel until you're actually running Omni as opposed to modified pseudo-Omni.
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.
(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.