yashsingh1/xdaforums huggingface dataset:
[Xperia SP Original Android Development] KelleyCook:
And it is due to this commit https://github.com/CyanogenMod/andr...mmit/324fa77f0d8868806af7025e670516105fd89a65

Which looks to unify the kernel with the 1st gen Krait 200 devices: Assuming that is correct, it would also needs an obvious change to the dependency file here since the unified kernel tree is not getting pulled.

https://github.com/CyanogenMod/android_device_sony_huashan/blob/cm-11.0/cm.dependencies

I just commented on the commit, hopefully it gets back to the initial committer.
[Xperia SP Original Android Development] Rycon33:
^Yup, the BoardConfig.mk file is looking for msm8x60 while the path is still msm8960t.

Tapatalked from my Xperia
[Xperia SP Original Android Development] uberlaggydarwin:
Yup. I missed the blue-common merging then the start of the DMCA drama so I forgot to check if the cm.dependencies had been updated and only noticed 5 or 6 hours ago....

Sorry about that but you should get a new nightly tomorrow as this patch was MERGED.

We joined a family :P instead of being the weird stepchild (in terms of kernel).
[Xperia SP Original Android Development] RoXzAn:
Is there any way to get 2 mic working
[Xperia SP Original Android Development] TechnoSparks:
So far I didn't faced any troubles at all. ;)
[Xperia SP Original Android Development] MrSteve555:
No, currently there is no way for that, but it's being worked on and a fix will be available soon.
[Xperia SP Original Android Development] :
Changelog for FXP 327 ?
[Xperia SP Original Android Development] Daniel.Medeiros:
Thank you for the updates!!
[Xperia SP Original Android Development] Rycon33:
Just did a resync with the updated kernel repo path, and updated wifi drivers working.:good:
[Xperia SP Original Android Development] Theliakos:
ok guys cant understand something ! nighlies are AUTOMATICALLY generated by whom ?? i mean people biuld them ??

stupid but please help me
[Xperia SP Original Android Development] Rycon33:
they already said it will come very soon:D it is auto-build by the cm build-bots once the developers' changes are commited, approved and sent upstream for syncing

but some of us are self-compiling from their repo source, that's why we can have it at anytime(wether there's some changes or not it depends on the timing that we made the sync and build)

p.s. I sent you a PM
[Xperia SP Original Android Development] Theliakos:
thankssss!! :D
[Xperia SP Original Android Development] uberlaggydarwin:
here's a build

Back to nightlies and other magic:

with love from the CM team

download.cyanogenmod.org seems to be a bit broken so here's a mirror

sorry for all the delays :)
[Xperia SP Original Android Development] claudio917:
Nightlies are BACK ladies and gentlemen :D Thanks again to the developers, keep up the good work! The only bug I experienced in the latest versions is that sometimes the screen goes totally blank for a few minutes, you can't turn the screen on, but then it comes back... Don't know if it's a kernel issue maybe, I'm using Williams v3.2.. Anybody else experienced this?
[Xperia SP Original Android Development] Juri Jacopo G:
Why we can t get a SNAPSHOT release from CM team ??
[Xperia SP Original Android Development] mykamran:
I have this issue with cm kernel and other kernel.
[Xperia SP Original Android Development] francescohtc:
because the development for our device is on an early status, we have to wait that all features works, like the 2nd mic for example, after the cm team will release a "stable".

What devices had the Milestone and are missing basic hardware features?
[Xperia SP Original Android Development] Juri Jacopo G:
Thanks so much ! So is there any chance to have a stable version ?
[Xperia SP Original Android Development] MrSteve555:
It's not like that...

We were close to getting M8 snapshot, but the DMCA takedown held us back from it.

Every device with nightlies, even with all features not fully working, gets the snapshots.

And there are no "stables" in CM now, only nightlies and M snapshots.
[Xperia SP Original Android Development] francescohtc:
that's why i put "" between the word "stables" ;)
[Xperia SP Original Android Development] elaff:
My wifi is not working on last nightly with Williams kernel. With Cm kernel wifi runs ok
[Xperia SP Original Android Development] francescohtc:
instal the fix for modules in williams kernel thread... ;)
[Xperia SP Original Android Development] claudio917:
I've experienced that bug too with williams kernel... Unfortunately it doesn't work even with the fix zip... I went back to 30th June nightly to use it with Williams kernel... Faux sound tweaks are too important for me at the moment...
[Xperia SP Original Android Development] KelleyCook:
Or … stop installing the Williams kernel and complaining that things broke. Cyanogenmod has its own kernel which is flashed every time you install a CM ROM.

And if you do install an alternative kernel and something breaks, this thread is not the place to complain about it. Go to the thread where you got that kernel.

Also note that beginning with the 20140710 nightly, the SP is using different kernel sources (same kernel as the older Xperia T and V).
[Xperia SP Original Android Development] Theliakos:
using differenet kernel sources give as something ? i mean its better ??
[Xperia SP Original Android Development] ironshadow2:
guys, how do I take logcat in bootloop?
[Xperia SP Original Android Development] antoyn:
No offence, but i feel that william kernel does not help much in terms of battery consumption and performance. For battery consumption, it depends more on how you use your phone. Moreover, some so-called battery saving apps like battery gxxu, i deem they just have little effect. The only thing in which i think can inprove battery consumption and performance is ART runtime mode
[Xperia SP Original Android Development] TsunaH:
Yeah I agree about ART but most of us use Xposed and it's not compatible with ART
[Xperia SP Original Android Development] elaff:
I only was saying that about williams kernel to alert a lot of people who use it. I'm sorry, try to be a little more hapy. Have a nice day.
[Xperia SP Original Android Development] MrSteve555:
[MENTION=4193352]adfad666[/MENTION] [MENTION=5314976]uberlaggydarwin[/MENTION]

I'm digging through the rear mic issue with [MENTION=4291029]peters.[/MENTION]. And after research we've got some information, which might be helpful.

1. We can add the second mic to Handset device, which gives us working two mics while recording:

https://mega.co.nz/#!qZwzESgQ!tuyzSSfdfsklnVaqEgzwS-4V8SrvNoC3xQr3-3CMG-Q

But sometimes we don't have access to second mic with error:

alsa_pcm - cannot open device '/dev/snd/pcmC0D0c', errno 22

2. Strangely, CM audio system uses Handset device with ACDB id of 4 for recording, while stock uses DMIC Stereo Tx (but according to legacy alsa-intf sources, the correct name of that device should be Dualmic Handset Tx Endfire). We can change Handset acdb id to 35, and the OS will use it, even with changed ACDB. For reference, Moto X uses Camcorder Tx with ACDB id of 61. Unfortunately even if camcorder is set, it's not used on our devices.

3. Both stock and CM use usecase HiFi Rec with modifier Capture Music

4. Using stock audio libs leads to non-working audio with lots of alsa errors.

5. Compiling audio as "normal"(non-legacy) gives us working audio, but rear mic is still not working.

