Jump to content

Recommended Posts

Guest xlightwaverx
Posted (edited)

Installed some sense packages on stock today. Can't find the provxml or any registry settings that tell Sense to start on boot. It just goes to windows default titatium. when i look in the settings to see what's checkable on the today screen, sense isn't even there.

any suggestions?

Edited by xlightwaverx
Guest amdzero
Posted
Installed some sense packages on stock today. Can't find the provxml or any registry settings that tell Sense to start on boot. It just goes to windows default titatium. when i look in the settings to see what's checkable on the today screen, sense isn't even there.

any suggestions?

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"Windows Default"]

"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"HTC Sense"]

"DLL"="ManilaToday.dll"

"Order"=dword:00000000

"Selectability"=dword:00000002

"Type"=dword:00000004

"Enabled"=dword:00000001

try to cook this into an .rgu

preferably one that is run last.

Guest xlightwaverx
Posted

Thanks AMD. But more importantly where did you find that information out...??? And don't tell me because you been doing this for 6 months. :(

X

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"Windows Default"]

"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"HTC Sense"]

"DLL"="ManilaToday.dll"

"Order"=dword:00000000

"Selectability"=dword:00000002

"Type"=dword:00000004

"Enabled"=dword:00000001

try to cook this into an .rgu

preferably one that is run last.

Guest amdzero
Posted
Thanks AMD. But more importantly where did you find that information out...??? And don't tell me because you been doing this for 6 months. :(

X

its in the sense folder...

d042d2b9-5904-4305-b413-a0b2ec7c43d1.rgu

Guest xlightwaverx
Posted

i think im using way different packages.

its in the sense folder...

d042d2b9-5904-4305-b413-a0b2ec7c43d1.rgu

Guest xlightwaverx
Posted

Ya ok, that did not work at all.

Any other suggestions?

X

Thanks AMD. But more importantly where did you find that information out...??? And don't tell me because you been doing this for 6 months. :(

X

Guest xlightwaverx
Posted

This still isn't working, any suggestions....

zzzzzzPureSense.provxml in OEMLang Directory where the other Provxml files get parsed.

zzzzzz so it is at the end, still nothing taking.

flashed 6 times.

Please help.

<wap-provisioningdoc>

<characteristic type="Registry">

<characteristic type="HKLM\Software\Microsoft\Today\Items\"Windows Default"" translation="filesystem">

<parm name="Enabled" datatype="integer" value="0"/>

</characteristic>

<characteristic type="HKLM\Software\Microsoft\Today\Items\"HTC Sense"" translation="filesystem">

<parm name="DLL" datatype="string" value="ManilaToday.dll"/>

<parm name="Order" datatype="integer" value="0"/>

<parm name="Selectability" datatype="integer" value="2"/>

<parm name="Type" datatype="integer" value="4"/>

<parm name="Enabled" datatype="integer" value="1"/>

</characteristic>

</characteristic>

</wap-provisioningdoc>

Guest amdzero
Posted
This still isn't working, any suggestions....

zzzzzzPureSense.provxml in OEMLang Directory where the other Provxml files get parsed.

zzzzzz so it is at the end, still nothing taking.

flashed 6 times.

Please help.

<wap-provisioningdoc>

<characteristic type="Registry">

<characteristic type="HKLM\Software\Microsoft\Today\Items\"Windows Default"" translation="filesystem">

<parm name="Enabled" datatype="integer" value="0"/>

</characteristic>

<characteristic type="HKLM\Software\Microsoft\Today\Items\"HTC Sense"" translation="filesystem">

<parm name="DLL" datatype="string" value="ManilaToday.dll"/>

<parm name="Order" datatype="integer" value="0"/>

<parm name="Selectability" datatype="integer" value="2"/>

<parm name="Type" datatype="integer" value="4"/>

<parm name="Enabled" datatype="integer" value="1"/>

</characteristic>

</characteristic>

</wap-provisioningdoc>

like I said I don't like provxml, as it is the most critical file to get parsed. if you there one thing out of place, the whole file gets thrown out. Try again with a .rgu

