Develop Bugs

Sgs2 movie maker app

I seen the app in a review of the epic touch 4g is there anyway to port this over to us? Or push the apk
Sent from my SPH-D700 using XDA Premium App

Try using this?
http://forum.xda-developers.com/showthread.php?t=946499
Merg, I take it back, it doesn't install.
But, I grabbed the Video Maker from the Epic Touch 4G, it installs, but FC's on start.
logcat...
I/ActivityManager( 387): Starting: Intent { act=android.intent.action.MAIN cat=
[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.sec.android.app.ve/.ac
tivity.ProjectListActivity } from pid 1141
D/PhoneWindow( 1141): couldn't save which view has focus because the focused vie
w [email protected] has no id.
I/ActivityManager( 387): Start proc com.sec.android.app.ve for activity com.sec
.android.app.ve/.activity.ProjectListActivity: pid=1551 uid=1000 gids={3002, 300
1, 1015, 1001, 1006, 3003, 2001}
I/Zygote ( 1551): Zygote: pid 1551 has CALL PRIVILEGED permission, then set cap
ability for CAP_SYS_ADMIN (21)
I/WindowManagerService( 387): Setting rotation to 1, animFlags=1
I/ActivityManager( 387): Config changed: { scale=1.0 imsi=310/120 loc=en_US tou
ch=3 keys=2/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=15 FlipFont=0}
D/PhoneApp( 486): updateProximitySensorMode: state = IDLE
D/PhoneApp( 486): updateProximitySensorMode: lock already released.
I/dalvikvm( 1551): Could not find method com.android.internal.telephony.ITelepho
ny.isVoIPDialing, referenced from method com.sec.android.app.ve.util.Utils.isVOI
PActivated
W/dalvikvm( 1551): VFY: unable to resolve interface method 493: Lcom/android/int
ernal/telephony/ITelephony;.isVoIPDialing ()Z
D/dalvikvm( 1551): VFY: replacing opcode 0x72 at 0x000a
D/dalvikvm( 1551): VFY: dead code 0x000d-001b in Lcom/sec/android/app/ve/util/Ut
ils;.isVOIPActivated ()Z
D/VideoEditorApp( 1551): Space:::/mnt/sdcard 1123180544
W/dalvikvm( 1551): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initi
alizing Lcom/samsung/app/video/editor/external/NativeInterface;
D/AndroidRuntime( 1551): Shutting down VM
W/dalvikvm( 1551): threadid=1: thread exiting with uncaught exception (group=0x4
0015578)
E/AndroidRuntime( 1551): FATAL EXCEPTION: main
E/AndroidRuntime( 1551): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1551): at com.sec.android.app.ve.activity.ProjectListAc
tivity.onCreate(ProjectListActivity.java:497)
E/AndroidRuntime( 1551): at android.app.Instrumentation.callActivityOnCre
ate(Instrumentation.java:1047)
E/AndroidRuntime( 1551): at android.app.ActivityThread.performLaunchActiv
ity(ActivityThread.java:1615)
E/AndroidRuntime( 1551): at android.app.ActivityThread.handleLaunchActivi
ty(ActivityThread.java:1667)
E/AndroidRuntime( 1551): at android.app.ActivityThread.access$1500(Activi
tyThread.java:117)
E/AndroidRuntime( 1551): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:935)
E/AndroidRuntime( 1551): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 1551): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1551): at android.app.ActivityThread.main(ActivityThrea
d.java:3687)
E/AndroidRuntime( 1551): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 1551): at java.lang.reflect.Method.invoke(Method.java:5
07)
E/AndroidRuntime( 1551): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:842)
E/AndroidRuntime( 1551): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:600)
E/AndroidRuntime( 1551): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1551): Caused by: java.lang.UnsatisfiedLinkError: Couldn't loa
d videieditor: findLibrary returned null
E/AndroidRuntime( 1551): at java.lang.Runtime.loadLibrary(Runtime.java:42
9)
E/AndroidRuntime( 1551): at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 1551): at com.samsung.app.video.editor.external.NativeI
nterface.<clinit>(NativeInterface.java:53)
E/AndroidRuntime( 1551): ... 14 more
E/ ( 387): Dumpstate > /data/log/dumpstate_app_error
W/ActivityManager( 387): Force finishing activity com.sec.android.app.ve/.act
ivity.ProjectListActivity
I/WindowManagerService( 387): Setting rotation to 0, animFlags=1
I/dumpstate( 1561): begin
W/ActivityManager( 387): Activity pause timeout for HistoryRecord{40858180 com.
sec.android.app.ve/.activity.ProjectListActivity}
D/BatteryService( 387): update start
D/BatteryService( 387): updateBattery level:44 scale:100 status:2 health:2 pres
ent:true voltage: 3803 temperature: 270 technology: Li-ion AC powered:false USB
powered:true icon:17302217
W/su ( 1569): request rejected (0->0 /system/bin/sh)
E/VoldCmdListener( 67): asec list
W/SurfaceFlinger( 387): timeout expired mFreezeDisplay=1, mFreezeCount=0
I/dumpstate( 1561): done
I/ActivityManager( 387): Config changed: { scale=1.0 imsi=310/120 loc=en_US tou
ch=3 keys=2/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=16 FlipFont=0}
D/PhoneApp( 486): updateProximitySensorMode: state = IDLE
D/PhoneApp( 486): updateProximitySensorMode: lock already released.
W/WindowManagerService( 387): Window freeze timeout expired.
W/WindowManagerService( 387): Force clearing orientation change: Window{4094bd5
8 StatusBar paused=false}
W/WindowManagerService( 387): Force clearing orientation change: Window{407bb4e
8 StatusBarExpanded paused=false}
V/NotificationService( 387): notification manager receiver action = android.int
ent.action.BATTERY_CHANGED
I/StatusBarPolicy( 467): BAT. S:2 H:2
D/SyncmlService( 486): mBatteryReceiver: action - android.intent.action.BATTERY
_CHANGED
W/PowerManagerService( 387): Timer 0x7->0x3|0x0
I/PowerManagerService( 387): Ulight 7->3|0
D/PowerManagerService( 387): updateLightsLocked: onMask=0 offMask=4 dimMask=0
D/LightsService( 387): BUTTON : 0
I/InputReader( 387): dispatchTouch::touch event's action is 0
I/InputDispatcher( 387): Delivering touch to current input target: action: 0, c
hannel '40876200 Sorry! (server)'
I/PowerManagerService( 387): Ulight 3->7|0
D/PowerManagerService( 387): updateLightsLocked: onMask=4 offMask=0 dimMask=0
D/LightsService( 387): BUTTON : 30
I/InputReader( 387): dispatchTouch::touch event's action is 1
I/InputDispatcher( 387): Delivering touch to current input target: action: 1, c
hannel '40876200 Sorry! (server)'
D/dalvikvm( 387): GC_EXPLICIT freed 405K, 41% free 7376K/12295K, external 4034K
/4541K, paused 107ms
I/Process ( 1551): Sending signal. PID: 1551 SIG: 9
W/InputManagerService( 387): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 387): Process com.sec.android.app.ve (pid 1551) has died.
D/BatteryService( 387): update start
D/BatteryService( 387): updateBattery level:45 scale:100 status:2 health:2 pres
ent:true voltage: 3843 temperature: 270 technology: Li-ion AC powered:false USB
powered:true icon:17302217
V/NotificationService( 387): notification manager receiver action = android.int
ent.action.BATTERY_CHANGED
I/StatusBarPolicy( 467): BAT. S:2 H:2
D/SyncmlService( 486): mBatteryReceiver: action - android.intent.action.BATTERY
_CHANGED
D/dalvikvm( 417): GC_CONCURRENT freed 501K, 51% free 2846K/5767K, external 1596
K/2108K, paused 2ms+2ms
W/PowerManagerService( 387): Timer 0x7->0x3|0x0
I/PowerManagerService( 387): Ulight 7->3|0
D/PowerManagerService( 387): updateLightsLocked: onMask=0 offMask=4 dimMask=0
D/LightsService( 387): BUTTON : 0
W/ActivityManager( 387): Activity destroy timeout for HistoryRecord{40858180 co
m.sec.android.app.ve/.activity.ProjectListActivity}
Click to expand...
Click to collapse

