yashsingh1/xdaforums huggingface dataset:
[RAZR i Android Development] drunk_ryder24:
intel released source code for android 4.4

http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image

if its helpful
[RAZR i Android Development] kelvinmorcillo:
Did you guys saw this?

http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
[RAZR i Android Development] pangyaaaaaa:
hey this is just

Android* 4.4 (KitKat) x86 Emulator System Image

this is for developers who running a pc (x86) and want to emulate the newest android.

this has nothing to do with our fone.

i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin ;)

regard
[RAZR i Android Development] Hazou:
Yep, as you are saying. They are only for emulating android-x86.

They don't contain some form of drivers for any device, and won't be helpfull for us, but it says that android 4.4 for x86 can be build with is a nice thing :)
[RAZR i Android Development] Sagic:
news about the sound?
[RAZR i Android Development] Hazou:
nope, no improvements. if there will be any improvements about the sound from me, it will be next year.
[RAZR i Android Development] drunk_ryder24:
how about the source code files wich allows you to precompile your own desired image,as for my knolege the system.img isnt too much different than the motorola,just some proprietary stuff,in a video presented by intel they made allmost the entire board ready to go for manufacturers(probably why moto created the phone)and also claimed that the img its easy to boot on an intel powerted board,its pure x86 atom build

http://software.intel.com/en-us/articles/intel-eula-x86-android-4-4-kitkat-source
[RAZR i Android Development] Hazou:
You are right about that, but Intel hasn't provided the configuration files for Medfield devices like ours. They were 1 or 2 years ago online under the name mfld_pr2. But not anymore, there's no source available for it. All locked behind a password or in servers.

What intel did is providing a working system that works when you put some device files in it. But here is another problem. There are differences between android versions and how they work. Especially the sound. And here is were our problems lies. We need to get a workaround working or make totally new sound files. The last one is only durable when we have the source. And the ALSA source is sort of available, but the ones we use are modified by intel, and we don't know what they changed or added. So we are trying workarounds, but that cost time. It is a lot of testing (mainly failing), we eventually will get it working. Always stay positive :P
[RAZR i Android Development] pangyaaaaaa:
someone asked intel for the sorce files??

developing is not a crime !!!!
[RAZR i Android Development] mcastagnaa:
"shouldn't be" is more appropriate I am afraid. Xda is full of people crying for the absolute lack of cooperation from hardware providers. Ask the guys at Cyanogen about the stupid exynos Samsung chipset.

I am pretty sure my next mobile will be Qualcomm based.
[RAZR i Android Development] thiagomtl:
Maybe the Git mentioned here helps?

http://hi.baidu.com/onlinesen/item/ed0359c1b71bf357ac00efb1
[RAZR i Android Development] Hazou:
password locked
[RAZR i Android Development] Hazou:
The git is password locked ;) not the website :P
[RAZR i Android Development] Burn02:
The answer is not the same for me:

Could not resolve hostname shsrv888.sh.intel.com: Name or service not known

It could not find the repo in fact.
[RAZR i Android Development] Omar-Avelar:
Hey Hazou -- I got some free time now... let me see if I can help with something -- I think that Intel's 4.2 sources do have the modifications required for ALSA to work but we need to analyze to see what and where we need to start re-using code :D.

What steps am I missing to get the ota.zip to build (I see there is also an smi-plus repoository also I don't know if you are overlaying some files in the CM's repo from Motorola's sourceforce as "ApplyPatches.sh" complained and so did build process.

# My Linux box has an already working environment and tools
[B]mkdir cm10.1
cd cm10.1
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo sync[/B]

[B]mkdir -p device/motorola/smi
git clone https://github.com/HazouPH/android_device_motorola_smi device/motorola/smi
cd device/motorola/smi
./ApplyPatches.sh[/B]

# Go back to cm10.1's folder
[B]source build/envsetup.sh
./vendor/cm/get-prebuilts
lunch cm_smi-userdebug
time make -j10 bacon[/B]

But it failed :eek:, let me know what you see wrong/missing :good:...

Note: Just an idea here but first I tried to run ApplyPatches from some other current working directory and it fails... I think you could add the following variable to the bash script on top so it knows from where to start executing "CURR_PATH=${0%/*}" and append "$CURR_PATH" where necesary :laugh:
[RAZR i Android Development] Hazou:
Y, I am overlaying some stuff from my own files. And they are mostly by comparing the aosp, cm, Motorola and intel sources with each other, were it is needed.

U need to repo init my manifest from the github github.com/hazouph/android

It includes some changes and all the files who are needed. Because I have made some changes in bionic, dalvik, system/core and some more.

The applypatches.sh has some small changes to frameworks and powertop. I didn't want to fork an entire repo for it. Next to that it includes the recovery patches to get a smooth experience in it.

I will test this all out again somewhere tonight to get rid of all the errors so u get a working zip.

I see u use the command 'brunch' I never used it? I use the command lunch indeed, after that just the 'make' command and when it is finished the 'make otapackage' command.

B.t.w. do u have any command to get a symlink directly in the updater-script? Haven't looked into that, but we maybe need it for WiFi.

Will update this post when all is done.

Edit:

Looks good to me now. Take a look at the tutorial in my github. Its called "small tutorial" in the SMI repo. If you have anything that can automate the processes I am using pls, say it ;)
[RAZR i Android Development] Omar-Avelar:
Thanks, I think we could add the following in full_smi.mk to have a symlink that will be zipped and installed and points to the pds partition regardless of where it is :laugh:

# Wireless related stuff
$(shell ln -fsbS $(OUT_DIR)/target/product/smi/system/system/etc/firmware/ti-connectivity/wl12xx-fac-nvs.bin /pds/wifi/nvs_map_mac80211.bin)

I remember that if that symlink is not created you will get a generic MAC address and weird readings in the signal strength/noise indicators...
[RAZR i Android Development] Hazou:
Thx Omar, will add it in the source.

I just found out that the audioflinger from the 4.2.2 system dump is almost the same as the 4.1.2 one. So in theories they used all the audio files from jb 4.1 in jb 4.2. Will try to replace them all and get them working on 4.2.
[RAZR i Android Development] Victor-G:
Have you tried implemting the HAL overlay from the hardware_intel_mfld_cdk.tgz file from the Motorola source?
[RAZR i Android Development] Hazou:
Thanks for the suggestion. Yes, I have. But to get those things working I need more source code were we don't have access too...
[RAZR i Android Development] kelvinmorcillo:
http://gizmodo.com/asus-zenfones-an-android-army-with-intel-inside-1495505999

Maaaaybe this will help us?
[RAZR i Android Development] Marco Lomas:
Any hope for my heart? :')

Enviado desde mi XT890 mediante Tapatalk
[RAZR i Android Development] pangyaaaaaa:
where did you ask yet for the source code we need?

moto? google? intel? all 3 done??
[RAZR i Android Development] Hazou:
I only haven't asked Motorola. Google doesn't have the right sources. And i may have some contact with Intel, maybe.

But Motorola would be a nice one to go.
[RAZR i Android Development] pangyaaaaaa:
cool! hope u will have a nice contact with intel, if the guy is nice you talked maybe you could ask for the users of this thread:

service require code currupt

to getthe files they need to fix this but just in case you speak with a nice person.

tell me exactly what u need and i will do what i can to get it from moto! ;)

see u
[RAZR i Android Development] Hazou:
We will see, small chance though ;)

About the source from moto. If u have a look at the following file on your device: data/dontpanic/droidboot_manifest.txt.

Those are (maybe) all the source files Motorola changed to get it working on our device. The things I am interested in are :

Device/moto/intel_mfld

Device/moto/SMI

Frameworks/base

Hardware/libhardware_legacy

We could ask for them, hopefully they will provide them :) but I doubt it.
[RAZR i Android Development] pangyaaaaaa:
a lil chance is there.

whats about reverse engeneering? someone who can do that tryed already?¿
[RAZR i Android Development] YaPeL:
Is not as easy as it looks, it requires a lot of hardwork, thats why he is asking for it, to avoid the "reverse eng" process.
[RAZR i Android Development] Hazou:
Yep, it is heavy time consuming, and if u are studying, don't have the best knowledge about those things, it is not worth the time ;)
[RAZR i Android Development] YaPeL:
Yep, its simply not worth it, more if you take into account that you can get a kitkat device for 2 bucks, and here we are, fighting to get 4.2, I still think, that chinece rom is our best shot, I need to start looking at it again...
[RAZR i Android Development] pangyaaaaaa:
cool, yep reading asm eat much time..
[RAZR i Android Development] tedeha:
Cmon!!!!!!!:D:D:thumbup:
[RAZR i Android Development] Marco Lomas:
I have see that the galaxy tab 10.1 with intel proccesor have a lot of new people trying to build aosp and cm! Also, the tab has native 4.2, maybe the sound libs or something similar can help??

Enviado desde mi XT890 mediante Tapatalk
[RAZR i Android Development] Burn02:
The problem is it's not the same hardware exactly. :/

The cpu is new, and not a Medfield. :/

I doupt that the sound part would be the same. But well perhaps we could have good news from that. But that's not sure. Even if it's a X86cpu, it's not exactly ower processor and hardware.
[RAZR i Android Development] Le_Poilu:
http://ark.intel.com/fr/compare/70098,70101

Not quite the same CPU cores.

And the SoC based ont this cores are different. Radio, Sound, etc may not be the same.

Don't think you can use any other recent x86 android device to help here.

There not many devices with medfield SoC : Lenovo K800, XOLO X900, ZTE GRAND X IN ... and that's pretty all...
[RAZR i Android Development] Hazou:
They are indeed different. The galaxy has a cloverfield board with cloverfield audio, it won't work on ours, but maybe if they have the same problem and can get around it it could benefit our device.

At this moment i am on a dead end. I thought i got a leash yesterday, because i found out that the error starts when the hall is asking for "adev_get_parameters". It gets wrong parameters (strlen error) or something. I know the qcom variant is using different audioparameters so looked into it. But i found out just this morning that our device isn't using any specific parameters. Taken into account only the ones from libmedia, not the ones in etc/framework-parameters (they are loaded on a different pointer somewhere in the audiohardwarealsa and are using 2 libs to get them working,(libparameter.so, libxmlserializer.so) no problems here)

So i don't know it anymore, taken me to much time already :P.

Maybe the galaxy one can help us when they are ready.

Hazou
[RAZR i Android Development] Le_Poilu:
To sad you're blocked on this one.

Maybe can you put audio on the side and try to make the rest working ?

If you can get everything but audio working that may motivate other people to take a look on it.
[RAZR i Android Development] paulle:
sailfish

Can it be possible to run sailfish os on the razr i, because there are builds fo the N9 x86.

http://xdaforums.com/jolla-sailfish/general/salfish-os-rom-download-t2611503/post49606043
[RAZR i Android Development] Hazou:
Almost everything is be possible. Another OS for x86 could run on our device, but without the right vendor settings and files u won't get any were. And we still have trouble with android ;)
[RAZR i Android Development] Sagic:
If i understand... It's possible to port the OS ROM (sailfish) to the razr i but... How ?

What files to modify for the os run on the Razr I ?

And it's possible to test on my PC the rom for run on the Razr I ?

Thank's !
[RAZR i Android Development] Hazou:
Yes, it is maybe possible, but it needs some modifications in the sailfish ROM itself. How I don't know. To boot CM is already not a pleasure.

U can't test it on your PC.
[RAZR i Android Development] Marco Lomas:
Hazou what about try aosp? Maybe there is another errors regarding the sound problem but with another perspective?

Only to give some idea or something :)

Enviado desde mi XT890 mediante Tapatalk
[RAZR i Android Development] YaPeL:
I remember reading in the source code of moto that you can build aosp from source, you know, having AOSP/cyanogenmod from android 4.1.2 may sound stupid, but with that we can build, ubuntu touch, ffos, and so on.
[RAZR i Android Development] Sagic:
Hmm okai... I prefer cyanogen anyway ... But, the sound is always a problem ?
[RAZR i Android Development] Hazou:
I am thinking of that and maybe will try it out. But CM is not that different from aosp so I don't expect much. I also heard that android 4.4 has more support for x86. Maybe will try that one too someday.
[RAZR i Android Development] adddaamo:
Hazou, if CM 10.1 is so hard to achieve, maybe CM 10.0 based on our Android 4.1 is possible ? For me having ANY version of Cyanogenmod would be great, and it could work as base for other custom ROMS. We should have all the necessary files to make CM 10 works on RazrI.

BTW. Hazou, thanks for your great work!
[RAZR i Android Development] Hazou:
Yes, would be Nice if any cm version would work. But the jellybean one of cm has the same problem... There is just something missing in the audioflinger or libmedia* files I think, but what?
[RAZR i Android Development] Sagic:
News about the sound ?
[RAZR i Android Development] Burn02:
Hello.

Hazou perhaps you could ask something here for the sound driver?

