yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Entropy512:
That's even stranger - They have been working consistently as documented (in multiple places) for the kernels:

Older kernels: Orange if awake/trying to sleep, green if asleep

Newer kernels: Orange if awake, blinking green if trying to sleep, solid green if in deep sleep

I would say "including the FAQ", but the FAQ doesn't cover the "new" behavior of newer kernels, only older ones. However the consistent thing between new/old kernels is that there is no high-level (e.g. notifications) LED functionality currently.

As to the guy who keeps linking Cotulla's twitter feed - Maybe rather than linking his feed in generic, you should link a specific Twitter post and explain why it might be so interesting in this thread or another?

As I understand it, Cotulla is the MAGLDR author, and:

1) MAGLDR is closed source, doesn't make me drool that much - It has to be awesome on an epic scale for a closed-source app to make me drool

2) As I understand it MAGLDR is somehow related to running from NAND, we have a lot of more important issues to get squashed before we can think of direct NAND booting:

a) XTRA (aka QuickGPS) interface not yet implemented on the Android side (no documentation on interface?)

b) Location/time hinting to the GPS not yet implemented on the Android side (no documentation?)

c) No Bluetooth (I rarely use BT, but once or twice a month I do need to make a headset call while driving, and that is one of three reasons I keep WinMo around)
[Touch Pro2, Tilt 2 Android Development] gmanfuzing:
my phone definitely isn't going into deep sleep !

on a side note CAN SOMEONE PLEASE upload an apk for sparetools or include it in the next build so that we can map the end key to home ! please please please, or tell me another workaround.
[Touch Pro2, Tilt 2 Android Development] Quincux:
Download it from Market or here:

http://db.tt/8c81Bqq

Sent from my HTC Tilt2 FRX05 Android Phone
[Touch Pro2, Tilt 2 Android Development] gmanfuzing:
oh, i assumed it wasn't on the market for some reason ? i don't know why. thank you very much !

are live wallpapers an apk that can be installed, i thought i saw it floating around a few months ago but im not sure if you can just install it or it has to come with built in ? any insight ?

im only asking because i use the wp clock app for my home clock and its not a widget, its a live wallpaper!
[Touch Pro2, Tilt 2 Android Development] Quincux:
One more think: my battery is too hot while charging (50°C).

Sent from my HTC Tilt2 FRX05 Android Phone
[Touch Pro2, Tilt 2 Android Development] gmanfuzing:
take off the back cover, its something that can happen in winmo too so im not sure if you could attribute it to android charging.
[Touch Pro2, Tilt 2 Android Development] Quincux:
thanks, i will.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Did you nuke and repave your data.img when you moved to FRX05?

I know "Spare Parts" is included in:

The FRX04 builds

Builds made from the 2.2.1 branch as per http://xdandroid.com/wiki/Getting_the_Source

Builds made from the 2.2.2 branch (as per above - at some point the tree moved from 2.2.1 to 2.2.2)

I would assume that FRX05 would also have it, as since I understand it, it's almost straight out of the xdandroid git repos, so I'm surprised it isn't already in there. (I'm not entirely sure - I've been running straight from the source tree as I finish up my GPS data validity patch)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nope, it can be nabbed on the market. The build was moved from an engineering build to a consumer build basically - so no dev tools or spare parts out of the box.
[Touch Pro2, Tilt 2 Android Development] T_D_H:
spare parts was missed, also no installed apps seem to be showing up on my RHOD500 doing a restart to see if it is just me, also not seeing the phone in droid explorer

just my 2 cents other than that this is awesome
[Touch Pro2, Tilt 2 Android Development] T_D_H:
ignore this post
[Touch Pro2, Tilt 2 Android Development] T_D_H:
reboot fixed the apps not showing up, not sure how i will fix droid explorer though heh

seems to reboot if you get to intense with installing apps though as well, other than that I am still impressed greatly
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Ah, that would explain it. I'm still building eng builds locally.
[Touch Pro2, Tilt 2 Android Development] budbrown:
Hi folks - I've been struggling with this so I hope I can get s ome help. I have a Tilt 2 with the original AT&T rom and I can't get this to work.

Can someone with a similar setup let me know all the files (and which versions) I will need to get this working properly.

Thanks.
[Touch Pro2, Tilt 2 Android Development] rcgators:
This package should work out of the box. Make sure you are using the right startup file for the tilt2 and you did the tscalibration step. What are your symptoms? Then search for your symptoms, it's usually already covered.

Hard to guess what problem you're having with so little info.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Well those two are easy: google doesn't supply a file explorer, but there are several on the market; and both Android and WinMo are using the same system clock - it is just that Windows sets it to be the local time (UTC +2 if you are in Italy) and Linux sets it to UTC and then makes the timezone adjustment in the operating system.

Have fun, and welcome to XDAndroid!
[Touch Pro2, Tilt 2 Android Development] babak:
Thanks my friend :)
[Touch Pro2, Tilt 2 Android Development] rimincha:
I followed the steps and was able to boot up the android os with Tilt 2 device. But touch screen has problem. when i touch any shortcuts, that selects before the shortcut link or when i touch right corner shortcut, the device selects left corner shortcut.......when i get incoming calls, if i click reject the call, device pickup the calls.....if i want to cancel any popup window, i should select ok button rather than cancel button.

Please suggest me anything missing.....or build problem for tilt2 device?? any solution !! Appreciated your help.

Thanks

Rimi
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Anyone can add to the FAQ man, it's a wiki for a reason ;).

There's a lot of things that should probably be added to the FAQ.

You can try getting a lock in WinMo before, but that's certainly not required. Are you using the vanilla bundle in the first post, anything changed?

Dev tools is in AndroidApps/Other IIRC...

Delete the ts-calibration file and follow the steps in the first post to create your own calib file.
[Touch Pro2, Tilt 2 Android Development] argenisaz:
Under M.IP Settings, I changed my MIP_MODE to "Mobile IP Preferred" (it was set to Simple IP Only).

That did the trick for me.

Hope it helps you too! :D

By the way, I forgot to mention that I found this little tweak at HTCMania (http://www.htcmania.com/showpost.php?p=2045999&postcount=838), thanks to HTCMania member Kenouno (http://www.htcmania.com/member.php?u=38108) for this!
[Touch Pro2, Tilt 2 Android Development] mstammyt:
I appreciate the help so much.. I got impatient and loaded the newest one.. and now I cant even get through haret! uggg..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't know what your issue is, but I wouldn't say Android is 'easy' to use on these phones at this stage.

It'll hopefully get easier, but it'll never be simple - even if we get to the flashing stage, it's probably only going to get harder. There's just a lot of silly things that need to be cleaned up, which we're in the process of doing as we move towards NAND.

Might just be best (for you) to stick to WinMo...

If you do still want to try this, you're going to have to provide A LOT more information for me (or anyone else for that matter) to even think about helping you.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I've heard that supposedly Navigation/Maps combined with GPS can cause the phone to reboot eventually - it happened for me maybe once.

You might want to take a look at the RIL or kernel testing threads for methods people have been using to obtain the kernel klog/dmesg log along with radio/system logcats in the background using GScript Lite from the market - Start a log capture and then reproduce the problem, then post the dmesg logs here.

There's an app in the Market called GPS Status - does this work for you?

In my case, with WisTilt's kernels, I haven't had GPS cause any spontaneous reboots. The basic state of GPS for me is:

1) There was a GPS data validity bug to cause you to get reported as at lat/long 0,0 when GPS was not yet locked. The bug is fixed in the FRX06 system images, however the rootfs overrides this bugfix currently and isn't updated.

2) You need to periodically update XTRA data (QuickGPS) in WinMo. Our drivers don't support XTRA.

3) Lock times without valid XTRA data are obscenely long

4) Lock times with XTRA data are still fairly long due to lack of time/location injection in the driver, especially if you are moving. If you get a GPS lock in WinMo and then boot Android it'll re-lock very fast if you try to re-lock within 20-30 minutes. The GPS does stupid things and seems to self-lobotomize to an uninitialized state after 20-30 minutes of inactivity.
[Touch Pro2, Tilt 2 Android Development] MerlinOfLore:
OK. Couldn't get FR06 or Gingerbread to load properly (both ran fine for weeks but now FR06 just loops during boot and never gets to XDANDROID load screen, Gingerbread (GBX0A) will actually boot then lock up). So I copied the contents of the SD card to my laptop, ran HP Format tool doing a full format not a quick format then copied everything back and now I get this when it runs the DOSFSCK during boot:

