Database Users

[Q] Galaxy s4 I9505 with Google edition andriod

Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan

dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan

dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.

[WIP] [NO RELEASE] [MEMBERS NEEDED] MIUI 7 Marshmallow [Port from MI Max]

I have started to port MIUI 7 Marshmallow rom from MI Max to Redmi Note 3.
Here is the MIUI 7 Marshmallow ROM: http://en.miui.com/download-302.html
Anyone working on the same project may contact, also anyone experienced in porting may contact too.
Initial ports will be closed released for testing and stable ports will be posted here.

MIUI8?good work

Me bro
Sent from my Redmi Note 3 using XDA-Developers mobile app

<rant>
It's fairly simple to "port" I guess, as far as I know the process consists of: downloading the MiMax ROM and copying over the hardware files from our Kenzo MIUI-7 ROM, of course before any of this your either going to need system dumps or a way to extract the firmwares, and even then you'll need to put together an update-script to properly flash it all, and then you can start testing stuff out to see what works/dosnt and then you rinse and repeat until everything works, I've done this before for another device and although it did boot, there were countless issues and the entire process is archaic and pointless tbh, building from source (but we can't since MIUI is closed source so id say just wait for MIUI8 lol) would be easier in some sense since having the source upfront helps you have an idea of wtf is actually going on compared to the guess work that is copying & pasting libs and stuff from /system/etc, my point is, just wait till June 28th or whenever were supposed to have MIUI-8 since hacking together an M based MIUI-7 for our device based on another devices firmware with "similar" hardware would just be painful and I'd feel sorry for you if you had to do such, then again I could be awfully wrong and the entire thing may work (it is quite possible) relatively easily considering the familiarity of the hardware, I just wouldn't expect it to be bugless, but someone please do prove me wrong, I'd be happy.
</rant>

DiamondBond said:
It's fairly simple to "port" I guess, as far as I know the process consists of: downloading the MiMax ROM and copying over the hardware files from our Kenzo MIUI-7 ROM, of course before any of this your either going to need system dumps or a way to extract the firmwares, and even then you'll need to put together an update-script to properly flash it all, and then you can start testing stuff out to see what works/dosnt and then you rinse and repeat until everything works, I've done this before for another device and although it did boot, there were countless issues and the entire process is archaic and pointless tbh, building from source (but we can't since MIUI is closed source so id say just wait for MIUI8 lol) would be easier in some sense since having the source upfront helps you have an idea of wtf is actually going on compared to the guess work that is copying & pasting libs and stuff from /system/etc, my point is, just wait till June 28th or whenever were supposed to have MIUI-8 since hacking together an M based MIUI-7 for our device based on another devices firmware with "similar" hardware would just be painful and I'd feel sorry for you if you had to do such, then again I could be awfully wrong and the entire thing may work (it is quite possible) relatively easily considering the familiarity of the hardware, I just wouldn't expect it to be bugless, but someone please do prove me wrong, I'd be happy.
Click to expand...
Click to collapse
1. I have ported Roms for Micromax canvas music, Micromax unite 2. They were mtk. I have themed complete rom for LG l 3 e405. It was Qualcomm.
2. Flashing will be block based. If what I have planned will work.
3. We have no other better option to get marshmallow right now. And I live in present.
4. Without trying I can't know if it is a good idea or not. What I will loose? Few hours. What many will gain? May be a stable marshmallow miui 7.
Be positive.
Sent from my Redmi Note 3 using XDA-Developers mobile app

Sudeep Duhoon said:
3. We have no other better option to get marshmallow right now. And I live in present.
4. Without trying I can't know if it is a good idea or not. What I will loose? Few hours. What many will gain? May be a stable marshmallow miui 7.
Be positive.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Keep up good work my friend. Looking forward for this..

count me in bro, i have spare redmi note 3 to test and provide logcats or anything you want.

Sudeep Duhoon said:
I have started to port MIUI 7 Marshmallow rom from MI Max to Redmi Note 3.
Here is the MIUI 7 Marshmallow ROM: http://en.miui.com/download-302.html
Anyone working on the same project may contact, also anyone experienced in porting may contact too.
Initial ports will be closed released for testing and stable ports will be posted here.
Click to expand...
Click to collapse
nice work bro...
keep moving...

I think you will be founder of quick charge 2.0 for RN3 if you can port this rom :good:

Here you have a beta tester of your work men! Good luck

Nice..can you please port to MTK?

The leaked version of
Miui 7:http://forum.xda-developers.com/showthread.php?t=3377347
and cm13:http://forum.xda-developers.com/showthread.php?t=3350656
are stable enough now. Though the initial boot was failed of Port rom. I see no point of trying now.
Please close the thread.
Sent from my Redmi Note 3 using XDA-Developers mobile app

No official Nougat drivers?

according to Qualcomm (not sure how reliable the resource is)
http://m.pocketnow.com/2016/08/26/qualcomm-snapdragon-800-801-no-android-nougat-support
Sent from my A0001 using Tapatalk

Yes, this is somewhat old news now. Qualcomm dropped drivers for the Adreno 3xx series used on the 800/801, so we have no Vulkan support and thus cannot pass CTS. Therefore, we will have no official Nougat builds. I'm sure people are working on making the drivers from Marshmallow work (maybe not with Vulkan, but still at least be able to boot and have graphics work, etc.).

Oneplus One is in the official list of devices that will receive cm14, so i guess that driver support won't be a problem

effry said:
Oneplus One is in the official list of devices that will receive cm14, so i guess that driver support won't be a problem
Click to expand...
Click to collapse
"Official" list? Source? AFAIK CM hasn't posted anything since Nougat source dropped

MI A2 lite getting PIE update

Question to the developers here. Anyone excited about this update? The G5+ and the A2 lite are basically the same device aside from the battery and camera. Possible 64bit pie port in the future?

JohnSmith8786 said:
Possible 64bit pie port in the future?
Click to expand...
Click to collapse
There has been 64 bit pie since android pie has been on our phone.

Hirorails said:
There has been 64 bit pie since android pie has been on our phone.
Click to expand...
Click to collapse
But most of the ported ROM's have VOLTE troubles and UI issues. NFC isn't working good too. If a port from a phone which has nearly the same hardware and near stock experience, I think his question is valid and probably devs should consider this.

All ROMs will need to implement proper Bluetooth, NFC or fingerprint blobs to work properly. This also requires to flash stock Oreo before flashing any of Pie ROM. Volte issue is basically issue because of Persist partition. I am not sure about any issues with UI. Anyway ArrowOS from built released on 26/11 has already solved all issues and NFC for example works fine. I am using for last two days and so far nothing is wrong with it. You can't say A2 is same if it hasn't different camera for example. it might have other components or chips which differs. For example Moto Z Play (Addidson) has same components as potter except camera and anyone trying to flash ROM from it was bricking G5+. Also because of that there was never a possiblity to release an official Lineage.

It will surely be beneficial to us. Someone already ported Dirac and audio libs from MI A2 to potter for better overall sound quality.

Can i use the device tree from K20 Pro?

I'm interested to build for Redmi Mi 9T/K20 and now i will know, can i use the device tree from raphael(K20 Pro)?

I know there is a thread and all for treble k20 pro roms that brave k20 users have flashed, and apparently work the same.
I'm precisely looking for the same as you, build a treble rom (pixelexperience) with phhusson's patches with the k20 kernel source.
The kernel is the only source i'm aware that exists for the k20, unless somebody has found vendor and the rest.
Things to note:
I followed phhussons treble guide up to a certain point, I currently have pixelex cloned.
Im stuck at where to put xiaomis source in the manifests (if I need it at all)
Its a system a/b arm64 device.
Edit: My master plan is to build a clean twrp, a kernel with spectrum support and a low 600mhz preferred clock speed until gpu opengl is fired up, pixelexperience with a few useful mods and magisk pre-baked (although i doubt this point).
Appreciate any help
I would like the k20 to have proper dedicated rom threads, since many international users cannot get the k20 pro.

superwave99 said:
I know there is a thread and all for treble k20 pro roms that brave k20 users have flashed, and apparently work the same.
I'm precisely looking for the same as you, build a treble rom (pixelexperience) with phhusson's patches with the k20 kernel source.
The kernel is the only source i'm aware that exists for the k20, unless somebody has found vendor and the rest.
Things to note:
I followed phhussons treble guide up to a certain point, I currently have pixelex cloned.
Im stuck at where to put xiaomis source in the manifests (if I need it at all)
Its a system a/b arm64 device.
Edit: My master plan is to build a clean twrp, a kernel with spectrum support and a low 600mhz preferred clock speed until gpu opengl is fired up, pixelexperience with a few useful mods and magisk pre-baked (although i doubt this point).
Appreciate any help
I would like the k20 to have proper dedicated rom threads, since many international users cannot get the k20 pro.
Click to expand...
Click to collapse
What's different from the k20 pro ? Only the processor?

lucki1000 said:
What's different from the k20 pro ? Only the processor?
Click to expand...
Click to collapse
Processor is the big difference, camera is too but sony has bundled the drivers together

superwave99 said:
Processor is the big difference, camera is too but sony has bundled the drivers together
Click to expand...
Click to collapse
Yes but processor is kernel stuff and not device tree stuff and the kernel source did we have.

lucki1000 said:
Yes but processor is kernel stuff and not device tree stuff and the kernel source did we have.
Click to expand...
Click to collapse
Nobody has found the k20 tree yet.
Edit: Actually, the sources might be the whole thing bundled together, but i wouldn't want to gamble on it.