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...
Related
I'm just curious about something. There are these 4 "base" ROMS floating around. Can someone tell me what exactly is the difference? I mean why should someone use Faria over Core for cooking? What makes Ingenetics better than Pandora? (Not sure if these statements are true...they are just examples)
I've been looking high and low to see why any of these would be better than any other one and I can't find an answer. Is there a comparison spreadsheet or something where you can see them back to back as to what they have and don't have? Is there one that is empirically and statistically faster, better, more stable? (I use the word empirically because I've heard many people say one is faster than the other even if its a complete contradiction)
Which one is better?
You sound like asking which one is better Cannon or Nikon?
My answer is all of them are equally good.few have some bugs/ limitations verses others and by an large its up to your taste and prefrences.
As Far as I have seen there is no comparison chart so far.
It might be a great task if you prefer to put together one while you go through assesing them. ( I am willing to help as others in here are ).
I would be all for it, but I won't know what aspects to assess. I mean I know speed is one, features would be another. I wouldn't even know where to start to be honest. However, I would guess there are people that actually do something similar for a living and might be better suited to get us going.
I used to be a network engineer, so I can usually figure things out in the wonderful world of software...and when I can't I ask questions. However, for the last 6 years I've been working towards a doctorate in clinical psychology and have put the computer world almost entirely behind me...so the skills I have are becoming old and stale. On the other hand...I follow directions well. So let me know what to do and I'll do it. Is there some standard for Mobile Phone benchmarking that we should start with?
ExploreMN can you please tell me where can I get the Original Ingenetics ROM which he got from Microsoft?
as banerjeez said, each one has its own limitations. As a rom cooker, you can test each one of these base's and see which one is right for you. It depends on the user. also, I don't think that there is an actual way to test the advantages/disadvantages of a base. Here's what I think most people do:
Test radio signal. (always can be changed with radio version
Memory that is left over after the rom image has been updated
Page pool of the memory
Speed test via playing video/music
Speed test via running multiple memory eating programs at once
Check on the build version. Newer builds are usually faster but could contain
more bugs if ported from anohter device[/LIST]
I don't know. I could be totally wrong. I guess I never thought to ever test things. If it works better for me, I keep it. If it doesn't, I don't.
You sound like asking which one is better Cannon or Nikon?
Click to expand...
Click to collapse
Cannon!
I have been a linux user for years, love it. so when i heard about android i bought a g1 as soon as i could... and honestly i HATE the java base... it sucks. For a while ii have been using debian on my sd and i think i have found a way to read ( but not send ) texts from within debian. any chance of developing debian to the point where we could use it as the primary system ? can the g1 g1 boot loader load it ?
No.........
damageless said:
No.........
Click to expand...
Click to collapse
Thanks ****, how about some reasoning or logic ? nothing cannot be done it is just a matter of how much effort is required to achieve the desired result.
modem_over said:
I have been a linux user for years, love it. so when i heard about android i bought a g1 as soon as i could... and honestly i HATE the java base... it sucks. For a while ii have been using debian on my sd and i think i have found a way to read ( but not send ) texts from within debian. any chance of developing debian to the point where we could use it as the primary system ? can the g1 g1 boot loader load it ?
Click to expand...
Click to collapse
Yes.
Seriously.
I haven't looked at Android in ages, but regardless - debian is just a packaging and deployment system. It has little to do with the actual code and configuration of what is deployed in the end. It's work, but it's trivial work.
As for your disdain for the Java - how about some elaboration there? Do you really think you feel a performance hit?
i do really feel that java does slow the system down for one, and second, i don't want to learn another language...
...
no..............
yes, the bootloader will load it just fine.
i have played with nothing but debian on my phone... although, it's fairly useless.
until someone reverse engineers some way to talk to rild and control the wifi module and its userspace components you're pretty much tied to the java environment if you want... well, anything but a fancy embedded debian computer.
anyway, initramfs-tools package is your friend, as well as the android development environment. the bootloader will load the kernel + initramfs, and from there the sky (and linux) is the limit.
and i had to comment on the java performance... seriously, does anyone doubt that there is a *huge* performance hit? while a register based vm is fancy and fairly efficient as far as non JIT vm's go, it's still ridiculously slow and wasteful for the operating specs of this machine. 96mb of usable ram? dalvik forks off separate processes for each vm instances, so not only do you incur major pain for the COW operation, but enough changes in the working set to almost eliminate any helpfulness of COW. it's confusing as the point of zygote is to have a basically mostly started vm, but i'm not entirely sure how that's working in the background.
FWIW, when you clock this beast up to full CPU spec speed (528mhz) interface responsiveness doubles in fluidity.
Of course there is a huge performance hit, few people saying no are google's blind lovers.
Im sorry for this useless post..
The issue to me is the time it would take to develop debian to full working capacity with all the hardware. Possible? Yes. Fun? Depends on who you ask. Probability high for it to be actually completed better than Android? Doubtful.
JMO
i agree with you in most points, however, there are already standard non-android mobile linux stacks. the only hardware specific areas that need to be addressed are the wifi and telephony libraries.
the graphics are simple, it's a standard linux framebuffer, and an x server will run directly on it. if that's too heavy for the g1 (likely) directfb can also be used.
in the end - will it be better than android? probably not. too much development has gone into android.
will standard native apps utterly outperform android apps? believe it.
though, without either: a port of an x server to interface with surfaceflinger, or: a modified version of surfaceflinger to talk to an x server running on the framebuffer, you will never get the best of both worlds without some intermediate transport like vnc.
i'm in no way an advocate of 'debian only!' however, the poster of this thread was smacked down by some people who obviously had no real knowledge in the matter, so i sought to inform him.
the better direction i think, is someone to write a nice tight little c api for the binder surface flinger interface so people can start writing some more memory conscious native apps for people with rooted phones. streaming daemons, etc. while i think the stock development capabilities of the android platform is much better than the stock iphone's, a jailbroken iphone is 100% cooler than a jailbroken g1 at this point, but once there is enough community drive - that can change.
Booting into debian primarily which then runs android ontop of it should be possible, and then using android for things until more is developed on debian. Should work.
Still the original post was more about strictly debian only.
modem_over said:
Thanks ****, how about some reasoning or logic ? nothing cannot be done it is just a matter of how much effort is required to achieve the desired result.
Click to expand...
Click to collapse
Temper tantrums aside, if you knew the answer to your question already what's the point of this thread? There's already a thread for people running debian on their G1, ask it there.
http://forum.xda-developers.com/showthread.php?t=444419&highlight=debian
nolageek said:
Temper tantrums aside, if you knew the answer to your question already what's the point of this thread? There's already a thread for people running debian on their G1, ask it there.
http://forum.xda-developers.com/showthread.php?t=444419&highlight=debian
Click to expand...
Click to collapse
Guess he can't now - been banned. Shame, too, I am sure we'll miss his pleasant demeanor.
davecanada said:
Yes.
Seriously.
I haven't looked at Android in ages, but regardless - debian is just a packaging and deployment system. It has little to do with the actual code and configuration of what is deployed in the end. It's work, but it's trivial work.
As for your disdain for the Java - how about some elaboration there? Do you really think you feel a performance hit?
Click to expand...
Click to collapse
OMFG yes there is a performance hit.
Yes i do bring certain special qualities to this forum don't I. at any rate i have began to build a port to be able to run directly off the jf bootloader.
vettejock99 said:
Guess he can't now - been banned. Shame, too, I am sure we'll miss his pleasant demeanor.
Click to expand...
Click to collapse
Yes i do bring certain special qualities to this forum don't I. at any rate i have began to build a port to be able to run directly off the jf bootloader.
Click to expand...
Click to collapse
cool i can't wait to try it out
modem_over said:
Yes i do bring certain special qualities to this forum don't I. at any rate i have began to build a port to be able to run directly off the jf bootloader.
Click to expand...
Click to collapse
Cool - that sounds great
modem_over said:
Yes i do bring certain special qualities to this forum don't I. at any rate i have began to build a port to be able to run directly off the jf bootloader.
Click to expand...
Click to collapse
any bootloader will work. there is no verification done by the bootloader during the bootstrap process, only during the flash process. flashing of the modified boot image with a debian initramfs instead of an android initramfs can be done from a functioning rooted android os, or from a test-keys enabled recovery partition. the method i used was to do a normal debian install on a partition of the sd card, installing initramfs-tools, building an initramfs, built a new boot.img with the stock android dev environment.
i've also compiled a kernel with full namespace support and a custom init that launches the android init and debian inits in separate namespaces allowing them to run concurrently. not much use since they can't talk to each other, but it is somewhat neat. virtuozzo like containers on your g1 =)
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.
I have a question that turns me on the head a few weeks, but there is a real alternative Home? .. I mean, almost two years now I have the hands on my HTC Dream, I must admit that I've seen very few, and try less. The question arises, there really is a programmer who is working on a real alternative to classic and multiple ROM that you see around? or we will always have many copies of already cooked ROM with only small changes that can range from icons, graphics or small settings to improve performance? Well i notice I'm not complaining about the excellent results we are getting our programmers, who try to keep pace with each new release, ported to every device imaginable (almost all with small donations) etc etc. but I doubt that I'll never have a real alternative as it could be TAT Home or easier SlideScreenPro ..
Sorry for my bad English
deleted...
sorry why?..
Good point, wrong section.
You're totally right about devs who only change or pimp Cyanogen's work. I think it's dumb and pointless. I understand amount of work etc, most of android devs on XDA are very talented people, but after trying 34 or 67th custom rom i saw there's nothing better than CM. Of course, there were several awesome roms like SuperD or sth like that, but after all it's just another pimped CM.
Speaking about home replacements - the greatest apps are those which are modified stock launchers. I don't like a fact, there's no really good other home replacement, but i'd rather use perfect-working ADW or LauncherPro than incompatible, slow, unstable, blablablah, etc. home like TAT, SlideScreen or Zune. And of couse most of those super-extra-special-unique home replacements (which don't even work stable) are paid. There's nothing more to say.
in the pre-CM5 era, there were lots of roms not based on cyanogen
anyone remember open eclair? it had the BEST boot animation ever.
Make your own Simple as that. If you're not capable hire someone. Or lastly, learn to code so you may make your own. Don't think any of the three are worth it, then maybe your idea isn't worth it. Just saying. A last option or rather possibility is having someone more talented than you(coding wise) do it out of their own free will because they share your thoughts.
asb123 said:
in the pre-CM5 era, there were lots of roms not based on cyanogen
anyone remember open eclair? it had the BEST boot animation ever.
Click to expand...
Click to collapse
You got that right. The only real reason all our ROMs are based on CM now is because almost everyone has moved on to a better phone. As soon as the N1 came out it started and hasn't stopped. Also, for that reason, this topic is pretty pointless. If this were occurring way back when Android was new and everyone copypasta'd cyanogen then it would make sense. That was never the case.
And there is nothing wrong with tweaking Cyanogen ROMs. Open source is meant for this. Cyanogen modifies AOSP then themers and file pushers share their optimizations on top of that.
And about a real home replacement: ADWLauncher is a real home replacement that kicks major a**. Ander states that his work is open source as well... So you can take his wheel and make your own little bike, dude. Peddle on...
If this is in the wrong section please move it instead of deleted it. Thanks y'all are awesome
So, what I want to is make my own Ice Cream Sandwich ROM.
I want to take stock android and:
-Make everything work right (camera, buttons, drivers for proper graphics and stuff, etc)...
-Use a good boot animation (I already have in mind which one)
Stuff like that. Would my old server with a dual dual-core Intel Xeon CPUs (total of 4 cores), 6GB RAM, and RAID SCSI disks be good enough, to compile it? Do I even need to compile it? or just unzip and zip?
Thanks!
PS: can I use Windows or would Ubuntu work better? I've also got a MacBook Air that I guess I could use
I won't touch on the driver thing (simply because it's not an easy thing as you suggest). Not only are there various 'work arounds' for the camera issue... but... eh.
Also, I will say that boot animations are nothing more than a text file and a bunch of images... no compiling done there. Just google around and you'll find the 'needed' format VERY easily... and probably even suggested software to make it easy.
Be careful, as you have a condescending style about how things that are easy but aren't, and aren't easy but are... while you haven't even really done any research. These things... they do not go over well here.
Ok as stated it is not as easy as it sounds. Compiling from source is not easy and making everything work is not easy either as the drivers are not released for this device. As all the source is ported from another device. Some of the best minds on XDA have been working for months trying to get the camera to work but with the new rules to the AOSP source from Google it is a huge undertaking. No longer can you build a full working rom from AOSP as the OEM drivers are no longer included due to being closed source and not released.
There are walk thru videos out there but like the Gentlemens above me said it is not a simple task. If you look at the developers it's a collaboration of several members making a team just for one ROM. But you can play around with several ROMs like I did:
Some Ice Cold Sandwich with a little salt from Redemption and a little pepper from Zues and BOOM my perfect ROM for me. (My Frankenstein)
BUT!!!!!!!!!!!!!!!!!!!
1. Dont get me wrong I'm not saying you can take bits and pieces from different ROMS and create your own and offer it here cause thats stealing from developers without their permission. But only for your enjoyment and PLAY AT YOUR OWN RISK.
2. you can't ask for help from developers when you alter their ROMs.
GOOD GOD!!!! Hope my phone don't die with so much flashing and testing (lmao)
Sorry if I made it sound like I didn't realize how huge of an effort good ROM development is. I do!
However, if I just take AOSP then attach the device drivers then add the features I want, I can release it as mine, right?
I'm bored with web design and development, so I figured hey let me try android stuff!
Maybe I should learn how to make an Android app first I have a feeling my basic Java knowledge won't be enough.
Would it be better to start with that, then progress to the more complicated stuff?
And I appreciate the time you are all taking to answer my random questions
I wish I could make Android apps with HTML, CSS, PHP, and Javascript. LOL!
Reinaldo33897 said:
GOOD GOD!!!! Hope my phone don't die with so much flashing and testing (lmao)
Click to expand...
Click to collapse
HAHA yeah sometimes I wonder if it's bad for it
But I've dropped it about 20 times and it still works no damage except for a tiny scratch in the screen so I'd say flashing ROMs is much safer for it than dropping it. LOL!