FORUMS
Remove All Ads from XDA

[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]

4,824 posts
Thanks Meter: 19,218
 
Post Reply Email Thread
3rd November 2019, 12:44 AM |#21  
superdragonpt's Avatar
OP Recognized Developer
Flag Lisbon / Taiwan / USA
Thanks Meter: 19,218
 
Donate to Me
More
Quote:
Originally Posted by Trubbs

Installed rom without issue, good instructions

I also get problems waking device, in fact always have to reboot. Main reason to install was to allow netflix downloads however it appears that is a deeper issue than just android version, possibly architecture. But it does allow install of kodi so positive there. Main use is entertainment device in my car during lunch break.

Also have weird keyboard issues, double key entry type android get androoid and random other key presses miles away from where my fat fingers are pressing.

Great work so far otherwise, thanks

Let me know if I can assist dev with any test or info.

Cheers


The low ram, seems to be the issue here.


Installing GAPPS makes the device very slow, when handling some big apps/ resource ungry apps...

without GAPPS, device is smooth.

So, my latest work lately, had been around optimizating all i can, concerning ram usage and resources...

Google APPS, have been such an resource ungry, over the years, it's an shame

cheers
The Following User Says Thank You to superdragonpt For This Useful Post: [ View ]
3rd November 2019, 01:13 AM |#22  
Trubbs's Avatar
Member
Thanks Meter: 20
 
More
Quote:
Originally Posted by superdragonpt

The low ram, seems to be the issue here.
...

Google APPS, have been such an resource ungry, over the years, it's an shame

cheers

Sorry just to be clear netflix downloads is a software issue something to do with trusted platform. Also i had same wake issue on 1st install with no gapps and yes definitely more fluid interface / opening apps.

I then did factory reset, flashed pico open gapps and formatted cache and dalvik.
3rd November 2019, 09:47 PM |#23  
superdragonpt's Avatar
OP Recognized Developer
Flag Lisbon / Taiwan / USA
Thanks Meter: 19,218
 
Donate to Me
More
Build: 20191103
  • GPU PowerVR SGX 544: Update driver & DDK update from 2204701 > 2564405
  • LCM: nt35521_dsi_vdo: Improved Gamma / color
  • cpufreq & HotPlug Mechanism Backport from MTK KitKat
  • Reverted ASMP
  • Charger: BQ24156: Corrections: in some scenarios (thermal) current was too low to init charging
  • LCM: nt35521_dsi_vdo: More reverse engineering done ( greatly improved resume, suspend, etc)
  • Other Kernel optimizations, check github for full list
  • Fixed and enabled HWC (hardware composer)
  • ART: improvements for low ram devices
  • Many low ram optimizations
  • Frameworks: tune for Faster app switching
  • Frameworks: tune System Animations for low ram
  • Frameworks: tune Scrolling, velocitytracker, other system animations









F.A.Q. also updated




cheers
The Following 3 Users Say Thank You to superdragonpt For This Useful Post: [ View ]
3rd November 2019, 10:17 PM |#24  
Senior Member
Flag Android
Thanks Meter: 530
 
More
Thumbs up
Big thumbs up! Great work man.
The Following User Says Thank You to tweakradje For This Useful Post: [ View ] Gift tweakradje Ad-Free
3rd November 2019, 11:36 PM |#25  
Trubbs's Avatar
Member
Thanks Meter: 20
 
More
Quote:
Originally Posted by superdragonpt

Build: 20191103


cheers

Nice one!

Ok to dirty flash over original or clean install recommended?
The Following User Says Thank You to Trubbs For This Useful Post: [ View ] Gift Trubbs Ad-Free
4th November 2019, 12:41 AM |#26  
Senior Member
Flag Android
Thanks Meter: 530
 
