yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] PKFR4Life:
I completely understand.

I have experienced the same exact thing! And I did the following to try and isolate the source of the issue:

[SGH-T999]

Opened up the camera app without GAPPS. Never restored data either. Camera comes up showing the rear. Switch to front side and there is the distortion. But leave the camera set to front and leave the app. Pull up the camera app again so that it loads up the front side at first. Distortion gone. Now, when the cam loads up in front side at first, you can switch to rear and the distortion appears again. Get the pattern? The distortion only occurs after a transition. Strange behavior.

1. Flashed different ROMs (Carbon, ChameleonOS, AOKP, CM 10.1 Stable, CM latest nightly [20130702]) Same symptoms.

---> Advance wipe (TWRP - Dalvik cache, system, data, cache) each time. Is the Format Data button any different? Haven't tried it.

2. ODIN STOCK Root66 4.1.2. No issue. Flash back to a CM ROM or CM based ROM, its funky all over again.

3. Tried alternative camera apps and the symptoms don't occur the way the default cam app does, but there are other issues. Take a photo (front side) with Snap Camera and the phone goes black and reboots. Take a front side shot with Camera 360 and the phone goes black and reboots. Front side shots doesn't freeze the phone with the default cam though.

4. Replaced /system/cameradata files with other files I've found on this site. Still nothing.

I'M DYING HERE.

I'm thinking about wiping the entire internal SD card. Perhaps reformatting or repartitioning the internal SD card.

PS: Distortion only occurs when the front side cam is set to 1.9 MP. Doesn't occur ever when set to 1.3MP. Freezing still happens though regardless.
[Galaxy S III Q&A, Help & Troubleshooting] PKFR4Life:
Distortion Finally Resolved?

It seems that with the 2013-07-08 nightly, the distortion is gone. I looked into the GITHUB on that nightly and found the following lines:

res/values-pt/cm_strings.xml

<string name="voice_hint">Tire foto à distância ao falar uma palavra chave: \'Cid\', \'Whisky\', ou \'Chesse!\'</string>

<string name="pref_nohands_persistent_title">Mãos livres persistente</string>

<string name="pref_camera_nohands_voice_entry">Voz</string>

+ <string name="pref_camera_picturesize_entry_13mp">13M pixels</string>

+ <string name="pref_camera_picturesize_entry_12_8mp">12.8M pixels</string>

+ <string name="pref_camera_picturesize_entry_11_5mp">11.5M pixels</string>

+ <string name="pref_camera_picturesize_entry_9mp">9M pixels</string>

+ <string name="pref_camera_picturesize_entry_7mp">7M pixels</string>

+ <string name="pref_camera_picturesize_entry_6_4mp">6.4M pixels</string>

+ <string name="pref_camera_picturesize_entry_6mp">6M pixels</string>

+ <string name="pref_camera_picturesize_entry_4_5mp">4.5M pixels</string>

+ <string name="pref_camera_picturesize_entry_4mp">4M pixels</string>

+ <string name="pref_camera_picturesize_entry_3_7mp">3.7M pixels</string>

+ <string name="pref_camera_picturesize_entry_2_5mp">2.5M pixels</string>

+ <string name="pref_camera_picturesize_entry_2_4mp">2.4M pixels</string>

+ <string name="pref_camera_picturesize_entry_2_1mp">2.1M pixels</string>

+ <string name="pref_camera_picturesize_entry_1_9mp">1.9M pixels</string>

+ <string name="pref_camera_picturesize_entry_1_5mp">1.5M pixels</string>

+ <string name="pref_camera_picturesize_entry_wxga">WXGA</string>

+ <string name="pref_camera_picturesize_entry_xga">XGA</string>

+ <string name="pref_camera_picturesize_entry_svga">SVGA</string>

+ <string name="pref_camera_picturesize_entry_wvga">WVGA</string>

+ <string name="pref_camera_picturesize_entry_wqvga">WQVGA</string>

