3g Tweak - Samsung Epic 4G Touch

In some of the roms the devs say they applied a 3g tweak. Can someone explain to me what tweak they are referring to?

http://forum.xda-developers.com/showthread.php?t=1265990
There are about half and half chances. Some pleople says that it works and the other half says it doesn't work. Because there's always chance going back after this tweak, you can try. If it does not work, then you put the original values back and reboot.

Works great for me i havent had any problems at all.
DOHCHP sent from ICS Epic Touch

kobridge said:
http://forum.xda-developers.com/showthread.php?t=1265990
There are about half and half chances. Some pleople says that it works and the other half says it doesn't work. Because there's always chance going back after this tweak, you can try. If it does not work, then you put the original values back and reboot.
Click to expand...
Click to collapse
Wrong. Flashing a rom can't do that. He's saying the devs have backed the tweak into their rom - you can't alter something that requires the MSL in order to change just be simply flashing a rom. Not trying to be an ass, just being blunt so as to eliminate confusion and farce information.
They are most likely talking about the build.prop tweaks which have been proven over and over to be snake oil. The only other one that it could be is the sys.conf tweak which depending on the reason your speeds are slow, could be helpful - or not.

Related

Advanced Config Tool vs Custom ROM

I've got a stock Sprint ROM in which I'm using the Advanced Config Tool and I'm curious is a custom ROM would be significantly better (faster, longer battery life, etc). Anyone have any insight on this matter?
I had a Touch that I bounced around to various ROMS, only go to back to stock Sprint for the stability. So, rather then doing the same with the Diamond, I'm looking for some advise as to what I'm getting already (with the advanced config tool).
ivtec20 said:
I've got a stock Sprint ROM in which I'm using the Advanced Config Tool and I'm curious is a custom ROM would be significantly better (faster, longer battery life, etc). Anyone have any insight on this matter?
I had a Touch that I bounced around to various ROMS, only go to back to stock Sprint for the stability. So, rather then doing the same with the Diamond, I'm looking for some advise as to what I'm getting already (with the advanced config tool).
Click to expand...
Click to collapse
just try the tool for your self....whats the worst you can do...a hardrest
if you mess things up
Oh no, I am using the tool and I like it. I was just curious if anyone knows how much faster an all out custom ROM would be... Yes, I could flash some myself, but that would be a lot of work if I just have to go back to stock (as I did with the Touch). But, if the custom ROM is significantly better then the advanced config tool alone, then I might consider giving it a try.
ivtec20 said:
Oh no, I am using the tool and I like it. I was just curious if anyone knows how much faster an all out custom ROM would be... Yes, I could flash some myself, but that would be a lot of work if I just have to go back to stock (as I did with the Touch). But, if the custom ROM is significantly better then the advanced config tool alone, then I might consider giving it a try.
Click to expand...
Click to collapse
I tweaked my phone as much as i could and did improve but Shine On 2.4 is faster!
I would rather use a cooked Rom because, the the chefs (almost ) always know what they're doing, and they have the experience with tweaking to perfection.
Sometimes when they experiment with things it causes unstability, but they're only doing it to develope the perfect Rom. When using the cooked Rom's you alsow contribute to the chef work, and to this forum, in the search for perfection.
Is there a poll to compare all ROM's that are out there?
MegadethPantera said:
Is there a poll to compare all ROM's that are out there?
Click to expand...
Click to collapse
Sticky's Sticky's
http://forum.xda-developers.com/showthread.php?t=415194
Significantly faster....no question!
Why?? Lots of reasons...from more available memory ("junk" removed), better memory management to page pooling up to 16mB
Most likely more stable as well (if using a well tested ROM)
Read thru the posts and convince yourself.........
You can only do so much tweaking with registry and/or Advanced Config. Further improvements needs to be cooked into the ROM.
Ok... So it sounds like there is fairly significant difference between the tweak tool and a custom rom. I had figured as much, but I was hoping the tool would have been close, because I just got all my icons set up perfectly.
But, I hate having the knowledge that the phone could be better, faster, etc. Too bad HTC or Sprint or whoever couldn't just get it right from the start! Oh well, I'm going to try a custom ROM one of these days...
Thanks Gang! Oh, and a bit off topic, but when I go to the custom ROM, I'm going to lose the Sprint crap, but the one item I actually use is Sprint music. I bet I can find a cab with it, but I am also going to lose the Sprint Music icon on the Music tab of TF3d. Any way to get it back there? Thanks.
I think AlphaZero has a ROM called "V7 SprintFlavor" that has all the Sprint stuff. Check it out.

Common misconceptions and other useful information (Updated 10/12/2010)

