yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] rogro82:
Ok ive done some work at work today :D

Ive cleared some of the calls made to some old features implemented in the original file like the touch cube etc.

Be aware that this isnt for daily use and only for testing purposes. But I really need some input on speed and reliability because i cant test everything on my own ( i flash my device every 4 hours or so so not really long testing times ). If you are not affraid of hard resetting your device and are willing to participate in testing current work please do but dont keep me responsible for freezes etc :)

I have only tested it on udk R4 because its easy for me to test speed on manilla 2d and it gives me a good impression of daily usability. And because i removed almost all calls to the original cube code it wont be any good for cube lovers as and original HTC roms.

Keep in mind that all ive done now has been done during work in a few hours and although ive tried to be on the safe side i cant tell you all is working as its suppose to and I think i havent done more then remove about 20% of garbage out of it.

I know not all is as fast as its supposed to be but like i said im better safe then sorry and i dont wanna hardreset every 2 mins or so... Some good testing can be done in Manila2d like scrolling through images fast and scrolling through the bottom bar. Also ive noticed that scrolling through the normal "All programs" is still on the slow side ( still need to resolve a lot of scrolling issues... HTC has included a lot of codes for all sorts of winmo controls like listviews etc ) but if you open up the all programs in manila from the programs menu u will see what kind of speed it can work at minimum....

As for the priorities mentioned earlier in this thread im going to set both the priority256 and the priorityhigh256 at 109 ( original microsoft value that can be found at msdn ) in the cab file so we can test the touch interface as it was suppose to be set up... you can easily change these values as you like ( read earlier posts ). Setting it lower then 109 will give it an higher priority which will make the device suffer more from touch input... Setting it higher ( upto 255 ) will give the touch input less priority and will make rendering faster but can also come of the cost of reliability.

I will continue further development ( basically ill start from scratch to better document changes and keep versioning etc ), but i really like to know if the current work done is working on other polaris devices so i will upload a cab file in about 10/20 minutes from now.
[Touch Cruise ROM Development] epimazzo:
Good news Rogro!

I can testify if you want!

Congrats and thanks for your time producing such thing!;)
[Touch Cruise ROM Development] rogro82:
Thnx epimazzo,

Make sure your rom has the "Sample Privileged Developer" Certificate installed because i signed both the file as the cab with this certificate ( files need to be signed because of being system file but im sure u already knew that ;) ).

Going to reinstall it myself at this moment to try out if all is working correct but ill upload it so you can test it also.

Can you also check if your registry is set at the values i specified? 109

Edit:

Just installed and everything is running fine...

If you test things can you tell me what is really faster ( programs etc ) and what needs to be worked on?

I just tested Manila and Opera and both seem faster in handling input and rendering to me... zoom in opera and scrolling in manila ( bar and images ) and using the all programs from manila seems ok.

I know the original all programs still suffers of lagging.. im going to try to fix that tomorrow as with some other issues ive seen.
[Touch Cruise ROM Development] epimazzo:
Sounds good.

I'll cook in a while...;)

I'm not sure about having this certificate already in...guess not..can you give me the path to correctly verify/install this? Should be in the root ones? Just have HTC previleged one. Not sample.

Thanks...:cool:
[Touch Cruise ROM Development] rogro82:
I have included the certificate i mentioned... most of the time its included.. i always use Microsoft Security Configuration Manager to install it and verify which certificates are installed ( dont know if you can download it but its part of visual studio ). I know udk has it installed as default so maybe its in the base wm6.1 rom.

If you dont have it and try to install the cab file you dont have any touch input and youll need to use a prog like MyMobiler to control your device or use the buttons :)
[Touch Cruise ROM Development] NeoS:
Did that touch.dll from HD help you any Rog?
[Touch Cruise ROM Development] rogro82:
Havent had a lot of time to look at it but it looks a lot like ours.... some things are taken out and some others are put in...

If i remember right it also uses the TSC2003 touch controller so hardware is the same.. If i have some more time ill look further into it to see if we can steal anything from it or port it :)
[Touch Cruise ROM Development] epimazzo:
I hadn't luck Rogro coz probably certificate wasn't well installed:p

Need to know where in ROM, I should add it correctly prior to cook.

Can you light me up? Shekhar? Anyone?

Thanks...:cool:
[Touch Cruise ROM Development] c_shekhar:
Have you made any changes in the orig touch.dll? If not then there is no need for the certification etc.

So far I understand that the additioal/change in two reg values was the only discovery done by you using the assembler (As mentioned in your initial post)?

correct me if I am wrong...
[Touch Cruise ROM Development] rogro82:
Without a certificate you cant load touch.dll because it will get no trust at boot.

I stripped out all old code like the old cube, old htc album and stuff that isnt really needed... So yeah its been changed a lot.. The 2 registry entries were just a quick fix to show how fast it can be. Now that i have rebuild the dll from assembly i can basically do whatever i want :)
[Touch Cruise ROM Development] rogro82:
Just install the microsoft security manager, that i have attached, on your pc. Connect to active sync and run the tool.

Now you can change the security model to security off and add development certificates. ( Device -> Add development certificates )
[Touch Cruise ROM Development] rogro82:
Updated 1st post to make it more clear what has been done and added all files needed in the post.
[Touch Cruise ROM Development] c_shekhar:
Thanks. It is clear now....
[Touch Cruise ROM Development] secoseco:
Hi rogro

I just test your new Touch DLL with c_shekhar last rom, i don't get any more performance with M2D, and I can't slide the pictures in Album from up to down, but working from down to up, No zoom ability and some time the screen not responsive for touching

roll back to old Touch DLL and waiting for your modifications

thx
[Touch Cruise ROM Development] rogro82:
Thanks for testing :)

Al last you had touch input so i know the rebuild is working on more roms... Strange thing is i dont have any of the problems you mentioned using udk's rom.

The version you tried dont really improves speed because its basically a copy of the original with some old stuff removed and not much else ( like i said i want to test if its working first before removing a lot of stuff )

If i have some time this week ill test it also with c_shekhar's rom. Maybe some one else with a udk rom can test it also to see if they also dont have any problems.

At the moment im trying to find out why scrolling in one app ( like explorer / all apps ) is so much slower then in ex. the all apps in manila... The biggest performance boost will be found there i guess.

I already have a complete stripped down version running but all though input seems more responsive it didnt speed up the scrolling.
[Touch Cruise ROM Development] secoseco:
Hi rogro82

I testing several rom and I will test the dll with every rom I test it, and will inform you with results

must test c_shekhar's last rom, it's super speed in displaying

any one want to test this dll just backup original dll (Touch.dll) in windows directory, install cap to add new dll and reg entry, test the new Touch, then repack the original dll again to windows directory to go back to orginal Touch

thx
[Touch Cruise ROM Development] polum:
Results UDK rom

Polaris with UDK working faster than ever !. Installed to days ago and no bugs detected so far...

Don´t know what you did but keep on that way because is working !
[Touch Cruise ROM Development] alinescoo:
Installed it on Touch Navia 1.5 Pro. Manilla 2D seems to be faster than before, S2U2 slider works without fragmentation.

The original reg keys are installed by default with this ROM .
[Touch Cruise ROM Development] imfloflo:
Try it on M-amine 2.0 RTM FRA.

Not working at all touchscreen not responding the only solution was to take controle by Mymobiler.exe and copy back the old touch.dll.

Before i tried to change the registry settings to 255-255 but without sucess not responding.

After that not responding anymore so hardreset or new rom install?don't know yet
[Touch Cruise ROM Development] rogro82:
Imfloflo did you install the certificate? If you dont you will indeed have no more touch input... Ive posted an application from microsoft which will allow you to easily install the appropriate certificates.

If you install the certificate using mymobiler then you can reinstall the cab file and you will have input again.
[Touch Cruise ROM Development] nir36:
edit:

nevermind..

i'll try it.
[Touch Cruise ROM Development] imfloflo:
Ok thanks, i don't install it, i hadn't understand it was necessary to install this specific certificat, I'm now with udk R4 rom will try later.
[Touch Cruise ROM Development] imfloflo:
edit sorry for double post didn't see i was the last post when i click on reply button.

I think you should add SamplePrivDeveloper.cer to the first post because you just add a soft to check certificat but can't install this one with it.

