Develop Bugs

Hide the Onscreen Keyboard

Try this
https://play.google.com/store/apps/details?id=com.wparam.nullkeyboard
Or
https://www.dropbox.com/s/spsemqwbq95mat9/Null Keyboard-com.wparam.nullkeyboard-5-vone.apk
https://www.dropbox.com/s/u2e9dm39nr8rw70/Settings.apk
http://apps.evozi.com/apk-downloader - did not work.
1 - Download and install Null Keyboard and settings.apk if you don't have it already.
2 - Open settings (settings.apk)
3 - Scroll down and click on 'Language & Input'
4 - With a mouse click the box for Null Keyboard then click OK
5 - Then click Default - With a mouse or remote click Null keyboard.
It should now say 'Null Keyboard' under 'KEYBOARD & INPUT METHODS' - Default
Screenshot
https://www.dropbox.com/s/to41058fbk5c2cn/2014_06_26_05.46.34.png
Update:
I could not get this to work again after factory reset.
It was not until I re-installed Xposed installer and the HDXPosed module, then it worked again.

Is this working for everyone? - my AFTV is rooted

..

Can anyone confirm if that settings.apk works? I've tried to install in the past and received a user incompatibility error.

JJ-KwiK said:
The first 2 links in your post are broken.
Click to expand...
Click to collapse
Fixed them - Thanks

It works,but most options cause it to immediately close.
The damn Languages and Input option closes on my Fire TV.
It makes it impossible to select null keyboard an option.
Can someone try to find a settings.apk from a 4.2.2 device?

Un-installed and re-installed settings.apk a few time and it worked.
Now it no longer installs and the Titanium back-up I had of it wont restore either.
It did work for my BT headphones and the Input settings.

I found a stupidly easy solution!
Just open ES File Explorer and enable the root explorer option to gain root access with ES.
Then go to "system/app/" and rename both BuellerIME apk and odex files to what I named them "BuellerIMEx.apk/BuellerIMEx.odex"
Now I no longer get the annoying keyboard popping up and forcing me to another page or completely killing access to the app until force stopped.

retroben said:
I found a stupidly easy solution!
Just open ES File Explorer and enable the root explorer option to gain root access with ES.
Then go to "system/app/" and rename both BuellerIME apk and odex files to what I named them "BuellerIMEx.apk/BuellerIMEx.odex"
Now I no longer get the annoying keyboard popping up and forcing me to another page or completely killing access to the app until force stopped.
Click to expand...
Click to collapse
Nice, basically just de-activating the apk from even running by renaming.

I just thought of another much safer idea if somebody can find the com.name of BuellerIME.
First,you would revert the name changes,and then do the pm disable command after somebody can figure out the com-name for it.
Try reverting the rename and using this in a Terminal Emulator app.
pm list packages -f
If somebody finds the proper com-name before I can reply with it,please post it in a reply.

If use use titanium backup to try and uninstall it, it should give you the package name on the confirmation screen. And then you can cancel the uninstall before you actually remove it. That may work for getting the name.

Found it using 7zipper 2.0 by viewing the details which required root access and was granted.
com.amazon.tv.ime
Just do the same steps as you would for dcp.
adb shell
su
pm disable com.amazon.tv.ime
And then it should no longer appear so you will never need to worry about the problems that could be caused by renaming it.

Ok so after testing using the method mentioned above it does in fact hide the on screen keyboard but it also completely disables the possibility of entering text in certain instances. For example, I enabled the above and disabled the similar method used for blocking. My FTV wasnt finding the update so I went to network settings and forgot my wifi network. When I tried to reconnect by selecting the network name there is no option at all to enter text of any sorts. I actually had to remove the password from my network connect unsecured and reconnect in to adb to disable the keyboard hiding to be able to reconnect to a secured network.

retroben said:
Found it using 7zipper 2.0 by viewing the details which required root access and was granted.
com.amazon.tv.ime
Just do the same steps as you would for dcp.
adb shell
su
pm disable com.amazon.tv.ime
And then it should no longer appear so you will never need to worry about the problems that could be caused by renaming it.
Click to expand...
Click to collapse
Great. Works like a charm!
Sent from my SCH-I545 using XDA Premium 4 mobile app

