yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 Themes and Apps] PulseDroid:
Hey guys found this on the market, might bee cool if you wanna get "Drunk"

(Child Friendly)

Description:

-Choose height of beer

-Can use battery percentage

-Beer uses "Ace"lorometer

Screenshots

Market link
[Galaxy Ace S5830 Themes and Apps] Pepper95:
Lol you're only 12 xD
[Galaxy Ace S5830 Themes and Apps] PulseDroid:
Yeah I wanted to test it :p
[Galaxy Ace S5830 Themes and Apps] PanzerKnackers:
Thanks was sent! This is great..

Sent From Jamban.. When I was Modol..
[Fascinate Q&A, Help & Troubleshooting] SantiMun:
I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.

Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit

After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).

Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.

Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?

At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).

Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).

At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.

I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
[Fascinate Q&A, Help & Troubleshooting] lordnikko:
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
[Fascinate Q&A, Help & Troubleshooting] SantiMun:
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.

He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.

But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
[Fascinate Q&A, Help & Troubleshooting] MultipleMonomials:
Check kernel settings. Sleep Of Death, maybe?
[Galaxy S III General (US Carriers)] bigant262:
http://rootzwiki.com/news/_/article...-jelly-bean-source-is-now-being-released-r955
[Galaxy S III General (US Carriers)] corythug:
http://www.androidpolice.com/2012/07/09/android-4-1-jelly-bean-released-to-aosp-right-now/

Damn it you beat me to the punch lol
[Galaxy S III General (US Carriers)] Serious_Beans:
CM10 soon!!!!!!
[Galaxy S III General (US Carriers)] MMontanez347:
hopefully we get CM9 support first :(
[Galaxy S III General (US Carriers)] freexx89:
lets see how fast we see something for s3 ;)
[Galaxy S III General (US Carriers)] Serious_Beans:
Why would they make CM9 for this phone when JB source is released? Lol that makes absolutely no sense.
[Galaxy S III General (US Carriers)] Restola:
I believe it was said that jb code is very similar to ics. Cm9 is very close for us. A stable cm9 to cm10 would probably be faster than cm10 built from scratch. Just a guess though, I'm not a dev.

Sent from my GS3
[Galaxy S III General (US Carriers)] Serious_Beans:
Nah I mean working off of CM9 would make sense if they could just merge the changes but I doubt it would officially be released just for them to release CM10 after that.
[Galaxy S III General (US Carriers)] razorseal:
I really hope we get CM7 before that :(

/sarcasm

really? why would you want the outdated one?
[Galaxy S III General (US Carriers)] jarnow94:
The CM team is merging the update as we speak. I think we will probably just get CM10 and not CM9 first (could be wrong though)
[Galaxy S III General (US Carriers)] yokken:
We will get CM10 before CM9. All development on CM9 is being ceased after version 1.0.0. Just be patient, the source was uploaded something like 2 or 3 hours ago.
[Galaxy S III General (US Carriers)] razorseal:
I think we will have something by next week
[Galaxy S III General (US Carriers)] jsmcmahon89:
I think we'll have something by tomorrow morning.. ;-)

Joking aside, this is cool to see.
[Galaxy S III General (US Carriers)] Master Ramy:
Joke? don't underestimate the developers on THIS phone, of all phones :)) I'm gonna definatelly keep an eye on these forums. if nothing else i expect someone starting a WIP thread, an AOSP built rom, most likely not fully functional ofcourse, but compiled enough to boot up, just to give us a taste while development begins in earnest :)

This is just what was needed to jump-start development for the SIII :)
[Galaxy S III General (US Carriers)] OneNutShort:
I'm curious, with Verizon's S3 flashing abilities currently being limited to roms stripped of kernels, how will this affect a jellybean rom? Is the ics kernel the same as the jb kernel?
[Galaxy S III General (US Carriers)] mt3g:
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
[Galaxy S III General (US Carriers)] bigant262:
Reason people are saying that we could see CM10 soon is because the CM team think the code should be able to merge right into what they have with CM9, and not break that many things. With CM7 to CM9, they had to basically do everything from the ground up again because ICS was such a huge update over GB. Now JB isn't that big of an upgrade over ICS, in a way it is, but in a way it isn't. Sorry if that sounds confusing.
[Galaxy S III General (US Carriers)] mt3g:
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
[Galaxy S III General (US Carriers)] Master Ramy:
I am no dev, but heres how i understand it works;

we start with an announcement of an OS, this is done generally at Google I/O or a Nexus Event, in this case was Google I/O.

On the announcement day, devs receive the SDK; Software Development Kit.

This is released to allow the devs to begin making apps that match and run on the new OS. However, aspiring rom devs then begin to build a rom off the released SDK, generally called an sdk port.

These tend to be made simply to give us an idea of how the system would work and function, and generally might boot up and have a couple working things, but major things tend not to function because the SDK is not made for that.

Then comes the Source code, this is the real deal, it is full code of the system, code that can then be compiled to produce a fully working system, or nearly fully working. Only thing that remains missing is proprietary drivers and such, these tend to be the things specific to each phone, files that would make particular chips work, particular functions, the specific phone kernel, etc. but once you have the source code, you're over 80% done as far as having the resources needed to develop a full rom. at this stage, some devs can produce a fully working, stellar rom, but it will take quite a bit more work than devs who choose to wait for the final stage

Then comes the OTA. this is where all the device-specific stuff comes to the devices, and devs have the absolute and complete freedom to produce a fully working, better than stock, experience. This is where roms flood the dev forums.

So as far as not having AOSP yet, and now this is our chance at AOSP? No, thats not why we dont have AOSP. we dont have it cause no one built it yet; the Touchwiz UX is sooo integrated in the system that untangling and taking it all out is a long and drawn out process, and theyd need to deconstruct what we currently have, take out elements of touchwiz until its all clean, all the while making sure it doesnt break anything else.

but getting the jellybean source code propels devs because now this is a new OS, a new AOSP with its own new interesting properties. and because Jelly bean is a small update compared to ICS, now that we have source code, many of the device specific stuff wont be broken by implementing jellybean code into it, therefore building a Jellybean rom is a faster path to AOSP than untangling the current ICS for Galaxy S III

Does that make sense?

AOSP in this case is talking about the actual Android Open Source Project. so it is a bunch of code. so why are we excited? we've had ICS AOSP code for nearly a year now, what we dont have is AOSP roms. building an ICS AOSP rom is much harder than building a JB Rom, and we currently have icecream sandwich on the SIII even if its touchwized, and undoing touchwiz is quite a bit of work. but Jellybean...Oh Jellybean, now we got the source, we will start getting that baby soon and it'll boost dev on these devices. make sense?
[Galaxy S III General (US Carriers)] bigant262:
Not sure if you were trying to come off rude or not, but people are excited because its the newest update, duh. Reason being we don't have 4.0 AOSP is because the phone hasn't been out that long for the US carriers.
[Galaxy S III General (US Carriers)] jarnow94:
I'm not sure it has as much to do with Touchwiz as it does with our hardware, since the international version has had AOSP for a while now.

Congrats on having the longest post I think I've ever seen lol
[Galaxy S III General (US Carriers)] mt3g:
New most of that but clears alot of the stuff I had questions on as well. Very good response and thanks. My thoughts are now that source is released we will probably see an attempt and more strive to get us CM10 on our phones, maybe they were just holding off since they knew 4.1 source was close. Mainly they need radio interface layers and such and a compatible kernel for 4.0 AOSP, wasn't that/is the standing issue at hand?
[Galaxy S III General (US Carriers)] Lieu10ant:
who wants to verify how accurate this is?
[Galaxy S III General (US Carriers)] mt3g:
No not trying to come off as rude, might have done that cause text is so monotone though lol, just trying to get a further understanding. I know it'll cone very soon cause we have great devs on this phone the sprint cm team has been doing great work and we also have Whirehawkx and the great romanbb also. Just trying to get a further grasp on the matter is all, wiki explains it all but does it in a so "blah blah blah blah" kind of way...
[Galaxy S III General (US Carriers)] bigant262:
Kind of figured that. lol. Depending on if the code doesn't break many things, I'd say we might see CM nightlies in about a month, month and a half.
[Galaxy S III General (US Carriers)] mt3g:
Ya it might take some time... we have smart guys working on this phone though I'm sure an abundance of roms will be coming our way though. This will be the most popular device I've owned since the G1 haha!
[Galaxy S III General (US Carriers)] bigant262:
I hope so. I remember the good ole G1 days! So many roms to choose from.
[Galaxy S III General (US Carriers)] Master Ramy:
Well, touchwiz is a part of the slowdown, as far as hardware, the only things really different would be radio and processor...idk...im not quite sure on that point, u may very well be dead on, but i do know that undoing touchwiz is a long and crazy process as of right now, particularly cause of its DEEP integration this time around.

Haha thats the longest post you've seen? sorry, hope it made sense tho :)

Please do, i think its accurate but id love someone else to confirm that :)

the other thing with CM is that they are very thorough and its a huge project, so expect Jellybean roms before CM nightlies start appearing for our device :) either way im excited for whatever comes next :)
[Galaxy S III General (US Carriers)] jarnow94:
From what I've heard CM9 was almost ready for us, so since Jellybean changes are being merged (and it's not a total revamp) we should have CM10 relatively soon, I think.
[Galaxy S III General (US Carriers)] capcanuck:
I read that roman and 1 other team kang devalready have AOKP booting, although nothing on it works yet, it's one hell of a start.

We all need to be patient, and not get disgruntled. I watched the t989 forums turn to bitter crap in a matter of months over nearly nothing. This device is amazing, I haven't ran a TW based rom in a looooong time, and I'm running one now and having a blast. Let's be satisfied and positively/patiently look forward to the goodness to come...

Woot Woot!
[Galaxy S III General (US Carriers)] mt3g:
Agreed, I've been waiting to jump on this phone first for color, then to make sure it was going to be backed by devs I had trust in, now its back to waiting on white one to show up in a Walmart near me.
[Galaxy S III General (US Carriers)] yokken:
I'm chillin on TW with the awesome ICS theme. Luckily I don't hate it so I'm fine until they release it... but it doesn't mean don't want it really bad...
[Galaxy S III General (US Carriers)] EndlessDissent:
I don't think I'm qualified to "verify" it, but most of it sounds accurate to me. Up until the OTA part, anyway. The OTA in our phone's case isn't nearly as helpful for AOSP ROMs as it would be for a Nexus device. The only benefits for us with an OTA is that we would get binary files for the proprietary drivers. And the actual OTA ROM doesn't matter; it's all about the kernel source code. It could mean the difference between mostly-working hardware and fully-working hardware, but it isn't really necessary for getting an AOSP ROM to work. Take the OG Evo for example. There was no OTA released with ICS, but we had great ICS ports. Was it fully-working? No, the FFC doesn't work, and neither does Wimax, and the camcorder is kind of buggy but works. EVERYTHING ELSE works fine. Would an OTA help? Sure, as long as it came with kernel source. An OTA with no source code is as helpful as a car without the key to start it. Unless the dev is good at "hotwiring" drivers, an OEM OTA means nothing in AOSP-land.

So, yeah, he was accurate (within the confines of my knowledge) except that the OTA part should specify the kernel source since a TW ROM doesn't matter in the AOSP process.
[Galaxy S III General (US Carriers)] MacTheRipperr:
please correct me if I'm wrong. But the reason it's using so long is because they can just rip tw off. But we would lose all the functionality of all the things we bought the phone for. They want to remove tw while maintaining all the features that make this phone as amazing as it is. This unraveling is the biggest hurdle we have to overcome.
[Galaxy S III General (US Carriers)] razorseal:
There is going to be a TW free AOSP soon. There won't be any of the things that's integrated into it, like battery saver, motion sensing features, the quick access lock menu etc etc.

you're going to lose all this. but that's what you are getting. a pure android experience.

so you're gonna have to decide if you want a TW to stick around in your phone, or a AOSP. perhaps in the future, there will be devs who combine the best features as has been done before.
[Galaxy S III General (US Carriers)] mt3g:
If you mean smart stay and gesture control, and such then I'm okay with it bring gone, I'd like the camera to stay and that's about it. Not much for gimmicks. I want the phone for the phone and its capabilities with CM behind it, well AOKP lol.
[Galaxy S III General (US Carriers)] Nelsocracy:
Here's a great talk some of the cyanogenmod team did at Google io explaining what makes the project so difficult:

http://androidandme.com/2012/07/new...discuss-the-cyanogenmod-project-at-google-io/

As I understand it they aren't "stripping out" touchwiz but rather building straight from the aosp code but adding in all the necessary code for it to function on our hardware, which as he says in the video is extremely difficult due to lots of the hardware specific code being closed source.

He did also say that once one chipset gets cyanogenmod, other phones with that chipset usually get it soon after. I see the s4 one x now has an unofficial alpha build of cm9 so hopefully that'll help our s3s a bit.
[Galaxy S III General (US Carriers)] yokken:
This is from the i9300 CM9 alpha thread.
[Galaxy S III General (US Carriers)] glensta:
You?

Sent from my Obsession
[Galaxy S III General (US Carriers)] razorseal:
exactly. it's built from the ground up, and kernel/drivers is the biggest hurdle. that's why you see ports that don't have certain things like the radio, wifi, camera etc.

imagine installing windows on a computer without the drivers for certain things. it'll work, but you're gonna be missing necessary hardware to make it a good experience

yep. that's it. the camera has no TW stuff integrated afaik, but you will most likely not see it. we will end up getting (from CM10 that is) the aosp camera. most rom cookers will probably put the camera back in, or the htc one x camera (or whatever else)

camera is all software. if pulled from say one x, there would be no limitation to use it in ours. perhaps that one is tuned to work with the sensor/camera combination though, and ours is tuned to ours. i'm not sure on specifics.
[Galaxy S III General (US Carriers)] jerrygooch:
Well not sure how I'm going to cope with not flashing daily but I'm going to try and stay stock till we see an aosp jellybean rom. Wish me luck! :D
[Galaxy S III General (US Carriers)] zsdersw:
One thing I've noticed about the AOSP roms and CM9 for my Galaxy Note (that I traded for a GS3) is that BT in my car connects and plays/controls audio but it does not display the song info on the navigation screen. TouchWiz-based roms do. Given how much I drive I really like and want to keep that feature.

I wonder if it's also true for the GS3 and any AOSP roms and CM9 we get.
[HTC Inspire 4G] didozer:
I have a belt clip for my old inspire that just sitting here if anyone wants is. Its the PT brand from best buy. Fits lots of different hard cases. If anyone wants it you can have it just cover shipping. PM me.
[Android Software/Hacking General [Developers Only]] pwit:
i rooted and install official samsung updates

Now still bootloop to cwm .help me pls
[Android Software/Hacking General [Developers Only]] tokidoki11:
have you solved it?

if no

flash your stock ROM via odin as PDA
[HTC Sensation] Taker18:
Hey Guys, looks like the JellyBean Source is out.

[New Link]

https://android.googlesource.com/platform/manifest/+/android-4.1.1_r1
[HTC Sensation] InfinityFTW:
So...it begins....
[HTC Sensation] M3nti0n:
Actually, there has been a naming problem.

insteed of android-4.1.1_r1 it is: jb-release
[HTC Sensation] kojot1234:
Lovely! :) Thanks for the tip. Another long night ahead.
[HTC Sensation] teddyforms:
Cant' wait to start seeing JB ROMS popping up! :D

