Develop Bugs

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74

I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!

Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?

bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.

fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.

I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4

Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!

I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app

If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app

I am definitely willing to help in any way I can.

I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...

grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.

Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?

mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.

Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.

JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?

droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source

JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!

Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.

Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

[ROM] [6.0.x] Official CyanogenMod 13.0 Nightly Builds Oppo N3

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01

Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!

SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).

jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it

good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.

How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk

cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor

Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!

SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.

Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help

This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?

SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.

jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!

SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...

Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.

Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.

To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.

Man, you are the best! And what about sensors?
And where did you find this solution?

hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.

How to make this logs? i know nothing in programming (

[AOSP Tamien 8.1 with OpenGapps]

I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......

deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk

yea, link?

?????

Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk

uplodz complete.

Interesting :good:

I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is

Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself

elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.

prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.

I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!

Nice can we flash the Kernels that have been around here for a while on this rom?

patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.

deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $

OnePlus One Official Lineage OS 15.1

https://download.lineageos.org/bacon
Currently Maintained by jrior001/
https://www.cyanogenmods.org/forums/topic-tag/jrior001/
Install instructions
https://wiki.lineageos.org/devices/bacon/install
Upgrade from official Lineage OS 14.1 possible but as usual clean install is better. Good time to wipe that phone clean.
Please update TWRP to the latest. If you have this device and don't know how to install please follow above procedure.
If you have device encryption enabled, consider removing as its a bit touch and go. As usual always have a full backup and separate copy of your data/pictures.
And the caveat you are responsible for what you do with your device applies and no one else is responsible for your action. People may be able to help if you ask kindly.
Official channel released finally on the 18th of July 2018.
Super effort by Devs specially jrior001, so please donate if you can.
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.

which is d stable twrp version???

jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
3.2.1-0

jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.

Is that cyanogenmods website some kind of fan site? It doesn't look official.

Kernel
Is anybody working on the included Kernel?
The background of my question is that I am experiencing spontaneous reboots when physically leaving a Wi-Fi connection, particularly my home Wi-Fi.
This defect was present in LineageOS 14.1 as well. There I could solve the problem completely by installing the latest Franco Kernel. However, in LineageOS 15.1 the Franco Kernel leads to very frequent soft reboots, like 5 in one hour, so I am now back on the stock kernel.
The only workaround I know is to disable Wi-Fi before leaving a Wi-Fi area, then re-enabling it.
Before other users jump in and state that they don't have this defect, not everybody has it. It is not clear under which conditions the defect shows up. It may depend on certain apps being present. But obviously it is not the apps' fault, as the fact proves that the Franco Kernel resolved it in LineageOS 14.1. Not to mention that no app has the right to reboot the system.

sn809 said:
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Click to expand...
Click to collapse
No sir....actually im nt frequent user of xda forums these days

NetGuard via VPN is not working for me. Under 14.1 was everything ok.

Hardware buttons backlighting is very dim for me even when set up to 100% brightness.

sn809 said:
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
Click to expand...
Click to collapse
The Development section is for users to post their own development work, not links to the development work of others. Please refer to the sticky posted here and be sure to follow the forum rules.
THREAD CLOSED

Android Auto on whyred?

Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!

mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.

drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.

mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!

drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.

mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.

It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.