yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] AgentCherryColla:
I've spent all day looking at apps that cause this #lockup#. I get it on XDA HD after waking the device and switching a thread and scrolling to the bottom. Same thing with YouTube, and other apps that have list that need to be cached. Even contacts will act up.

Also the faster I type, the more likely I am to get a lockup .
[Nexus 4 Original Android Development] Holcomb227:
Has anyone had this freeze while NOT touching the screen? I only seem to get this if I touch the screen at the exact same time a background task is stopping or starting. Or if I let my phone sit for a bit (10 - 15 sec) then go to touch the screen and bam.
[Nexus 4 Original Android Development] WillJitsu:
I noticed the deadlock issue in a sound recording app that was saving recordings to emulated/0. I updated the path to /mnt/sdcard/ and the issue went away. I know the path was causing issues with Titanium Backup as well in 4.3. However, I have still experienced the locks while typing. Could this be related to background apps trying to write data to the sdcard using an invalid path?
[Nexus 4 Original Android Development] occtec:
To help out I can provide any catalog you need, just say the word. I am on PA3.95 08/08 using halfbreed kernel, nova launcher and latest 08/08 GAPPS. Not one deadlock or freeze. 4.3 is running smooth as silk, this for me was rectified on the last update of PA.

I hope I can help in someway, if you're pissed that I'm posting on this thread I will immediately remove myself and delete my post.

Cheers.
[Nexus 4 Original Android Development] TR2N:
Hello folks. I am posting here, because I have downloaded and installed Pauls PA Beta/Developer ROM to help eliminating the freezes. I had them two times, one browsing Google Plus with the app and the other one typing while using WhatsApp.

Also I have some heavy Android OS usage with last build over night. I don't know, if this is relevant for the freeze problem.

It is the first time I have this heavy load since updating to PA basing on 4.3

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] hughfollett:
This doesn't really seem a dev topic..

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] sMtt:
+1 to this. Devs already know the problem and people still telling they have deadlocks. Even we don't understand anything, just let the devs argue about what's happening in technical aspects. Keep thread clean
[Nexus 4 Original Android Development] CoolApps:
The paths has always had issues since there is multiples.

Sometimes if you download a file it will be in one SD directory but not in the other.

Now with 4.3 the bug worsened by a lot so you have to pick the correct one, hopefully this should be fixed in KLP.
[Nexus 4 Original Android Development] zorginho:
i'm not a Dev but, can be an issue inherent to io scheduler? we understood that this happens when a lot of things needs to be cached and on some rom + kernel the issue in not here.

maybe u can take a look on it.

sorry for my English and if I told something silly.

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] shr33kant:
Has anyone tried running the rom without root? Could be the daemon causing the deadlocks.
[Nexus 4 Original Android Development] CoolApps:
The deadlock is pretty much caused by too much stuff on the main thread and the multi thread is not getting used automatically while the main thread has issues with queueing processes or something so one slips out at a bad time such has the keyboard for instance is getting used by the user but the main thread detects it has some service which it is a keyboard service but it is not detecting has a keyboard service though so it is attempting to wait for it but because the user is entering text input on it while waiting then it ends up has way too much for the main thread which is why it is waiting, because it is doing way too much the system has to go to a deadlock state to stop all services so it is like some emergency state to prevent a memory leak or something.

This is some guess which does make sense so I am not sure if this is true.
[Nexus 4 Original Android Development] molesarecoming:
that was one thing i thought about as well - but i believe in the android dev section some guy just compiled a clean jss aosp and got into freezes as well. what makes this hard is the random nature. it happens maybe once a day or two to me, i cant really afford testing a device for so long, leaving all my work.
[Nexus 4 Original Android Development] molesarecoming:
i've been testing googles dead lock fr/native bugfixes for a while and got one freeze yesterday - means its probably not it. :(

been trying to make sense out of the logcat data and its inputdispatcher who's throwing these warnings but there are no relevant changes from r1 to 2.1.
[Nexus 4 Original Android Development] bandit1976:
I'm not a dev as well but may the information helps you guys out.

I was on raspbeenbelly and had no freezes with keyboard so on. The only freez i got was, when i played this game:

https://play.google.com/store/apps/...ium=organic&utm_term=bopbop+inferno+playstore

Since i have changed the rom and went to crdroid there are no freezes at all. Always using the same kernel and same settings.

May be some one can look for some differences the two roms. There might be the solution.
[Nexus 4 Original Android Development] Devilman539:
I know you told me in a previous thread that JSS Roms had bug fixes in them that corrected issues in jwr but I'm still on factory jwr with Franco and I've never had a lock up freeze or anything like that. Could there be something that could be extracted from that ROM or kernel to address the issue? I'm sorry in advance for posting here. I'm not a Dev, I just started reading through this and this is the first time I've heard of this issue.
[Nexus 4 Original Android Development] jcmaddox1:
Has anybody thought MAYBE its device specific? I have a friend running Jss on his GS3, he says he's never had a hang up. Just a thought, it might only be specific to the Nexus 4

EDIT: Which might explain why Google released JWR, and not JSS to the Nexus 4.
[Nexus 4 Original Android Development] cocchiararo:
maybe we could start a registry of serial numbers or something to identify when the problem phones have been made.

I believe i don't have the freeze issue, i got my phone from the 2nd batch that was sold in USA.

Faux does not have freezes, and i believe his is an early one too.
[Nexus 4 Original Android Development] leonleonleon:
Guys I am not a developer but I am trying to help, I made some tastings and I can surely say that the cycle battery makes my phone freeze, I am trying it now for about half hour and while I am at cycle battery I got freezes nearly 5 times more than when I have it regularly.
[Nexus 4 Original Android Development] molesarecoming:
i dont use circle battery. and as i said, you get this with clean compiled aosp without additions.

rasbean has it as well, browse through his topic and you'll see the complaints. now this seems to vary quite a bit with some people noticing is more pronounced and some seem to not have it at all. i doubt it was caused by your game, it was caused by your rom. im using the same apps on 4.3 that i always use and nothing should bring a phone down like that.

its JSS. of course you dont have that in a JWR rom, stock is JWR.

no, i asked around, people experience that on other devices as well. i know for sure that the nexus 7 flo had it.
[Nexus 4 Original Android Development] jcmaddox1:
I'm having freezes on an earlier model, so its not a matter of models.
[Nexus 4 Original Android Development] Somairotevoli:
Does faux use his own kernel? I've been using his kernel also without a single freeze or hangup. Was getting them with included kernel and they stopped after installing his kernel.

Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
[Nexus 4 Original Android Development] chiikko561:
Most def not true... My nexus 7 flo is stock with jss build not rooted and has these same problems...
[Nexus 4 Original Android Development] molesarecoming:
you get this even on stock android?? why is there no outrage. i had the impression that flos hardware stuff perhaps prevents it.
[Nexus 4 Original Android Development] chiikko561:
There is but everyone is blaming I hardware but I believe it be software because it is not all the time

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

[Q] Erratic/Jumpy Multi-touch

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

Freezing

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

Those with touchscreen issues: try this (let's get some data)

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

Another touch issue, with reproducible steps

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

As a matter of fact when I first got flo before update to jss when I was on jwr for two days with no problem until updating to jss...
[Nexus 4 Original Android Development] Tanmaynarang:
That makes sense because every night, I wake up and my phone is unresponsive and I have to hard reset. This is going to be bad once school starts and I need an alarm. :c

er, sorry, I misread :x but just saying if that's relevant. I'm on rasbeanjelly and I generally leave Skype and AndChat running at night
[Nexus 4 Original Android Development] molesarecoming:
i give this up, trying to revert most of my stuff back to JWR. the way i see it JSS is ****ed. hope that ends freeze gate at least for PA.
[Nexus 4 Original Android Development] ciprianruse88:
Wise decission and I hope that google releases 4.3.1 soon and fixes dead locks

Sent from Inferno
[Nexus 4 Original Android Development] jcmaddox1:
Its not worth downgrading. Its a freeze maybe every few days. For 5 seconds. Not that big of a deal IMO.
[Nexus 4 Original Android Development] ikmax:
It is a big deal. As a dev you want the best rom for your users. If you leave bugs like this in your rom you'll start losing users because it is not perfect.

If you want a better functioning rom it is (for now) better to use R1 instead of R2.1
[Nexus 4 Original Android Development] ciprianruse88:
I agree

Sent from Inferno
[Nexus 4 Original Android Development] molesarecoming:
for you and me, its not a big deal. for the hordes that trample xda topics to hades and back, it seems to me they're taking it rather serious. anyway, you want to see them happy, right?

i still dont know yet if its fixed for pa but im curious how the others developers handle this. and hats off to those that were clever enough to go jwr right away.
[Nexus 4 Original Android Development] mi3zu:
Ok, I'm sorry if this is known already but it seems to me that atm devs think that the device gets stuck for a few secs then every command gets queued and executed after the freeze.

I was playing a piano game today when the screen froze but I could still hear the game in real time as I was playing it was just the image that was stuck.

Maybe it has something to do with the new gpu commits and it's just the image that gets frozen?
[Nexus 4 Original Android Development] chiikko561:
You read my mind I had asked this morning in rasbeanjelly thread y nobody had done that???

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 4 Original Android Development] molesarecoming:
this is raw code we're talking about, gigabytes of it.

