Database Develop

More Cupcake questions

"cupcake" development branch
A link to this was posted on the G1-Hackers mailing list. I haven't seen it here yet so I figured I would share. You can find the original post at http://source.android.com/roadmap/cupcake.
---------------------------------------------------------------------------------
"cupcake" development branch
From http://source.android.com/roadmap:
During Android's transition to anopen-source project, some development has continued to happen in aprivate branch. We are working to move the rest of these changes intothe open as soon as possible, and all future open-source work willhappen in the public git repositories. All changes that have alreadybeen submitted to the public repositories will be merged into the newercode base, so nothing should be lost.
The Android team has begun pushing these changes to the public git repositories, in the "cupcake" branch.
About this code drop:
The "cupcake" branch is a read-only mirror of the private Android branch.cupcake is still very much a work in progress. It is a development branch, not a release.
Thefirst drop is a large roll-up commit of all of the changes sincerelease-1.0. We will transition to regular, smaller roll-up drops,ultimately pushing individual commits.The cupcake branch willbe merged into the master branch, so that all of the public patches canbe used with the new code base. None of the commits in the publicrepositories will be lost, unless they no longer make sense or areobsoleted by the new code base. Due to the United States' holidayseason, though, this may not be finished until early January.
To check out the cupcake branch:mkdir cupcake # create a new client directory
cd cupcake
repo init -u git:/android.git.kernel.org/platform/manifest.git -b cupcake
repo sync
Notable changes introduced in cupcake:
Applications
MMS
New features
Save attachments from MMS.
Significant bug fixes
Faster conversation list scrolling
Email
Significant bug fixes
Accounts that were marked "never check" are not auto-checked.
Date & time displayed using user preference (e.g. 24 hr vs. AM/PM).
cc: displayed in message view.
Relaxed POP3 parser rules so it works with non-compliant email servers.
Password quoting bugs in IMAP. Makes it work for users with funny chars in their password (e.g. spaces).
Various sources of errors in auto & manual account setup.
Improvements on how we report various connection errors. Makes it much easier for user to diagnose failed account setups.
New-mail notifications for POP3 accounts.
Properly recover from POP3 connection failures, so that the next connection has a chance of working properly.
Remove automatic accounts setup entries that were broken or nottestable. Minor fixes to a few of the remaining entries. Improvementsto warning dialogs used for a few special cases.
New accounts are now set to check every 15 minutes (instead of defaulting to "never").
Fixed a bug causing approximately 1 in 25 outbound messages to freezeup the IMAP connection (to a Gmail based server) when transferred tothe Sent folder. This broke the entire connection so new messagescould not be downloaded either.
Unit test framework so Email can be extended & tested more reliably.
Fix IMAP manually-created accounts so message delete works properly.
Alarm Clock
Significant bug fixes
Alert now plays audio/vibe directly, rather than through AlarmManager.AlarmClock alert starts playing audio/vibe in its IntentReceiver,rather than on activity start. These changes should prevent alarms frombeing blocked by modal dialogs.
Package Installer
Significant bug fixes
Bugs related to replacing existing applications.
Settings
New features
New menu option to list running processes in Settings->ManageApplications.
Music
New features
Music playback fades in after suspending for phone call.New media search intent allows for 3rd party apps to launch or respondto media searches based on artist, album, or title.
Affects: MusicPlayer, YouTube, Browser applications.
Browser
New features
Updated WebKit browser core, synced with Nov 2008 WebKit version.
Support for new, optimized JavaScript engine (SquirrelFish).
Copy/ paste is enabled in the browser. To copy with touch, press and holdthe shift key and select the text. Releasing the shift key or endingthe touch drag copies the text. To copy with the trackball, press andhold the shift key, move the cursor to the selection start, click thetrackball, and move the trackball to the extend the selection.Releasing the shift key, or clicking the trackball a second time,copies the text.
Find is enabled in the browser. To find text, choose it from the menu and type the text to find.
Drawinghas been sped up substantially by supporting partial contentinvalidates and partial screen invalidates. Pages with animations are5x faster.
VoiceDialer
New features
VoiceDialer supports 'open app' command
Camera/Gallery
New features
Video recorder mode
Share intent for videos
Video thumbnailsLocal file playback
Download manager
New features
Support for HTTP codes 301, 302, 303 and 307 (redirects).
HTTP code 503 is now handled, with support for retry-after in delay-seconds.
Downloads that were cleanly interrupted are now resumed instead of failing.
Applications can now pause their downloads.
Retry delays are now randomized.
Connectivity is now checked on all interfaces.
Downloads with invalid characters in file name can now be saved.

