yashsingh1/xdaforums huggingface dataset:
[LG Optimus 2x] wulsic:
Well I am still on a gaming marathon :l but after that I will try somethings again.

Lollipop's SElinux could also be set to permissive, disabled I don't know really but recovery should boot even if SElinux is disabled right? Maybe that's also the cause a bit cause I think that djnoxd has selinux enabled and to permissive I guess cause enforcing sucks. Better logging then blocking everything.

But I also saw lollipop builds with Selinux disabled I believe so it's possible :D only enable selinux to flash selinux updater-scripts

So I will try today also to compile recovery and get it working :D the most hardest part for me is the long waiting on the LG logo.

EDIT: [MENTION=3605868]tonyp[/MENTION] I also tried to bring back the tegra2 patch but I had issues with it. Also because some things were deleted and are now different but I will try it later again :good:

Djnoxd had also compiled his slimrom builds with generic as cpu variant so I don't know. Can somebody report back who had compiled maybe first with generic cause I changed that in the device tree which I am using now. Also djnoxd follows us silently, he was also half an hour active with slim 5.0 so he is our nightwalker.
[LG Optimus 2x] TheMysteryouse:
Thats the thing.U can never exactly know if the rom is going to boot or no because Lollipop takes quite a bit of time to get booting but the thing is u dont know if it's in a bootloop or still in boot process.
[LG Optimus 2x] wulsic:
Well that isn't the real problem for me. The real problem that I am having is that it takes long to boot into recovery after flashing it and I am not used to that. I will continue after like an hour again with Lollipop I guess to get the 2.8.3.0 TWRP recovery working and I will also push the changes from that ro.hardware star things to the lollipop device tree and I will also update the patch for the BLOCK_BASED_OTA.

EDIT to save a post: [MENTION=5886593]TheMysteryouse[/MENTION] I am also busy with making a new TWRP 2.8.3.0 Recovery so don't worry about that. It also features new features which also speaks to me like that they have improved their MTP and they also merged some lollipop stuff into it so I will try to get the recovery working and if we get that working then we're a step closer to a booting lollipop cause the recovery I compiled resulted into a black screen bootloop to LG bootlogo and lollipop built that I've flashed from someone here with my custom test also resulted into that.

I don't know or we could get lollipop booting into 3 days but I guess that we'll see that.
[LG Optimus 2x] TheMysteryouse:
It isn't rly a problem but it's tricky.Even if u get everything working and get it flashed u can never know if the phone is booting or is it stuck somewhere without a logcat.I tried to flash the rom on every TWRP version and with CWM but still nothing also the only way is to compile a new one.I think it would be better to compile one too.
[LG Optimus 2x] TheMysteryouse:
If nothing, we can wait for DJNOXD and hope he could help us out if u dont get it.The improvements seem deliciouse hehe :D Good luck my friend.
[LG Optimus 2x] gucky01:
Build is ready! The same effect as in my last build. Flashing fails, but after exchanging the updater-binary with one from an 3.1 build flashing works. Rom boots, after the LG logo the animation starts but here it stucks.

Perhaps tomorrow I will upload a logcat.
[LG Optimus 2x] wulsic:
Hmm interessting that yours comes till animation. Could you share that updater-binary not for all builds but just to see or mine also comes to the animation or not. Which sourcecode are you actually all using and which device tree's may I ask?
[LG Optimus 2x] pijas82:
Sorry offtopic

Tomorrow, will make a year , the first ROM KitKat to our phone. Thanks master. [MENTION=3605868]tonyp[/MENTION]

Sent from my A0001
[LG Optimus 2x] zerocoolriddler:
After a quick look into your ROM from Post #161 i found that in /system/app (EDIT: and in /system/priv-app) every *.apk is moved into a corresponding Subfolder. Is that something new in Lollipop or a packaging Error?

Also the /system Folder contains a "recovery-from-boot.p" File i've never seen in a ROM.
[LG Optimus 2x] MatteoB92:
Is a new feature of Lollipop
[LG Optimus 2x] Hugo-PT:
gucky, may I ask if, when the animation started, he was in loop a long time, or froze in the animation? If it has been looping, how long you waited?

I'm asking this because in my other phone, I9001, which is running the lollipop, the first boot takes almost 40 minutes
[LG Optimus 2x] wulsic:
Yup like Matteo said it's all new. recovery-from-boot.p was actually also included already in cm11

it indeed is.

Guys I also discovered maybe why my recovery failed the whole time. It seems that first the ramdisk is okay but then it removes images also in the res/images folder and some other stuff after

