Advanced Extension — Mobile Part 34

EivoTech Laptop & Mobile Repair Master Course

Advanced Extension — Mobile Part 34

DC Power Supply + Smartphone Current Draw Pattern Mastery

Chapter 34: Current Draw ko Guessing ke Bajaye Boot Sequence ke Saath Interpret Karna

DC power supply mobile motherboard diagnosis mein bohat useful tool hai.

Lekin ek dangerous beginner habit hoti hai:

“0.10A aya = CPU fault.”

Ya:

“0.30A aya = UFS fault.”

Ye universal rule nahi.

Professional rule:

CURRENT VALUE SE ZYADA CURRENT BEHAVIOR IMPORTANT HAI

Master formula:

INPUT → IDLE → POWER REQUEST → CURRENT RISE → BOOT STAGES → STABLE / COLLAPSE


1. DC Power Supply ka Diagnostic Role

Bench DC supply technician ko broadly help karti hai:

  • Board power behavior observe karne mein

  • Current draw trend dekhne mein

  • Boot attempt identify karne mein

  • Cycling detect karne mein

  • Abnormal load ko clue ke taur par dekhne mein


2. Current Draw Fault Code Nahi

Ek exact current reading:

KISI SPECIFIC IC KA UNIVERSAL CODE NAHI

Same current:

Different models par different meaning rakh sakta hai.


3. Same Model Comparison Best

Best reference:

Same model.

Same board revision.

Same state.

Known-good board.


4. Safe Connection Rule

Bench supply sirf:

  • Documented board input

  • Known safe battery/input terminals

  • Manufacturer-compatible low-voltage conditions

par use karo.


5. Unknown Rail par Supply Mat Lagao

Do not connect bench supply randomly to:

  • CPU rail

  • RAM rail

  • UFS rail

  • Camera rail

  • Display rail

  • RF rail


6. Lithium Battery Bypass Nahi

Bench supply ko battery cell direct charging tool mat banao.

Do not:

  • Open battery

  • Direct-charge cell

  • Bypass BMS/protection

  • Feed damaged battery


7. Damaged Battery Rule

Swollen, punctured, overheated ya damaged battery:

STOP

Safe replacement/service required.


8. Mains Charger Repair Separate Hai

This chapter smartphone low-voltage board diagnosis ke liye hai.

Exposed mains adapter/charger internals par live testing nahi.


9. Current Limit Concept

Current limiting supply board ko uncontrolled current se protect karne mein help karti hai.

Lekin correct safe limit:

Device/model/input design par depend karti hai.

Universal number memorize mat karo.


10. Bench Supply Display

Usually shows:

  • Voltage

  • Current

Sometimes:

  • Power

  • Limit mode


11. CV

CV:

Constant Voltage

Supply selected voltage maintain karti hai within limit.


12. CC

CC:

Constant Current

Current limit reached hone par supply current restrict karti hai.


13. CC Mode ka Meaning

Agar supply immediately current-limit mode mein chali jaye:

Board/input abnormal load possible.

But correct input setup first verify karo.


14. Board Connection Before Power

Before connecting:

  • Polarity confirm

  • Correct terminals confirm

  • No accidental short

  • Board stable on bench


15. Reverse Polarity

Wrong polarity board ko damage kar sakti hai.

Never guess connector polarity.


16. Current Draw ke Main States

Useful conceptual states:

State A

No connection response.

State B

Low idle/standby activity.

State C

Power-key press response.

State D

Boot current progression.

State E

Stable boot.

State F

Cycling/collapse.


17. Zero Current

If correctly connected board shows no meaningful response:

Possible:

  • Open input path

  • Input connector fault

  • Fuse/path

  • Supply not actually reaching board


18. Zero Current ≠ CPU Fault

CPU tak pahunchne se pehle input path check karo.


19. Input Path Formula

SUPPLY INPUT → CONNECTOR → PROTECTION → MAIN RAIL → PMIC


20. Standby Current Concept

