Related
hello, not a noob for installing stuff just reporting some issues im having with this rom.
So currently the install went fine on the focus (ATT device running on Tmobile). the device is rebooting at random times, i would watch it flash the goodbye screen wait for a few seconds then the samsung screen comes on. Another thing is my connection is reporting to be on the E (Edge connection i guess) even though im rated for 3G with tmobile but at the time i just recently turned on my data so maybe when my new pay period kicks in that would change so that ones iffy. Other than that the rom seems to be running fine.
Until your area gets a network upgrade on TMobile's 1900Mhz band, you are going to see 2G.
As far as the reboots, I have 3 focus's running this Rom on Straighttalk. NO reboots.
wildbilll said:
Until your area gets a network upgrade on TMobile's 1900Mhz band, you are going to see 2G.
As far as the reboots, I have 3 focus's running this Rom on Straighttalk. NO reboots.
Click to expand...
Click to collapse
i know i get 3g before cause my father turned off the data plan when i wasn't working (and before i flashed the rom incase anyone asked), like i said i won't know until a couple of weeks as theres alot of extenuating circumstances which i can pin on Tmobile (my voicemail was kinda jacked up when i first joined).
Yea the reboot was just weird, i would just take it out of my pocket and i would noticed all of my pass tasks were missing even when i wasn't running anything on the background still does it, then last night i was on my computer look over to the right to my phone and it was restarting by itself . Also before i flashed, i had the same issue but not too frequently maybe once per 2 months.
ancienttyrael said:
i know i get 3g before cause my father turned off the data plan when i wasn't working (and before i flashed the rom incase anyone asked), like i said i won't know until a couple of weeks as theres alot of extenuating circumstances which i can pin on Tmobile (my voicemail was kinda jacked up when i first joined).
Yea the reboot was just weird, i would just take it out of my pocket and i would noticed all of my pass tasks were missing even when i wasn't running anything on the background still does it, then last night i was on my computer look over to the right to my phone and it was restarting by itself . Also before i flashed, i had the same issue but not too frequently maybe once per 2 months.
Click to expand...
Click to collapse
I had similar issues when I was on T-Mobile about 6 months ago, but I am not sure but I don't think your issues are because of T-Mobile, try a reflash.
ancienttyrael said:
hello, not a noob for installing stuff just reporting some issues im having with this rom.
So currently the install went fine on the focus (ATT device running on Tmobile). the device is rebooting at random times, i would watch it flash the goodbye screen wait for a few seconds then the samsung screen comes on. Another thing is my connection is reporting to be on the E (Edge connection i guess) even though im rated for 3G with tmobile but at the time i just recently turned on my data so maybe when my new pay period kicks in that would change so that ones iffy. Other than that the rom seems to be running fine.
Click to expand...
Click to collapse
do you clean storage after flash? i had a similar problem when i flashed with a novin´s custom and it was because i didn't clean it. with the dynamic rom i haven´t had any problem is for me the best rom ever created to the foucs
TrashSlash said:
do you clean storage after flash? i had a similar problem when i flashed with a novin´s custom and it was because i didn't clean it. with the dynamic rom i haven´t had any problem is for me the best rom ever created to the foucs
Click to expand...
Click to collapse
i cleaned before and after but heck reflashing helps too, i'll give that a shot tonight. Yea this rom is awesome, makes my focus still look shiny new
Here are the bugs I found:
1. The Clock Hub seems to flash every other time I look at it, as if it was flickering and loading up just then, not smooth.
2. The Clock Hub's code needs to be fixed to show AM and PM properly when the hour is 12. 12AM is shown as 12PM and the other way around too. Soon as it hits 1PM or 1AM, it's ok.
3. XBox avatar wakes up on the wrong side after shaking him down and he tries to pull the screen to the side. Shake your avatar, make him fall down, watch him get up pissed and pull the screen to a side. On the older stock rom, he pulled it correctly from left to right. In this ROM and the Tango ROM I got from here - he pulls it wrongly from right to left.
4. When I connected the phone to the computer, it detected it as a Samsung Omnia 7, instead of a Focus.
5. The image in Zune is a generic Windows Phone image, not the Samsung Focus as it used to be shown before.
6. When there's a phonecall, earlier it used to say "slide up to answer", why not anymore?
7. No charging sound/vibration when plugged in.
One request:
Can anyone find the original image from the stock rom from the 7 album, which had the person crossing their leg to form a 4, instead of the Mango image that has the latch with the 4 over it?
bugs
Testware said:
Here are the bugs I found:
1. The Clock Hub seems to flash every other time I look at it, as if it was flickering and loading up just then, not smooth.
2. The Clock Hub's code needs to be fixed to show AM and PM properly when the hour is 12. 12AM is shown as 12PM and the other way around too. Soon as it hits 1PM or 1AM, it's ok.
3. XBox avatar wakes up on the wrong side after shaking him down and he tries to pull the screen to the side. Shake your avatar, make him fall down, watch him get up pissed and pull the screen to a side. On the older stock rom, he pulled it correctly from left to right. In this ROM and the Tango ROM I got from here - he pulls it wrongly from right to left.
4. When I connected the phone to the computer, it detected it as a Samsung Omnia 7, instead of a Focus.
5. The image in Zune is a generic Windows Phone image, not the Samsung Focus as it used to be shown before.
6. When there's a phonecall, earlier it used to say "slide up to answer", why not anymore?
7. No charging sound/vibration when plugged in.
One request:
Can anyone find the original image from the stock rom from the 7 album, which had the person crossing their leg to form a 4, instead of the Mango image that has the latch with the 4 over it?
Click to expand...
Click to collapse
I found that the network profile does not work. The voice search does not work, also when u have a custom SMS tone it will not silence and also it will play when u are talking on the phone, and if you get more than one text it will play the sound for each sound all at once.
ancienttyrael said:
hello, not a noob for installing stuff just reporting some issues im having with this rom.
So currently the install went fine on the focus (ATT device running on Tmobile). the device is rebooting at random times, i would watch it flash the goodbye screen wait for a few seconds then the samsung screen comes on. Another thing is my connection is reporting to be on the E (Edge connection i guess) even though im rated for 3G with tmobile but at the time i just recently turned on my data so maybe when my new pay period kicks in that would change so that ones iffy. Other than that the rom seems to be running fine.
Click to expand...
Click to collapse
Your phone probably has bad NAND sectors. Aside from getting a new phone the only thing you can try is getting a very large SD card and hope that most of the data gets written to the SD card instead of the NAND. This is a common problem with the Focus I have noticed.
Solidus74 said:
I found that the network profile does not work. The voice search does not work, also when u have a custom SMS tone it will not silence and also it will play when u are talking on the phone, and if you get more than one text it will play the sound for each sound all at once.
Click to expand...
Click to collapse
The Dynamics ROM uses a lot of Omnia 7 files as well as it's newer firmware which can cause problems, such as changing providers with the diagnosis app via the provxml trick. The reason voice search doesn't work is because of ultrashot's SearchKeySettings package. If you want that to work you will have to use a ROKM that doesn't have that included.
hi guys. i tried getting an answer in the AICP 11 thread, but no one seems to be able to help. or maybe it was the wrong place to ask. a new thread is my last hope.
what i already wrote: "i first came to the conclusion, that i must face a hardware issue with my phone randomly shutting down and settings randomly reset / apps back to default. but in the meanwhile, after searching this and other threads, I've found quite some people having the same issues, but couldn't figure out, whether there is a solution or not. just couldn't find helpful answers to their issues. i switched to banksgapps, did lots of wipes an reinstalls, i even tried the 7.0 PA with the modded opengapps, but the problem keeps coming up. sometimes not for a week, sometimes several times a day. logcat wasn't of any help either, as it doesn't show logs before the reboot (or does it and I'm just too stupid to find it?)
i really love this rom and knew before, that I probably had to live with some bugs, but now it's just getting too unreliable."
my last hope was an incompatible recovery, so i updated to TWRP 3.0.2.0 and wiped and flashed everything again. AICP 11 with banksapps. no backups recovered or anything, just to be sure i really have a clean system.
but yesterday the phone shut down in the middle of something and I couldn't get it running again for 5 restarts.
i noticed, that the battery had shown 36% before the shutdown and 6% after i finally managed to get it to stay on.
i'd assume a battery defect, but first of all, the battery is just a month old and worked perfectly fine so far. and, secondly, a battery problem wouldn't resolve in settings being gone (like WiFi settings, font sizes, AICP settings, bluetooth connections, display settings, audio settings).
Anyone got any idea what on earth could cause this?
Or at least anyone else having that problem and having pointed out any pattern, when this happens?
our phones isn't surely a Windows system but it doesn't mean that if it shuts down unexpectedly it will not loose any settings.
What battery are you using? If a Jiayu one it is repeated that although new, a lot of batteries after the first release are defective and have problems of knowing if they are charged or not. They loose it's capacity. So many of us trust only the KonPson ones.
So you made clear actually you use a "clear" system without restoring backups but what about other settings inside the rom. I think there was a case that a user found a defect in the power button after trying a lot of things.
Think about it. Unfortunately under "a hardware problem" could be a defective SIM card, a SD card, or even the internal Ram of the phone ?
Perhaps you could try RC4 version for our phone, or even XTreme Rom, or the original KK, for a few days...
Best luck ?
Στάλθηκε από το s3 μου χρησιμοποιώντας Tapatalk
gorillaz_gr said:
our phones isn't surely a Windows system but it doesn't mean that if it shuts down unexpectedly it will not loose any settings.
What battery are you using? If a Jiayu one it is repeated that although new, a lot of batteries after the first release are defective and have problems of knowing if they are charged or not. They loose it's capacity. So many of us trust only the KonPson ones.
So you made clear actually you use a "clear" system without restoring backups but what about other settings inside the rom. I think there was a case that a user found a defect in the power button after trying a lot of things.
Think about it. Unfortunately under "a hardware problem" could be a defective SIM card, a SD card, or even the internal Ram of the phone
Perhaps you could try RC4 version for our phone, or even XTreme Rom, or the original KK, for a few days...
Best luck
Στάλθηκε από το s3 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I already have a Konpson battery, which was replaced by Jiayu, as a new "original" one didn't work properly (I'm glad the first original one didn't explode, as it really began to physically expand). As I had so many issues with the two batteries before, I tend to believe I'd recognize a battery defect by now.
About other settings in the ROM: as I used AICP 11 as well as AOSPA 7 and had the problem with both, I don't think any of the settings match at all. I don't even think I had any setting in AOSPA identical to AICP.
And my power button has been replaced by Jiayu a month ago as well, as I broke the connection cable between power button and mainboard while changing the (defective) sideboard myself.
Thing is, though, I have read of at least 2 other people facing the same problems, which is why I changed from assuming to have a hardware problem back to the software bug conclusion.
well then try an older ROM.
Perhaps the KK.
Στάλθηκε από το s3 μου χρησιμοποιώντας Tapatalk
gorillaz_gr said:
well then try an older ROM.
Perhaps the KK.
Στάλθηκε από το s3 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
what for?
i won't ever be happy with KK again. it's like using win xp nowadays. why should i?
even if i don't have this problem then, i wouldn't use the phone anymore. i'd be stuck with safety and compatibility issues.
it wouldn't help neither me nor anyone else..
i'd like to find out what the bug is. i can't do that by just avoiding it.
it was just a proposal to go a step back so that you can perhaps easily discover if it's a hardware problem or something with software. If with KK there is no problem then you know what you are looking for. Something in newer RoMs mess with your device.
Στάλθηκε από το s3 μου χρησιμοποιώντας Tapatalk
hm. maybe you're right. don't have any other choices.
still. if it really is the hardware, i will buy a new phone, and if it isn't, but nobody can help me, i will buy a new phone as well...
just hoped someone had any more ideas.
will keep this post updated when I'm back to KK... yay :/
Ive had the same issues. But only in mm roms. To me it restarts when I toggle airplane mode or when I toggle something that has anything to do with the modem. After the restart, developer settings and recent apps disappears and the quick settings in aospa mm also disappear. In LP roms I dont encounter any of these problems though. Up to now I havent found any fixes. Im currently using cm 13 mm, I just avoid toggling airplane mode.
dirtydime said:
Ive had the same issues. But only in mm roms. To me it restarts when I toggle airplane mode or when I toggle something that has anything to do with the modem. After the restart, developer settings and recent apps disappears and the quick settings in aospa mm also disappear. In LP roms I dont encounter any of these problems though. Up to now I havent found any fixes. Im currently using cm 13 mm, I just avoid toggling airplane mode.
Click to expand...
Click to collapse
it's got nothing to do with toggling anything in my case. it keeps happening for example when i type something in a messenger or while i'm in the middle of any game. no setting changes whatsoever. and, as i said, android m as well as andoid n. strange..
This happens only when I install any custom rom...the phone works fine with x720 5.8.018s version...anything apart from that device will shut down every 2-3 minutes ...very strange behaviour ...any one has any idea ?
any custom rom , android 6 or 7 , AOSP or stock based, it will boot fine and after initial setup , it will work for 3-4 minutes and then suddenly device shuts down. .. when i boot it up again , same thing happens, in one minute shuts down.
if i flash 5.8.018s stock rom , everything works fine....and it doesnt shut down...
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
marik1 said:
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
Click to expand...
Click to collapse
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Manan79 said:
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Click to expand...
Click to collapse
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Manan79 said:
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Click to expand...
Click to collapse
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
Click to expand...
Click to collapse
On my equipment too !!
Andresdsr said:
On my equipment too !!
Click to expand...
Click to collapse
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
mchlbenner said:
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Andresdsr said:
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Click to expand...
Click to collapse
Does anyone completely solved the shutting down issue on x720? I remember the same issue with the stock rom when i was getting the phone (5.8.018). but this rom could have been a shop rom, cant remember.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Click to expand...
Click to collapse
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
sk8223 said:
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
Click to expand...
Click to collapse
Thanks for the information.
Could be possible... If I'm shaking the phone like a cocktail-mixer, it feels something loose inside it and this could be the battery of course which could be not fixed correctly. But I am sure, that this issue has also something to do what is happening on the phone currently. Sometimes I am going to bed and the phone does not move for 8hrs, it simply lays on the table. In the morning, it is shutted down. Need to hold the power button for about 10sec to restart the phone (usually hold 2sec to power on). Sometimes (not really often) it warm-starts automatically.
I think this could be also a memory issue or internal storage. Yesterday I was playing a game (Bowling by Jason Belmonte) and after 3min, the phone hung up, display remains on, no reaction on pressing the hardware buttons, waiting 5min... nothing happens. So I pressed the power button 10sec, phone seems to reboot normally, but it take a bit more time in my oppinion. Now after entering the pin, some phone configurations were resetted to default, but not all. Playing this came, it sometimes happened, that the phone switches off (with one vibration). Rebooting with a 10sec press and it runs again normally. This time phone hung up and some configurations were resetted to default. WTF?
Today I have played Hmmsim 2. Phone hung up again, pressing the power button 10sec, phone begins to reboot, but rebooting never finished (waiting for about 1-2hrs). Long Press power button (10sec) to try to reboot again - same behaviour, never ending ROM loading screen. Wiped to factory via TWRP and the phone reboots again, but all configurations lost, like freshly installed rom. OK, whatever, using the google backup for apps and so on... when installing the apps in the background, the phone reboots about 3-4 times, app installations not finished. Cancelled and shutting the phone down to TWRP, where I am now...
What I will try to say is, that whenever the storage or memory is used to much or something like that, the phone begins with that behaviour.
And now I am thining about what to try next. I think I will try to flash the stock recovery via TOOL ALL IN ONE then flashing a stock rom like 5.9.023S.
I am still not sure of a hardware issue...
peed_neslo said:
I am still not sure of a hardware issue...
Click to expand...
Click to collapse
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
sk8223 said:
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
Click to expand...
Click to collapse
Thank you very much!
I am sure that the phone was doing the same on stock rom, but maybe fewer times. I have flashed a stock based rom now (Turbos mini 5.9.023s) and the issue still exists, but now the phone reboots normally more often than going into edl mode (emergency mode). I have found an old thread here on XDA and the issues described there sounds nearly the same. Finally the user in this thread also had hardware issue.
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
peed_neslo said:
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
Click to expand...
Click to collapse
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
Click to expand...
Click to collapse
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Admittedly I'm not sure at all if this issue was already present after starting the phone for the first time. One of the first things I have done during the initial setup wizard was using the integrated data transfer app by LeEco (scanning a QR code with the old Xperia Z, downloading app to transfer data to the x720). This app establishes a Wifi direct connection between both phones to transfer the data like apps and other stuff. This transfer process takes at least 6-7 hours and during that process I am sure that the phone was not rebooting a single time. Maybe a specific app or background process of an app causes this irregular rebootings. I have not testet this. I have installed the most common of my apps also using different custom ROMs later.
On the current ROM (Turbos mini 5.19.023s) I have now looked into the last_kmsg.log file severel times after the phone was hard-rebooting (not to emergency mode - the phone is switching down to emergence mode really rarely since I have flashed the stock based ROM) to debug for a kernel problem and the power off reason seems to be ""Triggered from PS_HOLD (PS_HOLD/MSM controlled shutdown)". In the log file I could also find some "kernel panic" entries. So I have a little gleam of hope that the issue is not a hardware problem. I have to test a bit more with the stock recovery/ROMto gain a better knowledge of the issue. I think I will post this into the ROM topic to ask a developer.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Finally - I got it working without any problems now!
Happily it seems to be not a hardware issue. I have flashed the Grossoshop ROM and Recovery via a provided .bat file. This .bat file has flashed the recovery first via fastboot, then the ROM via fastboot. This Grossoshop ROM was based on 5.8.018s I think. Then I have updated TWRP Recovery to the latest version via TWRP itself (flashed the new image). Then I have flashed Mauro's 2.2 (which is based on 5.9.023s) and it is running great! Super performance, no extrem battery drain, no reboots, all is working (except the chinese design downloads as I cannot create a Leeco account from Germany). But now I'm satisfied. :good::laugh:
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
Thanks!
Click to expand...
Click to collapse
My x720 has done the same to me a couple of times now, Vibrates once and turns off and I have to hold the power button for a few seconds longer to turn it back on again which is odd.
The battery was charged over 50% % 70% at the times it happened and I wasn't even using the phone, It was just sat on the table in front of me.
I didn't have any problems at all until a few days ago when it first shut down.
I'm using Oreo - AICP 13.1 from here - https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
The problem now is I don't know where to start troubleshooting When I get time I am planning on a clean wipe and fresh install of AICP again to see if that solves the problem
When using this ROM does your phone heat up a lot.
Sent from my LEX727 using xda premium
Did you manage to fix the problem somehow?
The last update is horrible! I am experiencing the following issues. I have been a long time user due of OnePlus phones due to the fast software and generally being bloat-free. Now they have published software with major problems and the stuff with forcing the "Red Cable Club" functionality to some users is just horrible. What is this crap? Why can't their engineers spot these problems a power users can spot in a few days of usage?
I hope they will fix these issues fast, or I will have to look for another phone. Maybe the Google Pixels are fast and bloat-free?
Random FPS drop
The FPS of the phone can randomly drop to about 10. Happens every few days and a reboot fixes this.
Wifi problems
5 GHz wifi seems not to be working properly. Random connection drops.
Proximity sensor always on
Every few days (probably related to making calls) it happens that the proximity sensor still thinks its in a call. It will turn of the screen if my finger passes over the sensor, regardless of what I am doing on the phone.
Vibrating notifications in silent mode
For some notifications, the phone has started to vibrate. Even though I always have the switch in the silent mode setting.
Hi.
- The "Red Cable Club" seems to be only for Indian users, I think you cand disable that app using ADB.
- The performance problems are there since the first beta of 10, with the passing of the updates the performance has been improving but it's still far from Pie (This isn't something specific of this device, even users of the 7 series suffer this problem).
- With 10 and 10.3.0 I had problems with the 5 GHz connection, but it's working fine with 10.3.1.
- In relation to the last two problems, I've never had them.
No problems here. Make sure you have updated to 10.3.1
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
xRogerxC said:
No problems here. Make sure you have updated to 10.3.1
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse
Fairly new to rooting (again) - I have a OPO6T rooted, with Magisk and TWRP installed running on 10.3.0. Can you point me to how I can update to 10.3.1 please?
My data speeds have been ATROCIOUS since unlocking Tmobile and rooting.
-horrible data speeds on network
-spotty wifi connections
-unable to use data during phone calls while on network (wifi is ok)
-constant taking screenshots (never had this before, buttons havent moved, what changed?)
I started with 10.3.0 and I am now on 10.3.1 and having the same issues.
And, I have another phone (Honor 6x), also with Tmobile and the data speed is much better than the OP6t.
Help. Phone data is almost unbearable anymore.
5aq1b said:
Fairly new to rooting (again) - I have a OPO6T rooted, with Magisk and TWRP installed running on 10.3.0. Can you point me to how I can update to 10.3.1 please?
Click to expand...
Click to collapse
Hello buddy, i followed those steps..
1. Download 10.3.1 and copy to the main folder of your phone.
2. Download latest @mauronofrio 's twrp zip (3.3.1-31) and copy it somewhere into your phone...
3 Delete all your security stuff such as fingerprints, passwords, etc...
4. Open Magisk and untick all your modules, delete stuff like substratum, reboot...
5. Launch your 10.3.1 update via local, when finished don't reboot...
6. Open Magisk, tap modules, tap plus icon ( + ), select @mauronofrio 's twrp zip, let it flash (yes like a module), don't reboot...
7. Be sure you're connected to the internet, be in the main menu of Magisk, tap install, again install and install into the inactive slot (after OTA).
8. Reboot your device, let it sit for a while and re-set all your stuff.
9. Done, enjoy your new system...
Cheers
Dadditz said:
Hello buddy, i followed those steps..
1. Download 10.3.1 and copy to the main folder of your phone.
2. Download latest @mauronofrio 's twrp zip (3.3.1-31) and copy it somewhere into your phone...
3 Delete all your security stuff such as fingerprints, passwords, etc...
4. Open Magisk and untick all your modules, delete stuff like substratum, reboot...
5. Launch your 10.3.1 update via local, when finished don't reboot...
6. Open Magisk, tap modules, tap plus icon ( + ), select @mauronofrio 's twrp zip, let it flash (yes like a module), don't reboot...
7. Be sure you're connected to the internet, be in the main menu of Magisk, tap install, again install and install into the inactive slot (after OTA).
8. Reboot your device, let it sit for a while and re-set all your stuff.
9. Done, enjoy your new system...
Cheers
Click to expand...
Click to collapse
Thanks for the reply bud. Silly question time -
1. Where am I downloading 10.3.1 from? I can only see 10.3.0 on the Official Oneplus site.
2. Does the above wipe all my apps and data?
tuomast said:
The last update is horrible! I am experiencing the following issues. I have been a long time user due of OnePlus phones due to the fast software and generally being bloat-free. Now they have published software with major problems and the stuff with forcing the "Red Cable Club" functionality to some users is just horrible. What is this crap? Why can't their engineers spot these problems a power users can spot in a few days of usage?
I hope they will fix these issues fast, or I will have to look for another phone. Maybe the Google Pixels are fast and bloat-free?
Random FPS drop
The FPS of the phone can randomly drop to about 10. Happens every few days and a reboot fixes this.
Wifi problems
5 GHz wifi seems not to be working properly. Random connection drops.
Proximity sensor always on
Every few days (probably related to making calls) it happens that the proximity sensor still thinks its in a call. It will turn of the screen if my finger passes over the sensor, regardless of what I am doing on the phone.
Vibrating notifications in silent mode
For some notifications, the phone has started to vibrate. Even though I always have the switch in the silent mode setting.
Click to expand...
Click to collapse
Also, "Handling Theme" notification seems to pop-up for no apparent reason. Not sure if this process drains battery.
5aq1b said:
Thanks for the reply bud. Silly question time -
1. Where am I downloading 10.3.1 from? I can only see 10.3.0 on the Official Oneplus site.
2. Does the above wipe all my apps and data?
Click to expand...
Click to collapse
You're right, it's not on the official website, at least I didn't bother doing a thorough search ...
I got it here on XDA in the global builds repo thread ... HERE, signed flashable zips...
and no don't worry, you won't lose your apps and data.
Have a good day
P.S .: it is always recommended to make backups in case something goes wrong ...
moodloid said:
Also, "Handling Theme" notification seems to pop-up for no apparent reason. Not sure if this process drains battery.
Click to expand...
Click to collapse
Yes, I also noticed this thing, sometimes it seems to appear for no reason ...
Yeah, I am also experiencing this random "handling theme" notification. I hope they fix this soon!
tuomast said:
Yeah, I am also experiencing this random "handling theme" notification. I hope they fix this soon!
Click to expand...
Click to collapse
It's not random, it appears briefly each time you install or update an app. I don't see why people are so upset by this thing that lasts 5 secondes.
Face unlock has so far failed to work on android 10 for me - I can setup the face, but unlock never works.
Did a full fresh install - not an upgrade.
Striatum_bdr said:
It's not random, it appears briefly each time you install or update an app. I don't see why people are so upset by this thing that lasts 5 secondes.
Click to expand...
Click to collapse
People are upset because they have published horrible software with no quality control. Updates, which make performance worse, not better.
tuomast said:
People are upset because they have published horrible software with no quality control. Updates, which make performance worse, not better.
Click to expand...
Click to collapse
Ranting here about OnePlus has strictly no effect, is totally useless. If you're upset enough consider changing your phone instead. Believe me the are many more serious things in life than being that upset for minor things.... Take a breath.
Plus the Fact that OnePlus despite all it's fault, is one of the Fastest OEM's to push out OTA's after Pixel and Essential. They are also the one that provide the longest support (3 years for the OP3 & 3T) and have arguably the best Software Skin, even better than Stock Android on Pixels. Their phones remain fast and snappy in the long run and did I mention they are almost half the Price of Modern Flagships? For me, OOS is alone enough to buy OnePlus phones. Now, regarding your "issues", OnePlus did push out a Hasty update but to their Credit they have been trying to fix it. If you are not satisfied with the Quality then you can either wait or as suggested previously, change your phone to either the 7 or 8 Series or another OEM altogether.
DarthVader said:
Plus the Fact that OnePlus despite all it's fault, is one of the Fastest OEM's to push out OTA's after Pixel and Essential. They are also the one that provide the longest support (3 years for the OP3 & 3T) and have arguably the best Software Skin, even better than Stock Android on Pixels. Their phones remain fast and snappy in the long run and did I mention they are almost half the Price of Modern Flagships? For me, OOS is alone enough to buy OnePlus phones. Now, regarding your "issues", OnePlus did push out a Hasty update but to their Credit they have been trying to fix it. If you are not satisfied with the Quality then you can either wait or as suggested previously, change your phone to either the 7 or 8 Series or another OEM altogether.
Click to expand...
Click to collapse
This ^^^ and yeah altho some ppl experience some problems... There's a whole lot of ppl that do not have a single problem at all... I'm one of them ?
(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.