yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] scaryshark:
To further this, I have never had any problems running at 1.4 but when setting to 1.5/1.6 it always freezes and needs a hard reboot after about 20seconds. However I've heard people run it at 1.6 all the time with no problems so I suggest a max of 1.4 but if you really want to know, try it at 1.5/1.6 for an hour or two with high usage and make sure set on boot is not ticked. If you feel it's stable then I guess YOUR device can handle it.

You have to remember any OC above 1ghz has the possibility of causing some damage but if you want performance 1.2 is a "safe" OC. 1.4 is riskier bit probably fine but 1.5&6 can pose some risk to the device if mishandled.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Bigandrewgold:
I run mine at 1.5 with no issues, but it varies from device to device.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] D.N.K.:
Yes... I have Overclocked my tab to 1600Mhz... Only problem is faster battery drains...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Hawk600:
I am running 1600 and so far no problems.

It froze only once while watching HBO Go but it could be something Wifi related as well.

Still watching watching battery life. I set the lowest speed to 216mhz in order to save some battery.

Above 1400 this tab feels smooth as the Nexus 10, I am running stock ROM with A1 kernel by the way.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] pwhitetom:
yes, it will be useful
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Self-Mao:
Never overclock my tab so much but you have to expect some issues if you overclock too much and too long.

As everybody say, it depend of your device. And of course, on all device you'll experience a faster battery drain. Try not to set the CPU manager to "performance" :p
[Galaxy Note II Q&A, Help & Troubleshooting] bassM:
Is there any way to force the accelerometers to stay on when display sleeps?

I'd like to use apps that require accelerometers to work even when screen is off, such as accupedo and "Zombies, Run!" (on a treadmill).

Currently it's not possible since they stop working when display goes to sleep.

Any way to fix this?

Thanks in advance!
[Galaxy Note II Q&A, Help & Troubleshooting] bassM:
Screen Standby

Okey so a temporary workaround can be achieved by installing Screen Standby from Market (root).

I believe this could probably be achieved by patching the kernel since it's likely a config option (works as I'd like on the sgs3).
[Galaxy Note II Q&A, Help & Troubleshooting] wdylag:
Hello,

I would like to add to device custom cerificate issued by Comodo CA. This certificate secure my e-mail account on my computer now, so I have a copy of this cert with private key in one file .p12

How can I add this cert this my Note II and how can I use this cert im E-mail app to secure my messages (signing, encryption, decryption)?
[Galaxy S II Q&A, Help & Troubleshooting] basilhsk.7:
Hello,

i want to ask if someone try a different kernel in OlloS2 Armageddon RoM 4.1.2

I try dorimanx and siyah but phone stuck in bootload and shutdown..!!!

Its a great rom but i want to overclock cpu because it stuck in overflowed cpu and its annoying..!!!!

PLZ anyone help..!!!

P.S

(its my first thread so dont judged me plz)!!!!! :rolleyes:
[Galaxy S II Q&A, Help & Troubleshooting] Donnie Sins:
First search and read before you post. Then you would know there aren't any other kernels than Philz at the moment for roms based on the JB-leak. That it's your first thread isn't an excuse, because you can read English;)

Sent from the Matrix
[Galaxy S II Q&A, Help & Troubleshooting] basilhsk.7:
I didnt know that i cant use another kernel on the JB-leak.... :/
[Galaxy S II Q&A, Help & Troubleshooting] Donnie Sins:
And that's why you have to read;)

Sent from the Matrix
[Galaxy S II Q&A, Help & Troubleshooting] basilhsk.7:
apparently i am not such smart as u :p :p :laugh: :laugh:
[Galaxy S II Q&A, Help & Troubleshooting] basilhsk.7:
ff

