Database Users

Sony Mobile Battery Testing App [Version 1.13.0]

Sony Mobile Battery test application.
the archive includes adb drivers and instructions.
Description
New version 1.13.0 Sony Mobile Battery test application is prepared for
Xperia Acro S (LT26w),
Xperia AX (SO-01E),
Xperia C (C2305, S39h),
Xperia Go (ST27i ,ST27a),
Xperia GX (SO-04D),
Xperia Ion (LT28at,LT28h,LT28i),
Xperia P (LT22i),
Xperia S (LT26i),
Xperia SL (LT26ii),
Xperia Sola (MT27i),
Xperia SP (C5302, C5303, C5306, M35c, M35h) ,
Xperia T (LT30p),
Xperia TL (LT30a,LT30at),
Xperia TX (LT29i),
Xperia V (LT25c,LT25i),
Xperia VL (SOL21),
Xperia Tablet Z (SGP311, SGP312, SGP321,SGP341, SGP351, SO-03E) ,
Xperia Z (C6602,C6603,C6606,C6616,L36h,SO-02E),
Xperia Z Ultra (C6802,C6806, C6833, C6843, XL39h) ,
Xperia Z1 (C6902, C6903, C6906, C6943, SO-01F,SOL23)
Xperia ZL (C6502, C6503, C6506, L35h),
More products will follow.
This test is designed to identify a faulty battery or a hardware issue in the phone or with the charger.
The guide will describe different procedures depending on the battery level when the battery test is initiated.
The following equipment is needed to do the installation and perform the test:
• Computer with Bluetooth device or Computer and EC480 [Micro USB] cable to transfer the application to the phone
• An EP800 [Mains] charger and EC480 [Micro USB] cable is regarded as reference equipment when trouble shooting
the charger system if the users charger/cable has been returned together with the phone and battery
• SD card to install the application if no internally memory is available.(other models)
RELEASE NOTES - 2013-11-03
--------------------------------
Version 1.13.0 Added support C6843 and C6943.
Version 1.12.0 Added support for M35t.
Version 1.11.0 Added support for C6806, C6933, C6902, C6903, C6906, L39h, SO-01F and SOL23
Version 1.10.0 Added support for C2305 and S39h.
Version 1.9.0 Added support for C6616, C6802 and XL39h.
Version 1.8.0 Added support for C5302, C5303, C5306, M35c and M35h.
Version 1.7.0 Added support for C6606, SGP311, SGP312, SGP321, SGP341 and SGP351
Version 1.6.0 Added support for SO-03E
Version 1.5.0 Added support for C6502, C6503, C6506 and L35h
Version 1.4.0 Added support for C6602, C6603, L36h and SO-02E
Version 1.3.0 Added support for LT25c, LT25i, LT28at, LT28i, LT30a, LT30at, SO-01E and SOL21
Version 1.2.0 Automatic driver installation added. Added support for LT28h, LT29i, LT30p and SO-04D
Version 1.1.0 Added support for ST27i, ST27a, LT26i, LT26ii and LT26w.
Version 1.0.0 Added support for LT22i and MT27i .
Download
DevHost
EmbedUpload

Good, I try in my Xperia TX LT29i and it's work...
And all result PASS.......
Thanks...

Great Thanks to share, i also tried, its very helpful :good:

Any can reupload? Thanks for advance!

Can you please Support for Xperia ZR (C5502)?

NEOCRIVI said:
Any can reupload? Thanks for advance!
Click to expand...
Click to collapse
http://d-h.st/Agp
you can still down it here, just need to disable adblocks and make sure you are downloading a file that's 16MB, not the 3MB version as it might be adware or something
Daedroza said:
Can you please Support for Xperia ZR (C5502)?
Click to expand...
Click to collapse
I think this is from Official Sony so there won't be support for your request

hii...i have xperia z and i installed this apk test but is saying to me: model is not suported. I have rom resurection remix cm13...can u tell me which can be the problem?

op3n said:
hii...i have xperia z and i installed this apk test but is saying to me: model is not suported. I have rom resurection remix cm13...can u tell me which can be the problem?
Click to expand...
Click to collapse
Same Problem with the same Rom Here
Can anybody tell me that if i have a full Nandroid backup of my present custom Rom & then install a StockRom, when i do a Full Wipe and restore my past Backup, now can i exactly have my previous Custom Rom with full settings ?! (without any failure!)
Sorry for my bad English.. Plz Help me

Cyrus_Persian said:
Same Problem with the same Rom Here
Can anybody tell me that if i have a full Nandroid backup of my present custom Rom & then install a StockRom, when i do a Full Wipe and restore my past Backup, now can i exactly have my previous Custom Rom with full settings ?! (without any failure!)
Sorry for my bad English.. Plz Help me
Click to expand...
Click to collapse
you can do full backup,via twrp. check all boxes and set on sdcard; after that u can flash official rom and come back on resurection when u will want. will work (i tested it).

op3n said:
you can do full backup,via twrp. check all boxes and set on sdcard; after that u can flash official rom and come back on resurection when u will want. will work (i tested it).
Click to expand...
Click to collapse
thank u so much Dear

Cyrus_Persian said:
thank u so much Dear
Click to expand...
Click to collapse
u are welcome, but im not a girl to say to me "dear" ))))

LINKS FOR SONY TEST APP download TROJANS and COINMINERS > AVOID !!
The links from this page which are meant to enable a download of "Sony Mobile Battery Tester.rar" will get anyone who clicks on them some nice Infections !
- Is it too much to ask to put a downloadable file in a google drive or dropbox ?
Surprised that XDA allows this type of thing at ALL - not good for the rep XDA and droid102 !!
tried for past hour and only managed to get INFECTED...TWICE !!
NOT HAPPY

Do anyone still have the apk file of this xperia z battery test app? Cause all the links in this post are broken

JoshuaX12 said:
Do anyone still have the apk file of this xperia z battery test app? Cause all the links in this post are broken
Click to expand...
Click to collapse
Here you go
https://mega.nz/#!xAIiAQBA!7bUDJ3P6GdkDSndqV23gpIQeOI-X-Ndte_DYtXHUBhg
...
...

kulvertti said:
Here you go
https://mega.nz/#!xAIiAQBA!7bUDJ3P6GdkDSndqV23gpIQeOI-X-Ndte_DYtXHUBhg
...
...
Click to expand...
Click to collapse
Thank you very much

Samsung note (N7000) wallpapercropper issue

Hi there.
I'm using OmniROM 20150520 (the final) on my N7000.
Some time ago I faced with problem: when I try to set wallpaper to lockscreen, after wallpaper chosen and cropping action expected, I'm getting message like "application "com.android.wallpapercropper" error".
Which could a reason of the problem be?
I'm using OmniROM a long time. Had no mentioned bug on prevoius versions and on the final one first time also. For now reinstallation of the firmware and dalvik's wipe give no results.

demonx993x said:
Hi there.
I'm using OmniROM 20150520 (the final) on my N7000.
Some time ago I faced with problem: when I try to set wallpaper to lockscreen, after wallpaper chosen and cropping action expected, I'm getting message like "application "com.android.wallpapercropper" error".
Which could a reason of the problem be?
I'm using OmniROM a long time. Had no mentioned bug on prevoius versions and on the final one first time also. For now reinstallation of the firmware and dalvik's wipe give no results.
Click to expand...
Click to collapse
Not sure... N7000 has been abandoned for a long time, it was basically coasting on inertia for months. As the device no longer has a maintainer, nothing is going to get fixed.

Entropy512 said:
Not sure... N7000 has been abandoned for a long time, it was basically coasting on inertia for months. As the device no longer has a maintainer, nothing is going to get fixed.
Click to expand...
Click to collapse
Thanks Entropy512, I'm sure you are right. BTW, I saw only one new Android mod (based on CM12.1) for N7000, but it has no direct attention to Omni.
Nevertheless, it seems, the mentioned issue is not linked with FW own bugs because there was no problems first time after installation.
Suppose, the issue could be linked with errors of file system, or paths and permissions, or even third party software influence (unlikely).
I couldn't find algorithm of wallpapercropper work (where does it place current lockscreen wall files, how should them be named, which system files/properties does it change and to which files/folders should it have permissions) to try fixing manually.
Could you help me with this?

There is log of wallpapercropper operation, where errors appear, below (gotten by Catlog SW)
build.board: smdk4210
build.bootloader: unknown
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: n7000
build.display: omni_n7000-userdebug 4.4.4 KTU84P 560 test-keys
build.fingerprint: samsung/omni_n7000/n7000:4.4.4/KTU84P/560:userdebug/test-keys
build.hardware: smdk4210
build.host: devbox.omnirom.org
build.id: KTU84P
build.manufacturer: Samsung
build.model: GT-N7000
build.product: omni_n7000
build.radio: unknown
build.serial: 001a7a0708dc9e
build.tags: test-keys
build.time: 1432164566000
build.type: userdebug
build.user: jenkins
version.codename: REL
version.incremental: 560
version.release: 4.4.4
version.sdk_int: 19
11-12 21:49:32.698 I/ActivityManager(2362): START u0 {cmp=com.android.wallpapercropper/.LockscreenWallpaper} from pid 6093
11-12 21:49:32.923 I/ActivityManager(2362): Displayed com.android.wallpapercropper/.LockscreenWallpaper: +205ms
11-12 21:49:53.498 E/MediaStore(6148): at com.android.wallpapercropper.LockscreenWallpaper.cropImage(LockscreenWallpaper.java:232)
11-12 21:49:53.498 E/MediaStore(6148): at com.android.wallpapercropper.LockscreenWallpaper.onActivityResult(LockscreenWallpaper.java:343)
11-12 21:49:53.563 E/AndroidRuntime(6148): Process: com.android.wallpapercropper, PID: 6148
11-12 21:49:53.563 E/AndroidRuntime(6148): java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1024, result=-1, data=Intent { dat=content://media/external/images/media/92730 flg=0x1 }} to activity {com.android.wallpapercropper/com.android.wallpapercropper.LockscreenWallpaper}: java.lang.NullPointerException: uriString
11-12 21:49:53.563 E/AndroidRuntime(6148): at com.android.wallpapercropper.LockscreenWallpaper.cropImage(LockscreenWallpaper.java:233)
11-12 21:49:53.563 E/AndroidRuntime(6148): at com.android.wallpapercropper.LockscreenWallpaper.onActivityResult(LockscreenWallpaper.java:343)
11-12 21:49:53.568 W/ActivityManager(2362): Force finishing activity com.android.wallpapercropper/.LockscreenWallpaper
11-12 21:49:54.068 W/ActivityManager(2362): Activity pause timeout for ActivityRecord{421b9250 u0 com.android.wallpapercropper/.LockscreenWallpaper t9 f}
11-12 21:49:55.778 I/WindowState(2362): WIN DEATH: Window{42191228 u0 com.android.wallpapercropper/com.android.wallpapercropper.LockscreenWallpaper}
11-12 21:49:55.778 I/ActivityManager(2362): Process com.android.wallpapercropper (pid 6148) has died.

Hello everyone, is there some info for me?

Hi there, still no any info?

I already gave you all the info you're going to get (unless you fix this yourself) in my last post - no one is maintaining this device any more and has not for over two years now, so it's not going to get fixed.

Entropy512 said:
I already gave you all the info you're going to get (unless you fix this yourself) in my last post - no one is maintaining this device any more and has not for over two years now, so it's not going to get fixed.
Click to expand...
Click to collapse
I just hoped someone could clarify java exceptions).

Android Oreo 8.0 / Lineage 15.0 Dev Discussion

Currently on hold due to working on Nougat first.
I've got a booting or should I say bootlooping build of Lineage 15.0 for I9000. (galaxysmtd)
I've had to use crazy hacks like adb binary from 7.1 in ramdisk.
Just to get `adb logcat` working.
For now it's stuck at bootlogo. I've attached the logcat here.
I'm looking into it to figure out what needs to be done.
Sources:
manifests and patches I've used.
https://github.com/galaxys1-resurrected/local_manifests
https://github.com/galaxys1-resurrected/android_patches
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
Device Tree:
https://github.com/galaxys1-resurrected/android_device_samsung_aries-common
https://github.com/galaxys1-resurrected/android_device_samsung_galaxysmtd
Thanks:
@rINanDO for backporting kernel side of things to 3.0
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1
And all others who had worked from beginning till now on this device.

Is there anyone still working on this?
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.

a1shakes said:
I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.
I went through the logs and a couple of things jumped out:
1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.
2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.
3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.
For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:
Code:
// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.
I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.
Even if this might not work out, I would like to thank @(°_o), @xc-racer99 , @Coldwindofnowhere and @rINanDO for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
Click to expand...
Click to collapse
Unfortunately, no one is really actively working on Oreo. As you've found out, it's an issue with the graphics drivers that is holding everything back. No device (that I've found) that uses a PowerVR graphics chip (we use the PowerVR SGX 540) has working graphics drivers on Oreo. There were rumours that someone had found newer working blobs, but weren't able to release them publicly due to intellectual property laws that they were trying to figure out (but this was months ago).
Our GPU does support sufficient enough OpenGL, but only using BGRA8888 as opposed to RGBA8888. BGRA hasn't officially been supported in Android since ~4.2, but there's been a hack used to make things work. Come Oreo, things have changed and the hack no longer applies cleanly. However, I think the really issue is that the gralloc blobs was extended by PowerVR (see https://github.com/xc-racer99/andro...6.0/exynos3/s5pc110/include/hal_public.h#L119) but with the binderized HALs/VNDK/other low-level Oreo changes something has broken. I had a go at trying to work around things, but failed too.
There are a few ways I can think of getting working graphics:
1) Someone finds some updated blobs for the PowerVR SGX 540 for ARM (I've found x86 ones, but they don't work for obvious reasons)
2) Someone hacks around the source code so that the blobs work - but I'm not sure if it's PowerVR "extension" of the gralloc interface that is causing issues or not...
3) We simply use software rendering, but this would be so slow with our ancient CPU that I haven't bothered to try
4) We work on porting a newer kernel so we have the Samsung DRM kernel driver, use the Linux PowerVR blobs coupled with drm_gralloc/drm_hwcomposer and maybe a wrapper like https://github.com/TexasInstruments/dri3wsegl and somehow cobble together working support
In terms of the mediaextractor crash, that's due to the kernel missing seccomp support. There's a whole bunch of different backports, some more successful than others. Due to our ancient kernel, backporting is no longer very easy...
If we could somehow get the graphics drivers working, we'd have a pretty good base as there are free implementations of all HALs/drivers except for GPS and TV-Out (and, of course, graphics....).

Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?

nailyk said:
Are you really working on porting oreo on the i9000?
How do you deal with the small amount of ram?
Are you using the 'low end device' oreo feature?
Click to expand...
Click to collapse
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.

xc-racer99 said:
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
Click to expand...
Click to collapse
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.

nailyk said:
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.
Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 )
Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers
Thanks for your time.
Click to expand...
Click to collapse
If you're serious about trying to mess with graphics drivers, it might be interesting to check out the blobs from https://www.renesas.com/pt-br/produ...ion-boards/renesas-starter-kit-for-rzg1e.html as it's an ARM-based device with the SGX540. It's possible that they're new enough to not run into the same issues as the older blobs (but equally possible that even the kernel part is closed source). The binary blobs are only semi-SoC specific as I've managed to use the OMAP blobs with only having hardware decoding being broken.

Is it for real???
I9000 !!

Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490

Use android go it will be better.

MYEUHD said:
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:
https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/
https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged
In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).
https://forum.xda-developers.com/showpost.php?p=77526206&postcount=2490
Click to expand...
Click to collapse
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time

xc-racer99 said:
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time
Click to expand...
Click to collapse
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).

xc-racer99 said:
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
Click to expand...
Click to collapse
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
ChronoMonochrome said:
In 9.0, to get graphics to work, device is required to support HWC2 (or use either HWC2on1 or HWC2onFb adapters).
Click to expand...
Click to collapse
ChronoMonochrome said:
Yes, HWC has to be at least 1.3, to work with one of aforementioned adapters. With one of those adapters it will work like it was HWC 2 (but actually not exactly same).
Click to expand...
Click to collapse
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung

MYEUHD said:
We need a newer hwc anyway, as Pie requires at least hwc 1.3:
As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread
hardware/samsung
Click to expand...
Click to collapse
Was unaware of the fact. Are you volunteering to make the patches?
I've uploaded my changes to https://github.com/xc-racer99/proprietary_vendor_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_hardware_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_kernel_samsung_aries/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_aries-common/tree/ddk-1.14 but I think this might be the last I work on this as I don't really have the motivation to work on it anymore. Note the patches are against a custom version of Unlegacy Android 4.4 so you'll need to cherry pick the changes to your ROM of choice if desired.
The changes build, the EGL appears to initialize, but I always get
Code:
E/libEGL ( 471): validate_display:254 error 3008 (EGL_BAD_DISPLAY)
And in dmesg:
Code:
[ 8.509291] init: computing context for service '/system/vendor/bin/pvrsrvinit'
[ 8.509601] init: starting 'pvrsrvinit'
...
[ 8.601890] PVR_K: UM DDK-(4081762) and KM DDK-(4081762) match. [ OK ]
...
[ 8.765955] init: process 'pvrsrvinit', pid 99 exited
...
[ 55.560021] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.563491] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.597577] s3cfb s3cfb: [fb0] video memory released
Whether the issue is in the HWC or the gralloc blob that we've stolen from OMAP, I have no idea.

xc-racer99 said:
Was unaware of the fact. Are you volunteering to make the patches?
Click to expand...
Click to collapse
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??

MYEUHD said:
Will try to do my best!
BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
Click to expand...
Click to collapse
You really do need jdk-7... I used the "reference implementation" available at http://jdk.java.net/java-se-ri/7 and made sure the java executables were in the PATH before the java I actually have installed.
Note that my Unlegacy Android trees will not work for the i9000 (well, they might, but you'd need to install u-boot as well at a bare minimum...)

It's kinda Insane that people are trying to get an 8 year phone to run oreo

@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?

MYEUHD said:
@xc-racer99 Do you still have the AOSP 7.1 source code on your computer?
Click to expand...
Click to collapse
I've got the .repo folder, but don't have the individual files expanded as I don't have the disk space Could run a repo sync and look at things but don't have the disk space for a full build.

The_Pacific_gamer said:
It's kinda Insane that people are trying to get an 8 year phone to run oreo
Click to expand...
Click to collapse
its kinda insane that people are still using this phone.

[WIP] [Help wanted] Making postmarketOS Linux port

Hey everyone!
So inspired by the Ubuntu thread, I decided to tackle making a port of postmarketOS, a version of Alpine Linux designed to run on legacy smartphones.
The progress is going pretty well, the device boots, the display works and you can log in via ssh. What doesn't work yet is Wifi and the kernel complains about several issues with CPU frequency drivers and then panics after a few minutes.
It'd be great if someone who knows more than I do could build the OS themselves and try to debug the kernel and upload patches or suggest a troubleshooting path.
Sources are here: https://github.com/postmarketos/pmbootstrap
Additional info on porting: https://wiki.postmarketos.org/wiki/Porting_to_a_new_device

Good to see some more interest in this. I'm far from being any help coding/building but will keep following to help test. My tablet has just been sitting lately anyway.

The pull request actually got approved. The initial device config is now in the official repo, waiting to be improved upon. Updated the link to point to the postmarketos github.

@flar2 @USBhost
If you're not too busy or bored by this project, it'd be neat of you could have a look at the current issue we're having. You're more experienced with kernels than I am, derp:
https://github.com/postmarketOS/pmbootstrap/issues/1384

Alexandroid99 said:
@flar2 @USBhost
If you're not too busy or bored by this project, it'd be neat of you could have a look at the current issue we're having. You're more experienced with kernels than I am, derp:
https://github.com/postmarketOS/pmbootstrap/issues/1384
Click to expand...
Click to collapse
Any kernel logs ?
It could be that the kernel was configured wrong. Or bad toolchain.

There's a dmesg posted on the issue.

Alexandroid99 said:
There's a dmesg posted on the issue.
Click to expand...
Click to collapse
Let's pretend that never happened :angel:
Edit: @Alexandroid99 I think I know what happened... Disable hung task in the config.
If you still have problems I will look through the whole config in the morning.

USBhost said:
Let's pretend that never happened :angel:
Click to expand...
Click to collapse
No worries. I'm glad enough that you're taking time to look at it anyway. From what I can gather, it's failing to control the CPU and fails to find firmware, even though I'm using kernel params and the correct wifi fw path in the kernel config.

USBhost said:
Let's pretend that never happened :angel:
Edit: @Alexandroid99 I think I know what happened... Disable hung task in the config.
If you still have problems I will look through the whole config in the morning.
Click to expand...
Click to collapse
Ooo that does sound helpful for further debugging at the very least. Thanks!

Alexandroid99 said:
Ooo that does sound helpful for further debugging at the very least. Thanks!
Click to expand...
Click to collapse
Does it still crash?

USBhost said:
Does it still crash?
Click to expand...
Click to collapse
Sadly, yes. Dmesg is still complaining about the firmware issues even when /vendor is mounted & the firmware is automatically copied to the initfs ramdisk at startup to /lib/firmware, plus we get these strange errors about the cpu frequency not being controllable. It does seem to run a tiny bit longer, so I could pipe a very late dmesg output to a file and pull it from the device. Gist here: https://gist.github.com/Alexandroid99/21fd1dafa931421d87c16d784ec6068d
Defconfig:
https://github.com/postmarketOS/pmb...inux-htc-flounder/config-htc-flounder.aarch64
At this point I'm not sure if it's related to the kernel not finding its firmware or if it's related to the modifications the distro makes. At least it kind of does boot, which is an advantage over other devices that don't even make it to userland.
Thanks for taking time, I appreciate you helping. ^_^

Alexandroid99 said:
Hey everyone!
So inspired by the Ubuntu thread, I decided to tackle making a port of postmarketOS, a version of Alpine Linux designed to run on legacy smartphones.
The progress is going pretty well, the device boots, the display works and you can log in via ssh. What doesn't work yet is Wifi and the kernel complains about several issues with CPU frequency drivers and then panics after a few minutes.
It'd be great if someone who knows more than I do could build the OS themselves and try to debug the kernel and upload patches or suggest a troubleshooting path.
Sources are here: https://github.com/postmarketos/pmbootstrap
Additional info on porting: https://wiki.postmarketos.org/wiki/Porting_to_a_new_device
Click to expand...
Click to collapse
WHoooaa wow, This is great to here, as I plan on tackling Sailfish OS on flounder after it comes in the mail (still working on manta Nexus 10 audio issues >:c ). Any special configs you had to set with the kernel? I assume PostMarket OS uses Hybris or something similar for HW adaptation

Galaxyninja66 said:
WHoooaa wow, This is great to here, as I plan on tackling Sailfish OS on flounder after it comes in the mail (still working on manta Nexus 10 audio issues >:c ). Any special configs you had to set with the kernel? I assume PostMarket OS uses Hybris or something similar for HW adaptation
Click to expand...
Click to collapse
Ehm we're nowhere near hwaccel yet and I've posted different versions of the defconfig before. The most recent is already in the official repo. All we have is a more or less booting device with a cyan cursor (if Mate desktop is installed) that crashes after three minutes. Look around the pmbootstrap repo and wiki for more info. And the devs said they haven't packaged libhybris for the Alpine Linux base yet, so that's still no-go.

@Alexandroid99 What CM/LOS base are you using? CM12.1? LOS14.1???
---------- Post added at 03:44 AM ---------- Previous post was at 03:05 AM ----------
Alexandroid99 said:
Ehm we're nowhere near hwaccel yet and I've posted different versions of the defconfig before. The most recent is already in the official repo. All we have is a more or less booting device with a cyan cursor (if Mate desktop is installed) that crashes after three minutes. Look around the pmbootstrap repo and wiki for more info. And the devs said they haven't packaged libhybris for the Alpine Linux base yet, so that's still no-go.
Click to expand...
Click to collapse
If you can, spam dmesg in terminal until it crashes, or, if possible, telnet into the device (maybe postmarket doesn't have telnet, I don't know) and run dmesg, and figure out what process is causing the crash.

Galaxyninja66 said:
@Alexandroid99 What CM/LOS base are you using? CM12.1? LOS14.1???
---------- Post added at 03:44 AM ---------- Previous post was at 03:05 AM ----------
If you can, spam dmesg in terminal until it crashes, or, if possible, telnet into the device (maybe postmarket doesn't have telnet, I don't know) and run dmesg, and figure out what process is causing the crash.
Click to expand...
Click to collapse
Base is LOS-15.1 branch.
And pmos has got ssh built in and I've already spammed dmesg, that's how I got that dmesg gist.

Alexandroid99 said:
Base is LOS-15.1 branch.
And pmos has got ssh built in and I've already spammed dmesg, that's how I got that dmesg gist.
Click to expand...
Click to collapse
Guess I'll need to wait for Hybris-15.1 for sailfish os : ( oh well;

Galaxyninja66 said:
Guess I'll need to wait for Hybris-15.1 for sailfish os : ( oh well;
Click to expand...
Click to collapse
Who cares about libhybris when we don't have a stable kernel yet? FYI the tegra vendor libs stopped being updated during the times of 7.1.2; they don't have to do anything with Lineage 15.1. The kernel itself is from the 15.1 branch because that's the version receiving updates right now afaik and not that different from 14.1 (I think).
The Ubuntu port is stable enough to run even though it doesn't use libhybris for anything, at least it wasn't mentioned. I appreciate your interest, but kindly have a look at the dmesg gist and tinker around with the builds if you've got an idea, or just leave it be. All we need right now is debug the kworker hang that occurs after about three minutes of uptime and is probably at least partially caused by missing firmware. There's of stuff you can do while forking:
- try to install firmware into the initramfs and see if that helps
- Add an initramfs hook and fstab entry to mount /vendor
- Make a new kernel defconfig with fixes if you think there's an error in there
- Make a new kernel package based on different lineage branches just to be sure
So, fork the pmbootstrap repo and get to it and forget about libhybris and next time read my posts better, because you suggested making a dmesg log when I had already mentioned that I managed to pull a very late dmesg aaand you could have found out the kernel base by yourself by looking at the repo on github.

@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Code:
WARNING: at drivers/platform/tegra/../../../arch/arm/mach-tegra/tegra12_clocks.c:1585 tegra12_cpu_clk_set_rate+0x16c/0x4b0()
[ 1.450449] Increasing CPU rate while regulator is not ready is not allowed
[ 1.450463] Modules linked in:
[ 1.450497] CPU: 1 PID: 48 Comm: cfinteractive Tainted: G W 3.10.103-pmos #1-postmarketOS
[ 1.450518] Call trace:
[ 1.450546] [<ffffffc000089508>] dump_backtrace+0x0/0x150
[ 1.450570] [<ffffffc00008966c>] show_stack+0x14/0x20
[ 1.450626] [<ffffffc000ae8ce8>] dump_stack+0x20/0x28
[ 1.450648] [<ffffffc0000ac1b0>] warn_slowpath_common+0x78/0xa0
[ 1.450669] [<ffffffc0000ac218>] warn_slowpath_fmt+0x40/0x48
[ 1.450688] [<ffffffc000832674>] tegra12_cpu_clk_set_rate+0x16c/0x4b0
[ 1.450709] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450729] [<ffffffc00082a070>] tegra12_cpu_cmplx_clk_set_rate+0x48/0xd8
[ 1.450748] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450766] [<ffffffc000828bd0>] clk_set_rate+0x58/0x230
[ 1.450787] [<ffffffc00083e028>] tegra_update_cpu_speed+0x180/0x3d8
[ 1.450806] [<ffffffc00083e75c>] tegra_cpu_set_speed_cap_locked+0x8c/0x100
[ 1.450824] [<ffffffc00083ee4c>] tegra_target+0x7c/0xa8
[ 1.450845] [<ffffffc0007acc8c>] __cpufreq_driver_target+0xa4/0x368
[ 1.450867] [<ffffffc0007b69bc>] cpufreq_interactive_speedchange_task+0x174/0x258
[ 1.450888] [<ffffffc0000d8fc8>] kthread+0xd0/0xd8
[ 1.450903] ---[ end trace 1b75b31a2719ed1f ]---
[ 1.450919] cpu-tegra: Failed to set cpu frequency to 714000 kHz

