Develop Bugs

TWRP Touch recovery - 2.6.3.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​ For Latest Download Link Click Here
full SELinux support
Features:
Tested and Working
Backup / Restore
ROM Flashing (of course :good: )
Mounting partitions (and SD via USB to PC)
Screen Timeout - Lock / Unlock (double tap to wake or use power - change timeout in settings)
adb sideload
Clock
Battery
Log
File Manager
Advanced Reboot Options
when powered off and you plug in phone it auto boots to recovery, maybe nice for someone with a broken power button? (so not really a feature...)
Haven't Tested
Fix Permissions
[*]Terminal
[*]Themes
[*]Partition SD Card
let me know if you can confirm these working, my vision is out on loan to a friend an can not test - thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*broken
SD-ext wipe/backup/restore - still working on this one, hopefully wont take too much longer to fix
anyone who wants to test will be rewarded with praise from me! should be safe, has been for me, but I guess I should say the whole I'm not responsible for xyz... but you're on xda, you know this
Just Some Random Screen Shots Of TWRP, Not From This Phone
​*oh and I have some new clockwork recoveries if you all want these too, they appear fine with the minimal test I've done, if you all want I can upload these too - built from newest source something like 6.0.4.6? cant recall the versions and am lazy now, but built for kitkat roms

For sure gonna try this out if I have some free time tomorrow. It's getting late or else I would already be testing it out now

demkantor as you advised me first i just booted the recovery .. works well
flashed recovery works as expected
i dont have sdcard so you know the broken section is not for me

Working ADB sideload confirmed
Mind sharing how did you fix that?
My idea is that the problem is in fstab.recovery, but I'm not entirely sure on that. Could you please share "device-related" changes for TWRP?

Sure thing, I hope have some time in front of a PC this next week, I'll put up a new build with sd-ext fix and post a github link and clean up the op. Sorry just haven't had like ant quality PC time in the past few months
Sent from my Nexus 7 using XDA Premium 4 mobile app

Alright, finally got around to flashing this. All the basic functionality I used CWM for, works perfect in TWRP. Pretty awesome

Man, this is awesome! I was using some old TWRP 2.2.0 version i found on some weird chinese site after failing to build it myself. Thanks fr thins man! :laugh:

awesome job demkantor
and i can gladly take all the credits for this tool :d LoL

Why switch?
Hey @demkantor,
great work again, I guess, thanks. We vision users are lucky to have folks like you still working on our device.
One overarching question--why switch recoveries, and if I do, to this TWRP or your (or Nevergone's?) CWM? I have used 4EXT (I think at your suggestion, in fact) ever since I rooted my phone in August, 2012, and no problems. I have kept up with all the latest ROMs in the Flinny line (and a few others) including 11.0, though I have now stepped back to his last 10.1 build while KitKat needs fixing. My needs are pretty basic, I suppose...I just flash the occasional new ROM, make backups, occasionally restore them (like in going from 11.0 back to 10.1.) I rarely touch adb...it just hasn't been necessary. I am perfectly happy with my phone, and marvel at its longevity!
So, stick with the latest 4EXT, or jump to something newer?
Thanks,
p-d
ps still at the U? Go to Al's for me sometime, I miss breakfast there.

Thanks!
In truth I still prefer 4ext myself, its my favorite recovery but development on it has slowed over the past year. The only reason I bothered to make this was for @AYEHAN who has a broken SD tray and needed to be able to sideload a ROM, currently 4ext is lacking this feature. So if your current recovery is still working for you then I would suggest to stick with it, TWRP is nice and I use it on most my devices (as 4ext isn't available) but if it ain't broke don't fix it!
Yeah last few days of brake before the new semester begins, and for sure will go to Al's, best whole in the wall there is!
Sent from my Nexus 7 using XDA Premium 4 mobile app

One major bug I came across, is it will no longer flash roms. Like, regardless of what the rom is it just won't flash it, it spits out
assert failed: get prop("ro.product.device") == "
E:Error executing updater binary in zip '/sdcard ,
and I know these roms all work since it was flashing them beforehand. Just thought I'd let you know
*Edit*
So any rom other than G2Slim won't flash for me. CM10.1, Flinny's CM11, etc. It's so odd
*Edit 2*
I installed CWM v5 again just to make sure it wasn't a problem with the roms themselves or my sd card, and things install fine, so it must be a random bug with twrp, hopefully a very rare one at that

I just tried and found a similar result, without looking into it much I see there are a couple update-binaries used with various ROMs and this build works for one and not the other, at least that's what I see so far as I'm coaching my friend on how to do this as the phone is with him on the other side of town right now.
I'll look into a fix for this as it would be nice to be able to flash all Roms not just some, thanks for the bug report!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Fix permissions and terminal work fine, I'll try a theme if I can work out how to do it but I don't have a spare SD card I can test partitioning on. All in all great work

Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just tried a theme, works fine. I would make some but I have no working PC right now. Might be able to unpack and edit an existing one on device though

Needed to get a recovery compatible with SELinux support in order to install latest CM11 Alpha 3 (Flinny's).
Works fine. None of the errors above when installing CM11 and gapps.
Great work!

tried this alot of times , plus flash the recovery 3 times but could not sideload an image :/
e:/ sdcard not found something error

sorry for that, I'm sure it's a stupid question, but just to be sure...
there is no different way except flashing this .img using a pc...right? I tried using TWRP app last night but it wants to know which device is and it's not listed
thank you a lot
Alex

If you want I'll make you a flashable.zip or you can use a terminal emulator on your phone, just download to SD card and name it recovery.img
Then open up emulator
su
flash_image recovery /sdcard/recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app

[CLOSED] Goto G3 Android Development

GOTO: NebulaKernel On G3 Android Development
XDA:DevDB Information
NebulaKernel, Kernel for the T-Mobile LG G3
Contributors
Eliminater74, thewalkingdude
Source Code: https://github.com/Eliminater74/NebulaKernel/tree/nebula-mod
Kernel Special Features: Tons of Mods
Version Information
Status: Testing
Created 2015-06-26
Last Updated 2015-10-01

( Downloadz )
CLOSED

NFO:
Closed

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi thanks for your work is appreciated , I have problem installing the file using TWRP it said Error executing updater binary in zip Failed any help will be appreciated.

Nice! Thanks for this!
Sent from my LG-D851 using Tapatalk

egalpr said:
Hi thanks for your work is appreciated , I have problem installing the file using TWRP it said Error executing updater binary in zip Failed any help will be appreciated.
Click to expand...
Click to collapse
Must be an error in zip, Ill fix that and Re-Upload it..

Update: Do to a problem with the Zip file, I had to Redo Zip. New one has been tested by me, And works.
Sorry for the inconvenience..
BTW: This kernel is worked on all the time, So new updates will be released alot. I already know of a few more things that I want to add.
My Goal is to make this Operate at low temps while keeping its performance as well at Longer Battery Life.
One of my test builds, The battery lasted me 3 days on a single charge. Without heavy usage.
My temps range betwen 87f /30c - and - 100f/37c (Stabilize around 97f/ 36c).

Eliminater74 said:
Reerved
Click to expand...
Click to collapse
Updater Binary failed at install... Downloaded from both links, same deal. Swapped out boot img into zip from 06/25 and it installed fine. Just a heads up. Thanks, good work. Todays update even more fun stuff!!!
Edit: I'm too slow, you already know.

zoman7663 said:
Updater Binary failed at install... Downloaded from both links, same deal. Swapped out boot img into zip from 06/25 and it installed fine. Just a heads up. Thanks, good work. Todays update even more fun stuff!!!
Edit: I'm too slow, you already know.
Click to expand...
Click to collapse
You must have gotten the zip that was bad before I replaced it with new one...........
Cause I tested the new one my self. and it worked......

@Eliminater74
Keep it up! It will get easier over time and its nice to look back and see how you have become more adept at what you are doing.
Just some friendly advice:
1. Always give proper credit
2. Always make clean commits.
1. is just because we do this for fun and for some sort of recognition (Even if some Devs won't admit it) and 2. because it makes troubleshooting, and reverting WAYYYY easier. When I started, I learned this the hard way. This way if you get into a situation where you have to make reverts or reset the branch, you are able to be more surgical about what you remove. If you have a commit that has alot going on in it then sometimes you cannot revert cleanly and it will have to be done manually. This can sometimes leave you more prone to make simple mistakes. Ones that we ALL make when Dev'ing late at night after a day of hard work and should really be getting more sleep. lol
Oh and 3. Learn to use Meld properly. This will make merging so easy, and will save you a metric crap ton of time.
If you need anything, feel free to PM me.
Regards,
Render

Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
Sent from my LG-D851 using Tapatalk

bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
This Kernel is for Aosp only that is why your rom is not booting past the splash screen.
Click to expand...
Click to collapse

TheBlackMaou said:
bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
This Kernel is for Aosp only that is why your rom is not booting past the splash screen.
Click to expand...
Click to collapse
Well sh!t. Guess i missed that in the op
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse

bofiana said:
Anybody get a successful boot? I flashed on my existing 20e Rom and even on a fresh install of the Rom and doesnt boot. Stays on LG splash screen. Thanks.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Yes, you you cant install over a stock rom.. its only for Custom Roms AOSP example: CM,PAC-Rom,Bliss,Resurrection Remix, Ext...

RenderBroken said:
@Eliminater74
Keep it up! It will get easier over time and its nice to look back and see how you have become more adept at what you are doing.
Just some friendly advice:
1. Always give proper credit
2. Always make clean commits.
1. is just because we do this for fun and for some sort of recognition (Even if some Devs won't admit it) and 2. because it makes troubleshooting, and reverting WAYYYY easier. When I started, I learned this the hard way. This way if you get into a situation where you have to make reverts or reset the branch, you are able to be more surgical about what you remove. If you have a commit that has alot going on in it then sometimes you cannot revert cleanly and it will have to be done manually. This can sometimes leave you more prone to make simple mistakes. Ones that we ALL make when Dev'ing late at night after a day of hard work and should really be getting more sleep. lol
Oh and 3. Learn to use Meld properly. This will make merging so easy, and will save you a metric crap ton of time.
If you need anything, feel free to PM me.
Regards,
Render
Click to expand...
Click to collapse
Wow, I would of never thought that someone like you would stop in to say anything. And very positive feedback indeed..
When I saw your name, I thought I was seeing things. I had to look twice.
But thanks man... I appreciate everything you said.. It all makes perfect sense..

It's a pity this kernel won't work with slim based roms. I really wanted to try it. Running Tesla ROM and it gets stuck on boot-up screen.

EVR_PR said:
It's a pity this kernel won't work with slim based roms. I really wanted to try it. Running Tesla ROM and it gets stuck on boot-up screen.
Click to expand...
Click to collapse
It boots on my friends Slim Rom.. This kernel is for 5.1.1.

Eliminater74 said:
It boots on my friends Slim Rom.. This kernel is for 5.1.1.
Click to expand...
Click to collapse
Apparently only the original 777kernel works with Tesla. Tesla is lollipop 5.1.1_r4. Thanks anyway.

Proof that it works with Slim based Roms.....
PS: Thats not a screen shot of my phone.. its a friends..

CM 13 ( androi 6.0) for Lg Gpro

Who can build it ??

I could try to Boot it up. Not More. So it have enough bugs for daily use. *troll*

I've been wanting to take a jab at it for some time, but I've been so busy with school especially now with finals coming up. But once finals are over and I'm on break I'll see what I can do.

We got the official cm 12.1 that went to trash more than a year ago. I doubt you sew CM 13.
Sent from my LG-H811 using XDA-Developers mobile app

duongthinh441 said:
Who can build it ??
Click to expand...
Click to collapse
I just started. I am noob with ROM development. Even if I do this would be my first ROM. So dont get your hopes hight. Please let me know if you can help me out with pointers to guides. Just syncing the CM13 repo.

DroidSK said:
I just started. I am noob with ROM development. Even if I do this would be my first ROM. So dont get your hopes hight. Please let me know if you can help me out with pointers to guides. Just syncing the CM13 repo.
Click to expand...
Click to collapse
You can build cm 13???

Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk

DroidSK said:
Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk
Click to expand...
Click to collapse
Yes thanks bro . yeah i think it run on gpro device

DroidSK said:
Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk
Click to expand...
Click to collapse
You have to work ?

Yes i have to work. Will work on this during the weekend.
Sent from my FIND7 using Tapatalk

this is one of the problems with 6.0 on GPRO provided by dev
"I'll be honest: I needed just few more weeks with working USB to get Marshmallow fully functional. I got it running on E988, but some important stuff was broken, thus, device was unusable.
I got it to boot without SELinux - device tree needs new set of rules/fixes on current ones, because some old QCOM rules are dropped from vendor repos since mako isn't officially supported for M. That was ~90% fixed.
There were other problems which made device useless: modem and sensors - main reasons I haven't finished what I started. I had issues with reboots by DSP subsystem on every damn build, and just before my USB died, while experimenting with kernel and init files, I got an idea to disable modem and sensors services (they were causing DSP subsystem reboots) and boom, Marshmallow booted. Managed even to login to my Google account, install apps, use it for a while but had to revert back to LP - main phone without working modem is a tablet, not a phone Unfortunately, some time after that my USB decided to become just a simple charging port, so job was left unfinished.
So whoever is willing to tackle this issue:
- GPU drivers need update, both ion and gpu/msm update (kernel) and libs (need newer libs from mako/flo)
- Modem and sensors HAL need some updating - possibly only libs should be updated, since there were no changes in msm8960/apq8064 3.4 kernels connected to drivers
- Some SELinux stuff needs to be fixed
- Our device is stuck with OpenSSL, Marshmallow uses BoringSSL which has crippled some OpenSSL symbols, so there are some compatibility modules with missing symbols which need to be written... at least, that had to be done back then. Not sure now, it's nearly 5 months later now. Missing symbols can be the reason why both current and Lollipop (kanged from F240) modem/sensors didn't work, I really haven't managed to get usable logs before device's total freeze and reboot with these two services on, so whoever fixes this, well, gets functional Marshmallow
- Camera HAL, our issue since last KitKat days "

But haven't cm13 source code from cyanogenmod

I got some news for you all:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just booted it. No modem, no network, no GPS, no camera, no sensors. It just boots.

Wow!!!

This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
EDIT: Crash is caused by sensors; disabling sensors service in init removes that crash, gets firmwares loaded but... that doesn't help our RIL, not at all. And of course there are no error messages from RIL, absolutely none to be found - dmesg simply states "rild-service crashed", logcat is flooded with NFC crashes so I simply don't have nerves to go through all of that... Gah. I really love this device.
Also, I've spotted an interesting problem - I've fixed fstab, both storages are visible, but it seems like I don't have access to external SD - probably something missing somewhere. Also, I think that kernel needs some more commits (I've patched it enough to get SELinux and GPU going, picking anything other than that causes too much conflicts and build issues... and I'm not even using ShadyKernel as a base, started from clean CM12.1 kernel), so I'll try patching google's kernel_msm for E980 support (from KK source drop). possibly something else is broken... who knows? Better question is what isn't broken, lol.
I'll fix that once I get RIL and sensors working. Other than that, Marshmallow is really nicely working on E980, it just needs a lot of work, and a bit more knowledge than I have... well, time to learn.
Whoever is willing to join, kernel is available on my github (lge-kernel-gproj, branch cm-13.0). Device tree and vendor files aren't still uploaded (there are bunch of changes I haven't committed yet), so you may want to wait for them...

Try bro !!

ShadySquirrel said:
This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
Click to expand...
Click to collapse
Thx for still be trying!

Thanks---I'd love for this to work so I have a viable spare brought back from the dead!

ShadySquirrel said:
This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
EDIT: Crash is caused by sensors; disabling sensors service in init removes that crash, gets firmwares loaded but... that doesn't help our RIL, not at all. And of course there are no error messages from RIL, absolutely none to be found - dmesg simply states "rild-service crashed", logcat is flooded with NFC crashes so I simply don't have nerves to go through all of that... Gah. I really love this device.
Also, I've spotted an interesting problem - I've fixed fstab, both storages are visible, but it seems like I don't have access to external SD - probably something missing somewhere. Also, I think that kernel needs some more commits (I've patched it enough to get SELinux and GPU going, picking anything other than that causes too much conflicts and build issues... and I'm not even using ShadyKernel as a base, started from clean CM12.1 kernel), so I'll try patching google's kernel_msm for E980 support (from KK source drop). possibly something else is broken... who knows? Better question is what isn't broken, lol.
I'll fix that once I get RIL and sensors working. Other than that, Marshmallow is really nicely working on E980, it just needs a lot of work, and a bit more knowledge than I have... well, time to learn.
Whoever is willing to join, kernel is available on my github (lge-kernel-gproj, branch cm-13.0). Device tree and vendor files aren't still uploaded (there are bunch of changes I haven't committed yet), so you may want to wait for them...
Click to expand...
Click to collapse
LG got a lot of G/Gpro hacks in our current ~LP kernel. You'd probably have an easier time porting what ever changes you needed from the other kernel you're referencing, to our current kernel. Rather than starting fresh. However if sometimes starting fresh is a lil easier if another similar device has done it already, and you have something to hold onto. I wish I could actively help your efforts but apart from not having a booting computer rn lol, school ain't no joke. I'm a senior now and I'm still tryna master my ACT score and start applying for colleges soon

Emmanuel U said:
LG got a lot of G/Gpro hacks in our current ~LP kernel. You'd probably have an easier time porting what ever changes you needed from the other kernel you're referencing, to our current kernel. Rather than starting fresh. However if sometimes starting fresh is a lil easier if another similar device has done it already, and you have something to hold onto. I wish I could actively help your efforts but apart from not having a booting computer rn lol, school ain't no joke. I'm a senior now and I'm still tryna master my ACT score and start applying for colleges soon
Click to expand...
Click to collapse
I do have CAF based kernel (LA.AF.1.1_rb8 + LG patches from Lollipop sources - believe it or not, LG pushed sources for E98x together with F240x ones), ready and booting. It was easier working on that than patching existing one - I don't want to spend few weeks just patchibg things up, like I had for lollipop and gpu driver backport... That kernel is 5.0.2 ready, just have to figure out from where does CM patch those - stuff isn't only from kernel_common... so I'm thinking about similar thing now - google_msm (everything is already there) + kitkat drop patchup, just to get camera and board going.
Our device tree is also a mess, part mako, part Optimus G. Missing lots of things (have you ever unpacked stock boot.img? Damn those inits...) Started working on pure G Pro tree, but that will have to wait for a bit - there is bit too much work, and I have studies to finish, lol. Just lets hope that my USB won't die again, since "fix" I've applied is kind of temporary.

[DISCUSSION] Android 7.0 Nougat

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let the discussion begin ​

Hopefully this will no show stopper -> No Nougat on smartphone with Snapdragon 800/801 see e.g. here and here

Oppo must be relieved. No more criticism about their awful software support. Now you can blame android.

Let's hope so... It would be a shame not to get N on our devices...

interessting article - Android 7.0 and the Snapdragon 800 — a conundrum

Hummm... OnePlus 1 that have the same SoC has Find7 already have an experimental Android N build... The few main questions here is about if there any CM N builds, since Qualcomm wont delievery any drivers for 801 socket...
CM will support Find7 with Android N?????
If there any AOSP/CM you can have the full potential of the software graphic drivers...????
EDIT: IT seems CM will support Find7s/a on Androind N (CM 14) :highfive: :good: :laugh:

Injected said:
EDIT: IT seems CM will support Find7s/a on Androind N (CM 14) :highfive: :good: [emoji23]
Click to expand...
Click to collapse
just your guess or fact ? Any sources for that information ?

der_Kief said:
just your guess or fact ? Any sources for that information ?
Click to expand...
Click to collapse
Sorry forgot update the post... hehehe
Here the source, find7a/s is listed in line #15
http://www.gammerson.com/2016/05/devices-getting-official-cm14-rom-android-n.html

thx for that link .... would be nice if they end up being right .....
and to be honest i hope @maxwen will bring OMNI to our Find7
--Update--
short statement from maxwen:
Code:
[I]... Regarding 8974 situation - I am pretty sure we can continue on 7 with what we have.[/I]

Injected said:
Sorry forgot update the post... hehehe
Here the source, find7a/s is listed in line #15
http://www.gammerson.com/2016/05/devices-getting-official-cm14-rom-android-n.html
Click to expand...
Click to collapse
Not only abv is written at the end of May, this "source" is bare of any facts regarding the problem.
There's a lot of rumor about the fact that Qualcomm's Adreno 300 probably wouldn't support the new Vulkan-Graphics-Interface of
Nougat; since Google hasn't published the Compatibility Defnition Document (CCD) yet, nobody REALLY knows - it will stay a rumor until it's released.
It's very unlikely that CM would work on a solution for "old" devices for which development they cannot pay for (since they don't have the resources - and who is going to pay them back?). They simply couldn't finance it - and economically it wouldn't make sense - even if they could.
It's very unlikely that Qualcomm would invest into new drivers etc, since they don't sell the "old stuff" anymore - what would be their return on investment for this?
Last but not least, the device manufacturers as key accounts would'n push Qualcomm to go for it - since they want to sell new devices (which are being supported), and customers would drop their old phones (maybe) earlier to buy a new one.
If the rumor should be confirmed at the end - the only one to blame is Google. Up to day, they haven't developed a reliable strategy to stop the fragmentation of
this OS. At least that's the very reliable and solid fact. And unfortunately, the only one.

cm14 for find7 h t t p://yun.baidu.com/s/1eSbm6dk#path=%252Fandroid%252F%25E7%25AC%25AC%25E4%25B8%2589%25E6%2596%25B9ROM%252FOPPO%2520Find%25207%252FCM14.0-Find7%252Faosp-nougat

clxer said:
cm14 for find7 h t t p://yun.baidu.com/s/1eSbm6dk#path=%252Fandroid%252F%25E7%25AC%25AC%25E4%25B8%2589%25E6%2596%25B9ROM%252FOPPO%2520Find%25207%252FCM14.0-Find7%252Faosp-nougat
Click to expand...
Click to collapse
there nothing....

Injected said:
there nothing....
Click to expand...
Click to collapse
There is AOSP nougat for find7, not CM. Downloaded, gonna try soon.

boss.zz said:
There is AOSP nougat for find7, not CM. Downloaded, gonna try soon.
Click to expand...
Click to collapse
Yes... but there nothing there in the link...
Or the link you gave me is wrong somehow...
PS.: Found it... xD

Injected said:
Yes... but there nothing there in the link...
Or the link you gave me is wrong somehow...
PS.: Found it... xD
Click to expand...
Click to collapse
may you share the link ? or maybe upload to cloud ?

der_Kief said:
may you share the link ? or maybe upload to cloud ?
Click to expand...
Click to collapse
The problem i cant download even with jdownloader... need someone who have baidu account...

boss.zz said:
There is AOSP nougat for find7, not CM. Downloaded, gonna try soon.
Click to expand...
Click to collapse
Can upload to drive or other cloud share....???
Sent from my X9076 using XDA Free mobile app

I'll upload tmr mornimg. It's almost 4am here.
This rom has some bugs. First, you need to remove dpmservices or disable it (known issue for opo too) to avoid continuous fc. Second, for gapps you need to manually enable all permission for google play services to avoid fc. Last, camera is not working in this build. I cannot find any workaround for this.
Ps. This rom does not support f2fs, ext4, ntfs for SDcard (exFat not tested).
Ps2. Except broken camera, everything is working smooth.
Ps3. I have no idea about battery life since I've just install it for a few hours.

boss.zz said:
I'll upload tmr mornimg. It's almost 4am here.
This rom has some bugs. First, you need to remove dpmservices or disable it (known issue for opo too) to avoid continuous fc. Second, for gapps you need to manually enable all permission for google play services to avoid fc. Last, camera is not working in this build. I cannot find any workaround for this.
Ps. This rom does not support f2fs, ext4, ntfs for SDcard (exFat not tested).
Ps2. Except broken camera, everything is working smooth.
Ps3. I have no idea about battery life since I've just install it for a few hours.
Click to expand...
Click to collapse
Got it... Already downloading... By the way it support LVM or any other unification storage... ??
Offtopic
This Wuxianlin is so fuking bad ass so much roms he port in his baidu cloud.... JESUS.... oO
There unification patch for AOSP roms like omni and Spectrum for those who are in chinese partition and there are unification patch for COS 2.1.5 in chinese partition... Dam i gonna have LONG WEEKEND

Injected said:
Got it... Already downloading... By the way it support LVM or any other unification storage... ??
Offtopic
This Wuxianlin is so fuking bad ass so much roms he port in his baidu cloud.... JESUS.... oO
There unification patch for AOSP roms like omni and Spectrum for those who are in chinese partition
Click to expand...
Click to collapse
Only chinese partition. LVM not supported. Coldbird untested.

LineageOS 15.1 and Treble Progress

Hey everyone
So... because i rather made a "big" of breakthrough today, im gonna share my progress on various projects.
My progress on LineageOS 15.1 (and GZOSP and CrDroid, didnt try more yet) all work pretty fine, basically everything works. Theres just 1 annoying thing (which im hunting down since easter). It can crash rather often during boot. Means: it freezes and then reboots.
See for yourself:
https://www.youtube.com/watch?v=rUUopOYDYjs:
https://youtu.be/l7HEMIreVwE:
A video of CrDroid (recorded with my OnePlus 2 lol)
https://youtu.be/d5XGM9xCrqE:
I also managed to create a seperate vendor partition (yes, i actually repartitioned) by making /system smaller (had 1.5GB left even though on full stock rom, not debloated a single bit). Made it 512MB in size.
This allowed me to actually use it (mount in kernel), and i managed to (nearly) bring Treble support to the V30
With nearly i mean that the GSI boots, but the process "system" crashes (2 libs missing, need to see how i get them to /vendor, currently they are in /system of my lineage build)
The libs are called [email protected] and [email protected]
Here a video of LOS15.1 with Treble Check (yes, that prop can be faked, i know, and its only half true so far i guess)
https://youtu.be/MUNij0sspKM:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
2) share my progress, making people hope that the V30 development isnt completly dead
3) Hopefully get a the attention of a few more devs, so we can figure those boot issues out (the reason i didnt release it yet, as it sometimes also freezes when you have gapps flashed)
best regards
SGCMarkus
PS: Ask all the devs you know, maybe someone knows the issue too, and knows a way to fix it
PPS: idk why the embedded youtube links dont work, but i put the links there on their own

Expect it to be used everyday! Beautifully

Wow good work. Hopefully tmobile varient will get recovery someday [emoji849] miss experimenting with roms. Stock on v30 is good with a theme but sometimes i miss custom roms
Sent from my LG-H932 using Tapatalk

So.. tested a build from last night fast before i rushed to the train ?
The GSI now boots successful and seems to be stable. Everything except haptic feedback/vibrator seems to work (i know the reason for that, as it loads the aosp implementation first, but the v30 needs the lge implementation in vendor)
Only saw wifi, bt, nfc was on, had signal (and asked for sim pin), and checked if camera had a preview, it did
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess

Doblix said:
Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess
Click to expand...
Click to collapse
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)

SGCMarkus said:
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)
Click to expand...
Click to collapse
I would be interested in testing the treble ones if possible, if you can guide me how to do the repartitioning or what tools to use that would be no problem for me.
I solely use Linux on my PCs (Arch if that matters) so that is no obstacle for me.
A nice and user solution would probably be a flashable .zip file for TWRP which does the repartitioning directly on the device.

Excited
I'm really excited to get Lineage OS onto my V30. But I just don't think I can make the transition until the Camera is ported. The the only app which can utilize both sensors, 4k video recording and laser focus. I use the ported G camera for pictures right now because of HDR+, and it can record 240fps slow mo. But it can't record 4K video. There is just nothing which can fully replace the stock LG app and use all the camera's hardware properly. Even things like open camera can't use Laser focus. So I just can't make the switch until the LG camera is ported. Also I hope that the QuadDAC will be supported.

GSIs also dont seem to have the boot issues for some reason....
So its neither the ramdisk, nor kernel, nor vendor files.... something in my device tree is wrong then xD
PS: added a poll

Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!

Just wanted to add my 2 cents. Definitely extremely excited about a fully stable and working LineageOS. Even if it doesn't have Trebble. Stability is definitely a must (at least for me) since this phone is a daily driver, but I would love more than words could convey if we had a working AOSP type ROM for this phone. Please keep up the solid work, and thank you in advance! As a dev myself (not android, sorry) who has done volunteer work, I know how important the props are to keep you motivated. So again, awesome job so far, and thank you!

okaiuz said:
Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!
Click to expand...
Click to collapse
All GSIs should work, currently booted a LineageOS GSI, also tried the AOSP one
PS: found the fix for the vibrator... LGs implementation is just stupid lol
Needs ro.product.manufacturer set to LG or LGE, but GSIs dont have that.... only ro.vendor.product.manufacturer is set to LGE, but that isnt enough...

SGCMarkus said:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
Click to expand...
Click to collapse
Hey SGCMarkus,
First Off.... Amazing Work!!!!! Rly nice to see, that there is some developing going on. Cant explain, why this phone is like beeing dead to devs.
To get to the Point... I would imediately Stop setting Up my Linux Dev system and would Test 4 you. It is more important to Help the community getting some kickass Roms rather cooking for myself
If you are interested, Just leave me a PN with dl-link and additional Infos.
So Long,
Please keep Up that great Work.
Tipnuck