I have gotten so far in this. The device boots and operates quite normally, with three exceptions.
The camera fails to record. If it starts to record, ending the recording freezes the camera. Or, it just won't start at all.
Some graphical glitches on the lockscreen. Nothing major, or breaking, but weird (see below) but the glowpadview is missing a chunk and there's a strong line of dots towards the lock icon.
Animations are jerky.
These are the device trees I'm using
# Device Samsung i9300
https://github.com/UltimaAOSP/android_device_samsung_i9300
# smdk44121-common
https://github.com/UltimaAOSP/android_device_samsung_smdk4412-common
# Kernel source
https://github.com/UltimaAOSP/android_kernel_samsung_smdk4412
This is the AOSP tree I'm using, by broodplank1337
https://github.com/AOSP-S4-KK
The source tree is great. broodplank1337 did a great job, and it builds and runs wonderfully on the S4 i9505. I have nearly got this down but I'd appreciate any help or advice available!
@Kryten2k35 I was surprised to find no pure AOSP ROMs for SIII. I'll be getting one soon so wanted to have compiled 4.4.4 for it.
I'm surprised you get the problems you have however, as surely these aren't apparent in AOSPA, SlimKat, etc. which are based on AOSP also? Surely you must have had to add vendor/samsung stuff, maybe some hardware/ repos, etc. as missing proprietary blobs would explain the broken camera. I'd be glad to help out anyway. I was about to sync pure AOSP source but do you think this'll be too much of a challenge?
Hi,
I should've updated this thread. It turns out I was compiling with ofast CFLAGS, which was causing the graphical glitches and animation issues. The camera I haven't tested yet, but I suspect the same.
Kryten2k35 said:
Hi,
I should've updated this thread. It turns out I was compiling with ofast CFLAGS, which was causing the graphical glitches and animation issues. The camera I haven't tested yet, but I suspect the same.
Click to expand...
Click to collapse
Thanks a lot, I may as well try building my own AOSP if I know you've been successful then. Will those UltimaAOSP trees work fine for me or should I use CyanogenMods or probably better AOSPAs? I'd be grateful if you could point me towards the correct vendor tree if I'll need to use anything our of the ordinary, but I assume CMs will be fine?
Thanks and sorry for the questions but I have 0 experience with this device (don't even own it yet ) so there's many more sources, trees, and stuff than I'm used to (Desire Z only had 1 maintained device tree).
The UltimaROM trees should work fine when I update them slightly based on these changes.
Everything is mostly AOSP, with the obvious exception of the device tree and kernel tree, both of which are Cyanogen, oh, and Camera, which is also Cyanogen. I had to make a few small changes to AOSP stuff to enable it to work with the S3, as well. nothing major, though.
EDIT:
My UltimaAOSP aim is to remain as close to AOSP as possible. Any modifications are 100% optional and disabled on a new install, so a user can have a Nexus-like experience if they wish.
You are 100% welcome to download UltimaAOSP's source and help in any way you see fit. I appreciate any help I can get.
Kryten2k35 said:
The UltimaROM trees should work fine when I update them slightly based on these changes.
Everything is mostly AOSP, with the obvious exception of the device tree and kernel tree, both of which are Cyanogen, oh, and Camera, which is also Cyanogen. I had to make a few small changes to AOSP stuff to enable it to work with the S3, as well. nothing major, though.
EDIT:
My UltimaAOSP aim is to remain as close to AOSP as possible. Any modifications are 100% optional and disabled on a new install, so a user can have a Nexus-like experience if they wish.
You are 100% welcome to download UltimaAOSP's source and help in any way you see fit. I appreciate any help I can get.
Click to expand...
Click to collapse
@Kryten2k35 Thanks, although I'd love to help I'm currently working on a few of my own projetcs with other members already. Is there no need for the android_hardware_samsung repo or SamsungServiceMode any more then as I can't find them in your sources? I've synced AOSP so I'm gonna have a go with your tree right now to see if it works, is it all updated? Thanks alot
EDIT: Found those repos in your default.xml, I assume they're needed then.
EDIT2: Will I need your vendor repo too? At the moment I assume I'll just have to run lunch full_i9300-userdebug as nothing else appears to work
@HTCDreamOn
Yeah you'll need my vendor repo and my Samsung propitiatory blobs repo, I think.
I've picked back up where I left off this last few days. All the graphical glitches were fixed. But the camera glitch remains: details are here: http://forum.xda-developers.com/showpost.php?p=54234546&postcount=585
I have one choice: ArchiKernel. No other kernel works with camera recording. Which is insane, since the CyanogenMod kernel should work fine, but does not.
Related
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
I use the Ninphetamine kernel and a clockwork recovery initramfs. The initramfs has been altered and will not boot with other ones. This is because of a missing socket that the older init.rc doesn't make.
I'll be using the next post to describe what I'm working on and update it with any useful info I find.
Currently it's in an unusable state, here's where it stands:
Working
Making calls
SMS
Audio
Internet (Data Connection)
Note: When you open browser, it will crash because google's home page try's to use location services, you need to navigate away quickly in order for it not to crash.
Proximity Sensor
Internal Storage
microSD Storage
Vibration
Camera
USB Transfer with Internal Storage
Untested
Other Sensors
TV Out (doubtful)
Not Working (yet)
WiFi (don't even turn this on, it will reboot endlessly) <-- working on it
Camcorder
Bluetooth
GPS
USB Transfer with microSD (not a huge priority)
I know that cyanogenmod is pretty darn close to AOSP and that I'm duplicating work, but I'm doing it anyways.
If you want to try it out:
Binaries:
CWM Kernel Zip
CWM AOSP Zip
Note: Obviously you need to wipe.
Sources:
https://github.com/nemasu/
Working on WiFi
no notes yet
nemasu said:
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
Click to expand...
Click to collapse
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Pume said:
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Click to expand...
Click to collapse
Ah, yeah, I forgot about that one. I'll be leaving it completely stock AOSP though (when it works well anyways). Might speed things up for me a bit. I am doing this as a sort of hobby too, interesting to learn how it works.
EDIT: It WILL speed things up a great deal....DevNull did some great work.
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
All the same, great work mate, we need more AOSP ROM's, since AdamG has taken a break due to personal reasons it's nice for another dev to take the helm.
Good luck mate, all the best.
nesquix said:
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
Click to expand...
Click to collapse
Does A2DP work on Oxygen?
Sent from my CM7 powered SGS2
This xda members...
AdamG did great work yes but it does not preclude to new AOSP roms.
Keep your respected work.
Edit: If AdamG had taken a break, maybe you should think to fork devnull. This speeds up work and you can focus another thinks etc A2DP and tvout. Its open source
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
bluheart said:
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
Click to expand...
Click to collapse
Agree......
Sent from my GT-I9100 using Tapatalk
Keep up the good work!
Nice work buddy
I turn my back for 1 day and you're nearly done! Keep it up
does it have a aosp lockscreen only?
Always nice to see more AOSP love will be keeping an eye on this, good luck man no wifi would be a dealbreaker for me ATM..
wliu88 said:
does it have a aosp lockscreen only?
Click to expand...
Click to collapse
yup, I've added nothing to it, pure aosp.
Hi! I'm trying to reproduce this compilation but no success. It stucks with a lot of libs errors. Any idea? I'm using a little modified device configuration from android_device_samsung_galaxys2.
Sent from my GT-I9100 using XDA App
Hey,
does someone know, why one of the Promoted 4.0 features, "video snapshots"
is not available in AOSP builds like Cyanogenmod? it means you can take a high-res photo while recording video at the same time.
It is an android 4.0 feature and not specific to the HTC One X as some people suggested earlier (http://www.youtube.com/watch?v=64JulxSOjzc&feature=relmfu#t=46m13s)
It does not need a special camera sensor since it is available in the value pack for the galaxy S i9000 (http://www.sammobile.com/2012/04/10/guide-samsung-galaxy-s-s-value-pack/)
does someone know how this comes?
The Samsung camera hardware drivers are not open source and are therefore not part of AOSP, the CM devs have modded the AOSP camera apk to run on the SGS2 camera, but not all features are implemented, until a couple of weeks ago you couldn't even save video taken with the SGS2 camera, if it's possible to implement, I'm sure they will at some point, be patient. If you want it faster than 12/24/2045 I suggest downloading the sources for the AOSP camera and see if you can add the features yourself.
thracemerin said:
The Samsung camera hardware drivers are not open source and are therefore not part of AOSP, the CM devs have modded the AOSP camera apk to run on the SGS2 camera, but not all features are implemented, until a couple of weeks ago you couldn't even save video taken with the SGS2 camera, if it's possible to implement, I'm sure they will at some point, be patient. If you want it faster than 12/24/2045 I suggest downloading the sources for the AOSP camera and see if you can add the features yourself.
Click to expand...
Click to collapse
yeah, i know that video recording wasn't working until just recently (i've been using CM9 since the first nightlies)
i wish i could help with this feature but i have barely any clue of coding so i would be of no use
Generally the CM team worries about things actually working and working properly before they get into added features, they've made a lot of progress but there are still a few issues that are probably on the list above camera snapshot, patience is always the key with these things.
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]
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.