i am thinking about trying out stock from on my LG Optimus G, i didn't use it a lot when i got the phone bcs it didn't work properly but the newest version fixed the bug i had.
So basicly have been running Cyanogenmod since it was first released by Ricardo, but i kinda having BSOD from time to time, and it's external_modem that causes it, and i am wondering if that will stop if i run the stock rom.
ino i got more "freedom" with Cyanogenmod then stock, but well i use Apex Launcher anyway, and if i root stock rom i can do all the same things.
and no it's not one of my apps i use that gives me BSOD, even running clean rom with no other then stock CM apps instead i get the BSOD so i am kinda sure it's the rom/kernel that's buggy.
BSODs for me were related to the Chrome Beta I was using. After latest updates, I'm BSOD free
Related
This is my first thread here at xda
I don't know if this issue is already known or if it's just me with this problem. I have an HTC Evo and I've tried both Evervolv Roms for Android 2.3 http://forum.xda-developers.com/showthread.php?t=878020 and 2.2 http://forum.xda-developers.com/showthread.php?t=840285. Both Roms have problems with connecting with WiFi automatically, even when connecting manually, and require me to constantly turn the WiFi on and off to connect. Sometimes a reboot is needed on the 2.3 version because the WiFi gets stuck on "turning off". I'm wondering if there's a fix for this or if the developer of Evervolv will fix this in the future. I'm not able to comment on the developer's thread so this is my only way to get the problem out there. Also in the 2.3 version, the application launcher crashes often and requires a reboot each time to get anything to work. Flash Player doesn't seem to work at all (in fact only way i was able to install it was through Titanium-backup, as trying to install it from the market doesn't work) . I've also noticed random reboots on both versions 2.2 and 2.3. I really like the 2.3 Rom but the constant crashes of the app launcher forced me to switch to the 2.2 version and the WiFi problems persist on that as well. (if anyone asks why don't i just try another launcher, it's cause i like stock Android launchers the best )
Welcome!! The 2.3 rom is still beta so issues will be there. Are you using stock kernel? I've used cm roms and know you must change your wifi policy to never sleep. Not 100% sure if that's where your problem lies but its worth checking. Also the aosp roms IMO are still kinda iffy. Most seem very promising and some run very well but all still need alot of work. If it is becoming to big of an issue I'd nandroid backup, completely wipe and format and try a sense based rom, im trying Koni's ELITE and so far, im very impressed. Just a Thought.
Hi community. I'm new to thus phone. I've been around for a while but never created a profile here. I unlocked the boot loader and rooted it. First from installed is aopk with Franco kernel. Seems to be running okay but I am getting random force closes here and there from different apps. Not sure if this is ice issue or rom. Its intermittent so not an annoyance yet. Got some freezes when typing horizontally on the keyboard and xda app fc as well as other apps. I am running yakju. Would I benefit from just going back to stock and just keeping unlocked boot loader and rooted? Is there more stability with 4.04 vs 4.2 ? Being as this is my first Google phone I'd like to always get updates from Google without too much hassle. Please input and I'm always willing to take criticism.
When you get freezes and closes from apps randomly, I always tend to blame the rom. It could be the kernel too.
If you're wanting official updates then I would go with the stock rom. I flashed a custom rom and tested a few of them out and they were pants so I just roll with a rooted stock rom.
Just flashed the new Franco kernel and it sped things up. Haven had any freezes yet. Just running the kernel out of the box without any tweaks. Seems snap pier too, specially in app drawer.
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
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
Before the official v20b update came out, I was installing 5.0.2 AOSP based ROMS without issues. Used The Pagel's TWRP method to upgrade from 10r to 20b with no issues. AOSP ROMS based on 5.0.2 didn't give me issues at that point either. As soon as 5.1 ROMS came out, I started getting an error where the phone would go dead on me until I did a battery pull. It happened on BlissPop once and it increased on Candy5. Thinking it was a CM bug, I went back to my nandroid backup of 20b and now it is happening there too!
On the AOSP ROMs it's happened when the phone goes to sleep, if I try to update AdAway or the internal ROM's Ad Blocker, or simply when installing some CM themes. On v20b, it happened when I tried to reboot after updating my hosts file using AdAway.
On AOSP based ROMs, it does this randomly, and more with some ROMs than others. This will happen whether I use the kernel that came with the ROM or 777kernel, only script I use is the Android Cid camera script for AOSP based Roms. With stock v20b, I use the oversharpening script and textdroider to adjust the DPI. That's it.
When it happens, the phone just shuts off and the screen is completely unresponsive and the hard buttons do not work. Not even pressing power+down button does anything.
I need your help guys. Thanks for your replies!
Same problem here on 5.1 roms. I haven't tried rolling back yet. Came from Kitkat.