yashsingh1/xdaforums huggingface dataset:
[Thunderbolt General] Bxsteez:
This is what I don't understand about HTC. Its like look you know how to make a spectacular keyboard so keep the keyboard the same and change the rest of the design. Beef up the internals and modernize the design. But NOOOOOOOOO...
[Thunderbolt General] gemro311:
Local Verizon store in (Raleigh, NC) said TB will be released on 2/24.
[Thunderbolt General] myv6mustang:
Hey how'd that purchase go?
[Thunderbolt General] ska.t73:
Epic!!! LOL!!

The OP had a post deleted a couple days ago that claimed he had his TB in hand and would post a video...
[Thunderbolt General] Gadget Man 007:
In the OP's defense, when I preordered last week, the fools at Best Buy scheduled me to pick it up today (17th). Of course, knowing it wouldn't be there I called them to "confirm." They said "Oh yeah, late last night Verizon delayed it till the first week of March... sorry about that." Read: "we don't know anything"

Anyway, I'm ready to cancel my preorder. As the final specs are leaking out, there's less and less incentive to break contract on my Evo just to buy an over priced phone. Will probably wait for something better down the line.
[Thunderbolt General] Androidfreakz:
Funny thing is Duel core are coming by summer and Nvidia say they should have quad cores in phones at the end of the year lol. If using wait to buy a dual core ur already being out dated by years end. I'm patient, I really like the evo when I was at sprint, the TB is going to be awsome.
[XPERIA X10 General] as1mz:
Hello all,

I've been having this weird problem where even after sending a message it automatically saves as a draft because it just doesn't disappear from the box. Have tried searching this forum here but it didn't yield any results.. Did anyone look into it? Any help at all appreciated.

Thanks.

EDIT: Oh and I'm running 2.1 build .435
[XPERIA X10 General] as1mz:
Doesn't matter now since I'm on Wolfbreaks ROM..... :D
[Desire Q&A, Help & Troubleshooting] KevAmiga:
Hi guys.

I have flashed numerous ROM's onto my desire, but never a radio.

Im not sure what I need, and what the risks are. All i hear is that its possible to brick flashing Radio's and a bricked desire is something I cannot afford to replace.

My desire, is running DeFroSt 6.0j.

Everything is running OK at the moment, but if I can improve, then I will :)

My desire Spec :

BRAVO PVT3 SHIP S-ON

HBOOT-0.93.0001

MICROP-051D

TOUCH PANEL-SYNT0101

RADIO-5.11.05.27

AUG 10 2010, 17:52:18

Cheers guys :)

Kev
[Desire Q&A, Help & Troubleshooting] davebugyi:
Just flash it like a ROM from CWM/AmonRA. I can assure you, if you download radios from here (with md5 checksums to verify them), nothing can go wrong.
[Desire Q&A, Help & Troubleshooting] KevAmiga:
Thanks for the reply. So the problem isnt the flashing of the radio, its a corrupt or infected radio file?
[Desire Q&A, Help & Troubleshooting] davebugyi:
Yes, but as I said, if you get it from here, it will work.
[Desire Q&A, Help & Troubleshooting] KevAmiga:
Brill, thanks for the advice :)

Any idea what radio to use? Is there a way to pair a radio with a Rom?
[Desire Q&A, Help & Troubleshooting] davebugyi:
Latest is OK, you can use it with any ROM.
[Desire Q&A, Help & Troubleshooting] KevAmiga:
Great. And finally.. what is the latest (is there a "latest radio" thread), does it work with all desire's and how do i check the MD5? (i understand what a checksum is, but have never worked with them before).
[Desire Q&A, Help & Troubleshooting] davebugyi:
Posted the thread in my previous post (post #4). Latest radio is shown on top.

No MD5 in that thread, but I can guarantee that the latest will work (installed the same from there).
[Desire Q&A, Help & Troubleshooting] KevAmiga:
Thanks again! :)
[Desire Q&A, Help & Troubleshooting] EddyOS:
The radio you're on is actually just as good as the latest one so you've no real need to change
[Click Accessories] djemm1996:
Hello,

Is real to buy htc tattoo new buttons? My buttons are scratched.

And if that real to replace buttons?

Thanks for help.

Edmunds.
[Click Accessories] Hirakim:
If you need Tattoo buttons why not buy a broken HTC Tattoo on ebay?

