Related
Hi Guys,
First post on XDA-DEV and I unfortunately can't post in the developer page for this phone.
I recently flashed the ICS Perfection II 04.15.12 and my phone freezes when powering off. Not a huge deal but I would like to remedy the issue.
I have wiped the phone and all the cache and fixed the permissions after the flash.
The page for the ROM does not address this issue and I have searched for the issue on the phone forums with no avail.
Anyone have any ideas? Anyone dealt with this issue before?
1) Honestly I don't understand how if you watched this video, you didn't learn that if you use the search function, you will find answers to all your questions. *facepalm*
2) Never, never, never post in a question in the developer section. Only start a new thread only if you are a developer, hence the "Developer" section.
3)Its a known bug for the skyrocket leak ports, some other ROMs have addressed this issue while others...well they haven't. Quickboot (I think is the name of the app) will do the trick.
4) Hit the thanks button
Breeches said:
Hi Guys,
First post on XDA-DEV and I unfortunately can't post in the developer page for this phone.
I recently flashed the ICS Perfection II 04.15.12 and my phone freezes when powering off. Not a huge deal but I would like to remedy the issue.
I have wiped the phone and all the cache and fixed the permissions after the flash.
The page for the ROM does not address this issue and I have searched for the issue on the phone forums with no avail.
Anyone have any ideas? Anyone dealt with this issue before?
Click to expand...
Click to collapse
This is what i did to fix the rebbot issue. Go into recovery make a nandroid backup, right after the backup is done, flash it. Don't wipe or clear anything just flash it and it should fix it. It worked for me so it might work for you.
the new ucld2 based roms have all resolved this issue (embryo 2.0, new nexus mod beta, sky pics 4.2D-6)
Hi guys. I've rooted couple of months ago and I am still looking for a good rom. ILWT 419 right now but it doesnt have gpu video playback support like some sense romes and have terrible wifi speeds for downloading...
But I wanted to ask something else. clockwork boot menu. There is "reset battery stats" or something among these words in advanced menu.
Is it wise do use that? Always when I am installing new rom I am using "Clear cache, wipe, clear dalvik" options. Don't know anything else about other options.
Right now I am getting 1 dat with moderate use.
Edit: Also one more question. I don't want to create new topic just for this.
What is a difference between superwipeg2+ext4.zp and clearing/wipe as I explained above?
The reset of battery stats is useful if you notify that your battery drains faster than usual...you have to fully charge it and then reset its stats from recovery.
The superwipe is a script that does all the wipe operations at once plus, in that case, formatting as ext4, that otherwise would be ext2. It gets better performance with some roms...anyway it's recommended in the rom's topic if it's the case.
Q&A for [ROM/KERNEL][4.4.4] Quantum 5.2 & QuantumKernel 10/6
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Simple question, from a simple user
singhz905 said:
Yep, Thanks. I just re downloaded the Kernel and it flashed perfectly.
Click to expand...
Click to collapse
First, want to say a big thank you to Pwn for the great ROM you created and the support you've given in the threads.
I've been keeping up with updates for about a year now, but wanted to ask the simple question about "flashing" a new ROM version or Kernel.
I use CW Mod recovery as well as titanium root to back up data and apps etc. When needing to flash a new kernel, what steps are required to ensure it is done correctly? I follow your directions on the home page, wiping everything a few times and installing fresh. From what I gather, that is only needed for flashing new rom's, is that the same process I must follow for Kernel's? Each time I return from the bootloader I install titanium backup from the play store and run my restore of apps etc, not sure that's the best practice, but I am looking for simple answers. I'm a father and work a lot of hours here in Bosnia and Herzegovina, and don't have a lot of time to dedicate to spending hours tweaking the device. I use your rom for it's simplicity and battery life. Any guidance is much appreciated.
Thanks,
Andrew
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Great information as well as confirmation. I will take your advice and create the zip file. That will make things a lot easier for sure. And thank you for the quick response!
Quantum Kernel 10/11
I take it that bluetooth is working again on Quantum Kernel 10/11?
Thanks!
Hey pwn! Thanks for Quantum/ Quantum kernel! I used to always use CM10/11 and it was never that stable for me and the GPS wouldn't work most of the time. I installed Quantum kernel 9/8 and the rom and it was pretty stable I did get some restarts in apps once in a while. However, once you released the new 10/11 kernel everything has been running super smooth! Thank you so much for all your work. I only had one issue with the new kernel, when my battery was completely drained and then shut off, I then plugged in my phone to the AC adapter and it would stay at the boot logo with samsung and pwncakes at the bottom. However, once I let my phone charge for a couple minutes I was able to start it up without any problems. Thanks again!
---------- Post added at 06:29 AM ---------- Previous post was at 06:16 AM ----------
trent2 said:
I take it that bluetooth is working again on Quantum Kernel 10/11?
Click to expand...
Click to collapse
Yep, it's working for me. I'm using a pioneer head unit in my truck and stream audio and phone calls.
Quantum Kernel
Thanks, I'll have to try out the latest.
Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
REPORT: 3hrs post clean flash. att sghi747UCUFNE4.
twrp 2.6.3.1. superSU v2.0.
carbon nightly 10-16 with QK 10-11.
wifi , sound , gps all good. (never have used bluetooth, so dont know. srry).
NO : f/c , random reboots.
no calendar icon (?). & would like to request , if able and not too much trouble , the APN settings menu.(!?). unless i totally overlooked it , which i don't think i did. (please). thanks once again pwn for helping to keep our 'ol s3's up-to-date.
err on the side of kindness
:GOOD:
err on the side of kindness
That looks familiar
Sent from my SAMSUNG-SGH-I747 using Tapatalk
manfromgta said:
Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My guess is you have an unsupported version of recovery installed like d2can instead of d2att. Follow these steps to find the problem: http://forum.xda-developers.com/showthread.php?t=2302599
Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Texan806 said:
Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
Click to expand...
Click to collapse
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809
luckie10 said:
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.
Quantum 5.2 is running very smooth on my phone. Quick question though, my bootloader is I747UCALG1 and modem is I747UCLG1. What bootloader and modem should I upgrade to in cwm, I've been hearing about this NE4. Or should I just go for the jellybean ones? Thanks!
Texan806 said:
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.
Click to expand...
Click to collapse
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!
have you put this on the general s3 Q & A thread ? more would see it there. just an idea.
err on the side of kindness
Update. So I finally had some time to scour the forums for a possible solution and troubleshoot further. Turns out the power button was shorted, had to watch a tutorial and removed it. After getting to recovery I was able to flash 5.2 and latest kernel etc. So far so good, it needs a full charge and hopefully that will go smooth. As this problem started it was discharging the battery so incredibly fast I couldn't keep it charged. Thanks for your help everyone, crossing my fingers it stays up!
Texan806 said:
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!
Click to expand...
Click to collapse
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
aircooledbusses said:
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
Click to expand...
Click to collapse
Well glad you got it sorted out any way
Q&A for [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/25/15
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 [KERNEL][AOSP4.4/5.0/5.1] dkp - d2att - 4/25/15. 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!
whodisname said:
I had to restore a backup today. Battery got to 10% turned on battery saver for a few seconds before remembering this could be an issue still (build 4/25 PAC ROM) then my battery went dead after a while. Wouldn't boot past the Samsung logo. Hot to recovery and after getting it charged to about 50% tried again. Vibrate once, Samsung logo then blank screen then repeat and repeat some more. Restored nandroid. The kernel also deleted itself once after accidentally over clocking to like 1900 or some such (damn touchscreen )
Click to expand...
Click to collapse
I'm also on 4/25 build of PAC ROM. I used Voltage Control and set zen as I/O and asswax as governor. Went to bed with the phone plugged into a USB charger. This morning when I checked it, the notification light was blinking but the phone would not wake and after a hard reset I got the vibrate, Samsung logo, blank screen, repeat. I had to restore to an earlier back up.
I just got a new battery after getting one that was defective last week (wouldn't charge right and drained super fast) just got the new one. Noticed that every time the battery was removed I had to reinstall the kernel.
Whenever I power the phone down completely and try to turn it back on the phone boot loops on the Samsung splash screen. The only way to get it to boot properly is to go into recovery and having it reboot into system. Additionally if I'm fully booted into android and I reboot from the power menu it also boots properly.
Regarding freezes, the only build that won't freeze (I hope :fingers-crossed is the one that I posted to the main thread a day or two ago. It's not in the normal MediaFire downloads, so check the thread for a link.
There have been a lot of reports of boot issues, but I don't have any idea what's going on. I haven't run into this problem, so I don't have any solid information yet. In addition to the usual helpful information (ROM & build date, etc.), a last_kmsg would be a huge help. You'll have to get it from recovery, though.
Try to boot normally. When it fails, boot into recovery. If your phone doesn't reboot automatically, don't pull the battery, hold power to reboot instead!
If you have adb handy, just "adb pull /proc/last_kmsg" and you're done.
Using a file manager (TWRP's builtin or Aroma Filemanager or whatever), navigate to /proc, and copy last_kmsg to /sdcard.
PM me the logcat (hint: /sdcard is actually internal storage, confusingly enough )
Official Nightly
Edit: wrong thread
Can't Flash DKP
I've used this kernel before and been able to flash it successfully. But now whenever I try
To flash it I always get a bootloop. I've tried flashing it with Oct L ROM, PAC ROM,Cyanide L
But it never works. I flashed it and cleared cache and dalvik and tried using fix permissions
to see if it would work but it still doesn't boot.
ocufb24 said:
Whenever I power the phone down completely and try to turn it back on the phone boot loops on the Samsung splash screen. The only way to get it to boot properly is to go into recovery and having it reboot into system. Additionally if I'm fully booted into android and I reboot from the power menu it also boots properly.
Click to expand...
Click to collapse
The same problem here please help
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
aumast said:
The same problem here please help
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
My first thought would be reflashing your current bootloader and modem.
If that fails, then flashing a stock rom. I'm not sure if either of these will fix things for you, but I haven't seen any one else make suggestions. The device has secondary bootloader partitions and these may be what are allowing the phone to boot in those cases where it does.
dawgdoc said:
My first thought would be reflashing your current bootloader and modem.
If that fails, then flashing a stock rom. I'm not sure if either of these will fix things for you, but I haven't seen any one else make suggestions. The device has secondary bootloader partitions and these may be what are allowing the phone to boot in those cases where it does.
Click to expand...
Click to collapse
Are you quite sure about this advice? This looks like a recipient for a brick.
whodisname said:
Are you quite sure about this advice? This looks like a recipient for a brick.
Click to expand...
Click to collapse
If you reflash the bootloader and modem you are currently on there should be no bricks occurring. As far as flashing a stock ROM, always make certain you are flashing one with the same bootloader and modem that is now on the device.
In neither instance would a person be downgrading the bootloader and modem, they would also be keeping both the bootloader and modem at the same version. I haven't seen where anyone has reported this causing a brick, have you?
What is your kernel setup?
governor etc
1. Flashed the kernel, as you can see in my signature however I used to use the Ktoonsez/Task650 kernel. I have to say the leankernel scheduler is amazing. Saves a lot of battery, however in terms of underclocking, is there anyway to get more 'steps'? I cannot lower the voltage for a lot of frequencies in between say 1200mhz and 800mhz as I would with the Ktoonsez kernel. Also the minimum is not low enough, and it seems like the only way I can lower it is by using the flashed zip.
2. Can I use the Ktoonsez kernel with this rom, any tips on stopping both rom/frequency controllers from interfering with each other?
zetsui said:
1. Flashed the kernel, as you can see in my signature however I used to use the Ktoonsez/Task650 kernel. I have to say the leankernel scheduler is amazing. Saves a lot of battery, however in terms of underclocking, is there anyway to get more 'steps'? I cannot lower the voltage for a lot of frequencies in between say 1200mhz and 800mhz as I would with the Ktoonsez kernel. Also the minimum is not low enough, and it seems like the only way I can lower it is by using the flashed zip.
2. Can I use the Ktoonsez kernel with this rom, any tips on stopping both rom/frequency controllers from interfering with each other?
Click to expand...
Click to collapse
Ktoonsez has kernels for both Touchwiz and AOSP based roms. It's been awhile since I read the OP of his kernel thread but it should say if it is good. I don't recall much about Task650 KitKat.
Help with random reboots
I am using the 7/29 revert spinlock kernel and have been having random reboots a few times a day with this version and the normal version. I have last_kmsg.txt . This is the link to the txt file in my google drive : https://drive.google.com/file/d/0B4Oi85yG9ALcTS1saXFCamRnaDQ/view?usp=sharing
I had to paste the link as text because I'm new and cannot insert a link into a message yet. I hope that's ok.
If you have time to look it over and see if you can tell me anything I might be doing wrong or if it's a kernel issue I would appreciate it.
Thank you sir!
dkp 2.1 GHz
Can you tell me how i can setup this kernel? How increase voltages?
Use a kernel app such as trickstermod.
whodisname said:
Use a kernel app such as trickstermod.
Click to expand...
Click to collapse
I understand. How much increase voltage? I don't found.
I don't know. I undervolted all one "step". If you are overclocking, seems prudent to step up in like fashion as before. (I.e. step up 50-75 millivolts every other step over. Something like that. Just be sure to have a solid backup.
Hey. I have this thing on here. It sometimes loses all signal. Just every once in a while. Don't have a logcat cuz its extremely intermittent. Anyone else have that? Otherwise its awesome and no other problems. Stable, random reboot twice in 2 months. That's it. No overheat, no lag, amazing! Super good!
I switched to the Honor 7x from my Ascend Mate 2 a few months back, and while I love close to everything about this phone, my headphones are substantially quieter using the headphone jack on this phone. I tried fixing this originally by installing viper4android and/dolby, but neither wanted to work on the stock rom. I then tried upgrading to Android Pie, and they didn't work on that, then I tried Resurrection Remix, Omnirom and Lineage OS, and neither would work on any of those either. (I already used the Morfuz kernel to switch to permissive on each rom, didn't help).
I am about at my wit's end and really don't want to have to carry a headphone amp with me. Have any of you found a fix for this?
I had assumed that it was a limit set somewhere in it's OS or software, but could it be a hardware limit that's can't be bypassed?
There is probably some fancy way by editing system files or flashing something.
Since I'm stuck with a locked bootloader and therefor without root or custom recovery I use this app: https://play.google.com/store/apps/details?id=com.goodev.volume.booster
I know it's super nooby to solve it this way but I'm not smart enough to figure out another way. I hope this may help you.
Edit: I blocked the notification and enabled start on bootup, so I it's not bothering me. Boost is set to 8% which works fine for me.
br0wni3 said:
There is probably some fancy way by editing system files or flashing something.
Since I'm stuck with a locked bootloader and therefor without root or custom recovery I use this app: https://play.google.com/store/apps/details?id=com.goodev.volume.booster
I know it's super nooby to solve it this way but I'm not smart enough to figure out another way. I hope this may help you.
Edit: I blocked the notification and enabled start on bootup, so I it's not bothering me. Boost is set to 8% which works fine for me.
Click to expand...
Click to collapse
I was using the same app when I was on a stock rom, but had issues with it crashing constantly and having to reopen it. That and you only get a little bit of a boost before it starts clipping from my experience. I am going to do some volume tests with custom roms today and will post my findings here.