Develop Bugs

[APP] One Click Lag Fix APK - 2.0 (UNSUPPORTED development halted)

OneClickLagFixV2PLUS inside the app is currently in RELEASE status. It has been tested on a fairly enormous number of devices without issue.
This is an APK (Normal Android App) that will install an EXT2 lag fix for you.
The APK itself can support a number of different lag fixes. It currently has the old OCLF V1 fix, which uses symlinks, and it now also has a new V2 fix which uses bind mounts.
This is in a new thead, as the old thread is very very long, and this is now version 2.
New features of the OCLF2+ lagfix vs OCLF1+
- Bind mounts are faster and require less O/S overhead than symlinks, making this fix smoother in everyday use.
- The bind mount allows for Android to report the correct free space available.
- If something goes wrong at boot, and the bind mount does not initialize, you will boot up to a copy of your data from before the lagfix was applied. This makes V2 safer than V1. (copying /system/bin/playlogosnow onto /system/bin/playlogos1 will effectively restore your device to how it was before you applied the lagfix. There is also an undo option, which will copy all of your changed data back to RFS before restoring.)
- As a bonus, an option to set the wifi screen off timeout is included.
How to use this:
Copy over the APK file onto your phone, and run/install it as normal using 'My Files'. There will be a 'One Click Lag Fix' app installed. Run that, and select the option you want!
The app will automatically kill all running tasks, and enable flight mode. You should probably not use the device while the lag fix is running. If you accidentally hit back or home by mistake, re-enter the app and re-select the lag fix. It should still be running.
Known issues in 2.0.0
Some devices with heavy carrier customization cannot install EXT2 Tools. Fix should be in the next version, if possible.
On Froyo (Android 2.2) this lag fix will refuse to install if the apps2sd feature is in use. The error you will see if Apps2SD is in use on installation will be that the loopback cannot be mounted.
Workaround: In order to install the lagfix on froyo, you will need to set each app that is on the external SD back to regular. Once the lagfix is installed, you can move apps back to the SD.
Fix should be included in the next version, if possible.
If you use up more space inside the EXT2 than is available outside the EXT2, you will have to remove apps/delete data until you have enough space to copy your data back when you want to uninstall. To help avoid this, don't set the space bar all the way on the far right.
Supported Devices And Firmwares
Root support is available for:
- I9000 Galaxy S on Android 2.1
- Captivate on Android 2.1
- Vibrant on Android 2.1
Other devices / Android versions will have to use a different method to root
Lagfix support is available for:
- I9000 Galaxy S on All Firmwares
- Captivate on All Firmwares
- Vibrant on All Firmwares
- Fascinate on All Firmwares
2.0.1 - 2.0.4 Changelog
- Fixed WifiTimeout option to work on Froyo
- Fix for OCLFV1 undo.
- Sync is called before bind-mounting, to ensure no data is lost.
- Fix for APPS2SD error (loopback can't be linked error)
2.0.5 Changelog
- Fixed WifiTimeout to work on strange firmwares without a system.system
2.1.0, 2.1.1Changelog
+ Lagfix V2+ has been updated to V2.1+ which features enhanced data security
In order to install it, you must first undo V2 using the option, and then install V2.1+ as usual
- Fixed WifiTimeout to now correctly require EXT2 Tools
- Fixed Cleanup option to now correctly clean up the V2 lagfix as well as V1
- EXT2 Tools will now remount /system as read-write
- Changelog included in app for market users
2.1.2 Changelog
- Fixed 'Restore Bootlogo' option to work correctly when V2 lagfix is installed.
- Fixed 'Restore Bootlogo' option to restore the froyo bootlogo if running froyo.
2.2.3 Changelog
+ Lagfix updated to V2.2+ which contains:
- Fix for new Vibrant, and I9000 JJ1 firmware.
- Fix for the timezone issue.
~ To Install V2.2+, use the undo V2 function, and then re-do with V2.2+
+ Kernel Installer (ALPHA) that allows you to easily flash a kernel to your device
2.2.4 Changelog
- Fix for menu->help button opening kernels page.
- Minfree now shows current settings
- Set scheduler now shows current settings
- Set scheduler now has an option to apply tweaks from hardcore on XDA forums
- Text cleanup
- Fix for occasional crash on fetching kernel manifest
2.2.8 Changelog
- Galaxy Tab Support
- Fix for installing with APPS2SD active
- Fix for set-on-boot for minfree and scheduler/tweaks
2.3.0 Changelog
- Bug fixes for occasional 'Broken Pipe', as well as related failure to copy boot up scripts.
- z4root option added, which opens the market to the z4root app.
- update.zip root option now downloads update.zip instead of having it included.
- Fix for typo in cleanup option, it should now work correctly
Rooting Froyo
Froyo's recovery mode is locked down, so you can't root it from your device.
However, you can use this: http://forum.xda-developers.com/showthread.php?t=803682
Donations
Since a lot of people have been asking, I set up a paypal account and got a donate link: https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
Feel free to donate if you want, but I'm happy if you don't donate too.

Full source code under the GPL is available from http://code.google.com/p/oclf/

Nice work! Will test it soon!
Sent from my GT-I9000 using XDA App

Very nice, thanks, will try it asap

Now downloading to test. I hope it will be great work.

Damn! Just when I decided to try out the stock firmware without any lagfixes. :-| Guess I have no choice but to succumb to your awesomeness now.
Will make a backup of data on my internal memory (just in case) and give this a shot on my brand new JM8 now
Sent from my GT-I9000 using XDA App

Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!

Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks

Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?

Hmm, can't find the lagfix

Thx for readding it
lol ^^
Will report back in a few minutes

RyanZA said:
Hang on, looks like it has a bug! I did a clean firmware flash, and its just giving a 'disabled' message, because it seems to be erroring on trying to find /dbdata/ext2data/
I'll have a 2.0.1 up within a few minutes with the fix. Sorry! I need a QA department!
Click to expand...
Click to collapse
2.0.1 is up in the first post. If you downloaded 2.0.0 and noticed that it didn't work, grab that one.
Steephig said:
Good work!
Do we need to uninstall APK v1 before using this APK?
I guess yes, but you never know.
Thanks
Click to expand...
Click to collapse
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
dupel said:
Is this the app version of "voodoo" fix only with ext2 (the one you started testing earlier in different topic) or its old virtual file method?
Click to expand...
Click to collapse
Virtual file method, but better.

RyanZA said:
You don't need to uninstall APK v1 first. It will overwrite it.
V1 lagfix will need to be uninstalled first, but the uninstall can be done by either V1 or V2 APKs.
Click to expand...
Click to collapse
I phrased my question a bit weird, what I meant to say was if the v1 lagfix should be uninstalled, but you gave the answer anyway.
Nifty!

Can I try it this in 2.2 JPH?
Thanks...

halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
It was deved this evening now, completely in JPH. So yeah, JPH works. If anything else works is unknown!
Also, the wifi timeout option does not work in 2.2, only in 2.1 Android. I'll put the fix up with whatever other bugs people find in a bit.

halabibk said:
Can I try it this in 2.2 JPH?
Thanks...
Click to expand...
Click to collapse
Tried it on my sluggish JPH.
Now it's blazing fast!

Very nice RyanZA.
THX!
Now my JPH firmware seems to be as fast as JM6 with Voodoo fix
Dennis

Thanks, another Q? actually I am using CFLagFix 1.80, still can use this?

Got an error (running XXJPH):
"Could not link loopback device /dev/loop0 to /dbdata/rtssdata/ext2/linux.ex2! loseup: /dev/loop0"

Damm i chose to upgrade the app from 1.6.7 but there are no install options am i missing something ? when i open the app no options to install anything
wifi timeout defo not working on 2.2 JPH

[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!

Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RHOD/TOPA) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog

Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location). I think this also breaks the stock browser, I recommend using Dolphin Mini!
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...

