Database Develop

[SOLVED] CameraRunner.exe not found (Problem caused by osKitchen alpha)

I've been trying to build my own ROM using osKitchen. Everything has worked and I've been able to upgrade a stock ROM to build 23569. The only problems I've had are with the panel and camera software. The panel and camera buttons on my phone don't work. Pressing either of them will give me an error that the program that should be launched can't be found. CameraRunner.exe is in the Windows folder. I am able to launch it but none of the icons for the UI and menus appear. I am still able to take pictures.
PanelManager.exe is different. When I run that I'm presented with a black screen. I am unable to do anything to close it. It hijacks the Today screen. Other than that the phone will still work normally.
I assumed that these problems were caused by changes I made to the ROM but that doesn't appear to be the case. I imported my stock ROM into osKitchen and built it without changing anything. The resulting ROM had the same issues.
I searched the forums but could not find a solution to this problem. Does anyone know how to fix this? Thanks in advance.

For CameraRunner.exe, did you include the Xperia camera package?
For the Panels, you probably excluded one or more packages needed for this to run proper.

try this camera package

Lokatho said:
For CameraRunner.exe, did you include the Xperia camera package?
For the Panels, you probably excluded one or more packages needed for this to run proper.
Click to expand...
Click to collapse
I initially thought that might be the case but I tried building the ROM with all original packages included and without any modifications and it still has this issue.
spikegotti said:
try this camera package
Click to expand...
Click to collapse
The package didn't help. Pressing the camera button gives me an error and the icons are still missing if I run CameraRunner.exe manually.

I was using OSKitchen too, having troubles(Not sure how to get it to the next rom or w/e) anyway to get camera to work, I used the X2 Camera Update as a package Use the Package Converter option up the top > choose cab > choose the camera > tick it > build ROM > Install ROM > Camera should work
Also my panel manager didnt work through OSKitchen either.

I figured out the problem. The alpha version of osKitchen doesn't copy the PROVXML files into the ROM, which means that the files for the camera and panel software won't be moved to their correct locations. The old version, 1.30v3, doesn't have this problem. The camera and panels work in the ROMs I've built using that version.

glad you could work it our
can you pls change thread title, like add [SOLVED] and rephrase to better describe the content?
thx a lot, appreciate your help

I added [SOLVED] to the title of the thread but I don't understand what you want me to rephrase.

hey, I meant it like this: you don't have problems with the file in one of the custom roms available here (with the need to just reinstall it) but while trying to cook your own and the problem was kitchen (oskitchen, alpha) related, so it would be nice to have that in the thread title to clarify the content and that it's dev related, nothing more, just a suggestion
thx and best

[OBSOLETE] Disable OTA update notification

When an OTA update becomes available, there is a recurrent notification prompting to upgrade.
The below method tricks the OS into thinking that it is already at the latest version, in effect stopping the update notification from appearing.
I am not responsible for anything you do with your device.
Pre-requisite
Device must be rooted
Steps
Download FOTAKill apk
Put the apk in "/system/app"
Set proper file permissions (644, or rw-r--r--) for the apk
Clear "/cache" (e.g. boot into CWM and clear cache)
Reboot
Check "Settings > About tablet > System updates" and it should show "up to date" now.
Note that after rebooting there may still be a notification to update, after clearing no further notification will appear.
Rollback
To re-enable OTA update notification, delete the apk and reboot!

iamelton said:
lately since Android 4.2 OTA update became available for my device, there was a recurrent update notification prompting me to update..
as i dont want to upgrade yet due to app incompatibility issues not being resolved, i asked for help and was given a solution after searching and reading some posts..
it worked for me and i would like to share it here as i found that there were other users looking for a solution like i did..
ur device needs to be rooted to follow the steps below..
steps:
(1) download FOTAKill (firmware over-the-air kill) apk
(2) put the apk in "/system/app" with a file explorer
(3) set proper file permissions (644) for the apk
(4) clear "/cache" (i booted into CWM and cleared cache there)
(5) reboot
(6) check "Settings > About tablet > System updates".. should tell you "up to date" now..
note that after rebooting i still got a notification on update, but after clearing it there was no further notification since then..
Click to expand...
Click to collapse
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date

Worked great, better than messing around with Google services framework.

Another possibility to get rid of OTA updates reminders on 4.1.2:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.

OR... download Autorun manager from the Play store and disable the following in Services( must enable system settings in preferences)
Receiver com.google.android.gsf.update.SystemUpdateService
Requires root access

wilx said:
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Click to expand...
Click to collapse
Same here thank you iamelton!

andro54 said:
Same here thank you iamelton!
Click to expand...
Click to collapse
Same here didn't need to clear cache. The whole thing took about 30 seconds.
Thank you
Sent from my Nexus 7 using xda app-developers app

the clear cache part is for those who might have already downloaded the update package file (which is about 80MB) by the ota service.. it removes this file and frees up some cache space..

What does FOTAkill actually do to your system?
Sent from my Nexus 7 using Tapatalk 2

ExploreMN said:
What does FOTAkill actually do to your system?
Click to expand...
Click to collapse
That's a GREAT question.
iamelton do you know the specifics? It would also be interesting to know what permission if any are effected with this method.
Sent from my Nexus 7 using xda app-developers app

sorry but i have no idea what it actually does to the system, apart from the obvious function of stopping the OTA service..
from this page, it requires the following permissions..
Code:
android.permission.RECEIVE_BOOT_COMPLETED
com.google.android.providers.gsf.permission.WRITE_GSERVICES
com.google.android.providers.gsf.permission.READ_GSERVICES

It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.

datorprofessor said:
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
Click to expand...
Click to collapse
afaik it should stop any future OTA updates regardless of android versions..
and granting permission 755 is more than the needed 644, but that does no harm..
i thought 4.2 was the version with multi-user support, but then im not on 4.2 yet so cant tell much about it..

What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app

gelhack said:
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i think removing the apk from /system/app/ should allow OTA notifications to show again, though i have not tried it yet..
btw, we have the same reason as why not to upgrade..

I used this from other thread, forgot where it is.
"Install Autostarts app.
Go to "After Startup"
Scroll down until you see "Google Services Framework"
There should be several of them. For me it was the third one. Touch it and read the bottom of the popup to find out. It will say "Receiver com.google.android.gsf.update.SystemUpdateService. ....(you get the point)
Disable it. Done..."
Peaceful on 4.1.2.

There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.

helloterence said:
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
Click to expand...
Click to collapse
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..

iamelton said:
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
Click to expand...
Click to collapse
Nope. I'm still on 4.1.2 and haven't gotten any notification about 4.2.1.

I'm assuming that updates to 4.2 and 4.2.1 are incremental, and as such you couldn't install or get a notification for 4.2.1 until you installed 4.2. So any method that stopped 4.2 notices would also stop 4.2.1 notices.
Sent from my Nexus 7 using xda app-developers app

Help with OMNI rom

Hi,
I have flashed a custom rom for the very first time.
I have flashed OMNI rom 18/12 build.
I find the haptic feedback or the vibration intensity too high to my liking. I can't find any setting where I can configure this.
The phone vibrates very strongly even when i press things like 'menu' , 'back button' or typing
Its very annoying, please help

kckinn said:
Hi,
I have flashed a custom rom for the very first time.
I have flashed OMNI rom 18/12 build.
I find the haptic feedback or the vibration intensity too high to my liking. I can't find any setting where I can configure this.
The phone vibrates very strongly even when i press things like 'menu' , 'back button' or typing
Its very annoying, please help
Click to expand...
Click to collapse
I think your only solution for that is to turn it off... Or to find out what to change to make it lower. You do not have an option in settings for that.

shut_down said:
I think your only solution for that is to turn it off... Or to find out what to change to make it lower. You do not have an option in settings for that.
Click to expand...
Click to collapse
I am willing to turn off the haptic feedback, but I can't find any option for that anywhere.

kckinn said:
I am willing to turn off the haptic feedback, but I can't find any option for that anywhere.
Click to expand...
Click to collapse
I can't remember where it was, but I did remove it when I used Omni. Try settings>more options - search there.

shut_down said:
I can't remember where it was, but I did remove it when I used Omni. Try settings>more options - search there.
Click to expand...
Click to collapse
Hi,
Thanks again. I found the option to completely turn it off yesterday. Sad, there was no feature to reduce its intensity.
After turning it off, I realized the samsung JB always had a subtle vibration feedback when touching all this. Initially found it a bit weird getting no vibration but now used to it.
Another thing, in samsung JB I could sync FB contacts as well. In this ROM neither does the option in 'contacts' nor in FB app allow to sync contacts to phone book. Not a major issue though.
But, in samsung JB I could sync my calendar with FB, so that I could see all b'days etc on my calendar. No option here. Even though FB is displayed under 'accounts' in setting. There is no option to sync.
But the great thing about it is its speed. There is no lag whatsoever, very smooth so far.
Have a couple of free days in hand, so thinking of trying out CM 10.2 as well

kckinn said:
Hi,
Thanks again. I found the option to completely turn it off yesterday. Sad, there was no feature to reduce its intensity.
After turning it off, I realized the samsung JB always had a subtle vibration feedback when touching all this. Initially found it a bit weird getting no vibration but now used to it.
Another thing, in samsung JB I could sync FB contacts as well. In this ROM neither does the option in 'contacts' nor in FB app allow to sync contacts to phone book. Not a major issue though.
But, in samsung JB I could sync my calendar with FB, so that I could see all b'days etc on my calendar. No option here. Even though FB is displayed under 'accounts' in setting. There is no option to sync.
But the great thing about it is its speed. There is no lag whatsoever, very smooth so far.
Have a couple of free days in hand, so thinking of trying out CM 10.2 as well
Click to expand...
Click to collapse
Maybe some app can help you with FB sync.

Hi,
You may be aware of the problem with the dash clock. It force closes. And it appears partially cut in the lock screen.
After going through the OMNI rom, I found that you had mentioned in post no. #225 to go to system/app and delete dashclock.apk from there.
Since there is no file manager in this ROM. I installed ES file manager and tried to delete dashclock.apk from system/app
But when I try to delete it says "dashclock.apk can not be deleted". I don't know why ?
Is it anything to do with rooting ? I found some discussion in the forum about rooting as well. But couldn't make much of it.

kckinn said:
Hi,
You may be aware of the problem with the dash clock. It force closes. And it appears partially cut in the lock screen.
After going through the OMNI rom, I found that you had mentioned in post no. #225 to go to system/app and delete dashclock.apk from there.
Since there is no file manager in this ROM. I installed ES file manager and tried to delete dashclock.apk from system/app
But when I try to delete it says "dashclock.apk can not be deleted". I don't know why ?
Is it anything to do with rooting ? I found some discussion in the forum about rooting as well. But couldn't make much of it.
Click to expand...
Click to collapse
Root it, set usb debugging on, in ES file explorer set Root explorer ON. Or use some other root explorer if that do not work.

shut_down said:
Root it, set usb debugging on, in ES file explorer set Root explorer ON. Or use some other root explorer if that do not work.
Click to expand...
Click to collapse
I read in the OMNI forum that installing OMNI Rom automatically roots the phone. So is that not true ? If that is the case I will google and find how to root the phone.
I tried to turn on 'root explorer' in the ES file manager. It says 'Sorry, test failed. This feature can not run on your device". Is it an indicator of the the fact that the phone is not rooted ?
Edit: Temporary workaround: I found the post wherein you had told a user how to expand the dash clock widget by sliding it down and holding it and removing it by taking it to the 'x'. I removed it from the lock screen and added the normal clock in its place.

kckinn said:
I read in the OMNI forum that installing OMNI Rom automatically roots the phone. So is that not true ? If that is the case I will google and find how to root the phone.
I tried to turn on 'root explorer' in the ES file manager. It says 'Sorry, test failed. This feature can not run on your device". Is it an indicator of the the fact that the phone is not rooted ?
Edit: Temporary workaround: I found the post wherein you had told a user how to expand the dash clock widget by sliding it down and holding it and removing it by taking it to the 'x'. I removed it from the lock screen and added the normal clock in its place.
Click to expand...
Click to collapse
No it doesn't have SU binaries installed.

metalhead.mechie said:
No it doesn't have SU binaries installed.
Click to expand...
Click to collapse
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?

kckinn said:
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?
Click to expand...
Click to collapse
Just install zip in TWRP. And check if usb debugging is on later in Developer options.

kckinn said:
@metalhead.mechie Well I don't know what that means. I dont know much about tech stuff
From what I have gathered from the discussion in the OMNI Rom Forum, that I download something called 'Super SU" from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip .
Question:
1. Do i need to extract the contents of the zip ? Or just go to TWRP and just select install from SD card and select the zip folder like i did with OMNI and gapps ?
2. Will this root the phone or do I need to follow other procedure as well ?
Click to expand...
Click to collapse
Just flash the zip as shut_down said. This zip contains the binaries as well as supersu app for root acess

Network speed display EMU 3.1

Hello!
I want to switch on the network connectivity speed display. It was in the settings panel earlier, but now it disappeared.
Or maybe not completely. If I search in the settings I can see that the option exists, but when I click on it, it's hidden... (See the PIC attached)
I'm guessing there is a option in a deeper level where I can set it.
Does anyone know a solution? My phone is rooted, so if it requires editing some config files, I'm all for it.
Thanks.

Mines the same except I got no root.. how did you do yours?

I managed to root with the recovery version.
More details here: http://forum.xda-developers.com/ascend-p7/general/guide-root-b803-recovery-version-t3157477

Thanks for the reply ... I will downgrade mine to 2.3 and root it and then upgrade again if that setting becomes available again ill let you know

So i have rooted my device via your method and after reinstalling lolipop i found that the setting was stil missing. I however noticed that if you installed the lolipop update from the vodacom version posted here (http://forum.xda-developers.com/ascend-p7/general/huawei-p7-l10c02b817-android-5emui3-1-t3207363) it was there again. Unfortunatly for me there is some bugs in that update, there is no keybord app. I then started searching for a way to edit the system wide prefrence database file, where i also found the entry located inside the settings.db file , but it is not possible to edit it without corrupting the data for further use by the phone.
here are some screenshots from my findings
https://mega.nz/#!v9VjASBY!qRxEwBDQN59_fK-WRNHIfq6hJO8rKUY8rYYfpTZoCo0
https://mega.nz/#!GhtGzArS!RGP947yCgch1Ema6-g72o3lz5nrXlcth1OEhYbjRmDM
https://mega.nz/#!as921b6A!3QOG-xgwXZrADFQEHqKm7_bQSDNg-R4o-8cNW7svCkE
https://mega.nz/#!S09VFDoa!R7ccks6CnqlLgD5QyuQDMaNuDc7GHr-UOLipc6P33-k

@Unified21 @DomeNet
with root edit data/cust/prop/local.prop
find this line:
ro.config.hw_hideNetworkSpeed=true
and change it to
ro.config.hw_hideNetworkSpeed=false
reboot
Now there is a new setting entry in display section

Great it works!
Thank you!

(06/01/22)(Official)(One Ui 3.1) TinyCore 1 Stable For Galaxy M21 "The Tiny One Ui Project For Gaming"

Name Change From PixieRom To TinyCore
Sorry About No Screenshot
Features:
Very Small Apps and Priv-app folder size (Only 1.39GB Of App And Priv-App Folder Size When Calculate Together)
Most of this need to replace floating_features.xml in vendor/etc (i put in in this thread)
Google Discover Feed
Flagship Animations
Enchanted Processing
Flagship Edge Lighting Animations
And More
How to install
Extract All File Out From Zip
Flash in System in system partition
Flash vendor in vendor partition
Flash product in product partition
Format data
Finish
If want to tweak download floating_feature.xml from under of this thread then replace in vendor/etc/
Bugs:Tell me pls i don't know
Download Links
https://drive.google.com/file/d/1zHf1B6EgEemCsqEduvnKWlfPMndbmB_-/view?usp=drivesdk
Sources:
GitHub - m21-dev/android_kernel_samsung_universal9610: Kernel source for samsung universal9610-common devices
Kernel source for samsung universal9610-common devices - GitHub - m21-dev/android_kernel_samsung_universal9610: Kernel source for samsung universal9610-common devices
github.com
@soulr344 For Permissions Script
Thanks
Flylarb

Google-Drive link is broken it seems, can you post link again?

OldNoobOne said:
Google-Drive link is broken it seems, can you post link again?
Click to expand...
Click to collapse
Okay

Flylarb said:
Okay
Click to expand...
Click to collapse
Thanks, but I still get error msg for the download link above.
I'm not sure if its a problem in my browser or the link is broken.

OldNoobOne said:
Thanks, but I still get error msg for the download link above.
I'm not sure if its a problem in my browser or the link is broken.
Click to expand...
Click to collapse
I removed that
Fix now

OldNoobOne said:
Thanks, but I still get error msg for the download link above.
I'm not sure if its a problem in my browser or the link is broken.
Click to expand...
Click to collapse
Try again

Flylarb said:
Try again
Click to expand...
Click to collapse
Thanks Dev, Downloading...
EDIT -- Where should I flash the floating_feature.xml file? Is it config file for camera?

OldNoobOne said:
Thanks Dev, Downloading...
EDIT -- Where should I flash the floating_feature.xml file? Is it config file for camera?
Click to expand...
Click to collapse
Nope
Replace in vendor/etc
Also flash fix permissions

Flylarb said:
Nope
Replace in vendor/etc
Also flash fix permissions
Click to expand...
Click to collapse
Thanks Dev Flylarb, will do, flashing now
what fixpermission do but, i mean what it is for?

OldNoobOne said:
Thanks Dev Flylarb, will do, flashing now
Click to expand...
Click to collapse
Thx

Thanks Dev, Great job!
Its booting on SM-M215G/DS as well which is great,
So far I found a few issues though maybe because its not meant for M215G so but nevertheless
1) Bluetooth Not Working error popup, bluetooth does not detect devices.
2) Battery Saver Mode absent, No Battery Saver icon as well as No battery option under settings tab
3) Can't create New Folder inside Internal Storage
4) GCam not able to save or click any pictures.

OldNoobOne said:
Thanks Dev, Great job!
Its booting on SM-M215G as well which is great,
So far I found a few issues though maybe because its not meant for M215G so but nevertheless
1) Bluetooth Not Working error popup, bluetooth does not detect devices.
2) Battery Saver Mode absent, No Battery Saver icon as well as No battery option under settings tab
3) Can't create New Folder inside Internal Storage
4) GCam not able to save or click any pictures.
Click to expand...
Click to collapse
Bluetooth are main bugs
Happen for m215f as well
Battery Saver bec i remove device manager
Cant create new folder is bugs
Gcam and samsung cam is bug at camera features
Will fix in next build
If you want to contact me
My telegram is 0816278942

Flylarb said:
Bluetooth are main bugs
Happen for m215f as well
Battery Saver bec i remove device manager
Cant create new folder is bugs
Gcam and samsung cam is bug at camera features
Will fix in next build
If you want to contact me
My telegram is 0816278942
Click to expand...
Click to collapse
1) True
2) I'm not a dev or programmer but, I saw in ( Shamshung as well as Xioame) like if we deleted the Device Security or Device Manager app OR even if we disable just one of the services of those two apps, the built-in Android Battery Saver still offered Medium Battery Saving option (no extreme battery saving option) from the QS Drop-Down Menu and if we long-clicked on the battery saver icon it took us to Battery Settings option & there too only medium battery saving option available, in Pixie the whole battery option was absent. So just an observation.
3) Also, in About Device option under Settings, it shows ElementaryOS in one place and under Software Info it shows PixieOS. So thats another one I noticed.
4) One more thing I noticed is that, after flashing FixPermissions zip , I disabled a critical system app then rebooted to recovery & wiped Dalvik/ART + CACHE and when I rebooted to system after that, OS still managed to boot but kept showing a progress bar "Starting Andoid" but went back to TWRP , so I think FixPermission is partially working, if i'm not wrong. Without flashing FixPermission it wouldnt even boot , so I think FixPermission is partly working.
5) My number got banned by Telegram for some kiddish reasons but I can DM you?

OldNoobOne said:
1) True
2) I'm not a dev or programmer but, I saw in ( Shamshung as well as Xioame) like if we deleted the Device Security or Device Manager app OR even if we disable just one of the services of those two apps, the built-in Android Battery Saver still offered Medium Battery Saving option (no extreme battery saving option) from the QS Drop-Down Menu and if we long-clicked on the battery saver icon it took us to Battery Settings option & there too only medium battery saving option available, in Pixie the whole battery option was absent. So just an observation.
3) Also, in About Device option under Settings, it shows ElementaryOS in one place and under Software Info it shows PixieOS. So thats another one I noticed.
4) One more thing I noticed is that, after flashing FixPermissions zip , I disabled a critical system app then rebooted to recovery & wiped Dalvik/ART + CACHE and when I rebooted to system after that, OS still managed to boot but kept showing a progress bar "Starting Andoid" but went back to TWRP , so I think FixPermission is partially working, if i'm not wrong. Without flashing FixPermission it wouldnt even boot , so I think FixPermission is partly working.
5) My number got banned by Telegram for some kiddish reasons but I can DM you?
Click to expand...
Click to collapse
Yep
Use Discord
i will add that battery soon
Floating feature from my elementary os port so it will say elementary
Fix permissions make system boot bec it have correct permissions bec i mistake and i dont know where

Flylarb said:
Yep
Use Discord
i will add that battery soon
Floating feature from my elementary os port so it will say elementary
Fix permissions make system boot bec it have correct permissions bec i mistake and i dont know where
Click to expand...
Click to collapse
Thanks, will wait for updates or full ROM for M215G

OldNoobOne said:
Thanks, will wait for updates or full ROM for M215G
Click to expand...
Click to collapse
Full One Ui?

Flylarb said:
Full One Ui?
Click to expand...
Click to collapse
Thanks, One UI is great but anything will do, also pls work on FixPermission zip ( Q permission system will also do if not N or P ) coz its half-functional already also pls post Donate button so we can donate to you.

Hi Flylarb, do you have the updated Fixpermission.zip file? I wanted to test it on M215G.
I'm not able to login to both telegram or discord for some technical reasons.