Anyone else experiencing problems and/or general instability with the new nameless ROM builds
div9013 said:
Anyone else experiencing problems and/or general instability with the new nameless ROM builds
Click to expand...
Click to collapse
Afraid your question isn't specific enough to elicit directly helpful responses. Did you flash a custom ROM and are now experiencing problems with your phone after this? If so, what kind of problems? There are far too many custom ROMs out there for a generic solution to apply and, needless to say, a good deal of personal research and caution needs to be exercised before one proceeds with a custom ROM installation.
Larry2999 said:
Afraid your question isn't specific enough to elicit directly helpful responses. Did you flash a custom ROM and are now experiencing problems with your phone after this? If so, what kind of problems? There are far too many custom ROMs out there for a generic solution to apply and, needless to say, a good deal of personal research and caution needs to be exercised before one proceeds with a custom ROM installation.
Click to expand...
Click to collapse
Well yes, I did specify the ROM name. It is quite literally called Nameless ROM. The problems that I am experiencing are with the latest nightlies and this instability specifically affects the the dialler applications, sometimes it works but most times whenever I get a call on my phone I just get the pop up "Unfortunately the dialler app has stopped"
I have wiped cache and dalvik cache, reflashed the ROM and the Gapps to no avail.
div9013 said:
Well yes, I did specify the ROM name. It is quite literally called Nameless ROM. The problems that I am experiencing are with the latest nightlies and this instability specifically affects the the dialler applications, sometimes it works but most times whenever I get a call on my phone I just get the pop up "Unfortunately the dialler app has stopped"
I have wiped cache and dalvik cache, reflashed the ROM and the Gapps to no avail.
Click to expand...
Click to collapse
Apologies. I was also being too general in my response. I checked a few Nameless fora on the web and it would appear such instabilities are not uncommon with nightly builds as is often the case with all custom ROMs still undergoing development. Your best option might be to flash a stable version or, if not out of your preference, revert to stock.
Larry2999 said:
Apologies. I was also being too general in my response. I checked a few Nameless fora on the web and it would appear such instabilities are not uncommon with nightly builds as is often the case with all custom ROMs still undergoing development. Your best option might be to flash a stable version or, if not out of your preference, revert to stock.
Click to expand...
Click to collapse
Yes I would prefer to not reverting to stock. I guess I shall be looking at other ROM's that have similar features. Thanks for your help.
Related
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
kamp said:
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
Click to expand...
Click to collapse
FYI, CM10 is an AOSP based ROM.
I've experienced nothing but smoothness from CM10. Have you been checking the MD5 sum? Could be a bad download, I've actually had to download a ROM more than once from the CM servers because the sums didn't match up.
I'm on latest paranoid droid 2.21 with trinity kernel alpha 67. oc to 1.3ghz/384gpu interactive. I've had paranoid droid since 1.6 and i've been experiencing similar lag OP described. Mainly opening google now, camera app, settings. Have not tried stock 4.1.2 rom yet... although I'm really tempted to flash back to stock since it seems to solve the lag problem for some people. I've played with all the settings but to no avail. It's frustrating seeing how people are saying their jellybean galaxy nexus is so smooth and flies while mine stutters intermittently all the time
Here's a quick video i made demonstrating some of the lag
http://www.youtube.com/watch?v=Tq7mhqmKZtA
would like to know if others have a similar experience as me. Whether this is normal behavior or is there something I need to change/tweak?
lcambriz said:
FYI, CM10 is an AOSP based ROM.
I've experienced nothing but smoothness from CM10. Have you been checking the MD5 sum? Could be a bad download, I've actually had to download a ROM more than once from the CM servers because the sums didn't match up.
Click to expand...
Click to collapse
Thanks. I have checked all the MD5 sums - they all match up. I've tried a lot of roms based on CM10 - CM10 nightlies, JellyBro, Paranoid and Paranoid dark, but still the same issue.
I should have clarified what I meant by AOSP based rom. I meant any roms that doesn't have too much changes from pure AOSP (Eg. stock rom, Android Revolution and the roms by Team EOS)
When I flash CM10 based roms, even the initial setup seems to be lagging (I've been doing clean installations - format cache/system/data, clear dalvik). For example, on the initial setup screen, upon selecting the language and hit next, it takes a lot longer (probably around 10 seconds or so) to progress to the next step whereas anything based on stock takes me to the next screen within a second.
I'm not too sure if my perception of lag is different from others. I've actually come from using Galaxy S2 (I've decided to try GN after accidently dropping my S2 in the washing machine). I've never had this sorts of lags on any of the CM10 based roms on S2.
It looks like some of these lags go away if I disable fsync in the kernels, but not all the lags
maniaxzero said:
I'm on latest paranoid droid 2.21 with trinity kernel alpha 67. oc to 1.3ghz/384gpu interactive. I've had paranoid droid since 1.6 and i've been experiencing similar lag OP described. Mainly opening google now, camera app, settings. Have not tried stock 4.1.2 rom yet... although I'm really tempted to flash back to stock since it seems to solve the lag problem for some people. I've played with all the settings but to no avail. It's frustrating seeing how people are saying their jellybean galaxy nexus is so smooth and flies while mine stutters intermittently all the time
Here's a quick video i made demonstrating some of the lag
http://www.youtube.com/watch?v=Tq7mhqmKZtA
would like to know if others have a similar experience as me. Whether this is normal behavior or is there something I need to change/tweak?
Click to expand...
Click to collapse
Yeh, i'm having similar lags on my phone on any CM10 based roms (including Paranoid). One thing that sort of helped me was disabling fsync (on Franco's kernel). Or try flashing the stock rom and see if it gets better. At least stock rom seems to be very smooth in my case.
kamp said:
Hi,
I've only got my Galaxy Nexus earlier this week. I tried out the stock rom for a day, then decided to switch to CM10.
It looks like whenever I flash CM10 based Roms, I experience lags when opening applications, reading/writing files to the system, however I am not experiencing these issues in any AOSP based roms.
For example, when I restore SMS by an app called SMS Backup & Restore, on AOSP based roms, the restore happens A LOT quicker than CM10 based roms.
I've tried CM10 nightly from 10/10 as well as JellyBro. I've done complete wipe (format /system /data /cache, clear dalvik, delete Android folder from internal SD). I've also tried different kernels (Franco and Trinity seemed to be populat in the forum) but didn't make any differences. I am still getting the annoying lags in CM10 based roms.
Is this normal for CM10 based roms? or is there anything I can do to fix the issue?
Click to expand...
Click to collapse
Yeah, I'm basically having the same problem. When I went back to stock, it seemed to be a lot faster. Granted, I did reinstall all my apps at that point. When I get a minute, I'll probably reinstall cyanogenmod 10 to see if it is still slow or not with a fresh install.
kamp said:
Thanks. I have checked all the MD5 sums - they all match up. I've tried a lot of roms based on CM10 - CM10 nightlies, JellyBro, Paranoid and Paranoid dark, but still the same issue.
I should have clarified what I meant by AOSP based rom. I meant any roms that doesn't have too much changes from pure AOSP (Eg. stock rom, Android Revolution and the roms by Team EOS)
When I flash CM10 based roms, even the initial setup seems to be lagging (I've been doing clean installations - format cache/system/data, clear dalvik). For example, on the initial setup screen, upon selecting the language and hit next, it takes a lot longer (probably around 10 seconds or so) to progress to the next step whereas anything based on stock takes me to the next screen within a second.
I'm not too sure if my perception of lag is different from others. I've actually come from using Galaxy S2 (I've decided to try GN after accidently dropping my S2 in the washing machine). I've never had this sorts of lags on any of the CM10 based roms on S2.
It looks like some of these lags go away if I disable fsync in the kernels, but not all the lags
Yeh, i'm having similar lags on my phone on any CM10 based roms (including Paranoid). One thing that sort of helped me was disabling fsync (on Franco's kernel). Or try flashing the stock rom and see if it gets better. At least stock rom seems to be very smooth in my case.
Click to expand...
Click to collapse
EnderTheThird said:
Yeah, I'm basically having the same problem. When I went back to stock, it seemed to be a lot faster. Granted, I did reinstall all my apps at that point. When I get a minute, I'll probably reinstall cyanogenmod 10 to see if it is still slow or not with a fresh install.
Click to expand...
Click to collapse
I can attest to having annoying lag in CM10 based roms such as ParanoidAndroid. It's always smooth in the beginning but as I install more apps, it just slows down considerably.
I just wiped my entire phone last night and started over running Rasbean Jelly 10.16 Build(AOSP Based) with Trinity A67 1344/307 and it's as smooth as it can get. I have about 130 apps installed and it's still fast as ****. Google now/ google search takes about 1 sec. to start versus it can take up to 5-6 seconds before on CM based roms. All apps are responsive and starts super fast.
Don't know why this occurs but it seems that some galaxy nexus' like ours just dont like the CM10 Builds..
So if anyone is having lag problems, I'd recommend the rasbean jelly + trinity combo before looking for a new phone..
Do you guys see "lags" on stock rom? Yes? Then return the device.
maniaxzero said:
I can attest to having annoying lag in CM10 based roms such as ParanoidAndroid. It's always smooth in the beginning but as I install more apps, it just slows down considerably.
I just wiped my entire phone last night and started over running Rasbean Jelly 10.16 Build(AOSP Based) with Trinity A67 1344/307 and it's as smooth as it can get. I have about 130 apps installed and it's still fast as ****. Google now/ google search takes about 1 sec. to start versus it can take up to 5-6 seconds before on CM based roms. All apps are responsive and starts super fast.
Don't know why this occurs but it seems that some galaxy nexus' like ours just dont like the CM10 Builds..
So if anyone is having lag problems, I'd recommend the rasbean jelly + trinity combo before looking for a new phone..
Click to expand...
Click to collapse
Thanks, glad to see I'm not the only one. I'd check out Rasbean Jelly + Trinity, but I'm using this as an excuse to dump VZW and go with the Nexus 4 next week.
Hi Folks
On my device the lag is connected to how full the file system is.
If I copy lot of music on the phone then it becomes laggy
If I delete it, it is still laggy.
To recover its full smmothness I have to do a full wipe and then restore the FW.
Did anyone find the same problem?
thnx
lollonet said:
Hi Folks
On my device the lag is connected to how full the file system is.
If I copy lot of music on the phone then it becomes laggy
If I delete it, it is still laggy.
To recover its full smmothness I have to do a full wipe and then restore the FW.
Did anyone find the same problem?
thnx
Click to expand...
Click to collapse
This can be fixed with fstrim. Here is a cwm zip that runs fstrim as a script upon each boot and places a fstrim.log file in /data/local to verify it worked. It trims /system, /data and /cache.
https://www.box.com/shared/l5afni1mxe1wpb2ubw3s
Edit:
*Important* There are some emmc cards that have a so called "brick bug". Use this app to check and use the fstrim at your own risk.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my Galaxy Nexus using Tapatalk 2
From searching around on this topic is seems that, especially with the new CM 10.1, it is considered quite safe to dirty flash up to a more recent CM version.
My usage scenario is using the nightlies on a regular basis, but falling back to the stable 10.0 on the odd event in which I need to use tethering or some other feature which is buggy in the nightlies -- but I must avoid the need to restore from backup apps, call logs, etc.
Is it also considered safe to dirty flash down from a nightly 10.1 to 10.0?
kambufi said:
From searching around on this topic is seems that, especially with the new CM 10.1, it is considered quite safe to dirty flash up to a more recent CM version.
My usage scenario is using the nightlies on a regular basis, but falling back to the stable 10.0 on the odd event in which I need to use tethering or some other feature which is buggy in the nightlies -- but I must avoid the need to restore from backup apps, call logs, etc.
Is it also considered safe to dirty flash down from a nightly 10.1 to 10.0?
Click to expand...
Click to collapse
That is really dirty!
Safe? It is not going to brick your phone if that is what your worried about.
Stable? Maybe but probably not so much.
bry7 said:
That is really dirty!
Safe? It is not going to brick your phone if that is what your worried about.
Stable? Maybe but probably not so much.
Click to expand...
Click to collapse
i would not recommend it.
kambufi said:
From searching around on this topic is seems that, especially with the new CM 10.1, it is considered quite safe to dirty flash up to a more recent CM version.
My usage scenario is using the nightlies on a regular basis, but falling back to the stable 10.0 on the odd event in which I need to use tethering or some other feature which is buggy in the nightlies -- but I must avoid the need to restore from backup apps, call logs, etc.
Is it also considered safe to dirty flash down from a nightly 10.1 to 10.0?
Click to expand...
Click to collapse
Short answer, no
When flashing in the same version, it might work, but ANY dirty flash is bound to leave stuff behind
When flashing to a different android version (aka, different CM number), then a dirty flash will most likely screw things up and you'll get a ton of FCing if you can even get it to boot. Each android version DOES have stuff in common, but the framework for each is heavily modified from previous ones, so a dirty flash is not recommended
Sent from my PG06100 using xda premium
Hey all so I'm fairly new to this whole world of rooting and flashing custom ROMs (although I know how to) and I had just a couple of questions. I was thinking of flashing CM10.1 but I'm unsure of which to flash, should I just flash the most recent snapshot or the most recent stable version(10.0)? Is it more experienced people who typically flash the nightlies? I tried posting on the CM forums but they are incredibly slow.
Also, I know that there is no "best" ROM but I would like to know: what ROM are you on? Why did you choose it?
Personally I need my ROMs to be pretty stable for work, so I won't go with nightlies because they can vary in reliability somewhat.
I had avoided CM10.1 based roms for a while because I was worried about stability. My first couple of attempts didn't go so well. Lately though I've found that most all of the 10.1 based ROMs have been pretty solid and just vary in features and looks more than anything.
After using various stock ROMs (all freeza's), I switched over to LiquidSmooth for a while. When Carbon split off I followed that thread for a little while, but the last release just didn't work that great for me and I switched back to LiquidSmooth. I've found it rock solid stable, excellent battery life, and all of the AOSP features I need.
I think you'll find an extremely wide array of opinions on the ROMs. Everyone likes different ROMs for different reasons. It took me a solid day of flashing various ROMs when I first started out, so take your time and try everything that looks interesting. There are some amazing developers around here!
Spuddlethud said:
Personally I need my ROMs to be pretty stable for work, so I won't go with nightlies because they can vary in reliability somewhat.
I had avoided CM10.1 based roms for a while because I was worried about stability. My first couple of attempts didn't go so well. Lately though I've found that most all of the 10.1 based ROMs have been pretty solid and just vary in features and looks more than anything.
After using various stock ROMs (all freeza's), I switched over to LiquidSmooth for a while. When Carbon split off I followed that thread for a little while, but the last release just didn't work that great for me and I switched back to LiquidSmooth. I've found it rock solid stable, excellent battery life, and all of the AOSP features I need.
I think you'll find an extremely wide array of opinions on the ROMs. Everyone likes different ROMs for different reasons. It took me a solid day of flashing various ROMs when I first started out, so take your time and try everything that looks interesting. There are some amazing developers around here!
Click to expand...
Click to collapse
Thanks! I figured there would be a range of opinions but still wanted to ask. So does that mean I have to wipe data/cache and flash the new nightly every time it comes out?
sevenpioverthree said:
Thanks! I figured there would be a range of opinions but still wanted to ask. So does that mean I have to wipe data/cache and flash the new nightly every time if came out?
Click to expand...
Click to collapse
No, not necessarily. The trick though is that you can never be certain where your issues may be coming from if you don't do a clean flash (wiping everything). You'd be amazed at how many completely unexplainable little nagging bugs show after a few consecutive dirty flashes. So by dirty flashing a lot of the time you don't know if the latest version has bugs or if the dirty flash is causing little issues so you've essentially added another layer of troubleshooting difficulties to the issue. You'll also find that 99% of the time if you haven't done a clean flash the devs will tell you to do a clean before you try anything else when reporting a bug. That kind of says something.
Spuddlethud said:
No, not necessarily. The trick though is that you can never be certain where your issues may be coming from if you don't do a clean flash (wiping everything). You'd be amazed at how many completely unexplainable little nagging bugs show after a few consecutive dirty flashes. So by dirty flashing a lot of the time you don't know if the latest version has bugs or if the dirty flash is causing little issues so you've essentially added another layer of troubleshooting difficulties to the issue. You'll also find that 99% of the time if you haven't done a clean flash the devs will tell you to do a clean before you try anything else when reporting a bug. That kind of says something.
Click to expand...
Click to collapse
Sooooo I'm just gonna go ahead and assume I should buy titanium backup pro haha
Support the developer if you can afford it, if not the free version has the main features you'll need.
Sent from my SPH-L710 using xda premium
Vfan23 said:
Support the developer if you can afford it, if not the free version has the main features you'll need.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Oh I plan on it I love supporting open source developers, means more for everyone!
Wipe data/cache/dalvick for a clean install. Possibly even internal sometimes. Just make sure whatever you are flashing is on the external card, such as your ROM and GAPPS.
Sent from my SPH-L710 using Tapatalk 2
GiantJay said:
Wipe data/cache/dalvick for a clean install. Possibly even internal sometimes, just. Ake sure whatever you are flashing is on the external card, such as your ROM and GAPPS.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Oh thanks for the tip and do I have to wipe them in that order? I feel like it's always listed that way for a reason
Also what ROM are you on and why did you choose it?
I would HIGHLY recommend to you Liquid Smooth RC2. Its blazing fast, amazing battery life, loads of customizations, Android 4.2.2 and it is based off of CM10. Just try it out and you'll never flash another ROM!
Joe0113 said:
I would HIGHLY recommend to you Liquid Smooth RC2. Its blazing fast, amazing battery life, loads of customizations, Android 4.2.2 and it is based off of CM10. Just try it out and you'll never flash another ROM!
Click to expand...
Click to collapse
I've been deciding between CM10.1 and liquidsmooth lol but I really can't decide between any of them
sevenpioverthree said:
I've been deciding between CM10.1 and liquidsmooth lol but I really can't decide between any of them
Click to expand...
Click to collapse
Once you start flashing, you'll probably never want to stop.
I might suggest going with a pure CM 10.1 to get an idea of things. Then go to one of the 4.2.2 ROMs based on 10.1 so you can get a gauge of the differences. Right now though my vote is LiquidSmooth for the ROM.
Spuddlethud said:
Once you start flashing, you'll probably never want to stop.
I might suggest going with a pure CM 10.1 to get an idea of things. Then go to one of the 4.2.2 ROMs based on 10.1 so you can get a gauge of the differences. Right now though my vote is LiquidSmooth for the ROM.
Click to expand...
Click to collapse
I think I'm just gonna go with LiquidSmooth then
I have another question, do I have to flash my gapps RIGHT after the rom? or can I just do the rom and all other apps after I reboot and see what I have
And do you recommend using goo manager? It looks nice but I feel like doing it myself with adb is a lot safer
sevenpioverthree said:
I think I'm just gonna go with LiquidSmooth then
I have another question, do I have to flash my gapps RIGHT after the rom? or can I just do the rom and all other apps after I reboot and see what I have
And do you recommend using goo manager? It looks nice but I feel like doing it myself with adb is a lot safer
Click to expand...
Click to collapse
I use TWRP which allows me to queue up multiple zips to flash in one go. So I do the ROM and gapps.
Never took the ADB route for the S3, but that's just laziness. I used this to root and install the recovery. Then I just put the ROM and gapps on the SDCard and started flashing.
Hello! I've searched quite a bit but have been unable to find anything to address the frustration I'm having. Recently I have been having an issue where my phone will restart itself at random intervals. The best way to recreate the issue is to use a streaming media app like Spotify/YouTube/Google Play Music/etc but it does happen at other times as well. This will occur on all ROMs I've tried including AOKP, CM10.1, Carbon, etc.
I believe I have narrowed the issue down to the 3.4 kernel as all the ROMs I've flashed in recent weeks have been using 3.4. If I use an older ROM (such as the stable release of CM10 with the 3.0 kernel) I do not have the issue.
It gets even stranger...I have found that LeanKernel is the only 3.4 kernel to work and has been stable for about 3 days on my device. So apparently I am stuck with reflashing LeanKernel after each ROM update if I want to run the latest and greatest.
My question is two-fold....
Is this a known issue for the AT&T GS3?
Any suggestions to fix this problem?
For the record, I have reverted to the stock, unrooted ROM and do not have the issues there.
Thanks in advance for any guidance!
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
xBeerdroiDx said:
Issues and bugs with 3.4 kernels are known. This is not specific to you.
I am running tasks 4/23 with the packaged kernel. No issues. Full wipe is key
Click to expand...
Click to collapse
Thanks for the feedback. I may look at Task's ROM in the future.
I am "new" here, so for start warm Hello to everyone In fact I registered here 4 years ago but I used to be only reader until now.
I have a LG G3 d855, and after using CM on Desire Z many years ago and after Nexus 4 I knew from the begining that I want only AOSP based ROM. So I rooted phone, installed TWRP then Lolli-based Xenon HD and now - Euphoria. The latter one seems to be very slightly slower than former one, but more stable. But one thing came to my mind and I am not sure. What is your experience with various AOSP based ROMs? Is it worth to try another one than these two mentioned here? Perhaps I should go with pure CM 12.1, which above ROMs are based on? Just which of AOSP ROMs is the most stable and fast for you? Are there any really pure AOSP 5.1.1. ROMs in "stable" version for G3? I couldn't find one... Any suggestions are welcome.
Xenon HD is AOSP based and i use it ATM. It's stable for me and i use experimental build. I also tried Slim Minux build, wich is also AOSP based but it was kinda slower for me. Euphoria OS is CM based i think. And you do have a pure AOSP rom in android dev section, just look a little harder next time. And, as always, Google is your friend.
F-AOSP suits my taste. Absolutely smooth and battery friendly (stock aosp kernel). But there aren't many features like CM for this is based on pure AOSP. Note that this rom is very stable and proximity works very well.
CM based are cool and packed with features, but I found our AOSP versions tend to be a little smoother, eve if you have to exchange some features for performance. F-AOSP is leading in performance for me, but since I take a lot of pictures... well... you can guess. :|
DeHuMaNiZeD said:
Xenon HD is AOSP based and i use it ATM. It's stable for me and i use experimental build.
Click to expand...
Click to collapse
I had a small problem with double screen tap wakeup with Xenon, so I gave Euphoria a shot I thought Xenon was somewhat CM based too?
I also tried Slim Minux build, wich is also AOSP based but it was kinda slower for me. Euphoria OS is CM based i think. And you do have a pure AOSP rom in android dev section, just look a little harder next time. And, as always, Google is your friend.
Click to expand...
Click to collapse
Thanks, I saw it in ROMs section, but it is in "testing" stage for now, perhaps I should start testing it too
filbertmang said:
F-AOSP suits my taste. Absolutely smooth and battery friendly (stock aosp kernel). But there aren't many features like CM for this is based on pure AOSP. Note that this rom is very stable and proximity works very well.
Click to expand...
Click to collapse
F-AOSP is in "testing" stage as I could see, but it is great to hear from you that it is very stable Thanks, I'll give it a try. Usually I don't need to many gimmicks in OS, Android i its pure form is very mature and usable now.
MidnightDevil said:
CM based are cool and packed with features, but I found our AOSP versions tend to be a little smoother, eve if you have to exchange some features for performance. F-AOSP is leading in performance for me, but since I take a lot of pictures... well... you can guess. :|
Click to expand...
Click to collapse
Whenever I plan to take good photos, I take my "serious" camera with me, so using somewhat limited Google Camera app is not a problem for me. And another voice for F-AOSP, thanks!
Definetly, F-AOSP deserves a handful of votes. It's vanilla AOSP, very stable and the animations don't lag like CM Roms do.
Yup I'm using the F-AOSP by kjjjnob. Stable and would definitely recommend to other users.
Any one knows when updating the custom rom, do you have to wipe everything again or just clear cache ?
What is the proper procedure to update ?
I do not want to reinstall all my apps again
_DeeK_ said:
Yup I'm using the F-AOSP by kjjjnob. Stable and would definitely recommend to other users.
Any one knows when updating the custom rom, do you have to wipe everything again or just clear cache ?
What is the proper procedure to update ?
I do not want to reinstall all my apps again
Click to expand...
Click to collapse
If you REALLY do not want your apps to dissapear, try flashing a custom rom and wipe cache and dalvik cache only. If you are coming from Stock and want to migrate ti AOSP, pretty sure you need to wipe data and not just the cache. Keep in mind that clearing the cache only will cause problems like FC or overheating. I suggest you use Titanium Backup.
Hit the thanks button if I helped you.
filbertmang said:
If you REALLY do not want your apps to dissapear, try flashing a custom rom and wipe cache and dalvik cache only. If you are coming from Stock and want to migrate ti AOSP, pretty sure you need to wipe data and not just the cache. Keep in mind that clearing the cache only will cause problems like FC or overheating. I suggest you use Titanium Backup.
Hit the thanks button if I helped you.
Click to expand...
Click to collapse
Thanks for the advice!
I've tried to update the custom rom and only wiping cache and dalvik cache but android errors are popping up.
Perhaps I'll try backing up my apps first before wiping everything else.
Thankfully I made a backup at recovery of my rom first.
MidnightDevil said:
Definetly, F-AOSP deserves a handful of votes. It's vanilla AOSP, very stable and the animations don't lag like CM Roms do.
Click to expand...
Click to collapse
_DeeK_ said:
Yup I'm using the F-AOSP by kjjjnob. Stable and would definitely recommend to other users.
Click to expand...
Click to collapse
After a first day with F-AOSP I can only confirm your experience! Very fast, reliable and stable. I just used Open Gapps instead of suggested packet. The only small glitch I've noticed were web and calendar applications not conforming to material design, but I guess it is common thing for AOSP and I easily have fixed it with appropriate apps from google play.
galaxy s3
sylwiuszp said:
After a first day with F-AOSP I can only confirm your experience! Very fast, reliable and stable. I just used Open Gapps instead of suggested packet. The only small glitch I've noticed were web and calendar applications not conforming to material design, but I guess it is common thing for AOSP and I easily have fixed it with appropriate apps from google play.
Click to expand...
Click to collapse
I'm guessing F-AOSP brings AOSP apps, so flashing a stock google package (from opengapp) would replace the aosp components with google ones
MidnightDevil said:
I'm guessing F-AOSP brings AOSP apps, so flashing a stock google package (from opengapp) would replace the aosp components with google ones
Click to expand...
Click to collapse
Yes, it seems so. Both browser and calendar are part of AOSP ROM, but I've installed mini version of GAPPS, so only calendar gets replaced when you install newer version from Google Play. Chrome from Google Play was installed besides AOSP browser. This is somewhat a plus for CM based ROMs, where at least browser has more modern, material UI.