yashsingh1/xdaforums huggingface dataset:
[HTC Salsa] godsgreat_87:
So can we expect to get it soon ? As it already has data2sd working n WiFi working...
[HTC Salsa] karanparikh:
Ya expectations are something, searching the forum for the newly created ROM thread is what is required. :laugh:

Great going guys, really appreciate your hard work. Thanks a lot to the trio :p
[HTC Salsa] BigBearEvo:
there is no data2sd but it is similar!.....and please don't ask when...its not fair!

please see the rom thread for CM10
[HTC Salsa] godsgreat_87:
Lol! I did not see the Rom thread...my bad!

Thanks to all 3 of you!
[HTC Salsa] theschneidi:
I've found out that back camera is a Samsung s5k4e1gx and front camera a Micron mt9v113, maybe it helps for CM7 or CM10.
[HTC Salsa] Darkorn:
Nice, but the problem is in your libcamera.so.

https://groups.google.com/forum/?fromgroups=#!msg/android-platform/ktE524v8NZ0/WdhEno7xlBoJ

The error is clear, it's saying that android can't load camera because another library is using that particular memory address. We could change libcamera.so address and rebuild the rom, but which address is the good one?

Can't we ask for help? I think it's a pretty common error and if we fix this rear camera will start to work.
[HTC Salsa] meswar:
But rear camera works fine for me. Camcorder buggy find new app to work that too. Using jelly king ROM ported from wfs. And int2ex+ script with ex3 fs.
[HTC Salsa] Darkorn:
Rear camera on cm10?

We've the same problem as here http://xdaforums.com/showthread.php?t=1764584 , I don't know how they solved.
[HTC Salsa] meswar:
Yes jelly king is based on cm10.
[HTC Salsa] BigBearEvo:
Its based and a port, but jot a direct build meant for us. True cm10 which we now have needs fixing, the port you have isn't built for us and may cause problems. Same as cm7 its been built for us from scratch as all cm Roms shoud be.

BigBearEvo is using Xparent Tapatalk ICS on CM10
[HTC Salsa] meswar:
Try to fix it.
[HTC Salsa] BigBearEvo:
What did I say. Do not demand anything.......its very unfair on the deveelopers. If your using a port then fine. Were using a pure salsa made non ported version which cannot be just fixed.

BigBearEvo is using Xparent Tapatalk ICS on CM10
[HTC Salsa] theschneidi:
I need to recompile my whole ROM, because I changed from openJDK to SunJDK, which is more supported from Google when building Android. I only have to fix some compiler errors in network driver and other stuff. I post them maybe in this thread.

Could somebody list in a short overview, which modifications were done after I posted the whitescreen CM10-20130224 ROM? It would be helpful, when I apply some of them to the new ROM.
[HTC Salsa] BigBearEvo:
darkorn knows what he did..i added and removed some stuff to thin it out...will do the same again if you recompile it to match as i know what i did lol
[HTC Salsa] Darkorn:
1. Changed Gallery2.apk because it won't start

2. Compiled Benjamin's kernel with wifidriver from htc chacha I posted before (for wifi and graphics).
[HTC Salsa] vigoos:
Did anyone try to use chacha driver for Bluetooth.

