yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] AptLogic:
Not quite yet. See the problem with getting fingerprinting to work is I have to first somehow get this Settings app (ported from a Nexus 5 with no fingerprint support) to recognize and accept the registration and use of fingerprints.

After that, I'd have to somehow get the also-fingerprint-unsupported SystemUI/Keyguard to accept fingerprinting as a lock method, and get it to correctly "communicate" with the fingerprint driver in the Kernel.

So obviously its not as simple as slapping a fingerprint HAL onto the thing, so it will take a rather long time to get working. I'll try nonetheless, but I'm not sure what my results will be.
[AT&T Samsung Galaxy S 5] Suburban Afro:
Even better! Thanks, I didn't notice.
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] have you figured out nfc yet?
[AT&T Samsung Galaxy S 5] AptLogic:
No, but I'm working on it.

No matter what I try, the option just doesn't come up in the Settings like its supposed to. I've even tried replacing the drivers with the ones from the Nexus 5, but no dice.
[AT&T Samsung Galaxy S 5] arrmo:
Hi,

Anyone else finding that Settings crashes when trying to go in to the Battery settings?

Thanks!
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah that's a known bug, full disclosure at this point it also crashes when you try to view the data usage.
[AT&T Samsung Galaxy S 5] arrmo:
NP! Just in case it was me, or you didn't know about it. No biggie.
[AT&T Samsung Galaxy S 5] AptLogic:
Okay so I made some progress on the NFC issue... I have been able to track the issue down to the NfcNci Application that comes with the S5 Stock OF3...

When it crashes, the resulting logcat displays a "java.lang.NoClassDefFoundError: com.android.nfc.NfcService$6", and then the standard crash log, blah blah.

But what's interesting is, upon decompiling the NFC app, the NfcService$6.smali file is right there!

Hoping someone smarter than me in this regard can step in and point me to a solution... I can provide any necessary files.
[AT&T Samsung Galaxy S 5] Suburban Afro:
I'm also noticing trouble with my call logs. Whenever I receive calls or miss calls, they don't show up. Is this an already known issue?
[AT&T Samsung Galaxy S 5] Rllns05:
Thanks a lot man!

---------- Post added at 07:22 AM ---------- Previous post was at 06:51 AM ----------

I also wanna point out that if you press down on the quick settings for too long, the system ui crashes and required a battery pull. Don't know if it was a known problem or not.
[AT&T Samsung Galaxy S 5] AptLogic:
Haven't had that issue yet, thanks for the input.

Yes, it is. I'm focusing on that and the NFC issue right now. Afterwards I'll be working on the Data Usage and Battery bugs.
[AT&T Samsung Galaxy S 5] sejodesign:
Note that after fresh install, at least for me, battery and data worked fine. After a day, this morning actually, it started crashing.
[AT&T Samsung Galaxy S 5] AptLogic:
I haven't had that luxury.. I did a fresh install (running a newer beta version) and things are still not working.
[AT&T Samsung Galaxy S 5] sejodesign:
I've seen it once before on earlier builds. Given how call log has issue, then battery and data logs... I'm sure you connected the dots already so what could possibly cause logging issues?

Either way, as I said this rom brought life to this device.
[AT&T Samsung Galaxy S 5] AptLogic:
The call log is a different issue, its logged as below:

W/AsyncQuery(20148): at
com.android.dialer.callog.CallLogQueryHandler$CatchingWorkerHandler.handleMessage(CallLogQueryHandler.java:86)

The log for the Data Usage log is:

E/AndroidRuntime(219450): at
com.android.settings.DataUsageSummary$DataUsageAdapter.getView(DataUsageSummary.java:1708)

And battery usage is simply:

E/AndroidRuntime(22753): Process: com.android.settings, PID: 22753

So these all seem to be pretty isolated, and the call log works fine in other dialer apps so it just seems to be that we need to replace/rebuild the Dialer.
[AT&T Samsung Galaxy S 5] sejodesign:
I see your point.
[AT&T Samsung Galaxy S 5] brianosaurus:
I've been using AptOS for a day and a half now. I love it. My phone doesn't feel like a 3 year old phone. Thanks, man!

I don't remember this showing up in the thread yet, so here goes. The Sound settings don't let me adjust volumes. I can adjust the "current" sound volume using the volume buttons on the side, but the sliders in Settings are all on 0 and won't move. One of the labels is screwy, too; it looks like a short, wide rectangle.

