Develop Bugs

[Q] Problem with HTC TOUCH PRO

Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.

I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.

i must only update with this kernel?

master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.

The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.

master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...

Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.

djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!

I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.

djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.

But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.

Nothing, i have the same problem

master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.

I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.

master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?

Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.

master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .

I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.

Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)

master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!

[Q] viper x reboots when receiving calls

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!

[Q] Would this be a hardware problem? T210R hangs, reboots

On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance

logs?
poodleDoo said:
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
Click to expand...
Click to collapse
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m

moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks

I would use ODIN or KYES to flash it back to OEM stock firmware. Also remove the micro SD card if you have one in there, sometimes corrupt cards can cause boot loop.

true
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again

sharing
poodleDoo said:
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
Click to expand...
Click to collapse
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m

dsilx said:
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
Click to expand...
Click to collapse
The tablet did the same without the sdcard, and I tried a couple times to do a factory reset with no luck.
The fact that it does the same with a different ROM and kernel is what makes me think it's hardware related
moonbutt74 said:
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
Click to expand...
Click to collapse
Cool, i'll get syslog installed and see if I can find anything.

Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx

awesome
poodleDoo said:
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
Click to expand...
Click to collapse
Awesome to hear sounds like @moonbutt74 was right
Hope it keeps working have fun

Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.

cool
poodleDoo said:
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
Click to expand...
Click to collapse
Well that sucks u have to have battery saver on all the time but at least its working now

hmmm
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m

moonbutt74 said:
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
Click to expand...
Click to collapse
I'm running rooted deodexed stock ROM with Blackhawk 2.1 kernel.
But as I mentioned in the OP, the problem was there with the full stock device, the new ROM and kernel were installed after the problem started.

ouch
i think you pegged it right with internal storage being damaged.
only thing i can think of besides getting your money back is do a full data partition wipe and format
and a full system wipe and format
either way that has to suck. sorry i couldn't help.
m

[Q&A] [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 | Hercules

Q&A for [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 | Hercules
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][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 | Hercules. 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!

Bootloop problem!
Hi bryan2894, i have a problem of bootloop with the Rom but isn't only in this rom, its on all roms for this
device, i mean this rom i love it because I used it on a previous device but when i flash the rom following all the steps
the device reboot and reboot and same and same.
Recently, the user "gravitysandwich" togheter with SultanXda, discovery a mutex on cyannogen kernel, this mutex locks
the keypad and causes the device to reboot.
I will quote what was written by them:
Originally Posted by Sultanxda
New build and kernel uploaded. I fixed a known bootlooping issue occurring on KitKat for some users: http://forum.xda-developers.com/gala...-roms-t2833574
This bootlooping issue was originally created in the official CyanogenMod kernel, when dferg added a bunch of mutex locks to the keypad driver (one of the mutex locks he added locks onto a NULL pointer).
Going to look at adding BLN some time soon and fixing the device shutdown when using flash on low battery (this issue occurs with all ROM/kernels and is caused by battery degradation).
Can you help for all the users with this problem can install this wonderful rom.
regards
and this is the log of the user Gravitysandwich:
I GOT IT.
Logs, Logs, and LOGS.
This is on cm11 (08/24/2014 Nightly)
Will try to get logs from latest AOSPA if needed.
Last_kmsg attached (both of them seem the same. You should also use a text editing program like Notepad ++ to view them).
Here is where it crashed (guessing):
[ 20*181213 raqout_irq_handler PMIC Initiated QhutDown
Last couple Lines for quick view:
[ 15.75!447Y sdio_al:waIt for bootloadeR completiof on card 4
S 15.752075] sdio_alBgoTloader Worker Started, wait fo2 bootloader_done event..
K 16.439025] sdio_al: sdim_dld_open, TTY DEVIAE FOR FLASHLESS BMOT OPDNED
[ 16.13366U chArm_statU3_chan'E: charm senT status change interrupt
S 16.513488] c`ari]sTaus_change: charm is no7 re!dy
[ 20*181213 raqout_irq_handler PMIC Initiated QhutDown
[ 20.8335] PMIB Initiated sHut`own apu_powEr[Off Cpu=0
[ 00.181365] PMIC Initiated shutdoun #pu_power_off cpu=1
[ 20.181549] Powepilg oFf the SoB
[ 20.81640] set_dload_mode <0> ( C017514 )
[ 20.18
793] pm8xxx_rese4_pwr_ofd, [1][ 20.181884] pm8xpxWreset_p7r_off, [2]
[ 20.101976] pm8xxx_Reset_Pwr_off, K]
[ 2018232] pm8xxx_beset_pwr_off [4]
R 0.182403] pm8xxx_peset_pur_off, [5][ 20.206573] pm0xxx_rEset_pWr_off, [6]
S 20.206726] pm8xxx_Reset_pwr_off, [7][ 20.206(17] pm8xxx_resET_pwr_odf, Y8]
[ 20.206878] pm8Xxx_reset_pwr_of$ iq called
[ 20.207061] Callifg sCm to disabhe arbiter
Attached Files

