yashsingh1/xdaforums huggingface dataset:
[HTC Salsa] Darkorn:
Front camera -> doesn't work

Video recording -> Lg camera (meh, but it works)

Wifi thethering -> Doesn't work from settings but should work if you download something from the market

Bluetooth thethering -> not tested

Usb thethering -> Everything crashes

FM Radio -> should works

Youtube -> not tested
[HTC Salsa] Darkorn:
Compiling 4.2.2 from https://github.com/Luzifer1984/android_device_htc_chacha .
[HTC Salsa] Darkorn:
I managed to get a working rom but I accidentaly updated my source so now it's a mess. Anyway I put the device tree on my github so everyone can start easily.

https://github.com/Zap123

I will rebuild a working rom, meanwhile when I tried:

Video playback doesn't work

Camera crashes after a while (but maybe it was my messed up source)

Bluetooth still works

Wifi works only with old driver

I've started modifying this one because it explain you what to do https://github.com/Luzifer1984/android_device_htc_chacha but I forked something from here too https://github.com/JDevs/android_device_htc_msm7x27-common .
[HTC Salsa] Darkorn:
Does the phone reboot when you switch bluetooth on-off multiple times or is just another bug of cm10.1?
[HTC Salsa] BigBearEvo:
i'm gonna be a bugger and ask can u host me a full rom....with my circumstances, resources are limited right now
[HTC Salsa] Darkorn:
ok no problem, but it's full of bugs and I was waiting to publish it because it's pretty unusable now...

Keyboard crash if you press more than a key simultaneously (like swype).

phone reboot if you switch bluetooth on/of two times (every rom, there must be a problem in the patch I found).

Video playback it's broken (probably work with mxplayer but's only a workaround)

Camera crash after few seconds