"cupcake" development branch continued
Framework
New features
Support of touch events in WebView.New JavaScript engine (SquirrelFish) in WebView.
Input method framework, for soft keyboards and other on-screen inputmethods. Includes new APIs for applications to interact with inputmethods, and the ability for third party developers to write their owninput methods.
Access to the raw audio data for playback and recording from application code.
New PendingIntent.FLAG_UPDATE_CURRENT option.
Support for top-level boolean resources.
Tactile feedback to the LockPatternView. Tactile feedback can beenabled/disabled by going to Settings > Security & location andthen checking/unchecking "Use tactile feedback". Note that this can beused independently of the visual feedback of the lines ("Use visiblepattern"). Thus it gives users a middle ground between showing thelines on the screen and having no feedback at all.
PackageManager changes to support un-installation ofpartially installed applications. Added new flagPackageManager.GET_UNINSTALLED_PACKAGES to include partially installedapps in all relevant PackageManager api's. ManageApplications screennow lists such partially installed apps and the user can uninstallthese applications completely.
Support third party updates of system applications. Newmenu options in Settings->ManageApplications to list updated systemapplications.
Framework support to list current running processes. New API in ActivityManager.
Framework feature to declare required configurations by applications.New manifest attribute uses-configuration in android manifest.
Hardware accelerated video encode (video recorder) in opencore.
Simplified SREC speech recognition API available.
Streaming audio I/O for applications.
Significant bug fixes
Fixed issues with saving state in the view hierarchy, so that you canproperly subclass from something like TextView and create your ownstate that inherits from that provided by TextView.
TextView now implements onKeyMultiple(), so that flinging the trackballwill result in accelerated scrolling. This required some changes tomovement methods, and included some improvements to the accelerationcomputed when flinging.
Framework bug fixes in PackageManager to share/un-share permissions for applications with shared uid's.Significant rework of Settings->ManageApplications Performance and UI enhancements.
Anumber of settings in android.provider.Settings.System were moved toandroid.provider.Settings.Secure. Only system software can modify thesesettings. Additionally, a new permission, WRITE_SECURE_SETTINGS, isrequired to access these settings. The old constants in Settings.Systemhave been deprecated. It is possible to read settings values viaSettings.System using the deprecated constants. However, attempts tomodify these settings via Settings.System will result in a log messageand the setting value will be left unchanged.Many bug fixes in the media framework
Bluetooth
New features
Support for A2DP & AVRCP profiles.
Significant bug fixes
First connection after pairing always fails on many carkits.
Mini Cooper and some late model BMW cars fail to use Bluetooth or take 2 minutes for Phone Book transfer.
System software
New features
New kernel based on Linux 2.6.27.
Improvements to the wakelock API.
Work to transition to the USB Gadget Framework underway.
Basic x86 support.
Radio & Telephony
New features
SIM Application Toolkit 1.0.
Green CALL button is no longer a shortcut for "add a new call". Thishas been a rarely used feature and confusing if triggered accidentally.
Longer in-call screen timeout when using the speakerphone.
"Show dialpad" / "Hide dialpad" item added to the in-call menu, to make it easier to discover the DTMF dialpad.
Significant bug fixes
An obscure case where the Phone UI could cause the device to not go tosleep on its own. This would happen if user bails out of the in-callscreen by hitting HOME, followed by the call disconnecting remotely. Don't allow a single tap to open the in-call dialpad. Itis now required to touch and drag it. This makes it much harder toaccidentally open the dialpad by touching the screen with your face.
Developer Tools
New features
Enable handset manufacturers to extend the Android SDK with add-ons. SDK add-ons will include:
systemlibraries to let developers use additional APIs provided by handsetmanufacturers or from other 3rd party vendors that handsetmanufacturers chose to include
emulator system images,skins, and hardware configuration to let developers test theirapplications on their Android implementation
This is work-in-progress. Please note that the latest Android SDK (Android 1.0 SDK, Release 2) is not compatible with the SDKplugin in the new branch, please use ADT 0.8.0. SDK add-on support is planned for future SDK release.
Build System
New features
The functions in build/envsetup.sh should be much more useful

nice, this is some secret undercover stuff that is much needed!! you all rock!
hbguy

I'm wondering would it be available to install for non-jailbraked phone?

worry said:
I'm wondering would it be available to install for non-jailbraked phone?
Click to expand...
Click to collapse
We are talking about Android source code here. It would need to be compiled appropriately to even flash to any phone. Your phone would still subject it to the same key test before it will flash it. So, No this won't work... Yet. Hopefully we will find a way to sign these images with the OTA keys instead of just test keys as we do now.

