yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] sgibney:
Thank you Deviant

Thank you for the information. I found another Rom from ktmdave7 [ROM] JB 4.1.1 STOCK Slim 01-18-2013 (3rd Release) which I decided to try. I concur with your assessment of the device with stock software. I like this ROM, but I have no GPS now. I'd rather have no GPS than no camera, but damn if it hasn't had me looking around for a fix. At this point, what I found was says it is a stock t-mobile sgh-t999 rom T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar that I will try to go back to stock and see if the GPS works. This is about the only solution I've seen replicated to some success. I do not know why I'm letting the GPS crap bother me... I will keep you folks informed.

Thank you again for taking the time to go over the steps you added. I will do what you suggest if I still have problems. I sure would like to use some more ROMs and these are so much more functional than stock Samsung/T-Mobile.
[T-Mobile, Samsung Galaxy SIII] sgibney:
You are not the only one

I have the same exact firmware zhfj02 on my g3 and it was just purchased 3 weeks ago. No working camera on any non stock based roms. I had no GPS with all non stock roms until I went to 4.2.1 but then again no camera. Going back to stock before would never get the GPS working again. I just went back to stock again to check the cam firmware and suddenly the gps is working again. Going to try ktmdave7's rom again as it is basically stock slimmed.

So, you are not the only one. I have a shg-t999 from t-mobile and experience the same problem. I was able to take one pic using Deviant's method, but then right back to "can't connect to camera" or whatever the message was. I would have to reboot, then I could take one picture. This prompted back to stock, then discovered gps working again, now going back to ktmdave7's rom.
[T-Mobile, Samsung Galaxy SIII] civicvx94:
I've been experiencing this error for the past month.. normally it would fix itself after a reboot/clear cache, but not this time. I've messed with it countless times, wiped it, flashed different roms, nothing worked... So just now I ODIN'd back to stock...and it STILL DOESN'T WORK.. Is there any reason why using ODIN to return to stock from an AOSP rom, wouldn't fix this problem?

I attempted to go thru the steps here.. http://xdaforums.com/showthread.php?t=2113526 but for some reason I'm unable to pull up that camera firmware menu though, the screen goes black then closes and "factory test" FC's every damn time.....

So at this point, I've been searching around and I can't get any of the Factory Test USSD codes to work, most fail or just FC. I can't check my firmware version and even if I knew what it was, I still wouldn't be able to flash an updated fw. What options do I have left? Is it possible to manually flash the drivers..?

I've tried both the stock JB rom and the prerooted stock JB rom and neither will pull up the menu...
[T-Mobile, Samsung Galaxy SIII] Deviant Ollam:
i am not familiar with whether ODIN return to stock flashing would fail to flash, say, the boot partition (and thus if you have some other kernel somehow, say) but overall that is genuinely weird.

some questions...

1. what is the exact way in which this error manifests itself? when you launch the camera app does it give you "cannot connect to camera" error or something else?

2. does EITHER camera work for you? for example, using Skype with the camera facing the user... can that camera operate properly?

overall, this may just be odd and academic. if you are running stock Galaxy S III and it looks factory-normal, etc... you could likely just go into the store where you purchased this and attempt a warranty exchange. explain that the camera worked fine until the other day, and now it's erroring.

tell them that trouble shooting forums (or even reps on the phone) informed you that this is a sign of a faulty camera lens or something else you choose to make up. let them proceed with the warranty swap.
[T-Mobile, Samsung Galaxy SIII] civicvx94:
Yes, if I'm on an AOSP rom and open the camera it says "cannot connect to camera" and closes.. when I'm on a stock rom it says "camera failed" and closes.

The FFC does work, but i can't access it. The only way I was able to find this out was by running a USSD code to get to the hardware test menu. The rear camera fails and closes, but the front works fine. However, in apps like Instagram for example, when I attempt to use it, it defaults to the rear camera and closes before I can switch to the FFC.

All issues are consistant no matter the rom or the firmware.. I've flashed 3 roms, 2 different stock firmwares and 1 stock rooted one today alone.. Same on each.

I'm going to try to get it replaced I guess.. It just seems crazy to me that its stuck like this.
[T-Mobile, Samsung Galaxy SIII] Deviant Ollam:
have you tried adding the .bin files that we have added to make it work?

