I know there is tons of threads on this. I understand CM6 is basically all we got. Right? CM6 is great and all... But the lack of 4G is a killer, i use it frequently. So i just cant live without it... Its nice to have when you are downloading Big ROMs (psx) for the emulators our phone is so good at playing.... But, DAMN did I love the Wiimote support on CM6! It basically made any other form of Emulation obsolete for me. CM6 is a godsend for emulators... But it lacks the bandwidth I need/want to download ROMs (among other things I.E. Youtube HQ).
It seems like i got to choose between 4G and Wiimote support. Why cant we (functionality) all get along, the EVO can do it. But, Why can't it do it at the same time?
So my question is... How do I get Wiimote support and 4G on my EVO? Does anyone have BOTH of these capabilities?
Btw, my current ROM that i have been nestled into for about 3 weeks is VaelPaks ROM. And I'm getting itchy to Flash something new, but only if it meets this criteria.. or I wont be making an upgrade in my eyes... Doesn't anyone else feel the same?
4G was cobbled and spliced together by HTC. There's no good documentation on how to implement it and HTC is not required to release the source code or any documentation to support 4G. The only way to enable 4G in a ROM like CM is to essentially reverse engineer it - not an easy task. The Evo is also only one of 2 phones released so far with 4G. Worse still is that Sprint is using WiMax technology and is thus far the only significant carrier in the world to commit to WiMax. Pretty much everyone else is going with LTE, so there will be less development on WiMax devices.
The HTC software that comes with working 4G also comes with HTC's special Bluetooth software. The HTC Bluetooth implementation does not include the Bluetooth HID support that is needed for wiimote or keyboard support. Unfortunately, it's also not a simple matter of replacing the Bluetooth software because HTC's Sense permeates the Android system and doesn't play nice.
Based on the way things are going, CM6 is your best bet for eventually getting wiimote and 4G in one ROM. Sadly, 4G support was dropped from the upcoming 6.1 release of CM. Development of 4G probably won't start again until 6.1 is finalized. Personally, I'm worried that Cyanogen will end up working on other devices (e.g. the T-Mobile G2) or that Gingerbread will be released. The longer that CM goes without 4G support, the less likely it will ever happen. Eventually the Evo will become obsolete or at least, a lower priority.
Another possibility is to look into dual booting 2 ROMs. Not nearly as good a solution as having it all in one ROM, but certainly less time consuming than nandroid.
Related
I don't know what else you could really change in android to make it better other than updates for software outside of it's reach (flash,html, that stuff) but they are more than likely rolling out newer firmwares in the future.
Now my question is do you think us new G2 owners will get the update when it comes out? I've heard that it's only on stronger chipsets (namely 1ghz) even though we're on a second generation cpu we're not exactly up to par. Also not to mention, if history repeats itself we may not get the full package like the predecessor G1. (only went to 1.6) while it's almost identical twin the MyTouch 3G recently got a 2.2 update.
Anyways what do you think will happen?
1 ghz was never required, just recommended. Once the source is released I'm sure Cyanogen will merge it into CM.
Also, the G2 can be superclocked!
Hi all,
I have Palm Treo 700p's and want to update a bit without losing my fair and flex
family plan with Sprint; unfortunately Spring says I can't upgrade to any of the
phones that natively run Android,
I learned about flashing HTC phones running WM and have been trying to learn.
Trying to decide between the Touch or Touch Pro which seem to be the newest
HTC phones I can use.
It appears that the Touch had the best support but the developers have moved
on and the Touch Pro may now be getting more support; do I read this correctly?
Which would you recommend, Touch or Touch Pro, or is there another phone I
should check with Sprint for use?
I welcome your input
Thanks
FS
You're going to be very disappointed if you expect either of these phones to run Android natively well.
This port isn't nearly done. Perhaps the only phone (to my knowledge) that could be considered complete is the HTC Vogue - which is ironically the original Touch you are probably speaking of.
The TouchPro IMHO is a better phone (the keyboard is fantastic - only better is on the TP2 ) but does not run Android very well. Android is just a plaything, for testing and for fun on most WinCE devices.
To sum up - the Vogue & the HD2 have the most complete port of Android, with the Vogue probably being considered "completely finished" (full NAND), however... that hardware is old. HD2 is very promising, they have a few little bugs to squash and then NAND... But no HD2 love for Sprint.
Not sure how good of an Android experience it is on the Vogue. Won't ever be that fantastic on the TP or TP2 tho.... Old hardware there as well my friend
I was in the same boat. have a great (cheap) old data plan that I was not willing to give up.
I went with a touch diamond. My previous phone was a vogue.
I can say that the diamond is a far better phone than the vogue. Better screen, more responsive touchscreen, better video, accelerometer, better camera... but the Vogue probably does better with Android since it can run Android from Nand instead of the storage (SD) card.
Android is fun on the Diamond, but its pretty crippled. No camera. No speakerphone for things like GPS. Poor battery life. Too slow for any flash apps to run fluidly... Basically android on the Diamond feels more like an emulation- because that is all it is.
That said, its fun to be able to play around with android, and WinMo is not so bad for a dead OS. There are some decent ROMs and plenty of freeware still floating around. And the Diamond makes for a nice phone on terms of small size, GPS, good speakerphone, WIFI and even WIFI sharing with the right ROM.
tk76 said:
I can say that the diamond is a far better phone than the vogue. Better screen, more responsive touchscreen, better video, accelerometer, better camera... but the Vogue probably does better with Android since it can run Android from Nand instead of the storage (SD) card.
Android is fun on the Diamond, but its pretty crippled. No camera. No speakerphone for things like GPS. Poor battery life. Too slow for any flash apps to run fluidly... Basically android on the Diamond feels more like an emulation- because that is all it is.
That said, its fun to be able to play around with android, and WinMo is not so bad for a dead OS. There are some decent ROMs and plenty of freeware still floating around. And the Diamond makes for a nice phone on terms of small size, GPS, good speakerphone, WIFI and even WIFI sharing with the right ROM.
Click to expand...
Click to collapse
Just to set the record straight, this project is running natively on the hardware - it's not a virtual machine, and it is certainly not being emulated in any way shape or form...
I could see how you would think that, because of all the broken/not working stuff... Well we just have to reverse engineer WinMo libs, dlls, etc and then write our own drivers basically for the different pieces of hardware.
Hence the reason new kernels come out so frequently - there's a lot of work that needs to be done on that kernel to get everything working the way it should. Devs are making some good progress lately, hopefully DIAM/RAPH will have NAND soon. I heard Neopeek was working on NAND back in August on his DIAM... haven't heard much about it since unfortunately. However, RHOD's have a partial NAND, and with the head of steam we've got going now, I'm pretty confident soon we will be up to the level of the Vogue - if not beyond it. However, the processor/RAM specs are pretty paltry compared to most native Android devices.
Sorry for the damned long post. One last question, your speakerphone doesn't work in GPS? Hrm. It should. Have you tried the newest kernels...? The autobuild service is down, but F22's been kindly building them for us...
why not just get a NEWER phone other then one that was released 2-4 years ago?
Cause after having invested SO MUCH time into running android on the phone, it's impossible to give up.. And having full control over hardware compensates for the hardware being ancient
Aaron McCarthy said:
why not just get a NEWER phone other then one that was released 2-4 years ago?
Click to expand...
Click to collapse
Because moneys doesn't grow on the trees..
HELICOPTER88 said:
Because moneys doesn't grow on the trees..
Click to expand...
Click to collapse
Exactly! Or I would have had a nexus 1 a long time ago... ;D
e334 said:
Exactly! Or I would have had a nexus 1 a long time ago... ;D
Click to expand...
Click to collapse
and I would have had a Desire...
Hi please remove this if it is not in the right place. Ok so i was in the Magic forum and i found that they have a Honeycomb rom in the making. Since the Magic has a mdpi screen i thought it would be nice to port it on to our Silde. Now with that in mind is there a dev out there that may want to guide me through the porting process? I have permission by the dev of the original rom to port it once it comes out. Any help would be much appreciated.
Original thread:
http://forum.xda-developers.com/showthread.php?t=974038
Thats possible? I thought the core of honeycomb was built to run on tablets purely
Sent from my T-Mobile myTouch 3G Slide using XDA App
I thought that too but devs started to ported to HDPI phones like the N1 and NS but I didn't think I see on our MDPI phones until I came over this thread... hopefully someone can help me port it over
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
but the slide's screen is micro sized compared to a tablet.
any phone, for that matter doesn't have the proper screen real estate to take advantage of honeycomb features
maybe the dell streak. maybe....
I agree, 3.0 was designed as a tablet OS, not a phone OS.
Like the post above me says, no phone really has the resolution to take advantage of things like tabbed browsing and other tablet features, at least not efficiently or realistically. Plus, seeing as most tablets are at LEAST 800 mhz, most being 1 GHz or more, it probably would run slower than froyo and gingerbread on our phones. It probably would use a lot more RAM/CPU/GPU resources, making the whole system overall laggier. I think it might be cool to have a honeycomb ROM, but honestly, it's not very practical, it may not be worth it.
You may have a point but I'm doing it to support the Slide community which is slowly being traded for other phones... plus I think ill be pretty cool to run honeycomb on my Slide
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Yeah it would be cool, and it would be an addition to a slow community. Go for it, if it can be built for the magic, surely it can run on our phones, seeing as our phones are from a later generation of android devices than the dream/magic/sapphire.
Im just asking for some assistance considering that dev skills have not been developed yet and was hoping that this task would help me there.
izzy001 said:
You may have a point but I'm doing it to support the Slide community which is slowly being traded for other phones...
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
lol, i just joined the slide community last week.
and i'm here to stay. go for it!
This is vid of it on G1...
http://www.youtube.com/watch?v=-RKEHfOwnSI&feature=player_embedded
Guys it is more like a proof of concept. It will be fun to run it to show off or to look at honeycomb but I'm sure it is not meant to be a daily driver for any phone. I would love a HoneyComb ROM and I could test it for you (I know adb, fastboot, and I can get logcat for you if needed).
If it can run on G1 I bet it can run on our slide (I'm not saying full speed but at a decent speed to mess with the ROM)
If it can run on G1, it will be much smoother on Slide because we have a better CPU and a much better GPU than G1 has. And we also have 320Mbs more RAM.
I have to wait till they release the alpha rom so that i can start messing with it
hey all
i just wanted to get some of your feedback regarding the Evo 3D and the love/lack of love it will get from the development community.
I love the specs on it, but the new 3D technology and display seems like it could be hell AOSP devs to create roms for.
For example, it took nearly 9 months to get 4G fully working on CM (which i love and appreciate b/c it's been my daily driver since my G1). So i feel like the same type of delay would be in effect for all the new technology the 3D will have, such as the dual 5MP cameras.
Anyways, i could be completely off on my analysis of this.
The thing is, i would consider an upgrade to the 3D purely based off the dual core processor and other specs. But, if i can't have a functional, nice CM build for it, i honestly don't think i would go near it.
opinions?
bweisholtz said:
hey all
i just wanted to get some of your feedback regarding the Evo 3D and the love/lack of love it will get from the development community.
I love the specs on it, but the new 3D technology and display seems like it could be hell AOSP devs to create roms for.
For example, it took nearly 9 months to get 4G fully working on CM (which i love and appreciate b/c it's been my daily driver since my G1). So i feel like the same type of delay would be in effect for all the new technology the 3D will have, such as the dual 5MP cameras.
Anyways, i could be completely off on my analysis of this.
The thing is, i would consider an upgrade to the 3D purely based off the dual core processor and other specs. But, if i can't have a functional, nice CM build for it, i honestly don't think i would go near it.
opinions?
Click to expand...
Click to collapse
I am certainly no developer but the existence of the Nexus S 4G should help to iron out any 4G issues that are left and make 4G available in any EVO 3D AOSP builds. AFAIK, I believe the biggest reason behind the delay in 4G for the EVO was that they basically had to build it from the ground up since they didn't have any AOSP source to modify for it.
As for the developer support, I was wondering the same. I really want the EVO 3D but I don't want to get stuck in a position like all the Epic users are with little developer and no CM support. I hate waiting but I might wait to see how much love each of the new phones gets before deciding which one to go with.
Chances are that since the Nexus is supposed to be released first and there is already a version available, that will be the phone that many people flock to. I had actually considered PM'ing a couple of my favorite developers (Toast, Flipzmode, Myn) and see what phones they were leaning toward. I think that the ease of rooting might also be a factor. If HTC and/or Samsung end up locking the phones down real tight, that might end up swaying some people one way or another.
Check out the Evo 3d forum...
http://forum.xda-developers.com/forumdisplay.php?f=1095
They just made it a few days ago so I don't think it shows up on the xda app yet.
Sent from my PC36100 using XDA Premium App
xHausx said:
Check out the Evo 3d forum...
http://forum.xda-developers.com/forumdisplay.php?f=1095
They just made it a few days ago so I don't think it shows up on the xda app yet.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just looked at it, it looks like joeykrim and toastcfh are in which means, at the very least, the thing will probably be rooted before it's released. And if anyone can get the 3D thing figured out, TeamWin can.
I'm currently on the Samsung Epic 4G (OG, not touch). I'm switching from Sprint as the service is lacking in my neighborhood (and work is footing the service bill).
I read that Verizon was going to lock the bootloader, but I also know that chainfire has a root solution (dunno if that will bypass Verizon's shenanigans).
The dev community for the Epic has been AMAZING in making things work (such as AOKP, Paranoid Android and CM10), despite the limitations they've faced (lack of official support (CM in the early days), having to port updates from the Nexus, etc)
Is the Note II looking to be a good phone for flashaholics?
Thanks,
Drew
simple answer no. until samsung opens up the source for many things on these phones the support is very very poor. the best developers of the CM team will not even touch this device because of the lack of source. it's just too difficult without it. it's not looking good. only time will tell.
maybe
rumor has it that there was some good communication between some devs and the exynos folks at android bbq, so maybe it will pan out
This question might be dumb, but since AOSP might be some time away, how much of TouchWiz can be replaced so far? My wife has a Captivate Glide with ICS and I installed Nova, but there's still just so much hideous Samsung UI... the pull down, the menus, the drawer, etc.
nutpn said:
rumor has it that there was some good communication between some devs and the exynos folks at android bbq, so maybe it will pan out
Click to expand...
Click to collapse
that's the problem. they are going to release some exynos sources but this doesn't mean it's what we need to get everything going i'm hoping for the best! we need AOSP for this beastly phone!