"Chicken Soups for Andy Phones"

Yes, I am aware of you should compile it first.
So you are saying, since it is not officially signed by google, you'll be able to install it only on dev or has-proper-boot-image phones?

wait, how do we get all these updates in the future though? sdk?
also what you mean as finding a way to sign these images with ota keys instead of just test key? meaning with jf's mod rc30 we could get these update?
hbguy

man, well these were a few of the things that i wanted to see changed its good that they are keeping in touch with the ppl runnin the app. this is very compelling information. can i suggest and addendum to the title, something alluding to the "update" nature of this dev team. i dont think theres a date, but ill def be willing to pick a G1 back up for that, esp if they managed to make a few of the processes faster.

hbguy said:
wait, how do we get all these updates in the future though? sdk?
also what you mean as finding a way to sign these images with ota keys instead of just test key? meaning with jf's mod rc30 we could get these update?
hbguy
Click to expand...
Click to collapse
Cupcake can't be built to run on Dream hardware yet. Not to worry as an OTA RC with the cupcake code drops should be available by year's end or early Jan 09.

Support third party updates of system applications. New menu options in Settings->ManageApplications to list updated system applications.
Click to expand...
Click to collapse
I haven't had a chance to look into it too much but, depending on the applications and files made accessible, this looks very promising. Things like the autorotating browser, maybe even skinning, could potentially be "legitimized" and no longer require root.

so how would one go about compiling to run on the dream?

korndub said:
so how would one go about compiling to run on the dream?
Click to expand...
Click to collapse
Right now...... You wait. There isn't 100% of the code here. Nothing specific to the dream hardware etc. I am hopeful we will be seeing things come soon though.
As far as what I meant about the keys... Right now in order to be able to flash an update that is signed with test keys, aka the keys we have right now, you need to use an exploit to gain root access and modify the keys the system looks for when updating. There are two possible ways that I see to get OTA RC30 flashed with with an unofficial image. The first way is for some ingenious person to find an exploit that can be used to obtain root again and therefore be able to change the keys the system looks for. The other option would be for someone to come up with a way to sign the image with the OTA keys.

kronarq said:
Right now...... You wait. There isn't 100% of the code here. Nothing specific to the dream hardware etc. I am hopeful we will be seeing things come soon though.
As far as what I meant about the keys... Right now in order to be able to flash an update that is signed with test keys, aka the keys we have right now, you need to use an exploit to gain root access and modify the keys the system looks for when updating. There are two possible ways that I see to get OTA RC30 flashed with with an unofficial image. The first way is for some ingenious person to find an exploit that can be used to obtain root again and therefore be able to change the keys the system looks for. The other option would be for someone to come up with a way to sign the image with the OTA keys.
Click to expand...
Click to collapse
kronarq is there a way to merge the existing source with the cupcake to fill in the parts that are missing?

Anyone else having problems pulling the source with repo?

hbguy said:
nice, this is some secret undercover stuff that is much needed!! you all rock!
hbguy
Click to expand...
Click to collapse
This was not "undercover" work. Google wanted to be able to work on stuff, yet release the G1 with a semi-stable firmware.
kronarq said:
We are talking about Android source code here. It would need to be compiled appropriately to even flash to any phone. Your phone would still subject it to the same key test before it will flash it. So, No this won't work... Yet. Hopefully we will find a way to sign these images with the OTA keys instead of just test keys as we do now.
Click to expand...
Click to collapse
This won't be the case. This is an official Google release, meaning when they merge them together in January, they will release an OTA update with all of these features.

I'm hoping there will be an OTA update with all these new goodies, but just because google is rolling "cupcake" into the open-source project, that does not mean that it will get rolled out to our G1's. That's up to T-Mobile and HTC. Let's just keep our fingers crossed.

Ok, maybe I'm missing something, but where are people getting the idea that this is not dream specific? From how I read it these are all things that are being built into the main source and as such will be compiled as an ota as other updates have been done in the past. Someone enlighten me here as I'm just not seeing the "specific" requirements people are putting on this? I'm no coder, but it doesn't look like anything more then just enabling what was already there or planned on being there. [/rant?]

MMTest97 said:
Ok, maybe I'm missing something, but where are people getting the idea that this is not dream specific? From how I read it these are all things that are being built into the main source and as such will be compiled as an ota as other updates have been done in the past. Someone enlighten me here as I'm just not seeing the "specific" requirements people are putting on this? I'm no coder, but it doesn't look like anything more then just enabling what was already there or planned on being there. [/rant?]
Click to expand...
Click to collapse
Agreed... everything that is dream specific is either on the android git repository or can be extracted from stock G1 Firmware

MMTest97 said:
Ok, maybe I'm missing something, but where are people getting the idea that this is not dream specific? From how I read it these are all things that are being built into the main source and as such will be compiled as an ota as other updates have been done in the past. Someone enlighten me here as I'm just not seeing the "specific" requirements people are putting on this? I'm no coder, but it doesn't look like anything more then just enabling what was already there or planned on being there. [/rant?]
Click to expand...
Click to collapse
Everything in the open source repository should be non-device specific (with the obvious exception of stuff like binary drivers). The repo will build an emulator image. To build for dream, there are some additional instructions. However the cupcake branch cannot be built for Dream at this time, so it is definitely not Dream-specific.
Datruesurfer said:
Agreed... everything that is dream specific is either on the android git repository or can be extracted from stock G1 Firmware
Click to expand...
Click to collapse
The differences between G1 and the repo extend beyond just Google-proprietary apps. There are subtle differences in the framework too.

Build camera/camcorder/video for eclair/froyo.

I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...

Bump. Totally interested. If OP already got an answer, please share.

Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?

I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.

Please test ReelPortal video chat/conference app

So far my app is working well on the Archos 70/101 and Viewsonic gTablet:
http://forum.xda-developers.com/showthread.php?t=908613
http://forum.xda-developers.com/showthread.php?t=918551
These devices are on Android 2.2 and have a single front camera. The app can't access the front camera on the Samsung Galaxy Tablet, because supposedly Android 2.2 doesn't support multiple cameras natively, according to the Adobe forums.
Since the Nexus S has Android 2.3, I'm curious to find out if it would allow my app to work properly. You can download the apk from my first post in the Viewsonic thread. And please make sure you get Adobe AIR 2.5.1, preferably from the Android Market. Note: on the ReelPortal app, pressing the webcam button allows iterating through all available webcams (e.g. front cam->back cam->pause).
Please post feedback if you try it. Thanks.

I'm not sure why but I get stuck on connecting to server.

kenvan19 said:
I'm not sure why but I get stuck on connecting to server.
Click to expand...
Click to collapse
hmm...does it happen if you try again? if it keeps getting stuck with the apk, can you try sign on via the web client at www.reelportal.com, and see if that goes thru...its the exact same code. if it works in one and not the other, then i'd need to track down if AIR 2.5.1 is having some kind of issues with Android 2.3. thanks.

reelportal said:
hmm...does it happen if you try again? if it keeps getting stuck with the apk, can you try sign on via the web client at www.reelportal.com, and see if that goes thru...its the exact same code. if it works in one and not the other, then i'd need to track down if AIR 2.5.1 is having some kind of issues with Android 2.3. thanks.
Click to expand...
Click to collapse
I tried a few times earlier but I decided to try again and it went through. However, unless I'm missing a setting it will not let me change to the FFC from the RFC.

kenvan19 said:
I tried a few times earlier but I decided to try again and it went through. However, unless I'm missing a setting it will not let me change to the FFC from the RFC.
Click to expand...
Click to collapse
button 10 (webcam toggle) allows you to iterate thru all the available cameras that AIR can detect....so initially the webcam is in paused mode (button 10 flashing red), pressing it once will turn on a camera, pressing it again will switch to the next camera....when the list end, it go to pause again...then repeat. at least that's what it does on the PC, and i'm hoping Android 2.3 allows it to do the same thing.

reelportal said:
button 10 (webcam toggle) allows you to iterate thru all the available cameras that AIR can detect....so initially the webcam is in paused mode (button 10 flashing red), pressing it once will turn on a camera, pressing it again will switch to the next camera....when the list end, it go to pause again...then repeat. at least that's what it does on the PC, and i'm hoping Android 2.3 allows it to do the same thing.
Click to expand...
Click to collapse
Ah, having cycled through that button a few times it merely turned on the RFC and then paused the feed which to me indicates that for some reason Air isn't picking up the FFC (I checked and I do have the most current version).

kenvan19 said:
Ah, having cycled through that button a few times it merely turned on the RFC and then paused the feed which to me indicates that for some reason Air isn't picking up the FFC (I checked and I do have the most current version).
Click to expand...
Click to collapse
ic...i'm disappointed to hear it's still not working, but thanks for doing the testing! i'll do some digging to see if there's some setting that need to be enabled.

reelportal said:
ic...i'm disappointed to hear it's still not working, but thanks for doing the testing! i'll do some digging to see if there's some setting that need to be enabled.
Click to expand...
Click to collapse
No problem at all, let me know if you wanted it tested later =) Good luck!

kenvan19 said:
No problem at all, let me know if you wanted it tested later =) Good luck!
Click to expand...
Click to collapse
I found that currently Adobe AIR 2.5.1 supports only ONE camera, and apparently it chose the rear one on the Nexus S .
So I'd have to wait for Adobe to add support for multiple cameras to AIR.
I wonder if there's a way to manually turn off the rear camera (e.g. disable the driver), and thus, make AIR defaults to the front cam.

paid app?
are we getting a free version for helping you test the App?
i don't see any reference to GPL on the topics you have linked
reelportal said:
So far my app is working well on the Archos 70/101 and Viewsonic gTablet:
http://forum.xda-developers.com/showthread.php?t=908613
http://forum.xda-developers.com/showthread.php?t=918551
These devices are on Android 2.2 and have a single front camera. The app can't access the front camera on the Samsung Galaxy Tablet, because supposedly Android 2.2 doesn't support multiple cameras natively, according to the Adobe forums.
Since the Nexus S has Android 2.3, I'm curious to find out if it would allow my app to work properly. You can download the apk from my first post in the Viewsonic thread. And please make sure you get Adobe AIR 2.5.1, preferably from the Android Market. Note: on the ReelPortal app, pressing the webcam button allows iterating through all available webcams (e.g. front cam->back cam->pause).
Please post feedback if you try it. Thanks.
Click to expand...
Click to collapse

AllGamer said:
are we getting a free version for helping you test the App?
i don't see any reference to GPL on the topics you have linked
Click to expand...
Click to collapse
the app is all free....even the server executable is free...so you can run it on your own server....you can also download the apk from AppsLib and Appoke...the web client is at www.reelportal.com...
sorry, i don't have much time to work on the legalese stuff...i prefer coding

reelportal said:
I found that currently Adobe AIR 2.5.1 supports only ONE camera, and apparently it chose the rear one on the Nexus S .
So I'd have to wait for Adobe to add support for multiple cameras to AIR.
I wonder if there's a way to manually turn off the rear camera (e.g. disable the driver), and thus, make AIR defaults to the front cam.
Click to expand...
Click to collapse
Well if you figure it out man I'm always happy to blow up my phone testing stuff. Let me know
Sent from my Darkginger CM7 Google Nexus S!

kenvan19 said:
Well if you figure it out man I'm always happy to blow up my phone testing stuff. Let me know
Sent from my Darkginger CM7 Google Nexus S!
Click to expand...
Click to collapse
Hmm...can you compile the Android 2.3 source code? Check out the diagram here
http://source.android.com/porting/camera.html
I believe the "Camera" green box in "Libraries (user space)" need to be modified and recompiled. That is, we need to modify function open() in class android.hardware.Camera:
public static Camera open() {
int numberOfCameras = getNumberOfCameras();
CameraInfo cameraInfo = new CameraInfo();
for (int i = 0; i < numberOfCameras; i++) {
getCameraInfo(i, cameraInfo);
if (cameraInfo.facing == CameraInfo.CAMERA_FACING_BACK) {
return new Camera(i);
}
}
return null;
}
As you can see, it's actually searching for a back facing camera. I would change the logic so that it read in the camera index from some file, e.g. defaultCamera.txt, so the user can change it any time without recompiling.
If you or someone who has compiled Android before, it would be easy to make this mod. Unfortunately, I don't have the resources to do it.

reelportal said:
Hmm...can you compile the Android 2.3 source code? Check out the diagram here
http://source.android.com/porting/camera.html
I believe the "Camera" green box in "Libraries (user space)" need to be modified and recompiled. That is, we need to modify function open() in class android.hardware.Camera:
public static Camera open() {
int numberOfCameras = getNumberOfCameras();
CameraInfo cameraInfo = new CameraInfo();
for (int i = 0; i < numberOfCameras; i++) {
getCameraInfo(i, cameraInfo);
if (cameraInfo.facing == CameraInfo.CAMERA_FACING_BACK) {
return new Camera(i);
}
}
return null;
}
As you can see, it's actually searching for a back facing camera. I would change the logic so that it read in the camera index from some file, e.g. defaultCamera.txt, so the user can change it any time without recompiling.
If you or someone who has compiled Android before, it would be easy to make this mod. Unfortunately, I don't have the resources to do it.
Click to expand...
Click to collapse
I do not know how to compile nor do I have the resources either lol