Some boards connected hone par immediately small standby activity show kar sakte hain.

Exact value model-specific.


21. Standby Activity Kahan Se?

Possible:

  • PMIC always-on

  • EC-like control logic

  • RTC/always-on domains

  • Charger/power controller


22. No Standby Activity

If model normally standby draw show karta hai:

Check:

Main rail.

PMIC input.

Always-on rails.


23. Power-Key Press

Power key press ke baad current behavior change hona chahiye if startup request accepted.


24. No Current Change on Power Key

Possible:

  • Power-key flex

  • PWR_KEY signal

  • PMIC control

  • Standby system


25. Power-Key Signal Check

Use multimeter/scope on documented safe test point.

Button press se logic transition verify karo.


26. Current Rises then Returns Immediately

Board startup attempt karta hai but sequence sustain nahi hoti.


27. First Question

KONSI RAIL PEHLE GIRTI HAI?

Current pattern alone se answer mat guess karo.


28. Current Pulse

Brief current pulse can indicate:

  • PMIC startup attempt

  • Rail sequencing

  • CPU initialization attempt


29. Repeated Pulses

Could indicate:

  • Boot loop

  • Protection cycling

  • Peripheral fault

  • Power instability


30. Repeated Pulse ka Best Tool

Oscilloscope + rail measurement.

Current trend ko rail collapse ke saath correlate karo.


31. Current Pattern + Voltage Rails

Professional diagnosis:

Current says:

“Something happened.”

Rail tells:

“Where sequence stopped.”


32. Current Pattern + USB Detection

Example:

Current activity + low-level USB detection:

CPU/boot ROM activity to some extent present.


33. Current Pattern + Logo

Logo appears:

Significant boot progress.

Current value alone less important.


34. Current Pattern + Recovery

Stable recovery:

CPU/RAM/storage/USB functioning significantly.


35. High Current Immediately on Connection

Possible abnormal load/short.

Before power button.


36. Immediate High Draw Workflow

Disconnect power.

Then:

MAIN RAIL RESISTANCE → NET MAP → BRANCH ISOLATION


37. Don't Keep Power Applied to Abnormal Load

If board unexpectedly draws heavily or heats:

Stop and investigate.


38. Heat Location

Thermal camera can help.

But:

HOTTEST COMPONENT ≠ AUTOMATIC ROOT CAUSE


39. PMIC Hot in High Draw

Could be supplying downstream short.


40. Charger IC Hot

Could be system-side load.


41. RF PA Hot

Could be main/input rail issue or internal load.

Need rail mapping.


42. Capacitor Hot

If one MLCC abnormal on confirmed short rail:

Strong clue.


43. Static High Current

Current remains high immediately after connection without boot request.

Strong abnormal main-input load clue.


44. Dynamic High Current

High current during boot/use can be normal depending state.

Context matters.


45. Idle Current vs Boot Current

Do not compare:

Idle phone current

with

Booting phone current.


46. Screen Changes Current

Display ON naturally increases load.


47. Brightness Changes Current

LCD/OLED brightness affects consumption.


48. Cellular Changes Current

Network search/transmit creates dynamic current.


49. Camera Changes Current

Camera opens:

ISP + camera rails + display + CPU load.


50. Flash Changes Current

Flash LED can create short high-load event.

Weak battery/power path may fail here.


51. Speaker Changes Current

High-volume loudspeaker can increase load.


52. Gaming Changes Current

CPU/GPU/display/RF all active.


53. Known-Good Comparison Rule

Same model.

Same brightness.

Same network.

Same boot state.

Then comparison meaningful.


54. Current Draw Pattern Categories

Rather than memorizing numbers, memorize shapes:

Pattern A — Flat Zero

Pattern B — Standby Only

Pattern C — Brief Pulse

Pattern D — Rise then Collapse

Pattern E — Repeating Cycle

Pattern F — Progressive Boot

Pattern G — High Static Draw


55. Pattern A — Flat Zero

Correct input connected.

No meaningful draw.

Investigate:

  • Input path

  • Protection

  • PMIC input


56. Pattern B — Standby Only

Standby exists.

Power key press gives no change.

Investigate:

Power key/control.


57. Pattern C — Brief Pulse

Startup request accepted.

Then sequence stops quickly.

Investigate first startup rails.


58. Pattern D — Rise then Collapse

More stages start.

Then failure shuts system down.

Use:

FIRST FALLING RAIL


59. Pattern E — Repeating Cycle

Possible boot loop/protection retry.

Observe frequency/pattern and corresponding rail.


60. Pattern F — Progressive Boot

Current changes through multiple stages and reaches stable operating condition.

Likely normal boot behavior.


61. Pattern G — High Static Draw

Before boot request current already abnormal.

Think main-rail/input load.


62. Current Freeze at Same Stage

If current progression repeatedly stops at same stage:

Useful clue.

But map to electrical events.


63. “Stuck at 0.xxA” Rule

Never diagnose an IC only from current number.


64. Why Internet Current Charts Can Mislead

Different:

  • SoC

  • PMIC

  • Screen

  • Modem

  • Firmware

  • Board revision

change current behavior.


65. Current Values Are Model Specific

A number normal on one phone may be abnormal on another.


66. Current Trend More Valuable

Ask:

Did it:

  • Rise?

  • Pulse?

  • Cycle?

  • Collapse?

  • Stabilize?


67. Dead Android Example

Connection:

Standby response present.

Power key:

Current rises briefly.

Then zero.

Next

Check startup rails.


68. Dead Android Example 2

Connection:

No current.

Main rail at board:

Absent.

Root Direction

Input path before PMIC.


69. Android Boot Loop Example

Current cycles.

Logo cycles.

Battery known-good.

Next

Power rail first-falling analysis + boot stage.


70. iPhone No-Power Example

Main input present.

Always-on rails present.

Power request recognized.

Startup activity appears.

USB low-level detection present.

Conclusion

Not simple PMIC/no-power.

Move boot-chain diagnosis.


71. iPhone Current Pattern Rule

Do not memorize a specific amp value as:

“NAND current.”

“NAND current” universal concept nahi.


72. Storage Fault Current Behavior

Storage fault can produce various current patterns depending failure mode.

Need:

  • Storage rails

  • Reset

  • Clock

  • Recovery/restore behavior


73. CPU Fault Current Behavior

Same.

No universal CPU-fault amp value.


74. RAM Fault

Can prevent boot progression.

Current pattern alone can't prove RAM.


75. Peripheral Fault Current

Shorted camera/display/sub-board may distort boot current.


76. Peripheral Isolation

Power off.

Disconnect suspect removable module.

Re-test behavior.


77. Current Pattern Changes after Module Removal

Strong diagnostic evidence.


78. Example

With display:

Board cycles.

Without display:

USB boot detected.

Direction

Display/module rail loading.


79. Camera Example

Camera connected:

Boot/restart fault.

Camera disconnected:

Stable.

Direction

Camera subsystem.


80. Charging Sub-Board Example

Sub-board connected:

High standby load.

Known-good sub-board:

Normal.

Root Direction

Original sub-board.


81. Current Draw and Shorts

Main-rail short investigation mein:

Resistance testing first.

Current supply observation secondary clue.


82. Blind Voltage Injection Nahi

Unknown short rail par random voltage inject mat karo.

This course rail mapping and safe documented input diagnosis follow karta hai.


83. Safe Short Diagnosis

POWER OFF → RESISTANCE → BOARDVIEW → BRANCH → COMPONENT


84. Power Supply ≠ Short Finder Only

It is mainly controlled input/current observation tool.


85. Boot-Stage Mapping

Current event ko boot stage ke saath correlate karo:

Input

↓

Standby

↓

Power request

↓

PMIC startup

↓

SoC

↓

RAM/storage

↓

Display

↓

OS.


86. Current Before Power Key

Represents input/standby state.


87. Current after Power Key

Represents startup sequence.


88. Current with Logo

Represents later boot stage.


89. Current at Home Screen

Represents full system + varying load.


90. Sleep Current Concept

Phone screen OFF aur stable hone ke baad lower-power state mein jana chahiye.


91. Sleep Current Varies

No universal sleep amp figure.

Use same-model reference.


92. Doesn't Enter Sleep

Current remains elevated.

Could be:

  • Software

  • Network

  • USB

  • Sensor

  • Hardware leakage


93. Airplane Mode Comparison

If sleep consumption improves:

Cellular/network activity direction.


94. Screen-Off Comparison

If load drops significantly:

Normal display/system contribution.


95. USB Cable Can Keep Device Awake

Connected USB/data state can prevent deepest sleep.


96. Measurement Conditions Document Karo

Always note:

  • Screen state

  • Wi-Fi

  • SIM

  • Boot stage

  • USB

  • Charger

  • Battery


97. Current Draw Recording Sheet

Model: __________

Input Setup: __________

Initial Draw: __________

Power-Key Response: __________

Boot Progress: __________

Peak/Pattern: __________

Stable State: __________

Cycle: Yes / No

Heating Area: __________

First Falling Rail: __________

Final Direction: __________


98. No-Power Power-Supply Worksheet

Main Input Present: __________

Initial Current Response: __________

PMIC Input: __________

Standby Rails: __________

Power Key: __________

Startup Rails: __________

USB Detection: __________

First Missing Stage: __________


99. Boot-Loop Worksheet

Battery Known-Good: __________

Current Cycle: __________

Logo: __________

Recovery: __________

Rail 1: __________

Rail 2: __________

First Falling Rail: __________

Peripheral Isolation: __________

Root Direction: __________


100. Sleep/Drain Worksheet

Phone Booted: __________

Screen Off: __________

Network State: __________

Current Trend: __________

Sleep Reached: __________

Airplane Mode Difference: __________

Warm Area: __________

Root Direction: __________


101. Case Study — Zero Draw

Correct Board Input

Confirmed.

Input connector

Voltage present before fuse.

After fuse

Missing.

Root

Open input path/fuse area.

Lesson

Zero current can be input-open, not CPU.


102. Case Study — Standby but No Start

Initial

Standby current pattern.

Power Button

No change.

PWR_KEY

No transition.

Known-Good Flex

Works.

Root

Power-key flex.


103. Case Study — Startup Pulse

Power Button

Accepted.

Current

Brief rise then collapse.

Standby

Stable.

Startup Rail

One secondary rail missing.

Direction

Startup regulator/load.


104. Case Study — Repeated Cycling

Current

Regular repeated cycle.

Scope

One storage rail appears then collapses first.

Enable

Remains active initially.

Direction

Storage rail/load/regulator.


105. Case Study — Current Cycle after Screen Change

History

Screen replaced.

With Screen

Board cycles.

Screen disconnected

Board boots/detects.

Root

Replacement screen/module loading rail.


106. Case Study — High Static Draw

Immediately Connected

Unexpected high load.

Power Removed

Main rail resistance abnormal.

Net Map

One MLCC branch short.

Root

Main-rail capacitor.


107. Case Study — PMIC Hot

Current

High static.

PMIC

Warmest.

Output Rail

Shorted.

Peripheral Removed

Rail normal.

Root

Peripheral, not PMIC.


108. Case Study — Boot Current Normal but Screen Black

Board

Boot progression normal.

Incoming Call

Works.

Known-Good OLED

Works.

Root

Display.

Lesson

Current cannot replace functional testing.


109. Case Study — High Current only Camera Open

Idle

Normal.

Camera Open

Current rises and phone restarts.

Battery

Known-good.

Camera Rail

Collapses.

Known-Good Camera

Stable.

Root

Camera module.


110. Case Study — High Load During Call

Idle

