LEGION MODZ
I have enabled a lock on this site to keep trollz out. This is a team of Android hackerz that believes in teamwork. So, Kinfolk if you wouldn't mind, please register and log in and help us grow. A.S.A.P...

LEGION MODZ

We Are Legion
 
HomePortalCalendarGalleryFAQSearchMemberlistUsergroupsRegisterLog in

Share | 
 

 My vice Iz da device

Go down 
Go to page : 1, 2, 3  Next
AuthorMessage
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: My vice Iz da device   Mon Jan 13, 2014 5:05 pm

Ramdisk has 800kb now.  Up from 2100'$ 257 kb that almost booted
And its filled with a bunch of stuff that dont help it
Removed root folder.
Changed a few things
Going back to square one
Adding the bare essentials
I now know 123 things not to do to get this thing to boot. lol


This is pulled from the boot.img. this is backed up by me putting the rom in the kitchen.
It changed the kernel base during re-compression.
I then ran the stock rom through it without incident.
Added overlay to d tree
Completely removed prop list
Only 4 prop files remain
I ran into this in the sequent days.
I overloaded the list and broke the build.
We will see what happens without them

___________________________________________


Last edited by WARP3D420Admin on Tue Jan 21, 2014 2:51 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Wed Jan 15, 2014 5:29 pm

Extracting the proprietary binaries

Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.

Cleaning up when adding proprietary binaries

In order to make sure that the newly installed binaries are properly taken into account after being extracted, the existing output of any previous build needs to be deleted with

$ make clobber


Added "module" folder with 18 kernel modules and linked it in the device.mk
Removed prebuilt/etc/module. Removed prima folder. Added link to prima.wlan.ko
Moving everything to system/lib/modules

Removed libchromatix and other camera libs
The camera and the bluetooth seem to give developers the most problem.
Id rather it throw errata now and boot then have it screw my build.
On that subject though WiFi= very important

My build looks good though.

Kernel hasnt given much problems, other than changing out the local path
Then changing it to TARGET_KERNEL_BINARIES

Then having to change the local path back to device\…

___________________________________________


Last edited by WARP3D420Admin on Sun Jan 19, 2014 3:47 am; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Thu Jan 16, 2014 3:04 am


If anybody needs to check kernel base address
Proc/iomem with root browser

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Thu Jan 16, 2014 6:50 am

For camera, we have to add libgemini.so
Added include/spi_aic3254.h && tpa2051d3.h
and a few prop libs

I'm trying to figure out unmkbootimg binary .
I want to double check the ramdisk offset

https://www.dropbox.com/s/nkrvkslad29dxhj/zte.tar.gz
This is still a broken tree, but it has additions that didnt break the build.
i have changed a few things since making this backup.
i'm about to build again using completely different "includes"

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Sat Jan 18, 2014 1:48 am

https://www.dropbox.com/s/i8mssstvbary28c/warplte.tar.gz
Tree with a few different includes from DM/HROARK.
Havent run the build yet
Actually didnt work<----------------+update

___________________________________________


Last edited by WARP3D420Admin on Sun Jan 19, 2014 3:39 am; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
Guest
Guest



PostSubject: Re: My vice Iz da device   Sat Jan 18, 2014 9:16 am

Waiting patiently, lol...
Back to top Go down
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Sat Jan 18, 2014 1:40 pm

I'm trying big brother lol. I did some clean up on it. I'll post the new one soon. If you can work your magic for me and find out what info goes in "init.warplte.rc" and "ueventd.warplte.rc" it would be appreciated.
Maybe even a init.warplte.usb.rc

I mean my process is simple.
Choose two devs that work on similar phones.
Go to github
Study how they compiled it.
Then cherry pick the commits
Yesterday it was Shinru & PG

It works cuz my pc is so slow I get to see the errata as it scrolls down
I have been going in and fixing code in the source folders as well.


Remember,
no more "repo sync" if you change anything in the source folder.
Unless you add a folder.
Folders aren't affected by what I see


Always grab a repo of Cyan. I didnt do it, but I see where I need to now.
Sometimes during sync .cpp .h .o etc will come through broken. And need to be pulled from another source that was used as base.

