yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
System_server bug should be no more. libsensors had a loop in it that would just spam the system, bringing it to its knees. Stinebd put a wait and continue in the function, and it works great now!

So it is fixed, and the bug symptom was a painfully slow phone (that does not ever get better on its own) and if you check something like 'top' thru adb, the system_server process was the culprit for the overzealous utilization.
[Touch Pro2, Tilt 2 Android Development] F22:
new rootfs

There was another new commit to the rootfs git repo today so I've created another new build to stay up to date. Its author Emwe tells me that it fixes a memory leak in the radio and corrects the exit behavior of the cell-based location hook. As always, see the first post for the download link.
[Touch Pro2, Tilt 2 Android Development] randomblame:
does that mean cell based location services works properly now?
[Touch Pro2, Tilt 2 Android Development] Eodun:
Edit: NVM, stupid question.
[Touch Pro2, Tilt 2 Android Development] F22:
I suppose that depends on what you mean. CDMA location service is still broken. This fix only effects GSM signals.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
finally! support for my beloved rhod110

many thanks!

any suggestion on what kernel/modules to use for the rhod110 - seem to be having freezing problems with whatever I choose (seems to be an issue with that zoom bar?)
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
It seems that when you install this rootfs into the Sense X 10/2/2011 that that distro doesn't boot anymore... When the graphics should show up, the phone reboots...

Rhod100 (Belgian...)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Take a look at the test kernel thread and see if your panel is AUO or EID. If it is AUO, that'll be why you are having issues. Up to now, only rhod100s have been found to have this panel, but then no one with a rhod110 has shown up before!

If it is AUO, please use the new test kernel if you can, and send logs when it freezes. If you can't afford to do that, go way back to the second kernel on November 24th!
[Touch Pro2, Tilt 2 Android Development] F22:
Sense X is probably dependent on modified initialization scripts that set Sense up. In fact my rootfs init script has its own modifications. So I'm not guaranteeing compatibility with any builds aside from FRX03, FRX04, and the upcoming GNX alpha. Once my work gets committed to the git, I'm sure we'll start seeing other new builds that include it.
[Touch Pro2, Tilt 2 Android Development] sjabbie88:
Perhaps I`m mistaking and I can`t remember correctly...

But with this flawlessly working rootfs, I get a popup with a 3x4 table with special characters whenever I hit fn+sym

But If I recall correctly there was a moment, not too long ago, that whenever I hit fn+sym I got a popup with a "huge" table with all kinds of symbols and special characters...is was this with an older rootfs or with FRX03?

and if I remember this correct..is there a way to get this table with all these symbols back?
[Touch Pro2, Tilt 2 Android Development] radcpuman:
I'm using a Rhod300/Tilt2 (FRX04, latest test kernel). The Dpad back light seems to stay on for an extended time. I noticed it first with the 2/9 rootfs. I went to post a comment and noticed the new rootfs 2/10. Eventually it shuts off, not sure what the trigger was. It has been on now for about an hour. The rest of the phone is sleeping fine (blinking green LED). I've made a call, sent a text. Still on.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Was the light on when booting into android? Maybe it works the same as the call, winmo, back buttons.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Interesting, have you ever run with any alternative builds, like maybe from Neopeek? Since fn+sym hasn't been working in official XDAndroid until F22 enabled it in his rootfs, and I believe F22 has already extended the symbols table actually.
[Touch Pro2, Tilt 2 Android Development] F22:
SYM Table Size

The character set for the symbol package isn't in the rootfs, it's in the system package. If you're running FRX04 you'll see a popup with 18 special characters. If you're running a different android system package you'll only see 12 special characters. That's because as Manekineko has already mentioned, I submitted a patch to expand the symbol table from 12 characters (the 3x4 table you mentioned) to the larger 18 character table that was included in FRX04.
[Touch Pro2, Tilt 2 Android Development] sjabbie88:
Hmm,,,getting interesting.

I`m running FRX04 and just updated my Rootfs from 2/2 to 10/2.

So If I understand correctly I should`ve already gotten 18 characters because I use FRX04. And because I just updated my Rootfs, I should once again see the larger 18 character table...hmm,,,I still only get 12..

Unfortunately I can`t remember when it was (and with system package/roofs) the last time I got this larger table :(

btw, is there a way I can find out, when booted into android, what my current/loaded rootfs is? (it`s not in the list @ settings->about phone)
[Touch Pro2, Tilt 2 Android Development] F22:
Hmmm... my symbol palette expansion patch may not have made it into FRX04 for some odd reason. I need to look into what happened with that further.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
rhod110

FN key doesnt work at all D:

FRX04
[Touch Pro2, Tilt 2 Android Development] snalbansed:
What happens when you put rhod100_uk in your startup.txt instead?
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod110

Ah, this is a bug. There is a missing symbolic link. Thanks for reporting it. I'll put out a new version with a fix shortly.

Given that the 110 and the 100_uk are identical, rhod100_uk should work fine for him. ;)
[Touch Pro2, Tilt 2 Android Development] F22:
New Rootfs - Feb 13th

New Rootfs posted. Changes include:

Rhod110: Missing microp key layout link added.

Rhod300/Tilt2: Reassigned ! and @ to keycodes that don't have special properties, and are thus less likely to cause issues.

See the first post in this thread for the updated download link.
[Touch Pro2, Tilt 2 Android Development] the.decoy:
While we are giving the Rhod110 some love ... any chance you happened to notice my post last week? ;)
[Touch Pro2, Tilt 2 Android Development] EazyVG:
Any possibility of having a Russian (Enhlish/Russian) Rhod100 layout that works?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
oh wow. I can't stress enough how much I thank you for the rhod110 support!

F22 = my hero xD

Only just found out that all my keys previously without any second function now have symbols assigned to them, great idea!

-Much Appreciated

ryannathans
[Touch Pro2, Tilt 2 Android Development] pleaseking:
Just echo that but for Rhod210. I've read the thread and I found that I to provide F22 with some files from a Russian Android handset - do I need the one with hardware keyboard? Or any? And any pointers for the quickest way to get those files once I touch the device - I am a complete Android newbie so have no idea where to look :(
[Touch Pro2, Tilt 2 Android Development] EazyVG:
This is the pic of Rhod100_Rus keyboard layout. Is there anyone who knows how to make one for Android? This would be awesome, as even the symbols, by pressing FN key, are not working correctly with available layout options for rhod100.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I was using the b4HOME option, and LOVE the recent apps option, but went back to normal after a day because I couldn't get used to ending calls with the power button. Would it also be possible to have long press on the back button give you the recent apps? So then:

Power = sleep (also in calls)

End button = home or end call

Back button = back

Long press back button = recent apps

Just a request, I have no idea how much time this would take, or if its even possible?
[Touch Pro2, Tilt 2 Android Development] F22:
Russian Key Map/Layout Set

Fixing the function symbols wouldn't take long at all, but I don't believe anybody would be happy with just that. The key I think is to get the yazik button to work which means taking a look to see how Android handles switching between Latin & Cryililic alphabets on native android phones. Once we get that figured out, the rest should be fairly straightforward. It's on my to do list, but I haven't really had much time to look into it as of yet.
[Touch Pro2, Tilt 2 Android Development] F22:
Separating Recent Apps from Home

Nope, sorry. Recent apps is directly tied to the HOME keycode in the framework.
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod 110 Locale Setting

As far as I know, the keymaps/layouts have nothing to do with the locale which is selected via the framework. This sounds like something in the system partition, not in the rootfs. I can look into it, but it may be a good while before I get around to it.
[Touch Pro2, Tilt 2 Android Development] F22:
More on the Russian Keymap

Xirxes was kind enough to get me a copy of the Russian keymap/layout set from the Desire Z. The keys are ordered oddly in the layout file however, so the yazik key wasn't immediately clear to me after a casual observation. If I were to hazard a guess however, I'd say it's either FUNC_1 or FUNC_3. I should be able to take a more careful look at it over this weekend. If I need something further I'll provide you with instructions then.
[Touch Pro2, Tilt 2 Android Development] the.decoy:
No worries, I was just checking in case you had come across anything in the process of defining new layout names (especially since you were creating new rootfs to do so).

I know it sounds like it should be unrelated but I can't imagine why else those of us who used rhod100_uk would end up with EN_GB as a locale (especially when we are literally on the other side of the planet from that locale :rolleyes:).

