yashsingh1/xdaforums huggingface dataset:
[Touch HD Android Development] arrrghhh:
I couldn't really follow you post, these were the only questions I could find..

You can overclock - stably, dunno. I don't, so you tell me if you can OC.

Front-facing cam doesn't work, kernel issue not build.

Startup wizard...? There isn't a startup wizard on XDAndroid builds...
[Touch HD Android Development] alphecca911:
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.

Thankyou for your answers to my questions.

Great rom, best i have tried
[Touch HD Android Development] arrrghhh:
Hrm. I've heard BLAC doesn't work on the newest kernel... I'll have to ask emwe, he had a list of changes for FRX07 release, but I assumed they were RHOD-only... Perhaps something is effecting BLAC that isn't supposed to be :p.

I don't have a BLAC, so you'll have to help me - what is the newest kernel that does work? 20110711_082424? Also, how far does it get in the process? If adb is up, logs would be appreciated. Thanks.
[Touch HD Android Development] bdacier:
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
[Touch HD Android Development] arrrghhh:
Sorry mate, seems the newest kernel isn't BLAC friendly! Please tell me which kernel does work... Use the autobuild service and try older kernels. First post has details on how to change your kernel, plus links to autobuild service...

To alphecca911 - most of your issues seem to be first boot related. Remember, you should let it sit on first boot so all the processes that run on first boot have plenty of time to work! I usually let it sit until it sleeps. I've had a lot of weird issues trying to do too many things on first boot on the device... I am impatient just like you probably :p. Just fight it ;).
[Touch HD Android Development] ThaiDai:
That might explain a lot :D

I just checked the system/app folder in the frx07 package. Of course you're right. I copied apps into this without looking. And there was an old SetupWizard.apk.

But just in the moment I started frx07 without any error.

Now I can start to make a real nice package for CWM. And "most" important: try a different boot animation.

I have to thank all XDAndroid developers for this and arrrghhh here for pointing me to it with his posts.

Really great job you are doing here at XDA developers

Thanks
[Touch HD Android Development] arrrghhh:
Heh, I edited my post. I wasn't thinking straight - perhaps I shouldn't be fixing this stuff so early in the morning ;).
[Touch HD Android Development] welard:
lol......:D
[Touch HD Android Development] eusebe:
Hi guys,

Seems that the Blackstone keys problem is a rootfs problem.

I changed the one released with FRXO7.1 by g3rm0's :

http://xdaforums.com/showthread.php?t=999544

and the keys are back.

Unfortunately, with this version the WiFi doesn't work anymore :(

For info in above thread, ThaiDai reported the problem as being a change to the wireless name in FRX07 :

Hopefully, reflecting this change into g3rm0's rootfs should fix it.
[Touch HD Android Development] arrrghhh:
I think I have it fixed. Thanks for your testing, there was a pretty big assumption I made about how the boot process works - and I should not assume :p.

Once I diff'd the images, I saw what was so wrong. I have a user testing the new image now - if all goes well, I will fix the bundle. Thanks.
[Touch HD Android Development] eusebe:
arrrghhh, no all the thanks have to go to you.

On top of that, I understood that you don't even have a backstone device so taking care of us is great !
[Touch HD Android Development] arrrghhh:
Uploading a fixed bundle now. I'll let you know when it's done ;).

Edit - hrm... I uploaded the bundle, but it hasn't updated on files.xdandroid.com. If it doesn't update before I go to bed tonight, I'll put it on multiupload so people can at least get the update...
[Touch HD Android Development] dewasha:
i test and not work in the blac100 blackstone fails to start the animation of the animation repeats indefinitely
[Touch HD Android Development] ksg1966:
is this rom in German language

Thank you
[Touch HD Android Development] eusebe:
Well done arrrghhh keys are back with your changes to system.ext2.

Nevertheless, the WiFi issue with g3rm0's rootfs.img is still there when I put it in as its keys mapping is more convenient (at least to me).

May be you could coordinate a fix with g3rm0 to make it fully operational ?

dewasha did you make sure to include the ts-calibration from the first post and to change kernel ?

For info, I am now using kernel 20110627_223755 level.
[Touch HD Android Development] arrrghhh:
Excellent. Now keep in mind, g3rm0 isn't updating his rootfs - so please only use the official rootfs.

