Related
So i decided i wanted the new radio 3.39.10 so i flashed the leaked sprint rom. Didn't have enough time so I just kept it on my phone for a few days. One thing i noticed with this rom was everything was QUICK. Even icontact was smooth with no lagging or jittery scrolling. I also noticed memory consumption over a days time was very minimal. I would not be under 20mb free after an entire day.
That said, I've always liked dcd's roms and they always seemed faster than sprint roms. So i decided to flash to his newest 3.1.6. At first boot I had 25mb free compared to 22mb free with sprints. That was a plus, but i also noticed with the same applications installed on both that icontact was not smooth on scrolling anymore and my memory usage throughout the day would drop under 20mb easily.
Is it just me or does it seem like the sprint 3.49 rom has graphics acceleration and better memory management?
It's not just you..
everything runs faster on 3.49. Apps respond quicker and fewer hang ups and lock ups as well...
theonetruecoco said:
It's not just you..
everything runs faster on 3.49. Apps respond quicker and fewer hang ups and lock ups as well...
Click to expand...
Click to collapse
HMMM
Can someone comfirm this?
do some research?
Wow....just wow...
For Test Not For Sale
I installed the leaked Sprint ROM, and I did not have time to test it because I like DCD ROMS, so I tried 3.1.6, but it was not a good experience for me. I kept loosing and gaining signals, at some points it will not get the signal at all.
Till the day it just did not, and all my contacts were erased and my soft keys stopped working. So I reverted back to 3.04 which for me has been the most stable for me, with NO PROBLEM.
But please I have a problem, ever since I tried that Leaked Rom, and Flashed back to DCD 3.0.4, I get the message "FOR TEST NOT FOR SALE" at boot up. How do I get this message off please. I hate seeing that. I have flashed 3 times and it is still there
This thread should be closed
Damionix said:
I installed the leaked Sprint ROM, and I did not have time to test it because I like DCD ROMS, so I tried 3.1.6, but it was not a good experience for me. I kept loosing and gaining signals, at some points it will not get the signal at all.
Till the day it just did not, and all my contacts were erased and my soft keys stopped working. So I reverted back to 3.04 which for me has been the most stable for me, with NO PROBLEM.
But please I have a problem, ever since I tried that Leaked Rom, and Flashed back to DCD 3.0.4, I get the message "FOR TEST NOT FOR SALE" at boot up. How do I get this message off please. I hate seeing that. I have flashed 3 times and it is still there
Click to expand...
Click to collapse
Need to change bootsplash images
http://forum.xda-developers.com/showthread.php?t=399925
gc14 said:
This thread should be closed
Click to expand...
Click to collapse
Why? Is it no longer ok to compare roms?
ScottC said:
Why? Is it no longer ok to compare roms?
Click to expand...
Click to collapse
I'll chime in here too
The newest Sprint rom does seem much faster, I'm not sure if there is a pool size diff or what, but they take about the same ammount of time to boot up, and give or take a meg or two, about the same free mem.. The Sprint rom has a bunch of ugly sprint crap and themes(easily changed) but there is something to be said with having a nice new clean rom. Unfortunatly, I wouldn't use the 3.1.6, it seems to have too many issues with cell sig.... I was happiest on a rom called "________ Sexier Rom" But it had issues w/ AS. So right now, I'm sitting with the Sprint rom again.
You guys never cease to amaze me...
I don't know what probs you guys are having with 3.1.6. but everything works fine for me that sprint rom don't have no pizzaz!
gc14.....add some insight to this if you do not think its true. I'm going by actual usage though and have yet to have a rom as fast as the new sprint one.
gc14.....add some insight to this if you do not think its true. I'm going by actual usage though and have yet to have a rom as fast as the new sprint one.
Click to expand...
Click to collapse
This thread should be closed because everything said in it is moot. Since 3.1.1, these roms have been based off 3.49 and cleaned. Any differences are simply placebo.
well someone's acting a bit smug, aren't they.
gc14, many things go into DCD building a custom rom, often much more than just "cleaning up" a leaked rom. He's been in there in the XIP tinkering about which can cause night and day differences as far as performance and free memory from the "stock" leaked Sprint rom.
I'm not agreeing with anyone here (I haven't compared the two roms, right now testing some of no2chem's direct draw from the diamond support), however I felt the need to point out that your comments are neither helpful nor properly informed.
Unless you've conducted a test and posted your own thread about it that we don't know about, I'd write off your comments as mere speculation.
Someone asked for my insight...I gave it to them, period.
I know exactly what goes into building a custom rom. I didn't feel the need to go into all of it in this thread. As far as "tinkering in the XIP" goes, well, we'll just leave it at that.
Don't ask for me to post what I think, then get all bent out of shape when I post the truth. I won't say anything else about it, though trust me, my "speculation" isn't coming from nowhere and is very well informed.
gc14 said:
Someone asked for my insight...I gave it to them, period.
Click to expand...
Click to collapse
Actually, you were technically asked to explain your cryptic condescending one liners.
You started with "You never cease to amaze me" and "This thread should be closed", without any explanation as if this was the memory leak, bluetooth, or some other bug that already have a million threads dedicated to it.
These are legitimate concerns that whether are placebo or not, deserve to be discussed and analyzed if people are noticing it.
Don't ask for me to post what I think, then get all bent out of shape when I post the truth. I won't say anything else about it, though trust me, my "speculation" isn't coming from nowhere and is very well informed.
Click to expand...
Click to collapse
Once again, you sort of forced them to ask what you think by posting usless condescending drivel. Don't be a jerk and then get bent out of shape when its pointed out publicly.
I know exactly what goes into building a custom rom. I didn't feel the need to go into all of it in this thread.
Click to expand...
Click to collapse
Really? Because if you're saying that nothing has changed from 3.1.1, I really don't think you do. Do you even know what the XIP is, or what changing components into modules means?
I haven't posted in XDA much lately, so I'll give you the benefit of thinking I'm a n00b. Since it appears we haven't met, I'll assume you also didn't know that dcd and I go back to before he was releasing roms, and we've kept in touch behind the scenes, often part of a group that gets to test and debug before he releases new ones. Dcd has told me what he's done to these releases, and I can honestly say that he's changed it enough to barely resemble the leaked rom, far less match its performance verbatim.
Your comments are not only baseless, but juvenile.
I recommend that you control your sarcastic tone and don't post unless it is somehow constructive to the thread. Otherwise, you're going to piss off some people who won't want to help you when the time comes.
As far as whether or not this is true (dcd's being slower than leaked "stock"), I don't know since I haven't performed any tests. It is possible that something he's tweaked to free up memory has effected performance elsewhere in the rom (similar things have happened in earlier roms). The drivers should be similar, however, so its most likely not an acceleration issue.
Dishe said:
I haven't posted in XDA much lately, so I'll give you the benefit of thinking I'm a n00b. Since it appears we haven't met, I'll assume you also didn't know that dcd and I go back...
Click to expand...
Click to collapse
The greatly ironic thing is, Dishe, you not knowing the background and direct involvement of the other you are attempting to knock down.
Dishe, I strongly suggest you to avoid a personal pissing fest with the posturing of you being better than another.
If you feel differently about a position then stick to the core of the topic rather than devolve into a battle of egos and calling another member a "jerk.".
....just my 2 cents.
..but to add, I knew exactly what GC was inferring with his comment on the previous page.
Really? Because if you're saying that nothing has changed from 3.1.1, I really don't think you do. Do you even know what the XIP is, or what changing components into modules means?
Click to expand...
Click to collapse
If I didn't know what the XIP is, or what modules were, I wouldn't have said I know what goes into building a custom rom now would I?
I also never said that nothing has changed from 3.1.1.
I haven't posted in XDA much lately, so I'll give you the benefit of thinking I'm a n00b. Since it appears we haven't met, I'll assume you also didn't know that dcd and I go back to before he was releasing roms, and we've kept in touch behind the scenes, often part of a group that gets to test and debug before he releases new ones.
Click to expand...
Click to collapse
I never once thought you were a n00b, nor questioned your relationship with dcd. I'll give YOU the benefit of thinking I don't know what I'm talking about. I know all about the group, being part of it and all, hence how I know exactly what has been changed and what hasn't, as I personally tested 3.1.2, 3, 4, 5 and 6.
Dcd has told me what he's done to these releases, and I can honestly say that he's changed it enough to barely resemble the leaked rom, far less match its performance verbatim.
Your comments are not only baseless, but juvenile.
Click to expand...
Click to collapse
I wouldn't say barely resemble the leaked rom.
However, I can say that my comments are not baseless.
Key, I agree 100%
setlle down
there could be a slight difference due to cache sizes. people wanted more free ram, so i reduced cache. this reduces speed (but i didnt think it was noticable personally)
i did benchmark the 3.35 oemxipkernel vs 3.49 and found that 3.35 was actually a tiny bit faster, so i'm still using it.
there could be a slight difference due to cache sizes. people wanted more free ram, so i reduced cache. this reduces speed (but i didnt think it was noticable personally)
Click to expand...
Click to collapse
Yeah, that was the first question you asked me during testing, whether or not speed was reduced due to the cache changes. I didn't notice any difference either.
32M at boot I am running numerous apps and no problems......smooth and fast......I had 7 apps open at once and it ran them no problem....Skyfire, messaging, etc.......I have TL loaded and still sit at 25-26M....this is by far the best ROM I have run and it is not finished yet.....the camera is not loaded until NO2Chem finishes working on it....if your looking for memory....this is for you!!!!!
is the bluetooth working on it? also, what is the link for it?
edit:
he has a fix for bluetooth, and here is the link. you must donate to download.
http://www.nuerom.com/BlogEngine/
Sweet... I will wait till Someone finishes beta testing right now the release is only for Sprint Users and not for Verizon users.... I am looking foward when they have a verizon release.
Can you upload the newest No2chem rom, please?
urcboss07 said:
Can you upload the newest No2chem rom, please?
Click to expand...
Click to collapse
lol...no....he said finals will be available for all, but beta builds for those who donate.....if you really want to try it, give him a buck. for all he has done for this device...people should really donate....
I just went up there and only see 6096-3pre1. Is that the rom you are talking about. Also,is it true these will work on Sprint only?
Donate, it is well worth it. Even if its only a small amount, it helps him out alot. and 3pre1 is the latest release. it is a very very stripped down version of wm but it works wonderfully. I can actually do stuff on my mogul now. Biggest noticable loss is no more camera, but he is working on that. IMO, best rom out there right now. Hands down. worth any penny in donations. I plan on donating more when i have the money to
rsohne said:
I just went up there and only see 6096-3pre1. Is that the rom you are talking about. Also,is it true these will work on Sprint only?
Click to expand...
Click to collapse
works on my verizon got my internet and my vzw stuff
its an impressive beta release but no nuetools *sniffs*
just installed this. the screen switch is REALLY quick. my jawbone works nicely as well.
gmaps/voice command are fast too.
I have Mogul/2.47/3.42.50 & 2.04_003 w/ 60711
I donated, downloaded, and flashed. It's got a lot of memory available, but it's still buggy.
I went back to dcd 3.2.6, which also has good memory and is much less buggy with a working camera.
indagroove said:
I donated, downloaded, and flashed. It's got a lot of memory available, but it's still buggy.
I went back to dcd 3.2.6, which also has good memory and is much less buggy with a working camera.
Click to expand...
Click to collapse
Can you elaborate as to what exactly was buggy?
indagroove said:
I donated, downloaded, and flashed. It's got a lot of memory available, but it's still buggy.
I went back to dcd 3.2.6, which also has good memory and is much less buggy with a working camera.
Click to expand...
Click to collapse
What is buggy? I have mine loaded up with apps and have no issues at all...I had a scrolling issue where it kept scrolling on its own once....that was I first installed everything which was much earlier in the day.....been running 8-10 hours with no more issues at all.....
I flashed preview 1 last night, pulled out battery, put it back in, loaded my apps, and it ran like sh*t all day today. Great memory but very slow, buggy, half of my programs didn't work, and the battery life was terrible.
Since everyone else seemed to be having a grand time with it, I figured it was my error, and of course it was.
All it took was another hard reset, reinstall, now it runs like a charm
I've always heard people talk about these complex post-flashing rituals, but I figured it wasn't necessary. Well i guess it is a good idea to pull the battery, AND hard reset after a flash after all.
flyers2114 said:
What is buggy? I have mine loaded up with apps and have no issues at all...I had a scrolling issue where it kept scrolling on its own once....that was I first installed everything which was much earlier in the day.....been running 8-10 hours with no more issues at all.....
Click to expand...
Click to collapse
The on-screen keyboard is buggy, you can't see the bottom row of characters.
I think enlarge start menu caused some problems with weirdness in the start menu.
I'm not a fan of the stock dialer, and when I tried to cab install the vogue dialer, the icon for call history was transparent to the today screen.
It seemed to run slower than dcd's rom after I added all my usual programs, even though I had more ram available.
I did not build from the kitchen, just added cabs to the pre-build, so maybe a kitchen build would be more stable. It could also be some non-compatable program that added overall bugginess.
Obviously no camera is kind of a bummer, even though i don't really use the camera all that much anyways.
Overall, I'd say it's a big step forward, and is groundbreaking in some ways. However, I still feel that today, dcd 3.2.6 is overall a more solid rom.
Sprint Users Only? Not really
Per No2Chem, the flash-ready rom is for Sprint. But the kitchen allows you to choose any carrier. I built mine from the kitchen. It took a little time to figure out how to use the kitchen and I can explain if someone needs helps.
Adjust OOM...?
Does anyone know what the 2 "Adjust OOM" options do in the nueROM3 kitchen?
I tried to find answers before posting but was unsuccessful. I just figured since the kitchen and rom itself were so stripped down, that No2Chem would not have made it a point to include them if they were useless, so yesterday I just checked them both and my phone seems fine so far...
Also - I tried posting this question on http://www.nuerom.com but when I hit "save comment" it just sits there and does not actually submit my post. Maybe I'm not signed there? is the login different than the donator login?
indagroove said:
The on-screen keyboard is buggy, you can't see the bottom row of characters.
I think enlarge start menu caused some problems with weirdness in the start menu.
I'm not a fan of the stock dialer, and when I tried to cab install the vogue dialer, the icon for call history was transparent to the today screen.
It seemed to run slower than dcd's rom after I added all my usual programs, even though I had more ram available.
I did not build from the kitchen, just added cabs to the pre-build, so maybe a kitchen build would be more stable. It could also be some non-compatable program that added overall bugginess.
Obviously no camera is kind of a bummer, even though i don't really use the camera all that much anyways.
Overall, I'd say it's a big step forward, and is groundbreaking in some ways. However, I still feel that today, dcd 3.2.6 is overall a more solid rom.
Click to expand...
Click to collapse
1...on screen keyboard issue yes...
2 I am runnning Quick menu
3 I am running the Minimal dialer with no probs...
4. In my opinion it is the fatest rom I have used outside of JD's ROM
5. I added all of my apps and regedits through SASHAMI......and added a few OEM's through NuePackage installer.....
6 Camera is an ssue but he is working on that and I knew there was no camera before flashing....I know no camera is a deal breaker for now.....
It is a pre-release but I am sure it will all be working fine when the final build is done....but mine seems to be running fine really....
I am running my setup with WAD and WA3 as startup, usually always a slow go on my titan. I boot up with 27+mb of memory. I set my pagepool at 10 when i made the rom and am very happy. pre0 was a deal breaker for me cause he didn't have working bluetooth. But now that its in the rom again, i couldn't be happier.
Cobaltikus said:
Does anyone know what the 2 "Adjust OOM" options do in the nueROM3 kitchen?
I tried to find answers before posting but was unsuccessful. I just figured since the kitchen and rom itself were so stripped down, that No2Chem would not have made it a point to include them if they were useless, so yesterday I just checked them both and my phone seems fine so far...
Click to expand...
Click to collapse
It has to do with the "Out Of Memory" in windows mobile. (see here http://msdn.microsoft.com/en-us/library/ms911907.aspx) Changing that basically adjust the way WinMo handles OOM's. By lowering the threshold, WinMo doesn't close down apps as eagerly as normal.
-edit-
I also must add that having the extra RAM makes this phone an entirely different beast for me. iGO8 and Opera Mobile 9.5 caused some issues before due to how RAM hungry they are. Now, they are not a problem. But not having the camera is kind of a bummer, and the keyboard is horrible . But I will continue testing because this has MAJOR potential
Cobaltikus said:
Per No2Chem, the flash-ready rom is for Sprint. But the kitchen allows you to choose any carrier. I built mine from the kitchen. It took a little time to figure out how to use the kitchen and I can explain if someone needs helps.
Click to expand...
Click to collapse
I would love to try it - please do explain or pm me!
I always want newer and better. Last week I upgraded from dcd's 3.2.6 to 4.1.2. Much faster, better memory, speedy gps locks, and no crashes yet.
I run a few commercial medical reference programs that are a major hassle to load and activate, so it is a pain to keep flashing my phone.
Can anyone comment between how well the 6.5's work vs. dcd 4.1.2
It's a very different animal.
First and foremost, the Today Screen has been completely redone in the default Titanium screen. I'm sure you've seen it around. You can still revert back to the old Today screen with a simple setting adjustment in the Settings Menu.
Secondly, nearly everything features finger friendly scrolling. It's built in with no real need for additional items such as FTouchFLO.
Third, the start menu has been redone to make it look more contemporary. Some people like it, some don't. You can adjust it to your liking by replacing various files.
Fourth, a programmer/PPC junkie going by no2chem introduced something in his 6.1 ROMs called nueKernel which is being implemented into nearly every 6.5 ROM. It allows you to enable or disable the camera temporarily to add more available RAM. Because of this, it's possible to have more free available RAM than you've most likely seen before on the Titan. For example, my ROM (and Ryan's, and most other current 6.5 ROMs) will boot with 25+ meg free.
Fifth, please note that those are most superficial UI adjustments. They are improving things under the hood, too, to make the OS better.
Your best way to compare is by flashing. If you like 6.5, stick with it. If you don't, there are plenty of fantastic 6.1 ROMs to choose from.
if its speed what you want then stay with dcd. no 6.5 has been able to come close to dcd.
on the other hand like btonetbone said a different animal and slower no matter the tweaking.
GeLopez said:
if its speed what you want then stay with dcd. no 6.5 has been able to come close to dcd.
on the other hand like btonetbone said a different animal and slower no matter the tweaking.
Click to expand...
Click to collapse
I won't argue with this because I don't have benchmarks. DCD's ROMs are extremely fast; I used them all the up through 3.3.something and loved them.
But 6.5 isn't a hog, either. It runs very fast and snappy on my phone, and I have very little complaints regarding speed. Please don't take the above comments as saying the 6.5 ROMs are slow.
compared to dcd 6.5 is slower. i didnt say 6.5 is slow
I'll give you my opinion......... since I played with them all.
I had been running DCD 3.3.4 for 6-8 months until about a month ago when the "tinker bug" kicked in again and I had to flash and play with new ROM's.
I first went to 6.5 ROM's by RyanMogul and a few others both here and on PPCGeeks. All of them are visually stunning, but, all of them ARE slower than ROM's running 6.1
Also, for me, free memory was an issue. 6.5 simply needs more memory than 6.1 and there isn't nothing you can do about it. 6.5 ideally should be run on phones with 128MB RAM or more.
I loved 6.5 for its looks, but, I run programs like SPB Phone Suite, Pocket Weather, Palringo, and others, often simultaneously, and that just wasnt realistic with 6.5 due to low RAM availability.
So I went back to 6.1, and to good old DCD. 4.1.2 is amazing in my opinion. It has major performance and memory management improvements over his previous ROM's. It's incredibly stable, and it IS faster than any other ROM (6.1 or 6.5) I've personally tried out.
It's given my xv6800 some more life. Until the Tour comes out and I jump onto the evil Blackberry bandwagon, 4.1.2 is it for me.
I highly recommend.
rajuabju said:
I'll give you my opinion......... since I played with them all.
I had been running DCD 3.3.4 for 6-8 months until about a month ago when the "tinker bug" kicked in again and I had to flash and play with new ROM's.
I first went to 6.5 ROM's by RyanMogul and a few others both here and on PPCGeeks. All of them are visually stunning, but, all of them ARE slower than ROM's running 6.1
Also, for me, free memory was an issue. 6.5 simply needs more memory than 6.1 and there isn't nothing you can do about it. 6.5 ideally should be run on phones with 128MB RAM or more.
I loved 6.5 for its looks, but, I run programs like SPB Phone Suite, Pocket Weather, Palringo, and others, often simultaneously, and that just wasnt realistic with 6.5 due to low RAM availability.
So I went back to 6.1, and to good old DCD. 4.1.2 is amazing in my opinion. It has major performance and memory management improvements over his previous ROM's. It's incredibly stable, and it IS faster than any other ROM (6.1 or 6.5) I've personally tried out.
It's given my xv6800 some more life. Until the Tour comes out and I jump onto the evil Blackberry bandwagon, 4.1.2 is it for me.
I highly recommend.
Click to expand...
Click to collapse
Thank you for explaining that so eloquently. I think you've just convinced me to go back to 6.1 after running 6.5 for roughly a month. 6.5 is amazing and very finger friendly, but not the OS for the Titan. Just uses too much memory, no matter what. I've tried different programs to free up RAM and keep me from soft resetting 2 or 3 times a day, but none of them really work. On 6.5 I can almost never run 2 apps at once, unless they are very small. So back to good ol DCD for me. At least until I get a new device! (touch pro maybe )
Just my 2 cents
Currently I am running Mattsm 6.5 23003b and this morning I was running 4 apps and switching between them with enough memory for all of them. I was on a website, Biblegateway, had a java application open, Go Bible by Jolon Faichney, Word 6.1 and Windows Mobile 6.5 Titanium Today (this skin allows both vertical scrolling and on some panes, horizontal movement) which I was using as the switching point to jump back and forth. I have run DCD ROMs in the past and they are great ROMs but if you want to see what is possible with your Titan follow the different developers.
Showtime7 said:
Thank you for explaining that so eloquently. I think you've just convinced me to go back to 6.1 after running 6.5 for roughly a month. 6.5 is amazing and very finger friendly, but not the OS for the Titan. Just uses too much memory, no matter what. I've tried different programs to free up RAM and keep me from soft resetting 2 or 3 times a day, but none of them really work. On 6.5 I can almost never run 2 apps at once, unless they are very small. So back to good ol DCD for me. At least until I get a new device! (touch pro maybe )
Click to expand...
Click to collapse
One thing that DCD kept on repeating with the release of 4.1.2 was that the amount of free memory was determined by what was in the ROM. So you stripped EVERYTHING out and added it later with cabs and you suddenly start with a higher amount of memory from the outset.
I'd love to see Ryan prove this by releasing his "light" rom with a required cab. I bet if the rom didn't have all the the extra ring tones and addons he includes, we'd boot to more than 17.5mb I've available in his wm7 rom.
I'm glad you mentioned you can turn off the new today screen. I'm not impressed so far. But the big thing is that my GPS is working again which it never did with DCD's last release.
BrianLayman said:
One thing that DCD kept on repeating with the release of 4.1.2 was that the amount of free memory was determined by what was in the ROM. So you stripped EVERYTHING out and added it later with cabs and you suddenly start with a higher amount of memory from the outset.
Click to expand...
Click to collapse
i think you misunderstood me, or i misspoke. free program memory should be the same whether an application is in rom, or installed post-flash.
free storage memory may be slightly higher when applications are installed via cab after flashing, because any files outside of /windows are duplicated when cooked in. however, this is the reason that most htc-written applications run from /windows, and those applications would thus would require the same storage memory whether in ROM or not.
dcd1182 said:
i think you misunderstood me, or i misspoke. free program memory should be the same whether an application is in rom, or installed post-flash.
free storage memory may be slightly higher when applications are installed via cab after flashing, because any files outside of /windows are duplicated when cooked in. however, this is the reason that most htc-written applications run from /windows, and those applications would thus would require the same storage memory whether in ROM or not.
Click to expand...
Click to collapse
I was just thinking, DCD should change his name to Optimus Prime
BrianLayman said:
One thing that DCD kept on repeating with the release of 4.1.2 was that the amount of free memory was determined by what was in the ROM. So you stripped EVERYTHING out and added it later with cabs and you suddenly start with a higher amount of memory from the outset.
I'd love to see Ryan prove this by releasing his "light" rom with a required cab. I bet if the CAB didn't have all the the extra ring tones and addons he includes, we'd boot to more than 17.5mb I've available in his wm7 rom.
I'm glad you mentioned you can turn off the new today screen. I'm not impressed so far. But the big thing is that my GPS is working again which it never did with DCD's last release.
Click to expand...
Click to collapse
Please don't mumble about me incoherently. My ROMs do not use any CABs besides 1.1 Heavy and thats 1 out of 7 ROMs. Version 1.1 Heavy installs Google maps using a cab and M2D via Auto Customization.. Otherwise there is not a single CAB involved in the any other of my ROMs flashing and booting the first time..
The ringtones are not a CAB.. They are added ingredients used while cooking a ROM in a kitchen..
Release my ROM without the required cab...??? wtf.. lol
I know I should include less ringtones but I do the best I can. I don't appreciate my work being examined with a fine tooth comb pointing out any imperfection you can find to take away from its luster..
I release several versions so if you want pretty and loaded, you get that. If you want ugly and slim, you get that too. And a few things in between. Like I said I try.
I will remove some of the ringtones next time I cook and relocate several installs to make sure they stay only in the windows directory because I know what you guys mean.
Some ppl are just dicks. I'm currently running ryans 6.5 the heavy one. He did a great job since I want 6.5 on my mogul till the TP2 comes out. I turned off most of the things I don't need like the new today screen and the camera which I hardly ever use, I'm consistently at over 25mb but I mostly use my phone to get e-mails and txt.
dcd1182 said:
i think you misunderstood me, or i misspoke. free program memory should be the same whether an application is in rom, or installed post-flash.
free storage memory may be slightly higher when applications are installed via cab after flashing, because any files outside of /windows are duplicated when cooked in. however, this is the reason that most htc-written applications run from /windows, and those applications would thus would require the same storage memory whether in ROM or not.
Click to expand...
Click to collapse
Hey who's this guy?? Glad to see your alive and well dcd.... Just another thanks for all you've done for the community....
dcd1182 said:
i think you misunderstood me, or i misspoke. free program memory should be the same whether an application is in rom, or installed post-flash. Free storage memory may be slightly higher when applications are installed via cab after flashing, because any files outside of /windows are duplicated when cooked in.
Click to expand...
Click to collapse
Ah, that could fit with what you were saying. Man, now I wish I could find the exact quote. I'd like to better understand what you were saying with this added bit of info. I've searched for about 20 minutes with no luck.
You were responding for the 20th time to someone asking why you'd only released a ROM and one that didn't have games or something in it. I read it to say that if the ROM was smaller and people installed their req software via cabs, in general, everyone would have more free program memory. Which seemed to make sense... I just carried it a little further than you meant, and assumed then that items installed to the device later didn't affect the amount of "ram" available. sigh... I miss the days the memory slider on my old e750 that allowed me to override balance between storage memory and program memory. Anyway, thanks for the additional info.
RyanMogul6800 said:
Please don't mumble about me incoherently. My ROMs do not use any CABs besides 1.1 Heavy and thats 1 out of 7 ROMs. Version 1.1 Heavy installs Google maps using a cab and M2D via Auto Customization.. Otherwise there is not a single CAB involved in the any other of my ROMs flashing and booting the first time..
The ringtones are not a CAB.. They are added ingredients used while cooking a ROM in a kitchen..
Release my ROM without the required cab...??? wtf.. lol
Click to expand...
Click to collapse
Ryan, dude, slow down a minute and read what I actually typed.
I never said anything about your current ROMS requiring CABs nor did I say that you'd released a ROM that was a missing required CAB.
I was talking about doing an experiment, making a test build, to prove a theory about memory usage. Sometimes that's what we do, we try an idea, see if it improves the situation and drop it when it doesn't pan out. Heck, I didn't even expect you to be reading this thread. So, I certainly wouldn't have been criticizing you or your work here.
What worries me more is the "Please don't mumble about me". No one said anything against you. Even if people do say stuff about your works, don't take it as a criticism about you, personally. If you keep doing that, you'll lead a miserable life as a developer.
I know releasing no-cost software on which everyone has an opinion is difficult. But if you are so uptight, so quickly, you really should step back from reading threads for a bit. This place WILL drive you nuts if you let it, but it will happen much faster if you take everything as a judgment of your worth.
RyanMogul6800 said:
I know I should include less ringtones but I do the best I can. I don't appreciate my work being examined with a fine tooth comb pointing out any imperfection you can find to take away from its luster..
Click to expand...
Click to collapse
As explained above, I've never criticized a single feature of your ROM. I mentioned 17.5 free on your heavy ROM with the wm7 extras, but I consider that darn good for your heaviest ROM. I've booted under other roms to 15 something.
And as far as "I don't appreciate my work being examined with a fine tooth comb", well... you should.
Take all the input and critiques you can. After 20 years as a programmer I know bugs happen. I'm not perfect. Making good stuff makes me proud, but I'll tell you now that I won't ever create a perfect piece of complex software on the 1st or 10th go around. If someone points out a problem, then that is a chance for my stuff to be even better, if I decide I want to fix it.
I am now running your 6.1 light version, which I think is incredible. Your roms have resolved several issues I've had with this refurb phone I am now using. And while I am extremely impressed with the level of detail you've gone to(like the fact that you've included the right codecs/dlls for tcpmp to play wma files on 6.1), you should not be surprised that I have found a nit-picky mistake and have some suggestions for you to consider.
I'd not share them here in any case, as it is off topic to this thread, and if it will hurt your feelings or honor for me to post it anywhere, I'll keep the information to myself. At least the one suggestion, will add a missing feature to your ROM, but I'll leave it up to you.
Hi,
This is just a sum up of my last two day's experience flashing my Athena.
When I got it from eBay, it hat the german WM5 installed. Though I speak German, I did not want a german Firmware, so I installed Michy's WM6.1.
I was quite happy with it, but one thing annoyed me: on the original WM5, I could scroll in IE by tilting the device and Opera worked quite well, too.
On Michy's firmware, that functionality lacked somehow.
What I never got used to, was the huge size of icon's and menu's, so I started to use RealVGA. Unfortunatly the phone dialer doesn't like it, so I had to install an alternative software for it.
Over all, the phone worked pretty OK.
Because I got the swine flue, I had some extra time on my own, specially inbetween the fevers and so I decided to try out AP40, specially in order to get the SPL35 done for future WM6.5 releases.
1) AP40
The install went through fine and I had no problems.
First thing I checked was WIFI, because of the dreaded MAC-loss, but WIFI worked straight ahead.
I finished syncing, rebuilding all links in Start Menu and was happy about the new firmware...
...until I tried to switch on WIFI again. It could see my AP's, but Athena would not connect to any.
2) WM6.5
Because I did not find any fix for that, but found a few posts of others complaining about the same problem with AP40, I moved on and installed avengerpenguin's WM6.5.
While the ROM is great and the only bug I noticed was the wrong mapping of the FUNCTION key, I discovered something else:
WM6.5 sucks!
Huge icons, in a kind of honeycomb arrangement, making you have to scroll forever until the required icon is found.
Everything slow like hell (and Athena's CPU is fast enough, I would say).
Also, the menu structure is ridiculous. Makes no sense at all.
3) Back to Michy WM6.1
At then end, I went back to the ROM I had in the beginning of this journey. Now I need to rebuild all the Start Menu links (stupid me, I deleted the backup). It's about 30-40 programs I have installed on my SD - what the heck.
Conclusions:
1) AP40 has indeed a WIFI problem besides the missing MAC. This renders AP40 pretty useless to me.
2) WM6.5 sucks big time. I hate it.
3) Not sure if I should try an official WM6.0 ROM, before restoring all links. Curious about IE supporting the tilting to scroll.
4) My next phone will be an iPhone. Yes, I said it. Here is why:
- best browser around
- has some great applications
- best touch screen around
- just works
Perhaps I am getting old, but I do feel frustrated of having to flash all these firmware and none is giving all I need. Each firmware has something great but lacks something else.
Of course it's not the cookers fault - they are doing a great job.
It rather seems that Microsoft and the Provider (not even HTC's fault), just don't seem to give a F*** to their customer's satisfaction.
Example: How can it be possible that a device as the Athena, with such a big screen, has to be put up with the same menu's like a QVGA device? It almost hurts the eye to have such big menu's and icons.
Of course, you can install RealVGA, but then half of the programs don't work properly...
I just hope the company switches provider soon and gives me the option to pay the price difference for the iPhone.
Cheers,
vma
firmware frustration
vma said:
Hi,
This is just a sum up of my last two day's experience flashing my Athena.
When I got it from eBay, it hat the german WM5 installed. Though I speak German, I did not want a german Firmware, so I installed Michy's WM6.1.
I was quite happy with it, but one thing annoyed me: on the original WM5, I could scroll in IE by tilting the device and Opera worked quite well, too.
On Michy's firmware, that functionality lacked somehow.
What I never got used to, was the huge size of icon's and menu's, so I started to use RealVGA. Unfortunatly the phone dialer doesn't like it, so I had to install an alternative software for it.
Over all, the phone worked pretty OK.
Because I got the swine flue, I had some extra time on my own, specially inbetween the fevers and so I decided to try out AP40, specially in order to get the SPL35 done for future WM6.5 releases.
1) AP40
The install went through fine and I had no problems.
First thing I checked was WIFI, because of the dreaded MAC-loss, but WIFI worked straight ahead.
I finished syncing, rebuilding all links in Start Menu and was happy about the new firmware...
...until I tried to switch on WIFI again. It could see my AP's, but Athena would not connect to any.
2) WM6.5
Because I did not find any fix for that, but found a few posts of others complaining about the same problem with AP40, I moved on and installed avengerpenguin's WM6.5.
While the ROM is great and the only bug I noticed was the wrong mapping of the FUNCTION key, I discovered something else:
WM6.5 sucks!
Huge icons, in a kind of honeycomb arrangement, making you have to scroll forever until the required icon is found.
Everything slow like hell (and Athena's CPU is fast enough, I would say).
Also, the menu structure is ridiculous. Makes no sense at all.
3) Back to Michy WM6.1
At then end, I went back to the ROM I had in the beginning of this journey. Now I need to rebuild all the Start Menu links (stupid me, I deleted the backup). It's about 30-40 programs I have installed on my SD - what the heck.
Conclusions:
1) AP40 has indeed a WIFI problem besides the missing MAC. This renders AP40 pretty useless to me.
2) WM6.5 sucks big time. I hate it.
3) Not sure if I should try an official WM6.0 ROM, before restoring all links. Curious about IE supporting the tilting to scroll.
4) My next phone will be an iPhone. Yes, I said it. Here is why:
- best browser around
- has some great applications
- best touch screen around
- just works
Perhaps I am getting old, but I do feel frustrated of having to flash all these firmware and none is giving all I need. Each firmware has something great but lacks something else.
Of course it's not the cookers fault - they are doing a great job.
It rather seems that Microsoft and the Provider (not even HTC's fault), just don't seem to give a F*** to their customer's satisfaction.
Example: How can it be possible that a device as the Athena, with such a big screen, has to be put up with the same menu's like a QVGA device? It almost hurts the eye to have such big menu's and icons.
Of course, you can install RealVGA, but then half of the programs don't work properly...
I just hope the company switches provider soon and gives me the option to pay the price difference for the iPhone.
Cheers,
vma
Click to expand...
Click to collapse
HI vma
I must say frankly, you've just expressed the conclusion I have been slowly coming to myself. I have also tried all possible roms and actually never been happy as there's always sth that doesn't work.
Perhaps it's windows mobile. I still hesitate as I'm waiting for a new athena from HTC. But perhaps Iphone is not such a bad idea.
Hi,
When I saw a first reply, I though it was to flame me for my unkind word to WM devices...
I have to admit I was a bit pissed. Afterall it took me two days of flashing, backing up, restoring backups, only to realize that the firmware I had (Michy's WM6.1) wasn't that bad.
During all that I thought I had fried my Athena - it stopped responding and it took me hald an hour to realize that the trick is to hold BOTH the camera and the communications buttons, while doing the reset.
I then reinstalled Michy's ROM again and somehow it has a bug, which must be the reason I had problems in the past: it will produce errors syncronizing.
At the end I thought that after so much efforts and me being in bed anyway, I might as well give the official WM6 from T-Mobile a try.
Well, I just finished shaping it to my desires. Took quite some time, but: tilting works, Youtube works (not inside the browser, but still it works), Opera and IE have nice renderings, allowing to zoom in and out (somehow on Michy's ROM the zoomlevel was always to big).
I think the ROM is now pretty OK. If I knew how to cook ROM's, I would cook it exactly like this.
Does this give me inner peace to take back what I said before?
No.
I am totally disappointed by WM6.5. It just sucks and is a waste of space on any screen with more than 320x200 resolution.
It is a waste on resources (our devices have faster and faster processors, yet WM seems to get less and less responsive).
The most important applications are the internet applications: wtf has IE such a big menu bar on top and bottom?
The list goes on and on and I won't even bother.
To all the cooks: I truly respect and appreciate your work. Please don't get annoyed by my postings. It is not your fault that Microsoft has been producing such a bad OS.
To all of you, who did not yet try it: pick an iPhone from someone (not the ones in the shops, specially the ones not connected to the internet) and play with it for 10 minutes... You will understand what I mean:
- you swipe the finger to scroll a page and it like flies under your finger. No resistance or lag whatsoever
- you open a webpage and it loads FAST. You can scroll it, zoom in and out and it just is so responsive
Ok. Enough crying...
Truth is: look at my signature and see that I always liked WinCE devices a lot... Shame the evolution seemed to have gone the wrong way.
Cheers,
vma
vma said:
Because I did not find any fix for that, but found a few posts of others complaining about the same problem with AP40, I moved on and installed avengerpenguin's WM6.5.
While the ROM is great and the only bug I noticed was the wrong mapping of the FUNCTION key, I discovered something else:
WM6.5 sucks!
Huge icons, in a kind of honeycomb arrangement, making you have to scroll forever until the required icon is found.
Everything slow like hell (and Athena's CPU is fast enough, I would say).
Also, the menu structure is ridiculous. Makes no sense at all.
Click to expand...
Click to collapse
Maybe I can answer some of your issues with 6.5, the function key, is close to being fixed just needs some work on the keyboard map posted by xtep in the x7510 section.
The icons/menu can be fixed to an extent, not sure how though, it is possible to get smaller icons etc 4 or 5 across but I havent had time to research it fully as yet, also I have used some 6.5 roms for my blackstone that manage to use the old 6.1 menu system.
Now the biggest possibly hardest issue is the speed, I believe that most of the issues come from the fact that we do not have a native 6.5 memory kernel for the athena, which gives an additional 2 32mb memory slots to the OS, I am no expert but I think it is possible to port a memory kernel to the athena but this exceeds my capabilities and I am yet to find someone who can do it.
This would give us the greatest increase in speed etc, whilst my roms are optimized as far as I am capable there is still a long way to go.
However with this said I do agree with you winmo 6.5 is not that fast, not as fast as it should be with a 624mhz processor. When you compare it to something like android or Iphone it really seems to show its age/limitations
for me the R0 6.1 ROM has given me the most speed of ANY ROM out yet. It also has no bugs that I can see. Mem after a reset is 70MB and I think this goes a long way to giving the most speed.
I also want to make sure I'm not misunderstood, I think all the cooks on here have done incredible things given the constraints this OS gives them and my hats off to all of you that put so much time into developing new ROMs.
One other issue I think has hampered overall speed and usefullnes is the lack of a good driver for the graphics chip in the athena. I don't think we have ever had full access to it so rendering could be greatly improved thus making the speed that much better.
mietulok said:
HI vma
I must say frankly, you've just expressed the conclusion I have been slowly coming to myself. I have also tried all possible roms and actually never been happy as there's always sth that doesn't work.
Perhaps it's windows mobile. I still hesitate as I'm waiting for a new athena from HTC. But perhaps Iphone is not such a bad idea.
Click to expand...
Click to collapse
I'm with you there. I have actually purchased a MacBook Pro to replace my old Toshiba Satellite 5105 s702 recently. Even though I installed XP (dual boot) on the MacBook Pro, I found myself using OS X on it more than XP. I plan to do the same (buy an iPhone) when my Athena dies. Micro$oft has lost control of their hardware vendors who have no interest in long term support/loyalty building and only interested in taking customers' money and run.
our dear athenas
"I am no expert but I think it is possible to port a memory kernel to the athena but this exceeds my capabilities and I am yet to find someone who can do it."
avengerpenguin,
Like sb else has written here, I also don't want to be misundersood as I have a lot of respect for all the cooks here, and especially for you as I have been following your work on win 6.5 ROM. If there were more guys here with so much enthusiasm, perhaps we wouldn't be moaning about windows mobile.
Anyway I still use a cooked rom so even with some minor bugs we can at least partly enjoy our athenas. I guess HTC has just forgotten about probably the most loyal user group - athena owners. I have had mine for almost 3 years and got used to it so much that it's a pain for me to think that there may come the time when I'll have to replace it.
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Click to expand...
Click to collapse
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
we are "stable" look at Arrrghs post below
BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes
Originally Posted By: arrrghhh
I was running this bundle for a while and in the begining I did have some issues but that's cause I didnt know crap. but now that I have learned a litle about each bundle and how they work and how to make it run better, I said good bye to windows and hello droid.
I'm testing another bundle and so far its prettty good.
THANKS TO ALL DEVS, ARRRGH PLEASE EXCUSE THOSE WHO COMPLAIN BUT DONT DO ANYTHING TO FIX THINGS. THANKS ARRGH FOR ALL YOUR WORK AND I AM SCREAMING DAMN IT!!!!!
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
It really depends, partially on usage scenarios. xdandroid FRX05/06 on RHOD300 is close to what many WinMo ROMs achieved in terms of general stability. It's actually better than the old version of Energy I was using (which hung on boot 50% of the time, but would be fine after that.) I'm using the xdandroid source tree myself as my daily phone with lots of success.
Power management issues are getting knocked down pretty fast (major focus right now for the devs, primarily being worked by WisTilt2)
RIL issues are on the way to resolution, thanks to independent efforts by highlandsun and WisTilt2. I'm personally hoping to maybe see WisTilt2 hand off his work to highlandsun so WisTilt2 can resume working the kernel PM stuff
Bluetooth is in progress - sounds like we're close, but it's lower priority. Unfortunately the Bluetooth commits and WisTilt2's latest PM work are conflicting, so there isn't a kernel that includes both the improved PM and the improved BT support. I suspect this will change in a week or two.
GPS - It's functional enough for most people, so currently is very low priority. I've done a little work here since I'm not really qualified to work some of the other stuff. Ideally the GPS will get cleaned up so it doesn't wakelock us (we have an easy workaround for that), and time/loc injection can be implemented for faster locking (This requires a significant reverse engineering effort though - Qualcomm changed the interface enough with newer gpsOne solutions that I don't think we can use the code/documentation from the cyanogenMod and AOSP GIT trees.). Lack of XTRA isn't a priority at all for those running from SD, it's a big issue for NAND though.
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
toadlife said:
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
Click to expand...
Click to collapse
I already forgot about windows. I use droid daily. it's stable enough for me
arrrghhh said:
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
Click to expand...
Click to collapse
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Click to expand...
Click to collapse
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
I'm on FRX05 with the 3/11 wistilt2 kernal and this thing is heaven. I don't get any lagging unless I run a crap ton of apps at once or try and download a ton of programs off the market at once (that would slow down any phone). I get through the day with about 40% battery still left. Bluetooth isn't completely working but I don't use that. What more are you looking for in terms of stability? Android can be even less buggy/laggy than some Winmo Cookie 2.0 ROMs in my opinion.
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
arrrghhh said:
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
Click to expand...
Click to collapse
Yeah, my wife has the HD2 and *everything* (that I know of) works.
EtherBoo said:
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1) All UI elements are large enough that I've never had a need for the stylus in Android. However, since it is a resistive touchscreen, often "fingertip" dragging isn't so hot (single-presses OK, dragging less so) - Fingernails are great for this. I'd say it's about on par with my Huawei S7 in terms of touchability.
2) 3.5mm jack is completely nonfunctional on devices that have it
Headset via ExtUSB is flaky - few people use it so it doesn't get much testing/dev attention
BT is nonfunctional right now, I'd say it's the biggest "missing" item
GPS is usable but has performance issues in terms of initial lock times. Once locked it works great. There are two issues - Ephemeride preloading (XTRA, or in terminology more familiar on the WinMo side, QuickGPS) is not implemented. Fortunately XTRA loading can be done from WinMo prior to booting Android. There's also GPS time/location injection used to "warm start" the GPS - also not implemented.
Camera is a little flaky, but there have been major strides in that in the past month
Power management is still a little flaky, but I think WisTilt2's kernel work is nearly complete
Our RIL has definite known issues, esp. on CDMA phones. WisTilt2 was working it a bit, and highlandsun has made MAJOR improvements in just the past week
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
The HD2 has a pretty close to 100% port of android... the HD2 is even starting to get it's own CM7 build... not a port, a build made specifically for it. I think it was easier porting android to the HD2, though, because there are many similar android devices that use similar hardware. Also the HD2 seemed to have a lot more devs working on the project.
I love my HD2... it's my main phone and will be for at least another 6 months. Currently running WP7 on NAND and running a CM7 build from my SD card, and even running from SD card, it runs about as well as a native android device. It's going to be hard to move on to a new phone when I'm used to being able to run both WP7 and Android.
Anyways, sorry for the HD2 talk in the Rhodium forum. I'm new in this section... just got myself a T-Mobile Touch Pro 2 to play with and use as spare phone, so I'll be around these parts more from now on.
Is cotulla still working on magldr for the rhodium? Any recent news on that. Having magldr can make the rhodium much more like a native android phone, especially if he has recovery support.
absolutely, magldr 113 is phenominal on my hd2, i'd never go back to windows again, i've been using frx06 with different highlandsun's ril and arrrghhh's kernel for a few days with verrry few problems. i can't wait to get it on nand and have a clockwork mod system
As to the HD2 - As I understand it, there seems to be far fewer variations between Snapdragon configurations as there were for MSM7k configurations.
As a result, it's a lot easier to target one of the rare non-Android Snapdragons when so many Snapdragons ran Android.
EtherBoo said:
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
7 I recommend you try them all. All of them have issues. Find one you can live with
Many people has had success with Huawei, its pretty easy to install, so I would start with that. Does not work for me though.
FRX05/06 are easy ready-to-go-bundles as well.
EtherBoo said:
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1.) I much prefer androids UI to that of winmo, stylus is needed less but I still use it occasionly . But I didn't use it much in winmo eithar as iv grown good at precise use of the touchscreen But android is still a lot less fiddly
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
3.) Great progress is being made. . . . .but atm its still reccomended to boot using HARET on sd
6.) Yes afaik the builds are rooted because root is access to /system . . .which seeing as its on the sd card it can be accesed/edited. (Btw can only onfirm for certain that root apps and exploring of root in android in neopeek builds . . . Havnt tried on an xda build as of yet)
7.)well first of all you need to decide wether you want to run a partition(neopeek) build , or a system.ext2 file (xda) build . . . . .you being new id recommend a build here on xda as setup is easier, that does leav you with less choices though but The latest FRX0- build should satify your craving for android . Arrrghhh has made a thread with the build and instructions.
Jandyman said:
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
Click to expand...
Click to collapse
I'd like to address this issue.
I think this is simply an issue with ID3v1 and v2 tags. Have you made sure both tags are populated on your music?
If it's not this issue, then I'm not sure. I've only tried streaming music, haven't tried playing it locally yet...
teemo said:
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
Click to expand...
Click to collapse
I had this problem too but you can simply fix it by downloading a keyboard app from the market (like 'Gingerbread Keyboard' or 'SwiftKey').
I am using Gingerbread Keyboard and that is working much more exactly than the standard keyboard for me.
One more questi.
Is it possibe to make the browser scroll faster. And less choppy?
Sent from my MSM using Tapatalk