So occasionally I will try to unlock my rezound and the screen will never come on. The back light turns on but i have no UI display. I have stock GB firmware with ineffabilis 1.4 and turboprop v2 installed. I am wondering if it is a turboprop issue because Ive only had it happen in the last couple of days since I installed it.
I am ruuing and rerooting it for a current fix but I don't know if it is hardware or firm/software at this point.
I'm having that problem on CleanROM DE, no changes to the build prop. I'm not sure if it's a hardware or software problem?
Sent from my ADR6425LVW using xda premium
thelandon said:
I'm having that problem on CleanROM DE, no changes to the build prop. I'm not sure if it's a hardware or software problem?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The only way I can get it to stop is to pull the battery. It isn't overheating. The hottest mine has been in the past month is 106 F.
I'm gonna run stock for a little while to see where/when this problem occurs. Just so I can rule out custom rom issues.
So I have been running stock for a few days now and this problem has vanished. It seems turboprop might have been the cause.
I flashed turboprop last night. No issues. Not on that Rom though
Sent from my ADR6425LVW using Tapatalk 2
turbo prop swap disable?
I looked in the build.prop file and do not see any lines that reference SWAP.
I have turboprop v4 installed on One XxX v3.2.1
Seems really fast and solid, but was investigating the SWAP being enabled and cannot see it or how to disable.
Related
As stated in the topic, will the thunderbolt reboot itself even with custom roms, kernals, and radios?
Sent from my ADR6400L using XDA Premium App
It's been happening to everyone, reagardless of ROM or OTA upgrade.
Sent from my HTC RootedBolt running CM-7.0.
Sweet, thanks for the confirmation.
It really sucks though.
Sent from my ADR6400L using XDA Premium App
Das Bamf 1.6.1 and lean kernel 2.5, new radio
ZERO random reboots
No issues here. das BMF 1.6.3 with newest radio.
Sent from my BAMF ADR6400L using XDA Premium App
From stock out of the box.
To root, to Das Bamf remix 1.6.3.
Not any reboot issue at all.
I remember 2 reboot in the root process.
1 after the install of Bamf remix 1.6.
1 after 1.6.3.
Up time shows 26 hours.
I never had a problem with reboots..I've tried a lot of roms....everything is running smoother then ever with the new leaked gingerbread leak...don't worry everything is about to get much nicer
No reboots with CM7 and stock radio, but using the recent OTA radio with CM7 gave me reboots. Using OTA radio with any ROM for that matter.
Oy, I'm pretty heart broken over this because I wasn't aware of the reboot problem plaguing the Thunderbolt when I picked it up. Anyone with recent upgrades or just running BAMF 1.7 having issues?
I had between zero and two reboots a day with 1.6.3, desensed, with AOSP dialer. HTC is working on it. For me, it's not been a problem, really.
Sent via GingerBAMF
I was unrooted for the first three weeks I had this, and I didn't have ANY random reboots. Then I installed the OTA and got about 2-3 a day, then a few days later I rooted and have had no problem since. Stock radio (hasn't changed) and I've switched between a number of ROMS, but so far CM7 with the Honeybread theme is doing the best IMO.
I didn't get any reboots on stock radio. After I switched to the OTA radio update, I started getting some random ones occasionally, maybe once every couple of days. Then I tried one of the combos in the radio thread, the .7 CDMA radio with the .6 LTE radio, and I haven't had a reboot since. I believe it is something in the current OTA radio update causing it, so you can just avoid that update for now.
Toxk said:
Oy, I'm pretty heart broken over this because I wasn't aware of the reboot problem plaguing the Thunderbolt when I picked it up. Anyone with recent upgrades or just running BAMF 1.7 having issues?
Click to expand...
Click to collapse
Running 1.7 never had one reboot.
I never had a issue with reboots... After I bricked, I ran stock for the day until I had a chance to re root and flash Gingeritis... In the days time, I had 4 reboots. After I rooted and went back to GB, I have had none (except for a odd issue with a kernel I was testing). After reflashing the kernel. 0
Sent from my ADR6400L using XDA App
No random reboots at all here. I've been using the last 4 or so builds of CM7 from Slayher.
i've never had a single random reboot, running bamf 1.5
azturbomini said:
No issues here. das BMF 1.6.3 with newest radio.
Sent from my BAMF ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I could say the same until yesterday. I have been running 1.6.3 since its release. Had my first random reboot yesterday morning, and had another in the afternoon.
None since then.....
reboots on stock and custom roms.
the only thing i can think of the cause is the transition in and out of 4g areas.
i drive from nj to va frequently and i get 1 or 2 reboots (that i noticed while driving) on my trip up/down 95.
r0guenj said:
reboots on stock and custom roms.
the only thing i can think of the cause is the transition in and out of 4g areas.
i drive from nj to va frequently and i get 1 or 2 reboots (that i noticed while driving) on my trip up/down 95.
Click to expand...
Click to collapse
I am personally in a big transition area on the east coast, it would make a good deal of sense if this is what's happening.
i've never had a random reboot
In the past two weeks I have used Gingeritis, Bamf 2.0 and Gingerbean using the latest updated imoseyon kernel. I am currently using the latest Gingeritis with imoseyon 3.0.1 and the MR2 radio that was just leaked.
There is one lingering issue that is uniform throughout all updates and changes of roms/kernels/radios. Charging time/speed.
After a new Rom install, charging is just how it should be. Then, after a phone call the charging time becomes extremely slow or even sometimes stops at a certain percentage. The only way to fix this is a reboot.
Anyone able to explain what in the GB OS and/or kernels is causing this?
Sent from my ADR6400L using XDA Premium App
I can't, but I promise you the search button can
joshnichols189 said:
I can't, but I promise you the search button can
Click to expand...
Click to collapse
Dide come on...he just had a simple question. You didn't have to blast him like that.
Simple question != Dev thread
sent via telepathy
This was in my backyard today.
Sent from my ADR6400L using XDA Premium App
KGBxxx said:
This was in my backyard today.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
You need to ****ing move now.
Sent through the interwebs.
Mudavo said:
In the past two weeks I have used Gingeritis, Bamf 2.0 and Gingerbean using the latest updated imoseyon kernel. I am currently using the latest Gingeritis with imoseyon 3.0.1 and the MR2 radio that was just leaked.
There is one lingering issue that is uniform throughout all updates and changes of roms/kernels/radios. Charging time/speed.
After a new Rom install, charging is just how it should be. Then, after a phone call the charging time becomes extremely slow or even sometimes stops at a certain percentage. The only way to fix this is a reboot.
Anyone able to explain what in the GB OS and/or kernels is causing this?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Same here and I have searched and can't find solution .
Same here - also no solution upon searching. Back to Froyo BAMF 1.7 until someone finally addresses this...
gramsey1911 said:
Dide come on...he just had a simple question. You didn't have to blast him like that.
Click to expand...
Click to collapse
It was kind of harsh I'm sorry but it's talked about a lot in the rom threads
Sent from my ThunderBolt using XDA Premium App
yep.. charging time is definitely an issue.. I wonder if it has anything to do with the kernel.
I must have been lucky then, because after i flashed the MR2 radio, all that BS went away. Now I have super fast charging and it goes to 100%
It is a slight hassle, but there is a fix for it right now. When your phone is plugged in and charging, restart it while keeping the cord in. It should charge normally after it restarts. I've had the same issue and this makes things act normal. However, you need to do this every time you charge, not just once.
Why aren't developers asking for help on fixing this?
Why's everyone so mum about the issue?
This is starting to drive me nuts.
I know you reboot to fix it but , what specificly is causing it??
I mean when you think about it. Wouldn't killing the process whatever it may be, that kicks in when you get a call fix it?
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Xirta said:
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Click to expand...
Click to collapse
Ghosts
Sent from my MB860 using XDA Premium App
Xirta said:
I am running CM7 pre-beta #2 on Faux 1.6. Underclocked to 600mhz today and undervolted -75 at that speed.
Today on a few occasions my keyboard started acting odd. I was typing a text message and noticed that keys were being "pressed" while my finger was still 1/4 to 1/2 inch from the screen over or near those keys (Q and W mostly)
Anyone else had that happen before? Any idea as to what could be causing it? undervolt, underclock, kernel, rom, ghosts, gnomes?
Click to expand...
Click to collapse
Make a poll. But yeah is it refurbished? If it is maybe the guy who owned it before you got into a horrific accident and his wife got it back and sent it in to get replaced. That could be the cause of the paranormal activity.
Who you gonna text?!?!
---
- adb push iPad2post.apk to /forum/thread
I had that problem on the aura rom, flashed kens alien rom haven't had it since.
Sent from my MB860 using XDA Premium App
Been having the same issue on and off for a couple of weeks.
The longest it has remained stable is 3 days.
After running through the nandroid backups, sometimes this works, I fastboot back to 1.8.3.
If that doesn't work I SBF to a random build, have never used the firmware OTA so have never bricked. Then keep playing with them till voila everything returns to stability. Can take a while though.
I have tried different ROM's, searched this and every other forum, uploading editing pds files, posted here twice on 2 different forums.
Good luck in working it out as it seems I can't.
Those three days of stability ? That ended today and I am on back up no.3 so about to start the fastboot route.
Fixed.
Sgs Screen Booster from the Market has done the job.
Can't remember who suggested it but worked a treat!
Sent from my MB860 using XDA App
Andy_Thatcher said:
Fixed.
Sgs Screen Booster from the Market has done the job.
Can't remember who suggested it but worked a treat!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
What settings did you use for the app?
Sent from my MB860 using XDA Premium App
I went with Super Optimized.
Rebooted did it again and have been fine ever since.
Sent from my MB860 using XDA App
I've had this exact same problem and SGS Booster appears to have fixed it! I'll report back if it stops working again, flashing a new ROM made the problem go away for a while, but it came back.
Edit: Nope, it came back.
TheBassman369 said:
Who you gonna text?!?!
---
- adb push iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Ghostbusters!!!
---
Everything was fine until I flashed PAC-man and Paranoid Android a while back. I went back to stock after and then realized my proximity sensor wasn't working. It was 100% fine before that. In a phone call, my screen turns off and then doesn't come back on unless I stick the phone under light. Somehow my proximity sensor turned into a light sensor. I have tried everything since. I read somewhere that Perseus kernel would help. So I unlocked again, flashed CleanROM (which I liked very much) and Perseus v30. It seemed to work again. I was happy... Until I flashed the latest Perseus v31 a few days ago. It's broken again and I can't get it back. Went back to stock again, unlocked again, flashed a stock rooted rom, flashed beans deodexed rom, flashed CleanROM, flashed perseus, nothing. NOTHING works. What the heck is going on here!? Should I just finally give in and go the warranty route, or can someone identify this problem and come up with a fix. And I know about the temporary setting in call settings, I want my sensor to work though. I know it's not just me, I've seen this in multiple threads for other devices as well, also happening after flashing PA or another AOSP ROM. I wonder what else broke that I don't even know about? I'm tired of dealing with this issue. Thoughts?
I'm not surprised this happened in PAC. All the Asop ROMs are based off of cm10 build we have which has a known big of proximity not working. If you had success with Pegasus 30 and clean ROM, try flashing that again. I guarantee someone else on Xda can come up with a better solution so don't waste your root by getting a new device with a new boot loader in it XD
Sent from my SCH-I605 using xda app-developers app
Sounds less like a hardware issue and more like a custom rom issue.
Yeah....better warranty that.
/s
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
Sounds less like a hardware issue and more like a custom rom issue.
Yeah....better warranty that.
/s
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Exactly why Verizon wants these things locked down. ... Oh and they suck
Sent from my SCH-I605 (AKA NOTE 2)
Exactly. The guy troubleshooted his own post and doesn't even know it.
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
Exactly. The guy troubleshooted his own post and doesn't even know it.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
he just doesn't want to take responsibility for breaking his own stuff.
Sent from my SCH-I605 (AKA NOTE 2)
Rooted, Unlocked, running Beans 18 w/Faux Kernel. Recently my Note 2 has been turning off randomly and won't turn back on unless you pull the battery first. I haven't made any voltage changes and don't have any Verizon software installed. I have seen in other forums that people say it is a hardware issue. However, I never had any issues in the months of ownership until I started installing custom Roms. The Screen of Death (SOD) is becoming an issue across different phones so I am wondering what the common denominator could be. Something in Android? Can't be a hardware issue due to the variety of people using different phones, different roms. Suggestions? Done the factory reset, fix permissions, re-install Beans, different kernels...
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Which version of Faux were you running? V4 I believe had problems with lockups.
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I've tried MeanBean but I am sort of a crack flasher so I didn't stay on it long enough to know. I always clean install everything to avoid problems. I'd really hate to think it could be the Beans. It's been very reliable. Then again...I never had this problem before either...
RemnantKing2 said:
Which version of Faux were you running? V4 I believe had problems with lockups.
Click to expand...
Click to collapse
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
S0UTHPAWK1LLA said:
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
Click to expand...
Click to collapse
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
RemnantKing2 said:
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
Click to expand...
Click to collapse
Man..what a drag..but no, I haven't gone stock yet. I guess it makes sense to go ahead and go stock and maybe even un-root to see if it helps. I definitely can take it back with the BB extended warranty. What gets me is that as you start researching this random turn off issue, you start to see a pattern with more and more sites registering more and more complaints. I get the sneaking suspicion that Samsung knows something.. Possibly hardware issues with the Exynos chipsets. Pure conspiracy theory fodder naturally...Thank you for your suggestions...
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
S0UTHPAWK1LLA said:
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
Click to expand...
Click to collapse
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
S0UTHPAWK1LLA said:
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
Click to expand...
Click to collapse
I don't, I have seen a few incidents with this but not enough to call foul on Sammy's part. 9 times out of 10 it is the users fault for doing something they shouldn't, and most of these complaints you have found are from the same people with the same screenames on different websites.
There will always be a few phones with issues because nothing is perfect, just because you may have gotten a faulty phone doesn't mean Samsung is sending out defective products. If we were in the Nexus forums with all the **** that went down there I would agree but we aren't. Nothing is perfect.
Sent from my SCH-I605 using XDA Premium HD app
Well...I went a whole day on stock without an issue. Not that that means anything, but that my note 2 may be finicky about custom roms. I have always done clean installs and don't mess with voltage on kernels. I am gonna try Beans again to see if I can figure out what I enabled that could've caused my black screen of death. The only thing that I can say for sure that I know was on was Bluetooth each time. Thank you all for your help. It is what makes XDA the go to site.