[Q] Is OmniROM compatible with franco kernel and Swype keyboard - Omni Q&A

Hey guys. I'm new to the world of Android (had a Nexus 5 since November, coming from BB and iPhone). I'm even newer to modding (unlocked/rooted/installed CM on my device 4 days ago), and I'm even newer than that to XDA (first post!) so I apologize if these questions either don't belong here or are a little naive.
I've been reading and viewing a lot of reviews on OmniROM and I'm thinking of installing it when my new device comes in this week (had to RMA due to pixel issues). For the last few days I decided to unlock/root/flash a ROM on my phone just to try it out. Based on what I've seen and read, I think OmniROM would meet my needs better than CM, so I think that's the direction I'm going to go.
One thing I want to improve about my phone's performance is battery life. I've noticed a slight improvement with CM, but not nearly the improvement others have noticed when using custom kernels, such as Franco Kernel. I know that Franco Kernel has some compatibility issues with CM, and I'm wondering if those issues exist with OmniROM? If Franco Kernel is NOT compatible with Omni, could you suggest other options to achieve the same or similar improvements to battery life?
Second question is with Swype keyboard. Swype worked great for the first day or so after installing CM, but lately I'm getting the "stopped working" dialogue box after every word I type. The keyboard doesn't go away, and I can keep typing, but I get that dialogue box after every. single. word. I have no idea if it's the rom that's causing it. I downloaded Swype off of Amazon when they had a free app giveaway, but there are no updates available there. IF the issues with Swype are linked to CM, will those same issues exist with Omni? Are there any solutions to this issue?
Thanks a lot!

No clue. Alternate kernels are NOT supported and no one on the team is going to endorse one. It might work, it might not, you will not be able to file bug reports if you're running a modified configuration.

I think that Franco will work normally. It doesn't work on CM 'cuz it's CAF ROM. As I know, Omni is not CAF based so Franco (btw for me ElementalX kernel fits better, take a look at it too) should work.

Related

Asus Transformer TF101 4.1.1 (JellyBean) ROM Feature Comparison

