[ROM][28 OCT]CM7 KANG for Sensation (pyramid) testing - HTC Sensation

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.

Related

[development]cyanogen mod camera

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/

[Q] I can't compile recovery

Hi all I'm translating cwm recovery. I downloaded cm source. But when i enter this command :
make -j4 recoveryimage
i get too many errors and compilation fails :
Code:
[email protected]:~/android$ make -j4 recoveryimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-19-generic-x86_64-with-Ubuntu-13.04-raring
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/home/jale/android/out
============================================
/home/jale/android/out/target/product/generic/obj/APPS/SignatureTest_intermediates
find: “src”: No file or directory
grep: /build/target/board/generic/recovery.fstab: No file or directory
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/arm-linux-androideabi-ld: error: /home/jale/android/out/target/product/generic/obj/lib/crtbrand.o: file is empty
make: *** [/home/jale/android/out/target/product/generic/obj/lib/crtbegin_static.o] Hata 1
make: *** Waiting for unfinished operations....
target thumb C++: libc <= bionic/libc/bionic/pthread_debug.cpp
target thumb C++: libc <= bionic/libc/bionic/libc_init_dynamic.cpp
cc1plus: warning: command line option '-std=gnu99' is valid for C/ObjC but not for C++ [enabled by default]
cc1plus: warning: command line option '-std=gnu99' is valid for C/ObjC but not for C++ [enabled by default]
bionic/libc/bionic/libc_init_dynamic.cpp:95:17: warning: unused parameter 'onexit' [-Wunused-parameter]
bionic/libc/bionic/pthread_debug.cpp:545:13: warning: 'void hashmap_removeEntry(HashTable*, HashEntry*)' defined but not used [-Wunused-function]
[email protected]:~/android$
Thanks.
I have the same problem. Have you been able to fix this?
Harmc0re said:
I have the same problem. Have you been able to fix this?
Click to expand...
Click to collapse
i already fixed this.
Sent from my Nexus 5 using Tapatalk.
yashade2001 said:
i already fixed this.
Click to expand...
Click to collapse
May I ask how ?
jdegreef said:
May I ask how ?
Click to expand...
Click to collapse
There was a problem with kernel tree.
yashade2001 said:
There was a problem with kernel tree.
Click to expand...
Click to collapse
Can you give details ? I have the same message. (no recovery resource...) The recovery finish building but doesn't boot.
jdegreef said:
Can you give details ? I have the same message. (no recovery resource...) The recovery finish building but doesn't boot.
Click to expand...
Click to collapse
Are u buildin for maguro?
yashade2001 said:
Are u buildin for maguro?
Click to expand...
Click to collapse
No, I'm building for trebon (gt-s7500) using omnirom sources. The rom is booting but not the recovery. I've also tried with CM11 TheWhisp trebon sources but with both I get this "No private recovery resources for TARGET_DEVICE trebon". I'm only interrested in the recovery.img as my goal is to port Philz CWM to trebon. But for this I first need to have the stock recovery working.
jdegreef said:
No, I'm building for trebon (gt-s7500) using omnirom sources. The rom is booting but not the recovery. I've also tried with CM11 TheWhisp trebon sources but with both I get this "No private recovery resources for TARGET_DEVICE trebon". I'm only interrested in the recovery.img as my goal is to port Philz CWM to trebon. But for this I first need to have the stock recovery working.
Click to expand...
Click to collapse
Make sure u have working device-vendor-kernel tree.
yashade2001 said:
Make sure u have working device-vendor-kernel tree.
Click to expand...
Click to collapse
Well, I assume it is correct as the rom compiles, is flashable and boot.
I have the feeling that recovery is broken in Omnirom.
Yesterday I build CM11 (nightly sources) for Galaxy Tab 2 (gt-p5100) and I get the same "No private recovery resources for TARGET_DEVICE p5100" message. BUT the rom is working AND the recovery too !
The fact that the recovery from Omnirom is not booting as therefore nothing to do with this message.
I'll keep on searching and, more important, learn
One month ago I didn't know anything about building a rom but I had some knowledge about compiling the Linux kernel.
Anyway thank you for your help.
jdegreef said:
Well, I assume it is correct as the rom compiles, is flashable and boot.
I have the feeling that recovery is broken in Omnirom.
Yesterday I build CM11 (nightly sources) for Galaxy Tab 2 (gt-p5100) and I get the same "No private recovery resources for TARGET_DEVICE p5100" message. BUT the rom is working AND the recovery too !
The fact that the recovery from Omnirom is not booting as therefore nothing to do with this message.
I'll keep on searching and, more important, learn
One month ago I didn't know anything about building a rom but I had some knowledge about compiling the Linux kernel.
Anyway thank you for your help.
Click to expand...
Click to collapse
Recovery from omni is twrp and buildin twrp is a little different
yashade2001 said:
Recovery from omni is twrp and buildin twrp is a little different
Click to expand...
Click to collapse
Yes, I notice that.
I've made progresses and been able to compile both cwm and twrp. Compilation goes without error, recovery.fstab, twrp.fstab and BoardConfig.mk seem correct and recovery is flashed on the right partition but the recovery doesn't boot. It either get stucked at the first Samsung logo, either bootlooping at that logo. I have no idea what could be the cause and, worst, I have no idea how to debug that...
Even the method with the extracted boot.img gives the same results.
Sent from my GT-P5100 using Tapatalk

[WIP] Building custom ROM for Lenovo Tab2A7-10F

This thread is meant to share informations about trying to build a custom rom (CM, Omnirom...) for Lenovo Tab2 A7-10F
I'm currently trying to build CM12.1 using source
Any comment, hint, link, collaboration is welcome
Previously...
Previously...
[email protected] said:
Now time for new rom , i think you should try out building any cm based rom , omni is 75% Aosp so there might be some issues.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
How can AOSP be an issue ? I always choose opensource when possible.
Click to expand...
Click to collapse
[email protected] said:
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
Ok, i may try some other rom though.
Thanks for your advice.
Do you have any info/link to mediatek sources ?
Click to expand...
Click to collapse
MaRtYy01 said:
Yep,agreed.With the years cyanogenmod went on its own and its not really based on aosp right now,while omni is more aosp based rom.
Click to expand...
Click to collapse
[email protected] said:
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
---------- Post added at 03:31 AM ---------- Previous post was at 02:52 AM ----------
Can you link me any device/vendor tree . I'll try to compile cm12.1.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
pix106 said:
A few month ago, with a friend we did this for omnirom, we got boot (prebuilt kernel), graphics, but no wifi etc... : https://github.com/PixNDom/android_device_lenovo_Tab2A710F https://github.com/PixNDom/android_vendor_lenovo_Tab2A710F (other repos https://github.com/PixNDom).
We stopped as we did not know how to go on.
Yesterday after your advice i started a cm12.1 branch on my github (https://github.com/pix106/android_device_lenovo_Tab2A710F/blob/cm12.1), and got TWRP running using cm12.1 sources (with wrong device id, but it does not matter now).
I tried building the kernel again using lenovo sources (https://github.com/pix106/android_kernel_lenovo_Tab2A710F/tree/lenovo_osc_201511), with cm12, i got the same result than i got with omnirom : no graphics, "GTP Reset", i2C errors...
Thanks for your help
Click to expand...
Click to collapse
pix106 said:
Previously...
Click to expand...
Click to collapse
Try compiling with stock kernel ,
Sent from my A311 using XDA-Developers mobile app
That's what i do, i use prebuilt stock kernel.
But i would like to use kernel sources to build kernel with rom
If cm12 has the same problems as omni its most likely a kernel issue.Or there is something wrong with the sources.
I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome
pix106 said:
I have worked on building CM12.1 today, and updated the first post
System is booting, adb and logcat work.
I added a few mali and hw related blobs, and a script to extract blobs from a file system dump instead of using adb to extract them from a running stock rom.
Any comment, hint, link, collaboration is welcome
Click to expand...
Click to collapse
Cm12.1 booted succesfully. Then what are issues.
Sent from my A311 using XDA-Developers mobile app
[email protected] said:
Cm12.1 booted succesfully. Then what are issues.
Click to expand...
Click to collapse
Yesterday only adb and logcat were working.
Today, with a few MTK related flags, and a fresh build while i was at work, bootanimation starts
I'm going to add the missing files i detect from logcat and see what happens next...
After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?
pix106 said:
After adding libxlog to PRODUCT_PACKAGES and providing a source for it, to avoid : cannot locate symbol "__xlog_buf_printf" referenced by "libdpframework.so", I got bootanimation.
I then added a few missing files as blobs.
Here are some errors i get :
Code:
E/audit_rules( 135): Could not read audit rules /data/misc/audit/audit.rules: No such file or directory
I/Vold ( 131): Vold 2.1 (the revenge) firing up
D/Vold ( 131): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 131): Volume usbotg state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 131): Check if PFE is activated on Boot
E/Cryptfs ( 131): Bad magic for real block device /[email protected]
E/Cryptfs ( 131): Error getting crypt footer and key
W/DirectVolume( 131): Deprecated implied prefix pattern detected, please use '/devices/platform/mtk-msdc.0/mmc_host*' instead
I/[MALI][Gralloc]( 132): dlopen libtz_uree.so fail
E/HAL ( 132): dlopen failed: library "libtz_uree.so" not found
I/[MALI][Gralloc]( 207): dlopen libtz_uree.so fail
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ifb1/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 520): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/android.os.Debug( 522): failed to load memtrack module: -2
E/MediaPlayerFactory(15733): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15733): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
E/CameraService(15733): setUpVendorTags: Vendor tag operations not fully defined. Ignoring definitions.
E/HAL (15733): load: module=/system/lib/hw/audio.primary.mt8127.so
E/HAL (15733): dlopen failed: cannot locate symbol "_ZN7android11AudioSystem24getVoiceUnlockDLInstanceEv" referenced by "audio.primary.mt8127.so"...
E/AudioFlinger(15733): int android::load_audio_interface(const char*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
E/MonoPipe(15733): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
E/AudioPolicyManager(15733): Default device 00000002 is unreachable
E/AudioPolicyManager(15733): Failed to open primary output
If add libtz_uree.so, hwcomposer (blob) fails, bootanimation does not start anymore.
I also tried adding libdashplayer to PRODUCT_PACKAGES, but it didn't help. And i have no source.
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Does anyone have a recent repository for mediatek sources, so hwcomposer (and other files that are blobs for now) could be built ?
Click to expand...
Click to collapse
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.
MaRtYy01 said:
Can't you use something from the fire 2015 device tree?Its fully complete,the cm12.1 for it is bugless.Not sure if building roms works like that,but if you are missing drivers or something since it has the same chipset and kernel the stuff from it might work,I guess.
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
BTW as far as I know mediatek has no official source like qualcomm,thats why building roms for it is an issue.
Click to expand...
Click to collapse
Thanks, i'll have a look at this.
Either try to build it changing hardware related stuff, or pick a few things from it... or both.
I had already looked on fire 2015 source on github in 2015, it has changed since then too.
At the moment, i'm trying to build with some other mt8127 github repo (https://github.com/neporood/android_device_viking_mt8127), changing hardware stuff.
Thanks
pix106 said:
During a previous omnirom 5.1 build with a friend (https://github.com/PixNDom/android_device_lenovo_Tab2A710F), we used https://github.com/aomp/android_mediatek_frameworks
It allowed to build some libs, but it's rather old, i think.
Click to expand...
Click to collapse
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware
pix106 said:
sorry, i actualy wanted to mention https://github.com/aomp/android_mediatek_hardware
Click to expand...
Click to collapse
I'm now trying to build using this hardware/mediatek repo, it should provide libs that are blobs for now.
After adding a few .h files, it builds fine, but i don't get all the libs that should be built from this repo, although i added them to PRODUCT_PACKAGES.
I'll push these changes to github.
Even with a linux and python dev experience, i'm quite new to building roms, i may have missed a few things.
I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?
thE_29 said:
I made some ROMs for my Nexus4 and even there, you needed some closed source libs from LG which was not so easy to obtain.. On a damn nexus device..
Some people mentioned that an Amazon Fire tablet is mostly the same tablet..
The CPU looks the same for the Fire HD 7" (4th gen - 2014) and the GPU is the same from FireHD 8.9" (2.5th Gen) and Fire HD 7 (3rd Gen).
Does CM and/or other Custom ROMs work with Amazon-Fire tablets?
Click to expand...
Click to collapse
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.
pix106 said:
apparently it does, so there's hope.
I tried building using a mt8127 device tree and vendor from github, with my device tree and his vendor.
I have also made a "noblob" build (before using the hardware/mediatek repo) so that blobs can be pushed.
Click to expand...
Click to collapse
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).
MaRtYy01 said:
Can you provide cm12.1 meta inf folder and boot.img?I feel like the one from the amazon fire is superpatched because of fire os crap and cant be ported and Im trying to make a flashable version of your modified stock rom but I dont have meta inf folder(tried one from cm12.0 from one mt6582 device,it did boot but it got stuck at the first boot loading screen).
Click to expand...
Click to collapse
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .
pix106 said:
I tried too a few months ago, neither did it boot.
The "noblobs" build i did a few days ago : https://mega.nz/#F!i5h23AKY!jnsxiU8Ob0WiDt1YnSabLg
I'm quite sure a few needed init scripts are missing from this build, and from the device tree in general.
Happy testing .
Click to expand...
Click to collapse
is this build boots or not . (just asking) by the way :good::good:
[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
Its stuck on the bootlogo,since it has no blobs.
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.
[email protected] said:
is this build boots or not . (just asking) by the way :good::good:
Click to expand...
Click to collapse
MaRtYy01 said:
Its stuck on the bootlogo,since it has no blobs.
Click to expand...
Click to collapse
Exactly. It boots, adb and logcat work, but nothing more.
Missing files can be looking for errors in logcat, and be pushed "live" from stock rom dump.
MaRtYy01 said:
BTW the results of my "testing"
-changing the boot.img didnt help,the frecking amazon fire cm12.1 refuses to boot no matter what I do
Click to expand...
Click to collapse
no adb nor logcat ?
MaRtYy01 said:
-the updater script seemed useless,since the system folder in the roms built from source is in just one file
Click to expand...
Click to collapse
is /system mounted ?
MaRtYy01 said:
Anyway,got another idea.If I do a backup of system via twrp I probably can use the updater script with it.
Click to expand...
Click to collapse
i did not understand what you are planning to do... anyway good luck with it

Random rebooting issues after the Android 10 update [Logcat inside]

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.

cannot set lock screen pin, pattern or password on my samsung galaxy tab

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.

Categories

Resources