Hi all! I'm getting some weird and specific errors in various places during my operation my Kindle Fire (rooted running Jelly Bean 4.1 CM10 20121119-1523-Linaro)
Here are the ones I can think of:
If I bring the normal volume slider all the way to zero, I get stuck in an infinite loop of the Settings App closing and restarting. This also happens if the slider gets automatically put there, like if I try switching to silent mode.
If I try selecting Themes in Settings, I get the "Unfortunately, Settings has stopped." message.
At random intervals, I get a message saying gapps has encountered an error and closed (it never closes any app, just gives me that pop-up)
I've encountered all of this on the previous 4 or so version of CM10, and I've even tried unrooting and re-rooting (although, as newb, I can't be certain I did that to the fullest possible extent). I'd be happy to put some log stuff up here, but I don't really know how. I'm reaching out to you for some help, oh community!
Thanks in advance!
Installing a custom ROM, this kind of instability is kinda expected. Try a different ROM though. I've found that Jandycane is the most stable among the Jelly Bean ROMs I've tried.
jji7skyline said:
Installing a custom ROM, this kind of instability is kinda expected. Try a different ROM though. I've found that Jandycane is the most stable among the Jelly Bean ROMs I've tried.
Click to expand...
Click to collapse
Good news! In learning the ropes of installing a DIFFERENT ROM (i.e Jandycane over CM10) I have discovered the missing step I was doing to try to reset (simply enough, it was the Factory Wipe in TWRP. Not sure how I missed that) Jandycane was great, but there were some weird oddities to it (but luckily, no errors) that I simply could not deal with. The main thing was the fact that whenever I returned to the homescreen, I would have to choose either the Launcher or Trebuchet. Each seemed to have their own homescreens, and some settings would change one but not the other, and vice versa. Also I was stuck with the Tablet Setting UI, which squishes things into almost unreadable columns.
But it was an EXCELLENT learning process for me, thanks so much!
Related
Hi there, since I'm not obligated to post replays under development thread here's the place to do it.
I just installed newest version of LiteROM (used 0.7 previously) and I found some unpleasant behaviors.
First of all - I couldn't get wifi connection to work. Password was ok but it continuously tried to authenticate or get proper ip. Re-flashing with stock rooted rom, then gettin literom over it worked like a charm.
But, after installing newest LiteRom I'm getting message every time I reboot device: ... android.process.acore has stopped working.
Also, when trying to set lockscreen wallpaper it gets me a message: ... TwWallpaperChooser has stopped.
So, is there any proper fix to get things right or maybe I'm doing it wrong?
(I did full wipe before all installations but it does not resolve issues)
First, you might try downloading the ROM again(preferably from a pc) to see if maybe the download was bad.
Sent from my jelly monster.
Already did. Then reflash with FULL wipe - nothing. As long as sim card isn't on, there's no issue with .acore (it happens even when switching airplane mode on/off). I also tried to wipe contact and contact manager data but with no good solution.
Another thing is - I've tried IcePop rom and it worked fine. IMHO, there's something in literom that causes such bad behavior.
I would be grateful for helping me resolve that :good:
Hmmmm. The only problem when i flashed literom is if i didnt install the stock gallery then it seemed to crash the lockscreen wallpaper when trying to choose a wallpaper from settings and did not give me and option in quickpic.
Sent from my jelly monster.
I need help finding a stable rom. I've tried a lot over the past few months, and they all have problems rendering my tablet inconvenient for use.
Before I was using a CM7 mod which was working pretty well, but then I upgraded to an ICS rom somewhere around September. That's when the performance started to drop. Then somewhere around March I upgraded to a Jelly Bean rom, and that's where the serious problems started.
At first I tried SmoothRom, but that just wouldn't install until I did some tweaks (removed an "assert" line of code). And even then, stuff in settings kept crashing. So I tried the HellFire rom, which worked but was having some serious performance problems. The launcher I was using (Apex) was slow and unresponsive at times, and various apps (browser, music player) kept crashing at times.
A few weeks later, I tried SmoothRom again, and it seems to work better. No more tweaking needed to flash it, and no more crashing in settings. But the problems were even worse. My browsers (Dolphin, Chrome) kept crashing frequently when I browse, the music player (winamp) kept stopping, and worst of all, sometimes my kindle won't wake up from sleep (I have to hold my finger on the power button to turn it off before turning it back on).
I just don't know why I keep having problems. So today I tried using the modified stock roms. The http://forum.xda-developers.com/showthread.php?t=2211872 won't even flash (something about failing). So I tried the older modaco rom. I had a problem with a launcher (Holo) where it kept saying "holo launcher stopped unexpectedly" every time I tried to run it. I tried rebooting, clearing the cache, but it still had problems. Plus I found out not a lot of apps were compatible with my gingerbread based android os, so now I'm going to give this rom a shot:
http://forum.xda-developers.com/showthread.php?t=2051331
But basically, why am I running into so many problems? Is this normal, or is there something abnormal with my kindle fire?
Do a full wipe while installing a new rom. I don't think Holo Launcher works with stock. And for the stock modded, are you sure you downloaded the main not alt zip?
Sent from a DROID Pro that is rooted and runs vanillalvl's CM7
Hmm......I use twa_priv's latest CM10.1 ROM (4-01-13) and it runs sweet. I have my Kindle set up to boot either CM7 or JB.....the CM7 ROM is sblood's November 2012 release. When I get tired of JB, I will switch to GB. There are certain apps that won't perform correctly on JB but run flawlessly on CM7.
You need to start with a truly clean wiped system and SD card partition, but please make sure you have the ability to mount the Kindle's storage from recovery to place the ROM after wiping SD. Install apps sparingly so it's easier to weed out potential culprits of malfunction......it sure is hard to figure out what is going on if you install 50 apps all at once.
And remember no OS is flaw free.....they are like human beings, unique and not perfect
There are plenty of stable enough for daily use ROMs, some faring better than others.
Sent from my Amazon Kindle Fire using xda premium
Yeah, I have TWRP and I always wipe and factory reset before flashing a ROM.
Try using an Official CM10.1 from hash ode. It seems to be the most stable out there
Sent from my Amazon Kindle Fire using xda premium
You need wipe all the cache before you install any new rom
Hi, I'm using Galaxy Note N7100. I have been experiencing random freezes on my phone lately. I have tried switching from ProBam to various other AOSP roms and nothing much changed. I have cleared Cache+Dalvik every time along with Factory reset. Also, I cannot add my Google account to the newly installed rom sometimes. It shows a message that says that "Connection could not be established." Presently I am on RootBox ROM. Please help, this is really frustrating. Also, would cleaning Internal storage help in any way?
Also, I haven't flashed any kernels. Just the stock ones, that come with the respective Roms.
Htc Pirate said:
Hi, I'm using Galaxy Note N7100. I have been experiencing random freezes on my phone lately. I have tried switching from ProBam to various other AOSP roms and nothing much changed. I have cleared Cache+Dalvik every time along with Factory reset. Also, I cannot add my Google account to the newly installed rom sometimes. It shows a message that says that "Connection could not be established." Presently I am on RootBox ROM. Please help, this is really frustrating. Also, would cleaning Internal storage help in any way?
Also, I haven't flashed any kernels. Just the stock ones, that come with the respective Roms.
Click to expand...
Click to collapse
What I would do is to install a original rom from sammy and if you still have this problem with that rom get sammy to fix it.
Just tell them what you have problems with and they will probably take it in for a fix.
And it sounds like you might have a emmc problem, have a look here as alot of users have had the same problem.
http://forum.xda-developers.com/showthread.php?t=2093599
And her is a more in detail http://forum.xda-developers.com/showpost.php?p=36499838&postcount=1
Hope it helps.
flash latest TW ROM :good:
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS
I have tried literally everything, ran super wipe script, wiped everything possible in TWRP, i have 2 roms that will work, PA 5.1(glitchy and unuseable) and hackingwiz(not a fan of the stock feel)
Ive tried probably 7 other roms and every one does the same thing, crash reboot right at or right after "Finishing Boot" then after restart does the android is upgrading this again and repeats
Any advice appreciated, thanks.
seems as though it crashes when it tries starting a certain app
have you tried another roms???