Database Info

Begging for advice on performance...

All I really care about is email and sms/mms for my HTC Fuze. I have 4 email accounts (2 gmail and to standard smtp) and am using Seven Beta to check them. I'm currently running the latest EnergyROM as I've found it to run the fastest. I have been running SPB Mobile Shell 3.1 as it seemed to be the fastest interface. However, it's still unbearable. Is everyone else's FUZE this slow or am I missing something that everyone else is doing to make this thing usable?
When I get a new email or sms, I hit the icon and wait sometimes 30 seconds for the messaging app to open. Many times, the entire phone freezes for a minute or so. I've been through ROM after ROM and literally done everything that I can to make this thing faster. It always runs a little better when I first flash a new rom and then slows down within a week. I always have to clean out my emails/sms to get a margin of performance back.
All I need is suggestions for the lightest setup, simply for SMS/MMS/Email because that is 95% of what I use my cell for, the other 5% is Facebook and Google News.
Any helps please?? I've got 2 months before I can get an iPhone... counting down the days. I just can't take Windows Mobile anymore...

Well, since you only use email, facebook and google news, you should get a light weight rom. I don't know what you're using now, but don't use a Sense (or any manila) rom. Get the lightest weight one you can. You should try Trueg's rom. It didn't get any attention, but it may be perfect for you. If I were flashing other people's roms, that might be the one I'd use. On the other hand, you may want a 6.1 rom. Noonski's rom might be worth looking into.
The only other advice is to keep you inbox clean. Don't store thousands of texts/emails on your device. Archive all the old crap somewhere.

Ok, I will look into those. I did reflash with the latest stable EnergyROM last night.. May 2nd and the speed has recovered a lot, even with Sense so maybe something was really messed up in the last ROM.
However, the messaging app still will not load until I restart the devide. I can normally get to my inbox once or twice and then it will never show up again no matter how many times I hit the button. The messaging icon just sits there glowing.
Curtis

curtis_shirley said:
Ok, I will look into those. I did reflash with the latest stable EnergyROM last night.. May 2nd and the speed has recovered a lot, even with Sense so maybe something was really messed up in the last ROM.
However, the messaging app still will not load until I restart the devide. I can normally get to my inbox once or twice and then it will never show up again no matter how many times I hit the button. The messaging icon just sits there glowing.
Curtis
Click to expand...
Click to collapse
I don't use HTC messaging, but from what I've read, that's typical. Disable it and use the stock MS messaging. Personally, I'm not a big fan of any of HTC's stock apps.

if your into wm6.5 I would recommend trying TAELS standard ROM a go (the v4.23547 14th march Standard RD version works better than newest)
It is important to have flashed a standard ROM prior to flashing to a custom ROM & also installing correct rilphone.dll is important.
I am using the above ROM and have 4 mail accounts, over 300 sms/mms in my inbox & it all runs smooth. My device does not hang, does not slow down & is heavily used.
May be worth analysing what apps you are adding as this could be causing some conflict.
Touch Pro can run quite fast & smooth even the standard ROMs are not bad.
When dealing with custom roms based on beta builds ported to your device & using sense 2.5 on a processor half the speed recommended you can expect to have the odd issue !

Stock Jelly Bean disapointment : smooth like butter ???

Hello,
I installed (with pain) the official stock jelly bean on my GEDified Xoom. I thought "project butter" was a real big improvement, according to what I could read in many threads, I was then asking myself why, if it's such a big improvement, the release name didn't change to 5.0 instead of 4.1.1...
Now I have my answer !
Launcher :
I can say yes, there is a fluidity enhancements, but not as much as expected. I could not see much differences between ICS and JB regarding the fluidity, the stock launcher has only been improved a bit : if an icon page is full of icons, with 2 widgets on it, then there are a few lags ...
I use Nova launcher since ICS, and this one is really smooth as butter, much more than the stock JB launcher. You can put 3 or 4 widgets on a same icons page with absolutly no lag at all.
Web browser :
The same with the default JB web browser : I can feel improvements, but some web pages (with no Flash activated) are still laggy ... Compare it with Opera Mini and you will see what smooth as butter should mean ! Opera is just perfectly smooth, no lag at all on any web page.
Non-Google applications :
I couldn't find any fluidity enhancement when running non-google applications. The applications which where laggy with ICS are still laggy with JB, and unfortunatly, perfectly smooth Android applications are too rares ...
I can't even really use most of the new features of JB :
- I can't use the new icons auto-rearranging when moving a widget on a page as the stock launcher is not smooth enough for me, I use Nova Launcher which is perfectly fluid but does not have this feature.
- I can't ear the beautifull voice of Google Voice Search, as I'm french, and it only works for English language ... But I'm not even sure the problem is here, the main problem is that on the official stock JB release, there is no "download offline speach recognition" option in Google Now, so you just cannot activate it. But you can do it on a Team EOS ROM !!!!! This is a shame !!!
- I forgot this one ... I even lost an important feature ! My external SD Card could read or write with ICS, now it's READ ONLY !!!
As the fluidity is my main concern on my Xoom, I was disapointed, I was expecting too many improvements when I read threads of people testing Jelly Bean, so by making this thread I hope I will help people not yet running JB to not be disapointed as I am.
Now I hope the "project butter" is not closed at Google as there are still many improvements to do on this point, I can say that because some third party applications are perfectly smooth where the Google ones are not, so it is not an hardware problem, I am pretty sure that a dual core tablet should be enough to display 2D applications smoothly. But will our good old Xoom receive the future major Android release ? I don't think so as we are already lucky enough to receive JB after more than one year of existence for the Xoom ... But there are still a few bugs to remove in JB, I hope Google will update it (I never had a single crash when running ICS, on JB, I had one the first day I used it when I tried to change the background wall paper, my screen became black and the Xoom rebooted ...).
So now I am thinking of trying a JB custom ROM, but it was so painful to me to restore all my data and applications after the official OTA update (my bootloader was unlocked so the OTA didn't work, I had to put back my Xoom to a factory state with locked bootloader which let me loose all my data) that I'm now a bit lazy and not sure that the custom ROM will be smooter than the stock one.

I have HTC One X and if I get the same JB results on this phone I am definitely giving up on Android and testing Windows Phone. There was a Nokia promotion at my school a few months back and I tested one of their models with Windows. I was impressed by how fast and lag-free it is. I would definitely give it a go.
This phone that I am using has a quad core cpu, 1gb of RAM and what not and OS still lags!! I mean come on!!
Sent from my HTC One X using xda premium

flash an eos rom and you will see the real "smooth as butter"

omnia1994 said:
flash an eos rom and you will see the real "smooth as butter"
Click to expand...
Click to collapse
Did you compare the EOS rom to the stock one ? In fact I would be glad to see a video of the Team EOS release running on a Xoom ...

One of my friends tried windows phone and said it was like running a Beta. Came back to Android.
Major benefits were integration with Xbox.
Windows tablet may fair slightly better but the ARM not being able to run current apps seems a bit like cutting of their arms
I don't think there is cause to assume we will not get KLP (Android 4.2 or 5.0) yet, its a year old. Google seem to want to support devices for 18 months as per last IO...?
Sent from my HTC EVO 3D X515m using xda premium

It's time to be honest- there's only going to be so much ANY software can do on our Xooms, as it turns out that part of the issue is a hardware problem- but not where you'd expect. One of the things folks don't realize about Android is that the performance can be heavily dependent on the type, kind and size of the Flash disk storage a device contains. Flash storage, especially the what's-now-older kind that's on our Xooms, just doesn't perform very well if there's a lot of small, random writes to it, and there's a lot of these in a typical running Android system.
What ends up happening during these small writes is the system can end up waiting a relative eternity on any other disk-based I/O once the Flash controller chip (the one built into the Flash device, not the controller on the CPU) determines it's time to reorganize itself- and what that means is that during that time, the system can (and often does) appear unresponsive, or "stutter". I've worked on several Android handsets and tablets over the last few years, and this problem is beginning to be well-known.
A good example of this is to try listening to music, then browsing a complex webpage- as the browser writes its cache and various database files, many times the music will pause, stutter or click.
I've been doing what I can in EOS kernels to improve the random-small-write performance of the Flash disk- changing when and where writes happen, changing the geometry of where they occur, and I'm now actually testing a series of changes that are based on an academic Whitepaper that look quite promising (but it'll require an entire "Factory Reset" type wipe to make it work).
BTW, if you want to see something eye-opening, run PassMark (or some other disk-I/O benchmark that compares against other devices) and see how badly we do against more-modern devices.
(TL;DR: newer handsets and tablets will likely perform better on JB, mostly 'cause our Flash devices could perform better in many often-used scenarios.)

Thanks a lot for this answer, I understand what you mean about flash memory.
But there are some ways, with the current Xoom hardware, to make things very smooth as some third party softwares do it :
- Nova Launcher -> Perfectly smooth, no lags whatever the number of Widgets are displayed. JB Launcher is much more laggy ...
- Opera Mini -> Perfectly smooth, and very responsive.
So I really cannot understand why Google cannot make things smoother if other companies do !
Plus some apps have perfectly fluid menus (I mean when you just scroll a menu, it's perfectly fluid) and some other apps have their menu so laggy ...
So I really feel like it's not a hardware question but more the way the apps have been developped.
and what about the Linaro code ? Wouldn't it make JB smoother ?

Opera Mini isn't really a fair comparison. How does it compare to Opera Mobile or Firefox or Dolphin or whatever? Opera Mini was intended for small memory devices and doesn't even render the pages locally. The are rendered on Opera's servers and then the result is compressed and sent to the device to be displayed.
I'd say your comparison regarding the launcher though is valid. I haven't personally experienced much lag but I don't have many Widgets.
Sent from my Xoom using Tapatalk

Go EOS you will not be disappointed!! I was very disappointed when ICS came out for my stingray Xoom i didn't even stay on it for more than a couple hours after getting it OTA before i went and flashed the EOS ICS ROM.
As for browsers i love Dolphin HD.

I have stock JB on my Xoom and other than minor launcher lag with multiple widgets, I find this to be really smooth and 100% stable. I see very noticeable improvements over ICS, especially with graphics and overall the smoothness. Overall I am very content.
I will also say, the battery life has surely improved over ICS! For 3D gaming, I lose about 7.5% - 10% in 45 minutes, which projects to about 7.5 hours of gaming with a possible max of 10 hours!!

Sounds like project rusty beans on your Xoom then.
Sent from my Xoom using xda premium

I was wondering if many of the Project Butter enhancements were launcher related. I've always used Nova Launcher as well, and I have seen lag in the past on ICS. Especially since my desktop consists mostly of widgets. PB Launcher is definitely a little better than Nova when loaded with widgets, in my experience. But the ability to customize rows/columns and get rid of icon labels is compelling enough to use Nova. Nevermind the ability to utilize most of the screen without a 1" border on each side, as is the cast with the stock launcher.
One huge difference is with the Netflix app. I remember them talking about Project Butter enhancements to the Framework during the I/O keynote speech, and I suspect the changes helped almost completely eliminate the AWFUL lag I'd experienced in the Netflix app in ICS. Once a show got going, the streaming was fine. It was when navigating through the app that it was horrendous. In JB, it is great!

Fix External Card Write problems
Dizzy,
I had the same exact issue when trying to write to my SD Card - it was write protected and only allowed read permissions. I had problems restoring backups with Titanium Backup and creating new ones - as my backups were on my External card.
I found the solution which seemed to cure-all. I found it with this post: http://forum.xda-developers.com/showpost.php?p=20869996&postcount=7
Basically, assuming you are rooted, in /system/etc/permissions/ mount this folder using ES File Explorer or Root Explorer as R/W, then open platform.xml in text editor and find WRITE_EXTERNAL_STORAGE permission. Add an additional group definition for this permission...<group gid="media_rw" />. Save changes or exit and save changes and then reboot tablet.
You can always try the automated way: http://forum.xda-developers.com/showthread.php?t=1458021
Good luck!

Skeetch79 said:
Dizzy,
I had the same exact issue when trying to write to my SD Card - it was write protected and only allowed read permissions. I had problems restoring backups with Titanium Backup and creating new ones - as my backups were on my External card.
I found the solution which seemed to cure-all. I found it with this post: http://forum.xda-developers.com/showpost.php?p=20869996&postcount=7
Basically, assuming you are rooted, in /system/etc/permissions/ mount this folder using ES File Explorer or Root Explorer as R/W, then open platform.xml in text editor and find WRITE_EXTERNAL_STORAGE permission. Add an additional group definition for this permission...<group gid="media_rw" />. Save changes or exit and save changes and then reboot tablet.
You can always try the automated way: http://forum.xda-developers.com/showthread.php?t=1458021
Good luck!
Click to expand...
Click to collapse
Thanks a lot for these informations, unfortunatly my Xoom is not rooted (I had so many problems to update to JB when my Xoom had the bootloader unlocked that I had to re-lock it...).
So I cannot use this solution, and I don't understand why Google put the SD card Readonly where it was read/write in ICS ...
This is really a big disapointment for me from Jelly Bean. I hope Google will change that in the next JB update.

I have tried Jelly Bean as well and noticed that while it is a little smoother than ICS, it isn't "buttery" smooth. That said I don't believe it's so much the software as it is the hardware. Tegra 2's GPU is quite lacking in general and was a huge letdown for many people. If for example you check out JB on an Asus Transformer Prime/Infinity or a Nexus 7, you'll notice it is MUCH smoother overall. Finally, a lot of older apps haven't been updated yet to use GPU acceleration but there is a setting in the developer options to force gpu acceleration which should make those apps perform better.
My Droid Bionic running an ICS leak is smoother than my Xoom on JB simply because it has a faster gpu. The only thing I really noticed that helped with my Xoom's performance was running it at 1.5Ghz OC on the Team EOS rom. There are still websites that lag and have issues, but in general it does run much better than stock.
As for WP7 it is a smooth OS yes but VERY incomplete....WP8 looks to address many of the issues with WP7 but it will also break a lot of compatibility yet again and will basically alienate the current entire WP7 userbase...(if you didnt know WP8 will run most WP7 apps, but WP7 can't run any of the WP8 apps).

Is it just me, or does the Xoom seem to get faster over time with Jelly Bean? I was part of the soak test, so may have had it a few days loner than most, and I have done a couple of resets early on, but over the last couple of days, it definitely seems snappier
Sent from my Xoom using Tapatalk 2

I've got a mz601 and i have to say that JB is totally lag-free on my XOOM. I've never used stock firmware (EOS only) and after updating from ICS (that was laggy as hell) i havn't seen any lag whatsoever. But when i updated to JB i did a complete factory reset (formatted system, user data, cache, internal sdcard and external sdcard) and it was as if i had bought a new tablet.
Stock JB launcher has no lag, system ui has no lag, browser has a little lag when opening complex websites, music and videos have no lag. Also Flash works much better (even if it's not officially supported).
Some apps still lag like they did on ICS but i guess that is an app developement problem since most apps also work lag-free...
GO... GO.... GOOGLE... Android just keeps getting better and better...
PS! I also have the original iPad and that lags alot with ios 5. I also have a powerful desktop-PC (i7 with 8gb ram) with windows 7 and I have to say that the XOOM opens websites faster and scrolls much smoother (even with a bluetooth mouse).
PS2! I'm not an android fan. I like all gadgets but android seems to be moving in the right direction.

http://arstechnica.com/gadgets/2012/07/revisiting-the-xoom-examining-jelly-bean-on-a-10-inch-tablet/
Here is an interesting review of JB on the Xoom

rcatron said:
Is it just me, or does the Xoom seem to get faster over time with Jelly Bean? I was part of the soak test, so may have had it a few days loner than most, and I have done a couple of resets early on, but over the last couple of days, it definitely seems snappier
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
I have the exact same feeling ...

dizzy33 said:
I have the exact same feeling ...
Click to expand...
Click to collapse
I have been very critical of JB since getting it last Friday but I have to say that today the whole experience seems to be coming together and some of the early faults I was experiencing have pretty much gone all of a sudden.
It seems quicker now though only marginally but thats still a step up from how it was at the beginning. And since switching to chrome instead of ICS browser it seems to be giving a better browsing experience; which was definitely not the case with chrome on ICS for me.

[ROM][14-02-13][Flinny] Andromadus - AOSP4.2.2[9]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Reserved

Build 5 was pretty stable, interested to see what has changed.
Tapatalked from Desire S running Andromadus

Build 5 was first build i used of AOSP 4.2 and it was fantatic experience, i never expected 4.2 to work so flawlessly on desire s so fast after release. And to be honest i did not see many bugs.
So i flashed build 6 and i was not disapointed, as you said you will release only stable and advanced releases and it was the point with 4.2 build6.
It would be nice to see official changelog, but i have noticed some nice little resize job done and few small glitches fixed.
I just found one thing i dont know how to fix. On android keyboard swype Lithuanian dictionary doesnt work. It is not in official list until i refresh it and then it pops up and i install it ( it worked well with build 5) and with build 6 it just doesnt work, and when i return to dictionary list there is no Lithuanian dictionary again .

Sensors are not working properly. When i make a call, screen turns off even when i don't block the sensors and it stays that way till the time call is going
Sorry man posted it in wrong thread. Its for andromadus cm 10.1 but do look into the matter as its really is irritating
Sent from my Desire S using Tapatalk 2

Thanks for the info..

Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.

Taranis said:
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Click to expand...
Click to collapse
That's just the way it is for 4.2, Google made it that way.

I thought I saw videos on YT with Google option on 4.2...

Taranis said:
I thought I saw videos on YT with Google option on 4.2...
Click to expand...
Click to collapse
Yeah, that is for devices with On Screen buttons (Galaxy Nexus or Nexus 4/7/10). For those, the buttons are replaced with a dotted circle on the lockscreen, swiping up from which opens Google Now. Since AOSP doesn't officially support any device without hardware buttons, Google probably thought that it would be best to remove the option from the lockscreen, since swiping from the buttons opens that anyways

Trouble with bluetooth
Hi,
Thanks for your work on this rom!
I would like to report an issue with the Bluetooth functionality in this (and earlier) versions of this rom. In my circumstance it doesn't produce an error of crash.
For example. My phone is connected with a handsfree carkit (parrot) and when entering the car it recognizes the phone, asks for pin code and 'gets connected'. The problem is that the phone is not visible (as usual) on the handsfree device and the overall functionality does not work.
If I can be of any assistance in this I'll gladly be of help.
Thanks for your work!

Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus

Anyone know why the sound disappear?. notifications, alarms, ringtones, ect.

Thanks for the enlightenment!
suku_patel_22 said:
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse

Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!

Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Click to expand...
Click to collapse
camera animations do lag sometimes and some pictures you take tend to not show up in gallery after you have taken them.
As for battery all i can say is :highfive: battery is almost same in all 4.0/4.1/ 4.2 roms AND it is not at all bad here. I managed to get from full charge(100%) to 81% in 30 hours. I doubt many roms can do something like this in low-med usage.
Other then that this rom is my personal favorite until someone release 4.2 rom with better theme or perfomance.
The only thing i lack in here is conservative cpu governor and maybe little undervoltage.

Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
Click to expand...
Click to collapse
+1
Who can tell me how can I put GPS shortcut on quick setting ??I have everything I need except GPS shortcut...

Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.

noponies said:
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
Click to expand...
Click to collapse
Clean or dirty install?
By dirty install remove Google accound(s) and then add your accound(s) again.
Worked for me!

For JB4.2 based roms (CM10.1 and AOSP4.2)
if you use a BT headset and are having problems with the mic give this a try.
download the following file.
http://andromadus.flinny.org/libbt-vendor.zip
extract it
Push it to your phone with adb - from the command line
adb remount
adb push libbt-vendor.so /system/vendor/lib
adb reboot
try it now.
Give it a try again and tell me if it all works... If all goes to plan new builds soon
Nick.

My Daily Driver Hall of Fame

Index (use Ctrl + F)
Introduction
Panache DD HoF Requirements
Physical upgrades
After Root Report
2014 Stepp_aospX Editorial Correction
Stepp_aospX Troubleshooting Final Corrections
Beauty Shots -- Phone Screenshots
Click to expand...
Click to collapse
Introduction
It's 2014, and stock GingerBread is so boring, so you googled and found the best surviving Glacier rooting guide, upon the newest ROM list, but you saw the entries covered with dust, links as old as Fred Flintstone rolling towards extinction in a dinosaur powered car. You said to yourself, It's too late, the phone's dead.
Your lead is cold, and you don't feel like playing thread detective, so allow me to present, your best answer since the last phone retirement case...
Panache DD HoF Requirements
Well I do say old chap, we ought to have standards coming from a Titanic class phone, and thus...​
Stability - The least crashes, freezes, and bugs.
Function - Every hardware function works with software. Buttons! GPS! BlueTooth! WIFI! Data! Camera! Speakers! Light! Sound! Action! all working as intended.
Battery - Efficient Kernel, combined with ROM must match or exceed stock battery uptime.
Compatibility - Common apps on the market works on the phone. (Youtube, MX player, Browser, etc)
Physical upgrades
We can rebuild him, with a bigger battery!.​
SD Card: SanDisk ultra 64GB microSD from stock Samsung 8GB (iirc)
This was just an adhoc cheap fill one day on amazon.
Battery: Mugen 1700mAh Thunderbolt slim (similar size for MT4G/Panache) from stock 1400mAh OEM
Why? Stock died on 2013, charge held for literally 1 hour max, then battery started bulging.
Improvements: 48 hours uptime on light use, stock gingerbread 2.3
Also: Slightly bigger than stock 1400mAh, in length, fits very tight, no extra backcover required.
Alternatives: Anker batteries, use the search, I've heard they're the best upgrade and bang for your buck.
After Root Report
How I ate the breadcrumb trail, ROM after ROM; optional read..​So the first thing I did was find the newest version of android and the most recent candidate.
aospSX, which was the Synthetic.Nightmare's aospX's work carried over to android 4.2.2 (Jellybean) by SteppNasty.
Looked and felt amazing, however impassable amounts of issues lead me to switch, including malfunctioning stock camera, firefox, dolphin, and stock browser stops responding, and 1-bar signal which plagued Android 4.2 (term: "signal drop" if you want to search).
So I searched for the word "stable"...
CM 7.2, the most stable version of Gingerbread, the stability and battery was amazing, but it didn't feel as good as the JB ROM before.
So I searched again, and I found a like-minded user from the past with similar objectives, Darkgiant revealed through a conversation to another user about the most stable ROMs.
The clue is CM10.0 by either 0.0 or coderz, but one is a dead link, the other have outlined issues after it got discontinued.
So I went back, double guessed myself on the older versions of Steppnasty's ROM.
2014 Stepp_aospX Editorial Correction
For installation of aforementioned ROM, some non-obvious things he didn't mention..​To summon the proper Steppnasty's ROM for your android... you must:
Install the Stepp_aospSX Final
Fix Permissions
Reboot and setup phone settings (Language, google sync etc.,)
Reboot into recovery
Wipe Cache, Dalvik Cache
Install ICS GAPPs
Reboot and use the phone!
Trouble with ICS GAPPs ? (Based off of my anecdotal evidence).​After ROM installation from downgraded Froyo, ICS GAPPs wasn't applicable (md5 double checked)
I just used the phone as is, later on, somehow I was able to install the ICS GAPPs.
Incase you can't use GAPPs, know this may be temporary and you're missing these features (afaik):
Facial recognition via lockscreen
Software EQ for stock Music player
TLDR:
aospSX 1.0.0 -- Android 4.2.2 (JellyBean) -- newer version -- Unstable
Stepp_aospX Final -- Android 4.0.4 (IceCreamSandwich) works only without GAPPs.
Although the ICS version (Stepp_aospX) is old, it's better and not much different, a halfway mark between GB and JB.
Stepp_aospX Troubleshooting Final Corrections
Radio, bugs/glitches, GPS locking, Perma-Voicemail-Notification, My battery omg my battery :crying:!.​
Only swap radio files if absolutely necessary, and when you do, check the md5 sum every hair of the way.
The Radio Version, most important function to your phone, receiving calls from the network towers, has been changed! Haha I should've posted this before the link to rooting. It's when you were downgrading to Froyo (iirc), because no other ROMs I've installed changes radio, this ROM didn't change it either. But no worries, there are vast lists of these radios, available to download either here (CM Wiki) or here (dropbox by acefsw). Just use adb to push the PD15IMG.zip file as usual to sd for a recovery install. The difference between your signal, if it's even different, should be almost immediate after a reboot.
Bugs/Glitches:
Matrix/Zalgo Text // looks like y͏̴̡͢o͜͞҉̴͢u̢̨̕͝'̸ĺ̛͞͝l̕͜ ̸̵k̢͟͟͢ǹ̢̡̕͟ơ̸̡w̨͏҉̡̧ // Fix via rebooting
GPS Never-lock // Fix via dorqus
For GPS, you can also try FasterGPS the app.​
Perma-voicemail-Notification on every reboot // Temp fix: Settings => Manage Apps => Phone => Clear Cache.
Trying permanent fixes now, I've heard if you get voicemail, delete it from voicemail center, it'll work.​
Battery Drain from wakelock // GOOGLE PLAY SERVICES! // To Fix, either task it or filter it (require xposed framework) (For more information on battery, I'll make a separate section later on for wakelocks to filter by, to reduce drain, it allows battery drain only from user permitted activity apart from being idle)
Screen turns off automatically on camera mode and youtube videos // Fix: use screenOn app
Notification cannot be manually toggled off like app settings of JB. // No Fix, hope your app isn't as bad as my Lux D:
Headphone Heat: No bug noticeable, with ATH-M50 headphones, Skullcandy earbuds, Speaker phone over long hours, no over heating.
Extra tips while Unix Editing:
Code:
adb remount
to change permissions of /system/ folder files
[in shell]
Code:
mv renameMe.file renamed.bak
renames .file to renamed.bak, useful for creating backups before pushing gps.conf.
Code:
rm renameMe.file
deletes renameMe.file
Code:
cd ..
cd space
Moves up a directory outside of current folder
Moves into space folder
Code:
ls
lists items in folder
Final Result
Subject to change from threats, bribes and future tweaks/experiences.​
:good: Stability - 9/10, only zalgo text so far...
:good: Function - 8/10 Every hardware button works from stock apps, two of the cameras, LED, Flash, light sensor, microphone, voice search, gps, bluetooth, speakers, mobile data, backup-sync, auto-rotate all work well, I only wish some functions could work without tweaking, ie GPS and notifications bug.
Battery - 5/10 Efficient options provided with smartassv2 and selectable others, however the phone is awake more than necessary, see batstats Currently I'm trying to figure out what wake trigger is doing this (apart from google play) to see if it can beat <20 hour battery time from stock >48 hours with light usage.
Problem solved, new section write-up incoming soon...
:good: Compatibility - 10/10 Stepp_Nasty advised some amazon apps doesn't work, I don't dwell on those fields, being a canadian. However it's awesome that this works just as well as the stock gingerbread, and your camera resolution increased. See comparison (2592px × 1456px vs 2592px x 1936px).
This is the best ROM I can find, if you have another favourite, please list it and give it a rating, because in a few years this phone is going to the grave yard, and whoever is looking here now, still have a glimmer of hope!
Shoutout to XDA Glacier, past and future posters, for giving us the resources to build on this awesome phone.
Future Edits: Format; txt y u no wrd wrap, More Links, Updated Root Guide, Experience/Final Result, more Bugs/tweaks.

[Q&A] Unofficial CM11 for Saga [06.10.14]

Q&A for Unofficial CM11 for Saga [06.10.14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hello! I have my Desire S for more than 3 years and it's really wonderful that it has fresh updates thanks to you guys! Great work! Maybe one day it'll be Lollipop also on our device
I've been using cm-11-20141006-UNOFFICIAL-saga for about 2 weeks, it had "no camera" error, some lagging, but it hadn't "mic error", wifi, gps problems or something else and all in all it was good for a daily use. Then I decided to flash the latest build - cm-11-20141020-UNOFFICIAL-saga and from the start it has problem "Unfortunately, the process com.android.phone has stopped"
I will test your new builds as possible and very glad to help you.

com.android.phone
Installed the latest version of CM11 works, but again an error "com.android.phone".

com.android.phone
Installed the latest version of CM11 works, but again an error "com.android.phone".
what to do?

Issues
cons:
Other person cant hear me during call (in loudspeaker mode everything is alright)
Front facing camera is just fliped 180 degrees back camera
signal stucked at 1 bar
themes tendt to crash but nothing special

dolinh said:
cons:
Other person cant hear me during call (in loudspeaker mode everything is alright)
Front facing camera is just fliped 180 degrees back camera
signal stucked at 1 bar
themes tendt to crash but nothing special
Click to expand...
Click to collapse
There is ver.2 for testing

During development MoKee for DS, I do not know how Ruling solved the problems on warning no text context during flashing Rom and Calling problem on his ROM development. I remembered he has the same problem on version prior to date 08/08/2014.

So far CM11-2014-10-24 is providing users with fast responsive, smooth and stable, however, it is still contained some bugs considerable minor for me in comparison to the mentioned functions. On top of that in SuperSU, list of managed apps which require SerperSU granted is easily shown up when open SerperSU of which none of CM11s for Saga has provided even popular CM11-MoKee 2014-08-09 which provides users with responsive, smooth and rather stable is still not provided this feather which I consider as important as other. If the ROM is not providing the feathers as it is supposed to be, there should be some bugs preventing that feather to normally function. However, considering the machine itself is also far from perfect when using ROMs that it is not orginally assigned for, bugs is not avoidable; besides ROM software itself has to be developed to suite many kinds of apps from various developers. So developing software for variety of favourite is a hectic task. Android phones, for me, small ROM with small algorithms with less complexity should be a good ROM since it provides a direct access rather than going around. I have been testing many kinds of ROMs including sens, JB and Kitkat for a while and decided to stick on Kitkat rather than sens or JB. For old machine like Saga, if users could ignore some minor bugs and battery drainage in comparison to sens or JB , Kitkat is considering a good choice of ROMs around. I mainly used MoKee by Ruling after Devin Kin stop his development and found that the ROM still has some bugs such as list of apps allocated by SeperSU did not shown up and occationally lag and hang up. I found this version of ROM kindly developed by Kylon and sHAKajaada has suite my needs. Thank you very much.

Remix151 said:
Is cm-11-20141028-UNOFFICIAL-saga.zip fixes ringtone_fix_flinny_a5?
Is everything on this point is working or further need to apply this patch?
http://forum.xda-developers.com/showpost.php?p=51318467
Regards and thanks for your hard work!
Click to expand...
Click to collapse
It is working by itself, there is no need to fix, calling can be heard on both sides. Kylon has compiled with his fix though. The problem, I have so far is Wifi Ap, I could not figure out how to enable it, because Kylon has disable WiFi Ap.

here

kchaisu said:
So far CM11-2014-10-24 is providing users with fast responsive, smooth and stable, however, it is still contained some bugs considerable minor for me in comparison to the mentioned functions. On top of that in SuperSU, list of managed apps which require SerperSU granted is easily shown up when open SerperSU of which none of CM11s for Saga has provided even popular CM11-MoKee 2014-08-09 which provides users with responsive, smooth and rather stable is still not provided this feather which I consider as important as other. If the ROM is not providing the feathers as it is supposed to be, there should be some bugs preventing that feather to normally function. However, considering the machine itself is also far from perfect when using ROMs that it is not orginally assigned for, bugs is not avoidable; besides ROM software itself has to be developed to suite many kinds of apps from various developers. So developing software for variety of favourite is a hectic task. Android phones, for me, small ROM with small algorithms with less complexity should be a good ROM since it provides a direct access rather than going around. I have been testing many kinds of ROMs including sens, JB and Kitkat for a while and decided to stick on Kitkat rather than sens or JB. For old machine like Saga, if users could ignore some minor bugs and battery drainage in comparison to sens or JB , Kitkat is considering a good choice of ROMs around. I mainly used MoKee by Ruling after Devin Kin stop his development and found that the ROM still has some bugs such as list of apps allocated by SeperSU did not shown up and occationally lag and hang up. I found this version of ROM kindly developed by Kylon and sHAKajaada has suite my needs. Thank you very much.
Click to expand...
Click to collapse
The feature on SuperSU of which I mentioned that app permission list is not function on CM11-MoKee 2014-08-09 now is working perfectly after updated to new version of chain fire. This problem should be related to SuperSU itself.

Installing CM11 on HTC Desire
Funny thing my answer seems to go to a different thread, but nevertheless...
In the "Unofficial CM11 for Saga [06.10.14]" thread ManishGade described a blank screen after installing CM11. That may happen when boot.img has not been flashed, especially if there's a stock ROM there.
Moving from stock ICS 4.0.4 to CM11 on HTC Desire S:
1. Unlock bootloader (HTCDev etc)
2. Download cm-11-xxxxxxxx-UNOFFICIAL-saga.zip
3. Replace upload-binary (inside the zip) with patched version, or you'll get "set_metadata_recursive" error (see this thread: http://forum.xda-developers.com/showthread.php?t=2532300)
4. "fastboot flash recovery recovery.img", with 4EXTRecovery_v2.1.3RC4 (none of 1.0.0.6 I found worked for me - the screen stuck on "HTC", that's why the trick with upload-binary was needed) - http://www.4ext.net/get.php?f=4EXTRecovery_v2.1.3RC4.zip&device=saga
5. "fastboot flash boot boot.img" with boot.img from the CM11 package
6. Go to the 4ext recovery (battery out/in, VolumeDown+Power, Recovery)
7. Wipe data, clear caches, install the CM11 zip package.
Regards,

Thanks I installed it last monday.
When my waranty on my desire ran out I installed Cyanogen 7.2 even though it is old it is brilliant. Last Monday I decided to install CM11 unofficial for Saga. Also a Brilliant Rom!