Related
Hello everyone
I like to know if there is any way to amplify the vibration of this device.
I searched several android applications, but nothing at all.
I enabled the root access on my W Galaxy, installed some advanced tools but have not yet managed a way to increase the vibration of the device.
Best Regards
renato3d said:
Hello everyone
I like to know if there is any way to amplify the vibration of this device.
I searched several android applications, but nothing at all.
I enabled the root access on my W Galaxy, installed some advanced tools but have not yet managed a way to increase the vibration of the device.
Best Regards
Click to expand...
Click to collapse
U can take a look at this app. Hope it helps.
http://www.xda-developers.com/windows-mobile/vibro-change-vibration-pattern-for-incoming-calls-sms-and-e-mail/
yewsiong said:
U can take a look at this app. Hope it helps.
http://www.xda-developers.com/windows-mobile/vibro-change-vibration-pattern-for-incoming-calls-sms-and-e-mail/
Click to expand...
Click to collapse
isn't this for winmo?
frnt said:
isn't this for winmo?
Click to expand...
Click to collapse
sorry~ my mistake~ LOL
Improve the vibration via Kernel configuration
yewsiong said:
sorry~ my mistake~ LOL
Click to expand...
Click to collapse
Hello people
After many searches and trying dozens of applications, one guy tell how I can make this improvement, but this level of programming is too high for me, but, here is the solution to increase the vibration of Galaxy W:
Response from Mr Chad Froebel (Google Play application developper):
You should be able to get it from samsung. I googled the specifications and it looks like it uses a qualcomm chip so the
vibration driver will most likely be at:
/arch/arm/mach-msm/msm_vibrator.c
You're going to want to get the kernel source, modify that file (there is a parameter called PMIC_VIBRATOR_LEVEL) and then compile a new kernel.
If you are unsure how to compile a kernel yourself, you may be able to contact someone who develops specifically for your device to compile one for you.
I would, but I do not have the device to test it on and I don't like to send out kernels that I haven't personally tested.
if it experienced programmer does not feel comfortable doing this adaptation, I imagine that I am a mere apprentice.
Nevertheless I am downloading the open source code available from Samsung and when able to do this modification safely post here for all
Who wants the source code of Samsung mobile phones, just download the template for your specic phone at the following site:
Denied permission to put the link of Samsung opensource phones sdk
* How I am still new in the forum I do not yet have permission to post the Samsung site that contains open source code available, but can easily find the official site or searching on google for opensource.samsung
Any help is welcome!
I'm no developer either, but I guess I'll give it a try later :-D
Sent from my GT-I8150 using Tapatalk 2
This phone will never die
Synthetic.nightmare
I created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM Synthetic.nightmare if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
I have modified Synthetic-nightmare's ICS kernel, to hopefully support B2G here is the link
reserved
Mine
EDIT: Making this my reserve
Synthetic.Nightmare said:
This "build process" is just you syncing your repositories. There's still a mountain to climb once you get past this. It seems your manifest is off. When adjusting it look for things it says it cannot fetch. From there check to see if you got the repos and revisions and whatnot written out correctly in the xml in your manifest.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
hmm i will look at that here is my manifest https://github.com/deadman96385/b2g-manifest/blob/master/default.xml
Very exciting! Thank You and good luck.
Fixed some errors
Ok i fixed all of the errors except the one in OP!
Holy crap this is awesome. I need to thank all the devs here for your hard work. This is just so amazing.
Sent from my Toasted Marshmallow using XDA
Looking good brother hopefully we will get this bad boy up and running soon...
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
b4d455b345t said:
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
Click to expand...
Click to collapse
Actual OS developed by Mozilla.
saranhai said:
Actual OS developed by Mozilla.
Click to expand...
Click to collapse
Ohhh shizzzz. :victory:
Our Glaciers would be able to rock 2 OSs (Android & Firefox) Can't wait.
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
THEindian said:
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
Click to expand...
Click to collapse
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Synthetic.Nightmare said:
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
deadman96385 said:
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Click to expand...
Click to collapse
Do you guys mind if i come on this project with you? This sounds very interesting...
I'll be downloading this at work tomorrow - 64 bit Xubuntu 11.10 (single boot), desktop, wired.
yeah this looks good, may have to give this one a crack in the near future
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
ggolemg said:
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
Click to expand...
Click to collapse
Just saw that on Cnet
Sent from my Dark JellyBellyG1 using xda app-developers app
Howdy dudes! Any news?
Developers Support Thread
What does that mean?
Quite literally, this thread is intended to support developers. I intend to help out anyone who needs a hand in an attempt to develop for the Galaxy Nexus, or any other phone but I'm going to reference my website with step by step instructions to get you through the beginning stages and comfortable with development. This will also cut down on the number of "noob questions".
Background:
My private messages and e-mail stay filled with usually the same questions. There are lots of people who have android phones and the excitement of owning them doesn't stop there. They want to learn how these other people are creating custom roms on their phone. Some people want a minimalism rom, pure AOSP with maybe one or two mods, such as reboot and status bar toggles, but otherwise want a stock setup. They browse around all these great roms but they are just too many mods for their taste. What do you do from there? You can request a developer release a version with only those two mods, and then wait for the end of time because it's not coming. Or you can compile your own rom from source code and have whatever mods you choose.
Rules:
1) No trolling. If someone appears to be a troll and everyone agrees they are a troll, leave it at that. NOT responding to a troll is the only way to defeat them so practice that rampid in this thread.
2) Anyone who knows an answer to a question posted, feel free to join in, the entire community including current developers should participate. This will only serve to strengthen the development community.
3) No question is too small. Everyone starts somewhere so if someone post asking what a terminal is, or how to find usb debugging in settings, do not discourage them from continuing to learn. There is no place for that and you will have become a troll. You will know it too because everyone will ignore your comments .
Get your start here:
http://source.android.com/source/initializing.html
This is google's own instruction but it's hard for some people just starting off to feel comfortable with. I have elaborated on this guide with an entire website aimed at educating people. Please visit here: http://www.dreamsforgotten.net Understand the site is very new, I have been working on it for a month or so, but it will grow and evolve as does this thread. Any questions that get tackled here that are repeated, and seem to affect many people, I will add the resolution to the website as well.
I do have ad sense on the website in an attempt to cover the hosting fees, there is no option to set up an account @ dreamsforgotten.net. Anyone is free to stop by and view it, and take from it what they need. So far I have enough instruction in place to get anyone who is using a supported development device (as well as sprint and verizon galaxy nexi lol) compiling from source rather quickly.
Please leave me feedback on what you would like to see addressed in the future, and consider this the support thread. Dreamsforgotten.net is for you to get a step by step instruction on setting up an environment, this thread is for you to expand that and get assistance when you hit a snag in the road. Thanks guys and I'll be responding to questions as I get time. Enjoy.
Okay im planning on Porting Rasbean Jelly to the Toroplus variant as Dreams and others from the Black Bean thread know. Just some questions.. Ubuntu 12.10 was just released and that is what i am planning on installing since it now supports my laptop. Will that be sufficient? I remember hearing some issues with compiling on it. Also how much space should i dedicate to the install? I planned on dedicating around 250GB but all im doing is syncing Rascarlo's git with his permission of course and then adding the necesseties for the toroplus (if thats even what im needing to do). And compiling? Do i honestly need that much space? Also will i need Swap to help my Laptop build? It has 6GB's of RAM and i hear the Minimum for building is around 16GB's otherwise it will take quite a while. Any insight would be great
ÜBER™ said:
Okay im planning on Porting Rasbean Jelly to the Toroplus variant as Dreams and others from the Black Bean thread know. Just some questions.. Ubuntu 12.10 was just released and that is what i am planning on installing since it now supports my laptop. Will that be sufficient? I remember hearing some issues with compiling on it. Also how much space should i dedicate to the install? I planned on dedicating around 250GB but all im doing is syncing Rascarlo's git with his permission of course and then adding the necesseties for the toroplus (if thats even what im needing to do). And compiling? Do i honestly need that much space? Also will i need Swap to help my Laptop build? It has 6GB's of RAM and i hear the Minimum for building is around 16GB's otherwise it will take quite a while. Any insight would be great
Click to expand...
Click to collapse
I already spoke with you but i recommend two hundred gigs really two fifty minimum hdd. I roll with 8 gigs but compile time is horrendous since jelly bean. I'm sure almost all distributions can be set up to develop debian arch mint ubuntu etc but each have to be done so desperately. I'll work on write ups for each java 6 being the biggest hurdle for most new developers.
Sent from my Galaxy Nexus using Tapatalk 2
dreamsforgotten said:
I already spoke with you but i recommend two hundred gigs really two fifty minimum hdd. I roll with 8 gigs but compile time is horrendous since jelly bean. I'm sure almost all distributions can be set up to develop debian arch mint ubuntu etc but each have to be done so desperately. I'll work on write ups for each java 6 being the biggest hurdle for most new developers.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How long do you think it'll take? Using 6GB of RAM. And I have a quad core amd at 2.0ghz?
Sent From My N7 via Tapatalk
ÜBER™ said:
How long do you think it'll take? Using 6GB of RAM. And I have a quad core amd at 2.0ghz?
Sent From My N7 via Tapatalk
Click to expand...
Click to collapse
8 gig 1.2 gig quad core 8 hours. Use ccache when you build I would go 50 gigs
Sent from my Galaxy Nexus using Tapatalk 2
dreamsforgotten said:
8 gig 1.2 gig quad core 8 hours. Use ccache when you build I would go 50 gigs
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You'll have to explain that.
That's quite ridiculous... now in doubting it... I don't think it'll handle that stress... it is a laptop I have a fan for it and it has a pretty good exhaust fan but that's still ass long as time.
Sent From My Toro+ via Tapatalk
ÜBER™ said:
You'll have to explain that.
Sent From My Toro+ via Tapatalk
Click to expand...
Click to collapse
Yeah on the build android page there are directions for setting up ccache you have to add a line to your bash rc and run a command before you build. When I head home, I'll add a page in tutorials explaining that further, it was next on the list.
Sent from my Galaxy Nexus using Tapatalk 2
Talking to motcher he says he uses ccache and with his dualcore 1.7ghz and 2 GB of RAM it takes him 3hrs and 1.5 after he builds ccache.
Sent From My Toro+ via Tapatalk
Great idea man.
I want to add status bar toggle and navigator key re–map in Stock ROM.
I have tried system ui.apk & framework.apk decompile, but somewhere struck.
Can you please help to achieve the goal
Sent from my Galaxy Nexus
8 hours!?
mine builds in 10 minutes after CCACHE, and 30-40 before....
ÜBER™ said:
Talking to motcher he says he uses ccache and with his dualcore 1.7ghz and 2 GB of RAM it takes him 3hrs and 1.5 after he builds ccache.
Sent From My Toro+ via Tapatalk
Click to expand...
Click to collapse
Instructions added here http://dreamsforgotten.net/ccahce.html Note the actual ccache folder difference in the command? Changed in JB.
sendhiloo7 said:
Great idea man.
I want to add status bar toggle and navigator key re–map in Stock ROM.
I have tried system ui.apk & framework.apk decompile, but somewhere struck.
Can you please help to achieve the goal
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Galaxy Nexus, I'd say don't do that. If you have a machine even remotely capable put you a linux partition, through VM if you must , and compile you a version from source. With step by step instructions those too mods wouldn't be that hard. First off, by decompiling you have to decompile both stock rom and a rom with the features you want. Then you have to put those changes in your file in smali which is bytecode aka machine readable. If you know my history, you know I have done this before with the Nexus S because the mod I wanted to copy was samsung proprietary code but in no other circumstance would I want to do that. You need to sync google source, add in the files for your phone, and then do some searching on github to find the two mods your wanting. You copy that code into your source and compile. It's more difficult than that and I just hit you with a lot so start at it, and when you reach a snag come back for help. But...if you must do this in smali...this is what you missing based on what you say you already started. decompile systemui.apk decompile frameworks/base decompile settings.apk. Find (whatever rom you find source for your mod) their version of the file rom control.apk. Copy that in your zip (obviously last step). Diff merge your stock decompiled 3 files against the rom's smali files. Same way as source, use github to find the affected lines of code. Copy over all code, all images, all xml files that are missing. Fix what's there and altered. Settings.apk is going to have a file in src/com/android/settings/foo/foo/ called settings.smali. This file is where your mods in rom control are going to be able to speak to mods you just did to the frameworks/base.
Thanks a ton dreams adrenaline is pumping hope I can get some sleep super excited for tomorrow.
Sent From My N7 via Tapatalk
ÜBER™ said:
Thanks a ton dreams adrenaline is pumping hope I can get some sleep super excited for tomorrow.
Sent From My N7 via Tapatalk
Click to expand...
Click to collapse
I seen how much my theme guides were referenced this is bigger and a huge load but much needed. Your quite welcome.
Sent from my Galaxy Nexus using Tapatalk 2
dreamsforgotten said:
Instructions added here http://dreamsforgotten.net/ccahce.html Note the actual ccache folder difference in the command? Changed in JB.
Galaxy Nexus, I'd say don't do that. If you have a machine even remotely capable put you a linux partition, through VM if you must , and compile you a version from source. With step by step instructions those too mods wouldn't be that hard. First off, by decompiling you have to decompile both stock rom and a rom with the features you want. Then you have to put those changes in your file in smali which is bytecode aka machine readable. If you know my history, you know I have done this before with the Nexus S because the mod I wanted to copy was samsung proprietary code but in no other circumstance would I want to do that. You need to sync google source, add in the files for your phone, and then do some searching on github to find the two mods your wanting. You copy that code into your source and compile. It's more difficult than that and I just hit you with a lot so start at it, and when you reach a snag come back for help. But...if you must do this in smali...this is what you missing based on what you say you already started. decompile systemui.apk decompile frameworks/base decompile settings.apk. Find (whatever rom you find source for your mod) their version of the file rom control.apk. Copy that in your zip (obviously last step). Diff merge your stock decompiled 3 files against the rom's smali files. Same way as source, use github to find the affected lines of code. Copy over all code, all images, all xml files that are missing. Fix what's there and altered. Settings.apk is going to have a file in src/com/android/settings/foo/foo/ called settings.smali. This file is where your mods in rom control are going to be able to speak to mods you just did to the frameworks/base.
Click to expand...
Click to collapse
Ok. its little bit hard to understand :crying: . Ok first i will build the VM & compile from sourece.. Then let you know
sendhiloo7 said:
Ok. its little bit hard to understand :crying: . Ok first i will build the VM & compile from sourece.. Then let you know
Click to expand...
Click to collapse
No problem, you start the work and I'll help where needed. Goto my website and use google for the VM. That should get you to where you are ready to build. Once you get there I'll help you with the options to both find the source code changes for your mods, and incorporate them into your source code.
dreamsforgotten said:
No problem, you start the work and I'll help where needed. Goto my website and use google for the VM. That should get you to where you are ready to build. Once you get there I'll help you with the options to both find the source code changes for your mods, and incorporate them into your source code.
Click to expand...
Click to collapse
Thanks
Sent from my Galaxy Nexus
Anybody have experience with Ubuntu 12.x and building android? Ran into an issue with repo. Trying to init the repo i want to sync it spits out the error 23: error : Python not found. Or something similar I forget exactly. The only thing Google brought up was the fact that I either have the wrong Python version or it is not in my shell path.
Sent From My Toro+ via Tapatalk
ubuntu 12.04 64bit: http://forum.xda-developers.com/showthread.php?t=1863547
its all you need. just replace the repo down there with rasbean's or whatever you want to compile. 12.04 has been a terrible pain in the ass for me, at some point i had to revert back to 11. but back then i couldnt find a nice and compact manual, so this one should guide you through.
molesarecoming said:
ubuntu 12.04 64bit: http://forum.xda-developers.com/showthread.php?t=1863547
its all you need. just replace the repo down there with rasbean's or whatever you want to compile. 12.04 has been a terrible pain in the ass for me, at some point i had to revert back to 11. but back then i couldnt find a nice and compact manual, so this one should guide you through.
Click to expand...
Click to collapse
Yeah that's what I feared... didn't feel like having to reinstall... I've been using 12.10 not .04 I know motcher uses 12.04 just fine. Going to get a bootable for it hopefully it likes my laptop.
Sent From My Toro+ via Tapatalk
I prefer debian over ubuntu now, with any distro that don't work with you pc out the box you probably need a proprietary kernel version. If you have a lap top that sound doesn't work you'll def need one. Additional files may need to be loaded for Wi-Fi support as well. All of these have pretty easy guides to get the job done. Be sure to set Linux up completely before establishing the build environment.
Sent from my Galaxy Nexus using Tapatalk 2
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.
How many people are tired of not seeing any love for this awesome little device? Well I made sure to change that
Yes, you read that right. The Rugby Smart is officially supported by VanirAOSP.
Now, on to the boring part:
DO NOT FLASH TO THE GALAXY W OR GALAXY S +
Now that that's taken care of, on with the post.
What's working:
- Data
- MMS
- Calling
- Bluetooth
- Updater
- WiFi
- Vsync
- init.d
(more as I remember/fix stuff)
;
What's broken:
- Internal SD (Unfortunately this is a major grievance and is not isolated to the apache. This is a WIP fix)
- Camera (The setup on this is a b!%ch, I'm still working on it)
- USB tethering (Not sure why this one has to be difficult)
- Screenshots (Tied to SD bug)
And since this is official, We don't need a ROM changelog
Credits
Team VanirAOSP for providing the opportunity for officiated support
arco68 for providing the base code needed for source. building
NuclearMistake and DHOMD for hosting nightlies
grumpyspud for his thirst for more. Thanks for testing unofficially
Links:
Google +: VanirAOSP
Official Webpage: Vaniir
Nightlies:Apache NIGHTLIES
Thirst for more?
I got props omg.
You went out of your way to get the nightlies, so yes .
How are you liking it so far?
I goofed with the 1017 nightly for a little on my break.
Titanium backup actually loaded and kept my location of my folder in the physical SD card. It's never done that till this nightly.
Its way more smoother. What on the changelog (on nuke) made it smoother?
The display drivers from arco didn't agree with their sources so we're using the OpenSEMC one
[/COLOR]Good deal. The gallery, screen print, andcamera issue keep this one from being a Daily driver.
I make a backup of Kemo's cm 9 when I load ur nightlies. If you need me to test things let me know.
I am a decent blackbox tester not a coder.
once the sd issue is fixed the gallery and screenshots should come back to normal. The camera is mainly isolated around the kernel though.
Motorhead1991 said:
once the sd issue is fixed the gallery and screenshots should come back to normal. The camera is mainly isolated around the kernel though.
Click to expand...
Click to collapse
changelogs... until i see control f motorhead. No broken things are getting fixed right?
Just wondering how to read what is being changed.
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
grumpyspud said:
changelogs... until i see control f motorhead. No broken things are getting fixed right?
Just wondering how to read what is being changed.
Click to expand...
Click to collapse
The way their changelogs are set up makes reading them difficult, but all the changes that are specific to the apache I test on local builds before pushing to the main stream.
Heroata said:
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
Click to expand...
Click to collapse
That's because it's not a Wonder, it is a very close relative of it. It's been on these boards longer than you've been a member here .
And?
Camera's still broken, from what I can see so is SD. They're still digging for the SD thing.
Heroata said:
Wow so good. How is offical? And pic is not galaxy wonder
Galaksi Wonder Candır.
Click to expand...
Click to collapse
Its of galaxy rugby smart, a variant of galaxy w (AT & T)
Any news. The thread has been silent for well over a month.
I'm still fixing stuff and nightlies should still be coming out.
So, i guess we should forget about getting a fully working ROM for our beloved device?
Yea the last nightly was in November 2013. I think its a dead phone.
Sent from my SGH-I337 using Tapatalk
It's not dead, just on hold. Moving to CAF drivers requires major kernel updates that I haven't done yet
The download links for the ROM seem to be dead. They are leading me to a 404 error fire truck...
Sent from my SGH-I847 using XDA Free mobile app