Database Develop

New posts should go to Koush's CM6 thread. Mods, please close.

Koush posted a new thread with the release of CM6 RC3 and this one will no longer be maintained.
Thanks to everyone for their testing and bug reports!
http://forum.xda-developers.com/showthread.php?t=755690

Thx, I hate having to read through all the other pages to get this. PLEASE edit with nightly builds.

Wireless tether works fine if u download it from the market.
Sent from my Incredible using XDA App

Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?

killer2239 said:
Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?
Click to expand...
Click to collapse
Yes. Does the same to me.

jermaine151 said:
Yes. Does the same to me.
Click to expand...
Click to collapse
Ok, thanks for clarifying. In your summary might want to put something regarding "Unable to add to accounts & sync" , just for others that might be curious.

Wireless tethering worked for me, i just installed the one provided in the 10minute root video again after CM6 was installed. Then tested it and it worked fine. I also have Hydra Rom for stock speed undervoted with wireless N. Noticed when i did tethering it only connected to my laptop in G mode, however i am able to connect to my router in strictly wireless N broadcast.

Had this problem last night which forced me to revert back to stock firmware.
I plugged in my phone to charge at 11 PM. Then at 12.30 ish AM, i heard my phone vibrating. I looked and it rebooted. So i let it be, then few minutes later I heard it again. Then I decided to revert back to Stock.
Thinking that it was maybe caused when charging the battery. That the batt got 100% then rebooted? Not quite sure.
I can test again if needed.

Good idea.
Thanks!

You are most welcome!

Thank You very much

what time is the nightly build and what time standard/zone?
i would love to try this but cant without bluetooth and am hoping it makes it into the next build. in my state they are cracking down on using your cell phone without a handsfree and giving big tickets to make up for budget shortfalls. so i need bluetooth. (i am too deaf for speakerphone, especially on the incredible, its not that loud)
i am excited, especially now i am 90% sure i am keeping the DINC now that the DX is officially going to be a ***** to root and no roms looks likely. and i dont know why blogs that pimp the phone keep saying "root is still inevitable" but i dont agree with that, if you cant get into the boot loader we would have never rooted the incredible and it only makes sense motorola has locked down the backflip root methods and made sure rooting will also be hard.
i just really want a bigger screen and a fast gpu, other than that, the DINC is the best.

cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!

jermaine151 said:
cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!
Click to expand...
Click to collapse
thanks man! keep up the good work!
and nice, based on your answer on the first post, we have a new build as of a couple hours ago, anyone running it yet? anyone have a revised bug list? should we discuss that here or in the other thread?

It would appear that the incredible has been removed from the buildbot cycle as of the latest build. A version was built today (check the dates) but looking here: http://buildbot.teamdouche.net/tgrid it's no longer listed

I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.

killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
if you clear download cache and redownload it should be newer, someone posted the repo and it clearly showed a date and time of today even though the file name still said 7-8 or 7-9 on it the time and date were 7-10 unless it was mirrored then or osmething.

killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.

Sometimes download of apps in market just stalls.
Some apps fail to install. (android-vnc)
Sometimes screen doesn't register touches until rotated.

jermaine151 said:
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.
Click to expand...
Click to collapse
Deleted the CM6 zip file from the sd card, then redownloaded the nightly build. Installed and noticed the rom version now has 7/11 as the date instead of the zip files number. So thats good. I see you crossed out the green light while charging bug. Thats only difference i have noticed thats been fixed.
I really hope they are concentrating on Facebook, Camera, GPS bug the most. Thats the biggest deal breaker for most i know.

Curiosity about the state of CM 10.2 Nightlies

For those of you who are running the latest CM 10.2 nightly, what is the current state of the builds? The last time I ran a nightly (which must be almost a month ago now), NFC functionality was not not working correctly, the messaging app would not rotate correctly after locking the screen, notification sounds were delayed causing the system to lag, and any application had the tendency to randomlly on rare occasions.
So, have you noticed any issues (even if only small)? Have the issues the listed been fixed?
P.S. Yes, I am aware of the beta-like state with nightlies, so please don't complain to me about 'breaking the CM rules'. This post is far from a complaint; it is more like a means of gathering information about the ROMs, to determine whether or not to run them.
Thank you, those any who may reply

Im not in cm right now but you can check this thread:
http://forum.xda-developers.com/showthread.php?t=2264616
Or the official cyanogenmod forums.

csfrank271 said:
For those of you who are running the latest CM 10.2 nightly, what is the current state of the builds? The last time I ran a nightly (which must be almost a month ago now), NFC functionality was not not working correctly, the messaging app would not rotate correctly after locking the screen, notification sounds were delayed causing the system to lag, and any application had the tendency to randomlly on rare occasions.
So, have you noticed any issues (even if only small)? Have the issues the listed been fixed?
P.S. Yes, I am aware of the beta-like state with nightlies, so please don't complain to me about 'breaking the CM rules'. This post is far from a complaint; it is more like a means of gathering information about the ROMs, to determine whether or not to run them.
Thank you, those any who may reply
Click to expand...
Click to collapse
I am sorry to say you are aware of most of the things about CM 10.2 but not aware about rules on XDA and posting your question in wrong section................:banghead:
Sent from my LG-P880 using xda premium app.
Like what I said hit " Thanks" Button.

rellagher said:
Im not in cm right now but you can check this thread:
http://forum.xda-developers.com/showthread.php?t=2264616
Or the official cyanogenmod forums.
Click to expand...
Click to collapse
hmmmm , link goes something like that 10.2-20131004 so if u reverse it , it looks like it got latest update yesterday.
Edit: but i dont see any infos. isnt there somewhere where the official site should have at least a section with changes on the update ? i wonder.....

[Q] Hangouts 2.3 on T679

I have the CM11 Rom installed on my Galaxy Exhibit and installed Google+ Hangouts 2.1 a while ago. I tried to update to 2.3 (new google voice integration!) but the Google Play store says Hangouts in incompatible with the "T-Mobile - US Samsung SGH-T679" Is this something with this ROM, or it is a real hardware issue? Have other people gotten Hangouts 2.3 working on the T679? Could I side-load Hangouts?
Thanks,

I am on cars' latest CM11 ROM with the Christopher K^Kernel and had no problems updating to the latest Hangouts 2.3.75067996. Got it straight from Google Play automatically. Also installed the latest Hangouts Dialer from Google Play, plus Google Voice. Not sure why it wouldn't work for you. Are you sure you're on CM11?

Interesting. Glad to know it can work on my hardware. I'm running CyanogenMod 11 20140714-UNOFFICIAL from http://forum.xda-developers.com/showthread.php?t=2542793 -- which ROM are you using? The latest CM 11 doesn't mention using Christopher's Kernel, although the 7/10 version does. If it were a kernel thing, I'd be surprised that when I go to the google play website (on my desktop) it says that Hangouts isn't compatible with SGH-T679 -- although maybe it is really saying it isn't compatible with my phone in its current form and it happens to be a SGH-T679.
Are you running a different DPI? I've occasionally had this issue on some apps when I switched to 182 DPI, but since gmail, etc works I didn't think that was the issue.

Cars' ROM is at http://forum.xda-developers.com/showthread.php?t=2600757. Standard DPI. Using the final Banks Minimal Gapps. I haven't changed my install much beyond that.
Guessing it's the difference in ROMs. Also, do you have Google Voice installed? If not, I'd try getting that first.

exhibit679 said:
I'm running CyanogenMod 11 20140714-UNOFFICIAL from http://forum.xda-developers.com/showthread.php?t=2542793 -- which ROM are you using? The latest CM 11 doesn't mention using Christopher's Kernel, although the 7/10 version does. If it were a kernel thing, I'd be surprised that when I go to the google play website (on my desktop) it says that Hangouts isn't compatible with SGH-T679 -- although maybe it is really saying it isn't compatible with my phone in its current form and it happens to be a SGH-T679.
Are you running a different DPI? I've occasionally had this issue on some apps when I switched to 182 DPI, but since gmail, etc works I didn't think that was the issue.
Click to expand...
Click to collapse
Previously I successfully installed and ran Hangouts on the ROM you linked: CM11 by @jfbs.
The GApps I used was also the one that @ulibube mentioned: BaNkS 7-29_GApps_Minimal_4.4.4 (no longer available).
My theory is you're running into some GApps issues.
For example, the last couple of days I've been playing around with different ROM, kernel, and runtime setups.
One time I flashed a GApps version dated 6/6/14; this one had an older Play Store version, so when I installed Hangouts, I received a message from Hangouts that said I have to update Play Store and Google Framework Services. I thought this was weird so I started from scratch again as not to encounter any errors.
This is my current setup as of this morning and I haven't encountered any errors:
ROM: CM11 by @cars1189 Build 9-9-14. Can be found here (scroll down to ROM 9-9-14).
Kernel: ADC/Linaro (note: this kernel may not support OC/UV, if you need that, use Christopher K^Kernel). Can be found on same link as above (use the build corresponding to ROM build date).
GApps: PA GApps - Nano Modular. Can be found here.
Runtime: Dalvik
Note: I am not running a custom DPI and a search reveals that may also be a issue.
I found this link that may pertain to your use-case: Play Store Fixes | Xposed Module Repository I have no experience with Xposed Module though, so you're on your own and further research is required.

should you need banks still i uploaded and posted under Mahdi 4 page 3rd to last post about a week or so ago.

One more note, not sure if it's relevant - I overclock to 1.4GHz.
Also, not sure what the audio quality of the VoIP Hangouts is on our little phone - have not put it to use yet.

ulibube said:
Also, not sure what the audio quality of the VoIP Hangouts is on our little phone - have not put it to use yet.
Click to expand...
Click to collapse
It's pretty good.
I'm using AT&T with this phone and in my area signal quality is very poor; for some reason the other night I could not make a regular phone call (received some error about Mobile Network not being available) but the phone showed I had 3G, so I made a Hangouts call and it was just like listening to a regular call.

So, I sideloaded Hangouts 2.3 on my phone and it worked fine. Google Play still said the app was incompatible, but whatever. Then this morning I see that there is a Google Play update to Hangouts. Seems like whatever issue I was having got fixed with the latest Hangouts update and it now says my phone is compatible. Weird as I didn't change anything on my phone, but whatever.
I'd say VOIP quality isn't great, but is useable. My VOIP phone over the same internet connection is significantly better. Haven't tried over 3G, only WiFi.

I'm running cars' 9-9-14 cm11 build with k^kernel 3.4.102 and have Hangouts 2.3 running ok, and I can make and receive Google Voice calls, but the phone will vibrate only when there is an incoming call. I checked all the volume levels and the ringer volume is turned up. It rings normally if I do a hangouts video call. Anybody else having this issue?

spiked_mistborn said:
I'm running cars' 9-9-14 cm11 build with k^kernel 3.4.102 and have Hangouts 2.3 running ok, and I can make and receive Google Voice calls, but the phone will vibrate only when there is an incoming call. I checked all the volume levels and the ringer volume is turned up. It rings normally if I do a hangouts video call. Anybody else having this issue?
Click to expand...
Click to collapse
I just called my Google Voice number and I'm having the same issue described as you; only vibration on incoming call.
I wonder if this is an app issue or ROM issue. I just got a Moto G tonight, will test and report back.

Just wanted to report that when calling my Google Voice number and Hangouts v2.3.75731955 setting Incoming phone calls is checked and Phone ringtone is set to ring, the Hangouts app indeed rings.
As for the Exhibit and Hangouts, maybe have to Clear app data and try again.

[Q] Google Play Services Wakelock with CM Installer ROM, suggestions?

Hi,
Last year I've installed CM with the Installer (http://beta.download.cyanogenmod.org/install) on my HTC One M7. It works like a charm but since then I haven't received any updates. After some searching I've found why: the CM version installed by the installer doesn't follow the default CM channels. Only stable releases done by CM itself can be installed with the updater. I'm currently running this build: cm_m7_userdebug 4.4.4 KTU84Q InstallerXNPQ32P release-keys from Aug 6 2014
But, my battery drains because of the Google Play Services "bug", see: https://jira.cyanogenmod.org/browse/CYAN-6438. It's fixed but since I've not received any updates I've got still trouble with this. So I've followed this tutorial to fix it: http://forum.xda-developers.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548. It worked for some days but then I was getting every x minutes a error that "Google Play Services stopped working". So I've searched around and did this: https://forums.oneplus.net/threads/...s-stopped-working.302508/page-2#post-11373191. It worked for some days but now the error is back AND my battery drains again.
My next thought was, installing the latest build from the default CM channels, so I went here: http://download.cyanogenmod.org/?device=m7 but I only see CM 12.1, not CM 11. Since I don't want to do a factory reset, backup everything and move over to Lollipop (just wanted to flash CM11 from the default channels over my current ROM to keep all settings, data and apps) I came here for some help.
What do you guys recommend? I've advised a lot of people to install CM through the installer to get rid of Sence and all HTC it's default apps to get easily a clean and faster smartphone. Even my girlfriend is running CM11 on her Samsung Galaxy S4 with the same problems. Backup all the phones and flash the latest roms takes some time... I've found two other possible solutions:
- http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082 (but that's for Google Play Services version 7.3.29 (030), I'm running 7.5.74 (1997312-038))
- http://forum.xda-developers.com/google-nexus-5/general/script-google-play-services-battery-t3059585 (the first solutions sounds nice, but what will happen if Google updates the app?)
I hope someone can help me out.
Thanks in advance,
Roy

Anyone?

royduin said:
What do you guys recommend?
Click to expand...
Click to collapse
royduin said:
Anyone?
Click to expand...
Click to collapse
I would recommend to try CM12 or to stay away from Cyanogenmod if you don't have the time to play with your phone (backing up / restoring / re-flashing). Cyanogenmod roms are great but rarely bug-free / stable.
Btw another good alternative if you want to get rid of HTC Sense roms is to use GPE rom which is also made by HTC and will ensure better stability and less bugs over other aosp roms like CM.

Thanks for your response! I've the time but as I told I've recommended a lot of people who don't have much knowledge about flashing roms to install CM with the CM Installer. So I'm searching for the easiest way to stop the wakelock.

When I was having that problem, I found this worked perfectly:
muzso.hu/2014/09/18/how-to-fix-the-partial-wakelock-problem-on-cyanogenmod-11-with-google-play-services-and-o

b00tstrap said:
When I was having that problem, I found this worked perfectly:
muzso.hu/2014/09/18/how-to-fix-the-partial-wakelock-problem-on-cyanogenmod-11-with-google-play-services-and-o
Click to expand...
Click to collapse
I see you are giving some good advice in many threads today, might worth to quote the OPs of all these threads if you want them to read your comment otherwise they are not notified.:good:
@royduin read above post

alray said:
I see you are giving some good advice in many threads today, might worth to quote the OPs of all these threads if you want them to read your comment otherwise they are not notified.:good:
@royduin read above post
Click to expand...
Click to collapse
ah, oops, I didn't realize it worked like that....thanks

b00tstrap said:
When I was having that problem, I found this worked perfectly:
muzso.hu/2014/09/18/how-to-fix-the-partial-wakelock-problem-on-cyanogenmod-11-with-google-play-services-and-o
Click to expand...
Click to collapse
Thanks for your reply, I've undone all my previous changes and ran those commands through ADB. Let's wait for now thanks!

b00tstrap said:
When I was having that problem, I found this worked perfectly:
muzso.hu/2014/09/18/how-to-fix-the-partial-wakelock-problem-on-cyanogenmod-11-with-google-play-services-and-o
Click to expand...
Click to collapse
It work's like a charm but now "Google Services" uses a lot of battery. I don't remember if I disabled "com.google.android.gms/.gcm.nts.SchedulerInternalReceiver" too, so I did that today. Let's see what it does.
How can I see what specific process is taking so much battery? I see the app but I don't see what process/service it is...

royduin said:
It work's like a charm but now "Google Services" uses a lot of battery. I don't remember if I disabled "com.google.android.gms/.gcm.nts.SchedulerInternalReceiver" too, so I did that today. Let's see what it does.
How can I see what specific process is taking so much battery? I see the app but I don't see what process/service it is...
Click to expand...
Click to collapse
You might be running into a fundamental CM11 issue with the Google Services battery use. For tracking the battery usage, I like BetterBatteryStats the best, in the section "Partial Wakelocks". It does a good job of showing what's keeping the phone awake.

b00tstrap said:
You might be running into a fundamental CM11 issue with the Google Services battery use. For tracking the battery usage, I like BetterBatteryStats the best, in the section "Partial Wakelocks". It does a good job of showing what's keeping the phone awake.
Click to expand...
Click to collapse
Thanks for your reply, I've disabled "com.google.android.gms/.gcm.nts.SchedulerInternalReceiver" yesterday and my battery doesn't drain now I'll looking too the BetterBatteryStats app, thanks!

No calendar notifications on lock screen since update to LineageOS 19.1

Hello
Since updating to LineageOS 19.1 I no longer receive notifications from the calendar app. The notification only appears after I open the calendar app. Does anyone know the problem and can help me solve it?
Many thanks

Found this thread, says apps such as cleaner master can cause such an issue.

iddqd23 said:
Hello
Since updating to LineageOS 19.1 I no longer receive notifications from the calendar app. The notification only appears after I open the calendar app. Does anyone know the problem and can help me solve it?
Many thanks
Click to expand...
Click to collapse
I have the same problem. One thing to try is long press on the calendar app and tap the "i" to see the app info. Make sure that alarms are allowed (at the bottom) and also try changing Battery to "unrestricted".

I have the same problem in a Pixel 4a (sunfish). I was going to open an issue at Gitlab, but haven't been able to narrow the focus. Last week I got a notification (right on time), while I was on a phone call. However, I can't figure out when it works (almost never), or why.
As you said, sometimes I get old notifications (24+ hrs old) while working on the calendar app.
There's another issue with Calendar. It crashes when you try 'search'. I saw this on Gitlab. That can be fixed by installing the FDroid version of Etar 1.0.30. However, notifications aren't fixed by using that version. I tried.
I just changed Battery from 'Optimized' to 'Unrestricted'. I don't have much hope, though.
I'll post if that helps.

juserj said:
I have the same problem. One thing to try is long press on the calendar app and tap the "i" to see the app info. Make sure that alarms are allowed (at the bottom) and also try changing Battery to "unrestricted".
Click to expand...
Click to collapse
Changing battery to "Unrestricted" made the difference for me. I've not missed a calendar notification since the change. Thanks for this.
However, is this a bug? Should it work with battery 'Optimized'?
BTW, you might consider having this discussion within the official LOS19 thread.

mangokm40 said:
Changing battery to "Unrestricted" made the difference for me. I've not missed a calendar notification since the change. Thanks for this.
However, is this a bug? Should it work with battery 'Optimized'?
BTW, you might consider having this discussion within the official LOS19 thread.
Click to expand...
Click to collapse
Yes, this method seems to be working for me as well. May be good to mention it in the LOS19 thread. It is sort of a bug in design if anything. Since the calendar app may not be accessed much or have constant reminders, it might not be given high priority in the optimization.

Thank you for that information. Will try that with changing battery to "Unrestricted".

Thank you! Everything now works perfectly!