Database Info

Device & Vendor files released for HTC Chacha (CM7 & SuperOSR)

Hi,
I've decided to publicly release my device & vendor files for HTC Chacha:
https://github.com/adumont/android_device_htc_chacha
https://github.com/adumont/android_vendor_htc_chacha
https://github.com/adumont/htc-kernel-msm7227
Hopefully someone can help with the missing parts and help getting the rom better with a better support to this nice little phone (if that is the case I'd appreciate people to do pull request and share their work).
To build SuperOSR:
Code:
repo init -u git://github.com/SuperTeam/android.git -b gingerbread
repo sync
. build/envsetup.sh
lunch team_chacha-eng
make bacon
Let's the fun begin (or continue) :-D
IIRC, here are the modifications I did to other repositories:
* Change I87e5f21d: Add chacha support (HTC ChaCha A810e)
http://review.cyanogenmod.com/#change,11922
* Change Ice487342: InputMethodManager: prevent Sym key from displaying the IME picker
http://review.cyanogenmod.com/#change,11924
https://github.com/SuperTeam/android_frameworks_base/commit/78e0d0ed4b9850292856a5720589f58690ebf1f9
* Change I279d3283: Implement rotation compensation for landscape devices
http://review.cyanogenmod.com/#change,11925
https://github.com/SuperTeam/androi...mmit/eafe204ce415d05c49f687512955bb78e2097cea
Unnecessary patches (Abandonned or already merged):
* Change Ic7ad89ac: Change proximity behaviour for devices w/ fixed keyboard (MERGED)
http://review.cyanogenmod.com/#change,11926
https://github.com/SuperTeam/androi...mmit/942d97d95495705d6f46b3d5d43cfbd10efe0d64
* Declare chacha as VISION_KEYPAD (ABANDONED)
https://github.com/SuperTeam/android_frameworks_base/commit/fb7326a1ec2db3be7e25ea3dece6ddf1d2999bd7
http://review.cyanogenmod.com/#change,11923

Reserved for future use

Noob-question: what can i do with this stuff or other way ... what will be possible?

basti84 said:
Noob-question: what can i do with this stuff or other way ... what will be possible?
Click to expand...
Click to collapse
You can download the sources, and build a rom from source for HTC Chacha.

adlx. add the camera fixes to your mods list in the OP.

Alex C. said:
adlx. add the camera fixes to your mods list in the OP.
Click to expand...
Click to collapse
Added (for the moment it's a temporary fix, it's not pushed even to SuperOSR git)

I have pushed the changes to Gerrit, for CM team to review them:
http://review.cyanogenmod.com/#dashboard,1829

adlx.xda said:
I have pushed the changes to Gerrit, for CM team to review them:
http://review.cyanogenmod.com/#dashboard,1829
Click to expand...
Click to collapse
This would mean official CM support, right?
Also: might it be a good idea to get CWM Recovery that we have in the forums submitted to koush so we can use ROM Manager too?

Yeah good idea. I'll build one tomorrow from my sources...

Just a tip: If you can, add ext2/3/4 mounting in it - the current CWM we have can't mount /sd-ext, but can format it

2-way / 2wcr kernet patch
will be possible to patch the kernel with 2-way / 2-wcr that will allow us to record calls ?

evilinside said:
will be possible to patch the kernel with 2-way / 2-wcr that will allow us to record calls ?
Click to expand...
Click to collapse
Idk, maybe

Hello. I finally decided to test CM7 in my ChaCha. I'm used too much to Sense style of work, but I'm trying to get used to this.
With stock rom, lgCamera didn't allow to record 800x480 videos, being 720 the most. Now with CM7 I can select that resolution and record videos in that resolution. I can even select 1280x720 but the screen get garbled. I think that is a limitation of the camera firmware, and being that it's the same camera modula the HTC Desire Z has, maybe it could be 'ported' to chacha.
I'd like to know if the kernel the latest CM7 port has /proc/mic_level enabled or included. I'd like to be able to set the mic recording level, and there is an app for that (Mic control for HD2), but it can't work because the absence of that /proc/mic_level stuff.
Thanks for your work.

[ROM][4.3][CM 10.2][31/07/13] elicik's Unofficial CM 10.2 builds

Hey, I realized that there aren't many CM 10.2 ROMs out there yet, so I made one of my own. This is my first published ROM, so expect a buggy, unsupported experience. I am using fat-tire's repos for the time being. For now, I recommend the GAPPS posted here. I will attempt to post a new build everyday, but no promises.
I don't do support, but I will try to answer questions, and I would appreciate bug reports. Note that CM 10.2 is very much in development right now.
Download/ Changelog
07/31/13 (mirror) - Just a new sync, there should be no real changes.
07/30/13 (mirror) - Initial build, uses fat-tire's repos for device and kernel
For detailed changes see the gerrit page.
Bugs
Focal doesn't work
Two Clock apps, one from Google, one from Android.

Sweet. Been waiting for this. Thanks

the only reason that there are two clocks is because there is one in the cm10.2 zip and the 4.3 gapps.

Can I get a mirror, please? The download always fails at 144MB for me.

Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?

MBQ_ said:
Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?
Click to expand...
Click to collapse
I would, but grouper's device and kernel don't as of yet have 10.2 branches. I use fattire's because I believe they are the best I can do until we have official.
fattire said:
* The /device tree is basically 10.1's device plus a bunch of cherry-picked stuff from AOSP 4.3, plus newer SELinux rules, plus my own minor changes.
* The /kernel tree is currently AOSP 4.3 stock with a cyanogenmod_android_defconfig added. None of the customization from 10.1 are here yet.
Click to expand...
Click to collapse

sgt. meow said:
Can I get a mirror, please? The download always fails at 144MB for me.
Click to expand...
Click to collapse
Done

[ROM][5.1.1][Experimental] CyanogenMod 12.1 | Linaro 4.9 | Code Review

Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.

Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?

Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.

starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)