If there's something I can do that might help make the official rootfs more Blackstone-friendly, please let me know what I can do. I'm not exactly sure what his rootfs adds over the official one - thanks!

Edit - I looked at his thread, I honestly don't see what his rootfs provides other than a different layout that mixes up the home/end keys... Please, let me know what I can do to improve the official rootfs ;).
[Touch HD Android Development] eusebe:
You are right it is just a question of changing the Home and EndCall functionalities, but seems that some blackstone users are expecting that.

In fact, g3rm0 introduced an option in the startup.txt cmdline ("physkeyboard=blac") to satisfy the request he had for this layout.

In summary the Home Key (second from the left) is acting as a Home key which means that hitting it bring you direct to the main screen.

Beside the fact that it is better from a pure logical standpoint, this avoids successives Back keys to return to the main screen.

The Endcall button in "your" rootfs being asociated with Sleep is a duplication of the Sleep/Power button, so it makes sense to use it for the "Menu" currently linked to Home.

Of course this could be parameter driven as g3rm0 implemented it.

I take this opportunity to ask a stupid question. I saw in Windows that the bundle includes a couple of additional programs in "AndroidApps" folder but I didn't find a way to navigate to them so I can activate some of them.

Could you please let me know the trick ?
[Touch HD Android Development] Fuseless:
Go to market download a file explorer such as ASTRO and run the .apk files through it.

Regards.
[Touch HD Android Development] Fuseless:
I don't know if any of you have already faced this and were able to find a solution.

Sometimes XDANDROID starts normally, some other times, while running its commands before starting it says something like:

" end_request: I/O error, dev mmcblk0, sector ..." multiple times and fails to start.

I then have to remove battery and re-try, which usually ends up failing as the data gets corrupted.

I searched a bit and found that it may be SDcard related, also aaarghh has already suggested that I try a different card, which I don't have atm, however, my card works perfectly, I have been using it for a while, and formatting it with multiple tools such as HP tool, SDFormatter, ... without any error, and I have been been storing all my data running them through WINmo without problems.

I am using FRX07 bundle with the latest incremental updates (kernel, rootfs, initrd)
[Touch HD Android Development] gummbah30:
First of all, thanks arrrghhh for the update. Runs great!

it's definitely SD card related. The blackstone appears to be picky. I got my two of my SD cards to work by adding:

msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave

to the startup.txt.

good luck,

gummbah30
[Touch HD Android Development] Fuseless:
I just tried to reinstall, didn't give any IO error but froze on the XDANDROID animation.

It doesn't look like I'm meant to enjoy XDANDROID :(

Ill try to add this command and see what happens.

Thanks a lot :)
[Touch HD Android Development] Fuseless:
is this msg normal?:

ext2fs_check_if_mount: no such file or directory while determining whether /dev/block/loop2 is mounted.

/lib/modules/lz0_compress no such file ...

This happens many times for many files, particularly in the /dev and /lib folder, and especially in the 1st run.
[Touch HD Android Development] arrrghhh:
If g3rm0's method can be pushed upstream, I will see about doing it. If it cannot... then it cannot. He will have to continually update his stuff if it cannot be placed upstream...

Or just move the APK to the AndroidApps folder... there's even a file there that encourages you to move the APK's there - any APK's in this folder will be cp'd to /data/app on boot - automatically installed in other words.

Obviously you can also install them by doing the Astro method..

Ah, I remember these. They do *sometimes* get cards working that previously have not - I shall add this tip to the beginning posts, thanks.

I would think this is "normal" - are you having issues because of it?

The fsck happens because it's a loop mount that isn't properly unmounted... the missing files, I'm not sure why but perhaps the modules are missing from the autobuild? Sometimes things don't always match on both sides, and some cleanup needs to be done that was missed. lz0_compress I don't think is a big deal to miss, it's something similar to compcache IIRC.
[Touch HD Android Development] arrrghhh:
Removed... Bad rootfs!
[Touch HD Android Development] tridan:
Just installed your last version and all works fine. Thanks for your work and I will keep you updated with any event that will ocur.
[Touch HD Android Development] tridan:
First problem: When I receive and answer a call, I cannot hear the other person. I must switch speaker on then turn it off and works, but it's not ok to do this every time.
[Touch HD Android Development] Fuseless:
Thanks a lot I think this has done the trick as since yesterday I have not yet seen the IO error.

Will this affect the overall performance?
[Touch HD Android Development] eusebe:
@Fuseless thanks, have downloaded ASTRO and now I can navigate thru my SD Card. I look like a dummy, but this is my first contact with Android and yes, this is what I am. :o

@arrrghhh@ have tested your modified rootfs.img associated with the parameter in the Startup.txt, but unfortunately, this did not change anything to your initial key mapping ; too bad.

Have also tried the "trick" to put ".apk" files in "AndroidApps" and this one is a success !

Question about it, can the ".apk" be deleted once installed after the re-boot or do they have to stay there as long as you use the program ?

Other question, I am very curious to explore the ".img" files (e.g. Data.img or Rootfs.img), is that do-able from Windows using a specific tool ?

In g3rm0's thread, nikitto made a reference to Gizmo Drive software to achieve that, had tried it but did not manage to open the Virtualdrive with Window Explorer, keep telling me that the drive is not formatted.
[Touch HD Android Development] arrrghhh:
Bah, there must be something simple I'm overlooking... reading init it's dead simple, but if it's not working then perhaps I am not understanding it properly. I'll have to look more at the keymapping problems... I really need a few Blackstone users to hang out on IRC so they can test stuff for me :p. Or if someone feels like donating a Blackstone to me... :D

At least they're "fixed" to how they were before. It'll just take a little bit more work to get 'em working how you folks want them to work.

Anyhoo, for the .img files - I use Linux, so I can't really help you in Windows. It's really simple in Linux tho, mount -o loop and the image appears as a folder structure. Gotta love Linux! ;)
[Touch HD Android Development] yasser_de72:
I have that problem too... also with new rootfs and also with adding that parameter to startup...

I'm ready for trying your order step by step ...
[Touch HD Android Development] arrrghhh:
Yea, like I said, I did something wrong. Hop on IRC if you can sometime - I'm not always on, but sometime perhaps we'll run into eachother. Much easier to troubleshoot where I went wrong that way...
[Touch HD Android Development] arrrghhh:
Another doublepost, another test rootfs... Let me know how this one goes guys.

Also, if anyone does have some free time to test hop on IRC and see if I'm around! Freenode @ #XDAndroid... It's much easier to test with someone live on IRC ;).

So try out this new rootfs. Again, make sure physkeyboard=blac is in your startup.txt, like I have below:

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 gsensor_axis=-2,-1,3 pm.sleep_mode=1 physkeyboard=blac"
boot

Thanks guys!
[Touch HD Android Development] eusebe:
arrrghhh, this one seems to be the good one ! :cool:

From what I have seen so far, it is OK so thanks a lot from me and blackstone users.

Hope you will be able to keep this feature in future releases.

Found the answer to my question "can the ".apk" be deleted once installed after the re-boot or do they have to stay there as long as you use the program ?" by testing it, "yes" they can be deleted.
[Touch HD Android Development] yasser_de72:
Great job arrrghhh!

this rootfs fixed that problem...

but i cant be with this build, because of slow speed and crash of market.

when i enter to market while searching, exit quikly...
[Touch HD Android Development] arrrghhh:
Did you try clearing the Market's cache...? In Manage Applications under Settings. If that doesn't work, perhaps try a new data.img? The Market works great for me (albeit a little slow). I found if you update to the newest Market, it works much better. It's kind of a pain, but here's how to do it. Just grab the newest Market APK you can find and follow those directions.

I will admit, the Market does cause issues for whatever reason. I would sometimes get reboots within Android if I update too many apps at once.

Edit - almost forgot about the rootfs comments. Hooray! Use this rootfs in the short-term, but I will try to get stine to commit the change to the repo so going forwards you can use physkeyboad=blac on the autobuild rootfs! Perhaps we should just make that the default - if you have a Blackstone, you get this layout. Please let me know if anyone would be against making that the default for Blackstone. It seems logical to me, but I'd like to hear from you folks, the actual users ;).
[Touch HD Android Development] Halsahaf:
very good work congratulations. So one thing I use on windows mobile WiMoSpeed ​​overclocking. If I have not overclocked mobile phone conssigo open Android. When you run the Haret cellphone freezes and need reset. Is That Normal?

Thanks
[Touch HD Android Development] arrrghhh:
Yes, as is stated in the FAQ you should not overclock WinMo before booting Android.
[Touch HD Android Development] Halsahaf:
I didn't see. Sorry about that
[Touch HD Android Development] dewasha:
in the blackstone work? i try and not work
[Touch HD Android Development] arrrghhh:
Uhm... yes, this works on Blackstones. Perhaps you can provide me with some more information? "not work" isn't enough for me to go off of.
[Touch HD Android Development] eusebe:
Hi arrrghhh, I'm back with a new idea :p as you know, customers are never fully satisfied !

Since XDAndroid seems to be smart enough to launch different actions for the keys based upon the context, then couldn't it be possible to have the EndCall key (the first from the right) to act as designed when, and only when, activated from an on-going call screen ?

Of course, in all other instances it should continue as per the settings from your new rootfs.

It's only a suggestion, one would say "nice to have", but if this can be easily implemented then we will have 100% compatibility with basic blackstone keys PLUS all the advantages of additional contextual actions.

If it's too much asking, don't worry, I'am already happy with what you did.
[Touch HD Android Development] arrrghhh:
lol.

I completely agree with you - but the button cannot act as end call if it is also a "true" home key. We had both (kinda), but long press would not work as recent apps. I tried, trust me I did. I liked having a hard key to end calls...

This is for RHOD - obviously you folks have a slightly different layout with menu being end. I'm not so sure you can have both - what if you need to hit menu in a call...?

There's a little trick you might like - I don't like it personally, but using the Accessibility menu you can remap the power button to end calls. It's not a solution for me, but perhaps you will like it ;).
[Touch HD Android Development] eusebe:
As stated, was "nice to have" so forget about it ; it's OK as it is.
[Touch HD Android Development] Fuseless:
Guys I tried to install market 3.1.3 but as soon as i run it it crashes.

Anyone knwos anything about this?

I have read somewhere that changing the language from the market menu may resolve the problem, however i can't seem to be able to reach any menu.

On the other hand, for those of you who tried the new root file with the home key mapped to going to home screen, where is the menu button now?
[Touch HD Android Development] arrrghhh:
Evidently the "End Call" button is mapped to menu, per g3rm0's thread. I merely took his .kl file and put it into the newest rootfs...

As for the newest Market, how did you install it? It's not as straightforward as other app installs, you have to use adb or su in a shell and remount the system partition RW, and then you can replace the apk for the Market.
[Touch HD Android Development] ying4050:
Wifi doesn't work

I finally installed android into my blackstone successfully, but it always shows mistakes during connecting to wifi. What is going on?
[Touch HD Android Development] mr.bryce:
latitude app freeze

Hi there,

i'm getting random freezes whenever i use latitude, android becomes unresponsive, the buttons will still vibrate but nothing happens and i have to reset to winmo. Is this a known bug with latitude or the gps ?
[Touch HD Android Development] ypsmav:
Audio Stuttering - kill -9 28

Hi Arrrghhh,

I'm very happy with the FRX07.1. The main issue for me is the audio stuttering (besides the BT/In call speaker not working).

How I do kill the battery process?

I thought that was an ADB command, but tried and failed.

Where is this code to be included?

thanks
[Touch HD Android Development] arrrghhh:
What does it actually say? I doubt it says "I've made a mistake" :p. Please be verbose! Also, make sure you read the FAQ. There's a caveat about wifi in the TouchPro2 section, but I believe that could apply to all devices. Basically sometimes Android doesn't detect the MAC address (don't know why it doesn't work for some...) and you have to manually tell Android your MAC using the wifi-nvram.txt file.

Hrm. I use Latitude, but rarely GPS. Have you tried using Latitude without GPS...? Have you tried just using Google Maps with GPS...? I'd like to try and isolate the problem if possible. It also just might be a pegged processor, crunching numbers on other things. Try using it on a fresh data.img (rename your existing data.img to data.bak so you can revert) and see if it's any different.

Also, GPS takes forever to get a lock without using something like QuickGPS in WinMo before booting Android. Do you have any issues in Android getting a GPS lock...?

I didn't think I needed to spell it all out, but try this:

adb shell

su

kill -9 28

