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!
Related
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?
[THEMES] Super Swiftkey (140+ added free themes) THREAD CLOSED!
Thread is Closed!!!!
No longer supporting this mod here due to users not wanting to be patient and not following forum rules!
I may keep updating but no longer here!!! Thank those who can't read rules and think my time is theirs to dictate!!!!!!
I DON'T EVEN USE THIS MOD!
BYE!
DJ
TEAMBLACKOUT
SUPER SWIFTKEY
Hello Everyone,
Super Swiftkey is a version of Swiftkey which includes custom themes by me, @sonnysekhon and other very helpful xda members/developers.
We will keep it up to date by posting our modified version in the TBO updater as soon as an update to Swiftkey hits our Play Store.
I will update when TIME allows.
DO NOT REPOST THIS ANYWHERE...MANY DEVELOPERS GAVE US PERMISSION TO DISTRIBUTE..PLEASE HONOR THEM.
Beta will be updated only for research not every one will get themed.
ATTENTION EVERYONE:
FOLLOW XDA RULES...DO NOT ASK FOR ETA .........WE FOLLOW THEM ON PUSHBULLET....I GET NOTIFIED RIGHT AWAY....:highfive::good:....So if it's not a hard update it should only take a few min to check if anything changed in themes and drop our goodies in. Longer if they changed things or I have other obligations. I will report what's up. Ok now the education is over go have fun. [emoji14]
Updated = June 24 2016
Stable SuperSwiftkey:
*****Notice******
New versions for MM and N also arm64 so PAY ATTENTION please!
ALSO:
******If you are on LP M or N and it fails install you'll need to uninstall the old apk then install the new....They change the certificates from LP MM and N to the old one due to making it cross api.
*******NEW******* 6/24/2016
Uploads will now be in the TeamBlackout Updater
Here: TeamBlackOut Updater This is v6.2.1 with Firebase notifications, so No need for pushbullet anymore!
{
"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"
}
Click to expand...
Click to collapse
Zip's to flash = "Fixes sync and will help with system installed SwiftKey." "BACKUP FIRST" Flash in recovery.
PAY ATTENTION TO THE ZIP LABLES!!!!!!!!! no label is for older devices.......... LP-Lollipop. MM-Marshmallow N-??
SuperSwiftkey folder for the older ones=
"Depreciated
https://www.androidfilehost.com/?w=files&flid=19897"
If you want older ones from the updater go here: TBO Resources
Click to expand...
Click to collapse
Small Change Log:
Updated stable apk's and zips!
Don't wanna wait for us or want beta updates...then you can self update, remove unwanted themes here http://forum.xda-developers.com/showthread.php?t=2958328 for personal use ONLY! NO posting it...Only post YOUR themes YOU create not others.
If we can keep this fun we will keep it updated....So don't be a party pooper...Just relax and enjoy SuperSwiftKey!
Also remember we theme it NOT mod it, please keep this thread on theming NOT modding it. - we will NOT recreate paid themes so don't even ask! Ok now that's covered.....
Enjoy!
DJ, Sonny and all the contributors!
A few sample screens below...MANY more inside!!!
wow looks real sweet, too bad I missed the free offer.
You are my hero
excellent! i hope more people mod this now, i dont really like the dark theme on the Swiftkey Beta.
look good but possible to add few more colors? i want green
I thank you for your hard work. Hope to see more colors coming during your free time. Cheers.
will this work on the swiftkey beta?
I've got an error when compiling using apk manager:
"res\drawable-mdpi\sym_keyboard_search.png:0: Originally defined here.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\D3V1L\AppData\Local\Temp\A
PKTOOL7988472857239820988.tmp, -I, C:\Users\D3V1L\apktool\framework\1.apk, -S, C
:\Users\D3V1L\Desktop\android-sdk-windows\apk_manager\other\..\projects\Swift.ap
k\res, -M, C:\Users\D3V1L\Desktop\android-sdk-windows\apk_manager\other\..\proje
cts\Swift.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\D3V1L\AppData\Local\Temp\APKTOOL7988472857239820988.tmp, -I, C:\Users\D3V1L
\apktool\framework\1.apk, -S, C:\Users\D3V1L\Desktop\android-sdk-windows\apk_man
ager\other\..\projects\Swift.apk\res, -M, C:\Users\D3V1L\Desktop\android-sdk-win
dows\apk_manager\other\..\projects\Swift.apk\AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more
Press any key to continue . . ."
Any Guess??
finsmaniac02 said:
will this work on the swiftkey beta?
Click to expand...
Click to collapse
Probably not, this is for the version shown in the pics.
rinxas said:
I've got an error when compiling using apk manager:
"res\drawable-mdpi\sym_keyboard_search.png:0: Originally defined here.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\D3V1L\AppData\Local\Temp\A
PKTOOL7988472857239820988.tmp, -I, C:\Users\D3V1L\apktool\framework\1.apk, -S, C
:\Users\D3V1L\Desktop\android-sdk-windows\apk_manager\other\..\projects\Swift.ap
k\res, -M, C:\Users\D3V1L\Desktop\android-sdk-windows\apk_manager\other\..\proje
cts\Swift.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\D3V1L\AppData\Local\Temp\APKTOOL7988472857239820988.tmp, -I, C:\Users\D3V1L
\apktool\framework\1.apk, -S, C:\Users\D3V1L\Desktop\android-sdk-windows\apk_man
ager\other\..\projects\Swift.apk\res, -M, C:\Users\D3V1L\Desktop\android-sdk-win
dows\apk_manager\other\..\projects\Swift.apk\AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more
Press any key to continue . . ."
Any Guess??
Click to expand...
Click to collapse
Did you replace entire folders in Apkmanager? If so, just replace the contents of the folders.
same error here
replaced all files except the fonts, but when compiling an error occurs
idea?
edit:worked for me
you dont have to change the whole folders,just the files inside.the it will work...
thx
Hi, after modding, the sizes of the alphabets appear over-sized. Upon checking, I realize that the mdpi-4 you had had some oversized icons. For instance, the "abc_icon.png" should be 50x50, however the mdpi-4 had 60x55. I am a little helpless here. The same problem applies with the drawables.
I will list out specifically the icons, and hope that it will help you save time:
These icons in both drawable and drawable-mdpi:
Size should be in 50x50 for the following:
abc_icon.png
alt_icon.png
delete_icon_preview.png
done_icon_preview.png
go_icon_preview.png
menu_icon_preview.png
mode_icon.png
mode_icon_preview.png
next_icon_preview.png
send_icon_preview.png
shift_icon.png
shift_icon_active.png
smiley_icon_preview.png
Size should be in 32x52 for the following:
btn_popup_key_normal.9.png
btn_popup_key_blank.9.png
I sincerely thank you for your time.
hey bro, its giving me some java errors and i even tried re-installing java to my computer so pretty much cant gewt it to work.... any ways you could explain about the process a little more. or maybe a pm with a file lol
thanks anyways
JokerAce said:
Hi, after modding, the sizes of the alphabets appear over-sized. Upon checking, I realize that the mdpi-4 you had had some oversized icons. For instance, the "abc_icon.png" should be 50x50, however the mdpi-4 had 60x55. I am a little helpless here. The same problem applies with the drawables.
I will list out specifically the icons, and hope that it will help you save time:
These icons in both drawable and drawable-mdpi:
Size should be in 50x50 for the following:
abc_icon.png
alt_icon.png
delete_icon_preview.png
done_icon_preview.png
go_icon_preview.png
menu_icon_preview.png
mode_icon.png
mode_icon_preview.png
next_icon_preview.png
send_icon_preview.png
shift_icon.png
shift_icon_active.png
smiley_icon_preview.png
Size should be in 32x52 for the following:
btn_popup_key_normal.9.png
btn_popup_key_blank.9.png
I sincerely thank you for your time.
Click to expand...
Click to collapse
Sorry about that, I overlooked those since I have a hdpi device.
You can resize all those images at http://pixlr.com/editor/, go to Image/Image Size.
I will update the OP to say that the MOD is for HDPI devices only.
sonnysekhon said:
Sorry about that, I overlooked those since I have a hdpi device.
You can resize all those images at http://pixlr.com/editor/, go to Image/Image Size.
I will update the OP to say that the MOD is for HDPI devices only.
Click to expand...
Click to collapse
I can also apply changes in size to the .9.png as well?
JokerAce said:
I can also apply changes in size to the .9.png as well?
Click to expand...
Click to collapse
Yes, also make sure you change other .9 images and keyboard background images. Basically I left it all untouched except for the preview images because those are shared in the hdpi folders as well.
sonnysekhon said:
Yes, also make sure you change other .9 images and keyboard background images. Basically I left it all untouched except for the preview images because those are shared in the hdpi folders as well.
Click to expand...
Click to collapse
I do not have to use any 9.png compiler right?
JokerAce said:
I do not have to use any 9.png compiler right?
Click to expand...
Click to collapse
Okay I tried. It failed to compile the .9.png files. I am really helpless with .9.png files. Could you please help me? Just those 2 files, in 32x52.
JokerAce said:
Okay I tried. It failed to compile the .9.png files. I am really helpless with .9.png files. Could you please help me? Just those 2 files, in 32x52.
Click to expand...
Click to collapse
Ok, I just tried resizing them. The problem is that upon resizing the black border is compromised. You have to recolor it again.
And it's not just the 2 images, you have to replace all the images in mdpi and with my WP7 images and resize them all. Then recolor the black border.
It's a lot of work. Get started I will try to help out when I have some free tome tomorrow .
i resized all the icons to work for mdpi, however i dunno how to edit the values in the public file in the values folder, and i get a error when i try and recompile the apk cuz it says the file sizes dont match up, any idea how to fix this? it seems to be all thats stopping me from having a full mdpi version of this skin
twilightvanquisher said:
i resized all the icons to work for mdpi, however i dunno how to edit the values in the public file in the values folder, and i get a error when i try and recompile the apk cuz it says the file sizes dont match up, any idea how to fix this? it seems to be all thats stopping me from having a full mdpi version of this skin
Click to expand...
Click to collapse
Can you post your edited images and I will be able to see what's causing the error.
Also, you don't have to edit the public.xml.
This thread is for the development progress of the Dell Streak 7 running Jelly Bean Android 4.1.2 using Cyanogenmod 10 as the basis.
It is now being moved up a version, from Alpha 0.4 to Alpha 1.0.
This reverts us to the ICS-B4 partition layout. The reason being is that Dell decieded to be different and it causes problems with the sdcard fuse daemon. But switching to this layout, it allowed the sdcard daemon to work correctly and give us more space.
Developers:
giveen - CM10 Port / Kernel Updates
geramy - Sound and other fixes.
DJ_Steve - Sound idea that worked.
Thanks:
Cyanogenmod team - for making the port actually pretty easy
geramy - for all your incredible help getting sound going.
snargledorf - basically rebuilding CM9 for the Dell Streak 7 , to which I was able to base my work off of.
DJ_Steve - for teaching me and all the tips and putting up with my annoying questions
My wife - giving me grace and putting up with the hours I put into this
(oops forgot a couple people)
_motley - for clues onto framebuffers and overlays failing, without him it would have never booted
Borkata - for help with wifi and other little hints.
pengus77 - for helping me fix wifi on CM10.1 (and invertly new changes on CM10 had the same problem)
https://github.com/giveen/android_device_dell_streak7
Alpha v1.1E
Working:
Boots!!!
Touchscreen
Hapatic feedback
External SD
Internal Storage (shows full space, can install apps to it, but you cannot store anything on it)
Power button
Brightness
Root
Capacitive buttons
Bluetooth (audio as well, so far the only way audio works)
WIFI
MTP to external SD
Sound
Headphones - are a bit loud and volume control doesn't always work
Speakers - is a bit quiet and sometimes takes a moment for it to adjust volumes
Not Working:
camera (what do you think I am...a miracle worker?)
GPS (turns on but doesn't lock on)
Sensors
What else doesn't work...I"m still checking it all out.
{
"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"
}
Recognized Donators:
azrael
Mohamad R. (let me know your screen name and I'll change this )
Robert Trier
Bradley F.
Fixed a bunch and it looks like surfaceflinger is segfaulting, will look at tomorrow morning
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
giveen said:
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
attach your init.rc, init.goldfish.rc and init.streak7.rc files, I guess 2 people looking over this could provide more help than just one
See your PM's
Are you guys "teasing" all us Streak 7 owners with this Jelly Bean Rom thread?
ICS just dropped and Jelly Bean...?
What is the difference and is Jelly Bean going to be a easier build if so?
I thought Jelly Bean was just ascetic changes, not a revamp.
Please tell me you are really developing the rom cause I was about to gift it to a friend but now im holding off.... I would hate to indian give it....
Jb has better performance just like every new version of Android. Also a bunch if new features
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
ashyk36 said:
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
Click to expand...
Click to collapse
Don't ask for ETA's.. just be patient and wait like everyone else, we don't provide ETA's as we could have errors or other variables that could influence the completion of roms (from server going down to zombie apocalypse)
Who has Jelly Bean on the Dell Streak 7 booting right now....yeah this guy does.
I'd be interested in seeing if my flash script is stable enough to work on more then my 1 sucessful test flash.
If/when you're willing to seed me a copy to test stuff on my end, I'd be happy to report back on it. But I have a ton of backlog to keep me busy, so take your time.
Oh: I'm still a little confused, do you have a working version of CWM for ICS partitions?
I can blind-port a version if you give me the geometries of it.
(I'd like to see the output from a live system to check against the nvflash config)
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
giveen said:
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
Click to expand...
Click to collapse
get a logcat and see what errors are occurring
This isn't my first rodeo. Lol. Logcat will be up in the morning.
Sent from my Nexus 7
as long as we get everything working I guess its all good
Would love for camera to work.
Sent from my Nexus 7
take HS7R8 camera drivers and cross reference wih nexus 7 ones to see if anything is different (other than addressing... unless its the same in which case it may just work)
You'd need the source code for the camera drivers for that to work.
All we have are the binaries for them
Exactly.
Sent from my Nexus 7
Camera was working in froyo to my knowledge why not give the source for that a try? (unless that too is also just binaries)
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?