Damn I really want it
Sent from my SPH-D700 using XDA Premium App

Even when I push this is doesnt show in my app drawer

I believe it relies on the Touchwiz 4 framework.
Sent from my Epic 4G

Is there anyway to get tw4 so it works?
Sent from my SPH-D700 using XDA Premium App

musikalharmony said:
Is there anyway to get tw4 so it works?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Ummm perhaps? We've a post with the framework.jar files but the work put into that I'd be unsure of. Hard or simple I'm unaware.
Sent from my Epic 4G

AproSamurai said:
Ummm perhaps? We've a post with the framework.jar files but the work put into that I'd be unsure of. Hard or simple I'm unaware.
Sent from my Epic 4G
Click to expand...
Click to collapse
Acer just released a TW4 theme ported from the Epic Touch. The the reliable widgets work so maybe the apk will. I could be totally wrong but it's worth a try. I I will give it a go in the morning
Sent from my SPH-D700 using xda premium

JohnCorleone said:
Acer just released a TW4 theme ported from the Epic Touch. The the reliable widgets work so maybe the apk will. I could be totally wrong but it's worth a try. I I will give it a go in the morning
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Ahh yeah, I saw I wish I was still on EC05 to mess with it. Maddogin said he was going to add some TW4 elements to his mod, although I wish I knew what that entailed exactly. Thanks for all the testing you've done man, it's beyond appreciated.