4.3 alone was a tough merge, hardest i have ever done. then you finally have a rom, and now you must revert hundreds of commits to go back or start from scratch. good luck with that!
[Nexus 4 Original Android Development] chiikko561:
That's why I salute all you hard working devs... You are the true reasons a nexus device is a NEXUS...

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 4 Original Android Development] cocchiararo:
He does.

I do too, but i used PA kernel ferst without issues.

Too bad google keeps screwing up like this
[Nexus 4 Original Android Development] ckret:
someone considered this? something like this happend to me, when i had a lockup in musicplayer

the music kept on running, just the input was frozen
[Nexus 4 Original Android Development] mi3zu:
Thing is input was still working for me I could play notes and hear them while the screen was stuck
[Nexus 4 Original Android Development] cocchiararo:
The freezes are already known and explained...

The issue affects most (but not all) people on JSS roms (different devices, not just Nexus 4 it seems). I myself don't see it on my Nexus 4 16gb from the 2nd batch that was sold in USA.

Moles already reverted most of JSS (wifi fix remains, kernel must be JWR now) on AOSPA, only google or some wizzard will be able to identify the JSS issue and fix it.
[Nexus 4 Original Android Development] ciprianruse88:
Yes.that is true.when the freeze happends if you touch nav keys or something else the sound is hearing but everything is frozen. Eighter google will release a fix or 4.3.1 or cm team will fix and release cm 10.2 official

"use the search button before posting stupid questions"
[Nexus 4 Original Android Development] PetritH:
Sorry guys, its says devs only but I have to confirm this, my father uses the Nexus 4 16gb from 2nd batch and he doesn't have any freezes or dead locks...but on my Nexus 4 8gb that I bought on December or January I experience those dead locks and freezes quite often.

Sorry again, im off.
[Nexus 4 Original Android Development] cocchiararo:
I was thinking about this issue in some kind of "parallel" to computers and SSD.

Its not acurate, since TRIM was introduced as a fix for the micro stuters (nor more than 2 secs as i remember) that appeared on computers using SSDs after the drive had been used for a while.

I do not have any freezes on my 16gb nexus 4 on AOSPA 3.94 JSS.

Android 4.3 instroduced the scheduled use of TRIM for improving storage performance (something that made android devices slower over time, specially if you filled the storage).

I kept my nexus 4 with more than 4 gb of its storage free, always.

I also ran FSTRIM myself a couple times each month.

How much free storage do you freeze aflicted people have ? did you ever run fstrim before 4.3 ? (apps like lagfix (fstrim) do this).
[Nexus 4 Original Android Development] dancom96:
Freezes occur only on JSS. They are gone on JWR, so TRIM is unrelated.

My rev11 (batch 2) phone experiences dead locks, it is a software issue that JSS introduced.
[Nexus 4 Original Android Development] cocchiararo:
Trim, storage related... no one knows why it happens, and some people don't have it on JSS either, i don't know why you are so fast to disregard an idea like that :P

(unless you read each commit from JWR to JSS and know nothing related to storage changed, of course)
[Nexus 4 Original Android Development] justthefacts:
I had Maps (7.0.2) on while driving then after a while I noticed that my screen is on so I pressed power button to turn the screen off and there was no response. Then I realized that all functions of the phone have frozen.

