so i was investigating the Vengeance rom (which is nearly exactly like the cynogenmod) nd decided to compare files from thiaiZo3d and Vengeance; i realised if you look under \system\etc\permissions, the stock roms have:
-com.lge.real3d.hrz.xml
-com.lge.real3d.xml
-com.lge.sound3D.xml
-lge.hardware.real3d.xml
also HRZ.apk in system\app
whereas the cynogen/veneagence rom dont, could this solve the 3d issue :O,
not really a developer so I wont have a clue lol, could someone maybe investigate
No need to investigate. Real3D is the LG's proprietary framework, so no Real3D for CM... Unless LG opens it or somebody ports it.
Related
I'm on Trip's Gingerbread Miui but esp. with Videorecording the SE is much better then the Miui. Could please anyone extract it from the official ROM and offer a download?
drdownload said:
I'm on Trip's Gingerbread Miui but esp. with Videorecording the SE is much better then the Miui. Could please anyone extract it from the official ROM and offer a download?
Click to expand...
Click to collapse
SE Camera is the best camera application at the moment when it comes to X10,
but it will not work on any other ROM, it depends on SE framework, libs and drivers.
So it's a no-go, unfortunately.
not the answer I hoped for maybe when the first miui rom comes around that is build on the SE-ROM and has not just ripped the camera drivers from it, maybe it will work
drdownload said:
not the answer I hoped for maybe when the first miui rom comes around that is build on the SE-ROM and has not just ripped the camera drivers from it, maybe it will work
Click to expand...
Click to collapse
Actually the camera drivers for GB are not yet available,
since SE hasn't released the sources for the new firmware,
so MiUI Camera is not using the official drivers at the moment.
We'll see how it goes when we get the actual drivers!
As far as MiUI ROM based on stock ROM... oh well...
There goes one more answer you will not like:
It's not going to happen.
MiUI is closed-source, there's no way to really mod it to the core,
let alone mix it with another firmware.
Sorry!
from rdannar's porting miui guide I assumed that Miui can be ported while preserving most of the original ROM files, however I never looked deeper into that. although I earn my money as Software Dev I never had time to cook something on my own.
drdownload said:
from rdannar's porting miui guide I assumed that Miui can be ported while preserving most of the original ROM files, however I never looked deeper into that. although I earn my money as Software Dev I never had time to cook something on my own.
Click to expand...
Click to collapse
You can -actually must- preserve some libs and other specific to the phone files
in order to make MiUI functional (that's exactly what a port is)
but modifying MiUI to its core in order to port its features to another firmware
is not possible because the source is not available publicly.
What I miss when I'm on MiUI is the SE Camera
and what I miss when I am on stock is MiUI statusbar toggles and the
wonderful theming opportunities! I guess it's one way or another!
I did had some hope because the SE Panorama apps also was patched to work on most ROMs,
I'm at my wits end.. I've downloaded and compiled GB 2.3.5 to find no auto-rotate on my 9020A NS.. So I downloaded 2.3.4 and compiled that, STILL no auto rotate..
I downloaded and extracted into the code the 4 binaries from google but the accelerometer isnt among them.
Is this a problem for the AOSP builds of 2.3.4 and 2.3.5?
Am I nuts?
Is there a patch?
Any info would be awesome.
Take libakm.so from stock rom and put it in your build.
Worked perfectly! Thanks a bunch Pete!
As this thread floats into oblivion, if there is any interest in a unmodified completely 100% AOSP compile of 2.3.5 for the Nexus S, (I couldnt find one that was 100% unmodified, perhaps I didnt look hard enough) everyone let me know I'll produce a cwm zip of my build. I realize AOSP is easy for the semi initiated, but some people might not have the time/desire/knowhow,etc..
My goal of starting this is to port over some aspects of Honeycomb I like, including the launcher, lockscreen and what not by modifying existing functioning gb code..
Hopefully I'll finally make my first dev ROM in a couple of weeks.
Thanks again to Pete for the accelerometer fix.
hi,
as the title suggests, i would like to make a custom rom for this device... either modify the current 2.1 rom and make it app2sd compatible or make a 2.2 or higher rom that natively supports it...
i just need some info... firstly, which would be the easier thing to do?
if modifying the stock rom, what would i need to do 2 make it app2sd compatible?
if making a custom rom, how would i go about doing that?
i would imagine its possibly like getting a windows os and adding drivers for a specific machine before instalation... except in this case i think its a custom build.prop right? any help is much aprieciated...
oh and a final thought, if i make a mirror of the stock rom which bits can ibuse from it 2 aid me in the making of a new rom? id ideally like a 2.3.7 cyanogenmod7 rom just coz my current device (hd2) has a cyanogenmod7 rom and it works flawlessly... i do have a few hd2 android builds, can i disect these and modify them from what i have on the cyberjam?
basically i have a lot of apps and would like 2 have hardly any limitation on how many i can have as opposed to having 4-5 n gettin the memory getting full warning...
again, thanks in advance...
better still, add a forum for this device and have a big long list of compatible roms lol...
and finally, (another p.s)
there is a device which is very simmilar called a bsense 383.
now this does have a 2.2 rom available, only difference i can see is the cpu in the bsense is dual core aparently... the other hardware appears to be the same (haven't seen a list of every part inside both but the few parts i have seen are the same minus the aforementioned cpu)
so i look forward to your reply and hope that this is possible and plausable...
thanks, luke
31 views and noone can help me? come on xda community... surely someone can help me out...
Just read up on dsixda kitchen and once you get it installed in the right environment you can run pretty much any Rom through it and add that feature along with many other things. As long as you don't redistribute someone else's work, its ok.
Hi.
Might be retarded to ask this, but as the title says: are all the roms in the dev section (the ones' which are GB roms, of course) uses LG's drivers and 2.3GB?
Let me explain myself (if needed):
Recently I have found out that one obstacle in building the ICS ROMs is not having the LG drivers in order to "sit" the ROM on the hardware.
Ok. Great.
Now this makes me ask, what about the GB Roms? Are they all using the official LG drivers? Are they "based" on these driver?
I am assuming that a ROM which is basing itself on official LG drivers will be the most reliable, least likely to force-close, and so on.
Thanks!
I think so, and I'm pretty sure they are; even if it's the the degree that the original drivers are modified to some degree, such as a custom kernel. I wouldn't imagine that the drivers, except maybe for CM9, have been rewritten from the ground up.
This is my educated opinion and I may still be wrong.
So, Since the Cyanogenmod source is so big (I heard that it has 19GB), people like us who have gay as slow internet have no chance of even trying to cook a ROM for our unsupported devices.
Since I can't download the whole CM source and I see awesome ROM's out there, I Ported one ROM called Cyanfox (which was made for Samsung S2 i9100) to Samsung Infuse 4G using Beanstalk ROM as a base. I followed a guide which asks me to replace some folders and edit some files. It was walking fine. Then came an update to both the ROMs, Thinking that cince it is a update, it will have the updated apps and source, I tried porting them again but this time Beanstalk updated ROM as a base cause a bootloop while the Beanstalk old ROM works fine as a Base ROM.
Now what I don't get is, why is Beanstalk new ROM not working as a base? (Since the new Beanstalk ROM will have updated Source, I want to use that ROM as my base.)
And the second question is, what files does actually matter when you are Porting or cooking an Android ROM? (I mean like windows works on all kind of PC's all it needs is the drivers right? The drivers actually matter on windows)
And the 3rd question is can I update the source files somehow without downloading the whole 19GB CM source and if possible how?
The 4rth is, I heard from somewhere that boot.img is the file which separates the phones? Then why can't we just port ROM's by replacing boot.img since these two phone's are from the same vendor and it has likely specs. (Which is not possible I think)
I am really really a newbie to this thingies, I just wanted to clear out these things. Sorry for my noobness.
Thanks!