can someone please help me understand the major issues of porting android to the hd2? devs from htc can obviously get android running perfectly across numerous hardware platforms, so why is it so hard for anyone to port any version of android to the hd2 without some type of bug or problem? you can flame me all you want I just want to know what the major hurdles are so I can have a better understanding. Is it that HTC doesn't give you guys enough info on the hardware? is htc purposely holding back info from you guys so it's impossible to succeed? The hd2 has been out for ages and as far as I know, there is not one 100% fully working port of sense or stock froyo to the hd2 that I have seen.
It says right at the top of the forum.
READ BEFORE POSTING.
http://forum.xda-developers.com/showthread.php?t=734335
You must be able to read some English, even if it is one giant block of text...
Read everything in that thread, THEN ask a question, in the appropriate section.
You have no idea how much work is involved in porting over an operating system, or creating drivers from scratch. You sound like an ignorant moron, and that is not me flaming you, but being honest.
I have a 100% working version of Android on my HD2, and I have had it for more than 2 months now. You're probably just doing it wrong, because you have failed to read the stickies.
Read the stickies.
Good luck.
Custom drivers to initialize the hardware. The problem is that when you don't have the proper hardware schematics or internals, you have to write them from scratch and/or piece code together in order to get it to work.
The main issue is around creating things from scratch at times - very hard to do when you don't have the hardware particulars to build the code from.
Make sense? It's NOT an easy process at all. And yes, the hardware IS different between a lot of the phones. Anything from screens to CPU's to antennae configs, etc.
No idea what are you talking about, I am using Mdeejay Froyo Sense 2.4 and it is working 100% for me, every function i use on a daily basis works as well as when my HD2 was running WM if not better. As mentioned in the replies above, read, search if you feel your Android isnt working to your liking. If you do not understand how difficult it is to port an OS onto a device, research about it and you will understand these devs have done so much in such a short time and they rival any group of highly-skilled SW engineers that any tech company would love to get their hands on.
FriedSushi87 said:
It says right at the top of the forum.
READ BEFORE POSTING.
http://forum.xda-developers.com/showthread.php?t=734335
You must be able to read some English, even if it is one giant block of text...
Read everything in that thread, THEN ask a question, in the appropriate section.
You have no idea how much work is involved in porting over an operating system, or creating drivers from scratch. You sound like an ignorant moron, and that is not me flaming you, but being honest.
I have a 100% working version of Android on my HD2, and I have had it for more than 2 months now. You're probably just doing it wrong, because you have failed to read the stickies.
Read the stickies.
Good luck.
Click to expand...
Click to collapse
so you're telling me you have 100% working version as original as far as battery drain, tethering, camera, wifi, boot time, call quality, etc etc? if so, which one is that? seems I missed it somehow.
ruinertt said:
Custom drivers to initialize the hardware. The problem is that when you don't have the proper hardware schematics or internals, you have to write them from scratch and/or piece code together in order to get it to work.
The main issue is around creating things from scratch at times - very hard to do when you don't have the hardware particulars to build the code from.
Make sense? It's NOT an easy process at all. And yes, the hardware IS different between a lot of the phones. Anything from screens to CPU's to antennae configs, etc.
Click to expand...
Click to collapse
then it sounds to me like HTC is crazy, why would they change each hardware so much and have to re-invent the wheel constantly?
If u read my last reply in a previous post, NO QUESTION IS A DUMB ONE! Thats why these forums are here. Now I'm not a dev nor am I that tech savvy but I wud assume that the software has to match the hardware. While different companies make multiple devices, u wud think it shouldn't be hard to root one from the other, understand that each device has different hardware specs, therefore requiring hardware specific software. Hope that helps. As for the other guy telling u to read all the threads to find wut u are looking for, not everyone has the time to read thru all the threads to find the answer to a specific question. Sometimes it's easier to just ask the question in hopes that someone who knows the answer wud reply.
microse23 said:
If u read my last reply in a previous post, NO QUESTION IS A DUMB ONE! Thats why these forums are here. Now I'm not a dev nor am I that tech savvy but I wud assume that the software has to match the hardware. While different companies make multiple devices, u wud think it shouldn't be hard to root one from the other, understand that each device has different hardware specs, therefore requiring hardware specific software. Hope that helps. As for the other guy telling u to read all the threads to find wut u are looking for, not everyone has the time to read thru all the threads to find the answer to a specific question. Sometimes it's easier to just ask the question in hopes that someone who knows the answer wud reply.
Click to expand...
Click to collapse
you guys are all the best, and that's why I posted my question here. Yes the search feature is a PITA in it's own right, with the captcha bs and 1000 search hits. I could spend another hour refining my search, or spend 2 mins asking the question. If everyone expects people to search first then at least it should be faster or equal to just asking the question, then people would use it more I would think.
initzero said:
then it sounds to me like HTC is crazy, why would they change each hardware so much and have to re-invent the wheel constantly?
Click to expand...
Click to collapse
Each software has certain hardware needs to work. Obviously HTC is raking in millions and millions, so I wouldnt say they are too crazy.
Just because we can get a lot of different ROMs to work on our phones does not mean that all phones can handle all versions of Android and run perfectly out of the box. Although it would be cool.
thanks guys, so it seems the root issue is that HTC really does change their hardware fairly drastically between models and that just seems so insane to me. Why would they do such a thing? It seems so counter productive, and adds so many extra costs. That really sucks but I guess they have the $$ to do it with their stock being up there above google's.
I realize now that htc really is making (figuratively speaking) an apple, a pc, an xbox, a nintendo ds, a psp, a palm etc and getting their OS to run on it. That is really unbelievable. It must be a requirement of the different carriers. Pretty amazing how they were able to do that if you think about it. No wonder it's a nightmare for the devs here. That is exactly what I needed to know and it makes everything very clear now, thanks everyone.
p.s. microse23 you're always so nice, thanks man I appreciate it
initzero said:
so you're telling me you have 100% working version as original as far as battery drain, tethering, camera, wifi, boot time, call quality, etc etc? if so, which one is that? seems I missed it somehow.
Click to expand...
Click to collapse
please elaborate what y
you mean by battery drain. obivously the battery is going to drain, constant use of the SD card will do that to a phone , as far as boot time is concerned have you ever booted into a Linux live disk? it isnt all too fast is it? hmmmm i wonder why android take a sec to boot.... and here is a working rom for you: Nexus to HD2. I am using it and it works great! GPS lock in like 20 sec for me, sd is fine, tethering works, camera works (5mpx) boot time is about the same as my mytouch 3G slide after HaRET, call quality is clear no robot voice, apps from market install, HD youtube works. little to no touchscreen freezes, screen wakes up fast. (<--run-on lol) seems to be working 100%...
You don't understand how a computer runs.
There are apps that run ontop of runtime environments which are connected to the OS, the Kernel through the API (applicaiton programming interface) and then that talks directly to the hardware via the Hardware Abstraction layer, which is made up of a bunch of drivers which are individual files that detail what language and what commands are to be sent to a device to make it do certain things, which change with each device, which each screen resolution change and new technology or tweak on old technologies. Especially with the radio where it changes from 2G and 2.5G and 3G and H and H+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
APPS
API
OS
DRIVERS
HAL
HARDWARE
why can't they port a perfect copies? MONEY!...HTC paid their employees millions of dollar to put this thing together and make it run. Here at XDA, we have geniuses but they are working own their own time and reverse engineering isn't easy. I guess it would be like walking in a maze that doesn't always have an exit. Another thing, HTC is not exactly giving away much information on their hardware too which makes thing harder.
Think about it, we still can't get a PERFECT snes Emulators. They work and have MORE features than the original hardware console but still have issues.
Making software/os work on hardware that's not intended for isn't always clear cut.
encrypti0n said:
Nexus to HD2. I am using it and it works great! GPS lock in like 20 sec for me, sd is fine, tethering works, camera works (5mpx with 720p)
Click to expand...
Click to collapse
What.
Did I miss this?
FriedSushi87 said:
You don't understand how a computer runs.
There are apps that run ontop of runtime environments which are connected to the OS, the Kernel through the API (applicaiton programming interface) and then that talks directly to the hardware via the Hardware Abstraction layer, which is made up of a bunch of drivers which are individual files that detail what language and what commands are to be sent to a device to make it do certain things, which change with each device, which each screen resolution change and new technology or tweak on old technologies. Especially with the radio where it changes from 2G and 2.5G and 3G and H and H+.
APPS
API
OS
DRIVERS
HAL
HARDWARE
Click to expand...
Click to collapse
I assume you mean me? I do understand how a computer works as I repair them, the LiveCD/usb thing was very vague comparison.
shadiku said:
What.
Did I miss this?
Click to expand...
Click to collapse
OHSHI- thought I read it in the post was WRONG, my bad disregard that. FIX'D
Key points missed so far.
When HTC gets hardware from a supplier (Eg Qualcomm) they include driver source. Hardware API's etc for HTC to quickly develop drivers. Guys like Cotulla don't have access to this information so they clip some code from here, there and everywhere.
The hardware may be the same but the Bios (Radio) also defines how that HW is presented to the OS. The radio for a WM phone may present the hardware differently to an android phone. This needs different drivers.
There are 1000's of components and features in a phone all comprising of different models, revisions and manufacturers.
Cotulla and the guys work for free in there spare time. Big difference compared to being paid as part of a team of 20 people to do the job.
So in summary. What the guys are doing is trying to build there own UFO using photo's of an alien UFO that no one even understands the technology or how it works.
Would be a lot easier if the aliens left the instruction and design manual in the glovebox
Hi please stop this thread
Hi to the person who started this thread if you are so smart stop asking questions and read between the lines ,do you have any idea how an os is built and how programs are written in different languages,please google and find your answers rather than wasting the developers hard time they are spending at developing the android builds.please dont spend your valuable time answering my reply rather google your question you may get more info towards your required answer.
Please to the moderator stop such threads unless they are reporting build problems.
Related
I've been working with a great group of developers over at PPC-geeks.com on the Titan bluetooth problems, and I'm proud to say that our efforts have been fruitful!
The History:
In case you didn't know, the Titan has had horrible official Bluetooth support, and even the custom roms only get it "partway" there.
HTC's latest CDMA device, the Touch, uses roughly the same hardware under the hood as the Titan, however their bluetooth worked flawlessly. So, clearly the hardware is capable, its a matter of running the proper software!
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
The Solution:
Update the OS, but keep the drivers from an earlier build that had less new "issues" with BT. The 2.09 rom from sprint had stable bluetooth, however it had poor quality over the headset/handsfree profile. This was apparently NOT an issue with the drivers as much as it was an issue with how the OS handles them!
Replacing the OS with a ported AKU .7 from a Universal, and basing the rest of the rom on 2.09, we have what appears to be a release with stable, decent quality bluetooth that works as it should have out of the box!
More testing is needed, but it seems like the best build so far, and should be a strong candidate as a base rom for future customs.
What this fixes:
-No more poor BT quality
-No more random BT shutoffs
-No more system freezes when coming out of standby due to BT stack left on and disconnected
-No more D-pad lock issues
-Generally stable Bluetooth performance that works AS EXPECTED.
Known issues:
-Alarm Bug, which was and still is a part of 2.09
However, we're working on a fix for this.
Find it here:
ftp://ppcgeeks:[email protected]/Titan/Users/sfaure03/ithinkwegotsit.rar
(as of this writing, the ppcgeeks ftp and webserver have been hit pretty hard, and are timing out an awful lot, so if it doesn't work, try again later. Perhaps someone would like to mirror it somewhere?)
Special thanks to all who contributed to this effort, particularly PPC-geeks users Sfaure03, DogGuy, no2chem, jtrag, and all the others who tested, theorized, and gave sage advice.
Personal thanks to ImCoKeMaN, for explaining how things work and having the patience to answer bizzare questions from the rest of the group.
edit: whoops nevermind
I'm not expereinced enough in using this type of file - can you please tell me what is the procedure to install a .rar file into the phone.
its an .nbh file, rar is the compression method. Its like .zip, only you need winrar (or something compatible) to uncompress it.
there's a tutorial on ppc-geeks (which I should really post here as well) about how to unlock and flash custom firmwares on the titan.
you guys rock!
So installed this ROM a couple hours ago. So far the phone's working fine. Tested BT in my RAV4. Wife says it's much improved -- previously if I called from the carphone she'd known instantly and ask me to switch it off. Now she's says it's fine. (High praise indeed. )
So bottom line: quality issues appear much improved. Major kudos!
Update: maybe I was slightly hasty. So the phone sits in my pocket for a few hours. I press the power button to bring it out of sleep. Password screen takes 15 seconds to come up. Enter the password, Today screen takes 30 seconds. Click on the Voicemail link, get a message that the phone cannot make the call. (low RAM?) Nothing else (afaik) except SPB Mobile Shell running at the time.
Boom, soft reset. Is it the phone? Is it the ROM? Is it me?
Mirror at: http://rapidshare.com/files/71094429/ithinkwegotsit.rar.html
The ROM finally makes my BT usable, but is still quite choppy and compressed. Unfortunately not a true fix for my device.
But, kudos to the developers for getting it to be usable! Thanks!!! You clearly beat Sprint/HTC!
However, my RAZR2 and Touch still have much better BT, so will keep using them at least for awhile.
Will see if the 'official' Sprint ROM (1) actually happens, (2) truly fixes the problem. If not, then I'll use my Touch until the Treo 800w or Titan 2.0 come out and likely swap my Titan at that point.
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
wsparvis said:
Unfortunately, even if Sprint fixes BT, Titan 1.0 will never have adequate memory for WM6. Sadly, the lack of memory is an unfixable product design deficiency.
Click to expand...
Click to collapse
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
I have to agree here - the Cingular 8525 runs quite well with only 64MB of RAM (Other at work run it). My Titan runs quite well with only 64MB of RAM - HTC Home from the touch on the other hand makes it run like a three legged dog. Without the 3rd party plugins it zooms along quite well even with several apps running.
Dishe said:
Heh, I love it how everyone keeps badgering that.
Look, I don't want to take my thread off-course, but when WM6 was released, ALL DEVICES HAD ONLY 64MB!
It wasn't until recently that we really started to see 128mb become more standard. The Touch (vogue) is actually the first 128mb WM6 device I've ever put my hands on, and I've had WM6 running flawlessly on the last 5 or so devices I've owned.
So, don't tell me that this is a major unfixable product design deficiency. It'd be nice to have more memory so you can leave more stuff open, but if you're not new to this and know what you're doing, its perfectly acceptable.
::end rant::
Click to expand...
Click to collapse
OK - fair enough, my memory comment WAS off topic! BTW you introduced the word "major"; I never said it was major - just unfixable. And, yes, you're right - if you want to manually do the OS's job for it, there is an acceptable workaround.
Interesting, though, that you responded only to that one sentence out of five in my post, not the other four which stated that BT quality is poor/mediocre on my device (which is an improvement from the prior unlistenable state).
Anyway - what kind of success rate are you seeing from various forums with this ROM? I still suspect the problem is partially HW, and that BT on some devices (mine probably one of them) may be unfixable.
Dishe said:
After many attempts at porting the Vogue (htc touch) Bluetooth drivers into any number and combination of titan roms, it was concluded that it is NOT the answer (sorry custel).
This was the first obvious approach, however every attempt had some problem or bug, or sometimes wouldn't even boot up!
So we took another approach...
Click to expand...
Click to collapse
Why call out another developer? I fail to see how it was necessary. I'm assuming you have no life, and make roms for a living? I'll download whatever works; but because of your approach to criticize other people who try (which is EXACTLY what you do) to make something work, makes me not want to download your rom.
dishe is an such arrogant SOB, who think he's all that because he's creating ROM...well props to you that you do create rom...but its just people opinion/wish about having more ram (which is UNFIXABLE! on mogul)...you don't have to bash them for it...would u preferred an old style laptop/computer from the 2000's or newer/faster in 07's. However, you might be able to upgrade their RAM through hardware...but does HTC have such RAM upgrade for mogul!? anyways...i'm not hating on your work at all...but i just get disgusted when you go and ranted on someone post (n it was a valid post.)
ps. If you want to brag, make something that's useful w/o any glitches. Success at that then brag all you want, but at this moment you still using the public to test whatever ya doing. So stop tripping home boy.
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
hey DISHE
bro u dont even owe these guys an explanation, they contribute nothing and take everything. they dont understand whats involved and quick to criticize anything they dont agree with.
it appears to me that they think they are all that and a bag of chips/ but if the DEVs of these fixes decided not to share, i bet they would keep there mouth shut real quick/
bottom line bro, dont bother posting any more responses to these idiots / look at the end of the "
Hard-SPL - or how to not brick your PDA ever again" post and u will see what these guys are like on this forum, calling each other names and etc just like they r doing now.
i c u at ppcgeeks
Dishe said:
Wow, I've heard of people venting on forums, but this is rediculous. Did you all have really bad days or something?
Look, there's a lot going on that doesn't take place on this forum. I used to be a big XDA-dev's fan, but unfortunatley I've found that there just isn't enough research and development for our particular device going on here, so I started broadening my horizons.
Maybe I didn't make it clear in the first post, but I didn't make this rom.
At least, not by myself. I worked with a team of people from other boards and we formed a group that has been testing theories and building different rom combinations to try and come up with the best solution possible currently. We've made some amazing progress, and the nostalgic part of me wanted to come back to XDA and not leave you guys in the dark.
We've noticed Custel doing similar things on XDA, and we had already tried a lot of what he was doing. We found that the vogue BT didn't play nice with the rest of the Titan rom components in many situations, yet Custel kept trying. I beleive that some of the devs in our group tried to contact him, possibly even get him involved, share what we've learned so far (collaborative efforts are the best way to go). I don't know exactly what happened after that, and I didn't ask because its not my business. I mentioned him because he's still trying something, where we've had a bit of success. Not that its a race, but it would appear that we got there first using another method. I'm sorry that you read that as a "flame" on his part, I didn't mean to disrespect. Just that we we're doing is not what he's doing, and we've tried that route already.
Some of the others in the group of devs warned me not to go posting here. Thought maybe there would be too much animosity. I decided on my own to bring the information here because XDA was always a great source of info in the past, and there's no reason you guys should be left out. Are you trying to make me regret it, as if I'm wasting my time here?
Lazy and cool6324, I'm not forcing you to try this rom. I'm also not "bragging" about what was created. I'm filling you guys in. If you don't want it, that's fine. I won't bother updating.
Click to expand...
Click to collapse
Where was I supposedly contacted?
dishe don't even trip! The folks *****ing are the ones using the Roms also. Take their comments with a grain of salt....F**K EM!!!! Don't waste your time on these idiots. Others apperciate the work you do to make our Moguls useful.
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
lazee said:
to step: shut ur ass kissing d!ck sucking ***** depriving n a **** hole that you called a mouth! I dont even use BT, yeah its nice to have clean/custom rom to rig my phone. But a stock is fine with me. Just tired of people kissing dev's asses geeze....get them stick out of ur ass....
ps. i never did dish at dishe's rom nor either ***** at it....it was his tactics of bashing on people posts...so get it right...
Click to expand...
Click to collapse
LMAO...such childish folks here....I'm gonna just LMAO!! at u...so sad
Lazee,
its not about kissing ass. Its about appreciation for what these guys do (AND FOR FREE they do it!!!!) they rarely ask anything of the rest of us, if anything at all. Because of the fact that they do give up alot of free time, which they could be doing something else, to help out alot people they dont even know, i have a certain amount of respect for that alone, regardless if they might seem arrogant. the truth is that they really do care about people or they wouldnt even share what they do! theres no law that says that they have to share anything with us/ sometimes its easy for us to forget this and take it all for granit/ lets just call a truce and stop with the name callin and etc and try to maintain a respectible forum ok.
PEACE!!! come on guys we are all in this together
Oh and by the way Custel, u rock bro, do what it is u do and dont stop!! dishe luvs ya nothing personal, i dont want to speak for him but i get the feeling that things might have came out wrong when he was responding to the "lazee's post and was just a lil fluddered.
I recently switched to Sprint and opted to buy the Mogul as opposed to the Touch thanks to the larger ROM space but was shocked and disappointed in the lack of activity and ROM development here as opposed to the over in the Wizard Forum where I came from. It seems that almost once a week a new ROM is released for the Wizard but here in the Titan forum there is next to none. I have only seen a few custom ROMs and some of the problems I have read about and this only discourages me from wanting to update. I really liked having the HTC Touch look and feel built into ROM on my Wizard but because noone seems to want to create a ROM for the Titan that has the same total look and feel, I had to search for applications to add to my Mogul to give it that same look because of this my RAM is very limited and cannot run very many applications at the same time without having serious lag or having to soft-reset because of lock ups thanks to low virtual memory.
Aren't there any master chefs out there that can cook up something for the mogul that have the COMPLETE touch look?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know there are several different carriers and that these are CDMA devices but isn't there a way to create a universal ROM for all of the carriers that will adapt to whatever settings you need as seen for many other phones?
Or creating ROMs for a specific carrier that can be used on other carriers models with only minor customization?
For example: Create a ROM that is designed to work for the Sprint Mogul only to maintain Sprint's connection settings and not have to re-configure the device after a ROM upgrade but also have smaller packages that can adapt that ROM to other carriers?
I would say that this is just food for thought.
Hey man, welcome! You made the same move I made. You forget it took us a while to get good roms for the Wizard too, but we finally got them. This forum is a lot younger than the wizard, and I think it will eventually get to the same spot.
We didn't even have a custom rom available at all a while back, but now thanks to some gifted individuals we have several to choose from.
Just be patient, new things come every day
I'm really looking forward to it.
Trade in your Mogul for a Touch and you will be happy....
Mogul hasn't been around for too long and you are expecting too much too soon.
ryanwood said:
Trade in your Mogul for a Touch and you will be happy....
Mogul hasn't been around for too long and you are expecting too much too soon.
Click to expand...
Click to collapse
I'm not following your logic here. The Touch is a newer device than the Mogul!
my kitchen and dogguys kitchen are available, all the tools exist, nothing is stopping anybody.
two of your screenshots of what you want came from my custom rom post. everything is out there and the roms that have been put together by different people just dont 100% suit what you personally want. you should try a kitchen.
im playing with the idea of a touch rom. but you guys should be able to make anything you want.
jhendrickson said:
I'm not following your logic here. The Touch is a newer device than the Mogul!
Click to expand...
Click to collapse
but it seems his ultimate goal is to make the mogul look like the touch, but the touch looks like the touch right out of the box
^ Yeah, I thought it was pretty clear what he was saying.
Guess I should wait to post till AFTER I get my first cup of coffee down
dcd1182 said:
two of your screenshots of what you want came from my custom rom post.
Click to expand...
Click to collapse
Yes I did borrow those screenshots as a way to show what I was looking for since I could not find them anywhere else.
defaultdotxbe said:
but it seems his ultimate goal is to make the mogul look like the touch, but the touch looks like the touch right out of the box
Click to expand...
Click to collapse
Yes my goal is to make the Mogul look like the Touch because personally I am not satisfied with the lack of device storage on the Touch. If I was to trade in my Mogul for the Touch I would be downgrading to virtually the same exact thing I had before, a Wizard which has 128Mb of ROM and 64Mb of RAM... Not interested...
I enjoy having a larger device storage and if it is possible to have the Touch look and maintain my 256Mb of device memory that would be great.
Unfortunately I do not have the kitchen skills nor do I really have the Mogul skills yet. I just recently upgraded like a week ago not even and came over to this part of the forum seeing as I no longer have a Wizard but a Titan. Ask me a question about the Wizard and odds are I could answer you but I'm totally new to the Titan board and was just shocked that there wasn't really too much going on. Thats all.
I have that total Touch look already, but they're all 3rd party apps installed and it just hogs up space and slows down the device. If they were in ROM already, I wouldn't have that problem. Not to mention that having a larger device memory, the Titan could probably smoothly handle a 16Mb pagepool with no problem and with the 400MHz processor it would be stupid fast and thats just how I like it. Not having it slow down to a crawl and having to soft-reset every 12 hours...
dharvey4651 said:
Yes my goal is to make the Mogul look like the Touch because personally I am not satisfied with the lack of device storage on the Touch. If I was to trade in my Mogul for the Touch I would be downgrading to virtually the same exact thing I had before, a Wizard which has 128Mb of ROM and 64Mb of RAM... Not interested...
I enjoy having a larger device storage and if it is possible to have the Touch look and maintain my 256Mb of device memory that would be great.
Unfortunately I do not have the kitchen skills nor do I really have the Mogul skills yet.
Click to expand...
Click to collapse
before everybody jumps on you...the touch has 128mb ram
i do understand your reasoning, i made a rom today that is 'touch style', the only issue i have is that the cube interferes with calibration. it works if you disable the welcome screen, otherwise hangs there. i need to make it boot and let u calibrate, then put the cube files in startup, and i have a game to watch in a little bit maybe this weekend i will throw it together if i am bored...but the different touchflo/cube distributions out there are very rapidly updated and its pointless to try and widely support a tf/cube rom. if i post you a rom its just some thing i threw together.
however this is my point again, the stuff is out there for the titan and anybody can throw together any rom they want any time. i think right now you see less activity on this device because most of the people working on it are more focused on improving the OS before making it fancy. i think most people are playing around with a few wm6 versions and will settle on one (or just use whatevers newest), eventually qualcomm will put together better display drivers, htc will improve bt drivers...
ryanwood said:
Trade in your Mogul for a Touch and you will be happy....
Mogul hasn't been around for too long and you are expecting too much too soon.
Click to expand...
Click to collapse
yes,that is true,and in a few weeks there should be a new hacked rom for the touch that will give it a slide out hardware keyboard..... oh wait,never mind,there wont be. Guess Ill keep trying to make my mogul look like a touch.
dcd1182 said:
before everybody jumps on you...the touch has 128mb ram
i do understand your reasoning, i made a rom today that is 'touch style', the only issue i have is that the cube interferes with calibration. it works if you disable the welcome screen, otherwise hangs there. i need to make it boot and let u calibrate, then put the cube files in startup, and i have a game to watch in a little bit maybe this weekend i will throw it together if i am bored...but the different touchflo/cube distributions out there are very rapidly updated and its pointless to try and widely support a tf/cube rom. if i post you a rom its just some thing i threw together.
however this is my point again, the stuff is out there for the titan and anybody can throw together any rom they want any time. i think right now you see less activity on this device because most of the people working on it are more focused on improving the OS before making it fancy. i think most people are playing around with a few wm6 versions and will settle on one (or just use whatevers newest), eventually qualcomm will put together better display drivers, htc will improve bt drivers...
Click to expand...
Click to collapse
I am not disagreeing with you because I just did some looking on eBay for the Touch through Sprint but I have seen so many sellers saying it only has 128Mb of ROM and 64Mb of RAM but then some others say that the memory is double that, which compliments what you just said. I don't know. I've never played with a Touch but will have the chance in like a week because my store is getting them in soon.
EDIT:
I have found some disputing evidence to what you have told me in the form of an official review. Click HERE for the link.
Armed with a 201MHz TI OMAP850 processor and 128MB ROM/64MB RAM, general operation was a tad slow. With about 12MB of free program memory, there was often a few-second delay when opening applications. At first we thought our device just didn't register our touch commands, but it was really a performance issue. Launching any of the multimedia functions really did a number on the Touch, as the screen sometimes froze midway between the music player and menu screen. This happened on a number of occasions, and got to be quite frustrating.
Click to expand...
Click to collapse
This quote is located under performance in the link above. If this is wrong and the HTC Touch that Sprint in the United States is selling is in fact double what that quote says then I will stand corrected.
dharvey4651 said:
.....If this is wrong and the HTC Touch that Sprint in the United States is selling is in fact double what that quote says then I will stand corrected.
Click to expand...
Click to collapse
It's wrong. The Sprint CDMA Touch (HTC Vogue) does indeed have 2x CPU and 2x memory compared the GSM Touch.
is this the cube you are wanting?
http://forum.xda-developers.com/showthread.php?t=343583
dcd1182 said:
is this the cube you are wanting?
http://forum.xda-developers.com/showthread.php?t=343583
Click to expand...
Click to collapse
Thats nice and all but not entirely what I am looking for. Until I can upgrade the RAM in my device(which I discovered is nearly impossible), I would much rather just have a Touch style ROM for my Mogul. I like the Touch but I prefer devices with that nice, convenient, easy to use qwerty keyboard and unfortunately the Touch doesn't have that nice, easy to use, convenient feature and the Touch Dual is WAY out of my price range for now. Not to mention from all of the threads I have read they are GSM only and Sprint is CDMA so I couldn't use it if I could afford it.
would you mind linking me to the installation cab(s) for the cube you do have in mind then?
you mention in post 1 that you already have your phone setup with the applications pictured in screenshots installed..i see the cube.
Actually it was just a cab that I found here on the forum. (http://forum.xda-developers.com/showthread.php?t=343583) it was kinda buggy and I didn't really like it that much but it was something.
Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
xriderx66 said:
because porting doesn't involve copying the nexus' rom and pasting it on the vibrant.
the Drivers, which run the whole phone are incompatible, there is a ALPHA build version, with no gps, the buttons are switched, voice doesn't work, etc.
Drivers are not possible for devs to make, and only samsung, and other manufacturers, can make them, and make it compatible.
Click to expand...
Click to collapse
Thanks for your response. I do understand that "cutting & pasting" is a no go. But what got me curious is that the hardware is the same. So speaking from a PC Geek's view a series of GPU's if you will can be produced by different third party vender's. However the Drivers would be the same even if the third party vender changes the BIOS they could still be flashed to another card ex. flashing ASUS bios to a similar card like a MSI GPU. Some vender's may slightly change the user interaction ex. software suites for "tweaking" settings ie over-clocking. So I guess this is why I'm asking what is so different regarding these two phones that prevents a "clean" port. If the hardware was a completely different generation I totally could understand. This unless I am wrong (which I probably am) is what is bending my logic.
Edit: I stand corrected the Nexus is different
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
vs.
http://www.ubmtechinsights.com/repo...stigative-analysis/samsung-galaxy-s/teardown/
amwilliams9 said:
Can someone kindly explain why porting the Nexus S to the Vibrant doesn't work? I have tried to use "Search" but have been unsuccessful with finding in depth information on the subject. From what I have gathered, with the exception of Bluetooth 2.0 vs. 3.0, Front Facing Camera (VGA) lack of external storage, and obviously Android 2.3. There is no other difference. I guess I'm wanting a more technical answer regarding the differences. Yes I understand regarding modems/source codes etc. But I still don't get it. I'm more of an amateur over-clocker on desktops and I guess the differences vs. a desktop and smartphone are greater than I initially realized. Perhaps my chosen search definitions aren't specific enough or are too vague. I'm sure this may have been beaten to death but my want to know has gotten the better of me. I find this community to be full of knowledge but I fear that using search can be frustrating. Thanks in advance for you expertise guys (gals) BTW the similar threads box is awesome.
Click to expand...
Click to collapse
difgerent radio, difgerent storage inand on ns, basically two different phones
And most importantly the lack of vibrant source code
Sent from my Nero powered Vibrant
how many firmwares, can xda devs firms ware, when the firm they wear, cares not for warez?
ok - delete this... o.. maybe not...
44.44% would rather have one single GingerBread ROM over anything else, excellent!
Keep the vote's rolling, let's find out what people really want!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MrHassell said:
delete this
Click to expand...
Click to collapse
What was that? It makes me even more excited since it's deleted
hehe, to bad you deleted the first post, it was very well said
MrHassell said:
how many firmwares, can xda devs firms ware, when the firm they wear, cares not for warez?
ok - delete this...
Click to expand...
Click to collapse
What?-....-........
Delete lame 'roms' - firmware stools
qwer23 said:
What was that? It makes me even more excited since it's deleted
Click to expand...
Click to collapse
Well half these firmwares could be deleted here and nobody would notice. There is some kind of trend to spit out firmwares, confuse people calling them ROM's and act like it's in the name of progress?
Where I sit, all this cloning is not flattering, it's more akin to theft and I'm sick of seeing all these useless crap ware - camera doesn't work - because you copied J? Z? - Oh where did you get that Cyanogen Mod from.. etc.. ha
Took a bit from here and bit from there... rebadged, rebranded, lifted, ripped - whatever.. it's funny for 5 minutes but it's just happening more and more and becoming - BORING!
Mirthel said:
hehe, to bad you deleted the first post, it was very well said
Click to expand...
Click to collapse
...or not...
he`s half right about what he wrote.
obviously the ones and only that made a "almost fully" rom for ours x10, was/is Z, J and T.
but one interesting thing is. a few months ago, when i see this so called 2.1 roms never read anything about it. and they were called "rom".
i give that opinion on those times...nobody give a **** about that...
but if we go further, they don`t do any roms aswell. they pick some here, some there, mix all together and...hey, it worked...great.
the ONLY way we can have a TRUE custom rom is when we crack the f..k`in BL, untill now...
my understanding is:
this so called roms are...mod roms.
but thats just me
I think the Z J and trip are really developer.THX them
MrHassell said:
Well half these firmwares could be deleted here and nobody would notice. There is some kind of trend to spit out firmwares, confuse people calling them ROM's and act like it's in the name of progress?
Where I sit, all this cloning is not flattering, it's more akin to theft and I'm sick of seeing all these useless crap ware - camera doesn't work - because you copied J? Z? - Oh where did you get that Cyanogen Mod from.. etc.. ha
Took a bit from here and bit from there... rebadged, rebranded, lifted, ripped - whatever.. it's funny for 5 minutes but it's just happening more and more and becoming - BORING!
Click to expand...
Click to collapse
Well I can understand your point of view, even if I don't share it. Giving the people possibilities to choose from isn't the worst thing. And by modding one "ROM" in many ways, a lot of heads think about solutions for bugs and problems. In that way it actually is in the name of progress
Regarding the word ROM: I think most xda users are used to have ROMs for their phones and since the different firmwares we have for the X10 behave like a ROM in most aspects, it would be more confusing to call them firmwares, even if it is more correct...
Too funny
Honestly, I really kicked a hornets nest here - haha - Wow!
It's not really about names, firmwares and roms, apples and oranges etc.. I'm just really perplexed by the sheer volume of unfinished projects some blatantly ripped without any credit to the authors and more than anything, the sheer uselessness of the majority.
It's great that people want to contribute something, so how about downloading the favorable 'rom' (if it makes you feel cool.. or whatever) and make your contribution and then ONE BETTER, instead of uploading the whole schamozzle of mish mash..
Just the mods' that matter? I.E; Changed the Framework-Res.apk and a few apps, then do what Sempeternal does and release an update.zip! - Include screen shots.. but the whole firmware for a theme.. seem's overkill..
Put this in context, not naming names here but I downloaded a GingerBread a while back and it had one single app.. aside from that it was a virgin clone of another guy's rom - with no credit or even value... and it's nearly every day I'm seeing someone pop up with another CM or something and it's actually.. distracting.
Personally I'm 150% behind the work of Z, J and Sempiternal (my favorite theme is the new HC) which looks awesome on any GB modified firmware, even on Eclair and Froyo.
That is what I'm talking about! - Semp really knows what time it is and releases amazing work, free of charge. Best of all across any flavour, without any nonsense! All killer - no filler
Ginger!
i would say gingerbread and a cyanogen brew (which J would start to cook up soon^^)
i mean, who doesn't want the latest version of the most powerful android rom?
Since this is a thread opened for discussion, allow me to do exactly that. The below is strictly my own opinion and not a rant and/or an attack aimed at anyone.
I'm extremely disappointed at the way things are moving in the X10 Dev section. There are dozens of unnecessary half cooked 'ROMs' that're of no practical use. The blind self-righteous and immature dev worshipping present in the thread is shockingly mind numbing. Ask questions, even valid ones, and you're swarmed by these retarded sheep who respond back with insults and personal digs. One user even told me to go buy another X10 when I supported another user who posted a question for the Dev. about the the newer basebands, especially since the Dev himself mentioned that the newer baseband support may [or may not] come. Regardless, the question was for the Dev. and not the sheep.
Just when I feel consoled read something that hints at *some* progress being made with the current firmware, I find myself reading another post, after a while, which takes on a completely different direction. The firmware suddenly gets dropped in favor of a newer/<some popular ROM> which, then, necessitates the Dev. to re-engage himself with the long list of functions and features that aren't working. In essence it means, we're back to ground zero. Why is that necessary? It's a fact that we aren't going to see a 100% functional port because of the locked bootloader - so wouldn't it make more sense to concentrate on just 1 firmware and make it as perfect as possible, with the omission of things that wouldn't be working due to the locked down bootloader?
I sincerely think we need just *2* FIRMWARE threads in the Dev. area - one for 2.3.x and one for 2.2.x. The CM additions can be easily had by installing the CM Settings app, the themes etc. on top of whichever edition one chooses. There's no need to have a complete 'ROM' uploaded with the same critical and few non critical issues.
I should reiterate, the above is simply my own opinion and is in no way a rant or an attack on anyone.
Yes too many rom. Devs should work together to make a perfect room than every dev make their own rom better.
There are developers... and chefs... devs develop the software. Cooks or chefs take ingredients or parts of software and mix or cook them. If you have been a long member of xda you would know that this has always been how it is for EVERY phone that is on this site... but more so this thread propably should be moved to a different section.
Sent from my X10i using XDA App
It's never wrong to share. If you don't like it, just don't download. It's that simple.
And from what I see, credits are given where it's due. Many don't even ask for donation. And they don't pretend to be a dev like J, Z & T.
Yes these are mods & tweaks. But some really did a nice job - like wolfbreak's rom - it's fast and stable with a great look.
It's always good to have choices. IMO their threads are much more useful than this thread which contributes nothing.
Of course you don't have to agree with me and I don't have to agree with you
People on here seem to have the mistaken impression that if devs came together we would have a perfect rom instead of several roms that have bugs... That is not the case. We would just have less choice, the bugs would still remain, things like the camcorder and camera issues don't just get fixed overnight. It's nice to see peoples own twist on things, sad to see some people don't appreciate this..
cobrato said:
It's never wrong to share. If you don't like it, just don't download. It's that simple.
And from what I see, credits are given where it's due. Many don't even ask for donation. And they don't pretend to be a dev like J, Z & T.
Yes these are mods & tweaks. But some really did a nice job - like wolfbreak's rom - it's fast and stable with a great look.
It's always good to have choices. IMO their threads are much more useful than this thread which contributes nothing.
Of course you don't have to agree with me and I don't have to agree with you
Click to expand...
Click to collapse
Agreed with u...
+1
I personally would like the developers and the site to do the following.
1. Sticky the First Rom post from each guy, and only allow him to update it and a second post.
2. All comments, questions regarding it should be in a separate thread of the same title appended with [Discussion], which should be culled (or have a strike through put the heading) from the system the moment the dev releases a new version.
I for one, can not go through hundreds or thousands of posts most of which are not relevant any longer to the current version of the firmware/baseband whatever update. IT's very intimidating, and onerous on the reader- even professional IT people. I can't imagine what someone from a non-technical bent sent here by someone - "Hey you can get an update for that at XDA!" thinks when they encounter some of these 2,000+ plus postings.
The developers should take a bit of responsibility and update the first or second posts with any new issues that crop up from the discussions. You should not have to read 50 posts in to a thread to find out that there is a step missing in the install or a new bug has been confirmed. I've burned two X10's myself due to bugs and unclear instructions that were later corrected.
Meanwhile, I'm happy to support with money these guys, even though I have not actually put a 'custom' firmware onto any of my phones. I have put/used the tools that have been provided to do other things like JIT and rooting/updating SE firmware. I am looking forward to seeing a fully functional update to give me some of the things that are not available in 2.1 so I can get better applications. I think that not having some items like Hotspot, Tether and even 16m color on the display which require kernel updates are not that important since tether/hotspot can be added via applications in the market.
I don't think there can be a better example of why we don't need random people come up with ROMs [they're firmwares, NOT ROMs]
http://forum.xda-developers.com/showpost.php?p=11669817&postcount=97
In that thread, the main issue is not about giving or not giving credits, it's about calling oneself a 'Chef' and delivering half baked results which ultimately causes grief when users don't receive solutions to their legitimate queries/firmware related problems.
Guys (and girls ... if any are reading .. )
After some tinkering about (for days now) with Mango build 7720 (Thanks again YUKI + XBOXMOD!) I can confirm that the many of the issues present in Mango Beta are now gone ... Ok granted the MicroSD gets encrypted but its not meant to be removed on an original WP7! You can refer to Yuki's thread on how to unlock your MicroSD card if you don't fancy the likes Microsofts OS and want to revert back to Android .....
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way. Have been using it some years now on a daily basis. I am willing to provide my help. I hope that anyone could help along maybe we create yet another open source bootloader which does the trick.
Hoping to hear from you so we get something going ...
Regards
Al
I would really like to hear from some devs I am more than sure that the community would be very grateful.
Secondly (courtesy of warriorvibhu)
I suggest that you all Sign this Petition.. Kindly inform all fellow HD2 owners to sign it ... especially if they were impressed by WP7 on HD2.
Alcatrazx said:
Guys (and girls ... if any are reading .. )
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
No there are some issues in camera and sound with android but is related to incomplete kernel. They are not related to each other for example no multi touch issues on android. All those issues are related to not perfect drivers hd7 is using another touchscreen panel I guess and maybe different speakers and camera. Anyway those drivers are complexed to write because we dont get source from microsoft on how to write them.
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Theoritically yes but CLK is designed to load an linux kernel. So if we want that we need to write a complete new bootloader.
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
Yes but you need to go backt to Windows 6.5 and read out the current drivers and port them to windows phone 7 properly. But you will need a JTAG for it and you must be very skilled.
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way.
Hoping to hear from you so we get something going ...
Regards
Al
Question
Click to expand...
Click to collapse
Hope this make some stuff clear.
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
We need an asm developer for try to fix multitouch problem... or the source code of driver...
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Just hope that's will come soon, I cant wait it !
However, I also hope the Mango will worked with flash and include more apps in the marketplace.
Fisher_9511 said:
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Click to expand...
Click to collapse
Its not working in any of multitouch Games.
Nice thread,curious to See the answers, definitely camera is a big issue for me, hope it get fixed soon.
Sent from my HTC HD2 using XDA App
Dont forget the need to use the "batterytrick"
good thread by the way
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Try to think positive man... Have you ever seen the arm listed file? We need to find a timer between the two finger... would not be so so so hard... but only hard...XD
TonyCubed said:
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Click to expand...
Click to collapse
Hi and thanks for the feedback. With a negative attitude the thread will lead to nowhere yes. That was what people said a year ago when they said that WP7 will never run on the HD2 but the devs ultimately got there. Thanks for answering the question re the Android drivers though.
You are RIGHT that the drivers in WP7 are closed source drivers ... so is MAGLDR. Rewriting another bootloader (if needed) which does not have all the frills of MAGLDR but which is open source could be a possibility.
I am not interested in getting into the WP7 ROM and modifying the drivers built in ... We have to use a technique similar to what they use when creating emulators by reverse engineering ... The most die hard emulators out there such as some of the Playstation emus out there were all closed source but it did not stop the devs from doing a proper emulation of the console.
I'd really appreciate if you could be more specific when you said that we are using the stuff which was leaked from the original "LEO" ROM ... as far as I know, is it not the Schubert which was leaked? Correct me if I'm wrong ... We got too far to give up just now...
Multitouch games do not work .. with the current Multitouch driver .. mainly due to the finger position bug .... This is explained in detail on youtube.
Sound is distorted because the input gain is too high ...
Let's not speak about the camera for now ... I think those are the two major issues which need to be remedied for now. Hopefully this thread will get us somewhere.
Regards
Al
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
backlashsid said:
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
Click to expand...
Click to collapse
Nicely said and many thanks
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
Click to expand...
Click to collapse
That is not exactly fixing the issue... It just modifies the maxima and minima ... The sound (input gain) is too high making it sound distorted from the HD2. The fix does remedy this a bit but its ... erm not really fixing the problem.
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
dazza9075 said:
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
Click to expand...
Click to collapse
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
backlashsid said:
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
Click to expand...
Click to collapse
I'd say... let's do this! If we get enough people, and those will send emails like everyday, then why not? There's nothing to lose
IF, and its a big IF, we are going to get it working better its going to need ideas like the comment from backlashsid to get unofficial support from these companies
In my humble opinion there is little chance of getting anything else working better without the support of people in the loop, essentially that means HTC and Qualcomm, but remember that by getting the HD2 running WP7 we are costing them money in lost sales, so there is little incentive for them to support us in an official capacity, what we're looking for is an insider!
it doesnt hurt hunting for new devices with the same hardware but its unlikely anyone would use old gear.
This would be nice so then we (as the community of XDA) can show off our HD2's as the beast-mode phone and bestest phone ever!