yashsingh1/xdaforums huggingface dataset:
[HTC Desire C] adityaiyerq:
daily use?

can this be used for daily use?
[HTC Desire C] Aman_Arora:
ImOf course its like all other cm based roms
[HTC Desire C] tekken 2:
SO Beautiful rom,Everything is wrking fine,But problem with Wifi,it not opens,just showing that wifi opening but not opens:rolleyes:

PLEASE help:confused:
[HTC Desire C] Quasar:
Just reboot
[HTC Desire C] racky29:
Bluetooth A2DP fix CM10

I think I may have found a fix for people having problems with A2DP Bluetooth music

I installed this honamiz beta recently and the A2DP Bluetooth music wasn't working like with most of the CM10 roms for Desire C

like t4nchan posted on post 94

the Bluetooth calls work but the music just plays on the phone speaker

so I had a look around and found this fix that worked for me straight away.

link to page I found

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

A2DP fix for media CM10

Looks like sample rate is missing in the at a2dp line in the "audio_policy.conf" file

File location:

/system/etc/audio_policy.conf

the line "sampling_rates 48000"

the number 44100 needs to be added before the 48000 with this "|" symbol

and it should look like this

"sampling_rates 44100|48000".

After changing the sampling rate save and reboot your device in order for it to take effect.

Edit file with ES-explorer or Root Explorer text editors.

and make sure you have system set to RW

the section your looking for is near the bottom section of the file

and looks like this

