yashsingh1/xdaforums huggingface dataset:
[Hero CDMA General] mrinehart93:
Ok, I have good news, and bad news. We'll start with the good :)

So if you want to try and replicate what I did to get force roaming, here's what you do (atleast what I did).

Be running Fresh ROM 1.1. Without wiping data, flash to MoDaCo 2.0. Now, if you look in the About Phone menu, it will say Needs Reboot. Reboot the phone. Now, remove "Dropbear". The phone will reboot again. At this point, I installed WaveSecure by using the .zip MoDaCo posted. A few minutes later, I decided I didn't like the MoDaCo ROM, so I did a nandroid restore back to RIGHT BEFORE I flashed to MoDaCo. After the restore was complete, I was back in Recovery Mode. I pressed Reboot System Now, and then once the phone booted, it was in forced roaming. Sadly, I only had 1xEV :( But hey, atleast it force roamed :)

Bad news: I rebooted my phone again (because I actually needed to use it), and it was once again using Sprint.

Maybe some dev can look into file changes between Fresh->Modaco-nandroid restore->Fresh? I'm not experienced enough with Android hacking to know how to mess with this stuff :(
[Hero CDMA General] david_ag:
LOL nice explanation :D. Yeah, while you are roaming, you are limited to 1X, no EVDO. But it's a great start and thanks for sharing! Whomever is knowledgeable please try working on this. I sadly have no clue :(.
[Hero CDMA General] WhiteWidows:
Has anyone been able to replicate this?
[Hero CDMA General] flexgrip:
I don't get a good sprint signal in my house and sometimes, in the right situation, it will switch to roaming. It then takes a few minutes to get off of the roaming tower and get back on sprint.

I am not saying you didn't force it to roam and don't take any offense, but it sounds like to me you booted your phone and it glitched or something caused it to not pickup the sprint tower (maybe there was a problem with the tower). Once you rebooted it tried again and was able to grab the sprint tower.

I don't see how flashing a rom would force it to roam. That just doesn't seem very likely. Considering a quick grep only brings up a few options for enabling and disabling the ability to roam, I doubt it was a problem with the flashing.

Hopefully, someone figures out how to force roaming soon. And I really hope I am wrong and this leads to a solution.
[Hero CDMA General] mrinehart93:
Nah, it's ok. No offense taken :) Yeah, it's likely that it was just a glitch... I only posted what I did before the glitch happened, in the case that someone may be able to find it useful (mix match of files from ROM's or whatever).
[Touch 3G ROM Development] fedrat:
As Promised:

1) Download the latest Hard-SPL package (currently v5.20) from here and extract to an empty folder.

2) You must have your phone synced with your PC.

XP users need Activesync from here: here

Vista/Windows 7 users need Windows Mobile Device Centre from here: here

3) NEW: internet access is required as the program checks online for updates and license.

4) Run Jade-Hard-SPL.EXE on your PC. Make sure it's launched from a local drive, not a network drive.

If you using Vista/Windows 7, launching as Administrator is strongly recommended, on XP administrator login is required.

Important: if your AV (norton/symantec mainly) warns about a virus, ignore it, it just doesn't like the packer I used to pack the program. Disabling your AV is strongly recommended.

5) If possible, always use Automatic flash mode (for instructions on how to use the Manual mode, see troubleshooting advice here). You may get a message stating this is not for your device, click yes and allow the screen to go blank.

6) It will ask you to wait while it prepares for the flashing, press OK. Follow the steps in the program and then in the RUU.

8) Device should go to a tricolour screen now that says 1.40.1000 (not .0000!!!), this is the SSPL version, which is temporary. When your phone goes to the bootloader screen for the first time, quickly unplug the USB cable, then reconnect it. Wait around 30 seconds and click Next on your PC.

9) SPLwill now flash, device automatically reboots, job done.

10)Tto confirm you got it installed, go into bootloader mode (tricolour screen!) and the screen will show 2.32.OliNex, which is the Hard-SPL version. If it is 1.64.xxx instead, then please make sure you actually download last version (v5.20) and flash using that. 2.32.OliNex is the correct Hard-SPL version.

These instructions SHOULD work first time every time.

Instructions copied from OliNex, tidied up by me. USB disconnect/reconnect trick discovered by zannyuk and found here.

I recommend lsc's WM6.5 ROM (here) for WM 6.5 only and Ironeagle's Jade Overloaded (here) for all the trimmings.

PM me with any errors or corrections. And feel free to comment
[Touch 3G ROM Development] fedrat:
Has anyone used this yet? Can you let me know?
[Touch 3G ROM Development] mikecoffee:
i've used it and it works pefectly no more rubbish orange roms.
[Touch 3G ROM Development] ch4ni:
Jade Flashing Guide

Hi,

When trying to following these instructions, I cannot get past instr 6) as at that point I get the error:

"hard- spl is for non-commercial purpose only,we have detected that you appear to alreadyhvae unlocked a device, if you wish to unlock commercially"

The phone does not go into the bootloader mode (tricolor screen), the program terminates at this point, please advise how to overcome this and successfully apply the Hard SPL v5.2

Thanks
[Touch 3G ROM Development] fedrat:
Look under the Hard SPL stickie to resolve this one.
[Touch 3G ROM Development] ch4ni:
Please can you point HSPL Stickie as I tried to find this information and was unable to. Your help is greatly appreicated.
[Touch 3G ROM Development] fedrat:
go here: http://xdaforums.com/showthread.php?t=483465.

You should be able to find the answer.
[Touch 3G ROM Development] maxrfon:
Does anyone have original Orange UK 1.40 ROM? Need to recover the device Urgent ((
[Nexus One General] svntsvn:
Would it be hard to program the trackball to wake to the lock screen rather than having to hit the top button. I find it very annoying and it would be so much better for one handed use.

(this thing is slippery!)
[Nexus One General] iVisionX01:
It bugs me a bit too. When I had an iPhone I almost always use the home button to bring the unlock screen up. Also my nexus one is a bit slippery too I want a case.
[Nexus One General] kolyan:
I would be more interested in using volume keys to play/pause/forward/rewind the music payer without waking up the phone. This was one of the applications in iPhone.
[Nexus One General] Over Achiever:
If you're playing music, the volume keys are still able to adjust the media volume while music is playing and the phone is locked (and the screen doesn't turn on while doing it either). I prefer that behavior actually.
[Nexus One General] uansari1:
That's the one thing that always bugged me about the Droid, and what do you know... the N1 has the same problem, lol. Anyway, there has been a lot of discussion about this (including here: http://xdaforums.com/showthread.php?t=613678&highlight=trackball). There's a thread in development as well about maybe mapping that function to the trackball... who knows.
[Nexus One General] PISSANDVINEGAR:
Lots of great thoughts here. Bump.
[Nexus One General] noodles12:
I hated this as well!

I found a solution! (sort of).

"Lock bot Free" from the android market is what i use now.

It enables you to pick differnt lock screens ( i like the hero one since u just scroll downwards to unlock) and it allows for u to press the trackball to wake up.

I have found that it is kind of buggy still. If i reboot the phone, I end up with two lockscreens. The regular nexus 1 one and then my hero one. So i had to reinstall it for it to work properly.

Disclaimer: I am not affiliated with that app. I just found it on my search to make my N1 less annoying.
[Nexus One General] seanhassars:
I was about to come post this same thing, although I'm experiencing a weird glitch too, but I actually like it. For some reason I don't get a lock screen at all after my phone locks. I hit the trackball/volume keys/power button and it just goes straight to whatever screen I was at when it locked. Pretty sweet actually.
[Nexus One General] pesho00:
This is Very good, if it was working:(

it randomly locks or not the screen which is Unaxeptable in my pocket:(
[Nexus One General] grainysand:
I tried the alpha3 of myLock. It... sort of worked, except that every time I unlocked/woke the screen, the app itself would toggle itself off. No idea why; it's not like I even have a task killer anymore.
[Nexus One General] jp_macaroni:
Lock 2.0 from the market works well.
[Nexus One General] noodles12:
does that allow you to have a regular or hero lockscreen?

ALl i saw on the screenshots were Iphone lockscreen ripoffs.

And if i wanted an iphone i would've gotten one. Why you'd want to make your N1 look like an iphone I can never figure out.
[Nexus One General] zole2112:
Trying Lock 2.0 free, so far it works pretty good. I can't change my lockscreen pic and I don't like how it goes to the lockscreen when touch home...
[Nexus One General] scrappyabs2:
What I don't like about Lock 2.0:

1) If you wake up your phone by accident (and don't unlock the phone) it doesn't go back to sleep after a few seconds of inactivity,

2) it doesn't show your notification bar so you don't know whether you got a new email or text message or other notification.
[Nexus One General] Eclair~:
Have you even looked in the settings? Please examine the app more closely.
[Nexus One General] grainysand:
Using Lockbot free now. Does what I wanted perfectly (press any hard button to wake up), plus lets me use the Eclair lockscreen which I've always found more aesthetically pleasing.
[Nexus One General] kevwright:
Installed Lockbot Free, and it does exactly what I want with the trackball, but I can not work out why sometimes it gives me the Eclair screen which I like, and sometimes it chooses a different screen?

Kev
[Nexus One General] Eclair~:
You have to uncheck the stars (I can't remember specifically) next to the unlock screens you do not want to show up. I never liked LockBot, it isn't a precise copy of the real lock screen(s), if I'm going to use a imitation I rather it look complete..
[Nexus One General] grainysand:
Open up the app, press "My theme." It'll give you a "playlist" of different lock screens. I simply un-star all the ones I don't want and stick with Eclair after changing the background. The clock's font is a bit off, but I will cope.
[Nexus One General] kevwright:
Thanks Eclair and Grainysand, just the job. One more thing off the list!

Kev
[Nexus One General] KrazyBlonde:
im getting the pro one, I dont like that I cant use the nexus unlock screen with the free one, the pro has a shake to wake feature too *cool*
[Nexus One General] nickustinov:
everything i would need is actuallty a mapping of power button to trackball :)))

