Database Users

[Android] AOSP 2.0.1 Proof-of-Concept Build. Assistance appreciated.

Tonight I managed to get my first Android build, 2.0.1, compiled myself from AOSP, up and running on the Vogue from NAND.
I made some small changes, most notably, updating the build.prop to adjust the DPI to 120 and adding the libhtcgeneric_ril.so library, as well as adding the necessary (or.. is it necessary?) build.prop entry to get the radio functioning.
I proudly present my first Android build.
NOTE: This is purely for testing/evaluation purposes.
Working:
Radio
Data
Screen resolution is accurate
Not Working:
Audio
Power Functionality (buttons do not wake the phone?)
GPS
Anyone up for pointing out what I need to do differently to get the non-working aspects functioning? Any tips on optimization? Clues to setup and take full advantage of build.prop?
Additionally, do we have a central repository of Vogue (or MSM7k) drivers that've been ported as source, ready to be compiled for different versions?
There's probably a lot missing here that I'm not even considering.. so please feel free to make any comments, give any advice, or point me towards any documentation.
All help is appreciated. Thanks!

I think this is the repo you're looking for:
http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
It contains Audio & GPS drivers, among other things. Can you wake the phone over adb shell with the command echo "wake" > /sys/android_power/request_state ? I'm also interested in getting an AOSP build running from source, I'd like to get the camera working for Eclair.
EDIT: Also, in the zenulator's eclair mod, the /system/etc/keychars directory contains these files:
Code:
htcvogue-ts.kcm.bin
qwerty2.kcm.bin
qwerty.kcm.bin
sapphire-keypad.kcm.bin
trout-keypad.kcm.bin
trout-keypad-qwertz.kcm.bin
trout-keypad-v2.kcm.bin
trout-keypad-v3.kcm.bin
tuttle2.kcm.bin
vogue-ts.kcm.bin
Perhaps that vogue binary is needed? That's my shot in the dark.

Those files are just for the keymapping, nothing more..
polyrhythmic said:
I think this is the repo you're looking for:
http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi
It contains Audio & GPS drivers, among other things. Can you wake the phone over adb shell with the command echo "wake" > /sys/android_power/request_state ? I'm also interested in getting an AOSP build running from source, I'd like to get the camera working for Eclair.
EDIT: Also, in the zenulator's eclair mod, the /system/etc/keychars directory contains these files:
Code:
htcvogue-ts.kcm.bin
qwerty2.kcm.bin
qwerty.kcm.bin
sapphire-keypad.kcm.bin
trout-keypad.kcm.bin
trout-keypad-qwertz.kcm.bin
trout-keypad-v2.kcm.bin
trout-keypad-v3.kcm.bin
tuttle2.kcm.bin
vogue-ts.kcm.bin
Perhaps that vogue binary is needed? That's my shot in the dark.
Click to expand...
Click to collapse

What's responsible (or handles) power management, then?
And why are there so many keymapping files? According to AOSP, Android will default to qwerty.kl, and certainly with the Vogue being as simple as it is, a single qwerty.kl set up for the Vogue would be sufficient.
So what gives? Or are these files all leftover as this was "ported", and they existed to support previous devices, etc.?

first off great job. this is exactly how i started out by building my own builds from source and then taking apart others to see what fits together. if i have time this weeked i'll have a look at it.

There are an awful lot of moving parts in power management in Android (and any OS, really) - there's the kernel's power subsystem which controls deep sleep / suspend, and which Android attaches a "wakelock" system to, each radio lib (Bluetooth, WiFi, phone) has power management (which hooks up to kernel interfaces), there's the panel driver which controls brightness, etc.
I think the keymapping files are just there so that no matter which one the framework looks for, it always finds one, speeding things up - rather than having to try to find each one and failing down until it finds its eventual failsafe qwerty, it loads the Vogue one straight away.

Awesome man, way to go!
Can you throw in links for rootfs/zimage, I will try later today on my wife's phone.

Thanks sshark, I would, but I've been tweaking that image continuously and at it's current state, it's broken.
Here are the major hurdles I'm facing right now:
How do I determine which drivers are and are not necessary in a build? If we use an AOSP build, or someone else's port, obviously we don't want audio drivers from the Nexus One or generic Goldfish sensors from AOSP, so how can we know what we need to be able to keep images clean?
Along the same vein, how does one incorporate drivers accordingly, such as audio?
Is power management really a dark art right now? Plemen's AOSP build is fantastic, but I typically have to push the power button four times to get the OS to wake up, whereas a 2.1 build I just played with on the Vogue would power up right away on one click. What gives?
When compiling images using genext2fs, does 80000 vs 160000 matter, NAND vs HaRET booting? What's the maximum?
Lastly, I've recently tried unsquashing others images, making changes, and then trying to re-ext2 them, mount them, and squash them. However, when I do this, my images no longer boot fully on my Vogue--instead they'll get as far as the boot animation, it'll run for a bit, and then the boot animation will pause for a second or two, and restart. This happens endlessly. Is this a problem with my process, be it ext2, sqsh (sqsh version, perhaps?) anyone have an idea?

Shidell said:
Thanks sshark, I would, but I've been tweaking that image continuously and at it's current state, it's broken.
Here are the major hurdles I'm facing right now:
How do I determine which drivers are and are not necessary in a build? If we use an AOSP build, or someone else's port, obviously we don't want audio drivers from the Nexus One or generic Goldfish sensors from AOSP, so how can we know what we need to be able to keep images clean?
Along the same vein, how does one incorporate drivers accordingly, such as audio?
Is power management really a dark art right now? Plemen's AOSP build is fantastic, but I typically have to push the power button four times to get the OS to wake up, whereas a 2.1 build I just played with on the Vogue would power up right away on one click. What gives?
When compiling images using genext2fs, does 80000 vs 160000 matter, NAND vs HaRET booting? What's the maximum?
Lastly, I've recently tried unsquashing others images, making changes, and then trying to re-ext2 them, mount them, and squash them. However, when I do this, my images no longer boot fully on my Vogue--instead they'll get as far as the boot animation, it'll run for a bit, and then the boot animation will pause for a second or two, and restart. This happens endlessly. Is this a problem with my process, be it ext2, sqsh (sqsh version, perhaps?) anyone have an idea?
Click to expand...
Click to collapse
i cant answer all of those questions, with that said ill tackle the last two
4. when using genext2fs to compile builds it doesnt matter what the -b count is we just use
Code:
genext2fs -d ./system -b [B]180000[/B] -a system.ext2
to make sure we could fit a ~180 mb system so if your system folder is ~120mb(uncompressed), using -b 125000 should work.
5. make sure you arent using squashfs-tools 4.0 because it isnt supported in our kernel version. so use 3.3 or 3.1 .
5b. when you see the boot logo looping, that means the build has crashed and like i said to you before i strongly recommend you setup adb on you box so you can run logcat to see what the phone is actually doing and to debug what went wrong and why it is looping

Thanks Jamezelle. So NAND users need to make sure it's -b 90000 (or less), as NAND only supports 90 mb. max, correct?

Shidell said:
Thanks Jamezelle. So NAND users need to make sure it's -b 90000 (or less), as NAND only supports 90 mb. max, correct?
Click to expand...
Click to collapse
right i would keep it around 88 to be safe.

I'm trying to get ADB to work (using ubuntu 9.10) and I've followed the instructions here, including restarting udev, but even still when I try to start adb, I get "command not found" in terminal.
Any ideas on what I'm missing?
EDIT: I'm missing a ./. I'm really starting to wish I could do this natively in Windows.. geeze.

Shidell said:
I'm trying to get ADB to work (using ubuntu 9.10) and I've followed the instructions here, including restarting udev, but even still when I try to start adb, I get "command not found" in terminal.
Any ideas on what I'm missing?
EDIT: I'm missing a ./. I'm really starting to wish I could do this natively in Windows.. geeze.
Click to expand...
Click to collapse
did you make sure you added the path to adb in .bashrc
# On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Click to expand...
Click to collapse
that should clear up the "Command not found" issue

jamezelle said:
did you make sure you added the path to adb in .bashrc
that should clear up the "Command not found" issue
Click to expand...
Click to collapse
Yep, that was the issue. It needs to be there, or launched as ./, I presume.
Thanks much for your help tonight, Jamezelle.. I'm happy to report that I'm steadily making progress for a working release.

Shidell said:
Yep, that was the issue. It needs to be there, or launched as ./, I presume.
Thanks much for your help tonight, Jamezelle.. I'm happy to report that I'm steadily making progress for a working release.
Click to expand...
Click to collapse
thats great to hear, also thanks for your additions to the libgps.so! its nice to still see some android enthusiasm in this community

Kernals, Nand, full functioning Android?

I gave my Dad my old blackstone when my Desore turned up.
He has winged that he can't get the marketplace and about all those general WinMo issues that people have (it dead etc)
I can't find a clear message on the status of NANDROID for blackstone.
TIAD8s site has NAND versions that are missing bluetooth or other funcitons
It appears there are basic functions that are lost according which kernal is being run.
I'm willing to do one completely convoluted install just to get Froyo style on my dads phone but only once. I never have trouble with new flashing procedures (slow and steady wins the race) but I don't want to hand him back the phone broken especially as he uses hands free in the car
So - can anyone say categorically that a NAND version work fully?

Categorically: Not yet. Wondering if ever...

Forget it...

Think Tiad8 only has test team working on a NAND build anyway?
Not seen it in action yet

Kernals?! ....

I find deliberate typos (NOT TEXT SPEAK) can get people to engage.

olly230 said:
I find deliberate typos (NOT TEXT SPEAK) can get people to engage.
Click to expand...
Click to collapse
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .

t8 let people wait and wait.
though it's good to try, we don't know whether he really works on it as he start many threads to other device besieds HD.

arrrghhh said:
Is that also why you called it a "Desore" instead of Desire?
lol, you made a typo or you just didn't know. No need to try and rationalize it .
Click to expand...
Click to collapse
Desore was a proper typo, I'll put my hands up to that

Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.

MietasSR said:
Tiad8's just kidding us, it will send to test team files from NVIDIA Tegra device. Only RUU_signed is working, but I think it's my modded LK Bootloader from Rhodium (with modified mtype). Something's wrong with this nand.
I have runned this but touchscreen not working properly and I don't have GSM.
Click to expand...
Click to collapse
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post.
With your post here I had to smile a little: now your name is connected to the "null nands" for many consumers in tiad8's forum. Even I thought you're part of it now and that's why I tried the build yesterday again: Boot partition to small and Kernel not working.
I think now it's getting to the critical point in the NAND experiments: correct or good partition sizes for NAND (some members there startet to change partition values in the image files with a hex editor) and more important: building a working kernel with modules for Blackstone NAND.
Until now all experiments reached a few preparing goals: getting a working .nbh for starting into fastboot, getting a recovery.img for a working CWM etc.
But now (if I am completely wrong please correct me, I really want to know) you have to change partition and ram parameters in clk and hope you will spare the protected parts.
And after that: Kernel and Modules for Blackstone on Nand. I am starting to believe here would be the real point for developers.
I started to build Kernel and Modules, a Boot Environment (initrdgz) from git and packed them with changed parameters in a Tinboot-Package. I can flash with the .nbh, I can boot, I got a lot of errors in init first, but I succeeded in running and loading the kernel, I get access to the changed mtd partitions etc. Debugging on Blackstone with Echo "" ist quite funny.
I got stuck when I tried to cp files from SD card to the /system partition (which is mounted r/w) - I can cp files from / to /system anyway. Big ?? for me. But I like to play with it a little more, because I learned a lot.

ThaiDai said:
I thought you were part of his developer team because he now give credits to you for your ruu and recovery.img (at last he ist starting to do this: giving credits) in the NAND download post..
Click to expand...
Click to collapse
Me Too!! Does this mean you are working on different things?

[Q] How to recover Acer a500 without any backup? NEED HELP!!

