Hi all.
The issue has been SOLVED as of today (9 Nov), thanks to marc1706. He successfully identified a line in the kernel video drivers, which has completely eliminated the color banding from what I can see. There is no need for any other fix to be applied.
The thread for his kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1282435. Be sure to thank him for his wonderful work!
For kernel devs interested in applying to fix to current kernels, his commit can be viewed here: https://github.com/marc1706/cm-on-wince-htc/commit/dfe41d02cac454e3e58c583cd4fa0c0825160d1f.
Thanks for all the support guys, glad it's finally solved.
MrP.
It's a great thread, but the kernel developers are already aware of this I'm sure
Thanks for the compliment.
I'm sure they're aware of it, but possibly not aware of its solution. Hopefully this can serve as a general thread to discuss its solution for all devs to benefit from.
MrP.
Sent from my HTC HD2 using XDA App
Developing on the hd2 will never stop
Eagerly waiting for a solution, I hope someone find a solution for this!
This is the last big issue left to solve...
One other thing - if anyone has any ideas of what the video incompatibility might be related to, please let me know and I'll play around with possible fixes.
MrP.
sbryan12144 said:
Ok. I'll tell before I release.
The old kernel was based off of the EVO 4G's 2.6.32 source right? -Yes
The new kernel is based off of the Desire's 2.6.35 source right? -Yes
Doesn't that mean we'd need actual Desire libs rather than others? -Yes!
I tested marc's 1e kernel with my OLD Bravo build that I made from the Desire's Official RUU (3.14) and CAM WORKS. So my theory is correct. I tested it on my RCMix3D Runny Build and it works as well.
Hope you guys are happy
Don't forget to credit the kernel builders and me for this fix!
Click to expand...
Click to collapse
Maybe this will help?
Sent from my HTC HD2 using XDA App from my HTC HD2 using XDA App
Thanks for the heads up.
I am aware of that post and I'm actually busy looking into it. The only problem with simply bringing the Desire libs over is that those libs are designed for Sense builds, so as sybryan12144 has mentioned, it will work for bringing those libs over to our Sense ports. The real problem is getting them working under AOSP builds. Shall take a further look never the less.
MrP.
The easiest way I found to reduce colour banding is to set the DPI to 217, although that means losing a lot of apps in the market with my rom.
I don't think we can ever fully eliminate due to our 65k displays...
Sent from my HD2 using xda premium
Contrary to popular belief, the color banding in Android is not necessarily due to a limitation of our 65k screens. Although the pictures in the OP are representing the fix for the notification pane only, there were no color banding issues that I could find anywhere in the ROM. It truly removed the issue completely.
If you'd like to test, you don't even have to reinstall your current ROM - just grab marc's 2.6.35 kernel, and warrenb123's 2.6.35 kernel. You should be able to install them over your current build, but you'll notice that warrenb123's kernel eliminates the color banding, probably due to the fact that it uses the Desire GPU driver. Marc's kernel, despite being a 2.6.35 kernel, does not solve this (yet).
MrP.
Try changing this in your build.prop...
debug.fb.rgb565=1
Works wonders for sense builds!
Sent from my HTC Desire HD A9191 using XDA App
tobiascrystal said:
Try changing this in your build.prop...
debug.fb.rgb565=1
Works wonders for sense builds!
Sent from my HTC Desire HD A9191 using XDA App
Click to expand...
Click to collapse
That only works if you already have the Desire kernel installed though...
I am using heiros kernel and it is working fine for me!
Sent from my HTC Desire HD A9191 using XDA App
MrPadie said:
Contrary to popular belief, the color banding in Android is not necessarily due to a limitation of our 65k screens. Although the pictures in the OP are representing the fix for the notification pane only, there were no color banding issues that I could find anywhere in the ROM. .
Click to expand...
Click to collapse
things like notification panes etc which have simple gradients can be nearly eliminated. But look at more complex ones eg photos of clouds. 65k is 65k and 'you cannae break the laws of physics.. .'
Sent from my HD2 using xda premium
http://forum.xda-developers.com/showthread.php?t=1268085
@consolation - no doubt, I agree with you. However maybe I should more clearly state that I am referring to the quality of ROM elements. 65k is 65k, and some gradients will be visible obviously, but the quality of ROM elements without the fix is somewhat disappointing.
MrP.
Sent from my HTC HD2 using XDA App
@famewolf - that doesn't truly solve the issue, nor does it work well with regards to ROM elements. Already tried it on typhoon, banding issue doesn't change in the notification pane at all.
MrP.
Sent from my HTC HD2 using XDA App
I belive that, as most android comming after 2.2 came with 250k+ colors, the gradient algo was not updated. Try this, on CM roms, add the music and the analog clock to your screen. Notice the heavy banding. Now, try to move them. Notice that a different algorithm is used whyle moving.
That algorith is probably used all the time on the gallery, solvind the banding issues.
That yellowish/blueish gradients on the background should suffer from the banding also.
Well put daedric. I am therefore assuming that this 'algorithm' then has been updated/fixed/implemented properly in the Desire GPU driver.
To everyone - I think what we need to understand here is that the issue exists, and it's main cause is directly related to the GPU driver. Yes, there are one or two things that possibly ease the issue (saturation fix and rgb565 flag in build.prop), but the proper, native fix lies somewhere in the Desire GPU driver. Now, seeing as I am not a kernel dev, I cannot pinpoint the cause/solution.
So, the main point that this thread should express is that the issue can be fixed, by applying the Desire 2.6.35 port. However what we are trying to achieve is using this port without breaking video/camera/camcorder compatibility.
MrP.
MrPadie said:
Well put daedric. I am therefore assuming that this 'algorithm' then has been updated/fixed/implemented properly in the Desire GPU driver.
To everyone - I think what we need to understand here is that the issue exists, and it's main cause is directly related to the GPU driver. Yes, there are one or two things that possibly ease the issue (saturation fix and rgb565 flag in build.prop), but the proper, native fix lies somewhere in the Desire GPU driver. Now, seeing as I am not a kernel dev, I cannot pinpoint the cause/solution.
So, the main point that this thread should express is that the issue can be fixed, by applying the Desire 2.6.35 port. However what we are trying to achieve is using this port without breaking video/camera/camcorder compatibility.
MrP.
Click to expand...
Click to collapse
Might just be a simple setting. Let us remember that there are no HTC drivers for the HD2 in particular. We got everything from the Desire and probably the Nexus.
Now, those two devices are 24bit color from ground 0, and the driver problably belives that we have a 24bit capable screen. Warren's driver must have something in it, that makes it behave nicely with RGB565 instead of RGB888.
I have a questions. The Desire came out in two versions, Amoled and LCD. How does the android finds out which type of screen is being used? Or is it transparent to the OS?
Related
It's a good time to be a desire owner these days.
The roms just keeps popping out day after another.
Question is, which one is the fastest, most stable, best one?
I think a poll is in place.
Please only vote if you've actually tried them all.
ROM Links:
InsertCoin: http://forum.xda-developers.com/showthread.php?t=1016940
RCMix S: http://forum.xda-developers.com/showthread.php?t=988570
Ace/Vision S: http://forum.xda-developers.com/showthread.php?t=1018843
Also, if you found one not listed here, please elaborate.
And I think replying to this thread with your personal reviews of your favorite one with pro's and con's against the others would be appreciated too.
Happy flashing!
Tried 2 of them robo and Baadnewz v similar but TBH no video camera,no trackball wake then none of them is the ****
InsertCoin v1 was running very sweet for me but for some reason updated versions caused problems,probably my fault couldn't be bothered with a full wipe currently using RCMix Sv08 very happy with that apart from the 2 points mentioned above and the lack of a menu function to swap from 2G to 3G easily signal,GPS,battery life all great compass i think borked but i never use it
I selected the rcmix S, because for now it's the only one I tested, and what I can say is that it is really fast for normal use. Compared to version rcmixHD
For other ROMs, they seem to be all good as each other. The developers follow the well updated and are listening to users. The user feedback at speed and bug are equivalent for all roms.
You guys did a great job! Thank you for all your work for our small desires.
ziggy1001 said:
Tried 2 of them robo and Baadnewz v similar but TBH no video camera,no trackball wake then none of them is the ****
InsertCoin v1 was running very sweet for me but for some reason updated versions caused problems,probably my fault couldn't be bothered with a full wipe currently using RCMix Sv08 very happy with that apart from the 2 points mentioned above and the lack of a menu function to swap from 2G to 3G easily signal,GPS,battery life all great compass i think borked but i never use it
Click to expand...
Click to collapse
Camera is fixed in both, lag is fixed in insertcoint.
There are solutions for both roms to get the extra settings working in quick menu. (use search in thread)
There are solutions for both roms to get trackballwake(guides, search in threads).
-video rec. still down
-compas still down
anyhow, my 2 cents.. their both great! I picked insertcoin, not alot of difference between the 2 roms.. but in time that will change imo..
but for now, both very viable! havent tried ace & vision roms yet
In general I agree on:
skippy68220 said:
You guys did a great job! Thank you for all your work for our small desires.
Click to expand...
Click to collapse
Srkineo said:
There are solutions for both roms to get trackballwake(guides, search in threads).
Click to expand...
Click to collapse
Interesting i have home& menu wake working but not reliably, but didn't see any options for trackball, looks like i'll have to spend even more time searching XDA
Srkineo said:
Camera is fixed in both, lag is fixed in insertcoint.
There are solutions for both roms to get the extra settings working in quick menu. (use search in thread)
There are solutions for both roms to get trackballwake(guides, search in threads).
-video rec. still down
-compas still down
anyhow, my 2 cents.. their both great! I picked insertcoin, not alot of difference between the 2 roms.. but in time that will change imo..
but for now, both very viable! havent tried ace & vision roms yet
In general I agree on:
Click to expand...
Click to collapse
Yes, as you noticed there are almost no differences in our roms, what i can see when i diff the roms is that only thing changed is the ril and some apps removed from insertcoin... so i dont know what is causing lag in my rom :/ strange... should be the same... It can be the plurk which he removed and i still have in my rom (possible memory leak in that app), i will check that when i come back from my vacation, now i am working on A2SD version of v08.
have a nice day everyone
robocik said:
Yes, as you noticed there are almost no differences in our roms, what i can see when i diff the roms is that only thing changed is the ril and some apps removed from insertcoin... so i dont know what is causing lag in my rom :/ strange... should be the same... It can be the plurk which he removed and i still have in my rom (possible memory leak in that app), i will check that when i come back from my vacation, now i am working on A2SD version of v08.
have a nice day everyone
Click to expand...
Click to collapse
well i don't know where the lag appears, i changed the rils, modded init.rc, changed all wpa related files with the ones from gb leak in an effort to fix some wifi problems, i removed some files, fonts, and moved lib_s to /system/lib.
Problem with my roms later than v01 is flash player 10.2, problem that is also on my froyo roms. and i have no clue how to fix it, thou in robo's roms the problem doesnt exists, plurk i removed from v04 so users should tell if that did the trick or not.
And as mentioned before, robocik did the hard - porting - hacking part. without this we wouldn't have a sense 2.1 rom.
btw, anyone have a clue why compass is acting strange? not that i ever use it, but some users need it
Hmmm its too difficult to compare 3 roms...coz me n baadnewz using same base even features is 100% same...only difference between tweaking n optimization...
But my vote for RCmixS coz robo is the first person who port sense 2.1 Rom...
Sent From Nokia 3310...!!!
If you look at the SuperDuperAwesomeROM v0.3 by eddyOS isn't that 2.33 Gb with an earlier version of Sense but made for the Desire, not a port and people say compass doesn't work, so maybe HTC cockup?
baadnewz said:
well i don't know where the lag appears, i changed the rils, modded init.rc, changed all wpa related files with the ones from gb leak in an effort to fix some wifi problems, i removed some files, fonts, and moved lib_s to /system/lib.
Problem with my roms later than v01 is flash player 10.2, problem that is also on my froyo roms. and i have no clue how to fix it, thou in robo's roms the problem doesnt exists, plurk i removed from v04 so users should tell if that did the trick or not.
And as mentioned before, robocik did the hard - porting - hacking part. without this we wouldn't have a sense 2.1 rom.
btw, anyone have a clue why compass is acting strange? not that i ever use it, but some users need it
Click to expand...
Click to collapse
try to take my flash player and libs... uploading my A2SD rom, i have changed some flash stuff, we'll see if it helps for the users... have not tried it myself yet.
my users are reporting some calling issues, is that caused by the ril? i am using the one from the leaked rom... i think anyway hehe dont remember anymore.
need to run now. A2SD+ is on the way up.
ziggy1001 said:
If you look at the SuperDuperAwesomeROM v0.3 by eddyOS isn't that 2.33 Gb with an earlier version of Sense but made for the Desire, not a port and people say compass doesn't work, so maybe HTC cockup?
Click to expand...
Click to collapse
if the compass problem is in the bravo leak then yes is a problem from HTC. But again the leak is a TEST Build so problems are expected.
robocik said:
try to take my flash player and libs... uploading my A2SD rom, i have changed some flash stuff, we'll see if it helps for the users... have not tried it myself yet.
my users are reporting some calling issues, is that caused by the ril? i am using the one from the leaked rom... i think anyway hehe dont remember anymore.
need to run now. A2SD+ is on the way up.
Click to expand...
Click to collapse
i took them in v04 /lib/plugins but still nogo, will keep investigating but same as you I'm on vacation with my family. After Easter I'll have more time
I think its leedroid 2.3.3
Sent from my HTC Desire using XDA Premium App
gurpreet3579 said:
I think its leedroid 2.3.3
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
read the thread question before posting ****! btw currently running insertcoin S v04, no problems at all, removed plurk and stocks, also thinking about removing peep but I don't know how will this affect the UI(friendswidget for example). Peep is also using a lot of memory.
ciprigeorgiu said:
read the thread question before posting ****! btw currently running insertcoin S v04, no problems at all, removed plurk and stocks, also thinking about removing peep but I don't know how will this affect the UI(friendswidget for example). Peep is also using a lot of memory.
Click to expand...
Click to collapse
if u remove peep, friend stream will stll work but it will show only facebook updates
would like to vote for
RC-MIX
&
InsertCoin as both of them feel very good in allday work situation
gave my vote to I-Coin cause i used it longer but now im on RCmix V8 and think i will stay there (top)
thx to Robo for making new STUFF available for our/my Desire
i couldnt find any way to get trackballwake on gb sense roms,i searched a lot.
Would someone plz be so nice to show where to get a flashable zip for it.
Why don't you three musketeers join forces to focus on just one bad ass rom?
I experienced slowdowns when I flashed the vorkmod of rcmix s 0.7, no slowdowns anymore after going back to the original rcmix s. I suspect it's some of these extra modules added (undervolt or a different governor)
btw my compass works quite well
Is anyone having problems with autobrightness (ie brightness suddenly going up and down again?)
oh my vote goes to robocik for now
On insertcoin, the WiFi randomly disconnects when the signal is low. Does this happen on other ROMs?
325i. said:
On insertcoin, the WiFi randomly disconnects when the signal is low. Does this happen on other ROMs?
Click to expand...
Click to collapse
the wi-fi problem on insertcoin seems to be fixed now. check you wi-fi sleep policy. but i seem to have a little problem. from the day i got my desire i used switchpro widget. i use it now also but now i can't make the flashlight work(the flash doesn't turn on). does anyone know a fix for this problem?
Hey guys is it possible to resize or convert desire roms to buzz roms?
Practically, No. Else we would have had a lot more ROMs, especially Sense 2.1 / 3.0 ones, apart from SFM.
3xeno said:
Practically, No. Else we would have had a lot more ROMs, especially Sense 2.1 / 3.0 ones, apart from SFM.
Click to expand...
Click to collapse
Ann Alright ... but cant we just Resize the graphics and use any other Rom 's Scripts?
They are optimized for that device's hardware, and I am sure you know that there's a difference as big as day and night when you compare the hardware of Desire and Wildfire. If you saw the recent AOSP ROMs being developed by xdbg and Devnull, even a simple task of swiping from one homescreen to another uses the GPU by default (Which is absent, causing lag), which has to be overcome by using special functions. But this doesn't work everywhere.
Besides, resizing is an extremely tough job, and involves editing of tons of image files and XML files. You can see that in SFM, where inspite of evilsto resizing many apps and worked a lot on it, the overall appearance of the ROM is not suited for the Wildfire.
3xeno said:
They are optimized for that device's hardware, and I am sure you know that there's a difference as big as day and night when you compare the hardware of Desire and Wildfire. If you saw the recent AOSP ROMs being developed by xdbg and Devnull, even a simple task of swiping from one homescreen to another uses the GPU by default (Which is absent, causing lag), which has to be overcome by using special functions. But this doesn't work everywhere.
Besides, resizing is an extremely tough job, and involves editing of tons of image files and XML files. You can see that in SFM, where inspite of evilsto resizing many apps and worked a lot on it, the overall appearance of the ROM is not suited for the Wildfire.
Click to expand...
Click to collapse
Yeah ofcourse i know difference between hardware stuff also .. nyways ... hoping to develop some exe to do resizing stuff -- Finger crossed
This is the HoneySense ROM ported from the desireHD to the desireZ! i like it, its fast, and looks elegant. What cuts it apart from the others, is the speed of a sense 2.1 rom, the versatility of sense 3, and the slickness of honeycomb. This uses virtuous OC daemon, so if you install setCPU or any other overclock app, it will disable.
How to install
(OPTIONAL) NANDROID BACKUP
(optional, RECOMMENDED! Some of the updates wont work if you dont) 1.Wipe EVERYTHING
2.install the ROM ZIP in clockworkmod
ROM Download 1.1 : ( http://www.megaupload.com/?d=IXM84O1M )
2.0 : http://www.megaupload.com/?d=PA4NVZQ0
Click to expand...
Click to collapse
Android 2.3.3 (Gingerbread) - OFFICIAL HTC RUU 2.50.405.2 (RELEASED 3.7.11)
Honeycomb themed
Brain **** CPU Scheduler as default (CFS optional)
VR I/O Scheduler as default (Deadline, Noop, SIO, BFQ V2.1 & CFQ Optional)
OpenVPN - CIFS - UTF8 - - EXT3 - EXT4 - JDB2
Audio boosts - 10% all outputs, 15% External speaker
WiFi Driver improvements & greater range
Rooted and Superuser added
Unsecured boot.img
Various tweaks for speed improvements
Battery calibration script (Thanks to the dev seo)
Multilingual ROM as all WWE are
Zipaligned @ system/app and data/app on boot
Fully de-odexed
init.d scripts (BusyBox run-parts) support
NANO text editor & sysro/sysrw commands support
EXT 4 VERSION
EXT 3 VERSION - for you non adventurous types (Coming soon)
Improved battery life, imagine a newer car vs the older car.. (Older car being STOCK ROM)
Includes support for customization and flash 2.50 mods ONLY over this release
Arabic and hebrew support find them in the addons section!
Click to expand...
Click to collapse
IF YOUR WIFI DOES NOT WORK, FLASH THE UNITY V4 KERNEL ONTOP OF THIS. Here is the LINK !
Anything with a V infront of it (V1, V2, V2873924 etc) is an RC, so V1 is RC1. Anything without a V is not an RC.
THE DESIRE Z HBOOT IS REQUIRED!
Read the tutorial at http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html to migrate to it.
Alternative Way to install Desire Z HBOOT
1. Download the PC10IMG.zip from the link above
2. Place it on the root of your SD
3. Boot into Bootloader
4. Choose the appropriate options
5. Remove the PC10IMG from the root, or else you cant boot into clockwork mod.
BTW, THIS ALSO CHANGES THE RADIO, SO YOU WILL HAVE TO FLASH A DIFFERENT RADIO
Thanks to
Adamholden85 For help with swype and the theme
Killersloth for the swype release and his Undervolt script, cheers pal
Seo for sense 3.0 for 2.1 and for help
Leedroid for the kernel + inspire 4g patch
Mike1986 for EXT4 Help and O/C Daemon help
Krzysiec for help and links
Cappy & Co for bringing half of this to us
Leith51 for inspiration and the help
Major thanks to he_stheone64 for all the help and the theme.
andyharney for the ftp and helping me with CM7 theme
Click to expand...
Click to collapse
Also, a special thanks to bsbokc, as without him, i would not know how to do this!
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE OR ANYTHING LIKE THAT
The Function XYZ is missing from this ROM.
Well, this is a PORT of a DHD rom, so they have the same features. it will only be added if its in the real HoneySense from DHD, or if its an optimisation, or something small, i may add it though.
Click to expand...
Click to collapse
CHANGELOG:
1.1: 29/7/11
removed gmail (install from market!!!)
fixed settings (showing as desire hd, showing incorrect ram, wrong MPX etc)
removed magicsmoke wallpapers
added keyboard without arrows
Friendstream widget added back in
1.0: 28/7/11
NO LONGER RC!
deleted stocks
updated adobe reader
FIXED WIFI!!!
now uses RMK's kernel (can install unity over it)
added DSP Manager
Removed: fmradio widget, friendstream widget, Twitter 3d widget
deleted facebook.apk (install facebook from market!)
deleted flickr.apk (install flickr from market!)
RC2: Speed improvements, included gingerbread ghostly so sms dont get lost (just incase), trackpad wake enabled - 27/7/11
if you are experiencing frequent freezes, it may be because your CPU is overclocked too high. flash http://www.megaupload.com/?d=A5ASHRM4 to stop it.
wifi calling patch: (I HAVE NOT TESTED IT, AS I AM AN O2 UK CUSTOMER SO IDK IF IT WORKS)
http://www.megaupload.com/?d=PIZNZ6O9
if apps are being killed frequently, it is due to gingerbread's aggressive RAM system. to make it better, use this guide http://forum.xda-developers.com/showthread.php?t=1126940
if MMS messages are too small, apply this fix (thanks to RMK!!!) http://www.megaupload.com/?d=YICSXR5W
what 3.0 sense features are included?
It looks fantastic!!
kowal_001 said:
what 3.0 sense features are included?
It looks fantastic!!
Click to expand...
Click to collapse
It's a complete sense 3 rom, but its not slow. it may be slow first, but give it time to settle in, and it will speed up plus in the next version i will make corrections to make it faster, and create a patch to remove the CRT animations, as they cause an orange led bug to occur.
Very nice and congrats can't wait to try it.
Just when I thought I found a rom I wont have to leave for a while..sigh..dammit..well, fueling my flashaholicness even further
Sent from my Synergy Rom using XDA App
Galery 3d ( sense 3.0 )included?
Good to see new dev added to the list of talented devs for DZ, and this is a time of sense 3.0 Roms rather than 2.1, guys welcome this new developer
is ext 4 recomended for a class 2 card or should i just not bother?
Happy to see another dev here. Excited to see what you can do!
slapshot30 said:
Happy to see another dev here. Excited to see what you can do!
Click to expand...
Click to collapse
+1
Sent from my HTC Vision using XDA App
master.peterm said:
is ext 4 recomended for a class 2 card or should i just not bother?
Click to expand...
Click to collapse
I believe ext4 requires at minimum class4 sd cards and up
Sent from my HTC Desire Z using XDA Premium App
Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
astriaos said:
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
+1
Sent from my HTC Vision using XDA App
On one hand, I appreciate the positive vibes. On the other, you're contributing to the overall gentrification and stupidity of this forum so I am torn between if I want to set you on fire for being an intentionally obtuse ****, of trying to buy you a beer via the internet.
astriaos said:
Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
dude are you serious? Make or port a rom and make perfect to your standards....
Sent from my HTC Desire Z using XDA Premium App
Yes I am perfectly serious. We have thread naming standards for a reason. He posted a ton of the same screens, they're undersized and hard to see. He also didn't really say what puts him apart from the rest. I fail to see the issue here.
I'm certainly not denigrating his work or the amount of time he put into its development. I believe all of these are valid questions. Why you gotta hate the fact that I'm not immediately sucking **** over a rom that hasn't even been put up for download yet?
PS: It's people like you that make me want to set fire to the internet. Go soak your head.
Edit: Now, shall we all grow up a bit and let the OP address my questions or shall we continue this pointless derail until one or the both of us gets banned, OR the mods decide to "delete offending material" which may or may not include perfectly legitimate questions.
astriaos said:
Hi there, thanks for posting up this supposed teaser. A couple things:
A: What exactly about this rom sets it apart from the plethora of other Sense3.0 ports to the DesireZ/G2.
B: You posted 5 completely identical screen shots of the exact same four screens, all of whom were undersized and difficult to see. Considering that this is a step up from the usual zero screen shots I can see why you felt that somehow more=better but let me assure you we would all be better off that if we could actually see one set of four, this would make me happier than punched beets.
C: There is a thread naming scheme in place to prevent confusion, is there any way you can edit your OP to reflect this? (On second look it seems you just forgot the date)
I look forward to seeing what you have to offer, welcome to XDA please try and help make this place not be the insufferable hellhole of double quotes, "+1"s, crap themeing, and poorly implemented code that this place seems to thrive on. Remember not all of us are 15 and have all day to bugtest!
Click to expand...
Click to collapse
A:what sets it apart is the look, it gives it a classic honeycomb look, whilst maintaining the functionality of sense 3
B: I have resolved this issue.
C: i will have a look on the naming scheme, and change it accordingly. Thanks.
BTW, im 15, in the UK, but i dont have all day to bugtest
THE ROM IS UP!!! ENJOY!!! REMEMBER TO REPORT ANY BUGS
HURRY UP! I HAVE WORK IN THE MORNING! In Arizona (US) and its 1:04 AM haha ;-)
Sent from my Synergy Rom using XDA App
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Included in IceColdJelly
waiting for feedback
thanks!
I know it sounds weird, and I certainly can't explain it, but the way I got around it was going into the system/lib/modules folder, copying a file (any) then deleting it. All of a sudden touch operated normally again. (until reboot). I'd start a game realise there's no multi touch, and carry out the above weirdness, and hey ho, it worked.
Spooky. But true. Done it over fifty times.
Thanks for the proper fix by the way!
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
Will this be incorporated into your CyanogenMod 9 ROM? Thanks
Sent from my HTC One X using xda premium
theDroidfanatic said:
Will this be incorporated into your CyanogenMod 9 ROM? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes, that's planned of course!
tbalden said:
yes, that's planned of course!
Click to expand...
Click to collapse
running fine in icecold jelly
thanks
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
will add commit to my kernel and report back. thanks for all your work. really appreciate it
Totally PRO! I knew you guys could do it
tbalden said:
yes, that's planned of course!
Click to expand...
Click to collapse
WooHoo!
Sent from my HTC One X using xda premium
Gonna add this to my future AoSP JB rom thanks tbalden
Team Fire
Hey,man.The work will be started again.The issue appeares again!
JohnYang1997 said:
Hey,man.The work will be started again.The issue appeares again!
Click to expand...
Click to collapse
Yep, i think it's normal: devs are using a fresh source that needs to be patched, most probably because AOSP roms and sense roms are using different libraries.
In case anyone needs it, this Multi touch fix was incorporated into the CM9 kernel, found here: http://d-h.st/ass
EDIT: nvm, its removed
Sent from my One X running Blade v4.7.0. At a mere 217 MB, with tons of AROMA Mods and tweaks, this, is what you want.
All I want to say is http://forum.xda-developers.com/showthread.php?t=2136731 this kernel has already fixed this earlly today(here +8.00)
Thanks will try later
Sent from my HTC One X using Tapatalk 2
tbalden said:
While fiddling around with the multitouch issue in games, i've found out what causes the loss of touch events upon releasing one finger.
A calibration code included in synaptics 3k driver that one x tegra3 is using, causes a reset of the touch screen states when one finger is released in a multitouch combo.
Removing the calibration define in the driver seems to have no negative side effects, and fixes the reset issue in the drriver.
Here's the commit related;
https://github.com/TeamNDVRu/htc-kernel-endeavoru/commit/08d512328aaa898d92190fbb85b7df1382ca29ec
Kernel devs, please test, and try to include this if you think it's appropriate, so users can enjoy a fully working touchscreen with all of the kernels, in combination of aosp derivation roms as well.
Click to expand...
Click to collapse
Just to mention it here:
It seems thatt removing the calibration by default can lead to the
"touchscreen not responsing after wakeup" issue.
This is very random but has been reported on both sense and AOSP
A possible solution is to make calibration control switchable in user-space
using a sysfs. Default is to enable it it and if problems with multi-touch
are experienced to let the user disable it "on demand"
see here for the impl
https://github.com/maxwen/enrc2b-kernel-BLADE/commit/deb62c8e4aa893030abc6a3e546092c9bb61cd74
Code:
echo 0 > /sys/android_touch/calibration_control
Hi All,
I have been reading that a fully functional Sense rom is not possible, and it is about kernels or such, But I am having trouble understanding the real problem. I tried digging the site for the reason, but searching HTC and Sense in a mobile developer forum hardly filters any entry, so please help me understand.
I am thinking as 3 layered structure, Linux kernel in the middle, drivers at the bottom and AOSP with sense modifications at the top.
The problem I am having is, since the kernel is GPL, how come nobody was able to glue all of them together. I am assuming the top part has some non standart calls/interfaces with the kernel, but it must be open source, so what is the part that makes patching same interfaces/calls to another kernel impossible?
If the calls require driver changes(taking in to account nearly all drivers are proprietary) that means we need same hardware of a sense device, but it possible if hardwares match, right?
The real question, is it not possible technically, too hard to implement practically or just won't worth the effort?
enginmanap said:
but it possible if hardwares match, right?
Click to expand...
Click to collapse
There isn't a single HTC device with OMAP4 CPU to my knowledge.
Sent from Samsung Galaxy Nexus @ CM11