Related
Project)
The Wing Linux project is happy to announce our 0.3 release! We're geared towards the development of Linux and Android on the T-Mobile Wing, HTC Herald, and HTC Atlas series of phones. This release features a much easier CAB file based installation! Simply install to Windows Mobile and you're good to go! It's also got a bunch of other goodies, like Android 1.5, fully working touchscreen / keyboard, and a better scaled display for QVGA. Previous problems with white screens on boot have been fixed!
The project is being hosted on Sourceforge at:
http://wing-linux.sf.net
The files can be gotten at:
https://sourceforge.net/project/platformdownload.php?group_id=253356
Discussion for this and future releases can be had at:
https://sourceforge.net/forum/?group_id=253356
See these threads for more info about the development leading up to this release:
Google Android for Herald and Tmobile Wing
Installable Linux Image for HTC Herald / T-Mobile Wing (UPDATED: Android Install)
Thanks to all who have helped in debugging, testing, and developing this release!
I have a question about the Virtual RAM. Does it just borrow some from the devices RAM, or does it use some of the space on the storage card as Virtual RAM?
Also does landscape work yet?
Still can't wait for Wifi and GSM! I love Android, but my contract doesn't expire for a while, so this would be awesome if it could be a viable replacement.
apreichner said:
I have a question about the Virtual RAM. Does it just borrow some from the devices RAM, or does it use some of the space on the storage card as Virtual RAM?
Also does landscape work yet?
Still can't wait for Wifi and GSM! I love Android, but my contract doesn't expire for a while, so this would be awesome if it could be a viable replacement.
Click to expand...
Click to collapse
The virtual RAM uses space on the flash card, kinda like a Windows swap file. Landscape does not yet work, but it's on our list.
We'll probably have GSM working before wifi, so keep tuned for the development releases. We're hoping to get things complete enough to be a viable replacement for WM, but we've still got a ways to go.
- d
darkstar62 said:
The virtual RAM uses space on the flash card, kinda like a Windows swap file. Landscape does not yet work, but it's on our list.
We'll probably have GSM working before wifi, so keep tuned for the development releases. We're hoping to get things complete enough to be a viable replacement for WM, but we've still got a ways to go.
- d
Click to expand...
Click to collapse
That's okay, I use GSM more than WiFi. I assume GPRS and EDGE fall into that category? Will they all come together at once, or will we get one before the other? I'm not much of a developer but I'm still trying to learn these things.
Since it's able to do use RAM from a flash card, in theory, couldn't we push our wings to 1gb of RAM on Android? Or is there some sort of limit?
I haven't been able to test it yet because I don't have a large enough flash drive.
What about overclocking? Are there any problems with overclocking through Windows Mobile and then running Android? Or has that not been really tested yet.
apreichner said:
That's okay, I use GSM more than WiFi. I assume GPRS and EDGE fall into that category? Will they all come together at once, or will we get one before the other? I'm not much of a developer but I'm still trying to learn these things.
Since it's able to do use RAM from a flash card, in theory, couldn't we push our wings to 1gb of RAM on Android? Or is there some sort of limit?
I haven't been able to test it yet because I don't have a large enough flash drive.
What about overclocking? Are there any problems with overclocking through Windows Mobile and then running Android? Or has that not been really tested yet.
Click to expand...
Click to collapse
The 64mb of RAM from the phone is still the main RAM. The swap "file" being used to get more RAM isn't very fast, so it doesn't really make it faster, it just gives it the ability to RUN programs without them being closed due to lack of memory.
There would be no point in having that much memory. As it stands, my G1 has never ran out of memory and I use a lot of third part android apps.
As far as overclocking, I would imagine it wouldn't work the normal way, as WM is kicked out when android loads and along with it the CPU controlling driver that controls the CPU speed.
ivanmmj said:
The 64mb of RAM from the phone is still the main RAM. The swap "file" being used to get more RAM isn't very fast, so it doesn't really make it faster, it just gives it the ability to RUN programs without them being closed due to lack of memory.
There would be no point in having that much memory. As it stands, my G1 has never ran out of memory and I use a lot of third part android apps.
As far as overclocking, I would imagine it wouldn't work the normal way, as WM is kicked out when android loads and along with it the CPU controlling driver that controls the CPU speed.
Click to expand...
Click to collapse
Oh so when you run Linux it isn't like a virtual machine running in Windows? It actually takes full control of the CPU and RAM. So it wouldn't make a difference if I used a more RAM/CPU hungry ROM like JustHome rather than JustStable Micro?
What about the SD card, does Android detect the rest of the data on your SD card?
apreichner said:
Oh so when you run Linux it isn't like a virtual machine running in Windows? It actually takes full control of the CPU and RAM. So it wouldn't make a difference if I used a more RAM/CPU hungry ROM like JustHome rather than JustStable Micro?
What about the SD card, does Android detect the rest of the data on your SD card?
Click to expand...
Click to collapse
That's right, Linux takes over completely. We've gotten testing from people running a wide range of ROMs, and nobody has ever had a problem. So, use what you like
As for the SD card, Linux detects and can use the entirety of the card. We haven't set up Android to be able to do that yet, but it shouldn't be hard.
- d
darkstar62 said:
That's right, Linux takes over completely. We've gotten testing from people running a wide range of ROMs, and nobody has ever had a problem. So, use what you like
As for the SD card, Linux detects and can use the entirety of the card. We haven't set up Android to be able to do that yet, but it shouldn't be hard.
- d
Click to expand...
Click to collapse
Just for curiosity sake... I realized that even if GSM worked, you couldn't really make a phone call without Sound/Microphone drivers. Does the Wizard team have anything that might help us here? I tried looking on the Sourceforge but it isn't listed under any Tasks.
apreichner said:
Just for curiosity sake... I realized that even if GSM worked, you couldn't really make a phone call without Sound/Microphone drivers. Does the Wizard team have anything that might help us here? I tried looking on the Sourceforge but it isn't listed under any Tasks.
Click to expand...
Click to collapse
There is currently a sound driver but when it was originally ported to this build, it had a problem building. I'm not sure if darkstar has had time to look at it, again, yet.
Lol it seems like I'm the only one asking questions here. Has there been any testing of this using SDHC cards? Do they work properly? I'd like to get a 4 or 8gb card soon.
apreichner said:
Lol it seems like I'm the only one asking questions here. Has there been any testing of this using SDHC cards? Do they work properly? I'd like to get a 4 or 8gb card soon.
Click to expand...
Click to collapse
Yes, it works fine with my 8GB SDHC. I am not feeling the idea that Android completely takes over my Windows Mobile. It is still too new at this point for me. Still, it's a really great job by the author. I been skimming through the chronicle thread for months and it has come a long way. From having to install Linux to a simple cab must be a lot of work. I hope this will lead somewhere great in the future. Best of luck.
apreichner said:
Lol it seems like I'm the only one asking questions here. Has there been any testing of this using SDHC cards? Do they work properly? I'd like to get a 4 or 8gb card soon.
Click to expand...
Click to collapse
I run all this stuff on a 16gb card, so I'd say no problems at all.
- d
Alright, sounds good, thanks! Can't wait to give it a try!
very good work. Big thx to all the people involved in the deveolpment.
I thougt android would never run on the Herald but you proof me wrong.
Awesome stuff darkstar and ivan! It works very well, and picks up my lcd settings properly (I used to get a ghost image with the earlier kernel). Anyhow, I did notice a bit of flickering in the screen around the top-edge. Not sure what that is.
Quick question: I remember you saying dark, that it takes you almost a day each time to compile the kernel. Would it make a difference if we used a multi-core machine? Perhaps ssh to a very powerful server and build everything there?
Kernel Jag said:
Awesome stuff darkstar and ivan! It works very well, and picks up my lcd settings properly (I used to get a ghost image with the earlier kernel). Anyhow, I did notice a bit of flickering in the screen around the top-edge. Not sure what that is.
Quick question: I remember you saying dark, that it takes you almost a day each time to compile the kernel. Would it make a difference if we used a multi-core machine? Perhaps ssh to a very powerful server and build everything there?
Click to expand...
Click to collapse
A multi-core machine I think could help...not sure how parallelizable the build is. It isn't the kernel that takes that long, it's the whole Android/Angstrom image. The kernel itself from start to finish takes about 10 minutes. 1 minute for incremental builds.
The server I'm using is a Celeron D 3.33gHz single-core originally designed to be a DVR/home entertainment system. Having a beefier processor would definitely help. Do you have something in mind?
- d
And I haven't done any of the coding. ^_^
It's all darkstar.
darkstar62 said:
A multi-core machine I think could help...not sure how parallelizable the build is. It isn't the kernel that takes that long, it's the whole Android/Angstrom image. The kernel itself from start to finish takes about 10 minutes. 1 minute for incremental builds.
The server I'm using is a Celeron D 3.33gHz single-core originally designed to be a DVR/home entertainment system. Having a beefier processor would definitely help. Do you have something in mind?
- d
Click to expand...
Click to collapse
I'm not sure if I could be of any help... I have some experience with Linux, unfortunately none with rebuilding kernels. My computers a Intel Core2Quad 2.5ghz 4gb RAM.
PM me if you want, I might need a crash course in it first though
apreichner said:
I'm not sure if I could be of any help... I have some experience with Linux, unfortunately none with rebuilding kernels. My computers a Intel Core2Quad 2.5ghz 4gb RAM.
PM me if you want, I might need a crash course in it first though
Click to expand...
Click to collapse
It's not too hard to get into it. The wiki has instructions for downloading and building from source. Haven't tested them though, so you'd be a good guinee pig for that, if you're interested.
- d
darkstar62 said:
It's not too hard to get into it. The wiki has instructions for downloading and building from source. Haven't tested them though, so you'd be a good guinee pig for that, if you're interested.
- d
Click to expand...
Click to collapse
Why not? I'll give it a try. Unfortunately I still have no phone to test it on, so someone else would have to do that. I assume I'll need to install Linux on my PC of course?
Also where on the wiki can I find this? I can't seem to locate the instructions.
How do I do it? I downloaded the software but I am having issues trying to get it on the mytouch
You're gonna have to wait as it seems the APL for the new mytouch3g is "perfect" and can't be rooted yet.
Not only that but if you have the 32B board, like the google ion, it's going to be very very slow.
seraph1024 said:
Not only that but if you have the 32B board, like the google ion, it's going to be very very slow.
Click to expand...
Click to collapse
So is the mytouch different then the european magic?? i know the rogers magic has more ram but i thought the mytouch and european magic were the same?
Im asking this because i have seen the hero rom running fine on the magic (not rogers)
here is a vid
http://www.youtube.com/watch?v=8TKOF-zBU2I
but maybe that is a rogers magic, not too sure. But even so i have seen it running on the dream so?
Once you get the swapped and everything setup correctly with a good class 6 card hero runs fine on the ion. As a matter of fact I have it running much better then any build I have tried for the g1 the only slowness I have is coming back to the home screen from using the browser and even then it is only at most 30 seconds.
But as of right now the mytouch is not rootable yet. Currently there is no way to get arround the security of the spl. Fastboot and adb don't work. Do us a favor go into your bootloader and post all the information that come up there for us just as a record for consistancy checking. Plus I know my ion came with a different version just as a comparison. So far I haven't seen the bootloader of the mytouch with certainty yet. If it says "S-off G" there may be hope. The only way I can figure of doing it id trying to get an nbh file for it like the G1 and building in a modified spl. I have tried to decipher the one for G1 with no luck yet. Can't even really pick it apart. Really locked down it seems with some form on encryption.
BTW this was typed on the ion running hero by fatal1ty v 1.4
yeah i figured that also as people who use the G1 who is running hero runs it perfect now no lag nothing so im sure the same method applied to the G1 can be applied to the mytouch 3g
Class 6
I am going to have to stand corrected regarding slowness. I've been watching the videos of hero on normal speed. Then I realize something. Something that should have hit me in the face considering I am in the IT business. Swap Space. That dang thing is stored on the SD card and I am running on a 16GB SDHC Class 2. Then I retried the same with 8GB SDHC Class 4. There is a huge difference. I am going to get a class 6 8GB tomorrow. Things should run fine with a decent class 6 card.
What I did not realize initially was that he (the rom maker) put the swap on the SD card which is a damn good idea. Something I'd have done but... I guess I was not thinking.
seraph1024 said:
I am going to have to stand corrected regarding slowness. I've been watching the videos of hero on normal speed. Then I realize something. Something that should have hit me in the face considering I am in the IT business. Swap Space. That dang thing is stored on the SD card and I am running on a 16GB SDHC Class 2. Then I retried the same with 8GB SDHC Class 4. There is a huge difference. I am going to get a class 6 8GB tomorrow. Things should run fine with a decent class 6 card.
What I did not realize initially was that he (the rom maker) put the swap on the SD card which is a damn good idea. Something I'd have done but... I guess I was not thinking.
Click to expand...
Click to collapse
do the swap space have to be on the microsd what about the phone internal memory... also how do you know the class of your micosd i got a 16gb i hope i don't have to replace it..and what about using ext4 for partitions would that boost up speed?
mykenyc said:
do the swap space have to be on the microsd what about the phone internal memory... also how do you know the class of your micosd i got a 16gb i hope i don't have to replace it..and what about using ext4 for partitions would that boost up speed?
Click to expand...
Click to collapse
It should say the class speed on the microsd itself. If it doesn't say then its most likely a Class 2.
mykenyc said:
do the swap space have to be on the microsd what about the phone internal memory... also how do you know the class of your micosd i got a 16gb i hope i don't have to replace it..and what about using ext4 for partitions would that boost up speed?
Click to expand...
Click to collapse
seraph1024 said:
Not only that but if you have the 32B board, like the google ion, it's going to be very very slow.
Click to expand...
Click to collapse
I have the google ion and it is slow even with the swap file on my class 6 microsd. It still is usable but not as smooth as it would be on the 32A version of the magic. I just reflashed to the nk02's ION v4 and its very fast. You should try that. nk02's ion rom doesn't have the hero added stuff.
thanks just seen the 2 on it lol i feel dumb guess i got to get another one...
I went to class 4 and there was an improvement. On class 6, improvement was not that noticeable.
????? i'm lost
howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views
I'm no programmer but this seems plausible so this would be a program that would prioritize all programs running in the foreground and background or all programs?
dont you think running this program in the background would use up alot of cpu usage also?
even in the background apps of rosie already use up alot of power...this would just take up more space and room and slow stuff down.
if it does get made it would have to be extremely lightweight
good luck
looking forward to what develops
redmdc said:
howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views
Click to expand...
Click to collapse
If you can figure out a way to edit the fameworks in /system/framework you'll be fine.
This is called cpgroups - and Cy's ROM and xROM already do this.
The problem with Hero/Mytouch is that the framework is odexed and we have no way to unodex them, edit the files, then remake them.
I love this community. i have confidance that this thread will turn into something good.
im running jaxhero 1.2 and it doesnt lag for me at all. im running compcache with a linux swap
I think this problem is partly due to lack of memory and possibly poor coding.
Hero UI on Dream is slow. Hero UI on Hero is faster, but still not smooth. The extra RAM on the Hero obviously helps since it's the same hardware besides more RAM.
There's a lot of work ahead to get it to run faster. Perhaps work with the NDK instead of the SDK. I assume when an application goes into the background it stops and writes data to memory, the services don't stop. I think to make Hero UI work faster, the code needs to be improved for less memory usage and then optimized more for efficient code. Not a simple task.
I'm not sure if prioritizing tasks will make it faster. It may make it faster to get to Home (once), but once you are there and if you want to start another application it will still need to do what it originally needed to done before it got de-prioritized.
Think of it as cooking, each time you cook something and you want to start something else you can clean up dishes or just leave them in the sink. If you clean up your dishes after each project, you take some time before starting the next one. If you don't clean up the dishes, you can start the new project quickly. However, soon afterward you'll have a sink full of dishes and you can't continue and they need to be cleaned and will take a long time. Thats how I view the problem. Get a bigger sink and more dishes (RAM) or optimize the process so it doesn't use as much dishes or it's quicker to wash them..
Maybe it'll be easily solvable when much fast sd cards are out that we can swap out a lot without slowdowns.
Good luck to anybody who is tackling this.
jad011 said:
im running jaxhero 1.2 and it doesnt lag for me at all. im running compcache with a linux swap
Click to expand...
Click to collapse
compcache is not supported in 1.2
You can remove some of the bloat by reducing the home screen to 5 or even 3 desktops. This should be hex editable, but I don't know enough about HTC ROM to do this.
I also see a lot of improvement in responsiveness of the ROM if I install spare parts from market and turn off window animations as well transition animations. This reduces my battery consumption a lot (passes my overnight standy test: thou shall not use more than 5% battery while on standy overnight for 8 hours) because it seems to be using some sort of graphics hardware accelaration and/or CPU, which makes battery deplete faster.
For my usage, I have been observing the swap usage with swappiness of 30 and I seem to need about 30-35MB most of the time. Now, since this ROM runs slow on Hero also, it seems like the RAM is only a part the problem because Hero does provide more than 35MB RAM on top of Dream. So, the conclusion is that its the inherent bloat in the source code and optimizations which need to be done to reduce the CPU usage. But only HTC can do that.
am i the only one not having any issues w/ the speed? Friend of mine has Cy and im able to keep up with him even though i have 6 big widgets. Only issue is getting in and out of contacts.
imbonez9 said:
am i the only one not having any issues w/ the speed? Friend of mine has Cy and im able to keep up with him even though i have 6 big widgets. Only issue is getting in and out of contacts.
Click to expand...
Click to collapse
YES!
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
sha.goyjo said:
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
Click to expand...
Click to collapse
two important things my momma taught me.
1. Don't say anything if you can't say anything nice
2. Don't do anything you are gonna apologize for later.
I, unlike Mr.Negativity who seems to have some underlying hate for life itself, want a faster Hero rom. Thank you all the dev's that have contributed and will contribute to this cause in the future.
Here's what I have done and seen a good pick up in speed with hero builds, I have an 8 gig cl 4 card but I guess you can do this with a 4 gig card too. make your linux swap partion 128
From what I understand the swap runs kinda like ram. I ordered a 8 gig class 6 card and I will try a linux swap of 256, but I think that will hang bad I'll let you all know in a few days.
But try linux swap set at 128 its much better
sha.goyjo said:
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
Click to expand...
Click to collapse
great advice.....is anyone willin to teach me how to make my own rom??
That_Guy_19033 said:
Here's what I have done and seen a good pick up in speed with hero builds, I have an 8 gig cl 4 card but I guess you can do this with a 4 gig card too. make your linux swap partion 128
From what I understand the swap runs kinda like ram. I ordered a 8 gig class 6 card and I will try a linux swap of 256, but I think that will hang bad I'll let you all know in a few days.
But try linux swap set at 128 its much better
Click to expand...
Click to collapse
Hey guy are you running 128 swap on 1.2? I ran 128 on all the others and they ran super smooth. For whatever reason I had lots of lag with 1.2 and lowered it to 96 which made it run smoother
Naw i got 1.2 but didn't flash it i might skip 1.2 and wait on 1.3 but thanks for the reply and input
ccyrowski said:
If you can figure out a way to edit the fameworks in /system/framework you'll be fine.
This is called cpgroups - and Cy's ROM and xROM already do this.
The problem with Hero/Mytouch is that the framework is odexed and we have no way to unodex them, edit the files, then remake them.
Click to expand...
Click to collapse
wouldn't it be possible to baksmali the odexes, then smali them to a dex and put it inside the apk?
jubeh said:
wouldn't it be possible to baksmali the odexes, then smali them to a dex and put it inside the apk?
Click to expand...
Click to collapse
Sadly only baksmali does not work. There is a way to undex but not as simple to compile as a dex when done.
Seoulboy1 said:
two important things my momma taught me.
1. Don't say anything if you can't say anything nice
2. Don't do anything you are gonna apologize for later.
I, unlike Mr.Negativity who seems to have some underlying hate for life itself, want a faster Hero rom. Thank you all the dev's that have contributed and will contribute to this cause in the future.
Click to expand...
Click to collapse
No one needs to apologize, everything that was said is true. You just don't consider it to be "nice" because you want a faster ROM which you know you probably won't get because of the reasons that were stated. Take the blue pill or the red pill, your choice...
Hi,
I am currently running CM6-RC3 on my G1. I am fed up with the slowness of the phone and I want to go to a fast OS, though I am spoilt rotten by some of the Froyo features. However, I think a fast ROM is still my prio.
First step is to get a Class 6 card and I have ordered an 8gig one from ebay. Should get that in a couple of days.
The second step of course is the ROM itself. Currently I have shortlisted SuperD 1.11 and SuperFroyo 2.6 Lite based on the reviews that I have read on the forum.
Firstly, if anyone has used these two ROMs, or can give me a comparative opinion of these two, then it would make my choice all the more easy. Is the SuperD really that that fast as compared to SuperFroyo that I should willingly sacrifice some Froyo functionality?
Also, how do I flash either of the ROMs? As I said, I have CM6 and AmonRa 1.7.0 Recovery. Now SuperD goes on about installing a legal base ROM and DRC83 (which itself has some new and updated versions in many threads) and then installing SuperD 1.11 itself. But coming from CM, is that necessary, or is it dangerous, or in short what am I supposed to do?
Similarly, if I have to flash SuperFroyo, should I do any preparations or just wipe and flash from the recovery?
The tough thing is that CM is so so so well documented that the other ROMs seem stark compared to that. I already have bricked a phone during the JF ROM era, so I don't want to screw up the one which is currently working. Any sort of detailed help, or pointers to other thread would be most helpful. I have been searching the forum and have not found anything that clarifies my doubts.
TIA.
I'm interested in the answers to your questions too. I've tried to improve speed and responsiveness by using many of the tricks posted in various threads but for daily usage the lags and the battery life are still not acceptable for me (though I like many of the Froyo features).
Having said that - you might want to check out the last pages of this thread [FAST][STABLE]SpeedTeam Froyo [v3.1.1][OFFICIAL RELEASE][8/23/10]
XxKOLOHExX is developing a 1.6-ROM with as many Froyo-Features as possible while retaining the speed, responsivness and stability of Donut. I'm very much looking forward to that ROM.
Having said that - you might want to check out the last pages of this thread [FAST][STABLE]SpeedTeam Froyo [v3.1.1][OFFICIAL RELEASE][8/23/10]
XxKOLOHExX is developing a 1.6-ROM with as many Froyo-Features as possible while retaining the speed, responsivness and stability of Donut. I'm very much looking forward to that ROM.
Click to expand...
Click to collapse
did he say when about hed be done? or did he just start on the donut rom?
I am currently running CM6-RC3 on my G1. I am fed up with the slowness of the phone and I want to go to a fast OS, though I am spoilt rotten by some of the Froyo features. However, I think a fast ROM is still my prio.
Click to expand...
Click to collapse
the final cyanogenmod v6 is really fast and stable. ive been running it since it was uploaded and havent had any problem at all.. kinda weird lol im used to some kind of force close or reboots but so far this rom seems really stable, you should try it out.
You might want to figure out why cm6 is so slow for you. Its probably the user, not the rom. I'm not a cyan groupie but this is by far the fastest rom I've used...and I've tried A LOT of different roms.
Sent from my jitterbug
staunty said:
You might want to figure out why cm6 is so slow for you. Its probably the user, not the rom. I'm not a cyan groupie but this is by far the fastest rom I've used...and I've tried A LOT of different roms.
Sent from my jitterbug
Click to expand...
Click to collapse
Really?, and you using it on a G1? CM5 was quite fast until ADW crashed on me and I had to reflash - decided to flash CM6 at that time. What are your SD partitions, if any? I am running it plain with only one large FAT32 partition.
I am a heavy texter. On Hero ROMs, it takes about 500-600 text's to start FC's and loading screens. On Froyo, I don't know how, but it took 200-300...Im on Super E right now and I can say I'm pleased. I'm at 1,902 Texts right now and its running ill say 90% of how fast it was when I just flashed it.
geekoo said:
Really?, and you using it on a G1? CM5 was quite fast until ADW crashed on me and I had to reflash - decided to flash CM6 at that time. What are your SD partitions, if any? I am running it plain with only one large FAT32 partition.
Click to expand...
Click to collapse
Everyone has their personal preference with regard to swap or no swap, compcache, jit, etc. I have no clue what works best even on my own phone (mt3g). But to let you know, I have a 32 MB swap partition, 512 ext 3 or 4 (can't remember, I think its ext4) and the rest FAT32.
donut/1.6? super d
eclair/2.1? super e
froyo/2.2? super f (not completed yet)
theyre all based off CM
geekoo said:
Hi,
I am currently running CM6-RC3 on my G1. I am fed up with the slowness of the phone and I want to go to a fast OS, though I am spoilt rotten by some of the Froyo features. However, I think a fast ROM is still my prio.
Click to expand...
Click to collapse
I felt the same way. I've went back to CM4 and CM5 trying to find the right balance. I am now back on CM6 latest and I think I may have found the key to making my phone perform well.
Swap. On a G1 with Froyo it seems that swap is a must. Once I enabled swap my market issues (would return to home at random, especially when searching) and other weird issues went away (shortcuts to URLs wouldn't open he URL but just my homepage). Try swap before you completely bail out of CM6. Even running swap on FAT showed a lot of improvement. I have noticed though that after a couple of days my phone starts acting funny so I turn swap off (swapoff command from terminal) and then back on and things clear up.
Of course this is all my common observation but I really think swap changed CM6 on my G1 from too slow for everyday use to the best ROM there is. I really think with the extra RAM needed for Froyo there just isn't enough left for simple apps (market, browser, etc) to function correctly.
Matt
Super D 1.11 (aka 1.10.4) is quality and I'm so happily suprised at how fast it is
I had forgotten what it was like to own a phone that just well worked without hassle of lose of functionality. As pretty as Eclair and Froyo are they simply can't match a good donut.
Give it a try and use the Setup Up Guide for Donut in my sig a look, it was designed around Super D
shadowch31 said:
Super D 1.11 (aka 1.10.4) is quality and I'm so happily suprised at how fast it is
I had forgotten what it was like to own a phone that just well worked without hassle of lose of functionality. As pretty as Eclair and Froyo are they simply can't match a good donut.
Give it a try and use the Setup Up Guide for Donut in my sig a look, it was designed around Super D
Click to expand...
Click to collapse
i just went to Super-E cause all of the froyos are too slow for my taste and all seem to be based on CM6 so what's the point? Plus one of my fav devs, Ben isnt working on SuperF atm so im kind of sad about that. His was my fav but its discontinued . The battery on it is good and speed, not as quick on its feet as donut but gets the job done, plus still has some newer features.
Not a fan of Sense, but it is at least bearable on HDPI devices. I used the official HTC RUU from the UK as a base, and now have a bootable, somewhat working Froyo ROM for the CDMA Desire.
It is by no means a daily ROM. I'm uploading here so we can get some testers and help from other developers. Since I'm usually occupied writing code for a living, any help is welcomed and appreciated.
What's working?
Audio, incoming/outgoing calls, SMS, data (works, but flaky), camera, GPS (needs more testing to really be given a thumbs up), backlight, vibration, live wallpapers
What's not working?
Wifi, BT, orientation, lights, MMS, and I'm sure much more.
What's included that isn't stock?
Busybox, DarkTremor apps2sd, root shell, deodexed
Currently, it's booting off of the stock 2.6.29 kernel and modules. I was able to get the 2.6.35 Cyanogen kernel to boot, but did not get all drivers/modules loading properly. I will be looking into that soon as well as possibly using the Incredible ROM as a base.
What can I do to help?
Download, test, tweak, get in touch with me. Twitter or PM on here will work. Pay attention to this thread, I will keep it updated. I look forward to your feedback.
Download Link
Remember to wipe before flashing.
http://dphase.net/desire/dphase_desirec_froyo_0.0001-signed.zip (146MB)
MD5 Checksum: 786d54cd68f30f8a890f072113364a19
reserved for later
good luck with everything i will give this a try once it becomes a little more stable. nice to see some cdma roms out here
I was correct in assuming we'd have success with the Droid Incredible build. Testing now and will tweak more tomorrow, stay tuned for updates.
Wonderful news!! I have been using the CM6 nightly on my Cell South with only a MMS bug but I will def rock out DPhase's ROM once it gets a little more stable. I am so excited to see a developer from Cell South! Can't wait to buy you a beer. I use my phone for work but I will flash this weekend to check it out and test for sure. I have a source that is putting the release of a OTA 2.2 on cell south to no earlier than the first quarter of '11 at best.
Phocas said:
Wonderful news!! I have been using the CM6 nightly on my Cell South with only a MMS bug but I will def rock out DPhase's ROM once it gets a little more stable. I am so excited to see a developer from Cell South! Can't wait to buy you a beer. I use my phone for work but I will flash this weekend to check it out and test for sure. I have a source that is putting the release of a OTA 2.2 on cell south to no earlier than the first quarter of '11 at best.
Click to expand...
Click to collapse
Have you had any issues with data on CM6?
I have been using CM6 as well on my cell south desire, I have not experienced any data issues. But it has only been a couple days since flash.
It seems a little slow but I think that is more Cell South than anything. I jump on wifi any chance I get. Still no MMS no matter what size file I try to send.
I would love to help with this... thank you for looking into it. Since it is not a "daily" rom, I really cannot run it too long until WiFi is fixed.
By lights is that the Message LED only correct? Or is it the Camera LED too?
Thanks again for starting this project! I would hope that you get the cyanogen kernel working, because I want the overclock
what can i do to help with this? i have a lot of time at work. but am far from a developer. CM6.1 is well on its way. id like to test for more devs. let me know what i can do. im flashing your rom now. then im going to try your MIUI
con247 said:
I would love to help with this... thank you for looking into it. Since it is not a "daily" rom, I really cannot run it too long until WiFi is fixed.
By lights is that the Message LED only correct? Or is it the Camera LED too?
Thanks again for starting this project! I would hope that you get the cyanogen kernel working, because I want the overclock
Click to expand...
Click to collapse
Camera LED is working.
Ok great... I'll load this up sometime tomorrow. I am doing a battery test on my phone today to see how CM6 compares to the 2.1 stock sense rom.
I'm in
I'm onboard i've been running your 2.2 w/o sice all day it works great. There have been a few things and i am sure i will find more in the next few days. But so far so good i will write in that thread what i find.But i am also gonna give this a shot tonight so i will hit you back with what happens.
hell yeah
After just 20 minutes of using this it is the [email protected]#$ other than the things you mentioned it is running great keep it up.
i just installed this and have been playing with it for an hour,and OMFG it is so sweet,thank you so much for working on this ROM. i will post any bugs i come across and hope it help to build better sense UI froyo ROMS for the CDMA desire!
thank you again! loving this so much right now i feel like a kid on Christmas!
i have formatted and partitioned my sd card ,the first one is 6 gigs fat32 and the 2nd is 2 gigs ext2. i cant get the SD card to show up on the phone,says its unmounted??? is this a known bug or something new. or am i doing something wrong? i will try taking the partition out and leaving it as 8 gigs fat32, however i thought that for APPS2SD needed a ext2 partition?
EDIT.... i deleted the ext partition and left the sd card as a full 8 gigs (7.65 gigs) fat32 and now this rom will see the sd card,however it will not move apps to the sd card.....
I don't think you are supposed to have an EXT partition more than about 1GB. That might be part of your problem.
lostcause247 said:
i have formatted and partitioned my sd card ,the first one is 6 gigs fat32 and the 2nd is 2 gigs ext2. i cant get the SD card to show up on the phone,says its unmounted??? is this a known bug or something new. or am i doing something wrong? i will try taking the partition out and leaving it as 8 gigs fat32, however i thought that for APPS2SD needed a ext2 partition?
EDIT.... i deleted the ext partition and left the sd card as a full 8 gigs (7.65 gigs) fat32 and now this rom will see the sd card,however it will not move apps to the sd card.....
Click to expand...
Click to collapse
apps2sd will not work with fat32 partitions. You must have an ext partition, recreate but don't go over a gig.
Sorry Dphase I didn't get a chance to load it up today... I had alot on my plate today. I will give it a shot tomorrow night and probably through the weekend. How is the battery life on this compared to 2.1? I am getting double the battery life on 2.2 cyanogen for the BravoC than I did with the stock rom, so I am having trouble getting myself to switch at this point.
dphase said:
apps2sd will not work with fat32 partitions. You must have an ext partition, recreate but don't go over a gig.
Click to expand...
Click to collapse
thank you, i will try to recreate a smaller partition now and try again.
EDIT.. I cleaned up the sd card and started from scratch, set my fat32,then created a 512mb in ext2,(1st partition is fat32,2nd is ext2) same problem. when i start the phone it says on the top of the screen "safe to remove SD card" message goes away,then i go to settings/SD card it says the card is unavailable.
but if i format the whole card as fat32 it will show up and work for everything BUT apps2sd. i know that i wont be able to move apps till i get a ext partition on the card, i just cant get the phone to see the sd card after i set it up.