yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] imex99:
the devs are here but must be no interest to them... you shouldn't give up so fast though! you should also know that most threads end up with more questions/complaining than actually helping out, most here just follow the directions laid out and don't read all the pages bc its 2 much. The search option is also overrated bc it spits out a lot of crap....
[EVO 4G Android Development] regulator207:
no dont give up on this. There is so much going on now with the new root and source release that this is on the afterburner. I would love to have this incorporated into a rom!
[EVO 4G Android Development] zikronix:
didnt we go through this on the hero?
[EVO 4G Android Development] maejrep:
Calling

int networkMode = Settings.Secure.getInt(getContentResolver(), "preferred_network_mode", 8);

gives me networkMode == 4:

from packages/apps/Settings2/src/com/android/settings/RadioInfo.java:

private String[] mPreferredNetworkLabels = {
"WCDMA preferred",
"GSM only",
"WCDMA only",
"GSM auto (PRL)",
"CDMA auto (PRL)",
"CDMA only",
"EvDo only",
"GSM/CDMA auto (PRL)",
"Unknown"};

So the settings provider at least thinks the preferred network mode is what RadioInfo showed: CDMA auto (PRL).

Changing that is not going to be something that a standard app will easily be able to do, as doing what RadioInfo.java does requires a slew of permissions that a standard app can't get access to.

But it actually commits the changes by communicating with the ril daemon. Should be possible to interact with the ril a different way, if just a hack (ie, may only work on the Evo, or something like that)
[EVO 4G Android Development] Ceger:
So it seems that the setting on boot might only have the effect of making the default that shows to be CDMA PRL, but it is actually set to GSM PRL instead. Might be worth checking this out with different ROMs as it might be specific to what you are running.

If it is across all ROMs, then it would probably be best to send this information in to HTC/Sprint to make them aware that the setting is not working correctly. I am sure they would love to get better battery life as a known fact. Wonder if this was fixed with the latest OTA/Radio.

Ceger
[EVO 4G Android Development] xak944:
I am currently running Fresh 0.3 and baseband 2.05.00.06.10. I definitely can confirm the battery was being negatively affected on the stock ROM and Fresh 0.2 as well. I can try to find time to take a nandroid backup and test another ROM if you'd like me to test something specific, just let me know what.

Thanks!

edit: Yay, I can haz signaturez nao!
[EVO 4G Android Development] WillJitsu:
Where do you find the "Time without Signal" value?
[EVO 4G Android Development] Ceger:
Unfortunately, Fresh is pre-OTA. You might want to try rooted OTA based ROM or one of the others.

Ceger
[EVO 4G Android Development] xak944:
Is there any evidence that this is fixed in the OTA? Could someone running it and familiar with this issue please confirm their "Time without signal" value and battery life?

I really hope it's fixed... I'd be really happy not having to figure out a hacked fix :p
[EVO 4G Android Development] Ceger:
Same boat as I am on Fresh 0.5.3. Waiting for the OTA update.

I might try BakedSnack 9.5 though.

Ceger
[EVO 4G Android Development] acrh2:
Since this morning, for no reason whatsoever, I've been getting 100% TWS and severe battery drain in standby. Basically, cell standby drain is about 3 times normal.

Has anything changed while we were sleeping?

Any ideas?
[EVO 4G Android Development] Stochasticity:
Go to Settings ---> About Phone --> Battery --> Battery use --> select "Cell Standby". Time without signal will here; roughly in the middle.
[EVO 4G Android Development] dmc971989:
i have yet to see a rom this wasnt a problem on (excluding froyo, apparently)

and i have also yet to see anyone who really didnt have this problem, ive just seen people who didnt check for it properly

we have been emailing sprint/htc about this exact issue since the hero days... and they have yet to even acknowledge the issue.

I HIGHLY doubt they would have fixed it in the most recent OTA considering they have made no mention of it at all
[EVO 4G Android Development] xak944:
Thank you for your entirely on-topic, sensible, and informed post. Hope everyone reads it.

Cheers!
[EVO 4G Android Development] dschoenike:
ive been following this thread (very interesting) and finally looked at my "time without signal". After 8 hours of driving (my job) im at 3% without signal. im guessing this issue isnt affecting me.? sorry for not really adding anything except for my stats.

dschoenike

oh yeah, evo hardware ver 003 running freah .3 rom, 1.2 oc kernel
[EVO 4G Android Development] Jeffrey_L:
not fixed in OTA