http://software.intel.com/en-us/forums/topic/500784
[RAZR i Android Development] Hazou:
Nope, no improvements on sound. Busy with other things ;)
[RAZR i Android Development] chuckiebronco:
Being a bit nosy, you mean other things regarding cm/Razr i :fingers-crossed: or other things :crying:?
[RAZR i Android Development] Angel_666:
Hi Hazou! I have a same problem with cm11 on galaxy tab 3 10.1 (intel clovertrail). I implement all possible alsa code and utils in source and no luck. But then i see, that in our (sgt3) stock system image there are no any "alsa" libs included. Only audioprimary and audiopolicy in HW folder and libtinyalsa in lib folder. Then i open my kernel config and see that we have wolfson WM1811 card as audio device.

After that, i find a wolfson microelectronic site with lot of opensourse drivers for their chips and tinyalsa and tinyhal sources to build drivers for android. http://opensource.wolfsonmicro.com/content/tinyhal I don't build it yet, but soon i'll do it. What do you think about it?
[RAZR i Android Development] Hazou:
On the razri:

- searching and trying sound sources and configs, still i am way off

- wifi fixes, almost done

Other android

- twrp lag fix in Samsung tab 3 10.1, provided sources to them

Other things

- school stuff

This is already implemented in the source of cm. What u need to know is what alsa config files u have? If u got a mixer_path.xml , just copy it over with the hw libs and try. I can have a look to see what the tab 3 is using, but most likely it is different from ours ;) But the sources for the chip can have a positive effect as a second option. But need to take more time to look into that. I am not an alsa guru :P

For instance, in the RAZR I. We make use off the old asound.so and asound.conf for our medfieldaudio sound card. We need to get them working under the new jb. And that is difficult, without the original source we need to rewrite all of it.
[RAZR i Android Development] Thorstenk:
go go go

A bit off topic but I:

Just want to let you know that I really celebrate you!

We will from my point of view most likely not get any official update and you have already done so much, thats very very cool!

Cross my fingers that you will sort to the missing bits, or somebody will be able to use your work as a base for doing so!

Your my personal hero!

Best

Thorsten
[RAZR i Android Development] Paul L.:
Sorry for disturbing (or for uploading wrong files).

external_alsa-lib.tar.gz

http://d-h.st/4SV

external_alsa-utils.tar.gz

http://d-h.st/bji

hardware_intel_include.tar.gz

http://d-h.st/H0y

hardware_intel_mfld_cdk.tar.gz

http://d-h.st/pRj

hardware_intel_psb_headers.tar.gz

http://d-h.st/852

vendor_intel_common.tar.gz

http://d-h.st/c03

I don't remember where I got them from, probably from a FTP server somewhere; they are for this phone for sure, or atleast for the medfield platform; I searched for a file for my ST-Ericsson SoC on my Samsung Galaxy S Advance and I found it on one of these tar.gz archives;

a long time ago

- Today, while checking this phone (and this thread), I remembered that I have those files, I uploaded them, maybe they could be useful for someone here...
[RAZR i Android Development] Hazou:
Thx for the input, I already implemented some of them in the source ;) but yes, we need some of those files.
[RAZR i Android Development] Angel_666:
Well.. I research that our device (SGT3) use TinyUCM to realize audio finctions. (tinyucm.conf in etc folder) I already tried to implement 3 possible variants of audio: 1. full alsa 2.Tinyalsa. 3.TunyUCM. The point is, that all 3 variants seems to works (correctly found and use audiocards in proc/alsa), but no sound to speakers. I think, we need to dig config files.. And one more thing: variant with tinyUCM include audience-fx and ril-audio implementation. I think this is most closest variant of audio implementation (if we look at original set of libs). As for original libs - they won't work with opensource and cm builds: conflicts with libmedia (missed symbols).
[RAZR i Android Development] Hazou:
Hmm, looks interesting. Can you post your audio cards from proc/alsa and send me a copy of the tinyucm?
[RAZR i Android Development] Angel_666:
cat /proc/asound/cards
0 [cloverviewaudio]: cloverview_audi - cloverview_audio
cloverview_audio
1 [Loopback ]: Loopback - Loopback
Loopback 1
2 [IntelHDMI ]: IntelHDMI - IntelHDMI

cards

cat /proc/asound/devices
0: [ 0] : control
16: [ 0- 0]: digital audio playback
17: [ 0- 1]: digital audio playback
18: [ 0- 2]: digital audio playback
24: [ 0- 0]: digital audio capture
25: [ 0- 1]: digital audio capture
26: [ 0- 2]: digital audio capture
32: [ 1] : control
33: : timer
48: [ 1- 0]: digital audio playback
49: [ 1- 1]: digital audio playback
56: [ 1- 0]: digital audio capture
57: [ 1- 1]: digital audio capture
64: [ 2] : control
80: [ 2- 0]: digital audio playback