I am running CM10 and it worked when i dropped in the SlimISP_ZH.bin file.
[T-Mobile, Samsung Galaxy SIII] civicvx94:
Yeah... I extracted those all of those files and pasted them all in /data/ and set permissions to 777.. but still nothing.
[T-Mobile, Samsung Galaxy SIII] civicvx94:
Any other ideas or should I try to get a warranty replacement?
[Samsung Galaxy Nexus] jeff5347:
Hey guys

Figured I'd post this in qa. Was wondering if anyone new of some good books to learn development. Such as stuff for theming and apps. Downloads so far

App inventor for android: build your own apps

And

Xda developers android hackers toolkit the complete guide to rooting Rom and theming

I'm pretty versed in rooting and all that but want to try to get into building. Any good recommendations to read
[Nexus 4 Q&A, Help & Troubleshooting] austinlblanton:
No matter what I do my windows xp machine will not autoplay my nexus 4 so I cannot drag and drop files. I'm pretty sure I have the right drivers installed. I found them in some other thread. I know it's not the phone cause whenever I plug it into my roommates windows 7 computer it opens right up. Please help!
[Nexus 4 Q&A, Help & Troubleshooting] meangreenie:
Try disabling usb-debugging if you have it on.
[Nexus 4 Q&A, Help & Troubleshooting] austinlblanton:
Tried that, nothing happened. In device manager it shows up as Android ADB Interface but my computer will not autoplay it for the life of me.
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
It should be showing up as an MTP device and installing an MTP driver if you want to be able to open up a file window etc. On XP this often doesn't work till you turn off USB debugging on the phone.

It sounds like you might still not have the correct MTP driver installed.
[Nexus 4 Q&A, Help & Troubleshooting] Greefus:
Upgrade to newer windows media player to get MTP on XP.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] ctcx:
Hello all.

My device is S5830L (but is S5830 for CyanogenMod), and using CyanogenMod 7.2.0 stable, no custom kernel.

I have unsuccessfully searched around for a way to see what wireless chipset (Broadcom, Atheros, Realtek, etc...) my device has. Lastly someone through mail told me to use Menuconfig, but as far as I found, that's a developer tool for building kernels, and of course I don't know how to use it.

Does anyone know about a way to check my chipset?

Or could anyone help me using Menuconfig for this matter?

Thanks for your help.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] ctcx:
Any help? (excuse me)
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] ctcx:
Never mind, after a big while found it in the device tree:

https://github.com/CyanogenMod/android_device_samsung_cooper/blob/gingerbread/BoardConfig.mk

It's a sh***y Atheros ar6000, which is not even supported or even considered as a Linux driver:

http://wireless.kernel.org/en/users/Drivers

No overclock and no USB OTG (at least not without custom kernels), seriously the Ace is really the lowest worse Samsung smartphone by now. No wonder it's a legacy officially unsupported device. Well, this one must be the best I can have in a 3rd world country with monopolies where having nice gadgets is expensive and *not forgiven* (getting robbed or bullied for that).

Anyway, thank you all. At least with CM 7.2.0 it charges battery faster... And I have my vendor stock backup if I get tired of it...

Thank you.
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Hi All

Just flashed Pacman Rom onto my DHD, got it here http://xdaforums.com/showthread.php?t=1933804

Lovin the rom but the Google Navigation is no longer working.

It's just says "Searching for GPS" and never finds it.

I installed NavFree and it seems to work ok....

I do prefer the Google Nav app though

Anyone have any idea why this is??

Cheers

HB2K
[Desire HD Q&A, Help & Troubleshooting] Fallon9111:
I don't use pacman, maybe try posting in the pacman thread/searching. Did you flash a version of gapps that included google nav. Maybe you flashed the wrong gapps?

What gapps are you using?
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Use GPS Status and in the menu>tools>manage A-GPS , do a reset. Then check that GPS are fixed. If that is not working, then try using the fixes in this thread:

http://xdaforums.com/showthread.php?t=1252011
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Thanks you guys!!!!

@Fallon911 Cheers for the advice, I'm using gapps-jb-20121011-signed

@glevitan I don't see GPS Status in the settings listing or anywhere else in the menus, will try the fixes in the thread you posted, cheers mate :)

HB2K
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Sorry get GPS status from the play store....forgot to mention that...:o

[
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
lol

Will do mate :)

One Sec

HB2K
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Hey

Well I re-flashed my previous ROM, Jellytime, after a full data reset, and the problem persists.

I tried GPS Status and did a reset. No joy

Anyone have any advice??

HB2K
[Desire HD Q&A, Help & Troubleshooting] glevitan:
What radio are you running? Is it the lastest GB one?
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Em, and how do I find out what radio I'm using.. :D
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Is it the Baseband version?

Thats 12.56.60.25U_26.10.04.03_M

Sorry I'm kinda new at this :)

Cheers

HB2K
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Anybody know what radio I should be using for the gps navigation to work??
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Still havin probs gettin the Nav to work.

Would any of the suggestions here http://xdaforums.com/showthread.php?t=1266525 work?

Cheers

HB2K
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Bump. Anyone.

Really bugging me that I have no sat nav
[Desire HD Q&A, Help & Troubleshooting] heywheelie:
Not sure it will help but try turning the google location services on as well as GPS satellites.
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
Hey heywheelie

Yeah all that is activated so I really can't see why it won't work.

As for the stock radio fixing the problem.... I think might.

Never flashed radios, and only roms, so really don't know a lot about em.

Maybe someone on here would point is in the right direction :D
[Desire HD Q&A, Help & Troubleshooting] AndreiMel:
i've got the same problem... for some users gps work, for others not. i will try to flash another radio
[Desire HD Q&A, Help & Troubleshooting] Hamsterboy2000:
I've never flashed a radio.

How risky is it?

What radios should I be looking at to fix this
[Nexus 4 Android Development] thracemerin:
4.2.2 Version

Experimental WiFi Fix

Confused about all the fixes floating around? Maybe this will help: http://xdaforums.com/showpost.php?p=40432746&postcount=578

Date: April 15, 2013

Download: hsic_fix_nexus4_wlan_v6.zip

MD5: 8ba0f874efc894c8aaa2e115c5fe2438

See here: http://xdaforums.com/showpost.php?p=40340768&postcount=522

Revert Zip: wlan_revert.zip

MD5: 381013687035626bcb1cbaf609ea431

Note: Flash this if you have flashed any of the WiFi fix versions prior to switching to a different kernel.

Stable Version: (anykernel)

Date: March 04, 2013

Download (any kernel): hsic_fix_nexus4_4.2.2v1.zip

MD5: 17127c1ce03ce0489c49ed7377204a6c

Source: https://github.com/thracemerin/Mako (branch: jb-hsic-rel tag: release-v1)

4.2.1 Version (anykernel)

Date: Feb 04, 2013

Download (any kernel): https://hotfile.com/dl/192620778/4b1c43e/hsic_fix_nexus4_v2.zip.html

MD5: 22be4821f3c16087a04a8084cc0d5703

Source: https://github.com/thracemerin/lge-kernel-mako
[Nexus 4 Android Development] spncrmoo:
Fingers crossed for this, will be testing tomorrow!
[Nexus 4 Android Development] veyka:
With this test kernel I got 11min of hsic wakelock in 11h, which is very simular to what I get on harsh's kernel. (when I was trying it out last night)

I also had no data stuck issue, where as on previous attempts I was always able to reproduce the problem within a few min!

Just to be clear, these patches reduce the hsic wakelock by a lot, while preventing the issue where data would get "stuck", signal would show, but nothing would go in or out.

Edit: as well as fixing the hsic issue, these patches should also reduce power consumption while on mobile data, a general win/win.

Sods law states that the moment we truly have this under control, google will push 4.2.2 with all these fixes anyway ;)

Thanks a lot for bothering todo this!
[Nexus 4 Android Development] Bluewall:
Going to give it a try too, thanks for the work mate !

I'm wondering, does the CM team will merge these patches if all work properly ? I don't know the point of view of CM about CAF :)
[Nexus 4 Android Development] thracemerin:
Well, a bunch of the fixes got pushed initially to the CM kernel, but were reverted because of the 3G data stalls, if this works out and 4.2.2 doesn't drop soon or doesn't fix the problem I'd consider resubmitting them to Gerrit, I would want some solid evidence that this works before I go through the trouble however.
[Nexus 4 Android Development] Firefox17:
Can you please post a flashable zip?
[Nexus 4 Android Development] joaoennes:
Hi,

It seems to be working.

I have about 6h on battery, 93% left and the msm_hsic_host used 15 m, 4%. No problems with 3g so far.
[Nexus 4 Android Development] thracemerin:
I'll get on that later today.

In the mean time I had a few mins to repack it for stock, for the moment it's untested (my device is elsewhere atm), if you're brave feel free to try it, I'll post here later when I confirm it works unless someone beats me to it. Update: Confirmed Working
[Nexus 4 Android Development] thracemerin:
Any kernel version is now in post 2, I've confirmed that it works on CM, but I can't see why it wouldn't work on other ROMs. Big thanks to _motley for the zip file I used.
[Nexus 4 Android Development] Firefox17:
Indeed I can also confirm this one really works I have tested for a few hours and the results are great.

Thank you :)
[Nexus 4 Android Development] jakejm79:
What is the build date of the CM kernel, just so I can match it with the same date nightly
[Nexus 4 Android Development] thracemerin:
1/15 I believe, the anykernel one that works with CM was built on 1/16, either should work on today's nightly as there were no modifications to the ramdisk in the CM repos.
[Nexus 4 Android Development] jakejm79:
Ok thanks, I will test tonight/tomorrow with the 1/17 nightly
[Nexus 4 Android Development] spncrmoo:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

On MinCo v6 + Franco kernel r34, the zip is giving me bootloops. Tried twice, once on a fresh install.
[Nexus 4 Android Development] thracemerin:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Franco's kernel uses a non stock ramdisk which I gather from other threads is only compatible with his kernel, you will probably have to either flash the stockboot.img from here or use one of the reset kernels floating around the forums before flashing this.
[Nexus 4 Android Development] Nebucatnetzer:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

I haven't tested it fully yet but it really looks like I'm finally getting a normal deep sleep.
[Nexus 4 Android Development] poofish:
Sorry if this post is ignorant, but I just started using CyanogenMod for the first time having gotten a Nexus 4, and I'm not 100% familiar with it yet.

I've flashed your kernel and it is working great with no wakelocks, but will updating to the latest nightly flash the stock CyanogenMod kernel again? meaning I would to reflash yours? Not that it would be a problem given that I have the flashable zip, but just for future reference as to whether I need to reflash your kernel every time I update for nightlies.
[Nexus 4 Android Development] Nebucatnetzer:
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix

Yes you have to reflash everytime you flash a nightly.
[Nexus 4 Android Development] MatMaul:
Same here, seems to work great, good job !
[Nexus 4 Android Development] chrone:
quick impression on one day mild usage of n4 4.2.2 battery life from 100% to 1% (6.6%/hr) on stock kernel:

battery life 14.9 hours

screen time 2.5 hours

3G most of the time, sometimes WiFi and 2G

autosync on

msm_hsic_host 1256 wakelocks, 10% ~ 2 hours wakelock

update:

uploaded bbs log and some screenshots.
[Nexus 4 Android Development] thracemerin:
Not at the moment, it's just Google sources in v1, I will be looking at adding other stuff, I just wanted to make sure the new sources were solid before installing anything into them that may cause unforseen issues.

Yeah, the stock AOSP stock kernel and the OTA kernel should be the same other than who compiled it, since I'm using the Google toolchain as well there should be no difference. Digging around in the new sources I noticed that Google didn't push all the changes I made in my previous 4.2.1 versions, so I wanted to see if there was some other change that they made to fix the wake locks before I went ahead and added in the patches again.
[Nexus 4 Android Development] thracemerin:
Ok, New version:

Back in Post 2

I re-added some of the HSIC patches from the 4.2.1 version and this may or may not have re-introduced the 3G data drop/lock up issue, I want to see if it did or not before I continue.

I would like people to run the version from the 14th first (for a full day and post the logs I asked for before) to get a baseline on the wake lock before trying the 15th version.

If you get a data drop, lock up or any other unusual behavior on the 15th version, please let me know. Logcats, last_kmsg, etc would be helpful as well if you can.
[Nexus 4 Android Development] sotong:
Hi,

