Related
HTC S730 ('Wings'): Has anyone spotted it already?
It's now available on Tmobiles website:
http://www.t-mobile.com/shop/phones/Detail.aspx?device=acc8102d-4506-4eaa-bc2f-9c7b8ec1b1e0
I may walk over to the local tmobile store later and see if they have one. You thinking about switching from your Vox?
sting0r said:
You thinking about switching from your Vox?
Click to expand...
Click to collapse
Yeah, I'd like 3G (even though it drains the battery much faster).
And then supposably there is the 2nd video cam and a GPS receiver.
The cpu is apparently a Samsung running on 400MHz.
Combined with the same form factor as the S710 it sounds unbeatable to me.
Ah, that's the "Wing" in T-mobile's shop and is a different model.
The S730's nickname is "Wings"
Here's a preliminary spec:
http://handheld.softpedia.com/devices/HTC/HTC-S730--Wings-322.shtml
The release date is July '07
jockyw2001 said:
Yeah, I'd like 3G (even though it drains the battery much faster).
And then supposably there is the 2nd video cam and a GPS receiver.
The cpu is apparently a Samsung running on 400MHz.
Combined with the same form factor as the S710 it sounds unbeatable to me.
Click to expand...
Click to collapse
Where are you located, I don't think the US version has all those capabilities....
That's not the HTC wings
this is : http://pdadb.net/index.php?m=specs&id=728
T-mobile Wing looks like a TyTN to me
This S730 3G Windows Mobile Smartphone is vaporware right now
Everyone keeps saying it is coming out, but frankly, besides a photoshop'd mockup of this, there have been NO, repeat NO pictures of this in any form. No one has reported seeing one, no fuzzy pictures, etc. Until we get some information about this phone, some pictures, a release of info that is credible, I think that it's no where near release, and more like a Christmas time release at earliest. Seriously, why release the Vox, and then something that will blow it out of the water less than 6 months after the Vox release? It will cannibalize it's own market segment. I hope I am wrong, but with no pictures, or info on it, I don't see it as anything more than a future release, and nothing sooner.
Yes, it seems hard to imagine that they will release it so soon after the S710. However, there are different markets for both models. Don't forget that many users have no need for 3G, besides that the battery drains much faster. In that spec on pdadb.net it mentions only 12 hours! If that's true then many users are better off with the S710.
The Qalcomm MSM7200 chipset exists already since more than a year and does offer all those cool features. Usually mobile manufacturers need about a year to build phones around a new chipset. So from that point of view the timing could be right.
Here is more info about the chipset:
http://www.cdmatech.com/download_library/pdf/msm7200_chipset.pdf
http://www.cdmatech.com/products/msm7200_chipset_solution.jsp
Anyhow, I would love to test a S730
t-mobile wings
this wings phone does not have a front camera !!!!
HTC Wings is not the same as the T-Mobile Wings...
Check this blog: http://artedelcelular.blogspot.com/2007/09/htc-s730-successor-of-htc-s710.html
They found spectacular real photos of the upcoming HTC S730 Wings!
tocache said:
Check this blog: http://artedelcelular.blogspot.com/2007/09/htc-s730-successor-of-htc-s710.html
They found spectacular real photos of the upcoming HTC S730 Wings!
Click to expand...
Click to collapse
Wow ! But well i like the design on the S710 much more.. Wonder where they got them from ?
S730 have no gps but QUALCOMM chipset yes. Is deactived?
You can get the full product sheet here:
http://www.europe.htc.com/z/pdf/products/HTC_S730_PS_EN_280907.pdf
http://bp1.blogger.com/_Na8y0wPGxNE/RwKMgT2IGdI/AAAAAAAAAC4/aphncGBmKkM/s1600-h/GPS+on+S730.jpg
Looks like the S730 does have a GPS chipset but that it is disabled.
creamhackered said:
http://bp1.blogger.com/_Na8y0wPGxNE/RwKMgT2IGdI/AAAAAAAAAC4/aphncGBmKkM/s1600-h/GPS+on+S730.jpg
Looks like the S730 does have a GPS chipset but that it is disabled.
Click to expand...
Click to collapse
Yes, I'm sure I can enable it
htc-s730 samplese are shipped
gd day all here you can see the real pictures i hope you can understand your qestion from it and if not then u have to wait for some one to get his hands on sample whic are on the way now !!
http://www.boygeniusreport.com/gallery/handsets/htc-s730-unboxing
jockyw2001 said:
Yes, I'm sure I can enable it
Click to expand...
Click to collapse
D'you think the pic showing "active GPS" is for real or just a mockup?
GPS is a deal/no deal feature for me (in addition to the feeble battery... but as for the Vox there may be more powerful replacement batteries available).
Like for the Hermes there will most likely be a Wings100, Wings200... at least with different casing. Would a provider (like T-Mo Germany) be able to order units which are GPS hardware-deficient (lacking antenna, for instance)? For example, T-Mo Germany disabled (mechanically blocked!) the front videocall button of its "MDA vario II" Hermes variant.
How would one be able to tell if a specific S730 unit indeed has all necessary GPS hardware onboard?
Paquette said:
How would one be able to tell if a specific S730 unit indeed has all necessary GPS hardware onboard?
Click to expand...
Click to collapse
The chipset seems ok, see here. Don't know if other gps system components are built in.
jockyw2001 said:
The chipset seems ok, see here. Don't know if other gps system components are built in.
Click to expand...
Click to collapse
Thanks for the link. Looks ok, indeed. Please keep me posted if you find a way to activate the GPS feature. Will a registry hack do?
Does anybody recall how difficult it was to enable GPS for the Trinity?
Paquette said:
Thanks for the link. Looks ok, indeed. Please keep me posted if you find a way to activate the GPS feature. Will a registry hack do?
Click to expand...
Click to collapse
I claimed I can do, but I need the device in my hands first
Hi, as you know HTC (and all others) disallow call recording in their phones since the times of Windows Mobile 2003. This problem is now on the Android devices too. There are many opened issues on Google code for this problem, that gained a lot of stars, especially this one code.google.com/p/android/issues/detail?id=2117 (sorry, I'm new and not allowed to post links)
There are workarounds like recording trough loudspeaker, but as you know this is far from useful.
However, there is no official answer from Google about this "issue". However, last week the Koreans released a ROM for Samsung Galaxy S, that has built-in native call recorder.
This is from the Samsung's Hub:
Samsung has released a new update for South Korean Galaxy S (SHW-M110S) owners. The update DH09 is not a Froyo update but it does bring worthy additions to the handset. Few visible features are the inclusion of Swype keyboard, ability to record conversations and an app to detects the slope of the magnetic field sensor.
Other than that, the DH09 features RAM management, includes a 3G data widget, downloadable fonts and improves on many other fronts like Allshare, Google Maps software, call quality etc.
The update is available via Kies.
Click to expand...
Click to collapse
There is a screenshot as attachment (it's in Chinese):
Is there any way to break apart this ROM (DH09) and bring this or similar functionality to Froyo for Desire or Nexus or anything...?
Could you explain me where exactly is the problem for successful two-way call recording? Some say it's in the hardware, other think it's in the ROMs of the manufactures or in Android in general. However in Android emulators it works perfectly!
waooooo....someone please extract it
Anyone? Any answer? At least people who hacked WM ROM's to explain me where exactly is the problem for two-way call recording.
Call Recording is something very useful and I think is a "must have" function in today's world. However big companies and carriers are afraid letting people do that for legal reasons. That's why I think they will never allow us to do that out of the box, so we (the users) have to make it reality with custom hacked ROMs, like we did previously for Windows Mobile devices!
Anybody say something, please
The voice streams were handled by the baseband processor, it's that the baseband firmware aren't setup to offer the streams to the application processor that's limiting the ability to truly record a call. The Android system long has the API implemented, but it can do nothing in this case.
I remember there was an explanation in the Google code issue report mentioned above.
Here it's: http://code.google.com/p/android/issues/detail?id=2117#c226
Since the baseband firmware is close sourced and available in binary only, I doubt if the brilliant hackers here can do anything about this.
So, get a Galaxy S (the true one, not even those US variants) if you really want this feature.
Thanks for the reply. So, the bad guy is the baseband processor. iPhone guys hack the baseband processor of the iPhone to unlock it for different carriers. So, I guess it's doable to hack the firmware for two-way recording too.
I read here in XDA Devs that someone found a "cure" for HD2 very easily, just by editing the registry - xda-developers.com/windows-mobile/two-way-in-call-recording-on-hd2-fixed/
HD2 uses the Qualcomm’s Snapdragon QSD8250 processor with built-in baseband processor. The same is used by HTC Desire, HTC Dragon, HTC Mozart, Nexus One, Dell Streak, SE Xperia X10 and many more.
So, why with HD2 is so easily, but with Nexus is not? What is the difference when they use the same CPU with the same baseband processor built-in? Is the baseband firmware different for Android OS and Windows Mobile? If so, how they run Android on HD2 and the cellular is working?
Just my thoughts
I found TotalRecall on the Android Market and it records both sides of my conversations.
jamesmannes said:
I found TotalRecall on the Android Market and it records both sides of my conversations.
Click to expand...
Click to collapse
Many call recorders can record both-way, but only with the use of speakerphone. I suspect it's the same for TotalRecall, judging by the ratings of the 14-day demo (http://www.appbrain.com/app/total-recall-call-recorder/com.killermobile.totalrecall.trial)...?
mishoboss said:
Thanks for the reply. So, the bad guy is the baseband processor. iPhone guys hack the baseband processor of the iPhone to unlock it for different carriers. So, I guess it's doable to hack the firmware for two-way recording too.
I read here in XDA Devs that someone found a "cure" for HD2 very easily, just by editing the registry - xda-developers.com/windows-mobile/two-way-in-call-recording-on-hd2-fixed/
HD2 uses the Qualcomm’s Snapdragon QSD8250 processor with built-in baseband processor. The same is used by HTC Desire, HTC Dragon, HTC Mozart, Nexus One, Dell Streak, SE Xperia X10 and many more.
So, why with HD2 is so easily, but with Nexus is not? What is the difference when they use the same CPU with the same baseband processor built-in? Is the baseband firmware different for Android OS and Windows Mobile? If so, how they run Android on HD2 and the cellular is working?
Just my thoughts
Click to expand...
Click to collapse
I hope I have an answer but, getting the Galaxy S is still the most fool-proof way thus far.
jamesmannes said:
I found TotalRecall on the Android Market and it records both sides of my conversations.
Click to expand...
Click to collapse
Which phone you use? Which Android version? I hope you record the conversation without speaker turned on, right?
999phonebug said:
I hope I have an answer but, getting the Galaxy S is still the most fool-proof way thus far.
Click to expand...
Click to collapse
OK, does somebody tested the Galaxy S with TotalRecall or other call recording software? Is it working out of the box or do I have to preflash the ROM with the korean's one? And if I do, could I continue to use my phone normally and in English language?
mishoboss said:
OK, does somebody tested the Galaxy S with TotalRecall or other call recording software? Is it working out of the box or do I have to preflash the ROM with the korean's one? And if I do, could I continue to use my phone normally and in English language?
Click to expand...
Click to collapse
Ooops... I wasn't aware only the South Korean firmware has native support for call recording... I wonder if it's available in the latest 2.2/Froyo global release...?
999phonebug said:
Ooops... I wasn't aware only the South Korean firmware has native support for call recording... I wonder if it's available in the latest 2.2/Froyo global release...?
Click to expand...
Click to collapse
Any one know how to get the "real" Galaxy S? I have been searching the internet to no avail?
Can some Genius please tell me how to flash the new Korean Froyo http://translate.google.at/translate?js=n&prev=_t&hl=de&ie=UTF-8&layout=2&eotf=1&sl=ko&tl=en&u=http%3A%2F%2Fmatpclub.com%2Fboard%2Findex.html%3Fid%3Duser9%26no%3D5203 onto a European Galaxy S ? Thanks
airplus said:
Any one know how to get the "real" Galaxy S? I have been searching the internet to no avail?
Click to expand...
Click to collapse
Tried ebay?
dillovic said:
Can some Genius please tell me how to flash the new Korean Froyo http://translate.google.at/translate?js=n&prev=_t&hl=de&ie=UTF-8&layout=2&eotf=1&sl=ko&tl=en&u=http%3A%2F%2Fmatpclub.com%2Fboard%2Findex.html%3Fid%3Duser9%26no%3D5203 onto a European Galaxy S ? Thanks
Click to expand...
Click to collapse
Anyone????
there's an utility called AirVoice which claims to support voice recording without speakerphone on rooted g2 (htc magic) and g3 (htc hero) with certain ROM versions.
http://www.airrunner.cn/wordpress/
999phonebug said:
Ooops... I wasn't aware only the South Korean firmware has native support for call recording... I wonder if it's available in the latest 2.2/Froyo global release...?
Click to expand...
Click to collapse
No, it's not available in Froyo. This is only for Koreans. However the important thing here is that CALL RECORDING IS POSSIBLE on Galaxy S. As you stated in your first post, to record a call Android needs access to the baseband processor. Galaxy S uses own CPU called S5PC110 (ARM Cortex A8) with built-in baseband processor, which is different from the baseband that is used in the new HTC devices, SE Xperia and Droid. As we all know these devices doesn't work with the call recording apps on the Market. Samsung Galaxy S has really good chances to work properly with these apps!
SO, SOMEBODY PLEASE TEST!
999phonebug said:
there's an utility called AirVoice which claims to support voice recording without speakerphone on rooted g2 (htc magic) and g3 (htc hero) with certain ROM versions.
http://www.airrunner.cn/wordpress/
Click to expand...
Click to collapse
Nice! However for the EPIC STUPIDITY of the most users who gave low app rating, the author unpublished it from Market.
His app clearly shows that two-way call recording IS POSSIBLE, even on certain hardware and rooted Android. The author notes that his app only works on Hero and Magic. They use Qualcomm® MSM7000 and MSM7200, probably with the same baseband processor and he found a way to access it. I will try to contact him for more info and I hope some source code...
Hi,
I tried some apps like Ultimate Voice Recorder, Total Recall, Call Recorder, they all pick up sounds from the second you press dial so that you hear on the recording the phone ringing at the other side, and they stop a few seconds after the conversation starts. I cold hear on the recordings bouth sides, but no recording is over 10 seconds, no matter what settings I choosed. I didn't use the speaker mode.
Maybe some files need to be run as administrator...don't know... I'm new to android and don't know much about linux.
The other apps that claim to be able to record calls are designed for Android 1.6 so it may be possible but not with 2.1 or 2.2
As far as I understood from what I've read, the korean version of I9000 has also a different hardware not just firmware, so it might be more than just a software adjustment needed.
ccris said:
Hi,
I tried some apps like Ultimate Voice Recorder, Total Recall, Call Recorder, they all pick up sounds from the second you press dial so that you hear on the recording the phone ringing at the other side, and they stop a few seconds after the conversation starts. I cold hear on the recordings bouth sides, but no recording is over 10 seconds, no matter what settings I choosed. I didn't use the speaker mode.
Maybe some files need to be run as administrator...don't know... I'm new to android and don't know much about linux.
The other apps that claim to be able to record calls are designed for Android 1.6 so it may be possible but not with 2.1 or 2.2
As far as I understood from what I've read, the korean version of I9000 has also a different hardware not just firmware, so it might be more than just a software adjustment needed.
Click to expand...
Click to collapse
I presume you use Galaxy S, right? That what you said is really interesting! The fact that recordings contain both sides is very encouraging! The 10 seconds bug I guess is due to some rights or something. I don't own Galaxy S to do further investigation of this problem, but I hope somebody who own it and is deep in Android to do it.
I don't think the Koreans version has different hardware. At least it uses the same CPU, and that means the same baseband processor.
Any news...?
Galaxy S has:
Removeable SD Card
Ability to watch movies without converting etc
Can use 3.5 jack to see movies etc on TV - not sure if the nexus s can do this or not
Bluetooth 3.0 - But its better that it has 2.1 so you can use wiimote
Thats all I can think of off the top of my head if anyone has any other things id like to know.
barmanham said:
Galaxy S has:
Removeable SD Card
Ability to watch movies without converting etc
Can use 3.5 jack to see movies etc on TV - not sure if the nexus s can do this or not
Bluetooth 3.0 - But its better that it has 2.1 so you can use wiimote
Thats all I can think of off the top of my head if anyone has any other things id like to know.
Click to expand...
Click to collapse
13GB SD card internal is more than enough for most people.
between all the streaming apps coming, and the apps on the market for playing divx, it shouldn't be an issue.
3.5 tv out should work, if not then most likely someone will write an app, or code a stock rom that includes the function.
meh. 3.0 is alright, but as you said, no wiimote and it has other issues as well.
barmanham said:
Galaxy S has:
Removeable SD Card
Ability to watch movies without converting etc
Can use 3.5 jack to see movies etc on TV - not sure if the nexus s can do this or not
Bluetooth 3.0 - But its better that it has 2.1 so you can use wiimote
Thats all I can think of off the top of my head if anyone has any other things id like to know.
Click to expand...
Click to collapse
Realistically its all preference
barmanham said:
Thats all I can think of off the top of my head if anyone has any other things id like to know.
Click to expand...
Click to collapse
SIM-lock and crapware?
much better video camera, 720p and suport for various codecs
I'm willing to bet the actual camera sensor in the Nexus S is identical to the Galaxy's. From pictures, the aperture looks the same, and also reviews of the Nexus S have noted how well the low light performance is, which is similar on the Galaxy S. I'm quite certain the lack of 720p is merely a software limitation rather than hardware being different... but of course this is all speculation.
Igor 3 said:
much better video camera, 720p and suport for various codecs
Click to expand...
Click to collapse
it seems that still pictures are decent enough but video samples are terrible, for example this, http://www.youtube.com/watch?v=rDDn-MXzd3U in the background i truly cant tell whats on the video. There are many more examples on you tube, I hope they can fix it.
All "HD" video shot with cameraphones is terrible anyway. You're better off shooting in 480p.
mortzz said:
All "HD" video shot with cameraphones is terrible anyway. You're better off shooting in 480p.
Click to expand...
Click to collapse
Have you seen the Vibrant's video capabilities? I highly doubt it based on your comment. While the pics on it are average, the video it takes is EXTREMELY good.
I bet the lower capability video camera on the S is due to the lack of a SD slot.
a working GPS
maybe..
Wi-Fi proxy support, Swype bundled
ekerazha said:
Wi-Fi proxy support, Swype bundled
Click to expand...
Click to collapse
yeah, i forgot to ask. I didnt see swype in any of the review. Is it possible that they even took that out?
What do you mean "took it out"? Swype has never been a part of Android, it is a carrier/manufacturer add-on.
There was a video review that showed what writing options the Ns came with, and Swype was not one of them - in fact, it only had Android Keyboard. Forgot which video.
BTW, what's the deal with Bluetooth 3.0 and the Wiimote? What happens, it prevents the Wiimote from working? I've never heard of this.
Third-party apps for WiiMote pairing do not work with Bluetooth 3.0 (or some skins, such as HTC Sense)
-TouchWiz
-Broken GPS
-Sim Locks
-Laggy RFS Filesystem
-Internal Storage Failures from trying to replace Laggy RFS Filesystem ( androidcentral .com/bell-samsung-galaxy-s-phones-dying-bad-hardware-or-bad-hacks )
-Froyo (Or in some cases, Eclair)
-Lack of official Google branding/support
-Lack of AOSP support (Which is why there's no official CyanogenMod release for Galaxy S Phones)
AndroidZ28 said:
What do you mean "took it out"? Swype has never been a part of Android, it is a carrier/manufacturer add-on.
Click to expand...
Click to collapse
yeah, but somehow i hoped that when they team up with samsung they would bring over all the goods samsung (galaxy s) has to ofer (excelent camera, swype, codec support etc.). But they brought nothing except super amoled and plastic design.
Who knew that removing features would make the device better? =)
BlackOtaku said:
-TouchWiz
-Broken GPS
-Sim Locks
-Laggy RFS Filesystem
-Internal Storage Failures from trying to replace Laggy RFS Filesystem ( androidcentral .com/bell-samsung-galaxy-s-phones-dying-bad-hardware-or-bad-hacks )
-Froyo (Or in some cases, Eclair)
-Lack of official Google branding/support
-Lack of AOSP support (Which is why there's no official CyanogenMod release for Galaxy S Phones)
Click to expand...
Click to collapse
Igor 3 said:
yeah, but somehow i hoped that when they team up with samsung they would bring over all the goods samsung (galaxy s) has to ofer (excelent camera, swype, codec support etc.). But they brought nothing except super amoled and plastic design.
Click to expand...
Click to collapse
Well, If Swype wants to open source it's keyboard, I'm certainly interested.
The one thing that matters most in a phone: ability to make calls when you're not in town or on a major highway. I.E.-a decent provider I.e.-Verizon
Sent from my SCH-I500 using XDA App
I have tried several apps with multitouch (Phone Tester, android-multitouch-controller...), all of them show that the gtablet has a maximum of 2 touch points in the gtablet.
I am using the Vegan-tab 5.1, anyone has better results? Is it a hardware or a software limitation?
Dont know if its a hardware limitation, but as I posted in another thread before, this is "normal" imo. I have tested a Droid, Droid Inc, Evo, and the Gpad. Every device else Evo, has 2 finger detection. Evo has 5.
Cheers
Htc G2 has 4 finger detection just fyi
Sent from my T-Mobile G2 using XDA App
Wrong section I would think..
xBANGx said:
Wrong section I would think..
Click to expand...
Click to collapse
not if its a software limitation and there is opportunity for development...
renau said:
I have tried several apps with multitouch (Phone Tester, android-multitouch-controller...), all of them show that the gtablet has a maximum of 2 touch points in the gtablet.
I am using the Vegan-tab 5.1, anyone has better results? Is it a hardware or a software limitation?
Click to expand...
Click to collapse
I've already looked into this in the kernel source code, if that's what you're asking.
It's hard to know for certain, but it appears to be a limitation of the microcontroller code for the touchscreen subsystem, based on the at168 driver code. The raw capacitive sensor readouts are done by this microcontroller, translated into up to two sets of X and Y coordinates, and read in by the driver.
There is some unused data in there - the driver is relatively simple, and we could try debug dumping out everything it can read from the Atmel chip, and see if some of that unused data could prove useful, but I am skeptical that we'd have any luck without re-programming the Atmel. That requires a microcontroller person to figure out, not me.
pmcnano said:
Dont know if its a hardware limitation, but as I posted in another thread before, this is "normal" imo. I have tested a Droid, Droid Inc, Evo, and the Gpad. Every device else Evo, has 2 finger detection. Evo has 5.
Cheers
Click to expand...
Click to collapse
Evo has either 3 or 5, depending on the touch controller revision (literally 4 characters of hex). I got pwned when I traded in my faulty 002/Nova/.76hboot for my new 003/Nova/2.02hboot... LAME.
Anyway, toastcfh did a thread on it back when they were first figuring the evo out.
Moved to general
mmm. Interesting. The kernel has the option to load new firmware to the atmel chip. These are fairly easy to program, the problem is that we do now have the original code.
Did anyone find specs about the display? If this at164 chip just does the touch display, it may be possible to recreate the firmware if we have the hardware specs.
It may be interesting project,
The at164 kernel code only handles 2 touches, but if you see the driver capabilities (AT168_Capabilities), it sets the handler to 2 fingers *MaxNumberOfCoorReported". This value is written to th nvram that the AT168 reads.
Did anyone tried to change this value? (Something like 4)
The AT128 I2C registers may change when the NVRAM changes. If I were the designer I would have read the capability, and added as may AT168_X/Y pos as necessary. This will shift the registers, but it may be interesting to check.
I have the 002 Evo model and I only have 2 touch points. I would love to have more for certain apps that use more. Is there a fix for this? I've seen many people say that their Evo has 4 or 5 points. Is there a way to update to a newer version?
So I've been doing research on the Gtab on this issue because although it's a great device, I really want something that can do more than 2 inputs. so far what I've found is that the touch sensor in this device is the tango S32 controller shown by this thread:
http://forum.xda-developers.com/showpost.php?p=10062618&postcount=134
http://img171.imageshack.us/img171/149/digitizerx.jpg
I found the companies main website and found some interesting facts about the chip. Firstly they don't have a number of touch points listed and it also says the max screen size the chip handles is 5" (maybe this is compensated because the gtab has 2 S32 chips).
http://www.pixcir.com.cn/e-product.asp?classId=2
http://donar.messe.de/exhibitor/007...1/links/20090226153411-DS TANGO-S32 Brief.pdf
All the videos I've seen concerning the s32 chip have only shown 2 touch points and knowing that there are plenty of android devices on 2.2/2.3 that support more than 2 points I believe I've come to the conclusion that the Gtab is limited to 2 points at a hardware level.
Anyone want to confirm or deny?
ICS 4.0.1: https://groups.google.com/forum/#!topic/android-building/T4XZJCZnqF8
well... good to hear that. but hopefully got some pro devs able to port for us then people like me beginner able to try do something on it... hehehe...
e.japonica said:
well... good to hear that. but hopefully got some pro devs able to port for us then people like me beginner able to try do something on it... hehehe...
Click to expand...
Click to collapse
It's going to be somewhat annoying to port, since Google changed the hardware interface (camera, gps, lights, etc.) again apparently for no good reason. This means most existing 2.3 proprietary libraries cannot be used as-is (in particular libcamera and libaudio) -- instead I guess generic wrappers will have to be developed, much like the existing gpsshim.
EDIT: I may have spoken too quickly -- it could be easier than I previously thought.
Hopefully, if we can get a official CM support / ROM, we will be able to go to ICS.
I'll try to see if I can port a version o the ChaCha.
that would be awesome if you did
Longer way for chacha to ics, imho
Sent from my HTC A810e
Download ICS surces and SDK tools..
Am gona give it a try
Can someone give me complete hardware specs (technical) of the chacha ??
abraham89 said:
Download ICS surces and SDK tools..
Am gona give it a try
Can someone give me complete hardware specs (technical) of the chacha ??
Click to expand...
Click to collapse
What do you mean by technical?
Hardware version
0128
Processor
800MHz
Memory
512MB
Display
2.6inch HVGA resolution
Main camera
5M
Front camera
VGA
Wi-Fi
802.11 b/g/n
Bluetooth
3.0
e.japonica said:
What do you mean by technical?
Hardware version
0128
Processor
800MHz
Memory
512MB
Display
2.6inch HVGA resolution
Main camera
5M
Front camera
VGA
Wi-Fi
802.11 b/g/n
Bluetooth
3.0
Click to expand...
Click to collapse
thats the basic configuration right ??
I meant, like the different chips in the device.. Like the Wifi chip Model, etc..
Isn't it all needed to compile an ICS build ??
I am a total beginner.. But since ICS could be ported to the G1 and Nexus one and other low end devices, why not for our chacha ??
WE NEED SOME SERIOUS COMBINED KNOWLEDGE AND EFFORT GUYS !!!
i guess adlx.xda the maker of ROM SuperOSR and CyanogenMod7 on HTC ChaCha.
will have more knowledge on this xD
e.japonica said:
i guess adlx.xda the maker of ROM SuperOSR and CyanogenMod7 on HTC ChaCha.
will have more knowledge on this xD
Click to expand...
Click to collapse
The CM7 port is made by xdbg.
Alex C. said:
The CM7 port is made by xdbg.
Click to expand...
Click to collapse
sorry my bad