Related
So I have tried encrypting both CM10.1 and Task's AOKP on two separate devices and after the encryption neither device comes back from a screen off no matter what we do.
We get the initial enter encryption password, we then get the standard PIN password screen and the device functions just fine UNTIL the screen powers off. Once the screen powers off, if you try to wake it the device reboots.
Nothing installed on the device, fresh drop of the ROM. This sucks because we are also now stuck on an earlier version of JB.
Anyone have any idea why this is happening?
Does anyone know of a way to fool the server into thinking you are encrypted?
Code:
[ 02-11 12:39:09.368 1476: 1497 I/PowerManagerService ]
Waking up from sleep...
[ 02-11 12:39:09.388 1476: 1496 E/ ]
../../accel.c|inv_get_accel_offset|211 returning 19
[ 02-11 12:39:09.388 1476: 1496 D/Sensors ]
enable accel bias check
[ 02-11 12:39:09.388 1476: 1496 V/Sensors ]
enable - sensor Accelerometer (handle 4) dis -> en
[ 02-11 12:39:09.388 1476: 1496 E/Sensors ]
mEnabled = 10
[ 02-11 12:39:09.388 1476: 1496 V/Sensors ]
setDelay - sensor Accelerometer (handle 4), rate 200 ms (5.00 Hz)
[ 02-11 12:39:09.388 1476: 1496 V/Sensors ]
setDelay - sensor Accelerometer (handle 4), rate 66 ms (15.00 Hz)
[ 02-11 12:39:09.398 1476: 1495 E/Sensors ]
activatePendingSensors : mEnabled = 10
[ 02-11 12:39:09.398 1476: 1495 E/Sensors ]
requested_sensors(0) from kernel
[ 02-11 12:39:09.398 1476: 1495 V/Sensors ]
calling inv_set_mpu_sensors(000070)
[ 02-11 12:39:09.398 1476: 1495 I/MPL-fifo ]
Actual ODR: 14285 mHz
[ 02-11 12:39:09.398 1476: 1495 E/Sensors ]
set fifo rate - divider : 13, delay : 66 ms (15.00 Hz)
[ 02-11 12:39:09.398 1476: 1495 I/MPL-fifo ]
Actual ODR: 14285 mHz
[ 02-11 12:39:09.398 1476: 1495 V/Sensors ]
Starting DMP
[ 02-11 12:39:09.398 1476: 1495 W/MPL-9_sup ]
9 axis sensor fusion not available - No compass detected.
[ 02-11 12:39:09.398 1476: 1495 I/Sensors ]
Enabled 9 axis sensor fusion
[ 02-11 12:39:09.408 1476: 1495 I/MPL-mldl_cfg_mpu: ]
inv_mpu_resume(,,,,0070) -> 0070
[ 02-11 12:39:09.538 1127: 1176 D/SurfaceFlinger ]
Screen acquired, type=0 flinger=0x407a9318
[ 02-11 12:39:09.538 1127: 1176 D/qdhwcomposer ]
hwc_blank: Doing Dpy=0, blank=0
[ 02-11 12:39:09.578 3230: 3230 I/WLBroadcast ]
VISIBLE atLockScreen:true inInteraction:true
[ 02-11 12:39:09.668 1476: 2169 W/BackupManagerService ]
dataChanged but no participant pkg='com.android.providers.settings' uid=10099
[ 02-11 12:39:09.779 1127: 1176 D/qdhwcomposer ]
hwc_blank: Done Dpy=0, blank=0
Not sure if I did the logcat correctly but from what I can understand, I press the power button and that is what logcat spits out before the device reboots.
If it's a company requirement and they expect it as terms of employment...I'd just go along with them
Looks like this is a known issue:
https://jira.cyanogenmod.org/browse/CYAN-91
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since KitKat is becoming stable, I have built another ROM and decided to share it with you.
OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance, reliability and features over stock Android for your device. It is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts.
All the source code for OmniROM is available in the OmniROM Github repo.
More information about Omni
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOT WORKING/BROKEN
Same as in CM11
Camera
CHANGELOG
Code:
[B][U]29/05/2014:[/U][/B]
[LIST]
[*]Fixed USB Mass storage - [URL="gerrit.omnirom.org/#/c/5041/"]gerrit.omnirom.org/#/c/5041/[/URL]
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]06/05/2014:[/U][/B]
[LIST]
[*]Fixed OMX
[*]Fixed camera video recording
[*]Omni/omniarmv6 upstream
[/LIST]
[B][U]01/05/2014:[/U][/B]
[LIST]
[*]Initial release
[/LIST]
DOWNLOAD
OmniROM - team-simplicit.com
BTW: This ROM is not rooted, you have to flash SuperSU!
SCREENSHOTs
SOURCEs
Manifest
Device Config
Kernel Source
CREDITS
My awesome team (izi501, feroxx, Kevinjoa, thehacka1) for being so awesome!
WinSuk for the linker/reboot fix
benjamingwynn
niks255
JDevs and the OWL Team
The androidarmv6 team
The Omni team
Great job Oli. [emoji111]
Gesendet von meinem LG-gee mit Tapatalk
Info about ME
You're impossible @Olivier :laugh:
Anyway... New dev is coming
CyanFrank said:
You're impossible @Olivier :laugh:
Anyway... New dev is coming
Click to expand...
Click to collapse
Oh my goodness I really can't get it Just gonna press the download button...
I can haz logcat?
Logcat time!
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Code:
[ 05-03 16:55:09.561 5054: 5054 E/memalloc ]
/dev/pmem: Failed to map buffer size:4202496 offset:1843200 fd:83 Error: Invalid
argument
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
Could not mmap handle 0x2a1eac10, fd=83 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/gralloc ]
gralloc_register_buffer: gralloc_map failed
[ 05-03 16:55:09.561 5054: 5054 W/GraphicBufferMapper ]
registerBuffer(0x2a1eac10) failed -22 (Invalid argument)
[ 05-03 16:55:09.561 5054: 5054 E/GraphicBuffer ]
unflatten: registerBuffer failed: Invalid argument (-22)
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGLSUB ]
CreateImage() Invalid Native Buffer or handle
[ 05-03 16:55:09.561 5054: 5054 E/Adreno200-EGL ]
<qeglDrvAPI_eglCreateImageKHR:4160>: EGL_BAD_PARAMETER
Also, "Advanced settings" in "Performance" FCs
Code:
[ 05-03 16:58:34.951 4889: 4889 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.settings, PID: 4889
java.lang.NullPointerException
at java.io.File.fixSlashes(File.java:185)
at java.io.File.<init>(File.java:134)
at java.io.FileInputStream.<init>(FileInputStream.java:105)
at java.io.FileReader.<init>(FileReader.java:66)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.getVolts
(VoltageControlSettings.java:229)
at com.brewcrewfoo.performance.fragments.VoltageControlSettings.onCreate
(VoltageControlSettings.java:77)
at android.app.Fragment.performCreate(Fragment.java:1678)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062
)
at android.app.BackStackRecord.run(BackStackRecord.java:684)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.ja
va:1447)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:443)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit
.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
at dalvik.system.NativeStart.main(Native Method)
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Very Very good new htc wildfire s good olivier
csoulr666 said:
Logcat time!
Click to expand...
Click to collapse
Thanks for the logs! :good:
csoulr666 said:
The rom is quite smooth IMHO even with INT2EXT enabled, there are a few quirks here and there
This is something that pops up quite some times in the logcat, something to do with the GPU
Click to expand...
Click to collapse
Should be fixed in the next release...
csoulr666 said:
The lights of capacitive keys and the notification LED do not work. Suggestions to get logcats for these?
Finally, The phone doesn't show any charging status or animation when the phone is plugged in, the phone is charging though.
Click to expand...
Click to collapse
Look at the first screenshot, the device does show the charging symbol in the statusbar.
However, the lights and the notification LED really don't work. I will look into it ASAP.
EDIT: New update is up, check the OP!
Olivier said:
Look at the first screenshot, the device does show the charging symbol in the statusbar.
Click to expand...
Click to collapse
It does show a charging animation(I was using percent only, no animation there), but in the quick settings toggle or the diag menu(*#*#4636#*#*) do not show the charging status.
However, the lights and the notification LED really don't work. I will look into it ASAP.
Click to expand...
Click to collapse
Actually I found saw that LED works for certain notifications(only Gmail so far) but never for charging.......the latter might be because the system doesn't show the charging status
Also I have a question, will flashing the new update on the rom without wiping remove root as well??
csoulr666 said:
Will flashing the new update on the rom without wiping remove root as well??
Click to expand...
Click to collapse
I think so, because system (where SuperSU is located) gets wiped.
Olivier said:
I think so, because system (where SuperSU is located) gets wiped.
Click to expand...
Click to collapse
I just remembered, SuperSU asked me to install an addon script just to survive flashing...... Silly me:silly:
Question, you have not added UMS as of now am I right?? Because nothing pops up when I connect my phone to my PC
Wow! Looks like I'm the only one using OMNI, everyone else is glued to CM11 :laugh:
I got some more logs, hopefully helpful ones, regarding VPN ,bluetooth and wifi tethering
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Build from source ?
Olivier said:
Thanks for the logs! Yep I just noticed that bug too - I will maybe look into it on the weekend.
Click to expand...
Click to collapse
I have built CM11 from source, and would love to build this one too, to compare, I was expecting an omni branch in your github but didn't see it ?
Omni is at "android-4.4".
Gesendet von meinem Lenovo A3000-H mit Tapatalk
Awesome ROM but the quick pulldown disappear after reboot.
The patch not working camera
You always do the best olivier
Sent from my XT1032 using XDA Free mobile app
I'm not using this ROM
But,there is a workaround for USB Mass Storage bug,you see you can maybe use mobogenie pc app to make it work,because it mounts sd to pc without having to unmount it from device.
Best Wishes and tell me if it works
Camera?
I tried the camera patch with a complete wipe(including system) following the 6th may build........The "Can't connect to camera" prompt doesn't come but I'm greeted with a completely black screen, I tried a few other photo taking apps(Splitpic, Instagram and even a barcode scanner) but I still go the same result.
So here's a logcat of me opening the stock camera app
Code:
[ 05-07 21:02:49.867 615: 667 I/ActivityManager ]
Start proc com.android.camera2 for activity com.android.camera2/com.android.came
ra.CameraLauncher: pid=4766 uid=10050 gids={50050, 3003, 1028, 1015, 1023}
[ 05-07 21:02:50.817 4766: 4766 D/CameraStorage ]
External storage state=mounted
[ 05-07 21:02:50.827 4766: 4766 V/NFC ]
this device does not have NFC support
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
On resume.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Executing onResumeTasks.
[ 05-07 21:02:50.858 4766: 4766 V/CAM_PhotoModule ]
Open camera device.
[ 05-07 21:02:50.858 129: 129 D/AK8975 ]
Compass Start
[ 05-07 21:02:50.878 124: 1053 D/CameraHAL ]
CameraHAL_GetNum_Cameras: loading libcamera at 0x4077eed8
[ 05-07 21:02:50.888 4766: 4766 V/CameraHolder ]
open camera 0
[ 05-07 21:02:51.298 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.558 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.808 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:51.919 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.119 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.299 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.519 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.719 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:52.920 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.110 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.190 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.410 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.590 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:53.790 124: 4221 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:53.790 124: 4221 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.021 124: 668 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.031 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.231 124: 668 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:54.411 124: 1053 W/MPEG4Extractor ]
ignoring edit list with 2 entries
[ 05-07 21:02:54.421 124: 1053 D/ExtendedUtils ]
extended extractor not needed, return default
[ 05-07 21:02:59.786 615: 631 E/WindowManager ]
Starting window AppWindowToken{420b01a8 token=Token{420af890 ActivityRecord{420a
f6b8 u0 com.android.camera2/com.android.camera.CameraLauncher t453}}} timed out
[ 05-07 21:02:59.796 615: 632 W/ActivityManager ]
Launch timeout has expired, giving up wake lock!
[ 05-07 21:03:10.857 615: 632 W/ActivityManager ]
Timeout executing service: ServiceRecord{42208360 u0 com.android.camera2/com.and
roid.camera.MediaSaveService}
[ 05-07 21:03:10.917 615: 632 I/Process ]
Sending signal. PID: 4766 SIG: 3
[ 05-07 21:03:10.917 4766: 4771 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:10.967 4766: 4771 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:10.967 615: 632 I/Process ]
Sending signal. PID: 615 SIG: 3
[ 05-07 21:03:10.967 615: 620 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.538 615: 627 E/Sensors ]
poll() failed (Interrupted system call)
[ 05-07 21:03:11.578 615: 632 I/Process ]
Sending signal. PID: 991 SIG: 3
[ 05-07 21:03:11.578 991: 996 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.608 615: 620 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.608 615: 632 I/Process ]
Sending signal. PID: 803 SIG: 3
[ 05-07 21:03:11.618 803: 815 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.728 803: 815 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.738 615: 632 I/Process ]
Sending signal. PID: 795 SIG: 3
[ 05-07 21:03:11.738 795: 809 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.758 991: 996 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.768 615: 632 I/Process ]
Sending signal. PID: 783 SIG: 3
[ 05-07 21:03:11.768 783: 794 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 05-07 21:03:11.858 783: 794 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:11.958 795: 809 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 05-07 21:03:13.920 615: 632 E/ActivityManager ]
ANR in com.android.camera2
PID: 4766
Reason: Executing service com.android.camera2/com.android.camera.MediaSaveServic
e
Load: 10.33 / 14.25 / 12.94
CPU usage from 6040ms to 0ms ago:
1.3% 129/akmd: 0.1% user + 1.1% kernel
1.3% 615/system_server: 0.8% user + 0.4% kernel
0.3% 5/events/0: 0% user + 0.3% kernel
0.1% 109/yaffs-bg-1: 0% user + 0.1% kernel
0.1% 754/wpa_supplicant: 0.1% user + 0% kernel
1.8% TOTAL: 0.6% user + 1.1% kernel
CPU usage from 2456ms to 2995ms later:
12% 615/system_server: 1.7% user + 10% kernel
10% 632/ActivityManager: 1.7% user + 8.9% kernel
1.7% 615/system_server: 1.7% user + 0% kernel
9.2% TOTAL: 1.8% user + 7.4% kernel
[ 05-07 21:03:22.719 615: 632 W/ActivityManager ]
Force finishing activity com.android.camera2/com.android.camera.CameraLauncher
[ 05-07 21:03:22.729 615: 632 I/ActivityManager ]
Killing 4766:com.android.camera2/u0a50 (adj 0): user request after error
[ 05-07 21:03:23.019 129: 129 D/AK8975 ]
Compass CLOSE
[ 05-07 21:03:23.439 615: 625 W/InputMethodManagerService ]
Window already focused, ignoring focus gain of: com.android.internal.view.IInput
[email protected] attribute=null, token = [email protected]
41ed3308
**** Log buffer [000001] 2018-04-29_23:09:21 ****
[ 0.000] Opening device: \\.\COM9
[ 0.063] Detecting device
[ 0.078] ...cpu.id = 94 (0x5e)
[ 0.125] ...cpu.sn = 4273788185 (0xfebcd519)
[ 0.125] Opening singleimage
[ 0.531] Loading package
[ 0.609] ...filename = pkg.xml
[ 0.688] Loading programmer
[ 0.938] ...filename = programmer.elf
[ 0.938] Sending programmer
[ 1.142] ReadFile() failed, GetLastError()=0
[ 1.510] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 1.551] ERROR: sahara_download()->general error
[ 1.554] Check qboot_log.txt for more details
[ 1.593] Total time: 1.609s
[ 1.611]
[ 1.611] qboot version 3.85
[ 1.611]
[ 1.611] DEVICE {
[ 1.611] name = "\\.\COM9",
[ 1.611] flags = "0x64",
[ 1.611] addr = "0x62FD64",
[ 1.611] sahara.current_mode = "0",
[ 1.611] api.buffer = "0x28B6020",
[ 1.611] cpu.serial = "4273788185",
[ 1.611] cpu.id = "94",
[ 1.611] cpu.sv_sbl = "0",
[ 1.611] cpu.name = "MSM8998",
[ 1.611] storage.type = "UFS",
[ 1.611] sahara.programmer = "programmer.elf",
[ 1.611] api.bnr = "0x27F3E10",
[ 1.611] }
[ 1.611]
[ 1.611]
[ 1.611] Backup & Restore {
[ 1.611] num_entries = 0,
[ 1.611] restoring = "false",
[ 1.611] backup_error = "not started",
[ 1.611] restore_error = "not started",
[ 1.611] }
[ 1.611]
--------------
this is blank flash error log. I don't know this error. any solutions?
**** Log buffer [000001] 2018-05-27_19:15:58 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 79 (0x4f)
[ 0.002] ...cpu.sn = 3414389940 (0xcb8374b4)
[ 0.002] Opening singleimage
[ 0.339] Loading package
[ 0.343] ...filename = singleimage.pkg.xml
[ 0.345] Loading programmer
[ 0.347] ...filename = programmer.mbn
[ 0.347] Sending programmer
[ 1.378] ERROR: sahara_download()->IO error
[ 1.378] Check qboot_log.txt for more details
[ 1.378] Total time: 1.378s
[ 1.378]
[ 1.378] qboot version 3.40
[ 1.378]
[ 1.378] DEVICE {
[ 1.378] name = "/dev/ttyUSB0",
[ 1.378] flags = "0x60",
[ 1.378] addr = "0x41C63D78",
[ 1.378] serial_nix.device_pathname = "/sys/bus/usb/devices/2-1.3/2-1.3:1.0/ttyUSB0",
[ 1.378] sahara.current_mode = "0",
[ 1.378] api.buffer = "0x7FE2D204C010",
[ 1.378] cpu.serial = "3414389940",
[ 1.378] cpu.id = "79",
[ 1.378] cpu.sv_sbl = "1",
[ 1.378] cpu.name = "MSM8937",
[ 1.378] storage.type = "eMMC",
[ 1.378] sahara.programmer = "programmer.mbn",
[ 1.378] api.bnr = "0xC5B7F0",
[ 1.378] }
[ 1.378]
[ 1.378]
[ 1.378] Backup & Restore {
[ 1.378] num_entries = 0,
[ 1.378] restoring = "false",
[ 1.378] backup_error = "not started",
[ 1.378] restore_error = "not started",
[ 1.378] }
[ 1.378]