"There are differences between the boot sector and its backup. Differences: (offset:original/backyp)64: 80/00 Not automatically fixing this."

I even deleted the directory and started from scratch with the same result.

Does anyone know where these "backup" files are? Will deleting then and starting fresh work?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess you mean the data.img for the 'backup' file? It's basically where all userdata goes, and if you delete it you're starting over from square one - excluding anything you added to the build like the test RIL or kernel, etc.
[Touch Pro2, Tilt 2 Android Development] MerlinOfLore:
I thought that as well but them I deleted the entire directory, extracted FRX06 to it's directory and ran Haret... the message popped up BEFORE it creates the data.img file....:confused:
[Touch Pro2, Tilt 2 Android Development] mrife:
I installed the Development application in the AndroidApps/Other, but unfortunately it does not have the Terminal Emulator in it. The list goes down to "Syn Tester" and stops. The Development.apk file was version 1.0 from 20-DEC-2009.

It looks like something is messed up in my configuration. I am going to whip it all clean and start from scratch again.

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well the fsck message you posted is innocuous, and I believe occurs on every boot.

Does it just hang at this message without continuing or something??

Ah... I didn't realize that, sorry. I'll see if I can get that fixed - honestly I vastly perfer ConnectBot to the 'Terminal Emulator' that was in the old dev tools.

I'm thinking I'm going to add some more apps to that folder, but I don't want to go crazy for space reasons and just so there's not some unwieldy list of apps to sort thru.
[Touch Pro2, Tilt 2 Android Development] mrife:
Installed term.apk to get a VT100 terminal. The files listed in kbd_info are:

Mon Apr 25 15:54:56 UTC 2011

Selected Keyboard: tilt2

Selected GPIOKeyOpts:

RhodKbdInfo=tilt2

RhodModel=tilt2

RhodLang=

RhodMPKeyOpts=

gpiokl=b4END

mpkl=tilt2

mpkcm=tilt2

Selected GPIO Key Layout: /init.etc/keymaps/rhod_gpio-keypad_b4END.kl

Selected MicroP Key Layout: /init.etc/keymaps/tilt2_microp-keypad.kl

Selected MicroP Key Code Map: /init.etc/keymaps/tilt2_microp-keypad.kcm.bin

I did not even think of the fact that these files are not accessible for editing while linux (Android) is up and running. I assume that results in the unmounting and mounting of the files. Boy this is getting really deep.
[Touch Pro2, Tilt 2 Android Development] Zombie069:
I'm having an issue with texting, and maybe it's some obscure setting that I'm missing, but not sure.

Put this on the GF's phone, and imported all contacts from google, all went well. Started out with some test messages to myself and back, seemed to work. But then in the text window, the number of the recipient at the top is appended with the +1, so for example, I have my number in her phone contacts as 9702225555, but after I send myself a test message, the next time I go into the thread it shows my number as +19702225555, and it won't send or receive, just get the red triangle. Is there something I can do to keep it from appending the numbers? Or is there another issue?

On Tmo, for reference.

On edit: It seems it's actually adding ,+1 as soon anyone replies. But only in the messaging, doesn't change the number in contacts.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you using Google Voice? Need north_am_dialing=1. Might need that anyway, there's an issue with plus dialing. It's fixed in the new RIL however...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Those issues only ever affected CDMA, not GSM, and he's on T-Mobile/GSM...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
orly... Well what's the prob then bob? I obviously don't know hahaha :p
[Touch Pro2, Tilt 2 Android Development] techluvr:
My first boot has taken about 45 minutes now, and is still going. It is still actively scrolling the code. Any suggestions?
[Touch Pro2, Tilt 2 Android Development] ShowYouHow:
WEP on Sprint TP2 using WiFi ACE?

I've gotten my NRG Sprint TP2 running Froyo 06

Data and phone seem to work with minimal errors.

I could live with BT as well as the camera limits.

I can't change WEP to WPA2 right now, and hear installing WiFi ACE app to get WEB working

