Related
ParanoidAndroid build from sources with the new 2.6.53 kernel from TheWhisp; see more detail about this project on http://www.paranoid-rom.com/
please, when you have a problem, attach a logcat
-How to install:
Transfer the .zip file to your SD card
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes.
Reboot and enjoy!
Remember: if you come from any other version of android that isn't PA jb (or PA jb based) you'll have to wipe data from CWMR
-Gapps:
use jb-20121017-KonstaKANG on modaco
http://www.mediafire.com/?qscnhfuadsujki1
-How to check file's hash:
i recommed you to install hashtab, so just right-click on the file, click propriety and go to hash file tab
-2.99:
updated to android 4.2
it uses modified libstagefright from Rashed97
built whit gcc 4.6 + some trick to reduce apk size
hash: [md5sum] 3f572d3b240ad124f35e93bd0aa240e1
http://depositfiles.com/files/4m6sx4gre
-2.55:
first release, see what works/not works down here
http://depositfiles.com/files/spbfpz8xj
Working:
2D & 3D acceleration with triple-buffering (Butter UI)
Camera (Barcode Scanner mode also works)
GPS
Headset
Lights
Sensors
Touchscreen
USB Mass Storage
keys
Not Working:
Telephony (calling, mobiledata & messaging)
bluetooth
wifi
sdcard isn't recognized
Partially working:
Video camera (can capture video, but saved media will have artifacts/low FPS)
OMX video encoders/decoders
Not working:
USB tethering
Wifi tethering
Thanks to:
Motafoca
TheWhisp, squadzone & all contributors associated with the shared Samsung msm7x27 jellybean kernel & device config used as a base for the galaxy5 port
nend for MAD Manager & general assistance
KonstaT for his reduced gapps-jb package
Rashed97 for his modified libstagefright
richie161cfc (madteam) for testing many test build
All other testers for your patience & support - thank you.
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
XdaNoob98 said:
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
thanks; did you tested it? if yes can you attach a logcat?
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
sixline said:
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
Click to expand...
Click to collapse
thanks for reporting, to fix button problem you can try to substitute the folder usr inside system with the one from psyke's cm10
for wifi try substitude the folder wifi with the one from psyke's cm10
next update will fix them all; can you attach a logcat?
manuel100 said:
thanks; did you tested it? if yes can you attach a logcat?
Click to expand...
Click to collapse
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
XdaNoob98 said:
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
ok
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
Click to expand...
Click to collapse
here: http://depositfiles.com/files/0edassb32
i need a logcat for the sound problem
updated the rom to pa 2.99 (4.2), i need some testers and many logcats
Like i said i will test it a give logcats in six days if it isn't too long?
Sent from my GT-S5360 using xda premium
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
IDntKnwHowUse said:
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
Click to expand...
Click to collapse
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
E/AndroidRuntime( 2510): FATAL EXCEPTION: main
E/AndroidRuntime( 2510): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4384)
E/AndroidRuntime( 2510): at android.app.ActivityThread.access$1300(ActivityThread.java:145)
E/AndroidRuntime( 2510): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1271)
E/AndroidRuntime( 2510): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2510): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2510): at android.app.ActivityThread.main(ActivityThread.java:4978)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 2510): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2510): Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:155)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:59)
E/AndroidRuntime( 2510): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:470)
E/AndroidRuntime( 2510): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4381)
E/AndroidRuntime( 2510): ... 10 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at java.lang.Class.classForName(Native Method)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:217)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:172)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:148)
E/AndroidRuntime( 2510): ... 14 more
E/AndroidRuntime( 2510): Caused by: java.lang.NoClassDefFoundError: com/android/internal/telephony/SamsungMSMRIL
E/AndroidRuntime( 2510): ... 18 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
E/AndroidRuntime( 2510): ... 18 more
W/ActivityManager( 1494): Process com.android.phone has crashed too many times: killing!
I/Process ( 2510): Sending signal. PID: 2510 SIG: 9
I/ActivityManager( 1494): Process com.android.phone (pid 2510) has died.
Click to expand...
Click to collapse
OK I'm so exited because paranoid is the best rom for me:thumbup:
Sent from my GT-S5360 using xda premium
Paranoid Android doesn't work! It boots after 10 minutes. FC's on telephony every second
Sent from my GT-I5500 using xda premium
manuel100 said:
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
Click to expand...
Click to collapse
You have to point the RIL to boardconfig. As I said here:
Paul L. said:
Is the RIL working? You can make it work by pasting the propietary RIL java class to the optional telephony package and pointing it out in the boardconfig by using the example from the lastest commit from codeworkx to the CM10.1 staging branch
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Which, by the way, it's not enough. You will have to adapt SamsungMSMRIL to Android 4.2
Why don't you ask some other developers to help you? Or simply post it to madteam?
Sent from my superphone in 2000 BC
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
brewy said:
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Well, the dev's doing the right thing. He is building the ROM from source code, not change/theming someone else's work!. He is doing the right thing asking for logcats. That is how its actually done!.
You might not have been here when development on cm7 started. It was pretty bad. Everything was broken/not working. Psyke eventually fixed everything and made it what it is now.
So stop your nonsense talk and try contributing to the development.
Sent from my GT-I9300 using xda-developers app
Hello thanks for your work bro why not you come to madteam , there you will get more tester and your development goes more fast.
We found that some ppl can not access the TapJoy.com in some area , So we change the 5 app limit count to 15.
Fonter is the best font manager on Android,not only support CHANGE SYSTEM FONT also support CHANGE APP's FONT, also have thousands of fonts for you.
Fonter is desigined to change your phone's font, or just change an app's font. It's super easy to use, change every app's font every day!
If you find Fonter is useful， please rate a five star. If you have any problems, please email([email protected]) us or feedback in this thread before rate one star. THANK YOUR !
Help to translate this app to your language
English: http://osvya69.oneskyapp.com/collaboration/project?id=36345
Download
repo.xposed.info/module/git.hub.font
PLEASE NOTE: THIS IS A BETA TEST APP, BACKUP YOUR DEVICES DATA BEFORE CHANGE YOUR SYSTEM FONT.
FEATURES:
<b>* Support to change an app's font</b>
<b>*</b> Support Samsung,OnePlus,part of Color OS phones to change font perfectly (NO ROOT needed)
<b>*</b> Support generate Huawei,Xiaomi theme package, using theme manager to change font on those phones (NO ROOT needed）
<b>*</b> Support HTC,Motorola,Lenovo,Nokia X, Nexus series phones to change font(NEED ROOT)
<b>*</b> Support Flipfont changer system
<b>*</b> Support custom fonts
<b>*</b> Easy to use, no tedious steps
<b>*</b> Support multi THEME
HOW TO CHANGE AN APP's FONT
First you need install Xposed framework( repo.xposed.info ) and enable it. Then enable the Fonter module on the Xposed modules screen and reboot your device.
After that, you can select the "Change app font" menu on the left drawer. Pick the app you want to change, and enable change app font function on the app's settings screen, pick the font you want to use.
That's all, have fun!
HOW TO CHANGE SYSTEM FONT
If you have a phone with Flipfont(Most Samsung, OnePlus, Part of Color os):
FIRST OF ALL
You have to check "unknown sources" option on the Settings
1. Go to home screen > "settings" > "security" , and check "unknown sources".
2. Please note: some Carriers doesn't allow non-market apps (downloaded or copyed) be installed. In such case you should root your device to use this feature.
HOW TO USE?
1. Check if your phone have Flipfont.(Home > Settings > Display, check there has Font or Font style or not). Then run this app, download a font you want to use, after download there have to optinos: CHANGE SYSTEM FONT and CHANGE APP FONT. if you want change system font, pick the CHANGE SYSTEM FONT button; if you want change an app's font, pick the CHANGE APP FONT button(this option nend Xposed framewrok:
If you pick the CHANGE SYSTEM FONT option, will ask you to install the font app. After installed , go to font setting screen (Home > Setting > Display > Font or Font sytle). If everything ok, you will see a new font name on font list.
pick it , enable it and enjoy it.
HOW TO UNINSTALL FONTS?
** Go to 'Home > Setting > Application > Manage Application'
** Select font you want to uninstall
Cool, it works great! But I have a question. I have a font saved here, can you add an option to make the apk file so it's installable? The method I used makes the apk incompatible with KitKat.
Enviado do meu Galaxy S5
Does it work with Sony?
Thanks.
I got error and Fonter crashed when I choose font for an app.
Device: Xperia Z2 D6503 4.4.2
Code:
10-02 16:36:34.184: W/dalvikvm(21801): threadid=1: thread exiting with uncaught exception (group=0x4156cd88)
10-02 16:36:34.184: E/AndroidRuntime(21801): FATAL EXCEPTION: main
10-02 16:36:34.184: E/AndroidRuntime(21801): Process: git.hub.font, PID: 21801
10-02 16:36:34.184: E/AndroidRuntime(21801): java.lang.NullPointerException
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.e.f.d(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.a.d.a(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.n.onItemClick(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AdapterView.performItemClick(AdapterView.java:299)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$3.run(AbsListView.java:3638)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.handleCallback(Handler.java:733)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.dispatchMessage(Handler.java:95)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Looper.loop(Looper.java:212)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.app.ActivityThread.main(ActivityThread.java:5151)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invokeNative(Native Method)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invoke(Method.java:515)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:684)
10-02 16:36:34.184: E/AndroidRuntime(21801): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-02 16:36:34.184: E/AndroidRuntime(21801): at dalvik.system.NativeStart.main(Native Method)
Does it work with aosp Roms?
Send with Stylus from Pegasus Galaxy by a Boeffla powered slim device
dandroid13 said:
Cool, it works great! But I have a question. I have a font saved here, can you add an option to make the apk file so it's installable? The method I used makes the apk incompatible with KitKat.
Enviado do meu Galaxy S5
Click to expand...
Click to collapse
The Make apk file feature is developing.
Right now, you can using the "Change App Font" function to set custom font.
Andii S. said:
Does it work with aosp Roms?
[/QUOTE}
yes, any 4.0.3+ aosp roms
Click to expand...
Click to collapse
Thank you, RyokoN
This is a bug, just fixed, and published on the xposed repo
RyokoN said:
I got error and Fonter crashed when I choose font for an app.
Device: Xperia Z2 D6503 4.4.2
Code:
10-02 16:36:34.184: W/dalvikvm(21801): threadid=1: thread exiting with uncaught exception (group=0x4156cd88)
10-02 16:36:34.184: E/AndroidRuntime(21801): FATAL EXCEPTION: main
10-02 16:36:34.184: E/AndroidRuntime(21801): Process: git.hub.font, PID: 21801
10-02 16:36:34.184: E/AndroidRuntime(21801): java.lang.NullPointerException
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.e.f.d(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.a.d.a(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at git.hub.font.x.n.onItemClick(Unknown Source)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AdapterView.performItemClick(AdapterView.java:299)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.widget.AbsListView$3.run(AbsListView.java:3638)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.handleCallback(Handler.java:733)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Handler.dispatchMessage(Handler.java:95)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.os.Looper.loop(Looper.java:212)
10-02 16:36:34.184: E/AndroidRuntime(21801): at android.app.ActivityThread.main(ActivityThread.java:5151)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invokeNative(Native Method)
10-02 16:36:34.184: E/AndroidRuntime(21801): at java.lang.reflect.Method.invoke(Method.java:515)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
10-02 16:36:34.184: E/AndroidRuntime(21801): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:684)
10-02 16:36:34.184: E/AndroidRuntime(21801): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-02 16:36:34.184: E/AndroidRuntime(21801): at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
hassanmahmood said:
Does it work with Sony?
Thanks.
Click to expand...
Click to collapse
I do not have a Sony device, so i have no idea.
But, if you can use xposed on Sony devices, you can use the "Change App Font" function to Change an app's font, or Change System UI font .
goodevh said:
Thank you, RyokoN
This is a bug, just fixed, and published on the xposed repo
Click to expand...
Click to collapse
Great!
Fonter now works perfectly on my Xperia!
I want to translate Fonter to Japanese, but there is no choise for it.
Can you add Japanese to the list of translating languages?
[EDIT]
One question, how can I choose fonts in custom font folder to change system font?
How to change custom font? I have ttf font in my sd card
Thanks! how i can add more font? (i want fonts in hebrew)
Wow thank you for this new apps so easy to use fonts
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
exodius48 said:
How to change custom font? I have ttf font in my sd card
Click to expand...
Click to collapse
Create two floder fonter + fonts and put your TTF fonts in
Japanese is added, thanks again for your support!! :good:
RyokoN said:
Great!
Fonter now works perfectly on my Xperia!
I want to translate Fonter to Japanese, but there is no choise for it.
Can you add Japanese to the list of translating languages?
[EDIT]
One question, how can I choose fonts in custom font folder to change system font?
Click to expand...
Click to collapse
exodius48 said:
How to change custom font? I have ttf font in my sd card
Click to expand...
Click to collapse
Put your ttf files on /Sdcard/fonter/fonts (you can change the folder on the settings screen) folder.
Then when you change an app's font, can pick this folders font.
next release will Support open ttf files and set to system font!
@goodevh can you help me? I have these fonts here, but the app doesn't see them.
{
"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"
}
Enviado do meu Galaxy S5
1910
dandroid13 said:
@goodevh can you help me? I have these fonts here, but the app doesn't see them.
Enviado do meu Galaxy S5
Click to expand...
Click to collapse
Right now the custom font only shows on the "PICK FONT" screen:
the "CHOOSE FONT" button will launch the PICK FONT screen
goodevh said:
Right now the custom font only shows on the "PICK FONT" screen:
the "CHOOSE FONT" button will launch the PICK FONT screen
Click to expand...
Click to collapse
Oh, man, I feel so dumb, I didn't get a notification the first time you quoted me.
Now it works, thanks mate.
goodevh said:
Japanese is added, thanks again for your support!! :good:
Click to expand...
Click to collapse
strings for arrays such as Font install mode selection and Orientation are showed as one long string, so maybe it will cause a problem dividing one translated string to multiple strings.
I also want "Copy source text into translation textarea" since I don't know how to input some characters such as black box for theme selection
If you are OK to change translation manager system, I recommened OneSkyApp.com.
Using OneSkyApp translators can work with PC with usuful functions and you can manage translations easily.
RyokoN said:
strings for arrays such as Font install mode selection and Orientation are showed as one long string, so maybe it will cause a problem dividing one translated string to multiple strings.
I also want "Copy source text into translation textarea" since I don't know how to input some characters such as black box for theme selection
If you are OK to change translation manager system, I recommened OneSkyApp.com.
Using OneSkyApp translators can work with PC with usuful functions and you can manage translations easily.
Click to expand...
Click to collapse
I'm checking the OneSkyApp service,
transcommu also can work on PC, open the url on you browser:
http://transcommu.yasesprox.com/transcommu/Applications/View/185
EDIT:
add on oneskyapp
English: http://osvya69.oneskyapp.com/collaboration/project?id=36345
Chinese: http://osvya69.oneskyapp.com/collaboration/project?id=36343
Hello I'm running sacs moar s5 v5 port with the sleep kernel but I have tried going back to stock I have flashed to the stockfish 4.4.4 ROM I've tried different nc5 ROMs and this one widget force closes I wrote the developer but they said there's nothing wrong that should be making the widget force close my wife has the same phone running stockish 4.4.4 and the widget works fine and it used to work fine on mine the problem started when I first flashed sacs moar ROM s5 port v1 with the v1 fixes and now no matter what I do it want work and the app to me is a must have here's a logcat if anybody can explain what's going on and maybe how to fix it I would thank you so much all the widget name is Alabama live clock widget made by smartphone technologies
https://www.dropbox.com/s/z9a0tk4hvwjlobh/Log_2014-10-30_23-10-43.txt?dl=0
Any help is good help
Here's a link to the app https://play.google.com/store/apps/details?id=com.smartPhones.clockwidget.ncaa.live.alabama_AND
I've also formatted my phone and reflashed still force close its like its not seeing that I paid or something
uknow said:
Any help is good help
Here's a link to the app https://play.google.com/store/apps/details?id=com.smartPhones.clockwidget.ncaa.live.alabama_AND
I've also formatted my phone and reflashed still force close its like its not seeing that I paid or something
Click to expand...
Click to collapse
I'm no expert at reading logcats, nor do I know anything about the app that you installed, but from what I can tell, the app sets up an XML file that says which widgets you have bought. It appears that the widget is having a tough time reading from that XML file.
Code:
10-30 22:58:20.588 3252 3252 W System.err: java.text.ParseException: Unparseable date: "0" (at offset 1)
10-30 22:58:20.588 3252 3252 W System.err: at java.text.DateFormat.parse(DateFormat.java:555)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.readPurchaseXML(MainActivity.java:486)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.checkPurchase(MainActivity.java:451)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.onCreate(MainActivity.java:267)
It's possible that even though you wiped your phone, that there were leftover files on the device which the app is continuing to try to use. Can you go through these steps ans see if it helps?
Install your favorite ROOT file explorer. I personally use ES File Explorer, but you can choose any that has root access.
Uninstall the Alabama Live Clock App
Find the following folders and delete them (if they exist):
/InternalStorage/Android/data/com.smartPhones.clockwidget.ncaa.live.alabama_AND
/ExternalStorage/Android/data/com.smartPhones.clockwidget.ncaa.live.alabama_AND
Reinstall the Live Clock App.
Hello there! I'm new to these parts because I recently acquired a Gear Fit.
TL;DR: I took aooga's stuff (thanks!) and made it work on my CM 12 (5.0.2) phone. I hope it works for you. Get it here.
Anyway, I'm using a Galaxy Nexus running a cm 12 build from Ziyan, and I quickly realized that I needed to do some extra work. Unfortunately, zwegnet's patched Gear Fit Manager didn't work for me, and neither did aooga's very comprehensive guide, so I figured I'd try doing it myself. I see that some of you are interested in how this works, so I'm documenting my process for everyone's benefit (let's collaborate!).
You will learn the basics of:
how to debug using adb logcat
how to disassemble an app (specifically, a dex file) into smali
how to navigate and modify smali code
how to reassemble smali to dex and rebuild the app
how to sign an app for deployment
You will need:
adb
java runtime environment
smali/baksmali
signapk with test keys
I've collected some of the tools for you here; just add adb and java.
1. Debugging
So, we've got Gear Fit Manager and Gear Fitness installed... but Gear Fit Manager crashes! Darn it. How are we gonna connect a Gear Fit? Let's see.
First, let's pop open your favorite terminal (yes, we will be using the command line) and start streaming some logs:
Code:
adb logcat
There should be a bunch of text scrolling through the terminal. While that's going on, try to launch the offending app, and wait until it crashes. As soon as it crashes, hit Ctrl+C in the terminal to stop logging. Look, a fatal exception:
Code:
E/AndroidRuntime(32368): FATAL EXCEPTION: main
E/AndroidRuntime(32368): Process: com.samsung.android.wms, PID: 32368
E/AndroidRuntime(32368): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2298)
E/AndroidRuntime(32368): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2360)
E/AndroidRuntime(32368): at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime(32368): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
E/AndroidRuntime(32368): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(32368): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(32368): at android.app.ActivityThread.main(ActivityThread.java:5223)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AndroidRuntime(32368): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.content.res.Resources.getValue(Resources.java:1233)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:756)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.ContentsActivity.onCreate(ContentsActivity.java:139)
E/AndroidRuntime(32368): at android.app.Activity.performCreate(Activity.java:5933)
E/AndroidRuntime(32368): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
E/AndroidRuntime(32368): ... 10 more
When you've been bug-hunting for a while, you start to notice these stack traces quite readily, even in a sea of irrelevant output. This one tells us that:
the offending app is named com.samsung.android.wms
a Resources$NotFoundException occurred, likely because the app requested a resource that did not exist
... and so on
Note that the stack trace appears in reverse-chronological order; that is, what happens later appears first. I often like to read these things backwards. Now, have a look at these lines:
Code:
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
What happened?
a WingtipBaseActivity is created to display the app, and is being initialized in its onCreate method
... which calls brandGlowEffect
... which calls into the Android system
... which eventually leads to the crash
With the entire chain of events exposed to us, we could now look for the culprit! Why don't we examine WingtipBaseActivity.brandGlowEffect? It's the last thing the app does before passing control over to Android, and we're assuming that the app (not Android) is faulty.
2. Disassembly
To do this, we need to take a peek under Gear Fit Manager's hood. An apk file is just a zip file, so we already know how to unpack it. We're interested in the classes.dex within, which contains the executable code. dex is not a very human-readable format, so we need to disassemble it using baksmali.
Firstly, let's extract the classes.dex from the archive. Then, we could disassemble it by running:
Code:
java -jar baksmali.jar -o dexout classes.dex
3. Modification
This generates a folder full of disassembled code. Because we're interested in com.samsung.android.wms.app.base.WingtipBaseActivity, we'll look inside the file dexout/com/samsung/android/wms/app/base/WingtipBaseActivity.smali
There, on line 693, we see the method WingtipBaseActivity.brandGlowEffect getting called from WingtipBaseActivity.onCreate. This looks like some cosmetic fluff that we could dispense with, so let's just delete the line altogether and save the file. Sorry, Samsung, your brand's not gonna glow this time.
4. Reassembly
Now we could re-generate the classes.dex:
Code:
java -jar smali.jar -o classes.dex dexout
... and we'll drop the new classes.dex inside the apk.
5. Signing
But wait! We couldn't install this new apk yet — it needs to be signed. This is easy enough with signapk:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 GearFitManager.apk GearFitManager_signed.apk
6. Deploying
We need to uninstall the original app before we could install the new one, because they were signed using different keys (the original was signed using Samsung's keys). After that, we just need to install and test!
We've barely scratched the surface. I hope this helps someone, and I certainly hope we could team up to make something awesome. I've had a look at the more recent versions of Gear Fit Manager, and I have a feeling a lot more work would be required...
Just when I was about to give up , I found this thread . Thank you so much .
The app finally doesn't crash . But it doesn't seem to be connecting with the Fitness app .
Running Nexus 4 with CyanogenMod 12 , v5.0.2 .
[DIY][CM 12][Android 5.0] Gear Fit on Non-Samsung Devices with Lollipop
Hello there! I'm new to these parts because I recently acquired a Gear Fit.
TL;DR: I took aooga's stuff (thanks!) and made it work on my CM 12 (5.0.2) phone. I hope it works for you. Get it here.
Anyway, I'm using a Galaxy Nexus running a cm 12 build from Ziyan, and I quickly realized that I needed to do some extra work. Unfortunately, zwegnet's patched Gear Fit Manager didn't work for me, and neither did aooga's very comprehensive guide, so I figured I'd try doing it myself. I see that some of you are interested in how this works, so I'm documenting my process for everyone's benefit (let's collaborate!).
You will learn the basics of:
1.how to debug using adb logcat
2.how to disassemble an app (specifically, a dex file) into smali
3.how to navigate and modify smali code
4.how to reassemble smali to dex and rebuild the app
5.how to sign an app for deployment
You will need:
•adb
•java runtime environment
•smali/baksmali
•signapk with test keys
I've collected some of the tools for you here; just add adb and java.
1. Debugging
So, we've got Gear Fit Manager and Gear Fitness installed... but Gear Fit Manager crashes! Darn it. How are we gonna connect a Gear Fit? Let's see.
First, let's pop open your favorite terminal (yes, we will be using the command line) and start streaming some logs:
Code:
adb logcat
There should be a bunch of text scrolling through the terminal. While that's going on, try to launch the offending app, and wait until it crashes. As soon as it crashes, hit Ctrl+C in the terminal to stop logging. Look, a fatal exception:
Code:
E/AndroidRuntime(32368): FATAL EXCEPTION: main
E/AndroidRuntime(32368): Process: com.samsung.android.wms, PID: 32368
E/AndroidRuntime(32368): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2298)
E/AndroidRuntime(32368): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2360)
E/AndroidRuntime(32368): at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime(32368): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
E/AndroidRuntime(32368): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(32368): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(32368): at android.app.ActivityThread.main(ActivityThread.java:5223)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AndroidRuntime(32368): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.content.res.Resources.getValue(Resources.java:1233)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:756)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.ContentsActivity.onCreate(ContentsActivity.java:139)
E/AndroidRuntime(32368): at android.app.Activity.performCreate(Activity.java:5933)
E/AndroidRuntime(32368): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
E/AndroidRuntime(32368): ... 10 more
When you've been bug-hunting for a while, you start to notice these stack traces quite readily, even in a sea of irrelevant output. This one tells us that:
•the offending app is named com.samsung.android.wms
•a Resources$NotFoundException occurred, likely because the app requested a resource that did not exist
•... and so on
Note that the stack trace appears in reverse-chronological order; that is, what happens later appears first. I often like to read these things backwards. Now, have a look at these lines:
Code:
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
What happened?
1.a WingtipBaseActivity is created to display the app, and is being initialized in its onCreate method
2.... which calls brandGlowEffect
3.... which calls into the Android system
4.... which eventually leads to the crash
With the entire chain of events exposed to us, we could now look for the culprit! Why don't we examine WingtipBaseActivity.brandGlowEffect? It's the last thing the app does before passing control over to Android, and we're assuming that the app (not Android) is faulty.
2. Disassembly
To do this, we need to take a peek under Gear Fit Manager's hood. An apk file is just a zip file, so we already know how to unpack it. We're interested in the classes.dex within, which contains the executable code. dex is not a very human-readable format, so we need to disassemble it using baksmali.
Firstly, let's extract the classes.dex from the archive. Then, we could disassemble it by running:
Code:
java -jar baksmali.jar -o dexout classes.dex
3. Modification
This generates a folder full of disassembled code. Because we're interested in com.samsung.android.wms.app.base.WingtipBaseActivi ty, we'll look inside the file dexout/com/samsung/android/wms/app/base/WingtipBaseActivity.smali
There, on line 693, we see the method WingtipBaseActivity.brandGlowEffect getting called from WingtipBaseActivity.onCreate. This looks like some cosmetic fluff that we could dispense with, so let's just delete the line altogether and save the file. Sorry, Samsung, your brand's not gonna glow this time.
4. Reassembly
Now we could re-generate the classes.dex:
Code:
java -jar smali.jar -o classes.dex dexout
... and we'll drop the new classes.dex inside the apk.
5. Signing
But wait! We couldn't install this new apk yet — it needs to be signed. This is easy enough with signapk:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 GearFitManager.apk GearFitManager_signed.apk
6. Deploying
We need to uninstall the original app before we could install the new one, because they were signed using different keys (the original was signed using Samsung's keys). After that, we just need to install and test!
We've barely scratched the surface. I hope this helps someone, and I certainly hope we could team up to make something awesome. I've had a look at the more recent versions of Gear Fit Manager, and I have a feeling a lot more work would be required...
Click to expand...
Click to collapse
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Help
bronxgsi said:
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Click to expand...
Click to collapse
I installed the zip by renaming it as an apk but when I try to pair it give the same confirmation but doesn't finish pairing please help... I have Nexus 5 it has stock 5.0.1 rooted as well.
I haven't been able to sync the Fitness with Gear app either, even with Samsung Account installed per Virnik0's recommendation.
I believe this stack trace is relevant:
Code:
D/SessionInputStream(29439): move remain data to first index / mTotalDataLength : 83 mTotalReceivedLength : 88
W/SessionManager(29439): notifyDataReceived port : 2
I/SessionManager(29439): mBinderMap.get action:com.samsung.android.wms.communication.session_manager_for_interanalbinder:115174198
I/SessionManager(29439): listener.onDataReceived is called
V/DataExchangeManager(29439): SessionManagerEventListener onDataReceived
W/DataExchangeManager(29439): From : HEALTH, Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): java.lang.NullPointerException: Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): at com.samsung.android.wms.service.communication.DataExchangeManager$InternalHandler.handleMessage(DataExchangeManager.java:126)
W/DataExchangeManager(29439): at android.os.Handler.dispatchMessage(Handler.java:102)
W/DataExchangeManager(29439): at android.os.Looper.loop(Looper.java:135)
W/DataExchangeManager(29439): at android.app.ActivityThread.main(ActivityThread.java:5223)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Native Method)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Method.java:372)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
It seems that it actually connected to Samsung's servers, but had some trouble handling the response. I'll investigate this sometime...
will1549 said:
I installed the zip by renaming it as an apk but when I try to pair it give the same confirmation but doesn't finish pairing please help... I have Nexus 5 it has stock 5.0.1 rooted as well.
Click to expand...
Click to collapse
Same here -- I'd blame the differences among ROMS
I actually haven't been able to get any recent versions working, myself...
inportb said:
I haven't been able to sync the Fitness with Gear app either, even with Samsung Account installed per Virnik0's recommendation.
I believe this stack trace is relevant:
Code:
D/SessionInputStream(29439): move remain data to first index / mTotalDataLength : 83 mTotalReceivedLength : 88
W/SessionManager(29439): notifyDataReceived port : 2
I/SessionManager(29439): mBinderMap.get action:com.samsung.android.wms.communication.session_manager_for_interanalbinder:115174198
I/SessionManager(29439): listener.onDataReceived is called
V/DataExchangeManager(29439): SessionManagerEventListener onDataReceived
W/DataExchangeManager(29439): From : HEALTH, Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): java.lang.NullPointerException: Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): at com.samsung.android.wms.service.communication.DataExchangeManager$InternalHandler.handleMessage(DataExchangeManager.java:126)
W/DataExchangeManager(29439): at android.os.Handler.dispatchMessage(Handler.java:102)
W/DataExchangeManager(29439): at android.os.Looper.loop(Looper.java:135)
W/DataExchangeManager(29439): at android.app.ActivityThread.main(ActivityThread.java:5223)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Native Method)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Method.java:372)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
It seems that it actually connected to Samsung's servers, but had some trouble handling the response. I'll investigate this sometime...
Same here -- I'd blame the differences among ROMS
I actually haven't been able to get any recent versions working, myself...
Click to expand...
Click to collapse
My problem getting the Bluetooth pair to GFM. On version 1.49 for lollipop it was but not this zip
will1549 said:
My problem getting the Bluetooth pair to GFM. On version 1.49 for lollipop it was but not this zip
Click to expand...
Click to collapse
It works. Sort of. Basically it asks for update every time I connect to my Fit. That update then fail due to different signing keys, but then it works.
I have used the version from OP
Virnik0 said:
It works. Sort of. Basically it asks for update every time I connect to my Fit. That update then fail due to different signing keys, but then it works.
I have used the version from OP
Click to expand...
Click to collapse
My problem is it only pair Bluetooth but never connect gear fit manager to the gear fit it keeps send verification codes.
bronxgsi said:
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Click to expand...
Click to collapse
This one works fine! Thanks for sharing!
---------- Post added at 10:43 PM ---------- Previous post was at 10:25 PM ----------
Virnik0 said:
This one works fine! Thanks for sharing!
Click to expand...
Click to collapse
BTW, we'll need version 1.102, and original genuine keys. so, once you'll compile/smali odex, just add it to original APK, that shall do it, otherwise we won't be able to use any gear app plugin
I don't know why it doesn't pair... Sorry I'm not an expert in this issue.
Virnik0 said:
This one works fine! Thanks for sharing!
---------- Post added at 10:43 PM ---------- Previous post was at 10:25 PM ----------
BTW, we'll need version 1.102, and original genuine keys. so, once you'll compile/smali odex, just add it to original APK, that shall do it, otherwise we won't be able to use any gear app plugin
Click to expand...
Click to collapse
I tried to patch the last versión (GearFitManager_NL1_1.111.1216_USER.apk) but it doesn't pair. The original one, in a G2 with KitKat doesn't pair neither.
I was able to use all the plugins from App connect patching the "dexout\com\samsung\android\sdk\cup\Scup.smali" file to not to check the keys. Just changing:
if-eq v1, v6, :cond_e2
to
if-ne v1, v6, :cond_e2
The problema is that I had to patch every App I want to use and it is a little tedious. Maybe we can make an script or a program to automatically doing it...
Dunno what will be best way to do this now. I have a very little time to do any coding nowadays. But at least version 1.98 works fine. Running RR 5.2.9 (CM12 - Android 5.0.2) on GT9300. Pairing works correctly
A script would be wonderful
pcp12 said:
A script would be wonderful
Click to expand...
Click to collapse
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Does this versions just work on cm12? I have GPE lollipop on my s4 and when I connect my phone to the gear fit, the gear fit manager crashes immediately.
poaudet said:
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Click to expand...
Click to collapse
Because you have to modify ro.product.manufacturer=samsung to something else (like ro.product.manufacturer=GPE) in /system/build.prop
Reboot after modification is done and you should be OK.
BTW, SGS5 does have LP available for download for more then month, but GFM is the same. Works there fine, because all classes are provided from TW framework.
Virnik0 said:
Because you have to modify ro.product.manufacturer=samsung to something else (like ro.product.manufacturer=GPE) in /system/build.prop
Reboot after modification is done and you should be OK.
BTW, SGS5 does have LP available for download for more then month, but GFM is the same. Works there fine, because all classes are provided from TW framework.
Click to expand...
Click to collapse
Thanks, got it working. Really nice work! [emoji1]
poaudet said:
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Click to expand...
Click to collapse
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
alexxio said:
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
Click to expand...
Click to collapse
Im using google play edition on my s4. Its like the lollipop on nexus 5 and everything for me is working.
alexxio said:
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
Click to expand...
Click to collapse
I've stock lollipop rom.
Things that didn't work:
-music control
-everything that need Samsung Account
-Endomondo
-GPS (Gear Navigation, Weather, ...)
Everything else seems to work, with some edit it the apk of Connected App, see the other post in this thread.
I've attached those i've already edit.
Noob question: I flew over the tutorial and didn't really noticed any variable data. Is there something preventing someone from generating and sharing a patched apk of GFM that would work with basically any non-Samsung Lollipop phone ?
Battery Shutdown Manager
Download @ Google Play
Do you know that moment when you're on 1% of battery and think "I'll just use my device 20 more seconds then I'll get my charger" - and at exactly that moment it'll switch to 0% and you'll see the threaded "Shutting down" dialog and know it's too late now?
This Xposed module will help by showing you a dialog with a countdown before the actual shutdown, so you'll have time to attach your charger.
The module achieves this by postponing the shutdown for a couple of seconds to give you time to connect the charger.
Please post any kind of feedback or ideas you have regarding this app :fingers-crossed:
I tested the module a lot but can't possibly test it for all those different phones and versions out there.
Thus I will flag it as beta for now so you can provide feedback before I'll release the 1.0 version.
It would be great if some more people could test it. I used the StabilityTest app to quickly drain my battery down to 0%.
Compatibility:
I wrote this module and tested it with AOSP devices as well as on Cyanogenmod.
It should work without any issues on all Nexus and Google Play Edition devices from Android 4.2 to 5.1+.
As almost all Custom ROMs are based on either AOSP or CM they should work without issues, too.
Some vendors might have changed the original code and thus render this module incompatible on their device. Nothing bad will happen when you install it, it just won't work.
Compatible:
Nexus / AOSP / GPE ROMs
Cyanogenmod
Almost all custom ROMs (as they're usually either based on AOSP or CM)
Sony Stock ROMs
Not compatible:
Currently not working for LG Stock ROMs due to internal code changes by LG.
Android devices <4.2. Support for Android 4.0.3+ and 4.1 might be added when I see a greater demand for it.
Installation:
- Download the app
- Activate the module in the Xposed Insaller
- Reboot your device
- Open the app to change it's options to your liking
Bugs/Issues:
If you encounter any bugs just report them here and I'll try to fix them. Always include as much information as possible, including your device model, android version and exact ROM details.
Note that I will most likely need a log to fix the issue, a generic "doesn't work on phone xyz" won't help me fixing the issues.
There are two possibilities to get a log.
Use the Catlog app. In the app press Menu > Record Log before the device shuts down, then attach the logcat to your bugreport.
Alternatively you need to use adb to grab the log.
Unfortunately logging is a bit more complicated for this module as the interesting part happens on shutdown.
The best solution (and what I do personally for debugging this app) is to use ADB over WiFi (e.g. with this app) and grab the log.
Download:
Google Play Store
Xposed Module Repository
Google+:
www.google.com/+thetonyp
Last but not least an obligatory huge thanks to @rovo89 for his amazing Xposed framework!
If you like this module don't forget to press thanks, rate this thread with 5 stars, consider a donation etc. etc.
:fingers-crossed:
I love your icon pack!
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Samsung galaxy s3 i9300 4.3 mk6 stock rom, bootloops.
Sent from a stolen phone!
Bootloop on Nexus 4, Stock Android 4.3.3...
EDIT Because OP asked how the bootloop occurs on Nexus 4, Android 4.3.3:
Bootloop occurs after activating module and normal (not soft) reboot.
Before reboot app can be runned and configurated.
I have no log app running, so I'm not able to deliver logs.
Yes, please send me a logcat. Bootloops are great, then you can just get the log after the reboot. I literally can't do anything without a log.
mobihack said:
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Click to expand...
Click to collapse
Thanks for the feedback, then I will add 5.1 to the compatibility at the Play Store.
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
tonyp said:
Thanks for the feedback, then I will add 5.1 to the compatibility at the
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
Click to expand...
Click to collapse
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
bootloops
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
akhilkbaby said:
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
Click to expand...
Click to collapse
I'd like to fix the issue, could you kindly send me a logcat of the bootloop?
Unfortunately there is literally nothing I could possibly do without a log.
mobihack said:
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
Click to expand...
Click to collapse
I'm using the stock dialog which guarantees the highest possible compatibility with other devices.
Regarding the notification, I don't know when the battery will be empty before, so there's no way to display a message one minute before. All I could do is starting the dialog at 1% (which I'm considering for a future version), but that would be quite different.
I like the idea for a shutdown button, an option to include that will be in an upcoming version.
Oh, true, the icon pack is called etched material.
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
HydraS4 said:
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
Click to expand...
Click to collapse
This sounds very strange, the module is only hooking into one class which has nothing to do with receiving messages.
Yes, usually it works to log the freeze, just start logging (best would be with adb logcat) before it happens.
Can not install on 4.1
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
---------- Post added at 02:41 PM ---------- Previous post was at 01:49 PM ----------
Fif_ said:
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
Click to expand...
Click to collapse
There we go, I have it.
This is a logcat of the behavior I was describing earlier: after the countdown, the system performs a soft reboot instead of shutting down.
I have seen this behavior on Nexus 4/5/10 (mako/hammerhead/manta) on CM11 M11.
The logcat below is on a Nexus 4 running CM11 M11 and Battery Shutdown Manager 0.93:
Code:
I/Xposed ( 1726): BatterySM: invokeOriginalMethod. batteryLevel=2, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=false, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: Showing dialog. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: Dismiss dialog
W/InputMethodManagerService( 1726): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/AndroidRuntime( 1726): Shutting down VM
W/dalvikvm( 1726): threadid=1: thread exiting with uncaught exception (group=0x415e4ce0)
E/AndroidRuntime( 1726): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 1726): java.lang.NoSuchMethodError: com.android.server.BatteryService#processValuesLocked(java.lang.Boolean)#bestmatch
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:271)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:284)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:947)
E/AndroidRuntime( 1726): at com.thetonyp.batteryshutdownmanager.BatteryDialog$2.onFinish(BatteryDialog.java:258)
E/AndroidRuntime( 1726): at android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:118)
E/AndroidRuntime( 1726): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1726): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(SystemServer.java:1289)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(Native Method)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(SystemServer.java:1386)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/AndroidRuntime( 1726): at dalvik.system.NativeStart.main(Native Method)
W/DropBoxManagerService( 1726): Dropping: system_server_crash (1667 > 0 bytes)
I/Process ( 1726): Sending signal. PID: 1726 SIG: 9
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Mubasher96 said:
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
Click to expand...
Click to collapse
The module currently requires Android 4.2 or higher. You can't install the module on CM10 as that is based on Android 4.1.
To support Android 4.0 and 4.1 I need to write some custom code which I need some people to test, so everyone interested in this module on a 4.0 or 4.1 device (including CM9 / CM10 etc of course) please write here or send me a PM and I'll contact you as soon as I have a version ready for testing! Can I count you in?
Fif_ said:
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
...
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Click to expand...
Click to collapse
Thank you very much for the logcat! It contained exactly what I needed!
Thanks to that I identified the issue and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Additionally this version fixes a potential bootloop cause for devices running Jellybean (4.2 / 4.3).
Could the affected people please test this and confirm? Again, if you manage to get me a log it will make it a lot easier for me to fix any issue whatsoever.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Nice! This is so necessary… I'm gonna test it.
tonyp said:
Thank you very much for the logcat! It contained exactly what I needed!
I believe I identified the issue thanks to the log and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Click to expand...
Click to collapse
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Fif_ said:
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
Click to expand...
Click to collapse
No worries, they're using the same codebase so it will work on all devices.
Thanks a lot for buying pro
That purchase should work on all devices of course sometimes it takes a little while to propagate at Google, when you still have the issue after a couple more hours could you please drop me a PM? I did test the IAP purchases with all possible ways Google offers for me, but unfortunately that's something that could be greatly improved on their side.
exodius48 said:
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Click to expand...
Click to collapse
Ah, I didn't know there exists an alternative manager. I'm explicitly checking for the Xposed Installer. You can ignore the warning for now and I will push an update which recognizes the WSM Manager as well
No bootloops on moto g stock 5.0.2