View Single Post
  #1369 (permalink)  
Old 11-15-2009, 05:02 PM
ShadowDrake's Avatar
ShadowDrake
Guest
 
Posts: n/a
Mentioned: Post(s)
Tagged: Thread(s)
Re: [KITCHEN][ROM]->>Nov 9<<6.5 NK-23506-RZ Baseline TF3d 2.1 & Titanium

Quote:
Originally Posted by raidzero View Post
airaves do not produce perfect service. they do not regenerate evdo, therefore your phone will still get hot and battery will suck, will still constantly try to switch between 1x and evdo. the airave only repeats 1x, as you can see when your phone switches to 1x, you get full bars (in a call). I have an airave and it works for calls but does nothing for data. I have had trouble with Touch Pro's shutting down randomly even with a good charged battery, I just go to get my phone and it's off, I turn it on and it has the critical battery message. This has happened on stock ROM, other ROM's a few times with my ROM's too. I think its the radio, I am using the stock sprint radio. With the new release though I am using dcd's sprint carrier package. it comes with a new PRL, which I have to say is a great improvement. it seems crazy, but before I was using dcd's carrier, I had no bars in my house (except when on a call, thanks to airave) but now I have like 3 bars in my house! its crazy. I know signal bars are not all that, but even when I do ##debug#, I see -78dbm rx power! I am a believer than PRL can do a lot now. Anyway my point is I think the behavior you describe is considered normal in Touch Pro world, at least it is for me in my house where I have no service.

edit: Drake, if you don't use my latest nightly kitchen to make yourself a new ROM with the new PRL, I suggest installing dcd's carrier cab or doing a PRL update. see if it helps the situation
I've already got DCD's carrier cab installed - and I flashed the newest Sprint ROM before switching to your kitchen from Juicy's ROMs simply because it contained the latest Sprint PRL.

Yeah, I know the Airave only gives out a 1xrtt signal and it isn't just a repeater. If it were repeating a signal that were in the area it wouldn't work by me, because there's nothing available to repeat :P Interestingly enough, the hardware in the Airave supports EVDO, but it's disabled. Maybe they will enable it with a future firmware update, because I know the other companies femtocells support 3G. Even so, this is definitely unrelated to that though.

I have ZERO EVDO coverage out at my house, so it's 1x only. In the past, and when I first flashed, it worked alright. A couple of days after the flash it will sometimes say EVDO and show full signal, which I know isn't correct... but I figured it was just an icon issue.

It's done the same thing when I'm out and about, at work, where I have decent service (and EVDO coverage). It will be roaming, stuck on 1x, be slow, and get extremely hot. A soft reset (or radio toggle) solves the issue. If I just toggle the radio off and on again, as soon as it switches to 1x for a text, it won't switch back, then it will roam, then it will die. A soft reset was the only "fix" in that it would make it a couple of hours before getting stuck again.

It hasn't happened since I switched to last night's kitchen. Maybe it's a bug of the past.

Which is still giving me intermittent issues too. The Weather settings page didn't display, I just figured it was broken. I did a hard reset here at work because I changed some of my sashimi info around and wanted to start clean. Poof, now the weather page works again, among a few other things. Another hard reset later and it doesn't work again. Seems to be luck of the draw.

Only other issue I'm having is the internet tab in TF3D opens up PIE instead of Opera. Not sure where to change that but this latest manila build still needs some things worked out so I'm not going to worry myself over it quite yet.

Thanks again for your hard work

Oh, also, it was getting stuck in 1x on both the newest Sprint radio and my old favorite, the Telus radio. Was definitely a software issue, but who knows what it was.

Edit: I tried sashimi compliance based on the old thread in their forums about it. It's just a basic version of mortscript (enough to run sashimi). It's supposed to run at the end of the AutoRun. Since you switched to RunCC, it seems to cause some issues. What luck on the timing, huh So, it's not worth worrying about for now, it's only one extra step to run the exe after it's done setting up. I'll just convert all my programs to exts so it's more automated... one of these days.

Last edited by ShadowDrake; 11-15-2009 at 05:06 PM.
Reply With Quote