Sent from my HTC Salsa C510e using Xparent Cyan Tapatalk 2
[HTC Salsa] theschneidi:
Tried to rebuild, but screen got black after HTC screen so it rebooted. Does somebody know what a reason could be? I tried to flash only the boot sector on top of the existing working CM10, it booted. No Wifi, Bluetooth, Camera. :(

I dont't know which bionic and kernel I should use. I use now the bionic from Cyanogenmod Jellybean with the mentioned patches. Then the Kernel from adumont/htc-kernel-msm7227.

This is my local manifest.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="benjamingwynn/android_device_htc_marvel" path="device/htc/marvel" />
<project name="benjamingwynn/android_device_htc_icong" path="device/htc/icong" />
<!--<project name="benjamingwynn/android_kernel_htc_msm7227" path="kernel/htc/msm7227" />-->

<project name="adumont/htc-kernel-msm7227" path="kernel/htc/msm7227" />

<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="Ganster41/android_frameworks_av" path="frameworks/av" />
<!-- Fix bionic -->
<!--<remove-project name="CyanogenMod/android_bionic" />-->
<!--<project name="ProjectLlama/android_bionic" path="bionic" />-->
<!--<project name="benjamingwynn/android_bionic" path="bionic" />-->

<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<!--<project name="ProjectLlama/android_hardware_qcom_display" path="hardware/qcom/display" />-->
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" />

<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="ProjectLlama/android_hardware_msm7k" path="hardware/msm7k" />
</manifest>
[HTC Salsa] Darkorn:
https://github.com/benjamingwynn/android_kernel_htc_msm7227

I used this one, no wifi (without switching drivers) but graphics works
[HTC Salsa] theschneidi:
Damn, rebuilt the ROM with ODEX-Option, but it got too big :(

Install system fs image: /home/schneider/CYANOGENMOD/out/target/product/icong/system.img
/home/schneider/CYANOGENMOD/out/target/product/icong/system.img+ maxsize=278175744 blocksize=270336 total=304812288 reserve=2973696
error: /home/schneider/CYANOGENMOD/out/target/product/icong/system.img+ too large (304812288 > [281149440 - 2973696])
make: *** [/home/schneider/CYANOGENMOD/out/target/product/icong/system.img] Error 1
make: *** Deleting file `/home/schneider/CYANOGENMOD/out/target/product/icong/system.img'
[HTC Salsa] Darkorn:
Yep, you must remove something from the rom to odex it. I odexed our cm10 rom with Titanium backup and now I have 70mb of free space, but I removed a lot of stuff in the rom.
[HTC Salsa] BigBearEvo:
I thought I'd add this in here as its partly development and partly idea etc.

I came across the idea of recording my uptimes. Mainly to see when my phone randomly reboots while on cm roms. Currently I've managed 23.27 hrs without a reboot.

Things causing it to reboot, sluggish response and low charge.

Other things......... sometimes I cannot get my notifications. Some msgs fail to show up. Calls missed or no connection. Have tried this on purpose to test and i got this mumber is not avaliable lol.

Just some things we need to look into at some point. But I would like all users on cm roms to get an uptime widget or app to live record times for developmeent purposes. Thanks

BigBearEvo is using Xparent Tapatalk ICS on CM10
[HTC Salsa] Darkorn:
theschneidi did you try the patch I sent you? Could you publish new libcamera* libraries so I can play with camera?
[HTC Salsa] theschneidi:
New build ;) Kernel boots, CM10 bootscreen appears, then the homescreen appears, but crashes. I found out that gps keeps crashing, so I need to rename /system/lib/hw/gps.icong.so to a .bak file, if you need it.

Gallery, Wifi, HSDPA works ;)

Camera (Unlockscreen -> slide left) said No connection to Camera :'( I think Bluetooth still doesn't work.

See my logcat file: https://dl.dropbox.com/u/8541272/CM10/logcat6.txt

ROM-file: https://dl.dropbox.com/u/8541272/CM10/cm-10-20130315-UNOFFICIAL-icong_theschneidi.zip

Use it on your own risk.
[HTC Salsa] BigBearEvo:
good work mate...we need to try and give users something to keep them going...ie a camera at least lol did u use any of the stuff darkorn gave u?
[HTC Salsa] theschneidi:
I/CameraService( 104): CameraService started (pid=104)

E/HAL ( 104): load: module=/system/lib/hw/camera.msm7x27.so

E/HAL ( 104): Cannot load library: link_image[1916]: 104 could not load needed library 'libcamera.so' for 'camera.msm7x27.so' (reloc_library[1331]: 104 cannot locate '_debug_pthread_create'...

E/HAL ( 104): )

E/CameraService( 104): Could not load camera HAL module

I sent PM to Darkorn, hope he answers. ;)
[HTC Salsa] theschneidi:
White smoke! I got camera working, but with some display errors (I need a logcat). Now I can take only photos yeah! ;)

No Bluetooth, no GPS (prevents device from booting system/lib/hw/gps.icong.so renamed to .bak).

Upload of ROM soon.

EDIT:

here it is!

http://dl.dropbox.com/u/8541272/CM10/cm-10-20130315-UNOFFICIAL-PATCHED-icong_theschneidi.zip
[HTC Salsa] Darkorn:
Not tried to reflash the rom, just switched the libraries. Could someone confirm these:

Random glitch using camera

video recording don't works
[HTC Salsa] BigBearEvo:
Camcorder not working, but camera works fine if u use lgcamera from google play
[HTC Salsa] BigBearEvo:
I would like to know if u could disable the auto CPU thingy lol

Reason being, I can control the battery level and reduce the drain if I could get access to it. Aimed at theschneidi lol
[HTC Salsa] BigBearEvo:
when activating voice functions ie voice search/cmds it will not pick up the mic....any ideas?
[HTC Salsa] rohanpatkar:
dEvil Battery !!

Thats quite urgently required.Every night i plug in my phone and charge it for 5-6 hrs to finally find it fully charged early in the morn.

Last night i didn't charge it and later found out that the battery drained from 56% to 4% within 8-9 hrs of standby mode !!

Its like..while being on cm7/10 i care a lot about battery issues..and thats a headache..gb was good....returning to old good gb roms until this is fixed alongwith other issues.
[HTC Salsa] BigBearEvo:
If you have battery issues then something your using is draining it. I get 48hts on a full charge if I don't hammer it playing games etc. My uptime is inclusive of calls aand texts. I proved this not long ago Rom a weekend away. Managed to get from Fri evening to Sunday afternoon before charging.
[HTC Salsa] uberano26:
Damn how do you manage that? I hardly make it past 20Hrs before i have to charge again and that too on standby -_-

And acc to the battery stats the biggest eater is the display which is a litte odd considering the brightness is set quite low.

Secondly, is there no way to make tethering work on CM7??
[HTC Salsa] theschneidi:
Try Wakelock Detector from XDA or market. There you can find out apps which use much battery.

Other issues with Bluetooth, GPS, front cam, Camcorder will need a lot of time to fix. Be patient and if you want to help collect logcat messages or search in the net then post your results.
[HTC Salsa] vigoos:
The main culprits are display and network. So we need something to reduce the damage caused.

Sent from my GT-P3100 using Xparent Cyan Tapatalk 2
[HTC Salsa] vigoos:
Front cam

Holy moly!!!!!

I got you guys a front cam driver!!! You people can try it in a test build. It is a cpp file.

Directed to- theschneidi, darkorn, benjamingwynn and (Sir) BBE
[HTC Salsa] vigoos:
Also I've investigated battery drain in other devices with CM10 and AOSP. Display consumption is 67% . So I say nothing can be done except reducing brightness. Also I'm unable to find source of BT drivers in benjamingwynns KCS
[HTC Salsa] Darkorn:
Did anybody tried Android 4.2.2? Because I did, and it boots fine but probably there's some problems with the framework since at the lockscreen I get a lot of "Phone Crashed" "SystemUI crashed". I know benjamingwynn source it's not for this version of android, but whatever, I did just for fun. Maybe I shouldn't have mixed Cyanogenmod and AOKP sources uhm.
[HTC Salsa] vigoos:
I have observed nothing much different between 4.1 and 4.2, I suppose editing kcs will give us a tremendous scope. Please have a look @ the driver source I posted. If you also want .h then I'll pm you.
[HTC Salsa] vigoos:
I've edited 4.1 kcs so that it can work on 4.2 . Waiting from Ben for permissions to host.
[HTC Salsa] vigoos:
Okay so I got sources for CM 10.1. Firstly I thank darkorn for giving me idea (CM 10.1 kanging target name from marvel) . I got bens source code for cm10.1 on wildfire s. Then I set all target names to icong. Now you will ask me what for front camera? I have added front camera c++ file and .h file. Also I have edited 1 more file in camera library. So I hope I can get front camera working. I asked permissions from Ben if I could use my git to host the source code but I didn't get any reply. So I'm kind of stuck. Also my internet is an absolute sloth. So I can't do a source compile. If Ben gives permissions then I can host sources.
[HTC Salsa] BigBearEvo:
U can host a source code as long as its open. Go ahead and do it, just drop him a pm saying u done it. Remember if u host it, link it here for others to use.

In all fairness, we need gps/Bluetooth and a fully bug free rear camera more than the front. Consider these fixes rather than a fix for something that's minor.
[HTC Salsa] vigoos:
Thanks bb. Tomorrow morning then.
[HTC Salsa] theschneidi:
Sounds nice, so I can switch my codebase to cm10.1 ;). Hope we can get those camera glitches fixed and of course Bluetooth and GPS.
[HTC Salsa] vigoos:
OpenBase and CM10.1 are absolutely different. Open base is my own sense base 2.3.3 and cm10.1 source is cm10.1 source

Sent from my GT-P3100 using Xparent Skyblue Tapatalk 2
[HTC Salsa] vigoos:
Looks like github work is gonna take some more time
[HTC Salsa] vigoos:
Let me try that .bak thing. But somehow GPS works in a port from Wildfire S.
[HTC Salsa] theschneidi:
Some device names I found in Stock ROM, which could help:

some devices are attached to I²C bus with (address?) ... hope it helps for kernel config :fingers-crossed:

adp1650 -- Led Flash driver

akm8973 -- 3-axis Magnetic field sensor / Orientation sensor

akm8975 (i2c 0-000d) -- 3-axis electronic compass (same like in iPhone 4^^)

atmega-microp (i2c 0-0066) -- ATMEL microcontroller which controlls the GPIO

atmel_qt602240 touchscreen sensor

bcm4329_wlan -- Low-Power 802.11n with Bluetooth® 2.1 + EDR and FM (Tx and Rx)

bma150_up_spi -- accelerometer

bma250 3-AXIS ACCELEROMETER

cm3602 -- capella_cm3602 proximity, light sensor

cm3628 (i2c 0-0018) optical sensor

cy8ctma340 or cyctma340 (i2c 0-0067) Cypress Microcontroller

cy8c-touchscreen

himax8250 TFT LCD Source Driver

himax_cabc -- Himax Content Adaptive Brightness Control

mt9v113 (i2c 0-003c) front camera

s5k4e1gx (i2c 0-0010) rear Camera

synaptics-rmi-ts something with touchscreen and chip which monitors temperatures and PWM ...f75375s sensor?

tps65200 (i2c 0-006a) Li+ Battery Charger With WLED Driver and Current Shunt Monitor

Qualcomm Adreno (TM) 200
[HTC Salsa] vigoos:
It helps a lot Schneider. Because if there is any error in the driver source then we can correct it. As of now I really have no idea where Bluetooth driver source is located. If that can be figured out we can do something.

Nexus one has same Bluetooth. We can borrow it from there and test

C file for back camera. Swap it and rename it in place of current CPP file.

https://code.google.com/p/photon-an...htly/drivers/media/video/msm/s5k4e1gx.c?r=126

If you do not rename file and just copy over and delete the previous file, go to the make_obj in same directory and change reference/path

The .h file of back camera. Swap it and rename it in place of current .h file if any. If there is no .h file then just copy it over without renaming.

http://code.google.com/p/photon-and...ghtly/drivers/media/video/msm/s5k4e1gx.h?r=75

Compile a build with following mods. Test and report issues. If there is any error with camcorder, it might get fixed. I'm doing some more investigation on this

Here is that f75375s function

http://www.digchip.com/datasheets/parts/datasheet/931/F75375S.php

Looks like it is some kind of integrator to integrate all drivers
[HTC Salsa] vigoos:
Bluetooth location found!

Bluetooth location found! /firmware/

There MUST be some errors in the source because of which it does not work.

We have 2 options.

A> use this bcm4329.hcd

https://github.com/Andromadus/android_device_htc_ace/tree/jellybean/firmware

In general change source code

B> We can alternatively borrow .ko/.so from any device like crespo, htc passion, U8850 because they have same BT chipset i.e Bcm4329 and make a patch

EDIT 1-

Directed to theschneidi- I suggest we proceed with B. What's your take
[HTC Salsa] vigoos:
My git is up and alive!!!!

https://github.com/vigoos/android_salsa_cm_10.1

Use command in terminal

git clone https://github.com/vigoos/android_salsa_cm_10.1
[HTC Salsa] vigoos:
Breakthrough! Linux kernel 3.x!

github.com/vigoos/android_kernel_htcmsm7227

Do a git clone

Then Google for xda university and follow their guide for compiling from source,

In university guide change deconfig to icong_deconfig instead of bravo_deconfig,

Do the compile, post results

I messed up in last stage. Gonna rework tomorrow.

Directed to theschneidi and darkorn.
[HTC Salsa] vigoos:
Bluetooth problem cause detected.

The problem is with the compilation of libbluetooth.so and libbluetoothhd.so in the system/lib folder. They seem to be improperly compiled.

I had discovered this when I was playing with my source code and found that when I used bcm4329.ko which I compiled then my WiFi stopped. But when I replaced it with chachas then things started to work.

Similarly I'll be borrowing these 2 files from crespo, nexus 1 or some device with same Bluetooth chip set and see if it works.

EDIT 1-

List of devices with similar chipset-

Wildfire S

Nexus One

Nexus S

HTC HD2

HTC EVO 4G

Huawei U8850

Chacha
[HTC Salsa] BigBearEvo:
if the files do work, please host them up seperatly so we can all try them in the builds we are using...it will be interesting to see them work.

Just a quickie.....on future Cm10 releases why don't you add the working GPS config file instead of making the user download it and fix it themselves. I just did it on the paranoid version before flashing and it works for me. Its something you may want to think about.

My GPS config files http://www.mediafire.com/download/dx6dxa9fi8u9258/gps.rar just open and add to proper folder.
[HTC Salsa] Darkorn:
Meh, I'm getting sick of Android. It's a shame I must opt between usability and stability! It makes me want to switch to stock but since it sucks bad I keep our CM10...
[HTC Salsa] BigBearEvo:
I agree. I'm due and upgrade in the next 2 months...seriously considering my options now. I want what we all want. usability and Stability...we cannot have both!

Myself I've resorted to using a mix of all 3 CM10 roms, using paranoid as a base but built on top of it.....But i need more, i crave more. more can only be gained on another handset! In which will give me greater scope to learn more advanced stuff...that i can give back to this phone.

Sad times....:(
[HTC Salsa] vigoos:
I personally have all stamina to do something good for salsa. I never get tired of doing all tricks to get things working. After all this was my first android and only because of HTCs attitude did I sit on for development in which I learnt so much. I agree CM10 is not stable and usable. I personally use my v6 and sometimes shift to PA. To some extent I feel that our hardware specs aren't top notch, nowhere near it. Plus there are hardly a few people willing to develop this device, like on xda itself only 7 of us.

Now in India we have no contract system. So I'm gonna keep my salsa for long years to come. Plus I got my vacations till like mid July. So never too late. The only thing that puts me down is very less numbers of active rooted users. Still we made it till CM10, we still have a lot left.

Come on guys, let us not focus on sad times. All of us are awesome, all can do something. When smaller devices can do it then why can't we? Let the morale not come down, if we have such low morale how will we develop? Let's do it.

Our next targets with decreasing importance-

Bluetooth

Battery life

Stability

Front camera.

Sent from my GT-P3100 using Xparent Skyblue Tapatalk 2
[HTC Salsa] vigoos:
Okay so time for a research report-

I used Wildfire S and ChaCha drivers to no prevail. They didn't work.

Nexus one, Nexus S and HD2 have same chipset. All sites show they have bluetooth 2.1. But when I was preparing my base, I found out they are the same. Have a look @ build.prop of 2.3.3 stock.

# Release Bluetooth HW/SW information
ro.bt.chipset	= Broadcom BCM4329-B1
ro.bt.version	= Bluetooth 2.1 + EDR
ro.bt.stack	= Broadcom BTL-A
ro.bt.stack.version	= 2.2.017
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles	= 4270339

So HD2 driver testing needs to be done. HTC and Samsung have used 2.1+A2DP mainly because they hadn't made updated stack. However 3.0+EDR can function properly. If my theory is correct, then we hit a jackpot. Else, we need to work.
[MENTION=4860185]Darkorn[/MENTION] how did we get WiFi working on CM10?
[HTC Salsa] BigBearEvo:
there is one thing that would help me out..

In all CM10 roms the gov is set to smartass v2 only and noop scheduler. I need these setting back to free not locked. I don't use noop anyway, plus it seems its slowing me down badly cos it won't activate quick enough.

is there anyway to keep it unlocked with smartass v2, possibly some others added in as well...? (minimax and some other crazy setups...)

this might make cm10 respond faster overall....plus we can use setcpu or some other cpu controller to our own advantage.
[HTC Salsa] Darkorn:
Cut and paste from chacha kernel of the wifi dir, but probably we should find a better kernel.

I know, we had ported CM10 but we didn't do anything to make things better.

But the android build system it's such a pain in the ass! I can't recompile android without going mad...

Bluetooth it's not working probably it's something in the kernel, or maybe we forgot the firmware, or it could even be something in the rom.
[HTC Salsa] BigBearEvo:
I know the feeling there lol, i go mad when it just won't play ball with me lol.

If anyone out there has the time to decompile it to add stuff in then feel free. it would benefit if it was done before a new cm10 rom comes out...least then it maybe better to use overall lol.
[HTC Salsa] vigoos:
Gonna test my new kernel today. You people can use my source

https://github.com/vigoos/android_kernel_htc_msm7227

just use XDA University guide. The deconfig file is included. It is called icong_deconfig.

Some problem must be there with the boot image. I suspect so.
[HTC Salsa] vigoos:
QUICKIE-

Has anyone tried BT support option in menuconfig, in driver support last option is for BT support, have a look at it asap. We are inching closer....

Have a look at my config attached
[HTC Salsa] vigoos:
I want some person compiling to test my config file, load the file and compile to tell me. I have a very strong suspicion that the boot image hasn't got support for Broadcom drivers. Is someone still alive and compiling? Because till I don't get any response I can't ascertain what is to be done next. As I would like to mention I can't compile from source thanks to my ISP. If I compare him to a sloth I feel the sloth is a zillion times better. So no source compiling from my side for next few days, atleast till I find a better one.
[HTC Salsa] vigoos:
Who all are still available for compiling? I'm partially available.
[HTC Salsa] theschneidi:
I built a kernel image with some settings I changed in my config file. I haven't checked if mine works. I study your config on weekend.
[HTC Salsa] Darkorn:
Bluetooth now works, boot.img below

PATCH FOR DEVELOPERS (not for icong but I adapted for our phone): https://github.com/adumont/htc-kernel-msm7227/commit/df2ad720771d3c70041f57d07214e78936355b6e

Flash boot.img and put bcm4329.hcd to /etc/firmware.

Anyway I see they ported CM10.1 for marvel, It should be easier for us now...

http://xdaforums.com/showthread.php?t=2283549
[HTC Salsa] BigBearEvo:
Nice boss. Is this cm10 only?

Sent from my HTC Salsa using Xparent ICS Blue Tapatalk 2
[HTC Salsa] Darkorn:
Uhm, the kernel is for CM10, it won't work on CM7 unless you use the ramdisk that works for CM7. But the patch should work.
[HTC Salsa] BigBearEvo:
ill give it a bash on cm7 and cm10 some point this week....depending if i'm still alive that is....and have a home.
[HTC Salsa] vigoos:
I will try this out once I finish my studies for the day. Top class work darkorn..... Now the only 2 left are GPS and front cam. GPS works on ports if the gps.conf file is changed. So I'm gonna focus on front camera now. Hopefully I will get a better ISP next month.