Also, what does this mean for Sense? Must we wait for an official Sense JB ROM to surface?
[HTC Sensation] James1o1o:
Wouldn't we need to wait for HTC for that? I can imagine us porting Sense 4.0 to other devices, but to port Sense across to a different Android version?
[HTC Sensation] futty:
this is cool but damn i just got ics from tmobile not 2 long ago.
[HTC Sensation] Taker18:
Hopr our great devs will bake us a awesome JellyBean ;)
[HTC Sensation] blackwing182:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

branch is jb-dev.
[HTC Sensation] DylanTheVillian:
I look forward to your work :)

Thanks!
[HTC Sensation] DragunKorr:
error: revision android-4.1_r1 in manifests not found

rms@rms-RV410-RV510-S3510-E3510:~/android/system$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1_r1

error: revision android-4.1_r1 in manifests not found

rms@rms-RV410-RV510-S3510-E3510:~/android/system$

help please thanks

---------- Post added at 03:58 AM ---------- Previous post was at 03:48 AM ----------

need default manifest or local please nton=get repo goin thanks guys waiting patiently!!!

o cm repo ?

should i splice into cm repo?

:confused:
[HTC Sensation] blackwing182:
https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

Febcyv is planing something i think, he opened a new git folder
[HTC Sensation] Maikeu Locatelli:
is android-4.1.1_r1 not android-4.1_r1
[HTC Sensation] DragunKorr:
nice we need full repo then massive things will happen for all:good:

---------- Post added at 04:24 AM ---------- Previous post was at 04:15 AM ----------

repo goin good work bro thaqnks
[HTC Sensation] blackwing182:
yes wee need it lol :) i hope that this new OS doesent be a pain in the ass to merge
[HTC Sensation] DragunKorr:
this will be seroius team work effort whick device tree are you workin for balck if i may ask?

---------- Post added at 04:54 AM ---------- Previous post was at 04:35 AM ----------

proper sync command

---------- Post added at 05:01 AM ---------- Previous post was at 04:54 AM ----------

gonna take htc device work tree i feel to build proper i feel

:laugh:

repo still goin strong so far

---------- Post added at 05:38 AM ---------- Previous post was at 05:01 AM ----------

work tree syning

---------- Post added at 05:49 AM ---------- Previous post was at 05:38 AM ----------

got full repo

Fetching projects: 100% (294/294), done.

Checking out files: 100% (14194/14194), done. files: 18% (2563/14194)

Checking out files: 100% (4587/4587), done.ut files: 9% (448/4587)

Checking out files: 100% (229/229), done.g out files: 37% (87/229)

Checking out files: 100% (6222/6222), done.out files: 6% (398/6222)

Checking out files: 100% (765/765), done.g out files: 0% (2/765)

Checking out files: 100% (8843/8843), done. out files: 26% (2370/8843)

Checking out files: 100% (1654/1654), done. out files: 31% (522/1654)

Checking out files: 100% (24601/24601), done.

Checking out files: 100% (17893/17893), done.ut files: 0% (87/17893)

Checking out files: 100% (4261/4261), done. out files: 38% (1648/4261)

Checking out files: 100% (210/210), done.ng out files: 2% (6/210)

Checking out files: 100% (974/974), done.ng out files: 34% (339/974)

Checking out files: 100% (667/667), done.ng out files: 14% (98/667)

Checking out files: 100% (431/431), done.ng out files: 15% (65/431)

Checking out files: 100% (370/370), done.ng out files: 49% (184/370)

Checking out files: 100% (433/433), done.ng out files: 15% (68/433)

Checking out files: 100% (2407/2407), done.

Checking out files: 100% (2489/2489), done.

Checking out files: 100% (2412/2412), done. out files: 4% (105/2412)

Checking out files: 100% (974/974), done.

Checking out files: 100% (26958/26958), done.ut files: 24% (6671/26958)

Checking out files: 100% (81/81), done.

Checking out files: 100% (4344/4344), done. out files: 0% (42/4344)

Syncing work tree: 100% (294/294), done.

now what peeps?
[HTC Sensation] blackwing182:
let me know so i can help you fixing things :-)
[HTC Sensation] DragunKorr:
shootin for pyramid device treee
[HTC Sensation] DragunKorr:
thanks black