finally have it running on my udK r4 works fine will test it little more.

thanks
[Touch Cruise ROM Development] secoseco:
Hi rogro

test it with KhanX Touch_Navia_V1.4-PRO, very little improvement in speed may be not notice able to all

thx
[Touch Cruise ROM Development] rogro82:
Did you try Device -> Add developement certificates in the Security configuration manager?

Thanks for trying... still debugging to find out where most performance is lost
[Touch Cruise ROM Development] imfloflo:
Yes try to do Device -> Add developement certificates but nothing change after reset and install cab, the only solution was to copy .cer on my SD via mymobiler and to run it after that all was good.

it seems there are different speed of scroling in Program if i scroll very slow the render is good if i scroll fast it's lag. but if i you the "All programs "link on M2D programs tab all is fast and no lag
[Touch Cruise ROM Development] c_shekhar:
@rogro82

Can touch.dll be modified to ingnore any other third party prog (like phatpad) just like it ignores notes or album etc...?
[Touch Cruise ROM Development] bergfuechse:
Hi Polum,

are you running any navi progs, like TT7, MN7 or IGO... ? Did you notice any problems with it like the other guys?
[Touch Cruise ROM Development] polum:
TT7 no problems

Using TT7... So far so good
[Touch Cruise ROM Development] rogro82:
Sorry for not posting as much lately but ive been very busy at work... ill pick up on this as soon as i get some more free time.

Maybe ill just release the rebuild touch sourcecode so more people can contribute.
[Touch Cruise ROM Development] Bass A:
Hi,

have some problems with your dll.

when manilla 2d starts i can scroll over any icon with one move.

but then when i try a second time i can only move over max. 3 icon. then he stops the movement while moving with the stick. Same in explorer.

I tried already changing the registry keys but they dont' make any change to this problem.

i'm using m-amime 2.0.

but while moving it feels al littlebit faster than the original.

has someone maybe a cab for the original touch.dll ? :-)
[Touch Cruise ROM Development] HRQ.SLV:
Hey rogro82,

first thanks for all your contribuition on the Polaris forum!

Well, i took advantage that i was going to flash my phone and decided to try the touched cab on the first post.

For now (1 day) the results are good! I can see improvements when i scroll the pages on UltimateLaunch (got tired of M2D). The scroll is much smother!

I'm using now 3LIT3 V Suite [Naked] Rom.

I hope that you haven't abondened this project!

You are a very big help to us Polaris users!
[Touch Cruise ROM Development] SuperJMN:
I noticed that new ROMs with 6.5 suffer from the same issue: when you touch the screen, the CPU load goes up like mad.

I tweaked the registry with the famous values (Priority and Priority256), and the improvement in the performance is very very noticeable.

Are there any drivers for Polaris? I heard somebody saying there's one for the Kaiser.

Please, enlighten us!
[Touch Cruise ROM Development] SuperJMN:
Confirmed

Confirmed: the touch driver makes the graphic performance HORRIBLE. If you thought WM6.5 runs smooth, just take a look at when you decrease the priority of the badass driver: it runs SMOOTH!!! like if it had 2D acceleration...! When it has the default priority, it consumes almost the whole CPU.

rogro82 told us that touch.dll was a bunch of tricky-programmed code. Anyone to "touch" that touch.dll?
[Touch Cruise ROM Development] HRQ.SLV:
More Priority's

@SuperJMN

If you liked does settings try this ones:

I decided to try them out after rogro82 started this thread.

Here you can see what MSDN says about this subject:

http://msdn.microsoft.com/en-gb/library/aa910698.aspx

And here is more about this subject:

http://msdn.microsoft.com/en-gb/library/aa910702.aspx

Well for me there has been a small speed increase. Hope you have luck yourself!;)

This values where tested only with WM6.1, and the best results so far have been with chavonbravo 3LIT3 VI (great ROM).

Have fun!

