Develop Bugs

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

Wipe -> Flash -> Test... Wipe -> Flash -> Test ... The Neverending Story!!!

Wipe -> Flash -> Test... Wipe -> Flash -> Test ... The Neverending Story!!!
I took some time to return back to pure stock Android to see what I was missing from the great custom roms. From the minute your first boot completes, two things happen: You feel comforted as you know that everything works as expected. You feel the stability and safety as your phone probably won't play any weird tricks to you. But as you go through your settings, pulling down your notification panel or pressing the power menu (and probably a million other things!) you see that all the extra things you were used to are not there. Confusion is the next thing to occur as you may indeed like the polished look and safe playing - ahhh, the original firmware on your device -, but you would definately like your phone to do more things.
Most of us, like to make the most of our devices. So we try custom roms, kernels, radios, themes...the list is endless...to find the golden rule in order for our phone to look and perform the best possible. Developers come up with new and innovative ideas most of the time and testers try their mods in order to provide feedback for things to get better. This is a nice thing and I guess this is called evolution or progress, name it what you like. It's an addictive process for both ends, especially for devs as the joy of making something work the way they pictured it to be, is the most rewarding thing in the world and for the end user the joy of helping devs out and by having the latest and the greatest is a reason to make their day.
But let's get focused on the end user. Wiping and flashing...wiping and flashing...it's a vicious circle man! Everybody's searching for the holy grail, the ultimate rom for their device. But guess what...YOU'LL NEVER GONNA GET IT! Why? Concerning custom roms and as the updates are very frequent, even if you have flashed a version with the minimum bugs possible, the next one will probably have an annoying or critical bug. So either you wait for an update or you start searching for a rom similar to the one you use in order to avoid a certain issue. So as you guess, this is a neverending road trip! And the truth is that after a year or two flashing a million of things on your phone, your device gets old and you probably thinking of upgrading to a newer model. Which of course you need to try it's true potentials, so you will start testing things again... What you realise is you as the end user, you never trully enjoy your phone as it has become a "lab rat", constantly under testing.
So what's the "cure" for you? You can spend some time flashing all different kinds of roms and kernels. When it comes to roms, look for the features that you think suits your needs the most and will be used on a daily basis more or less. I know that a million other features might seem cool to you but if you are not gonna use them they are useless to you. The truth is that we are living in a world were more is better but you need to focus on what is really useful to you. Do not forget that the more the features on a rom, probably the more the possibility of issues to occur or the more the battery consumption. So look for something that is not extremely overloaded with all mods available outhere. Look more for stabiltiy and a little less for performance.
To end this...by doing the above, you already provided feedback on devs the time you were trying things, so you helped them improve their work, and by settling down to a specific rom, you will start enjoying your phone and you'll have a device that suits your daily needs. In the end, even if you still haven't got that, you will need to settle down on something. Otherwise you are doomed to play a role in the "Neverending Story" movie!!!

I got my GN on Oct 16th, played with it on stock ROM for a couple of weeks, then 4.1.2 came out so decided to root it and install Paranoid Android 2.54 on Nov 8th...
Running/loving it since.
No theme, just tablet mode.
Of course I've also customized things more to my likings:
Flash player
4.2 swipe keyboard
S4 gallery/camera
Nova launcher
Pie pro
Easy eyes
Llama
Lag fix

For me it's just Flash -> Test -> Flash -> Test, haven't done any wiping since the last few months and I can run a multitude of different ROMs (MIUI excluded) fine. If there are something that FCs constantly, I just clear its data.
I only test out different ROMs when I'm in the mood. When it's just the usual daily routine I use CM 10.1 nightlies since, in my opinion, they are one of the more reliable ROMs. CyanDelta also makes the whole process a lot easier. If I'm going somewhere without internet access for more than a few days, I slap CM 10.1.2 on my GNex and it's ready to go.
Running CM hasn't caused me any issues so far (like not being able to make a call, or GPS suddenly fails to work). I prefer the constant flashing rather than staying on the same firmware for weeks.

