{
"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"
}
Since KitKat is becoming stable, I have built another ROM and decided to share it with you.
OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance, reliability and features over stock Android for your device. It is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
More information about Omni
Code:
#include
/*
* 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.
*/
NOT WORKING/BROKEN
Same as in CM11
Camera
CHANGELOG
Code:
[B][U]29/05/2014:[/U][/B]
[LIST]
[*]Fixed USB Mass storage - [URL="gerrit.omnirom.org/#/c/5041/"]gerrit.omnirom.org/#/c/5041/[/URL]
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]06/05/2014:[/U][/B]
[LIST]
[*]Fixed OMX
[*]Fixed camera video recording
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]01/05/2014:[/U][/B]
[LIST]
[*]Initial release
[/LIST]
DOWNLOAD
OmniROM - team-simplicit.com
BTW: This ROM is not rooted, you have to flash SuperSU!
SCREENSHOTs
SOURCEs
Manifest
Device Config
Kernel Source
CREDITS
My awesome team (izi501, feroxx, Kevinjoa, thehacka1) for being so awesome!
WinSuk for the linker/reboot fix
benjamingwynn
niks255
JDevs and the OWL Team
The androidarmv6 team
The Omni team
Great job Oli. [emoji111]
Gesendet von meinem LG-gee mit Tapatalk
Info about ME
You're impossible @Olivier :laugh:
Anyway... New dev is coming
CyanFrank said:
You're impossible @Olivier :laugh:
Anyway... New dev is coming
Click to expand...
Click to collapse
Oh my goodness I really can't get it Just gonna press the download button...
I can haz logcat?
Logcat time!
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Code:
[ 05-03 16:55:09.561 5054: 5054 E/memalloc ]
/dev/pmem: Failed to map buffer size:4202496 offset:1843200 fd:83 Error: Invalid
argument
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
Could not mmap handle 0x2a1eac10, fd=83 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
gralloc_register_buffer: gralloc_map failed
[ 05-03 16:55:09.561 5054: 5054 W/GraphicBufferMapper ]
registerBuffer(0x2a1eac10) failed -22 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/GraphicBuffer ]
unflatten: registerBuffer failed: Invalid argument (-22)
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGLSUB ]
CreateImage() Invalid Native Buffer or handle
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGL ]
<qeglDrvAPI_eglCreateImageKHR:4160>: EGL_BAD_PARAMETER
Also, "Advanced settings" in "Performance" FCs
Code:
[ 05-03 16:58:34.951 4889: 4889 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.settings, PID: 4889
java.lang.NullPointerException
at java.io.File.fixSlashes(File.java:185)
at java.io.File.<init>(File.java:134)
at java.io.FileInputStream.<init>(FileInputStream.java:105)
at java.io.FileReader.<init>(FileReader.java:66)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.getVolts
(VoltageControlSettings.java:229)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.onCreate
(VoltageControlSettings.java:77)
at android.app.Fragment.performCreate(Fragment.java:1678)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062
)
at android.app.BackStackRecord.run(BackStackRecord.java:684)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.ja
va:1447)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:443)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit
.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
at dalvik.system.NativeStart.main(Native Method)
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Very Very good new htc wildfire s good olivier
csoulr666 said:
Logcat time!
Click to expand...
Click to collapse
Thanks for the logs! :good:
csoulr666 said:
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Click to expand...
Click to collapse
Should be fixed in the next release...
csoulr666 said:
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Click to expand...
Click to collapse
Look at the first screenshot, the device does show the charging symbol in the statusbar.
However, the lights and the notification LED really don't work. I will look into it ASAP.
EDIT: New update is up, check the OP!
Olivier said:
Look at the first screenshot, the device does show the charging symbol in the statusbar.
Click to expand...
Click to collapse
It does show a charging animation(I was using percent only, no animation there), but in the quick settings toggle or the diag menu(*#*#4636#*#*) do not show the charging status.
However, the lights and the notification LED really don't work. I will look into it ASAP.
Click to expand...
Click to collapse
Actually I found saw that LED works for certain notifications(only Gmail so far) but never for charging.......the latter might be because the system doesn't show the charging status
Also I have a question, will flashing the new update on the rom without wiping remove root as well??
csoulr666 said:
Will flashing the new update on the rom without wiping remove root as well??
Click to expand...
Click to collapse
I think so, because system (where SuperSU is located) gets wiped.
Olivier said:
I think so, because system (where SuperSU is located) gets wiped.
Click to expand...
Click to collapse
I just remembered, SuperSU asked me to install an addon script just to survive flashing...... Silly me:silly:
Question, you have not added UMS as of now am I right?? Because nothing pops up when I connect my phone to my PC
Wow! Looks like I'm the only one using OMNI, everyone else is glued to CM11 :laugh:
I got some more logs, hopefully helpful ones, regarding VPN ,bluetooth and wifi tethering
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Build from source ?
Olivier said:
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Click to expand...
Click to collapse
I have built CM11 from source, and would love to build this one too, to compare, I was expecting an omni branch in your github but didn't see it ?
Omni is at "android-4.4".
Gesendet von meinem Lenovo A3000-H mit Tapatalk
Awesome ROM but the quick pulldown disappear after reboot.
The patch not working camera
You always do the best olivier
Sent from my XT1032 using XDA Free mobile app
I'm not using this ROM
But,there is a workaround for USB Mass Storage bug,you see you can maybe use mobogenie pc app to make it work,because it mounts sd to pc without having to unmount it from device.
Best Wishes and tell me if it works
Camera?
I tried the camera patch with a complete wipe(including system) following the 6th may build........The "Can't connect to camera" prompt doesn't come but I'm greeted with a completely black screen, I tried a few other photo taking apps(Splitpic, Instagram and even a barcode scanner) but I still go the same result.
So here's a logcat of me opening the stock camera app
Code:
[ 05-07 21:02:49.867 615: 667 I/ActivityManager ]
Start proc com.android.camera2 for activity com.android.camera2/com.android.came
ra.CameraLauncher: pid=4766 uid=10050 gids={50050, 3003, 1028, 1015, 1023}
[ 05-07 21:02:50.817 4766: 4766 D/CameraStorage ]
External storage state=mounted
[ 05-07 21:02:50.827 4766: 4766 V/NFC ]
this device does not have NFC support
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
On resume.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Executing onResumeTasks.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Open camera device.
[ 05-07 21:02:50.858 129: 129 D/AK8975 ]
Compass Start
[ 05-07 21:02:50.878 124: 1053 D/CameraHAL ]
CameraHAL_GetNum_Cameras: loading libcamera at 0x4077eed8
[ 05-07 21:02:50.888 4766: 4766 V/CameraHolder ]
open camera 0
[ 05-07 21:02:51.298 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.558 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.808 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.919 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.119 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.299 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.519 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.719 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.920 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.110 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.190 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.410 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.590 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.790 124: 4221 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:53.790 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.021 124: 668 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.031 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.231 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.411 124: 1053 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.421 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:59.786 615: 631 E/WindowManager ]
Starting window AppWindowToken{420b01a8 token=Token{420af890 ActivityRecord{420a
f6b8 u0 com.android.camera2/com.android.camera.CameraLauncher t453}}} timed out
[ 05-07 21:02:59.796 615: 632 W/ActivityManager ]
Launch timeout has expired, giving up wake lock!
[ 05-07 21:03:10.857 615: 632 W/ActivityManager ]
Timeout executing service: ServiceRecord{42208360 u0 com.android.camera2/com.and
roid.camera.MediaSaveService}
[ 05-07 21:03:10.917 615: 632 I/Process ]
Sending signal. PID: 4766 SIG: 3
[ 05-07 21:03:10.917 4766: 4771 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:10.967 4766: 4771 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:10.967 615: 632 I/Process ]
Sending signal. PID: 615 SIG: 3
[ 05-07 21:03:10.967 615: 620 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.538 615: 627 E/Sensors ]
poll() failed (Interrupted system call)
[ 05-07 21:03:11.578 615: 632 I/Process ]
Sending signal. PID: 991 SIG: 3
[ 05-07 21:03:11.578 991: 996 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.608 615: 620 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.608 615: 632 I/Process ]
Sending signal. PID: 803 SIG: 3
[ 05-07 21:03:11.618 803: 815 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.728 803: 815 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.738 615: 632 I/Process ]
Sending signal. PID: 795 SIG: 3
[ 05-07 21:03:11.738 795: 809 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.758 991: 996 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.768 615: 632 I/Process ]
Sending signal. PID: 783 SIG: 3
[ 05-07 21:03:11.768 783: 794 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.858 783: 794 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.958 795: 809 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:13.920 615: 632 E/ActivityManager ]
ANR in com.android.camera2
PID: 4766
Reason: Executing service com.android.camera2/com.android.camera.MediaSaveServic
e
Load: 10.33 / 14.25 / 12.94
CPU usage from 6040ms to 0ms ago:
1.3% 129/akmd: 0.1% user + 1.1% kernel
1.3% 615/system_server: 0.8% user + 0.4% kernel
0.3% 5/events/0: 0% user + 0.3% kernel
0.1% 109/yaffs-bg-1: 0% user + 0.1% kernel
0.1% 754/wpa_supplicant: 0.1% user + 0% kernel
1.8% TOTAL: 0.6% user + 1.1% kernel
CPU usage from 2456ms to 2995ms later:
12% 615/system_server: 1.7% user + 10% kernel
10% 632/ActivityManager: 1.7% user + 8.9% kernel
1.7% 615/system_server: 1.7% user + 0% kernel
9.2% TOTAL: 1.8% user + 7.4% kernel
[ 05-07 21:03:22.719 615: 632 W/ActivityManager ]
Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
[ 05-07 21:03:22.729 615: 632 I/ActivityManager ]
Killing 4766:com.android.camera2/u0a50 (adj 0): user request after error
[ 05-07 21:03:23.019 129: 129 D/AK8975 ]
Compass CLOSE
[ 05-07 21:03:23.439 615: 625 W/InputMethodManagerService ]
Window already focused, ignoring focus gain of: com.android.internal.view.IInput
[email protected] attribute=null, token = [email protected]
41ed3308
Hello
I try ti make meteo wiget using zooper and tasker
I read an HTML pace and extract something like this
pioggia e schiarite
And i want show in wiget
Pioggia e schiarite
Can zooper recognize the HTML code?
Thanks
Mauro
I'm guessing by what you have written there that you want to get some content off of a webpage and put it into a Zooper widget?
It's easier to show:
https://www.youtube.com/watch?v=nLuoOhXuCvA
The splitting part may become somewhat involved.
Good Luck!
I and thanks for tour answer
I don't undestand if in tour video there is a solution for my problemi bit my english is not good
This is what i make with tasker
Sampeyre (48)
A1: HTTP Get [ Serverort:****************/meteo_italia_localita_valori.php?lid=7301&nome=Torino Path: Attributes: Cookies: Timeout:10 Mime Type:text/html Output File:wallapper/cerca2.html Continue Task After Errorn ]
A2: Read File [ File:wallapper/cerca2.html To Var:%Tempoora ]
A3: Variable Split [ Name:%Tempoora Splitter:alt=" Delete Baseff ]
A4: Variable Split [ Name:%Tempoora4 Splitter:" Delete Baseff ]
And the result is this
%Tempoora41 nubi sparse
If i pur it in zooper with tasker in the wiget show
nubi sparse
I want to show
nubi sparse
Can zooper make it?
Or ther is another way?
Thanks
Mauro
Hi,
I want to get the last outgoing call's image in my zooper widget.
I am trying to use tasker for that:
Code:
Caller (45)
A1: Test Phone [ Type:Contact Photo URI Data:%CONUM Store Result In:%called ]
A2: Load Image [ Source:%called Max Width Or Height:0 Respect EXIF Orientation:eek:ff ]
A3: Zooper Widget Pro Variable [ Configuration:#TCaller# = %called Package:org.zooper.zwpro Name:Zooper Widget Pro Variable Timeout (Seconds):0 ]
and in zooper, I have done:
Code:
bitmap->advanced->#TCaller#
which shows value:
Code:
content://com.android.contacts/display_photo/574
But this is not showing anything, but the default "open file" image.
Kindly help
Barud said:
Hi,
I want to get the last outgoing call's image in my zooper widget.
I am trying to use tasker for that:
Code:
Caller (45)
A1: Test Phone [ Type:Contact Photo URI Data:%CONUM Store Result In:%called ]
A2: Load Image [ Source:%called Max Width Or Height:0 Respect EXIF Orientation:eek:ff ]
A3: Zooper Widget Pro Variable [ Configuration:#TCaller# = %called Package:org.zooper.zwpro Name:Zooper Widget Pro Variable Timeout (Seconds):0 ]
and in zooper, I have done:
Code:
bitmap->advanced->#TCaller#
which shows value:
Code:
content://com.android.contacts/display_photo/574
But this is not showing anything, but the default "open file" image.
Kindly help
Click to expand...
Click to collapse
One thing, make sure your variable is passing into zooper, forget the image and just get text. Once I tried and couldn't get it to work, forgot that my profile was time dependant and I didn't run the task... Run your task if you haven't already...
Thanks for your reply.
If I only want the text, its working absolutely fine. only its the image which is not coming.
Hi there,
I have installed CyanogenMod on my Xperia Z1 Compact 2 weeks ago, and I was really happy with it, until I realized a very annoying issue: I don't receive any text message longer than 160 characters. I tried with another phone, with the same SIM card, and they arrive correctly. I also sent them from different phones, it doesn't make any difference. To troubleshoot further, I fired up adb and looked at the log entries when a short text message arrives:
[ 06-24 21:37:32.475 3251: 4805 V/GsmInboundSmsHandler ]
Unable to find carrier package: [], nor systemPackages: []
[ 06-24 21:37:32.485 3251: 4805 D/MmsService ]
getAutoPersisting
[ 06-24 21:37:32.485 2426: 2460 I/ActivityManager ]
Killing 9833:com.android.cellbroadcastreceiver/u0a5 (adj 13): empty for 1839s
[ 06-24 21:37:32.505 2426: 2460 I/ActivityManager ]
Killing 10059:com.google.android.youtube/u0a88 (adj 13): empty for 1841s
[ 06-24 21:37:32.525 2426: 2460 I/ActivityManager ]
Killing 8733:com.cyanogenmod.lockclock/u0a52 (adj 15): empty for 1842s
[ 06-24 21:37:32.535 2426: 2460 I/ActivityManager ]
Killing 10030:com.cyanogenmod.eleven/u0a41 (adj 15): empty for 1842s
[ 06-24 21:37:32.585 5856: 5856 V/Mms ]
onStart: #1 resultCode: -1 = Activity.RESULT_OK
[ 06-24 21:37:32.615 5856:13263 D/Mms ]
cancelNotification
[ 06-24 21:37:32.705 5856:13263 D/Mms ]
cancelNotification
[ 06-24 21:37:32.705 5856:13263 D/Mms ]
handleSmsReceived messageUri: content://sms/2 threadId: 189
[ 06-24 21:37:32.725 5856:13263 D/Mms ]
updateNotification: new message, adding sound to the notification
[ 06-24 21:37:32.725 2426: 2520 W/ActivityManager ]
getTasks: caller 10012 is using old GET_TASKS but privileged; allowing
[ 06-24 21:37:32.725 5856:13263 D/Mms ]
checkIsFullScreenMode: the top activity is: com.android.mms.ui.MessagingPreferenceActivity
[ 06-24 21:37:32.735 2426: 2426 I/ValidateNoPeople ]
Validating: 0|com.android.mms|123|null|10012
[ 06-24 21:37:32.735 2426: 2724 I/ValidateNoPeople ]
Executing: validation for: 0|com.android.mms|123|null|10012
[ 06-24 21:37:32.745 2426: 2426 D/lights.msm8974 ]
led [1000,6000] = ffffffff
[ 06-24 21:37:32.765 2426: 2724 I/ValidateNoPeople ]
final affinity: 0.5
[ 06-24 21:37:33.705 3869: 3953 I/Icing ]
Indexing AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B from com.google.android.gms
[ 06-24 21:37:33.735 3869: 3953 I/Icing ]
Indexing done AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B
[ 06-24 21:37:33.825 3869: 3953 I/Icing ]
Indexing AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B from com.google.android.gms
[ 06-24 21:37:33.825 3869: 3953 I/Icing ]
Indexing done AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B
Click to expand...
Click to collapse
This is how it looks like when long text message is received:
[ 06-24 21:35:19.465 3643: 6032 D/GCM ]
Message class com.google.f.a.a.i
[ 06-24 21:35:31.345 3869: 3953 I/Icing ]
Indexing AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B from com.google.android.gms
[ 06-24 21:35:31.365 3869: 3953 I/Icing ]
Indexing done AA223C2CACCAC63D7C40BD43F9ED2B9487F57A7B
[ 06-24 21:35:54.795 2946: 2946 I/wpa_supplicant ]
wlan0: WPA: Group rekeying completed with 00:24:fe:04:89:a1 [GTK=CCMP]
Click to expand...
Click to collapse
This is reproducible. So the phone gets some kind of data from the carrier. However, I don't know how to find out if the carrier sends invalid data OR if the phone messes it up.
Here is some information about the versions:
Android version 5.1.1
CyanogenMod version 12.1-20150606-NIGHTLY-amami
8974-AAAAANAZQ-10270045-39
My questions would be:
Has anyone heard of similar problem? After hours of Google, I found only one post where users had the same issue, and the solution was to buy new phone
Has anyone any idea how to troubleshoot this issue further?
Thanks for any hint.
Olivier
oliv4 said:
Hi there,
I have installed CyanogenMod on my Xperia Z1 Compact 2 weeks ago, and I was really happy with it, until I realized a very annoying issue: I don't receive any text message longer than 160 characters. I tried with another phone, with the same SIM card, and they arrive correctly. I also sent them from different phones, it doesn't make any difference. To troubleshoot further, I fired up adb and looked at the log entries when a short text message arrives:
.....
Olivier
Click to expand...
Click to collapse
You don't receive them at all or receive them after a delay? I'm on stock firmware, rooted, and have delayed messages when the text is greater the 160 characters.
Mirhawk said:
You don't receive them at all or receive them after a delay? I'm on stock firmware, rooted, and have delayed messages when the text is greater the 160 characters.
Click to expand...
Click to collapse
I don't receive them at all, even after several days.
Since my troubleshooting was blocked by the lack of tools or logs to dig further, I did the following:
Installed the latest stock firmware available (14.5.A.0.283) using flashtool -> Long SMS received successfully
Installed the latest CyanogenMod firmware available (12.1-20150625-NIGHTLY-amami -> Long SMS received successfully
So in the end, my problem is fixed, but I don't know if it was the stock firmware, which might have updated silently some other internal firmware, or if the problem was just in 12.1-20150606-NIGHTLY-amami and fixed in 12.1-20150625-NIGHTLY-amami. Since I have already spent hours on this problem, I don't want to investigate further...
Links:
www (dot) xperiablog.net (slash) 2015/05/27/new-firmware-14-5-a-0-283-certified-for-xperia-z1-z1-compact-and-z-ultra/
Hi all, here's my scoop:
First, rooted and using Magisk. I'm looking for a way to quickly switch between my eSIM (Fi) and SIM card (T-Mobile data-only) without having to navigate the menu. I believe I found the correct intent (android.telephony.action.CARRIER_CONFIG_CHANGED, flag=0x5000010) but Android stopped allowing background broadcasts in Oreo. So, when I try to run it as a broadcast
Code:
am broadcast -a android.telephony.action.CARRIER_CONFIG_CHANGED
I get
Code:
BroadcastQueue: Background execution not allowed: receiving Intent
in logcat. Does anyone have a suggestion on how to change the syntax to run this as an
Code:
am start
command? Thanks!
NOTE:If you're wondering why I am even doing this: I have a $10 2GB data-only plan with T-Mobile. This data-only plan includes Music Freedom, which means I can listen to all the music I want, and still take FI phone calls and texts over Hangouts.
I use FiSwitch from the Play Store, it works great especially with root as it automates switching for you. It also has wigets and QS tiles for quick access. :good:
Edit: I apologize as I didn't directly answer your question. I've not tried to use Tasker with switching.
Bologner said:
Hi all, here's my scoop:
First, rooted and using Magisk. I'm looking for a way to quickly switch between my eSIM (Fi) and SIM card (T-Mobile data-only) without having to navigate the menu. I believe I found the correct intent (android.telephony.action.CARRIER_CONFIG_CHANGED, flag=0x5000010) but Android stopped allowing background broadcasts in Oreo. So, when I try to run it as a broadcast
Code:
am broadcast -a android.telephony.action.CARRIER_CONFIG_CHANGED
I get
Code:
BroadcastQueue: Background execution not allowed: receiving Intent
in logcat. Does anyone have a suggestion on how to change the syntax to run this as an
Code:
am start
command? Thanks!
NOTE:If you're wondering why I am even doing this: I have a $10 2GB data-only plan with T-Mobile. This data-only plan includes Music Freedom, which means I can listen to all the music I want, and still take FI phone calls and texts over Hangouts.
Click to expand...
Click to collapse
Did you find a way to solve this?
I'm outside USA, so I can't use FiSwitch, but here in Spain we've got two mobile networks with eSim support, so I'm currently using my Pixel 3 with an eSim and I've got also a physical SIM, and I'd like to automate card switching. Same thing as you.
I've tried the new "Custom Setting" Tasker feature, and I've found some variable changes when you switch the SIM:
multi_sim_sms
multi_sim_voice_call
multi_sim_data_call
They all are set to 2 with eSIM, and 3 with physical SIM... I've tried manually changing those system variables using that "Custom Setting" Tasker feature, but it does nothing... I guess there's something more to be done to activate the change... but no idea what at the moment.
Thanks a lot.
The guy above mentioned FiSwitch, but I'm not sure it was clear that it has a widget that can do exactly this. (I do the same thing as you, but with Fi and mint mobile)
https://drive.google.com/file/d/1ErREmtX8UfzXSrOOhGpv_z2pJ7ZW7qYm/view?usp=drivesdk
In my previous post I didn't mention that the fiswitch solution didn't work for my device (pixel 4). When googling for a way to switch SIMs without going through a hundred menus, this post is one of the first that always came up. My previous post had some issues, which I hope are cleaned up. If there are other ways to accomplish this, someone please reply and let me know where.
Disclaimer: I'm not a tasker expert. Just an old guy that enjoys making shtuff work. The tasker stuff is after the green text (if you just want to scroll).
I have Google fi and at&t. All I wanted was a quick tile to switch from one sim to the other and back. For my setup I primarily use Fi for phone and sms. I switch between Fi and at&t data depending on who's fastest.
Fi has 3 cellular providers, TMobile, Sprint and US cellular.
There are 9 options for providers in Android global settings:
mobile_data1, mobile_data2, ... mobile_data9 (might also be a mobile_data (with out a numerical suffix), can't remember lol).
Your sim will use one for each provider. So I would have 3 providers for Fi and 1 for at&t. You will need to figure out which of the 9 you are using. Easy way would be to use autotools and read the values of these settings then just "flash" the value on the screen. If you have a computer and can use adb, that works too. You can use fiswitch to change Fi providers, then use the flash method to figure out the provider number.
In my case it was mobile_data4 (TMobile), mobile_data5 (Sprint), mobile_data6 (US cellular), and mobile_data8 (at&t).
When switching SIMs the active sim has all of its providers disabled. The providers for the new sim are then enabled. After that you update a setting (multi_sim_data_call) to tell Android which provider to use for data. You will want to disable data, update this setting, then enable data. You will also need to stop and start ril-daemon using a shell command (toggling air plane mode works too, but I think restarting ril is faster).
Note: because I use the Fi sim for phone, I use the multi_sim_voice_call setting to figure out which provider (ex 4,5,6) to use when switching data to fi.
I used autotools to set the globals because that's where I started (it's working great so I don't want to mess with it). There are probably several ways to do it.
Here's what I did in tasker:
SIM Swap Example (18)
<get current data provider>
A1: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Read Setting: true Timeout (Seconds):60 ]
<get current phone provider>
A2: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_voice_call
Input Type: String
Read Setting: true Timeout (Seconds):60 ]
A3: [X] Flash [ Textata: %multi_sim_data_call Voice: %multi_sim_voice_call Longff ]
<if att>
A4: If [ %multi_sim_data_call ~ 8 ]
<disable att>
A5: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data8
Input Type: Int
Value: 0 Timeout (Seconds):60 ]
<enable TMobile>
A6: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data4
Input Type: Int
Value: 1 Timeout (Seconds):60 ]
<enable sprint>
A7: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data5
Input Type: Int
Value: 1 Timeout (Seconds):60 ]
<enable us cellular>
A8: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data6
Input Type: Int
Value: 1 Timeout (Seconds):60 ]
<set data to fi phone provider>
A9: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Value: %multi_sim_voice_call Timeout (Seconds):60 ]
A10: Mobile Data [ Setff ]
<stop ril-daemon>
A11: Run Shell [ Command:stop ril-daemon Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
<else fi selected>
A12: Else
<disable Fi (TMobile)>
A13: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data4
Input Type: Int
Value: 0 Timeout (Seconds):60 ]
<disable Sprint>
A14: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data5
Input Type: Int
Value: 0 Timeout (Seconds):60 ]
<disable us cellular>
A15: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data6
Input Type: Int
Value: 0 Timeout (Seconds):60 ]
<enable at&t>
A16: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: mobile_data8
Input Type: Int
Value: 1 Timeout (Seconds):60 ]
<set data to at&t>
A17: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Value: 8 Timeout (Seconds):60 ]
A18: Mobile Data [ Setff ]
<stop ril-daemon>
A19: Run Shell [ Command:stop ril-daemon Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A20: End If
A21: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
<start ril-daemon>
A22: Run Shell [ Command:start ril-daemon Timeout (Seconds):0 Use Rootn Store Output In: Store Errors In: Store Result In: ]
A23: Mobile Data [ Setn ]
A24: [X] AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Read Setting: true Timeout (Seconds):60 ]
A25: [X] Flash [ Textata: %multi_sim_data_call Voice: %multi_sim_voice_call Longff ]
Hope this helps someone. You all have a great Christmas and New year!
I know this is old, but I was able to automate sim switching by disabling mobile data, then changing the multi_sim_data_call setting, then turning mobile data back on. In my case, my sim numbers are 4 and 8.
SIM Swap
A1: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Read Setting: true Timeout (Seconds):60 ]
A2: [X] Flash [ Text:%multi_sim_data_call Longff ]
A3: Mobile Data [ Setff ]
A4: If [ %multi_sim_data_call ~ 8 ]
A5: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Value: 4 Timeout (Seconds):60 ]
A6: Else
A7: AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Value: 8 Timeout (Seconds):60 ]
A8: End If
A9: Mobile Data [ Setn ]
A10: [X] AutoTools Secure Settings [ Configuration:Setting Type: Global
Name: multi_sim_data_call
Input Type: String
Read Setting: true Timeout (Seconds):60 ]
A11: [X] Flash [ Text:%multi_sim_data_call Longff ]