{
"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.
Related
Hey Guys...
A few month passed since my last release.
But now it's time to show you, that i'm still working on it!
I ported MIUIv4.1 to our milestone.
It's still pre alpha but it's stable enough to boot ^^
Bases:
CM10: CM10 2012-10-29 with 2ndboot
MIUI: NEXUS S 2012-10-26
there are still a lot of things that doesn't work but i'm working on it.
Have Fun ^^
http://android-files.de/kostom/ota/MIUIv4JB/MIUIv4_MS_DE_EN.zip
it might be, that i'll be a bit slow on update here... but if there is an update you'll see it on android-hilfe.de.
thx for sharing
Thanks. I have been looking for MIUI V4 ROM.
Could you please list out, what all working and what all not.
My main concern is performace.
I've flashed it just before.
Unlock screen was super laggy, no virtual keyboard appeared on PIN entry (hat to use the physical) and now it's stuck after language selection with a non-responding settings-app.
When the prompt to wait or kill settings app comes up and I select kill the Gmail app dies to and I'm thrown back to language selection.
Don't get me wrong - I know that this is still an extremely early stage of the ROM and I appreciate your will to port MIUIv4 to this ancient device.
So kudos for making it this far :good:
Keep us updated
after language select i must wait about 10 sec. to get to the next screen
but i used my 98swapon script from the first start
i post my quicktest report on a-h.de in german, cause my english is not the best
the rom is very laggy at the moment and many apps fc instadly but for the first try its realy good, but laggy
It reminds me of the first cm10 builds. They were as laggy as this rom but with time/work/care cm10 builds are usable as a daily driver.
It would be awesome if this will be as usable as cm10 in some months. :fingers-crossed:
Please keep on working on it and thanks for sharing it. :good:
any one tested his ROM 4.0.1?
there some bugs and the rom is laggy but nice to see miui 4 an milestone...
for me its just for test use at the moment
Any updates on this project?
I don't think so. Too bad.
Well, yes it is pretty sad, but I understand that. It must be difficult to develop an outdated phone, while so many better devices are being released every day. Anyways, thanks ManCloud for your support.
{
"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"
}
Welcome to the All New RC Elite Teams S5 Port.
We have worked a new base, now completely NE6 based with NG3 based apps. Search search search, that's the first rule of posting here, if your issue has been posted, don't bother posting the same issue again. If you post any issues previously stated (which means you did not do a search or read the whole thread) it will be ignored. If you have a issue PLEASE post a logcat so we can help, instructions to follow. As with any ROM we are not responsible for any permanent damage to your phone or life, we do this as a hobby and have real life jobs(some of us are students ).
RC Elite Team:
@cdmvirt
@stash9123
@tyre777
@Kevin_1351
If you enjoy this rom please consider DONATING
LOGCAT INSTRUCTIONS:
Spoiler
Download: ADB Tools (credit to Snoop05)
Install process:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot or N/No to skip
3. Press Y/Yes to install ADB system-wide or N/No for current user only
4. Press Y/Yes to install Drivers or N/No to skip
5. Continue Driver installation
6. 15 seconds passed - finished!
Download: LogCatTools4.0 (credit to FuzzyMeep Two)
Just unzip and run as ADMINSTRATOR, follow on screen instructions, all logs will be placed in c:/logcat
Click to expand...
Click to collapse
Screenshots:
S5 themed Android L Keyboard by @kevin_1351: (fixed in 17.1.2)
So, what's all this about?:
After more than 3 weeks of hard work we're finally ready to present you the brand new v17 version. Now with an amazing Aroma installer that, based on your device model, installs the right fixes to make it fully working with your particular Note 3. You can also, if you're using the international Note 3, select from many of the leading kernels out there and much much more. We've also managed to get it even a little bit ram friendlier and have removed many UI errors and annoyances.
But no, we aren't finished yet my friends. We have also included a fully integrated OTA update system that will notify you in case there are some updates (to be found in Settings). Also in Settings there is now - assuming you've installed Xposed Framework- an Xposed button integrated into settings. And right now you're about to ask: "Well, what about Appops?". Well that's there too!
We've tested it for a long time now but if you manage to find some bugs don't even bother to post them here before you have:
A.Used the provided logcat app to gather the log.
B. Searched if someone else already has mentioned it.
ALSO:Please state if you have performed a full-wipe aswell every time you report a problem. And for ota flashing issues use TWRP.
What variants does this rom work on?
N9005, N900T and N900W8
What's missing/Not working?
Bluetooth tethering (?)
Video calling (probably will get fixed, can't promise it)
Display mirroring (update: Well it seems that our provided fix didn't fix it... We'll work on it)
Direct pen input/Writingbuddy (needs major smali editing, would be easier once a new note device comes out)
Wifi-timer(coming soon with ota)
Multilanguage (will also be available as a separate post-installer really soon)
Fully functional S5 themed google keyboard (coming soon)
Download booster/Wificalling toggle (coming soon)
Private mode (won't work because it's deodexed)
ART (same)
S5 camera. It works but it it will forceclose when trying to launch it with a sview cover. Some other functions are missing to, but most of it is trivial. Waiting for @fahadali to fix it.
MHL/HDMI (maybe tyre will be able to fix it)
Possible future additions:
Optional battery themes
Autocallrecording
Aroma installer that remembers your last choices
More air-command themes
Rebase on the newest International firmware
Optional multidpi setting app integrated in settings with respective modded TW apps to fully support true multiDPI
Torch settings
RC-ELITE app with all customisation settings in one place
So with that being said, here we proudly present:
READ THE IMPORTANT NOTES FIRST(below), before downloading!
DOWNLOAD LINK HERE!
MD5: 470d0a60e0a3f5131292462f8a60a3bb
Please take an extra note: Although this IS STATED in the aroma installer. Some users simply do not want to follow it. You have so perform a fullwipe (included in aroma) to make this ROM fully work. Please do not, as some users already have, waste our time with errors that could have been avoided by following our instructions. A fullwipe is only needed once, and won't be needed with the coming OTA updates.
And one more thing: It is strictly forbidden to post any reuploads or direct-links of our rom or ota updates. Anyone doing so will be reported. Please respect this. We have our reasons.
We also strongly recommend to download and install the latest GAPPS (Full modular package) after installing the ROM
RC-ELITE TEAM S5 ROM - V17.0
A brand new way of installing, giving you many options to choose from.
Universal for all snapdragon phones. Includes custom fixes for each model.
OTA-UPDATES. Yeah that's right, you'll get updates on the fly now.
All apps - besides settings - are updated to the newest NG3 UPDATE.
5-digit code fix,
Removed that annoying TOAST after boot, the one stating image-with-text
I also themed the new Android L keyboard to look more inline with the S5's color palette
Tweaked csc files
Removed some toggles
Optional beta mirroring fix
Apk cleanup, more free ram
New launcher grid options
Added Themechooser, App opps and Xposed-Framework to Settings
Advanced powermenu with screenshot and flashlight
Optional Viper4android sound engine
Optional Build.prop tweaks
RC-ELITE TEAM S5 ROM - V17.1
Changes the position of the Xposed icon under Settings
Removes the annoying battery cover popup
Updates the Settings version number to v17.1 (lol)
RC-ELITE TEAM S5 ROM - V17.1.1
Fixes the signal bar issue - sets them to 4
Fixes Sms delivery issue in CSC
Removes the iOS7 signal bar, still selectable in this OTA
Makes the background for native android selection windows darker
Fixes the Mail syncing
Optional Memo app
RC-ELITE TEAM S5 ROM - V17.1.2 - COMING SOON -
Android L apps LPV81C (on hold for now)
Android L sounds/ringtones
Optional sexy Android L bootanimation, grrr
3-minit battery mod implemented by @tyre777 with 2-3 themes custom made by @kevin_1351
Fixed google apps (no more FCs that has been an issue for some people)
Fixed 4g/lte and download booster icons for some people
Updated official Android L keyboard
Optional S5 themed Android L keyboard with optional number row (NOW FULLY WORKING) by @kevin_1351 (adding number row too)
N9005 Kernels updated to the newest versions
Wifi fix for some N9005 devices (with different chips?)
Google Everywhere fix
Limits the max volume to prevent crappy sound quality during alarms etc
Adds download booster toggle back, and if you're on a g900t dwnbooster toggle AND wificalling toggle
Modded the bigger launchers to have the Folder text aligned with the Icon's.
Dev Options on by Default in Settings
Optional dark Music app
Torch in Settings (still not implemented)
New Android L roboto font
Optional infinite tw launcher Scrolling
Note 3 Settings and camera (S5 themed) - useful for missing Options like dock Settings etc
A lot of csc fixes/additions
Added all past Galaxy lockscreen effects
PLEASE READ the personal note below. 2nd post.
UPCOMING OTA Update:
New settings base app with Wifitimer in advanced wifi settings.
Multilang - which will be offered as a separate optional installation.
17.x.x updates will all be small OTA updates!
Important notes:
IMPORTANT:
Although this should be obvious, you need to be on a 4.4.x firmware first. So update to a new samsung note 3 firmware based on 4.4.x before flashing our ROM. Don't even try to experiment with this. You'll just waste your/our time.
Regarding ROM reflashing:
If you want flash any other kernels or apps since your first install. Just flash the main v17.0 again without performing a full-wipe. You will have to reflash the latest OTA update aswell.
Regarding gps problems when returning to normal rom:
tyre777 said:
(...) MAKE SURE YOU HAVE GPS in DEVICE ONLY or HIGH ACCURACY before flashing any note 3 rom so that the GPS bug/ problem won't happen
Click to expand...
Click to collapse
Regarding the THEMED Google Keyboard:
Fixed in 17.1.2.
About Xposed Framework:
Please DO NOT recover Xposed from a backup OR install it in any other way! It's already included in Aroma. IF you install it you will end up with two apks! This is because the provided Xposed apk is modded to not show it's icon. The icon as stated above, is now integrated in Settings.
Regarding the time sync delay:
This isn't our fault. To fix it, go to Settings>Lockscreen and set Dual-clock to OFF. That will "fix" it. For any further complaints about this. Go to Samsung.com
Regarding "wifi is not working" issues:
Update your bootloader to NF4 via ODIN. Google it if you don't know how to perform this task. (Of course I'm talking about the one for note 3, NOT the S5)
Regarding the themes app forceclosing:
If you HAVE NOT selected any themes at all in aroma. It will forceclose. In the new aroma I will make sure that "themes" doesn't even get installed if don't select any.
Regarding random reboots:
This isn't really our fault either. It's a kernel issue. Flash the stock kernel. Most people like @kevin_1351 don't have this issue at all with any kernel whatsoever. But some may have them. Now you know.
Regarding lockscreen related problems like pinlock issues:
We've encountered more than 3 users with this problem. In all cases the solution was to use a pit file to completely repartition the Note 3 (internal SD will also be wiped). Don't be mad if it doesn't work, but we have more and more evidence that it works.
One important thing though is that securelock time only comes up when you have a pin selected and not just set it on swipe. @kevin_1351 fist believed this was a bug due to other v6 ports having it enabled on swipe aswell. After further research though it became clear that it's actually behaving as is should. Also, it is normal in android for the screen to not lock directly after it shuts off. It's made in order to lessen the frustration when you're reading for instance. If you want instant locking you'll have to use a pin and set the proper settings. It's actually not our business to specify this but we taught it might come in handy to know.
OTA updates:
Yes, this ROM provides you with OTA updates, you'll find it in Settings. We initially had problems with this because we were using DropBox. Now @cdmvirt has provided dedicated servers to fix it once and for all. He has payed for this out of his own pocket's (for the most part) so please show him some appreciation.
Also, you don't need to keep the old OTA updates. Just keep the latest one in case you want to reflash some options.
For all issues regarding flashing OTA updates, be sure that you're using the TWRP recovery (v2.7.2.1 or newer). We will not provide support for the other recoveries (although in the most cases you can manually flash it by navigating to OTA folder).
Here is the N9005 TWRP Recovery page btw: CLICK ME!
For issues regarding the OTA download: please delete the OTA folder first and try again.
BETA channel:
With 17.1.2 you will be asked to select if you want to take part of the BETA program. If you choose that you will get faster OTA updates with the downside of them being unfinished, without aroma and may contain some bugs. This is only for the more advanced user. With other words you will have to know how to handle adb, root explorers, being actually mentally able to READ; that sort of stuff. Nothing major but still more than the average joe knows about.
Taking part of the beta program also comes with responsabilites. You'll have to report whether or not the new features and fixes work and be quite specific about the outcomes. The beta versions will contain a "b" at the end of the version number. If you choose to take part, don't complain about stuff not working but instead try to be productive.
Live-support:
Sadly XDA doesn't provide us with any chat system, which we really would love to see in the future btw. Therefore @cdmvirt has integrated a chat system in order for you to get live support from either us or other users. Follow the download link to get there.
Credits:
@ksr007 - for the 5digit smali, thanks mate
@hsbadr - for his smali teachings, help and guidance!
@klenamenis - for his build.prop editing script
@SkywalkerZ - for the big launchers
@seshmaru - for Vrtheme
@g00h - for his amazing build.prop tweaks and for helping me with AppOps, sorry mate how could I forget...
@gharrington - for his 3minit battery tweak (coming in 17.1.2)
OMEGA team - for the wipe script (for inspiring me how to do it)
OTA UPDATE CENTER- @M3nti0n - for their app, which is NOT ours.
And many more (will update the credits soon).
Donations:
None of us are into this for the money. But we've got server costs (for the OTA dedicated server) to pay for and we really have spent countless hours on this. This simply is a fact. It's not a simple task to do what Samsung should have done at our place. It requires weeks of studying, trial and error and lots of coffee. We do this for fun and for the challenge that comes with it. But it goes without saying that we also would like some appreciation for our work. Either by just a thanks or by a small donation. As for everyone saying that they're too poor and/or are students. Well 1$ is nothing and if you own a Note in the first place you should be able to spend 1$ more dollar on this aswell. Some of us are students too, so we know what we're talking about. But hey, this is XDA. You're free to use it without paying a cent, but at least try to show some appreciation for it.
Old base downloads:
Code:
V17.0
Thanks to the ~24 people who have donated. (04.09.14)
As of now (04.09.14) more than 1617 people are on 17.1.1.(active users from all Note variants)
XDA:DevDB Information
RC ELITE S5 PORT, ROM for the Samsung Galaxy Note 3
Contributors
kevin_1351, cdmvirt, tyre777 , stash9123
ROM OS Version: 4.4.x KitKat
Based On: Stock S5 Frimware
Version Information
Status: Stable
Current Stable Version: 17.1.1
Stable Release Date: 2014-08-06
Created 2014-08-07
Last Updated 2014-09-14
Personal (Kevin_1351) related stuff:
- here I'll add stuff that doesn't belong in the official post -
Extra Credits:
Thanks @Shaftamle for helping me with my themed keyboard (He told me how to fix it). Go and check out his keyboard themes btw!
Many thanks to @fahadali2315 for the "Hell NO!" vote. lol and for initially helping me getting up on my own legs.
N9005 Specific downloads:
I've added the NF4 bootloader for wifi in this post.
I've also added a PIT file if you want to COMPLETELY format your phone. Use this with odin aswell. Be careful though, and read up on what it does. This is only to be used with a stock Note 3 .tar.md5 firmware. If you have pinlock issues with our ROM for example: this is needed.
The pit file is going to create a >50kb partition. With other words, is gonna make room for all types of csc. As I said though, read up on this.
Please keep one more thing in mind: The PIT will erase the internal SDCARD as well.
About the next OTA update:
Probably, v17.1.2 -or whatever version number it will have- will be my personally last update(I'll be around and help my team but I won't be this active anymore). Until now tyre and I have been the ones working the most on v17, while cdmvirt has been the one who together with stash made v16, the very foundation of v17. Lately his dedication has partially shifted to his webportal instead, and to the dedicated servers we use for the OTA and for his portal. Now when spending that much time on the rom, it hurts to see how cdm is still struggling with serverside issues and has to pay out of his own pockets in order to maintain it. Especially considering the enormous user base we've gathered in only a week. It seriously disappoints me to see people being ungrateful and complaining about something, but on the other hand don't offer the help in order maintain their desired quality.
This isn't the only thing though, I've received over at least 50 pm complaining about stuff that we don't have anything to do with. User errors or even worse, the fact that people can't even spend 10 min of their time on reading the main post through. This considering the 7 weeks we've spent on this. I've been really active in the iOS scene once and I can tell you, THIS was a totally different story. Night and day. I've heard that XDA has changed, that it has once been the place I'm speaking about. Idk. This is not meant to be offensive in any way. There are a lot of grateful and helpful people too. But they are as rare as truffle. And another factor is that I simply don't have this much time to spend on it either.
I won't leave as I said. And I will really try to help my team further, if they feel like they want to continue. But I won't put this much effort into it anymore. Because it's not being answered back.
I hope you'll understand my frustration. I'm surprised that the ones directly involved like cdm himself just take it, and thinks it's ok. For me at least this is NOT ok.
Due to time constraints and the fact that we want to obtain a bugfree experience, there still are some things I need to figure out in order to flash this OTA in the correct way. Therefore it will be slightly delayed. Maybe 24-48h.
Also it's strictly forbidden to post any direct links to our rom here. Or to make any modifications to it without our permission. Thank you.
What I'm doing right now:
-Packing the next OTA
-Kitesufing
very good work man:good:
Fantastic! I just gave up trying to get one of the n9005 versions running on my telus branded phone. No joy there so went back to cm11. Will now await your up load. Thanks for this
Sent from my SM-N900W8 using Tapatalk
O yeah finally ...
support chinese language?
your rom is great,I flash before V17;
but not chinese langugage!!!
this version support chinese language?
Thanks waiting for this one..
Sent from my SM-G900F using XDA Premium 4 mobile app
many thanks and wait for link !
Something big is coming ....
ok for screen mirroring but mhl cable works? thanks for your works
Sent from my SM-N9005 using xda premium
kendragon said:
ok for screen mirroring but mhl cable works? thanks for your works
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
If the fix works it should also be working I think. But maybe it still isn't fully working. We're close though.
WOW!! It's amazing! I hope there isn't the gps bug when return to note 3 based ROM
Thanks mate for your work
kevin_1351 said:
If the fix works it should also be working I think. But maybe it still isn't fully working. We're close though.
Click to expand...
Click to collapse
Only with stock kernel?
Sent from my SM-N9005 using xda premium
hi
firstly thanks for this hard work. i wondering that video call is working with operator?
kendragon said:
Only with stock kernel?
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That will never change. Has and will always be the case. For all roms.
stormy_ugur said:
hi
firstly thanks for this hard work. i wondering that video call is working with operator?
Click to expand...
Click to collapse
EDIT: Videocalling isn't included cause of the T-mobile base. We will maybe fix it though.
download link availible , yeahpp
stock kernel is good or we have some limitations as battery life?
Sent from my SM-N9005 using xda premium
kendragon said:
stock kernel is good or we have some limitations as battery life?
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
Well it's the stock note 3 one. Of course some unofficial kernels will give you better battery life since they're downvolting/clocking. Still I wouldn't worry to much about it.
First of all - all credits go to cordell and Slim Team. After will left the hlte slim scene, I found great gap when it comes to light and functional roms. Aim of this rom will be to stay close to Slim principles, but optimised with various toolchains and adding few features that I deem necessary.
This is the worst OP ever.
At this stage, it is still early to add or request features, as Slim just started developing again. When the code settles, I will have my own take on this rom. It will stay small, fast and stable above everything else.
Slim is back! Getting better with each release.
XDA:DevDB Information
Slim Kiss Edition, ROM for the Samsung Galaxy Note 3
Contributors
encho
ROM OS Version: 5.1.x Lollipop
Version Information
Status: DD quality
GPL/Sources
Kernel
Device tree
Slim
Downloads
Download ROM
Recommended Gapps Slim Zero of course.
Changelog
24 April 2015 - initial build - 0.1 alpha
25 May 2015 - - build 0.3 alpha - 'Return of the Slim'
28 May 2015 -Updated Layers support: Dialler, Contacts, InCallUI. Vertical scrolling gallery from CM. New MMS app.
03 June 2015- Upstream changes.
11 June 2015- Upstream changes.
19 June 2015- build 0.4 alpha - upstream changes, emergency call fix.
29 June 2015- Upstream changes.
05 July - Slim beta 0.1. Includes full layers support, f2fs and NTFS support.
28 July - Slim beta 0.2. Custom kernel, upstream changes.
09 September - Back to basics, modified Slim kernel, UBER TC. No Layers.
17 September - Slim 0.7. Layers. System f2fs. Kernel updates, including powersave and adreno idler.
21 September - Minor update, move to sdcard and Titanium large apps restore fully working.
13 January 2016 - Slim Beta 0.14
Extra Features - some already added to main source
Layers 2.1 support - done
Vertical scrolling gallery - done
New SMS - done
UBERTC - done
Arter's sound and bluetooth fixes - done
Vibration control - done
Button backlight customisation - done
Working (what I tested so far, you tell me):
LTE
Calling
Camera
Bluetooth
RRO Layers 2.1
GPS
Charging
Smoothness and speed!
Not working/missing:
No slim settings yet.
Because of the above no way to setup home-to wake (but power button works).
No Slim launcher yet.
No other advanced features that used to be there.
It might be too smooth and fast for some people.
Observations:
New Slim features new cm-based app ops (yay), including built-in root.
Camera has storage settings option.
Quick Boot works (in dev settings).
It is smooth and fast.
Thanks, do mobile connections works this time?
Irony71 said:
Thanks, do mobile connections works this time?
Click to expand...
Click to collapse
Yep. I wouldn't post otherwise.
Will try this soon. Thanks for building so many different roms.
Irony71 said:
Will try this soon. Thanks for building so many different roms.
Click to expand...
Click to collapse
I am flashaholic like the rest of you. If nobody wanted to build I had to. [emoji12]
Remember this kind of ROM is not everybody's cup of tea. Not many features, but boy it feels light.
Then it's my cup oft tea. After searching for more and more features since Note 1 I settled down a bit and search for a stable slim rom.
Btw. Will is back in the building game for hlte but only with a slim cm build.
Irony71 said:
Then it's my cup oft tea. After searching for more and more features since Note 1 I settled down a bit and search for a stable slim rom.
Btw. Will is back in the building game for hlte but only with a slim cm build.
Click to expand...
Click to collapse
I've seen it, although I prefer slim base.
hello and congats for your work. been using slim rom for my old galaxy II.
does this rom support spen functions?
regards
dlemonis16 said:
hello and congats for your work. been using slim rom for my old galaxy II.
does this rom support spen functions?
regards
Click to expand...
Click to collapse
get CM S-pen add on - Note Buddy - Papyrus and you're good to go
Nice rom. Two issues: didn't figure out how to activate recents and battery use is on the high side.
Will go back to euphoria
Irony71 said:
Nice rom. Two issues: didn't figure out how to activate recents and battery use is on the high side.
Will go back to euphoria
Click to expand...
Click to collapse
Yes, as I mentioned no button config in the menu yet. Still very early days.
encho said:
Yes, as I mentioned no button config in the menu yet. Still very early days.
Click to expand...
Click to collapse
FANTASTIC !!
MANY THANKS FOR ALL YOUR WORK AS WELL AS FOR STARTING THIS THREAD !!
Have used (and really enjoyed) ROM intensively at work for the last three days or so.
Very - very light, smooth, rock stable and lightning fast !! (windows open after you think and before you click !!).
Love this bare bone feeling !!
Appreciated very much the save photos to sd option as well as the enter instead of emoticon in keyboard (no need for x-posed modules) and the volume buttons moving cursor options (I think both are missing in AOSPA - also an EXCELLENT ROM !!).
Lovely grey signal bars for 2G turn white for 3G - LTE.
Quick boot option is there to activate but shut down function in advanced power menu doesn't actually shut device down, therefore unable to confirm that it works.
Minor issue: after boot, ROM hangs for quite a while (I haven't timed it but I'm getting the impression it takes quite a bit longer than other 5.1.1 ROMs to boot up) in home screen before lockscreen is activated (therefore danger of shortcuts getting accidentally pressed in one's pocket etc).
A cupple of functions I could definitely live without but which would make (my) life easier if present:
Phone keypad T9 localizations.
Symbols for long press in AOSP keyboard.
Battery percentage (instead of icon) option for taskbar (I COMPLETELY ADORED the semi hidden -like easter egg- function when pressing the little battery icon in AOSPA's battery settings).
Another small thing: I think missed calls appear as received in call history.
And possibly no more than a cupple more (almost not worth mentioning) I don't remember.
My hardware buttons workaround is currently "gesture navigation" x-posed module that does an excellent job once one gets used to it (I will probably use it instead of buttons from now on).
Currently trying AOSPA daily at work (this, to me, is the only real testing) which gives me a very good feeling of fluidity, smoothness and stability though without the imediate responsiveness that Slim does (often reminds me of "Broken" which, after all is a Slim on steroids). I will post in the appropriate thread (many thanks for this also) when I'm done.
All the best.
Yours as always
costasparisis
After a long while, new update is up. Lots of updates. Enjoy.
The ok button is unavailable when putting in the sim card number so I have been unable to use the Rom even after a factory reset
Sent from my SM-N9005 using XDA Premium HD app
encho said:
After a long while, new update is up. Lots of updates. Enjoy.
Click to expand...
Click to collapse
People who read this please visit following link first
http://forum.xda-developers.com/showpost.php?p=60646694&postcount=53
Many thanks again encho.
Excellent ROM overall.
Enjoyed and still enjoying. Using since yesterday afternoon (24 hrs) <-I too always come back to Slim & have a tendency to stay->.
Really fast and light feeling even after having lived with Broken for 24 hrs so:
speed & snappiness 990/1.000 (agreeing that the latest version of Broken is always the standard for speed & snappiness ie 999/1.000 unless stated otherways).
No lack of any feature I would consider essential or find hard to live without. This said, hardware button mapping preferably with ability to assign app or shortcut to long-press and/or double press (excellent workaround for this is Gesture Navigation x-posed module), phonepad button T9 localization and long press phonepad button speed dialling would definitely have made my life easier.
Slim Launcher integration is very welcome and the addition of Personalisation>Interface in settings very promising for having one or two more features in future builds.
QuickBoot mode in Developer options an excellent addition - but Power Off command in Power Button long press menu doesn't work when QuickBoot mode is activated (works fine otherways but then there's no QuickBoot- haha) so let's say:
features 900/1.000 (agreeing that the latest version of BlissPop is always the standard for features ie 999/1.000 -or maybe I shouldn't have mentioned this at all -LOL- going to try latest version imediately after this)
Stability now is 999/1.000 since all basic settings and built-in applications work fine (QuickBoot mode is more of a feature than a basic setting so it doesn't count). And which ROM shall we agree is setting the standard for stability ? Probably EOS I should think.
Anyway, this was a first try -hopefully will mature over time (& get shorter and more juicy). I will try and post every time I have tried a new ROM / ROM version, either for a very short time (ie flashacholic's curiosity to see what's "inside the box") or for a longer period, at work etc. For anyone who happens to read this: please feel free to suggest anything and always remember that this is done purely for fun.
All the best
costasparisis
costasparisis said:
People who read this please visit following link first
http://forum.xda-developers.com/showpost.php?p=60646694&postcount=53
Many thanks again encho.
Excellent ROM overall.
Enjoyed and still enjoying. Using since yesterday afternoon (24 hrs) <-I too always come back to Slim & have a tendency to stay->.
Really fast and light feeling even after having lived with Broken for 24 hrs so:
speed & snappiness 990/1.000 (agreeing that the latest version of Broken is always the standard for speed & snappiness ie 999/1.000 unless stated otherways).
No lack of any feature I would consider essential or find hard to live without. This said, hardware button mapping preferably with ability to assign app or shortcut to long-press and/or double press (excellent workaround for this is Gesture Navigation x-posed module), phonepad button T9 localization and long press phonepad button speed dialling would definitely have made my life easier.
Slim Launcher integration is very welcome and the addition of Personalisation>Interface in settings very promising for having one or two more features in future builds.
QuickBoot mode in Developer options an excellent addition - but Power Off command in Power Button long press menu doesn't work when QuickBoot mode is activated (works fine otherways but then there's no QuickBoot- haha) so let's say:
features 900/1.000 (agreeing that the latest version of BlissPop is always the standard for features ie 999/1.000 -or maybe I shouldn't have mentioned this at all -LOL- going to try latest version imediately after this)
Stability now is 999/1.000 since all basic settings and built-in applications work fine (QuickBoot mode is more of a feature than a basic setting so it doesn't count). And which ROM shall we agree is setting the standard for stability ? Probably EOS I should think.
Anyway, this was a first try -hopefully will mature over time (& get shorter and more juicy). I will try and post every time I have tried a new ROM / ROM version, either for a very short time (ie flashacholic's curiosity to see what's "inside the box") or for a longer period, at work etc. For anyone who happens to read this: please feel free to suggest anything and always remember that this is done purely for fun.
All the best
costasparisis
Click to expand...
Click to collapse
Great review, people will know what to expect before flashing. :good:
@encho thanks for the update and your hard work.
Are you planning to make this rom compatible with other custom kernels like arter97's or temasek's?
piats said:
@encho thanks for the update and your hard work.
Are you planning to make this rom compatible with other custom kernels like arter97's or temasek's?
Click to expand...
Click to collapse
Soon, I hope. Lots and lots of commits coming from slim team, so it would be pointless at this stage to do any framework changes.
{
"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!
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.