Normal.

Cellular Call

Restart.

Known-Good Battery

Solves.

Root

Battery unable to support RF load.


111. Case Study — Sleep Drain

Home Screen

Normal.

Screen OFF

Current remains elevated.

Airplane Mode

Drops significantly.

Signal

Very poor.

Root

Network search/activity.


112. Case Study — Hardware Sleep Drain

Screen OFF

High load.

Airplane Mode

No change.

Warm Area

Charging sub-board.

Known-Good Sub-Board

Normal sleep.

Root

Sub-board leakage.


113. Case Study — Software Keeps CPU Awake

Board

No electrical abnormalities.

SoC

Warm in idle.

Battery Usage

Heavy background app.

Software Correction

Sleep behavior returns.

Root

Software.


114. Current Draw + Multimeter

Use current behavior to decide:

Which rail should be measured next.


115. Current Draw + Scope

Best for:

  • Short pulses

  • Startup timing

  • Cycling

  • Rail collapse


116. Current Draw + BoardView

Map first missing/collapsing rail to consumers.


117. Current Draw + Thermal

Use only after electrical context.


118. Current Draw + Known-Good Board

Best training method:

Compare identical boot sequence side-by-side conceptually.


119. Current Draw Training Exercise

On working dead practice boards/known-good samples:

Observe difference between:

  • Connected

  • Power-key pressed

  • Booting

  • Screen on

  • Sleep

without modifying unknown rails.


120. Don't Intentionally Create Shorts

Training ke liye board ko damage karke fault create mat karo.

Use naturally faulty practice boards.


121. Current Draw and Previous Repair

If current abnormal after board rework:

Touched area first inspect.


122. Current Draw after Liquid

Unexpected idle/static draw can indicate leakage.


123. Current Draw after Drop

Could involve:

  • Board crack

  • Connector short

  • Peripheral damage


124. Current Draw after Firmware Update

If electrical sequence stable:

Software/boot stage may be relevant.


125. Power Supply Does Not Replace Battery Test

Some faults only appear with real battery data/temperature/communication.


126. Battery Data Lines

Bench supply cannot automatically reproduce:

  • Temperature

  • ID

  • Smart battery communication


127. Therefore

If device requires battery communication:

Use known-good compatible battery as primary test.


128. Power Supply and Charging Diagnosis

Bench supply at board battery input does not fully test USB charging path.

Charging should be tested from actual supported USB source.


129. Power Supply and RF

Bench current rise during RF use can show load behavior.

It cannot analyze actual RF signal quality.


130. Power Supply and Audio

High-volume audio increases dynamic load.

Doesn't diagnose amp itself.


131. Power Supply and Display

Screen brightness changes current.

Doesn't prove MIPI/backlight correctness.


132. Power Supply Limitations

It tells:

HOW MUCH INPUT CURRENT SYSTEM IS REQUESTING

It does not directly tell:

WHICH EXACT IC IS BAD


133. Master Interpretation Rule

If current abnormal:

Ask:

At what state?

After what trigger?

Which rail changed?

Which module is active?

Which rail falls first?


134. “No Current” Diagnostic Tree

Correct input?

↓

Input reaches board?

↓

Protection/fuse?

↓

Main rail?

↓

PMIC input?

↓

Standby.


135. “Standby Only” Diagnostic Tree

Standby good.

↓

Power key transition?

↓

Startup command?

↓

PMIC startup outputs.


136. “Pulse then Zero” Diagnostic Tree

Startup requested.

↓

Which startup rail appears?

↓

Which expected rail is first missing?

↓

Clock/reset/CPU stage.


137. “Repeated Cycle” Diagnostic Tree

Battery/input stable?

↓

First falling rail?

↓

Peripheral isolation?

↓

Boot-stage/firmware.


138. “High Static Draw” Diagnostic Tree

Disconnect.

↓

Resistance check.

↓

Main rail/net identify.

↓

Branch isolate.

↓

Component confirm.