I decided to write this to clarify a lot of the misconceptions around here. This is also good information for people who are new to modding their phones, the Evo in particular. I see a lot of the same questions being asked over and over so here is some information that some may find useful. I will also warn people if I know that what they are doing can potentially destroy their phone or cause it to stop working properly.
RADIO/WIMAX/PRI/NV UPDATES: I see a lot of questions concerning this. Like, "Oh wow, the new HTC build # 3.29.651.5 is out. I installed it and for some reason I still have the same Radio and PRI. What version should I have?"
Answer: The same! Funny thing is a lot of people asking this question have flashed a few ROMS and should know the answer. But still, updating any of the 4 stick regardless of what ROM you are running. Once you flash them, those are the versions you have until you re-flash to update them. ROMS and any of the 4 updates are a separate entity. (ROMS CAN contain radio updates within them, but none that I have found that are not custom have radio updates built it. It is just possible to do, for arguments sake.)
WARNINGS: KNOW THE DANGERS INVOLVED WITH WHAT YOU ARE DOING
1. Flashing radios from another handset can make your Evo stop working correctly. Only use radios made for an Evo. Period.
2. Common knowledge is to always use the latest radios for the best performance, battery life, and signal. I see this in a lot of ROM threads. While true, radio updates and the like can be tricky at times. Make sure you do those updates separate from any other installation. I do not recommend doing a ROM and radio flash at the same time.
3. Did you know flashing your Radio can break 4G? It can. Each phone has a unique encryption key for the 4G. So let's say Grace buys an Evo and I want her radio update. So I take the update off her phone and add it to mine. Well, it will probably work, but there is a chance it will overwrite my keys and then what happens? Well, if Grace is using 4G, I cannot use it at the same time since we have the same keys now! Now you have two handsets with one set of keys. There is a way to fix it (will update with link soon) but still, did you know you can mess it up?
4. While it is always best to use the latest, I suggest EVERYONE (regardless of anything else) should have a copy of a rooted 2.2 ROM. This way you can at least restore your radios to a working state in almost every case.
5. While there might be fixes out there listed (if you do screw it up), do you have the ability to use them? What if that fix does not work on your phone?
6. Ivide Infra brought this up, "Doesn't a Nandroid back up everything, including radios?" No it does not! I read that there is a way to back radios up using Amon RA recovery but not sure if it is true or not. I cannot seem to find that post again and I looked (didn't look hard, but still). This is a good example of a situation where you think you have a safety net but may find out there is none if something goes wrong.
The moral of the story? Read up on something before you do it, especially if it is something you are trying for the first time.
What ROM works best for me? I see this a lot.
Answer: I don't know, nor does anyone else. This is like asking your buddy at the party which girl you should try and hook up with.
You have to try a few because we all have our preferences. (ROMS, not the women!) Some like Sense, some hate it. Some want a stock ROM with added features, others want a totally customized ROM that is radically different that stock (like CM6). You know you have the right ROM when it has everything you want and everything you use works. You have to try as many as you can until you find the right one for you.
A better thing to do is tell people what you want in a ROM and ask what ROM they suggest after they get an idea of what you are looking for. Try their suggestions but still try a few that seem to be what you are looking for. The first post in all of the ROM pages on here have detailed information about the ROM; read up and find out what the ROM has to offer. If you need your phone for important stuff (like work), I highly suggest you do not use a RC (release candidate) or especially a Beta ROM (unless the description claims everything works). It may decide not to work at the worst possible moment!
If you are happy with your phone at stock yet want to have the benefits of being rooted with super user ability, use a stock ROM that is already rooted.
You also have to be aware that some ROMS can have issues. Sometimes stuff will not work when you try and use them (for example, 4G, HDMI, Cameras, and FM Radio to name a few). You really have to read the known problems and if it sounds like something you use will not work or if you want a completely 100% working device, do not use a ROM that says something is not working. Double that if it is something you use often.
Lastly, if you really want a ROM that has everything you want, you will have to learn how to make your own. Please do, I have released the second version of my ROM, feel free to check it out! (Link is in my signature)
After rooting, how do I install a ROM?
Answer: Through your recovery. It is always highly suggested to wipe data, cache, Dalvik. Here is the steps (this is how I do it and have not had any problems yet.)
Before flashing, ALWAYS do a Nandroid backup in case anything goes wrong! Do this periodically to keep your phone able to be restored in case of problems. I also suggest doing a full backup with Titanium Backup before you proceed.
1. Copy the ROM and optionally the radio/WIMAX/PRI/NV updates, kernel, and theme you plan on using (if any) to the root of your SD card. Hook up your USB cable to your computer, then on your phone switch from charge only to disk drive mode. Your phone's SD card pops up and then you can copy/paste your files onto there.
2. Make sure the transfer is complete and then power down your phone.
3. Reboot into recovery. Do this by holding the volume down key on your phone as you turn it back on.
4. Your phone will enter Hboot, let it load up for a few seconds, then use volume down to go to recovery. Press power to enter recovery. (NOTE: if you select recovery and your phone shows a disk icon with an exclamation mark your recovery is either missing or damaged and needs to be reflashed. That or you may not be fully rooted.)
5. Once in recovery (using Amon RA as my example) you go down to the wipe menu and hit your power button.
6. Once in the wipe menu, I usually do them in the order they are listed. First do a data wipe, then cache, then Davlik. I then tend to do a SD: EXT wipe, battery stats, and rotate settings as well just for good measure. Some recommend doing this twice, but I have never had to and think that is unnecessary.
7. Now you are ready to flash away (reminder, did you do a backup first? If not get to it before doing step 6!). Now you have a choice but I prefer to do it my way. You can flash everything at once, or reboot after each item. I do the reboot after each personally. Flash them in this order: ROM, kernel, theme, Radio/WIMAX/NV/PRI. You can try to flash the ROM and custom kernel afterwards only, then do the rest after rebooting.
8. If everything went well, your phone should take a long time to boot up the first time. Be patient. If it went well, within about 5-7 minutes or less the ROM should load up.
9. If your phone gets stuck on the EVO Screen or the boot animation repeats itself, that means the ROM did not take correctly. Do a full reset by taking out the battery for about 10 second and then reboot and see if it fixes the problem. If it happens again try and start over from step 6. Redo the wiping and flashing process. Also, if flashing more than one at a time, try doing each one, then rebooting before you flash the other.
10. If you do it again and still experience problems, check to see if you are fully rooted. If you determine you are indeed fully rooted, try and reinstall the rooted version of the stock HTC ROM and then try flashing your custom ROM again.
11. If no problems, congratulations and enjoy your new ROM!
What kernel works best for my EVO? This is another question you will often see. A variation is, "What kernel/ROM combo works best?"
Answer: Well, a stock HTC kernel is the short answer. It will work with everyone's phone (well) and likely have some of the best battery life. Now that the newest kernel was just released and has already been rooted, it will work better than the custom kernels overall (as far as being universally compatible). Now that they removed the 30 frame per second limit on the Evo with the 3.29.651.5 kernel, there is less reasons to use a custom one. There are exceptions, of course. But if you want your phone to behave like stock and work well with your phone, a HTC kernel is the only one you need (unless you want stuff like audio tweaks, multi-touch, overclocking ability, or the ability to customize more. In that case, a custom kernel is better). Use the new one with the FPS fix though!
For a custom kernel, again we do not know. A kernel is just above the hardware (speaking of the layers). It is more important than finding the correct ROM. A ROM is more like preference. With a kernel, it is very important to find the correct one for your phone. It has a lot to do with how smooth or fast your phone acts. A kernel that works good for my Evo can run like **** on your Evo. Some phones will work better with Netarchy kernels, others will be better with a Kingklick. Some phone will work well with HAVS, other may hate it. That is how this stuff works!
Sometimes you will know immediately that you have the wrong kernel for your phone. Your phone will act up, restart, connection problems, graphical glitches, and all kinds of funkiness! Other times it may take a day or so of using your phone to spot potential problems. You know it is definitely the wrong kernel if your phone refuses to bootup, even after a battery pull!
Kingklick and Netarchy are the two who make the best for Sense based ROMS, which is most of them. The only exception is Cyanogen. You need to run a kernel made for his ROMS (which are AOSP based, not Sense.) His is the only exception unless they are made from Cyanogen's ROMS (use it as a base).
If running Sense, I would try a few of King's and Netarchy's kernels. I suggest using their latest and working your way down until you find the right one for your Evo. You will know when you have the right one when your phone runs smooth (you have to run them for a day and use them, see what happens.) and you do not encounter any problems that were not present before you switched kernels.
If using CM6 or any Cyanogen ROM build (older, nightlies, etc.) you have to use a kernel made for that ROM. Snap is a popular one. Again, you have to experiment to find the right one.
So the answer is find one that works good for you, stick with it. Or just use a HTC kernel if using Sense and call it a night!
With kernels, what is BFS and CFS? Which would work better for my phone?
Answer: CFS stands for Completely Fair Scheduler. BFS stands for Brain **** Scheduler (sounds fun, right?). These are two different ways that the phone's CPU uses to schedule events. Without getting into the technicalities, here is what I have found for my Evo. Your mileage may vary and again, you have to experiment to find which works better for your particular phone.
CFS: Generally more consistent, use when you want consistent performance and/or if BFS kernels do not work well with your phone. Sometimes will appear to be smoother than a BFS kernel in overall use. The stock HTC kernel uses CFS and it is more standard than BFS.
BFS: Generally a bit faster but a bit more inconsistent (might appear to slow down more and such). Usually faster overall performance but will not look as smooth as a CFS kernel (in general).
Another way to put it, CFS is closer to a flat line, if you drew a performance map it would have less peaks and more consistency. With BFS, there would be more peaks and higher peaks with the faster readings and lower peaks with the slower.
You will find that one or the other may work better for you, or fit your needs better. It is a good idea to try both and see your results. My phone seems to heavily favor CFS kernels and I like the overall smoothness and consistency better. To me, BFS often appears to be more laggy than a CFS kernel. Again, each phone is different though and my results may not match yours.
I want to unroot my phone, what is the best way to do this? If you want to root using a different method, or need to return your phone to where you got it from for any reason, read on.
Answer: You need to download a RUU and install it. You can download an older RUU or get a newer one. This will unroot your phone and make it look like you never rooted it in the first place. You can even do a RUU if your screen is busted, just always keep USB debugging on. To use it, follow the instructions in the RUU executable and do what it says.
Is a full wipe needed when changing kernels? (Thanks to m4rk0358 for this!)
Answer: No, a full wipe is not needed to install a different kernel. I do suggest you go into your recovery and wipe the Cache and Dalvik before installing the new kernel though. In most cases, you can just flash the new kernel over the last kernel. But a full wipe is completely unnecessary (unless you are coming off a kernel made for CM6, in that case a full wipe and flashing a stock HTC kernel is recommended before switching back to a custom kernel).
Overclocking: "How much should I overclock, what should my SetCPU settings be set at?"
Answer: In this new age of phones, we are seeing them become faster and faster. Now with SetCPU readily available and overclock-ready custom kernels, a lot of people are overclocking their phones. These same people also wonder why they are having poor battery life. You see a few posts a day with something like, "Well, I tried the new (insert kernel here) and I overclocked but I noticed I am getting poor battery life!"
The HTC Evo has some really nice components, including the 1 GHZ Snapdragon CPU and the graphics chipset is plenty powerful. Do you really need to make it faster? Considering now that the FPS is unlocked, the phone is as smooth as butter as it is. Most apps work smooth on less capable and older handsets.
Again, all phones have the same components but results will not be the same at all (well, some can have slight differences..for example: the touch screen can be different). Mine may overclock to 1288 MHz without a problem, yours may lock up before you reach 1200 MHz. This is how it works
Most are only overclocking 10-12% or less. While benchmarking scores will increase, you will not see a major difference in overall use of your phone. In fact, you might not see a difference at all.
So yeah, if you want to impress people you never met, overclock and post your screenies! For me, my phone is more than fast enough and eating up battery for little to no perceivable gain is not worth it. This is not a computer with fans and a cooling system that can be upgraded!
But hey, if you really feel you need to run your phone 5-10C hotter just to make it a tad bit faster, knock yourself out! You can either have better battery life, or make your phone faster. Generally you cannot have both.
If using a kernel with HAVS, you do not need SetCPU to under clock. That is exactly what HAVS does, lowers voltages when your phone is idling. You are defeating the purpose by using SetCPU. This is why Kingklick himself tells everyone not to use SetCPU with his kernels.
Is a Task Killer needed for Froyo? (Thank to beatblaster for this!)
Answer: Believe it or not, Android 2.2 does a fantastic job managing apps all by itself. The Android OS is designed to kill apps/tasks as resources are needed and usually only does so when it's absolutely necessary. Using a task killer app can be handy when you encounter an app that freezes or is otherwise stuck but to use it as the primary task killer (instead of letting the OS do its thing) is contrary to the built in efficiency of Froyo itself. Try to trust the OS. Though a task killer is still recommended for the odd lot who are still using Android 2.1 or lower!
Which recovery should I use: Amon Ra or Clockwork? What are the pros and cons of each? Does Clockwork really wipe the Dalvik?:
Answer: Amon RA. Amon RA works, does everything you need it to do, and does it well! I highly recommend using Amon RA, it is generally considered the superior of the two and does a better job of wiping. Everything is right there and it is extremely easy to use.
Clockwork is pretty good too, but here are some pros and cons of each. (I will list a few, there are more differences but I will cover what I can think of offhand).
Clockwork Download here
PROS:
Able to use Rom Manager to flash ROMS and perform other functions (This is by no means necessary though, that is what a Recovery is for and it is generally safer)
Able to read ROMS stored in any folder.
CONS:
Does not seem to work as well as Amon RA in doing it's job.
Rumor that it does not properly clean the Dalvik cache when wiping. You hit it and it does not seem to do anything. Some claim that they checked the Davlik after using it and it is indeed wiped.
Some (including myself) find it a little more clunky to use.
Amon RA Download here
PROS:
Generally considered to be a superior recovery as it is based on Cyanogen code (who is really good, let us just put it that way!) and there are lots of posts where people switched to Amon RA because they were having issues with Clockwork.
Easy access to all functions, no need to scroll through 5 no selections to reach to a yes!
I find it better laid out and functions are nicely categorized.
It works better than Clockwork. Fewer reports of problems.
CONS:
You can only read ROMS and files on the root of your SD card.
It does not play well with the program ROM Manager. Most functions on ROM Manager are only usable through Clockwork (considering the overall poor experience with ROM Manager trying to download ROMS that no longer exist, bad checksum ROMS that I downloaded through it, and other problems....IMO NOT a con. Plus, safer to flash through recovery anyhow.)
Do the signal bars indicate signal strength for the 3G? (Thank to LovethyEVO for this!)
Answer: No. It indicates the connection for just the phone connection. You can have good reception for calls and still get slow download speeds. Generally if you have good signal, you will have good download speeds though.
How do you wipe the battery stats, or how do you increase your battery life?
Answer: As you may or may not be aware, you cannot trickle charge the battery on these phones as they will blow up! To counter this, the last 10% of your battery is going to be a bit flakey. What the phone does is once the battery reaches 100%, the phone software will let the battery drop down to 90% before it allows more charging to take place. That is why you often can use your phone after a full day's charge and immediately be at around 90% for no apparent reason. When you reset battery stats, you are effectively resetting the phone's software. it will take a couple of days for it to relearn your battery and give you a more accurate result and more efficient recharge.
Battery recalibration (Thanks to Cyanogen for this and to fachadick for bringing it to my attention).
If you're experiencing higher than normal battery drain, try the following:
1. Charge the phone to full battery; let it keep charging until the battery says it is fully charged. Do not just wait until the light is green, it isn't always fully charged, causing a lot of inaccuracies. (You can check by going to: Settings -> About Phone -> Status -> Battery Level = Full.)
2. Boot to recovery and wipe battery stats.
(To have the most accurate of battery stats, reboot the phone immediately after wiping the battery stats and wait for your ROM to boot completely to the desktop. Once your entire boot is done and you have full access to the phone, go ahead and pull the charger and continue.)
3. Do not charge the phone until after draining the battery completely, resulting in it automatically shutting off. Take out the battery, and keep trying to turn on your phone until it will not turn back on at all.
4. Recharge the phone completely and then use as you normally would.
This is a method that has been proven to work, I am sure there are other ways. My battery lasts longer after doing this and the reading is much more accurate. It might be advisable to do this after every ROM install if you want the most battery life and most accurate battery reading by the phone's software.
I will add more and reserve a couple more slots, but I think this is a good start. Please feel free to offer suggestions or your own misconceptions and answer.
MY Take on SetCPU
SetCPU is a great program, does what it says, author is good and keeps it updated. I have nothing against SetCPU, the author of it, or anyone who uses it. In fact, I have the purchased version, why would I pay for it if I thought it was garbage? I wouldn't. I also agree with you when you say it allows more control over our phones.
The problem with it is:
1) Too many people are messing with it and do not know what they are doing. They are just trying to mimic what they see others doing, which may or may not work for them. This is the biggest, most common, and most damaging problem with SetCPU.
2) It can cause problems and/or hurt battery life if it is set incorrectly.
3) You do not know it is set correctly or not until you use it for a while. You may be also permanently damaging your phone as you have it set wrong and not even know it (Too high of an overclock for your particular phone, phone getting too hot in a warm environment, etc.)
4) It can cause problems for people who are trying to switch ROMS and forget to disable it.
5) King himself told people not to use it because it can interfere with HAVS. Though yes, one adjusts frequency, the other voltage, they can interfere with each other. HAVS will read the lower voltage and set itself different than if you are at stock clocks, this can cause either problems or quicker battery drainage. Maybe both. Both are going to try ramping up and down constantly and this is what causes the problems and the quicker battery eating.
6) If you set your CPU too high or low and it locks up and you happened to set it to "Save settings on reboot" you may have to do a full wipe and reinstall. Your phone may even be fine for a few days, then decide it does not like the settings you have and then this problem emerges.
7) This is not a computer with a fan cooled case. It is enclosed and there is no easy way to modify the cooling system. Even with a computer it is always recommended to upgrade the cooling system from stock if you wish to overclock. Most are only able to achieve a measly 10-12% overclock. It will test faster, naturally but in use it is not going to blow you away. In fact, if it seems much faster it is more of a placebo, you will barely notice it, if you notice at all. Notice the FPS only goes up 1-3 points? You are not going to see that with your eyes.
8) I notice most people experiencing problems also happen to be running SetCPU. Coincidence?
9) For that measly 10-12%, you can running your phone 10C more or hotter, that is a BIG difference in heat.
So, as great of a program as it is, it is also dangerous in the wrong hands or if it is set wrong, purposely or accidentally. User error is a big issue with it.
I was a an avid user of it myself but now I do not want to use it and will advise others not to because frankly it is not needed unless you want to impress people with your Linpack score or want to see what your phone can do. Overclocking kills battery faster, common sense. Also, the candle that burns twice as bright lasts half as long, the long term effects are unknown.
But hey, if you want to use it...do so. Anyone can do what they want, I never said what I said was the end all/be all. Just remember if you have problems, it is one of the first things you want to disable to troubleshoot.
Hopefully this explains better why I advised not to use it. In case anyone thinks I have animosity towards it or questions why I advised not to use it.
++ Sticky!!!
Reserved for more information
When my 4g was said "broken" from adding a new radio all I did was update my profile in system updates and problem solved.
rutter9 said:
When my 4g was said "broken" from adding a new radio all I did was update my profile in system updates and problem solved.
Click to expand...
Click to collapse
While that is good to hear, you got lucky!
The point is that it is a high risk thing to do and you stand to gain little or nothing from it.
Sometimes the encryption keys can be erased altogether. If you do not happen to have a backup of your keys with your original radio, you are more or less screwed. I know of a few members around here that have broken 4G thanks to this. It can be fixed, but then they will be using someone else's keys. An update will not fix this.
Another point is people do things blindly without knowing the dangers of what they are doing. Maybe this will cause more people to read up more before they do something.
IMHO this thread is great. Thanks for the contribution.
ricsim78 said:
While that is good to hear, you got lucky!
The point is that it is a high risk thing to do and you stand to gain little or nothing from it.
Sometimes the encryption keys can be erased altogether. If you do not happen to have a backup of your keys with your original radio, you are more or less screwed. I know of a few members around here that have broken 4G thanks to this. It can be fixed, but then they will be using someone else's keys. An update will not fix this.
Another point is people do things blindly without knowing the dangers of what they are doing. Maybe this will cause more people to read up more before they do something.
Click to expand...
Click to collapse
then why do most (if not all) of the devs put links to the newest radio/wimax with their roms? Do they strip out the keys so they don't overwrite yours? I don't see why so many developers would stress updating radios if it was potentially hazardous.
what about nandroid? when you do a backup does it backup your radio? if you flash a new one and it breaks 4g, when you nandroid back to your old rom will 4g work?
eurominican said:
IMHO this thread is great. Thanks for the contribution.
Click to expand...
Click to collapse
Thank you and I am glad to help. I hope to make this as useful as possible and add much more as I have time.
Like I said, please anyone else feel free to add your own entries to this.
ivide infra said:
what about nandroid? when you do a backup does it backup your radio? if you flash a new one and it breaks 4g, when you nandroid back to your old rom will 4g work?
Click to expand...
Click to collapse
That is a good point, will have to update my first post. Nandroid does DOES NOT back it up. But I can guarantee a lot of people probably do not use Nandroid before they mess with stuff. Even if they do, what happens if your SD card messes up or there is a problem where your Nandroid does not back things up properly?
The answer: You will still have a broken whatever is broken
These phone are essentially computers with phone functions built in. As soon as you start messing with them, there is a good chance you can mess things up or that things do not work like they should.
I'm pretty sure that a nandroid does not backup the radios.
ivide infra said:
then why do most (if not all) of the devs put links to the newest radio/wimax with their roms? Do they strip out the keys so they don't overwrite yours? I don't see why so many developers would stress updating radios if it was potentially hazardous.
Click to expand...
Click to collapse
Because the developers know a heck a lot more about the phones than most of us do, including me. They know how to fix things if they get broke, and they have knowledge you may not possess. Like the inner workings of the phone.
They might not have been aware of the problems. I am sure you can fix almost any problem that comes up, but it if was not hazardous you would not hear people saying, "I have permanently broken 4G" or "I had to return my Evo because I messed it up."
It is like my mom, she knows how to use a computer to check her bank account and email, plus shop. But she freaks out when Firefox asks her if it is ok to update. Yet for us who know what that does, it is an after thought.
timtlm said:
I'm pretty sure that a nandroid does not backup the radios.
Click to expand...
Click to collapse
Clockwork I am not sure about but I read that Amon RA backup does, not sure if it does it by default or if there is a way to do it.
That is another point, you may be relying on a Nandroid that does not have backed up what you think is backed up.
Id talk about clockwork vs amon...pros and cons...and insist people work with amon, perhaps provide a link
Id also add something about "Getting bootloops?" especially when people are flashing known, working, stable roms... clearly the problem is 99% in the wiping of caches.
evohnoo said:
Id talk about clockwork vs amon...pros and cons...and insist people work with amon, perhaps provide a link
Id also add something about "Getting bootloops?" especially when people are flashing known, working, stable roms... clearly the problem is 99% in the wiping of caches.
Click to expand...
Click to collapse
Funny, you must have read my mind!
I will definitely do that and a good idea. I intend to add on whenever I can and provide as many answers as possible.
evohnoo said:
Id talk about clockwork vs amon...pros and cons...and insist people work with amon, perhaps provide a link
Id also add something about "Getting bootloops?" especially when people are flashing known, working, stable roms... clearly the problem is 99% in the wiping of caches.
Click to expand...
Click to collapse
I like using Rom Manager...I'd use it more if only it played nicer with Amon Ra.
firemedic1343 said:
I like using Rom Manager...I'd use it more if only it played nicer with Amon Ra.
Click to expand...
Click to collapse
Agreed. I, perhaps unfairly, associate Clockwork with the pecker heads who borked my 4G so I'll never be able to try Rom Manager as long they require it.
Thanks for the info. Well written and informative article. Thanks again.
Feel free to re-word this if the wording seems confusing.
Sense widgets and alternative home launchers (like ADW Launcher and Launcher Pro): My Sense widgets are missing!
Answer: Sense widgets require Sense. If you're running any home launcher except HTC's Sense you cannot use Sense-specific widgets (or anything else that requires Sense like HTC's default lock screen). There are very good alternatives to Sense widgets anyway such as SwitchPro Widget for quick access to radio toggles or Launcher Pro Plus' Facebook/Twitter/Friends widgets. Use Google to find more.

We need stable Roms!

First off i would like to thank all devs for their hard work!
When are we going to have roms that don't soft reset on their own? everyone is making roms based on calks and they all soft reset when installing software needed and like to use.
for instance i cant install my backup pro on calks roms, but the free my backup works. when installing launcher 7 on his roms, it soft resets during calls.
why can't we have someone use the stock rom, root it, remove ciq, add tethering and so forth so we don't have issues.
i know the default response is "don't download them if you don't like them". We are here to have fun and test stuff but these roms soft reset after stating their roms are a finished product.
We?
I've been through just about every ROM in the development section and have never had a problem.
Sent from the future.
+1
Drunk Browsing
I have been running Calkulin's since I got my device... no issues.
this thread comers off as sorta disrespectful to a dev who works hard on them. imo
Wow
Sent from my SPH-D710 using XDA App
Wow.
You don't get to use "thank you" as an excuse to start bashing the work here. It doesn't matter if the wonderful devs "state their ROM is a finished product" or not. They don't owe you, me, XDA or anyone else a goddamn thing. Frankly, if they want to intentionally put in boot loops for giggles, that's their right and you don't get to say a thing about it. They're doing it for free; entirely for free so that folks like you and I might be able to enjoy an improved user experience on our $600 phones.
Why can't "we" have "stable ROMs?" Because you haven't spent a couple hundred hours programming one for us so we can bash every single problem it has.
Either get working on that or, please, kindly shut the **** up.
Thank you!
Let me know when you create one, OR when you start paying the DEV to work for you and you.
Till then, kindly stfu .
itster2 said:
First off i would like to thank all devs for their hard work!
When are we going to have roms that don't soft reset on their own? everyone is making roms based on calks and they all soft reset when installing software needed and like to use.
for instance i cant install my backup pro on calks roms, but the free my backup works. when installing launcher 7 on his roms, it soft resets during calls.
why can't we have someone use the stock rom, root it, remove ciq, add tethering and so forth so we don't have issues.
i know the default response is "don't download them if you don't like them". We are here to have fun and test stuff but these roms soft reset after stating their roms are a finished product.
Click to expand...
Click to collapse
My Backup Pro works perfect for me on all versions of calk's rom. Sounds like your phone just sucks. I have had 0 reboots unless using the OLD lockscreen mod (before the most recent update), or because of the LOS repair daemon.
Snowflakes
Yeah, no stability issues here and I've tried several ROM's. That said it seems like our phones are like snowflakes. No two seem to be exactly the same. For example, I have never experienced LoS (knock on wood) but obviously this is a significant problem for lots of folks. And some phones can be under and overclocked more than others. Weird.
itster2 said:
First off i would like to thank all devs for their hard work!
When are we going to have roms that don't soft reset on their own? everyone is making roms based on calks and they all soft reset when installing software needed and like to use.
for instance i cant install my backup pro on calks roms, but the free my backup works. when installing launcher 7 on his roms, it soft resets during calls.
why can't we have someone use the stock rom, root it, remove ciq, add tethering and so forth so we don't have issues.
i know the default response is "don't download them if you don't like them". We are here to have fun and test stuff but these roms soft reset after stating their roms are a finished product.
Click to expand...
Click to collapse
Wtf are you talking about? Lol
I can understand where the OP is coming from. When I was on the Evo 3D and every other phone on my signature, when the dev said there rom was complete it was finished and stable.
On this phone, it was a different story. I was also one of the phone Epic users who phone would reboot on EVERY SINGLE rom and that was with no custom launcher and no overclock. It would just hot reboot randomly by it self on every rom.
The OP is correct to a certain extent that EVERY rom on here is built off Culks work so what every problem Culks rom had the other roms had the same problem. So of course my phone was hot rebooting on every rom.
This seemed to have been fixed with the EK02 stock rom became available because now that im on Calks 2.0 rom I havnt had a hot reboot ever since.
To the OP go ahead and install the EK Rom / Radio / Kernal and your hot reboots should go away. If your having reboots from using custom launcher then I dont have a solution for that.
As for MyBackUp Pro it always worked on every rom so I dont know what to say there.
Good luck!
First off, why point fingers at roms when it could, in fact, be the app that is causing the issue? I've been running Caulkin's Rom since his first issue and have yet to have a single reboot.
Any backup program can cause issues depending upon what you're restoring. If you're trying to restore any system settings you're setting yourself up for problems. Even restoring some apps with data can cause issues as file structures may change as roms are updated.
So, do yourself a favor before you start pointing fingers at devs and roms. Don't take the lazy way out just once. Do a full wipe, install all your apps fresh from the market and see what happens. I highly doubt you'll see any reboots at all.
.....
Starburst and Venum have been perfect for me. Sometimes I swear its the device, mine won't overclock at all and playing with voltages causes more problems than it solves on my device. Stock kernel seems to solve all my problems though.
Sent from my SPH-D710 using xda premium
Seriously, I have to back the other responses here. The day you have a ROM that works perfectly for YOU is the day you compile it yourself. Until then, be happy that these guys spend any of their valuable free time contributing something that makes all of our lives more enjoyable. If you can't do that, then kindly find the door.
I havent had a problem with any rom. No reboots at all. Overclocked, underclocked or stock, havent had a problem. Perhaps the problem isnt the phone, but whats behind it.....
Ignorance is bliss.
HappyFillmore said:
Ignorance is bliss.
Click to expand...
Click to collapse
Just so the op knows, I am working on a fully stock rom with no mods or tweaks... Just added apps (I posted a thread over in Q and A for what people wanted in a stock rom).
wolfkstaag said:
Wow.
You don't get to use "thank you" as an excuse to start bashing the work here. It doesn't matter if the wonderful devs "state their ROM is a finished product" or not. They don't owe you, me, XDA or anyone else a goddamn thing. Frankly, if they want to intentionally put in boot loops for giggles, that's their right and you don't get to say a thing about it. They're doing it for free; entirely for free so that folks like you and I might be able to enjoy an improved user experience on our $600 phones.
Why can't "we" have "stable ROMs?" Because you haven't spent a couple hundred hours programming one for us so we can bash every single problem it has.
Either get working on that or, please, kindly shut the **** up.
Thank you!
Click to expand...
Click to collapse
QFT - The non programming user base needs to get some perspective about the fact that they are contributing nothing so therefore have no say in any aspect of development. Such is life.
hypersonicx and venum,
thank you for your response.
all others,
no comment

[ROM][NAND] [No longer being developed] GBX0* + 3.4.41 kernel - update 04/25/13

First I would like to give credit to everyone who has worked on GBX0* in any way. ACL, arrrghhh, detule, and Stinger22 to name a few important faces around here. I do not take credit for 99% of this. It is a modded version of the GBX already published on XDA.
Stinger22 is responsible for building the killer new kernel. I packaged the kernel into a boot.img and collected all the compatible updates into a single installable Zip with lots of tweaks.Stinger22 deserves big thanks for his work here.
There will be limited support for this build. Feel free to ask questions, and even better if you can help answer them. If you know how to fix something that is broken I would love to hear from you. I would be happy to include anything that you can contribute.
Due to the number of people unhappy with the RHOD100s phones and this rom, we do not recommend it for the RHOD100s (not that we ever did as we only have RHOD400s to test with).
New install guide.
Now what you came for:
GBX*
Includes:
GBX 5-8-12 lib update.
Slightly smoother boot animation used.
Build.prop tweaks.
Added a couple of ringtone/media sounds.
Superuser replaced with SuperSU .97
Modded audio.conf file to allow for the streaming of media metadata from apps like Pandora when the advanced menu / car bluetooth mode is enabled in the app. Also this change should allow for more Bluetooth devices to connect to the phone. Does only appear to support AVRCP 1.0, so no metadata without extra app support. However track forward/back/pause will work with some setups.
Added circle battery icons with %s for more precise gauging. Shows in 5% blocks. What you see is +/-3% of what the battery is really reporting. Based off the themes here. It is better than a half filled bar IMHO. It might take a full discharge or two before the battery gague/acl code becomes accurate. The battery also tends to drop quickly in the first 10% and then levels off.
RHOD300 keyboard fix. Credit to Detule
Changed RHOD100 from default keyboard to RHOD100_UK keyboard map.
Fix to ramdisk to resolve error reported during boot.
Fix to bluetooth main.conf to prevent bluetooth media devices from crashing OS. *only included in the 3.4.26.1 and newer full build*
-Still have issues where connecting/disconnecting the sink device can sometimes cause the phone to reboot. Seems sink device dependent. Mostly fixed in 3.4.26.13
Fixed bluetooth typo bug to 3.4.26.1 in 3.4.26.11
Boot animation in 3.4.26.13 credit.
3.4.17 Kernel update:
Including ACL's newer battery code.
More accurate readings from battery gague.
Maybe slightly better sleep battery usage.
Small Bluetooth fix (I find paring to be easier).
Kernel panic fix that may help prevent phone lockup if apps crash.
Many other small patches.
Fixed USB detection issue in 3.4 kernels.
Overclocking still supported. (SetCPU is free to XDA members)
Added a hack supplied by detule to prevent the sd card reader from suspending to prevent unexpected sd card removal errors.
Added a kernel splash screen to cover up some of the rolling text during boot time. Credit.
Sleep works with wifi turned on. - Battery life should improve where wifi prevented sleep before. Wifi tethering will prevent wifi sleep.
Zoom slider bar now works. Acts like a two finger touch moving from the center of the screen. If you tap on the zoom bar it will be just like tapping in the middle of your screen. Something to keep in mind if you get unexpected touches while holding the bottom of your phone. More benefit than a draw back IMHO. Added permission files. Link at bottom for those who just need this (based off of mankineko's work).
3.4.24 Kernel *minor update*
Includes updates from source.
Added code to cause system to reboot rather than hang from a system crash.
3.4.26 Kernel
Reboot function in shutdown menu has been fixed (power off is still broken)
Host file is no longer over written on boot up. This had been preventing ad blocker apps from working correctly.
ACL's panel code has been used. Hopefully this will resolve some issues for the RHOD100 users. We have no way to test, so it is as-is.
Auto brightness has been fixed. You may need to press the power button and force the lcd off, after it has been enabled, before it will take effect.
Device name is no longer reported as 00000000 by ADB. It should show as the serial number.
3.4.35 Kernel
Slight performance tweaks.
Added CrossBreeder mod. Basically helps tethering internet.
Added "Smartassv2" cpu governor. Can be set using apps like SetCPU. Should be slightly better performance, but may come at the cost of battery life.
Added "row" scheduler.
3.4.41 Experimental Rhod400 Kernel.
Shutdown working
Fps limit fixed, plus a slight gpu performance boost (previously was benching about 19fps for both 2d/3d, now I'm getting up to 60fps 2d, 26fps 3d)
Enabled more compiler optimizations. Kernel is slightly larger, but seems to perform a bit better
USB: No need to plug/unplug once before adb works, faster cable connection detection
Other miscellaneous tweaks that may or may not help battery life
Known bugs:
Many of these bugs are found in the 3.X kernels, and so they may be found here too.
MMS does not work out of the box. Add this APN info if you want it.
Google maps newer than 5.9 shows graphic distortions with street names, and other graphic issues sometimes. Waze is a good gps alternative if you want something with more features.
Shutdown and reboot options on the power button menu do not work.
Auto backlight does not work.
8-15-12 RIL update breaks radio (on CDMA for sure/no reports from GSM owners).
SD card unexpected removal errors when the phone wakes from sleep on *some* phones. -try a non SDHC sd card if all other standard troubleshooting fails. I have been able to use a 512mb and 1gb card micro sd card without issue. However all my 4,8,16, and 32gb micro SDHC cards have this issue. Hacked work around as of update 3.4.17.
May have to remove and reinsert USB cable a few times before the phone will recognize it has been plugged into a data port. Also you may need to turn features on/off to get the correct tethering/usb storage/usb debug to work correctly.
No front facing camera support for RHOD100.
Deleting bluetooth.apk may be necessary to get the phone to connect to some Bluetooth devices that have any advanced features.
If Bluetooth is left on and the phone is rebooted/crashes, the unit may bootloop. I have not found a fix other than reloading the Rom from recovery.
This bug seems to effect A2DP and other audio streaming devices the most v.s a bluetooth mono ear piece for calling with. This is a bug I have been able to repro on the GBX*+ 3.3.6 kernel as well. Make backups before using Bluetooth. If you are a CDMA user, you could try the original Ril from inside the GBX+3.x rom. It seemed to cause the reboot loop a little less. However GSM users must have the 5-8 Ril to use this Rom.
Found that this bug seems to be for devices that support multiple profiles. I have a Bluetooth receiver that will use phone and media profiles. If the phone profile is disabled the lock-ups do not happen. This work around will not let you use the phone features, but you can stream media. You need to pair the device. Then long touch it to get a to an options menu. Uncheck the phone profile option to stop the crashes when playing any media.
Sometimes if the phone locks up during the boot animation from this issue, then you reboot once or twice, and leave it alone for a long long time it will sometimes finally finish booting. It is worth a couple of reboots, and a lot of waiting vs reloading the rom. It also seems to help if you plug the phone into the usb on a computer after the boot process has passed the blue screen.
Pandora's internal/advanced bluetooth settings must be turned off, otherwise it may crash the phone on device disconnect.
Bluetooth is not 100% stable, and may crash the phone on connecting or disconnecting devices. During use it is stable.
If the phone crashes while bluetooth is turned on it may boot loop. If this happens connect the phone's usb port to a charger or usb port on a computer. This should cause it to boot correctly on the next time around.
Sprint phones must be activated on the Sprint network in WM before loading Android. Android can not activate everything correctly.
It has been reported that the keymap for the RHOD300 is not correct.
Not an Android bug, but Sprint DNS services are crap. I found good working links not working correctly due to bad dns info. Of course you can use any public dns server you like.
A suggestion for getting your own dns in more easily is this App.
If you tether on Sprint I suggest that you put your own DNS server in under the TCP/IP settings on client device as it will only use sprint's by default. I leaned this the hard way.
RHOD100 WIFI may not reconnect to access point automatically upon waking from sleep. Disable and reconnect to work around.
This Rom was only tested on the Sprint TP2 RHOD400. It will probably work on any that worked with the GBX0* + 3.3.x kernel, but we can't promise it.
Updated RIL from Skysoft here. Not included in any build. 4-16-2013
Full Downloads:
GBX0*+3.4.17 Full.
GBX0*+3.4.24 Full
GBX0*+3.4.26 Full
GBX0*+3.4.26.13 Full *feedback on if Bluetooth is still crashing the phone after a clean rom load would be interesting.*
GBX0*+3.4.35 Full
Kernels:
3.4.26 Kernel update.
3.4.24 Kernel update.
3.4.17 kernel update.
3.4.35 kernel update.
3.4.41 Experimental Rhod400 Kernel.
If you download please hit thanks at the bottom and/or post feedback. I'm curious as to how many people are downloading.
New install guide.
Old install directions for all other NAND roms.
It is assumed that you have unlocked your phone. If not read here and/or here, and/or here.
If you are running the 8-15 ril that was patched, and you are unable to get a cell signal, I would highly suggest that you install the older patch ril file.
If you want to add just the permission files for the zoom bar (and a few other things) rather than downloading the whole thing again here they are. When I did this it broke Zeam. I had to add another launcher, and then switch between the two. That fixed it for me.
As always BACKUP, BACKUP, BACKUP before doing anything. Please use at your own risk.
*Related goodies*
Gapps package.
For those of you who want an ICS facelift, check out the modded Zeam launcher.
Most recent recovery thread. - this recovery creates a md5 error on a backup's restore. Anyone know how to fix it?
ACL's known good recovery.
Good chance you will need to calibrate your touch screen. This thread covers that,and how to make it stick.
I may have found a launcher that is more lightweight than Zeam from what I can tell. I am running Lighting Launcher, and am quite happy. Seems to have an even smaller memory footprint, which is great for phones without much memory.
Swapper2 app. This is an interesting thing I found the other day. It allows you to use your SD card for swap (Virtual ram). I did verify that a 64mb swap file (did not test swap partition) can work on our phones. I would love to hear some feedback from people who might be interested in playing with it. I would suggest a Micro sd card with a high random read/write speed. Here is a guide that is already made if you want to use a swap partition rather than a swap file. It will probably wear out your sd card faster, but sd cards are cheap these days. Also note that SD storage vie USB may not work if you use this mod.
Update.
I got out my 32gb high random speed sd card today, and I whipped up a swap partition according to the guide above. I bumped the swappyness setting to 100. I was in a generous mood, so I lopped off 1gb of space for swap (256mg would have probably been a better choice). I did get a name error when I enabled it, but it seemed to work just fine. The swap space of 1gb showed up by the free command, and the swap space showed use after I ran a few apps. It is a subjective observation, but I think multitasking is a little smoother. I plan on leaving it setup like this for now.
{
"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"
}
I did manage to max out the cpu, and crash the system resulting in a reboot. I was running two gps apps, and two music apps, and two or three other apps all at the same time (abit poorly though). It might not have liked having multiple apps access the same resources.
Here is a handy app for rebooting the phone quickly, and entering into recovery.
Possible way to disable the proxmity sensor for people who have bad ones causing a non-waking screen here. Credit.
*Bonus for Sprint RHOD400 TP2 users*
If you are tired of the white HTC splash screen here are two nbh files you can flash just like a rom from the SD card. They should only touch the splash screen. Everything else is left alone. Flash one, or both in any order. These probably work on other Rhod phones, but I have no way to test them. So no screaming if something gets bricked. Based off the work in this thread. Reported not working on RHOD100 by this post. Reported working on RHOD300 here.
If you know of an image (480x800 res) that is even more amazing than these, and you feel it would be a good replacement drop me a link to it. If I love it, it will make it to the first post. Otherwise I might just whip one up special for you for contributing.
Primary
Secondary
As of 3-25-13 I have moved onto the EG4G/SII phone after reading about it and SERO legacy at Howardforums.
I will stop in from time to time, and if I am given a newer kernel I will post it. However I will no longer be using this phone.
So long, and thanks for all the fish.
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Slipdoozy said:
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Click to expand...
Click to collapse
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
wizardknight said:
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
Click to expand...
Click to collapse
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Slipdoozy said:
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Click to expand...
Click to collapse
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
wizardknight said:
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
Click to expand...
Click to collapse
im not happy with google selling my info so i refuse to give them any space on my phone lol
i tried the modded zeam all the ways i could think of, before flash, after flash, through adb didnt matter. maybe corrupt apk?
no worries. ill try to redownload it and try it your way with launcher2 first
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Slipdoozy said:
i tried the modded zeam all the ways i could maybe corrupt apk. before flash, after flash, through adb didnt matter.
no worries.
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Click to expand...
Click to collapse
Be ok with loosing the money. Some people have reported that they didn't get the unlock info, and the dev for that is next to impossible to get to respond.
You might check this thread. Not sure if they got it working.
Most of the credit goes to Stinger22. The man is kicking some serious code butt!
I would try re-downloading the apk. I was able to install it with a adb install. Not sure what else it could be. Did you hold your tongue just right while dancing madly during the install?
Slipdoozy said:
im not happy with google selling my info so i refuse to give them any space on my phone lol.
Click to expand...
Click to collapse
You do realize where Android is coming from... Right? lol
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it... Glad it did not get forgotten!
Zoombar!!
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Caldair said:
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Click to expand...
Click to collapse
HAHA. I didn't think the zoom bar would be the selling feature of this rom, but I am glad you are happy.
arrrghhh said:
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it.
Click to expand...
Click to collapse
Didn't know who did the base work. - Gave credit in the post.
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
CodaHighland said:
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
Click to expand...
Click to collapse
Wow. I had no idea that the zoom bar was so popular. Just doing what we can to keep the phone going.
Thank you so much for your hard work (especially fixing zoom bar!!!.)
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
Yes, overclocking is supported. This should be the same as 3.3.6. I believe the frequency range you can choose from is 122-825. Download your favorite overclocking app from the market, and have at it. I use quick cpu overclock lite.
*edit. I think we have some new governor options. Link for descriptions.
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Slipdoozy said:
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Click to expand...
Click to collapse
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
wizardknight said:
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
Click to expand...
Click to collapse
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Slipdoozy said:
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Click to expand...
Click to collapse
I am assuming that you mean OMGB by ACL's rom. To the best of my knowledge there is no way to port the feature without building your own kernel. It is my understanding that the 3.x kernels (what we use) are not compatible with that rom. OMGB userland is no longer receiving updates, so unless another dev adopts that rom it will never work.
I will take the 1% credit for this rom. I have done behind the scenes, packaging, some Bluetooth mods, and testing stuff. The other 99% goes to everyone (esp Stinger22) who has worked on it before me or with me.
On the phone that the zoom bar is not working, did you download that rom zip before or after 11-3? I didn't change the file names or links with the last update. You might try downloading the perms file at the end of the post, and installing that. Otherwise I would re-download, wipe, and reinstall.
If you are still having trouble let me know, and I will go check the zips to make sure that something didn't get busted in the last round of updates.

Turn the S4 into an Oppo Find 7

I wanted to let everyone know for the past day or so ive been testing out the Color OS 2.0 for the I9505, here are some of those results, screenshots, and how to install for yourself.
So, the reason im bringing this up to get started is that for the past year or so i was unable to install this rom on my S4 i assume from not having the correct version of TWRP required for the install (AND the install will fail a few times for random reasons if SU is not installed (rom or not)...I found this out after a full wipe and it not letting me install the rom until i rebooted back into TWRP and told it to root my phone because it found no root access.
So the initial install went like this
Wipe...
Install...
fail halfway...
wipe...
install...
fail haflway...
reboot to recovery from recovery...
tell twrp to root....​back in recovery....
wipe...
install...
success...
Now the rom does include its own gapps package so there isnt a need for that, It also includes its own kernel that because of how heavily modified Color OS is from stock cannot be changed (unless you can find one that will work, the AOSP Ktoonz kernel didnt work and that was the only test i really attempted as i had to re-install the rom (wouldn't boot)
So, once the rom is installed it asks you to pick a language and looks a lot like regular AOSP (dark) but as soon as you do it prompts for wifi and settings FC's, then you move on to accounts and accounts FC's
So to get through this just skip ALL setup processes and type in your name with the built in keyboard (it has to be changed back to full qwerty or your gonna come up wth some weird things)
Then you can go into settings and apply your accounts and things like that to get your contacts and everything back per the usual.
Now onto my impressions of the rom so far...
This is the fastest rom i have ever put on my phone and yes it does come at a cost but from what i could see it is the most overall fluid rom especially when it comes to animations.
It has a lot of cool features i am still learning to use (gesture panel pull up from bottom, lets you draw a shape to preform action and set your own custom...looks cool as hell) and none of them even when enabled slow the device down.
The cost however is battery life...you WANT to have an extra battery or a fast charger on hand because this thing loves to suck power. Im alright with it currently with how fast the thing moves i am going to use it as my daily driver but i went from 50 to 2 in about an hour and a half with screen on. Screen on time isnt that awesome on this phone but standby seems to be pretty good.
Its a nice break from AOSP and Touchwiz, thats all that needs to be said really. Its much faster than either AOSP or Touchwiz even with custom kernels you can take that from me being a crack flasher, ive gone through every kernel made for the device, learnt about them, customized them, and then moved on to test another kernel.
This rom has ceased development but will currently be remaining my daily driver until i can find something else unique, i would say give it a shot guys and see how much you like it
For my install i needed TWRP 2.7.1.0
It will fail, do some troubleshooting to find out why (such as change to RM -rf formatting in settings in twrp) and after you wipe reboot to recovery and let TWRP do the root thing even though there is no rom (i dont know why this mattered at all -_-;;;; but it did) do another wipe when you get it and you should be able to install the rom and it will boot. (THERE ARE NO SIGNAL BARS TO INDICATE SIGNAL STRENGTH when you get in) and once you are finally in make sure you run to your APN settings under Mobile network and then go down to the T-mobile LTE APN and modify it, remove the password and the server info thats in there (for some reason) and change the APN protocol to IPv4/IPV6 and the roaming protocol and then save it so you have good data speeds and such (just to make it set up the same as a standard T-mobile rom)
in this rom ive noticed you CANNOT have wifi on and send MMS so to send pictures ensure you are off of wifi.
There is also a problem being noted in the comments on the rom page with Whatsapp...i dont use it >.> i know what it is but whatever it doesnt bug me at all.
Alright SO TO CLEARLY LIST THE STEPS
1. Wipe phone
2. Attempt to install rom
3. (IF FAILS on install) wipe phone
4. (IF FAILS on install) reboot from recovery to recovery
5. (IF FAILS on install) tell it to root
6. repeat steps 1 and 2.
7. when successful, boot into rom
8. select english and FC your way to the end of setup
9. enter your name or a random name into phone owner
10. setup your account in settings (or just open play store and it will prompt you)
11. Match your APN to T-mobiles standard (Settings>mobilenetworks>APn> T-mobile Us LTe)
--------Remove Password, Server, Change APN protocol to IPv4/IPv6, same with roaming, save and use that apn-------------------
You will not be able to send MMS with WIFI on. (you can if its off)
You WILL have to change keyboards (the one that comes with the rom is absolute ****, use enter to keep what you type english...)
There is a FIX for Whatsapp inside of the roms official forums ( i dont use it though )
ALSO unsure if USB file transfer is working right >.> sure there is a fix for that but it doesnt but me either. (i use wifi file transfer anyways >.>)
YOU CANNOT INSTALL A CUSTOM KERNEL (unless your willing to find one that works)
So far i havnt found any problems for my use, this is one of, if not the, fastest and smoothest roms ive ever used so i am attempting to show others the awesome
link to rom forum below (MAKE SURE YOU DOWNLOAD THE NEWEST ONE, old one borked and buggy)
http://forum.xda-developers.com/showthread.php?t=2748022
NEWEST VERSION (Taken from OP) http://www.androidfilehost.com/?fid=23487008491964142
Just for those of you who didnt know this was out there, or were like me and gave up trying to install it at first.
SCREENSHOTS (CLICK FOR FULL RESOLUTION) (TAKEN DIRECTLY FROM PHONE) (VIA OPPO 3 FINGER SWIPE UP (customizable to change to anything i believe))
Now to get dual tap to wake download an app called Knokr <- from the playstore (its part of the Oppo screen so this is the only way to emulate)
igotlostintampa said:
I wanted to let everyone know for the past day or so ive been testing out the Color OS 2.0 for the I9505, here are some of those results, screenshots, and how to install for yourself.
So, the reason im bringing this up to get started is that for the past year or so i was unable to install this rom on my S4 i assume from not having the correct version of TWRP required for the install (AND the install will fail a few times for random reasons if SU is not installed (rom or not)...I found this out after a full wipe and it not letting me install the rom until i rebooted back into TWRP and told it to root my phone because it found no root access.
or were like me and gave up trying to install it at first.
SCREENSHOTS (CLICK FOR FULL RESOLUTION) (TAKEN DIRECTLY FROM PHONE) (VIA OPPO 3 FINGER SWIPE UP (customizable to change to anything i believe))
Now to get dual tap to wake download an app called Knokr <- from the playstore (its part of the Oppo screen so this is the only way to emulate)
Click to expand...
Click to collapse
o.o was i the only one excited feels bad being the only crack flasher here.
Is it stable? If yes, will like to give it a try
dunhillpanda said:
Is it stable? If yes, will like to give it a try
Click to expand...
Click to collapse
Yeah I really like it once its got a new keyboard. Havnt had a force close or random reboot. The thing is so much smoother than any other rom ive tried its crazy. And after about a day the battery drain has gone away. I honestly am thunkibg about keepimg the thing if it keeps going this well as a perm backup.
The onky issues ive seen i listed in the OP but they arent problems for me really
Looks interesting. Props on the info, I'll look into this soon
Sent from my SGH-M919 using XDA Free mobile app
All Functional
IT seems everything i use the phone for is functional on this rom. I have seen no issues at all with everything that i regularly do and with some added functionality from the android general section (acid audio (i prefer it >.>)) I dont see any reason to change off the rom o.o it has some of the best touch response i have seen on a rom (less lag on inital jerk from finger than touchwiz/aosp) the only thing its missing is the over the top customizations some roms have that will be kinda stock in android L o.o so i think im going to wait for either an L rom or color os 2.5 > 3
>.> <.<
unless another rom peaks my interest before then but im so tired of AOSP and Touchwiz xD and that seems to be the majority of this forum o.o like ive googled a lot of other roms... >.> MIUI and XUI both exist for this phone as does Color OS and many hybrid Touchwiz/AOSP roms exist over in international, as well as many roms that just never make it to our forum because they are being undercut by the popular roms for our device and immediately jump to the end of the forum..some of which are more stable than some of our most popular roms >.<
Sorry i ranted, just overal kind of curious what the Samsung user Obsession is with Touchwiz and AOSP when better than both exist for the devices we use >.> i mean i get liking the style of a rom but im not used to entering a forum here where other roms dont exist o.o i wonder what roms the nexus devices get.
Ooh! This looks fascinating! Im pretty new here but ive lurked forever and I have been looking for a new rom to try. It looks like we value the same things in a rom and the bugs wont be a problem for me either (almost never ever turn on wifi for instance) so im excited to try a rom that youve decided will be your DD.
Ill let ya know how it worked.
Oh man. This ROM is cool...
My phone played nice with it upon install for whatever reason. On my first wipe it took. Most of the setup crashed like you said, for some reason the google log in part didn't crash. After changing the APN settings everything seems to be working great. It really is fast and responsive ( there is a scroll slide effect kinda like iOS that makes lists feel slick)
My small qualm is that it shows that you have no service at all times. Even the weather app says "no service" in it so having that on the home screen and in the status bar is bothersome.
My large qualm is battery. This ROM is freaking gorgeous, I seriously want a phone beefy enough to run like this for a long time, I can't stress how pretty this is for anyone who hasn't tried Oppo's stuff. But I'm getting roughly what OP did on battery though, it feels like only a bit over 1/3 the longetivity of most other Roms I've tried... Reminds me of my old iPhone 4 after 3 years of use. So that really bites. But hell if it isn't pretty.
Another user said the battery problems go away after the ROM settles so imma give that a bit and if it does... I couldn't possibly change it. The weather effects on the home screen are addicting and I love how the rain/snow will fall on icons and splash or accumulate. It feels like a ROM in step with the future.
---------- Post added at 11:56 AM ---------- Previous post was at 11:44 AM ----------
Scrawlerism said:
Oh man. This ROM is cool...
My phone played nice with it upon install for whatever reason. On my first wipe it took. Most of the setup crashed like you said, for some reason the google log in part didn't crash. After changing the APN settings everything seems to be working great. It really is fast and responsive ( there is a scroll slide effect kinda like iOS that makes lists feel slick)
My small qualm is that it shows that you have no service at all times. Even the weather app says "no service" in it so having that on the home screen and in the status bar is bothersome.
My large qualm is battery. This ROM is freaking gorgeous, I seriously want a phone beefy enough to run like this for a long time, I can't stress how pretty this is for anyone who hasn't tried Oppo's stuff. But I'm getting roughly what OP did on battery though, it feels like only a bit over 1/3 the longetivity of most other Roms I've tried... Reminds me of my old iPhone 4 after 3 years of use. So that really bites. But hell if it isn't pretty.
Another user said the battery problems go away after the ROM settles so imma give that a bit and if it does... I couldn't possibly change it. The weather effects on the home screen are addicting and I love how the rain/snow will fall on icons and splash or accumulate. It feels like a ROM in step with the future.
Click to expand...
Click to collapse
Oh shoot I forgot to mention, sorry to spam this thread! Some apps return "package file invalid" and you flat out can't install those apps. This was fixed for me by wiping the caches in recovery but I've read this doesn't always work. In the end I personally got every app I wanted installed so idk if that will be a problem but yeah.
My issues with battery life so far have greatly dimmed, I am unsure if it was just the rom getting used to itself or the kernel setting itself up...but my battery issues have gone down greatly.
THOUGH I will mention that it is still worse than AOSP and Touchwiz, just not by nearly as much as previously thought. (EDIT: THE BATTERY LIFE, I actually don't think ill give this rom up
Also I did also have the problem with "Package File Invalid" and I also wiped the caches to get everything to install properly, but I also found that a full storage wipe of the phone (copy everything important off first) prevents that issue with most roms, I may try it with this one if I decide to ever uninstall it in the first place. The rom is kind of amazing...
Normally I would be experiencing some kind of stability issue with an app or something by now or maybe a keyboard...but not with this rom, not at all. It is still running as amazing as when I first turned it on.
OH I have to mention I guess that I did turn on some power saving settings so that may have been what effected the battery life so dramatically. In honesty I think now it lasts me quite a while...I may actually think I get better battery life in the last 15-20% than AOSP or Touchwiz, touchwiz being the only one with a decent power saver setting (with ROM)
but yeah I love this rom and wish there were more like it for our device....I know miui is available and I might look back into it for more of a full themeing effect, but I love the gesture panel and im gonna try to port it over to the miui rom >.> and see if it will load. Seems to be an app that's built into the phone but im unsure how deep rooted it is.
MIUI+ColorOS = Amazing combo.
Thanks though guys for looking into this! glad to see some other crack flashers around.
This rom does seem to be taking kind of a large leap, but at least its forward.
igotlostintampa said:
My issues with battery life so far have greatly dimmed, I am unsure if it was just the rom getting used to itself or the kernel setting itself up...but my battery issues have gone down greatly.
THOUGH I will mention that it is still worse than AOSP and Touchwiz, just not by nearly as much as previously thought. (EDIT: THE BATTERY LIFE, I actually don't think ill give this rom up
Also I did also have the problem with "Package File Invalid" and I also wiped the caches to get everything to install properly, but I also found that a full storage wipe of the phone (copy everything important off first) prevents that issue with most roms, I may try it with this one if I decide to ever uninstall it in the first place. The rom is kind of amazing...
Normally I would be experiencing some kind of stability issue with an app or something by now or maybe a keyboard...but not with this rom, not at all. It is still running as amazing as when I first turned it on.
OH I have to mention I guess that I did turn on some power saving settings so that may have been what effected the battery life so dramatically. In honesty I think now it lasts me quite a while...I may actually think I get better battery life in the last 15-20% than AOSP or Touchwiz, touchwiz being the only one with a decent power saver setting (with ROM)
but yeah I love this rom and wish there were more like it for our device....I know miui is available and I might look back into it for more of a full themeing effect, but I love the gesture panel and im gonna try to port it over to the miui rom >.> and see if it will load. Seems to be an app that's built into the phone but im unsure how deep rooted it is.
MIUI+ColorOS = Amazing combo.
Thanks though guys for looking into this! glad to see some other crack flashers around.
This rom does seem to be taking kind of a large leap, but at least its forward.
Click to expand...
Click to collapse
Honestly the battery did get better after a couple days. Aosp has probably spoiled me. I really really liked this ROM.
Edit: and I know what you mean by "forward thinking" this ROM feels like the future.
And yes, definitely a crack flasher here. Even now that I have a ROM that I always fall back on I'm still flashing at least a few times a week, and trying new Roms on weekends. >.<
Will try this soon
this is a really nice rom for the s4 , i didn't have to reflash at all, one wipe flashed the rom, it was succesful and booted right up on the first try. Thanks for this, i tried the newest 9/6 debloated version from the link in the OP but it seemed to be a lil glitchy, the one in OP works fine. Thanks again

Categories

Resources