Develop Bugs

[ROM][AOSP 2.3.7] OMFGB compiled and ported

Hy all,
inspired by this thread I spend some spare time in compiling OMFGB sources for use with the hero gsm.
Because of the fact, that I did not manage to successfully compile the OMFGB sources directly for the hero gsm (compiling was OK but could not get rom to boot) I did it the other way.
I compiled the sources for the hero cdma (heroc) and afterwards ported it to hero gsm.
I integrated Erasmux fly-kernel 13 since I used it with all other hero roms before.
After testing the rom for ~1 week (also my son is quite satisfied with it) I decided to share it.
I took out some apps that were not usable (for example God Mode) and put in minimal gapps so that it's possible to sign in on google account and run market.
Also I replaced the LatinIME.apk with the CMs one to get other keyboard layouts than querty.
I'd recommend to install morelocale2 to be able to dial 123456 instead of 123-456.
What I have to say is that I'm by far no developer (at least not on android platform).
Download
OMFGB-Hero -www.2shared.com
OMFGB-Hero - www.mediafire.com
Thanks and credits go to
OMFGB Team for their sources
Erasmux for the kernel
stritfajt and bharat_goku for their patients and giving me directions

i'll take a look at this when i've got some spare time

Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D

cartman333 said:
Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D
Click to expand...
Click to collapse
God mode seems not to be compatible with hero, all menu entries were grayed out, so I decided to delete it from package.
Maybe someone has a clue how to get it run

Can you upload it to some other site? I can't seem to download from 2shared.

aca89 said:
Can you upload it to some other site? I can't seem to download from 2shared.
Click to expand...
Click to collapse
Uploaded to mediafire

Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium

bharat_goku said:
Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I ported and tested the rom step by step.
Since all keys work as they should, I skipped this step.

I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers

aca89 said:
I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers
Click to expand...
Click to collapse
For the advanced settings, I could not get the God_Mode fully working so far.
For a2ext, I don't use it since I don't need it.
My son, which has a hero too, uses a lot of games.
For him I did custom mtd layout, much faster than a2ext cause it's kept all internal.

Please add the Russian.

[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.

[Q&A] [ROM][4.4.4][KTU84Q][SlimKat - Hercules][OFFICIAL+Weeklies]

Q&A for [ROM][4.4.4][KTU84Q][SlimKat - Hercules][OFFICIAL+Weeklies]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][KTU84Q][SlimKat - Hercules][OFFICIAL+Weeklies]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

BEEN LOOKING For SO LONG!!
NoSpamDan said:
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you will find everything you need to know about SlimRoms.
Slim Downloads - Download the ROM, GApps and other Addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequently asked questions with answers.
Kernel Source - The source of your device's kernel.
See Post #2 for Known Issues and Installation Notes.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Special thanks to (in no particular order):
The Slim Team
CyanogenMod
prbassplayer
wantowan2
kintwofan
Disclaimer: SlimRoms are not responsible for any damages to your device.
Click to expand...
Click to collapse
helllo,
will this work for mine??
Heres is my Phones info.
SGH-T989
Android Version
2.3.6
Baseband Version
T989UVLDH
Kernel version
2.6.35.11-1209942
Build Number
GINGERBREAD.UVLDH

mono956 said:
helllo,
will this work for mine??
Heres is my Phones info.
SGH-T989
Android Version
2.3.6
Baseband Version
T989UVLDH
Kernel version
2.6.35.11-1209942
Build Number
GINGERBREAD.UVLDH
Click to expand...
Click to collapse
Absolutely should work, however, you have some homework to do in order to ensure success. You will need a new recovery, new radio and might need to jump to ICS first, not sure. One other thing I would recommend is turning on your GPS and getting a GPS lock before rebooting to flash a new radio, recovery and ROM if coming from GingerBread as you are...
Head on over to Vincom's 1-Stop Sticky Thread, which contains information all about the SGH-i727 Skyrocket, and the T-Mobile Dev Thread. The Hercules is almost identical and hardware, and most Skyrocket ROMs should work on both, with maybe one issue of screen orientation (turned 90 degrees).
There are radio links in the OP of my SlimKat Hercules thread.
Read up in those threads, and then find a newer recovery and radio that you need need to proceed.

Thank to Slimrom
I'm very happy to keep my old pal (T989) on working everyday with Slimrom.
I change from CM11 to Slimkat build 7 serveral months agos.
I flashed by zip with CWM, it was working but couldn't reboot by default, dark screen and no response anything. I think it was my fault.
Then I restored and flashed it again with Rom Manager, it's successful.
With mini gapps pack, Rom (build 7) works like a charm. Then I disabled some google services for better RAM and speed (for example Hangout is kinda heavy)
Herein is some point that I think could make it better:
There is no option to change launcher ( Nova launcher by default)
There is no option to change/customize clock widget on LockScreen (DashClock Widget by default)
Recent Apps function: didn't show the latest using app on the list (when my current screen is homescreen).
Recent Apps function: Couldn't access to previous app (Close App error)
Step to reproduce: If you're using App A, then App B, you try to access App A via Recent Apps function. Then error message "Close App" will be display. But luckily I've found my own way to resolve, just change to random App C, then back to App A as usual (a little bit unconvenience but it was not a problem)
Notification couldn't updated by user behavior. For example, I have notification for new message on Viber, then i access Viber to check a new message ( do not touch on Notification ), so this notification will be remained for a long time ( until I touch on it for re-read)
I couln't tested with build 8 due to camera error ( couldn't handle camcorder function, couldn't focus) but I'm really happy with the build 7.
Thank you.

Can't hear or make calls after flashing
Installed the stable Slimkat for t989 I can't hear any dialing sound or anything when somebody calls me :/ back to stock

4xxxxL said:
Installed the stable Slimkat for t989 I can't hear any dialing sound or anything when somebody calls me :/ back to stock
Click to expand...
Click to collapse
Stable version 8? No such issues have been reported. Bugreport?
One Skyrocket user has reported the inability to receive casks in WEEKLY version 8.12.1. He went back to weekly version 8.10 and incoming calls are working. These phones share a lot of source code.
It must be caused by something merged since the 8.12.1 WEEKLY.
Read post 2 in the main thread for how to submit a Slim bugreport to help fix this.
Sent from my OnePlus One BACON using Tapatalk

yep
NoSpamDan said:
Stable version 8? No such issues have been reported. Bugreport?
One Skyrocket user has reported the inability to receive casks in WEEKLY version 8.12.1. He went back to weekly version 8.10 and incoming calls are working. These phones share a lot of source code.
It must be caused by something merged since the 8.12.1 WEEKLY.
Read post 2 for how to submit a Slim bugreport to help fix this.
Sent from my OnePlus One BACON using Tapatalk
Click to expand...
Click to collapse
Yes. 8.0 stable release from the site slim-hercules-4-4-4-build-8-0-official-6919
as for the bug report I panicked since I needed the phone in working state withing an hour so I flashed the stock firmware back so not much help from me now . But yeah I called a phone in the household and phone was making a call its just I couldn't hear the dialing tone and when the second person picked up it was dead silence on my side.
This is not he first time I had this issue previously I tried cyanogenmod 10.2.0 stable and had the same issue out of nowhere after month of working just fine

