Related
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
I'm using Snipers PACMAN, and battery just seems to drain way to fast. It is the latest push. Being newly registered on here I hate to introduce my self this way but I need advice. What tweaks are being used by people for the SPH-D710 to help with this issue? I originally started with the CM 10.1 rom and found I had no data, flashed a different modem. Still no data, switched roms and now have data....go figure! But the battery drain is killing me, I've got it throttled back as far as I can go and it still be a daily driver. So anyone have any suggestions?
Godlys Comadose Tweak pack works great:thumbup:
Give it a shot and thank him while you're over there...here's the link
http://forum.xda-developers.com/showthread.php?p=39080082
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Most 4.2 Roms use ICS modems. As for battery us betterbatterystats found here on xda or gsam in the play store to determine if there's any rogue apps keeping the phone from sleeping. I also do manual syncing. Greenify is a great app to keep apps from running on their own. You can also use a custom kernel to limit max frequency and even undervolt. Kernels also come with different governors
Sent from my SPH-D710 using Tapatalk 2
godzilla61 said:
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Try the latest version....2.1
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
rapman543 said:
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
Read...Read...Read
After reading through the above posts you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.Also read this http://forum.xda-developers.com/showthread.php?t=2005306
Gil81 said:
http://forum.xda-developers.com/show...03&postcount=3
Read...Read...Read
After reading through the above post you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.
Click to expand...
Click to collapse
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
CyberpodS2 said:
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
Click to expand...
Click to collapse
Thank You...... I went ahead and added another link for him to read. I hope it helps. As to what you said, I like to think of myself as the poster child for the search button..lol..I think if you do the research it makes you feel better when it works and it is more likely to stick with you. This site is so great about that because there is just so much knowledge here to learn.I think some people get over-whelmed by it though or they are just unsure and need that go ahead push to know it works.
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
erikalin said:
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
Click to expand...
Click to collapse
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
godzilla61 said:
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
Click to expand...
Click to collapse
Hey bro, easy on the tone. Because there are so many ways to ask the question, the best way is to just spell it out how you did above. Battery life depends on the apps/ROM/user all at the same time. I am on Project X ROM. It has Crossbreeder installed. Now I am not no where informative about that app other than a lot of people like it. So with that being said and it is installed on the ROM, I leave it. I also have ROM Toolbox Pro. I have adjusted my CPU control to 1000MHZ. I also have DS Battery Saver Pro set to custom and to kill all apps when the screen goes off. Last the ROM I am on comes with Greenify. A great app in saving battery. I also turn off data and only have WIFI on when I need it. No need to just let things run. With that I have had 50% battery life left after 11 hrs. That is my setup and may not work for you. The main thing is to understand that battery life for EACH phone is different no matter how many common denominators people may have. Team Venum did a comparison of ROM's and their respective battery life. I don't know the post, but if you type "battery life" in the search, then I am sure you can find it. As for you response, I was in your shoes at one time. It does help to be specific in your questions. Not saying that you weren't. Reading each and every post will get tiresome, but if you type in what you want in the search, you will get a slew of post to get info. I have only been a member for 4 months, but I have learned how to flash a ROM, Mods, push and app, setup custom home screen. I have even been given the honor of testing a ROM. If you still need help, you can PM me and I will do what I can. Have a great one.
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Gil81 said:
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Click to expand...
Click to collapse
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
godzilla61 said:
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
Click to expand...
Click to collapse
First off...I have had the lzp_4 boot loop on me. I pulled the battery,waited about 2 min. Put it back in and booted to recovery. Then I wiped cache and dalvik. Rebooted and it took off(booted fine). I have no idea why or how, but this worked for me. Now to my main concern. If you came straight from ics to a jb rom I think this is going to cause you issues, if you hadn't been on jb before. I suggest the one - click full restore(it wipes data,so back-up you're internal memory).This will get you're phone partition right for jb. After this. I think you should be able to flash what you want with no problems. I didn't see a problem with how you flashed. Wipe cache and dalvik on the kernal flashes you do.Here's the link for the one -click..
go to linked page and click on download ota at top of page
I would read through the page it sends you to well.Don't forget to thank those guys..Hope this helps.Hit me up if it doesn't.
.http://forum.xda-developers.com/showthread.php?t=2148072
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
godzilla61 said:
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
Click to expand...
Click to collapse
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
fitting toryBB
bigmike6200 said:
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
Click to expand...
Click to collapse
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
godzilla61 said:
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
Click to expand...
Click to collapse
What ROM did you flash? Was it ICS or Jellybean? What carrier are you on. That was never revealed.
Never kill the battery. I sed you tried" Wild for the night" and Pac something. Can you get to recovery?
X'ed out the game
Hi,
please give keywords and guiding advice, I will try to find the corresponding threads by myself
I have a brand new GT-I9195 Black Edition. I want to do as less damage as possible, so what do I have to do to get CM11 with Xposed framework running?
I just switched it on, started KIES 2 and connected. No SIM-card is inserted, no microSD-card, no WiFi connection. The phone is offline.
KIES says that the firmware is the most recent and gives this:
Code:
I9195XXUBML4 / I9195YBTBNA2 / I9195XXUBML4 / I9195XXUBML4 (DBT)
I assume this is not the newest firmware, and according to this thread (German) "I9195XXUCNE6 I9195OXACNE6 DBT 4.4.2 23.05.2014 is newer.
I have or see no possibility to upgrade via KIES.
Would the new firmware give me another, better modem/baseband firmware? If so, I would flash with Odin 3.09.
I think I need root permissions for Xposed and XPrivacy, at least this is what I did with my Sony Xperia mango. Is that correct?
What steps do I have to take to get root access without interacting with KNOX? Does it make sense to avoid the KNOX counter increase?
What part of the warranty will be void if KNOX is triggered?
What recovery should I use? There is already a recovery available, accessible by pressing Volume Up and home button at the same time when switching on.
I wanted to start with CM11 and no special kernel, just what CM11 brings, to keep it easy. So flashing serranoltexx M9 or later should be sufficient?
How do I get Xposed and XPrivacy to work? I want it working before putting in the SIM card and connecting to the internet. Do I have to worry about dalvik and ART?
GApps 20140105 from http://wiki.cyanogenmod.org/w/Google_Apps are the right ones?
Did I forget something?
Thank you
Raubsau
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
MarkAndroid.UK said:
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
Click to expand...
Click to collapse
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
Why is it so important to you to install XPrivacy before first boot?
Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
No one wants to brick their device, do they? I've never bricked mine and I've made lots of mistakes. It is highly unlikely unless you try to flash something not meant for your device or something similarly bad.
I certainly haven't found CWM being recommended over TWRP - devs here tend not to recommend, just point things out; ALL choices are yours. There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it. ROM's are built from components and not everything has to be there - one of the brilliant things about Android is how it interfaces with all the different aspects of a mobile device - it appears to be one program running everything but it is extremely modular.
With external apk's I just copy them to external SD and install them on the phone.
Raubsau said:
Do I have to worry about dalvik and ART?
Click to expand...
Click to collapse
Forgot this bit!
No. You can elect to use ART in the system setting of some ROM's (certainly SLIM) and I know some people who do. However, ART is still under development and by no means are all apps ready for it yet. Xposed Framework itself will not work under ART and won't be for quite a while yet.
MarkAndroid.UK said:
There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it.
With external apk's I just copy them to external SD and install them on the phone.
Click to expand...
Click to collapse
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Raubsau said:
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Click to expand...
Click to collapse
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
MarkAndroid.UK said:
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
Click to expand...
Click to collapse
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Raubsau said:
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Click to expand...
Click to collapse
'Small' would be fine
MarkAndroid.UK said:
'Small' would be fine
Click to expand...
Click to collapse
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Raubsau said:
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Click to expand...
Click to collapse
That's great, have fun and you're welcome
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
I intend to buy the 'black edition' too but I am worried whether the internals changed as it's a later model and hence CM wouldn't run on it...
black edition:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
"ordinary" black version:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-1.jpg
Thanks a lot
soikku said:
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
Thanks a lot
Click to expand...
Click to collapse
If the model number of the device you wish to buy is I9190 or I9195 then you can follow standard procedure.
Black edition is just cosmetic variation. Nothing special about that. Model number is always I9190/2/5.
So use normal procedure from threads in this forum. Good luck.
My phone looks like this:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
Info in the Settings menu says "GT-I9195".
As I was using XPrivacy fromt the start, some of these problems may have occured because of wrong restrictions:
- orientation of indicator in Google Maps shows wrong direction
- no compass app is working
I use my phone for calling, reading and writing mails, and remote control my media box. In the few cases I needed it for navigation, it worked fine (regardless of the wrong indicator).
Hope that helps.
Thank you for the replies, Raubsau and sasank360
Thank you for pointing out that the 'black edition' indeed is identical to the previous one internally.
I ordered the phone now and am looking forward to happy flashing (CM11 for the time being as freecyngn doesn't work for CM12 (yet)).
Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
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][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). 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!
Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.
temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out
Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.
total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.
bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.
flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.
This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.
chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).
I've haven't tried it but since it's a 4.4.4 rom they should work fine.
Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).
**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930A_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930A_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Will it work for g935a? And does it fix lag?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Awesome!
Ok how many folks have successfully flashed this?
It's still using eng boot? And will I be able to update super su script once installed? Also curious if maybe deodexed means I can get v4a running on this bad boy sorry for the question blast just excited to see the att s7 taking off into #root =D in Texas it goes "y'all got root?!"
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Can you fix the URL? I get a 404 when clicking it.
Thanks,
Aaron
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
smknutson said:
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
Click to expand...
Click to collapse
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
I think I am. It's either this Rom or the eng bootloader, but it runs hotter. It's running in interactive governor but cpu temperature is averaging idle at 45°c whereas on stock it felt much cooler. Something about this installation is causing this thing to heat up.
Carlos Terán said:
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I'm not sure what lag you're referring to?
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
noobtxtech said:
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
Click to expand...
Click to collapse
Haven't tried v4a but Wanams modified Xposed is working and I have several modules operational.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
dirtydodge said:
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
Click to expand...
Click to collapse
Modified Odin for both EngBoot and this threads addon .zip
smknutson said:
Modified Odin for both EngBoot and this threads addon .zip
Click to expand...
Click to collapse
Ok thank you. Figured so but just wanted to make sure. I'm downloading the Rom now. Glad you found the fix and debloat from the Verizon thread, I seen that the other day and used it and his other guide on how to set up Greenify and amplify. My phone is running awesome on the stock rooted but I always like to grab muniz's deodex versions and run them.
Also, if you want to get rid of the Custom icon on boot and reset it to Official in status, use the XTouchWiz xposed module.
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
joe3681 said:
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
Click to expand...
Click to collapse
You have to be rooted prior to flashing this.
Clearly. I meant post flash
joe3681 said:
Clearly. I meant post flash
Click to expand...
Click to collapse
" To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy! " is copy pasted from the OP so that would imply that it isn't rooted until you root it, as for why you would want a deodexed Rom (which is a performance hit) without root is beyond me. From what I gather reading this short thread you will need root and possibly even xposed to get it running right. In order to do that you would have to do some more reading. Hope this helps.