Any step by step to doing so? Thanks in advance
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Dunno. +1 makes no difference on my phone.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
10 mins, max.

Did you skip the ts-calibration part? Re-read the first post.

I thought it was pretty obvious, but I've never done it myself - do have the app installed? I think you just put your credentials into it...
[Touch Pro2, Tilt 2 Android Development] TechGuy77:
Finally figured out my no data issue, just wanted to share for others, same should work for U.S. Cellular and Verizon I believe. I created a new APN as follows since Alltel uses #777 to connect to data:

Name: whatever you want

APN: internet

Username: yournumber@alltel.net

Password: alltel

APN Type: *

The rest I left as default and now I finally have data and its 3G to top it all off. I named my APN "U.S. Cellular" due to having a U.S. Cellular TP2 on Alltel and in Android the carrier shows as U.S. Cellular. Not sure if the name has any barring but I am happy with finally after over a month of trying to figure data out. Now to just back the APN and make a few copies on my PC...I am hanging on to this one!
[Touch Pro2, Tilt 2 Android Development] Zombie069:
For some reason I can't multi-quote... But, no not using google voice. Tried that once, friggin joke.

Just fresh install, then google contacts sync'd, then imported texts with sms backup.

Even deleted all threads, then sent test just fine, but a reply screws the pooch.

The +1 works too, the problem is the comma, It changes the number to this in text window, "Contact <,+19072225555>" versus normal, "Contact <9702225555>"

Don't know why, but only on the reply. If I manually type in the number everytime it works just fine, but replying to an existing thread shows the appendage on the number.
[Touch Pro2, Tilt 2 Android Development] angelfire226:
That would be awesome. I'd love to see more available skin options for this build. We've got a new android in the family 2.1 on MT4G. She flaunts it in my face everytime she flips to a new skin, like a blink. What an awesome skinning utility on that thing! Makes me wanna cry. I miss my dusk 2.1, but I'm thinking about running this f/t. Maybe I'll go nand for awhile, until I can really afford a killer new phone. I'm waiting on the fabled Prime, I think. Then I can flaunt it in her face. =D
[Touch Pro2, Tilt 2 Android Development] mrife:
I remounted the root level directory with read write.

I made a backup copy of the KL file in /init.etc/keymaps

The keyboard layout file had a symbolic link to the actual file which was the RHOD 300 AT&T KL file.

I VI'ed the KL file to remove the WAKE_DROPPED option from the MENU key and all the other keys in the "Front panel" section of the KL file.

I restarted XDAndroid.

The MENU button still functions and bypasses the lock screen making it possible to butt dial people while the phone is in my holster.

Did I miss something?

PS: I develop software on Unix boxes that is why I used VI.
[Touch Pro2, Tilt 2 Android Development] argenisaz:
Hello.

When I send an SMS with special characters (ñ, á, é) the other party receives it as a blank message.

I'm assuming that in its currente state special characters are not supported, am I right?

Thanks!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Wrong. The full Unicode set is supported on these builds. The problem is on the other end, whoever you're sending to doesn't have those characters in their font.
[Touch Pro2, Tilt 2 Android Development] moolash:
Notification bar

I have searched this thread, I just don't have the pull down notification bar.

Is it a calibration thing???

Did I miss something??
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, is the bar not there? I can pull it down no problem.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Have you rebooted? I've seen this bug randomly crop up from time to time before. Usually goes away on reboot.
[Touch Pro2, Tilt 2 Android Development] mrife:
For now I am going with a PIN on the lock screen. This works around the problem. I did some searching and found this to be a common problem with Android. There was an option on an older version of the lock screen that allowed the user to disable the menu button. Unfortunately it was taken out.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Odd, I have been using a modified kl file with all the wakes removed as well. Originally I did this by directly mounting and editing the files in Linux, but now I'm just bind mounting my modified versions.

