OFFICIAL: Nexus One chat thread

[djunio]

Ya I forgot about that.. oops. lol
Well still, I know this is for PC's n such but it's progress on 10.1 and all the performance tweaks n such. So maybe this will get incorporated into the Android version and Froyo will be coming. It's got to be any day now anyways! It's been "A Few Weeks" already.

oh and no one responded to my de-odex'd comment.. what is that? is Cyan building from the source code for froyo right now, do we know?

In short, an odex file is an optimized version of a classes.dex file that has optimizations that are device specific. In particular, an odex file has dependencies on every "BOOTCLASSPATH" file that is loaded when it is generated. The odex file is only valid when used with these exact BOOTCLASSPATH files. dalvik enforces this by storing a checksum of each file that the odex file is dependent on, and ensuring that the checksum for each file matches when the odex file is loaded.
The BOOTCLASSPATH is simply a list of the jars/apk from which classes can be loaded, in addition to the main apk/jar that is loaded. A normal android system has 5 jars in it's base BOOTCLASSPATH - core.jar, ext.jar, framework.jar, android.policy.jar and services.jar. These can all be found in /system/framework. However, some apks have dependencies on additional jar or apks files beyond that of the base 5 jars. For example, for applications that use google maps, com.google.android.maps.jar will be appended to the BOOTCLASSPATH for that application's apk.
These odex dependencies make life a bit difficult for a couple of reasons. For one - you can't take an apk+odex file from one system image and run it on another system image (unless the other system image uses the exact same framework files). Another problem is that if you make any changes to any of the BOOTCLASSPATH files, it will invalidate every odex that depends on that file - basically every apk/jar on the device.



http://code.google.com/p/smali/wiki/DeodexInstructions

[TheJuan]

Ya I forgot about that.. oops. lol
Well still, I know this is for PC's n such but it's progress on 10.1 and all the performance tweaks n such. So mayb

In short, an odex file is an optimized version of a classes.dex file that has optimizations that are device specific. In particular, an odex file has dependencies on every "BOOTCLASSPATH" file that is loaded when it is generated. The odex file is only valid when used with these exact BOOTCLASSPATH files. dalvik enforces this by storing a checksum of each file that the odex file is dependent on, and ensuring that the checksum for each file matches when the odex file is loaded.
The BOOTCLASSPATH is simply a list of the jars/apk from which classes can be loaded, in addition to the main apk/jar that is loaded. A normal android system has 5 jars in it's base BOOTCLASSPATH - core.jar, ext.jar, framework.jar, android.policy.jar and services.jar. These can all be found in /system/framework. However, some apks have dependencies on additional jar or apks files beyond that of the base 5 jars. For example, for applications that use google maps, com.google.android.maps.jar will be appended to the BOOTCLASSPATH for that application's apk.
These odex dependencies make life a bit difficult for a couple of reasons. For one - you can't take an apk+odex file from one system image and run it on another system image (unless the other system image uses the exact same framework files). Another problem is that if you make any changes to any of the BOOTCLASSPATH files, it will invalidate every odex that depends on that file - basically every apk/jar on the device.



http://code.google.com/p/smali/wiki/DeodexInstructions

whoa whoa. talk about taking us to school..
what?

[xguntherc]

wow... English. lol jk jk

thanks for the explanation. Progress is good.

[ggrant3876]

Usb just crapped out, was transfering some files and had to move the micro end around quite a bit just to get it to mount. Didn't think much about it, left it on to charge and after 30 minutes the charge went down instead of up. Called HTC and they are sending out a new cable, said just throw the old one away like when I got my new battery under warranty. There customer support seems awfully good.

[xguntherc]

So, can anyone explain to me the different kernals.. like what exactly do they do. I always see people talking about cyan's .34 kernal or something. is that what was on all the CM5's that i seemed to get good battery life with?

[stalker]

kernel is basically refers to the core part of an operating system. Check this out..

http://en.wikipedia.org/wiki/Kernel_%28computing%29

[xguntherc]

Thanks.. I sort of understood how base kernals work and all that. I was referring to android specific different oernals people flash over there OS. Like Cyan's. 34 kernal people were adding onto there Froyo updates. Or the pershoot oc / uv kernal. Basically it just makes changes to the core parts of the OS in a stable way..

I'm still slowly learning everything, I wish I was running Cyans .34 this last month.

[stalker]

Thanks.. I sort of understood how base kernals work and all that. I was referring to android specific different oernals people flash over there OS. Like Cyan's. 34 kernal people were adding onto there Froyo updates. Or the pershoot oc / uv kernal. Basically it just makes changes to the core parts of the OS in a stable way..

I'm still slowly learning everything, I wish I was running Cyans .34 this last month.

Yup.. if a kernel version is changed then it is sure that the core part is changed a little bit.

[Elyse_mal]

I just got a new Nexus one and I plugged it in and it will not start up past the X. The X is not animated just static. I have had it on the charger now for over 4 hrs and the light is still not green. I have pulled the batt and now it is off and still at an orange light. When I turn it on all I get is the X. If anyone knows what this is all about please help. THANKS!