retroben said:
Found it using 7zipper 2.0 by viewing the details which required root access and was granted.
com.amazon.tv.ime
Just do the same steps as you would for dcp.
adb shell
su
pm disable com.amazon.tv.ime
And then it should no longer appear so you will never need to worry about the problems that could be caused by renaming it.
Click to expand...
Click to collapse
nice! worked for me. thanks. I have a friend with an unrooted AFTV. is there a way to run the command without root, or is it needed?

shutterslaps said:
nice! worked for me. thanks. I have a friend with an unrooted AFTV. is there a way to run the command without root, or is it needed?
Click to expand...
Click to collapse
Anytme you use the "su" command you have to be rooted, so no it will not work on unrooted devices.

shutterslaps said:
nice! worked for me. thanks. I have a friend with an unrooted AFTV. is there a way to run the command without root, or is it needed?
Click to expand...
Click to collapse
You can use ADB commands. I demonstrate on the example of an alternative keyboard which I develop - Fire TV Style keyboard.
How to install and activate the root privileges are not required (enter commands in the queue):
Code:
adb connect 192.168.1.134:5555
adb install /home/semitop7/FireTV_style_keyboard.apk
- (Instead of / home / semitop7 / - indicate your way to the .apk file).
Code:
adb shell ime list -a
- Pop up about such a list:
com.amazon.tv.ime/.FireTVIME:
mId=com.amazon.tv.ime/.FireTVIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.amazon.tv.ime.FireTVIME
packageName=com.amazon.tv.ime
enabled=true exported=true processName=com.amazon.tv.ime
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.example.semitop7.FireTVStyle/.FireTVStyleIME:
mId=com.example.semitop7.FireTVStyle/.FireTVStyleIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.example.semitop7.FireTVStyle/.FireTVStyleIME
packageName=com.example.semitop7.mydpadkeyboard
labelRes=0x7f07001d nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true processName=com.example.semitop7.mydpadkeyboard
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.amazon.tv.ime/.FireTVIME - native keyboard Fire TV Stick
com.example.semitop7.FireTVStyle/.FireTVStyleIME - Keyboard Fire TV style keyboard
Now, we activate the keyboard and put it by default:
Code:
adb shell ime enable com.example.semitop7.FireTVStyle/.FireTVStyleIME
adb shell ime set com.example.semitop7.FireTVStyle/.FireTVStyleIME
To revert back to the native keyboard type:
Code:
adb shell ime set com.amazon.tv.ime/.FireTVIME

I am following your instructions to replace the keyboard (with Swiftkey). When I try and run the Enable command I get "Error Unknown ID: com.amazon.tv.ime/.FireTVIME"
Looks like the actual ID is com.amazon.tv.ime/ .FireTVIME
Not sure what to do now. Any ideas?
I'm not rooted Fire 2 5.2.1.1
sem_top7 said:
You can use ADB commands. I demonstrate on the example of an alternative keyboard which I develop - Fire TV Style keyboard.
How to install and activate the root privileges are not required (enter commands in the queue):
Code:
adb connect 192.168.1.134:5555
adb install /home/semitop7/FireTV_style_keyboard.apk
- (Instead of / home / semitop7 / - indicate your way to the .apk file).
Code:
adb shell ime list -a
- Pop up about such a list:
com.amazon.tv.ime/.FireTVIME:
mId=com.amazon.tv.ime/.FireTVIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.amazon.tv.ime.FireTVIME
packageName=com.amazon.tv.ime
enabled=true exported=true processName=com.amazon.tv.ime
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.example.semitop7.FireTVStyle/.FireTVStyleIME:
mId=com.example.semitop7.FireTVStyle/.FireTVStyleIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.example.semitop7.FireTVStyle/.FireTVStyleIME
packageName=com.example.semitop7.mydpadkeyboard
labelRes=0x7f07001d nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true processName=com.example.semitop7.mydpadkeyboard
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.amazon.tv.ime/.FireTVIME - native keyboard Fire TV Stick
com.example.semitop7.FireTVStyle/.FireTVStyleIME - Keyboard Fire TV style keyboard
Now, we activate the keyboard and put it by default:
Code:
adb shell ime enable com.example.semitop7.FireTVStyle/.FireTVStyleIME
adb shell ime set com.example.semitop7.FireTVStyle/.FireTVStyleIME
To revert back to the native keyboard type:
Code:
adb shell ime set com.amazon.tv.ime/.FireTVIME
Click to expand...
Click to collapse

pd555 said:
I am following your instructions to replace the keyboard (with Swiftkey). When I try and run the Enable command I get "Error Unknown ID: com.amazon.tv.ime/.FireTVIME"
Looks like the actual ID is com.amazon.tv.ime/ .FireTVIME
Not sure what to do now. Any ideas?
I'm not rooted Fire 2 5.2.1.1
Click to expand...
Click to collapse
This ID is specified for example. He's on my Fire TV Stick. Most likely you he has a different ID. To see your ID:
Code:
adb shell ime list -a
- Pop up about such a list:
com.amazon.tv.ime/.FireTVIME:
mId=com.amazon.tv.ime/.FireTVIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.amazon.tv.ime.FireTVIME
packageName=com.amazon.tv.ime
enabled=true exported=true processName=com.amazon.tv.ime
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.example.semitop7.FireTVStyle/.FireTVStyleIME:
mId=com.example.semitop7.FireTVStyle/.FireTVStyleIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.example.semitop7.FireTVStyle/.FireTVStyleIME
packageName=com.example.semitop7.mydpadkeyboard
labelRes=0x7f07001d nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true processName=com.example.semitop7.mydpadkeyboard
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
See after the line mId=
For example on my Fire TV Stick:
com.amazon.tv.ime/.FireTVIME - native keyboard Fire TV Stick
com.example.semitop7.FireTVStyle/.FireTVStyleIME - Keyboard Fire TV style keyboard
You can also use this command:
Code:
adb shell ime list -s
But if the keyboard is install but not activated ID udet not shown by this team. So I recommend to use the first command
Code:
adb shell ime list -a
.

Thanks but I am typing
adb shell ime enable com.touchtype.swiftkey/com.touchtype.keyboardservice
and that gives me the error
"Error Unknown ID: com.amazon.tv.ime/.FireTVIME"
Sorry I didn't make that clearer
sem_top7 said:
This ID is specified for example. He's on my Fire TV Stick. Most likely you he has a different ID. To see your ID:
Code:
adb shell ime list -a
- Pop up about such a list:
com.amazon.tv.ime/.FireTVIME:
mId=com.amazon.tv.ime/.FireTVIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.amazon.tv.ime.FireTVIME
packageName=com.amazon.tv.ime
enabled=true exported=true processName=com.amazon.tv.ime
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
com.example.semitop7.FireTVStyle/.FireTVStyleIME:
mId=com.example.semitop7.FireTVStyle/.FireTVStyleIME mSettingsActivityName=null
mIsDefaultResId=0x0
Service:
priority=0 preferredOrder=0 match=0x108000 specificIndex=-1 isDefault=false
ServiceInfo:
name=com.example.semitop7.FireTVStyle/.FireTVStyleIME
packageName=com.example.semitop7.mydpadkeyboard
labelRes=0x7f07001d nonLocalizedLabel=null icon=0x0 banner=0x0
enabled=true exported=true processName=com.example.semitop7.mydpadkeyboard
permission=android.permission.BIND_INPUT_METHOD
flags=0x0
See after the line mId=
For example on my Fire TV Stick:
com.amazon.tv.ime/.FireTVIME - native keyboard Fire TV Stick
com.example.semitop7.FireTVStyle/.FireTVStyleIME - Keyboard Fire TV style keyboard
You can also use this command:
Code:
adb shell ime list -s
But if the keyboard is install but not activated ID udet not shown by this team. So I recommend to use the first command
Code:
adb shell ime list -a
.
Click to expand...
Click to collapse

[Q] Rom Bootlooping cause of systemservice SIGABRT

Hi Guys,
I'm trying to port to Android 5.0 to a new device (BQ Aquaris E5 4G) and I can't make it fully boot. I'm always hitting this error :
Code:
pid: 634, tid: 634, name: servicemanager >>> /system/bin/servicemanager <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I can't give you ADB Logcat as logcat doesn't seams to work (adb works fine, I can browse adb shell and so on). It kept giving me this error : "logcat read failure: No such file or directory"
The only thing I've got is some tombstone files witch all look similar (please see one attached)
If you could give me an hint that would be great
I tried to change the kernel also but everytime I boot it (using fastboot boot newboot.img) I get a dark blinking screen.
Thanks and merry christmas!

Thread closed as duplicated with https://forum.xda-developers.com/android/help/rom-bootlooping-cause-systemservice-t2984083

Developing an HTC 3 Finger Gesture App - Need Testers!

Based off of this post shared earlier on Reddit (https://www.reddit.com/r/htc/comments/6ibr84/3finger_tap_gesture_to_turn_offlock_phone_for_htc/) , I'm trying to make an app that uses this proof of concept to add more features. The only problem is that I don't have an HTC phone myself to test this on.
The issue I'm trying to resolve right now is that it appears that HTC's Media Gestures currently intercept any 3 finger swipe action before my app can receive them (at least that's what I think is happening, without a logcat I can't tell for sure).
If possible, can any of you help test this for me? The app will be totally free of course.
Just enable HTC's Media Gestures feature, then run the following commands via ADB:
adb shell
am broadcast -a com.htc.action.MULTIPLE_FINGER_SWIPE_EVENT --ei Direction 3
This will send the broadcast intent that HTC's app should react to, letting me know which package is reacting. We might be able to disable it then so my app can take advantage of the gestures.

MishaalRahman said:
Based off of this post shared earlier on Reddit (https://www.reddit.com/r/htc/comments/6ibr84/3finger_tap_gesture_to_turn_offlock_phone_for_htc/) , I'm trying to make an app that uses this proof of concept to add more features. The only problem is that I don't have an HTC phone myself to test this on.
The issue I'm trying to resolve right now is that it appears that HTC's Media Gestures currently intercept any 3 finger swipe action before my app can receive them (at least that's what I think is happening, without a logcat I can't tell for sure).
If possible, can any of you help test this for me? The app will be totally free of course.
Just enable HTC's Media Gestures feature, then run the following commands via ADB:
adb shell
am broadcast -a com.htc.action.MULTIPLE_FINGER_SWIPE_EVENT --ei Direction 3
This will send the broadcast intent that HTC's app should react to, letting me know which package is reacting. We might be able to disable it then so my app can take advantage of the gestures.
Click to expand...
Click to collapse
06-25 19:05:34.880 14851-14851/? D/AmCmd: args=[broadcast, -a, com.htc.action.MULTIPLE_FINGER_SWIPE_EVENT, --ei, Direction, 3] uid=2000
06-25 19:05:34.882 14851-14851/? D/AmCmd: pid=14851(app_process) from pid=13358(/system/bin/sh) from pid=1456(/sbin/adbd) from pid=1(/init)
06-25 19:05:38.034 1203-1203/? E/TPD: [TPD] ERR: tamper detect flag = 0x10, detect symptom = 0x10
06-25 19:05:41.375 3404-3418/? I/art: JIT added (osr=false) void leo.a(android.app.Service, int, int)@0x7fa61b4108 ccache_size=243KB: dcache_size=244KB: 0x7f994d03e0,0x7f994d08d8
06-25 19:05:41.484 1959-3255/? D/PMS: acquireWL(f0efc61): PARTIAL_WAKE_LOCK CMWakeLock 0x1 3124 10023 WorkSource{10023 com.google.android.gms}
06-25 19:05:41.490 1959-4721/? D/PMS: releaseWL(f0efc61): PARTIAL_WAKE_LOCK CMWakeLock 0x1 WorkSource{10023 com.google.android.gms}
06-25 19:05:48.106 1203-1203/? E/TPD: [TPD] ERR: tamper detect flag = 0x10, detect symptom = 0x10
06-25 19:05:51.157 14604-14643/? D/EASAppSvc: [ NA ]MSG_STOP_SERVICE: stopSelf
06-25 19:05:51.164 14604-14604/? I/EASAppSvc: [ NA ]onDestroy
06-25 19:05:51.165 14604-14643/? I/EASAppSvc: [ NA ]> uninitEASService
06-25 19:05:51.175 1959-3220/? I/ActivityManager: Killing 13688:com.htc.Weather:weather_sync_provider/u0a74 (adj 906): empty #17
06-25 19:05:51.176 1959-3220/? D/Process: killProcessQuiet, pid=13688
06-25 19:05:51.177 1959-3220/? D/Process: com.android.server.am.ProcessRecord.kill:-1 com.android.server.am.ActivityManagerService.updateOomAdjLocked:-1 com.android.server.am.ActivityManagerService.updateOomAdjLocked:-1
06-25 19:05:51.180 1959-3220/? I/ActivityManager: Killing 14173:com.facebook.katana/u0a142 (adj 906): empty #18

Hi,
Did the command prompt/terminal not show any output? The Logcat here doesn't really show me what I'm looking for.

MishaalRahman said:
Hi,
Did the command prompt/terminal not show any output? The Logcat here doesn't really show me what I'm looking for.
Click to expand...
Click to collapse
that was it,
I executed the command several times.

"Welcome" Screen of ROM Fails to Respond to Touch

I rooted my SGH-T999, running Android 4.3, flashing TWRP recovery w/ Odin.
The rooting was successful.
Now, on to the part where I ran into trouble.
Problem: I can't successfully install any ROMs for Android M or later.
NOTE: I need Android M or later to have more control over individual apps' permissions.
I tried to flash Pac-ROM through TWRP, like so:
(from TWRP home menu)
1. Wipe>Swipe to Factory Reset
2. Go Back to Home Menu
3. Install>Select pac_d2tmo_MM.Beta.Official_20160920-165602.zip>Swipe to confirm Flash
Note: The first time I tried to flash Pac-ROM, I wasn't aware of GApps. So, I didn't flash it.
4. Reboot
The phone booted to the "Welcome/Language Selection" screen, but I couldn't select a language.
It seems that the UI elements belonging to the "Welcome" screen fail to respond to touch, while other UI elements respond normally (as demonstrated at the end of the video at the URL below).
All attempts to re-flash, since, have included the additional step off adding the GApps zip (for ARM, Android 6.0) to the "ZIP Queue".
However, all attempts end the same way.
I've documented the process in the video @ the following URL: youtu.be/EZTwaURkRSs
Another strange behavior (that isn't apparent in the video) is that, immediately after being shown on the display, the "Welcome" screen looks fine for a few hundred milliseconds or so before the screen is drawn with a yellowish-hue. As if blue-light filtering kicks in (even when the system clock is mid-day).
I also tried to flash a different ROM (Oct-OS OCT-M-R3) on a few of the attempts, but again I observed the same exact behavior ("Welcome" screen's yellowish hue and lack of response to touch).
It doesn't seem to be a hardware issue, because touch does work, just not on the "Welcome" screen.
I'm fairly certain I've selected the correct ROM for the model.
So, what did I mess up?

I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again

andynoob said:
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
Click to expand...
Click to collapse
Do you mean that you were able to flash a ROM successfully, after flashing stock (4.4.2)?
Or, you were ONLY able to flash stock (4.4.2) successfully?
Thank you for the reply,
Gerald

I just restored my twrp backup of stock os .. Had urgent work so couldn't try to flash those ROMs again.. will try them next week

UPDATE:
So, I successfully restored my stock backup.
With the stock setup I experienced no problems.
Since my original post, I've alternated between restoring stock backup and flashing ROMs.
I tried flashing Oct-OS and Pac-ROM, again and again.
I also tried to install LineageOS, as well.
I am able to install CyanogenMod 12.1, but this doesn't meet my requirement of android version 6 or later.
Installation of any of the custom ROMs has resulted in the same behavior demonstrated in the video (youtu.be/EZTwaURkRSs):
- after boot, device fails to respond to touch input
- however, device does accept touch input on some UI objects. so, I don't think it's a screen/hardware issue
How can I debug further?
I'd like to try to capture some sort of boot log, but adb is "offline" during boot process.
And, since I can't make it past the "language selection/welcome" screen, I can't get to settings and enable USB debugging.

UPDATE:
I managed to enable ADB during boot, by using the ADB shell while the device was in recovery mode.
Code:
[email protected] ~ $ adb push ~/.android/adbkey.pub /data/misc/adb/
[email protected] ~ $ adb shell
~# cd /data/misc/adb/
/data/misc/adb# cat adbkey.pub > adb_keys
/data/misc/adb# cd /
~# mkdir /system2
~# mount -o rw /dev/block/mmcblk0p14 /system2 ## NOTE: for this command, had to figure out which partition was the system partition; here it was /dev/block/mmcblk0p14
~# echo "persist.service.adb.enable=1" >> default.prop
~# echo "persist.service.debuggable=1" >> default.prop
~# echo "persist.sys.usb.config=mtp,adb" >> default.prop
~# echo "persist.service.adb.enable=1" >> /system2/build.prop
~# echo "persist.service.debuggable=1" >> /system2/build.prop
~# echo "persist.sys.usb.config=mtp,adb" >> /system2/build.prop
~# ## now press Ctrl-D to exit the ADB shell
NOTE: thanks to @ErnestChia for the following post forum.xda-developers.com/showpost.php?p=63829295&postcount=27
So, I was able to get a logcat during the SetupWizard.
There were 3 lines, related to the SystemUI, that were repeated over and over.
Code:
W BroadcastQueue: Timeout of broadcast BroadcastRecord{51dfd23 u-1 android.intent.action.TIME_TICK} - [email protected], started 10010ms ago
W BroadcastQueue: Receiver during timeout: BroadcastFilter{a4079bf u0 ReceiverList{4b103de 730 com.android.systemui/10018/u0 remote:448f719}}
I ActivityManager: Skipping duplicate ANR: ProcessRecord{768d889 730:com.android.systemui/u0a18} Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
All I've gathered is that SystemUI isn't responding.
Which seems to have started during boot, with the following output.
Code:
W ActivityManager: Timeout executing service: ServiceRecord{dd2251a u0 com.android.systemui/.ImageWallpaper}
E ActivityManager: ANR in com.android.systemui
E ActivityManager: Reason: executing service com.android.systemui/.ImageWallpaper
E ActivityManager: 4.1% 730/com.android.systemui: 2.2% user + 1.8% kernel / faults: 1246 minor 2 major
SystemUI Stack Trace
Code:
Cmd line: com.android.systemui
Build fingerprint: 'samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys'
ABI: 'arm'
Build type: optimized
Zygote loaded classes=3986 post zygote classes=991
Intern table: 46441 strong; 62 weak
JNI: CheckJNI is off; globals=427 (plus 368 weak)
Libraries: /system/lib/libandroid.so /system/lib/libcompiler_rt.so /system/lib/libjavacrypto.so /system/lib/libjnigraphics.so /system/lib/libmedia_jni.so /system/lib/libsoundpool.so /system/lib/libwebviewchromium_loader.so libjavacore.so (8)
Heap: 5% free, 12MB/13MB; 84371 objects
Dumping cumulative Gc timings
Total number of allocations 84371
Total bytes allocated 12MB
Total bytes freed 0B
Free memory 813KB
Free memory until GC 813KB
Free memory until OOME 179MB
Total memory 13MB
Max memory 192MB
Zygote space size 1972KB
Total mutator paused time: 0
Total time waiting for GC to complete: 0
Total GC count: 0
Total GC time: 0
Total blocking GC count: 0
Total blocking GC time: 0
...
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x745992a0 self=0xb77f9b30
| sysTid=730 nice=0 cgrp=default sched=0/0 handle=0xb6efab44
| state=S schedstat=( 0 0 0 ) utm=64 stm=14 core=1 HZ=100
| stack=0xbe5d0000-0xbe5d2000 stackSize=8MB
| held mutexes=
native: #00 pc 0004290c /system/lib/libc.so (__ioctl+8)
native: #01 pc 00049391 /system/lib/libc.so (ioctl+14)
native: #02 pc 0001e8c9 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
native: #03 pc 0001eefb /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
native: #04 pc 0001f0b1 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
native: #05 pc 0001a0b3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
native: #06 pc 00089471 /system/lib/libandroid_runtime.so (???)
native: #07 pc 00db9189 /data/dalvik-cache/arm/[email protected]@boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative(Native method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:421)
at java.lang.reflect.Method.invoke!(Native method)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:80)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at android.hardware.ICameraService.getCameraCharacteristics(ICameraService.java:-2)
at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:635)
at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:99)
- locked <0x0da89d30> (a java.lang.Object)
at com.android.systemui.statusbar.policy.FlashlightController.getCameraId(FlashlightController.java:126)
at com.android.systemui.statusbar.policy.FlashlightController.<init>(FlashlightController.java:62)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1087)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3285)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3281)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:619)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:800)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:230)
at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java:-1)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke!(Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

i solved this issue by flashing the pac rom 6.0 from at&t . (Flash only the rom )

Do you have a copy of carbon ROM or Pac man for the d2tmo?

Mirror screen

Hi guys,
Is it possible to mirror the screen from the watch to an PC?
You can put everything on the watch but from the watch to other devices no way! ?
It's nothing out there and I think I'm the only person on earth searching like this.
?

Sam.ung is par.noid...
Maybe 1 reason could be Knox crap like Samsung Pay...
Since Tizen 3 no Screencapture nor Video capture possible without ROOT...
Best Regards

Found in GW3 Firmware...
com.samsung.screen-capture.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns="http://tizen.org/ns/packages" package="com.samsung.screen-capture" api-version="[COLOR="Green"][B]3[/B][/COLOR].0" support-mode="ultra-power-saving" version="0.2" install-location="internal-only" type="rpm" readonly="true" preload="true" removable="false">
<profile name="mobile"/>
<label>screen capture</label>
<description>Screen Capture</description>
<ui-application appid="com.samsung.screen-capture" exec="/usr/apps/com.samsung.screen-capture/bin/screen-capture" nodisplay="true" launch_mode="single" multiple="true" type="capp" taskmanage="false" hw-acceleration="use-GL">
<label>Screen Capture</label>
<label xml:lang="en-us">Screen Capture</label>
<icon>com.samsung.screen-capture.png</icon>
</ui-application>
<privileges>
<privilege>http://developer.samsung.com/tizen/privilege/logmanager</privilege>
<privilege>http://tizen.org/privilege/window.priority.set</privilege>
<privilege>http://tizen.org/privilege/mediastorage</privilege>
<privilege>http://tizen.org/privilege/content.write</privilege>
<privilege>http://tizen.org/privilege/content.read</privilege>
<privilege>http://tizen.org/privilege/externalstorage</privilege>
<privilege>http://tizen.org/privilege/notification</privilege>
<privilege>http://tizen.org/privilege/screenshot</privilege>
<privilege>http://tizen.org/privilege/haptic</privilege>
<privilege>http://tizen.org/privilege/appdir.shareddata</privilege>
<privilege>http://tizen.org/privilege/appmanager.launch</privilege>
<privilege>http://tizen.org/privilege/keygrab</privilege>
</privileges>
<service-application component-type="svcapp" auto-restart="false" on-boot="false" hw-acceleration="use-GL" appid="com.samsung.screen-capture-service" exec="/usr/apps/com.samsung.screen-capture/bin/screen-capture-svc" nodisplay="true" multiple="true" type="capp" taskmanage="false">
<icon>com.samsung.screen-capture.png</icon>
<label>Screen Capture SVC</label>
</service-application>
</manifest>
And in /usr/bin folder:
Code:
scmirroring_sink_test
screen_recorder
But I have only damaged/corrupted rootfs.img...
Otherwise I would try to use it...
Best Regards
Edit 1.
Oh, not realized...
Code:
sh-3.2# /home/scmirroring_test --help
=====================================================================
SCMIRRORING Testsuite(press q to quit)
=====================================================================
m : Make mirroring source handle(create handle)
a : set ip & port(ex. a 192.168.49.1 2022)
c : set resolution(ex. c 0 (0 : 1920x1080_P30, 1 : 1280x720_P30, 2 : 960x540_P30, 3: 640x360_P30)
f : set connection mode(ex. f 0 (0 : wifi_direct, 1 : Other)
C : Connect
I : dIsconnect
S : Start
P : Pause
R : Resume
s : Direct Streaming (ex. s 1 file:///tmp/file.mp4 (0:disable, 1:enable))
u : Switch to UDP
t : Switch ti TCP
T : sTop
D : Destroy
q : quit
Best Regards