yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Unjustified Dev:
Lol I had cwm built before I got it. I'm all over that thread . I do have code but its not for my version .
[Miscellaneous Android Development] InkSlinger420:
cool..Just looking out..
[Miscellaneous Android Development] Unjustified Dev:
Thanks bud :D
[Miscellaneous Android Development] j3r3goss:
had to add .txt to get it to upload

View attachment fstab.qcom.txt
[Miscellaneous Android Development] Eris _2.1_2010:
The one by jrummy yea

Sent From My Galaxy S4 Running BeanStalk Android 4.3 And KT's Kernel
[Miscellaneous Android Development] j3r3goss:
View attachment fstab.goldfish.txt

View attachment fstab.qcom.txt
[Miscellaneous Android Development] InkSlinger420:
hey

eris, If your running 10.2 will you check the build.prop for a line similar to

"Enable swapping of SD card"

I have read thats an option in 4.3
[Miscellaneous Android Development] Eris _2.1_2010:
All I seen was ro.emmc.sdcard.partition

Sent From My Galaxy S4 Running BeanStalk Android 4.3 And KT's Kernel
[Miscellaneous Android Development] InkSlinger420:
j3r3

Where those files in system/etc?
[Miscellaneous Android Development] afme89:
battery charge %

A bit out of topic, but I was wondering if you get the same battery bug I have in stock ICS. When the battery charges complete I unplug the phone and it drops to any were between 96 and 99% I haven't seen a steady 100% in months.
[Miscellaneous Android Development] InkSlinger420:
nope..cant say i've seen that.Mine rides at 100 for about 30-45 of nonuse before I hit 99..
[Miscellaneous Android Development] ktempleton:
Just thought I'd drop this off right here

Slim-exhilarate-4.3.beta.4-UNOFFICIAL-20130903-1416.zip - 95.56 MB

I'll update the op by the weekend with all these new builds just so you guys know I have all this source on my box already feel free to build any of these I'm in no way laying claim on them just like to have different ROMs to play with
[Miscellaneous Android Development] jobankler:
Thats because you leave it plugged in at 100%. The battery will stop charging itself at 100% but it will still show 100% so thats why it jumps to 96 when you unplug
[Miscellaneous Android Development] afme89:
You're my hero! thanks! :)

I will report how it works on my exhilarate
[Miscellaneous Android Development] j3r3goss:
I extracted them from the boot.img of the alpha 3 cm-10.2 rom.
[Miscellaneous Android Development] ktempleton:
I will say this as always slim has come in at the top of the list besides the known issues it is smooth and solid
[Miscellaneous Android Development] Eris _2.1_2010:
I can't find them anywhere lol

Sent From My Galaxy S4 Running BeanStalk Android 4.3 And KT's Kernel
[Miscellaneous Android Development] afme89:
Great Slim ktemp

really good ROM! although I have a couple of questions..

Does screen rotation work for you on home and apps menu? Mine doesn't

The app drawer icon on the bottom can't be moved.. usually don't want to move it but this time the icon isn't centered. It's about a third to the left.
[Miscellaneous Android Development] ktempleton:
I've moved all my icons around and s far as the rotation you have to open nova settings look and feel and rotation set it to auto rotate
[Miscellaneous Android Development] Unjustified Dev:
Finally [MENTION=5190980]InkSlinger420[/MENTION]

http://review.pac-rom.com/#/c/2234/
[Miscellaneous Android Development] afme89:
Ok got the auto rotate working but the circle icon with 6 white squares to be precise can't be moved.. theres space for 7 shortcuts, should be only 6 or 5.

One more thing, what camera have people used as a substitute? I tried lomo camera and didn't work
[Miscellaneous Android Development] ktempleton:
Don't know why you can't move it because as you can see mine is moving
[Miscellaneous Android Development] Unjustified Dev:
PAC is now official [MENTION=5190980]InkSlinger420[/MENTION]

https://github.com/PAC-man/android_vendor_pac/commit/48889944e72e633a672ab2f81177bac631bf591d

Also you didn't have it copying the boot animation :p fixed that as well. To fix sync errors delete vendor/PAC and sync and you shouldn't have anymore issues
[Miscellaneous Android Development] InkSlinger420:
Awesome

Thats great news!! Glad I could help...
[Miscellaneous Android Development] Dieselsmok:
Do we have to have a multi dpi play store for this slim 4.3?
[Miscellaneous Android Development] ktempleton:
Any one will do a long as it's for 4.3
[Miscellaneous Android Development] afme89:
The main problem with 4.3 and exhilarate is the dead flash.. it may be related to a driver missing.

Without a flash and a decent camera, this isn't close to a daily driver IMO
[Miscellaneous Android Development] Unjustified Dev:
Cameramx worked perfectly I doubt the flash worked though. Focal had me laughing it was moving all type of directions
[Miscellaneous Android Development] ktempleton:
That just depends on if you use the camera or not I've been running 4.3 since the Wi-Fi was fixed but I rarely use the camera
[Miscellaneous Android Development] InkSlinger420:
ok..

Heres a pac 4.3 v2 i just ran.. Havent tested it but boot ani should be fixed ie Unjustifieds adjust. Thanks bro...

http://d-h.st/oz4

Let me know...

and I RARELY use the camera also...
[Miscellaneous Android Development] j3r3goss:
Same here... Missing camera a bit, but it'll be here very soon.
[Miscellaneous Android Development] afme89:
that focal is crazy! lol I enjoyed it too.

ktemp - My phone is also my camera so its an essential feature. I have a feeling that the flash not working is related to the crashing camera app and torch..
[Miscellaneous Android Development] ktempleton:
I'm pretty sure it's all tied together
[Miscellaneous Android Development] Unjustified Dev:
I will toy with kernel again to try to fix the camera.
[Miscellaneous Android Development] InkSlinger420:
hey

I was such a big fan of liquidsmooth i am now building a 4.3 from source..FYI..Will update when finished..
[Miscellaneous Android Development] ktempleton:
Good luck I've been trying for two days and decided to give up

Don't let that discourage you though things get fixed upstream every day I just moved on to other source I have lol
[Miscellaneous Android Development] InkSlinger420:
ktemp

How far did you get in the build?
[Miscellaneous Android Development] ktempleton:
Everything but the system image and I had to work it to get it that far lol
[Miscellaneous Android Development] InkSlinger420:
good lord

Geez louise thats an interesting rom to build...about as fun as carbon...Still trying to work out the kinks..
[Miscellaneous Android Development] car vs driver:
Just a heads up guys, I'm going to bump the msm8660 kernel up to 3.0.94 over the next couple of days. Want to get that out of the way before I dig into the i577 known issues. Ideally, Mike and I want to move quickly to get us into nightlies.
[Miscellaneous Android Development] ktempleton:
Sweet
[Miscellaneous Android Development] InkSlinger420:
sounds fantastic

Really appreciate all the help from you guys..
[Miscellaneous Android Development] InkSlinger420:
Alright

Liquid is toast for the time being...I feel your pain ktemp... ;)
[Miscellaneous Android Development] ns17:
Hey guys, I'm working on AOKP, which is my first build, and I'm kinda stuck. I already synced the rom source, and I'm trying to get our device stuff to sync now.

This is the error I'm getting:

fatal: https://github.com/Cyanogenmod/andr...8660-common/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server?

And this is my local manifest file:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote name="github"

fetch="https://github.com"

/>

<project name="SGH-I577/android_device_samsung_i577" path="device/samsung/i577" remote="github" revision="cm-10.2-test" />

<project name="SGH-I577/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.2" />

<project name="Cyanogenmod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />

<project name="SGH-I577/android_vendor_samsung_i577" path="vendor/samsung" remote="github" revision="cm-10.2-test" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />

</manifest>

I've been messing with it for a while, but I can't seem to get it. Maybe I'm using the wrong kernel or something.

Any help would be appreciated. Thanks.
[Miscellaneous Android Development] ktempleton:
I would delete the kernel Samsung msm8660 common and sync again
[Miscellaneous Android Development] ns17:
Ok that worked perfect. Do I need to add a kernel or do I just build now?

Edit: When I try to build, I get this:

vendor/aokp/products/i577.mk: PRODUCT_NAME must be defined.. Stop.
[Miscellaneous Android Development] ktempleton:
Actually you should be using the exhilarate device tree from cm

I'm assuming your building 4.3

Then make your vendor/aokp/products exhilarate mk in that you need to make sure the product name is defined aokp_exhilarate
[Miscellaneous Android Development] InkSlinger420:
this is mine

I believe my local_manifests roomservice.xml reads as...

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="CyanogenMod/android_device_samsung_exhilarate" path="device/samsung/exhilarate" remote="github" revision="cm-10.2" />

<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.2" />

<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />

<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.2" />

<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.2" />

</manifest>

or you can remove the kernel line, download the kernel as zip from github and put in proper folder before build..
[Miscellaneous Android Development] ktempleton:
I always sync the ROM first and see what actually gets pulled in then I edit my room service to pull in anything that the ROM source has and then get what's left from cm especially the hardware and common folders I use the ones from the ROM I'm building if available to minimize the errors I may face while building
[Miscellaneous Android Development] ktempleton:
Let me elaborate a little on this cm uses a backup tool sh in their build aokp doesn't this is checked at the end of the build while it's zipping this check is in the release tool s found in the device Samsung msm8660 common folder if you use the cm one then it errors out and can take a couple of weeks to figure out why If you use the aokp one it zips right up that's because the aokp release tool has a file in it with one extra line

Use backuptool.sh =false that the cm one doesn't

True story by the way
[Miscellaneous Android Development] Unjustified Dev:
Figured that out when building root box months ago very true man . I found my fix looking in s2 common on their github
[Miscellaneous Android Development] ns17:
Inkslinger, I used your manifest and downloaded the kernel manually.

backuptool.sh =false gets added to releasetools.py, right?

And how do I define the product name in i577.mk?

Thanks for all the help everyone
[Miscellaneous Android Development] ktempleton:
You want it to be exhilarate.mk not i577 the name was changed also look on aokp git hub and use their device samsung msm8660 common the product name would be aokp_exhilarate I told you this in my first post by the way lol
[Miscellaneous Android Development] ns17:
Whoops I must have misread lol. I got all that sorted out, now when I try to build, I get: No config file found for TARGET_DEVICE
[Miscellaneous Android Development] InkSlinger420:
Are you lunching your build?

and have added lunch combo to vendorsetup?
[Miscellaneous Android Development] ns17:
Yup. I did: . build/envsetup.sh, then lunch, then I choose the device and it says:

No config file found for TARGET_DEVICE . Stop.

** Don't have a product spec for: 'aokp_exhilarate'

** Do you have the right repo manifest?
[Miscellaneous Android Development] ktempleton:
Did you add the exhilarate to the android products mk in the vendor aokp products folder that's what it looks like to me anyway
[Miscellaneous Android Development] InkSlinger420:
that was my first guess also...Beat me again..;)
[Miscellaneous Android Development] ns17:
Just tried that but it's still giving me the same error
[Miscellaneous Android Development] InkSlinger420:
and you have changed the name of the file in vendor/cm from cm_exhilarate.mk to aokp_exhilarate.mk and changed it in vendorsetup? I dunno..Just throwing ideas...

---------- Post added at 11:42 PM ---------- Previous post was at 11:36 PM ----------

Have you read car vs drivers guide to building?

http://xdaforums.com/showthread.php?t=1798056

He has a part about unofficial aokp.. Just wherever you see skyrocket change it to exhilarate and model from SGH-I727 to SGH-I577 in aokp/products..
[Miscellaneous Android Development] ns17:
Yess it worked! I had to fix the exhilarate.mk file in vendor/AOKP/products.

I can't believe I missed that lol.

Thanks alot man :)
[Miscellaneous Android Development] ktempleton:
So last night I synced liquid smooth and started a build before I went to sleep woke up this morning and had a zip flashed it and it's actually pretty solid will upload when I can
[Miscellaneous Android Development] :
I thought I'd pop in and report some progress. I got the stock camera up and running... Before you get too excited

1. Preview window is rotated 90 degrees on both cameras.

2. Rear Camera force closes after a bit when trying to take a picture.

3. Front Camera takes mangled pictures.

I thought the other dev's might get some insight into the problem by taking a look...

https://docs.google.com/file/d/0B7NiUakbkMuFWVhiZ2xlY09EWUU/edit?usp=sharing
[Miscellaneous Android Development] ktempleton:
Can you tell me what you did to get it where it's at that way I can get it on my end
[Miscellaneous Android Development] :
Its really not a good permanent solution. I had to write some Java code into the android framework to strip out some camera perameters that were causing those initial exceptions... Its kinda hacky, but I needed a place to start
[Miscellaneous Android Development] ns17:
So I'm at the end of building where it's zipping, and I can't figure out this error:

File "./build/tools/releasetools/ota_from_target_files", line 536, in GetBuildProp

if source_version == 0:

NameError: global name 'source_version' is not defined

Any suggestions?
[Miscellaneous Android Development] Spark1223:
As an end user, I don't care how hacky it is, as long as it works. By the way, nice progress you guys are making on this
[Miscellaneous Android Development] :
Just a shot in the dark but

export source_version=18
[Miscellaneous Android Development] ktempleton:
OK I'm just going to say thanks super secret Samsung ninja lmao
[Miscellaneous Android Development] InkSlinger420:
yeah

no joke...Where did the penguin come from?? great to have them on our side... ;)

who the.......????????????????????
[Miscellaneous Android Development] ns17:
Sorry but I'm lost lol. Where exactly do I put that?
[Miscellaneous Android Development] ktempleton:
OK I'm just going to say you need to start a github and fork whatever files you are writing to them push your changes once you get it figured out I can let the people at cm know and get it added to the source I'm serious
[Miscellaneous Android Development] :
Try typing it in the terminal before you start the build...;)

---------- Post added at 10:17 PM ---------- Previous post was at 09:54 PM ----------

Thanks for the vote of confidence but I'm not sure I can figure it out... But I'm hopeful. There's no need to get serious, I'll document what I've got so far if that's what you want, when I get some time. Right now, It's a work in diagnostics.
[Miscellaneous Android Development] ns17:
Hmm I'm still getting the same error
[Miscellaneous Android Development] :
Looks like my shot in the dark was way off...
[Miscellaneous Android Development] InkSlinger420:
for your error...

https://github.com/gimco/mytqe/blob/master/build/tools/releasetools/ota_from_target_files

maybe you can get beyond an error ...just an idea...
[Miscellaneous Android Development] :
That's what I was thinking too... When you go to that file https://github.com/AOKP/build/blob/jb-mr2/tools/releasetools/ota_from_target_files, you can see on lines 532 -537

def WriteIncrementalOTAPackage(target_zip, source_zip, output_zip):
source_version = OPTIONS.source_info_dict["recovery_api_version"]
target_version = OPTIONS.target_info_dict["recovery_api_version"]

if source_version == 0:
print ("WARNING: generating edify script for a source that "
"can't install it.")

It seems as though recovery_api_version is null. The error he was getting indicates that source_version is not defined which means that it's not even 0. He could get passed the error by changing the code to this

def WriteIncrementalOTAPackage(target_zip, source_zip, output_zip):
source_version = 0
source_version = OPTIONS.source_info_dict["recovery_api_version"]
target_version = OPTIONS.target_info_dict["recovery_api_version"]

if source_version == 0:
print ("WARNING: generating edify script for a source that "
"can't install it.")

But I think there are bigger problems. I've never build aokp but I wondering if you have to pull in the recovery source on your own... It seems to be checking the recover_api_version to know how to write the edify update script for the otapackage....
[Miscellaneous Android Development] ktempleton:
Also check to see if aokp has the device msm8660 common folder in their repo since they build for the skyrocket and Hercules I bet they do and that that error has been solved
[Miscellaneous Android Development] ktempleton:
Holy crap who is this guy and where have you been for the last 8 months lol glad you're here that's for sure
[Miscellaneous Android Development] :
As you can see, I am quite literally Meticulus ( with an exception when it comes to spelling!;)). For the past 8 months, I've been in Windows land developing a custom http proxy server. I'm new to building android, relatively new to linux but I've been writing code for years. I can write code in just about any programming language (no asm please) but am most proficient in .net C#

Nice to meet you!
[Miscellaneous Android Development] InkSlinger420:
Glad to see we were on the same page... ;)
[Miscellaneous Android Development] ktempleton:
Well then you could probably benefit with this the error the camera is throwing has to do with the focus mode trying to set an invalid number I believe it's 256 and it needs to be 1425 or something

<7>[ 2111.517547] [ISX012] isx012_sensor_open_init : E

<4>[ 2111.517669] isx012_sensor_open_init POWER ON START

<4>[ 2111.517913] isx012_sensor_init_probe

<4>[ 2111.536895] [isx012] VT STBY : 1

<4>[ 2111.747039] [isx012] I2C sleep mode

<4>[ 2111.773895] [isx012] I2C sleep mode end

<4>[ 2111.784515] [isx012] isx012_mode_transition_OM/715

<4>[ 2111.859802] [isx012] isx012_mode_transition_OM/715

<7>[ 2111.864501] [isx012] isx012_Sensor_Calibration/813

<4>[ 2111.962921] [isx012] isx012_mode_transition_OM/715