3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!

Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.

@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.

Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.

I'll upload to Google drive starting tonight also. Driving home from work, will do another one.

CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.

New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.

CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.

I've been dirty flashing; should be good to go.

Update: yes, this ROM is very fast indeed! Thanks for sharing.

This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86

starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.

just wondering what recovery you are using and do partitions need changed from stock?

What models are supported?

@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds

Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.

Who can build CM13 for mate7?

Huawei has opened the sources (6.0 Marshmallow) for mate7 chinese version.Who can build a full-working (include fingerprint) rom for it?Hope to success.

Dont laugh at my poor English...

jsdfly said:
Huawei has opened the sources (6.0 Marshmallow) for mate7 chinese version.Who can build a full-working (include fingerprint) rom for it?Hope to success.
Click to expand...
Click to collapse
If this is true and they have released the necessary source files I would gladly pay someone to develop a CM ROM for the Mate 7.
Hopefully someone will pick this up soon and start working on it. If that happens I may even reconsider getting rid of the phone...

this good news. i would pay it too if someone could do it

Wow this is ingesting new even thigh mate 7 is on its end of its lifespan a possible cm release would prolong the lifespand a lot.
---------- Post added at 03:51 AM ---------- Previous post was at 03:50 AM ----------
Does any one know how man working hours or time it take to finish this for mate 7?
I would be willing to donate too.

Correct me if I am wrong but.. For security reasons It must be hard to get the fingerprint scanner to work on any non official rom or would this be included in the source code?

jsdfly said:
Huawei has opened the sources (6.0 Marshmallow) for mate7 chinese version.Who can build a full-working (include fingerprint) rom for it?Hope to success.
Click to expand...
Click to collapse
Where these sources can be found? Can you post or pm me the link?

I would gladly pay too for a well developed cm port

Tazmaniiac said:
I would gladly pay too for a well developed cm port
Click to expand...
Click to collapse
+1000

If true where is the source link, I call bull ****.
Sent from my VX3 using Tapatalk

Source Code 5.1.1
download-c.huawei.com/download/downloadCenter?downloadId=58644&version=196837&siteCode=cn&view=true

DVRS96 said:
download-c.huawei.com/download/downloadCenter?downloadId=58644&version=196837&siteCode=cn&view=true
Click to expand...
Click to collapse
Can you upload this to the cloud if you already downloaded it? (as Mega for example) It's very slow, about 6 hours here.. Thank you
EDIT: I did it, here's the link
https://mega.nz/#!bJdVUCSa!cRNz4yN3Ag_xuzSYSxS30ZAAAR8b2LZRDpmJY97D1Io
MD5: 6e63387cfdcb32fcdafb6570a134b7d2

blackinfinity said:
Correct me if I am wrong but.. For security reasons It must be hard to get the fingerprint scanner to work on any non official rom or would this be included in the source code?
Click to expand...
Click to collapse
I guess you are right here. I don't hink I have come across a single OEM (correct me if I'm wrong) that has released the necessary files for fingerprint readers. It wouldn't surprise me if it could potentially pose a massive security risk, especially with Android Pay on the rise.
snake65 said:
If true where is the source link, I call bull ****.
Agreed. Like I said, I heard this from someone who replied on a different thread, though I didn't ask him for links / proof. Could just be rumors.
But think about it this way, the Mate 7 is reaching the end if its lifespan anyway, fast approaching 2 years. Most Android OEMs stop supporting a device two years after release (once again, correct me if I'm wrong), so Huawei really won't feel any impact if it were to release source files for a nearly 'retired' device. But that having been said it probably is hearsay.
Sent from my VX3 using Tapatalk
Click to expand...
Click to collapse

gabry3795 said:
Where these sources can be found? Can you post or pm me the link?
Click to expand...
Click to collapse
Sources Download(6.0)
Offical link:http://download-c.huawei.com/download/downloadCenter?downloadId=76323&version=286198&siteCode=cn
Mega:https://mega.nz/#!y1cAQLpJ!HhM1bSkctN7xkaiwgIkOH9RgH-PCutIitNBFHK-uwcE
P.S. File name extension is wrong,is".tar"

I would do it but idk if i have the time. Its really easy to get into though. look up stuff on youtube and such. One of you guys could do it

I have compiled the kernel, added it to the boot.img and flashed it via fastboot, unfortunately I end in a bootloop.
How can I debug the kernel boot? (UART Jig maybe?)

ruffy91 said:
I have compiled the kernel, added it to the boot.img and flashed it via fastboot, unfortunately I end in a bootloop.
How can I debug the kernel boot? (UART Jig maybe?)
Click to expand...
Click to collapse
How did you do it? I get missing .h headers.. (I am building Lollipop kernel)

gabry3795 said:
How did you do it? I get missing .h headers..
Click to expand...
Click to collapse
Code:
diff --git a/drivers/hisi/modem_hi3630/drv/Makefile b/drivers/hisi/modem_hi3630/drv/Makefile
index 430a5b8..710cc36 100755
--- a/drivers/hisi/modem_hi3630/drv/Makefile
+++ b/drivers/hisi/modem_hi3630/drv/Makefile
@@ -75,7 +75,7 @@ ifeq ($(strip $(CFG_CONFIG_IPF)),YES)
obj-y += ipf/
endif
obj-y += lowpower_mntn/
-obj-$(CONFIG_BALONG_OAM_PS) += $(if $(findstring .o,$(shell ls $(CURDIR)/drivers/hisi/modem_hi3630/drv/balong_oam_ps)), balong_oam_ps/, )
+obj-$(CONFIG_BALONG_OAM_PS) += $(if $(findstring .o,$(shell ls $(BALONG_TOPDIR)/../../../drivers/hisi/modem_hi3630/drv/balong_oam_ps)), balong_oam_ps/, )
subdir-ccflags-y := -Werror
source has to be in "kernel" folder and you have to create "out" folder besides it.
I have commented out #include "hisi-partition.h" in every file where it appears. (Not very good solution I know, but made the kernel compilable and I was not sure if it is even needed. HiSilicon code gives thousands of warnings, no chance to read them all!).
I will search older sources for this missing file, or maybe it is generated by a script?
Edit: I have made a git repo with untouched Marshmallow source (B551 as in the link above): https://github.com/ruffy91/android_kernel_huawei_jazz

ruffy91 said:
Code:
diff --git a/drivers/hisi/modem_hi3630/drv/Makefile b/drivers/hisi/modem_hi3630/drv/Makefile
index 430a5b8..710cc36 100755
--- a/drivers/hisi/modem_hi3630/drv/Makefile
+++ b/drivers/hisi/modem_hi3630/drv/Makefile
@@ -75,7 +75,7 @@ ifeq ($(strip $(CFG_CONFIG_IPF)),YES)
obj-y += ipf/
endif
obj-y += lowpower_mntn/
-obj-$(CONFIG_BALONG_OAM_PS) += $(if $(findstring .o,$(shell ls $(CURDIR)/drivers/hisi/modem_hi3630/drv/balong_oam_ps)), balong_oam_ps/, )
+obj-$(CONFIG_BALONG_OAM_PS) += $(if $(findstring .o,$(shell ls $(BALONG_TOPDIR)/../../../drivers/hisi/modem_hi3630/drv/balong_oam_ps)), balong_oam_ps/, )
subdir-ccflags-y := -Werror
source has to be in "kernel" folder and you have to create "out" folder besides it.
I have commented out #include "hisi-partition.h" in every file where it appears. (Not very good solution I know, but made the kernel compilable and I was not sure if it is even needed. HiSilicon code gives thousands of warnings, no chance to read them all!).
I will search older sources for this missing file, or maybe it is generated by a script?
Edit: I have made a git repo with untouched Marshmallow source (B551 as in the link above): https://github.com/ruffy91/android_kernel_huawei_jazz
Click to expand...
Click to collapse
Thank you! Built successfully by commenting out hisi_partition.h include.. I think that is an automatically generated file, I looked for it in github but no repo seems to have it, I also looked in my old mate7 kernel repo (kitkat) and in new lollipop kernel but nothing. I think (and I hope) that it does not cause the bootloop issue :highfive:

so how the development continues? can't wait for testing!

[LineageOS port] libqdutils_intermediates/export_includes needed but can't make

As the title suggests, I am porting lineageOS and keep getting this error
/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
here is the full log https://paste.myself5.de/JfHg5EA2Je.sql
I have tried re syncing the repo and re downloading the source trees. nothing seems to be fixing this.. :/

Is this problem solved?

How did u solved this issue? @nzzane

Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing

nzzane said:
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
Click to expand...
Click to collapse
Sry i didnt get u. What do u mean two different repos?
Sent from my AO5510 using Tapatalk

Raja_12 said:
What do u mean two different repos?
Click to expand...
Click to collapse
If there is a repo named abc at github that supports i.e. FMRadio and another named xyz, that also supports FMRadio, it is neccessary that depending files are coming from the same repo. Actually the repo from LineageOS clashes with the one from SonyLOS and vice versa.
That's, what nzzane wanted to say IMHO...

Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)

nzzane said:
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
Click to expand...
Click to collapse
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.

Raja_12 said:
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Click to expand...
Click to collapse
It depends what each repo does, and how you want to build it (stock blobs or all device tree)

nzzane said:
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
Click to expand...
Click to collapse
all device tree

Raja_12 said:
all device tree
Click to expand...
Click to collapse
Then one of the repos must be conflicting somewhere :S

nzzane said:
Then one of the repos must be conflicting somewhere :S
Click to expand...
Click to collapse
Yea sometimes I can't make clean or clobber. With one repo it works with other it didn't. So I have to maintain only one repo at a time.

I ran into another issue. Can u help
target arm C: audio.primary.msm8916_32 <= hardware/qcom/audio/hal/voice.c
In file included from hardware/qcom/audio/hal/voice.c:32:
hardware/qcom/audio/hal/voice_extn/voice_extn.h:194:71: error: unused parameter 'adev' [-Werror,-Wunused-parameter]
static int voice_extn_compress_voip_set_mic_mute(struct audio_device *adev, bool state __unused)
Sent from my AO5510 using Tapatalk