Related
How is the latest HTC update incorporated into ROMs, specifically non-Sense based ROMs ? I think with Sense-based ones, it's somewhat easier, but for Cyanogen-based ones, I'm completely clueless.
Main reason I ask is because of the silent-call issue. It's supposedly fixed with this update (I don't know for sure though) and it would be real nice to have it incorporated into the CM ROMs. I was hoping that running a CM ROM would avoid this issue, but alas, it doesn't.
hallstevenson said:
How is the latest HTC update incorporated into ROMs, specifically non-Sense based ROMs ? I think with Sense-based ones, it's somewhat easier, but for Cyanogen-based ones, I'm completely clueless.
Main reason I ask is because of the silent-call issue. It's supposedly fixed with this update (I don't know for sure though) and it would be real nice to have it incorporated into the CM ROMs. I was hoping that running a CM ROM would avoid this issue, but alas, it doesn't.
Click to expand...
Click to collapse
i have yet to have any silent call at all on any rom i have ever flashed
When I was running Sense-based ROMs, it was getting to the point that I was ready to return my phone to VZW. When I switched to CM5 ROMs, it was much improved, but still happened on occasion.
hallstevenson said:
When I was running Sense-based ROMs, it was getting to the point that I was ready to return my phone to VZW. When I switched to CM5 ROMs, it was much improved, but still happened on occasion.
Click to expand...
Click to collapse
wish i could offer advice but ive yet to experience it
I'm beginning to think that the silent issue is user error. Maybe a setting or am app that some people use or something. I have never had the issue and I have tested just about every rom.
Sorry off topic.
Sent from my KaosFroyoEris
Speculation is that the new radio may be the "silent call" bugfix. Flash that & see if it helps.
Sent from my Eris using XDA App
PPCGeek01 said:
Speculation is that the new radio may be the "silent call" bugfix. Flash that & see if it helps.
Click to expand...
Click to collapse
That "new" radio has been available from Sprint for more than a few weeks, if not longer, and I can personally attest that it does NOT fix the issue.
i have noticed this issue with my gfs phone. when she answers her phone no one can hear her. shes had this problem on several different roms. i however haven't on any...
I can confirm that the latest fix pushed from VZN has fixed the no-audio bug on my wife's Eris. She was rebooting multiple times a day, and has not since the update!
The real question is can I safely root and load EvilEris 3.0 now without losing the fix??
dman776 said:
The real question is can I safely root and load EvilEris 3.0 now without losing the fix??
Click to expand...
Click to collapse
I think the answer to that is "no".
listyb01 said:
I'm beginning to think that the silent issue is user error. Maybe a setting or am app that some people use or something.
Click to expand...
Click to collapse
Too many people have changed the same setting or added the same app then.... And if that many people have done the same thing "wrong", it still warrants a fix from VZW or HTC.
Havent had the problem with PlainJane2.0, will report if I do though
I've been running non-Sense ROMs since I rooted and haven't had the silent bug yet. I had it a few times after the 2.1 OTA, but nothing since running White Widow 4.5 and now CELB 2.8... hopefully it stays that way
DDustiNN said:
I've been running non-Sense ROMs since I rooted and haven't had the silent bug yet. I had it a few times after the 2.1 OTA, but nothing since running White Widow 4.5 and now CELB 2.8... hopefully it stays that way
Click to expand...
Click to collapse
If you're like me, you just jinxed yourself. I said the same thing -- had the same experience -- for a good while after switching to CM-based ROMs. I posted this and bam ! Started experiencing it again...
hallstevenson said:
I think the answer to that is "no".
Click to expand...
Click to collapse
I can confirm this. The EvilEris 3.0 ROM does not include this bug fix and the bug is still present. The bug ceased for me until I rooted my phone and installed the EvilEris 3.0 ROM.
No one ? The original question still has me wondering....
hallstevenson said:
No one ? The original question still has me wondering....
Click to expand...
Click to collapse
I have been experimenting with the files from the MR4 update in a few ROMs that I have built but I still can not seem to get them to "take". I am not sure if the update is in build.prop or one of the other files included in MR4. I am still looking for any good documentation on how to cook the update in to my ROMs.
There are folks who know how to do it, but I don't know if it's documented anywhere.
Every rom i have used that was made without the July patch has done the glitch. Now that im on a rom with the patch i havent had an issue. Sucks cause i was loving Sense-able, but im getting use to Xtr
SCato said:
Every rom i have used that was made without the July patch has done the glitch. Now that im on a rom with the patch i havent had an issue. Sucks cause i was loving Sense-able, but im getting use to Xtr
Click to expand...
Click to collapse
I know Sense-Able is Sense-based, but is XTR ? If a ROM is not Sense-based or if it's ported from another (HTC) phone without the issue, and therefore no patch has been made, I wonder if it can be incorporated.
I moved to a new apt about a month ago and have a great 4g signal (sprint is my carrier). For the first three weeks the 4g worked great. Now I will be connected to the 4g signal and streaming a video, playing a game, or doing school work and the connection will just cut out. I will still be connected to the 4g signal and have full bars but have no data connection. I connect to the internet with pdanet or wireless tether (I have tried to use my phone's browser as well when this happens and it also does not have data so I know this is not a pdanet or wireless tether issue). I can turn off the 4g and reconnect with 3g service. I will then turn on 4g again and it will take a good 5 to 10 min before it will reconnect and the process starts over again. I generally can get between 5 and 30 min of connection with 4g before it flakes out.
I could not find this issue on these forums anywhere and have enjoyed reading threads on here, but cannot find this issue posted anywhere so far.
What I have done so far:
1.Restore
2.Reset (installed Azrael's rom with Netarchy's kernel in place of stock sense with unrevoked I had before)
3.Updated prl
4.Updated profile
5.Changed the Wimax sleep mode setting from 10 seconds to 300 seconds. I have not had a chance to test this but do not see this helping considering when it cuts out I am generally in the middle of something so there would be no chance for the connection to time out.
6.Contacted Sprint multiple times and been transfered around and got a confirmation number on a ticket for them to check the 4g signal (still a possibility it is on their end, just want to make sure its nothing on my end)
Are there any other settings or things I can try on my end to verify that it is either on my end or sprints end? I really would like to get this working, it is my primary source of internet and I need it for online classes. I have rooted my phone and do have my msl number so if there are any tweaks I can do with these please let me know.
On a final note thank you to everyone who contributes to these forums. This is one of my first posts here but I have been a regular reader since I got my Evo. I am a huge fan of all the work that the devs and posters put into this site. This is a great resource and I am very grateful for any responses that anyone can provide for me.
From the posts that have read 4g problems almost always are Kernel related... Especially Bfs kernels.
Have you tried any other kernel and duplicated the failure?
Net's 4.3.2 cfs kernels work great with my 004 hardware EVO running MikFroYo 4.4 (IMO the absolute best Rom choice for your EVO.
DreamSQK said:
From the posts that have read 4g problems almost always are Kernel related... Especially Bfs kernels.
Have you tried any other kernel and duplicated the failure?
Net's 4.3.2 cfs kernels work great with my 004 hardware EVO running MikFroYo 4.4 (IMO the absolute best Rom choice for your EVO.
Click to expand...
Click to collapse
Honestly I just am getting into the custom rom/kernels. I wanted to be able to overclock and get better battery life out of my phone. I did have unrevoked on there but the issue started while I had unrevoked.
Is MikFroYo a sense based rom? I have hardware version 0003. Do you think that this is a kernel issue? I didn't change kernels until after this issue started.
Xenomisis said:
Honestly I just am getting into the custom rom/kernels. I wanted to be able to overclock and get better battery life out of my phone. I did have unrevoked on there but the issue started while I had unrevoked.
Is MikFroYo a sense based rom? I have hardware version 0003. Do you think that this is a kernel issue? I didn't change kernels until after this issue started.
Click to expand...
Click to collapse
Yes it is sense based. Lightning fast, VERY stable, with an amazing support forum. Again, I brought up the kernel based on what I have read.
Check out Mik's ROM. I can't imagine using anything else!
I've got the same issue and I'm running mikfroyo 4.4 and even have it on steelrom, both sense-based roms. And I have never used a BRS kernel.
Anybody got any suggestions?
I had this problem since SC roms but now I have Evil froyo rom and having alot more missing calls. My friend told me that he called me three times but didnt get any....i really dont care about the multimedia but phone calls!!!! phone should functioned as it should be but its not...so anybody knows how to solve this problem...?? I tried to do *228 thingy but still doing this...
What radio/modem are you using? Try using ED04, if you're not already on it. I had your problem before and ED04 seemed to help.
Sent from my SCH-I500 using XDA App
Go back to eclair with ea28 radio. There is no froyo rom/radio free of this issue currently available. I have tested all radios available right now and had missed calls on all of them. ED04 made it even worse actually.
I've tried numerous radios, roms, and kernels and am currently on stock ED04 with the same issues. I think ED04 is actually worse on my phone as well. I've read about quite a few people having the same problem and the overall consensus is that it's a hardware issue.
For ****s and giggles, Odin the EC09 radio. I personally use it and find it to be pretty nice, much faster data speeds, and it MAY fix your issue.
It's not a FroYo deal, it's a network issue. My wife's Fascinate is still on DL09 and she has missed calls too. A lot of people believe it is an issue with LTE affecting 3G, since the problems started popping up around the same time LTE was flipped on
Call and complain... They know it's a known issue, but they are not fixing fast enough. It's pretty sad. I miss calls from the wife and boss... You may even get the droid charge...
RacerXFD said:
Call and complain... They know it's a known issue, but they are not fixing fast enough. It's pretty sad. I miss calls from the wife and boss... You may even get the droid charge...
Click to expand...
Click to collapse
Yeah I did call and they offered me another Fascinate, Droid X or D1 so nothing that I could accept. The only upgrade that makes sense available right now would be Charge but had no luck convincing them. Right now I'm testing EC09 leak modem and so far all calls came through (as far as I know) but it was just 2 days so it's too soon to know if it helps or not.
They won't offer me jack... Am I saying something wrong? Hahaha
This freakin issues is pissing me off since i got this VZN fascinate imported here in India ,
and its not NETWORK its just bloody FROYO and FASCINATE , somehow all froyo ROMS have got this crap issue.
i have started inumerable threads about so many ROMs and setups but this issue always keeps coming back.
I am keeping my fingers crossed that the GB roms wont have this bug..
Just to keep myself connected i have yesterday flashed back to dl09 debloated and using ed04 ( i know its full of crap this modem is , but i am giving it a shot with dl09 and so far in last 24 hours havent missed a single call.
I'm on hold with VZ tech support right now, I can't stand this bug anymore.. I'm trying to find a new job so I can't afford to be missing calls
edit: they're sending me a new fascinate.. might just have to buy another phone and use my fascinate as an mp3 player
Trying out the EC09 (gingerbread) radio.. I may not know anything for a few days.
I have been having this problem every since I started using froyo
if I switch back to eclair it is gone
It is not in the radio
It has to do with the phone going in a deep sleep it will not wake up
The deep sleep is causing other issues with sms, mms, alarm not working when set all because it will not wake up
Alot of problems Same cause
The only way I have found to stop this is go to Eclair
wardcst said:
I have been having this problem every since I started using froyo
if I switch back to eclair it is gone
It is not in the radio
It has to do with the phone going in a deep sleep it will not wake up
The deep sleep is causing other issues with sms, mms, alarm not working when set all because it will not wake up
Alot of problems Same cause
The only way I have found to stop this is go to Eclair
Click to expand...
Click to collapse
Yes indeed, ECLAiR is the only answer for this issue.
if anyone wants to install debloated rooted version of dl09 then simply ODIN this > http://forum.xda-developers.com/showthread.php?t=911677
after that boot it up
store latest SU file in sd card and this debloated ROM (only ROM and nothing else ) from adryn >>
http://adrynalyne.us/files/roms/DL09_2.zip
and then again shutdown and ODIN CWM and without booting install SU first via recovery
boot up
shutdown
reboot into recoveryand flash the alreday stored adreyn's debloated version.
My wife has always been on DL09 and still experiences it... Which is why I keep saying it isn't a froyo issue
Sent from my SCH-I500 using XDA App
You are probly right
It just got way worse with froyo
Is it doing this on the GB Leak
JaeKar99 said:
Trying out the EC09 (gingerbread) radio.. I may not know anything for a few days.
Click to expand...
Click to collapse
Been using it for couple days. Nothing new to report, went back to ED03. If we could just get the stability of GB 3G signal I would be a very happy camper.
+1 for the EA28 modem, at least for my phone in a VZW marginal reception area where 1x reigns supreme. Easy to get the missed calls, by attempting calls during bootup, sleep-wake, busy with GPS/aGPS, etc.
In my particular case, ED04 made things worse. EC09 was much much better. EA28 had the least missed calls as far as I can tell (n=1). YMMV.
Link to jazzyjames discussion:
"Interesting GPS find"
http://forum.xda-developers.com/showthread.php?t=1106868
Link to Comradesven's thread:
"[MODEM][ODIN][CWM]DL09, EA28, ED01, ED03, ED04 modems without ridiculous 100MB OTAs"
http://forum.xda-developers.com/show....php?t=1097355
Link to JPTech7's thread:
"[EC09][MODEM][ODIN] EC09 Radio/Modem for Odin"
http://forum.xda-developers.com/show....php?t=1132236
Deep Sleep Missed Calls
Download softlocker from market. Keeps the phone from going into deep sleep and helps out with the missed calls issue. It is mostly for tablets but will also work for android phones.
I just want to make sure everyone knows that 911 does no work on roms that are based off the AOSP, and it NEVER HAS WORKED. You can read a better description on this post:
http://forum.xda-developers.com/showthread.php?t=1385613&page=7#68
The only ROMs that 911 has worked on are ROMs based off of official releases from Samsung. I would suggest for your safety flashing back to a Samsung based ROM.
Went back to Bionix 1.3.1, at least GPS works now. (Yeah I know why it did not work in CM7, just saying that is not too bad going back to a Samsung ROM :/)
E911 doesn't work. 911 works, different.
E911 is if you have no sim card or have no service and can make emergency calls only.
I lived a long, long time before 911 existed and I can't remember the last time I had no service to t-mobile and had to rely on att towers for an emergency call.
I'll take my chances, thank you.
Ohh now I get it I thought it did not work completely now I get it now I understand how having no source code would effect that!
Sent from my SGH-T959 using XDA App
Does 911 calling work on MIUI?
Sent from my Vibrant
Kind of scary that some people are barely now finding out that their custom flashed Vibrant doesn't make 911 calls. I wonder how many other people who don't frequent the forums often still have no clue their phone doesn't make 911 calls.
It still blows my mind why a disclaimer wasn't posted in large bold font in the CM thread when the stable was released.
Anyway I still think they did the right thing to stop support. Maybe Samsung will surprise us with source or a leak soon and we can get support back.
Tynen said:
I just want to make sure everyone knows that 911 does no work on roms that are based off the AOSP, and it NEVER HAS WORKED. You can read a better description on this post:
http://forum.xda-developers.com/showthread.php?t=1385613&page=7#68
The only ROMs that 911 has worked on are ROMs based off of official releases from Samsung. I would suggest for your safety flashing back to a Samsung based ROM.
Click to expand...
Click to collapse
according to your link:
"The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail"
What makes you think it is working on all the I9000 ports to the Vibrant and not just Official Samsung Vibrant Roms if the above statement is true? back to KB5 I guess.
I'm not saying E911 works, but why would it work on a I9000 rom with I9000 framework running on a Vibrant if it's a incompatible framework issue?
Nabeel10 said:
Does 911 calling work on MIUI?
Sent from my Vibrant
Click to expand...
Click to collapse
As long as I have been on MIUI, I have had to call 911 a few times. Each time, it would not even connect. Luckily I had my wife's phone handy.
My best combo.
Well when I found out that 911 doesn't work on CM/MiUi I switched back to 2.2.
I have been back on 2.2 for a while now and my phone is actually fast without the frequent crashes and problems that came with CM/MiUi.
If you want a fast lag free experience with working 911 I suggest the following semi-stock combo.
(before any of these steps always good idea to backup your nv_data.bin so that you don't lose your imei ever)
1) Flash stock deodexed/rooted KB5, found in the development section
2) Flash the stock KB5 kernel with voodoo lagfix included in the kernel. Also in development section. Make sure you go into recovery and enable Lagfix after you flash the Kernel. Also make sure you disable Lagfix anytime you want to flash something new.
3) Touchwiz is very laggy, so use LauncherPro instead. LauncherPro found in Market.
The above combo has been fast and lag free. 911 works and the GPS works also as best as it can.
+1 on this. I have had same experiences but with different set up. KB5 and Voodoo and am completely happy with performance, speed and stability. On Toxic D9 RC3 Bali X kernel. GPS lock 9 birds down to 10 feet.
bobshute said:
E911 doesn't work. 911 works, different.
E911 is if you have no sim card or have no service and can make emergency calls only.
I lived a long, long time before 911 existed and I can't remember the last time I had no service to t-mobile and had to rely on att towers for an emergency call.
I'll take my chances, thank you.
Click to expand...
Click to collapse
Actually, 911 doesn't really work either - you will get no audio during the call and will have to wait for a call back if your phone doesn't actually freeze when your call fails (which also happens sometimes during the 911 call on the Vibrant when using any code derived from our source). E911 is just an extreme case of the same issue. Our advice, go back to a Samsung derived framework for the Vibrant on the Vibrant.
bobshute said:
according to your link:
"The same emergency call callback handling that is present on Galaxy S and Captivate doesn't work on Vibrant, and the differences are enough to make E911 fail"
What makes you think it is working on all the I9000 ports to the Vibrant and not just Official Samsung Vibrant Roms if the above statement is true? back to KB5 I guess.
I'm not saying E911 works, but why would it work on a I9000 rom with I9000 framework running on a Vibrant if it's a incompatible framework issue?
Click to expand...
Click to collapse
The framework is incompatible with tmo - it works fine on Galaxy S and Captivate, which is one reason it took longer to find out because we didn't actually have Vibrants to test on. I don't know of any AOSP builds that didn't start with our code (CyanogenMod), and therefore it would be safe to assume that all AOSP builds for Vibrant cannot do (E)911 calls correctly. Our suggestion is to go back to a Samsung or Samsung derived ROM that is using Samsung's framework for the Vibrant on the Vibrant.
Thank you atinm. I have appreciated all your work to make our Vibrant phones better. This 911 issue has people spooked. But outside of the CM team (you and coolya). Its not understood very well. I'm dumb sometimes but I can't figure out how this would not affect non vibrant stock rooms as much as aosp roms.
Sent from my SGH-T959 using XDA App
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.
claucXC said:
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.
Click to expand...
Click to collapse
why don't you call 911 yourself ?
If your call doesn't goes thru for any reason they will try to call you back, if that's the case then just answer the phone and tell them that you bought a used phone and you were testing 911 calling.
Simple as that, I did it myself and my result varied between asop roms from phone crashing and only solution was a battery pull to connecting but not audio plus new years force close party.
claucXC said:
Sorry, I'm slow...still confused. Can someone please answer yes or no if 911 and e911 will work on any i9000 Samsung Gingerbread ROMs ported to the Vibrant? Not sure if the Simply Honey (2.3.4 JVR) ROM falls into this category but I read in that post that 911 was not working -- at least in the August and September time frame.
I'm just trying to find out if there are any Gingerbread ROMs (non AOSP) I can use that will have this functionality because I'm ditching my land line and this will be my primary phone soon. If not, back to Froyo.
Click to expand...
Click to collapse
If 911 doesn't work in CM and MiUi do you think it would work in ported i900 Gingerbread roms? I'm not 100 percent certain but I would think NO.
SamsungVibrant said:
If 911 doesn't work in CM and MiUi do you think it would work in ported i900 Gingerbread roms? I'm not 100 percent certain but I would think NO.
Click to expand...
Click to collapse
CM7 and MIUI are AOSP and i9000 Gingerbread is international Samsung if I'm not mistaken. Hence my question.
If you are like me, Cyanogen,of works great as media player for Vibrant.... happy with it, never use it as a phone anyways.
Sent from my Xoom
old news.. this has been pretty common knowledge for almost a year now. But good job compiling all the info together i suppose?
luckily in the 12 years i've cellular devices i've ha to dial 911 twice.
and even then you can call non emergency and get forwarded to local enforcement based on your Cell tower triangulation.
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
claucXC said:
CM7 and MIUI are AOSP and i9000 Gingerbread is international Samsung if I'm not mistaken. Hence my question.
Click to expand...
Click to collapse
Most i9000 roms "are" samsung. However if you read the OP of the rom itself you are looking to flash the Dev will usually tell you what source the rom is built off of.
For those interested...a little info on 911.
E911 stands for enhanced 911. E911 differs from 911 in that location information is transmitted to the 911 call center. This is for landline phones attached to a physical address. For wireless call, there are two types of data transmitted. The old standard (and still in use on older cell phones and with some of the newer carriers) was call Phase 1 Wireless Data (WPH1). It was simply the location of the Cell Phone tower the cell phone radio attached itself to. The current standard is called Phase 2 wireless Data (WPH2). This provides GPS location data to the call center. Depending upon the carrier, it can be actual GPS data from the cell phone chip or GPS data triangulated via cell phone towers.
Further more, none of the AOSP ROMS (miui or CM based) that I've tested work with 911. The Cyanogenmod team did the right thing pulling their work. Genesis3 (props to Genesis3!!!!) continues to dig into the problem and I'm his canary. I have personnaly verified that Simply Honey Gingerbread 2.3.4 JVR + Modem JVS works as well as NeoBuddies ICS V7. Other than that, it's a waiting game for source or a fix.
Ken
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
ketonkss4 said:
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
Click to expand...
Click to collapse
what about trying an other kernel...?
regards
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
molesarecoming said:
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
Click to expand...
Click to collapse
you are absolutely right when it comes to the older 33 radio. but ive had a few people report that the even older 27 radio is working with 4.2.2 roms. i havent tried, so i cant confirm it myself.
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
Click to expand...
Click to collapse
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
simms22 said:
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
Click to expand...
Click to collapse
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
ketonkss4 said:
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
Click to expand...
Click to collapse
no. try the 27 radio, i hear people have luck with it and 4.2.2 roms. if not, then youll need the 48 radio http://forum.xda-developers.com/showthread.php?t=2087227
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue...
Click to expand...
Click to collapse
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
molesarecoming said:
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
Click to expand...
Click to collapse
...Yeah I think you make a good point. Damn, and here I was trying to hold out until t-mobile rolled out their LTE so I could finally make use of the LTE chip.
I suppose ill just have to upgrade the radio... I could always go back right?
Well hopefully Google releases a LTE capable, 32 gig Nexus 4 and stops toying with us... lord knows I would give so many things for that.