Hi guys!
I encountered a weird problem with the backlight adjust.
COM2 build, Blackstone OEM, Sense2.5 and Sense2.1
Something in my kitchen is broken, because the manual backlight slider has no effect. Automatic adjust is working and the slider itself.
But sliding does not change backlight brightness. :/
Any Ideas where to start looking? (already tried different power packages)
thx 4 any hint!
goldlocke said:
Hi guys!
I encountered a weird problem with the backlight adjust.
COM2 build, Blackstone OEM, Sense2.5 and Sense2.1
Something in my kitchen is broken, because the manual backlight slider has no effect. Automatic adjust is working and the slider itself.
But sliding does not change backlight brightness. :/
Any Ideas where to start looking? (already tried different power packages)
thx 4 any hint!
Click to expand...
Click to collapse
You should include HTC Util from a blackstone ROM.
EpiphanyNL said:
You should include HTC Util from a blackstone ROM.
Click to expand...
Click to collapse
Hi to everyone,
I have exactly the same problem and I could not find "HTC Utility" Cab / packages from Blackstone although I used search function
Could someone share this package / cab please ?
PS : I have Diamond with WM 6.1 + Sense 2.5 2016
Regards
EpiphanyNL said:
You should include HTC Util from a blackstone ROM.
Click to expand...
Click to collapse
You are so right sir! Thank you very much.
It was indeed a bad combination of non-Blackstone HTC Util and a Power_3_6_0_0 package.
mkucuksari said:
I have exactly the same problem and I could not find "HTC Utility" Cab / packages from Blackstone although I used search function
Could someone share this package / cab please ?
PS : I have Diamond with WM 6.1 + Sense 2.5 2016
Click to expand...
Click to collapse
Hi, why would you want to use a Blackstone HTC Util on the Diamond?
Go look for that in a shipped Diamond ROM.
+1, you need HTCUtil which suites your device model otherwise it won't work.
goldlocke said:
Hi, why would you want to use a Blackstone HTC Util on the Diamond?
Go look for that in a shipped Diamond ROM.
Click to expand...
Click to collapse
I am using HTCUtil 4_19_0_0 form lastest Huashan rom on Topaz and it works. How is this possible?
billyJ said:
I am using HTCUtil 4_19_0_0 form lastest Huashan rom on Topaz and it works. How is this possible?
Click to expand...
Click to collapse
It probably suits your device! I am using util from Huashan in Rhodium as well without any issues.
I don't know mate you are lucky.
Maybe you could check dependencies if you like to know why?
My experience is that using HTCUtil from the same device model makes the backlight sliders work.
You should know that cooking is all about trial and effort so if it works it works.
It can also happen that a package make one thing work and the other thing not if you know what I mean.
That's why you need to test all stuff working before you publish a rom.
The name says what it does, HTCUtil is taking care of HTC utilities so I would check them all.
billyJ said:
I am using HTCUtil 4_19_0_0 form lastest Huashan rom on Topaz and it works. How is this possible?
Click to expand...
Click to collapse
Laurentius26 said:
I don't know mate you are lucky.
Maybe you could check dependencies if you like to know why?
My experience is that using HTCUtil from the same device model makes the backlight sliders work.
Click to expand...
Click to collapse
I doubt the HTCUtil is device specific dll.
Look at the Leo 1.66 stock rom uses HTCUtil 4.12.0.1 same as Rhodium/Topaz's.
Yah offcourse version numbers are same, I've dumped many roms myself.
But I've learned it the hard way in trial and effort, changing HTCUtil make the backlight sliders work.
williyung said:
I doubt the HTCUtil is device specific dll.
Look at the Leo 1.66 stock rom uses HTCUtil 4.12.0.1 same as Rhodium/Topaz's.
Click to expand...
Click to collapse
Related
New call log tab which support mentioned rom + tested and proven on 2.03.421.1 base rom . (Fabliv call history tab may cause some menu malfunction)
new version
http://forum.xda-developers.com/showthread.php?t=487825
Sorry, where did you find the second colour line, in the taskbar? Is it for the memory?
Hoping you can help me, best regards!
thanks, i am now choosing new rom - want to find one stable... hope i can find 2.0 based RUssian rom otherwise will use some 2.0, and your's tab
problem, and on screen too - no nubmer showing...
plvigo said:
Sorry, where did you find the second colour line, in the taskbar? Is it for the memory?
Hoping you can help me, best regards!
Click to expand...
Click to collapse
attach please create a shortcut in the startup folder or paste it in the startup folder
Yuna said:
thanks, i am now choosing new rom - want to find one stable... hope i can find 2.0 based RUssian rom otherwise will use some 2.0, and your's tab
Click to expand...
Click to collapse
official htc wwe 2.0 rom
http://forum.xda-developers.com/showthread.php?t=465324
Really many thanks for your kind help. Can I ask you which is the difference between dcibattery and VistaHide Battery? I read that dcibattery can decrease only by 10%. Is it true? Again, many thanks!
lucasjohny said:
attach please create a shortcut in the startup folder or paste it in the startup folder
Click to expand...
Click to collapse
??has anyone tried this callhistory tab on the new 2.03 roms ??
Is this developed by HTC and ripped from another ROM or is this developed by a XDA-Dev user?
Ripped from (i think) O2 ROM...
Calllog works with the new AZTOR Rom 2.03
Yuna said:
Ripped from (i think) O2 ROM...
Click to expand...
Click to collapse
If this is from an O2 rom than not from the german one or at least from a Toch HD rom. I have a german O2 XDA Diamond and in the official rom there is no call log tab.
.................................
Thanks...it works good on CT6.2ROM
Thanks. This solved my problem on call history.
The comm tab also works on 2.00.421.1 but because comm tab and tab setting in Settings shared the same 1f3be060_manila file therefore I could get either comm tab or tab setting function working. I do not know how to edit the 1f3be060_manila file. Does anyone know how to do this. having both enable would be a cool thing to do.
Thanks
Dynomite232 said:
??has anyone tried this callhistory tab on the new 2.03 roms ??
Click to expand...
Click to collapse
Yer, tested and worked on Dutty v4 based on 2.03
the cab works just perfext with the 2.03 aztor x, so thx alot
Thnx alot its just what i was looking for.
I really like it that when you got a missed it shows it down at the sliding menu.
Hi!
Anyway to get this on a 2.03 HD rom? Thanks for getting it to 2.03
Aletheia said:
Hi!
Anyway to get this on a 2.03 HD rom? Thanks for getting it to 2.03
Click to expand...
Click to collapse
can but i don't have hd so please copy this file 26948339_manila from the windows folder and send it to me.
Alright thanks, here you go (renamed it to .zip).
I've been breaking my head trying to figure out why the Rhodium Menu Enhancement works fine on some phones but never works on others. Is it certain builds? Is it certain files? Certain file versions?
In order to figure it out, I want to collect as much info as possible on the dependencies. I know that the dependencies are:
Coredll.dll
aygshell.dll
I'm gonna try to track down the dependencies for each dll.
I need some help. Help me gather as much info on it as possible.
gwes.exe and gwes.exe.0409.mui are the big ones. the ones you mentioned aren't necessary
mbarvian said:
gwes.exe and gwes.exe.0409.mui are the big ones. the ones you mentioned aren't necessary
Click to expand...
Click to collapse
WHICH gwes.exe and gwes.exe.0409.mui?
I am using the 21042 build and the Notification enhancement works but not the menu enhancement.
ivanmmj said:
WHICH gwes.exe and gwes.exe.0409.mui?
I am using the 21042 build and the Notification enhancement works but not the menu enhancement.
Click to expand...
Click to collapse
the ones from that build. im using them and both are working fine.
which menu enhancement .cab are u using?
also, make sure u have verinfou2.dll somewhere in the rom and the htc scroll package
mbarvian said:
the ones from that build. im using them and both are working fine.
which menu enhancement .cab are u using?
also, make sure u have verinfou2.dll somewhere in the rom and the htc scroll package
Click to expand...
Click to collapse
I have verinfou2.dll version: 1.0.1818.2525. What version are you using?
What HTC Scroll Package? I've got HTCScroll.dll version 1.0.1911.1624. What else is in the package?
Also, do you have RunCC installed?
On my own roms, WM 6.1 or WM 6.5, HTCMenus only work when manila is active.
VERSION: "MenuEnhancement"="1_0_19123624_01"
ark666 said:
On my own roms, WM 6.1 or WM 6.5, HTCMenus only work when manila is active.
VERSION: "MenuEnhancement"="1_0_19123624_01"
Click to expand...
Click to collapse
Isn't there an option that disables the Manila Check. I'm almost 90% sure.
ark666 said:
On my own roms, WM 6.1 or WM 6.5, HTCMenus only work when manila is active.
VERSION: "MenuEnhancement"="1_0_19123624_01"
Click to expand...
Click to collapse
[HKEY_LOCAL_MACHINE\Software\HTC\HTCMenus]
"EnableManilaCheck"=dword:00000000
how do i get RunCC and verinfou2.dll and HTC Scroll Package?
tcchuin said:
how do i get RunCC and verinfou2.dll and HTC Scroll Package?
Click to expand...
Click to collapse
you can get them from latest topaz rom
dump it and you have the packages
must we cook it into a rom?or can we convert it into a cab file and install?please tell me...if can..please help me dump it and convert it int cab..thx..^^
tcchuin said:
must we cook it into a rom?or can we convert it into a cab file and install?please tell me...if can..please help me dump it and convert it int cab..thx..^^
Click to expand...
Click to collapse
There are always a few cabs out there. The problem is getting it to work in the first place.
HTCScroll.dll is definately needed. it may also require ResLoader.dll (part of the ResourceProxy package), but i'm not 100% sure on that.
on most roms running build 21xxx, you'll have to cook it in to get it working.
kimi_sae_ireba said:
HTCScroll.dll is definately needed. it may also require ResLoader.dll (part of the ResourceProxy package), but i'm not 100% sure on that.
on most roms running build 21xxx, you'll have to cook it in to get it working.
Click to expand...
Click to collapse
I have ResLoader there for other reasons and I only cook ROMs, never use CABs, but it's still not working... I'm going to try the 21015 GWES and see what happens.
ivanmmj said:
I've been breaking my head trying to figure out why the Rhodium Menu Enhancement works fine on some phones but never works on others. Is it certain builds? Is it certain files? Certain file versions?
In order to figure it out, I want to collect as much info as possible on the dependencies. I know that the dependencies are:
Coredll.dll
aygshell.dll
I'm gonna try to track down the dependencies for each dll.
I need some help. Help me gather as much info on it as possible.
Click to expand...
Click to collapse
You can figure it out yourself by using http://www.dependencywalker.com/
Hi,
heres an challange/issue that i cant solve. If i press the ex big ben in footprints, and then menu, i dont the the option to use digital compass. Leo ROM 1.66 have this option, but i havent found a package that works with the new manila with positionfix. Ive expremented a bit and just replaced the manila footprint package with the one from Leo 1.66/1.77, but slowed manila down, or it crashes.
Im no good at editing manila files, anyone got this working, or are willing to give it a shot?
greets
/bp
barbapappa_86 said:
Hi,
heres an challange/issue that i cant solve. If i press the ex big ben in footprints, and then menu, i dont the the option to use digital compass. Leo ROM 1.66 have this option, but i havent found a package that works with the new manila with positionfix. Ive expremented a bit and just replaced the manila footprint package with the one from Leo 1.66/1.77, but slowed manila down, or it crashes.
Im no good at editing manila files, anyone got this working, or are willing to give it a shot?
greets
/bp
Click to expand...
Click to collapse
Did you try swapping the Footprints_Pages.XML ?
skr_xd said:
Did you try swapping the Footprints_Pages.XML ?
Click to expand...
Click to collapse
Didnt tried that Will try and report back..
barbapappa_86 said:
Didnt tried that Will try and report back..
Click to expand...
Click to collapse
It will work
Regards,
kumar
skr_xd said:
It will work
Regards,
kumar
Click to expand...
Click to collapse
Yep, it did The only file in the package that i didnt check
barbapappa_86 said:
Yep, it did The only file in the package that i didnt check
Click to expand...
Click to collapse
Glad it worked for you
Please change the thread title adding [Solved].
Thread closed by OP request do to solution being found
hi guys,
i have a problem with quickgps.
It doesnt update. When i try to update it says
DATA ACTIVATION FAILED
Location settings must be on so that downloading satelites can be used to speed up GPS startup time
I have tried several packages but none of them worked.
i have searched a lot but nothing helps
Everything else is working fine only this little isseu is driving me mad
thx for the help
edit i have atached the reg file what i have for quickgps
EDIT :
the reason was Boot_Launcher.
If you guys want to use Quick Gps include Boot_Launcher
If you don't provide some info of what kitchen you use/what base you use/which build, there is no one who can help you I ques.
Grtz Leo
Laurentius26 said:
If you don't provide some info of what kitchen you use/what base you use/which build, there is no one who can help you I ques.
Grtz Leo
Click to expand...
Click to collapse
well i use Os kitchen and EVK
i use the com2 branch (21898) same thing in com5
It doesnt matter which build i use, I have the same problem with quick gps
I have read somewhere it is related to the oem packages?
I have tried it with different manila packs like from rhodium an hd2 2.07 2.10
last but not least i have used as base the latest oem drivers from HD (1)
thx for the reply
I actually just had the issue-it was because I was testing out removing things from the startup queue to get faster reboots, and I removed bootlauncher, mainly to kill startkey.exe and sipgt_app, because I use FNKBD. Anyway, I overlooked the fact that bootlauncher also kick-starts some services (some totally effing useless, like usb2pcpopup). Among the services is gpsaux.dll-make sure it's loaded. If it isn't, the download doesn't work.
Sorry mate but that's what I'm asking, 'which base are you using OEM/EXT'.
Maybe a packages list would be wise if you made a hybrid rom I'm just quesing
rambo12345 said:
well i use Os kitchen and EVK
i use the com2 branch (21898) same thing in com5
It doesnt matter which build i use, I have the same problem with quick gps
I have read somewhere it is related to the oem packages?
I have tried it with different manila packs like from rhodium an hd2 2.07 2.10
last but not least i have used as base the latest oem drivers from HD (1)
thx for the reply
Click to expand...
Click to collapse
Farmer Ted said:
I actually just had the issue-it was because I was testing out removing things from the startup queue to get faster reboots, and I removed bootlauncher, mainly to kill startkey.exe and sipgt_app, because I use FNKBD. Anyway, I overlooked the fact that bootlauncher also kick-starts some services (some totally effing useless, like usb2pcpopup). Among the services is gpsaux.dll-make sure it's loaded. If it isn't, the download doesn't work.
Click to expand...
Click to collapse
that could be the problem because i have removed some of the startup queue
i will look in that
thx
Sorry mate but that's what I'm asking, 'which base are you using OEM/EXT'.
Maybe a packages list would be wise if you made a hybrid rom I'm just quesing
Click to expand...
Click to collapse
i use leo 2.10 packages as ext and http://forum.xda-developers.com/showthread.php?t=466040 as mine Oem
thx
edit: attached build log
Looking at your buildlog I would try to downgrade the commmanager as well to a Blackstone compatible one.
rambo12345 said:
i use leo 2.10 packages as ext and http://forum.xda-developers.com/showthread.php?t=466040 as mine Oem
thx
edit: attached build log
Click to expand...
Click to collapse
Since i have had the same problem with Kaiser and Mega EXT packages,never had QuickGps working, how can be the communication manager involved in this such a problem?
Laurentius26 said:
Looking at your buildlog I would try to downgrade the commmanager as well to a Blackstone compatible one.
Click to expand...
Click to collapse
Hi,
Because it has several components for Internet and bandswitching and Quickgps can only do a upgrade if your Internet connection is working 100%.
If you check the dlls/exe in commmanager it has a lot of dependencies.
ril.dll
dnsapi.dll
iphlapi.dll
to name a view.
Not that I'm such a expert but these dlls could affect Quickgps if you ask me.
af974 said:
Since i have had the same problem with Kaiser and Mega EXT packages,never had QuickGps working, how can be the communication manager involved in this such a problem?
Click to expand...
Click to collapse
Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Laurentius26 said:
Hi,
Because it has several components for Internet and bandswitching and Quickgps can only do a upgrade if your Internet connection is working 100%.
Click to expand...
Click to collapse
Sorry added some extra to my previous post.
af974 said:
Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Click to expand...
Click to collapse
Mostly QuickGps.exe dependency are into Shared_Modules but i cant find a dll into the dump folder IESHIMS.DLL, using depends Walker though.
I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.
af974 said:
Yes of course, but the error gotten is "Enable to retrieve data , location service must be on"....i switched to the old QuickGps and it works.....i guess ill go to check some dependency.
Click to expand...
Click to collapse
try changing this reg in mega pkg to dword:00000001
Code:
"EnableInitData"=dword:00000000
Laurentius26 said:
I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.
Click to expand...
Click to collapse
I'd like to adopt this post as my own.
Yes you are right, indeed i gave up with new QuickGps but honestly i feel good if i can find a solution to let it work .
Laurentius26 said:
I know most people like to use the latest packages but sometimes it's good to dowgrade certain components so they suite better to your oemdrivers.
A componont like commmanager is trivial in this case.
Click to expand...
Click to collapse
Thanks Shane im going to try it ....just need to cook it again.ill let yoknow later if it work.
twopumpchump said:
try changing this reg in mega pkg to dword:00000001
Code:
"EnableInitData"=dword:00000000
Click to expand...
Click to collapse
Unfortunaly no luck with that reg key,still getting same error.
I would try to change CommManager but damn the old one for Kaiser its so ugly
Haha.. well you can try first and see if QuickGPS works.
What Commmanager are you using btw, a converted 2.10 WVGA to QVGA?
af974 said:
Unfortunaly no luck with that reg key,still getting same error.
I would try to change CommManager but damn the old one for Kaiser its so ugly
Click to expand...
Click to collapse
Ehehe...yup just for try if QuickGps work otherwise i will delete
Im using the Original from Mega Touch 2.
Laurentius26 said:
Haha.. well you can try first and see if QuickGPS works.
What Commmanager are you using btw, a converted 2.10 WVGA to QVGA?
Click to expand...
Click to collapse
Man it's just wild quesing as I don't know your kitchen LoL.
Maybe you need to downgrade Quickgps and the depended packages as well.
Best advise I can give is to keep everything from the same source close to your device specs and upgrade packages one by one and see yourself if everything functions.
Sorry old boring story but that's how I work testing many times.
af974 said:
Ehehe...yup just for try if QuickGps work otherwise i will delete
Im using the Original from Mega Touch 2.
Click to expand...
Click to collapse
hello to all
i have cooked a rom with 23673 build with manila 2015 sometimes i had this graphical problem i dont know what provoque this problem...;please see the screenshot below
will anyone please help if u have any idea about this problem...and i also i have enountered this problem with 23569 build and my manila is cfc compressed
thanks to all:
shafizal said:
hello to all
i have cooked a rom with 23673 build with manila 2015 sometimes i had this graphical problem i dont know what provoque this problem...;please see the screenshot below
will anyone please help if u have any idea about this problem...and i also i have enountered this problem with 23569 build and my manila is cfc compressed
thanks to all
Click to expand...
Click to collapse
i think its because of position fix
if you look at the top and lower bar it arent affected by the strange affect
not sure asi dont use builds with startmenu at the bottom but could it be positionfix is a manilla file and there fore also needs to be cfc'd?
just a wild guess though
miniterror said:
i think its because of position fix
if you look at the top and lower bar it arent affected by the strange affect
not sure asi dont use builds with startmenu at the bottom but could it be positionfix is a manilla file and there fore also needs to be cfc'd?
just a wild guess though
Click to expand...
Click to collapse
i did not think so... i did not use position fix here is the new screenshot once again i have this problem ..;i have this problem with com 3 build maybe i used gwes.exe,gwes.040c.ex and commctrl.dll from 23563 build for bold font issue with 23680 build...may be this one provoque the problem
This time it happens with Manila 2018
That definitely looks like an OpenGL driver problem. Make sure you're not overwriting the stock GL drivers with third party drivers, such as chainfire's or any "other" drivers...
Well there is only a way to know it...cook a rom with original gwes.exe and see if it works.
Do you know of Cloudyfa bold font fix right?http://forum.xda-developers.com/showthread.php?t=705334
Maybe using his files should solve your problem.
shafizal said:
i did not think so... i did not use position fix here is the new screenshot once again i have this problem ..;i have this problem with com 3 build maybe i used gwes.exe,gwes.040c.ex and commctrl.dll from 23563 build for bold font issue with 23680 build...may be this one provoque the problem
This time it happens with Manila 2018
Click to expand...
Click to collapse
NRGZ28 said:
That definitely looks like an OpenGL driver problem. Make sure you're not overwriting the stock GL drivers with third party drivers, such as chainfire's or any "other" drivers...
Click to expand...
Click to collapse
thanks for the reply bro ...i cooked with Neo drivers 2010 and i deleted the old open vg drivers from oem drivers....
af974 said:
Well there is only a way to know it...cook a rom with original gwes.exe and see if it works.
Do you know of Cloudyfa bold font fix right?http://forum.xda-developers.com/showthread.php?t=705334
Maybe using his files should solve your problem.
Click to expand...
Click to collapse
thanks for the reply//
it happens suddenly when i wake my device with my power button;..cloudy fix has gwes.exe.0409 like mine is french so why i used from 23563 build..
shafizal said:
thanks for the reply bro ...i cooked with Neo drivers 2010 and i deleted the old open vg drivers from oem drivers....
Click to expand...
Click to collapse
Ahhh!!! Remove NeoDrivers and watch manila work properly
NRGZ28 said:
Ahhh!!! Remove NeoDrivers and watch manila work properly
Click to expand...
Click to collapse
ok thanks NRG will try........but is it any other video drivers for xperia or Stock drivers are good because i never cooked with stock video drivers..
thanks once again
NRGZ28 said:
Ahhh!!! Remove NeoDrivers and watch manila work properly
Click to expand...
Click to collapse
Yes u r right NRG with stock drivers it works well...No graphical problem ..But without third party drivers in Xperia with sense 2.5 ...ok will try with topaz open vg and d3dm from?????