please help me frnds
i have a sgs i9000 with RS rom
witch takes long to boot i thinks when i root it or i dont know
so at every time when i run the hp it takes 1~2 mins in mackay kernel screen
and 3~3½ min on boot screen
i already test the stock rom and full wipe
aiting for internal mmc...
Reading all physical volumes. This may take a while...
Found volume group "lvpool" using metadata type lvm2
2 logical volume(s) in volume group "lvpool" now active
LED settings is CMLED
Current active LED settings is CMLED
lights.aries.so doesn't need to be updated
Navbar setting is DISABLED
Current active navbar settings is DISABLED
Navbar doesn't need to be updated
Low RAM setting is DISABLED
Current active low RAM settings is DISABLED
Low RAM settings doesn't need to be updated
umount: can't umount /sdcard: Invalid argument
1972 blocks
cleaning up...
Segmentation fault
i found this in /system/boot.txt
and i think that format ing the internal sdcard fix my problem
Hi guys,
i have a problem. I did execute the mtknoled.apk becoause oft some battery issues.
And the result was not gold, because my battery Problem still was not fixed, and the notification light was disabled.
Now I want my led notification work again.
Can someone help me out, with an apk which enables the led again?! Would be great!
THX in advance
Not sure if this is still needed but here's what worked for me:
1) install and launch Minimal ADB and Fastboot;
2) once the phone is connected and recognized, execute
Code:
adb shell settings put system notification_light_pulse 1
You can verify the result with:
Code:
adb shell settings get system notification_light_pulse
It will give "0" if disabled and "1" if enabled.
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Sigosuuu said:
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Click to expand...
Click to collapse
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Davey126 said:
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Click to expand...
Click to collapse
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Sigosuuu said:
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Likely an app. You will need to use a tool like GSAM or BBS to identify the culprit.
My Apollo HDX behaves similarly, and has since I got it (refurbished) six months ago: very shortly after going into screen-off mode, a reboot occurs.
This happened under the stock 4.5.5.2 OS, but seemed to be mitigated if I set it to keep wifi on during sleep.
Under LineageOS 14.1, however, it reboots whether that option is enabled or disabled.
I've tried several times to see if anything interesting appears via wireless logcat, but nothing is terribly obvious. Here's the last attempt:
Code:
07-03 01:59:19.246 1157 1234 E WifiHAL : wifi_error acquire_supported_features(wifi_interface_handle, feature_set *): requestResponse Error:-95
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.248 1567 1567 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-03 01:59:19.257 1157 1540 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-03 01:59:20.383 544 884 D audio_hw_primary: out_standby: enter: stream (0xb624ab00) usecase(1: low-latency-playback)
07-03 01:59:20.489 544 884 D hardware_info: hw_info_append_hw_type : device_name = speaker
After that, the device no longer pings as it has begun restarting.
Using Wake Lock (https://play.google.com/store/apps/details?id=eu.thedarken.wl), I found certain combinations that would prevent reboots when the screen goes off:
wifi on, wakelock WIFI_MODE_FULL_HIGH_PERF => ok
wifi on, wakelock WIFI_MODE_FULL (or less) => *restart on sleep*
wifi off, wakelock PARTIAL_WAKELOCK => ok
wifi off, wakelock WIFI_MODE_FULL_HIGH_PERF (or less) => *restart on sleep*
airplane mode, no wakelock => ok
Seems almost like some sort of hardware/driver issue.
Offline Charging :- When charger is connected to switched off device, it boots the device into offline charging mode and charging bootanimation comes. System is triggered into normal boot by holding the power button.
But am trying to build a kiosk device using Redmi 4A and cannot have user interaction. Thus need to override this offline charging so that device automatically boots into normal mode when connected to charger.
DEVICE IS ROOTED
I have followed all the methods suggested throughout the web --
fastboot oem off-mode-charge 0 -- NOT WORKING
/system/bin/lpm , /system/bin/charge_only_mode, /system/bin/kpoc_charger, /system/bin/chargemon or any other related file -- NOT PRESENT
https://appdictive.dk/blog/android/how-to/2017/04/20/disabeling_offline_charge_on_android/ -- tried this tutorial, but device gets stuck in bootloop.
The link in the last point, provides several options. I found this in my init.rc file -->
Code:
# Healthd can trigger a full boot from charger mode by signaling this
# property when the power button is held.
on property:sys.boot_from_charger_mode=1
class_stop charger
trigger late-init
...
...
on charger
class_start charger
As suggested, I modified the on charger trigger to contain the same code used to boot in normal mode when power button is held -->
Code:
on charger
class_start charger
class_stop charger
trigger late_init
This leads to bootloop i.e. device gets stuck on start screen and doesn't enter into normal boot. Couldn't find out the reason for same.
Tried increasing the log level 8 of init and checked adb shell dmesg, but no sign of where booting crashes.
Can anybody suggest remedy or any other alternative to disable offline booting.
Do u find any solution ????
Removed
moto actions?
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
KamiGooDz said:
moto actions?
Click to expand...
Click to collapse
Yes, it's available
snapchat don't work, how fix?
Update
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
FpX said:
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
Click to expand...
Click to collapse
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
KamiGooDz said:
snapchat don't work, how fix?
Click to expand...
Click to collapse
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
AsD Monio said:
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
Click to expand...
Click to collapse
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
anybody tested nin moto g5S xt1795 indian edition
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:28 AM ---------- Previous post was at 07:26 AM ----------
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
anybody tested in moto g5S xt1795 indian edition ?
FpX said:
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
Click to expand...
Click to collapse
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
AsD Monio said:
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
Click to expand...
Click to collapse
I was using the previous build, now it's working perfectly, thanks!
Update
aicp_montana_o-13.1-UNOFFICIAL-20190121
Changes
Enforcing SELinux
Download: http://www.mediafire.com/file/hquz82ge8werfgf/aicp_montana_o-13.1-UNOFFICIAL-20190121.zip/file
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
newinnov said:
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Click to expand...
Click to collapse
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
AsD Monio said:
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
Click to expand...
Click to collapse
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.
Flashed it om my wifes phone yesterday, she's very happy, less battery drain and wifi is better, which was the main reason to try a custom rom.
Thanks guys!
Hi, is Fingerprint, camera photo/video recording, and Moto display notifications working good ?
Thank´s
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
SvenHee said:
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
Click to expand...
Click to collapse
I had that happen to me as well, it's not the ROM's fault. Either fastboot or the stock recovery store some data in the /misc partition. That tells the bootloader/kernel to boot to recovery by default. It's probably meant to ensure that a partially upgraded system does not get booted while flashing a stock ROM. To fix it just wipe the /misc partition, I recommend making a backup first. I used dd in the terminal in TWRP for both operations (adb shell will work as well but it has some problems with displaying some characters in the Windows command prompt). To back up the partition:
Code:
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
^ (replace "external_sd" with "data/media/0" to save it in the internal storage instead of the external microSD card)
To wipe /misc:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
It may also work using fastboot, though I have not tried this way:
Code:
fastboot erase misc
Thanks!
That is slightly intimidating to execute but I'll give it a go!
aicp_montana_o-13.1-UNOFFICIAL-20190116
My device : xt1799-2
64bit os.
VoLte works for my xt1799-2.
Bugs:
1. Can't copy any file from the device to my PC. The same bug in crDroid 8.1.0 rom. And lineageos. This happens in all the third party rom between 8.1.0-9.0. Date at least before 2019-09-23. But can copy the folder from the device. But also can send file to the device, so weird.
________________________________________________
I see the lineageos 15.1 changelog:
2019-09-23:
September security patch
Optimized SEPolicy
Fixed MTP (thanks to @wiktorek140)
We're back to LTE
________________________________________________
But can copy the folder from the device. But also can send file to the device, so weird.
2. Front camera doesn't work.
3. Fingerprint doesn't work.
4. Delay a lot when you scroll the page, or move the app icon. The same bug in crDroid 8.1.0.
5. Call recorder. If you don't open the speaker, the inner voice recorded from the other side is too small, unable to hear it clearly.