Related
Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..
Iperzampem0 said:
Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..
Click to expand...
Click to collapse
I'm up for that. I think if a lot of devs work together we can do it. I dunno about java experience
Sent from my HTC Desire using xda app-developers app
**** Shaky. He stopped all his job =(
But good idea and good luck
I can be your tester if you want of course
Sent from my Nexus One using Tapatalk 2
Iperzampem0 said:
Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..
Click to expand...
Click to collapse
can you please upload the system.img file somewhere? (or post the link to the original RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed file )
Here you go. It's ruu
http://hotfile.com/dl/158782968/55e3eb6/
Do we need 3.0 kernel ?
Sent from my Nexus One using Tapatalk 2
thanks..
i think shaky's Sense 4.0 alpha rom was based on Desire V dump.. dont know if it is worth the effort to start all over again...
Wait. It was based from One V rom. Not desire V
Sent from my Nexus One using Tapatalk 2
I agree with xeloni. Shaky was using the One V rom dump, which has the Adreno205 gpu!
The great thing of having a device with at least the same GPU is that we can have the right GPU files/drivers and maybe have a complete full gpu rendering. Obviously we gonna have to build a 3.0 kernel and proper cpu drivers...
Cmon dbasabe ! !
And shaky has almost finished thé kernel but he stopped all :/
After Imperzampemo, in this rom delete all useless appartement. Some ringtones. Fast and Light sense
Sent from my Nexus One using Tapatalk 2
i managed to extract system.img, it is 800mb after uncompressing...
one more thing, i couldn't extract the secure boot image. anyone know how to extract that?
xeloni said:
Cmon dbasabe ! !
And shaky has almost finished thé kernel but he stopped all :/
After Imperzampemo, in this rom delete all useless appartement. Some ringtones. Fast and Light sense
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Shaky has not stopped . He continues in silence and won't post on xda again. You better be following him on Twitter.
Also, dbasabe has left a long time ago
Sent from my HTC Desire using xda app-developers app
fake_japanese_guy said:
i managed to extract system.img, it is 800mb after uncompressing...
one more thing, i couldn't extract the secure boot image. anyone know how to extract that?
Click to expand...
Click to collapse
OK, but now the main thing is to extract all the content from system.img!
About boot_signed.img don't know yet.
Anyway I still have to install Linux on my pc, so I'm stuck as of now..
race55 said:
Shaky has not stopped . He continues in silence and won't post on xda again. You better be following him on Twitter.
Also, dbasabe has left a long time ago
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'm following him on twitter
If someone wants to add me look in m'y signature
Sent from my Nexus One using Tapatalk 2
Iperzampem0 said:
OK, but now the main thing is to extract all the content from system.img!
About boot_signed.img don't know yet.
Anyway I still have to install Linux on my pc, so I'm stuck as of now..
Click to expand...
Click to collapse
Virtual box
Sent from my Nexus One using Tapatalk 2
xeloni said:
I'm following him on twitter
If someone wants to add me look in m'y signature
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Does shaky have his twitter account protected?
Didn't realise he had quit xda until I read this. Another dev loss; reminds me of Medroid / Samuaz.
Sent from my Nexus One using xda app-developers app
xeloni said:
Virtual box
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yea, I'm using that but it's really slow and I have problems... wtf! I hate Linux.
cpm said:
Does shaky have his twitter account protected?
Didn't realise he had quit xda until I read this. Another dev loss; reminds me of Medroid / Samuaz.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
No itsnt protected
Sent from my Nexus One using Tapatalk 2
i managed to extract boot_secure.img also.. it had 256bytes of some security key on the beginning.. i had to tail it and then extract.
any way, after extracting, the system.img is more than 600mb.. we need to reduce it to less than 200mb to install to nexus one...
meanwhile im trying to boot with the kernel from the dump.. as of now, its not working.. kernel panic..
fake_japanese_guy said:
i managed to extract boot_secure.img also.. it had 256bytes of some security key on the beginning.. i had to tail it and then extract.
any way, after extracting, the system.img is more than 600mb.. we need to reduce it to less than 200mb to install to nexus one...
meanwhile im trying to boot with the kernel from the dump.. as of now, its not working.. kernel panic..
Click to expand...
Click to collapse
Try to boot with the kernel included in shaky rom
Sent from my Nexus One using Tapatalk 2
ill try that. but before that, need to find some applications to remove the the dump so that i can reduce the /system size to less than 200mb...
Does anyone have a link to the OTA update IAN76K from IAN76H? I know factory images are available for IAN76K, but I'm looking for the actual OTA file that was pushed to Nexus Q devices. Thanks in advance!
oldblue910 said:
Does anyone have a link to the OTA update IAN76K from IAN76H? I know factory images are available for IAN76K, but I'm looking for the actual OTA file that was pushed to Nexus Q devices. Thanks in advance!
Click to expand...
Click to collapse
I have this sneaking suspicion that the I/O Q's shipped with H loaded but K in the recovery or whatever. I noticed that mine had changed when i did a factory reset. I don't know for sure though. Doubt anybody is able to get a logcat at this point in time. Do you have a device with ian67 H installed?
animal24 said:
I have this sneaking suspicion that the I/O Q's shipped with H loaded but K in the recovery or whatever. I noticed that mine had changed when i did a factory reset. I don't know for sure though. Doubt anybody is able to get a logcat at this point in time. Do you have a device with ian67 H installed?
Click to expand...
Click to collapse
No. I don't own a Q actually. I operate a firmware repository for every Nexus device from the Nexus S onward. I mirror official factory images and OTA updates for posterity. The site is http://randomphantasmagoria.com. I just added a page for the NQ today and was looking to see if anyone had the OTA link so I could mirror it.
Sent from my Galaxy Nexus using Tapatalk 2
If anyone that has a NQ is willing to take about 30 minutes to assist: I'd like to find the IAN67K ota:
If you would like to help, here's what you can do:
Reflash IAN67K (if you are not already on stock, and you must be on stock to do this)
Root your device
Change the following lines in build.prop:
Code:
ro.build.date.utc=1339795569
ro.build.fingerprint=google/tungsten/phantasm:4.0.4/IAN67H/384240:user/release-keys
Check for updates
Post the name of the update zip it downloads
TheManii said:
If anyone that has a NQ is willing to take about 30 minutes to assist: I'd like to find the IAN67K ota:
If you would like to help, here's what you can do:
Reflash IAN67K (if you are not already on stock, and you must be on stock to do this)
Root your device
Change the following lines in build.prop:
Code:
ro.build.date.utc=1339795569
ro.build.fingerprint=google/tungsten/phantasm:4.0.4/IAN67H/384240:user/release-keys
Check for updates
Post the name of the update zip it downloads
Click to expand...
Click to collapse
I'll give it a try in a little while.
You might need to check adb logcat while doing the check for updates, as we do not have the actual URL for it, just giving the filename will only give the filename.
I'm not sure how setting up adb works on the NQ though, I assume it's like normal devices as it has a usb port(?)
(if you know how to set up adb you can skip to step 7)
Download platform tools
Download usb drivers
extract both packages
Turn on usb debugging (I dont know the exact steps to do this on the NQ)
Install the drivers if windows requests it (and I am assuming you are using windows)
go to where you extracted platform tools and do "adb logcat"
Check for updates, if there is one available then post the contents of logcat
If you are able to get that far you can just directly post the logcat if you do not know how to read it.
animal24 said:
I'll give it a try in a little while.
Click to expand...
Click to collapse
Any luck?
Sent from my Nexus 4 using Tapatalk 2
oldblue910 said:
Any luck?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
http://android.clients.google.com/p...gned-tungsten-IAN67K-from-IAN67H.29d5a723.zip
Booya!
You, sir, are the man! Thank you!
Sent from my Nexus 4 using Tapatalk 2
oldblue910 said:
You, sir, are the man! Thank you!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No problem. I wish I would have seen this thread months ago. I would have done it then. I don't get over to the Nexus Q forums too often.
Sent from my Nexus 7 using xda premium
Well we only realised that this works a couple days ago, unless you actually had a NQ with IAN67H the entire time
TheManii said:
Well we only realised that this works a couple days ago, unless you actually had a NQ with IAN67H the entire time
Click to expand...
Click to collapse
I don't ever remember seeing IAN67H. As far as I can remember its been "k". I really hope its not the last version we'll see...
Sent from my Nexus 7 using xda premium
Given the current (lack) of news on the NQ, it seems unlikely.
I dont even own one but I'd hope it does too.
Like a hypothetical merger of NQ type media streamers and google TVs into KLP like how ICS merged tablets and phones.
But I digress
Because we now have this information, I have created a Nexus Q page on the website to mirror the firmware.
oldblue910 said:
Because we now have this information, I have created a Nexus Q page on the website to mirror the firmware.
Click to expand...
Click to collapse
Nice! Glad I could contribute.
Sent from my Nexus 7 using xda premium
looks like very few things were updated. framework-res, hub broker,libwvstreamcontrol, all the stuff in /app is about 1.8 to 2k..
animal24 said:
looks like very few things were updated. framework-res, hub broker,libwvstreamcontrol, all the stuff in /app is about 1.8 to 2k..
Click to expand...
Click to collapse
Yeah it seems like a very minor update.
User facing changes:
Hubbroker.apk got updated (what is this? is it the NQ's launcher?)
Music2.apk got updated
Lib/frameworks/non user facing updates:
/system/bin/common_time
/system/framework/ext.jar
/system/framework/framework-res.apk
/system/vendor/lib/libWVStreamControlAPI_L1.so (WV as in widevine?)
and that's it, every other file is simply updating the timestamp.
OK, so maybe a dumb question, so bare with me here. I m new to the Q but not the android world.
How would us users who have a stock Q go about updating to this latest version. I am having issues with my Q after about 20 minutes and was hoping to give this a whirl and see if it fixes it.
-Kovs
Kovs said:
OK, so maybe a dumb question, so bare with me here. I m new to the Q but not the android world.
How would us users who have a stock Q go about updating to this latest version. I am having issues with my Q after about 20 minutes and was hoping to give this a whirl and see if it fixes it.
-Kovs
Click to expand...
Click to collapse
I can almost guarantee you have the latest version as its been around since I got the Q last July.
I have the same issue you have as well. I'm pretty sure its a Google back end thing and not a problem with the build. Although Google may release an update that fixes the problem.
Sent from my Nexus 7 using xda premium
The subject is on.
We are on the list but in the NS topic there is no full version rom.
Anybody knows anything?
Sensitivity said:
The subject is on.
We are on the lost but in the NS topic there is no full version rom.
Anybody knows anything?
Click to expand...
Click to collapse
I have a gnex but I remember seeing that someone ported it in the ns4g.
Its still under the name boot2gecko but you probably going to need to wait for a more stable version gets released. Right now I think its buggy with limited functions but has a radio.
I'm not 100% positive this is correct but I'm just trying to give some insight.
Sent from my Galaxy Nexus using Tapatalk 2
robogoflow said:
I have a gnex but I remember seeing that someone ported it in the ns4g.
Its still under the name boot2gecko but you probably going to need to wait for a more stable version gets released. Right now I think its buggy with limited functions but has a radio.
I'm not 100% positive this is correct but I'm just trying to give some insight.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi!
Firefox os did support Nexus S. Here is my method to put Firefox os into Nexus S.
1. Download ICS image from google, soju-imm76d-factory-ca4ae9ee.tgz
2. tar zxvf soju-imm76d-factory-ca4ae9ee.tgz
3. Press volume up + power key. Nexus S will get into fastboot mode.
4. run "./flash-all.sh" Nexus S will be flashed with ICS image
5. get into B2G code and run script "./config.sh nexus-s"
6. build image "./build.sh"
7. flash image "./flash.sh"
--
Keven
Sensitivity said:
The subject is on.
We are on the list but in the NS topic there is no full version rom.
Anybody knows anything?
Click to expand...
Click to collapse
Hi,
You can give this a try:
http://forum.xda-developers.com/showpost.php?p=40044238&postcount=112
Hi there,
Today I set up my machine to start building omni Rom for my Nexus 7 gsm (tilapia)
I followed the guide from the wiki for the Nexus 4 and changed it to suit the tilapia.
After I finished I got some errors about grouper Commons files missing so I guessed that the tilapia builds rely on the grouper(Nexus 7 wifi) and executed breakfast for grouper, too.
Afterwards the build started, however it gave me an error /warning to begin with
"device/asus/tilapia/omni.Dependencies file not found"
As mentioned before, the build started nevertheless.
Will this render my build useless or is it one of the warnings that might occur without harm?
If so, How can I fix it?
Sent from my Nexus 7 using xda app-developers app
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
dibblebill said:
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
Click to expand...
Click to collapse
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I've seen it said that you must have 4gb available, but I don't know. I can do a Tilapia build for you after Xmas if you like.
Sent from my Nexus 10
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
make core/java/android/
make packages/SystemUI/
make policy/src/com/android/internal/policy/impl/
make services/java/com/android/server/
Click to expand...
Click to collapse
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
punshkin said:
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
Click to expand...
Click to collapse
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
dibblebill said:
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
Click to expand...
Click to collapse
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Story runs thus.
I run a custom desktop with a 2nd generation Intel i7 at 3.06GHz (quad-core, Hyperthreading), 12GB triple-channel XMP RAM, and a good graphics card. 1.5TB hard drive. I have WIndows 7 on that. I procured, in exchange for beer to an adult of legal age, a 80GB, 7200RPM notebook HDD which I put Linux on, and build on that. I'm replacing that 80GB drive with a new 3.5" 1TB drive. 64MB of cache. I plan to give it a ccache of around 50GB. Since I boot into a full Linux installation, I get to use the full power of that CPU and RAM, and boy does compilling Android kick that CPU's ass.
well my build core failed (no make file)
I added 16Gb swap and run over night and see what happens
I'm not done with this yet
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
punshkin said:
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Click to expand...
Click to collapse
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
dibblebill said:
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
Click to expand...
Click to collapse
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
punshkin said:
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
Click to expand...
Click to collapse
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Tweakecho said:
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Click to expand...
Click to collapse
thank you, i just glanced over it but it seems very helpful
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
punshkin said:
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
Click to expand...
Click to collapse
do you clear before you build again? make clobber will clean up your "out" with out killing your build times to bad as far as i can tell. All you need to do is get the proprietary blobs for the grouper from either CM or Google and let them place themselves in the Vendor/asus/ directory and then you can make breakfast grouper to pull down the needed repos. my grouper specific stuff is only ~70 MB so it wont be to bad for your Hard drive i don't think. so you'd have to pull down some other radio stuff extra is about all.
I do think doing the builds together will double the size of the output as now you will have an OUT/product/Grouper as well as a OUT/product/Tiliapia... but i'm just making assumptions
If anything you could build them one at a time.
I'm sure i'll be corrected by one of the real dev's if i'm wrong...
EDIT: did some digging in to all the directories and it looks like mose of the stuff is already there for tiliapia in my repo so you should have the grouper stuff too.... i think.. lol
Hi Friends, I was wondering how to compile android from source for My MAKO Device ?
before anyone says that What the Heck ?? ____ I have been through many tutorials, unfortunatily those are for compiline CM which i am not able to clone on my Laptop due to some GIT access issue from my Workplace.
Further i followed the official documentation for compilind android on source.android.com and was able to bild the IMAGE but as soon as i flashed the Image My Nexus's scren got blank and nothing happened .
so, can someone please guide me on how to compile Android from Source (NO CM/ ETC.) for MAKO ..
Thanks in Advance.
AOSP (source.android.com) is android. Are you sure you compiled the right packages. That you included the prebuilts and everything?
Ya . I did everything step by step. And finally I got the images but after flashing the images on my N4 I got a blank screen after boot animation.
Do you have another link so that I can try that method !.
Sent from my Nexus 4 using XDA Free mobile app
gur-i said:
Ya . I did everything step by step. And finally I got the images but after flashing the images on my N4 I got a blank screen after boot animation.
Do you have another link so that I can try that method !.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Did you compile for the right device? I believe the guide on source.android.com is for the emulator.
Well they also have a device guide, which i followed , do i have to manually add device driver binaries as i did not do that as ot was not there in the guide.
Sent from my Nexus 4 using XDA Free mobile app
gur-i said:
Well they also have a device guide, which i followed , do i have to manually add device driver binaries as i did not do that as ot was not there in the guide.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
It is, maybe you should read it again to see if you haven't missed anything.
Sure SMillerNL, i will do it again and report back.
Another thing, is actually , when i compile the sorce, I get various images, bootloader.img, system.img, etc. So, How to make a flashable zip out of those, so i can test the rom on MultiRom on my device, rather than flashing from ground 0 , as nexus4 is my kinna daily driver mobile phone.
You have to run "make mako otapackage"