yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] desalesouche:
same here.
[Android Software/Hacking General [Developers Only]] Dr.Gasmo:
I didn't
[Android Software/Hacking General [Developers Only]] timpohladthomas:
Haha, thanks.
[Android Software/Hacking General [Developers Only]] patch_Adams:
Has anyone lost settings->advanced in their latest build last few days?? I don't have the option in settings anymore. I have looked through git a bit and am sort of lost here...
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
Thx for the update Scott.

Samsung Galaxy S4 (jfltetmo) is OK (capacitive keys) and the optional navbar does work. So, it seems to affect softkeys-only devices. Mako has currently nonworking home softkey.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
I literally just posted about this... Your device settings are not lost, they were intentionally removed from your device tree from the cm changes.... Please pay attention to what is added/removed from your device/kernel sources.

For those that reported the home key issues... Was it working on the first 4.3 release from the other week and stopped on this past release or has it been busted since the start of 4.3.. ?
[Android Software/Hacking General [Developers Only]] patch_Adams:
I saw your post Scott...and I appreciate your reply. I have been trying to locate the changes but being the inexperienced rookie that I am I have not found them yet. I'll keep looking.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Its cool, whats the link to the cm device repo that you are using?
[Android Software/Hacking General [Developers Only]] patch_Adams:
I use these...not sure which one it'd be under

CyanogenMod/android_device_samsung_msm8660-common

CyanogenMod/android_device_samsung_quincyatt

CyanogenMod/android_device_samsung_qcom-common

CyanogenMod/android_device_samsung_quincy-common

I wonder is this the one or no??

http://review.cyanogenmod.org/#/c/47886/
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
No that change isn't what I'm referring to. The change is probably under one of the common devices you use... And it'll be something along the lines of "removed advanced device settings"... Away from computer at the moment... I can take a look for you in a bit
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Honestly though... I wouldn't sweat it... I'm going to follow their layout which will remove the device settings anyways... Hopefully soon.
[Android Software/Hacking General [Developers Only]] patch_Adams:
Appreciate it. I'm leaving for work soon, I'll check back at lunch or in the a.m.

edit:

I found it.....I should spend more time on gerrit...I see the removed settings right in the code...thanks again man!
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
No problem.... Gotta look out for all the baby stalks out there. :)
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Guys with home key issues... Can you get me links to the device/kernel repos you are using? Also a logcat? From first glance I don't see anything out of the ordinary..
[Android Software/Hacking General [Developers Only]] ktempleton:
Is any one else having an issue in frameworks base services GPS not declared in this scope error
[Android Software/Hacking General [Developers Only]] timpohladthomas:
It was working on 4.3 up until about maybe the August 19th build.

Device repo

https://github.com/CyanogenMod/android_device_motorola_msm8960-common

https://github.com/CyanogenMod/android_device_motorola_xt907

Kernel repo

https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common
[Android Software/Hacking General [Developers Only]] csking33:
http://pastebin.com/ALsMb9Ek

Those are all the errors thrown when it's pressed. If you need more let me know.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Thanks for the info... as suspected... i think this might be related to a CM change and not an issue with my build... Do me a favor...

cd to your device/motorola/msm8960-common tree (or however you have it)

issue the following:

git revert 20a44095b706c073f63cbf38dc69cb2d4169fda6

You should get something along the lines of "revert: Overlay: Indicate that we have no hardware keys on device face" - Just hit ctrl x and y to save the changes.

Then try to rebuild and let me know the results. Not sure if that is the issue or not, but it stands out to me... And the commit is from the 20th... which is right around the time you said it stopped working.

Please report back ASAP.
[Android Software/Hacking General [Developers Only]] timpohladthomas:
Ok, doing this now then will build and let you know

Edit: Building has started...I am on a build server so should be fast...
[Android Software/Hacking General [Developers Only]] :
[MENTION=5275632]patch_Adams[/MENTION] take a look at this post