+ <string name="pref_camera_focustime_entry_5">5s</string>

+ <string name="pref_camera_focustime_entry_10">10s</string>

+ <string name="pref_camera_focustime_entry_15">15s</string>

+ <string name="pref_camera_focustime_entry_20">20s</string>

+ <string name="pref_camera_focustime_entry_30">30s</string>

+ <string name="pref_camera_timer_entry_10">10s</string>

+ <string name="pref_camera_timer_entry_20">20s</string>

+ <string name="pref_camera_timer_entry_30">30s</string>

+ <string name="pref_camera_timer_entry_40">40s</string>

+ <string name="pref_camera_timer_entry_50">50s</string>

+ <string name="pref_camera_timer_entry_60">60s</string>

+ <string name="pref_video_hdr">HDR</string>

I have this nightly and the distortion is gone. It seems this may have been the fix.
[Galaxy S III Q&A, Help & Troubleshooting] PKFR4Life:
Camera Distortion / Crashing Finally Fixed

Hey everyone, I think I've finally done away with the camera distortions and crashing. My last post, stating the distortion was resolved after downloading a nightly was not quite all that I had expected. The distortion symptoms changed and simply seemed fixed, until I changed more settings that would make it evident that the issue still persisted.

I could go into the default camera app and switch from rear to front and vice versa without getting the distortion this time, but when in front view, you set the resolution from 1.9 MP to 1.3 and the distortion occurs. As before you would simply transition from rear to front or the other way around to catch the distortion.

My absolute fix was downgrading from JB 4.2.2 to JB 4.1.2 on a stock TW ROM. I couldn't remember at the time if I had already done this. I wanted to see if the distortion had occurred here too. I mean, the Gallery app would definitely be different. I found the issue no longer persisted. I started thinking that I guess I'll just stay with this but felt sad about leaving CM. I then flashed CM 10.0 since it was also JB 4.1.2 and I got excited that the issue still didn't occur! Taking front-side camera shots with all 4.2.2 ROMs crashes my phone making it reboot.

My thought/theory is that since the T999 never got 4.2.2 officially, the porting of 4.2.2 was problematic in general. But only to T999 models? I haven't heard anyone else have these issues on this site. Since 4.1.2 was officially deployed, CM had that to go off of to build his CM version. I don't know. But I am SET.

NOTE: In the process of going back to 4.1.2, my GPS lock went whack. I did this to resolve the issue.

http://xdaforums.com/showthread.php?t=2211690
[Motorola Droid 4] downloader3230:
Hi! In headphone jack was a lot of junk, and I disassenble phone to clean it up. Now when I try to turn on phone, it simply turn off. fristable shows Moto logo, when after some random time phone turn off, as if battery have no energy for. and when phone is off, I plug charger, and phone shows indication of charging: 0%, 5% and at once 100% during some seconds. what is the problem and how to solve it?
[Android Q&A, Help & Troubleshooting] clsmn:
Hey guys!

I've already posted my problem in the Nexus 4 Q/A-Forum.. till now without help. Well i thought that maybe here is a good place to get help, too!

So whats my problem.. Yesterday i flashed a new update of Xylon-Rom (clean flash) on my Nexus 4. Installed and restored all Apps. Usually I use Swiftkey 4 as keyboard, so I set up everything like all the times before. The last times everything works fine, but this time not. I set up SK as my standard keyboard and began to write. After a while I wanted to write again, but suddenly there was the AOSP keyboard. Changed back to SK. But after some moments it happend again. So everytime when there is a text input AOSP appears.. I change back to SK then, but after turning screen on some minutes later AOSP again.

As it would be not enough, the same thing is happening since yesterday on my gf phone (HTC One S, also rooted with Carbon Rom). Like on my phone, it never happenend before.

What I've done till now? Erased App-Data of both keyboards, disabled AOSP keyboard. Everything without success.

Dont know why it happens now... I often flash other Roms, Updates etc and I use Swiftkey for a long time. Restoring with Titanium works everytime. And this time i haven't done any other thing on Restoring.

I hope u understand my problem (my english isn't the best :D ) and anyone could help me!?

Thanks so far.

Cls
[Android Q&A, Help & Troubleshooting] clsmn:
Tried to freeze the AOSP in Titanium -> no effect

Set Swiftkey as System-App -> no effect

:X
[Android Q&A, Help & Troubleshooting] zard:
I was encountering this with swipe keyboard previously, and my solution was to use swiftkey.
[Android Q&A, Help & Troubleshooting] zein_syria:
same thing

im suffering from this problem too.. no solution yet :3
[Sony Xperia L] theserpent:
This thread is the one stop to all problems we have so far faced with our Xperia L,Basically it's a FAQ

Q.1:My Xperia L has a BatteryDrain issue.

Yes,that's a common problem in most of our devices,Jelly bean is known for battery drains

Q.2.The Notification light is not multicolored?

The LED light is multi colored, but for notifications(Messages,facebook,whatsapp) we get only a whitish purple light,while for calls we get red or a color depending on your theme :)

Tell me what all to add up more
[Sony Xperia L] sudhamsu:
For longer battery life, use Wakelock Detector app to find out the heavy-on-battery apps.

Then one can try the Snapdragon BatteryGuru app by Qualcomm (just dont forget to add your most needed apps to the whitelist).

Also, STAMINA mode provided by Sony is quite good, here too, dont forget to whitelist your most used apps.

Battery life should be good with these apps watching the battery-hungry apps!

I'm able to sail through the day easily, with around 18 hours backup - can go beyond 24 hours sometimes, depends on the day. Of course, the results will be different for everyone depending on the apps you whitelist.
[Sony Xperia L] theserpent:
Same here, these days my phone lasts for 30 hours.I'm not a heavy user :)

Just whatsapp,music,little browsing.Day ends with 65-70%(As 8 hours stand by after removing from charger at 7 AM )
[Sony Xperia L] theserpent:
Any more Normal problems?
[Sony Xperia L] Dr Goodvibes:
(1)Does the XPERIA L support 32GB Class10 MicroSD cards?

(2)Does the XPERIA L provide on the go (OTG) USB support?

Can I plug a 32GB USB flash drive into the USB/MHL port?
[Sony Xperia L] Outpapa:
Xperia L supports 32GB class 10 SD card, that's written on Sony's website. It could probably support 64GB SD card if it is like the Xperia Z.

I did not see any option concernin OTG. Maybe is it possible, I don't know.
[Sony Xperia L] Dr Goodvibes:
Cool, but does it say Class10? It may say 32GB MicroSD cards and we assume class10, but is that a correct assumption.

The Sony XPERIA L white paper only refers to 32GB MicroSD cards and this could be Class4 or Class6.

I've read posts on Sony talk where many people have not been able to use their existing class10 16-32GB MicroSD cards.

But maybe, it could be just a format/cluster size issues on the card and not a general class10 MicroSD card issue.

Anybody have a 16-32GB Class10 MicroSD successfully working in their XPERIA L?

I only have class10 32GB and above cards.

I have a class10 UHS-I 64GB MicroSD card in my XPERIA X10i

Hmmm, OTG USB is a bit of a worry and the sooner someone plugs a flash drive into their XPERIA L and verifies a successful USB/MHL connection the better.

Logitech USB 2.4GHz Unifying mouse/keyboard connection would probably be hoping for too much, but if possible, that'd be brilliant.

Considering buying an XPERIA L and just ticking a few boxes.

Thank you for your input.
[Sony Xperia L] Shivam Kuchhal:
I have checked OTG connection. It doesn't work, however with custom kernel, you can use PS3 controller. I have tested that
[Sony Xperia L] Toledo_JAB:
this thread is the same type of discusion thread as THIS THREAD

thread closed
[Galaxy S II Android Development] kalpik:
This was just a personal hobby project, but it seems many people are using these builds, so I'm starting this thread to keep the main CM thread clean.

The nightly is built at 6:30AM IndianStandardTime (GMT+5:30), and contains all changes synced till then. The most prominent difference between these builds and the official ones is that there builds are compiled using the Linaro toolchain. To me, this results in a smoother UI, and better battery life than the official builds. From time to time, these builds may also contain some hotfixes for small problems on official builds, and they may also contain some cherrypicks.

You can just install these builds over official builds without a data wipe. You can even go back to the official builds without a data wipe.

Download link: https://copy.com/vJqpoVqwoUXJ

Please check MD5 before flashing.
[Galaxy S II Android Development] TheSaw:
What are the drawbacks of building with Linaro? I assume there must be some, if the official build is not using this, right?
[Galaxy S II Android Development] kalpik:
The drawbacks are that theoretically, there might be some unexpected side effects if building from a non-standard compiler. I personally haven't seen any since I've been using it. Also, I think the CM team thinks Linaro is just placebo, and hence they don't use it.
[Galaxy S II Android Development] chrhei:
Can you please provide the MD5sum?
[Galaxy S II Android Development] mr_zuff:
I'm glad you opened an independent thread for your build! :D

Keep it up!! :)
[Galaxy S II Android Development] kalpik:
The MD5s are also present in the link.
[Galaxy S II Android Development] markjamezmark:
Is the pixelated icons fixed on your latest build: "6-25-2013"??

thanks.. :D
[Galaxy S II Android Development] kalpik:
Yes, they are fixed. Just so you know, they will be fixed in the next official nightly too :)
[Galaxy S II Android Development] markjamezmark:
Nice! That's I've waiting for. Currently downloading your personal compiled build.

Do you have any ideas when the final/stable build will be released?
[Galaxy S II Android Development] kalpik:
Never, as our devices are't fully open source :(
[Galaxy S II Android Development] dinos3:
What is hotfix? Sry for noob question ;)

And where is changelog?
[Galaxy S II Android Development] kalpik:
There are no stupid questions, only stupid answers ;)

I'm sorry I didn't explain it better in the OP. By hotfix, I mean like the icon pixellation issue that was present in the past few official nightly builds wasn't there on mine. So from time to time, if I find some problem in the official nightlies, and I can fix them, the fixes will be included in my builds :)
[Galaxy S II Android Development] dinos3:
Thanks ;)

Are you going to write changelog maybe?
[Galaxy S II Android Development] kalpik:
Changelog is the same as the official changelog :)
[Galaxy S II Android Development] diddly3000:
Going to flash this because.

A) last few roms I Flashed have either broken phone or Gps won't lock never both working.

b) and cos cyanogen mod is my preferred base for a rom :D

thanks buddy will report back after installing :)
[Galaxy S II Android Development] feydakin:
Just to be sure: Can I fix your build over the official CM10.1 nightly without a full wipe and go back to the official Nightly when needed?

Edit: Chrome reports m-10.1-20130625-UNOFFICIAL-i9100.zip as malicious "m-10.1-20130625-UNOFFICIAL-i9100.zip scheint schädlich zu sein."
[Galaxy S II Android Development] kalpik:
That is correct :)
[Galaxy S II Android Development] 70x7:
When GPS don't lock in a nightly, wipe cache partitions and dalvik cache and fix permitions. Ever works for me.
[Galaxy S II Android Development] CRXed:
Yup, I have seen that too. But I think Chrome does not like copy.com.
[Galaxy S II Android Development] diddly3000:
Nice rom so far. Gps works as does phone :p
[Galaxy S II Android Development] ph3n0mII:
[MENTION=2588207]kalpik[/MENTION] thanks for cleaning up your downloads folder. Much neater now :):good:
[Galaxy S II Android Development] kalpik:
Good to know people still use my builds :D
[Galaxy S II Android Development] ph3n0mII:
Yeh I use your cm10.2 builds, and [MENTION=1077833]infected_[/MENTION]'s cm10.1's, both with latest [MENTION=2376110]dorimanx[/MENTION] beta's :D

