OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
jcrompton said:
OK so I know everybody had different experiences but I thought I'd share mine and see what others are experiencing .....
Currently running Multirom
Primary -- Android N
Secondaries Tried -- Pure Nexus, Stock Lite, UberStock, and couple others
The N ROM is just a bit buggy and although there are apparently work arounds I can't get many apps to work. Fairly fluid but not "snappy".
Stock Lite has interestingly been the most steady but requires Cat mod to get the bare minimum Moss that I like.
Weirdly enough despite Pure Nexus being so popular, it and a few other AOSP builds have just not been as reliable. I just got a phone call on PN and the screen wouldn't come on until several power button pushes.
UberStock was snappy but it just irritates me to not have a text percentage battery.
The CM builds of various authors usually have their bugs.
Any thoughts? Or share experiences ..... Not necessarily of a specific ROM but more of thoughts Stock, vs AOSP, vs CM etc
Certainly don't want to insult any developers .... Their shared work is appreciated
Click to expand...
Click to collapse
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
sgloki77 said:
stock+xposed+gravity box and other modules? you don't really need custom roms anymore, having said that I prefer aosp, cm not even once
Click to expand...
Click to collapse
Do you ever have or feel like xposed slows things down .....? It's been a while since I've tried
simms22 said:
running pure nexus myself. generally, I like staying with aosp builds. but, user experience can be heavily effected by whatever the user installs or mods. like your power button issue, that can happen because of an app, a theme, or a mod. not because the ROM doesn't like it, but becauseany apps, themes, or mods are not made by professionals, but by amateurs.
stock, I usually am on for the first hour to a max of a couple days after getting a nexus. then its usually an aosp build. CM, or CM based ROMs I stay very far away from. I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Thanks
have all these modules working on pure nexus, snappy as usual
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
Since the introduction of Lollipop, I really haven't felt the need to flash a custom ROM.
Stock ROM has always worked great for me, I use root for a few things like Greenify and Xposed, but I stopped using those as well.
On my N6:
Stock ROM - Best so far. Sometimes I don't even use root. Excellent battery life, no bugs and great performance.
PureNexus - Great ROM, however the CMTE version was a bit buggy when I used it. No disrespect to the devs, they're doing an excellent job.
CyanogenMod - My second choice, always. Nightly builds are stable in most ways, I'm using one right now and it's working great with a custom theme and a few mods installed.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
simms22 said:
I used to be the biggest CM fanboy years ago, but CM is not the CM that used to be. now they are different, as are their goals.
Click to expand...
Click to collapse
Can you elaborate a bit on this?
Everything seems the same to me.
I got my Nexus last year. I ran several kind of custom roms. Most of them dont last longer then a few hours. The one i am using the most and always go back to is Lite Rom. It has everything that i need and is stable, good battery life and just works. Sometimes i feel like the builders just try to put too many things into the rom and it can be confusing. I like to keep it simple and clean.
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Strephon Alkhalikoi said:
@murtaza02: I'm not @simms22, but I can provide some insight here. Back before Android hit version 4, Cyanogenmod was "king of custom ROMs". They were on the cutting edge, with lots of features that simply weren't available in Google's stock Android. This was done not for money, but out of love of Android. A few years ago they incorporated and now offer a commercial alternative to Android. Afterward they pretty much stopped innovating, especially after the Focal fiasco.
Cyanogenmod strayed from its roots, looking to get paid money rather than respect.
Click to expand...
Click to collapse
Yes I recall during the time that this was going on there were several very heated discussions that took place here on XDA. The bottom line though 4 those of us not in the know basically I just noticed that cm ROMs definitely changed
Once they incorporated is when the innovation stopped, as that is when they changed focus away from what brought them to the attention of everyone in the Android community. Instead of making a "better" Android, they settled for simply making Android. The Focal fiasco cost them, in that they lost many of their freelance developers, and lost a lot of respect from the community at large.
To this day I don't put Cyanogenmod on my devices, because Cyanogenmod left the building a long time ago.
To be honest I stopped using CM and CM based roms years ago. While it has a little o do with their business model it was mostly due to the fact that there are bugs that have been around for years that were never fixed. Then they merge in code without testing it which has been known to cause huge issues.
I prefer roms built from AOSP which there are very few. I also never go for what is popular. To be honest to many people are sheep and follow the crowd. (yes even in android) I prefer to try some out and make up my own mind. And then I stick with it.
Honestly, I ditched Cyanogenmod because they stopped being innovative. It goes hand in hand with them incorporating, because the profit motive overrides everything else. Profit first, last, and always.
Related
Check this story. Looks like may for us.
Sorry about the sparse post but I'm on the move
http://www.androidcentral.com/list-bell-android-40-updates-appears-timelines-each-device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, roughly May-June . . . so most likely August.
ok. we might get a leak or something by the late april and cm9 people are gonna fix the camera and we're gonna keep not caring about the stock firmware release. fingers crossed.
Bateluer said:
So, roughly May-June . . . so most likely August.
Click to expand...
Click to collapse
Actually no. If you read the article carefully, you'd expect the opposite to be true. This roll out is for Bell devices, and the Bell ROMs will be based on the stock ROM which one would assume to come out first.
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
safir187 said:
ok. we might get a leak or something by the late april and cm9 people are gonna fix the camera and we're gonna keep not caring about the stock firmware release. fingers crossed.
Click to expand...
Click to collapse
Forget that. I'm looking forward to an Overcome ICS
CafeKampuchia said:
Forget that. I'm looking forward to an Overcome ICS
Click to expand...
Click to collapse
ok i will. i'm with you bro.
just any fully functional ics rom.
im estimating a november timeframe
Looks like we will end up waiting a while. Like usual with Samsung......
Sent from my GT-P7310 using XDA Premium HD app
I heard Samsung will make ICS available by Christmas 2013.
triften said:
I heard Samsung will make ICS available by Christmas 2013.
Click to expand...
Click to collapse
Now thats a realistic guess.
this is for i957 btw
I would expect the standard non carrier specific units to get it earlier, so April-May.
Im surprised there are no leaks though, maybe there just isnt the demand.
This was helpfull when determining when the official SGS2 ICS roms are available. I have been unable to find anyone doing this for the Tabs. I assume we have a CSC code.
http://androidforums.com/samsung-galaxy-s2-international/523455-ics-csc-you-eligible-update.html
wow just about everyone has gotten official ics now
acer released last week and now even the friggin sony tablet got ics!
samsung is the LAST of the big manufacturers to release. all because of the friggin touchwizz im guessing...
pseudoheld said:
wow just about everyone has gotten official ics now
acer released last week and now even the friggin sony tablet got ics!
samsung is the LAST of the big manufacturers to release. all because of the friggin touchwizz im guessing...
Click to expand...
Click to collapse
AFAIK, TouchWiz is working under ICS because they've upgraded the SGS2 and there've been some leaks for the Note. They're slackers.
Delays over updates in this day and age are unacceptable.
the galaxy tab 2 7" is out now, can it be helping the camera and other issues on ics?
Bateluer said:
AFAIK, TouchWiz is working under ICS because they've upgraded the SGS2 and there've been some leaks for the Note. They're slackers.
Delays over updates in this day and age are unacceptable.
Click to expand...
Click to collapse
TW for phones is VERY different to TW for tabs. Just because its working for the SGS2 it doesnt mean it is for the Tabs.
Each device is different, and requires a lot of work to be fully functional. Remember Samsung have many different devices to upgrade. Even with all the work Cyanogen have done its ROMs are still far from as slick or reliable as OEM ROMs on any device(IMHO) and the AOSP or AOKP ROMs aren't optimised that well either. They work, mostly , but are far from delivering the performance of an OEM ROM.
Its been said many times. Dont like skins like Sense or TW, dont buy an HTC or Samsung. If you still want the devices then have the patience to wait. If you hate them that much you should be using a Nexus and a Xoom.
rovex said:
TW for phones is VERY different to TW for tabs. Just because its working for the SGS2 it doesnt mean it is for the Tabs.
Each device is different, and requires a lot of work to be fully functional. Remember Samsung have many different devices to upgrade. Even with all the work Cyanogen have done its ROMs are still far from as slick or reliable as OEM ROMs on any device(IMHO) and the AOSP or AOKP ROMs aren't optimised that well either. They work, mostly , but are far from delivering the performance of an OEM ROM.
Click to expand...
Click to collapse
I guess "slick" and "reliable" when it comes to ROMs are debatable; I have always preferred custom ROMs on my Android devices (except my Nexus S). How you can say that they don't deliver the performance of an OEM ROM I can't really fathom, since everything I've seen demonstrates that they are capable of performing as well if not better than manufacturer-bloated ROMs.
You can overclock a custom ROM; that in and of itself is a pretty big performance enhancement.
Custom ROMs based on OEM base ROMs are definitely better, no question, but the ground-up ROMs like Cyanogen and AOSP or AOKP, no way, not a chance. There is usually something that doesnt work, some sort of lag, broken codec or missing feature.
Ive tried Cyanogen on numerous devices, there is always something that isnt right, always.
rovex said:
Custom ROMs based on OEM base ROMs are definitely better, no question, but the ground-up ROMs like Cyanogen and AOSP or AOKP, no way, not a chance. There is usually something that doesnt work, some sort of lag, broken codec or missing feature.
Ive tried Cyanogen on numerous devices, there is always something that isnt right, always.
Click to expand...
Click to collapse
It seems like your making a universal statement based solely on your own personal experiences. I have used CyanogenMod for years on various phones and it often worked very well with virtually no issues. In fact, on my EVO Shift there was no comparison; CM7 blew the Sense-addled OEM ROM out of the water.
Again you are missing the point. I dont like sense or TW either, but the ROM base is still vastly superior. That is why i use a non-TW Samsung base ROM based custom ROM on my SGS2.
hi guys i was just wondering if anyone could explain the benefits of Omni Rom?
I have switched continuously between stock and Omni, however i seem to always return to stock mainly because of the screen of death issue and blue screen issues that Omni has.
However, it would be nice to know what benefits Omni has and why i have that urge to always want to try Omni again!
Don't
PeterGeorgiou said:
hi guys i was just wondering if anyone could explain the benefits of Omni Rom?
I have switched continuously between stock and Omni, however i seem to always return to stock mainly because of the screen of death issue and blue screen issues that Omni has.
However, it would be nice to know what benefits Omni has and why i have that urge to always want to try Omni again!
Click to expand...
Click to collapse
As an advice, Do not use at all
I used for about a week, and i needed to open my mobile many times to unplug then replug the battery again to make my mobile come back to life, you will see many sudden restarts, and you will see many blue screens.
PeterGeorgiou said:
hi guys i was just wondering if anyone could explain the benefits of Omni Rom?
I have switched continuously between stock and Omni, however i seem to always return to stock mainly because of the screen of death issue and blue screen issues that Omni has.
However, it would be nice to know what benefits Omni has and why i have that urge to always want to try Omni again!
Click to expand...
Click to collapse
I think it is simply because either you love flashing and testing new things out or you love the simplicity and AOSP feel. I know I love it. Its also the fact that you've on the latest android version with is super "light" when compared to others. Its very snappy and can multitask like a bull compared to even the 4.3, and no massive themeing or bloatware. And not to forget the multitude of features and customizations you get with the ROM. I personally love the Active Display and I don't know how I lived without it. Anyway if you have the urge, like me, to switch between ROM, CWM backups are the best because setting up a ROM from the beginning is a pain. Another such person is moly82! He too flashes every release!
Ghaiooth said:
As an advice, Do not use at all
I used for about a week, and i needed to open my mobile many times to unplug then replug the battery again to make my mobile come back to life, you will see many sudden restarts, and you will see many blue screens.
Click to expand...
Click to collapse
Haha WHAT? That's the most ridiculous thing I've heard. Yes you do see blue screens, but mostly one per day. And even then the phone reboots in under a minute and is back to normal as if nothing happened. Please re-flash and re-evaluate.
!!!
Haha WHAT? That's the most ridiculous thing I've heard. Yes you do see blue screens, but mostly one per day. And even then the phone reboots in under a minute and is back to normal as if nothing happened. Please re-flash and re-evaluate.[/QUOTE]
Excuse me!!
Are you serious??
Is it OK for you to have reboots more than five times a day and this is only for the daily use??!! I did not even try demanding games.
And do you know anything about the need to remove your (non-removable) battery and re-plug it??
Please, if you think my opinion is ridiculous, then give that rom a try, and then give me your own opinion.
I wonder how can you consider your mobile reliable anymore if it will reboot even during playing the silliest and tiniest games ever there.
After all, this is my opinion which you may not agree with, but you are supposed to respect.
Ghaiooth said:
Excuse me!!
Are you serious??
Is it OK for you to have reboots more than five times a day and this is only for the daily use??!! I did not even try demanding games.
And do you know anything about the need to remove your (non-removable) battery and re-plug it??
Please, if you think my opinion is ridiculous, then give that rom a try, and then give me your own opinion.
I wonder how can you consider your mobile reliable anymore if it will reboot even during playing the silliest and tiniest games ever there.
After all, this is my opinion which you may not agree with, but you are supposed to respect.
Click to expand...
Click to collapse
Yes. You are certainly entitled to your opinion. Respect there. But not to mislead others, you just gave a very uniquely bad experience. Everyone else loves this ROM. I have been on it since the first week of its release. There are loads of other Omni users who will agree with me.
As for the battery removal, i cannot remove mine. Its an XT. Reboots do not occur five times a day, mostly twice! At least not for me. I listen to music constantly with JetAudio which is a heavy app, use Whatsapp all the time, browse with Chrome at least twice a day and many other things. I do not play games though... so I can't say anything about that.
Thank you for the concern guys but you still haven't answered my question what are the benefits of omni against stock???
PeterGeorgiou said:
hi guys i was just wondering if anyone could explain the benefits of Omni Rom?
I have switched continuously between stock and Omni, however i seem to always return to stock mainly because of the screen of death issue and blue screen issues that Omni has.
However, it would be nice to know what benefits Omni has and why i have that urge to always want to try Omni again!
Click to expand...
Click to collapse
Advantages: incredibly fast in relation with stock, immersive mode (love it), personalisation, great support, less 3G consumption, latest android version,boot in 27s, and the battery, this is my best, a lot of free RAM(400MB with 35 apps installed by me).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disadvantages: blue screen, normally one per day, camera is worse than in stock(a lot) ,low sound speaker.
Enviado desde mi Nexus 7 mediante Tapatalk
moliverac8 said:
Advantages: incredibly fast in relation with stock, immersive mode (love it), personalisation, great support, less 3G consumption, latest android version,boot in 27s, and the battery, this is my best, a lot of free RAM(400MB with 35 apps installed by me).
Disadvantages: blue screen, normally one per day, camera is worse than in stock(a lot) ,low sound speaker.
Click to expand...
Click to collapse
I have had Omnirom since first tilals build and it was amazing. Since 4.4.2 it becomes more unstable and I sometimes have had more than one reboot. Using my phone as drivers log I really can't use random reboots. The sound is very low, a workaround makes it loud and whistle.
Now I am an stock and yes, it isn't the stable it should be, but there seems to be an update shortly. But stock rom is also very fast, fast enough I guess. A benefit stock rom has is usb otg, a feature I need, too and don't have with OmniRom or Cyanogen Rom.
thedisturbedone said:
I think it is simply because either you love flashing and testing new things out or you love the simplicity and AOSP feel. I know I love it. Its also the fact that you've on the latest android version with is super "light" when compared to others. Its very snappy and can multitask like a bull compared to even the 4.3, and no massive themeing or bloatware. And not to forget the multitude of features and customizations you get with the ROM. I personally love the Active Display and I don't know how I lived without it. Anyway if you have the urge, like me, to switch between ROM, CWM backups are the best because setting up a ROM from the beginning is a pain. Another such person is moly82! He too flashes every release!
Haha WHAT? That's the most ridiculous thing I've heard. Yes you do see blue screens, but mostly one per day. And even then the phone reboots in under a minute and is back to normal as if nothing happened. Please re-flash and re-evaluate.
Click to expand...
Click to collapse
Not true. I got 3 to 5 blue screens a day on omni. A few times a day my Xperia got stuck on a black screen. For both i had to do a hard reboot (power + volume).
The battery was very bad to for me. It was empty in 10 to 12 hours with 2 hours screen time. With 4.3 i get a day with the same screen on time. Also the camera on stock is a lot better
As long as Sony haven't released the source it's not gonna get much better.
Don't get me wrong. I normally prefer aosp above a stock rom. But this time 4.3 is a lot better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
harowa said:
I have had Omnirom since first tilals build and it was amazing. Since 4.4.2 it becomes more unstable and I sometimes have had more than one reboot. Using my phone as drivers log I really can't use random reboots. The sound is very low, a workaround makes it loud and whistle.
Now I am an stock and yes, it isn't the stable it should be, but there seems to be an update shortly. But stock rom is also very fast, fast enough I guess. A benefit stock rom has is usb otg, a feature I need, too and don't have with OmniRom or Cyanogen Rom.
Click to expand...
Click to collapse
Yes,the OTG and the HDMI don't work,but that are features that not all the people use, this is the best of ROMs, you can choose your best option depending of your needs.
Did you try the nighlties with the new branches?
I have tested stock and Omni feels faster,in my opinion.
Enviado desde mi Nexus 7 mediante Tapatalk
moliverac8 said:
Yes,the OTG and the HDMI don't work,but that are features that not all the people use, this is the best of ROMs, you can choose your best option depending of your needs.
Did you try the nighlties with the new branches?
I have tested stock and Omni feels faster,in my opinion.
Click to expand...
Click to collapse
Yes I have tested some homebuilds and after the new branches comes back to the nightlies I also have flashed these builds.
You are right, OmniRom feels faster than stock rom but I can't use the random reboots. I need the drivers log and every reboot is a showstopper I really don't need. A rom should be fast, yes, but it must be stable at all.
I have to say, there is nothing I really miss with stock rom, on the contrary.
r-l said:
Not true. I got 3 to 5 blue screens a day on omni. A few times a day my Xperia got stuck on a black screen. For both i had to do a hard reboot (power + volume).
The battery was very bad to for me. It was empty in 10 to 12 hours with 2 hours screen time. With 4.3 i get a day with the same screen on time. Also the camera on stock is a lot better
As long as Sony haven't released the source it's not gonna get much better.
Don't get me wrong. I normally prefer aosp above a stock rom. But this time 4.3 is a lot better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I think there is no point in arguing about the blue screens because it must certainly depend on the amount usage and kind of usage. As for the battery life, I can get much better battery life.. about 2.5 hours screen time and can last overnight. It would be <14% though.
harowa said:
Yes I have tested some homebuilds and after the new branches comes back to the nightlies I also have flashed these builds.
You are right, OmniRom feels faster than stock rom but I can't use the random reboots. I need the drivers log and every reboot is a showstopper I really don't need. A rom should be fast, yes, but it must be stable at all.
I have to say, there is nothing I really miss with stock rom, on the contrary.
Click to expand...
Click to collapse
To conclude,when Sony release the new open source files and the developer use them I recommend you to use Omni, you won't regret.?
Enviado desde mi Nexus 7 mediante Tapatalk
moliverac8 said:
To conclude,when Sony release the new open source files and the developer use them I recommend you to use Omni, you won't regret.?
Click to expand...
Click to collapse
I will
if they will support usb otg
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Serial67 said:
I know that build a rom it's not that easy, and make it stable and fully working it's even harder. I also know that drivers and blobs are closed-source, so it's hard to make a device fully working.
But I wanna give some advice, because who want to mod his phone finds about 30/40 roms all unstable and full of bugs.
In my opinion, it's useless to release a rom if it isn't finished, wifi or bluetooth doesn't work, apps force-close, phone reboots randomly or maybe drinks the battery in 2 hours.
Lags in games, the home screen lags with 3/4 widgets. Maybe after a clean install the rom performs well but then you discover that it's not so good.
Let's not forget also that despite the roms are not finished, many times they aren't update any more to solve the bugs, or they are updated but the bugs remain.
I don't mean that ALL the roms have ALL the bugs, but each rom has at least two of those problems.
Some people may say that there are hardware limits to justify the bugs. Or maybe that the battery has to be changed. But those are only excuses considering that on three pages of roms, ONLY one performs well.
I have always been told “you have to change the battery”, or “the phone has got few ram” to justify the bugs. But why with the FluidRom gType (an Italian rom) I manage 24 hours with a normal usage (mobile data always on, wifi, background apps, little playing with games, several calls, facebook and whatsapp)? No lags in games, home and browser. So I assume that “change the battery” and “we have few ram” are only excuses.
If you release a rom only to show that you are able to develop something but then it’s full of bugs, stop. Don’t release it. Or release it when it performs really well.
The 4X it’s a 2012 flagship phone, but the roms are badly developed. So let’s not blame the hardware.
Some people may say “who forces you to change rom?” People try new roms because modders promise improvements.
Maybe this topic will be closed to restrict freedom of speech. But mine are only suggestions.
Click to expand...
Click to collapse
Haha, there are so many angles i can take on this.
I and the other 4x developers and users don't owe you ANYTHING, dont like our roms? dont use them, Simple. It amazes me some people are so entitled...
Go and make some Roms by yourself we'll see how good they would be .
For your information bringing roms to device in long chain of more people than just our devs
Sent from my LG-P880 using Tapatalk
Serial67 said:
I know that... TL;DR
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
ectoplasma22 said:
Wow ! Never thought I'd read something like this on the 4X forum !
You're so wrong. So so wrong !
Do you realize that when a dev releases a ROM he does this on his time and (most of the time) he doesn't expect anything in return.
Have you ever tried to build a ROM from source ? To compile ? To fix bugs ? To spend hours developing ? I really doubt since you don't realize what this is and the time it takes.
Moreover, our device is "special". The last official update we had was 4.1.2 and thanks to the dev you criticized we are now at 4.4.2 !!! I'm not sure you realized the work of these devs.
Also you say that we don't have any stable ROM but you're wrong ! For me, "stable" means that you can use the ROM daily and profit of all basic and important features of the ROM therefore there ARE stable ROMs ! Since I'm in charge of Beanstalk 4.4.2 I won't give any name but for having personally tried many customs ROMs I can say that we do have stable ROMs.
Everybody has its opinion but man... You're wrong and some devs may understand your post as an offence.
I hope you see what I'm trying to explain.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry ecto, we are talking about it in the italian forum where this kind of discussion began.. And we are composing it saying exactly what you're saying right here..hope that it'll stop as a great mistake, and to go on..
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
one word, ridiculous
We should change abit this letter and sent it to the LG dev-update department so they can ask @Demetris @laufer @adam @Ectoplasma @JoinTheRealms @SnXo (and many other talented and good people) for help next time they decide to push or even make any software for any LG phone.I know.this guyment to say official software not custom one so i am just correcting his type mistake.
Послато са LG-P880 уз помоћ Тапатока
whoa, easy there, mate...
First of all, I haven't seen an unstable ROM on our phones up till now. I am personally using CM (unofficial) and SlimKat as my daily drivers, and both are rock stable. The only bugs I have personally encountered are the camera (which is extremely hard to properly fix) and the broken reboot into recovery on Slim. And that's it.
All ROMs you find on xda are made for free, you don't need to pay anything, which means you also can't demand anything. Bringing a ROM to a device can take several hours (disregarding the time the pure download of the sourcecode takes), as every ROM needs its special treatment.
Furthermore, do you have any idea how long the pure compile process takes? On my new machine (which I upgraded for development only) needs ~75min for a clean build. Before that, my lappy was working over 8 hours for a clean build...
Saying we devs wouldn't maintain our ROMs isn't really nice, nor what XDA stands for. We do our best to provide you with the best/fully functional stuff, but there are things we can't fix/improve simply because we don't experience these issues. As an example, I am debugging my kernel ATM, and @FunkyRasta and I both run the kernel, however, FunkyRasta is experiencing lags, that I never experienced. So without his reports, I wouldn't even know about that until someone else might encounter it after the release.
@Serial67, nobody forces you to use "unstable" ROMs, but please don't just complain, but rather give some helpful feedback (logs) to help solve the issues. If you're not willing to provide such info (you don't have to), please don't complain.
Thread closed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Overview
OmniROM is pretty close to AOSP, as the 4.4.4 era comes to a close I've decided to post it.
This build has nothing to do with Nobe1976.
It is not his build on Droidrzr forums and was built by me, from source. Although it is likely the same (assuming configs for our device haven't changed much the past year)
Download
Feb/27/2015: OmniROM 4.4.4
KKBL only for now folks!!!
Source
Device
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960/tree/cm-11.0
Kernel
https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0
Vendor
https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-11.0
Yes JJBL people, I will build for you, but I need someone to test so OmniROM aside; IF JBBL people want these firmware I will need a tester :<
Just flashed this on my XT926 and the only issue ive had is when going into Settings>More>Mobile Networks>Carrier Settings The process com.android.phone force closes.
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
lol
Do you know about Lollipop? lol
Working really great on my XT925.. I love OmniRom.. Thanks @Tqr
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
kkruglov said:
nice rom, works fairly well on my razr m. feels lighter than cyanogenmod and other 4.4.x roms.
Click to expand...
Click to collapse
A lot of people use my MIUI or other fork builds but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Some compatibility takes a huge hit after I start chopping stuff to pieces so I just wanted to throw this up for people who are the opposite of the MIUI/Lewa/Whatever crowd and just want something as close to 'stock' android as possible.
Tqr said:
but don't really have the chance to use my source-builds which are almost always nearly 'perfect' (I don't usually post them)
Click to expand...
Click to collapse
why?
kkruglov said:
why?
Click to expand...
Click to collapse
It would annoy me if someone ported a ROM I had planned to work on using a base I built.
Tqr said:
The fact that this base appeared here means MIUI v6 comes soon
Edit: I'm NOT heading MIUI v6 I am only working as an assistant this is not my era to shine; with that being said if I can't get a JBBL volunteer It's not likely JBBL people will get MIUI v6
Click to expand...
Click to collapse
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
dulexetina said:
Looking forward to see MIUI v6! Loved MIUI even since my evo 3d. Hope it comes soon
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Me too but my build configs are currently not working correctly for some devices.
It's kind of problematic on my end at this point because the past two builds of (pretty much) AOSP have resulted in failure for some unknown reason; even with supported configs.
At the same time to bring a close-to-AOSP ROM to this firmware I had to make a lot of changes in source; changes which may have caused breakage upon building for some devices so I've had to revert everything for this specific build which will probably set the process back a day or two.
But I don't want to sound over-important; the person heading v6 could have(and has) done this fully on their own power without issue and I am really contributing nothing except for build related stuff which isn't even essential It's just to save them time because a lot of time was saved in my life during v5.
It's like they say, someone does something for you and you do something for them if you can; a capacity I'm kind of failing in right now because a lot of the devices I'd like to see get hit with v6 do not have proper source bases
Thanks, very smooth... can you add HDR feature?
ikromy said:
Thanks, very smooth... can you add HDR feature?
Click to expand...
Click to collapse
Maybe, I have to address JBBL right after I finished with the device I'm building for right now.
Like a true piece of scum I neglected the JBBL folks during v5 because I wasn't aware of the exacts surrounding it and frankly was too lazy/busy to produce it.
But from here out all of my builds will also accomodate JBBL now that I know how to deal with it.
I mean it's really like a friend of mine said; that it's better to release broken things at first because If you release something right the first time your topic won't have as many views and as much attention but I've always kind of been a black sheep with my preference for (nearly fully) functional first releases
Edit: I can do MIUIv5 for JBBL if people really still care about it but I'd rather focus on getting things ready for V6, and other projects I'm working on
It's really important that ANY errors with this code-base are brought to my attention , I really do not want to find out there is some inherent error in this when V6 is released It's really important that I do this right so I don't have to bother the developer of it to do yet another build on a rebase.
I feel like I've really annoyed people because I've had multiple peers/friends/co-workers/whatever download firmware that somehow 'wasn't right' this week
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Get lolly miui for mb886.
manuski said:
Do it. It's been awhile. And that miui phone overseas is killing em softly. I'm on jbbl now to start fresh but if you decide to put out v5 I'll try it. I am ecstatic about v6 to try out.. I will be trying the omni for now. I need a real stable ROM at the moment.
Click to expand...
Click to collapse
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
TecknoFreak said:
Get lolly miui for mb886.
Click to expand...
Click to collapse
It's being worked on as well, but 4.4 takes priority because it is literally almost finished.
Tqr said:
MIUI v6 is now nearly fully functioning on moto_msm8960 JBBL & KKBL, including V6 camera, scanner and all the other stuff you'd expect.
Unlike being a PatchROM build this is a direct adaptation from a Xiaomi device so there is a level of exclusivity here.
I really don't have the right to release this, It will be part of a friends multi-base thread; It'll show up at some point next month, hopefully.
I wanted to let people who are really anticipating being able to use V6 know that the codebase is finished; it does have all the features you'd expect on true stock MIUI that have never been ported (In this era):
- MIUI camera (Everything, including filters, panorama, fast&slow-motion recording mode...)
- MIUI Scanner (Everything)
- Nearly full native Xiaomi drivers (!)
- Everything, all features
Click to expand...
Click to collapse
This is great to hear man! Now I want to try it even more.Can't wait till next month...release it tomorrow MIUI 5 was great,simple and smart,just hope that v6 is gonna be same or even better.
Sent from my DROID RAZR HD using XDA Free mobile app
Honestly I straight up lied.
MIUI v6 boots with full function except RIL- Because of the nature of this work all builds have been kept closed. I will check with the head of development and ask if beta may begin.
If anyone here feels strong in development and can address RIL both the KKBL and JBBL can have this firmware in the very forseeable future. It's because we use some kind of fked up Generic RIL and I'm not sure where to play Xiaomis invasive code because It's so different.
I do not even know how this device handles RIL in the 4.4 era, if anyone has an understanding of this please be in touch.
With the recent influx of Oreo ROMs I was wondering just what people are using now and why?
I personally am still on AICP 12.1 Nougat, simply because I use my phone a lot and found it to be quite stable and very battery friendly.
But as a enthusiast I can't lose that itch that is telling me to finally upgrade my Mix to Oreo...
So, tell me about your experiences and why you made the choice you made.
MrColdbird said:
With the recent influx of Oreo ROMs I was wondering just what people are using now and why?
I personally am still on AICP 12.1 Nougat, simply because I use my phone a lot and found it to be quite stable and very battery friendly.
But as a enthusiast I can't lose that itch that is telling me to finally upgrade my Mix to Oreo...
So, tell me about your experiences and why you made the choice you made.
Click to expand...
Click to collapse
I was on Oreo builds but ended up returning to AOSiP Nougat. Been on it for 2 weeks, feels comfortable and stable and etc. First tried AICP 12.1 but a visual glitch occurred due to using RTL layout. Not even a single issue on AOSiP that I'd call it a deal breaker. Cheers.
Sent from my Xiaomi Mi Mix using XDA Labs
Konstantine34 said:
I was on Oreo builds but ended up returning to AOSiP Nougat. Been on it for 2 weeks, feels comfortable and stable and etc. First tried AICP 12.1 but a visual glitch occurred due to using RTL layout. Not even a single issue on AOSiP that I'd call it a deal breaker. Cheers.
Click to expand...
Click to collapse
What made you go back? Did you perceive any deal-breaking issues?
The only thing that really irks me on AICP 12.1 Nougat is that it (randomly) black screens on me after 2-3 days of continuous use.
My hopes are that with my next move I can finally leave that bug behind.
I obviously don't want to invite additional bugs however...
MrColdbird said:
What made you go back? Did you perceive any deal-breaking issues?
The only thing that really irks me on AICP 12.1 Nougat is that it (randomly) black screens on me after 2-3 days of continuous use.
My hopes are that with my next move I can finally leave that bug behind.
I obviously don't want to invite additional bugs however...
Click to expand...
Click to collapse
Sorry, missed the why part. On Oreo roms, there are issues like Mobile network stand-by drainage which is always draining more amperes than the rest(while using the mobile data connection). And the proximity issues, one has got an almost working proximity sensor but at the same time breaks the in-call sound when you switch between speaker-earphone and the other one has no proximity sensor which sometimes become irritating. One of these is becoming a deal breaker after sometime.
Beside, there is no black screen issue on AOSiP for two weeks of usage, but I was and am using Floppy kernel RC 1.2(Google toolchain one) for the whole time. Take a look at the Up time in the screenshot, there is not even a reboot or freeze. You may want to give it a go.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Xiaomi Mi Mix using XDA Labs
After taking the time and checking all (I kid you not) Oreo ROMs out there I have finally settled down on Pixel Experience for now.
It's less feature packed than the other ROMs (given it's pure AOSP focus) but as such it's the only one I've found without "broken" features, glitched settings menus, etc.
So far everything seems to work, sans the proximity sensor, which is more or less the same completeness of functionality my previous Nougat ROM had.
I was forced to rely on Magisk and Xposed to get my beloved Pie Controls back up and running however (as all app-based implementations out there suck so far).
I'll take my time with this ROM now and report back after a week or so of active use. That should give me enough time to test everything out properly.
MrColdbird said:
After taking the time and checking all (I kid you not) Oreo ROMs out there I have finally settled down on Pixel Experience for now.
It's less feature packed than the other ROMs (given it's pure AOSP focus) but as such it's the only one I've found without "broken" features, glitched settings menus, etc.
So far everything seems to work, sans the proximity sensor, which is more or less the same completeness of functionality my previous Nougat ROM had.
I was forced to rely on Magisk and Xposed to get my beloved Pie Controls back up and running however (as all app-based implementations out there suck so far).
I'll take my time with this ROM now and report back after a week or so of active use. That should give me enough time to test everything out properly.
Click to expand...
Click to collapse
It's been a week now and I've been pleasantly surprised except for two things:
Battery life isn't quite up to par to what I had on AICP, which is a shame because I've gotten so damn used to the thing lasting me three days.
Now I need to recharge every second day.
Still better than most smartphones but I know we can get more out of this and I'm looking forward to new builds of the ROM addressing this.
The second thing is mostly a personal thing and some people will be totally unaffected by this.
Namely, the lack of built in Pie Controls...
I've come to enjoy the huge screen estate that is the Mi Mix and I just hate wasting space with a navbar.
This is where Pie Controls usually step in, but with Pixel Experience I'm forced to "add those in" via a combination of Magisk and systemless Xposed + Gravity Box.
This ends up double irking me as I prefer to run ROMs clean instead of hacking them up to add things which in my opinion should have been part of the basic bundle.
And... I guess as a optional third issue: Yes, the proximity sensor doesn't work on it but... I'm not really missing it.
MrColdbird said:
It's been a week now and I've been pleasantly surprised except for two things:
Battery life isn't quite up to par to what I had on AICP, which is a shame because I've gotten so damn used to the thing lasting me three days.
Now I need to recharge every second day.
Still better than most smartphones but I know we can get more out of this and I'm looking forward to new builds of the ROM addressing this.
The second thing is mostly a personal thing and some people will be totally unaffected by this.
Namely, the lack of built in Pie Controls...
I've come to enjoy the huge screen estate that is the Mi Mix and I just hate wasting space with a navbar.
This is where Pie Controls usually step in, but with Pixel Experience I'm forced to "add those in" via a combination of Magisk and systemless Xposed + Gravity Box.
This ends up double irking me as I prefer to run ROMs clean instead of hacking them up to add things which in my opinion should have been part of the basic bundle.
And... I guess as a optional third issue: Yes, the proximity sensor doesn't work on it but... I'm not really missing it.
Click to expand...
Click to collapse
Thanks. I have been wanting to switch to Oreo myself but wasn't sure which one was a stable option. I am on Nougat RR and it's running flawlessly. Your review definitely helps. I will wait a little more before making a switch.
psychedelicNerd said:
Thanks. I have been wanting to switch to Oreo myself but wasn't sure which one was a stable option. I am on Nougat RR and it's running flawlessly. Your review definitely helps. I will wait a little more before making a switch.
Click to expand...
Click to collapse
I've found this ROM to be very pleasant to use, even now. I'm sure you'll enjoy it.
If I had to add anything to my previous summary it is that at times the phone will heat up quite a lot.
I haven't found out what triggers it yet and it's seemingly random and as such I can't guarantee that the blame actually lies with the ROM or an app of mine.
MrColdbird said:
I've found this ROM to be very pleasant to use, even now. I'm sure you'll enjoy it.
If I had to add anything to my previous summary it is that at times the phone will heat up quite a lot.
I haven't found out what triggers it yet and it's seemingly random and as such I can't guarantee that the blame actually lies with the ROM or an app of mine.
Click to expand...
Click to collapse
Maybe the current governor profile for your kernel is ineffective. See if you can put a custom kernel and then play around with the governor or CPU settings (if you are unsure on this, do not risk it)
I had a similar issue when I first started using RR. Someone pointed me to use the AKT Profiles apk and select one of the governors. My phone went from being toasty all times to a cool cucumber. Further updates to RR fixed the issue.
Hope this helps.
I’ve been running RR Oreo for months with no major issues. The general responsiveness seems faster than Nougat, though it's difficult to judge, and although the battery life appears to drop faster, I get the feeling that this is more to do with a change in the way the remaining battery life is measured rather than a higher drain rate i.e. nougat used to stay high longer then drop quickly when approaching empty, oreo seems to drop more evenly maybe even slowing down towards empty.
I'm looking forward to trying LOS when it comes of age, but for now, RR gets two thumbs up.
Slàinte
mmidders
I've come to the same conclusion about battery life in the new Oreo based ROMs.