helldagp said:
Hi bryan2894, i have a problem of bootloop with the Rom but isn't only in this rom, its on all roms for this
device, i mean this rom i love it because I used it on a previous device but when i flash the rom following all the steps
the device reboot and reboot and same and same.
Recently, the user "gravitysandwich" togheter with SultanXda, discovery a mutex on cyannogen kernel, this mutex locks
the keypad and causes the device to reboot.
I will quote what was written by them:
Originally Posted by Sultanxda
New build and kernel uploaded. I fixed a known bootlooping issue occurring on KitKat for some users: http://forum.xda-developers.com/gala...-roms-t2833574
This bootlooping issue was originally created in the official CyanogenMod kernel, when dferg added a bunch of mutex locks to the keypad driver (one of the mutex locks he added locks onto a NULL pointer).
Going to look at adding BLN some time soon and fixing the device shutdown when using flash on low battery (this issue occurs with all ROM/kernels and is caused by battery degradation).
Can you help for all the users with this problem can install this wonderful rom.
regards
and this is the log of the user Gravitysandwich:
I GOT IT.
Logs, Logs, and LOGS.
This is on cm11 (08/24/2014 Nightly)
Will try to get logs from latest AOSPA if needed.
Last_kmsg attached (both of them seem the same. You should also use a text editing program like Notepad ++ to view them).
Here is where it crashed (guessing):
[ 20*181213 raqout_irq_handler PMIC Initiated QhutDown
Last couple Lines for quick view:
[ 15.75!447Y sdio_al:waIt for bootloadeR completiof on card 4
S 15.752075] sdio_alBgoTloader Worker Started, wait fo2 bootloader_done event..
K 16.439025] sdio_al: sdim_dld_open, TTY DEVIAE FOR FLASHLESS BMOT OPDNED
[ 16.13366U chArm_statU3_chan'E: charm senT status change interrupt
S 16.513488] c`ari]sTaus_change: charm is no7 re!dy
[ 20*181213 raqout_irq_handler PMIC Initiated QhutDown
[ 20.8335] PMIB Initiated sHut`own apu_powEr[Off Cpu=0
[ 00.181365] PMIC Initiated shutdoun #pu_power_off cpu=1
[ 20.181549] Powepilg oFf the SoB
[ 20.81640] set_dload_mode <0> ( C017514 )
[ 20.18793] pm8xxx_rese4_pwr_ofd, [1][ 20.181884] pm8xpxWreset_p7r_off, [2]
[ 20.101976] pm8xxx_Reset_Pwr_off, K]
[ 2018232] pm8xxx_beset_pwr_off [4]
R 0.182403] pm8xxx_peset_pur_off, [5][ 20.206573] pm0xxx_rEset_pWr_off, [6]
S 20.206726] pm8xxx_Reset_pwr_off, [7][ 20.206(17] pm8xxx_resET_pwr_odf, Y8]
[ 20.206878] pm8Xxx_reset_pwr_of$ iq called
[ 20.207061] Callifg sCm to disabhe arbiter
Attached Files
Click to expand...
Click to collapse
I'll take a look at it for the next release
Sent from my LG-D851 using Tapatalk

Thanks man!!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

I haven't used PA in a while and was really hoping to use it again since its one of my favorite ROMs but for some reason, I keep getting the "Insufficient space" error. I've already tried full wiping, wiping cache, and wiping davlik etc and nothing seems to be working.

gotthegalaxy said:
I haven't used PA in a while and was really hoping to use it again since its one of my favorite ROMs but for some reason, I keep getting the "Insufficient space" error. I've already tried full wiping, wiping cache, and wiping davlik etc and nothing seems to be working.
Click to expand...
Click to collapse
Try install micro google apps
Enviado desde mi SAMSUNG-SGH-T989 mediante Tapatalk

Hey Bryan2984, thanks to fix the problem with kernel, now the ROM haven't bootloop but when this finish ti load and appears the installer of google, these freeze and reboot, when the device reboot, these start but the same, the screen freeze on installer and reboot.
Can you help with this problem?
thanks and wait for your great work
Enviado desde mi SAMSUNG-SGH-T989 mediante Tapatalk

Upgrading from 4.6-beta4 to 4.6-beta5 via the OTA updater has caused my Hercules to not want to wake from sleep. After boot, everything seems fine until the phone goes to sleep, at which point I can't get the power button to turn the phone screen on again. Flashing beta4 over beta5 didn't resolve the issue. This isn't a Q or A, just a report of what is hopefully a coincidence or fluke. XDA made me post it here instead of the main thread.

Battery problems
Hey!
I have just flashed this ROM with WildKernel, and it runs very smoothly.
However, I have a weird problem with charging/my battery, which did not occur with the previously used stock ROM.
Basically, when the phone is turned on or on airplane mode, and plugged into a charger, it will say it is charging but actually looses charge. If it is turned off and plugged in, it shows the charging animation, but it doesn't seem to change it's charge.
The only way I have been able to charge it yet is to boot it to TWRP recovery, and plug it in.
Did anybody have a similar problem, and is there a way to fix it? It is pretty inconvenient to have to boot into recovery to be able to charge the phone

helldagp said:
Try install micro google apps
Enviado desde mi SAMSUNG-SGH-T989 mediante Tapatalk
Click to expand...
Click to collapse
Update: I figured out what was wrong. I had formated my Data filesystem to f2fs for when I used Chet Kenner's LiquidBlood rom and since other roms I had used hadn't seemed affected by it i had just left it that way. However, when I switched the partition back to ext4 the problem was gone. Thanks for the help.

