Database Develop

Signing made easy.... [ Updated July/2009 ]

Note, this will not work if your SDK or the path that you place this in has any spaces in the dir name!
An Example of this is c:\users\Nikki and Stephen\sdk\tools
Try to put the SDK and the contents of the zip in a dir where the names are all together and not like the one above.
Ok, so I have made a batch file that will automate the entire process of setting up to use the signing tool made by JF. This batch file will set the CLASSPATH, set the PATH, install the registries, let you sign the files manually, and let you push/pull files to the phone.
In order to use this you should have downloaded the sdk already. Simply extract all of the files into the tools dir of your sdk, and run autosign.bat follow the instructions and go through the options one by one, starting with 1 working through 4. You can however, put the contents of this zip anywhere on your computer and it will work. It is just better to put them into the tools dir of your SDK. Especially for the consideration of future versions.
Enjoy,
Stericson
Autosign .zip: http://www.DroidBin.com/Androidstuff/signing.zip

You are one hard working, man.
Thanks.

awesome sir! looking foward to using this great tool....in a virtual machine...with windows xp.....on my mac.....ha ha

Please let me know how it works. It works for me, but there are so many different computer configurations. This is also only tested and expected to work for xp and vista....I don't know if it will work for other o/s versions.
Stericson

will give it a whirl as soon as my cupcake is done baking.

Doesn't work for me on vista, running a 64bit machine, I think it has something to do with how my computer is set up though because of the error message I get

can you be specific as too the error message and what you are doing when it happens?
Stericson

This is badass! Ive been playing with it this morning and all I can say is........
{
"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"
}
Now no one has an excuse to not be able to create their own theme!

yeah, it's a great tool, thanks for the help in getting it all work stericson.

Thanks for the autosign batch. It seems like it would make things easier. Now if I could just get it to work....
Here is the error I am getting when running it. (Either via right click or manually through the bat file)
**************
Signing File!
**************
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
I have it installed in my c:\and_sdk\tools\ folder
Any ideas?
EDIT: Updating Java to most recent version fixed the problem.
Thanks!

tinpusher1 said:
Thanks for the autosign batch. It seems like it would make things easier. Now if I could just get it to work....
Here is the error I am getting when running it. (Either via right click or manually through the bat file)
**************
Signing File!
**************
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
I have it installed in my c:\and_sdk\tools\ folder
Any ideas?
EDIT: Updating Java to most recent version fixed the problem.
Thanks!
Click to expand...
Click to collapse
I downloaded j2re-1_4_2_19-windows-i586-p.exe but still gives me error...
------------------------------
Exception in thread "main" java.lang.UnsupportedClassVersionError: testsign (Unsupported major.minor version 50.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
File signed successfully if no Errors above.
-------------------------------
Anyone have any idea?

Awesome work! Thank You! I got this to work the first time, and I can finally start to make a theme now. At least I had time to come up with some ideas.
I just want to mention that it was brandenk's thread that got me to look into this. Thanks to all that put in the hard work. Thank you Stericson.

Why isn't this a sticky?

Mac OS X?
Hi all,
There are a few Mac OS X users on this site that would like to do this as well. Obviously we can't use BAT and EXE files in our native environment, but we can use a UNIX-based approach. Does anyone have an intelligible or pre-packaged version of how to do this in UNIX? (I say intelligible because the Google document on this is pretty unintelligible.)

Question, I have a theme in my folder c:\sdk\tools. Do I need to leave the in a zipped file or extract it? The theme would be c:\sdk\tools\update.zip?

Leave it zipped and just sign the update.

I would love to be able to sign my new theme in Ubuntu 9.04.. Anyone know how?
p.s have been searching/reading until 2:30 am am and since 8 am this morning. Driving me nuts.

problem flashing update.zip
I am having some issues flashing my update.zip files. I am getting an error of not being able to find the update path. I am trying to flash a font that I found online. I noticed after signing the zip with the .bat file provided that there is a new folder titled "META-INF". From downloading other signed fonts this looks correct but the ones I have downloaded contain another tree of folders within META-INF that eventually lead to a file titled "update-script". I am assuming that is what is missing from my signed file. What am I doing wrong?

hmmm should be other files inside of the meta folder yes.....just do this, copy the folders from those other font upddates, assuming they are only font updates, and put them in your current meta folder. the update script should be the same.....
if any other problems just post your update.zip...one of us will take a look at it.
Stericson

im on vista and i keep getting an error saying
'java' is not recognized as an internal or external command, operable program or batch file.
can anyone help me with this?

Porting the Google dialer

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!

[Problelm] Push Notifications Bug

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.

lava iris alfa- xposed not working

hi guys i just installed xposed on my phone(lava iris alfa)
its still showing the red line saying-The latest version of Xposed is currently not active. Did you install the framework and reboot?
tried alredy:
uninstalled and again installed......
reboots................
Here is the log..
-----------------
Dec 6, 2015 7:54:10 AM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'LAVA_iris alfa_S107_20141216' with fingerprint 'LAVA/alfa/iris_alfa:4.4.2/KOT49H/20141216.225934:user/release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.SPRDResources
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
please help........
i am just a beginner at all this trying to learn, so please explain in detail...
{
"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"
}

Have you flashed the zip file?
its called something like xposed-v78-sdk22-arm.zip

Ranchoolal said:
hi guys i just installed xposed on my phone(lava iris alfa)
its still showing the red line saying-The latest version of Xposed is currently not active. Did you install the framework and reboot?
tried alredy:
uninstalled and again installed......
reboots................
Here is the log..
-----------------
Dec 6, 2015 7:54:10 AM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'LAVA_iris alfa_S107_20141216' with fingerprint 'LAVA/alfa/iris_alfa:4.4.2/KOT49H/20141216.225934:user/release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.SPRDResources
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
please help........
i am just a beginner at all this trying to learn, so please explain in detail...
Click to expand...
Click to collapse
Could you give us some more information about your device? Android version, for example. Seems you are running Android 4.4.2, right?
savvy1968 said:
Have you flashed the zip file?
its called something like xposed-v78-sdk22-arm.zip
Click to expand...
Click to collapse
It seems he is running Android KitKat, so the typical installation way for Lollipop doesn't apply for him.

if its kk you dont need to flash anything just install XposedInstaller_3.0_alpha4.apk and you should be good to go.
in settings have you ticked the disabled resource hooks? if you have untick it cos thats very rarely needed.

savvy1968 said:
if its kk you dont need to flash anything just install XposedInstaller_3.0_alpha4.apk and you should be good to go.
in settings have you ticked the disabled resource hooks? if you have untick it cos thats very rarely needed.
Click to expand...
Click to collapse
XposedInstaller_3.0_alpha4.apk is for Lollipop. The last working version for KitKat is v2.7 experimental1, which can be found in the Xposed repo.
@Ranchoolal:
Maybe check this thread for more infos and a possible fix for issues with Xposed on latest KitKat ROMs.

hi guys,
thanks for reply.....
i installed XposedInstaller_3.0_alpha4.apk and now........
the red line is still flashing........
but on the next page of frame work is like this...........
NOTES:
I have android 4.2.2
the screenshots on the very first post were of v2.7 experimental1
nothing happens if i enable resource hooks option
please also tell about it if i should enable it or not
thanks in advance

Ranchoolal said:
hi guys,
thanks for reply.....
i installed XposedInstaller_3.0_alpha4.apk and now........
the red line is still flashing........
but on the next page of frame work is like this...........
NOTES:
I have android 4.2.2
the screenshots on the very first post were of v2.7 experimental1
nothing happens if i enable resource hooks option
please also tell about it if i should enable it or not
thanks in advance
Click to expand...
Click to collapse
We can not see any of your screenshots. Please upload them as attachement. I guess, you need 10 posts to be able to upload some attachements. Try to reach this limit and come back with all screenshots.
Furthermore, v2.7 should be the correct version for your device. After you have installed the Xposed Installer, go th Framework section and click on Install. Afterwards reboot. If you have done this, it would be good if you could provide a Xposed log file (if you don't know how to do this, search for it on XDA, keywords "how to logcat").

orville87 said:
We can not see any of your screenshots. Please upload them as attachement. I guess, you need 10 posts to be able to upload some attachements. Try to reach this limit and come back with all screenshots.
Furthermore, v2.7 should be the correct version for your device. After you have installed the Xposed Installer, go th Framework section and click on Install. Afterwards reboot. If you have done this, it would be good if you could provide a Xposed log file (if you don't know how to do this, search for it on XDA, keywords "how to logcat").
Click to expand...
Click to collapse
its still showing the red line saying-The latest version of Xposed is currently not active. Did you install the framework and reboot?
here is the log-
-----------------
Dec 9, 2015 2:51:22 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'LAVA_iris alfa_S107_20141216' with fingerprint 'LAVA/alfa/iris_alfa:4.4.2/KOT49H/20141216.225934:user/release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.SPRDResources
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)

Ranchoolal said:
its still showing the red line saying-The latest version of Xposed is currently not active. Did you install the framework and reboot?
here is the log-
-----------------
Dec 9, 2015 2:51:22 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'LAVA_iris alfa_S107_20141216' with fingerprint 'LAVA/alfa/iris_alfa:4.4.2/KOT49H/20141216.225934:user/release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.SPRDResources
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
Try to use Xposed v2.6 or even below this instead of v2.7 experimental1. Seems that v2.7 is causing issues on devices that are running pre-KitKat Android. Source.

i am using v2.6 and thats not working

v2.1.2
v2.1.2

v2.1.2=v2.1.3

v2.1.3=v2.1.4

v2.2 beta 1

v2.2 beta 2 = v2.2 beta 1 = v2.2

v2.3

v2.3=v2.3.1

v2.4
everything goes fine before reboot but as soon as my phone starts again it keeps shows a lit black screen.....

[ROM][UNOFFICIAL] LineageOS 14.1 for LG L90

{
"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?