yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] pookieguy:
Hi all,

I've been able to replace the hideous white dialer on my S4 Tmobile with previous android versions. I just had to restore entire phone and took that opportunity to update from Tmobile. Found I'm now on kit kat but that has prevented me from successfully changing the stock dialer on this rooted phone.

Can anyone please prove the seccontacts or secphone apks to replace to black? Any other ways to change it from white dialer?

Thanks!

--Sent from Samsung Galaxy S4--

--Sent from Samsung Galaxy S4--
[AT&T LG G3] tankxr:
I forgot to freeze the OTA update on my rooted AT&T g3. Since the update every time I try to add my Google account I get the "couldn't establish secure connection" error message. I've factory reset twice and have cleared the Google services cache several times. Please help me!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] baniaczek:
Don't use. Users reports, that it worse, than before.

Attachment deleted

Old post:

In the old days of WM5 on BlueAngel there was a problem with BT driver:

- it doesn't properly wake up after device suspend/resume

- it was unusable as hands free if device is in the suspend mode.

There is a good fix: http://xdaforums.com/showthread.php?t=267389 but device wakes up randomly.

I have no advanced hands free device (simple bluetrek G2). Could anybody check attached CAB and provide some feedback?

BT is still on after pressing power button on/off

BT device can wakeup BA.

I cann't test more :(
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] motisu:
I may just be thick, but I don't understand what this cab does as opposed to the Big Mike fix, and I don't understand what exactly you want us to test. I have a Motorola HS850 which I use all the time as my hands free device. I'd be glad to test if you explain what you want me to test.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] baniaczek:
cab contains only bthuart.dll (like big_mike patch), It replaces big_mike patch.

It looks, that:

- BT still works

- BT properly wakes up when BlueAngel wakes up

- BlueAngel doesn't wakes up randomly

- after pressing power off: BlueAngel can be woken up using hands free.

I can't check:

As I can understand: advanced hands free can be used to: dial (or redial) using only hands free. I don't know if it was possible without this patch. If yes - I can't check if this possibility still exists.

I can't check quality of the sound.

I can't check if BT stereo headset is still working after using this.

If redial still would be possible, quality would be the same and stereo would work - I would replace big_mike patched bthuart.dll with this one. BlueAngel would't wake up randomly anymore.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cescof:
I've tryng it now, i'll post any feedback later.

Thanks and regards
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kerio:
I've used H1.4.Ban.R1 (lazy to flash new one:)) + NOKIA LD-3W /GPS and BT is working like the old one.

BA wakes up randomly, ..., everything remains the same.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cescof:
To me is no good. Every time turn off/on bt is off. (loke before bikmike) and when my headset is connect it's impossiile to disconnect it . (i've to call and stop calling to disconnect my headset).

For now i coe back to old dll.

Regards.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] baniaczek:
Strange :(

Thanks for feedback :)

I'm deleting it.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Nick the Toll:
baniaczek, while you're looking at BT, let me remind you the problem I have when trying to use a BT stereo headphone with Windows Media (or with another player, for that matter): alas, it doesn't work...

By the way, I have no problem at all with BT when using the same headphone as hand free, or when using a GPS device... the only issue is with music...

Thanks again for your huge work!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chrisstavrou:
Hi baniaczek,

i have tried it and it seems that the problems still exist.

Actually using it over the ROM created by your kitchen, made the use of BT difficult:

- It turns the BT off after the PDA is powered on.

- It turns on the PDA randomly, more frequently than before.

Cheers

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Shift Lollipop Kernel​

This kernel supports only Lollipop AOSP. Should support all roms but not sure about Slim, if it doesn't work for a ROM please upload the boot.img from the ROM and post it here and I will see about adding support. Basically this kernel was developed only for CyanideL ROM but has progressed into a decent standalone kernel from reports as I do not own this device, so I thought I would just go ahead and share it so it was known and people could use it for other Lollipop Roms since I keep the source updated for the ROM I figured a kernel with some features and up to date source would be worth posting. Hopefully you all enjoy it

CPU GOVERNORS: smartass, smartassV2, ondemand, powersave, interactiveX, performance, userspace, zzmoove, wheatley and nightmare

I/O GOVERNORS: noop, deadline, cfq, row, sio

default cpu governor: InteractiveX

default I/O governor: row

F2FS/EXT4

OverClock to 1881

CPU Voltage Control

GPU Step Control

Advanced TCP Controls

Faux Sound Mod

Quick Charge

Compiled with Linaro GCC 4.9.1

Install Instructions: Standard flash in recovery, wiping caches in recommended but usual shouldn't be required

Current version is 3.0

Downloads: Shift Kernel

Thank you and enjoy!!

If you like our work, then maybe you would like to give a small donation or buy me a beer. You know you want to lol :victory:

Donate to @rogersb11

Thank you and ENJOY!!!!!

​

XDA:DevDB Information

Shift Kernel, Kernel for the AT&T Samsung Galaxy S III

Contributors

rogersb11

Kernel Special Features:

Version Information

Status: Stable

Current Stable Version: 3.0

Stable Release Date: 2015-02-19

Created 2015-02-20

Last Updated 2015-02-19
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kizzmiazz:
Nice work here man ?

GS3-T999L : SOKP-MS-04-KK444
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Hey rogersb11. I just installed on my sgh-i747m. Running an alpha self built pacman ROM. I will test it out today and report back results. Thanks for all your contributions in the Dev world. Cheers!!!!

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
exfat?

Thanks! This kernel has been working great on Cyanide L.

Quick question, does it have exfat support built in?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] innocent25:
This kernel is working great on Oct-L
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Top of my head I'm not sure and I'm not by my build machine to check the source. If it's not I can look into adding it tho. I have it in my they kernel source so I'm sure I can port it over
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Thanks. I have a microsd that may be of dubious quality. It works best as exfat. I've found I have to be really cautious with it. I'm pretty sure I didn't try it with cyanide.

Doesn't seem to support exfat, but it's nice and smooth on the official Slim weekly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnnyy9262:
Loving your kernel, hey I am wondering about f2fs, is it new? I tried formating my system and data to f2fs flashed shift v2.2 and didn't boot I tried this on cyanide L and I am a currently on it (ext4), if there are different steps I need to take please let me know other wise I am loving v3!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
You need the kernel changer from the f2fs thread to allow ROM to boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roogerrisboredd:
Would this work for d2tmo?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnnyy9262:
Link me? It would be amazing if actually get f2fs working in lollipop [emoji1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Yes it SHOULD. Comes with cyanide ROM and it's for tmobile as well

F2fs ramdisk support was added in 3.0. I only added it for data and cache tho and that's where the improvements are to be had
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Shift 3.0 bootloops on CyanideL

I've been running CyanideL with the Shift kernel for a couple of months with no problems. The latest version (20150220) bootloops on me, though. I tried a dirty flash, then factory reset but either way it shows the Samsung flash screen, buzzes and then back. I tried flashing Shift 3.0 separately after this happened, as suggested by [MENTION=5315289]TheGeekyNimrod[/MENTION], but that produced the same result. But then I flashed Shift 2.2 D2 over CyanideL-20150220, and now it's booting fine.

I tried to take a logcat while it was booting with adb logcat>logfile but I got the message -waiting for device- and nothing more. The logifle was empty. Is there another way to take a boottime logcat? My recovery is TWRP 2.8.4.0.

Thanks, [MENTION=5554845]rogersb11[/MENTION], for all your work on this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Yea this seems to be a very random issue. Geeky himself has this on a previous kernel I gave him. After failed boot you can boot straight to recovery and pull the last_kmsg. I can't remember exactly the command but a quick search will tell you. That's the kernel log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
3.0 running great on Oct-L. Awesome work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
I tried this but there was no last_kmsg. I did get one from a successful boot with the 2.2-D2 kernel; that one said "no errors" at the bottom. But I guess it doesn't get far enough to even create the kmsg file with the 3.0 kernel. :( The last time I tried it stayed on the Samsung flash screen with the LED pulsing blue for about 10 minutes before I pulled the battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
If it stays on the Samsung screen very long at all then it's just not gonna boot. Well that's unfortunate man, 3.0 is a massive improvement. Not sure how to help you since almost all haven't had this issue. Maybe next build will work for you. Not sure what else I will add but I'm sure I'll find something. Anybody have any requests?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
You're awesome, I know I'll be happy when a new build comes out that works. Fiops please, and I don't know if f2fs support for sdcard would work but that seems like the best file format for an sdcard to me. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
I'll look into fiops. F2fs should work on an sdcard. Kernel supports f2fs cache and data so internal and external should work that way
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
Cool stuff, I flashed the newest twrp recovery and latest modem/baseband NJ1 using Exodus rom from team Vanir http://www.vanir-exodus.net/exodus/d2att/ shift kernel 2.2 works sortof, zzmoove hardlocks the phone and xposed alpha won't work[works on exo kernel]. 3.0 is broken for me still on a clean flash the splash loads this time then after a bit the screen goes black, oddly enough touching the power button causes a vibrate but other then that phone won't wake. Phone is unresponsive from pc side using adb logcat etc when on 3.0 so I don't know how I would report any bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
You can try rebooting into recovery, then in TWRP tap Advanced, File Manager and see if /proc/last_kmsg exists. If it does, use the TWRP file manager to copy it to /sdcard and post it here. Perhaps it will be of use to [MENTION=5554845]rogersb11[/MENTION]. I tried doing that but the boot process doesn't get far enough to generate the last_kmsg file. You may have better luck. I hope you do, for all of our sake.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
[MENTION=5554845]rogersb11[/MENTION]

Is this normal for it to run at default max? http://xdaforums.com/showpost.php?p=59014654&postcount=14
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
Okay found a kmsg, let me know if it's relevant, if not I could install 3.0 and try getting another one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
Unable to use app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
No, that is not

normal. You can check source to see. I'll look into it tho. Without the device things like this may happen sometimes because normally I test for two weeks before I release anything

Thanks. I'll check it later this evening and see if anything of use is in there

Strange. I'll check the source but I KNOW the sound mod is there and enabled. I've had this with boeffla before on my n2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Thanks. I have a feeling that that's why the kernel is unstable on my phone. Lead to a lot of force closures and I had to switch it to version 2, which worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
[MENTION=5554845]rogersb11[/MENTION] if it matters I'm using Shift 3.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
last_kmsg #2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
Hey Rogers, is the latest Cyanide release still using the same kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Yes. I haven't had time for ant kernel work lately at all. My device kernel needs an update and I haven't even started it yet and theme engine is reeking havoc on the status bar at the moment
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDC2389:
Alright, thanks for the update! Have a few bux, I appreciate your work on our phones. Have a good day bud :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flaming_flamingo:
Boot loop with bright flashes

Hello,

I recently tried flashing this rom and all i have gotten is a boot loop and my screen flashing bright white. i have tried everything. i have done every kind of wipe and installed the rom, gapps, kernel multiple time. i am coming off of carbon rom and don't know what i am doing wrong.

thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] $avage$3:
I responded to your same question over in the CyanideL thread

what I didn't ask was...why are you flashing a kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] killablack:
Even if you underclock the cpu the second one will still use the full frequency range up to 1800Omhz ut the first core will be underclocked and follow the frequency table of say 1350 mhz. also I haven't been able to get faux sound to work since the first release. If you do get a chance to look at it can you make sure it's the updated version of the driver with telephony controls please that would make it complete for me. Thanks for your work on the device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
I'm gonna try to work on this kernel this week. You have a link to the updated driver? That could be the issue. CPU I may drop oc support for now since it seems to be the issue to most. Most don't have an issue but when they do it seems to be CPU related
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] killablack:
No rush the kernal runs stable for me. I believe the most up to date driver would just be on the faux sound github which you can be directed to through the app description in Google play store; it's a little beyond my knowledge as if it's the most up to date or not but honeslty any faux sound control would be a good start whether its the newest or not. As for the CPU issue maybe someone with a little more expertise than me can see if there are other problems with the second core other than oc such as if the selected governor is being applied to both cores or not. I hope you don't take these as demands I'm just trying to point out possible flaws I wish I could help more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysix79:
Anyone having issue where the phone doesn't go to deep sleep? Mine just go to minimum speed but not deep sleep. What gov are you guys using. I'm on shift 3.0 and on T-Mobile phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Known issue with new play services. It's all over aosp, not just here lol. Check the wakelocks, you'll see it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] $avage$3:
[MENTION=5554845]rogersb11[/MENTION] does this new play services issue have anything to do with reports of unusually fast battery drain that allot of users are experiencing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysix79:
Ic thank you.. Is that the same kernel wakelock as "PowerManagerService.WakeLocks" 97 percent

I also see WiFi is being used by com.android.pending. google play store by 76 percent
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Power manager isn't actually using that much, basically impossible. Play services is your real issue. Kill that thing with wakelock blocker

Yes, all related
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysix79:
Roger I've reflashed the old shift kernel 2.2 this morning. I didn't really monitor the phone since you told me its common issue for all lollipop. I just checked battery stat this evening and I've seen 5 hrs of deep sleep. I'll will charge my phone fully before I go to bed and restart. I'll report tomorrow what's my finding
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Well it's common BUT not everyone has it. Geeky and I have the exact same device, running exact same ROM and he uses my note 2 kernel and HE had this issue but I myself didn't. It's very strange. Could vary depending on gapps package/ what Google apps you use. I know it's being worked on and there is a 2 part commit to HELP remedy the issue but it's still under review. For sure tho this is a known issue. It's been wreaking havoc on One Plus users
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysix79:
I c. So it could be different from phone to phone.

Here are my findings for other whose having battery drain . Last night before going to sleep my phone was fully charge and I restarted the phone. Just like what I did yesterday and unplug it.

Phone did not go to sleep but it has way better battery life on kernel 2.2 than 3.0. Last night after 7-8 hrs from 100 down to 34 percent battery life . Today with older kernel for just over 7 hrs, 100 down to 78 percent battery life. Nothing is change with the phone beside the kernel and its dirty flash. (Clear dalvik and cache)

It could've have been some random app that got trigger on the background yesterday that causes the big drain on 3.0 kernel. I will stay with the 2.2 for a few days and see how it works .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bschnelk:
Kind of off-topic, but thank you for mentioning this. I've flashed 3 different 4.4.4 ROMs in the last week trying to figure out why my phone suddenly started draining twice as fast as normal. The only thing sucking battery (preventing sleep of any kind) is the SystemUpdateService process that will not go away no matter how many different apps I use to disable the process.

What sucks is that it is probably causing a lot of people to think a ROM is bad when it is just this stupid process screwing everything up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
A couple of questions:

I can't seem to get Fast Charge to stick. If I enable it, after a reboot it shows a Status of Off. Bug?

What are the defaults set to? Maximize performance? Maximize battery life?

Any recommended settings for Scheduler and Governor to maximize performance? Battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Defaults are stock values. What app are you using to set it? That is most likely the issue lol and it shouldn't even need turned on, I thought I just flat out enabled it so everyone had it even if they didn't know because L charges slower than kk did so was basically using this to negate a bug lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
I was using Shift Tools! It has a "Fast Charge" toggle. Should we be using that switch in Shift Tools? Should we ignore it? Can you fix it? What about accessing the phone using USB? I thought when we do that we have to turn off fast charge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
I didn't even know shift tools had that switch haha. It has a lot of features it auto finds, and I have just added specific stuff for my kernels on top. That's why I chose that app as a base even tho the base is old. Fast charge must me auto found, I can look into it tho. I THOUGHT that the new fat charge 2.0, which is what I added didn't need to be changed for USB but I don't have the device so you know better than I would for sure. Can you get me the device path to the file it changes to turn it on and off? If so I should be able to make it stick but it also may reset on purpose if your USB details are correct then it figures when you want it then you turn it on. Idk, you tell me what YOU think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
OK. I installed Trickster MOD, and it's Fast Charge status matches Shift Tools status. Both tools are able to change the status of fast charging, and both tools report the state change.

I don't know anything about fast charge 2.0, but in my testing, while Fast Charge was on, I could not connect to the device through USB. The one thing I don't know how to test is whether it is still fast charging when the Fast Charge status is off.

I would like for the setting to stick, and I would leave it fast charging all the time. I rarely need USB access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mik3di3s3l:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsilx:
will this work

Hello I was wondering does this work with android 5.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Not yet. I have updated the kernel but have not built shift. Geeky will be building tomorrow I think with it inline and if it works then I will build it with the new linaro 4.9.3 I'm using now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireclaw316:
I'm running the unofficial CM12.1 on the SGH-I747. After I install the kernel, the phone boots up, but it shows the lockscreen for a millisecond before rebooting.

XDA Thread(it won't let me upload the boot.img):

http://xdaforums.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
I'm sure it does lol. Sepolicy needs updated in the kernel. I'll try to update it this week
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireclaw316:
Are there any updates regarding being able to install this on CM 12.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Give me the cm12.1 and I'll fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spiffy.sam:
cm12.1

Yea I tried flashing this on cm12.1 and PAC man ROM and it didn't work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
love this kernel so much, waiting patiently for update fix on 5.1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Well I asked for latest cm kernel so I could update the ramdisk AWHILE back, nobody came through so....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hasansabuz:
can i use in d2tmo?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
[MENTION=5554845]rogersb11[/MENTION] currently running cyanide L 5.1.1 can I flash the latest shift kernel 3.0 .....can't wait to run this super awesome Kernel... good work done..thumbs up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
SOMEBODY give me the latest CM 12.1 boot.img and I will update this kernel, that's all I need. I'm too lazy to pull the whole rom and since I don't use or even own this device that isn't much to ask for haha, hook me up so I can hook you up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] $avage$3:
here ya go
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
can you test this? https://www.androidfilehost.com/?fid=23991606952612147
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] $avage$3:
yeppers,lol