yashsingh1/xdaforums huggingface dataset:
[Mogul, XV6800 General] jfclouti:
Ok I exagerated a bit in the title, but...

I bought this HTC 6800 Bell, from a nice guy, unlocked, upgraded, GPS activated, WM6.1. Bell entered my ESN in their system, gave me my MSL unlock code and when I dial ##(MSL)# and hit the talk button, the phone does not get into programming mode at all. I even tried a few HTC ##codes# and none of them succeed to get into programming mode.

Instead, the phone calls the ##code# and somehow gets redirected to a Bell Mobility recorded message telling me to call the activation hotline. Which I finally did. The person could not do anything, so he sent me to a Bell Mobility store, where another very skilled person was unable to do the programming.

What is supposed to happen when you enter your MSL unlock code? Anyone can help me?

I flashed successfuly a few DCD ROMS (3.3.4, 4.1.2), they all worked fine but I still can't activate the phone with my MSL :mad:

Thanks
[Mogul, XV6800 General] dfc849:
If you're using DCD's ROMs, make sure you have installed the Bell carrier cab from DCD.

http://dcd1182.n715dp.com/index.php?dir=carriers%2F&download=dcd+Bell+Carrier+20081031.cab

then try ##778# or ##778[dial]

after that it'll ask your for your MSL... should be just 000000
[Mogul, XV6800 General] jfclouti:
Thanks. That was the problem. The phone works well now. Thanks again.
[Upgrading, Modifying and Unlocking] mikewtw:
Any of you guys who find that the Toshiba G810 has battery life issues - just install two program - acbPowerMeter (to monitor power usage patterns) and S2U2 (V1.4 above). Set S2U2 settings to lock phone and power off within 5-10sec. Play around with it to find your optimum settings. After that your battery will last 2days even with bluetooth turned on and average usage

If you still have Power drain issues, disable Tasbar Smart Gesture under SPB Mobile Shell which comes with Toshiba G810 and try again.

I'm enjoying my Toshiba G810 now...and its better than the Iphone 3G in so many ways. The GPS rocks when I'm looking for directions via MapKing. And the 3MP camera takes pretty decent photos.

Enjoy!
[G1 Android Development] flamingblue8z:
Okay, the other night when the ADP 1.5 came out, I downloaded the bits from HTC's site, and followed the directions to the T, not realizing that i was going to lose my recovery partition with Nandroid in it. When I fastbooted my nandroid backup back onto the phone, the recovery partition never came back. How do I put that back on? I redownloaded it, put it on my SD card, and tried to go through the root directions again, but when i type cat recovery.img > /system/recovery.img" it comes back with an error about not enough space on the phone. Also typing "flash_image recovery recovery.img" is too fast for my taste. it's almost instantly back to the bash prompt, no delay like it did the first time i rooted my phone. So uhh, yeah, what do i do to get that back??? I didn't stay on the official ADP 1.5 because I forgot that I couldn't download my paid apps... I tried, wouldn't work, and I thought I had read a news article a while back that the Holiday update fixed that... but maybe I'm just going crazy or have been out of the loop too long (have a new iPod Touch and been playing with iPhone OS 3.0 beta on it, and WOW does that give Android a run for its money, but the 1.5 upgrade is definitely making Android all the more relevant)
[G1 Android Development] tubaking182:
when you first made a nandroid backup there were several files, recovery.img was one of them, or you could go get the recovery.img from when you rooted you phone. then just fastboot it to your phone and you will be all better
[G1 Android Development] flamingblue8z:
Yeahhh i did that... the original one i rooted with, i tried fastbooting that one onto the phone, 3 diff times now, doesn't work. And if i still had my nandroid backup i'd be golden.... (had deleted it).
[G1 Android Development] tubaking182:
did you try putting the recovery.img on your sdcard and flash_image recovery /sdcard/recovery.img like when you rooted the phone?
[G1 Android Development] flamingblue8z:
Yup. Used the Terminal program in JF 1.42 (which I've now noticed isn't the latest according to the JFUpdater???)... and i did su to get up to root, then mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system, cd sdcard, flash_image recovery recovery.img, and finally the cat. Ran through the same steps over and over, rebooted the phone over and over. NOTHING is working. And yes, the recovery.img is in the root of my SD card.
[G1 Android Development] korndub:
had the same problem..

boot to fastboot - fastboot erase recovery....OK

now put the recovery image on the sdcard and flash from shell...this shoudl fix it.
[G1 Android Development] flamingblue8z:
AH, thank you SOO much. I'll try it now. Gosh, what would happen if it wouldn't boot to the shell LOL then you're stuck fastbooting it. But thank you SOOO much!
[G1 Android Development] flamingblue8z:
Uhhhh, uh oh... something didn't work....... OH, THE JF RECOVERY ENVIRONMENT IS WHAT'S MISSING!!! AH HAH! How do we get the recovery.img out of the JF update?
[G1 Android Development] carlosjcar:
Here you go: http://rapidshare.com/files/227806623/recovery.img.html

this is the md MD5: B0290DB8D554E1378620023E0C5A93DB

hope that helps!:)
[G1 Android Development] koocat:
Hey I know I'm more of a leech than a seed but I want to start an open discussion / brainstorm about the limited bluetooth capabilities within Android. Specifically on the HTC Dream (G1).

I don't have a strong grasp on Linux but I've been playing with different flavors since i was 13 (11 years). I don't have the knowledge or the support to even attempt this.

HOWEVER I do have a job and I do have the money (donation) to support anyone with the ability and the time.

That being said I would like to talk to anybody who would be Seriously interested in developing additional profiles for the bluetooth stack.

Anyone who has wanted to FTP over bluetooth or for me send my phonebook to my Lexus GS350 I would appreciate donations towards a common goal.

The $ would go to the developer or team. Of course after that it would have to be open source and free to the community.

I have not created a paypal or account for pooling donations but whoever is seriously interested contact me. I've got $300 (donation) to get you started (motivated)

Au Revoir,

-Koocat
[G1 Android Development] koocat:
how do i make it bold lol
[G1 Android Development] jaaronmoody:
i'm all about development and hard work, but with the release of blutooth 3.0, wouldn't it be better just to save the $ and put it towards the next android device that is compatible with bt3.0( which utilizes wifi for bt transfer...not to mention the improved battery life). what are your thoughts?
[G1 Android Development] koocat:
its not about the money. I'm using dudes cupcake rom whatever latest rom .92 and as far as i know there is no way to send my phone book to my Lexus when it prompts me to create a phonebook and because of this I can't use voice dial and nazi lexus basicly won't allow you to input anything while the car is in motion. the specs released on 1.5 only included stereo bluetooth theres still no push allowed or PBA
[G1 Android Development] koocat:
would my car even work if bt is trans over wifi spectrum?
[G1 Android Development] jaaronmoody:
no, and sorry for the confusion. My point was that this android incarnation is lacking in bluetooth capabilities, and there has just been a new bluetooth technology released, not only having the wifi capability, but also all current profiles. I am sure that android will support this in the future with hardware in a new device, but for now, they are probably content with what they have, since it is an evolving technology.
[G1 Android Development] jordanjay29:
Umm, Bluetooth 3.0 standard was just released. We're not going to be seeing any Bluetooth 3.0 devices for another few years, one at the minimum. Not to mention that the OP's Lexus would still require a transfer via Bluetooth 2.0 technology.
[G1 Android Development] koocat:
I would be content if an open phone with an open platform supported bluetooth features I could actually use.

I manually added one contact into the lexus and manually set the voice rec. and then attempted to call using 'dial by name' and it will only work if the dream is unlocked and awake.

BT 3.0 will be great. but I'd have to get a new phone and depending on the backward capabilities a new car too.

but that brings the question "how long do i have to wait for bt 3.0"

"how long do i have to wait for cupcake"

I was hoping with 1.5 they would expand on the BT stack and they did but not for anything I can use. whats funny is 2 years ago when I had Verizon and a Voyager I thought I was cool to have stereo bluetooth headphones to rock out too. and they want to market stereo bt as being a great new feature but its not new
[G1 Android Development] jaaronmoody:
This is an appropriate place to post issues with supported bt profiles already supported, but there is no guarantee that it will be addressed. i'm not speaking for anybody here, but me... butif it were my build, i probably wouldn't modify it for one make of car. There are other vehicles where this is working...am i right? i think so.

so far i think only broadcom has achieved and are planning to produce the new standard, but how long will it be till we see it??? my guess is 6mo- 1yr. Yes, stereo bluetooth is not a new thing, but i'm sure you can grasp the technology curve. "they" are only gonna release what they have to, in the time that will make sense to them, not the consumers. This

is a business, and will be treated as such. For how many years have we been scratching at the heels of EVERY advancement, just to PURCHASE it as soon as it comes around. edit...but to go along with you i was looking forward to file transfer myself, and it didn't happen.
[G1 Android Development] alfmetal:
what can i do on my car to verify the bluetooth version installed?, or bluetooth capabilities if you know what i mean

its a mazda 3 2010 sport

Thank you.
[G1 Android Development] koocat:
Your exactly right and thats what makes Android such a beautiful thing. Because we are longer governed by whatever corporate timeline 'they' decide. the timeline is to maximize profit. cupcake is marketed as a feature update to show dedication to their product and to their customer base but its not a dedication because they were forced to evolve it to make it compatiable with additonal hardware and minimize the media attention towards custom devleopment and end user modification. Google doesnt want to piss off Apple or HTC or T-mobile or Vodaphone ect because thats business.

Google doesnt care if you transfer over bt they dont care if you mod your phone. but when Apple says no mulitouch and vodaphone says No Bluetooth profiles they don't have much of a choice if they want Android to succeed.

and Thats why they made it open.

same with rooting your phone google had to fix it beacuse if they make it look easy they run into problems. T-mob or voda don't want you to teather your phone and use it as a modem and root allows this. so you must disable and discourage root and tell people its a security risk.

fcuk T-mobile and their G1 bs marketing. My phone is a Dream.

---btw the new radio gives me 3G in my house now wootwoot so i can actually talk on the phone with t-mobiles shi*ty service--- I only left Verizon because phones suck Donkey...Anyways..

its not just one car. go http://en.wikipedia.org/wiki/Bluetooth to see all supported profiles

there are profiles that all cars support. most likely PBA "phone book access"

I know when the Prius 1st came out I was like 16 or 17 lol and none of VZW phones could send phone book data to the Prius only because VZW policy with phone makers demanded they crimple BT profiles even on smart phones. so you couldn't FTP a mp3 and set it as ur ringtone you had to buy the ringtone for 2.99 or what i did back them I used Bitpim but you get the idea.

-Koocat
[G1 Android Development] koocat:
I would google some keywords and try and find a user forum for Mazda cars.

I know theres clublexus.com where I have learned a lot about my car.

for some Lexus (i know for sure the GS and LS models) you turn the car on, then hold down the INFO button while turning the Lights from OFF to ON four times. and the car enters a Service Diagnostic mode and you can view different settings and run diagnostics, clear error codes and rescan. I know theres a spot to view the bluetooth version and software version. You can adjust the Mic volume, send and recieve volume and adjust voice quality.

You really don't need to adjust your car (thats not what this post is about).

Depending on your car you can get updates from the dealer and you can find software mods online for some cars.

example; lexus had a override in the system menu to allow user input while the car was in motion. IN 07' that option was removed on all models so for my 07 Lexus i found a post from someone that had taken the Nav disc for the same model in 06 and he modded and issued a ISO for users burn to get that override feature back.

-Koocat
[G1 Android Development] MarcusMaximus04@gmail.com:
Bah! @ Bluetooth 3.0. Totally overhyped standard. Could be completely done with adhoc wifi and would be easier and more than 2x as fast.
[G1 Android Development] Joushou:
MarcusMaximus04@gmail.com:

Yeah, it is... It's just a wifi coop mode, which requires both parties to have a wifi-radio free to use...

It's not really an optimization of bluetooth :/

Everyone else in here:

Well, i'm not sure you're gonna catch many devs in here :) (There doesn't seem to be any
[G1 Android Development] paesano:
Power management is much better in Bluetooth. Combining the two gives the best of both worlds. BT 3.0 will be able to connect, go into low power states and only turn on WiFi if a higher speed transfer is required.

BT 3.0 is more than just BT+WiFi anyway. The ability to have an Alternate Mac-Phy (AMP) like WiFi is one feature. There are other new features as well (like better quality of service). Also, an AMP could be a Ultra Wide Band (UWB) radio, with speeds much higher than WiFi with lower power consumption. The potential for 3.0 is really interesting.

But as others have stated in the thread, it will be a while before there are any implementations. We are just starting to see 2.1 devices in the market.

paesano
[G1 Android Development] crxtasi:
I know this is only my 2nd post, but I too am looking for better BT Stack. Dont get me wrong I love that I got back my stereo BT on my Pioneer Avic-D3 but unlike my Nokia N95 and my Tilt which lets me transfer my contacts to my Headunit.

Also another thing I miss is sending contact info from one phone to another!

Waiting for the time I can ditch my ipod and be apple-free LOL:p
[G1 Android Development] userfriendlyme:
I think a total update of the bluetooth would be cool. I think the 3.0 is a bit away but besides just a specific car profile i think it should be and all around compatible bluetooth. with all the devices and allow file transfer as well something that non g1 phones can already do. I think that alone will make it feel much better until until the newer technology is intergrated. That would probably lean me more to donating
[G1 Android Development] JackD3ath:
I have two old Motorola RAZR's and they transfer data over BT, it is really surprising that the Dream falls short in this area.
[G1 Android Development] Breach:
I just miss the very basic file transfer (obex) to move images, mp3, contacts, etc. from device to device. I know I can set up an ftp or webserver to allow phone to phone access, but quite frankly we shouldn't have to use a work around for such a standard phone option. ALso, I like to bluetooth pictures from my phone right to the Kodak picture printer in Walmart and other stores. There is no way to install an FTP server or client on that machine (without some hacking).

I would donate if we had some devs on here taking up the task.

Rick
[G1 Android Development] paesano:
Personally, I'm not surprised that the Dream falls short in Bluetooth support. My experience with Bluetooth in Linux has been very unsatisfying. I don't know if that stems from the Blue Z stack, or if no one cares enough to do things properly. The last couple of times I upgraded Ubuntu or Kubuntu, Bluetooth was totally broken, and I had to figure out my own workarounds to get some of the functionality I needed.

What I would currently like to see is DUN support, so that my Tom Tom can access the internet. Very few BT phones don't have DUN, especially on T-Mobile. Makes me wonder why T-Mobile wanted to get the Tethering apps out of the marketplace. You can tether with almost every Bluetooth phone they sell!

paesano
[G1 Android Development] Joushou:
Higher speeds are the main topic on bluetooth 3, and specially the use of the wi-fi radio. But using that eliminates the purpose of bluetooth (Very-low-power radio).

Also, theres not a chance in hell bluetooth is gonna bypass wifi. I've been at 30MB/s over wifi, do that with a low-power radio ;)

Anyway, the dream as bluetooth 2.1, and theres a long time till 3.0, so lets stop talking about it, ok? :)
[G1 Android Development] testing567:
If i had to guess, it's probably because their other phones don't have 3G and the G1 does. T-Mobile's 3G network is probably still young and fragile.
[G1 Android Development] crxtasi:
Plus 1 on this one too...
[G1 Android Development] paesano:
Yes, higher speeds are one of the main goals of Bluetooth 3.0. Its intent is not to supplant WiFi, however. It is strictly an ad-hoc cable replacement. With 3.0 you can take advantage of a higher speed radio to use the same services that previous BT radios used. So now, if you have a large file to send from one device to another, the two devices can negotiate to use 802.11 (not WiFi, technically) or some other radio to send the data.

So, you can connect with a low-power radio (BT), find services, negotiate bandwidth requirements, and bring up a faster connection if needed. The 802.11 radio (or other radio) is off except for the time that it is needed to send. This can actually save power over a BT transfer, because the transfer happens faster than it would over a Bluetooth radio.

In the future, faster radios may come into play. The WiMedia alliance just transfered control of its Ultra Wideband specs to the Bluetooth SIG. If UWB ever takes off, it will make current 802.11 radios look embarrassingly slow. Current implemenations run a 480 Mbps.

Anyway, this if all off topic, but as a developer of BT stacks for 10 years, I often feel the need to interject when these topics come up. BT 3.0 is unlikely to be used on the G1, though with BT controller firmware updates and the fact that it has Wifi, it it feasible.

A better implementation would have BT and 802.11 controllers on the same chip, sharing the same radio.

BTW, low power is always a goal for handheld devices. Judging by the poor battery life of the G1, I wish they had paid more attention to it. :-)

Sorry for the rambling...

