**************************************************
I am no longer supporting or porting this theme. Sorry.
**************************************************
Thanks to ultra spikey and kyleds for many of the images.
nice nice nice
this Aero looks nice
Very nice. I am switching immediately. I am on CM 3.5.
I would like to replace some more of the icons. Can you tell me please where to put them in the file structure so that they are changed in the launcher as well as the home screens? It looks like you have changed many but not all.
Very nice work.
PS: Like the wallpaper on your older build. ;-)
PPS: Where in the St.Pete area are you? I am in Clearwater.
Looks nice. I'll test it out on CM 3.5 also.
stellarman said:
Very nice. I am switching immediately. I am on CM 3.5.
I would like to replace some more of the icons. Can you tell me please where to put them in the file structure so that they are changed in the launcher as well as the home screens? It looks like you have changed many but not all.
Very nice work.
PS: Like the wallpaper on your older build. ;-)
PPS: Where in the St.Pete area are you? I am in Clearwater.
Click to expand...
Click to collapse
The individual APKs have the images in them, that's why the core apps are done (mostly), but the 3rd party apps are on my sd card....
I liked it too, the gf wasn't feeling it I don't think...
I'm in the feathersound area, /wave!!!
Missing Im App
the im app is missing. i think their is something wrong with the template cause this happened on the Progitcal sun theme as well, 3.4.6 has im but when you flash its gone. the only theme it works on is hero. u guys should contact CM
aero has always been such a good looking theme. It's a shame that not all apps have that glass background to them, kind of breaks the zen of the theme
rasturn said:
the im app is missing. i think their is something wrong with the template cause this happened on the Progitcal sun theme as well, 3.4.6 has im but when you flash its gone. the only theme it works on is hero. u guys should contact CM
Click to expand...
Click to collapse
My Messaging app is missing/broken too. It is there, but will not open. I have tried almost everything to fix, but no luck. Would re-install if I could find the APK file for it. For me, it disappeared a couple of CM builds ago when my SD card ext3 partition crapped out. I was on the Hero theme at the time, so it probably is not theme specific problem.
Any help would be appreciated.
I've updated the theme.
If you redownload and install it - you should have an IM application:
Latest md5sum: 9a55e693ae795f8813e85a1ee4aca52c
Latest theme: rAero1.5_ADP1_SMM.zip
I'm not keeping old versions, I apologize in advance.
So....that should take care of:
Camera image.
Camcorder image.
Gallery image.
Instant Messenger.
Instant Messenger image.
*****BE ADVISED: IF YOU UPDATE THIS IT WILL SHOW 3.5.1-NOSQUASH AS YOUR MOD IN THE SETTINGS > ABOUT PHONE ******
Let me know if there is more that I can do. : )
Auto rotate
Let me know if there is more that I can do. : )[/QUOTE]
Looks like auto rotate is not working in 3.4.x. Anybody else having that issue?
Also. Cyan released a new theme template with 3.5.. is this going to be compatible with Cyan's 3.5.x or upcoming 3.6?
Thanks a lot for your contributions
ranjaheer said:
Let me know if there is more that I can do. : )
Click to expand...
Click to collapse
Looks like auto rotate is not working in 3.4.x. Anybody else having that issue?
Also. Cyan released a new theme template with 3.5.. is this going to be compatible with Cyan's 3.5.x or upcoming 3.6?
Thanks a lot for your contributions [/QUOTE]
I don't know why the auto rotate wouldn't work...I've had nothing but luck with the 3.4 and 3.5/3.5.1-no squashfs.....
I'll be looking into the new build environment and theme template tomorrow for sure. : )
Updated using cyanogens 3.5.2 template.
Thanks for putting this together! I was doing it the other night but got lazy and gave up lol. I just updated to CM3.4.6, then ran your Aero port for CM3.4. I havnt used it much yet, but everything seems to be there. The only thing that doesnt work is the HTC Camcorder. This is biggie for me. It will open up, and even start recording, but when I stop recording it force closes. Is this happening to anyone else?
edit: Did you use Cyanogens 3.4.5 theme template to make this?
ultra spikey said:
Thanks for putting this together! I was doing it the other night but got lazy and gave up lol. I just updated to CM3.4.6, then ran your Aero port for CM3.4. I havnt used it much yet, but everything seems to be there. The only thing that doesnt work is the HTC Camcorder. This is biggie for me. It will open up, and even start recording, but when I stop recording it force closes. Is this happening to anyone else?
edit: Did you use Cyanogens 3.4.5 theme template to make this?
Click to expand...
Click to collapse
That is odd, I am having the same issue with the camcorder.
I just pulled the Camera.apk out of cyanogen's theme template and I'm getting the same force close. Lame, if anyone knows of a good Camera.apk let me know - and I'll roll it up into the themes.
Code:
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 578): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 578): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 578): Caused by: java.io.FileNotFoundException: This file can
not be opened as a file descriptor; it is probably compressed
E/AndroidRuntime( 578): at android.content.res.AssetManager.openNonAsset
FdNative(Native Method)
E/AndroidRuntime( 578): at android.content.res.AssetManager.openNonAsset
Fd(AssetManager.java:412)
E/AndroidRuntime( 578): at android.content.res.Resources.openRawResource
Fd(Resources.java:811)
E/AndroidRuntime( 578): ... 29 more
I/Process ( 129): Sending signal. PID: 578 SIG: 3
I/dalvikvm( 578): threadid=7: reacting to signal 3
I/dalvikvm( 578): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 129): Added state dump to 1 crashes
Here's the strace on the camera pid crashing:
Code:
----- pid 578 at 2009-06-29 23:32:40 -----
Cmd line: com.android.camera
DALVIK THREADS:
"main" prio=5 tid=3 NATIVE
| group="main" sCount=1 dsCount=0 s=0 obj=0x40018f00
| sysTid=578 nice=0 sched=0/0 handle=-1092580372
at android.os.BinderProxy.transact(Native Method)
at android.app.ActivityManagerProxy.handleApplicationError(ActivityManagerNati
ve.java:2103)
at com.android.internal.os.RuntimeInit.crash(RuntimeInit.java:302)
at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(Runti
meInit.java:75)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
at dalvik.system.NativeStart.main(Native Method)
"android.hardware.SensorManager$SensorThread" prio=5 tid=17 NATIVE
| group="main" sCount=1 dsCount=0 s=0 obj=0x43967898
| sysTid=585 nice=-4 sched=0/0 handle=1899640
at android.hardware.SensorManager.sensors_data_poll(Native Method)
at android.hardware.SensorManager$SensorThread$SensorThreadRunnable.run(Sensor
Manager.java:325)
at java.lang.Thread.run(Thread.java:1058)
"Binder Thread #3" prio=5 tid=15 NATIVE
| group="main" sCount=1 dsCount=0 s=0 obj=0x43919110
| sysTid=584 nice=0 sched=0/0 handle=1587608
at dalvik.system.NativeStart.run(Native Method)
"Binder Thread #2" prio=5 tid=13 NATIVE
| group="main" sCount=1 dsCount=0 s=0 obj=0x43919050
| sysTid=583 nice=0 sched=0/0 handle=1618800
at dalvik.system.NativeStart.run(Native Method)
"Binder Thread #1" prio=5 tid=11 NATIVE
| group="main" sCount=1 dsCount=0 s=0 obj=0x43918f90
| sysTid=582 nice=0 sched=0/0 handle=1615424
at dalvik.system.NativeStart.run(Native Method)
"JDWP" daemon prio=5 tid=9 VMWAIT
| group="system" sCount=1 dsCount=0 s=0 obj=0x439182a0
| sysTid=581 nice=0 sched=0/0 handle=1591752
at dalvik.system.NativeStart.run(Native Method)
"Signal Catcher" daemon prio=5 tid=7 RUNNABLE
| group="system" sCount=0 dsCount=0 s=0 obj=0x439181e8
| sysTid=580 nice=0 sched=0/0 handle=1590984
at dalvik.system.NativeStart.run(Native Method)
"HeapWorker" daemon prio=5 tid=5 VMWAIT
| group="system" sCount=1 dsCount=0 s=0 obj=0x42b5df50
| sysTid=579 nice=0 sched=0/0 handle=1588344
at dalvik.system.NativeStart.run(Native Method)
----- end 578 -----
I have no idea what that means lol...I haven't seen anyone else report that their Camcorder doesnt work in the new CM roms. Could it be corrupt in your theme? Have you tried copying over the camera.apk from like a CM zip?
ultra spikey said:
I have no idea what that means lol...I haven't seen anyone else report that their Camcorder doesnt work in the new CM roms. Could it be corrupt in your theme? Have you tried copying over the camera.apk from like a CM zip?
Click to expand...
Click to collapse
Yes, I just tested with the camera.apk from his template.
Works perfectly in the 3.5.2 rom, I'm going to copy it over to my theme for 3.5.2 if it works I'll do it for the 3.4x as well.
Well, I went ahead and copied the camera.apk from CM3.4.6 and pasted it into your theme zip, and it worked. Looks like your apk is corrupt(or the apk in CM's template is corrupt).
Yep, it looks that way, I just pulled the apk out of his latest rom as well. For some reason even when I pull a known good Camera.apk and zip it back into the theme it's force closing still. I'm miffed. : (
ultra spikey said:
Thanks for putting this together! I was doing it the other night but got lazy and gave up lol. I just updated to CM3.4.6, then ran your Aero port for CM3.4. I havnt used it much yet, but everything seems to be there. The only thing that doesnt work is the HTC Camcorder. This is biggie for me. It will open up, and even start recording, but when I stop recording it force closes. Is this happening to anyone else?
edit: Did you use Cyanogens 3.4.5 theme template to make this?
Click to expand...
Click to collapse
Same here camcorder force closes when stopping the video on 3.5.2.
edit: Moving back to a re-flash of 3.5.2 camcorder works again. i also noticed I had no camcorder sounds with the theme, but I do on a clean 352 cyanogen flash.
I will upload Aero for CM3.4.x with working htc camcorder later today.
Hi, guys. I am having some troubles with the MIUI rom and the application "Cardiotrainer" because of a class that crashes in miui. I sent a message to a couple of admins of the miui main page, and also posted a couple of threads in the miui developers forum, but I had no response of any of the messages. I hope you can help me. I attach the last message I sent:
Hi. I sent you a message a couple of days ago, but I suppose it was deleted when the server failed. I hope you can help me, because I can't read chinese, so I can only read what google can translate hehehehe. First of all I would like to thank all the miui staff because of their great job. I like miui much more than any other rom, but since some versions ago I am having troubles with an application.
When I go running, I use the "Cardiotrainer" application, but since some versions ago, when I select some versions of the settings menu (all of them that display another submenu) the program crashes. It only happens with miui, so it's a rom problem. I read the crash log and I suppose the problem is becaus a NullPointerException in the PreferenceActivity class. Anyway I attach the crash error just in case it's helpful.
Code:
ERROR REPORT
Report type
Crash
Package name
com.wsl.CardioTrainer
Package version
63
Package version name
3.4.1
Installed by
com.google.android.feedback
Process name
com.wsl.CardioTrainer
Time
wednesday 22 december 2010
System app
false
SYSTEM
Device
passion
Build id
MIUI.0.12.11
Build type
userdebug
Model
Nexus One
Product
libra_passion
SDK version
8
Release
2.2.1
Incremental version
0.12.11
Codename
REL
Board
mahimahi
Brand
generic
Running applications
com.google.android.feedback
com.android.inputmethod.latin
com.android.providers.calendar
android.process.acore
com.google.process.gapps
com.android.phone
system
com.google.android.googlequicksearchbox
android.process.media
com.android.vending
com.svox.pico
com.android.voicedialer
com.noshufou.android.su
com.android.defcontainer
com.cooliris.media
com.google.android.apps.mapsocationFriendService
com.android.vending.updater
com.android.launcher
com.android.updater
com.miui.player
com.google.android.apps.uploader
com.twitter.android
(sorry, but it's quite impossible to copy the logs )
CRASH
Exception class name
java.lang.NullPointerException
Source file
PreferenceActivity.java
Source class
android.preference.PreferenceActivity
Source method
bindPreferences
Line number
247
Stack trace
java.lang.NullPointerException
at android.preference.PreferenceActivity.
bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.
access$000(PreferenceActivity.java:86)
at android.preference.
PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.
dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.
main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(NativeMethod)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.
ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.
main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(NativeMethod)
I hope with this information the problem can be solved. Thanks for your time.
Click to expand...
Click to collapse
+1
I am also using CardioTrainer on a MIUI ROM and it always crashes in settings :'(
I also have a similar problem with the Youversion Bible app. The tech support guys there reported that this is common problem with different apps in MIUI as MIUI has some "different structure" of handling settings. When pressing settings, the app crashes.
Here's my log:
processName:com.sirma.mobile.bible.android
pid:12915
uid:10072
tag:null
shortMsg:java.lang.NullPointerException
longMsg:java.lang.NullPointerException
stackTrace:java.lang.NullPointerException
at android.preference.PreferenceActivity.bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.access$000(PreferenceActivity.java:86)
at android.preference.PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4628)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:870)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
I have MIUI 1.3.5 on the Sprint EVO, but I believe this is a general MIUI problem, so posting here.
Just flashe (and re-flashed just in case) update-cm-7-20111030-Magpie-DS-signed by "Firerat" from his dropbox, go to select CyanogenMod Settings under Setting and get "com.android setting" FCs....
Logcat shown the follong......
11-06 10:10:06.700 I/ActivityManager(248)Starting: Intent { act=android.intent.action.MAIN cmp=com.cyanogenmod.cmparts/.activities.MainActivity } from pid 6687
11-06 10:10:06.710 D/AndroidRuntime(6687)Shutting down VM
11-06 10:10:06.730 W/dalvikvm(6687)threadid=1: thread exiting with uncaught exception (group=0x401a8560)
11-06 10:10:06.750 E/AndroidRuntime(6687)FATAL EXCEPTION: main
11-06 10:10:06.750 E/AndroidRuntime(6687)android.content.ActivityNotFoundException: Unable to find explicit activity class {com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.MainActivity}; have you declared this activity in your AndroidManifest.xml?
any help appriciated
thaks in advance
Tim
It's been a long time since I've even tried to port a ROM. Android surely has changed a lot and now I get to meet new errors that I have never seen and have no idea to get past.
Mainly posting this because I only actually have an hour or less every day to work on this, and if I couldn't get it working quickly enough then I'd just leave it up to the community. Used MapleSyrup's AOSP 4.1.1 ROM and Galaxy Nexus's MIUI.US ROM. Whoever can fix this error will win 100 internetz, and maybe a small donation if it's fully booting/working. As I said I really have little time to work on this.
The error;
Code:
W/Zygote ( 105): Class not found for preloading: android.media.AudioManager$2
E/JNIHelp ( 105): Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
F/libc ( 105): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 105 (zygote)
MIUI boots to the bootanimation. The animation doesn't loop but the system is looping at that. Want to try an fix it? Here ya go;
By clicking the download link, you fully acknowledge that this ROM is still under development, and not all, if any, features may be available to the user. You also acknowledge that you are fully accountable for any damages, explosions, sword fights, or other unexpected activity that may occur to your device.
http://goo.gl/4zzzl
Btw I see no rules as to whether non-fully-booting ROMs can be placed here so if not... Oops.
GazaIan said:
Code:
W/Zygote ( 105): Class not found for preloading: android.media.AudioManager$2
E/JNIHelp ( 105): Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
F/libc ( 105): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 105 (zygote)
Click to expand...
Click to collapse
Wild assed guess, here... but it looks like you are missing JNI library. I can't post a link, but I found the following in the source code for com.android.media.videoeditor.VideoEditorProfile.java.You'll notice a promising bit in the constructor...
Code:
static {
System.loadLibrary("media_jni");
native_init();
}
You might want to see if your ROM has that lib available.
Hello everyone, i want to connect file shared on my windows
I make app android to view file on any windows by share file
but i have a problem
please help me!
this is my code:
NtlmPasswordAuthentication auth = new NtlmPasswordAuthentication("","wd","admin123");
String path = "smb://10.10.120.195/Share/a.txt";
try {
SmbFile file = new SmbFile(path, auth);
file.connect();
}
catch(Exception e)
{
}
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ problem
D/libc-netbsd: [getaddrinfo]: ai_addrlen=0; ai_canonname=(null); ai_flags=4; ai_family=0
D/AndroidRuntime: Shutting down VM
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.admin.myapplication, PID: 12663
java.lang.ExceptionInInitializerError
at jcifs.netbios.NbtAddress.getWINSAddress(NbtAddress.java:533)
at jcifs.UniAddress.<clinit>(UniAddress.java:62)
at jcifs.smb.SmbFile.getFirstAddress(SmbFile.java:922)
at jcifs.smb.SmbFile.connect(SmbFile.java:1012)
at com.example.admin.myapplication.MainActivity.onCreate(MainActivity.java:31)
at android.app.Activity.performCreate(Activity.java:6309)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2519)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2654)
at android.app.ActivityThread.-wrap11(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1488)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5728)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: android.os.NetworkOnMainThreadException
at android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(StrictMode.java:1288)
at java.net.InetAddress.lookupHostByName(InetAddress.java:432)
at java.net.InetAddress.getLocalHost(InetAddress.java:410)
at jcifs.netbios.NbtAddress.<clinit>(NbtAddress.java:187)
at jcifs.netbios.NbtAddress.getWINSAddress(NbtAddress.java:533)*
at jcifs.UniAddress.<clinit>(UniAddress.java:62)*
at jcifs.smb.SmbFile.getFirstAddress(SmbFile.java:922)*
at jcifs.smb.SmbFile.connect(SmbFile.java:1012)*
at com.example.admin.myapplication.MainActivity.onCreate(MainActivity.java:31)*
at android.app.Activity.performCreate(Activity.java:6309)*
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)*
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2519)*
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2654)*
at android.app.ActivityThread.-wrap11(ActivityThread.java)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1488)*
at android.os.Handler.dispatchMessage(Handler.java:111)*
at android.os.Looper.loop(Looper.java:207)*
at android.app.ActivityThread.main(ActivityThread.java:5728)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)*
I/System: FinalizerDaemon: finalize objects = 1
help me! please!
Reading through the error you will see that is is caused by Network on main thread exception.
In Android you are not allowed to do network calls on the main application thread. You need to use a separate AsyncTask. See this Stack Overflow thread.
http://stackoverflow.com/questions/6343166/how-to-fix-android-os-networkonmainthreadexception