Posted this in the CM10 dev thread, but decided I may get some better help by posting here, and here's my OP from the thread:
so yesterday my phone randomly shut off and it seemed to completely reset my phone. It booted up fine with two or three apps missing and all of my settings lost. I didn't think much of it until today when I tried to fix it. I did a fully wipe because some apps had disappeared and wouldn't download from the play store and wouldn't restore from TiBu. I went ahead and did the full wipe, flashed latest gapps and my device started up. I began trying to restore my apps and what not, but at I was navigating the phone my app switch soft key and home key would not function. They vibrate when pressed but don't do anything; only the back key works. I went to settings and remapped the soft keys to see if it was just a glitch and nothing changed. Still no function, only vibration. I then rebooted to recovery and did yet another full wipe and this time tried to install aokp just to see if it was a bug with cm (yes I know aokp i built from cm but I had just downloaded the latest nightly to my phone and deleted the old one so this was a test of the new nightly). Still no cheese. I was then thinking to myself, screw it and at least try to restore some apps, but after configuring my google account and opening he play store i get a constant no connection, retry button. Most of the stock apps will not even open. I flashed a TiBu.zip to restore the app and great, that worked but restoring from in TiBu doesn't work now. I tried reflashing cm and essentially repeated the above steps without any luck. Any ideas? I can't test my data/phone connection other than the fact that after setting up my google account, my email synced and I was able to make a call because the browser won't even open. MY [email protected]$s didn't do a nandroid either
Help a desperate guy in need, please!!
PS redownloading cm and gapps right now on my computer in case of a corrupted download, but to have the issue on cm and aokp is suspicious. I'll have to wait for an hour or two because my internet speed is that slow...
Click to expand...
Click to collapse
Now I redownloaded CM10 fresh from the get.cm page and even did a md5 check and everything matched up, yet still no luck. another strange thing I've noticed is that my power menu, when I verified in the setting that all options for my power menu were selected, the only options that show up are power off, reboot and screenshot. I checked to be sure app permissions were correct and even fixed permissions from recovery. All apps that do open force close upon any activity, for example upon receiving an email in gmail, the gmail app force closes. I don't know if providing a logcat would be beneficial to anyone because I don't know how to read them.
I am currently waiting on a sense rom to finish downloading to verify that it isn't just aosp based roms, but my internet connection is terrible so the 600+mb file still has 2+hrs left. I am also downloading an ruu if nothing else works, but again with a 500+mb file it will take 2+hrs
Any help is much appreciated and I can provide more info if needed.
SOLVED
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
iElvis said:
Sounds like it might be a kernel issue. Try flashing a different one.
If nothing else works, relock and RUU.
Click to expand...
Click to collapse
Even if it's the stock cm kernel? i never had issues with it before, but I'll flash one now because luckily I have a couple on my phone already
Edit: flashed a different kernel and nothing changed, but thanks for the suggestion
So I feel as if I've been having poor GPS on any rom, whether it be AOKP, CM or even Stock based. I've tried a few apps to know luck. Using Waze yesterday, it was dropping in and out as I was going down a highway. Currently I'm using Eclipse rom on my phone. And I've tried flashing roms with TWRP and CWM with the same results.
The only thing I'm doing differently is running a 4.2 gapps made for 4.1.2 roms, could this be causing the issue?
Or should I just go root66 and redo everything?
Recon0212 said:
So I feel as if I've been having poor GPS on any rom, whether it be AOKP, CM or even Stock based. I've tried a few apps to know luck. Using Waze yesterday, it was dropping in and out as I was going down a highway. Currently I'm using Eclipse rom on my phone. And I've tried flashing roms with TWRP and CWM with the same results.
The only thing I'm doing differently is running a 4.2 gapps made for 4.1.2 roms, could this be causing the issue?
Or should I just go root66 and redo everything?
Click to expand...
Click to collapse
I experience the same issue with AOKP, CM, and stock roms. I can get a GPS lock if my phone is on the dashboard of my car, but it goes in and out if the phone is sitting on my lap. This makes it very difficult to use the S3 for turn by turn navigation. I haven't had any problems while running Eclipse though.
Try this! Worked for me. Found this somewhere on XDA
1. Download "GPS Test" from the play store
2. Turn on your GPS and open the app
3. Press the menu button and go to settings
4. Press "Clear AGPS" at the top (your phone might reboot)
5. After that go back to settings and "Update AGPS"
Or this (also worked for me - from some XDA post):
"like some of you, i too was having GPS lock issues. here's what i did which fixed it for me. can't guarantee anything, but might be worth your try.
go to application manager - click on 'mapservicesamsung' - force stop - back out then click on 'maps' - force stop - clear cache - clear data - reboot into recovery - wipe dalvik and cache - reboot.
hope this works for some of you also. my GPS has been locking within 5 secs since doing this, and it hasn't been that good since before flashing my first S3 rom back in july! =) "
Wow! The second one worked. I'm on a cm based ROM so it didn't have a the Samsung app. But I cleared the data for maps and cleared the data/cache and it worked! I even lock on inside my house.
Sent from my SCH-I535 using xda app-developers app
Recon0212 said:
Wow! The second one worked. I'm on a cm based ROM so it didn't have a the Samsung app. But I cleared the data for maps and cleared the data/cache and it worked! I even lock on inside my house.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That one always works for everyone! Glad it worked for you too!
So for some reason my phone doesn't like the dialer on every 4.3 AOSP ROM I've tried. I've been on Slim bean, Eclipse and now Liquid Smooth. I get a force close whenever I open the dialer on all these ROMs. I just Odin'd back to stock and rooted using the casual method. This hasn't happened on 4.1.2 or 4.2.2 ROMs. Something on my phone doesn't like it. I just can't figure it out. I thought going back to stock and starting from fresh would help it. Please don't ask if I dirty flash. I never do. I wipe everything a minimum of 3 times and have even wiped internal storage.
I'm using ex dialer and it works just fine. And I disabled the stock phone app. Makes me think it's a graphical issue.
Would switching kernels help?
Sent from my SCH-I535 using Tapatalk
Are you using the gapps that come with Slim? I believe that message means that the gapps package you're using is conflicted with something in the ROM or vice versa. I'm on Slim with their AIO and not having the same issue.
For example, I used to test Slim for Cordell and had the same thing happen. It happened because he forgot he had updated the gapps package he was using and I was still using the one from the site. Once I flashes the correct gapps, then the issue was solved.
I always download the correct gapps and I did so from the slim ROM website. I tried two different gapps packages from there, AIO and aroma gapps, and it still happened. This same thing happened on two other 4.3 ROMs as well, Eclipse 6.0(4.3) and LS 2.10 with the 20130813.zip gapps.
It just doesn't add up but it's still not enough of a deal breaker for me to leave 4.3 ROMs.
Sent from my SCH-I535 using Tapatalk
ExDialer is awsome, I never use the stock one anymore. I'd move on and not worry about it.
Sent from my GS3 running Pac-Man ROM 4.3 nightlies with KT747 Kernel
Sorry, not sure what it could be. Only other thing would be the kernel
So I had the issue on root box 4.2.2. I have been on this ROM before with no issues. It worked right after the initial boot up. But after I finished downloading apps from play store and a couple from my SD card is when it started not working. Pretty sure it's not rom, gapps or kernel related. If I felt like it and had the time, I'd wipe and start over but I just don't feel like doing that right now. If I ever switch to another AOSP ROM, I will try just downloading apps from the play store and seeing if that fixes it. It's just weird, that I removed all apps installed from my SD card and it still won't work. I install all of the same apps on tw ROMs and have never had these problems. Oh well. I will stick with ex dialer.
Sent from my SCH-I535 using Tapatalk
Wow! That was easier than I thought. I was using Super Backup and restoring my call logs across different ROMs. This is what was causing my dialer app to crash. All I did was go into the dialer app settings and looked at the permissions for the app and it just came to me. Maybe if I clear my call log it will work. So I did and immediately it worked. Didn't even have to reboot. Such a relief to know that the problems weren't with the ROM.
Sent from my SCH-I535 using Tapatalk
i flashed my one x with miui 4.2.14. its android version is 4.2.2. i din have gapps for 4.2.2 and so i flashed gapps 4.3. and am facing the following problems.
1. Contacts not syncing from gmail. (it syncs perfectly in other devices . but my gmail app has synced perfectly in my fone).
2. Incoming calls automatically gets disconnected.
3. Browser is crashing once i open it.
4. Play store shows "NO CONNECTION" inspite of mobile data being on.
Are the above problems due to wrong installation of gapps????
Why did you flash the incorrect gapps? That's probably the root of your problems. Get the right gapps, perform a full wipe, and flash the ROM again with the right gapps.
Sent from my Evita
I don't believe we Evita users have a 4.2.2 miui. Might wanna make sure you have the right phone.
Sent from my Wabbajack using Tapatalk Classic
Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)