[STABLE1] [UNOFFICIAL] [ROM] OMGB 1.2.3 (Android 2.3.7 - .35 kernel)

[Bytecode]

Using AOSP framework config worked!

 

[HawkeyeWPR]

what about God Mode?

 

[Jrhodes85]

I just read on wiki pages what omfgb really is and the God mode function.... Is this rom going to have everything included just like the other phones that omfgb is compatible with

Sent from my LG-P500 using xda premium

 

[cupliz]

I just read on wiki pages what omfgb really is and the God mode function.... Is this rom going to have everything included just like the other phones that omfgb is compatible with

Sent from my LG-P500 using xda premium

So you mean OMFGB = AOSP + GOD MODE.
Without any tweaks and optimized code??

@TS please make it clear, I need know what exactly I need to use On my phone. Sorry for my stupid ask.

Sent from my LG-P500

 

[Jrhodes85]

Yes, I'm pretty sure that omfgb is a modified version of AOSP + god mode, it's the first time I've heard of it but I wonder how omfgb differs from lupohirp's AOSP rom.. Now as far as tweaks, ciaox usually includes tweaks in his roms, take openoptimus for example

Sent from my LG-P500 using xda premium

 

[Bytecode]

Updated first post,more clear now.

Still everything FCs. Posted some logcat in the first post. Anyone take a look

 

[Bytecode]

Hmm... I probably made a newb mistake: I initialized repo with CM url and not with AOSP,so maybe some AOSP stuffs needed by OMFGB are CM.

Re-syncing with android-2.3.7-r1 manifest.

 

[andy572]

Still everything FCs. Posted some logcat in the first post. Anyone take a look

the logcat says, there are some stuff missing, in renderscript there is a missing drawable, the statusbar is crying about a **** xml file (maybe the statusbar.xml):
its ainfalte error, so it means a component (can be a class, drawable or layout)
cant be found.

 

[Bytecode]

the logcat says, there are some stuff missing, in renderscript there is a missing drawable, the statusbar is crying about a **** xml file (maybe the statusbar.xml):
its ainfalte error, so it means a component (can be a class, drawable or layout)
cant be found.

Thank you anyway sorry for not making progresses here anymore guys,lemme make CAF boot and I'll be back here

 

[Bytecode]

@Andy:

I probably found the cause. Last time I build without overlay folder (so without any framework config.xml) because I couldn't declare undeclared stuff in device folder's config.xml. But now I placed stuff in frameworks base the right way,so it's building with new "modules"

