{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AOSPA-L 5.1 for the AT&T LG G3 (D850)!
The Legacy extension of the ParanoidAndroid project.
Disclaimer!
Code:
#include
/*
* [B]Your warranty is now void.[/B]
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
READ THIS FIRST!
Google+
The Legacy of Paranoid Android
Instructions
If installing fresh and/or coming from another ROM (including previous PA versions)
Reboot into Recovery (I prefer TWRP 2.8.6.1) and MAKE A BACKUP!
This is Alpha software on a $500+ device, being cautious is okay.
Wipe System, Data, Cache, and Dalvik Cache
Install the ROM
Install GApps
Install SuperSU (if you want to have root, that is)
Wipe Caches and Reboot
Profit!
If coming from a previous version of PA 5.1 ONLY
Reboot into Recovery (I prefer TWRP 2.8.6.1) and MAKE A BACKUP!
Wipe Cache and Dalvik Cache
IMPORTANT! If you are coming from a build BEFORE 5/13, you will need to wipe /system/, and install GApps and SuperSU again. If you are on that build or later already, you do not!
Install the ROM
Wipe Caches and Reboot
Profit!
Download Links
ROM: https://www.androidfilehost.com/?w=files&flid=36181
Gapps: Official TK Gapps or other LP Gapps
SuperSU: http://download.chainfire.eu/supersu
AOSPA-Legacy Links
Google+: https://plus.google.com/communities/103106032137232805260
Gerrit: http://gerrit.aospal.com/
GitHub: https://github.com/AOSPA-L
Known Issues
DT2W sometimes doesn't stick after reboot.
Misc
Questions about "battery life" with this ROM? - Read this!
#StayParanoid
XDA:DevDB Information
AOSPA-L 5.1 for D850, ROM for the AT&T LG G3
Contributors
Cryptecks, bryan2894, invisiblek, savoca, CyanogenMod
Source Code: https://github.com/AOSPA-L/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2015-05-06
Last Updated 2016-02-24
Changelog
July 4th, 2015 - Happy 4th of July!
Full Release Notes: Google+
NFC Fixes
EdgeService updates
LOTS of bug fixes, see full release notes and Gerrit merged commits
June 19th, 2015 - A Sweet and Polished Path
Full Release Notes: Google+
Immersive mode QS detail panel clean up.
QS reorder reset button is now either on Settings/Backup and Reset or long pressing the settings wheel in statusbar header
Screen unpinning fixed on devices with hardware buttons.
Volume Panel tweaks.
Volume Key Controls Settings
New Settings Cellular drawable
Fixes to the status bar battery icon
Much more
June 12th, 2015 - The Paranoid Road to Perfection
Full Release Notes: Google+
Immersive Mode
QS Re-Order
LOTS of bug fixes, see full release notes.
May 28th, 2015 - I/O and Android M
Full Release Notes: Google+
Switch to officially recommending TK GApps
Wake on plug
Home button wake
Theme Engine bug fixes
Volume Panel enhancements
Low-level optimizations to our core base
Loads of bug fixes for several NPEs, ANRs and OOMs.
G3 specific: Possible fix for AUX cord/port issues (I personally have them and it drives me insane).
May 20th, 2015 - My Melancholy Blues
Full Release Notes: Google+
Sound: connect/disconnect notification support (with ability to specify tone)
Add option to disable search bar on recents
Heads Up snooze (swipe up on a heads up notification initiates this)
Change default mode of AppOps to make it more reliable
Language translations (Thank you to our great Translators!)
ParanoidOTA: fix inability to download OTAs
Misc Bug Fixes
May 13th, 2015 - Let the Theme Games Begin!
Full Release Notes: Google+
Merge of android-5.1.1_r2 tag from AOSP
Theme Engine support from CM-12.1
Screenshot fixes (NPE and leaks)
Cellular Networks migration (accessible through main settings now)
Mute notification sounds threshold
ParanoidOTA revamp with Material update
Status Bar’s Double Tap to Sleep
Misc Bug Fixes
May 6th, 2015 - The Revenge of the Sixth
Full Release Notes: Google+
First 5.1 release! First 5.x official release on XDA!
The Theme Engine and Quick-Settings reordering will be back soon!
Paranoid OTA updates are not included, but will also be back soon.
Screenshots
Coming soon.
Is this pure aosp, or a cm based rom?
Sent from my LG D850
Spz0 said:
Is this pure aosp, or a cm based rom?
Sent from my LG D850
Click to expand...
Click to collapse
CM-based, but as minimally as possible (just device trees).
It's going to be a LONG time (if ever, honestly) before we see any pure AOSP builds for devices like the G3. CM and it's MASSIVE team of maintainers are pretty much the only people keeping device trees and drivers up-to-date for anything other than Nexus/OnePlus/Opo/Yu.
For the G3, your options are going to be:
An LG/stock based ROM
CM
A ROM that is built using as many AOSP sources as possible, but still includes some CM stuff for device-level code.
Unless LG releases entirely full sources for the device, then the above is always going to be the case.
Edit: Just saw your XDA title and signature, you know all of this haha. Yeah, we're using CM for some device trees, because there's really no way not to.
features or vanilla?
Cryptecks said:
CM-based, but as minimally as possible (just device trees).
It's going to be a LONG time (if ever, honestly) before we see any pure AOSP builds for devices like the G3. CM and it's MASSIVE team of maintainers are pretty much the only people keeping device trees and drivers up-to-date for anything other than Nexus/OnePlus/Opo/Yu.
For the G3, your options are going to be:
An LG/stock based ROM
CM
A ROM that is built using as many AOSP sources as possible, but still includes some CM stuff for device-level code.
Unless LG releases entirely full sources for the device, then the above is always going to be the case.
Edit: Just saw your XDA title and signature, you know all of this haha. Yeah, we're using CM for some device trees, because there's really no way not to.
Click to expand...
Click to collapse
Thank you for explaining why CM is in every single Rom, I came from nexus 4 so I was scratching my head....also is there any known issues other than CM bugs? Correction just re read the OP nevermind
You did it. Omg... Flashing now.
Cryptecks said:
CM-based, but as minimally as possible (just device trees).
...
...
Edit: Just saw your XDA title and signature, you know all of this haha. Yeah, we're using CM for some device trees, because there's really no way not to.
Click to expand...
Click to collapse
Aye got it. Sounds promising. I'll run it through its paces in a week or so. Settling and testing another rom atm.
Good work m8
Sent from my LG D850
i42o said:
You did it. Omg... Flashing now.
Click to expand...
Click to collapse
Spz0 said:
Aye got it. Sounds promising. I'll run it through its paces in a week or so. Settling and testing another rom atm.
Good work m8
Click to expand...
Click to collapse
It would be extremely selfish of me to take full/much credit for this first build. All of that praise should go to bryan2894 and the rest of the AOSPA-L guys. I was committed to other things for a little while and couldn't help as much as I would have liked, but I'm back to it now!
We're excited for what PA and AOSPA-L have to show you guys, just give us a little bit of time to get back into the groove with our changed-up team and get a few more devices brought up. The plan at the moment is to release again early-mid next week, but we shall see how that all goes!
I've just added a link into the first post that is a MUST READ for AOSPA-L users moving forward. Also I added a link to the May 6th changelog on the Official AOSPA-L G+ for further information. Both are also below because they are important to read.
READ THIS FIRST!
Google+
The Legacy of Paranoid Android
May 6th, 2015 - The Revenge of the Sixth
Full Release Notes: Google+
Question on "Known Issue"
Hi,
So I see that you have listed a "Known Issue"
Known Issues
backuptool broken
What is the backuptool used for? is it the same as the TWRP backup?
Coldheat1906 said:
Hi,
So I see that you have listed a "Known Issue"
Known Issues
backuptool broken
What is the backuptool used for? is it the same as the TWRP backup?
Click to expand...
Click to collapse
If you read in the directions, you will see that your Gapps, SuperSU, and stuff on /system/ won't be backed up (like they should be) when you flash over them. It is nothing like TWRP backup, it is simply used for preserving parts of the ROM/Gapps/SuperSU when flashing. It's also something we're working on fixing for the next build.
This first version should really be clean flashed anyway, so it ultimately doesn't matter.
I am devoted to aospa I'm on this ROM now and so far so good. Thank you guys for the build and I will be staying on this rom from now on. If you ever need testers or anything feel free to contact my AIM @ Riflez . AOSPA was more than a ROM it was a movement, and the day I actually followed you guys is when my eyes opened to seeing the amazing job you guys do. Thanks for the inspiration brothers. Thanks @Cryptecks@bryan2984TRY THE ROM OUT GUYS! IT'S SO BUTTERY!!! I LOVE P.A!!!
i42o said:
I am devoted to aospa I'm on this ROM now and so far so good. Thank you guys for the build and I will be staying on this rom from now on. If you ever need testers or anything feel free to contact my AIM @ Riflez . AOSPA was more than a ROM it was a movement, and the day I actually followed you guys is when my eyes opened to seeing the amazing job you guys do. Thanks for the inspiration brothers. Thanks @Cryptecks@bryan2984TRY THE ROM OUT GUYS! IT'S SO BUTTERY!!! I LOVE P.A!!!
Click to expand...
Click to collapse
Ok so CM base minus theming capabilities, various customization, no double tap to sleep, no hold back to kill app....I'm really not trying to be rude but I really don't get it, what am I missing? Are they going to introduce features but in a PA way? Sorry if this is a redundant question. I'm thankful for every contributor in anything open-source more choice= more better Linux rules
noobtxtech said:
Ok so CM base minus theming capabilities, various customization, no double tap to sleep, no hold back to kill app....I'm really not trying to be rude but I really don't get it, what am I missing? Are they going to introduce features but in a PA way? Sorry if this is a redundant question. I'm thankful for every contributor in anything open-source more choice= more better Linux rules
Click to expand...
Click to collapse
Have you never seen a ROM during initial bring-up before? It takes time to add specific features, and we're just getting AOSPA-L off the ground. It's not a redundant question, just rude. If you want to stick with CM, that's fine.
You're not missing anything, you're just here too soon, come back later when we've had more time to work on things, it sounds like you are too invested in other features that CM has.
Theme Engine support is already working on my build there are just a couple of bugs, which we're working on. I would imagine it should be ready for the next build.
Holding back to kill an app is a trivial thing, we can get that added in time, and it's really not a big deal.
DT2 sleep is there, it's just different than CM (which is kind of the point), Settings > Buttons > Double Tap Home (Turn Screen Off)'
This is literally the first build from the AOSPA-L team for the D850, and the fact that it boots and runs smooth should be good enough. Features, customizations, and refinements will come with time. It has taken CM months to get to where they are now, and we don't want to just kang things on top of CM, we're building a proper AOSP/CM blend with only the best parts of CM and additional goodies from the PA and AOSPA-L teams.
Set a Google Inbox reminder to send you this thread in a month or so, you'll like it a lot more then.
thanks
Cryptecks said:
Have you never seen a ROM during initial bring-up before? It takes time to add specific features, and we're just getting AOSPA-L off the ground. It's not a redundant question, just rude. If you want to stick with CM, that's fine.
You're not missing anything, you're just here too soon, come back later when we've had more time to work on things, it sounds like you are too invested in other features that CM has.
Theme Engine support is already working on my build there are just a couple of bugs, which we're working on. I would imagine it should be ready for the next build.
Holding back to kill an app is a trivial thing, we can get that added in time, and it's really not a big deal.
DT2 sleep is there, it's just different than CM (which is kind of the point), Settings > Buttons > Double Tap Home (Turn Screen Off)'
This is literally the first build from the AOSPA-L team for the D850, and the fact that it boots and runs smooth should be good enough. Features, customizations, and refinements will come with time. It has taken CM months to get to where they are now, and we don't want to just kang things on top of CM, we're building a proper AOSP/CM blend with only the best parts of CM and additional goodies from the PA and AOSPA-L teams.
Set a Google Inbox reminder to send you this thread in a month or so, you'll like it a lot more then.
Click to expand...
Click to collapse
This is the answer I was hoping for, I do not wish to stay with CM, yes I've been on the bandwagon for quite a while, the first PA I installed was 4.1 on evo 3d, I have it running on my friends nexus 4 right now (4.4.4) and that build isn't hardly customizable so I was honestly scratching my head on the direction PA has gone because I remember 4.1 being highly customizable..... I honestly tried my best to not sound rude... I'm glad to hear it is headed in this direction.... Nice work !
noobtxtech said:
This is the answer I was hoping for, I do not wish to stay with CM, yes I've been on the bandwagon for quite a while, the first PA I installed was 4.1 on evo 3d, I have it running on my friends nexus 4 right now (4.4.4) and that build isn't hardly customizable so I was honestly scratching my head on the direction PA has gone because I remember 4.1 being highly customizable..... I honestly tried my best to not sound rude... I'm glad to hear it is headed in this direction.... Nice work !
Click to expand...
Click to collapse
No worries, I was also a bit annoyed at work things earlier and should have probably chosen my words better when typing.
CM will continue to do what they do, add/remove/break things at an extremely fast pace.
Our AOSPA-L team wants to start off with a very solid base, and then build our new ideas on top of that (trust me, some of the ideas, people will love).
sounds legit
Cryptecks said:
No worries, I was also a bit annoyed at work things earlier and should have probably chosen my words better when typing.
CM will continue to do what they do, add/remove/break things at an extremely fast pace.
Our AOSPA-L team wants to start off with a very solid base, and then build our new ideas on top of that (trust me, some of the ideas, people will love).
Click to expand...
Click to collapse
I'll keep a eye on this thread
This build is fluid bro! AWESOME JOB TO BOTH OF YOU GUYS. BATTERY LIFE IS SUPERB!
And to those who are iffy about this ROM,
The OP did say it'll be even better by next month,
With features that people will love.
Take your time and lets transition into the new PA together
#stayparanoid
i42o said:
This build is fluid bro! AWESOME JOB TO BOTH OF YOU GUYS. BATTERY LIFE IS SUPERB!
And to those who are iffy about this ROM,
The OP did say it'll be even better by next month,
With features that people will love.
When has a new ROM dev ever given an expected time for new awesome features?
Take your time and lets transition into the new and refined PA together.
Click to expand...
Click to collapse
Haha thanks. Don't hold me to any timelines haha, but you can get an idea of some (public) things we're working on by checking Gerrit.
This is the most excited I've been with the G3 since the first lollipop ROMs were released! pa is the leaders of the ROM community for bringing new and innovative features that nobody else has. I'm very excited to see what you guys have in store!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am proud to present to you BeanStalk Builds put together by myself. This is a build composed off of the CM builds and i have added alot of features on top of it. So you get speed, stability, and ultra customization ability. Many of the additional code additions came from slim ROM and also Derteufels build and have been modified to work with my current setup. A huge thanks to Derteufel and the Slim ROM guys for their work and dedication. Also a big thanks to everyone involved with CM as that is the building stone in this project. Thanks to skyliner33v for the bootanimation and upcoming wallpapers!
I plan on updating this and adding features on a pretty regular basis, so if you happen to like this, keep checking back.
Like what you see? Click the thanks button or Donate to scott.hart.bti by clicking HERE
Interested in Porting/Building BeanStalk on another device? Check out Post #3!
If you have building/development concerns or issues, Please visit the BeanStalk Development Thread to avoid cluttering this thread.
CM based
Lockscreen background options (Color fill, Custom image, Transparent)
Customizable Lockscreen text color
Lockscreen rotation
Option to enable all widgets
Minimize lockscreen challange
Use widget carousel
Slider Shortcuts
Static Lockscreen shortcuts
Lockscreen button actions
LCD Density
Scroll elasticity options
Default App grip option
Custom Carrier label
Dual Pane options
Customizable boot animation (off, default, set your own bootanimation)
Custom original BeanStalk Wallpapers by skyliner33v
Custom BeanStalk bootanimation by skyliner33v
Status bar color and transparency
Clock and date options which includes color, location, style
Signal Styles which include color and text instead of icons, alternate GB signal layout, hide signal icons
Breathing SMS option
Battery styles - Includes specific colors and styles. Also includes battery bar
Do not disturb option
Show notification count
Pie controls (need to have lockscreen background set to something other then default to work correctly (dont ask why) )
Fully customizable navigation bar - Includes style, layout, color, nav rings, pretty much everything you can think of.
Quick settings color settings, tiles per row, Quick pulldown, text color
Notification shortcuts, behaviour, drawer style (customizable colors), toggle colors, longpress quicksettings icon to enable/disable toggles
Keyboard and input method options which include disable full screen keyboard and auto rotate
Kill app back button with customizable timeout values
High end graphic effects option
option to disable/enable vibrate on expand for notifications alerts
Low battery warning customizable options
Recents RAM bar fully customizable with color styles
Clock widget for LockClock including extra options to fully customize every feature of the lockclock
Build.prop MOD options to enable/disable tweaks as preferred
Less frequent Notification sounds options
CRT screen off/on options to specify how the animation shows
Enable/disable wake up on charge option
Superuser fully embedded into the build and accessed from settings menu
CM Performance options and features
About BeanStalk option with links to github source and facebook for beanstalk. Also links to my twitter and donate.
insane amount of edits/tweaks/fixes to make this build absolutely fly
option to use a fully themable MMS packages. You can access from mms - settings - theme settings
Numerous other options hidding throughout the build
FC's! Missing drawables might cause random FC's here and there. Please get me a logcat, or at least post the exact steps that'd reproduce the problem
Find one suitable, yourself; and post here if it works
***For a complete listing of all supported BeanStalk devices and downloads, please visit www.goo.im/devs/beanstalk***
***Our device isn't supported, so downloads are below***
BeanStalk Build 4.4.240 - 11/Feb/14: http://forum.xda-developers.com/showpost.php?p=50231646&postcount=16
BeanStalk Build 4.4.215 - 12/Jan/14: http://www.mediafire.com/download/28jz5zfjtfs3mg2/BeanStalk-4.4.215-20140112-pico.zip
***Please keep in mind that this is the initial release and bugs are to be expected. Before reporting bugs, please make sure you verify everything on your end and make sure you do a full wipe and format first to make sure it is a legitimate issue. Im going to say this once and only once... I am doing this for fun. It is my CHOICE to share my work with everyone. If you decide that you do not like my work, good for you.. Move on and flash something else. I will not tolerate ungrateful people in my thread.***
Copy ROM,
Reboot into Recovery,
Factory Reset,
Flash ROM,
Reboot.
SlimROM source can be found HERE
DerTeufel's source can be found HERE
My source can be found HERE
Donate to scott.hart.bti by clicking HERE
Click to expand...
Click to collapse
XDA:DevDB Information
[ROM][KitKat][4.4.2][Unofficial]BeanStalk Build 4.4.215 - Updated 12/Jan/2013, a ROM for the HTC Pico (Explorer)
Contributors
thewisenerd
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-01-12
Created 2014-01-12
Last Updated 2014-02-11
Reserved
This is constantly changing. Please read this here: http://forum.xda-developers.com/showpost.php?p=48122087&postcount=2
Reserved
Yeah, I've been seeing gradual decreasing support for MDPI devices. Hopefully I'd be adding back most of the 'resized' drawables (which would fix any FC's that you might face), but till then, please stay put (or gimme a hand in resizing them drawables )
Also, I've fixed up two lines in BoardConfig.mk (thanks to galaxyfreak), which might have been causing the "Can't connect to camera" error randomly.
And, reverted back two commits in kernel disabling lpa audio. in case lpa audio was causing the call issue
Anyways, this is a discussion thread. Please feel free to report such issues.
Rom & gapps can be on nand? I don't wanna use any script on startup. I just use mount2sd & move App+dalvikvm but not the data of the apps for speed purposes.
Btw I'm once again hoping great work from your side. :good:
Sent from my HTC Explorer A310e using Tapatalk
Awesome work mate! :victory: :good: but it would be nice if you post details about what works and what doesnt! cause i seriously wanna download this!!
ateeq72 said:
Awesome work mate! :victory: :good: but it would be nice if you post details about what works and what doesnt! cause i seriously wanna download this!!
Click to expand...
Click to collapse
yes ! please do so homie!
yo man! i respect ur work! i honestly do! but how about releasing 1 rom , fixing it fully , making it fully stable and then releasing another homie ? u have released sooooo many roms recently but all are buggy man! whats the use ? i appreciate ur hard work bro but wudnt it be nice to fix the bugs of the roms u have already released and making them fully stable instead of just releasing more and more buggy roms ? no offence meant though man! trust me I RESPECT YOUR WORK! :good::highfive:
NeoTrix said:
yo man! i respect ur work! i honestly do! but how about releasing 1 rom , fixing it fully , making it fully stable and then releasing another homie ? u have released sooooo many roms recently but all are buggy man! whats the use ? i appreciate ur hard work bro but wudnt it be nice to fix the bugs of the roms u have already released and making them fully stable instead of just releasing more and more buggy roms ? no offence meant though man! trust me I RESPECT YOUR WORK! :good::highfive:
Click to expand...
Click to collapse
same opinion with u。Number is not so important in roms as a fixed quality rom.
wish author's work become better and better.
wsdyleon said:
same opinion with u。Number is not so important in roms as a fixed quality rom.
wish author's work become better and better.
Click to expand...
Click to collapse
I agree with yu both... Bt these bugs may take a lot of time to solve...
And users can try different roms instead asking ETAs and all and each have its own features... Am not opposing anyone... Just telling what i feel.. :thumbup:
And gud luck bro... Love your work bro.. . Pico now got a lot 4.4 roms..
NeoTrix said:
yo man! i respect ur work! i honestly do! but how about releasing 1 rom , fixing it fully , making it fully stable and then releasing another homie ? u have released sooooo many roms recently but all are buggy man! whats the use ? i appreciate ur hard work bro but wudnt it be nice to fix the bugs of the roms u have already released and making them fully stable instead of just releasing more and more buggy roms ? no offence meant though man! trust me I RESPECT YOUR WORK! :good::highfive:
Click to expand...
Click to collapse
Ok, let's quote scott.hart.bti here.
I am doing this for fun. It is my CHOICE to share my work with everyone. If you decide that you do not like my work, good for you.. Move on and flash something else. I will not tolerate ungrateful people in my thread.
Click to expand...
Click to collapse
I remember my first work, around 7 months ago, which I released on XDA (before that I was just working on some random tools, scripts and stuff, making custom themed CM ROMs, naming them "Zeta ROM" etc), which was Cyanic Sense. Before that I had my first experience "making" a kernel. It took 40 minutes on my pre-pentium 4 processor. I remember Rishik999 who I worked with. I remember releasing a flashable zip for the Stock ROM v1.43.720.2 with the combined efforts of me, rishik and racerroney, with help from explorerman.
Back to cyanic sense, Though it was just theming, it was difficult, for I didn't know where to start. I quit that, because of two reasons.
1. stock, was buggy, and slow.
2. there wasn't any "real" developing that I was doing.
2.5. I had got a new computer, so, no longer did I have to wait for ~40 minutes to get a kernel compiled.
Now, looking back to about two months ago. The end of october. Cyanogenmod ICS was the first ROM that I compiled, just to test the specs of my pc, build times, etc. Still, I was making builds at the rate of a build per hour and half, or so. Looked at MiniCM, there was great potential in there, for it. I was starting to learn things.
MiniCM was THE greatest project (IMO, until now) ever that I worked on, that I can be proud of (till this day), just because I did it, and It was my first work. No matter, I decided to "stabilize" the ICS ROM with k3.0.101. I remember that day, when @rcane had released a flashable s2w zip update for it on the thread. I flashed it, didn't work. Decided to make it work, and voila! That was the first build, with very few changelog.
First, started out with cherry-picking, (too many of them), most useful ones had been abandoned by them cm-gerrit, just because ICS was outdated. decided to create repos, and implement some real useful features into ICS, making it "rock stable", and stuff as you'd say it. User suggestions started flowing in (those who did care for ICS). Had a hard time keeping up with all the features that the users requested (not many, as only a few used ICS). I wasn't able to fix up all their requests, but still... Anyways, I was still learning. Collaborated with Umair (omerjerk), and went on to add toggles and stuff... Finally, went on to create CodyROM, (with some more great collab, with Vaibhav (#Superuser), and Dhruman (dhrumangajjar)) just because of two things:
1. It was over with the MiniCM brand name, as it limited my functionality.
2. Users really didn't think any different of MiniCM, and i was just the guy, providing builds, and they neither do that now, either.
I also did a few builds of cm10, cm10.2, but never really released them. just because there wasn't anything that I added or so :\
Did anyone bother? Nope. Except the ones who used ICS? Nope. Did I bother? Nope. Because I knew I was outdated, and Kitkat had released too, so none really bothered. Did I care? No. Because I was learning. That project gave me both the headstart and confidence, experience and a little knowledge about the android build system.
Without it, I wouldn't be what I am today.
Finally, went from "I" to "we". Then, there was quite a some pressure from "people" regarding, "ICS is outdated", "move on", and so on...
So, decided to work on my first kitkat ROM, Omni. Thanks to the experience that I gained from MiniCM, and CodyROM, I was able to get it booted at first attempt (using the really outdated device tree at picokat) (the tree's still the same way).
Ok, so Kitkat booted. Problems: audio not routing. RIL didn't work. black screen in browser. dang outdated, because pico was using ION. and mainly: incompatibility of sources. AOSP doesn't simply make sources compatible. Even now, for CM, we use a hacked display-legacy, media-legacy, and frameworks/av. hoepfully, there were certain commits in the gerrit of omni, that helped me along the way. I'd like to thank sachin thomas for helping me get ION booted in pico, and cute_prince for enabling ION in the pico kernel. This fixed some of the issues. Also, few others like Nihar, and galaxyfreak helped, and RIL, camera working. That was Omni, for Pico. That was the ever first release of TeamCody, in kitkat.
At this point, i'd take a timeout to say how the ROMs itself are made:
First they add the features (keeping in mind to add compatibility later)
ROMs are compatible for nexus, voila! great! bravo!
And, at some point of time, it slips out of their mind that they have to add compatibility too.
One common example of it would be missing drawables. When adding new featues, mostly these are tested in XHDPI devices, like the Nexus? So, another problem faced: I really wouldn't know what's missing, until I boot the ROM, and get hell lot of FC's.
Meanwhile, ROMs were releasing in the Development section. Ported ROMs. I was never with the idea of ported ROMs, because I have a blind belief that ROMs built for the device would be stabler, and bugs can be more easily fixed that way. (not that I don't use ported ROMs. I do use them, in cases inevitable, or when I don't be able to build them from source)
So, decided to make them ROMs, so that I could fix bugs, along the way, thus helping the community back, and in the course, learning more. If you'd have seen, Carbon, AOSPA, Beanstalk, AOKP was already ported. I'd done only Evervolv, and Omni.
AOKP was a request by Amal, who said that he couldn't get AOKP booted with ION by porting... Evervolv, I did it for the legacy support (they're teh best at that). Beanstalk, I had a strong feeling to get this one done. because of the customizations available. Carbon, had to be done, because its another great ROM. Omni, was my wish to do.
Now, there's one thing that *most* of the custom ROMs lack today. Legacy support. I decided to use AOSPA-legacy repos, just because one can't build from the official AOSPA repos for older hardware. its built FOR nexus. Carbon, NVM, had a tough time cherry-picking commits. AOKP, was equally difficult. Omni, please. They said that legacy support would be their prime aim. now, all that vanished into thin air.
On the other hand, Cyanogenmod, says you. Great! Functionality at its best! Reason: solid legacy support! legacy support at its best. ALL phones are likely supported. You just need to hack device specific repos that are hardware oriented like media-legacy, display-legacy, and frameworks/av to get it working. Its easy to just sync the cm repos, and make fully booting, working ROMs, "without any bugs", as you say.
But, that's not the case with all other ROMs, both cm-derived and otherwise.
It takes time to find, merge support for legacy devices like ours.
It takes time to find missing drawables.
It takes time to hash out all changes that are "device specific" breaking builds, or so.
It takes time for me to build kitkat. 3 hours, for the first compile, with ccache, and a hour and half the next time. Not to mention, 3 hours, if the build doesn't break. and the build doesn't boot? then, derp around with frameworks, and hardware repos a bit more to find why it doesn't work, and how to get it working.
I don't have a build server that churns out builds every half an hour, so that I can test it, rebuild with fixes.
Beanstalk's frameworks/av was almost not synced with CM's for the past few days.
Also, Beanstalk had missing drawables, as said earlier, just like Carbon did. Sorry, if it seems like I'm repeating stuff.
And yes, users seem to be very very biased to names, ROms, and otherwise.
Cyanogenmod, yes. A build by a "recognized person", yes. I remember joilaroi, the person who was responsible to making a very stable cm-10.2, was first recieved with "doubt" when he said that he'd fixed them bugs.
Ok, this post's gone too far. Spoke too much.
I ain't saying that I am a great developer or anything. The real great people are the poeple who work on the ROMs, and its features. I am still learning stuff. just that it's taking too much of a toll on me, my health, and my academic life.
I've still got a lot to learn, and won't be *not* doing it, just because people say so.
Finally, I quote scott again.
I am doing this for fun. It is my CHOICE to share my work with everyone. If you decide that you do not like my work, good for you.. Move on and flash something else. I will not tolerate ungrateful people in my thread.
Click to expand...
Click to collapse
Don't like what I said? Go on, report this post. Report me. Just to let you know, that I don't give a damn.
so long the post。Thnak u 4 your efforts first，and then your work。
some people ask for the roms to be fixed mainly because they like it，with eager。
they can ask for the work，but cannnot ask u to do the work。
if tired，just take a break。
it is really a outdate device，but it has to be the goood one with the effort of “the android masters” 。
it is a miracle itself just for the Roms。Thanks for all people who work hard on it。
---------- Post added at 02:22 PM ---------- Previous post was at 02:13 PM ----------
sorry for my poor english
wsdyleon said:
same opinion with u。Number is not so important in roms as a fixed quality rom.
wish author's work become better and better.
Click to expand...
Click to collapse
NeoTrix said:
yo man! i respect ur work! i honestly do! but how about releasing 1 rom , fixing it fully , making it fully stable and then releasing another homie ? u have released sooooo many roms recently but all are buggy man! whats the use ? i appreciate ur hard work bro but wudnt it be nice to fix the bugs of the roms u have already released and making them fully stable instead of just releasing more and more buggy roms ? no offence meant though man! trust me I RESPECT YOUR WORK! :good::highfive:
Click to expand...
Click to collapse
thewisenerd said:
Ok, let's quote scott.hart.bti here.
I remember my first work, around 7 months ago, which I released on XDA (before that I was just working on some random tools, scripts and stuff, making custom themed CM ROMs, naming them "Zeta ROM" etc), which was Cyanic Sense. Before that I had my first experience "making" a kernel. It took 40 minutes on my pre-pentium 4 processor. I remember Rishik999 who I worked with. I remember releasing a flashable zip for the Stock ROM v1.43.720.2 with the combined efforts of me, rishik and racerroney, with help from explorerman.
Back to cyanic sense, Though it was just theming, it was difficult, for I didn't know where to start. I quit that, because of two reasons.
1. stock, was buggy, and slow.
2. there wasn't any "real" developing that I was doing.
2.5. I had got a new computer, so, no longer did I have to wait for ~40 minutes to get a kernel compiled.
Now, looking back to about two months ago. The end of october. Cyanogenmod ICS was the first ROM that I compiled, just to test the specs of my pc, build times, etc. Still, I was making builds at the rate of a build per hour and half, or so. Looked at MiniCM, there was great potential in there, for it. I was starting to learn things.
MiniCM was THE greatest project (IMO, until now) ever that I worked on, that I can be proud of (till this day), just because I did it, and It was my first work. No matter, I decided to "stabilize" the ICS ROM with k3.0.101. I remember that day, when @rcane had released a flashable s2w zip update for it on the thread. I flashed it, didn't work. Decided to make it work, and voila! That was the first build, with very few changelog.
First, started out with cherry-picking, (too many of them), most useful ones had been abandoned by them cm-gerrit, just because ICS was outdated. decided to create repos, and implement some real useful features into ICS, making it "rock stable", and stuff as you'd say it. User suggestions started flowing in (those who did care for ICS). Had a hard time keeping up with all the features that the users requested (not many, as only a few used ICS). I wasn't able to fix up all their requests, but still... Anyways, I was still learning. Collaborated with Umair (omerjerk), and went on to add toggles and stuff... Finally, went on to create CodyROM, (with some more great collab, with Vaibhav (#Superuser), and Dhruman (dhrumangajjar)) just because of two things:
1. It was over with the MiniCM brand name, as it limited my functionality.
2. Users really didn't think any different of MiniCM, and i was just the guy, providing builds, and they neither do that now, either.
I also did a few builds of cm10, cm10.2, but never really released them. just because there wasn't anything that I added or so :\
Did anyone bother? Nope. Except the ones who used ICS? Nope. Did I bother? Nope. Because I knew I was outdated, and Kitkat had released too, so none really bothered. Did I care? No. Because I was learning. That project gave me both the headstart and confidence, experience and a little knowledge about the android build system.
Without it, I wouldn't be what I am today.
Finally, went from "I" to "we". Then, there was quite a some pressure from "people" regarding, "ICS is outdated", "move on", and so on...
So, decided to work on my first kitkat ROM, Omni. Thanks to the experience that I gained from MiniCM, and CodyROM, I was able to get it booted at first attempt (using the really outdated device tree at picokat) (the tree's still the same way).
Ok, so Kitkat booted. Problems: audio not routing. RIL didn't work. black screen in browser. dang outdated, because pico was using ION. and mainly: incompatibility of sources. AOSP doesn't simply make sources compatible. Even now, for CM, we use a hacked display-legacy, media-legacy, and frameworks/av. hoepfully, there were certain commits in the gerrit of omni, that helped me along the way. I'd like to thank sachin thomas for helping me get ION booted in pico, and cute_prince for enabling ION in the pico kernel. This fixed some of the issues. Also, few others like Nihar, and galaxyfreak helped, and RIL, camera working. That was Omni, for Pico. That was the ever first release of TeamCody, in kitkat.
At this point, i'd take a timeout to say how the ROMs itself are made:
First they add the features (keeping in mind to add compatibility later)
ROMs are compatible for nexus, voila! great! bravo!
And, at some point of time, it slips out of their mind that they have to add compatibility too.
One common example of it would be missing drawables. When adding new featues, mostly these are tested in XHDPI devices, like the Nexus? So, another problem faced: I really wouldn't know what's missing, until I boot the ROM, and get hell lot of FC's.
Meanwhile, ROMs were releasing in the Development section. Ported ROMs. I was never with the idea of ported ROMs, because I have a blind belief that ROMs built for the device would be stabler, and bugs can be more easily fixed that way. (not that I don't use ported ROMs. I do use them, in cases inevitable, or when I don't be able to build them from source)
So, decided to make them ROMs, so that I could fix bugs, along the way, thus helping the community back, and in the course, learning more. If you'd have seen, Carbon, AOSPA, Beanstalk, AOKP was already ported. I'd done only Evervolv, and Omni.
AOKP was a request by Amal, who said that he couldn't get AOKP booted with ION by porting... Evervolv, I did it for the legacy support (they're teh best at that). Beanstalk, I had a strong feeling to get this one done. because of the customizations available. Carbon, had to be done, because its another great ROM. Omni, was my wish to do.
Now, there's one thing that *most* of the custom ROMs lack today. Legacy support. I decided to use AOSPA-legacy repos, just because one can't build from the official AOSPA repos for older hardware. its built FOR nexus. Carbon, NVM, had a tough time cherry-picking commits. AOKP, was equally difficult. Omni, please. They said that legacy support would be their prime aim. now, all that vanished into thin air.
On the other hand, Cyanogenmod, says you. Great! Functionality at its best! Reason: solid legacy support! legacy support at its best. ALL phones are likely supported. You just need to hack device specific repos that are hardware oriented like media-legacy, display-legacy, and frameworks/av to get it working. Its easy to just sync the cm repos, and make fully booting, working ROMs, "without any bugs", as you say.
But, that's not the case with all other ROMs, both cm-derived and otherwise.
It takes time to find, merge support for legacy devices like ours.
It takes time to find missing drawables.
It takes time to hash out all changes that are "device specific" breaking builds, or so.
It takes time for me to build kitkat. 3 hours, for the first compile, with ccache, and a hour and half the next time. Not to mention, 3 hours, if the build doesn't break. and the build doesn't boot? then, derp around with frameworks, and hardware repos a bit more to find why it doesn't work, and how to get it working.
I don't have a build server that churns out builds every half an hour, so that I can test it, rebuild with fixes.
Beanstalk's frameworks/av was almost not synced with CM's for the past few days.
Also, Beanstalk had missing drawables, as said earlier, just like Carbon did. Sorry, if it seems like I'm repeating stuff.
And yes, users seem to be very very biased to names, ROms, and otherwise.
Cyanogenmod, yes. A build by a "recognized person", yes. I remember joilaroi, the person who was responsible to making a very stable cm-10.2, was first recieved with "doubt" when he said that he'd fixed them bugs.
Ok, this post's gone too far. Spoke too much.
I ain't saying that I am a great developer or anything. The real great people are the poeple who work on the ROMs, and its features. I am still learning stuff. just that it's taking too much of a toll on me, my health, and my academic life.
I've still got a lot to learn, and won't be *not* doing it, just because people say so.
Finally, I quote scott again.
Don't like what I said? Go on, report this post. Report me. Just to let you know, that I don't give a damn.
Click to expand...
Click to collapse
yo man! u goota chill ur bals! I LOVE UR WORK! trust me im currently on ur omni rom as there are almost NO BUGS! just few minor sh*i*t! i really wanted to try all ur roms! u kept on releasing and i kept thinking that u wer fixing! though its not my job to tell u wat to do! u have released so many roms and ure learning ! real good ! really good for our phones ! because of ppl like im running android 4.4 which i never though wud be possible! the thing is the rom u r releasing are great ! awsum features but they are buggy! u can port as many u want but if u fix we can all use them as daily driver mate! u r not getting my point! i didnt mean to offend u homie! its just that if u can fix the current roms u released , everyone can try it and enjoy the features which u WORKED HARD to give us! but as it is buggy so many ppl dont try it! they wait n wait for ur fixes! in the end ! ur pc , ur time u do what u want! it was just a suggestion mate! not only mine , but almost everyone thinks the same! and chill man! ur roms are great! cheers :good:
the rom is too buggy , mp3 files doesn't play in any players , then the call distortion bug ,
thats it other than that this is an awesome and smooth rom
pls fix it...
:good:
Call audio Bug fix
Download patch_callaudio.zip from this post: http://forum.xda-developers.com/showpost.php?p=49483706&postcount=23
This should fix the "user at other end not able to hear your voice properly" bug
If it doesn't work, reboot once?
p.s. This *should* be flashable on all of my kitkat ROMs, but I need testers for them all.
Hey @thewisenerd these are some bugs I faced in this rom
1. Okay frankly speaking the ROM is damn laggy I know cuz of many customization options.
2. Video recording not working ( I didn't use the cam fix cuz u said it deteriorate the image quality )
3. When playing the video in hw mode the video controls disappear but video plays fine and in sw mode everything is good
4. Sometimes the Google play music doesn't play music after reboot but other music players work just fine
5. Screen recording gives reboot
Other than this the rom good for those who love customizations but can do with a lag
I hope you update this rom soon
Sent from my Explorer A310e using XDA Premium 4 mobile app
BETA 2
electron.hTcpico said:
Hey @thewisenerd these are some bugs I faced in this rom
1. Okay frankly speaking the ROM is damn laggy I know cuz of many customization options.
2. Video recording not working ( I didn't use the cam fix cuz u said it deteriorate the image quality )
3. When playing the video in hw mode the video controls disappear but video plays fine and in sw mode everything is good
4. Sometimes the Google play music doesn't play music after reboot but other music players work just fine
5. Screen recording gives reboot
Other than this the rom good for those who love customizations but can do with a lag
6.I hope you update this rom soon
Click to expand...
Click to collapse
1. idk why or how, but might be due to its laarge size and many many features
2. dunno why
3. upstream derp
4. idk... apollo's working fine
5. screen recording ain't completely supported for our phone yet.
6. see below:
Beta 2:
Changelog:
upstream changes
fixed apollo
fixed in call audio
fixed games
fixed memtrack spam in logcat
fixed some other randome shiz (see, i don't really remember all of it now )
bugs:
video recording doesn't work (lemme first find a way to get logs first)
see, the motive of this forum si that people report bugs, and there's interaction. this is a forum. not a place where one just keeps talking to themselves. if ain't gonna get bug reports/logs, that bug is probably not going to be fixed. also, know about the kind of bug. if its an upstream bug, probably just wait for them to fix the bug.
notable upstream changes:
multiwindow, anyone? (though ain't much useful on a 3.2" screen, helsp to show off )
Download: http://www.mediafire.com/download/114jwz3vydokqkb/BeanStalk-4.4.240-20140211-pico.zip
Also note: Beanstalk 4.4.247 is out. Haven't recieved any bug reports, so, don't expect any bug fixes.
i can t wait omni build so i flash this.now i am feeling beanstalk is :good: thank you thewisenerd
but any solutuon to install googleplay.. etc ? and can we flash a kernel with swep2wake on this rom**(i dont know what i say :silly: but thanks your effort to understanding me )
last question can we flash cm10 apps i mean (Xperia 'lockscreen http://forum.xda-developers.com/showthread.php?t=2200706') in theese 4.4.x roms ......
sorry about lot of grammer killing but i wonder recent app switcher change ? is it possible (http://forum.xda-developers.com/showthread.php?t=2197272 theese switcher is different but i am only curious and dreamer :cyclops: thank you and all of xda for 4.4 revolution :highfive:
XenoMorphv2 said:
i can t wait omni build so i flash this.now i am feeling beanstalk is :good: thank you thewisenerd
but any solutuon to install googleplay.. etc ? and can we flash a kernel with swep2wake on this rom**(i dont know what i say :silly: but thanks your effort to understanding me )
last question can we flash cm10 apps i mean (Xperia 'lockscreen http://forum.xda-developers.com/showthread.php?t=2200706') in theese 4.4.x roms ......
sorry about lot of grammer killing but i wonder recent app switcher change ? is it possible (http://forum.xda-developers.com/showthread.php?t=2197272 theese switcher is different but i am only curious and dreamer :cyclops: thank you and all of xda for 4.4 revolution :highfive:
Click to expand...
Click to collapse
Slimmer the ROM, somehow, and flash GApps :cyclops:
It already has a Sweep2Wake kernel (?).
Yes, you may. But I ain't responsible for anything that happens.
^Same as above.
You're welcome.
thewisenerd said:
Slimmer the ROM, somehow, and flash GApps :cyclops:
It already has a Sweep2Wake kernel (?).
Yes, you may. But I ain't responsible for anything that happens.
^Same as above.
You're welcome.
Click to expand...
Click to collapse
thanks to reply but i cant find any options to enable sweep2wake ?
how to enable that feature ? sorry for my noobism :silly:
Thread closed.
Someone else interested in continuing this, please PM me. Thread would be reopened, and ownership transferred.
What is NamelessROM?
What is NamelessROM ?
Simple - NamelessROM is opportunity.
An opportunity to have a voice to the development team of the after-market firmware that you run on your device.
The main goal of NamelessROM is to provide quality development for android devices, phones and tablets alike.
NamelessROM developers are available nearly 24/7 and respond to bug reports and feature requests almost instantly.
This availability will allow you, the end-user, to have direct input into exactly what features and functions are included on the firmware that YOU run.
NamelessROM maintains features and functions of several well-known open-source, AOSP-based ROMs, as well as many features of our own. See the screenshots in the 3rd post, and visit our website for more detailed information.
NamelessROM = endless possibilities. Unless you have an iPhone, then you're out of luck.
Click to expand...
Click to collapse
NamelessROM Gerrit Review
NamelessROM Youtube
For video reviews and stuff :highfive:
ANNOUNCEMENT: We are looking for Device Maintainers to expand our support, please visit our IRC channel or PM @jakew02, @Evisceration or @jumoog for information
Disclaimer
#include <std_disclaimer.h>
*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
*/
Click to expand...
Click to collapse
Got a bug report? Want to request a feature? Need extended support?
NamelessROM Forums
http://NamelessROM IRC
Or from your IRC client:
Server: irc.freenode.net
Channels: General Discussion - #namelessrom
Development Discussion - #namelessrom-dev
Installation Instructions
FROM OTHER ROMS
Factory Reset/Wipe Data
Format System
Format Dalvik Cache
Install ROM
Install Gapps
Reboot
Profit
UPDATE FROM NamelessROM TO NEWER RELEASE
Just download the zip and flash it. You will NOT need to wipe anything.
OTA Updater is work in progress and will be available soon!
Click to expand...
Click to collapse
Downloads
ROM:
jflte
Gapps:
Banks Gapps
Click to expand...
Click to collapse
ExtrasSoundPackages for AudioThemes
courtesy XplodWild's thread
ZOOPER WIDGET template from Screenshots
Made by @jakew02
Click to expand...
Click to collapse
Contributions and Credit
CyanogenMod
OmniROM
AOKP
SlimROMs
AOSPA
Android/Google/AOSP
ALL OF OUR AWESOME TESTERS
Click to expand...
Click to collapse
Source
NamelessROM Source
Click to expand...
Click to collapse
here
Features List
NamelessROM Proprietary Features
NamelessROM Setup Wizard (replaces Google SetupWizard)
DeviceControl App - Allows for device-specific customizations
NamelessROM OTA Update Center
Fully Integrated KitKat White UI Theme
Advanced Device Information in Settings -> About Phone
Interface Features
DarkToggle - TRDS
Animation Control
Custom Battery Icon Settings
Center Clock Setting
Custom Carrier Label
Signal Icon Settings
Network Activity Indicator
Network Speed Indicator
Notification Count in StatusBar
Double-Tap StatusBar to Sleep
Theme Chooser
Recents RAM Bar
Configurable / Hide-able ClearAll Button in Recents
Screen-Off Animations
Notification Drawer Features
BrightnessSlider in Notification Drawer (see screenshots - like Stock ROMs)
Contextual Notification Panel Headers (notification header background image changes based on time of day)
Auto-Close Notification Drawer
Notification Drawer / Notification Transparency Settings
CM QuickToggles and Ribbons
Lockscreen Features
Lockscreen Notifications
Lockscreen See-Through
QuickUnlock for PIN/Password Security Lockscreens
Battery Level Around UnlockRing
Carousel Animation for Lockscreen Widgets
Custom Lockscreen Widgets
Sound Features
Audio Themes - (will be grayed out until SoundPackages are placed in proper directory on SD Card!!!)
QuietHours
Charging Sounds
Dialer Features
Non-Intrusive InCallUI
Flip to Mute / Flip to Reject Incoming Call
Send Incoming Call to NotificationDrawer/StatusBar
Reverse Lookup
Nearby Location Search within Dialer (like GoogleDialer)
Button Features
Music Playback Control (long-press volume buttons to skip music tracks)
Reorient Volume Buttons on rotation
Keyboard Cursor Control with Volume Buttons
Volume Button Wake
Screenshot / Screenrecord PowerMenu options
Click to expand...
Click to collapse
screenshots 02/04/2014
jakew02 said:
reserve2
Click to expand...
Click to collapse
interesting... Is this CM based ? Omni ? I have to say I'm confused
Nice to see you Jake, looking forward to a test drive but right now the download takes me to a survey
hednik said:
interesting... Is this CM based ? Omni ? I have to say I'm confused
Click to expand...
Click to collapse
we are currently using a CM base but have made major modifications to it, proprietary NamelessROM stuff as well as several features from other AOSP roms such as OmniROM, AOKP, Slim, etc.
PapaMag said:
Nice to see you Jake, looking forward to a test drive but right now the download takes me to a survey
Click to expand...
Click to collapse
i'll fix that, i was between classes when i posted and didn't have time to revise it -- doing that now..
jakew02 said:
we are currently using a CM base but have made major modifications to it, proprietary NamelessROM stuff as well as several features from other AOSP roms such as OmniROM, AOKP, Slim, etc.
i'll fix that, i was between classes when i posted and didn't have time to revise it -- doing that now..
Click to expand...
Click to collapse
Got it, going to flash and take a look now
Thanks
jakew02 said:
we are currently using a CM base but have made major modifications to it, proprietary NamelessROM stuff as well as several features from other AOSP roms such as OmniROM, AOKP, Slim, etc.
i'll fix that, i was between classes when i posted and didn't have time to revise it -- doing that now..
Click to expand...
Click to collapse
You should build a pacman like Rom. With all the features of everything from everywhere
Right now I am impressed with what I see. As far as performance this Kat is the best benchmark I have logged on 4.4. I like the customization so far, would like to see a few more options with the buttons such as power off etc. Battery seems to be very stable and holding steady. Rom is nice and smooth.
Guess I'll have to come up with a new signature banner
Could you please post a list of features included in the ROM somewhere? I can't seem to find one on your site or its forums, unless I missed something.
Make a backup and flash it to see...works every time
Sent from my SGH-I337 using XDA Premium 4 mobile app
Tryer1234 said:
Could you please post a list of features included in the ROM somewhere? I can't seem to find one on your site or its forums, unless I missed something.
Click to expand...
Click to collapse
look at post #2 jake may add more features later. but that is a good start for now.
@jakew02 Just so I understand correctly...the reason that flashing custom kernels on Nameless and Omni causes display issues is because the Omni kernel has components that the CM kernel does not have? Or is it the other way around? I love both Omni and Nameless, but I also am attached to my custom kernels lol.
Is there one particular thing in the framework that depends on having the Omni kernel? Ie is there a certain thing I could pull from the Omni kernel and use to kang the custom CM-based kernels to be fully compatible?
I do know that the KT Kernal doesn't marry up well, had to reflash after flashing it. Just wanted to try it to compare, and now I know the rest of the story
only issue i've come across is the battery icon. Upon reboot, i lose the circle battery with %. I have to toggle the option that enables percentage display and the circle icon reappears.
Otherwise, everything else is good so far!
thanks a lot!
CPA Poke said:
@jakew02 Just so I understand correctly...the reason that flashing custom kernels on Nameless and Omni causes display issues is because the Omni kernel has components that the CM kernel does not have? Or is it the other way around? I love both Omni and Nameless, but I also am attached to my custom kernels lol.
Is there one particular thing in the framework that depends on having the Omni kernel? Ie is there a certain thing I could pull from the Omni kernel and use to kang the custom CM-based kernels to be fully compatible?
Click to expand...
Click to collapse
the problem with the custom kernels, ie with ktoonsez's kernel, is that he's updated the kernel-side drivers to the Flo adreno stuff, but we aren't building omni or this with the device-side or blob-side stuff, so it causes a mismatch, hence the errors. I'll see if I can't get it to work with the device stuff in, but not the kernel stuff, therefore making it compatible with both kernels with and without the updated flo stuff, but i doubt that will work. maybe we should just bite the bullet and add the flo stuff :silly:
Great rom no problems that i am aware of.
jakew02 said:
the problem with the custom kernels, ie with ktoonsez's kernel, is that he's updated the kernel-side drivers to the Flo adreno stuff, but we aren't building omni or this with the device-side or blob-side stuff, so it causes a mismatch, hence the errors. I'll see if I can't get it to work with the device stuff in, but not the kernel stuff, therefore making it compatible with both kernels with and without the updated flo stuff, but i doubt that will work. maybe we should just bite the bullet and add the flo stuff :silly:
Click to expand...
Click to collapse
With your stock kernal I'm getting better performance than any other KitKat, KT did not help with the 01-05 version and mismatched as you say very badly with the 01-13 update which I guess is the side stuff added I presume. All I know is I can leave this build on my device without the urge to flash back to Liquid v2.37.
Thanks again for your efforts and time spent
jakew02 said:
the problem with the custom kernels, ie with ktoonsez's kernel, is that he's updated the kernel-side drivers to the Flo adreno stuff, but we aren't building omni or this with the device-side or blob-side stuff, so it causes a mismatch, hence the errors. I'll see if I can't get it to work with the device stuff in, but not the kernel stuff, therefore making it compatible with both kernels with and without the updated flo stuff, but i doubt that will work. maybe we should just bite the bullet and add the flo stuff :silly:
Click to expand...
Click to collapse
Awesome, thanks for clarifying.
So when you say the ROMs aren't built with the device-side or blob-side stuff, are there specific blobs from vendor/samsung and device/samsung/jf-common that are in CM's repos but not AOSP's? If so I'd love to know which ones so I could just cherry-pick them from CM and build this for my personal use
Edit: I just realized that my last question isn't really that easy to answer without you wading through the CM and TheMuppets repo commits...I can do that, but if you happen to know which project(s) are missing the blobs, that would help tremendously!
CPA Poke said:
Awesome, thanks for clarifying.
So when you say the ROMs aren't built with the device-side or blob-side stuff, are there specific blobs from vendor/samsung and device/samsung/jf-common that are in CM's repos but not AOSP's? If so I'd love to know which ones so I could just cherry-pick them from CM and build this for my personal use
Edit: I just realized that my last question isn't really that easy to answer without you wading through the CM and TheMuppets repo commits...I can do that, but if you happen to know which project(s) are missing the blobs, that would help tremendously!
Click to expand...
Click to collapse
haha yes, Evisceration said it pretty well when he said in the jfltexx forum "why would we put the drivers for a different piece of hardware in the source?"
makes sense to me, maybe the kernel devs can be convinced to release kernels that don't include the flo adreno stuff.
but yea you could probably get away with using CM's blobs as they are now, but there are several commits that you can see regarding "Flo Adreno" , you can click the "jf-common" folder and then click "History" button for all the commits made that affected the "jf-common" folder. then you will see them, probably on page 2 or 3 :highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Bliss is pleased to present to you BlissPop Rom!
BlissPop is one of the most highly customizable roms that you can install on your mobile device,
and we hope you have a truly blissful experience.
A huge thanks to CyanogenMod for the source and all the work and dedication their team puts in to keep us updated.
BlissPop is CM12.1 based, with some features added in from various roms,
and we will continue to update features as they become available.
We will keep up to date with the latest CM code, and updates will be posted on a regular basis.
However, please do not ask for ETA's. We will update the links as soon as they become available.
As a side note, I'm only the official thread maintainer for flo and deb , ALL credits for building and compiling goes to @pjgraber03
We will not tolerate any rudeness or anyone being disrespectful in this thread.
We will do our best to answer your questions or concerns as soon as possible.
Visit our website for features that include:
Member sign-up, staff information, all the latest rom downloads,
the option to open support tickets for issues & more!
BlissRoms Website
Personalization Options
CM12 Theme Engine
Status Bar
•Clock & Date Options
•Battery Options
•Battery Bar Options
•SuperUser Indicator
•Bluetooth Indicator
•Brightness Control
•Mobile & Wifi Icon Options
•Notification & System Icon Options
•Network Traffic Monitor
•Bliss Logo Option
•Notification Count
Navigation & Button Options
•Set Navigation Ring Targets
•Overflow Button Settings
•Navigation Bar Toggle
•Set Navigation Buttons, Layout & Dimension
•Double Tap to Sleep
•Search Button Options
•Left-Handed Mode
Recents Options
•Memory Bar
•Clear All Button Tweaks
•Clear All tasks
•Clear All Recents Location
•Option to show Google Search Bar in Recents Menu
•OmniSwitch (Option to replace Recents Menu with OmniSwitch)
Notification Drawer
•Status Bar Header (Weather)
•Tile Options
•Flashlight Option
-Custom Color Tile Options (Set Background, Icons & Text)
•Quick Setting Options
•Quick & Smart Pulldown
•Brightness Slider Toggle
•Vibrate, Detailed Wifi View & Advanced Location Options
•SlimActions Tile
•Auto Close Panel
•Force Expanded Notifications
Heads Up Notifications
Lockscreen Options
•Long Press Lock Icon to Sleep
•Shortcuts
•Bottom Corner Targets
•Weather Options
•Customize Text & Icon Colors
•Clock Widget Settings
•Music Visualizer Options
•Power Button Lock Options
•Lock Method Options
Power Menu Options
•Power Off
•Reboot
•One Click Reboot
•Screenshot (with delay Option)
•Screen Record
•Profile Switcher
•Airplane Mode
•User Switcher
•Settings Shortcut
•Device Lockdown
•Sound Panel
Gesture Anywhere
•Location Options
•Trigger Regions
Animations
•IME Animations
•Toast Animations
•Listview Animations
•System Animations
•Scrolling Cache
•Scrolling Modifiers
App Circle Bar
•Included Apps
•Trigger width, position and height
Sound Options
•Media, Alarm Notification Sound Options
•Volume Steps
•Volume Panel Timeout
•Interruptions
•Launch Music Apps
•Dial Pad Tones
•Screen Locking Sound
•Touch Sounds
•Charging Sounds
•Camera Shutter & Screenshot Sounds
•Safe Headset Volume
•Less Frequent Notifications
•Media Control
•Vibration Options
Display & Light Options
•Smart Cover
•Adaptive Brightness
•LiveDisplay
•Rotation
•Double Tap to Sleep
•Sleep Time
•Wake on Plug
•Cast Screen
•Expanded Desktop
•Daydream
•Font Size
•DPI
•Battery Light
•Notification Light with Per App Settings
Notification Manager
•Device Lock Options
•Block App Notifications
•Disable Persistent Info
•Priority App Notifications
More Stuff Included
Bliss Download Section
•All current downloads for your convenience
AudioFX Equalizer
-SuperSU - Huge thanks to @[COLOR="LightBlue"]Chainfire[/COLOR]
•BlissPop Wallpapers (via launcher’s Wallpapers)
•Home Launcher Option
•CM Camera
•User Profiles
•System Profiles
•Location Options
•Security Options
•Privacy Options
•Accounts & Sync
•Language & Input
•Backup & Reset
•Date & Time
•Accessibility
•Printing
•Developer Options
•Rom & Hardware Information
•Changelog
•Bliss OTA Updates
--Many other settings throughout the rom. Take some time to familiarize yourself with all the blissful options!
BlissPop Source
https://github.com/TeamBliss-LP
TeamBliss Devices Source
https://github.com/TeamBliss-Devices
We recommend using any of the following sets of GApps:
Banks GApps
OR
Minimal Edition GApps
BlissPop 5.1 V3.5 - Official Nexus 7 2013 WiFi Flo
BlissPop 5.1 V3.5 - Official Nexus 7 2013 LTE -Deb
Team Bliss is not responsible in any way for anything that happens to your device in the process of flashing.
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom.
Please make sure you download the correct version of BlissPop for your specific device. The links are labeled clearly.
• Make sure you are rooted.
• Make sure you have a custom recovery installed. (TWRP is the preferred recovery)
• Download the latest Bliss Rom & the latest GApps package.
• Boot into recovery.
• Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
• Flash Bliss Rom
• Flash Google Apps package (for 5.1!)
• Reboot
• First boot may take up to 10 minutes
If you have a major bug to report that has not been reported already, and is not a known issue with CM,
please take the following steps to report it to us. It will save you time, as well as us.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
•After downloading the Catlog App, go to the App Settings, and change the log level to Debug.
•Clear All previous logs and Take the exact Steps to produce the error you are receiving.
•As soon As you receive the error (probably a Force Close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
•Save the log, and Copy and paste the Link into the forum with a brief description of the error.
•you can also open trouble tickets on our website for bugs.
Team Bliss is a team consisting of developers and device maintainers that work on this project in our
spare time to be able to give Android users a custom rom packed with features that will make a lasting impression.
@[COLOR="LightBlue"]pimpmaneaton[/COLOR], @[COLOR="LightBlue"]jackeagle[/COLOR], @[COLOR="LightBlue"]nprev420[/COLOR], @[COLOR="LightBlue"]remicks[/COLOR], @[COLOR="LightBlue"]Deliberate[/COLOR], @[COLOR="LightBlue"]xboxfanj[/COLOR], @[COLOR="Magenta"]nerdyblonde[/COLOR],
@[COLOR="LightBlue"]pjgraber03[/COLOR], @[COLOR="LightBlue"]bracketslash[/COLOR], @[COLOR="LightBlue"]Vortex1969[/COLOR], @[COLOR="LightBlue"]death2all110[/COLOR], @[COLOR="LightBlue"]electrikjesus[/COLOR], @[COLOR="LightBlue"]tobitege[/COLOR] @[COLOR="LightBlue"]asianflavor[/COLOR],
@[COLOR="LightBlue"]Jiggs82[/COLOR], @[COLOR="LightBlue"]genesixxbf3[/COLOR],@[COLOR="LightBlue"]sixohtew[/COLOR], @[COLOR="LightBlue"]nicholaschum[/COLOR], @[COLOR="LightBlue"]TheStrix[/COLOR],[/MENTION],@[COLOR="LightBlue"]APOPHIS9283[/COLOR], @[COLOR="LightBlue"]thecrazyskull[/COLOR], @[COLOR="LightBlue"]men_in_black007[/COLOR], @[COLOR="LightBlue"]beany>[/COLOR]
Huge thanks to all members of Cyanogenmod for the source.
Also a huge thanks to Chainfire, NamelessRom, SlimRoms, EuphoriaOS,
CRDoid, OmniRom, @temasek, @arter97 & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thanks to @[COLOR="LightBlue"]skyliner33v[/COLOR] for making our wallpaper & boot animation, @[COLOR="LightBlue"]electrikjesus[/COLOR] for making the optional boot animations,
@[COLOR="LightBlue"]pjgraber03[/COLOR] for developing and maintaining our website,
@[COLOR="LightBlue"]death2all110[/COLOR] for developing the BlissPop Wallpapers app, and @[COLOR="LightBlue"]nicholaschum[/COLOR], @[COLOR="LightBlue"]genesixxbf3[/COLOR] and @[COLOR="LightBlue"]tobitege[/COLOR] for the OTA xml generator.
Thanks to @[COLOR="LightBlue"]Kryten2k35[/COLOR] for the original source of the OTA app.
We do NOT ask for or expect any donations from users.
If someone takes it upon themselves to donate to us, of course it will be appreciated,
and all funds will be used to pay our server fees.
If someone does choose to donate, our PayPal link is below.
PayPal Link
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using BlissPop! We appreciate each and every one of our users!
XDA:DevDB Information
[ROM][OFFICIAL][5.1.1_r5] BlissPop 3.5 by Team Bliss, ROM for the Nexus 7 2013 [FLO] and Nexus 7 2013 LTE [DEB]
Contributors
beany>, pjgraber03
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-24-01
Last Updated 2015-06-14
Current build:
Flo: BlissPop-v3.7-flo-OFFICIAL-20150728-0416.zip - Official BlissRoms Flo Download (v3.7 - LP 5.1.1)
Deb: BlissPop-v3.7-deb-OFFICIAL-20150729-0204.zip - Official BlissRoms Deb Download (v3.7 - LP 5.1.1)
GApps compatible with Lollipop 5.1 are required (if you want working PlayStore)!!!
Known Issues
Some are experiencing some notification/heads up colour issues. This is usually resolved by changing the colour and changing it back again.
GUIDE, FAQ and Useful Links
Much of what follows applies to many ROMs. If you have suggestions for things to be added to this guide or find any errors then please let me know.
Purpose and Rules of XDA
XDA is a developers site. It is for learning and sharing. It is not here to "provide" apps or support to users. Most of the people that develop or help or support do so in their free time. No one "owes" you anything. You are not "entitled" to anything. Those that help others, are polite and try to help themselves will be more likely receive helpful and polite assistance.
Rule number one of XDA is : Search
Other rules include:
Be respectful
Be tolerant
Be hepful
Don't be an ass
Q&A or Dev Thread?
There is a separate development thread and Q&A/Discussion thread. Right now, I am happy for you to report all issues in the development thread.
But as it is a development thread, you should provide logs where ever possible and only report bugs if you have clean flashed. Telling others there may be an issue if you dirty flash is acceptable but please word it as such not a bug.
A little banter is accepted in the development thread, but please don't turn the thread into a chat room. Let's keep it fun but not so long nobody can be bothered to read, otherwise I'll have to revert to using the Q&A.
The Q&A is still there and available and is more "free".
Flashing
You should clean install for best results. If you "dirty flash" then at least wipe cache and dalvik/ART and you MUST provide logs with any issues.
Clean v Dirty Flash
There are a number of interpretations of clean flash. In recovery you should factory reset or wip everything except internal storage. This will wipe your apps and most app settings.
Whilst there are ways of backing up your settings they are not recommended because they can cause issues when there are changes to the ROM which affect how settings are stored or recorded. Do not restore system data: this often leads to forced closes and constant error messages.
You can use a backup app like Titanium Backup or Parcel. Sometimes restored apps can cause issues, and it is better and cleaner to re-download them, although not everyone has the time or inclination to do this.
If you do not wipe as per above, then you are dirty flashing. This is quicker and often works. But because things are left behind from the previous flash this can result in weird issues. When you dirty flash you really should wipe cache and dalvik/ART, so that there aren't residual
Reporting Issues
Before Reporting Issues
If you have issues with your new flashed system there are a few things to do before you report them.
First, if you have dirty flashed then try a clean flash to see if the issue remains - many issues are cleared this way. Also, it is very difficult to pin-point certain issues after a dirty flash.
Also, if you have Xposed installed then remove that before reporting. This is because Xposed can change things deep within the OS and make things behave differently, which in turn makes it very difficult to troubleshoot and resolve issues. This is Xposed hate - many devs require this and will not offer any support if Xposed is installed.
Reboot. It's surprising how many issues can be resolved by this simple step. Especially if an app is misbehaving or using a lot of battery.
How to Report An Issue
The biggest bugbear of those trying to help with issues is when they are not properly reported and require to have the same questions answered over and over. The circumstances may require different information, but here are a few common items to consider posting:
Version. Often people miss this and are reporting something that was solved days or weeks ago. Others say "latest" when it may not be. Quote the version number and/or build date.
Firmware. Again, quote the date or source.
GApps. The GApps version can affect which version of Google Play Services and PlayStore, amongst others that are used. Whilst often GApps can be "out of date" without any issue, when there is a lot of development by CM this can be very relevant.
Whether you clean or dirty flashed.
A log. Necessary if you dirty flashed, very useful even if you clean flashed. See below for how to do this.
How to replicate the issue. The more specific about how the issue arises and when, the more likely you are to get a quick resolution. If no one can replicate the issue it is unlikely they can resolve the issue.
How to Take a Log
This is an excellent guide.
Some kernels have their own log/bug report option to make things easier.
Useful Links
Google and the XDA search bar are your friends.
Whatever you want to ask or find, it's probaly already there. This is why you often see replies just saying "Search!"
XDA: RULES - MOD HELP - SUMMED UP 1 - SUMMED UP 2 - BEST WAY TO GET A LOG
Frequently Asked Questions
No one answered my question.
Maybe no one has read it yet - you may need to give it time. Maybe no one knows the answer yet. Have you already tried to solve the issue? Were you polite? Did you give enough information? There is no need to keep bumping your post.
Which folder does the OTA file get downloaded to? Is it the full file or just the incremental update? Are there nightlies?
/sdcard/Download and it's the full file. They aren't nightly but they are normally very frequent.
Does BlissPop support Layers / RRO?
No. It has the CM theme engine.
Which kernel is best for....?
Stock is really quite good, so I'm not going to suggest any others, as there aren't many now and are easy to find on XDA. So much depends on you: your setup, apps, usage, signal. The list goes on. The real best way to find out is try them for yourself; give each one a few days to settle and you can observe battery usage, smoothness, speed, tweakability etc. But there is no Holy Grail kernel - one that gives the best of everything for everybody. "Performance" and "battery" aren't mutually exclusive, but most kernels are biased towards one or the other. Kernel governors and hotplugs also have an effect. If you are interested in a kernel, read some of the kernel thread.
One last point. When there are changes from CM the date and commits of a kernel can be important so the kernel and ROM aren't out of sync.
How is Battery Life
This often gets asked, but there is no clear answer that suits everyone. So lets start of by saying the team finds battery life to be very good.
There are however many things affecting battery life. Your apps, settings and signal all have a big effect. As does how often your apps are updating and whether over wifi or mobile data. Additionally, which kernel and it's settings also have an effect. As does screen brightness. Certain social and messaging apps can have a huge drain. How often you flash a new ROM has a big effect too. Ideally, from a battery life perspective, you should allow everything to settle and go through a couple of charge cycles. With the frequency of BlissPop updates I have never achieved this!
So every user will have different battery life and typical screen on time. Make sure when doing comparisons you really do it on a like for like basis.
If you want to investigate battery usage, consider apps like Wakelock Detector (WLD) and Better Battery Stats (BBS) as well as GSAM Battery Monitor. These will often pinpoint where battery is being consumed and what is waking your device. Quite often you will see an app misbehaving which can often be resolved with a simple reboot.
?
?
Been waiting for this for some time...didn't think it would make it to flo...
Thanks...
Dude FC When Clicking On Setting/LockScreen
Right on man. I too have been hoping this would happen. Its great to see bliss on flo!
checked the blisspop download page two days ago for an official build for our beloved flo. felt a bit sad until i stumbled across this thread
thanks a lot mate! you made my day
Bro the ROM dosen't work for me ..
It wont boot at all only FC system ui bootloops
Hope you van fix it in the nextbuild
Regards
ROM booting?
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Will theme engine(cm/rro) be added?
)
davideelde said:
Bro the ROM dosen't work for me ..
It wont boot at all only FC system ui bootloops
Hope you van fix it in the nextbuild
Regards
Click to expand...
Click to collapse
No probs here..as a first suggestion I would follow instructions in the op. If you have problems after that, let me know...
---------- Post added at 04:18 ---------- Previous post was at 04:14 ----------
@pimpmaneaton
What a ROM....!
Looks interesting, will download and give it a try. I can't speak for others but I'm partially colour blind and the links in your thread are practically invisible to me. I have to highlight the area to see the links.
Nice now booth my devices are blissed ??
Enviado do meu Nexus 7
rom runs great on my flo. had my concerns on the first boot after since i had a constant white flashing during the bootanimation. it didn't appear on the next boot so i think it was a temporary thing..
freakzapster said:
Dude FC When Clicking On Setting/LockScreen
Click to expand...
Click to collapse
i have this too, full wipe+system
the built in dark heme has an issue in the settings, white borders, font and wallpapers work good.
just 1st impressions as i just installed. lookn good. :highfive:
Just a quick question... How come no flo nightlies?
TIA...
Fantastic ROM BTW.
Vcolumn said:
i have this too, full wipe+system
the built in dark heme has an issue in the settings, white borders, font and wallpapers work good.
just 1st impressions as i just installed. lookn good. :highfive:
Click to expand...
Click to collapse
i did the same
full system wipe then too fc
When selecting the settings screen lock off with an error
ElementalX kernel working with this rom?
VannMann said:
ElementalX kernel working with this rom?
Click to expand...
Click to collapse
Flashed the caf version and it works fine!
Good rom :thumbup:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
SlimLP is the project name for SlimRoms based on Android 5.x Lollipop and offers the following original features:
Slim Dialer
A full replacement of the official Google closed source dialer with added features. - We've got you covered.
Privacy guard
Disable unnecessary permissions set by app developers. - Privacy is part of the experience.
Slim Center [WIP]
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticons..etc. - You'll be tapping away to your heart's content.
Custom Shortcuts [WIP]
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - Customize it the way you like it.
Important links:
slimroms.eu - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for the Samsung SGH-i727 Skyrocket from here.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: SlimRoms are not responsible for any damages to your device.
--------------------------------------
Changelog for my custom builds is in Post #2.
Download links and Installation instructions for my custom builds are in Post #3.
1080p video recording is not working right now. If you need 1080p recording, you can use A Better Camera.
Special thanks to (in no particular order):
gimmeitorilltell
RobbieL811
prbassplayer
SultanXDA
Steveromingagain
XDA:DevDB Information
[DISCONTINUED][ROM][5.1.1] SlimLP - Skyrocket [UNOFFICIAL], ROM for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
NoSpamDan, gimmeitorilltell
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: No Longer Updated
Created 2015-01-26
Last Updated 2016-11-15
Changelog:
NOTE: I don't have time to maintain this list, but will try to post notable fixes and/or updates in the announcement posts for new builds.
Some of these features are added by myself and may or may not continue to show up in the builds. Slim has started the weekly builds, but don't expect those builds to have features that aren't merged yet, like some of the below ones!
Slim-skyrocket-5.1.1.alpha.0.1-UNOFFICIAL-20150510-0221.zip
MD5: ba0df799af5c2b1bec60b97929f1a82f
Fix mobile data issue(s)
Possible lag/wake from sleep improvements
Quick Settings tile customizations
Latest Slim commits...
Slim-skyrocket-5.1.1.alpha.0.1-UNOFFICIAL-20150426-2142.zip
MD5: 70f4884c4ed92879391e417de3f6b81e
Fixed Phone app FC
Display overlay CAF fixes
Mobile data may still have issues. WIP
Slim-skyrocket-5.1.1.alpha.0.1-UNOFFICIAL-20150423-1933.zip
MD5: 1526faeadc3b6545b292b8c936ff805e
Removed default DPI
Added low memory adjustment
v5.1.1 updates across the board
Slim-skyrocket-5.0.2.alpha.1.0.3-UNOFFICIAL-20150331-1044.zip
MD5: a585a75fab0458211c738d67213646b2
Torch/Flashlight tile is working
Low memory optimizations
Latest Slim WIP commits from RobbieL811
Slim-skyrocket-5.0.2.alpha.1.0.3-UNOFFICIAL-20150322-0521.zip
MD5: b2f1b55c3b6ba2bec3f1473d90d06c68
New features like Blacklist, expandable volume panel, and SlimCenter (not fully functional to inform of updates yet).
Basic BLN support in the kernel. Enable/disable it in Settings > Sound & notification > Notification > Notification light
Should be a noticeable improvement in the occasional lag, but there seems to be a general bug related to this that affects many devices. With our device, it's more noticeable due to lower resources in general than newer devices have.
Default DPI is now set to the native device default of 240, but you can change this to several preset values in Settings > Display > LCD density.
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150312-1448.zip
MD5: 2131cca37fb25c74d05653dce053318c
Updated WiFi, camera and display vendor blobs.
Wifi: removed sockets implementation.
Lagginess should be improved, if not gone...
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150305-0204.zip
MD5: cf7bba521709785eca9354829e784b72
Power-off charging is fixed, along with animated images and even % display during power-off charge. So if your phone dies, you can charge it back up without issue!
BLN (Button Light Notificaiton) support, and it can be disabled if you want in the Settings menu! (Sorry no per-app control right now.) Thanks to @gimmeitorilltell!
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150228-2118.zip
MD5: 23b09052ec18783266037088a47f7bd2
Kernel fix for keypad null pointer.
Fix for first install WiFi HAL soft reboots.
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150226-1520.zip
MD5: 7dc4acb4e25c5daff59f0b4b31f318fd
Added power menu customization
Added SlimCenter
More Quick Settings updates, including a Reboot tile
Many other updates
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150222-0036.zip
MD5: 6896fb4aed5d9c3d56093e118fc932e8
Added Slim's new hardware key rebinding
MMS updates and fixes
USB Charging
Updated Quick Settings tile customization
Show each app name being optimized during boot
Slim-skyrocket-5.0.2.alpha.1.0-UNOFFICIAL-20150221-0122.zip
MD5: f74766fd46b6bd7f3e53b349eeebeede
Soft reboots fixed!
Fix for possible NFC bug.
Quick Settings tiles customization (Settings > Interface > Quick settings). Note: there still may be bugs...
Battery icon customization (Settings > Interface > Status bar > Battery icon options)
DPI changer (Settings > Display > LCD density)
Cursory RRO Theme suport. Slim is currently not implementing CM's theme engine. RRO is better in many ways... If you don't know what RRO Themes are or how to use them, you need an app and theme apks. Check it out here: RRO Themes App Official Thread and here: some RRO themes hosted on RobbieL811's server. Thanks, @RobbieL811!
Audio policy tweaked some more - Please test various audio/video scenarios.
Ringtones may not appear until after the Media Scanner picks them up, the phone sleeps, or a reboot. Not sure which at this point, but they are there!
Various other updates and code clean-up
Slim-skyrocket-5.0.2.alpha.0.91-UNOFFICIAL-20150214-2343.zip
MD5: 5f231fbf4e38f1dc8dc1f660b18463eb
Mobile data and MMS are working now! Thanks to @Sultanxda for pointing me in the right direction!
Camera API updates and bug fixes (no 1080p yet though)
Torch
Audio policy cleaned up
Media codecs cleaned up
MTP transfer mode is selected by default
Removed unused libaudioamp config
Re-enabled qcom aac encoder
Removed call volume steps prop overrides
Removed PowerHAL
Various other updates and code clean-up
Slim-skyrocket-5.0.2.alpha.0.91-UNOFFICIAL-20150205-2203.zip
MD5: fcac1bdad6b3f1fae35fde4fe10c711e
Moved almost all code to Slim source.
Using modified CM kernel, compiled inline with the ROM using gcc 4.8 armeabi kernel toolchain
Using new msm8660 CAF branches
Device code updates and clean-up
Slim-skyrocket-5.0.2.alpha.0.91-UNOFFICIAL-20150203-1411.zip
Audio now works
Kernel booting and compiled with gcc 4.8 armeabi toolchain
New modified kernel based on CM 12.0 msm8660-common kernel
Media/codec updates
My underwear - when I first heard SlimLP audio on the Skyrocket!
Download and Installation Instructions:
Download links:
ROM:
Slim-skyrocket-5.1.1.beta.0.10-UNOFFICIAL-20151027-0853.zip
Special thanks to @RobbieL811 for temporarily hosting some of these builds! If you see him around, be sure to thank him!
GApps:
Use TK PIco GApps from AndroidFileHost | BasketBuild
(Main TK GApps thread on XDA)
TWRP Recovery:
TWRP 2.8.7.0 with F2FS support in IMG, TAR and ZIP formats. Thanks to @javelinanddart for compiling these.
Instructions:
Reboot to recovery.
Make a nandroid backup.
Boot into recovery. You need a newer version for lollipop. Tested with TWRP 2.8.7.0 recovery linked above.
Make a nandroid backup.
Make sure you're on one of these radios or newer for now: I727:UCMC1|I727R:UXUMA7
FULL WIPE/Format: /system, /data, /cache and /dalvik.
Flash the ROM.
Flash GApps(use Slim Mini or Zero GApps).
If you want ROOT, you have to unlock Developer Options by going to Settings > About phone and clicking on the Build number field 7 times. Then you can enable Root in Settings > Developer Options > Root access.
Reboot when finished
Boot animation is delayed 10-20 seconds, and takes about 10 minutes to boot up on a clean flash, so be patient and give it time.
Enjoy!
Note: You may not see all the ringtones, notification sounds, etc. until the phone goes to sleep, or the Media Scanner finds them. Also, check the Settings > Sound & notification > Interruptions menu to make sure these aren't disabled, as in "No interruptions". This disables the sounds.
Issues? Post a logcat on Pastebin, link to it here, and provide as many details as possible, such as ROM version, GApps used, radio/modem, cell provider, or anything relevant to the problem or how to duplicate the issue.
Enjoy!
Screen shots and stuff:
NOTE: RRO is no longer part of the Slim sources. Basic layer support is included (v1). I am not sure where this is going with Slim but feel we need a theme engine of some kind. I've left these images here for fun. If I find I can pick the RRO commits back into my builds I will try, but if we go weekly, it will have to come from the bosses...
Some screen shots using RRO Layer Theme Synergy_v4 by Brian Gill are attached.
Note you need the Bitsyko RRO Themes app, which you can get by signing up for beta testing, and then you can use Google to find other themes. Full instructions are in the link.
Note there is some Teal mixed in with the Blue, but you get the idea...
great stuff
question, did u test w/philz cwm, he has abandoned all work on cwm as of july 2014
vincom said:
great stuff
question, did u test w/philz cwm, he has abandoned all work on cwm as of july 2014
Click to expand...
Click to collapse
Yes sir, it's what I primarily use. It still works well, even though it's discontinued.
My computer likes to connect to the phone's USB storage with PhilZ, whereas with TWRP it has trouble sometimes.
Both should work (for now)... [emoji14]
Sent from my OnePlus One BACON using Tapatalk
LP Rom
Nice to see you're doing a 5.o rom. good luck.
@NoSpamDan What? You got it going? Good work!
RobbieL811 said:
@NoSpamDan What? You got it going? Good work!
Click to expand...
Click to collapse
Thanks. Well got it going, kind of... struggling with audio issues right now but hopeful. Kernel not booting is back again.
New build is up in the OP, with updated instructions. Still a WIP...
Go Pats!
Audio is working!
New build in OP with WORKING AUDIO ! Huge thanks to @gimmeitorilltell for collaborating on this! GPS locks fast... The source needs to be sorted out and pushed to Slim still, so if you're looking to build, you'll have to wait a bit. Still a WIP...
I need some people to test phone calls and SMS/MMS functionality since my Skyrocket has no SIM card. Share a link to your logcat on Pastebin if possible please.
Let's get this thing all prettied up!
-Dan
Like to have Ported to hercules!!!!
Sent from my T-Mobile S2 using XDA Free mobile app
1st test
NoSpamDan said:
New build in OP with WORKING AUDIO ! Huge thanks to @gimmeitorilltell for collaborating on this! GPS locks fast... The source needs to be sorted out and pushed to Slim still, so if you're looking to build, you'll have to wait a bit. Still a WIP...
I need some people to test phone calls and SMS/MMS functionality since my Skyrocket has no SIM card. Share a link to your logcat on Pastebin if possible please.
Let's get this thing all prettied up!
-Dan
Click to expand...
Click to collapse
20150203 build
wifi working-phone working,in and out calls
sms over wifi works but not pic mes
showing LTE but no sms or brower data(apn correct)
on 1st boot t lock screen with circle s hit power button to wake and boot from circle s again,did this 3 times then stayed in rom
browser pages sluggish,hardware search key would not bring up keyboard search (cm12 same)
phone rom itself is very fast and smooth-no gapps installed during test
battery doing well
hope this helps
pawanzZ said:
Like to have Ported to hercules!!!!
Sent from my T-Mobile S2 using XDA Free mobile app
Click to expand...
Click to collapse
It is planned once the SR is stable...
Steveromingagain said:
20150203 build
wifi working-phone working,in and out calls
sms over wifi works but not pic mes
showing LTE but no sms or brower data(apn correct)
on 1st boot t lock screen with circle s hit power button to wake and boot from circle s again,did this 3 times then stayed in rom
browser pages sluggish,hardware search key would not bring up keyboard search (cm12 same)
phone rom itself is very fast and smooth-no gapps installed during test
battery doing well
hope this helps
Click to expand...
Click to collapse
Thanks for the feedback. Got a logcat of these?
sms over wifi works but not pic mes
showing LTE but no sms or brower data(apn correct)
browser pages sluggish
Says have not been member long enough to summit file ,sorry.
Update- text working over LTE connecting after second clean install_no SMS pics or data
Steveromingagain said:
Says have not been member long enough to summit file ,sorry.
Update- text working over LTE connecting after second clean install_no SMS pics or data
Click to expand...
Click to collapse
OK, thanks so MMS pics aren't working? Did you set your default data type and APN correctly? If you can try other ones, it might be useful.
You can share your log using pastebin.com and providing a link here to it. If you can't post links, just spell out the url with words or PM me (if you can).
New build is up in the OP. Not a lot changed, except some source moved around on Slim since msm8660 got it's own CAF branches.
Beware if you try the torch tile, you will have to reboot to use the camera. This is an issue with the Nexus phones too and I hope to see it fixed soon.
Here's a direct link to the ROM (instructions are in the OP):
Slim-skyrocket-5.0.2.alpha.0.91-UNOFFICIAL-20150205-2203.zip
Use the latest Slim normal GApps v467 or Slim mini GApps v467. The full GApps package is very large and might not fit into the system. I had issues with apps disappearing like Play Store and Play Services issues. You don't want that deal...
Just put this on my skyrocket. Wow! Its like a new phone . So fast and smooth. I had to order a new battery though. It will be interesting to see what the battery life is really like as the one I have dies pretty quickly considering it the original. Wish I could access all 16gb of the internal memory for apps though.
eosman said:
Just put this on my skyrocket. Wow! Its like a new phone . So fast and smooth. I had to order a new battery though. It will be interesting to see what the battery life is really like as the one I have dies pretty quickly considering it the original. Wish I could access all 16gb of the internal memory for apps though.
Click to expand...
Click to collapse
What is the issue with internal storage?
Sent from my OnePlus One BACON using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might question, my answer would be why not. After all Harry's patronus was a stag(pun intended). After having a couple of iterations, we still intend to stick to our roots, and keep refining what we have. With Android 12, Stag would still be aiming at an elegantly beautiful close to stock experience, that satisfies just the features and customisations you'd crave for (nothing more, nothing less), at the same time being blazing fast and silky smooth. You'll have to try it to believe it .
~Sic Parvis Magna~
PS: for people wondering what sic parvis magna is, it translates to great endings from small beginnings, Something i picked up while playing a game.
Credits where they are Due:
Google(No explanation needed n this regards)
Lineage(For starting of the custom rom war)
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
This Build is a Beta Build, I will not be responsible for any kind of issues that might come up (while flashing)
Pristine Build - Non Gapps: Download Here
Gapps Build: Download Here
Bugs
You tell me
Features
Refresh rate switch
Advanced Reboot
Google Style monet made better thanks to ProtonAOSP and kdragon
OOS Style Screen Recorder (Check qs tiles)
Enforcing Build
CTS Passes
Unlimited Google photos backup (Fingerprint spoofed)
CTS Passes sucessfully
Face Unlock
Less Annoying Notifications
Working Gcam Pre Installed
Ambient Display Gestures
Off Screen Getures
OTA Support
And much much more, hope you all love the build.
The build will be updated with bug fixes, but please don't ask ETA.
Hope you like it.
Please follow the instructions properly.
**Make sure your boot loader is unlocked**
Spoiler: If you are on OOS 11 or OOS 11 based ROM
Follow These Instructions if you are on OOS 11 or OOS 11 Based ROM
Download the boot.img from here
Reboot to bootloader
Use the following command to flash boot.img to both slots
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot to recovery
Format Data (Optional if already on Stag)
Select Apply update
Run the following command
Code:
adb sideload romname.zip
Spoiler: If you are on OOS 12 or OOS 12 based ROM
Follow These Instructions if you are on OOS 12 or OOS 12 Based ROM
Download the boot.img, vendor_boot.img, debt.img from here
Reboot to bootloader
Use the following command to flash boot.img to both slots
Code:
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot to recovery
Format Data (Optional if already on Stag)
Select Apply update
Run the following command
Code:
adb sideload romname.zip
If none of the above methods work, please use the following.
Spoiler: If nothing works
Beware this is OOS 12 C.48 based build so it is important that you follow instructions properly and that you are own OOS 12 C.48.
All builds can be found here
The Proper due credits will be updated promptly, A huge thanks to the Lineage team and luk for bring up of OnePlus 9 trees.
A huge huge thanks to everyone who helped me test it, and develop:
@chandu dyavanapelli for helping me with 12 bringup
and
@aswin_a_s forhelping me deal with some huge issues, and stabilizing source (both rom and device)@tbiwalkar for always actively testing out 9 builds all the timeEtherealRemnant for testing in general and also, testing multiple builds out to help me fix Verizon.Yashwant for testing almost all the builds, which made it possible for this build today
Robert, @Jhoopes517, rohan, avid_droid for testing the builds promptly and reporting all the major bugs.
This release would have been super difficult without your help. Thanks a lot.
I am extremeley sorry if I forgot someone, please dm me and I will promptly add your names.
and currently this build is work in progress.
ROM
Kernel
Device Tree
I work on this project as a hobby, and the money for the servers completely go out from my pocket.
If you like my work it'd be great if you could: https://buymeacoffee.com/vjspranav
I would really appreciate it.
Thanks and hope you enjoy the build
ROM OS Version: Android 12.1
ROM Kernel: Linux 5.4.x GKI
Based On: AOSP
Version Information
Status: OFFICIAL
Current Build Version: 12.1
Build Release Date: 2022-08-09
Reserved for SS
Changelog - 08/09/2022
Hey everyone, this update took a bit longer. I have been super busy with life. I'll keep changelog this time short and concise.
1. OOS Cam is finally here, everything works.
2. Build is based on August Patch
3. Added volte icon
4. And some stability fixes .
Hope you enjoy this release, this will be the final A12 release for OP9 series, see you in A13
Changelog - 20/07/2022
Hola, We're here quicker then before. This stag build is a simple elegant build that has some beautiful additions. Firstly the build is updated to July Security Patch. Up to date AF.
I'll directly jump on to changelog:
1. Now you have multiple options in alert slider, it's a waste just using alert slider for silent, sound and vibrate. Let's use it for a lot more than that. We call it the Awesome Alert Slider.
2. Added option for higher touch sampling rate.
3. We have an OOS style clear all icon in notifications, it's boring to see clear all text.
4. Now you can flaunt android 12L in your version hehe.
5. We have a screen off fod now, you can use fingerprint when screen is off. You can find the option in Settings > System > Gestures.
6. And many crashes fixed internally )
Changelog - 23/06/2022
Guys this is a small hot fix build that ensures that sensors are fixed. The older update had a bug due to which all sensors stopped working
Changelog - 21/06/2022 - Sensors Broken
Hiya, This time the changelog might turn out pretty long, so yup stay tuned. Before anything else, Yes I realise the time between updates is kinda long, honestly I really try had to get it to you guys much sooner, but this is the best I can do. Another factor that comes in is, every time I add a new feature or fix a bug, I feel like there's something else that can be better, and I go on to fix/work on that, this cycle keeps happening because come on guys, I want to ship out nothing but the absolute best for you guys to use.
And this time with the OOS 12 base, a lot of things broke, and I had to work on fixing things from around up, so without further ado I'll jump right into the changelog. As always, will start with what's bad
Assuming not everyone will read through, please follow the install instructions carefully, as mentioned in OP. else you might end up in brick
So there are two known bugs which I really couldn't fix at this point:
1. Low mic volume in recording apps, calls are perfectly fine (some reported that if you turn on speaker in call once after every reboot, the mic seemingly becomes better)
2. Speaker starts crackling in specific audio (only on max volume) otherwise it's absolutely fine as long as you don't hit the absolulte max.
Ok that aside, now let's get into the good news, the juicy part :
Device Specific:
1. Ok the biggest change, Now the builds are going to be OOS 12 based, partly the reason why there was an even bigger delay, but man o man, the build just flies, you'll forget using any other OS.
2. Biggest challenge was to get the haptics right, the vibrations you feel when you touch your keyboard, or the the haptics when there's a notification, OOS 12 base created a huge mess with them but guess what, you'll not have to worry about them because the haptics are much much better than ever, you'll just fall in love with how your phone vibes (literally hehe).
3. On a few requests, I've decided not to include Gcam in this build, whoever wants are free to install whichever version you want to go with .
4. Verizon sims should finally work, Had multiple tests this time so you should have it working for sure, here's to everyone waiting with a Verizon sim.
5. And everything else that yo love and remember from previous version exactly as they were, if not better
Rom Side:
So here's a lot more magic this time, about time I felt the need of a few essential and good to have feature additions without in the slightest compromising how the usability feels.
1. We now have a working GameSpace dashboard, like for every gaming enthusiasts, finally you can game with the full power without any disturbance of notification.
2. Again for all the gamers out there, we have added some props to allow a game to unlock the maximum FPS possible, for more info:
Spoiler: Click Here
* Free Fire - Spoof Asus ROG Phone 1 will unlock 90 FPS
* COD Mobile - Spoof Xperia 5 || will unlock 120 FPS (only on multiplayer mode)
* PUBG Mobile - Spoof OnePlus 8 Pro will unlock 90 FPS
* Wild Rift - Spoof OnePlus 8 Pro will unlock 120 FPS
* Cyber Hunter - Spoof OnePlus 8 Pro will unlock 90 FPS
* Fortnite - Spoof OnePlus 8 Pro will unlock 90 FPS
3. For apps builds, now we ship a modded Pixel Launcher (credits: source). Gone is the pain of using a half baked custom icons. This is a much more optimised pixel launcher with a lot more goodies (like upto 6x9 grid in launcher)
4. A small aesthetic change, re arranged the layout of qs tiles, gone are the tiles which you rarely used and a rather depreciated wifi/mobile data tile. Now we have separate tiles for mobile data and wifi just like we remember and love from Android 11, and that's what is default.
5. Ohh and on the note of QS tiles, Hasn't it been annoying when you long tap on wifi just to be able to quickly connect but you are having to change the screen, now a small panel pops up as an overlay on the existing screen allowing you to work without leaving whatever you were doing.
6. A proper lock screen charging info, Instead of the boring wrong display, the estimate and wattage have now been fixed, and as multiple people questioned, yes Warp Charging does work .
7. And a highly requested feature (and I can see why), long press power button to turn on torch. You ask and thee shall receive, this build comes with the said feature.
8. Now we allow you to have a haptic feedback on QS tiles, when you tap on that, you know want that, don't you.
9. Some over the hood source changes, that'll make scrolling and animations go whoosh (faster and smoother), especially optimising the download and upload animations.
10. And a huge addition to feature list, Network traffic on status bar. For everyone who have been asking it is finally here.
11. Making life easier with this one, giving you an option to complete pull down the quick status bar either from left side or right side, depending on what you select. So you select, let's say right side, now if you pull down from left you'll have notifications. and if you pull down from right side you'll have the QS tiles. pretty handy right .
12. Added an Ambient music ticker, that'll flash new songs on ambient display, I personally love this, happy to finally be able to have it on stag .
13. Ok finally everything bugging with lock screen pin and pattern has been fixed, which allows to have scrambled pin layout back ).
14. Now directly delete a screenshot if you do not like it, directly from the preview when you take a new screenshot.
15. That's not all, now you can directly feed a screenshot into google lens, isn't that cool.
16. Added font customisation and a huge bunch of fonts, you'll absolutely love it. (We also have status bar, launcher icon customisations) you can find them in Horns > System.
17. Don't like watching '!' when mobile data is off ? worry not you can disable that now. see super thoughtful of me (just kidding)
18. If you are like me, you just want to watch the battery percentage on quick header and not something like "6 hours remaining", so like any sane person would do, I have added an option for you guys to be able to delete it.
Well that's all the changes for this update people....
oops spoke too soon, there's,more
19. Here's a little gesture touch, we now give you an option to turn of sleep either by double tapping on status bar or double tapping on Lock Screen. Use both or use neither upto you.
20. Wanna wake up your device using volume keys instead of power button. Just like shenron would say: "Your wish has been granted"
21. Ever seen a Samsung phone, Noticed their pop up notification (click here for reference), See how non intrusive and beautiful they look, don't be sad, you can have a very similar experience in stag, just go ahead and enable reticker from Horns. yay!!!
22. Ever see all the real estate in the status bar being wasted, the clock being so annoyed stuck beside camera, now you have the ability to customise it's location and the control that gives is amazing.
23. Made battery settings beautiful, added battery health info and capacity info so you also know what you have.
24. Added data usage panel.
25. Nav bar inversion, used to inverted back and recents layout, fear not when stag is here.
26. Smart auto-rotate, i.e. you rotate the phone by mistake when auto rotate is on, and phone just annoyingly rotates? not gonna happen that often anymore, phone will keep a track of your face and rotate only when it deems necessary based on orientation of your phone. (Will lead to higher battery consumption)
I could go on, but that's about most of it, there's still tiny under the hood improvements which aim at making stag ever better,
A huge change set this time, so I really am looking forward for you guys to try this build out, I really really wish you would love it and never want to leave ..
Happy Flashing
~Sic Parvis Magna~
Changelog - 10/04/2022
Hola guys long time no see, I know I promised monthly updates, but this one stretched far too long. The reasons include my college and android 12.1, which was a huge pain for me. But nevertheless here we are as stable as ever ).. Ok as always
Without further ado, I'll quickly list down the Changelog.
Bad news first:
1. We won't be having OOS camera anytime soon, Almost everything works except for rear normal photo, I need some help for fixing hence I am not including it in release builds. If anyone wants to try it out, feel free to pm me on telegram: @vjspranav.
Ok that was it, everything further just keeps getting better.
Device Specific
* Tweaked the position of alert slider UI to make it feel more natural.
* There was a small chance of sim not being detected on first boot, that has been fixed.
* Issues with Verizon have been fixed. A few devices report it as working, a few report it as broken, so you can probably just try it out and let me know.
* Wait must have been super annoying to see wrong charging info on Lock Screen, stuck at some 1hr 24 mins always. Now your phone works as it should have! Lock-screen charging info now shows correct estimates.
* One of the biggest things, we no longer spoof our whole device as pixel, It detects as a oneplus and that helps a great deal with refresh rate in a few apps. And guess what!?
CTS still successfully passes ).
* Added a bit of optimised charging support, although you can't control start stop percentage, your phone will still make sure to stop charging after a certain point. This will be adapted based on your usage.
* Finally for everyone not being able to flash gapps on pristine build, Now you can do so and much more, The issue has been fixed. You can flash any and every apps package, be it micro, mini, full or stock.
* For people having Indian version or any other version which does not support wireless charging, they were unable to turn off, power sharing. Now you all don't have to worry .
Rom
* Updated to Android 12.1 with April security patch, nothing but the latest and the best.
* Added back charging animation ripple removed as part of 12.1 by Google.
* Temporarily removed pocket lock as it is causing issues with device wake.
* Added quick unlock with pin, many have asked for it.
* Added option to enable always on display on charging only.
* Added options to customise fonts and styles of status bar.
* And a lot of under the hood changes thanks to both android 12.1 and also things we at stag do.
As always, stag is as good as you last remember it if not better. I really hope you enjoy the build, and keep showing the love!!.
Cheers
Changelog - 25/02/2022
Hello everyone, first of all, sorry for the delay of two months. I was super busy with life and had covid and college and stuff, secondly I am super happy and thrilled for the support everyone has been giving. I really hope you find this build and also the next exactly to your liking if not more .
Without further ado, I'll quickly list down the changelog.
Device Specific
* Firstly The clock being overlapped by camera cut out, padding issue has been fixed.
* On Lock Screen, you must've seen FP icon and charging info overlapping each other, this issue has also been fixed.
* You must've loved the new unlock animations of A12 right?, But I'm sure everyone felt, the power button location of animation is off, guess what we've got that fixed too!
* Ohh how could I forget, the dreaded ring issue, you won't have to face it anymore, every call you do will for sure have a ring giving you the peace of the call being connected and not having to face surprises.
* We Added OnePlus Specific Settings, That let you select Hyper Touch, Edge touch etc.
* Added Touch screen gestures, these are just love (we also support single tap for ambient display )
* Wake device on pick up, and a couple more ambient display options have been added.
* Build comes with a pre installed working GCam on gapps build.
* Wanted to share your battery to your friends? We have power share toggle added, you can wirelessly or through wire charge your friends phone or any chargeable device!
If you think those are good, wait till you see, what the ROM brings
Rom
* Updated to February patch.
* Ever wanted to look at your phone, and just wanted it to unlock, no sweat, stag has the long awaited face unlock support now.
* We have ota support now, all further builds can be downloaded and installed seamlessly over OTA.
* Added an idle battery manager, this helps in saving idle battery.
* Guess what ever wanted too listen to your class and YouTube, and wanted to decrease volume of your class/meeting only ? It's now possible, we have per app volume control, let your meeting run in silence and let the music begin!. (just kidding, we have the feature but don't miss out on classes )
* I believe there was an issue with no default notification or ringtone in the last build, worry not we got you covered!
* And remember that annoying screenshot sound ? I don't, because we don't have it anymore.
* And And, Live translate works, Complete the initial setup and update all apps, and you're all set.
* For all the enthusiasts, we have an amazing black theme, I know you are there and you are going to love it!
* You scared your phone gets unlocked in your pocket? Well just a toggle and your phone can be smart enough to not unlock as long as it's in your pocket! with pocket lock.
* You like your brightness slider at the bottom? Do not want to see the auto brightness icon ? Or don't want to see the bar at all ? Well you can do all of them now.
* We have saner heads up now, if you are constantly annoyed by every notification pop up on your screen! Explore it to know it.
Upcoming
* We are working on OOS Cam, we have potrait pro mode etc working, so expect to see the next build with OOS Cam .
and too much more, small changes and tweaks to make your experience the best possible!!.
Due to the volume of changes, it is highly recommended to clean flash for the best experience.
Nice flashing now !!!!
Dont try it if you are coming from oos 12 stable . no luck. You must come from oos11
*even from oos 11 no luck.
It booted fine on the TMO op9 fingerprint sensor just flashes when I try to register but other than that everything else works perfectly. Thank you!
JimmyJurner said:
It booted fine on the TMO op9 fingerprint sensor just flashes when I try to register but other than that everything else works perfectly. Thank you!
Click to expand...
Click to collapse
can you tell what recovery you used to please? and from what os did you flash it ?
Woot excited for a new rom to flash. Sick
papad13 said:
can you tell what recovery you used to please? and from what os did you flash it ?
Click to expand...
Click to collapse
I came from an older version of lineage recovery because when I tried using the newer one it would not boot to the recovery. I came from 11.2.10.10 after using the TMO convert msm
Now that it booted android 12 let me try a fresh recovery flash of the newer one and start from scratch.
It booted to the newer recovery fine this time. Booted to the os as well. Still no fingerprint sensor. It seems it it just won't register.
JimmyJurner said:
It booted to the newer recovery fine this time. Booted to the os as well. Still no fingerprint sensor. It seems it it just won't register.
Click to expand...
Click to collapse
At initial install,use the 0626 dated LineageOs recovery.img. Any newer nightly build losrecovery may cause an issue. After installing recovery and installing system, do not attempt to flash any recovery on device. It messes up the Os. I'm running Stag and FP sensor is working fast and easy on my end
avid_droid said:
At initial install,use the 0626 dated LineageOs recovery.img. Any newer nightly build losrecovery may cause an issue. After installing recovery and installing system, do not attempt to flash any recovery on device. It messes up the Os. I'm running Stag and FP sensor is working fast and easy on my end
Click to expand...
Click to collapse
Yeah , everything else is giving a non bootable device . Only booting on fastboot
Maybe a good advice for the TS to add it in the post !!
papad13 said:
Yeah , everything else is giving a non bootable device . Only booting on fastboot
Maybe a good advice for the TS to add it in the post !!
Click to expand...
Click to collapse
Everything is being updated in OP soon.
avid_droid said:
Everything is being updated in OP soon.
Click to expand...
Click to collapse
Yep soooon,
But I spend about 3 hours just to come back on oos11.
In a "tested" build !!
Who cares
avid_droid said:
At initial install,use the 0626 dated LineageOs recovery.img. Any newer nightly build losrecovery may cause an issue. After installing recovery and installing system, do not attempt to flash any recovery on device. It messes up the Os. I'm running Stag and FP sensor is working fast and easy on my end
Click to expand...
Click to collapse
LOS RECOVERY 06/26
papad13 said:
Yep soooon,
But I spend about 3 hours just to come back on oos11.
In a "tested" build !!
Who cares
Click to expand...
Click to collapse
3hrs? I can MSM and update to 11.2.9.9 then Beta 1 and up to C.39 in less than an hour.
It's not a test build,testing is over.
I've messaged OP and instructions and files will be updated soon.
Yep ,you are the one yeaaa!!
You have it bigger !!
I can do it to !
But I was trying to install THIS rom ,with different lineage recoveries .
Because even in the first upload of the TS the recovery was for lemonadep (onep9pro)
So no luck .
I had a personal conversation with the dev and he changed it to the newest and right one .
But even this that is uploaded now it doesn't boot.
papad13 said:
Yep ,you are the one yeaaa!!
You have it bigger !!
I can do it to !
But I was trying to install THIS rom ,with different lineage recoveries .
Because even in the first upload of the TS the recovery was for lemonadep (onep9pro)
So no luck .
I had a personal conversation with the dev and he changed it to the newest and right one .
But even this that is uploaded now it doesn't boot.
Click to expand...
Click to collapse
Okay,so, I'll post instructions for you here until VJS updates it with file links.
Disclaimer: I am not responsible if you destroy your device. Method posted is tried and true and will work if directions are followed.
You must be updated to latest,11.2.10.10
Unlock bootloader
Here are the files needed:
Recovery:
https://androidfilehost.com/?fid=14943124697586357860
Copy partitions:
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
In bootloader:
fastboot flash boot losrecovery-0626.img
Reboot to recovery
adb sideload copy partitions.zip
Reboot recovery
Format data
adb sideload StagOS.zip
Reboot and enjoy
Warning: Do not attempt any other flashing of recovery as it may result in having NO OS!
avid_droid said:
Okay,so, I'll post instructions for you here until VJS updates it with file links.
Disclaimer: I am not responsible if you destroy your device. Method posted is tried and true and will work if directions are followed.
You must be updated to latest,11.2.10.10
Unlock bootloader
Here are the files needed:
Recovery:
https://androidfilehost.com/?fid=14943124697586357860
Copy partitions:
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
In bootloader:
fastboot flash boot losrecovery-0626.img
Reboot to recovery
adb sideload copy partitions.zip
Reboot recovery
Format data
adb sideload StagOS.zip
Reboot and enjoy
Warning: Do not attempt any other flashing of recovery as it may result in having NO OS!
Click to expand...
Click to collapse
Yep thanks . I knew all this !!
But it wasn't available in the op.
Even now that the dev knows that if you come from oos12 : no boot.
If you try with the newest lineage rec : no boot