yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] giveme13s:
Faced same problems, but compiling now is running after commenting out lines 15 and 191 in file bootable/recovery-cm/Android.mk

Not sure about the side-effects

# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

[COLOR=Red]#ifeq ($(call my-dir),$(call project-path-for,recovery))[/COLOR]

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_SRC_FILES := \
recovery.cpp \

$(LOCAL_PATH)/tools/Android.mk \
$(LOCAL_PATH)/edify/Android.mk \
$(LOCAL_PATH)/updater/Android.mk \
$(LOCAL_PATH)/applypatch/Android.mk \
$(LOCAL_PATH)/voldclient/Android.mk

[COLOR=Red]#endif[/COLOR]
[Android Software/Hacking General [Developers Only]] kornfed:
after a repo sync I get the following error:

make[1]: Entering directory `/home/ubuntu/android/beanstalk/kernel/samsung/klte'

make: *** No rule to make target `NOTICE-TARGET-STATIC_LIBRARIES-libminui', needed by `/home/ubuntu/android/beanstalk/out/target/product/klte/root/charger'. Stop.

make: *** Waiting for unfinished jobs....

I managed to build succesfully on this computer previously, but i get the same error on 2 pc's, any idea, what to do?

I see more peope have this issue.
[Android Software/Hacking General [Developers Only]] Vortex1969:
That worked good good....

Thanks
[Android Software/Hacking General [Developers Only]] kornfed:
that brought me a little bit further, but i ended with:

make: *** [/home/ubuntu/android/beanstalk/out/target/product/klte/obj/SHARED_LIBRARIES/libstagefright_soft_ffmpegadec_intermediates/SoftFFmpegAudio.o] Error 1

make: *** Waiting for unfinished jobs....

any ideas?
[Android Software/Hacking General [Developers Only]] Vortex1969:
Got that one as well. Look for fix right now.

Not sure why all this has changed last commit was a day aso from Scott but it started this with the changes from 4 days ago.
[Android Software/Hacking General [Developers Only]] chineel:
this things were recently changed in CM source and is still changing wait for some time than resync repo.
[Android Software/Hacking General [Developers Only]] jackeagle:
U need to revert a commit in external... It's cm commit issue if u are tracking from Co-BeanStalk sources there it's fixed...
[Android Software/Hacking General [Developers Only]] kornfed:
any guide for the dummies? :o
[Android Software/Hacking General [Developers Only]] Vortex1969:
Cool went to Co-Beanstalk git but I didn't see any commit. Care to share a link.

Thanks.

Edit:: found it this should fix you build problems.

https://github.com/Co-BeanStalk/and...mmit/0d129f8865d67148cb5047d6c1624a0ca51c7ae2

Commits fixed my build. Build is complete.
[Android Software/Hacking General [Developers Only]] kornfed:
could you please share some kind of tutorial / howto- to get the fix.?
[Android Software/Hacking General [Developers Only]] giveme13s:
Here is a good one (at least for me)
[Android Software/Hacking General [Developers Only]] jackeagle:
Here you go :) If u have any issues we will help u here :)
[Android Software/Hacking General [Developers Only]] giveme13s:
lol..we gave same link :)
[Android Software/Hacking General [Developers Only]] kornfed:
Thank you, I will look into it :)

The weirdest thing, for now repo sync managed to complete the file. :o
[Android Software/Hacking General [Developers Only]] danjull:
make: *** No rule to make target `/home/android/beanstalk/out/target/product/dlx/obj/STATIC_LIBRARIES/libtar_intermediates/export_includes', needed by `/home/android/beanstalk/out/target/product/dlx/obj/RECOVERY_EXECUTABLES/bu_recovery_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....

Getting this error too. Tried the bootable/recovery-cm/Android.mk edit as suggested earlier in this thread, but still getting the error. Any idea what's causing it? Tried reverting recent commits to recovery with no change...
[Android Software/Hacking General [Developers Only]] Vortex1969:
Add this to your roomservice.xml looks to me like you are missing your libtar.

https://github.com/CyanogenMod/android_external_libtar
[Android Software/Hacking General [Developers Only]] kornfed:
Does anyone have weather forced close when booting in the recent build?
[Android Software/Hacking General [Developers Only]] t3chwizard:
Quick question, why is it that the non intrusive call dialog does not allow you to use your phone in the area on the screen it is not blocking while a call is coming through?
[Android Software/Hacking General [Developers Only]] nprev420:
Um weather was completely removed at least a week ago. It shouldn't be in the build.....
[Android Software/Hacking General [Developers Only]] kornfed:
I've made clobber, and repo sync, lets see what the new build will bring.
[Android Software/Hacking General [Developers Only]] freddienux:
Sorry for asking but does anyone know if there unofficial builds for Nexus5 hammerhead
[Android Software/Hacking General [Developers Only]] xtcdk:
There is