Changelog​ March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)

Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT

mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!

The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226

Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .

so this is the neopeek build only in an image?

husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!

arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh

randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.

Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?

JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.

arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.

JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...

arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed

Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).

steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!

this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.

kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!

[App] 2BOrange - Install any kernel (Voodoo, SpeedMode, Infusion...) without computer

____________________________________
2BOrange
____________________________________​
Hi everybody,
I have made a free application to install any kernel on your SGS very easily.
The idea is that there is a website where kernel are uploaded with a script and an application to:
- search
- download
- install it on your phone.
The application and the website are not limited to install kernell but I think it is a good way to try it.It can execute any script in the android shell.
So I have made some script for some kernel, there are so much that I have not the time to make one for each of them.
To make a script is very easy, I have attached an example of one I have uploaded on the website. If you need to attach a file, put it in a zip and upload both (the script and the zip) through the upload form on the website,
The address of the website is:
http://www.2borange.com/
A general thread on XDA (not dedicated to kernel on SGS) about the application:
http://forum.xda-developers.com/showthread.php?p=14875954#post14875954
You need to create an account to upload but it is not mandatory to just search, download and install a kernel.
Please keep me informed if everything work or not. I have only test it on my phone.
For the author of the kernels: I am sorry to have not yet informed you of the sharing of your great work, I will do it for sure when I will have done enough test to offer you an interesting way to share your work.
For the user: if you have time, don't hesitate to upload some scripts, it is free and easy to do...
Thank you for everything,
Michael
LIST OF KERNEL AVAILABLE AS OF JUNE, 27:
- Galaxian
- Infusion Kernel Faster Fusion Reaction
- Semaphore Kernel JVH - JVP
- SpeedMod Gingerbread
- TalonDEV
- TEGRAK lagfix- Voodoo kernel installer
- Voodoo kernel JVP
Don't hesitate to upload some new firmware. A model of script is provided below as attachment

niceee something to look foreward to

Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
This allows you to actually find a kernel, download it and flash it as well. The Kernel Flasher is just for kernels already on your sd card.

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
Thank you for your message.
I did not know about this application. I have read the description and I can tell you the purpose of mine is totally different.
I have understood that Nedar application is to install a Kernel that you have already downloaded and copy on your SDCARD.
The purpose of my application is to download automatically a script and a zip file, and execute the script.
So there are 2 main differences between these two applications:
- my application get files you need directly from the cloud (Internet), so it is like a deposit of files
- my application is not limited to kernel installation, it is just a usefull example to show people how it works, but it can do more, really lot more tasks.
However, because the application of Nedar is dedicated to one particular task, it has option I have not yet implemented in mine. By example, I have not yet construct a script to backup the kernel in an update.zip file, which could be very usefull.
So they are really very different. I hope I will be able to construct more script, but may be the biggest difference with any dedicated application is that anyone can participate to my project without any knowledge in Java programation.
You just have to know a little bit about shell to be able to share your work with others.
THAT IS THE REAL PURPOSE OF THIS APPLICATION : SHARING!

Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!

Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
Thank you for your interest.
The thing I need now is not money, donation,etc... but report of test and ideas of improvment.
By the way, I only have a samsung phone, and I am wondering if there are possibilities to install kernel in other phone only by using the shell, have you an idea ?
Second question: have you an idea how to proceed to install an entire ROM through the shell ? I suppose the phone has to be rebooted before installation begin and lauche in a recovery mode, but how to make it automatic like in ROM Manager?
Thank you for your help!

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
What is the way it should take for you?
I need ideas

lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
I have already included a kind of filter based on brand, model of phone and firmware version plus sdk version, do you think it could be more precise?

Fixed script on server, should work on every phone now

Hey snoopy33, why do you have not yet updated this page?

[ROM] 4.0.2 CamDroid w/more to come

