I'll leave my phone on the table for a while, come back, hit the home button, and a flood of notifications will pop up (I use groupme a lot so in extreme cases my phone will buzz and make noise for about 30 seconds to catch up with ~50 missed notifications).
Has anyone else experienced this issue? Any ideas at fixing it?*
I tried Push Notifications Fixer , but it didn't worked. I use WiFi . There is no problem on stock rom , even I've tested on other devices . I don't use Greenify too. Help here
Bump Anyone?
I have exactly the same problem.... But only when on WIfi, on mobile data it works flawlessly...
also tried PNF and "Wifi stay awake"... as soon as the display went off also the notifications (Whatsapp mainly) only come up when the power key is pressesd. I am running stock Motorola 4.4.4 .
As this is the third Moto G 2014 I am owning its definitly a hardware issue, as i tried different ROM based on stock like MicroKat, and also CM11 and CM12
msc2015 said:
I have exactly the same problem.... But only when on WIfi, on mobile data it works flawlessly...
also tried PNF and "Wifi stay awake"... as soon as the display went off also the notifications (Whatsapp mainly) only come up when the power key is pressesd. I am running stock Motorola 4.4.4 .
As this is the third Moto G 2014 I am owning its definitly a hardware issue, as i tried different ROM based on stock like MicroKat, and also CM11 and CM12
Click to expand...
Click to collapse
No it is not a hardware issuse , I think I've got a fix. Use WiFi Automatic or Wifi Advanced Locker App , which keeps WiFi on during sleep. By default WiFi cuts off connection after 15 Mins I think. Please , try it. I'll make a Fix thread for this , Soon.
@AmolAmrit03 Install Catlog.Leave the phone idle and send a few messages to your WhatsApp.Open Catlog and filter the logs by 'GCM'.Post the results here.
Tapped from my ①+②=❸
vaisakh7 said:
@AmolAmrit03 Install Catlog.Leave the phone idle and send a few messages to your WhatsApp.Open Catlog and filter the logs by 'GCM'.Post the results here.
Tapped from my ①+②=❸
Click to expand...
Click to collapse
Thank You bro , You looked here. Sure I'll do.
msc2015 said:
I have exactly the same problem.... But only when on WIfi, on mobile data it works flawlessly...
also tried PNF and "Wifi stay awake"... as soon as the display went off also the notifications (Whatsapp mainly) only come up when the power key is pressesd. I am running stock Motorola 4.4.4 .
As this is the third Moto G 2014 I am owning its definitly a hardware issue, as i tried different ROM based on stock like MicroKat, and also CM11 and CM12
Click to expand...
Click to collapse
Please do as instructed by @vaisakh7
@vaisakh7 I can be little late here , I mean It will take time for me to collect logcat for that.
@vaisakh here is the logcat
09-10 08:52:22.185 D/GCM (24317): Message class com.google.f.a.a.i
09-10 08:54:21.812 I/GCM (24317): GCM message com.whatsapp 0:1441855409385237%a3bffb5f00000031
09-10 08:56:25.990 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 08:57:00.446 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:02:39.216 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:06:00.378 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:10:40.193 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:13:20.573 D/GCM (24317): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
09-10 09:13:21.110 D/GCM (24317): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
09-10 09:16:33.736 I/GCM (24317): GCM message com.whatsapp 0:1441856741636718%a3bffb5f00000031
09-10 09:20:09.815 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:26:36.331 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:32:07.668 I/GCM (24317): GCM message com.whatsapp 0:1441857675103046%a3bffb5f00000031
AmolAmrit03 said:
09-10 08:52:22.185 D/GCM (24317): Message class com.google.f.a.a.i
09-10 08:54:21.812 I/GCM (24317): GCM message com.whatsapp 0:1441855409385237%a3bffb5f00000031
09-10 08:56:25.990 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 08:57:00.446 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:02:39.216 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:06:00.378 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:10:40.193 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:13:20.573 D/GCM (24317): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
09-10 09:13:21.110 D/GCM (24317): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
09-10 09:16:33.736 I/GCM (24317): GCM message com.whatsapp 0:1441856741636718%a3bffb5f00000031
09-10 09:20:09.815 D/GCM (24317): GcmService start Intent { act=com.google.android.c2dm.intent.REGISTER cmp=com.google.android.gms/.gcm.GcmService (has extras) } com.google.android.c2dm.intent.REGISTER
09-10 09:26:36.331 D/GCM (24317): Message class com.google.f.a.a.i
09-10 09:32:07.668 I/GCM (24317): GCM message com.whatsapp 0:1441857675103046%a3bffb5f00000031
Click to expand...
Click to collapse
This happens only with Whatsapp?Or with other IMs too?
Tapped from my ①+②=❸
vaisakh7 said:
This happens only with Whatsapp?Or with other IMs too?
Tapped from my ①+②=❸
Click to expand...
Click to collapse
With All other Applications with Push Notifications
AmolAmrit03 said:
No it is not a hardware issuse , I think I've got a fix. Use WiFi Automatic or Wifi Advanced Locker App , which keeps WiFi on during sleep. By default WiFi cuts off connection after 15 Mins I think. Please , try it. I'll make a Fix thread for this , Soon.
Click to expand...
Click to collapse
Can you share your settings for Wifi Automatic, please ? Thanks !
AmolAmrit03 said:
With All other Applications with Push Notifications
Click to expand...
Click to collapse
What GooglePlayServices version are you running?
Tapped from my ①+②=❸
[Gorgasm] said:
Can you share your settings for Wifi Automatic, please ? Thanks !
Click to expand...
Click to collapse
I deleted it. It didn't worked.
vaisakh7 said:
What GooglePlayServices version are you running?
Tapped from my ①+②=❸
Click to expand...
Click to collapse
7.8.99
AmolAmrit03 said:
7.8.99
Click to expand...
Click to collapse
This situation exits on mobile data too?
What device do you have?Have you tried to change ROMs/clean flash the current one?
Tapped from my ①+②=❸
vaisakh7 said:
This situation exits on mobile data too?
What device do you have?Have you tried to change ROMs/clean flash the current one?
Tapped from my ①+②=❸
Click to expand...
Click to collapse
It only happens in WiFi. I use Moto G 2014. This never happens on Stock nor on any other devices. It happens only on Custom ROMs. I think there is a Time Out for WiFi in all ROMs based on CM and AOSP.
AmolAmrit03 said:
It only happens in WiFi. I use Moto G 2014. This never happens on Stock nor on any other devices. It happens only on Custom ROMs. I think there is a Time Out for WiFi in all ROMs based on CM and AOSP.
Click to expand...
Click to collapse
Have you tried to test it on different routers/WiFi access points?
Tapped from my ①+②=❸
vaisakh7 said:
Have you tried to test it on different routers/WiFi access points?
Tapped from my ①+②=❸
Click to expand...
Click to collapse
My WiFi router is fine. There must be some settings in rom. I think my WiFi cuts off its connection after going into Sleep for some minutes.
Related
edit: not much use in this thread anymore, except maybe a good reference for people making an app
How about rebooting the phone? Will that work?
well yeah, but i don't think people will pay for an app that reboots your phone each time you change the volume settings
I think its, Runtime.getRuntime.exec("your command");
have you seen this?
http://forum.xda-developers.com/showpost.php?p=3434331&postcount=35
hamshu said:
I think its, Runtime.getRuntime.exec("your command");
Click to expand...
Click to collapse
do you think you could elaborate a little more?
i'm still a complete java noob
Process process = Runtime.getRuntime().exec("killall mediaserver");
That line should do it.
hamshu said:
Process process = Runtime.getRuntime().exec("killall mediaserver");
That line should do it.
Click to expand...
Click to collapse
i've got:
try {
Process process = Runtime.getRuntime().exec("killall mediaserver");
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
and it doesn't seem to do anything.
any ideas?
try {
Process process = Runtime.getRuntime().exec("sh");
DataOutputStream out = new DataOutputStream(process.getOutputStream());
out.writeBytes("killall mediaserver\n");
out.writeBytes("exit\n");
out.flush();
} catch (IOException e) {
e.printStackTrace();
}
try this, see what it does man
or try this:
Code:
try {
Class<?> execClass = Class.forName("android.os.Exec");
Method createSubprocess = execClass.getMethod("createSubprocess",
String.class, String.class, String.class, int[].class);
Method waitFor = execClass.getMethod("waitFor", int.class);
int[] pid = new int[1];
FileDescriptor fd = (FileDescriptor)createSubprocess.invoke(
null, "/system/xbin/bb/killall", "mediaserver", null, pid);
FileInputStream in = new FileInputStream(fd);
BufferedReader reader = new BufferedReader(new InputStreamReader(in));
String output = "";
try {
String line;
while ((line = reader.readLine()) != null) {
output += line + "\n";
}
} catch (IOException e) {
}
waitFor.invoke(null, pid[0]);
return output;
} catch (ClassNotFoundException e) {
throw new RuntimeException(e.getMessage());
} catch (SecurityException e) {
throw new RuntimeException(e.getMessage());
} catch (NoSuchMethodException e) {
throw new RuntimeException(e.getMessage());
} catch (IllegalArgumentException e) {
throw new RuntimeException(e.getMessage());
} catch (IllegalAccessException e) {
throw new RuntimeException(e.getMessage());
} catch (InvocationTargetException e) {
throw new RuntimeException(e.getMessage());
}
the last bit of code i posted dude i know works with an ls command, but with this, we are trying to spawn killall and pass the mediaserver argument, so i dont know if the stack will even handle this.... doesnt hurt to try though
corp769 said:
the last bit of code i posted dude i know works with an ls command, but with this, we are trying to spawn killall and pass the mediaserver argument, so i dont know if the stack will even handle this.... doesnt hurt to try though
Click to expand...
Click to collapse
From the little I know about Android Development, I think that it will work. Then again, I am not a Java coder nor a Android Developer(C# coding ftw). Sorry about getting the Java code wrong, like I stated, I don't code any Java.
It's cool...meltus, how's it going? You have a pm btw...
sorry guys, not had any success yet, but my girlfriends come round so i'll be away for a while
I suppose you need superuser privileges to kill the mediaserver.
This might work :
Process process = Runtime.getRuntime().exec("su -c \"killall mediaserver\"");
Meltus said:
sorry guys, not had any success yet, but my girlfriends come round so i'll be away for a while
Click to expand...
Click to collapse
Pervert lol JK
Zappletoo said:
I suppose you need superuser privileges to kill the mediaserver.
This might work :
Process process = Runtime.getRuntime().exec("su -c \"killall mediaserver\"");
Click to expand...
Click to collapse
this kinda works. i get a SU permission request, but it doesn't reboot the mediaserver. any ideas? ><
alritewhadeva said:
Pervert lol JK
Click to expand...
Click to collapse
lies
goddammit i hate this damn app lol ><
now i've run across another problem, which is, i just realised the system needs to be in read/write mode (im an idiot).
so:
Code:
try {
Process process = Runtime.getRuntime().exec("su");
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
works fine. makes an SU request popup thing appear, but...
Code:
try {
Process process = Runtime.getRuntime().exec("mount -o rw,remount /dev/block/mtdblock3 /system");
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
afterwards doesn't do anything. anyone know why this isn't working?
damn, i hate java lol
EDIT: I've also realised that
Code:
(Process process = Runtime.getRuntime().exec("su");
works fine but replacing it with
Code:
(Process process = Runtime.getRuntime().exec("reboot");
does nothing?!? wtf's going on!! lol
ONLY su works. no other commands seem to do anything
I'm not a coder by any means (more like a beta tester, but I can go through a code and 'see' it pretty easily) and I've often refered to this specific code for sms backup for root user app to do basic things..it basically uses two buttons and sends commands to the system. Check out the source code to see if it helps any: http://code.google.com/p/sms-backup-root/
Specifically the event when a button is pressed (notice it gets 'su' the same way you currently do, but does the actual commands differently):
Code:
backup.setOnClickListener(new Button.OnClickListener() {
public void onClick(View v) {
Process process = null;
DataOutputStream os = null;
try {
process = Runtime.getRuntime().exec("su");
os = new DataOutputStream(process.getOutputStream());
[B]os.writeBytes("cp /data/data/com.android.providers.telephony/databases/mmssms.db /sdcard \n");[/B]
[B]os.writeBytes("exit\n");[/B]
os.flush();
process.waitFor();
builder.setMessage("Backup done.. Found it in /sdcard/mmssms.db");
builder.show();
} catch (Exception e) {
return;
}
finally {
try {
if (os != null) {
os.close();
}
process.destroy();
} catch (Exception e) {
// Be Happy :)
}
}
return;
} });
It uses writebytes to send the code to the os. Try your code around that template and it may give you what you want.
Again im no coder, but there are a lot of open source apps that can give you a start towards what you want to do. Hope that helps!
p.s. love the audio mods, keep up the great work! Let me know if you want graphic work :]
Here you go.
Runtime rt = Runtime.getRuntime();
try {
Process process = Runtime.getRuntime().exec("su");
DataOutputStream os = new DataOutputStream(process.getOutputStream());
os.writeBytes("reboot");
os.flush();
} catch (IOException e) {
e.printStackTrace();
}
I just ran this on my phone and it rebooted.... Once you start the process, you use .writeBytes to "type to it". As if you were at the terminal and just typed "su"...
Instead of "reboot", you could do "killall mediaserver" or anything else you want to type to the console...
I thought I might put this on this forum for any of the developers to help out with porting this dialer to other devices
Enclosed in the zip is the files I have obtained from from the Nexus 5 that supports caller-id lookup and business lookup on the dialer. Although the google dialer works, it will not handle calls with the teleservice.apk that is included with CM11. If you make or receive calls with the the google dialer, it will still use the old dialer for call handling, incoming or outgoing. You cannot delete the original dialer because you have no way to answer or end calls.
The biggest reason I decided to make a push for this port is the incoming caller-id business lookup. This will be expanded to G+ information on Caller-ID in January and who knows what's next.
EDIT: New Information as follows:
In the package I've downloaded, Nexus 5 Experience for Nexus 4 and NONE of the MD5's matched the files I have. So, I decided to make a flashable zip of Teleservice.apk and the odex file in system\priv-app and telephonyprovider.apk and the odex file in system/app as well as the GoogleDialer.apk and odex file in system\priv-app.
The Nexus 5 Stock DOES use TelephonyProvider.
Although the com.android.phone hangs relentlessly, HOWEVER!!! I do get a Verizon Wireless' signal until I finish the FC with the "OK" button.
Any help with this? I think I am getting close.
This is what happens if I flash the dialer AFTER I've already established cellular service by flashing CM11, booting into the system, rebooting and flashing the dialer.
Code:
[ 11-23 20:26:56.699 2585: 2585 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.phone, PID: 2585
android.database.sqlite.SQLiteException: Can't downgrade database from version 589832 to 524296
at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:361)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:255)
at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:188)
at com.android.providers.telephony.TelephonyProvider.query(TelephonyProvider.java:465)
at android.content.ContentProvider.query(ContentProvider.java:855)
at android.content.ContentProvider$Transport.query(ContentProvider.java:200)
at android.content.ContentResolver.query(ContentResolver.java:461)
at android.content.ContentResolver.query(ContentResolver.java:404)
at com.android.internal.telephony.dataconnection.DcTracker.createAllApnList(DcTracker.java:1910)
at com.android.internal.telephony.dataconnection.DcTracker.onRecordsLoaded(DcTracker.java:1257)
at com.android.internal.telephony.dataconnection.DcTracker.handleMessage(DcTracker.java:2139)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5062)
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:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at dalvik.system.NativeStart.main(Native Method)
This is what happens if I flash the dialer at the same time I flash the rom.
Code:
[ 11-23 15:44:14.477 7986: 7986 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.phone, PID: 7986
java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4392)
at android.app.ActivityThread.access$1400(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1467)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5062)
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:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS
at android.os.Parcel.readException(Parcel.java:1461)
at android.os.Parcel.readException(Parcel.java:1415)
at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:2382)
at android.app.ActivityManagerNative.broadcastStickyIntent(ActivityManagerNative.java:96)
at com.android.internal.telephony.uicc.IccCardProxy.broadcastIccStateChangedIntent(IccCardProxy.java:344)
at com.android.internal.telephony.uicc.IccCardProxy.setExternalState(IccCardProxy.java:387)
at com.android.internal.telephony.uicc.IccCardProxy.setExternalState(IccCardProxy.java:393)
at com.android.internal.telephony.uicc.IccCardProxy.<init>(IccCardProxy.java:117)
at com.android.internal.telephony.PhoneProxy.<init>(PhoneProxy.java:85)
at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:141)
at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:59)
at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:391)
at com.android.phone.PhoneApp.onCreate(PhoneApp.java:38)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4389)
... 10 more
I also included a full logcat of each type of instance and the files I am flashing.
http://www.tinozplace.com/moto-kitkat/GoogleDialerProject-NotFlashable.zip
Thanks to anyone getting involved. If you can't help, please at least try to turn some developers onto this post.
I've done a bit of apk reverse engineering before (disassembled smali code and what not). Do you have any background info on what's happening with it now? Crashes at certain points, lockups, or just general "it doesn't do what it's supposed to and there is no feedback"?
djuniah said:
I've done a bit of apk reverse engineering before (disassembled smali code and what not). Do you have any background info on what's happening with it now? Crashes at certain points, lockups, or just general "it doesn't do what it's supposed to and there is no feedback"?
Click to expand...
Click to collapse
Here is what I know so far from my own experiences and research:
- If you flash the dialer alone, it works well.
- If you flash the dialer and the Teleservices.apk (odex too) it will force close or possibly cause a bootloop.
My research:
-Teleservice calls googledialer up to prompt the user to answer the call, includes business caller id, etc.
-TelephonyProvider is a thing of the past with the google dialer.
My decompile showed differences in about 10-15 files and about 10-20 additions/subtractions of smali files to the apk.
I'd be more than willing to give you an adb logcat.
abuttino said:
Here is what I know so far from my own experiences and research:
- If you flash the dialer alone, it works well.
- If you flash the dialer and the Teleservices.apk (odex too) it will force close or possibly cause a bootloop.
My research:
-Teleservice calls googledialer up to prompt the user to answer the call, includes business caller id, etc.
-TelephonyProvider is a thing of the past with the google dialer.
My decompile showed differences in about 10-15 files and about 10-20 additions/subtractions of smali files to the apk.
I'd be more than willing to give you an adb logcat.
Click to expand...
Click to collapse
Ok, i'll see if i can dig into it over the weekend. Man, this is one of the things i miss about safestrap. I always had one slot for testing things like this. Made it a lot more painless.
I'll see about getting it on github and I'll continue to try to get more attention to this thread
EDIT: It's on github...
https://github.com/abuttino/teleservice.apk
First post edited.
abuttino said:
First post edited.
Click to expand...
Click to collapse
More explorations on this..
I tried a ROM with no teleservice.apk, telephonyprovider.apk and googledialer.apk, then installed them once I got into the system. Unfortunately that didn't work to pick cell service back up, and any phone settings I tried just crashed the dialer.
Here is the crash:
Code:
I/ActivityManager( 833): START u0 {act=android.intent.action.MAIN flg=0x4000000 cmp=com.android.phone/.CallFeaturesSetting} from pid 2190
E/AndroidRuntime( 2190): FATAL EXCEPTION: main
E/AndroidRuntime( 2190): Process: com.google.android.dialer, PID: 2190
E/AndroidRuntime( 2190): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.phone/com.android.phone.CallFeaturesSetting}; have you declared this activity in your AndroidManifest.xml?
E/AndroidRuntime( 2190): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1628)
E/AndroidRuntime( 2190): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1424)
E/AndroidRuntime( 2190): at android.app.Activity.startActivityForResult(Activity.java:3423)
E/AndroidRuntime( 2190): at android.app.Activity.startActivityForResult(Activity.java:3384)
E/AndroidRuntime( 2190): at android.app.Activity.startActivity(Activity.java:3626)
E/AndroidRuntime( 2190): at android.app.Activity.startActivity(Activity.java:3594)
E/AndroidRuntime( 2190): at android.preference.PreferenceActivity.onHeaderClick(PreferenceActivity.java:1058)
E/AndroidRuntime( 2190): at android.preference.PreferenceActivity.onListItemClick(PreferenceActivity.java:1030)
E/AndroidRuntime( 2190): at android.app.ListActivity$2.onItemClick(ListActivity.java:319)
E/AndroidRuntime( 2190): at android.widget.AdapterView.performItemClick(AdapterView.java:298)
E/AndroidRuntime( 2190): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
E/AndroidRuntime( 2190): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
E/AndroidRuntime( 2190): at android.widget.AbsListView$3.run(AbsListView.java:3638)
E/AndroidRuntime( 2190): at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 2190): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 2190): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2190): at android.app.ActivityThread.main(ActivityThread.java:5062)
E/AndroidRuntime( 2190): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2190): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 2190): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 2190): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 2190): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 833): Force finishing activity com.google.android.dialer/.settings.GoogleDialerSettingsActivity
D/wpa_supplicant( 1006): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
D/wpa_supplicant( 1006): wlan0: Control interface command 'SIGNAL_POLL'
D/wpa_supplicant( 1006): nl80211: survey data missing!
W/ActivityManager( 833): Activity pause timeout for ActivityRecord{41da0018 u0 com.google.android.dialer/.settings.GoogleDialerSettingsActivity t2 f}
Once I cleared data, the com.android.phone was just relentlessly hanging with the permission problem stated in the main post.
I would hope that some developers are looking at this thread and this helps out.
Don't remember where I found this ( somewhere on xda) but flash this it will keep your regular dialer apk also so you'll see your old one in app drawer too.
https://copy.com/MFw1d
Sent from my MB886 using Tapatalk
tember1214 said:
Don't remember where I found this ( somewhere on xda) but flash this it will keep your regular dialer apk also so you'll see your old one in app drawer too.
https://copy.com/MFw1d
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
The dialer also comes with Caller-ID lookup through google businesses (Places) and Google+. This is the purpose of the porting project, to have the dialer "fully functional" instead of just the business search for dialing.
abuttino said:
The dialer also comes with Caller-ID lookup through google businesses (Places) and Google+. This is the purpose of the porting project, to have the dialer "fully functional" instead of just the business search for dialing.
Click to expand...
Click to collapse
You mean this? Correct?
{
"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"
}
Sent from my MB886 using Tapatalk
Yes. But it doesn't actually function because the telephonyprovider.apk and teleservices.apk only talk to the aosp dialer.
Sent from my XT926 using Tapatalk
Oh got ya I don't think I've even got a phone call since I've flashed this. Sorry thought I could maybe help.
Sent from my MB886 using Tapatalk
If you know of any developers or can do a small social networking outreach (a post on Google+ or Twitter) that would help.
Sent from my XT926 using Tapatalk
It can be ported because Google has got it working on both Nexus 5 and Nexus 4 already. But I really don't know how to do it.
mushan3420 said:
It can be ported because Google has got it working on both Nexus 5 and Nexus 4 already. But I really don't know how to do it.
Click to expand...
Click to collapse
Thank you for at least taking a look at it. I appreciate it.
Do you have any idea of where to start?
Sent from my XT926 using Tapatalk
abuttino said:
Thank you for at least taking a look at it. I appreciate it.
Do you have any idea of where to start?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
Please compare TeleService.apk in Nexus 4 with Nexus 5. Google has aready did an example porting it from one phone to another.
mushan3420 said:
Please compare TeleService.apk in Nexus 4 with Nexus 5. Google has aready did an example porting it from one phone to another.
Click to expand...
Click to collapse
There are NO differences in the SMALI code, none at all. I compared two bone stock versions from the Nexus 5 and Nexus 4
Here are the differences in the apk.
abuttino said:
There are NO differences in the SMALI code, none at all. I compared two bone stock versions from the Nexus 5 and Nexus 4
Here are the differences in the apk.
Click to expand...
Click to collapse
So the difference is the DPI? OK. Just change the DPI of images, and sign the modified apk with Android Platform Key.
And then, if it still doesn't work, please compare the teleservice.apk from Nexus 4 or 5 with the one from AOSP.
I am not sure if this will help, but please kindly have a try.
mushan3420 said:
So the difference is the DPI? OK. Just change the DPI of images, and sign the modified apk with Android Platform Key.
And then, if it still doesn't work, please compare the teleservice.apk from Nexus 4 or 5 with the one from AOSP.
I am not sure if this will help, but please kindly have a try.
Click to expand...
Click to collapse
I have already compared the Nexus 5 to AOSP and there are at least 10 smali files with differences that add/subtract hundreds of lines of code, and add/subtract serveral DPI files.
Compared the Nexus 5 to the Moto X as well.. About the same amount of difference..
EDIT.
abuttino said:
I have already compared the Nexus 5 to AOSP and there are at least 10 smali files with differences that add/subtract hundreds of lines of code, and add/subtract serveral DPI files.
Compared the Nexus 5 to the Moto X as well.. About the same amount of difference..
EDIT.
Click to expand...
Click to collapse
Ok, I separated the smali files with differences in two folders, one for CM11/AOSP and one for Nexus 5. There were also file count differences. I notated them in a text file as well as the png I just posted.
http://www.tinozplace.com/moto-kitkat/TeleserviceDiff.zip
Thanks for helping!
Hi there, dSploit's developer here .... I recently purchased the LG Watch Urbane and I was wondering, is there any known method to root it? I'd like to port a minimal version of dSploit/zANTI to Android wear .... you know, the "James Bond" effect
Thanks
evilsocket said:
Hi there, dSploit's developer here .... I recently purchased the LG Watch Urbane and I was wondering, is there any known method to root it? I'd like to port a minimal version of dSploit/zANTI to Android wear .... you know, the "James Bond" effect
Thanks
Click to expand...
Click to collapse
Root method for watch r works.
suzook said:
Root method for watch r works.
Click to expand...
Click to collapse
Thanks suzook, I'm trying this method and it all goes fine until part 11, if i reboot into recovery mode after flashing the TWRP image, I only see this image and can't do anything, just keep pushing the button to restart the device into normal mode:
{
"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"
}
How can I fix this?
evilsocket said:
Thanks suzook, I'm trying this method and it all goes fine until part 11, if i reboot into recovery mode after flashing the TWRP image, I only see this image and can't do anything, just keep pushing the button to restart the device into normal mode:
How can I fix this?
Click to expand...
Click to collapse
Did you flash the correct twrp???? There is a specific one for the urbane.
suzook said:
Did you flash the correct twrp???? There is a specific one for the urbane.
Click to expand...
Click to collapse
ooops, I'm afraid I've flashed the one for the R ... I didn't find any Urbane specific TWRP here https://twrp.me/Devices/ so I just used that one ... how can I fix this?
evilsocket said:
ooops, I'm afraid I've flashed the one for the R ... I didn't find any Urbane specific TWRP here https://twrp.me/Devices/ so I just used that one ... how can I fix this?
Click to expand...
Click to collapse
Try this, ..http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452 then start over with the correct twrp for our device, then flash supersu.
suzook said:
Try this, ..http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452 then start over with the correct twrp for our device, then flash supersu.
Click to expand...
Click to collapse
I was able to flash the stock recovery, but when I boot into it I get the same icon
evilsocket said:
I was able to flash the stock recovery, but when I boot into it I get the same icon
Click to expand...
Click to collapse
Try flashing stock image
suzook said:
Try flashing stock image
Click to expand...
Click to collapse
where can I find it?
evilsocket said:
where can I find it?
Click to expand...
Click to collapse
flash this one it should stick unlike the others
https://dl.twrp.me/bass/
suljo94 said:
flash this one it should stick unlike the others
https://dl.twrp.me/bass/
Click to expand...
Click to collapse
Thanks! That worked flawlessly and now I have the TWRP up and runnig ... I've flasshed the UPDATE-SuperSU-v2.46.zip archive but it doesn't seem to work.
If i exec "su" on adb shell, it just gets stuck, if I try to open the app from the wear itself, I see the following exception ( on the logcat ):
D/AndroidRuntime( 1923): Shutting down VM
E/AndroidRuntime( 1923): FATAL EXCEPTION: main
E/AndroidRuntime( 1923): Process: eu.chainfire.supersu, PID: 1923
E/AndroidRuntime( 1923): java.lang.RuntimeException: Unable to start activity ComponentInfo{eu.chainfire.supersu/eu.chainfire.supersu.MainActivity}: android.util.AndroidRuntimeException: You cannot combine swipe dismissal and the action bar.
E/AndroidRuntime( 1923): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
E/AndroidRuntime( 1923): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
E/AndroidRuntime( 1923): at android.app.ActivityThread.access$800(ActivityThread.java:151)
E/AndroidRuntime( 1923): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
E/AndroidRuntime( 1923): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1923): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 1923): at android.app.ActivityThread.main(ActivityThread.java:5254)
E/AndroidRuntime( 1923): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 1923): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 1923): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime( 1923): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
E/AndroidRuntime( 1923): Caused by: android.util.AndroidRuntimeException: You cannot combine swipe dismissal and the action bar.
E/AndroidRuntime( 1923): at com.android.internal.policy.impl.PhoneWindow.requestFeature(PhoneWindow.java:324)
E/AndroidRuntime( 1923): at com.android.internal.policy.impl.PhoneWindow.generateLayout(PhoneWindow.java:3374)
E/AndroidRuntime( 1923): at com.android.internal.policy.impl.PhoneWindow.installDecor(PhoneWindow.java:3675)
E/AndroidRuntime( 1923): at com.android.internal.policy.impl.PhoneWindow.getDecorView(PhoneWindow.java:1945)
E/AndroidRuntime( 1923): at android.app.Activity.initWindowDecorActionBar(Activity.java:2122)
E/AndroidRuntime( 1923): at android.app.Activity.getActionBar(Activity.java:2082)
E/AndroidRuntime( 1923): at com.actionbarsherlock.internal.ActionBarSherlockNative.initActionBar(Unknown Source)
E/AndroidRuntime( 1923): at com.actionbarsherlock.internal.ActionBarSherlockNative.getActionBar(Unknown Source)
E/AndroidRuntime( 1923): at android.support.v4.app.FragmentActivity.getSupportActionBar(Unknown Source)
E/AndroidRuntime( 1923): at eu.chainfire.supersu.compat.FragmentActivity.onCreate(Unknown Source)
E/AndroidRuntime( 1923): at eu.chainfire.supersu.MainActivity.onCreate(Unknown Source)
E/AndroidRuntime( 1923): at android.app.Activity.performCreate(Activity.java:5990)
E/AndroidRuntime( 1923): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
E/AndroidRuntime( 1923): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
E/AndroidRuntime( 1923): ... 10 more
W/ActivityManager( 613): Force finishing activity 1 eu.chainfire.supersu/.MainActivity-Material
Click to expand...
Click to collapse
Do I need to flash a wear specific supersu zip package? If so, where can I find it?
I've managed to make this work using this SuperSU version http://rootjunkysdl.com/getdownload.php?file=LG G Watch/Root/Wear-SuperSU-v2.40.zip !
Thanks all.
evilsocket said:
I've managed to make this work using this SuperSU version http://rootjunkysdl.com/getdownload.php?file=LG G Watch/Root/Wear-SuperSU-v2.40.zip !
Thanks all.
Click to expand...
Click to collapse
I deleted the app via twrp and I was good to go
What is the point of rooting? What can be gained?
aaronc_98 said:
What is the point of rooting? What can be gained?
Click to expand...
Click to collapse
Build.prop & init.d tweaks, I am working on a ROM with some tweaks should be ready for testing soon. I did get the watch to last almost 3 days without charge
sharky481232 said:
Build.prop & init.d tweaks, I am working on a ROM with some tweaks should be ready for testing soon. I did get the watch to last almost 3 days without charge
Click to expand...
Click to collapse
Cool- I hadn't seen anyone working on ROM's so I look forward to your work! Love SD...
evilsocket said:
Hi there, dSploit's developer here .... I recently purchased the LG Watch Urbane and I was wondering, is there any known method to root it? I'd like to port a minimal version of dSploit/zANTI to Android wear .... you know, the "James Bond" effect
Thanks
Click to expand...
Click to collapse
dSploit is awesome, let us know what you come up with ?
Hopefully sharky481232 can also get this watch to respond faster/speed up. (stock is very laggy ATM) Thanks in advance for your work, I'll be a guinea pig
jeffc83 said:
Hopefully sharky481232 can also get this watch to respond faster/speed up. (stock is very laggy ATM) Thanks in advance for your work, I'll be a guinea pig
Click to expand...
Click to collapse
Just an update:
I got some tweaks working, is a bit faster, less lag, battery is lasting almost 48hrs with normal usage. I didn't have much time to work on it last week hoping for sometime this week. All I have left to do is get some working init.d tweaks. Hoping for a test build available this weekend maybe sooner depending on how work is for me this week.
Awesome...anything that you have done will be a huge improvement over stock! (the serious lag is starting to piss me off, especially when I reboot it twice a day) Standing by, ready to flash and test
{
"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"
}
This is LineageOS 14.1 for w7. The builds are very very experimental and it is recommended to NOT use this as daily ROM.What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Video Playback
Audio
Sensors
Camera
What's not working :
Everything is working, if you have any bug, report it with logs.
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Builds: https://www.androidfilehost.com/?w=files&flid=146209 (Make sure to have lastest TWRP)
Google Apps: http://opengapps.org/
Credits :
Quarx
GrinningFerret
mosimchah
Me
CyanogenMod Team
Contributors
SlimShady's
GrinningFerret
Source Code: https://github.com/Nougat-w7
ROM OS Version: 7.1.1 Nougat
Version Information
Status: Beta
Created 2016-10-05
Last Updated 2016-10-05
Bug reports are welcome but make sure to include proper descriptions and logs(or screenshots if necessary)! ?
I have cm 14 from September, can I dirty flash this latest one?
D1358531 said:
I have cm 14 from September, can I dirty flash this latest one?
Click to expand...
Click to collapse
We'd highly recommend you to flash it clean, but of course you can try it.
GrinningFerret said:
We'd highly recommend you to flash it clean, but of course you can try it.
Click to expand...
Click to collapse
Thanks...I'll let you know if it works
No problem dirty flashing.
I'll wait until camera will work .
I've tested it for couple of days and it's really smooth , it brings new life to the L90 .
Ok i've seen some battery drain ,but it's ok , this builds are still experimental .
Great Work .
Thank you guys for doing this. The rom installs fine on a D405n. The camera doesn't work as you said, but I can't get the bluetooth to work either. Here's some logs:
Code:
10-06 17:55:03.712 18367 18367 E BluetoothVendorJni: register_com_android_bluetooth_btservice_vendor:
10-06 17:55:03.760 1358 1563 D BluetoothManagerService: Message: 20
10-06 17:55:03.760 1358 1563 D BluetoothManagerService: Added callback: [email protected]:true
10-06 17:55:03.764 18367 18367 I BluetoothVendorJni: classInitNative: succeeds
10-06 17:55:03.764 18367 18367 D BluetoothAdapterState: make() - Creating AdapterState
10-06 17:55:03.768 18367 18367 I bt_btif : init
10-06 17:55:03.770 18367 18382 I BluetoothAdapterState: Entering OffState
10-06 17:55:03.771 18367 18383 W bt_osi_thread: run_thread: thread id 18383, thread name stack_manager started
10-06 17:55:03.771 18367 18383 I bt_stack_manager: event_init_stack is initializing the stack
10-06 17:55:03.771 18367 18383 I bt_core_module: module_init Initializing module "osi_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initialized module "osi_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initializing module "bt_utils_module"
10-06 17:55:03.772 18367 18383 I bt_utils: init_soc_type
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initialized module "bt_utils_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initializing module "btif_config_module"
10-06 17:55:03.772 18367 18383 E bt_osi_config: config_new unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
10-06 17:55:03.772 18367 18383 W %s unable to load config file: %s; using backup.: init
10-06 17:55:03.772 18367 18383 E bt_osi_config: config_new unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
10-06 17:55:03.772 18367 18383 W %s unable to load backup; attempting to transcode legacy file.: init
10-06 17:55:03.772 18367 18383 E %s unable to load XML file '%s': %d: config_t *btif_config_transcode(const char *)
10-06 17:55:03.772 18367 18383 E %s unable to transcode legacy file; creating empty config.: init
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: timer_create_internal unable to create timer with clock 9: Invalid argument
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: The kernel might not have support for timer_create(CLOCK_BOOTTIME_ALARM): https://lwn.net/Articles/429925/
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: See following patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=CLOCK_BOOTTIME_ALARM
10-06 17:55:03.773 18367 18383 F libc : system/bt/osi/./src/alarm.c:161: alarm_new_internal: assertion "false" failed
10-06 17:55:03.774 18367 18383 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 18383 (stack_manager)
Can someone port systemui from 14th to cm13?
Star_king12 said:
Can someone port systemui from 14th to cm13?
Click to expand...
Click to collapse
Use themes "Nougat" (Play Store or XDA Labs)
stojmenovski said:
Thank you guys for doing this. The rom installs fine on a D405n. The camera doesn't work as you said, but I can't get the bluetooth to work either. Here's some logs:
Click to expand...
Click to collapse
Will be fixed in next build, thanks
SlimShady's said:
Will be fixed in next build, thanks
Click to expand...
Click to collapse
awesome
Sent from my LG-D410 using Tapatalk
First of all, great job on this ROM! I immediately fell in love with the new UI, and I can't wait to use it as my daily driver!
That being said, nearly all the apps lagged to the point of non-functionality, Bluetooth kept crashing, the SMS app had a weird issue where if you opened an existing conversation, clicked on the textbox to reply, the textbox would disappear and the keyboard would be unusable. About 5 seconds later it would crash. I tried replacing the default app with Google Messenger and that did the same thing. YouTube also (I noticed that was one of the things not working before, so I figured I'd test it out) was stuck loading the home screen for forever. I could open the settings panel but it ignored me when I tried to click on the "search" button. The Camera just gave a black screen (didn't even bother to crash). The Contacts app worked perfect, though.
I was testing on a D415. I'm back to CM13 for now, but I eagerly await the next update!
BellaMay95 said:
First of all, great job on this ROM! I immediately fell in love with the new UI, and I can't wait to use it as my daily driver!
That being said, nearly all the apps lagged to the point of non-functionality, Bluetooth kept crashing, the SMS app had a weird issue where if you opened an existing conversation, clicked on the textbox to reply, the textbox would disappear and the keyboard would be unusable. About 5 seconds later it would crash. I tried replacing the default app with Google Messenger and that did the same thing. YouTube also (I noticed that was one of the things not working before, so I figured I'd test it out) was stuck loading the home screen for forever. I could open the settings panel but it ignored me when I tried to click on the "search" button. The Camera just gave a black screen (didn't even bother to crash). The Contacts app worked perfect, though.
I was testing on a D415. I'm back to CM13 for now, but I eagerly await the next update!
Click to expand...
Click to collapse
Give us logs, bug reports are useless without logs.
mosimchah said:
Give us logs, bug reports are useless without logs.
Click to expand...
Click to collapse
Done. Hope this helps... I did the flag *:W so it grabbed warnings, errors, and fatal errors but the log is like 5,000 lines!!
So what I did while making the logcat, first I tried turning on Bluetooth and waited for the dialog box to appear telling me that Bluetooth kept crashing and asking if I wanted to kill the app.
Then, I replicated the messaging failure. I opened a new thread (because there were no existing threads at that time), starting typing, then I hit the back button to get out of it. Everything was fine up until I tried to click on the box to type some more. Then the box disappeared (the keyboard was still up there) and the app froze and finally crashed.
Also I saw a whole bunch of stuff about the camera crashing so hopefully there's enough information about that.
The bug report (as a .txt file) just barely exceeded the file size limit at 532 kb (the limit is 512) so I compressed it in a .zip file. Hope it helps! Let me know if you'd like me to test anything more - I dug out my mom's old l90 (it's also a d415) so I can test stuff without ruining the setup on my daily driver.
I don't know if I did it right, but I've attached the log taken from SysLog app.
I use ROM Toolbox Pro, and when I went to the root browser, I wasn't able to change any of the permissions. Also, when using CM file manager, I wasn't able to read the external SD card even though I have root access. In my previous post, I attached a log, would either of those problems be seen in the log?
Sent from my LG-D415 using XDA Free mobile app
D1358531 said:
I use ROM Toolbox Pro, and when I went to the root browser, I wasn't able to change any of the permissions. Also, when using CM file manager, I wasn't able to read the external SD card even though I have root access. In my previous post, I attached a log, would either of those problems be seen in the log?
Click to expand...
Click to collapse
Did you clean flash?
mosimchah said:
Did you clean flash?
Click to expand...
Click to collapse
Yes.
D1358531 said:
Yes.
Click to expand...
Click to collapse
Are you using SuperSU? Can you see if it'll work with a different file manager, maybe try solid explorer?
Hi all,
for Android 9, I used Magisk module "libsecure_storage companion" that allowed my device to restore bluetooth pairings (e.g. with a watch) after reboot. Without that module, any pairings are lost. Unfortunately, the module does not seem to work with Android 10. When enabled, I cannot enable WiFi anymore. Is there any workaround for that?
Thanks for any suggestion.
I can confirm same issue on Note9 Q beta.
Even when putting the libsecure_storage.so directly in system library folders and disabling the secure storage props.
At data/log/bluedroiddump, log gives things like that :
Code:
11-30 11:33:00.432--BluetoothManagerService -- ===== BOOT_COMPLETED (N960FXXU4ZSK7) ===== false false false false
11-30 11:33:00.433--HFBMS-bind PSC
11-30 11:33:00.440--HFBMS-bind fail by mEnableExternal(false) from android
11-30 11:33:02.355--HFBMS-bind fail by mEnableExternal(false) from com.android.server.telecom
11-30 11:33:02.442--HFBMS-bind fail by mEnableExternal(false) from com.android.server.telecom
11-30 11:33:02.445--HFBMS-bind fail by mEnableExternal(false) from com.android.systemui
11-30 11:33:02.491--HFBMS-bind fail by mEnableExternal(false) from com.android.systemui
11-30 11:33:03.652--HFBMS-bind fail by mEnableExternal(false) from com.android.phone
11-30 11:33:08.876--BluetoothManagerService -- User unlocked. userHandle : 0
11-30 11:33:40.398--BluetoothAdapter -- semSetStandAloneBleMode(true) called by PID : 16479 @ null
11-30 11:33:40.399--BluetoothAdapter -- enableRadio() called by PID : 16479 @ null
11-30 11:33:40.400--BluetoothManagerService -- enableBle(null) BT ManagerService enableBle called
11-30 11:33:40.661--AdapterState Entering BT OFF
11-30 11:33:40.872--BluetoothManagerService BLUETOOTH_SERVICE_CONNECTED: 1
11-30 11:33:40.876--AdapterState Current state: BT OFF, message: BLE_TURN_ON
11-30 11:33:40.878--AdapterState Entering Turning BLE ON
11-30 11:33:40.935--btsnoop.cc -- Config HCI log for external : enable=0
11-30 11:33:48.002--btif_storage.cc -- before ssSupport
11-30 11:33:48.002--btif_storage.cc -- after ssSupport = 1 vkSupport = 0
11-30 11:33:48.004--btif_storage.cc -- Failed to get getKeyIVLen = -19
11-30 11:33:48.005--btif_storage.cc -- Failed to get getKeyIVLen = 0
11-30 11:33:48.005--btif_storage.cc -- Failed to get getKeyIVLen = 0
11-30 11:33:48.005--btif_storage.cc -- Failed to get getKeyIVLen = 0
11-30 11:33:48.137--[5008]{0029})(04::0)
11-30 11:33:48.138--[5008]{002A}(20::80)(04::0)
11-30 11:33:48.138--PFQU-connect : empty
11-30 11:33:48.138--AdapterState Current state: Turning BLE ON, message: BLE_STARTED
11-30 11:33:48.147--AdapterState Entering BLE ON
11-30 11:33:48.154--BluetoothManagerService BLUETOOTH_SERVICE_CONNECTED: 2
11-30 11:33:48.166--BtGatt.GattService registerServer(android.uid.system)
The "after ssSupport = 1" seems to confirm that secure storage is detected as active. Which cause our issue.
Any update on that issue ?
Hey
Just fixed it on my Note9 :highfive:
Could you provide me libbluetooth.so file from your /system/lib64 folder?
I have to compare with the Note9 one, it should be very similar.
Arteush said:
Hey
Just fixed it on my Note9 :highfive:
Could you provide me libbluetooth.so file from your /system/lib64 folder?
I have to compare with the Note9 one, it should be very similar.
Click to expand...
Click to collapse
Of course, here it is (as ZIP-Archive)... Thanks a lot for looking at it!
Arteush said:
Hey
Just fixed it on my Note9 :highfive:
Could you provide me libbluetooth.so file from your /system/lib64 folder?
I have to compare with the Note9 one, it should be very similar.
Click to expand...
Click to collapse
How did you resolve? I have S10 and i have the same issue
atlantix1 said:
Of course, here it is (as ZIP-Archive)... Thanks a lot for looking at it!
Click to expand...
Click to collapse
No problem!
As expected the library is very similar to the N9.
Try this, it should work.
Ivymike52 said:
How did you resolve? I have S10 and i have the same issue
Click to expand...
Click to collapse
Lot of search and try with a dissembler and a hex editor :silly:
Arteush said:
Lot of search and try with a dissembler and a hex editor :silly:
Click to expand...
Click to collapse
Great the file above the last message works, now pairing stay after reboot.
But another question: if i set "Visibility telephone" to on, it reset to off, why?
Ivymike52 said:
Great the file above the last message works, now pairing stay after reboot.
But another question: if i set "Visibility telephone" to on, it reset to off, why?
Click to expand...
Click to collapse
Not sure to understand, I don't have such option on my N9. Could you send a screenshot?
Arteush said:
No problem!
As expected the library is very similar to the N9.
Try this, it should work.
Click to expand...
Click to collapse
Many, many thanks again! It works!
This option:
{
"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"
}
Arteush said:
No problem!
As expected the library is very similar to the N9.
Try this, it should work.
Click to expand...
Click to collapse
Very nice work, thank you!
atlantix1 said:
Many, many thanks again! It works!
Click to expand...
Click to collapse
Great!
Ivymike52 said:
This option:
Click to expand...
Click to collapse
Hmm.. I don't have this setting so..
@atlantix do you have same issue?
Arteush said:
Great!
Hmm.. I don't have this setting so..
@atlantix do you have same issue?
Click to expand...
Click to collapse
Hm, I don't have that setting either. No matter if I use stock or your modified library...
After placing libary in /system/lib64 is there anything else to do? I mean changing something in build.prop? Thanks for help so far.
Arteush said:
Great!
Hmm.. I don't have this setting so..
@atlantix do you have same issue?
Click to expand...
Click to collapse
I have this setting and it works
Olli2k said:
After placing libary in /system/lib64 is there anything else to do? I mean changing something in build.prop? Thanks for help so far.
Click to expand...
Click to collapse
I recommend to not modify anything else if it works.
If you want, not sure yet but maybe add/replace "ro.securestorage.knox=false" and "ro.securestorage.support=false" in build.prop and replace "start" by "stop" in /system/vendor/etc/init/secure_storage_daemon_kinibi.rc or similar file. To avoid secure storage service to start without need.
But you could loose and have to add again your stored wifi passwords with this!
Arteush said:
I recommend to not modify anything else if it works.
If you want, not sure yet but maybe add/replace "ro.securestorage.knox=false" and "ro.securestorage.support=false" in build.prop and replace "start" by "stop" in /system/vendor/etc/init/secure_storage_daemon_kinibi.rc or similar file. To avoid secure storage service to start without need.
But you could loose and have to add again your stored wifi passwords with this!
Click to expand...
Click to collapse
Thx, so after placing this file, headset pairings is still there after reboot, so yes it works, but I was hoping to find a solution for my not to be able to pair with a galaxy watch in this as well. This problem is still up, but I will try your suggestions.
Arteush said:
No problem!
As expected the library is very similar to the N9.
Try this, it should work.
Click to expand...
Click to collapse
Tested and works too on s10e, I'm glad you did it because most people (including me) are not good enough to use disassembler and reverse Samsung modules. Thanks you very much!
Btw it works perfectly with my galaxy watch, answering to the post above.