I have not been able to test V1 on wakelocks as my usage pattern the past day was for heavy gaming. However, i do notice that the wi-fi data dropouts i used to have (delayed notifications) have gone. I still noticed it using the stock 4.2.2 kernel, so i find this very odd. I will try re-flashing the stock kernel and giving it another go. I noticed this delayed notification also with other custom kernels based on 4.2.2.
[Nexus 4 Android Development] thracemerin:
So the delayed notification is gone? That's a good sign. I only ever had it intermittently on the 4.2.1 kernel, so it may just be random good luck that you don't have it anymore and it may pop up again, I don't see anywhere that Google fixed this, but it could have been hidden in something else.
[Nexus 4 Android Development] sotong:
That is correct. I just did further testing again:

1. Flash back to stock 4.2.2 kernel. Wait 5 mins. Sent gmail to my phone. Notification did not come in until i turn the screen on.

2. Flash to your V1 kernel. Wait 5 mins. Sent gmail again, and i got the notification almost immediately.

I am also puzzled as to why this is happening. But i am not complaining! Will test your V2 now. Thanks for your efforts
[Nexus 4 Android Development] thracemerin:
Interesting...as far as I know V1 should be exactly identical to stock, so I can't explain why that would be, but I guess it's a happy side effect.
[Nexus 4 Android Development] sotong:
Hi, just a quick update again. V2 seems to also have delayed notifications. Went back to V1, same test, and no delay.
[Nexus 4 Android Development] thracemerin:
I can't explain that, V1 and Stock are identical, V2 has nothing related to WiFi changed. So unless it's random coincidence that you aren't having problems with V1, I'm not sure what else it could be, I'll look into it further.

Edit: I tried hard to reproduce this on my local version with is essentially V2 and I can't, so either it's something I added in V2 and changed back in the local version (not likely) or it's something to do with your setup.
[Nexus 4 Android Development] sotong:
I agree with you, it must be my set up because it does not make sense also. Could be a random coincidence. Is there a quicker way to test this (i read about pinging etc) instead of waiting several minutes when the phone is in standby?

Edit: You are correct. Just sent a gmail to my phone (on V1) and nothing came in :( There goes my short-lived joy! Or gmail is having issues also.
[Nexus 4 Android Development] thracemerin:
I guess that they more or less confirmed in this thread: http://xdaforums.com/showthread.php?t=2072930 that Google did not fix the WiFi notification issue, so I don't think it's you, blame Google.
[Nexus 4 Android Development] thracemerin:
New build in post 2 (see there for changelog)

I added a couple more CAF patches and used the data fix that Faux123 used in his enhanced stock kernel instead of the one I used previously, I want to see what happens with this as it relates to the wakelock and data use to see how it goes, if it doesn't work I'll install my previous solution.

Happy Flashing.
[Nexus 4 Android Development] chrone:
i'm testing your v3 right now, will post the log tomorrow now after full day use.

no need to test v1 since it's the same as stock and i've posted the bbs log above, right?
[Nexus 4 Android Development] thracemerin:
Yeah v1 is the same as stock.
[Nexus 4 Android Development] floepie:
Sending yourself a gmail turns out to be a very poor test. Invariably, if I send myself an email, notification delays are very random, and this has been confirmed by others on this board. However, getting emails from 3rd parties is much more reliable for delay testing. It may have something to do with "loopback" settings on the router. In any case, if you have a router which flushes its ARP cache every couple minutes, you will get delays (up to 15 minutes) because Google hasn't updated the wifi driver to offload ARP broadcast requests. They decided battery life was more important, so they chose to drop requests entirely when the screen is off.

Fortunately, if you have a dd-wrt router, you can set a static IP address from the router to get around this issue.
[Nexus 4 Android Development] thracemerin:
True, but the WiFi issue is definitely not fixed, I tested it using the ping method. If I used a PC that hadn't previously connected to the phone while the screen was off, the pings timed out, as soon as I turned the screen on they'd work until the ARP timed out, then it would go back to time out.
[Nexus 4 Android Development] jakejm79:
Theracemerin, having upgraded to 4.2.2 (CM10.1 2/16) and using you v3 fix, my wakelock performance isn't as good (about 30 mins over 10 hours of sleep with wifi on) when compared to the older v2 (for 4.2.1 built 2/4) version I was using before. Hopefully you can add the rest of your fixes you had for the 4.2.1 kernel to the 4.2.2 kernel.