a2dp {
outputs {
primary {
sampling_rates 48000

Just add the 44100 like below and save file

a2dp {
outputs {
primary {
sampling_rates 44100|48000

this worked for me and may work on other Roms. good luck

thanks to the post by KRZ-2pa
[HTC Desire C] SiqrCarnbon:
DONT QUOTE THE WHOLE OP #VeryAnnoyingSoProbablyShould'ntDoIt
[HTC Desire C] hardymall20:
How can i get rid of 4.2.2 quick settings ?
[HTC Desire C] sohailrabani:
boot loops

hi folks

dont use this rom it boots up normal for 1st time then it will keep boot loops untill it get stuck on boot animation i have tried many times it just waste of time
[HTC Desire C] hardymall20:
sorry to say but this rom is not useless.. ...............i used this rom for 1-2 months i never had any problems ....................there might be some mistake in your flashing method.................... ..this ROM is really good .................it has bugs ,i agree but bugs that almost all CM10 ROMs have.......before coming to conclusion first ask if there is someone who faced the same problem.......did u try flashing again?....i never faced this problem:):D:D
[HTC Desire C] sohailrabani:
Hi [MENTION=259014]hardy[/MENTION]

i know very well how to flash a rom mate so its out of the question if i was doing something wrong anyways i have already sold the device coz its battery life was a problem now holding tohuawei :)
[HTC Desire C] hardymall20:
I am also waiting for my exams to get over so that I can change my mobile ..still it has been a great experience using this device given the fact it can run KitKat 4.4.4 ...really a great device and worthy enough to be my first android ...
[HTC Desire C] beegeero:
Thank you for your work.
[HTC Desire C] andr3marin:
gapps

where i can find gapps for this rom?
[HTC Desire C] hardymall20:
http://wiki.cyanogenmod.org/w/Google_Apps

Follow this link you can find the Gapps for CM10 ...That will work with this ROM ..:):)
[Verizon Samsung Galaxy Note II] xghino:
Hi.

I was wondering if anyone can help me out.

Im currently in Albania using Vodafone sim card. My signal sucks most of the time I have no signal its comes once in a while for couple minutes maybe and then leaves again.

When I put the sim card in my cousins S3 (which his s3 is from here) it works fine, full bars 3G

So its leading me to believe its my notes fault.

My APN settings are good because when the signal comes for that short time my phones data and voice work as they should
[Droid RAZR M Q&A, Help & Troubleshooting] netizenmt:
I am running CM 10.2 by Skrilax - http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907 (Might be fine with the DHacker version also, but this is what I used.

Pretty much everything seems to work including GPS. I do not have Bluetooth anything so I can't speak to that. Some (maybe most) people seem to have difficulty getting it installed, but it can be done. There are a few tricks to it. Here's what worked for me:

I highly recommend using TWRP 2.6.0 as that's what I use and I know it works. Not sure whether other recoveries will function the same or not.

What you need:

1. The most recent version of CM 10.2 from the link above.

2. Gapps Core 4.3 - http://goo.im/devs/BaNkS/GApps 4.3

3. Root for 4.3 - http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip

1. Erase everything except the external sdcard. Do it three times. (Don't ask, just do it.)

2. Also Format Data - what the heck, do that 3 times too.

3. Install the CM 10.2 ROM, wipe dalvik and cache again and reboot into the system. DO NOT install anything else at this time for best results.

4. Let the OS boot all the way to the desktop.

5. Unlock the developer options by going into Settings\About Phone and tapping 8 times on Build number. (Only needs done one time, updates do not hide it again.)

6. In Developer options, change Root Access to "Apps and ADB". (Go ahead and set up whatever else you want in Settings.Do not install any apps or updates at this time.)

7. Reboot into Recovery. Install Gapps Core 4.3

8. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)

9. Once the phone boots all the way, reboot into Recovery again and install Root using Supersu 1.43.

10. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)

11. Once System has booted, you can update SuperSu in the Google Play Store. The first time you open it, it will want to update the binary. It's very important that you choose the option to do it from Recovery. Your phone will reboot into Recovery, update the binary and then boot back into System.

12. Once all this is done, so are you. Restore your apps, allow Google Play to do any updates, and customize the layout to your tastes.

Note: Once you get a successfully installed 10.2 setup, you can dirty flash the nightlies. Always clear dalvik and cache. And always backup your apps before flashing anything if you want to make your life easier.

ENJOY!!!
[Droid RAZR M Q&A, Help & Troubleshooting] Brucifer5150:
Going to give it a go with CWM I'll let you know how it goes.
[Droid RAZR M Q&A, Help & Troubleshooting] Brucifer5150:
Well I got the rom to work but I could not get it to boot after loading gapps. I tried wiping data but no joy!
[Droid RAZR M Q&A, Help & Troubleshooting] kensdavid:
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!

I am not able to successfully root though. SuperSU complains:

"There is no SU binary installed and SuperSU cannot install it. This is a problem!

If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"

I have tried to reflash the SuperSU zip posted here multiple times to no avail...

Thoughts?

EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
[Droid RAZR M Q&A, Help & Troubleshooting] Brucifer5150:
Flashed TWRP and I was able to get it up and running having the same issue with root going to try the file above and I'll update again.

edit

*** the supersu 1.51 file worked for me as well. ***

---------- Post added at 04:43 PM ---------- Previous post was at 03:47 PM ----------

I'm still having issues. I got the root to work but everytime I reboot the device I have wipe data or it hangs on the boot logo.

---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------

Restored back to carbon rom 1.8. I may try again after a few more dailies are out. As this is my primary device I can not have the issues I saw. Admittedly it may be something that I did wrong and not the rom.
[Droid RAZR M Q&A, Help & Troubleshooting] ender4212:
Got this up and running last night and no issues so far for me. I'm wondering though if any custom kernels work with 10.2? I was curious about the vanquishpuppiesn12 kernel.
[Droid RAZR M Q&A, Help & Troubleshooting] netizenmt:
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters! :)
[Droid RAZR M Q&A, Help & Troubleshooting] helious007:
Thanks for sharing , make a mark
[Droid RAZR M Q&A, Help & Troubleshooting] jco23:
can you confirm if rear mic is working when taking videos? this has been the only hangup for me on the 4.2.2 ROMs...

I doubt it, since that functionality is probably kernel related, but still just curious...

thanks!
[Droid RAZR M Q&A, Help & Troubleshooting] Brucifer5150:
Ok I noticed that I had somehow installed the wrong TWRP I installed 2.6.0 today and I have so far had good luck phone is up and running and seems to be stable. At first I had some issues with a few apps throwing errors during the mass install when I sync'ed with Google but a manual download after and they installed just fine. Also the new camera app called focal has some issues for me it opened and took pics but images in gallery are blank. However the stock camera app seems to working fine at least for stills I have not tried video yet.
[Droid RAZR M Q&A, Help & Troubleshooting] georgeascott:
I've got this all working too, including root. But I've been noticing about a second delay when pressing power to unlock the phone. Sometimes it delays so long that I press power again. So when the phone does wake up, the screen goes off again from my double press of impatience. I'm running the 0907 nighlty
[Droid RAZR M Q&A, Help & Troubleshooting] sloosecannon:
FWIW, never needed to wipe data multiple times and I flashed everything at once. That said, still a good procedure to follow

Also, [MENTION=3024154]georgeascott[/MENTION], that's a known bug. It tends to SOD on occasion... Not much to do to fix except maybe overclocking
[Droid RAZR M Q&A, Help & Troubleshooting] zombolt:
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
[Droid RAZR M Q&A, Help & Troubleshooting] sloosecannon:
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...

Can always hope someone will Dev for it though
[Droid RAZR M Q&A, Help & Troubleshooting] zombolt:
I have no clue how to do those things. I got really spoiled on the dinc. So many people spoon feeding contributions to a fabulous device. It sure is a shame it's impossible to unlock my boot loader
[Droid RAZR M Q&A, Help & Troubleshooting] fargles:
everything I've run into *works*

but it all doesn't work so smoothly

Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
[Droid RAZR M Q&A, Help & Troubleshooting] yenchuchn:
netizenmt,

Thx a lot for your help. I`m now on cm10.2, too.

But there seemed to be some bugs.

1.I cannot install any apps from Google Play Store, or it hangs on the MOTO logo after reboot.

2.I can take calls, but cannot reach the 3G network.

P.S.When I try to use QPST to configure the phone, the QPST tells Serious error encountered, write to phone aborted.
[Droid RAZR M Q&A, Help & Troubleshooting] j27h:
I've installed CM10.2 two weeks ago and everything is working great! The first time I flashed it I got stuck at the CM boot animation... After ten minutes spent watching it I forced it to reboot: stuck again. At this point I booted back to recovery, followed thoroughly netizenmt instructions (wipe three times, really!!!), installed CM10.2, Installed gapps, installed supersu v1.43 and so on (follow all the steps netizenmt told us!)... Everithing worked fine then. At this point I changed build.props to make the phone works in GSM mode.
[Droid RAZR M Q&A, Help & Troubleshooting] IndianaBond:
If you go to settings/developer options and scroll down to HW overlays. Check the box to disable HW overlays. That should help with the tearing/chopping.
[Droid RAZR M Q&A, Help & Troubleshooting] fargles:
Also, maps FC all over the place as soon as you're using GPS.
[Droid RAZR M Q&A, Help & Troubleshooting] csa00:
from Vz

I having issue getting the TWRP 2.6.0 does any body know where i might be able to get it?

my xt907 is from Vz and ive been having issues rooting its a pain the ass i hope this method works any suggestions?

i ll try this method posted here once am able to get the TWRP 2.6.0.??

:) thanks.

:fingers-crossed:
[Galaxy Tab Q&A, Help & Troubleshooting] klappera:
Hello,

Is there a Samsung Galaxy Tab 3 Touchwiz rom for the Samsung Galaxy Tab P1000?

Thanks!
[Nexus 4 Original Android Development] molesarecoming:
As we all have figured by now, JSS is broken. The dead locks are in AOSP r2.1.

Do we want to search for solutions together and share what we might find here?

Options would be to bring this to Googles attention, monitoring and cherry-picking master commits (i just saw some today referring to dead locks) and tracking the differences between JWR (r1) and JSS (r2.1).

To me the issue seems to be not kernel related, looks like surfaceflinger to me, thread concurrency.

as for the symptoms,
[Nexus 4 Original Android Development] CoolApps:
It is true that it goes to deadlock for input but it occurs on other parts of the OS so it is not just input, input is just a strong way to get to the issue which is why it is reported on that part and it is more common on input.

Has stated above, Surfaceflinger is not just having issues with text input, it is also having issues with screen input has well.

Maybe some code in Surfaceflinger is having issues with the kernel since the code is not completely correct.

By the way I did get a deadlock while typing this.
[Nexus 4 Original Android Development] Bluewall:
This doesnt look like a memory (RAM) problem. I just used again my N4 and I got one of those freezes.

I say that because I got it right after rebooting, with no apps opened
[Nexus 4 Original Android Development] CoolApps:
I have over 1GB of ram free and still get this issue.
[Nexus 4 Original Android Development] realfelix:
I dont think that this is only related to surfaceflinger. It happens often enough when I left the phone with screen on some time and want to use it again. Everything locks up. Even the signal bar does just sit there. Aswell as when waking it up to enter my pin code.
[Nexus 4 Original Android Development] molesarecoming:
there are new commits up for frameworks/native master

R2.1 (JSS)

R1 (JWR)

it's interesting that R2.1 saw dead lock related "fixes" while master comes back to it.

the google developer had this to say

i'm trying this now - problem is the random nature. i haven't had a freeze for 3 days now. if more developers can implement changes maybe we can evaluate this better.

perhaps tracking more repos would make sense, fw/native is just a stab into the blue.
[Nexus 4 Original Android Development] derPianist:
I just wanted to say that its seems to be very app pendant.

I am experiencing those freezes only within whatsapp. while typing very fast on the keyboard, the freezes do often occur. it's not an app freeze, it's the deadlock freeze.

I did not notice something similar while using other apps, even apps which use a lot more of resources (like 3d games and stuff like that)

P
[Nexus 4 Original Android Development] CoolApps:
I have got the logcat and it contains a damn long list of ANRs, kernel issues and MUCH more. o.o

Screenshot of a log which says what is going on:

View attachment 2176393

Logcat here on my site: http://caftp.3owl.com/Downloads/Logcats/Log_2013-08-09_12-00-25.txt
[Nexus 4 Original Android Development] ceejay83:
I use Swype and never seen this issue. Weird
[Nexus 4 Original Android Development] franciscofranco:
I only got that problem while typing something and it seems some **** is doing too much work on the Main Thread.
[Nexus 4 Original Android Development] rmead01:
Moles I'm on your latest beta in the dev, the 8.9 build and I just experienced a lock playing candy crush. Wanted to give the feedback that the changes may not have helped.
[Nexus 4 Original Android Development] cocchiararo:
Is't it weird that some users have this and others do not ?

I had never seen this, 1 day with AOSPA kernel, then updated to faux 19b4 and then 19b4m (no oc).

I thought it might be related to the new touch driver, because i though only input was freezing (since i never saw this issue), but now i seem to understand that it is freezing the whole phone ?
[Nexus 4 Original Android Development] ciprianruse88:
I've tested plenty JSS roms and kernels combo and freezes are there and happening randomly.I really hope you guys can solve this issue.Good luck !:thumbup:

"using the search button won't get you killed" <--taptalk sig
[Nexus 4 Original Android Development] derPianist:
yes. I can confirm this. just answered a message in Skype and got the freeze. so it does not seem to be app pendant.

P
[Nexus 4 Original Android Development] franciscofranco:
I just got it using XDA app while typing. It looked like something was blocking the Main Thread/UI Thread.
[Nexus 4 Original Android Development] darkrom:
I got lockups constantly while texting. Froze the aosp keyboard and installed the Google keyboard from play store. So far not a single lockup
[Nexus 4 Original Android Development] scottharris4:
It's not a specific keyboard problem. Before I flashed back to stock ROM, I was getting freezes with google keyboard, swiftkey, and kii. Additionally, I was getting freezes when not even doing input. Most of the worst freezes occurred when downloading.
[Nexus 4 Original Android Development] dex2grigg:
+1
[Nexus 4 Original Android Development] justthefacts:
Google should be paying you guys instead of their pot head so called Engineers. :laugh:
[Nexus 4 Original Android Development] darkrom:
Just reporting in case anyone else was having the same issue I had. Typing was slow and choppy on aosp and had a roughly 80% chance of lockup. Since switching to Google keyboard that hasn't happened a single time.
[Nexus 4 Original Android Development] franciscofranco:
Keep the thread clean of useless posts please. If you have anything useful to add, logs, code improvements, ideas on how to fix this, then post. Otherwise dont bother posting.
[Nexus 4 Original Android Development] P00t:
delete. Wrong pa thread
[Nexus 4 Original Android Development] drawkcaB:
I somehow feel that these two are linked

http://www.androidpolice.com/2013/0...-other-apps-to-crash-when-you-copy-from-them/

I get freezes on whatsapp with swype

Hope this helps else delete :)
[Nexus 4 Original Android Development] odin13:
*******derp********
[Nexus 4 Original Android Development] bixano:
I'm using paranoidandroid date 8/9 beta, and have one freezy right now ! just to report that the "fix" don't fix =/

I'm on stock kernel ( that's come with paranoid android ) and don't change anything in the rom just open the app store and then click on the nav buttom to go to home and BUM it's freeze for a 5 seconds.....just to report it i don't know how to make a kernel debug, but in crdroid 4.3 and bricked kernel I pass 1 day typing a lot and send a lot of sms, playing a bit and didn't hade any frezze !

the same rom (crdroid) with another kernel like AK113 or Stock kernel, had freezes.... maybe bricked kernel fix something ? or the combo crdroid and bricked fix it ?! it's very ramdomly....but with paranoidandroid and the stock kernel that comes with the rom it's happen mst of time time for me ! even in the new test build ....

very sorry for my bad english !!!
[Nexus 4 Original Android Development] 1ceb0x:
Just wanted to add that with 4.3 alpha slim rom and franco unofficial jss kernel I had only one single freeze in 4 days and i text a lot. Using aosp keyboard. Bootloader and latest radio installed.
[Nexus 4 Original Android Development] nickshertzer:
Honest question, why not just rebase AOSPA off JWR?
[Nexus 4 Original Android Development] markd0wn:
People on XDA who like custom ROMs/kernels, usually want everything to be latest and greatest. Even if there are some bugs, they'd prefer having them fixed instead of reverting to an older android revision. JSS still has some advantages such as optimizations/improvements (newer GPU commits etc).
[Nexus 4 Original Android Development] Scottyfer:
Just got one while on a phone call and sending a text message, and the phone call stayed active in the background (I've had the same thing happen with Google Music). Whatever is causing it must be locking up the foreground process only.
[Nexus 4 Original Android Development] CoolApps:
Yeah that is pretty much what a deadlock is.

---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------

Franco is not Moles.

---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------

Nothing to do with touch drivers because it still picks up what you are inputting.

---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------

Both for sure, the System UI and the app is doing too much on main thread which causes a deadlock but it still registers the touch input so I have a feeling that there is more to that.
[Nexus 4 Original Android Development] dusk1911:
Guys I have been using 4.3 with Franco unofficial since they were released. I experience no freeze what so ever. I have tried to replicate that by typing very fast in both the xda app and whatsapp. Let me know if I can be of any help regarding logs or whatever you might need.
[Nexus 4 Original Android Development] CoolApps:
That is a Android 4.3 bug itself and this place is not a good place to talk about other 4.3 bugs except JSS deadlocks.

---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------

In the first page I did upload a logcat for any of you to look at so you know what is going on.

---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------

I know, it is just that you there talking to moles also quoting Franco.

Anyway we have to keep this place clean so useful stuff can be placed here and easy to find.
[Nexus 4 Original Android Development] CoolApps:
To clean this up there is a logcat on my website concerning this issue: http://caftp.3owl.com/Downloads/Logcats/Log_2013-08-09_12-00-25.txt

The issue occurs mostly on keyboard input which somehow either big in the main thread or something else is being big.

The deadlock also occurs outside keyboard input.

Now while this deadlock occurs it is still allowing touch input but of course it will not do that input until the deadlock ends which is like a queue of touch input which means it could be processing from anywhere.

In case you where wondering yes I did get a deadlock while typing and interesting enough it does go to deadlock if you type too fast due to too much input to process in the main thread which will end up flooding the main thread.

I am assuming that different keyboards do help because they use less processing in the main thread.

Because of the extended processing of keyboards or input the OS is waiting until it ends but because it didn't end within that timeout it will either be forced or obsolete for that time until it comes out of deadlock.

When the deadlock occurs it will hang on EVERYTHING, so bad that it will not update anything in the status bar such has the charging status.

Remember that I am assuming this so if it is wrong in a way then correct me if you really think it goes that way.