I can confirm that I installed the OTA (running 1.47.651.1 build no. CL195459). The install was done automatically on 6/28/10, and I am still having problems with very high Time Without Service. Last night was 52%.

The prior post that talks about driving without problems is a different type of situation than many of us are facing. When I drive around, I have very little problem keeping a signal (TWS is < 5%, and usually -zero-). It is when my phone sits at home on the counter all night that the TWS goes through the roof.

The problem is that I live in an area with a very weak Sprint signal (even though I can see 2 cell towers from my house . . . grrrrr . . . ). When my phone sits idle over night, it cannot hold a signal and tries to bounce around looking for a stronger connection. The result is a huge drain on battery life and very high Time Without Signal.

- Jeff
[EVO 4G Android Development] xak944:
Indeed, it is difficult to troubleshoot this issue in an area or situation that is prone to a weak signal :-(

As dmc971989 said though, nobody has definitively confirmed that the issue is fixed in any ROM, despite many people having misinformation about how to truly determine if they are affected.

I spent some time watching 'logcat -b radio' while messing with all combinations of setting the radio, but it's inconclusive. There is no consistency between log entries that appear on boot and when setting the radio through the Testing menu. I suspect that we still may need to somehow call ril_func_prefer_network_type_set(), a.k.a. REQUEST_SET_PREFERRED_NETWORK_TYPE. But I don't know how to do that :rolleyes:
[EVO 4G Android Development] rawdikrik:
IM watching this closely as I could definitely use some more battery life.

I just checked my TWS (thanks for the instructions) and found that I have 0%.

I usually have very good signal wherever I am, and havent really seen a problem.

I am using Baked Snack 9.5 with the updated Radio and Wimax.

Just wanted to share my experiences incase it helps.
[EVO 4G Android Development] acrh2:
If your phone is afflicted with TWS > 0, try this procedure.

1) In dialer, dial *#*#4636#*#* to enter "Testing" app.

2) Under Phone Information, set Set preferred network type to CDMA only.

3) Exit Testing by pressing "back" key.

4) Enter Testing again.

5) Set network to CDMA auto (PRL).

6) Exit Testing again.

This fixed my TWS, and the settings stick on reboot.
[EVO 4G Android Development] xak944:
I was really hopeful that this would work, but I can't get it to survive a reboot. However, it does appear that the Select radio band/force-close procedure is not necessary, just following your steps seems to correctly set the radio.

How are you verifying that it survives a reboot on your device? Simply by a low TWS value? And with what ROM & radios?
[EVO 4G Android Development] acrh2:
By zero TWS value. And about 1% an hour charge drop rate in standby. Before rebooting, the first time I tried this procedure, I did check logcat -b radio to make sure that the preferred network was set correctly. After rebooting (many times now), tws remains at 0.

Latest stock rooted rom, latest radio/wimax, 2a epson kernel to unlock fps.
[EVO 4G Android Development] Evo1X:
I confused

While some may have this problem, I have tried several roms and after getting the WiMax fixed with the newest radio, I'm getting 24 hours with 4G on, I don't always have WiFi on, but everything else is pretty much stock.

If you're only getting a couple of hours, have you considered your phone is simply "broken"? Why not try exchanging it?

Originally I was getting 4-6 hours with WiMax on. With the last Radio and Wimax update, life is good...

IMHO...your mileage obviously has varied..
[EVO 4G Android Development] sblum:
Where exactly can I check my TWS? Thanks...

Oops, missed it on the previous page.
[EVO 4G Android Development] xak944:
Could you paste the output lines from your radio log where you're confirming this? I'm having trouble determining which ones actually indicate the radio is being properly set.

Thanks!
[EVO 4G Android Development] xak944:
I am running EVO_Radio_2.05.00.06.10, however EVO_WiMAX_25641_R01 and EVO_WiMAX_25043_R04 caused my 4G to stop working. I had to downgrade back to EVO_WiMAX_24722. Are you using one of these or another one? Also, which ROM did you end up using?

I did try to swap my unit a few weeks ago, and Sprint told me they would absolutely not replace it because of a battery issue, that this is normal for the device. Plus, they didn't even have any other Evos to swap with. They did offer to install ATK and "help me with my settings"... :mad:

Glad to hear that your original battery life was similar to mine and that you were able to fix it, although I'm hesitant to think that the 4G radio has anything to do with it. I only turn my 4G on maybe once or twice a week when I'm tethering or downloading something huge, and it's usually also charging. It is also my understanding that the CDMA/GSM radio has nothing to do with 4G/WiMax.
[EVO 4G Android Development] Evo1X:
My original batter life was only truly miserable with 4g on. With it off, I was good for more than 16 hours, probably not the 24+ I'm getting now. I did much the same as you, only turned 4G on when I needed it, then I had "decent" battery life. Now I can leave 4G on (don't use bluetooth, so it's off as well as wifi) but 4G now only seems to slightly limit battery life. I suspect about 24 hours with it on and 28 or so with it off.

To sum it up, I think your battery situation was worse than mine from the start. One other thing, I only have the Rev 2 hardware. I'd bet the rev3 is probaby slightly better with power, but I haven't seen much to justify that thought.

In case I didn't mention it, my CDMA settings are and have been correct....

Again, just wonding if there isn't something wrong with your unit.
[EVO 4G Android Development] sblum:
So, my TWS was 6% for so far today. I checked my settings and it was already on "CDMA auto". I set it to CDMA only and back, then updated my PRS... I feel like my battery life is already OK (55% after 6.5 hours with moderate use) but I am already using Fresh with setcpu and would like to believe it could be better.

Edit: Flashed the latest radio. Maybe this was the step I was missing! Will update later with my TWS.
[EVO 4G Android Development] justinisyoung:
i've noticed something that may give a lead to this problem.

i've been using avalaunchmod's evolutionv9 froyo rom for awhile now, but i've always been using ffolkes's kernel with the T2 timings to increase the screen's frame rate to around 50.

after HTC released the evo's kernel source, ffolkes rebuilt the kernel from the official HTC source, but camera still didn't work for froyo roms so i stuck with the one built from toast's hacked incredible source because i could reliably get 50+ frames per second, as opposed to the 40 i'd get with ffolkes's v5 kernel (uses official evo kernel).

anyways, i decided to flash the v5 kernel today and along with losing those extra frames per second, i noticed that my battery was draining noticeably faster than it was when i was using his kernel based on the incredible source. i checked the TWS and it was at 50%, which means that the preferred network was set to GSM. i flashed back to the old kernel(again, built from incredible source) and when i checked the TWS for that, the TWS was 0%.

that means that this problem is likely not something that any app can just fix. it's definitely something in the kernel that's causing this. interestingly enough, kernels built from the HTC Incredible source with the evo's board files don't have the TWS problem, only the official evo kernels do.

strange.
[EVO 4G Android Development] bigdogdan2:
If you know any developers working with the official evo kernel, let them know what you've found. They might have some additional insight.
[EVO 4G Android Development] ejittles:
Really? You think the devs around here wouldn't know how to properly check for the condition? I've been unplugged for 6 hours and 19 minutes and have a TWS of exactly 0%. I have never set my phone to CDMA but yes I have checked.

To be honest, I think that it is the "force close" that is making you think it's an issue. Don't you think that after making app crashes that there could be some sort of glitch in the software that causes it to come up as GSM?

It's a network issue plain and simple. Why do I say that? Because I'm on vacation and it's at 0% and when I am at home (in an area w/ poor network despite the phone always appearing to have at least 2 bars) it hovers around 50%.
[EVO 4G Android Development] justinisyoung:
well, i doubt it's a network issue as in it's Sprint's fault. if you read my earlier post, you'll see how for me at least, the TWS problem depends on the kernel. i kept my phone at the exact same spot at my home and saw that i'd get 50% TWS with some kernels and 0% TWS with other kernels.
[EVO 4G Android Development] hoshmosh:
id love to see this get fix....
[EVO 4G Android Development] wmstwo002:
I read somewhere that the SMS app uses GSM stacks to send/recieve messages.
[EVO 4G Android Development] Geniusdog254:
This is turning into one of those "my brother told me his friend's cousin's sister's cat walked on his phone and then it had FroYo" type threads.

This phone isn't doing ANYTHING with GSM. It just isn't possible.

Let me spell it out. The field test app was originally designed for GSM phones, thus it expects it to be on GSM by default. CDMA support was added later. When you make the app crash, it reverts to the default settings.

Call it sloppy coding, call it whatever you want, but it is not searching for a GSM network just because the app says so. It can pass that arg to the radio all it wants, but the radio will deny it, since it isn't GSM!

When you make an app crash, expect things to go wrong. If you think that it's an issue, mayyybee you shouldn't make the app crash!