So I long pressed the power button to turn the phone off. The screen went off (I don't think the phone powered off though).

Now I get no response from the phone. I can not go into bootloader. It seems like the phone has bricked.

The only sign of life I can see is When I do volume down + Power with the phone connected to power, I get a red blinking notification light which blinks for 11 times then goes off.

Is this phone bricked?
[Nexus 4 Original Android Development] spaceman860:
Your problem has nothing to do with this search for red light of death fix if you can't fix it you going to have to RMA it to Google.

Sent via BLACKED OUT LTE N4

---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------

I have noticed that after flashing banks Google latinIME addon zip I haven't gotten any locks.

Sent via BLACKED OUT LTE N4
[Nexus 4 Original Android Development] justthefacts:
The reason I posted on this thread is because I did not flash anything to brick my phone. I was using 4.3 for a few days and all of the sudden this happened.
[Nexus 4 Original Android Development] mangomonkey00:
i'm not a dev

i got a freeze or dead lock while watching a video but the thing is audio was working flawless inputs were working just the video was stuck so maybe it has something to do with the graphic department gui or something i dont know it properly just thought it would be helpful if its not surely can delete this to keep the thread clean
[Nexus 4 Original Android Development] Martin_Ro:
Hm, seems like it might be one of the graphical patches. Maybe there is a concurrency lock between input (touch) and graphical output ?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] 1ceb0x:
Sorry if this sounds disrespectful. I asure you it isn't cause i love what you do with android and I am more than happy that i "met" you in android dev world.

You say 4.3 was a thought merge... Maybe it was, but slim team stated that they merged the latest jss into their sources without any hustle cause their code is pretty much stripped and optimized. They also had working led changes from the first build of 4.3 and i know PA had them borked (cm led configurations) - i think they have their own code for leds but i might be wrong.
[Nexus 4 Original Android Development] Martin_Ro:
It sounds disrespectfull ;)

The difference is that the pa thinks like per APP dpi, halo etc. Goes way More into the deep of the system then that of Slims or CM's changes and additions does (except maybe privacy guard).

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] 1ceb0x:
Yeah, you are right. As many of us said, the only big changes in jss are those gpu commits. To test every commit would take too much. Maybe if someone reverts the gpu commits out of jss and do a build, then we will narrow down a little bit the problem if the deadlocks are gone after that.
[Nexus 4 Original Android Development] ciprianruse88:
I am a slim user but I also like to be fair play and this^^ reply has nothing to do with the topic of this thread and can start a long and unnecessary discussion.Please don't take this the wrong way.:thumbup:

"use the search button before posting stupid questions"
[Nexus 4 Original Android Development] molesarecoming:
im not sure what you are saying. if slim is on JSS it dead locks. that *should* mean hustle for them. about code being pretty and stripped - a merge means that the OS you are basing on and which you changed massively starts to shift and clash. 4.3 was the biggest "minor" update i have ever seen. these are thousands and thousands of commits. no rom goes through that without pain. especially if you have taken foreign features. the safest bet is to start from scratch, which we usually do, but googles keynote made it seem like 4.3 was very small.
[Nexus 4 Original Android Development] molesarecoming:
i looked there, but nothing i did seemed to work. now pa is essentially JWR with JSS stuff left untouched (wifi for instance). and the issue is finally gone.
[Nexus 4 Original Android Development] Raza Qadri:
The previous build in which you only added AOSP own fix of problem i was having freezes with dirty flash on it.

But after a clean wipe I didn't had any deadlock
[Nexus 4 Original Android Development] richteralan:
I have to say that I flashed Banks gapps and haven't experienced any lock ups yet.
[Nexus 4 Original Android Development] molesarecoming:
its not a magic pill, these are just google apps. :laugh:

guys, i close it down now. thanks to everyone who participated. (-:
[JAM, MDA Compact, S100 General] ID64:
:D

My JAM served me perfectly for a almost a year and now it's time to move on. Just sold it and ordered ETEN M500. I've got a bit tired of iMATE's position in OS upgrades, first with my XDA2 not having 2003 SE and now JAM with no 2005. Also, cripled BT, no voice dialing possibility also was a big factor for me. ETEN is using MS BT stack and does have this feature. Let's see how it performs in person. :) I am willing to help you guys with getting BT stack from ETEN working on JAM. Let me know if you need anything.

