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
Related
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..
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.
So, my good pal freeza found this one. I am merely posting it. We are working on getting it enabled by porting some code over from the galaxy note 2 (if it exists)... but for now, you can see the hidden setting in settings>more settings>"auto power on/off" by adding this line of code here to the very end of your /system/csc/feature.xml file:
</SamsungMobileFeature>
<CscFeature_Clock_ExclusiveEnablingAutoPowerSetting>true
</CscFeature_Clock_ExclusiveEnablingAutoPowerSetting>
(make sure you leave one extra blank line at the end)
you can add these lines using a file explorer that is able to edit system file's text..
after you add this feature, and save it, reboot.
what does this feature do? you can basically set a time interval for your phone to shut off and on automatically. pretty slick.
the trick is, when we were playing around with this, tried to enable it, and it force closes the settings app... I ran a logcat and it showed the classes.dex was not found. boooooo... but looking into and I will keep you guys posted. I have a note 2 rom downloaded right now and so does freeza. cross your fingers, because this is an awesome extra setting!!!
hats off to freeza for finding this.... because when he gets bored he decompiles apks and looks for cool ***t... lol
here is a screenshot of the setting
Nice effin find!!!
Sent from my SGH-T999 using xda premium
Great find dev
Sent from my SGH-T999 using xda premium
agreed! the man is a boss
as i said, we are both investigating this further as we speak (type.. )
Edit** didn't realise I copied an extra line from my feature.xml file.. the "samsung mobile feature" (the first line) does not need to be added because it is already there at the end of your file
AOKP has this already I love it! Good to see it available for a stock Rom.
This doesn't work for me on Frosty v11..any ideas why? I also tried pasting the lines under the settings heading in the feature.xml file but that had no effect also..
Adds option ... But crashes
WarlockW said:
Adds option ... But crashes
Click to expand...
Click to collapse
right. this:
12-04 21:41:49.433 E/AndroidRuntime( 4685): Caused by: android.app.Fragment$InstantiationException: Unable to instantiate fragment com.android.settings.autopoweronoff.AutoPowerOnOffSettings: make sure class name exists, is public, and has an empty constructor that is public
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Fragment.instantiate(Fragment.java:584)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.switchToHeaderInner(PreferenceActivity.java:1222)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.switchToHeader(PreferenceActivity.java:1238)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.onCreate(PreferenceActivity.java:611)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at com.android.settings.Settings.onCreate(Settings.java:185)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Activity.performCreate(Activity.java:5048)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2052)
12-04 21:41:49.433 E/AndroidRuntime( 4685): ... 11 more
12-04 21:41:49.433 E/AndroidRuntime( 4685): Caused by: java.lang.ClassNotFoundException: com.android.settings.autopoweronoff.AutoPowerOnOffSettings
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 !?
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This thread is for build questions. See other thread for general info, reports of bugs etc.
NOTE: Be sure to read post #2 in this thread as it contains important info on non-T-Mobile devices, how to build this yourself, and more
The code is now being opened up for community development. Fattire has some instructions below to help you build. Just note the code is still under heavy development and will be changing often.
Just for clarification, myself and fattire are NOT paid employees of Cyngn INC. This is our hobby, and our free time to make this work.
Download
See Official CM-12.0 for Note 4 Thread, go here download.cyanogenmod.org
Also, follow us if you like. We're on the Twitter!
Slayher
fattire
↓↓↓↓↓ Don't forget to read the next post for the CHANGELOG, tips, and info on building this yourself ↓↓↓↓↓
XDA:DevDB Information
CM-12.0 for Tmobile Note 4, ROM for the T-Mobile Samsung Galaxy Note 4
Contributors
slayher, fattire
Source Code: http://github.com/slayher
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-12-07
Last Updated 2015-01-26
I also have to give a big thanks to @fattire for his assistance in getting this up and running.
Click to expand...
Click to collapse
It has been a ton of fun!!! This is my first samsung device and I think we got pretty far in something like 10 days 3 weeks (time flies)
IRC
You *might* find some people hanging out on freenode in #cm-note4. Don't know what that means? No worries, here's a link you can use.
DON'T HAVE T-MOBILE?
That's okay. While the major porting work to the Note 4 is being done by people with TMO, there are threads pertaining to other variants (who work off the T-Mobile version). You can find them here. If your particular device isn't here, start a new device repository for your flavor of the Note 4 and then start a new thread!
Sprint thread (SM-910P). Slayher has started a new repository specifically for sprint users here.
International "EU" thread (SM-910F)
LET THE GAMES BEGIN!
RECENT CHANGES
Official CM nightlies are coming very soon. The latest few releases from Slayher above have last-minute fixes (to audio, bluetooth, battery, etc.) to prepare for the nightly builds... read the last few posts for details.
CHANGES IN 1-20-15 BUILD
Battery Improvements
Audio Updates.
Settings FC's are fixed.
A few other upstream changes.
CHANGES IN 1-18-15 BUILD
More Audio enhancements
Fixes and Cleanups in the init scripts
Kernel adjustments, including disabling the UV and FP sensors
And hopefully some power draw improvements.
FIXED IN 1-9-15 BUILD
Selinux is setup, and fully functional. I have not enforced yet, but it should be good to go.
Revamped the hardware backed keystore system.
UHD (4K) Now working in the Normal Camera APK as well as Google Camera.
The audio stack is now sharing the same HAL as the msm8974.
. Attempted to raise recording Volume. Lets see what happens.
Changed the default DPI to 560. Its better than 640, not as extreme as 515, and its a fully supported DPI in Google Play store.
Upstream CM changes effected normal root access. If you dirty flash, your current root stuff should stay. If you clean wipe you have to enable root in development settings.
Updated the Lockscreen Notification config. Now when the notification comes in, you can interact with the black and white "Ambient Display". It still does not turn on the display when you pick the device up, or remove it from a pocket.
Now you may ask, "What does all this mean?" Well it means that the device tree should be at a point to merged in to CM mainline code, which means..... NIGHTLIES and M-Releases!
FIXED (etc.) IN 1-1-15 BUILD
hefty changes to the power hal system (better battery)
changes to audio HAL and Kernel audio drivers.
Music playback after a resume from pause should be fixed.
Performance profiles are back, and set to "Balanced" The other 2 options are Performance and Power Save.
If you buy the App Cinema FV-5 you will be able to record video in UHD/4k. (stock camera not fixed yet)
More fixes and features from mainline CM12.
FIXED (we think) IN 12-30-14 BUILD
Time service (finally?) fixed (??)
keystore stuff fixed (hardware-backed)
cpu settings fixed
A ton of new stuff forward-ported upstream from CM11->CM12.
BTW you may have to forget and reconnect wifi networks, BT stuff etc, cause of the new crypto routine
FIXED (we think) IN 12-28-14 BUILD
Near-field communication (NFC)
LED color/blink pattern customization (in Settings->Sound & Notification)
SmartCover sleep/wake on open/closing cover
Stylus cursor replaced with new circley-one
Time service (we THINK.. time will tell on this one-- no that is not a pun)
Audio volume reversal now fixed
Many fixes from mainline CM since last time.
FIXED (we think) IN 12-20-14 BUILD
DRM Video (Google Movies, Netflix, etc.) works
Blank screen on some banking apps fixed
MPEG-DASH player
Stylus orientation bug fixed
capacitive buttons works with stylus
p2p fixed
wifi direct works
MMS bug fixed for native MMS app
menu item should appear now in many apps
Simcard Toolkit enabled
Random crash that caused reboots appears to be fixed
Android 5.0.2 merged (because...)
Tons of upstream CM-12 improvements
FIXED (we think) IN 12-11-14 BUILD
Capacitive screen can now be disabled/replaced by soft keys (Settings->Buttons)
SD card/MTP issues fixed (hopefully)
Play Store works w/apps you want.
offmode charging
IR mostly works apparently (I can't test this as I don't have a thing.)
Hangouts now does video/audio chat
NFC shut off (to preserve battery-- wont' keep trying to start)
LOTS of goodness from upstream CM.
You may need to wipe caches, clear settings in the play store and/or wipe /data if nothing else works. Don't come and complain in the thread until you've tried these steps.
OVERALL LIST OF STUFF THAT SEEMS TO WORK
screen w/accelerated graphics
sleep and return from sleep
touchscreen multitouch
panel backlight (adaptive brightness)
audio
SmartCover support
headphone jack detection/playing/buttons
s-pen as mouse (w/ pressure data)
wifi
Camera (front and back)
SD card and internal storage and MTP
voice calls
LED lights (in correct colors)
A ton more sensors (accelerometer/light sensor/proximity/gyroscope/sound/magnetic/pressure) work.
vol/power/capacitive buttons + button backlight
Torch
Mobile data
MMS/SMS
Vibrator (with adjustable intensity)
Video (w/o DRM) works w/sound & rotates correctly. Youtube, etc.
screenshots/screenrecord
GPS
IR
Hangouts video chat
Bluetooth pairing/audio
wireless charging
Play store compatibility
turn off capacitive buttons feature
DRM Video (Google Movies, Netflix, etc.) works
Secure apps
MPEG DASH
p2p/wifi direct
Simcard Toolkit
NFC
UHD (4k) video
hardware-backed encryption
selinux: enforcing
much much more!
In the TODO column still
???
MIGHT GET TO SOMEDAY
fingerprint sensor (There is undocumented support for it in Android 5.0 but no UI in the Settings app to enter your fingerprints. So I think someone would need to write one, if someone hasn't already. Here is the HAL component)
pop s-pen in-out [should it do something special? Let us know what you think...]
UNLIKELY TO EVER WORK (but who knows)
TMobile wifi calling
Samsung-specific magic
touchwiz
THINGS OF INTEREST
User @bttfpromo says you can return the stock cursor (instead of the mouse pointer) with these instructions.
User @DragonAndLance posted a link to boost the in-call sound for those who feel that the defaults aren't high enough.
If you don't like the default screen density, @slayher points out that the following adb command will change it: adb shell wm density 515. I prefer smaller icons (which actually match the physical size of a Nexus 5). Note that these changes will "stick" to the next boot.
Want handwriting recognition? Try the Stylus beta -- a handwriting keyboard similar to the one in TouchWiz.
A terrific demo of the pressure sensitivity of the S-pen stylus is Markers-- it's open source too!
If you need something special to happen when you pop the pen in and out (or press the button), check out this app.
TO BUILD YOURSELF
Building CyanogenMod yourself? That's encouraged here. If you want to learn to build (and thus never have to bother weirdo strangers), you've come to the right place. Start reading about the building process on the wiki, and then join in on the fun.
There are specific step-by-step build instructions for Lollipop on the note 4 (TMO) right here (T-Mobile) and here (Sprint).
Please fix stuff and submit your code pull requests to Slayher's github! Muchas gracias!
wow glad to see CM here its early in the build im sure the bugs will be worked out
Good to go.
Nice ! But how to download source code ? On this link:
slayher said:
Source Code: http://github.com/slayher
Click to expand...
Click to collapse
I don't see any repo I can clone is that correct ? Thanks !
fattire said:
Note: Might want to hold off a few seconds on getting this as a fix to sdcard is coming... right now it shows up in Android but not in file manager and shell /sdcard etc until the fix gets checked in.
Slayher's uploading a fix now...
Click to expand...
Click to collapse
Thanks for the work you have done - been eagerly waiting for this - I knwo a lot is yet to be done - but thanks for all you guys have done so far..
Can you tell me .WHich Gapps are reccomended?
Unoffcial CM-12.0 for T-Mobile Note 4. (trltetmo)
I love u slayher and fattire. Lol. I've been waiting for this day.
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
By the way, I have an account on dev-host if you would like to use it to host your work. Just let me know
Dec 6 2014
fattire said:
Might want get checked in now...
Click to expand...
Click to collapse
T-Mobile Note 4 Owners Should Mark This Day...
Because.. This is the Day it all begins.
The Birth of CM has just arrived for the T-Mobile Samsung Galaxy Note 4 Family..
Congratulations! "Live Long.. And Prosper" :good:
My mobile data doesn't work. but for a first build it's pretty damn impressive.
Oh no Lord. I'm gonna party lol thanks.
Thanks for getting the Ball Rolling! :good:
Oh yeah let the games begin ??????! Very nice to see this & thank you man!
I had a feeling this was gonna happen soon; thanks so much for getting this started guys:good::good:
Thanks so much for this. So glad to have cyanogenmod and not touchwiz. Runs extremely well for me.
For those having issues connecting to WiFi, it seems as though it won't connect if a password is enabled. I configured my router to just use a mac address filter and removed the password to get it working.
Here is a guide for linksys routers: http://kb.linksys.com/Linksys/GetAr...ksys_Wireless_N_Router.xml&pid=80&converted=0
ChrisJ951 said:
Thanks so much for this. So glad to have cyanogenmod and not touchwiz. Runs extremely well for me.
For those having issues connecting to WiFi, it seems as though it won't connect if a password is enabled. I configured my router to just use a mac address filter and removed the password to get it working.
Here is a guide for linksys routers: http://kb.linksys.com/Linksys/GetAr...ksys_Wireless_N_Router.xml&pid=80&converted=0
Click to expand...
Click to collapse
That's interesting... I didn't have any such issue w/my router, which does have a password... actually I've set it up on 3 different routers-- so question, what kind of security settings does your router use?
Mine: WPA2 personal w/AES (possibly not as secure as it could be..) should probably use TKIP-AES but anyhoo
second question-- if you go to /data/misc/wifi/wpa_supplicant.conf you sohuld see some settings that look like this:
network={
ssid="My Router Name"
psk="donttellanyone"
key_mgmt=WPA-PSK
priority=132
}
Are you able to set it up manually by changing this file? Or does it still not work?
MAC address works too for now, but the more we know about the router, the easier it would be to fix...
Ya, I can't connect to my wifi. Haven't tried removing password. Don't feel like going through all that. Seems really smooth though
Great work man..
Don't forget that lollipop has WiFi connectivity issues with routers that have dashes (and spaces?) I believe in the network name. Its been reported on google bug tracker. Does yours have a dash in it by chance ChrisJ951? It affects me connecting to networks at work on the nexus 6.
Actually I just got my wifi working!! Went into advanced wifi menu and changed the Wi-Fi frequency band from auto to 2.4 GHz only
fattire said:
That's interesting... I didn't have any such issue w/my router, which does have a password... actually I've set it up on 3 different routers-- so question, what kind of security settings does your router use?
Mine: WPA2 personal w/AES (possibly not as secure as it could be..) should probably use TKIP-AES but anyhoo
second question-- if you go to /data/misc/wifi/wpa_supplicant.conf you sohuld see some settings that look like this:
network={
ssid="My Router Name"
psk="donttellanyone"
key_mgmt=WPA-PSK
priority=132
}
Are you able to set it up manually by changing this file? Or does it still not work?
MAC address works too for now, but the more we know about the router, the easier it would be to fix...
Click to expand...
Click to collapse
Was using WPA2 personal. Let me re-enable it and try modifying the file manually. Also I don't believe it's a lollipop issue as I have no issue connecting from a Nexus 6
EDIT: So re-enabling the password and it seems to work now. I had rebooted twice without success so I'm unsure of the exact reasoning why it was failing earlier? If it happens again I'll try to get more information on it. It used to immediately popup saying it failed to connect as soon as I entered the password.
2nd edit:
Here was an adb logcat back from when it was happening
Code:
D/DownloadManager( 946): [119] Starting
D/DownloadManager( 946): [119] Finished with status SUCCESS
E/SQLiteLog( 4016): (284) automatic index on sqlite_sq_AFFF7780(url)
D/DownloadManager( 946): [120] Starting
I/LatinIME( 1074): Starting input. Cursor position = 0,73
D/StatusBar.NetworkController( 920): refreshViews: Data not connected!! Set no data type icon / Roaming
D/DownloadManager( 946): [120] Finished with status SUCCESS
D/hardware_info( 369): hw_info_append_hw_type : device_name = speaker
I/art ( 784): Explicit concurrent mark sweep GC freed 21200(971KB) AllocSpace objects, 1(16KB) LOS objects, 29% free, 38MB/54MB, paused 1.105ms total 65.83
1ms
D/DownloadManager( 946): [121] Starting
D/DownloadManager( 946): [121] Finished with status SUCCESS
I/ActivityManager( 784): Killing 2925:com.google.android.gms.unstable/u0a19 (adj 15): empty #17
W/libprocessgroup( 784): failed to open /acct/uid_10019/pid_2925/cgroup.procs: No such file or directory
D/DownloadManager( 946): [122] Starting
E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again
D/DownloadManager( 946): [122] Finished with status SUCCESS
D/DownloadManager( 946): [123] Starting
D/StatusBar.NetworkController( 920): refreshViews: Data not connected!! Set no data type icon / Roaming
D/DownloadManager( 946): [123] Finished with status SUCCESS
I/art ( 946): Explicit concurrent mark sweep GC freed 41968(2MB) AllocSpace objects, 0(0B) LOS objects, 24% free, 18MB/25MB, paused 549us total 38.970ms
D/DownloadManager( 946): [124] Starting
I/Timeline( 4016): Timeline: Activity_launch_request id:com.google.android.googlequicksearchbox time:665124
I/ActivityManager( 784): START u0 {act=android.intent.action.WEB_SEARCH cat=[android.intent.category.DEFAULT] cmp=com.google.android.googlequicksearchbox/com.g
oogle.android.search.core.google.GoogleSearch (has extras)} from uid 10028 on display 0
W/IInputConnectionWrapper( 4016): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper( 4016): getTextBeforeCursor on inactive InputConnection
D/WebViewTimersControl( 4016): onBrowserActivityPause
D/WebViewTimersControl( 4016): Pausing webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,1225}
E/RichInputConnection( 1074): Unable to connect to the editor to retrieve text.
D/RichInputConnection( 1074): Will try to retrieve text later.
I/QSB.GoogleSearch( 4431): Got intent: #Intent;action=android.intent.action.WEB_SEARCH;category=android.intent.category.DEFAULT;launchFlags=0x800000;component=c
om.google.android.googlequicksearchbox/com.google.android.search.core.google.GoogleSearch;S.com.android.browser.application_id=com.android.browser;S.query=reddi
t;end
W/LocationOracleImpl( 4431): Best location was null
W/IInputConnectionWrapper( 4016): getTextBeforeCursor on inactive InputConnection
E/RichInputConnection( 1074): Unable to connect to the editor to retrieve text.
W/RichInputConnection( 1074): Unable to connect to the editor. Setting caps mode without knowing text.
I/ActivityManager( 784): START u0 {act=android.intent.action.VIEW dat=https://www.google.com/search?redir_esc=&client=ms-android-google&hl=en-US&safe=images&oe
=utf-8&q=reddit&source=android-browser-type&qsubts=1417921621917 flg=0x10000000 pkg=com.android.browser cmp=com.android.browser/.BrowserActivity (has extras)} f
rom uid 10028 on display 0
W/ActivityManager( 784): Duplicate finish request for ActivityRecord{37917e3f u0 com.google.android.googlequicksearchbox/com.google.android.search.core.google.
GoogleSearch t16 f}
W/InputMethodManagerService( 784): Window already focused, ignoring focus gain of: [email protected] attribute=n
ull, token = [email protected]
D/WebViewTimersControl( 4016): onBrowserActivityResume
D/WebViewTimersControl( 4016): Resuming webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,1225}
I/Timeline( 4016): Timeline: Activity_idle id: [email protected] time:665287
I/art ( 784): Explicit concurrent mark sweep GC freed 16627(695KB) AllocSpace objects, 3(4MB) LOS objects, 30% free, 36MB/52MB, paused 1.041ms total 73.512
ms
D/DownloadManager( 946): [124] Finished with status SUCCESS
D/DownloadManager( 946): [125] Starting
D/DownloadManager( 946): [125] Finished with status SUCCESS
D/DownloadManager( 946): [126] Starting
D/DownloadManager( 946): [126] Finished with status SUCCESS
I/ActivityManager( 784): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/com.android.l
auncher3.Launcher} from uid 1000 on display 0
D/WebViewTimersControl( 4016): onBrowserActivityPause
D/WebViewTimersControl( 4016): Pausing webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,2479}
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:90000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:90000 mC
W/IInputConnectionWrapper( 4016): showStatusIcon on inactive InputConnection
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:88000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:88000 mC
I/Timeline( 1247): Timeline: Activity_idle id: [email protected] time:666164
D/DownloadManager( 946): [127] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:92000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:92000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:91000 mC
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[0] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[1] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[2] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[3] to 2572800
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:87000 mC
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[0] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[1] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[2] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[3] to 2649600
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:87000 mC
I/Timeline( 784): Timeline: Activity_windows_visible id: ActivityRecord{5fd96ce u0 com.cyanogenmod.trebuchet/com.android.launcher3.Launcher t11} time:666423
D/DownloadManager( 946): [127] Finished with status SUCCESS
D/DownloadManager( 946): [128] Starting
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
E/AudioTrack( 784): AudioTrack::set : Exit
D/audio_hw_primary( 369): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
E/audio_hw_primary( 369): voice_extn_compress_voip_is_active: COMPRESS_VOIP_ENABLED is not defined
E/msm8974_platform( 369): voice_extn_compress_voip_is_active: COMPRESS_VOIP_ENABLED is not defined
D/audio_hw_primary( 369): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 369): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 369): ACDB -> send_audio_cal, acdb_id = 15, path = 0
D/ACDB-LOADER( 369): ACDB -> send_adm_topology
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
D/ACDB-LOADER( 369): ACDB -> send_asm_topology
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
D/ACDB-LOADER( 369): ACDB -> send_audtable
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AUDPROC_CAL
D/ACDB-LOADER( 369): ACDB -> send_audvoltable
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
D/ACDB-LOADER( 369): ACDB -> send_afe_cal
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AFE_CAL
D/DownloadManager( 946): [128] Finished with status SUCCESS
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: SlidingUpPanelLayout, destroying layer...
I/art ( 784): Explicit concurrent mark sweep GC freed 17401(696KB) AllocSpace objects, 0(0B) LOS objects, 28% free, 39MB/55MB, paused 1.108ms total 66.484m
s
D/DownloadManager( 946): [129] Starting
E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again
D/DownloadManager( 946): [129] Finished with status SUCCESS
D/DownloadManager( 946): [130] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor5:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor7:70000 mC
D/DownloadManager( 946): [130] Finished with status SUCCESS
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor7:70000 mC
D/DownloadManager( 946): [131] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor5:87000 mC
D/DownloadManager( 946): [131] Finished with status SUCCESS
The only thing of use that I could see was: E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again