This is the ROM that I've been working on for the past week or so. My first attempt so I'd like to get some feedback (and hopefully a name ).
Details:
-built from stock 4.0.2 img
-rooted
-deodexed
-busybox installed
Changelog:
1.0: 12/28/11 Initial build. Base created.
1.1: 12/29/11 Fix Facebook font issue.
1.2: 1/2/12 Add advanced power menu.
1.3: 1/4/12 build.prop edits. Remove USB Debugging icon. Set system framerate to 240 fps.
I haven't tried this on anything but stock (bootloader, radios, kernel, etc.). If you are willing to test with the leaked stuff and let me know that we be great.
To install:
Make a backup
Download http://www.megaupload.com/?d=OVJA07DX
Check MD5 (provided below)
Reboot into Clockwork Mod Recovery
Factory Reset (if coming from other ROM, 4.0.3, or anything like that) (not needed from stock 4.0.2)
Wipe Cache
Install zip from SD Card
Reboot system (this may take a few minutes)
md5sum:
6df0181c7a9603c7f4aa3e05a2a8520d
Big thanks to @bigxie for answering my questions!

Screenshots: (even though its stock)

Your screenshots aren't coming through. Do you have a link to an imagehost?
Is this pure stock other than deodexed and busybox?
Must be pretty stable (which I like!)
Good luck with the new ROM!

Good work. I hope you make this ROM into something that sets it apart from the others! Good luck.

I like the remove usb debugging icon. i dont know if the other roms have it. (probably do) but good work I hate the stupid icon.

Sorry about the screenshots. Dropbox link kept failing. Attached them through the actual file so they work now. Not very nice questioning my dev abilities on behalf on dropbox link fails
rabaker07 said:
Your screenshots aren't coming through. Do you have a link to an imagehost?
Is this pure stock other than deodexed and busybox?
Must be pretty stable (which I like!)
Good luck with the new ROM!
Click to expand...
Click to collapse
This is built from the stock 4.0.2 .img with all additions being the ones in the OP. Got a few ideas of things to add down the road that Ill be working on/hopefully adding soon. Don't be afraid to try it out and let me know what you think!

zehkaiser said:
Don't be a jerk or anything...
But really, good work. I hope you make this ROM into something that sets it apart from the others! Good luck.
Click to expand...
Click to collapse
Thanks for the kind words and support! I'm still learning but hey, I gotta start somewhere. This is my start. Feel free to add input! It's always appreciated.

bpherbst said:
I like the remove usb debugging icon. i dont know if the other roms have it. (probably do) but good work I hate the stupid icon.
Click to expand...
Click to collapse
It's just a simple build.prop addition. I'm with you as well on hating the icon being there though which is why I removed it. Thanks for the feedback!

AOSP 4.1.1 R4 (JRO03L) for Wingray

I've started a project building an AOSP ROM for wingray for my own amusement, and I thought I'd share, just in case someone wanted a nearly pure AOSP ROM with some carefully chosen tweaks.
As far as I am aware this is a fully functional ROM, but I am unable to test exhaustively so treat it as a pre-release beta, use at your own risk, blah, blah, blah.
I don't make any promises to continue development or fix bugs.
Features:
Built from pure AOSP 4.1.1 R4 (JRO03L) source with the following tweaks:
Fixed Guava compilation errors (thanks to CM10)
Added Busybox binary (thanks to ChainsDD)
Added Superuser package (thanks to ChainsDD)
Removed cellular and tethering references from wingray build (thanks to Peter Alfonso)
Disabled inclusion of AOSP recovery in the build (thanks to Peter Alfonso)
Fixed init.d support (thanks to CM10)
Working Camera
Bigger thumbnail size in recent apps menu
To do:
Horizontal recent apps menu
Reboot menu
T-Mobile Theme Chooser
More ...
Known Issues:
May encounter an issue with Superuser forgetting app permissions. Workaround: install SuperSU.

To install this ROM, I recommend wiping System, and Dalvik Cache, and performing a Factory Reset, but feel free to try it your way.
Make a Nandroid backup first!
Use standard Jellybean gapps.
http://goo.im/devs/zigackly/roms/wingray/AOSP_JRO03L
All feedback/bug reports welcome!