My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
He never had it connected to the computer.
We tried the factory reset.
We tried the hard reset.
We cleaned the cache & whatnot...
Nothing helps.
I've tried to use the GUIDE: Recovering Recovery/Obtaining SKB
Of course we only option we have, because nothing was ever back up, connected to a computer. I downloaded unbumtu 12.04 and installed it onto my laptop.
The requirements:
-ubuntu 12.04
-micro USB cable
-paper clip ....
I also made sure I installed gcc, lsusb, libusb-1.0-dev, & libusb-1.0.x
I get it to show on the desktop ...
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
I am by all no means a computer code writer, and hope someone will help me solve this issue.
I just can't afford sending the tablet back to Acer to be fixed.
I even tried flashing the information on the micro SD card, but I believe since his tablet wasn't connected ever to a computer things aren't running as smoothly as I would like.
I've downloaded nvFlash, blackthud3r, and many Roms.
I.ve even tried to flash a few with no luck. Mister Android has fallen and can't get up with the RED triangle and all.
I can get the tablet in Apx mode.
Also I can get the screen with the Fastboot...
I've tried all the tricks with the volume up and power button and toggle switch, AND/OR the volume down button and toggle.
But without the UIP or CPUID those items aren't doing me any good.
The tablet was only updated the old fashioned way. No customized anything.
Hubby mainly used it to get email and play pocker over the internet with it.
Not sure what other information you need, but I hope someone could get me out of this MISERY!
Been messing with it for over a week trying to read and get as much information about others having simular situations.
Thank you in advance & Hope to hear from you SOON!
We've even tried doing things in different computers...:crying:

radarbill said:
My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
Click to expand...
Click to collapse
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD

How to recover Acer a500 without any backup? Need Help?
Moscow Desire said:
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD
Click to expand...
Click to collapse
I appreciate you getting back so quickly.
I've already tried these.
I also tried most of these from this web page.
http://forum.xda-developers.com/showthread.php?t=1816560
Nothing seems to work.
There was a couple of them that would install about 25% but then android would keel over and the red triangle of death took over.
I would appreciate if you had any other suggestions, or if anyone else did.
There has to something I can do?!?

Well, without having the UID number, I think NVFlash is out of the question. Usually we get these quite simply when the tab is operating.
There is a Linux solution, to get UID, but I'm not a linux guy. There's a thread about UID, I think in the dev section. In there are steps to get it through Linux I believe.
With the UID, I think we can run TimmyDeans rollback tool. But as far as I know, you have to have the UID number.
MD

radarbill said:
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
Click to expand...
Click to collapse
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
Moscow Desire said:
There is a Linux solution, to get UID, but I'm not a linux guy.
Click to expand...
Click to collapse
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.

solved thankyou all
eppeP said:
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.
Click to expand...
Click to collapse
well we ended up getting a new mobo and that did the trick. so thankyou one and all

Official Ubuntu Touch for Galaxy Tab 10.1 is here!

I've been following the progress on official Ubuntu Touch port to Galaxy Tab 10.1 for a while and today they have updated the wiki for a dedicated session and early build install instructions.
This is an early build, some things work, some things are unknown and wifi is work in progress.
Installation
1. Download the ubuntu preinstalled and the p4wifi specific cyanogenmod image from the unlock instruction section below.
2. Put both zip files onto your sdcard
3. Enter recovery mode and do a wipe data/factory reset
4. Flash in this order:
First the cyanogenmod image (e.g. cm-10.1-20130325-UNOFFICIAL-p4wifi.zip)
Then the ubuntu image (this may take a while)
5. reboot
fix screen pixel ratio (this will become obsolete once the config file is included by default):
1. download p4wifi.conf: http://ubuntuone.com/688wubidavYnvfKvBWV7cY
2. copy p4wifi.conf into /etc/ubuntu-session.d/
3. reboot
Unlocking instructions
link to images
1. Ubuntu stuff:
Current: http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
2. CyanogenMod image:
Current: http://ubuntuone.com/6V0ZxZ8cqB2AGcF8nImrDV
*Note: I am not involved with the development and I do not own this project, for more details please go to the link below.
https://wiki.ubuntu.com/Touch/Devices/p4wifi

Thanks, friend! I'm gonna test it soon :good:

AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
I tried it. Installation worked fine and the first start (reboot after install) also went fine. Can't test more things than boot up right now - no time so far. I'll have a look this evening.
But why are there already users exsisting an how do i log in?
Sent from my One S using xda app-developers app

They say it's a test-only version and you can only log in to guest account...
and if you read the ubuntu-part file's name it is "quantal-PREINSTALLED", which means it is an installed image of Ubuntu that was tested on some previous devices by Ubuntu devs...
it's my thought, though...

AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app

customromfan said:
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I'm testing this now, but I cannot find /etc/ubuntu-session.d/

Wifi not working after returning image back to Cyanogenmod
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks

Can someone make a video of this running? I want to do it myself but can't find the 10.1's charger

GazaIan said:
Can someone make a video of this running?
Click to expand...
Click to collapse
I've installed it with no problems, just followed the instructions in the first post...
I'm now attempting to get screen pixel ratio fixed and wifi running, and then will upload a video to youtube (probably in the next few hours)

Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...

Dingles666 said:
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks
Click to expand...
Click to collapse
Not sure why you're having this problem. Maybe try format everything before flashing back or use a nand backup if you have one?

I think we must put the p4wifi.conf into ubuntu-session.d folder in the quantal before we install the image, right?
The proof I can provide is that there are folders named ubuntu-session.d and data in the quantal, but they're extracted to somewhere else during installation...
Video coming soon...

arashtarafar said:
Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...
Click to expand...
Click to collapse
My memory is a bit vague on this, but I think it's in the /ubuntu folder, as well as the rest of the filesystem. It confused the hell out of me when I had it on my Sensation, it seemed like there was an entire filesystem at the root of the storage, then another inside /ubuntu where everything seemed to be.
You could use the search in Nautilus to find it as well, just make sure it's searching all subdirectories

I had a problem adding the p4wifi.conf file to /etc/ubuntu-session.d/ folder. This is how I solved it.
My problem basically was that when using adb shell to access the device I was inside the android system. And you need to get inside the ubuntu-system.
My way to get shell access to the ubuntu-system was the following:
>adb root
>adb shell
You should now see something similar to [email protected]:/ #
Then enter:
>ubuntu_chroot shell
You should now see something similar to [email protected]:/#
You are now in the ubuntu-system.
to get the p4wifi.conf file into /etc/ubuntu-session.d I did the following:
>cd /etc/ubuntu-session.d
>echo -e "GRID_UNIT_PX=10\nQTWEBKIT_DPR=2.0\nFORM_FACTOR=\"tablet\"" | sudo tee p4wifi.conf
For some reason there is a space between " and tablet. This space should be removed! It seems as if the forum adds it when rendering my post.
Now for the changes to take effect you will need to reboot your device. You can do that by writing the following
>reboot
I hope this helped someone that just as me struggled to get the pixel-ratio fix applied to the system.

Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again

arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
Yeah I read about this post too, I'm a bit busy this week but maybe I'll try it out this weekend.