kenvan19 said:
I do not know how to compile nor do I have the resources either lol
Click to expand...
Click to collapse
ah too bad, cuz this mod would allow all other video chats program to work with the FFC too, not just my app.

Odd. I use fring with my wife and it uses the ffc. Perhaps if I posted the apk for that you could tear it apart and see how it accesses the ffc
Sent from my Darkginger CM7 Google Nexus S!

kenvan19 said:
Odd. I use fring with my wife and it uses the ffc. Perhaps if I posted the apk for that you could tear it apart and see how it accesses the ffc
Sent from my Darkginger CM7 Google Nexus S!
Click to expand...
Click to collapse
There's two "open()" functions in Android 2.3, and perhaps Fring uses the new one:
public static Camera open(int cameraId) {
return new Camera(cameraId);
}
Most older software (for Android 2.2) uses the older open(), which doesn't have "cameraId" passed in, so Google hardcoded it to the RFC, which I think is bad coding practice . My app relies on Adobe AIR, which currently uses this old "open()" function.
Other software may access the FFC on Android 2.2, but they'd have to use the manufacturer's proprietary interface, which breaks when moving to Android 2.3.

New skype release today!

http://techcrunch.com/2011/06/30/skype-for-android-now-support-video-calls-works-over-wifi-and-3g/
Not working on the transformer or the gtablet yet. But hopefully we'll get a working app soon either from microsoft or from the dev community.

I tried a patched version that took out the restriction. It force closes when trying to accept a call and enable video, but the settings and buttons show up...

gtab
Can some one upload the APK when they get the new video skype so we can try this on the gtablet.

Here's the issue, I think...
The support for video chat requires Gingerbread. If I understand correctly, this is because GB finally introduced a standard API to access the front camera.
Until Gingerbread did this, all apps that accessed the camera needed their own drivers to do so (there was no standard camera driver to access back then, which is why apps needed to have built in support for specific devices).
Skype is using this to their advantage by releasing an app that doesn't require much code change to support device almost any device (why they are only supporting specific devices at a time is mostly political AFAIK).
But here's the problem- There is no official Gingerbread for our hardware! All the GB roms we have are hacked together with peices of code with missing native hardware drivers since they don't exist! That means, I would guess, the new Gingerbread camera API is USELESS BECAUSE GINGERBREAD LACKS THE NATIVE HARDWARE SUPPORT!
Yes, this is awfully depressing. But without a real Official Gingerbread rom, unless Skype starts offering Froyo camera support (unlikely since they would go back to the old problem of suporting each camera hardware individually), this is just not going to happen.
Maybe if the rumors of official Honeycomb drivers turn out to be true, and Skype eventually supports video with HC (another *IF*), then maybe. But that's a long way off.
Very depressing- I was very excited about this working until I came to this realization.

Wrong thread.

How's that? Looks like the correct thread to me.

Dishe said:
How's that? Looks like the correct thread to me.
Click to expand...
Click to collapse
I meant myself. I put a post here and then realized it was meant for elsewhere. Multiple windows openned.

Here's the apk for the new released skype vid app.

[ROM][JellyBean][4.1.1]Unofficial CyanogenMod 10 (WIP)

Ill organize this and make it look good later...but for now lets get to the point:
This is an Android 4.1.1 Jellybean (JB) ROM, it is an unofficial version of a popular after market firmware known as CyanogenMod. it is essentially AOSP with some cool added features by the CyanogMod team -this has no sense, and it is not based off a sense stock rom
Befor i even begin stating what works and doesnt i would like to thank Synergy, he is the one who got this started, he is the one who got the first version of this to boot...unfortunately he quit due to frustrations with HTC and how hard they have made things, i am just picking up where he left off...
What works:
WiFi
Audio
Calls? **check out not working***
SMS...aka texting
home button -I know it sounds funny, but for a while the home button didnt work on CM10
Not working:
Data
Bluetooth
GPS
MMS...aka picture messaging and othe multimedia messaging (will work as soon as data works)
Camera
Video-likely a driver issue...mx player allows for videos to be played but they are extremely laggy...only tested with mp4's of videos i filmed while on ICS
Calls? i need people to test calls...i believe if you have ATT in call mic wont work...so the other end wont be able to hear you work...i cant verify it...but if you use any other carrier (even if you have an ATT vivid but are unlocked and using a differnt carrier) then i believe in call mic does work...i need people to verify...so make some calls and let me know if they work and if the other line can hear you, and also let me know what carrier you have
Instructions
1) Wipe data/factory reset
2) Wipe cache
3) wipe dalvic cache
4) flash CM10
5) flash GAPPS
S-ON?
just fastboot flash the boot.img located in the zip then follow the instructions above
Download
CM10
http://goo.im/gapps/gapps-jb-20120726-signed.zip
All versions of GAPPS: http://goo.im/gapps/
what are GAPPS? GAPPS are just google applications...like Play store, GMail...ETC, its not necessary...but if you wanna get any apps your gonna need it
Other stuff...
Featuring Synergys Kangbang-rebirth kernel...supports OC up to 2052 MHz...or about 2 GHz (you can change clock speed under settings/performancee
Features a built in file explorer...not included in most cm builds
Thanks/Credits
once again...synergy...cant thank him enough
kevstheblast, he also worked on cm10 for a little bit
TeamCodefireAOSP - most of my device trees are from you...some with slight modifications
DragunKorr - i am using your msm8660-common device tree
...ill add to this list later, but its late and i need to finish my homework and go to bed
-Its time to bring the vivid back to life...CM10 opens the door to numerous AOSP based JB ROM ports...lets get this stabilized!

Screenshots...coming soon

How to build:
1) First you need to sync CM10 source:
A)
Code:
mkdir cm10
-this creates a folder for where the source will be downloaded
B)
Code:
cd cm10
-this navigates you to the folder the source will be downloaded in
C)
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
-this initializes the repo...gets it ready/prepares for the sync
D)
Code:
repo sync
-this downloads the source...depending on the rom can range from 8-15+ GBs!
E)
Code:
./vendor/cm/get-prebuilts
-downloads necessary prebuilts for CM10
2) Now you need to clone my local manifest:
A)
Code:
cd ~/cm10/.repo
-this navigates to where the local manifest will be cloned
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
-this makes a copy of the local manifest in your .repo folder
C)
Code:
repo sync
-downloads the sources that were added by my local manifest
3) Now you can build:
A)
Code:
. build/envsetup.sh
-prepares the system to build
B)
Code:
lunch
-opens the device menu for you to choose your device
c)
Code:
6
***or whatever number the holiday pops up as*** -the item number of the device
D)
Code:
mka bacon
-begins the build...can take a few hours depending on your computers CPU
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
How to build other roms from source:
1) First you need to sync there source:
A)
Code:
mkdir workingdirectory
you can name "workingdirectory" whatever you want...i suggest the name of the rom for organization purposes...so for AOKP i would do "mkdir AOKP"
B)
Code:
cd workingdirectory
C) repo init there manifest...for AOKP:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb
found from here: AOKP...so basically find the roms source, then find there manifest, type "repo init -u gitreadlinkhere -b branchnamehere"
D)
Code:
repo sync
2) Now you need to clone my local manifest: (this gets you all the device specific stuff...device tree, common device tree, kernel...ETC)
A)
Code:
cd ~/workingdirectory/.repo
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
C)
Code:
repo sync
3) Now you can build:
A)
Code:
. build/envsetup.sh
B)
Code:
lunch
c)
Code:
6
***or whatever number the holiday pops up as***
D)
Code:
mka bacon
***please note, this may or may not work for every roms source...some require a little extra work...but this should get you the core files needed...look at how other official devices are set up, try and match them...specifically in the workingfolder/vendor***
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
SOURCE
https://github.com/mg2195
https://github.com/KangBangKreations/KangBanged-Kernel/tree/kb-rebirth

CHANGELOG
10-08-2012
-First real release/started thread...

Post any bugs...and if possible get me some LOGCATS
To save a log to a file:
Code:
adb logcat > logcat.txt
Press
Code:
ctrl+c
once you are done collecting information
Then upload the logcat.txt as an attachment so I can look at it with ease...DO NOT JUST COPY AND PASTE THE LOGCATS HERE! that just hogs space and is a pain for those on mobile devices...if you really want to copy and paste there is this great site called pastebin paste it there, hit submit and post the link here

