Related
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app
Over all I'm very happy with MM on Z5 Compact. But I've got some issues with my Bluetooth since the update.
I've got a DVD800 in an Opel. Before the update it worked mostly. Once a month I had the issue, that I had to toggle bluetooth, because the connection ran into a bad state.
But since the update I've got regulary disconnects. Special here: I don't have to toggle Bluetooth on either site.. Only try to force a reconnect and mostly it works.
But on my 30 minute drive to work, it disconnects around every 2-15 minutes.
Did anyone discover such things?
Is it possible that some Battery Optimization -Feautres makes some problem here? energy saver (doze) is not active.
Have to add here:
I'm on:
- E5823_Customized CH_1298-7257_32.1.A.1.163_R2C with my 1298-1220 device
- Installed AndroPlus v20
- Installed TWRP 3 from xy.03.2016
- Installed SuperSu
Now I'm testing on
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016
I'm on Customized Nordic and I have not experienced any disconnects with my BT earphones (with phone in pants) nor with my BT speakers. Had MM since it was released on XDA. Doze active.
Yep. Here's a copy/paste from my post in the BIG Z5 Marshmallow thread:
I've been getting the same issue as you. Just now, I was playing through my bluetooth speakers and suddenly the sound completely cuts out. I go and try to toggle the volume up and down and no volume indicator shows up. After about half a minute to a minute the volume indicator appears and the sound comes back. Very strange.
Has anyone noticed a very long delay in bluetooth auto connecting? When my Z3c, when I enter my car, the bluetooth hooks up immediately, within 10 seconds of being in my car. With my Z5c it's a hit or a miss. Sometimes, it won't connect for up to 5 minutes and I'd have to go into my settings and manual connect.
Hopefully, the April update will work out all the kinks.
Click to expand...
Click to collapse
Yeah, I have a fitness tracker - a Basis Peak - that will not connect to the Z5C since the Marshmallow update. The phone can see the watch (and vice versa) but they just can establish a working connection.
Update for today: I didn't have a disconnect within the 20 minute drive. But have to monitor a few days further
Unfortunately I changed more than one thing. So I don't know which one changed the behaviour.
now with
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016 (not really think, thats comming from here... but I changed that too)
- And Battery Optimization disabled for (NOT DOZE)
Bluetooth-Sharing
Bluetooth-MIDI-Service (not really think, thats comming from here but...)
Anyone have an ETA for 6.01? Looks like that's the fix I'm going to need.
milesg said:
Anyone have an ETA for 6.01? Looks like that's the fix I'm going to need.
Click to expand...
Click to collapse
Probably first week of May.
youvedone said:
Update for today: I didn't have a disconnect within the 20 minute drive. But have to monitor a few days further
Unfortunately I changed more than one thing. So I don't know which one changed the behaviour.
now with
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016 (not really think, thats comming from here... but I changed that too)
- And Battery Optimization disabled for (NOT DOZE)
Bluetooth-Sharing
Bluetooth-MIDI-Service (not really think, thats comming from here but...)
Click to expand...
Click to collapse
Unfortunately it's better..... but not good at all... but I can reconnect any time, when it disconnects.
Hi all,
I have been experiencing issues with the notifications on my Stratos 3 for a couple of weeks. Very often there is a big delay from when I get the notifications on the phone to when the notifications are shown on the watch. Another problem is that I get the same notifications again on the watch some time after (even if the notifications are already gone on the phone). Also very often notifications stay on the watch after being cleared on the phone.
I have checked that Zepp app is not battery optimized and that it has access to notifications. Not sure if there is some other permission that needs to be granted which might have lost when changing from Amazfit to Zepp.
I didn't have any issues with amazfit app, I think this started when they changed the app to Zepp....
Anyone else encountered the same issues?
I'm having the same issues with Stratos 3.
However, I had them already with the amazfit app.
I'm using it with the Galaxy Note 10+. Also battery optimization is off and all other permissions given.
Notifications work normally in ultra mode!
Any help is highly appreciated.
Mmm then it could also be related to the 4.2.7 firmware update that I did recently.
I have enabled the phone anti-lost feature and I noticed that the watch is constantly loosing connection even if it is 10cm far from the phone.
My phone is a Moto One Action
kulaki0 said:
Mmm then it could also be related to the 4.2.7 firmware update that I did recently.
I have enabled the phone anti-lost feature and I noticed that the watch is constantly loosing connection even if it is 10cm far from the phone.
My phone is a Moto One Action
Click to expand...
Click to collapse
My first firmware was 4.2.6.0 and I had the problem already.
I read it was better with 4.2.5.0... but I don't really understand how to downgrade.
I have a Galaxy note 10+ Deactivating "find my mobile" didn't have any effect for me.
After updating to 4.2.8 I have the same issues with the notifications and lost connection frequency.
I will raise a bug on the Zepp app and hope it is looked at
Hey there,
I had the same problem, and Zepp was configured to be battery optimized...
I turned it off and now everything is fine !
arbaus said:
Hey there,
I had the same problem, and Zepp was configured to be battery optimized...
I turned it off and now everything is fine !
Click to expand...
Click to collapse
Hi! I have the same issue and I had battery optimization "ON" for Zepp, turned it off and..no result. I believe its either a bug on the firmware or some minor tweak required on the ROM( its a custom ROM, not stock). But with the Stratos 2, same phone, same ROM, no issues whatsoever...
Guys, massive improvement: tried with an older Zepp version (Amazfit 4.7.1) and even if I havent tested WhatsApp notifications all the others are super fast and I had zero connection lost warnings! Wish you all the best of luck!
Hi guys,
COuld you dump your firmware and upload?
The only way I could receive notifications properly was using Amazmod (sorry if you own an iPhone) and turning off everything related to graphics/images in notifications. They are some seconds late, but still usable though.
farrayoles said:
Guys, massive improvement: tried with an older Zepp version (Amazfit 4.7.1) and even if I havent tested WhatsApp notifications all the others are super fast and I had zero connection lost warnings! Wish you all the best of luck!
Click to expand...
Click to collapse
Dude, thanks a lot, the only thing I didn't tried, except for factory reset the phone, was an older version of the app. I could only find Amazfit Watch 2.7.2, but it's working flawlessly with it, watch is first Stratos
Hello Everyone,
Well to start, after update Sony Xperia 1 III (QX BC-52) to latest system update build number 61.1.A.9.128 I noticed the following couple of problems:
1) When I am in an area where the network coverage is weak, when the phone does not use 3g 4g but only the 2g network, it sometimes happens that the phone cannot make calls as if there is no signal, and also a message for a missed call arrives, or when I someone calls the phone starts ringing and stops after a second, as if someone just called me and hung up.
2) When the mobile data is turned on (wi-fi turned off) and after that it enters the following applications, there is a problem with the interruption of the internet.
1 Music player - play song with max volume level
2.Facebook - start video with sound on max volume level
3. Instagram - start video with sound on max volume level
4 Youtube - start video with sound on max volume level
5. Viber video call
As I wrote at the beginning, I noticed these bugs after the software update. I have been trying to solve this problem for a week in the following ways:
- software reinstallation via Xperia Companion,
- restoring to factory settings,
- resetting network settings, returning apn parameters to factory values,
- despite all that, I took a new sim card, but the problem was still not solved.
After a week of trying to solve this problem, last night I was able to see exactly how this problem occurs, that is, what needs to be done to make this bug appear, and also what needs to be done to prevent this bug from appearing and what the problem is let me know if I do things to fix this problem. This software bug was confirmed by a few more people after the latest system update on a couple of forums (xda developers and reddit xperia. I post this problem on this two sites and get answer.
If you need I can record video and show this bug?
All that needs to be done to detect this bug is the following:
Launch one of the apps I listed above and do the following:
Press the volume up button to the maximum volume level or press and hold once. After that, click a few more times, but you don't have to, and then reduce it by one click or a couple of clicks and repeat this several times. AFTER THAT THE 3G, 4G ICON DISAPPEARS FOR A SECOND, APPEARS AGAIN AND DISAPPEARS AGAIN AND SO MANY TIMES UNTIL WE REDUCE THE VOLUME TO A LITTLE MORE THAN HALF. AT THAT MOMENT WHEN THE 4G ICON DISAPPEARS, DATA TRANSMISSION IS TERMINATED AND THEN THE INTERNET DOESN'T WORK.
I NOTICED THIS PROBLEM FOR THE FIRST TIME WHEN I WAS TALKING ON VIBER ON A VIDEO CALL AND NOT KNOWING WHEN I VOLUME UP ALL THE WAY THE VIDEO CALL CUT OFF, AND THE SAME WHEN I WAS WATCHING A VIDEO ON YOUTUBE AND WHEN I VOLUME IT TO THE MAXIMUM VOLUME LEVEL IN A VERTICAL POSITION THE 4G ICON DISAPPEARS, AND IN A HORIZONTAL POSITION IT PUTS OUT THE MESSAGE AT THE BOTTOM OF THE SCREEN THERE IS NO INTERNET CONNECTION, AND AFTER A FEW SECONDS IT WRITES BACK ONLINE. THIS KIND OF NONSENSE AFFECTS THE USER EXPERIENCE A LOT. IMAGINE WHEN YOU ARE WATCHING A VIDEO ON YOUTUBE AND EVERY MOMENT YOUR MOBILE DATA CUT OFF AND DURING A VIDEO CONVERSATION ON VIBER, YOUR VIDEO IS INTERRUPTED. I NOTICED THESE COUPLE OF BUGS, FOUND IN WHICH SITUATIONS THEY APPEAR AND WHAT TO DO TO PREVENT THEM FROM OCCURRING, BUT IN TURNS, SOME OTHER PROBLEM ARISES.
IMAGINE WHEN YOU ARE WATCHING A VIDEO ON YOUTUBE AND EVERY MOMENT YOUR MOBILE DATA TURN OFF AND DURING A VIDEO CONVERSATION ON VIBER, YOUR VIDEO IS INTERRUPTED. I NOTICED THESE COUPLE OF BUGS, FOUND IN WHICH SITUATIONS THEY APPEAR AND WHAT TO DO TO PREVENT THEM FROM OCCURRING, BUT IN THIS CASE SOME OTHER PROBLEM ARISES. IF YOU SET THE VOLUME ON MAX LEVEL THIS BUG WILL TURN OFF YOUR MOBILE DATA EVERY SECOND, BUT IF YOU SET VOLUME LEVEL ON THE MIDDLE OR LITTLE HIGHER THIS BUG WILL BE GONE.
SONY XPERIA TEAM, I HAVE FOUND THIS BUG, AND RESEARCHED AND SHOW HOW IT AFFECTS THE USER EXPERIENCE, AND IT'S UP TO YOU TO FIX THIS PROBLEM AS SOON AS POSSIBLE. THE PHONE COSTS OVER 1000E AND I THINK IT IS UNACCEPTABLE THAT SUCH PROBLEMS ARE OCCURRING. OTHERWISE, I AM A LONG-TERM SONY USER SINCE THE AGE OF SONY ERICSSON. THANKS A LOT
This sounds like a flaw in RF shielding or power stability. The OS should have hacks to avoid triggering conditions of common defects - stuff like making sure variable digital clocks don't align with the radio signals and pulses of power consumption don't overlap to an overload.
If yours is uncommon you might need a warranty replacement.
My US model has a lot of weird radio, touchscreen, and fingerprint glitches that haven't been completely fixed in updates. Good luck.
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
evaokay said:
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
Click to expand...
Click to collapse
Im debating if I should go back to stock since Evolution Gsi aren't being updated. I may start building them
bountyman334 said:
Im debating if I should go back to stock since Evolution Gsi aren't being updated. I may start building them
Click to expand...
Click to collapse
Yes please Make a Evolution GSI for the Xperia 1 III
Ainz_Ooal_Gown said:
Yes please Make a Evolution GSI for the Xperia 1 III
Click to expand...
Click to collapse
There is one but it's not being maintained.
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
bountyman334 said:
There is one but it's not being maintained.
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
Click to expand...
Click to collapse
But I want it to updated daily. No choice but to builf
evaokay said:
XQ-BC72 61.1.A.9.219 have fixed mobile data bug
Click to expand...
Click to collapse
I've just wanted to ask about the new update all I have to do is to wait for the EEA customized
LaceeWearsPrada said:
I've just wanted to ask about the new update all I have to do is to wait for the EEA customized
Click to expand...
Click to collapse
Xperia 1 III: 61.1.A.9.219
This system software update features
Android security patch level: July 1st, 2022
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
bountyman334 said:
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
Click to expand...
Click to collapse
Which magisk you use ? I am on latest fw .219 and magisk 25.2 just works fine.
Pandemic said:
Which magisk you use ? I am on latest fw .219 and magisk 25.2 just works fine.
Click to expand...
Click to collapse
Yep Magisk 25.2 app and 25.2 (25200) Magisk install...just saw this and updated myself just to get the infinite Xperia Boot Animation
Ainz_Ooal_Gown said:
Yep Magisk 25.2 app and 25.2 (25200) Magisk install...just saw this and updated myself just to get the infinite Xperia Boot Animation
Click to expand...
Click to collapse
Patch your boot.img with magisk 25.2 i did it to and works fine
Pandemic said:
Patch your boot.img with magisk 25.2 i did it to and works fine
Click to expand...
Click to collapse
no your using stock kernel. I was using Sagami. now on evo11
bountyman334 said:
One thing with this latest version is that magisk doesn't play nice. I think Google got johnwu to give up the back door to his method. I mean that using the Kirisakura_Sagami_S_2.0 kernel will cause you to bootloop. Until u reflash using new flasher to save your data
Click to expand...
Click to collapse
Both statements are incorrect. There's no backdoor that magisk is using. Magisk requires bootloader unlock, there's no backdoor needed.
Kernel works also fine on latest firmware on my end.
After updating my Sony Xperia 1 III to the latest software version build number 61.1.A.9.219 all the problems or bugs that I wrote in this post that I published here on XDA developers are resolved. No more problems with mobile data, no more interruptions during phone calls. Sony team, thank you very much for solving these problems that existed in the previous version of the software in the shortest possible time. Thanks to all the people who gave their suggestions on how to solve the problems here.
Hi guys
i have the XQ-CQ54 model with android 12 and i'm experiencing a lot of crashes with Android Auto. Tried everything including factory reset. Problem appears both on USB connection and wireless and appears on all cars i've tried it on (about 4 this far of different brands and models).
Anyone else with this?
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
viper. said:
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
Click to expand...
Click to collapse
i've tried various versions of android auto, they all crash... but they don't on my Samsung S20FE with same Android OS version (12)
Latest thing i tried was making sure power management is off for both AA and Spotify. We'll see if that makes a difference...
Yet again s20fe is not new on the market ,i know what you are saying but i still feel bugs might need some time to be polished on 5 iv as they dont have same hardware .
You can try to test it in safe mode...tho i am not sure if android auto is disabled or not in safe mode
tried changing battery management settings for apps, i'll see if that makes a difference.
andost said:
tried changing battery management settings for apps, i'll see if that makes a difference.
Click to expand...
Click to collapse
nope, didn't... still crashes...
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
dhj1949er said:
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
Click to expand...
Click to collapse
yeah, it's just that the behaviour is the same both on wireless android auto and with USB-c connected...
tonysunshine said:
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
Click to expand...
Click to collapse
just updated to android 13 (64.1.x) from 64.0.x firmware - same problem except on the way home it was worse than it has ever been before, crashed / disconnected every 5 minutes and reconnected... extremely annoying.
i have 1 IV and don't have crashes. But generally, not as reliable as it was with my XZ2.
Car is Peugeot 3008 mk2 from 2017. Wireless does not work at all but don't really care about that because it just drains battery instead of charging. Now, charging........sometimes it does not charge despite having AA active and using sat nav. Cable that I used with XZ2 (ugreen) does not work at all for AA. And most of the time not even for data on laptop. Cable from XZ2 works with AA every time, did a 5000km trip a few months back, no issues. Except it does not charge sometimes, LED is on, sign for charging is on but battery charge goes down.
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
TodNex said:
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
Click to expand...
Click to collapse
Yeah, I've tried that including completely removing / reinstalling app etc.
Now trying on another phone (yes, another 5 IV) which is set up from scratch without restoring from backup.
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
somm15 said:
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
Click to expand...
Click to collapse
Hep, another one here!
i'm trying to remove apps one by one now...
Well, I had 1 hours without any crash... after enabling the debug layer for android auto. I didn't notice any difference or additional info but no crash.
Hey Guys; I am facing the same issue. Just, that it's not related to Android Auto.
Many apps were crashing just randomly.
For example, like Tidal, sometimes it was playing music for hours and sometimes just for a few minutes until it crashed.
So I enabled a feature in developer mode which allows to show a crashing dialog. And just a few moments later the nextcloud app crashed and the error message was something like "out of memory".
Looking in to it => Yep, there it was => the OS is holding almost all of the available memory.
So, you might want to check your memory in Settings => Developer Options => Memory.
And since I almost bricked my device last night, I just flashed the latest 64.1.A.0.857 via newflasher and at the moment (fresh OS) it seems to be better - but I will surley find out these days.
Merry Christmas everyone ...
Hi guys, I had similar problems with Android auto. I did a software repair with Xperia Companion, since then AA works fine.