yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] siljaer:
Reserved

Changelog

20171021: update kernel to LA.BR.1.2.9-03710-8x16.0. Security fixes (Blueborne and KRACK).

20170820: New GPS blobs from crackling. In my case, it resulted in improved GPS precision. People with overheating problem, please let me know if it improves the issue.

20170730: New Thermal blobs from crackling. New thermal engine configuration. Hopefully, that should prevent overheating.

20170709: New GPU blobs from crackling. Because of a case of reported overheating, several drivers were added in kernel config. Some related SELinux denials were addressed. Something strange was also found in Trunk's DTs: GPIO pins for the tps65132 were wrong, leading to failed driver probe (however, that happens in stock rom too). Correct values for them was added. However, real effectiveness for those changes in preventing overheating is to be proved.

20170618: Fixed reboot to recovery (and automatic updates). Using again Trunk's Camera HAL.

20170603: now compatible with 64bit opengapps, fixed start recording sound at beginning of video recordings, SELinux fixes (by [MENTION=7319300]ottmi[/MENTION]), long press of home key now shows recent apps.

20170529: update kernel to LA.BR.1.2.9-02910-8x16.0

20170526: first build
[Miscellaneous Android Development] josoft86:
[MENTION=7529884]siljaer[/MENTION]

Happy for your new job I'll let you know my impression after installing and testing it. I am currently using the "aicp_peach_n-12.1-NIGHTLY-20170526.zip" rom with great efficiency with up-to-date OTA updates at the same time as the Open Gapps update. It's just 32bit and has been made for "ARK Benefit A3" and not for our Elephone Trunk. It would be interesting, for the many extra functions of this rom, its fluency, the OTA updates, to recover all that has good and transfer it to your rom, even that I saw that something you used as a contribution from "lolmaxlik_ru". In any case thank you for your work and I apologize if I have been able to give you that imput.
[Miscellaneous Android Development] ve66:
Hi siljaer, I would like to test your ROM. I'm using ottmi's ROM but I have some problems: i.e. focus problem on the camera, camera works only for photo and non for videos, sometimes I have random reboots.... So I would like to try: which TWRP should I use? may I use gapps? what are the wipes that I need: can you describe me a sequence? TKS
[Miscellaneous Android Development] siljaer:
Sorry for the delay. You can use the same TWRP you're using now. The sequence is exactly the same one described by [MENTION=7319300]ottmi[/MENTION] for his rom. And you can use gapps, 64bit. Your feedback will be very appreciated!

