yashsingh1/xdaforums huggingface dataset:
[EVO 4G Accessories] evoflorida:
Sirchuk - here's what i found

Pricing

Sprint AIRAVE Base Station - $99.99/each (requires activation at time of purchase and subscription to an AIRAVE plan. Excludes taxes.)

AIRAVE Enhanced Coverage Charge - $4.99/mo. (required per AIRAVE unit)**

Single Line Unlimited Calling Plan (optional) - $10/mo. per account**

Multi-Line (multiple phones sharing minutes on one account) Unlimited Calling Plan (optional) - $20/mo. per account**
[EVO 4G Accessories] evoflorida:
Samzebian the ONE YX400-P is Sprint friendly.

see chart half way down on

http://www.wi-ex.com/solutions.aspx
[EVO 4G Accessories] Sirchuk:
Ahh, okay, so it's an extra $5 a month just to use. I would probably pay the $10 for unlimited talk in the home as well, so for the extra $150 you spend on the device you can get unlimited talk from home for 10 months.

Also, I've heard that if you go into your local store and talk about how bad your service is at home, they will sometimes either give you the airave for free or wave the $5 monthly fee. It's worth a shot!
[EVO 4G Accessories] dwertz:
I have the Airave but I paid $99 and they comp me the $5 per month so I get for free.

I would say that antenna would be nice in a car with a AC converter. Hopefully less dropped calls in specific dead spots.
[EVO 4G Accessories] kwajr:
On the airave note

It just doesn't work everywhere the gave me one for free in bc but moved to va and it don't work

Sent from my Evo on on the Now network from Sprint

oh and duck Apple
[EVO 4G Accessories] illmaticone:
i got the airave completely free and monthly fee credited.

i would try that first since its no out of pocket expensive and im sure ull be happy with the results.
[EVO 4G Accessories] Droga:
How did you get them to do that? I tried when I got my Evo, and it was a no-go. They didnt even offer it at all. :mad:
[EVO 4G Accessories] Slappy_G:
My guess is he spoke to someone in Retentions...
[EVO 4G Accessories] foxgrey:
I've posted this on the actaul sprint forums, all the good that did me :mad:

I have terrible reception in only one place that I use my phone. My house. I called sprint went through the run around and they determined that the only thing that would help is the airwave unit. The person on the phone started to offer it to me for free, then decided that since I am a new customer they will not send me one. Instead I have to pay for it.

That in on itself isn't terrible, except that its really stupid I have to pay extra a month to use my current broadband, a service that I already pay for, to be able to make use of my cell plan that I already pay for.

Anyway, way to go sprint. Driving away new customers before I pay for this ridiculous data plan. :rolleyes:
[EVO 4G Accessories] evoflorida:
thanks for all the tips. but i order the booster because i wanted 2 uses. home and truck.
[Touch Pro2, Tilt 2 Windows Mobile General] DisneyF1:
Hey all,

I took a picture with my TP2 and when viewing it later hit the trash can button...

My pics are stored on SD and I have used ZAR to get all pics it sees but this one is not in there.

Googled my buttoff and checked the forums, but I can't find anything that helps. Any ideas?

Thanks,

DF1
[Touch Pro2, Tilt 2 Windows Mobile General] lufc:
You need to have a SD Card recovery I am not at my pc at present but when i am i will send you the link to a good one :)
[Touch Pro2, Tilt 2 Windows Mobile General] arrrghhh:
lol, way to drag up an old thread :rolleyes:.
[Touch Pro2, Tilt 2 Windows Mobile General] sussana:
How to recover memory card? is the common question arises, when you accidentally delete your memorable pictures from memory card. In order to recover deleted photos from memory card, you need to use relevant recovery software. I have used memory card recovery software to recover accidentally deleted pictures from my SD card. This software can also recover lost pictures from different types of memory cards like XD cards, MMC, CF cards etc. This software is capable of recovering different types of files from accidentally formatted memory cards. You can download free demo version of this software, where you can preview recovered pictures. If you find your deleted pictures then use full version of this software to save recovered pictures.
[Touch Pro2, Tilt 2 Windows Mobile General] wizardknight:
Wholly necro thread batman. Only 2+ years ago it was last written in. :eek:

I won't even start in on how this is not a iPhone/iPad/iPod touch thread, and that no one here uses iOS.
[HTC Aria Themes and Apps] FtaWolf:
Can anyone let me know if this app Funambol works on HTC Aria from AT&T .

That way it help make my mine up to get one these Aria's...

Thats ok fellows I found my answer..
[Nexus One Q&A, Help & Troubleshooting] JAW$:
Hi,

I have just updated my Nexus One to Stock FRF91 in the last few days & I keep dropping signal on call. Has anybody else experienced these problems.

I bought my Nexus one when it was first released from Google's webstore.

I have checked the radio version on my phone & it is a U version. I heard that there is two versions of radio i.e. H & U & I was wondering what version was for the UK.

I would appreciate some help.

I am on O2 UK.

Thanks

JAW$
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] bodybuilder27:
quick screen and everything else ok, just i'm using Cookie GTX Themed (white theme) rom and when i click start, background is white, but so id font!!!

Any ideas how i change font in start menu icons to black???

cheers

Matt
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] watcher64:
I am not 100% on this , but I think it has to do with the theme that is loaded, so you would have to create a theme, or copy an existing one and use a tool that edits windows mobile themes ....
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] conantroutman:
this ones a bit of a pain in the ass.... im sure theres a simple way to do it, just haven't found it yet...

my quick fix, set a dark lockscreen background....

not a great solution but its all ive got I'm afraid....

as watcher mentioned you can edit the themes....

theres also a method which involves editing one of the system files that I found whilst searching for a solution.....

best of luck.....
[G1 Android Development] lbcoder:
I've been thinking about bricks recently.

The common brick is caused by a failure to boot the recovery system in conjunction with having the command field of the MISC partition set to "boot-recovery".

When the command field is set to boot-recovery, the SPL will ***IGNORE*** the boot-time signals for altering the boot mode, such as the BACK or CAMERA buttons to go into FASTBOOT.

When a recovery fails to boot, it will NOT clear the command field as a successful boot will, hence it will always try to boot into the broken recovery, and nothing you do will break it out.... bricked.

In general, it is my belief that having the recovery fail to boot ***FOR ANY REASON*** will have the same effect.

Yes, a REALLY broken recovery will convince the SPL to skip straight to fastboot. Unfortunately, a PARTLY working recovery will NOT, i.e. it just needs to be good enough that the SPL can recognize a recovery image.

There are many reasons why a recovery partition can fail to boot!

A recent observation by FIRERAT is that the CM5.0.8 kernel WILL NOT successfully boot a phone with 0.95.3000 *when flashed*. It *will* boot it using "fastboot boot"... which adds to the danger since the typical testing procedure IS to "fastboot boot". The second observation is that it works perfectly with 1.33.2003, which actually uses the SAME PARTITION TABLE as 0.95.3000.

So if someone builds a recovery using the CM5.0.8 kernel, you could have a brick factory.

The process that would brick a phone is this:

From the SYSTEM, flash the recovery image, then "reboot recovery". You are now bricked. And this, of course, is a very common process.

This is my WARNING about building custom recovery images:

1) Testing the image using "fastboot boot" is ***NOT ADEQUATE***. It MUST be tested by being FLASHED.

2) You can safely test it by NOT doing ANYTHING that will set the command field to "boot-recovery".... i.e. flash the image, and do a NORMAL reboot holding the HOME button.

3) Recovery image MUST be EXTENSIVELY TESTED... 0.95.x000, 1.33.2003, 1.33.2005. I suggest that YOU THE USER test your recovery image when you install it!

Further thought: It is seeming more and more that the simple presence of a recovery image is the cause of bricks. Since a BLANK recovery image will convince the SPL to jump into fastboot, I suggest that it might just be a really good idea to keep your recovery blank. As long as you have FASTBOOT, you can always "fastboot boot recovery.img" with no chance of bricking.

So... in rooting, the first step is to install SOME SPL with fastboot... i.e. 1.33.2003 or 0.95.3000. The second step for added security is to wipe out your recovery partition.

Note: This is by no means to be taken as a negative with respect to the CM image or kernel. There is nothing particularly wrong with it or dangerous about it since it was never *INTENDED* that that kernel be used for a recovery. Breaking your boot partition is never a problem since you have fastboot waiting to save the day.
[G1 Android Development] jtroye32:
Is it possible to build an spl that always allows access to fastboot?
[G1 Android Development] lbcoder:
Possible? Certainly.

The problem is in convincing EVERYONE to actually INSTALL it.

Keep in mind that there are a LOT of people who still use the 0.95.0000 SPL (stock dream no fastboot), despite all the information everywhere saying that they should have *SOME* kind of engineering SPL.

The RECOVERY is a much easier place to play, for several reasons;

1) flashing the recovery feels "safer".

2) everybody's doing it ;)

3) SOURCE CODE!!! (rather than decompile/reverse engineer/hack).

If the recovery was made to be SAFE (which includes being GONE), then a severe oversight in the SPL design loses its teeth.
[G1 Android Development] Tony_SpaZ:
You could always get devs to recommend a hacked SPL with that functionality. I mean, there's so many people with Danger now, when it used to be only people playing with ports.
[G1 Android Development] lbcoder:
You can recommend whatever you want. There is NOTHING you can do to make people use it.

Recovery on the other hand... well that's fairly easy.... you can enforce a custom recovery with a custom update-script much more completely than you can enforce a particular SPL.... and people are MUCH more comfortable with flashing a custom recovery than a custom SPL since they figure that the SPL is still there to protect them! For that matter, there are VERY FEW recoveries that would need to be modified in order to cover EVERYBODY -- most importantly, amon-ra and clockwork. The old recoveries (jf, cm) don't matter much since nobody is pushing them.... even CM recommends amon-ra and clockwork over his recovery.

And then to force everybody to use a single SPL? Well *right now* there are TONS of SPLs in use! You want to shut the door on all of them?

Fact is simple. I am NOT suggesting that you don't go hack up a custom "safe" SPL. In fact I ENCOURAGE it. I don't think you CAN though -- otherwise you wouldn't be asking for it. Find somebody who CAN -- hint: not too many around, ezterry is one of those few, he even mentioned that he WANTED to, but it is FAR from trivial.

Hint 2: 1.33.2003 is probably your best starting point... it seems to have the greatest universal compatibility of ALL the available SPLs.... it boots kernels incompatible with 0.95 and its compatible with radios incompatible with 1.33.2005.

But this does NOT eliminate the need for a safe RECOVERY, because FACE IT -- the RECOVERY is where the bricking ACTUALLY OCCURS.
[G1 Android Development] jubeh:
Ok, this caught my attention.

I like your idea of working without recovery. Rom updates could force either the install of a "safe" recovery (I assume that that's why AOSP and official builds include recovery images and force-flash them), or just format the recovery partition entirely without writing anything back.

It would also force people to use an engineering SPL since any work that you might have to do through recovery would have to be done through fastboot boot recovery.

I see one problem, though. Say you're a person who has 0.95 SPL, you pick up a rom that force-removes recovery, and you finish flashing the rom. Now you're sans recovery and with an SPL that can't fastboot boot. Your only option at this point is to flash recovery through system, and that has a chance (if the "dev" who packed the forced recovery is an idiot) of bricking your phone.

A better choice would be to force-flash an SPL that's safe to use (1.33+), but I don't know if that can be done from an OTA package.

Let's face it. If a person bricks a phone, it's usually because they're dumb, so we can't realistically expect a person to learn to use fastboot boot recovery any time they have to flash a new rom.

I believe the force-flash SPL is a better option.
[G1 Android Development] Firerat:
whenever I switch from 0.95.xxxx to 1.33.xxxx I

fastboot erase system -w

fastboot erase recovery

fastboot boot recovery.img

flash spl-1.33.xxxx.zip

fastboot boot recovery.img

seems the safest way
[G1 Android Development] the_fish:
good to know! thanks for the warning :) i really love how much you guys care about the community and this kind of.... obsolete? phone :)
[G1 Android Development] lbcoder:
I wouldn't want to FORCE erase the recovery when installing a system image... that would be silly since the recovery failure is related to the radio and spl and NOT the system image.

You are also missing one option for a 0.95.0000 SPL (note that 0.95.3000 is also a 0.95 SPL, but has fastboot, so blank recovery OK there) is NBH files.

Best way to erase a recovery is through fastboot. This has the added benefit of ensuring that you HAVE fastboot.
[G1 Android Development] lbcoder:
Obsolete? Nope. Not even close. The defining characteristic of obsolete is that it is not able to perform the required function. This hardware still works great and 2.2 is supposed to be even better on it.
[G1 Android Development] lbcoder:
That appears to be quite safe ;)

It should even withstand a radio/spl mismatch (1.x radio + 1.33.2005 SPL or 3.x radio + SPL < 1.33.2005)
[G1 Android Development] Firerat:
been thinking, I'm not sure it is quite as dangerous

Clockwork ROM Manager reboots to recovery

and we know that we don't get bricks when it fails to flash recovery via cm5.0.7test5+ based ROM

does that set the boot flag in the same way?
[G1 Android Development] lbcoder:
When it fails to flash recovery, it must be leaving it in the OLD state, or in a so-dead-the-SPL-can-see-it state.
[G1 Android Development] relevent81:
what about suggesting that you should *never* use the reboot recovery command from shell? its easier than suggesting a new spl, and its a guarantee against stupidly bricking your phone.

$.02, and im gone.
[G1 Android Development] lbcoder:
Because reboot-recovery can also be set from update-radio and update-hboot. This is where the REAL danger comes in -- if it didn't do that, then there wouldn't be nearly as many deathspl bricks -- it would look nice and bricked, but still respond perfectly to back/camera, which would bring up fastboot and offer the cure -- especially since 1.33.2005 is actually a strong SPL that can fastboot flash both radio and SPL.
[G1 Android Development] rpmccormick:
My thoughts exactly. I had Clockwork running fine installed from a test4 rom. I wiped and upgraded to a 5.0.8 rom (via clockwork), and then on the new install Clockwork forced me to re-install the recovery again in order to use it. I did that and rebooted in to it and almost had a heart attack when it was stuck on G1. After a battery pull it started up fine again. I flashed clockwork yet again through the app, rebooted, and all is normal again. Whew.

Now this thread is saying that the first time clockwork flashed its recovery it messed it up so bad even the header that tells SPL it is a recovery was broken, but it it had that header correct I would have been bricked? ...and sorry for OT, but why did the recovery flash fine the second time through ROM manager? How are you supposed to flash a recovery in a 5.0.8cm branch?
[G1 Android Development] Firerat:
flash recovery via fastboot or recovery
[G1 Android Development] juangil:
@Firerat

not sure it belongs to this thread but am trying to use MTD 70 2 on LeFeuDeDieu v2.5.1 which uses CM 5.0.8 and I haven't been able to make it boot (on previous version 2.4) I am about to try v2.5.1, any help will be appreciated as always
[G1 Android Development] Ace42:
For me i must do this if I want it to boot! I have clockwork now, not amon_ra

-Goto rec, Flash 1-1 recovery of MTD.zip thing

-wipe everything(exc batt stats)

-reboot recovery

-flash rom, then any xtras

-flash the boot MTD file.zip(version 1)

My Partition is, 3-cache, 90-sys, rest-data
[G1 Android Development] juangil:
thanks, I'll try that

1 more Question (I know am on the wrong thread sorry:o)

how about no wipe updates? will that affect the new partition or should I flash the boot MTD again?

thx
[G1 Android Development] Ace42:
Im not completely sure, if the no-wipe has a boot.img it might change your partitions to the def ones. If it have a boot.img then you should be fine.
[G1 Android Development] juangil:
cool, thanks Ace:p
[G1 Android Development] ezterry:
For cm5 you look good:

Flash cm update then reflash boot hack from partition hacked recovery
[Galaxy S I9000 Themes and Apps] FrezoreR:
Hi Guys!

Thought I'd share this one!

I will also attach the android wallpaper in the same fashion I did yesterday, if you've missed it!

Cheers!
[Galaxy S I9000 Themes and Apps] jUsT2eXy:
very very nice

looks great on the phone :p
[Galaxy S I9000 Themes and Apps] Ferdimage:
thanx buddy very cute and slick!

edit: shame they are low res..looks too blurry for my picky eyes.. but keep up the good work and thanks
[Galaxy S I9000 Themes and Apps] FrezoreR:
low res?

they are made to fit the WVGA, so if it seems blurry it could be due to the glow of the S?
[Galaxy S I9000 Themes and Apps] zgmf-x322a:
nice, i like the wallpapr :D
[Galaxy S I9000 Themes and Apps] NZtechfreak:
They should be 960x800 for wallpaper, could be why they don't seem sharp enough...
[Galaxy S I9000 Themes and Apps] sensi_:
yea good job mate but im guessing they are phone wallpapers.

you could render them larger so we can have them on our desktops :P defo!
[Galaxy S I9000 Themes and Apps] arnonrgo:
Looks great. Thanks
[Galaxy S I9000 Themes and Apps] zipolly:
wallpaper

hi

how do i actually get this ?

cheers
[Galaxy S I9000 Themes and Apps] littlephoenix:
great work, here is the same one i modified and put some color and carbon fiber instead of the wood. enjoy
[Galaxy S I9000 Themes and Apps] jondeman:
great share...thank you!!!
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] anubis1126:
hi for some reason i cannot copy mp3,s to my storage card does not matter what rom i have on any ideas please
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] rp-x1:
Where are you copying them from?

Is it just MP3s?

What error message do you get?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] watcher64:
Been an issue with activesync for a while, seems to have no rhyme or reason which MP3's or what machines it affects ...

The way around it is, connect your phone as a disk drive not via activesync and then copy away, it is faster that way too ....
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] anubis1126:
Thanks for the reply disc drive worked awsome
[HTC Aria Accessories] jznomoney:
Is there a way to mod the internal

Antennae to boost WiFi and/or gsm signal?
[HTC Aria Accessories] cegna09:
antenna design is a very specific thing. It's not a matter of just making it longer, or slapping on some extra wire to improve; the antenna needs to be a specific length for specific frequencies.

However, since the antenna (at least for GSM) is in the rear cover, i would think that third parties could make a replacement cover with a different antenna.
[Touch Pro2, Tilt 2 Themes and Apps] iridium21:
I don't know if you guys are aware, but HTC have today released an update that enhances SMS functionality.

This update is suitable for ROM versions less than or equal to 2.08.XXX.X.

You can get it from the HTC website or from here:

HTC TP2 SMS Update

Follow the instructions below to download and install the update on your device:

Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.

Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.

Download the Update file “RHO_S2_00896.exe” to your PC or NB.

Copy RHO_S2_00896.exe, to your device.

To install the Update, Follow the instruction below

1. Tap the RHO_S2_00896.exe which must be copied to your phone and follow the on-screen instructions to install it.
[Touch Pro2, Tilt 2 Themes and Apps] firefurby:
Could you link to the official posting please?
[Touch Pro2, Tilt 2 Themes and Apps] wesley762:
Can you post a link to HTC's site with this?
[Touch Pro2, Tilt 2 Themes and Apps] iridium21:
1st post edited :)
[Touch Pro2, Tilt 2 Themes and Apps] Aaron McCarthy:
is this the 'official' HTC messaging version 1.8 that was released/hacked a while back?
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Has anyone tried this yet?
[Touch Pro2, Tilt 2 Themes and Apps] Mr. Equalizer:
i´ve tried the update.

HTC Messaging is now really fast, but you always get a Message Sent notification and there is no option to disable this.
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Aww... not even with a registry tweak or anything?
[Touch Pro2, Tilt 2 Themes and Apps] SirMcFrosty:
try the attached file - in return please check for me the version of that new sms message client. thx
[Touch Pro2, Tilt 2 Themes and Apps] agrickard:
I cannot download from Europe 1 or 2 locales, but can from US, although when I tap on the .exe file once transferred to my device, nothing happens - anyone else experience similar?

In addition, where can I find out the version information of HTC messages so I can check my current one?
[Touch Pro2, Tilt 2 Themes and Apps] agrickard:
[EDIT] Double posting.

Stupid system... stupid poster...

[Mod - please remove or can we just have a "delete own posts" option?]
[Touch Pro2, Tilt 2 Themes and Apps] firefurby:
Experiencing the same error. Sometimes when I run it I get an error stating it's not a valid Win32 application.
[Touch Pro2, Tilt 2 Themes and Apps] AngelDeath:
HTC Messaging Client 1.5.2016.2424

I looked into this package, and seems this is newer then the HD2 3.04 rom, which that version was 1.5.2016.1228. I converted the exe to a cab.

Here is the EXT for Chefs.

I'll be trying this out and seeing if there is any improvements.

*Note this EXT does not include all the files needed, replace these files with existing EXT Package, or create a new EXT Package.
[Touch Pro2, Tilt 2 Themes and Apps] agrickard:
Its should be run from your phone and not your PC. But even so, nothing happens for me!:(
[Touch Pro2, Tilt 2 Themes and Apps] bartez:
Tried downloading it from the HTC site & the Megaupload mirror, but nothing happens when trying to install it on my phone. Could be because i'm using a newer rom? (26 june NRG rom)
[Touch Pro2, Tilt 2 Themes and Apps] forster:
I got this hotfix is not comapatible with your device..
[Touch Pro2, Tilt 2 Themes and Apps] TheSopranos16:
I get the same error. I tried running it on the stock Tilt 2 rom. Seems like the enhancement could apply to Tilt 2 rom as well, but HTC only shows this update on the Touch Pro 2 section of their site...
[Touch Pro2, Tilt 2 Themes and Apps] krwshl:
I also received the message "This hotfix is not comapatible with your device" I am using a Sprint TP2 with WM 6.5