6. Some devices in snd_soc_msm_2x have wrong ACDB id's, and some of them aren't present in sources. However, editing that file to only include the devices that are present on Moto X(I think it's a good reference for devices, because other than devices from Moto X we only have HDMI/MHL devices) gives us xLoud volume level.

8. The sources are giving us the correct values for fusion3 board, but they don't work as nicely with viskan platform.

I hope this helps somehow.
[Xperia SP Original Android Development] badaboumcrac:
Hi all, since the last update, emojis doesn't (all are white), someone has a fix fort that ?
[Xperia SP Original Android Development] KelleyCook:
I refrained from answering this until I could try it for a while.

The Good!

* I will say that with a few hours use of the post DCMA CM11, it is much better than the laggy system that came with the old kernel. My SP now acts like a even quicker Xperia T (my wife's phone). Absolutely, no hesitation when choosing new applications.

* Battery seems fine even with highres location services on.

* And with one exception (see below), no crashes or FC

The Bad

* Still no Tap-To-Pay (surprising as it works on her T), but everything else seems great.

* Second mike still not fixed, but from a few posts back it seems people know about it and are working on it

The ugly:

* I, too, once had a black screen freeze a few minutes after installing the new system. After pushing the hard-reset button, it has not reoccurred.
[Xperia SP Original Android Development] Rycon33:
I noticed that when pressing the toggles in notification and quick settings, there's no haptic feedback. I don't see any option about it in settings as well.

Tapatalked from my Xperia
[Xperia SP Original Android Development] Levered:
what about latest cm? does it fix black screen?

0711
[Xperia SP Original Android Development] Juri Jacopo G:
Where i can find changelog of lst nightlies added ? on http://www.cmxlog.com/11/ , sony xperia does not exist..
[Xperia SP Original Android Development] KelleyCook:
Yep and BBQlog stopped working correctly for the SP also. More fallout from the DMCA.

Until they get fixed, the easiest way would be to check from the phone.

Settings -> About Phone -> ... updates -> Choose Development to show nightly -> If I remember right, Clicking on the name of the July 11th one and it will give you a changelog.

Plus the free ($1 to turn off ads) app Cyandelta which all CM11 nightly users should have has a tab at the top with the daily changelogs.

Also for the record, a quick check of the custom repos Huashan uses shows nothing Huashan/Sony specific was committed yesterday
[Xperia SP Original Android Development] ironshadow2:
guys, how do I install all my phone drivers on my pc and my phone? please help

Trying to take a logcat in bootloop at sony logo
[Xperia SP Original Android Development] Metzel0s:
Hi all, I have the latest kernel of doomlord (3.4.0-DooMKernel) and my build is: 12.1.A.0.266.

Can I just flash CM11 on my SP without downgrading?

Thanks
[Xperia SP Original Android Development] RoXzAn:
Yes you can.
[Xperia SP Original Android Development] TechnoSparks:
Why would you need to downgrade? Flashing CM will replace your /system and also flashes stock CM kernel. This means, you'll require an unlocked bootloader and also your original kernel will be gone.

Remember to unlock your bootloader otherwise the worse may destroy your life!
[Xperia SP Original Android Development] Metzel0s:
I think in order to flash Doomkernel I had to unlock bootloader. How can I check if it's unlocked now?
[Xperia SP Original Android Development] RoXzAn:
It is already unlocked othr wise you would have bricked your phone because flashing a custom kernel requires unlocked bootloader.bt if you want to chek dial *#*#7378423#*#* aftr that select 1st option then configuration... I think so
[Xperia SP Original Android Development] Metzel0s:
yeap..thanks a lot :)
[Xperia SP Original Android Development] TechnoSparks:
Okay to check if your bootloader in unlocked, and currently you are on a stock Sony ROM, go to dialpad (your phone app) and type in "service" which is *#*#7378423#*#*

Then go to Service Info > Configuration

If yours not unlocked it will say

I don't quite remember what it will say if it is unlocked but yea above example is enough. :)
[Xperia SP Original Android Development] KelleyCook:
You will have to wipe data.
[Xperia SP Original Android Development] adfad666:
This is very interesting. I've been hacking B2G recently, but I'll come back to CM check this audio issue out.

How exactly are you checking the audio routes? is it simply in logcat when you test different functions?
[Xperia SP Original Android Development] MrSteve555:
Yep, it's simply in the logcat(to make reading logs from audio easier I'm using grep acdb and grep alsa).
[Xperia SP Original Android Development] peters.:
Even better: logcat | grep -i alsa

;)
[Xperia SP Original Android Development] [GER]Roxxor:
Hello,

While you're looking at audio bugs, could someone have a look into SIP/VoIP?

No audio is working in those calls. There is a report with log in the bug section.

Thank you very much :)
[Xperia SP Original Android Development] DThought:
WIFI Mac Collision

Since the reboot of CM11, i get a WIFI/Wlan MAC adress collision.

Prior versions of CM11 worked well and pulled the devices' original MAC adress from some magic storage to use it.

The current version ( cm-11-20140711-NIGHTLY-huashan ) assigns both xperia-sp we've got to the same mac adress, which yields to realy unwanted behaviour with the access point. (The Mac adress i get is 00:0a:f5:89:89:ff )

Could you check whether you've got the same MAC adress (visible in about the phone...)

Thanks
[Xperia SP Original Android Development] rafus:
Same here, I confirm.
[Xperia SP Original Android Development] Rycon33:
^^edit the MAC address files in /data/etc
[Xperia SP Original Android Development] adfad666:
I've been bashing and bashing and testing and testing.

I think I've found a solution.

I've uploaded 3 commits to CM gerrit:

one that removes most of Sony's additional paths (mostly legacy bluetooth),

one that renames the SGLTE paths to Voice2 according to CM/CAF audio drivers,

one that replaces 'Handset Tx' config with Sony's custom 'DMIC stereo Tx' config.

I did some testing and it works! however I ONLY tested recording a video, so it may actually break everything else...

Test the file here: http://filebin.net/57axkvf41o replace it with the one in /system/etc/snd_soc_msm

http://review.cyanogenmod.org/#/c/68000/

EDIT: if everyone can test this file, I'm not able to test LTE or bluetooth - so that's LTE calls, bluetooth calls, bluetooth music etc etc.
[Xperia SP Original Android Development] TechnoSparks:
I just want to know if anyone else have this problem. Do you guys encounter random systemui crashes right after waking up the screen? Not frequently but it just happens. I just want to know that i am not the only one facing this.
[Xperia SP Original Android Development] RoXzAn:
I dont have any systemui crashes
[Xperia SP Original Android Development] nplezka:
Sometimes. Very rare but it happens.