I doubt you can exchange the Hard-Buttons on your device :(
[Click Accessories] alcatel444:
You can Buy New Buttons from HTC

Hi i called HTC and asked them about this and they told me that they can replace it for me for 150 Egyptian pounds = $25
[Click Accessories] Hirakim:
25$ is not that expensive. Thanks for the info.
[Click Accessories] yankhor:
my 'call' button is bad too.

thanks for this info.

do you know if they send all the buttons for $25? or just one?

the main button is a lil scratched, but its still fine.
[Click Accessories] alcatel444:
I think all the set of buttons and maybe other attached stuff
[Click Accessories] yankhor:
hmmm that's pretty nice.
[Click Accessories] csz9981:
i dont think you shouod exchange the hard-button

and you could have a try these 2 soft button :
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well you really need to break it down better.

What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?

I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Okay, firstly my startup.txt

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot

Full Packages I have tried:

FROYO X RED 2011.02.06

ProjectAndroid2.2Froyo.012311

RhodiumXDAndroid23.01.10

XDAndroid2.2Froyo.012211

SENSE x 2011.02.10

Along with these Modules:

htc-msm-linux-20101204_010857-package

htc-msm-linux-20110210_213850-package

modules-2.6.27.46-01253-gd53ddf6-dirty

initrd:

initrd-20100813-b11116a

Rootfs:

rootfs-20110210-2cb7ec0

(and many others i have just deleted)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.

Have you tried with FRX04?

Have you tried with a "regular" rootfs from the autobuild service?

You also have deprecated commands in your startup.txt, I highlighted them in red.

I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...

I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.

If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)

where could I grab logs from?

Tried FRX04 too.

Just making sure im doing it right

Dowloaded	RAR - Android v2.2.1 Froyo: Reference

unrar to 'andboot' on sd card.

edit startup.txt

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 rel_path=andboot"
boot

Downloaded and put modules-2.6.27.46-01212-ge59fdaf.tar and its zImage in andboot

(deleted old ones first)

replaced rootfs with rootfs-20110210-2cb7ec0 (renamed of couse to rootfs.img)

.....

run haret.exe

past all the booting

past the xdandroid logo loop

screen is horizontal

slow and laggy android

screen flips to verticle

seems to be more stable

set up my wifi, connected.

so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.

what do you need now? Am I forever stuck with this old module?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.

Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull

adb pull /data/system/dropbox/ /path/to/folder/on/your/pc

It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.

Hell, attach a few of them.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Just to clear it up, logs from module that dont boot or the one that does?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The dropbox will have logs from failed boots hopefully.

If you can get a log when it's failing to boot, that would be ideal. Might want to rename your data.img, grab the newest 1253 kernel from GIT and boot. See if you can grab a dmesg from adb,

adb shell dmesg > dmesg.txt

Will dump the dmesg.txt file to where ever you're running that command from. You can change the path on the right side of that command if you want to direct the output to a different folder.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
i cant get droid explorer to find me device =/

scratch that, it picked up a "00000" that seems to be it.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
new data.img, kernel and module from 1253. loads home screen with the google search bar and the android and it just froze up, performing soft reset, putting on the working modules and retrieving the logs for you.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
done! :D

see attachment
[Touch Pro2, Tilt 2 Android Development] ryannathans:
is that all you need?

What should I do next?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
any kernel after november 2010 just freezes after booting (something to do with the panel?)

Trying a different 'package' and hopefully I can get the logs.

this time im using: http://xdaforums.com/showthread.php?t=933177

okay is seems to be working -.- its modules-2.6.27.46-01232-gb7033df

ill try and load 1253
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices ;).
[Touch Pro2, Tilt 2 Android Development] ryannathans:
can you point me to where I can download 1232 - 1253? :) appreciate the help so far

EDIT: I think i found them.

Trying now.

EDIT:

01245 - PASS

01246 - PASS

01250 - PASS
[Touch Pro2, Tilt 2 Android Development] ryannathans:
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version

using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.

keyboard layout in startup.txt is set to rhod110
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, it happens.

Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
[Touch Pro2, Tilt 2 Android Development] ryannathans:
ahh noo. still same problem with it :(

thanks anyway :)

EDIT: everything's working sweet now that I had a chat with F22 and we got rhod110 support now :)
[Touch Pro2, Tilt 2 Android Development] praveen_y76:
I faced same issue, it froze while installing, or so it seems. then one fine day, i accidently clicked on screen for 2-3 secs with stylus and then ... the screen moved one line up showing some message related to 'point 2' or in other words caliberation. My guess was it was waiting for caliberation and i thought it froze. Not sure of this is the same case with yours, but you can try it once. I clicked for 2-3 seconds on top-left corner first, then top-right, bottom-left, bottom-right, and lastly center of screen. After that everything worked properly.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
...Is it actually calibrated correctly? If you couldn't see the boxes I don't see how it could be calibrated correctly.
[Touch Pro2, Tilt 2 Android Development] F22:
That sounds like the touch screen calibration bug that was fixed for rhodium in kernel 1258.
[Touch Pro2, Tilt 2 Android Development] praveen_y76:
oh yes, sorry i forgot to tell you that.. i also didnot see the boxes, you can say it was my wildest guess that it turned out to be for calibration. Also the sequence of clicking the imaginary boxes may differ. For me it took me multiple tries before I got correct sequence for calibration. I had to delete ts-calibration.txt after every wrong setting and then re-run haret.exe
[Touch Pro2, Tilt 2 Android Development] shacknasty:
Hi All,