Menu button no longer bypasses the lock screen for me. I never noticed before, but it does wake the CPU when you press one of the buttons (light turns orange), but it doesn't activate the screen, and when I do activate the screen, I'm at the lock screen still.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
If my phone is sleeping properly (solid green, wistilt2's testing kernel), only the power or end-call buttons will wake it.

If my phone is not sleeping (orange light) or partially sleeping (flashing green), then any key will wake it. The menu key would normally then unlock too, but my Active Directory synchronisation forces a pin unlock, so it only gets as far as the pin entry.

If you have used GPS, then the phone will never sleep properly, and any key will wake it until GPS is disabled so it can sleep again.

Remember, this is all with WisTilt2's testing kernel that did a lot of work on getting the phones to sleep properly - I have no idea what the status is with the autobuild kernels and sleep.
[Touch Pro2, Tilt 2 Android Development] OldSkool-II:
Got a [Q] about google maps navigation.

Whenever i try to use it, it says my location is not available?

I'm in the netherlands, and when i just use standard maps, it finds my location...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nav requires GPS - do you have GPS enabled with a lock? Nav won't work with just the 'coarse' location of netloc/aGPS.
[Touch Pro2, Tilt 2 Android Development] OldSkool-II:
How do i do that, cuz i don't know what you mean....
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, enable GPS in Location & Security? Is that your problem?
[Touch Pro2, Tilt 2 Android Development] Fierofiend:
Well my messaging app broke this evening. Every time I click on Messaging I get an immediate force close. I tried to stop the process or clear data, but nothing seems to help. Not sure how to fix this...
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Go into the App Management area where you uninstall apps, select all at the top, then select the messaging app, don't uninstall it just clear the data, you will lose all of your messages, the problem is likely a corrupted message.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If this doesn't work, new data.img surely will ;).
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Partitioned builds

Well, I've figured out why USB storage won't remount on a partitioned install - there's still a mount entry for /sdcard left over in the mount table from initrd mounting the rootfs. When the vold scans the mount table it thinks /sdcard is already mounted, so it doesn't do anything else, and so when you turn off USB storage you're left with no /sdcard.

I think we can fix this by changing the name of the mountpoint so that vold does't get confused. (Pretty sure we can't just unmount it, unfortunately. But still looking into it.)

Nope, there's more to it than just that. I changed the initrd init script to use "/card0" instead of "/sdcard" but that's just the tip of the iceberg. Somehow when we tell the kernel that we want to stop sharing the card, the kernel only reports partition 4 as returning. Annoying...

Ah, I see. Our freakin 2.6.27 kernel is too damn old for Froyo.

It's missing commit 260beca149ba7355f990f1dda6efe65755dff088 which is present in the 2.6.35 tree. So the kernel isn't telling vold what vold wants to know about the SDcard. Time to give up for a while, there's no way we're going to get Froyo working 100% as long as we're stuck on such an old kernel. To say nothing of Gingerbread....
[Touch Pro2, Tilt 2 Android Development] OldSkool-II:
That's already enabled, and when i start the program, you can see the GPS logo on top. But it won't recognize my location...
[Touch Pro2, Tilt 2 Android Development] moolash:
Folks, it could've been a calibration problem. The bar has always been there, I just wasn't able to pull it down. I used my calibration file from Gingerbread, now I use the one attached here.
[Touch Pro2, Tilt 2 Android Development] zikson:
can flashplayer work on FRX06?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First, locks in Android can take an exceedingly long time. Make sure you have a good lock in Google Maps before going over to Nav.

Second, to improve lock times either a) get a lock in WinMo before booting Android, or b) use QuickGPS in WinMo frequently - both of these things will drastically improve lock times.

Well, it doesn't really work too well on native devices, unless they have a lot of horsepower. I've heard it "kinda" works with Skyfire, but I haven't tried it myself.

Test it out, see if you can get it working - and let us know how you did it if you do ;).
[Touch Pro2, Tilt 2 Android Development] Z1nK:
Hi guys.im new on touch pro2.I went through FAQ but didnt find answer to my question.on xperia i used to have ext2 partition but here i see its not needed so i formated my sd to one fat32 partition....then i did everything as in first post but during the haret boot screen (black background...lots of code running across the screen) it sudenly restarts back to wm...

can anyone help me?

I tried different kernels,different android builds (froyo,ginger) same problem....
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try a different SD card, that's not normal.

Also, perhaps try to format with the HP Tool, full format FAT32.

FYI You can run XDAndroid on dedicated partitions, but it's a lot easier to not require ext2 partitions :p.