yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] r4v3rr:
It's not planned unfortunately. Right now I'm struggling with a few bugs. Notably Video playback seems to have broken for no apparent reason. when this gets to a point that I am happy with it's overall stability, then i might see if i can add dual SIM.
[Moto G Android Development] andogeek10:
This problem was there in CM also. It was fixed a while back when dhacker made a few commits regarding the kernel and updated the adreno blobs.
[Moto G Android Development] r4v3rr:
yer...i'm using the latest source. there is a good chance i've just missed someting stupid... i got a few hours now to have a look. fingers crossed

Edit: Found it! ...I think. Hopefully a build up before i have to go to work later.

Edit 2: having to make clobber :S
[Moto G Android Development] r4v3rr:
New build up, based on very recently merged 4.4.3 so expect bugs. only bug i'm seeing is boot animation not working. otherwise fine.

Enjoy
[Moto G Android Development] Bundizle:
used the rom for about a day nice work dev! I like the aokp customizations alot. and about the rom its pretty damn smooth..also battery life is ok. i got little fc's in some settings area but generally is usable as a daily driver,thanks for ur amazing work ^^^
[Moto G Android Development] r4v3rr:
Hey dude,

Thanks for the kind words. Can you tell me what is force closing for you please?
[Moto G Android Development] Bundizle:
when u go to settings>mobile data>carrier settings. also system ui restarts itself whrn ur changing the tile styles. n btw where can i get the crt animation off? thanks again.
[Moto G Android Development] r4v3rr:
I thinks it's normal for the UI to restart when you apply changes to it in some places. The crt off animation is set by default. If you meant 'turn the animation off' then you can't do that from the settings in aokp at the moment. This ROM is straight aokp so it is at the mercy of the changes the aokp team have made. If you could alter that animation In previous versions they may have not included that functionality in this version.
[Moto G Android Development] Bundizle:
okay mate keep up the good work man!
[Moto G Android Development] Bundizle:
btw at times when u open applications they fc,it happened to opera min,whatsapp and zombie highway..
[Moto G Android Development] scdsone:
working great on a o2 xt1032 thanks
[Moto G Android Development] outlawmodzz:
confirmed working on xt1034

Security fc is only problem I ran into. I need to be able to side load apps. Otherwise great job.
[Moto G Android Development] r4v3rr:
Can you grab a log by any chance? No fc here. I am on a newer build but no changes related to your problem.
[Moto G Android Development] baruch6132:
Google speech to text is constantly crashing.
[8125, K-JAM, P4300, MDA Vario General] Jerry-S:
Ok folks, many of you will probably now know that TomTom Navigator 6 is available.

Apart from features added, they have removed the scren orientation option in the preferences.

A rough and ready solution is the magnet near the camera button trick.

What would be slick, is if we could adapt the TT today plugin to do the following.

Tap TT today > This then sets rotation > then runs tomtom

The wizard has this in the settings so can we control it from a command line in the shortcut of the today plugin???

Come on boffins, there must be a way?
[8125, K-JAM, P4300, MDA Vario General] vijay555:
Couldn't you use mortscript?

V
[8125, K-JAM, P4300, MDA Vario General] Jerry-S:
To be perfectly honest my friend, I dont have the first idea of where to start LOL

I was throwing the idea open to others in the hope that someone could explain how to do it.

Whats mortscript?? :lol:
[8125, K-JAM, P4300, MDA Vario General] eddieitman:
why not use ae button plus to rotate the screen i installed this and can confirm that it works perfect i used the voice record single press and just press it and rotate the screen http://ae.inc.ru/aebplus.php
[8125, K-JAM, P4300, MDA Vario General] Jerry-S:
I installed AE to give it a try and couldnt believe all that it can do.

I must admit its good, but i'm lazy, I have to press my voice button 3 times to get it how I want it!! :lol: :lol:

Now if only AE had a "rotate clockwise" or "rotate anti-clockwise", :lol: :lol:

I'm still going to look at installing a magnet, so it rotates as i put the phone on the holder.

I think the numbers are easier to dial in landscape mode.
[AT&T, Rogers HTC One X, Telstra One XL] USFguy:
I'm just planning on the new battery I've ordered not fixing the problem so it's got my mind wandering....is the internal SD something that can be pulled and put into some sort of adapter or reader to allow saving pictures and files? I'd love to save my texts but can't expect miracles. So back to point is such a thing even possible?
[AT&T, Rogers HTC One X, Telstra One XL] marknoll:
http://xdaforums.com/showthread.php?t=1631426

mark

---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------

Not saying impossible, but very illogical to mess with SD. Its fully integrated

mark
[AT&T, Rogers HTC One X, Telstra One XL] tjhooker73:
Its a NAND chip so If you get a way to dump it (Teensy dev board, Progskeet, Some othe Nand/Nor Dumper) You should be able to solder on a new NAND chip with bigger memory if you can rewrite everything back on. but you might have to rewrite a new ROM for that memory chip. :confused:
[Nexus 7 Q&A, Help & Troubleshooting] dafater:
So I was being a stupid ass and disconnected the LCD cable from the motherboard before turn off the system. Now the screen doesn't turn on.

Here's what I know for sure:

1. The system turns on, I can hear the processor working.

2. Before I completely lost the ability to have it show anything on screen, I tested two different screens and they both displayed something, albeit in weird colors (showed the correct color if I kinda yanked on the cable), so the screen is not the issue.

Here's my question, where do you guys think the problem lies? The cable? Or the connection socket on the motherboard?

Any answer is greatly appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
If you are able to test multiple screens and ribbons with no effect then I would say your problem is the motherboard connection

Sent from my Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] dafater:
I haven't test it with another cable, it's in the mail though. I really hope it's just the cable, cause I just got the replacement screen
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
It sounds like it will be the ribbon then they are very fragile it would be unusual to damage the motherboard connection
[Nexus 7 Q&A, Help & Troubleshooting] dafater:
the cable just arrived. I am very relieved to say that my stupidity only damaged the cable.
[Verizon Samsung Galaxy S 4] Nwwolf1:
I've tried every ROM, different kernels, everything but I still get screen of death on every 4.4 ROM I try no matter what. I know WiFi is causing it cause it only happens on WiFi but no matter what I do my screen locks up and I have to battery pull almost every single time the screen goes off. Does anyone have any info? Please I'm desperate and so badly want to run a kitkat ROM.
[Verizon Samsung Galaxy S 4] thesoldier:
I'm still living with the issue after trying a billion different things. Pretty much can't use WiFi.. Ever
[Verizon Samsung Galaxy S 4] jmgib:
Using WiFi and have never experienced this issue. I'm not on MDK so am using Surge's rooted odexed NC5. Issue may be the roms or kernels you are using.
[Verizon Samsung Galaxy S 4] Mistertac:
I'm really surprised someone in that logcat thread didn't help you with this
[Verizon Samsung Galaxy S 4] joshm.1219:
What are your methods for flashing a 4.4 rom/kernel? This is a weird issue
[Verizon Samsung Galaxy S 4] Nwwolf1:
So these are my exact methods in order:

1. Download ROM and Gapps

2. Boot into Recovery

3. Complete wipe of phone

4. Install ROM

5. Wipe Cache/Dalvik

6. Install Gapps

7. Wipe Cache/Dalvik once more

8. Reboot
[Verizon Samsung Galaxy S 4] joshm.1219:
And you're already on the correct kernel before this?
[Verizon Samsung Galaxy S 4] Nwwolf1:
I've just been staying on CM10.2 the entire time. I tried running a couple KitKat ROMs lately to see if maybe the issues were fixed like the GPE ROM and SlimKat (which I would really like by the way if I didn't have this issue haha) but still does it no matter what.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Yeah, and I've also tried seperate Kernels as well. Curious though, what is the correct kernel? Wouldn't it be whatever the ROM boots with?
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah i know.. May go quote my post to see if anyone new could take a look at it.

We've tried countless ROM/kernel combinations both AOSP and TW.

---------- Post added at 11:36 AM ---------- Previous post was at 11:35 AM ----------

Do you have the 16gb or 32gb version of the phone?
[Verizon Samsung Galaxy S 4] Nwwolf1:
16gb
[Verizon Samsung Galaxy S 4] thesoldier:
Damn I've got the 32gb. I literally can't find any similarities between what we're doing that would cause the issue.
[Verizon Samsung Galaxy S 4] Nwwolf1:
I know, I just don't get it. Like I know a decent amount about tech and android, but I can't figure out where the issue is. And of course on XDA there are sooo many more people who know so much more and they can't figure it out either. I can't believe it just hasn't been fixed yet. So do you really just stay on a 4.4 ROM and not use WiFi?
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah I usually have LTE everywhere (my work is really spotty though) so I don't exactly need WiFi, but it would be a lot more convenient and better for my battery. I got two extra batteries I just swap out to deal with that...
[Verizon Samsung Galaxy S 4] Nwwolf1:
I'm guessing you have unlimited data?
[Verizon Samsung Galaxy S 4] thesoldier:
Oh yeah that too haha.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Haha, I mean I share 10gb's with my family, which usually gives me about 5gb's since my brother is the only one who uses data. But still I want WiFi haha.
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah I would NEED WiFi if I had even 10gbs a month, I'm already up to 7gbs halfway thru the cycle.
[Verizon Samsung Galaxy S 4] Nwwolf1:
So no one has anything at all they think we could try that we haven't already?
[Verizon Samsung Galaxy S 4] mochamoo:
I would suggest (almost) stock kitkat if you haven't tried it yet:

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

If you can't get this to work then is it possible your device is faulty? Also, does it only happen with wifi at your home or elsewhere too?
[Verizon Samsung Galaxy S 4] thesoldier:
That's what I'm on right now, does it completely stock (except for the bootloader obviously). It happens to me on any WiFi network, not just my home network.

And if it was hardware related, what are the chances it happened to two of us ONLY when running 4.4?
[Verizon Samsung Galaxy S 4] mochamoo:
Don't shoot the messenger. Just trying to help man. Don't know what else to tell you.
[Verizon Samsung Galaxy S 4] Surge1223:
I really dont even know what problem exactly is but from what I can gather it seems that WiFi causes the device to freeze up? If it was me, id build a stock optimized loki NC5 kernel, then delete all the files in /system/lib/modules of the rom and flash/adb push + set perms on stock NC5 kernel modules then before I started WiFi id open terminal and run a kmsg log + dmesg |grep lk and have them save the output. Also last_kmsg might contain useful info. You could try manually loading the wifi module with insmod and see what log output says.

just throwing out some ideas
[Verizon Samsung Galaxy S 4] Nwwolf1:
It happens on any Wifi. Maybe I'll try that rom, I just hate TW but I might as well see if it has the same problem.
[Verizon Samsung Galaxy S 4] thesoldier:
Lol sorry. Didnt mean to come off a douche just pretty frustrated with the problem.

Basically, being on WiFi causes the device to BSOD at any given time, but only on KitKat.

If you could tell me how to go about doing this I'd be MORE than happy to lol. I've used adb before so I'm a little familiar with it. I've also grabbed last_kmsg, logcat, and dmesg from the last time it crashed thinking one could be of some help.

Edit: actually, the only thing I'd need help with is building a stock NC5 kernel... Deleting the modules and setting permissions on new ones I am familiar with, along with getting logs.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Yeah I don't know any of these things ha so if you do it and it works let me know.
[Verizon Samsung Galaxy S 4] thesoldier:
Haha no problem. I'll try anything at this point.

Surge - here's a better description of what happens that I posted in another thread.
[Verizon Samsung Galaxy S 4] Nwwolf1:
I've never pulled a logcat or anything so here's hoping someone can read this stuff and help us out.
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah, I think Surge is our biggest help at this point. I'm gonna see if there's a stock 4.4 kernel and try what he said.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Let me know what you come up with, fingers crossed.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Any luck, man?
[Verizon Samsung Galaxy S 4] thesoldier:
Nope I have been pretty busy the past week. I may have some time to mess with it this weekend though
[Verizon Samsung Galaxy S 4] Nwwolf1:
I tried Hyperdrive a couple days ago. It never SOD'd for me but I HATE TouchWiz so much I just couldn't stay with it. I'm now on CM11. Its still doing it but not nearly as often as it used to. It literally used to do it every time I'd turn the s screen off. Now its only doing it 3 or 4 times a day. I'm just going to live with it till I get a new phone.
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah I hate tw too. Only reason I'm still on it is because when it freezes it will auto reboot on tw, but requires a battery pull on aosp
[Verizon Samsung Galaxy S 4] thesoldier:
Still looking for solutions here, but what recovery are you using? Can't remember if I asked you.
[Verizon Samsung Galaxy S 4] Nwwolf1:
I'm using TWRP.
[Verizon Samsung Galaxy S 4] thesoldier:
Try this for me ASAP. Try switching to philz touch recovery. Goto the link and download it, then flash it in TWRP. Reboot recovery and you'll have philz.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/philz_touch_6.44.8-jflte.zip
[Verizon Samsung Galaxy S 4] Nwwolf1:
And then flash a kitkat ROM?
[Verizon Samsung Galaxy S 4] thesoldier:
Only if you want to. Just switching recoveries is good and then rebooting to your current ROM. Reason I ask you to try is because its been over 24 hours since I switched from TWRP and the bug hasn't happened YET

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

Keeping my fingers crossed lol
[Verizon Samsung Galaxy S 4] Nwwolf1:
I'll definitely give it a shot.is that recovery easy to use? I'm very cautious about recoveries cause I don't want to screw anything up haha
[Verizon Samsung Galaxy S 4] thesoldier:
I actually haven't flashed anything yet but I did go digging thru menus. Looks simple enough, if you've ever used ClockworkMod in the past it's just like that except touch.
[Verizon Samsung Galaxy S 4] Nwwolf1:
So you were already running kitkat and flashed the recovery? And it just hasn't SOD'd yet? (Fingers Crossed)
[Verizon Samsung Galaxy S 4] thesoldier:
I've been on a stock 4.4 TW ROM for like the past month..with the bug occurring all the time. Flashed just philZ recovery the other day and it hasn't happened yet. Noooo idea how a custom recovery would affect WiFi but who knows. Really really hoping I found the problem lol
[Verizon Samsung Galaxy S 4] Nwwolf1:
Here's hoping! I'll give you an update by tomorrow night. Give it some time to run its course.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Well unfortunately it SOD'd only minutes after using new recovery and flashing cm11. Now my problem is my back of cm10 is in TWRP so I can't flash it through Philz and I can't figure out for the life of me how to flash TWRP again since its not a zip. Could you kind of give me a step by step of how to go back to TWRP?
[Verizon Samsung Galaxy S 4] thesoldier:
Ah crap that blows. Still hasn't happened to me yet...

To go back to TWRP all you need to do is download the app called Goomanager. Under options click "install open recovery script." It will install it right there.
[Verizon Samsung Galaxy S 4] Mistertac:
Grab Flashify from Play Store. Works better than Goo most the time. Very easy to use also you have nothing to worry about.

Flashify is very actively being developed so it's update a lot... Just a better program if you ask me.
[Verizon Samsung Galaxy S 4] Nwwolf1:
I tried downloading through Goo. It downloads but when I reboot to recovery it sticks to Philz. I tried downloading the .img from their site and going through terminal.emulator but it says the command is wrong.
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah I noticed goo wasn't really being updated much, Flashify probably is better.

Have you tried Flashify?
[Verizon Samsung Galaxy S 4] Mistertac:
Flashify should work. SuperSu is all updated and Flashify has SuperUser rights?
[Verizon Samsung Galaxy S 4] Nwwolf1:
Flashify isn't working either. Any time I go to download it just says "Something went wrong downloading. Please try again in a moment"
[Verizon Samsung Galaxy S 4] Mistertac:
Well you could try KToonsez's TWRP

https://www.dropbox.com/s/hht2z87mh87d8is/TWRP-KT.ALL-IN-1.zip

It's the version prior to TWRPs latest release. But if your just trying to get back to TWRP for the time being that should work for you. It's an All in One Ext4/F2FS version. Everything would be the same though... You'd have to manually go on and toggle F2FS so don't worry about that too much unless you want to convert over.

See if u can flash that in Philz.

---------- Post added at 09:36 AM ---------- Previous post was at 09:30 AM ----------

The latest just downloaded fine for me using Flashify
[Verizon Samsung Galaxy S 4] Nwwolf1:
Awesome thank you. That's what I was looking for. It worked. And it's stil an updated version to the one I had haha. Unfortunately still no freaking fix for the SOD issue! I can't believe we can't figure this out...
[Verizon Samsung Galaxy S 4] Mistertac:
Yea well that's good!! Back to twrp worked out at least lol

I don't know what to say about your problem with sod though. There's some heavy hitters on XDA that I'd think could figure that out from a Logcat but that hasn't even helped you.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Yeah I know, it's just so frustrating. I want to run KitKat so badly but now I'm just going to have to wait till I get a new phone. I could get one now but I'm waiting for the next Moto X.
[Verizon Samsung Galaxy S 4] mochamoo:
My best buddy is running a completely stock S4. No root. Locked bootloader. NC5. He gets SODs regularly since kitkat. So there is something inherent in the OS causing the issue. Not sure if it is fixable until we get another update. At the moment I am back to a 4.3 TW rom and it is running solid as a rock. Might be worth checking out Verizon's forums to see if there's any info there on the matter since it is happening on stock S4s too.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Not a bad idea. I've just been running CM10.2, so I'm on AOSP 4.3. All I know is that Wifi is what's causing it. So I've pinpointed what's causing the issue. I just have no idea how to fix it at all.
[Verizon Samsung Galaxy S 4] 318sugarhill:
I thought this was a ROM issue. I've used Echo, Baja, and Stock rooted 4.4.2 and I've had this issue on the first two. Just went back to 4.4.2 stock rom. Haven't had it yet....but I'm sure it's coming. Basically I'll pull the phone out and the screen won't come on. I'll press the home button and/or power and sometimes the phone will wake up, but usually when it happens, it will just reboot itself. Very annoying. I don't have to do a battery pull. I'm MDK, no safestrap.
[Verizon Samsung Galaxy S 4] decaturbob:
I been running kitkat with bajarom and zero sod s and my wife's s4 is stock with kitkat OTA and no sod there either....not a kitkat issue. ..per say