As for the wipes, I am afraid that you have to wipe everything except internal sd card :( For later flashings, you don't have to wipe anything.

First time boot takes several minutes, wait some time.

Thanks!
[Miscellaneous Android Development] siljaer:
opengapps 64/32 bit!

Actually there's a problem and you can only flash 32 bit gapps. I have fixed this and I am uploading the build later.
[Miscellaneous Android Development] siljaer:
I uploaded the fixed build. Now you can install 64bit opengapps. Since the previous builds were 64bit but they used zygote32 (a mistake) I deleted them.
[Miscellaneous Android Development] ve66:
Ok, now I will download this new build. Tomorrow I think to install and then I'll send U my feedback

Inviato dal mio trunk utilizzando Tapatalk
[Miscellaneous Android Development] siljaer:
OMS/Substratum working

BTW, for those interested in theme engines, I have tested Substratum and it works without root.
[Miscellaneous Android Development] siljaer:
Thanks!
[Miscellaneous Android Development] ve66:
Ok, my feedback:

I wiped cache, dalvik, data and system, then I flashed the ROM and after I flashed the gapps. After reboot I didn't reach to configure the telephone: it appeared me this message "L'app Configurazione guidata si è interrotta" and there isn't a way to configure the telephone. I'm writing from the PC 'cause the phone is out of service. I see the BT icon opened on the right-top of the screen, I don't know if this can help (you told you had problems with BT....). What do you suggest me to do?

EDIT: I flashed the ROM once again without Gapps, I did it two times but without any success, I also had a couple of random reboots
[Miscellaneous Android Development] siljaer:
What do you mean with "without any success?"
[Miscellaneous Android Development] ve66:
I had to power off. I want to say that to make my telephone works I had to reinstall otttmi's ROM. In fact, also if i did a backup just after flashing your ROM, it was impossible to reload the backup. I think it's because - wiping all cache, dalvik, data and system - I deleted also parts that could contain parts of the backup. I reached to have some screenshot, tomorrow I'll post here
[Miscellaneous Android Development] ve66:
This is what happenedView attachment 4171496

Inviato dal mio trunk utilizzando Tapatalk
[Miscellaneous Android Development] siljaer:
When did you do a backup? Did you backup your data online? From the screenshot, it looks like the restore application failed.
[Miscellaneous Android Development] Bizen-Ya:
Hi,

With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.

Thank you

---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------

Ok i have reformated my /data from f2fs to ext4, it's ok now.
[Miscellaneous Android Development] siljaer:
Yes, f2fs is not enabled. I don't know enough about its reliability with CAF kernel.
[Miscellaneous Android Development] siljaer:
gapps and camera

BTW, if you're installing gapps I would suggest a flavour that does not replace default applications. Otherwise you will lose Snapdragon Camera that in my opinion is much better than google (legacy, as we use an old HAL) camera.
[Miscellaneous Android Development] josoft86:
@ siljaer

Tried the ROM using TWRP-3.0.2-20161108-trunk.img, without installing gapps as recommended. Pretty fluid without breaks and quite complete without so many customizations. Problems with Smart Launcher does not activate the home key for shutdown or recovery commands. Weekly update to switch to version 20170611 all OK download but failed restart for flash with recovery. Tried several times but nothing to do. Obviously using either Launcher 3 or OmniSwitch. Installed TWRP manual and all OK. By the way, with the first installation I installed Supersu, which I did not find after updating. This is my first impression.
[Miscellaneous Android Development] megalon59:
New trunk installation

4 days ago I installed the trunk of my wife with the image omni-7.1.2.-20170604-trunk-WEEKLY. The first impressions are very positive. I especially the charging of the battery seems to be faster. Within an hour, approximately 80% of the battery will be charged.

When I connect the mobile phone to the PC, however, does not appear with me a removable disk. However, I can issue ADB commands. Is this correct?

The change to the new version of yesterday I have not yet carried out. I'm waiting for my wife to like the new Android.
[Miscellaneous Android Development] siljaer:
I have fixed the restart problem and I have pushed the changes. Meanwhile, camera stopped working, so I switched back to the ottmi's HAL, so camera's working again. Those changes should be in the next weekly build. Thanks to [MENTION=6487919]josoft86[/MENTION] :)
[Miscellaneous Android Development] siljaer:
Sorry for the delay. File transfer is not enabled by default in many android builds. You can click on the "USB charging this device" notification, the click "Transfer Files". To enable it permanently, you have to enable developer options (Settings-> About Phone, then click 7 times on "Build Number") then Settings -> Developer Options ->"Select USB configuration"

Thank you for trying my ROM. BTW, it is still a work in progress. If you need a stabler and feature richer ROM, you can try also ottmi's LineageOS: https://xdaforums.com/android/development/rom-lineageos-14-1-elephone-trunk-t3554011
[Miscellaneous Android Development] megalon59:
Thanks for the answer.

But the change I have already done. I think it is a problem of Windows drivers. Here I will try something else.

I noticed, however, that the mobile phone is very quickly charged. But the power consumption is also much higher than before.

It's probably because of the many apps. I have the open_gapps-arm64-7.1-stock installed. Which version would you recommend?
[Miscellaneous Android Development] siljaer:
I don't think there's a problem with windows drivers: AFAIK file transfers should work out of the box (because usb storage is normally integrated), unlike adb debugging which requires drivers.

I appreciate your feedback about battery life and I will try to investigate. Meanwhile, you can try the LineageOS ROM. Gapps decrease battery life, that's a fact, because many apps are working in background. Which version of Gapps is a matter of preference, it depends on which google apps you actually use. I've read that most of people suggest pico or nano, unless you need some functionality not available on the store but included in micro or mini. Pico and nano will probably increase your battery life. Stock is the complete set of gapps, my only suggestion is to use full instead, because it's the same set, but it does not replace non google apps, allowing you to keep the Snapdragon Camera. My choice is a radical one, since I don't use gapps at all and my only store is F-droid :)
[Miscellaneous Android Development] siljaer:
New weekly is on omniROM's downloads (http://dl.omnirom.org/trunk/omni-7.1.2-20170618-trunk-WEEKLY.zip) and it includes those changes.
[Miscellaneous Android Development] josoft86:
[MENTION=7529884]siljaer[/MENTION]

Installed version of 18, OK tutton has a strange difficulty installing wifi. The ID is regularly saved but can not connect. Controlled IMEI, disabled data, disabled and restored wifi, but nothing to do even after turning off and restarting. With the other Roms ever had this problem and on the other smart Elephone P6000 android 7.1.2 no connection problem with the same network and same ID. Can you give me some explanation ??? In any case rom very fluid and fast customization capability not yet at AICP level. Wishing you a good job and continues so even waiting to test the automatic restart.
[Miscellaneous Android Development] saboy1976:
siljaer this ROM is very good. I've installed it one week ago, and i have no problems. The only bug is the temperature of the phone when I use data connection or my GPS application (Tomtom Go).The phone is so heat that it power off. I there a way to increase value of the temperature so that phone doesn't stop anytime. Thanks.
[Miscellaneous Android Development] siljaer:
Thank you for reporting this. I have never experienced any power off, but I know that some heating occurs when using data connection. I have tried some change, but if you are using the latest weekly they were ineffective. Currently, I am trying the new thermal engine (latest binary), but I have not pushed it yet. I am sorry, but I haven't found a good solution yet :(

I will try to reproduce the problem using GPS too. Maybe it occurs with both GPS and data connection on.
[Miscellaneous Android Development] siljaer:
Some news about overheating:

- I have been testing new crackling thermal binaries for a while, now I consider them safe and I pushed them. I hope they can make a difference.

- I have also tried to rewrite the thermal engine configuration; I have added a modem_monitor in order to throttle modem performance when overheating occurs. Most of you experience overheating while using 4G or telephone and I have experienced a temperature increase while using 3G-4G.

- Unfortunately, I have not been able to reproduce the problem. However, I have enabled thermal debugging. So, if any of you can trigger overheating, they can use logcat and send me the logs.

These changes are already pushed and ready to be in the next weekly, 30th July (probably). That gives me some more time to test them :)
[Miscellaneous Android Development] ve66:
Hi siljaer, I'm downloading it on my pc. As you know I don't reach to update via mobile so the only way to do it is to download the rom, transfer it on my sd and then flash it from there. I hope to solve my problems with rebooting, anyway I've ordered a new Vernee Thor, also because the screen of the camera is broken as the back cover too and I couldn't find any spare parts. When I'll receive my Thor I will move the sim in it and the Trunk will work without it and only via WiFi but I firmly want to continue to test your rom, so if you have any question let me know. Many thanks for Ur work :good:
[Miscellaneous Android Development] siljaer:
I hope you're enjoying your new phone :) BTW, I have updated the GPS blobs. Since it looks like overheating problem occurs when using GPS, let me know whether this change has any effect.
[Miscellaneous Android Development] dimqua:
Are there any reasons why the kernel version so old? I mean 3.10.49 instead of 3.10.104 or later (3.16, for example).

This is 3.10.104 source code: github.com/BenefitA3/android_kernel_ark_msm8916/tree/ZetsuBou

May be there are newer versions too, I don't know for sure. :)

P.S. Your firmware works great on my ARK Benefit A3. Thanks. :good:
[Miscellaneous Android Development] ve66:
Hi Sil, in August I've updated the ROM regularly every week but my Trunk continue to switch off in a lot of situations: it happens when I use it in any app, also during normal calls, so I can't be sure it is due to a particular situation of use. As I told U some times ago maybe I made a mistake during a past flash and I have damaged my phone.

More: as you can see from the photos, case and camera glass are really in bad condition, for this reason I decided to buy this new cell with whose I'm writing. Maybe I will use my Trunk at work with another sim with the OMNI ROM

Inviato dal mio thor utilizzando Tapatalk
[Miscellaneous Android Development] siljaer:
Since you have another phone now, and the trunk is a bit weary, you could also try reflashing it with the Qualcomm tool...
[Miscellaneous Android Development] siljaer:
Yes, there's a reason: I am using the CAF kernel with a minimal set of changes. I have also tried the kernel by ottmi (LineageOS based), that is probably better, but I was not sure it would work in any circumstances, as Omnirom suggest CAF or AOSP kernels. However, the 3.10.49 CAF kernel is continuously updated by Qualcomm (about monthly), and I am updating accordingly.

The 3.10.104 or 105 are AOSP kernels. However, since the available kernel is for the google seed and it is 32 bit, it would require some more changes.

As far as I know, we cannot use 3.10+ kernels like 3.16 on the trunk, because we are forced to use proprietary binary blobs that work with 3.10 kernels. This is an issue with any phone, though: actually you can use a newer kernel version only if updated binary drivers are released for any device on your phone. Besides, android is very conservative with kernels: I think that the newest kernel in use are 3.18, in some Mediatek and Qualcomm devices.
[Miscellaneous Android Development] dimqua:
Do you know why LineageOS kernel is CAF-based and not AOSP-based? :)

BTW, where I can get the latest AOSP kernel source code?
[Miscellaneous Android Development] siljaer:
AFAIK, CM kernel was an CAF-AOSP hybrid. However, I guess it's mainly CAF based because of better performance...

here: https://android.googlesource.com/kernel/

you are probably looking for common/android-3.10 or common/android-3.10y
[Miscellaneous Android Development] siljaer:
Thanks for your feedback. I am surprised it can work well on A3: the Trunk has 2GB RAM, while A3 has 1GB. And I disabled zram, that should have some effect on A3 (I haven't done so to hinder A3, though :) ).
[Miscellaneous Android Development] siljaer:
Omnirom is still updating some builds once in a while, as they are working hard with Oreo. But not trunk's: unfortunately, the Blueborne vulnerability must be fixed in order to make a build.

I am using the CAF kernel, and a fix has not been released yet (at least I have not found it). I could cherrypick the fix from other kernels, but I am not sure it will work without problems. Eventually, if CodeAurora does not fix it, I will have to by cherrypicking.

About Oreo, I guess there's still a lot of work (by Omnirom team, not by me) to do. And CAF code for msm8916 has not been released yet either.

I hope to fix my build ASAP.
[Miscellaneous Android Development] dimqua:
Will Trunk get Oreo (Omni, LOS) any time soon?
[Miscellaneous Android Development] siljaer:
Definitely not soon: Omnirom team is still working hard on Oreo, but the alarming thing for the trunk is the lack of official Oreo CAF releases for msm8916 so far...
[Miscellaneous Android Development] dimqua:
Is OmniROM based on CAF AOSP variant, or you just mean the kernel?
[Miscellaneous Android Development] siljaer:
Omnirom uses code from CAF (mostly HALs: sound, display and so on). If there's no Oreo code for such msm8916 HALs, it's much more complicated. Not impossible, though, I have read that some other mods are working on it.
[Miscellaneous Android Development] dimqua:
There're AOSP-based ROMs for Redmi 2 and Lenovo A6000, for example, both uses 3.10.x kernels and the same CPU as Trunk.
[Miscellaneous Android Development] siljaer:
those ROMs are 32-bit... I would like a 64-bit ROM. AOSP 3.10.x kernel requires many more changes in order to work with a 64-bit build. However, the A6000 developer is waiting for an Oreo Omnirom release, the he will start working with A6000 :) It's good news, since if it can be done for A6000, it could be done for trunk too. We'll see.
[Miscellaneous Android Development] siljaer:
Security fixes

As you know, while working with Oreo, omnirom team is releasing security updates builds.

I have fixed the Blueborne vulnerability (late, but official CAF patch is yet to come, so I had to copy it from seed) and Omnirom fixed KRACK.

Next build should be available shortly.
[Miscellaneous Android Development] dimqua:
I'm curious, are there any benefits of using 64-bit kernel with 32-bit userspace, compared to 32-bit kernel+userspace? At least, theoretically.
[Miscellaneous Android Development] siljaer:
A small performance increase, according to ARM: https://www.arm.com/files/event/C2_...ource_Project_Applications_and_Advantages.pdf

And the other advantages of a more advanced ARM architecture. Nothing really game-changing, but why not?

BTW, I am not completely sure that the userspace is 32-bit only: I thought it was 64/32-bit. Can you elaborate on that? (vendor libs for trunk include a 64-bit version for most of them).
[Miscellaneous Android Development] dimqua:
In general, yes.

I'm taking about, for example, these builds for ARK. They are 32-bit, bit it's possible to replace the kernel with 64-bit version (by ottmi). But I'm unsure that it has any sense, since the userspace remains 32-bit in this case.
[Miscellaneous Android Development] siljaer:
I guess they offer a negligible advantage, if any. A 32/64 bit android system is purposedly built this way. However, I managed to build such a system (64 bit kernel, 32 bit userspace) by mistake, and it worked so well it took quite a long time for me to realize the error :)
[Miscellaneous Android Development] dimqua:
http://news.softpedia.com/news/linu...e-urged-to-move-to-linux-4-4-lts-518407.shtml

Any chance to get v3.10.108 CAF kernel?
[Miscellaneous Android Development] siljaer:
None, I guess. That's because CAF versioning scheme is different, even though the kernel is costantly updated, even with contributions from mainline kernel. Don't ask me why :)
[Miscellaneous Android Development] dimqua:
Here's an information, that upstream merges are not merged into CAF. Probably, that's why.
[Android Q&A, Help & Troubleshooting] Nikola010:
I need to do some image processing in real time on mobile. I am using camera2 library. I managed to put camera preview directly on surfaceView but when i redirect it to ImageReader to do something with frames before i preview them it goes really slow, and there is not even processing just taking Y value from YUV_420_888 and converting it to gray picture in ARGB_8888 format. Code is below. For that one for loop i need about 600ms. And for image processing i will need to go trough that image at least one more time. In Bits array i form ARGB_8888 format out of Y array which is Y value of YUV_420_888 format. I test it on phone with Quad Core 1ghz processor and 1gb ram. Is there any way to speed this code up so i can go lets say 2-3 times trough picture and have at least 7-10 fps? If i delete for loop and just measure fps its 8-12fps. Why is it so slow compering to 25fps when i put it directly on surfaceView?

private final CameraDevice.StateCallback mStateCallback = new CameraDevice.StateCallback() {

@Override
public void onOpened(@NonNull CameraDevice cameraDevice) {
// This method is called when the camera is opened. We start camera preview here.
mCameraOpenCloseLock.release();
mCameraDevice = cameraDevice;
createCameraPreviewSession();
mImageReader.setOnImageAvailableListener(new ImageReader.OnImageAvailableListener() {
@Override
public void onImageAvailable(ImageReader reader) {
Image image = reader.acquireLatestImage();
if(image != null) {
ByteBuffer buffer0 = image.getPlanes()[0].getBuffer();
byte[] Y = new byte[buffer0.remaining()];
buffer0.get(Y);

byte[] Bits = new byte[Y.length*4]; //That's where the RGBA array goes.

int Ylength = Y.length;

for (int i = 0; i < Ylength; i++) {
int i1 = i*4;
Bits[i1] =Y[i];
Bits[i1 + 1] =Y[i];
Bits[i1 + 2] = Y[i];
Bits[i1 + 3] = -1;//0xff, that's the alpha.
}

Bitmap bm = Bitmap.createBitmap(image.getWidth(), image.getHeight(), Bitmap.Config.ARGB_8888);
bm.copyPixelsFromBuffer(ByteBuffer.wrap(Bits));
Bitmap scaled = Bitmap.createScaledBitmap(bm, surfaceView.getWidth(), surfaceView.getHeight(), true);
Canvas c;
c = surfaceHolder.lockCanvas();
c.drawBitmap(scaled, 0, 0, null);
surfaceHolder.unlockCanvasAndPost(c);
image.close();

time2 = System.nanoTime();
Log.d("Vreme",Double.toString(1000000000/(time2-time1))+"fps");
time1 = System.nanoTime();

}

}
},mBackgroundHandler);

}

@Override
public void onDisconnected(@NonNull CameraDevice cameraDevice) {
mCameraOpenCloseLock.release();
cameraDevice.close();
mCameraDevice = null;
}

@Override
public void onError(@NonNull CameraDevice cameraDevice, int error) {
mCameraOpenCloseLock.release();
cameraDevice.close();
mCameraDevice = null;

}

};
[Samsung Galaxy S8+ Guides, News, & Discussion] nicholaschum:
So I was just a bit confused with the sheer amount of small threads that try to answer questions regarding the Korean variant of our beloved device with consistent questions and answers floating around, so this guide aims to consolidate those threads as it seems like we need a unified thread for this variant.

System Specs provided by [MENTION=5063250]murtaza02[/MENTION]

Model Number: SM-G955N

Country of Production: South Korea

Carriers: LG U+, SK Telecom, KT

2G: 900, 1800, 1900 MHz

3G (UMTS/HSPA): 850, 1900, 2100 MHz

4G (LTE): B1, B2, B3, B4, B5, B7, B8, B12, B13, B17, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41, B46

SoC: Samsung Exynos 9 Octa (8895)

RAM/Internal: 4GB / 64GB or 6GB / 128GB