I made preview of rom.
Work perfect on YouTube with HQ and same on browser.
Radio FM it's work with Spirit FM from Google Play.
using a theme I assume? what theme is it, and what weather widget is on your homescreen?
[ROM] [4.2.2] [UNOFFICIAL] CyanogenMod 10.1 for ChaCha [a810e / Status] [28.05.2013]
- Thread starter luzifer1984
- Start date
-
- Tags
- development
using a theme I assume? what theme is it, and what weather widget is on your homescreen?
So I've been using this for a while and the performance is horrible. Might just be me but sometimes it'll take 5-10 sec to wake up to the lock screen. Any ideas on how to fix this? I've only got Facebook, FTPDroid, PimpMyRom and Twitter installed if that helps (known issues maybe?)
I really wish people would actually -READ- the fracking opening posts before asking stupid questions.
tap the build no. multible times then go to performance and lock the cpu clock speed to 800 and performance governor but it will decrease battry lfe time
Hi luzifer1984
i tried to build a ROM using ur build (https://github.com/Luzifer1984/android_device_htc_chacha) the compilation failed with the below error. Do you have any idea on how to fix it? Thanks
i tried to build a ROM using ur build (https://github.com/Luzifer1984/android_device_htc_chacha) the compilation failed with the below error. Do you have any idea on how to fix it? Thanks
Code:
CC fs/read_write.o
CC arch/arm/mach-msm/board-marvel.o
CC kernel/time/timecompare.o
/home/aj/and101/kernel/htc/chacha/arch/arm/mach-msm/board-marvel.c:1206: error: unknown field
'wakeup_irq' specified in initializer
cc1: warning: unrecognized command line option "-Wno-unused-but-set-variable"
make[3]: *** [arch/arm/mach-msm/board-marvel.o] Error 1
make[2]: *** [arch/arm/mach-msm] Error 2
make[2]: *** Waiting for unfinished jobs....
CC kernel/time/timeconv.o
CC kernel/rtmutex.o
CC kernel/time/clockevents.o
Code:
target thumb C: libc_common <= bionic/libc/stdlib/assert.c
target thumb C: libc_common <= bionic/libc/stdlib/atexit.c
target thumb C: libc_common <= bionic/libc/stdlib/atoi.c
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/ajai/and101/kernel/htc/chacha'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.@ajeevlal
https://github.com/Luzifer1984/OWL-Predator-KERNEL
UPDATED 20130712. I have not TEST. I do not konw does it work.
EDIT:
https://github.com/Luzifer1984/OWL-Predator-KERNEL/commits/master
Maybe you can improve it
Last edited:
The backup kernal didnt work for me, the compile failed with below reasons for kernal https://github.com/Luzifer1984/OWL-Predator-KERNEL_BAK
also when compiled with current kernal https://github.com/Luzifer1984/OWL-Predator-KERNEL, i got the below error
Code:
host C++: libLLVMCore <= external/llvm/lib/VMCore/Verifier.cpp
Install: /home/aj/and101/out/host/linux-x86/bin/minigzip
preparing StaticLib: libc [including /home/aj/and101/out/target/product/chacha/obj/STATIC_LIBRARIES/libc_common_intermediates/libc_common.a]
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/nandroid-md5.sh
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/killrecovery.sh
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/raw-backup.sh
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/ors-mount.sh
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/fix_permissions
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/parted
Install: /home/aj/and101/out/target/product/chacha/recovery/root/sbin/sdparted
Install: /home/aj/and101/out/target/product/chacha/recovery/root/res/images/stitch.png
target asm: aroma_filemanager <= bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s: Assembler messages:
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:121: Error: selected processor does not support ARM mode `vdup.8 q0,r12'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:129: Error: selected processor does not support ARM mode `vst1.8 {q0},[r3]!'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:169: Error: selected processor does not support ARM mode `vld1.16 {d0[0]},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:170: Error: selected processor does not support ARM mode `vdup.16 q0,d0[0]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:179: Error: selected processor does not support ARM mode `vst1.8 {q0},[r3]!'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:222: Error: selected processor does not support ARM mode `vld1.32 {d0[0]},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:229: Error: selected processor does not support ARM mode `vst1.32 {d0[0]},[r3],r4'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:271: Error: selected processor does not support ARM mode `vld1.32 {d0[0]},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:272: Error: selected processor does not support ARM mode `vdup.32 q0,d0[0]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:281: Error: selected processor does not support ARM mode `vst1.32 {q0},[r3]!'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:324: Error: selected processor does not support ARM mode `vld1.8 {d0},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:331: Error: selected processor does not support ARM mode `vst1.8 {d0},[r3],r4'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:373: Error: selected processor does not support ARM mode `vld1.8 {d0},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:374: Error: selected FPU does not support instruction -- `vmov d1,d0'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:383: Error: selected processor does not support ARM mode `vst1.8 {q0},[r3]!'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:426: Error: selected processor does not support ARM mode `vld1.8 {q0},[r2]'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:433: Error: selected processor does not support ARM mode `vst1.8 {q0},[r3],r4'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:481: Error: selected processor does not support ARM mode `vld1.8 {q0},[r2]!'
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:483: Error: selected processor does not support ARM mode `vst1.8 {q0},[r3]!'
make: *** [/home/aj/and101/out/target/product/chacha/obj/EXECUTABLES/aroma_filemanager_intermediates/libs/zlib/inflate_fast_copy_neon.o] Error 1
make: *** Waiting for unfinished jobs....
target StaticLib: libc (/home/aj/and101/out/target/product/chacha/obj/STATIC_LIBRARIES/libc_intermediates/libc.a)also when compiled with current kernal https://github.com/Luzifer1984/OWL-Predator-KERNEL, i got the below error
Code:
selected FPU does not support instruction -- `vmov d1,d0'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:385: Error:
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:383: Error: selected processor does
not support ARM mode `vst1.8 {d0},[r2]!'
selected processor does not support ARM mode `vst1.8 {q0},[r3]!'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:420:
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:426: Error: Error: selected processor
does not support ARM mode `vld1.8 {q0},[r3]!'selected processor does not support ARM mode `vld1.8
{q0},[r2]'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:421:
bootable/recovery/aromafm/libs/zlib/inflate_fast_copy_neon.s:433: Error: selected processor does
not support ARM mode `vld1.8 {q2},[r3]!'Error: selected processor does not support ARM mode `vst1.8
{q0},[r3],r4'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:424: Error: selected processor does
not support ARM mode `vld1.8 {q1},[r12]!'
support instruction -- `vadd.i8 d2,d2,d14'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:1152: Error: selected FPU does not
support instruction -- `vadd.i8 d2,d2,d0'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:1153: Error: selected FPU does not
support instruction -- `vmov d1,d3'
bootable/recovery/aromafm/libs/png/png_read_filter_row_neon.s:1154: Error: selected processor does
not support ARM mode `vst1.8 {d2},[r2]!'
make: ***
[/home/aj/and101/out/target/product/chacha/obj/EXECUTABLES/aroma_filemanager_intermediates/libs/png
/png_read_filter_row_neon.o] Error 1
aj@aj-VirtualBox:~/and101$
yes Chacha is not neon.... i pulled the source using local manifest --> https://raw.github.com/Luzifer1984/android_device_htc_chacha/cm-10.1/extra/roomservice.xml
and based on the xml the bootable/recovery in pulled for repository --> <project name="PhilZ-cwm6/philz_touch_cwm6" path="bootable/recovery" revision="cm-10.1" /> and it looks some recent commits were done (2 days back) to PhilZ-cwm6/philz_touch_cwm6
my question is do we have any alternate sources for this? or can armoa_filemanager alone be removed during compile?
Thanks in advance for your help
and based on the xml the bootable/recovery in pulled for repository --> <project name="PhilZ-cwm6/philz_touch_cwm6" path="bootable/recovery" revision="cm-10.1" /> and it looks some recent commits were done (2 days back) to PhilZ-cwm6/philz_touch_cwm6
my question is do we have any alternate sources for this? or can armoa_filemanager alone be removed during compile?
Thanks in advance for your help
Last edited:
yes Chacha is not neon.... i pulled the source using local manifest --> https://raw.github.com/Luzifer1984/android_device_htc_chacha/cm-10.1/extra/roomservice.xml
and based on the xml the bootable/recovery in pulled for repository --> <project name="PhilZ-cwm6/philz_touch_cwm6" path="bootable/recovery" revision="cm-10.1" /> and it looks some recent commits were done (2 days back) to PhilZ-cwm6/philz_touch_cwm6
my question is do we have any alternate sources for this? or can armoa_filemanager alone be removed during compile?
Thanks in advance for your help
You can do something like git reset --hard badcommithash~1 and compile without those commits
i see luzifer1984 has fixed the local manifest file to remove the bootloader/recovery.
but still the compile fails with it reads below file....
but still the compile fails with it reads below file....
Code:
target thumb C: libbt-brcm_stack <= external/bluetooth/bluedroid/stack/./btm/btm_main.c
device/htc/msm7x27-common/overlay/frameworks/base/core/res/res/values/config.xml:199: error: Resource at config_screenOnAnimation appears in overlay but not in the base package; use <add-resource> to add.
device/htc/msm7x27-common/overlay/frameworks/base/core/res/res/values/config.xml:208: error: Resource at disableSoftwareHDR appears in overlay but not in the base package; use <add-resource> to add.
make: *** [/home/aj/and101/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Error 1
make: *** Deleting file `/home/aj/and101/out/target/common/obj/APPS/framework-res_intermediates/package-export.apk'
make: *** Waiting for unfinished jobs...use <add-resource> to add. @ajeevlal TWO WAYS
https://github.com/Luzifer1984/andr...mmit/aef90afd28627498382ef0ca1e32a26c28cca432
Last edited:
thanks a lot, that solved most of the problem.......now rom is compiled (with current kernal).... and it fails after flashing.....
here is the log and i dont see any error in the log, may be i am wrong... can you help?
here is the log and i dont see any error in the log, may be i am wrong... can you help?
Code:
Starting recovery on Sun Jan 6 00:01:05 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 320)
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
mtd: successfully wrote block at fffffd5800000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRJ90
ro.build.display.id=GWK74
ro.build.version.incremental=eng.adlx.20120415.000333
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Apr 15 00:03:42 CEST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=adlx
ro.build.host=localhost
ro.build.tags=test-keys
ro.product.model=HTC ChaCha A810e
ro.product.brand=htc
ro.product.name=htc_chacha
ro.product.device=chacha
ro.product.board=chacha
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=chacha
ro.build.description=1.54.401.2 CL189894 release-keys
ro.build.fingerprint=htc_europe/htc_chacha/chacha:2.3.5/GRJ90/189894.2:user/release-keys
ro.cm.device=chacha
ro.product.sym_ime_picker=disabled
ro.device.screenrotation=90
persist.sys.scrollingcache=2
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
ro.compcache.default=0
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.def.agps.mode=2
ro.ril.hsxpa=2
ro.ril.gprsclass=12
mobiledata.interfaces=rmnet0,rmnet1,rmnet2,gprs,ppp0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.sf.lcd_density=160
ro.opengles.version=131072
dalvik.vm.dexopt-data-only=1
ro.telephony.default_network=0
dalvik.vm.heapsize=32m
settings.display.autobacklight=1
settings.display.brightness=143
persist.service.mount.playsnd=0
ro.com.google.locationfeatures=1
ro.setupwizard.enable_bypass=1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
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.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
persist.sys.themeId=Cyanbread
persist.sys.themePackageName=com.tmobile.theme.Cyanbread
ro.modversion=CyanogenMod-7.2.0-RC1-chacha-UNOFFICIAL
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT16SV409382
ro.bootmode=recovery
ro.baseband=7.51.35.19
ro.carrier=ALL
ro.bootloader=1.13.0000
ro.hardware=chacha
ro.revision=128
ro.emmc=0
init.svc.choice_fn=stopped
init.svc.adbd=running
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at fffffd5800000000
I:Set boot command ""
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
24CyanogeMod 10.1 for HTC ChaCha [a810e / Status]
Code:/* * Your warranty is now void. * * I am not responsible for bricked devices, broken hearts, * thermonuclear war, you getting fired because the alarm app failed, or * unfulfilled sexual partners. Please do some research if you have any * concerns about features included in this ROM before flashing it! YOU are * choosing to make these modifications, and if you point the finger at me * for messing up your device, I will point that finger back at you and laugh. * make sure you do a nandroid backup in case your phone blows up in * your face because your phone cant handle the speed :). */
Code:Google Android CyanogenMod androidarmv6 OWLProject Andreas Schneider Special thank to winsuk Special thank to JDevs (kernel,Device & Vendor,bug fixed,guide,support) alquez Droste pabloPL WFS: crossfire77 rallapag ChaCha: adumont (patches Lucas Arran everyone who's been working on CM10.1 And you!
??? I have not tested themCode:- GSM - Data (2G/3G) - SMS / MMS - GPS ??? - USB - Bluetooth - WI-FI - LED - Camera - Photocamera [fully] - Camcoder (low FPS) - Panorama mode [figured screen sometimes,It can be fixed easily] - Video playback [not fully, with the 90º rotation playback,It can be fixed easily] - YouTube [LQ/HQ/Browser] ??? - FM ???
BUG:
Code:- Battery drain fast - Front camera - USB Tethering - Wi-Fi-Modem - A2DP lag - FM Radio - in-call screen - caller picture is not in the right place with the right dimensions.It can be fixed easily
https://github.com/OWLProject/OWL-Predator-KERNEL/blob/master/README.md
NO NEXT
BUT I'll upload my source files and step-by-step guide on my github(https://github.com/luzifer1984). a few days later.
I'm Chinese,so I would not compile next ROM for WWE.
My next build is only support for HTC CN CHS.
You can build a rom from source. plz add zh_CN (Chinese Simplified) support. THX!
cm-10.1-20130528-EXPERIMENTAL-chacha-A1.zip
https://docs.google.com/file/d/0B2l4GSuwT6TKMExrRXpmXzZyb3M/edit
CronMod-INT2EXT
http://xdaforums.com/showthread.php?t=1716124
33
with your advice the incall screen is fixed, but i was not able get the proximity sensor work with the patch from adumont.... do i need to apply all the patches available in five folders under 'adumont/android_device_htc_chacha / extra / patch /' or just the patches in folder 'android_packages_apps_Phone'?
and i have released the compiled rom.... all credits go to you man. Thank you :good:3
go to /system and find the build.prop file and search for this line "ro.sf.lcd.density=150" and change it to "160" and reboot into recovery and wipe data and cache all will go right with all apps in the play store
New posts
-
Does usb otg not work on all custom roms or works on some?
- Latest: myanonymousaccountname
-
-
-
