yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] LinoX:
ok, but in your thread about ril you say that

"Update: Everything in my initpppd branch has been merged into the main xdandroid repo. All of my fixes will be in the next official xdandroid builds, there's no longer any need to use my personal repo."

So... the ril HAS been merged but not the rootfs.

(is there a reason for this?)

Moreover as far as I understood the new ril requires a patched rootfs so I suppose that if you merged your code into the standard git you already merged the rootfs changes (to the standard rootfs git)...

Am I right? So if I download the rootfs built on 16 may I get your patches but not f22's?

Is there a reason why those are still not merged?

I'm going crazy trying to follow all those 10.000+ post!!!!!

It is an HELL!! we should try to keep things as simple as possible:

when a development is completed (like F22's) the thread should be marked as "completed/merged" and closed.

So..the new audio routing you are working on is still "in testing stages" and it makes sense to be opened but this one has already been tested and should be merged and closed IMHO.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
F22's work has not been completed, who ever said it was?

Yes, the RIL has been merged, but not the rootfs. As far as I know, the reason is because F22 has not yet asked for his changes to be merged. He still considers them incomplete. Feel free to have a conversation with F22 and impress upon him your Humble Opinion.
[Touch Pro2, Tilt 2 Android Development] pleaseking:
Help with Russian layout?

How can I help with the Russian keyboard layout? I understand it's in the works, so maybe I can contribute something to make it done somehow? That's something that I desperately need to switch to Android..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Gonna throw down some posts from this thread related to the Russian/Cyrillic stuff... Search is amazing :p.

#1 and #2
[Touch Pro2, Tilt 2 Android Development] pleaseking:
Thanks a lot although I've actually read those already - search is amazing for me as well :) I'd love to get some insight into how rootfs is actually built. I am not asking anybody to write long explanations just for me, just point me to the relevant wikis/threads and I will try to figure out the rest. Sorry if search works for that as well, but I find so many different development branches and components here so I am a little bit lost.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm not really in the know as to how the rootfs is built - I know there's a script for building it on the repo, and that's about it...

What are you looking for? I assume you've seen the repo for the rootfs?
[Touch Pro2, Tilt 2 Android Development] F22:
rhod 500 issue

I've confirmed that there is an issue with the microp key layout file for the rhod500. I am looking into it. With the tilt2 bug now fixed, this is the only existing bug I'm currently aware of in this rootfs.
[Touch Pro2, Tilt 2 Android Development] randomblame:
good work f22 I'll test out the new one shortly

*edit-

It's working correctly again on tilt2 - oh and we do have an envelope button it's directly left of the space bar.
[Touch Pro2, Tilt 2 Android Development] F22:
Let me clarify that statment of mine. The Tilt2/Rhod 300 doesn't have a dedicated envelope key the way the others do. The primary duty of that key on the 300 is to print a comma. Unfortunately search/short-cut functionality is dependent upon the keycode and that is assigned at the layout level in android. So I can't assign search/short-cut to fn-, in the keymap. On the other hand if I assigned the keycode SEARCH to the scan code for the comma key in the layout, you'd get search/short-cut every time you pressed that key, even when you only wanted to print a comma. That issue doesn't exist on the other rhodium models currently in the git tree because they have dedicated envelope keys that have no other purpose.

BTW, I'm glad to hear it's working properly on the Tilt2 now.
[Touch Pro2, Tilt 2 Android Development] thomas d:
hey f22 so i tried out your new rootfs and it goes to home by putting b4home in the startup text but i cant seem to figure out how to make it bring up the recent app folder. Right now i just switched back to your old rootfs that you made awhile back
[Touch Pro2, Tilt 2 Android Development] F22:
The correct startup option for the new rootfs is: b4HOME

Linux is case-sensitive, so HOME needs to be capitalized.
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod500 Bug Fixed!

Finally squashed the rhod 500 bug. The layout file was failing to load due to a typo. The first post has been updated with a link to the latest rootfs image. Thank you jmstumme for reporting this one. All known bugs have been fixed. If anyone is still encountering problems with this rootfs please report them.
[Touch Pro2, Tilt 2 Android Development] CrEOF:
This is great, thanks! Been playing with it for a bit on my Tilt2 and I've noticed a couple of things (and being an Android newbie/noob maybe the cause):

Using PPT as the search key, when I press PPT with any of the shortcut keys it brings up the search with the shortcut key in the search box. No matter how fast I press the key there is always at least one character in the search box.

This may be an app issue, but not all the keys function in Terminal Emulator (both from Dev Tools and "Android Terminal Emulator" from the Market). It seems like it's mostly the useful ones (_ ! $ ctrl/ok), though being able to get the pipe with fn-l is awesome!

My Tilt2 thanks you, you've saved it from an "accidental" fall into a toilet for at least a few more days :)
[Touch Pro2, Tilt 2 Android Development] F22:
Shortcuts require you to hold down the search key while pressing a letter or number. It's a bit counterintuitive, I know, since shift/fn/caps all only require one short press before pressing another character, while Search needs to be held down as you press the other character. I suspect it's because Search was originally intended to be a button, and buttons unlike keys, were given a "long press" function. So opening up short-cuts is Search's "long press" function.

Apps aren't required to respect the keymap. They're free to do what they want with the keycodes that are sent to them. For example, terminal emulator doesn't respect the symbol key, but the browser does.

My pleasure. :)
[Touch Pro2, Tilt 2 Android Development] CrEOF:
I think maybe it's not working correctly then? If I just press the PPT button, nothing happens. If I press one of the shortcut keys (on the hardware keyboard) while holding PPT I get the behavior noted above. It sounds like PTT-B should bring up the browser? I get a "search bar" with the character "b" in it with a list of results below it (Browser, BBC, best buy, bank of america). I checked in the Quick Launch settings and they are all set to default (like you listed). Not that this is really an issue for me since I don't know if I'd really use it much (or at all before this update), just wanted to give the feedback.

Thanks again!
[Touch Pro2, Tilt 2 Android Development] F22:
Please post your startup.txt.
[Touch Pro2, Tilt 2 Android Development] CrEOF:
Here you go:

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 b4HOME physkeyboard=tilt2-pttSEARCH"
boot
[Touch Pro2, Tilt 2 Android Development] F22:
Looks good. The hw3d.force=1 isn't really needed any more since it's the default, but it won't hurt anything. Can you also post the contents of /sdcard/kbd_info?
[Touch Pro2, Tilt 2 Android Development] CrEOF:
Thanks, I'll take it out then. I like to keep things as simple/clean as possible :). Here's the kbd_info file:

Selected Keyboard: tilt2-pttSEARCH
RhodInfo=tilt2
RhodModel=tilt2
Rhod100Lang=
RhodOptions=-pttSEARCH
mpkl=tilt2-pttSEARCH
Selected MicroP Key Layout: /init.etc/keymaps/tilt2-pttSEARCH_microp-keypad.kl
Selected MicroP Key Code Map: /init.etc/keymaps/tilt2_microp-keypad.kcm
Mapping Button 4 to HOME
[Touch Pro2, Tilt 2 Android Development] F22:
tilt2-pttSEARCH bug - ptt doesn't get assigned to search

You're right! There is a bug. I'll post a fixed rootfs shortly.
[Touch Pro2, Tilt 2 Android Development] F22:
tilt2-pttSEARCH bug squashed

2nd bug today found and squashed. See the 1st post for the updated download link. Thank you CREOF for the feedback.
[Touch Pro2, Tilt 2 Android Development] CrEOF:
Thank you! That fixed it.
[Touch Pro2, Tilt 2 Android Development] thomas d:
Thanks f22 that worked perfectly
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Thanks F22, works great now! Is there anyway you can map the mute button on the back of RHOD500 to something, someone at some point had an idea for it...
[Touch Pro2, Tilt 2 Android Development] snalbansed:
spreadsheet

Hi F22

Thanks for this - I'm looking forward to getting my home button back, just about to try it out!

In the spreadsheet you have the information about b4HOME, but the capitalisation isn't right.

Ed
[Touch Pro2, Tilt 2 Android Development] Raul^:
Can I somehow tweak your keyboard layout to and polish special characters? They aren't on keyboard, but I would like to add them to make this phone almost perfect.

If it's possible I would like to know how to make them as combination of Sprint Mail key or other.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
For my phone it's need to be b4HOME otherwise it won't work.

Read it wrong:P
[Touch Pro2, Tilt 2 Android Development] F22:
Editing Key Map/Layout Files

Yes it is. It won't be quick or easy however, and will require some real work on your part. Probably the most challenging part is slipping the modified keymap and/or layout file back into your rootfs. Do you have access to a computer running Linux?

If your goal is to make a Polish keymap/layout set then probably the easiest and most straightforward approach would be for me to supply you with an existing keymap/layout set and for you to make the needed alterations for the Polish keyboard. You could then send them back to me so that I can compile your keymap and then slip them into a new version of my rootfs for testing. I plan to submit all of these new keymaps/layouts to the main tree for inclusion in future versions of xdandroid once they're thoroughly tested.

On the other hand if your goal is to make a custom set just for yourself, you'll likely have quite a bit of work ahead of you if you aren't already comfortable with linux.

Android's method of handling the keyboard is rather flawed. It depends on what you're trying to do. Making a key print "special" characters is pretty easy as long as you know, or can successfully look up the UTF8 hex codes for those characters. On the other hand, if you wish to assign a single key two different keycodes such as SEARCH and CAMERA depending on whether the fn key is pressed, that is impossible given the way Android's java framework is written. A physical key's scan code may only have one keycode assigned to it, and functionality tied to the keycode can't be made dependent on a modifier key such as fn, shift or alt.
[Touch Pro2, Tilt 2 Android Development] F22:
b4HOME spreadsheet error

Thanks! I was wondering why people were still adding b4home instead of b4HOME. I'll post an updated spreadsheet shortly.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Hi F22,

I changed keyboard layout rhod100_uk to be able to use the Croatian "special" characters. I have not compiled KCM file because I do not use Linux, so I properly hard coded BIN file. For now, I use changed BIN file mounted via "custom_shells" in the "froyo.user.conf" file and works very well. I also changed KCM file to see what keys are changed.

Could you please slip files into a new version of rootfs for testing.
[Touch Pro2, Tilt 2 Android Development] F22:
Updated Key Listing Spreadsheet

New key listing spreadsheet posted! Changes include:

1) The b4HOME option is now correctly capitalized. (Previously it was listed as b4home and that didn't work since Linux/Android is case-sensitive.)

2) Entry for rhod100_nl added.

3) Entry for the upcoming rhod110 key map/layout set added.

4) Correctly noted that the rhod300/tilt2 does already have a home key on its keyboard.

See first post for the download link.
[Touch Pro2, Tilt 2 Android Development] F22:
Croatian Key Map

Nice. I'll put it on my to do list for integrating into the rootfs over this weekend.
[Touch Pro2, Tilt 2 Android Development] F22:
Croatian Key Map

Hmm...I don't see a user manual for the Croatian model of the rhod100 on HTC's site. Can you take a picture of the keyboard and post it here. I'd like to add the same new keys I've added to the other kbds to this one as well.
[Touch Pro2, Tilt 2 Android Development] trusa1:
There is no Croatian model of the rhod100. In Croatia we are using UK version of the rhod100, so keyboard layout is very same as is rhod100_uk. Croatian "special" characters I achieved by using combination of FN + Z, S, D, C, V keys. (Ž, Š, Đ, Č, Ć).
[Touch Pro2, Tilt 2 Android Development] husam666:
good job with that mute button ;)

keep up the good work
[Touch Pro2, Tilt 2 Android Development] Raul^:
Yes. Can't I change keymap from within Android?

My phone is RHOD400, and I think that way is even better.

Doing it for myself would be a waste of time. And If I could make it for Sprint, making it for rhod100 (as most TP2 in Poland are HTC ones) would be easier.

I can look up for the codes. So it's not lke in WM. How is it done then?
[Touch Pro2, Tilt 2 Android Development] F22:
Working Mute Button

LOL. Now that I think about it, I was under the impression that the issue with the mute button was in the kernel, and once the kernel was properly adjusted it would be fixed. So I hadn't really looked at it. Manekineko actually brought the subject up with me in a conversation in mid-January about it not working and possibly reassigning it to something else. So I will give him credit for putting the idea in my head of reassigning it, although it wasn't until two days later or so when I actually got around to looking at it. It was only then that I realized that the REAR_MUTE keycode that had been assigned by whoever had added that entry wasn't even defined by android. So I replaced REAR_MUTE with MUTE instead, and then it started working. Very understandably, he did the same thing in parallel at pretty much the same time with the rootfs he released as well.
[Touch Pro2, Tilt 2 Android Development] F22:
New Rootfs Image (Feb 6, 2011)

A new rootfs is up. I've pulled into my build the new RIL (radio interface library) that was just committed by stinebd to the rootfs git, keeping my rootfs up to date. Please let us know if the new RIL has any effects on your handset. I've also added rhod110 support as previously promised.

See the first post for download links and the changelog as always.
[Touch Pro2, Tilt 2 Android Development] F22:
Missing Rootfs Link

Whoops! Fixed! thanks for pointing that oversight out.

As to your question, the keycode for the PTT is assigned in the microp key layout file. Unfortunately, as things currently stand a new microp file needs to be created for each combination of keycode options. While this works for a small number of options, this will quickly become unwieldy for larger numbers, ie. the current 2 options results in 4 possibilities, 3 options would result in 8 possibilties, 4 options would result in 16 different possibilities, etc... I do plan to look into the possibility of reassigning keycodes from a menu within XDAndroid, something similar to what is currently possible with shortcuts, but that's a ways off right now.
[Touch Pro2, Tilt 2 Android Development] the.decoy:
Awesome! Many thanks for including the RHOD110 in this F22 :D

Do you have any control over what the LOCALE setting will be with that layout?

As I mentioned to you before (on IRC), the rhod100_uk layout would always set the locale to EN_GB (i.e. British news/weather defaults, UK google servers, etc).

Technically the home country for rhod110 is Australia (locale EN_AU) but I understand that plenty of them were (unofficially) exported elsewhere.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Is this the best place to give feedback on the rootfs changes?

On my Rhod400 the new RIL does NOT help...the last few boots have actually been slower than previous...does it matter what kernel is being used? I'm using the 2/2 test kernel for rhod...
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Rhod100_nl

Just wondering what changes the Rhod100_nl have? Is it just the name? cause as far as I know a dutch Rhod100 is the uk version? Anyway, no chance of testing for me yet, Rhodless for a week now, stupid repairs.. My fingers are freaking out on a samsung dumbphone!
[Touch Pro2, Tilt 2 Android Development] jmstumme:
boot is a lot faster with new rootfs on rhod500 :) THANKS!!!
[Touch Pro2, Tilt 2 Android Development] F22:
It's the same. So no, there wasn't any real work involved to add it. ;)
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Has anyone else had an issue with the rhod500 not waking durring a phone call? I currently have the b4HOME enabled.
[Touch Pro2, Tilt 2 Android Development] LinoX:
Hey, F22, were your changes committed to the main rootfs? :))))
[Touch Pro2, Tilt 2 Android Development] F22:
new rootfs w/ system_server bug fix

New Rootfs posted! See 1st post for both the changelog and the updated download link. Thanks to stinebd, the system_server bug is now believed to be fixed!
[Touch Pro2, Tilt 2 Android Development] F22:
Not yet. I will try to get them submitted in the next few days.
[Touch Pro2, Tilt 2 Android Development] F22:
The b4HOME option simply gives you a different gpio key layout. It has no effect on whether or not your phone will wake during a phone call. Now if you set your power button to end phone calls then it will end the phone call during a phone call even if the phone falls asleep. If that happens then you can wake the phone without ending the call by pressing the menu button.
[Touch Pro2, Tilt 2 Android Development] sublemon:
Just fired up the new test kernel by wistilt2 and this rootfs. I'll give it a work out tomorrow and see how it fairs out. I've only had 2 system server crashes recently so I'm not sure if I'll see much improvement, but I will report none the less.
[Touch Pro2, Tilt 2 Android Development] randomblame:
new rootfs really improved boot speed! We'll see if the system server issue rears it's head
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice! Glad to see you integrated this so quickly :p.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
i have b4HOME is my startup file, but i can't end a call with that button(witch i knew). Is there a way to have end call mapped as: short press - end call and long press - home?

Or do i need to change it in the layout file?

Find the answer in post #1. Sorry
[Touch Pro2, Tilt 2 Android Development] Thegn:
Hi,

@F22 and devs

Don't know where else to post this, but I guess the fix in the rootfs is the same as the one announced on the xdandroid twitter page? I tested the new rootfs on my Blackstone running the latest XDAndroid FRX04, and it seems like it broke WiFi.

WiFi worked before switching to the new rootfs. The only change I did was change the rootfs and delete all the cache on the SD-Card and removed the data.img so the install would be fresh and nice.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
If you look at the changelog in the rootfs commit, you'll see the only thing added is a simple sleep command in the sensor library, nothing else. So no the officially committed rootfs did not break wifi. I can't speak to F22's version of the rootfs, but I'd doubt it broke wifi either. Since you deleted data.img anyways I'd recommend just starting with a stock FRX04, update the kernel to the official 1253 version (with the modules file! very important for wifi), update the rootfs, and see how that goes.
[Touch Pro2, Tilt 2 Android Development] crazyC:
Thought I would try this out with FROYOX Red, so swapped in the feb 9 rootfs.

Everytime I used the keyboard it went nuts.

Amended my startup so that the RHOD100 had the uk bit after it and voila, keyboard worked a treat.

But, and it is probably not due to the Rootfs, I could receive and make no calls. The phone said it had signal and was dialling, but got nowhere, if I called my phone I could hear it ringing on my landline but the phone did not respond, even with screen already awake.

I booted back to winmo, dropped the original rootfs in and reloaded Android - and my calls are back.

Dunno what I did there to cause this problem.
[Touch Pro2, Tilt 2 Android Development] F22:
Rootfs Changes

I didn't add anything new of my own in this update. I simply synchronized my local tree with the new official rootfs git by pulling over the last 2 commits.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I know that, I was not sure if Thegn had ever used one of your rootfs builds before, so I was saying there shouldn't be anything different between the official version and your version that could be attributed to his problem.
[Touch Pro2, Tilt 2 Android Development] F22:
Default Keymap/Layout & Outbound Calling Issues

It should have worked anyway. I set rhod100_uk to be the default rhodium keyboard in my rootfs. I may need to double check that.

Every so often this seems to happen, and not just with my rootfs. Not sure why yet. Deleting your data.img seems to fix it pretty much every time. (You probably want to back up your apps and other files with a program like Titanium Backup before trying that however.) So some bad or corrupt data may be written out to the date image every so often. Another possible solution that someone told me worked for them is to spend some time making calls from WinMo before going back to xdandroid.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
can some one tell me what the rootfs do? and do i need to update if i have the reference one?
[Touch Pro2, Tilt 2 Android Development] crazyC:
Thats what I thought - but it was not just as if I was using a differently mapped keyboard - everytime I hit a key it was like hitting the back button on the hard keys.

Things just started closing with each key press.

I think I may have buggered something up on my install so may do a clean one soon anyway - too much messing around with kernals and rootfs etc.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Why did you ask this question twice? Crossposting is not cool.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
can you answer? and i thought it was the same thread, simple mistake
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you were planning on asking the same question 2x in the same thread? I answered you in the other thread. I'm still trying to find that explanation page tho.
[Touch Pro2, Tilt 2 Android Development] F22:
Read the first post in this thread if you want to know what this rootfs can do that the reference one can not. As of today, none of the features in the numbered list at the top of that post are in the reference rootfs. Nevertheless, I do plan to commit them at some time in the near future. So it's up to you whether you want those new features now, or would prefer to wait until they make it into the reference.
[Touch Pro2, Tilt 2 Android Development] outerdepth:
I can say I've been running the new rootfs and it seems to be working 100% straight on my 210. I did have to alter my startup.txt file. I won't claim that affected anything anyway. I was just mentioning. You might wanna try erasing your startup file and using a fresh new one.

Just wanted to say thanks for all your hard work. Great job,man. Also, I was curious as to the system server bug. I have looked into it by searching, but am not 100% clear on what it exactly is and where the dev's stand on it as far as fixing the bug. If you wouldn't mind explaining it to me just to sum it up, I would greatly appreciate it, mate.

Once again, thanks to you and arrrghhh and the other devs for all your hard work.