Hi, I have installed CM10.1.3 stable on my US Cellular XT901 electrify M. The ROM is same as for XT907. everything works fine until after few days my some of the apps specifically games starts freezing giving error ' process.system not responding' and game also force closes. After that every other game or browser like chrome start to Force close giving same error. I reflashed the ROM in clean way.
wipe data/factory reset
wipe cache
manual format system
mount system(tried without this step also, nothing changes)
flashed ROM zip
wipe dalvik cache
after activation reboot
flashed Gapps
Tried slim bean ROM build 7.1......having issues with musicFX and poweramp compatibility.
tried different 4.3 ROMS they all feel somewhat laggy.
So can anyone suggest me any solution for CM10.1.3? or suggest another 4.2.2 based stable custom rom.
Back up whatever you need to and reflash back to stock 4.1 using Matts Utility ( Look in Developement Section). Then download and read the instructions on how to flash Liquid Smooth. Its by far the smoothest and astest rom ive used on my Droid M. Except i cant get my bloody Whatsapp contacts to sink. Good luck.
I used liquid smooth and loved it... except batery life which sucked really bad!... it made my M's batery life feel as bad as my Galaxy Nexus was... Terribad!
..
I've tried AOKP and never looked back, batery life is awesome!
Also, big part of Liquid Smooth's slickness is due to the launcher it comes with => Nova Launcher.
Thanks for the reply.
can you provide the link for Liquid Smooth V2.9 because i have v2.8 and it is not working fine. Not able access quick settings menu!!
Does making Nandroid restore to stock 4.1 will help?
Related
It's currently 7am on monday morning, and I have college. I haven't slept at all because my [red lens] defy has been giving me problems.
I've been trying to re-flash CM7 to get a clean install of it, with no frills/apps that I've installed over time.
I've done a factory reset through CWM, and re-flashed CM7.1 from here:
http://download.cyanogenmod.com/?type=stable&device=umts_jordan
I've tried finding GApps for this, but to no avail. None of them install properly (CWM says they have, but actually hasn't - It's nowhere on my app drawer/home/manage apps).
I've tried adding an account to sync but when it asks what google products I want to install (such as YouTube, Maps, StreetView), it crashes mentioning "process com.teamdouche.pacman"
That's problem 1
Problem 2 is my Home and Search button no longer work! I've tried everything I could google for, but nothing has helped.
[Edit: they do vibrate, but nothing happens]
Any help on these matters would be much appreciated, as this is really annoying :/ Thanks.
Also I've just realised the apps in Manage Applications are all my old apps, even though I've actually formatted my SD card in CWM since, each has a SD card icon, and is taking up 0.00B space,but I'm just wondering how they even show there..
Did you try flashing the CM7 kernel ?
Or did you mount /system ?
Herpderp Defy.
Here's my About Phone info:
Android Version - 2.3.7
Baseband Version - EPU93_U_00.59.01
Kernel Version - 2.6.32.9-gb08c3c8 [email protected] #1
Mod version - CyanogenMod-7.2.0-RC1-Defy-KANG (CM7 White Rabbit)
http://forum.xda-developers.com/showthread.php?t=1510063 <- WhiteRabbit
Do you have a link to the CM7 Kernel? :S
System is mounted
I've managed to get Market installed, but it only opens once, and when I try to download something it Force Closes, and then after that it force closes when I open it.
Flash stock rom for noow ....
Sent from my MB525 using XDA App
dude, restore stock room, and try flashing an official cm7, what i think is that the room that you flashed is corrupted or something like that
1º: Reflash a stock room
2º: Get a official stable CM7 room ( http://download.cyanogenmod.com/?type=stable&device=umts_jordan )
3º: Don't forget to wipe all data, cache and dalvik cache.
4º: See if that works and thank me for this
EDIT:
Here is a link to Gapps, just in case (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip )
good luck with your defy
I have a problem where when I clear the Dalvik Cashe, it says E: Unknown volume SD_ext... People have said on other forums that this is not a problem, but I believe it is because it only happens with ICS roms, and when this started happening, the camera and gallery also stopped working. When I launch the camera or gallery, it says "media scanning" and it immediately closes the app. Anyone have any ideas about this. I'm worrying that I've broken something and I won't be able to use an ICS Rom. So far I've tried a few ICS roms and they all have this problem, but I didn't have this problem with ICS roms before. And Gingerbread roms are fine. None of the problems above.
Did you flash this way?
- Flash CF Repack via Mobile Odin
- Stay in recovery and do the following
- Fullwipe (factory reset)
- Flash ICS ROM
- Fullwipe (factory reset) again. This is important.
- Reboot device.
If you didnt full wipe before and after flash this may of had something to do with it.
Try reflash this way especially if camera is still working on GB.
I also get that same message but no problems with camera. On MIDNOTE ics but also tried TRR 1.5 ics
It isn't a problem. All ICS roms say this. Even on the Galaxy Nexus.
I used Redpill recovery...some say nonsense, but it worked like a charm. I flashed the Midnote ROM w/Chinese leak base (which has Chainfire's kernel in it), then I was able to flash any thing else over that...AOSP, MIUI, ect...
It worked for me.
I will be downgrading from PA 2.99 to PA 2.54 in hopes Jellybean 4.1.2 will play better with wifi. Does anyone know which Gapps should be flashed with it? And will I have to do a full wipe or will clearing cache and dalvik suffice? Thanks!
pottersam said:
I will be downgrading from PA 2.99 to PA 2.54 in hopes Jellybean 4.1.2 will play better with wifi. Does anyone know which Gapps should be flashed with it? And will I have to do a full wipe or will clearing cache and dalvik suffice? Thanks!
Click to expand...
Click to collapse
Go back from 4.2.x to 4.1.2 - unless I'm mistaken & stand corrected, it is necessary to do a full wipe, factory reset, wipe system , wipe cache partition and wipe dalvik cache before switching to PA 2.54, after making a (CWM) backup first.
I ran PA 2.54 myself briefly and used the recommended one: gapps-jb-20121011-signed
And, yes - PA and Kaos Droid under 4.1.2 have no issues with WiFi whatsoever, but - I'm back running rooted stock Rom with franco kernel, with a few tweaks, no lags and the added bonus of excellent standby battery life.
Letitride said:
Go back from 4.2.x to 4.1.2 - unless I'm mistaken & stand corrected, it is necessary to do a full wipe, factory reset, wipe system , wipe cache partition and wipe dalvik cache before switching to PA 2.54, after making a (CWM) backup first.
I ran PA 2.54 myself briefly and used the recommended one: gapps-jb-20121011-signed
And, yes - PA and Kaos Droid under 4.1.2 have no issues with WiFi whatsoever, but - I'm back running rooted stock Rom with franco kernel, with a few tweaks, no lags and the added bonus of excellent standby battery life.
Click to expand...
Click to collapse
Excellent info! I really wish I read this before bootlooping my device, looks like I'll be forced to full wipe . Luckily nothing really important was on the device.
What made you switch away from PA back to stock?
pottersam said:
... nothing really important was on the device. What made you switch away from PA back to stock?
Click to expand...
Click to collapse
Backing up is the key to flashing Android roms & kernels, we've all paid our "dues" in hard lessons on skipping or rushing without doing a proper safe.
I've flashed majority of the roms & kernels, some briefly and others ran for a while, more than a quick test drive or spin to get a real feel for whether it's for my device to meet my objectives - stability, reliability and good battery life/standby time without pushing it for speed/gaming, all of them are fast for Angry Birds. Tablet UI and landscape views are important, as long as the icons & fonts are "readable" - even with progressive lens at my age. PA is nice, and like several others, great with tablet UI but - except that it's not "easy" on the eyes for long period of time.
BAMF's Paradigm's 2.4.1 grouper rom is also great if you wanted to try it out, solid on 4.1.2 with many nice features - rooted stock rom with a custom kernel is a nice compromise, and best on battery life for my usage - down the road, when the 4.2.1 bugs are worked out in a future update, I would switch & upgrade to have the option of taking full advantage of all the Google Apps preloaded on the device.
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Hi everyone,
Until recently I've been using a KitKat based ROM and I was pretty OK with how my NOTE 3 SM-9005 was performing. However, a few days ago I decided to try a Lollipop based ROM and the problems started. I had similar problems with 3 different ROMs with great reviews. My battery went, for example, from 100% to 15% in ONE HOUR while streaming from YouTube. It never did that before. Also, It sometimes gives a "system stopped responding" error or something like that (it's like the equivalent of explorer.exe crashing on Windows) and after a few seconds it starts working again. Other system apps crash as well every now and then and sometimes the phone just decides to restart by itself.
I initially used Philz recovery and after the initial errors I switched to TWRP and started from scratch. I completely wiped my system internal space before flashing and, of course, I wiped dalvik cache and cache before and after flashing the ROM. I only used recommended gapps. Also, I did not restore any system apps. I started from scratch after the installation and the problem is the same.
To be more exact, I tries flashing so far the following ROMS, experiencing more or less the same problems on each:
temasek's UNOFFICIAL CM12.1
AryaMod V5.4 TW Lollipop Official BOB6
BlissPop 3.5 Unofficial
I also tried the Dirty Unicorns v9.4 ROM from the Original Android Development section but this one went on a reboot loop initially after the first restart so it never really even installed.
At this point I believe I might have done something that I should't have, but it seems strange because this is not the first time I am flashing a new ROM and I never had problems in the past. Also, my NOTE 3 SM-9500 did not have any problem on my previous KitKat ROM. Did I miss something? Should I have used another kernel? If I understood correctly, the ROMs come with a recommended kernel already. If this is not the problem, what could it be? Should I have done any additional thing before flashing a Lolipop ROM after using a KitKat ROM?
I now installed an app for trying to find out what exactly drains my battery but this is not the only problem. The system itself is really unstable.
I would really appreciate some help, suggestions, or opinions. I really don't know what else should I be doing at this point.
Thanks a lot!
Apparently is the media server eating all that battery (currently 68%).
I will format the SD card hoping this fixes the issue.....but could this have something to do with the system error and, sometimes, restarts?
Well I really don't know what to say! A lot of people report battery problems on 5.0 just because they didn't wipe the phone while coming from KK! But you did, so that's no go. Battery life on LP is much better than KK for me, at least 20% better if not more. And I didn't face any system crashing issues either! Don't really know what's going on with you mate.
Someone suggested that maybe I shoud update the bootloader and modem to a Lollipop version but I really couldn't find any info on how to do that.
Formatting the SD card just slightly reduced the battery drain. The phone is still discharging like crazy. Any suggestion on how to update the bootloader and modem?
Thank you.