[Q&A] [KERNEL] Furnace-1.0.0 for Moto G (2nd Gen) [STOCK][10/28/2014][RGB][SoundCont
Q&A for [KERNEL] Furnace-1.0.0 for Moto G (2nd Gen) [STOCK][10/28/2014][RGB][SoundControl]
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 [KERNEL] Furnace-1.0.0 for Moto G (2nd Gen) [STOCK][10/28/2014][RGB][SoundControl]. 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!
Compatible with xt1069? How to instal instrutions?
Lighting fast when turned off xposed and switch to art!
Sent from my XT1068 using XDA Free mobile app
ty, looks great.
Quick question: To back up the stock kernel i have to backup boot.img through adb? Or it isn't necessary because we can extract it from stock firmware?
TY
Will it work on the XT1068?
Installed, had issue with touch screen being 5mm low, eg had to touch above, but a second reboot and it seems stable.
Antutu of 16528 rather than the 18 shown
Sent from my XT1068 using XDA Free mobile app
Can i use kernel tweaker app from playstore and try adding double tap to wake option?
prateek.khurana31 said:
Can i use kernel tweaker app from playstore and try adding double tap to wake option?
Click to expand...
Click to collapse
Nope you can't
SAVOCA, There is a possibility to add the function to light with 2 clicks? Thank you
It look very nice
I you made a great app called Furnace app is official I got the pro version. Thank you for the great app
First time posting, ehehe
Hello, I'm looking forward to buy a Moto G 2014, because my HTC Sensation XL died. But I just can't use stock ROM anymore, even if it's clean android.
I'm going to port CM11 M12 when I buy this phone. Can I use your kernel? I know that's open-source, but you have done a great job
Kernel its Compatible with Android 5.0.1 (Lollipop)?
Hy, i have the moto G 2014 and reciently upgrado to Android Lollipop (5.0.1), my question its ¿this kernel its compatible with this android?
Lollipop/Double Tap
Hi, congratulations on the job!
Waiting in the future is compatible with Lollipop and above all, having double tap !!!
Thanks for sharing savoca.
Since so many people are interested in Motorola's system ,I decided to ask help here to get a flashable .zip of the system .
Here is the link to the system files https://docs.google.com/file/d/0By2Nq4_gBuTQYUhmSXlBMDZPZFE/edit?usp=docslist_api
We only need an updater-script to get these files flashed .
I hope someone helps us to make this possible
In short terms :
We have access to the Motorola's Moto X Pro system dump .And since it is way more advanced in features ,we want to "PORT" it to our Nexus 6 since both devices share identical Hardwares .What we have is the whole System Dump ,system files ,boot.img even bootloader ,but we need to make the ROM flash-able for our device ,(since I personally don't feel safe flashing a factory image which is actually made for another device ,let it be same or identical ,it's still not safe ), so to make it flash-able we need update-script , which I have no enough knowledge to make one. So if someone can help us, it'd be great
If needed ,here is the Factory Image of the Moto X Pro :
https://docs.google.com/file/d/0By2Nq4_gBuTQMzh6OVNhUTdpVms/edit?usp=docslist_api
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nexus 6 Specifications
___________________
Moto X Pro Specifications
Edit : The Moto X Pro's codename is also Shamu ,as Nexus 6 ,just a "_retcn" added to the end . Shamu_retcn ,Shamu-Nexus 6 , ret-Retail , cn-China (not sure what ret means , but the only explanation I can give is retail)
Is there not a moto x pro forum m
rootSU said:
Is there not a moto x pro forum m
Click to expand...
Click to collapse
Dunno ,but what if there was .We want to make this ROM install-able on Nexus 6 ,not on Moto X Pro .
blinqipa said:
Dunno ,but what if there was .We want to make this ROM install-able on Nexus 6 ,not on Moto X Pro .
Click to expand...
Click to collapse
Perhaps then, you could make that more clear in your first post.
Oh and has anyone actually proven it will run without bricking an n6 yet? It has slightly different hardware so its a brave man who flashes untested
rootSU said:
Perhaps then, you could make that more clear in your first post.
Oh and has anyone actually proven it will run without bricking an n6 yet? It has slightly different hardware so its a brave man who flashes untested
Click to expand...
Click to collapse
From what we know ,both devices share "IDENTICAL ,COMPLETELY IDENTICAL" (sorry for caps) hardwares ,besides moto x pro has one thing extra which is I think IR sensor .That's why we want to make it flash-able ,so we can test it .Either way we have access to the factory image ,we could flash it all away ,but no one feels safe .
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
blinqipa said:
Since so many people are interested in Motorola's system ,I decided to ask help here to get a flashable .zip of the system .
Here is the link to the system files https://docs.google.com/file/d/0By2Nq4_gBuTQYUhmSXlBMDZPZFE/edit?usp=docslist_api
We only need an updater-script to get these files flashed .
I hope someone helps us to make this possible
In short terms :
We have access to the Motorola's Moto X Pro system dump .And since it is way more advanced in features ,we want to "PORT" it to our Nexus 6 since both devices share identical Hardwares .What we have is the whole System Dump ,system files ,boot.img even bootloader ,but we need to make the ROM flash-able for our device ,(since I personally don't feel safe flashing a factory image which is actually made for another device ,let it be same or identical ,it's still not safe ), so to make it flash-able we need update-script , which I have no enough knowledge to make one. So if someone can help us, it'd be great
If needed ,here is the Factory Image of the Moto X Pro :
https://docs.google.com/file/d/0By2Nq4_gBuTQMzh6OVNhUTdpVms/edit?usp=docslist_api
Click to expand...
Click to collapse
Working on this now.
I can't verify anything will work, and will need a tester tomorrow.
Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
It's not that I want the IR sensor ,I want the whole system because it has great useful features.Between thank you so much ,will try to make a flashable zip with dsixda's kitches asap .
Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
ALL the Motorola proprietary apps (Moto Assist, Moto Voice, Moto Actions, etc.) are supposed to be on the Moto X Pro, and there are many Nexus 6 owners who really want these apps to make the N6 the whole package.
We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.
KnifeSkills said:
We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.
Click to expand...
Click to collapse
Or ,another great thing ,is to make a flashable .zip of whole System .I know this is just too much of flashing ,but it's safer and it's way easier to replace .Then if it works ,we can make a flashable .zip of only NEEDED files ,libraries ,bin files etc.
KnifeSkills said:
We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.
Click to expand...
Click to collapse
We need to deodex first , but I keep getting errors ..
---------- Post added at 06:15 AM ---------- Previous post was at 06:13 AM ----------
Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
I've made a flashable zip and flashed it but I keep getting symlink errors really want just flash via mfastboot but afraid of bricking on the process
Omar1c said:
We need to deodex first , but I keep getting errors ..
---------- Post added at 06:15 AM ---------- Previous post was at 06:13 AM ----------
I've made a flashable zip and flashed it but I keep getting symlink errors really want just flash via mfastboot but afraid of bricking on the process
Click to expand...
Click to collapse
All I can say ,the bootloader flashing can result in a "soft brick" which renders the phone unusable ,and it directly gives you QHUSB BULK mode .That's caused by bootloader downgrading from new (5.1) to the old one (5.0.2) .
blinqipa said:
All I can say ,the bootloader flashing can result in a "soft brick" which renders the phone unusable ,and it directly gives you QHUSB BULK mode .That's caused by bootloader downgrading from new (5.1) to the old one (5.0.2) .
Click to expand...
Click to collapse
"There's an app for that" > http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
cam30era said:
"There's an app for that" > http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
App? Perhaps you mean , guide to fix .But why put yourself on a "recoverable situation" which is much of hard to fix for non-advanced users .
blinqipa said:
App? Perhaps you mean , guide to fix .
Click to expand...
Click to collapse
Yes, it was meant as a joke...
cam30era said:
Yes, it was meant as a joke...
Click to expand...
Click to collapse
LOL ,my sense of humor sometimes fails to the ground XD .Enough out of topic discussion XD have you tried getting a working .zip ? Or has anyone tried that? Seems like dsixda's kitchen has been abandoned as of 2013 (I guess) ,and since I've seen posts that it does not work for KK ,it would literally not work on Lollipop either :/
blinqipa said:
LOL ,my sense of humor sometimes fails to the ground XD .Enough out of topic discussion XD have you tried getting a working .zip ? Or has anyone tried that? Seems like dsixda's kitchen has been abandoned as of 2013 (I guess) ,and since I've seen posts that it does not work for KK ,it would literally not work on Lollipop either :/
Click to expand...
Click to collapse
No, I've not. Doing that is way out of my league. I want to thank you for all of your efforts, though. :good:
Though guys if you want a more active community on Nexus 6 and Moto X Pro head over here http://bbs.ihei5.com/forum-234-1.html , though it is on chinese , I almost understand nothing , but just translate the page into English .
just so that you all know, the moto x pro and nexus 6 are similar hardware wise, they are not the same and do differ, and would probably brick your nexus 6 if you actually flashed it onto your n6.