After you flash gapps keyboard stop working (I don't know why).

+ bugs from CM10 (front camera, thethering...)

https://dl.dropboxusercontent.com/u...el/cm-10.1-20130703-EXPERIMENTAL-icong-A1.zip
[HTC Salsa] vigoos:
I'm getting compile errors while compiling Owl kernel from - https://github.com/Zap123/OWL-Predator-KERNEL
[HTC Salsa] Darkorn:
Which errors and which compiler's version?
[HTC Salsa] vigoos:
The

make -j10 ARCH=arm CROSS_COMPILE=arm-eabi-

is where I'm facing problems. I'm using Linaro 4.8 ATM It compiles with a few warnings

fs/cifs/cifssmb.c: In function 'CIFSSMBSetFileInfo':
fs/cifs/cifssmb.c:4988:8: warning: array subscript is above array bounds [-Warray-bounds]
memcpy(data_offset, data, sizeof(FILE_BASIC_INFO));
^
CC fs/ext2/super.o
fs/cifs/cifssmb.c: In function 'CIFSSMBUnixSetFileInfo':
fs/cifs/cifssmb.c:5278:25: warning: array subscript is above array bounds [-Warray-bounds]
cifs_fill_unix_set_info(data_offset, args);

CC arch/arm/mach-msm/msm_vibrator.o
make[2]: *** No rule to make target `drivers/btport/btport.o', needed by `drivers/btport/built-in.o'. Stop.
make[1]: *** [drivers/btport] Error 2
make[1]: *** Waiting for unfinished jobs....
CC mm/mmap.o

arch/arm/mach-msm/acpuclock-arm11.c: In function 'acpuclk_init':
arch/arm/mach-msm/acpuclock-arm11.c:607:45: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
if (machine_arch_type != MACH_TYPE_MARVEL && (SOCINFO_VERSION_MAJOR(socinfo_get_version()) > 1)

No zimage is made however. The rest of the compile goes well. Thats my cause of concern. I'll try with NDK today.
[HTC Salsa] Darkorn:
I used the ndk, compile with gcc 4.4.3 otherwise it will translate this instruction in a non-compatible arm instruction and it won't boot.
[HTC Salsa] benjamingwynn:
Looks like your bt's screwed.

protip: make -j0 bacon

You can't ever go wrong with bacon.
[HTC Salsa] theschneidi:
I used kernel from benjamingwynn/android_kernel_htc_msm7227

my btport folder is nearly empty. Some sources for this folder I found here, I try them now for my kernel config

https://github.com/Decad3nce/htc-kernel-heroc-BFS/tree/master/drivers/btport

Edit: hm maybe this is better btport, because some variables from uart were renamed in 2.6.x kernel

https://github.com/2fast4u88/Htc-Merge-FastKernel/tree/master/drivers/btport

Edit: I also added dummy_keypad.c to drivers/input/misc/

Edit: I got now some funny compile error

MODPOST vmlinux.o
WARNING: vmlinux.o(.data+0x10304): Section mismatch in reference from the variable msm_hw3d_driver to the function .init.text:hw3d_probe()
The variable msm_hw3d_driver references
the function __init hw3d_probe()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

To build the kernel despite the mismatches, build with:
'make CONFIG_NO_ERROR_ON_MISMATCH=y'
(NOTE: This is not recommended)
make[3]: *** [vmlinux.o] Error 1
make[2]: *** [vmlinux.o] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/.../CYANOGENMOD/kernel/htc/msm7227'
make: *** [TARGET_KERNEL_BINARIES] Error 2

Shall I ignore this error or what could the cause for this?
[HTC Salsa] vigoos:
Had you enabled msm 3d driver? That seems to be the problem. This is an error and not a warning. I recommend you compile OWL kernel from darkorns github and see what the results are.
[HTC Salsa] theschneidi:
Built successfully cm10 Android 4.1.2 with bluetooth support. GPS.icong.so still keeps the phone in a bootloop and renamed to a .bak

Link oft ROM and config I send soon for modders and interested users.
[HTC Salsa] vigoos:
Does GPS work then? What about camcorder and which kernel?
[HTC Salsa] vigoos:
Darkorn must know..... Anyways there seems to be some problem in the GPS library file which occupied too much ram and led to all other processes being killed. Because of this the system is going into boot loop. Thanks Schneider for documenting this logcat.
[HTC Salsa] Darkorn:
I didn't change anything because I was busy,

theschneidi what about video playback and keyboard? Does the keyboard crashes if you act like "swype" (pressing more than a key)?
[HTC Salsa] theschneidi:
Test it on your own risk. :) (GPS, front cam & camcorder not working :crying: ) (main camera, network, wifi, bluetooth works :good: )

Keyboard doesn't crash on my phone. Video playback works.

Some lags are annoying. But with governor Smoothass (instead of SmartassH3) there are fewer lags.

Battery consumption I have to monitor.

Link for the current build: https://dl.dropboxusercontent.com/u/8541272/CM10/cm-10-20130315-UNOFFICIAL-icong270713.zip

Config is in attachments.

View attachment cyanogen_msm7227_defconfig.txt

For those who want a CM10.1 build I still need some time.
[HTC Salsa] Darkorn:
How you solved the video playback problem?

Try enabling and disabling bluetooth two times, I think there's something wrong because it makes the phone reboot on CM10.
[HTC Salsa] theschneidi:
Some videos run slower than on stock now. Can someone check the config?

For some people who want to know, the YouTube app works here.

Can you make a logcat from BT crash?
[HTC Salsa] theschneidi:
Do some people have lags in CM10? I have many of them. I don't know if they stand in connection with int2ext4.
[HTC Salsa] vigoos:
Highly possible.... Because on sense 5 I had some as well
[HTC Salsa] godsgreat_87:
Guys!! you would want to test this. Working CM10.1 for htc salsa. ported by meswar.

cm10.1 experimental port

http://www.mediafire.com/download/6m...ntal-icong.zip.

Edit: Link broken.. i dont know where to upload and how. If someone can contack meswar. It is working fine. Love the lock screen features, few clean up needed.
[HTC Salsa] vigoos:
I have it... He had sent it to me also. I'll test it out.
[HTC Salsa] theschneidi:
Copy&Paste of URLs is not so easy (hint: use "right-click" and "copy link") :). Could someone post it here again, please?
[HTC Salsa] vigoos:
Check your PM Schneider
[HTC Salsa] taimur272:
Please post some screenshots so we can see what's new.........
[HTC Salsa] godsgreat_87:
The music player lags when the screen is off. Even when we get a call and the screen was off, It lags and takes time to show up. can u plz check this and correct it..I feel its something to do with setCPU for screen off. But i am not sure so didnt want to play with it. thought of asking the experts.

Everything else looks cool apart from few simple bugs which i am pretty much fine with.
[HTC Salsa] vigoos:
Take a backup and try playing around with ROM toolbox pro..... Might be something in some embedded values.....
[HTC Salsa] theschneidi:
CM10.1 by meswar:

+ looks nice with the Trebuchet 1.0 launcher

+ camcorder records videos (but no playback :( )

+ Nice Camera/Camcoder app

+ Bluetooth works, but with errors

- bluetooth reboots the phone, when switching on->off

- no videos can be played (Error message)

not tested: WiFi, GPS
[HTC Salsa] Darkorn:
Does GApps works?
[HTC Salsa] theschneidi:
I think but I have not tested yet.
[HTC Salsa] godsgreat_87:
Yes it works. I m using this rom from past 1 month. Need to flash jb gapps
[HTC Salsa] vigoos:
Anything new? And do we need a Linux 3.0.x kernel? I am doing some stuff for that.... If anyone has made any new builds post them here.
[HTC Salsa] theschneidi:
Nothing new in development. But I am interested in Kernel 3.x development. Maybe some useful things from Wildfire S could help to build our own kernel.

But I think that the first goal should be that nearly all things need to work on 2.6.x kernel.
[HTC Salsa] vigoos:
I got a Linux 3.0.8 kernel ready..... I'll be uploading the source code once I get some time......
[HTC Salsa] theschneidi:
Is someone interested in CM 10.1.3 or CM 10.2 development?
[HTC Salsa] vigoos:
CM10.2, I'll write the git for that. After that FireFox OS.

No one is developing this device it seems, only me and Schneider on it. This is boring now, only 2 people? Come on man, bb is busy, where are others?!
[HTC Salsa] vigoos:
But instead of spending time on 10.2 I think we can work on 10.1 and then later when android kitkat is released we can do for that. Personally I don't find any sense in developing 10.2 and stabilizing it because in no time it will become obsolete.

In the meantime let us do FireFox OS. It looks promising to me.
[HTC Salsa] theschneidi:
Firefox OS works on a device which has nearly same specs ( CPU 1GHz, RAM 512MB, Data 160MB ) like Salsa.

Ok I will set up a new build environment for 10.1 on my other PC.
[HTC Salsa] vigoos:
FireFox worked on HTC Explorer. So I see no way it won't work on salsa.

My CM10.1 git is going to be repaired in some time. I forgot to remove some files from it. My git has got experimental front camera support. So it might just luckily work for us.
[HTC Salsa] crest_delta:
Firefox OS seems a good idea . Frankly I am not too keen on the Android KitKat .I feel we have more issues to address like the Camera GPS and Battery issues , not working on older ROMs ( JB ) as i feel its half-baked.I remember using windows phone updated to WM 6.1 on my older O2 device and it was perfect

I totally agree that only demanding things wont work anymore given the limited ppl developing and working on this device and hence I urge everyone using the Salsa should volunter in what ever ways they can .I am not a engineer , but i can always help to test newly developed ROMS

Cheers to all !!
[HTC Salsa] vigoos:
I agree we need to stabilize jellybean ROM. And you have a valid point, we need to get features working. The problem is with not exactly half baked but with the fact that over experimenting with a build can lead to a mess. Come on, no one can fix front camera, WiFi tether and all other dysfunctional features in one go.

People only coming up with demands is totally unfair on their side because we have our own priorities and we are voluntarily developing here.

It does not need one to be an engineer to compile cm from source. With the resources we have like top class guides even a first grade kid can build cm, I'm not kidding, if you got let's say 2 hours a day and a good 2mbps unlimited internet and a PC with decent or good specs you can easily compile. I got problems with my ISP and I'm upgrading soon to simply go ahead and transform this device. After which I will bid it a well deserved bye bye. Don't worry I'll still develop after that, I'll need testers and that's it.
[HTC Salsa] vigoos:
Better LatinIME.apk

You guys can use this in your build, this keyboard is smaller in size -

http://xdaforums.com/showpost.php?p=45985076&postcount=5
[HTC Salsa] benjamingwynn:
Right, okay, I have everything working the way I want it to in terms of repos. I've been fighting with them because of Cyanogenmod's changes to the upstream (AOSP) android_prebuilt_* repos.

I'm going to look for the correct hals for your compass model now. I still need that touch board model BigBearEvo!

As for the kernel it looks like I can directly use ASN's common msm7k kernel without any tweaks besides changing the name of the ramdisk init script so your bootloader likes it and boots past the HTC screen, it might be automatically underclocked to 600mhz though, but I don't think that'd be a problem really since there are settings to change this, I could also just write an init.d script later to automatically boost speeds to 800mhz on first boost, but that's not really a priority.

Source code is here (https://github.com/benjamingwynn/android_device_htc_icon_g) by the way. If you want to send a pull request or fork the code, feel free to :)
[HTC Salsa] BigBearEvo:
help me find it lol
[HTC Salsa] benjamingwynn:
Look for something called defconfig I think
[HTC Salsa] BigBearEvo:
not found anything by that...

and im unable to access anything Linux so...
[HTC Salsa] benjamingwynn:
Hm okay, I guess I'll just assume that it'll work with the Wildfire S touch driver lol.

Things seem to be building well, what recovery do you guys use at the moment?
[HTC Salsa] BigBearEvo:
ClockWorkMod 5.0.2.6 is the only working one that's fully functional.

I've tried various others with no success, the only other that worked is here >http://xdaforums.com/showthread.php?t=1791707
[HTC Salsa] benjamingwynn:
I can build CWM 6 for you :)
[HTC Salsa] BigBearEvo:
go for it :highfive:
[HTC Salsa] benjamingwynn:
Untested: http://goo.im/devs/benjamingwynn/icon_g/ClockworkMod6
[HTC Salsa] BigBearEvo:
4.2mb img file

1.6mb zip file lol hmmm is this correct
[HTC Salsa] benjamingwynn:
The ZIP file is compressed where the img file isn't. Taking a quick look at the ZIP file tells me that it basically overwrites your current recovery image by image/script by script. Like a big updater.
[HTC Salsa] BigBearEvo:
okies...here goes

YOU RULE!

cwm 6.0.1.3 is working...testing functions out now
[HTC Salsa] benjamingwynn:
If it works I'll make a thread for it.
[HTC Salsa] BigBearEvo:
hmmm i did the flash....it loaded fine...i rebooted recovery..back to 5.0.2.6 again...running it from bootloader now...see if i can get it perm
[HTC Salsa] benjamingwynn:
That's really good!

1) I can show off a fancy thread