Well this is pretty neat, Thanks!

Glad you like it. I'm finding it quite snappy to use, even though it's not overclocked. I'll try to build in some more features as I get the time, if I can do it without losing the butteriness.

Hey thanx for your work.:good:
I wonder how this would run with a Tiamat/Eos Kernel ? Anyone tried?

Only one way to find out
Development is going a bit slowly in the last two days as I have been having trouble with corruption in my git repository.

i was just wondering if someone might ever do an aosp build for my xoom. thank you so much for your efforts, and for sharing the fruits with us!

cool deal man, i'll give this a spin and report back. so good to see others dev'ing for the Xoom! thank you thank you thank you

when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
just like to add that first impressions go a long way and i dont normally look at the boot animation, but i did this time and it was way smoother than any other ive seen on my tablet, dont know what the diff is, but i like it
so far so good

Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.

dodgefan67 said:
when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
Click to expand...
Click to collapse
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
tincbtrar said:
Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.
Click to expand...
Click to collapse
Could you try the download again? Build.prop should be replaced in system when you install, so it doesn't sound like a problem with where you are coming from.
MD5 checksum is 8cfdb670d42b5486f07f816f0e9a4791. You can check with MD5 checker from the play store.
If it's not a download problem, try a factory reset and wipe system before installing. Make sure you back up first.
In other news, I have fixed my git repositories although I had to redo all my work, but I am now working on a new build with improvements to the recents menu to take advantage of the Xoom's screen size. Hoping to implement bigger app thumbnails tonight and possibly a horizontal menu tomorrow.
The addition of a reboot menu is challenging. I made some changes based on the way Peter Alfonso does it and that didn't work, so I looked at the way CM10 do it and that didn't work either! I don't give up easily though. I'll take another stab at it this week. I'm learning this as I go along. Best way to learn, I think.
I'm also hoping to look at adding Theme Chooser this week.

Thank you for the md5, it matches, but still doesnt install.

z1gackly said:
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
Click to expand...
Click to collapse
thanks and looking forward to the updates!
may i suggest one or two? i like the options for things like setting quiet hours or profiles, being able to change toggles, etc. not sure how easy those would be to add in. i'm more than willing to help out and test things.
tincbtrar said:
Thank you for the md5, it matches, but still doesnt install.
Click to expand...
Click to collapse
what recovery are you using and are you sure you have done a complete wipe? (factory reset/wipe data, format cache, format system, wipe dalvik)?

Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.

tincbtrar said:
Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.
Click to expand...
Click to collapse
understandable. maybe try TWRP recovery just to make sure? if you have the time or are up to it?

I guess I could try TWRP, but I dont like how I always have issues with mounting sd with it...its why I stick to Rogue.
Ill give it a shot later on with TWRP to try and pinpoint the cause.
Edit: Tried TWRP and it flashed. Interesting! Thanks a bunch!

Build 7 added with larger app thumbnails in the recent apps menu. Available for download in post 2.
I'll look at what it might take to add those features, dodgefan67. I'm looking to implement the ones in my wish list in the OP first though.
I also need to get my head around merging in some improvements from the AOSP code base from after 4.1.1 r4.

The build.prop error is caused by an assert in the updater-script which checks you're installing the ROM on the correct device.
You could extract the updater-script and remove the assert, then replace the updater-script in the ROM.
It's in /META-INF/com/google/android in the zip.
I'm trying to get hold of a build.prop from a wingray which exhibits this problem, so I can correct for it in the script, but I expect yours will be fine now.
Worst case I can just remove the assert, then if someone flashes it on the wrong device it's their lookout, but I'd rather add the variant which is causing the problem to the assert.

I'm going to have to halt development on this for a time whilst I work on some stuff for my Nexus 7. I've updated build 7 so it will work with Rogue recovery. Back in a little while.

thanks for the update!