:laugh::laugh::laugh::laugh::laugh:
[Galaxy S II Q&A, Help & Troubleshooting] basilhsk.7:
:laugh::laugh::laugh:
[Sprint LG Optimus G] neno2323:
This might not mean much being its for our neighbors to the north but hopefully its a step closer for us... http://www.androidauthority.com/canadian-lg-optimus-g-cyanogenmod-10-1-140556/
[Sprint LG Optimus G] megamaster2:
A dev is trying to build AOSP here. Maybe by Christmas :)
[Sprint LG Optimus G] sheek360:
Seems promising
[Sprint LG Optimus G] autoprime:
there are builds floating around for the sprint version. tho idk whats working(perhaps nothing other than booting).

IRC is the place to be. check the sticky at the top of the general forums or Q&A forums.
[Sprint LG Optimus G] johnq54:
Unfortunately they have a newer kennel than the US devices. Which makes it much harder to convert ours to jellybean.

That being said, you will find there are a handful of guys working on it on IRC. And trust me, they want it as bad as we do. Rest assured, we have a nice group of devs. This is the quiet before the Storm
[Sprint LG Optimus G] kh4osX:
I am coming to the Optimus community from the Evo 3D. With the bootloader we had to overcome, I have complete faith in the optimus devs. Hell, we've already got an unlocked bootloader, just a lil longer till we have some awesome roms.
[Sprint LG Optimus G] ackNalej:
I'm coming from the 3VO as well. I have full faith in the dev community here. Can't wait :)
[Sprint LG Optimus G] TechNinja49:
I'm guessing we'll have an AOSP build by early January. It's going to be awesome!
[HTC 7 Pro] bilmiyorumabi:
hi,

i m newbie on 7 pro. i want to install new rom to my t7576. but i didnt connect that with windows mobile device center. i connected to windows 7 with zune application. but when i want to install new rom deployment, running ROMupdateutility and it s says no connection with phone. i seeing in the device manager 2 item about my phone. first "Windows Phone USB" and second "HTC 7 PRO T7576" but the wdmc not seeing the phone. not connectting.

how can i connect my phone to windows 7 without zune and how can i install new roms?

thank you everybody.
[HTC 7 Pro] evath:
Hey,

You'll want to read this thread before doing anything to your phone, it has the info you need.
[Sony Xperia T, TL, TX, V] chrisp7:
Has anyone tried this on their Xperia V yet?

http://xdaforums.com/showthread.php?t=2049235
[Sony Xperia T, TL, TX, V] Harimoto:
Didn't dare try as there isn't a Tsubasa version the last time i checked the download site. :o
[Sony Xperia T, TL, TX, V] chrisp7:
How can you tell? Mine is bought from Sweden, wonder if that version is there.
[Sony Xperia T, TL, TX, V] chompiz:
It doesnt matter where you bought it. The name of Xperia V is always Tsubasa.

And until there is a file with the name Tsubasa in the download folder its not ready yet.

You can find the links to the folders here: https://sites.google.com/site/projectfreexperia/download/cyanogen-mod-10
[Galaxy Tab 2 General] _Variable:
Is there an official 4.1 for the 7" wifi only?
[Galaxy Tab 2 General] greeny2010:
This is for the wifi/3G P3100 - http://hotfile.com/dl/182576483/c6a...3100_BRI_1_20121127145652_eeluaie49v.zip.html
[Galaxy Tab 2 General] jaydyan:
try this

Try to look at this thread.

http://xdaforums.com/showthread.php?t=2032683
[Defy Q&A, Help & Troubleshooting] neolid:
Hi all!

Almost all ROMs out there are failing to work correctly or even boot on my Defy (red lens). Some do boot, some go to bootloop.

Here's the full story. Two days ago the latest CM10 nightly from Quarx went to bootloop, it was working just fine, but at some point the phone rebooted and didn't boot back up.

I've decided to try another ROM and installed WIUI v4 (JB) from CWM. I went to check device's internal memory and it appeared that I had 48 MB used and that that was all internal memory - the system hasn't even loaded total memory info.

