Related
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.
Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.
Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug
superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.
Bump
Anyone have some insight on this?
Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug
Any news ?
soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse
Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Q&A for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no sound, no auto-rotate
I am fairly new to Rooting and updating my Xoom to the newest Kitkat system. I am having 2 issues as of right now. The sound has never worked no matter what the settings say, and initially the auto-rotate was functioning and suddenly it stopped.
I have checked all options/setting and see nothing that should explain either of these 2 issues. I also didnt add any new apps in the time from initial update to the auto-rotate not working so if anyone has any suggestions or ideas, it would be greatly appreciated.
Again I am fairly new to all this, so the simpler or more detailed the potential solution the more likely I will understand it.
Thanks.
No sound on Omni 4.4 cmda version
I love the rom, only problem is I have no sound on the cmda version. I read the comments and saw people suggest install the top rom version over the bottom and then reflashing gapps. Should have sound. When I do this tablet boots but keeps giving me error "Unfortunately, the process com.android.phone has stopped" I say ok but it keeps coming up and wont let me get any further. Any suggestions?
volume issue
Anyone know how to fix the no sound issue in omni rom 4.4.4 stingray cdma? I cant get any sound at all. Help would be appreciated.
Took a couple go's but now up and running 4.4.2!
Thank you!
First time I've moved from the standard stock implementation, never even rooted the device before, but a couple attempts and following your instructions I managed to install BigPart, Flash omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip, gapps-xxxx.zip & UPDATE-SuperSU-v1.86.zip.
I was about to give up on the Xoom and buy something newer, Tab S or something, but this appears to have put new life back into the old Xoom!
Followed the instructions above, but could not get it to clear Dalvik, failed every time. In the end I bit the bullet and formatted the internal drive, then flashed again - worked like a charm - figured since I was going to pass it over for a new one or this was going to work I had little to lose. As it happens I now seem to have it back & working well.
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Blackdogn3 said:
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Click to expand...
Click to collapse
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
slow1234 said:
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
Click to expand...
Click to collapse
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Blackdogn3 said:
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Click to expand...
Click to collapse
It has also been noted that 9.2.0 is rolling out and that it works on the Xoom. I updated yesterday and did a quick check - it does appear to work fine!
No Sound
After I flashed "[ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart." onto my Verizon Motorola Xoom 4G Tablet,
I have no sound at all and also the auto-rotate feature does not work (stays locked in portrait mode until reboot).
A number of other forum members have posted the same problem. Can we get a solution from someone on the forum?
have all but twrp v 2.6.3 big part
I have every thing I need except big part v2.6.3, none of the links I've found work? Does it have to be v2.6..3. ? There seem to be updated versions?
No 3g or 1x fallback
Install this today, everything went ok, execpt i could not get verizon 3g or 1x service. 4g works fine, when i have coverage. SBF back to stock again i guess.
e:unable to mount '/cache
The process for flashing the xoom (stingray model) seems somewhat straightforward. Yet I can't seem to get a working flash from the effort. Two problems:
1) during the "wipe this and that" stage while running in recovery, I get "FAILED" for each of the requisite areas to wipe, along with other messages such as that in the title. while i find a handful of other posts within this forum from folks experiencing the same problem, i find nothing in response with useful suggestions to fix what's apparently broken;
2) the tablet boots up to the OMNI splash-screen, and that's it.
I've repeated the steps at the head of this thread umpteen-zillion times. But the result is the same after each attempt. Either some critical step (or two) is/are missing from the initial (and horribly written) description, or I have the most stubborn tablet built.
i haven't bricked the thing... i can access it via adb, and i can get into recovery with no issues. what i can't seem to do is:
1) find a TWRP download using the links provided that doesn't trip quarantine due to virus detection; or,
2) find a coherent set of instructions that correctly describe the logical flow of the process of flashing a ROM on a Xoom.
Suggestions?
CDMA Voice and data programming
Hi,
Thanks for your effort and excellent work but I need some help, The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Another question that I have is related to BP tools or programming the Cdma xoom, every time I try to start in bp tools I was not able to see the utility, just today i tried to connect to my PC and its not able to connect to CDMA Workshop or QPST, is there a way to do that? i need to activate something? any idea would be great!
And would be great if you have any MZ600 SBF where has included the first baseband 2.00 'cause probably it will help me to recover my 3g data (it's the only thing i didn't find and try).
Thanks!!!
is this have a default calling future like any mobile?
Thank You to OmniRom for xoom devolopers (all of you)
I just wanted to post a thank you to all of the developers of the omnirom for xoom. I was able to install it tonight, with a couple soft brick scares, but it is up and ruining. I love my xoom and am very appreciative.
Thanks....Steve
Xoom OnmiROM freezes
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
semi-anonymous said:
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
Click to expand...
Click to collapse
It's not real common for this to happen, but this same issue does occasionally happen on the CyanogenMod 11 Rom also. Other than this, and the workarounds to do a few other things in Android 4.4.4, the Xoom has been a real God send that is just amazing.
Non-Functioning Sensors post-flash w/Omni Stingray
Finished flashing XOOM 4G with (in order listed):
Xoom-Universal-Root
R.A.H._TWRPv2.6.3
omni-4.4.4-20141130-1816+0100-stingray_cdma-HOMEMADE
pa_gapps-modular-pico-4.4.4-20150215-signed
UPDATE-SuperSU-v2.45
After I noticed that the auto-rotate didn't work, I downloaded "My Android Sensors" from the Play Store. It shows the NO sensor is working. What gives..?
Looking for file EOS-Stingray-imm76l-radios-update.zip
Hi all,
Can someone help with the file ?
EOS-Stingray-imm76l-radios-update.zip
Thank you
The Rom works great.
I installed it month ago and it is working fine.
Batterylife is perfect and all things are working.
Thanks
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
I'm using cm and lineage and they are alright, cm from November has less bugs right now
What bugs are you seeing on Lineage?
jdinkel said:
What bugs are you seeing on Lineage?
Click to expand...
Click to collapse
Sprint variant, normal cm complaints early: SMS issues, some calling issues, can't cheat at pokemon go, 5ghz WiFi crashes for me 900p on lollipop bootloader...ok4 firmware
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
jdinkel said:
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
Click to expand...
Click to collapse
Is it a bug in the. .looking at the screen thing? My cm flashes sometimes because it thinks Im looking at it or not
i7vSa7vi7y said:
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
Click to expand...
Click to collapse
the internal storage issue youre having isnt ROM specific, its basically an issue with the ROM basically ghosting your internal storage and ignoring whats there by not looking at the table of contents. Ive been looking for a solution for this myself and not finding much. If i find a solution, ill post something up