Related
i was running cm9 on my sgsgh-959w 4g then i decided to upgrade to ics -passion .. i flashed it and everything but it wont fully load,, everytime it starts booting the phone shut off n come back on and start loading again,, i left it for like 15-20 mins but it does the same thing. can anyone help please.
http://forum.xda-developers.com/showthread.php?p=43211527
sent from me
I have a Galaxy S 4G and trying to up to 4.0 too. I'm having big issues too. So far from what I learned, you can't treat it as the Vibrant (Avator version) phone. Completely different.
I'm following a different source but I am stuck.
but my phone can't mount the sd card right now. after formatting from the phone then it works. I'm in progress right now.
---------- Post added at 08:24 AM ---------- Previous post was at 08:18 AM ----------
Apparently I can't post the link because I havne't made 10 post yet.
If you find anything let me know. You should consider Slim ICS too, it seems like it's so much faster but the big issue "i think" is the USB Mass Storage doesn't work.
So I installed ICS 4.0.4 successfully, but now the phone won't receive any signal from t-mo, just the annoying 2.1 & 2.2. The sim card isn't bad because it connects with other phone like normal.
I'll post the procedure as soon as I can post a link.
Does anybody else find it interesting that even though this guy flashed a vibrant ROM, the passion recovery actually installed on our phone?
Sent from my SGH-T959V using xda app-developers app
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
sorry misread, wrong answer
---------- Post added at 11:43 AM ---------- Previous post was at 11:23 AM ----------
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
dparrothead1 said:
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
Click to expand...
Click to collapse
The advanced reboot menu is already enabled, what I'm saying is that when i click reboot to recovery, it simply passes the splash screen and proceeds to boot
up normally...
g-noob said:
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Click to expand...
Click to collapse
I'll try the rom manager part and reflashing the different ROMs when i get time and I'll let you know. I already have 6.0.4.7 by the way.
DE52 said:
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
Click to expand...
Click to collapse
I use goo manager app to boot into recovery, always works and is good to go IMO
Judge Joseph Dredd said:
I use goo manager app to boot into recovery, always works and is good to go IMO
Click to expand...
Click to collapse
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
DE52 said:
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
Click to expand...
Click to collapse
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
eZdubzitmk4 said:
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
Click to expand...
Click to collapse
I installed it and tried the reboot to recovery option which didn't work either in this app. Thanks for suggestion also
Flashing back has worked so far
I flashed back to GB as I said earlier. So far all ROMs have indeed booted into recovery. I guess on my way up the other times, I hadn't followed instructions in detail since I have not experienced any issues that I used to get so far. Hope it keeps going that way anyway once again thanks to everyone for your help! If I have any problems, I'll let you know (currently on Helly Bean 4.2.2 which I just flashed). The real test will come when I flash JB 4.3 and KK which is where I used to have problems booting from power menu.
EDIT: Ok so basically my problems start occurring on jb 4.3. I noticed that going from 4.2.2 to 4.3, the recovery reports a status 7 error. I already know that means the recovery is "old", but the thing is, it allows you to do an install anyway which I usually do in order for it to convert the file system and install the newer recovery which it does. The only thing though is I guess it doesn't repartition correctly due to that status 7 error. So I guess my question would be how I should proceed to get a 4.3 recovery without flashing a ROM or if there's a way to proceed that I am not aware of? Do you happen to have any links @eZdubzitmk4 or @Judge Joseph Dredd or @g-noob ?
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
g-noob said:
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
Click to expand...
Click to collapse
Haha thanks, it's not so bad anyway. At least I can get into recovery through the manual way (3 buttons) and at least the ROMs install like you said. I was just checking if there was a way to avoid the status 7 which is caused by incompatible partition layout (which is why you flash twice by the way;the second time it ignores the layout and just proceeds). I'll give the link a try by the way.
hey guys,
wasnt sure where to put this
my names simon and im from the uk,ive been reading this forum for a while now and the past few months ive unlocked/flashed my htc one with AICP
i was wondering if theres any tweak pages for this rom to make things better lol?
ive just done another venom rom through this site but when it rebooted to the screen unlock it would go white with the htc logo on and come up with a htc.dialer problem all the time and sit there for say 10 mins then go through the setup for a few pages to have this error again,ive waited for it to close also but with no luck
cheers
simon:good:
Just try diffrent roms until you find one that suits you (works as should ).
Remember to clear data, cache, system before flashing each rom.
If you want to increase performance or battery life you can flash custom kernel via recovery
Rafostar said:
Just try diffrent roms until you find one that suits you (works as should ).
Remember to clear data, cache, system before flashing each rom.
If you want to increase performance or battery life you can flash custom kernel via recovery
Click to expand...
Click to collapse
Thanks for the reply m8,now do I clean everything in this rim I'm on now with say ccleaner then wipe data and reflash?
Also you got a link for the kernal flash please?
Step by step instructions you can find by Googling (I can't post you link to that site because it's not allowed)
Custom Kernels are here on XDA:
http://forum.xda-developers.com/htc-one#kernels
Just read about them and chose the one that you like or try different ones
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
No, you dont need to clear junk with Ccleaner, because you will be formatting data, cache and system via recovery...
The same way you did when flashing your previous rom
You don't have to do this only when updating the same custom rom to a new release (but has to be the same Android version)
lol,i think ive tried all the kernals now and all seem to 'brick it'
they either sit there for about 10 mins and just keep restarting or do nowt at all
good job i backed up the aokp rom first
also ive just installed the candykat rom but that wont even boot up haha
Can someone please help me out with an issue I am having...?
I can't seem to get Service after installing an AOSP ROM. I have been messing around with this issue for several days now. When I install a 'NON AOSP' ROM such as 'the 'MOAR ROM' it works fine, but then I go to in recovery (Newest TWRP or Newest Philz Touch) and do all of the required 'Wipes' then Install an AOSP ROM like 'Fusion', 'PAC' or the most recent 'CM11 Nightly' and I do not get any Cellular Service (WiFi is fine) and I have been looking for answers for several days and I can't seem to find any.
Can someone please help me out and let me know what I need to do, or point me to the right direction?
Thanks in advance for any help and/or resources that anyone can provide me with. It will be greatly appreciated.
Phone:
Sprint Samsung Galaxy S5 NE5 (Rooted with Knox Tripped :crying
MOAR ROM Installed / Touchwiz Interface.
_________________________________
My Web Design Portfolio
Same was happening to me on philz recovery . so I install trwp for sprint/Verizon . then I installed trwp manager from play store . I install the PAC ROM from in the app and let it wipe it self . and that did the trick at least for me. I have tried many ways like your self. Nothing work that's the only way I got it working. Hope that help.
Sent from my unknown using Tapatalk
I'll give it a shot and see what happens. Thanks for the tip...
Has anyone else had this problem? If so, can you post anything you did to get it working...
My Phone Thanks You...
Im having the same problem on both TW and AOSP. If I mess around with the connection settings I can get a signal but when I reboot its lost.
Ive tried both recoveries and its the same on both. Ive tried flashing modems but that did nothing
EDIT: Seems that any kernel that I flash breaks my phones signal, I need to test further to see what part of the kernel flash is causing this.
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Shad Stang said:
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Click to expand...
Click to collapse
I think you guys need to flash an APN package with klte roms. Kltespr roms should not have this problem, but if you run into it flashing the APN package shouldn;t hurt there either. Not sure if there is still an APN zip floating around, you may have to manually fix your APN.
It turns out that the custom kernel I was using broke the signal for some reason. Other than that, I had no problems as long as I flashed a kltespr rom. Klte roms worked for data if i used a virgin mobile apn, but there was no texting or calling.
I attached the flashable zip I used to get the virgin mobile apn. I would recommend flashing it right after you flash your rom.
having this same issue also..
i have tried several things.. going back to complete stock and working forward
no matter what i do i get no service on any AOSP rom.. im going to try this apn fix. hopefully it doesnt further break anything lol
Anyone figure this out yet? I've tried about 4 aosp roms and no luck.
PacMan rom with PA Gapps and Ktoonsez kernel worked for me. None of the others did so it must be a ROM issue.
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
garwynn said:
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
Click to expand...
Click to collapse
I couldn't get data on any kltespr builds except Pac Man and even then I lost data the next day for some reason. The new lollipop build has data working for me even though it's "GSM only" so just hoping it stays that way haha Waiting on fixes for battery drainage and I'll run it daily
Q&A for [STOCK ROM][5.0] OA6 Android L Deodexed
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 [STOCK ROM][5.0] OA6 Android L Deodexed. 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!
Wifi
I flashed as directed, and it is running. The issue I have is wifi keeps disconnecting and reconnecting. I was running MOAR and it was great, but it would not roam, it was stuck on CDMA. Now this will not stay connected to wifi.
tedmales said:
I flashed as directed, and it is running. The issue I have is wifi keeps disconnecting and reconnecting. I was running MOAR and it was great, but it would not roam, it was stuck on CDMA. Now this will not stay connected to wifi.
Click to expand...
Click to collapse
Not sure. Did you also flash the wifi calling fix and toggles addon in Post #2?
Just wondering if that had anything to do with it.
You can try reflashing the full stock tar and see if its doing it there. Then try reflashing the deodexed rom without the wifi calling fix, test it again and then flash with wifi calling fix at the very end to see if that's what is giving you the problem.
---------- Post added at 01:36 PM ---------- Previous post was at 01:18 PM ----------
@tedmales
I've added a stock features.xml flashable to Post #2 of the home thread. Flash that first to see if it resolves any of your issues. If it doesn't, follow the other directions I posted. Not sure what else to try.
Cheers - TD
Is it possible to flash the 4.4.2 kernel and use towel root with Knox at 0x0 and flash back?
I was able to do this on 4.4.4
Sent from my SM-G900P using XDA Free mobile app
tdunham said:
Not sure. Did you also flash the wifi calling fix and toggles addon in Post #2?
Just wondering if that had anything to do with it.
You can try reflashing the full stock tar and see if its doing it there. Then try reflashing the deodexed rom without the wifi calling fix, test it again and then flash with wifi calling fix at the very end to see if that's what is giving you the problem.
---------- Post added at 01:36 PM ---------- Previous post was at 01:18 PM ----------
@tedmales
I've added a stock features.xml flashable to Post #2 of the home thread. Flash that first to see if it resolves any of your issues. If it doesn't, follow the other directions I posted. Not sure what else to try.
Cheers - TD
Click to expand...
Click to collapse
Thanks for the quick reply. In a fit of rage about 330 last night I wiped and flashed my way back to moar 2.2. Only issue there is I noticed the OA6 modem is still on it and I tried to phone and it works. I will leave as is for the day and try again tonight using your advice.
Thanks
Ted
tedmales said:
Thanks for the quick reply. In a fit of rage about 330 last night I wiped and flashed my way back to moar 2.2. Only issue there is I noticed the OA6 modem is still on it and I tried to phone and it works. I will leave as is for the day and try again tonight using your advice.
Thanks
Ted
Click to expand...
Click to collapse
Hey Ted, someone in the main thread with the same issue with wifi said he turned off Smart network switching or something in advanced wifi settings and that fixed it for him. Myself, I always uncheck all the boxes in there...
[STOCK ROM][5.0] OA6 Android L Deodexed is the best!
Loving this ROM. It has everything I need except for a wireless charging notification toggle. Would NKD New Stuff Rev. 1.3 run on OA6?
tdunham said:
Hey Ted, someone in the main thread with the same issue with wifi said he turned off Smart network switching or something in advanced wifi settings and that fixed it for him. Myself, I always uncheck all the boxes in there...
Click to expand...
Click to collapse
I had the issue with constantly losing Wifi connection when standing less than 10 feet from my router. I turned off Smart Network Switching and the problem went away. Battery life improved drastically as well since my phone was no longer trying to pull all its data from the network.
Debloat seems to remove Pro Audio functionallity
Hey tdunham!
I finally got a chance to try out your OA6 ROM, and I'm really enjoying it! I just wanted to follow up on the pro audio functionality I had posted about in the MOAR 5.0 thread, or what might be another cause.
So I followed all the instructions, wiped, odined stock and recovery, flashed the ROM, flashed the debloat package, booted up, everything worked fine. First thing I did was download the galaxy store so I could try the pro audio application amplitube and soundcamp, same issues I had in MOAR, force closes on Soundcamp, no audio input through the mic.
Just to make sure it wasn't firmware, I flashed back to stock, everything with the pro audio apps worked well. Then I wiped and reflashed your ROM without the debloat package, and low and behold, the pro audio functionality worked fine. So whatever it is that cripples it is in what gets removed from the bloat I'm guessing, something that wasn't removed in the International BOA3 based ROM either. I'm fine living with all of the sprint apps, just a few more boxes to un-tick and things to hide in the launcher, but just thought I'd mention it in case anyone else runs into these issues.
Thanks again for all the great work!
hugantic said:
Hey tdunham!
I finally got a chance to try out your OA6 ROM, and I'm really enjoying it! I just wanted to follow up on the pro audio functionality I had posted about in the MOAR 5.0 thread, or what might be another cause.
So I followed all the instructions, wiped, odined stock and recovery, flashed the ROM, flashed the debloat package, booted up, everything worked fine. First thing I did was download the galaxy store so I could try the pro audio application amplitube and soundcamp, same issues I had in MOAR, force closes on Soundcamp, no audio input through the mic.
Just to make sure it wasn't firmware, I flashed back to stock, everything with the pro audio apps worked well. Then I wiped and reflashed your ROM without the debloat package, and low and behold, the pro audio functionality worked fine. So whatever it is that cripples it is in what gets removed from the bloat I'm guessing, something that wasn't removed in the International BOA3 based ROM either. I'm fine living with all of the sprint apps, just a few more boxes to un-tick and things to hide in the launcher, but just thought I'd mention it in case anyone else runs into these issues.
Thanks again for all the great work!
Click to expand...
Click to collapse
Just wondering, did you install v1.1 of the deodexed rom?
And below is the list of what gets deleted in the debloat tool, see anything that sticks out?
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
My guess would be the Samsung Billing being removed as was stated by the other person after installing the Samsung App it still fc'd. Just a guess though
Sent from my SM-G900P using Tapatalk
no sprint yellow boot screen missing?
I had this issue awhile back on the first ROM that was released when the phone came out. The yellow boot screen is still included. along with pretty much every carriers custom boot animation. The problem is that csc file was rewritten to XAS, you want it to be SPR. This is the app I used to changed mine when it got changed. The downfall is that it wipes your phone and you have to start over, it could work with a backup but I usually just start from scratch anyway. Most of my data is cloud based so once I log into the apps I use nothing has changed. It also says it doesn't work with custom roms but it did work for me, on a dioxide custom rom. I cannot verify it works on 5.0 and I'm currently working on testing it if it can, unless you can get it completed yourself faster then I can.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&hl=en
---------- Post added at 06:39 PM ---------- Previous post was at 06:29 PM ----------
I currently cannot download this rom as androidfilehost is down so I will figure out a way to test on boa6 stock with cf-auto root in the mean time.
On stock 5.0 BOA6 with root via cf-autoroot, I was able to rewrite the CSC from SPR to XAS/BST and back to SPR. It does indeed wipe your device so make sure to back up before use, or be prepared to start from scratch clean install of rom
deoxed boot animation fix
Ok a separate post for what I did. I flashed the BOA6 deoxed with CWM, flashing debloated and stock boot animation right after and before first boot. I let the device boot (10-15) minutes then did a basic setup to install CSC changer from the play store. I changed from XAS to SPR and let the app complete its processes, this included a reboot to a special recovery. The phone then rebooted with the sprint boot animation and continued to first set up where I then set my phone up as I wanted. I do not think a recovery will work as the XAS CSC would be in a back up before using CSC changer. however the app does do its job as far as getting the sprint boot animation back.
Hope this helps
ADB Shell does not work
I recently installed this ROM and am having issues getting the shell to cooperate. Whenever i attempt to run any command in the shell I am given a response of "Aborted". Any ideas?
tdunham said:
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
Click to expand...
Click to collapse
Yeup, running version 1.1, which is really nice and smooth by the way.
Unfortunately nothing in there looks significant in terms of this functionality, so I have no idea what the professional audio system is associated with that keeps getting broken. Just to check though I made a nandroid backup after I set up the phone this time, then flashed the debloat (v1.2) tool...it was strange, it seemed like it worked for a minute, but then after not using it for a while the professional audio related apps started glitching again. Restarted, still glitched, restored to before I flashed the debloat package and it all worked again. It's been about a day or so and haven't had a problem since.
unable to install apps error 491 after installing this rom
I can't install anything since installing this rom.. All i get is an unable to install error 491.... Any ideas?
hugantic said:
Yeup, running version 1.1, which is really nice and smooth by the way.
Unfortunately nothing in there looks significant in terms of this functionality, so I have no idea what the professional audio system is associated with that keeps getting broken. Just to check though I made a nandroid backup after I set up the phone this time, then flashed the debloat (v1.2) tool...it was strange, it seemed like it worked for a minute, but then after not using it for a while the professional audio related apps started glitching again. Restarted, still glitched, restored to before I flashed the debloat package and it all worked again. It's been about a day or so and haven't had a problem since.
Click to expand...
Click to collapse
My guess would be the Samsung Billing being removed as you stated you only installed just the Samsung App. There is also a SamsungBilling App that gets removed also. If its a paid app its probably trying to check on something to verify its not a pirated app. Just a guess though [emoji780]
Sent from my SM-G900P using Tapatalk
Internal Storage Double COunted
I'm having a problem whereas I'm getting notices that I'm running out of space and I know that I'm not.
I'm seeing a "/storage/emulated/legacy " path and a "/storage/SD Card" path. Is it possible that both are being counted against my total space count?
Is it possible to fix this? I'm backed up so formatting it or some other way that may erase just the contents of the internal card isn't a problem.
Everything else seems to be working fine. I haven't seen any of the reported issues.
battery drain?
Is anybody experiencing a high amount of battery drain. I flashed fresh last night and used ktoonez updated kernel to fix the 491 play store error... i dropped 30% battery in 1.5 hours this morning..
F22loader said:
I'm having a problem whereas I'm getting notices that I'm running out of space and I know that I'm not.
I'm seeing a "/storage/emulated/legacy " path and a "/storage/SD Card" path. Is it possible that both are being counted against my total space count?
Is it possible to fix this? I'm backed up so formatting it or some other way that may erase just the contents of the internal card isn't a problem.
Everything else seems to be working fine. I haven't seen any of the reported issues.
Click to expand...
Click to collapse
Something may have gone wrong in the flash continuum. For me, I didn't OTA at all. I Odin-ed the tarball and everything is fine except for showing I am "Custom".
7.04 Gb still available....even after the flash of TDunham's Deodex.
---------- Post added at 01:17 AM ---------- Previous post was at 01:12 AM ----------
exodusprime1337 said:
Is anybody experiencing a high amount of battery drain. I flashed fresh last night and used ktoonez updated kernel to fix the 491 play store error... i dropped 30% battery in 1.5 hours this morning..
Click to expand...
Click to collapse
Unless heavy web surfing/app using, that's a little heavy. I'm not sure what your settings are, but I did find that the Ktoonservative setting doesn't do for Lollipop what it used to on KitKat. I am set to 2475 over 300, Conservative @ bfq, No overclocking and no undervolting. GPU turned up full blast. KThermal only and Thermald enabled.
I go about 18-20 hours. I CAN get more, but I never turn data/GPS off. We wanted Lollipop and we got it. Ya gotta pay to play. It drains juice.
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
elwood said:
My guess would be the Samsung Billing being removed as you stated you only installed just the Samsung App. There is also a SamsungBilling App that gets removed also. If its a paid app its probably trying to check on something to verify its not a pirated app. Just a guess though [emoji780]
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
This is just ONE idea(and it may not work for everyone).
I had the old backup from TiBu. I restored it(app only) and it stuck. I can do everything in Samsung's app store.