Thanks for the feedback. Full wipe, including /data wipe or factory reset?
bacsidien94 said:
Herein is some point that I think could make it better:
There is no option to change launcher ( Nova launcher by default)
Click to expand...
Click to collapse
All you have to do is install another launcher, then press the home key and select your preferred one and select "Always"...
There is no option to change/customize clock widget on LockScreen (DashClock Widget by default)
Click to expand...
Click to collapse
You have to allow lock screen widgets, then drag it off the screen and add what you want.
Recent Apps function: didn't show the latest using app on the list (when my current screen is homescreen).
Recent Apps function: Couldn't access to previous app (Close App error)
Step to reproduce: If you're using App A, then App B, you try to access App A via Recent Apps function. Then error message "Close App" will be display. But luckily I've found my own way to resolve, just change to random App C, then back to App A as usual (a little bit unconvenience but it was not a problem)
Click to expand...
Click to collapse
To many possibilities without a bugreport...
Notification couldn't updated by user behavior. For example, I have notification for new message on Viber, then i access Viber to check a new message ( do not touch on Notification ), so this notification will be remained for a long time ( until I touch on it for re-read)
Click to expand...
Click to collapse
What other apps do this? Tapatalk does this for me on CM11S with my OnePlus One even. Probably an app issue.
I couln't tested with build 8 due to camera error ( couldn't handle camcorder function, couldn't focus) but I'm really happy with the build 7.
Click to expand...
Click to collapse
Full wipe. Camera is fine on Build 8.
Everyone, PLEASE, if you have issues, refer to post 2 IN THE MAIN TOPIC for instructions on submitting a Slim bugreport in a new thread on the SlimROMs support forum!
Sent from my OnePlus One BACON using Tapatalk
---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------
4xxxxL said:
Yes. 8.0 stable release from the site slim-hercules-4-4-4-build-8-0-official-6919
as for the bug report I panicked since I needed the phone in working state withing an hour so I flashed the stock firmware back so not much help from me now . But yeah I called a phone in the household and phone was making a call its just I couldn't hear the dialing tone and when the second person picked up it was dead silence on my side.
This is not he first time I had this issue previously I tried cyanogenmod 10.2.0 stable and had the same issue out of nowhere after month of working just fine
Click to expand...
Click to collapse
No problem. Sounds like a radio issue though or dirty flash.
Sent from my OnePlus One BACON using Tapatalk

I'm using the build by Dan that fixed calling, and I'm getting a huge memory leak problem. The Base System process would start using 100 MB to 200 MB of my RAM, while hogging a part of my CPU at all times. I was watching a video earlier and noticed my CPU usage jumped to 100% and the available RAM started going around 200 MB before the system killed my on-screen system stats display (Cool Tool). I didn't have any other apps running and nothing was being updated at that moment. The video started getting choppy and my phone froze soon after. If you need a log from me, I'll be happy to provide one.

dennis96411 said:
I'm using the build by Dan that fixed calling, and I'm getting a huge memory leak problem. The Base System process would start using 100 MB to 200 MB of my RAM, while hogging a part of my CPU at all times. I was watching a video earlier and noticed my CPU usage jumped to 100% and the available RAM started going around 200 MB before the system killed my on-screen system stats display (Cool Tool). I didn't have any other apps running and nothing was being updated at that moment. The video started getting choppy and my phone froze soon after. If you need a log from me, I'll be happy to provide one.
Click to expand...
Click to collapse
Have you tried the 8.16 weekly from the Slim site, or the test build I posted? Either way, there shouldn't have been any changes (that I made, at least) which would cause such a memory leak...
Clean flash? What GApps version? What app were you using to watch video? YouTube has had some intermittent issues, and I have also heard of recent Google Play Services issues...
If you can start a new thread in the Slim Hercules forum and post a good description with a Slim bugreport, it may be helpful. See Post 2 of the main thread for more details on helping to squash any bugs.

After I installed the rom, the slim gapps, and supersu, my phone did not boot up and did not even show a bootanimation. I tried going into recovery to restore a backup but it would not enter recovery mode. There would just be gentle vibrations and then a black screen. I was using TWRP v2.8.4.0. I would prefer to avoid the hassle of flashing through odin. Please help, thank you.

berZerk7 said:
After I installed the rom, the slim gapps, and supersu, my phone did not boot up and did not even show a bootanimation. I tried going into recovery to restore a backup but it would not enter recovery mode. There would just be gentle vibrations and then a black screen. I was using TWRP v2.8.4.0. I would prefer to avoid the hassle of flashing through odin. Please help, thank you.
Click to expand...
Click to collapse
Can you get to download mode? With phone off, hold both Vol Up & Vol Dn while plugging a computer USB cable in.
Sounds like a bad flash, bad download, recovery issue, or possible h/w problem. The fact that you can't get to recovery suggests a recovery or h/w issue to me.
Does the below work for Recovery mode?
Press and hold Vol Up, Vol Dn and Power for 2 seconds, then release Power but continue holding Vol Up & Vol Dn until recovery loads.
Sent from my OnePlus One BACON using Tapatalk

General Discussion [ Share and Compare ALL Custom Builds]

Keep the trouble shooting questions for each specific ROM or Kernel to THEIR threads. So that way Devs can be made aware of any errors to be able to work on, if need be, and for when people are searching for solutions to their problems the answers won't be scattered around. Consolidation makes everything easier!
What's your build? What are you loving about it? Any MOD recommendations?
Mine:
Viper10 ROM by TeamVenom
ElementalX Kernel
&
A.R.I.S.E
Sound Systems™ audio MOD
I'm a first time rooter (introduced to it by my fiance) and aspiring developer. I am going back to school to get that ball rolling. I'm socially awkward whilst being a social butterfly (once I'm out of my shell). The A.R.I.S.E team and TeamVenom have helped me to come out of that shell here on XDA so I'm ready to get socializing and talk all things root! However, I don't want to blow up their threads with unrelated posts...and so I've created this thread - so let's have at it and share ideas, opinions, and have fun! Remember to keep issue/ questions related to each ROM, Kernel, MOD etc. posted ON THEIR threads! So please include a link to their XDA thread when sharing what you've got.
Be kind and respectful. And have fun!
(Still need assistance with getting your HTC 10 rooted? Check This Guide out!)
https://youtu.be/1iAYhQsQhSY​

Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs​
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers

Only Cool Kids Reply to Their Empty Threads
EDIT: Lol got a post while taking 10 years to write this one...so it doesn't appear as though I was my own first response...but if I wrote like a normal person, I would have been.
TL;DR - Zip below will get rid of red message during boot, REQUIRES S/OFF, if you choose to flash this I'm NOT responsible for bricked phones, this zip file works for US Unlocked HTC 10 phones - but I'll rewrite the files inside to match your CID if you need me to, not originally my work and I don't know who's it is...sorry!
-Rename the zip file 2PS6IMG.zip & place it in the external SD card
-Boot down to download mode and if it's all groovy there will be a message at the bottom outlining that it found the "2PS6IMG" zip file and will tell you to press VolUp to proceed with the flash or VolDwn to continue to the normal download mode screen options
NOTE: if your screen doesn't display that initial message at the bottom and just goes to the normal download mode options then you've named the zip file wrong. Make sure that you didn't end up with 2PS6IMG.zip.zip during the renaming process - it HAS to read 2PS6IMG.zip or download mode will not see it as it is scanning for that name exclusively!
- If you got the message go ahead and hit volume up and, when prompted at the end, hit the power button. If you're phone boots down immediately after hitting the volume up button DON'T FREAK and leave it be. It'll kick back up and finish it's thing.
- Reboot and enjoy! (First boot up may take longer than you're comfortable with, that's normal chill for a moment and it'll all work out)
(First to reply to my own thread, crazy stuff happening here...watch out! )
Never understood why the TL;DR is put at the bottom. I know I write novels...I love words but I feel the TL;DR is more thoughtful to place at the top...so you don't have to wade through the overwhelmingly copious amounts of my words to find out there was a TL;DR option. Always thinking of you :angel: however, surely there exists an individual who not only continues and reads my posts in their entirety, but is as entertained reading it as I am writing it!
.............
Anyway, since this is meant to be a thread in which we share fun rooting tweaks and whatnot, I thought I'd go ahead and add this zip file. If you aren't a fan of the red message during the boot up that appears after you've successfully rooted - I've got your solution! I do have to apologize... I'm not sure who the original creator is. My fiance sent the file to me through Bluetooth and I rewrote a couple lines in the file so it would work with my CID. I tried to find the correct individual or thread to link in order to give them the proper credit, but there were a few posts for it so I'm unsure who it is. Just know I'm not trying to claim this for my own... just sharing the love :victory:
MAKE SURE YOU ARE S/OFF BEFORE DOING THIS! YOU'RE FLASHING THIS ON YOUR OWN ACCORD, I'M NOT RESPONSIBLE FOR ANY SOFTWARE/ HARDWARE FAILINGS
This is for the US Unlocked phones. So if you're not US Unlocked, but you want up in this sexy zip action, let me know and I can rewrite the file for you. The CID just needs to be rewritten to match the one on your phone. As a precaution I also rewrote the "mainver" line. It had the original 1.21.531.1 (T-Mobile's current software number) to the updated 1.80.617.1 (the current software number for US Unlocked). I wanted it all lined up perfectly, just in case, however IDK if you need to rewrite the "mainver" live in that text file my phone is fully functional after the rewrite and flash so I'm confident that I took the right steps. I posted what I've got going on for my custom ROM/ Kernel in the OP, if that's important for you to know. I've got the instructions above in TL;DR - no need to repeat. Let me know if you have any questions!
:highfive:​

5m4r7ph0n36uru said:
Mine are
LeeDrOiD10 ROM
either with the build-in
~clumsy~ Kernel
or
ElementalX Kernel
No sound mods as the audio boost of LeeDrOiD is workin' just fine with the build in DACs​
Used Viper for a long time and it is a great ROM. In fact I went to LeeDrOiD10 cause the tweaks on Viper10 are just so many, and most of them I've never used at all. On LeeDrOiD there are just a few tweaks, where all those I need and use are present.
Cheers
Click to expand...
Click to collapse
Thank you for the reply! I haven't checked LeeDrOiD10 out personally, but I saw it on my fiances phone when he got uber frustrated at a camera defect post viper update. The V10 ROM update caused our kernel to be temporarily incompatible...so he temporarily ditched V10 and tried LeeDrOiD10.
He was saying the same things as you in regards to fewer customisation's. And hebmade mention of it being a little more user friendly. But, ultimately, he returned to V10
EDIT:@5m4r7ph0n36uru what exactly does the LeeDrOiD10 ROM offer in terms of the sound boost? An equalizer? Or a little more than that. I didn't check that feature out. I didn't know it was one. My other half may have known though. We love the crazy amounts of tweaking you can do with Viper4Android in the A.R.I.S.E. MOD and all their tweak.prop files/ profiles that we can load up!
Being a spectator of LeeDrOiD10 was sufficient enough for me...only because I know myself, and I LOVE having as many options and open doors, in regards to messing around with my phone, as possible. Tis more dangerous waters to tread that way...but that's all the fun! And I'm confident enough in myself to be able to recover from most things. After all XDA has strong support to offer!

Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs

5m4r7ph0n36uru said:
Yeah I know and it always has been fun changing nearly every detail in a ROMs behavior as it is possible on Viper10. But in fact I guess I'm maturing from this phase in my live where modding was the one and only, as we'd say in germany.
In fact I'm getting older and less fascinated by all those features. Maybe it'll come a time when I'll again become fascinated by modding and tuning every tiny bit of a ROM, but at the moment I really just need some basics.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
There's a flavor for everyone! And our taste buds change over time for sure. So long as you're happy with your phone and its features, that's all that matters!

[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 $