turtle187
Member
this is a jelly bean problem for most Samsung phones
heres how i fixed it first i made it a system app with titanium backup and went to the /system/app folder and had to reinstall did the setup then i rebooted to see if it sicked it dident what it did was keep crashing not sure why. so i moved it back to a user app , did clean up the dalvik cache in titanium , redid swiftkey set up and rebooted and bingo it stayed as default
now for why it dosent stay default when you download it from the play store it installs to /data/app-asec do to it being a paid app and for some reason when the phone boots i dosent seem to boot from that folder and when you do what i did it puts it back in the app folder and it boots correctly i also believe that you could freeze the stock keyboard but if swiftkey fails you would have to unfreeze or you could be screwed and not have a key board at all
when you update swiftkey it mite go back to the /data/app-asec folder
hope this helps any one with this problem
heres how i fixed it first i made it a system app with titanium backup and went to the /system/app folder and had to reinstall did the setup then i rebooted to see if it sicked it dident what it did was keep crashing not sure why. so i moved it back to a user app , did clean up the dalvik cache in titanium , redid swiftkey set up and rebooted and bingo it stayed as default
now for why it dosent stay default when you download it from the play store it installs to /data/app-asec do to it being a paid app and for some reason when the phone boots i dosent seem to boot from that folder and when you do what i did it puts it back in the app folder and it boots correctly i also believe that you could freeze the stock keyboard but if swiftkey fails you would have to unfreeze or you could be screwed and not have a key board at all
when you update swiftkey it mite go back to the /data/app-asec folder
hope this helps any one with this problem