I performed some search and found this thread with the similar issue: http://xdaforums.com/showthread.php?t=1940503

It suggested flashing an SBF via RSD Lite. I did that using the SBF from that thread (2.2 CEE Froyo). I suppose that was my mistake since the thread referred to Defy with a green lens. However, I was finally able to boot the device. I decided to try another SBF. JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDN to be precise. Everything went just fine. I was able to root the device, install CWM using SndInitDefy 2.0, and install stable CM7 (the official one, update-cm-7.1.0-jordan-signed.zip) and Froyo kernel from WIUI.

Everything was working fine except for the camera. It was showing the following error:

"Camera error. Cannot connect to camera"

After that I though that maybe I've messed up with SBF versions. The phone is not sold in Ukraine officially and I didn't remember which SBF it used when it was shipped.

I then followed the guide from All-in-one beginners guide and installed that Chinese SBF with Version 5 CG (thus I presume I can't flash any full SBF now since this will cause a black screen and I will have to re-flash 97.21.51 SBF and do all that stuff all over). Again, I was able to root the phone and stuff. However, none of Quarx's nightlies are working, CM7.2 or 2nd-boot CM10 are simply bootlooping, WIUI v4 can't connect to any of Google's services (they constantly FC), and none of the ROMs can connect to the camera.

Currently I'm using the following:

official CM7.1.0

Android 2.3.7

kernel 2.6.32.9-bg08c3c8vfcj78@zch68lnxdroid50 #1

Build number Gingerbread GWK74

I'm okay with staying on CM7.1, but I require the camera to work. So, the question is, what should be done in order to make the camera work?

Maybe, I should change some lib files, if so, could you please provide with the link to the correct ones? I've already tried some camera fix SBF's but they didn't seem to work. If there is any additional information required, please let me know.

Any help will be really appreciated!

Thank you in advance.
[Defy Q&A, Help & Troubleshooting] thekguy:
Maybe you could get rid of the sbf problem(camera issue caused by wrong flashing) by flashing a defyplus sbf with group code 6. Then your camera should work.
[Defy Q&A, Help & Troubleshooting] neolid:
Thanks, thekguy! Will try this later today.
[Defy Q&A, Help & Troubleshooting] neolid:
Nope, that didn't work, unfortunately. Flashed 4.5.1-134_DFP-125, but the camera is still failing, as well as the latest CM10. Any suggestions are welcome.
[Defy Q&A, Help & Troubleshooting] thekguy:
Hmm, latest cm10 2ndboot right? That's a very bad sign, since that rom indeed works with both the camera modules, and its really curious that it's not working.

Flash back to any defy bl6 sbf from this list(don't flash defy+ sbf since that approach isn't working):

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

Wipe data, and use the defy ultimate wiper script(it's there in themes and apps section, use ext4 version if you're on cm10 or ext3 for any other rom).

Now flash cm10 2ndboot build, and try using the camera.

Normally that should work, even if you have a green lens module, but if not so then it could be add a result of a hardware failure:confused:
[Defy Q&A, Help & Troubleshooting] neolid:
Yeah, I've also tried CM7 for Defy+, but that didn't work either. And I guess I pushed my device few steps closer to the brick yesterday. I flashed one of Chinese SBFs (JRDNEM_U3_3.4.3-36-1_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTINT_P011_A013_HWp3_Service1FF). It's BL7 SBF and it's known for its outstanding unbricking abilities. Didn't work for me. However, the bootloader is still accessible and I will keep playing with the phone today.

I'm getting tired of all this.
[Defy Q&A, Help & Troubleshooting] thekguy:
Didn't work? Camera or unable to boot?

Remember, you must wipe data from stock recovery before you can boot into the stock rom

Once you are running on the stock rom, check if the camera works. If not then follow my other post about getting to cm10 2ndboot. It may hang once on boot but it will boot after that. If still the camera is not working then I'm afraid it's beyond help
[Defy Q&A, Help & Troubleshooting] neolid:
Didn't boot at all, just a blank black screen. I can't enter stock recovery and the bootloader is not visible. However, if I boot up with power+vol+ and connect the phone to the desktop, RSD Lite detects the phone and I can flash an SBF. But my guess is that this would be useless since the last SBF I flashed was BL7.

Well, I'm at work right now, thus I can't try anything out right now. Theoretically, I should be able to flash any SBF with BL7, and root it using this guide http://xdaforums.com/showthread.php?t=1542956
[Defy Q&A, Help & Troubleshooting] thekguy:
Then, flash both sbfs from that guide, and it should work.

You shouldn't get any blank screen, simply because you've got the highest possible group code, and you cannot have a wrong kernel just after flashing the sbf. It must work
[Defy Q&A, Help & Troubleshooting] neolid:
Thanks. Will definitely give it a try once I get home.
[Defy Q&A, Help & Troubleshooting] neolid:
OK, I've managed to install 4.5.1-134 DFP-231 Retail.en.EU CEE, root it, and flashed CM10 2nd-boot nightly. However, I'm still unable to boot the phone. It shows CM10 logo spinning for 10-20 seconds and then reboots. I assume that this is the only ROM which can make the camera work. Am I right? If yes, what should I check or do in order to fix the boot looping? If I can use some other ROM, could you please let me know which one exactly and what can be done in order to fix the camera?

Thank you!
[Defy Q&A, Help & Troubleshooting] neolid:
Just flashed CM10 and checked the log, there's the following message:

Could this be a source of the problem?
[Defy Q&A, Help & Troubleshooting] neolid:
Another update. I've installed WIUI v4 for GB kernel and looks like it requires less internal memory/RAM to run so I'm able to boot the phone completely. And it's showing that I have 0.00 MB of internal storage in total and 58 MB used. I guess internal memory issue is somehow related to the bootloop.
[Defy Q&A, Help & Troubleshooting] thekguy:
Before flashing cm10, use both the ultimate wiper scripts(ext4 and ext3 version)

After flashing cm10, go back to boot menu and select tools, file system tools and format to ext4. It should boot now
[Defy Q&A, Help & Troubleshooting] neolid:
Thanks for the clue, but I'm afraid that didn't work. Since I had some time and have no data to lose, I wiped the phone from stock recovery, flashed both standard 4.5.1-134 DFP-231 and rooted 4.5.1-134 DFP-231, wiped everything using both ext3 and ext4 Ultimate scripts, flashed Quarx's 2nd boot CM10, formatted data and cache to ext4 using File System tools. CM10 still bootloops, but at least now I have internal memory info displayed correctly in WIUI v4 (JB). But since it's not a 2nd boot ROM, the camera isn't working.

In fact, I've tried some other 2nd boot scripts (NEGAN-6DIC and Codenameandroid 3.6.6), but they are bootlooping as well.

Maybe there are some other 2nd boot ROMs I should check? Or maybe if I get a nandroid backup of a working system I could restore it on my phone?
[Defy Q&A, Help & Troubleshooting] thekguy:
Try converting to ext4 and flash after that. It is really curious why it bootloops. You must get cm10 to boot, so that the camera works. Look here for downloading a stock kernel that should hopefully fix the boot loops.

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

Scroll down for the post which talks about having a compatible stock kernel which should allow 2ndboot to work(it's titled for bl7 users).

Flash this kernel after stock sbf flash, then try installing cm10.

Let's see how this goes
[Defy Q&A, Help & Troubleshooting] neolid:
Still no joy. Neither formatting, nor following this guide http://xdaforums.com/showthread.php?t=1909242 worked. Is there a way to see boot log from a desktop? I have both Debian and Win7 on my desktop.

Thanks.
[Defy Q&A, Help & Troubleshooting] thekguy:
There is a way to debug using uart, but I have no experience with it. So, sbf flash+ compatible stock kernel failed? Please describe the boot loop. Does it reach the cyanogenmod logo? Or stuck at red Motorola logo? I am at my wits end at this one. All my semi bricks and other problems I could fix by the methods outlined in my previous posts, but they don't seem to work in your case. You flash full sbfs right? And are you able to boot the stock Rom?
[Defy Q&A, Help & Troubleshooting] neolid:
Here's how it loops:

- the phone starts

- shows red Moto logo

- blue led

- red led

- blank black screen

- HW buttons blink once

- CM10 spins for approx 5-10 seconds

- the phone restarts and all the steps repeat

Yes, I'm able to flash full SBF (BL7 ones). I'm able to boot into a stock ROM, I can flash modded SBF for BL7 (the rooted one). I've tried flashing CM10 SBF, but the phone booted into a bootloader and showed an error, with set of numbers. Looks like because of the kernel (my guess is that SBF contains non-2nd boot version of CM10).

If I install WIUI v4 right after I flash rooted SBF I have no issues with the internal storage.

If I install 2nd boot CM10 (Kayant's, Quarx's) I get a boot loop (Ultimate Wipe doesn't help)

If I install WIUI v4 after CM10 (without re-flashing SBF's), I get 0.00 internal storage, but wiping data/cache from stock recovery solves the issue.

Unfortunately, wiping data/cache from stock recovery doesn't do the trick for CM10 2nd boot builds.

One more thing, after I flash CM10 and try to wipe data/cache from stock recovery for the first time, it shows recover log errors. There are errors when entering stock recovery after that.
[Defy Q&A, Help & Troubleshooting] thekguy:
Might be a false trail, but what about wiping from custom recovery? Dalvik cache wipe?

This indicates that the kernel had loaded before some other problem caused the phone to enter into boot loop. What about the camera in the stock build? Same error as before?:banghead::confused:

The cm10 sbf probably had a lower group code(bl6 perhaps) hence that approach won't work, and even discarding that it will yield the same results as before.

Also, in stock, check if the kernel version changes after you flash the compatible stock kernel from the thread I had mentioned earlier. This is important because otherwise there is no chance for cm10 to boot.
[Defy Q&A, Help & Troubleshooting] neolid:
Tried that as well with no luck. In fact, I can get non-2nd boot CM10 (from September, 24) to boot with a custom Quarx's kernel. Everything works, except for the camera.
[Defy Q&A, Help & Troubleshooting] thekguy:
The non 2ndboot version with quarx kernel? Did you use the jellyx custom kernel to achieve that? And what about stock Rom? Any luck?

If all this doesn't work then I guess something is messed up very badly and I guess no software repairs are possible at this stage. Probably should claim warranty:(
[Defy Q&A, Help & Troubleshooting] neolid:
I was using this kernel https://dl.dropbox.com/u/50071721/2ndboot_06.10.zip . It's from this guide:

I haven't tried stock ROM with that kernel yet. Should I give it a try?
[Defy Q&A, Help & Troubleshooting] neolid:
Forgot to mention. That thread indicates that the kernel, before flashing Quarx's kernel, should be 2.6.32.9-ge281b6e

hudsoncm@il93lnxdroid51#1. It is.
[Defy Q&A, Help & Troubleshooting] thekguy:
Don't try with stock. If that(your current configuration) is booting, then cm10 SHOULD boot. I'm really unable to figure out why the hell is an early version of cm10 custom kernel booting, and a recent one isn't. Try disabling adb deamon in the boot menu before booting cm10

And what about camera in stock Rom?

And stock kernel version is fine
[Defy Q&A, Help & Troubleshooting] neolid:
OK, I've flashed CM10 from 24.09, installed that kernel, rebooted, flashed CM10 2nd-boot, wiped Dalvik, formatted data/cache from Tools to ext4 and current system info is:

Model: MB526

Android: 4.1.2

Kernel: 2.6.32.60-Jellybeanquarx@debian#1

CM version: 10-20121205-NIghtly-mb526

Still cannot connect to the camera.
[Defy Q&A, Help & Troubleshooting] neolid:
Ha-ha. It's bootlooping again. This is driving me nuts.
[Defy Q&A, Help & Troubleshooting] thekguy:
Ok man, now I'm out of ideas. Does the camera work in cm10 without custom kernel? If not then it will probably not work with the 2ndboot kernel because both have support for red lense implemented in the same way(not a different driver I think). I'm really unable to help you any further:(. If I can think of something helpful I'll be sure to post back
[Defy Q&A, Help & Troubleshooting] neolid:
Nah, the camera doesn't work in any ROM. Thanks for helping me out and for not turning this thread in OP_his_thread.png.

Will keep wiping and flashing. Maybe I'm missing something.

The worst thing is that I can live without the camera, but I was going to give this phone away to my wife to replace her Wildfire S. And she's not excited with the idea of the phone without the camera.
[Defy Q&A, Help & Troubleshooting] thekguy:
As far as I can see, you've not missed anything, and probably done more than enough. It looks like some very weird hardware problem, but best of luck in your efforts, and may your camera start clicking again:D

Feel free to ask q's, and I'll try to answer when I have spare time in my hands
[Defy Q&A, Help & Troubleshooting] neolid:
Thanks! Will try to re-flash everything from the scratch once again.
[Defy Q&A, Help & Troubleshooting] neolid:
Re-flashed 4.5.1-134 DFP-231, rooted. I can boot into 2nd-boot ROM only after I format data and cache to ext3 or ext4 and only once. If I reboot after that, the phone will into the bootloop again. Camera still does work. Thoughts, anyone?

Thank you.
[Defy Q&A, Help & Troubleshooting] ScullShot:
Guys I've installed the latest 2nd-boot builds for my defy+ but i have problems with wifi and keyboard (they dont work) is that a known bug or am i doing something wrong? please help
[Defy Q&A, Help & Troubleshooting] thekguy:
@neolid if the camera didn't work then it rules out software problem, probably the module has failed. And, as usual, the 2ndboot problem does not fail to amaze:D and try to wipe cache and dalvik after 1st reboot

@ScullShot there's no such bug refer to the earlier posts in this thread for instructions on how to clean flash cm10
[Defy Q&A, Help & Troubleshooting] neolid:
Looks like you're right. There's one thing I've forgotten to mention in OP: when the phone first restarted and went bootloooping, the camera LED was always on (not full power, though) even when the phone was completely off, but with the pattery plugged. I guess I should try to find someone who works with the hardware issues.
[Nexus 10 Android Development] jakdillard:
delete this thread
[Nexus 10 Android Development] jakdillard:
http://d-h.st/jPi

Small update adds recents clear all button and removes some g-apps that are available in the play store also adds hi-res wallpapers to launcher
[Nexus 10 Android Development] jakdillard:
ROM Overhaul ......

Ok so I noticed that most of the ROMs that I have used here including my own has been recreating the wheel so I have decided to go back to my roots and make pure AOSP with only the "fixes" found here and from AOSP so my ROM has become "clean" and basically stripped of its samplings from other developers written code to pursue my own originality so if you want just a basic AOSP ROM here is where you can come.

flavor of the day:

http://d-h.st/28m

Happy Holidays to All!!!
[Nexus 10 Android Development] situman:
Running your latest build and its really smooth. I'm hoping the WiFi not reconnecting after tablet sleep bug is not present but it did take a while for it to reconnect.
[Nexus 10 Android Development] Leon H:
Running the latest version, it resets every once in a while. Doesn't seem to be tied to any particular app or activity.
[Nexus 10 Android Development] jakdillard:
Thanks I will look into that at the moment I am in the process of updating and fixing some of the bugs I've found