Related
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
Try this:
1. turn it off completely
2. press at the same time the power button (back side) and the two lower side buttons (bottom left and bottom right page)
3. it should start the recovery and restore your device to stock
Link: http://forum.xda-developers.com/showthread.php?t=1137967
Let us know if it works.
hi,
now i don't have the Nook available (i'm at office), but yesterday i was playing with ADB and having a look at nook system folders; i remember seeing a property file in which there is a property like demoMode=enable/disable or something like that (i'm not sure, but if i remember well this file should be in the same folder where also other device specific properties like serial number, mac address, etc.. are stored).
Until reading your message i didn't even know such a mode existed. But now i think that maybe it could be possible to edit that file and enable the "regular" mode on your Nook.
Of course, even if that is possible, you would need to get root and ADB access to to that, and there is the risk of bricking the unit (even though if you can create a backup image to be on the safe side).
When i'll be back home, i will try to find further info about the above mentioned file.
Regards
hi,
i don't know if you already solved, in any case i had a better look at the system folders of Nook, and it seems to me that the Demo Mode is managed by a dedicated application (/system/app/DemoMode.apk). Baksmaling the source code of this app, it seems that it is activated on any Nook unit after boot, but in case the value of setting "demo_mode" is not set to "on", it just exits without doing anything; on contrary, the demo mode is activated (i.e. the continuous loop through a set of images).
So, to get rid of demo mode is activated, you could launch a script to change the relevant value of the setting "demo_mode", to set it to "off"; and then reboot the Nook:
Code:
echo *************************
echo * Setting Demo-Mode off *
echo *************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value='off' where name='demo_mode';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Of course, to be able to launch it, you need to have your Nook already rooted, so that ADB is enabled.
The script is inspired from similar scripts present in the batch file "xe-autoroot.bat" from user xboxexpert of this forum. Therefore, in case you still don't have rooted your Nook, i suggest you to use its script to get it (link to the thread). In this case, you can easily launch the script to disable demo mode from the same folder where you have xe-autoroot.bat, since yu already have all the needed software (sqlite3).
Another possible solution could be just to remove DemoMode.apk from /system/app folder (but i'm not 100% sure this would have side effect).
In any case, not having a demo mode Nook unit, i cannot be sure these methods would work.
Hope this help
That doesn't work
When I have tried to root it I can't because I can not get to the menu to setup the wifi it won't let me get away from the screen saver my mom ordered one of these off ebay for like $40
Figured it out
If it is on an older version you can just drop the official firmware on your nook let it update and it worked like a charm
https://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
how to disable DEMO mode on Nook simple touch
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
a lot of time passed since other guys had a problem of demo mode on nook. i got my nook (simple touch) as secondhand, unfortunately locked to demo mode.
below is step-by-step how to switch it back to 'normal' mode >>>>>>
--- turn your Nook ON
--- go to Settings - Screen - on Screen window press-and-hold top-right button AND same time keep tapping the "Screen" caption (on a top of display)
--- Demo Mode will pop up on your display
--- undo 'Toggle the demo mode'
--- now to activate "normal" mode switch off-and-on your Nook !
that's It :good:
WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
+1 intrested to this. I have a lg g watch r.
In Cinema Mode i have Touch2Wake disabled but watch dont show anything and does not vibrate. It becomes really useless if it does not vibrate In Cinema Mode.
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
I am also searching for this:good:
I've been looking everywhere for a solution to this. I hasn't even considered it as an issue, but just a couple of days is enough to make me realise this is a requirement. I can't believe it didn't come up in development! Aside from your own accidental touches, there's also the issue of inquisitive fingers from children touching that nice shiny screen... Tapping the side button to wake the screen would be perfect (whilst retaining the monochrome screen and notifications).
Cinema mode is really dumb. Just very poorly thought out. There has got to be a way to disable touch to wake. Or even enable vibrating notifications in cinema mode.
Yes there is a way
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
adb root
adb push /system/usr/idc/sec_touchscreen.idc <choose where you want to have the file in your pc>
Click to expand...
Click to collapse
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
adb pull <where you have the file> /system/usr/idc/
Click to expand...
Click to collapse
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
adb pull <where you have the copy> /system/usr/idc/
Click to expand...
Click to collapse
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
dataonlycod said:
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
Click to expand...
Click to collapse
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
-RioT- said:
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
Click to expand...
Click to collapse
Yep you can use it to wake up the device. But as I say, make a backup because this happen with my alpha of the gear 2 neo, so probably this is not going to work with other devices. Just in case xD
Works for me on LG G Watch R
The file name is different "synaptics_rmi4_i2c.idc"
Same edit, copied to sdcard and moved in recovery to /system/usr/idc/ as mentioned above.
I have swipe menu still available and I can swipe down for the quick toggles.
Button is used to wake (and I use screen always on)
Going to be interesting how this performs in the shower and in general. Thanks to the suggestion posted.
Any update on this after using it for a while? Looking to apply this to my LG G watch R running the Urbane port.
Ok well i tried it any ways and i still have the problem when my arms are crossed my arm starts doing things on my watch...
Starting from version 1.6 this app supports wake on touch changing - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings (here is apk - View attachment AdvancedSettings-v1.6-11.apk)
I downloaded the advanced settings app tried the disable touch wake... it doesn't wake but you can still scroll notifications and long press to change the face.
Any chance of completely turning off the touch screen while in sleep...
..
castructuraleng said:
I tried the Advanced Settings app on my LG Watch Urbane 2nd Edition with Android 6.0.1, which is not rooted. It has an option for "Touch to wake screen" that I tried to set to "off"; however, when I go back to look at it, it is always set to "on". Do I need to root to have this stay, or is the app just not compatible with 6.0.1?
Update... just answered my own question. It appears you need to be rooted to do this.
Click to expand...
Click to collapse
Yep, it works on Marshmallow 6.0.1 when Rooted. Just tested it on my Huawei Watch.
..
I installed "Showear". You can set a simple touch pattern to unlock the watch. Crossing your arms will no longer trigger any action on your watch (except making the screen on).
..
..
Hi m8. I've done this on my LG urbane and works just fine ty a lot... but i modified a little your steps...
1) My lg urbane is rooted
2) I went to the ADB folder in my PC (using windows explorer) then using shift+right click i select "open command window here"
3) in this command window i did:
adb reboot bootloader
fastboot flash recovery (starts twrp)
in the TWRP:
Go to "Mount"
tick the "system" box
In the command window :
adb pull /system/usr/idc/synaptics_rmi4_i2c.idc (Dont need to select the folder, will appear in the ADB folder used to open the command window)***
*** When i tried to write the destination folder have not worked so i strongly advise not to fill this part, the command in the beginning is PULL not PUSH to take from the device and the file to be taken from the device had a different name as someone have stated before ***
4) In the notepad i did
I opened the file with the notepad and edit "touch.wake = 1" to "touch.wake = 0" (I did not delete this part just change the value)
5) in the command window:
adb pull <where you have the file> /system/usr/idc/
6) Reset my phone and works great!
After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.
Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102
After many sleepless nights, I found solution.
As we don't have in our stock ROMs System UI tuner, we can do this even without root.
First, you'll need ADB, USB debugging ON and Samsung Drivers.
ADB:
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip
- https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Turn on usb debugging from developer menu (tap build number 7 times to show developer settings menu)
Samsung Drivers
- http://www.devfiles.co/download/AbRa7wHc/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Connect your device via USB.
Open terminal (command prompt) inside ADB folder (hold shift and mouse right click on blank space)
write :
Code:
adb devices
You should see your phone listed as numbers. After that write:
Code:
adb shell settings put global heads_up_notifications_enabled 0
Restart your phone. Now your heads up notification nightmare has gone.
I FOUND A SOLUTION WITHOUT HAVING TO INSTALL ANY EXTRA APPS!
So we have all been getting the annoying heads up notifications that we don't want appearing on our phone when it's unlocked right?! Well I found a solution after playing round with my phone. First I changed the notification settings in my apps for example WhatsApp, Facebook messenger etc by going to settings > notifications > select each app you want to stop heads up from > allow notifications > show silently. Toggle this to on.
Now wait I've not finished, the go back into settings > accessibility > notification reminder and turn this on. Then turn sound on and vibrate on and select the apps you wish to receive notifications from. Then there you have it , this stops the heads up but then reminds you 1 minute later that you have a notification! I'm sure a 1 minute wait won't hurt to stop those heads up!
Yesterday I was searching a solution for my Note 5 and I didn't notice that it was the S7 edge forum.
I follow the tutorial step by step and it works very well too on my Note 5 SM-N920C NRD90M.N920CXXS4CRD1 (April 2018 release).
However, I do not know how to use this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip , what is it?
In my case I use the other link for ADB installation.
P.D.: may someone put this tutorial in Note 5 forum too? I think it will be useful.
Great, except your phone then beebs ever minute until you review the notification - which can be incredibly annoying.
Thank you for this!