Related
I upgraded my XDA Exec with the new ROM 1.30.162 WWE and Activesync 4.1 but each time I sync, I get a "bad_pool_header" error on a blue background which crashes my machine.
I installed Activesync 4.1 on another laptop to check if this problem was due to drivers etc on my main laptop, and discovered that the device syncs with no problems. There is, therefore, a conflict between the new Activesync 4.1 or the new ROM, and something on my main laptop.
Has anyone come across this problem?
Thanks
The problem is definitely on your PC. Reinstall motherboard drivers, reflash bios, remove antivirus, reinstall windows, etc.
Thanks - pretty drastic...!
Is there a short cut? ie reinstalling drivers one by one? If so, which are likely to be the main culprits? Motherboard? Broadband modem? etc
The error code after reboot of the laptop is:
BC code 19 BCP1:00000020 BCP2: 89A76000 BCP3: 89A766C0 BCP4: 0AD8000
OS Ver 5_1_2600 SP: 2_0 Product 256_1
\WER22c7.dir00\Mini052506-06.dmp
\WER22c7.dir00\sysdata.xml
Does this reveal anything that could explain which driver?
Thanks
10860 said:
Does this reveal anything that could explain which driver?
Click to expand...
Click to collapse
no.
You should create a complete crash dump, and use microsoft debugging tools to find faulting driver. Or better reinstall windows.
I looked at the minidump file and used MS debugger, the readout is below. I am not sure if I did the debugging ok, or how to interpret it. Anything useful in the readout?
Thanks
Loading Dump File [C:\Mini052406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 24 20:25:34.038 2006 (GMT+1)
System Uptime: 0 days 0:52:32.633
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, 88187000, 881876c0, ad80000}
Probably caused by : Unknown_Image ( nt!KeBugCheck2+4d4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 88187000, The pool entry we were looking for within the page.
Arg3: 881876c0, The next pool entry.
Arg4: 0ad80000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 88187000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 8053331e
STACK_TEXT:
f78cab74 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x4d4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeBugCheck2+4d4
8053331e ?? ???
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeBugCheck2+4d4
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Nothing useful, minidump does not have enough information
It is very difficult to debug pool corruptions.
Hi all.
This thread only for developers! Only! No questions - when?!!!!!!!
This is my attempt to porting android on S8600.
I wrote custom bootloader - emmcboot, based on codeaurora LK-bootloader.
Bootloader is successfully start, work and trying to load android kernel from internal
microsd card.
Now is unsuccessfully,after type message "Uncompressing Linux... done, booting the kernel." device rebooted or stopped.
[370] Panel is power on
[370] Display initialized
[370] Display logo
[370] Waiting for modem+++
[370] Waiting for modem: Done
[370] smem ram ptable found: ver: 0 len: 6
[370] scratch: 0x8000000
[370] Starting in SD mode!
[370] SD_DETECT pin : 0x0
[380] Initializing MMC host data structure and clock!
[380] Error No. 2: Failure Initializing MMC Card!
[400] Decoded CID fields:
[400] Manufacturer ID: 27
[400] OEM ID: 0x5048
[400] Product Name: SD16G
[400] Product revision: 3.0
[400] Product serial number: 7C88FF04
[400] Manufacturing date: 2 2012
[410] Serial number -[410] serial number:
[410] partition misc doesn't exist
[410] error in emmc_recovery_init
[580]
kernel @ 208000 (4132528 bytes)
[580] ramdisk @ 1200000 (175204 bytes)
[580] cmdline = 'console=null androidboot.hardware=qcom user_debug=31'
[580]
Booting Linux
[580] smem ram ptable found: ver: 0 len: 6
[580] booting linux @ 0x208000, ramdisk @ 0x1200000 (175204)
[590] cmdline: console=null androidboot.hardware=qcom user_debug=31
Uncompressing Linux... done, booting the kernel.
source code for lk-bootloader for S8600:
https://github.com/Oleg-k/LK_BOOT_S8600
To build for S8600, type: "make -j4 s8600 EMMC_BOOT=1"
Also, i got memory dump, stage - after load oemsbl and before loading my bootloader.
as we see, oemsbl decompress and load apps_compressed.bin into memory,
starting at 0x200000.
https://www.dropbox.com/s/5wf6dp5gfgudkdc/MEM_DUMP_128MB.rar
And for for understanding boot process on MSM7x30, read this:
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess#BootProcess
Welcome back my friend ))
If you able to port,I 100% will buy S8600
Good Luck
I was actually going to ask you what happened to the wave 3 port. Anyway Welcome back . But a question why don't you help rebellos and volk in the wave and wave II porting ? So the porting can be a bit more better. Just my question. :good:
Sounds interesting.
1.
You found ELF files for S8600 Boot ?
2.
You found way without JTAG, or JTAG is needed to write your Boot?
Thanx in advance.
Best Regards
CONFIG_DEBUG_LL
and
CONFIG_EARLY_PRINTK
plx <3
it's my current config for my kernel:
adfree said:
Sounds interesting.
1.
You found ELF files for S8600 Boot ?
2.
You found way without JTAG, or JTAG is needed to write your Boot?
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
No, don't ELF files for S8600, i wrote new bootloader for boot linux kernel.
Now i use JTAG, but if we find a way to cript my bootloader,like appsboot.mbn,we will use regular multiloader
So cool!
http://forum.xda-developers.com/showthread.php?t=1443575
Blowfish encryption
Click to expand...
Click to collapse
Maybe PlatformDownloader_S8600_KI5.exe maybe have unsecured Boot...
But I can't flash nor I have connected my S8600 with RIFF...
TPs seems to small for my big Fingers...
Best Regards
oleg_k said:
it's my current config for my kernel:
Click to expand...
Click to collapse
Thanks. I'd check debug macros and debug uart configuration. There's few UART ports in it, and maybe kernel is printing to the wrong one... though this wouldn't explain why kernel unpacker is printing something (Uncompressing and booting comes already from zImage) - this would indicate that debug port number is correct. Are you sure that kernel and ATAGs location is correct, and RAM is set up properly by LK? Maybe something bad happens when kernel proceeds to enabling MMU and caches... I'm pretty clueless. :<
I collected some links I found useful in this article: http://xda-university.com/as-a-developer/porting-android-to-non-android-devices
Especially interesting for you might be last link in "Custom bootloader" section.
No, don't ELF files for S8600, i wrote new bootloader for boot linux kernel.
Now i use JTAG, but if we find a way to cript my bootloader,like appsboot.mbn,we will use regular multiloader
Click to expand...
Click to collapse
For S8500 I found way to write direct into OneNAND at:
Code:
0x0010 0001
No need to encrypt something...
With Multiloader... choose ETC.
http://forum.xda-developers.com/showpost.php?p=37229969&postcount=37
S8600 not tested...
This is far far away from perfect... but maybe helpfull.
Need someone who is able to remove restriction from ML to use lower adresses then 0x10000...
I was only able to change text strings... in ML...
Best Regards
On first page i posted bootloader source and memory dump, stage - after load oemsbl and before loading my bootloader.
To Adfree,
S8600 don't use OneNAND, used EMMC flash memory (like sd-card).
Today I've found S8600XXKI9.zip
I have forgotten this Firmware... but I have now short compared with Bootfiles from XXKJC... BIG differences... So I think this should be nearly identical with PlatformDownloader_S8600_KI5.exe
Still unsolved to decrypt or extract content of:
PlatformDownloader_S8600_KI5.exe
and
PlatformDownloader_S8600_KJ7.exe
Best Regards
Not my S8600... but user tried PlatformDownloader_S8600_KJ7.exe
It seems it was wrong Partition Table aka partition.bin...
Code:
Boot Binary Download Start Ch[0]
Appsboot 338.7KB OK[1.1s]
OemSbl 1757.7KB OK[1.8s]
ERR : NAK_FLASH_ERROR 0
Error : [B]partition Write[/B] [0.2s]
ERR : NAK_FLASH_ERROR 0
Download Start Ch[0]
Amss 16654.3KB OK[15.6s]
Apps 29622.3KB OK[54.1s]
_Open_Europe_Common 40370.2KB OK[73.5s]
(Low) 2980.3KB OK[1.9s]
ERR : NAK_INVALID_CONTENT 0
ERR : _Open_Europe_Common Erase
Now S8600 ask for QHSUSB_DLOAD
My first idea is Qualcomm QPST now...
Or maybe if Driver used, then Multiloader will work again... for second attempt..
Found only 64 Bit Driver yet... not tested nor Thread... only attachment...
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
Will check also QPST to check what is needed...
Best Regards
Edit 1.
More Driver...
http://forum.xda-developers.com/showpost.php?p=21911621&postcount=2
Okay...
It seems for QPST fsbl.mbn is missing...
I can remember from old MSM6250 handsets it is mandatory to have all files for QPST... because otherwise you need JTAG...
Important...
Qualcomm not use Encryption for QPST files...
This is Samsung thingie + "end.bin" last 1024 Byte...
So decrypt all Bootfiles and cut last 1024 Byte...
For fsbl.mbn I will check JTAG dump from S8600...
Best Regards
Edit 1.
http://forum.xda-developers.com/showthread.php?t=1367055
downgrade_WM6_boot.zip contain fsbl.mbn ... maybe as example...
http://forum.gsmhosting.com/vbb/f634/htc-desire-s-qhsusb_dload-driver-1436354/
Found this...
Here is also fsbl.mbn maybe not available... or...
But maybe if we can attach such S8600 we can see few infos...
Best Regards
Edit 1.
About QPST Version contain this eMMC...
Code:
4. RELEASE NOTES
...
10/27/11 QPST [B]2.7.378[/B]
1) Add support for QSC11x5 CDMA only (4073) and CDMA+GSM (4074).
2) Fix problem with eMMC Software Download not correctly patching addresses > 8 GB.
10/13/11 QPST 2.7.377
1) Fix crash when QPSTServer.config are NULs (bad format).
2) Add model ID 4072 = "APQ8064". Apps processor only, no service programming.
3) Change flash programmer name from nprg9615.hex to nprg9x15.hex.
4) Add emergency download support for user partitions.
5) Fix case where user partition download fails if the flash programmer is on a file share.
6) Fix error case when add port is used but no port is specified.
7) Fix case where restoring an EFS file doesn't work if the file was modified by QXDM.
8) In Service Programming BC SMS fix case where if user enters 32 as the service type it get written to NV as 4096.
9) Fix case where a phone will stay in "no phone" state if the phone takes > 20 seconds to reboot.
10) Take care of cases in eMMC Software Download where we try to lock the disk volume but the drive letter isn't available.
11) Fix "server busy" issue when a device connects but it's modem isn't running.
12) Insert more status message in Memory Debug app so that we can see why fast unframed dump failed.
8/17/11 QPST 2.7.375
1) Add support for MDM9615 (model 4070). Rename model 4068 to 7627A-ANDROID from SURF7627A.
Add model 4071 (7627A-WinMob). Add 1x/UMTS service programming to 4068 and 4071.
2) eMMC Software Download: Don't try to lock volume if drive letter not present.
Devices that use GPT will not mount and get a drive letter assigned.
7/22/11 QPST 2.7.374
1) Added missing file to installer to fix Service Programming problem in 2.7.373.
2) For eMMC Software Download, abort the download if a sparse="true" directive is present.
Sparse files cannot be downloaded with QPST, only with fastboot.
3) Began the process of moving QPST application and server settings from registry to
configuration files.
4) Added more error checking to EFS Explorer file drop code.
7/5/11 QPST 2.7.373
1) Add support for SURF8960 model ID 4069.
2) Fix issue with Port Enable/Disable for IP Ports.
3) NAND Software Download: Correct flash programmer descriptions for 7225A, 7625A, 7227A, and 7627A.
4) Roaming List Editor: Added two new bands LTE 24 and LTE 25.
5) eMMC Software Download:
- Fix problem where some file names print as "(null)".
- Add support for Meta Build contents.xml file ("Build Contents"). The contents file will provide the path for the
rawprogram and patch files, extra search paths, and names of flash programmer and boot image files.
- Ignore unexpected elements in schema.
- Support zeroout directive to zero parts of partitions.
- Allow usage by app of "orderly" as well as surprise removal storage devices.
- Add support for computations in the <patch> (CRC32 for GPT support), <program>, and <zeroout> directives.
6) EfsExplorer:
- Enable reset button in Efs Explorer even if target not in offline mode.
- More text description in Mode column for Efs Explorer
- Modify the list context menu of Efs-Explorer.
- If the proposed item file size copy is > 2048 bytes, warn the user and bail out.
...
Adfree,
link pls for founded S8600XXKI9.zip
link pls for founded S8600XXKI9.zip
Click to expand...
Click to collapse
http://hotfile.com/dl/145796951/79ecec6/S8600XXKI9.zip.html?lang=de
Try this. If not then I search again...
About fsbl.mbn...
I have searched for fsbl_hw.c string in 4 GB JTAG dump SAMSUNG_GTS8600_FullFlash.bin...
Can not find so I think fsbl is not or in other area...
About your Memory Dump FROM_MEM_0_128MB.bin
I am not 100 % sure but maybe read problems...
Short tried to extract Cert, but string Qualcomm is not written correct...
Q5alcomm1
qualcoem.com
Click to expand...
Click to collapse
Best Regards
I try to read again memory dump )
thanks for links...
Also,
i find,what samsung used OKL4 Microkernel 3.0 (maybe 4.0)
http://wiki.ok-labs.com/Release/3.0
About ver 4.0 --
The OKL4 Microvisor is designed from the ground up as a high-performance mobile virtualization platform. It is a microkernel-based embedded hypervisor - called a Microvisor, with a small footprint and the right combination of performance and hardware support to target mobile telephony use. The OKL4 Microvisor 4.0 is distinguished by supporting mobile virtualization, componentization, and security, enabling a new generation of applications and capabilities with impact across the mobile ecosystem.
OKL4(with Qualcomm RTOS) also used in modem AMSS
http://forum.xda-developers.com/showthread.php?t=1829915
Need overview/list with Firmware packages with Bootfiles included...
Here this is what I have...
Later I will compare if difference...
Code:
XXKI9
XXKJC
S8600BOKJ1_TPLKJ1.rar
S8600BOKK6_S8500TPLKK7_T-Mobile.rar
S8600JPKK2_S8500OJPKK2_OJP.rar
S8600ZCLA1.7z
S8600NAKL1_S8600EPLKL1
Best Regards
UPDATE
Initial OmniROM release for Athene out now:
omni-7.1.1-20170219-athene-HOMEMADE.zip
--- Original OP below ---
Hi guys, I have started the bringup for OmniROM on Athene:
Device
Kernel
It starts to boot up, but gets stuck in the bootanimation and restarts soon after. According to dmesg / logcat, the modem does not come up (see attached files). I compared init.rc files and blobs being used with other roms (lineage / aex), but couldn't identify the root cause for that error at this early stage:
Code:
[ 7.022888,0] Fatal error on the modem.
[ 7.022913,0] modem subsystem failure reason: fs_device_efs_rmts.c:175:Invalid shared ram address from Apps.
@rahulsnair, @Silesh.Nair (or anybody else): Can you guys please help out here, is that something you have come across in any of your bringups? Really would like to bring Omni to life on Athene.
Thanks in advance :good:
Looks like rmt_storage can't load the needed modem firmware :
Code:
09-21 03:07:13.861 342 342 D rmt_storage: GZFSG open /fsg/athene_dsds_emea.img.gz
09-21 03:07:13.861 342 342 E rmt_storage: Couldn't open /fsg/athene_dsds_emea.img.gz, trying default for product-radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/athene_emea.img.gz, trying default for radio
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/emea.img.gz, trying default
09-21 03:07:13.862 342 342 E rmt_storage: Couldn't open /fsg/0.img.gz
09-21 03:07:13.862 342 342 I rmt_storage: rmt_storage_open_cb: Unable to open /boot/modem_fsg
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Code:
strace -fF -s 1000 rmt_storage > /sdcard/rmt_storage_strace.txt
vache said:
Looks like rmt_storage can't load the needed modem firmware :
Check that /fsg partition is mounted (can't check that in logs cause it's not full logs) and files are there.
You can also try to "strace" rmt-storage process :
Click to expand...
Click to collapse
Good point, thanks. Haven't checked the mounts on boot yet. Eventually, fstab.qcom does not get parsed.
Making some progress: There is an issue with the ramdisk of the inline-built kernel: It is not picking up the correct .rc files. I don't get where these references to "recovery" are coming from:
Code:
<13>[ 3.022567,0] init: init second stage started!
<11>[ 3.207517,0] init: waitpid failed: No child processes
<11>[ 3.209434,0] init: property_set("ro.com.google.clientidbase", "android-motorola") failed
<11>[ 3.209584,0] init: property_set("ro.config.notification_sound", "Argon.ogg") failed
<11>[ 3.209599,0] init: property_set("ro.config.alarm_alert", "Helium.ogg") failed
<11>[ 3.209710,0] init: property_set("ro.config.ringtone", "Orion.ogg") failed
<13>[ 3.209803,0] init: (Loading properties from /default.prop took 0.00s.)
<11>[ 3.210260,0] init: /init.rc: 12: invalid command 'setcon'
<11>[ 3.210326,0] init: /init.rc: 62: invalid command 'load_all_props'
<11>[ 3.210406,0] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<13>[ 3.210688,0] init: (Parsing /init.recovery.usb.rc took 0.00s.)
<13>[ 3.210735,0] init: (Parsing /init.recovery.service.rc took 0.00s.)
<11>[ 3.210812,0] init: could not import file 'init.target.recovery.rc' from '/init.recovery.qcom.rc'
<13>[ 3.210827,0] init: (Parsing /init.recovery.qcom.rc took 0.00s.)
However, having flashed a Lineage kernel, it's booting up now.
@vache: /fsg indeed was not mounted. I think there is an issue with the mkdir, will amend that now.
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
golden-guy said:
Unhandled fsg_file security context on the fstab /fsg entry was the root cause for not mounting /fsg. Omni kernel booting up now.
Click to expand...
Click to collapse
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
vache said:
Well done
To get RIL working, you need to add android_system_qcom from Lineage in your manifest and rebuilt.
Or you can push libqsap_sdk.so manually.
Click to expand...
Click to collapse
Thanks mate, I have done that yesterday to get RIL working (radio logcat showed that rild was complaining about that missing libqsap_sdk.so lib). All fine there already.
But I am still struggling with at least three things atm: Sensors, media playback and camcorder.
Sensors: I can see them initialized, but they don't return any values. According to logcat, e.g proximity gets disabled on screen on (sic!) Which sounds weird tbh
Media playback: Acodec cannot instantiate decoders upon ringtone playback and when music is to be played via bluetooth. mp3/mpeg playback does work when played via phone' speaker though. It could be a codec issue, but it could be audio policy / routing related. We are using a custom policy, aren't we?
Camcorder - didn't look into that yet. But is very likely related to media codec issue.
Will add some logs to further explain.
EDIT: Logs are added now.
PS: Device repo updated
Will cross-check with LineageOS, but the lack of sensor data might be permission related after all. All sensors seem to be up and configured, with their /dev and /sys entries being populated. Unfortunately, there is no error to be seen in the logs, giving no indication of the root cause...
Got the sensor issue sorted. It was selinux related again - what else. :silly:
Anyhow, one issue less.
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Sent from my Moto G4 Plus using Tapatalk
vinylmeister said:
Great news. How many issues are left now? :highfive:
Seriously, i would really appreaciate it if it´ll be released and maintained sometime... :fingers-crossed:
Click to expand...
Click to collapse
+1
1chrome said:
He is courteous enough to give us status updates on what is happening and what he is currently fixing.
I dont think he would appreciate the ETA-ish question.
It will be released when he is done. Im sure he is not on this full time. Have patience.
Click to expand...
Click to collapse
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
vinylmeister said:
Didn't you realize that the issue related sentence was just ironic? The high-five smiley should indicate that, followed by seriously...
Click to expand...
Click to collapse
Sorry man my bad... smileys didn't show up on my Tapatalk!
Sent from my Moto G4 Plus using Tapatalk
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
golden-guy said:
Vorbis decoder and camcorder are still open.
I'd love to have a fully working Omni build up by now, but time-wise this is a best-effort activity.
It is ready when it's done.
Click to expand...
Click to collapse
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
vache said:
Could you grab fresh logs after trying to record a video ? Can't find traces in current logs.
Also, did you try with different camera apps ?
Click to expand...
Click to collapse
I tried with Snap and SnapDragonCamera. I wanted to do that with a fresh build. After having synched sources, mm-camera daemon keeps crashing and causing bootloops. Omni has updated their manifest to r14, also, lineage seems to have merged in fresh caf sources causing issues with qcom blobs. If I had known that earlier, I wouldn't have synched anew.
I see u uploaded to afh is it ready for testing I'm excited
joeeboogz said:
I see u uploaded to afh is it ready for testing I'm excited
Click to expand...
Click to collapse
????!!
Good catch! ?
Yes, it's up for testing now: https://www.androidfilehost.com/?fid=457095661767137952
Please note that this is an early ALPHA build: Media playback (ogg/mp4) and camcorder are still broken. But apart from that it seems to work just fine.
Need Assistance in Modifying a BenQ T3 (Performance wise, Reducing Apps & Flashing)
Hello,
Before I begin explaining my predicament I would like to state that this is essentially my first post on this website so I apologize in advance if I am essentially breaching any forum policies or rules and regulations for that matter. The moderators can amend this post as they may see fit since I am not too familiar with how things work here. That said let me get straight into what I am hoping to achieve.
I have a Benq T3 Android phone that I would like to customize, upgrade, add new features, remove flagship (reads default phone) applications, since they're essentially hogging space on the phone, and I hardly use them & finally upgrade the said former to a new Android (custom) or standard OS if it's possible based on the details I will be posting below. With all this I would like a custom or simple boot up screen as well without the Benq logo flashing all over the screen every time I power on or restart the phone.
The purpose of this exercise is:
1) I need to push this phone to the maximum limits of its hardware capability, overclocking, optimizing RAM, increasing swap space etc (currently it's not fast enough for me)
2) Remove all unnecessary applications completely (Flipboard, Benq applications that are part of the phone, WPS office), all these are by default inside the phone and even though I have tried uninstalling them they only uninstall the updates and the application still sits in hogging the phone space, which is quite frustrating.
3) To see if any relatively latest Android version could be used with the acceleration (hypothetically) done in the above point (1).
4) Flashing a new ROM (if necessary) something that may actually make this phone a better version of itself.
What will I use this phone for (Once it is done)
1) Twitter (Main function)
2) Texting (Main function)
3) Whatsapp (Main function)
4) Newspaper Applications~Text Reading Mainly, some sort of Flash / HTML5 as well (Main Function)
5) PDF reading (Main Function)
6) Discussion Board Browsing (Main function)
7) Emails (Secondary Function) ~ Using an Email client (Also need recommendations of light Apps that might work on the new made over system)
8) Youtube (Secondary Function)
9) Soundcloud (Secondary Function)
10) Word Processing including Spreadsheet + Ppt stuff occasionally (Secondary Function)
VERY IMPORTANT ~ EVERYTHING OTHER THAN WHAT I HAVE WRITTEN NEEDS TO GO
VERY IMPORTANT ~ THIS PHONE IS ROOTED VIA KINGO ROOT ALREADY
What I have currently
1) A computer running Windows 7 Home Premium x64 bit, i5 Gen 2 with 6 GB DDR2 RAM - Dell Inspiron N5110
2) An internet connection of around 20-30 Mbps
3) No programming ability whatsoever (A complete Newbie while being a downright noob in such stuff)
4) 3 hours a day (at best) to understand, implement and get this over with ASAP
5) English as my first language
6) Nothing else I am afraid
Please note that my generic aim to customize this BenQ phone is in pursuits of attaining maximum performance that the phone can generate for me while running the basic apps that I have mentioned above.
----------------------------------------------------------------------------------------------------------
That said I will now proceed to mention all my phone's tidbits based on the information that I gathered via Aida64 application
----------------------------------------------------------------------------------------------------------
Code:
----------------------------------------------------------------------------------
System
----------------------------------------------------------------------------------
Manufacturer - BenQ
Model - BenQ T3
Board - MSM8926
Device - T3_17A
Hardware - QCom
Platform - msm8226
Product - T3_08
Installed RAM - 1 GB
Total Memory - 866 MB
Available Memory - 256 MB
Internal Storage (Total Space) - 2051 MB
Internal Storage (Free Space) - 732 MB
----------------------------------------------------------------------------------
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.autofocus
android.hardware.camera.flash
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.protrait
android.hardware.sensor.accelerometer
android.hardware.sensor.compass
android.hardware.sensor.light
android.hardware.sensor.proximity
android.hardware.sensor.stepcounter
android.hardware.sensor.stepdetector
android.hardware.telephony
android.hardware.telephony.gsm
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.district
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.sip
android.software.sip.voip
com.nxp.mifare
mobi.qiss.preload.benq
mobi.qiss.preload.benqhome
Code:
----------------------------------------------------------------------------------
CPU
-----------------------------------------------------------------------------------
SoC Model - Quadcomm Snapdragon 400 (MSM8926)
Core Architecture - 4x ARM Cortex-A7 @ 1190 MHz
Manufacturing Process - 28 nm
Instruction Set - 32-bit ARMv7
CPU Revision - r0p3
CPU Cores - 4
CPU Clock Range - 300 - 1190 MHz
Core 1 Clock - 787 MHz
Core 2 Clock - 787 MHz
Core 3 Clock - 787 MHz
Core 4 Clock - (Sleeping)
CPU Utilization - 74%
Scaling Governor ondemand
CPU ABI - armeabi-v7a
CPU ABI2 - armeabi
AES - Not Supported
NEON - Supported
SHA1 - Not Supported
SHA2 - Not Supported
Code:
------------------------------------------------------------------------------------
DISPLAY
------------------------------------------------------------------------------------
Screen Resolution - 540 x 960
Screen Size - 56 mm x 99 mm
Screen Diagonal - 4.48 inches
Pixel Density - 246 dpi (hdpi)
xdpi / ydpi - 245 / 246 dpi
GPU Vendor - Qualcomm
GPU Renderer - Adreno 305
GPU ALUs - 24
Current GPU Clock - 320 MHz
CPU Clock Range - 200 - 450 MHz
GPU Utilization - 0%
Scaling Governor msm-adreno-tz
Refresh Rate - 62 Hz
Default Orientation - Portrait
OpenGL ES Version - 3.0
GPU Version - OpenGL ES 3.0 [email protected]
[email protected]
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
4448_release_ENGG
([email protected])
--------------------------------------------------------------------------------------
GL_AMD_compressed_ATC_texture
GL_AMD_performance_monitor
GL_AMD_program_binary_Z400
GL_EXT_debug_label
GL_EXT_debug_marker
GL_EXT_discard_framebuffer
GL_EXT_robustness
GL_EXT_texture_format_BGRA8888
GL_EXT_texture-type_2_10_10_10_REV
GL_NV_fence
GL_OES_compress_ETC1_RGB8_texture
GL_OES_depth_texture
GL_OES_depth24
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_element_index_uint
GL_OES_fbo_render_mipmap
GL_OES_fragment_precision_high
GL_OES_get_program_binary
GL_OES_packed_depth_stencil
GL_OES_depth_texture_cube_map
GL_OES_rgb8_rgba8
GL_OES_standard_derivatives
GL_OES_texture_3D
GL_OES_texture_float
GL_OES_texture_half_float
GL_OES_texture_half_float_linear
GL_OES_texture_npot
GL_OES_vertex_half_float
GL_OES_vertex_type_10_10_10_2
GL_OES_vertex_array_object
GL_QCOM_alpha_test
GL_QCOM_binning_control
GL_QCOM_driver_control
GL_QCOM_perform_global_mode
GL_QCOM_extended_get
GL_QCOM_extended_get2
GL_QCOM_tiled_rendering
GL_QCOM_writenly_rendering
GL_EXT_sRGB
GL_EXT_sRGB_write_control
GL_EXT_texture_sRGB_decode
GL_EXT_texture_filter_anisotropic
GL_EXT_multisampled_render_to_texture
GL_EXT_color_buffer_float
GL_EXT_color_buffer_half_float
Code:
--------------------------------------------------------------------------------
NETWORK
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
TELEPHONY
--------------------------------------------------------------------------------
Phone Type - GSM
SIM State - Absent
ICC Card - Not Present
---------------------------------------------------------------------------------
WIFI
---------------------------------------------------------------------------------
State - Enabled
SSID - DSC Network
BSSID - d4:6e:0e:ee:2c:6b
Hidden SSID - No
MAC Address - 1c:e1:92:1c:11:ba
Signal Strength - 47 dBm (Excellent)
Link Speed - 65 Mbps
Network ID - 3
Gateway - 192.168.0.1
Netmask - 255.255.255.0
DNS1 - 192.168.0.1
DHCP Lease Duration - 2 hours
Wi-Fi Aware - Not Supported
Wi-Fi Direct - Supported
Code:
--------------------------------------------------------------------------------
BATTERY
--------------------------------------------------------------------------------
Power Source - A/C Charger
Level - 67 %
Status - Charging
Health - Good
Technology - Li-ion
Temperature - 40.6 C
Voltage - 4.044 V
Capacity (Reported by Andorid) - 2520 mAh
Code:
--------------------------------------------------------------------------------
ANDROID
---------------------------------------------------------------------------------
Andriod Version - 4.4.2 (KitKat)
API Level - 19
Rooted Device - YES
Android ID - 63f50428151aae1c
Baseband - MPSS.DI.2.0.1.c1-00223-
M8926DAAAANAZM-1
Build ID - SWEP_GA31I17A_v01.057.03.g_08
Codename - REL
Fingerprint - BenQ/T3_08/T3_17A:4.4.2/
KVT49L/
SWEP_GA3I17A_v01.057.03
.g_08:user/release-keys
ID - KVT49L
Incremental - 376
Java Runtime Version - Android Runtime 0.9
Java VM Version - Dalvik 1.6.0
Java VM Heap Size - 96 MB
Kernel Architecture - armv7I
Kernel Version - 3.4.-g3104c58
([email protected]
)(gcc version 4.7 (GCC))
#1 SMP PREEMPT Thu Mar
12 10:52:17 CST 2015
Tags - release-keys
Type - User
Google Play Services Version - 11.5.09 (034-164803921)
OpenSSL Version - OpenSSL 1.0.1e 11 Feb 2013
ZLib Version - 1.2.8.f-linuxfoundation-
mods-v1
ICU CLDR - 23.0
ICU library Version - 51.1.0.1
ICU Unicode Version - 6.2
Android Language - English (United States)
Configured Time - Malaysia Time (UTC+08:00)
UpTime - 01:16:03
Code:
-----------------------------------------------------------------------------
DEVICES
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Rear Facing Camera
-----------------------------------------------------------------------------
Resolution - 8.0 MP (3264 x 2448)
Video Resolution - 2.1 MP (1920 x 1080)
Focal Length - 3.85 mm
Focus Modes - auto, infinity, macro,
continious-video,
continuous-picture
Video Snapshot - Supported
Video Stabilization - Not Supported
Zoom - Supported
Smooth Zoom - Not Supported
Auto Exposure Locking - Supported
Auto White Balance Locking - Supported
Flash - Supported
-----------------------------------------------------------------------------
Front-Facing Camera
-----------------------------------------------------------------------------
Resolution - 0.3 MP (640 x 480)
Video Resolution - 0.3 MP (640 x 480)
Focal length - 1.21 mm
Focus Modes - Fixed
Video Snapshot - Supported
Video Stabilization - Not Supported
Zoom - Supported
Smooth Zoom - Not Supported
Auto Exposure Locking - No Supported
Auto White Balance Locking - Not Supported
-----------------------------------------------------------------------------
OpenCL Device - QUALCOMM
Adreno(TM)
-----------------------------------------------------------------------------
Device name - QUALCOMM Adreno (TM)
Device Type - GPU
Device Vendor - QUALCOMM
Device Vendor ID - 0xBF4D3C4B
Device Version - OpenCL 1.1 Adreno(TM) 305
Device Profile - Embedded
Driver Version - OpenCL 1.1 QUALCOMM build:
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
448_release_ENGG
(CL3304448)
Build Date: 04/21/14 Mon
Local Branch:
Remote Branch: quic/
LNX.LA.3.5.1_RB1.1
Compiler E031.24.00.14
OpenCL C Version - OpenCL C1.1 Adreno(TM) 305
Clock Rate - 400 MHz
Compute Units - 1
Address Space Size - 32-bit
Max 2D Image Size - 4096 x 4096
Max 3D Image Size - 4096 x 4096 x 512
Max Samplers - 16
Max Work-Item Size - 256 x 256 x 256
Max Work Group Size - 256
Max Argument Size - 256 Bytes
Max Constant Buffer Size - 4 KB
Max Constant Arguments - 8
Max Printf Buffer Size - 1 MB
Native ISA Vector Widths - char1, short1, int1, half1, float1
Preferred Native Vector Widths - char1, short1, int1, long1, half1, float1
Profilling Timer Resolution - 1000 ns
OpenCl Library - /system/vendor/lib/libOpenCL.so
Global Memory - 443684 KB
Global Memory Cache - 8 KB (Read/Write, 64 Byte Line)
Local Memory - 8 KB
Max Memory Object Allocation Size - 443684 KB
Memory Base Address Alignment - 512-bit
Min Data Type Alignment - 64 Bytes
Command-Queue Out of Order Execution - Enabled
Command-Queue Profiling - Enabled
Compiler Available - Yes
Error Correction - Not Supported
Images - Supported
Kernel Execution - Supported
Linker Available - Yes
Linker-Endian Device - Yes
Native Kernel Execution - Not Supported
SVM Automics - Not Supported
SVM Coarse Grain Buffer - Not Supported
SVM Fine Grain System - Not Supported
Unified Memory - Yes
OpenCL Extension
cl_img_egl_image
cl_khr_byte_addressable_store
cl_khr_egl_event
cl_khr_fp16
cl_khr_gl_gl_sharing
cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_int32_extended_atomics
cl_qcom_create_buffer_from_image
cl_qcom_ext_host_ptr
cl_qcom_ion_host_ptr
cl_qcom_limited_printf
cl_qcom_extended_images
-----------------------------------------------------------------------
OpenCL Device - QUALCOMM Krait(TM)
-----------------------------------------------------------------------
Device Name - QUALCOMM Krait(TM)
Device Type - CPU
Device Vendor - QUALCOMM
Device Vendor ID - 0xBF4D3C4B
Device Version - OpenCL 1.1. Krait(TM)
Device Profile - Embedded
Driver Version - OpenCl 1.1 QUALCOMM
build:
LNXBUILD_Nondeterminist
ic_AU+PATCH[ES]_msm8226
_LNX.LA.3.5.1_RB1_CL330
4448_release_ENGG
(CL3304448)
Build Date: 04/21/14 Mon
Local Branch:
Remote Branch: quic/
LNX.L.A.3.5.1_RB1.1
Compiler E031.24.00.14
OpenCL C Version - OpenCL C 1.1. Krait(TM)
Compute Units - 1
Address Space Size - 32-bit
Max 2D Image Size - 8192 x 8192
Max 3D Image Size - 2048 x 2048 x 2048
Max Samplers - 16
Max Work-Item Size - 1 x 1 x 1
Max Work-Group Size - 1
Max Argument Size - 256 bytes
Max Constant Buffer Size - 64 KB
Max Constant Buffer Size - 8
Native ISA Vector Widths - char16, short8,int4, long1, half8, float4
Preferred Native Vector Widths - char16, short16, int16, long1, half16,float16
OpenCL Library - /system/vendor/lib/libOpenCL.so
Global Memory - 443684 KB
Global Memory Cache - 1 MB (Read/Write, 64-byte
line)
Local Memory - 32 KB
Man Memory Object Allocation Size - 443684 KB
Memory Base Address Alignment - 1024-bit
Min Data Type Alignment - 128 bytes
Command-Queue Out of Order Execution - Enabled
Command-Queue Profiling - Enabled
Compiler Available - Yes
Error Correction - Not Supported
Images - Supported
Kernel Execution - Supported
Linker Available - Yes
Little-Edndian Device - Yes
Native Kernel Execution - Supported
SVM Atomics - Not Supported
SVM Coarse Grain Buffer - Not Supported
SVM Fine Grain Buffer - Not Supported
SVM Fine Grain System - Not Supported
United Memory - Yes
OpenCL Extensions
cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_extended_atomics
cl_khr_byte_addressable_store
cles_khr_int64
cl_khr_fp16
No USB devices found.
No CUDA devices found.
No Vulkan devices found.
No PCI devices found.
Code:
----------------------------------------------------------------------------
THERMAL
----------------------------------------------------------------------------
tsens_tz_sensor0 - 42.0 C
tsens_tz_sensor1 - 43.0 C
tsens_tz_sensor2 - 42.0 C
tsens_tz_sensor3 - 42.0 C
tsens_tz_sensor4 - 41.0 C
tsens_tz_sensor5 - 43.0 C
ppm8226_tz - 38.7 C
pa_therm0 - 25.0 C
pa_therm1 - 25.0 C
Battery - 31.6 C
Ok, I did a bit of a mess up with the phone - Sorry! I tried removing the bloatware (BenQ software) using SuperUser app that I had installed previously after the KingoRoot and now the phone has lost it's systemUi
I see no icons on my screen and it takes very long to boot up the phone (heck most times it just gets stuck on the loading screen). I tried to do a master reset by pressing the power button + Volume down and cleaning all user data but everything I try seems to be in vain. The data was reset as I had to enter my google account and all flagship apps lost its updates but even so the result (i.e. no SystemUi) remains.
There seem to be no guides on this phone Model (BenQ - T3) at all on XDA forum or the internet for that matter.
Any suggestions on what can I do next ??
P.S. The phone has no SD card and this is just a Testing phone so I can play around with it as much as I can. Any help on the matter would be much appreciated.
Writing this after I've successfully troubleshooted and resurrected the phone to a much better state. Apparently in my haste to try out things I accidently damaged the launcher for my phone which totally messed up the User Interface.
Nearly three months of searching and reading various online material for my phone (still cannot find stock ROM) without avail I came back on XDA and posted this entire problem from scratch in the Noob Friendly Questions Thread.
Luckily a couple of blokes helped me out on the matter and I have managed to bring my phone back to a working state (typing this post from the XDA app itself on my BenQ)
If you want the reference to the conversation please visit the thread '[HELP THREAD] Ask ANY Question. by immortalneo' and start reading my post from page 4075 onwards.
Tools that I used to rectify this:
1) Adb and Fastboot drivers installed in the PC
2) Rooted BenQ T3 (if you haven't Rooted yet then just download KingoRoot, enable USB debugging and root the phone - Do a Google search and you'll find it pretty easy)
3) KitKat launcher apk app
At first I went into recovery mode and wiped clean the data and cache, this helped me boot into the phone after which I connected it to my PC (USB debugging on) and ran the following command:
Code:
Adb reboot bootloader
The phone then went into Fastboot mode and I had to further write this:
Code:
Fastboot oem unlock
The above command unlocked the bootloader after which I once again booted into the phone recovery and wiped clean the data and cache. When the boot up process was done I had to connect again to the PC (USB debugging on) and install the launcher by writing:
Code:
Adb install [launcher_name]
This repaired my UI and all the icons and screen windows came back to normal, my problem of being stuck at a normal boot up process also resolved once I reinstalled the launcher correctly!
Once the GUI came back I reentered my Google credentials, carefully uninstalled all bloat ware and unnecessary apps via Kingo Super user app and updated all the ones that I use on a daily basis.
I now will look to find TWRP or any custom recovery for my phone and Custom ROMs as well. If anyone can point me to the right direction then that would be highly appreciated !!!
Hi
I'm trying to migrate an existing device tree from lineage 18.1 to 20.
with adb logcat, i get the following error:
VintfObject: VintfObject.verifyWithoutAvb() returns 1: Runtime info and framework compatibility matrix are incompatible: kernelSepolicyVersion = 30 but required >= 33
I could disable this check in frameworks/base/core/java/android/os/Build.java but i prefer to understand.
What should i do?
Thanks
I took a deeper look at the problem.
The required SEPolicyVersion of lineageos 20 is defined in /system/policy/sepolicy/policy_version.mk. It is 33.
The kernelSepolicyVersion is read in /sys/fs/selinux/policyvers. For the kernel I use, it is 30.
This value comes from /kernel/x/y/security/selinux/include/security.h:
#define POLICYDB_VERSION_XPERMS_IOCTL 30
I need to update my kernel. For now, i have to live with the startup popup "There is an internal problem in your device. Please contact your manufacturer." The warning seems relevant