yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] mcmexican:
Oh I dont use any of the G-Sensor apps I only go to landscape when I use the HW keyboard which is rarely so I wouldnt have noticed. For me if it was between the G-sensor apps or the phone turning off during a call I would choose the phone not turning off. Sorry if I caused any issues to anyone.

-McMex
[Touch Pro, Fuze General] tb5...:
i would take this 'hit' as well... i see it's not too definite of a fix but... the screen turning off during calls is weak.

*installs no sleep*
[Touch Pro, Fuze General] PUNiZZLE:
I don't think anyone is understanding what I am asking for. I am not asking for a way to keep the screen on during a phone call or to avoid turning it off.

I am looking for a developer to make a program that uses the TP's light sensor durning a phone call to AUTOMATICALLY turn screen on and off.

Example:

When there is full darkness(Phone is up to your ear) - turn the screen off

When there is light shown(Phone away from ear) - turn screen on

I need this but only during phone call.
[Touch Pro, Fuze General] salamt:
I am not an expert but I think you have a problem here as the light sensor doesn't work in sleep mode
[Touch Pro, Fuze General] PUNiZZLE:
No it's not a problem.

It's a feature I want implemented using the light sensor.
[Touch Pro, Fuze General] ronnie1983:
lol, i think it is rediculious that people dont read his question (who can create a file/program that automaticly change with screen on/off).

Looking forward to see a change, because the screen goes ON or OFF manually isnt the solution.
[Touch Pro, Fuze General] mike freegan:
Whoever makes this guy's program will be a hero.

I like that the screen turns off when I put the phone to my ear but it is annoying to have to turn it on again to enter pin numbers. Especially if you use the autolock feature as this means when the phone is awakened its back on the home screen. By the time I get back to the phone app and into the keypad it's often too late to enter my pin!
[Touch Pro, Fuze General] stozmon:
DOH!

I fell prey to this and now my g-sensor is behaving badly:rolleyes:. Does anyone happen to know what the default g-sensor polling number is so that I can restore normal functionality.

Thanx.
[Touch Pro, Fuze General] :
it blows me away that people don't take the time, build their ppc to specs and make a backup for restore purposes - saving time, frustration and playing with fire...

anyways, can't help you there...

still would like to know how to have the screen remain on during calls.

tvos
[Touch Pro, Fuze General] FOSA:
RE

Quote

"The problem with this CAB is that is changes the G-Sensor Polling to a ridiculous number like 10000, and that causes issues with any programs that rely on the accelerometer to rotate the screen automatically"

Try 3000 for your polling number. It works but a bit slow
[Touch Pro, Fuze General] garagebandking9:
Just go into advance config and change your g-sensor polling interval to 200

Problem solved
[Touch Pro, Fuze General] PUNiZZLE:
THANK YOU! I thought I was going crazy, but apparently NO ONE besides you can actually read what I am asking for.

You understand my problem completely! This is EXACTLY what I am talking about.

I'm not trying to keep the screen on during the phone call. Please read my posts carefully. I still want the screen to go off when I make a phone call. But, I want it to automatically come back on when I pull the phone away from my ear.

Please go make your own thread with your issues.

NO! PROBLEM NOT SOLVED! His problem got solved when he stole my thread! MY problem still remains. So don't you say "problem solved".

