yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] indianneel:
hey so just a few graphical things that i noticed, the dialer skin is a little off-placed, and wow this thing is fast. i cant wait for it to be fully working with audio! =) thanks dzo
[Touch CDMA Android Development] grktaurus83:
Was hoping to give this a peek., but it looks like sourceforge is down right now. *sigh*
[Touch CDMA Android Development] hexto:
That's amazing. I'm using an Incredible now but still follow the Vogue since I used it for 26mo. I miss the Vogue community and devs.
[Touch CDMA Android Development] drkow19:
It booted first time for me, only took 5 minutes install and everything. SD card wasn't recognized for me either. I'm sure when that's working a lot of other problems will go away. I couldn't load any apps to test performance because no Astro and no data, but I'm sure I could install Astro with adb or a androidupdate.tar no? Anyway good work dzo!
[Touch CDMA Android Development] vilord:
I miss this community too :( I've made the same jump as you, used Vogue for 25mo

-Jesse
[Touch CDMA Android Development] loserskater:
I thought I just read somewhere, but I can't seem to find it, that if a build is odexed than JIT can't happen. So it's basically one or the other.
[Touch CDMA Android Development] *M*:
CPU benches dont seem to change wether its odex'd or not so I dunno about that.
[Touch CDMA Android Development] dzo:
All you need to do is:

git push ssh://username,androidhtc@androidhtc.git.sourceforge.net/gitroot/androidhtc/reponame.git

e.g.

git push ssh://msmission,androidhtc@androidhtc.git.sourceforge.net/gitroot/androidhtc/device-vogue.git

Thanks again for your help.
[Touch CDMA Android Development] dzo:
Not true, there is no reason why an odexed build would be any faster or slower than a non odexed build. Probably the reason why it seems faster is that for the most recent build I took out lots of languages and without all these translations there are more apps that can be kept in memory at the same time.
[Touch CDMA Android Development] minir4:
USB Tethering

hey so does this support usb tethering on the vogue? i cant seem to find the option anywhere but thought it was supposed to be in froyo... please, any help is greatly appreciated
[Touch CDMA Android Development] Kot_Ik:
I understand that english is international language, but can you put languages back? So pity that your builds are left without national support...
[Touch CDMA Android Development] imfloflo:
@dzo have you tried to contact @cyanogen to work together ?to make a CM6.0 version for us ?and sync the git ?
[Touch CDMA Android Development] kallt_kaffe:
Still it is, at least for Eclair and Donut. Just odexing the framework makes an noticable difference.

I've googled a little and odex stands for Optimized DEX and odexing means the dex files are optimized for the specific hardware platform it runs on. (Source: http://mylifewithandroid.blogspot.com/2009/02/optimized-dex-files.html )

Maybe this is also done dynamicly when files end up in the dalvik cache. In that case an odexed and a non odexed system should perform more or less identical, at least when all the apps have ended up in the dalvik cache. The non-odexed may get a little more overhead needing to check that the cache has the latest (optimized?) dex files. But what if the dex files in the cache are not optimized, then the only performance gain that the cache gives us is that it doesn't need to extract the dex from the apk on each start of the application.

Now, if the odex files are in fact optimized dex files we should expect a perfomance gain from odexing. And everyone who have tried your odexed Donut knows that it's a fast build. VaniljEclair is also rather fast (for being an Eclair build) and also vilords old Tattoo build is odexed unless I'm mistaken.

Now if my speculation above is correct, then what about JIT? Now, what if JIT in Froyo means that the dex files in the dalvikcache is not only extracted but also optimized for your hardware? In that case we wouldn't see any noticable difference between odexed and non-odexed builds. It could even be possible that the dexopt-wrapper we use for odexing isn't as effective as the JIT optimization that ends up in the dalvik cache. In that case we would even get worse performance by odexing.

Now, this is just speculations and I may be totally wrong but I know that when odexing an Eclair build I notice the difference after having odexed it and unless I remember it wrong I didn't notice much or any difference at all when I odex:ed the first Froyo builds.

I also read that Incubus got better linpack score with the non-odexed build and I don't think removing languages should affect benchmarks.
[Touch CDMA Android Development] -Arturo-:
Hi Dzo. Could you please, attach the removed language files to the first post and provide a short tutorial on how to put them back to androidinstall?
[Touch CDMA Android Development] dzo:
Taking out the languages makes a big difference on our devices, each app has translations and the icudata for the full languages is twice the size. I'd actually like to take out even more languages.

I'm currently building with only english and spanish to see if that makes much difference. I think what we should do is make 3 builds, english and spanish only, european languages and all languages. That way you could get a speedy build if you only need english.
[Touch CDMA Android Development] dzo:
It's not that simple, you have to build the whole system since the translations are in the apks.
[Touch CDMA Android Development] minir4:
usb tethering

hey again, i made a ppst a few posts ago and no one seemed to answer my question and would really like some help with this... does anyone know if usb tethering is in this release and how do i access it? is it expected? the first post on this threat has nothing under the section that says "not working" so i am to assume it is in working... any help?
[Touch CDMA Android Development] scooter1556:
I think this is a great idea!!! That's the idea of vanilla at the end of the day, only having installed what is really necessary. I guess it's just the pain of having to maintain and compile numerous builds for each language, takes a lot of time!!!
[Touch CDMA Android Development] blindguyinanorgy:
this is the impression i got when i looked up JIT after myn posted it for his eclair (or donut i cant remember).

this was before odexing and it did make everything faster. but for me myns was never stable enough and was worse with JIT. now that JIT is native to this version i think its worth giving a significant look into non odex.

i wonder if specific applications benifit more from ODEX and some benifit more from JIT.
[Touch CDMA Android Development] blindguyinanorgy:
I agree, and lucky for me i speak the same language as the developer :D
[Touch CDMA Android Development] mssmison:
the main difference right now is just the space left on /data, and boot time. I've tested both ways a the speeds are very similar when the system is up and running.
[Touch CDMA Android Development] incubus26jc:
yes and my linpack increase i think was do to the FRF91 System and not because it was a non odexed build. The fact that the non odexed build seems more snappy is probably just plecebo.
[Touch CDMA Android Development] kallt_kaffe:
I've installed the non odexed build and installed all the things I usually installs then I ran Neocore twice.

I then odexed everything, framework, system apps and market apps and ran it again. My fps where identical but I now have much more space left on data. Overall the system performance about the same or perhaps even a bit snappier after odexing but that may be placebo.
[Touch CDMA Android Development] loserskater:
I'm not saying it would be faster or slower. I was just saying that from my understanding, you couldn't use JIT if a build was odexed. So you either have an unodexed build with JIT or an odexed build without.
[Touch CDMA Android Development] KeRmiT80:
i think i've been the first to download it (yesterday the counter was 0) :D

personally i'm using with polaris (nand) i don't see big performance difference...sure more space occupied in data but till now is not a problem. :)

