Hello World
So I pulled IrRemote.apk and IrRemoteServices.apk, decompiled them, and wow a lot more work was put into the ir remote than I had originally anticipated. I am now convinced making a simple widget for the remote is over my head. I also logcat'ed the tablet s and tapped the tv power button and this is what I got
Code:
I/ActivityManager( 144): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.sony.nfx.app.irremote/.IrRemote bnds=[402,0][458,56] } from pid 251
I/ActivityManager( 144): Start proc com.sony.nfx.app.irremote for activity com.sony.nfx.app.irremote/.IrRemote: pid=3276 uid=10042 gids={}
I/ActivityManager( 144): Start proc com.sony.nfx.providers.region for content provider com.sony.nfx.providers.region/.RegionProvider: pid=3283 uid=10017 gids={}
I think I'm giving up, though if anyone wants the decompiled apks to give it a shot let me know,
I'd love fully customisable interface with macros. Hope your suggestion will help someone to develop this
Sent from my Sony Tablet S using Tapatalk
ps3taker said:
I'd love fully customisable interface with macros. Hope your suggestion will help someone to develop this
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Me too.
Here is the link to Sony SDK if anybody is interested.
http://android.developer.sony.com/pages/documents/view/?id=4000049
You need to register to see it.
Related
Hi all,
Some of you might know I'm currently working my NubDial (http://forum.xda-developers.com/showthread.php?t=629032) during my free time. However, I've run into a bug that I'm quite lost at.
Basically, whenever I long-press the "Menu" button to get the virtual keyboard to display, it messes up my layout. When I press "Back" or long press "Menu" again to hide the virtual keyboard, my layout remains messed up until I exit the app. See attached files for what I'm saying.
My source code is available here: http://code.google.com/p/nubdial
Any help would be greatly appreciated, thank you!
Update:
Anyone knows how to launch Call log and Favourites using Intent?
The following:
Code:
public Intent getCallLogIntent() {
Intent i = new Intent();
i.setAction(Intent.ACTION_VIEW);
i.setData(android.provider.CallLog.CONTENT_URI);
return i;
}
Works but it launches Dialer instead of Call log -_-. Thanks!
Are you trying to have the android keyboard cover the dialpad or just trying to figure out how to keep the layout from staying messed up after you close the android keyboard?
Only looked for a minute and I'm sure you've tried a lot of things but as for the alignment if you look in finger-layout>main.xml, in the RelativeLayout tag, have you tried changing the android:gravity so that the child table is "prepositioned" if you know what I mean?
JoshHart: I would love to have the keyboard simply cover the layout (similar to default Dialer). Any tips? Thanks for the help!
I'll check out the prepositioned thing later, out now.
On a different note, anyone knows how to launch Call log or Favourites using intent? Thanks
Wysie said:
On a different note, anyone knows how to launch Call log or Favourites using intent? Thanks
Click to expand...
Click to collapse
This seems to work on my Nexus:
Code:
Intent i = new Intent(Intent.ACTION_VIEW);
i.setClassName("com.android.contacts", "com.android.contacts.DialtactsActivity");
i.setType("vnd.android.cursor.dir/calls");
//i.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
this.startActivity(i);
Don't know for favorites though, a variation of type might do it, but neither "starred" nor "favorites" worked for me.
illojal: Thanks but I already did that and it worked ! Yeah Favourites is kinda weird.
I'm finding the apk's location.... Do you have any idea?
Not sure, but i think there´s no "proper" .apk for that. I suppose the widget it´s part of some other service or system file. The only thing i can figure to "locate" that it´s to push all the system files to your computer, and then you can "browse" inside (using winrar or better 7zip) and look for the graphics of the widget, so you know that´s the correct .apk.
Regards.
PS: Is your question related to this: http://code.google.com/p/extendedcontrols/issues/detail?id=34 ??
I suppose is Settings.apk
With alogcat:
I/ActivityManager( 1154): Starting activity: Intent { act=android.appwidget.action.APPWIDG cmp=com.android.settings/.AppWidgetPickActivity (has extras) }
That´s a good point.
Apart from the "Energy Control" widget, the last firmware available on the mini added a new widget, called "Status switch" or something similar... It´s a 2 rows widget, with 3 icons on each row. It controls the same as the Energy Control, but adds the plane mode icon switch.
i am an app developer with few apps already in the play store. i am currently in a project in which i need to make an app that functions likes the launcher apps. for example if i click a button named camera the default camera app should start,or clicking on setttings button should start default android settings activity.
i am having a big trouble in finding the default intent codes for the system apps.
actually this is what i meant to start the default camera app we do
Intent intent = new Intent("android.media.action.IMAGE_CAPTURE");
startActivityForResult(intent, 0);
i want the intent actions for other system apps. googling doesnt brings me to a correct solution.stack overflow doesnt helps much too.
could someone help me in this or give me a link to the source were i could find it..
thanks
i am still waiting for a helping hand.
Hello,
I bought Nova Launcher Prime about three days ago, because I absolutely loved the way it handles, well, everything, and everything was going okay, until yesterday.
This is what happened. I was fidgeting around the settings tab (just checking which applications used battery, not really changing anything), and when I was done, I pressed the back key, to return to the home screen. So, I exited the battery tab, and arrived on the main settings page. So I pressed the back button again. However, this time, everything froze for about 5 seconds, and then the screen turned black. That lasted for about 15 seconds, then a dialog appeared, saying Nova Launcher Has Stopped, or something, but before I could select "Report", it disappeared, and I guess it restarted; so I was back on the home screen. The first time, I thought nothing of it, but then it started happening quite often, and it just happened again, 5 minutes ago, as I was exiting my messages "window". Same thing - I pressed the back button, to go back to my home screen... bam - blackness, however no dialog. In fact, the only time the dialog appeared, saying it's stopped working, was the first time.. Anyway, after the blackness, 15 seconds later, I was again, at my home screen, after what I assume was a restart of the launcher.
I downloaded an app, called Catlog and filtered the log to only show entries with the word "Launcher" in there, and here is what came out after the last crash, 5 minutes ago:
01-04 10:48:47.463 V/Mms/ConversationComposer(13649): Launcher task Running
01-04 10:48:50.198 I/SurfaceFlinger(1822): id=4584(8) createSurface 0x276cc (480x800),1 flag=0, Launcher
01-04 10:48:50.213 V/Nova.Launcher(17368): Trying bind
01-04 10:48:50.218 V/Nova.Launcher(17368): bind unread took 2
01-04 10:49:59.253 V/Nova.Launcher(17368): Trying bind
01-04 10:49:59.258 V/Nova.Launcher(17368): bind unread took 6
01-04 10:52:39.088 V/Nova.Launcher(17368): Trying bind
01-04 10:52:39.098 V/Nova.Launcher(17368): bind unread took 11
01-04 10:52:41.083 I/SurfaceFlinger(1822): id=4584 Removed Launcher idx=1 Map Size=4
01-04 10:52:41.083 I/SurfaceFlinger(1822): id=4584 Removed Launcher idx=-2 Map Size=4
01-04 10:55:41.253 V/Mms/ConversationComposer(13649): Launcher task Running
01-04 10:55:41.303 I/SurfaceFlinger(1822): id=4719(9) createSurface 0x276cc (480x800),1 flag=0, Launcher
01-04 10:55:41.818 I/DEBUG (12856): pid: 17368, tid: 17368 >>> com.teslacoilsw.launcher <<<
01-04 10:56:06.338 I/InputDispatcher(1976): Application is not responding: AppWindowToken{41bf4688 token=Token{41bf1798 ActivityRecord{41bf1368 com.teslacoilsw.launcher/com.android.launcher2.Launcher}}} - Window{41d48ff8 com.teslacoilsw.launcher/com.android.launcher2.Launcher paused=false}. 24287.6ms since event, 20020.8ms since wait started
01-04 10:56:06.338 I/WindowManager(1976): Input event dispatching timed out sending to com.teslacoilsw.launcher/com.android.launcher2.Launcher
01-04 10:56:07.623 E/ActivityManager(1976): ANR in com.teslacoilsw.launcher (com.teslacoilsw.launcher/com.android.launcher2.Launcher)
01-04 10:56:13.623 I/ActivityThread(18892): Pub com.teslacoilsw.launcher.settings: com.android.launcher2.LauncherProvider
01-04 10:56:13.638 V/ActivityManager(18892): Start proc com.teslacoilsw.launcher (This is fake for proclogcat on sgs3): pid=18892
01-04 10:56:13.643 D/ACRA (18892): ACRA is enabled for com.teslacoilsw.launcher, intializing...
01-04 10:56:13.658 D/ACRA (18892): Looking for error files in /data/data/com.teslacoilsw.launcher/files
01-04 10:56:13.703 V/IconPack(18892): Icon theme for GO com.go.launcherex.theme.kxnt.glasklart
01-04 10:56:13.783 I/dalvikvm(18892): Could not find method android.app.ActivityOptions.makeScaleUpAnimation, referenced from method com.android.launcher2.Launcher.櫯
01-04 10:56:13.898 I/dalvikvm(18892): Could not find method com.android.launcher2.Workspace.getImportantForAccessibility, referenced from method com.android.launcher2.Workspace.<init>
01-04 10:56:13.898 W/dalvikvm(18892): VFY: unable to resolve virtual method 2169: Lcom/android/launcher2/Workspace;.getImportantForAccessibility ()I
01-04 10:56:14.458 V/Nova.Launcher(18892): First page bound after 609ms
01-04 10:56:14.468 I/SurfaceFlinger(1822): id=4721(1) createSurface 0x30b3c (1x1),1 flag=0, Launcher
01-04 10:56:14.598 V/Nova.Launcher(18892): Trying bind
01-04 10:56:14.608 V/Nova.Launcher(18892): bind unread took 6
01-04 10:56:14.718 V/Nova.Launcher(18892): Finishing binding after 868
01-04 10:56:15.138 I/SurfaceFlinger(1822): id=4719 Removed Launcher idx=3 Map Size=4
01-04 10:56:15.138 I/SurfaceFlinger(1822): id=4719 Removed Launcher idx=-2 Map Size=4
01-04 10:56:15.143 I/SurfaceFlinger(1822): id=4719 Removed Launcher idx=-2 Map Size=4
01-04 10:56:25.998 I/SurfaceFlinger(1822): id=4721 Removed Launcher idx=1 Map Size=4
01-04 10:56:25.998 I/SurfaceFlinger(1822): id=4721 Removed Launcher idx=-2 Map Size=4
I guess it says something there about why it crashed, but I've no idea what it means.. I hope you can help me, these are my specs:
Galaxy SII, Model Number GT-I9100
Android Version: 4.0.4
Baseband Version: I9100BOLP7
Kernel Version: 3.0.15-1056084 [email protected] #3
It's not rooted, and the apps I've running in the background are Gentle Alarm and Widget Locker (among many others, but those two are the ones that modify the home screen, that's why I think they may be relevant)
I look forward to your answer, or at least some directions on who to turn to for this issue. I apologize if I've made many grammatical mistakes, English isn't my first language. Also, if I am in the wrong forum/board/doing something wrong, please tell me where I can go with this issue; I've already used the search and it has no results that have the same issue as I do; I just wanna use my phone normally.. I'm posting here, because I have a feeling that the bug is exclusive to the Galaxy S2, but if I'm wrong to post here, just please tell me where...
Are you using the new 2.0 version? It crashes pretty often to me too.The previous release was more stable...
911-Future_Maker said:
Are you using the new 2.0 version? It crashes pretty often to me too.The previous release was more stable...
Click to expand...
Click to collapse
Yes, I'm using the version that's in the Play Store right now, so I guess 2.0 it is... A ideas how to fix it?
I'll guess we have to wait for an update from the dev. Or switching to an older version of Nova.
911-Future_Maker said:
I'll guess we have to wait for an update from the dev. Or switching to an older version of Nova.
Click to expand...
Click to collapse
I guess I'm switching to Go Launcher Ex, until this is fixed... it's basically making my phone unusable
And to think I paid for this app..
I have created a widget that displays a digital clock, I have it done in two different ways, using a Handler and using a BroadcastReceiver to display the actual time with seconds, both of them work, however, I'd like to understand which one is better in terms of battery saving (because of the constant update), performance, functionality, etc. I would appreciate your comments on this, thank you.
saman0suke1 said:
I have created a widget that displays a digital clock, I have it done in two different ways, using a Handler and using a BroadcastReceiver to display the actual time with seconds, both of them work, however, I'd like to understand which one is better in terms of battery saving (because of the constant update), performance, functionality, etc. I would appreciate your comments on this, thank you.
Click to expand...
Click to collapse
The handler seems better to me, because this just counts second by second without any connection, the broadcast receiver receives every second individually, you could add an broadcast receiver to the handler time to time
Sent from my HTC One X+ using xda app-developers app
Thatgrass said:
The handler seems better to me, because this just counts second by second without any connection, the broadcast receiver receives every second individually
Click to expand...
Click to collapse
In the case of the BroadcastReceiver I use an AlarmManager to set it in the onEnabled method of the widget that extends AppWidgetProvider:
Code:
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, System.currentTimeMillis() + 1000, 1000, pendingIntent);
While in the Handler, I set it in the onUpdate method of the widget:
Code:
handler.postDelayed(updateClock, 1000);
I understand that the handler uses the onUpdate method every second, while the BroadcastReceiver does not, am I right? if so, the handler should have worst performance isn't? I'm still learning to use BroadcastReceiver and its functionality, I appreciate the help.
Thatgrass said:
you could add an broadcast receiver to the handler time to time
Click to expand...
Click to collapse
I did not quite understand this, could you explain a little bit more?
saman0suke1 said:
I did not quite understand this, could you explain a little bit more?
Click to expand...
Click to collapse
I mean: the handler is pretty much offline, if you set a BroadcastReceiver for every 12 hours or something, the time is always correct, but your phone isn't always picking up seconds from the air.
Sent from my HTC One X+ using xda app-developers app