Hi all, i have a problem with the maximushd in fact, the auto rotate doesn't work. I have recently install this Rom after having s off and I don't think that a full wipe can fix this. As far as I remember the auto rotation worked when I was s on with other roms like source 1.4.
Thanks in advice
Inviato dal mio HTC One S utilizzando Tapatalk
Anyone?
Inviato dal mio HTC One S utilizzando Tapatalk
finally I realized that the elementalx that i have installed on the maximushd was the problem, in fact i returned to the stock kernel. mean while i was with the elementalx i take a logcat of what happens when i press the auto rotation button. here it is:
Code:
V/HtcDLNAServiceManager(21596): Settings:Agentname: hide_rotation_lock_toggle_for_accessibility
W/System.err(21596): at com.android.internal.view.RotationPolicy.setRotationLockForAccessibility(RotationPolicy.java)
W/System.err(21596): at com.android.settings.AccessibilitySettings.handleLockScreenRotationPreferenceClick(AccessibilitySettings.java)
I/QuickSettingRotate( 963): onRotationChanged:false
I/QuickSettingRotation( 963): onRotationLockChanged:false
V/HtcDLNAServiceManager( 754): Settings:Agentname: accelerometer_rotation
W/System.err( 754): at com.android.internal.policy.impl.PhoneWindowManager.setUserRotationMode(PhoneWindowManager.java)
W/System.err( 754): at com.android.server.wm.WindowManagerService.freezeRotation(WindowManagerService.java)
I/QuickSettingRotate( 963): onRotationChanged:true
I/QuickSettingRotation( 963): onRotationLockChanged:true
I/QuickSettingRotate( 963): onRotationChanged:true
I/QuickSettingRotation( 963): onRotationLockChanged:true
V/HtcDLNAServiceManager(21596): Settings:Agentname: hide_rotation_lock_toggle_for_accessibility
W/System.err(21596): at com.android.internal.view.RotationPolicy.setRotationLockForAccessibility(RotationPolicy.java)
W/System.err(21596): at com.android.settings.AccessibilitySettings.handleLockScreenRotationPreferenceClick(AccessibilitySettings.java)
I/QuickSettingRotate( 963): onRotationChanged:true
I/QuickSettingRotation( 963): onRotationLockChanged:true
V/HtcDLNAServiceManager( 754): Settings:Agentname: accelerometer_rotation
W/System.err( 754): at com.android.internal.policy.impl.PhoneWindowManager.setUserRotationMode(PhoneWindowManager.java)
W/System.err( 754): at com.android.server.wm.WindowManagerService.thawRotation(WindowManagerService.java)
I/QuickSettingRotate( 963): onRotationChanged:false
I/QuickSettingRotation( 963): onRotationLockChanged:false
I/QuickSettingRotate( 963): onRotationChanged:false
I/QuickSettingRotation( 963): onRotationLockChanged:false
W/ViewFinder(23442): initializeOverride() - No IUIRotationManager interface
guys, the issue is reappeared again in my maximushd but this time even with full wipe and reflash of the rom doesn't fix it. any ideas?
Related
I'm trying to get JACxHERO 1.1 from over on the Dream boards running on my 32B. So I've been trying to follow the procedure that dazcox51 described in his post below
http://forum.xda-developers.com/showthread.php?t=539052
(for those who can't be bothered to take the jump, it's basically a case of unpacking the boot.img, renaming init.trout.rc to init.sapphire.rc, and then packing it all up again, resigning the update.zip, and flashing)
I've managed to flash, it starts to boot - and then I get a reboot loop.
Logcat shows the following. There's more, but I think the pertinent part is:
Code:
I/SystemServer( 137): Starting NetStat Service.
I/SystemServer( 137): Starting Connectivity Service.
W/dalvikvm( 137): threadid=23: thread exiting with uncaught exception (group=0x4000fe70)
E/AndroidRuntime( 137): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 137): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 137): java.lang.NullPointerException
E/AndroidRuntime( 137): at android.app.ActivityThread.getProvider(ActivityThread.java:3689)
E/AndroidRuntime( 137): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3718)
E/AndroidRuntime( 137): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1473)
E/AndroidRuntime( 137): at android.content.ContentResolver.acquireProvider(ContentResolver.java:576)
E/AndroidRuntime( 137): at android.content.ContentResolver.query(ContentResolver.java:144)
E/AndroidRuntime( 137): at android.provider.Settings$NameValueCache.getString(Settings.java:472)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getString(Settings.java:1759)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getInt(Settings.java:1799)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:186)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:127)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:51)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:91)
Does anyone have any bright ideas?
There is more, but unfortunately the board won't let me post it. I'll put it in a second post, just in case it's relevant.
It's not letting me post the entire logcat, it tells me the post is too long. I'm pretty sure I've got the relevant bit. If anyone wants the whole thing, drop me a PM and I'll mail it. To be it looks network related but must confess I'm just fumbling around here.
Just out of curiosity, I flashed the original Dream ROM without changing it. I got the same reboot loop so I think I'm missing something fundamental and/or obvious.
Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?
If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues
bhav007 said:
Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?
Click to expand...
Click to collapse
I think I will try that as an experiment, but I don't really want to do that as a "release" ROM, as the whole point of this is to see if we can get a decent Compcached version of Hero running on the Magic. If I just whack in (for example) Qtek's boot.img I suspect that, if it worked, we'd end up with a ROM that has the same shortcomings (i.e. unreliable texts due to memory shortages, and a kernel that runs Compcache slower than a swap!).
dazcox5181 said:
If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues
Click to expand...
Click to collapse
Yep, on OSX but did replace cpio. Brand new SD card, 8Gb class 6, partitioned with the latest Amon Ra recovery image.
Will try a new download but I'd be surprised if it was that, because I can unzip/rezip it all just fine.
I don't believe this - it looks like it's my new SD card. Qtek's ordinarily working ROM dies with the same error (albeit before it gets to the Hero loading screen) if I try to boot it with that card in. Have tried with a single fat32 partition and also with the usual three partitioned fat32/ext2/swap scenario.
The card seems to work fine plugged into my Mac and also from within the recovery image on the Magic. I think I'll start a new thread on this as it has naff all to do with JACxHERO it seems.
Hi, everyone!
I've made some efforts to get my CM7 repo to compile for HTC Sensation, and I think I finally made it. The problem is that I'm using MIUI and I don't really have the time to test this out properly. I'd love to see you enthusiasts trying this one and give me feedback on what works and what doesn't.
This is probably not much different from the SelfKang that is also in this forum. Maybe the SelfKang9 is even more fixed than mine, since the device tree I'm using hasn't been updated for quite some time. Mine has all the newest commits from the CM7 repo, though. The device tree (android_device_htc_pyramid) are just device specific parts.
No cherry picks except for camera touch focus and some pyramid specific commits in gerrit.
Please let me know if/how it works.
Download:
update-cm-7.1.0-SelfKANG9-Sensation-KANG-signed.zip
MD5: 5eec00422f38d7048c435eb9d28ffe9a
PS.
The name is SelfKANG9, since this was in Kmob's pyramid commits on gerrit and I have chosen not to change anything of it.
it has been released weeks ago ...i think
Wanhao said:
it has been released weeks ago ...i think
Click to expand...
Click to collapse
So this one has several weeks of new commits. And what has been released is just the ROM and not the complete source code.
Sent from my HTC Sensation Z710e using Tapatalk
I must ask, because I am a noob, but whats the point of this if the real deal is out and about? Ive had CM7 on my phone for months.
Matt
mrg02d said:
I must ask, because I am a noob, but whats the point of this if the real deal is out and about? Ive had CM7 on my phone for months.
Matt
Click to expand...
Click to collapse
Unless you know something otherwise an official CM release is not yet available for the sensation.
The point is for me to be able to give you updated kangs more than once every two weeks. New commits etc. I'm not trying to compete or anything, I want to contribute.
Sent from my HTC Sensation Z710e using Tapatalk
So whose device tree are you using?
blahbl4hblah said:
So whose device tree are you using?
Click to expand...
Click to collapse
This one:
https://github.com/zyonee/android_device_htc_pyramid
I also had to add this:
https://github.com/zyonee/android_device_htc_8x60-recovery
and another one that I can't find with my mobile, which adds support for the 8x60 architecture.
Sent from my HTC Sensation Z710e using Tapatalk
this doesn't even work.... test next time k?
Code:
/NetdConnector( 216): Communications error
E/NetdConnector( 216): java.io.IOException: No such file or directory
E/NetdConnector( 216): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 216): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 216): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 216): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 216): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 216): at java.lang.Thread.run(Thread.java:1019)
E/NetdConnector( 216): Error in NativeDaemonConnector
E/NetdConnector( 216): java.io.IOException: No such file or directory
E/NetdConnector( 216): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 216): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 216): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 216): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 216): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 216): at java.lang.Thread.run(Thread.java:1019)
I/Netd ( 633): Netd 1.0 starting
E/SocketListener( 633): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/Netd ( 633): Unable to start DnsProxyListener (No such file or directory)
Not as easy to compile as I thought, then. We'll see if I can figure it out.
Thanks for testing, though.
Sent from my HTC Sensation Z710e using Tapatalk
Edit: I'm probably not going to update this thread very often, but I'll keep trying to get CM7 compiling in my environment. If I make any progress, I'll post it here. Thanks for your patience.
cam's working now working now
thanks to cute_prince and liroka
give all the credits to them
here the download link : http://www.mediafire.com/?i7skgxn34s4is58
heres a logcat
heres a logcat of what happens when camera app is loaded :
Code:
I/ActivityManager( 169): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera} from pid 3
27
I/ActivityManager( 169): Start proc com.android.camera for activity com.android
.camera/.Camera: pid=1078 uid=10032 gids={1006, 1015}
D/OpenGLRenderer( 327): Flushing caches (mode 1)
D/dalvikvm( 169): GC_EXPLICIT freed 2006K, 56% free 5011K/11207K, paused 5ms+13
ms
V/CameraHolder( 1078): open camera 0
E/CameraService( 107): Camera HAL module not loaded
E/CameraHolder( 1078): fail to connect Camera
E/CameraHolder( 1078): java.lang.RuntimeException: Fail to connect to camera ser
vice
E/CameraHolder( 1078): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1078): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 1078): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 1078): at com.android.camera.CameraHolder.open(CameraHolder.jav
a:131)
E/CameraHolder( 1078): at com.android.camera.Util.openCamera(Util.java:321)
E/CameraHolder( 1078): at com.android.camera.Camera$4.run(Camera.java:1251)
E/CameraHolder( 1078): at java.lang.Thread.run(Thread.java:856)
I/Process ( 169): Sending signal. PID: 1078 SIG: 3
I/dalvikvm( 1078): threadid=3: reacting to signal 3
I/dalvikvm( 1078): Wrote stack traces to '/data/anr/traces.txt'
D/OpenGLRenderer( 327): Flushing caches (mode 0)
D/libEGL ( 1078): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1078): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1078): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1078): loaded /system/lib/egl/libGLESv2_adreno200.so
D/OpenGLRenderer( 1078): Enabling debug mode 0
V/camera ( 1078): surfaceChanged. w=320. h=427
I/ActivityManager( 169): Displayed com.android.camera/.Camera: +1s59ms
D/OpenGLRenderer( 327): Flushing caches (mode 1)
i think the problem is here : E/CameraService( 107): Camera HAL module not loaded
hope it helps
good news
camera is on the verge to get working plz give me some time
this was the life saver : http://forum.xda-developers.com/showthread.php?t=1427030
ayushrox said:
camera is on the verge to get working plz give me some time
this was the life saver : http://forum.xda-developers.com/showthread.php?t=1427030
Click to expand...
Click to collapse
Define "On the verge of working." I don't exactly want to end in a bootloop in the middle of the class.
on the verge means
AIndoria said:
Define "On the verge of working."
Click to expand...
Click to collapse
on the verge means - to get very near
well it seems that a camera worked but really bad :crying:
only preview app like night vision that too crashed after about 10 sec :crying:
when tried to fix it :silly: i messed with the whole boot.img and now its bootlooping :crying: :crying: :crying:
if i again get preview worked i'll upload it
i seriously need some dev help
i seriously need some dev help
ayushrox said:
i seriously need some dev help
Click to expand...
Click to collapse
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
thanks
LiVeRpOoL-FaN said:
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
Click to expand...
Click to collapse
thanks
hey did you try the link there ?
@ayushrox
Hey you can also add
https://www.codeaurora.org/gitweb/q...erry_rb3.4;hb=refs/heads/ics_strawberry_rb3.4
derefas posted this link in 4pda.. He told that this might help in fixing the camera..
This one looks interesting, worth studying a bit.
Will have a look at it when I got some free, But first must fix graphics problems.
Sent from my GT-P5110 using xda app-developers app
hal passed
hey 2 updates
good one- cute prince got past hal error
bad one - cam still not workin
result - maybe workin cam in few days/weeks
any one try this
hey i have made a some changes in source
plz some one compile it with ur rom and see if gets past the HAL
link (my github): https://github.com/ayushrox/ics-cam-HAL
LiVeRpOoL-FaN said:
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
Click to expand...
Click to collapse
Did u tried with plan u mentioned??
Sorry for asking question. Just wantd to keep this important thread active
Sent from my HTC Explorer A310e using xda app-developers app
this is active
the only prob we have no organized participation;
any way back to topic
camera HAL is now confirmed passed by cute_prince (donno how ? :silly: )
no new updates
Liroka made camera working))
He used htc golf files n succeeded:)
really ?
sbacham said:
Liroka made camera working))
He used htc golf files n succeeded:)
Click to expand...
Click to collapse
really where did he posted it ?
Link
http://forum.xda-develo
pers.com/showpost.php?p=3
0742590&postcount=558
that's really a gr8 news
that's really a gr8 news !
updates
liroka got cam working (yay :victory: )
see his post :
lirokoa said:
Got a piece of camera working
I can take picture, but can't record movie
To make it to work I backported camera driver from golf kernel (our sensor is supported by this kernel) and used all proprietary libs from golf.
Click to expand...
Click to collapse
Waiting for full camera support. Video and image capture both, for CM9. \m/
Hello everyone, I hope that someone here can help me understand what is the culprit behind this issue, I know it's related to Wifi since the random reboots almost never happen when Wifi is turned of (regardless if it's actually connected to a network or not)
Logcat:
Error: AndroidRuntime
*** FATAL EXCEPTION IN SYSTEM PROCESS: ClientModeImpl
java.lang.IllegalArgumentException: ssid bytes size out of range: 64
at com.android.server.wifi.util.NativeUtil.decodeSsid(NativeUtil.java:278)
at com.android.server.wifi.WifiScoreCard.computeHashLong(WifiScoreCard.java:588)
at com.android.server.wifi.WifiScoreCard.access$100(WifiScoreCard.java:63)
at com.android.server.wifi.WifiScoreCard$PerBssid.<init>(WifiScoreCard.java:380)
at com.android.server.wifi.WifiScoreCard.lookupBssid(WifiScoreCard.java:530)
at com.android.server.wifi.WifiCandidates.add(WifiCandidates.java:374)
at com.android.server.wifi.WifiCandidates.add(WifiCandidates.java:393)
at com.android.server.wifi.WifiNetworkSelector.lambda$selectNetwork$0$WifiNetworkSelector(WifiNetworkSelector.java:911)
at com.android.server.wifi.-$$Lambda$WifiNetworkSelector$Z7htivbXF5AzGeTh0ZNbtUXC_0Q.onConnectable(Unknown Source:15)
at com.android.server.wifi.SavedNetworkEvaluator.evaluateNetworks(SavedNetworkEvaluator.java:279)
at com.android.server.wifi.WifiNetworkSelector.selectNetwork(WifiNetworkSelector.java:900)
at com.android.server.wifi.WifiConnectivityManager.handleScanResults(WifiConnectivityManager.java:342)
at com.android.server.wifi.WifiConnectivityManager.access$900(WifiConnectivityManager.java:73)
at com.android.server.wifi.WifiConnectivityManager$AllSingleScanListener.onResults(WifiConnectivityManager.java:425)
at android.net.wifi.WifiScanner$ServiceHandler.handleMessage(WifiScanner.java:1429)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
PID: 28683
TID: 28862
The following error message says:
FATAL EXCEPTION: main
Process: com.google.android.gms.persistent, PID: 30417
DeadSystemException: The system died; earlier logs will point to the root cause
This is consistent and the same exact error I posted shows up everytime the system crashes/reboots.
Hope someone can help me out, thanks
Have you cleared your cache?
tech_head said:
Have you cleared your cache?
Click to expand...
Click to collapse
Yes I tried clearing cache using TWRP, the issue still persists.
hello guys
so i started flashing custom roms on my samsung galaxy tab s6 lite with lineage 17, 18, gsi and after that I noticed that the I cannot set a PATTERN, PIN, PASSWORD screenlock except for swipe. so what I did was a clean flash of the STOCK ROM through odin with relocked bootloader but the problem still persists where I cannot set any screenlock type except swipe and none. last thing to do was log it. so here are some logs. do you guys know a way to fix this?
Code:
2021-12-12 08:36:24.725 4657 20641 system E AndroidRuntime : FATAL EXCEPTION: AsyncTask #2
Process: com.android.settings, PID: 4657
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
at android.os.Parcel.createExceptionOrNull(Parcel.java:2381)
at android.os.Parcel.createException(Parcel.java:2357)
at android.os.Parcel.readException(Parcel.java:2340)
at android.os.Parcel.readException(Parcel.java:2282)
at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1208)
at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:660)
at com.android.settings.password.ChooseLockPattern$SaveAndFinishWorker.saveAndVerifyInBackground(ChooseLockPattern.java:922)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:138)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:134)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 4 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:779)
at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2688)
at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1741)
at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1663)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:537)
2021-12-12 08:36:58.370 4317 4997 system E BufferQueueProducer : [com.android.settings/com.android.settings.password.ChooseLockPatternSize#0](id:10dd000000a7,api:0,p:-1,c:4317) disconnect: not connected (req=1)
Did you ever find a solution to this?
I have the stock and the LineageOS ROM (19.1) ROMS working fine, but a custom build of the eOS (https://e.foundation) for the S20+ (y2s) has this issue.