PEACE...it was suggested to me to bump this question on here, for further understanding...
i am GREATLY interested in knowing jus how these devices do their "magic"..my question(s) are:
1)i found that .netCF are pre-coded solutions that make the use of the windows mobile device for easier, when peepl customize their ROM, are they added their own written code to these "pre-coded" solutions??? OR..are they completely customizing the .netCF themselves????(hence the word custom ROM)
2)is "code" a sequence of characters(random or consequential) or are they actual command prompts(C:blah blah, stuff) or sumthin totally different?? for example, in morse code, ...---... is code for SOS..what does the actual "code" look like...to tell the phone to lock da touchscreen when the red phone key is pressed, for example??? NOW..i do know that tem[plates are used for customizing ROM, is .netCF the template?? or sumthing else????
3)what role does xml play?? i googled to find out that its used to deploy web applications, but what exactly is its responsibility as whole, pertaining to a ROM
THANK you sincerely for any info, as it would be used in building a stronger understanding on the PPC itself, for myself and others
ok, mayb i showed my inexperience with that last question, now, when a ROM is customized, what exactly is happening?? is code being added to existing code?? or is enitrely whole new code written in place of the "stock" or original ROM? pleez any info that gets me in the right direction is appreciated...again, TIA
Related
im trying to compare these two dll files but i dont reall know how to
I use this app.
http://www.ultraedit.com/index.php?name=Content&pid=34
I also recommend the free (!) WinDiff, on which I've elaborated in depth at http://discussion.brighthand.com/showthread.php?t=215073
hmm i like the ultraedit but it makes the dlls look all wierd. maybe its supposed to be like that.
my problem is that the dll bta2dp.dll from tornado makes the a2dp work. and the bta2dp.dll from treo 750v does allow it to work.
i feel this file is necessary but i dont know the differances
I presume that's a typo because as I read it, both dll's allow your application to work?
I don't understand the problem, if you have have one that works then isn't that the solution? I don't get what you're trying to achieve. DLL's are composed of functions which are dynamically linked to at runtime from the application code. If the parameters passed from the application to the function in the DLL differ from one version to another, or the return information is different then that's the reason why one works and the other doesn't.
Unless you have the programming skill to debug the procedure as it is entered and subsequently change it then there's nothing that you're going to be able to do other than compare version numbers of the files but since you have already found one that works, what's the issue?
David.
(Now I've noticed you try to compare binary files - windiff is only usable for comparing textual ones. Sorry.)
not sure if any body thought of this what if chefs let users to sign their names addresses and finger print scan in the rom
1st will be thief deterent
2nd good hearted will return it if found
3rda phone will be a personal thing,chefs can leave their name somewhere for the smell and taste fo thier cooking
I'd think Chefs should also put a file in the \windows directory called release_notes with their ROM name and a forum link to their ROM thread.
Can't say how many times I've forgotten who's I've got flashed at any given time.
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
GSLEON3 said:
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
Click to expand...
Click to collapse
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
actually, for anti-theft, I was thinking of a kit...
1) modified SPL; requires non-standard password and a signed NBH using your own custom certificate
2) OS is locked down with a trusted certificate of your own in the store so SSPL won't run at all... unless you sign it with your certificate
3) program that checks the SIMcard IMSI; if it changes then it sends an SMS to another number.
now... there are a few practical issues with 2) because it makes installing new apps a pain in the arse since they all need to be signed, so maybe a way of buggering up SSPL would be better.
ras said:
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
Click to expand...
Click to collapse
A Chef that makes ROMs used by thousands is not gonna want to customize or personalize each one for every user. That said, with a donation, there are many that might consider it for you. Of course, you can always use a base ROM & the Kitchen to do it yourself. I do this.
Also, you can use provisioning xml's to customize or personalize them on a basic level using UC. Read Sleuth's thread on UC (User Customization).
@ Olipro, I really like the idea's 1 & 3. I have played a bit with CID locking to an imagined CID & with false Model ID's but of course while you then can't flash a ROM that's not customized to match, you could bypass it with SSPL, making it pointless against anyone half competent.
Your solution 1 & 3 would almost have to go hand in hand, having the password & a way to keep SSPL from jumping the password measures. Something like this, in conjunction with WIMP & UC in ROM, would be a great tool for security. Very Interesting indeed.
I am absolutely new to ROM cooking stuff, I searched the Q & A section but did not find any thread related to the topics I was interested to know:
1. I want to incorporate certain registry tweaks in my ROM, which is somehow getting over written (to be exact I want to turn off all plugins except Home Screen plus plus clock ui and quick launcher). I have exported the registry settings and tried to incorporate in the ROM, but somehow they are getting over written. I want to know is there any way I can make a particular package (in this case my tweaks) get compiled into the ROM last, so that whatever I define there don't get over written.
2. I have found some great freeware like the finger friendly keyboard in this forum, when I try to integrate them into my ROM using Package Creator 5.4, it gives error saying duplicate files. however upon viewing the cab, I saw that the file names may be same, but they are placed in different folders , what is the way to do it.
Can some one help me out?
BTW I do not use any kitchen and I am talking about building for my Gene.
Thanks for the help.
No one wants to share his/her knowledge? Wow
I know there are a lot of thread about Android but I would like to have some explanations to understand the whole pictures.
In fact, every times I read a post about android, it's more an ad for a ROM than a real explanation ... what I would to understand is really what's going on. A more High level understanding.
As per my understanding, Android is a graphical layer over Linux. So first I would like to understand how Linux is running on our Polaris
I know there are 3 files:
zImage which is the Kernel itself (and I think it's developped and maintained by DZO)
initrd which is the initial ram disk (like a standard Linux system)
NBH ... And I don't know what is the goal of the NBH ?
This makes me wonder 2 things
Why do we have different panel type ?
What is updated in this NBH every time DZO update it ?
Anyway, over that if I've correctly understand we have Android.
Ok but what I don't understand is the different method.
RootFS
NoMoreRootFS
SQSH
I've to admit I didn't investigate much in this.
I don't know what is RootFS or SQSH. If anyone can explain me that would be highly appreciated.
But I've tried the NoMoreRootFS method. I think it's the more recent and advanced method but not sure at all about that.
Anyway, I've understood that we start Linux and if we press "Voume Up" during the boot sequence it launches the application which is either in androidinstall.tgz or androidupdate.tgz (depending on the option "install" or "update" we select in the menu which appears after pressing "volume up").
Well, that's a beginning but over all of that I'v discovered that there are more than 1 version of Android.
1.6 : Donut
2.1 : Eclair
What are the differences between these versions ? Are there any other version ? I've heard of an "OpenEclair" version but don't what it is.
I think that's it for the moment. I hope that some people will be able to help me. Thanks a lot for any suoport you can provide.
the warm´s donut is the fastest...but only the hero sense builds have the "cool" style and EzInput 2 with german lang....but the hero sense builds are very slow...
Thank you Alexander but in fact my post was not related to any roms particulary.
I just would like to understand how it is working from a high level point of view.
There are lot of post to explain how to flash, what to flash but I dind't find anything on how this is working ?
How all these pieces are related with each others ?
Does anyone have links or help to provide with, please ?
P.S. : Yes it seems that Warm donut is an excellent ROM.
Hey
Aplologies if this is in the wrong place! Please move if necessary.
So a while ago I tried Untermenschs Resource Mapper.
It worked ok but it would sometimes miss ID's and sometimes would find ID's incorrectly where the same name existed for say a string and an id.
I was porting lockscreens through SGS2 firmwares, had excel 2003 installed and a bit of VBA knowledge so thought I'd give it a go myself.
It works on the same principal. Mod your framework-res.apk with the images, strings,ids,layouts etc etc. Compile and get your new public.xml.
I used this on files I had ported code across into from android.policy.jar and framework.jar.
When prompted, give the tool your old roms public.xml and the new one. Show it where the files are that you have ported the code across into and it will look up the IDs names and types in the old public and then find the new ID in the new public and change the file accordingley. It comments that line with the type and name for easy identification in the same way untermenschs tool did but includes the type as well.
IT OVERWRITES THE FILES, SO MAKE SURE THEY'RE NOT YOUR ONLY COPY, JUST IN CASE!
Excel 2003 is needed as I only realised afterwards that they removed filesearch from excel 2007 inwards. I will redo that part of the routine.
The code is scrappy and Im certainly no expert when it comes to VBA but this has worked 100% in the last 2 ports we have tried. The 10 lockscreens for SGS2 KL1 and 11 for SGS1 JW1.
Please someone try it and let me know how it goes. Would be nice to see if its working good for others or failing miserably.
If it saves someone as much time as it saved me in the last port it will be worth posting
Link removed for updating...
Any chances of getting the link soon ?