no fancy iphone lockscreens for sure :)))
[Nexus One General] kevwright:
I actually prefer the Eclair "dial" one, but until I decide if I can make the N1 my daily driver, I am not gonna pay for any apps unless I really have to.

Kev
[Nexus One General] grainysand:
nickustinov: Lockbot, free or pro, lets you press any hardware button to wake up the screen. Volume rocker, trackball, power button.

It doesn't force you to use the iPhone lock screen either, thankfully. You can choose from iPhone, Hero, or Eclair (the N1's lock screen is only available if you pay for pro), or have it cycle through all three. So yeah, it'll do what you're looking for.
[Nexus One General] scrappyabs2:
After I installed Lockbot free my phone no longer asks for my SIM CODE when I reboot. It just boots me straight into my home screen, but doesn't activate the cellular signal, so my phone is basically useless.

Anyone know how to remedy this problem?
[Nexus One General] ztm.000:
So get this..

When I sleep I don't lock the phone I just put the clock app on and then lock the phone. Someone posted earlier that the phone doesn't really go onto sleep mode when the clock I'm enabled. Is this true?
[Nexus One General] wolfman87:
Doesn't using a program almost defeat the whole purpose? I mean this is something that should be natively supported from the OS. Personally, I think that using the memory and space to install a third party app (and jump through two unlock screens) to do something this fundamentally simple is ridiculous.
[Nexus One General] civicvx94:
Agreed.Ive always hated using third party lock screen apps..I dont understand why its so difficult..something like this would be a simple directory edit with WinMo..
[Nexus One General] jerrycycle:
MENU SETTINGS, these issues can be set to your liking
[Nexus One General] djmcnz:
Flyscreen is a free app in the market that does what you want (and a little more). Any hardware button to bring up the swipe screen.

I get very few, if any accidental "unlocks".

I found LockBot a little slow to respond, it does more than I need and last time I looked the Nexus "Flan" unlock screen wasn't available in the free version.
[Touch Pro2, Tilt 2 Windows Mobile General] dahauss:
I found some registry changes to resolve a lot of the bluetooth issues as far as the connection disconnecting after 1 ring, the hangup issue, etc.. HOWEVER.. now I have an issue with LAG where when connected to bluetooth, after a while the phone will lag and you can see everything moving in slow motion.. if I disconnect the bluetooth then the phone speeds back up.. ANY IDEAS? the only device I see this NOT happening with is my STEREO BLUETOOTH HEADPHONES MOTOROLA S9... Here is what I changed:

1. Modify the HandsFree plug-in:

HKLM\Software\WIDCOMM\Plugin\HandsFree

i. Change SupportedFeatures to 45 (default is 1135)

ii. Add value HFBDA binary, set to same value as LastConnectedBda

iii. Add value HFDeviceType decimal 2

2. Modify the WIDCOMM bluetooth general settings:

HKLM\Software\WIDCOMM\BtConfig\General

i. Change bdaddr to (no value)

ii. Change DisableReopenAudio to 0 (default is 1)

If anyone can figure out how to resolve the bluetooth LAG I would appreciate it....
[Touch Pro2, Tilt 2 Windows Mobile General] dahauss:
anyone have a fix? also now the last received, last called and missed do not grab info from the phone.. it only shows the calls I have made using the bluetooth device...
[Touch Pro2, Tilt 2 Windows Mobile General] p51d007:
I have noticed a similar lag, and, on my end it's not so much after a phone call, but after anything associated with BT (I use a Moto HX-1).

Does not do it all the time....If I am in the middle of doing something with the phone, and I get a notification through the ear piece (voice command), everything starts to stutter. Side note, at times, the silly phone heats up, and battery starts to drop.

I reran an OLDER rom for a couple days, and didn't have ONE issue.

Sounds like something in the later rom builds has changed something in the BT?
[Touch Pro2, Tilt 2 Windows Mobile General] rob_p:
I've also noticed this recently. Whenever the phone is hooked up to my in-car bluetooth (Audi), it runs like an absolute dog. As soon as it disconnects, it runs fine again. This is most frustrating as it can make the phone unusable when connected to the car kit.

Anyone gotten to the bottom of this yet - is it an issue with a newer bluetooth stack or something?
[General Topics] orb3000:
With the posibility on the air of opening XDA for non HTC devices, what is your opinion?

Should this go ahead?

Or should we stay only with HTC?

This poll will help Admin & Owners to see what is members opinions, which are very important!

So please vote:)

See what´s happening here:

http://xdaforums.com/showthread.php?p=5335158

http://xdaforums.com/showthread.php?t=616206
[General Topics] dcarr622:
I'm quite interested about this (of course there aren't too many votes yet, but we'll see)...what do people have against non-XDA phones? If we can maintain the same set of quality ROMs and information, what's the objective?

The XDA admins are beginning to experiment with some non-XDA sections (of course sticking with WinMo and Android), so I hope everything continues to move in that direction.
[General Topics] cmstackar:
We should stay HTC. There are a ton of users as it is, and while more would be great, xda is slow now, think of it later. I would love to have other manufacturers, but it works about the same if they are all grouped into the general forum. Or everyone could just have HTC manufacture their device and be done with it.
[General Topics] Master_H:
I would like XDA-Devs to open to also non-HTC-devices. There are several non HTC-devices that are also very interesting, like for instance Xperia X2, Samsung, Toshiba, etc..
[General Topics] irkan:
Why not? .. unless the traffic could be compromised, otherwise i dont see why not having other WinMo devices sections, like Samsung , Toshiba, and Other windows mobile devices
[General Topics] caraboy:
Besides my HTC phone, I also have a WM Samsung device, and it`s great I can find good info for it here too. So if you can handle the extra users, why not? There are many great smartphone devices from other manufacturers, let`s give them a chance. :D Competition makes the world evolve.
[General Topics] rishi2504:
Of course , yes. I don't have anything against HTC, as 5 of my six WM phones have been HTC but I feel we are more a user community which does not need to be distinguished and divided based on manufacturers.

Also, I feel it will lead to better phones from HTC. Reason, simple - if other brands are allowed here, more people will buy those brands owing to better support leading to increased competition for HTC. Eventually, as users we will get more technology for less :)
[General Topics] Tabbe:
no point of having this post or poll as xda is already a open forum for windows mobile all the while

the name 'xda' came from O2 Xda product line on touchscreen & powered by windows.

when xda atom came along from O2 asia, its already known that its not a htc product but its still listed here.
[General Topics] orb3000:
Not yet...

Not yet. To this date we are still an HTC devices forum, the discussion is open for including non HTC devices and this poll was created to help Owners and Admin to feel the pulse of the members, so it´s important to know what is members opinion:cool:
[General Topics] Tabbe:
its is only u who always bring this up
[General Topics] orb3000:
Somebody has to do it:D

If I´m doing something wrong take for sure Mods will let me know:)
[General Topics] galaxys:
Keep it to WM & Android. Maybe try one other than HTC device forum first before adding others. Then phase them in slowly. To make sure it doesn't get over crowded or unproductive!
[General Topics] DaveTheTytnIIGuy:
That was actually a mistake made by the admins, and they deemed it unfair to remove the forum after they realized their error. If you notice, other O2 XDA models not made by HTC don't have forums here.
[General Topics] FloatingFatMan:
I hope they do decide to go for it. Sure, there are other forums for other manufacturers devices, but NONE of them are even remotely as good as this one.

Take the Acer M900 device as an example. On the ETEN users forum, some ROMS came out for that device, one of which had been built blind, but the chef didn't tell anyone that little tidbit. Now, anyone that burned that ROM is hosed with burning official ROMS as you just get a "ROM Incompatible" error. The only way now is to edit the "magic byte" to burn a ROM, any ROM. Still no fix for it.

If that had happened here, a fix would have been around by now...
[General Topics] BrooklynAvi:
It shouldn't even be a question. Who cares which company made the device? If people need help and this forum can do that, then I fail to see why it shouldn't. While I personally prefer HTC devices, I'm open to other being helped in any way possible.

In my opinion, XDA's first non-HTC device should be the Droid.
[General Topics] Tabbe:
and thats my point, why restrict since by using "xda" and not 'htc'
[General Topics] Dust2Dust:
I hope so

Cuz I am in the mood for a samsung B7620. Not because it is so beautiful, it is completely ugly and I hate Armani, but I realy like the specs on that device. The biggest problem however is the lak of a community like XDA. As HTC is not bringing out any high end devices with qwerty and winmo, TP2 was just a makeover, I feel forced into other directions.
[General Topics] poetryrocksalot:
I say stick with HTC. Because once this forum becomes something like Howard Forums, I'm going to leave it forever.

I believe now that forums should be specific to manufacturer, or else chaos and confusion will ensue.
[General Topics] Tabbe:
by adding sub forum, what confusion & chaos will it cause to you to leave this forum?

anyway the poll result has the answer
[General Topics] charge1313:
I agree that this forum should include sections for non-HTC WM (and maybe android) devices.

I currently own a samsung jack and it, along with its predecessors - the blackjacks, are probably the most popular non-touchscreen WM phones. Yet they have no dedicated section.

Sever less popular phones on the other hand do have their own sections.

I see very little distinction between any WM phone manufacturers - the software is mostly what matters right?

And I would love it if my Jack had the kind of support my old Gene had around here.
[General Topics] bydanit:
Yes. Because...

I think XDA coul benefit with non HTC device threads. (Remember the core player wich was ported from tg01 to HTC H2). Just one example.:rolleyes:
[General Topics] poetryrocksalot:
Because I get overwhelmed by the enormousness, and I get disconnected from the forum. Also have you been to howard-forums?
[General Topics] Tabbe:
well it seems like you will be disconnected soon from xda forum too as something new coming soon.
[General Topics] Varking:
Yes, they should. I have been looking for a Motorola Droid section and finally decided to sign up just to say this.
[General Topics] Philux:
My ¢2

There are already lot of non HTC Devices on this forum already. However there is not as much on them as most of our developers and cookers are die hard HTC fans. I am open to whatever, however I think it would be better to have these Non HTC Devices grouped together in there own categories in a link of the main page for NON-HTC Devices. Then the NON Devices break down like the rest of the HTC Devices Main Page. I know this will be a ton of work, but whoever wanted to be an admin for the NON-HTC Devices can stay a very very busy person.
[General Topics] dik23:
I agree, that Droid is very good. No reason not to have a non HTC devices, seems silly to limit the reach of this forum
[General Topics] Bulldog:
This site has started and has been called XDA-developers because device "O2 XDA (Wallaby)" that were build by HTC was the first device that has combine PDA and Phone functionality on windows platform.

People come here to talk and exchange information and Developed tools and software for Windows phone. Most issues that we exchange here are based on Software rather than hardware.

HTC has not given us any free lunch. Therefore why should we promote and provide a large platform for their market share by limiting this forum only for HTC devices. Many of us unsatisfied with HTC’s devices but mostly we are limited to HTC because we think they are the best amount worse. How many times we have decided to HTC devices between others because even though we know HTC give us ****e we still have XDA-Developers to get support.

Most of us may not aware what kind influence already XDA developers has to buying a device. With continuing such way we are drying out other Device manufacturer and we our self limiting our own choices.

Therefore I really see it as only valuable to extent the forum for other devices
[General Topics] wywywywy:
So when are we going to see a decision?
[General Topics] freakzone:
Why should we have a droid forum and not have N97 one or iStick one?

I don't like htc, however I haven't came across anything better.

I don't like windows, linux and macos for that matter, be it mobile or desktop. However I'm stuck with using at least one of them