Related
I am currently work on a program/script to manage ROMs, and I will be releasing it initially for the Kindle Fire for beta testing. This will be a full featured program with the following :
- Compile ROMs from source
- Extract & zip ROMs
- Decompile/Compile APK and JAR files in the ROM (selective or the whole ROM at once)
- Unpack / repack kernel
- ROMs and devices each will have their own config file to store information specific to each, such as comments and status
- Much more planned, such as the ability to browse and edit files, search and compare, etc
The big advantage to this, and what prompted me to write this in the first place, is the ability to have all of the necessary tools in one place and better keep track of your ROM projects. As I was working on modifying or porting ROMs, a big headache was having to go to so many places to do different things to a ROM, which leaves files scattered all over your hard drive.
This will help keep everything more organized and the goal is to cut out manually having to do so much when it comes to basic tasks, and eventually even the more advanced tasks involved.
The initial release will be for Linux, but a Windows version will follow (minus the Linux specific features such as compile from source).
I have made some great progress on this already, and am close to a beta release.
So, what I need help on is a name for this. Here is what I have so far as choices, I welcome suggestions. Those that reply with suggestions for a name will be the first to receive beta versions to try out
- DEVROID
- [ARM] Android Rom Master
That is all I have so far, so please throw some good options my way.
How about - Kindle Fire Rom Manager?
romifi_R_ed? or ROMIFI_r_ED? linked with youe nick
animefun135 said:
How about - Kindle Fire Rom Manager?
Click to expand...
Click to collapse
This was originally just for the KF but most of this stuff is generic enough to work on other devices, so I will be adding functionality for multiple devices. So the name shouldn't be specific to the KF. I'm just offering it for the KF first.
When it was going to be KF specific I had "Kindle Inferno" in mind....
Now that would be a good name for a ROM !
[ARDS] - Android Rom Developer Script (or Studio)
or
[ARDT] - Android Rom Developer Tool
or simply
[ARD] - Android Rom Developer (the shortcut is like a german television channel)
b63 said:
[TARDiS] - The Android Rom Developer Script (or Studio)
Click to expand...
Click to collapse
Fixed
Need to come up with something foe the "i"!
Sent from my SPH-D710 using xda premium
[CRT] Complete Rom Tool
Sent from my myTouch_4G_Slide using XDA App
I like the variation that @nykuil modified. Don't think you need to come up with anything for the I really. I know nearly nothing about Dr. Who, but love the name because it is recognizable.
Yeah the tardis is really a cool idea. who doesn't love Dr Who. ( at least the original )
Rockin' the Miui Incredible 2 w/xda premium
Thanks guys, keep 'em coming...
CWMR+KF
ClockWorkModRecovery+KindleFire? ?
Sent from my Kindle Fire using xda premium
Slrb script library for ROM
Slrp script library for ROM publishing
b63 said:
[TARDIS!] - Total Android Rom Development is Easy!
Click to expand...
Click to collapse
Maybe this?
Sent from my myTouch_4G_Slide using XDA App
UPDATE: PDROID NOW AVAILABLE VIA BOTBREW:
http://forum.xda-developers.com/showpost.php?p=26033156&postcount=10
First, for those who haven't heard about it:
PDroid
PDroid ICS Port
At this point, as far as I can tell, PDroid is only available as a patchset, not in any rom.
It looks like it is a lot more powerful than CM Permission Management.
The purpose of this poll is so Vibrant users can show interest in a rom with PDroid built in, hopefully motivating rom devs to add it.
I'll check this out tonight - looks interesting.
jellette said:
I'll check this out tonight - looks interesting.
Click to expand...
Click to collapse
I'm not set up to develop at present, but I'll try any CM or ICS open-source rom that has this built-in, or an open-source zip to hot-patch it into said roms.
Yeah pdroid looks awesome! I asked about this in slim forum and cm forum somewhere around here but got no love lol... its really awesome permission management and if they add a firewall it would be a must need app that I would love to buy... you can use it with droidwall but it has leaks and allows access before it loads up on reboot... pdroid could block that from the start if it had a firewall incorporated tho... I look forward to the development of this awesome app.
Looks like we might get a try ourselves with an ics patcher in the not so far off future
Sent from my SGH-T959 using XDA
An ICS patch does appear to be in the works.
As for CM, you're right, it will never have PDroid, and I'm really beginning to wonder if they will even bring any permission management into CM9. If you look at the PDroid patch, it's not a huge amount of code, meaning if Google wanted android to allow privacy, they would have added it long ago. But the frankly rather seedy business model of Google and many "free" app writers and Facebook is the harvesting and selling of personal information, and they apparently threatened to cut CM off from Market access if they added strong privacy.
Clearly the long-term solution is Google-free phones running Debian or Ubuntu, but until then, there's PDroid.
Pdroid Linux patcher ported and working for aokp and cm9
Sent from my SGH-T959 using XDA
c-pimp said:
Pdroid Linux patcher ported and working for aokp and cm9
Click to expand...
Click to collapse
Nice. Where?
Pdroid working for AOKP and CM9
PDroid is finally available for AOKP and CM9 on T959 Vibrant via botbrew. Follow instructions at http://forum.xda-developers.com/showpost.php?p=24934484&postcount=123 big thanks to mateorod for porting it over.
Hey guys-
UPDATE 6-5-12
I haven't had any requests for updated packages except for AOKP, so I can only confirm that AOKP Build 40 and CM7rc2 are currently supported! Any other ROMS are at your own risk! If you would like a ROM for vibrant or any other device to be supported, please post a request.
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button.
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
New!
android-framework-pdroid-cm7.2final
For CM7.2 Final!
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!
I confirm this is working with the 5-12 CM9 nightly. Thanks to mateorod and everyone he thanks in the post above!
Thanks, cashmundy. The problem was that cm9 has a weird naming convention for just your device, at least unique as far as I have seen.
I just changed the package to reflect your arch.conf.
So thanks very much for testing and finding the problem. I am pretty sure everything is OK now, but let me know!
Still on CM9. Did a reset, installed botbrew and your repo, and I now have no pdroid package.
As expected, botbrew fetched the CM9 props on install
, except that it down-cased the model to "sgh-t959".
arch.conf:
arch all 10
arch any 20
arch noarch 30
arch armeabi 100
arch armeabi-v7a 110
arch sgh-t959 120
build.props:
ro.product.model=SGH-T959
ro.product.brand=samsung
ro.product.name=SGH-T959
ro.product.device=SGH-T959
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
Okay man. I took out the sgh-t959 package because I thought you said cm9 had vibranttmd as arch.
Are you saying that it changes whether or not you install cm9 as an update? Cause I don't see how that would be.
I am going to make it so Botbrew has cm9 packages for sgh-t959 and vibrantmtd. We'll sort it out for good later tonight when I have some time.
Thanks for your time and effort testing this stuff!
CM7 has vibrantmtd as ....device and SGH-T959 as ....model. CM9 has SGH-T959 as both model and device, as does AOKP. If you (or BotBrew) could use model instead of device, it might work well.
What happened before was I tried CM9 over CM7 without a reset. BotBrew didn't catch the upgrade, and so kept the conf from CM7. When I reset and then installed BotBrew, it found the new props and configured accordingly. A hook in BotBrew to check the current rom on startup and reconfigure itself on flashes would be a good thing.
I'm currently showing all three packages, version -9.
One minor note: somewhere you specify the BotBrew refresh button as being on the top right. On my phone it is always on the bottom left. Maybe more vibrant weirdness.
Final random thought: I'm not very impressed with CM9. It has some real drawbacks (the keyboard for example).
CM7 is still overall a lot better (to me) and if PDroid ever makes it there, I'll test it.
Well, I am still considering about cm7. Let me see.
Botbrew does has services you can turn on to configure at boot, as well as several ways it detects flashes, although most of those are centered around packages or the terminal.
But thanks for those tips, there is definitely some weirdness going on with the vibrant that I haven't seen elsewhere, but is good to know about because it could resurface in other devices.
But yeah, for instance, you could use light pad to turn your sdcard into a web server, and host websites off of it, so that's one of the services options.
There is honestly a world of stuff in the repo already, and he's about to add debian INSIDE android.
Crazy. Thanks, cashmundy. I will look into cm7.
Very cool.
I think I'll try AOKP again when a new build is out, and test the patch there.
One thing that would be useful would be a white-hat app which would request all permissions, gather all possible data, and display it. As it stands, we have to take it on faith that pdroid, droidwall etc actually work.
For the long term, I am very much hoping for Debian instead of android.
mateorod said:
Hey guys-
Most everyone in this thread I already know from the port thread. I was looking for a good place to put out this info. Glad I didn't start another thread already!
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button at top right!
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!
Click to expand...
Click to collapse
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
The Vibrant is I think the most recent device, and the BandN Nook is supported,
so I expect the Kindle will be someday.
gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
If you run cm9 or aokp, I can take care of you.
Post your services, core, and services.jar plus build.prop at my packages thread so we keep this vibrant only.
Thanks for your interest.
Guardian Project Installer V1.0 Beta
Many thanks to the people at www.guardianproject.info for their hard work!
What is this?
This is a flashable zip (tested with CWM) that installs most of the apps from the Guardian Project. The guardian project is a non-profit organization that is building apps and tools to help users and whistle-blowers alike to stay safe and anonymous in this day and age. This is a faster way to setup a secure/private device. I also encourage enabling Full Disk Encryption in ICS/JB settings. Quote from the site:
How Guardian Helps
While we think that a secure, privacy-enhanced mobile phone is a good thing for just about anybody going about their daily lives, we like to also consider the extreme cases, where this technology might change the course of someones life.
Click to expand...
Click to collapse
Source: https://guardianproject.info/home/use-cases/
What apps are installed?
Orbot: TOR (Anonymous Web Browsing) for Android
Gibberbot: Secure Encrypted IM using Google Talk
ObscuraCam: Secure Camera that obscures faces
InTheClear: Data Wipe (“Poison Pill”) Wipes phone on command
Android Privacy Guard: Public Key Crypto (GPG) for Android
TextSecure: *****REMOVED**** See HERE for details.
DroidWall: Firewall that uses IPTables to prevent data leaks and Network attacks.
FDroid: Alternative to Google Playstore. All apps are FOSS.
ORweb: Privacy oriented web browser that works automatically with Orbot (TOR). [ADDED: 08//19/2012]
OSTel: Encrypted VOIP phone calls using ZRTP. The app is based on CSipSimple For more info go here to create a free acount go here. NOTE: This service & app are in public beta status. [ADDED: 08/20/2012]
K-9 Mail: Open Source E-mail app that works with APG for sending encrypted E-mails. Has lots of powerful options. [ADDED: 08/21/2012]
CaCertMan: Manage the list of Certificate Authorities on you phone. Let's you revoke any CA's you distrust. ROOT Needed. [ADDED: 08/21/2012]
CryptFS Password Manager - Allows you to have one password for encryption and a shorter one for lockscreen. see here. [ADDED: 09/08/2012]
NoteCipher - Allows you to store messages in a AES256bit Encrypted SQL database. [ADDED: 09/12/2012]
GnuPG - GPG encryption for android (Uses busybox) [ADDED: 05/19/2013]
How To
Download the zip bellow
Copy the zip to the sdcard
Boot into recovery
flash the zip from the sdcard
Reboot
Done
WARNINGS
Please note: THIS IS BETA. I AM NOT RESPONSIBLE IF THIS BRICKS YOUR DEVICE. FLASH AT YOUR OWN RISK.
With that said I have successfully used this multiple (10) times on three different devices. Please report any bugs and issues.
Known Working Roms
CM9 Official
CM10 JellyBro
CM10 EuroSkank AOSP
Rasbean
Tested on CM9 Motorola Atrix 4G
androidme aosp light v.1.1
Codename Android JellyBean 3.3.0
HTC One S Stock Rooted.
Nexus S GSM CM9
Galaxy S
Galaxy Note N7000 CM9 Stable
Known Bugs
Not working on Nexus 7 - Can someone test If it installs fine with TWRP on any device?
Comming soon & Downloads
More apps will be added along the way. I will also be trying to get aroma set up so you can select what apps are installed.
All of these apps are released Open Source under their respective licences. All Credit goes to the developers of the apps. I have only bundled them into an easily installable zip file.
UPDATE: Thanks to Volk the installer is now Aroma! You can now select what apps you want installed and if you want to uninstall the old ones.
Mirrors:
Latest Versions:
GPI Version 0.9.1
Signature
New: Updated all binaries, added GnuPG
Changes: Minor bug fixes. added GnuPG.
Please check your download against the checksum on the page. For security please check the signature against the public key . To check the signature place both the ZIP and .sig file in the same folder and use any PGP/GPG program to import the public key and verify the signature. PM me for some suggested programs if you are unsure.
Depreciated - No Longer Available.:
Old versions have been pulled due to possible security issues.
Please mirror this download if you can. Also Any feedback is greatly appreciated. If this helps you please press thanks!
I also highly recomend you read this presentation to see what inspired me to do this.
Test+Mirror
Awesome! Now booting again....
Mirror: http://www.4shared.com/zip/vDiK6V4K/Guardian_Project_Installer_Alp.html
Edit!: Tested and working on Jellybro cm10
Thatgrass said:
Awesome! Now booting again....
Edit!: Tested and working on Jellybro cm10
Click to expand...
Click to collapse
Awesome! Thanks for the feedback! I will post that it worked in the OP.
Really nice idea!
Good and original work
Great!
Great!
Really inovative !
Good luck for your project !
Looks awesome.Tnx dude!
Works with rasbean
Sent from my Galaxy Nexus using xda premium
Thanks all for the feedback! I will be updating the addon in a bit and adding on some more stuff. :good:
This is absolutely fantastic, I was wondering when something like this would be put together! The guardians are absolutely right when they say the mobile platform is the least secure, anything that can be done to change this is beyond welcomed.
Anyone tested on CNA?
Sent from my Galaxy Nexus using Tapatalk 2
New versions are up!!
EDIT: I also want to reccomend FuguMod Kernel nikademus did a great job incorporating PaX and Stack Protector into his kernel to increase security.
Using this on androidme aosp light v.1.1, works great. Thank you for this!
Sent from my Galaxy Nexus using xda premium
Mo_Nexus said:
Using this on androidme aosp light v.1.1, works great. Thank you for this!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks added to the OP.
Gucci.Nexus said:
Anyone tested on CNA?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tested. Confimed working over here on my GSM Galaxy Nexus.
UPDATED: New versions are up. Added in Ostel for encrypt Voice calls. Also tested new devices (posted in OP).
Thanks for providing this package, works great, would love to see more added to this or maybe a complete privacy/secure ROM.
Sent from my Galaxy Nexus using Tapatalk 2
defconoi said:
Thanks for providing this package, works great, would love to see more added to this or maybe a complete privacy/secure ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm glad you like it! I am currently working on a version of CM10 that will incorporate these features/apps as well as a more secure kernel. I should (hopefully) have Alpha builds out this week.
x942 said:
I'm glad you like it! I am currently working on a version of CM10 that will incorporate these features/apps as well as a more secure kernel. I should (hopefully) have Alpha builds out this week.
Click to expand...
Click to collapse
See if u can prebundle the repo of guardian project of https://guardianproject.info/repo/ as well.
Sent from my Galaxy Nexus using Tapatalk 2
defconoi said:
See if u can prebundle the repo of guardian project of https://guardianproject.info/repo/ as well.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I will add it to the list I will have to take a look at the resource files and see where FDroid stores the repos.
hey, thanks for this. I got here from the Guardian Project mailing list, and I just posted this feedback there.
The full zip installs fine on a Samsung Galaxy S i9000, running CM10 nightly 20120820 and Semaphore 2.0.6 kernel. The progress bar didn't go all the way across, so I thought it might've bailed, but it looks all good now.
So far tried I've Orbot and TextSecure, which I assume were reinstalled, and my settings+data remained. Ostel kept my login info, too, but going into settings I get incredible lags (which may be the new CM10, and the funky partitions that the dev/device maintainer used to work around our space limitations and NAND speeds). Also tried ObscuraCam and opened Panic, looks OK. New toys that I've never played with yet.
Before flashing this, though, I tried installing the update zip, in the hopes I'd add Orweb, ObscuraCam, etc., and not lose data+settings with the apps I already had. The flash said it completed (again, despite that the progress bar didn't go all the way across), but when I rebooted, I had no new apps. Then a weird quirk: I opened a data connection and Orbot, and it connected fine, but a check with Firefox Beta said I had no net connection. Checking mail in K9 gave me errors, but Twitter with Tor proxies set loaded fine. According to IP Track, I had no external IP. I turned off Orbot, turned it on again, and then all was working as expected. Strange.
Anyway, thanks; this is a great project. I also want to ask: Any chances of including RedPhone? It's open source now, but unavailable on Play where I am; I think it's limited to only the US. I used Market Unlocker to get it, and will be testing it here soon. Nathan of Guardian Project was saying that outside of the US, it may have push/wake problems. I'll find out soon here, but if it's not too buggy, it'd be great for everyone outside the US.
edit: also, what about adding MD5 checksums, or a GPG signature?
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Hello everybody, It´s been like a week since I last posted, a lot of things went wrong in my house and I somehow lost all my computers
anyway, back in business again, Last night I had to install the stock Sprint GB sbf, to my surprise it worked Really, Really good.
I´ve had a Defy+ and a Milestone 2, And I remembered having lots of issues with modding aka. no signal, wifi issues (like the cm7 and 9 ones) data issues, system lags, poor battery life, kernel errors on development, Overclocking settings not being saved, recovery mess-ups, and a lot of depicable stuff, most of all kernel-related.
Anyway, last night I flashed the stock rom over cm7 and noticed a real speed, functionality and battery boost, so I thought of just theming, de-bloating and optimizing the stock Sprint ROM.
Please follow me here:
We will never be able to flash custom kernels (not w/o the help of a reaaaaal good DEV)
CM9 &10, though they are eye-candy, are based actually on Gingerbread kernel, so no new features can be added besides the ones you can get withg new apps.
CM7, though stable, lacks the performance and functionality of the stock rom.
Finally, the stock rom as I said, (and I´ve tested TONS of ROMS in different motorola devices) is the one with the best responsivenness, snappiness and battery life, plus It's almost clean (eg. bloatware is easily removed.)
How will it be done?, you may ask.
Well Our first step, will be deodexing the stock GB SBF.
After deodexing we will be optimizing the build.prop on our phone, to trick apps into installing on our phones, and to make some quick optimizations.
Once we have deodexed our rom, we will be able to run,autorun and theme /system/apps.
Apps like Gnow, the statusbar and other tweaks can be easily (RELLY EASY) ported to deodexed ROMS
So this is the challenge guys, Let´s build our own stockcustom ROM.
So far I´m re-flashing stock sprint GB to continue testing only the essential apps, so we can build from there.
And just for a tease; here is my latest build.prop, with some tweaks and tricks taken from other roms and my personal experience, just make sure you have root access, fire up a file explorer and replace your build.prop
Please Refer to next post for links on how to maybe help me with deodexing the full rom.
And please, developers, dont take this as a shady move towards your development, I just think that the best way to make something is to start from scratch..... there are too many source files, modded files and crap files on cm7,9&10 specially when not officially supported (Because everybody messes with the files and re-distributes them, so a lot of clutter and unneeded files, references and code are injected on some releases....)
So my friends, we have a common goal, By now I have succesfully overclocked/undervolted the phone to 1350/233 mhz (not on recovery!!)
I´ve deodexed system/framework/
and Im stuck trying to deodex system/apps/
Xprt Owners of the world, please come on over here, we can do this...
I´m an architect/artist so I really want this to have a sleek look, but not copying a specific stock look, if you know what I mean....
From now on refer to the "wished features post" for features you´d like
And now my final statement:
Though it IS possible to compile JB or ICS from source to our phones, my experience with this somehow outdated android motorolas, is that you will not get significant performance boosts or super cool functions with new software. The only way to get this functionality is by upgrading the kernel which I again declare IS NOT POSSIBLE on our phone. CM9 and 10 my look like JB and ICS, but run straight off a GB kernel.
Yes you will get a lot of new stuff like menus and graphics, but the functionality will be the same, plus all the eye candy will trade off your new features with lags and possible errors.
Software is built in time with devices, and it doesn´t matter how much you say "but the hardware is capable of more!!", incremental software updates "ignore" some HW features, so they have to be forced or modified to run, which adds more procesess/tasks to the kernel and this will suck your speed and battery.
Let´s build something pretty...............:laugh:
Hello everybody, and welcome to the world of modding.
From today, we will be coordinating an army of people to work towards a common goal: Having the best ROM for our phones, and surviving the day.
The tools you absolutely need:
Brain
Hands
Eyes
Text-comprehension.
Be a self-troubleshooter
Advanced Google skills
Patience
Some Weed
First of all I will just oversee the topic: ODEXED vs DEODEXED
In simple words, Odexed systems have XX.apk and XX.odex, which store certain app properties (like icons, colors, fonts, menus) so that they wont be messed up with, thus making the system more stable, Deodexed systems, have only APK´s with their icons, colors and behaviors packed on, thus making theming, modding and using alternative system apps easier.
If you would LOVE to read about the subject, please refer to this: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Well, now that you are totally aware of the odex-deodex situation, you might ask yourself..
-how the phuck do I deodex my system??????
Well, deodexing implies merging the .odex properties onto the apk.
Hey!!!! but how???
you need brains, patience, Java SDK7, Android sdk, and music.
http://forum.xda-developers.com/showthread.php?t=1852322 this instructions are for deodexing.. good luck....
To save your time, you need Android SDK and JSDK properly installed, you need xUltimate (Try and find the version that works on you), and you need the patience and willingness of Sidharta.
Ive tried already 5 versions of xUltimate to find out errors on different files!!!!!!
http://forum.xda-developers.com/showthread.php?t=2065270This will tell you some other basics on the xultimate deal.
There are other ways to deodex, help me google that.
We will be based on the stock 1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US SBF....
I would love to develop something good to both sprint and boost, but I have a Sprint handset, so I cannot assure our development will work on boost handsets, so please just sprint handset owners only for now.
For xultimate errors and troubleshooting, please refer to Google.com!
Ive been up all last night deodexing my system apps, and found out that most google related apps cannot be deodexed...
maybe that's why you need to install gapps in cm7 or other custom roms...
anyway people, let's get fully deodexed.
Make sure you have both Android SDK and Java SDK 7 PROPERLY installed oin your pc before trying this.
Cheers, luck and please reply
One last thing, I dont know if it is related somehow, but try to flash your stock rom without a SIM card inserted
Quick update: I Think I´ve got it figured out....
You need full Android SDK, and Java development kit, Android sdk tools alone wont do it, and java alone wont do it, you need developer runtimes and libraries for some programs like xultimate to run right.....
And you need not to activate, use or anything your phone before trying to deodex, I guess just starting up and entering simple things as the time, or having a sim card installed, or your google account can write data on the phone and mess up with the deodexing process.....
xultimate has already deodexed full framework and has passed from the yesterday´s troublesome google quick search box...(first thing to fail last night) so let´s hope it goes well.. it is indeed a loong process...
and just another error, but now I think I have it figured out, you need smali-baksmali assembler/disassembler for some specific .jar packed files... I´ve just installed it, and hopefully will post a fully deodexed stock rom today or tomorrow, for you to test and for us to start theming.
remember if you want to try... you need jdk not just java, you need full android sdk bundle, and you need smali/baksmali on your jdk installation for it to work properly...
%#%"!!!
This completely sucks, I´ve been trying to troubleshoot the errors xultimate is throwing at me on specific files, that lead me to download A LOT of java JRE and JDK versions, and both in x64 and x32 flavors, which apparently caused a major mixup on my PC´s guts....
Now I´m freaking trying to clean up my dev enviroment, trying to re-set the appropiate paths and classes, but hell with it...
Anyone succeeded??? please let me know if you´ve tried and if you get into any error can you please upload a screenshot???
thanx
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
tzuba12 said:
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
Same.
Sent from my MB612 using xda app-developers app
are you trying to deodex the stock rom?
rongsang said:
are you trying to deodex the stock rom?
Click to expand...
Click to collapse
yes sir, but in the mean time I managed to patch it with the battery mod, power menu and ICS style notifications
If I can deodex it I think I can improve it a little bit more in terms of performance and looks and functionality , but my powerful pc is a zombie right now, this is no task an old notebook can handle
I have deodexed it a long time back but sadly I can't upload it now. You can run kitchen from cygwin and it will deodexed your rom completely.
Sent from my MB612 using xda app-developers app
Ive used the kitchen and xUltimate with no good results mate!...
I always get smali errors or heap size errors despite I was using even a 4gb heap size, and tried using different versions of smali baksmali....
I am beggining to think I´ve been cursed by the digital gods.
BTW, if you´re able to upload it, I´ll be very thankful dude! I think Im going nowhere right now