THIS IS AN ALPHA VERSION AND NOT SUITED FOR DAILY USE
Hello all,
I didnt had a name for it, so that its for now hehe.
Here is my first release of the android 4 for desire s, this port is from the dump of galaxy nexus rom.
wipe all before installing!
Works:
oSound
oBoots withought any issue
oWallpapers (live ones will crash at the beggining)
oPhone ( read below how to setup it to work) (2G)
oTouch
oKeys
oSD Card
oWifi ( You need to manually add the details from wifi menu - add network)
oSensors
oRoot ( Thanks Rapier)
omore
Not working:
oMarket - Cant download ( works for some)
oBluetooth
oEGL ( no hardware acceleration)
oCamera
oMobile Data ( works for some)
oMount usb to can access on pc
oHeadphones
omore
What in orange is fixed and will be released in next release
To get phone working go to- settings - more(in the network part) - mobile networks - network operators - select automaticly
not sure why is needed
Download:
Link v2.4.1 (Lastest): http://www.mediafire.com/?d7h7nbuhpyq7rxv
Link v2.3: http://www.mediafire.com/?3i2510d89reyiyi
Gapps:
http://download.clockworkmod.com/test/gapps-ics-20111122-4-full.zip
To flash gapps you need to delete some apks from the zip the list are:
FaceLock.apk NfcGoogle.apk TagGoogle.apk
If you find fixes , please send me on pm or post here.
Thanks to:
SuperKid - for being with me all the time.... (me)
djpbx - for helping and video
shaky153 - helping me fix stuff
proxuser - helping fixing stuff
LorD ClockaN - egl fix
(will add thanks soon)
I am not responsible of anything that happens to your device, use at your own responsibility!
(dont sue me if you need to call 999 and cant because of no mic)
IF YOU USE THIS ROM AS A BASE, PLEASE POST HERE.
NO NEED TO ASK FOR PERMISSION, BUT SEND ME FIXES IF YOU FIND ANY.
And its soooo freakin' awesome
The only thing i ask is that any fixes you find please send it to me so i can add them, also if you find bugs that not in the list tell me too
Gr8 work men!
Sent from my Nexus S using xda premium
@superkid specially and all guys that help you
thanks a lot ,this is magnificent
keep up the great work
thanx a lot guys...keep it up!!! :-D
thanks superkid, can u tell me what language will be support?! sorry for eng
i press thanks button for all of you!!!
so many! it have a full list of languages!
wow. this is great start.
I havnt a clue how but the rom booted without me having to kill anything in adb....
So cant wait for a more stable rom...will play as much as I can see if i can fix anything
Sometimes no need to kill the service
xda is sucks, every thing limited, i want thanks more but it limited too!!
download complete! i going to flash it! i hope my ds doesn't explode!!
I have a few new ideas for fixing touch, hope will have time tomorrow to test them!
are u kiding?!? nothing work! except vibrat!!! and pointer mode is so trible!!
but it's so sexy! very much! i couldn'd leave it!! if tuch and mobile network be fixed i used it for daily!and wait for wifi fix! and full port!
thanks superkid, please fix touch, and if u can mobile network
jacob73 said:
are u kiding?!? nothing work! except vibrat!!! and pointer mode is so trible!!
but it's so sexy! very much! i couldn'd leave it!! if tuch and mobile network be fixed i used it for daily!and wait for wifi fix! and full port!
thanks superkid, please fix touch, and if u can mobile network
Click to expand...
Click to collapse
I told already that nothing works xD its just for development atm
And i agree
if touch and sound/phone would work, it would be stable
superkid said:
I told already that nothing works xD its just for development atm
And i agree
touch and sound/phone would work, it would be stable
Click to expand...
Click to collapse
you are our hero!!
i finally see ics in my hands after 4 month!!
now i hate android gb and sense o...!!!
just ics!!
دلگيرم از دست خودم، كاش عاشقت نميشدم!!!
superkid said:
touch and sound/phone would work, it would be stable
Click to expand...
Click to collapse
true, even getting the touchscreen to work and the cursor is a momentum thing at this moment. great work bro. really great work.!
I would be happy if other devs can help with this, just choose one bug and try to fix it... one bug at a time we can fix all of them i think
Well, i am choosing touch, and working on it now hehe
i can't download it
A few things -
1) This ROM is epic, wifi fix would be great, as sound seems to hard for now
2) Hate the lockscreen? Disable it ! Go to Settings>Security>Screen Lock> NONE.
3) To swipe around, in app drawer, settings etc, simply use two fingers. It's much easier than adjusting the pointer ind sliding second finger.
4) I rebooted 4-5 times, no need to kill service yet.
5) Has anyone submitted this to portal? I'm about to, but don't wanna spam the authors....
6) I own superkid's 500th thanks
{
"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.
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.