Hi everyone! Sorry for my english.
My phone is good but 2 days ago my phone can't charging 100%. I trial lots of rom (miui, flyme, RR....) Only 96% and full battery notifications.
Somebody help me.
To fix not full charging execute the command from a terminal after su rm /data/system/battery* and reboot
by @droidBeam
NguyenCaoTuanAnh said:
Hi everyone! Sorry for my english.
My phone is good but 2 days ago my phone can't charging 100%. I trial lots of rom (miui, flyme, RR....) Only 96% and full battery notifications.
Somebody help me.
Click to expand...
Click to collapse
Good afternoon, my friend, I have the same problem, how can you make a tutorial to solve this problem? thank you
---------- Post added at 09:08 PM ---------- Previous post was at 09:05 PM ----------
aburezk said:
To fix not full charging execute the command from a terminal after su rm /data/system/battery* and reboot
by @droidBeam
Click to expand...
Click to collapse
Good afternoon, my friend, I have the same problem, how can you make a tutorial to solve this problem? thank you
same problem
Gilcomando said:
Good afternoon, my friend, I have the same problem, how can you make a tutorial to solve this problem? thank you
---------- Post added at 09:08 PM ---------- Previous post was at 09:05 PM ----------
Good afternoon, my friend, I have the same problem, how can you make a tutorial to solve this problem? thank you
Click to expand...
Click to collapse
x_not_full_charging (by Urmish - @droidBeam)
1. Install < Terminal Emulator for Android - Jack Palavich >
2. Open app
3. Type < su > (enter) and grant permission to use this app (need root)
4. Type < chmod 0755 /data/system/battery* > (enter)
5. Type < rm /data/system/battery* >
6. Reboot
And 1 more solution.
Open your phone and plug out battery jack and plug in.
NguyenCaoTuanAnh said:
x_not_full_charging (by Urmish - @droidBeam)
1. Install < Terminal Emulator for Android - Jack Palavich >
2. Open app
3. Type < su > (enter) and grant permission to use this app (need root)
4. Type < chmod 0755 /data/system/battery* > (enter)
5. Type < rm /data/system/battery* >
6. Reboot
And 1 more solution.
Open your phone and plug out battery jack and plug in.
Click to expand...
Click to collapse
Thank you my friend, I'll test here to see if it will solve
NguyenCaoTuanAnh said:
x_not_full_charging (by Urmish - @droidBeam)
1. Install < Terminal Emulator for Android - Jack Palavich >
2. Open app
3. Type < su > (enter) and grant permission to use this app (need root)
4. Type < chmod 0755 /data/system/battery* > (enter)
5. Type < rm /data/system/battery* >
6. Reboot
And 1 more solution.
Open your phone and plug out battery jack and plug in.
Click to expand...
Click to collapse
well, unfortunately with me it did not work, I did the whole procedure, but my battery is still no more than 97%
Gilcomando said:
well, unfortunately with me it did not work, I did the whole procedure, but my battery is still no more than 97%
Click to expand...
Click to collapse
I'm not sure if you have same situation as I've had before.
After flash my R5P with custom ROM, I start facing the charging issue, stuck at 98% but the lockscreen info mentioned "charged". First thing I did is switching OFF my phone with charging cable still plugged-in. I wait for few minutes to continue the charging until it reach 100%, then switch ON the phone and I got my phone fully charged 100%, then pull off the charging cable.
But it was not finish yet, after normal usage got 8h++ sot, at 25% level the phone suddenly OFF. Couldn't switch ON, totally no power left in the battery. I can tell no power left because when I charged the phone, I need to wait few minutes with empty black screen until I got the green battery charging indicator shown 1%.
After few hours the battery fully charged again 100%. But then suddenly OFF again at 25% level, same thing as before.
Then charged the phone again, when it reach full 100% I did the battery calibration (you can get the apps from playstore). After normal usage the phone suddenly OFF again at 22% battery level.
Then I redo again the fully charged and calibration. Then after the 2nd fully charged+calibration, charging could reach full 100% and no more sudden OFF, I could reach 1% level.
I'm not sure what might causing this, battery stat?
Actually I was thinking to revert back to stock MIUI, to make sure that it was not battery hardware issue. Anyway it's ok now, so no need to do that.
still 90% i think it should replug battery connector
Yup, confirmed, after reconnect battery from modul, it show 100% again..
I am on miui.am
And im use big opener (pry tool) for easy way to open back case.
gandrigoes said:
Yup, confirmed, after reconnect battery from modul, it show 100% again..
I am on miui.am
And im use big opener (pry tool) for easy way to open back case.
Click to expand...
Click to collapse
OT but what theme are you using?
Lightracer said:
OT but what theme are you using?
Click to expand...
Click to collapse
Nova Launcher
Another Widget
yitax icon pack
Is that really work??
NguyenCaoTuanAnh said:
x_not_full_charging (by Urmish - @droidBeam)
1. Install < Terminal Emulator for Android - Jack Palavich >
2. Open app
3. Type < su > (enter) and grant permission to use this app (need root)
4. Type < chmod 0755 /data/system/battery* > (enter)
5. Type < rm /data/system/battery* >
6. Reboot
Click to expand...
Click to collapse
Works perfectly! Thanks!
NguyenCaoTuanAnh said:
x_not_full_charging (by Urmish - @droidBeam)
1. Install < Terminal Emulator for Android - Jack Palavich >
2. Open app
3. Type < su > (enter) and grant permission to use this app (need root)
4. Type < chmod 0755 /data/system/battery* > (enter)
5. Type < rm /data/system/battery* >
6. Reboot
And 1 more solution.
Open your phone and plug out battery jack and plug in.
Click to expand...
Click to collapse
Hello, did all commands but on the last command rm /data/system/battery* it return this error "/data/system/battery-saver is a directory"
Lineage 16 Pie
inouext said:
Hello, did all commands but on the last command rm /data/system/battery* it return this error "/data/system/battery-saver is a directory"
Lineage 16 Pie
Click to expand...
Click to collapse
The crucial file to delete is "/data/system/batterystats.bin". If that was deleted, then you can ignore the error message.
DarthJabba9 said:
The crucial file to delete is "/data/system/batterystats.bin". If that was deleted, then you can ignore the error message.
Click to expand...
Click to collapse
Thanks.
I deleted the "batterystats.bin" with a app (root) but it did not work.
I think my only solution is to open the phone and re-connect the battery?
Or has anything that i can do?
inouext said:
...Or has anything that i can do?
Click to expand...
Click to collapse
Plug in the charger, turn off the phone, with the charger still plugged in, and leave it to continue charging while turned off for about an hour. Then remove the charger, and turn on the phone.
DarthJabba9 said:
Plug in the charger, turn off the phone, with the charger still plugged in, and leave it to continue charging while turned off for about an hour. Then remove the charger, and turn on the phone.
Click to expand...
Click to collapse
The problem is even with the phone off it stucks on 96% 97%
The only way that i found to charge past 96% 97% is to enter in recovery (orangefox).
While in recovery it charges without issue to 100%
inouext said:
The problem is even with the phone off it stucks on 96% 97%
The only way that i found to charge past 96% 97% is to enter in recovery (orangefox).
While in recovery it charges without issue to 100%
Click to expand...
Click to collapse
Hmm ... I'm not sure why OrangeFox is able to bypass that problem!
Related
Trying to wipe battery stats with terminal emulator, get the following:
$ $ rm failed for /data/system/batterystats.bin, no such file or directory
Verified in root explorer that directory is there but not the file. CWm battery stats wipe doesnt work either.
-50 PBJ, UK 2.0 with ec09 radio.
any suggestions on how to wipe the battery stats ? performance has been lacking since the UK upgrade, radio change didnt help.
Two ways: manually wipe in cwm, or download battery calibration from the market. Both do the exact same thing.
Also, from your terminal command, you tried to do it without superuser access. Type "su" first, then hit enter.
Sent from mah Fascinate using XDA Premium App
Thanks, i did try it with su, but it failed to reboot. Just goes back to a prompt, #.
Also tried in cwm, blank response. I do have cwm red if that matters.
Sent from my SCH-I500 using XDA App
The # sign means the next command will be executed with root access, so try your original command again at the # prompt.
Sent from mah Fascinate using XDA Premium App
I experienced that in Terminal Emulator as well. However, it appeared to work fine in CWM.
I just got an update for the Terminal Emulator software and tried again but still get a return to the # prompt with no reboot. It *used* to work just fine - it was just since loading UKB 2.0 -50 PBJ that it didn't.
---------------
Did some Googling --- Try this:
For Terminal
1. open terminal emulator, press menu button, then preferences
2. scroll down to "shell" and changed initial command to read
"export PATH=/system/xbin: $PATH
3. press back button, Terminal will close, reopen terminal
4. type "su" hit return, grant su when promt pops up
5. type "bstats" and hit return
6. phone will reboot.
Found it here.
Yup, I see the same thing........was working fine with the reboot under commavolt, quite working only after the switch to PBJ -50
Tried the instructions above, no reboot. Acts the same as if I copied and pasted the extracted bstats commands like I used to do. ( back to # prompt)
pokey9000 found in the kernel, drivers/accessory/30pin_con.c:
if (acc_adc != false) {
if ((2600 < acc_adc) && (2800 > acc_adc)) {
env_ptr = "ACCESSORY=OTG";
acc->current_accessory = ACCESSORY_OTG;
Which he used to figure out what was needed to put the unit into Host mode and through his help and testing I figured out that you needed a 3:1 split on the power to get the unit to think it was charging from an OEM charger.
Is it possible to change the above code and whatever the other code is that senses power on the data lines so that we can force the tablet into whatever mode we want?
I don't have the proper setup to code myself so I hope there might be a Dev out there up for the challenge.
This works, it not only allows usb charging from a computer/laptop, but it enables it to be charged from any (In my case my Kindle's wall plug.) wall plug.
Hope that helps!
FillTheVoid said:
I am having trouble with command
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Works fine from my Laptop, but when in a terminal on the tab I get
adb shell
error: device not found
I did give the terminal su permission. Anything special I have to do when running this script from the tab itself. I would like to be able to do this "on the go" since it is not persistent after reboot. Thanks.
Click to expand...
Click to collapse
Mullicious said:
You can make it persistent, slap it in a bog standard text editor, then by using script manager, create it as a script to run as root and at boot. Confirmed it to work myself, very handy.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Edit:
I see this doesn't answer your question, I'm sorry; misread.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A
Could someone put this into a package or give detailed instructions for a noob like me to get this running? I really hate that the Tab doesnt just recognize car usb power like my galaxy phone does...Thanks!
Mullicious said:
This works, it not only allows usb charging from a computer/laptop, but it enables it to be charged from any (In my case my Kindle's wall plug.) wall plug.
Hope that helps!
Edit:
I see this doesn't answer your question, I'm sorry; misread.
Click to expand...
Click to collapse
D you mean this command works:
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Did you get it to work from terminal eventually?
Can you share the script you created please?
Szadzik said:
D you mean this command works:
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Did you get it to work from terminal eventually?
Can you share the script you created please?
Click to expand...
Click to collapse
This shell command works if you are running pershoot's kernel, it is not persistent after reboot though. This doesnt bother me cause if I really need to charge it in the car I just open a terminal emulator and type in in. Takes 30 sec.
FillTheVoid said:
This shell command works if you are running pershoot's kernel, it is not persistent after reboot though. This doesnt bother me cause if I really need to charge it in the car I just open a terminal emulator and type in in. Takes 30 sec.
Click to expand...
Click to collapse
SO it does not work on stock kernel?
Szadzik said:
SO it does not work on stock kernel?
Click to expand...
Click to collapse
That is correct. Pershoot built it into his kernel.
FillTheVoid said:
That is correct. Pershoot built it into his kernel.
Click to expand...
Click to collapse
Any idea if Pershoot's kernel is available for P7500?
Szadzik said:
Any idea if Pershoot's kernel is available for P7500?
Click to expand...
Click to collapse
It is available. That's the 3G model right?
FillTheVoid said:
It is available. That's the 3G model right?
Click to expand...
Click to collapse
Yes, it is 3G. I have to look for the right thread. LEt me know if you have any pointers.
Szadzik said:
Yes, it is 3G. I have to look for the right thread. LEt me know if you have any pointers.
Click to expand...
Click to collapse
See forum.xda-developers.com/showthread.php?t=1138167
Hello all!
I realize that many many Android users have that issue and don't get any satisfying answer.
Let me introduce you my own experience. This may help and clear things up about Android safe mode.
It started one week ago when I got into a party and the barman threw lots of water at my friends and me. When I went to bed I didn't bother dry myself up, went straight to bed and slept.
When I woke up the next morning (with such a bad headache by the way ), my phone was acting really weird :
1 : it couldn't recognize my SIM card or any SIM card
2 : the little textbox "Safe Mode" had appeared
3 : My Volume up/Volume Down buttons weren't working anymore.
I rebooted the device several times, wondering why would it do that to me!! I googled that all day to understand what was happening to it.
All of the sudden, after a reboot, the Sim Card was recognized again and this problem was fixed. Yay!
Then, I tried all I could about the buttons (opened the device with youtube tutorial and a Torx screw driver T5) tried to clean the volume flex cable, dry it... Nothing to do.
The volume buttons still not responding, safe mode still here.
There are several reasons for safe mode to show itself :
-Holding a button while booting (depending on the device and manufacturer) : simply reboot the device to get back in normal mode.
-A previously downloaded and installed app is causing issues on the device (Android self protection) : you'll need to find that app and uninstall it to get back in normal mode.
-I ran into a forum where someone was explaing how changing one of his internal components that wasn't working anymore fixed his safe mode problem (mostly non responding buttons like my phone).
So I ordered a brand new volume flex cable for my HTC sensation and I am still wating for it (long delivery...) I'll let you know as soon as I replace the component if that has fixed it.
The problem is : in the meantime I just can't access non system apps (in other words : all origin apps, no others). I bought a smartphone to be able to do many more things on it than just call, text message or email...
So I found a solution about it (I am going to test it tonight and will let you know) :
You need to have a rooted device in order to install all apps that you need to run, even though Android is running under safe mode, into /system/apps location. This will "make believe" those apps are actually system apps and will force your device run them at boot.
How does this work?
You need to get ADB tool in order to push command shell to the device (because terminal emulator or other apps that ease root commands directly on the device can't be loaded... Thanks safe mode!!)
!!!!! Important !!!!!!! I haven't tested this myself yet but will tonight and will let you know on that thread, so watch it before doing anything you wouldn't understand.
from Adb terminal you'll need to get into the system partition and mount it as read and write :
adb shell
su
mount -o remount,rw /dev/null /system
give everyone permissions to write in that folder :
chmod 777 /system/app/
Then, you'll need to store the apks you need into your sdcard (wherever).
Then, copy all apps you need into the folder :
cp -a /sdcard/[pathtoyourapk/theapkyouwanttoinstall] /system/app/
reset the permissions on that folder :
chmod 755 /system/app/
mount -o remount,ro /dev/null /system
sync
Reboot the device :
reboot
You're done.
Don't hesitate correct me if I gave any wrong information, but trust me, I spent enough time on this problem to get self confident and write in here.
Thanks for your attention!
Regards!
Adding information
I tested it and it does work.
However I forgot something :
Once you've copied your apk into the system\app folder just chmod it with 644 :
chmod 644 /system/app/[yourapp.apk]
This will give the system and yourself access grant to the application.
There! =)
21.03.2014 RELEASE #4 UPDATE
Here is first ever CM for LG D605 (Optimus L9 II).
This is unofficial ROM and might have some serious faults, if this breaks your phone or they fire you from your job because alarm didn't start it will be your own fault since you have installed it. You have been warned!
The installation procedure was tested with unbranded phone (OPEN_EU variant). This might not work with branded ROM (but it would be good if someone check it).
Sources can be found at:
https://github.com/Varcain/android_kernel_lge_d605
https://github.com/Varcain/android_device_lge_d605
Things that don't work and won't be included in this ROM by default (possible enable by porting stock apps):
- FM radio
- IR port
Things that I already know that don't work at all or are bugged:
- NFC (no support at all yet)
- Manual service network selection (only auto supported right now)
- SIM card contact/SMS reading
For best battery life keep bluetooth off if you are not using it. It will keep constant wakelock if left on right now
NEWEST RELEASE #4
- Added USB tethering
- Added Bluetooth tethering
- Working move to sd-card function (but MTP on internal memory is disabled, external SD card is now mandatory)
- Vibration patterns tuning
- Correct WLAN and Bluetooth MAC addresses should be used now
CHANGES FROM RELEASE #3
- Fixed first call with no voice bug
- Fixed incoming call volumes
CHANGES FROM RELEASE #2
- Fixed voice call volume
- Fixed mute microphone option during calls
NEWEST ROM RELEASE #4:
d605_cm10_v4.zip - 164.61 MB
GAPPS:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Old releases:
release #3:
http://d-h.st/Zr4
How to install:
1. Flash CWM (from here: http://forum.xda-developers.com/showthread.php?p=50407619)
2. Download the ROM and gapps to sdcard
3. Boot to recovery
4. Wipe all userdata
5. Install CyanogenMod first then gapps
6. Reboot.
Now wait for CM to boot... (first boot will take longer as always).
For reporting bugs/problems:
- Send me logcat output (it would be good to have "logcat -b radio" output too if this is related to sim card/radio)
- Send me dmesg output
If you experience reboot (kernel panic most likely) then send me contents of /proc/last_kmsg (you have to copy this right after reboot, you can do it from terminal application if you don't have access to PC with adb at that time).
Reserve for info.
Thanks Varcain!
Beginning installation right now.
----------------------------------------EDIT---------------------------------------------
Help: http://forum.xda-developers.com/showpost.php?p=50007962&postcount=318
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
TaZRAge said:
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
Click to expand...
Click to collapse
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
How to install:
Unzip contents, boot your phone to stock ROM, connect via USB with USB debugging mode on, install adb (if you don't have it yet), then adb push all unzipped files to /data/local/tmp (for example adb push ./system.tar /data/local/tmp). After that enter adb shell, issue "su" command and:
# cd /data/local/tmp
# chmod 777 clear_partitions.sh
# chmod 777 loki_flash
# chmod 777 system_update.sh
# mkdir mntpoint
# ./clear_partitions.sh
# ./loki_flash recovery rom.lok
# ./system_update.sh
After that locate your unzipped gapps and do the following (I assume gapps are unzipped directly in /storage/external_SD/Download
# cp -r /storage/external_SD/Download/system/* mntpoint/
# sync
# reboot recovery
Click to expand...
Click to collapse
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/sdcard1/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Varcain said:
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/external_SD/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Click to expand...
Click to collapse
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
TaZRAge said:
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
Click to expand...
Click to collapse
I made a typo, try /storage/sdcard1 instead of /storage/external_SD.
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
TaZRAge said:
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
Click to expand...
Click to collapse
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Varcain said:
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Click to expand...
Click to collapse
reinstalled everything
maybe I gona set up a dualboot on my PC too =)
made 2 screenshots from my adb shell with wel.... rare behaviour
but now it worked!
i have Gapps
Not rare behavior at all! You forgot Download directory in first screenshot and in second one it looks fine to me.
Varcain said:
Not rare behavior at all! You forgot Download directory in first screenshot and in second it looks fine to me.
Click to expand...
Click to collapse
*headpalm* no wonder it did not work
Well whatever.... that is one fine port =)
I am only missing my apps i installed via the amazon appmarket =D
And since its not really a ROM for daily use i will not install everything i have in my stock ROM
---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------
Varcain said:
Just use the ROM like you normally would, compare with stock and if you find some anomalies report it in my ROM's thread, I will add them to bug list and hopefully fix in next release.
you can save logs to sd card and then load them from PC connection (I turned off MTP setting by default so it wont be detected as MTP device for file transfers, you need to turn it on in settings>storage>press menu> select MTP).
To do this from console app in phone:
logcat -d > /storage/sdcard1/logcat.txt
logcat -d -b radio > /storage/sdcard1/logcatradio.txt
dmesg > /storage/sdcard1/dmesg.txt
cat /proc/last_kmsg > /storage/sdcard1/lastkmsg.txt
Click to expand...
Click to collapse
This should be in here too!
And by the way, after activating MTP in the ROM i can use adb shell at my computer again!
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
TaZRAge said:
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
Click to expand...
Click to collapse
Settings>Launcher>Homescreen>Homescreens
TaZRAge said:
*headpalm*
Click to expand...
Click to collapse
Thanks again
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Varcain said:
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Click to expand...
Click to collapse
Works this way!
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
I connected my BT stereoheadset to listen to some music that doesn't sound like coming out a can....
Music via BT is no fun with this right now
I'm sitting next to my phone and the music comes interruptedly and sometimes with crackling sounds.
Gets even worse when i begin to experiment with the equalizer.
Next song comes flawless.... Ah display got disabled.
Screen back working and interruptions are back.
Controlls work perfect as i am used to (volume up + down + start/stop + next song + previous song do what they are supposed to do).
BT Speed to slow?
Disabled GPS now its better again.
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Varcain said:
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Click to expand...
Click to collapse
I tested it with stock many times before. Without problems like these.
And its sure I am in a radio-noisy environment. Around here are 4 wifi nets and the one i am in has 3 repeaters.
I had BT disabled on my computer during the test.
I will test it with a cable headset today, I don't have another BT headset.
Yet i had no other problems, bugs or errors!
Just install it!
First impression is VERY GOOD!
I think is faster than stock rom.
Minor problems with installation.
GApps works ok.
Known problem with camera.
Play some games, all run ok and FAST.
I think battery goes faster.
Install some themes, minor problems.
Basic Bluetooth ok.
That's all for now. I will play more later.
Thanks a lot Varcain! :victory:
I will upload new build in a moment and update the OP with it. There is major bug in first alpha release which causes constant wakelock (so the phone never goes into deep sleep). I managed to debug and fix it, please install new version.
Hello everyone.
This is a guide to enable the Photochrom camera without using a PC.
Steps:
1. Install Termux - https://play.google.com/store/apps/details?id=com.termux&hl=en&gl=US
2. Run this command on Termux:
apt update > /dev/null 2>&1 && apt --assume-yes install wget > /dev/null 2>&1 && wget https://github.com/MasterDevX/Termux-ADB/raw/master/InstallTools.sh -q && bash InstallTools.sh
Wait for a while and let this command complete. (Needs internet connected)
3. Run this command in Termux:
adb devices
4. Go to developers settings. We need to change 3 settings:
First turn all of them off:
a) Wireless debugging
b) Wireless ADB debugging
c) USB debugging
Now you have to turn them on in this order (Yes the order is important)
a) Wireless debugging (Also click allow on prompt)
b) Wireless ADB debugging
c) USB debugging (Also click allow on prompt)
5. Go back to Termux and type:
Adb devices
You phone should show up with the IP
6. In termux run:
Adb shell
and then run:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
CONGRATS!! The camera runs now.
Change camera to camera 4. This is the photochrom camera.
Now go to recent apps and lock this camera app.
Now you never have to worry again.
This app will always be available in recent apps.
EXTRA STEP. If "adb shell" command does not run.
You need to do one extra step after step 5
5.5. If your ip is 192.168.2.3:5555
run this command
adb connect 192.168.2.3:5555
then do step 6
DOESN'T WORK?
Uninstall Termux and repeat procedure again. Follow the video attached.
VIDEO TUTORIAL
For Video Tutorial please follow the link
2020_12_06_19_06_32.mp4
drive.google.com
Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?
Zokinet said:
Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?
Click to expand...
Click to collapse
You stock camera will not be changed
This works fabulous on OnePlus 8 pro IN2021 running Android 11.0.2.2 thanks again.
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
iamtalha said:
You stock camera will not be changed
Click to expand...
Click to collapse
Thanks, All works good.
Good job.
I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...
Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post
GatorsUF said:
I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...
Click to expand...
Click to collapse
Please check the video I just attached.
Good video : cheers
Awesome, this works fine on OOS 11 stable. Thanks a lot.
Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
You need to disable all your magisk modules to use it.
Tried, no x ray effect
I am not even rooted
Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse
iamtalha said:
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post
Click to expand...
Click to collapse
Will it work on oos 10?
Rajul said:
Will it work on oos 10?
Click to expand...
Click to collapse
Not sure. But it should
Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse
Xray effect is very slight. It is just hyped
OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!
oSumAtrIX said:
OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!
Click to expand...
Click to collapse
Yes this method was for non rooted phones. Rooted phones have other better methods
For anyone trying this on OOS 10, it will not work for non rooted oos 10 as the factory mode feature was disabled by OnePlus in latest Stable update but it works for OOS 11 stable.(as of now)
iamtalha said:
Xray effect is very slight. It is just hyped
Click to expand...
Click to collapse
Well this guide does work for me 11.0.2.2 BA but the hype i had was big lol