You still using the automated buildbot yeh?
[Galaxy S II Android Development] kalpik:
Yep. Still using the automated buildbot :)
[Galaxy S II Android Development] ph3n0mII:
Any possibility of making a cm10.1 build without the stupid http://review.cyanogenmod.org/#/c/48204/ bugfix removed? :cowboy:

Or whatever disabled the back-to-unlock feature(bug)?

They should have made a checkbox for it instead of removing it :(
[Galaxy S II Android Development] deepongi:
[MENTION=2588207]kalpik[/MENTION] how many cherry-picks are you using to build 10.2 with linaro arm-linux-androideabi 4.8?

Sent from a i9100, a mobile bad ass machine..!
[Galaxy S II Android Development] kalpik:
None.
[Galaxy S II Android Development] deepongi:
LOL... Cool mate... Then you are making fake linaro builds...

Sent from a i9100, a mobile bad ass machine..!
[Galaxy S II Android Development] kalpik:
Cool :)
[Galaxy S II Android Development] deepongi:
You better delete default AOSP toolchains... And then try to build with linaro.. :D

Sent from a i9100, a mobile bad ass machine..!
[Galaxy S II Android Development] jgcaap:
Any update comigo for cm 10.1 ? :)
[Galaxy S II Android Development] kalpik:
Sure! Why not! Wait for Monday :)
[Galaxy S II Android Development] deepongi:
eu se fosse a ti não me fiava muito nesta rom ser completamente compilada com linaro...

é impossível compilar apenas com as linaro toolchains (rom e kernel), sem aplicar cherry-picks/commits necessárias, para a build nao quebrar devido a erros, por falta dessas mesmo...

o mais provável e certo, é ele estar a compilar em mixed-mode... ou seja esta a usar a linaro toolchain e as AOSP ao mesmo tempo... fake linaro builds...

~~~~~~~~~~~~~

i wouldn't really on those builds. its imposible to compile ONLY with linaro without applying the necessary cherry-picks...

more info: http://xdaforums.com/showthread.php?t=1988315 (important stuff on the last pages...)

@kalpik , mate i know you tough that you were building it right, but if you remove from manifests xml the AOSP toolchains or delete the folders with it, and try to compile with only with linaro/sabermod, after 5m the build will break, because it weren't applied the necessary cherry-picks to custom compile with linaro/sabermod...

hope you're not mad at me, but users have the right to know what they are flashing on their phones...

cumprimentos/regards...
[Galaxy S II Android Development] kalpik:
Too all who want to know, I'm only compiling the kernel with linaro. And I absolutely know what I'm doing and how.
[Galaxy S II Android Development] deepongi:
yep, piece of cake... just add TARGET_KERNEL_CUSTOM_TOOLCHAIN = xxxx to BoardConfig.mk .. :D, and place the arm-eabi toolchain on the right folder... cool...

the idea of a linaro build is that the build is fully compiled with linaro... it wouldn't make much sense compile only the kernel, and not the rom itself.. most users don0t even use stock kernel, so if they flash another kernel, will end up with a normal build... lol.

but i'm out of here...! i had to inform users.

cheers!
[Galaxy S II Android Development] CRXed:
Then let me inform the users too: Kalpiks builds have always worked perfectly, improving speed and battery life over official CM.

I prefer this over a build that needs cherrypicks to work. More room for error...

Way to go to call other peoples builds unreliable and question the quality of their ROMs or say they are doing it wrong....not cool man, not cool.
[Galaxy S II Android Development] CRXed:
CM10.2 http://review.cyanogenmod.org/#/c/50766/