Believe one thing. This is just the beginning. We will see ChA0$ L3G|0N $R0M$.
I need to make an account @ qcom I think we need drivers.
I pulled the hardware/qcom/display-media-legacy folders .
They were transferred from OG to 2 not to 3

I think the ueventd.rc works on permissions. And the init sets parameters for boot initiation. But did they pull this from init.rc , init.qcom.rc , init.goldfish.rc, init.cos.rc, init.target.rc ???

https://www.dropbox.com/s/0nda8epbnxz530p/warplte.tar.gz
This thing is torn up but its clean. Most of it. Device.mk needs subtractions.
Prop list needs to be finished.(google each lib and move it to its section)
My cos.mk needs to be switched back to common_full.mk . Etc drivers etc lol

Removed dexopt./ Config.mk
thats how you make odex .
I learn something new everyday

Errata on mesa3d, setting config.mk to     3d := false

Re-added build-info.text.

Removed the root of device/prebuilt/lib

make -C kernel O=/home/h311sdr0id/android/system/out/target/product/warplte/obj/KERNEL_OBJ INSTALL_MOD_PATH=../../system ARCH=arm CROSS_COMPILE=" /home/h311sdr0id/android/system/prebuilt/linux-x86/toolchain/arm-eabi-linaro-4.6.2/bin/arm-eabi-" modules_install
make[1]: Entering directory `/home/h311sdr0id/android/system/kernel'
 INSTALL arch/arm/mach-msm/dma_test.ko
 INSTALL arch/arm/mach-msm/msm-buspm-dev.ko
 INSTALL arch/arm/mach-msm/reset_modem.ko
 INSTALL block/test-iosched.ko
 INSTALL crypto/ansi_cprng.ko
 INSTALL drivers/crypto/msm/qce40.ko
 INSTALL drivers/crypto/msm/qcedev.ko
 INSTALL drivers/crypto/msm/qcrypto.ko
 INSTALL drivers/gud/mcdrvmodule.ko
 INSTALL drivers/gud/mckernelapi.ko
 INSTALL drivers/input/evbug.ko
 INSTALL drivers/media/radio/radio-iris-transport.ko
 INSTALL drivers/media/video/gspca/gspca_main.ko
 INSTALL drivers/mmc/card/mmc_test.ko
 INSTALL drivers/scsi/scsi_wait_scan.ko
 INSTALL drivers/spi/spidev.ko
 INSTALL drivers/video/backlight/lcd.ko
 DEPMOD  3.4.0


i like lol

But I did it by adding them in device.mk  it found the ones in the kernel folder wtf?

Went back to a d tree backup. I broke the ota package and couldnt fix it.

I could have changed code in the source but I was getting "VALUE ERROR" so I said forget it.

Did a sync. And back at it.

My slow system is a curse and a blessing
I can see errata, but I can't make changes and get back a output fast enough

@ninja . You was asking me about the device tree.
Granted I dont follow it cuz I like to learn the hard way
But go to main.mk and Makefile in build/core of source.
Good reading lol

My way goes through hundreds of variables and hack it until it either breaks or boot. I have seen too much breaking though

A little hint to aspiring developers
When you speak to the source developers for permission.
You should relay what it is you like about the rom
Be humble
Thank people that help you.
No credit= $tealin
Credit=)
LoL
Thank you goes out to
ChameleonOS
The inspiration for this forum
Got to get back to this building
My pc sucks I need Alienware

___________________________________________


Last edited by WARP3D420Admin on Mon Jan 20, 2014 12:57 am; edited 3 times in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:08 am

the next couple text will be templates for .mk files etc

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

ALL_PREBUILT += $(INSTALLED_KERNEL_TARGET)

# include the non-open-source counterpart to this file
-include vendor/__MANUFACTURER__/__DEVICE__/AndroidBoardVendor.mk

(AndroidBoard.mk)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:08 am

PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/device___DEVICE__.mk

(AndroidProducts.mk)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:09 am

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/__MANUFACTURER__/__DEVICE__/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi
TARGET_BOOTLOADER_BOARD_NAME := __DEVICE__

BOARD_KERNEL_CMDLINE := __CMDLINE__
BOARD_KERNEL_BASE := 0x__BASE__
BOARD_KERNEL_PAGESIZE := __PAGE_SIZE__

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/__MANUFACTURER__/__DEVICE__/kernel

BOARD_HAS_NO_SELECT_BUTTON := true

(BoardConfig.mk)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:10 am

## Specify phone tech before including full_phone
$(call inherit-product, vendor/cos/config/gsm.mk)

# Release name
PRODUCT_RELEASE_NAME := __DEVICE__

# Inherit some common COS stuff.
$(call inherit-product, vendor/cos/config/common_full_phone.mk)

# Inherit device configuration
$(call inherit-product, device/__MANUFACTURER__/__DEVICE__/device___DEVICE__.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := __DEVICE__
PRODUCT_NAME := cos___DEVICE__
PRODUCT_BRAND := __MANUFACTURER__
PRODUCT_MODEL := __DEVICE__
PRODUCT_MANUFACTURER := __MANUFACTURER__

(cos.mk)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:11 am

$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# The gps config appropriate for this device
$(call inherit-product, device/common/gps/gps_us_supl.mk)

$(call inherit-product-if-exists, vendor/__MANUFACTURER__/__DEVICE__/__DEVICE__-vendor.mk)

DEVICE_PACKAGE_OVERLAYS += device/__MANUFACTURER__/__DEVICE__/overlay

LOCAL_PATH := device/__MANUFACTURER__/__DEVICE__
ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := $(LOCAL_PATH)/kernel
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

PRODUCT_COPY_FILES += \
$(LOCAL_KERNEL):kernel

$(call inherit-product, build/target/product/full.mk)

PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0
PRODUCT_NAME := full___DEVICE__
PRODUCT_DEVICE := __DEVICE__

(Device_warplte.mk)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:18 am

# This is the open-source version of board-info.txt; it should contain
# version of the radio and bootloader that are available to the
# public.
require board=warplte


(board-info.txt)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 4:19 am

[
   {
       "project": "ChameleonOS",
       "repository": "android_system_vendor_zte_warplte",
       "target_path": "vendor/zte/warplte",
       "branch": "jellybean-mr1"
   }
]
[
   {
       "project": "ChameleonOS",
       "repository": "android_system_kernel",
       "target_path": "kernel",
       "branch": "jellybean-mr1"
   }
]

(cos.dependencies)

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 8:29 am

https://www.dropbox.com/s/n9lunace98dhyd2/warplte.tar
Baby steps. Since making this I had to remove the power.msm8960 package thing but much better.

___________________________________________


Last edited by WARP3D420Admin on Mon Jan 20, 2014 7:05 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
Guest
Guest



PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 5:42 pm

WARP3D420Admin wrote:
https://www.dropbox.com/s/n9lunace98dhyd2/warplte.tar
Baby steps. Since making this I shade to remove the power.msm8960 package thing but much better.

What's this?
Back to top Go down
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Mon Jan 20, 2014 5:48 pm

Its a d tree w additions but most of everything isnt linked in the device.mk cuz I'm trying new prop files from the mako
Its basically bringing everything local in the device.mk. I had blue droid in it as well but it kept trying to build but with errors

Ninja was asking me questions about the d tree from scratch

@2100. I ended up just renaming init.qcom.rc to init.warplte.rc but I removed the import until I see I need them. ty

Now to fix the system.prop

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Tue Jan 21, 2014 1:40 am

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=zte_warplte-userdebug 4.2.2 JDQ39 eng.h311sdr0id.20140120.233303 test-keys
ro.build.version.incremental=eng.h311sdr0id.20140120.233303
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Mon Jan 20 23:33:49 CST 2014
ro.build.date.utc=1390282429
ro.build.type=userdebug
ro.build.user=h311sdr0id
ro.build.host=h311sdr0id
ro.build.tags=test-keys
ro.product.model=N9510
ro.product.brand=BoostMobile
ro.product.name=zte_warplte
ro.product.device=warplte
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=warplte
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=zte_warplte-userdebug 4.2.2 JDQ39 eng.h311sdr0id.20140120.233303 test-keys
ro.build.fingerprint=BoostMobile/zte_warplte/warplte:4.2.2/JDQ39/eng.h311sdr0id.20140120.233303:userdebug/test-keys
ro.build.characteristics=phone
ro.cos.device=warplte
# end build properties
#
# system.prop for warplte
#

ro.product.operator=SPRINT
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=gpu
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=4
debug.mdpcomp.logs=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true
ro.use_data_netmgrd=true
persist.timed.enable=true
ro.qualcomm.bt.hci_transport=smd
ro.bluetooth.request.master=truero.bluetooth.remote.autoconnect=true
persist.gps.qmienabled=true
ro.qualcomm.cabl=0
ro.ril.transmitpower=true
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
ro.warmboot.capability=1
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
ro.qc.sdk.camera.facialproc=false
ro.qc.sdk.gestures.camera=false
ro.camera.sound.forced=0
net.early.sockets=0
#forbid format in mount menu
(use only rm -r)
ro.cwm.forbid_format=misc,/config,/boot,/recovery
#sdk
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#networks
ro.telephony.default_network=2
#bright or not
ro.lcd_min_brightness=40
ro.lcd_brightness=160
#multi-touch
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
#disable it
ro.config.nocheckin=1
#hold up now
ro.telephony.call_ring.delay=0
#go 2 sleep
#ro.config.hwfeature_wakeupkey=0
#come on back
mot.proximity.delay=25
ro.lge.proximity.delay=25
#ext4
ro.ext4fs=1
#debug gone
persist.adb.notify=0
#key lights
ro.mot.buttonlight.timeout=0
#disable that noise
persist.service.mount.playsnd=0
#prox sensor
mot.proximity.delay=450
mot.proximity.distance=60
#roaming much
ro.com.dataroaming=true
#scroll away
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=1

#quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100

#flash
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchintensity=65
ro.media.capture.flashintensity=70

#speed
ro.eil.hep=1
ro.enable.a53=1

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
media.stagefright.enable-meta=true
media.stagefright.enable-record=true
mmp.enable.3g2=true

#google
net.wlan0.dns1=8.8.8.8
net.wlan0.dns2=8.8.4.4
net.pdp0.dns1=8.8.8.8
net.pdp0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.eth0.dns1=8.8.8.8
net.eth0.dns2=8.8.4.4
net.gprs.dns1=8.8.8.8
net.gprs.dns2=8.8.4.4


#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cos.version=0.8-20140121-UNOFFICIAL-warplte
ro.modversion=ChameleonOS-0.8-20140121-UNOFFICIAL-warplte
ro.goo.developerid=chaos
ro.goo.rom=ChameleonOS
ro.goo.version=1390282383
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
persist.audio.handset.mic=analog
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
ro.opengles.version=131072
ro.sf.lcd_density=320
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=80
debug.egl.recordable.rgba8888=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt




not sure where its messed up

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Tue Jan 21, 2014 2:21 pm

So after countless failures, I'm once again going back to square one.
Removed system.prop
Removed device.mk
Replaced with
Core & Base.mk and Cos common.mk  with kernel & module hack && overides from the mako from old device.mk
I'm guessing with core && base I will get the android stuff
With Cos common I will get chaos stuff
Forcing the boardconfig etc to present the phone specific stuff

I'm starting to see there are a lot of issues inside of this source code
MCAssembler needs work
Qemu
Mesa3d
Harf buzz
Unpack has a "eng tag"
Icu4c

But if it doesnt break it, keep building

___________________________________________


Last edited by WARP3D420Admin on Tue Jan 21, 2014 2:50 pm; edited 1 time in total
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
Guest
Guest



PostSubject: Re: My vice Iz da device   Tue Jan 21, 2014 2:41 pm

ZTE source code broken as well...
Back to top Go down
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Tue Jan 21, 2014 3:04 pm

? Kernel source ?
Kernel 8960 builds well
Its the 8930 that is broken or ???

I havent been able to get to the boot animation. So I think I hacked the boot logo. LoL
^----------update;) I did not create my initlogo.rle file correctly and now the green guy is gone but the other pic is also.;(

@bc I found a overclock source with .conf file. I'll upload it later . Give it to rb/cdz team see if they can fix it

https://www.dropbox.com/s/pylfkmdp52s9774/overclock.zip

Made some changes via the lge blue repo will post new tree in a bit.


Pulled Android.mk from root
Pulled liblight folder
Pulled power folder
Pulled custom battery hack
Pulled a couple things from warplte.mk
Pulled FM
Added a few prebuilts
Added apn conf for strictly boost mobile from the Zte Arthur

Then we come back here after it bricks
https://www.dropbox.com/s/7fzk23zgmjrihxt/zte.tar.gz

/default.prop
/system/build.prop
/system/default.prop
/data/local.prop

The next step is start property service. In this step, a unix domain socket server is created. This socket's pathname is "/dev/socket/property_service" which is well known to other client processes.
Finally, init process calls poll to wait for connect event on the socket.

On the consumer side, when it initializes libc(bionic/libc/bionic/libc_common.c __libc_init_common function).
http://rxwen.blogspot.com/2010/01/android-property-system.html?m=1
Pulled from an article on build.prop.
It shows me that the libc bionic erratta was from the entries I added that it couldnt read
Probably out dated properties

I think I figured out the boot image issue. It calls for a init.recovery.*.rc so of course I make a init.recovery.warplte.rc. plug it in to the boot section. Build again. Lol

I may have figured out why the theme manager didnt work on chaos warp2. It doesnt pull the theme init file

@bc I need your help with something

We need a proper " overlay" & " LegionParts" . I believe PG called the CM Warp2 , Warped parts

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Fri Jan 24, 2014 2:36 pm

https://www.dropbox.com/s/97yevxh2t7pvfq8/zte.tar.gz

K so this is the tree with a little more detail added.
I made this so anyone can trace its origins even if you dont have source code
Just look for the .mk in the root folder.

Ofc I learned my lesson...
Dont mod it until after it boots lol

Tree is broken @ "did you specify -keep on connectivity test and gps test.
Jar is empty.
Instead of writing a keep flag file I just removed connection- test & gpslocation-test

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Sat Jan 25, 2014 2:35 pm

The device tree is never explained from beginning to booting. When I get it to that point I will be able to right a bad A$$ tutorial. I'm talking in depth two or three pages. Thats why I experiment so much and dont post to github.

I dont want anyone doing what I do. I learned one thing @ AF that I believe saves my butt.
Dont fool with the partition sizes.
O k maybe two
Have custom recovery.
O k two part b
Make a backup. LoL

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Sat Jan 25, 2014 9:31 pm

Word to the wise.
When running a build set up
Dont add fast jars
If you do add it
run
sudo update-alternatives --config jar
And choose the jdk

I had to add it and it broke

I added qemu-prop and bin/ pppd

Running build with the make 4.0 upgraded from 3.8.2
It works the same

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
WARP3D420\Admin
BIG DOG STATUS
BIG DOG STATUS
avatar

Posts : 195
Points : 3002101
Thanks : 7
Join date : 2014-01-02
Age : 40
Location : In da Swamps

PostSubject: Re: My vice Iz da device   Fri Jan 31, 2014 5:19 am

I $tr8 took the day off. Got lifted on them spirits. 2mara back 2 the grind

___________________________________________
Back to top Go down
View user profile http://legionmodz.forumotion.com/u1
Sponsored content




PostSubject: Re: My vice Iz da device   

Back to top Go down
 
My vice Iz da device
Back to top 
Page 1 of 3Go to page : 1, 2, 3  Next
 Similar topics
-
» Vice
» Here is some really useful information about travelling with your Ipad and using MM.
» UDID without connecting to PC/ iTunes (iOS)
» Device's date
» Time Warrior: The Armageddon Device

Permissions in this forum:You cannot reply to topics in this forum
LEGION MODZ :: ROOT UNIVERSE :: ROM DEVELOPMENT :: PHONE BRANDZ :: ###ZTE###-
Jump to: