Just downgraded from 4.3 to 4.2.2 and I have got rid of the bluetooth problems I was having.. I.e. Could not use my handsfree system in my car... Proving that Sony / Google completely screwed up the.bluetooth stack... Muppets.. Have either of them ever heard of regression testing?
It would appear not!!!!!!
nalab1 said:
Just downgraded from 4.3 to 4.2.2 and I have got rid of the bluetooth problems I was having.. I.e. Could not use my handsfree system in my car... Proving that Sony / Google completely screwed up the.bluetooth stack... Muppets.. Have either of them ever heard of regression testing?
It would appear not!!!!!!
Click to expand...
Click to collapse
how hard is it to downgrade back to 4.2.2 from 4.3? I'm running stock no root.
I'm having bad problems with Bluetooth and memory leak issues.
ssj_jaypee said:
how hard is it to downgrade back to 4.2.2 from 4.3? I'm running stock no root.
I'm having bad problems with Bluetooth and memory leak issues.
Click to expand...
Click to collapse
It's not hard.
But if go to 257 and then to 534 if you don't want to use 257 or want to root 257.
If you go 534 from 290 you'll lose IMEI
Sent from my C6903 using Tapatalk
nalab1 said:
Just downgraded from 4.3 to 4.2.2 and I have got rid of the bluetooth problems I was having.
Click to expand...
Click to collapse
Thanks for posting up about it. Until now, I hadn't heard of anyone actually trying the downgrade to confirm it fixes the problem. Would you be willing to contact Sony directly about it to make sure they know about it? We know two firmwares since 290 have been certified, but they haven't been released and we don't know the changes. It would suck for Sony to push new firmware and not fix this.
ssj_jaypee said:
how hard is it to downgrade back to 4.2.2 from 4.3? I'm running stock no root.
I'm having bad problems with Bluetooth and memory leak issues.
Click to expand...
Click to collapse
It's not hard - just get a copy of the FTF you want from the mega-thread and a copy of flashtool. There are tutorials on how to flash if you can't figure it out. However, since you're downgrading, you'll lose all your data (you must wipe data, or 257 won't boot).
I just went from 290 to 257.. Just copied everything I wanted from my phone to my pc, did the flash then a factory reset and then copied everything back.. Bit of a chore as I had to restore all of my apps etc but worth it to get the handsfree working again.. Still can't believe that Sony and or Google have screwed the bluetooth up so much.. I hate apple but they seen to make it work across their devices and various versions of ios...
not only the bluetooth, the whole fw is acting out.. slowing down, ram is filling too fast and apps don't remain in memory...
also my wifi seems less stable, on .257 the bars "seemed" lower but i was connected at all times, now i have 3 bars, but connection drops all the time...
Try different 290 fw - you can flash other regions as well.
My bluetooth us working great, wifi is better and all apps and features is working without any problems.
Try generic or something similar - that's not gereral problem.
Sent from my C6903 using Tapatalk
funky0308 said:
Try different 290 fw - you can flash other regions as well.
My bluetooth us working great, wifi is better and all apps and features is working without any problems.
Try generic or something similar - that's not gereral problem.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
When you say your bluetooth is working great - does it connect to your car audio and let you make hands-free calls?
Related
Is it possible to change the radio on the Xperia Play? I have been having some major Wifi issues on here.. 2.3.3 breaks Wifi, and flashing 2.3.2 fixes it.. is it possible to keep 2.3.3 but 'downgrade' the radio?
If i disable data traffic at home., it appears to stay wifi connected.. weird, but a workaround for now.
dassub said:
Is it possible to change the radio on the Xperia Play? I have been having some major Wifi issues on here.. 2.3.3 breaks Wifi, and flashing 2.3.2 fixes it.. is it possible to keep 2.3.3 but 'downgrade' the radio?
Click to expand...
Click to collapse
Are you on the stock images, or on one of the dev's ROMs? I heard there were issues on FXP/CM7 and on FTS for a bit with one of the kernels, but I think that might have been resolved.
If you are on stock images, not sure why to tell you. You are using the R800a or which model? is it Bootloader locked and/or simlocked? (I have to ask because you don't list a model in your profile)
ryocoon said:
Are you on the stock images, or on one of the dev's ROMs? I heard there were issues on FXP/CM7 and on FTS for a bit with one of the kernels, but I think that might have been resolved.
If you are on stock images, not sure why to tell you. You are using the R800a or which model? is it Bootloader locked and/or simlocked? (I have to ask because you don't list a model in your profile)
Click to expand...
Click to collapse
Generic UK 2.3.2, rooted, worked great for weeks, then OTA to 2.3.3 (xloud) and the problem comes up.. I had reverted back to 2.3.2 because of this issue before, but hoped it would resolve itself I guess.
So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?
Are you on 4.2.2? If so, you need your radio baseband upgraded to .48.
If that's not the case, then it could be a hardware issue.
Sent from my Nexus 4 using Tapatalk 2
cmacia06 said:
So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?
Click to expand...
Click to collapse
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).
simms22 said:
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).
Click to expand...
Click to collapse
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.
cmacia06 said:
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.
Click to expand...
Click to collapse
Where can I get the 4.2.1 Images seeing as how it was taken down from the google website. And so the .48 boot loader image
I Found this http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but i am not sure what version to download? are they all compatible?
Hey guys, I've been having A LOT of issues with the new updates. First the 4.4 and then the 4.4.2 that didn't solve a thing. I've installed them via OTA but after that i've already did:
- factory reset
- installed via fastboot 4.3, then updated via OTA to 4.4.2
- installed via fastboot 4.4, then updated via OTA to 4.4.2
- factory reset AGAIN - installed via fastboot 4.4.2.
I don't know what do to anymore! I can't take pictures because nexus just turns off the moment i take one. I can't install facebook, twitter or instagram and another random apps... And btw, is it normal that in 10 minutes the battery charges to 1% to 50%? i think i never noticed that...
BUT WHAT DO I DO? PLEASE HELP!
UPDATE:
This problem is solved, it was the battery. I've changed the screen recently and it needed a new battery too. Thanks to everyone that tried to help me
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
saifulh2304 said:
just flash the factory images for 4.4.2 via fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I do that? sorry but I'm a little noob.
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
follow the guide here: http://rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
maznex said:
how do I do that? sorry but I'm a little noob.
Click to expand...
Click to collapse
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Riro Zizo said:
follow the guide here: rirozizo.blogspot.com/2013/11/guide-how-to-flash-factory-images-from.html
Click to expand...
Click to collapse
maritimesbob said:
If you don't know how to use fastboot, use the Wugfresh toolkit, makes life very easy. It has the drivers, downloads recoveries, root files and the factory images. Really is easy with that.
Click to expand...
Click to collapse
Guys, like I said I used fastboot to install 4.4.2, it still didn't work. I followed this guide googlenexusforum.com/forum/nexus-4-roms/4046-guide-flash-stock-option-using-android-sdk-tools.html
Hey, guys, I haven't updated it to 4.4.2 yet cause my phone is rooted so I'm asking is it worth to go through all the process again? And if yes can anyone state the new features? ☺ thx a lot!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
evdrmr said:
Looks like a hardware issue to me. Probably your battery is faulty... Could explain the shut downs and trying to use the camera usually drains more battery so again that could it be. Could you be more specific about the other errors that you get?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hardware? It started to happen only when I updated the first time via OTA to 4.4.
I open the camera, I try to take a picture, the flash goes on and then the phone goes off. Sometimes I can turn it on and the battery it's the same, sometimes I can't turn it on without connecting to the charger because it goes off when I go to insert the PIN.
Well, after I understood that the problem was that apps, when I turned the WI-FI on, the phone immediately turned off after that I unistalled that apps and when I turned the WI-FI on I could go on Chrome and Play Store, and installed some apps (like n7 player) and everything was OK.
One time I installed Twitter and I used it for a bit and everything seemed fine but then I installed Facebook and the phone crashed again so I unistalled both. Same with Instagram.
I don't know how much more specific I can be... I really need help :s
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
aaronrw said:
it's not hardware. anyone who had this phone running pre 4.3 aosp will remember the camera issues and the clicking noises that went along with the focusing and then the reboots. the battery charging is also a widely experienced issue as well as going from a full charge to 50% in a few minutes. I'm getting the camera bug again on 4.4.2 hope a .3 build pops up soon to deal with it. I'm also 100% stock no root
Click to expand...
Click to collapse
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
maznex said:
exactly this is happening but on 4.4.2
BTW, when I'm charging the phone, none of this problems happens. I can install and use all apps and use the camera.
Click to expand...
Click to collapse
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
aaronrw said:
if I were having all those issues I'd try installing the Factory Image again or maybe try 4.4.1 and then use the OTA to update. BUT there is definitely some bugs in the latest KK release
Click to expand...
Click to collapse
I did all of that as I refered in the beggining... I will try to install 4.4.1 though, that was the only thing I didn't do, but I doubt it's gonna work, because installing 4.4 and 4.4.2 didn't solve a thing
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.2 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
maznex said:
sorry about the double post but there isn't the factory image for 4.4.1 here... https://developers.google.com/android/nexus/images#occamkot49h .
I tried to flash 4.4.1 following this guide http://rirozizo.blogspot.pt/2013/11/guide-how-to-flash-factory-images-from.html and when I turned it on I had no signal.. what does that mean? I guess it didn't worked..
Click to expand...
Click to collapse
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
taodan said:
The latest factory images are 4.4.2, that's why you didn't see 4.4.1 on Google's server. When you flash factory images, your radio will also be updated. When you flash a custom ROM, your radio doesn't get updated, that's why you had problem with cell signal. Or flash the appropriate radio for the ROM.
Click to expand...
Click to collapse
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
maznex said:
The phone asked me to insert PIN and then I had cell signal again.. Should I flash 4.4.2 again flashing the radio too? Because I have the feeling that this will not solve my problem. Like I said in the beggining I followed another guide to flash my phone, and in that guide it said to flash radio and "bootloader-mako..." (not sure what that is) and the cell signal problem still happened and then I couldnt install Facebook or Twitter or had my location on or using the camera without the phone turning off or rebooting...
EDIT: The phone just turned off when updating Google apps, so yeah... Didn't work :s
Click to expand...
Click to collapse
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
taodan said:
You said that when a PIN is input, the phone has signal again which means it's not a radio issue. Did you set up a PIN in the security section in your phone?
Click to expand...
Click to collapse
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
maznex said:
No this is just something that started to happen along with the other problems... Sometimes the phone loses signal for no reason and goes to the PIN input screen.
Click to expand...
Click to collapse
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
taodan said:
Which radio are you using? It should be .98 if you are on KitKat 4.4.2. You can flash a standalone radio zip file in recovery.
Click to expand...
Click to collapse
I don't know I will check later because now I'm not home. But when can I find that zip file and if I flash that it will only solve the cell signal thing right?
ever since updating to kitkat my nexus 4 is running in to a lot of issues with wifi, when i turn on my device wifi would work for about ten minutes and then stop, while still sowing connected to my home network but unable to load a page in chrome or send a message in whatsapp. if i downgrade back to 4.3 everything works fine again but updating again would do the same thing. even installing a custom ROM like CM11 would make wifi unusable while CM10.x would work fine.
Try flashing different radio. Use the one that comes with 4.3.
arffrhn said:
Try flashing different radio. Use the one that comes with 4.3.
Click to expand...
Click to collapse
ware can i find it?
leejenshil said:
ware can i find it?
Click to expand...
Click to collapse
In general section, there are threads called modem collection. You can start there.
Sent from a battery powered device.
Hello guys.... this is one of my first posts here so go easy on me...
Trying to get to the bottom of an issue I'm experiencing on my Nexus 4 16GB after updating.
So I had been postponing updating to Lollipop for months... (was still on 4.4.4 stock cuz I didn't quite like the new UI) and decided to update Sunday (Aug 10th) morning. Big mistake, apparently.
The OTA 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome! Regular google apps are generally non-responsive and supper laggy.
For Ex: Can't open Play Store, the app tries to open but all I see is a white app window,same with Photos, or maps... ironically Whatsapp and certain other non-google apps are opening.
So I currently can't even use my N4 much, I'm trying to find out a what's causing this and if I need to revert the upgrade or flash a ROM or something,
My 4.4.4 was rooted FWIW, and now it's not. Not sure if it's helpful, but I have about 1.3GB free internal storage, and 1GB free memory when I run. So I don't think the issues are being caused by an app I installed or some service running wild. Any help is appreciated, thanks!
combatplane57 said:
Hello guys.... this is one of my first posts here so go easy on me...
Trying to get to the bottom of an issue I'm experiencing on my Nexus 4 16GB after updating.
So I had been postponing updating to Lollipop for months... (was still on 4.4.4 stock cuz I didn't quite like the new UI) and decided to update Sunday (Aug 10th) morning. Big mistake, apparently.
The OTA 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome! Regular google apps are generally non-responsive and supper laggy.
For Ex: Can't open Play Store, the app tries to open but all I see is a white app window,same with Photos, or maps... ironically Whatsapp and certain other non-google apps are opening.
So I currently can't even use my N4 much, I'm trying to find out a what's causing this and if I need to revert the upgrade or flash a ROM or something,
My 4.4.4 was rooted FWIW, and now it's not. Not sure if it's helpful, but I have about 1.3GB free internal storage, and 1GB free memory when I run. So I don't think the issues are being caused by an app I installed or some service running wild. Any help is appreciated, thanks!
Click to expand...
Click to collapse
You could try flashing a factory image of 5.0.1 and see if that helps.
theminikiller said:
You could try flashing a factory image of 5.0.1 and see if that helps.
Click to expand...
Click to collapse
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
combatplane57 said:
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
Click to expand...
Click to collapse
If you're rooted ota's won't work
Sent from my Nexus 9 using XDA Free mobile app
combatplane57 said:
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
Click to expand...
Click to collapse
You might try upgrading to 5.1.1 LMY48I, it is all the bug fixes for 5.+, and should be more stable.