CM10.1 http://review.cyanogenmod.org/#/c/50738/ with more detailed explanation

So hopefully no more high Android OS in the next nightly!
[Galaxy S II Android Development] kalpik:
Cm 10.2 will auto compile. Will manually do a new 10.1 build on Monday :)
[Galaxy S II Android Development] lerkin:
Can Monday start a bit earlier, today for example )?
[Galaxy S II Android Development] deepongi:
you really don't know jack about custom building ... lol. you MUST cherry-pick all the necessary commits, so you can FULLY compile a linaro build... inform your self a little more...

and, yeah... its better lead the users in mistake, thinking they are flashing a full linaro build, while they are flashing "half" a linaro build, and if they use another kernel, it will be a normal build... ;)

and for your information, cherry-picks (most, if not all of then made by one of the more than +100 engineers at Linaro, named Bernhard Rosenkraenzer), are necessary to compile a full working linaro build, and not just the kernel... you should better inform yourself, and not do "trash-talk" without having a single clue in how to build with custom toolchains or what you are talking about... building the kernel, doesn't required any patches cherry-picks, so wooooww thats a lot of work to place on one rom, thats is auto-built... :D

so maybe its better the thread title be named "[ROM][i9100][JB4.3] Linaro compiled CM10.2 nightlies (KERNEL ONLY)"

and at least i know i am building FULL linaro builds, and required a lot work, time and patience until it reached a full working bug-less compiled linaro build.... :)

but hey..., keep up the "good work?" until now ...

cheers!

PS: i would really like to know who elected you XDA Official CM Police... lol! my thread is opened to everyone... so those who want and have a reason to complain or want to criticize my work, i would love the feedback leaved on the thread... thanks! :cool:
[Galaxy S II Android Development] Jonny:
ENOUGH. Cut the flaming out NOW.

There is nothing wrong with calling out developers on matters if you think they may be wrong, however, it should be done in a polite and respectful manner and you should be willing to accept their side. Don't go into an argument like a big headed moron because you will get your ass kicked.

I'd also advise any fanboi's on either side not to get involved in a dispute between developers. These disputes can get quite hot headed as it is without you lot adding fuel to the fire and if severe enough the flaming could lead to an infraction or worse so for your own benifit, stay out of developer disputes unless you have something meaningful to contribute.

To the user who was spamming the report system (and for any other users who think this is funny and a good idea) if you ever do something like that again I will personally see to it that you are given a trip to bansville (free of charge of course).

Thread cleaned.
[Galaxy S II Android Development] kalpik:
I did not get involved anywhere. I never claimed I compile the full ROM with Linaro. This very issue has been discussed before in this thread. I do not see the need for it to be discussed every few pages.

There really was no dispute here. Please point me to it, if you think there was.

Thanks!

Back on topic: New CM 10.1 build released :)
[Galaxy S II Android Development] kalpik:
Thanks for replying! I changed thread title as per your suggestion. About the dispute, you mentioned it as a "developer dispute". I didn't get into any dispute with the other developer. Was merely pointing that out :)

Anyway, the other developer in question has a habit of coming to this thread, and starting a flame war, so I've learnt how to ignore that. So you won't find me arguing with him ever :)
[Galaxy S II Android Development] deepongi:
You dont have to. Already said what was needed to be said.

Good luck with your project.

Regards.

Sent from a i9100, a mobile bad ass machine..!
[Galaxy S II Android Development] CRXed:
Will make a lot of people happy, since you are almost the only one still compiling stock CM10.1

I've take the change and switched to 10.2 now, so I will be flashing your 10.2 builds soon :D:good:
[Galaxy S II Android Development] kalpik:
If you guys need 10.1 daily, I can set up the buildbot for that too ;)
[Galaxy S II Android Development] Edvin73:
Maybe not daily but once or twice a week would be more than good enough.:cool:
[Galaxy S II Android Development] kalpik:
Will see what I can do tomorrow :)