EDIT: Also, don't take this as being rude. I'm saying that if you make an app crash, it won't work right. Thats the meaning of a crash. You're grasping at straws trying to find out why your phone drops service sometimes. There may be an issue, but it isn't because of this.
[EVO 4G Android Development] ejittles:
Try switching to a Verizon PRL and you'll probably see your TWS go down to 0-10%. That is what I did to verify that this is not an issue with the phone itself. I switched back to a Sprint PRL though as I don't want to be on Verizon's towers 100% of the time.
[EVO 4G Android Development] tempe38:
Look here (In dialer, dial *#*#4636#*#* to enter "Testing" app), right? Mine was already set to auto CDMA, I didn't have to change anything. TWS for me is usually 3% or less, completely stock and updated.
[EVO 4G Android Development] sflotr:
Your steps worked on my phone. Thanks for your input.:)
[EVO 4G Android Development] SouL Shadow:
I'd have to agree that the testing app is just showing wrong info after a crash. To directly see the settings your phone is using open a terminal and run "getprop"

(Expect over 300 lines of output)

There are multiple properties that clearly show the phone is solely operating on sprint's cdma network.

I too have noticed horrible service in areas that used to be good, both at my home and as I drive throughout Connecticut for work. I've really only seen the difference since around the time the newest radio came out. However I have compared 2 different evo's, with different radio's, getting the same level of service.

I haven't checked in a while, but there could be higher then usual solar or cosmic interference. We've enjoyed a longer then usual solar minimum and if there had been increased activity lately that could account for some of the recent fluctuations. Of course this is pure speculation on my part, but scientifically possible.

-SLS-
[EVO 4G Android Development] aaron580:
hmm... mine has no network 95% of the time according to batt info.
[EVO 4G Android Development] jrmithdobbs:
Froyo's cdma stuff seems to fix this. Averaging 4-6% w/o signal in places I was previously getting 45%+ using the cm6 nightlies.

Without performing the manual workaround.
[EVO 4G Android Development] cmdeforest:
I have a friend who just pruchased the EVO and did the 2.2 android update before he did this... We found the code *#*#4636#*#* does not work to gain access to this menu... anyone know the code for the 2.2 release? or is it even needed?

Thanks for any help.
[EVO 4G Android Development] ray90813:
I think there's an app on the market called network that will allow you to check and change the settings without using the dialer method.
[EVO 4G Android Development] ms79723:
ive been lookin for that app in the market for the longest, cannot find it
[EVO 4G Android Development] thedudejdog:
is not in the market. anymore
[EVO 4G Android Development] mikeinghilterra:
I just downloaded using appbrain send a pm if you can't find it and ill upload the apk
[EVO 4G Android Development] xHausx:
have you guys tried editing the build.prop file and changing the preferred/default network?

it should look something like:

rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network = 4
ro.telephony.default_network = 4
[Windows Mobile] shafizal:
hello to all i have cooked a french rom with 1.8 htc mesage client from OBOE rom...i have these packages from OBOE rom :

Htc message client1.8

Menu Enhancement

after flash i have a problem when i want to copy and paste my message i have some stange charecters please see the pictures:

and when i click menu there is one one ligne is missing please see the screenshot:

and i checked with othere roms in that ligne they have "Secured Box"

like i have used the 1.8 message client it had inbox secure so are i mise something dependies for 1.8 message client??

thanks to all
[Windows Mobile] miniterror:
i think you need to tr a different textselection package

maybe the same one as where you got the htc messgaing from
[Windows Mobile] starbase64:
Hi,

all mui files checked? I had a similar error.

with friendly greet

starbase64
[Windows Mobile] shafizal:
thanks for the confirmation ..;so i am not the one having this problem...is there is any solution????
[Windows Mobile] shafizal:
thanks i solved the problem in my first screenshot buy traducting the CCPCustomize.dll
[Windows Mobile] shafizal:
are i miss something for the "Secured box" in message client because i dont have this option?
[Windows Mobile] starbase64:
Hi,

is secure box activated?

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Menu]
"SecureMode"=dword:00000001

with friendly greet

starbase64
[Windows Mobile] shafizal:
thanks i tried to change the reg to 1 but after reset it change to 0 and still have same problem
[Windows Mobile] starbase64:
Hi,

attached is my complete HTCMessaging_Client_1_8_20164224_00.

More files and also wwe mui´s can you finde here: http://xdaforums.com/showthread.php?t=700495

with friendly greet

starbase64
[Windows Mobile] totalcmdext:
Where did you found the file MessagingService.dll because it is deifferent from the Huashan/Oboe file?
[Windows Mobile] shafizal:
thanks bro when i swap directly these packages it shows the secured box but after i traducted to my language it does not shown the secured box this time i dont have the blank box........
[Windows Mobile] starbase64:
Hi,

here is a new Hotfix OEM Package with many languages:

http://xdaforums.com/showpost.php?p=7100261&postcount=25

with friendly greet

starbase64
[Windows Mobile] totalcmdext:
This hotfix include the Secure Mode for the HTCMessaging_Client_1_5_20111932_00 package (1.66.xx)?

I have tried to install but wasn't possible to activate the SecureMode
[Windows Mobile] starbase64:
Hi,

the mui files from last messaging hotfix contains secure box, but i have not tested.

with friendly greet

starbase64
[Windows Mobile] shafizal:
thank u vry much bro now its works great ....i think i have messed some line in traduction .....
[Android Themes] hebdenlad:
Hi there,

Am a newbie to HTC Desire and wonder how I can change my boot screen (currently T-mobile0 to something else (am a vodafone user).

Any ideas or pointers very welcome.

Cheers,

Phil
[Android Themes] Daneshm90:
Dont have a htc desire so not too sure. But its one of two :

1. Theres a bootanimation.zip in /system/media/

2. Theres a couple of animated gifs inside /system/media/boot*
[XPERIA X10 General] 10123:
Post any good X10 deals, preferably PAYG.

.....

CEX- Second hand phones http://www.cex.co.uk/products/Phone...ed/index.php?rad_which_stock=1&stext=sony+x10

Mint - Working phone in as new/mint condition. Complete with original box and accessories as sold new. Unlocked- £310

Good - Working phone in good condition with slight cosmetic blemishes. Charger supplied. If the phone includes a music player/radio then it is supplied with headphones. If the phone has PDA functionality a sync cable and/or docking cradle is supplied. Missing original packaging. Unlocked- £275

Poor - Working phone in poor cosmetic condition. Original or 3rd party charger supplied but missing accessories and original packaging. Unlocked- £225

They are around £50 cheaper when locked to a network and have around 180 online to purchase in total, and around 300 in stores.
[XPERIA X10 General] JoelMan1121:
Aha I work at cex in Leeds UK.

Sent from my X10i
[XPERIA X10 General] 10123:
I live in Leeds as-well!!!
[Nexus One Q&A, Help & Troubleshooting] jblazea50:
I searched and read through some of the threads and really didn't find a conclusive answer to what I am looking for. So I decided to create a new thread.

My question is: Is there any way to root the N1 that has Stock FRF91? I'm not a noob in rooting, just wanted to make sure. I don't really care about unlocking the bootloader (warranty isn't an issue for me).

Can I just use the fastboot oem unlock command to unlock bootloader then install the custom recovery and install custom roms? Or is there a new method to rooting Stock FRF91 currently.

Thanks
[Nexus One Q&A, Help & Troubleshooting] Frankenstooge:
Yes.

http://xdaforums.com/showthread.php?t=715798

You're welcome. Get familiar with the search tool.
[Nexus One Q&A, Help & Troubleshooting] ecapox:
The instructions in that link wont work for stock FRF91 with stock recovery. I couldnt get the Amon recovery to load onto my phone in order to flash the root. I have tried to ADB it 5 times and each time it says successful, but when i go into recovery all i get is the android with the !.

By all means OP, you can try this and if you get it to work, let me know what you did. I tried 5 times and couldnt get it to work.

my bootloader is unlocked also.
[Nexus One Q&A, Help & Troubleshooting] jblazea50:
after you pushed custom recovery, did you press Volume Down button while rebooting to go directly into recovery? because after you install custom recovery and let the phone reboot, the stock recovery will remain; you should try to go into recovery immediately after pushing the amon ra recovery without letting the phone boot up

let me know if that works
[Nexus One Q&A, Help & Troubleshooting] carbeyaz:
What is the method for rooting "without using SDK tools"? There are emulator apps in the market but they refuse to work without super user permissions? I have stock frf91 and looking for a way to root my nexus one?
[Nexus One Q&A, Help & Troubleshooting] ecapox:
that did it sir. thank you. Was it like this in 2.1? I dont remember having it revery back to stock recovery when following the tutorials. Then again maybe i never let it completely boot back up...