P.S.: after soft-reset and first boot turn the screen on and off (don't know why this happens) and then you'll see the diference!
[Touch Cruise ROM Development] TITAN-23:
I have a Kaiser and have 50+% cpu usage when the touch screen is pressed. I cannot find any project like this one for my Kaiser and this cab did not work on my rom. I am wondering if there are any plans for it to be developed further.
[Touch Cruise ROM Development] mr.jaguar:
on a raphael, changing the registry settings as stated by rogro, the touch screen became unresponsive, I did not use the touch.cab, but just used the registry changes.
[Touch Cruise ROM Development] Antubis:
Is there any chance the driver may be ported to Nike too ? This work look very promising.

I tried to install the CAB but my device just didn't get responsive anymore (had to hardreset :P)
[Touch Cruise ROM Development] SuperJMN:
I think we all Polaris users should focus on this. It's unacceptable that we have >50% of CPU usage when the screen is touched. It slows down every response and makes our devices non touch-friendly.

I can conclude that the effects of installing P3D and GfxBoost are way better in conjunction with this .cab.

I encourage any coder alive to check this .dll to enhance it and remove all the unnecessary stuff in it.

@rogro82, I've tested your .cab and it makes the touch screen response more quick, while some users report unresponsive touch screens.

Can you tell us what tools you used to "rebuild" this .dll? Some developers, me included, could take a look at it to find ways to improve this key file.
[Touch Cruise ROM Development] raulzitoo:
Bachup

I need urgent the original htc polaris touch.dll... Where i can find this?? thnaks
[Moto G5S Plus Questions & Answers] maicomaico:
Hello guys

First I apologize for my bad English

I'm new in the business, I came across the first big problem with a Motorola Moto G5S Plus (XT1802) that doesn't boot, it turns on the Bootloader logs screen, and presents the following messages:

AP Fastboot Flash Mode (Secure)

Fastboot Reason: Volume down key pressed

failed to validate boot image

ERROR: Failed to pass validation, backup to fastboot

The device worked perfectly, it started to crash, with difficulties to restart, then it crashed in the bootloader. I put root a while ago, and I was with android 8.1.0. I've tried everything.

Here is my output of the command "fastboot getvar all":

C:\Users\PRISTON TALE\Desktop\Comandos ADB Romtekcell>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8953-C2.12(*)

(bootloader) product: sanders

(bootloader) board: sanders

(bootloader) secure: yes

(bootloader) hwrev: P4

(bootloader) radio: 4

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B

(bootloader) cpu: MSM8953

(bootloader) serialno: 2006e0b2

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: FBC7888C00000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 534773760

(bootloader) reason: Fall-through from charger boot mode

(bootloader) imei: 000000000000000

(bootloader) meid:

(bootloader) date: 01-01-1970

(bootloader) sku: 000000000000000

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) devcfg.git: devcfg.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) cmnlib64.git: cmnlib64.git

(bootloader) prov.git: prov.git

