Root [MetroPCS] [ROM] [DEV] [WIP] AOSP Rom Build

[codingninja62001]

OK I'm fine with that

 

[codingninja62001]

what i have done so far today


https://github.com/Dm47021/android_device_lge_f6mt/commits/cm-11.0

in your BoardConfig i saw you changed the qcom-adreno-305 line to the adreno 200 im thought it was a 305

 

[codingninja62001]

Have any of you guys gotten this error I cant find any info

  running:  imgdiff /tmp/tmp_cPgij /tmp/tmp8uXEmJ /tmp/tmp66_Ngw
Traceback (most recent call last):
  File "./build/tools/releasetools/ota_from_target_files", line 1131, in <module>
    main(sys.argv[1:])
  File "./build/tools/releasetools/ota_from_target_files", line 1099, in main
    WriteFullOTAPackage(input_zip, output_zip)
  File "./build/tools/releasetools/ota_from_target_files", line 543, in WriteFullOTAPackage
    MakeRecoveryPatch(OPTIONS.input_tmp, output_zip, recovery_img, boot_img)
  File "./build/tools/releasetools/ota_from_target_files", line 409, in MakeRecoveryPatch
    boot_type, boot_device = common.GetTypeAndDevice("/boot", OPTIONS.info_dict)
TypeError: 'NoneType' object is not iterable
make: *** [/home/ryan/android/system/out/target/product/f6mt/f6-ota-e72e109525.zip] Error 1
ryan@ryan-Desktop:~/android/system$

EDIT: fixed idk how

 

[Dm47021]

in your BoardConfig i saw you changed the qcom-adreno-305 line to the adreno 200 im thought it was a 305

i double checked it with logcat last night, W/Adreno200-ES20( 546): <process_gl_state_enables:463>:

Theres the answer lol

 

[codingninja62001]

i double checked it with logcat last night, W/Adreno200-ES20( 546): <process_gl_state_enables:463>:

Theres the answer lol

Huh that's weird gsm arena says its a 305 but I'm not argueing with logcat
LG Optimus F6 - Full phone specifications

 

[Dm47021]

It.could be a 305 idk lol

 

[jokerpks]

It.could be a 305 idk lol

I'm certain it is 305. The benchmark app Antutu gives all the specs you should check it out.

 

[Trevor Philips]

I'm certain it is 305. The benchmark app Antutu gives all the specs you should check it out.

+1 CPU-Z says 305 as well

 

[codingninja62001]

Hey does anybody know how to fix that error I posted above and dm47021 why do you always post lol

 

[Dm47021]

So lets assume it is 305 then.
And the problem is in releasetools. I.cant tell u right off.

 

[Dm47021]

Everything says 305 except that logcat

 

[JR44]

Yep CPU-Z says 305. Go with the 305 maybe the logcat isn't detecting it right.

 

[Trevor Philips]

Or maybe we have all been fooled lol

 

[Dm47021]

okay guys, done a TON to the tree the last day or 2.
just fixing some small errors now

https://github.com/Dm47021/android_device_lge_f6mt/commits/cm-11.0

 

[codingninja62001]

okay guys, done a TON to the tree the last day or 2.
just fixing some small errors now

https://github.com/Dm47021/android_device_lge_f6mt/commits/cm-11.0

Hey since i have 2 diffrent source dirs both cm11 im going to fork your repo to the other one and try to build that it might help that i have a good processor (the FX-8350) and a bit of ram

 

[codingninja62001]

haha i hit a error and look what its says

bootable/recovery/su/../../../external/koush/Superuser/Superuser/jni/su/su.c: In function 'fork_zero_*****':

And no i didnt add that
EDIT: android fourms bleeped it out it was xxxx where the ***** are

 

[Dm47021]

That could be tree idk. Still a wip

 

[codingninja62001]

Oh that wasn't the actual error I had fixed that shortly after I posted it was just a line that it spit out

 

[chevanlol360]

Yep CPU-Z says 305. Go with the 305 maybe the logcat isn't detecting it right.

wtf is the bull**** lol, LG gives the f6 and f3 adreno 305 and gives the f7 225? lol excuse me for lurking. Btw cant u check via /system/lib/egl?
Glad to see you on the f6 dm4721, you folks are in good hands

 

[Trevor Philips]

wtf is the bull**** lol, LG gives the f6 and f3 adreno 305 and gives the f7 225? lol excuse me for lurking. Btw cant u check via /system/lib/egl?
Glad to see you on the f6 dm4721, you folks are in good hands

egl.cfg says adreno200 lol

 

[JR44]

Yeah looks like we have been fooled the entire time

 

[jokerpks]

Yeah looks like we have been fooled the entire time

I believe it was a mistake on behalf of LG. They probably made a mistake in the there but the actual chip is Andreno 305. Andreno 200 would never give us high benchmark score "graphic wise". And not to mention play games like GTA San Andreas lag free. There is no way we have Andreno 200. That GPU is mostly found on Gingerbread single core devices and it just would not be able to handle running Jellybean and on top of that play high demanding games. Not to mention our limited 804 MB of RAM which thanks to our LG Skin is always running low. And our CPU is not really that good. I had a device 2 years ago that has a better CPU than what we have.

Now since all the apps identify this device as having Andreno 305. There must be a other way which ultimately tells them that this device has that specific chip.

 

[codingninja62001]

Well since we have a few devs working on this we might be able to try a build for both GPUs but I think we are all building for the 305

 

[jokerpks]

Well since we have a few devs working on this we might be able to try a build for both GPUs but I think we are all building for the 305

I agree it is Andreno 305. But it would be a waste of time and resources to develop for the wrong GPU.

 

[Dm47021]

Lol whats up man ? Yeah kinda got tired of the og warp