http://xdaforums.com/showpost.php?p=44746084&postcount=548
[Android Software/Hacking General [Developers Only]] timpohladthomas:
Build, just finished, i flashed a test and VOILA that solved the home key issue! Good sleuthing! Let me know if there is anything else you need from me. All works great now.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Figured it would... told you my build was fine. :). Just goes to show you.... you really need to keep an eye on what goes into your device/kernel trees as alot of those commits are CM specific and will break my build or your device.

The other guy that was having the issue... Send me a link to your device/kernel trees so i can fix your build as well.
[Android Software/Hacking General [Developers Only]] timpohladthomas:
Thanks buddy, I was pretty sure it was my fault all along. :)
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Its cool man... it wasnt necessarily your fault as much as it was a case of overlooking something. Honestly, that commit shouldnt have been introduced and should be reverted on the CM end of things... When a repo is labeled as 'common', they need to verify that any change or addition that is introduced will not have a negative effect of any of the devices that count on it... I have a feeling this is the same exact scenario that is causing the issue for the other person.
[Android Software/Hacking General [Developers Only]] csking33:
Will do, at work now so it'll be in the morning. I'll take a look before I send a link to see if I can save you some work. Thanks again.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Sounds good. Gotta be something in one of your trees.

On a separate note... What do you guys think of the new cm settings menu layout? I'm still not sure if I want to keep the layout how I have it now or conform to their standards. Either way, I will follow them by removing device settings and adding their new hardware settings
[Android Software/Hacking General [Developers Only]] desalesouche:
hi am facing error while compiling bean 4.3.

http://pastebin.com/hDLUTL9m

compiling for huawei u8800pro.

https://github.com/desalesouche/android_device_huawei_u8800pro

https://github.com/desalesouche/android_vendor_huawei-1/tree/cm-10.1/u8800pro

thank you.
[Android Software/Hacking General [Developers Only]] timpohladthomas:
hey buddy,

this is probably on my end, but i keep getting this while compiling. I even rm -rfed my folder to make sure i hadnt messed something up.

http://pastebin.com/DZGj5Jfw

Also, as a note, I am getting this error on most of my cm based ports.
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
okey dokey!

https://github.com/CyanogenMod/lge-kernel-mako

https://github.com/CyanogenMod/android_device_lge_mako

https://github.com/TheMuppets/proprietary_vendor_lge

I didn't have the device since 4.300 arrived, so no idea when it stopped working after 1.300. I'm borrowing a Nexus 4 now to diagnose the prob.

logcat pastebin

Looks like a lot of these:

E/InputManager-JNI( 607): An exception was thrown by callback 'interceptKeyBeforeDispatching'.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Ok.. Same exact issue as the other guy.... In you device tree commits... There is one labeled "define hardware keys properly". You need to either revert that commit or you can just remove the code from the commit. That's all...

Now... If anyone else is having the same issue, I'm hoping you can figure it out since it is confirmed that a device change for hardware keys is what broke it... Just revert it then build and your good to go. Again, my build isn't exactly like cm... You need to look at what your adding to your source... I dont mind helping, but i am extremely limited with free time and barely have enough time to work on my own stuff.

EDIT:

More specifically... cd to your device/lge/mako

issue the following:

git revert 2c941f82ede76dc2598fe2d67a3071882b524980 - Then hit ctrl x - then y

then just build. That reverts the hardware commit that broke your device.
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
brilliant! thanks again Scott. after reading some of the stuff behind the scenes re: CM and recent botches in management I'm wondering if it's possible to port BeanStalk to another base, eg PA? or is this just insane uninformed boobery.?
[Android Software/Hacking General [Developers Only]] wantowan2:
Hey there. I am assuming this is something on the BeanStalk side as this doesn't happen on a strait cm10.2 compile.

So basically, if I 'make recovery' it stops here. I know all the bootable stuff comes from cm too.

EDIT:

