[Q] Binaries...what do they mean? - Samsung Galaxy Nexus

I'm curious to what the binaries mean for upcoming roms. My assuption was that the roms were from the source meaning they had everything. So what are they and what for and why would they matter now? No this is not a "i'm a noob question" I just don't know...:angel:

www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app

b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking

digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
They have provided th 4.2.2 binaries for building a 4.2.2 rom from aosp, that's all.
Currently, developers have been building 4.2.2 hybrid roms.

digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus

bk201doesntexist said:
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
Click to expand...
Click to collapse
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.

digitallure said:
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
Click to expand...
Click to collapse
Well, they do allow custom ROMs to be made, but new binaries don't necessarily mean new ROMs will be stabler. If you don't build from source, don't worry about it.
Sent from my Nexus

b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.

Electrodeath0 said:
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Click to expand...
Click to collapse
Thanks for the answer

Does anyone have a zip file to flash the new binaries for Maguro?

ReggieS2 said:
Does anyone have a zip file to flash the new binaries for Maguro?
Click to expand...
Click to collapse
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD

najaboy said:
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I read this over at Paranoid Android's G+ page so it lead me to think that I needed something
Recently the AOSP has been fully completely, all the needed drivers are supplied. We have updated AOSPA immediately of course and a couple of hours later we've had it merged.
Now i want everyone to listen up. YOU ABSOLUTELY NEED TO BE UP TO DATE. Or else your device will be incompatible, unable to make calls perhaps or who knows what. Google supplied a new bootloader, and for phones, new radios. You can get them straight from Google and install via fastboot. Or, the easier way perhaps, you go to XDA and get them as flashable ZIP files.
Either way, this concerns all 4.2.2 roms out there that include Googles new 4.2.2 hardware drivers.

Related

Compiling Android for the Epic.

Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.
+1 on this.
+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel
I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!
I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...
yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.

[KERNELS] Looking for Kernel Developers for Kernel Manager!

Hey everyone! I wanted to introduce a new project with a very simple but ambitious goal: create a place where all kernel developers can submit kernels easily and reach a much wider audience with ease.
Using Kernel Manager to flash kernels takes less than 30 seconds, generally, and it is extremely simple for end-users to find a kernel, filter by kernel features (BFS, CFS, HAVS, SBC, etc) download/install kernels, and submit ratings for their favorites.
We need from kernel developers like YOU! Submitting a kernel to Kernel Manager is totally free and we even provide hosting for you! Submitting kernels is easy, and kernel developers receive a FREE copy of Kernel Manager Pro when they submit a kernel to Kernel Manager!
If you use IRC, join us in freenode in #kernel-manager!
THIS LINK IS FOR KERNEL DEVELOPERS SPECIFICALLY! Go to http://kernels.teamw.in and register for an account! Once it's approved, you can easily enter new kernels, which immediately show up in the app. The app is currently available in the market.
Please feel free to provide me with any feedback you have, or feature requests in order to make this a great tool for all of android to utilize!
Should I submit my kernels to this? This guy is making dough off this which I have no issues with at all...
Just wanted some opinions from you guys...
If it makes easier for us to keep up with your work, then whynot?
How many other Dev's have starrted using?
It's like Rom Manager for kernels, no?
If this had other features developed into the app and happened to support kernel downloads it'd be one thing, but I will not be paying someone else so that I can have access to the kernels that originate here. I'll save my money for the kernel devs. That being said if others find value in this, or if the dev community thinks it will do some good I'm all for it.
I see a **** ton of people having problems and coming straight to you faux.
I say make em flash the old fashion way... it at least deters some of the noobs. Making it something where anyone can one click change kernels.... sounds like opening a big can of worms.
Just my 2¢.
Sent from my HTC Glacier using XDA App
I dont know, i would wait and see how it effects other kernel devs.
camalus said:
I see a **** ton of people having problems and coming straight to you faux.
I say make em flash the old fashion way... it at least deters some of the noobs. Making it something where anyone can one click change kernels.... sounds like opening a big can of worms.
Just my 2¢.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
+1 I would like to see less repitition in the forums of "help I'm bricked!" Then 3 posts from a senior member with some knowledge "oh I just had 2.5.1.2 installed or 3.0.0.5" then there's the others like (this still makes me laugh) my internets slow, must be the sim card! Lol. Sorry rant I think it'd be a good app if only available to more seasoned users to inhibit the amount of screw ups..
Sent from my HTC Glaciee using XDA Premium App
Faux you are the kernal king !!! thanks alot for all your cool kernals dude. but i would just submit one and see what happeneds !!!
Good idea, but I agree with the others posts. It would be helpful to have everything in one spot, even with older versions, but him making scratch on you, with you as basically free support?
Unless you want to get your name out there to more people, then go for it.
Thank you for everything so far and in the future.
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
option94 said:
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
Click to expand...
Click to collapse
Yeah good point... I will wait a bit and see how other kernel devs react to this...
Sent from my HTC Glacier using XDA App
darinmc said:
If this had other features developed into the app and happened to support kernel downloads it'd be one thing, but I will not be paying someone else so that I can have access to the kernels that originate here. I'll save my money for the kernel devs. That being said if others find value in this, or if the dev community thinks it will do some good I'm all for it.
Click to expand...
Click to collapse
Just to clarify something - it costs nothing for a dev to host a kernel, and it costs nothing for someone to download that kernel through the app.
Kernel Manager provides kernel devs a super easy way to distribute their work for free. Kernel Manager Lite can download and flash kernels for free, so I'm not sure why you feel like you need to pay for anything?
xdviper said:
If it makes easier for us to keep up with your work, then whynot?
How many other Dev's have starrted using?
It's like Rom Manager for kernels, no?
Click to expand...
Click to collapse
Currently we have 37 developers signed up and submitting kernels.
I make my kernels for ME but share them because it is the proper thing to do. Feel free to use them, host them whatever. I do not want to make any money off of them because I did NOTHING. If you want to make money off of them, or share them feel free. Depending on what you do, I will have more (or less) respect for you. But really, who cares. I respect shiznzul (so far), so have fun and good luck.
option94 said:
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
Click to expand...
Click to collapse
Shinzul,
How is this handled in your app?
ziggy34 said:
Shinzul,
How is this handled in your app?
Click to expand...
Click to collapse
The app only displays kernels that are your for your particular device so there's no chance of flashing a kernel that's for the wrong phone.
If there's any question about what type of phone you have (see: samsung phones...), it pops up a message asking you to confirm which of the options your phone is.
Shinzul said:
The app only displays kernels that are your for your particular device so there's no chance of flashing a kernel that's for the wrong phone.
If there's any question about what type of phone you have (see: samsung phones...), it pops up a message asking you to confirm which of the options your phone is.
Click to expand...
Click to collapse
What about seperating for different versions. We have two different Aosp formats... and two or three sense formats that we use on the 4g.
How does your app keep other kernels seperate so it doesn't screw up peoples phones?
That is the biggest issue I think most of us on the 4g see.
Sent from my HTC Glacier using XDA App
being that it's in the market there is always a chance it will become a paid app. I just don't want devs to become dependent on it, that's all. I like reading into what I'm doing, so I guess I should ask, is there a section for a changelog, install notes, etc?
darinmc said:
being that it's in the market there is always a chance it will become a paid app. I just don't want devs to become dependent on it, that's all. I like reading into what I'm doing, so I guess I should ask, is there a section for a changelog, install notes, etc?
Click to expand...
Click to collapse
There will always be a free version that provides access to the kernels. There is a free version (Lite) and a cost version (Pro) right now.
Pro will just have more features, but everyone will still be able to download+flash kernels for free if they like.
camalus said:
What about seperating for different versions. We have two different Aosp formats... and two or three sense formats that we use on the 4g.
How does your app keep other kernels seperate so it doesn't screw up peoples phones?
That is the biggest issue I think most of us on the 4g see.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I am going to add a confirmation on the android flavor (AOSP vs Sense). I might add a filter option for it, but it's difficult because that field is developer-input. There isn't a standard list.

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[HELP] Creating custom ROM

Hello everyone,
I've been on these forums for some time already, and have avidly watched the development of new ROMs and apps. But always only as a user.
I have now become interested in developing my own ROMs for the Xperia Play, and I would like to ask you some questions:
1) What programs and utilities exist for developing custom ROMs, and which one would you suggest for a beginner?
2) I myself have an r800i, but I would like my ROMs to work on the other models too, how difficult is that to do?
Thanks in advance,
Si1ver Shad0w
No idea how to do it myself but look here:
http://forum.xda-developers.com/showthread.php?t=1801690
Sent from my R800i using xda app-developers app
Its not that easy as creating your own bootlogo.
1. Make the name
2. The features mustnt be same, implent something different, something cool and useful, because if you make something that was already released like 2times, people doesnt care..
3. Use Android SDK
However you will need Ubuntu, but you need a knowledge how to do it. You cant just say from day one to day two "Hey i want to be famous! I make the best ROM!".. If you are stuck at this point and you arent modder or hacker, i woudnt recommend it doing.
Click "Thanks" if useful.
Sent from my R800i using xda app-developers app
wuby said:
Its not that easy as creating your own bootlogo.
1. Make the name
2. The features mustnt be same, implent something different, something cool and useful, because if you make something that was already released like 2times, people doesnt care..
3. Use Android SDK
However you will need Ubuntu, but you need a knowledge how to do it. You cant just say from day one to day two "Hey i want to be famous! I make the best ROM!".. If you are stuck at this point and you arent modder or hacker, i woudnt recommend it doing.
Click "Thanks" if useful.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
For the moment I won't be releasing anything, just want to tinker by myself and if it works out then maybe share it with the community.
I'm currently wanting to just modify the stock 2.3.4 ROM, so I don't think I will be needing the Android SDK. But apparently Android Kitchen needs a Unix environment to work, so I'm now downloading the latest Ubuntu and gonna put that on a virtual machine. =)
Also, I was wondering, I have seen some custom ROMs that can be installed even with a locked bootloader, how exactly is that done?

[Q] kinda would like to see some ICS help please?

Okay, so I've had i317 for about 4 months now, its a great phone. I would just love to see an ics 4.0.4 rom, be it stock or aosp,, aokp, etc for this device. The reason being is that there are alot of apps I used to use, such as UMA and a few others I cannot remember as of right now. Forgive me if this isn't the correct area to post the question lol. But can anyone possibly help me with my issue I'm having? A. ort or something would be ideal if possible.
On a side note: I have some prior knowledge with developing roms and getting them to work fully and such, like betas alphas and what not. just haven't gave much thought as to post on the forum untill now. So I'm not completely of the noob calibur so to speak.
Lastly, my final question, would anyone be interested in deving up a 100% pure custom 4.3 rom that is completely Pokemon themed right down to the contacts and dialer. I will include more detail upon request, also one that isn't 10.1 based or cm in general. The reason I say non cm based is because volume+ sound boost breaks the speaker and crackles pretty badly, and i am partialy deaf so the apk is much needed. Any help would be be very appreciated and id be eternally greatful.
ghost_user said:
Okay, so I've had i317 for about 4 months now, its a great phone. I would just love to see an ics 4.0.4 rom, be it stock or aosp,, aokp, etc for this device. The reason being is that there are alot of apps I used to use, such as UMA and a few others I cannot remember as of right now. Forgive me if this isn't the correct area to post the question lol. But can anyone possibly help me with my issue I'm having? A. ort or something would be ideal if possible.
On a side note: I have some prior knowledge with developing roms and getting them to work fully and such, like betas alphas and what not. just haven't gave much thought as to post on the forum untill now. So I'm not completely of the noob calibur so to speak.
Lastly, my final question, would anyone be interested in deving up a 100% pure custom 4.3 rom that is completely Pokemon themed right down to the contacts and dialer. I will include more detail upon request, also one that isn't 10.1 based or cm in general. The reason I say non cm based is because volume+ sound boost breaks the speaker and crackles pretty badly, and i am partialy deaf so the apk is much needed. Any help would be be very appreciated and id be eternally greatful.
Click to expand...
Click to collapse
It's not going to happen. The note 2 was shipped with 4.1.1 (or higher) so there is no 4.0 source for devs to work with.
Also, since pretty much every AOSP rom uses the CM Theme Manager, it's not that common to see themed roms (there are exceptions, but they tend to be lightly themed). Either find a CM theme to your liking or learn to theme your rom.
Sorry my friend...
You aren't the only one wanting it...
I'd even take a nice CM6 ROM for this device...
But as mentioned... It's just a dream... g
Sent from my GT-N7105 using XDA Premium 4 mobile app
jibust said:
It's not going to happen. The note 2 was shipped with 4.1.1 (or higher) so there is no 4.0 source for devs to work with.
Also, since pretty much every AOSP rom uses the CM Theme Manager, it's not that common to see themed roms (there are exceptions, but they tend to be lightly themed). Either find a CM theme to your liking or learn to theme your rom.[/QUOTE
Okay, well shoot. Could you at least tell me that the possibility to get an apk to adapt and work on a newer rom is possible? I ask this because the main reason for me asking a dream question is simply that I love the ultimate mobile armor apk. it is the best privacy apk ever thought of. It was removed for reasons unknown. Back when I had my S3 and I717, it worked on both. Sadly it will not stick on the rooms I run currently. (Cleanrom 5.0, lionrom 2.1, etc.) Could the scripts and such be altered somehow for it to be compatible? On the S3 I always ran cm10 and its stick. Any thoughts, ideas and suggestions that are helpful and or leading to an apk exactly similar to ultimate mobile armour would be greatly appreciated.
Click to expand...
Click to collapse
Apk alteration is very possible ...
The trick is finding a dev to work it out ...and since apps are owned by their respective creators ...you would need permission from him/her to use or modify the code...
And I've always said it ...
A few emails and pm's go a long way..
Hit up the dev and see what you can learn ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gregsarg said:
Apk alteration is very possible ...
The trick is finding a dev to work it out ...and since apps are owned by their respective creators ...you would need permission from him/her to use or modify the code...
And I've always said it ...
A few emails and pm's go a long way..
Hit up the dev and see what you can learn ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ive looked and searched and I've found nothing from the devs of this apk. Its been completely stricken from the web. What are my other options here as far as these apk Modding concerns go? I've found nothing for secure mobile sadly.
I see...
That being said ...it appears the app has been killed off for legal reasons ??
And lookout mobile is inferior how ??
Most of these security apps are monitored via 3rd party in addition to device activity ...
So it stands to reason that if your service for the apk is dead....it won't work anyway..
Best advice...pick an alternate and move forward....
Lookout and AVG are both exceptional ...and many others are available ..
Norton or Mccaffe possibly too...
Happy hunting ...and sorry I couldn't be of more help...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Categories

Resources