BTW, moderators, is that possible to create another forum here dedicated to ETEN? :D
[JAM, MDA Compact, S100 General] saldous:
Why order the M500 now and not wait a few months for the M600? Please post your findings on the M500 though as I'd love to hear how good / bad it is.
[JAM, MDA Compact, S100 General] ID64:
Because in few months my JAM will be older few months :) and I wouldn't be able to sell it for a good price. M600 doesn't impress me much over M500 - same memory size, same CPU, same look ( I am not big fan of black color either). Only WiFi. But I don't care about it much. If I really need one I have WiFi SD card ( which I maybe used once in 6 month). Price for m500 is good now and Windows 2005 upgrade is officially anonced for it.

My unit should be here on Tuesday. I'll let you know how it goes.
[JAM, MDA Compact, S100 General] HBK:
I'd love to yell at you for deserting HTC, but I am afraid you are doing the right thing. Darned... :(
[JAM, MDA Compact, S100 General] Paragon:
Since you don't use WiFi, I think you made a very good move.

Dave
[JAM, MDA Compact, S100 General] BeyondtheTech:
You can always get a really short Sceptre 802.11b Wi-Fi card from MadMonkeyBoy (http://www.dweiniger.com).
[JAM, MDA Compact, S100 General] Calvin337:
ID64... so how's the Eten coming along?
[JAM, MDA Compact, S100 General] esackbauer:
As I read on some reviews, Windows Mobile 5 is not the leap we are all waiting for. Or to be more specific: The leap I am waiting for.

I am happy with my Magician and I have not seen features that would make me switch to WM5 or another device with WM5.

The main thing for me is stability first, features second.

I don't want to be a beta tester for WM5, being an early adopter, life is hard enough ;-)

Regards

Mundl
[JAM, MDA Compact, S100 General] ID64:
Not here yet :? Tomorrow :D
[JAM, MDA Compact, S100 General] jaykumarr:
m500??????

m500?

what make is it?

can someone post a link or tell me who make's them.

thanks in advance.
[JAM, MDA Compact, S100 General] kta:
jaykummar, the make is E-TEN. If you do a search in google for E-TEN M500 you'll get lots of info.
[JAM, MDA Compact, S100 General] Calvin337:
Alas, I think we may be asking too much to open an "Eten" thread in an XDA forum... :oops:

I'll try other PDA forums. 8)
[HTC One S] jweezy56:
I run CM 10.1 Nightly ville and I was having issues connecting to T-mobile HSPA+ so I flashed Tecardo's Sense v6 Radio and now I can connect to the network but I can't turn on wifi. I initially flashed TMUS 1.13 with wifi fix and build.prob.

Things I've tried:

Rerunning Sense v6 with TMUS 1.11t without wifi fix and build.prob

Restoring a NAND backup

Flashing Boot.img

Help a noob out plox?

-Jweezy56
[HTC One S] khan.orak:
Did a reboot help?

Also, try it with TWRP 2.3.3.0.
[HTC One S] jweezy56:
I tried rebooting and now its in a reboot loop. uh oh.

I've been using TWRP v2.6.0.0
[HTC One S] khan.orak:
Use TWRP 2.3.3.0, magical version
[HTC One S] jweezy56:
I've installed TWRP v2.3.3.0 via their website, re-ran sense v6, installed TMUS 1.13, wi-fi fix off, build.prop off. Flashed boot.img.

The phone still reboots every 5 minutes, wifi still not working, however mobile network still works.
[HTC One S] jweezy56:
I did a clean wipe and install and restored the NAND backup and it seems to be fine. Fingers crossed
[HTC One X] miHah:
HELLO!

As you probably already read on XDA News, HTC One X+ is getting 4.2.2 via OTA for specific CID.

That means there is a great possibility we get first costum ROMs with Sense 5 for our One X too? :)

Read the news HERE.

What do you think about it?

HAVE FUN!
[HTC One X] exocetdj:
This should probably be in the current update thread buddy :)
[HTC One X] miHah:
You are right, I was impatient actualy ;)

Can a MOD please delete this thread
[HTC One X] Stephen:
Thread closed.

Please check for existing sense 5 threads before posting new ones. It is against forum rules to duplicate threads.
[Galaxy S III Mini Themes and Apps] kicker63:
Seen this thread for anyone who wants faster internet and wifi. For Upto Android 4.2. NOT MY WORK use at your own risk.

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