This has been an ongoing problem I'd say since KitKat ROMs released for me anyway. I've seen other people post about it but it's kind of sporadic as far as who it's happening to because the majority of people don't seem to have this issue. When using an AOSP based ROM no matter what I've used (currently ParanoidAnroid, in the past LiquidSmooth, CM, and a few others) my SMS capabilities are very hindered. I can send one, maybe two texts and then it will just not send anymore until I reboot the phone. Incoming text still come in just fine. It's just when I text to someone it will sit there sending for about 30 seconds follow by "Unable to send". I tried some of the workarounds people suggested in specific ROM threads that they thought might fix it to no avail (using 3rd party SMS app, disabling Google Movies). What ends up happening is that I'll have to flash back to a Sense ROM which isn't the end of the world but I really like using the AOSP based ROMs as I can do so much more with those in the means of customization and they just seem more snappy and "familiar" to me, coming from a Galaxy Nexus that I was always tweaking and trying out new ROMs.
Has there been any fixes that people have found for this issue? As I said right now I'm running ParanoidAndroid, the latest build with PA GAPPs and I'm afraid I'm going to have to go back to a Sense app once again. I waited a couple months before flashing any more AOSP based ROMs thinking with all the updates that get done to some of these ROMs maybe whatever was causing this to happen would be magically fixed in newer versions of the ROMS. Any help/tips you could shoot my way I'd be very appreciative!
Related
Hi guys,
I'm currently running the latest nightly of CM9, really liking it at the moment but I'm always up for trying new things out. I've noticed the Omega AOKP ROM and saw it comprised of a few CM9 features.
My main question is more of a comparison, whats the difference between CM9 and Omega, are there certain benefits or which one do you solely prefer? Any info would be good so don't think I'm asking for an essay of a comparison, but just wondering if it's worth trying out, and why.
Saying that, any other ROMs that are worth trying as well?
Cheers for reading, looking forward to the replies.
I can almost bet that all the roms you can find here are good in their own way. Just try them and see which suits you better
Hey Joey.. you need to look at the changelogs. Look at what the ROMs have/come with. Flash em and try em for yourself. What works for one person may not necessarily work for another. Same with favorite features.. its all taste.
For that reason, threads like these are closed almost immediately. Its all a matter of opinion.
Omega is a Sammy ROM and CM10 is AOSP. If you don't know the difference Google it, or spend a little time on XDA.. Google is a faster answer. But in short.. things like swipe a contact to left or right for shortcut to SMS or Call, that is a stock ROM feature.. along with other features you will lose flashing AOSP.. but AOSP has its benefits too. Really, try em yourself and decide.
Sent from my Galaxy Nexus using Tapatalk 2
Cheers for replying so quickly, I figured I'd get a lot of "try it yourself" which I completely understand... and which I'll do.
I know there's a Samsung Omega ROM, but I thought there was an AOKP version as well? Im assuming the samsung one is based on the stock ROM, where as AOKP is based on open source.
Another question, when flashing a new ROM, whats the best way of restoring data. Currently using SMS backup for messages and have all contacts on google. But its just a bit of a ballache restoring apps and sync accounts, obviously I've heard of titanium backup and similar but I've read a few times not to use that to restore apps. Any help would be good as I'm slowly learning the android ways.... I've had a business supplied iPhone for years now and finally got sick of it!!
Closed, as mentioned above, you really need to try them yourself, no one else can tell you what the best fit for your usage patterns will be.
As far as backing up goes:
Titanium backup: apps (Don't restore system apps or system app data between diff roms, or even diff versions of the same rom), SMS, Call log, bookmarks (need pro for some stuff) (Generally, you can restore user app data between roms that use the same major android version, aka ICS > ICS, but not GB > ICS, you can try, at worst you will get FC's and have to do a full wipe) (Also best to grab the apps of the market and then restore data with TB)
SMS backup+: Free sms backup to gmail
Google contacts sync (!)
Hello everyone,
I have tried looking around the XDA forums regarding my issue but my case seems a bit unique and so I haven't really seen any threads that solved my problem.
I have always stuck with AOSP and AOKP roms solely for their customisation capabilities and quick updates. Only gripe I have with these is just the poor battery life, which is why I went back to using a sammy rom.
Specifically, when I use a 4.3 stock sammy rom (i.e. I was using Indie's Omega Rom when this first happened), after I record a video in instagram and try to upload it, the app crashes. I can get to the page just before the caption page and the app crashes. This isn't just specific to the Omega Rom but all 4.3 stock roms I have tried, so I'm thinking that this isn't a rom-specific issue maybe..? But it might be something to do with the camera itself?
I have tried wiping the dalvik cache, fixing permissions, and even formatting my whole phone - both internal and external storages, so I'm not sure what might be the problem. Which is why I hope someone can help me out
I have seen some threads which have said it might be an issue with changing some camera settings but I haven't touched these so that shouldn't be an issue.
On a side note, another issue I've noticed with the 4.3 stock roms is that apps such as LMT don't work even though they are running in the background and I receive toast notifications about them having root access and all. Not sure if this is related, or something else completely.
I thank you for taking the time to read this, and really hope I can get some help regarding this isue.
Regards.
having the same issue here on s3...... on mk6 4.3 rom. has also happened to me across CM11 and cm10.2 and s4 revolution rom.
anyone know what i can try?
On any stock ROM I try I can turn the phone on and use it until I turn the screen off. For whatever reason I can never get it to go back on I've tried raising the minimum processor speed and changing the governor. But when I flash aosp the problem disappears entirely. I would really like to know what's going on there's a couple stock based ROMs I would like to try
I had the same issue when I was on stock. So you aren't alone there
optimusv45 said:
I had the same issue when I was on stock. So you aren't alone there
Click to expand...
Click to collapse
did you ever find a fix? I want to try some of those qslide apps. and slightly unrelated but which ROMs have the qslide browser working?
Nope, I just flashed other roms. haven't been on stock in a while, don't know what qslide browser is
Last shot for help fixing this ive included a logcat as well not sure why i didnt do it first. ive lgnpst every bin for this phone there is and ive even tried a couple ls970 roms. the only thing that seems to boot and work correctly is kit kat (which i find horribly boring)
http://pastebin.com/hrh2MA98
I think you may want to post it in a specific stock based rom thread so that the developer of that particular rom can look at it and attempt a fix
it persists across all stock based including lgnpst flashes. I tried the nexus 4 fix just in case but that didn't help. it must be a software problem because every aosp ROM I've tried works flawlessly. its quite frustrating
I'm running LiquidSmooth v3.0 Beta (LS-KK-v3.0-2014-02-13-dlx) on my Verizon DNA and I'm pretty happy with it. Big thanks to deadman96385, santod040, and anyone else who contributed to this project!
This is the first custom ROM I've run as a "daily driver" on my DNA after ~16 months on the stock ROM, so most of my impressions are in comparison with the most recent stock HTC software. I briefly tried CyanFox but switched back to stock. I also tried the "HTC One *STOCK* ROM Port" (DLX_WL_K442_SENSE55_MR_4.19.401.8) but couldn't get it to boot; actually flashing it messed up my recovery as well. I suspect maybe my download was corrupted since other people reported success with that ROM.
Back to LiquidSmooth:
- Perceived performance is generally pretty solid. It's mostly very smooth, living up to its name.
- I do get the occasional app crash (FC); haven't noticed a pattern yet. It's not frequent enough to bother me much.
- A few times I have had the phone become unresponsive when opening the recent apps view or when trying to unlock from the lock screen. But this hasn't happened in a few days. Could be the freezing was related to one of the features I tried and later disabled (see below), or just due to the ROM "settling in" (populating caches, etc.)
- Love KitKat and the add-on features:
- I'm using the "pie control" for quick access to apps, quick screen off, menu access, etc.
- I tried HALO and couldn't really figure it out / didn't find it useful.
- I like the idea of Active Display but it didn't work that well in combination with the way I use the lock screen, so I turned it off and use the lock screen's built-in active display features instead.
- I'm using the default Google Now launcher for the moment. I like the easy access to voice search and google now. Don't like that it doesn't have multi-touch for dragging icons between home screens.
I think the battery is draining faster than with the stock ROM, though it's hard to say because I've also been using the phone a lot more actively while I get it set up and configured the way I want. It may be that the active display feature of the lockscreen is using more power?
People in the development forum mention an over-the-air (OTA) update mechanism; I haven't been able to find that yet.
There's a new version posted called 03-05-14; I haven't tried that version yet.
Anyway, I'm quite happy with this ROM and imagine I'll stick with it for a while. I would recommend it to anyone looking for a clean, fast, stable ROM, and in particular to anyone freshly rooted and looking for a solid ROM to try out KitKat and get a lot of great new features.
(note—maybe it would have made more sense to put this directly in the existing LiquidSmooth development thread, but I don't have permission to post there. And I'm not developing the ROM, just using it.)
Thanks again! Great ROM.
How much did they pay you? LOL
I tried it as well as all of the other KK AOSP ROMS. I really like AOSP.
I was on stock until viperDNA 2.0 came out, then I decided to S=OFF/ROOT/etc... and plugged Viperware in. It was awesome. Not an issue ever. So I wanted to give 3.0 a try, after trying every ROM out there (actually it kinda became like crack to me LOL).
So far after several days, it's 5x5, not an issue at all. On my phone, only the Viperware works as advertised.
That's not to say that Viperware doesn't have its issues, but I just haven't seen any yet. As I said I really like AOSP, but because Viperware uses Aroma installer, I can delete almost everything - which gives it a kind of AOSPishy look/feel.
My sig hits it; these developers (ALL of them) are amazing and do all of this for US on their own time for FREE. If I were a kagillionaire, I'd employ you ALL.
Hah! Thanks Yehuda. I started this thread because I wish there were more ROM reviews here on xda, since I don't really have time to try out every ROM. I appreciate your review of ViperDNA; maybe I'll try that next.
Update on LiquidSmooth: after a week or so I found that it wasn't as clean as I originally thought and went back to (rooted) stock for a while.
GPS doesn't work on any KitKat ROMs that I've flashed, but works fine on 4.3 stock, viper, Y18 and sense 5.5.
I feel like I must be the only one who had this issue because nobody else seems to be complaining about it.
At the same time it seems like since I've had this problem on every single one of the 15+ KitKat ROMs, that its got to be happening to others too.
Ideas?
New partitions, fire water s-off, 2.10.0000 HBOOT, running TWRP 2.7.0.8b.
Sent from my EVO using telepathic awesomeness
Seemed to be a fairly common issue with AOSP. Make a backup of your current setup. Flash back to a Sense ROM, turn GPS on and get a good lock. Once you've done this, leave GPS on and restore your AOSP ROM. Furthermore, you can also use an app like GPS Status to clear your A-GPS data. See if any of that helps. I haven't used any AOSP ROM's on the new partition setup but the fix I listed seemed to have worked for quite a few folks on the old setup running various AOSP ROM's.
Sent from my HTC device
Makes no sense to me whatsoever, but it worked! Thanks!
Sent from my EVO using telepathic awesomeness
Magnum_Enforcer said:
Seemed to be a fairly common issue with AOSP. Make a backup of your current setup. Flash back to a Sense ROM, turn GPS on and get a good lock. Once you've done this, leave GPS on and restore your AOSP ROM. Furthermore, you can also use an app like GPS Status to clear your A-GPS data. See if any of that helps. I haven't used any AOSP ROM's on the new partition setup but the fix I listed seemed to have worked for quite a few folks on the old setup running various AOSP ROM's.
Sent from my HTC device
Click to expand...
Click to collapse
YUP! Whenever I get a complaint about GPS on any AOSP roms I suggest the Sense Lock trick. It will work for some time afterward but sooner or later you will need to do it again. I can confirm this works on the new partition format AOSP roms. At least the ones I work on.