Sorry I have been meaning to delve into the system image and kernel source to chase this up but since the floods here (Brisbane) I have been busy with work and also for some reason all my installs of FRX04 and latest kernels have been corrupting the filesystem on my SD Card :confused:

Anyway, thanks for reply. It helps to know one way or the other.
[Touch Pro2, Tilt 2 Android Development] EazyVG:
Thank you F22 for having this on your to do list. It is strange, even none of Russians so far have come up with a solution for TP2 on Androis ports. Till then, I guess at least for FN to function well shall I be using the rhod100_uk or other one?e
[Touch Pro2, Tilt 2 Android Development] F22:
Closest existing keymap/layout set to Russian

At the moment rhod100_uk is closest. Some of the fn keys are mapped differently, and you won't get any Cyrillic letters, but at least the basic layout is the same.

And yes, I'm a bit surprised that one of our Russian comrades hasn't already come up with a solution for this as well. Taking another look at the Russian variant of the Desire Z's keymap, the only Cyrillic character actually present in that file is ж. That's the only one that doesn't require the yazik key. Clearly yazik doesn't behave the same way internally that shift and fn do. It appears that I will need to dig deeper into Android's java framework to figure out what's going on with the yazik key.
[Touch Pro2, Tilt 2 Android Development] husam666:
power button as home, please :)
[Touch Pro2, Tilt 2 Android Development] F22:
Switching Between Latin & Cyrillic Alphabets

I've looked at this more closely and I've discovered that stock android, including Gingerbread, doesn't appear to have a solution for this. The yazik key looks to be an HTC add-on to the framework. The solution is going to require more time and thought then I had originally hoped.
[Touch Pro2, Tilt 2 Android Development] F22:
Power Button as Home

Very soon. :)
[Touch Pro2, Tilt 2 Android Development] ryannathans:
ctrl key makes FN light turn on, rhod 110.

reinstalling android so i will let you know if this problem persists =)

should I go for gingerbread or froyo?
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Common problem.
[Touch Pro2, Tilt 2 Android Development] F22:
FN Light Attached to the Ctrl Key

This is an issue with the kernel, not the rootfs. I expect WisTilt2 will be posting a test kernel to fix this in the near future, if he hasn't already done so.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well honestly he might be waiting to get the proper fix in userland. These shouldn't be handled in the kernel, userland should simply tell the kernel what to do...

He does need to get the LEDs right tho, he keeps getting distracted by the failed wake issue :p.
[Touch Pro2, Tilt 2 Android Development] Quincux:
Thanks for your job.

Works flawsly on my Tilt 2 using XDA FRX04 reference or FROXO X RED with kernels 1262,1260,1253. Keyboard LEDs (FN/SHIFT).

On tiad8 BLAZN don't works.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Keyboard LED's are in the kernel, so not sure why you posted that in this rootfs thread.

Also, if you have an issue with a particular build, please post in that thread.
[Touch Pro2, Tilt 2 Android Development] F22:
New Home, Power, Search & Camera Button Options

By popular demand, I've added the ability to reassign the power button to HOME and front panel button 4 (end) to POWER. In addition, I've added the ability to reassign button 4 to SEARCH and CAMERA as well. So b4 can now be set to HOME, POWER, SEARCH or CAMERA depending on one's preference. Finally I've also added the ability to reassign front panel button #1 to HOME like it is on most native android phones. The first post has been updated with the details. See the changelog if you just want to see the new stuff.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Wooooo! Great job! Gonna commit soon?:D
[Touch Pro2, Tilt 2 Android Development] F22:
I'm still mulling over the "final" option name(s). Right now I have physkeyboard= for keys handled by microp and gpiokeyopts= for keys handled by gpio. While it's dead-on accurate regarding what's going on beneath the hood, I think it's also a bit confusing.

I've decided that next I'm going to write a little program to dynamically build the key layout file. That should reduce the exponentially growing overhead of maintaining the microp layout files to something more manageable and enable me to "close the hood" so to speak so that regular users won't be as exposed to the internals unless they really want to dig deeper. Once I have that done, I'll finalize the command line syntax and commit.
[Touch Pro2, Tilt 2 Android Development] EazyVG:
28th rootfs is really cool with home button for recent apps working nicely and giving previews of all LaunchPro screens. Just waiting for Russian keyboard layout release.
[Touch Pro2, Tilt 2 Android Development] F22:
F22's Latest Rootfs (Mar 1st, 2011) Improved Froyo Support

New rootfs image. Shouldn't make a difference for Froyo, but for Gingerbread it includes the latest commit to the main tree so that it will use the libraries for Gingerbread instead of Froyo. See the 1st post for the changelog and download info.
[Touch Pro2, Tilt 2 Android Development] snowmaiden11:
Quick question - just upgraded to the FRX05 system.ext2 and I can no longer find the "set power button to end call" option under accessibility and I reallllly want it since pulling up the on screen menu can be finicky in a call. I want to be able to use option 1 (set button 4 to HOME/long press recent apps) instead of switching that with the power button. Anyone know how I can get it back, or is it just gone under FRX05?
[Touch Pro2, Tilt 2 Android Development] tovarish:
Hi F22,

Is it possible to add some configuration to your next release to set the "Rear Mute" button to "SEARCH". I dont really use the rear button for MUTE and would like to use it as SEARCH.

What I have done for the time being is that i mounted the img file and changed the keycode 102 to SEARCH instead of mute in the rhod100_qwerty_microp-keypad.kl keymap file (since I have a rhod100_uk). It would be nicer to have a command line option in STARTUP.TXT to do this.

thanks,

tovarish
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Hey F22, I wonder if you'd consider this patch to the init script. Instead of blowing away /data/etc and reconstructing it on every boot, it checks timestamps of rootfs and system.ext2 to decide if it really needs to change anything or not. Speeds up the boot process a bit and saves unnecessary wear on the SD card.

[fixed patch now attached.]
[Touch Pro2, Tilt 2 Android Development] likounin:
i'm using raph100 under frx05 and i cannot find where is the setting button which used to be the #4 home button,but it just returns to the launcher
[Touch Pro2, Tilt 2 Android Development] shatred:
it can be done trough an app called "spareparts" where the setting says: end button behavior set it to return to home screen.
[Touch Pro2, Tilt 2 Android Development] likounin:
you misunderstood me, but thank you anyway:-)

after tried the latest roofs.img , the problem was solved
[Touch Pro2, Tilt 2 Android Development] highlandsun:
With this patch, I no longer see MMC I/O errors during boot on my class 10 SD card. They still crop up once in a while when certain apps run, but at least now I know simply booting can't corrupt my filesystem any more.

There are two parts of the patch that I need to point out.

One, I changed the vermagic check in the modules from using wlan.ko because wlan.ko is missing in WisTilt2's latest testing kernels. I mentioned this already in the testing thread.

Two, I commented out a chmod of /bin/pppd because there's no reason to ever be modifying the root filesystem at boot time. This chmod should have been done when the rootfs was created. But if it hasn't been done yet on your rootfs, you need to do it once.

Also, the timestamp checking is based on the assumption that the copy from root init.etc and system/etc to /data/etc is done in a way that preserves their original timestamps. My patch does this using tar, but the original script just used cp which doesn't preserve timestamps. So if you're using my patch on an existing data image and switching from an old root or system to a slightly newer root or system, it's possible that it won't recognize it as "new". And if you're switching to an *older* root or system, it definitely won't do anything. Possibly we should check for the timestamps matching exactly, to allow both upgrading and downgrading the rootfs or system, but so far I've never had any reason to switch back to an older rootfs.
[Touch Pro2, Tilt 2 Android Development] Centz:
Bug?

Using RHOD400 and have had a lingering issue the past few releases where when I have the keyboard out the back button on the screen panel does not work. This forces me to slide in the keyboard to have back button functionality.

This issue is only when the keyboard is slid out. When I simply rotate the phone to landscape (with the keyboard still in), the back button works fine.
[Touch Pro2, Tilt 2 Android Development] wmg316:
I installed the rootfs.img in order to have my PTT button on my Tilt 2 to call up the camera.

I must be missing something...it is not working.

I am running FRX04 Reference build...FRX05 system.ext2...WisTilt2 3/1/11 kernel. I downloaded 'rootfs-rootfs-f22-20110301-f4409a9.img.7z' from the first post, extracted, renamed to rootfs.img, dropped in andboot folder.

Startup Text:

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 rel_path=andboot north_am_dialing=1 force_cdma=0 pm.sleep_mode=1 acpuclock.oc_freq_khz=747110 hw3d.force=1 physkeyboard=tilt2"

boot

Any advice on having the PTT default to camera?

EDIT:

Also with this rootfs.img I seem to have lost my "auto rotation" in my browser, YouTube, Maps.

I can delete this rootfs; go back to the 2/24 version; boot to Android; auto rotation works.

Power down; replace rootfs again with the 3/1 version; boot to Android; auto rotation does not work.

Power down; back to 2/24 version; boot to Android; auto rotation works.
[Touch Pro2, Tilt 2 Android Development] F22:
tilt2 PTT as camera button + auto-rotation

1) Have you tried holding the button down for longer instead of just a quick press?

2) Does your camera app open up fine if you start it up from the launcher?

3) Please post the contents of your /sdcard/kbd_info file.

4) I haven't made any changes that could potentially affect auto-rotation to my knowledge. It auto-rotates in my browser just fine. Is anyone else experiencing a problem with auto-rotation related to my rootfs that they're not experieincing with the stock rootfs?
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod400 back button + keyboard weirdness

This problem does not occur on my handset which is a rhod210. Are you experiencing this problem with the stock rootfs as well? Are any other rhod400 users experiencing this issue? Arrrghhh, have you experienced it? Given that the rhodium's back button is physical and not capacitive, this sounds like a strange one.
[Touch Pro2, Tilt 2 Android Development] F22:
Patch to Reduce Writing to SD Card

Sounds great to me. I'll take a look at it.

Lovely, I'm all for reducing the probability of data image corruption as much as possible. It's a very annoyingly real problem as we've all experienced.

Understandable. This way it doesn't reinstall every boot on WisTilt2's test kernels even when the correct modules are already installed.

Ok. I'll take a look to see what the perms on the executable are.

There are often times when problems aren't reported until well after they first crop up, particularly when only a small number of people are affected. It's useful for them to be able to try out older builds in order to nail down when the problem appeared.

The cp's really should have had the -a or -p options set depending on the situation. It's my understanding that these options are available in android's version of cp, so I have no idea why it wasn't done.
[Touch Pro2, Tilt 2 Android Development] F22:
Mute Button as Search

Yes. I plan to eventually add this option. It's on hold until I finish writing my little program to dynamically build the layout files. That will make adding things like this less work since currently every single microp kl file and link would need to have a new version made.
[Touch Pro2, Tilt 2 Android Development] F22:
Cyrillic Key Layouts

The Russian key layout is on the to do list, but since the yazik key doesn't appear to be built into stock android, it isn't something quick or simple. HTC has done it with the G2, but it would be so much more straightforward if I had access to the original source tree.
[Touch Pro2, Tilt 2 Android Development] Centz:
I figured it out. This is an issue with my device, testing it further it occurs while in WinMo as well, so a trip to the Sprint store is due.
[Touch Pro2, Tilt 2 Android Development] wmg316:
1. I have quick pressed; held for 5 seconds; held for 10 seconds. Unresponsive.

2. Yes, camera will launch fine when selected from launcher (app drawer menu).

3. I have attached the kbd_info file from the 2/24 rootfs and the new rootfs.

4. Ok...odd. Today I reloaded the rootfs.img. Initially the rotation problem was there. I checked Settings, Display - Auto-rotate screen is checked. I am running Zeam, so I checked Preferences, General, and I checked Sensor rotation. After this EVERYTHING would rotate. I went back to Preferences, General and unchecked Sensor rotation...and now my rotation is working as it should (i.e., Maps, Browser, YouTube vids are rotating...Home screen not rotating)...maybe a conflict with Zeam?? To see if it "stuck", I rebooted and rotation seems to be ok now.
[Touch Pro2, Tilt 2 Android Development] wmg316:
I wanted to add that the back mute button appears to be working fine
[Touch Pro2, Tilt 2 Android Development] F22:
tilt2 ptt->CAMERA button

The stock rootfs doesn't write to kbd_info, only my rootfs does. So all the entries in both files are from my rootfs. They look fine though. If you change physkeyboard=tilt2 to physkeyboard=tilt2-pttSEARCH does the ptt button work as search for you? Your response to that question will help narrow down the potential causes of the problem.