Hi, many devs in thier stock based ROMs include split window for all apps by simply modfying line persist.splitwindow.support_all=false to persist.splitwindow.support_all=true , when I'm trying to do it myself the phone falls into a bootloop, anybody knows what may cause it?
Related
I've been reading the forum, and based on the information and the tools there I have been able to modify my extended ROM, which is great. Now of course I'd like to modify the main ROM as well, but despite the many hours I've spent searching the forum, I can't find the necessary information to do it. There's always something essential missing, something which probably is obvious to a programmer, but not to a normal user. As I've been able to modify the extended ROM, I guess I should be able to modify the main ROM too. Who can point me in the right direction?
from what i understand it's not even 100% possible with xda1 since people cant seem to make the extracted files back to a nbf file
and there are no tools that i know of that even extract the main rom from a xda2
As I understand it, when you upgrade the operating system, you're actually modifying the ROM. Some people here like to call it to "flash", I think, and there are a lot of messages about it in here. I just haven't found the information necessary to do it. I want to modify the ROM on my XDAII.
no the operating system is the rom which is in a eeprom in the device
when you flash the rom you replace the operating system with the new one
when you say modifying it mean more in the way of exchanging different files inside the rom
but if you just mean flashing the rom with a newer then here is a guide
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
What does EEP stand for? How many ROMs are there?
I've seen a ROM created here for the XDAI, containing more programs than what the devices normally come with. I would like to have a ROM on my XDAII containing the programs I use, so that I don't need to reinstall them every time the device is hard reset. Isn't this possible?
What does EEP stand for?
Click to expand...
Click to collapse
huh what does EEP have to do with this ?
suppose it could stand for
Executive Excellence Publishing
or
European Environmental Press
how many roms there are i think there are 1.5 1.6 1.66 and 1.72
about extra programs then they are not! in the rom they are in the extended rom any CAB file you copy to the extented will install after automatic after a hardreset
you should take a look at the romkitchens ( specifically for xda1, but can be made for xda2 as well ).
and mkrom, and the other romtools
EEPROM stands for "electrically erasable programmable read only memory".
this is sort of the predecessor of flash memory.
"electrically erasable programmable read only memory" sounds like a contradiction, but thanks for that, it makes more sense than EEPROM.
What about all of us users who don't have a Unix machine? I suppose we're stuck with the original ROM then, and have to install our programs over and over again for every hard reset. Of course you can put a few of them in the extended ROM, but it becomes full too quickly and you're left with installing the rest of them manually.
well you can upgrade to a newer rom as they come out
like i have 1.66 but if i wanted 1.72 i could upgrade
about contradiction heh yeah suppose so but then if it was 100% always READ ONLY then it would be random was what in it as how the transistors randomly set when it was produced
A newer ROM wouldn't contain the programs I want.
no :/ but it could contain bug fixes for ms and radiostack and such
i suspect that extented rom was made so it would be easier for the phonecompanys' and other 3th party resellers to get programs preinstalled fast without having to mess around too much in the rom
this is at the cost of memory though
but then some programs dident like to be in the rom i believe here i mean if setting files were places in the rom aswell and the program could not write to the setting file
mkrom also works on cygwin under windows.
( now I also wrote this in the wiki page )
Isn't that just for XDA I?
it works for windows ce in general.
that doesn't mean that there is no work involved in getting it to work, but it is possible to make it work for the xda2. I use it to build custom roms for the devices we sell, that is why I wrote it in the first place.
What's cygwin?
How much space is there in the ROM to add extra programs? In the ROM that this forum developed for XDA I they added quite many programs from what I could see.
http://www.google.dk/search?hl=da&ie=UTF-8&q=cygwin&btnG=Google-søgning
Thanks for that, Rudegar.
To Itsme: I don't mind the work, but it looks like its written for programmers and that if you're not a fairly skilled programmer, you wouldn't be able to do it.
Wondering if anyone would be so kind as to give me a quick guide how-to make an AOSP build for the Rhodium?
Can someone give me abit pointer, like a guide or somethng?
You mean something like this? http://source.android.com/index.html
I think the best way to do it would be to use squashfs-tools to unsquash system.sqsh, and simply make the edits you want to. Then you would want to recompress it into a new system.sqsh (using version 3 of squashfs-tools, NOT version 4).
Alternatively, you might be able install everything you want on a vanilla build of Android, and simply distribute all those files (data.img and system.sqsh) when you've made all the customizations you want. I'd imagine this second method would be more likely to lead to problems when being run on other models of the device, or on other service providers.
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Hi, I'm from Greenland. I don't know how to tweak or customize android, and don't want to brick my phone.
I've downloaded and installed some custom roms and kernels.
I've seen Huawei with Greenlandic Language, is it also possible in LG or other devices?
Some tweaks to enable it?
I've tried some apps, but they only change the date names like Ataasinngorneq for Monday and Septemberi, but I'm looking for whole system languages.
Hi
I am a big fan of MultiRom and DualBoot and any other "multibooting" solutions
So I decided to take a look at DualBoot since it is more than less easy solution…
So I added S9/9+ (Exynos) properties to devices.json, but there are other known bug with DualBoot, so I fixed it by patching the kernel…
But then I get other TouchWizard Related Bug ?, after bootingup the rom I can't unlock the device, after entering the code System UI is ForceClosing and need to enter code other time ?, so it's impossible to unlock the device ?
If somebody can help to fix this problem we will get working DualBoot Patcher
Thanks
Can someone please help?
I tried to use the modded .json file from VagKout but on the one hand it crashes randomely and always on the ´Roms´ page an on the other there is no S9 shown in the list of devices?!
Thanks...
Just got my s9 and this was the first thing I looked for, I miss this I used to use on my s8+ all the time. Any update to this?