There also doesn't seem to be a way to adjust Notifications volume separately from Ring volume, as I could in the Alliance ROM (I don't remember what the stock ROM had).

I'm also getting a lot of "System UI has stopped", particularly when I try to run Samsung Health. Maybe its because I restored it using Titanium Backup, and it is expecting something that isn't there. I haven't done any android dev. How do I find the log file to see where it is breaking?
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] what is the aioswf folder for? also why is AyaTube in it and AXBattery
[AT&T Samsung Galaxy S 5] AptLogic:
??? No idea what you're talking about lol. Can I get an exact file path or screenshot? :confused:
[AT&T Samsung Galaxy S 5] AptLogic:
Just checked my phone running an EXPLORER build which is really close to the release build, and I don't have that folder present on my device. Must be some garbage from something you installed..
[AT&T Samsung Galaxy S 5] arrmo:
FYI, tried to change the background wallpaper (to a live wallpaper) - but it says "App isn't installed". Oh ya, it is ... ;).

Just so you know. BTW, should we log items as issues in Git? Only asking as it's likely easier to track them there, rather than in a thread like this. Just a thought.

Thanks!!!
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah I originally wanted issues to be tracked in Git, just for the sake of my own sanity. But when I tried to set an example by posting early issues nobody caught on.

If you guys can start submitting issues to Git that would be great!
[AT&T Samsung Galaxy S 5] arrmo:
Absolutely, will do! And please don't take it the wrong way - to me it's just a tool to be used to help organize thoughts (and capture issues). Nothing more - I just find it helpful.

To make sure to add these in the right place - can you confirm the correct repository to use? Thanks!
[AT&T Samsung Galaxy S 5] AptLogic:
The repository is located at https://github.com/coretechsystems/AptOS-G900A

The readme contains the standard bug-filing procedure for all of the AptOS repositories.

The settings repository is located at https://github.com/coretechsystems/aptos-packages_settings

The bootanimation repository is located at: https://github.com/coretechsystems/aptos_framework-bootanimation

The OTA Updater repository is located at: https://github.com/coretechsystems/aptos_packages-OTAUpdater

The framework-res repository is located at: https://github.com/coretechsystems/aptos_framework-res

You are allowed to fork off of any of these repositories for your own use, but please make sure to link back to the original AptOS main repository if you release something, and tag [MENTION=7597286]AptLogic[/MENTION].

Bug fixes and pull requests for any of these repositories are welcome as long as you have tested them before submitting the pull request. If you submit a pull request, it will be tested a second time just to make sure.

Porting AptOS is allowed, but again please make sure to link back to the main AptOS repository (AptOS-G900A), and tag [MENTION=7597286]AptLogic[/MENTION] if posting on XDA.