2) The recovery uses the common MSM7k kernel not a sense one, meaning it'll work in CM.
[HTC Salsa] benjamingwynn:
Weird, try flashing using the image.

EDIT: It's a fakeflash ZIP, oops. Use the image.
[HTC Salsa] BigBearEvo:
just did...said it flashed...but nothings there

wait...having a play now

........................................................................................................

C:\android-sdk\platform-tools>fastboot flash recovery recovery.img

sending 'recovery' (4234 KB)... OKAY

writing 'recovery'... OKAY

now fails to boot into recovery.
[HTC Salsa] benjamingwynn:
fastboot flash recovery NAME_OF_IMAGE.img

or if that doesn't work

adb shell write_raw_image recovery PATH/TO/IMAGE/NAME_OF_IMAGE.img
[HTC Salsa] benjamingwynn:
adb shell dmesg > output.txt
[HTC Salsa] BigBearEvo:
ok...non work...my adb is limited...i cant even get the damn this to logcat it until the boot animation starts
[HTC Salsa] benjamingwynn:
Having compile problems, but that's okay since I can fix these pretty easily with a few modifications.
[HTC Salsa] razer1224:
Compile errors makes the Rom not to boot..always try to give the best solution and not the worst solution
[HTC Salsa] benjamingwynn:
Eh that doesn't make sense. Can you rephrase that?
[HTC Salsa] benjamingwynn:
Check the Op if your up for testing.
[HTC Salsa] razer1224:
I'm crying because I bricked my salsa for flashing a cm7 test base

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

