Related
**Last update! This thread will (shortly) be locked, and a new one will be posted With Galaxian-Soup ICS Alpha 2
Check back in a few hours!
**Update, this tread will be retired and locked come this Thursday 1/5/2012
Read between the lines, and you will see that a brand new thread in its place will be posted, complete with a yummy new alpha of ICS for our dedicated fans to enjoy... We thank you for your patience, after this alpha goes out we believe tere will be more frequent releases and postings
Stay tuned, but from what I've seen so far we have many surprises in store for our next release, and you, is ICS nirvana just around the corner? Check back on thursday!
Please don't take this to mean we've fixed every outstanding bug, but we have made major core improvements, and fixed some of the big "items"
We are seaking anyone with expeirence working HAL's and drivers.. if you are interested please PM me.
TTFN!!
** Update ** Work around for voice search
It appears that voice search is broken in several AOSP roms, during my research I managed to get voice search working, however its the older version (prior to ICS). So far it seems to work fine!
So until Google fixes (or we do hah) do this to get voice search to work
Download
Voice_Search_2.1.4
Go to the location the this file was downloaded and from a terminal (linux/mac) or the command prompt (windows)
Code:
adb shell
su (if not root)
rm /system/app/VoiceSearch.apk
reboot
Then side load adb Voice_Search_2.1.4
Code:
adb install Voice_Search_2.1.4.apk
After the install click on the microphone icon near search at the top left of the home screen, accept the permissions (you have to do this a few times, 3 by my count), don't panic if it asks a few times, it does stick.
Enjoy!
** Update** Happy New Year XDA and esp our friends with the Galaxy Tab 8.9! is this the year of the droid? We shall see!
Hey everyone I wanted to give everyone an update and general goings on! Im sorry to inform you that there will not be a New Years alpha, but we will have something for you all very soon after.
Here is a taste of what early 2012 will bring to Alpha 2.
1. We have decided to use ASOP source rather than Cyanogen Mod, this is primarily why there hasn't been a new release since xmas. After reviewing some of the initial bugs, and reflecting on what we accomplished in under 4 days, we decided we wanted the focus of this rom to become "best in breed" optimized for the Galaxy Tab 8.9. Meaning we are going to cherry pick the best features of both to create the best possible experience, with the lightest footprint, and most importantly stock ICS launcher! NoWiz, no Trebuchet. So far it has yielded very positive results.
2. Moving to ASOP and stock launcher has fixed one of the big bugs, automatic home screen orientation. I know more than a few of you were hoping this would be resolved fast, well there.. happy now?
3. MTD
4. General cleanup and optimizations have resulted in improved launcher response, it feels more fluid and less laggy...
5. Our repo is nearly finished, we are just ironing out some manifest bugs, when alpha2 arrives, so will our git links!
6. We have chosen a team name! Galaxian-Soup!
Thanks for supporting us, and we look forward to celebrating a "Droid 2012".
In the spirit of openness, if you would like to use our rom in your work please credit us in your OP and release notes. Our git repo should be up soon.
***Update*** Xmas Dinner Edition ***
Updated links to a 1.1 version, I added the livewallpaper.apks and re-zipped, no other changes.
and a newer version of Google Apps, seems to be more stable, but I've only been using it an hour, let us know!
Good Morning and Merry Christmas!
Is there something in your stocking for your GT7310? Well Santa Clause (in the form of _Motely, nycbjr, poisike, termleech (still need a team name!)) is delivering the first public alpha!
This build has been tested on the 7310 (Gtab 8.9 wifi, no 3g), and 7300 with no 3g (3g is being looked at).
Standard YMMV tag: You are flashing this at your own risk, make a nandroid backup first! If this breaks your tab we are NOT responsible.. now go play and have fun!
ICYXMAS-p5wifi-alpha1.1-cwm
icyGapps V2
Alpha V1 - ICYXMAS!
ICS 4.0.3_r1 vanilla
Rooted, deodexed,
Includes motley kernel v2e beta (see his thread for git details)
WiFi, GPS, Bluetooth
Installation:
In CWM recovery, clear your data/factory reset
Clear the dalvik cache (under advanced, or under the wipe menu in overcome cwm)
Flash the provided zip using CWM recovery
Flash gapps from CWM recovery
Bootup and setup your Google account
Install cpu control of choice, and set to interactive governor (this is required!)
*tested SetCPU, No-frills CPU control, and Antuantu.
Give it a chance, this is a deodexed ROM and will boot slow the first time and when you use apps the first time.
Doesn't work/Limitations:
WiFi-only, but 3G will be looked at for a future version (no ETA at the moment)
Camera doesn't work, don't know when or if it can be fixed.
Some video limitations, youtube HD vids not working. Some stuttering will occur until we get the kinks out.
Charger screen doesn't look correct when you plugin without booting up (charging status)
Voice search doesn't work - May have something to do with this error:
W/PackageManager(257): Failure retrieving resources forcom.google.android.voicesearch: Resource ID #0x0
Probably more that we haven't listed, this is an alpha - please let us know.
Team members:
nycbjr - project manager, dev (first working build), testing/troubleshooting
motley - lead dev, p5 device tree, final build, kernel development
poisike - pioneer testing with other tegra ICS ROMs, testing/troubleshooting
termleech - testing
Credits:
Google - for the releasing the OS
Cyanogen Mod Team - for their awesome git repo and developers. We used the p4 device tree as a starting point.
We would like to offer our p5 device if they are interested.
Samsung for the awesome device and kernel source (for HC 3.1 at least)
digetx - for pointing us in the right direction on the green frame buffer fix!
alterbridge - for his CWM Recovery port for 73xx.
JaeCar99 - for the sweet "Blue Hallway" bootanimation
I'm looking forward to a fully working ICS rom But a good thing takes time. Keep up the good work, guys!
great to see this development start
Sent from my HTC Incredible S using Tapatalk
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
termleech said:
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
Click to expand...
Click to collapse
I would never turn down any help, I'm very new at this (long time sysadmin, but only been a droid head since march hah).
Only caveat is you will need approval from motley before I can release anything to you, for now you can PM me and I will give you my aim/gchat and offline email, but I think we should setup an IRC, or aim/gmail chat to make this go faster.
As this is coming from CM9 sources I need to contact them too, I don't want to flub any licensing issues, etc, and maybe they will want to help, or us to help them!
Awesome! Thanks fellers!
great work
_motley said:
As far as WiFi, the P4 (Galaxy 10.1) uses a broadcom 4329 and we (the P5) uses the newer 4330. This is where the challenge will come it. When I get a better look at the Android code and have a flash up and running, hopefully it will become clear if something needs to be done on the kernel side or the Android side. If we start making good progress, we will need to get a git setup for our P5 stuff so we can share changes and files etc.
Click to expand...
Click to collapse
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
this is awesome guys.. after the posts yesterday and staying up till 3:Am , I got the sucker booting.. of course that was it though. Great to see this post today.. Sounds like it's not too far off.. at least for me wifi would be the only thing left that's important since I havent touched the camera app or bluetooth yet.
poisike said:
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
Click to expand...
Click to collapse
right, I'm going back over the source, and the board config, some wifi stuff seems commented out. I know I need to get on irc.. but work interjects lol..
for the record on linux to use broadcom it has to extract the firmware for the card, I don't think it has to for droid as in this case the firmware is provided to us. I should probably stop spinning my wheels and go back and read/learn more about how android treats these things.
I am all ears however, anyone with debugging exp can have the rom with permission to use the kernel from motly.
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
ok thanks I was looking at the source on my build system remotely, and the drive went oiffine, I think my ssd is going, so I'm going to get a new on on the way home. pisses me off!
Great work!
I'm seeing forward to try this out.
Gesendet von meinem GT-P7300 mit Tapatalk
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Well other than the green screen affect, wifi, camera,bluethooth this thing really runs well.
HC was a pig for memory, as I noted on my Acer when I ran ICS for a bit, memory mamagment is hugely improved over honeycomb, I never had more than 200mb free on a regular basis, with ICS its well over 400mb.
and the thing really cooks along, I snap in and out of screens really fast, and angry birds works! haha
I will spend some time tonight on wifi, and making a new build.
poisike I'll setup irc tonight, I may have to rebuild the macpro, who knew running an os other than apple would cause a problem lol..
_motley said:
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Click to expand...
Click to collapse
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
This is great news!! Once the wifi is working, I'll be using this as my daily driver. Will this be a completely AOSP project or still based on TouchWiz. I wish I could have stock e-mail, calendar, etc.
Excellent news! I will be waiting patiently....
Asop only! "Don't wiz on my ICS"
Sent from my SGH-I777 using xda premium
nycbjr said:
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
Click to expand...
Click to collapse
That sounds like it is just the zImage binary for their build, I think I remember seeing it there too. It won't do me any good. Sounds good about the repo. I can still browse the repos to look at code as necessary for the time being. Glad to hear that the OC is is still working good.
I just sent poisike a 3G kernel with the touchscreen fix so he can start working on that end.
"Don't wiz on my ICS!" haha
UPDATE: PDROID NOW AVAILABLE VIA BOTBREW:
http://forum.xda-developers.com/showpost.php?p=26033156&postcount=10
First, for those who haven't heard about it:
PDroid
PDroid ICS Port
At this point, as far as I can tell, PDroid is only available as a patchset, not in any rom.
It looks like it is a lot more powerful than CM Permission Management.
The purpose of this poll is so Vibrant users can show interest in a rom with PDroid built in, hopefully motivating rom devs to add it.
I'll check this out tonight - looks interesting.
jellette said:
I'll check this out tonight - looks interesting.
Click to expand...
Click to collapse
I'm not set up to develop at present, but I'll try any CM or ICS open-source rom that has this built-in, or an open-source zip to hot-patch it into said roms.
Yeah pdroid looks awesome! I asked about this in slim forum and cm forum somewhere around here but got no love lol... its really awesome permission management and if they add a firewall it would be a must need app that I would love to buy... you can use it with droidwall but it has leaks and allows access before it loads up on reboot... pdroid could block that from the start if it had a firewall incorporated tho... I look forward to the development of this awesome app.
Looks like we might get a try ourselves with an ics patcher in the not so far off future
Sent from my SGH-T959 using XDA
An ICS patch does appear to be in the works.
As for CM, you're right, it will never have PDroid, and I'm really beginning to wonder if they will even bring any permission management into CM9. If you look at the PDroid patch, it's not a huge amount of code, meaning if Google wanted android to allow privacy, they would have added it long ago. But the frankly rather seedy business model of Google and many "free" app writers and Facebook is the harvesting and selling of personal information, and they apparently threatened to cut CM off from Market access if they added strong privacy.
Clearly the long-term solution is Google-free phones running Debian or Ubuntu, but until then, there's PDroid.
Pdroid Linux patcher ported and working for aokp and cm9
Sent from my SGH-T959 using XDA
c-pimp said:
Pdroid Linux patcher ported and working for aokp and cm9
Click to expand...
Click to collapse
Nice. Where?
Pdroid working for AOKP and CM9
PDroid is finally available for AOKP and CM9 on T959 Vibrant via botbrew. Follow instructions at http://forum.xda-developers.com/showpost.php?p=24934484&postcount=123 big thanks to mateorod for porting it over.
Hey guys-
UPDATE 6-5-12
I haven't had any requests for updated packages except for AOKP, so I can only confirm that AOKP Build 40 and CM7rc2 are currently supported! Any other ROMS are at your own risk! If you would like a ROM for vibrant or any other device to be supported, please post a request.
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button.
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
New!
android-framework-pdroid-cm7.2final
For CM7.2 Final!
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!
I confirm this is working with the 5-12 CM9 nightly. Thanks to mateorod and everyone he thanks in the post above!
Thanks, cashmundy. The problem was that cm9 has a weird naming convention for just your device, at least unique as far as I have seen.
I just changed the package to reflect your arch.conf.
So thanks very much for testing and finding the problem. I am pretty sure everything is OK now, but let me know!
Still on CM9. Did a reset, installed botbrew and your repo, and I now have no pdroid package.
As expected, botbrew fetched the CM9 props on install
, except that it down-cased the model to "sgh-t959".
arch.conf:
arch all 10
arch any 20
arch noarch 30
arch armeabi 100
arch armeabi-v7a 110
arch sgh-t959 120
build.props:
ro.product.model=SGH-T959
ro.product.brand=samsung
ro.product.name=SGH-T959
ro.product.device=SGH-T959
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
Okay man. I took out the sgh-t959 package because I thought you said cm9 had vibranttmd as arch.
Are you saying that it changes whether or not you install cm9 as an update? Cause I don't see how that would be.
I am going to make it so Botbrew has cm9 packages for sgh-t959 and vibrantmtd. We'll sort it out for good later tonight when I have some time.
Thanks for your time and effort testing this stuff!
CM7 has vibrantmtd as ....device and SGH-T959 as ....model. CM9 has SGH-T959 as both model and device, as does AOKP. If you (or BotBrew) could use model instead of device, it might work well.
What happened before was I tried CM9 over CM7 without a reset. BotBrew didn't catch the upgrade, and so kept the conf from CM7. When I reset and then installed BotBrew, it found the new props and configured accordingly. A hook in BotBrew to check the current rom on startup and reconfigure itself on flashes would be a good thing.
I'm currently showing all three packages, version -9.
One minor note: somewhere you specify the BotBrew refresh button as being on the top right. On my phone it is always on the bottom left. Maybe more vibrant weirdness.
Final random thought: I'm not very impressed with CM9. It has some real drawbacks (the keyboard for example).
CM7 is still overall a lot better (to me) and if PDroid ever makes it there, I'll test it.
Well, I am still considering about cm7. Let me see.
Botbrew does has services you can turn on to configure at boot, as well as several ways it detects flashes, although most of those are centered around packages or the terminal.
But thanks for those tips, there is definitely some weirdness going on with the vibrant that I haven't seen elsewhere, but is good to know about because it could resurface in other devices.
But yeah, for instance, you could use light pad to turn your sdcard into a web server, and host websites off of it, so that's one of the services options.
There is honestly a world of stuff in the repo already, and he's about to add debian INSIDE android.
Crazy. Thanks, cashmundy. I will look into cm7.
Very cool.
I think I'll try AOKP again when a new build is out, and test the patch there.
One thing that would be useful would be a white-hat app which would request all permissions, gather all possible data, and display it. As it stands, we have to take it on faith that pdroid, droidwall etc actually work.
For the long term, I am very much hoping for Debian instead of android.
mateorod said:
Hey guys-
Most everyone in this thread I already know from the port thread. I was looking for a good place to put out this info. Glad I didn't start another thread already!
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button at top right!
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!
Click to expand...
Click to collapse
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
The Vibrant is I think the most recent device, and the BandN Nook is supported,
so I expect the Kindle will be someday.
gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
If you run cm9 or aokp, I can take care of you.
Post your services, core, and services.jar plus build.prop at my packages thread so we keep this vibrant only.
Thanks for your interest.
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Hi,
I am trying to download omnirom for my device from dl (dot) omnirom (dot) org/hammerhead however it lists no builds. All the other directories are empty for me as well. Is anyone experiencing this issue?
I have attached a screenshot.
Here is the same issue, too.
I'm waiting for the nexxt OmniKk nightly, last one was 04.17.
Same here
Neither changelog and download link
Same here...???
I need lastest omnirom 4.4.4 zip for s3...any link?
polmone said:
Same here...
I need lastest omnirom 4.4.4 zip for s3...any link?
Click to expand...
Click to collapse
What's wrong with Omnirom, no one knows for something?
3 Days later: Same problem here.
I was away for most of last week (weather too nice), and also don't handle the downloads directory (other people do that).
I have no idea what's going on... We've had issues in the past with running out of space causing bogus builds, but this... It's new.
Perhaps the cleanup bot responsible for trying to avoid running out of space had a bug and got overzealous...
Entropy512 said:
I was away for most of last week (weather too nice), and also don't handle the downloads directory (other people do that).
I have no idea what's going on... We've had issues in the past with running out of space causing bogus builds, but this... It's new.
Perhaps the cleanup bot responsible for trying to avoid running out of space had a bug and got overzealous...
Click to expand...
Click to collapse
Since yesterday the weather is also fine here, but tomorrow it will rain again.
Could you please tell the right people notice to fix the error, Entropy512.
We want to download and / or update the nice system and there is no way since 2015.04.17.. :fingers-crossed:
MichaBit said:
Since yesterday the weather is also fine here, but tomorrow it will rain again.
Could you please tell the right people notice to fix the error, Entropy512.
We want to download and / or update the nice system and there is no way since 2015.04.17.. :fingers-crossed:
Click to expand...
Click to collapse
Seems like the cleanup bot was overzealous, it deleted everything older than X weeks old... Plodey was planning on having 5.1 nightlies started by now but the CAF ifdefing nightmare is taking far longer to finish than anticipated.
I've asked plodey to kick off another build cycle for 4.4, although I just realized there's a wpa_supplicant security patch we should stick in there first.
Entropy512 said:
Seems like the cleanup bot was overzealous, it deleted everything older than X weeks old... Plodey was planning on having 5.1 nightlies started by now but the CAF ifdefing nightmare is taking far longer to finish than anticipated.
I've asked plodey to kick off another build cycle for 4.4, although I just realized there's a wpa_supplicant security patch we should stick in there first.
Click to expand...
Click to collapse
Thank you and Plodey in advance, remain (for now) with delicious Kitkat and hoping for tasty updates. :good:
Unfortunately nothing new..
The Changelog apk shows just the dates of last updates -13.05.2015 & so on- Changelog (0)
and the folders on dl.omnirom.org -05.05.2015 17:01- are still all empty.
I feel so cropped! :crying:
Omni is Down?
No more updates in the blog, de dl. is empty...
Please, I dont want to back to CM
nachopro said:
Omni is Down?
No more updates in the blog, de dl. is empty...
Please, I dont want to back to CM
Click to expand...
Click to collapse
If you take a look at their issue tracker you can see that there are patches being merged almost every day. That hardly looks like a dead project to me.
aeveris said:
If you take a look at their issue tracker you can see that there are patches being merged almost every day. That hardly looks like a dead project to me.
Click to expand...
Click to collapse
No news from Feb 09 on their page, no downloads from their download page, looks like a dead rom to me (like a final user that I be).
Do not be angry, it's what I think.
nachopro said:
No news from Feb 09 on their page, no downloads from their download page, looks like a dead rom to me (like a final user that I be).
Do not be angry, it's what I think.
Click to expand...
Click to collapse
Don't worry, I am not angry at all, I just wanted to prevent anyone from jumping to conclusions.
I also am eagerly awaiting the 5.1 update, but some things just take time
aeveris said:
I also am eagerly awaiting the 5.1 update, but some things just take time
Click to expand...
Click to collapse
A new version of 4.4 would be fine for me. I started this week with omni and had only an old nightly from last year and would be happy to have an update trough the integrated updater.
Slayerrider said:
A new version of 4.4 would be fine for me. I started this week with omni and had only an old nightly from last year and would be happy to have an update trough the integrated updater.
Click to expand...
Click to collapse
Almost surely this would break the OpenDelta chain (I really at some point need to make it have a fallback where it'll detect a broken chain and download a full update), you'd have to download and manually flash a full build.
I was away nearly all weekend, I'll pester plodey about making the server do a build and try to make the script preserve at least ONE build for each device.
Entropy512 said:
Almost surely this would break the OpenDelta chain (I really at some point need to make it have a fallback where it'll detect a broken chain and download a full update), you'd have to download and manually flash a full build.
I was away nearly all weekend, I'll pester plodey about making the server do a build and try to make the script preserve at least ONE build for each device.
Click to expand...
Click to collapse
Thanks a lot, this would be really nice.
Builds are starting to appear
an0n981 said:
Builds are starting to appear
Click to expand...
Click to collapse
-20150520-yuga-FINAL.zip is successfully installed! :good: :good:
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/amp/
wmfreak said:
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/amp/
Click to expand...
Click to collapse
Let's hope more to follow.
His latest update has me super excited. He says it's now fully functional. Awesome work!!
Not quite fully functional
moxiot said:
His latest update has me super excited. He says it's now fully functional. Awesome work!!
Click to expand...
Click to collapse
I read the article along with the update, It's not quite fully functional, still quite a ways from being a working rom but he has shown that project treble does work and is somewhat viable. from looking at his screenshots the ril (sim stuff) is not working yet, I made some suggestions to him regarding his build that might fix that but he hasn't gotten back to me. Still not there yet but at least it shows that a generic AOSP Android can be installed and booted (at least the system and data images) by virtue of project treble. There are still a lot of things that are closed source relating to the hardware on our device and the SoC itself.
NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards
OldDroid said:
NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards
Click to expand...
Click to collapse
Thanks for the report. Let's hope to see a stable build in the near future.
AOSP
OldDroid said:
NFC not working, BT is wonky, FPS is not enabled, Keyboard is crashing when opening numbers/special chars, no HotSpot/Tethering, RIL does somewhat work but requires some more work on the actual device overlay.
But the essential things are working, Video Enc/Dec, Camera (Video, Photo), LEDs, Audio, HWC, vulkan, WiFi, BT (atleast its visible when i scan for it), power hal, maybe i forgot a few things ..
I've tested a self-compiled build on my H8 Pro, and thats the result, so i'd expect some similar situation for the Mate 9.
Regards
Click to expand...
Click to collapse
Did a build myself for the HiKey 960 reference board that uses the same SoC as the mate 9 and am doing a generic arm64 build right now, I'll be testing the both out when I get a chance. I think that I might have a little more luck with the HiKey build as it is the same SoC. It's a work in progress but project treble is showing some promise. I'm looking at making a flashable (in twrp) that will install the AOSP build (whichever one works)
revjamescarver said:
Did a build myself for the HiKey 960 reference board that uses the same SoC as the mate 9 and am doing a generic arm64 build right now, I'll be testing the both out when I get a chance. I think that I might have a little more luck with the HiKey build as it is the same SoC. It's a work in progress but project treble is showing some promise. I'm looking at making a flashable (in twrp) that will install the AOSP build (whichever one works)
Click to expand...
Click to collapse
Thanks my dear friend for your work and interest on our beloved Mate 9.
Thanks
albertobom said:
Thanks my dear friend for your work and interest on our beloved Mate 9.
Click to expand...
Click to collapse
You are very welcome, this all is a work in progress but from what I see so far project treble is going to make development easier in the future. I might try installing the boot image from my HiKey build to see how that works, it's the same SoC as our devices so it "should" boot, it's kernel version 4.9 which is the latest and supposedly greatest so we will see. If it doesn't boot I can always flash back the stock Oreo boot image.
I got a spare Mate 9 and can install and test stuff, happy to help
I'll keep that in mind
Exelios said:
I got a spare Mate 9 and can install and test stuff, happy to help
Click to expand...
Click to collapse
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.
revjamescarver said:
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.
Click to expand...
Click to collapse
Sounds good, yes my device is unlocked and on Oreo beta with oreo TWRP and everything, I'm not new to this
revjamescarver said:
I'll keep that in mind, I will be uploading my system.img and custdata.img for both builds when this one gets finished (takes forever on my old PC) they can be flashed via fastboot provided your bootloader is unlocked. I'll post the links after I get them uploaded.
Click to expand...
Click to collapse
Only progress on this?
Rebuilding
tiennemannes said:
Only progress on this?
Click to expand...
Click to collapse
I'm rebuilding, there is a thread on AOSP here https://forum.xda-developers.com/project-treble so I'm following the work there to see what changes to the framework need to be made, my build hung at 99% so I ended up starting it over, I think my build machine is running out of memory and the Java compiler is chocking. his v2 build boots and is mostly functional you can download it on his thread. His build is based on the 8.0.0-vts_r4 testing branch and mine is the 8.0.0_r34 release branch. You can download a build based on his changes and the vts branch here https://drive.google.com/file/d/1wMa_dgkWrqbC9i4GxUNOQlH0qIwffPph/view?usp=drivesdk
revjamescarver said:
I'm rebuilding, there is a thread on AOSP here https://forum.xda-developers.com/project-treble so I'm following the work there to see what changes to the framework need to be made, my build hung at 99% so I ended up starting it over, I think my build machine is running out of memory and the Java compiler is chocking. his v2 build boots and is mostly functional you can download it on his thread. His build is based on the 8.0.0-vts_r4 testing branch and mine is the 8.0.0_r34 release branch. You can download a build based on his changes and the vts branch here https://drive.google.com/file/d/1wMa_dgkWrqbC9i4GxUNOQlH0qIwffPph/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks. Can you confirm Galileo satellites are being picked up with AOSP Oreo? Should see EU flags in https://play.google.com/store/apps/details?id=com.android.gpstest
See stock ROM results at http://www.startlr.com/we-tried-galileo-huawei-mate-9-already-sees-the-european-satellites/
Galileo
tiennemannes said:
Thanks. Can you confirm Galileo satellites are being picked up with AOSP Oreo? Should see EU flags in https://play.google.com/store/apps/details?id=com.android.gpstest
See stock ROM results at http://www.startlr.com/we-tried-galileo-huawei-mate-9-already-sees-the-european-satellites/
Click to expand...
Click to collapse
Haven't tried it out, it's supposed to but I'll have to check that out, there was a report of taking a very long time to get a fix off GPS, but nothing specific to Galileo.
revjamescarver said:
Haven't tried it out, it's supposed to but I'll have to check that out, there was a report of taking a very long time to get a fix off GPS, but nothing specific to Galileo.
Click to expand...
Click to collapse
Yeah, saw the same (that's why I'm curious).
AOSP
tiennemannes said:
Yeah, saw the same (that's why I'm curious).
Click to expand...
Click to collapse
Yeah, the whole ASOP and treble thing is definitely a work in progress and it's going to take a little time to get that all working with the phone hardware properly but once it gets all figured out it is going to make updates easy and open the door to a lot of possibilities with custom ROMs
revjamescarver said:
Yeah, the whole ASOP and treble thing is definitely a work in progress and it's going to take a little time to get that all working with the phone hardware properly but once it gets all figured out it is going to make updates easy and open the door to a lot of possibilities with custom ROMs
Click to expand...
Click to collapse
Indeed, this stuff is exciting. My mate 9 should arrive tomorrow.... Can't wait.
Is the kernel compiled too from AOSP, or is that pre-compiled already in a boot.img?
Kernel
tiennemannes said:
Indeed, this stuff is exciting. My mate 9 should arrive tomorrow.... Can't wait.
Is the kernel compiled too from AOSP, or is that pre-compiled already in a boot.img?
Click to expand...
Click to collapse
No, in order to use the AOSP build you have to install Oreo beforehand, there are beta builds available for a few of the mate 9 variants right now but the "official" Oreo updates should start rolling out sometime in December. I had downloaded and installed the beta for the US variant.