Related
Hey all,
Very, very new to the forums (and I'm putting this here as I can't seem to add to the Dev forum thread) but I just wanted to pop on and report a critical bug I found after installing Salty Bean 4.2.1 (02/01/13 build).
I installed an app called LBE Privacy Guard onto my sgh-i896, gave it SU permissions and immediately the phone died. As in power off. But not quite, I couldn't reboot -- I had to pull the battery in order for it to boot again. After that rebooting worked fine... until LBE auto-loaded after boot -- at which point the phone powered down again.
I booted into Recovery and used the file manager to delete the .apk and that fixed the problem.
Also, apparently flash doesn't work (though I see there may be a patch available so I'll try that out and report back).
Thanks everyone for these incredible forums and thanks to dave71670 for this fantastic ROM.
Cheers!
Brandon
BCLaraby said:
Hey all,
Very, very new to the forums (and I'm putting this here as I can't seem to add to the Dev forum thread) but I just wanted to pop on and report a critical bug I found after installing Salty Bean 4.2.1 (02/01/13 build).
I installed an app called LBE Privacy Guard onto my sgh-i896, gave it SU permissions and immediately the phone died. As in power off. But not quite, I couldn't reboot -- I had to pull the battery in order for it to boot again. After that rebooting worked fine... until LBE auto-loaded after boot -- at which point the phone powered down again.
I booted into Recovery and used the file manager to delete the .apk and that fixed the problem.
Also, apparently flash doesn't work (though I see there may be a patch available so I'll try that out and report back).
Thanks everyone for these incredible forums and thanks to dave71670 for this fantastic ROM.
Cheers!
Brandon
Click to expand...
Click to collapse
Based on what I just read about that app, it is the one causing the bootloop and has nothing to do with Salty Bean.
you might take a look in your etc/init.d folder for any scripts the app left behind. Init.d scripts can bork things up before your phone finishes booting.
Ok So.. I am using my HTC One for almost a year now, when I came across this xposed frame work and xblast module, and I got so so excited after reading this, that trust me the sole reason for Rooting my HTC One was to be able to use xblast.
I rooted my HTC One, successfully, and installed xposed framework successfully as well, Installed xblast and did all sorts of modifications like, changing carrier text, wifi signal color, battery color, mobile signal color and couple of others and did a reboot, and to my surprised and much to the anticlimax to my excitement NOTHING worked not even one change happened ... ... I was like in tears ... ..... well check and re checked everything, and tried a hard re boot and still nothing.
I then noticed if I go in to xposed framework, it says the latest version of xposed is not active and I have like red "42" in front of app_process.
Searched xda and came to conclusion that you have to manually or automatically (what ever works) have to install the xposed framework file.
I tried the below files from THIS thread
cwm-Xposed.Framework.Installer.v2.3.1.zip
cwm-Xposed.Framework.Installer.v2.4.1.zip
Version 2.4.1 if I install by going in to recovery mode, the phone does not boot at all and gets stuck at HTC Logo screen, I have to then go to recovery and load the " Xposed-Disabler-Recovery.zip " to be able to boot.
Version 2.3.1 if I install I am able to boot BUT it still says the latest version of xposed is not installed. and its all red in front of app_process.
Searched XDA AGAIN and some post suggested that do a manual install and when in recover install the xposed-installer-recovery.zip from Android/data/de.robv.android.xposed.installer/files BUT doing this again does not let my phone boot and I am stuck at HTC Logo till the time I re boot to recovery and run the Xposed-Disabler-Recovery.zip
I am using a rooted HTC One M7 with Android 4.4.2 and HTC sense 6 with Nova Launcher ..
Friends as you can see I have done every part of my own trouble shooting and have read like gazillions thread on XDA and tried out every possible thing I can think off.
I believe I now have the right to start a thread and ask for help officially ....SO PLEASE HELP ...:crying:
Hi Friends, any one on this, I could really use some help and guidance here ....
Have you tried to reinstall xposed? Deinstall the app and reinstall everything? What about root access? Have you granted xposed root access?
Use the latest version (2.6.1) and flash Xposed from the recovery. We can't help you if you're using an old version (2.4.1).
(FYI, the installer would've told you to do exactly that if you just used the latest version.)
OK OK wait I did some more reading, mean time I was waiting for a reply here, and did some troubleshooting, it seems the S-On was the culprit ....... I had to use firewater to get S-OFF even that was not straight as I was getting some error. I then had to flash kernal Bulletproof and then use firewater to have S-OFF.
Anyway with S-OFF I finally was able ti have Xposed framework all green. BUT BUT xblast which was the sole purpose of the entire saga, messed up my phone like anything. I loaded Xblast module and again did all sorts of changes, and re booted, ...
Here goes my experience ...
1. It took a truck load of time to boot,
2. Then when I finally saw the desktop screen, my carrier signal was off, No signal what so ever ...
2.1 BTW I was able to see few xblase changes like my name on the status bar.
2.2 Crashed few apps like DS Audio and lastfm
3. Even before I could think to proceed I started getting this message "com.android.phone has stopped unexpectedly" repeatedly, again n again. I kept on pressing Dont send but the message would not go.
4. I rebooted again and same behavior the message simply would not go, plus no signal.
5. What I finally did was somehow go in to xposed framework and uncheck xblast and rebooted
6. Finally I was able to boot with everything back.
Good new is atleast Xposed Framework is working with all Green. Xblast didnt and is checkedoff
BTW xblast version is latest (AFAIK) ...1.8.7
Any suggestions steps the gurus here can recommend to have xblast working.
Mean time will try some other modules like BubbleUPnP (Audio cast) , sense 6 tools etc and report ...
Thanks for all the help and guidance
This is the wrong place for module specific support, you should post in the modules' threads instead.
could have atleast point me in the right direction .... anyway thanks for all help here ....
sam9s said:
could have atleast point me in the right direction .... anyway thanks for all help here ....
Click to expand...
Click to collapse
I did: I told you to post in the modules' threads. Those are usually linked from inside the module itself or from the module's repo page, but I'm not going to search for the links myself and paste them for you.
Q&A for [ROM][Lollipop][Z3C] Cyanogenmod 12 - Nightly
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][Lollipop][Z3C] Cyanogenmod 12 - Nightly. 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!
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
mauroalpha said:
Ciao Guys,
actually I have rEctiFy ROM with clockworkmod recovery..do I have to flash anyway the cyanogen boot.img ?
Click to expand...
Click to collapse
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Video or pictures
I would like to see how the cyanogenmod works on the Z3 Compact. Could you send me a video or some pictures?
Thanks!
Lukas
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
supermanlovers said:
I have still some problems with my bluetooth headset. The connection and the controlls works, but often i dont get sound.
Click to expand...
Click to collapse
My Bluetooth headset was acting up when i had the built in equalizer (AudioFx) turned on , try to turn it off and see if it helps.
I also installed viper4android instead which is way better.
Thanks, this worked for me
2mal16 said:
I think you do. I tried it once in cwm and it failed, it could also have been a different issue but it works fine with the boot.img of the zip. Just keep in mind to store the zip on the internal storage before you flash the kernel and after wiping it.and that the recovery menu is very dim, you should avoid bright conditions.
Click to expand...
Click to collapse
I've just installed with cyano recovery, everything was fine..
I want to report that somethimes the mic recorder loss some seconds while i'm using it..i've just updated now the nightly
need to test it again
anyway i'm really happy, the phone for me is now really faster than the stock rom.
Camera button
Anyone figure out how to remap the camera button yet?
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Is it just me, or is the Auto Updater not rebooting to recovery after downloading the cm-12-20150214-NIGHTLY-z3c -
I did extract and ABD'flashed the boot.img
And theres still an issue with the LED brightness and audio engine wakeup ( Sound seems dim at first, and sometimes notification audio is skipped, almost like it is in hibernation and cant always get out of it ) , cant seem to find it in the fixlog or changelog either
I just got cm12 setup on my galaxy tab 8.4, the only issue i notice thus far is that im finding it impossible to set a different wallpaper on my lockscreen from my gallery pics... If i want to use one of my personal backgrounds i have to use the same as my homescreen. The only way to change just the lockscreen background is to pick one from a theme i downloaded but that option sucks because i never use theme backgrounds... Anyone have a workaround or is that something well have to wait on in another nightly? I was able to do this easily in cm11, just had to go to lockscreen in settings and themes and i could pick it there
kiliimanjaro said:
So i'm kind of a noob here I guess but I thought to install this one would need to have their device rooted (like I had) and I have it on my device working perfectly, the only problem is the phone is telling me that it is not rooted and thus not letting me use titanium backup and greenify etc.
Click to expand...
Click to collapse
Go to Settings, Developer Options, then a few settings from the top you will see "Root access", click it and choose "Apps and ADB" or just "Apps only" (if you don't use ADB).
After root access is enabled you can install SuperSU from the Play Store (or just use the CM root access if you don't want SuperSU).....
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
kiliimanjaro said:
Thanks that worked perfectly!
Another problem though (or else me just being silly and overlooking something simple) that when I boot to recovery it brings up the Cyanogenmod Recovery and there is no option to Backup my files. The only options I have are to wipe everything or reboot.
Click to expand...
Click to collapse
When you flash boot.img from the nightly .zip file you get the CM Recovery. You are correct in that there is no backup option. Use Titanium or some other app to back up your stuff. You can also use a different recovery but you may run into a different problem where the phone identifies itself as "aries" and won't flash the ROM. The CM Recovery takes care of that problem.
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
jflow36 said:
I have a tab pro 8.4 running cm12 latest nightlies and i cant get adblock plus to work on it. Ive tried everything. It ran beautifully on cm 11 but on cm12 it FCs either right after u launch it or sometimes i can almost get done downloading the site block list. I have the wifi only version of the sm-t320 if that helps. Any ideas anyone? Either a way to fix it or an alternative app?
Click to expand...
Click to collapse
try adaway (the newest dev build version) from this thread: http://forum.xda-developers.com/showthread.php?t=2190753
I think it worked for me when i was running cm 12.
firsty said:
Anyone found a fix to the dim notification led issue? I think its related to the CM recovery. Anyone that can confirm this issue aswell?
Click to expand...
Click to collapse
+1. Loving it but the notification LED is basically invisible compared to the stock ROM. Anyone know of a fix for this?
A couple of issues I've run into is sometimes bluetooth audio gets sped-up so my music sounds like it is playing a 2x speed (Google play music) and I'm unable to activate any accessibility services (I can get into the cancel or ok screen but can't click ok). Anybody else have these or know a workaround?
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk