Any reson why there is no fm radio on moto e4 custom roms?
theportal2 said:
Any reson why there is no fm radio on moto e4 custom roms?
Click to expand...
Click to collapse
Any reason? Alot of work has to be done to make fm radio work on custom roms. You're welcome to do it if you want. Others have done the hard work, creating the device tree (squid) and compiling all of those wonderful ROMs (fireball, nyandeka, etc.). Go check seanstar's work on the plus model and see what he did to get it, then jump on in bro.
So no, no reason at all. Maybe they just forgot to.
Thanks for the reply, it is an over site indeed. I will be looking at all his posts to fix the fix.
It can be done, it's just gonna take much work. It may even involve modifying the device tree. I was kidding when I said they forgot. They were building the roms from source using squid's tree. The FM radio stuff wasn't included in the sources or device tree.
Oh thanks for letting me know.
Sent seanstar a pm asking for the FM radio files, if i get the files then I could make universal flashable zip to add FM radio, if that is all that is needed.
Related
I the last couple of days, i installed about 15 ROMs, to check what ROM best fits my needs, i haven't found the right ROM yet, but i want to install one of the 15 ROMs COMPLETELY CLEAN... i love when i install something, and it's clean! i hope you understand what i'm saying
I have an idea
and you are not alone
woow, i am not that opsessive xD
can i somehow "unpack" custom ROM and change just a little pieces ?
i have found really good roms but some little things are missing...
and, what's radio? i see on your signature that u have 1.16.25.48
mine is 1.06.25.29 what's the difference, and what is radio?
milancex said:
woow, i am not that opsessive xD
can i somehow "unpack" custom ROM and change just a little pieces ?
i have found really good roms but some little things are missing...
and, what's radio? i see on your signature that u have 1.16.25.48
mine is 1.06.25.29 what's the difference, and what is radio?
Click to expand...
Click to collapse
so there is still room for "improvement"
with a kitchen possibly (though I never cooked myself), but I expect chefs might have an opinion on that, so asking before would show the proper respect for their work
radio in wiki
radio faq
X1 tutorials/library
radio collection
Best, DK
Draken Korin said:
so there is still room for "improvement"
with a kitchen possibly (though I never cooked myself), but I expect chefs might have an opinion on that, so asking before would show the proper respect for their work
radio in wiki
radio faq
X1 tutorials/library
radio collection
Best, DK
Click to expand...
Click to collapse
Okay, thank you
Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
@VictoriousShooter
@rr46000
@S0bes
@yajnab
I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)
@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.
for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?
For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.
Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Nice! What's the status of your efforts?
How to the testing .....
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
F0L said:
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
Click to expand...
Click to collapse
Ok, should have read it better. Are you able to just compile a kernel for testing. Once you have a working one, that would be a good base for updating rom.
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
Any update on this?
Guess this is not going to happen. Just wish I still had the time I used to. I would have had a go my self, as the vanilla kernel is what kills this cool bit of kit.
I managed to get it to a usable state with google play installed, by installing SkyNET. Which tweaks the system on the fly when needed. Helps keep as much memory as possible.
Would the kernel source of the Nokia X help? as it uses the exact same hardware.
I have it downloaded, so if it will help, I can link.
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
F0L said:
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
Click to expand...
Click to collapse
Can you post how you did it? Thanks
@fol I would also be interested in it.
killervette said:
Can you post how you did it? Thanks
Click to expand...
Click to collapse
I used rom kichen to mess with ramdisk (it was very risky as messing with boot image can brick pine). I manually added init.d support. Then repacked it. Luckly it worked fine. I even flashed it to my sons.
I extracted stock system.zip and tweaked it the way I wanted (debloated added apps I owned), then flashed that. As I added init.d, I could use scripts on boot to alter running of pine.
Im currently using Project skynet vr4, which runs very nice.
@fol What is skynet? Do you have a link?
So I searched the whole rom recoveries kernel section, did not see any base roms. If there isn't, where to info about pulling system to make one? Trying to get a custom OOS rom going as AOSP can suck it lol. Original software is always more stable IMO
icedventimocha said:
So I searched the whole rom recoveries kernel section, did not see any base roms. If there isn't, where to info about pulling system to make one? Trying to get a custom OOS rom going as AOSP can suck it lol. Original software is always more stable IMO
Click to expand...
Click to collapse
What is a base ROM for you?
Normally pure AOSP is considered as the reference as it's Google code without modification. But people don't like pure AOSP because it's lacking many features people are used to. So even AOSP labeled ROM have some non AOSP add-ons.
If you want a 'pure' AOSP ROM you'll have to compile it.
Striatum_bdr said:
What is a base ROM for you?
Normally pure AOSP is considered as the reference as it's Google code without modification. But people don't like pure AOSP because it's lacking many features people are used to. So even AOSP labeled ROM have some non AOSP add-ons.
If you want a 'pure' AOSP ROM you'll have to compile it.
Click to expand...
Click to collapse
Back in the days someone usually created an optimized stock Rom for different devices based off the OEMs software so that others could flash it or use it as a base for custom ROMs based off of stock.
I believe that's what he is referencing if I am not mistaken.
icedventimocha said:
So I searched the whole rom recoveries kernel section, did not see any base roms. If there isn't, where to info about pulling system to make one? Trying to get a custom OOS rom going as AOSP can suck it lol. Original software is always more stable IMO
Click to expand...
Click to collapse
There is no base ROM for the OnePlus 6T. Its so AOSP like almost everything is done from source. I thought about posting a base ROM, as that is what I used to primarily use (and usually posted). I wasnt much into Source.
Another cool thing some devs due are make mods that can be flashed in magisk, and so long as you have the stock oos you can enjoy there version of stock oos with whatever tweaks they have done to it such as custom settings apps, etc.
Milly7 said:
Back in the days someone usually created an optimized stock Rom for different devices based off the OEMs software so that others could flash it or use it as a base for custom ROMs based off of stock.
I believe that's what he is referencing if I am not mistaken.
Click to expand...
Click to collapse
You are 100% correct
Scott said:
There is no base ROM for the OnePlus 6T. Its so AOSP like almost everything is done from source. I thought about posting a base ROM, as that is what I used to primarily use (and usually posted). I wasnt much into Source.
Another cool thing some devs due are make mods that can be flashed in magisk, and so long as you have the stock oos you can enjoy there version of stock oos with whatever tweaks they have done to it such as custom settings apps, etc.
Click to expand...
Click to collapse
Nailed Scott as usual. This device and how android handles files is extremely different than other phones we've both worked on as well (pretty sure that's android specific) I'm gonna have to look into the magisk thing. Never did the from source thing so that might be over my head. Don't have Linux set up on my machine either so a lot of time would have to go into just getting a stock flashable to work with.
I want to get some of the mods and themes I always post for this phone, but this might be a hurtle as I usually got a base to run with. I always try to show some love and since developers are jumping ship (because the money's not there, let's not lie and say that isn't what it's about) I know my work would be appreciated
icedventimocha said:
You are 100% correct
Nailed Scott as usual. This device and how android handles files is extremely different than other phones we've both worked on as well (pretty sure that's android specific) I'm gonna have to look into the magisk thing. Never did the from source thing so that might be over my head. Don't have Linux set up on my machine either so a lot of time would have to go into just getting a stock flashable to work with.
I want to get some of the mods and themes I always post for this phone, but this might be a hurtle as I usually got a base to run with. I always try to show some love and since developers are jumping ship (because the money's not there, let's not lie and say that isn't what it's about) I know my work would be appreciated
Click to expand...
Click to collapse
The magisk modules are a great way to go because its reversible as well. Not sure if you knew that. You can uninstall these MagiskROM's just as easy as installing.
Scott said:
The magisk modules are a great way to go because its reversible as well. Not sure if you knew that. You can uninstall these MagiskROM's just as easy as installing.
Click to expand...
Click to collapse
I did, but think I'm just gonna make a flashable over stock package, too much catching up to do so gonna stick to what I know
Anybody knows if there is a 6er update for the LTE Qualcomm Version?
Maybe for a similar build, Tornado Fly?
cheers
As I see your device has Snapdragon 410, I can try to port a Custom ROM or a Custom recovery if you want
processor info in "about device" says Qualcomm MSM8916
current build is BLU_V0010UU_V13_Generic with android 5.0.2
Kernel 3.10.49
That's nice. Is your device rooted?
Do you have any experience in flashing custom roms/custom recoveries?
i did root it, dont know which method i used,
tried to put on a trwp, but didnt find a version that worked as i recall..
so how would it work, do you have a FW for the phone?
schlunk said:
i did root it, dont know which method i used,
tried to put on a trwp, but didnt find a version that worked as i recall..
so how would it work, do you have a FW for the phone?
Click to expand...
Click to collapse
I probably will port TWRP from a similar device that has MSM8916.
And no, I don't have the firmware (i'll research soon) neither the phone.
oh, ok. but twrp without a matching 6er rom wouldnt help me much
but thanks for trying to help!
schlunk said:
oh, ok. but twrp without a matching 6er rom wouldnt help me much
but thanks for trying to help!
Click to expand...
Click to collapse
it's okay. after TWRP, I can try to port an android 6 based ROM
does this make sense if you dont have the phone to test it on??
should be pretty buggy with lots of stuff not working, i guess, like with all other custom roms?
schlunk said:
does this make sense if you dont have the phone to test it on??
Click to expand...
Click to collapse
not really, but I do everything if you want a custom rom haha
schlunk said:
should be pretty buggy with lots of stuff not working, i guess, like with all other custom roms?
Click to expand...
Click to collapse
as for msm8916 it shouldn't have much bugs
im not an expert, but all custom roms have issues? like different stuff not working, camera, lte, blutooth etc..
hard to believe if you take like lineage or something and porting it on a specific phone, everything will work ??
thank for trying to help, but i dont really have time for testing. if youre saying everything will work out of the box, i will gladly take it
schlunk said:
im not an expert, but all custom roms have issues? like different stuff not working, camera, lte, blutooth etc..
hard to believe if you take like lineage or something and porting it on a specific phone, everything will work ??
thank for trying to help, but i dont really have time for testing. if youre saying everything will work out of the box, i will gladly take it
Click to expand...
Click to collapse
yeah, all custom roms have issues, but it's pretty easy to fix on msm8916 chipsets. there are a lot of guides where you can fix these bugs