yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] wantowan2:
Is anybody else having this "Gallery crash bug? I've asked around, tried different roms and it seems to come back to Beanstalk...

MP4's crash Gallery/phone as room as you open gallery since the beginning of September.

@ scott.hart.bti , anyone that knows more then me....=-) This is what the crash looks like in last_kmsg"

[54472.595581] [pcm_out.c:pcm_out_release] release session id[1]

[54475.191345] msm_vidc_dec: Inside vid_dec_open()

[54475.191619]

[54475.191650] res_trk_download_firmware(): Request firmware download

[54475.246978] fw_version 7:19:2012

[54475.250579] msm_vidc_dec: Inside vid_dec_release()

[54475.270874] msm_vidc_dec: Return from vid_dec_release()

[54475.273712] msm_vidc_dec: Inside vid_dec_open()

[54475.296966] fw_version 7:19:2012

[54475.399902]

[54475.399932] err: Buffer pool is full

[54475.400482] Unable to handle kernel NULL pointer dereference at virtual address 00000018

[54475.400695] pgd = dce4c000

[54475.400787] [00000018] *pgd=00000000

[54475.400909] Internal error: Oops: 5 [#1] PREEMPT SMP

[54475.401062] Modules linked in: dhd vibrator [last unloaded: dhd]

[54475.401397] CPU: 0 Tainted: G W (3.0.94+Moretz-4.0.1a+ #1)

[54475.401580] PC is at vcd_find_buffer_pool_entry+0x1c/0x60

[54475.401672] LR is at vcd_free_one_buffer_internal+0x58/0x140

[54475.401824] pc : [<c04074c4>] lr : [<c0407560>] psr: 60000013

[54475.401855] sp : dbc43dd8 ip : 00000000 fp : dcc52078

[54475.402038] r10: 416d7920 r9 : dbc42000 r8 : 00000017

[54475.402130] r7 : e5580000 r6 : ce296470 r5 : ce296400 r4 : 000000a0

[54475.402282] r3 : 00000001 r2 : 00000000 r1 : e5580000 r0 : ce296470

[54475.402374] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user

[54475.402526] Control: 10c5787d Table: 5d24c06a DAC: 00000015

[54475.402679]

[54475.402679] PC: 0xc0407444:

[54475.402832] 7444 e0611007 e584101c e0666001 e0836006 e5846018 eaffffff e5942018 e3a00000

last_kmsg was the only capture possible...
[Android Software/Hacking General [Developers Only]] desalesouche:
Radio FM Open Source

may be this would interest some ? it might be interesting to add to beanstalk ?

https://github.com/arco/android_vendor_qcom_opensource_fm

builded but kind of fc...(can't connect).hope i can fix..
[Android Software/Hacking General [Developers Only]] phoenixita:
What's this an FM radio? :)
[Android Software/Hacking General [Developers Only]] desalesouche:
yeah my device support fm radio...
[Android Software/Hacking General [Developers Only]] phoenixita:
I might try adding this to my build and see if it boots anyway was the build process again working cause few days back it wasn't?

Edit: sorry this was a question i forgot the "?".
[Android Software/Hacking General [Developers Only]] phoenixita:
I've tried this and it was not working D:
[Android Software/Hacking General [Developers Only]] wantowan2:
I can't tell what is being updated. This new git version is not helpful. Something is broken cuz I get 'setup wizard has stopped working'. 2 consecutive builds over 3 hours. The only reason I know there was a version change is because vendor/cm/config/common.mk broke sync.

So every time I hit the button on the welcome screen I get that error.

Help please....
[Android Software/Hacking General [Developers Only]] desalesouche:
here is new error coming from build for huawei u8800pro....i made no change to my device tree so error must come from git...

packages/apps/Calculator/res/values/styles.xml:141: error: Resource entry Theme.Calculator.ButtonStyle already has bag item android:textColor.

packages/apps/Calculator/res/values/styles.xml:139: Originally defined here.

packages/apps/Calculator/res/values/styles.xml:207: error: Resource entry Theme.Calculator.ButtonFunctionCellStyle already has bag item android:textColor.

packages/apps/Calculator/res/values/styles.xml:205: Originally defined here.

packages/apps/Calculator/res/values/styles.xml:229: error: Resource entry Theme.Calculator.ButtonDigitCellStyle already has bag item android:textColor.

packages/apps/Calculator/res/values/styles.xml:227: Originally defined here.

make: *** [/home/desalesouche/beanstalk4.3/out/target/common/obj/APPS/Calculator_intermediates/src/R.stamp] Error 1

any idea ?

EDIT: Fixed by replacing with the same file but from Cyanogenmod10.2/packages/apps/Calculator/res/values/styles.xm

ps: i know it is a bad fix...but i have not enough knowledge for the moment to do in other way...
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
built 1001 ok for mako and jfltetmo, then I checked github and 1001 has been reverted with note "DO NOT BUILD"

Oops!

Big things are afoot here.
[Android Software/Hacking General [Developers Only]] phoenixita:
Me too i've built this for ville and had no strange issues...
[Android Software/Hacking General [Developers Only]] willl03:
Things are moving nicely on github, hope we'll see fixes for proximity sensor issues that came with the initial implementation of Active Display

I say that but it's not even officialy released or complete, no doubt Scott has some good stuff ahead

Good source for Active Display commits https://github.com/VanirAOSP/platform_frameworks_base/commits/jb43

Thanks again for the outstanding work Scott, few of my users on the Note 2 should have donated to you. The popularity of the rom is insane by far the most used and praised AOSP on my device with good reason
[Android Software/Hacking General [Developers Only]] phoenixita:
I've trien pasting the whole activedisplayview.java in my activedisplay directory and the proximity sensor is always on when active display itìs on..While if I use the one from CarbonROM the prox sensor is on only if the pocket mode is enabled..! Take a look to carbon github man :)
[Android Software/Hacking General [Developers Only]] willl03:
What a good trick grab the whole file instead of dealing with 10 cherry picks, will use the file from Carbon until Active Display is sorted in our source

Thanks man!
[Android Software/Hacking General [Developers Only]] phoenixita:
This will work and stay there even if you repo sync deleting the frameworks folder and then reposyinc bring you the original Active-displayView.java back anyway yesterday i duilt 4.3.1001 with no issues but i was using vanir instead of carbon and i got no working active display so i decided rebuilding this buti got this error now...someone else?

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
make: *** [/home/phoenixita/beanstalk/out/target/common/obj/APPS/SystemUI_intermediates/classes-full-debug.jar] Errore 41
make: *** Attesa per i processi non terminati....
Note: Some input files use or override a deprecated API.
[Android Software/Hacking General [Developers Only]] BMP7777:
So, does the new build have the active display issues resolved, or should I try the Carbon 'patch' when I build this evening? If so, could someone lay out the process for implementation, please?
[Android Software/Hacking General [Developers Only]] willl03:
Fixes are not in the Beanstalk source, hopefully in future version. I'm currently building with Carbon file will let you know how well it goes

How to do it,

1)

Grab the file here https://github.com/CarbonDev/androi...r/policy/activedisplay/ActiveDisplayView.java

------------

2)

Take ownership of your build folder

In term:

cd

sudo chown -R *your ubuntu user name* *your beanstalk build folder*

example:

sudo chown -R will beanstalk43

--------------

3)