Lol,give the appropriate .ko and .so <

This is what I meant
[HTC Salsa] benjamingwynn:
.so are libs that are compiled. If they error during the compile then its most likely a problem with the device tree that I use, so I change it.

.ko are kernel modules and are automatically compiled when the kernel is.
[HTC Salsa] BigBearEvo:
Will test shortly and post results up. Fingers crossed.

BigBear is using Xparent Tapatalk Purple
[HTC Salsa] BigBearEvo:
assert failed: getprop("ro.product.device") =="icon_g" I I getprop("ro.build.product") == "icon_g"

(status 7)
[HTC Salsa] razer1224:
I think the device tree isn't correct
[HTC Salsa] BigBearEvo:
will see what ben has to say.....won't be able to flash anything now till Sunday evening
[HTC Salsa] benjamingwynn:
Use winrar or something to remove that line from META-INF/com/Google/android/update-script
[HTC Salsa] BigBearEvo:
Lol can't in out for weekend now back on Sunday

BigBear is using Xparent Tapatalk Purple
[HTC Salsa] razer1224:
Why don't u guys jus make the cm9
[HTC Salsa] benjamingwynn:
Because it'll have the same problem, and the ICS branch was abandoned by CyanogenMod, so no new fixes/features will added to CM9.
[HTC Salsa] razer1224:
I get it now
[HTC Salsa] Go.Bin:
Still on going or what? wish i could help but in fact not :D
[HTC Salsa] benjamingwynn:
A build is up but nobody has told me if it works or not.
[HTC Salsa] BigBearEvo:
that's because im only just coming online via the pc lol, so....where were we fri? what did you want me to do?
[HTC Salsa] benjamingwynn:
I've built the ROM, go test it :D
[HTC Salsa] razer1224:
BB I guess we get the postive results

Team Fire
[HTC Salsa] BigBearEvo:
did you do the thingy with the thingy from a previous post :laugh: ie edit the line you said...
[HTC Salsa] benjamingwynn:
Nope, you'll have to do that yourself or use a different recovery.
[HTC Salsa] razer1224:
Recovery?

Team Fire
[HTC Salsa] BigBearEvo:
Edited Line as stated

Wipes.....................Complete

Installing.................Complete

Rebooting...............white HTC screen lol

Unable to get logcat or demsg files either, won't record them
[HTC Salsa] razer1224:
Guys why don't you try the vendor tree of wfs..

Team Fire
[HTC Salsa] benjamingwynn:
Its nothing to do with the vendor, and we are using it but with references to the icon_g instead of marvel.
[HTC Salsa] razer1224:
Sorry,I thought the files might differ

Team Fire
[HTC Salsa] puppet13th:
kernel defconfig from htc kernel source :

icong-2.6.35-gb-crc-ea564c7.tar.gz : arch/arm/configs/msm7227_defconfig

marvel-gb-mr-2.6.35-a66971c.tar.gz : arch/arm/configs/msm7227_defconfig

it's look like icong and marvel have same kernel defconfig

puppet13th@nall-home:~/android/kernel/htc> diff msm7227_defconfig-icong.txt msm7227_defconfig-marvel.txt
puppet13th@nall-home:~/android/kernel/htc>
[HTC Salsa] benjamingwynn:
Hm, I am using an MSM7k common kernel repo, so stuff should work fine... ramdisk maybe? Can somebody rip open the HTC Sense boot.img and do

ls[CODE] inside the extracted RAMDISK, you can do this with dsixda's ROM kitchen.
[HTC Salsa] BigBearEvo:
swapped boot.img, installed again, stuck at white htc again.