but without odex files is easier to apply or create themes (the original services.jar is not patched for transparency) and even if there are tool like xultimate to deodex everything not all the apks and jars are always rebuilt correctly...

thanks to your scripts everyone can run later and odex everything...so unodexed version is REALLY APPRECIATED!

have to say that i wouldn't believe that one day i've could run android this way in my old pola100...your work is really A-W-E-S-O-M-E! :D
[Touch CDMA Android Development] dzo:
I see something that might be the problem, I've been using google's odexing tool (dexpreopt) and it looks like it doesn't zipalign the apk after taking out classes.dex. I don't know what difference this would make but I'll make a zipaligned build for people to test.
[Touch CDMA Android Development] incubus26jc:
thanks man, maybe a non odexed version as well?
[Touch CDMA Android Development] *M*:
http://mylifewithandroid.blogspot.com/2009/02/optimized-dex-files.html
[Touch CDMA Android Development] dzo:
Here's another system:

https://sourceforge.net/projects/androidhtc/files/system-froyo-05-07-10_16.tgz/download

This is english only, odexed and zipaligned. It includes working speech input for the kbd.

I've also managed to find 11M of extra memory in the kernel. If you use this with the latest NBH from my site it should be a bit faster.

http://it029000.massey.ac.nz/vogue/files/voguimg-240x320-froyo-05-07-10.nbh
[Touch CDMA Android Development] SuperJMN:
Wooohooh! I will donate to you as soon as I receive my salary!
[Touch CDMA Android Development] lunigma:
Amazing. I can confirm, exactly 11Ms extra
[Touch CDMA Android Development] ebautista:
Cool. Do you have available latest kernel for Kaiser? :D You are the best man!
[Touch CDMA Android Development] uncynd:
Using this but my wifi won't turn on, it returns "error"
[Touch CDMA Android Development] TheKartus:
is there a zImage with the extra memory?
[Touch CDMA Android Development] incubus26jc:
nice work man. An unodexed build would be fantastic so I could theme it. Thanks again man.
[Touch CDMA Android Development] kallt_kaffe:
11Mb should make a noticable difference but it's only for the Vogue, right? Is this a change that would work on Kaisers and Polaris aswell?
[Touch CDMA Android Development] incubus26jc:
im getting force close on camera with new nbh.
[Touch CDMA Android Development] pardonmyownage:
kaiser and polaris would be nice to have... unless this one works for those also. im guessing not
[Touch CDMA Android Development] kallt_kaffe:
The file works after putting it through NBH editor but it doesn't matter because the changes are only done for Vogue devices. I'll see what happens if I do the same changes for the Kaiser.
[Touch CDMA Android Development] pardonmyownage:
thanks...