looks like its missing some framework jars..

Any way to enable/port Camera3D, 3D Album or Swipe Panorama on Xperia Play?

That's my question, I tried all the ports/apps/mods in the forum but without success.
3D Album works without problems and integrates to the stock gallery
Camera3D says "Camera no available" and FC
Sweep Panorama (Sony Panorama Beta) works and open the camera. Even the flash works, but after I stop the shooting, it doen't save the picture. It says "Could not save. Pan the phone in the direction you selected with the arrow button"
Any way to port the apps? I read that Sweep Panorama doesn't work properly because it was make for gingerbread 2.1 and actually have some issues with 2.3+
Please help me! I saw all the threads and I have no success
Maybe I missed some libs or dependencies, I only installed a script from here:
http://forum.xda-developers.com/showthread.php?t=1134048
It has a framework file and its permission to make the app "work". Any suggestions or clues?
--- 91 views and no answers ---

its not made for Xperia play ....
and about the porting....
its only made for some phones
sorry ..

But it's because hardware compatibilities or what?
Because it supposed to support any ARMv7 NEON CPU, and de Xplay has it.

yeah thats true but it you have to install a apk !
And that apk is only for the phones listed...

I have the apks, the jar and permission I need, I installed it and works partially. Camera 3d FC, 3D Album fully works and Panorama Beta works but doesn't save the picture.

sorry i cant help you any further then ....
Try PM'ing the guy behind the fix ?

I'll try, but actually I'm decompiling the apks in a try to port them... thanks anyways

UPDATE
I installed catlog and I have some clues with Panorama BETA
07-08 04:08:30.879 D/VoldCmdListener(152): asec path com.sonyericsson.panorama-1
07-08 04:08:32.849 D/VoldCmdListener(152): asec mount com.sonyericsson.panorama-1 {} 1000
07-08 04:08:32.899 D/VoldCmdListener(152): asec path com.sonyericsson.panorama-1
07-08 04:13:13.485 I/ActivityManager(677): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.sonyericsson.panorama/.PanoramaCameraActivity bnds=[14,631][127,763] } from pid 1707
07-08 04:13:13.585 I/ActivityManager(677): Start proc com.sonyericsson.panorama for activity com.sonyericsson.panorama/.PanoramaCameraActivity: pid=3215 uid=10225 gids={1006, 1015, 3003}
07-08 04:13:14.695 D/dalvikvm(3215): Trying to load lib /mnt/asec/com.sonyericsson.panorama-1/lib/libGmvPanoramaAndroid.so 0x2abf3ad8
07-08 04:13:14.695 D/dalvikvm(3215): Added shared lib /mnt/asec/com.sonyericsson.panorama-1/lib/libGmvPanoramaAndroid.so 0x2abf3ad8
07-08 04:13:14.705 D/dalvikvm(3215): No JNI_OnLoad found in /mnt/asec/com.sonyericsson.panorama-1/lib/libGmvPanoramaAndroid.so 0x2abf3ad8, skipping init
07-08 04:13:16.049 I/ActivityManager(677): Displayed com.sonyericsson.panorama/.PanoramaCameraActivity: +2s463ms
07-08 04:13:29.665 E/com.sonyericsson.panorama.states.IdleState(3215): Action not supported: onStopped Parameters: [null - null ]
07-08 04:13:30.669 D/dalvikvm(3215): Trying to load lib /mnt/asec/com.sonyericsson.panorama-1/lib/libGmvPanoramaAndroid.so 0x2abf3ad8
07-08 04:13:30.669 D/dalvikvm(3215): Shared lib '/mnt/asec/com.sonyericsson.panorama-1/lib/libGmvPanoramaAndroid.so' already loaded in same CL 0x2abf3ad8
07-08 04:13:34.815 E/com.sonyericsson.panorama.states.IdleState(3215): Action not supported: onStopped Parameters: [null - null ]
07-08 04:13:35.325 W/ActivityManager(677): Activity pause timeout for HistoryRecord{2b3ee4d8 com.sonyericsson.panorama/.PanoramaCameraActivity}
07-08 04:13:46.835 I/ActivityManager(677): Process com.sonyericsson.panorama (pid 3215) has died.
07-08 04:13:46.845 W/kernel (177): select 3215 (icsson.panorama), adj 10, size 7187, to kill
07-08 04:13:46.845 W/kernel (177): send sigkill to 3215 (icsson.panorama), adj 10, size 7187
The first red one was when I started to capture and the last red one when I finished.
Missing libraries? Hardware support?

Please help me I want this app so bad and I'm still too noob to make a fix

vicl89 said:
snip
07-08 04:13:29.665 E/com.sonyericsson.panorama.states.IdleState(3215): Action not supported: onStopped Parameters: [null - null ]
Snip
Missing libraries? Hardware support?
Click to expand...
Click to collapse
no hardware support, same with 3d camera.
Pax
Sent from my R800x using Tapatalk 2

Thanks!
Thank you so much!!... in that case it's impossible to port this app on Xplay because of hardware. Well, if nobody have any comment to do, please close this thread
Thanks again

Hey Pax, sorry for bumping, I know that it's against the rules, but please see this thread:
http://forum.xda-developers.com/showthread.php?t=1430230&highlight=cm7+apps
Why is working well on CM7 ROM and fail in stock?
Maybe isn't the hardware support issue, it could be a missing library that CM7 have.
Could someone please give me a logcat with the activities of Panorama Beta from CM7 ROM?

[DEV-WIP] MIC testing (To enable GoogleNow function in JB)

NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs

times_infinity said:
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs
Click to expand...
Click to collapse
Yeah you're right .
Envoyé depuis mon GT-I9000 avec Tapatalk

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T

webdroidmt said:
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T
Click to expand...
Click to collapse
Nice catch!

I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.

You guys could try (sp?)Meltus as well...the Volume+ guy.
Sent from my Galaxy Nexus using xda app-developers app

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Even if the mic isn't the issue I would still like to see this implemented this would let many more apps function like shazam, voice typing and of course voice search...
Sent from my Amazon Kindle Fire using xda premium

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
{removed}
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
No ALSA experience other than ticking a box or two on my Puppy Linux install - sure wish I did.
This needs to be nailed down for Jelly Bean to work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hashcode said:
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.
Click to expand...
Click to collapse
This is purely speculation, but did the other stacktrace come from the 7/11 build? Maybe your half-fix for Wi-Fi location actually broke things, and we actually have TWO blockers here. We won't know for sure until you get location working all the way though.

BUMP
Sent from my PC36100 using xda premium

Alsa mixer keeps installing
I had no luck trying to experiment with alsa mixer sound variables - I installed it from store successfully, but anytime I leave alsa mixer in a way to check is external mic working with some recording app, when I come back to alsa mixer it demands to be again installed. Someone went further with alsa mixer on Kindle JB?

No luck
I've tested it as well but without luck!.
Hoping it works in the near future...

any one here
hope this will work

minhchick said:
any one here
hope this will work
Click to expand...
Click to collapse
Seems it won't.

BrooklynNY said:
Seems it won't.
Click to expand...
Click to collapse
I wouldnt hold my breath...

Hashcode said:
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Click to expand...
Click to collapse
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.

stylon said:
Hi Hash, I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did: tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16......
Click to expand...
Click to collapse
Can it be done with this ROM?

stylon said:
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.
Click to expand...
Click to collapse
I'm not sure hashcode follows this thread anymore...you may want to PM him or try him on another thread
Sent from my GT-N7000 using Tapatalk 2

[Q] Ingress (Niantic Project) on Kindle Fire MoDaCo Gr9 (6.3.1)

Does anyone know why the Niantic Labs app Ingress (V1.00.0) will not work on the Kindle Fire 1st gen with MoDaCo Gr9 [ROM]? After selecting an account, it goes to the v1.00.0 splash screen and then flashes the SCAN screen before force closing.
The Niantic Labs app Field Guide (V1.06) works fine and they have the same version requirements and similar permission requirements. I do see that version 1.06 of Field Guides had the following update: "Fixed crashes for selected devices." Surely they wouldn't release the initial version of ingress with the same issue?

It looks like it may be an issue with the lack of gps. I was hoping this wasn't the case since gr9 enables coarse location based on the network. The Field Trip app works perfectly fine using the coarse network location but perhaps Ingress doesn't like this?
A portion of the logcat is attached as log3.txt. If this log is missing some important pieces, let me know and I can attach more.
Here are some incriminating snippets: (see the attachment for more)
E/AndroidRuntime( 7381): FATAL EXCEPTION: LocationTracker
E/AndroidRuntime( 7381): java.lang.IllegalArgumentException: provider=gps
"E/AndroidRuntime( 7381): at android.os.Parcel.readException(Parcel.java:1326)"
"E/AndroidRuntime( 7381): at android.os.Parcel.readException(Parcel.java:1276)"
"E/AndroidRuntime( 7381): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)"
"E/AndroidRuntime( 7381): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:582)"
"E/AndroidRuntime( 7381): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:446)"
"E/AndroidRuntime( 7381): at com.niantic.nemesis.sensors.c.c(SourceFile:40)"
"E/AndroidRuntime( 7381): at com.niantic.nemesis.sensors.f.run(SourceFile:255)"
"E/AndroidRuntime( 7381): at android.os.Handler.handleCallback(Handler.java:587)"
"E/AndroidRuntime( 7381): at android.os.Handler.dispatchMessage(Handler.java:92)"
"E/AndroidRuntime( 7381): at android.os.Looper.loop(Looper.java:130)"
"E/AndroidRuntime( 7381): at android.os.HandlerThread.run(HandlerThread.java:60)"
W/ActivityManager( 1395): Force finishing activity com.nianticproject.ingress/com.niantic.nemesis.NemesisActivity
I/AndroidComm( 7381): onLoadFinished
Click to expand...
Click to collapse
Feel free to elaborate if you guys know of a solution or work-around (without trying to tether a gps from another android device... I don't have one).
(Ps: I would love for this to be in the "Amazon Kindle Fire > Kindle Fire Android Development > [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire" thread but, alas, I do not have 10 posts.)

Ummm yeah, there's no GPS on the Kindle Fire. It's missing a lot of sensors.. It's a eBook reader. Even if root/hacked/ROMd

icebrkr said:
Ummm yeah, there's no GPS on the Kindle Fire. It's missing a lot of sensors.. It's a eBook reader. Even if root/hacked/ROMd
Click to expand...
Click to collapse
I'm well aware of this. I was wondering if anyone had any success getting it to work with coarse network location identification, alone.

anywhose said:
I'm well aware of this. I was wondering if anyone had any success getting it to work with coarse network location identification, alone.
Click to expand...
Click to collapse
So I don't know if you are saying it crashes or doesn't work, but I am running twa_priv's cm10 jellybean ROM, and I installed the app. When I launched it, it opened fine, but since I didn't (and still don't) have the acces code to participate yet, I can't tell you if it doesn't work or not. Does google Maps work for you? it works on the ROM I am running. More specifically, the location part of Google Maps...

jma9454 said:
So I don't know if you are saying it crashes or doesn't work, but I am running twa_priv's cm10 jellybean ROM, and I installed the app. When I launched it, it opened fine, but since I didn't (and still don't) have the acces code to participate yet, I can't tell you if it doesn't work or not. Does google Maps work for you? it works on the ROM I am running. More specifically, the location part of Google Maps...
Click to expand...
Click to collapse
The location part of Google Maps works fine and so does the Field Trip app by niantic projects. I mention the Field Trip app because it also seeks a gps signal but when it does not detect gps hardware, it uses the coarse network location.
For me, the app works fine until you enter the access code. At this point, it tries to locate your position and force crashes.

Google Now Voice Search kills Voice Search Systemwide

Hi all,
i've got an odd issue and wonder if somebody else has this.
I'm on pabx' AOSP ROM rc19.
When using Voice Search in Google Now it works the first time. After switching to another app and returning Voice Search fails with something like "Could not be understood". It fails immediately and doesn't even try to record anything.
PLUS: at this point voice recording fails in any app (e.g android voice input / swiftkey, what so ever).
when i force kill Google Search App, everything works again. so this somehow seems to block voice input.
maybe someone can reproduce this..
here's my logcat..
Code:
W/AudioFlinger( 193): findSuitableHwDev_l() loading well know audio hw modules
W/AudioFlinger( 193): loadHwModule() module primary already loaded
W/AudioFlinger( 193): loadHwModule() module a2dp already loaded
E/AudioFlinger( 193): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 193): loadHwModule() error -2 loading module usb
E/AudioRecord(10035): Could not get audio input for record source 6
E/AudioRecord-JNI(10035): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java(10035): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
D/dalvikvm(10035): GC_FOR_ALLOC freed 455K, 16% free 15471K/18248K, paused 28ms, total 28ms
I/dalvikvm-heap(10035): Grow heap (frag case) to 15.439MB for 320016-byte allocation
D/dalvikvm(10035): GC_FOR_ALLOC freed 7K, 16% free 15776K/18564K, paused 27ms, total 27ms
I/AudioService( 576): AudioFocus requestAudioFocus() from [email protected][email protected]
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(10035): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
I/VS.G3EngineManager(10035): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 3 ms
I/decoder (10035): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err(10035): java.io.IOException: AudioRecord failed to initialize.
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
W/System.err(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err(10035): at java.io.InputStream.read(InputStream.java:163)
W/System.err(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
D/dalvikvm(10035): threadid=49: thread exiting, not yet detached (count=0)
E/VS.G3EngineManager(10035): Error running recognition: 3
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/AudioService( 576): AudioFocus abandonAudioFocus() from [email protected][email protected]
E/UberRecognizerController(10035): onError
E/UberRecognizerController(10035): com.google.android.speech.exception.AudioRecognizeException: Audio error
E/UberRecognizerController(10035): at com.google.android.speech.embedded.Greco3Recognizer.read(Greco3Recognizer.java:98)
E/UberRecognizerController(10035): at dalvik.system.NativeStart.run(Native Method)
E/UberRecognizerController(10035): Caused by: java.io.IOException: AudioRecord failed to initialize.
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
E/UberRecognizerController(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
E/UberRecognizerController(10035): at java.io.InputStream.read(InputStream.java:163)
E/UberRecognizerController(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
E/UberRecognizerController(10035): Got error after recognizing []

I had exactly the same thing few weeks ago on a number of roms, couldn't get a fix so just settled on a rom that didn't have the issue
Sent from my HTC One X using xda premium

Thanks for your reply.
can you tell me on which roms you experienced the issue and on which it does not occur?
on AOKP it doesn't work either.
Sense ROMs seem to be working..
I also sent a feedback report to google but i don't think there will be any response.

It worked on sense ROMs but I don't like them, most aokp and aosp ROMs had the the problem but for some reason it works fine on xenonhd and slimbean. I like slim so I just stuck with it
Sent from my HTC One X using xda premium

I digged in a little bit deeper and it's really odd.
on the first launch google now initializes in my local language:
Code:
I/VS.G3EngineManager(23710): create_rm: m=ENDPOINTER_VOICESEARCH,l=de-DE
I/VS.G3EngineManager(23710): Brought up new g3 instance :/data/data/com.google.android.googlequicksearchbox/app_g3_models/de-DE/endpointer_voicesearch.config for: de-DEin: 34 ms
which works.
after returning it tries to bring up
Code:
I/VS.G3EngineManager(30287): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
W/Search.ConcurrentUtils(30287): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(30287): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 2 ms
I/decoder (30287): ERROR: Exception thrown from GoogleRecognizer.read()
which than fails.
when setting the system language to english it works all the time.
Do you still use a different language than EN_US on SlimBean (I suppose you did) ? or might that be the reason it is working on Slim ?

Phone and search are set to eng UK. Just tried changing to eng generic on Google now and the problem returns, changed back to eng UK and still problem then cleared app cache in system setting and all is fine again. So looks like you found something, good job
Sent from my HTC One X using xda premium

thanks for trying.
would be awesome if someone with a sense rom could try as well.
But i guess it will be an AOSP / 4.2.2 issue only.
maybe one of the dev's can have a look into it.. would be awesome to get this one figured out.

seems like the latest google search / now update solved the problem for me.
maybe you can confirm !?