{
"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.
LAST UPDATE: 04 March 2019
Hello guys,
Note: This thread has evolved a lot and now I don't feel it's about my personnal experience anymore. So I've just removed all the bits about myself as they are not relevant and appropriate. You'll have way enough information from the Google sheet as well as the summaries made by the community and myself.
Here you can find a nice spreadsheet made by @Macusercom and improved by @blinkin, the community and general and myself
https://docs.google.com/spreadsheets/d/1OKpuzMbvMLZ8qtyDmbxMUCayUKM3nkuWhH00fRQqfcs/edit?usp=sharing
The spreadsheet is now in read only mode since some funny guys had fun messing with it. If you want to add something to the spreadsheet, just send a message on this thread and I'll add it myself. Don't waste my time / Macusercom's time sending PMs about getting the rights to edit it. Thank you for you understanding.
CAUTION: most of the following is outdated, and while it's usually still true, most ROMs are mature enough to be very similar in terms of performance, battery life and even features. So even more than before, it's mostly about personal preference. The spreadsheet should still be useful however, as long as it keeps being updated.
Lineage OS:(thread link: https://forum.xda-developers.com/oneplus-6/development/rom-lineageos-16-0-t3839750 )★ Positive things
-Great performance
-Great battery life
-A few interesting features not available on other ROMs except HAVOC.
-Only custom ROM where Android Auto works.
-Privacy guard now works
★ Less-positive things (i.e. "bad" things)
-No signature spoofing
-Not as many features as other ROMs
AOSIP (Android Open Source Illusion Project)(https://forum.xda-developers.com/oneplus-6/development/rom-android-source-illusion-project-t3855343 )★ Positive things
-Great performance
-Good battery life
-A lot, but not too many, useful features well ordered, so easy to find.
-OOS camera is included, as well as OnePlus gallery.
-OTA updates
★ Less-positive things (i.e. "bad" things)
?
Havoc OS:(thread link: https://forum.xda-developers.com/oneplus-6/development/rom-havoc-os-t3817805)Feedback from @Macusercom
★ Positive things
- Currently, the ROM with the most features on the OP6. Period. (LiquidRemix has about the same amount of features).
-Stable
- OOS cam with portrait & night mode
★ Less-positive things (i.e. "bad" things)
?
Pixel Experience(https://forum.xda-developers.com/oneplus-6/development/rom-pixel-experience-t3856643 )Feedback from @elmu
★ Positive things
-Great performance
-overall working well
-Low ram usage
-Bluetooth+bullets wireless work very well
★ Less-positive things (i.e. "bad" things)
-Dark theme not working properly?
-Some apps crashes/freezes?
-Camera crashes/freezes?
-Battery stats recording ambient display in your sot alltime (i hope you understand what i mean)?
OmniRom TreskMod(https://www.treskmod.ru/ )Feedback from @dante_nfs
★ Positive things
-Great performance, latency is very good with redflare kernel
-Great battery life
★ Less-positive things (i.e. "bad" things)
-No XDA thread, so hard to follow updates and feedback
-GAPPS included
OmniRom(https://forum.xda-developers.com/oneplus-6/development/rom-omnirom-oneplus6-t3841813 )★ Positive things
-Great performance
-Feature rich
-Leading custom ROM when it comes to fix bugs etc.
-Great battery life
-OTA udpates
★ Less-positive things (i.e. "bad" things)
?
LiquidRemix(https://forum.xda-developers.com/oneplus-6/development/rom-liquidremix-t3840206 )★ Positive things
-A LOT of settings and features
-Great performance
-Good support for MicroG (better than OMNI in my experience)
-Privacy guard is useful for privacy and it's working! You also get advanced permissions control (AppOps) which is neat.
-OOS Cam included
-[Official] so you get OTA udpates
★ Less-positive things (i.e. "bad" things)
-Lots of settings but they are a bit messy, you never know if they will be in /settings/display or /settings/liquidsettings/display for example.
-The theme is a little different to stock Pie. I don't like it as much.
-Fingerprint stops working randomly and the only temporary fix is to reboot device, until it happens again. It hasn't been reported lately so maybe it's fixed.
ArrowOS(https://forum.xda-developers.com/oneplus-6/development/rom-arrowos-t3869015 )★ Positive things
-Very unique experience as most advanced settings are integrated in already existing menus. You won't find anything like "ArrowOS extra settings" and I think it's much easier to find options like that. Also, all custom settings are listed probably when using the search bar.
-Great performance
-Great support for MicroG (similar to Liquid, better than Omni)
-OOS Cam included
-[Official] so you get OTA udpates
★ Less-positive things (i.e. "bad" things)
-No vibration strength control
-Battery drain in standby is important (11% over a night). It migtht be fixed?
I will try to update this post with different feedback and will let you know about my experience on other custom ROMs.
Enjoy your OP6 and our wonderful community of developers, cheers! :good:
I feel like this thread is more about discussion than asking a particular question and expecting a specific answer. If you want, I could reformulate my thread as "Discussion about custom ROMs".
Tomatot- said:
I feel like this thread is more about discussion than asking a particular question and expecting a specific answer. If you want, I could reformulate my thread as "Discussion about custom ROMs".
Click to expand...
Click to collapse
I agreed with you that this is more like a general discussion of ROM, hence it belongs to General Section.
Enjoy!
jerryhou85 said:
I agreed with you that this is more like a general discussion of ROM, hence it belongs to General Section.
Enjoy!
Click to expand...
Click to collapse
Thank you for granting my request! Hopefully, more people will be interested by the thread. I'm going to try to test other ROMs to see if this thread can get any momentum, when I'll have some time for it. :fingers-crossed:
I use stock with xXx module run into on top of it. The stock ROM has the features I need out of the box and the module on top helps supplement the experience. I'm shooting for a reliable stable experience which is why I'm not going to branch off to anything AOSP like.
The OnePlus 5 and now the OnePlus 6 for me have the been the only 2 phones I've never felt the need or want to put a custom Rom on them. The OOS has had just about all the features I used to put a custom Rom on a phone. What I don't get from the OOS Rom I get with ex kernel manager (increase vibration strength, increase max sound and in call volume). The one thing I miss is separating ringtone and notification sounds.
spartan268 said:
I use stock with xXx module run into on top of it. The stock ROM has the features I need out of the box and the module on top helps supplement the experience. I'm shooting for a reliable stable experience which is why I'm not going to branch off to anything AOSP like.
Click to expand...
Click to collapse
Sorry for the OT. But I'd like to know how do you flash it? The module of xXx. I'm very interested in that. Also, what you say is right, OOS gives to us the features that we need
mf117 said:
Sorry for the OT. But I'd like to know how do you flash it? The module of xXx. I'm very interested in that. Also, what you say is right, OOS gives to us the features that we need
Click to expand...
Click to collapse
Nothing special. Just make sure you have Magisk setup and then you flash it through TWRP. The only hard part is making use of the profile file that is needed for making your individual selections. Most people overlook it and then complain because it's using the default profile which gets rid of most things
spartan268 said:
Nothing special. Just make sure you have Magisk setup and then you flash it through TWRP. The only hard part is making use of the profile file that is needed for making your individual selections. Most people overlook it and then complain because it's using the default profile which gets rid of most things
Click to expand...
Click to collapse
But is it easy to use the profile?
Awesome thread idea as I've been meaning to try out some custom ROMs or kernels. As a side note, this is my first OnePlus device and coming from primarily Samsung devices this is the first device I can happily say so far that I haven't felt the need to install custom ROMs on as the experience has been fluid and updates have been quick.
I'm mostly curious about one feature to know whether it is available in either ROM or kernel format. On previous devices Resurrection Remix was my ROM of choice as it offered the customization and performance I needed without much compromise. One feature that I loved having the option for in RR that I sorely miss in OOS was enabling the volume rocker to skip or play the previous track by long press.
I know this is available in the OP6 Resurrection Remix ROM, but I've seen too many bugs reported to consider it a daily driver. I've also heard good things about the Havoc ROM listing it in its description, but from the videos I've seen it doesn't seem to have the fluidity that I love in OOS.
I'm curious if anyone has tried either a different ROM with similar fluidity too OOS with this feature, or if there is any kernel available that has this option. Any information would be appreciated.
mf117 said:
But is it easy to use the profile?
Click to expand...
Click to collapse
Super easy if you can grasp the concept. It's just setting a bunch of 1s and 0s for things you want and don't want
DMan1993 said:
Awesome thread idea as I've been meaning to try out some custom ROMs or kernels. As a side note, this is my first OnePlus device and coming from primarily Samsung devices this is the first device I can happily say so far that I haven't felt the need to install custom ROMs on as the experience has been fluid and updates have been quick.
I'm mostly curious about one feature to know whether it is available in either ROM or kernel format. On previous devices Resurrection Remix was my ROM of choice as it offered the customization and performance I needed without much compromise. One feature that I loved having the option for in RR that I sorely miss in OOS was enabling the volume rocker to skip or play the previous track by long press.
I know this is available in the OP6 Resurrection Remix ROM, but I've seen too many bugs reported to consider it a daily driver. I've also heard good things about the Havoc ROM listing it in its description, but from the videos I've seen it doesn't seem to have the fluidity that I love in OOS.
I'm curious if anyone has tried either a different ROM with similar fluidity too OOS with this feature, or if there is any kernel available that has this option. Any information would be appreciated.
Click to expand...
Click to collapse
Hi, thank you for your post. I'm actually using this feature on LOS. Apart from the few bugs I've listed, this ROM is very solid. Amazing performance (I can tell you, you won't be disappointed) and good battery life as well. You should give it a try, as long as the bugs don't affect you too much.
The HAVOC Rom seems very well maintained, unfortunately, I agree, there are too many features for my simple needs and it probably affects performance as well.
Using the stock rom with francokernel installed, I love the extra features and to have a awesome look I am using the AOD coupled with viper4Ndroid, lawchair launcher,lawnstep and Google framework.
Tomatot- said:
Hi, thank you for your post. I'm actually using this feature on LOS. Apart from the few bugs I've listed, this ROM is very solid. Amazing performance (I can tell you, you won't be disappointed) and good battery life as well. You should give it a try, as long as the bugs don't affect you too much.
The HAVOC Rom seems very well maintained, unfortunately, I agree, there are too many features for my simple needs and it probably affects performance as well.
Click to expand...
Click to collapse
Awesome thread idea ! I am actually about to flash my first rom ! About LOS, are these camera issues that much of an issue iyo ? Or is the camera still usable ?
ilininja said:
Awesome thread idea ! I am actually about to flash my first rom ! About LOS, are these camera issues that much of an issue iyo ? Or is the camera still usable ?
Click to expand...
Click to collapse
Well, it actually happened to me once. I've tried since then to use my camera and never got an issue again. Also, in between there's been an update and since the update I didn't have any bug. So maybe it's fixed, I'm not sure.
If the bug is still present, it's not ideal obviously, but it's ok as far as you don't have to take an "instant" picture (i.e. something you have to take on the moment and not two minutes later).
Also, I don't know if that's related but I didn't have any issue since I've been using the OP6T apk.
So, to sum up, I don't know if:
1) I'm lucky
2) it's the 6T apk which works better
3) it's the last LOS update which fixes the issue
Original post updated with my first impressions on AOSIP.
I'll follow your first post
About Havoc OS: (thread link: https://forum.xda-developers.com/oneplus-6/development/rom-havoc-os-t3817805)★ Positive things
- Many features even border radius of the screen corners
- Stable and no crashes
- OOS cam with portrait & night mode
- Almost all bugs gone if OB6 is used
★ Less-positive things (i.e. "bad" things)
- Notch hide will return on next build (currently not available)
- Battery life (3–4 % standby drain per hour)
- Security patch says September 2018 but I assume it's from vendor and not from the ROM but I can't tell
Macusercom said:
I'll follow your first post
About Havoc OS: (thread link: https://forum.xda-developers.com/oneplus-6/development/rom-havoc-os-t3817805)★ Positive things
- Many features even border radius of the screen corners
- Stable and no crashes
- OOS cam with portrait & night mode
- Almost all bugs gone if OB6 is used
★ Less-positive things (i.e. "bad" things)
- Notch hide will return on next build (currently not available)
- Battery life (3–4 % standby drain per hour)
- Security patch says September 2018 but I assume it's from vendor and not from the ROM but I can't tell
Click to expand...
Click to collapse
Cool, that's perfect! If you don't mind, I'll add your post to the OP.
Tomatot- said:
Cool, that's perfect! If you don't mind, I'll add your post to the OP.
Click to expand...
Click to collapse
Sure thing! I'm searching for a custom ROM with good battery, features and OOS cam. I only used LOS for the past 3 years but I really want the OOS cam
Macusercom said:
Sure thing! I'm searching for a custom ROM with good battery, features and OOS cam. I only used LOS for the past 3 years but I really want the OOS cam
Click to expand...
Click to collapse
The OOS cam is available on AOSIP, you should give it a try. I can't tell about battery yet though.