I finally fixed screen pixel ratio by flashing the .zip package linked in post 15 in this thread ... simply adb push it and flash using CWM (ubuntu won't erase CWM after being flashed)...
I'm now going to fix WiFi to upload a video that's worth seeing ...

arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
I have tried this but no success Please share if anyone solves the wifi-issue.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
Does iwlist work for anyone? For me it dosen't even recognise the command.

does 3G work on this?

3G doesn't work yet, but I'm testing the OS on my galaxy tab 3G
yeah, I too have tried putting userinit.sh file in /data/loca/ with no success... but note that you must put the file using ubuntu_chroot shell... did you try that?
maybe we can put the commands in afterflash-p4.zip and then flash it, like the way we solved the screen pixel ratio issue...
inform us if this method worked for you

[SUPPORT] Ouya Boot Menu Support Thread

Hello everyone,
This thread previously was a discussion area for the Ouya Boot Menu feature during its early development.
It's now being transitioned to a support area. The new project description/download page is at:
http://forum.xda-developers.com/showthread.php?t=2499673.
Thanks!

CWM Bootloop
Hal9k+1 said:
Hello everyone, attached is the ZIP of an updated CWM Recovery IMG file.
This image is based on the latest stock Ouya kernel in GitHub. The kernel contains some newer HDMI code, which will hopefully increase the chance of getting the CWM graphics showing up properly. I also turned off HDMI’s HDCP in the compile (not needed for a utility partition such as this), and grabbed a patch from Kulve’s Ouya kernel fork to really ensure HDCP bypass.
More importantly, the image contains Tasssadar’s excellent work involving KExec-HardBoot. This technology should allow for the implementation of a “fastboot boot”-related capability from a running ROM, enabling kernel chain loading. The recovery image in particular will be a place to practice with KExec-HardBoot, and come up with a booting method that could eventually be flashed to the boot/kernel partition.
It is fine (and recommended) to fastboot to this image as a quick verification of things. However, it will be necessary to flash to the Recovery (“SOS”) partition for proper testing of KExec-HardBoot, since there’s an embedded reboot (to Recovery in this case) in there. Do *NOT* flash this to the Boot.
A simple chain load test can be done by extracting “zImage” from this image, and “initramfs.cpio.gz” from your current ROM kernel. (Included is “unmkbootimg” that can help here - runs on Linux.) Push these to /tmp on the Ouya while it is running this image. Then enter the Ouya shell and do:
kexec --load-hardboot zImage --initrd initramfs.cpio.gz --mem-min=0xA0000000 --command-line=”$(cat /proc/cmdline)”
kexec -e
It should come up with this new kernel under your current ROM’s environment. As verification, you should see kexec files under /sys/kernel.
I’m looking to implement a basic chain loading application. It would come up before the Recovery and ADB services, and do the following:
% Pause for a bit, to allow any Alt-SysRq keyboard action (jump to Recovery or Bootloader) that may be needed.
% Check for any attached USB mass-storage devices (e.g., thumb drive), and look for the file “kernel.img”. Pull it in and boot it if present.
% If that failed, then look to “/system/kernel.img” on the Ouya itself, and boot it.
% And if that didn’t pan out, then exit and allow Recovery/ADB services to come up.
I hope all of this will be of help to others along the way!
Click to expand...
Click to collapse
Will this help with the problem I have?..
New update today it downloads automatically and then reboot to CWM and it fail verification...reboot system and it does all over again?...Any ideas Plz

View2Askew said:
Will this help with the problem I have?..
New update today it downloads automatically and then reboot to CWM and it fail verification...reboot system and it does all over again?...Any ideas Plz
Click to expand...
Click to collapse
Sorry, I'm not sure I understand. It sounds like the new stock firmware update is failing to go in, perhaps because of consistent download corruption. Whether you're actually being dropped in to the recovery partition is unclear. You might try the download again with the other networking type (Ethernet vs WiFi). You might also just disconnect from the network for the time being, and see if you remain in the firmware without interruption. From there you can consider setting up ADB to see if you can administer the Ouya from a PC.
My post is more for the developers at heart, just in case my investigation piqued anyone's interest. Ideally the post would go in the Development section, but I evidently need a few more posts here to unlock that area.
Best of luck!

Dual booting
Yes, please do enable dual/multi booting
Is there something I can do to help in that regard?

kulve said:
Yes, please do enable dual/multi booting
Is there something I can do to help in that regard?
Click to expand...
Click to collapse
Thanks kulve, and thank you for the kernel patch set. I need to get familiar with the offerings there.
I don't see any blockages in my plan so far; I just need to start in and see what comes up. At least it's a better feeling than the dead-ends encountered with the U-Boot and regular KExec investigations.
Someone more enterprising could possibly port in the MultiROM project, but I'll stick with this. Will let you know if I get stuck.

My findings so far...
- I've finally decided that shutting off HDCP in the build does nothing to help avoid the funky pink/purple squeezed screen that sometimes appears when CWM comes up. With my Asus monitor, I see the issue when the monitor was in sleep mode. Likewise, if I can switch the monitor to HDMI input at the same time as starting Recovery, then it's fine. It may be possible to hack in a fix by somehow starting and closing an HDMI session shortly before CWM itself starts. (I don't want to fight this too hard but would be nice to resolve.)
- I see how to pull the kernel and ramdisk out of an Android image (on the Ouya itself), so that they could be passed to KExec-HardBoot. I've done it with a script as a test but it may end up in an executable.
- I tried out a USB thumb drive. It's detected but no block device is made available under /dev -- I've finally decided that support is likely in a kernel module, which does not exist on the Recovery image. I'm probably not going to sweat this due to the next item.
- I notice that the CWM application can read the Ouya power button as something comparable to a keyboard key press. Borrowing this capability may allow us to count the button presses in a limited time range, and thus boot an appropriate image. (Would be easier than dealing with the pairing of the controller, but at least still wouldn't require a keyboard.) With this line of thought, I'm thinking the main image could sit in /system while any alternates could be in /sdcard or /data.
So in general, studying the code of the CWM application appears to be the next direction. Thanks - feel free to send any ideas.

Hal9k+1 said:
- I've finally decided that shutting off HDCP in the build does nothing to help avoid the funky pink/purple squeezed screen that sometimes appears when CWM comes up. With my Asus monitor, I see the issue when the monitor was in sleep mode. Likewise, if I can switch the monitor to HDMI input at the same time as starting Recovery, then it's fine. It may be possible to hack in a fix by somehow starting and closing an HDMI session shortly before CWM itself starts. (I don't want to fight this too hard but would be nice to resolve.)
Click to expand...
Click to collapse
What does the rendering in CWM? Is it Android or something lower level? I think my kernel has better HDMI support but for that the software needs to use that explicitly instead of the default one as there is not internal LCD panel (/dev/graphics/fb0 vs. fb1).

kulve said:
What does the rendering in CWM? Is it Android or something lower level? I think my kernel has better HDMI support but for that the software needs to use that explicitly instead of the default one as there is not internal LCD panel (/dev/graphics/fb0 vs. fb1).
Click to expand...
Click to collapse
It does look to be low-level, as CWM directly opens /dev/graphics/fb0 and uses ioctl() on it. I've decided to try my own compile of CWM as it does look to be a nice base for the booting effort. Will definitely look to your patches for the improved HDMI when I'm all ready -- thanks!

Hal9k+1 said:
It does look to be low-level, as CWM directly opens /dev/graphics/fb0 and uses ioctl() on it. I've decided to try my own compile of CWM as it does look to be a nice base for the booting effort. Will definitely look to your patches for the improved HDMI when I'm all ready -- thanks!
Click to expand...
Click to collapse
I noticed your comments related to this on the "Ouya CWM Recovery" thread but I'm not allowed to post there, so I'll post here.
Or actually repost as I'm mostly repeating myself. I had all kinds of issues in getting output using /dev/graphics/fb0 in Linux with the stock Ouya kernel but after some fixes the fb1 seems to work quite reliable. I get the output even if I don't have HDMI plugged in during the boot and it chooses the right resolution both for my TV (1080p) and for my monitor (1680x1050).

To all: I have updated the attachment that's present on the first post. I've synced to the latest Ouya kernel and pulled in the next HDMI patch set from Kulve. My HDMI issue now appears to be fully resolved.
Kulve: Thanks so much for refocusing me! I should have grabbed the patch from day 1, but that summary description had me a bit spooked. Note that I kept the HDMI/PRIMARY symbol enabled, so there's still only the fb0 device on this kernel.
With this handled and due to my thinking in general, I'm going to back away from trying to compile CWM itself -- I don't want to invest in CM10.1's environment at this time. Instead I will borrow CWM's UI and input technology to build an independent front-end with this Ubuntu/glibc environment I have working. My idea is to release another Recovery image when that's ready so we'll have a chance to practice/debug before moving to the Boot image.

Hal9k+1 said:
Kulve: Thanks so much for refocusing me! I should have grabbed the patch from day 1, but that summary description had me a bit spooked. Note that I kept the HDMI/PRIMARY symbol enabled, so there's still only the fb0 device on this kernel.
Click to expand...
Click to collapse
Hit the Thanks button
Anyway, do you have your kernel source code somewhere? Being able to use multiple resolutions on HDMI while keeping it as primary might be something that many Ouya Android gamers want as they might be able to play at 720p then.

ooo nice, ill try it out and see what happens

kulve said:
Hit the Thanks button
Anyway, do you have your kernel source code somewhere? Being able to use multiple resolutions on HDMI while keeping it as primary might be something that many Ouya Android gamers want as they might be able to play at 720p then.
Click to expand...
Click to collapse
Done! :laugh:
My modified files were tarred up and placed in the ZIP; let me know of any possible issue. I'm not planning on a GIT account, but anyone may feel free to pull anything back to their project. Also I understand that sticking with HDMI/PRIMARY may reduce some of the capability/flexibility you're seeing, but I wanted to stay honored to the Android/CM layout expectation if possible.

Hal9k+1 said:
Done! :laugh:
My modified files were tarred up and placed in the ZIP; let me know of any possible issue. I'm not planning on a GIT account, but anyone may feel free to pull anything back to their project. Also I understand that sticking with HDMI/PRIMARY may reduce some of the capability/flexibility you're seeing, but I wanted to stay honored to the Android/CM layout expectation if possible.
Click to expand...
Click to collapse
Any chance of getting some concise installation instructions?

zondajag said:
Any chance of getting some concise installation instructions?
Click to expand...
Click to collapse
Here's a quick executive summary until I can update the 1st post.
I'm reminded there's another XDA project (Ouya Safe Recovery) with a very similar goal as this, and works by reversing the Boot and Recovery concepts. However it's completely incompatible with us, and those users should not be doing any flashing -- at least not until we have a Boot image ready.
First step is to get rcvy092613.img to the Ouya in its /tmp directory. This may be done with an "adb push rcvy092613.img /tmp" command, or can by done through Secure Copy if an appropriate SSH server is set up.
Next step is to access the Ouya shell, either running from the main ROM or from a Recovery ROM. Be sure to become root (ensure "#" in the prompt) as needed.
Run the following to back up the old image:
cd /dev/block/platform/sdhci-tegra.3/by-name/
dd if=SOS of=/sdcard/old_rcvy.img
Make sure the new image is correct - should see "2a882d1ba8c2d543503cacb49ab0d397":
md5sum /tmp/rcvy092613.img
On to flashing Recovery:
dd if=/tmp/rcvy092613.img of=SOS
Now wait at least a full minute in case there is any internal flushing still taking place. And to finish up:
sync
reboot recovery

Aye....never enough time to tinker it seems, especially with getting over this flu.
At this point I have my own compiled code splitting the boot image file, as well as counting the power button clicks.
I want to see if I can make a welcome/instruction screen, probably by getting CWM's minui down to its core essence. From there it will hopefully just be normal integration work to achieve a new Recovery for testing.

Everyone, a new boot menu is ready for testing. Please read through the first post to see if you'd like to try it out. Apologies once again for the delay in getting this ready.

Hal9k+1 said:
Everyone, a new boot menu is ready for testing. Please read through the first post to see if you'd like to try it out. Apologies once again for the delay in getting this ready.
Click to expand...
Click to collapse
Did I read correctly that the image support multibooting?

kulve said:
Did I read correctly that the image support multibooting?
Click to expand...
Click to collapse
Hi again Kulve. It supports three Android boot images - the main + two alternates: kernel.img, kernelA1.img, & kernelA2.img. It prefers to see the selected image in /sdcard, but will shift to /system as needed.
So, it is multi-booting, but you should keep in mind that there is still only the single /system partition. So installing two normal ROMs together probably won't work out, due to that common storage area. However, one of the ROMs could be based out of /system, while any others could use some form of external/networked storage. Note that the Android image format contains both the kernel and the initial ramdisk, so I feel that a multi-boot arrangement could be done.

Hal9k+1 said:
Hi again Kulve. It supports three Android boot images - the main + two alternates: kernel.img, kernelA1.img, & kernelA2.img. It prefers to see the selected image in /sdcard, but will shift to /system as needed.
So, it is multi-booting, but you should keep in mind that there is still only the single /system partition. So installing two normal ROMs together probably won't work out, due to that common storage area. However, one of the ROMs could be based out of /system, while any others could use some form of external/networked storage. Note that the Android image format contains both the kernel and the initial ramdisk, so I feel that a multi-boot arrangement could be done.
Click to expand...
Click to collapse
My kernel is hard coded to mount the Debian (or whatever) rootfs from /dev/sdaX so Ouya's internal partitioning doesn't matter. It would be really cool to be able to put kernelA1.im to /sdcard, an USB flash drive to the USB port and boot to Debian without tinkering with adb/fastboot/etc. on a PC.
I'm not currently using any initrd-images but adding something simple should be straightforward.