Hey guys. I'm an AOSP, AOKP noob. Is there a dark setting for sms, dialer, ect? I love this rom so far for my Hercules phone. It's been really fast and battery life has been amazing. Thank you
(((Super Nerdified 4.4.2 Note 3 n900a
Dual boot thanks to Safestrap
FireKat v8
DynamicKat GPE v6
bobcatroms awesome theme with my own personal touch.
Who's the genius who thought blinding me at night with ugly white screens was a good idea? Thank you devs who know how to black out/invert.)))
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
SnappyCrunch said:
Upgrading from 4.6-beta4 to 4.6-beta5 via the OTA updater has caused my Hercules to not want to wake from sleep. After boot, everything seems fine until the phone goes to sleep, at which point I can't get the power button to turn the phone screen on again. Flashing beta4 over beta5 didn't resolve the issue. This isn't a Q or A, just a report of what is hopefully a coincidence or fluke. XDA made me post it here instead of the main thread.
Click to expand...
Click to collapse
That happened to me coming from a stock rom on my Hercules. I flashed wild kernel and all was right with the world again.
Hope this helps
(((Super Nerdified 4.4.2 Note 3 n900a
Dual boot thanks to Safestrap
FireKat v8
DynamicKat GPE v6
bobcatroms awesome theme with my own personal touch.
Who's the genius who thought blinding me at night with ugly white screens was a good idea? Thank you devs who know how to black out/invert.)))

SnappyCrunch said:
my Hercules to not want to wake from sleep. After boot, everything seems fine until the phone goes to sleep, at which point I can't get the power button to turn the phone screen on again.
Click to expand...
Click to collapse
I have this issue roughly half the time.
Sometimes power button works as it should.
Sometimes the capacitive button LEDs go on, screen remains black for a short time, and then turns on
Sometimes the LEDs go on but the screen does not. A few time's when holding power button to turn off phone from this state, the shutdown menu comes up, which turns on the screen.
Any suggestions?

GeneralVeers said:
I have this issue roughly half the time.
Sometimes power button works as it should.
Sometimes the capacitive button LEDs go on, screen remains black for a short time, and then turns on
Sometimes the LEDs go on but the screen does not. A few time's when holding power button to turn off phone from this state, the shutdown menu comes up, which turns on the screen.
Any suggestions?
Click to expand...
Click to collapse
Another person on this thread said that they fixed their issue about not coming back from sleep by flashing WildKernel. Flashing a different kernel may fix some of your issues.
As for me, I fixed my issues by going doing a factory reset, flashing the latest stable (4.4.5) staying with that for a day or two, and then flashing 4.6-beta5 overtop of it. I'm not sure exactly what fixed my issues, but my phone is back to being as stable as ever.

Paranoid - airplane mode leaves mobile data on
I got a T989 from a friend the other day and flashed the latest ParanoidAndroid 4.6 beta5. Looking fairly good, but when I turn on airplane mode, mobile data is not turned off - I still receive email, and looking at the settings also shows mobile data on.
I did a fairly vanilla install together with PA GApps.

Snapchat breaking in-call audio
The phone works fine until I open Snapchat. After that, in-call audio on both ends stops working. Any update on a fix/workaround for this? Or would it help to upload a logcat when it happens?

magicmedicine204\ said:
The phone works fine until I open Snapchat. After that, in-call audio on both ends stops working. Any update on a fix/workaround for this? Or would it help to upload a logcat when it happens?
Click to expand...
Click to collapse
It's a common issue, search the threads. You need to uninstall snapchat (and hangouts dialer, if you have it) and install an older version. The exact version escapes me, but it's on these boards somewhere. Look in the Q&A and General sections, you'll find it.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app

I would like to install this, but...
I would like to install this, but i want to know if is perfectly functional for a daily using and what differences are with the rom of "sultanxda". Thanks for your help/support

Android L
Camera is broken for me? Is there a fix?

ehtshamulhaq said:
Camera is broken for me? Is there a fix?
Click to expand...
Click to collapse
If you're using lollipop, camera is broken at the moment.

On T989.
Loving the L update. Downloaded last night been using since. Two things, seems like I'm having intermittent touch calibration issues. The other being Bluetooth crashes occasionally. Anyone else experiencing either?
Will continue using to find more bugs.
Thank you.

G930A_QE1_Stock_Deodexed_Rooted_ROM

This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0

Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom

jrkruse said:
Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom
Click to expand...
Click to collapse
Thanks bud. I've been looking for the latest but can't find it. I tried to pull it from my phone using superR kitchen but couldn't deodex it correctly. So inn still working on it. Lol

Congrats bud!!!

Cool. Does adoptable storage work with this ROM?

yuejon said:
Cool. Does adoptable storage work with this ROM?
Click to expand...
Click to collapse
This is 100% stock rooted, deodex, if it didn't work on stock unrooted, chances are that it don't work on this one either.

Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.

OfferedBison said:
Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.
Click to expand...
Click to collapse
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.

dirtydodge said:
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.
Click to expand...
Click to collapse
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.

OfferedBison said:
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.
Click to expand...
Click to collapse
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.

dirtydodge said:
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.
Click to expand...
Click to collapse
Here,

OfferedBison said:
Here,
Click to expand...
Click to collapse
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.

dirtydodge said:
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.
Click to expand...
Click to collapse
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.

OfferedBison said:
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.
Click to expand...
Click to collapse
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.

dirtydodge said:
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.
Click to expand...
Click to collapse
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.

OfferedBison said:
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.
Click to expand...
Click to collapse
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.

dirtydodge said:
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.
Click to expand...
Click to collapse
I have reflashed the rom and also added a dual speaker mod. Everything is working like a charm. Bluetooth and Wifi are all working.

Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?

JJHiemenz said:
Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?
Click to expand...
Click to collapse
Use root explorer, go to system/build.prop and make sure ro.secure.storage is set to "true" as shown in the attachment. I live around Houston TX so we're prepping for the hurricane at the moment so I might be oit for a few days but I'll try to check back on here as soon as I can. Another issue that has been brought up is the phone forgetting Bluetooth device after a reboot. At this moment there is no fix for it that i can find. As soon as I can find a fix for this i will upload a new version.

same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same
same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same).help me pls all user phone no down mode.
http://forum.gsmhosting.com/vbb/f10...0a-sbl-error-upload-mode-pls-help-me-2301220/
dirtydodge said:
This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0
Click to expand...
Click to collapse