sent by bajarom v2.2 kitkat
[Verizon Samsung Galaxy S 4] thesoldier:
I've had it on every single ROM on KitKat. AOSP and TW. The only difference is on TW it will auto reboot after the SOD, but not on AOSP. Since I flashed philz recovery I still haven't had one, though I've got no idea how that would affect anything.
[Verizon Samsung Galaxy S 4] thesoldier:
Well it took 5 days... But it finally happened again. Still clueless as to what causes it.
[Verizon Samsung Galaxy S 4] thesoldier:
Is the issue still happening to you too?

I used some Bluetooth headphones earlier and left BT on with WiFi and haven't had the issue in over a day. Anyone else wanna try it?
[Verizon Samsung Galaxy S 4] 318sugarhill:
I've been using the Echo Rom and I can't say it doesn't happen anymore....but it's very infrequent. Used to be once a day minimum. Now its maybe 1 or 2 times a week. And it's weird....I have no idea what triggers it.
[Verizon Samsung Galaxy S 4] Bijiont:
Same here but with CM11 (4.4.4) running nightly builds and never saw any issues which were KK related. I am also on MDK baseband which may or may not have something to do with it.
[Verizon Samsung Galaxy S 4] decaturbob:
I'm safestrap and never had a SOD on kitkat based roms like echo, hyperdrive or baja
[Verizon Samsung Galaxy S 4] Mistertac:
I believe these guys have even had this issue on stock MDK.

Seems maybe like it could be some driver or something idk.

I'm still amazed that with the logcats they've made no one seems to be able to pin point it
[Verizon Samsung Galaxy S 4] thesoldier:
I don't recall ever having the issue pre-KitKat, though it is possible. I think my next step will be to Odin back to MDK and then flash 4.4 and restore nothing. If it persists, I can only guess it's a rare hardware issue.
[Verizon Samsung Galaxy S 4] decaturbob:
good to place start with clean slate
[Verizon Samsung Galaxy S 4] Mistertac:
My bad could have sworn you or the other guy had the problem no matter what...
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah I think I did that before but I restored my Google account.. Wanna try it without even that.
[Verizon Samsung Galaxy S 4] Nwwolf1:
Has anyone found a fix for this yet?
[Verizon Samsung Galaxy S 4] thesoldier:
I wish. Maybe "L" will fix it lol. Jk I'm not waiting that long.

If I can free some time this weekend I can do what [MENTION=4939386]Surge1223[/MENTION] suggested awhile back, just need some guidance on how to build a kernel and a couple other things. Would really love to get to the bottom of this.
[Verizon Samsung Galaxy S 4] thesoldier:
So I worked the last few weeks straight and had no time to try anything. Odined back to mdk and flashed a 4.4 gpe ROM while restoring nothing but my google account...was fine for almost the whole day until it happened again.

Just odined to mdk again, this time not flashing the pre release kernel or using motochopper, but using towelroot instead. Maybe us select few used a bad combination of downloads or one of those tools...who knows. This is getting quite annoying lol if there was a phone worth "upgrading" to, I would've done it a long time ago.
[Microsoft Surface] code72:
I've just seen Surface Pro 3 event and... i love it, i want it... i must sell my Pro 1 and buy it.

What do you think about SP3 guys?

And its 3:2 screen instead of 16:9?
[Microsoft Surface] mcosmin222:
I like the 16:9 screen ratio better.

The surface pro 2 is still a powerful product regardless, but imo the thing holding them back is the policy of selling the keyboard separately.
[Microsoft Surface] julz:
im keen to find out if the new bluetooth enabled surface pro 3 pen will work with the surface pro 2. Im definitely considering selling off my surface pro 2 to upgrade to the 3.
[Microsoft Surface] SixSixSevenSeven:
New pen is NTrig not wacom so will not function on a pro 2.