(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

(bootloader) current-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

all: listed above

Finished. Total time: 0.141s

As you can see in the command output and in the attached photos, what worries me the most is that both the IMEI and the model are zeroed, neither the IMEI number nor the XT1802 appears. On the Barcodes screen, everything is also reset, with the exception of the serial, which appears perfectly.
[Moto G5S Plus Questions & Answers] Biz92k:
Same situation for me, no solution available after 2 years.
[OnePlus 8 Questions & Answers] faXal@21:
View attachment 5644881

Even After Relock Bootloader it not passes Google & WidewineL1 Key. Safety Net Also Seems Broken. I have tired every msm tool but no luck. I think unlock method is break the TA partition

View attachment 5644883

Is there any possible solution for this issue or do you also face this issue on your op8 Verizon after unlock the bootloader.

Safety Net Shows CTS Profile Mismatch

View attachment 5644889
[OnePlus 8 Questions & Answers] Xryphon:
Unfortunately, this is the case when unlocking the bootloader on any device. You can try to lock it again, or you can simply use the Magisk Safetynet Module to get some features back.

However, Widevine will likely be that way forever; one should have been notified of this when doing any bootloader unlocking.
[OnePlus 8 Questions & Answers] faXal@21:
Yes bootloader relock helps to pass basic integrity but cts still mismatch. So lets hope A12 Update will bring some changes.
[Fire TV Android Development] SweenWolf:
Package Installer:

Added TV layout

Amazon Security:

Removed Apps Blacklist check

LM Settings:

Launcher Manager -> LM Settings

Removed everything related to launcher

ADB and LOGS are removed

changed package name

Needs to be setup using ADB (only once)
[Fire TV Android Development] SweenWolf:
For total beginners.

To install 6702 stock rom with patches.​

Download NS6702 (Stock without eFuse).zip

Download Patch - 6.7.0.2 (mantis).zip

Move these zip to USB Thumb drive.

Attach the thumb drive and a mouse to your Firestick 4K

Open TWRP

Go to wipe > advanced wipe > select

Dalvik-cache, cache, system, data

(Do not check Internal storage, this is the place where your downloaded stuff is stored)

then "Swipe to wipe"

press home

click on Install

select storage 1 (this will most likely be your thump drive)

select NS6702 (Stock without eFuse).zip and install

after that press home again then go to install

select Patch - 6.7.0.2 (mantis).zip and install

Click Wipe Dalvik-cache/cache and click on reboot.

Launcher Selection​

If you want to use CLH but want to keep using the stock launcher, you can

enable CLH, and select KFTV laucher as your launcher, it will work the same, or you can select any launcher of your choice.

Stock System Settings​

You can access stock system settings by pressing [HOME] twice and select "System Settings"

Apps Update​

Some of your apps will not be updated, to update them either go to the github gist on OP and download and install the lastest apks. or double press [HOME] and press "FTV OTA App".

Click on "APP UPDATES:BLOCKED" [It will then say "APP UPDATES:ALLOWED]

Just restart your stick after that.
[Fire TV Android Development] SweenWolf:
CLH v1.13

Updated at: UTC 21-04-2024 08:28:28 AM

Changes:

Changing UI mode does not require a reboot anymore.

HDMI Broadcast status is fixed.

Button Behaviours:->

Long Pressing Back Button opens CLH Settings

Double Tapping Home Button opens CLH HUD
[Fire TV Android Development] Finnzz:
Wow, this great work! I love the new features.

But everything is either Plus or Max these days. It should be 'Launcher Manager Plus' or 'Launcher Manager Max' :D
[Fire TV Android Development] Tejas tedi:
Can you make anything like this for firestick lite?
[Fire TV Android Development] SweenWolf:
Without a device i will not be able to test the patches. I don't want to make someone's stick a paperweight.

Maybe I will create a version but will not be able to maintain it.
[Fire TV Android Development] xerel89:
How I can set unlocked bootloader on the stick?
[Fire TV Android Development] Sus_i:
Nothing to worry about as long as the preloader is untouched ;)

and maybe a bit easier, since there isn't an efuse to keep from burning :)

--> Launcher Manager Pro Plus + ;)

(y)
[Fire TV Android Development] anphabvn:
Can i use it for old firmware??
[Fire TV Android Development] Zerollama:
Thank you for your hard work! I'm having a problem with my FireStick after I flashed patch 6.2.9.0 my stick won't boot anymore ☹️. It just gets to the FireTV loading screen and doesn't get any further. What can I do?
[Fire TV Android Development] SweenWolf:
Have you flashed patched boot image?
[Fire TV Android Development] SweenWolf:
You shouldn't, your stick will bootloop
[Fire TV Android Development] Zerollama:
Thank you, yeah I had flashed the boot image too. I ended up reflashing my stick with the full firmware and it's booting again now. I'll stick to the regular the Launcher Manager for now.
[Fire TV Android Development] anphabvn:
@SweenWolf can you create Wolf Laucher Manager with root supported? Old LM use adb only to work !!!
[Fire TV Android Development] shin3c:
del...
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Love the wolf launcher and appreciate all your contributions and efforts.

Was wondering if we can have the patches for Firetv tank on the latest firmware 5.2.9.5 ?,as it does not support Accessibility services and features blocked by Amazon.

Can help you with the testing.

Thank you once again!

Cheers!
[Fire TV Android Development] Skel40:
@SweenWolf I successfully compiled the 6.2.9.0 rom with all the patches you have and I need help making newer ones for 6.2.9.7/4655 .jar, and odex
[Fire TV Android Development] SweenWolf:
6.7.0.1 patched