btw you guys are awesome... kinda sad that i cant find a froyo release as stable as this even for the Evo 4g. Glad we have you guys on our side! (dzo, incubus, kallt_kaffe)
[Touch CDMA Android Development] Naemion:
Neither does bluetooth
[Touch CDMA Android Development] grktaurus83:
Where'd the 11mb come from?

And is this Froyo/Eclair specific or does it apply to Donut as well?
[Touch CDMA Android Development] n2rjt:
Perhaps the "English Only" diet was a bit too extreme... In the weather widget it shows a box instead of the degree symbol.
[Touch CDMA Android Development] kallt_kaffe:
I noticed that too. Not the stock weather app though, but the widget from here does indeed display an ugly box now: http://www.ermesjo.org/blog/?page_id=66
[Touch CDMA Android Development] dzo:
I've just put an unodexed system on sourceforge.
[Touch CDMA Android Development] jin5:
i'm getting the same problem
[Touch CDMA Android Development] iseeka:
would be nice if someone compare performance diffs now again
[Touch CDMA Android Development] scooter1556:
I have to say, this odexed build with languages stripped is certainly a lot faster!! Hopefully the kaiser kernel can also be tweaked to gain the extra space.
[Touch CDMA Android Development] dzo:
You need /system/libcamera.so from my latest build to stop this. The 11M comes from the platform memory, with donut I was allocating 8M for the 2d graphics cache and 8M for the adsp cache. For donut, these were handled by proprietary libs so couldn't easily be changed. For froyo, the new gralloc lib checks the size of pmem and I used /dev/pmem_camera rather than /dev/pmem_adsp for the camera library. All we need now is 1M for pmem_adsp (for colour conversion and camera preview) and 4M for pmem (since our display is smaller than other devices).

Two new kernel params let you specify the size of the pmem areas.
[Touch CDMA Android Development] kallt_kaffe:
I didn't see any difference on the Kaiser. I suppose it should show then typing "free" at the command prompt?

I also tried to put the changes into board-htckaiser.c but got scared off by this part of the code:

mi->nr_banks=2;
mi->bank[0].start = 0x10000000;
mi->bank[0].node = 0;
mi->bank[0].size = 0x03800000;
mi->bank[1].start = 0x14000000;
mi->bank[1].node = 0;
mi->bank[1].size = 0x02800000;

Didn't dare to touch that so I dropped it and did a modification to the keypad code instead that I had been planning to try for some time.
[Touch CDMA Android Development] djmattm:
I just updated with lat kernel and froyo and it's quite better, the job you're doing here is stunning, it's almost perfectly stable, just few stutterings here and there
[Touch CDMA Android Development] dzo:
You should be able to increase the bank 1 size to 0x03300000 with pmem of 4M at 0x17400000 and pmem_adsp of 1M at 0x17300000. Don't try using the kernel parameters to work out the bak size, i tried that and they aren't available that early in the boot.
[Touch CDMA Android Development] kallt_kaffe:
Ok, I'll give it another try then. Btw, is libspeech really supposed to go in /system/app/lib?
[Touch CDMA Android Development] kallt_kaffe:
Works!

Attached an NBH. Although it says "ECLAIR" in the name I suppose this one is Froyo only and DO NOT use anything other than a hexeditor to change panel type etc...

Not sure if I should push this change or not. It will propably break backward compability so we need a strategy for this.

btw, this one also has landscape/portrait flip on the mail button. :)

EDIT: Added the zImage aswell. Important! Add "board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1" to your parameters or things will go bad.
[Touch CDMA Android Development] kallt_kaffe:
Did the same changes for Polairs, no idea if it works though.

