I've read elsewhere that “Developers cant customize the in-call screen because of security concerns”
So, I am trying to understand the functionality of the in-call screen at the source level.
Can any Android devs, especially those that have created their own custom ROMs, tell me which specific classes in the AOSP are responsible for both display and functionality of this screen?
Related
On every ROM the camera causes the phone to reboot. I am very surprised that developers haven't paid any attention to this and released ROMs with this bug and call it an official build when the ROMs are more like early alphas its embarrassing.
Every dev knows that, instead of blaming them ask Samsung to release proper camera driver sources, which is not the case now.
aharnick2013 said:
On every ROM the camera causes the phone to reboot. I am very surprised that developers haven't paid any attention to this and released ROMs with this bug and call it an official build when the ROMs are more like early alphas its embarrassing.
Click to expand...
Click to collapse
Hi aharnick2013,
The last nightly I tried for CM10.1 was 06/17/2013 and the camera was working fine, apart from the usual audio bugs and poor camera performance.
I'm not sure about AOKP and AOSP, but for what I see in the CM changelogs, some parts of the sensor drivers in the kernel will be back ported from a previous release for the nightly of 06/20/2013, not sure if this has to do with the issue you are having as I never experienced myself in CM.
To be included in next nightly:
Derp fix. (android_frameworks_base)
Hide navigation ring if no targets are configured. (android_frameworks_base)
Cleanup. (android_frameworks_base)
Close notification panel when swiping away the last clearable notification. (android_frameworks_base)
Add media-caf repository (android)
u1: port sensors and modem interface from smdk4210 kernel (android_kernel_samsung_smdk4412)
Camera: Add a GPS indicator (android_packages_apps_Camera)
Check and fail early if requested wallpaper size exceeds maximum texture size. (android_frameworks_base)
Lockscreen : Fix widgets disabled (android_frameworks_base)
Fix ringer mode being unneededly changed by setting ringer mode volume to 0. (android_frameworks_base)
Squashed commit of A/V changes from CodeAurora (android_frameworks_av)
Also take into account that the i9300 is a tough nut to crack, because of samsung, and the guys at AOSP and CM are working for FREE and are making all they can to support and develop all that samsung does not give to the community.
As for me I love CM, but don't use it in my i9300 (occasionally make a nandroid backup and do a clean install of CM just for fun and testing) but I do in my Nexus 7 and i9000.
Also always remember that without a logcat almost no one will take you serious, I'll try to reproduce your issue in todays nightly and see if I get the camera issue, I'm no dev but I'll do whatever is needed to see CM work as it should.
Solaris_irc said:
Hi aharnick2013,
The last nightly I tried for CM10.1 was 06/17/2013 and the camera was working fine, apart from the usual audio bugs and poor camera performance.
I'm not sure about AOKP and AOSP, but for what I see in the CM changelogs, some parts of the sensor drivers in the kernel will be back ported from a previous release for the nightly of 06/20/2013, not sure if this has to do with the issue you are having as I never experienced myself in CM.
To be included in next nightly:
Derp fix. (android_frameworks_base)
Hide navigation ring if no targets are configured. (android_frameworks_base)
Cleanup. (android_frameworks_base)
Close notification panel when swiping away the last clearable notification. (android_frameworks_base)
Add media-caf repository (android)
u1: port sensors and modem interface from smdk4210 kernel (android_kernel_samsung_smdk4412)
Camera: Add a GPS indicator (android_packages_apps_Camera)
Check and fail early if requested wallpaper size exceeds maximum texture size. (android_frameworks_base)
Lockscreen : Fix widgets disabled (android_frameworks_base)
Fix ringer mode being unneededly changed by setting ringer mode volume to 0. (android_frameworks_base)
Squashed commit of A/V changes from CodeAurora (android_frameworks_av)
Also take into account that the i9300 is a tough nut to crack, because of samsung, and the guys at AOSP and CM are working for FREE and are making all they can to support and develop all that samsung does not give to the community.
As for me I love CM, but don't use it in my i9300 (occasionally make a nandroid backup and do a clean install of CM just for fun and testing) but I do in my Nexus 7 and i9000.
Also always remember that without a logcat almost no one will take you serious, I'll try to reproduce your issue in todays nightly and see if I get the camera issue, I'm no dev but I'll do whatever is needed to see CM work as it should.
Click to expand...
Click to collapse
Thanks, I just found a fix for AOSP roms. Flash Siyah kernel 1.9.1 after installation and boot of AOSP rom then reboot = Camera working.
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.
SlimLP is the project name for SlimRoms based on Android 5.x 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.
Bugs
The bugs on this rom that i have seen are the same as the CM 12 bugs
Major key changes from SlimKat 3 are as follows:
Notification reminder: An easy way to quickly set short reminders to show on the notification drawer.
Slim Recents: A complete replacement of the AOSP recents screen to allow better multitasking, along with marking favourite apps.
Dialer: Introduced with SlimKat 3: forward lookup and reverse lookup of contacts. Sadly we needed to remove certain parts due to legal issues with the Google+ reverse lookup. An intelligent People lookup service has been added to replace this, along with several other enhancements.
Quiet Hours: Several tweaks and enhancements to make it more powerful than previous.
Lockscreen: Further color enhancements and options.
And of course tons of small changes, features, enhancements and fixes all over the firmware.
DOWNLODS
https://drive.google.com/file/d/0B2oKFrNf-r_KXzVqUEhlMmFoN1E/view?usp=sharing
XDA:DevDB Information
[ROM][SlimLP Unofficial][5.1.1] , ROM for the Sony Xperia Z3
Contributors
jonte28
Source Code: https://github.com/SlimRoms
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Beta
Created 2015-06-12
Last Updated 2015-06-13
Nice rom
thanks for this rom
I stop xda now I have too much with my school
Do u need an unlocked bootloader ?
fabilaaaa said:
Do u need an unlocked bootloader ?
Click to expand...
Click to collapse
Yes
is this aosp or cm based and can u change recent back to default
Hi all,
I'm trying to find a resource that explains what files and systems control various mid- to low-level aspects of an Android ROM.
For example, I'm looking for a resource that explains:
How to change the System UI volume change sound
How to calibrate the accelerometer threshold that controls screen rotation
How to control system app priority (keep something running and awake)
The volume one in particular may seem a little trivial, but I'm researching a project that aims to tighten some aspects of the Android UX, and these elements are critical.
Any direction would be extremely helpful!
Hi all, I have a conceptual gap. Why are all of the custom ROMS in our dev section based on either Stock or CM13?
Stock makes sense to me; it's taking what we have and modifying it.
So what is special about the CM13 development that others are unable/unwilling to do?
Thanks
CM 13 is one of the most stable and popular ROMs around. Most of the developers try to develop for CM13 because of it's closeness to stock Android (although it has it's own useful features). If any other developer wants to bring new features to him own custom ROMs they generally pick up CM13. Part of the reason may be due to the number of users of CM. There are millions. And they have a great community.
Known CM issues:
* Camera hangs and sucks batttery like crazy if you do 2 hdr photos. Don't use hdr.
* dt2wake doesn't use the proximity sensor to filter bogus d2twake triggers and therefore can turn on too easily in your pocket.
* Fingerprint sensor not yet implemented! (Do not even ask for it, search the thread!)
I posted the following question a few days ago, but there have been no replies.
https://forum.xda-developers.com/nexus-6p/help/adjust-screen-gamma-value-t3651947
So, I just wonder if screen gamma value is adjustable in Android at all? Of course it is unlikely to be achievable in stock ROM's, but what if you are using a custom ROM that you can build from source?
Or is the gamma value fixed in hardware or in the binary from the manufacturer that custom ROM developers cannot modify?