<7>[ 2111.968750] [ISX012] isx012_mode_transition_CM : E

<7>[ 2112.506439] [ISX012] isx012_sensor_init_probe : POWER ON END

<7>[ 2112.506713] [ISX012] isx012_sensor_open_init : X

<7>[ 2112.531921] [ISX012] isx012_set_scene : 1

<3>[ 2112.542022] [ISX012] isx012_set_flash:1168:FINAL flash value1(0) value2(0) isx012_ctrl->setting.flash_mode(0)

<7>[ 2112.588531] [ISX012] isx012_set_picture_size : 640

<4>[ 2112.588745] isx012_set_picture_size

<7>[ 2112.673919] [ISX012] isx012_sensor_config : cfgtype = 0, mode = 0

<4>[ 2112.674102] isx012_set_sensor_mode

<7>[ 2112.674255] [ISX012] isx012_set_sensor_mode : SENSOR_PREVIEW_MODE START

<7>[ 2112.674346] [ISX012] isx012_start : E

<4>[ 2112.674499] isx012_start

<7>[ 2112.674591] [ISX012] isx012_mipi_mode : E

<7>[ 2112.675537] [ISX012] isx012_mipi_mode : X

<7>[ 2112.727233] [ISX012] isx012_start : X

<7>[ 2115.495178] [ISX012] isx012_set_af_start : E

<6>[ 2116.969024] [ISX012]Focus mode : 256

<7>[ 2116.969268] [ISX012][isx012_set_focus_mode:1778] invalid[256/1]

<7>[ 2117.007446] [ISX012] isx012_sensor_config : cfgtype = 0, mode = 1

<4>[ 2117.007568] isx012_set_sensor_mode

<7>[ 2117.007751] [ISX012] isx012_set_sensor_mode : SENSOR_SNAPSHOT_MODE START

<3>[ 2117.007873] [ISX012] isx012_set_flash:1168:FINAL flash value1(0) value2(50) isx012_ctrl->setting.flash_mode(0)

<7>[ 2117.008087] [ISX012] isx012_set_sensor_mode : ISX012_Capture_Mode start

<7>[ 2117.056182] [ISX012] isx012_mode_transition_CM : E

<7>[ 2117.058380] [ISX012] isx012_set_sensor_mode : ISX012_Capture_Mode end

<6>[ 2124.515930] [ISX012]Focus mode : 256

<7>[ 2124.516235] [ISX012][isx012_set_focus_mode:1778] invalid[256/1]

<7>[ 2124.564788] [ISX012] isx012_sensor_release : POWER OFF START

<3>[ 2124.736358] [ISX012] isx012_set_flash:1168:FINAL flash value1(0) value2(50) isx012_ctrl->setting.flash_mode(0)

<7>[ 2124.853973] [ISX012] isx012_sensor_release : POWER OFF END

Here is the actual log
[Miscellaneous Android Development] ns17:
Ok got past that, but now I'm getting:

File "./build/tools/releasetools/ota_from_target_files", line 545, in GetBuildProp

OPTIONS.source_info_dict),

AttributeError: 'Options' object has no attribute 'source_info_dict'
[Miscellaneous Android Development] :
I haven't had a chance to evaluate the stock camera's error logs since I got it running. I just barely got it done yesterday. Is that from my build or ...?
[Miscellaneous Android Development] ktempleton:
No that's error from the unmodified build of the camera but it's what we believe is the cause if the fc to begin with
[Miscellaneous Android Development] :
Is that from trying to snap a picture on the rear camera?
[Miscellaneous Android Development] ktempleton:
That's from opening the camera
[Miscellaneous Android Development] :
What are the commands that you are using to start the build?
[Miscellaneous Android Development] ns17:
. build/envsetup.sh

lunch aokp_exhilarate-userdebug && mka bacon
[Miscellaneous Android Development] car vs driver:
Yeah, the sensor settings are jacked right now. That's one of the next things we're going to dig into and fix.
[Miscellaneous Android Development] :
try this

. build/envsetup.sh

lunch aokp_exhilarate-userdebug

make otapackage
[Miscellaneous Android Development] ktempleton:
Awesome
[Miscellaneous Android Development] ns17:
Nope, still the same.

Could it be because source_version is used twice here?

def WriteIncrementalOTAPackage(target_zip, source_zip, output_zip):
source_version = 0
source_version = OPTIONS.source_info_dict["recovery_api_version"]
target_version = OPTIONS.target_info_dict["recovery_api_version"]