will look into the kernel now...
[HTC Salsa] razer1224:
Bb u updated the kitchen...btw I'm back BB
[HTC Salsa] BigBearEvo:
no its currently doing it....along with all the other 599 ubuntu updates lol...gonna take awhile lol

will sort it asap unless you can get the required info
[HTC Salsa] benjamingwynn:
Oh okay, thanks. This is really useful. It seems the name of your device is icong in some places, but icon_g in others. I'll research this more.
[HTC Salsa] razer1224:
The in the ramdisk every lines are named as icong.......as I checked maybe

Icong is the other name for the salsa I was code named as u guys know

My one x is named as endevoru

Real Steel
[HTC Salsa] benjamingwynn:
My Wildfire S is named as marvel, but the Salsa seems to be called icon_g by some parts (such as build.prop) and icong by others (ramdisk)
[HTC Salsa] razer1224:
Hey ramdisk is more important than build.prop

Real Steel
[HTC Salsa] BigBearEvo:
could this be why things just are not working for us then lol
[HTC Salsa] benjamingwynn:
probably lol
[HTC Salsa] BigBearEvo:
that's a quality signature kid!
[HTC Salsa] razer1224:
I AM KID,okay i am a kid thanks for that

Real Steel

---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------

Specifying this the ramdisk is more important

Real Steel
[HTC Salsa] benjamingwynn:
le bump :)

Sorry guys I've been busy with school work and my own device is throwing fits and not booting for an unknown retarded reason.

As soon as I get the marvel working again I'll get CM working here.

Also, if stuff works here I'll port Project Llama to this phone.
[HTC Salsa] BigBearEvo:
Personal life is priority kiddo :D

BigBear is using Xparent Tapatalk Purple
[HTC Salsa] Darkorn:
Wouldn't be easier to port CM 7.0 first? If we try with rom from other devices it won't work because it's like playing domino, but if we had a general build of CM we could add stock kernel and the other files and it should boot fine. I really appreciate benjamingwynn's work with CM10, but I think we should try with CM 7.0 first. For example "extract-files.sh", if it works with CM 7 we know that it's right. Port CM10 without porting CM7 it's like build a space shuttle without trying to build an airplane lol. CM 7.0 is based on android 2.3.3 so every proprietary library should work fine as stated here general-cyanogenmod-porting-discussion/.

"Chances are, if you just make a generic build of CM and bundle it with the kernel from a working rom/system, it will boot into CM, hopefully to the standby screen."

Correct me if I'm wrong.

I would really try do it by myself and compile CM 7.0, but I only have an old computer, you know...you really do not want to compile something like android with a pentium 4 from 2006 lol.
[HTC Salsa] BigBearEvo:
Lol point Is, the cm10 build can be done to work for us and we go backwards. I'd much prefer a working ics than a working cm7. I have spent weeks porting cm7 across with failures all down to the screen. Now there's plenty of working cm10 out there, and Ben is really good at porting to use.

You will notice as well the decline in cm7 roms as everything is moving ics/cm10. I run my xperia x8 on gingerdx which is ics 4/cm10 and I will never go back to cm7. Its just as lightweight and fast, but more useable in today's needs.

So I do know what your saying, but we have tried from the bottom.....now were trying from the top and going downwards.

BigBear is using Xparent Tapatalk Purple
[HTC Salsa] Darkorn:
I know BigBearEvo, I don't want cm7 because I like it lol. I'm just saying cm10 could add more problem because it's a different android version and may be easier if we have a working cm7 to study first. But I'm not the developer here, I'm just saying. You are a hero for your patience, but if you have a cm7 generic build you could do the same magic you used to make it boot and there won't be any files that are specifically for another device, it would be easier to debug and I think it would be easier to port cm10 for benjamingwynn too.
[HTC Salsa] BigBearEvo:
Anything we get is based on a port really, Ben has managed to get this lot running, mainly due to his other cm10 rom on his wildfire s, in theory what works for our sister phone will work for us. But we are attacking this rom set from all angles lol and will continue to till we suceed! :D

BigBear is using Xparent Tapatalk Purple