Absolutely awesome man! I love the persistence . Picking up where others left due to frustration, so x10 thumbs up for the dedication!
Will definitely be testing this out and posting back as much bug info I can get you (I will edit this, not just a thank you post). I can't agree more, hopefully you can bring the Vivid back to life . I have faith!
LOG/BUG UPDATE:
Ok so whooo again, great build! Very smooth and speedy, just love this phone without sense (sense works good, but this JB is so refreshing - 0 lag).
Cant wait for the bugs to be worked out, it will be very worth it. Anyway, onto the my report:
_______________________
First boot, it restarted after the white and green HTC screen, so anyone testing no worries when it reboots.
Everything loaded up pretty quickly, and no FCs or bugs besides the known ones. I did notice I think its new probably because of the work you did to get audio to work (messing with the display), when rotating it sometimes makes the screen go all funky (part of the current image is displayed like 4 times in a horizontal line for about .5 seconds) then its fine. So not a big deal.
Bugs:
I tested the calls using my VM, sound works . Now if I try to change the volume of the headset speaker it changes ringer volume I believe, as I didnt notice a difference in volume when the VM automation was talking to me. It also showed a telephone, not w.e it supposed to be (shows same image as not in a call - like its not realizing its 'in' a call). I tried to record a new greeting message, but mic does not work still (tmo).
Data is still the same [as your test builds], blinks E real quick (.5 seconds) then goes away. Under phone status it shows Mobile network type as EDGE:2. Then DCed for network state (changes to connected for the .5 secs when E pops up). Changing bearer to LTE or unspecified doesnt change anything. Also forcing LTE/GSM/WCDMA or GSM/WCDMA Preferred doesnt change anything either.
Camera I tried but FCs with gallery. So also with a few other apps that wouldnt be linked to gallery (though gallery works), no go. They all FC for some reason.
Now no worries, I got you logcats of everything here. I tried to slim them to just the problem although I dont know exactly where the problems end in these huge scripts lol. So I apologize for the length of some, rather you get more than less and I miss the problem line.
Making Calls while changing Volume: http://pastebin.com/gXmiHrCc
Changing bearer to LTE: http://pastebin.com/9hXBiNmS
Clicking Enable Data: http://pastebin.com/xH3AWUp4
Stock Camera: http://pastebin.com/xRsyUTmj (Sorry for lengthy, couldnt tell if it was looping or just straight erroring out million times x( )
Camera Illusion: http://pastebin.com/NFxf2nxd (Again sorry for lenthy, same ^^)
Camera 360: http://pastebin.com/YmRfXBxJ
Maybe hopefully you can get some matching errors on the camera, narrow the problem on that. And hopefully you can figure out the data, thats really big. Same with mic of course. But, again, very good job first actual alpha build.

Unless you wanna damage your hearing....I don't suggest using DSP manager while wearing headphones...went to change the bass and as soon as I changed it my volume went to like full blast lol...definitely some work needs to be done there
Anyways its bed time for me
Sent from my Holiday using Tapatalk 2

Lied about going to bed...found a work around for video...
Go to settings/developer options
Make sure its on
Then disable hw overlays
-my mp4s now play...but they are really laggy...YouTube app now playa video s flawlessly now... maybe its the resolution/quality?
Now I go to bed...
Sent from my Holiday using Tapatalk 2

Would love to try this now, but as this phone is my only phone, I'll have to wait. But once calls and data are working, I'd be more than happy to test out the rest for you. Thank you for your efforts!
Sent from my De-Sensed HTC Vivid using xda app-developers app

finally some JB love for Vivid. as soon as most of the features work, ill test it out.

Dear Santa.....

Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.

MisterSchnapps said:
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
Click to expand...
Click to collapse
Didn't think to test USB as it was working on previous builds...since it was previously working it shouldn't be to hard to fix
Sent from my Holiday using Tapatalk 2

It may be because data doesn't work lol, but I'm getting great battery life!
Anyways...doing some research...trying to figure out how to fix what's currently broken...
Also, it appears that many different devices have graphics/video problems caused by hw overlays....no real fix has been discovered except the work around I mentioned earlier about disabling hw overlays under developer options in settings
As far as USB...I think I might've deleted a line in accident that "defines" its function...
Once I get this stabilized I'll do a tutorial on how to build from source using my existing device sources and plug them into other source ROMs like aokp...
Sent from my Holiday using Tapatalk 2

:fingers-crossed:

Do both mics not work? Could we maybe use the camera mic instead?

Brand New said:
Do both mics not work? Could we maybe use the camera mic instead?
Click to expand...
Click to collapse
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***

mg2195 said:
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
Click to expand...
Click to collapse
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].

theslam08 said:
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
Click to expand...
Click to collapse
Thanks! I'll take a look later...and you have an Att vivid unlocked for T-Mobile?
Maybe in call mic will work for the velocity/raider...me having Att with a vivid...I don't really know, i just remember when syn was working on this he stated in call mic didn't work on Att...but he said it worked for other carriers...
I was able to use mic for voice search...so the problem isn't with the mic its self...has to be with the way the vivid handles calls...
Sent from my Holiday using Tapatalk 2

What about including as littlemount of HTC framework as possible for phone calls?
Just throwing ideas out hahah