To be honest, before this thread I admired xda-dev's, but apparently no one has respect or can read here. People are hijacking my thread, going off topic. It's just insane that a group of such intelligent people can't even help me with this small issue. I'm disappointed :(

It looks like I'm going have to create the solution my self :confused:
[Touch Pro, Fuze General] untrueparadox:
there is a function built into wm6 that u can enable but it sucks. in diamond tweak in the first section theres something thats like "enable light sensor during call for lock" or something like that, turn it on and its good. the annoyance is that when u get it off ur ear, it doesnt unlock, you have to do it manually which is a pain when you need to dial a number for an option or something.

edit: option is called "light sensor" but the description talks about it for use during phone calls.
[Touch Pro, Fuze General] ramontrotman:
knock it off and watch your mouth.

you've been warned.
[Touch Pro, Fuze General] StevePritchard:
I don't think he's way off the mark, to be honest. The solution being sought is for a specific issue, and it's not helping that the situation is being pulled off topic - although that's not unusual.

I think that the light sensor idea might be pulling it in the wrong direction though - the screen appears to go off due to the G sensor noticing a "to ear" orientation. Maybe the in-call laying flat orientation is something that a Gyrator-type app could pick up and switch the screen back on? That seems like less of an issue than trying to start a whole new thread of development using the light sensor - especially as that wouldn't help if you are making calls in the dark?

Cheers,

Steve.
[Touch Pro, Fuze General] Fourstarzzzz:
I agree. This is also something I would like to see. I hate when I am on a call and have to turn the phone back on, especially when I am calling AT&T and have to enter my phone number etc. I have to turn it on, hit keypad before I can do anything. The iphone is great for doing this and hopefully a solution can be found for the Fuze.
[Touch Pro, Fuze General] sarantos:
so, if someone has made the mistake to install this cab, will this issue (of the g-sensor) be solved by uninstalling it ?

if not, what else do we need to do ?
[Touch Pro, Fuze General] baboola:
I like the light sensor idea

but a quick question, what does the iphone use for its proximity sensor? i don't think it uses a light sensor right?
[Touch Pro, Fuze General] ftdn2006:
I understand your frustration thugdrummer, and I know what your asking for. Trust me, I hate the stupid backlight on this phone as well. I've been modding phone since the motorola e398. You have to be patient for an answer man or the moderators will definitely ban you. People will hijack your thread and others will answer their questions. Just be cool, it will take time, but someone will get around to it. The forums are really our only place to go for answers, so we just have to go with the flow. I'm not installing that cab either because it doesn't do what I want. Personally, I'm not about restoring my phone everyday either because some new half-fix came out. The phone is still relatively new, so we have plenty of time. Until a real fix comes out, we just have to deal with it. Trust me, the devs who know what to do understand your question, but that doesn't mean they will answer your post right away.
[Touch Pro, Fuze General] 600GOL:
To thugdrummer

Yeap. Ftdn2006 is right. Someone threw a link to this thread and proposed the problem in another thread I started for an entirely different thing...

BUT! I see the problem and I think its freakin CRAZY that this feature is not built in, or that the "screen off" feature cannot be turned "off" (can it?). You shouldn't need to wait for the call to end for the OS to realize that the screen should be turned back on. I don't even use my Touch Pro for calls but that kind of "error" in the OS itself is a little upsetting. Regardless, I've been looking into the issue. Haven't found anything concrete yet but just so you have the peace of mind... people (i'm sure others besides myself as well) are working on it!

Hopefully soon - everyone who owns these devices can remove their phone from their ear and see their screen turn on without having to do anything!
[Touch Pro, Fuze General] banjax:
I thougth when replying here:

http://xdaforums.com/showthread.php?t=413562&page=21

that I have switched off the "blank in call" feature... but as it shows it only stops blanking when I'm talking through headset (perhaps the light sensor was not blocked). So I guess the Phone/Sleep registry settings don't actually block this behaviour, it merely helped not blanking in some cases :(

(strangly enough before I've changed the Sleep setting the screen was going off even if the phone was laying on the table and I responded via BT headset).
[Touch Pro, Fuze General] inq44:
This is not that easy to solve; the iphone uses heat sensors (infrared) to detect whether it's close to the human skin or not. I think the iphone stands for everything that is bright, shiny and yet devoid of most substance and usefullness, BUT they got this right. Relying on the light-sensor is not good. Low light level in a car at night is probably the main reason why this is not the right way to approach this issue...
[Touch Pro, Fuze General] Icheb1:
Well, I don't think replicating the entire functionality of the iphone is needed.

But still, there's a way to solve even the 'dark room' issue, if a setting was created allowing the use of the gsensor with the light detection.

Something like:

If the gsensor and the light detector detect the phone is near an ear, save the gsensor and light rates, if there is a significant change, turn the screen back on.

This will cause a new issue, because you wouldn't know when exactly a change is significant. This however might be partially solved by setting certain threshold levels / profiles. Like, when you're in a car / have a carkit, you've most likely enabled bluetooth, so if that's the case, switch detection levels to ...

(I have no clue on how to make this unfortunately)

But wouldn't the first step be a solution to keep the screen enabled without having the scr*w with the gsensor retrieval interval values?

I have absolutely no experience in coding programs for these types of devices, so really doing this might not be something I could do, however if there is a clear solution, it might be easier to find someone who could make something like this...
[Touch Pro, Fuze General] 600GOL:
I would assume that people still want the screen to turn off... So that you dont start pressing buttons with your cheek! Turning the device back on however seems to be a little bit of a problem because it seems as though the device continues to try and turn it back off!

I've gotten the screen to turn back on after you remove the phone from your ear but again, the device then tries to turn the screen back off! Atleast this is the behavior of my device...

Regardless I think we're getting closer to a fix...
[Touch Pro, Fuze General] Der_wahre_Phi:
I've found a similar thread on the software forum, why not fuse them or make one out of it?

http://xdaforums.com/showthread.php?t=469301
[Touch Pro, Fuze General] techspy:
I too would really like a solution to this problem. How about a slightly different approach.

How about have the screen brightness set to half when its up to your ear AND have the screen sensitivity set very low as well? This way it would take a more deliberate press, like with your finger to take make a key press?

Or how about half brightness while on a call and full sensitivity but you have to "slide down" to unlock?

Or, how about light off, locked, but shaking the phone (g-sensor) turns the light on and unlocks? (My favorite)
[Touch Pro, Fuze General] StevePritchard:
A software solution to this problem using the G-Sensor is being worked on by 600GOL in this thread --> http://xdaforums.com/showthread.php?t=465586

I think the issue that is causing the problem is how to wake the phone up so that it doesn't want to go immediately asleep. Pressing the power button has the desired effect, so if somebody knows how to emulate that, or how to emulate its effect in code, then let him know.

Cheers,

Steve.
[Touch Pro, Fuze General] techspy:
I just checked that thread and looked at what he has addressed. i don't see anything in relation to what we are asking about here.....?
[Touch Pro, Fuze General] StevePritchard:
It's in there - he refers to it as the "Call Feature" --> http://xdaforums.com/showpost.php?p=3133987&postcount=147

Cheers,

Steve.
[Touch Pro, Fuze General] Michael_514:
Whoa!!! That's a cool slider, and a cool cover!!!!

I did a preliminary search, but can't find it. I love it!

Do you have any cabs for it???

Very slick!
[Touch Pro, Fuze General] :
http://xdaforums.com/showthread.php?t=464286

and

http://www.ppcmobility.com/forums/showthread.php?t=390
[Touch Pro, Fuze General] captainron:
Screen Off During Phone Call...New Idea

I realize the last post in this tread was in January, so there may be a solution I have not yet found. If so, please let me know what it is.

If there is not a solution how about mapping a function to the PTT button? Here is a link my brother sent me on mapping the PTT button:

http://www.fuzemobility.com/how-to-remap-your-att-fuze-ptt-button/

Would it be possible to use the short_PTT.lnk option to turn the screen back on while on a call? If so, how would one go about doing so?

Thanks for your input.

captainron
[Touch Pro, Fuze General] gladht:
Screen off during call fix found

I fouund this thread with a CAB to adjust the screen off feature, including utilizing or ignoring the light sensor. Installed it on Fuze and seems to work.

http://xdaforums.com/showthread.php?t=488991
[Touch Pro, Fuze General] paperWastage:
+1 with this

right now, in call mode, when i place the phone to my ear, the screen goes off... put it on face-up mode, the screen comes back on

only thing i can't figure out is to make the speaker go on in face-down mode... the current action when i place the phone face-down during a call is for the phone to automatically hang up... need to play around more with the settings
[Android Q&A, Help & Troubleshooting] teep11:
Hi,

I need help on my phone, I think it's in deadboot state right now. I accidentally used BRom mode using Android Utility Tool.

The phone doesn't turn on and charge but when I plug it into my pc, it is being recognized.

View attachment 6087254

Is there anyway to restore it's original state? I was trying to remove the FRP but it didn't go well. If I can restore the phone back to it's original state I'll just take it to a tech to remove the FRP.

Please help! :(
[Android Q&A, Help & Troubleshooting] aymncpr:
same problem, did u find any solution?
[Android Q&A, Help & Troubleshooting] mvikrant97:
Does it boot into Preloader mode?

Your device preloader shall be intact to fix it in BROM mode or preloader mode and if the device can boot to preloader mode then there are still hopes to recover it because MT6769 is fairly new CPU and Samsung including all other manufacturer have completely removed BROM protocol from this CPU.

I help people on the forum with FRP in this dedicate Samsung FRP thread.

I have recently unlocked a Samsung A155 using Odin Mode.

Samsung Galaxy FRP Unlock Thread!

Please apologise me if your thread or messages remain unanswered but I get a lot of messages and notifications from so many thread and users on a daily basis from all over XDA so there would be a delay in answering you back. Thank you for your...

xdaforums.com

View attachment 6088016
[Android Q&A, Help & Troubleshooting] mvikrant97:
I would like to know that what option did you used in Android Utility to get the device into BROM mode?

If you have forced the device to BROM using download mode then the preloader would have been likely damaged.
[Android Q&A, Help & Troubleshooting] aymncpr:
i accidently used FORCE BROM (pgpt)

is there any method to repair it?
[Android Q&A, Help & Troubleshooting] teep11:
Same here. That's what I used.
[Android Q&A, Help & Troubleshooting] mvikrant97:
Add filter using lib usb win32 for Mediatek USB PORT and do auth bypass using Android Utility V132 software and post the results here.
[Android Q&A, Help & Troubleshooting] aymncpr:
thats what it shows
[Android Q&A, Help & Troubleshooting] mvikrant97:
As per the log it is clear that it does not supports BROM auth bypass.
[Android Q&A, Help & Troubleshooting] aymncpr:
yep, the chip is not yet supported. rip
[Android Q&A, Help & Troubleshooting] mvikrant97:
Check if your device supports preloader mode.
[Android Q&A, Help & Troubleshooting] aymncpr:
no it doesnt

the device lst the primary GPT

so i dont think theres any solution :(
[Android Q&A, Help & Troubleshooting] AliG87:
If anyone figures a way to fix this exact issue please update/share, have unlocktool but at the moment it says chip not yet supported. Many thanks
[Android Q&A, Help & Troubleshooting] mvikrant97:
Samsung A15 5G?
[Android Q&A, Help & Troubleshooting] AliG87:
Yep, A15 5G - SM-A156W , Canadian variant
[Android Q&A, Help & Troubleshooting] phuochiep24:
Pandora tool used for many MTK chips also does not support Unbrick SS A155F

View attachment 6102540
[Android Q&A, Help & Troubleshooting] white99svt:
Any luck yet? Same issue!
[Android Q&A, Help & Troubleshooting] white99svt:
Also this phone is a mtk mt6835 dimensity 6100+ and not a mt6789 like mentioned originally... I have Unlocktool and UAT Pro at moment but no luck myself
[Android Q&A, Help & Troubleshooting] AliG87:
Nope, I'm still sitting here with the phone not able to boot besides the mtk serial port and black screen, every week or so i search around google for a bit but zero luck so far. because the mt6835 is one of the newer mediatek V6 chips i think that is what makes it hard. i've tried countless ways to try and flash a new preloader but the new chips dont use the same sort of scatter.txt file, the V6 sp flash tool wants an xml file instead to even try to flash.. which no matter what i try it just says no good when i try to load one. i know only surface level things when it comes to fixing problems but this is the only time in over 10 years ive had a phone that still picks up on my pc that i just cant make work again. the one thing i have not done is opened the phone up to physically unplug the battery. then one might be able to use a testpoint to get into a different mode.. or flash it with a jtag.. or something like that. my phones in pristine condition so i have held off cracking it open lol, hoping eventually i might find a way
[Android Q&A, Help & Troubleshooting] AliG87:
also checking the different tools, Pandora tool is one i think might do the trick, also have not wanted to buy a year of it just to find out it does not.. but besides that.. UMT's newest mtk tool also shows support for the chip, and i think theres one more tool, all paid for of course, i already have a Z3x box so i will probably just go with pandora out of ease, if i do, ill post here and let you know how it goes.. and if i can fix it, ill make sure we get yours fixed aswell
[Android Q&A, Help & Troubleshooting] Edwin Hamal:
was this issue fixed and if yes can someone post an update on how? thanks.
[Android Q&A, Help & Troubleshooting] white99svt:
Not yet here....
[Android Q&A, Help & Troubleshooting] eyobaaa:
I think brom protocol removed from this chip MT6789(G99) mine is come for frp on bit 2 latest security removing frp from download mode is patched not work anymore so i disassemble the phone and connect tp no tool can connect in brom tried all cm2,chimera,eft,hydra,octoplus none of them so brom protocol is gone
[Android Q&A, Help & Troubleshooting] Flashouse-Labs:
A156E Scatter ROM | Halab Tech Support

support.halabtech.com
[Android Q&A, Help & Troubleshooting] SKY90599:
I have a Samsung Galaxy SM-A346B which I used the android utility and it's in the same state. so I was wondering if anyone u has unlock tool software can remotely fix my issue cause I have the (dead boot files) from (Halab Tech).
[Samsung Galaxy Z Flip 5] fenrry:
I was trying to change the carrier name as it shows a long line of nonsense "#coberturaCLARO" (#coverageCLARO), I don't mind if it was just "Claro", but is just toooo long, was wondering, is there any way to modify it that it will just show "Claro" ?!

Thanks in advance everyone!
[Android Stick & Console AMLogic based Computers] Chipman417:
Hey guys has anyoneade and custom recoveries or firmwares for the 4gb/128GB variant?

I'm looking to have some fun with this TV box and see what I can get it to do
[Android Stick & Console AMLogic based Computers] mAtvXk:
Which device (specs) , no results through google search !?
[Samsung Galaxy S23] bule..loco:
This tutorial is to roll back from Samsung Ui 6.1 recent update, that,

crapped a lot of phones. My phone s23 ultra and recently

replaced the screen. So that could be a common denominator on touch

screen issues, where only the S-pen works and not with finger.

This will roll your firmware to 6.0 or earlier depending on the

firmware you choose. Hope this helps anyone with similar issues, I'm sure there's better tuts out there.

1.) On your phone go to settings>Sofware information>

(there tap Build Number 7 times) tap..tap..tap..

that enables developer mode.

2.) Go back to settings>Developer options>

make sure to enable ON...and while your there disable Auto update system

Go to settings>Security and privacy>Auto Blocker>*disable Block software updates by USB cable

then *disable ON auto blocker

3.) Go back to settings>About phone

write down your Model name **

4.) About phone>Status information

write down your Model Code** and serial number** , you will need this info.

5.) Download Samsung usb drivers if you don't already have them. https://developer.samsung.com/android-usb-driver and install

also, download Odin tool at https://samfw.com/Odin/Odin3_v3.13.1_3B_Patched_Samfw.com.rar

extract with winrar

6.) ok so now go to samfw.com where you can get your firmware downloaded. Plug in your s23 with usb cord, and samfw online tool will detect

your phone model and information. If your able to do it that way great! If not, then thats where the info. you wrote down comes in handy.

7.) VERY IMPORTANT! NOTICE: CSC/ Version/ Bit/SW REV./ OS

