This thread has gone on a different approach on resolving this, so I'll be setting aside my old post (I wont be deleting them for some reasons). Everything under the hash army (###) in this single post is about getting the Spica stuff on the O1. We moved to focusing on the O1's ts driver itself.
Other note: Fixes are independent. Choose whichever works for you. A universal fix may come in the future though (Tell me if this post still confuses you. I'll edit ASAP)
Multitouch axis inversion fix (First release: Feb 6, 2011): Forum member waleedq came up with a workaround that inverts the inversion. This seems very straightforward, and it works. Please note, however, that this is a workaround and not a fix. As always, do a backup.
Stuff you should know:
- Most of us who tried it (inc. me), lost our OC.
- mik_os' touchscreen lag fix is here. Tested it with Android Status while touching the screen.
- Axis inversion is still a problem. Check video 2.
Videos: http://forum.xda-developers.com/showpost.php?p=11178060&postcount=67
Link to the download link: http://forum.xda-developers.com/showpost.php?p=11166426&postcount=47
waleedq's source: https://github.com/waleedq/ThunderG-Kernel/blob/thunderg_oc/drivers/input/touchscreen/mcs6000_ts.c
Faster readout fix (First release: Feb 8, 2011) : Der_Caveman released for testing a kernel with some delay fix (modified from stock kernel). Apparent goals were to make touchscreen input readouts faster. Also, useless and non-working functions that doesn't work were removed. No CPU spike (somewhere around 30%cpu use when touching screen)
UPD: v3 is based on drellisdee's kernel source, so yes, it's OCable.
Link to download link: http://forum.xda-developers.com/showpost.php?p=11195243&postcount=84
Link to download link(v3): http://forum.xda-developers.com/showpost.php?p=11221504&postcount=126 or a forum upload http://forum.xda-developers.com/showpost.php?p=11230915&postcount=137
Changes and stuff: http://forum.xda-developers.com/showpost.php?p=11206827&postcount=91
Touchscreen optimization + axis inversion workaround(First release: Feb 10, 2011):Der_Caveman and waleedq's work combined by Sippolo.
Link to download link + source + details: http://forum.xda-developers.com/showpost.php?p=11256797&postcount=198
Link to download link + source + details (v1.1): http://forum.xda-developers.com/showpost.php?p=11270721&postcount=237
#########################################################
Okay, so I just recently found out that the Galaxy Spica (was supposed to choose it over the O1 --') -unofficially- supports multitouch.
A link to the driver's was PMed to me by adi4motion:
https://github.com/Gabriel-LG/i5700-multitouch-kernel
Anyway, is it possible that we could implement their method on our drivers? I understand that there might be some hardware differences between the two. I'm just trying my luck
Lastly, for sample videos, check YouTube. I have to say that the performance with those drivers really are impressive (well, I saw the axis invert once)
https://github.com/Gabriel-LG/i5700-multitouch-kernel/tree/master/drivers/input/touchscreen
I didn't find any melfas drivers in there- so I doubt that the Galaxy Spica has a melfas touchscreen controller in it.
But it's possible that we could write a driver based on those, right?
only kpbotbot can do tht and i hope he does
What about O1 brother the LG Chic? Does it have the same issues?
Sent from my LG-P500
ccdreadcc said:
only kpbotbot can do tht and i hope he does
Click to expand...
Click to collapse
Sorry, can't code. But I assure you, I'm trying my best not to just leech (And I'm still figuring out how to compile FroYo to learn how ROMs get born)
N3mesis said:
What about O1 brother the LG Chic? Does it have the same issues?
Click to expand...
Click to collapse
There may be a guy here in the forum that has the Chic. Maybe he can test out the inversion issues (If you're reading this and you have the Chic, please test if the axis inverts using a tool like touch test xD)
kpbotbot said:
But it's possible that we could write a driver based on those, right?
Click to expand...
Click to collapse
In the O1 a melfas MCS6000 touchscreen controller reads the capacitive touchscreen. The controller itself got a proprietary firmware in it (don't know if its from melfas or LG)- you can find that somewhere in the system folder (melfas.bin(?)). Then there is the LG kernel driver which "interacts" with the melfas controller ic- it also has the ability to flash the melfas controller.
So if there is a problem in the MCS6000 firmware- we're most likely screwed, because lack of datasheets.
Furthermore I want to know how android gets the multitouch data. Maybe the android interface itself is not that multitouch friendly?
The easiest way would have been that each finger represents a "mouse event", but I doubt that this way was chosen...
I see. Is it possible to decompile that .bin somehow? I know, that question might sound stupid xD
I too did a search for melfas related stuff including source codes and the like. The only stuff I found was about Samsung phones having the same touch screen.
Let's just hope (for now that we cant do anything about it) that LG -at least- releases an improved version of their drivers for their 2.3 update
Update: The Chic has the same problem :/
http://forum.xda-developers.com/showpost.php?p=11014035&postcount=5
Maybe the axis inversion is somehow also android related.
Multitouch is something new for linux.
Der_Caveman said:
Maybe the axis inversion is somehow also android related.
Multitouch is something new for linux.
Click to expand...
Click to collapse
I think is just the crappy touch controller that's installed on our device; It can't spot more than 2 touches, and has got axis inversion. So I don't think there's so much to do with drivers
kite86 said:
I think is just the crappy touch controller that's installed on our device; It can't spot more than 2 touches, and has got axis inversion. So I don't think there's so much to do with drivers
Click to expand...
Click to collapse
LG only implemented "two fingers"- one can read that in LG's sources.
Again: axis inversion could also be android related (if android only requests coordinates without "finger assignments" bugs are preassigned).
I don't really care whether it would accept more than 2 presses That would be awesome for people doing extreme gaming with the phone, but with normal use it's awkward to use 3 fingers.
I bet the axis inversion issue is very much fixable. We just don't know how yet. But considering the fact that the Spica has less of this as a problem, we might fix it a bit, or completely fix it.
This is just my opinion though. I saw some guy explain multitouch with an illustration.
Wow, I have found this:
http://www.mjmwired.net/kernel/Documentation/input/multi-touch-protocol.txt
Just had to open my eyes
Let's see...
kpbotbot said:
I bet the axis inversion issue is very much fixable. We just don't know how yet. But considering the fact that the Spica has less of this as a problem, we might fix it a bit, or completely fix it.
Click to expand...
Click to collapse
You are 100% sure that the Spica does not have "the axis inversion bug"?
Der_Caveman said:
You are 100% sure that the Spica does not have "the axis inversion bug"?
Click to expand...
Click to collapse
I'm 100% sure.
I talked to a guy who used to own the phone. He said the drivers perform well.
I didn't say that there really was no inversion. It happens less (inverted once on the video I watched)
kpbotbot said:
I talked to a guy who used to own the phone. He said the drivers perform well.
I didn't say that there really was no inversion. It happens less (inverted once on the video I watched)
Click to expand...
Click to collapse
Ok, then I would say there is hope.
Der_Caveman said:
Ok, then I would say there is hope.
Click to expand...
Click to collapse
I sure do prey that someone will take this project and fix the driver or write it from scrath. As i can see the code is not that long
our driver
https://github.com/mik9/ThunderG-Kernel/blob/master/drivers/input/touchscreen/mcs6000_ts.c
spica's driver
https://github.com/Gabriel-LG/i5700...4461c4a3d4e2be0b5f4b1a94b451604c6541f1#diff-0
I have 2 months of doing absolutely nothing at home (stopped this sem. doctor said i have to rest. and yes, I have a life xD), so I might be able to understand a bit of the code. It really isn't that complex, but my lack of programming knowledge hinders me from modifying the code.
However, I sure do hope that someone figures this out
Related
See http://www.corecodec.com/forums/index.php?topic=596.0
sounds coool, I wonder how they want to fix the misssing driver support...
If you read the explanation posted on that forum -
The issue was that they used something called QTV for overlay (undocumented qualcomm driver).
Click to expand...
Click to collapse
I'm assuming "they" is HTC, which suggests that the driver support isn't missing, it's just not working very well, and Coreplayer have switched to something else.
G Reat News
That is very interesting also for all the future users of Polaris too!
Boinng said:
If you read the explanation posted on that forum -
I'm assuming "they" is HTC, which suggests that the driver support isn't missing, it's just not working very well, and Coreplayer have switched to something else.
Click to expand...
Click to collapse
Yes, maybe they are NOT missing (as some people have said) and this is the first app that actually uses the correct calls.
Can we get rid of that sticky now??
how will i get the additional driver or update for my htc tytn II? when will this be available?
kurashige said:
how will i get the additional driver or update for my htc tytn II? when will this be available?
Click to expand...
Click to collapse
There is no additional driver or update for the Tytn II, only a new version of Coreplayer which is compatible with the driver already in the Tytn II. This will be on sale in the new year.
Farsquidge said:
Can we get rid of that sticky now??
Click to expand...
Click to collapse
This guy is the definition of annoying...
dsyro said:
This guy is the definition of annoying...
Click to expand...
Click to collapse
Sorry, I did not say remove the thread, that would be wrong. I just asked if it could be made un-sticky!
Do you mean petition thread?
That petition is much more general. It touches problems with accelerated 3D graphics as well as video playback issues.
None of these are solved yet. I don't see any reason for un-sticky-ing that thread.
Bottom line: No, I don't think that petition will solve anything. But I still like people to know about Kaiser's problems.
omikr0n said:
Do you mean petition thread?
That petition is much more general. It touches problems with accelerated 3D graphics as well as video playback issues.
None of these are solved yet. I don't see any reason for un-sticky-ing that thread.
Bottom line: No, I don't think that petition will solve anything. But I still like people to know about Kaiser's problems.
Click to expand...
Click to collapse
Unlike others who, for reasons that escape us all, would rather hide them under the carpet
Ahhh... You people and your petitions.... very amusing.
Now come on, don't all jump on me now... It's cute that you have an interest and you feel that your 'doing something'
greeek said:
Ahhh... You people and your petitions.... very amusing.
Now come on, don't all jump on me now... It's cute that you have an interest and you feel that your 'doing something'
Click to expand...
Click to collapse
It would be a pity if the problem was solved and admins could put a block on certain people downloading from this site.....
Will this fix in any way help with the Camera/Video Camera jerky/blurry-video issue?
Either way it's nice to see some solutions are finally surfacing.
Menneisyys said:
See http://www.corecodec.com/forums/index.php?topic=596.0
Click to expand...
Click to collapse
Really, you call this good news? This is horrible news. And it isn't even correct either.
They haven't solved anything, they're just used a propriety technology driver to do something that by all means SHOULD WORK with the already existing and used-in-every-normal-program DirectDraw and GDI.
This gives HTC even LESS incentive to fix our problems, since there is now (a particularly bad) workaround.
So now we have to use a custom player we have to pay for to do something our device should have done already out-of-the-box, and it still doesn't solve our GDI, DD, D3D or GLES issues.
You call this good news, I call this a farce.
(And actually, the correct GDI/DD should be able to decide when to actually use QTV and do this internally, just like the KS20 D3Dm driver uses GLES internally)
Chainfire said:
Really, you call this good news? This is horrible news.
Click to expand...
Click to collapse
It is very good news for anyone wanting to watch videos with CorePlayer. Noone else, I know. But, at least, video playback becomes much easier.
Chainfire said:
This gives HTC even LESS incentive to fix our problems
Click to expand...
Click to collapse
Do you really think HTC would fix these issues? They haven't even fixed the two-year-old touchscreen CPU usage issue plaguing ALL 2.8" HTC phones... a major pain in the back with ALL these phones.
Menneisyys said:
It is very good news for anyone wanting to watch videos with CorePlayer. Noone else, I know. But, at least, video playback becomes much easier.
Do you really think HTC would fix these issues? They haven't even fixed the two-year-old touchscreen CPU usage issue plaguing ALL 2.8" HTC phones... a major pain in the back with ALL these phones.
Click to expand...
Click to collapse
Which is why my next device will not be a HTC device. I am seriously thinking of switching to the new US nokia with the upgraded ram and cpu.
Bratag said:
Which is why my next device will not be a HTC device. I am seriously thinking of switching to the new US nokia with the upgraded ram and cpu.
Click to expand...
Click to collapse
You mean the N95-3? That's a very nice model - highly recommended.
Farsquidge said:
Sorry, I did not say remove the thread, that would be wrong. I just asked if it could be made un-sticky!
Click to expand...
Click to collapse
If any sticky gets removed it should be the "The thread to address ALL TILT-specific questions". What a mess that turned into. It is completely useless. In addition to the length and disjointed topics, many of the questions aren't even Tilt specific. The first several posts should be moved to the wiki, glean what you can from the rest and let that abomination fade into a long overdue digital oblivian! ...nuf said
Back on topic, I think this is good news but the petitioned issue still stands. Core Player will help for encoded video only, and has not yet been released. Until I see it, I am sceptical. Plus it requires an additional purchase for something that should be free. Still, being able to transcode my video library once and be able to play on multiple devices with respectible quality will make it well worth the price.
So I will probably wind up using it if/when it does come out and if it does indeed work, but I still think the petition thread serves a good purpose, if only to make potential purchasers aware of the situation, and also what to expect form HTC support (which is basiaclly nothing).
This thread is here for information and discussion about the Linux kernel (and Linux based userspaces like Ångström distribution or google android.
If you have no clue what this is all about, click the above links and read a bit about it.
The xperia(kovsky) research information vital to porting the linux kernel is available at htc-linux.org
The kovsky is very similar to raphael, diamond and the other htc phones that are based on the QCT msm7xxxA chip. This is why the raphael/diamond development kernel code from the htc-linux project runs well on it.
Kovsky has its own machine type in the htc-msm-2.6.27 (see link above) branch now.
im kinda excited about this! if linux (& android) is able to run on the X1 smoothly, I'm definitely donating!
New thread = very good news.
If you need someone for testing then let me know.
I would be willing to donate as well.
Keep working hard everyone!
somehow i feel like setting up an X1 android version for it. since im more the "script" guy im rather useless for u if it comes to kernel development ^^
how stable and functional is the kernel so far?
and especialy, is the Wifi running allready?
hey decordes,
there is the question where to get the [email protected] files 0.8 and 1.0... (i have them. but dont know if i may provide these files while they are not from my self!)
a simple yes or no and they are available for the next years or not
--
cyberdesigner.net
achmed20 said:
how stable and functional is the kernel so far?
and especialy, is the Wifi running allready?
Click to expand...
Click to collapse
afaik the wifi doesnt work. only usb0 which is laggy. (but works! you could ssh to the x1 per default.)
i am a little bit bussy at the moment (have to provide some sap-python-mysql-interface for productive use.)
but if i get spare time i will take a closer look at wifi...
--
cyberdesigner.net
kk thx.
as long i can use ssh, i'm all set up i guess
time for some android theory
NSRocket said:
Ooops (forgot to strike key), yes I mean TNETW12511.
Click to expand...
Click to collapse
isnt that the same wifichip as the kaiser has?
but why is wifi needed to boot android?
Reversedhex said:
isnt that the same wifichip as the kaiser has?
but why is wifi needed to boot android?
Click to expand...
Click to collapse
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.
NSRocket said:
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.
Click to expand...
Click to collapse
i was reading a combination of things,
-wifi not working and usb0 laggy.
-log readout over usb0
so i thought maybe for the log or something, nevermind
---------------------------------------------------------
wifi not working on kaiser either so we cannot take the driver from there, but i dont think wifi has high priority...
http://www.androidonhtc.com/kaiser:port_status
NSRocket said:
I don't know many things on Kaiser device but if you read somewhere that it use a TI 1251 WLAN then... yes, it's the same.
I don't understand why do you correlate wifi and android booting
We're talking about this wifi chip just because it isn't supported in the linux-htc-kovsky package at the moment.
Click to expand...
Click to collapse
its not related. i jsut read that the USB connection was kind of laggy so once i set up a working wifi connection i can continue working with SSH over wifi. that was the only reason.
ah... ok i think this was my intention.
most of the time i am waiting for usb0 to get any response! i cant read on the display them self... so the next needed feature for _me_ was to get a stable/responsible connection (like wifi
achmed20: you got it!
--
cyberdesigner.net
Hi,
very nice project. Maybe i could help out a bit
At least i may help testing and do some hardware discoveries, because i'm not a good kernel hacker.
Anyway i'm used to digg the kernel source and all the other stuff.
There are some questions though:
Those are introduced in the git repository of Mariusz "Aiv" Dalewski. Among other changes, it has the fully working xperia keyboard.
Click to expand...
Click to collapse
Is the git already accessible?
Maybe someone could create a patch to get started more easily
afaik the wifi doesnt work. only usb0 which is laggy. (but works! you could ssh to the x1 per default.)
Click to expand...
Click to collapse
What's the exact state of USB connection right now?
Does it work on Raphael?
Concerning debugging:
Anything known about JTAG on Kovksy?
As you might know i'm addicted to this interface
Best regards,
scholbert
scholbert said:
Hi,
very nice project. Maybe i could help out a bit
At least i may help testing and do some hardware discoveries, because i'm not a good kernel hacker.
Anyway i'm used to digg the kernel source and all the other stuff.
There are some questions though:
Is the git already accessible?
Maybe someone could create a patch to get started more easily
What's the exact state of USB connection right now?
Does it work on Raphael?
Concerning debugging:
Anything known about JTAG on Kovksy?
As you might know i'm addicted to this interface
Best regards,
scholbert
Click to expand...
Click to collapse
http://www.htc-linux.org/wiki/index.php?title=Kernel#Kernel_for_QCT_MSM7xxxA_based_devices
The aiv code is htc-msm-2.6.27 branch plus xperia changes. I think he doesn't want to make it available publicly yet. I'm waiting for it too so I can push it to linuxtogo. You can pull the htc-msm-2.6.27 either way.
usbnet is same driver as used for raphael.
drivers/usb/msm_usb
For jtag, I think you need to wire it to the board manually.
For the raphael you can get a serial connection by making a cable that plugs in the usb port. Ask dreamkill about it. I don't know if it is wired the same way in xperia.
Hope this makes sense I have horrbile hangover
http://www.phonewreck.com/wiki/index.php?title=Sony_Ericsson_XPERIA_X1
So what has to be done is get the linux drivers for al these hardware components and compile them to a kernel to make it fully working?
that probably ist going to be easy
---------------------------------------------------------
btw about wifi cant the driver from g1 be extracted?
same hardware G1/X1
-Power Management PMIC: Qualcomm PM7540
-WLAN Texas Instruments WL1251B/WL1251FE
-UMTS: 2100MHz avago ACPM-7381
-USB SMSC USB3316
Hi dcordes,
thanks for your reply.
http://www.htc-linux.org/wiki/index.php?title=Kernel#Kernel_for_QCT_MSM7xxxA_based_devices
The aiv code is htc-msm-2.6.27 branch plus xperia changes. I think he doesn't want to make it available publicly yet. I'm waiting for it too so I can push it to linuxtogo. You can pull the htc-msm-2.6.27 either way.
Click to expand...
Click to collapse
Yeah did that already.
Unfortunately right now i got no X1 for testing. Should arive the next days i suppose
usbnet is same driver as used for raphael.
drivers/usb/msm_usb
Click to expand...
Click to collapse
O.K., i see so we will also use the config for raphael, i suppose..
For jtag, I think you need to wire it to the board manually.
Click to expand...
Click to collapse
Sure, that's essential
I just wanted to know if there's anyone apart from Sony and HTC engineers who got some info about these testpoints ?
For the raphael you can get a serial connection by making a cable that plugs in the usb port. Ask dreamkill about it. I don't know if it is wired the same way in xperia.
Click to expand...
Click to collapse
That's cool!
Hope this makes sense I have horrbile hangover
Click to expand...
Click to collapse
Does make sense to me
BTW anyone tried this patch to get WIFI support on X1?
http://linuxtogo.org/~lgorris/diffs/git-diff_htc-msm-2.6.27_add-ti1251.diff
Best regards,
scholbert
BTW anyone tried this patch to get WIFI support on X1?
http://linuxtogo.org/~lgorris/diffs/git-diff_htc-msm-2.6.27_add-ti1251.diff
Click to expand...
Click to collapse
Have to quote myself
The patch applies fine but after having a short glimpse, this one has been extracted from the SDK. No proper Kconfigs or Makefiles
So i don't think this huge patch is intended to go into kernel tree again.
AFAIK, there's also a lot of stuff for userland inside.
Insider may know more about it!
Perhaps for WIFI on the X1 it's better to start with a more clean driver.
You make have a look here:
http://osdir.com/ml/linux-wireless/2009-02/msg00390.html
I will try to integrate the patch to current 2.6.27-msm.
There's work to do of course, e.g. SDIO support and PM.
Best regards,
scholbert
I have no idea what you guys are saying.
But Android on the Xperia is f*****g awesome!
could any1 just quickly recap how close we are on a ROM with Android?
D4113R said:
I have no idea what you guys are saying.
But Android on the Xperia is f*****g awesome!
could any1 just quickly recap how close we are on a ROM with Android?
Click to expand...
Click to collapse
though i understand just a little, id like to qoute myself on this
So what has to be done is get the linux drivers for al these hardware components and compile them to a kernel to make it fully working?
that probably ist going to be easy
Click to expand...
Click to collapse
yes with htcraphael_defconfig xperia boots.
I will ask some people about 7xxxA jtag pins and let you know if I have any information.
scholbert said:
Have to quote myself
The patch applies fine but after having a short glimpse, this one has been extracted from the SDK. No proper Kconfigs or Makefiles
So i don't think this huge patch is intended to go into kernel tree again.
AFAIK, there's also a lot of stuff for userland inside.
Insider may know more about it!
Click to expand...
Click to collapse
Right, It copies some revision (see date of file upload) of the android git ti1251. It should enable you to build the kernel module.
lgorris=dcordes
scholbert said:
Perhaps for WIFI on the X1 it's better to start with a more clean driver.
You make have a look here:
http://osdir.com/ml/linux-wireless/2009-02/msg00390.html
Click to expand...
Click to collapse
It's no big secret the 10M google ti1251 driver is crap and it might really be better to use that wl12xx as soon as they have the SDIO.
scholbert said:
I will try to integrate the patch to current 2.6.27-msm.
There's work to do of course, e.g. SDIO support and PM.
Click to expand...
Click to collapse
That will be nice. Let me know when you tried.
hi
I'm very surprised because tuxhero said yesterday that the blackstone has compass harware:
http://forum.xda-developers.com/showpost.php?p=4304713&postcount=833
bad link... you cant link it with dots: )
Not sure but some sources say that we have it.
daguerrotipo said:
hi
I'm very surprised because tuxhero said yesterday that the blackstone has compass harware:
http://forum.xda-developers.com/show...&postcount=833
Click to expand...
Click to collapse
Your link does not work
Fallen Spartan said:
Your link does not work
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4304713&postcount=833
tuxhero said:
Not sure but some sources say that we have it.
Click to expand...
Click to collapse
"1. Today i came to know that our Blackstone has Compass Hardware too and we have code for it too."
Seems to me that you were sure?
Moony1987 said:
"1. Today i came to know that our Blackstone has Compass Hardware too and we have code for it too."
Seems to me that you were sure?
Click to expand...
Click to collapse
Ya but not tested it to be so sure
tuxhero said:
Ya but not tested it to be so sure
Click to expand...
Click to collapse
Ahh righto
I think we do have.
Thats the shame 'bout HTC (besides da poor quality of hard- and software): they setup ONE hardware and make 5 PDAs with slighty changed details. they were never interested in making good hardware.. everytime they took something away the previous model had... now, they do have android and are able to clone nearly the same device just with another OS.
in commercial aspects, this makes sense.... but as consumer I can only think of it as a pain in the neck. my old universal has a high res display, a 3,5mm audioconnector, a well made keyboard and a fast cpu... years ago... a shame it is the size of a brick .
If someone would mad it possible to use the Compass HW with WinMo i would gladly set a bounty of 50$.
Goal would be a little App to proof that it ist working plus the sourcecode for other Devs.
Does anyone join in?
its probably another 'tv out' scenario...
basically the chipset has the tech but other required hardware / software is not present hence the features can never be used.
why on earth HTC cripple devices like this is boggling.....if the HD had been released with TV-out (which the qualcomm chipset supports) & a hw compass (to be confimed) it would have levelled the competition.....
i am sure their marketing strategy has good reasons for not doing...but as said earlier from the consumers point of view its a pain in the butt...especially considering some of us are locked in 24 month contracts.!! so wont be purchasing other handsets even if we wanted too.
lets hope some clever devs find a way to unlock these features!! (if possible)
purec0de said:
its probably another 'tv out' scenario...
basically the chipset has the tech but other required hardware / software is not present hence the features can never be used.
why on earth HTC cripple devices like this is boggling.....if the HD had been released with TV-out (which the qualcomm chipset supports) & a hw compass (to be confimed) it would have levelled the competition.....
i am sure their marketing strategy has good reasons for not doing...but as said earlier from the consumers point of view its a pain in the butt...especially considering some of us are locked in 24 month contracts.!! so wont be purchasing other handsets even if we wanted too.
lets hope some clever devs find a way to unlock these features!! (if possible)
Click to expand...
Click to collapse
I disagree your argumentation:
Developers here wrote drivers to implement TMC and RDS into the features of the Blackstone. HTC hasn´t done it yet.
HTC seems to leave possible feature unused. Maybe to save time for their developers.
The old topic of a missing video driver is another example for that.
Draque:the_Plaque said:
If someone would mad it possible to use the Compass HW with WinMo i would gladly set a bounty of 50$.
Goal would be a little App to proof that it ist working plus the sourcecode for other Devs.
Does anyone join in?
Click to expand...
Click to collapse
50$ from me for unlocking the feature + another 100$ if anyone makes it work with Google Maps + another 100$ if someone makes an augmented reality app like Wikitude (Android).
Only if it's done before the release of the HTC Leo
It's a AK8976A chip
well i would chip in $50 as well .. if it worked !!
KlausFindus said:
It's a AK8976A chip
Click to expand...
Click to collapse
is the same that dream phone?
Byes
haha, did anyone think that they mite have released the phone in haste, or maybe they did it on purpose to allow the release of the HD pro to include such features, along with a 128GB internal memory (i wish).
ghosty_uk said:
haha, did anyone think that they mite have released the phone in haste, or maybe they did it on purpose to allow the release of the HD pro to include such features, along with a 128GB internal memory (i wish).
Click to expand...
Click to collapse
Sometimes happen... It's true that more with anothers brands (apple), I can remember Ipod touch, iphone, wifi in the macs....
may be this time no but is possible.
Byes
I've read the same thread from Tuxhero and I have to see it before I believe it. The only thing we've got is a blanket statement that he has read it somewhere. Someone else created slight confusion on this site before with similar statements.
Not saying that he's lying (in fact, I hope he's right), a source would help. Until then, I'm not getting my hopes up.
Im guessin they didnt include alot of features cause when the phone was released whoever ws going to buy it would buy it anyway, and when competitors (Iphone3gs) release phones with features like the compass thing etc , htc can easily release newer phones with the same features ... sort of like having it ready on earlier models so when they need to release it they can quickly!
My guess
Hi, guys,
SNAPSHOT:
see Kalim's ROM release thread. Enjoy!
PS, sources have been synced with my github repo. check out this commit.
I met a problem to understand the assemble codes of a KEY function(ie reg_unreg_buf() in libcamera.so in Tattoo Donut system). I just know a little about arm assembly language. How does the assembly deal with structures and pointers to structer in C? If we can implement this function into libcamera.so in Froyo, I think it's not too far from working camera preview. So here are some details.
Current question is, why msm_poll in the kernel won't be called while I did system-call select()? I tried lots of times, but always no luck.
Forget them all, thanks to boz_x.
I will try to take a look into it this evening
KalimochoAz said:
I will try to take a look into it this evening
Click to expand...
Click to collapse
OK, thanks in advance. What confused me is what layout should be token in stack by arm assembly for structure data in C/C++. Are they exactly same as structures in memory or would arm-eabi-gcc apply some padding as well?
cn.fyodor said:
Hi, guys,
I met a problem to understand the assemble codes of a KEY function(ie reg_unreg_buf() in libcamera.so in Tattoo Donut system). I just know a little about arm assembly language. How does the assembly deal with structures and pointers to structer in C? If we can implement this function into libcamera.so in Froyo, I think it's not too far from working camera preview. So here are some details.
Current question is, why msm_poll in the kernel won't be called while I did system-call select()? I tried lots of times, but always no luck.
Forget them all, thanks to boz_x.
Click to expand...
Click to collapse
?¿? What do you mean. Something to share with us?
KalimochoAz said:
?¿? What do you mean. Something to share with us?
Click to expand...
Click to collapse
No, not currently. I just solve some little problems that I met. Addresses of frame I got were always wrong. Codes are messed up right now. Time to rest. Good night.
cn.fyodor said:
No, not currently. I just solve some little problems that I met. Addresses of frame I got were always wrong. Codes are messed up right now. Time to rest. Good night.
Click to expand...
Click to collapse
git your code to reach this. I will continue there if you want. here is 5 pm
cn.fyodor said:
Hi, guys,
Here is the color spectrum :
Click to expand...
Click to collapse
Does that image ever change. or is it static?
I'm wondering if perhaps it's data from the camera, just not in the format the app is expecting...
cn.fyodor said:
hi, guys,
i met a problem to understand the assemble codes of a key function(ie reg_unreg_buf() in libcamera.so in tattoo donut system). I just know a little about arm assembly language. How does the assembly deal with structures and pointers to structer in c? If we can implement this function into libcamera.so in froyo, i think it's not too far from working camera preview. So here are some details.
current question is, why msm_poll in the kernel won't be called while i did system-call select()? I tried lots of times, but always no luck.
forget them all, thanks to boz_x.
This is my wireless headset(8 frames overlapped ):
ps, sources have been synced with my github repo. Check out this commit.
Click to expand...
Click to collapse
i love you fn.fyodor
KalimochoAz said:
i love you fn.fyodor
Click to expand...
Click to collapse
We all <3 u fyodor!
Looks like messed yuv422, where green is Y and UV are black and light gray
Probably proportions are right but surface configured wrong
CAMERA WORKS ( No problem now )
Fyodor & Arco. I have already solved.
I would like to release the 3 versions at the same time. Fyodor PM me and we manage to release it all the ROMs with fully camera!!!!!!!!!!!!!!!!!!!!
YUPIEEEE!!!!
kalimochoaz said:
fyodor & arco. I have already solved.
I would like to release the 3 versions at the same time. Fyodor pm me and we manage to release it all the roms with fully camera!!!!!!!!!!!!!!!!!!!!
Yupieeee!!!!
Click to expand...
Click to collapse
devs are the best. Thank you!!!
I missed Fyodor a lot. We needed to be 3 coding to solve that puzzle
KalimochoAz said:
Fyodor & Arco. I have already solved.
I would like to release the 3 versions at the same time. Fyodor PM me and we manage to release it all the ROMs with fully camera!!!!!!!!!!!!!!!!!!!!
YUPIEEEE!!!!
Click to expand...
Click to collapse
See, this is why the HTC Tattoo communtity is so awesome!!
Keep up the good work!!
-- Kiljacken
well camera is now working. great! what about the video camcorder? is it gonna work too?
KalimochoAz said:
Fyodor & Arco. I have already solved.
I would like to release the 3 versions at the same time. Fyodor PM me and we manage to release it all the ROMs with fully camera!!!!!!!!!!!!!!!!!!!!
YUPIEEEE!!!!
Click to expand...
Click to collapse
How did you solve the y_cbcr offset issues? Actually I really don't know what they are, I just read the assembled codes step by step and fill my implementing function codes. LOL
And I don't mind the time when devs release their ROMs, so just go on your way, I will release my AOSP ROMs at a proper period.
Cheers && Enjoy!
when cn.fyodor just return to this forum FM radio works and now Camera preview.
Now I see the reason for buying this tattoo.
Big thanks to Kalim...and all others
Thank you guys. Thanks kalim, arco, fyodor
Excellent work.
My opinion
Let me say one think: Its really amazing and good to spend time with fn.Fyodor and Arco68 in this forum. When I change my device I will miss this way of working.
KalimochoAz said:
Let me say one think: Its really amazing and good to spend time with fn.Fyodor and Arco68 in this forum. When I change my device I will miss this way of working.
Click to expand...
Click to collapse
Thanks a lot Guys!
What device are you going to?? ( I want to go to the same!!)
I am looking at the Optimus 2x, it is a lot less expensive then the Galaxy S II!
so i dropped my heroc the other day when getting it off the shelf so that i could create/port something for this phone, sense i was getting bored with my evo, and after i dropped it i picked it up and checked to make sure everything works but only thing that doesn't is installing apps
any suggestions for fixes besides replacing are welcome
also i'd like to know somethings people would like to see done on the hero:
any mod ports to the phone you'd like?
any rom ports you all would like to see?
would you like a new rom?
a new theme?
any app ideas?
anything? lol
just trying to help
you shure your not kifno bsing us again this sounds like something he would post lmao.
Bierce22 said:
you shure your not kifno bsing us again this sounds like something he would post lmao.
Click to expand...
Click to collapse
Account currently disabled
CH3NO2 said:
also i'd like to know somethings people would like to see done on the hero:
any mod ports to the phone you'd like?
any rom ports you all would like to see?
would you like a new rom?
a new theme?
any app ideas?
anything? lol
just trying to help
Click to expand...
Click to collapse
If you really wanted to do something useful, you would get into improving our current driver situation. We have an open-source camera driver (which wraps the OEM camera driver) in the CyanogenMod tree, but it needs work, especially on the camcorder side (camcorder doesn't focus at present).
There's also still a lot of work needed on the GL side. We have the libgles_qcom.so file from previous ROM images, but it isn't 100% compatible with Gingerbread (missing textures in Quadrant, etc).
The YouTube player sometimes plays audio-only when viewing "HQ" videos. I suspect this is due to a missing video codec and/or related to the above GL issues. We need work done on various codecs.
There's plenty of work to be done in kernel space. The 2.6.35 kernel posted by s0be is significant progress, but there is still plenty of room for improvement. Personally I would like to see more optimizations done on the kernel side because these will benefit all ROM images.
There are also various bugs in CyanogenMod that shouldn't be too difficult to fix, such as notification power widgets disappearing when changing themes. Check their issue tracker on Google Code to find some easy things to fix.
It would be awesome to see a fully-working 2.3.4 ROM image that was 100% AOSP and had completely working drivers. It would certainly make future development much easier and provide a nice base to build other ROM images from.
...oh, wait, that's right. You just want to "port" "tweaks"/themes/nonsense. Try fixing what we have right now before you give us more half-working junk.
Bierce22 said:
you shure your not kifno bsing us again this sounds like something he would post lmao.
Click to expand...
Click to collapse
honestly the questions he had reek of kifno, check join date also, hmmmm....
if he is kifno, at least he stopped with all the stupid smilies at the end of every sentence
xfrobex said:
honestly the questions he had reek of kifno, check join date also, hmmmm....
if he is kifno, at least he stopped with all the stupid smilies at the end of every sentence
Click to expand...
Click to collapse
I'm sure it was, as the account was disabled hours after making the post.
this dude needs to discover some vagina to take his mind off his hero. Anyone that ran his tweaks has to be insane.
lmfao how did I miss this thread before xD
You think he'd get the hint after he's been banned X # of times along with getting flamed every time he comes back...smh
On a positive note, I hereby name Bierce22:
.:]Official kifno alter ego finder[:.