Ive been trying to do alot of reading in learning the past week. i flashed my phone maybe 9 times already atleast. Now i keep reading abouts modem versions then kernels then roms. what are the difference? are they each upgradable on their own? Or do the roms upgrade them by themselves. Thanks in advance.
Some Roms upgrade through rom manager. But most of the time you have to flash the new version to get the update. Don't know much about kernals sorry but may somebody cam clearify for both of us
Sent from my phone exuse the typos(if any)
Put simply, the kernel is the part of the software that talks directly to the hardware, different modifications are included in kernels, such as lagfixes, the ability to overclock, and BLN (backlight notifications). Most of the custom Captivate kernels you see are in fact i9000 kernels that have been tweaked to work on our phones.
Once again put simply, a ROM is the operating system of your phone, it includes applications such as the Launcher, Phone, Contacts, Email, Calculator, Calendar, Market, etc. as well as any custom settings put in by the ROM maker (AKA chef) such as the sideloading of apps and root access. ROMs can be added onto later by the user such as the installation of themes or the removal of bloatware. Most of the recent ROMs are based on i9000 ROMs.
Modems are the software that talk to the cellular radio in your phone, they also seem to effect GPS performance. Modems are bit different from kernels and roms in that there aren't any custom modems. All the modems you see on the forums are from Samsung. Modems from several different Galaxy S variants work on the Captivate.
Most ROMs (and ROM updates) are prepackaged with a kernel and a modem, but all the parts can potentially be upgraded separately with the right knowledge. One thing to keep in mind is that to avoid issues you should not mix your parts. For example, in most cases if you use an i9000 modem with a captivate kernel you will not get any sound on phone calls.
The best thing to do before you flash anything is to read, read, read.
I'm a little confused as to which ROMs in the att subforum work on my g900a. I'm assuming everything under Android Development does since those are all touchwiz, but there are many more under unified ROMs, like cm12 that it's not really clear if it's compatible. They keep using the term klte, but I don't know what that means. Does anyone know? Thanks
Don't get me wrong I love the roms out for it now (I'm using Looper X) but is there like something about the phone that isn't allowing AOSP roms?
See thread: http://forum.xda-developers.com/galaxy-s6/help/exynos-custom-roms-t3043652
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
MrBrady said:
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
Click to expand...
Click to collapse
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
simms22 said:
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
Click to expand...
Click to collapse
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
MrBrady said:
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
Click to expand...
Click to collapse
well, first off, aosp and stock are two completely different roms. stock roms also have closed source code included, where aosp roms dont have that code included, so they WILL run differently, as two different roms should.
---------- Post added at 03:20 PM ---------- Previous post was at 02:58 PM ----------
anyways, the answer to your question is really simple.. better is whatever is better for you,personally. to you, image based roms are better. for me, aosp is better.
as a real answer of which is better doesnt exist, its all which is better for you(or me).
Had you followed the rules you would know threads like this don't stay open long.
There is no best. Or better. There is only what works for you.
Most people that get a nexus device do it for the active development. Which does mean some bugs here and there, but that is the fun. In learning, finding and killing bugs. If you got a nexus for any other reason you really are not doing yourself any favors.
I've tried 3 different Nougat roms and I have the same issues
1. The battery LED does not turn on while inside the ROM
2. The camera app crashes or reports that it can't connect to the camera, depending on the rom
3. The flashlight button doesn't do anything
I've tried XenonHD-181116-Official-m7, RR-N-v5.8.5-20171213-m7-Unofficial, and LineageOS.
A little bit more information that might be useful: I'm using an HTL22 HTC One J (AU). I got it unlocked/s-off using Sunshine just today. I have twrp-3.2.1-0-m7.img flashed to the recovery. I haven't tried any custom roms below 7.1 yet (I'll do that tomorrow likely if nothing gets figured out), though I did try 8.1 but that was completely broken, though I'm not going to complain about that because I know it is experimental.
So do any of these issues sound like things that have happened before? I tried looking for a pretty long while but I can't find anything on anyone else having these issues. Maybe I'm looking in the wrong places. Any help will be greatly appreciated. It might be worth mentioning that I'm only slightly experienced, so if there's an obvious mistake I've made then I may not have realized it.
Edit: So it looks like these things aren't working because the HTC One J is marginally different from the HTC One. Which sucks... since I don't think there is much support for it here, letalone it's one forum. Any suggestions on what I could do besides return to my stock backup would be much appreciated.
Edit 2 [Solution]: Turns out that I was flashing M7 roms to my HTL22 (I didn't realize the devices required different roms since the HTL22 is basically just the japanese variant of the M7). To anyone finding this post in the future, here's what I did. This dude I found on a Japanese forum who has ROMS & recoveries for the HTL22 (HTC One J), so I installed the latest version of Lineage he had and also the latest TWRP recovery he had, and everything works great now.
Here's the forum I found it from
And here is where I got my recovery & ROM. Anything labled m7wlj should work on the HTL22
After flashing the recovery & ROM, I also installed Magisk & OpenGapps (ARM, 7.1, nano). Enjoy.