Replace or edit the ActiveDisplayView.java in your build folder with the one from CarbonDev

---------------

4)

Commit the change, so it dosn't break your future repo sync and without having to delete the whole frameworks folder

In term (replace ''beanstalk43'' with your build folder name):

cd beanstalk43/frameworks/base

git commit -am "CarbonDev active display file"

cd

cd beanstalk43

----------------

5)

Build and enjoy

---------------

Because you commited your change doing repo sync will revert everything back to stock, inline with the source. So if you screw up just do a repo sync and start over

GL
[Android Software/Hacking General [Developers Only]] BMP7777:
Thank you. I'll try it out and let you know this evening.....
[Android Software/Hacking General [Developers Only]] willl03:
My proximity sensor is broken so I won't be able to test myself, please let us know how it's working for you and your users
[Android Software/Hacking General [Developers Only]] BMP7777:
Most definitely :good:
[Android Software/Hacking General [Developers Only]] :
So what is the do not build note?
[Android Software/Hacking General [Developers Only]] BMP7777:
I would imagine its a warning that the ROM isn't quite ready for primetime in the active display area. Most likely for guys like me that jumped the gun and built my own before the whole thing was done.

UPDATE: Thought everyone would want to know, Scott has sounded the 'everything's alright' alarm on Git:

THANK YOU SCOTT!
[Android Software/Hacking General [Developers Only]] willl03:
Built with the carbon dev active display file and sensor works like it should

Proximity sensor is off when

