Related
So after seeing many things that is said with the DX I thought I should write a post like this. This is just to clear up confusion so users can have the knowledge to use in the future.
Every ROM for the DX is AOSP
I have seen this said many times and it bugs me that people think that all ROMs are AOSP. As of now, there are actually only a few AOSP ROMs for the DX, cvpcs' Tanzanite/Obsidian, Cobalt, and blackdroid's Ultimate Droid. Other ROMs like rubiX, Liberty, ApeX, and Fission are basically Motorola ROMs with the blur applications replaced with AOSP applications. Now this does not actually make it AOSP. It has features from AOSP, but there is much more to it than the applications. These blur-based ROMs actually have other AOSP-like features, such as lock screen music controls and a few others. Now that also doesn't make it AOSP, those are just a few features that were originally modifications to AOSP to add more functionality to a ROM. That doesn't mean these ROMs are bad in any way. They are actually very good. The only downfall of them is the fact that they are limited to what can be done.
There can't be AOSP ROMs without a custom kernel.
Another statement I have been told or have seen several times. It is considered AOSP if it comes from Google's source. A kernel won't affect the fact that it was built from source. Although it would be ideal for a custom kernel with AOSP, it isn't needed.
A custom kernel is needed.
This is another incorrect statement. It would be nice to replace the kernel, but it isn't needed. The kernel that is provided to us from Motorola includes basically everything the end user would need. Also there is overclocking(although it isn't the easiest implementation) by adding a temporary module to the kernel that is erased after the phone is powered off.
Gingerbread won't come to the DX until Motorola releases a new kernel with their Gingerbread update.
Incorrect. What the original concern was that Gingerbread would not boot with a .32 kernel(the kernel the DX has.) and that it needs a .35 kernel. This was later proven wrong with D1. The D1 has been running Gingerbread for a bit now with a .32 kernel. Now I know people will say it is is a different kernel or something along those lines, but that doesn't matter. Gingerbread will boot on it without needing to replace the current kernel.
this is something that should be posted on every forum about the DX. Great info
Would getting building GB on the DX give us the new garbage collector too? I'm so tired of waiting for memory to clear after PewPew (makes a TON of objects).
Trongable said:
Would getting building GB on the DX give us the new garbage collector too? I'm so tired of waiting for memory to clear after PewPew (makes a TON of objects).
Click to expand...
Click to collapse
Don't think GB would do anything different with it.
Moved and stuck. Thanks Matt! Please add info as it strikes you, this could be really helpful to the newer folks.
I feel like this info is either wrong or irrelevent.
I'm leaning towards irrelevent. Why don't we have Gingerbread yet if it's possible? I feel like you are saying technically we can have 2.3 w/ the X's current kernel, but it looks like realistically we will never see 2.3 until Moto steps up.
edit: I was mainly referring to your last point
sciulli999 said:
I feel like this info is either wrong or irrelevent.
I'm leaning towards irrelevent. Why don't we have Gingerbread yet if it's possible? I feel like you are saying technically we can have 2.3 w/ the X's current kernel, but it looks like realistically we will never see 2.3 until Moto steps up.
edit: I was mainly referring to your last point
Click to expand...
Click to collapse
First off, please don't bash on the devs that work so hard to give us new material for a phone that everyone expected to be impossible to do anything on...
2nd, gingerbread is possible, but you can't just take a release (even when possible) and dump it on a phone. It needs to be recompiled with the appropriate modifications to allow it to work on the X's hardware. Droid2169 is currently working on this, and has made some progress, he is working out usb drivers/connectivity I believe.
I understand waiting can be frustrating, but please don't bash on the devs who help us out.
thanks for the info
misconceptions
misconception?---do i really need to "deodex" my droid x before flashing a custom rom? i was under the impression that installing a custom rom would deodex the phone, and deodexing only has to be done manually before theming.
ernesttatum said:
misconception?---do i really need to "deodex" my droid x before flashing a custom rom? i was under the impression that installing a custom rom would deodex the phone, and deodexing only has to be done manually before theming.
Click to expand...
Click to collapse
Odexing is a process that optimizes the java code. most carrier roms are odexed. It is possible to de-odex a rom. also, if you build an aosp rom, it is not odexed, but can be if you wish.
you cannot apply a theme to an odexed rom.
Definitely something that applies to the rom, not the phone.
Sent from my Incredible using XDA Premium App
Your kernel statement seems wrong. If the current Moto ROM has kernel # 1.2, but the newest version of Google's AOSP rom is kernel #1.4, there is no way for us to update to the newest AOSP kernel. Sure we can update the apps and whatnot from the newest version, but strictly speaking without the same kernel it is not AOSP.
Also I dunno where you get the idea that everyone think all DX roms are AOSP. If it has any sort of blur, it's not and many roms do.
aldo37 said:
Your kernel statement seems wrong. If the current Moto ROM has kernel # 1.2, but the newest version of Google's AOSP rom is kernel #1.4, there is no way for us to update to the newest AOSP kernel. Sure we can update the apps and whatnot from the newest version, but strictly speaking without the same kernel it is not AOSP..
Click to expand...
Click to collapse
The best example of this is probably coming up soon. If Netflix's app require's DRM api calls that are only supported in the 2.3+ kernels then you are SOL if you can't mess with your kernel. You lose features and any kernel fixes/optimizations.
Does a custom Rom come with a Kernel?
My specific case :
Nexus 7 32Gb Wifi
Android 4.1.2
Rom : PA 2.54
Kernel : Franco 3.1.10
My plan is to update to PA 2.99Beta6 which is based on Android 4.2.
I'd like to know if I'll also need to flash a new kernel as part of the upgrade process or if the PA 2.99Rom also includes the required kernel.
My guess is that it will be included with the Rom but figured it wouldn't do any harm to ask.
PMSL, how on earth do you think a ROM would actually work otherwise without a kernel.
Sorry but.... #facepalm
Sent from my Nexus 7 using xda app-developers app
My fear was that a Rom might use or expect the stock kernel, cheers for the answer though.
With that in mind, I wonder why Roms don't tend to ship with custom kernels. Franco's seems to be widely preferred to stock.
Mr_Loon said:
My fear was that a Rom might use or expect the stock kernel, cheers for the answer though.
With that in mind, I wonder why Roms don't tend to ship with custom kernels. Franco's seems to be widely preferred to stock.
Click to expand...
Click to collapse
most roms that are actually developed ship with custom kernels(like cm for example). roms that are just compiled from aosp source that have some mods added usually use the default android kernel(or stock roms with added mods). also, many roms ship with other custom kernels included. anyways, many others prefer trinity kernel
Mr_Loon said:
My fear was that a Rom might use or expect the stock kernel, cheers for the answer though.
With that in mind, I wonder why Roms don't tend to ship with custom kernels. Franco's seems to be widely preferred to stock.
Click to expand...
Click to collapse
Sorry I may have picked up on your question wrong, but many developers, well in fact most would use custom kernels, some prefer stock, stock kernels are generally very stable but quite limited in what they can do, for example take the pretty amazing Siyah on Galaxy S3 which gives you the ability to dual boot different ROM, s, i had AOSP as my main ROM and a Samsung ROM as my secondary ROM which was great for a while but they novelty wore off for me as I really only used the AOSP ROM, not to mention over clocking , etc, etc, etc.
I use Trinity Seven kernel on the Nexus and i find that the tablet seems to charge faster than with the CM kernel that comes with Liquid Smooth ROM.
Hope that answers some of your questions anyway
Sent from my Nexus 7 using xda app-developers app
Hi all!
I recently got Nexus 4 and I'm getting back to the android scene now since my old Mytouch 4G days. I was an iphone user. So, Ive read lot of forums and did search up typical questions I have.
Firstly, is there a relatively good custom rom for availaboe for nexus 4 besides the Stock 4.2 that im using currently. Any opinions? I prefer better battery life, touch screen response, and overall smoothness, but dont want to compromise performance though. Also, is CWM more reliable custom recovery than TWRP?
Thanks!
Well first of all to get those "Custom Rom's" you need to Root (Jailbreak) your device.
Cyanogenmod 10.1 is pretty good for starters Rom wise. And before you do anything DO YOUR HOMEWORK! ... go on Youtube watch and learn how people Root, Flash Customs ROMS & Kernels (Overclocking, better Battery Life etc etc) before blindly doing anything.
What you are asking here is purely opinion. I prefer TWRP and others prefer CWM. I like Twrp because I can easily flash multiple files instead of flashing them all separately. Custom Rom I use is CyanogenMod. But again, that's all opinion. See, we have an AOSP device, so most roms will be very stable. Custom Roms are based on AOSP instead of Touchwiz or other skinned Android version. This means less hacking is required to get things working in custom roms. When a Samsung or HTC phone gets CyanogenMod or another AOSP based Rom, there are several hacks to get things working and even then, not everything works. You will find all Roms to be stable. I choose CM because they have great features, but don't go overboard. AOKP IMO is too much and most of it is useless to me. But, some people like having all the options AOKP brings.
I suggest trying things out! That's the best part of Android. Make a backup of your current setup in recovery and flash away! It's easy to restore what you had. It's nearly impossible to brick a Nexus and I recommend giving each Rom you try more than just an hour or two and really try it out. You made a great choice by getting a Nexus as your first Android after being away for a while. Take advantage of it!
risktaker84 said:
Well first of all to get those "Custom Rom's" you need to Root (Jailbreak) your device.
Cyanogenmod 10.1 is pretty good for starters Rom wise. And before you do anything DO YOUR HOMEWORK! ... go on Youtube watch and learn how people Root, Flash Customs ROMS & Kernels (Overclocking, better Battery Life etc etc) before blindly doing anything.
Click to expand...
Click to collapse
says the guy who bricked his n4 ...i kid :lol:
Try sr1 ROM,,that thing runs the smoothest out of all the ROMs out there. Which is crazy, as anything you'll try will be rather fast due to how responsive this device is. Pair that with Franco kernel and you'll have pretty great battery life as well.
Sent from my Nexus 4 using xda app-developers app
risktaker84 said:
Well first of all to get those "Custom Rom's" you need to Root (Jailbreak) your device.
Cyanogenmod 10.1 is pretty good for starters Rom wise. And before you do anything DO YOUR HOMEWORK! ... go on Youtube watch and learn how people Root, Flash Customs ROMS & Kernels (Overclocking, better Battery Life etc etc) before blindly doing anything.
Click to expand...
Click to collapse
Haha lol, Thank you my new friend for the advise ! I am currently reading a thread here on XDA on manually rooting and stuff. I am learning C programming so this should help me in learning =)! I prefer XDA thread guides over Youtube videos, which honestly have and are bad, in my opinion. I want to know exactly why this and what this even the minor details. Thanks for your input !
housry23 said:
What you are asking here is purely opinion. I prefer TWRP and others prefer CWM. I like Twrp because I can easily flash multiple files instead of flashing them all separately. Custom Rom I use is CyanogenMod. But again, that's all opinion. See, we have an AOSP device, so most roms will be very stable. Custom Roms are based on AOSP instead of Touchwiz or other skinned Android version. This means less hacking is required to get things working in custom roms. When a Samsung or HTC phone gets CyanogenMod or another AOSP based Rom, there are several hacks to get things working and even then, not everything works. You will find all Roms to be stable. I choose CM because they have great features, but don't go overboard. AOKP IMO is too much and most of it is useless to me. But, some people like having all the options AOKP brings.
I suggest trying things out! That's the best part of Android. Make a backup of your current setup in recovery and flash away! It's easy to restore what you had. It's nearly impossible to brick a Nexus and I recommend giving each Rom you try more than just an hour or two and really try it out. You made a great choice by getting a Nexus as your first Android after being away for a while. Take advantage of it!
Click to expand...
Click to collapse
Wonderful reply, thank you. I did use TWRP on my brothers Gnex, it did a soft brick, and had to revert to CWM when flashing CM on his phone, i dont know why it did. I did full wipe, and other wiping in recovery :S. For a noob like myself, I'm just afraid of bricking despite all the reading I do and know it well, in real world things do go wrong. As for Roms, I do understand what AOSP and AOKP mean, but don't know whats the difference in actual roms.
I won't have a lot of time with flashing roms my university opens soon, so I can give it a shot. CM 10.1 nightlies is a good start? Or Xylon? From my research, I leaning towards them and the MinCo + Franco.
Thank you for the warm welcome , I feel really happy and glad to be back to android again . This time there is no going back, I love penta band 3G phones and they only exist in android and windows. But, prefer android due to so much you can do now!
One last thing though, about the kernel, should I start with Franco one, or stick with stock for now?
air2k57 said:
Try sr1 ROM,,that thing runs the smoothest out of all the ROMs out there. Which is crazy, as anything you'll try will be rather fast due to how responsive this device is. Pair that with Franco kernel and you'll have pretty great battery life as well.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Aright , thank you friend ! I will start with sr1 Rom then and see how things go from there .
You must read a lot before start tweaking, xda is the biggest encyclopedia of all.
I highly recommend Paranoid Android, it's just super awesome!
hi all. just wondering what roms are stable and dds. im not new to flashing just new to the sg4. once rooting and flashing rom what functions might i lose that i should be aware of? just looking for a reason to froot and flash lol. thanks
Everyone has a different opinion, I prefer TW roms, I have used aosp roms for years, but rom of choice now is TW roms, Omega 7 is a complete error free rom.
Running CM10.1 Nightly builds. Been running very very well for almost two weeks now. Just today's build 7/5 seems possibly broken. Other than that very stable.
I previously ran Goldeneye. My favorite stock based ROM. Used it will CM10.1 was ironing out bugs.
http://forum.xda-developers.com/showthread.php?t=2349520 - CLOSED
http://forum.xda-developers.com/showthread.php?t=2346804 - CLOSED
as seen above, these types of threads tend to get shut down.
research and try. thats the best way to determine the best rom for YOU
cheers
Goldeneye 3.0 is great, i prefer touchjizz, is why
just the stock rooted ROM with Nottach's exposed mod.
What beerdroid said. But I'm running bean stalk with the marla kernel. But don't flash that on your device.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Im using the Google Edition ROM posted in this thread:
http://forum.xda-developers.com/showthread.php?t=2341376
I never use probably 95% of all the extra stuff Samsung puts on the GS4, and I love the clean pure operation of the GE ROM. Once you go pure android, it's really hard to ever go back. It is really amazing how much smoother and lag free the GE rom is.
But if you do prefer a TW rom, I would recommend Goldeneye, which is based on the latest Euro release.
Mint Jelly, TW based
I been wondering about that for a longer while. Every time I want to flash something I'm getting paranoid while reading the threads.
Which custom rom [or roms] is the best one for now and why exactly?
Is gcam quality on custom roms better?
I personally want upgrade it with predator kernel, but which benefits the most from the modifications and which is the most reliable comparing to stock?
jagth22 said:
I been wondering about that for a longer while. Every time I want to flash something I'm getting paranoid while reading the threads.
Which custom rom [or roms] is the best one for now and why exactly?
Is gcam quality on custom roms better?
I personally want upgrade it with predator kernel, but which benefits the most from the modifications and which is the most reliable comparing to stock?
Click to expand...
Click to collapse
Hi Jagth. If you only have one phone that you depend on for daily use, my suggestion is to stay stock until you have a second phone to experiment with. However, if you have a second phone, I would suggest you read some reviews, then pick a ROM and a kernel you think you would like, and experiment and have some fun.
You can continue flashing ROMs and kernels until you find something you really like, and then maybe you could stick with it for a while before you go again. However, if you only have one phone, then stay stock, because custom ROMs can be very unpredictable. Good luck!