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 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!
Okay, now thats a simplistic version of my question. An expanded version:
What modifications have to be made to a ROM base for it to be a totally new ROM? And what sets apart the ROM from its base upon completion? And what are the limits of what you can use as a ROM base?
A rom has a lot of tweaks and changes made to the code. These can be evening from changing the way ram is handled to enabling tethering. The rom base can be anything but the more different the hardware is the harder it will be to make it compatible
Sent from my GT-I9000 using XDA App
My stab at answering
To be technical, what makes a ROM a ROM is that it is software that gets wirtten into the "read only" section of the phone's memory. In its simplest form a ROM is changes made to the OS software that are beyond what a user can do wile unrooted.
I've seen some ROMs that are little more then glorified themes, and we've had a few here that were changes to everything but.
I would say that any changes that make a noticeable difference in how the phone functions or what can be done with the phone are enough to consider it a different ROM. For our phone these typically include: Mobile AP/tethering enabled, "lag fix" -ext- file system support, lock screen changes, minor tweaks to things like memory management / CPU management, and a few smaller changes like different notification bar icons.
What really makes one ROM different the next is the dev who mods it.
As for what can be used as a base, well anything really. You can use any source you'ed like or even no source as all, as one dev here has done. One problem is that if you use an already existing ROM without getting the original dev's permission it may lead to a conflicts over "stolen code". Another problem is that if the base is not written to work on a specific phone a lot of modding will be needed to get it to run, and even more will be needed to further work out changes in hardware so it runs w/o crashing, freezing, FC'n all over the place.
One last thing to note: there is a big difference between the improvements in performance (speed, battery life, etc) that can be made with a ROM, as compared to a kernel. And much of what we really notice as improvements from one ROM to the next is actually related to the kernel the dev has chosen to include with the ROM and tweaks made to optimize it for the kernel.
First of all, Sorry! I know this question was asked like billion times over and over, and the amount of opinions is equal to the amount of the people who comment, but still.
Currently I'm running stock deodexed XXJVO ROM with CF-Root kernel.
The phone never was stable 100%, but the last days are horrible. Waze stuck (need hard reboot), phone turns off at night (=I dont have alarm clock = I late to work), it FCs and/or reboots randomly.
Now I want to get clear about the ROMs. There are 2 kind of them:
1. ROMs based on stock Samsung roms
2. ROMs based on Googles roms (like miui and CM)
Am I right?
Right now I don't have time nor the interest to play with really custom roms (miui/cm) since I'm not sure how stable they are (am I wrong about their stability?).
I just need phone that calls, surfs the web, sends sms, take photos, records videos and allows me to use GPS for navigation while I drive. For this reason I prefer to go with the roms based on stock Samsung roms (again correct me if I'm wrong. Maybe roms like MIUI/CM are stable enough for day-day use without flashing and reflashing the nightly every few days).
I need suggestion for either full ROM or combination of ROM and Kernel that will unleash the full potential of my phone with the minimum lags/FCs/reboots/etc.
From fast reading here I understood that Semaphore kernel is good enough (of course any other suggestions are welcomed). What do you think about combining it with stock deodexed ROM? Or maybe you have other more preferable ROMS (I don't have any preference to specific rom, however there are some things I can't live without and they are: a) NON increasing ringtone b) preferably root c) Ability to theme the phone, All other fixes/tweaks are optional and are in state of "nice to have").
Thanks a lot for reading this long posts, understand me and helping!
Have a good day and an awesome weekend!
I think you should try stock jvu and latest Semaphore kernel.
And convert to ext4.
That's fast enough.
BTW MIUI and CM7 are very fast and stable.
**tapatalked with galaxy s on CNA and Glitch kernel**
Flash mint berry miui, it's fast and will fit your requirements
Thanks for the replies!
dark_knight35
Stock JVU you mean stock, or stock and deodexed?
Should I bother and try MIUI/CM? (As I understood there is also ICS ROMs, what are those?)
hassaan123
Thanks, Ill consider this. Tough I'm a bit afraid about MIUI/CM since those are different ROMs.
More comments are welcomed!
Team ICSSGS RC4.2 the best for we till now
i wouldnt prefer miui/cm for gps. i used mintberry for 2 months but after the first weeks of pure stabilty it began to random reboot more than twice a day. reflash, new version everytime the same.
the ram management was also horrible in my eyes. i dont really like the cm kernels. they are updated too fast and it seems that they are never really stable for some reason. my battery life was horrible on miui. also annoying is that you always has to clear your memory manually before you want to play a game which isnt even in 3D. plus 720p is always choppy because they want to use more ram which is taken from the reserved memory for video recording. ah the compass isnt working too sometimes... depends on kernel but i didnt find a kernel which works
i am back on darky 10.4.2 with semaphore kernel. darkcore is also very good kernel with good stabilty and battery but i dont use it because i need voodoo color for my display...
especially for you skwo i would prefer the base versions from darky. they are kinda pure samsung with some tweaks and then you can try the dark core which is brought with and if you dont like it switch to semaphore. the standart theme is also very decent and if you dont like you can still customize your phone with the ota app such as things like camera hack (that annoying under 10% thingy that doesnt let you use your cam) or the exteneded toggepanel.
i understand good what you want. i mean its really cool to have such a great community which is working on so much roms but they are too heavy customized sometimes. everything seems so overloaded and the most skins doesnt fit with they own colors they use. i mean there are so much ics themed roms but with 15 different blue tones, that doesnt look "professional" and make android look like a bad designed mess
Kodon
Thanks a lot for this helpful reply!
I heard the same about MIUI/CM/ICS ROMs, that they lack 720p video recording (which is sort of important to me), and how some issues with GPS, and not stable enough.
Yea I tried darky once, didn't like it. I consider trying it again (with maybe different kernel).
The theme is not that important to me, I just put some AOSP theme that adds the battery percentage indicator. I used to play with the phone few months ago (was a ROM hopper and liked to customize it), these days I'm too busy for all this and just need a smart-phone that works.
skwo said:
Thanks for the replies!
dark_knight35
Stock JVU you mean stock, or stock and deodexed?
Should I bother and try MIUI/CM? (As I understood there is also ICS ROMs, what are those?)
hassaan123
Thanks, Ill consider this. Tough I'm a bit afraid about MIUI/CM since those are different ROMs.
More comments are welcomed!
Click to expand...
Click to collapse
You can try Faryaab's jvu (deodexed&rooted). It's hear in general section.
I think a jvu/cm9/miui rom is better for you than ics, coz they are bit buggy.
**tapatalked with galaxy s on CNA and Glitch kernel**
CM7 battery life is not good and call is not stable like rock.
MIUI battery life is better than CM7 but is not good. Call is rock
MIUI / CM7 video recording 720P is sucks. (temp fix = Change bit rate to 1000000)
ICS video playback is bad and some apps will not work or FC. (still on development)
Stock battery is good / call is stable / video playback and 720 recoding is good / but speed is low.
There is not a BEST ROM for all things.
If u can be happy with low speed stocks are awesome.
Best way: Try one to one all ROMs and choose the best for self needs.
Vogie said:
CM7 battery life is not good and call is not stable like rock.
MIUI battery life is better than CM7 but is not good. Call is rock
MIUI / CM7 video recording 720P is sucks. (temp fix = Change bit rate to 1000000)
ICS video playback is bad and some apps will not work or FC. (still on development)
Stock battery is good / call is stable / video playback and 720 recoding is good / but speed is low.
There is not a BEST ROM for all things.
If u can be happy with low speed stocks are awesome.
Best way: Try one to one all ROMs and choose the best for self needs.
Click to expand...
Click to collapse
if you try every rom for sgs you are busy for the next 2 years. the most roms are in the first week very good till every app fills their cache and the partition is getting fragmented. the only method in my eyes to see if a rom is good is to use it for 3-4 weeks. even the battery does need 2-3 loading cycles which can take 4-5 days if the battery use is good and you want to see how it works when its recalibrated after flash.
especially we galaxy s users need to see others opinion in a thread like that. you really cant go through every thread and search for feedback between the whole bug reports and advices for bootloops
I can't decide between stock XXJVU (also not sure if I want the deodexed one) or DarkyRom or some other simple ROM that based on JVU (like SauroM). Any suggestions?
Go for stock jvu, odexed, add andip's theme, remove bloatware, use go launcher with ics theme, semaphore kernel 2.5.0 with ext4
Doesn't get any better than this
Sent using TCP/IP
Thanks a lot! Going to flash
Why so many post ?
Try MIUI (mintberry is very good) and revert to stock rom if you aren't happy.
MIUI has a lot of new things : it's not only the launcher and themes; Miui based on Ginger is stable. I try regulary to return to stock rom and every time I reflash an MIUI, too many things are missing on stock roms or CM7 !
*Before I begin, I must warn everyone that I am a newly registered XDA-Developers user, therefore I am technically a noob.
*English is NOT my first language/mother tongue. If some of the the questions posted below are not understandable, feel free to ask me and I will try my best to rephrase what I said. More information is added below every question for the same one.
*I have read the Forum rules, and did my best to comply with them. Hopefully this does not violate any of the aforementioned rules. If there is such a thing, I will immediately remove any parts/the entire thread.
*As stated above, I did use the search tool, however I did not find any similar thread to this one, hence the reason of opening one.
*Not really experienced with using forum tools, you'll notice the lack of formatting here.
*Summer just started, and with that I have a lot of free time that I wish to devote that time in increasing my knowledge of Android and (hopefully) start being useful with developing something.
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
6.What is the current highest version of kernel working on our device?
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
18.2. Do different drivers exist for our GPU?
18.3. If so, does using them make a difference in terms of performance?
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
That is all, and thank you to whoever can answer at least some of these.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
At the moment TWRP is not fully working, better choose CWMR.
A third one will be RZ Recovery, you can find it in "original development" thread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
Try to change as much as possible.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
Yes
This is present on cm7.2/9/10/10.1
On every Stock ROM or custom stock ROM headphones sound is limited by samsung.
I don't take this as a problem... i think it's a plus
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
No
There are Rom's with huge battery drain, and there are others that can make your phone last for 2-3 days
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
Via Custom Recovery.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
32GB max storage/ uhs-1 max speed
I have a class 10 8GB Kingston and it's perfect
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
The highest indeed is 864Mhz but i never heard anyone running at such high speed. Mine is at 729Mhz, that's 20% overclock...and never had problems like freezing or random rebooting.
Thanks for the answers XDRdaniel.
About the sound output, I think this should be considered a flaw, why push the jack above it's limit, all you get is defected sound, no matter what headphones you are using.
And the clarity also is worse on custom ROMs. Whether this has something to do with my ears, the sound is not clear as having a stock ROM.
Why not take the stock music app with its optimized equalizer and install it on CM for example. Is it copyrighted or something?
Hopefully, other users will answer the rest of my questions.
Reaper's Scythe said:
Thanks for the answers XDRdaniel.
About the sound output, I think this should be considered a flaw, why push the jack above it's limit, all you get is defected sound, no matter what headphones you are using.
And the clarity also is worse on custom ROMs. Whether this has something to do with my ears, the sound is not clear as having a stock ROM.
Why not take the stock music app with its optimized equalizer and install it on CM for example. Is it copyrighted or something?
Hopefully, other users will answer the rest of my questions.
Click to expand...
Click to collapse
It's not about the music player. The rom is the one that has volume boost. It's not that simple
also if you are using a CM based rom i recomend you to use this audio mod.
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
A > Java, and sometimes C++. But Java is better.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
A > No programming language needed, except when you want to add features to kernels, base, etc. Mostly Java and C++ are needed
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
A > Eclipse IDE
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
A > No, building can only done using Linux. Try using another distro.
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
A > Many libraries needed, you can search google for it.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
A> A power PC, with 64 Bit architecture. Around 10 GB RAM, more is better. Also, a fast internet speed is needed.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
A > TWRP isn't stable yet. Use CWMR
6.What is the current highest version of kernel working on our device?
A > 2.37.6
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
A > No
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
A > Team GingerDX or whatever they call it. They build GingerDX ROM based on Gingerbread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
A > Do some theming. To make it unique.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
A > No, sound is perfect for me, basically stock ROM music player have it's own equalizer. BUT, if you do a little more tweaking sound will be perfect.
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
A > No, you're already right. But for NFS, i think you can't.
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
A > Well, it's ROM problem or hardware problem. I have CM7.2 and the battery stand for 2 hours for browsing + music, and 5 hours for listening music, OR 24 Hours without being used.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
A > Some uses recovery some uses ODIN.
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
A > It's jack limitation.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
A > Yeah, sorta like that. No it doesn't impact battery life.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
A > Storage 32 GB. Speed 10 MBs.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
A > This is what make phone unique, some phone can handle 800 and more Mhz, some only handle 700 and more Mhz.
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
A > Intergrated. Not really fast, search for google for the answer.
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
A > It can't.
18.2. Do different drivers exist for our GPU?
A > No, only patched drivers exist.
18.3. If so, does using them make a difference in terms of performance?
A > It does on some Android version.
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
A > Only if you source build a ROM, you can change the drivers. Drivers are exist, like WiFi driver, etc. Yes, it's make a huge or small difference.
F4uzan said:
1.1. What programming language is required to know when developing an app?
-I've been informed that most apps are developed in Java for Android, however I am curious as to whether or not I can program in C++ as well.
A > Java, and sometimes C++. But Java is better.
1.2.What programming language(s) is/are required to know when building a ROM from source?
-Many OS's are developed in different programming languages, does this apply to Android as well?
A > No programming language needed, except when you want to add features to kernels, base, etc. Mostly Java and C++ are needed
1.3. What IDE is best for developing an app?
-I am referring to the Integrated Development Environment. Which is best for Android?
A > Eclipse IDE
2.When building from source, is it necessary to have a distribution of Linux running on your computer, or can this be done on Windows/OSX as well?
-Installing Ubuntu on my PC is problematic. For whatever reason, it can not initialize the drivers for my GTX 560 SE, thus rendering my computer unusable. So as stated, can't I work with Windows, or do I have to be forced to buy a new machine?
A > No, building can only done using Linux. Try using another distro.
3.What programs/files are required to install or download to create an environment for building from source?
-IDE's, libraries etc.
A > Many libraries needed, you can search google for it.
4.What system requirements are needed?
-If I do need to buy a new computer, what are the minimum requirements to work freely, as in without much stuttering when compiling?
A> A power PC, with 64 Bit architecture. Around 10 GB RAM, more is better. Also, a fast internet speed is needed.
5.Which custom recovery better suits the needs of our SGM?
TWRP or CWMR? Or a third one I have yet to familiarize myself with?
A > TWRP isn't stable yet. Use CWMR
6.What is the current highest version of kernel working on our device?
A > 2.37.6
7.Does our SGM have a custom ROM flash counter?
-In the Play Store, Chainfire has an app that resets the number of times you have flashed a custom ROM. Does our device have this?
A > No
8.What group/team(s) are currently building Android versions from source for our SGM?
-I do know of AndroidARMV6, any other team I should know of?
A > Team GingerDX or whatever they call it. They build GingerDX ROM based on Gingerbread.
9.What counts as a "custom ROM"?
-Can I take a build from rohan007, strap some apps in it, change the bootanimation and call it my own? (with permission of course)
A > Do some theming. To make it unique.
10.Does everyone encounter volume problems when flashing custom ROMs?
-On a stock ROM, the volume on the headphones is perfect, however on every custom ROM I have flashed, the sound is too loud. The volume rocker goes too high. Is this on purpose?
A > No, sound is perfect for me, basically stock ROM music player have it's own equalizer. BUT, if you do a little more tweaking sound will be perfect.
11.What does porting mean for ROMs and games?
-Simply put, with permission from the original developer, porting a ROM and a game means making it available for our device. But what are the limitations of this? I certainly can not take NFS Shift, scale down the textures and post it, right?
A > No, you're already right. But for NFS, i think you can't.
12.Does every custom ROM drain battery life on a huge scale?
-For every 20 min, 5% of my battery is drained, while on stand-by. I'm not even going to talk about the drain when actually using the device. I can't make it operate more that 2 hours without it dying. This problem is not present when having a stock ROM.
A > Well, it's ROM problem or hardware problem. I have CM7.2 and the battery stand for 2 hours for browsing + music, and 5 hours for listening music, OR 24 Hours without being used.
13.How is a custom kernel installed?
-Is it via ODIN or custom recovery? Or does it depend on what the file actually is?
A > Some uses recovery some uses ODIN.
14.What is the output power of our 3.5mm headphone jack?
-If I plug my 2 small desktop speakers, the phone just hangs, while, for example, my cousins IP5 has no issue with having 300W 2 speakers plugged in to it. What is the limit? I take it it is very small.
A > It's jack limitation.
15.What does GPU rendering mean?
-I've noticed a few custom ROMs being able to use GPU rendering. Does it mean it renders the UI with the GPU instead of the CPU to give a smoother experience? If so, does this impact battery life?
A > Yeah, sorta like that. No it doesn't impact battery life.
16.What is the limit of an SD card on our phone?
-In terms of storage and speed transfer.
A > Storage 32 GB. Speed 10 MBs.
17.What is the highest overclock recommended for the SGM?
-I think it is around 750MHz, but I've seen ROMs pushing our phone up to 864MHz, with no users reporting fried phones. Does it even matter if the voltage is not changed?
A > This is what make phone unique, some phone can handle 800 and more Mhz, some only handle 700 and more Mhz.
18.What is our GPU?
-You read it correctly. I mean this as in is it a standalone chip or is it integrated? Can you also provide information on how fast is exactly our Adreno 200?
A > Intergrated. Not really fast, search for google for the answer.
18.1. Can we overclock our GPU?
-Like on PCs, can we overclock our GPU to gain more performance? Has this been done before, and how successful is it?
A > It can't.
18.2. Do different drivers exist for our GPU?
A > No, only patched drivers exist.
18.3. If so, does using them make a difference in terms of performance?
A > It does on some Android version.
19.Do different (if any) drivers exist for other hardware located on our phone?
-Like our GPU, do we have individual drivers for Wi-Fi, Bluetooth etc.? If so, does using them make a difference?
A > Only if you source build a ROM, you can change the drivers. Drivers are exist, like WiFi driver, etc. Yes, it's make a huge or small difference.
Click to expand...
Click to collapse
Thank you so much, I guess that's all. This thread can be closed now