HaRET users adds "board_htcpolaris.pmem_size=4 board_htcpolairs.pmem_adsp_size=1" or they will be swallowed by a black hole.
[Touch CDMA Android Development] djmattm:
I'm sorry for the crossposting but i've to tell that tis kernel is amazing, 48mb of free ram and camera working!
[Touch CDMA Android Development] flinx42:
Are you saying that Loser's NBH Editor v3.4

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

won't work for this NBH?

According to his change-log version 3.4 supports Froyo..
[Touch CDMA Android Development] scooter1556:
I'm guessing there are some significant changes/restructuring of the kernel which will be messed up by NBH editor until an update arises??
[Touch CDMA Android Development] incubus26jc:
Thanks for the info.
[Touch CDMA Android Development] kallt_kaffe:
There are kernelparamaters (use a hexeditor to see them) that will likely be messed up if you use the NBH editor. If they are removed then the memory areas that is supposed to cover 5Mb will use 16Mb but the extra 11Mb will still be allocated to the system and as I said, bad things will happen.

Consider these builds experimental. We need a strategy on how to move on from here. We may need to compile separate kernels for Donut/Eclair and Froyo. If understand it correctly we can adjust Eclair (changes in camera lib?) to work with these changes but Donut I understand will not.

I don't know the details but dzo does so he may have a better idea on how we handle this. As I understand we can't use the kernel parameters for this on Kaiser/Polaris but I may be wrong.
[Touch CDMA Android Development] warttack:
Hi dzo, kk, incubus. First of all thanks for the great work on android for vogue, its really appreciated. I know my question is not the most important but its something that is bugging me on 2.2, the keyboard. Is there a way i could change the new froyo black and silver keyboard with the old basic black keyboard from eclair? i've being looking around for it and i did even changed the LatinIME.apk and it didnt help. Thanks in advance, and hope to read from you soon.

img1.imagebanana.com/img/bbjc9dio/old.jpg
[Touch CDMA Android Development] kallt_kaffe:
Push and hold any text input area. Choose input method. Choose "Android keyboard".
[Touch CDMA Android Development] scooter1556:
You are right, NBH editor removes these parameters, i just checked in hex editor. Impressive increase in available RAM, will make a huge difference on these relatively low RAM devices. I like the mail button orientation switch too, nice touch.
[Touch CDMA Android Development] warttack:
thanks kk for the fast response. im using the latest release of dzo system-froyo-05-07-10_16.tgz and the only option i have on the "select input method" popup is "Touch Input". :(
[Touch CDMA Android Development] loserskater:
I'll start working on an update tonight.
[Touch CDMA Android Development] dadevil666:
downloaded kk's newest froyo zImage for the kaiser added the paramaters to default.txt(atleast i think this is where they are supposed to be) installed latest fresh froyo and i get a black screen tried 2 times and still hangin on the black screen anyone have any idea why it's like that :confused: btw here's how i added the paramaters

set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0 board-htckaiser.panel_type=2

boot board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1"

Edit: found problem fixed it...
[Touch CDMA Android Development] flinx42:
WOW

You lot (loserskater, dzo, kalt_kaffe) are just too bloody fast!

Everyday I read the forum and think: Shall I have a go installing the latest build or wait half a day until whatever minor problem is fixed as well..

:)

I'm not afraid of using a Hex Editor, but if I'm about to be spoon fed by looserskater I can wait that extra day. ;)
[Touch CDMA Android Development] incubus26jc:
im still getting force close on voice keyboard. Do i need to move libspeech?
[Touch CDMA Android Development] kallt_kaffe:
Yes that should do the trick.
[Touch CDMA Android Development] incubus26jc:
it did thanks
[Touch CDMA Android Development] mnjm9b:
I tried the new froyo kernel and it does seem faster with new dzo system. even on sd partition.

although, until copilot updates to froyo I need to dual boot with the eclair I have in nand.

eclair seemed faster too with new kernel but...

as already noted, the camera fc.

I tried to patch libcamera.so from the new froyo build but that still fc

I am sure that is because it is made for froyo and not eclair.

for now I revert to eclair nbh.

is there any other way to keep the froyo nbh and fix camera in eclair?
[Touch CDMA Android Development] plemen:
Wow - just phenomenal! This is the most responsive I've ever seen the vogue - with Winmo or Android.