More
After resume from standy I have black screen with 20191103
logcat screen on:
Code:
I/PowerManagerService(  482): Waking up from sleep (uid 1000)...
D/lights  (  482): write_int open fd=164
V/KeyguardServiceDelegate(  482): onScreenTurnedOn(showListener = [email protected])
I/DisplayPowerController(  482): Blocking screen on until initial contents have been drawn.
D/Sensors (  482): activate handle =0, enable = 1
D/Sensors (  482): use new sensor index=1, mSensors[index](5f861000)
D/Accel   (  482): ACC enable: handle:0, en:1
D/Accel   (  482): path:/sys/class/misc/m_acc_misc/accactive
D/Accel   (  482): no ACC enable control attr
D/Sensors (  482): use old sensor err(-1),index(1) go to old hwmsen
D/Hwmsen_sensors(  482): Hwmsen_Enable: handle:0, en:1
D/Hwmsen_sensors(  482): virtual int Hwmsen::enable(int32_t, int): handle 0, enable or disable 1!
D/Hwmsen_sensors(  482): active_sensors =1
D/Accel   (  482): setDelay: (handle=0, ns=66667000)
D/Accel   (  482): no ACC setDelay control attr
E/Sensors (  482): new acc setDelay handle(0),ns(66667000) err! go to hwmsen
D/Hwmsen_sensors(  482): setDelay: (handle=0, ns=66667000)
D/Hwmsen_sensors(  482): setDelay: (what=0, ms=66)
D/Hwmsen_sensors(  482): really setDelay: (what=0, ms=66)
D/Accel   (  482): setDelay: (handle=0, ns=66667000)
D/Accel   (  482): no ACC setDelay control attr
E/Sensors (  482): new acc setDelay handle(0),ns(66667000) err! go to hwmsen
D/Hwmsen_sensors(  482): setDelay: (handle=0, ns=66667000)
D/Hwmsen_sensors(  482): setDelay: (what=0, ms=66)
D/Hwmsen_sensors(  482): really setDelay: (what=0, ms=66)
V/KeyguardServiceDelegate(  482): **** SHOWN CALLED ****
D/PowerManagerService-JNI(  482): Excessive delay in autosuspend_disable() while turning screen on: 332ms
W/art     (  482): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService$2.onDisplayStateChange(int) from PowerManagerService.java:2191 wai
W/art     (  482): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService$2.onDisplayStateChange(int) from PowerManagerService.java:2191 wai
W/art     (  482): Long monitor contention event with owner method=void com.android.server.power.PowerManagerService$2.onDisplayStateChange(int) from PowerManagerService.java:2191 wai
D/SurfaceFlinger(  131): Set power mode=2, type=0 flinger=0x40c82000
I/hwcomposer_v1.0(  131): [HWC] Blank(0) Display(0)
I/DisplayManagerService(  482): Display device changed: DisplayDeviceInfo{"Ingebouwd scherm": uniqueId="local:0", 800 x 1280, 60.000004 fps, supportedRefreshRates [60.000004], density
W/art     (  482): Long monitor contention event with owner method=void com.android.server.wm.WindowManagerService$H.handleMessage(android.os.Message) from WindowManagerService.java:7
V/ActivityManager(  482): Display changed displayId=0
I/BeaconBle(  991): Client requested scan, settings=BleSettings [scanMode=LOW_LATENCY, callbackType=ALL_MATCHES, reportDelayMillis=0, 5 filters, 1 clients, callingClientName=Nearby]
I/DisplayPowerController(  482): Unblocked screen on after 392 ms
D/lights  (  482): write_int open fd=224
I/BeaconBle(  991): 'L' hardware scan: 5 filters, scanMode=2, reportdelay=0, callback type=1, #clients=1, workSource=WorkSource{10019 com.google.android.gms}
E/WifiStateMachine(  482): cancelDelayedScan -> 80
D/wpa_supplicant( 1063): wlan0: Control interface command 'SIGNAL_POLL'
The Following User Says Thank You to tweakradje For This Useful Post: [ View ] Gift tweakradje Ad-Free
4th November 2019, 09:00 PM |#27  
Member
Thanks Meter: 3
 
More
I also have a black screen after waking up. You can see that the backlight turns on but no image.
5th November 2019, 02:16 AM |#28  
superdragonpt's Avatar
OP Recognized Developer
Flag Lisbon / Taiwan / USA
Thanks Meter: 19,218
 
Donate to Me
More
Well for the LCM driver variant my device uses, all is way better now


for the people that started having black screen on resume on this second build:




https://www.androidfilehost.com/?fid...26312261618854


https://www.androidfilehost.com/?fid...26312261618856




This are two new test kernels, just flash in recovery
this are total experimental, as i dont have this LCM version on my device


test one, boot up and check


do the same for the second



These are based from logs people provided me, and also some reverse engineering


PS: if by any chance these kernels;
Get stuck on bootlogo
Boots but with just an white screen
Boots but with just black screen or any other weird artifacts

--> just press power button for ~10 seconds to force power off
--> just boot to recovery again, and flash again any working ROM

cheers
The Following User Says Thank You to superdragonpt For This Useful Post: [ View ]
5th November 2019, 11:03 AM |#29  
Senior Member
Flag Android
Thanks Meter: 530
 
More
@superdragonpt LCM88 booted OK. But still the black screen on resume.
What info do you need from my tablet?
The Following User Says Thank You to tweakradje For This Useful Post: [ View ] Gift tweakradje Ad-Free
5th November 2019, 12:57 PM |#30  
superdragonpt's Avatar
OP Recognized Developer
Flag Lisbon / Taiwan / USA
Thanks Meter: 19,218
 
Donate to Me
More
Quote:
Originally Posted by tweakradje

@superdragonpt LCM88 booted OK. But still the black screen on resume.
What info do you need from my tablet?

If you know how to take logat ( adb > logcat)
Please start a log before you turned off the screen. Then turn off the screen for like 30 seconds, and wake it up

The second kernel , didn't boot?
That would help, thanks
5th November 2019, 06:54 PM |#31  
Senior Member
Flag Android
Thanks Meter: 530
 
More
Quote:
Originally Posted by superdragonpt

If you know how to take logat ( adb > logcat)
Please start a log before you turned off the screen. Then turn off the screen for like 30 seconds, and wake it up

The second kernel , didn't boot?
That would help, thanks

Only LCM88 booted.

LCM88 logcat attached. Added dmesg from boot and one screen off/on.

Why is Recovery and your kernel have 180 degrees rotation? Just before turn off it flips back.
Cannot be corrected in kernel?
Attached Files
File Type: txt _logcat.txt - [Click for QR Code] (96.7 KB, 16 views)
File Type: zip _dmesg.zip - [Click for QR Code] (115.2 KB, 6 views)
The Following User Says Thank You to tweakradje For This Useful Post: [ View ] Gift tweakradje Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes