yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Hi, i try your great rom on polaris but (in my case) adb stops working.

i use the latest dzo kernel and 2010-06-17 release. -> Kernel Problem :-(
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Definately use panel type=2 or 3. They are for the Kaiser, i'm using 3 curently but as loserskater said they are fundamentally the same on the surface.
[Tilt, TyTN II, MDA Vario III Android Development] piotrv:
mp4 video decoding is working in Myn's Warm Eclair Beta2/RLS1.

So it seems to be possible to get it working with Eclair!:D
[Tilt, TyTN II, MDA Vario III Android Development] msd24200:
Yeah i changed it to 3 last night and it looks good now i may try 2 because with 3 i get a brief white screen when waking tho the white screen with 3 only last a couple of seconds so its no big deal. I'm really liking android may end up flashing it to nand :)
[Tilt, TyTN II, MDA Vario III Android Development] SuperJMN:
@kallt_kaffe, how maintainable is the odexing feature? I mean... the default installation comes with all the apps odexed, but if you install new apps, they won't be odexed until you run some script.

Then, I have read that you could end up having problems with updates, so... odexing is a state in which the app runs faster but it you want to install a new version you may have to remove some .odex files. Am I right?

Couldn't that be automatically controlled? What steps should we make to odex every application and avoid the problems when some update is being installed?

Thanks a lot for any further clarification!
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Correct.

Correct again...

Yes, I'm sure it could be automated so that it upon reboot checks which .apk's contains a .dex file and delete their .odex file and create a new one. However, it would increase boot time, but it sure is possible. I have considered it.

I'll try to explain... All .apk's (apps) and the framework (.jar files) are pre odexed and zipalign when you install. All those are stored in /system/app and /system/framework. /system is a read-only filesystem and those apps never change so this is the default setup and it should not cause any problems.

Now, if you edit /system/bin/userinit.sh and enable odex.sh script to run at boot it gets a little bit more complicated. Now it will look at the apk's in /data/app (that is all apps that you've installed yourself) on each boot and odex and zipalign them. What happens then is that the .dex file in the apk is removed and instead a .odex file (with the same name as the apk) will be created in /data/app. The app will take more space as the .dex file is now stored uncompressed but on the other hand it won't use any dalvik cache at all so the impact is not as big as you might think.

This is all fine as long as you do not update the app. What happens when you update the app is that the .apk file will be replaced with a non-odexed one. And the odex.sh script looks for a .odex file and if it's present then it will assume that the .apk is allready odexed and zipaligned and it will be ignored. So the new version will not be odex:ed and zipaligned unless you delete the old .odex file from /data/app and restart the phone. Also I'm not 100% sure you won't run into some problems if you run the upgraded apk while the old .odex is in place. It didn't seem to have any effect when I tried but I haven't tested it that much.

So basicly, if you know what you are doing, enabling odex.sh is should be safe (I always run it that way) but it should be possible to automaticly detect and odex upgraded apps if you change the script to look for .dex files in the .apk instead of .odex files but it will increase the boot time. The more apps you have, the longer it will take to boot.

Anyway, with all the system apps and the framework pre-odex:ed and zipaligned I think you still get a noticable speed increase even if you do not enable odex.sh.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Interesting. I did change some things in build.prop between RLS2 and RLS3/3b.

RLS2

# RIL settings
ro.ril.gprsclass=12
ro.ril.hsxpa=0
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.hsupa.category = 5

RLS3/3b

## RIL settings
# US
#ro.ril.gprsclass=10
#ro.ril.hsxpa=1

# EU
ro.ril.gprsclass=12
ro.ril.hsxpa=2

#ro.ril.hep=1
#ro.ril.enable.dtm=1
#ro.ril.hsdpa.category=8
#ro.ril.enable.a53=1
#ro.ril.enable.3g.prefix=1
#ro.ril.htcmaskw1.bitmask = 4294967295
#ro.ril.htcmaskw1 = 14449
#ro.ril.hsupa.category = 5

As you can see I disabled a lot of ro.ril. variables that wasn't present in the original Cyanogenmod but is present in most, if not all other Vogue/Kaiser builds.

More importantly I did change the ro.ril.hsxpa variable. Here's some information about it: http://www.google.com/support/forum/p/android/thread?tid=70bc0539d1352511&hl=en

I can't say I fully understand what it does but depending on what operator you have it might make a difference.
[Tilt, TyTN II, MDA Vario III Android Development] SuperJMN:
Thank you for shedding light on this interesting subject. For the moment, I won't enable this feature as you said it might not improve the performance noticeably.

I have to say that your build is much improved and responsive, although it sometimes has some delays when switching from applications like Opera Mini 5 Beta, BeyondPod or Google Maps. I think they're memory intensive apps that reclaim almost all the system resources. I hope that memory management could still be improved.

Overall, a 9 out of 10 for this build.
[Tilt, TyTN II, MDA Vario III Android Development] foxct2005:
In my POLA100 when I press "RUN" on Haret for SD installer (NOT NAND), my cruise SHOUTDOWN. What files I must to use to install this build on polaris POLA100?

Thanks in advance.
[Tilt, TyTN II, MDA Vario III Android Development] blindguyinanorgy:
@k_k

could your write a script to do the long way that we could run on demand when we update?

even if needs to run on boot you could have two scripts and a third to run from inside OS that changes which script boots on next reboot...then at the end of the long script automatically change back
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Try enabling Compcache in Spare parts. It may help
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Actally if you update an app (and have odex.sh enabled in userinit.sh) you could do this in a terminal.

$ su

# cd /data/app

# rm whatever.app.you.just.updated.odex

# odex.sh

That would odex the new apk without the need of a reboot.
[Tilt, TyTN II, MDA Vario III Android Development] arkieiowa:
Best Kaiser build yet

Thanks to everyone for this build its great.

I have a quick comment for everyone that uses this build and does not have a unlimited data plan. You need to go into settings click on wireless and networks, then to mobile networks, access point names then change setting to none.

I ran up a $50 charge on my data connection. I just like using the wifi only. I just wanted everyone who downloads this great build that doesnt have unlimited data plan.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Re: VaniljEclair RLS3b [2010-06-17] + QVGA dialer update [2010-06-18]

I just saw that CM 5.0.8-stable was has been released for the G1 so I'll use that as the new base as soon as I get time to port it.
[Tilt, TyTN II, MDA Vario III Android Development] blindguyinanorgy:
so the script is odex.sh can be set to run at reboot, but can be run one time any time.

you talked about the other option for a script that actually checks.

heres my thought. i am *trying* to learn the android kernal and programing. ive heard its best to start by writing some programs. if you have both script i can [theoretically] make a quick UI so average users can use the ODEX comfortably.

even just the two scripts would be easier for a semi knowledgeable user...the names for the odex files in data apps are the long names not the pretty names. also say i update a few things at once, or a program is acting funny. running the long script would be a nice convenience
[Tilt, TyTN II, MDA Vario III Android Development] chourmovs:
I was reading your script attempt to de-odex manually with lost of interest when i read your signature

My personal ranking is exactly the same on POLARIS

Sorry to say nothing very interesting :p
[Tilt, TyTN II, MDA Vario III Android Development] peepingtom:
Has anybody had an issue with SIPdroid pushing audio through the external speakerphone speaker rather than the earpiece? I know this is not unique to this particular Android build, but it is an issue with certain android builds including ones shipped by Samsung and HTC. This likely occurs with other VoIP apps like Fring, too. The third link I posted has the most information.

ht tp://code.google.com/p/sipdroid/issues/detail?id=366

ht tp://code.google.com/p/sipdroid/issues/detail?id=341&q=speaker

Sorry I don't want to get anyone off track, this just seems like a really well put together build and I thought someone knowledgeable about audio routing may have noticed this, but i'm not sure if this is a problem with the build or SIPdroid and Fring.

kallt_kaffe, thank you so much for this android build and also your kernel binaries, I use them both on my Kaiser!
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
After 2 days...

Well... Thanks for those informations but I understand : nothing ! Sorry because I'm not a developer... But If I can help you I agree to do that.

At the end of this sunday, I tested most of your build and everything I used is ok for me in Polaris except BT audio for carkit (Kernel problem...). I lose just one time network : and when I lose it, I wait just a few seconds for receive a correct signal...

I use compcache and odex in userinit.sh and lcd with 120 (you're right it's the best for stable and fast...).

Gps is working good but IGO (navigation software) is a bit slow...

Wifi perfect but a bit slow with market : I think it's my internet connection (my 2 sons with WOW !!)...

Thanks again for this excellent work and for the time you spent for us : you doesn't have a paypal account ? :):)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I have a couple of paypal accounts but if you want to donate, donate to dzo for without his work with the kernel we wouldn't even be thinking about running Android on our WinMo phones.

You can find a donation link for dzo (Martin) here: http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
Donation : an obligation...

Thanks I do it right now...
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Guys it takes the system about 30 seconds to load the defaul dialer, since this is my first android build im wondering is that normal?? Overall it seems good although opening apps takes a while sometimes.

I'm running this build from my storage card. Any recommendation as to what kernel etc. should i use to speed up the loading process of apps would be appreciated. Also when i launch apps the screen goes black for 5 up to 30 seconds(dialer) it seems like some animations are missing??? Thanks
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
Exchange CAL+GAL?

I tried this very good build together with the latest kernel yesterday. It all worked quite well, except two (for me) crucial things:

1. No Exchange Calendar syncing or showing

2. No Exchange Global Address List (GAL)

I've seen/read a few threads regarding this issue e.g.

xdaforums.com/showthread.php?t=613404

(I'm not allowed to post the full URL :S )

I briefly tried a download of the corp.apk but only installed it via the file manager on the phone, which might have been wrong.

So big questions are:

Can this build support Exchange CAL/GAL?

If so, which (Kaiser?) specific package do I need?

How do I install it?

As I need the phone regularly, I've had to go back to WM, but I will try again if I get an idea.

Thanks for your support!!!
[Tilt, TyTN II, MDA Vario III Android Development] zenity:
To be totally honest, I'd recommend those who absolutely require the synchronisation provided by Windows Mobile stick with it at present.

Android on Kaiser is still very much Beta software at present, and still has a certain lack of functionality compared to Winmo, I am fortunate enough to be in a position where my only needs are SMS and occasional phone calls, music and email, all of which Android manages to do acceptably.

@Arturo; The delay is unfortunately common, and is mainly caused by the load/unload of resources on processors that are a little slower than Android was designed for, you can speed up some of if by tweaking the GUI a little, doing without some of the animations etc, all of which can be changed in settings and spare parts, you could also try turning on compcache as well.
[Tilt, TyTN II, MDA Vario III Android Development] msd24200:
only problem i've really noticed is that it won't import my sim contacts when i try to, but other than that no major problems, this android build is EXCELLENT, very nice, now i wish that ATT would release a GSM version of the SPRINT/HTC EVO :cool: then id be in htc heaven.
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
@zenity

Thanks for your advice.

I appreciate that it's still early days and had already tried a few other builds with way less success. But after seeing soo many happy news and reviews here I just had to give it a go.

As said I think it is very workable apart from the Exchange side.

By now I've found a newer version of the corpcal.apk (V1.0.4), so I'll give that a go next weekend if I get time.

One other question:

Apart from the rescue mode and the debug setup, is there no other way of getting to the phone/SD memory from the PC via USB?
[Tilt, TyTN II, MDA Vario III Android Development] omegazxd:
Hi kallt_kaffe

i download and install your RLS3b by NAND sys and NAND Data.

now there is a problem, sometimes the google account will be lost by himself(after restart).

does anyone have the same problem like me?
[Tilt, TyTN II, MDA Vario III Android Development] thoughtlesskyle:
were those the only changes to this build for rls4 or are there more? because it doesnt seem like a need to update since i dont use qvga, and dont have wifi
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
That's all really... I just wanted to make a last complete CM 5.0.7 release before releasing the CM 5.0.8 port that I'm currently working on, just in case someone prefer CM 5.0.7 then there will be a version to fall back to.
[Tilt, TyTN II, MDA Vario III Android Development] shanbh:
good

Thank you for you work, it make my old kaiser own a new life.
[Tilt, TyTN II, MDA Vario III Android Development] foxct2005:
Congratulation !!!

This is the only build working Wifi/BT for my Pola100 !!!

It's a GREAT BUILD ... Maybe a bit slower than Myn's Eclair, but works perfectly!!!

Only a question:

- When I try to install "LAUNCHERPRO" ... AFTER installing nothing change on "Home" Screen. Nothing.

How Installing Launcherpro correctly ?

(My installation is on SD with Haret, Not NAND).

Please any help is appreciated.

Thanks in Advance.
[Tilt, TyTN II, MDA Vario III Android Development] piotrv:
mp4 decoding in CM builds

I reckon the mp4 decoding problem I experience is related to all CM based builds.

I tested with CM 5.0.7 and CM 5.0.8

mp4 decoding in Myn's Warm Eclair however is working fine.

I can play videos, no problem.

It might be not high on your priority list, but its something I'm really missing in VaniljEclair (and Incubus's SuperE)
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
After installation, press the "home" button. On my Kaiser it is the "explorer" button. You should now get a choice between the two installed launchers.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I've tried just about everything and still no go... I think mssmison fixed this once in his build and I believe Myns build is based on the framework and libs that mssmison used. Propably something that needs to be changed in the code and then recompiled. Propably one of the libs. I've asked mssmison but I have not yet recieved an answer.