BTW I'm not sure if it's a known issue but capturing video with the camera app fc's.
[Touch CDMA Android Development] mnjm9b:
yes it is...
[Touch CDMA Android Development] mssmison:
Has anyone else been experiencing lockups with the libgps.so? Seems to work about 5 minutes or so, then the driver just freezes up.
[Touch CDMA Android Development] kallt_kaffe:
No, if anything the gps runs even better in Froyo. But I'm on Kaiser and our kernel gps code is different. But try removing the sensor file from /system/lib/hw to see if it makes a difference. Some gps apps uses the compass sensor.
[Touch CDMA Android Development] warttack:
anyone knows how can i get android keyboard as input method for latest dzo release? on my htc vogue i just have "touch input" as input method. thank you guys!
[Touch CDMA Android Development] gnezim:
I've checked out it029000.massey.ac.nz/vogue/files/ and didn't find any fresh build for polaimg-panel1 (the last one was at 24-May-2010) Is there any possibility or chance that you (kk or dzo) find some time and publish a new one?

In case that you don't have enough time or don't want, please give a direction along xda forum just to try it by myself (build the kernel).

Great thanks for your work and efforts.

oops, found xdaforums.com/showpost.php?p=7069205&postcount=232
[Touch CDMA Android Development] mssmison:
I'm currently testing some updates to the audio libs I did this morning. It should improve input quite a bit. Once I've confirmed everything working I'll post an update.

**EDIT**

Here is an androidupdate.tar with the updated audio libs.

This should make the voice keyboard more accurate. I'll push my changes to the git later today.
[Touch CDMA Android Development] tatnai:
trying to get voice keyboard functioning on my vogue, 5/7 release, new 5/7 .nbh from incubus' thread. mssmision update is applied. FC on using voice function on keyboard. where do I move libspeech from/to, or is that just for polaris?
[Touch CDMA Android Development] Fasst1:
Is there anyway to get my phone to recognize my sd card? I use sd-split to access it from computer but my phone doesn't seem to see it
[Touch CDMA Android Development] pardonmyownage:
reports in incubus's forum that it is not working... black screen before boot animation
[Touch CDMA Android Development] vanderaatje:
Indeed just installed the polaris NBH from KK and I'm now looking at a black screen

I've a POLA100
[Touch CDMA Android Development] waterpolo:
With HaRET and your zImage i get only a black screen.

I added the recommended parameters in the default.txt

Have anyone this working or do we have to use the DZO zImage?
[Touch CDMA Android Development] ParMaster:
I'm getting force closes on camera also...

(running from an sdcard ext2 partition)
[Touch CDMA Android Development] incubus26jc:
the new nbh only works with the latest system. camera works after that.
[Touch CDMA Android Development] ParMaster:
I'm not running an nbh. I'm running using haret and ext2 partitions on an sdcard. Also i downloaded and installed DZO's latest system "system-froyo-05-07-10_16.tgz"
[Touch CDMA Android Development] Naemion:
Have we gotten BT figured out yet? I am still getting rejected by my headset when trying to pair.
[Touch CDMA Android Development] gnezim:
Installed to rom - just black screen and nothing more.
[Touch CDMA Android Development] Badgerfan:
Same :( Pola 200
[Touch CDMA Android Development] Murrky:
Guys, as a temporary solution for Pola100, you can use this image.
[Touch CDMA Android Development] TheKartus:
Is it not possible to add the new memory changes into a zImage for HaRet users? The latest NBH is the 5th, last zImage is the 2nd
[Touch CDMA Android Development] incubus26jc:
just have to wait for dzo to make one
[Touch CDMA Android Development] ParMaster:
Thanks my mistake.
[Touch CDMA Android Development] BigMango:
The latest version has US English + UK English + Spanish.

How can I replace the Spanish with French? (Spanish is of no use to me but I would need French)

Furthermore, it now only supports qwerty keyboard. How can I add azerty back in (or replace qwerty with azerty)?

Thanks.

edit: if it is too complicated to have the French language, only having the azerty keyboard (to use the kaiser hardware keyboard) would be enough for me.
[Touch CDMA Android Development] BigMango:
SMS delivery reports don't work, the status always stays "pending" after the message was successfully delivered.

(this option is enabled in the messaging settings).
[Touch CDMA Android Development] blindguyinanorgy:
the system must be built with the languages. here is the depository if you know how to build.

i just noticed dzo updated the tree with a EU version so every build dump from now on could have both