Hi. As the title says i'm requesting for MIUI 10 Treble. Thanks!
*Please move if wrong forum*
no possible create GSI Miui 10 ??
I'm working on MIUI 9 one atm but it's based on 6x which isn't MIUI 10 yet. Maybe I will change to one of the other ones, if they're Treble. But only when xiaomi.eu builds come out.
I can't even get the device past init yet, because I have a seamless device perhaps and it just kicks me into fastboot (we encountered the same issue when porting Treble to the Mi A1). Not sure what the problem is.
I also have an annoying issue on my Ubuntu machine where I can't umount the system image because it's apparently busy, which could be causing issues.
CosmicDan said:
I'm working on MIUI 9 one atm but it's based on 6x which isn't MIUI 10 yet. Maybe I will change to one of the other ones, if they're Treble. But only when xiaomi.eu builds come out.
I can't even get the device past init yet, because I have a seamless device perhaps and it just kicks me into fastboot (we encountered the same issue when porting Treble to the Mi A1). Not sure what the problem is.
I also have an annoying issue on my Ubuntu machine where I can't umount the system image because it's apparently busy, which could be causing issues.
Click to expand...
Click to collapse
what miui9 your working??
Yes,we need some different ui like miui,flyme to taste something else other than aosp
CosmicDan said:
I'm working on MIUI 9 one atm but it's based on 6x which isn't MIUI 10 yet. Maybe I will change to one of the other ones, if they're Treble. But only when xiaomi.eu builds come out.
I can't even get the device past init yet, because I have a seamless device perhaps and it just kicks me into fastboot (we encountered the same issue when porting Treble to the Mi A1). Not sure what the problem is.
I also have an annoying issue on my Ubuntu machine where I can't umount the system image because it's apparently busy, which could be causing issues.
Click to expand...
Click to collapse
Are you sure it's possible? Someone said DSSI can't be modified into a GSI.
fxsheep said:
Are you sure it's possible? Someone said DSSI can't be modified into a GSI.
Click to expand...
Click to collapse
Why not? Source please?
CosmicDan said:
Why not? Source please?
Click to expand...
Click to collapse
I may have said something to the effect of it being difficult to do because of greater integration between system and vendor, since the DSSI can expect private vendor implementations to be available in /vendor that a GSI can't.
I do recall saying it was a bad idea to flash a DSSI on something other than the device it was made for (except maybe very similar devices), but I'd imagine that should be obvious.
irony_delerium said:
I may have said something to the effect of it being difficult to do because of greater integration between system and vendor, since the DSSI can expect private vendor implementations to be available in /vendor that a GSI can't.
I do recall saying it was a bad idea to flash a DSSI on something other than the device it was made for (except maybe very similar devices), but I'd imagine that should be obvious.
Click to expand...
Click to collapse
Fair enough.
Well I am hoping it's possible. Basically all I've tried so far is whacking the /system folder into a GSI, but I have a seamless device and it's not even getting past init so I can't see logcat. I'm not sure why. I've been diff'ing MIUI /system with GSI /system and nothing really stands out.
CosmicDan said:
Fair enough.
Well I am hoping it's possible. Basically all I've tried so far is whacking the /system folder into a GSI, but I have a seamless device and it's not even getting past init so I can't see logcat. I'm not sure why. I've been diff'ing MIUI /system with GSI /system and nothing really stands out.
Click to expand...
Click to collapse
On one hand, I've got 2 (technically 3, if you count my HiKey960 dev board) A-only devices. On the other, Xiaomi devices tend to run MTK or Qualcomm chipsets if I'm not mistaken, which none of mine have - both Mate 9's. (And the dev board, I have yet to get a working Treble implementation on it, and it would likely be API 27/P since it's only supported by AOSP master right now.)
Otherwise, I'd offer assistance - if I were going to do it, I'd start with hardware that's similar to what the DSSI expects, get it running there, and then start moving to dissimilar hardware.
I would imagine it _should_ be possible - someone managed to get somewhere with the Pixel P preview images, as I recall. I think I read that it was booting but still broken all over the place.
irony_delerium said:
On one hand, I've got 2 (technically 3, if you count my HiKey960 dev board) A-only devices. On the other, Xiaomi devices tend to run MTK or Qualcomm chipsets if I'm not mistaken, which none of mine have - both Mate 9's. (And the dev board, I have yet to get a working Treble implementation on it, and it would likely be API 27/P since it's only supported by AOSP master right now.)
Otherwise, I'd offer assistance - if I were going to do it, I'd start with hardware that's similar to what the DSSI expects, get it running there, and then start moving to dissimilar hardware.
I would imagine it _should_ be possible - someone managed to get somewhere with the Pixel P preview images, as I recall. I think I read that it was booting but still broken all over the place.
Click to expand...
Click to collapse
Fair idea. The Redmi S2 has same SoC as my A1 and is Treble, but there's no xiaomi.eu builds for it yet (and I need theirs because they remove some of the original device protections). So I'm working with 6x atm, next closest hardware.
CosmicDan said:
Why not? Source please?
Click to expand...
Click to collapse
This is from a P DSSI port
erfanoabdi said:
if you understand what is CLT it's nothing but a copy paste script
and we don't have GSI P at all
i used marlin system and vendor images to make this rom from lineage with many patches, hex edits and hacks
i'll make a guide for all i did on griffin later
Click to expand...
Click to collapse
---------- Post added at 01:37 PM ---------- Previous post was at 01:09 PM ----------
CosmicDan said:
I'm working on MIUI 9 one atm but it's based on 6x which isn't MIUI 10 yet. Maybe I will change to one of the other ones, if they're Treble. But only when xiaomi.eu builds come out.
I can't even get the device past init yet, because I have a seamless device perhaps and it just kicks me into fastboot (we encountered the same issue when porting Treble to the Mi A1). Not sure what the problem is.
I also have an annoying issue on my Ubuntu machine where I can't umount the system image because it's apparently busy, which could be causing issues.
Click to expand...
Click to collapse
irony_delerium said:
On one hand, I've got 2 (technically 3, if you count my HiKey960 dev board) A-only devices. On the other, Xiaomi devices tend to run MTK or Qualcomm chipsets if I'm not mistaken, which none of mine have - both Mate 9's. (And the dev board, I have yet to get a working Treble implementation on it, and it would likely be API 27/P since it's only supported by AOSP master right now.)
Otherwise, I'd offer assistance - if I were going to do it, I'd start with hardware that's similar to what the DSSI expects, get it running there, and then start moving to dissimilar hardware.
I would imagine it _should_ be possible - someone managed to get somewhere with the Pixel P preview images, as I recall. I think I read that it was booting but still broken all over the place.
Click to expand...
Click to collapse
P preview can be possible, the two phones have the same processor,so itis just like a ported ROM that don't related to treble.
I just *guess* that the DSSI is similar to a Non-Treble phone's ROM. I flashed a bootable AOSP GSI on a trebled phone and it boots fine,but since I just replace the /system/bin with one in MIUI DSSI, the phone will directly drop to fastboot mode.
So the DSSI maybe just like all the nougat roms,that they use the vendor directly,don't go through treble.
If GSI-ify a DSSI image is possible, then I have some ideas.
Before trying to make a MIUI GSI,we could first get a DSSI Lineage ROM,e.g. Xiaomi MI 6 Lineage OS 15.1 treble. This is a device with unofficial treble,and the lineage rom uses a DSSI image .This situation is just like the Redmi S2 or whyred, but this DSSI image contains the least private vendor stuff.It's nearly a GSI image.
So if we first get it boot on a phone with different processor,then we could prove that crossing processors is possible.Then we may use a similar way to make MIUI DSSI go past fastboot.
fxsheep said:
This is from a P DSSI port
---------- Post added at 01:37 PM ---------- Previous post was at 01:09 PM ----------
P preview can be possible, the two phones have the same processor,so itis just like a ported ROM that don't related to treble.
I just *guess* that the DSSI is similar to a Non-Treble phone's ROM. I flashed a bootable AOSP GSI on a trebled phone and it boots fine,but since I just replace the /system/bin with one in MIUI DSSI, the phone will directly drop to fastboot mode.
So the DSSI maybe just like all the nougat roms,that they use the vendor directly,don't go through treble.
If GSI-ify a DSSI image is possible, then I have some ideas.
Before trying to make a MIUI GSI,we could first get a DSSI Lineage ROM,e.g. Xiaomi MI 6 Lineage OS 15.1 treble. This is a device with unofficial treble,and the lineage rom uses a DSSI image .This situation is just like the Redmi S2 or whyred, but this DSSI image contains the least private vendor stuff.It's nearly a GSI image.
So if we first get it boot on a phone with different processor,then we could prove that crossing processors is possible.Then we may use a similar way to make MIUI DSSI go past fastboot.
Click to expand...
Click to collapse
GSI is something Phh created. It's basically the same as other Treble ROM's - it talks to vendor through VNDK. He uses a dummy device tree though to ensure that there are no broken contracts outside of the Treble architecture pattern.
It is likely that DSSI's use stuff on their own system or vendor that are outside of the VNDK interface, though - that's true. But those are specific to the ROM overlay, not the core Android experience.
Indeed, the goal in porting a DSSI is to identify these things.
We (I) already have a device with unofficial Treble, BTW - I and another guy developed it ourselves. So Mi 6 Treble (a device I don't even have) won't help.
When we compile RR for our device under Treble, the Vendor is 100% GSI compatible as a result. The RR ROM itself needed no changes - we basically just added some build flags and moved some blobs to vendor from system. This was needed to even get *our* Treble ROM booting, though. The GSI's just happened to work automatically after that (minus some issues like camera blobs having hardcoded paths to /system).
In other words, we effectively compiled a DSSI with GSI-compatible Vendor with only VNDK-related build flags (and some vendor-located scripts to inject hardware blobs onto system).
Reversing that process is the key to port a DSSI to GSI.
I have diff'ed our classic non-Treble RR with Treble RR build, but I didn't find any leads. It's something specific to MIUI.
Maybe instead of replacing the whole system, I'll just replace the GSI framework and app packages with MIUI ones and see what happens. At least then it should get past init. There will of course be missing services in initfs that MIUI depends on, at the least. But hopefully no kind of DRM-like protections that block it from init.
I've a hunch that MIUI vendor has things that aren't actually from the vendor but for MIUI, which would be technically incorrect but a simple and effective way to prevent direct kanging.
With all that said, I do have a source of anxiety here - I need to be able to record and then script all this porting process so the GSI-ported ROM can actually be updated as the base DSSI gets new builds. That's going to be a headache. I don't want to be spending the rest of my days updating and editing a build script for MIUI GSI :\
Alright, small progress update (in the spirit of openness).
Turns out my boot issues were because I needed to recreate the ext4 image with file_contexts, which I had to stick together from GSI and my vendor partition with a bit of extras.
If I replace the whole system/ with MIUI system, I just get a kick into fastboot with no console-ramoops so the sledgehammer approach is out.
Instead I've replaced app, priv-app and framework with MIUI versions so I can at least get to the zygote bring up stage and go from there.
Ofc it doesn't boot, I will need to modify my rootfs at least and probably add some MIUI specific init rc's and services and the like. Thankfully I have an AB device so I don't need to modify my boot.img at all for this.
Stay tuned.
CosmicDan said:
Alright, small progress update (in the spirit of openness).
Turns out my boot issues were because I needed to recreate the ext4 image with file_contexts, which I had to stick together from GSI and my vendor partition with a bit of extras.
If I replace the whole system/ with MIUI system, I just get a kick into fastboot with no console-ramoops so the sledgehammer approach is out.
Instead I've replaced app, priv-app and framework with MIUI versions so I can at least get to the zygote bring up stage and go from there.
Ofc it doesn't boot, I will need to modify my rootfs at least and probably add some MIUI specific init rc's and services and the like. Thankfully I have an AB device so I don't need to modify my boot.img at all for this.
Stay tuned.
Click to expand...
Click to collapse
Little noob doubt;... devs ported miui10 for oneplus5 and 5T . Then why can't we! And yea oneplus 5 is not A/B . But that we can discuss or try to rectify our A/B partition problem,then it should be slightly easy to port know. _just my little thoughts and yea im really confused
balavignesh s said:
Little noob doubt;... devs ported miui10 for oneplus5 and 5T . Then why can't we! And yea oneplus 5 is not A/B . But that we can discuss or try to rectify our A/B partition problem,then it should be slightly easy to port know. _just my little thoughts and yea im really confused
Click to expand...
Click to collapse
Porting to AB makes things easier actually. I don't need to repack boot.img.
But that's beside the point. I can port a normal MIUI easily, in fact I have got it working basically on Mi A1 with minor issues (no I will not release it). But I want to port it on a Treble GSI base so it's more universal and easier to maintain - that's the challenge.
EDIT: Another update. I'm now up to the stage of resolving lib mismatches (i.e. native methods that MIUI adds). This is the hard part.
CosmicDan said:
Porting to AB makes things easier actually. I don't need to repack boot.img.
But that's beside the point. I can port a normal MIUI easily, in fact I have got it working basically on Mi A1 with minor issues (no I will not release it). But I want to port it on a Treble GSI base so it's more universal and easier to maintain - that's the challenge.
EDIT: Another update. I'm now up to the stage of resolving lib mismatches (i.e. native methods that MIUI adds). This is the hard part.
Click to expand...
Click to collapse
I have seen that some huawei devices with sd625 are running emui. Is it possible to port it to our device? I had huawei phone before and it seems to be a bit more complicated than miui.
Btw. Good luck with miui port, you are great Dev
Wysłane z mojego Mi A1 przy użyciu Tapatalka
Mirdeusz said:
I have seen that some huawei devices with sd625 are running emui. Is it possible to port it to our device? I had huawei phone before and it seems to be a bit more complicated than miui.
Btw. Good luck with miui port, you are great Dev
Wysłane z mojego Mi A1 przy użyciu Tapatalka
Click to expand...
Click to collapse
Of course it's possible. Just a matter of someone skilled and interested enough to do it.
Off topic, though. I'm not doing EMUI. I might do Flyme because I've never used it, but probably not because I am not experienced with it (I have been porting MIUI since 2012).
Once I get MIUI up it will include build scripts though, so maybe it can help someone else work on porting other ROMs.
Another small update: In order to maintain as much GSI compatibility as possible, some hardware-related MIUI features will very likely be broken. I had to strip their custom camera stuff out already, for example - so that means using your own device's or AOSP compatible camera.
OK, here's a technical rundown of where I'm at now (which is also a bit of a blocker).
Trying to get the extra MIUI resources (framework and platform APK's) seems to be impossible without replacing a large chunk of libs. That's a bummer. But I'll post the info here for posterity reasons, if not to catch the attention of someone clever and interested enough to know more.
First of all, we need to inject the new framework/platform APK's to the zygote whitelist. I do this by hooking the start of ZygoteInit.smali#preloadClasses()V:
Code:
# CosmicDan - inject miui platform APK's to whitelist
const-string/jumbo v0, "/system/app/miui/miui.apk"
invoke-static {v0}, Lcom/android/internal/os/Zygote;->nativeAllowFileAcrossFork(Ljava/lang/String;)V
const-string/jumbo v0, "/system/app/miuisystem/miuisystem.apk"
invoke-static {v0}, Lcom/android/internal/os/Zygote;->nativeAllowFileAcrossFork(Ljava/lang/String;)V
const-string/jumbo v0, "/system/framework/framework-ext-res/framework-ext-res.apk"
invoke-static {v0}, Lcom/android/internal/os/Zygote;->nativeAllowFileAcrossFork(Ljava/lang/String;)V
...this worked. Well, at least it got rid of the "not whitelisted:" errors on logcat. Still, even with this here, I get errors like this in logcat:
Code:
06-09 02:40:10.374 599 599 I Zygote : Preloading resources...
06-09 02:40:10.446 599 599 I Zygote : ...preloaded 86 resources in 71ms.
06-09 02:40:10.448 599 599 W ReflectionUtils:
06-09 02:40:10.448 599 599 W ReflectionUtils: java.lang.reflect.InvocationTargetException
06-09 02:40:10.448 599 599 W ReflectionUtils: at java.lang.reflect.Method.invoke(Native Method)
06-09 02:40:10.448 599 599 W ReflectionUtils: at miui.util.ReflectionUtils.callStaticMethod(Unknown Source:5)
06-09 02:40:10.448 599 599 W ReflectionUtils: at miui.util.ReflectionUtils.tryCallStaticMethod(Unknown Source:3)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInitInjector.preloadMiuiResources(Unknown Source:44)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.preloadResources(Unknown Source:95)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.preload(Unknown Source:41)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.main(Unknown Source:252)
06-09 02:40:10.448 599 599 W ReflectionUtils: Caused by: android.content.res.Resources$NotFoundException: Drawable miui:drawable/action_bar_back_normal_dark with resource ID #0x10020080
06-09 02:40:10.448 599 599 W ReflectionUtils: Caused by: android.content.res.Resources$NotFoundException: File res/drawable-xxhdpi-v4/action_bar_back_normal_dark.png from drawable resource ID #0x10020080
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.ResourcesImpl.loadDrawableForCookie(Unknown Source:177)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.ResourcesImpl.loadDrawable(Unknown Source:338)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.MiuiResourcesImpl.loadDrawable(Unknown Source:25)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.Resources.getDrawableForDensity(Unknown Source:14)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.Resources.getDrawable(Unknown Source:1)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.preloadDrawables(Unknown Source:17)
06-09 02:40:10.448 599 599 W ReflectionUtils: at java.lang.reflect.Method.invoke(Native Method)
06-09 02:40:10.448 599 599 W ReflectionUtils: at miui.util.ReflectionUtils.callStaticMethod(Unknown Source:5)
06-09 02:40:10.448 599 599 W ReflectionUtils: at miui.util.ReflectionUtils.tryCallStaticMethod(Unknown Source:3)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInitInjector.preloadMiuiResources(Unknown Source:44)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.preloadResources(Unknown Source:95)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.preload(Unknown Source:41)
06-09 02:40:10.448 599 599 W ReflectionUtils: at com.android.internal.os.ZygoteInit.main(Unknown Source:252)
06-09 02:40:10.448 599 599 W ReflectionUtils: Caused by: java.io.FileNotFoundException: res/drawable-xxhdpi-v4/action_bar_back_normal_dark.png
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.AssetManager.openNonAssetNative(Native Method)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.AssetManager.openNonAsset(Unknown Source:17)
06-09 02:40:10.448 599 599 W ReflectionUtils: at android.content.res.ResourcesImpl.loadDrawableForCookie(Unknown Source:429)
06-09 02:40:10.448 599 599 W ReflectionUtils: ... 12 more
06-09 02:40:10.448 599 599 I ZygoteInitInjector: ...preloaded 0 miui sdk resources in 2ms.
...that resource exists in miuisystem.apk (IIRC, might be miui.apk), which is whitelisted now and indeed on the classpath (I see it in all the dex2oat related calls elsewhere). But for some reason it still can't seem to find it - it's resources aren't "included" for some reason.
Back in the day we had to add framework apk's to framework smali (AssetManager or some such class) when porting to get resources included, but we're already using 100% MIUI framework anyway so that should already be done.....
Now this is only a preload error - system should still boot after that. But what's worse is this error later on:
Code:
06-09 02:40:21.360 1632 1632 W ResourceType: DynamicRefTable(0x10): No mapping for build-time package ID 0x10.
06-09 02:40:21.361 1632 1632 W ResourceType: e[0x01] -> 0x01
06-09 02:40:21.361 1632 1632 W ResourceType: e[0x7f] -> 0x7f
06-09 02:40:21.361 1632 1632 E ResourceType: Failed resolving bag parent id 0x100d0100
06-09 02:40:21.373 1632 1684 D SystemServerInitThreadPool: Finished executing ReadingSystemConfig
06-09 02:40:21.377 1632 1632 I libthemeutils: Theme´╝Ü libthemeutil.so load success
06-09 02:40:21.383 1632 1632 E System : ******************************************
06-09 02:40:21.383 1632 1632 E System : ************ Failure starting system services
06-09 02:40:21.383 1632 1632 E System : java.lang.RuntimeException: Failed to create service com.android.server.am.ActivityManagerService$Lifecycle: service constructor threw an exception
06-09 02:40:21.383 1632 1632 E System : at com.android.server.SystemServiceManager.startService(Unknown Source:178)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.SystemServer.startBootstrapServices(Unknown Source:81)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.SystemServer.run(Unknown Source:266)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.SystemServer.main(Unknown Source:10)
06-09 02:40:21.383 1632 1632 E System : at java.lang.reflect.Method.invoke(Native Method)
06-09 02:40:21.383 1632 1632 E System : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
06-09 02:40:21.383 1632 1632 E System : at com.android.internal.os.ZygoteInit.main(Unknown Source:306)
06-09 02:40:21.383 1632 1632 E System : Caused by: java.lang.reflect.InvocationTargetException
06-09 02:40:21.383 1632 1632 E System : at java.lang.reflect.Constructor.newInstance0(Native Method)
06-09 02:40:21.383 1632 1632 E System : at java.lang.reflect.Constructor.newInstance(Constructor.java:334)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.SystemServiceManager.startService(Unknown Source:135)
06-09 02:40:21.383 1632 1632 E System : ... 6 more
06-09 02:40:21.383 1632 1632 E System : Caused by: android.content.res.Resources$NotFoundException: File res/xml/power_profile.xml from xml type xml resource ID #0x1170010
06-09 02:40:21.383 1632 1632 E System : at android.content.res.ResourcesImpl.loadXmlResourceParser(Unknown Source:190)
06-09 02:40:21.383 1632 1632 E System : at android.content.res.Resources.loadXmlResourceParser(Unknown Source:23)
06-09 02:40:21.383 1632 1632 E System : at android.content.res.Resources.getXml(Unknown Source:3)
06-09 02:40:21.383 1632 1632 E System : at com.android.internal.os.PowerProfile.readPowerValuesFromXml(Unknown Source:9)
06-09 02:40:21.383 1632 1632 E System : at com.android.internal.os.PowerProfile.<init>(Unknown Source:14)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.am.BatteryStatsService.<init>(Unknown Source:104)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.am.ActivityManagerService.<init>(Unknown Source:900)
06-09 02:40:21.383 1632 1632 E System : at com.android.server.am.ActivityManagerService$Lifecycle.<init>(Unknown Source:5)
06-09 02:40:21.383 1632 1632 E System : ... 9 more
06-09 02:40:21.383 1632 1632 E System : Caused by: java.io.FileNotFoundException: res/xml/power_profile.xml
06-09 02:40:21.383 1632 1632 E System : at android.content.res.AssetManager.openXmlAssetNative(Native Method)
06-09 02:40:21.383 1632 1632 E System : at android.content.res.AssetManager.openXmlBlockAsset(Unknown Source:17)
06-09 02:40:21.383 1632 1632 E System : at android.content.res.ResourcesImpl.loadXmlResourceParser(Unknown Source:48)
06-09 02:40:21.383 1632 1632 E System : ... 16 more
That's a resource that exists in the base framework-res.apk - but it's not being loaded for some reason.
I think the ResourceType errors just before it are a clue. The 0x10 might be a special ResourceType that MIUI adds. But ResourceTypes.cpp is part of androidfw (libandroidfw.so) - so it looks like it will need to be replaced.
This means that a true GSI MIUI may be impossible libandroidfw.so will definitely be linked against many other objects that MIUI has modified, and who knows how many of them are hardware-dependent.
I will make that attempt in replacing the required libs after libandroidfw.so (a tedious process of elimination) to at least see if it solves the resources problem. But if anybody knowledgeable enough comes a cross this and can help, please do.
CosmicDan said:
Of course it's possible. Just a matter of someone skilled and interested enough to do it.
Off topic, though. I'm not doing EMUI. I might do Flyme because I've never used it, but probably not because I am not experienced with it (I have been porting MIUI since 2012).
Once I get MIUI up it will include build scripts though, so maybe it can help someone else work on porting other ROMs.
Another small update: In order to maintain as much GSI compatibility as possible, some hardware-related MIUI features will very likely be broken. I had to strip their custom camera stuff out already, for example - so that means using your own device's or AOSP compatible camera.
Click to expand...
Click to collapse
Well we don't need to worry about flyme coz it has a patchrom project and it's still in maintenance.And since flyme updated to oreo ,we can patch an aosp gsi into flyme gsi.
Related
I dont really understand why only for this devices but please someone make it work on the Play!
Link: http://forum.xda-developers.com/showthread.php?p=20329850#post20329850
From xperia blog -
The alpha ROM will only work on three Xperia phones: arc S, neo V and ray. For those Xperia arc and Xperia neo users wondering whether they should try this, you are warned not to as the phones have different partition layouts compared to the arc S and neo V.
EDIT- Was meant to explain why it was only for those devices ; they prob have the same partition layout.
Nabeel_Nabs said:
From xperia blog -
The alpha ROM will only work on three Xperia phones: arc S, neo V and ray. For those Xperia arc and Xperia neo users wondering whether they should try this, you are warned not to as the phones have different partition layouts compared to the arc S and neo V.
Click to expand...
Click to collapse
But that does not mean that a dev can not change it a bit to make it work on the play correctly.
im downloading the arcs build now to examine it
i would take al look on this.
Maybe i get it working for the play (would be nice)
nickholtus said:
i would take al look on this.
Maybe i get it working for the play (would be nice)
Click to expand...
Click to collapse
nick extract the kernel from the arcs build and try flashing that with your ICS update.zip
might work!
In the arc forum they confirmed that the arc s build works on the arc. Maybe it works on the play too?
directly flashing the files to play partly works, im working through fixing issues now
edit: ok currently stuck at : D/dalvikvm( 630): GC_CONCURRENT freed 260K, 4% free 9790K/10119K, paused 2ms+3m
s
I/SurfaceFlinger( 647): SurfaceFlinger is starting
I/SurfaceFlinger( 647): SurfaceFlinger's main thread ready to run. Initializing
graphics H/W...
E/HAL ( 647): load: module=/system/lib/hw/gralloc.msm7x30.so
E/HAL ( 647): Cannot load library: link_image[1908]: 647 missing essentia
l tables
E/FramebufferNativeWindow( 647): Couldn't get gralloc module
E/SurfaceFlinger( 647): Display subsystem failed to initialize. check logs. exi
ting...
happens for both sensors and gralloc,
from wich phone are you using the files?
neo v arc s or ray
DJ_Steve said:
directly flashing the files to play partly works, im working through fixing issues now
edit: ok currently stuck at : D/dalvikvm( 630): GC_CONCURRENT freed 260K, 4% free 9790K/10119K, paused 2ms+3m
s
I/SurfaceFlinger( 647): SurfaceFlinger is starting
I/SurfaceFlinger( 647): SurfaceFlinger's main thread ready to run. Initializing
graphics H/W...
E/HAL ( 647): load: module=/system/lib/hw/gralloc.msm7x30.so
E/HAL ( 647): Cannot load library: link_image[1908]: 647 missing essentia
l tables
E/FramebufferNativeWindow( 647): Couldn't get gralloc module
E/SurfaceFlinger( 647): Display subsystem failed to initialize. check logs. exi
ting...
happens for both sensors and gralloc,
Click to expand...
Click to collapse
That means exactly? Also did you use the arc version or the neo v version?
IE-coRe said:
That means exactly? Also did you use the arc version or the neo v version?
Click to expand...
Click to collapse
Edit: haha nick was quicker xD
oh i clicked the quote insetead the edit button. Sorry^^
arc s version, was first one i picked it means its missing something somewhere but im not certain what
But you where able to install it and it boots?
it flashes and attempts to boot but no display due to those errors, but adb is runnind (although i needed to slightly mod boot img to get adb )
okay... doomloard said he will take a look on the play when he is done with the arc. lets hope he can help.
ill keep playing also
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
my modified boot image that forces adb mode rather than mtp is available : http://build.streakdroid.com/bootic.img
maybe you can use neo v (did you replaced files in boot.img with some files from play boot.img?
what files would need replacing, other than for uevent maybe, ill look at that next
............
nickholtus said:
maybe you can try it with this kernel: http://www.multiupload.com/7K22QRYC05
Click to expand...
Click to collapse
what kernel is that and what phone is it for ?
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).
Hello,
I'm opening this thread to provide some info about a bug introduced in the nougat releases.
Since 7.0 first release build-in VPN client is broken, any connection end with an error under the menu entry, without any traffic goingout of the device.
Logcat shows a link error un the racoon binary (responsible of ipsec connections):
Code:
12-11 10:16:19.669 3496 3496 F libc : CANNOT LINK EXECUTABLE "/system/bin/racoon": cannot locate symbol "DES_is_weak_key" referenced by "/system/bin/racoon"...
12-11 10:16:19.669 3496 3496 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 3496 (racoon)
12-11 10:16:19.725 3497 3497 F DEBUG : pid: 3496, tid: 3496, name: racoon >>> /system/bin/racoon <<<
This feature was working in LP/MM, but is broken since first N release. Digging a bit into the MM libs looks like the symbol "DES_is_weak_key" was in the dynamic table of libWVStreamControlAPI_L3.so library (which is missing in N):
Code:
$ ./aarch64-linux-android-objdump -T /mnt/vendor/lib/libWVStreamControlAPI_L3.so | grep DES_is_weak_key
0019b9ac g DF .text 00000028 Base DES_is_weak_key
Hope this helps to develop a fix in next updates.
Best regards,
Hello magamo79,
thank you for providing these infos. That is probably the best bug report, we have ever got .
We are using an older racoon binary in vendor which is wrong. I already made a bigger cleanup on s3 plus (which also removes this binary from vendor so that it gets build from source). This change is missing in s3 repos. We will work on merging them in the next days. Then this error will also be fixed.
Short correction: DES_is_weak_key isn't defined by libWVStreamControlAPI_L3. It is only used in libWVStreamControlAPI_L3 and racoon. This symbol got defined by openssl which isn't used in android anymore.
Cheers
Hi again,
The VPN error is fixed in that last build (Build [7.1.1] 20170105 - Stable 6). Great Job @fire855 & Team :good:
Best regards,
Hi Dev's... I'm trying to port MM rom From S5 Exynos... So i took rom from their and kernel from Tab S (Because it have the same Exynos 5420) and got this main errors in boot
03-26 07:58:51.900 2299 2337 I sdp.engine_list: Socket created with fd:-1
03-26 07:58:51.900 2299 2337 E sdp.engine_list: Exiting
03-26 07:58:51.940 2597 2726 E SamsungPowerSound: earphone state reading is fa
iled
Sent from my SM-N900 using Tapatalk
Yahia Angelo said:
Hi Dev's... I'm trying to port MM rom From S5 Exynos... So i took rom from their and kernel from Tab S (Because it have the same Exynos 5420) and got this main errors in boot
03-26 07:58:51.900 2299 2337 I sdp.engine_list: Socket created with fd:-1
03-26 07:58:51.900 2299 2337 E sdp.engine_list: Exiting
03-26 07:58:51.940 2597 2726 E SamsungPowerSound: earphone state reading is fa
iled
Click to expand...
Click to collapse
@tincho5588 can you help me with this
Yahia Angelo said:
Hi Dev's... I'm trying to port MM rom From S5 Exynos... So i took rom from their and kernel from Tab S (Because it have the same Exynos 5420) and got this main errors in boot
03-26 07:58:51.900 2299 2337 I sdp.engine_list: Socket created with fd:-1
03-26 07:58:51.900 2299 2337 E sdp.engine_list: Exiting
03-26 07:58:51.940 2597 2726 E SamsungPowerSound: earphone state reading is fa
iled
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Hi Hope help you. ( sorry i don't know about Create and edit android kernel and rom )
http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
and one thing are you sure you have all SDK and JDK and anything need for Android developer . i suggest to use Builduntu
http://forum.xda-developers.com/showthread.php?t=2585828
@Dilshad Younes
@henrylife could you please help ?
@Yahia Angelo Hi ,check this out stock marshmallow kernel for N900. It is ported from Tab S
android_kernel_samsung_universal5420/build.sh at stock-6.0 · jcadduono/android_kernel_samsung_universal5420 · GitHub
https://github.com/jcadduono/android_kernel_samsung_universal5420/blob/stock-6.0/build.sh
We have kernel, we have developers, i think finally its time to taste Marshmallow.
Hi guys,
Just thought I'd open up a thread where I can share my advancement on porting this great ROM
I am no porting expert, so I am really hoping to get some pointers and maybe some help from users and developers
The link to the ROM I want to port is this: https://forum.xda-developers.com/ga...ment/rom-prometheuslite-a6-port-v1-0-t3810860
Thanks to @ananjaser1211 for giving me the opportunity to port his great work
Both having the same processor makes things a whole lot easier, so there hasn't been much input on my part lol
Here I want to list the things that I have working and not-working so far:
Working:
-Edge screen
-Smart select
-Scroll capture
-Pop-up multiwindow
-Bixby vision (to some extent, haven't gotten it fully functional on the camera)
Most of these are almost framework dependent, so that is why they work pretty well.
Now, on to the things that don't work and I might need some pointers to make them work
Not working:
-Always On Display
-Infinity wallpapers
-Edge lighting (though, I think this doesn't work on the original ROM either)
I am of course still testing a few things here and there and trying to fix as much as possible.
Any suggestion is welcome, though I will try not to modify Anan's original ROM too much to keep it as close to his version as possible
I am attaching a few screenshots of what's working so far
Any questions, feel free to ask. Well, except ETA, I would appreciate that
Thanks guys!
I'm getting a very interesting crash on SystemUI.
It seems that if I replace the SystemUI, even with an exact copy of the UI I am using right now, I get the following crash upon reboot:
Code:
11-06 10:20:55.644 5392 6197 E AndroidRuntime: FATAL EXCEPTION: UEventObserver
11-06 10:20:55.644 5392 6197 E AndroidRuntime: Process: com.android.systemui, PID: 5392
11-06 10:20:55.644 5392 6197 E AndroidRuntime: java.lang.RuntimeException: Unable to open socket for UEventObserver
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver.nativeSetup(Native Method)
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver.-wrap3(Unknown Source:0)
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver$UEventThread.run(Unknown Source:0)
11-06 10:20:55.644 5392 5392 D StorageNotification: onDiskScannedInternal (DiskInfo{disk:179,32}:
11-06 10:20:55.644 5392 5392 D StorageNotification: flags=SD size=63864569856 label= volumeCount=1
11-06 10:20:55.644 5392 5392 D StorageNotification: sysPath=/sys//devices/13560000.dwmmc2/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1
11-06 10:20:55.644 5392 5392 D StorageNotification:
11-06 10:20:55.644 5392 5392 D StorageNotification: )
11-06 10:20:55.644 2652 2652 E audit : type=1300 audit(1541521255.625:347): arch=40000028 syscall=281 per=8 success=no exit=-13 a0=10 a1=2 a2=f a3=eb3da4e0 items=0 ppid=2757 pid=6197 auid=4294967295 uid=10008 gid=10008 euid=10008 suid=10008 fsuid=10008 egid=10008 sgid=10008 fsgid=10008 tty=(none) ses=4294967295 comm="UEventObserver" exe="/system/bin/app_process32" subj=u:r:priv_app:s0:c512,c768 key=(null)
11-06 10:20:55.645 3204 4259 D Notification: allPendingIntents
11-06 10:20:55.645 2837 2837 W keystore: ENTER remove operation from uid 10050
11-06 10:20:55.646 3204 4330 V RescueParty: Disabled because of manual property
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : SHIP
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : debug level:0x4f4c
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : Finally, system will skip dumpstate
11-06 10:20:55.646 2652 2652 E audit : type=1327 audit(1541521255.625:347): proctitle="com.android.systemui"
11-06 10:20:55.646 3204 4330 W ActivityManager: crash : com.android.systemui,0
11-06 10:20:55.646 3204 3224 D SecurityLogAgent:SEDenialService: Got Modify Event and sending Denial Intent for audit.log / "com.android.systemui"
11-06 10:20:55.647 3204 3224 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:0 com.android.server.SEDenialService$AuditFileObserver.onEvent:126 android.os.FileObserver$ObserverThread.onEvent:40 android.os.FileObserver$ObserverThread.observe:-2 android.os.FileObserver$ObserverThread.run:2
11-06 10:20:55.647 3204 4330 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
11-06 10:20:55.648 5392 5392 D StorageNotification: start() notiListSize is [1]
11-06 10:20:55.648 5661 5661 I SEMS:SamsungAccount: Not Skip Name Validation by accountMCC
11-06 10:20:55.649 5392 5392 D StorageNotification: start() Notification ID (27)
11-06 10:20:55.649 5392 6197 I Process : Sending signal. PID: 5392 SIG: 9
You can find the full log: Here
Interestingly, if I reboot normally without replacing SystemUI, the system boots fine.
If I replace the SystemUI (even with a copy of what I currently have in the folder), it crashes upon reboot but works fine if I don't do a reboot
Can't fix it it with a recovery of the /system partition
I have to do a recovery of the /data partition, so I'm sure something gets messed up there
Can anybody help?
Ok, I'm going to have to backtrack a little
Initially, I kept getting crashes on something called SSRM (which exists in system/framework/ssrm.jar)
It was calling some methods that exist in port framework.jar and services.jar but not on stock fw.
I tried to take the easy way out and replace ssrm.jar with stock ssrm.jar because they differ way too much. I'm talking like, SERIOUSLY a lot (80% different in regards to smali and location of said smali, even names.)
It works to get it booted and running without problems, but then I get the issue I stated on post #2 when I want to change anything regarding the SystemUI. I haven't tried installing ROM from a clean install but my best bet is that it's going to cause problems too (will update this post because I want to try it)
So here we go again, attempting the port from 0
I had done very little work on it, anyway so it's not a huge loss
Hopefully ai can come back with positive news on the weekend, where I can give it a better look
workin bro in j600g?
ezer90 said:
workin bro in j600g?
Click to expand...
Click to collapse
Yes, my variant is J600G
However I haven't made any real progress, that's why I haven't shared it yet
ShaDisNX255 said:
Yes, my variant is J600G
However I haven't made any real progress, that's why I haven't shared it yet
Click to expand...
Click to collapse
My variant is J600GM
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
ezer90 said:
My variant is J600GM
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
Click to expand...
Click to collapse
Stock kernel
Hows sensor? Do you yave telegram
slazh101 said:
Hows sensor? Do you yave telegram
Click to expand...
Click to collapse
Sensor? I don't understand.
Ues, same username in Telegram
What about J600F ? Can you add support for J600F later?
zahidul.sifat said:
What about J600F ? Can you add support for J600F later?
Click to expand...
Click to collapse
I can't add support to a device I don't have. Maybe there are no differences between variants but I can't guarantee it
ShaDisNX255 said:
Hi guys,
Just thought I'd open up a thread where I can share my advancement on porting this great ROM
I am no porting expert, so I am really hoping to get some pointers and maybe some help from users and developers
The link to the ROM I want to port is this: https://forum.xda-developers.com/ga...ment/rom-prometheuslite-a6-port-v1-0-t3810860
Thanks to @ananjaser1211 for giving me the opportunity to port his great work
Both having the same processor makes things a whole lot easier, so there hasn't been much input on my part lol
Here I want to list the things that I have working and not-working so far:
Working:
-Edge screen
-Smart select
-Scroll capture
-Pop-up multiwindow
-Bixby vision (to some extent, haven't gotten it fully functional on the camera)
Most of these are almost framework dependent, so that is why they work pretty well.
Now, on to the things that don't work and I might need some pointers to make them work
Not working:
-Always On Display
-Infinity wallpapers
-Edge lighting (though, I think this doesn't work on the original ROM either)
I am of course still testing a few things here and there and trying to fix as much as possible.
Any suggestion is welcome, though I will try not to modify Anan's original ROM too much to keep it as close to his version as possible
I am attaching a few screenshots of what's working so far
Any questions, feel free to ask. Well, except ETA, I would appreciate that[emoji14]
Thanks guys!
Click to expand...
Click to collapse
Please link test rom, my model j600g
Sent from my SM-J600G using XDA-Developers Legacy app
manuelamadeo said:
Please link test rom, my model j600g
Sent from my SM-J600G using XDA-Developers Legacy app
Click to expand...
Click to collapse
Please don't quote the entire OP
I am not done porting it since that is why I haven't shared it yet
ShaDisNX255 said:
Please don't quote the entire OP
I am not done porting it since that is why I haven't shared it yet
Click to expand...
Click to collapse
If you need help, you can count on me, my knowledge is not so many but in what I can help I will.
Sent from my SM-J600G using XDA-Developers Legacy app
I'm probably going to end this project.
While Prometheus ROM is relatively easy to port since both devices share the same processor, I noticed slight differences and it mainly has to do with the screen ratio. I can't activate the full screen on games and I am betting it has to do something in framework. Which is probably easy to revert back to allow it, but I am waaaaaaaay too lazy to look it up
Besides, I've been wanting to port the S9 firmware for a while now, and do it on my own
I am certain that Prometheus is going to be a better alternative than my S9 ported firmware, this is sort of a personal thing. I want to be able to port this firmware by myself.
But who knows, I'll update when I can because I haven't really done anything to the ROM (Prometheus)
I don't think I'll be sharing it either because:
1) It is a half-finished port, there are many bugs to be expected (but from personal use, I haven't experienced any bugs other than theme store crashing about once a day and Bixby vision on camera not working)
and
2) Can't install it by a clean install (wiping /data). I can only get this running on a dirty flash without wiping /data
Lazy lazy lazy is all I can say lol but yeah
After I port my own S9 firmware as a base, maybe I can come back to this as I am sure anan added more things than I would add to mine xD
Thanks everyone for understanding
ShaDisNX255 said:
I'm probably going to end this project.
While Prometheus ROM is relatively easy to port since both devices share the same processor, I noticed slight differences and it mainly has to do with the screen ratio. I can't activate the full screen on games and I am betting it has to do something in framework. Which is probably easy to revert back to allow it, but I am waaaaaaaay too lazy to look it up
Besides, I've been wanting to port the S9 firmware for a while now, and do it on my own
I am certain that Prometheus is going to be a better alternative than my S9 ported firmware, this is sort of a personal thing. I want to be able to port this firmware by myself.
But who knows, I'll update when I can because I haven't really done anything to the ROM (Prometheus)
I don't think I'll be sharing it either because:
1) It is a half-finished port, there are many bugs to be expected (but from personal use, I haven't experienced any bugs other than theme store crashing about once a day and Bixby vision on camera not working)
and
2) Can't install it by a clean install (wiping /data). I can only get this running on a dirty flash without wiping /data
Lazy lazy lazy is all I can say lol but yeah
After I port my own S9 firmware as a base, maybe I can come back to this as I am sure anan added more things than I would add to mine xD
Thanks everyone for understanding
Click to expand...
Click to collapse
I would like you to pass me the link and tinker, continue with your progress, the bug you mentioned is not a problem for me, please send Link for download by private.
Sent from my [device_name] using XDA-Developers Legacy app
Is there any method to root Samsung J600G ???
Good news
Seems that my S9 port is almost ready to go.
I'm testing this whole week to make sure I don't have major bugs, but for the most part it seems to be stable
I am trying to fix just one final thing, which is the Game Tools that don't seem to work, they don't appear on any game
I've lost one neat feature that Prometheus had and that the S9 doesn't, which is Bixby Vision on screen capture. Or even on the camera, for that matter.
In fact, I ditched the S9 camera and kept stock (for now) as I did not want to get into camera specifics for the time being, for this first version all I want to do is get a solid S9 firmware port for you guys to help me figure out some small bugs maybe I can try to fix.
On the flip side, I gained Infinity Wallpapers that I couldn't get to work on Prometheus on the J6 for some reason, but that's my fault as I just didn't give enough effort on it :S
Also Edge lighting works great, I am so happy to have this feature
Huge thanks to @ananjaser1211 for sharing his knowledge and experience on his S9 port and fixes he shared with me, I would have been lost without his help.
I haven't tried things like face recognition, which I believe will also give problems but I'll slowly start testing all these things out and if all goes well, I'll share the ROM in 6 days time
Thanks everyone for being so patient
Good i want to learn how to port ill wait you does this firmware have features for game? Like over locking gpu ? Because some games ceash becuase stock kernel have a default gpu clocm to 343mhz while the gpu came with 1001 mhz..
zzDoWnzz said:
Good i want to learn how to port ill wait you does this firmware have features for game? Like over locking gpu ? Because some games ceash becuase stock kernel have a default gpu clocm to 343mhz while the gpu came with 1001 mhz..
Click to expand...
Click to collapse
Nope, no overclocking features. I didn't touch the kernel as I have 0 knowledge on kernel building and lack my own PC to do so.
I mean the software has "Performance mode" in it, but I doubt it really improves on anything as again, it is stock kernel and lacks modification to unlock some features like AOD.
My humble suggestion would be, don't expect much out of this device. It is a 3 year old processor and if you want any sort of gaming power I would buy a newer phone. Samsung really cheaped out on the J6, just seems like a lazy device lol