You have to be root (superuser, SU) to do pretty much anything destructive.
[Touch HD Android Development] dewasha:
the errors:

init: service setupmodem requires console

init: console requires console

cannot find /system/bin/servicemanager

cannot find /system/bin/vold

cannot find /system/bin/debuggerd

cannot find /system/bin/rild

cannot find /system/bin/app_process

cannot find /system/bin/mediaserver

cannot find /system/bin/dbus-daemon

cannot find /system/bin/installd

and not continue loading android stop here and nothing reply
[Touch HD Android Development] arrrghhh:
Doesn't really help me solve your issue, so I'll take a guess:

Did you follow all the steps in the first post? ts-calibration and rel_path are especially important, please be sure to follow the directions closely.
[Touch HD Android Development] dewasha:
Yes, of course and I always read everything sent the first post,

this is my startup:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2030

set KERNEL zImage

set initrd initrd.gz

set cmdline "rel_path=npkboot lcd.density=240 msmvkeyb_toggle=off msm_blackstone_pad.vibrate=1 gsensor_axis=-2,-1,3 pm.sleep_mode=1"

boot

I put the rom in the folder like the other roms npkboot and that's why I reported in the startup file,

tell me you need to know to help you discover the problem

I have not modified any files in the rom or anything, just added my startup and my ts calibration
[Touch HD Android Development] arrrghhh:
If you have partitions on your SD card, you also need to add "no_partitions" to your cmdline. Perhaps that is your problem...?

It shouldn't matter what folder you put it in, so long as rel_path= matches the folder location.
[Touch HD Android Development] dewasha:
yes i have partitions ext2. i add no_partition and try again.

thanks
[Touch HD Android Development] mikereidis:
FM Radio (real, not streaming):

boran1 has been asking me about getting my FM app running on this device and ROM. (See my sig for app info.)

AFAICT my app works OK on this device, except for the one big problem I've faced on many devices: No Audio.

All I need is the ability to send an IOCtl to /dev/msm_snd to select "FM Speaker" or "FM Headset".. When I query this device I get:

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 0 name: HANDSET

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 1 name: SPEAKER

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 2 name: HEADSET

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 3 name: BT

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 44 name: BT_EC_OFF

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 10 name: HEADSET_AND_SPEAKER

m1_do SND_GET_ENDPOINT ioctl snd_endpoint.id: 256 name: CURRENT

As you can see there are no endpoints for FM.

An alternate method supported on many stock HTC devices allows these to work:

echo fm_headset > /sys/class/htc_accessory/fm/flag

echo fm_speaker > /sys/class/htc_accessory/fm/flag

I imagine kernel driver or libaudio code could be copied from other msm72k devices.

Do you think this might be viable ? Thanks !

EDIT: Sorry, perhaps this was better on the other thread.
[Touch HD Android Development] arrrghhh:
Hey there! I got a PM from probably the same guy about the same topic. Unfortunately, I don't think my device even has an FM radio. I don't have a Blackstone, perhaps those devices do...

I don't know any devs on our project with a Blackstone, but I'll try to poke around and ask. If you have some time, hop on #XDAndroid on Freenode and we can chat about it more - I would like to see if we can get this enabled for our users, and perhaps there are more devices with an FM radio than I'm aware of - I didn't think any of the devices we support have FM radio's, but evidently the Touch HD at least does...

Edit - btw, so long as it pertains to the TouchHD and somehow the XDAndroid build listed here, I don't mind you posting in this thread.
[Touch HD Android Development] dewasha:
arrrrrg thansk for your help, now work perfect, i evaluate the rom :)

congratulations for your work
[Touch HD Android Development] arrrghhh:
Excellent! I'll add that to the caveat list ;).
[Touch HD Android Development] motisu:
Hi Arrrghhh,

I have a RHOD210 and it has an FM radio built in. I use it all the time. Energy28's WM6.5 ROM comes with an FM tuner too. Its only problem is that it needs the headphones attached to be of any use as it uses it for the antenna. If someone could get the radio to work on both the Blackstone and the Rhodium, that would be SUPER!!
[Touch HD Android Development] arrrghhh:
Interesting... I guess I should try it. I have EnergyROM on a RHOD400. I looked, but never saw an FM radio app. I shall look again now!