Related
Well I want to start off by saying that I've rooted my N1 and tried several cooked roms including CM's and the Modaco version. I keep searching for a reason to use a custom rom. Every time I do, I end up reverting back to stock. I just don't get the purpose. I understand cooking Windows Mobile roms to get newer OS versions that included new features and stuff, and cooking in new updated apps... I've searched and searched looking for some solid reason to stay on a custom rom, but I can't find one.
The Nexus One is just awesome and pretty clean as it is out of the box. It seems like when I use a cooked rom, it's more bloated then stock and I "try" to make it work as my stock rom did, with same apps and homescreen setup (I like Launcher Pro/Dialer One). I know some of the roms include "newer kernels" which I'm guessing is like a newer build but I don't see anything really that "pops" out. I understand rooting the device to gain full access to the system. But you can root a stock rom.
I also understand porting different systems like Desire/Hero/whatever. But aside from cosmetics, rooting, overclocking, and undervolting... why use a custom roms?
And mods, I've searched and searched, and read and read, I've seen the stickies. I'm looking for specifics.
player911 said:
aside from cosmetics, rooting, overclocking, and undervolting... why use a custom roms?.
Click to expand...
Click to collapse
I think you summed it up pretty well. cosmetics, rooting, overclocking, and undervolting.
For me, custom roms is worth it JUST for trackball wake up, and unlock, on the nexus. I hated having to use the power button way at the top.
For some, its so you can use an entirely open source phone, free from proprietary google apps.
The great chefs put a ton of thought into all the additions they use, create, and implement. Things that save battery life, improve user experience, or fix bugs / quirks.
There isn't a huge demand for ROM's for the N1 because we're at the forefront of Android right now. We're the one's with 2.2. We have flash. Everyone else is getting ports of what we get stock. This will continue for the foreseeable future, until Google selects another handset to be its in-house testing model, or launches Nexus Two/Dev Phone 4 (counting N1 as 3). Once we're obsolete, then, and only then, will you see the modding community pick up and you'll see big reasons to go with custom ROM's.
CM has the latest android code that is publically availalble. (He just synced code today). The little features that are missing are enough for me. Things like invisible lock screen, to the newly added gestures in the music app(great for driving).
If you're not a tweaker by nature then stock OS code will suffice. Me? I can't get enough of the new little things that add up to an overall great package.
/cm nutriding
Because it's fun.
720p recording.
http://forum.xda-developers.com/showthread.php?t=698287
Titanium Backup and N1 Torch
ATnTdude said:
There isn't a huge demand for ROM's for the N1 because we're at the forefront of Android right now. We're the one's with 2.2. We have flash. Everyone else is getting ports of what we get stock. This will continue for the foreseeable future, until Google selects another handset to be its in-house testing model, or launches Nexus Two/Dev Phone 4 (counting N1 as 3). Once we're obsolete, then, and only then, will you see the modding community pick up and you'll see big reasons to go with custom ROM's.
Click to expand...
Click to collapse
Yea that makes sense.
I just feel that custom roms are more bloated then stock. I've been looking into trying one of the "Super Clean OC/UV Rooted" roms. But then again I think the stock OS is just the Bee's Knee's.
What is "bloated"?
There are zillions of reasons for custom ROMs, visual and functional:
Apps2SD
USB and WiFi tethering
Locales
OpenVPN
Dropbear, Bash, etc (better Linux experience)
Trackball colors, notifications
Torch (using flash LED as flashlight)
Deep system options made visible / changeable, lots of customization options
Most of Froyo features were implemented in custom ROMs way before Froyo test build.
My setup is VERY far from stock. And I use everything mentioned above. I can't even move to Froyo, because I need Apps2SD to work - overloaded with big apps.
I think that's a great reason..
player911 said:
Yea that makes sense.
I just feel that custom roms are more bloated then stock. I've been looking into trying one of the "Super Clean OC/UV Rooted" roms. But then again I think the stock OS is just the Bee's Knee's.
Click to expand...
Click to collapse
No reason why you can't use Cyanogen's Quick Root + Pershoot's OC/UV Kernel on FroYo to benefit from rcxquake's wonderful modded Flash .apk and watch Hulu. It's obviously not quite as complete as CM 5.0.x (desperately missing trackball wake), and despite having root for some reason I still can't rm -f and pm uninstall com.amazon.mp3.apk from adb shell, but it gets almost everything done for me. The main thing that made FroYo live-able for me was the addition of ogdobber's Black Bar, which I had gotten very used to on CM5. That said, I can't wait for a CM flavor of FroYo...
willverduzco said:
No reason why you can't use Cyanogen's Quick Root + Pershoot's OC/UV Kernel on FroYo to benefit from rcxquake's wonderful modded Flash .apk and watch Hulu. It's obviously not quite as complete as CM 5.0.x (desperately missing trackball wake), and despite having root for some reason I still can't rm -f and pm uninstall com.amazon.mp3.apk from adb shell, but it gets almost everything done for me. The main thing that made FroYo live-able for me was the addition of ogdobber's Black Bar, which I had gotten very used to on CM5. That said, I can't wait for a CM flavor of FroYo...
Click to expand...
Click to collapse
Have you tried "adb remount" to remount the System partition in read/write mode first?
I'm sure I'm setting myself up here, but what advantages are there to the custom ROMs at this point?
I'm running stock Froyo 2.2 (I did update the radio to 5.08, though), stock bootloader, and I'm not rooted. I'm on T-Mobile in the Tampa, FL area.
I'm not sure if it's a coincidence, or just because most people that are posting on XDA are running custom ROMs, but I don't really have ANY of the problems most people on here have. My battery life is great, and the phone is overall VERY stable. I've tried other launchers, themes, etc., but I always prefer the stability of the stock setup over aesthetics.
The few issues I have had I can attribute to poorly written apps (force closes, battery vampires), or known hardware problems (mediocre 3G connectivity at times, etc).
I can understand if you have a phone like the MyTouch that never got any official updates after 1.6, or you want to try the next leaked software on your phone. But the Nexus One has had tons of official support and updates up to this point. Before Froyo was officially released, I found myself better off with stock recovery to load the latest, greatest Froyo build.
Sorry for the rambling, but I would greatly appreciate any education I can get on what's packed into these custom ROMs that everyone gets so excited about.
THANKS!
Don't really feel like typing all the reasons haha, but there's a lot of stuff to enjoy with custom roms. If stock works for you that's great. I don't know anyone that's ever gone custom and wanted to go back but I'm sure it happens. End of the day it's whatever makes you happy. A lot of us want more than just a great experience, we want to see what's possible. You can view the changelog for the latest Cyanogenmod(most popular custom ROM) build here http://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
2. Removing the stock apps from the phone that you don't use or want. Why have them sitting there taking up space and potentially resources for no reason? Sure they don't take up much in terms of storage space, but if you use a lot of apps, every little bit counts.
3. Undervolting and over/underclocking. Get that extra little performance boost, or cut it back. When I was UV'd to 800mV and UC'd to 806mhz, I noticed no performance difference or problems (note: I don't play 3d games on my phone) and my battery life was insane. 24 hours of normal use would put me to 65% give or take.
4. Relating to number one, more control over other things. I've ripped stock, but customized, apps from random ROMs and pushed them to my phone. Black Facebook & Twitter widgets (white ones are ugly), darkened (black & dark grey) stock messaging interface with white text, etc.
5. Trackball Alert Pro.
I'm sure that others can add more, but the above are the main reasons I rooted mine.
A tiny little thing called Apps2SD+, for example.
Multiple audio/video decoder support.
Lots of Linux binaries bundled.
Lots of modifications to stock software (contacts, browser) that increase their usefulness (for example, do you really like to type "about:debug" each time you want to change browser client after reboot?).
etc etc.
Thanks for all the great info.
The underclocking sounds interesting. I don't play any games on my phone, and extra battery life is always nice.
I'm not too interested in customizing the appearance too much. Coming from an iPhone, I'm pretty happy with the looks of the stock Froyo UI compared to that.
Again, thanks for the time you guys took to give me some information. I greatly appreciate it!
Sent from my Nexus One using XDA App
Ryjabo said:
1. More control over the appearance of the OS. Get rid of that ugly white notification bar and replace it with a sexy black one, for example.
...
5. Trackball Alert Pro.
Click to expand...
Click to collapse
This was reason #1 and 2, 3, 4, 5, 6, 7 for me, respectively
Track ball skip song.. Enough said.
If I install a custom ROM, when a new one comes out, do I have to install the ROM from the start and I loose my setings etc. or do I just update it?
Depends on the ROM maker. Most make their ROMs backwards-compatible, so you can upgrade. Going between different makers' ROMs you mostly need to wipe and start fresh (though there are apps that can back up and restore pretty much everything).
I am thinking to try Cyanogenmod ROM, bot I don't wan't to cofigurate all the things when a new ROM comes out.
I have searched for this sort of thread for a while. Though I've only been changing my phone around for a couple months(Rooted & ROM changes) It's clear that every developer/group feels there's is best. While I find that different ROMs have great features, it would appear that each and every one has it's flaws. I also find that a person can literally search for hours on how to install, manipulate, customize and BRICK a phone. As a "Senior Member" I still find myself lost. Due to recommendations, I've purchased more then my share of "helpful apps". I hope that the most "Senior Members" (w/ extreme, non bias, knowledge) can help remedy a few staples for all users.
A comparative, most stable and complete ROM list per phone (updated frequently)
What do I really need? I don't know. I have purchased Root Manager, Root explorer, Rom manager, Titanium Backup, Drop Box the list goes on. To date I'm not 90% sure what any of these do, nor how they work. Ex. I've backed up my ROMs with Titanium Backup but I've also backed them up with Rom manager. I've changed ROMs and couldn't figure out how to reinstall apps, settings etc. using either one of these. You can find yourself changing a ROM and taking 2 - 3 hr's reinstalling apps, themes and settings.
Kernels! there 30 times as many of these as there are ROMs. There should be some real understanding of these. It would appear that some kernels will change the look of the ROM or is it the theme, it changes? Neither? so why do I need them, what really are there function?
There are some brilliant minds at work here. Hopefully some of them can pitch in and offer answers to some basic "need to knows" for many.
Thank you all for the work that you do
I'm definitely an enormous Noob (capital N!) but by now I can flash ROMs fairly quickly and reinstall my apps in a few seconds with TiBu. I still do agree with you that it's a bit hard to take in *everything*. Something I've been wondering since I began flashing (ROMs, not anything indecent) is:
1. KERNELS. What the hell is their function exactly? I know their compatibility with the custom ROM depends on...which Captivate model the ROM is based on, I think. But how does one know or how can one tell which is compatible to which?
2. Modem. ?! How do I flash this? Why do I need to flash this?
3. Probably O/T but what the heck is ROM Kitchen?
4. What is the other way of flashing without using ODIN?
Knowing that would set me a little further from Noobers State, at least.
Lancered said:
I'm definitely an enormous Noob (capital N!) but by now I can flash ROMs fairly quickly and reinstall my apps in a few seconds with TiBu. I still do agree with you that it's a bit hard to take in *everything*. Something I've been wondering since I began flashing (ROMs, not anything indecent) is:
1. KERNELS. What the hell is their function exactly? I know their compatibility with the custom ROM depends on...which Captivate model the ROM is based on, I think. But how does one know or how can one tell which is compatible to which?
2. Modem. ?! How do I flash this? Why do I need to flash this?
3. Probably O/T but what the heck is ROM Kitchen?
4. What is the other way of flashing without using ODIN?
Knowing that would set me a little further from Noobers State, at least.
Click to expand...
Click to collapse
I'm not an expert but this is my understanding.
1. Kernel: Set of controls that lets the software interact with the hardware of the phone. Typically affects GPS, battery, bluetooth, wifi, display, etc.
2. Modem: How your phone connects to and transmits voice/data/everything.
3. ROM kitchen is a tool to help build ROM.
4. You can flash new ROMs through ClockWorkMod Recovery. You choose to install new software from zip on sd card. It lets you install ROMs, Kernels, & modems, provided they have been setup to work with CWM.
Hope that helps answer some things.
Lancered said:
I'm definitely an enormous Noob (capital N!) but by now I can flash ROMs fairly quickly and reinstall my apps in a few seconds with TiBu. I still do agree with you that it's a bit hard to take in *everything*. Something I've been wondering since I began flashing (ROMs, not anything indecent) is:
1. KERNELS. What the hell is their function exactly? I know their compatibility with the custom ROM depends on...which Captivate model the ROM is based on, I think. But how does one know or how can one tell which is compatible to which?
2. Modem. ?! How do I flash this? Why do I need to flash this?
3. Probably O/T but what the heck is ROM Kitchen?
4. What is the other way of flashing without using ODIN?
Knowing that would set me a little further from Noobers State, at least.
Click to expand...
Click to collapse
Three more excellent questions, all of which for nubies and Seniors (without tech understanding) need to know.
trekie86 said:
1. Kernel: Set of controls that lets the software interact with the hardware of the phone. Typically affects GPS, battery, bluetooth, wifi, display, etc.
2. Modem: How your phone connects to and transmits voice/data/everything.
Click to expand...
Click to collapse
Good info but it doesn't help explain why there are so many of each. How is one to know what should be installed.
Different kernels allocate the phones resources in different ways.
For example sucker punch Or paragon allows the user to over clock the processor, as well as under volt. Both can be used to speed the phone up or reduce battery use.
Harcore speed mode tweaks brigtness settings, uses some tweaks to improve performance, and changes default from 250hz to 500hz
I guess it is like saying different kernels are like tuning your car up in different ways with different performance goals.
Modems performance appear to vary based off of your location. Only way to know what is best is to try them.
I do understand many are new to this (even I was new at some point of time). But there is one thing I would like to bring up in this thread.
A simple Google search would tell what the basic functionality of a kernel is. Likewise for most of things asked here.
Be patient, there are lots of people here who would guide/help u. Don't sound impatient nor show ur frustration here. This is a forum created by enthusiastic users, not by employees who are paid to service people.
1. Kernel:
Kernel is the heart of the system that keeps the phone running. U can consider the core machine level interacting portion of OS that translates all instructions to a format that the CPU can understand.It has complete control over everything that occurs in the system. The kernel provides basic services for all other parts of the operating system, typically including memory management, process management, file management and I/O (input/output) management.
Every kernel thread here has an OP where it tells what version it is based off, its features, etc.
Best way to know which is best for u: try it out. What's good for me may not be good for u.
2. Modem:
How do I flash this? : Modem thread is a sticky on development forum, and has details how to flash too.
Why do I need to flash this?: This is the core component needed to access the phone spectrum/signals.
3. Probably O/T but what the heck is ROM Kitchen?: OP says it all. This is one place where u can create a ROM by picking features/apps of the provided list. More for creating ur own custom ROM.
4. What is the other way of flashing without using ODIN? Check the first sticky thread in QA section "FOR NEW CAPTIVATE USERS - READ HERE FIRST - FAQs | HELPFUL LINKS"
So here's my .02 cents coming from a software engineer perceptive...
The kernel... It's the core/kernel of an operating system. It's main functions (as stated above) are to interact with the hardware a.k.a. Device Drivers, to manage resources (things like memory management and processor time sharing a.k.a. multi-tasking), service interrupt requests, network services and the like. It also provides a System Call Interface (API) to the user space (apps running on the machine) so the apps can use system resources.
Now the why so many part... First of all in general there are MANY options available when compiling (building) the kernel. Things like CPU schedulers, file system support, system type support (in the captivates case ARM), etc. etc. etc. So there are many different ways to configure the kernel and that gives many options to "test" and see which might work better or not. Some of them are dead giveaways like compiling the kernel for MIPS and trying to run it on the captivate won't work but some are "tweaks" that may help a little or a lot, like CPU management options.
Second part of the why so many is the code. Again as mentioned above things like changing code to make the colors of the display more or less sharp (display device driver), make the file system faster (voodoo lag fix) or overclocking the processor, and different "modem" tweaks are all "enhancements" that people have made to the original Linux kernel source. So those things "creep" into existence over time, since there are many people working on them, and you see different versions of the Kernel from that as well.
Anyone that plays music can relate to the options available in that there are only 12 notes on a guitar fret board but millions (or more) ways to put them together to play music. There are certain things that have to be present in the Kernel (notes) but writing code to enhance them and/or combining options at compile time is much broader (music).
ROM. Well IMO this one has a bad nomenclature. ROM is actually Random Access Memory and we flash an image to the "ROM" (which it really isn't but I'll leave that one alone). The "ROM" in this case is the operating system (a version of embedded Linux), which is the basic software needed to run and admin the phone, things like the Kernel, bootloader, device drivers, and file system plus any user apps like the phone dialer, launcher, etc. that are included in the ROM. As you can imagine the possibilities of customization are almost endless when it comes to the ROM. Different kernels, different drivers, different apps and many combinations of those. Thus we see all the different "ROM"s for the captivate with all the different options and unfortunately problems as well.
The modem is actually part of the kernel. It's the device driver for the phone hardware of the captivate. Being that it's part of the kernel it "works with" other code that's elsewhere in the kernel and ROM that is "tweaked" for a particular phone in this case. So when you see "use an i9000 modem with an i9000 kernel" it's because the code in the modem is written to work with the other code in the kernel. It doesn't necessarily mean it will brick the phone and/or not work but it quite often means it won't work the best if it's not "matched".
An example of the why so many here might be (and I'm just using this as a random example not a real world example) in the code below (which is the Samsung modem code in the SuckerPunch source in this case) notice the comment there about "no spec" and having to confirm how much time is needed to initialize. That may be an example where someone could play with those timings and get better performance out of the modem...
static void msm_reset(struct modemctl *mc)
{
<sniped code for briefness here>
gpio_set_value(mc->gpio_cp_reset, 0);
msleep(500); /* no spec, confirm later exactly how much time
needed to initialize CP with RESET_PMU_N */
gpio_set_value(mc->gpio_cp_reset, 1);
msleep(40); /* > 37.2 + 2 msec */
gpio_set_value(mc->gpio_phone_on, 0);
gpio_set_value(mc->gpio_cp_reset, 0);
}
So that's one example of how you might get another modem version if someone played with that code and saw better performance.
I don't know if that all helps or muddies the water, but again it's just an old software engineer's .02 cents.
mxracer101 said:
So here's my .02 cents coming from a software engineer perceptive...
<..............>
I don't know if that all helps or muddies the water, but again it's just an old software engineer's .02 cents.
Click to expand...
Click to collapse
good work!
I do understand many are new to this (even I was new at some point of time). But there is one thing I would like to bring up in this thread.
A simple Google search would tell what the basic functionality of a kernel is. Likewise for most of things asked here.
Click to expand...
Click to collapse
For those seeking help, looking on XDA this is the #1 source for this information. Most other forums refer to XDA. So you should be in good hands
Be patient, there are lots of people here who would guide/help u. Don't sound impatient nor show ur frustration here. This is a forum created by enthusiastic users, not by employees who are paid to service people.
Click to expand...
Click to collapse
MOST crucial to understand this. PLEASE don't re-ask a question in several different locations. In most cases a question will be answered in a short time.
1. Kernel:
Kernel is the heart of the system that keeps the phone running. U can consider the core machine level interacting portion of OS that translates all instructions to a format that the CPU can understand.It has complete control over everything that occurs in the system. The kernel provides basic services for all other parts of the operating system, typically including memory management, process management, file management and I/O (input/output) management.
Every kernel thread here has an OP where it tells what version it is based off, its features, etc.
Best way to know which is best for u: try it out. What's good for me may not be good for u.
Click to expand...
Click to collapse
This is an area I see more questions about, then I do ROMs. Be awre that all ROMs have built in kernels, it's a good idea to let the intended kernel do it's thing. This is a fine tweaking operation, learn what one does for each ROM. Don't feel you need to change it, because it's being talked about in a ROM post.
HTML:
2. Modem:
How do I flash this? : Modem thread is a sticky on development forum, and has details how to flash too. Why do I need to flash this?: This is the core component needed to access the phone spectrum/signals.
^^^^SEE ABOVE^^^^ Dito
kernels; the function has been explained so i wont go there. there are kernel settings that cant be changed once compiled that effect performance and battery life, often making one better hurts the other, kernel hz will affect the snappiness, some kernel devs like to put out 2 or more versions depending on the users preference. also there have been many mods made for the i9000, i9000 devs typically dont make ports for the other phones so the code is made available for other devs to include in there own kernels. part of the reason for soo many is that things are constantly developing but some people like what has been out there for a while. there are also a number of compiling tweeks that one developer or another may prefer.
some kernels have stock recovery 2e or 3e, some have cwm recovery some have steam recovery, some have a modded cwm recovery. cwm recovery and steam give you access to the rom backups (nandroid) and some other features, steam has a touch screen interface but the modded cwm versions have similar functionality with a hardware button interface.
lagfixes; lagfixes are incorporated into the kernel. some have "voodoo" which is ext4 and is like what non samsung android phones often have. voodoo only has a couple options and most run it default. voodoo lagfix options may be incorporated into the recovery or handeled by the presence of a folder/text file in the voodoo folder.
there is also ulf (universal lagfix/ultimate lagfix). ulf lets you choose between jfs, ext4, ext3, ext2 and rfs file systems on each partition. it also lets you do the earlier ext2 loopback like one click lag fix. it is total overkill with options an the benifits of each is subject to opinions and anecdotal observation. but if yo specifically want jfs it is the only option available on the captivate right now.
wifi; different wifi drivers cause problems with certain routers because of a security measure. once a couple fixes for this were found new kernels appeared.
other "voodoo" features; supercerio is the developer of voodoo and is obviously a talented dev. he has created a color/brightness/sharpness fix for the galaxy s line but the port to captivate kernels took some time to come about. some kernels have it and some don't. there is also voodoo sound which lets you change the amp output for the headphones.
overclock/undervolt; there was at one time development on this for captivate kernels in 2.1. it was stable but a lack of captivate froyo source kinda killed it. also there was no interface for it, changing settings was done on in a text file that you had to write into a folder with a script, people had trouble understanding it. many kernels now are i9000 ports but the undervolt code often causes "charge death" some prefer not to overclock do to this instability, but then glitterballs came up with a fix. glitterballs prefers the overclock settings to be "mild" they really arent in reference to a pc though, 20-28% is significant but still there are others that make 30-60% overclocks available. the overclock setting on some of these kernels is a multi stage setup and isnt that user friendly involving an app and configuration files. there are also sceduler differences that can balence battery life and speed but i think samsungs settings are just fine
basically if you want overclock i recomend glitterballs work. if youre phone handle 1300+mhz you must go elsewhere if you "need" the max your phone can handle.
if you dont care for overclock there are many other things to look at. kernel hz set at 500 is snappy but you may prefer battery life and find one set at stock or 300hz
if color sound is important to you and thats a big reason to by a galaxy s then you want voodoo color and sound. im not gonna talk about files systems and lagfixes because despite the apparent differences in quadrant the every day results are up for debate.
modems; im not gonna tell you to match modem to kernel because i never found that to be true.. what i will tell you is that if you use bluetooth and "need" hsupa(over rated) then dont choose a north american captivate rom other than the armani based roms. there are 5 poular ones for non captivates phones and many more that work as well, choose at random for all i care, the biggest factor is gps performance and none of them do poorly, i recomend jl3 but kp1 can work better with some playing around, it seems to not give a stable position because it constantly updates stalites, the list is constantly changing in lbs test mode but it does get more satalites in my experience. others are jk3/4 and jl2(different phone that jl3) some say in there area jl2 gets better transfers but i dont find that to be true here.
ported roms; i9000/m and t959/d ports are great and at this time dont give up too much, they work with canadian t959d and i9000m modems as well as many other oversees modems that have the att 850 band . but on some, not all but some ports you may experience sleep death. it's a captivate issue and captivate roms since jf7 have a fix incorperated, i have mostly good results on the ported roms but 1 or 2 have given me sleep death.
captivate roms; work great! use as is or add a kernel with x,yand z features. with a captivate rom you give up either bluetooth or hsupa but hsupa is over rated on a phone unless you tether or upload files directly from your phone, it does help snappiness loading web pages but seriously my isp gives me 30% the upload bandwidth that i get with hsupa and i only see about 50% of the hspa potential in my area. my 3g connection gives me 300kbps and my isp gives me 600kbps. i think non hsupa is fast enough most of the time.
to the op, titanium backup does a backup of your apk's and data for those apps. it is not recomended to restore all system data if a new rom has a different base rom. this is what to use to restore apps after a flash, chose the restore apps and data setting, if you have problems factory reset and restore apps only.
cwm backs up the rom. it is a fall back incase a flash fails. you need cwm recovery either in the kernel or in an "update.zip" in the root of the internal sdcard. if you have 2e recovery or modded 3e recovery in the kernel you need to reinstall packages to get there from the update.zip. you may need to try twice. you navigate with the volume and select with the power button.
if you have a stock 3e recovery (rare now that there are altenatives, unless you flashed a stock leak or rogers rom as is) it will fail, you will need to odin/heimdal/neldar sgskernel flasher app flash another kernel to reach cwm recovery.
root explorer helps you reach the system files. if you think you need it then get it but it is really most useful for making tweeks or installing themes, some of that is better done in a script via update.zip or remotely via adb so you may not want or need it.
Asking what ROM is best is like asking which midsized car priced in the mid $20k's is the best. They are all pretty close in quality and only differ so much, according to what the dev felt was pertinent to them. Look them over and see what people have to say about them and try it out. If you don't like it, flash another one. It really is that easy. As some of posted in other threads, it's fairly hard to totally brick your phone unless you have absolutely no clue what you're doing. It took me months to get to the point where I felt comfortable flashing and it scared the **** out of me to finally take the plunge. Now that i've done it, i'd have no problem doing it again when/if I find another ROM I like better than the one i'm on.
The absolutely best info I got was from this thread. I have no idea why it's not stickied. Connexion2005 has done an amazing job putting these together and has taught me more in the time it takes to watch the videos, than WEEKS of reading threads.
How to videos
Extremely thorough, thanks all!
Lancered said:
Extremely thorough, thanks all!
Click to expand...
Click to collapse
You're welcome. It's why I started this thread
Thanks !!
Thanks to all who provided these great answers !!
Much appreciated.
This was a very informative read thanks
Sent from my SGH-I897 using XDA App
{
"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"
}
MikeyMike01 said:
Click to expand...
Click to collapse
Meaning what exactly?
How I love when people bash people who are new to particular technologies when those same people were once new themselves.
Point is, provide education not just answer the question.
askpcguy said:
How I love when people bash people who are new to particular technologies when those same people were once new themselves.
Point is, provide education not just answer the question.
Click to expand...
Click to collapse
That was my intention when I started this. It was great to see the guys above hashed it out. Even with all my posts There's a ton that people don't get. My hope is people will ask questions AND NOT BE LOOKED DOWN ON!
There are many MANY great people out there in the know, that are willing to help. Post your need, someone will eventually answer. NO QUEST IS DUMB!
hi i'm not an expert excuse me if the question seems silly:
i own a google nexus one. i've seen a lot of kernels around and i was wondering what is their purpose. besides i wanted to know if the roms (cyano, stock deodexed rom and so on...) come with their own kernel or if it has to be installed separately. in this case how do i know which my stock kernel was?
Think of Kernels as mini ROMs, they are addons that you can install to the System Partition. Common addons are Undervolting (less power consumption), overclocking, and enabling 720p video recording. So yeah, they're like ROM addons. Some even speed up the phone and fix lag and coloration issues, but thats mainly for the Galaxy S line.
an example is the battery driver edits we did to the nexus one. if you want to change how the phone works with the hardware, changes had to be made to the driver, and re-compiled, then install that kernel to the phone.
so all the devs have all sorts of ideas and things they want to change to drivers and cpu voltages and whatnot to get better performance and stuff. so each kernel has different edits like that battery one. and people like to try out different ones to see which works the best. that's the idea.
ok tnz a lot for the explanation
Hi,
I'll receive my HTC One soon and I don't know what kernel and rom install...I have read many subject about it but it still be confuse in my mind and I don't want to spend a lot of time trying every kernel and rom. If you could help me to choose a kernel and rom (even the stock one it doesn't matter), it would be very nice.
Here is what i expect from my phone (from the most important) :
1 - Stability
2 - Autonomy
3 - Ergonomy (for exemple having very fast and accessible settings)
4 - Performance
And if possible, I'd like to (but this point must not counter the two first points) :
- Activate the HTC logo to lock and unlock screen OR lock and unlock via the tactil screen or gyroscope (with movment)
So, wich kernel and wich rom for my use ?
Pardon my english, I hope you got what I meaned and thank by advance!
I would simply stay on stock rom for best stability. the second best alternative would be to get s-off and convert your sense htc one into a GPE, for faster update cycle.
either way, you'd want with both a custom kernel such as elementalx for dt2w etc. for further customization you might want xposed + mods such as gravity box and others. for now however xposed doesn't support art runtime (some say art is much faster than dalvik, but myself didn't find it any more performant )
good luck
Sent from my HTC One using Tapatalk
Rom comparison threads are not allowed. People prefer different roms for many different reasons, so no one rom is best for everyone.
I'd stay stock for a while, but to the dev section and read up on some of the ROM threads. then when you are ready to flash, you can try out the ones that interest you and see which ones you like.
As Stated It is all user choice. What may work for me may not work for you. I also advise you to stay stock for a while and do some reading. Re-writting the OS on your device is not something to be taken lightly. You could end up with a paper weight that is nothing more then a skipping stone. Do you research and put he time into it and you will save yourself alot of grey hair and heart ache.