I saw this thread over at the Galaxy Nexus forums, and since I figured more people than just me might want to know more about the different ROMs, I thought it was worrth a thread here as well.
What I'm interested is a quick reference thread for the various Jellybean ROMs. Run by who, what's the aim, etc. Basically a quick reference guide to assist people (like me) decide which ROM fits my needs.
So far, these are the Jellybean builds that I know about for the TF101:
Team EOS 3 Jellybean nightlies
RaymanFX's 4.1.1 AOSP builds
CM10 preview edition
JellyBro (CM10 kang)
AOKP KANG
Let me know if you see anyone missing.
It would be nice for each ROM to have a a post which lists its key features:
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
State. In active development, experimental, mature, stable, abondoned, etc.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
Basically enough info to assist making a decision, without aiming for pages and pages of stuff which noone will ever bother to write (or read). See this post for an example of what I'm thinking about.
Feel free to recommend a non-default kernel for the ROM, but the focus should be on what the ROM itself offers out of the box.
Sounds good? Anyone wants to give it a go?
User summaries of the various ROMs.
I'm not guaranteeing that I will be able/willing to include all reviews here. If things get out of hand, I will edit this post to indicate so.
Team EOS 3 Jellybean nightlies:
2012.08.02: josteink
2012.08.02: fone_fanatic
RaymanFX's 4.1.1 AOSP builds:
None
CM10 preview edition:
None
JellyBro (CM10 kang):
None
AOKP KANG:
2012.08.02: K900
I've been meaning to make a thread like this, but I still have yet to find the time.
I read through all the JB threads about a week ago and Team Eos seemed to have the least amount of bugs so I chose it over the other options.
I'll start off by saying I've been using it daily since build #53 [2012-07-24] and I'm currently on build #54.
That said, here's what I've noticed so far:
Speaker volume is a bit low.
When using the HDMI out cable, sound plays via TF101 speakers, not TV speakers.
Video effects (Silly Faces) in Camera cause camera to crash.
GPS doesn't work.
Other than that, it's a very stable rom and working great. Dock functions 100%. Very responsive, stable and fast.
Also I'm using Guevor's JB Kernel 693. I just noticed 696 was released yesterday, so flashing that now .
Feel free to ask any questions about the rom. Maybe some time next week I can flash all the JB kernels out there and put them through their paces .
Note this rom is a GREAT daily driver, unless you really need GPS or use HDMI out very often, I highly recommend it.
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Great idea!
Will keep this thread under close observation :good:
CalvinH said:
Great idea!
Will keep this thread under close observation :good:
Click to expand...
Click to collapse
If you try any of these ROMs out, feel free to contribute
josteink said:
I'm also running Team EOS nightlies and I'm very happy with it.
Here's my quick summary:
ROM: Team EOS nightlies
Non-stock/AOSP features.. Notification toggles. Overclocking. (Themes added in build #55?)
Aim...................... Stability
ROM base................. Team EOS
State.................... In active development
Release-type............. Nightly
Build(s) tested.......... 2012.07.23 to current (2012.08.01). With and without dock.
Not working / problems:
Audio generally low. (Seems to be a general JB problem across devices?)
HDMI audio out
Have encountered 2 sleeps of death while using it for around 2 weeks.
Everything else seems to be working.
My only complaint so far is lack of a status-bar battery-widget for the dock, like you have in Megatron (ICS). But I don't think any other of the JB ROMs available has that one either.
Click to expand...
Click to collapse
Check out Dual Battery Widget from the play store. It has an option for having the dock battery level show in the status bar.
Also I'd like to add I haven't had a single SOD on Team Eos nightlies (been on since #53). But I have had a few reboots, all but 1 have occurred while not using the tablet.
Sent from my Transformer TF101 using xda premium
Officialzies for AOKP
Aim of the ROM. Tweaks, Stability, Speed, AOSP-like cleanness, etc
AOKP.
State. In active development, experimental, mature, stable, abondoned, etc.
In development.
ROM base, if any. Based on AOSP, AOKP, CM, etc.
AOKP.
Release-type/frequency: Nightly, interval, fixed releases, etc.
Frequent releases but no fixed timing.
Non-stock/AOSP features. Swag, Toggles, Theming, OCing, etc.
AOKP.
I've tried both AOSP build 3, and CM10 Kang.
I am eagerly awaiting a stable jellybean rom I can daily.
Using RaymanFX's 4.1.1 JB
Hi guys, thought I'd share this info. I'm using RaymanFX's ROM and overall it's running well. My only issue so far is that Google Now crashes right after launching. It was working before I started adding new apps, so I'm guessing there is a conflict with another app. Unfortunately I don't know which one it is. I'm guessing maybe gmail, Google maps, or Google +. I haven't tested the HDMI or used in the dock yet but WiFi and graphics seem good. The ROM itself is extremely lean, no bloat to speak of.
I had to flash the ROM a second time to get it working but it's possible that I goofed it up the first time because it does take a bit to do the initial boot and I was getting impatient and thought it locked up and rebooted.
I'll probably try the EOS ROM next.
Nonek said:
Team EOS nigthly.. Rayman has not updated this one in awhile and has been working on other projects. I'm not sure actually how good CM10 is, but I've run both this and TeamEOS and I changed to a TeamEOS / KAT 1.14 (now) combo and I have never looked back.. TeamEOS has the most fleshed out version of JB in my humble opinion.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
If just install the rom 0.7 from raymanfx. The first time from me i root my tf101 !
It work great, some small functionnality are missing on the keyboard but it gives a second life to our baby.
Sent from my Transformer(4.2.1 rom 0.7) using xda app-developers app
Yep, I' using 0.7 from Raymanfx also. Its great to have the mutli-user support, but I think it comes with significant overhead and I'm not sure the TF101 can handle this.... still testing and will keep everyone informed.

Out of these three ROM's, which is best?

In terms of stability, built-in features, battery life, performance and anything else important that I might have forgotten, which of the below three ROMs is top dog? Just so you know, I plan on flashing the non-overclocked GPU version of _motley's Linaro kernel regardless of which ROM I choose.
Paranoid Android
Glazed
JR6
krion64 said:
In terms of stability, built-in features, battery life, performance and anything else important that I might have forgotten, which of the below three ROMs is top dog? Just so you know, I plan on flashing the non-overclocked GPU version of _motley's Linaro kernel regardless of which ROM I choose.
Paranoid Android
Glazed
JR6
Click to expand...
Click to collapse
I'm running paranoid myself but the best advice I've read when people ask this question is try them all. What's best means to me might not be what it means to you. I've tried all three myself and they were all stable, I like paranoid because of the per app density feature it has. It was just updated again today btw. Motleys kernel is awesome I like the one without gpuoc. Good luck, happy flashing
Thanks for the advice. Also, I have another question for anybody who can answer. These three ROMs seem to be mostly similar in terms of features, so it's actually kind of hard telling the differences. So, what I'm trying to ask is, what sets each ROM apart?
krion64 said:
Paranoid Android
Glazed
JR6
Click to expand...
Click to collapse
Does anyone know the answer to this? I used JR5, EOS now PA. They are all very similar, as you would expect. PA has more config options for setting up tablet UI which is key for me and the reason I use it currently (with Nova Launcher).
I liked JRX Roms as they have lots of apps inbuilt that the others dont, ie working Flash, GAPPS etc.
I'm also using Trinity kernel which is working great, again, I have not noticed much difference between them all.
Try them and take your pick
I say EOS with Mortley kernel

[Q] What ROM are you using and why, and how often do you change?

I'm a new Android user and loving all of the options out there in terms of Kernels, ROMS, etc, but I find myself being overwhelmed with all of the options out there. So far I'm pretty set with running franco Kernel (running r20 right now), but I find myself always wanting to try out new ROMs, and I'm hoping that doing all of this switching around isn't going to mess up my device but I just can't nail myself down to a ROM that I'm set with.
I had been running CM 10.1 nightlies, but just recently a couple of days ago I jumped over to MiNCO because of the support for franco Kernel.
Now I find myself looking at the Xylon ROM but am worried that jumping around from ROM to ROM is going to mess with my device.
What ROMs are you guys using, and why are you using them? I find myself that the most important factors for me are battery life/performance, quick toggles, and the power menu.
I havean EVO 4G LTE .. ever since i got the o.g. EVO I was hooked on them. But I use a stock with goodies Rom by flex. Its a great rom has everything I need and its super smooth
Sent from my EVO using xda app-developers app
I generally stick to CyanogenMod. I keep an eye on the changelog and flash new nightlies when things I want are merged.
I've messed with AOKP and MIUI in the past but they're not really for me.
Cyanogenmod 10.1 Jellybro because it has everything I need and is clean code (no dirty hacks). Used to be a fan of aokp but too many dirty code and unicorns for me.
Sent from my Nexus 4 using xda premium
zephiK said:
clean code (no dirty hacks).
Click to expand...
Click to collapse
cm is my favourite rom, but thats not really the truth what you say. in order to stuff in tons of devices that normally do not run aosp they have to stretch the base wide open with hacks. this is the hackiest rom in the android scene and it must be, otherwise people out there wouldnt know what android is. thats why cm traditionally never had so much traction on this plattform than on others, simply because uncompromised aosp is leaner and more optimized for android itself and the nexus plattform. on a legacy device i'd always suggest cm, thats obvious. on nexus cm may not be the obvious best choice anymore, because the others are likely faster, more stable, have less daily fallouts, and in some cases have more features, like aokp, if youre the kind of guy that likes that sort of thing. if i flash cm here, its because i like their creative/inventive spirit and would like to support the project overall. flashing is easy though, trying out a couple of em isn't that much of a problem. (-:
Paranoid android. Not even considered any other ROM since I flashed this one. Its just so amazing. I couldn't live without all the colours that change per app, and all the other features it has.
I suggest trying it out now.
Sent from my Nexus 4.
With my previous device, s2, I changed a lot, from RR to AOKP to CM etc etc, I like them all.
On my N4, I'm using stock until a really good-good ROM comes out, I don't have any problems, other than battery, so I don't panic, YET.
calanizzle said:
With my previous device, s2, I changed a lot, from RR to AOKP to CM etc etc, I like them all.
On my N4, I'm using stock until a really good-good ROM comes out, I don't have any problems, other than battery, so I don't panic, YET.
Click to expand...
Click to collapse
Yeah other than battery issues everything else is a "nice to have" and nothing I "absolutely need"
I've been on xylon w matrix kernel
For battery customization and speed.
Sent from my Nexus 4 using xda premium
For me its PA rom....Ive tried every rom because I love flashing lol....but this is an honest opinion from experience....I know best rom talk is not allowed but the best to me is PA rom because of one simple reason....other than stock...its perfect!!!! And with that being said I have No issues with it very stable..super fast...alot of features man I can go on and on....if you want your N4 running perfect go PA...there are some other good roms because we have alot of elite devs in here and im sure more are on the way...but to me theres nothing better than super wiping your phone just to make sure its really clean and flashing PA...all you can say is wow after that lol......and now I change roms everytime Moles and his crew update PA....and also flash Franco kernel with this and your N4 will be excellent....
I'm currently on liquidsmooth. I've tried rasbeanjelly, Xylon, codefirex, CM 10.1, MinCo and a few others I can't remember. All were great. I'm really like liquidsmooth. It's a great balance. I flash, sometimes 3 times a day.
Setup: Code FireX w/ Faux beta
CFX is the first non-stock ROM that I decided to try because it uses the Linaro chain and I was pretty curious about the speed.
Long story short, CFX's performance is apparent as soon as you start using the device, it had much needed improvements.
Oh, and did I mention the CFX settings? Synegye's special built in mods allow you to improve your experience even more. For instance I decided to use the 6 signal Wi-Fi/Network, center clock, smaller Nav Bar, as well as dual view. This package, when combined with Faux's kernel presents you with an unbeatable experience on the best Android experience to date.​
Ace42 said:
Setup: Code FireX w/ Faux beta
CFX is the first non-stock ROM that I decided to try because it uses the Linaro chain and I was pretty curious about the speed.
Long story short, CFX's performance is apparent as soon as you start using the device, it had much needed improvements.
Oh, and did I mention the CFX settings? Synegye's special built in mods allow you to improve your experience even more. For instance I decided to use the 6 signal Wi-Fi/Network, center clock, smaller Nav Bar, as well as dual view. This package, when combined with Faux's kernel presents you with an unbeatable experience on the best Android experience to date.​
Click to expand...
Click to collapse
That sounds pretty intriguing, I think I just found the next ROM that is going to get flashed on my N4.
Nice discussion. Very interesting.
via Google Nexus 4
For reliability and just the right amount of mods for me it's been CM on any device I've owned 90% of the time. It's the least buggy for me, although of course, there will be the occasional bug along the way. Works beautifully on the the Nexus, although some mods may take longer to merge as other devices have to be taken into account.
Can't think of any "hacks" needed for CM to run on any Nexus, although much hackage needed for it to run on Samsung branded phones, and any other manufacturer that doesn't ship with AOSP and may be slow to release source. The kernel for the GN was less than impressive, but the N4 kernel is great.
Running stock rooted. Going CM 10.1 as soon as I get back home from vacation.
Skickat från min Galaxy Nexus
Stock with Franco kernel and you got the most stable combo ever seriously though. Feels very snappy while battery is great but also is really stable.
Sent from my Nexus 4 using xda app-developers app
I am flashing between a number of Roms daily. Change between cm 10.1, aokp, paranoid, slimbean, codefire. Currently on paranoid b9. I love the options we have on the nexus. It would be a lot less hassle for me if I don't have to restore my texts everytime. Still I pretty much flash a different ROM daily
kyokeun1234 said:
Stock with Franco kernel and you got the most stable combo ever seriously though. Feels very snappy while battery is great but also is really stable.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
+1 for stock with Franco.
No stable (official stable) roms out there yet that I like, and since n4 is my primary phone, I need my stability :/.
Probably will switch over to AOKP milestone or CM stable.
On past devices I've run with CyanogenMod (any variation), but on the Nexus line I tend to prefer staying with a stock ROM and a custom kernel (though I'm stock presently) for the sake of cleanliness. CyanogenMod is great, it's built by trusted developers, and all around well known for their great reputation. On the flip side, I tend to stay stock because I need to help other people out often enough that I start to forget which features were added by the CM team and which come with Android itself.

[Q] General questions from a new owner

Hey guys, I recently bought a Nexus 4 (I will get it tomorrow, but will have to wait more for screen protectors and case) and coming from an Xperia T it's like I'm a kid in a candy shop; all those kernels and ROMs, my head is spinning.
So my plan is to enjoy stock Android for 15 minutes and then root/unlock the device right away. Now, couple questions for you guys:
1, I've seen some Linaro builds of both ROMs and kernels here and there. Does it speed up the phone much? Does it make it worse (see: overheating)? Also, I don't know if I can run a stock toolchain ROM with a Linaro kernel or vice versa. How about that?
2. Regarding the kernels, I'll never stick to stock so will change to a custom one. I heard faux's and franco's (remember the latter from his very first release on the Optimus One ) are the best ones on the market and they both have customization apps. Now for what I've seen, faux's kernel provides more customization on the app, but don't know how does it perform in real-life situations, nor I do with franco's (altough I tend to prefer this one for the per-app settings). Could you guys give me some informations about this?
Thanks a lot
-Bytecode
Bytecode said:
Hey guys, I recently bought a Nexus 4 (I will get it tomorrow, but will have to wait more for screen protectors and case) and coming from an Xperia T it's like I'm a kid in a candy shop; all those kernels and ROMs, my head is spinning.
So my plan is to enjoy stock Android for 15 minutes and then root/unlock the device right away. Now, couple questions for you guys:
1, I've seen some Linaro builds of both ROMs and kernels here and there. Does it speed up the phone much? Does it make it worse (see: overheating)? Also, I don't know if I can run a stock toolchain ROM with a Linaro kernel or vice versa. How about that?
2. Regarding the kernels, I'll never stick to stock so will change to a custom one. I heard faux's and franco's (remember the latter from his very first release on the Optimus One ) are the best ones on the market and they both have customization apps. Now for what I've seen, faux's kernel provides more customization on the app, but don't know how does it perform in real-life situations, nor I do with franco's (altough I tend to prefer this one for the per-app settings). Could you guys give me some informations about this?
Thanks a lot
-Bytecode
Click to expand...
Click to collapse
1. 4.2.2 ROMs and Kernels are inteechangable. You can use any kernel with any ROM, even the stock one. However, with 4.3 , you have to match the build number of the ROM with the kernel type.
Sidenote : The Nexus 4 does not normally overheat. The glass gets warm because it's a good heat conductor, and pulls the heat out. Don't worry about it.
2. While Franco seeks to be the perfect balance between performance and battery life, faux gives you a choise: either performance or battery life, or both, in a balanced way.
I was in a similar situation as you are about a week ago. I came from a Galaxy Nexus and couldn't wait for my Nexus 4 to arrive. I too spent a lot of time in the Development forum trying to figure out which ROM would work well for my needs. In the past, I have never run stock Android. However, that was before the launch of 4.3.
Right now, I am still running stock (a whole week later!) and am really enjoying the smooth experience. With root, I can use Xposed framework to implement the few mods that I like.
Overall, I am very happy with the device. I'd give stock a try - at least a day or two, and see if it meets your needs as well.
Thanks all, I'll give both a shot. I'll give stock a shot too. First days will flash ROMs on ROMs and I will find the stablest for me
Sorry, but this is "what is the best rom/kernel" thread. Try them out for yourself and see what works for you. You mentioned some of them so just flash them first and see how they work, they're free. Personally I like franco and semaphore kernels, Neo is a good kernel for performance too, for roms I stick to the big names like CM, AOKP, SlimRoms and Paranoid.
Hey Bytecode,
Try slimbean, you probably remeber popdog's slimbean for p500, it is 10% of real slimbean on good device You will not need any custom kernel with it.

CM13 Bluetooth Problems

I have searched for literally months now, switching back and forth from stock to CM and this problem is absolutely maddening.
The bluetooth is garbage on CM. Constant stuttering. Anytime I unlock the phone, go to bluetooth settings, or even just leave the phone alone it skips horribly.
Is there any fix or resolution for this? I want the speed and features of CM, but this is ridiculous.
No, it is a CM problem and CM needs to be the one to fix it. Judging from the history of the problem, I doubt that will happen anytime soon.
For me it only stutters if I unlock the phone or if a notification comes in and when it does stutter it only stutters for 3 seconds. I'm on latest resserection remix.
That's the reason I stopped using CM13 on my Nexus 6P and probably never going back to it. At first I thought it was just a bug that cropped up in early builds and it would be quickly addressed, but when the second snapshot didn't fix it I just moved on.
I still can't believe that a serious bug that prevents the use of one of the basic functions of the phone is still ignored by the CM team. Unacceptable, if you ask me. I know CM is free, but it shows the lack of support CM has become notorious for.
That's the underlying problem with CM. There is never a "stable" build, it's a forever work in progress and by the time it reaches a point where is "good enough" as a daily driver, the next version of Android is available, so there is really no point to use it on Nexus devices anymore.
Sorry for the rant, but I was a supporter of CM in the early days and seeing it going down this road is very disappointing.
MaxNXS said:
That's the reason I stopped using CM13 on my Nexus 6P and probably never going back to it. At first I thought it was just a bug that cropped up in early builds and it would be quickly addressed, but when the second snapshot didn't fix it I just moved on.
I still can't believe that a serious bug that prevents the use of one of the basic functions of the phone is still ignored by the CM team. Unacceptable, if you ask me. I know CM is free, but it shows the lack of support CM has become notorious for.
That's the underlying problem with CM. There is never a "stable" build, it's a forever work in progress and by the time it reaches a point where is "good enough" as a daily driver, the next version of Android is available, so there is really no point to use it on Nexus devices anymore.
Sorry for the rant, but I was a supporter of CM in the early days and seeing it going down this road is very disappointing.
Click to expand...
Click to collapse
As was I. I've always loved CM. But when they're releasing "stable" builds that still have this major flaw....on a very popular device, makes me wonder what the hell they're doing.
What a shame.
CM is GARBAGE. As is almost anything based of it other then maybe RR. This is why everyone is re baseing off AOSP.
Sent from a Shaftamle Nexus 6P
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Double R - 6.0.1
To add onto what @Shaftamle said, ultimately the reason there are even CM based ROMs around is because CM has done the work to bring up support for almost every Android device imaginable (kernels, device trees, vendor blobs, etc). So it is easy for someone to fork CM and add their own mods and make it their own (like AICP, RR, and Temasek) while keeping support for all of those devices and making a name for themselves. CM is technically AOSP mixed with CAF for all of those other devices but it is not needed on Nexus devices and ends up screwing some stuff up. What would be ideal is for ROMs to have a pure AOSP variant for the Nexus devices and an AOSP + CAF (CM) variant for all other devices. Dirty Unicorns is a prime example of this. It is more effort for the developers but it makes for a better user experience. Just my two cents.
Cvansetten said:
I have searched for literally months now, switching back and forth from stock to CM and this problem is absolutely maddening.
The bluetooth is garbage on CM. Constant stuttering. Anytime I unlock the phone, go to bluetooth settings, or even just leave the phone alone it skips horribly.
Is there any fix or resolution for this? I want the speed and features of CM, but this is ridiculous.
Click to expand...
Click to collapse
Hasn't anyone got this solution yet im using unofficial cm13 and doesn't turn on Bluetooth

Categories

Resources