Related
Heya,
I have no idea how to put this without making me sound like an idiot, but here's what happened.
I was running CM10.1, stock kernel, beta 9 (I think...) and messed around in the settings a bit.
Here's what I changed
- disabled zRam
- allow purging of assets
- CPU governor to interactive
- min freq to 350mhz (the main issue I had was sound skipping when listening to music, I wanted to see if it's a CPU issue)
--> Phone reboot.
Result: CM boot animation comes up for a few seconds and the screen suddenly becomes garbled and all weird (but the CM logo is still there, just a lot more glitchy and not animated anymore)
Since I have backups of all files I felt like this was the perfect moment to update my CM10.1 to a newer version, now that I have screwed the system in some way. Booted into recovery, placed zips on the SD, did the whole update process, flashed boot.img etc. etc. aaaand:
Same thing.
Reflashed everything, wiped everything, praised cthulhu, tried out different roms, different kernels, I even flashed my failsafe nand backup from summer last year and it had the same issue. The only difference was that CM10.1 roms were the only ROMs that showed the garbled screen, PA, stock etc. only stopped the boot animation and rebooted.
So I gave up for the day and plugged it into the wall charger - lo and behold, it works. It boots up, runs stable, everything.
So the situation now is as follows:
My phone gets stuck on boot and reboots immediately.
My phone boots perfectly well and runs like normal if its connected to a charger.
My phone also boots perfectly well and runs like normal if its connected to a PC, USB storage works, too.
As soon as I unplug the USB cable, the phone just freezes and after a minute or so it reboots.
And I have absolutely no idea what to do. Can anyone help?
Odp: [Q] HOX needs an umbillical cord, and I think that's just wrong
Try to lock bootloader and run RUU, see if it helps if yes, then unlock vootloader and flash cyanogenmod from scratch, wipe everything, flash only kernel, cm10.1 and gapps, and see if it boots
Sent from my HTC One X.
POLSKAAAAAA BIAAAALOOOO CZEEEERWONIIIII!!!!!!!!!
Experienced something similar on another phone, I resolved it by redownloading the file, fastboot erase boot and re-flashing the boot due to a corrupt file. Either that or sacrifice your next of kin to Cthulhu, always works.
gallardo5 said:
Try to lock bootloader and run RUU, see if it helps if yes, then unlock vootloader and flash cyanogenmod from scratch, wipe everything, flash only kernel, cm10.1 and gapps, and see if it boots
Sent from my HTC One X.
POLSKAAAAAA BIAAAALOOOO CZEEEERWONIIIII!!!!!!!!!
Click to expand...
Click to collapse
Thing is, I'm on Linux so running RUU is out of the question. I could try to flash a stock nandroid backup but I'm really wondering whether flashing anything at all is really going to help.
It seems like I changed or corrupted something that persists no matter what ROM or kernel I use, I may try to up- or downgrade the HBOOT (is downgrading even possible? Time to find out!) because thats the only thing I'm aware of that doesn't change with ROM and kernel flashes.
However, I'm anxious to screw it even further so I'm kinda hoping that somebody replies who knows _exactly_ what is wrong, gives me a hug, wipes away my tears and tells me how easy and trivial it is to fix this.
A boy can dream, right?
sinkster said:
Experienced something similar on another phone, I resolved it by redownloading the file, fastboot erase boot and re-flashing the boot due to a corrupt file. Either that or sacrifice your next of kin to Cthulhu, always works.
Click to expand...
Click to collapse
Tried it, unfortunately no change. Although fastboot didn't allow me to erase boot, but I think thats normal with the HOX.
Aw jeez why do I always have to monkey around in the settings...
Minor update (and editing doesn't work for some reason...)
With stock O2 Germany JB 4.1.1 rom the phone gets to the initial lockscreen only to freeze there. So it seems like it boots properly but then something goes off the rails.
Also, when booting the phone plugged in (y'know, to actually use it) and then unplugging it, I have about 5 seconds of normal usage until the phone freezes again. So it's not instantaneous.
However, a bigger question came to me: What could be the relevant log files for this? I want to troubleshoot it myself since I'm pretty sure that this is a unique thing, but I don't know what logs I need to check.
I already looked in kmesg and last_kmesg but I can't see anything abnormal in there, no "xx failed", no "error!".
Install adb wireless (needs root), launch it and type on your PC's adb cmd prompt:
adb connect xxx.xxx.xx.xx (example: 192.168.0.10, the app tells you the exact ip)
adb logcat -v long > C:\log.txt
Now do the action that causes it to freeze and wait a moment
then press ctrl+c to terminate and take a look at the log file.
TToivanen said:
Install adb wireless (needs root), launch it and type on your PC's adb cmd prompt:
adb connect xxx.xxx.xx.xx (example: 192.168.0.10, the app tells you the exact ip)
adb logcat -v long > C:\log.txt
Now do the action that causes it to freeze and wait a moment
then press ctrl+c to terminate and take a look at the log file.
Click to expand...
Click to collapse
Did that twice, results look like this:
Plug pulled at 15:39
Code:
[ 03-26 15:39:00.037 463: 515 D/PowerManagerService ]
acquireWakeLock(415967c0): PARTIAL_WAKE_LOCK , tag=AlarmManager, flags=0x1, pid=463, uid=1000, mUserState=0x3
[ 03-26 15:39:00.047 463: 515 V/AlarmManager ]
sending alarm PendingIntent{4182c148: PendingIntentRecord{41890d00 android broadcastIntent}}, intent=android.intent.action.TIME_TICK, type=RTC, count=1, when=1364308740000, repeateInterval=0
[ 03-26 15:39:00.142 463: 485 D/PowerManagerService ]
releaseWakeLock(415967c0): PARTIAL_WAKE_LOCK , tag=AlarmManager, flags=0x1
[ 03-26 15:39:02.272 463: 545 D/StateMachine ]
handleMessage: E msg.what=131155
[ 03-26 15:39:02.272 463: 545 D/StateMachine ]
processMsg: ConnectedState
[ 03-26 15:39:02.277 463: 545 D/WifiStateMachine ]
ConnectedState{ what=131155 when=-4ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {418c0fb8} arg1=5 }
[ 03-26 15:39:02.277 463: 545 D/StateMachine ]
processMsg: L2ConnectedState
[ 03-26 15:39:02.277 463: 545 D/WifiStateMachine ]
L2ConnectedState{ what=131155 when=-5ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {418c0fb8} arg1=5 }
[ 03-26 15:39:02.277 566: 566 D/wpa_supplicant ]
wpa_s 0x41caa6a8 cmd SIGNAL_POLL
[ 03-26 15:39:02.277 566: 566 D/wpa_supplicant ]
RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
[ 03-26 15:39:02.277 566: 566 D/wpa_supplicant ]
ctrl_iface: SIGNAL_POLL
[ 03-26 15:39:02.287 566: 566 D/wpa_supplicant ]
nl80211: survey data missing!
[ 03-26 15:39:02.297 463: 545 D/WifiStateMachine ]
fetchRssiAndLinkSpeedNative RSSI = -55
[ 03-26 15:39:02.297 566: 566 D/wpa_supplicant ]
wpa_s 0x41caa6a8 cmd SignalStrength 7
[ 03-26 15:39:02.297 566: 566 D/wpa_supplicant ]
RX ctrl_iface - hexdump(len=16): 53 69 67 6e 61 6c 53 74 72 65 6e 67 74 68 20 37
[ 03-26 15:39:02.297 566: 566 D/wpa_supplicant ]
ctrl_iface: SignalStrength 7
[ 03-26 15:39:02.297 566: 566 D/wpa_supplicant ]
SignalStrength: =7
[ 03-26 15:39:02.327 463: 545 D/StateMachine ]
handleMessage: X
Plug pulled at 15:50:30
Code:
[ 03-26 15:50:31.821 439: 539 D/StateMachine ]
handleMessage: E msg.what=131155
[ 03-26 15:50:31.821 439: 539 D/StateMachine ]
processMsg: ConnectedState
[ 03-26 15:50:31.821 439: 539 D/WifiStateMachine ]
ConnectedState{ what=131155 when=-5ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {416cdc68} arg1=5 }
[ 03-26 15:50:31.821 439: 539 D/StateMachine ]
processMsg: L2ConnectedState
[ 03-26 15:50:31.821 439: 539 D/WifiStateMachine ]
L2ConnectedState{ what=131155 when=-6ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {416cdc68} arg1=5 }
[ 03-26 15:50:31.821 563: 563 D/wpa_supplicant ]
wpa_s 0x407d56a8 cmd SIGNAL_POLL
[ 03-26 15:50:31.821 563: 563 D/wpa_supplicant ]
RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
[ 03-26 15:50:31.821 563: 563 D/wpa_supplicant ]
ctrl_iface: SIGNAL_POLL
[ 03-26 15:50:31.831 563: 563 D/wpa_supplicant ]
nl80211: survey data missing!
[ 03-26 15:50:31.836 439: 539 D/WifiStateMachine ]
fetchRssiAndLinkSpeedNative RSSI = -45
[ 03-26 15:50:31.836 563: 563 D/wpa_supplicant ]
wpa_s 0x407d56a8 cmd SignalStrength 7
[ 03-26 15:50:31.836 563: 563 D/wpa_supplicant ]
RX ctrl_iface - hexdump(len=16): 53 69 67 6e 61 6c 53 74 72 65 6e 67 74 68 20 37
[ 03-26 15:50:31.836 563: 563 D/wpa_supplicant ]
ctrl_iface: SignalStrength 7
[ 03-26 15:50:31.836 563: 563 D/wpa_supplicant ]
SignalStrength: =7
[ 03-26 15:50:31.851 439: 539 D/StateMachine ]
handleMessage: X
Disabled WiFi to see whether there was some fault, no effect _however_ I noticed something else: If I pull the plug but leave my finger on the display and/or rub it around, the device stays responsive and awake. As soon as I lift my finger, even when it's really quick to tap something, the device freezes.
This weird behaviour definitely makes it a power manager issue in my opinion. I have this weird idea that the CPU might go to a ridiculously low level as soon as power is disconnected and no finger keeps the device awake, but I don't know what to do with that idea.
Okay so I tested around a bit and enabled every kind of tracer and debugging stuff I could find in the options and I think I found something interesting in the log.
Code:
[ 03-26 16:17:28.787 438: 505 D/PowerManagerService ]
ALG=2, lsvalue=225(4th)->320(5th), last_level=5, lValue=142->142, bValue=0, kValue=0, mPowerState=0x3, mSkippedScreenOn=false, mInitialAnimation=false, immediate=false
[ 03-26 16:17:29.992 995: 995 W/Rosie ]
closeFolder() -- Folder is null , AnimateClose? false
[ 03-26 16:17:30.267 438: 537 D/StateMachine ]
handleMessage: E msg.what=131155
[ 03-26 16:17:30.267 438: 537 D/StateMachine ]
processMsg: ConnectedState
[ 03-26 16:17:30.267 438: 537 D/WifiStateMachine ]
ConnectedState{ what=131155 when=-3ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {41aaab78} arg1=5 }
[ 03-26 16:17:30.267 438: 537 D/StateMachine ]
processMsg: L2ConnectedState
[ 03-26 16:17:30.267 438: 537 D/WifiStateMachine ]
L2ConnectedState{ what=131155 when=-3ms target=Handler (com.android.internal.util.StateMachine$SmHandler) {41aaab78} arg1=5 }
[ 03-26 16:17:30.267 561: 561 D/wpa_supplicant ]
wpa_s 0x40de36a8 cmd SIGNAL_POLL
[ 03-26 16:17:30.267 561: 561 D/wpa_supplicant ]
RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
[ 03-26 16:17:30.267 561: 561 D/wpa_supplicant ]
ctrl_iface: SIGNAL_POLL
[ 03-26 16:17:30.267 561: 561 D/wpa_supplicant ]
nl80211: survey data missing!
[ 03-26 16:17:30.267 438: 537 D/WifiStateMachine ]
fetchRssiAndLinkSpeedNative RSSI = -58
[ 03-26 16:17:30.267 438: 537 D/StateMachine ]
handleMessage: X
[ 03-26 16:17:30.477 995: 995 D/WakeLockManager ]
releaseWakeLock([email protected]) tag=RosieScroll_2
[ 03-26 16:17:30.482 438: 722 D/PowerManagerService ]
releaseWakeLock(41a460a0): CPU_MIN_NUM , tag=RosieScroll_2, flags=0x400
[ 03-26 16:17:30.482 438: 647 D/PowerManagerService ]
releaseWakeLock(41b1e900): CPU_MIN_FREQ , tag=RosieScroll_2, flags=0x100
[ 03-26 16:17:30.487 995: 995 W/dalvikvm ]
disableGcForExternalAlloc: false
Unfortunately I have absolutely no idea what the flags and commands mean so I think I'll have to hit up a kernel dev who does. Another thing I tried was a complete rollback including stock recovery and bootloader relock, which also had no effect.
At this point I think my aping around in the CPU governor and min/max freq may have caused irreparable damage to the CPU and/or power control, considering how flashing different kernels has zero effect on the issue I don't think it's a software problem anymore and I'm beginning to lose hope that it's fixable through software. If a One X has a BIOS I'd love to reset it, but I don't think it does. FYI, I also tried to disconnect the battery but HTC glued the battery onto the rest of the hardware (not just the back cover) and I will not take the risk of breaking anything any further.
Guess I'll have to upgrade to the One soon...
Clearly your phone is having difficulty setting the amount of active CPU's and assigning them a min frequency. It would imagine that you are going to get a lot more info from the kernel log.
You can acquire this by doing the following.
Unplug your phone causing it to crash.
Let it force reboot itself then plug it on to your PC.
Once booted do
Adb shell cat /proc/last_kmsg > last_kmsg.txt
This should point where the kernel is unable to continue
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
Clearly your phone is having difficulty setting the amount of active CPU's and assigning them a min frequency. It would imagine that you are going to get a lot more info from the kernel log.
Click to expand...
Click to collapse
I did what you said and the full last_kmsg is available here: http://pastebin.com/3AD6KLgT
Here's the last part, and it looks like you're right. The cores come on- and offline a couple of times (I think "1111", "1011" etc. describe which cores are online), going from 3 cores to 2 cores to 3 to 2 to 3 to 2 to 3 to 2... to 1 and ultimately just shuts the entire thing off.
I find it interesting that the cores are apparently trying to come back online but get send into NOHz mode (probably an intermediary state that gives them the "Go to bed, man!" signal), but I have no idea what to do with these information.
Code:
[ 296.343325] [CPUHP] current online: 1011
[ 296.344689] Switched to NOHz mode on CPU #2
[ 296.600621] CPU2: shutdown
[ 296.605225] [CPUHP] current online: 1001
[ 297.019427] [CPUHP] current online: 1011
[ 297.019752] Switched to NOHz mode on CPU #2
[ 297.297223] CPU3: shutdown
[ 297.300166] [CPUHP] current online: 1010
[ 298.184764] Switched to NOHz mode on CPU #3
[ 298.185364] [CPUHP] current online: 1011
[ 298.346157] CPU3: shutdown
[ 298.347751] [CPUHP] current online: 1010
[ 299.722376] [CPUHP] current online: 1011
[ 299.724604] Switched to NOHz mode on CPU #3
[ 299.896705] CPU3: shutdown
[ 299.897922] [CPUHP] current online: 1010
[ 300.629810] Switched to NOHz mode on CPU #3
[ 300.630288] [CPUHP] current online: 1011
[ 300.779935] CPU3: shutdown
[ 300.783137] [CPUHP] current online: 1010
[ 300.993123] CPU2: shutdown
[ 300.995116] [CPUHP] current online: 1000
[ 301.078096] [CPUHP] current online: 1001
[ 301.079767] Switched to NOHz mode on CPU #3
[ 302.165272] CPU3: shutdown
[ 302.166795] [CPUHP] current online: 1000
[ 302.449805] touch watchdog
[ 302.562689] cpu-tegra: force EDP limit 1400000 kHz
[ 302.563972] [CPUHP] current online: 1001
[ 302.564749] Switched to NOHz mode on CPU #3
[ 302.846416] [TMS] cpu temp = 52.50, local temp = 44
[ 303.330406] CPU3: shutdown
[ 303.333548] [CPUHP] current online: 1000
[ 303.678344] [CPUHP] current online: 1001
[ 303.679764] Switched to NOHz mode on CPU #3
[ 303.779515] CPU3: shutdown
[ 303.782713] [CPUHP] current online: 1000
7308 Corrected bytes, 8 unrecoverable blocks
Boot info:
start_on_event=none, last_off_event=pmu_poweroff
NoHZ Mode Is Normal
I done see anything that screams failure, but again im no expert with kernel debugging
there is no Kernel Panic which you would expect with a forced reboot
last_off_event=pmu_poweroff
Click to expand...
Click to collapse
I think pmu stands for Power Management Unit. Is this a normal event?
bagofcrap24 said:
NoHZ Mode Is Normal
Click to expand...
Click to collapse
Too bad...
Just flashed the stable version of xmister's kernel, same issue (fast kernel though ), then used trickster mod to change the I/O scheduler to the regular ROW mode (no effect), changed the min. freq to 1200mhz and PRAISE OUR DEEP SEA OVERLORD it keeps running without needing a cable or the touch of my finger.
Apparently the 51mhz min freq was too slow. Can't keep the phone running at this speed of course, so I'll spend the next hour or so finetuning the lowest setting that doesn't crash the phone.
Sweet jesus I'm so happy :victory:
Try increasing the running voltages as well like 5-10mV. Might increase stability on lower freqs too.
Its not advisable to leave the minclock at 1.2ghz as you will soon find yourself with a constantly hot device.
As said previously by ttoivanen checking voltages might be a good step.
Have you messed with undervolting previously? As that could cause the symptoms you are describing
In trickster mod under specific settings there is mpu voltages
Care to post your values just for double checking
Sent from my HTC One X using xda app-developers app
Morning,
here are the MPU voltages
Code:
1 - 780
520 - 830
700 - 880
860 - 930
1050 - 1005
1150 - 1030
1200 - 1055
1280 - 1080
1300 - 1105
1340 - 1130
1380 - 1155
1500 - 1180
It seems like 475mhz is the lowest I can go, as soon as I set the minimum frequency lower than that, the phone freezes and hard reboots.
I already tried to change the MPU voltage offset to +5, +10 and +15 with no effect, but I don't know if the voltages are okay in the first place.
Very odd indeed. them values look like stock+30mv so voltages look ok
Sent from my HTC One X using xda app-developers app
Hey guys!
For all of us who have the dock. When you open the lid, the screen doesnt turn on. Well i kind of wish it did. So i made it so
Just flash attached zip in recovery and enjoy the benefits of my mod (this is prolly my favorite mod that ive done )
Again, you may donate if you enjoy my work, its very appreciated, however, not expected, just click that thanks button
Tested and confirmed working on CROMI 4.4 (JB 4.2.1) may also work on others. MAKE A BACKUP BEFORE TESTING!!!! I am NOT responsible for bootloops However, if you do test this, and it doesnt work on your device, just attach your ROM you are running, and to make my life easier, attach the android.policy.jar found in /system/framework and i will make it work for you
Btw, i was being lazy, this mod also has advanced power menu with it. i didnt have the time to start from stock file. Now its off to finish writing my five page final!
elesbb said:
Hey guys!
For all of us who have the dock. When you open the lid, the screen doesnt turn on. Well i kind of wish it did. So i made it so
Just flash attached zip in recovery and enjoy the benefits of my mod (this is prolly my favorite mod that ive done )
Again, you may donate if you enjoy my work, its very appreciated, however, not expected, just click that thanks button
Tested and confirmed working on CROMI 4.4 (JB 4.2.1) may also work on others. MAKE A BACKUP BEFORE TESTING!!!! I am NOT responsible for bootloops However, if you do test this, and it doesnt work on your device, just attach your ROM you are running, and to make my life easier, attach the android.policy.jar found in /system/framework and i will make it work for you
Btw, i was being lazy, this mod also has advanced power menu with it. i didnt have the time to start from stock file. Now its off to finish writing my five page final!
Click to expand...
Click to collapse
Sweeet, will be testing this on CROMI-X 4.4.1 after I clean some files off the tab.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
macgyver40 said:
Sweeet, will be testing this on CROMI-X 4.4.1 after I clean some files off the tab.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Its not working when the device is in deep sleep.
Works if its plugged into the charger though or computer. FML god. well i gotta finish my final first before i delve deeper.
elesbb said:
Its not working when the device is in deep sleep.
Works if its plugged into the charger though or computer. FML god. well i gotta finish my final first before i delve deeper.
Click to expand...
Click to collapse
I feel confident that i fixed it. OP updated. Now i can finally get to my paper. xD I just couldnt leave this unsolved. God i hate when i do this i seriously hope you guys like this xD I'll prolly be up till 1:00 AM finishing my paper yay.
elesbb said:
I feel confident that i fixed it. OP updated. Now i can finally get to my paper. xD I just couldnt leave this unsolved. God i hate when i do this i seriously hope you guys like this xD I'll prolly be up till 1:00 AM finishing my paper yay.
Click to expand...
Click to collapse
will give the new one the test then. Just installed the CTM 1.2 mod for the battery icon mod. also need to update my sig.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Em, where is the download link?
Moe5508 said:
Em, where is the download link?
Click to expand...
Click to collapse
It's hiding
I got all excited, thought it was working, left tablet go for about 15 minutes to ensure it was deep sleeping. Came back opened lid and didn't work :'(
So I have a few more things to try first :3
Sent from my SGH-T999 using Tapatalk 2
Weirdly this just works on my TF700 without any mods. I wonder why?
sbdags said:
Weirdly this just works on my TF700 without any mods. I wonder why?
Click to expand...
Click to collapse
the screen comes on when you open the lid? Like by stock? Can you clear your logcat, then close the lid, wait like a minute, then open it wait a minute, and get the logcat for me?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Does this help?
Code:
ReconcilePopImapAccountsSync: done
[ 05-09 19:30:34.205 30206:30213 D/dalvikvm ]
GC_CONCURRENT freed 326K, 18% free 3455K/4172K, paused 2ms+2ms, total 17ms
[ 05-09 19:30:35.355 30206:30227 D/Email ]
*** synchronizeMailboxGeneric ***
[ 05-09 19:30:35.905 1210: 1929 D/AlarmManager ]
Removed alarm Alarm{42608ef8 type 2 com.android.email} type:ELAPSED_REALTIME_WAKEUP
[ 05-09 19:30:35.905 1210: 1929 D/AlarmManager ]
Added alarm Alarm{415c14d0 type 2 com.android.email} type:ELAPSED_REALTIME_WAKEUP when: After 0h:0m:47.0s
[ 05-09 19:30:37.565 1210: 1245 D/WindowManager ]
notifyLidSwitchChanged, lidOpen:false mHasDockFeature:true mHasKeyboardFeature:true mHasHallSensorFeature:true mLidState:1
[ 05-09 19:30:37.595 1210: 1245 D/WindowManager ]
adjustConfigurationLw, config:{0.0 ?mcc?mnc ?locale ?layoutDir sw901dp w1442dp h853dp 213dpi xlrg land ?uimode ?night finger qwerty/v/v -nav/v} mLidState:0 mHasDockFeature:true mHasKeyboardFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:1
[ 05-09 19:30:37.595 1210: 1245 I/ActivityManager ]
Config changed: {1.0 ?mcc?mnc en_GB ldltr sw901dp w1442dp h853dp 213dpi xlrg land finger qwerty/v/v -nav/h s.27}
[ 05-09 19:31:09.795 1210: 1245 D/WindowManager ]
notifyLidSwitchChanged, lidOpen:true mHasDockFeature:true mHasKeyboardFeature:true mHasHallSensorFeature:true mLidState:0
[ 05-09 19:31:09.825 1210: 1245 D/WindowManager ]
adjustConfigurationLw, config:{0.0 ?mcc?mnc ?locale ?layoutDir sw901dp w1442dp h853dp 213dpi xlrg land ?uimode ?night finger qwerty/v/v -nav/v} mLidState:1 mHasDockFeature:true mHasKeyboardFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:1
[ 05-09 19:31:09.835 1210: 1245 I/ActivityManager ]
Config changed: {1.0 ?mcc?mnc en_GB ldltr sw901dp w1442dp h853dp 213dpi xlrg land finger qwerty/v/v -nav/h s.28}
[ 05-09 19:31:09.905 1210: 1225 I/PowerManagerService ]
Waking up from sleep...
[ 05-09 19:31:09.915 1210: 1224 V/Sensors ]
enable - sensor Accelerometer (handle 4) dis -> en
[ 05-09 19:31:09.915 1210: 1224 V/Sensors ]
enabled_sensors: 16 dmp_started: 0
[ 05-09 19:31:09.915 1210: 1224 V/Sensors ]
Starting DMP
[ 05-09 19:31:09.915 1210: 1224 E/ ]
/home/mcaramello/Software/MPL/branch-CAN-4.1.0/mlsdk/mltools/batch/mlsdk-rel-android-src-CONFIDENTIAL/mldmp/mlsupervisor_9axis.c|inv_enable_9x_fusion_legacy|299 returning 1
[ 05-09 19:31:09.915 1210: 1224 E/Sensors ]
Error while trying to enable 9 axis sensor fusion : 1
[ 05-09 19:31:09.935 1210: 1224 I/MPL-mldl_cfg_mpu: ]
inv_mpu_resume(,,,,0070) -> 0070
[ 05-09 19:31:09.935 1210: 1224 V/Sensors ]
setDelay - sensor Accelerometer (handle 4), rate 200 ms (5.00 Hz)
[ 05-09 19:31:09.935 1210: 1224 V/Sensors ]
set fifo rate - divider : 39, delay : 200 ms (5.00 Hz)
[ 05-09 19:31:09.945 1210: 1224 I/MPL-fifo ]
Actual ODR: 25000 mHz
[ 05-09 19:31:09.945 1210: 1224 V/Sensors ]
setDelay - sensor Accelerometer (handle 4), rate 66 ms (15.00 Hz)
[ 05-09 19:31:09.945 1210: 1224 V/Sensors ]
set fifo rate - divider : 13, delay : 66 ms (15.00 Hz)
[ 05-09 19:31:09.965 1210: 1224 I/MPL-fifo ]
Actual ODR: 25000 mHz
[ 05-09 19:31:09.965 1210: 1225 I/WindowManager ]
No lock screen!
[ 05-09 19:31:10.055 1210: 1224 D/WindowManager ]
adjustConfigurationLw, config:{1.0 ?mcc?mnc ?locale ?layoutDir sw901dp w1442dp h853dp 213dpi xlrg land ?uimode ?night finger qwerty/v/v -nav/v} mLidState:1 mHasDockFeature:true mHasKeyboardFeature:true mHasHallSensorFeature:true config.hardKeyboardHidden:1
[ 05-09 19:31:10.085 1210: 1224 W/NvCpuClient ]
Failed to bind to service
[ 05-09 19:31:10.095 1210: 1224 D/Ethernet ]
Connect is not possible because : ETHERNET not ENABLE, sleep can sleep,
[ 05-09 19:31:10.095 1210: 1224 D/WifiService ]
ACTION_SCREEN_ON
[ 05-09 19:31:10.215 1210: 1592 D/PowerManagerService-JNI ]
Excessive delay in autosuspend_disable() while turning screen on: 300ms
[ 05-09 19:31:10.215 132: 316 D/SurfaceFlinger ]
Screen acquired, type=0 flinger=0x410c0358
[ 05-09 19:31:10.215 132: 316 D/hwcomposer ]
hwc_blank: display 0: unblank
[ 05-09 19:31:10.215 132: 316 D/hwcomposer ]
hwc_blank_display: display 0: [1 -> 0]
[ 05-09 19:31:10.215 132: 316 D/hwcomposer ]
Display 0 is 1920 x 1200
[ 05-09 19:31:10.215 132: 316 D/hwcomposer ]
dc_blank: display 0, [1 -> 0]
[ 05-09 19:31:10.225 32579:32583 D/dalvikvm ]
GC_CONCURRENT freed 214K, 13% free 2806K/3208K, paused 2ms+9ms, total 34ms
[ 05-09 19:31:10.225 1840: 1844 D/dalvikvm ]
GC_CONCURRENT freed 386K, 21% free 2910K/3640K, paused 1ms+2ms, total 97ms
[ 05-09 19:31:10.275 1210: 1823 W/InputMethodManagerService ]
Window already focused, ignoring focus gain of: [email protected] [email protected], token = [email protected]
[ 05-09 19:31:10.285 1210: 1223 V/Sensors ]
Changed Polling period to 40ms
[ 05-09 19:31:10.355 1669: 1673 D/dalvikvm ]
GC_CONCURRENT freed 2259K, 47% free 16007K/29780K, paused 6ms+9ms, total 81ms
[ 05-09 19:31:10.355 1210: 1592 D/LightsService ]
Excessive delay setting light: 133ms
[ 05-09 19:31:10.485 1210: 1225 V/KeyguardHostView ]
onDetachedFromWindow = com.android.internal.policy.impl.keyguard.KeyguardHostView{41504618 V.E..... ......ID 0,0-1920,1136 #10202b7 android:id/keyguard_host_view}
[ 05-09 19:31:10.865 1210: 1223 V/Sensors ]
Changed Polling period to 400ms
[ 05-09 19:31:10.985 1210: 1223 V/Sensors ]
Changed Polling period to 40ms
[ 05-09 19:31:11.445 1210: 1223 V/Sensors ]
Changed Polling period to 400ms
Here's hoping you get this working properly. I would love this modification! :highfive:
sbdags said:
Does this help?
Code:
snip
Click to expand...
Click to collapse
Yes it does! This is very intriguing! The TF700 is running a COMPLETELY different line of code then the TF300 is.
You are running your CROMI ROM i presume correct? And all files are the same right? Like if i selected TF700 in the Aroma installer, nothing but the build.prop changes correct?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
Yes it does! This is very intriguing! The TF700 is running a COMPLETELY different line of code then the TF300 is.
You are running your CROMI ROM i presume correct? And all files are the same right? Like if i selected TF700 in the Aroma installer, nothing but the build.prop changes correct?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yes nothing but the TF700 build.prop
sbdags said:
Yes nothing but the TF700 build.prop
Click to expand...
Click to collapse
This is very interesting. Can you post me your model number? Anything that would set your device different from ours. There has got to be some sort of conditional statement making different segments of code run.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
This is very interesting. Can you post me your model number? Anything that would set your device different from ours. There has got to be some sort of conditional statement making different segments of code run.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
There are differences in the kernels. It's similar I reckon to the way it detects the settings app for the 4.2 launcher. Which model number do you want? It's in the build.prop or do you want a terminal command run?
sbdags said:
There are differences in the kernels. It's similar I reckon to the way it detects the settings app for the 4.2 launcher. Which model number do you want? It's in the build.prop or do you want a terminal command run?
Click to expand...
Click to collapse
Terminal command run. I have already ran the TF700 build.prop and not seen anything different. And i dont see how its in the kernel when i can run pure TF700 kernels and not notice one thing change like missing 4.2 UI option or having the screen come on when i wake the device. Like i said before, there MUST be some sort of conditional statement that checks what the device is. Its just a matter of finding it
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Same on my rom on tf201 using the newest tf300 base.
If I open the lid it comes alive. It always has without any mods.
flumpster said:
Same on my rom on tf201 using the newest tf300 base.
If I open the lid it comes alive. It always has without any mods.
Click to expand...
Click to collapse
And that happens if its in deep sleep? Im getting closer, i found where the code is checking what device its on. Wonder why the changed it for the TF300
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
And that happens if its in deep sleep? Im getting closer, i found where the code is checking what device its on. Wonder why the changed it for the TF300
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Not only from deep sleep but the dock will actually turn the prime on from a full power off if you connect it to dock when powered off.
Don't know if it does that for you also.
flumpster said:
Not only from deep sleep but the dock will actually turn the prime on from a full power off if you connect it to dock when powered off.
Don't know if it does that for you also.
Click to expand...
Click to collapse
Never really tried. My tablet is hardly ever off
Sent from my SGH-T999 using Tapatalk 2
I was wondering if it was possible to put my buttons that are on the bottom on portrait screen mode in the same orientation in landscape
8 are the locked buttons
portrait
__________
[ ]
[ ]
[ ]
[ ]
[ ]
[__88888__]
Landscape
_________________________
[ ]
[ ]
[ ]
[ ]
[______8 8 8 8 8______]
I have managed to install an Arch Linux system boot on my SGN 10.1 2014 edition (P600) on the external SD Card using the RECOVERY partition. I have encountered an issue though: I can't manage to get any screen output. That's why I'm calling for help here.
Let me sum up what I did and what's working first.
I flashed on my tablet Xluco's kernel (1.7, found in the thread) and installed Arch Linux on the external SD Card using Linux Deploy.
In the chroot, I got rid of systemd and replaced it by initscripts-fork (found on the AUR). That is because I could not manage to boot using systemd. I also tried openrc without success.
I copied the mfc firmware from android's system partition. I then configured some wireless connection with netcfg and enabled sshd.
I built Xluco's kernel 1.7 with a few tweaks: enabled virtual terminal and fbcon (as a module), changed the CMDLINE to be able to boot. I copied all that in my chrooted linux and mkinitcpio built an initial ramdisk for me. A finally packed all that in some flashable image for my recovery partition using abootimg.
I dd'd my image to the RECOVERY and rebooted.
So. It boots (after quite a long Samsung Galaxy Note screen, seems to be linked with enabling VT), I can log in through ssh. The problem is, I can't get the screen to work. Calling "modprobe fbcon" gives me
Code:
modprobe: ERROR: could not insert 'fbcon': Invalid argument
but nothing new in dmesg.
I also tried to configure an X server using fbdev as a video driver. The screen blinks as a call startx, but nothing more. It speaks a lot in dmesg though
Code:
# dmesg | grep fb
[ 1299.916361] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 1
[ 1299.916372] s3c-fb exynos5-fb.1: pm_relax
[ 1300.224278] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1300.224283] s3c-fb exynos5-fb.1: ready to suspend!
[ 1300.224327] s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 1301.288983] s3c-fb exynos5-fb.1: s3c_fb_pan_display::output_on is FALSE
[ 1301.290184] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.290249] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.290255] s3c-fb exynos5-fb.1: ready to suspend!
.
.
.
[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!
[ 1302.254599] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 0
[ 1302.255261] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1302.256138] s3c-fb exynos5-fb.1: pm_stay_awake
[ 1302.256146] s3c-fb exynos5-fb.1: mali level : 0
[ 1302.256243] s3c-fb exynos5-fb.1: - s3c_fb_blank
The dots symbolize a few hundreds occurences of the three lines
Code:
[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!
My guess is, there should be nothing like "s3c_fb_pan_display:utput_on is FALSE" in here...
Does anyone have any idea or suggestion to solve that problem? Or to get a better diagnosis at least?
Has someone managed to have it working?
EDIT:
I've tested to use the framebuffer through some low-level tools. Using
Code:
fbi -d /dev/fb0 -T 1 -a picture.jpg
drew the nice picture on my screen. No output in the log files though.
Okay, I've investigated a bit. Looking at dmesg right after android's boot (the dmesg gets flooded by thermal stuff if you wait), I found that the s3c-fb driver start sequence begins with
Code:
[ 5.507243] B3 2007 s3c-fb exynos5-fb.1: + s3c_fb_blank mode 0
[ 5.507339] B3 2007 s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 5.779631] B2 1233 s3c-fb exynos5-fb.1: s3c_fb_psr_enter +
[ 5.791298] B2 1233 s3c-fb exynos5-fb.1: s3c_fb_psr_enter -
[ 5.870133] B3 2007 s3c-fb exynos5-fb.1: s3c_fb_psr_exit +
[ 5.905940] B3 2007 s3c-fb exynos5-fb.1: s3c_fb_psr_exit -
while linux's begins with
Code:
[ 1176.701586] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 1
[ 1176.701598] s3c-fb exynos5-fb.1: pm_relax
[ 1177.008097] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1177.008102] s3c-fb exynos5-fb.1: ready to suspend!
[ 1177.008146] s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 1178.076551] s3c-fb exynos5-fb.1: s3c_fb_pan_display::output_on is FALSE
Looking in s3c-fb source file, s3c_fb_blank mode 0 corresponds to displaying something while s3c_fb_blank mode 1 is, well, blanking the screen.
Stupidely forcing mode 0 in the driver's code, I got a fully functional X display. The question is now: why is xf86-video-fbdev calling for a blank screen? Is it a misunderstanding with the driver?
I'll post any development here, hopefully soon.
Awesome, doing something similar on my Tab S and this solved it! Thanks.
I think this is also applicable on any 2014+ Sammy flagship devices Exynos variant since GS4 and below (panning instead of blanking) :thumbsup:
EDIT:Would you mind sharing the modifications you have done to source? huge cpu drain with my method, messed up loop maybe. Thanks
Any chance you'd post your "rom" so I could give it a go?
Does anybody have any advice on how to get this going again? I'm kinda stumped..
Hi,
Sorry to trouble....
I have so far been able to get qboot communicating with the QDloader,
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 79 (0x4f)
[ -0.000] ...cpu.sn = 3471194414 (0xcee6392e)
[ 0.008] Opening singleimage
[ 0.054] Loading package
[ 0.054] Failed identify board. Wrong package?
[ 0.062] ERROR: error loading package
[ 0.062] Check qboot_log.txt for more details
[ 0.062] Total time: 0.070s
FAILED: qb_flash_singleimage()->error loading package
-----
[ 0.062] DEVICE {
[ 0.062] name = "\\.\COM3",
[ 0.062] flags = "0x64",
[ 0.062] addr = "0x61FE4C",
[ 0.062] sahara.current_mode = "3",
[ 0.062] api.buffer = "0xF01020",
[ 0.062] cpu.serial = "3471194414",
[ 0.062] cpu.id = "79",
[ 0.062] cpu.sv_sbl = "1",
[ 0.062] api.bnr = "0x6E1D70",
[ 0.062] }
-----
But i dont seem to have a singleimage.bin to match ?
i have tried the 64 page XT179x thread, but cant seem to find the working singleimage.bin file to try with qboot ?
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150/page1
Also my version of qboot is 3.4 and 3.8 is being discussed
Any ideas ? it seems i need:
- a 'blank-flash' for my xt1794 / G5S, arounf : 5MB in size
- a newer version of qboot
I have tried the installation onto an SD-card, but zero joy on that approach at the moment
HELP
ZT
Hi!hello, did you find the file?