Related
Hey,
When I mean samsung apps, more specifically I mean S Health since I have a lot of data saved in it. The problem is that when I switch from one TW rom to another TW rom, I can't seem to restore S Health data (I'm using Titanium Backup).
I've tried restoring data after doing a fresh install of S Health, as well as just trying to restore S Health without a previous install of it. Really, I want it to restore like all my other apps, but its seen as a system app and I wonder if that's the problem.
Hope I was clear, does anyone have an idea?
Thanks.
can you try another backup app like kousch's carbon
or, my backup pro--it lets you select just the apps you want--not sure if it does system apps though
If s health is a system app, in batch restore of tibu, run restore all system data, Deselect all and then just check s-health data so you restore only that.
jd1639 said:
If s health is a system app, in batch restore of tibu, run restore all system data, Deselect all and then just check s-health data so you restore only that.
Click to expand...
Click to collapse
+1
I usually don't restore System data from TB, esp btwn roms, so don't think much about that being an option.
Have a Nandroid as always--
Backups TB or Go back up will not work if you are using 4.3 rom. Since 4.3 leaked and is still not supported if this is the case all you can do is flash 4.2.2 or 4.1.2 these still work. Am having same issue with CM 10.2 have a lot of saved game data had to start over the price of update software. Lol
Sent from my SGH-I337 using XDA Premium 4 mobile app
VICIOUSVIC1 said:
Backups TB or Go back up will not work if you are using 4.3 rom. Since 4.3 leaked and is still not supported if this is the case all you can do is flash 4.2.2 or 4.1.2 these still work. Am having same issue with CM 10.2 have a lot of saved game data had to start over the price of update software. Lol
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm running cm 10.2 and I can restore user apps with tibu. Haven't tried system data though
Ya I tried it all. Short and simple we have to start over guy. Like I said before we are now on 4.3 firmware it is not supported by any backup yet since 4.3 Is not suppost to be out yet all we can do is wait till official 4.3 out for all back up apps to update to 4.3
Sent from my SGH-I337 using XDA Premium 4 mobile app
VICIOUSVIC1 said:
Ya I tried it all. Short and simple we have to start over guy. Like I said before we are now on 4.3 firmware it is not supported by any backup yet since 4.3 Is not suppost to be out yet all we can do is wait till official 4.3 out for all back up apps to update to 4.3
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I disagree, tibu is working fine with 4.3. Your doing something wrong.
Thanks everyone. I'm not using 4.3 right now since I'm sticking with touchwiz roms.
Titanium backup works really well for all my apps except for those system apps. When I try to restore app+data, TB seems to get stuck. Ah well, maybe samsung backs up the info somehow.
Btw, is there a way to use S Health without using a TW rom? Then I'd move up to a 4.3 rom.
The Environment
I have the SM-N9005, in the UK on EE.
Android 4.3,
Baseband N9005XXUBMI6,
Kernel 3.4.0-1628120
Build JSSJ.N9005XXUBMI7
SELinux Status - Enforcing
I have just installed the rom from here: http://forum.xda-developers.com/showpost.php?p=45972118&postcount=36 where KNOX is removed.
The Issue
I previously had a Samsung Galaxy S3, i9300, running different 4.3 roms. Apps were backed up with Titanium Backup and often restored without issue.
Now when I restore apps with data on my new Note 3, some apps restore okay and run without issue (WINAMP), however others give me force closes, either when starting the app (Call Blocker) or when closing the app (Candy Crush for instance).
I am unsure if the issue lies with Titanium Backup, or the SELinux Enforcing, or the KNOX stuff, or what?
Any devs that can help, would be greatly appreciated!
I have the same issue, anyine can help? Many many thanks.
Sent from my SM-N9005 using Tapatalk 2
danieljamie said:
The Environment
I have the SM-N9005, in the UK on EE.
Android 4.3,
Baseband N9005XXUBMI6,
Kernel 3.4.0-1628120
Build JSSJ.N9005XXUBMI7
SELinux Status - Enforcing
I have just installed the rom from here: http://forum.xda-developers.com/showpost.php?p=45972118&postcount=36 where KNOX is removed.
The Issue
I previously had a Samsung Galaxy S3, i9300, running different 4.3 roms. Apps were backed up with Titanium Backup and often restored without issue.
Now when I restore apps with data on my new Note 3, some apps restore okay and run without issue (WINAMP), however others give me force closes, either when starting the app (Call Blocker) or when closing the app (Candy Crush for instance).
I am unsure if the issue lies with Titanium Backup, or the SELinux Enforcing, or the KNOX stuff, or what?
Any devs that can help, would be greatly appreciated!
Click to expand...
Click to collapse
isnt this caused by a different system structure which came with JB 4.3?
danieljamie said:
I have just installed the rom from here: http://forum.xda-developers.com/showpost.php?p=45972118&postcount=36 where KNOX is removed.
Click to expand...
Click to collapse
We canot think like this "KNOX is remoded". We remove only some appl, but the KNOX is always there on Bootloader from hardware.
We must read and understand well this on the link:
https://www.samsungknox.com/overview/technical-details
See also the attach's:
Try to change backup folder in the preference:
storage/emulated/legacy
toofimoofi said:
isnt this caused by a different system structure which came with JB 4.3?
Click to expand...
Click to collapse
No, because I successfully restored apps on 4.3 on my previous phone I9300..
kenzolo said:
Try to change backup folder in the preference:
storage/emulated/legacy
Click to expand...
Click to collapse
I have changed my backup directory to the correct one (actually on my external card). This has no effect.
Sent from my SM-N9005 using xda app-developers app
How did you root? TB require root
weirdingway said:
How did you root? TB require root
Click to expand...
Click to collapse
Check the Android Dev section, root is done
Sent from my SM-N9005 using xda app-developers app
For me it's absolutely necessary that TB is working properly. Have you tried to contact the developer? Maybe he needs to fix the application somehow?
onyxogen said:
For me it's absolutely necessary that TB is working properly. Have you tried to contact the developer? Maybe he needs to fix the application somehow?
Click to expand...
Click to collapse
No I will do that later today..
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
No I will do that later today..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
I have the same issue. some apps just wotnrestore properly on titanium
toofimoofi said:
I have the same issue. some apps just wotnrestore properly on titanium
Click to expand...
Click to collapse
It's not just titanium restored aps, some aps from the play store won't work (i.e. whats ap, tasker etc) keep getting a knox notification that the ap has been blocked (even though Knox was not enabled).
Seems some sideloaded aps don't work either (adblock, adaway etc)
thelestat said:
It's not just titanium restored aps, some aps from the play store won't work (i.e. whats ap, tasker etc) keep getting a knox notification that the ap has been blocked (even though Knox was not enabled).
Seems some sideloaded aps don't work either (adblock, adaway etc)
Click to expand...
Click to collapse
So you are saying that whats app is not working on the note 3?can anyone confirm this? I could not be without it. And Tasker? Anyone?
onyxogen said:
So you are saying that whats app is not working on the note 3?can anyone confirm this? I could not be without it. And Tasker? Anyone?
Click to expand...
Click to collapse
The whatsapp verification fails, it can't read the sms that you receive. On the third try I got unknown error, press to initiate a call back, this worked and gives me a manual code to verify the ap. After that I can now send and recieve messages.
Tasker just crashes for me, knox popup saying app has been closed
WhatsApp works fine with me.
Tasker seems to work ok as well.I`m not a tasker expert so maybe it could be borked on some of it`s deeper functions.
I`m running on DjeMBeY`s pre-rooted rom.It`s meant to be de-Knoxified
thelestat said:
It's not just titanium restored aps, some aps from the play store won't work (i.e. whats ap, tasker etc) keep getting a knox notification that the ap has been blocked (even though Knox was not enabled).
Seems some sideloaded aps don't work either (adblock, adaway etc)
Click to expand...
Click to collapse
The issue with Titanium restores is unrelated to the Knox errors. Remove Knox completely. Whatsapp works.
onyxogen said:
So you are saying that whats app is not working on the note 3?can anyone confirm this? I could not be without it. And Tasker? Anyone?
Click to expand...
Click to collapse
Whatsapp works. Will test tasker now.
Edit: Tasker works fine
Sent from my SM-N9005 using xda app-developers app
I solved the selinux enforcing FC issues updating the su binaries on playstore after chainfire flashing.
Inviato dal mio SM-N9005 con Tapatalk 4
danieljamie said:
The Environment
I have the SM-N9005, in the UK on EE.
Android 4.3,
Baseband N9005XXUBMI6,
Kernel 3.4.0-1628120
Build JSSJ.N9005XXUBMI7
SELinux Status - Enforcing
I have just installed the rom from here: http://forum.xda-developers.com/showpost.php?p=45972118&postcount=36 where KNOX is removed.
The Issue
I previously had a Samsung Galaxy S3, i9300, running different 4.3 roms. Apps were backed up with Titanium Backup and often restored without issue.
Now when I restore apps with data on my new Note 3, some apps restore okay and run without issue (WINAMP), however others give me force closes, either when starting the app (Call Blocker) or when closing the app (Candy Crush for instance).
I am unsure if the issue lies with Titanium Backup, or the SELinux Enforcing, or the KNOX stuff, or what?
Any devs that can help, would be greatly appreciated!
Click to expand...
Click to collapse
That's quite normal when using Tita backup. Especially for the new device, just remove the problematic app and reinstall it. That happens to my previous Sony ZU as well.
For me, I won't restore app to my new purchased device unless apps with important data on it. I will install apps directly from play store. Then do the backup when all apps, themes are settled down. I will only restore apps in the same device just in case something happened.
The most valuable function of Tita backup for me is freeze or remove bloatwares.....
hagalah said:
That's quite normal when using Tita backup. Especially for the new device, just remove the problematic app and reinstall it. That happens to my previous Sony ZU as well.
For me, I won't restore app to my new purchased device unless apps with important data on it. I will install apps directly from play store. Then do the backup when all apps, themes are settled down. I will only restore apps in the same device just in case something happened.
The most valuable function of Tita backup for me is freeze or remove bloatwares.....
Click to expand...
Click to collapse
I appreciate there may be some conflicts but I have switched phone before and restored apps with data from previous phone and all was good.
I have some apps where I pay monthly via sms where I require the data to be restored.
It seems to be an issue with SELinux set to enforcing. There are many people in this forum and the GS4 forum having troubles with Titanium.
Sent from my SM-N9005 using xda app-developers app
+1 here.
I had to wipe data because my first "as usual" restore data gave nothing good : apps were not launching, constantly crashing.
I'm using the google restore app functionality to ensure a minimum is install and will test that again.
I cannot believe there's no way to make TB work properly. I don't know my new device enough yet to be sure if it's that Knox thing (didn't get what it is exactly) or any re-enforced (compared to my SGS3) security stuff.
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
You may need to do a full wipe when you flash stock, it's possible something has corrupted somewhere along the line.
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
..
Format all your data in system via CWM - then reinstall your ROM from scratch, it'll fix any coruption issues. ->>> Important >>> Make sure you make/get a PIT file for your device before you change anything in case you need to sort your partitions out for a reflash
I'll give it a try thank_you...
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
How bizarre , I'd stick with the custom ROM for now just in case something else gets crazy corrupted - This Kitkat stuff atm is causing havoc all around.
Yeah I think you're right, maybe different batches of phones and buggy kitkat are causing problems for a few of us? It'll all get ironed out in the end hopefully..
Sent from my SM-N9005 using xda app-developers app
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Colide said:
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Click to expand...
Click to collapse
got the same problem as yours, no idea why though, after the update samsung keyboard and action memo stopped working.
I think I will wipe it tomorrow but it seems it's not working either
I'm checking around and they say that problem probably lies in the application S Pen Keep, there is no data on this one ... I guess as you said it's linked to the handwriting recognition. tried to do that using Snote transform into text as well and it immediately stopped working as well..
For time being I'm using different keyboard and I like it better than stock one. I really don't want to wipe a phone. Takes so much time to install everything back.
Sent from my SM-N9005 using Tapatalk
Did u guys intentionally or unintentionally uninstalled Samsung apps? From what I've understand, certain Samsung apps needs to be either freeze thru TB or disable it...
Haven't touched it. I've upgraded to KitKat without updating a bootloader and it happened.
Sent from my SM-N9005 using Tapatalk
same here, got the OTA update, after that it simply stopped working.. I don't need the keyboard .. I need the action memo more
Mine still isn't working, I'm on omega rom now so it doesn't affect me, but it still does it if I flash stock... Strange..
try to download another stock rom? maybe that will fix it.. if it did .. let us know... try to download the newest one that came up in Poland..
mine got fixed by formatting and wiping, re-download another stock rom I guess yours has some form of data missing ..
@Colide , just go back to factory settings , will resolve the issue, do it from the recovery of course.
I kinda hate it to wipe data. Lot of apps to reinstall. Thanks for a tip. ?
Sent from my SM-N9005 using Tapatalk
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
ex-28 said:
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
Click to expand...
Click to collapse
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
@rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
FYI, on my stock AT&T S5 I had S Health "go bad" a little bit, finishing building a Samsung ID and updating it from their store fixed it.
Don't know if that helps or not, just a data point.
ex-28 said:
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
Click to expand...
Click to collapse
You forgot to use the @ to mention @rovo89.
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Greycloak42 said:
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Click to expand...
Click to collapse
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
Xeio said:
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
Click to expand...
Click to collapse
so you have s health running with xposed or wanam installed ?
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
siyue78 said:
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
Click to expand...
Click to collapse
I don't think root is the problem , as my phone and many others arerooted with twrp installed and shealth was working 100 % something to do with the xposed and / or wanam
divineiniquity said:
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Click to expand...
Click to collapse
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after you reinstalled s health is it running ok now with xposed installed ? if so could you please give more details on the steps you took and it is just xposed or wanam you have
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yah it took me a while to get s health working again as well , hoping for a fix soon.
Can confirm this on a Sprint S5. Rooted with chainfire autoroot and installed xposed and TWRP 2.7 and had S Health and Healthservices crashing like a drunk teenager. Uninstalled xposed and rebooted, S health now works. Guess I have to sit through Youtube ads for a while.
Ahh... Thought the problem was only for me. Hope @rovo89 could fix it soon.
may be can help to find the problem
hi everybody, i am a noob in android ect, BUT maybe it can help you : i am on i9500 omegaV20 perseus18, i modded my phones with root explorer, i add libs, perms, framework ect, modify my build prop /SM-G900F/kltexx/jfltexx , i did a lot of upgrade in samsung app store, AND I GOT S5 APPs WORK perfect, health widget work ect all works, and i got xposed ...
so to resume : i got S5 healths WORKING perfectly with xposed. hope it can help you.
Yup I also installed a different rom all working great now
Sent from my Sm-G900W8 using Tapatalk
I had the same concern, and after installing a new firmware on the SM-G900f .
I took the opportunity to not do the update shealth and securestorage..I can enjoy and wanam, Xposed
no problems with health
Hello
Every time I reboot my phone, I loose the notification accesses for android wear, runtastic, coffee...(all except Glanceviewmk).
Am I the only on with this issue? Do you know how to solve this problem? Thank you
I have met this issue wit both OMEGA and Imperium ROM on Lollipop.
I had the same problem, I was advised that if you are rooted then you can use Titanium Backup to freeze GlanceViewMK. This cured it for me.
philcoo2 said:
I had the same problem, I was advised that if you are rooted then you can use Titanium Backup to freeze GlanceViewMK. This cured it for me.
Click to expand...
Click to collapse
Cool, thx! I will try and and update this post if it works
I have the same problem but I have no root is it something I can do? Or must I root? I don't know exactly how I root S4
It has worked. Thx a lot! It changes my life!
In order to root your S4, you can see here
http://forum.xda-developers.com/showthread.php?t=2219803
It hapens me with i9506 stock 5.0.1, any news?
pille1 said:
It hapens me with i9506 stock 5.0.1, any news?
Click to expand...
Click to collapse
I had the same problem, but freezing/disabling GlanceViewMK seems to have solved the problem. You can either freeze it with TitaniumBackup or simply rename /system/app/GlanceView/GlanceView.apk to something like GlanceView.apk.old (in case you want to re-activate it).
Thanks for the tip mate.... gymkmb I had the same issue and found this.