Related
Hello!
Ok so this is an attempt to port MIUI to LGP500. We are trying this because porting on the Galaxy 3 (LDPI armv6) was a success and i'm sure it will work on our device too.
This is what we're using so far: MIUI for Desire & Overflow ROM
So far this has been done:
ADB now working
Merged framework.jar from base rom with MIUI one
Replaced all apks with miui except LatinIME.apk which seems to give an error on boot
Use libs, bin and xbin from base rom
Merged permissions
[Update 9.07.2011 - 17:48 GMT+3 DST]
Now using framework from CM7
Libs, and bins from CM7
Boot.img still from Overflow (CM7 Boot.img stops adb on boot after a while - so using Overflow for developing for now)
Replaced many smali files in framework but errors keep popping up - I think framework is pretty screwed up now and must be redone (again)
No more nasty error on boot (with stack dump and stuff...)
No need for logcat now because errors come from framework
[Update 11.07.2011 - 15:32 GMT+3 DST]
MIUI boots up and we have graphics BUT
It only boots up to some error dialogs that say some processes force closed with "Close" and "Report to MIUI"
Gapps, Provision, and StatusBar force close so they need work
Removed ContactsProvider.apk and CalendarProvider.apk
[Update 14.07.2011 - 10:58 GMT+3 DST]
Fixed framework.jar - no more errors seem to come from it
New zip not made on mac so no low memory errors
New problem that might fix the apps: All apps look for their classes.dex in /cache/dalvik-cache but only system classes are there. The app classes are created in /data/cache/dalvik-cache
All apps are back because the errors don't come from them
[Update 28.07.2011 - 18:53 GMT+3 DST]
Added dalvik-cache to /cache script
New zip with init.d script and updated framework
Need to fix dead code in framework
Need new kernel
Need MDPI apks
Need libs that don't make the apks crash
Latest flashable zip:
http://www.multiupload.com/VNM8QTDBZ3 [Updated 28.07.2011] Thank you 4silvertooth
(DOES NOT BOOT! DON'T FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!) Sorry... i had to put this in big red letters because apparently people didn't see it well...
If you would like to help go ahead. Download the rom or make your own one if you don't like our development and give input. But most of all don't try to bring us down with "this can't be done" stuff. It can be done and it was done for another armv6 device. We need to get apps and framework to work and rom to boot. Libs and bins will come after...
This being said i would like to thank these people for their work so far and for making me get off my ass and do something useful:
4silvertooth
jazux
DJoptimus-One
Also i would like to thank overflow for his rom. It's the base for our miui so far.
Fantastic news! I can't wait too see how this works out. Good luck, you're gonna need it!
look forward to.
Thanks popdog
Will get into works as soon as i get my laptop back
Great news!
Waiting for testing release!
wow ! MIUI for o1 ?
oh sh*t this is what i've been waiting for so long !
looks good ill be happy to help, just ask for now im looking the motorola dump... maybe theres something that will help my team on galaxy 3 but anyway i subscribed tol this thread
EDIT: damn that motorola dump is useful, already found many, many tweaks thanks a million times for 4silvertooth
Hey can we use pastebin.com for all the logs.. it will be convenient and easy.
Sent from my LG-P500 using XDA Premium App
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
popdog123 said:
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
Click to expand...
Click to collapse
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
About the log.
The error so.lcddensity(something) is in build.prop you have to add it, it's using 160 by default.
All the missing class will have to be taken from the decompiled framework.
Sent from my LG-P500 using XDA Premium App
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Breaking news of the day! I'll one of the first tester Keep going, heroes!
popdog123 said:
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Click to expand...
Click to collapse
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Great news!
4silvertooth said:
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
+1 for this, it would be easier to download for people with a slow connection like me.
ok ok... will do that... but for now we have to make a good base to start off of...
4silvertooth said:
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Whaaat???
Nice to see another dev porting some other firmwares to our phone if you want help then I'm in
Sent from my LG Optimus One P500 using XDA Premium App
jazux said:
Whaaat???
Click to expand...
Click to collapse
Never mind back to that later.
Sent from my LG-P500 using XDA Premium App
dsixda's Android Kitchen - Now for Samsung Galaxy Note GT-N7000
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy Note GT-N7000 custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy Note GT-N7000 ROMs with the kitchen.
To my surprise, since the file structure is very similar to that of the Galaxy SII GT-I9100, I only had to make a very minor update to the kitchen (one blank file) to allow GT-N7000 support.
Special thanks to long-time XDA user Ameet for testing and providing feedback!
I have already posted an equivalent guide for the Galaxy SII I9100, so no need for redundancy. The same steps will work for your device:
CLICK HERE FOR KITCHEN INSTRUCTIONS FOR YOUR GALAXY NOTE GT-N7000.http://forum.xda-developers.com/showthread.php?t=1227549
NOTE: This guide does not apply for the other models of the Galaxy Note; there is a separate thread for the SGH-I717.
Since the above link is for I9100 discussion only, please post all N7000 talk in the thread right here. Enjoy!
So good to see you here. Welcome.
chasmodo said:
So good to see you here. Welcome.
Click to expand...
Click to collapse
Thanks, I don't have the device but I have its little brother, the Exynos-based Galaxy SII GT-I9100
Thanks for coming over. I have actually been using it on the Note for a long time. Its a great tool. Thanks for developing it mate
Thanks for this...
Sent from my GT-N7000 using Tapatalk 2
Awesome work as always Dsixda, as always.. Am sure this will be of great help for Note users
Sent from my GT-N7000 using xda premium
---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------
Am surw many know this still thought I'll post an observation as a note
"You have to extract the CSC from cache.img and copy it to system folder to avoid the keyboard null error after flashing"
Sent from my GT-N7000 using xda premium
was waiting for this
Thanks a lot.
Nice to see you thanks mate
Sent from my GT-N7000 using Tapatalk 2
Awesome
I'm here at work, setting this up instead of working. Don't tell anyone...
Great.
Thanks:thumbup::thumbup:
Von meinen Project-ReVo Black Beast gesendet.
Nice I will try it as soon as possible
Heyyyy! Thx read all about the kitchen in another thread . Glad it is here . Time to cook.
Sent from a secure institution......
Great to see official NOTE support. :laugh: You're amazing dsixda...A HUGE Thanks from all the XDA members!! :good: :fingers-crossed:
Thank you!
Welcome Here, Master,
We had Pleasure using the Kitchen in S2, now I don't find the words !!!! :fingers-crossed:
THANKS A MILLION.
this is so cool...too bad i dont have my ubuntu now...and i dont like using cygwin.but this is good to know.. it exists:cyclops:
@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?
asf58967 said:
@not-i or anyone kind enough to answer, I am having some confusion here and can't find an answer after hours of searching. I am wanting to run the kitchen for a NANDROID of a backed up ODEXED LT5. I am having issues figuring out how to get preload included. is there something I am missing here?
Click to expand...
Click to collapse
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick
not-i said:
Easy way if you have a Nandroid is open archive of preload.ext.tar.a (coming from philz kernel backup) with 7zip and copy preload folder straight into Working Folder. All done and very quick
Click to expand...
Click to collapse
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip
asf58967 said:
ok, so when I actually build the zip via the kitchen, it will include preload? or should I just manually make it using a preexisting n7000 zip
Click to expand...
Click to collapse
Copy the preload folder into working folder before you deodex or do any mods. Thats what I have done anyway. I would then cut all apks from prelaod/app and paste into system/app for the deodex. Then when that is done copy those back that you want in preload.
The program will create the zip for you when you build it. I have found I need to modify updater script 9 out of 10 times though for it to flash. If yoour having trouble let me know and I'll forward you a script that works.
Make sure when you go through the process that the rom zip also includes create_preload_symlinks script. It should put this in for you in the process though.
Welcome happy campers
Here is a fully working pretty much fully tested port of Clockwork Mod Recovery 6.0.3.0
Big thanks to UTKANOS at #cyanogenmod irc channel for his help in building this for me to test till everything was working
FEATURES
All features in 6.0.3.0 based CWM recoveries are implemented
Touch screen working
Restore/Backup functions
All wipe functions
All Mount functions
Install from sd and Internal storage
Generally all features you expect from working ClockWorkMod recovery
without further ado here is the link to the recovery image: http://d-h.st/nMv
md5 Checksum : 8f7dda170425218f47717a9c9c931bea
source code at utkanos' github: https://github.com/utkanos/android_device_htc_golfu
Thanks goes out to mmmcfc for his initial work on the recovery we worked on to bring you this version, his original thread at :
http://forum.xda-developers.com/showthread.php?t=1785010
to install recovery is same as always for people who already know
for those of you who are new to this and do not know but are at the point of installing a custom recovery through a rom install guide please simply turn off your Desire C device, drop out the battery just in case fastboot is on in your rom settings, replace your battery then hold the volume down key and hold power button till you boot to bootloader.
Ensure phone is on fastboot setting (will have fastboot written in red if you are) plug in the usb cable and it should say fastboot usb now then enter this command from terminal window that is in the directory where you have this image downloaded to
Code:
fastboot flash recovery recovery-clockwork-6.0.3.0-golfu.img
with any joy you should now be able to reap the benefits of touch screen enabled up to date CWM recovery
enjoy
p.s. if you have issues installing this or do not know what our doing either do not install OR search the forums for root guide and recovery install guides and if you cannot find something relevant feel free to pm me
dont forget to come to our irc channel at irc.freenode.net ##HTCDesireCcm9 (dont forget to put two hash signs not one) we are friendly in the channel and are hoping it will begin to grow alongside development for the device
thanks
soon to come wifi fix for CM9, hopefully soon CM10 build and with all the fixes no doubt many custom roms from many users throughout our device section
Reserved this for maybe other information etc...
russell664 said:
Reserved this for maybe other information etc...
Click to expand...
Click to collapse
this is why we get along so well lol, albeit you do take forever to respond to irc chat but hey no one is perfect....
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
nikhil16242 said:
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
mehmehmen said:
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
Click to expand...
Click to collapse
Ahh ok Np . Anyway.. good to have a recovery that doesn't reboot itself :thumbup:
Sent from my Nexus 4 using xda premium
A damn of a recovery, great work and thank your for this. Keep up the good work. Thank you again.
Thank u for this ,and thank u for keeping this phone alive , gl on ur cm work guys
Sent from my HTC Desire C using xda app-developers app
no worries guys, amazing to have 200+ views and what 4 users post in the thread lol all thanks is aimed to utkanos for his work making it happen, and mmmcfc for his original version build we worked on. i just tested and provided needed files to utkanos. all thanks is more than appreciated as we spent a whole day pretty much fixing the bloody thing
By the way, we should contact the guys from CWM to get official support like nikihil did.
TheRedHunter said:
By the way, we should contact the guys from CWM to get official support like nikihil did.
Click to expand...
Click to collapse
you need to shoot a mail to koush to get rom manager or cwm support.
Finally a non-rebooting recovery!! Thanks! :good:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
mehmehmen said:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Click to expand...
Click to collapse
You are a great man, and your work is very appreciated. You have my thanks and I'll try to add as many thanks to you as I can.
I've shot you a few thanks as it's a damn fine cause, even if I strongly dislike cwm. I am afraid I am a Twerp through and through.
Ps I will try and get some extra thanks to you Redhunter as you are such a generous guy with your thanks and you always are upbeat and positive. It's good to see, thank you.
All the best rich
Sent from my Nexus 7 using xda premium
Dead link?
The download link to dev hub seems to be dead/broken ... is it just me?!?
AirCombat said:
The download link to dev hub seems to be dead/broken ... is it just me?!?
Click to expand...
Click to collapse
It works for me
calinorg said:
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
Click to expand...
Click to collapse
my ? too.i just updated to current version,and browsing around i noticed it is not there??
Can u make this in colours of mujenu touch recovery and create a guide for building recoveries
Sent from my HTC Desire C using xda app-developers app
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.
this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app
tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much
Here's presenting stock Slimbean ROM with just 2 commits reverted which prevented users from adding the big menu button to navigation bar and SlimPie. Besides this, this is pure Slimbean without any modification whatsoever. I'm not a developer, in fact I learnt to install linux because I wanted the menu button so bad. I thought maybe I should share this with similar minded people. I'm going to upload updates as and when Slim team releases 4.3 updates as I'm not sure about the changes that would be made in 4.4. I won't be able to take any request as I am totally unaware of how to make any modifications, cherry picks or anything else. Hope you enjoy this ROM.
Code:
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
SlimPIE
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter, SlimIRC and much more
Full feature list and changelog can be found on Slimroms website.
Installation instructions
For most users
Please keep in mind if a special instruction is needed it will be noted in the changelog.
Download the latest build from
Addons
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
Source
This ROM and kernel uses stock Slimbean code, which again can be accessed through Slimroms website.
Credits:
mar5hal
Nebucatnetzer [Slimroms forum]
NeB [Slimroms forum]
kufikugel
Entire Slimroms team for the source code.
Slim team has done an excellent job, please consider donating them.
Download Link:
http://d-h.st/DDf
[If you want to make a mirror, please contact me to update the OP]
Reserved...
another one... just in case...
@gururoop thank you so much for this, the one main thing missing from slim, Menu Button. In theory there shouldn't be any issues since its only 2 extra commits. Downloading now :good:
Just some screens to confirm. Everything is running smooth, no issues whatsoever
Sent from my Nexus 4 using XDA Premium 4 mobile app
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
dark_ente said:
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
That would be great, indeed. :good:
dark_ente said:
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
finistere said:
That would be great, indeed. :good:
Click to expand...
Click to collapse
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Changelog what is changed?
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
smartymcfly said:
Changelog what is changed?
Click to expand...
Click to collapse
No changelog... Just wanted to check how long does it take to compile in a virtualbox so synced the latest code and compiled...
Sent from my Nexus 4 using xda premium
scottx . said:
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What statusbar mods are you talking about? This build is pure stock with just 2 reverts which enable us to add the menu button, apart from that no other change. The latest build was synced on 5th November, so maybe the statusbar mods were added later.
Sent from my Nexus 4 using xda premium
gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
dark_ente said:
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
Click to expand...
Click to collapse
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
gururoop said:
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
Click to expand...
Click to collapse
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
dark_ente said:
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
gururoop said:
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
Click to expand...
Click to collapse
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
dark_ente said:
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So what you are saying is that if someone or I can just extract those 2 apks and add to a flashable zip I have lying round and menu button will be added to normal slim?
Would have been quicker!!
Sent by mobile telephone.
^^^^LOL I agree... Sidenote its funny how many people can creates so much goodness with building or modding files but dont know how to create flashable zips... LOL
dont re-invent the wheel I believe just get a gapps zip and mod away...
OH yea my bad thanks for the rom I too am a big fan of the menu and choose to live with it