[Q&A] [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015 - Galaxy S 4 Active Q&A, Help & Troubleshooting

Q&A for [ROM][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015
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][AOSP] Google Edition S4/ Pure Nexus[SAFESTRAP] Feb 24th, 2015. 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!

Just flashed this without having any trouble during the process until I powered off afterwards - or, attempted to. It hung on the power off screen, so I had to hold down the power button in order to turn it off. After I booted up again, Google Play Store crashed. I managed to get it to work long enough to install a few other apps (Textra, Lookout, Themer, and Dashclock) by disabling the Play Store app and then opening it. Whenever I tried to open these apps, they crashed upon opening and the app icon changed to the Android bot icon instead of the app's normal icon and the package name instead of the app name. After the first downloaded app crashed, then I got an error that Google Play Store crashed, and its icon changed the same way. I then attempted a factory reset within the ROM, but it hung on the power off screen. I held the power button again, booted back up, and it looks like all the preinstalled apps work except Play Store. When I try to test SuperSU, it says that Play Store has stopped and does not load a list of apps. Now, Google Now is saying that I "need Google Play Services, which is not supported by your device." Any idea what went wrong?

Had a similar problem, my mistake was not to follow the procedure EXACTLY as stated. It turns out that I did not wiped everything except from what's in the sd card, did that and boom! A nice ROM to play with. Give it a try.

I might give it a try again, but I know for a fact that I performed the wipe correctly.

Please, do tell how it went.

Worked this time! Thanks for your help!

Works great but have quite poor battery life, refuses to go into deep sleep.
msm-hsic-host wakelock, horrible wakelock pins the cpu 384 mhz min.
bugs ive found-
using the cast screen button renders a blank screen to my chrome cast.

Yup, battery life is pretty crappy. But had a similar battery life with stock NE3 firmware. In a couple of weeks I'll be getting a new battery. Bought my phone from eBay and it came with a used one, I'm just guessing at the moment.

I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.

ChristopherXDA said:
I lost 30% overnight but this morning changed some wifi settings and loaded up betterbatterystats to see what's causing the wakelocks. Maybe it's something straightforward. I like the aosp a lot and going to try and make this rom work as a daily driver.
I'll post any findings or improvements.
Click to expand...
Click to collapse
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.

bestestever said:
If possible go to the "raw info" in bbs, and check out your kernel wake locks, as far as the software went on this rom I saw no serious wakelocks, but when I switched to kernel view that's where the problem was. I lost all 80% over a period of ten hours while sleeping the other day. Thats with nothing installed but what came with the rom.
Click to expand...
Click to collapse
Yep, same here. Phone never enters deep sleep. After about 3 hours lost 10% of battery. 80% of the partial wakelocks were msm_hsic_host wakes.

I think the issue has to do with the wifi. Even though wifi is set to be off when the screen's off, betterbatterystats shows the wifi is on 100% of the time. This makes some sense since there appears to be an issue with the wifi driver where after a full reboot my wifi won't work until I do a hotboot. This happens for everyone else right?
I will try and look into the wifi fix that was part of the masterpatch and see if that provides any fixes.

Google edition pure nexus safestrap i537
tHANKS HOPE IT WORKS
---------- Post added at 08:06 AM ---------- Previous post was at 07:50 AM ----------
Unable to mount system original? that is the last message I get before last reboot. please help.

Littile things
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.

S4 Active Speaker Phone Fix
rockinwaggy said:
The issue with speakerphone, for me, is that the other end of the call doesn't hear anything when using speakerphone. Turn speakerphone off and it's back to normal.
Click to expand...
Click to collapse
ChristopherXDA said:
Is your speaker phone working on calls?
Click to expand...
Click to collapse
McJeg said:
Speaker phone NOT working.. (I can hear the caller, but they cant hear me)
Cant get Tethering to work either. It activates but cant find it as a hot-spot/AP on my devices.
Do get ghosts vibes every once in a while.
Click to expand...
Click to collapse
This is a known issue on the S4 Active as discussed here: http://forum.xda-developers.com/showthread.php?t=2412645
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.

Ha, oh man thats a little embarassing. You're right, that fix works on this Rom too.
I tried some of the other fixes though like for Wi-Fi in the masterpatch and that doesn't work on this rom.

k3u::straylight said:
This is a known issue on the S4 Active as discussed here: <url>
Flashing the file labeled "S4 Active Speaker Phone Fix" aka "S4_Active_Call_Record_Fix.zip" fixed this issue for me.
ChristopherXDA, it appears you were involved in the original fix!
Joe-Tech, you may want to incorporate the zip's changes to the sound configs in /system/etc/snd_soc_msm into your next S4 Active build.
Click to expand...
Click to collapse
Thank you so much, this issue was bothering me because I kept forgetting and putting people on speaker lol. Fix worked perfectly, I can confirm

Love this ROM, battery life is poop, but, can bear with it. Here is my antutu score.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I see little feedback for this ROM. What can I do to give give more accurate and useful info?

fuel426 said:
I see little feedback for this ROM. What can I do to give give more accurate and useful info?
Click to expand...
Click to collapse
The rom is generally problem free. Aside from the battery life, it's quite solid. Both of his nexus style roms have this msm_hsic_host wakelock problem (I've tested the GE S4 rom). He is aware of this issue. Unfortunately, he has had some personal things happen lately, so he's not available to work on the rom. Family comes first.
Also, I recently test DS Battery Saver from the Play Store. Even on its most aggressive battery saving mode, deep sleep was never entered. So, don't bother.

Related

Cyanogenmod 7 stable

Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?
http://download.cyanogenmod.com/?type=stable&device=legend
AND
http://wiki.cyanogenmod.com/index.php?title=HTC_Legend
Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?
Because right now the ROM is stable but not complete that's why nightlies are still going on.
I propose an idea
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sz1a said:
Hi guys,
Correct me if I am wrong but is CM7 STABLE already out?..
Click to expand...
Click to collapse
Yes it is, for the second time (first on 11.04 second from last night)
sz1a said:
...Why am I reading so many issues about GPS and various inquiries in the nightly section if there already is a stable out?
Click to expand...
Click to collapse
Because after first stable was out, there were still issues with GPS (in fact with the bearing during navigation). Later CM team has found a solution that was included in the nightlies, it was tested few days and most of us gave a positive feedback. Also some new things included (that "tablet" status bar was nice even if removed in #55). So, a new "stable" release was made to incorporate these.
50-3 said:
Because right now the ROM is stable but not complete that's why nightlies are still going on.
Click to expand...
Click to collapse
Nightlies are built every night and as long as the servers work they will be built every night.
Nightlies don't have anything to do with stable releases or feature completeness.
Ok, thanks. Surprised there isn't a thread dedicated to the stable release since more ppl would know about it then. I'll give 7.02 a go then, just flashed 7 stable last nite and pretty impressed so far (after new radio and the gps fix).
Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.
Rapier said:
Has anyone experienced some minor problems with the "wake with trackpad" option in the last stable version (7.0.3)? I mean, it wakes up the device, but mostly I have to press it several times not only once.
Click to expand...
Click to collapse
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.
Check that your cpu speed isn't set too low when sleeping
bonesy said:
Check that your cpu speed isn't set too low when sleeping
Click to expand...
Click to collapse
CPU settings were not altered from the begining. I run at 787 with min set to 245, interactive. It is like this from the first nightly that had the CPU OC included. It's not happening allways and also didn't had such problems with nightlies or other stable versions. That's not a big deal anyways...
By the way.. no questions in Dev section..
Sent from somewhere outta space using my phone..
beastie-boy said:
Yes, I experienced this issue and few other. Too annoying for me, so returned back to BlaYo's B-0.8. GPS issue fixed when upgraded radio. But I ocassionally pressed something on the screen with my face during calls. After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off). Automatic data synchronization (mail, news, weather) worked randomly - sometimes I had to manually check everything. I think, I just wait for fixes.
Click to expand...
Click to collapse
Having the loud speaker problem too, it's pretty annoying! Is it possible to revert back to 7.0.2 without wiping and just flashing?
sz1a said:
...Is it possible to revert back to 7.0.2 without wiping and just flashing?
Click to expand...
Click to collapse
Yes but won't solve the problem. This is present in all CM ROM's I've tried
Rapier said:
Yes but won't solve the problem. This is present in all CM ROM's I've tried
Click to expand...
Click to collapse
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..
And it seems it's somehow hardware dependent. I never had any "loudspeaker" problem with CM 7 stable or nightly.
regards
sz1a said:
You mean CM7 roms? I didn't have the loudspeaker issue with CM6 and as far as I know it was first with 7.0.3..
Click to expand...
Click to collapse
Yes, sorry, my mistake. I was talking only about CM7 ROMs, CM6 didn't had this
beastie-boy said:
After answering a call the voice was redirected to loud speaker by default (after about 1 s the loudspeaker was turned off).
Click to expand...
Click to collapse
Holy crap I thought I was the only one who had this. CM6 worked perfectly, since the update CM6 -> CM7.0.3 the ringtone plays, I accept the call, and can hear the other person on the (handsfree) loudspeaker for about 1 sec until the sound is switched back to the internal speaker.
It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.
oysteivi said:
It suddenly occurs to me that the reason I've never experienced this might be that I always keep the phone on "vibrate only".. Could be worth trying for those who frequently have the problem.
Click to expand...
Click to collapse
I dont get it and I have the ringtone on. Some hardware version dont have it and some do it seems.
I also have the problem with background data dropping when going into sleep mode after a while. When I wake my phone up the status bar icons are all white and I have to manually check gmail, etc. The phone establishes a connection with Google services again after a while and they go back to green but it is really annoying. Didn't notice this on 7.0.2. Apparently nexus s owners are having similar problems.

SOD or something else?

OOk, so I decided to flash Slim Bean 3.0.1 out of curiosity as I know my cappy has SOD issues when not running stock GB but this seems to be different from it.
To my knowledge the SOD issues mostly involve random reboots and shutdowns. My problem is a bit different.
Now mind you up until this morning I haven't had a single issue, it's been working flawlessly. Last night I decided to grab one of my favorite battery savers, Green Power Free. Now I'm not blaming the app, it's just the last thing I installed before all this happened. I've since un installed it but now every time I lock my phone, whether it be by my lock button, Button Savior, whatever, it reboots.
The thing is it doesn't even seem like a full reboot. Instead of doing the ATT logo, then the Semaphore logo, then SlimBean logo like it normally does. It only pops up with the Slim Bean logo. It also doesn't run the media scan. Also this weird toast message "Have a nice day" has been popping up since I installed Green power and even with the un install it still persists.
I don't really think this is SOD but if it is then I guess it's back to GB for me.
If there is anymore information I can provide please just ask, I'll gladly provide you with whatever info you need.
On that note, Captivate Keep Alive doesn't work.
Sent from my Samsung Captivate via Tapatalk 2.
athdaraxen said:
Ok, so I decided to flash Slim Bean 3.0.1 out of curiosity as I know my cappy has SOD issues when not running stock GB but this seems to be different from it.
To my knowledge the SOD issues mostly involve random reboots and shutdowns. My problem is a bit different.
Now mind you up until this morning I haven't had a single issue, it's been working flawlessly. Last night I decided to grab one of my favorite battery savers, Green Power. Now I'm not blaming the app, it's just the last thing I installed before all this happened. I've since un installed it but now every time I lock my phone, whether it be by my lock button, Button Savior, whatever, it reboots.
The thing is it doesn't even seem like a full reboot. Instead of doing the ATT logo, then the Semaphore logo, then SlimBean logo like it normally does. It only pops up with the Slim Bean logo. It also doesn't run the media scan. Also this weird toast message "Have a nice day" has been popping up since I installed Green power and even with the un install it still persists.
I don't really think this is SOD but if it is then I guess it's back to GB for me.
If there is anymore information I can provide please just ask, I'll gladly provide you with whatever info you need.
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
It's a hot-reboot. The phone runs out of ram and reboots itself for safety. As you noticed, it's doesn't turn off, it simply resets everything and start fresh from being overwhelmed.
Imo, you have something draining your ram, a rogue app or a bad backup.
So first thing, did you make any changes (mods/settings)? Did you restore your apps/data? Do you have Deep Idle turned on?
Next, that Green power app seems to install more than it should on your phone, I would suggest to look into that and uninstall anything else that it installed.
Look under your Apps (in settings) to see what's running and using your ram. If you see something unusually high, stop it and might wanna concider unistalling whichever app it is, just make sure it's something you don't need. Also, look at your battery stats to see if there's something top or 2nd that isn't screen on.
Have you tried running the ROM without any restore or mods? Or even without any extra apps, just with the Gapps. I'm thinking the issue is coming from a app you're using.
Another thing that might help is to OC to 1200 and run a bigmem version of your kernel (if you don't already). But those 2 shouldn't be needed.
I've never heard of that before but now that you say it that makes complete sense.
RAM has always been an issue for me on this phone, I usually only have maybe 44 mb of free RAM. I do my best to keep it down but it's hard. I had this issue with GB as well.
As for anything involving the ROM, no. Nothing extra, I did get the Gapps but other than this I have not messed with any setting as I feel I didn't know enough to go changing anything.
I'll watch my running services for a bit and report back with my findings. I'm glad it's possibly not SOD.
EDIT:
I do believe you were spot on, I went in and cleared out my running services list and my phone isn't acting up.
Is there anything you can suggest I use to prevent this from happening again? I've seen some RAM managers and such on the market but I wasn't sure which to pick, if any.
Here is my battery stuff.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Samsung Captivate via Tapatalk 2.
athdaraxen said:
I've never heard of that before but now that you say it that makes complete sense.
RAM has always been an issue for me on this phone, I usually only have maybe 44 mb of free RAM. I do my best to keep it down but it's hard. I had this issue with GB as well.
As for anything involving the ROM, no. Nothing extra, I did get the Gapps but other than this I have not messed with any setting as I feel I didn't know enough to go changing anything.
I'll watch my running services for a bit and report back with my findings. I'm glad it's possibly not SOD.
EDIT:
I do believe you were spot on, I went in and cleared out my running services list and my phone isn't acting up.
Is there anything you can suggest I use to prevent this from happening again? I've seen some RAM managers and such on the market but I wasn't sure which to pick, if any.
Here is my battery stuff.
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
Well first off, I would get a new modem, the one you have doesn't seem all too great in your area. (unless you're in a basement or bad coverage area?)
For ram, grab Semaphore manager from the market and enable Bigmem (requires reboot and breaks 720p recording). Also, whichever extra process you stopped that were up the roof, I would highly suggest unistalling if it's not something important, like a market app (no system process eh).
BWolf56 said:
Well first off, I would get a new modem, the one you have doesn't seem all too great in your area. (unless you're in a basement or bad coverage area?)
For ram, grab Semaphore manager from the market and enable Bigmem (requires reboot and breaks 720p recording). Also, whichever extra process you stopped that were up the roof, I would highly suggest unistalling if it's not something important, like a market app (no system process eh).
Click to expand...
Click to collapse
Bad coverage area. I'm in a small rural town where I work, but I live in a bigger city a little ways off, full bars all the time there lol. I actually had to flash a new modem when I got SlimBean, it's working great.
Well I ended up just killing everything not system apps to see what my RAM looked like and I got it down to 138mb. I also grabbed RAM booster off the market and it's keeping me around 100mb of free space.
I'll go grab the stuff you mentioned now and see what that does.
Thanks for the help. :3
Sent from my Samsung Captivate via Tapatalk 2.
athdaraxen said:
Bad coverage area. I'm in a small rural town where I work, but I live in a bigger city a little ways off, full bars all the time there lol. I actually had to flash a new modem when I got SlimBean, it's working great.
Well I ended up just killing everything not system apps to see what my RAM looked like and I got it down to 138mb. I also grabbed RAM booster off the market and it's keeping me around 100mb of free space.
I'll go grab the stuff you mentioned now and see what that does.
Thanks for the help. :3
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
I would uninstall RAM booster if I were you, it's a auto-kill app, which will drain your battery from killing apps that keep restarting and on top of that, it uses 39mb of ram itself!? That's insane. Just get Semaphore manager, it's made to work with your kernel and if you feel like you need the extra ram, enable Bigmem in the app's settings.
BWolf56 said:
I would uninstall RAM booster if I were you, it's a auto-kill app, which will drain your battery from killing apps that keep restarting and on top of that, it uses 39mb of ram itself!? That's insane. Just get Semaphore manager, it's made to work with your kernel and if you feel like you need the extra ram, enable Bigmem in the app's settings.
Click to expand...
Click to collapse
I figured it be a battery drain. These things usually are. I don't know if this makes any difference but I do have ROM Toolbox Pro. I know it has App Manager in it, I'll poke at it and see what it can do.
I did enable Bigmem, worked great! :3
The 720p thing, that's for video recording right?
Sent from my Samsung Captivate via Tapatalk 2.
athdaraxen said:
I figured it be a battery drain. These things usually are. I don't know if this makes any difference but I do have ROM Toolbox Pro. I know it has App Manager in it, I'll poke at it and see what it can do.
I did enable Bigmem, worked great! :3
The 720p thing, that's for video recording right?
Sent from my Samsung Captivate via Tapatalk 2.
Click to expand...
Click to collapse
I haven't looked much into ROM Toolbox Pro but I'm sure you'll be just fine with Bigmem as long as you keep track of your processes.
And yes, it breaks 720p video recording. Can be disabled though if you wanna use it.
Bigmem is definitely doing the trick. I've stayed around 100mb of free RAM since I activated it.
And that's actually fine with me, I have never recorded a video anyways so it won't even make a difference to me. Awesome.
I'm so glad it wasn't SOD thanks again for all the help.
Sent from my Samsung Captivate via Tapatalk 2.

[KERNEL-DEV][WI-FI FIX][ARP Offloading][Push Notifications][19 June][UPDATED]

The issue???
With all current kernels I and many other have been receiving delays in receiving notifications, in both screen on and off from 15mins to 2hours. Google should have released at least a minor update to fix this issue but they haven't and it bothers me.
As the title states I've worked on fixing WiFi and notification issues, its hasn't gone under mass testing so that's why I've created this thread for it, i have personally tested my device goes into sleep/deep sleep and i can ping the device when its in deep sleep, push notifications also work instantaneously I've received them within seconds
This should be used with Stock Android or Close to Stock e.g. AOSPA, Running on ROMS like MIUI will not work (tested)
Recommendations:
.54 Radio located here:
Push Notification Fixer (PNF Found in Play Store):
Installation:
1. Download this fix: Flashable zip wifi fix
Download: http://db.tt/NuQq7kk3
2. Download .54 radio:
3. Install Push Notification Fixer from Playstore:
4. Reboot into recovery
5. Flash zips in this order, radio, wifi fix, wipe cache & dalvik cache
6. Reboot into OS
Test for you:
1.Does my Device sleep?, let it sit for 10 minutes (device usually deepsleeps within 5 mins, allow your device to sit for 10mins)
3. Can you ping the device while its in deepsleep?
4. Any wakelocks showing? Mainly is there a suspend wakelock?
Once this has been tested ill push out another update, thank you!
Current issues:
On some devices suspend wakelock (Should be fixed)
Very rare occasion, 3/4 packets successfully received (packet lost while pinging)
Heartbeat interval can possibly be improved (haven't checked yet)
Ping to device when in deepsleep can be upto 1200ms which is too long for my opinion should be
Source code: https://dl.dropboxusercontent.com/u/58024932/prima.zip (PRIMA DRIVER)
Creditz & FAQ
Note to everyone: sooner i get results from more people, the sooner I can release the fix/ work on it quicker
Thank you @faux123 for your kernel base
Thanks to motley for his kernel base (wheres the dude gone?)
reserved
Dalidah said:
Hello,
dropbox link broken ...
Click to expand...
Click to collapse
Dropbox link working now, removed the previous version as it had trouble with cpu freq, the cpu freq went to min n locked on minimum lagging the whole OS, Just fixed now
I dont see any code posted in here http://forum.xda-developers.com/showthread.php?t=2272140 ... so why pouncing on someone who wants to help ? give him some time and he will release when its done.
Shaky156 said:
Dropbox link working now, removed the previous version as it had trouble with cpu freq and screen stutterin, the cpu freq went to min n locked on minimum lagging the whole OS, Just fixed now
Click to expand...
Click to collapse
Correction think there may be an issue with fauxs enhacement on locking with cpu at lowest freq, but my screen was lagging mainly cause o set gpu at 128mhz lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested deep sleeps perfectly fine
Anyone flashed this? Feedback?
Shaky156 said:
Anyone flashed this? Feedback?
Click to expand...
Click to collapse
Phone not sleeping. Tested in 3 different APs.
I don't wan't to be rude but what exactly are the Technical stuff that you've changed here? Sure you can say wifi but what part? Firmware? Drivers? If you just said that people won't be bashing your thread.
sigma392 said:
Phone not sleeping. Tested in 3 different APs.
I don't wan't to be rude but what exactly are the Technical stuff that you've changed here? Sure you can say wifi but what part? Firmware? Drivers? If you just said that people won't be bashing your thread.
Click to expand...
Click to collapse
3 people reported deepsleep, 2 person reported no deepsleep.
Changes in kernel, which ive already stated in thremcins hsic wakelock thread
Source code releasing within next few days
Sleeping like a baby
Hi,
I just tried it and my phone is not sleeping at all either. Why is it so hard for you to release the source code? This is quite suspicious to be honest.
I mean you say you want to release it within the next few days - lulz, why not now? Will anything change until then? I guess not.
I repeat: This is _NOT_ meant rude and I don't want to start a flame war.
They say seeing is believing id like screenshots of no deepsleep, release within the next few dayz as i have 2-3 kernels for testing, if alot of people do not get deepsleep then ill output another kernel, the point is to fix n release code, i have 2-3 kernels 1 of them will work for sure for people that cannot achieve deepsleep
Also my name is on that kernel like 100 times so i need to go through it n clean off comments
Edit: test this on stock ROM or Paranoid ROM, highly recommended, god knows whats causing the wakelock
And always provide screenshots
sorry for the question...but what is the point of this kernel?
i don't have a lot of time to lurk all topics, if someone can explain me why faux kernel need a wifi fix and what version of kernel has this problem (i'm not up to dated)...i'd be very grateful.
thx
beren said:
sorry for the question...but what is the point of this kernel?
i don't have a lot of time to lurk all topics, if someone can explain me why faux kernel need a wifi fix and what version of kernel has this problem (i'm not up to dated)...i'd be very grateful.
thx
Click to expand...
Click to collapse
All kernels have an issue with wifi, basically i have always recieved notifications late with both screen on and off from 15-mins to 60-mins, what i have done is fix this issue, some people reporting no deepsleep, me + few others have reported device sleeping and notifications on time. I chose faux kernel as his has a defconfig, didnt continue to test with francos hos doesnt include a defconfig making the source code uncompilable, this thread is here to fix and test wifi cuz i got tired of recieving late notifications
Sent from my Nexus 4 using Tapatalk 4 Beta
buster041284 said:
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I seeee deeeeepsleeeeeep!!!
Shaky156 said:
I seeee deeeeepsleeeeeep!!!
Click to expand...
Click to collapse
yea its sleeping and iam getting notification right away i stand corrected
Ok, latest update, fresh CM install, standard WiFi network I use (which never causes suspend_backoff on a kernel with my other notification solution). I think the screenshots speak for themselves.
Side Note: When I added another SSID to my network and blocked all internal and external multicast/broadcast traffic I did get some deep sleep but that's not a solution to the problem since most people wouldn't have access to do this nor would they want to if they could. I can also get the device to deep sleep on 3G/4G.
I remain skeptical that this fix works.
Sent from my Nexus 4 using Tapatalk 4 Beta
thracemerin said:
Ok, latest update, fresh CM install, standard WiFi network I use (which never causes suspend_backoff on a kernel with my other notification solution). I think the screenshots speak for themselves.
Side Note: When I added another SSID to my network and blocked all internal and external multicast/broadcast traffic I did get some deep sleep but that's not a solution to the problem since most people wouldn't have access to do this nor would they want to if they could. I can also get the device to deep sleep on 3G/4G.
I remain skeptical that this fix works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i was skeptical but look at my screen shots i did not have no wake locks how can this be your the dev i have no idea

Haven't had wakelock drainage since 2013 - so how's your Nexus 4 treating you?

The Nexus 4 is getting better with time. 4.3 went crazy on me so often I can't tell you, Google Keep, Calendar, Google Now! (now off) and other rogue apps causing wakelocks left and right... then KitKat came - with a rough start - and since on 4.4.2, I can't recall a single wakelock battery drainage. So much so that my utter disappointment of WLDetector unsupported then complicated on ART 4.4 quickly went away, and like task killers back in the day, wake fighting now seems like deeds of distant past...
So yeah, standby improved a great bit, just the other days I cracked the 100 hour barrier (not much stuff done, but with WiFi & hi accuracy on), so things are pretty nice. Now when traveling a lot, high accuracy taxes the battery plus ART runtime (the best thing in 2013) appears to be a bit heavier on resources. But oh the goodies of it! Spent like 2 hours last week playing around with the Z1, Z1 compact, Note 3, G2, couple of Lumias and HTCs, and all were noticeably laggier - no, they all had lags and stutters, this Nexus doesn't. Other than the choppy framerates of Real Racing 3 heh... We have an AndroiPhone on our hands, guys!
The 3rd thing I wanna say is how awesome and 'goodbye Nova' Action Launcher is, one home screen, swype right for app list, left for bookmarks/custom widgets, up for recents, down for notifications, tap on icons to launch app, swype over to pop-up folders or widgets - this thing is so simple and useful! Awesome to get the app & swype widget menu in any app too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2014 on the Nexus 4 has been quite awesome so far for me! How about you?
Wakelock? What's that?
No seriously, after the 4.4.2 KK update, everything went from good to great! Battery life really improved! So it all boils down to which ROM and kernel you're going to use to drive your Nexus 4. Quite happy with what i have right now.
Without wakelocks your device wouldnt get up from deep sleep to get notifications, etc. For example WhatsApp has 250+ wake-locks. Hence wakelocks arent bad. Wakelocks turn into a bad thing when they are unnecessary i.e the device will wake up for no reason or wont go to deep sleep, hence lesser battery life.
A partial wakelock means the CPU is ON, but the screen is OFF.
A full wakelock means the CPU and Screen are ON. (we don't really need to worry about this)
So the whole concept of saying u haven't had wakelocks since 2013 is flawed.
Here - http://forum.xda-developers.com/galaxy-nexus/general/kernel-wakelocks-t1462020
Well, I wish I could be as fortunate as you are. I have massive issues with msn_hsic_host kernel wakelock. Pretty much had it since I bought the phone a year ago. My feeling is that it got worse again with 4.4
On wifi everything is fine. On mobile data it can be ok or terrible. No way to tell why or when. A reboot solves it but I usually doesn't notice until the battery is already drained.
So my options seems to be to reboot the phone everytime I leave a wifi network or to use my Nexus as a dumphone. Right now I have background data restricted so it is pretty much a dumphone. Another option would be throw out this piece of **** and buy a good phone.
lndulgence said:
Wakelock? What's that?
No seriously, after the 4.4.2 KK update, everything went from good to great! Battery life really improved! So it all boils down to which ROM and kernel you're going to use to drive your Nexus 4. Quite happy with what i have right now.
Click to expand...
Click to collapse
Glad I'm not alone, Indulgence!
sandy-achar said:
Without wakelocks your device wouldnt get up from deep sleep to get notifications, etc. For example WhatsApp has 250+ wake-locks. Hence wakelocks arent bad. Wakelocks turn into a bad thing when they are unnecessary i.e the device will wake up for no reason or wont go to deep sleep, hence lesser battery life.
A partial wakelock means the CPU is ON, but the screen is OFF.
A full wakelock means the CPU and Screen are ON. (we don't really need to worry about this)
So the whole concept of saying u haven't had wakelocks since 2013 is flawed.
Here - http://forum.xda-developers.com/galaxy-nexus/general/kernel-wakelocks-t1462020
Click to expand...
Click to collapse
Thx, yeah you're right obviously, I should've said I haven't had any wakelock battery loops or whatnot, I changed the title. But you get the point. Things are great. :good:
Zinken said:
Well, I wish I could be as fortunate as you are. I have massive issues with msn_hsic_host kernel wakelock. Pretty much had it since I bought the phone a year ago. My feeling is that it got worse again with 4.4
On wifi everything is fine. On mobile data it can be ok or terrible. No way to tell why or when. A reboot solves it but I usually doesn't notice until the battery is already drained.
So my options seems to be to reboot the phone everytime I leave a wifi network or to use my Nexus as a dumphone. Right now I have background data restricted so it is pretty much a dumphone. Another option would be throw out this piece of **** and buy a good phone.
Click to expand...
Click to collapse
Sorry to hear that, no issues as such here. Maybe a factory reset? I'm sure you tried that already. Anyway, quick search brought this up, so I'm sharing:
http://forum.xda-developers.com/showthread.php?t=2297291
BoneXDA said:
Glad I'm not alone, Indulgence!
Thx, yeah you're right obviously, I should've said I haven't had any wakelock battery loops or whatnot, I changed the title. But you get the point. Things are great. :good:
Sorry to hear that, no issues as such here. Maybe a factory reset? I'm sure you tried that already. Anyway, quick search brought this up, so I'm sharing:
http://forum.xda-developers.com/showthread.php?t=2297291
Click to expand...
Click to collapse
Thanks for sharing but I have already googled my *ss off about this, nothing seems to help (other than disabling mobile data). I found 2 threads in google products forum about this where google employees admit that they are aware of the issue and investigating. Only problem is that those responses are many months old and the threads are closed due to inactivity.
Haven't done a factory reset on 4.4.2 but I did a clean install when moving to 4.4 - really hope to avoid losing all my data again.
Maybe I need to try to move away from stock and try a different ROM/kernel but that was one of the main reasons I bought the nexus, to have the latest android without having to flash. To easy to get addicted :silly:
What setup are u using? Audio mix, msim wakelocks are a pain in my arse right now
Sent from my Nexus 4 using Tapatalk
razi914 said:
What setup are u using? Audio mix, msim wakelocks are a pain in my arse right now
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Was that directed to me?
I'm completely stock 4.4.2. Google Now and location off. No "shadowy" apps, just mainstream popular apps on play store.
Still terrible wakelocks. With wifi or background data restricted it behaves "as it should".
Zinken said:
Was that directed to me?
I'm completely stock 4.4.2. Google Now and location off. No "shadowy" apps, just mainstream popular apps on play store.
Still terrible wakelocks. With wifi or background data restricted it behaves "as it should".
Click to expand...
Click to collapse
To the OP actually, u face my situation btw!!
Sent from my Nexus 4 using Tapatalk
razi914 said:
What setup are u using? Audio mix, msim wakelocks are a pain in my arse right now
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Stock unrooted 4.4.2 on ART (no FR), no Now!, 2G network preference (I'm almost exclusively near WiFi), Action Launcher with 6-7 widgets updating, GPS high accuracy mode. Wifi always on, but auto-search for networks off, no location sharing etc.
However today I installed Google Now Launcher, which means Now is active, let's see how it treats standby, probably bad. Oh and BTW, I run Google Now Launcher run over Action Launcher so I still retain the nice side-swype function, so it's a good mix, although GNL is quite limited and I'd prefer having "OK Google" listening on AL.
In other news: I did 2 further things to simplify my life:
- remove the dust and fingerprint collecting screen protector, tapping feels much nicer, navigation is much easier screen is a lot cleaner and the gorilla glass doesn't collect finger oil as much. Seriously guys, don't ruin your experience with cases and protectors, you treat your phone right, and it will treat you back
- turn off lockscreen. Since I look after my phone, there's little chance of theft and there's still locking option from any computer, so why lockscreen then? Whatever that was on it is on my homescreen (DashClock widget with notifications, camera icon plus everything else), lockscreen is... redundancy
At a good place right now on 4.3. Have everything I need: touch control, pie, halo, lte. Less I look for wakelocks,the more I notice the phone does pretty decent on battery. One time I came home from work with 74% battery (min usage- about 2 hour talk time on bluetooth). I never turn of lte and wifi. :good:

Tmobile Oreo out now!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just got the update message!
I look on tmobile official page and there was no mention of oreo update of this phone. I looked at this webpage https://support.t-mobile.com/docs/DOC-35970
Can you post your screenshot?
It is indeed live. I have Oreo on one device, trying to go back to stock on my second device and re-root.
For my device (on 26.7), it says it's up to date. They're rolling the update in waves.
Woooahhh..... Can we get a flashable zip file for it?
Posted the oto zip in rom section
same here, nothing, and when checking on T-Mobile page, it says it is still on the testing phase=(
---------- Post added at 01:47 AM ---------- Previous post was at 01:47 AM ----------
can anybody post a screenshot on OReo T-Mobile? Thanks
https://imgur.com/a/M3GOL
imna357 said:
same here, nothing, and when checking on T-Mobile page, it says it is still on the testing phase=(
Click to expand...
Click to collapse
TmoNews reports it's being released in waves. I'm sure we'll get it over the next couple days, but I'm impatient and spoiled since I've been on iPhone for the last few years.
the show stopper said:
Woooahhh..... Can we get a flashable zip file for it?
Click to expand...
Click to collapse
For the uninitiated and those who just forgot, is there a dead simple way to install the firmware on a stock T-Mobile Z2 Force using a microSD card, or does it need to be done through ADB? I've already downloaded both files (the 900MB really long filename and the 2.3GB zip file) from the other thread.
Well, I just received the Oreo Update on my TMO Moto Z2 Force and now no one can hear me during phone calls. Phone was working perfectly until Oreo installed and my phone rebooted. Going to try and wipe cache in Recovery to see it that does anything. I wouldn't be too anxious to update until a few peeps have chimed in.
Update: I was able to get my phone to work correctly, but only after completely disabling WiFi Calling. It seems something has broken in regards to WiFi calling. I have tried everything I can think of to get it to work with that option active. I don't use WiFi calling anyways, so no big deal for me, but still should not have happened to begin with.
To be honest, I haven't talked to anyone yet. But my stand by at night went from a 9 percent drain to about 3 percent. I haven't encountered any issues yet. I'm hoping it got rid of the audio hissing mine had sometimes and random audio anomalies in YouTube.
No fair
I have not rooted or anything. I had the update two days ago. Everything works fine with me. WiFi calling no problem.
gruiz3 said:
To be honest, I haven't talked to anyone yet. But my stand by at night went from a 9 percent drain to about 3 percent. I haven't encountered any issues yet. I'm hoping it got rid of the audio hissing mine had sometimes and random audio anomalies in YouTube.
Click to expand...
Click to collapse
Those were spin lock errors in the audio driver that were fixed in kernel upstream of 4.4.72-76 so it should have those fixes since it is 4.4.78.
It will still have some of the ipv6 latency spikes that randomly happen on web pages unless Moto cherry picked those net fixes from 4.4.97-106
The audio issues are somewhat solved. If the YouTube video is in the background, it's fine. But the audio hissing is still present if I'm watching the video. It's only in YouTube. I'm considering buying the Google usb c audio adapter to see if it's an issue with the proprietary moto audio protocol.
BeyondtheTech said:
For the uninitiated and those who just forgot, is there a dead simple way to install the firmware on a stock T-Mobile Z2 Force using a microSD card, or does it need to be done through ADB? I've already downloaded both files (the 900MB really long filename and the 2.3GB zip file) from the other thread.
Click to expand...
Click to collapse
I assume no. But to find the answer i think you should post in the oreo thread with the question. Few people have flashed orea on their phones so they should be able to answer your question.
So funny story... I own two of these tmobile devices... one stock, one unlocked and rooted. My stock device is still on august security patch and isnt receiving ota updates at all. So I called tech support cuz something is obviously wrong. first, they couldn't comprehend that I was talking about ANY update and not just Oreo... I haven't received OCT or Nov patches even... Then, since they were stuck on oreo what was interesting as the tech support people at Tmobile say that the latest release for our phone is 7.1.1 August patch... which we all know is wrong for several reasons. Needless to say I am not impressed with their tech department...
gruiz3 said:
To be honest, I haven't talked to anyone yet. But my stand by at night went from a 9 percent drain to about 3 percent. I haven't encountered any issues yet. I'm hoping it got rid of the audio hissing mine had sometimes and random audio anomalies in YouTube.
Click to expand...
Click to collapse
My standby drain has been the opposite. It's a little worse for me that in 7.1. I went from about 1-2%/hr in standby to around 5%/hr in standby. I've been off the charger for a little over 3 hours today with just 9 minutes of SoT and I'm at 86%. I'm not complaining, it's not bad, but before it was spectacular. Now it's just average.
I'm usually on wifi, that is my usual use scenario. I get around, no joke about 6 hours plus sot. As for my audio issues are still prevalent and now my netflix is a black screen all the time. But overall I'm still happy with the update. If I turn on power saver my standby time tanks lol. I think it turns off my wifi and tries to hold on to my one or two signal bars. I'm debating unlocking bl and rooting, but I really haven't felt a need. I'm probably alot more forgiving of the z2 issues due to I picked it up at 375.
Got mine

Categories

Resources