Hammerhead / Linaro / Dirty Unicorn / Beanstalk 4.4.4007 YUGA adm.
[Android Software/Hacking General [Developers Only]] kornfed:
Is someone familiar with the problem not getting facebook notifications / alerts alongside certain other apps in their build?

Isolated issue.
[Android Software/Hacking General [Developers Only]] freddienux:
Where can I find link? Thx in advance
[Android Software/Hacking General [Developers Only]] chineel:
Hi anyone got success building rom since last week I am stuck with this error.

make: *** No rule to make target '/home/chirag/beanstlk/out/target/product/mako/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by
[Android Software/Hacking General [Developers Only]] kornfed:
Try

- Repo sync

- Make clobber

and rebuilt
[Android Software/Hacking General [Developers Only]] chineel:
Doing that twice a day since 7th
[Android Software/Hacking General [Developers Only]] desalesouche:
here is a little hack you can add in android.mk from your devices

# Hack for build

$(shell mkdir -p $(OUT)/obj/SHARED_LIBRARIES/libminui_intermediates)

$(shell touch $(OUT)/obj/SHARED_LIBRARIES/libminui_intermediates/export_includes)
[Android Software/Hacking General [Developers Only]] chineel:
Now on this error this hack is not working

make: *** No rule to make target 'NOTICE-TARGET-STATIC_LIBRARIES-libminui', needed by '/home/chirag/beanstlk/out/target/product/mako/root/charger'. Stop
[Android Software/Hacking General [Developers Only]] mikshepard:
I tried adding that in and still got the same results. I put it in my devices android.mk like you suggested. Do you have any other ideas?

Thanks,

-Mike
[Android Software/Hacking General [Developers Only]] desalesouche:
no sorry
[Android Software/Hacking General [Developers Only]] mikshepard:
This fix posted a few pages back seems to work:

Had to add in the libtar repo to fix the error that popped up after that but I seem to be compiling now.

Thanks,

-Mike
[Android Software/Hacking General [Developers Only]] chineel:
if you can please share what you added to roomservice.xml
[Android Software/Hacking General [Developers Only]] mikshepard:
Sure, just added this:

<project name="CyanogenMod/android_external_libtar" path="external/libtar" remote="github" revision="cm-11.0" />

Hopefully that helps,

-Mike
[Android Software/Hacking General [Developers Only]] Vortex1969:
Lol cool I posted about libtar a page back. Look in you bootable recovery for libminui I had fixed it once but forgot.

The build is broke but it is fixable. I have it building for bacon and it boots. But my fixes are different. Don't see Scott doing any work as of late.

Good luck all.
[Android Software/Hacking General [Developers Only]] chineel:
Thanks, It's Fine compilation started. In mid of this error I had updated My OS to latest beta OpenSuse 13..2 which has removed two needed things gpref and bison. more over I was compiling with openjdk 1.7 gcc 4.8

Now I am getting error undefined audio format in qcom audio for wma and wmapro.

any one has this error recently? I had seen similar error in carbon rom .

Thanks again

