Database Develop

[MOD][NS][NS4G]FaceLock for ICS 4.0.3

Hi!
If you miss it the facelock feature from ICS 4.0.3 (NS-NS4G), flash this file and try.
http://dl.dropbox.com/u/54258750/FaceLock (4.0.2 - 235179).zip
md5: 9a143b8cd4213c554cdcd21bc80ac5b2
1. copy FaceLock (4.0.2 - 235179).zip to 'USB Storage'
2. reboot recovery and install
App version: 4.0.2 - 235179, shows 4.0.3 in applications.
Tested, and working, but slow, and the face recognition sometimes is not perfect.
(probably because of the nexus s vga camera)

downloading.. let's give facelock a chance!

Installed on CM9 Alpha17... it works very well, after a few more detections using "improve face detection" option, it recognizes my face almost always

Thanks it works!
It's not perfect, but funny
EDIT:
But I think the recording of a face needs much longer than on a Galaxy Nexus...

Works great on stock. Not that practical, but great for showing off

Took around 30 seconds to record my face for the first time and then tried like 20 times and worked 20 times haha also was pretty fast :S faster than using a pattern for example
---------- Post added at 10:31 AM ---------- Previous post was at 10:22 AM ----------
Oh btw im on beam 4.1.0 with glados 2.3 and i9020A unlocked from factory

Thanks,
works quite nice actually.

Looks like I'm the only one it's not working for!
I can set it up fine, but when I try to actually unlock the phone, it just freezes at the first attempt. No way out but to pull the battery.

everything seems to work perfectly here.. has recognized my face every single time

Awesome, now my nexus s is truly rich with features. Thanks OP.
Sent from my Nexus S using XDA App

This deserves more attention Nexus S users deserve to get the full ICS experience.

Works Great
i9023 Working Perfectly Thanks

works great on stock rom.
thanks :-D
Sent from my Nexus S using Tapatalk

Works, but... hasn't reconigised me once

Psych0Chimp said:
Looks like I'm the only one it's not working for!
I can set it up fine, but when I try to actually unlock the phone, it just freezes at the first attempt. No way out but to pull the battery.
Click to expand...
Click to collapse
It only recognized my face once...

does anyone know if this has been implemented on cm9 a18?

Yes, face unlock is implemented. From Kalim's CM9 thread here.

if it becomes unstable and doesnt seem to work well for some, how would one uninstall it using stock rom?

explorer-10 said:
if it becomes unstable and doesnt seem to work well for some, how would one uninstall it using stock rom?
Click to expand...
Click to collapse
Reflash stock rom, no need to wipe anything, no data will be erased.

It work but don't recognize my face
The vga is too bad

UPDATE! Atrix HD CM10 (RAZR M Port) with working Data and Wifi coming soon!

Link to the development thread:
http://forum.xda-developers.com/showthread.php?p=36557376#post36557376
After mindlessly toying with the RAZR M's CM10 build, and with help from mattlgroff, I was finally able to get CM10 with working data and WiFi to work on our beloved Atrix HD! Just one minor thing I'd like to squash out before I post it here on XDA which is getting usb storage to work. Even if it's just MTP (I may have found a way to get the old USB Mass Storage working if someone would like to link me to a system dump of the AHD's ICS build. This will likely work on all AHD JB builds.)
Here's some screenshots to wet your taste buds.
Note: The data icon doesn't show bars when connected to data but shows 3G, H, and H+, and the WiFi icon will remain gray.
--edit--
Hours of research have given way to a fix for the carrier issue. About to fire up the computer and hopefully get a fully functional CM10 (minus the USB mode) port for the AHD.

Beautiful!
Although the Wi-Fi icon is still grey, are you able to sign into Google services, including Google now?
Sent from my phone.

Not completely sure. Just downloaded the CM10 gapps so I'm about to flash it and continue testing. I read somewhere on here a while back on how to get usb to work but I've been unable to find it for some reason.

Quick Google search brought this up:
http://forum.xda-developers.com/showthread.php?t=1800935
Sent from my phone.

Markyzz said:
Quick Google search brought this up:
http://forum.xda-developers.com/showthread.php?t=1800935
Sent from my phone.
Click to expand...
Click to collapse
I meant getting usb to work at all on the CM10 ports for the AHD. Seems like I was wrong. Devs are hard at work figuring this out for us.

You could always try Gapps4BatakangROMv3. Worth a shot anyway.
http://batakang.com/ftp/Gapp/Gapps4BatakangROMv3.zip

mattlgroff said:
You could always try Gapps4BatakangROMv3. Worth a shot anyway.
http://batakang.com/ftp/Gapp/Gapps4BatakangROMv3.zip
Click to expand...
Click to collapse
Well, that certainly fixed the WiFi icon. Able to get into the Play store and Google Now is functional. Only problem is that com.android.phone crashes when making a call. Hopefully I can get this working or the only way to make a call is to NOT hit okay when it crashes, then hitting okay to hang up lol.

Awesome! Hoping for good news! Keep at it!

I think I may have found a way to make usb work. Cross your fingers.
--edit--
Alright, no usb storage lol. BUT. I was able to stop the phone from crashing repeatedly and you are now able to make calls normally. One last test to make sure market is working as it should and I shall be releasing what I have so far.

Neroga said:
I think I may have found a way to make usb work. Cross your fingers.
--edit--
Alright, no usb storage lol. BUT. I was able to stop the phone from crashing repeatedly and you are now able to make calls normally. One last test to make sure market is working as it should and I shall be releasing what I have so far.
Click to expand...
Click to collapse
--edit--
Thought I had everything up and running. Data, wifi, calling, and market all work. Can't send texts for some reason, though.

Is there any graphics problems as Razr M has a qHD resolution? Thanks for your work,Neroga..

Great progress man, thanks for all the work. Can't wait for it to become a daily driver
Sent from my MB886 using Tapatalk 2

huatz84 said:
Is there any graphics problems as Razr M has a qHD resolution? Thanks for your work,Neroga..
Click to expand...
Click to collapse
Upped the DPI to 320 (came with 240) and no problems at all. Smooth as butter. I passed out after literally messing with it all day, yesterday. Gonna upload what I have so far once I get out of work for people to mess with.
Abu-7abash said:
Great progress man, thanks for all the work. Can't wait for it to become a daily driver
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Hopefully someone can find something I haven't tried to get some kind of signal for texting. Gonna have to make a modded gapps, though. The com.android.phone crashing problem is directly linked to phonesky.apk. Boot up, signal, receive texts, repeated crash and no signal after.
Sent from my Atrix HD MAXX

Any updates?
Sent from my phone.

Waiting on a reply from dhacker. Being a stickler for protocol, I won't post it until I get the okay from him.
Sent from my Atrix HD MAXX

Neroga said:
Waiting on a reply from dhacker. Being a stickler for protocol, I won't post it until I get the okay from him.
Sent from my Atrix HD MAXX
Click to expand...
Click to collapse
That's cool. We're all waiting patiently for his response
Just to clarify in case someone doesn't know what you're talking about, you're asking for permission to post your port of his open source cm10 port?
Sent from my phone.

if it's open source I don't really understand why you want permission from him...

Markyzz said:
That's cool. We're all waiting patiently for his response
Just to clarify in case someone doesn't know what you're talking about, you're asking for permission to post your port of his open source cm10 port?
Sent from my phone.
Click to expand...
Click to collapse
centipedes said:
if it's open source I don't really understand why you want permission from him...
Click to expand...
Click to collapse
He took the time to build it from source which I did not. 99% of the work is his. Seeing as he isn't responding, I may just post it giving him credit with a link to the original thread.

Please please please post it.. I've been religiously checking this thread since I first saw it and the last couple of days have been hell because I know it's so so close.That being said, I'm pretty much begging you to post it. Oh, and is there anything that currently doesn't work right on it or is it now fit to daily drive?

insoundd said:
Please please please post it.. I've been religiously checking this thread since I first saw it and the last couple of days have been hell because I know it's so so close.That being said, I'm pretty much begging you to post it. Oh, and is there anything that currently doesn't work right on it or is it now fit to daily drive?
Click to expand...
Click to collapse
In the process of making a thread on the dev section.
Can't send / receive texts and installing gapps will cause com.android.phone to crash repeatedly. So make a backup of your apks before flashing this.

So bluetooth code is broken?

So from reading just about all the threads in the dev sections, it seems that Bluetooth is something that is inherently broken frome htc? This would explain alot of things...including why my awesome Bluetooth nyko controller doesn't work. lol. Anyone have any input on this matter? And i guess another thing i was curious about is the leaked 4.2 RUU that was posted in the dev section, does anyone know if the Bluetooth is fixed in that by chance? I know that the jump from 4.1.2 to 4.2 was a large improvement of Bluetooth for my nexus.

Bluetooth works just fine for me. Granted all I use it for is the headunit in my car.
Sent from my HTCONE using xda app-developers app

youkosnake said:
Bluetooth works just fine for me. Granted all I use it for is the headunit in my car.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Thats really weird. I always have problems trying to pair any bluetooth controller to the One. They all say they pair but never work in any apps :\

Bluetooth source is botched from HTC just for the Sprint variant. So on stock kernel you'll be fine but until fixed (which I'm working on) all custom kernels you won't be able to use bluetooth for calls. Streaming works fine.
Sent from my EVO using Tapatalk 2

HaiKaiDo said:
Thats really weird. I always have problems trying to pair any bluetooth controller to the One. They all say they pair but never work in any apps :\
Click to expand...
Click to collapse
Bluetooth pairing worked fine for me with my car, and I was able to import all my contacts to the car. Haven't actually used it for an in-phone call yet, but so far no issues. I also haven't rooted or run modded kernel/ROMs.

Bluetooth is only broken on custom kernels. I use viper rom and use Bluetooth all the time in the car for streaming and calls as well as at home with my desk headset from Plantronics.
Sent from my HTC One

HaiKaiDo said:
...I know that the jump from 4.1.2 to 4.2 was a large improvement of Bluetooth for my nexus.
Click to expand...
Click to collapse
This was my experience as well with my nexus s 4G on Sprint. I've had serious low volume issues with my HTC One when trying to connect with the factory bluetooth in my car (2004 330ci). I started a thread ( http://forum.xda-developers.com/showthread.php?t=2266974 ) but have yet to receive any replies. Good luck!
---------- Post added at 11:42 PM ---------- Previous post was at 11:31 PM ----------
thicklizard said:
Bluetooth source is botched from HTC just for the Sprint variant. So on stock kernel you'll be fine but until fixed (which I'm working on) all custom kernels you won't be able to use bluetooth for calls. Streaming works fine.
Click to expand...
Click to collapse
Thanks for working on this! I love this phone aside from this, which is a serious inconvenience. When you say you're working on this, is it a custom rom or custom kernel that you're working on, or just the bluetooth problem specifically? My phone is currently stock, but I'll happily root it if you release a solution for this. Thanks again!

Bluetooth is so slowly for my cell phone.

[ROM][Moved to General Populatiion] [Depreciated]

Moved to General Population for All Variants
Mods Do what you need to do if you want..
Thanks.
http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408​

Guess in going to be the first one

Oh... Yeah... Me second... LOL
Sent from my LG-VS980

Me three ?

Anyone figure out how to download from that link via mobile? I only get ads.

The "download now" button worked for me

I dunno what it is then. Ive tried chrome, stock browser and some ****ty browser from the market. The market browser downloads something but it's only 16mb.
---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------
Got Firefox to work. Thx

KBizzle said:
I dunno what it is then. Ive tried chrome, stock browser and some ****ty browser from the market. The market browser downloads something but it's only 16mb.
---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------
Got Firefox to work. Thx
Click to expand...
Click to collapse
This was discussed in his other thread. Use chrome not chrome beta, long press in the blue download now and open in new tab
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
@optimaprime
Everyone always has to have a first time, I'm proud of you bro.

Bugs?

dooperman said:
Bugs?
Click to expand...
Click to collapse
You can get spray bombs for them, how bad are they?

Lawlrus said:
You can get spray bombs for them, how bad are they?
Click to expand...
Click to collapse
[emoji23][emoji23] sorry for off topic, but I literally LOL'ed when I read this. Back on topic...

Lawlrus said:
You can get spray bombs for them, how bad are they?
Click to expand...
Click to collapse
ROFLMAO
dooperman said:
Bugs?
Click to expand...
Click to collapse
The only thing I see not working is NFC... It don't even turns on so might be something in the device tree. I have never used that feature and may never.
Sent from my LG-VS980

Installed this last night and it feels very snappy, can confirm that nfc doesn't turn on. I do get correct carrier info (Verizon Wireless instead of Verizon)
Edit: no GPS either, showing 0/0 satellites on GPS toolbox

Yeah, GPS Status says no GPS device found on device. Rom runs real nice aside from that.

KBizzle said:
Yeah, GPS Status says no GPS device found on device. Rom runs real nice aside from that.
Click to expand...
Click to collapse
I just now noticed this.. I usually run location on battery saver or high accuracy mode. I will look into it when I get some time.
Sent from my LG-VS980

nobe1976 said:
I just now noticed this.. I usually run location on battery saver or high accuracy mode. I will look into it when I get some time.
Sent from my LG-VS980
Click to expand...
Click to collapse
Not sure if it's fully aosp based or still using cm parts, but it's probably like cm based roms, there's an old commit that needs to be cherry picked forward to get GPS kinda working. Though it's still flaky even with that commit. I have the commits listed on post 2 of that PAC thread, if that's easier than searching JPCs thread for the past where he listed them.
It's the commit for checking if messages are supported or not. Even with that though, GPS will cut in and out in most roms.

Also USB tethering does not work, it says USB not connected. WiFi tethering works though!
As far as the "no GPS found" issue, a rom we had a while back did not have the actual GPS hardware file, after we pulled it from another rom it worked. I forgot where that file is located (/system/etc maybe?), could that be one of the problems?
Edit: /system/lib/ had no libgps, maybe that's where it is supposed to be?

heleos said:
Also USB tethering does not work, it says USB not connected. WiFi tethering works though!
As far as the "no GPS found" issue, a rom we had a while back did not have the actual GPS hardware file, after we pulled it from another rom it worked. I forgot where that file is located (/system/etc maybe?), could that be one of the problems?
Edit: /system/lib/ had no libgps, maybe that's where it is supposed to be?
Click to expand...
Click to collapse
System/lib/lib.utils.so and system/lib/hw/gps.msm8974.so might be gps.generic.so as well.

Fustercluck doesn't work for this ROM, from what I can tell. It hangs on the boot animation.before that everything looked good, but I didn't try GPS or NFC like others reported

KoolBurnX8 said:
Fustercluck doesn't work for this ROM, from what I can tell. It hangs on the boot animation.before that everything looked good, but I didn't try GPS or NFC like others reported
Click to expand...
Click to collapse
This would need reported in the kernel thread so he can see why there is a compatibility issue.

LineageOs 14.1 SM-G920T1 Phone calling not working and can't update Lineage error

Is there a patch for my SM-G920T1 Galaxy s6 Baseband version is G920T1UVU5EC2 or can I have better Lineage Rom for my version also I can't Update the os and when I call people they can't hear or I can't hear them. When you first boot Lineageos 14.1 if you have for metropcs it won't read your sim card so you have to edit the APN so search up for metropcs apn setting.

LineageOS doesn't support T*/W8 devices as of yet. They said they will be trying to add more support soon but as of right now, there is no calling and SIM doesn't always detect.

xJovs said:
LineageOS doesn't support T*/W8 devices as of yet. They said they will be trying to add more support soon but as of right now, there is no calling and SIM doesn't always detect.
Click to expand...
Click to collapse
And that alone is why I know longer build kernels for Lineage. They dont support our device model.

The Sickness said:
And that alone is why I know longer build kernels for Lineage. They dont support our device model.
Click to expand...
Click to collapse
Hi man I was wondering if you could send me a recovery.Img for galaxy s6 sm-g920t1 or I think the sm-g920t would work just fine.

If your LOS 14.1 is distributed by Team Nexus, then here is the wrong place to report bugs man. Go over to www.nexus-roms.eu and report bugs for LOS there from now on.
As for the bugs you asked about:
1) LOS for the S6 isn't official (although they have been approved), therefore, OTA updates do not work (some could say it doesn't work on official LOS software too hahaha)
2) The team are working on call for the G920T/W8 right now. So far, it's not been working, but they are trying hard. Also, I must add that SIM has always been detected for me

Mike.YT said:
If your LOS 14.1 is distributed by Team Nexus, then here is the wrong place to report bugs man. Go over to www.nexus-roms.eu and report bugs for LOS there from now on.
As for the bugs you asked about:
1) LOS for the S6 isn't official (although they have been approved), therefore, OTA updates do not work (some could say it doesn't work on official LOS software too hahaha)
2) The team are working on call for the G920T/W8 right now. So far, it's not been working, but they are trying hard. Also, I must add that SIM has always been detected for me
Click to expand...
Click to collapse
Any update on this? I just installed LOS and yes calls don't work lol.
Sent from my SM-G920F using XDA-Developers Legacy app

H3adru5H said:
Any update on this? I just installed LOS and yes calls don't work lol.
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
There was a new build released today on their website. Yes, there is supposed to be one link. Click the link, choose either RR or LOS. Then, choose your model. If you're running T/W8, choose the one that says fltecan/ltecan, and download both the ROM and the patch file to help with calls. If you're running any other models, then choose the normal flte/lte folder. As of now, the patch does enable call, but for the other person to hear, you must activate speaker phone. 'Mohamad', the guy who works on T/W8 models for the ROMs, is working in a fix for it right now I think.

Mike.YT said:
There was a new build released today on their website. Yes, there is supposed to be one link. Click the link, choose either RR or LOS. Then, choose your model. If you're running T/W8, choose the one that says fltecan/ltecan, and download both the ROM and the patch file to help with calls. If you're running any other models, then choose the normal flte/lte folder. As of now, the patch does enable call, but for the other person to hear, you must activate speaker phone. 'Mohamad', the guy who works on T/W8 models for the ROMs, is working in a fix for it right now I think.
Click to expand...
Click to collapse
I'm jumping on that now. Thanks! How bad is the lag you've experienced so far? Mine was pretty bad after a few minutes.
Sent from my SM-G920F using XDA-Developers Legacy app

H3adru5H said:
I'm jumping on that now. Thanks! How bad is the lag you've experienced so far? Mine was pretty bad after a few minutes.
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Everything is smooth for me. I've never experienced bad lag since their first builds tbh.

Mike.YT said:
Everything is smooth for me. I've never experienced bad lag since their first builds tbh.
Click to expand...
Click to collapse
I'll try reflashing now.
Sent from my SM-G920F using XDA-Developers Legacy app
---------- Post added at 11:42 PM ---------- Previous post was at 11:32 PM ----------
What's the difference between the flte and lte can? I believe I'm going with the lte can correct?
Sent from my SM-G920F using XDA-Developers Legacy app
---------- Post added at 06:34 AM ---------- Previous post was at 05:42 AM ----------
Mike.YT said:
Everything is smooth for me. I've never experienced bad lag since their first builds tbh.
Click to expand...
Click to collapse
Alright, flashed. Yes, everything is much smoother. Also, calls are working for both the earpiece and speaker for me. Two things though.. the capacitive back and menu buttons don't work. Had to enable to onscreen buttons. Secondly, I don't have root. Trying to enable it in the developer options and it only gives me an option for ADB. I'm gonna try flashing SuperSU.

H3adru5H said:
I'll try reflashing now.
Sent from my SM-G920F using XDA-Developers Legacy app
---------- Post added at 11:42 PM ---------- Previous post was at 11:32 PM ----------
What's the difference between the flte and lte can? I believe I'm going with the lte can correct?
Sent from my SM-G920F using XDA-Developers Legacy app
---------- Post added at 06:34 AM ---------- Previous post was at 05:42 AM ----------
Alright, flashed. Yes, everything is much smoother. Also, calls are working for both the earpiece and speaker for me. Two things though.. the capacitive back and menu buttons don't work. Had to enable to onscreen buttons. Secondly, I don't have root. Trying to enable it in the developer options and it only gives me an option for ADB. I'm gonna try flashing SuperSU.
Click to expand...
Click to collapse
Flte = flat, as stated by the F. I'm sure you can figure out what the other one is for. Also, tell me your secrets!! It doesn't work in the earpiece for me.
The hardware keys don't work? Strange. They work for me. Maybe try reflashing if it really bothers you.
Root isn't built in in the first place lol

Alright, SuperSU from here flashed through TWRP from this link worked beautifully.
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.80-201705171619.zip
Now just gotta figure out how to get my buttons back. This is awesome!
---------- Post added at 06:49 AM ---------- Previous post was at 06:47 AM ----------
Mike.YT said:
Flte = flat, as stated by the F. I'm sure you can figure out what the other one is for. Also, tell me your secrets!! It doesn't work in the earpiece for me.
The hardware keys don't work? Strange. They work for me. Maybe try reflashing if it really bothers you.
Root isn't built in in the first place lol
Click to expand...
Click to collapse
Hmm.. well that might be the factor as to why my earpiece works. I didn't download and flash the flat version LOL I got the zeroltecan version haha.

H3adru5H said:
Alright, SuperSU from here flashed through TWRP from this link worked beautifully.
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.80-201705171619.zip
Now just gotta figure out how to get my buttons back. This is awesome!
---------- Post added at 06:49 AM ---------- Previous post was at 06:47 AM ----------
Hmm.. well that might be the factor as to why my earpiece works. I didn't download and flash the flat version LOL I got the zeroltecan version haha.
Click to expand...
Click to collapse
wtffffffff???!11!1 I'm pretty sure the lte version would've given you a script error, but I mean whatever. As long as it works!

Mike.YT said:
wtffffffff???!11!1 I'm pretty sure the lte version would've given you a script error, but I mean whatever. As long as it works!
Click to expand...
Click to collapse
I probably didn't get a script error because I flashed the international version of TWRP instead of the g920t version lol works consistently too! Made a few calls to make sure it wasn't bugged.
Sent from my unknown using XDA-Developers Legacy app

H3adru5H said:
I probably didn't get a script error because I flashed the international version of TWRP instead of the g920t version lol works consistently too! Made a few calls to make sure it wasn't bugged.
Sent from my unknown using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wait, just to be clear, you're running a G920T, with LOS, and people can hear you with and without speakerphone on?

Mike.YT said:
Wait, just to be clear, you're running a G920T, with LOS, and people can hear you with and without speakerphone on?
Click to expand...
Click to collapse
Correct

H3adru5H said:
Correct
Click to expand...
Click to collapse
That is so weird.. I might try that tomorrow. I'll keep in touch
---------- Post added at 06:14 AM ---------- Previous post was at 06:08 AM ----------
H3adru5H said:
Correct
Click to expand...
Click to collapse
Does the audio go both ways? Meaning if they call you, w/o speakerphone they can hear you, and when you call them, w/o speakerphone they can hear you?

Mike.YT said:
That is so weird.. I might try that tomorrow. I'll keep in touch
---------- Post added at 06:14 AM ---------- Previous post was at 06:08 AM ----------
Does the audio go both ways? Meaning if they call you, w/o speakerphone they can hear you, and when you call them, w/o speakerphone they can hear you?
Click to expand...
Click to collapse
I haven't had anyone call me so I don't know if anyone is able to hear me. I only called my voicemail and checked for earpiece and speaker audio.

So in dire hopes of moving to the OS that my S5's have had for a while (!!!), I did exactly what H3adru5H said he did - I have an SM-G920T, but I applied (well, upgraded, technically) the international version of TWRP on my phone and then flashed the Edge version of the ROM he did (not the "flat"). Similar results - TWRP works great. ROM worked but no buttons. Sound was a problem (for calls) - it would work for Hangouts (I used to have Google Voice/Sprint integration, so I'm still stuck on Hangouts), and then it would stop. Earpiece made no difference. Also had the root issue - applied the SU package listed - seemed to be fixed. Then, because I had a Nandroid backup and a STRONG desire to stop being the last &*%(# Galaxy owners on earth to use Nougat, I see the "Testing" folder with a file called ResurrectionRemix-zero-multitarget-2017-05-28_2124.zip and think - yeah, I gotta try that. I dirty flashed it and it fixed the button issues - they came back, but the audio was no better. I don't recall if I tried patching the audio again - it was getting late and I needed to restore so I had a phone when I woke up.
Point is - I followed what sounded like the exact same steps as H3adru5H did on my SM-G920T (currently running MM XestroLite), but I basically didn't have functional call audio - toggling speakerphone didn't seem to help. If I could even get Hangouts sound to work reliably I'd be okay - I don't really use the native phone number or app.
I will say I'm somewhat confused by the instructions to use the "zerofltecan" version of the ROM and not the "zerofltexx" version, since technically I believe the SM-G920T would be zerofltexx, not zerofltecan (which is the Canadian version, I believe). I realize there was no sound patch for the "zerofltexx" version, so I had to use zerofltecan, but I am correct, right? All other things being equal, the SM-G920T would be zerofltexx, right? I notice that people lump the "T*/W8" together a lot - I don't know if it means they're really pretty much the same (the specs seem the same- bands might be different, though).
Soooooooooooooooooooooooooooooo close. Oh God, please let this get fixed. And then it's the last Samsung ever for me.

blautens said:
So in dire hopes of moving to the OS that my S5's have had for a while (!!!), I did exactly what H3adru5H said he did - I have an SM-G920T, but I applied (well, upgraded, technically) the international version of TWRP on my phone and then flashed the Edge version of the ROM he did (not the "flat"). Similar results - TWRP works great. ROM worked but no buttons. Sound was a problem (for calls) - it would work for Hangouts (I used to have Google Voice/Sprint integration, so I'm still stuck on Hangouts), and then it would stop. Earpiece made no difference. Also had the root issue - applied the SU package listed - seemed to be fixed. Then, because I had a Nandroid backup and a STRONG desire to stop being the last &*%(# Galaxy owners on earth to use Nougat, I see the "Testing" folder with a file called ResurrectionRemix-zero-multitarget-2017-05-28_2124.zip and think - yeah, I gotta try that. I dirty flashed it and it fixed the button issues - they came back, but the audio was no better. I don't recall if I tried patching the audio again - it was getting late and I needed to restore so I had a phone when I woke up.
Point is - I followed what sounded like the exact same steps as H3adru5H did on my SM-G920T (currently running MM XestroLite), but I basically didn't have functional call audio - toggling speakerphone didn't seem to help. If I could even get Hangouts sound to work reliably I'd be okay - I don't really use the native phone number or app.
I will say I'm somewhat confused by the instructions to use the "zerofltecan" version of the ROM and not the "zerofltexx" version, since technically I believe the SM-G920T would be zerofltexx, not zerofltecan (which is the Canadian version, I believe). I realize there was no sound patch for the "zerofltexx" version, so I had to use zerofltecan, but I am correct, right? All other things being equal, the SM-G920T would be zerofltexx, right? I notice that people lump the "T*/W8" together a lot - I don't know if it means they're really pretty much the same (the specs seem the same- bands might be different, though).
Soooooooooooooooooooooooooooooo close. Oh God, please let this get fixed. And then it's the last Samsung ever for me.
Click to expand...
Click to collapse
T/W8 use zeroflte/ltecan because the guy who is working on the audio fix, Mohammad, has a Canadian model. Canadian model and T-Mobile models use the same Audience chipset which is used for calls. Other models have different audio chipsets. Also, don't use international TWRP and flash the ROM you're not supposed to. It'd just mess everything up, like the buttons as you mentioned.
The newer builds are much more simple, as they'll be multi-target, meaning one zip for either LOS or RR can be used for any model. As long as you have the latest TWRP, it'll use AABS, which is an automated system which scans for what model you have and determines if it needs to flash any patch. If it does, it'll do it during the install process. It's very cool. The test builds have this now and it works well. I'd recommend waiting for the next stable builds though. By then, Mohammad would probably have call working 100%.