Related
Vanilla Flavored AOSP
Gtablet AOSP is a project for pure vanilla Android with the Gtablet. It aims to be barebones and as true to the AOSP code as possible. The Google AOSP code is modified as little as possible to provide functionality, and the ability to boot. It is stripped down for modification by the end user.
Using CyanogenMod device files, Pershoot's latest kernel (20110328, 2.6.32.36), and some cherry picked cyanogenmod/nv-tegra files, a functional 'rom' and a github repo for this project has been created. As functionality has been added since inception, more pieces from Cyanogen are making there way in (browser fix and tweaks, some under the hood stuff, internal storage fixes, etc) to improve overall experience. All variances from original AOSP code is visible via the public git.
Huge props to the Gtablet and the Cyanogen development community. Without your work, this wouldn't be possible.
Huge thanks to EJHart for his direct assistance with this project. Also, thanks to Bekit, Pershoot, GoJimi, Cyanogenmod team, Google... and I am probably missing others... This project would not be where it is without all of their work.
To use this rom, you will use ClockwordMod to flash the zip file as you would any other rom. I have only used ClockworkMod .8 in my testing.
DISCLAIMER: I cannot be held liable for anything you do to your GTablet. Make sure you are comfortable with recovery tools, such as nvflash, before proceeding. Though the rom is quite functional and stable in basic testing, this project is in early beta stages.
Download RC2 --http://www.mediafire.com/?t2rwxm9p9e4bcb7
MD5 -- fbb79ab9f4da245bb3ab2a320369f95b
*NOTE* GAPPS 20110307 for MDPI will not work.
Use the 20110120 MDPI GAPPS (for example, http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip).
Known Issues:
Most if not all the issues facing Cyanogen 7
Changes since RC1:
Latest Pershoot 20110328 kernel.
Browser crash loading google.com homepage is now fixed. This should resolve browser fc across the board.
Added User Agent, Fullscreen, Zoom controls, and Incognito to Browser.
Added Reboot to Power menu (intentionally excluding the recovery/bootloader options).
Fixed EMMC and basic information for Internal Storage in Settings->Storage.
Removed phone signal indicator, and tablified numerous text values.
Latest from AOSP Master (not much new since RC1).
Removal of extraneous junk, like speech recorder, voice dialer, and mms.
Retired changelog:
RC1 - Beta2:
My Apps now works in Market. Google Maps no longer force closes. -There is a downside to this-. The fix involves altering the LCD Density, which causes some apps to not scale properly.
Media on EMMC is now scanned and available in Music/Gallery/etc.
Live Wallpapers work.
Pershoot kernel 20110307
A bunch of under the hood stuff due to major changes upstream from AOSP.
Beta2 - Beta1:
AOSP is now pulling from master branch, making it version 2.3.3_r1.
Camera functions for still pictures. No mirroring or rotation issues. Video recording still not working.
Latest NVidia 3991 libs included (noticeable performance increase).
Pershoot kernel 20110301
Beta1 - Initial release:
Fixed EMMC.
Steamlined compile process.
Addition of Spare Parts/Dev Tools (possibly removed in future versions)
BUILD YOUR OWN:
GitHub -- https://github.com/aosp-gtablet
Use this project from github to create your own image:
repo init -u git://github.com/aosp-gtablet/gtablet-aosp.git
The process for CM7 will work. Run extract-files.sh, run envsetup.sh, lunch, make -j[X] bacon. Anything more is outside the scope of this post.
** Additional notes -- GoJimi's Soft Buttons are available in the source code, but are disabled in this release.
I am a minimalist, and I know there are others. I hope others enjoy, and help make this a better project
Please let me know what bugs you find so I can work on them! Thanks.
Sold! Will give this a try and report back. Nice writeup too. Is it true, development only available on linux?
Thanks.
I have done all my work in Linux, so I wouldn't know of any other way to create an image. Sorry.
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
jooky2000 said:
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
Click to expand...
Click to collapse
I have installed GAPPS, they work with the exception of the same Market/My Apps bug found in the CyanogenMod rom. I think it's fast too. I have not run battery test, or benchmarked it thoroughly. Someone has already recommended a possible fix for the 3d textures, that might help Quadrant run successfully. Without textures and all, I did get one run of Quadrant to complete (after numerous tries) and received a ~2100 score. Not the best, I know, but it still seems very snappy.
Not a quadrant user myself. Just the feel of it is impressive. I will report back with battery stats tomorrow.
Solid work getting this to the masses. Thanks.
What's with the weird Japanese keyboard and application that's included?
jooky2000 said:
What's with the weird Japanese keyboard and application that's included?
Click to expand...
Click to collapse
I assume you're asking about the Input Method options? I did not customize those, it's built with the full build of AOSP.
Please confirm what app you are talking about.
Has anyone tried MarketEnabler to see if it fixes the market issue?
just an FYI not sure what reports are coming in about it not working with 3.0.0.5 of CWM, but I was able to install it running 3.0.0.5.
-Josh
Excellent work, guys. Once everything works this will be my primary ROM.. since my wife also uses the tablet.
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
jooky2000 said:
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
Click to expand...
Click to collapse
Can you expand on what you removed? Just certain apks?
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
gdanko said:
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
Click to expand...
Click to collapse
The image is built using the device files from the CM7 repo, lightly modified and forked to it's own repo. This includes extract-files.sh, which is identical to that in CM7. I didn't see a point to re-invent the wheel on this step, as bekit & co. have done such an excellent job. It does not impact on the outcome of this being an AOSP image. Among other things (like defining hardware specifics in BoardConfig.mk), the device files bring in the core libraries already on your GTablet. This includes libaudio.so.
So ive installed this bad boy but ive seemed to have lost the market any ideas
jivy26 said:
So ive installed this bad boy but ive seemed to have lost the market any ideas
Click to expand...
Click to collapse
Same problem here. Market is not present.
You have to install google apps. Use the one for cm7/gingerbread found here http://goo-inside.me/gapps/ flash the zip as you would a rom in recovery.
can you please put screenshots?
If the rom is based on GB then screen shots at this point are not possible as ddms doesnt work with GB. It looks just like plain jane vanilla android.
Background
As a bit of background, I publicly posted ROMs on PPCGeeks for the HTC Touch w/WinMo several years ago. Since then, I continue to develop ROMs primarily for family and friends on the EVO4G, LG Optimus, Acer A500, and of course the HP TouchPad. After an initial testing period by a group of volunteers here at XDA (thank you, thank you, thank you), I have decided to publicly release this ROM. I hope you enjoy it.
Philosophy and Acknowledgements
My emphasis has always been on a very light and fast ROM that leaves plenty of room for one's own apps and customizations. My HP TouchPad ROM is based on a very stripped down KANG of the latest CM9 version (big thanks to Dalingrin, JCSullins, and all the other TPad devs that have brought this capability to us) that supports HW Video (meaning Netflix and HD YouTube) and all the other goodies you have come to know and love.
In addition there are also a few other treats thrown in, primarily,
the recently released QualComm adreno 2xx drivers,
the init.d tweaks published by Rohan,
the new ath6kl wifi drivers being incorporated into the 3.0 kernel,
the new HD Tablet launcher by the "Go" folks.
Big thanks to all the folks associated with these for their generosity in publicly providing these tweaks. Finally, I also employ a very stripped down version of the latest version of GApps that I will also link to. You can use the full version of GApps found elsewhere, but that will then somewhat defeat the intent of this ROM. The attached pics will give you some idea of what to expect. The benchmarks are all "typical" of the results I get on a non-overclocked CPU running at ~1.2GHz.
Updates
In terms of updates, I actually build the ROM and the kernel almost on a daily basis so my older AMD quadcore isn't tortured with having to handle an extraordinary number of new commits. But that doesn't mean I flash almost daily. It all depends on what looks significant, if I really want to try something new, or if I'm just bored . You can find out what's new in the below "News" section of this OP to find out what's the latest on my front.
Flashing and .apk's
Of course, all the standard cautions about doing the necessary backups (nandroids, titanium, or my backup) and the requirement for a complete set of wipes/formats (data, cache, system, dalvik) apply. Actually, I only find it necessary to wipe cache and dalvik between flashes of my own ROM. I also flash Gapps anew after each ROM flash. If you like experimenting with the other available ROMs, I advise a complete set of wipes and formats. And of course, you are flashing at your own risk.
Any .apk's included below need to be placed in the system/app directory with a rooted file manager, e.g. es file explorer, ensuring the permissions are the same as other .apk's in that directory, followed by a reboot. Unless, otherwise noted.
News
08/30/12
DISCONTINUED
Links
OaT's "Light n Tasty" GApps:
OaT's "Light n Tasty" ROMs:
I'm interested in your rom.
Reserved for furter test.
And maybe you can check out for this wifi driver.
http://rootzwiki.com/topic/18332-new-wifi-driver-ath6kl-from-compat-wireless/
First my sincere thanks to those who have already responded. Next, the ROM and Gapps are uploading now. I will be sending out the links as soon as the upload is complete. So that you can check your downloads, here are the MD5s that you can verify against.
ROM: fd3520fd207bfbab74eeaac04f964d1c
GApps: a70b46b81730846bafdb4174a013c09f
Edit: The ROM and GApps are finished uploading. Those who responded via PM, should be getting a reply PM with the links. If you don't receive, LMK, and I will send again.
I remember from the touchpeo days! Good to see you. I'm interested in testing of you need more. Take care OTA
Sent from my SPH-D700 using xda premium
O.a.T. said:
I'm considering publicly posting the ROM I build for family and friends, but I would like some additional feedback before deciding whether to go forward or not. As a bit of background, I publicly posted ROMs on PPCGeeks for the HTC Touch w/WinMo several years ago. Since then, I continue to develop ROMs primarily for family and friends on the EVO4G, LG Optimus, Acer A500, and of course the HP TouchPad. My emphasis has always been on a very light and fast ROM that leaves plenty of room for one's own apps and customizations.
My HP TouchPad ROM is based on a very stripped down KANG of the latest CM9 version that supports HW Video. In addition there are also a few other goodies thrown in including the recently released QualComm adreno 2xx drivers, the init.d tweaks published by Rohan, the new HD Tablet launcher by the "Go" folks, and some other stuff that I've undoubtedly forgotten to mention, but will with full credit if I do go forward with this publicly. I also employ a very stripped down version of the latest version of gapps that I will also link to. You can use the full version of gapps found elsewhere, but that will then somewhat defeat the intent of this ROM. The attached pics will give you some idea of what to expect.
I am only going to open this up to a "few" testers who might be interested in this kind of light ROM approach. If you are interested, PM me and I will get back to you with the links asap. Of course, all the standard cautions about doing the necessary backups (nandroids, titanium, or my backup) and the requirement for a complete set of wipes/formats (data, cache, system, dalvik) apply.
Click to expand...
Click to collapse
but whats new in this build
can you use bricked-kernal in your rom or overclock gpu please
Sent from my SGH-T989 using xda premium
I'd be happy to test if you still need people.
Sent from my Desire Saga using xda premium
sahhar1993 said:
but whats new in this build
can you use bricked-kernal in your rom or overclock gpu please
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
...............
Sent from my DROIDX using Tapatalk
I'm interested in this rom. I'd contribute also for it.
Please include a file manager for us folks that can' t get wifi to connect. It comes in handy to install apps Thanks
John
Sent from my MB855 using xda premium
sahhar1993 said:
but whats new in this build
can you use bricked-kernal in your rom or overclock gpu please
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Krunk_Kracker said:
...............
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
As I said in the OP, the emphasis is on lite that allows your favorite apps and customizations, not mine. In that vein, if bricked-kernal can be used on CM9, than it should be applicable to this ROM.
sonjohn1 said:
Please include a file manager for us folks that can' t get wifi to connect. It comes in handy to install apps Thanks
John
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Wow! No wifi at all, ever? Have you tried adb'ing files from your computer into your tablet? Guess I could include a file explorer as an app that could be uninstalled, but this seems a rather extreme situation. Any others facing this dilemma?
All: At this point I feel I have a good number of testers so I am closing the open call for volunteer testing.
Testers: For those who got a PM from me with the download links, please download the files as soon as possible as I will be removing the files from the server later today. Finally, my sincerest thanks to all my volunteers and a gentle reminder to please provide some feedback when you are able.
Awesome rom bro it runs really good to :thumbup:
Sent from my cm_tenderloin using xda premium
O.a.T. said:
As I said in the OP, the emphasis is on lite that allows your favorite apps and customizations, not mine. In that vein, if bricked-kernal can be used on CM9, than it should be applicable to this ROM.
Click to expand...
Click to collapse
Hey oat. First, hope to see you publish this to everyone, second, if you are compiling from source you can fork the file explorer from me/US if you want. It has such a small footprint on the Rom and would help those who need it.
Questions let me know. Thanks and BTW, if you need anything we certainly will help with what ever.
Good luck.
~Leo
Sent from my PG86100 using Tapatalk
Beta Test
Still beta testing O.A.T.?
Leoisright said:
Hey oat. First, hope to see you publish this to everyone, second, if you are compiling from source you can fork the file explorer from me/US if you want. It has such a small footprint on the Rom and would help those who need it.
Questions let me know. Thanks and BTW, if you need anything we certainly will help with what ever.
Good luck.
~Leo
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the encouraging words and thanks for the offer. I do build from source and early on included a file manager. I haven't lately as the taste for file managers among myself, friends and family changes routinely. I would only need to update that file and reactivate a few lines in the build script to get it back in.
babcocca said:
Still beta testing O.A.T.?
Click to expand...
Click to collapse
Yes, in the sense of waiting for feedback from the testers.
I'd absolutely love a ROM like this. I've been wanting something light and speedy.
Sent from my ADR6425LVW using xda premium
rom
so, i installed this rom this morning, came from [RC1.2] CM9 with Cornerstone, wiped cache and davlik, didn't wipe data or anything, everything carried over perfectly, and so far so good, youtube works hd also, the games i play work perfectly, been running smooth all day.
only hic-upsi had was videos on youtube site didn't load in chrome browser, and my wifi froze for literally 5 seconds. either than that, i've had no problems.
i'll report on how battery life is tomorrow, and which if any apps give me trouble, cause i like using a new rom all day, and see how battery life compares to a fresh recharge
can you add supercharger v6 ics to your rom please
it will be awesome
http://forum.xda-developers.com/showthread.php?p=16635544
Sent from my SGH-T989 using xda premium
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:
THIS IS A THREAD FOR TENDERLOIN ROM DEVELOPERS TO DISCUSS ISSUES REGARDING BUILDING, CODING, CREATING, DEBUGGING AND STABILIZING A CM10.1/JELLYBEAN 4.2.x ROM FOR THE HP TOUCHPAD. IF YOU AREN'T WORKING ON THIS, MOVE ALONG... NOTHING TO SEE HERE
Seriously, folks. This is an information exchange thread for developers. You're welcome to watch and listen, but PLEASE, please, don't ask user questions here, don't ask for ETA's, don't give huzzahs, and "I want this" stuff. Post that in the relevant ROM threads, the General or the Q&A. Thanks.
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
My device tree is on github:
https://github.com/drmarble/android_device_hp_tenderloin/tree/10.1-ugly
On the 10.1-ugly branch is a semi working device tree for hp tenderloin cm10.1.
Many more details for building are included in the README file.
If you aren't set up to build cyanogenmod roms for the tenderloin, this won't be any use to you. It truely is developer only.
It is a work in progress. Very, very much a WIP.
Camera doesn't work.
Bluetooth doesn't work.
Thanks to the efforts of James Sullins the SDCARD mounts and sound works from the speakers.
This is heavily reliant on the work of Arne Coucheron.
His invaluable patches include:
http://review.cyanogenmod.org/#/c/34375
http://review.cyanogenmod.org/#/c/34377/
http://review.cyanogenmod.org/#/c/34374/
and his highly useful google doc:
https://docs.google.com/document/d/1cGKMXx112gGls9a6ziDTpPgObnU6ZExPy5tByqqIyI4/edit?pli=1
Without his work, we would still have no display.
Of course, everything depends upon the work of the cyanogenmod hp developers Dalingren, FatTire, jcsullins, eyeballer, dorregaray and all the rest.
All my patches are in one big, ugly patch. I included various gerrit patches that my patch is dependent on. I'll work on neatening it up so the commits are separate and readable. I just wanted to get this out there so others could work on it and we can get cm10.1 working.
I think that this is everything.
Please, lets have lots of folks working on this. We can't use gerrit because this isn't cyanogenmod. Steve Kondik feels that since we are dependent upon the legacy qcom repositories it isn't really cm. This is just a kang. We can post patches here, or link to our githubs. Or use pull requests. I also started a thread on Rootzwiki. IRC on #cyanogenmod-touchpad on Freenode is a good place to chat. Jcsullins has already contributed two essential patches that got us SDCARD mounting and sound via irc.
We can get this done together.
drmarble said:
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
--SNIP--
We can get this done together.
Click to expand...
Click to collapse
Thanks for that informative post. What are you using for a default manifest and kernel source?
most of the information needed to build is in the README file at my github. I use the regular cm manifest and build tools. The local manifest I use is:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drmarble/android_device_hp_tenderloin" path="device/hp/tenderloin" remote="github" revision="10.1-ugly" />
<project name="CyanogenMod/hp-kernel-tenderloin" path="kernel/hp/tenderloin" remote="github" revision="ics" />
<project name="CyanogenMod/android_hardware_atheros_wlan" path="hardware/atheros/wlan" remote="github" revision="jellybean" />
<project name="arco/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" remote="github" revision="cm-10.1" />
<project name="arco/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" remote="github" revision="cm-10.1" />
</manifest>
I just use the regular cm kernel. The addional repos work together with a couple of flags in Boardconfig.mk. Those are set in my "big_ugly_patch" which should have been broken up into several different ones. Really, you just have to set up a cm build environment, put in my local_manifest.xml, repo sync, apply the various commits listed in the README file and "brunch tenderloin".
To those who want a downloadable ROM. There isn't one yet. I don't think this is ready for anybody but home brewers. jcsullins' and others cm10 builds are much more stable and useable. This is just more fun for build-it-yourself-ers because it is newer and shinier. It's not a better android experience yet.
It may be worth mentioning, for clarity, to make sure you have included vendor/hp/tenderloin.
<project name="TheMuppets/proprietary_vendor_hp" path="vendor/hp/tenderloin" remote="github" revision="jellybean" />
I've been working on including the latest Adreno drivers but have found they are dependent on the CAF varriant, and we are stuck using legacy. Which is exactly why Steve Kondik said "I do not want to create official builds for any device that needs to use this. If your device can't support the latest driver for whatever reason, it's going to be janky and slow and probably worse than stock on 10.1."
I am trying to take some inspiration from the HTC Sensation, aka Pyramid, because that device is also msm8660 and they are utilizing the legacy display variant in 4.2.2 as well - without any complaints about video playback.
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
drmarble said:
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
Click to expand...
Click to collapse
Are you getting any video playback with your builds using extract-flies.sh? All I ever seem to get is an infinite "loading" screen. I once used CM9 Adreno drivers in building CM10, with the same "loading" effect.
shumash said:
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
Click to expand...
Click to collapse
Ok, after much thrashing, I"ve got everything compiled and waiting in the OUT folder, it stops with this:
Code:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
out/target/product/tenderloin/obj/PACKAGING/systemimage_intermediates/unsparse_system.img: 1376/51296 files (0.0% non-contiguous), 60991/204800 blocks
Install system fs image: out/target/product/tenderloin/system.img
out/target/product/tenderloin/system.img+ maxsize=856424448 blocksize=135168 total=237901004 reserve=8650752
[email protected]:~/android/skz$
I'm guessing it has something to do with the releasetools, but I get no error. Any ideas?
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
drmarble said:
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
Click to expand...
Click to collapse
I think I've got that covered. I modified the releasetools, too, and tried both the modified Evervolv and CM versions, but what I get is that stop. I'll check and make sure, though, and I'll compile with the "-v" switch to see if there's something I missed.
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Chortle, I do need to watch everything, don't I? And I do use meld. It's a great tool. What I'd like to do is to run the "tenderloin_ota_from_target_files" python script from the command line. I can just see all those compiled files sitting there waiting to be zipped up!
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a CM10.1 to compile, but it boots to the flashy screen. I'm in process of running a clean make to ensure I didn't leave something nasty around. The Evervolv source built to the point that it needs to be zipped into the OTA and release files, but I think there's something missing in the make files that connects with the releasetools. I ran a compile with the verbose switch set, and it acted like it just reached the end of the make files. I have also successfully built a ROM from PAC-man sources, but it also boots to the flashy screen.
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
Click to expand...
Click to collapse
Just downloaded and flashed now, did not run into any errors. Hmm... I've uploaded it again under a different name :good:
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
Click to expand...
Click to collapse
Don't know if the attached are the same as those posted by SGA, but these are official ones from QualComm that I have been using with some sucess. They are advertised as...
"This release contains the user-mode driver binaries for Qualcomm's Adreno 3xx and 2xx GPU on Google Android 4.2 Jelly Bean MR1. It has been tested with the CAF release A8064AAAAANLGD133402.1 and M8960AAAAANLGD230306.1. Supports any Adreno 2xx and 3xx GPU on Android 4.2 Jelly Bean MR1."