Hey guys,
I done build for p5100 & p5110 but my sound is broken because of build.prop bad product name.
for the build i have product name of p5110 but for the build.prop i need espresso10wifixx
so I use
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=espresso10rfxx TARGET_DEVICE=espresso10rf BUILD_FINGERPRINT=samsung/espresso10rfxx/espresso10rf:4.0.3/IML74K/P5100XWALE2:user/release-keys PRIVATE_BUILD_DESC="espresso10rfxx-user 4.0.3 IML74K P5100XWALE2 release-keys"
into my custom_p5110.mk
But this do not override my build.prop and let the product_name as custom_p5110.
How can i solve this?
sevenup30 said:
Hey guys,
I done build for p5100 & p5110 but my sound is broken because of build.prop bad product name.
for the build i have product name of p5110 but for the build.prop i need espresso10wifixx
so I use
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=espresso10rfxx TARGET_DEVICE=espresso10rf BUILD_FINGERPRINT=samsung/espresso10rfxx/espresso10rf:4.0.3/IML74K/P5100XWALE2:user/release-keys PRIVATE_BUILD_DESC="espresso10rfxx-user 4.0.3 IML74K P5100XWALE2 release-keys"
into my custom_p5110.mk
But this do not override my build.prop and let the product_name as custom_p5110.
How can i solve this?
Click to expand...
Click to collapse
Might need to pull in a patch to support PRODUCT_BUILD_PROP_OVERRIDES... Won't be able to look at this for a few days.
All right thank you, I'll do it by hand until this.
Related
ENJOY ! And don't forget to press the Thanks button ^^
What's new ?:
- Faster (Overall speed and scrolling)
- Blue overglow effect
- Endless scrolling app menu
- Endless scrolling homescreen menu
- Better GPS signal
- NO WIFI issue for the majority
(For Belkin users: http://www.belkin.com/support/article/?lid=en&pid=F5D7230-4&aid=2437&scid=221)
- Noise reduction / Better quality during Call (need more feedback)
What sucks ?:
- Phone FC still present,
JVT Phone FIX here: (Thanks to no.one.writeme and AndiP)
http://forum.xda-developers.com/showpost.php?p=18233030&postcount=83
PLEASE, test the JVT firmware with a clean install & stock kernel before reporting any issues (Wifi, Force Close, battery charge etc...) Thanks for your understanding.
Custom kernel working on JVT:
*Semaphore 1.8 (and BM version)
*GTO Tornado Aureus Beta 1
*Midnight 0.7.6
*Speedmod K16-2
*Galaxian EE JVT
*CF-Root JVT v4.3
*Voodoo Galaxy S JVT
*TalonDev 0.5.1 RC1
*Tegrak Build 27 for JVT
NEW! DEODEXED XXJVT by Ramad:
http://forum.xda-developers.com/showthread.php?t=1290577
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Thu Sep 29 11:43:43 KST 2011
ro.build.date.utc=1317264223
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-22
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000XXJVT
ro.build.hidden_ver=I9000XXJVT
ro.build.changelist=617736
ro.flash.resolution=720
# end build properties
About installation:
"Flash using 3 files: CODE as PDA, MODEM as PHONE and CSC-HOME as CSC, you don't need to flash the big CSC file.
I did not flash the firmware yet, just looking at the files and the firmware looks good so far." Ramad.
LINK to download the JVT Firmware
http://www.multiupload.com/474JS6Q0IC
Additional download:
Electron Beam/CRT-OFF for JVT: By Bo$s
http://forum.xda-developers.com/showthread.php?t=1263527
[MOD] XXJVT stock browser with user-agent selection and unlimited tabs By Eric75004
http://forum.xda-developers.com/showthread.php?p=18174324
Tutorial
How to flash a Firmware: By jcspecs
http://forum.xda-developers.com/showthread.php?t=1139050
Sweet, another rom so soon
Yep, it's probably a bug free version of JVS.
I'll flash this one for sure !
It would be great.
Hoping all fixes are included...
Huhu, seems that samsung really want be the manufacturer nr. 1 for android phones. My next phone will definetly be a samsung one
Hope it has all the fixes
SGS_elko said:
Huhu, seems that samsung really want be the manufacturer nr. 1 for android phones. My next phone will definetly be a samsung one
Click to expand...
Click to collapse
Same for me ! (the question is... galaxy note, nexus prime or SGS III ?)
Before the hardware upgrade, i have hope for a ICS 4.0 firmware for your old SGS. The hardware is really close between the nexus S and the SGS... and in the worst case, i'll use cyanogenmod 8.
Just a question, the call quality in 2.3.5 rom are really better ? I've skip the JVS rom...
powerdams said:
Same for me ! (the question is... galaxy note, nexus prime or SGS III ?)
Before the hardware upgrade, i have hope for a ICS 4.0 firmware for your old SGS. The hardware is really close between the nexus S and the SGS... and in the worst case, i'll use cyanogenmod 8.
Just a question, the call quality in 2.3.5 rom are really better ? I've skip the JVS rom...
Click to expand...
Click to collapse
To be honest i didn't notice massive improvements on JVS regarding call quality. I had JVQ and JVR before.
xenon_bn said:
To be honest i didn't notice massive improvements on JVS regarding call quality. I had JVQ and JVR before.
Click to expand...
Click to collapse
Ok, thanks for the info. Maybe some improvement with JVT...
Nothing found on samfirmware yet. Any sources?
Hope it gets put on samfirmware soon
I have it, look the first post ; )
Sweet. Thanks.
Sent from my GT-I9000 using xda premium
powerdams said:
I have it, look the first post ; )
Click to expand...
Click to collapse
How many files 1 or 3
Thank you!
Sent from my GT-I9000 using xda premium
got-petrol said:
How many files 1 or 3
Click to expand...
Click to collapse
4 lol.
CODE_I9000XXJVT_CL617736_REV03_user_low_ship.tar.md5
GT-I9000-CSC-HOME-MULTI-OXAJVT.tar.md5
GT-I9000-CSC-MULTI-OXAJVT.tar.md5
MODEM_I9000XXJVT_REV_00_CL1064602.tar.md5
How do you flash 4 files
got-petrol said:
How do you flash 4 files
Click to expand...
Click to collapse
There is 2 CSC, the "Home" one (size=9,7 mo)
And the other one (size=86 mo)
You need to try, i'll choose the big CSC ^^
got-petrol said:
How do you flash 4 files
Click to expand...
Click to collapse
I'd just ignore the CSCs and configure the APNs by hand.
Du you guys have the sgs3 on mind for the omni rom and if is posible when can we spect the first version of this rom that sounds like is going to be an awesom custom rom for all devices.
Jairsantana said:
Du you guys have the sgs3 on mind for the omni rom and if is posible when can we spect the first version of this rom that sounds like is going to be an awesom custom rom for all devices.
Click to expand...
Click to collapse
Device requests are best asked to your device maintainers
However with it being the sgs3, it will probably come out fairly quickly
Sent from my Nexus 7 using Tapatalk now Free
Jairsantana said:
Du you guys have the sgs3 on mind for the omni rom and if is posible when can we spect the first version of this rom that sounds like is going to be an awesom custom rom for all devices.
Click to expand...
Click to collapse
Yes, it's been run on the SGS3, I believe.
pulser_g2 said:
Yes, it's been run on the SGS3, I believe.
Click to expand...
Click to collapse
so we migth get it for note 2(gt-n7100) too?
PS. if u get it builded im happy to try it out even with risk of brick.(got screen cracked so its going to insurance anyways, so i dont care if it bricks)
Jairsantana said:
Du you guys have the sgs3 on mind for the omni rom and if is posible when can we spect the first version of this rom that sounds like is going to be an awesom custom rom for all devices.
Click to expand...
Click to collapse
I9300 or a USA version? Rebellos has been working on I9300. For US variants - while technically they are easier to support due to being Qcom-based, no current Omni members have a Qcom-based S3. We'll see what the next few days/weeks bring in terms of maintainer support.
I'm doing a build for d2spr tomorrow and seeing how it goes. I might pick up the other d2xxx too.
Just because one is anonymous doesn't mean that one has privacy.
jamcar said:
I'm doing a build for d2spr tomorrow and seeing how it goes. I might pick up the other d2xxx too.
Just because one is anonymous doesn't mean that one has privacy.
Click to expand...
Click to collapse
Can barely wait... Would love this on d2spr...
How about the evil twin of the i9300? The i9305?
ezeuba said:
Can barely wait... Would love this on d2spr...
Click to expand...
Click to collapse
Downloading the source code now, there should be an alpha build later tonight.
Just because one is anonymous doesn't mean that one has privacy.
jamcar said:
I'm doing a build for d2spr tomorrow and seeing how it goes. I might pick up the other d2xxx too.
Just because one is anonymous doesn't mean that one has privacy.
Click to expand...
Click to collapse
Are you gonna share in the SprintGS3 Section?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Hit that "Thanks" Button if I helped you!
jamcar said:
I'm doing a build for d2spr tomorrow and seeing how it goes. I might pick up the other d2xxx too.
Just because one is anonymous doesn't mean that one has privacy.
Click to expand...
Click to collapse
d2att. good community! i would like to try this rom along w. d2att community.
Sent from my SAMSUNG-SGH-I747 using Tapatalk now Free
Whiplashh said:
Are you gonna share in the SprintGS3 Section?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Hit that "Thanks" Button if I helped you!
Click to expand...
Click to collapse
I'm going to try, I been having issues compiling. I've done AOSP before and can't seem to fix this one.
jamcar said:
I'm going to try, I been having issues compiling. I've done AOSP before and can't seem to fix this one.
Click to expand...
Click to collapse
whatcha hit? i have d2mtr compiling fine now. just waiting on a tester to find out if it works well or not
@shabbypenguin if you build for d2spr I'll gladly test it out right now lol.
Sent from my SPH-L710 using Tapatalk now Free
//Edited - for the builds go there - http://forum.xda-developers.com/showthread.php?t=2487507
iamikon said:
@shabbypenguin if you build for d2spr I'll gladly test it out right now lol.
Sent from my SPH-L710 using Tapatalk now Free
Click to expand...
Click to collapse
it didnt boot so im gunna hold off until things settle down a bit more.
Would be glad to test for d2spr. Can and will flash if there is a link. Also I have a laptop running Ubuntu 12.04 x64 with a 10MB/S internet connection in the office just lying idle. If I can get directions on compiling I can try as well.
Rebellos said:
Well. Since there are builds all around.
http://goo.im/devs/Rebellos/custom-4.3.0-20131014-custom_i9300-HOMEMADE.zip
GPS, BT and FM won't work.
List of cherrypicks:
Click to expand...
Click to collapse
Thank you very much for letting us try initial build. I see 9300 in build name. But just confirming again. This build is for Galaxy S3 i9300 international version right? I am really excited to see this and I am Ok with nonworking bluetooth and GPS.
Can you start a thread in i9300 forum. Or do you think it's premature?
Can someone help me? I synced all of the files (d2spr device tree, d2 common, android_kernel_samsung_d2, and all of the qualcomm things needed) and am still getting this error. Everything really does look right, I'm stumped
I run "make d2spr -j16" then get:
Code:
============================================
build/core/tasks/kernel.mk:86: **********************************************************
build/core/tasks/kernel.mk:87: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:88: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:89: * BoardConfig.mk file *
build/core/tasks/kernel.mk:90: **********************************************************
My d2spr BoardConfig.mk file is:
Code:
# Copyright (C) 2009 The CyanogenMod Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# 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.
#
# This file sets variables that control the way modules are built
# thorughout the system. It should not be used to conditionally
# disable makefiles (the proper mechanism to control what gets
# included in a build is to use PRODUCT_PACKAGES in a product
# definition file).
#
# inherit from common D2
-include device/samsung/d2-common/BoardConfigCommon.mk
# inherit from the proprietary version
-include vendor/samsung/d2spr/BoardConfigVendor.mk
# Assert
TARGET_OTA_ASSERT_DEVICE := d2spr,d2spi
# Kernel
TARGET_KERNEL_SOURCE := kernel/samsung/d2
TARGET_KERNEL_CONFIG := cyanogen_d2spr_defconfig
TARGET_BOARD_INFO_FILE ?= device/samsung/d2spr/board-info.txt
and my d2 common BoardConfigCommon.mk is:
Code:
# Copyright (C) 2009 The CyanogenMod Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# 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.
#
# This file sets variables that control the way modules are built
# thorughout the system. It should not be used to conditionally
# disable makefiles (the proper mechanism to control what gets
# included in a build is to use PRODUCT_PACKAGES in a product
# definition file).
#
# inherit from common msm8960
-include device/samsung/msm8960-common/BoardConfigCommon.mk
TARGET_SPECIFIC_HEADER_PATH := device/samsung/d2-common/include
# Kernel
TARGET_KERNEL_SOURCE := kernel/samsung/d2
BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom user_debug=31 zcache
BOARD_KERNEL_BASE := 0x80200000
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x01300000
BOARD_KERNEL_PAGESIZE := 2048
TARGET_KERNEL_VARIANT_CONFIG := cyanogen_d2_defconfig
TARGET_KERNEL_SELINUX_CONFIG := m2selinux_defconfig
TARGET_BOOTLOADER_BOARD_NAME := MSM8960
# Recovery
BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/samsung/d2-common/recovery/recovery_keys.c
BOARD_USE_CUSTOM_RECOVERY_FONT := \"roboto_15x24.h\"
BOARD_USES_MMCUTILS := true
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_MISC_PARTITION := true
BOARD_HAS_NO_SELECT_BUTTON := true
TARGET_RECOVERY_FSTAB := device/samsung/d2-common/rootdir/etc/fstab.qcom
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00A00000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00A00000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1572864000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 28651290624
BOARD_FLASH_BLOCK_SIZE := 131072
# bluetooth
BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR := device/samsung/d2-common/bluetooth
BOARD_BLUEDROID_VENDOR_CONF := device/samsung/d2-common/bluetooth/vnd_d2.txt
# Disable initlogo, Samsungs framebuffer is weird
TARGET_NO_INITLOGO := true
# Use Audience A2220 chip
BOARD_HAVE_AUDIENCE_A2220 := true
# Use USB Dock Audio
BOARD_HAVE_DOCK_USBAUDIO := true
#camera abi compatiblily
TARGET_DISPLAY_INSECURE_MM_HEAP := true
COMMON_GLOBAL_CFLAGS += -DQCOM_BSP_CAMERA_ABI_HACK
# Separate audio devices for VOIP
BOARD_USES_SEPERATED_VOIP := true
# SELinux
BOARD_SEPOLICY_DIRS += \
device/samsung/d2-common/sepolicy
BOARD_SEPOLICY_UNION += \
file_contexts \
property_contexts \
te_macros \
bridge.te \
camera.te \
conn_init.te \
device.te \
dhcp.te \
domain.te \
drmserver.te \
file.te \
kickstart.te \
init.te \
mediaserver.te \
mpdecision.te \
netmgrd.te \
property.te \
qmux.te \
rild.te \
rmt.te \
sensors.te \
surfaceflinger.te \
system.te \
tee.te \
thermald.te \
ueventd.te \
wpa_supplicant.te
Also, the android_kernel_samsung_d2 is located (and shows up) in kernel/samsung/d2 like I said, everything looks right, but something isn't.
sasikumardr said:
Thank you very much for letting us try initial build. I see 9300 in build name. But just confirming again. This build is for Galaxy S3 i9300 international version right? I am really excited to see this and I am Ok with nonworking bluetooth and GPS.
Can you start a thread in i9300 forum. Or do you think it's premature?
Click to expand...
Click to collapse
Nonworking BT/GPS says to me - "premature".
Hi guys,
I have the latest OMNI ROM and I cant find the splitview feature.
Anyone can help me?
There's some settings to do, or, just go to all apps that are already running, long press and the option should appear?
You have to have a special build of omni because split view is not yet merged into the default branch.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
My BUILD number:
omni_mako-userdebug 4.4.2 KVT49L 244 test-keys
hey guys,
im trying to port a rom for Lenovo a1000 t I found this rom for a device called lava iris(with similar MTK 6577 chipset) which is a lollipop themed rom.
need some assistance in editing the build prop.
Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.
revolutionyzer said:
Since you are porting from a lower processor to a higher , you'll have to edit the build.prop a lot.
Click to expand...
Click to collapse
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...
Check these :
vnktdpl said:
like, I edited the permissions section in the updater-script, I also made some changes in build-prop.
when I flashed it, it got flashed but it was stuck in a boot loop...
Click to expand...
Click to collapse
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck
Launcher
Hello Guys I Am Trying To Port sk17i's Laucher In My S duos 2 ......i am not able to do so.
Can anyone help me on how to port launchers of sony to samsung devices......please reply???:crying:
revolutionyzer said:
* The dpi ( if its more or less than your device's dpi , the ROM won't boot).
* Re-check if you have edited the systemui.apk or the framework.apk such that the values don't match.
* Check if the port has ' update-script ' or ' updater-script '. many new recoveries now don't support the amend format.
* Confirm that the updater-script values are not obsolete.
* Make sure you have an updated recovery.
Good Luck
Click to expand...
Click to collapse
Will check all the values by this weekend
Has it got anything to do with the build fingerprint??
Thanks for ur help
Does anyone know the difference between kernel version "[email protected]hd xxxxx#1" and "[email protected]dd xxxxx#1"?
What does "hd" or "dd" stand for?
ayuanx said:
Does anyone know the difference between kernel version "[email protected] xxxxx#1" and "[email protected] xxxxx#1"?
What does "hd" or "dd" stand for?
Click to expand...
Click to collapse
the name is mostly custom name, and was named like that by the developer himself, also one of them could be a misspelling of the other, so maybe both of them were created by the same developer
or maybe it has something to do with the rom name.
MigoMujahid said:
the name is mostly custom name, and was named like that by the developer himself, also one of them could be a misspelling of the other, so maybe both of them were created by the same developer
or maybe it has something to do with the rom name.
Click to expand...
Click to collapse
It doesn't seem to be a misspelling.
If you look wider, you will see most Samsung Galaxy devices follow this pattern.
One variant is "SWHD", the other is "SWDD".
3.10.49-5093529 [email protected] 7506#1
3.10.9-9944777 [email protected] 7520#1
3.10.28-4716428 [email protected] 7511#1
3.4.0-5869384 [email protected] 4323#1
3.3.0-4540543 [email protected] 6717#1
3.10.49-6302417 [email protected] 5922#1
3.4.0-433750 [email protected] 5006#1
3.4.0-481100 [email protected] 5604#1
ayuanx said:
It doesn't seem to be a misspelling.
If you look wider, you will see most Samsung Galaxy devices follow this pattern.
One variant is "SWHD", the other is "SWDD".
3.10.49-5093529 [email protected] 7506#1
3.10.9-9944777 [email protected] 7520#1
3.10.28-4716428 [email protected] 7511#1
3.4.0-5869384 [email protected] 4323#1
3.3.0-4540543 [email protected] 6717#1
3.10.49-6302417 [email protected] 5922#1
3.4.0-433750 [email protected] 5006#1
3.4.0-481100 [email protected] 5604#1
Click to expand...
Click to collapse
oh, you're right, i tried googling it, but ended up with nothing but that this is related only to S4 Variants, maybe one of the s4 kernel developers here can have an answer
The extra/local version (after 3.4.0 or whatever actual kernel version) is the changelist (correct me if it doesn't).
[email protected] #1:
dpi <- This is the username who compiled the build.
SWDD5922 <- Host PC where build is compiled.
#1 <- How many revisions have been done.
You can easily hijack these three values by exporting these before kernel build:
Code:
$ export KBUILD_BUILD_USER=<username> # Export a fixed username who build the kernel, ignoring current session's username
$ export KBUILD_BUILD_HOST=<hostname> # Export a fixed build host name where the kernel is built
$ export VERSION=<version> # Export a fixed revision, so it won't count at all at every dirty compile (make clean and build again)
If these values aren't set before build:
KBUILD_BUILD_USER is determined by 'whoami' command. 'whoami' command will always output your current username.
KBUILD_BUILD_HOST is determined by 'hostname' command. 'hostname' command will always output your PC's host name.
VERSION: It'll be 0 until a build is successfully compiled. Everytime build is compiled, current VERSION will be added by one and will reset when 'make mrproper' and 'make distclean' is passed from terminal.
As final note: It has nothing to do with the final kernel. The kernel might be compiled on different PCs.
Sent from my Redmi 3 using XDA Labs
Please sent new software update samsung galaxy a5 2016