Difforent issue but I know this is happening with a few of us on Samsung msm8660-common devices. I'm sure it's just some sort of update needed but I can even trace it...
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
The samsung common device has the commit implemented that breaks the hardware keys on the beanstalk builds.... So yes... If your having hardware key issues, it is the exact same thing and you just need to revert that one commit for it. Plain and very simple. If you'd like I can give you the commit you need to change. This is not cm... This is beanstalk. Id suggest to all builders to manually pick what goes into your device and kernel repos... That way you won't have something added for cm that breaks beanstalk.
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
FYI.... New beanstalk will be dropping tomorrow night at some point. The key thing that needs to be pointed out and really watched from this point forward is that beanstalk and cm have come to a split in the road. Up until now I've been able to maintain close similarity to cm to make things easier on you guys so you wouldn't have to worry about what you added into your device source. Well... That has changed. Cm is using a new settings layout and I do not agree with it and will be sticking with the same layout. It just makes more sense to me. Part of their new layout is removing the advanced device settings and implemented something called 'hardware tunables'... Or something along those lines. I will NOT be doing that. Beanstalk is going to be keeping the advanced device settings and I am not implementing their tunables in any way shape or form at this current time. What this means for the builders... There are going to be cm commits for your device that just will not work for beanstalk. The types of commits your going to want to avoid will say something about tunables and removing device settings. Do not use those.. You will end up with no advanced device menu if you do. I'm sure there are going to be a few other differences, but its your responsibility to understand and know what your adding/removing in your device repos.
[Android Software/Hacking General [Developers Only]] wantowan2:
Hardware keys? Not here. It was recovery. I noticed a whole bunch of frameworks reverts that seemed to fix the issue for my compile. I didn't mean to blame one thing or another. The limit of my knowlege ended at the cm recovery sources.

If I could ask... would these be something that we could put in our roomservice file to avoid them? (Like or similar...)

...or is that only something that you can do with manifest...?
[Android Software/Hacking General [Developers Only]] patch_Adams:
Two quick things.....

1. Why has holo launcher been fc'ing??

Edit: after update holo seems to be ok

2. I did a revert on the advanced settings commit (here) and I still have no advanced settings?

What am I borking up??
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Ah i see... sorry i misread that. The framework commits i reverted wouldnt have had any effect on anything related to the errors you were receiving. My guess is either a repo sync needed to be done to pull in the latest source or you were dirty building and needed a make clean. To answer your question, no that would not work. What id suggest you do is remove your device tree from your local manifests so that it is not updated when you repo sync... then you can go to the cm repo for your device and look to see if there is anything you can use on your end.
[Android Software/Hacking General [Developers Only]] timpohladthomas:
hey man, just an update...whatever you changed last night has fixed any build issues I was having. Thanks for all your work.
[Android Software/Hacking General [Developers Only]] desalesouche:
hi all.errors while compiling 4.3 for u8800pro.

http://pastebin.com/G34YymAV

may i request some help/advices? thank you
[Android Software/Hacking General [Developers Only]] patch_Adams:
Scott, you are genius man!!
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
So I was going to get a new build out last night ... But then I passed out in my couch.... I guess my lack of sleep finally caught up and got the better of me. Update will be released tonight.
[Android Software/Hacking General [Developers Only]] BMP7777:
Has anyone seen this?
[Android Software/Hacking General [Developers Only]] lreyes:
I occasionally get those but I just ignore and repo sync then brunch "device".
[Android Software/Hacking General [Developers Only]] BMP7777:
That's what I've been doing, but it just continues to error out. Tried disabling the andoid.mk there to get some forward motion, but it errored out right after anyway. If you think of anything, please let me know.
[Android Software/Hacking General [Developers Only]] patch_Adams:
Folks.....I am trying to edit my updater-script so I can give the torch the proper permissions to work properly...and while I'm not sure if it'll even work, I'd like to try......I understand I need to mount /sys before I can edit the permissions on my torch device node....can anyone help me out??

This is a line from my current script:

mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/system");

I need it to mount /sys but don't know the block address or how to find the block address...any help is appreciated.
[Android Software/Hacking General [Developers Only]] :
it's easy great guide to find your need is here :- http://xdaforums.com/showthread.php?t=1959445

my question was i m sucessfully building

cm 10.2 for my device (not supproted officially by cyanogenmod)

so .. building beanstalk has same procedures

Means i have to intialise beanstalk repo

and use same local_manifest like cm

and then

./buildenvsetupsh

and breakfast <device>

brunch(device)

for reference u can look here http://xdaforums.com/showthread.php?t=2397249

i m talking about xperia 2011 line up .. here is guide through which i build cm 10.2

thanks
[Android Software/Hacking General [Developers Only]] lreyes:
It may be the problem where you sync many repos.. I did that so ill start fresh and let you know.
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
No problems here. 4.307 is brilliant! Thanks again Scott.

Apparently many of the users love listview animations :confused:
[Android Software/Hacking General [Developers Only]] :
New version going well for N7100, N7000, and Kindle Fire.

I wrote a script that unzips the ROM, changes build.prop to have your own goo.Im info, and repackges it in one sweep, so all you devs can setup for OTA updates without troubles.

I will post it soon when I get back to a computer.
[Android Software/Hacking General [Developers Only]] phoenixita:
I followed this guide blended to this http://wiki.cyanogenmod.org/w/Build_for_ville

And i managed to get a 4.2.2 working Beanstalk ROM searching on the net i've found that there are some 4.3 Beanstalk's roms is there a way i can make one? We have a full working cm 10.2

Nvm i found it just searching I'm a noob :P
[Android Software/Hacking General [Developers Only]] willl03:
Same #2, reverted the DeviceSettings delete commit, the files are there but it's not getting built, no device settings in the build.zip

Anyone managed to get the advanced settings showin up?
[Android Software/Hacking General [Developers Only]] patch_Adams:
By using this repo instead of CyanogenMod's I was able to get advanced settings in my build...

https://github.com/JamieD81/android_device_samsung_msm8660-common

this commit: https://github.com/JamieD81/android...mmit/66a0648299b05e0911e370f0f5c549c7390c09e6

is genius!

I don't know if this'll help you with your device or not , but it's how I got the settings back....

Holo just has to update through the play store and it'll stop FC'ing
[Android Software/Hacking General [Developers Only]] willl03:
Thanks man! Will try to find the difference between this commit and the CM one to make changes for my device
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
Good find, thanks for sharing.

Can't wait til CM's hardware tunables framework is finished so we don't need to revert and keep the old Advanced Settings interface.
[Android Software/Hacking General [Developers Only]] :
Advanced settings are gone for good, unless CM makes a drastic decision change. At this point its never planned to be back

Read my post here from a few days ago
[Android Software/Hacking General [Developers Only]] CrashTestDroid:
IIRC it looks like the Advanced Settings functionality will be back but with a different back-end interface. So all the good stuff (like disable capacitive keys lights and screen tuning) will be set in other areas of the interface. Or am I wrong here?
[Android Software/Hacking General [Developers Only]] BMP7777:
Anyone ever see this and get past it?

In file included from hardware/qcom/display-caf/libexternal/external.cpp:31:0:
/home/bmp7777/beanstalk/out/target/product/m7spr/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h: In function 'void MSM_HDMI_MODES_INIT_TIMINGS(msm_hdmi_mode_timing_info*)':
/home/bmp7777/beanstalk/out/target/product/m7spr/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h:214:91: error: narrowing conversion of 'i' from 'int' to 'uint32_t {aka unsigned int}' inside { } is ill-formed in C++11 [-Werror=narrowing]
cc1plus: all warnings being treated as errors
make: *** [/home/bmp7777/beanstalk/out/target/product/m7spr/obj/SHARED_LIBRARIES/libexternal_intermediates/external.o] Error 1
make: *** Waiting for unfinished jobs....
bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/beanstalk$

Posted the other day, and still stuck there....
[Android Software/Hacking General [Developers Only]] :
Ok, I got some sirious problems here. I got some errors during compiling and I tried with resyncing and repo sync gave me the next error:

kv1dr@kv1dr-Extensa-5635G:~/beanstalk/system$ repo sync
Traceback (most recent call last):
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/main.py", line 414, in <module>
_Main(sys.argv[1:])
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/main.py", line 390, in _Main
result = repo._Run(argv) or 0
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/main.py", line 122, in _Run
copts, cargs = cmd.OptionParser.parse_args(argv)
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/command.py", line 67, in OptionParser
self._Options(self._optparse)
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/subcmds/sync.py", line 152, in _Options
self.jobs = self.manifest.default.sync_j
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/manifest_xml.py", line 292, in default
self._Load()
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/manifest_xml.py", line 327, in _Load
b = m.GetBranch(m.CurrentBranch).merge
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/project.py", line 573, in CurrentBranch
b = self.work_git.GetHead()
File "/media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/repo/project.py", line 2090, in GetHead
raise NoManifestException(path)
error.NoManifestException: /media/02723b66-6456-44bb-af83-ba5d262ee10a/kv1dr-elementary/beanstalk/system/.repo/manifests/.git/HEAD

I tried removing the repo folder, and running repo init, but after repo sync I get the same error
[Android Software/Hacking General [Developers Only]] wantowan2:
I would say that it thinks something has changed in your build trees/kernel. For those, I think I get by it by not only deleting your kernel folder contents but also go to '.repo/projects/kernel' and delete that too.

You might still be left with that last shared libraries tho
[Android Software/Hacking General [Developers Only]] phoenixita:
Is there a way to check changes? Are patches being submitted to the github?
[Android Software/Hacking General [Developers Only]] :
Thanks to [MENTION=4552996]scott.hart.bti[/MENTION] for awsome beanstalk

http://xdaforums.com/showthread.php?t=2429842 here my port for xperia Mini / mini pro / live with walkman /Arc-s
[Android Software/Hacking General [Developers Only]] wantowan2:
That's messed up. Because I have been using the revert you posted before that didn't work for you.

Worked like charm, thanks.
[Android Software/Hacking General [Developers Only]] patch_Adams:
The git repo I posted a link to had been taken down for everyone's fyi.....:(

sent from somewhere upon the beanstalk
[Android Software/Hacking General [Developers Only]] :
Its only for the snapdragon devices anyhow.

It's not feasible to use for other devices.
[Android Software/Hacking General [Developers Only]] BMP7777:
Has anyone gotten past this? I have been trying to sync for days now and continue to get this error. My build still won't compile and I have no idea if this is the reason or just a different issue. Somebody throw this poor dog a bone....
[Android Software/Hacking General [Developers Only]] :
bro restart from scratch by deleting Beanstalk folder and do again it somehow worked for me..:)
[Android Software/Hacking General [Developers Only]] BMP7777:
How long ago? I've tried that twice with no change, but it has been a few days. Either way, thanks for the tip. I haven't gotten any feedback on that or my other issues and it was driving me nuts.
[Android Software/Hacking General [Developers Only]] phoenixita:
every build i try comes out withouth the camera app....kernel for my device has changed to 3.4.60 may be this the problem?
[Android Software/Hacking General [Developers Only]] BMP7777:
Complete deletion of build files, fresh sync and build command, and once again .... this:

In file included from hardware/qcom/display-caf/libexternal/external.cpp:31:0:
/home/bmp7777/beanstalk/out/target/product/m7spr/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h: In function 'void MSM_HDMI_MODES_INIT_TIMINGS(msm_hdmi_mode_timing_info*)':
/home/bmp7777/beanstalk/out/target/product/m7spr/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h:214:91: error: narrowing conversion of 'i' from 'int' to 'uint32_t {aka unsigned int}' inside { } is ill-formed in C++11 [-Werror=narrowing]
cc1plus: all warnings being treated as errors
make: *** [/home/bmp7777/beanstalk/out/target/product/m7spr/obj/SHARED_LIBRARIES/libexternal_intermediates/external.o] Error 1
make: *** Waiting for unfinished jobs....

Nobody else has repeatedly gone through this? And gotten past it?