Otherwise,if it doesn't boot,I'll switch to Ubuntu 10.04 (found a old JBQ post: He said that older stuff than ICS can't be build on 11.10).

I'm almost melting my core i7 with all these builds! Currently the only stuff I changed are obviously vendor and device folder,but had to remove also FORTIFY_SOURCE to make it build on Ubuntu 11.10. Also dalvik was missing armv6-vfp stuffs.

 

[Bytecode]

Update: Sources available at: www.github.com/BytecodeX. Still FCs everywhere.

 

[popdog123]

You're missing resources... check if your source has all the the necessary mdpi resources. I don't see signs of missing classes though...

 

[Bytecode]

You're missing resources... check if your source has all the the necessary mdpi resources. I don't see signs of missing classes though...

I made a mistake in that old build,I didn't declare some stuffs into OMFGB_thunderg.mk and build without overlay folder but nothing still changes. Also ADB wasn't working for some reason,now it's working

New build log: http://pastebin.com/Y5TBsS5Q
You can find my sources @ github (BytecodeX) if you wanna check.

 

[popdog123]

As i said.. you are missing resources...
After a quick look at your sources framework/packages/SystemUi/res
drawable-mdpi is missing at least one file: ic_music_toggle.png. Copy it from hdpi folder and resize it so it fits the statusbar just fine. Then look for other files. I can't look for them in github but it should be easy if you have the sources downloaded. Just check out the number of files in the hdpi folder and the number of files in mdpi. It should be the same. If it's not then you have a problem.

Do the same for all the other apps that give out missing resources errors in logcat (i see launcher is also in that situation) and that should do the trick.
Also, building with no overlay folder is no big deal and should lead to no force closes. Maybe just unwanted phone behavior, unusable tethering and so on.

 

[Bytecode]

As i said.. you are missing resources...
After a quick look at your sources framework/packages/SystemUi/res
drawable-mdpi is missing at least one file: ic_music_toggle.png. Copy it from hdpi folder and resize it so it fits the statusbar just fine. Then look for other files. I can't look for them in github but it should be easy if you have the sources downloaded. Just check out the number of files in the hdpi folder and the number of files in mdpi. It should be the same. If it's not then you have a problem.

Do the same for all the other apps that give out missing resources errors in logcat (i see launcher is also in that situation) and that should do the trick.
Also, building with no overlay folder is no big deal and should lead to no force closes. Maybe just unwanted phone behavior, unusable tethering and so on.

Your post was really useful. SystemUI is missing 12 objects from MDPI to HDPI. Will check out other stuffs.

EDIT: Android basic stuffs have both mdpi and hdpi resources: OMFGB and others do not. I checked and fixed all package,making a test build with overlay folder,then I'll remove in next build if needed.

 

[Bytecode]

Currently it boots to a working UI - but OMFGB is messed up big way with MDPI devices.

Bugs:

• Launcher 3D Cube app drawer messed up
• When screen is locked,phone gets stuck (probably for non-working MDPI lockscreens)
• Some MDPI images messed up
• MDPI Bootanim is crappy
• Phone doesn't boot anymore after 1st boot

You can find updated sources at https://github.com/BytecodeX to build it yourself. But I keep updating them,so wait for a release


Ok,I'll give you a ETA : 20 dec. Remember it's an Estimated time of arrival,so don't trust it

 

[mDroidd]

Currently it boots to a working UI - but OMFGB is messed up big way with MDPI devices.

Bugs:

• Launcher 3D Cube app drawer messed up
• When screen is locked,phone gets stuck (probably for non-working MDPI lockscreens)
• Some MDPI images messed up
• MDPI Bootanim is crappy
• Phone doesn't boot anymore after 1st boot

You can find updated sources at https://github.com/BytecodeX to build it yourself. But I keep updating them,so wait for a release


Ok,I'll give you a ETA : 20 dec. Remember it's an Estimated time of arrival,so don't trust it

Phone doesnt boot after first boot...

That's really strange!

the MDPI images & bootanim should be easy to fix, right?

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

Your post was really useful. SystemUI is missing 12 objects from MDPI to HDPI. Will check out other stuffs.

EDIT: Android basic stuffs have both mdpi and hdpi resources: OMFGB and others do not. I checked and fixed all package,making a test build with overlay folder,then I'll remove in next build if needed.

Oh, and, btw:

If you would like to resize from HDPI to MDPI, wich percentage??

I made a simple script wich does it automatically on Ubuntu with ImageMagick, but when i resized 80%, everything looked crap...

 

[Bytecode]

Phone doesnt boot after first boot...

That's really strange!

the MDPI images & bootanim should be easy to fix, right?

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------



Oh, and, btw:

If you would like to resize from HDPI to MDPI, wich percentage??

I made a simple script wich does it automatically on Ubuntu with ImageMagick, but when i resized 80%, everything looked crap...

You tell me,what percentage is better?

Actually I hate MDPI OMFGB bootanim. Could you resize HDPI for me? Thank you

BTW,I didn't explain myself good: I have random reboots.

 

[DaXmax]

Actually I hate MDPI OMFGB bootanim.

I got a better one, save spaces too... Just give me a pm or alert, and i will do it for ya...


Sent from my GT-I9000 using Tapatalk

 

[mDroidd]

You tell me,what percentage is better?

Actually I hate MDPI OMFGB bootanim. Could you resize HDPI for me? Thank you

BTW,I didn't explain myself good: I have random reboots.

Lol, okay.
When i resized, i got text out of the box.

You know what, give me your framework and I'll resize 90 80 and 70 percent. After that I'll give you my script

Greets
____________
mDroid - Tapatalk

Phone: LG-P500
ROM: Ciaox' openOptimus
Kernel: franco .35
Theme: HoneySandwich (by me)
Tweaks: Turbocharged and Supercharged!
Wishlist: Galaxy Nexus