The reason I believe this is this post: http://xdaforums.com/showpost.php?p=5844809&postcount=52
[Tilt, TyTN II, MDA Vario III Android Development] foxct2005:
Installing Launcherpro on Vanilj

In My Polaris (Pola100) I have only a "Back" Key which exit from applications steps by steps and return to "Home". This key is under "Gps" Keys (under green telephone) ...

Do you know if in Polaris some other key (even holding it) works as "Home" ?

Thank you.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Just restart the phone. I think you will be asked also when you unlock after a fresh boot.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Try using Power button as "Home button"
[Tilt, TyTN II, MDA Vario III Android Development] foxct2005:
Thanks all for great replies.

From Where setting Power Button as "Home" ? Is there any option to find ?

In case of I could setting Power as Home, with wich button Polaris will Power On?

Power button will work both Home and Power in the contemporanely ?

I found this Key Map for Polaris: can you confirm ?

Volume controls volume

Long Press camera is home

Press and release camera is back

Press and release top power button is menu

Press and hold 1 second top power button for on screen keypad

Press and hold 2 seconds top power button for landscape (turn off auto rotate in settings)

Press and hold end key for shutdown menu

If true, Long press Camera = Home;

But in other topic i found that "camera" key is not working on polaris android.

Excuse for my stupid question but I am in office and I can't try in this moment.

Thanks to all!!!
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
RLS5 based on CM 5.0.8. My own reaction is that it may not be as fast as CM 5.0.7. Propably due to the new launcher. I will give a day or two then I will install Launcher Pro and see if I notice any speed difference.

Seems to stable though, new music player looks better in QVGA than the old one.
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
You're right but you forgot : long press speak button (in the left of the phone) for landscape and return it, and long press end key for options of phone...
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
Hard to take time for test but I will get it...

Hi,

I will try it right now : thanks for your support.

Cheers.
[Tilt, TyTN II, MDA Vario III Android Development] fiddelm3742:
The big question here is, do you have a Donation link?

I don't have the linux skill set to do what you guys do mish mashing things together to get the best experience on our Kaisers so I'd like to send a small donation your way as thanks/appreciation/encouragement to keep up the great work (and to keep you from abandoning the Kaiser like more and more people seem to be doing ;) )
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I've haven't bothered to measure the incoming call delay before but I know I've missed calls with other builds before so I expected it to still be an issue and I've was planning to try some process priority hacks to see what could be done.

