Related
This is a project I started to work on an AOSP ROM for our Grand 2.
When it gets to boot successfully, I'll make a DevDB thread for it.
The Grand 2 and the Moto G share the same chipset, the Sanpdragon 400. I'm downloading it and applying a few patches to see if it works.
I'll upload my success/failure here.
This is also a request for devs to help.
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
shabbypenguin said:
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
Click to expand...
Click to collapse
I'm going to try it if my Moto G ROM port fails. But don't these devices have totally different CPUs? The only other Samsungs with this chip are the Tab 4 variants (a ported Tab 4 ROM won't work) and the S3 Neo+, which doesn't have any custom ROM.
shabbypenguin said:
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
Click to expand...
Click to collapse
I'm going to try it if my Moto G ROM port fails. But don't these devices have totally different CPUs? The only other Samsungs with this chip are the Tab 4 variants (a ported Tab 4 ROM won't work) and the S3 Neo+, which doesn't have any custom ROM.
As you are a developer, can you help me if I use a CM ROM from the devices you mentioned? The patch applied only works for ROMs for the same CPU type. I don't think it will work in this case. And does a TouchWiz kernel work over an AOSP/CM ROM.
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
shabbypenguin said:
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
Click to expand...
Click to collapse
Okay. I'm trying the Mega 6.3's CM ROM, as the Mega is the closest Samsung phone to the Grand 2. Thanks.
shabbypenguin said:
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
Click to expand...
Click to collapse
Moto G ROM failed to boot. Though it passed the GALAXY GRAND 2 SM-G7102 thing at boot, it gives a flash of light and reboots the phone. Probably a result of using a TouchWiz kernel?
Failure will be uploaded later today.
My patch was about copying files from a Grand 2 ROM (TouchWiz used) to the new ROM.
IT FAILED. Trying on the Mega 6.3's CM build.
WaseemAlkurdi said:
Moto G ROM failed to boot. Though it passed the GALAXY GRAND 2 SM-G7102 thing at boot, it gives a flash of light and reboots the phone. Probably a result of using a TouchWiz kernel?
Failure will be uploaded later today.
My patch was about copying files from a Grand 2 ROM (TouchWiz used) to the new ROM.
IT FAILED. Trying on the Mega 6.3's CM build.
Click to expand...
Click to collapse
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
wat about miui??
shabbypenguin said:
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
Click to expand...
Click to collapse
Which I didn't ever understand. Can you help me?
Do you take the device tree thing as a file?
Is building CM from that harder than building a computer program using VB.NET, or harder?
Can you help me cuz I never built a ROM that way.
If it needs Linux, then I got it (32-bit Ubuntu and x86_64 Fedora), though Windows is better.
And thanks for patience with my dumb questions
shabbypenguin said:
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
I found this thing. Can you help me by translating this to human-understandable form? Could you just carry out the steps and I'll test and do virtually everything you need to do as if you had the device in your two bare hands?
Or can you just give me instructions and I'll execute?
No.
building Cm is fairly straight forward if your device is officially supported, this device doesnt have anything. someone needs to download the source code for CM, grab my devices trees and add in all the missing info by studying the stock rom and comparing it to similar device. this can take anywhere from days to months, and even then some devices end up with stuff that is forever broken.
shabbypenguin said:
No.
building Cm is fairly straight forward if your device is officially supported, this device doesnt have anything. someone needs to download the source code for CM, grab my devices trees and add in all the missing info by studying the stock rom and comparing it to similar device. this can take anywhere from days to months, and even then some devices end up with stuff that is forever broken.
Click to expand...
Click to collapse
Thanks a lot.
So it needs a really experienced developer, whereas I am a Grade 10 student at school who knows no android programming. Sorry for wasting your precious time. But do you anyone who's willing to do it? I have school, and my parents do not let me give up schoolwork to porting a ROM.
Sorry but there isnt a bunch of peopel out there waiting for new phones to port CM to, how it works is someone with the phone ports cm and once it is considered good enough is submitted to be made official through their gerrit. then they have to become the maintainer of it and any code changes, updates etc have to be handled. its a lot of work. it doesnt need to be experienced, just a matter of fast learning as well as having a background in java/c really helps.
shabbypenguin said:
Sorry but there isnt a bunch of peopel out there waiting for new phones to port CM to, how it works is someone with the phone ports cm and once it is considered good enough is submitted to be made official through their gerrit. then they have to become the maintainer of it and any code changes, updates etc have to be handled. its a lot of work. it doesnt need to be experienced, just a matter of fast learning as well as having a background in java/c really helps.
Click to expand...
Click to collapse
Thanks. Do you have the a link to the vendor trees? I'll try to check them. But tell me how to compare them and where is the missing info to add. I'll do it. Fast learning is done while you tell me to compare. So, it's me downloading the device and vendor trees, then what? Your turn.
P.S. 1. Stuff that's forever broken came to happen with the Galaxy Star. It has a CM ROM, which boots, but has no audio, no ril, no camera, and broken menu/back keys.
2. Are you American? I was born there too! Nice coincidence!
BTW, which state are you from? I'm from Illinois.
In AOSP, SystemUI and Build.prop require the main effort. If they are ready, you pretty near?
Sent from my SM-G7102 using XDA Premium 4 mobile app
keshavt said:
In AOSP, SystemUI and Build.prop require the main effort. If they are ready, you pretty near?
Sent from my SM-G7102 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not exactly. There's a lot of work to be done on ril, camera, Wi-Fi, and other hardware drivers, in addition to the kernel. I'm thinking about borrowing some files from the ill-fated CM build.
WaseemAlkurdi said:
Not exactly. There's a lot of work to be done on ril, camera, Wi-Fi, and other hardware drivers, in addition to the kernel. I'm thinking about borrowing some files from the ill-fated CM build.
Click to expand...
Click to collapse
What happened brother any progress
Sent from my SM-G900I using XDA Premium 4 mobile app
techmate98 said:
What happened brother any progress
Sent from my SM-G900I using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have paused development because, when I asked him for a couple of files from his failed CM build, mukulsoni told me to wait a little because he was nearly done with his CM11 build.
WaseemAlkurdi said:
Have paused development because, when I asked him for a couple of files from his failed CM build, mukulsoni told me to wait a little because he was nearly done with his CM11 build.
Click to expand...
Click to collapse
great!!! so is his build working now
I don't want to be missunderstood.
I do recognize all the work from our developers, altough they are only few... Unfortunately i only know how to port roms..
so can anyone of you guys give a shot to create a lollipop build ?
danilo96 said:
I don't want to be missunderstood.
I do recognize all the work from our developers, altough they are only few... Unfortunately i only know how to port roms..
so can anyone of you guys give a shot to create a lollipop build ?
Click to expand...
Click to collapse
We dont even have CM11
Flamestorm said:
We dont even have CM11
Click to expand...
Click to collapse
We have 3 daily drivers right now, Crystal is the best so far because of the camera, but still, we have 3 cm11 builds
Is cm12 out? I think making 4.4.4 builds is easier becouse we have sources from lg. Dont know about 5.0 with kernels and drivers and all must be harder for our device at this point.
invaderjohn said:
Is cm12 out? I think making 4.4.4 builds is easier becouse we have sources from lg. Dont know about 5.0 with kernels and drivers and all must be harder for our device at this point.
Click to expand...
Click to collapse
I'm not sure about it, but i saw a unoficiall build for htc explorer so i think yes
danilo96 said:
I'm not sure about it, but i saw a unoficiall build for htc explorer so i think yes
Click to expand...
Click to collapse
Cm12 isnt out yet, theres "cm12" based on clean aosp compiled with cm sources
Its unofficial build so cm team has nothing with it
It might be unstable and isnt for daily usage
Cm Has announced that cm12 will come next month
But the best way is to pray for official 5.0 because updated kernel might fix problems we have right now
sebatox said:
Cm12 isnt out yet, theres "cm12" based on clean aosp compiled with cm sources
Its unofficial build so cm team has nothing with it
It might be unstable and isnt for daily usage
Cm Has announced that cm12 will come next month
But the best way is to pray for official 5.0 because updated kernel might fix problems we have right now
Click to expand...
Click to collapse
Well, thanks , I didn't knew about that
let's wait and hope then :crying:
Looking for some rom for the D618 version (
LG L90 got AOSP 5.0 Lolipop whether someone can from LG L90 to port lolipop 5.0? Why do you always take a phone that has little support Developer
Hello all great devs o XDA Forum
I just have a very humble request...
Would anyone o you please take some time and
Build android lollipop ROM for mediatek mt6592 based devices??
There are so many devices in market with this chip but I couldn't
Find one single Lollipop ROM for this device.
Please guys...
Somebody do it...
I can agree on that. There is recently a lollipop for MTK6582 (from Doogee), so it should not be that hard to port it for MTK6592(T).
I think that Doogee will release soon lollipop ROM for DG550, which is MTK6592 powered phone.
Maor545 said:
I can agree on that. There is recently a lollipop for MTK6582 (from Doogee), so it should not be that hard to port it for MTK6592(T).
I think that Doogee will release soon lollipop ROM for DG550, which is MTK6592 powered phone.
Click to expand...
Click to collapse
Not possibly...
As far as I guess
Its a problem from mediatek (manufacturer o mt6592 chip)...
Until they provide rom... Lollipop will not be "officially" available for mt6592...
That's why i am hoping for some genius dev from XDA to do the magic and build a custom lollipop rom....
Any devs listening?????
Sent from my irisX8 using XDA Free mobile app
SaMi2233 said:
Not possibly...
As far as I guess
Its a problem from mediatek (manufacturer o mt6592 chip)...
Until they provide rom... Lollipop will not be "officially" available for mt6592...
That's why i am hoping for some genius dev from XDA to do the magic and build a custom lollipop rom....
Any devs listening?????
Sent from my irisX8 using XDA Free mobile app
Click to expand...
Click to collapse
They can listen all they want but without the kernel source for the device it won't do any good. Even if someone got something booting it will be plagued with issues.
zelendel said:
They can listen all they want but without the kernel source for the device it won't do any good. Even if someone got something booting it will be plagued with issues.
Click to expand...
Click to collapse
The existing kitkat kernel won't work???
It says version 3.4.67 under settings
Sorry but I don't know much about linux/android kernel
Sent from my irisX8 using XDA Free mobile app
SaMi2233 said:
The existing kitkat kernel won't work???
It says version 3.4.67 under settings
Sorry but I don't know much about linux/android kernel
Sent from my irisX8 using XDA Free mobile app
Click to expand...
Click to collapse
Not really. There were huge changes to the default runtime for the entire os and some of the files that work with the kernel need to be updated as well. 5.0 was a major code change all around.
zelendel said:
Not really. There were huge changes to the default runtime for the entire os and some of the files that work with the kernel need to be updated as well. 5.0 was a major code change all around.
Click to expand...
Click to collapse
That sounds good and bad at the same time...
Good b'coz that brings lot of useful things to android
And bad coz ... Don't know how long we will have to wait for it....
Cry cry...
Sent from my irisX8 using XDA Free mobile app
SaMi2233 said:
Not possibly...
As far as I guess
Its a problem from mediatek (manufacturer o mt6592 chip)...
Until they provide rom... Lollipop will not be "officially" available for mt6592...
That's why i am hoping for some genius dev from XDA to do the magic and build a custom lollipop rom....
Any devs listening?????
Sent from my irisX8 using XDA Free mobile app
Click to expand...
Click to collapse
Don't guess. 6582 and 6592 is almost the same chip. It differs by number of cores. Devs made Cyanogenmod 10 for MTK, they will make CM12 too, just give them time
Maor545 said:
Don't guess. 6582 and 6592 is almost the same chip. It differs by number of cores. Devs made Cyanogenmod 10 for MTK, they will make CM12 too, just give them time
Click to expand...
Click to collapse
So if the MT6592 is equal to the MT6582, how can you carry a rom Mt6582 for Mt6592? Any tutorial teaching this kind of port?
The problem also is, that in the basic porting you use some files from your stock ROM. And these files are not compatible between KitKat and Lollipop. You cen try some more sofisticated port procedure, the risk of hard bricking should be small.
forum.xda-developers.com/android/development/rom-cyanogenmod-12-kingzone-k1-turbo-t3119908
Yuppp
That's right dude... Lollipop CM12.1 there on the above link....
U can find the instruction here:
http://forum.xda-developers.com/android/development/guideport-cm-12-1-mtk6592-cm-12-1-t3142499
I ended up with no simcard, but maybe you get it worked in your hh... gud luck
lg-h540
lg g4 stylo 3g (lg-h540) has mtk6592 and has lolipop 5.0.2 out of the box.
I've been looking but can't find anything official. What is the latest official android version for this device? I found this site that says this device got Lollipop Spring last year: http://htcsource.com/2015/01/leaked-document-reveals-htcs-lollipop-update-roadmap/
My device is still on 4.4.2 though even after running the latest RUU I could find.
noxarcana said:
I've been looking but can't find anything official. What is the latest official android version for this device? I found this site that says this device got Lollipop Spring last year: http://htcsource.com/2015/01/leaked-document-reveals-htcs-lollipop-update-roadmap/
My device is still on 4.4.2 though even after running the latest RUU I could find.
Click to expand...
Click to collapse
No updates on the desire 610. only custom roms the best atm is MiniBlu cm 11 and cm 12...
I was afraid of that.
Sent from my HTC Desire 610 using Tapatalk
noxarcana said:
I was afraid of that.
Sent from my HTC Desire 610 using Tapatalk
Click to expand...
Click to collapse
Am noob to flashing and dvice working fine. if u want to use the custom rom cm 12.1 is being tested and cm 11 is stable jus use windriod to unlock bootloader and load twrp and ur basically good to go
remeber backup before unlocking to save her data
Yea, I've used CM 11, but I'm not a huge fan of CM. A bit to bland for my tastes.
Sent from my HTC Desire 610 using Tapatalk
only other bet is stock or slim rom which have bootloop issues
Well, I'm using stock right now. I'll probably go with CM in the end so I can use viper4android.
Sent from my HTC Desire 610 using Tapatalk
noxarcana said:
Well, I'm using stock right now. I'll probably go with CM in the end so I can use viper4android.
Sent from my HTC Desire 610 using Tapatalk
Click to expand...
Click to collapse
CM is good getting support from miniblu and zihan for new roms
noxarcana said:
Yea, I've used CM 11, but I'm not a huge fan of CM. A bit to bland for my tastes.
Sent from my HTC Desire 610 using Tapatalk
Click to expand...
Click to collapse
Reserection Remix is coming as soon as cm12.1 hits stable.:good:
Question
MiniBlu said:
Reserection Remix is coming as soon as cm12.1 hits stable.:good:
Click to expand...
Click to collapse
Is the Reserection remix still in works or just CM 13?
DaGWaR said:
Is the Reserection remix still in works or just CM 13?
Click to expand...
Click to collapse
I have the sources synced but waiting till I find a fix for GPS
Sent from my Desire 610 using XDA-Developers mobile app
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
DaGWaR said:
Is the Reserection remix still in works or just CM 13?
Click to expand...
Click to collapse
Sources are synced but waiting to find a fix for GPS.
Hey guys,
do you think we will ever see AOSP Android 7.x Nougat ROMs for the LG G2, like CyanogenMod 14 for example?
Do you think Android 7 can properly run on the LG G2?
Regards
Yea, maybe after a month or two (After N comes out) we'll have a basic port, then a few months later a stable ROM, G2 can handle anything
wq0913562 said:
Hey guys,
do you think we will ever see AOSP Android 7.x Nougat ROMs for the LG G2, like CyanogenMod 14 for example?
Do you think Android 7 can properly run on the LG G2?
Regards
Click to expand...
Click to collapse
As long there are developers for lg g2, I think everything is possible.
BlissRom 7 will be CM14 so yeah we will get that in future time
YES YES, when full code drop and cyanogen start nighlys
Android 7.0 Nougat has been released:
https://www.android.com/versions/nougat-7-0/
Let's hope they release the AOSP source code soon.
Would be nice if the LG G2 would get AOSP 7.0 / CM 14.0.
Nougat looks really nice .
When CM14 arrives, I think g2 will receive it in a week
Well it does not matter to me, I rather have a bug free MM than N filled with bugs due to old g2 blobs
6 months into MM cm13 and we still have some bugs due g2 old kernel/drivers source....so
LG G2 SOC is deprecated in AOSP
ImSpecialNot said:
LG G2 SOC is deprecated in AOSP
Click to expand...
Click to collapse
I read that the Z3 won't get N cause SD 800/801 is not compatible with Vulkan API, so we gonna need it to be ported which might be a problem...
shaneel1491 said:
I read that the Z3 won't get N cause SD 800/801 is not compatible with Vulkan API, so we gonna need it to be ported which might be a problem...
Click to expand...
Click to collapse
not just that , but the SD 800 supporting library and code has been totally removed from AOSP source code , check this commit :
goo.gl/S8dwrw
ImSpecialNot said:
not just that , but the SD 800 supporting library and code has been totally removed from AOSP source code , check this commit :
goo.gl/S8dwrw
Click to expand...
Click to collapse
It doesn't mean g2 won't get cm14, It will arrive soon
wzedlare said:
It doesn't mean g2 won't get cm14, It will arrive soon
Click to expand...
Click to collapse
I really hope so, as I just bought 2 LG G2's
ImSpecialNot said:
not just that , but the SD 800 supporting library and code has been totally removed from AOSP source code , check this commit :
goo.gl/S8dwrw
Click to expand...
Click to collapse
Damn, I'm sure we'll get it though, even though the odds are against us :'')
Well, they just ported 7.0 to the Nexus 5
edit:
https://github.com/CyanogenMod/android_kernel_lge_msm8974/tree/cm-14.0
https://github.com/CyanogenMod/android_device_lge_g2-common/tree/cm-14.0
There
Pacer_456 said:
Well, they just ported 7.0 to the Nexus 5
Click to expand...
Click to collapse
And the G2 has the same hardware
Sent from my LG-D802 using XDA-Developers mobile app
Pacer_456 said:
Well, they just ported 7.0 to the Nexus 5
edit:
https://github.com/CyanogenMod/android_kernel_lge_msm8974/tree/cm-14.0
https://github.com/CyanogenMod/android_device_lge_g2-common/tree/cm-14.0
There
Click to expand...
Click to collapse
So we already have kernel and g2 common, only need device specific blobs now and some other few things?
According to here
http://en.yibada.com/articles/131110/20160612/android-marshmallow-lg-g-flex-2-g4-stylo-android-n.htm
there should be official Android N for the G2.
... or maybe it's a mistake?
santope said:
According to here
http://en.yibada.com/articles/131110/20160612/android-marshmallow-lg-g-flex-2-g4-stylo-android-n.htm
there should be official Android N for the G2.
... or maybe it's a mistake?
Click to expand...
Click to collapse
Very highly unlikey. Qualcomm has depreciated msm8974 and will not be providing updates for things like the Vulkan API, and I doubt LG will work on updating a 3-4 year old device that requires a ton of work.
santope said:
According to here
http://en.yibada.com/articles/131110/20160612/android-marshmallow-lg-g-flex-2-g4-stylo-android-n.htm
there should be official Android N for the G2.
... or maybe it's a mistake?
Click to expand...
Click to collapse
Clickbait article ignore anything that says lg g2 will get an official update.