The AptOS main repository contains two branches, one called "master", which has the latest FINAL RELEASE version, and "explorer", which contains the latest stable beta (EXPLORER) version. These both have their own separate OTA channels.
[AT&T Samsung Galaxy S 5] pinheaD420:
Just flashed final release wiped all except internal ....running super smooth ...I no u said about reporting to something I'm not sure how to do that so leaving it here ..... Camera issue with flash and super dark photos is back for me I no you had fixed it but yeah def sucks . Do you still have what ever patch fixed it before ? I use camera alot don't really want to restore xrom again I like this so much better.
[AT&T Samsung Galaxy S 5] pinheaD420:
Nvm camera worked after several reboots ....
[AT&T Samsung Galaxy S 5] xdanilva:
Are you gonna figure out the accessibility problem in settings [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
Working on it. The settings app is rather delicate when it comes to modifications... I'm still trying to get it to build.
[AT&T Samsung Galaxy S 5] pinheaD420:
So just thought I'd mention I installed a call log app from play store it happend to find all my call logs even the ones from before I installed new dialer app just thought was weird that the data is actually there but Google dialer won't display it
[AT&T Samsung Galaxy S 5] Joeohoh:
is it possible to get a nogapps version of this rom?
[AT&T Samsung Galaxy S 5] xdanilva:
You can remove them from the zip file
[AT&T Samsung Galaxy S 5] AptLogic:
I'll look into splicing whatever it uses into the dialer.

I'm working on it.
[AT&T Samsung Galaxy S 5] AptLogic:
After the major issues are solved, I will be working on stripping out all the GApps so that you can flash your own.
[AT&T Samsung Galaxy S 5] Joeohoh:
I don't know how to go about doing this?

Cool! i'll be waiting for that.
[AT&T Samsung Galaxy S 5] sejodesign:
[MENTION=7597286]AptLogic[/MENTION] can I flash your xrom over this? Really need the phone... Untill that's fixed I'd like to go back to the next best thing The X-Rom.
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah you can flash X over AptOS!
[AT&T Samsung Galaxy S 5] sejodesign:
Awesome. I use the phone a lot throughout day so the lag and 3rd party dialers... You get the point. I'll be keeping an eye on this thread in the mean time. I am gonna miss the smooth looking UI!
[AT&T Samsung Galaxy S 5] Geo-XIII:
I dont know if it will help you, but when you open a contact in the PHONE app, to look at someones info, below that info it shows the recent call list. Idk why its there, but it is. Im not sure it shows missed calls because everything deleted when I applied the last update. I hope this helps! Eager for this last issue to be rectified, good work man!
[AT&T Samsung Galaxy S 5] xdanilva:
It would be nice if there was a landscape option [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
Would you care to elaborate as to what you mean by "landscape"? I feel like I have a basic idea of what you mean but I'd love some more info lol
[AT&T Samsung Galaxy S 5] xdanilva:
Oh I mean whenever I lock my phone to landscape it rotates back to portrait [MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] AptLogic:
Ohhhh. No, that's the intended usage of the Nexus lock screen. The TouchWiz lockscreen didn't even have that.
[AT&T Samsung Galaxy S 5] xdanilva:
There hasn't been any new stuff on this thread for a while
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah I've been doing some personal stuff, gonna get really into working on stuff next week.
[AT&T Samsung Galaxy S 5] AptLogic:
So, considering I haven't posted in the last five days... thought I might give a status update on what I've been doing.

So I was doing some thinking the last couple days, and a thought popped into my head. Why not try to build AOSP 5.0 for this device and grab the binaries from there instead of stealing everything from the Nexus 5? This could be the answer to a variety of bugs, which should include most of the Settings bugs and most likely the Google Dialer bug as well!

So, yesterday I started sharking around to figure out what it would take to build AOSP, and was happy to find out that I had basically everything I needed.

So, last night I fired up a new VMware machine running OS X, and tried to clone the Android source tree to the VM. Problem was, the connection was shared between my PC and the VM, and caused a lot of problems. So, I completely ditched that idea (OS X required a lot more work anyway)

Moving forward to today, I dusted off my old internal webserver (which is basically just a repurposed Lenovo B570), and set out to re-flash Linux and get rolling.

Took me 3 (yes, three) hours to accomplish the VERY basic task of installing Ubuntu Budgie 17.04 (for the record I blame Lenovo's temperamental UEFI firmware). So now I've got the terminal running, cloning the Android 5.0 source tree at 9MB/second and we'll see what happens.

My plan is to inject the Samsung OF2 Platform source into the AOSP source, build it, and then run the entire thing through WinMerge against the current AptOS Explorer build. Afterwards, its a simple procedure of picking out what we need and seeing what happens when I replace x with y.

I'll keep you guys posted on what happens. I really hope this works since I've been downloading for the last two hours.

:)

UPDATE: Its been about 20 minutes since I posted this and the Android source tree finally finished downloading. I'll be injecting the Samsung Platform source and attempting a build tomorrow!
[AT&T Samsung Galaxy S 5] AptLogic:
Just in case you guys haven't been looking at the GitHub page... I've decided to turn the GitHub account I use, coretechsystems, into an organization (which it already kind was but eh).

What this means for you:

You are now able to actively contribute to AptOS, X ROM, and any new projects! This includes the ability to fork or create new repositories to develop ROMs for new devices. This will hopefully aid by expanding the ability for us to port or re-create AptOS, X, or other ROMs to new devices.

Currently, due to the limitations of GitHub, you have to PM me or @ mention me in this thread with your GitHub username for me to add you to the organization, so you can get crackin'!
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] you should make a github.io page with a nice style
[AT&T Samsung Galaxy S 5] AptLogic:
Yeah that's what I'll be doing after I set up the buildbox. I bet it'll take about 2 hours or more to build so that's plenty of time.
[AT&T Samsung Galaxy S 5] AptLogic:
Just another quick update, finally got the buildbox building the AOSP, we *should* get something out of it in the next two hours. If not, I'll run it through the night.

We've got a quick website whipped up over at coretechsystems.github.io. Nothing too fancy as of now, but in about 3 days (05/14), it'll be replaced by the actual new site, and a new domain name as well (we've got the domain name ready, just gotta do fancy DNS things). Not only that, but I'll be announcing three new projects that'll be starting real soon!

Actually, while we're on that note... WE NEED NEW DEVELOPERS!!

More developers offering their help in making AptOS, X ROM, and other projects better will help expedite new features and expansions to NEW DEVICES. Of course, I can't say too much right now without letting the cat out of the bag three days early, but let's just say things will be coming to other devices (old and new) in the next couple months.

Remember, PM or [MENTION=2111323]MENTION[/MENTION] me with your GitHub username or email to be added to the CoreTech Organization on GitHub, where you can start forking, bugfixing, and developing to your heart's content! Not interested? Tell your friends, they might be ;)
[AT&T Samsung Galaxy S 5] xdanilva:
[MENTION=7597286]AptLogic[/MENTION] it redirects me to coretech.tk then it redirects to a 404 page
[AT&T Samsung Galaxy S 5] AptLogic:
Worked just fine for me just now... try going directly to coretech.tk all it does is forward to the github site.
[AT&T Samsung Galaxy S 5] xdanilva:
well it redirects to finder.cox.net which is a 404 page for cox networks
[AT&T Samsung Galaxy S 5] AptLogic:
Okay well then the only other explanation is that the domain is still transferring from the registrar's DNS to Cloudflare, which can take a while for some providers. Try checking it again in a couple hours.

Also Android failed to build the linker so the whole thing crashed, trying it again with ccache turned on this time so it might not take as long.
[AT&T Samsung Galaxy S 5] :
I can confirm the site is working, maybe your ISP is redirecting .tk sites?
[AT&T Samsung Galaxy S 5] xdanilva:
Probably the isp
[AT&T Samsung Galaxy S 5] AptLogic:
That could be the problem, but I doubt it since big cable companies like Cox don't usually redirect .tk sites, I've seen that more with corporate or school networks.

Just so you know, I only registered the nameservers for the domain about an hour ago, so it takes some time to propagate across the world's DNS servers, so the problem could just be that you have to wait a little while for your ISP to get up to speed, I've had that happen once or twice with my Time Warner Cable DNS, and then I switched the DNS servers on my router over to Google's Public DNS, which is usually faster than the ISP ones, and I can tell from the fact that it redirected you to a Cox search page that you're still using the ISP's DNS servers.

Protip: Use Google's Public DNS by going into your router and changing the IPv4 DNS servers to 8.8.8.8 and 8.8.4.4
[AT&T Samsung Galaxy S 5] xdanilva:
Well I'm at my house rn

---------- Post added at 07:54 AM ---------- Previous post was at 07:53 AM ----------

Well I'm not on cox anymorr
[AT&T Samsung Galaxy S 5] xdanilva:
It works
[AT&T Samsung Galaxy S 5] AptLogic:
Okay so the build finished a couple hours ago, solved my clang issue so that's nice.

Just deodexed and signed the new settings app, and the battery bug seems to be fixed (mostly). There's still an orange square instead of a refresh button but I suspect a simple framework conflict which I can fix later.

Storage, Data Usage, and Sounds/Notifications is still broken, so I'm working on that through modifications to the source where necessary. We're making some progress here.

The SystemUI built from source still has the low battery warning issue, so I'm gonna try to fix that from source and recompile.

I'll also try grabbing a newer Dialer source package and I'll make some makefile modifications so it'll work on API Level 21
[AT&T Samsung Galaxy S 5] Alief.Prophet:
Emojis

You think you can port Samsung's Nougat emojis onto this rom? That'd be lit
[AT&T Samsung Galaxy S 5] AptLogic:
I'm not sure because by default the GBoard handles the emojis. I could maybe make some modifications to the resources in framework-res but I think that would only affect OEM apps, which have been all but eliminated from the ROM.
[AT&T Samsung Galaxy S 5] AptLogic:
As of now the full site is up. Expect some bugs because I probably wasn't able to iron everything out ;)
[AT&T Samsung Galaxy S 5] pinheaD420:
Site looks great man ! Only thing I seen missing was a aptos update lolol
[AT&T Samsung Galaxy S 5] AptLogic:
lol yeah sorry about that... I'm trying to get a CAF version of AOSP to compile for me but I've been having issues with roomservice and lunch not recognizing the blobs I put into the source. Sometime this week I'll be shipping some new updates for those of you on the Explorer builds...

Upcoming:

-Possible Battery Bug Fix

-framework-res enhancements (mainly to fix a bug caused by the battery bug fix)

-Switching OTA XML providers from Azure to GitHub, integrating into the domain, and hosting releases off of GitHub as well.

-Migrating everything from AFH to GitHub repositories to make things just a little more transparent (and faster, considering AFH's expansion issues right now)

Maybe:

-Removing native Xposed, and putting it as an add-on in the AptOS OTA app.

-Putting some X ROM add-ons as AptOS add-ons in the OTA app.

As you can see, a lot of work with GitHub is going on right now. :D

Just throwing dates around right now... I'm thinking we'll be shipping version 2.4.5 to all users by late June or early-mid July. I'm also trying to remove the "Emergency Mode" toggle in the power menu, since that capability wasn't even present in X, and by extension AptOS.
[AT&T Samsung Galaxy S 5] xdanilva:
rip AptOS
[AT&T Samsung Galaxy S 5] AptLogic:
AptOS isn't dead, I've just got finals stuff to do lol, development will be back up in about two weeks after finals are over.
[AT&T Samsung Galaxy S 5] banditjackpotty:
Will there be a fix for the lockscreen always being rotated to landscape after the screen goes off? Also, it seems that there are some memory management issues over time

PS what was the reason for removing DivineBeats/viper? Will it be made optional like xposed?
[AT&T Samsung Galaxy S 5] dardanr3:
this rom it very good but please remove exposed because i cant use snapchat :(
[AT&T Samsung Galaxy S 5] AptLogic:
I'm considering it, but I don't think it'll have any real effect on whether Snapchat runs or not (it's really hard to bypass Safety net with a locked bootloader). Probably in the next release it'll be gone, but available as an add-on.
[AT&T Samsung Galaxy S 5] AptLogic:
Alright, so my Finals are done, let's get to work!

As of now, we currently have these bugs:

Settings:

- Opening Data Usage results in a FC

- Opening the Battery Usage results in a FC

- Attempting to turn on an accessibility service results in a FC

Dialer:

- Call logs do not display, but are definitely being recorded since you can see them in other dialer apps.

AptOS OTA:

- The merge to GitHub has not been completed yet (this is server-side and the migration will be completed in the next major release).

User Experience (UX)

- Live Wallpapers are currently unavailable (fixed already, waiting to be merged to the master branch)

And, also as of now, we have these solutions in line:

Settings:

- Attempt to dirty-replace some AOSP components with native TouchWiz by using APKtool - PENDING

Dialer:

- Unfortunately the only option we have here is a recompilation from source, which has been done and is awaiting testing.

AptOS OTA:

- Again, this is a migration thing and will be completed upon the next major release.

User Experience (UX):

- A fix for live wallpapers has been released to users on the EXPLORER update channel, and is guaranteed to be in the next major release.

As of now the next major release, 2.4.5, is planned for sometime in mid-July, provided that development and testing continues consistently until then. Users on the EXPLORER branch will be receiving updates shortly that include new versions of the Dialer, among other fixes and things in the pipeline.

The next EXPLORER release will be sometime tomorrow (June 11th) or Monday (June 12th). These releases will be prefixed with 24w. These new releases will NOT natively contain the Xposed framework. It will be released as an add-on sometime next week and will be available through the AptOS OTA app.

If anybody finds anything else that should be enhanced or fixed, please

do not hesitate

to lodge an issue ticket on the AptOS GitHub (https://github.com/coretechsystems/AptOS-G900A), or mention it in this thread.

Rock on, AptOS users!

:)
[AT&T Samsung Galaxy S 5] banditjackpotty:
Should I repost these bugs on Git for you? Just want to make sure you know about it
[AT&T Samsung Galaxy S 5] AptLogic:
DivineBeats had some issues, so that's why I removed it, it will, however, be available as an add-on in the coming days.

I've seen some slight memory leakage in the release build, but we'll have to wait and see if it gets worse or not before I look into it.

As for your lockscreen issue.. I haven't personally seen it yet. If you are on the Explorer update channel, try updating it later today and see if it fixes your problem. (and if it continues, shoot a couple screenies my way) :)