Alexandroid99 said:
@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Code:
WARNING: at drivers/platform/tegra/../../../arch/arm/mach-tegra/tegra12_clocks.c:1585 tegra12_cpu_clk_set_rate+0x16c/0x4b0()
[ 1.450449] Increasing CPU rate while regulator is not ready is not allowed
[ 1.450463] Modules linked in:
[ 1.450497] CPU: 1 PID: 48 Comm: cfinteractive Tainted: G W 3.10.103-pmos #1-postmarketOS
[ 1.450518] Call trace:
[ 1.450546] [<ffffffc000089508>] dump_backtrace+0x0/0x150
[ 1.450570] [<ffffffc00008966c>] show_stack+0x14/0x20
[ 1.450626] [<ffffffc000ae8ce8>] dump_stack+0x20/0x28
[ 1.450648] [<ffffffc0000ac1b0>] warn_slowpath_common+0x78/0xa0
[ 1.450669] [<ffffffc0000ac218>] warn_slowpath_fmt+0x40/0x48
[ 1.450688] [<ffffffc000832674>] tegra12_cpu_clk_set_rate+0x16c/0x4b0
[ 1.450709] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450729] [<ffffffc00082a070>] tegra12_cpu_cmplx_clk_set_rate+0x48/0xd8
[ 1.450748] [<ffffffc0008289a0>] clk_set_rate_locked+0x118/0x2f0
[ 1.450766] [<ffffffc000828bd0>] clk_set_rate+0x58/0x230
[ 1.450787] [<ffffffc00083e028>] tegra_update_cpu_speed+0x180/0x3d8
[ 1.450806] [<ffffffc00083e75c>] tegra_cpu_set_speed_cap_locked+0x8c/0x100
[ 1.450824] [<ffffffc00083ee4c>] tegra_target+0x7c/0xa8
[ 1.450845] [<ffffffc0007acc8c>] __cpufreq_driver_target+0xa4/0x368
[ 1.450867] [<ffffffc0007b69bc>] cpufreq_interactive_speedchange_task+0x174/0x258
[ 1.450888] [<ffffffc0000d8fc8>] kthread+0xd0/0xd8
[ 1.450903] ---[ end trace 1b75b31a2719ed1f ]---
[ 1.450919] cpu-tegra: Failed to set cpu frequency to 714000 kHz
Click to expand...
Click to collapse
Yo... I'll look into it. And yes I am.

USBhost said:
@USBhost Are you still onboard with this? I've been meaning to get back into the project and your more professional opinion would be greatly appreciated ^^
It does run a little longer with hung tasks disabled, but I think it might be a deeper problem. Perhaps it's got something to do with the cpufreq driver:
Yo... I'll look into it. And yes I am.
Click to expand...
Click to collapse
Alrighty, cheers! Are you doing builds yourself to debug or should I keep on feeding you kernel logs whenever you require some? Thanks!

Android 8.1 Development

Progress is being made many of the bugs are beginning to get fixed
Oreo roms that maybe created:
Lineage 15.1 (highly likely)
Nitrogen Os (by me and @ReversedPosix)
Bugs fixed in oreo generally:
Sound
Rild
Sim card ---->
Fixed By @Quarx2k (Telegram)
Bluetooth ---->
Thanks to these people this is possible @Olivier @ReversedPosix @EnesSastim @Myself5,
XDA:DevDB Information
Test developming, ROM for the Sony Xperia Z5
Contributors
Quantumkk123, QuantumKK123, Zacharias.Maladroit, olivier
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Aosp
Version Information
Status: Alpha/Beta (More things are working now)
Beta Release Date: 2018-05-05
Created 2018-05-10
Last Updated 2018-08-04

@Quantumkk123
you already got the ROM hooked up ?
please upload somewhere & write me a PM so I can take a look at it,
currently busy so kernel has to wait

Atm I think @zacharias.maladroit is reviewing the rom looking to edit the kernel so this rom can work on our phones I think also a few things need to be edited but yeah we might have an unofficial oreo Rom for the z5 and it will be the first

@Quantumkk123 top work! By seeing the features you listed, is this rom based on AOSP but with stock oreo things? :silly:
@zacharias.maladroit take your time. We just want this to work without irritating you guys. Nobody will ask for ETA. :silly: :highfive:

@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.

Quantumkk123 said:
@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.
Click to expand...
Click to collapse
Ok, I got it!

Quantumkk123 said:
@balrajs99 to be honest Bro thank @zacharias.maladroit for telling me the similarities that Xperia x and z5 had in common however I figured out Machao_44 makes his rom differently to the newer ones (easier to modify) the only difference between this rom and the Xperia x is meta inf replaced with z5 along with ftf and build.prop see I tried the exact same thing with z3 + and successfully ported the z5 rom to it by changing the same things. However we don't know yet if zacharias.maladroit kernel can make rom boot or infinite boot loop we don't know but yeah that's everything and your most welcome I want this rom as much as you guys do.
Click to expand...
Click to collapse
At first glance this definitely looks nicer, the issue might be in the details though :silly:
Thanks

zacharias.maladroit said:
At first glance this definitely looks nicer, the issue might be in the details though :silly:
Thanks
Click to expand...
Click to collapse
So @zacharias.maladroit whats happening how much of this rom needs to edited to fully work and how is the kernel doing?

Quantumkk123 said:
So @zacharias.maladroit whats happening how much of this rom needs to edited to fully work and how is the kernel doing?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76479481&postcount=30
&
CONFIG_BT_MSM_SLEEP -> bluetooth driver differences
CONFIG_MSM_DCC => ?
CONFIG_QNS_SYSTEM=y
CONFIG_QUOTA=y
CONFIG_QUOTACTL=y
CONFIG_SDCARD_FS=y
CONFIG_SPLIT_PTLOCK_CPUS=999999
CONFIG_DEBUG_SPINLOCK_BITE_ON_BUG=y
# CONFIG_DEBUG_SPINLOCK_PANIC_ON_BUG is not set
CONFIG_MSM_RTB_SEPARATE_CPUS=y
CONFIG_PROC_PID_CPUSET=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y (quotas)
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_QUOTA_TREE=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MSM_HSL_CONSOLE=y
ours:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CSVT=y
theirs:
# CONFIG_USB_SERIAL is not set
--- /dev/null
+++ b/arch/arm64/configs/diffconfig/suzu_diffconfig
@@ -0,0 +1,7 @@
+CONFIG_MACH_SONY_SUZU=y
+CONFIG_NFC_PN547=y
+CONFIG_QPNP_SMBCHARGER_ID_POLL=y
+CONFIG_TOUCHSCREEN_CLEARPAD=y
+CONFIG_USB_MIRRORLINK=y
+CONFIG_TOUCHSCREEN_CLEARPAD_I2C=y
+CONFIG_TOUCHSCREEN_CLEARPAD_RMI_DEV=y
--- a/arch/arm64/configs/msm8994-perf_defconfig
+++ b/arch/arm64/configs/msm8994-perf_defconfig
@@ -243,13 +243,14 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_USB_USBNET=y
-CONFIG_CNSS=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
-CONFIG_CNSS_MAC_BUG=y
-CONFIG_CLD_LL_CORE=y
CONFIG_ATH_CARDS=y
CONFIG_WIL6210=m
CONFIG_E1000E=y
+CONFIG_CNSS_PCI=y
+CONFIG_CNSS_MAC_BUG=y
+CONFIG_CLD_LL_CORE=y
+CONFIG_BUS_AUTO_SUSPEND=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
diff --git a/arch/arm64/configs/msm-perf_defconfig b/arch/arm64/configs/msm-perf_defconfig
index bfe14733b104..12a8d65cf3cd 100644
--- a/arch/arm64/configs/msm-perf_defconfig
+++ b/arch/arm64/configs/msm-perf_defconfig
@@ -220,7 +220,6 @@ CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
CONFIG_MSM_BT_POWER=y
CONFIG_CFG80211=y
-CONFIG_NL80211_TESTMODE=y
CONFIG_CFG80211_INTERNAL_REGDB=y
CONFIG_RFKILL=y
# CONFIG_NFC_QNCI=y
@@ -270,9 +269,11 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_WCNSS_CORE=y
+CONFIG_CNSS_SDIO=y
CONFIG_WCNSS_CORE_PRONTO=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
CONFIG_WCNSS_REGISTER_DUMP_ON_BITE=y
+CONFIG_CLD_HL_SDIO_CORE=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
@@ -288,8 +289,6 @@ CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI4_DEV=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE=y
CONFIG_SECURE_TOUCH=y
-CONFIG_TOUCHSCREEN_BU21150=y
-CONFIG_INPUT_MT_WRAPPER=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_HBTP_INPUT=y
CONFIG_SENSORS_MPU6050=y
@@ -305,6 +304,7 @@ CONFIG_SENSORS_ISL29044A=y
CONFIG_SENSORS_CAPELLA_CM36283=y
# CONFIG_SERIO_I8042 is not set
# CONFIG_VT is not set
+CONFIG_SERIAL_MSM_HS=y
CONFIG_SERIAL_MSM_SMD=y
CONFIG_DIAG_CHAR=y
CONFIG_HW_RANDOM=y
@@ -611,3 +611,4 @@ CONFIG_SPDM_SCM=y
CONFIG_SECCOMP=y
CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE=y
CONFIG_UID_CPUTIME=y
+CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
Click to expand...
Click to collapse
that'll get you an idea:
kernel-side:
bluetooth might be a problem, we need sdcardfs, our SoC/processor might lack certain parts that are necessary for functions of the ROM (DCC "MSM data capture and compare engine" and others),
binder needs updating,
display driver (?),
matching gpu driver (kernel-side) & adreno blobs (ROM-side)
we might need different kernel modules built for the ROM & subsystems might require rework (see attached list of kernel modules)
ROM-side:
modem needs to be replaced (M-ROM 2.4.8 by nreuge has those files in system/etc/customization/modem ),
ril / qcril might need work
wlan (system/firmware/wlan/bcmdhd) firmware might need to be replaced with ours
system/etc/wifi/wifi_txpower.conf might need modification
system/compatibility_matrix.xml might need changes
where is system/etc/mixer_paths.xml ? => system/vendor/etc/
system/vendor/lib{64}/{egl} adreno related libs need to be checked out - the driver most probably won't work with kernel-side
fingerprint & nfc libraries need to be evaluated [later]
msm_irqbalance, thermal, etc. all crucial subsystems and configurations need to be double and triple-checked before even attempting to put it on the device.
[I got a terrifying moment today while modifying MHL driver and got strange noises out of the phone & speaker - better safe than sorry]
That's only a first (and most likely incomplete) pass through the ROM files

So @zacharias.maladroit I am guessing their is a lot of work to be done well just asking how long will this take is it possible you are able to do all these modification yourself or do you need help from other devs? If you are able how long will It take I can also help out but not today or tomorrow busy with exams lol

Quantumkk123 said:
So @zacharias.maladroit I am guessing their is a lot of work to be done well just asking how long will this take is it possible you are able to do all these modification yourself or do you need help from other devs? If you are able how long will It take I can also help out but not today or tomorrow busy with exams lol
Click to expand...
Click to collapse
No ETA, I'll defer work since I need to focus on personal affairs right now, I can do some random kernel development (or rather: have to since this gives me my occasional "fix") but that's about it ... at least for now
I've pointed out the important points that need work but won't be able to do anything right now since other things need my full attention at the moment
edit:
to answer you question:
yes, help definitely would be appreciated and is required,
I won't do this on my own - since the M-ROM 2.4.8 variant for now is enough that I ask for, I'm mostly focusing on kernel work to get an optimum of performance, stability, security vs. battery runtime,
perhaps @GreyLeshy and additional folks/devs/users like @trax7 have interest in taking a look at this ...

OK welll thanks for all your help we all really appreciate it @zacharias.maladroit hopefully other devs can fix what needs improving as you have thankfully told us and they can fix it and maybe when you have more times on your hands you can fix everything

Great so to all devs out there who own Z5 of course please contribute and help make the first oreo Rom I will make.sure you get pointed out credits if you help Bro @enesstastim and others as well

Quantumkk123 said:
Great so to all devs out there who own Z5 of course please contribute and help make the first oreo Rom I will make.sure you get pointed out credits if you help Bro @enesstastim and others as well
Click to expand...
Click to collapse
We also need to document each and every step and what modifications are necessary so that others can easily reproduce
First and foremost:
what ROM base did you use ?
(MaChao_44) Xperia XP V1.1.5(Android O).zip ¹
or
(MaChao_44) Xperia XP V1.4(Android O).zip ²
?
(I'm guessing the first one but not sure)
https://forum.xda-developers.com/showpost.php?p=76476528&postcount=25 ¹, ²
thanks to @turnout96 for helping out with the download & upload

Version 1.4 @zacharias.maladroit

Quantumkk123 said:
Version 1.4 @zacharias.maladroit
Click to expand...
Click to collapse
Oh good, cause I accidentally compared your mod with that ROM
Only was wondering because a few files were differing that weren't obvious

@zacharias.maladroit oh lol so the changes won't be as different as you thought?

Quantumkk123 said:
@zacharias.maladroit oh lol so the changes won't be as different as you thought?
Click to expand...
Click to collapse
They are just like I wrote before - but just with a few additional files less to worry about
still pretty difficult - this needs quite a few experienced devs to do it (or quite some learning by doing ...)

Would it be possible to use some of the drivers (gpu for example) from roms of other devices?
The OnePlus 2 has the same Snapdragon 810 SoC and there are some Oreo roms available already.
Maybe merging parts of the X and OP2 rom could help?
I dont have any experience modifiying aosp, so if Im worng, just ignore my thoughts.

brothers anyone screenshot this rom thanxxxxxxxx