Database Users

ICS just dropped to AOSP

Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f

Just read this on AndroidPolice. Very excited!!!

Game.....on!
Sent from my PG86100 using XDA App

Developers make some rom's!!!!!! (Please)

this thread should make its way over to the development section. Thanks for the find op
Update: Already there

I'm actually curious about how long it will take for someone to make an A500 ICS ROM based on this. There is bound to be someone to do it, but who gets the #1 spot?

Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1

They're not necessarily requirements, but more or less just recommendations. A more average computer could still compile ICS, but it will just take a lot longer. And I'm betting Thor will be the first to cook us a ROM. Hopefully soon
Sent from my HTC Glacier using xda premium

FloatingFatMan said:
Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1
Click to expand...
Click to collapse
Those are only recommendations for developer workstations. It is certainly possible to compile it even on a low-grade office PC if you give it a week.

Hence my saying it won't be soon...

FloatingFatMan said:
Hence my saying it won't be soon...
Click to expand...
Click to collapse
Your still not understanding my friend. Unless your definition of soon is in 30 minutes. Peter Alfonso that develops for the OG Droid and a few other devices compiled his in about 1 hour and 45 minutes. That was a laptop core i7 and 8gb of ram.
Thats not whats going to be time consuming. The hard part will be finding/getting the hardware inside our devices to work. I asked THOR on his forum about ICS on the iconia, his response:
done know for now... depends how many proprietary stuff the a500 uses....
I'm worried the camera, sensors and battery as these seam to be tampered with...
for the moment I'm busy with other stuff will see when I get some time to sneak a peak at the code...
Click to expand...
Click to collapse
Time will tell.

I'm sure FFM understands that. As you say, the hard part is getting the hardware to work, but with a slower machine, how many test builds can you do in a day? With a big fast machine that can build in a few hours vs a laptop that might take a few days can make a huge difference of when you get to your final release.
But hey.. i don't know anything, so why don't I just shut up...

It takes about 3.5 hours for me to build a new version of ICS. I'm on a 3 year old laptop which is why it takes so long. It would be great to have a much newer machine to build with as it would help to make things go faster.

So I guess that Google engineer was taling out of his butt then.

Open Source Hardware

www auraslate com
Hey guys here is an open source hardware tablet site... it might help those out there

johanngummy said:
www auraslate com
Hey guys here is an open source hardware tablet site... it might help those out there
Click to expand...
Click to collapse
Open Source, never pertains to hardware, because you don't chisel code on to a circuit board, its Open Design, in which they also offer full open source code for the said open designed tablet. Just saying.

3D printers with atom precision/accuracy are possible in theory, that would really make open source hardware possible

RolAr said:
3D printers with atom precision/accuracy are possible in theory, that would really make open source hardware possible
Click to expand...
Click to collapse
Except theory isnt reality.

Very cool!
Good luck with this project, looking forward to see where it goes. Boards still seem a bit on the expensive side...
http://www.auraslate.com/

sounds awesome, but from pieces of hardware to all components of a smartphone it's a hard way.. hope they will coming

Ha, u guys may heared about open moko? Far away from first android, open source hardware and linux, no one take attention, its almost dead, a phone using linux os, it was born before android, and yet still in birth state, jus cox it have very few supporters,and devs.
Sent from my HTC HD2 using xda premium

Anybody have tried this tablets? The website says it's open for deliveries. The 7 inch version is just 150usd
Adam Outler did an "unboxing" with the 10 inch version.
I'm interested with a review of any of the unit, have any suggestion?

garuhhh said:
Anybody have tried this tablets? The website says it's open for deliveries. The 7 inch version is just 150usd
Adam Outler did an "unboxing" with the 10 inch version.
I'm interested with a review of any of the unit, have any suggestion?
Click to expand...
Click to collapse
At least Adam's first impression (him being an actual device owner) and mine (based on reading through their site) is they are not nearly as open as they claim to be.
1-2 months ago they were providing ICS firmwares without kernel source - that's less open than any legitimate Android tablet manufacturer. Not sure if they've rectified these issues, but any vendor claiming to be open source/open hardware should NEVER have done that except by accidental error - however there was a post in their forums effectively saying they were withholding source.
http://auraslate.freeforums.org/kernel-for-ics-t53.html - found it, see auraslateadmin's post - This is UNACCEPTABLE from ANY company, ESPECIALLY one that claims to be open source. If you have provided a kernel binary to the public, you MUST provide source code upon request.
Auraslate's marketing of being "open" is a blatant lie - they keep talking about how open they are to sell devices, but then withhold kernel source.

[Documenting] Google's Nexus 10 MALI GPU memory leak *NOW RESOLVED*

Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced. I'm not the most technical of this crowd (I mean c'mon I am here at XDA!) so please forgive me and notify me of any needed corrections or clarifications.
---[Documenting] Google's Nexus 10 MALI GPU memory leak *UNRESOLVED*---
The Nexus 10, henceforth N10, is an Android tablet made by Samsung for Google. At launch in November 2012 the N10 was shipped with Android 4.2.0
*
Included in the N10 is a SOC (system-on-a-chip) from the Exynos line:
http://en.wikipedia.org/wiki/Exynos_(system_on_chip)
*
The Exynos uses a GPU made by ARM. The GPU component is the ARM Mali-T604.
http://en.wikipedia.org/wiki/Mali_(GPU)
*
Starting immediately after the N10’s launch there were reports of “random reboots”. At first not much was known about the exact cause of these reboots. The audience participating in these reports experienced varying degrees of testing results, especially as 4.2.1 and 4.2.2 updates rolled out. The majority of this discussion is captured in two threads:
https://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[1-25-false] *
and
http://forum.xda-developers.com/showthread.php?t=1998496
(*Note that the Google thread was erroneously marked ‘Answered’ after one of the OTA roll outs.)
*
The community was able to flush out that the memory/RSS use of Android’s surfaceflinger process seemed to be the victim of a memory leak, and that by monitoring the RSS value one could predict when the tablet would experience the degraded performance. Viktor.M then created this open issue report that focuses in on that:
https://code.google.com/p/android/issues/detail?id=54757
*
About that time a user named apstrand, who appears to either be an ARM developer or at the very least someone who is extremely knowledgeable in this area had found more exact and detailed info on this, and he posted it here:
https://code.google.com/p/android/issues/detail?id=52579
*
Matthew Fry began contacting Samsung, then in turn ARM, as he posted in one of the Google threads. Eventually he was able to get this response: "I can confirm that we were able to reproduce the issue in the stock Nexus 10 4.2.2 provided by Google. We were, however, unable to reproduce it with our release driver.
We will test the application again when the next release of the firmware for Nexus 10 is published."
*
From this point, knowing ARM has code that avoids the error, people began looking into working on the code themselves, and asking ARM for assistance. ARM has posted source code components for the T-6xx series of drivers here:
http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/
However ARM has also stated, “these components are not a complete driver stack. To build a functional OpenGL ES you need access to the full source code of the Mali GPU DDK, which is provided under the standard ARM commercial licence to all Mali GPU customers.” This means Samsung has an ARM DDK (Driver Development Kit), but to date has not released it/aspects of it to the public.
*
For now there appears nothing anyone can do without access to the ARM DDK.
*
EDIT/UPDATE: Since my original post here, a lot of activity happened in a short period of time. Many comments below capture this. I will add the history into this thread, but the big news is 4.3 is out for the N10 now and the community is testing. Like each time a new Android version has rolled out, community testing is "all over the place" with different people reporting different results. People who know how to measure the exact parameters on this bug are reporting it looks like it may be fixed! Its noteworthy though that there is some suspicion of other issues. Because I want to keep this first post based only on facts, I am going to wait a while and see the community results before posting an update that cant be backed up by actual data.
***
FINAL UPDATE: Ok, looks like its fixed now. I'm not saying they didn't morph it somehow to another issue, but I am saying the exact situation we were all focused on here is no longer going on w/ the 4.3 (4.3.x if you want to include the 3mb update.)

bigmatty said:
Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced.
Click to expand...
Click to collapse
Nice overview of the problem. I would add that one of the Android bugs you link to is marked as assigned, by none other than Jean-Baptiste Queru, the technical lead of the Android Open Source Project at Google. He also renamed the other issue, so it appears that Google is finally aware of the problem and working on it. Hopefully, this means a fix is forthcoming in the upcoming Android 4.3 release, but that is merely a hope on my part: I have no inside info.

bigmatty said:
Hi everyone, I'm not sure how useful this thread will be - but I hope it will be useful. As I've watched new N10 users come into the fold of finding and wanting to learn more about "the reboot problem" I realize the information on this topic is spread all over the place. I've tried to gather the information, as well as present it in a good fashion, such that there is a link/thread that can be easily referenced. I'm not the most technical of this crowd (I mean c'mon I am here at XDA!) so please forgive me and notify me of any needed corrections or clarifications.
Click to expand...
Click to collapse
Thank you, this thread was sorely needed. This seems like a really big mess-up on Google's part. Has there been a memory leak this bad before for any other device?

patsmike said:
Thank you, this thread was sorely needed. This seems like a really big mess-up on Google's part. Has there been a memory leak this bad before for any other device?
Click to expand...
Click to collapse
I don't think so. My Dad has a Nexus 7 and it doesn't have this issue at all. I really hope that 4.2.3 or 4.3 fixes this - it's making me completely lose patience with the device and I'm getting tempted to sell it. First the light leak issue and now this. Come on Google, you really are taking the piss here. I'm not sure how they could get it so wrong?!

bigmatty said:
...This means Samsung has an ARM DDK (Driver Development Kit), but to date has not released it/aspects of it to the public.
Click to expand...
Click to collapse
So this fix requires Samsung to do it.
Almost hate to say it but I really don't see it being fixed anytime soon...

I confirm that surfaceflinger is f***ed up on my Nexus 10 too.
It screws up very, very fast when connected with USB debugging and I start to code OpenGL ES 2.0-based live wallpapers.
---------- Post added at 10:04 PM ---------- Previous post was at 09:58 PM ----------
espionage724 said:
So this fix requires Samsung to do it.
Almost hate to say it but I really don't see it being fixed anytime soon...
Click to expand...
Click to collapse
Not that bad. If it was HTC, we'd be screwed forever. With Samsung, we have a tiny (well, like, really tiny ) hope that something will be done in this regard.

I have been reading that Nexus owners may get 4.3 this month - anyone think the problem may be addressed?
In this thread http://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[476-500-false] - some dude from Google acknowledges that they know it's a problem - but he hasn't said anything in 6 months.
Really hope it is sorted out - I am keeping my fingers crossed.

bruce_aisher said:
I have been reading that Nexus owners may get 4.3 this month - anyone think the problem may be addressed?
In this thread http://productforums.google.com/forum/#!topic/mobile/VFYnt7uN9d0[476-500-false] - some dude from Google acknowledges that they know it's a problem - but he hasn't said anything in 6 months.
Really hope it is sorted out - I am keeping my fingers crossed.
Click to expand...
Click to collapse
As a comment above suggests, the bug has been assigned by Jean Baptiste-Queru little more than a week ago. We can only hope that it was fixed and merged into 4.3.

starkilling said:
As a comment above suggests, the bug has been assigned by Jean Baptiste-Queru little more than a week ago. We can only hope that it was fixed and merged into 4.3.
Click to expand...
Click to collapse
From what I read the developer of the surface finger driver already has an in-house fix and acknowledged that they reproduced the issue with the stock ROM. Those two comments give me hope.
Sorry but I do not have a link. I also have no idea why fixed drivers have not been released considering every ROM (stock and custom) must use the same proprietary drivers. It is likely that they require Google to distribute the fix.

I really hope to see this fixed soon, the random reboots really make the tablet unreliable. I can't do much serious work on the thing since every couple of hours or so the thing resets, losing all my work.

tbosje said:
I really hope to see this fixed soon, the random reboots really make the tablet unreliable. I can't do much serious work on the thing since every couple of hours or so the thing resets, losing all my work.
Click to expand...
Click to collapse
I use RasBeanjelly and I have not had a single random reboot. No reboots on mrRobinson's AOKP as well. You do have to reboot every couple of days, though. It really depends from ROM to ROM. Stock really rebooted on me like a motherf***er though.

I saw that one of the Google staff responded to the google product support thread the other day, a sign of progress?
starkilling said:
I use RasBeanjelly and I have not had a single random reboot. No reboots on mrRobinson's AOKP as well. You do have to reboot every couple of days, though. It really depends from ROM to ROM. Stock really rebooted on me like a motherf***er though.
Click to expand...
Click to collapse
I've spent so much time customising my apps and launcher, flashing my whole unit is such a hassle. Guess I might have to though :/

tbosje said:
I saw that one of the Google staff responded to the google product support thread the other day, a sign of progress?
I've spent so much time customising my apps and launcher, flashing my whole unit is such a hassle. Guess I might have to though :/
Click to expand...
Click to collapse
You can back them up, you know.

Posted by Matthew Fry on Google Product forums earlier today :good:
Ladies and gentlemen, I have the most amazing news. Pretty much the best news I can think of.
I have finally received word back from the Mali Developers. They revisited the issue and found that the fault was indeed in the Mali drivers.
"Following previous emails, the Nexus 10 issue that you have been mentioning has been fixed in the latest versions of the Mali driver."
It is, unfortunately, Google's responsibility to release this new driver version with the next Nexus 10 factory image. We can only hope that the fact that I/O has come and gone and the recent release of the Google Edition S4 and One on 4.2.2 does not mean that JB 4.3 or KLP are a long ways out.

chinmaysk said:
Posted by Matthew Fry on Google Product forums earlier today :good:
Ladies and gentlemen, I have the most amazing news. Pretty much the best news I can think of.
I have finally received word back from the Mali Developers. They revisited the issue and found that the fault was indeed in the Mali drivers.
"Following previous emails, the Nexus 10 issue that you have been mentioning has been fixed in the latest versions of the Mali driver."
It is, unfortunately, Google's responsibility to release this new driver version with the next Nexus 10 factory image. We can only hope that the fact that I/O has come and gone and the recent release of the Google Edition S4 and One on 4.2.2 does not mean that JB 4.3 or KLP are a long ways out.
Click to expand...
Click to collapse
Link, please? I can't find it.
Edit: found it, nvm. there were lots of pages

Can one of the mods please pin this thread in the forum? It seems like every week someone comes in and asks about this issue. Once a fix is released, this thread can be unpinned.

6 Month and Samsung and Google havent resolved that.....
Hope 4.3 comes out soon

kswiss86 said:
6 Month and Samsung and Google havent resolved that.....
Hope 4.3 comes out soon
Click to expand...
Click to collapse
Well, I hope the driver didn't come out from Mali too late to make the 4.3 release.

Funny thing is I even said to myself that I'll never buy anything from Samsung again, how wrong I was thinking the Nexus 10 would be different because it's from Google.

With 4.3 out next week (possibly) I do hope Google decide to put this emergency fix in. It really gets on my nerves that this tablet just randomly reboots because I know how much potential this tablet has and I feel this is holding it back.
Sent from my Nexus 10 using xda app-developers app

Same Source Code = Same ROM for YT3-850L/M??

http://support.lenovo.com/us/en/pro... and Software|Drivers and Software&beta=false
The above official Lenovo site lists only TWO (2) Source Code versions for THREE (3) devices: YT3-850L/M and the separate YT3-850F. This may explain why I've not located firmware specific to the YT3-850L. LOOKS as if the SAME ROM is used for the L AND M devices, suggesting there must be a hardware difference between the two. L is LTE DATA ONLY, whereas M is LTE DATA and PHONE. So I may have been on a wild goose chase. I'd hoped that M-firmware would turn my L-device into an M-device. Looks like maybe not. Other conclusions solicited if supported by evidence.
Thanks.
EDIT: I'm wondering if this should have been posted to a more general section. The small market share of Yoga Tablet users is not going to make this a hot thread. Anyway to get an administrator to move it? Thanks.

Galaxy View update to 6.0 or greater? Project XCloud purposes

Project XCloud is coming out soon and the Galaxy View tablets will be the perfect tablets to have portable xbox gaming on the go however the minimum requirements for Project XCloud is 6.0 (Marshmallow) or higher! The highest version the original Galaxy View has is 5.1 (Lollipop) now I'm aware their's custom roms for higher android versions but I don't want to strip the original software from Samsung in favor of other roms, is there anything we can do to have the software updated? Mine is the AT&T 64GB Black model that is LTE + Wifi.

Bump, I'm in the exact same boat

AOSP-ish?
What're you guys slow? Lmao! Sry jk! They've already released the Galaxy View 2. Being that the last official update for GV1 is what? 2016; I believe? I don't think there is anything we can do for an official update from Samsung. *shrug* MAYBE try e-signing some type of online petition? Maybe Fakebook? Twatter? (*sp-Squatter) Instascram?
I would also think that Samsung would have to be linked or tagged to make it count. I'm going to take a VERY ROUGH guesstimate on what would actually grab SS Dev's attention: ~10-25k people?
I was actually thinking of the possibility of doing a "just enough" mod of the View2 stock firmware to get it working, they have relatively the same physical attributes and when you .mk the Android Package if conf files are all in order it should work for the most part. Now I'm aware this is STILL not an "official" update/firmware but it's the closest you'll get without them damn lazy devs at SS signing the apks themselves. *shrug*
Feedback?

GhoztXero said:
What're you guys slow? Lmao! Sry jk! They've already released the Galaxy View 2. Being that the last official update for GV1 is what? 2016; I believe? I don't think there is anything we can do for an official update from Samsung. *shrug* MAYBE try e-signing some type of online petition? Maybe Fakebook? Twatter? (*sp-Squatter) Instascram?
I would also think that Samsung would have to be linked or tagged to make it count. I'm going to take a VERY ROUGH guesstimate on what would actually grab SS Dev's attention: ~10-25k people?
I was actually thinking of the possibility of doing a "just enough" mod of the View2 stock firmware to get it working, they have relatively the same physical attributes and when you .mk the Android Package if conf files are all in order it should work for the most part. Now I'm aware this is STILL not an "official" update/firmware but it's the closest you'll get without them damn lazy devs at SS signing the apks themselves. *shrug*
Feedback?
Click to expand...
Click to collapse
samsung is as worthless as their tvs! they update once maybe twice the software and then it is dead. because they are too busy trying to rip everyone off for the next $1000 phone or TV to care about keeping their stuff up to date. i have been sitting at 5.1 forever and the tablet lags so much now i have to disable 90% of the apps because they are memory hogs especially google apps. even updating the rom to 6.0 would make the tablet run smoother, but that will never happen.