----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...

I will look tomorrow in it, I could ofcourse make a dirty frankenstein recovery but I wanna do it on the right way:good: so that will be my job tomorrow to get the recovery compiled. I will also try tomorrow to recreate the p990 device tree for recovery and see if the same happens. But I will solve that problem tomorrow guaranteed:good:

As far as I know it should go wrong while they're busy with the ramdisk contents because it's first good but then it replaces it with another ramdisk items which I don't get because it was first good, but I will see it tomorrow I guess because it's now 02:52 AM and I am getting tired or somebody must have some nightly advice on this before I will fix it tomorrow.

[MENTION=5642683]Hugo-PT[/MENTION] why does it take 40 minuteson your phone to boot? Is it encrypting Or does the dex just takes a long time because of art?

Also, Merry Christmas Everyone!

Let's give ourselves a working 2.8.3.0 recovery as a preview for a soon booting lollipop :laugh:
[LG Optimus 2x] Hugo-PT:
Yes, is because of art. Only happens on the first boot after flash the rom.

Merry Christmas :)
[LG Optimus 2x] trocopassu:
Thank You, My Friend! To You Too...and Your Family & Friends... Merry Christmas for All!!...
[LG Optimus 2x] Puri2013:
Thank you Merry Christmas Everyone and Optimus 2X:)
[LG Optimus 2x] Genie's:
Merry Christmas, everyone!
[LG Optimus 2x] wulsic:
I just woke up and I had a idea what could be the cause and it was it. The makefile in build/core was causing issues with twrp recovery and it was it :) I am still trying somethings out and then I will flash the twrp recovery.

EDIT:Recovery bootlooped, :( Several attempts but they all bootlooped. I will try also today or I could logcat the problem.
[LG Optimus 2x] lolypop000:
Anybody know who is developer for su660 lollipop rom?

http://www.lollipop-rom.org/mp3-0/lg-optimus-2x-su660-3762.html
[LG Optimus 2x] pijas82:
Its fake my friend

Sent from my A0001
[LG Optimus 2x] Surplus:
For anyone here trying to port lollipop, i recommend checking these two tegra2 devices out. They already have android 5.0 booting and you might be able to cherry-pick necessary tegra2 compatibility commits.

http://xdaforums.com/eee-pad-transformer/development/rom-t2942560

http://xdaforums.com/galaxy-tab-10-1/development/rom-android-5-0-0-lollipop-lrx21m-p4wifi-t2938870
[LG Optimus 2x] mhkim4886:
When p990 develop success, then su660 can use it with small edits.
[LG Optimus 2x] Frecciablu(2):
Happy Christmas to any1 guys! :)

Your hard work is already a great gift :D
[LG Optimus 2x] TheMysteryouse:
Little bit offtopic but Merry Christmas everyone.Hope you guys have a great Christmas with ur family and friends. c: <3
[LG Optimus 2x] wulsic:
Have a merry christmas and also to everyone else :)

I will also look today again in the recovery why it won't boot and why the init file in the ramdisk is so big. If we could all just use the same device repository and source then we could help each other and fix the bugs/issues to make a perfect tree for the 2X cause we all know that humans makes mistakes and so do I.:good:
[LG Optimus 2x] MatteoB92:
Good Christmas my friends, and above all good luck with 'our' project :)
[LG Optimus 2x] pijas82:
M.c. for all, o2x never die

Sent from my A0001
[LG Optimus 2x] gucky01:
Hi guys, I wish you Merry Christmas, that the light of these night will shine brighter and the world will be a better place for those, who need our help.

I think, we are a good example , whatever our colour, religion or country is. we work together and there is peace!

Ok, now the news. I finished a new build with the posted sources. Attention builders! Keep your mind, that the charger is in the boot and recovery folder of our working directory. Some days ago I recognized, that it`s sometimes exchanged with a shortcut. After I copied it in both directories building finished and the rom completes the flashing without changing binary files!!!

The flashing needs about 5 minutes, then it`s ready. After that we see the bootloop, but I think there is a difference to older builds. Please look in my uploaded logcats. I think, there are few errors left, one annoying.

@ Hugo:

I let it booting for 1 hour, but it doesn`t come to an end!

Here the rom and the logcats

https://sourceforge.net/projects/lgoptimus2x/files/P990/CM12/

I have uploaded 3 different extracted boot.img. First from my CM11 rom, second my CM12 and third from a P4 lollipop build. Please compare the files, especially the sbin folder. In my CN12 build you can find a mkfs.f2fs file . Perhaps the file sytem has got a mismatch error.

Sorry forgot something... I deleted the target releasetool entry in boardconfig.mk, so I used the CM12 building-files!!!.
[LG Optimus 2x] wulsic:
I will also remove that prebuilt kernel thing/update the prebuilt kernel because that prebuilt kernel was built with tegra2 bionics and now we have cortex-a9 bionics.

Gucky are you sure that on your build that you are using my latest sourcecode? Because I saw somethings which I even fixed already and the errors still occurred in the log but that wouldn't be possible anymore.

Then I am also talking about the lines:

W/DirectVolume( 117): Deprecated implied prefix pattern detected, please use '/devices/platform/sdhci-tegra.3/mmc_host/mmc0*' instead
W/DirectVolume( 117): Deprecated implied prefix pattern detected, please use '/devices/platform/sdhci-tegra.2/mmc_host/mmc1*' instead

I also noticed this line and I marked the line which says the error in red, Which as far as I know if I am correct means that it got Illegal instructions, So that would probably again NEON related because it can't execute those codes. I don't think that the instructions are illegal but that they are probably for NEON devices. But they always could be illegal so I can't say which one of the 2 is the right thing since I am still learning.

I/DEBUG ( 125): signal 4 (SIGILL), code 1 ([COLOR="Red"]ILL_ILLOPC[/COLOR]), fault addr 0x72b112fa

Here is a link that I've found regarding to the error, it could be possible that it won't even have to do with it, but I think that it's probably also something related to our Nvidia Franky.

http://www.codedojo.com/?p=1509

Does your boardconfig contains generic or cortex-a9? My rom didn't even booted yet because I didn't rebuilded it and I didn't tried to replace it. I will try some dirty files switches to see or the error also occurs to my rom and or if it even wants to boot.

About that f2fs I will look into it to see why that's even included in your sbin folder, maybe it's because of cyanogenmod that they implented support or something like that, Else try to switch to F2FS but I think that if you would do that that it won't even reach the bootanimation just like on djnoxd's slimrom builds.

I didn't really invested much time today with the recovery I was busy with friends :good: but I will check out again regarding to the charger/ramdisk copying why it ignores that and uses their own, maybe we have to update the line and replace something with 1 symbol. I will also try with my rom to see how it goes :) it would be still fancy to see the bootanimation if my rom even boots :silly: Noob Alert detected here :)
[LG Optimus 2x] gucky01:
Very good that you spent time with friends. I with my family:)

I used Tonys sources as explained, my friend. Tomorrow I will include your changes in boardconfig in my next build to try if this combination works too.

my boardconfig contains generic .

If you want, I can upload the device folder.

Following your link and the link inside it should be a neon problem. Did you recognize the "zygote" entry in my logcat after the signal error and the zygote file in my cm12 boot..img. Perhaps this is a trace?.
[LG Optimus 2x] wulsic:
Also very good that you did that ;)

I was also wondering or you were using the sourcecode from TonyP that he merged from my device tree I also had more changes then only in the boardconfig so also look in my device tree :)

github.com/wulsic/android_device_lge_p990

Nahh you don't have to only if you have found something for the charger problem yet :) or if you maybe have things different then me which would be maybe critical for lollipop but I think that I already have the most things. But the good thing is that you got it compiled and you could logcat it without any dirty files so we are close to our destination.

Also about the charger, maybe we should see the makefile related to that when the charger gets symlinked to healthd and or when that happens and or the charger gets ignored for that.

EDIT: Damm I also compared yours and mine updater-binary huge size difference that explained everything actually, also my build didn't came till the bootanimation, it stayed on black screen. The only things that I could think of that caused that was: Using a prebuilt kernel(I don't know or I had used it then), Other Bionics then generic, Some Alien like thing?, Something that I might've removed but the only things that I've removed were android.mk and some patches. Also that long lollipop install time, it probably makes people less flashaholic like a bit it took so damm long.

So Gucky could you also compare your and mine device tree a bit? I still have to figure out why my device stays in black screen and then reboots to LG logo. If I know this then it would also fix my issue I had with TWRP cause there I had the same issue so I assume that it's also kernel related. I probably have cracked the foundation of the android system. EDIT, I see that you are also using the prebuilt image so Let's compare the ramdisks :D, It also seems that your binary files were larger then mine. I also experienced the same thing while compiling recovery that it was once big and other time small but I still gotta find the cause again, because I forgot to write it down somewhere xd

Or yeah could you share your device tree :) maybe on github if it's possible else just in a zip :D so I could compare things what I might've changed and what I would maybe think afterwards like why did I do that?

EDIT99999: I realised that I really have nothing to do in my time except for writing long messages. But I am now also downloading omnirom source because I also want to make some personal builds from it for my future device. Do you guys also have maybe some other aftermarket suggestions? I have also chosen omnirom because they have recovery twrp included automatically which just simplifies some stuff and then I could also discover more things, like where the problems are.

Edit4: I also recognized the zygote yes
[LG Optimus 2x] Hugo-PT:
Sad to hear that! :( When I heard that you had reached that stage. I had been hoping that it boots up! Because I had gone through similar experience with my other device. Apps require longer time to be installed because art needs to compile them, is the same reason the rom take longer to boot the first time after flashing it

I leave my thanks to everyone involved in the project lollipop for P990 :good:

Cheers,

Hugo
[LG Optimus 2x] gucky01:
Hi Wulsic, I'm compiling your sources at the moment. Ffmpeg patch doesn't work. There were changes in CM in the last days. Perhaps you can adjust it.

Later I'll upload the differences in our builds in txt file.

See you!
[LG Optimus 2x] wulsic:
Alright thanks, I will update the FFMpeg patch again :l Cyanogenmod is too quick for me.

Alright :good:

I also have found out why your init binary was bigger then mine, because I mentioned in mine boardconfig

# Jemalloc causes a lot of random crash on free()
MALLOC_IMPL := dlmalloc

But there is still a 5kb difference so I wonder why yours is still bigger then mine, could you share the device tree you had so I could compare it?

I wonder or your build will boot with my device tree :good: cause mine went into a bootloop and I wonder why, could it be because of the bionics or because of that dlmalloc because it's a different memory allocator.
[LG Optimus 2x] gucky01:
Here is my device folder:

http://sourceforge.net/projects/lgoptimus2x/files/P990/CM12/p990.rar/download

I decided to make clean with my out folder to avoid side effects. Ffmpeg patched manually. Build should be ready in the morning. I took your device settings but used the generic version.:fingers-crossed:
[LG Optimus 2x] pijas82:
Can flash my friend?, sorry for ask

Sent from my A0001
[LG Optimus 2x] wulsic:
Thankyou I will look into it :) I bought myself after 6 months smartphoneless the LG G2 so I am now playing with roms and flashing :cowboy:. LG is still a boss.

I think that he will try it tomorrow when it's done and if it boots, IF then he will share it.

I will also checkout his and mine device tree to see what he all changed and see why my init binary still had that 5kb less. But I think that the 2X will see lollipop soon since it's just a awesome phone.
[LG Optimus 2x] TheMysteryouse:
The strugge to get it booting is real.If nothing, ask some other devs that have lollipop on their tegra 2 devices like timduru and the s2 but the NEON is the hook on that point.
[LG Optimus 2x] gucky01:
Actually I'm pretty confused. Patching of ffmpeg needs more time, because there were more errors in building.

I set up a new building folder with Wulsic' device but there are many warnings in the beginning, that files in external/ffmpeg/libavcodec/ gonna be replaced or ignored. Did another test witbout the patches, but the same result.:confused:

Can' t remember that these warnings were present in my last builds.

Need help!
[LG Optimus 2x] wulsic:
Odd. Did you manually patched them good? I had no errors back then. I also believe that omnirom doesn't have that. I will make a omni build test later again.
[LG Optimus 2x] gucky01:
Yes. Check omnirom!

I tested a complete new build with Tonys sources and the errors are here, too.

Don't remember if this was a problem in the past.

You know, first

including vendor cm...

trying dependencies...

platform version...

ebtables is disabled...

and then the strange lines, all beginning with: external/ffmpeg/makefile:898:warning:

after then the known

find phone/java...

and dummy...

Please give me advice to these lines!
[LG Optimus 2x] wulsic:
[MENTION=5021221]gucky01[/MENTION] I will also try it when I have acces to my pc again. Are you sure that you applied the ffmpeg patch good?
[LG Optimus 2x] gucky01:
Your patch fails. Manually errors. Just compiling. Post the changes I did soon.

Update: Lets discuss your patch a bit.

1. Config-armv7-a.mak: the neon entrys exist in older cm trees, why to patch?

2. Config.h: Its an automatically generated file, is patching necessary?

3. Android.mk: This file contains the neon/mpegvideo entry, which was included on Dec12.

.
[LG Optimus 2x] wulsic:
It was a kindoff temporary/dirty patch, I will update my patch asap. I was just editing everything even the generated files to be sure to get rid off Neon:silly: but I will update it.
[LG Optimus 2x] gucky01:
Ok, the patch doesn't work,because android.mk was changed on Dec24. Ffmpeg_multilib 64 was added with a new mpegvideo entry. Should be no problem to add this to your patch.:)
[LG Optimus 2x] wulsic:
Yes I saw that and I think that it's also neccesary to edit config.h since that allows us to compile ffmpeg again, or we should see or we could exclude it but I don't think that that's neccesary. This error is also as far as I remember different then we had before. We had first a error about FPU and CPU but now it's something else. It seems that it has something to do with VP. I will try to solve that if you didn't solved that yet when I come back because I gotta go eat. Btw, I must also find out why my kernels are bootlooping so I will also compare after eating your and mine cm12 kernel.
[LG Optimus 2x] gucky01:
Thanks, my friend! My most hated words are "repo sync". Why have I done this? Build with sources from Dec12 finished well and we could concentrate on the bootloop!:(
[LG Optimus 2x] gucky01:
https://github.com/CyanogenMod/andr...mmit/b9c750dbf8d30c2dbe71871892eab7f495372548

This commit is the reason for the new problems. Android.mk in libavcodec has to be revered to the original values to get it work. The error lines I described above are gone in this way.
[LG Optimus 2x] wulsic:
I know its a pain in the ass but its also better on one side so you wont have to do it later. Else you could always checkout the device tree on the last commit in ffmpeg on 12 decembre
[LG Optimus 2x] gucky01:
Neon makes me crazy

2 days of searching, digging ...

That's the reason for our last problems. We have to edit the neon entry in this file+ those in config.h. that's all to patch!

https://github.com/CyanogenMod/android_external_ffmpeg/blob/cm-12.0/android/include/config-armv7-a.h

Update: 1 value to patch too. Config_thumb has to be 0 in config-armv7-a.h.(Building just fails again)

This will be my last post for today, because I have to work tomorrow and must sleep now.
[LG Optimus 2x] wulsic:
Alright well nice job anyway:good: I was looking into the files again and if you look into that history of those files then you will see what Rmcc has changed

https://github.com/CyanogenMod/andr...b7f495372548/android/include/config-armv7-a.h

https://github.com/CyanogenMod/andr...871892eab7f495372548/android/include/config.h

and we can do the following things to try maybe. I will try that tomorrow.

Open config.h and remove the line:

#include TARGET_CONFIG

or config-armv7-a.h to add this line under Config_thumb 1

#define FFMPEG_CONFIGURATION "--enable-gpl --disable-static --enable-shared --enable-optimizations --disable-doc --disable-symver --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-ffserver --disable-avdevice --disable-devices --disable-filters --disable-demuxer=srt --disable-demuxer=microdvd --disable-demuxer=jacosub --disable-demuxer=sami --disable-demuxer=realtext --disable-demuxer=dts --disable-demuxer=subviewer --disable-demuxer=subviewer1 --disable-demuxer=pjs --disable-demuxer=vplayer --disable-demuxer=mpl2 --disable-decoder=ass --disable-decoder=srt --disable-decoder=subrip --disable-decoder=microdvd --disable-decoder=jacosub --disable-decoder=sami --disable-decoder=realtext --disable-decoder=movtext --disable-decoder=subviewer --disable-decoder=subviewer1 --disable-decoder=pjs --disable-decoder=vplayer --disable-decoder=mpl2 --enable-zlib --enable-pic --disable-debug --arch=arm --cpu=armv7-a --build_suffix= --cross-prefix=../../prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- --enable-cross-compile --sysroot=../../prebuilts/ndk/current/platforms/android-17/arch-arm --target-os=linux --extra-cflags='-DNDEBUG -mandroid -ftree-vectorize -ffunction-sections -funwind-tables -fomit-frame-pointer -funswitch-loops -finline-limit=300 -finline-functions -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone -mfloat-abi=softfp -mfpu=vfpv3-d16 -fstack-protector -fstrict-aliasing' --extra-ldflags='-Wl,--fix-cortex-a8 -march=armv7-a' --optflags=-O2"
[LG Optimus 2x] Sparkles SP:
Very nice work, can't wait until this is up and running! How long do you guys think until it is usable (alpha stages even)? I'll gladly test it :)