139. “High Idle Draw” Diagnostic Tree

Phone truly asleep?

↓

Software/background?

↓

Airplane comparison?

↓

Heat?

↓

Active/leaking rail.


140. Common Beginner Mistake 1

Current number ko exact IC code samajhna.


141. Common Beginner Mistake 2

Wrong input terminals use karna.


142. Common Beginner Mistake 3

Battery voltage/data requirements ignore karna.


143. Common Beginner Mistake 4

High current dekh kar board ko powered chhor dena.


144. Common Beginner Mistake 5

Hottest IC immediately remove karna.


145. Common Beginner Mistake 6

Current pattern without rail measurement diagnose karna.


146. Common Beginner Mistake 7

Unknown secondary rail par power inject karna.


147. Common Beginner Mistake 8

USB charging fault ko bench battery-input test se fully prove samajhna.


148. Common Beginner Mistake 9

Same current value ko every model par same meaning dena.


149. Common Beginner Mistake 10

Known-good battery test skip karna.


150. DC Supply Golden Rules

1. Correct documented board input only.

2. Correct polarity first.

3. Controlled current limiting use karo.

4. Current number universal fault code nahi.

5. Current behavior/sequence observe karo.

6. High static draw par power remove karke resistance test karo.

7. Cycling mein First Falling Rail find karo.

8. Known-good battery ko ignore mat karo.

9. Unknown rails par blind power injection mat karo.

10. Current pattern ko schematic + multimeter + scope ke saath interpret karo.


151. Master Current Draw Formula

CONNECTION

↓

STANDBY

↓

POWER REQUEST

↓

STARTUP CURRENT

↓

BOOT PROGRESSION

↓

STABLE / COLLAPSE


152. Master No-Power Formula with Supply

INPUT CURRENT → MAIN RAIL → STANDBY → PWR_KEY → STARTUP RAILS → BOOT


153. Master Cycling Formula

CURRENT CYCLE → FIRST FALLING RAIL → NET → LOAD → ROOT CAUSE


154. Master High-Current Formula

STOP POWER → RESISTANCE → NET MAP → BRANCH → COMPONENT


155. Master Sleep Formula

BOOT → SCREEN OFF → SLEEP EXPECTATION → ACTIVE BLOCK → ROOT CAUSE


156. Part 34 ka Sabse Important Lesson

DC power supply ka purpose ye nahi ke display par:

“0.xx A”

dekho aur foran IC ka naam bolo.

Professional technician dekhta hai:

CURRENT KAB START HUA?

POWER KEY KE BAAD KYA BADLA?

CURRENT RISE HUI YA PULSE?

BOOT KITNA AAGE GAYA?

CURRENT KIS EVENT PAR COLLAPSE HUI?

Phir multimeter/scope se:

FIRST MISSING / FIRST FALLING RAIL

find karta hai.

Final rule:

CURRENT DRAW = CLUE

RAIL/SIGNAL MEASUREMENT = EVIDENCE

ISOLATION + REPAIR RESULT = CONFIRMATION


Mobile Advanced Extension — Part 34 Complete

Next — Part 35

Advanced Smartphone Component Testing Mastery

Part 35 mein hum ek complete component-testing reference banayenge:

  • Resistor

  • Zero-ohm resistor

  • Pull-up / pull-down

  • Capacitor

  • MLCC short

  • Coil/inductor

  • Ferrite bead

  • Diode

  • TVS/ESD

  • MOSFET

  • Fuse

  • Crystal/oscillator concepts

  • LDO

  • Buck regulator

  • Boost regulator

  • Load switch

  • Connector/filter arrays

  • Component in-circuit vs out-of-circuit testing

  • Known-good comparison

  • Common false readings

Master formula:

COMPONENT IDENTIFY → CIRCUIT ROLE → SAFE METER MODE → IN-CIRCUIT INTERPRETATION → KNOWN-GOOD COMPARE → CONFIRM

Post a Comment

0 Comments