Hi everyone. I've installed TheROM build 23 on my beloved Optimus 2X, everything was great, everything worked, but now 1 problem occured for me - Google Settings (Google Play Services) started to FC every time on startup. I've had this problem on tonyp's ParanoidAndroid ROM, the T5 build had no problems with this, and with this rom this problem re-appeared. It could happen either after I changed the DPI settings in TheROM Hybrid menu, or after installing feav's camera, which i guess is not the case. I've tried to reset the DPI to back what it was, to clear all the data of Google Play Market, Services, Framework, and it still FC's. Anyone had the same problem? Any ideas on how to fix it?
Try Parameters => Applications => All => Menu touch screen => Re-init preferences..
Reboot and retry.
So, i had the same issue last week on TonyP Build 5, no way to recover (even deleting and restoring Play store).., just after a couple of hours after flashing Camera feav.. Only way was to restore previous save of Rom via CMW..
Related
First off, this is a great ROM. Since I purchased my NC a couple months ago, I have had CM7 (up to nightly 32), Deeper Blue's 3.0v4 and Ultimate Droid and this one, IMHO works better even with a couple bugs and wonder if anyone else has had the same issues and found a workaround.
1) I get an error message that says "android.process.media has stopped working" and it force closes whatever media I am using except video and also affects the market when I try to download an app. I have cleared the dalvek cache and also reinstalled the ROM and I am still getting the error.
2) Issues downloading and sideloading apps. Some apps, mostly games and wallpapers will force reboot when I try to download or sideload them. For sideload, I have used Root Explorer and Easy Installer.
For first time installation of this ROM, format system, data and cache before the installation.
Worked fine for me.
Cheers!
I ROM'ed my phone from PilotX Rom to Cyanogen Mod (cm-10.0.0-galaxysmtd-2.zip).
That worked but then I didn't have my Google Apps.
I booted into Recovery and added Google Apps (the latest) then I got the error message
"Unfortunately, Android keyboard (AOSP) has stopped"
Then I booted into Recovery again and did a fresh ROM to Cyanogen Mod and this time and installed the "one previous" Google Apps (gapps-jb-20121011-signed.zip)
Now when I reboot my phone takes me directly to the "enter your Google account details" screen, but I can't do that because I have the "Unfortunately, Android keyboard (AOSP) has stopped".
Right now I can't even get to Settings / Applications / Keyboard to delete data or clear cache.
The Cyanogen Mod ROM seems like a big improvement over the (old) PilotX ROM I was using before. Please help me to resolve this problem.
Update: I ROM'ed it again without choosing to also install the Google Apps.
Now I have the Google apps and I was able to type without the "(AOSP) has stopped" error.
I entered the details for my Google accounts. I now see (at least most of) my contacts. (A problem yet to be worked out? Or just in the process of sync'ing?)
I hope this keeps working.
Now I need to get all my old apps back.
I used Titanium Backup
I also chose the backup option when ROM'ing.
Bug (PA 2.6 build 14, kk 126) -- trying to access "About Phone" crashes Settings menu
Long-time lurker, first time contributor -- I would have posted this in the dev forum thread, but unfortunately I'm a newbie (at least by post count) and don't have posting privileges there. Suppose that's what I get for being all silent-like.
Phone model: p990hN (Canada)
ROM: PA 2.6, build 14
Kernel: kk exp 126
Bug occurred shortly after flashing the above (with standard JB gapps) from a full wipe (full wipe/factory reset, wipe system, wipe dalvik), then installing PA, gapps, and kk in that order (followed by some user apps). When attempting to access the "About Phone" sub-menu from the Setting menu, I'm booted out of the Settings app with the error message "Unfortunately, Settings has stopped". Rebooting and trying to access the "About Phone" menu again yields the same response. Also tried clearing data for Settings, but the same behaviour occurs.
Phone operation seems otherwise normal (obviously awesome given that I flashed from a full-wipe something like half an hour ago), and this problem doesn't appear to otherwise affect the user experience, so definitely not an important bug, but just thought I'd get it out there.
(if tonyp reads this -- thanks for everything!)
Edit2: Updated Settings.apk which _should_ fix the Settings FC when going to Settings -> About phone.
Thanks at @kenra for reporting this and sending a log. Another great example why logs are important, as I don't have the ROM flashed there's no way to fix an issue without logs - so keep that in mind
http://tonyp.hopto.org/temp/Settings.apk
Click to expand...
Click to collapse
Remember you have to push it yourself to system/app. Set permessions when done
Custom40 said:
Remember you have to push it yourself to system/app. Set permessions when done
Click to expand...
Click to collapse
Oops, search fail for me. Updating Settings.apk and fixing permissions worked for me. Thanks!
Q&A for [ROM][SlimKat][4.4.4] [unofficial]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Anghirrim said:
Finally tried the cast fixed version and still have boot loop. So back to version 8.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem with 8.4. With 8. everything works fine
IparryU said:
Cast version works perfectly fine.
Any chance you could include OmniSwitch in the next build @infrag? And possibally an option to use that as default recents? If not, no problemo!
Click to expand...
Click to collapse
Reposting here.
Proximity
Anyone else having problems with their proximity sensor?
updated modern, still getting invalid mmi
I was getting loads of chinese text through with the ussd/mmi system like trubul here, infact I made a thread about it. And also the loss of ussd code functionality with "invalid mmi code" error that he described.
Azlanhu says:
"had the same problem. Apparently, u need to flash the new modem/baseband I9305XXUFNI3 . "
Trubul seems satisfied with the solution, however when I flash the modem linked, whilst it sorts out the Chinese text, I still get invalid mmi codes all the time.
Am I missing something? Is a baseband something separate I need to flash, and if so where can I find it. Or something else?
Cheers.
I9305 (d2lte) SlimKat
I would like to know is it possible to install in Germany the SlimKat D2LTE version, or it may thereby lead to problems?
SlimKat vs SlimSaber
I know that Slim Saber Saber with the mod has been created, but I do not see quite the difference, so I would like to know your opinion of what you think are friendly for BATTERY?
Google Play No connection issue
My i9300 is stuck in a no connection issue in all the gapps, tried everything, clearing cache, data and even hard resetting
I have a rooted Slimkat 4.4.4 build8.0, stock Slimkat's kernel
Sorry for my bad english
SlimKat 4.4.4 8.6 Camera issue
Really nice rom - well done! The only issue I found so far on i9305 is that the camera does not work - it crashes when trying to access it. Even installed Camera MX but that freezes the phone completely on a black screen and a restart is required. I've noticed others were having the same issue. Are there any fixes for this?
Anghirrim said:
Hi, camera used to be fixed by just going back into CWM and wipping cache + dalvik cache. It used to work for me.
For the DPI, did you activate the root in the security option. I think you need it.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same issue with my camera. It was working before V8.6 but now I can't seem to fix it anymore.
No wiping of cache, even clean install (with format of /system) didn't do any good.
I also tried to extract various camera2.apk packages from older versions but I always run into the same problem
when starting up the stock camera app (other camera apps result in a freeze of the entire phone).
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
TheDesperadoz said:
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
Click to expand...
Click to collapse
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
woww thanks you
Is there a way to return to the AOSP recent apps window? The only thing I don't like on this rom is the recent apps window and how it looks and also the fact that there's a gesture instead of a clear recent apps button
Sent from my GT-I9305 using Tapatalk
nielowen said:
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
Click to expand...
Click to collapse
Thanks for the support. I already tried this twice though (and yes I followed the instructions to the letter) but I get the same annoying "unfortunately camera has stopped"
popping up when I then start the CMfix app.
I'm just not sure if this is a ROM issue or if this might be due to a conflict between my apps. Maybe I will try a clean wipe, of cache and system, then reboot into ROM
and see if the camera will work or not. This should tell me if it's ROM related or not.
I hate to restore everything afterwards though and to return to the issue for further investigation
I'd be glad to hear if someone else found an alternative solution!
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Finally got the camera working again
nielowen said:
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Click to expand...
Click to collapse
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Also one could try installing a different GAPPS build - there is a stable one from mid September and various betas up to a day ago,
maybe that might be another cure (or cause) to fix the camera bug.
Slim install failed
hi people who can not install Slim, brings in TWRP 2.7 Failed with what have for a recovery flashed her. sorry for my english
https://drive.google.com/file/d/0B4k...ew?usp=sharing
TheDesperadoz said:
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Click to expand...
Click to collapse
Hey! Tried this and the other mentioned stuff several times but still no success... has anyone heard from other ways to get the cam to work? or maybe an alteration of the quoted post?
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh: