Database Info

Tired of WM6

I've been a WM user for years, I had the same issue when I upgraded my Axim X50V to WM5.
I've been upgrading to almost every single ROM posted here.
After 100s of crashes, battery drains, radio problems... switched back to WM5, cuz i was unreachable all the time.
Is there any ROM worth trying? no battery/memory drain, no radio issues and no crashes?
Any ideas, thoughts, suggestions?

Best Rom At This Time
aGoGo said:
I've been a WM user for years, I had the same issue when I upgraded my Axim X50V to WM5.
I've been upgrading to almost every single ROM posted here.
After 100s of crashes, battery drains, radio problems... switched back to WM5, cuz i was unreachable all the time.
Is there any ROM worth trying? no battery/memory drain, no radio issues and no crashes?
Any ideas, thoughts, suggestions?
Click to expand...
Click to collapse
Try Jwrightmcps Crossbow Rom 2.12.08 WWE which I am using on my Qtek 9000 since it was released on 12/16/2008. I think his rom is the best. I am very satisfied with his rom. I am waiting for his next rom release that supports 128mb of ram since I had my device recently upgraded from 64mb to 128mb of ram by PocketPCTechs.

aGoGo said:
After 100s of crashes, battery drains, radio problems... switched back to WM5, cuz i was unreachable all the time.
Is there any ROM worth trying? no battery/memory drain, no radio issues and no crashes?
Any ideas, thoughts, suggestions?
Click to expand...
Click to collapse
Thought: The problem's not the ROMs, it's something on your side.
I didn't try many ROMs and with one or two I had stability issues. With the 1.18 radio I had several radio crashes, but most certainly due to a weak battery. With 1.17 none of that. I also didn't have any issues with stability using a WM 6.0 version of thingonaspring's one and I don't have them with Ranju's 7.1 WM 6.1.
Idea: Possibly your problems have something to do with your battery or some software you use, that doesn't work all that good under WM 6.
Suggestion: Check that

Thanks for the quick replay guys,
I tried Jwrightmcps's and Ranju's ROMs, they were two of my favorites, I had some issues with Radio and battery, I decided that i'll buy a new battery and switched back to WM5 until my battery arrives.
Somehow, everything is very stable with WM5, I even canceled my battery order.
I'm pretty sure it's not software related, cuz I even tried ROMs without any additional software, I switched between radio ROMs looking for something that plays well with my service provider.
Do you guys think it's worth trying?

aGoGo said:
Do you guys think it's worth trying?
Click to expand...
Click to collapse
You gotta answer this for yourself. This depends on the benefits you get from WM6\6.1 and how intense the effort you put into this is. And especially the latter one is something we can't even estimate.
I'm usually the first to spend his free time fiddling around with some technical details without any real needs and I just can't help doing so. So I'd certainly try. My wife's just the opposite, so she would (most certainly) not
About the radios, what's your proider and where do you live?
I can't help you much with this, but at least for Germany most people are satisfied with the 1.17 and claim to have better signal or battery life. But sometimes I wonder if most of this isn't just mambo-jambo. Nobody seems to really know what's really different between the radios and I can imagine that many fall for some placebo and the rest is just experiencing "random" changes, not structural benefits of changed algorithms.
Settling for the version your provider distributes seems to be reasonable choice if you don't want to experiment yourself.

ROM performance measurement idea

Hi All Mighty Developers!
You all work hard to satisfy our needs on ROM and App developent but from our point of view (end user) there is no objective and comparable results of developed ROMs for HTC devices.
My idea is to develop a software that is capable of measuring device:
- MTBF (Mean time between failures) or between soft/hard reset
- Average and low high levels of RAM usage
- Average CPU levels, Net usage, etc.
- Device Manufacturer, Type,
- Device OS, ROM, ROM version
This is a small footprint of data which can be uploaded to a site. At server side data could be analysed and integrated into a structural view to hellp users decide to install ROM or not.
ROM developers should be allowed to register their ROM and decide weather to include the client software or not. They can maintain their ROM versions and follow its data.
Regards,
cina.

you are right. these is no objective way to measure performance of roms. the systematic benchmarks are totally usless
i think its much more useful to develop a simple application that does a messure of how long it takes to complete a set of well known tasks.
the application would for example run a script to visually start mail appication then run file explorer then create a tcalender item then change the time then copy a file to the SD card and read from it. the output would be the time it takes to do this. this should be extremely useful for rom cookers to really help them optimise their roms
anybody willing to give this a shot. it shouldnt be that complicated

That is a one shot execution of measuring performance of a software which is influenced by many factors - currently running applications, memory usage, etc.
If execution of a software needs to be measured (objectively and comparable) I think it needs to run several times - so a monitoring application should be developed which records timing of every execution and then averages results.
MTBF and the other parameters I've mentioned in post #1 also needs a monitoring method to develop. Small footprint as a service separated from the GUI which is only running during configuration, uploading result, etc.
I have a lot of ideas with this. But I'm not a PPC developer. I have some experience in desktop application development so I might help some desperate programmers with a basic specification and design if needed.

Idea is absolutely useless, imho.
Too many variables.
I am using soft i've added to rom to FEEL difference between roms, checking:
- overall speed in real life conditions,
- doc file reading test(ebook reader and word),
- emulators test(cpu and gfx speed test),
- overall GUI speed,
- cam performance differencies,
- vid playback differencies,
- battery behaviour in similar conditions,
- mem drain after launching/using exactly same set of soft(interesting - mem drain is always related to phone subsystem),
- some synthetic tests related to gapi, gdi etc(BUT NEVER SPB bench, that program is ridiculous!),
- filetypes read check(to test associations/codecs).
And you know what..i haven't had single wm crash, batt drain or weak performance(cpu,batt) for 4 years, always used best base available(funny thing is TO FIND such base...many builds are needed..), tweaked to the max, these tests always worked for me, all weak/problematic builds ALWAYS showed potential problems/weaknesses after such test set.
First thing is to know your device, feel it(let's say).
I think that ONE program to measure these:
MTBF (Mean time between failures) or between soft/hard reset
- Average and low high levels of RAM usage
- Average CPU levels, Net usage, etc.
- Device Manufacturer, Type,
- Device OS, ROM, ROM version
Click to expand...
Click to collapse
is just not good idea - vide spb benchmark - results ARE NOT reliable at all(to be honest - that soft is BULL****).
I assume it is just because it is ONE program(and it serves salary, not REAL benching), such thing has nothing to reallife usage schema.
sry for my 2 cents.
upd:
MTBF (Mean time between failures) or between soft/hard reset
Click to expand...
Click to collapse
this is seriously ridiculous - HOW can one test something like that, LOL?

pupakota said:
this is seriously ridiculous - HOW can one test something like that, LOL?
Click to expand...
Click to collapse
Well not that much ridiculous I think! In server world one important measure is availability which is primary based on MTBF. Supposing that an ideal PPC never needs to be soft/hard reseted an average measure of uptime of your ROM is an approximate of stability. Statistics I mean.
Averaging thousands of results of all previously cooked ROMS stability of device is measured which can be a valuable feedback to the manufacturer.
(I think I think in wide usually and open as well. Probably my nickname is producing a lot of negative feedback to my ideas. Maybe I should test this more. )

cina said:
(I think I think in wide usually and open as well. Probably my nickname is producing a lot of negative feedback to my ideas. Maybe I should test this more. )
Click to expand...
Click to collapse
Ohh, do not take it personally, please...
Averaging thousands of results of all previously cooked ROMS stability of device is measured which can be a valuable feedback to the manufacturer.
Click to expand...
Click to collapse
Do You think they WOULD CARE? It's all about salary, nothing more.
---
Notice, that NOBODY is using stock roms, too(and it is quite clear, there's reason for that ).
It may be interesting - reporting cooked roms performance to...stock rom manufacturer

pupakota said:
Ohh, do not take it personally, please...
Click to expand...
Click to collapse
Paranoid a bit I am. Anyway thx for the encouragement.
pupakota said:
Do You think they WOULD CARE? It's all about salary, nothing more.
---
Notice, that NOBODY is using stock roms, too(and it is quite clear, there's reason for that ).
It may be interesting - reporting cooked roms performance to...stock rom manufacturer
Click to expand...
Click to collapse
I know everything is driven by money. Even in healthcare where I currently work.
I don't want to repeat myself. But the basic idea was to help end users choose the ROM that best suits their needs. And to help chefs with feedback on their jobs.
Parallel with medical work all doctors need feedback about their patients to achieve better level of practice. A chef should learn from data collected from end-users and enhance their ROM development.
I understand that a lot of you cook for themselves and publish the result (one time cookers or beginners). But there are big names of cookers with huge experience working hard reading the posts about their ROMS and trying to debug based on that. Wouldn't it be easier to get collected data on ROM performance/stability, bug reports, SW incompatiblity, etc. in an organized way?
Anyway you said that
pupakota said:
And you know what..i haven't had single wm crash, batt drain or weak performance(cpu,batt) for 4 years, always used best base available
Click to expand...
Click to collapse
How do you know? Probably you are a lucky one that got an exceptional stable hardware, a battery with no weak cells and a wireless chip with no misaligned molecule in its layers. Others probably have weak hardware, SW from other source that you have never tested. Are you quite sure that your ROM is prepared for "all" situation? Probably not and no one can be sure about that. (And do not take it personal). "Perfection cannot be reached but we should try it hard." - source unknown.
So literally I propose a software that measure some performance/stability/compatiblity issues of cooked ROMs and I've just listed my ideas. Anyone who will develop a software like this will add its own ideas and probably suppress/emphasize some of mine. I intended just to inspire developers for such a solution. I didn't want to give a clear solution anyway but I offered some help with a work like that.
Best regards,
Cina.

Allright, good luck, really...
Paranoid a bit I am.
Click to expand...
Click to collapse
Me too, mate, me too
I understand that a lot of you cook for themselves and publish the result (one time cookers or beginners).
Click to expand...
Click to collapse
btw i am not beginner. i stopped making public roms 2 yrs ago.
How do you know?
Click to expand...
Click to collapse
..because i can see it.
my softpack was tuned for almost 2 yrs, practically every single apps' oem is made by me, every single app is reconfed by me.
my methods for getting optimal os base were tuned for almost 5 yrs(and regardless of base, builds are always made with same, OLD methods).
zero HTC soft inside. zero useless soft inside. zero useless dlls, zero useless reg entries. bases with ANY kind of problem are thrown out and not used by me.
i do not need any external info from anyone to get optimal results. strict methods have very important feature: elimination of sudden misbehaviours, unknown problems, so only problems with any of: performance, batt,whatever, may come from base then.
That's all.
i do not know anything about others' point of view on external performance/etc. data ideas, but it may be hard to believe that good cooks are not having similar ways. You know, i see that someone tells: "That base is good", allright, 20 minutes later i have ready rom, so it's quite fast way to check, if it is good base, then practical subsystems tests in reallife verificate REAL usability. btw hard to imagine such build list, if we cannot have EVEN clear com 2,3,5 builds list, lol.
sorry for LQ english(or engrish..).
"Perfection cannot be reached but we should try it hard."
Click to expand...
Click to collapse
So true...

Thanx. And I appreciate your posts. Really.
pupakota said:
btw i am not beginner.
Click to expand...
Click to collapse
I've already got that.

Radio update

hi guys, on my Desire S (s-off with Rev), i've updated to pre-rooted rom 2.10.401.5 but i'm still with the old radio (20.28I.30.085), no bugs, no issues but I would like to update to the "correct" radio
here are the questions:
- have i to format&clean cache and partitions?
- would i have any advantages with the new radio?
- is it real that the 20.4801.xx radio has some battery drain's issue and so it's better to use 20.48.30 radio?

To answer some of your questions:
You don't have to format anything, although wiping your cache is recommended, because not doing it could lead to a bootloop after the radio is updated.
Strictly speaking, any advantages gained by changing a radio is probably only minimal. Some report better battery life, better reception, while most (me included) don't notice any difference. The opposite can happen, a friend of mine updated to a newer radio and it broke his wireless for good, so he had to revert.
I don't know about any battery issues, since I've not used that particular radio, but the general rule of thumb is, if you don't have any real problems with your current radio, there shouldn't be any reason to change it.
That's my 2 cents anyway, hope someone more knowledgeable in these matters can provide more info

I'm running he 20.4801 radio and actuLly find my battery life has improved over he 20.48 one.
Sent from my HTC Desire S using XDA App

excuse me but didn't you say that you've had battery drain with 20.4801 and so you tryed the older 20.48.30?

[Q] can't decide on a custom [NS4G] ROM & Kernel

I'm sorry about the long post if you want to get straight to my question, skip the first paragraph
I was avoiding this because it is a fairly noob question set (and I've seen a history of new members on XDA being berated for questions that could have been answered by any amount of research and I'm unsure whether my question set will fall into that category), but I just can't do anymore research since most information I'm finding is not in one place and I can't seem to find a full feature list for any of the ROMs and Kernels I research and look into, and on top of that there are SOOO many.... I'm about to pull my hair out of my head and my skull along with it, and every search engine I use is contemplating homicide (google has divorced me and is planning my murder for the life insurance money, and duck-duck-go is biting my heels with its bill) and firefox is planning a suicide bombing taking the 50 or more tabs with it along with my RAM, and I'm not terribly sure any of those actions aren't justified (and also, as you can probably tell, I'm going NUTS!). Just the amount of information and the amount of digging I have to do to find a single answer for the MANY questions I have regarding these ROMs and Kernels is staggering (I remember having similar problems searching to find the right linux distribution for me, but it wasn't this hard and after 2 or more weeks of searching, I didn't find myself not having any substantial answer, nor did it actually take two weeks)
anyways, enough with the crazy intro to the question
My current phone is a Nexus S 4g (sprint) currently running the stock ROM and Kernel, gingerbread 2.3.7 (build GWK74). I have it rooted and I have clockwork mod recovery flashed as well as ROM manager installed. I'm looking for ROM and Kernel recommendations (and combinations, I want to make sure they're compatible) as well as reasons why they might fit my needs
I need a ROM and Kernel that:
1. Won't reduce any of the current features I have on the Stock ROM/Kernel I have (though I don't use NFC so if google wallet isn't applicable, that's not a loss)
2. Will allow more steps in frequencies on my CPU (so CPUtuner won't tell me it can only go between 100Mhz and 1Ghz when I attempt to manually change the frequency, I can get one governor to get me 400mhz, but that only adds one more step to the 2 current steps, and performance and powersave governors don't work with the stock kernel, not that it's a big deal, I prefer conservative and ondemand)
3. will allow voodoo control & voodoo color (or any other feature that might be useful, though BLN isn't a big deal to me)
4. Has better battery life (while in use, use being things similar to internet browsing) than stock ROM/Kernel (so UI flare isn't completely necessary, and underclocking and/or undervolting would be great, as long as it doesn't sacrifice speed)
5. The UI should be less jittery than I'm seeing the stock react half the time (though that might be an effect of the CPU tuner)
6. I would like overclocking (however if that interferes with battery life, then I can live without it as long as it doesn't make the speed worse than stock)
7. this coincides with #1, but I think it should be said anyways: I don't want any connectivity (besides maybe NFC) to be affected adversely, so I want 4g, 3g (given), wifi, tethering, etc...
a few questions I have that I can't seem to clear up:
1. I'm beginning to develop software for android, so I'm wondering if any ROM and/or Kernel will affect ADB or any connection to my PC at all
2. What advantages do CM7.1 nightlies have over the CM7.1 stable, and any disadvantages (because I would prefer stable unless there's something on the nightlies I might want)
3. And any advantages ICS ports might have to anything listed above? and compatible kernels?
well, I have done some research, and the two ROMs I'm currently considering are Oxygen and CM7.1 (stable). I like Oxygen because it's a barebones rom with a few extra features that (from what I've seen thus far) don't interfere with performance or battery life. I like CM7.1 because it seems to be fairly quick and has a good feature set.
now I know that the performance might be more affected by the kernel than the ROM, so the kernels I've been most interested in are Netarchy and Trinity. Netarchy has decent speeds (though I'm unsure of its effect on battery life) and has a great list of features (such as voodoo control). Trinity is fast (depending on which version, I was debating on the overclocked version that doesn't go to the highest clock setting and the undervolted version which stayed at 1ghz but had great powersaving) because of its speed and/or powersaving, but I'm unsure of all of the features it has)
I had read that CM has its own kernel, but I can't find any substantial evidence to it besides a few short forum posts on various forums. I can't find anything on the CM site that backs up those claims (I could have just missed it though)
I was considering MIUI but I had heard that it had some translation problems from chinese into english and I'm not sure if you can get the text to read from left to right (and be alligned that way). Not sure if that has been fixed and if the features on there are necessary and/or make it difficult to use
I'm asking here because I'm sure I've barely scratched the surface on all of the ROMs and Kernels that might be helpful to me (and hope to get info from more knowledgeable people)
I have been referring to this thread
http://forum.xda-developers.com/showthread.php?t=1067813
I'm sure somethings I want aren't possible or if they are, there's negligible gain (I'm starting to thing that about battery life with the more I read)
once again, I apologize for the extremely long post, as you can tell I'm verbose (as it's really the only way I know how to get my point across)
if you need further information, feel free to ask. If any information needs to be cut off (especially if this needs to be cut shorter) let me know

I hate to do this but
BUMP
my main problem with this is that most of these roms and kernels seem to do the same thing but all have different problems
I've also found that some versions are more buggy then others which has thrown yet another curve ball into my research (not as bad as ICS but bad enough). I should have expected it but it's just one more thing to go digging for
an answer at all would be nice, other than just the views with no post. Even if the next person's answer is "this is stupid" or something of the like
even that would help me believe it or not

Honestly, your answer is the same one everyone else gets. Try them out and see. Most of the kernels out there should work with any of the ROMs, even the stock ROM. Personally, I have had no real issues with any ROM/kernel combo I have tried. I use CM because I am so used to the features they add and I dislike the stock GB theme. I'm using the last nightly cm7 had because there was something they didn't have in the stable but I don't recall what that was. But most any ROM or kernel you get for gB is likely done being developed for. The combination in my signature serves me very well. A lot of people do like oxygen. I just missed cm too much. Most of the kernels should allow for all of the wants you have.
I also ran cm9 with the glados kernel and honestly, it ran perfect for me. My only issue was with a few apps i use not wanting to cooperate.
Sent from my Nexus S 4G running CM7/franco.Kernel
Sent from my Nexus S 4G running CM7/franco.Kernel

alright thanks (which the button did for me)
I understand that (and some threads I looked over had answers like that, so I figured someone might say something along the lines of "try it out") I was mostly looking for input from past users about some ROM or kernel
I just don't want to end up with a broken phone before I leave for a week or two (to a rural area for a couple of days)
thanks for the answer, all I really need to know now is have there been any problems with any of them running ADB or transferring files from PC to phone?
EDIT: well I'm going to continue trying to get android SDK working on my linux OS, and I'm going to install and run a few ROMs and Kernels
ROMs I'm going to try: CM7.1 Stable, Oxygen, CM9
Kernels: Netarchy, Trinity, matri1x, and glados (with CM9)

[Q] which is responsible for GPS signal Radio or Kernel?

Hi everyone
When I had the GB Arabic rom the gps signal was pretty good, and especially when i used the sports-tracker app for my bike tracking. When i updated to ICS the tracking was bad, the time interval of gps status opened to 3times longer, so the tracking is quite inaccurate, especially in highspeed bike routes.(<20km/h). So i trying to understand what's going on...i tried quite a few apps for tracking, and in different roms but the results are the same. I wonder what is the problem? is the kernel or the radio?

andrewschumi said:
Hi everyone
When I had the GB Arabic rom the gps signal was pretty good, and especially when i used the sports-tracker app for my bike tracking. When i updated to ICS the tracking was bad, the time interval of gps status opened to 3times longer, so the tracking is quite inaccurate, especially in highspeed bike routes.(<20km/h). So i trying to understand what's going on...i tried quite a few apps for tracking, and in different roms but the results are the same. I wonder what is the problem? is the kernel or the radio?
Click to expand...
Click to collapse
All signals (Data, WiFi and GPS...) are handled by the radio firmware. In your case, I would recommend that you downgrade your radio to the previous version and it will be back to normal, I guess, or at least back to the way it was.

That's what happens when you don't search - you get answers from people who don't know themselves and also mislead others.
For 100000th time:
The only thing that is governed by "radio" (baseband) - is cellular network, voice and data. All the rest is in the kernel. That includes WiFi, Bluetooth, GPS, NFC, and what not.

Where am I misleading him ? Sorry, but if i'm mistaken, I was previously misled by this sticky thread : http://forum.xda-developers.com/showthread.php?p=21856647
Of course, kernel has one responsibility in signal handling (even with baseband) but radio contains the firmware to the physical signal processing which is then handled to the kernel. In his case, it looked more like a radio problem but maybe I'm wrong as I'm pretty new to Android !
Sent from my HTC Saga using xda app-developers app

Indeed this thread is misleading, and it has probably mislead you among many others.
I've posted in this thread, hopefully this glossary will be updated.
Radio doesn't contain anything. The devices that aren't baseband-related aren't connected to it, they don't use the same HW, nothing. Their signals don't go through "radio", aren't processed by it, and aren't involved in its functionality. In fact, in most/all phones these devices (WiFi, GPS etc) are external modules that can be independent of the main chipset/SoC.