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.
Vanir is now in Beta for the TF700. We could use some feedback on how it is doing. Currently, we forked CM's device tree + kernel. (this will change based upon feedback)
Currently all TF700 builds can be found in the nightly section for both Vanir and Commotio
_______Goo.im_(Use First)________NuclearMistake's Server
________________________
Support
Support can be found 24/7 on our GooglePlus Community for all 50+ supported devices
Commotio + Vanir Features:
- I am a founding and current Vanir developer. Commotio is my personal take on Vanir
- Toro, toroplus, maguro, grouper, manta, mako, + 49 current devices
- Based on Vanir 4.4 r2_2 nightlies + my Gapps
Status Bar
- Quick Setting including numerous customizations
- Customize clock display and location, customize signal bar
- % displayed in battery + circle mod
- Transparency
Navigation Bar
- Customizable buttons + colors
- Customizable height + width
- Navi Ring
- Transparency
Lockscreen
- Fully customizable targets/rotation/widgets/ and more
- Transparency
General Tweaks
- Ad blocking
- Tablet UI Chooser
- DPI/LCD changer + force tablet settings mode
- Theme Chooser: Including inverted theme
- Galaxy Nexus Parts
- ADB over network
- Bravia Engine 2.0
- Custom Carrier text
- Custom backlight
- Expanded Desktop: with different modes
- Extended Power menu
- A-GPS. - Kang PrimeDirective --> Credit happily1986
- Long press back to kill (in developer options)
- Privacy Guard Manager
Application Tweaks
- Expanded Phone: noise reduction, advanced settings, speaker proximity, blacklists, white lists, enhanced dialer
- Expanded MMS including Quick Emoji
- Camera: Enhanced settings (credit CM)
- Functional Sound Recorder
- Koush's Superuser
- Vanir Keyboard - removed tracking/logging - highly optimized
- Media Scanner options
- Enhanced autobrightness
Performance Manager- Processor governor + speed
- Voltage control
- I/o Scheduler
- Disable boot animation
- Enhance recent menu
Sound
- Quiet Hours
- Highly modified DSP Manager unique to Commotio/Vanir (Credit CM)
- Volume wake / rocker music controls
- Rewritten Speaker proximity designed for Commotio/Vanir
Debloated
- All inclusive ~180 MB --> 60 MB of Bloat removed
- Fully featured LatinIME Keyboard, but only 2.2 MB (normally 16-20 MB), removed tracking/logging
- And soo much more
Butter
- Compiled with linaro keychain.
- Optimized with linaro 4.4.2
- GCC 4.8 w/ -O3 -fstrict-aliasing AKA highly optimized compiling for better results (like Linaro)
- Vanir.cfg - Set your CPU frequencies, colors, ZRAM, and much more. Set and once and forget; it stays on your SD card
- DHOtheory: Sets up the kernel/ROM the way I like it, then self destructs on first boot, so you can change it later
- Go-faster Axiom scripts
- Vanirice - makes everything just a bit smooth
- For every 1 user settings there are 5 power saving + performance tweaks tweaks
Kernels:
- Many devices such as Tuna, GS4, M7, G2, and many more offer custom Vanir kernels
- We use the best kernel choosen by our device maintainers for the current provided kernel please see our GitHub.
Theme
- TRIAGE theme - (Inspiration DroidTh3ory)
Gapps
- No Longer Included. See my Gapps post for further details, and my GAPPs
- Added File Manager + Titanium BU (for easy crack flashing)
- Terminal added
Screenshots:
Commotio 4.1 Build 20 and prior
Commotio 4.2 Build 21 and later
Files: MD5 found on download page
_______Goo.im_(Use First)________NuclearMistake's Server
M# = Monolith/Milestone build
B# = build number
Dirty = update file, does not wipe. Does not change ROM settings or user data.
Install: Easy as 1, 2, 3
Everything is taken care of for you. No need to wipe cache.
1) Download
2) Flash it
3) Profit
XDA:DevDB Information
[ROM] Vanir/Commotio TF700 , ROM for the Asus Transformer TF700
Contributors
DHO, PrimeDirective, NuclearMIstake
ROM OS Version: 4.4.x KitKat
Based On: VanirAOSP
Version Information
Status: Testing
Beta Release Date: 2014-05-25
Created 2014-05-26
Last Updated 2014-05-25
This is great. I use Vanir on my Flo, Yuga, and Hammerhead.
Sent from my ASUS Transformer Pad TF700T using XDA Premium 4 mobile app
Hi,
first many thanks ... :highfive: Am very happy to see this rom here.
Did a clean flash, your (DHO) gapps ... everything fine until now.
A small (optical) thing. The on/off buttons are not visible in the settings.
But only in landscape... Screenshots attached
Once again, many thanks. Looking forward .... :highfive:
And the Updater in the QS -> jumps to the status bar, but I think you know this.
edit: dual panel mode is ok ...
Will continue testing tomorrow.....
MotoFlasher said:
Hi,
first many thanks ... :highfive: Am very happy to see this rom here.
Did a clean flash, your (DHO) gapps ... everything fine until now.
A small (optical) thing. The on/off buttons are not visible in the settings.
But only in landscape... Screenshots attached
Once again, many thanks. Looking forward .... :highfive:
And the Updater in the QS -> jumps to the status bar, but I think you know this.
edit: dual panel mode is ok ...
Will continue testing tomorrow.....
Click to expand...
Click to collapse
I am trying to fix this now,... been a long time since I touched this part of the theme, so it is slow tracking it down,.. I need to curbside a themer
Compiled with Grimlock's for tonight. Seems smooth so far.
Using my own kernel based upon Grimlocks
Raises quadrant 1500
raised antutu score 1000
Nebulous scores aside it is very much noticeably faster
Nice & thank you for bringing us a new ROM. Do you support f2fs in the kernel? I've flashed mine with it an it makes this thing smooth, just wondering if I have to revert back to try vanir.
Thanks again
###Edit####
Looks like next grimlock kernel version will support f2fs right away. I may have to wait a day or 2 to see how this progresses. Thanks again
mikew29 said:
Nice & thank you for bringing us a new ROM. Do you support f2fs in the kernel? I've flashed mine with it an it makes this thing smooth, just wondering if I have to revert back to try vanir.
Thanks again
###Edit####
Looks like next grimlock kernel version will support f2fs right away. I may have to wait a day or 2 to see how this progresses. Thanks again
Click to expand...
Click to collapse
I am working on F2F,.. we are trying to do it properly the first time. Over the next week I would not be surprised to see test versions coming out.
Sweet! Thanks and I look forward to seeing the builds.
mikew29 said:
Sweet! Thanks and I look forward to seeing the builds.
Click to expand...
Click to collapse
Awesome, thank u
WOW, I just seen this. Vanir soon to be on my TF700 as well as my N7 and soon on my G2. Thanks DHO.
Sent from my VS980 4G using Tapatalk
Dock SDcard is not read.
It's detected when plug or unplug but not seen by any app.
Edit : Dock SDcard OK after new install.
Great rom ! Thx for it.
ghenarys said:
Dock SDcard is not read.
It's detected when plug or unplug but not seen by any app.
Edit : Dock SDcard OK after new install.
Great rom ! Thx for it.
Click to expand...
Click to collapse
Glad it's working
Works for me
Hey @DHO I'm going to finally unlock my bootloader for your ROM as it's probably the best on the tf700. Just wondering if it was compatible with F2FS or whether you plan to integrate it. Also are there plans for pie?
AJM-hackers said:
Hey @DHO I'm going to finally unlock my bootloader for your ROM as it's probably the best on the tf700. Just wondering if it was compatible with F2FS or whether you plan to integrate it. Also are there plans for pie?
Click to expand...
Click to collapse
Vanir + the kernel is fully F2FS compliant, but I have not tried implementing it on tf700... mainly b/c I do not have the time to backup and properly test. If you want to guinea pig I can whip out a build.
Or users can make a few tweaks to enable it (since the system is okay with it)
DHO said:
Vanir + the kernel is fully F2FS compliant, but I have not tried implementing it on tf700... mainly b/c I do not have the time to backup and properly test. If you want to guinea pig I can whip out a build.
Or users can make a few tweaks to enable it (since the system is okay with it)
Click to expand...
Click to collapse
Sure, I'll guinea pig it . I don't want to use the other switch method in the forum method because I want to keep the stock commotio kernel because it's probably the best on the tf700.
DHO said:
Vanir + the kernel is fully F2FS compliant, but I have not tried implementing it on tf700... mainly b/c I do not have the time to backup and properly test. If you want to guinea pig I can whip out a build.
Or users can make a few tweaks to enable it (since the system is okay with it)
Click to expand...
Click to collapse
I saw some commits in the changelog? Does it have F2FS-all already built in now?
AJM-hackers said:
I saw some commits in the changelog? Does it have F2FS-all already built in now?
Click to expand...
Click to collapse
I still have not tried... the bones are there....
I need more time
DHO said:
I still have not tried... the bones are there....
I need more time
Click to expand...
Click to collapse
Thanks for the heads up take all the time you need. So just to confirm, there's no way of keeping the commotio kernel whilst f2fs?
What's the most recent stable version?
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on CyanogenMod so use custom kernels compatible with them!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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.
*
*/
All the source code for crDroid is available in the Github repo. And if you would like to contribute feel free to pull a request.
Rom features
Nav bar tweaks (on/off toggle and custom dimensions);
Battery text mode (from cm);
Battery icon options (from cm);
Media scanner behavior on boot;
HSPA + icons on status bar;
SlimRoms heads up customization;
Traffic metter on status bar;
Gesture lockscreen;
Gesture anywhere (launch apps and activities from custom gestures);
Weather display on expanded status bar;
Wakelock blocker;
Left handed navbar option;
XuiMod toast animations;
AOKP custom system animations;
App circle sidebar;
CPU info overlay option in development settings;
[Connect/disconnect notification support;
Long click support on quick settings;
Screen recorder;
Animated rotation tile;
Wake up on plug;
Development shortcut;
Performance settings from CyanogenMod;
Clock and time clickable in expanded status bar;
Notification ticker;
Quick unlock;
PIN keypad shuffler;
Custom lockscreen shortcuts;
Answer calls with hardware home button;
Status bar clock tweaks (right, center or hide clock with many dates formats to show. Custom colors included);
Notifications counter;
Volume keys wake the device;
Ability to hide the alarm clock icon from status bar;
Dialer Lookup;
Profiles form CyanogenMod (new merges and lollipop style);
Protected apps (using trebuchet launcher);
Filter spam notifications;
CyanogenMod SuperUser;
Clear all button in recent panel with custom option (hide, top right or top left);
Disable search bar in recents;
Privacy guard from CyanogenMod with new Superuser access through it!!!;
Ability to hide superuser status bar icon;
Quick settings pull down with one finger (right, left or off);
Smart pull down;
Configurable 0, 90, 180 and 270 degree rotation;
Toggle to not allow quick settings on secure lockscreen;
Brightness control through status bar;
Double tap status bar sleep;
Data activity indicators;
Call blacklist support;
Increasing ring tone;
In call vibrations;
Ambient display (DOZE features);
Advanced reboot menu;
Option to hide adb notification;
Screen shot quick delete with confirmation;
Long press back to kill with configurable timeout;
Volume button custom actions (skeep track, wake screen, adjust sound and keyboard cursor control and swap volume buttons);
Less frequent notifications sound;
Advanced keyboard features (auto rotation with timeout, disable full screen, selector notification, show enter key, volume key cursor control);
New Eleven music player and AudioFX from CyanogenMod;
Among others. For more infor visit our github
Screenshots
http://crdroid.org/?page_id=472
crDroid official website
http://crdroid.org/
Download
Rom:
crdroid-5.0.2-20150331-ariesve
Google Apps:
https://s.basketbuild.com/gapps
How to install :
Use TWRP. with new partition
Warning: Only use this recovery to flash New build with new partitio layout.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
Wipe data and cache.
Format /system (only first time coning from older recovery)
Format /data and /data/media (only first time coning from older recovery)
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade the since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Builds and full support:
https://plus.google.com/communities...aa3e7d81-bf88-4973-9638-d5b0cd003b2d?hl=pt_br
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such Xposed!
- have modified system files
Source on Unofficial github
» Device
» Vendor
» Kernel
» audio-caf | display-caf | media-caf
XDA:DevDB Information
CrDroid Lollipop, ROM for the Samsung GT-I9000 Galaxy S
Contributors
K_TECH, DevConnection_Team, Christopher83
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2015-01-20
Last Updated 2015-04-02
Unofficial Changelogs
UNOFFICIAL CHANGELOGS
Code:
[B][SIZE="4"]2015/03/31[/SIZE][/B]
-Sync with device tree (Device, Vendor, Kernel)
-Sync with source
[B][SIZE="3"]Old Build[/SIZE][/B]
[HIDE]
[B][SIZE="4"]2015/02/12[/SIZE][/B]
-Sync with device tree (Device, Vendor, Kernel)
-425MB of RAM *Christopher83
[B][SIZE="4"]2015/01/19[/SIZE][/B]
-Initial release for ariesve
-Using K^kernel source as stock kernel (416 of ram) by Christopher83
-Remove CellBroadcast from build
[/HIDE]
ANNOYANCES
Code:
[B][SIZE="4"]2015/03/31[/SIZE][/B]
-Tell me please :p
Many thanks to @ahmed dzico for testing it
Hope you guys enjoy this one ^_^
Thanks bro for your hard work :thumbup:
Nice to see some more Lollipop ROMs for our device, beside CM12. Good work !
Maybe you could work together with @davidteri91 , he was also planning to do a CrDroid build for our device I think.
MajorD. said:
Nice to see some more Lollipop ROMs for our device, beside CM12. Good work !
Maybe you could work together with @davidteri91 , he was also planning to do a CrDroid build for our device I think.
Click to expand...
Click to collapse
Yeah i know it, If david release his official CrDroid for this device, i'll stop this project.. about collaboration with him. i think i can't, dont have skill enough to manage it all, and i like to use Unofficial release. Why? Because i can add/remove that i dont like it in Official release such as CellBroadcast.apk, OTA updater, etc
Is it difficult to build on your own?
I'm new in this and would like to give it a try.
Besides thanks for the unofficial build.
K_TECH said:
[*] Use CWM6.
Click to expand...
Click to collapse
I suppose it contains an error. Please correct if I'm right, because someone could really use a recovery-clockwork-6.0.5.1-ancora.
ze7zez said:
I suppose it contains an error. Please correct if I'm right, because someone could really use a recovery-clockwork-6.0.5.1-ancora.
Click to expand...
Click to collapse
Thanks
OP edited, sorry about that
Well, davidteri91 will give us Official support for our device. If it exits i'll discontinue this project
davidteri91 said:
Hi people today I start with the work for sammys msm7x30 soon I will contact with you
Click to expand...
Click to collapse
Thanks in advance
What's all that fuss about android 5.0, I tried few recently, but they all feel oversimplified, with less functionality, although the CrDroid Lolipop feels smooth (antutu benchmark scored over 13.000), but anyways I miss some of the nice features and cool looks that some of the latest kitkat roms had. To name a few, you cannot take pictures with camera by pressing power button, changing the looks of the clock in the lockscreen doesn't seem to work, also could'nt find where I could add the shortcuts on the lockscreen. However I am very glad to see new roms for my beloved sgs +, thank you.
nezhinaw said:
What's all that fuss about android 5.0, I tried few recently, but they all feel oversimplified, with less functionality, although the CrDroid Lolipop feels smooth (antutu benchmark scored over 13.000), but anyways I miss some of the nice features and cool looks that some of the latest kitkat roms had. To name a few, you cannot take pictures with camera by pressing power button, changing the looks of the clock in the lockscreen doesn't seem to work, also could'nt find where I could add the shortcuts on the lockscreen. However I am very glad to see new roms for my beloved sgs +, thank you.
Click to expand...
Click to collapse
CM is working to merge the features from KK but it needs time and patience....
A few days ago they merged the Theme Chooser engine which in my opinion is a very big step.
At the moment the priorities are to have first a stable build suitable for daily use, after that we would also talk about new features.
Alright, sounds promising, thank you, keep it up
Good work, the rom feels smooth and fast :good:
Problem in "Language & Input"
There's a problem in "Language & Input" , the "Android Keyboard" not working
hi
is there theme features in this rom
Update!!
UPDATE
Download link First Post
Changelog Second Post
Enjoy it guys!!! ^_^
Hello,
If you're updating a CM 12.0 released after 21/12/2014
Reboot inside recovery (always the new one)
Install the rom update
Reboot the system
Click to expand...
Click to collapse
Updating from previous crDroid version by this method will work?
I used only dalvik and cache wipe in addition to method above and it looks working to some extent.
Hey, I'm really happy that you made ROM for this phone, but i need your help with installation. I've downloaded your ROM and GAPPS, i made a backup of last ROM (just 2.3.6 stock) and I formatted Data, Cache, Dalvik, System and Internal. I tried to install your ROM with(out too) wiping data/dalvik after installation and I'm getting the same error all the time. When I'm booting, I'm getting information that my data is corrupted and I have to make a factory reset by button on screen. I doesn't make any changes, next boots are the same.
Of course I'm using TWRP which you mentioned in your post.
EDIT: I was installing latest verion.
Does this rom work for the i9000?
{
"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!
Code:
/*
* Your warranty is now maybe void.
*
* We are not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
About Project
Reloaded-CAF is a Custom ROM which is based on CAF. The main aim of this ROM is to bring stock AOSP experience as much as possible while maintaining performance, smoothness and good battery backup. I hope that you'll all love this project, and help us, shape it even better. Meanwhile, all of our sources are publicly available on our Github. Hope you enjoy your stay and like our work on Reloaded-CAF. We did add some features to improve the overall experience.
What's CAF?
Code Aurora Forum (CAF) is a consortium of companies with projects serving the mobile wireless industry. Software projects it concerns itself with are e.g. Android for MSM, Femto Linux Project, LLVM, MSM WLAN, and Linux-MSM. Code Aurora is basically AOSP + Qualcomm specific enhancements and optimization.
Features:
* Buttons
Enable/disable navbar
Invert navbar keys
Volume key wake
Volume key music control
* Status bar
Battery style options
Clock customizations
4G/LTE toggle
VoLTE icon toggle
Quick pulldown
Network Traffic Indicator
QS row/column settings
* Lights
Battery lights/Notification lights toggle
LED pulse when battery low toggle
* Display
System-wide dark mode
Accents color options
Proximity check on wake
Double tap to sleep on statusbar and lockscreen
* Sound and vibration
In-call vibration options
Ringtone chooser for 2nd sim card
Fingerprint authentication vibration
Screenshot sound toggle
Toggle for silent notifications while screen on
* Security
Advanced Reboot menu
AppOps
* Lockscreen
Disable qs on secure lock screen
Pin quick unlock
Auto Face unlock
Charging info
* QS Tiles
Power
Sync
Heads up
Caffeine
Screenshot
* Gestures
3 Finger swipe for screenshot
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
Volte.
Known issues:
You tell me
Instructions :
Download the latest build and GApps
Reboot to recovery and wipe system, data, cache, dalvik
Flash Pie vendor and Firmware, if you are on oreo vendor
Flash the latest build and Gapps
Flash magisk, if you want root access (optional)
Reboot
Downloads :
Reloaded-CAF: CLICK HERE
OpenGapps [arm64/9.0]: CLICK HERE
Telegram Groups:
Reloaded Telegram Group
Redmi Note 6 Pro Telegram Group
Redmi Note 6 Pro Telegram Channel
FAQ
Why is the security patch older than the latest AOSP patch?
CAF focus on delivering the latest hardware patches and are usually about a month behind Google on security patches, on the other hand, Google is usually a month or more behind on them on caf patches (sometimes months). No point in complaining about it, if you want the latest security patch, go with an AOSP based rom (like LineageOS), if you want latest Qualcomm optimizations for our hardware as well as fixes, go with caf, it's as simple as that.
Kernel Source: HERE
Device Source: HERE
And huge thanks to @fernandÃOdj for testing
XDA:DevDB Information
Reloaded-CAF, ROM for the Xiaomi Redmi Note 6 Pro
Contributors
@Pavanpatel @riteshsaxena @blackman01 @rama982
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Pie
Based On: CAF
Version Information
Status: Initial Release
Release Date: 2019-05-31
Created 2019-05-31
Last Updated 2019-09-31
Build Date 31-5-2019:
• Initial Build
Some Screenshots:
Perfect rom. You must try. Perfect, nice, good ROM perfect perfect perfect. I liked.
---------- Post added at 10:05 PM ---------- Previous post was at 10:05 PM ----------
please come on
Battery usage not wiping!!
Which camera is this rom using? Thanks!
Cioffaz said:
Which camera is this rom using? Thanks!
Click to expand...
Click to collapse
Looks a lot like Gcam, really simple camera with few options.
deathhall said:
Looks a lot like Gcam, really simple camera with few options.
Click to expand...
Click to collapse
I've read in many posts and telegram group that activating gcam is a bit tricky on tulip. Can anyone confirm that the camera (gcam) is working fine?
It also seems to me from the screens that there are two cameras...am i wrong about it?
Many thanks!
Cioffaz said:
I've read in many posts and telegram group that activating gcam is a bit tricky on tulip. Can anyone confirm that the camera (gcam) is working fine?
It also seems to me from the screens that there are two cameras...am i wrong about it?
Many thanks!
Click to expand...
Click to collapse
Besides chrome, these are the default apps that was with the latest ROM and gapps (nano). The camera is the first screenshot in the 2nd post, the one in the second to last screenshot wasn't included in the ROM. The apk just lists it as com.android.camera2
Really good rom, been using reloaded for 2 days now. And i think I'll use this as mu daily rom.
Anyway, i hope reloaded development for tulip will continued just like other rom
How abt the battery backup how many hours of sot can expect from this rom
galileogarin said:
Really good rom, been using reloaded for 2 days now. And i think I'll use this as mu daily rom.
Anyway, i hope reloaded development for tulip will continued just like other rom
Click to expand...
Click to collapse
It's getting continued till the time i own this device so don't worry we have a long journey to cover.
[email protected] said:
How abt the battery backup how many hours of sot can expect from this rom
Click to expand...
Click to collapse
It's totally upon your usage. So it's better try out yourself and let us know as well.
My new daily driver. Perfect rom, thank you!
Which Gcam is best suitable for this ROM? And what recovery should I use?
best rom i.ve tried
nullspirit said:
Which Gcam is best suitable for this ROM? And what recovery should I use?
Click to expand...
Click to collapse
Use latest unofficial twrp by @rama982
https://t.me/tulip_updates/1014
Pavanpatel said:
It's getting continued till the time i own this device so don't worry we have a long journey to cover.
Click to expand...
Click to collapse
Whoa dude, Nice to hear that. ??
A new build is available for download.
Build Date: 18-06-2019
Changelogs:
• An improved theme engine with a lot of new accents colors and a black theme.
• A new and improved launcher with google feed integration, icon pack support, icon size customization, gestures support, etc.
• Added support for microg.
• Fixed booting with Encryption.
• June security patch merged.
• Updated ANT+ vendor blobs from lavender
• Added boosted frameworks
• Update mlipay blobs to 1.1
• Drop mi sound enchancer
• Maybe something more
Download: FROM HERE
Please support me by donating: Paypal
Join the team: Click Here
Enjoy.
Double tap to wake doesn't work on the latest build.
Anyone facing same issue?