There's anyone facing problems with flash? It makes photos too yellow-brown than reality in every camera app I try. I must use flash in torch mode for best colors...
[Xperia SP Original Android Development] krokanic:
tested and working...now the rear mic is recording video :)
[Xperia SP Original Android Development] TechnoSparks:
Should "import dictionary" crashes the AOSP Keyboard when being tapped? If it shouldn't this might be a bug. :/ Eversince migrating from stock to this CM, I always wanted to have my Malay language up and working for the spell check. Before I temper with the latinIME, I want to start with the native settings first. But i am greeted with a crash.

Okay thank you for replying

Good to know someone else is having the same thing too. I guess I can now relax(?) :D

---------- Post added at 03:28 AM ---------- Previous post was at 03:15 AM ----------

I have tested your given file and I would gladly say that it worked. However sad that I could not test with bluetooth headset (don't have one) and LTE calls (apparently LTE is not yet everywhere at my place)
[Xperia SP Original Android Development] Rycon33:
With the new fix, bluetooth music is still fine on my sony sbh50.

Tapatalked from my Xperia
[Xperia SP Original Android Development] knightazura:
Guys, latest FXP327 is same with which (latest) version from nightlies?

Currently i am use FXP323 (Android 4.4.3), and if wanna upgrade to 327 should I clean install??

If there someone use 327, pls tell me how about it :fingers-crossed:

Thanks
[Xperia SP Original Android Development] KelleyCook:
Well there was no FXP327 built for the SP due to the DMCA mistake. But there is a 326 and there should be a 328. I would recommend waiting until 328, the replacement kernel is much better than all the other CM11 ones.

Contrary to what others may say, there is never a need to clean install from any previous CM11 (or for that matter CM10.x) rom, just flash the ROM.

You may need to wipe data if you go to a earlier build though.

Also note that for the SP with CM11 FXP is exactly the same as the official Cyanogenmod builds.
[Xperia SP Original Android Development] codeknight11:
So basically there's no difference between official CM and FXP CM for SP? Not even in terms of performance? :confused:
[Xperia SP Original Android Development] peters.:
Yes, both are built from same sources. The only difference is the bootlogo.
[Xperia SP Original Android Development] [GER]Roxxor:
SIP audio still doesn't work. As it didn't work before, your patch does not break it ;)

Hope you could have a look..

Thanks for everything!
[Xperia SP Original Android Development] peters.:
What client do you use? I'm using Csipsimple and audio works just OK...
[Xperia SP Original Android Development] Choucko:
I can't boot up my phone after placing in the new mic fix :/

It's just stuck on the boot animation even if I factory reset it
[Xperia SP Original Android Development] peters.:
Reflash the ROM, copy file and set 644 permission (chmod 644 snd_soc_msm_2x)
[Xperia SP Original Android Development] RounakCreationz:
Ramdom SystemUI crash

I guess you are also using some modules in Xposed like Gravity Box. Same happening with me :(
[Xperia SP Original Android Development] TechnoSparks:
My God! Gravity Box is behind this! I started noticing this behaviour right after flashing the 11th July Nightly. 12th make it worse but not that much. Man i need to learn comping. I just want to have GravityBox's app launcher that's all :(
[Xperia SP Original Android Development] RounakCreationz:
Also Tined status bar module does the problem. Which sums up which ever module tries to edit Status bar and Navigation Bar (Mainly) causes this SystemUI problem (Only my observation) But still I bear with the problem as I can't live with out CM or Xposed :(
[Xperia SP Original Android Development] Choucko:
hey dude what are the 644 permissions exactly? is it rw-r-r or something else?
[Xperia SP Original Android Development] sanaka:
rw-r-r
[Xperia SP Original Android Development] TechnoSparks:
I guess we are in same boat. I feel weird that i only rely on two functions only, which is GravityBox's app launcher and resizing the nav bar.

Without those only two I cannot live happily.

But yea really, i have to quickly learn Java, so that i can compile the GravityBox's source for only the function I need. Me is so sad :(
[Xperia SP Original Android Development] RounakCreationz:
I just done some more observation and seen that the navbar edit is causing the problem. :( Hope in newer builds it would be fixed
[Xperia SP Original Android Development] fsyh95:
how to increase the volume,it's too low to hear it.what can i flash via REC to fix it:):)
[Xperia SP Original Android Development] [GER]Roxxor:
Just checked. Csipsimple also works for me.

I used the built in client. Can you check if it works for you?
[Xperia SP Original Android Development] KelleyCook:
Correct.

Here is my understanding of how it works

The FreeXperia team is a group of developers that spend their spare time porting Cyanogenmod over to Sony devices. They develop, submit and build all their code off of the same Github repository that Cyanogenmod uses. Initially FreeXperia will be the only ones to release builds for newer devices.

When a particular device starts working well enough to the FreeXperia teams satisfaction, they will submit a change request adding that device to the CM master build list. And then Cyanogenmod starts nightly builds from the same sources.

HTH
[Xperia SP Original Android Development] knightazura:
Oh yea you r right, in download link there no 327 for our SP :D

Hmm, kernel which same sources with Xperia T and V or ??

Ahh, so eventhough its jump from 4.4.2 to 4.4.4 we just need wipe cache and dalvik??

Haha, everyone always "compare" about FXP and Official CM, but dont worry I never ask about that :D except there are big bang dat make changes in android world lol

One more, FXP released every Monday right? So I can assume that nightly build at Sunday are weekly compile for next FXP release. Correct me if i am wrong :fingers-crossed:
[Xperia SP Original Android Development] DThought:
Thanks for the hint. /data/etc/macaddr does hold my *correct* macaddress. Nevertheless settings does show the different mac address i mentioned before and that different address is used as well, to connect to the access point.
[Xperia SP Original Android Development] deemanthax:
new update released....

is that patch for sounds include in this update???

Changelog cm-11-20140714-NIGHTLY-huashan.zip

stagefright: Fix stub function (android_frameworks_av)

stagefright: Extra checks for HW AAC decoder (android_frameworks_av)

stagefright: Only invoker HW decoder for actual decoding (android_frameworks_av)

stagefright: Correct timescale in MvHd for HFR (android_frameworks_av)

Can't play AAC file with ID3 tag. (android_frameworks_av)

HLS: getDuration should return -1 for live streams (android_frameworks_av)

audio:mute duration at the beginning of the recording (android_frameworks_av)

stagefright: Use 64 bits for type mask in MediaCodecList (android_frameworks_av)

Stop thread before deleting object reference (android_frameworks_av)

stagefright: Correct total duration of HFR clips (android_frameworks_av)

stagefright: remove target specific checks for hfr (android_frameworks_av)

Fix aac decoder flush (android_frameworks_av)

stagefright: Use HW AAC decoder in ACodec if requested (android_frameworks_av)

mediaplayerservice: Untangle legacy callback function (android_frameworks_av)

Add support for MPEG audio elementary streams in HLS (android_frameworks_av)

Audio streaming error when playing a stream that contains "end of file". (android_frameworks_av)

Disconnect the mediaplayer when reset (android_frameworks_av)

Fix systemui crash on boot (android_frameworks_base)

Revert "trebuchet: remove CALL_PHONE permission" (android_packages_apps_Trebuchet)

Revert "Revert "ota: Make sure we don't install on top of an incompatible system"" (android_build)
[Xperia SP Original Android Development] DThought:
No that patch isn't included there. When you visit the gerrit review link (http://review.cyanogenmod.org/#/c/68000/) for that patch, you'll see the text that will show in the changelog: "huashan: audio: enable Dual MIC recording in videos"

also you'll see, that atm that patch isn't accepted into the main code yet.
[Xperia SP Original Android Development] Tomoms:
GPS

Does gps work in CM11?

Thanks ;)
[Xperia SP Original Android Development] DThought:
For me it works fine :good:
[Xperia SP Original Android Development] User013:
I used offical 4.3, now i went back to cm11, i thought there was option to change home settings, like remove search bar, make icons smaller but now i can't find it...

edit:

aha i found it

btw there is a Trebuchet and CM home, is CM Home new launcher? How to enable it?
[Xperia SP Original Android Development] KelleyCook:
Yes the merged msm8x60 kernel is shared with T, TX & V instead of its one-off msm8960t kernel.

You actually don't even need to do that; the CM update script takes care of everything including the required wipes.

The major exception to this rule is if you backlevel to a prior date. Then sometimes things will break due to changes in various database layout (their scripts handle forward changes only). Also GAPPS historically broke going from one major version to another (say 4.2.x -> 4.3.x). Though with Google shift to move most its APIs to Google Play Services, I am somewhat curious if this exception will still apply for 4.4->5.0.

Yes, it should be within 12 hours of newly accepted changes.