Let us get back once the CM14 nightlies start
Unofficial CM14 builds based on CyanogenMod + Grarak + Cherry-pick from CyanogenMod review stream
Facts:
Added 1 blob from OOS 3.1.0 to get the build working (Grarak is aware of it)
No extra features added, please do not request (still a n00b here)
Focus is more on debugging and hopefully help Grarak
Why is it not my daily driver though it is stable enough for a daily driver:
Unable to deactivate a SIM (just my itch)
Video recording does not work (Footej works but I want the stock camera to work: Will debug)
Busy to be able to spend more time debugging (especially with many other components changing rapidly)
Note:
Thank you all for being nice on this thread
hackworks said:
Unofficial builds of CM13 & AOSPA for OnePlus 2 with rotation vector fix. Please feel free to test it *only* for rotation vector bug (missing arrow in Google maps). Both builds are updated to latest source from their corresponding repositories.
AOSPA: https://www.androidfilehost.com/?w=files&flid=101343
CM13: https://www.androidfilehost.com/?w=files&flid=101350
CM13 changeset in review: http://review.cyanogenmod.org/#/c/157838/
AOSPA change (could not submit for review): http://pastebin.com/x9mMHzaq
Since this problem plagued us for a long time, I thought of sharing the builds for wider testing. Please be gentle, this is the first time I have shared a ROM that I have built
[All credits to the awesome hackers working on CM & AOSPA]
Click to expand...
Click to collapse
i would say, your hack is working just like your username..
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Mohit31 said:
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Click to expand...
Click to collapse
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
hackworks said:
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
Click to expand...
Click to collapse
Lol... It all went above my head
I think the answer is, it's not possible, right?
Thank you very much. It's working for me.
(I guess next/about next will have the fix, too. The existing commit only has to be merged)
Great work! This bug has been present since ever.
Sent from my ONE A2003 using Tapatalk
Todays build doesn't have the fix already. Am I right?
PeterImmel said:
Todays build doesn't have the fix already. Am I right?
Click to expand...
Click to collapse
Getting a patch merged is a slow process especially with almost all of CM devs focussing on 'N'. I will make a new build available with patch to hide signal for deactivated SIM in the status bar (when I get back home from work). There are/were 2 issues bugging me for a long time.
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
That's awesome
Great work
Thanks a ton..!!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Click to expand...
Click to collapse
You 're the man! Back to CM13 because of your fixes. Many thanks!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
Any chance of fixing loudspeaker echo, WhatsApp voice note not loud and random vibrations due to dt2w?
With these fixed, CM will be bug free.
Sent from my ONE A2003 using Tapatalk
@hackworks Has the rom been built with latest aospa code?
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Yea. :/
This has still not been fixed.
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554 @hackworks Please have a look.
P.S. This issue isn't present on AOSPA. So maybe that'll help.
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
John-J.Hammy said:
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
It is just CM13 with the 2 fixes. All that applies to CM13 or AOSPA remains valid on these builds
Mohit31 said:
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Click to expand...
Click to collapse
n00b here. No magic, just learning. I am working on using a cleaner approach to hide the SIM signal icon. Once done, will explore other areas
raburs said:
@hackworks Has the rom been built with latest aospa code?
Click to expand...
Click to collapse
Sorry for not responding earlier, I have uploaded a new build which is based on latest source as on today 26th Aug 2016 (night) for both CM13 & PA.
I tried my hands in Java code by implementing an event based mechanism to disable the SIM icon when it is disabled - Just ended up in flickering display and a SystemUI crash! Guess, I should just stick to C/C++ where I have spent most of my programming life (~18 yrs)! Summary: Will pick areas/bugs based programming language, no time to learn Java
Related
This is for developers only. No builds will be posted in this thread.
https://github.com/CM10DNA
Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
crpalmer said:
I thought I would share an update on how this very experimental code-base is doing.
The code is running again (much of yesterday it was crashing on startup).
I have been running dirty flashing from my CM 10.1 build. It seems like that was safe to do so. I tried doing a clean flash this morning but sadly, my clean flash seems to have broken cell service. No phone or data. Restoring my cm 10.1 backup of data to the same install fixed it. Strange. (This included the change pushed this morning that updates the version of the apns file).
Superuser is now working but may be a little flaky. For example, on my clean install Titanium Backup couldn't acquire root access until after I rebooted.
Camera is still not working. It says "failed to connect to camera". I haven't looked at it at all, but there is a massive commit in the M7 kernel pulling source from the HTC One Google Edition for the camera.
Overall, I'm finding it's either completely broken or working very well. I think that the cellular network issue is going to get resolved upstream. I am afraid that we might be on our own for the camera.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mmit/ec27077d6497c66f52488126ef6b181ef3fbed0d
seems cm has stopped camera building throughout probably prepping for the focal merge
edit: idk if m7 has cam working but it hasn't been detected as a bug
"Current bugs (they are known):
SMS sending will not work (receiving works)
Dialer sub-submenu FC's the dialer
Keyboard FC's when gesture swiping"
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Flyhalf205 said:
Not sure how much this helps. But the m7 kernel recently got its camera code updated with the Google edition. http://review.cyanogenmod.org/#/c/46164/
With that so. They are able to use the 4.2 libs http://review.cyanogenmod.org/#/c/46299/
Click to expand...
Click to collapse
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
JoelZ9614 said:
we'd probably have to merge their whole drivers/media/video/msm and use their camera binaries at least that's how it works with sense if you want to use their 4.2.2 cam libs
Click to expand...
Click to collapse
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
times_infinity said:
What about the commit introducing the HTCCDMAQualcommRIL?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Which commit?
crpalmer said:
Which commit?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/45607/
Hope it helps.
Sent from my HTC6435LVW using xda app-developers app
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Deck got data working on the m7 (Sprint), check the commits or wait until tomorrow if he hasn't pushed them yet
Sent from my buttered S3
chad0989 said:
I'll take a look at the radio stuff tomorrow. I have a couple ideas.
Click to expand...
Click to collapse
To be clear, it is working fine for me if I dirty flash. I have been running 10.2 builds for 48 hours everywhere from strong wifi to bad 3G in the middle of a forest.
It's only breaking if I do a factory reset before flashing a build. That's why my guess was that it was related to this event being missing:
cyanogenmod.org/#/c/46280/1/libril/ril.cpp
(around line 2240) and that a similar change was going to be required to our libril. My inclination would be to wait and see what happens with the M7 builds (which it sounds are coming along) and see if it just magically fixes itself for us....
Edited to add: sending of text messages wasn't working but looks like they were supposed fixed last night (I haven't built it to test it yet)
crpalmer said:
And their commit conflicts all over the place which is going to make it hard to cherry pick it. This was the commit I referred to earlier today.
On the plus side, the ril issue looks like it will get resolved for us. There is a commit out there for Samsung hardware that adds a couple of RIL events that look like they have been added.
Click to expand...
Click to collapse
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
JoelZ9614 said:
mm actually now that i look at it drivers/media/video/msm has been left basically untouched in our source updating to what the m7 has shouldn't be too much of a problem
Click to expand...
Click to collapse
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
crpalmer said:
I tried a cherry-pick before and it looked very bad. But, actually, a lot of it looks like it could be related to the comments that HTC strips from the source when the release that I added back (because it makes it easier to patch from all non-HTC sources).
If you want to take a crack at this, try doing this before cherry-picking their commit:
git show c81741a8337c2342d856ffeac0cc087452729290 drivers/media/video/msm include/media/msm_camera.h | patch -p1 -R
That will strip all the comments back out again and get rid of all those conflicts. The conflicts then look very simple (outside of arch/arm/mach-msm, which is where it gets much harder).
Click to expand...
Click to collapse
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
JoelZ9614 said:
the board-monarudo-camera.c doesn't need to be updated, at least i didn't update it in my m7 kernel port
but i can't seem to get the kernel to build
drivers/gpu/msm/adreno_snapshot.c: In function 'snapshot_rb':
drivers/gpu/msm/adreno_snapshot.c:628: sorry, unimplemented: inlining failed in call to 'parse_ib': recursive inlining
drivers/gpu/msm/adreno_snapshot.c:588: sorry, unimplemented: called from here
make[3]: *** [drivers/gpu/msm/adreno_snapshot.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
i don't believe it's related to any edits i made tho heres my commit https://github.com/Joelz9614/android_kernel_htc_dlx/commit/daa90f2bf8e64a8ad6f4f497ca412bc0a77ab7ef
Click to expand...
Click to collapse
Searching in the browser doesn't have any matches for adreno_snapshot...
Maybe try git checkout -b tmp HEAD~1 and make sure that builds?
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
chad0989 said:
Looks like CM just merged an updated audio HAL along with the legacy HAL, both of which incorrectly detect our device for now. Building with a fix now and if all is well I'll submit upstream.
Edit: It's going to cause a bunch of routing issues again also until some other stuff gets merged in. Best to just revert their change for now for builds.
Click to expand...
Click to collapse
Aside from the routing issues, this may already be fixed for us thanks to the m7:
http://review.cyanogenmod.org/#/c/46473/
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
crpalmer said:
@chad0989, FYI, I reverted the commit to use legacy alsa early this morning and haven't noticed any problems (play music on Bluetooth, voice calls with and without wired headset) using that build.
You may want to give it a try and see if you're ready to revert it.
Edit: actually, I just noticed that they had also enabled legacy audio in msm8960-common but since reverted that. So, I guess I was still running the legacy mode...
Click to expand...
Click to collapse
They aren't allowing new HAL to build yet (see https://github.com/CyanogenMod/android_hardware_qcom_audio-caf/blob/cm-10.2/Android.mk) But we will need that flag when they allow the new HAL to build. I added it preemptively to hopefully avoid breakage. The issue was that the legacy HAL they pushed hadn't included some changes for our CSD client and platform detection. Looking at what was committed last night/today it should work now though.
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat - Togari, ROM for the Sony Xperia Z Ultra
Contributors
OmarEinea, SlimRoms, prbassplayer
Source Code: https://github.com/SlimRoms
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Build 9
Stable Release Date: 2014-12-26
Current Beta Version: Build 8.20
Beta Release Date: 2014-12-09
Created 2014-06-30
Last Updated 2014-12-29
Camera fix apk
Found here
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Deleted
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
blueether said:
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
Click to expand...
Click to collapse
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
prbassplayer said:
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
Click to expand...
Click to collapse
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Edit:
I do know that carbon is using -caf as I had to change an include path to get past a not found .h
blueether said:
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Click to expand...
Click to collapse
Slim had problems with some video playback (browser video or Netflix) would be green unless I disabled hw overlays, when we moved caf that git fixed and camera was less problematic.
Sent from my Xperia Z1 using Tapatalk
Thanks a lot for another awesome firmware for the Z Ultra!!
Regarding the camera issue, I've been facing it on every custom firmware out there, and found a possible workaround (works for me, at least): as soon as the device boots, open the camera immediately, and it should open normally after a small delay / frame freeze. After that, it continues to work normally, without any freezes, until the next reboot. However, if you wait a while after boot before opening the camera, it will freeze with a static frame. Killing it will cause the "can't connect to camera" message to appear the next times you open the camera. And I've tested with different camera apps, it's the same thing.
Hope it helps to debug the issue.
Alright, currently running this as my main. No problems so far; Bluetooth, calling, LTE, Wi-Fi, and video all work completely. Haven't had a reason to use the camera yet, however.
all seems to be working, but it doesn't read my SD card. It's an class4 a-data 32GB card formatted as exFAT, I'm backing up its content and will format it in phone (it does recognize it, but when I tap mount sd card, more options just flash below and then it goes back to 'mount sd card')
edit: no luck, it doesn't even format the card. When I reformatted it via card reader to FAT32 or NTFS, it was recognized, but with NTFS formatting it does not see any data, so I guess it's just exFAT/NTFS support that's missing
oh and with this dpi settings, digits in PIN entry are too close together (but still possible to type them in) - see http://i.imgur.com/sNmEGOJ.jpg
awsome job buddy another device of Xperia Brigade
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
jouse i will do it if u want
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
blueether said:
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
Click to expand...
Click to collapse
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Not sure of the differences either, but as soon as I got Carbon togari to build the gpe built as well. There has only been a few little issues in the gpe build for carbon. although the last silm I built for the GPe didn't boot.
There only seems to be about 30 people downloading the GPe carbon so there may not be much of a call for it.
Been a while .. No new Updates for this ROM ???
VipiN'n'DroiD said:
Been a while .. No new Updates for this ROM ???
Click to expand...
Click to collapse
Bother reading much?
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
prbassplayer said:
Bother reading much?
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
Click to expand...
Click to collapse
Thanks Bro for your work [emoji106]
PARANOID 4.6 Beta1
Still No Public Source yet : ( I really should try to become the maintainer or something.
Bro, What's new now?
I've been looking for the commit that caused my instagram videos to stop working. It also affects mirroring the screen to a chromecast. That's on the horizon. What is definitely new is some changes to the snd_soc_msm file that came from someone at CM.
If there are any blatant issues let me know And I'll see what I can do to remedy them.
Now with more tenths of an increment!!!
ROM
GAPPS
CM GAPPS
Hey thanks! Trying it!
Enviado desde mi XT1053 mediante Tapatalk
Welcome and thank you for youre development
Any other bugs at this time? Or is very stable?
Marco Lomas said:
Welcome and thank you for youre development
Any other bugs at this time? Or is very stable?
Click to expand...
Click to collapse
I've been using it all day today and I haven't noticed anything totally funky. There is still the Netflix bug where you have to tap at different places on the seek bar to get a clear image. Also the Camera doesn't record video higher than QVGA. The Netflix bug goes all the back to Cyanogenmod but the Video recording may be fixable.
Tried the fix for the camera under cm11 thread ? Many reported it worked but it still fc'd
flasherruts said:
Tried the fix for the camera under cm11 thread ? Many reported it worked but it still fc'd
Click to expand...
Click to collapse
Try the OpenCamera from play store
Stock camera doesn't work even after the fix ..!
I found the media profiles fix but it looks like I'm still getting errors trying to upload videos to Instagram. The video plays back as all black. I'll add it to the ROM anyway. Maybe I can figure out if it's just Instagram or the media encoding.
@treyf711 is the new android L style recent apps screen is added in this rom...?
and are you going to update to PA 4.4.5 or 4.5 ...?
thanks for your effort and work (Y)
electron.hTcpico said:
@treyf711 is the new android L style recent apps screen is added in this rom...?
and are you going to update to PA 4.4.5 or 4.5 ...?
thanks for your effort and work (Y)
Click to expand...
Click to collapse
This feature is only on PA 4.5 alpha u.u
THANKS
Great!!! I'm gonna try!!!
electron.hTcpico said:
@treyf711 is the new android L style recent apps screen is added in this rom...?
and are you going to update to PA 4.4.5 or 4.5 ...?
thanks for your effort and work (Y)
Click to expand...
Click to collapse
@kjjjnob is right. The recents are in 4.5 And I haven't been able to find that source on github but someone can point me to it if I'm wrong. At the moment I'm making a mirror so I can put out 4.45 later this week but I derped and forgot to do it before I left school earlier this week so I'm using my home internet that is about 150 KB/s. It may be later this week.
The 1080p fix for the back camera doesn't actually result in working recording. When trying to stop the recording it force closes the camera at least with the google camera. I've left it out for this reason until I find something that actually makes it work.
Genius ahah
Bro thanks again for this! I'll try, downloading. Maybe you take a look at commits from msm8960dt Gummy team (dhacker mantain only this, he's the father of X and G ahaha).
kjjjnob said:
Bro thanks again for this! I'll try, downloading. Maybe you take a look at commits from msm8960dt Gummy team (dhacker mantain only this, he's the father of X and G ahaha).
Click to expand...
Click to collapse
I do check out the stuff he pushes but haven't really added anything device specific yet. How does the man know so much Motorola stuff? He's gotta have some kind of inside experience.
Any bugs anyone noticed? I'm about to flash in the morning regardless lol I'm ready for that recent menu...
You made me happy again
Oh and btw https://plus.google.com/app/basic/s...88d&sview=25&cid=5&soc-app=115&soc-platform=1
treyf711 said:
I do check out the stuff he pushes but haven't really added anything device specific yet. How does the man know so much Motorola stuff? He's gotta have some kind of inside experience.
Click to expand...
Click to collapse
Dhacker is magic ahah. Maybe you try to talk with DJLamontagneIII, he merge updates on Slim Kang rom (CAF and prima updates) from Team Gummy kernel The last build works perfect, what's the problem with Instagram?
@treyf711 can you please try to give a small changelog for every build ..? and thnaks for your efforts
kjjjnob said:
Dhacker is magic ahah. Maybe you try to talk with DJLamontagneIII, he merge updates on Slim Kang rom (CAF and prima updates) from Team Gummy kernel The last build works perfect, what's the problem with Instagram?
Click to expand...
Click to collapse
Whenever I record a video with instagram and try to upload it I get nothing but black video. Audio works fine on it but for whatever the reason the video doesn't show.
Has anyone got Netflix to work without xposed?
Sent from my Moto X using XDA Free mobile app
This thread is for my daily driver builds of @RobbieL811's Uber CM12.1 currently with @bbedward's Zen kernel. Sometimes I build @flar2's ElementalX kernel instead. Flash whatever makes you happy.
My understanding is UberCM is a lot like vanilla CM but with a few essential things added. Haven't run plain CM in so long so I don't know the differences anymore. Anyways it'd be selfish to hoard the Uber goodness so I came here to share. BUT I don't embellish UberCM or cherry-pick unless necessary and I'm not a developer so don't request features. I test all builds before posting.
Don't bug RobbieL811 if you encounter problems with this rom. He doesn't support Nexus 6 builds at all, nope nada uh uh..
FEATURES
all CM12.1 features incl CMTE for all the theming you crave. NO LAYERS.
call recording (mic only thx to shamu's crappy drivers) is not perfect but good enough
a few extra quick tiles. My fave: reboot tile w/recovery option.
works with Xposed. I love Xposed all day & all of the night, maybe you do too.
some other stuff
GOTCHAS
Call recording only works with AAC, seems that AMR is broken but it sucks anyway so just use AAC
LOCKSCREEN OPTION: if you enable secure lockscreen it'll also apply at bootup even if you choose otherwise. If you choose a lockscreen pattern ONLY use 3x3
VoLTE, wifi calling. They might work but don't expect it and I can't test 'em so don't care.
INSTALLATION
Get on a recent bootloader & modem. For example LMY47Z.
Download & install UberCM 2.0
install Slim GApps or Delta GApps
install SuperSU if you want root
OLDER RELEASES: UberCM 1.8
UberCM 1.7
Hopefully you will enjoy UberCM. If not maybe try another rom like Spring (awesome & innovative but might not work w/Xposed) or BlissPop (every feature in the world) or Euphoria (a possible cure for crackflashing).
Stuff I like:
Kernel Adiutor | Euphoria Dark theme | strong coffee
Credits/sources:
CyanogenMod
UberCM
Zen Kernel
ElementalX kernel
Screenshots
Screenshots come when I get the time.
future site of important updates
Reserved2...
Woot new ROM! Thanks will try later,
Good!
Nice one. I always use cm as secondary rom. Will give it a try. Thanks
Got a mirror? Mega is a **** host and forces their app installed to download on a device.
Don't need a mirror, put it in desktop mode.
beepea206 said:
Got a mirror? Mega is a **** host and forces their app installed to download on a device.
Click to expand...
Click to collapse
goo.im crapped itself and my account there has been iffy since maybe 2013. Mega is uber reliable and wfm. Got a suggestion for other mirror sites?
That sucks, man. I saw another dev using his SkyDrive account, so I don't know if that's an option. Frankly, I haven't used a dev mirror site since I worked on the Droid 2. Lol I But the build looks really interesting. The cm builds aren't working for me and are breaking encryption some how, so I'll give yours a try.
beepea206 said:
That sucks, man. I saw another dev using his SkyDrive account, so I don't know if that's an option. Frankly, I haven't used a dev mirror site since I worked on the Droid 2. Lol I But the build looks really interesting. The cm builds aren't working for me and are breaking encryption some how, so I'll give yours a try.
Click to expand...
Click to collapse
breaking encryption meaning you're not encrypted anymore? or /sdcard is inaccessible?
btw mine is working fine fully encrypted using the build in OP. AFAIK the kernel is encryption agnostic so even if you're not encrypted all should be well.
Not encrypted. It's the damndest thing and no one seems to know why, but I think it's related to the kernel flashed with some of the roms. Benzo, chroma, dirty unicorns, all good... Terminus, 2 of the other cm builds up... Breaks it. If I restore my stock nandroid, it fixes the issue, so I can only assume it's that specific kernel doing something wonky.
The encryption matters for me, because I'm using exchange with an administrator. Need it for work and that's how I've found encrypt broke... The administration setting goes haywire on me when I flash some roms.
beepea206 said:
Not encrypted. It's the damndest thing and no one seems to know why, but I think it's related to the kernel flashed with some of the roms. Benzo, chroma, dirty unicorns, all good... Terminus, 2 of the other cm builds up... Breaks it. If I restore my stock nandroid, it fixes the issue, so I can only assume it's that specific kernel doing something wonky.
The encryption matters for me, because I'm using exchange with an administrator. Need it for work and that's how I've found encrypt broke... The administration setting goes haywire on me when I flash some roms.
Click to expand...
Click to collapse
My money would be on Exchange being a piece of crap. Try stock rom, good luck.
Also related to Exchange: I have a generic rom unf*cker that deletes junkware (AKA stuff I don't like or use) incl exchange, most live wallpapers, other stuff, and adds a few good utils like Kernel Adiutor, Autostarts & f-droid. Could post it with the next UberCM build if somebody wants to try.
CrashTestDroid said:
goo.im crapped itself and my account there has been iffy since maybe 2013. Mega is uber reliable and wfm. Got a suggestion for other mirror sites?
Click to expand...
Click to collapse
Androidfilehost is pretty good imo. You have to register and wait for approval, but that's typically less than a couple hours. Decent speeds and interface.
Sent from my Nexus 6 using XDA Free mobile app
Some UI improvements and other goodness is in the works. UberCM 1.8 is building.
CrashTestDroid said:
Some UI improvements and other goodness is in the works. UberCM 1.8 is building.
Click to expand...
Click to collapse
First time trying this ROM, very nice change over STK cm, essential adds but not too much. Thanks for sharing!!
Stability issues with 1.8, made some changes and we're building again.
Meanwhile I posted an updated 1.7 that's been giving killer battery life for me.
Was thinking where did 1.8 go. No worries appreciate testing before posting!!
razrlover said:
Was thinking where did 1.8 go. No worries appreciate testing before posting!!
Click to expand...
Click to collapse
OP updated with UberCM 1.8, ElementalX is the kernel. Works for me. Hope you like it.
Got 2.0 posted up and it's delightfully speedy. Only gotcha is it'll apply secure lockscreen settings to bootup so don't use 4x4 or larger lockscreen pattern.
See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Reserved
Reserved
Just wanted to say thanks for this!
I use this phone with hangouts dialer on wifi when I'm out working (leaving my good, fragile phone safe in the house). I was using the old cyangenmod 13 rom because it was the only one that would work without missing sim errors.
This rom works perfectly for my needs, again, thanks!
javelinanddart said:
See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Click to expand...
Click to collapse
Is this rom still being actively developed? I'm interested in testing if so.
FanboyStudios said:
Is this rom still being actively developed? I'm interested in testing if so.
Click to expand...
Click to collapse
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
javelinanddart said:
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
Click to expand...
Click to collapse
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Edit: Stock equalizer seems to work on all my audio files (.wav, .flac, .m4a), except .mp3 files.
FanboyStudios said:
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Click to expand...
Click to collapse
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
javelinanddart said:
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
Click to expand...
Click to collapse
I'm using the latest official build from the official LineageOS website. It's 14.1
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
javelinanddart said:
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
Click to expand...
Click to collapse
Oh, that's good news! In fact I did not check the NFC function before writing that message, I think I saw somewhere that NFC does not work in LineageOS on S5.
Or maybe I got confused with S4 (jfltexx) which I also own and where NFC does not work for sure.
I've sent you a donation thru Paypal, many thanks for your work!
Just a side note for fun and general info. My bank flagged my account after using their banking app as accessing with a "known fraud device" and locked my savings and checking. In the end, I had to get new accounts because they could not turn them on after the fact. I tried to explain in vain and they would not hear it. So fair warning if you try to use your banking app on the Lineage ROM. Nothing extra added, only the current version of this ROM and open gapps.
Is there any chance to see Wireguard VPN support in this build?
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
What are the bugs with the lineage-14.1-20180222-nightly-kltesprsports-signed.zip build? I'm interested in flashing. Also, was the issue with airplane mode disconnecting LTE on the s5 sport ever resolved? Disabling airplane mode does not initiate LTE connection only until I reboot my phone. I'm on build 14.1-20170418 currently so curious to see what has improved. Also, a big thanks to everyone in this community. I moved from cm13 to this build a year ago and I've been happy. Just looking to resolve the LTE issue .
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
vrobo said:
Is there any chance to see Wireguard VPN support in this build?
Click to expand...
Click to collapse
Wireguard is awesome.
I found out that calendar does not notify about forthcoming events. I use LineageOS without Google stuff (with Offline Calendar https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/ instead).
Is this a bug in Offline Calendar on in LineageOS build for kltesprsports?
vrobo said:
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
Wireguard is awesome.
Click to expand...
Click to collapse
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
onlyoneway said:
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
Click to expand...
Click to collapse
https://download.lineageos.org/kltesprsports/changes/
Hey Guys! I have a Samsung S5 sport that I recently dirty flashed to the 14.1-20180803-NIGHTLY-kltesprsports build. Now my battery does not go beyond 65% no matter how long I leave my phone plugged in. I have tested different cables and adapters, and still the same thing. Didn't have this issue with the 20180720 build. Any thoughts? Bug maybe? Thanks in advance.