But to my surprise the delays aren't anything near what I've experienced in the past. I even enabled Vibration and got the name of the caller displaying within 4 seconds (from sleep). It's propably a combination of odex:ing, Cyanogenmod allready being a fast build and dzo making miracle with the kernel (as usual).

What are you experiencing?

EDIT: This is with NAND install, compcache enabled and all installed apps odex:ed.
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
Donate enough and I'll buy a Desire and you'll never see me here again. ;)

But seriously, this is the second time someone asked for this in a short time. I will consider it but in the meantime, the real hero working behind the scenes here is Martin (dzo). Without his work we would be discussing which WinMo 6.5 build was least crappy right now. You'll find a donation link for dzo on this page: http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart

This build specificly is Cyanogens work, I just ported it, so why not "buy him a beer" as the last line of the first post in this thread suggests? http://xdaforums.com/showthread.php?t=688262
[Tilt, TyTN II, MDA Vario III Android Development] kallt_kaffe:
I'm also interested in opinions on what gives the snappiest experience, the included ADW Launcher or Launcher Pro (free download from Market). I really like Launcher Pro and have been running it all the time but this ADW Launcher is nice too, they have a lot in common.
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
Same problem when someone tell me : I wait to see who is it ... I'm bored of that but I do with it...

I tested with many builds in combination with many versions of kernel but always the same comportment ! NAlways, I disabled vibration when incall and enable vibration just for second call... All of the rest is disable !

Well I think a little better with CM but not sure.

I also note that when you want to access a contact, it's a bit long... Same thing when you want to make a call but much better in your build (RS3b) -> the begin of call arrive 1 or 2 seconds after I pressed phone call button :)

Hope that's help you... I will test it with your new build...

Cheers
[Tilt, TyTN II, MDA Vario III Android Development] manu33xtro:
I like launcherpro too... I have just finish to install your new version... Hum great ! I think we have more options with ADW and a bit slower I think than launcherpro, but they are only the first impressions...

But could you for the last build, insert Astro or root explorer ?

Thanks in advance.

Cheers.
[Android Software Development] doaneramma:
I have been looking for ages to see if there is an app like what I am looking for.

I Have a lot of music. A LOT! And i had the wonderful experience of having itunes "organize" my music into XDJS.mp3. Well, thats all fine and dandy, but half of them either had incorrect or no ID3 tags before. Fast forward to my beloved android phone. it now has the tunes, but the albums/art are screwy and artists are all off.

Is there an app that ties shazam style song recognition, with an auto ID3/file rename capability? Something I can point at my collection and have it go through and fix the info automatically for the whole thing? Yea, lot of data and processor to do it. But I could plug the phone in and let it run on wifi. Just a thought.

I have no programming skills, so hoping someone out there has ran into something that can help me out.
[Desire General] zonkkk:
Just thought I should let everyone know, and don't worry there's enough for everybody. :-)
[Desire General] AdamLC:
Just need the apk now ;)
[Desire General] jannen:
I had the Google Earth installed when I first got the phone. But to be honest (to my opinion) the Google Maps do the same thing. The 3D viewing etc of course is cool, but for practical point of view Maps covers the same (sat view). And the Google Earth does eat you precious memory - well until Froyo I hope!! :)
[Nexus One Q&A, Help & Troubleshooting] clwclw:
If this isn't the correct place for this feel free to move it, I only posted it in this forum because I feel like this is the only place where I would get an answer.

Currently in fastboot my N1 says: NEXUSONE PVT SHIP S-ON

I want it to be turned off, so it'd be like NEXUSONE PVT SHIP S-OFF

Is there a way to do this? (I've seen it on some phones)

Thanks!
[Nexus One Q&A, Help & Troubleshooting] panthar:
Hmmmmm... are you trying to re-lock your rooted N1? ;)
[Nexus One Q&A, Help & Troubleshooting] clwclw:
is that what that means? I was just informed that it could be done and I need it for a certain thing that I'm trying to do=x
[Nexus One Q&A, Help & Troubleshooting] zha50:
Relocking not possible in the retail phones. Our N1's are not user lockable at this point in time.