http://www.htc.com/hk-en/SupportDownload.aspx?p_id=297&cat=0&dl_id=845
It's an RUU update, apparently to fix AGPS stuff, so I'd suspect it's a radio update, anyone tried it?
the_ape said:
http://www.htc.com/hk-en/SupportDownload.aspx?p_id=297&cat=0&dl_id=845
It's an RUU update, apparently to fix AGPS stuff, so I'd suspect it's a radio update, anyone tried it?
Click to expand...
Click to collapse
It´s too small to be a radio update.
No, it's not. But the "SIM contacts update" from January 7th is a RADIO-update. Take this.
Related
I've got JF 1.41 RC8, can I update the radio and if so are they any drawbacks/improvements I should be aware of?
I've been searching the forum but not really finding much info regarding RC8 (I'm unlocked, not on T-Mo AND roaming so I'd rather not risk RC33 and the horror stories about txt message charges)
Pretty sure the radio update is for RC33 only at the moment, and that there is a different update for RC9, which I hope gets rolled out properly very soon.
I have installed the radio update, and although I Haven't noticed any particular improvements, I haven't had any problems either
Shane2 said:
I have installed the radio update, and although I Haven't noticed any particular improvements, I haven't had any problems either
Click to expand...
Click to collapse
Same here!
Fushichou said:
Pretty sure the radio update is for RC33 only at the moment, and that there is a different update for RC9, which I hope gets rolled out properly very soon.
Click to expand...
Click to collapse
If a US phone can run RC9 without reflashing the radio to the EU version, that means there's no difference between them.
Granted, they could be doing something funky like hard coding in different radios for all firmwares, and RC9 doesn't have the RC33 radio update included in the code... but that is highly unlikely.
Just flash it, I very highly doubt it won't work. And if it doesn't, that's what the NBH is for.
How do you go about flashing the radio update if you already have JF's RC33 installed?
Thanks, if its no sig diff I'll just wait. I'm really waiting for the bluetooth stack to be updated ala 'cupcake' in an official capacity.
can i do this even tho i am running stock non rooted??? If so please can someone tell a newbie how to do this
From my experience, I wouldn't try it. I attempted with my ns4g something similar and the radio stopped working. I had to flash back to factory stock and call my carrier to reset my account. Since you're not experienced in doing this, I'd suggest not doing it. You can easily get yourself in a situation that your phone will be not working anymore and then you'll be back here asking us how to fix it. I'm not trying to be a ****, I'm just saying that it's not a good idea to try this.
oscarthegrouch said:
From my experience, I wouldn't try it. I attempted with my ns4g something similar and the radio stopped working. I had to flash back to factory stock and call my carrier to reset my account. Since you're not experienced in doing this, I'd suggest not doing it. You can easily get yourself in a situation that your phone will be not working anymore and then you'll be back here asking us how to fix it. I'm not trying to be a ****, I'm just saying that it's not a good idea to try this.
Click to expand...
Click to collapse
It's not really hard to do. You just flash a flashable zip or setup ADB and flash the radio image.
Is there a reason why you want to downgrade your radio?
Yes i have this stupid search button bug and its unbearable. I heard a new radio fixes the problem
JGAGNON10 said:
Yes i have this stupid search button bug and its unbearable. I heard a new radio fixes the problem
Click to expand...
Click to collapse
Search button? Radio wouldn't fix software.
Radio is responsible for your signal/reception.
the search button bug is connected to 3g connection.... it presses itself like crazy....although when wifi is on the problem is non existent. Its a common problem and is known to be fixed by a new radio
I cannot post on de development thread yet.
The random shutdown happens while the wifi is on, on the newer, recommended radio.
I could not make a report log.
Anyone have this problem?
the same for me
sirjerkalot said:
I cannot post on de development thread yet.
The random shutdown happens while the wifi is on, on the newer, recommended radio.
I could not make a report log.
Anyone have this problem?
Click to expand...
Click to collapse
i have the same issue, also with radio 1.20...
Originally Posted by sirjerkalot View Post
I cannot post on de development thread yet.
The random shutdown happens while the wifi is on, on the newer, recommended radio.
I could not make a report log.
Anyone have this problem?
Click to expand...
Click to collapse
i have the same issue, also with radio 1.20...
Click to expand...
Click to collapse
Just to check. You two are S-OFF and flashed the new radio AFTER S-Off'ing your phone?
Cause twrp will flash a new radio without errors, but it won't be applied if your phone's not s-off!
robdidu said:
Just to check. You two are S-OFF and flashed the new radio AFTER S-Off'ing your phone?
Cause twrp will flash a new radio without errors, but it won't be applied if your phone's not s-off!
Click to expand...
Click to collapse
I am S-off, superCID. Hboot is 1.09 I believe. The radio is the recommended one - 1.20xxxxxxL
Today I experienced something strange: I picked up the phone and it was shutdown. The difference was that this time the battery was drained and it didn't start until I'd plugged in the charger. I suspect the Fast Dormancy option, so I disabled it. But I am yet to confirm this. I also uninstalled G+, as I've seen in some forums to be the culprit. Again, I couldn't verify this yet. I'm doing this trial and error.
I had 2 random shutdowns today.
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?
My Nexus 5 which I upgraded from a 5.01 to the 5.1 (stock Google rom, without wipe) has a very big battery problem: the device never reaches deep sleep.
I have some years experience in identifying wakelocks, but this wakelock is new. And the strange thing is: I can't even find a thing on Google. Nothing!
The wakelock is a kernelwakelock (PowerManagerService.Wakelocks). I investigated at partial wakelocks which wakelock it is. It's a wakelock called 'ProxyController'. It's related to the phone process/app.
I wiped cache, tried different Kernel (elementalx). Changed CPU gov, wiped dalvik, changed network, refreshed some settings. Disabled unused apps. I even reinstalled the image and other files through recovery. But nothing helps.
Also I noticed, it might be related, that sometimes my phone reboots or it looses sim and signal. (Which worked perfect in 5.01!). All problems started after 5.1 upgrade.
Ofcourse I can do a full wipe, or revert back or try a custom rom. But I hope it is possible to fix, because besides these weird problems it was / is perfect!
Edit: Important, I couldn't be called either. Also calling someone was difficult and the phone process kept freezing. My phone (and then the phone part) was totally broken! Radio of 5.01 did fix. Read comments below!
Have you tried flashing an older radio.img version and/or a clean flash?
Elluel said:
Have you tried flashing an older radio.img version and/or a clean flash?
Click to expand...
Click to collapse
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
cognosco said:
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
Click to expand...
Click to collapse
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Elluel said:
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Click to expand...
Click to collapse
Yes I fear that too.
However, it started immediately after the 5.1 upgrade, before all was good...
It also seems there might be a link with screenoff/standby. When it's in standby and I switch the device on I see it has no connection or is reconnecting. As if something goes wrong with the connection then. Maybe important information.
I will investigate further. Ofcourse all new tips, ideas and infos are welcome. I will also keep you updated.
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Update: a few days later. Running 5.1 rom with 5.01 radio and all seems ok and fixed!
cognosco said:
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Click to expand...
Click to collapse
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
DarkSorcerer said:
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
Click to expand...
Click to collapse
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
cognosco said:
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
Click to expand...
Click to collapse
Hi,
Thank you for your quick answer. I'll try it first thing in the morning.
It is weird indeed.. My provider is the equivalent of Orange. As with you, it only started to happen after the update to 5.1.
I'll report back. Thanks!