I also have a similar issue with RHOD110 using FRX05. All goes well up to the XDAndroid splash, which just sits there for about 5 minutes going over and over.

If I leave it for 10 minutes it eventually gets to a desktop but keeps coming up with "The application Google services Framework(process com.google.process.gapps) has stopped unexpectedly".

Then the screen goes off, orange light stays on but no way to get the screen back on.

I am using the RHOD100 startup.txt, and extracted http://files.xdandroid.com/FRX05_Full_Bundle_3.3.2011.zip to the root of my sd.

Any help would be appreciated, I just lost my WP7 phone and cant handle 6.5 anymore! Possibly a week or more till I can replace the Trophy.

J
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So the pm.sleep_mode=1? That should work fine, although on first boot it does take a while to start - even after the 'desktop' appears, there's a lot going on in the background - especially on first boot.

I've also heard some people have issues with the default APN - if you can get the phone into Airplane Mode ASAP and then set the APN manually, should fix it.
[Touch Pro2, Tilt 2 Android Development] wilkok:
Airplane mode fixed the freezing issue for me. Does anyone know if there is a way to modify the APN settings in Airplane mode?
[Touch Pro2, Tilt 2 Android Development] TechGuy77:
I believe the only thing you can do is get the APN Backup and Restore from the market using Wi-Fi. Do a little googling to find APN settings for your carrier and create/download the APN files. Then use APN Backup and Restore to restore the file. Finally get out of Airplane mode and test. I am still working on getting one working for Alltel, mine just keeps freezing...grrrr!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps pull it out of airplane mode and try to get the APN stuffs in there? I think you should be able to if you are quick :p.

Sorry, my phone doesn't exhibit this problem. Perhaps we should put in empty APN's...

Edit - that gives me a thought, have you guys tried an empty apns xml conf file...? I'll try to brew one up today if not, that might solve your problems entirely...
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I think some people that have the freezes at boot due to APN issues might get helped by trying highlandsun's RIL. Many of us don't have these issues for whatever reason.

I wonder if it's something similar to http://mcbridematt.dhs.org/mobile/blog/?p=39

A radio logcat (adb logcat -b radio) at bootup would be useful.

Also, if you have acore force-closing - get an ADB logcat! Every time I've had an acore force-close loop it was due to a corrupt database. Shouldn't happen with a fresh data.img though.
[Touch Pro2, Tilt 2 Android Development] wilkok:
I am using a European gsm sim while residing in the USA on a rhod210. I installedthe FX06 package from march 25th. I'm relatively new to all this (still amazed at how well it works, I installed opera 11, skype and rhapsody so far).

I followed your advice, turned off airplane mode, and examined the APN settings. It appears the settings are correct for the european gsm operator associated with the sim in the phone. I tried disabling the 'Data Roaming' option, which solved the performance/stability issues.

I suspect that improperly setup roaming settings may be the cause of the problem in my case. I've never really worried too much about setting up data roaming due to the cost so I'm with having it disabled.

Now that it's functioning I will be able to check out the SMS! :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hey all,

I have a theory on the freezes, can someone who experienced it help me out?

See this post.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I will try this in the morning if I have time, if not, tomorrow evening. UTC +8
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I think we should really encourage people to get logcats... ADB is up and running during the boot animation so they should be able to catch the freeze on a radio logcat.

Admittedly, there is a possibility the last few messages might not get sent, unlike logcatting to SD, but so far it looks like no one that can reproduce the "freezes at boot" problem has even attempted to pull a radio logcat and post it. If you're able to go into settings to pop it into airplane mode, you should be able to start logcatting before it goes boom.

Waaaait a second... it looks like ryannathans is on Telstra?

http://mcbridematt.dhs.org/mobile/blog/?p=39 - we might have SIM timing issues in our RIL too. I'll look at this later - unfortunately I likely won't have much free time to poke at stuff until Sunday at the earliest.