CSC:last 3 letters of Model Code

Bit/SW REV: 5th number from right to left, of (your serial number), its either 2 or 1 for most part.

What you want is to download the firmware with that same number or higher. For example: Version# S918USQU2CXCG ..5TH number is 2..lets say your number was 2 of (your serial number). So that's the one. Notice OS:Android 14

*************************************************************************************

Make sure you have the correct firmware for your device, cant stress that enough! If you flash incorrect firmware it will brick your phone! And Render it useless!

*************************************************************************************

8.) ******From here on your on your own! Flash at your own risk! Bad flash will brick your phone! I'm not responsible for bricked phones. If your brave enough, go right ahead, may the force be with you!*******

1. Extract (unzip) the Samsung firmware file. Recommended using WinRAR or 7-Zip

2. Download Odin Tool 3.13.1

3. Extract Odin ZIP file

4. Open Odin execute file

5. Reboot Samsung phone in Download Mode (hold Home + Power + Volume Down buttons / hold Volume Down + Bixby buttons then plug-in cable)

6. Connect you Samsung phone and wait until you get a blue sign in Odin

7. Add the 1 file Samsung firmware to AP/PDA or 4 files Samsung firmware (AP/BL/CP/CSC) to it's slots

8. Make sure re-partition is NOT ticked

9. Click the START button, sit back and wait few minutes

:)
[Samsung Galaxy S23] echo124:
Work for s23 911u?
[Samsung Galaxy S23] bule..loco:
Yes
[Samsung Galaxy S23] Dreamelba:
Hello,

after some problems with 6.1 update i went back to 6.0

I just want to say to do not flash "CSC home" version and flash the "CSC" to avoid problems.

Everything is working fine again in 6.0

Thank you.
[Samsung Galaxy S23] noob_user14:
Hello. My current version is 6.1, now I want to back One ui 6.0 November security patch, is that possible? Or I have to go out of the box firmware 5.1? And after revert, will I receive update again?

Did u just follwed the above steps?
[Samsung Galaxy S23] bule..loco:
Disable automatic updates on your phone. If you want 6.0 then dl 6.0 and flash it.
[Samsung Galaxy S23] noob_user14:
Any issues u faced after rollback to 6.0?