Active display is off

or active display on + pocket mode off

or active display on + pocket mode on + screen on

Perfect!! Thanks phoenixita
[Android Software/Hacking General [Developers Only]] MRobbo80:
I will also thank you, I needed this information ta.
[Android Software/Hacking General [Developers Only]] BMP7777:
I used a commit for proximity calibration on my 9/30 build that appeared to alleviate the low-light 'black screen of death' that occurred when users were 'in-call'. This is it: http://review.cyanogenmod.org/#/c/49173/

I have a much less intense but still evident issue with in screen calls going black and having trouble coming back on. With the latest build, it only occurs in low ambient light, and an increase in light does the trick. But, rather than change out all of the files, I am going to try it this way and see if it does the trick like last time. I'll post my results this evening.....
[Android Software/Hacking General [Developers Only]] phoenixita:
heheheheh no problem man have you used the method you posted above? Do you manually copy and paste the file inside the active display .java or you use a github button that i've not seen? lol
[Android Software/Hacking General [Developers Only]] willl03:
Did it the way above

Copied the raw text from carbon github, pasted it inside the file overwriting our original code
[Android Software/Hacking General [Developers Only]] BMP7777:
Out of curiosity, have you or anyone else run a Meld on the two .javas? Wonder what the difference is....
[Android Software/Hacking General [Developers Only]] desalesouche:
did you manage to build the fm radio?
[Android Software/Hacking General [Developers Only]] willl03:
BeanStalk Active Display all in one FIX, thanks Carbon

https://github.com/willl03/android_frameworks_base/commit/8fd2c6e7d8d3095a88606c492b95a7eda66015d6

Feel free to cherry pick it, it's there for Scott too
[Android Software/Hacking General [Developers Only]] BMP7777:
To my novice eyes, it looks to be ixnaying the timeout function. Sweet! Thanks man!
[Android Software/Hacking General [Developers Only]] phoenixita:
in the previous build of this i managed to have a working active display now even copying the whole file i have the same bug lol

I think i'll cherry pick it from your github... a fast command to cherry pick it? Even folowing the guide for vaniraosp i've not managed to cherry pick so what the command for cherry picking in your github should be? :P
[Android Software/Hacking General [Developers Only]] BMP7777:
Go to that pick page, check cherrypick and copy it, look at project to find pick location - in this case its device/htc/m7-common

CD to that directory in terminal while in your build directory, paste and execute. Exit and start again; DO NOT SYNC again, just run your build command an go.
[Android Software/Hacking General [Developers Only]] phoenixita:
8fd2c6e7d8d3095a88606c492b95a7eda66015d6 you mean this?
[Android Software/Hacking General [Developers Only]] BMP7777:
No. That's just the I.D. This is the actual code you need to paste:

git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_htc_m7-common refs/changes/73/49173/1 && git format-patch -1 --stdout FETCH_HEAD

It can be found in the area of the commit page called PATCH SET #1. Be aware that some cherrypicks can have multiple patches and the first may not always be best. In this case, it's the only one. But, I ran into a problem because I didn't look closely enough at the patches and ended up building with a worthless patch for IR blaster(it was supposed to be patch#2 but I didn't look) and I had a whole released build with no improvement. So, look twice from now on....
[Android Software/Hacking General [Developers Only]] willl03:
Correct me if I'm wrong but I think phoenixita wants the active display commit, two things going on at the same time

In that case to cherry pick from my github

In terminal, start in your build folder:

cd frameworks/base

git fetch https://github.com/willl03/android_frameworks_base.git

git cherry-pick 8fd2c6e7d8d3095a88606c492b95a7eda66015d6
[Android Software/Hacking General [Developers Only]] BMP7777:
My bad. I thought he was asking about the patch I had used. On your Git, all of the changes are laid out right there. Me, I'd just go in and change what needed changing and run it. No need for a cherrypick at all.
[Android Software/Hacking General [Developers Only]] willl03:
No worries man :) it's a good thing you're in here sharing what you find, with a few of us rookies we can make things move in the right direction and help each other, it's appreciated
[Android Software/Hacking General [Developers Only]] droidmk:
So no one else has problems with lockscreen shortcuts? I deleted my build directory and did repo init and sync again and started from scratch. Pictured is all that I have as lockscreen shortcuts.
[Android Software/Hacking General [Developers Only]] willl03:
Missing apps, did you flash gapps?

---------- Post added at 01:30 AM ---------- Previous post was at 01:24 AM ----------

Here's the last issue I have with BeanStalk, common to every device

In MMS settings, when you pick the number of messages you want to keep

With Dark Stalk off

With Dark Stalk on

Guess it's a quick one to fix Scott, thanks
[Android Software/Hacking General [Developers Only]] droidmk:
Same shortcuts with or without gapps.
[Android Software/Hacking General [Developers Only]] patch_Adams:
An earlier release had the same issue. My new release also has the null shortcut too. You can go through Scott's github and find the change and revert it. I haven't done this and don't know where it'd be, sorry.

I just hit the reset button in the settings menu....it'll remove that shortcut.
[Android Software/Hacking General [Developers Only]] Saki3d:
Hi i need help to make this rom for mdpi devices,

i got error at bootanim.zip part

i attach terminal codes please check it

here is the last lines

make: *** No rule to make target `vendor/cm/prebuilt/common/bootanimation/.zip', needed by `/home/saki/beanstalk/system/out/target/product/smultron/system/media/bootanimation.zip'. Stop.

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

saki@saki-MS-16Y1:~/beanstalk/system$

big thanks
[Android Software/Hacking General [Developers Only]] ktempleton:
Wouldn't he have to git remote add willl03 URL first

Then git fetch willl03

And then the cherry-pick cmd

That's how I do it but maybe it works the other way to

sent through the worm hole from a galaxy far far away!!!!

---------- Post added at 01:30 PM ---------- Previous post was at 01:25 PM ----------

I should have quoted this for my above post

OK I see the git fetch but the other point still stands I believe

sent through the worm hole from a galaxy far far away!!!!
[Android Software/Hacking General [Developers Only]] danjull:
I've been maintaining a build for the Droid DNA and I've been having some reboots. I haven't been able to purposely do it though so I can get a log. One person said it seemed to be related to when it switches to 3G, another said it seems to happen after being on the phone for about 15 minutes. I've been noticing them when I'm on WiFi, opened up the play store and other data using apps a few times and it reboots when the app initially loads. Anyone else having any reboot issues?
[Android Software/Hacking General [Developers Only]] willl03:
Fixed it myself, here's the commit

https://github.com/willl03/android_packages_apps_Mms/commit/5a39ed699783aa1352b11199903947e4d76e2bd1

Fixes the selector popups
[Android Software/Hacking General [Developers Only]] phoenixita:
Everytime i build this committing activedisplay.java i have an error and don't let me build this..I've managed building43.08 with the active display file from carbon but now i'm not able building 4.3.1001 with activedisplayfix...
[Android Software/Hacking General [Developers Only]] willl03:
Are you talking about the MMS selector or active display fix? In both case I can build up to date source with the commits, let us know your build error and I'll try to help
[Android Software/Hacking General [Developers Only]] phoenixita:
I'm talking about the active display one...I'm trying rerepo syncing from the scratch i'll let you know if the errors comes back!
[Android Software/Hacking General [Developers Only]] wantowan2:
Has anybody worked out a change log for 4.3.10.01?
[Android Software/Hacking General [Developers Only]] phoenixita:
make: *** Attesa per i processi non terminati....

Note: frameworks/support/v4/jellybean/android/support/v4/app/NotificationCompatJellybean.java uses or overrides a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

last time i got this but my sister rebooted the pc so i can't grab a full error i'm now regiving brunch ville command to copy and paste the whole error!
[Android Software/Hacking General [Developers Only]] ny-hardcore:
hi guys,

i confronted with following error,and i'm really lost trying to solve the error

host C: acp <= build/tools/acp/acp.c
host C++: libhost <= build/libs/host/pseudolocalize.cpp
host C: libhost <= build/libs/host/CopyFile.c
i686-linux-gcc: error: 2: No such file or directory
make: *** [/home/koen/android/beanstalk/out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp.o] Error 1
make: *** Waiting for unfinished jobs....
i686-linux-g++: error: 2: No such file or directory
make: *** [/home/koen/android/beanstalk/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/pseudolocalize.o] Error 1
i686-linux-gcc: error: 2: No such file or directory
make: *** [/home/koen/android/beanstalk/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/CopyFile.o] Error 1

if i do a find -iname i686-linux-gcc in the beanstalk directory i get following results:

./prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/i686-linux-gcc
./prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/bin/i686-linux-gcc
./prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/bin/i686-linux-gcc

the files are there too:

./build/libs/host/pseudolocalize.cpp

does anything above ring a bell?
[Android Software/Hacking General [Developers Only]] mar5hal:
I wanted to start by saying thank you scott. awesome work mate. Had a build fail on me after the following; I ran the repo init from your github for 4.3, repo synced, cd vendor/cm && ./get-prebuilts then breakfast mako to pull in the device/kernel files. Once that finished I extracted the proprietary blobs from the nexus page and they went to their corresponding folders. For my first build it almost completed the process but errored out at the end. I will edit this post with a pastebin after my second attempt after i run a fresh repo sync but I am curious (and iapologize for asking this here) if the steps i took were sufficient. I know with building cm it is said that you need to be running a build of the branch you want to build from and navigate to say device/lge/mako and run ./extract-files.sh but i was under the impression that breakfast did that and the blobs from the nexus page were essentially the same process. Any help with this is greatly appreciated and if this post doesn't belong here then i will gladly delete it.

regards, mar5hal

Here is the pastebin:http://pastebin.com/mkZWjg1m

the error seems a bit different than my first and i read in the first couple pages it may take a couple repo syncs to stick but I figured i'd ask. Again any help is greatly appreciated
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
It's a mako specific problem atm. Means it's prob in the device tree. I last built successfully on Oct.1 and after that some commit killed it.

If you track it down plz post here
[Android Software/Hacking General [Developers Only]] mar5hal:
Thank you very much. It seems like it errors out at frameworks/base/core and packages/apps/settings but I'm sure everyone was aware of that given it lists it mad amounts ;) thanks for your reply
[Android Software/Hacking General [Developers Only]] patch_Adams:
device/lge/mako/overlay/packages/apps/Settings/res/values/arrays.xml:21: error: Error: No resource found that matches the given name (at '^index_0' with value '@string/gamma_tuning_contrast').

You have to fix this file. On line 21 you will find the problem. I am a rookie builder at best but after building various roms and attempting others, I have found that fixing the errors manually rather than looking for the gerrit picks (that aren't always there) can get your build moving again :)

good luck man I hope you get it going!
[Android Software/Hacking General [Developers Only]] mar5hal:
Thanks man I appreciate it. I've been trying to climb the beanstalk for some time now. Glad I finally asked :D
[Android Software/Hacking General [Developers Only]] rwaterspf1:
I just got a Nexus 4 on Saturday and got a working build by reverting commit 5600a1821abd8d642e2ce42abc5f4c1e6fb93cd2 in device/lge/mako

also reverted an older commit 2c941f82ede76dc2598fe2d67a3071882b524980 to get my home button to work

Hope this helps :)
[Android Software/Hacking General [Developers Only]] mar5hal:
Thanks man. I found the commit on github. Do we know what line 21 did to break the build? Or was it the entire array file altogether because the commit seems to have added the entire xml
[Android Software/Hacking General [Developers Only]] rwaterspf1:
The overlay is for apps/Settings so I am guessing since CM is redoing the advanced device settings it just isn't compatible with Beanstalks apps/Settings.

(on a second note I am getting my vendor tree from TheMuppets github and didn't pull them from my device).

-V
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
N4 is the canary in the coalmine. Eventually the other devices will need tlc so advanced device bits are aligned or reverted. I'm also using the muppets' tree.
[Android Software/Hacking General [Developers Only]] mar5hal:
Thanks again to everyone for their help.
[Android Software/Hacking General [Developers Only]] ktempleton:
Well Scott has already said in this thread that he wasn't going to go the way of cm with the device settings so you should fork your device tree and revert those commits so you can have the advanced settings as they have always been

sent through the worm hole from a galaxy far far away!!!!
[Android Software/Hacking General [Developers Only]] mar5hal:
Thanks. Has anyone gone as far back with reverting commits ea522384c1ecb38f0a5596ebf0241bd783b88- propmodder

e5629cab4374b4374b0002c186a90706e90a8777e3061- about beanstalk?
[Android Software/Hacking General [Developers Only]] phoenixita:
make: *** Nessuna regola per generare l'obiettivo "/home/phoenixita/beanstalk/out/target/product/ville/obj/SHARED_LIBRARIES/libqsap_sdk_intermediates/export_includes", necessario per "/home/phoenixita/beanstalk/out/target/product/ville/obj/EXECUTABLES/netd_intermediates/import_includes". Arresto.
make: *** Attesa per i processi non terminati....

Clean repo sync from the scratch :/