Related
I recently rooted my phone. I wanted to install a custom rom. My friend installed cleankat v2.6 but i wanted to go for something better. As expected none of the nicer ones like cyanogenmod or paranoid android or aokp roms were available. I managed to install htc sense rom . it is working but has lots of bugs. As soon as i make a call it crashes and screen goes blank. Nothing opens .it doesnt even swit h off and i have to remove the battery every time i make a call and reboot it.
Secondly many apps including settings crash for no reason.
Plz. Help coz i really want dat rom working fine
[email protected] said:
I recently rooted my phone. I wanted to install a custom rom. My friend installed cleankat v2.6 but i wanted to go for something better. As expected none of the nicer ones like cyanogenmod or paranoid android or aokp roms were available. I managed to install htc sense rom . it is working but has lots of bugs. As soon as i make a call it crashes and screen goes blank. Nothing opens .it doesnt even swit h off and i have to remove the battery every time i make a call and reboot it.
Secondly many apps including settings crash for no reason.
Plz. Help coz i really want dat rom working fine
Click to expand...
Click to collapse
Hi Murali,
The nature of mobile development is such as you have mentioned above. It doesn't work like windows or linux etc where you can install a generic OS on any system configuration by any manufacturer. The firmware has to be specifically built for your device. It takes great skill to port inter-device especially inter-manufacturer ROMs, so the fact that you actually have a bootable and semi functional SENSE ROM for a non HTC device itself is a big achievement. But it will never function on your Micromax phone like it does on an actual HTC phone. There are too many dependencies to counter. Also, there is a lot of closed source code that is not freely available to developers, especially with overlays like Sense and TouchWiz.
I would suggest you look for a good Custom ROM built on your phone's official firmware or wait for support from CyanogenMod, PA, Slim or such series to offer support to your device.
Sorry for the bad news, but I hope it helps.
what ab
Will flashing a custom kernel help or change the compatibility of the rom?
[email protected] said:
Will flashing a custom kernel help or change the compatibility of the rom?
Click to expand...
Click to collapse
It might. Then again, it might not. Changing kernels can make a huge difference in performance, both in a good and a bad way. There are too many variables to contend with, and without a strong active community behind your device, any answer I give you will be just guesswork and not based on facts. You can always try out a couple of compatible kernels and test out the difference.
Sorry I can't be of more help.
Which ROM is right now the simplest and the fastest? I don't play any games, i want the most stable rom, where i can make calls, type messages, use internet browser, facebook, messenger and one app named "wykop". Is there anything?
Thank you!
Samsung S4 I9506
LineageOS is a very good ROM; comes with Android 7.1 Nougat, and supports all of your described needs. It is possibly the fastest, although it does not come with the play store, you will have to flash OpenGapps through recovery. In fact I'm using Lineage right now.
Hope you have good luck with it
MoKee is another good one
Just try it
@Aroko: The previous posters are simply throwing out ROMs without taking into account your specific needs. Based upon those needs, the most stable ROM for you would be stock Touchwiz. Now, you haven't specified whether you want the latest version of Android or not, but custom ROMs also come with custom compromises. For example, in some custom ROMs the camera crashes so badly that a reboot is required to fix it. It happened to me when I was using my I9505 as a daily driver, and the solution I had come up with was to use a third party camera app with its own camera binaries, because the ones included in the ROM didn't work.
The above is merely one example. If you're willing to deal with such annoyances, the Optimized Lineage OS ROM or Optimized AOSP ROM by JDCTeam may be a suitable choice. Otherwise, stick with stock.
I've been mucking around with Android for a while but basically stay with a ROM and what it comes packaged (or recommended) with.
Recently I've been looking around at Custom Kernels and I see they offer different options and functionality, but I lack some basic information:
I am guessing that the Kernel and ROM have to be compatible?
Is, for example a Kernel like Blu Spark or Lighting (all for OP5 and Nougat) compatible with all OP5 Nougat ROMs or is it ROM by ROM?
I looked over the pages for both Kernels and also for xXx Freedom OS and didn't see any information concerning compatible ROMs or compatible Kernels, is there any place/list that shows the compatibility of ROMs and Kernels?
Any information, or guidance to where I can find it would be appreciated.
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues. Besides that, if you made a decision to flash a Different kernel, along with their ROM, you're on your own.
Sorry for being off-topic.
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
lekiaM said:
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues.
Click to expand...
Click to collapse
@lekiaM You provided a great answer and thank you. I did notice that some developers (xXx NoLimits) provide the option to select various Kernel during the install. I pretty much expected that matching a Rom to Kernel was a crap shoot to certain degree. I am going to try a few out and see how it goes.
One final question, if a Kernel offers functionality that is not offered in the original Kernel, how do you go about taking advantage of the added functionality?
Will the Kernel add those selection to the settings or will I need a different app to access them? I was thinking in particular of the don't wake on plug/unplug. I utilized some ROMs (CM) that had this feature in the setting, I use Freedom OS now and don't see that in the setting, but I see that the Blu Spark Kernel offers access to that function.
Zombie said:
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
Click to expand...
Click to collapse
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
noncomjd said:
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
Click to expand...
Click to collapse
An aosp based rom will install and run like any other rom you decide to flash. It comes with the stock kernel built in
Each rom has their advantages and disadvantages. Currently Im running xXx 4.0 which is OOS based with extra features and then of course my own kernel for better performance and battery
@noncomjd Good question. And honestly I've been wondering that too (most of the time) i could gave you a simple answer on that, but i wont.
A Kernel can interfere with the ROMs behavior (for example manipulate the vibration, sounds, led light strength, button behavior and so on.) But a Kernel has their limits too and also the Kernel Dev in question. Besides that , i did saw some very strange things a Kernel Dev can do to manipulate a ROMs behavior. But i wont go further in that.
Answer to your question:
Yes. A good kernel dev can overwrite or add some tweaks in the ROM itself (you won't see it while flashing, but believe me after that, some things in settings are missing or added in the build.prop) . But as i earlier said it has their limits. A good Kernel Dev is aware of their capabilities. And they mostly play save. If a kernel Dev mentioned or added a feature or something in their changelog, than the feature is there. But to enable or disable that feature, you mostly need an 3rd party app(like a Kernel Manager) to activate or deactivate their added feature.
You need a kernel tweaking app in order to change kernel settings.
You can change those settings even if you run the stock kernel, but it won't offer as much features.
There are many kernel tweaking apps available and some kernels even provide their own apps.
Thanks all for some great information. Have a good base to set out exploring a little more.
If we want to run a rom he can't (directly) we have to wait untill someone made it specifically for us. Thats fine i got it very device have its own kernel and rom integration. But if a person is using the same exact tree as official one do then why it is difficult to run stock apps directly w/o proting them.
Is it because of some legacy or copyright problem. One can build a rom on its own w/o having a team(like los, rr, paranoid).
Why porting is necessary? I would like to know that too
Sent from my Moto G4 Plus using Tapatalk
Cause you dont have updates
I am not a code/programme guy,
But what i have learned is, these different ROMs (Stock, AOSP based, Lineage based) have 0 (zero) interchangeability to their stock apps (except common apps). These may be because they use different codes?
For example, lineageSU addon will work only on lineagebased ROMs. Moto apps will work only on stock.
This looks like this apps are coded in way that it run only for specific ROM/device,
If you want such apps you need to modify it..
About ROM,
There are 4 sources/trees, 1)vendor 2) device 3)ROM 4)kernel.
Vendor, kernel, device tree can be used same for any ROM,
but ROM source is different for each ROM, which defines what is base of that ROM. You cannot build stock based ROM, you can only debloat,deodex, and modify stock ROM...
So, on different ROM, you need to modify apps to run...
@DgnrtnX I recommend to read that article about blob's so you get a better understanding why there's so much effort needed to "port" apps for example: https://www.xda-developers.com/came...opers-make-hardware-work-without-source-code/
I'm on a ledge about installing a custom rom (Lineage 16 (or something else)), but I have some questions regarding custom ROMs, any answers are appreciated!
1. Will I be able to use apps that requires a non rooted phone? (I've installed a custom rom on my old phone, and it fails to pass safety net)
2. Will there be OTA updates? (I.e. security patches, bud fixes for that rom)
3. Will it be stable? (I've watched some videos and they say custom ROMs slows down the phone, and have random crashes)
4. Can custom ROMs enable project treble? (Not that it matters, just curious)
5. Are there any compromises with custom ROMs over stock rom? (Just any down sides of custom ROMs)
As a traveller, compatibility is very important, so will custom ROMs have any affect? I.e. booking flights, hotels, transfering stuff.
1) I tried Resurrection Remix, AOSPExtended and now I'm on ArrowOS, no problems with SafetyNet and I've been able to use my banking and payment apps
2) Depends on the ROM, but mostly yes, every ROM is regularly updated
3) I have never experienced a significant crash on a custom ROM, Even 9.0 ROMs are pretty stable as of now, ArrowOS feels much snappier than stock imho
4) Yup, some ROMs here have treble support. There's a guide by CosmicDan that explains how to enable Treble on our device
5) Pretty much everything about having your original firmware VS having a wider range of customization options. I don't think the latter is too risky, but if you don't like it you can always do a backup and go back to stock. Phones like Mi A1 are made for modding and are all about the user's freedom
BetaPix said:
1) I tried Resurrection Remix, AOSPExtended and now I'm on ArrowOS, no problems with SafetyNet and I've been able to use my banking and payment apps
2) Depends on the ROM, but mostly yes, every ROM is regularly updated
3) I have never experienced a significant crash on a custom ROM, Even 9.0 ROMs are pretty stable as of now, ArrowOS feels much snappier than stock imho
4) Yup, some ROMs here have treble support. There's a guide by CosmicDan that explains how to enable Treble on our device
5) Pretty much everything about having your original firmware VS having a wider range of customization options. I don't think the latter is too risky, but if you don't like it you can always do a backup and go back to stock. Phones like Mi A1 are made for modding and are all about the user's freedom
Click to expand...
Click to collapse
Thanks for the info mate! I bought the Mi A1 because it has a strong modding community.
I have a modding addiction and always want to try something new but with this phone I have to resist.
I ask myself when do I actually want, for me, I flashed my Samsung to get a pure android experience without bloatware, then I have to remind myself, I bought this phone because it is AndroidOne and the little bloatware is easily disabled, I'm actually very happy with the experience.
Next I have to ask myself, what will I gain from modding, and the truth is the only thing I really want is Gcam and honestly I don't really need it.
Sometimes it's hard to resist but I just keep reminding myself I already have all I want, for me I will stay 100% stock until after P when the device becomes unsupported.
kudos1uk said:
I have a modding addiction and always want to try something new but with this phone I have to resist.
I ask myself when do I actually want, for me, I flashed my Samsung to get a pure android experience without bloatware, then I have to remind myself, I bought this phone because it is AndroidOne and the little bloatware is easily disabled, I'm actually very happy with the experience.
Next I have to ask myself, what will I gain from modding, and the truth is the only thing I really want is Gcam and honestly I don't really need it.
Sometimes it's hard to resist but I just keep reminding myself I already have all I want, for me I will stay 100% stock until after P when the device becomes unsupported.
Click to expand...
Click to collapse
I have the exact same "addiction" and i came to the same conclusion: I've bought this phone because its "pure" android so i wont mess with it! Flash a custom of 9.0 just to tell my friends that i got it first? Stock will always be stock, and until the device become unsupported i will stick to it. Then, flashing custom roms will be a addiction again :fingers-crossed::fingers-crossed:
Sorry to be kinda off-topic on this but I'd like to ask a question regarding custom ROMs (Treble or not) regarding the Mi A1.
I've tried some of them, and usually what makes me get back to stock is the unlocking delay. There's always a delay when pressing the button and the screen turning on.
Have tried LOS15.1, 2-3 Treble ROMs (I think it's normal that it's like that on every one of the Treble ones if it's a vendor issue) and I think one of the Pie ones.
Am I doing something wrong or is this how it is supposed to be? Is there any Pie ROM that doesn't have that issue?
If there isn't, I don't think it's worth flashing a custom ROM. Untouched Stock with Gcam is pretty neat.
kudos1uk said:
I have a modding addiction and always want to try something new but with this phone I have to resist.
I ask myself when do I actually want, for me, I flashed my Samsung to get a pure android experience without bloatware, then I have to remind myself, I bought this phone because it is AndroidOne and the little bloatware is easily disabled, I'm actually very happy with the experience.
Next I have to ask myself, what will I gain from modding, and the truth is the only thing I really want is Gcam and honestly I don't really need it.
Sometimes it's hard to resist but I just keep reminding myself I already have all I want, for me I will stay 100% stock until after P when the device becomes unsupported.
Click to expand...
Click to collapse
Yeah, I've tried liquid remix 10.0.1, and I must say, sticking to stock is the best. Don't get me wrong, I really like custom roms, but after installing it, I realised that it's not even worth it. Plus, I don't really like to much customisation. You could say I'm more of an apple sheep. I'll probably switch to custom roms once this phone gets outdated. All the custom mods I need is root. For me, the best solution is to stock to the stock rom with root access.
Hi,
I face the same questions as WhatzIt2Ya, the brand new A1 is in front of me, currently empty and up to date with latest October update, and I ask myself what to do.
The phone will be my daily driver, so the encryption is mandatory. That's why I'm sad to see LineageOS Pie has some problems with it as of today. I run LineageOS on my parents' Nexus 5 and it rocks.
We have basically five possibilities:
1. Don't touch anything, keep the original ROM, the locked bootloader, OTA and so on. As long as the security patches arrive, why not. However, no TWRP and no root = no nandroid backups and no Titanium Backup, i.e. I'll lose lots of time in one year to backup the phone and configure it again when I'll take the custom ROM route, and I of course will to keep the phone updated.
2. Just unlock the bootloader. The phone will wipe itself, but that's not a problem, it's empty anyway. TWRP can be installed later to perform the nandroid backup.
3. Install TWRP and keep the stock ROM with root eventually. A fellow developer has figured out how to convert OTA to images installable with TWRP, so basically it's one OTA per month vs one TWRP install per month.
4. Install some custom ROM. Which one?
5. Treblize the phone. That's the future, but are the ROMs ready?
In 2018 Android is still behind Apple regarding backups. I have a work provided iPhone and all I need to do before getting mad is a simple iTunes backup. The phone can be restored in exactly the same state later, without my intervention. On Android I need to figure out how to backup things one by one (icons in folders, call history, SMS, all chats, etc., etc...) and to configure the new phone again.
And with root one loses the possibility to use some banking apps, so we add yet another trick to hide we are rooted. It's fun and rewarding, but takes too much time.
WhatzIt2Ya said:
I'm on a ledge about installing a custom rom (Lineage 16 (or something else)), but I have some questions regarding custom ROMs, any answers are appreciated!
1. Will I be able to use apps that requires a non rooted phone? (I've installed a custom rom on my old phone, and it fails to pass safety net)
2. Will there be OTA updates? (I.e. security patches, bud fixes for that rom)
3. Will it be stable? (I've watched some videos and they say custom ROMs slows down the phone, and have random crashes)
4. Can custom ROMs enable project treble? (Not that it matters, just curious)
5. Are there any compromises with custom ROMs over stock rom? (Just any down sides of custom ROMs)
As a traveller, compatibility is very important, so will custom ROMs have any affect? I.e. booking flights, hotels, transfering stuff.
Click to expand...
Click to collapse
Generally well regarded roms like Lineageos which are developed by 'good' developers will be more stable. Some volunteers who develop lineageos builds have a better track record than others. "Official" lineageos requires volunteers to pledge to follow a set of rules which include things like timely updates on major security patches, release updates for x number of months etc. Lineage is generally quite stable because volunteers are working off from a good platform. If you are extra worried about security, you might want to stick with stock because who really has the time to keep reading through the commits even if the code is open sourced?
Lineage has a built in root which will not pass safetynet so don't use it if you want to pass. Or use Magisk to root instead. But Magisk will need regular updates to pass safetynet and its a continuing cat and mouse game where google will fix safetynet and magisk will fail safetynet until the next update.....
Edit- I forgot to add that just unlocking the bootloader will cause safetynet to fail so every Lineageos phone would fail safetynet even if root was not enabled.
If you have to ask about treble, don't do it. Noobs have bricked their phones and there are threads that they have started crying for help.
Custom roms are all developed by volunteers and the level of testing is dodgy - who has time for that when they are working on it in their spare time? Occasionally there might be mistakes and phones will get bricked or lose wifi/BT functionality like one early version of a custom rom which wrote to parts of the firmware which should have been normally left untouched.