yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] avs333:
No, I didn't touch the surfaceflinger code at all. Instead, you have to compile it with

LOCAL_CFLAGS += -UQCOM_HARDWARE

in those surfaceflinger makefiles I listed (as -DQCOM_HARDWARE is now set in global cflags), just to be able to boot! I haven't tested the audio-caf code much yet, but it looks very promising to me personally as I'm going to add direct 96/24 playback in my AndLess app now.

vitaliy_y, yes, exactly... the mako's camera header too. I'll set up a github branch a bit later this week, as franciscofranco suggests, but no more changes, really!
[Nexus 4 Original Android Development] OldDroid:
i will try to compile it using aosp, lets see if support has been added to it already :)

EDIT: not without caf-repos from cm ^^
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Great news!

At last some real developers making nexus 4 owners happier :)

I would like to support this , where i could donate?

Also, is it safe to start using now? Which method to use?

Thanks!
[Nexus 4 Original Android Development] OldDroid:
ok got it,

from where you get the audio-caf source and the display-caf source?

some provided links would be good ^^

PS: sry im new to n4 development :P
[Nexus 4 Original Android Development] avs333:
I used audio-caf from cm10.2 as a base, because new codeaurora ones aren't compatible with libcsd-client for n4 (not a real problem, though).

And I _didn't_ try porting display-caf (no TARGET_QCOM_DISPLAY_VARIANT was set)!!

My tree is in total mess for now, need to tidy up before setting a github branch...
[Nexus 4 Original Android Development] adityaxavier:
Hmm, tried compilling the same with CM10.2 and i get the error :-

'SNDRV_COMPRESS_METADATA_MODE' was not declared in this scope

The SNDRV_COMPRESS_METADATA_MODE is not mentioned in the kernel. It has to be in /include/sound/compress_offload.h

and sound/core/pcm_native.c

How did you get it to compile and which version of kernel did you use, and which Audio-caf did you use ?
[Nexus 4 Original Android Development] OldDroid:
while compilig it returns an error about usbaudio in ALSAAudioHardware.h ...

you need to re-define the value in Android.mk for the flag for usbaudio...

because its set to true by default
[Nexus 4 Original Android Development] avs333:
I used cm-10.2 audio-caf & kernel. Sorry so much for not uploading the sources yet, just need to get cm10.2 and patch it anew to sort out my stuff that doesn't really matter for this purpose :( ...

1. Yes, you need to "#define SNDRV_COMPRESS_METADATA_MODE _IOW('C', 0x99, int)" in kernel's compress_offload.h just to build with compression support now.

2. Could it be because of this commit? I had no problem compiling usbaudio before.

3. Uhh. Forgot a patch for devices/lge/mako/audio_policy.conf, to enable incall recording! Please find it attached...
[Nexus 4 Original Android Development] OldDroid:
yup ;)

the commit causes the build to fail ...

thx for the tip ^^

wel i got cm-10.2 compiled now :D

lets test cafaudio :P

EDIT: Looks good to me ^^

no problems with new audio hals, usbaudio working aswell, headphones/headset - fine aswell, voice recording on call - fine, enhanced audio quality - yup, mics, working :D
[Nexus 4 Original Android Development] iplexus4:
OldDroid, maybe you can compile latest paranoid android? will be great
[Nexus 4 Original Android Development] OldDroid:
So i discussed with my Team, MaclawStudios!

im done with CM-10.2-CM, and we thought over giving it a jenkins kick for automated weekly builds on our servers ;)

for those who are interested in keeping up to date ofc ^^

i will put all my config stuff and so on my github tonight, including kernel sauce!

(audio-caf source, my vendor aswell)

BTW, on cm-10.2 the Android.mk's dont need to get updated flags ;)

Regards,

OldDroid
[Nexus 4 Original Android Development] iplexus4:
OldDroid, any news? can't find any rom from you or MaclawStudios
[Nexus 4 Original Android Development] meangreenie:
Hope this thread doesn't die away, sound quality for me is the last unsolved issue on n4, yes viper ect do an amazing job at cleaning up the audio but need half decent input to be most effective.

This seems the last hope.
[Nexus 4 Original Android Development] adityaxavier:
QCOM Audio Integration

Hi guys, i have successfully integrated and been testing QCOM Audio using CM Repo.

You can find the my repo at http://github.com/adityaxavier/android_device_lge_mako

Issues found :-

1. Well known issue, found also with Sony :-

cannot open device '/dev/snd/pcmC0D0p', errno 16

Call in between of using headphone has the above error and device is crashes.

2. Audio volume is horribly low for Speaker, and there is an echo when using speaker for calling.

Let me know if there is any thing else which might fix it.

[MENTION=3292224]franciscofranco[/MENTION] i believe there are a bunch of fixes which need to be done towards LPA and compression.

Similarly, was compiling your kernel and it needs "msm_hdmi_modes.h" in /include/video/

Would let you guys know if i find some solution for the above problems.
[Nexus 4 Original Android Development] OldDroid:
weired, works here ;)

aswell kernel needs caf patches which are requiered to work without problems, i got no device crash or anything like that,

as i got no error from logcat
[Nexus 4 Original Android Development] adityaxavier:
Can you point me towards the CAF Patches you are referring to ?

Similarly, did you find the issue of low volume and echo problem in speaker mode ? If so any solution for it ?
[Nexus 4 Original Android Development] adityaxavier:
Just took a look at your repo. The Kernel is just pure CM with Compress flags right ?

Could find the CAF Patches you were directing me towards..
[Nexus 4 Original Android Development] vetzki:
First, thanks for your repo.

I picked your commits (lge-kernel-mako, hardware_qcom_audio-caf, device_lge_mako. I dont need the vendor and manifest stuff, do I?) and compiled cm with them. I think it works but I've one issue: If I take a screenshot while listening music the phone reboots. Any suggestions?

also while listening to music and i get a call I get a reboot when turning music on again after the call
[Nexus 4 Original Android Development] adityaxavier:
Thats exactly what i was referring to. But weirdly, dirty flashing a stock CM is still giving me the same issue.

Try the same thing on stock CM. I believe it has something to do with the Headphone Jack's Interupt.

Let me know if you find anything.
[Nexus 4 Original Android Development] vetzki:
Maybe a cm bug? But i don't read anything about this in cm thread, so i think it isn't one.

I test again with stock cm and maybe another build with new driver.
[Nexus 4 Original Android Development] adityaxavier:
Hi, I tested it with the Stock CM there wasn't any problem with it. I guess it has to do something with my BoardConfig.mk

Build and tested around 15 builds today.. :(

But at the same time i found many more fixes which should have been done, would upload my new config soon.

The weird part is, its the same Audio config being used in Oppo Find5. But there are no problems there.
[Nexus 4 Original Android Development] avs333:
Yes, on their last kernel. That is, the screenshot app tries to play some clicking sound after capturing (or phone.apk takes some actions after the call), but your music is playing or is going to be played.

Seems to be their recent kernel patches: I took a kernel from the rom I posted before and it worked like a charm, no such reboots.
[Nexus 4 Original Android Development] avs333:
Upd

That's it.
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Hey guys.

So when we can expect public release? Can't wait for it. Thanks
[Nexus 4 Original Android Development] vetzki:
Thanks. Can you maybe upload the whole msm-pcm-q6.c file?
[Nexus 4 Original Android Development] avs333:
Here's the complete sound/soc/msm directory I use (it also includes several recent patches from codeaurora).

Hope it'll work with their new builds, I didn't sync cm10.2 repo for some time.
[Nexus 4 Original Android Development] raz123:
Pardon my ignorance, but does this "fix" the broken echo cancellation / noise suppression on the MIC stream?
[Nexus 4 Original Android Development] ADJack:
It'd be appreciated if someone could release a new build for the willing flashers;

If it's in a state where the fundamentals are stable - give us a chance to help test it, please and thank you!

avs333 thanks for work:good:
[Nexus 4 Original Android Development] avs333:
You mean voip stuff, don't you?

I believe we have to setup the tabla codec for that. And it was the first thing I did albeit with no success, e.g. replacing 3 different setups, Sony Z, Htc One, and LG optimus G. Each time, something's gone really wrong, yet it _did_ work anyway. No sip or whatever but there _was_ the sound after rather quick 'n dirty mods so may be we'd better test that code, if it does indeed work on their devices.
[Nexus 4 Original Android Development] ObihoernchenDE:
Any news here? Really hope to see some Cm builds with this change soon.
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Cmon guys... Who i need to buy a beer to finish the job? :)
[Nexus 4 Original Android Development] pvkanjiyani:
Hi avs333

Great job

Dropbox link not work

Can u create mirror?

Thanks
[Nexus 4 Original Android Development] skvalex:
http://callrecorder.skvalex.com/update_mako.zip
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Hey skvalex,

Could you be more specific, is this vanilla 4.2.2 with new audio driver?

Thanks.
[Nexus 4 Original Android Development] ramkumar2000:
I know that post says devs only..i went through all the posts and have a question what exactly will this mod fix...? and is it android version specific (4.2.2 or 4.2.3) ?
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Build the Skvalex uploaded is 4.3 JWR66V. Just extracted build number. Anyone tester it already?
[Nexus 4 Original Android Development] skvalex:
Read the first post, this is mirror of avs333's build.
[Nexus 4 Original Android Development] gqcJYb3UN8xSIWNUy2xX:
Hey Mate,

Could you do your magic to 4.2.2 and make your build?

4.3 is buggy.

Thanks!
[Nexus 4 Original Android Development] avs333:
Sorry, no sound _at all_ if I do that with 4.2.2 (didn't try 10.1.3 though).
[Nexus 4 Original Android Development] pvkanjiyani:
hi avs333

is this mod apply to stock 4.3 JWR66Y ?

can u provide flashable zip for stock 4.3 JWR66Y ?

Thanks
[Nexus 4 Original Android Development] sdmeller:
I'm running this ROM for two days, yesterday it performed flawlessly, but today I'm experiencing numerous freezes and reboots. ;(

Rebooting when I'm trying to switch on Bluetooth, when I'm attaching headphones cord and when opening various media programs (MX player, Apollo, etc). Reinstalled the ROM couple of times after full cache and partitions wipe, without any luck.

Yesterday recording from line was perfect, almost bought the Callrecorder.

Keep it going, guys.

Огромное спасибо и успехов. Очень обнадёжили.
[Nexus 4 Original Android Development] Xoib:
Do you have any relevant logs ?
[Nexus 4 Original Android Development] sdmeller:
Sorry, I don't. This idea didn't cross my mind...

Wiped device and installed the stock ROM for now.
[Nexus 4 Original Android Development] pvkanjiyani:
i have flashed update mako.zip

sound was buggy

i attached logcat

plz do the need full

thanks
[Nexus 4 Original Android Development] womanizerzz:
nothing new
[Verizon Samsung Galaxy S 4] bunklung:
I accidentally accepted the OTA update (because it f*cking pops up every 5 minutes).

The phone rebooted into recovery to apply the update, but I pulled the battery.

I am not rooted and running stock. I just want to keep the old rootable/unlockable firmware in place.

How can I stop this update from applying? Every time I restart the phone it jumps into recovery to apply this update. Is there a way to stop this or am I doomed?

I can get into odin mode, but when I try to load recovery it tries to apply the update.
[Verizon Samsung Galaxy S 4] hexitnow:
I dont know if it will work but Boot to odin decline it and see if it will boot normally. If it works youll have to root and then freeze or rename sdm.apk to stop it. The ota data is located in data/fota if you want to delete it. If none of that works you can always try reflashing the mdk image.
[Verizon Samsung Galaxy S 4] Surge1223:
Wait if it was me, I would get into odin and flash the stock mdk tar image.,,,
[Verizon Samsung Galaxy S 4] hexitnow:
if he can get the phone to boot normally flashing mdk would be unnecessary. Could end up being the only way though. Wish I could say ive been in this situation to post a definitive answer but I havent.
[Verizon Samsung Galaxy S 4] Surge1223:
He isnt rooted though, so would have to root right away. If he rebooted before the update started deleting/patching files and changining permissions then it might be ok. I just would rather have no chance of the update patching the recovery or the kernel. The odin image would format the partitions and would delete the update it shouldny brick the phone because the bootloader and firmware arent patched until literally the screen shows 95.39% of the update is complete.

set_progress(0.953849);

ui_print("Patching hidden files...");

ui_print("Patching NON-HLOS modem image...");

apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name

Etc..etc
[Verizon Samsung Galaxy S 4] hexitnow:
And rooting is a long process? Hes going to have to root regardless if he wants to cancel it out. No reason to take an extra step to do the same thing.
[Verizon Samsung Galaxy S 4] Surge1223:
I agree, more often than not your suggestion would be sufficient. I guess its just personal preference.
[Verizon Samsung Galaxy S 4] Obsidian_soul:
Boot and pull the battery at the same place you did before, after about 9 or 10 times the phone will tell you update failed. Then root immediately. Do not pass go do not collect $200 :D
[Verizon Samsung Galaxy S 4] hexitnow:
I hear ya there.
[Verizon Samsung Galaxy S 4] bunklung:
All,

Thanks for the responses. Booting into ODIN did not stop the recovery install OTA loop.

I used the nowipe Odin image and all is well:

http://xdaforums.com/showthread.php?t=2301259

Still on MDK!

I took the extra steps and rooted the phone and renamed/deleted:

/data/fota contents

FWUpgrade.apk

FWUpgrade.odex

SDM.apk

SDM.odex

LocalFOTA.apk

I installed a custom recovery and then unrooted the phone. Thanks everyone. I hope this helps someone in a similar situation.
[Verizon Samsung Galaxy S 4] hexitnow:
Wasnt for sure if the odin decline would work but if it would have it would of saved you a lil bit of time. Glad you got her up and running.
[Verizon Samsung Galaxy S 4] Party_Grunt:
Im sorry for the several month bump, but can anyone confirm this will work for stock ME7 with the new OTA update. I just put myself into the same situation as the OP.
[Verizon Samsung Galaxy S 4] Surge1223:
Should work. Just boot into odin mode and either flash the ME7 factory restore image or the no-wipe ME7 image. But if you really wanted to impress the ladies you could flash the sch1545 pit file. But if you don't know what the pit file does then use one of the first two suggestions.
[Verizon Samsung Galaxy S 4] Party_Grunt:
Thanks, it did work. Unfortunately the last time this happened I was on vacation with no computer available so I was forced to take the OTA update or have no phone for two weeks. I had only rooted the week before and had not gotten around to putting in a custom recovery and bootloader, so I was SOL. Didn't even know root had been found for ME7 until last week. My timing seems to suck on this.

Now time to root and delete the upgrade files.
[Nokia Lumia 920] faroid:
Hi,

Would an unlocked Lumia 920 from amazon work on Virgin Mobile in the US?

Thanks
[Nokia Lumia 920] Solarenemy68:
Virgin Mobile USA is a CDMA provider (uses Sprint's network) and thus does not support GSM devices (the ones that use SIM cards).

Basically, you buy a phone; activate it via MEID; and add airtime with a card.

In short the Lumia uses a SIM card and will only work on a network that uses a SIM card as well.
[Nokia Lumia 920] faroid:
I see. Thanks!
[Asus  Eee Pad Transformer Prime] cBirdR:
I'm in a bootloop mentally and technically! I've spent days trying install Twrp, searching the forum, watching videos... Think I've tried most guides two or three times w/o success. From GooManager/Install OpenRecoveryScript it starts downloading it and then aborts w/a false MD5 blob pop-up. When I tried to install directly I had valid a MD5.

This is not a very helpful description of the problem but I'm so brain-drained that I really can't recall all the different things I've tried. Amazed I've not bricked the thing! Am just hoping someone can point me in the right direction.

TF700T, v.4.0.3, Kernel 2.6.39.4.

I just checked the posts "suggested" when I began mine and I've been to them all except the one about using motochopper to root and then using GooManager to install Twrp recovery. I'm already rooted. Should I unroot and reroot w/motochopper?
[Asus  Eee Pad Transformer Prime] flumpster:
Wrong forum mate. This is the tf201 forums.
[Asus  Eee Pad Transformer Prime] cBirdR:
Well, you can see I've verified my state of muddle. Sorry. Thanks.
[Asus  Eee Pad Transformer Prime] thepianoman77:
You probably didn't unlock the tablet. ...

---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------

Unlock bootloader
[Verizon Samsung Galaxy S 4] dmt010:
Since the bootloader is still unlockable, what are your thoughts on the continual development of ROMS, etc on the S4 ? Do you feel that future of S4 development is doomed? :( I recently just purchased my s4 and was one of the lucky few who were able to unlock theirrs prior to the mess. However, now I feel that I might have regretted buying one.

Thoughts?
[Verizon Samsung Galaxy S 4] brycekerr:
Esquew me? Me no thinks it's unlockable ;)

Sent from my SCH-I545 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S 4] Eric214:
I think you meant that you rooted it and got custom recovery installed on the pre-updated MDK. No one has unlocked the bootloader on any S4 came with it locked.
[Verizon Samsung Galaxy S 4] najaboy:
There never was an unlocked bootloader save for the developer edition only available direct from Samsung.

Development for the i545 is far from dying if you look through the forum. The fact that the bounty for root and recovery on ME7 is several thousand dollars should be telling.
[Verizon Samsung Galaxy S 4] hexitnow:
I agree. This is one of the most popular devices out at the moment. I dont see development dying out anytime soon.
[Verizon Samsung Galaxy S 4] IamPro:
Its fine at the moment and in the near future but could see it lose some people once Note 3 and other devices come out esp if bootloader exploit isn't found on new update :(
[Verizon Samsung Galaxy S 4] theboo7:
There will always be TW & cm ROMs. I think the question should've been "How long until no one has a mdk device?" Unless a new exploit is found of course...
[Verizon Samsung Galaxy S 4] Naddict:
Have you looked in the development sections to see that there are plenty of developers committed to the furthering of development?

Have Faith
[Verizon Samsung Galaxy S 4] brycekerr:
I agree this may be the only problem... As people lose devices and get warranty replacements with the new firmware the development will slowly die off with no unlock available

Sent from my SCH-I545 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S 4] bajasur:
You bring up a good point... buy a very good case for your phone! At this point if you crack the screen, water damage, etc... you would be screwed and forced to stay stock me7 or sell your refurbished phone
[Verizon Samsung Galaxy S 4] heath2805:
Im there now had to order a new one. Mine seems fried and wont connect to LTE with new sim and everything. My luck the new one will be on ME7 :(
[Verizon Samsung Galaxy S 4] bajasur:
That's a bummer.. sorry man. Just have to keep praying someone will unlock this thing...
[Verizon Samsung Galaxy S 4] gorillafist:
I assume the devs that have a verizon s4 themselves will continue to develop for the phone. Also it is possible to use some roms cross carrier if you use a verizon kernel and change the apn.
[Verizon Samsung Galaxy S 4] theboo7:
This. But there's evidence all around (check forums) that devs tend to stop developing for devices with to small of a user base.
[Verizon Samsung Galaxy S 4] hexitnow:
True but there is definitely not a small user base for the s4. Its one of the most popular devices at the moment.
[Verizon Samsung Galaxy S 4] Erievon:
Even if people start breaking/losing their MDK phones, there's still GPE and Dev versions. Should still see development for those, which will be of help to us MDK folks as well.

If you end up having to exchange it, and you get an ME7, could always sell it and put that cash towards a Dev edition as well.
[Verizon Samsung Galaxy S 4] Chris123NT:
GE phones are fine and dandy but none exist for VZW, just like VZW has no nexus phones, because they want complete control over the devices and the software.

I currently have an S3 and when my contracts runs out I will either move to another carrier and buy GE phones or buy Dev phones off contract for verizon, but I'm more inclined to go elsewhere and go with GE phones.
[Verizon Samsung Galaxy S 4] Dubbsy:
When it's announced(hopefully) I'll be ordering my developer edition note 3. As far as the gs4 goes, I only know of 1 developer who stopped developing for the gs4. No one else who has started has quit.

sent from my Verizon Galaxy s4
[Verizon Samsung Galaxy S 4] mlin:
I've had similar concerns. I took it as a reason to learn some of this stuff on my own. I've been building cm 10.2 from source to start. That said, I'm less concerned about development now but I will continue to learn how to do as much as I can on my own. I just hope I never physically damage the phone beyond usability. This is the first time I've had a case on a phone. I hate cases but it's worth reducing the chance of a cracked screen.
[Verizon Samsung Galaxy S 4] bajasur:
I want to hope team synergy has something major up their sleeves for us... trevE is literally a genius so I'm anxious for an announcement from that crew.
[Verizon Samsung Galaxy S 4] crystal.oman:
I hope find solution for your problem
[Verizon Samsung Galaxy S 4] dmt010:
I have faith man. Looking forward to KitKat.
[Verizon Samsung Galaxy S 4] trook:
Kit kat has insane security built in. Like root seek and destroy security. It's on the main page of the xda website. I think android as a whole is doomed. We always find a way around it but dude, do they really care that much? I've begged, pleaded, tried to reason with Verizon and they just don't care. Someday it will cool off but right now Google and Verizon and probably every other carrier are on a rampage it seems like. What to do? No LTE on the oppo n1? Wtf is that? I'm sad and angry and I still have a gnex if it gets much worse. But I'm still not giving up.
[Verizon Samsung Galaxy S 4] jh64dsb877r:
How would they keep all the government-approved backdoors if everyone could freely modify their phone? :p
[Verizon Samsung Galaxy S 4] udg21:
i agree with you on that
[Verizon Samsung Galaxy S 4] joshm.1219:
The enterprise companies who want secure smartphones are a hell of a lot bigger than the open source community, that's why they do it.

Sent from the 215
[Verizon Samsung Galaxy S 4] tkacer:
^^true dat - just follow the $$$
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
Google is also giving out bounties to any developers who finds any security flaws in its android system, I think I read someone got $50,000 from google. The future of unlocked bootloaders are slim.. Look at the development page of the att note 3. There's nothing going on in there.