Edit 2: Looks like Ryan has attempted to pull ADB logs, I'll see if I can see anything in them tonight. Haven't seen attempts from anyone else.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Telstra branded phone ;) I have an iinet sim (uses Optus network)

If the logs aren't good enough, tell me what you need and I will get it to you :)
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Try to get ADB running - since you're on a Linux box it shouldn't be too difficult.

Then, assuming you can at least get to the xdandroid boot animation (it sounds like originally you were having a kernel freeze, and then later had the "Android freezes shortly after the UI comes up unless you put it in airplane mode" issue), plug in the USB cable and pull an ADB logcat from the radio.

The following command should dump the radio logcat to stdout, easy enough to redirect it to a file, this is how I usually do it (my udev rules for accessing adb as a mortal only work half the time, so gotta use sudo):

sudo /path/to/adb logcat -b radio -v time > logcat_thiswentboom.txt

Wait for the freeze, then you can control-c the above command
[Touch Pro2, Tilt 2 Android Development] slobba:
Don't want to hijack the thread (I haven't been having the freezing issue) but I wanted mention that I have the exact symptoms and error messages that are detailed in the blog page that Entropy512 points to. I have attached a logcat of the radio and the similar error messages can be seen on lines 323-340 and also 582. I am using a Telstra SIM.

Hope this helps.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
See Attached.

I also noticed that in APN list NO radioboxes were marked, however my MMS settings are there AND the correct APN for data. All I have to do to stop freezing is check the radiobox for "Optus" with the subline 'internet' and bye bye freezes.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You're still using the original RIL. Judging from this log, it looks like the radio failed to connect because it used the wrong APN, and the RIL failed to notice the error message. I'm pretty sure this bug does not exist in my RIL.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I have downloaded the source of xdandroid (that I am working on anyway)

how do I replace the RIL?

Do I need to recompile?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Read this thread http://cleanimport.xda/index.php?threads/1009112/

No, you don't need to compile anything.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Is it possible to compile it into my custom build?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Of course. Just fetch my git repo into your current one and then checkout the androidhtc1 branch. (I guess I should have created a new branch name, since only 2 commits had anything to do with the androidhtc tree...)
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Have a look at the first post again, I put up the real fix finally :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Explanation

The hang is because the ril is stuck, it launches pppd and waits for a success status from it. But in this particular case, the connection used the wrong APN so pppd cannot succeed. With the "persist" setting in the ppp options file, pppd also never returns on failure, so ril waits forever, and everything grinds to a halt.

Commenting out the persist setting is the main fix for this. The additional ipcp/lcp lines are to decrease the time pppd spends retrying the connection setup, so that it will quit in less than 60 seconds, which allows ril to recover from the error sooner. I have some more patches for ril which will hopefully make the recovery even faster, coming up.
[Touch Pro2, Tilt 2 Android Development] dewagprs:
need help,

when i use RIL in my HTC tp 2 (android FRX06),

Data connection not working..

how i can solve this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Which rootfs are you using?

I was trying to use hyc's newest RIL and F22's rootfs with 'hyc RIL support' but something was awry. I wasn't able to get data until I used hyc's rootfs. I'm not positive this was the fix, but it seems that F22's rootfs with hyc RIL support no longer supports hyc's newest RIL.

I haven't confirmed it positively yet, but in my own independent tests this is what I have found...
[Touch Pro2, Tilt 2 Android Development] ryannathans:
As to what arrrghhh said, just follow the exact guide in my signature - Introduction to Android. If you don't have data then, we will investigate further.
[Touch Pro2, Tilt 2 Android Development] dewagprs:
I've been following your instructions, as in "Introduction to Android - SD Card".

But the "Data Connection" is still not working, APN settings are correct.
[Touch Pro2, Tilt 2 Android Development] dewagprs:
new problem appears again, after a few minutes, when i use GSM mode, GSM mode turn into CDMA mode and even no signal or network received, :confused:
[Touch Pro2, Tilt 2 Android Development] diegolvobanania:
My cents, maybe that will help:

I played a lot with Data and Wifi toggles yesterday evening and today and finally, data connection couldn't be activated anymore.

As i thougt the toggle dmaaged a file, i tried to install highlansun's RIL, no result.

Then I tried to replace the system.ext file by a fresh one, no result.

Then i restored APN settigns from deafult settings, no result.

Data connection (3G) came back by making a network detection from the settigns menu.

Give it a try, you never know...
[Touch Pro2, Tilt 2 Android Development] dewagprs:
problem "no Signal / No Network" solved when i use kernel 1253..
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I sincerely hope you aren't using the files from this thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You've posted this in 15 places, and I already told you that - why are you so surprised that what I told you was correct?!?

You don't need to post this in every single thread.