paesano
[G1 Android Development] paesano:
Yeah, your probably right. I don't think about 3G much, however, because T-Mobile hasn't rolled it out in my area yet. :-(
[G1 Android Development] reuthermonkey:
Do you have 1.5?

http://source.android.com/projects/bluetooth-features

for Android 1.5:

What does your car use to transfer the phonebook? OBEX?
[G1 Android Development] Joushou:
I love pie

Yes, but it also uses the extra power of 2 radios, so it really depends on the secondary radio in use.

Oh, theoretically or practically?

I believe theres a 600Mbps implementation of one of the N drafts...

Both platforms are in active development, so Wi-Fi will probably get faster aswell :)

And also, i didn't mean "bluetooth will never be..." but "bluetooth isn't, and won't be within the next year or 2"

I also love to jump on this kind of topics when this sort of stuff pops up, but i don't think i can beat your 10 years of experience... it's 63% of my whole life :)

And i also thought BT3.0 had some hardware changes to accommodate the new features...

See, NOW we're talking :)

Yup... *Plugs his phone into his solar-backpack+joint-generators*

Heh, i suck at letting discussions go aswell :D (You noticed that, didn't you? ;) )
[G1 Android Development] paesano:
Yes, but if properly managed, when the second radio is powered, the BT radio will be in sniff/sniff-subrating mode (essentially off most of the time), consuming very little power. And the 802.11 radio will be on only long enough to transfer, then powered off. There have been some analysis of power usage per bit in a data transfer that turning on 802.11, transmitting, turning 802.11 off may consume less power than just transmitting over BT, because BT has to stay powered for a longer time to move the same amount data.

Wireless USB runs at 480 MBps. That is probably the throughput in the RF, so you do have to subtract any overhead (headers, retransmissions, etc). Actual data throughput is less I'm sure. However, I was at CES two years ago watching demos of UWB running at 2 Gbps. The were shooting for Wireless HDMI implementations.

What? I have socks older than you! :-)

Hey never let a good argument go to waste, I always say (well, maybe that's the first time I ever said that, but you get the idea).

The wise man breaks wind and is gone. - Jethro Tull (Now I am showing my age)
[G1 Android Development] koocat:
I'm about to go and test JF's 1.5 release. but in all honesty even if this does work by some grace of God, the point of this thread was to discuss the possibilities and limitations for developing additional BT capabilities (profiles).

instead lets talk about everything except the topic. you guys want to help and i appreciate it but fixing my problem doesnt help the community. Fixing the BT in the phone does.

ok i'm gonna go sit in my car and if this doesnt work i'm going to play Android Roulette.

-Koocat
[G1 Android Development] paesano:
Well, back on your subject. :-) I know a little bit about Car Kits, in general. There are 3 main ways that phonebook information is exchanged.

1) AT commands, which Androind 1.5 supports. I can verify that this is true from my own testing. FYI, this is not an official Bluetooth profile, but was commonly supported in GSM phones before Bluetooth even existed, so many (most) phones support it, as do most Car Kits.

2) Object Push, which usually requires you to manually push your phonebook to the Bluetooth Car Kit. Obviously, Android does not support that yet, but this is a good area for some developer to work on.

3) Phonebook Access Profile (PBAP). Android doesn't support it, and I don't know if BueZ even supports it. It also is based on OBEX, but is a bit more involved to develop. If BlueZ has an implemenation already, that code could be used, otherwise you got a bit of coding to do.

Sorry for that off-topic discussions. My wife always accuses me of changing the subject also. :-)

paesano
[G1 Android Development] Joushou:
koocat:

Sorry for that before, couldn't help it :(

From what i know, bluetooth support isn't one of the main priorities, and as you might have noticed, it isn't part of cupcake.

If we're lucky, it will be in donut... (Who made up the naming-conventions for android? It's making me hungry!)

paesano:

I don't think i want to get anywhere near your socks if they're older than me, without a separate oxygen-supply ;)

And changing subject is good for adding some variety!.. Now, for the top 10 of toothbrushes...
[G1 Android Development] prscott1:
Hey koocat - you aren't alone on this issue. It is really my only gripe with the G1 Android. I am running ADP1.5 and still can't get my phonebook to upload to my BMW carkit. It pairs, connects, but once the phonebook tries to load, it immediately disconnects and then continually loops through connect, disconnect, etc. until I turn off BT. Let me know if you had success with your carkit. I've played with the audio.conf and hcid.conf files to see if they need tweaking - you may look at those too.

/etc/bluez