devices

Error in logcat:

E/AudioTrack( 2940): Could not get audio output for stream type 1
E/SoundPool( 2940): Error creating AudioTrack
[RAZR i Android Development] Hazou:
Is that the first error u get? Looks like somewhere else is another problem. Can you give me the output of the whole logcat file and the ucm.conf? I can't say I can solve it, but I am now a bit familiar with alsa, and how it works :P
[RAZR i Android Development] Hazou:
Audio working

Ok, replying to myself :P

But Great new, got Audio working. Haven't tested it fully, but ring-tones etc, do work. If call works and music/video i don't know yet. Will update the first post tomorrow, so everybody can give some feedback. Cant test it myself due to other priorities for the next couple of days.

Happy xD
[RAZR i Android Development] PatricioJP:
Wow, really, you guys are geniuses! It is the most awaited rom in the history of android ...

Sorry if my English is not very clear, I am from Argentina and management with google translator

Wow, la verdad, ustedes son unos genios !!! es la rom mas esperada en toda la historia de android ...

Disculpen si mi inglés no es muy claro, soy de Argentina y me manejo con traductor google

:fingers-crossed:
[RAZR i Android Development] TheOriginalAndroPaul:
are several in Argentina we hope this Rom and use the google translator hahaha
[RAZR i Android Development] PatricioJP:
Bién, entonces, cambiemos el idioma de este foro, jajajajajaja:laugh:
[RAZR i Android Development] Liszt Fender:
Jaja Veo que y hablan en Español, Entonces, Que mas falta para que sea "Estable"?

English: So, what is missing in the ROM to become "stable"?

Enviado desde mi XT890 usando Tapatalk
[RAZR i Android Development] Marco Lomas:
I only leave the forum 1 day, and comeback and there is sound!!. Im crying of happiness (ok no)

Thank you so much Hazou, you deserve all the respect! Congrats :D

Enviado desde mi XT890 mediante Tapatalk
[RAZR i Android Development] adddaamo:
Really, really great news. Amazing work Hazou ! What did you do to make it work ?
[RAZR i Android Development] Hazou:
Uploaded the new zip file, be careful. It isn't tested very good. Had it installed just 1 time for 5 min on my phone and ringtones did work.

How i got it working:

There are many ways to get alsa audio working on android phones, we are using an the oldest variant with libasound and asound.conf.

The others are: the new qcom alsa_sound, tinyalsa and tinyucm. But for those i need to change and try lots of different config files.

So i looked for a method to implement libasound into ours and i came across the device NookCollor. Steven676 has done some things for this device including getting the sound working with libasound. He already upgraded the old alsa_sound codes to the new ones so i didn't have to do it. Now i just needed to get the asound.conf working with libasound and the alsa_sound codes. Just a matter of trying. And that took some time.

At this moment, i think that normal sound over the speaker and headphones like ringtones, movies and music should work. I dont know it yet about calls and voip, because we maybe miss some code for this in the alsa source. Also the specific audio things from intel like the modem may not work, it isn't implemented and i don't have any source for that.

Hazou
[RAZR i Android Development] mercurio.:
just a quick reply:

sms work (also long ones that crashed the app using omars rom)

ringtones and system audio works

audio in browser and youtube works

camera crashes

audio routing to front speaker only works when call ended (the end call tone is the only thing i can hear trough the front speaker) but maybe it's a problem with the routing in the phone app because switching to rear speaker also gives no sound!

wifi and bluetooth still don't work (but i think they aren't supposed to work at this stage of the rom)

EDIT:

done some more tests:

audio routing trough headphones works great (it's insane how load the razr i drives my headphones when using cm!)

mic routing does not work for me. can't hear when calling the phone, also recorder does not work.

routing of key tones during a call works.

also routing to front speaker seems to work, the strange thing is that the only time i can hear something is when i call my own number and the line occupied tone is submitted. imo, the problem has to do with the phone app.

generally speaking the rom is super smooth. imo the browser is a lot faster than the stock one in the stock rom.

hazou i really hope you'll find some time and maybe also be able to port cm11 at some time. i think it'll be like a revival of a lot of razr i phones.

regarding the sound problems with the phone app, from what i remember when cm was first ported to the zte blade there were some similar problems, will have a look at it, maybe i find something that could help you.

EDIT:

did some more testing, found that the auto brightness does not work for me!