you should have a .rgu in your sense folder already right? (if not then there is something REALLY wrong with your oem package).

just add those lines (not the xml version, the first ones I posted) to the end of your .rgu file

remember to add an extra line or BuildOS will complain.

Guest xlightwaverx
Posted (edited)

Ok, each Sense Tab had its own registry entry named app.reg. I ended up deleting each one since it made buildos fail.

The registry entries are back, but I am flashing as I type with just Manila Core and Manila Home, with the registry entries converted to XML.

If that fails, I'll try the DSM name to .RGU name and make them regular RGU files.

If that fails, I'm throwing your ROM back on :(

X

Edit: It didn't work. Trying with RGU format.

like I said I don't like provxml, as it is the most critical file to get parsed. if you there one thing out of place, the whole file gets thrown out. Try again with a .rgu

you should have a .rgu in your sense folder already right? (if not then there is something REALLY wrong with your oem package).

just add those lines (not the xml version, the first ones I posted) to the end of your .rgu file

remember to add an extra line or BuildOS will complain.

Edited by xlightwaverx
Guest amdzero
Posted
Ok, each Sense Tab had its own registry entry named app.reg. I ended up deleting each one since it made buildos fail.

The registry entries are back, but I am flashing as I type with just Manila Core and Manila Home, with the registry entries converted to XML.

If that fails, I'll try the DSM name to .RGU name and make them regular RGU files.

If that fails, I'm throwing your ROM back on :(

X

Edit: It didn't work. Trying with RGU format.

whoa, whoa, whoa....

app.reg leads me to believe that you are trying to use an EXT package instead of an OEM package.

EXT packages are only for those who use a visual kitchen like erviskitchen (spelling).

you either need to find an OEM package for the sense you are trying to cook, or convert the EXT to OEM by hand.

by hand is difficult and often leads to errors...

just rename the app.reg, to a guid (generated by buildos) with .rgu extention.

do this for each folder.

there can be no sub-directories in you oem package, except ones that will be recommoded. So if you have a "files" directory in your oem package, pull them back to the root your root oem package folder.

OEM\custom_sense_package\files\23829_manila

needs to be moved to

OEM\custom_sense_package\23829_manila

also you can rename your app.dat, to initflashfiles.txt as this describes where the files will be placed during the cook.

let me know if I'm way off on my assumption here.

Guest xlightwaverx
Posted

Ok, the .Rgu method did prevail over XML, but Sense still doesn't load. It shows up on items on Today, but when you check it it fails to load it. It maybe because I only have Core and Home installed. Going to install HTC Framework and give it a try.

X

Ok, each Sense Tab had its own registry entry named app.reg. I ended up deleting each one since it made buildos fail.

The registry entries are back, but I am flashing as I type with just Manila Core and Manila Home, with the registry entries converted to XML.

If that fails, I'll try the DSM name to .RGU name and make them regular RGU files.

If that fails, I'm throwing your ROM back on :(

X

Edit: It didn't work. Trying with RGU format.

Guest Ninja4Hire
Posted (edited)

ok I did kinda skip over a lot of what you guys were saying, but here me out anywho....

If sense does not start on first boot, what does? Did you remove any starting today items from your OEMApps rgu?

for instance

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"Windows Default"]

"Enabled"=dword:1

Also you should have all your sense app.reg entries in one rgu file. you can basically just keep all your sense files in one folder including that rgu.

Edited by Ninja4Hire
Guest xlightwaverx
Posted (edited)

Basically, the getting started application starts on first boot, then you have the background image from the Windows Black theme (looks like puzzle piece) and when you close the getting started app out you see "Tap here to launch HTC Sense." You tap it, it blinks for a bit (trying to load) and then stops. Is it because I dont have all the manila tabs installed?

I'd like to try it again, but I don't have time this morning.

Edit: Tried installing all the Manila Cabs, Home, Mail, Message, Stock, blah blah. Still same results except the phone bogs right down to unresponsiveness. HTC Sense is NOT checked on startup but is in the Today Items list. Once selected, it doesn't freeze, but just is hard to operate. Home screen (puzzle bitmap) will not refresh or come back, gets stuck on samsung main menu a lot. Seems to be in there, but something obviously isn't right. I have to head to work. What am I missing to make HTC Sense load by itsself? And if it isn't loading what files am I missing.