Chineel
[Android Software/Hacking General [Developers Only]] mikshepard:
For the audio error (assuming it's the same one I got), I added this in roomservice.xml, I think I found the link a few pages back:

<remove-project name="CyanogenMod/android_external_stagefright-plugins" path="external/stagefright-plugins" />
<project name="TeamBliss/android_external_stagefright-plugins" path="external/stagefright-plugins" revision="kk4.4" />

However now I'm failing on this error:

bootable/recovery/minui/minui.h:77: error: undefined reference to 'res_create_surface'
bootable/recovery/minui/minui.h:77: error: undefined reference to 'res_create_surface'
collect2: error: ld returned 1 exit status
make: *** [/media/mike/8247787d-d461-4915-8824-fca311e55176/android/beanstalk/out/target/product/jflte/obj/EXECUTABLES/charger_intermediates/LINKED/charger] Error 1
make: *** Waiting for unfinished jobs....

Going to have to do some digging today on this one, unless someone has an idea?

Thanks,

-Mike
[Android Software/Hacking General [Developers Only]] chineel:
My error is in qcom audio not the one which you might have got. . I did one hack to go further but I know that is not the way to solve that issue.

Now even I have got the Same error as of you.

Thanks again.
[Android Software/Hacking General [Developers Only]] Vortex1969:
This commit may help your last build error.

https://github.com/CyanogenMod/andr...mmit/56704590840191fd040b42d84eda81b7360b402b
[Android Software/Hacking General [Developers Only]] mikshepard:
Thanks, I reverted that commit and we'll see if that fixes it. I'll post back.

Cheers,

-Mike
[Android Software/Hacking General [Developers Only]] Vortex1969:
No disrespect to Scott the one man band but trying to build this and keep up with CM changes his repo is way behind/out of date. Love the ROM to death. Its OK for a Google build bit for a CM build no go.

Even N4 and N5 builder's are having problems.

Things are moving fast. What BeanStalk needs is a team so commits can be added tested and of reverted or kept.

Long live the Bean...
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
For those currently building beanstalk, if you install and try to run Netflix, what is your outcome? Does the app run okay or does it force close.
[Android Software/Hacking General [Developers Only]] xtcdk:
Use old netflix APK

Hammerhead / Linaro / ^Uber /Dirty Unicorns / Beanstalk YUGA adm.
[Android Software/Hacking General [Developers Only]] mikshepard:
I use the Xposed Module to fix Netflix and the current version works fine.

-Mike
[Android Software/Hacking General [Developers Only]] kornfed:
Does anybody has issues with active display?
[Android Software/Hacking General [Developers Only]] kornfed:
Is Co-beanstalk dead?
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
In a way yes. Have have put a team together and call it now Bliss Stalk. TeamBliss on github.
[Android Software/Hacking General [Developers Only]] azoller1:
Wait, what?
[Android Software/Hacking General [Developers Only]] kornfed:
I just heard about it, good job, going to try it right now.

Btw, which path are you using for proprietary_vendor_samsung. the muppets, or do you have your own?
[Android Software/Hacking General [Developers Only]] Vortex1969:
Some Bacon BlissStalk love.[emoji6]
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
Yes we use the muppets.
[Android Software/Hacking General [Developers Only]] chineel:
There is New Updates and I could build one for mako Today and is working fine as usual.
[Android Software/Hacking General [Developers Only]] giveme13s:
Check Scott's github, guys.

I'm compiling new updates... 30 mins, and no errors...yet... :)
[Android Software/Hacking General [Developers Only]] jewnersey:
nvm, started to work for no apparent reason...
[Android Software/Hacking General [Developers Only]] Aceofzeroz:
Huge updates!!!

Attention all Beanstalk builders, lovers, haters and in-between! In preparation for the WIP Lollipop 5.0 version that's underway, Scott has finally decided to brand the 'Beanstalk' name in his rom repos instead of CM!!:D The details commit can be found in this link here, and so be prepared to make the changes for your respective devices accordingly.:cool:

With big new changes, so will older things change in a big way. Spread the word to avoid the highly possible confusion and get ready for the inevitable return of Beanstalk!!!:highfive::good:
[Android Software/Hacking General [Developers Only]] t3chwizard:
Does this mean it isn't going to be based on CM anymore?
[Android Software/Hacking General [Developers Only]] skyliner33v:
Still based on cm. But with a beanstalk twist.
[Android Software/Hacking General [Developers Only]] t3chwizard:
Now I am a bit confused. Are you saying you are going to be editing the CM repos and then adding a few things in before releasing it to the various sources that the Beanstalk compilers will use?
[Android Software/Hacking General [Developers Only]] skyliner33v:
Lol. So what happens is cm creates cm12 with their set of features. Then beanstalk will fork (make a copy of) that source with those base features, and add in additional features from other roms. The stuff that makes it beanstalk. Then if cm adds more stuff to cm12, beanstalk merges those features in to keep its base features current with cm12.

So beanstalk is essentially cm12, but with a ton more features, aka, the beanstalk twist. That's how most roms around here are. They use cm12 as a base. Some, like Paranoid Android, use just straight up AOSP source as their base. They take AOSP code and add in their specific set of features, Halo, Hover, DSB etc.

Make sense?
[Android Software/Hacking General [Developers Only]] phoenixita:
Are you saying that instead of giving brunch codenam after breakfast i have to go in the device folder and edit the make files writing beanstalk instead of cm where is needed? :D I can live with it :P It's like every rom now :D It was easier to build but now i have some building skills that i didn't have when i started building beanstalk :)
[Android Software/Hacking General [Developers Only]] phoenixita:
The switch is not happened yet..Or am i wrong? For the moment it is still using vendor/cm? Cause i built it and it's still missing the beanstalk flavour! I can't wait to build 5.0.1 beanstalk :D

What if i add vendor/beanstalk in the local manifest and do the proper modifications to the device tree? :D
[Android Software/Hacking General [Developers Only]] gimmeitorilltell:
The switch has been made bro. Build away some BeanStalk :) You will have to modify your device repo.
[Android Software/Hacking General [Developers Only]] phoenixita:
Bro i found why it's still building cyanogenmod...cause i repo inited cyanogenmod... the android project of beanstalk is still pointing to cyanogenmod repo init, https://github.com/scotthartbti/android/tree/lp5.0 as you can see here, instead of this repo init -u git://github.com/scotthartbti/android.git -b lp5.0
[Android Software/Hacking General [Developers Only]] gimmeitorilltell:
Woo Hoo now that's some refreshing news! Enjoy the new builds.
[Galaxy S II Q&A, Help & Troubleshooting] cortex69:
hi

first of all I'm not newbie, I've just made an account on xda.

I would live to find the way or workaround of changing values for dmask and fmask on the tom's default SD card mount?

I'm on SentinelROM v4.75 for i9100.

current fmask and dmask values are both 0702 which are preventing me from flashing ext2internalsd script.

if this the wrong section, point it out please. I'm at work atm and can't really search for good one
[Galaxy S II Q&A, Help & Troubleshooting] Friedenstaube81:
Hello there!

I'm encountering the same problem with my LG P880 (CM 10.2 Nightly). I'll keep you informed just in case I find it and it's still an issue at your place ;)

Regards,

Lukas
[General Questions and Answers] vlamnire:
Hi

I plan on buying a new Galaxy Tab 2 and I've figured out how I plan on rooting it. I've found several guides that say you should install CF-AutoRoot via ODIN then install CWM then install custom rom. I haven't rooted an Android device before but I've viewed a ton of tutorials on how to do it.

However, I've gotten the lastest CWM build for my device on their website and created an ODIN flashable package with it. Couldn't I just flash my ODIN CWM packaged that I made then install a rom since roms come rooted or don't they?
[General Questions and Answers] b.u.s.arash:
hi

usually it's like this:

1- flash your custom recovery by odin

2- write your root file by custom recovery

or

just flash cf auto root by the stock recovery that the phone has.

it depends on your phone and your procedure you choose...
[General Questions and Answers] jabrif:
You just need to flash the cwm via Odin. Then insert the Rom you want to flash in your internal or external ad card. Access cwm recovery. Do a full data, cache, dalvic cache wipe. Then flash Rom and then gapps.

No need to root if you want to install a custom Rom coz most of it comes pre rooted.
[General Questions and Answers] vlamnire:
Thank you I was just wondering that. I was confused because every tutorial I found for installing a custom ROM they always used some sort of thing to root first but logically that didn't make any sense to me. Because to install a ROM you have to wipe everything so you wouldn't have root access left. And I looked in the zip files for the rom I want to install and under xbin there was su which is the root command and saw busybox.
[General Questions and Answers] Bishal Pranto Roy:
I don't think they come rooted

If I Have Helped You Can You Press

.

.

THANKS BUTTON

.

.

To support Me.
[Sprint HTC One (M7)] MadDogMaddux:
So, I'm nervous about the fact that I can't replace the battery on my ONE. So far every night I've been staying up late until the phone dies, then plugging it in, waiting til the light stops flashing, then powering it up to charge while on overnight.

Problem is, this phone has awesome battery life. Right now at 10.30pm, I'm sitting at 41%, and debating just leaving it unplugged all night.

So what's the deal with memory on these batteries? How much, say over a 2 yr span, will charging a non-drained battery shorten its lifespan or lessen its capacity?
[Sprint HTC One (M7)] sauprankul:
Lithium ion batteries are awesome. They are lighter, smaller and do not suffer from "memory effect."

Do not drain then fully recharge this phone on a regular basis. That will accelerate capacitance loss. Keep it charged as much as possible, avoid fast charging, try to use your PC to charge it overnight. Do not leave it charging for too long (i.e. days on end). Though on board computers can refuse charging, it is best to stay on the safe side.

