yashsingh1/xdaforums huggingface dataset:
[Touch HD Android Development] Motik:
Third-party keyboards just work... Only the native one doesn't !
[Touch HD Android Development] arrrghhh:
There you go then...
[Touch HD Android Development] AcidBurns:
correct usage should be:

setprop qemu.sf.lcd_density 240

(without the quotes, according to adb shell output)

did try to set it to 210 and 240, not fixing... keyboard is still about 5mm size at the bottom.

tell me which logs you need!

\\edit:

I also tried the "reboot on missed call" error. the following issue is the problem:

when you have a wake up from the call, you just miss it by a second and then press any key or touchscreen the phone crashes. probably the wake up routine isn completed for "wakeup on incoming call" so that the touchscreen isn't ready... the phone just hangs for a few seconds with "missed call from blblabla" in the top line and then restarts.

Nevertheless, very good android port! runs flawlessly with a sandisk sd card.

greetings from germany!

Acid
[Touch HD Android Development] arrrghhh:
So for the keyboard, it seems the easiest fix is 'hacker keyboard' on the Market.

As for the call issue, definitely will need logs for that. You'll probably need to setup continuous logs too, and try to recreate the issue...

http://xdandroid.com/wiki/Logs
[Touch HD Android Development] AcidBurns:
Okay, I'll do the testing after some hours of sleep.

today was speed kernel day, I testes V12 with this release.

Runs somewhat faster, boot is good, everything else still works.

I attached the kernel and startup. Just copy everything to sdcard/V12

Add your system.ext2, rootfs.img, data.img and AndroidApps directory and boot.

\edit: removed, sorry guys too much straction from testing build.

Have fun!

-Acid
[Touch HD Android Development] arrrghhh:
Source...? Where did you get this from? WTH is V12?
[Touch HD Android Development] viktorandreev:
Hello, why I can not see video? Only gives me sound and black screen.I appearing when the program continues with the sound.Solution?
[Touch HD Android Development] AcidBurns:
neopeek[dot]com/viewtopic.php?f=70&t=7650 this is the source.

V12 is the name of the kernel.

kernel sources can be found here: gitorious[dot]org/~helicopter88/linux-on-qualcomm-s-msm/ext3-kernel

I also made a new startup txt. is attached to the post. battery is 80% after 4h standby.

to prevent the overclocking from "going to sleep" (setting to 128mhz while asleep) put pm.sleep_mode=3

greets from germany,

acid

\edit: may not post outside links -.-'

\edit2: attachment removed, too much distraction from main topic!!! TEST THE BUILD AS IS!
[Touch HD Android Development] arrrghhh:
Hrm... Video codecs *should* be up to snuff, but there still might be some videos that won't play.

What are you trying to play? Youtube HQ?? That should work, but again, there's probably some video resolutions that are just too much for this device. IIRC, hyc was able to get the binaries to pump up to 640x480, but was never able to get up to the 800x480 (er 400?) that our native resolutions are capable of...

I think he felt it was a hardware limitation. Whether it is or not, Android will probably never be on the same level as WinMo in the decoding high quality video area....

Ah, yea that stuff probably won't run on RHOD. Thanks tho.
[Touch HD Android Development] AcidBurns:
actually it should run on RHOD.

you just have to use the "blank" startup here: pastebin[dot]com/wkAnmWht

keyboard is rhod100

density is still 240

mtype is 2292

greets,

acid
[Touch HD Android Development] viktorandreev:
Thanks arrrghhh for the response.Definitely this is the best XDAndroid for Blackstone.Stable, fast, good sound.But with karnel of AcidBurns is much better.Thanks guys for the posts.Oh, and no partitions YESSSS!!!
[Touch HD Android Development] AcidBurns:
okay, I somehow couldn't recreate the reboot error. dunno what happend but apperently it solves itself with either V12 kernel or using the phone for a few days.

is there any way to get this version to use the ext3 partitions on the sdcard? I tried copying over the content from system.img etc pp to the parititions and booting with an recovery image instead of rootfs but this doesn't work out.... :(

Any hints on how to "compile" this build to be installed as update.zip with recovery?
[Touch HD Android Development] arrrghhh:
Any XDAndroid build can run on partitions. It's not easy to setup, nor is it a supported configuration - so you won't see any guides on it, we don't want a bunch of people doing it - support is much easier that way.

I can't really support kernels that aren't distributed by me... sorry, you are on your own there as well!
[Touch HD Android Development] AcidBurns:
okay, so i'll try myself and won't post anything about how to run this stuff on partitions ;)

to my mind the kernel doesn't really need support, runs like charm :) (at least on my blackstone)

greets,

acid

p.s. actually: why is this build a testing build?! it's by far the most stable gingerbread rls I know...
[Touch HD Android Development] arrrghhh:
Mainly because there were A LOT of changes from our last GB release, and we wanted to ensure no devices were left behind.

I think we're close to a full release. I'm working on hopefully the last test release.

We also wanted to sort out the whole CSV thing, so users wouldn't have to do that manually. I don't think much traction has happened there yet :p.
[Touch HD Android Development] AcidBurns:
okay, I guess you'll let us know when the final release is ready...

than i'm (eventually if my blackstone lasts) gonna start doing my partiton recovery boot stuff.
[Touch HD Android Development] arrrghhh:
You don't even need recovery. Our rootfs supports partitions...

Good luck.
[Touch HD Android Development] krzych:
After copying files from zip into root (!) of the SD card (when copied with folder which is inside GBX - kernel does not find the root partition), kernel boots and runs fsck. Fsck then finds a load of errors on root partition, automatically fixes them and after that, I can see nice kernel panic or something like this. Funny thing is that touchpad calibration _still_works_, so I can touch few times, then it ends and all phone life ends too. Only vibrations are alive when i touch the screen ;P

Anyone can tell me what I did wrong?

After copying all with overwrite again I have a result like on screenshot.

How is this even possible to have "unclean" status of at least two system partition images while installing a fresh rom?

[edit]

I suppose I know now what happened - kernel detected on my sd other root from different rom. Should change labels first.

[/edit][edit]

I was wrong, solution is even worse - this rom cannot be installed on other partition than FIRST. It has to be mmcblk0p1 !

You really should mention this. I've lost an hour to get it booting...

[/edit][edit]

Settings->Applications->Storage use, here, click third tab. It will run and immediately collapse (die) back to "applications". Then if you click anything, it will die too, but if you then click "Development", phone freezes. Only vibration still works while pressing "back" or "hangup". Battery removal is the only choice.

And I just wanted to check the size of the /data partition to know how much apps can be installed, so simple...

[/edit]
[Touch HD Android Development] AcidBurns:
you could have asked about the data size.

it's 256mb by default, but you can used almost any linux distribution to increase it to a number you want (<4gb because of FATsystem).

to your boot problem:

obviously your sdcard has some ext2 partitions on it. you have to add no_partitions to your startup.txt into the set cmdline " ... " argument.

and I don't think you have to mention that the partition has to be 1st, cause this is on EVERY build that uses *.img virtual storages for the files.
[Touch HD Android Development] viktorandreev:
I really like this build.But problem is that I can not see video.I tried with lower resolution(320*240) but still the same, no video only sound.When I stop the video "forced closed",and sound continues until I restart.
[Touch HD Android Development] krzych:
Hmm, thank you. I'll have to check if 256 will be enough. Is there any guide how to expand this partition?

But I'm a "first timer" - I have Touch HD quite long, but I started to androidify it a lil while ago when I bought Desire HD. I already even forgot how Touch HD looks ;P. And my first try was Neopeek's distro which is set up on real partitions, so I never had contact with images. And I do not know how haret works yet. SHouldn't this "no_partitions" parameter be already in statrup.txt since we all will be using images?

Thanks for the answers. What about settings problem, do you have it too or is it only mine?

Hmm, and I have to export my DHD's keyboard because I cannot type WiFi password, and have no connection by mobile - my provider does not allow it on this SIM (and I have no other SIM right now).
[Touch HD Android Development] AcidBurns:
hey there!

The resizing is pretty easy if you run linux. you have to connect your mircosd card somehow to your computer (for example by booting windows mobile and connecting it via "data storage" option, NOT using active sync)

after that you can use those commands:

preshweb[dot]co[dot]uk/2010/04/resizing-ext23-filesystem-in-loop-file/

open a terminal and use cd /media/*your sdcard name* to go to your sdcard.

and keep in mind that disk.img in your case is data.img.

for the record: I'm not responsible if you brick your ext2 system! It worked for my, but having a backup can't be wrong ;)

I don't have any problems with this android rls, video is good and all settings are well choosen for speed and stability.

I suggest you just delete the old partitions on your sdcard and check your FAT file systen.

-

acid
[Touch HD Android Development] krzych:
There is one BIG problem. The "red" phone key (a disconnect key) functions _exactly_ the same as "power key", but there is no "home" key which is _a_must_ as there is no "tab" functionality (task swicthing) at all.

I can't swicth to another activity in any normal way, I have to exit them one by one to get to the bottom. This is really annoying.

Thank you for all your answers, but this cannot be done until I figure out all the possible issues - this phone will be for my girlfriend and if this release won't work, I'll prefer to leave the old one (neopeek's) which is slow, but I can try to speed it up if I won't set up this one (which I would really prefer to).

PS. I have no characters on hacker's keyboard. Keyboard itself functions well, displays "tips" while pressing keys, but there are no chars on the keys befere you press them - like missing font or something

PS2. Anyone can publish his calibration file? I could not manage to set it up properly, don't know where to click while calibrationg, because it works this way

PS3.

Hmm, but where is this data.img? I have only system.ext2 and rootfs.img, no data.img nowhere...?

Something is very wrong at my setup - im checking for hardware problems (faulty SD) - checked - no, it's not the card. Changing SD does nothing, still no fonts on keyboard, no home key

After pressing "search" icon in market, nothing happens... how to search without it?

After connecting to notebook's USB, there is no USB wizard which can allow to choose USB mode
[Touch HD Android Development] krzych:
Ok, I already know I would like to have it working - it's best system compilation I've seen so far (for example, it has Kexec - reboot without messing with the winmo - very convenient) but, it has at least two bugs that i would like to be fixed.

- Lack of "home" key, can't live without this

- USB communication could be fixed, we can live without it, but it is really worse life

Rest seems to "stabilise" while using - for example - "search" in Market just started working without any real reason - maybe "go keyboard" did it (with hacker's keys it won't work).

The only thing I would check next, the partitions - will it run faster on real ext3 partitions?

Trying Acid's kernel.
[Touch HD Android Development] AcidBurns:
okay, i think the only real problem you have is installing a testing build without any preknowledge.

the key mapping can be adjusted using the startup.txt: physkeyboard=blac100

than end key should be menu, back key is back key, home key is home key and answer key get you to the telephone thing.

BUT: IF YOU HAVE NO DATA.IMG SOMETHING WITH THE BOOTING PROCESS IS NOT RIGHT!!!! it should be created on first boot.

Do you have enough space left on your sdcard?

to answer the partition question:

THEORETICALLY is SHOULD be faster on partitions, just because the data hasn't go to 2 file systems (virtual ext2 and fat on sdcard)...

I suggest you get your girlfriend a cheap android phone like htc wildfire. for productive use the neopeek builds are to slow, xdadroid is a little bit faster but still not suitable for a demanding girl...

greets,

acid
[Touch HD Android Development] krzych:
Yep. And I could not find it anywhere to be honest... I barely found the two distros - neopeek's and this one.

You're my hero now, you know? :) This means I'm staying on this distro.

I know, I resigned right now from messing with data.img, but as I changed my SD, it's now a different story. Maybe this time data.img will be in place as I've seen while boot that it was created. Now I cannot access SD because I'm booted to xdandroid and USB is not working, but as soon as I boot windows, I'll check this one and report.

Can't be done. The point is that we have two phones too old to sell (N95 and Touch HD) for a normal price, and too weak to use - I mean the features - both has too old system architecture while quite nice possibilities. So, as we have not much money, we decided to convert THD into Android one to get used to android. I will last a year, no more, the we will buy a real based one or maybe even something like Tizen ;P (song of the future ;P). And no, she's not so demanding - she uses phone mainly to make calls, but since android is so nice, we'll try to get her used to other things too. Symbian was too crappy to use it as a smart-one, WinMo has all software paid so there's not much choice, but android is much better and it's probably a final target for us now. And messing with such test bases is teaching me about this platform much - this is an advantage too.

Thanks for your efforts, you seem to be very helpful and smart guy :).

PS. Still on old kernel, but next along with data.img report I'll tell you what I think about new one. - data.img in place, changing kernel

PS2. Is there any particular reason why package manager displays "install/cancel" dialog while restoring apps from titanium? is it part of the Google's new system (2.3.7) bad decisions or something else?
[Touch HD Android Development] AcidBurns:
the install cancle dialog is a security function.

i think you can avoid this by using titanium backup PRO(!)...

the keymapping advice for startup.txt should work with any other distro as well... this is the kind of "preknowledge" i talked about ;)

you can also browse sdcard with any normal explorer from android market. sdcard should be mounted in /sdcard

hope everything is in place now...

greets from germany,

Acid
[Touch HD Android Development] krzych:
Never had this issue with "free" one before. But if you say so...

Yup, now I know. I even looked at Neopeek's - he has "blac" instead of blac100 - i will test the difference.

Yeah, but I talked about browsing from a PC. From Android itself the best so far was total commander's beta ;).

Yeah, almost. Only USB connection is still not working. Dunno about sound, not tested yet, video needs test too, but I won't use it much I think.

Been there few times - nice people, nice views. Even wondered I could learn the language to be more frequent guest, but it's harder than english ;) Have no time right now ;) But I will visit you more ;P :D

PS. About neopeeks params:

hw3d.force=1 - should we use this or not?

acpuclock.force_turbo=1 - or this one?

snd.force_headset=2 - I suppose this distro has sound done better than this, but what was this for or maybe we should use it too?

PS2. Erm, just looked into your startup.txt (for V12) - I think I will use it but ommit only one param - msmsdcc_fmax=14000000 - since I have no problems with SD right now - what is this param for? - LOL! That was a bad idea - kernel didn't find the SD card, heheheh, ok, I'm applying all params :D - and it just andwered about my rel_path question.

But still - where should be placed those *.csv files - in V12 or the root dir? Or maybe in this kernel it is not needed at all?

Home still does not work on your startup.txt - I'll try "blac" instead. - yep, this keyboard is perfect - only "hangup" is now "menu" - rest is ok according to icons

Kexec is not working with V12 kernel - i think we have to find a config for this one - it is probably command line for haret or kernel itself and it does not see the V12 dir or maybe even more than this (kernel params?)

Strange, every time I boot the system, it says partition wasn't cleanly unmounted, checks it and then sometimes founds something... Not sure taht with original kernel it's still an issue, but I'll check this

V12 kernel from AcidBurns is definitely faster. Kexec does not work with this kernel even when all is placed at root of SD.

A very sad news is that Neopeek's distro is WAY faster even with its old kernel. I tested it on call responsiveness - when you call the phone with GBX, you have to wait few (at least four) signals to phone rings, in Neopeek's gingerbread it takes only ONE (even when phone is in a sleep). In GBX when phone sleeps it can take up to 6 or seven signals to ring at all!

It's a very bad news for me as it's not acceptable to have a phone which does not ring, or rings only two, three signals lenght because then, operator disconnects the call saying "recipient does not answer the call, try again later"...

By the way, Neopeek's distro is loaded with apps running in bg, GBX is not. Maybe the difference is based on native ext3 partition, maybe not. I didn't have a time to try yet. So much for tests today, next try in a week or so...

PS. Testing on the same phone, same data, only GBX has less apps running in bg and it's own kernel or even faster V12. Now I'm going to test V12 + Neopeek's.
[Touch HD Android Development] arrrghhh:
This is in the third caveat post. This isn't private information, lookin at you krzych... Please READ!

The free version of TB is a pain to restore. It's a breeze to backup, but the free one prompts you with every app restore.

If you looked at that caveat post, you'd see that it's blac not blac100.

Use adb. If you're on Windows, Droid Explorer does a good job of 'faking' USB mass storage mode.

USB works great, see above. Read the FAQ please. You jumped straight to a TESTING build, bravo.

These are all deprecated, except maybe force_turbo. I think that's something that's Blackstone specific, and I cannot confirm myself - sorry, I only have a RHOD.

That's for SD card speed. Please search... Jeebus.

V12? I can't support this kernel, assuming you're only using this kernel... AFAIK that "comes with" a lot of other stuff. My stuff goes at the root of the SD.

Again, can't support this. I think kexec only works on .35+, and that doesn't work on Blackstones AFAIK. See above about the devices I own :rolleyes:.

That is normal. It can't be properly unmounted on shutdown.

Dude, can't support this. Also, who is it from? Holy hell.

Use what works best for you... No one is forcing you to use this.

You can put this build on dedicated partitions if you wish, our rootfs supports it. This is neither supported nor condoned... So you'd be on your own when doing this (which sounds like you already are...)

Please, if you're just going to be disrespectful go elsewhere.
[Touch HD Android Development] AcidBurns:
hey, arrrghhh ... calm down a little bit ...

I already told him he is in a TESTING BUILD topic ;)

It probably is the best to just stay with the neopeek build and come back in 2 month for getting a tested build of xdadroid.

the force turbo is still active in use and enables overclocking to abnormal steppings or something, but only for turbo kernels (such as v12 ;))

greets,

acid
[Touch HD Android Development] krzych:
Sorry, found your distro by accident with google. Could not find anything related - if I could find a FAQ, be sure, I would read it. You can see how much problems I encountered while trying to do it without a FAQ - I'm not that stupid to ommit it, I just couldn't find anything related. Yep, maybe I'm not google familiar enough, but didn't wanted to do a mess here (and I'm trying to set um Android already a month on THD, I thought I've googled everything)

Yes, your FAQ says everything about USB. Sorry for talking about FAQ. But adb is no USB substitute. It does not expose disks, it just serves files (push/pull) and droid explorer does adb push/pull. It is really slow. The much better way if you want to advise a substitute is Samba filesharing (smb server) - it can be much faster when much little files are to be copied and it is wire-less. Only thing the adb is good for is shell/logcat/etc or sometimes install.

I think not. But I'm not sure. There has to be a difference which causes Neopeek's distro faster. And I said before - I prefer yours, but can't do anything about it being faster right now.

[edit]Correction - I need to read FAQ more[/edit]

AcidBurns uses this kernel too. And he says it's faster too. A pity you cannot support similar (it does not have to be this one).

It would be nice to have faster kernel with this feature. It's really good one.

Ok, this is one more argument to move your distro on the real ext3.

Nobody expects you to support this. I just stated there is a way to speed up your distro, nothing more.

I definitely will do this, and definitely do not expect any support. I just want to speed it up and will not complain about real partitions problems, be sure about this.

Hmm, I don't know what is wrong about my way of writing, but surely it can be improved. But be sure, I want just to test your distro as the topic states, to point out what I found and to contribute as much as I can to make it released a best available one for THD. Yes, I started badly (with no knowledge), but I'll improove.

For now, sorry for bothering you, everything I asked about was answered by AcidBurns until the last post. Maybe I should ask him by PM, but thought it will help other testers too if they are not experienced as me.

I really do not know how to behave in such situations, asking gets me in the trouble like this, not asking causes I can't manage by myself :/

Yes, that seems to be better solution...

Sorry guys.