True. Personally I've settled with stock Google image since 4.1.1 came out and I use my spare time elsewhere then OCD'ing over "omg new nightly". Using the phone can be more fun.

Just wanted to say, thanks for getting The Neverending Story theme song in my head. lol
http://www.youtube.com/watch?v=4FM-ZkTTLMA

any completely stable finished roms available?

hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3

lasuazo said:
After reading a lot, I believe I can confirm that only GB, and stock ICS are stable, as with no issues, some little glitches but no deal breakers. As for Rogers, there's only Osimod GB ROM based of Rogers. The rest are based of UCLJ3
Click to expand...
Click to collapse
ok thanks lasuazo ;--)

I guess omni and cm11
jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice

thefusor said:
I may be off base here but I guess the [4.4] cyanogenmod 11 and omni ROM are pretty much stable ...
Though the pretty much is still a while away from complete the following are the general bugs with bubor's amazing Roms:
There is an audio bug when making VoIP calls which gives audio latency ..
There is fixed camera rotation which means all the pictures are in landscape
There is no Wi-Fi direct
Google experience launcher is not that Good looking (I know I am complaining)
Google maps 7 has issues but can be dual loaded with maps 6 so they work
Backlight,PPI, lag all have fixes though
Battery drain is a bit more
But as far as performance goes... They are pretty smooth..
So I guess make your choice
Click to expand...
Click to collapse
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.

Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!

I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.

Makshow said:
Maybe we have developer aura or something like that? I'm sure I just used 4.4 PAC ROM for a week without reboot or any crashes. Bluetooth, fixed camera rotation and VoIP - yes, these are issues we can't fix, the same is with google maps v.7 (we just have no hardware NEON support that uses v.7 of maps). There is also issue with wi-fi: if you turn it off, it sometimes don't turns on until reboot. As for myself, I just never turn it off.
Besides of these issues, everything is smooth and stable. Really is. But I got sometimes trebuchet crashes - this was a time when I flashed dirty and didn't make a factory reset - the new trebuchet version sometimes conflicts with the data from old version. I just went to Settings - Apps, found Trebuchet (or Launcher3 if old version) and tapped Erase Data. And the issue was gone! But I recommend to always make a factory reset with new ROM. That's really important.
And even if you have those constant trebuchet bugs whatever you do (icons disappearing is also a trebuchet bug, I never encountered it though), just install a different launcher. Google now launcher is the basic, and is like trebuchet in many ways, miui one is also good, and others, they are many!
Click to expand...
Click to collapse
like i said in my first post, i do really appriciate the fact that people spend Alot of time cooking theese roms, and it easy for me to come along and moan about them, but i have found over the years that after using a custom rom for a couple of weeks or so, its like the ram seems to gradually get eaten away, the device gradually slows down, becomes laggy and ultimately unuseable (not just this fone, and not just me that says this). im not saying all are like this, just many i have used, mainly because they never get finished.
i am very open though to people suggesting that i am doing something wrong, and maybe you have picked up on that something.. you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
also thank you for the erase data tip for trebucket, i will try that.. i have not used the google now launcher yet, but i tried using miui launcher but when i went back to trebucket the lockscreen stayed as the miui lockscreen, which has happened on past cm roms, so i just deleted it.
just gets a bit frustrating when you spend hours getting everything working/setting up personalisation, then the phone just seems to start getting worse day by day, but maybe like you say, its cos i "dirty flashed"?

linuxguy42 said:
I had problems with some icons disappearing when the system reboots. I found that the icons that disappeared were for applications which were installed on the SD card. When I moved them to the system, they stopped disappearing.
Click to expand...
Click to collapse
i did think that, and im sure you are right, but i have had every app/folder/widget dissappear twice now, then, randomly over several restarts, some widgets/apps will replace themselves over the top of the new ones i have just newly placed there.. strange, but i have came across this before on cm roms, so im sure there is a bug there somewhere, even if it is not too common..

jmpcrx said:
you say you do a factory reset, can i ask, do you mean a factory reset in the fone settings, or are you referring to a full wipe using cwm/twrp? as when i flash, i wipe everything accept what i dont want wiped on the external sd.. i dont factory reset, is this after you have flashed the new rom? or before you flash a new rom?
Click to expand...
Click to collapse
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
the device gradually slows down, becomes laggy and ultimately unuseable
Click to expand...
Click to collapse
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!

Welll here are some tip which have helped me
jmpcrx said:
i wish i could agree with you.. im running kitkat crdroid, and like every rom i have flashed over the years, has plenty of bugs that make it very annoying as a daily rom. phone switching off twice a day, icons/widgets dissapearing after rebooting, becomes laggy after a week or so of usig the rom, laggy browsing on all browsers, trebucket crashing regurly etc etc, thats on top of the bugs you list.. the only roms that are stable are completely finished official cm or miui roms (which there are none for this fone..). the stock rom is the only one that has not given me trouble. with the greatest respect to those that put their time i to make these roms, im sure people who flash them make them out to be more stable than they really are unfortunatelly.
Click to expand...
Click to collapse
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .

Makshow said:
Yes, what you do should suffice. I meant cwm/twrp wipe (boot, system, data, cache, android.secure). SD card is not touched. So you are doing fine with that, but anyway, there has to be something make those issues... Can you look at /system/addon.d folder? There is stored info about files that will be preserved even if you install a new ROM with a wipe. If there are many leftovers from ROMs or programs you tried earlier, then you should try to manually clear this folder before new ROM install.
That was the point with pre-4.2 ROMs, and even with 4.2 there was a bug with gallery thumbnails which made it to eat gigabyte and more of storage after some time. That was fixed in CM 10.1.3. Also a Lite-Kernel used by earlier ROMs is very great, but has its issues, for example, systemui crashes when camera launch after some phone use and sleep of death.
I used CM 10.1.3 for a a three months and still keeping a backup of it for a some case. There was no slowing or lagging, it was almost perfect (if you don't use VoIP or BT handset) even after those months of use. Strangely, but I didn't have even "settings -> about crash" issue bubor listed!
Click to expand...
Click to collapse
ok thanks, i cleared the data in trebucket, and started again with placing apps/widgets on home screen, and i also have deleted the hacked version of adobe flash that you install with dolphin browser, and, supprisingly after a couple of days of testing, my apps/widgets are not deleting themselves, the phone is significantly less laggy, and i have had no switch offs, so, im very pleased with that! so id suggest against downloading that version of flash player with this rom..
thefusor said:
i .. umm.. well i agree that as of now they have issues but they will get better .. ours is an old device... so i guess we should tread slowly . which is exactly what the developers are doing .. .
and i agree on the ram hungry part but there are ways for that too . .
funny i have been messaging people to help me post this stuff through them . . but well thats the prob with being a junior member .
My personal tested suggestions for omni rom which have really incremented to the performace some of which are :
- using one of the lightest launchers as i find trebuchet and even google launcher RAM hungry is 'Lightning Launcher' the bloody app itself is in BYTES!!
-also i use link2sd with ext4 that helps in storage and also use sd maid for regular clean up.
-also i have been testing memory swapping using linux swap partition on sd card (class 10 ) and yeah i know it degrades sd card but oh well like Glados testing testing testing
-i have also switch off startup at boot for certain apps
and i apologize for posting what maybe well known tricks or improvs but i really dont know where else to post these (still have the ten post ban from posting )
and if these dont help then sorry to waste your time . .
PS anyone think an F2FS file system like for the nexus7 would\might help ?
tl;dr use the given tips maybe they might help . . and with custom roms i guess you have to spend time to keep them running well .
Click to expand...
Click to collapse
some good tips there, thankyou, i havent tried any of them yet, but i will have a go at some of them and see what happens.. thanks thfusor..

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.

etherfish said:
For what it's worth, I recently had to reflash and decided to use dman325's stock UCLJ3. (He has two versions, stock and one with the aosp lockscreen. If you decide to use either, use the stock one. dman325 had to resign the aosp one with a test signing key that, recently, got invalidated or declined and it prevents Google Play from updating past 3.7.15 and Google Play Services wont install at all because of a shared_uid fault due to certificate conflict, etc.)
I got frustrated with the amount of bloat in an otherwise vendor fun-packed rom, so I went in and hacked out lots of crap. Largely relying on either "what is safe to get rid of" lists for similar samsung phones and my own poking around/guestimation using dex2jar and jd-gui. I really, honestly don't understand what InputEventApp.apk was meant to do. Seriously. But, getting rid of it reduced the logcat spam tremendously. Also, the wsslcm* apks are somewhat frightening in appearance.
I've gone a few steps further, I modified android.policy.jar smali to prevent the emergency dial option from showing up on the lock screen - I accidentally pocket dialed 911 a year ago and am not about to do that again. I also modified the kernel ramdisk image to set ro.debuggable=1 and ro.secure=0. I tried, while I was at it, to replace /dev/random with /dev/urandom, but I'll have to do some experimenting.
I've added a few static binaries for proper gnu utilities. bash, ls, grep, sort, du, etc. It surprises me that a functional shell environment doesn't get more attention on phones with keyboards.
So, that's my $0.02. Try the stock UCLJ3 and fiddle with it a bit. Good luck.
Click to expand...
Click to collapse
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice

jmpcrx said:
thanks etherfish, if i continue to have probs i may well do that, i was thinking about going back to stock. dont think i have the confidence to fiddle like you have though as im more of a windows man than linux, but thanks for the great advice
Click to expand...
Click to collapse
Well, you learn by doing, I believe. Also, I have a classy - for a flip phone - Motorola Razr2 v8 kicking around I can always put my SIM into if I've managed to hose my captivate glide. Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions. So, a number of things have piqued my curiosity.
So, first of all, this surprised me in the logs:
Code:
I/Launcher( 2263): onCreate(): product model family:U1 product model : GT-I9221
I'd always wondered why I had an SGH-I927 when other phones, like the remarkably similar Galaxy R, are GT-I9103. Is/was GT-I9221 an internal reference?
Also, there are other inconsistencies, for example:
Code:
D/RILJ ( 426): [1718]> REQUEST_GET_NEIGHBORING_CELL_IDS
D/RILJ ( 426): [1718]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
If you jump into the debug/field test menu system, (dial *#*#197328640#*#* ) you can bring up the list of neighboring cells in both GSM and WCDMA modes... So, why is the request marked not supported? Furthermore, why didn't samsung disable the request in the first place if they went to the trouble of disabling it from working. I imagine this has a reason, but I doubt it's a terribly great one.
And the FM receiver? I do believe our broadcom BCM4329 is a bluetooth+wifi_in_an_sdcard (well, SDIO really, but still, not pci-e and not usb.) and has an FM receiver built in, but it's omitted and hidden?
Code:
W/AudioPolicyManager( 112): FM radio recording off
Oh, the conspiracy theories. And then there's the weird lines you discover if you dump the string identifiers from /system/bin/drexe!
For example, these lines are all sequential:
Code:
broadcast -a android.provider.Telephony.SECRET_CODE android_secret_code://767*3855
InvokeOemRequestHookRaw broadcast factorst OK
InvokeOemRequestHookRaw factorst fail %d
/system/.configure.txt
(what's with /system/.configure.txt???)
Do not type 767*3855 into your phone. It's the factory wipe code or possibly part of it. I do believe drexe is the DataRouter you often see spamming the logs with:
Code:
E/DataRouter( 107): usb connection is true
E/DataRouter( 107): DSR is ON. Don't send DTR ON.
And we find these strings in drexe:
Code:
__initialize_usb_ipc
/data/.usb_stream
usb connection is true
InvokeOemRequestHookRaw usbstatus true is success
oh, and:
Code:
pipe failed (%s)
fork failed (%s)
child pid = %d.
execute sh.
system/bin/sh
execl fail %d
What do you think? Why does drexe seem to have code to support and start a shell? Well, if nothing else, thank you for reading.
P.S. I don't suspect anything the least bit conspiracy like, malicious, or devious. I've worked for some huge companies; i don't think it'd be likely.

etherfish said:
Also, I'm replying because I can't post in the rom development forum until I have 10 posts. Hurray for well founded, but nonetheless arbitrary restrictions.
Click to expand...
Click to collapse
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...

Makshow said:
Technically, you can post in cappy dev forums started from 3 posts. I saw someone posting there his fourth post.
As for other things you listed... Well, I'll be glad to have an FM receiver in our glide. But I really think that reason for all this staff can be as simply as hands growing from wrong place or restricted development time...
Click to expand...
Click to collapse
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
Other than those couple of things its been great!
im HOPING down the road for an un-buggy or at least minimally buggy version of 4.4. well see what happens with that i guess.

Some help
Pawprints1986 said:
I recently, after some research, also installed dans stock (i decided to go complete stock since i didnt know what the lock screen thing meant).
I havent had any trouble with being outdated. Only thing i noticed (unless im doing it wrong, im new to this phone) was that screencaps dont work. its power button and volume down, right?
Other things id like to customize are data being in the top drawer instead of bluetooth (since i never use it), and id like to be able to see who texted me on the lock screen, but while still using the stock messaging app, and without an app having to constantly run.
.
Click to expand...
Click to collapse
well i always say stock is best cause it IS optimized however there are things like keep and total Google integration that i like so i updated to kit kat
for screen caps if they dont work i could maybe suggest an application called super manager its pretty loaded it has screen cap and may even give you prox sense wake up for device.
also customizing the drawer hmm.. i guess you could try xposed framework but please be careful and make a backup before
as for who texts you and the content of the text you could try dash clock its able to do a lot

hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock. I completely removed all the system bloat with link2sd, uninstalled all att crap. Can anyone recommend me something since I feel the ram consuption still to high... battery so far is doing kind of good almost as in crdroid
But i believe it can be improved. Any recommended settings or something else i can do? Already tried lite kernel but it gave me some issues. Rather keep stock. Any recommendations please guys. Also if you know a "ok google" like app or something as a swifty assistant would be nice. Please recommend. Thanks in advance

jmpcrx said:
hi, just wondering if there are any roms available that are completely stable and finished for this phone?
if not, (as i have not found any), is the original stock rom (rojers) available to download anymore?
thanks guys..
Click to expand...
Click to collapse
Hi,
well that depends.. on what you mean with "finished"
I have tested all (3 months ago) available ROMs for the Glide. IMO the best available ROM is PACman but as said it depends. I used pac_i927-milestone.1.RC1.4.zip for a long time (months) without having any issues besides Bluetooth Headset which is a general problem in JB and higher version). I have tried other PACMan ROM versions as well but the above one was the best of stability and battery life (in my case).
So it depends what features you really need or are a must-have for you. If you do not have bluetooth headsets I would recommend the above otherwise .. well I would recommend sediROM
Regards
xdajog
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
lasuazo said:
hello guys I was just wondering if I could get some help since I returned back to fully Ice Cream Sandwich Stock.
Click to expand...
Click to collapse
Haven't done that before but would be rooted ICS stock also ok for you?
If so:
--> search for thread ID 1994902 or search for: [ROM] Stock UCLJ3 Rooted, Deodexed, Zipaligned
(sorry not allowed to post links..)
Regards
xdajog

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