Related
What's the verdict on this? I was running the leaked Gingerbread radio, seemed to be working fine. But I read in one of the ROM threads in the Dev section that the new radio is breaking phones. Apparently after some amount of time running it it completely breaks WiFi... permanently.
What's the story on this? It came from a dev directly, though he said he wasn't sure that is what caused it, he said his phone had to be replaced, and that others had had the issue with the leaked radio as well. Coming from a dev, it freaked me out enough to flash back to the stock radio immediately.
Prior to the GB leak, I'd been running the most recent leaked Evo radio (4/8 I think?) Also seemingly without any problems. Was that radio causing any issues?
Do you have the original post? What development said this?
Sent from my ADR6300 using XDA App
Birthofahero said:
Do you have the original post? What development said this?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Ditto. I've ran it since it leaked. And I've never had a problem. And I've ran all the leaked evo ones as well.
Sent from my ADR6300 using XDA App
He may have been referring to the leaked GB radio for the HTC Thunderbolt. A lot of people have reported bricks from it.
i've been running this radio since it came out, with wifi on most of the time, and haven't had any issues
I've heard this too, and it was in reference to the incredible 5.06 radio. I used it for a short time and it was fine (aside from terrible data speeds) but I'm not really inclined to risk it in the event that there is a correlation between those problems and the new radio.
Had to dig for it.... I have read thru so many threads, but here is what I'm referring to:
forum.xda-developers.com/showthread.php?t=1109355&page=15
Newtoroot is the dev who said that he suspected the new radio broke his WiFi. But a few other people in that thread say they've also had issues or heard that the new radio causes issues with WiFi that can be permanent.
Well ive seen about two people running the leaked radio go into an endless bootloop that doesnt allow you to go into recovery or anything just bootloop after bootloop after bootloop...so technically no hboot=brick idk what other problems it causes but it could be the same as the thunderbolt radio corrupting the emmc. I wouldnt recommend staying on the leaked radio if you really dont have to. Try out the Official Evo Gb Radio if you want the newest
My wife and I both have rooted Dincs, I was playing around flashing different radios on my dinc and comparing signal and data speeds, and GPS lock acquisition, between mine and hers. Hers is stock OTA ROM and stock radio. I tried the Evo 4.08 and the latest GB leak, I saw virtually NO difference in speeds or signal between my phone and hers, with them side by side.
- DSLreports.com consistently reported download speeds ~500-700 kbps
- Signal strength consistently -86 to -90 db
-GPS locks in about 8-10 seconds
both phones were very consistent regardless what radio I had ok my phone. That's enough to convince me that the stock radio is good enough for me
bast525 said:
My wife and I both have rooted Dincs, I was playing around flashing different radios on my dinc and comparing signal and data speeds, and GPS lock acquisition, between mine and hers. Hers is stock OTA ROM and stock radio. I tried the Evo 4.08 and the latest GB leak, I saw virtually NO difference in speeds or signal between my phone and hers, with them side by side.
- DSLreports.com consistently reported download speeds ~500-700 kbps
- Signal strength consistently -86 to -90 db
-GPS locks in about 8-10 seconds
both phones were very consistent regardless what radio I had ok my phone. That's enough to convince me that the stock radio is good enough for me
Click to expand...
Click to collapse
Yea the stock radio is good i just wanted to try something new and flash a radio im on 4.08 thing about switching to the offcial evo gb radio
I ran 4.08 for a few months. I had no problems with it. The GPS *seemed* to lock faster, but the testing today has me thinking it must have been more where I was or something else giving the faster locks. I'm going to try some more radios tonight and test side by side with my wife's dinc just to see if any of them actually makes a significant difference.
I've been using the leaked 10.05 radio since it came out and have had no problem with it ever. My wifi has never ceased to work and since I use it about 99% of the time you can bet this radio is safe.
Sent from my ADR6300 using XDA App
Anyone tried 2.15.00.11.19 and notice any drawbacks over the Evo Official?
Been running 2.15.00.11.19 since couple days after it hit and have had no adverse effects but hearing the Evo Official is good is giving me an itch that just has to be scratched. If someone says not to switch, it's no better, I'll leave it be. If however the EO is better.... AAAAA Flashing I will go!
which radio are we talking about? 05.02 or 05.06?
Well I've read 5.06 is the leaked and had bricked (no hboot, boot loop) so guessing 5.02 would be the official unless I'm wrong which is not uncommon.
Have great gps and call service, data is just miserable lately on 3g. If not radio, it's got to be big red slowing down in area to better support 4g.
Sent from my HTC Droid Incredible using XDA Premium App.
Hello everybody. I updated from eg30 (I only had the phone for a day and had one LOS on eg30) and went to ek02. I wanted to create this thread for all the brave souls who updated to let everyone know if it's worth losing the eg30. I haven't been running it too long... only ~ten hours or so. I haven't had LOS yet. As far as reception, speeds, quality, etc. I have no idea; I just got the phone yesterday night.
Let's try and keep this organized. If you want to report your findings on ek02 please do so in this format:
Previous LOS ~frequency (and Modem version):
With ek02, LOS frequency(if any... hopefully, none):
data speeds/ reception on old modem:
data speeds/ reception on ek02:
Just a courtesy thread for those who are laying back and waiting.
Edit: a few people brought up a good point. Kernel matters! Include kernel observations too.
Would love to see some reports. For those on eg30 that are going to update to ek02 run some speed tests first then update and run more and compare them. Thanks.
Sent my from IPad!
musclehead84 said:
Would love to see some reports. For those on eg30 that are going to update to ek02 run some speed tests first then update and run more and compare them. Thanks.
Sent my from IPad!
Click to expand...
Click to collapse
Pretty much my thoughts. Hopefully people will actually post their results in this thread to help others who haven't updated
With the EG31 modem and EG31 [or EK02] stock kernel, I have not have one LOS or ghost LOS.
Been 12 days.
I never got them while I was on the EG30 or 31 stock kernel. I would get los at least once a day on every custom kernel.
Today I got los (on the EK02 modem and Lostkernel) but it seemed to happen when the signal was handed off from my airave to the normal mobile signal. Once I left airave coverage I was looking at my phone. I saw it disconnect from it, my bars came back (full) but no 3g icon or data until I rebooted. I just flashed the stock Ek02 kernel so hopefully I wont get it again like I didnt on the other two stock pulled kernels
I'm referring to just the modem:, not the kernel.
Sent from my SPH-D710 using XDA App
Moose8106 said:
I'm referring to just the modem:, not the kernel.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Considering that they are both contributing factors (although the modem is more so) they are both relevant
mattykinsx said:
With the EG31 modem and EG31 [or EK02] stock kernel, I have not have one LOS or ghost LOS.
Been 12 days.
Click to expand...
Click to collapse
Same here and I went to some known bad spots too and the EK02 kernel with EG31 modem seems to be working really well so far. The kernel does play a role so hopefully we will see some comparisons using same kernel
Sent from my Nexus S 4G using xda premium
JohnCorleone said:
Same here and I went to some known bad spots too and the EK02 kernel with EG31 modem seems to be working really well so far. The kernel does play a role so hopefully we will see some comparisons using same kernel
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yeah Kernel plays a big part f,sure.
LOST kernel los has been out of control , many of its users went back stock kernel finding los to be little to none.
Why thats ignored placing majority of blame on modem is beyond me.
I knew that...(not really ) I'll add kernel to the op. Thanks
Sent from my SPH-D710 using XDA App
I'm running both the EK02 kernel with the EK02 modem. Not one LoS to speak of yet (running since about 1pm yesterday). The bars don't jump around as much, I seem to be getting a better signal. Before this I was running the Rogue stock kernel and had the EG30 modem (of course).
As far as speeds, that's difficult to say given all the variables on a mobile connection. So far though the 3G download speeds seem to be higher, double what they were almost. That doesn't say much when they were 7 - 24kBps before. Now I'm looking at 30 - 50+kBps. Like I said, that could just be a fluke so more testing will need to be done. WiMax has about the same speeds too, was 380kBps average, now it's around 440kBps. - Those are kiloBYTES not kiloBITS for those that get confused.
The kernel seems to be a significant improvement though. Benchmarking scores went up on Antutu, Quadrant, and Linpak. The system had no lag before so without benchmarking you really can't tell.
Lastly, the ROM updates are nice I guess. A few icon changes and the overscroll glow has now been changed to blue, as opposed to the yellow it was before. Other than that nothing fancy or notable has changed from what I can tell.
One addition here, the battery life is very noticeable with the update. For me at least - it drains significantly slower than the previous stock kernel.
I havent had LoS or ghost LoS ever since I installed the modem and the kernel, I usually get 3 a day but 18 hours in, nothing, nada.
I have noticed the phone "snappier" than normal though
Was anybody getting random hot reboots with any eg31 kernels? If you have, did the ek02 kernel remedy that? Others and myself have been trying to solve our hot reboot issue (in Calkulin's thread). We don't know what is causing them for a select few of us.
I flashed the ek02 kernel on blazer rom and still get hot reboots. I've tried almost every rom with different kernel combos and still get them. Got them on stock eg30 and eg31 kernels and modems.
kleen3r said:
I flashed the ek02 kernel on blazer rom and still get hot reboots. I've tried almost every rom with different kernel combos and still get them. Got them on eg30 and now eg31 modem.
Click to expand...
Click to collapse
Can you either post here or pm me a list of apps you have? I had these reboots on my Evo 3d and I'm using the same apps. Let's compare the apps that we have... because as of right now, the only variable I haven't tried is a rogue app. :/
I don't think it's an app but maybe a custom script used by the rom developers. The only time I didn't get the reboot is by going back to the stock rom.
kleen3r said:
I don't think it's an app but maybe a custom script used by the rom developers. The only time I didn't get the reboot is by going back to the stock rom.
Click to expand...
Click to collapse
If it was a script.... wouldn't everyone be getting these issues? Some are getting it on every single rom too.
If you're on Calk's do you think it's the undervolt?
just updated mine a couple of hours ago, so this may be a bit premature, but I dont really see any increases in network speed. When using the speedtest app the before and after results were about the same. That being said I am at work, where I get a halfway decent signal if I m outside the building. The true test will be when I get home tonight. Aside from network speed being the same everything else seems pretty much unchanged, with the exception of the phone seeming to be a bit more snappy, although it could just be in my head. Lin pack scores did seem a bit higher, but nothing to go crazy over. I have only had one LOS since launch day, so that isnt really an issue.
I just wanted to chime in with my experience after flashing the EK02 modem. I flashed it about 3 hours ago, after I had received 2 LOS at work this morning.. and typically been getting at least 3-4 a day (stock pulled kernel with CMW - Lost kernel was no better)
So far I haven't received any LOS but I've been getting the best 3G speeds I've seen yet. I was getting around 15KBps average in my office (and that is after months of running speed tests!) and I just ran a few tests now and I'm getting ~70KBps after 3 runs. Very noticeable improvement although it isn't spectacular, much more acceptable. I just compared it to my previous speedtest.net result history and it's by far the best speeds I've gotten since I've owned the phone in this same exact location (my desk at work)
Thanks again to everyone involved getting us this leaked firmware!
I don't think so. I was on calks, flashed a stock kernel, took out the undervolt script and still got the reboots.
Again, I never got them on a stock rom, only custom ones.
A liitle background:
I ran BonsaiRom with the EB13 modem for months.
Battery life was great. 3+ days with the "fat" battery.
I've tried 5 or 6 different roms since the sprint GB upgrade, the first of which preferred the EI22 modem so I "upgraded" to EI22.
Since flashing the EI22 modem, battery life is terrible. It may be due to the fact that I live in a low signal area. Battery stats confirm that most battery usage is for phone signal.
I'm now running CM7 and plan on sticking with it. (Is CM7 great or what?)
So my question is, will CM7 work with EB13 even though EI22 is recommended?
btw I've seen signatures in these forums that show people running CM7 with other modems. I'm sure I'll try it anyway but I'm just curious as to you guys experiences.
Yeah, I'm pretty sure the modem is independent of the ROM even in cm7. I'd try using the modem that works best for you in your area.
There has NEVER been a rom that needs a certain modem. Bonsai did, I dunno why though. It should've worked anyway.
sent from my always aosp epic
Thanks for the info guys!
Over the next week I plan on cycling thru different modems to determine the effect on battery life.
Which do you prefer and why. I Basically want the pro's and con's. I know CM10 is not meant for our phones, heck even CM9 for that matter. So im curious... whats your flavor.
How long have you been using JB (either one) and what's your battery like. Or how did you make it better.
What modem works for you and why.
Let's see some screenshots of your battery.
Its not that its not meant for our phones but not officially supported
Sent from my SPH-D710 using Tapatalk 2
Correct. But it does work better on other phones. But you are correct thanks for correcting me.
I am a big CM fan and after using the alphas I strayed and lived on the Unofficial CM9 nightlies for a while. I found those very smooth, but had sub-par battery.
After jumping back to GB for a month or so, I have played with both CM10 and JB AOSP. As expected, CM10 has more customization options while AOSP is very lean. Performance is very similar between the two as there has been a lot of collaboration between the devs and functionality is continually improving VERY fast with each update.
That being said, the only thing I miss on either ROM is bluetooth for media. Everything else that I use is working without issue. Some have reported LOS, but I have not experienced it with a clean data wipe and fresh install. I am still holding on to the EL29 modem, but considering trying a couple of the newer releases.
As for my preference, I am using JB AOSP as my DD at this point because I have experienced VERY good battery life with practical use CM10 seemed to drain a little faster, but it is coming along quite nicely IMO. Moving from Calks GB 3.0 to the JB ROMS lately has not been a dramatic transition in terms of battery and that is saying something.
I hope that is what you were looking for. Either way, IMO you can't go wrong test driving both and seeing which one does it for you.
Edit 1 (AOSP Alpha 5): Bluetooth media has been working since Alpha 4 and it is very stable. With Alpha 5, the screen transition from portrait to landscape (and back) is more responsive as it has been a little slow in the previous builds. This is a very nice build. The battery issue seems to be that the phone does not charge completely but shows 99-100% when disconnecting from the charger. Sbrissen has noted a potential battery fix on Alpha 5. I have not had it long enough to report anything at this point.
jamesissocool said:
I am a big CM fan and after using the alphas I strayed and lived on the Unofficial CM9 nightlies for a while. I found those very smooth, but had sub-par battery.
After jumping back to GB for a month or so, I have played with both CM10 and JB AOSP. As expected, CM10 has more customization options while AOSP is very lean. Performance is very similar between the two as there has been a lot of collaboration between the devs and functionality is continually improving VERY fast with each update.
That being said, the only thing I miss on either ROM is bluetooth for media. Everything else that I use is working without issue. Some have reported LOS, but I have not experienced it with a clean data wipe and fresh install. I am still holding on to the EL29 modem, but considering trying a couple of the newer releases.
As for my preference, I am using JB AOSP as my DD at this point because I have experience VERY good battery life with practical use CM10 seemed to drain a little faster, but it is coming along quite nicely IMO. Moving from Calks GB 3.0 to the JB ROMS lately has not been a dramatic transition in terms of battery and that is saying something.
I hope that is what you were looking for. Either way, IMO you can't go wrong test driving both and seeing which one does it for you.
Click to expand...
Click to collapse
That's exactly what I was looking for thank you sir.
Jelly bean running smoothly
I'm running Sbrissens aosp alpha 3 and its smooth sailing with no known issues so far! Also think its a DD for me,battery is not melting my phone like previous builds.
jamesissocool said:
I am a big CM fan and after using the alphas I strayed and lived on the Unofficial CM9 nightlies for a while. I found those very smooth, but had sub-par battery.
After jumping back to GB for a month or so, I have played with both CM10 and JB AOSP. As expected, CM10 has more customization options while AOSP is very lean. Performance is very similar between the two as there has been a lot of collaboration between the devs and functionality is continually improving VERY fast with each update.
That being said, the only thing I miss on either ROM is bluetooth for media. Everything else that I use is working without issue. Some have reported LOS, but I have not experienced it with a clean data wipe and fresh install. I am still holding on to the EL29 modem, but considering trying a couple of the newer releases.
As for my preference, I am using JB AOSP as my DD at this point because I have experience VERY good battery life with practical use CM10 seemed to drain a little faster, but it is coming along quite nicely IMO. Moving from Calks GB 3.0 to the JB ROMS lately has not been a dramatic transition in terms of battery and that is saying something.
I hope that is what you were looking for. Either way, IMO you can't go wrong test driving both and seeing which one does it for you.
Click to expand...
Click to collapse
I've been waiting for a post like this since Sbrissen released the ROM. Think I shall finally give it a go and see how it runs.
cm10 ftw.
after using cm you'll find it hard to go back to anything else! (unless its aokp)
there is just endless customization options..
cm10 may have more features for me aosp is a lil better far as battery and smoothness i ran both for a lil over a day aosp is the winner
Check out SB's AOSP Alpha 3. All the reviews say it is coming along nicely (almost Beta)
I tried it back when it was private, and it was amazing (other than LOS, which he seemed to have fixed)
So I'm installing it again now.
CM10 vs. AOSP
Well, for me CM does the trick. And when I got the EpTouch and found out it was not supported by CM, I was heartbroken. The Epic Touch is such a wonderful device with its screen, and CPU power; granted there are a number of devices currently better than this phone.
I think CM is a better choice just for how well they support development. I have never had an AOSP ROM before, but I enjoyed being able to boot into recovery from hitting the power button. I even enjoyed playing with a few of the CM settings in the phone.
AOSP is just pure, 100% Android, and is great if that is what you want. But, I still want a little suprises here and there.
Cm is very stable for the epic. They are quite close to official I would say.
Sent from my Nexus 7 using XDA Premium HD app
Nice post, guys. I'm gonna flash cm10 now. Haha.:victory:
What is the best way to go to AOSP from EL29 GB? And of get back to GB if needed?
Sent from my SPH-D710 using Tapatalk 2
bigblue4life said:
What is the best way to go to AOSP from EL29 GB? And of get back to GB if needed?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Use el26 cwm and wipe everything. To go back just use one click.
Well I was running the AOSP build and loved it with the exception that WiFi tether won't work. Can anyone confirm it works on cm10 before I go through the trouble of flashing?
From what I read, Wifi tether is not working on Jellybean right now and have been running CM10 Alpha 4 for over 12 hours now. Let your Rom settle. It takes time to set your accounts back up with syncing and will drain your battery the first cycle. The first battery cycle had 3 hours. I left it off and let it charge over night. I have now had it off the charger for an hour and half and am still at 87%. A huge increase since first cycle. In that same time I have a 1% Time without Cell signal (LOS).... I had this on GB, just b/c I have one tower about 3 miles away that I'm anchored to. If you haven't already I would recommend flashing the new FH13 modem as well.
sekondairy said:
From what I read, Wifi tether is not working on Jellybean right now and have been running CM10 Alpha 4 for over 12 hours now. Let your Rom settle. It takes time to set your accounts back up with syncing and will drain your battery the first cycle. The first battery cycle had 3 hours. I left it off and let it charge over night. I have now had it off the charger for an hour and half and am still at 87%. A huge increase since first cycle. In that same time I have a 1% Time without Cell signal (LOS).... I had this on GB, just b/c I have one tower about 3 miles away that I'm anchored to. If you haven't already I would recommend flashing the new FH13 modem as well.
Click to expand...
Click to collapse
Well, from what i read from your reply is, I dont know what im talking about , yada yada yada.... If you read a little closer it says wifi tether is not working on the AOSP build. I clearly asked above if someone could verify that it is indeed working on the CM10 build. Is that what you are trying to say? Cause no one here said they are having problems with syncing or other accounts.
Cm10 alpha 4 is running great, I was running el29 modem but I had some issues with Los, after I upgraded to fh13 I have not experienced any more Los. also turning off location services gets better battery in deep sleep.
Sent from my SPH-D710 using xda app-developers app
CM10 alpha 4 is not working well for me with LOS issues. I keep getting LOS atleast 4-5 times a day needing a reboot... going to try ASOP.
I'm currently on 4.1 and it is great. However I was considering moving to 4.2 for the new features but judging by many threads with problems on 4.2 I'm starting to reconsider. Is it really as bad as it looks (the battery dying quickly, problems with updating from 4.1, other stuff), or is it worth to update my Gnex?
I'm getting my GNex today. Hope this thread gets answers
There are numerous threads on this subject. Instead of being lazy and having someone answer your question, why don't you actually read the threads? Hell, you've already answered some of your own questions.
Read, read, read and then just when you think you have the answer, read some more. Ultimately, it comes down to your own judgements and opinions.
Yes but what I can see are some individual cases of those things. Or are they? I just want to know if all those things are common in 4.2.
Basically, my question: does anyone who moved from 4.1 to 4.2 regret it in any way?
That question is also answered in all the "i'm going back to 4.1" threads..
As for whether this is a general thing, it is definitely more common with problems than other updates, but as several of us have had no problems at all, it cannot be a problem with 4.2 as such, so it would have to be either
1. a problem with the update process(i made a clean install)
2. a problem with certain hw/sw combinations(there have been reports of a certain error in the latest hw, which has coincided with the update itself)
I dont have any problems with 4.2. Question for u is are u rooted? Stock?
Sent from my Galaxy Nexus using xda premium
Compared my nexus with a friend's and experience is different.
Same exactly clean installation and my phone after 1 day starts lagging but my friend's is smooth as ever..
Maybe slight variation in hardware causes this difference...
Don't know what else to assume..
Sent from my Galaxy Nexus using xda app-developers app
I've tried CM10.1 which is 4.2 and after awhile the phone will stop responding and the screen will turn off. Only way to get it back on is to battery pull, reverted back to 4.1 for now.
I ran stock 4.2 from release to about a week ago, had a few problems at first but after a factory reset I was happy. Only issue was occasionally, maybe after a day, maybe a week, screen would go black right after waking and have to battery pull. But as is not an everyday occurrence I'll stay with 4.2.1 (rasbean) and wait for Google to fix.
Sent from my Galaxy Nexus using xda premium
I suggest get a decent Kernel as many issues are Kernel related. I'm running LeanKernel for the Verizon Galaxy Nexus and everything runs perfect. I have used LeanKernel since the Thunderbolt days and have tried Trinity and Franco. I always end up coming back to Lean Kernel. No SODs, weird lags, rebooting or other issues. The only think I tweaked was bump the GPU to 384, and over clock to 1350 MHz. Plus force the GPU for 2D in the developer settings which have always used since 4.1.