Related
The AOKP build works great except for the constant disappearing keyboard that is about to make me kick puppies. I saw the note to install the wingray google apps to avoid the disappearing keyboard that is synonymous with the recommend gapps to use, but my dumb ass forgot and installed the recommenced apps and I surely do have the constant disappearing keyboard issue. I have flashed the "gapps-jb-20130129-P75xx" zip but still have the issue. Do I have to wipe everything and start over? Does flashing the new gapps zip not overwrite the "gapps-4.2.2-jb-3.4.2013-signed" I originally installed? It seems not to, but wanted confirmation before wiping everything again.
You should wipe everything and start over. IMHO.
Full wipe and used the "gapps-jb-20130129-P75xx". Disappearing keyboard will no longer boil my blood.
For reference, never use the "gapps-4.2.2-jb-3.4.2013-signed".
Glad I stumbled onto this thread. Exactly the problem, keyboard, (well one of them anyway) I am having.
Well for me I can't find anything to fix the disappearing keyboard issue. I tried using the suggestions above. No help. After finding more and more posts in the same subject on different boards it seemed only the Wingray gapps is the one that works properly. Just tried that one and it doesn't seem to fix the issue either. Tried several of the newer nightly ROMs too.
One suggestion was to download the Go keyboard. That didn't help either.
Dang how hard can this be? I have flashed and wiped cache so many times lately. lol
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
DefQoN_BE said:
The problem why is exactly explained in nakedninja's 4.2.2 thread, you should read before you install anything
Click to expand...
Click to collapse
Unfortunately that thread content has not helped in my case. I found that thread early on and have tried to follow the directions. So either I'm missing something or not doing something correctly it appears.
Someone in another forum suggested I try the free Jellibean keyboard.
I had this issue too with AOKP 4.2.2. I have not reflashed another new gapps yet, as I found re-installing a third-party keyboard which I liked from previous use solved the problem.
Andre
Well whatever I did I finally fixed it. I ended up simply formatting the internal SD card. Poof, everything gone. Had to restore from backup default ROM. Once the stock firmware was up and running I followed the procedures again. Wiped, cleared cache multiple times and when it was all done installing there is no more keyboard issue as of now.
I loaded the 4/08/2013 nightly ROM and Wingray gapps(which I've already tried multiple times). So all is well in Tablet land again.
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
Hi, a few days ago my phone camera fault, I get a notice saying "error connecting to camera", so I did a logcat to see what happened but I honestly don't know how to read it and thus can not understand where is the reason for the problem so that's why I put this here so that any experienced user help me and tell me what is the problem... Here is the log http://pastebin.com/print.php?i=rXU9DwAc
Thanks for your time guys!
PS: the front camera and flashlight also don't work, I try flashing another rom but didn't work (CyanogenMod 10.1)
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
fffft said:
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
Click to expand...
Click to collapse
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
martin_carpio17 said:
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
Click to expand...
Click to collapse
The essence of troubleshooting is looking for patterns.. which point us towards the ultimate cause of a problem. If I had a java error, the first thing I would try is simply rebooting the phone. If it continued, I would suspect a conflict (if I had recently installed an app or changed some settings). So.. try reversing those tweaks and see if that clears that error. Less common would be corruption.. and you might test that by flashing back to the same stock ROM if it was working fine before you saw the issue.
Flashing to a different CM ROM wouldn't be a first step. It might work. But you don't gain much knowledge if it doesn't as a new ROM introduces a host of new variables as well. If the cause of the issue is unclear, you want to confront the most obvious suspects first and try to change only one variable at a time. In your place, i'd go back to the stock ROM.. confirm that the camera works properly again. Then restore your tweaks one by one watching to see when the problem recurs.
Good luck
.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?
Hi. I'm using CM12.1 with my quark (xt1254). Using a clean install method if I flash cm with a current gapps build (tried 1/29/16 & 1/30/16) the play store will not download apps over approx 25 MB. Play store downloads the app to 99%, restarts the download, then fails with error 963. Small apps are unaffected. Using the exact same method, but with an open gapps from 12/08/15
https://www.dropbox.com/s/e7a48os7ucj014p/open_gapps-arm-5.1-stock-20151208.zip?dl=0
, works perfectly fine. Just thought I'd see if anyone had any thoughts as to what's up. Ideas, contents, suggestions appreciated.
sd card
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
kikkie said:
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
Click to expand...
Click to collapse
I think the issue is related to the way CM12 chooses the default install location for you. The newer gapps builds may have triggered something, but I believe the root of it to be the default installation location. Please see this post for a possible permanent solution.
http://forum.xda-developers.com/showpost.php?p=65139180&postcount=6
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
elderlypunk said:
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
Click to expand...
Click to collapse
No joy after changing the default location? Which way did you use to change the location? Did it give you any messages? it shouldn't have, if it worked, it should just have returned a prompt.
Just to be on the safe side, I would load the gapps file that you mentioned was working in the past, and change the default location before trying any of the apps. If you already have it all loaded up, then yes, I'd also recommend you clear the cache and data from the playstore and playservices apps.
Don't know if you're using opengapps, but I took a look at their most recent builds and noticed that the file size changed slightly after 01/20/2016, so your reasoning has merit.
If you happen to be using TWRP, you could also try changing the location from recovery. Advanced -> Terminal Command -> Select and then enter the command. I really hope this helps.
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
elderlypunk said:
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
Click to expand...
Click to collapse
Ugh. I was able to recreate the behavior you're experiencing on a 2012 Nexus 7 - the only device I have access to with no SD card slot. I used the last two nightlies of CM12 and opengapps from two days ago, and also the one I mentioned from 1/20. Always had the behavior when downloading large apps, and as you say, apps not from the playstore. And yes, same behavior whether I used nano, pico, et. al.
The behavior disappears once I flash the latest nightly with the gapps from 1/20 AND change the default location. I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Gster09 said:
I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Click to expand...
Click to collapse
No worries! Since I found a working older gapps I'm inclined to let this go for now.
Which older version did you install? I'm running into this issue.
See link in op.
Hello,
I have same 963 error issue on my both cm 12.1 devices : Galaxy Nexus and Nexus 7 (2012).
I tried on my Galaxy to "pm set-install-location 1" but it don't solved the issue.
(delete the play store app cache and data don't work)
Can you provide me the link to this Gapps, it is not working anymore
ancelin said:
Hello,
Can you provide me the link to this Gapps, it is not working anymore
Click to expand...
Click to collapse
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue.
Click to expand...
Click to collapse
Did s/he mention when it will be fixed?
If you're looking for a version of Open GApps that doesn't have the double download fail with error 963. Then you should install Open GApps 2016.01.05. Don't install the 2015.12.08 version if you're using CyanogenMod! You'll end up breaking WebView on your rom if you do. You can find an Older Version option on the Open GApps Web Site and get the version I mention from there.
As others may have mentioned you can temporarily dismount your SD Card as a work around to this issue, but I preferred to downgrade rather than having to do that every time I used the Google Play Store.
As I understand the issue it's not a bug with Open GApps itself but a bug with the Google Play Store, apparently but I haven't confirmed any version of Google Play above 6.0.5 can have this issue.
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
Click to expand...
Click to collapse
This fixed the issue for me, and I was able to install the 2 problematic apps. Strangely, I had no trouble installing some other apps, namely made by my operator (MEO music and MEO drive), which leads me to think it might be related to locale.
However, now I can't search the play store, as it force closes when tapping the search box :/
Best thread ever.
Finally it works.
Thanks everyone