2 years, you will definitely notice a decrease in battery life, but by the time it becomes intolerable, you will have upgraded. I can almost guarantee that.

EDIT: Please add to/refute any statements I made if you have greater knowledge on this subject, people.
[Sprint HTC One (M7)] MadDogMaddux:
Thanks! Can you explain why using mr PC to charge is better?
[Sprint HTC One (M7)] customhdrider:
Because it's a slower charge at a lower amp rating prolongs battery life by not boiling the cells
[Sprint HTC One (M7)] MadDogMaddux:
Gottit. Thanks!
[Sprint HTC One (M7)] customhdrider:
No problem,glad I could shed some light on the subject
[Sprint HTC One (M7)] Rirere:
As was previously noted, what you're doing is actually the worst possible thing you can do to a lithium ion battery. In general, best practice is to keep your battery somewhere between 10%-95% charge whenever possible. Once a month, you should "cycle" your battery under 10% (but not fully drained) to keep everything in peak condition. If you're ever not going to use the phone for any length of time, best practice is to drain to 40% and store in a cool, dark area.

When you first get a new device, you do want to condition it by doing three to five (varies on the device) full charge/discharge cycles, but after that, once a month with a conditioning cycle will take care of things for you. And again, as was previously noted, it's not a great idea to leave your phone charging overnight because you can't always depend on the battery controller chip.

These newer cells are all rated to relatively high cycle lifetimes, so I wouldn't worry overmuch. At that point, capacity is supposed to start degrading, although naturally it's going to happen a bit earlier for any number of reasons. I'd be much more worried about avoiding heat though than overcharge.
[Sprint HTC One (M7)] sauprankul:
I'm assuming charging it slowly would keep it slightly cooler than a wall socket and closer to room temp, the better.

There is probably some other reason, but I'm not the person to ask. you can do some independent research. :good:

Just charge your phone when it needs it and don't when it doesn't. Do that and you'll be good until you upgrade no problem.

EDIT: Oh, beat me to it... haha

EDIT: Also, does the 40% apply to phones? Mobile devices never really turn off, they just go into deep sleep, I'm told. I was going to say that too, but then I remembered this. Does the 40% rule apply to non-removable batteries?
[Sprint HTC One (M7)] Rirere:
It's a question of how much voltage you're chucking into the battery. If you use a low-voltage wall adapter it'll be the same as if you were charging from your PC.

The 40% rule applies to any battery, and they'll all discharge over time anyway (connected or no). If you shut your phone off, everything powers down except (if memory serves) what's necessary to run the internal clock. The impact that has should be pretty minimal (unless you're trying to bury your One for a thousand years, in which case...can't help you there).
[Sprint HTC One (M7)] sauprankul:
Who would buy a low voltage wall adapter? :p

And yes, I would like to bury my One safely for a thousand years, so when it is found by the generation of humadroids, they will see it and be amazed that a civilization so primitive could achieve such technological mastery.
[Sprint HTC One (M7)] Rirere:
I don't know that I bought any, but I have a few lying around from yesteryear's gadgetry.

And at that point, why not launch it into space instead, a la HTC Nexus One?
[Sprint HTC One (M7)] MadDogMaddux:
So I use my phone as my alarm clock and also run the Relax and Sleep app all night. Otherwise I'd just plug it into my lappy throughout the day and not worry about it.

But that raises another question: running the phone overnight while charging it at the same time. Bad juju?

I plugged into my lappy last night around midnight, woke up this morning and had about 95% charge, rather than the usual 100%. I'm assuming this is the result of power output for Relax and Sleep cutting int power input from charging.

I've also been in the habit of leaving my EVO 4G plugged in while tethering. I assume this is also a bad plan?
[Sprint HTC One (M7)] Admiral Sir Manley Power:
MOST of this advice is 100% true.

The only part that is not correct information is the advice to not let it die. It is perfectly OK to do this as long as you don't deep discharge the battery... Example like let it die then not charge it for like a week or something.

The science behind this is the fact that lithium ion batteries actually have a nominal voltage operating range which is like 3.2 - 4.3 volts or something like that. Your device is designed to shut itself down when it gets to about 3.5... This is done to protect the battery from deep discharge cycles.

Letting it die is perfectly alright. Just make sure you charge it soon after.

Also, you don't need to use your PC to charge it. That is in no way necessary. Your device came with a wall charger for a reason...

There are safety features built into the kernel and cable to keep you from damaging the device during charge. Use the wall.. It is perfectly safe and faster / more practical.