yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] aaronmy:
yea it looks great, but crazy not even a quad core cpu could handle that game perfectly, maybe the Tegra 3 could though
[Android Apps and Games] john9:
Looks great!Thanks for your contribution .
[Android Apps and Games] Mr.Mefisto:
Nice Video! Thanks!
[Android Apps and Games] voodoochild2008:
On the sgs3 it seems to have issues...well for me.

First it said not enough room (4gig left) so I made more room and seemed to be downloading fine but at 98% it says error code 91?

Anyone had this?

cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] j5boot:
Hello

Yesterday I flash my phone with CM7 and battery drain quickly. The batery only works 15 hours when the Stock ROM is about 36 hours.

The question is what is the best ROM for long battery life.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DreamerTKM:
BroodRom Business Edition :confused: NitroX :confused: ShadowRom :confused:

i feel quite ok with these...
[Galaxy S I9000 Q&A, Help & Troubleshooting] tchindalia:
Hey

If u want a long batter life and dont really care about the firmware then flash 2.1 update 1 (Eclair)...has a really long battery life...

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] Arthur Hucksake:
Hi folks,

Does anyone know the email address or contact page to get some help from Google?

I want to see if I can exchange my Nexus 7 for the loose screen fault.

Don't fancy waiting on the phone for over an hour in queue again.

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] gbroon:
In the nexus order in google wallet there should be a contact link.

Sent from my Transformer while the N7 is lost in the Play Store Black Hole.

16gb N7 UK ordered 3rd July.
[Samsung Galaxy Nexus] SC54:
I have searched all over the internet looking to find a solution to my problem. My Samsung Galaxy Nexus I just purchased off kijiji (craigslist) was unlocked so I could use my Bell sim card with it, it was not completely wiped. Everything works except during calls I cannot hear anything on the front speaker, the speakerphone and headphone jack both work fine, but without resorting to those methods I cannot hear anything during a call. Most people I have read either return their device or reflash/reroot, I can't return this so I'm hoping to restore this phone to a more default state, hopefully resolving my issue.

I am hoping that I can follow this thread to get my phone back to stock, or the Super Users Guide. But before I do this I wanted to know, can I use either of these guides on my phone knowing it is already unlocked? Will they work the same, or will it brick my phone?

Also, will my phone remain unlocked so that I can use my Bell sim card in it? It does not seem to be branded. If it does not is it simple to unlock again so I can use my sim card?

I have the following specs:

Baseband version: I9250UGKL1

Kernel Version: 3.0.1-ga052f63 android-build@apa28 #1

Build Number: ITL41F.I9250UGKL1

Thank you in advance, if anyone could even just say yes or no, or possibly point me in the right direction it would be much appreciated.

-SC54
[Samsung Galaxy Nexus] Gnomely:
From my past research it sounds like the same problem I have which is the faulty headphone jack hardware. Apparently, it's a problem that has plagued Samsung on multiple devices; however, I had never heard of it until my phone stopped playing any sound from the handset.

The headphone jack is busted, for the most part, so it ALWAYS thinks the headphones are plugged in to the jack, so it turns off the handset and the mic. Only way I've been able to use mine is using a Widget called "Toggle Headset 2" which forces the phone to use the handset. This has been the only "solution" to fixing this that I have ever found that actually did something.

Hope this helps.
[Samsung Galaxy Nexus] brettofamerica:
First and foremost, try what Gnomely suggested since that is going to be the easiest fix. If that doesn't work then I would suggest using the Galaxy Nexus ToolKit since it has almost everything you'll ever need for this phone including getting your phone back to stock! As for your phone, your phone is unlocked meaning that it can be used on any GSM carrier and will always stay that way unless you physically take the phone apart and replace the hardware :p
[Samsung Galaxy Nexus] tihsad:
ITS NOT THE SW!! when i bought my first GNEX LTE verizon in december when it first came out, i had the same problem. i sent it to samsung USA and they fixed it and sent it back to me. and then next day it broke again and i call them right away and they fixed some part again and samething happened. after one day it stopped working and i got pissed off and call samsung and told them its a lemon and told them to give me a new device instead trying to fix the problem. and i hadto talk to a supervisor to get me a brand new device.
[Samsung Galaxy Nexus] sitaramp:
Rule out all software issues. If it is hardware issue check with Samsung if they would service it for you.

If you are comfortable with opening the phone see this thread. Search for YouTube videos to get the idea.

http://xdaforums.com/showthread.php?p=29327946
[Galaxy S I9000 Q&A, Help & Troubleshooting] Alexo1337:
Hello guys,

the screen from my galaxy s i9000 is broken.

I think the phone is still working because i can hear the boot sound etc..

I need the data from my phone but cant turn on the usb mode without seeing something on the screen.

When i plug it into my pc the usb sound plays but the mass storage wont show up because i cant turn on usb mode...

Im on custom firmware with CWM..

Any ideas how to get my data without replacing the screen??

thanks in advance
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kurre:
Boot to CWM, plugin USB cable, fire up ADB, use it to pull your files from the phone.

Sorry, I don't have now time to explain it thoroughly, but you should be able to find some ADB tutorials from this forum.
[Galaxy S I9000 Q&A, Help & Troubleshooting] erpurohit:
Which rom you were using?

If using any custom rom then read how to use adb and you may pull the data using it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kurre:
Is it echoing in here ? :p just kidding..simultaneous posting about same matter ;)

Well, he said that he has custom firmware & CWM, so it shouldn't be a problem...I hope :rolleyes:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Alexo1337:
Thanks guys!

I´ll give it a try tonight..
[Nexus 7 Android Development] cwc3:
More the merrier. :good:
[Nexus 7 Android Development] Indirect:
Ewww, a sparksco has appeared. :P Just kidding bud, if you need any testing on the kernel I know you'll build let me know. Looks like a decent thing you have going here but unfortunately, I don't feel like flashing a new rom. :P
[Nexus 7 Android Development] sparksco:
I should have the boot animation fixed in the next build, then I can test more on the kernel..
[Nexus 7 Android Development] Shano56:
Let us know when boot animation is working... boot animation is 75% of the reason to install CM :D
[Nexus 7 Android Development] sparksco:
Don't worry I'll get it fixed, working on a build now. I'm sure every developer has their own ways of building so stability between different unofficial builds will still vary.
[Nexus 7 Android Development] Shano56:
Hey man its no worries, appreciate what you're doing
[Nexus 7 Android Development] Brigaid:
Pretty excited about this. One question though, why the lock screen camera launcher? Is it just an AOSP thing that is disabled in the stock N7 rom?

Sent from my SGH-I777
[Nexus 7 Android Development] thracemerin:
The AOSP default lock screen has the camera shortcut on it, so it would require removing it from the frameworks package most likely, CM generally comes with the ability to change the shortcuts, so once that gets merged up to JB it wont matter that it doesn't work cuz you'll be able to change it.
[Nexus 7 Android Development] sparksco:
Yeah I'm sure it's a setting somewhere that hides it from the launcher. It might be a setting in the camera app itself not to show much like many other system apps. I haven't really looked into it much but I'll look around some. I tried the nexus 7 launcher from the market and it just force closes, so that's not a option either.
[Nexus 7 Android Development] mgori:
Great work Sparksco. Just one question for you, does CM10 use the TabletUI or HybridUI? :D
[Nexus 7 Android Development] armyboy11b:
You can change the DPI with a app if this don't have it
[Nexus 7 Android Development] neilrl79:
Yes but tablet ui without changing dpi is the goal that I think most people want.
[Nexus 7 Android Development] th0r615:
I don't.
[Nexus 7 Android Development] sparksco:
Well you can't make everyone happy. I'm sure if it was that easy to implement it would have been done already. And there has to be a option, not force people into a tablet ui.
[Nexus 7 Android Development] dadoc04:
man this rom is awesome.... thx a ton
[Nexus 7 Android Development] sparksco:
The current landscape launcher patch I have applied may not become official in cm. If it doesn't I'll most likely keep it as a option if you all request it to stay the way it is.
[Nexus 7 Android Development] ptesmoke:
hey sparks, thanks for all your work :)

is there any way to calibrate the orientation sensor?? seems like i have to have my tab un-normally vertical for it to sense a rotation. i messed around with the sensor setting in a few games and apps, which works, but only in the game/app, not the system.

is there a hidden menu somewhere?

thanks x1000 for creating these awesome "nightlies" :)
[Nexus 7 Android Development] smirkis:
on the kindle fire, they have a toggle for tabletUI or JBhybridUI. jus saying, if u want to add the "option". I prefer the new JBhybrid UI
[Nexus 7 Android Development] NetSoerfer:
I have been getting boot loops as well the first time I installed this ROM. I then went to the official CMX nightlies and had the same problem.

Turns out the ADB driver installed by the Nexus 7 Toolkit were the cause. I installed the alternative drivers with PdaNet and the problem disappeared.
[Nexus 7 Android Development] sparksco:
hmm, that would make sense because I never used a Toolkit. I've been using the PdaNet drivers from day one.
[Nexus 7 Android Development] arian009:
Anyone else gets under clocked after they put the tablet into sleep? Mine goes back to stock 1300mhz after i put my tablet into sleep. I've also tried various O/C Applications.
[Nexus 7 Android Development] sparksco:
Hmm your right, thanks for pointing that out I'll have to look into what is causing that.

Edit: Think I know what's causing it, this:

https://github.com/pbeeler/Kernel-Grouper/commit/da43b602bf703ba74da7a00069490e054b6c6b70

I'll revert that commit in the next build and it should fix it.
[Nexus 7 Android Development] sparksco:
Ok so the overclocking issue was not kernel related. The issue is on the rom side of things. Faux123 has a fix for it that I'll be incorporating into the roms, so credit for that goes to him for fixing it.

https://github.com/faux123/android_...mmit/734843b8f73262d0196ced4974bd1bb066634e39

https://github.com/faux123/android_...mmit/c875ba8a02dfceaf731088758df9a70335aa22ff
[Nexus 7 Android Development] sparksco:
Make sure your not using any incorrect windows drivers from any toolkits and having your Nexus plugged into USB. This will cause just about any rom not to boot including official cm10 nightlies...

I do the same thing install with CWM after downloading with goo manager. Please read the OP as far as flashing and installing these ROMS.
[Nexus 7 Android Development] B-Mod:
I download from Goo, but install with CWM. How do I check the drivers? I used Wugfresh's tool. I have three nexus 7's in the family, used the same tool on all, but mine is the only one that boot loops, but my wife's and daughter's 7's are on older builds of your rom. I got boot loops one day this week. Went to wake up the nexus, and nothing, had to hold the power button for a long time, then got stuck in a boot loop with the cm10 logo, held the power button, turned off, then restarted again, and it booted right up. I am not complaining , so don't take it as such, I will just keep trying to work thru it. Thanks........Brian
[Nexus 7 Android Development] sorcio46:
Thanks to all DEVs for your work

This is my Video Overview of this ROM

[YOUTUBE]W-nczFG9Ptw[/YOUTUBE]

Fell free to use it for your purposes.
[Nexus 7 Android Development] sparksco:
That's a cool video but I don't think it's of this ROM. The video doesn't show the key features of this ROM like the kernel features or the TabletUI hacks. To me the video looks like stock cm nightlies?
[Nexus 7 Android Development] sorcio46:
Posted to the wrong thread sorry ^^
[Nexus 7 Android Development] sparksco:
Just a quick update I under-volted the kernel more because my battery temps were getting to high. If anyone could test the latest builds and report back that would be great.
[Nexus 7 Android Development] sparksco:
Interesting, not sure what's causing that, if it's a device thing or what. As I stated in a previous post I use to get random bootloops on the very first nightlies (think that was like a month or two ago), but have not had any n a long time now on the newer builds. Hope all is well.
[Nexus 7 Android Development] sparksco:
Oh alright... I thought the TITLE and OP were pretty obvious but apparently not :screwy:

I would not object if you did a review of THIS ROM :p
[Nexus 7 Android Development] Mesograt:
I know some other people got the same problem, but I'm stuck on a bootloop with this rom. I can't access recovery at all, and while I did manage to get into the bootloader, it froze completely and wouldn't work. The toolkit isn't working either. Are there any other solutions?
[Nexus 7 Android Development] YoungCorruptionV2.0:
Well to access recovery from a bootloop you need to plug your n7 to your computer. What recovery are you using? With cwm I never had this problem
[Nexus 7 Android Development] sparksco:
I think I should just put this out there for the people having bootloops. This is my last warning about the bootloops. Other people are having the same issue if you just SEARCH a little.

http://xdaforums.com/showthread.php?t=1797040

It doesn't matter what ROM your on just because you happened to be on this ROM when something went wrong.

On another note uploading a release candidate right now :)
[Nexus 7 Android Development] B-Mod:
That link doesn't help much, if at all, cause as you know, we don't flash gapps on this ROM. I have not used my 7 much, but I have had no issues lately.
[Nexus 7 Android Development] sparksco:
I never said it would provide you with a solution. The point being is lots of people are having the exact same problem, but on these roms? No, completely different roms. Not flashing gapps? You must be on a really old version, you don't check the OP much?
[Nexus 7 Android Development] sparksco:
Disregard this post.
[Nexus 7 Android Development] RoyalWitCheese:
I'm afraid to say that this CM-RC1 version is bootlooping on me too. (Google Screen, not CM screen) can only boot into Fastboot mode after looping

First time - Dirty Upgrade - wiping only Dalvik and Cache = looped

Fastboot flashed Stock

installed EOS (to check tablet was ok) = Ran perfect

Second time - Factory reset/dalvik/cache - Flash Rom - Wipe all - Flash newest Gapps = Same bootloop as first time

went to recovery through fastboot, Dirty upgraded to EOS - works.
[Nexus 7 Android Development] roadhead:
Same for me as well.
[Nexus 7 Android Development] sparksco:
New nightly is out give that a shot...

Also updated the gapps so make sure you download and flash the newer version gapps.

And while I'm here for those of you that follow my Google plus post you probably have noticed I've been developing a new app called Wallpaperz. It is now included in these ROMs. Original thread is here:

http://android-den.com/index.php?topic=1415.0
[Nexus 7 Android Development] sparksco:
I'm pretty sure in the OP it says to not dirty flash when coming from other ROMs. Did you even read it?
[Nexus 7 Android Development] sparksco:
I'll just leave this here... I would have posted a screenshot of RC1 that supposedly "bootloops" but im already on the latest build...

For ROMs that bootloop how am I able to post screenshots of the ROMs?
[Nexus 7 Android Development] armyboy11b:
I did a clean install as usual ...ROM works great...as usual lol thanks man!!
[Nexus 7 Android Development] brooksyx:
Hmm will have to give this a try over the official cm10 nightlys.
[Nexus 7 Android Development] sparksco:
Just added a new mod to the roms to resize the height of the navigation buttons, check OP for more information. Also some new kernel improvements.
[Nexus 7 Android Development] sparksco:
LINARO

Added Linaro toolchain 4.7.2 to the source. ROMs and Kernels are all now built with it, that is all...
[Nexus 7 Android Development] B-Mod:
Sparksco, the rom DOES NOT bootloop all the time, just some times. I also am finding on this rom that I have trouble waking the tablet with the power button. If I go back to one of your first builds I have, everything is fine. No one is calling you a liar, but you sure are trying to call the people with problems one. These android devices have their quirks, it seems not all devices act the same......
[Nexus 7 Android Development] sparksco:
I'm not calling anyone a liar. I did have the wake issue for awhile but that bug doesn't seem to be present in the latest builds, that's why I never added it to the "known issues" on the OP. I also haven't had the issue of the ROM not booting on reboots in a long time. I stated that in a previous post if you read back some.... Maybe you just need to do a full wipe coming from the older versions and flash the newer gapps but idk.

Edit: Also noticed you like to come on the thread and report bugs as soon as I post updates with new ROM features. Just seems a little odd. The older ROMs have a lot more bugs and do not include all the latest features.
[Nexus 7 Android Development] B-Mod:
I only post after you post, because that is when you keep telling people there is no way this rom can bootloop, lol. I am not trying to put down you or your work, I and others on here are just stating what our we are experiencing. I will try your latest build out, see if the wake issue is gone for me. Keep up the good work, just try not to discredit others with problems.
[Nexus 7 Android Development] sparksco:
Just a few suggestions for everyone.

1) Clean your cache every once in awhile, I use cache clearer NG from the market and it works great!

2) If you don't have any issues with one ROM but in a updated version have a bug/issue, try a clean wipe and install of ROM and gapps.

3) Install gapps with every update that you flash ( as stated in the first post ). Don't rely on cm's gapps backup tool. I noticed it's buggy and does not work properly with restoring all of the files that are included in the gapps packages.

4) Try different gapps, if you find some that work better than the ones I have in the first post report your findings here on this thread.

5) Having issues after rooting your device such as Various ROMs not booting or waking issues restore factory images ( including recovery ) and root again. This fixed a lot of the issues I was previously having before ( about a month or two ago when I had booting issues )

6) Don't use rootkits, your more than likely to run into issues later on.

7) If your having a issue/bug that is not listed on the first post under "known issues" it's because not enough people are having the same issue as others. There seems to be a VERY SMALL percentage of people having certain issues, that is not worthy of considering to be a known issue. Most likely it is your device having a rogue app or some type of other strange issue, perhaps even the type of recovery you are using. CyanogenMod ROMs do not like to be flashed in TWRP recovery I.m.o., which is why I promote CMW recovery when flashing these ROMs.

8) If you or anyone else you know wants to contribute to these ROMs or this project contact me via pm or make forks of my repos on github.com. The link is in the first post. After making forks of my repos send your pull request for me to review. If you would like to send pull request to a repo that is not on my github you need to submit it to CyanogenMod gerrit code review. 90%+ of the source code is from Google, 5%+ is from CyanogenMod and the rest is from other people and myself. You can build the full source as well exactly as I do using my android manifest on github.
[Nexus 7 Android Development] sparksco:
10/06

New version is out, check my github for changes. New power hal fix should fix all booting previous booting issues even though I never had them personally.
[Nexus 7 Android Development] 57op:
Is aokp_grouper-jb-1349548107-1006.zip latest zip name?

Does your rom include "expanded desktop" (like in paranoidandroid) feature in powermenu?
[Nexus 7 Android Development] sparksco:
Did you follow the link on the first post? Is this a paranoidandroid rom?
[Nexus 7 Android Development] 57op:
I may have followed the wrong link.

However, i didn't say this rom is a paranoidandroid... i was just wondering if is there a feature similar to "expanded desktop" which is on paranoid, nothing else.
[Nexus 7 Android Development] sparksco:
I haven't been keeping up with cm's changelog lately. I just merge things in and some of my own changes (on the first post I believe) and build the ROMs optimized with my own linaro toolchains that I build based off the monthly GCC releases from linaro. If there's a feature you want I'm all up for submitting new features to cm gerrit or merging them regardless if cm approves them. This all depends if the developers post their source as a open source project and if I can find that specific change/feature on github or wherever they post their source to. If there's no links to their source on their threads I don't even bother half the time.
[Nexus 7 Android Development] 57op:
Hey, i'm not asking you to merge any feature. It was just a question, that is whether your rom has an option to hide navbar.

Sorry if i bothered you.
[Nexus 7 Android Development] sparksco:
No worries. I'm just suggesting that you can answer all of your own questions by checking the first post and/or cm's changelog. Or if you have a feature request you can ask for it :)
[Nexus 7 Android Development] 57op:
I may have found sources of the feature i was talking about.

This shall be the code (which show toggle in powermenu if enabled):

// next: expanded desktop
// only shown if enabled, enabled by default
if(Settings.System.getInt(mContext.getContentResolver(),
POWER_MENU_EXPANDED_DESKTOP_ENABLED, 1) == 1){
mItems.add(
new SinglePressAction(R.drawable.ic_lock_statusbar, R.string.global_action_statusbar_status) {
public void onPress() {
Settings.System.putInt(mContext.getContentResolver(), Settings.System.STATUSBAR_STATE, Settings.System.getInt(mContext.getContentResolver(), Settings.System.STATUSBAR_STATE, 1) == 1 ? 0 : 1);
}

public boolean showDuringKeyguard() {
return true;
}

public boolean showBeforeProvisioning() {
return true;
}
});
}

in android_frameworks_base / policy / src / com / android / internal / policy / impl / GlobalActions.java (in private AlertDialog createDialog() {...})

Where POWER_MENU_EXPANDED_DESKTOP_ENABLED is

public static final String POWER_MENU_EXPANDED_DESKTOP_ENABLED = "power_menu_expanded_desktop_enabled";

in android_frameworks_base / core / java / android / provider / Settings.java (in public static final class System extends NameValueTable)

of course there should be other files (layout and strings.xml, public.xml i guess) that i'm not able to find due to my inexperience.
[Nexus 7 Android Development] sparksco:
Right now my main concern is fixing the power HAL but once I'm done with all of that I'll have a look at it.
[Nexus 7 Android Development] superleeds27:
Looks interesting :)

Whats battery life like on this?
[Nexus 7 Android Development] Chapi:
Tabletui is a built-in feature in this rom or a external patch may be applied?
[Nexus 7 Android Development] sparksco:
Its uv/oc but you can change the voltages with system tuner app from market.

I haven't tried a tabetui patch but it should work.