Running - Complete Stock (just to see if it will take)

Sense 2016, in separate packages.

HTC Framework.

OpenGL.

Also tried running SDKCerts.cab and rebooting in case it was some sort of security deal. To no avail. I'm going to check online via mobile through out the day see what ideas it could be. Thanks guys.

X

ok I did kinda skip over a lot of what you guys were saying, but here me out anywho....

If sense does not start on first boot, what does? Did you remove any starting today items from your OEMApps rgu?

for instance

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\"Windows Default"]

"Enabled"=dword:1

Also you should have all your sense app.reg entries in one rgu file. you can basically just keep all your sense files in one folder including that rgu.

Edited by xlightwaverx
Guest amdzero
Posted
Basically, the getting started application starts on first boot, then you have the background image from the Windows Black theme (looks like puzzle piece) and when you close the getting started app out you see "Tap here to launch HTC Sense." You tap it, it blinks for a bit (trying to load) and then stops. Is it because I dont have all the manila tabs installed?

I'd like to try it again, but I don't have time this morning.

Edit: Tried installing all the Manila Cabs, Home, Mail, Message, Stock, blah blah. Still same results except the phone bogs right down to unresponsiveness. HTC Sense is NOT checked on startup but is in the Today Items list. Once selected, it doesn't freeze, but just is hard to operate. Home screen (puzzle bitmap) will not refresh or come back, gets stuck on samsung main menu a lot. Seems to be in there, but something obviously isn't right. I have to head to work. What am I missing to make HTC Sense load by itsself? And if it isn't loading what files am I missing.

Running - Complete Stock (just to see if it will take)

Sense 2016, in separate packages.

HTC Framework.

OpenGL.

Also tried running SDKCerts.cab and rebooting in case it was some sort of security deal. To no avail. I'm going to check online via mobile through out the day see what ideas it could be. Thanks guys.

X

if you do ever end up getting this to work please share. As I've tried cooking 2012 in ever since we got 2015 working. I get the same problems you describe, launching sense flashes a few times and then stops loading. I've asked wozzer, and he said it could be the starticonloader isn't from the version I'm using. I changed from 1922 to 2012 to match the 2012 I was trying to cook and it didn't work. He also suggested that my tabs were not setup correctly, looking at 26948339_manila with notepad++ reveals what tabs are loaded when HTC launches. I looked at it and made sure all is well, even removed all but HOME tab and it didn't work.

I keep giving up on this 2012 cooked sense rom, but every now and then I go back to try and figure it out. Right now its way on the back burner as I've other projects.

he also suggested

You can try running B_L_Group_FixStartManila_2.5.cab from http://forum.xda-developers.com/showthread.php?t=670116 first (before editing the 26948339_manilla file).
Guest xlightwaverx
Posted

Browsing the registry files I was renaming to rgu's i seen a lot of calls to some weird htc dll files. I'll have to got thru the htc packages and see if i can find them and compile them in. but i wont be able to do that for another 4 hours :( i think it tries to start and manilla is calling other dll's it needs and it's not getting its fix so to say.

that would be my guess for now.

i'll mess with it tonight and post the results in here.

X da light waver X

if you do ever end up getting this to work please share. As I've tried cooking 2012 in ever since we got 2015 working. I get the same problems you describe, launching sense flashes a few times and then stops loading. I've asked wozzer, and he said it could be the starticonloader isn't from the version I'm using. I changed from 1922 to 2012 to match the 2012 I was trying to cook and it didn't work. He also suggested that my tabs were not setup correctly, looking at 26948339_manila with notepad++ reveals what tabs are loaded when HTC launches. I looked at it and made sure all is well, even removed all but HOME tab and it didn't work.

I keep giving up on this 2012 cooked sense rom, but every now and then I go back to try and figure it out. Right now its way on the back burner as I've other projects.

he also suggested

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.