Q&A for (news) Xiaomi Released Kernel Source for Mi 4i
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for (news) Xiaomi Released Kernel Source for Mi 4i. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
custom rom
when is the custom rom coming out? please bring it out soon..
somnath390 said:
when is the custom rom coming out? please bring it out soon..
Click to expand...
Click to collapse
Comming... . soooon.......
nice to see some development has going on!
I'm maman_ on the xiaomi forums, and I'm planning to compile aosp 5.1.1 or 5.0.2 for the Mi 4i. Any help will be very appreciated
currently I had downloaded the android sources, and cloning the kernel source to the `devices` folder. If I'm not wrong, the next step is constructing the device tree for mi4i. any pointers?
also seems that xda user dh.harald has been succesfully integrate the wifi drivers into the kernel, which is a good news.
also new thread in the development thread will be good too
Waiting fo relase its will be awesome
thanks for u r work
Thanks
Thanks for giving ur time highly obliged
CM
Now that a few people are trying to port CM to the Mi4i, I wonder what it takes that it will be officially "supported" by CM?
can i request for official support form custom recoveries like TWRP 1st instead of jumping to custom rom development??
wolkenjaeger said:
Now that a few people are trying to port CM to the Mi4i, I wonder what it takes that it will be officially "supported" by CM?
Click to expand...
Click to collapse
i dont think cm will officially support this device so sson...we need to fix everything to get official support.
k2wl said:
i dont think cm will officially support this device so sson...we need to fix everything to get official support.
Click to expand...
Click to collapse
I understand, but if everything works, how is the process to have it officially supported?
Related
Q&A for Lollipop - OPO - Pure Aosp 5.0 - Test Build only -16/11/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop - OPO - Pure Aosp 5.0 - Test Build only -16/11/14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Bugs
navendugoyal said:
This is a pure AOSP 5.0 - Lollipop - build compiled from source .
I would highly recommend it to be used only by developers and advanced users.
The build just completed and am uploading the image files for you to do whatever you please.
The idea is to get it out there so others can take a look and use it to make it better.
Please give your comments and updates if you do plan to use it on your device.
ADVISORY -
First build -likely to be highly unstable.
I am not responsible for any damages caused whatsoever.
This is for test purposes only, however it should work well.
I am out of town for next 24 hrs.. therefore can't provide too much hours into it as of now. Will await all of your responses.
images uploading - Links soon..
Regards
Click to expand...
Click to collapse
Will the bugs be of the current CM12 Lollipop that we are facing or you have rectifed some of the issues? Thanks for upcoming build btw. It would be great if you could provide us with the link to the gapps thatworks with this rom best and a little intructions on how to flash it for noobs friendly if they choose to proceed with the flashing of this dev rom.
Awesome! Thank you.
Q&A for Is CM12 buildable?
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Is CM12 buildable?. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Cm 12
Magamo said:
The short answer is 'yes', but there's some pretty big caveats.
The bare CM12 trees for apexqtmo are rather broken, and even TeamApexQ's repos currently audio is broken, but it does build. CM12.1, the answer is currently 'no'.
Click to expand...
Click to collapse
Hi ...
I have months hoping for the update of cyanogenmod 12 for samsung galaxy s relay.
There will be no official update from cyanogenmod 12 for samsung galaxy s relay ?? or are working on developing this rom?
We'll stay alone with 11 cm?
Thanks and sorry for my English, but I had to translate my Spanish through a translator hehehehe ...
quintero8 said:
Hi ...
I have months hoping for the update of cyanogenmod 12 for samsung galaxy s relay.
There will be no official update from cyanogenmod 12 for samsung galaxy s relay ?? or are working on developing this rom?
We'll stay alone with 11 cm?
Thanks and sorry for my English, but I had to translate my Spanish through a translator hehehehe ...
Click to expand...
Click to collapse
As far as I know, there is currently no official CM support for the Relay starting with 12.0. TeamApexQ has made a release of Lollipop (Android 5.0.2) based on CM 12.0 (Our unofficial builds are referred to as 'FatToad') for the relay, there is no official CM support a this time. I believe another group has done a 5.0.2 release (Validus) which is official for their image.
Magamo said:
As far as I know, there is currently no official CM support for the Relay starting with 12.0. TeamApexQ has made a release of Lollipop (Android 5.0.2) based on CM 12.0 (Our unofficial builds are referred to as 'FatToad') for the relay, there is no official CM support a this time. I believe another group has done a 5.0.2 release (Validus) which is official for their image.
Click to expand...
Click to collapse
Thank you very much for answering ...
Then it means that Validus is being updated to improve it?
Saludos... :good:
Those roms aren't updated for a while.
Q&A for [ROM] Huawei Honor6 MIUI6 Release [Update 5.5.17]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Huawei Honor6 MIUI6 Release [Update 5.5.17]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tabo8226 said:
ON h60-l04 it will work on B390?
So I need to flash B390 and then this patch yes?
OR i can just install this and that's all? ^^
Click to expand...
Click to collapse
nicholadia said:
No H60-L12 based on EmotionUI 3.0? Please let me know for me to try this ROM....thanks so much.
Click to expand...
Click to collapse
yes, you must go on B390 and then flash this rom!
it is most beautiful rom :fingers-crossed:
Can this be installed on b380? Also screen saver feature present?
Sent from my H60-L04
How do I get the play store working?
edit: flashing gapps helped
Modem of H60-L04
Good day!I have the same problem with the firmware (tried all versions), always error com.android.phone !!! The modem version of the same...
obninsk said:
Good day!I have the same problem with the firmware (tried all versions), always error com.android.phone !!! The modem version of the same...
Click to expand...
Click to collapse
Same problem: baseband 21.223.00.00.031
Hi,
I can't install any apk, from the google play neither, it says that I have no abaliable space when I have 12 gb free.
Can anyone solve this problem? thanks, im using Cm11 version on L02.
Sorry for my bad english.
MIUI 6 for Huawei Honor 6 Author: Ry09iu
I want to ask about problem com.android.phone. Because this is really very interesting bug. I want to know if it is carrier problem, then why I didn't meet this problem on some MIUI firmwares for H60-L02 ?? Like Miui 5.4.3 and Miui 5.6.13 ? But many users from 4pda tell that there is no MIUI version based on official firmware which haven't this problem. I will very happy if Ry09iu can correct this trouble. We can take a log for help. Thank you very much Ry09iu for this great work!
Q&A for [ROM]Pico KK4.4.4 FIUI ROM 2.22
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]Pico KK4.4.4 FIUI ROM 2.22. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Trickster22 said:
Hey I ported this rom to Samsung Galaxy Ace i ( s5830i ), it is armv6 device but luckily rom booted up but browser and wifi are not working and statusbar is always white and icons in settings app are wierd too. Help me
Click to expand...
Click to collapse
hi~ Im nic，from FIUI team.
and i saw your E-mail, and I will try to help u to fix something.
statusbar always strange， maybe u can try to write "fiui.argb.oder=1" in build.prop
Code:
fiui.argb.oder=1
cuz some old devices's RGB is different of new devices. so we tried to fix it. but i dont know is it work on ur devices. just try.
_Nic said:
hi~ Im nic，from FIUI team.
and i saw your E-mail, and I will try to help u to fix something.
statusbar always strange， maybe u can try to write "fiui.argb.oder=1" in build.prop
Code:
fiui.argb.oder=1
cuz some old devices's RGB is different of new devices. so we tried to fix it. but i dont know is it work on ur devices. just try.
Click to expand...
Click to collapse
Thank you for reply sir. I will try this solution for statusbar but what about browser and wifi. Do I need to copy some specific libraries from port rom to make them work? And in Settings app Icons are weird too
i couldn't find a similar thread or question asked about this. Does anyone know the ETA of marshmallow's availability (CM13 maybe) ?
You can search the development and original development sections. Below is a Marshmallow ROM. AOSParadox team is also working on one.
http://forum.xda-developers.com/one...nt/experimental-homemade-android-6-0-t3225725
It is pretty much AOSP though.
transvin said:
i couldn't find a similar thread or question asked about this. Does anyone know the ETA of marshmallow's availability (CM13 maybe) ?
Click to expand...
Click to collapse
It's generally never advised to ask for ETAs hence why you don't see threads like yours. Just wait patiently for the devs to bring up the source and implement features. If you're in a hurry learn to code and do it yourself
NB: I pressed thanx by mistake.
Renosh said:
It's generally never advised to ask for ETAs hence why you don't see threads like yours. Just wait patiently for the devs to bring up the source and implement features. If you're in a hurry learn to code and do it yourself
Click to expand...
Click to collapse
This^. Marshmallow will be here when it gets here. Until then.............
Thread closed