{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Bugs
What's working:
Boot
RIL (5G/LTE/Dual SIM/SMS)
WiFi
Hotspot (2.4Ghz / 5Ghz)
FM Radio
Bluetooth
Camera / Camcorder
Fingerprint Sensor
Hardware Encryption
GNSS GPS
Audio Playback
Video Playback
HDR
Torch
Always on Display
Widevine DRM L1
NFC
Sensors
USB (ADB/MTP/PTP)
Touch
What's not working:
VoLTE / VoWiFi (Samsung's implementation not gonna work on AOSP)
You tell me.
Installation instructions
Upgrade to OneUI 4.1 (Android 12) first!
Download the zip(s).
Download Odin, from example from https://downloads.corsicanu.ro/samsung/
If not done before, flash disabled VBMeta with Odin in AP or CP slot (originally posted here).
Install a compatible Recovery -> TWRP
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions and FORMAT DATA from TWRP of your device (required when coming from stock!).
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Downloads
Recovery : Unofficial TWRP < USE THIS TO FLASH!
Gapps : MindTheGApps ARM64 12.1
Rom : Download
GCAM: Download
Sources
device tree: sm7225-common
kernel tree: Kernel
vendor tree: vendor tree
Donate
DONATE To Me
Big Thanks
LineageOS Team.
@Simon1511 for A52/SM7125 device trees.
Changelogs
2023/04/28
Fixed 5G toggle on SIM card settings.
Fixed WiFi on A4260 model.
Allowing 3rd-party apps to access AUX cameras.
Fixed "Charging slowly" and "Charging rapidly" hints.
2023/04/11
Updated with 2023 March security patches.
Upstream updates and fixes.
Fixed RIL (5G/LTE/Calls/SMS) - Signal strengths is buggy, but not a big deal.
Thanks to @Simon1511
2022/08/07
Updated with August security patches.
Upstream updates and fixes.
Updated Kernel version to 4.19.254.
Added some missing RIL/GPS blobs.
Support M42 5G model.
2022/07/27
Improved Fingerprint sensor stability, Thanks to @Simon1511 .
Fixed Fingerprint sensor position on the screen.
Fixed lockscreen texts overlapping issue.
Added capabilityconfigstore blobs.
Updated Kernel version to 4.19.253.
Lower vibration intensity.
2022/07/24
Fixed Camera/Camcorder.
Fixed Fingerprint sensor. (A little bit buggy for now)
Updated Kernel version to 4.19.218.
Switched to source-built libril.
Fixed Doze.
Added missing blobs.
Device misc changes.
2022/07/20
Initial release of LineageOS 19.1 for A42 5G.
With 4.19.154 Kernel.
With OSS Vendor.
Screenshots
New build released
Fixed Camera/Camcorder.
Fixed Fingerprint sensor. (A little bit buggy for now)
Updated Kernel version to 4.19.218.
Switched to source-built libril.
Fixed Doze.
Added missing blobs.
Device misc changes.
You are telling me, after waiting a whole YEAR for roms, there's a basically a bugless one. Better go flashing! (volte and vowifi isn't available in my country)
awesomellama3 said:
You are telling me, after waiting a whole YEAR for roms, there's a basically a bugless one. Better go flashing! (volte and vowifi isn't available in my country)
Click to expand...
Click to collapse
Yes, A nice device deserved a nice development environment!
I know, this device is VERY underrated by the modding community, my phone is fast and the battery is great... I bought it for the 750G and the 5000 mAh battery and I don't regret it. It's just that I only have the 4 GB ram model.
awesomellama3 said:
I know, this device is VERY underrated by the modding community, my phone is fast and the battery is great... I bought it for the 750G and the 5000 mAh battery and I don't regret it. It's just that I only have the 4 GB ram model.
Click to expand...
Click to collapse
FYI, I will release another build for more stable fingerprint support and newer kernel version soon.
I mean... as long as it works it works! I also can enter my pin everytime, I do it sometimes on stock too!
Glad to see that there is starting to be more development on A Series devices!
New build released
Improved Fingerprint sensor stability, Thanks to Simon1511.
Fixed Fingerprint sensor position on the screen.
Fixed lockscreen texts overlapping issue.
Added capabilityconfigstore blobs.
Updated Kernel version to 4.19.253.
Lower vibration intensity.
hey, ril isn't working, sorry to bother you again
awesomellama3 said:
hey, ril isn't working, sorry to bother you again
Click to expand...
Click to collapse
Can you provide more detail?
Like:
Your stock ROM version?
Your Model name?
Did you format data before installing?
Can you grab logs for me?
Code:
logcat -b radio
Android 12.0, one ui 4.1, july security patch update
SM-A426B, OMN csc originally
I did, and formatted data and cache
I don't know if these are enough logs but here, they keep occouring ever so often:
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] Remove all timers
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] DefaultState: process EVENT_PHYSICAL_CHANNEL_CONFIG_NOTIF_CHANGED
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] mIsPhysicalChannelConfigOn changed to: false
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] Remove all timers
07-27 17:24:16.924 2142 2224 D RILJ : [0568]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error 1 [PHONE1]
07-27 17:24:16.924 2142 2224 D RilRequest: [0568]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret= result=null
07-27 17:24:16.925 2142 2224 D RILJ : [0569]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error 1 [PHONE1]
07-27 17:24:16.925 2142 2224 D RilRequest: [0569]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret= result=null
(edit: when i try to call it freezes for 6 seconds and tells me the network isnt available, then quits)
awesomellama3 said:
Android 12.0, one ui 4.1, july security patch update
SM-A426B, OMN csc originally
I did, and formatted data and cache
I don't know if these are enough logs but here, they keep occouring ever so often:
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] Remove all timers
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] DefaultState: process EVENT_PHYSICAL_CHANNEL_CONFIG_NOTIF_CHANGED
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] mIsPhysicalChannelConfigOn changed to: false
07-27 17:24:16.924 2142 2142 D NetworkTypeController: [1] Remove all timers
07-27 17:24:16.924 2142 2224 D RILJ : [0568]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error 1 [PHONE1]
07-27 17:24:16.924 2142 2224 D RilRequest: [0568]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret= result=null
07-27 17:24:16.925 2142 2224 D RILJ : [0569]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error 1 [PHONE1]
07-27 17:24:16.925 2142 2224 D RilRequest: [0569]< SET_SIGNAL_STRENGTH_REPORTING_CRITERIA error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret= result=null
(edit: when i try to call it freezes for 6 seconds and tells me the network isnt available, then quits)
Click to expand...
Click to collapse
Actually I have the same model as yours, A426B Dual SIM, but RIL SEEMS fine on mine, this is really weird.
For logs, those are not enough and can you try to grab the full logs and attach as file or pastebin links?
Thanks.
EDIT: It can't make a outgoing call with my expired SIM, will try with another SIM later.
Also, is SIM card detected and showing baseband version on About Phone?
@awesomellama3
Mine was expired too, lol sorry for the confusion... I'll try again now that it's working.
By the way your work is AMAZING! I love how every 3/4 days you update it over and over to make it more stable, if there wasn't a beta writing in the title I wouldn't have thought this was unstable.
awesomellama3 said:
Mine was expired too, lol sorry for the confusion... I'll try again now that it's working.
By the way your work is AMAZING! I love how every 3/4 days you update it over and over to make it more stable, if there wasn't a beta writing in the title I wouldn't have thought this was unstable.
Click to expand...
Click to collapse
Can you send some screenshots for RIL related stuff?
I just tried with my main SIM card and seems like it doesn't work lol.
I'm reflashing the rom, so if RIL works then I will have 4G access in the setup
Messages not sending, phone calls not going through saying I need to disable airplane mode which is off and mobile data not loading anything
awesomellama3 said:
Messages not sending, phone calls not going through saying I need to disable airplane mode which is off and mobile data not loading anything
Click to expand...
Click to collapse
Okay, so RIL is dead, I've noticed it here, will try to fix it.
Sorry for inconvenient.
Related
Hello everyone!
Android Wear for Gear 2 / Gear 2 Neo
This thread is about development of Android Wear for Gear 2 & Gear 2 Neo
IF YOU HAVE A QUESTION, ASK IT HERE: http://forum.xda-developers.com/gear-2/help/qa-porting-android-to-gear-2-t3018159
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
Code:
Your warranty is now void. Not only void,
it's not comming back. The moment you
flash anything on this thread you can say
goodbye to it. I almost hard bricked my
watch once. It can happen to you too.
I do my best to post things that aren't
dangerous for the device, but anything
as simple as a 9 instead of a 4 in the GPU
driver might make it overheat and kill it.
Everything here is at your own risk.
You have been warned.
Current development stage
Kernel:: Still work in progress. Most functions are working correctly. Expect some bugs.
GITHUB REPO: Github Android B2 Repository
Recovery:: Minimal image. Not actively worked on, but enough to wipe and access ADB: MediaFire
Android: Most of it is working, and for me at least, IS usable. Some things are still missing and will need to be worked out though.
Working:
Boot
USB: ADB, MTP [july 19th]
Display: Software rendering, OpenGL and mixed compositions
Screen dimming
Screen always on
Battery reporting and charging
Oportunistic Sleep (kernel)
Bluetooth: basic functionality (working for notifications, music control etc), Tethered internet access (still some bugs to work out though)
Vibration
Heart Rate Monitor
Accelerometer sensor
Step counter
Gyroscope (this includes tilt to wake)
Power management: CPU Hotplugging, frequency scaling, Amoled LPM, runtime suspend and opportunistic sleep.
Depending on use, can give from 12 to 48 hours of battery life. Normal use gives me about 18-20 hours with screen always on
Audio: Input and Output
Infrared
Basic TWRP recovery functions
Not working:
Camera
There's no way of playing music to the speaker directly from the watch
There's no gallery app
Palm-on-screen to suspend
Anything that's not specifically put as "working"
Android Wear 6
Remember: These are BETA, things may or may not work. No support, no nothing, just sharing them with you so you can play with them. I already know what works and what doesn't, and I'm trying to fix everything
March 4, 2016: https://mega.nz/#!QQwXQKCD!U-y82wTuBflzdBTrLccxrSLoLkTJUGWtEXMZ6TPikQU
Fixes over previous builds: Text To Speech, IR Support & New Gear Kernel Settings
Previous builds:
Beta #3 (Zenwatch based): https://mega.nz/#!FFYjQCxR!Et4bc8QSXstO1oxlAdXNfq82f7QH4cKsj5tnBNLPZog
Beta #2 (Gear Live based): https://mega.nz/#!IExADLQC!HThMj1Sc_BcPsywQXM0LZopvZd3y1aXiaW-5a5_CHuM
Beta #1 (Gear Live based): https://mega.nz/#!tQJFxSLS!Xu4_xJkW7qlXgz4IUTbFa2RqN8kWcIf0-UZfRTJ0LyM
Android Wear 5.1.1
September 24th, 2015: Android Wear Lollipop - 5.1.1 (build LCA43)
Full flash Package:
Mediafire: http://www.mediafire.com/download/aces995ufltx3vb/Wear_511_LCA43__09_24_2015.zip
Includes: Kernel Settings application, IR App:
** PREROOTED, no need to install anything else
Translate app DOES NOT WORK!
Previous builds:
August 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release,
Full flash Package:
Mediafire: http://www.mediafire.com/download/ar8ir73m32yx05n/Wear_511__08_13_2015.tar
Includes: Kernel Settings application:
* Control vibration intensity
* Control brightness in ambient mode
* Enable / Disable Partial Redraws (enable for best battery life)
* Enable / Disable Idle Mode (reduces color depth in ambient mode to enhance battery life)
July 22nd, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Bugfix release
Full flash Package:
Mediafire: http://www.mediafire.com/download/pr3vljpdecep0dd/wear_511__07_22_2015.tar
md5: def249f18214c7ca00a5bc65391d0c0f wear_511__07_22_2015.tar
After flashing the big file, flash one of these, depending on what you need:
ADB only boot image: http://www.mediafire.com/download/cuo5fa95d5tgmv5/bootimage_ADB_ONLY.tar
ADB+MTP boot image: http://www.mediafire.com/download/bs6rwapqcc35sc6/bootimage_MTP_AND_ADB.tar
July 17th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Screen always on in Low Power Mode, MTP Support, @bitstra IR App Updated
Full flash Package:
Mega: https://mega.co.nz/#!0ZxgQYZA!7m986voG9NLYUUx7Nxzx8EiYbdgXxwFi56otuxQFZbM
Mediafire: http://www.mediafire.com/download/k71o1m16g32x65y/Wear__5_1_1__07_19_2015.zip
MD5: deffb5160968d81a4e560416315791eb Wear__5_1_1__07_19_2015.zip
July 13th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J)** Infrared support (thanks @bitstra for your IR app!)
Full flash Package:http://www.mediafire.com/download/6mmb33lftfrr8w8/Wear_511__07_13_2015_Try2.zip
July 12th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Screen always on + Audio IN/OUT modifications
Full flash Package: http://www.mediafire.com/download/myzqnv4bkwa55b3/Wear_5_1_1_07_12_2015.zip
July 5th, 2015: Android Wear Lollipop - 5.1.1 (build LDZ22J) ** Audio support!
Full flash Package: http://www.mediafire.com/download/eths38jax91sgnd/Wear_511_07_05_2015.zip
July 1st, 2015: Android Wear Lolipop - 5.1.1 (buildLDZ22J)
Full Flash Package: http://www.mediafire.com/download/6rzpfswta2s8fg3/Wear_511_07_01_2015.zip
June 27th, 2015: Android Wear Lolipop - 5.1.1 (build LDZ22J)
Full Flash Package: http://www.mediafire.com/download/bmcjbaikve5sob2/Gear2_Wear_Lolipop_5.1.1_06292015.tar.zip
June 27th, 2015: Android Wear Kitkat - 4.4.2W (build KNX01Q)
Full Flash Package: http://www.mediafire.com/download/2ar5ye1vla8g8gf/full_06_27_2015.zip
Everything I have/done with the Gear 2 is available on this folder: https://www.mediafire.com/folder/092gaz7gudh0f/Gear2, in case you want to dig a bit deeper
Installing
Odin: http://www.mediafire.com/download/v67itqpjitxxogi/Odin3_v3.09(1).zip
User @alvaromartinezb has made a really good video explaining what you have to do, check it out! https://www.youtube.com/watch?v=bBqg72z8LOk&feature=youtu.be
@alvaromartinezb Walkthrough video on audio: https://www.youtube.com/watch?v=klYqseFd90g
KNOWN ISSUES
USB doesn't work! --> Check if you're running latest build, check your drivers. Windows 7 may have some issues with MTP
ADB doesn't work! --> You might need to manually install the driver on the device manager in Windows (you can use Google SDK's bundled driver)
Battery doesn't last! --> Be careful with battery hog watchfaces, some will prevent the watch from entering suspend, or keep the heart rate sensor active at all times.
I can't play music from the watch to the speaker --> I haven't found an app that works. We're the only people with a speaker on an Android Wear device, and there aren't many 3rd party apps for that. Driver level is OK
I can't take photos! --> Work in progress, everything takes time, and my watch doesn't even have a camera!
Calls don't get routed through the watch and without it I will die! --> Then go back to Tizen. That functionality doesn't exist in Android Wear, and hundreds of hours of work for a function that probably wouldn't end up working anyway. And I hated it when I had it on Tizen, it only gave my phone issues when connecting to my car's bluetooth handsfree, and forcing me to choose back my phone on each and every call. I'm not developing that. If you want to try to code it yourself and you succeed, I can link to your work if you want, but I'm not wasting my time on that.
Going back to Tizen
BE ADVISED: GOING BACK TO TIZEN MIGHT PROVE DIFFICULT TO ANYBODY WITHOUT KNOWLEDGE OF THE WATCH, SDB, ADB, AND ANYONE WHO DOESN'T USE ODIN. DON'T PM ME FOR IT. IT'S WRITTEN BELOW. ASK IN THE Q&A SECTION PLEASE. THIS IS A DEVELOPMENT THREAD, AND THESE IMAGES ARE FOR DEVELOPMENT ONLY.
BE ADVISED (again): There's no PIT file for this watch. If your favourite flashing app for samsung phones requests one, use Odin. I know, I don't like it either. But we live in a world full of virtual machines with the ability to share USB ports. Now it's your chance to use them if you don't feel like installing Windows in your machine.
*. Walkthrough video by @alvaromartinezb : https://www.youtube.com/watch?v=LhzIqFopQNY&feature=youtu.be
1. Flash this file: http://www.mediafire.com/download/3cg2eazoouur0bs/Tizenmod-Full-Restore.tar
2. When it fails to boot and the screen goes blank, reboot to the bootloader menu and select recovery.
Extreme Recovery mode - Only use if above method doesn't work
YOU NEED TO KNOW HOW TO USE ADB/SDB FOR THIS.
It may happen that you try to recover your watch but for whatever reason it still enters a bootloop when attempting to boot Tizen. This might happen if you played with partitions, if some permissions were set where they shouldn't be, etc. If you enter recovery mode in Tizen and you don't see a confirmation that the watch is being restored to default, you can try this:
*NOTE* This is highly destructive. You do this wrong, your watch might not boot again. I'm not responsible for whatever damage you do to your watch.
First of all download everything from this folder:
https://www.mediafire.com/folder/a1tcatuw1a8t3/Full_Restore
And then follow these steps:
Code:
1. Flash TizenModFull
It will start rebooting itself
2. Flash recovery_fota_cache
3. Enter recovery, and run the following commands through ADB:
adb shell ->
umount /data
mount /dev/block/mmcblk0p15 /system
mount /dev/block/mmcblk0p13 /system/opt
mount /dev/block/mmcblk0p14 /system/opt/usr
rm -rf /system/opt
cp /system/usr/system/RestoreDir/opt.zip /system
cd /system
unzip opt.zip
sync
cd /
umount /system/opt/usr
umount /system/opt
umount /system
Exit the shell and select "Reboot -> PowerOff" from TWRP
4. Now press and hold the power button until "Rebooting..." appears, then enter Download mode
5. Flash kernel_tizen.tar
6. Reboot again to download mode
7. Flash tizenmod2.tar
Some info about the device
Gear 2 specifications
Samsung Exynos 3250, dual core up to 1GHz
512 Mb of RAM
4 Gb of flash, divided in 15 partitions (see below)
Mali 400 GPU, using Exynos DRM driver
YMU381 audio, supported by ALSA
BCM4334W Bluetooth/WLAN controller, already supported by Android in a bunch of phones
Samsung SensorHub (STM32) controlling Gyro/accelerometer and HRM. Supported in the kernel and seen in Android HAL.
Partition layout
bota0 -> ../../mmcblk0p1
bota1 -> ../../mmcblk0p2
csa -> ../../mmcblk0p3 --> ext4 -> /csa
boot -> ../../mmcblk0p5 --> Main Kernel
csc -> ../../mmcblk0p12 --> ext4 -> /system/csc
fota -> ../../mmcblk0p10 --> seems empty
ramdisk-recovery -> mmcblk0p8 -> ext4 -> Unused in tizen --> USED AS BOOT PARTITION IN ANDROID
module -> ../../mmcblk0p9 --> ext4 -> /lib/modules --> USED FOR TWRP IN ANDROID
rootfs -> ../../mmcblk0p15 ext4 "/" --> Root file system, recovery works from here too. If you break it it will only boot to download mode. --> USED AS SYSTEM PARTITION IN ANDROID
system -> ../../mmcblk0p11 EMPTY --> Did samsung start with Android on this thing then changed their minds?
system-data -> ../../mmcblk0p13 --> ext4, /opt --> If you erase this partition, your watch won't boot back into Tizen. Do not touch it unless you have a backup and know your way into restoring it.
user -> ../../mmcblk0p14 EXT4, /opt/usr --> all user data, including the MTP available part (/opt/usr/media) --> USED AS DATA & SDCARD IN ANDROID
Hey,
I am no expert nor able to understand the details but I would like to thank you for this interesting work and I hope a skilled developper will help you through this. I am following this very closely!
Well done!
A little progress update...
I've built a base image for wear with all the required libraries I could find. It wonderfully crashes on the first boot stage:
Code:
- waiting for device -
--------- beginning of main
F/libc ( 94): Fatal signal 6 (SIGABRT) at 0x5e (code=-6), thread 94 (surfaceflinger)
F/libc ( 182): Fatal signal 6 (SIGABRT) at 0xb6 (code=-6), thread 182 (surfaceflinger)
F/libc ( 250): Fatal signal 6 (SIGABRT) at 0xfa (code=-6), thread 250 (surfaceflinger)
F/libc ( 322): Fatal signal 6 (SIGABRT) at 0x142 (code=-6), thread 322 (surfaceflinger)
F/libc ( 379): Fatal signal 6 (SIGABRT) at 0x17b (code=-6), thread 379 (surfaceflinger)
F/libc ( 435): Fatal signal 6 (SIGABRT) at 0x1b3 (code=-6), thread 435 (surfaceflinger)
F/libc ( 489): Fatal signal 6 (SIGABRT) at 0x1e9 (code=-6), thread 489 (surfaceflinger)
F/libc ( 544): Fatal signal 6 (SIGABRT) at 0x220 (code=-6), thread 544 (surfaceflinger)
F/libc ( 600): Fatal signal 6 (SIGABRT) at 0x258 (code=-6), thread 600 (surfaceflinger)
As far as I can guess, surfaceflinger can't start the hw composite device (the mali gpu) and crashes all the time. I think it's all related to the kernel but not too sure if I messed up somewhere else too (probably yes )
Right now I'm trying to clean up the kernel config to get rid of all the useless drivers and get ION working. Any kernel developers out there?
I will be leaving some stuff in Mediafire in case someone's willing to take a look:
https://www.mediafire.com/folder/wts6i0b4byxy0/Wear
Right now:
droid.tar.md5 --> minimal kernel to boot with android adb support
Kernel-Config-Android-ADB-minimal --> config file for the kernel (with mimal android support and part of the settings -no video-)
system.tar.md5 --> trashed up image of Android Wear with at least part of the exynos and mali libraries to help it boot. It crashes on boot but adb is available. Also fstab is messed up, but each thing at a time...
CAUTION: As it's always said, I'm in no way responsible for any damage done to your device if things go wrong. Do NOT touch the bootloader. And keep a ODIN package for restore when you want to go back. This will wipe your Tizen system partition.
Great work!
@biktor_gj i appreciate your development and your hard work! I really hope that you will succeed! My personal life is very stressing, and my laptop is down to help you in any way! I just wrote this to congrats your ambition and continuous work on this amazing smartwatch, that i just bought it for 1 week!
Awesome to see some development for our Gear 2! Congrats @biktor_gj and please keep it up! :good:
Looking forward to test something new, please count me in. :good:
I'm really eager to know how development is going on. :good:
Skin1980 may help. He is an awesome developer
Hey, right now stuck in here:
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/gpu/ion/ion_chunk_heap.o
drivers/gpu/ion/ion_chunk_heap.c: In function ‘ion_chunk_heap_free’:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
scripts/Makefile.build:307: recipe for target 'drivers/gpu/ion/ion_chunk_heap.o' failed
make[3]: *** [drivers/gpu/ion/ion_chunk_heap.o] Error 1
scripts/Makefile.build:443: recipe for target 'drivers/gpu/ion' failed
make[2]: *** [drivers/gpu/ion] Error 2
scripts/Makefile.build:443: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:948: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I really don't know if kernel source is messed up in purpose, if it's simply an old tree and should be trying to port the board config to a newer release (exynos 3250 support is merged in newer releases I think) or why the h*** it can't find a function that is declared in dma-mapping but not found by the ion driver.
OR it maybe colliding with the exynos drm driver, which seems to not be the same as the one defined in CONFIG_EXYNOS_HW_DRM (which is used by the exynos 3470) and in which the tizen-display module (gear2/neo display driver) depends...
Brain hurts
Wow I would be so happy if I could start using my watch again. Could not handle being on a samsung based rom, and the workarounds have been unpleasant to use.
I hope you are making progress, as soon as this can do anything useful I will flash it to my watch. Wish I could help but I am not a skilled programmer.
Also since the Gear Live is similar though not identical, would using that as a base make it easier to port Android? Might be too dissimilar
biktor_gj said:
Hey, right now stuck in here:
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/gpu/ion/ion_chunk_heap.o
drivers/gpu/ion/ion_chunk_heap.c: In function ‘ion_chunk_heap_free’:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
scripts/Makefile.build:307: recipe for target 'drivers/gpu/ion/ion_chunk_heap.o' failed
make[3]: *** [drivers/gpu/ion/ion_chunk_heap.o] Error 1
scripts/Makefile.build:443: recipe for target 'drivers/gpu/ion' failed
make[2]: *** [drivers/gpu/ion] Error 2
scripts/Makefile.build:443: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:948: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I really don't know if kernel source is messed up in purpose, if it's simply an old tree and should be trying to port the board config to a newer release (exynos 3250 support is merged in newer releases I think) or why the h*** it can't find a function that is declared in dma-mapping but not found by the ion driver.
OR it maybe colliding with the exynos drm driver, which seems to not be the same as the one defined in CONFIG_EXYNOS_HW_DRM (which is used by the exynos 3470) and in which the tizen-display module (gear2/neo display driver) depends...
Brain hurts
Click to expand...
Click to collapse
Maybe I got a hint..
Code:
drivers/gpu/ion/ion_chunk_heap.c:108:4: error: implicit declaration of function ‘__dma_page_cpu_to_dev’ [-Werror=implicit-function-declaration]
A friend of a friend of mine told me this:
"Well either the function is missing or its renamed.."
Made it any sense?
If you make this happen I will gladly pay you. I will finally be able to use this watch again. Its been sitting ever since I realized it was basically a dead platform (Tizen) and I moved away from Samsung phones.
So is it real to port Android wear with working heart rate? camera and IR doesn't matter for me. Want donate to dev if he can make it real
Its the if and camera will become use less what the point. Just buy an android wear watch.
diamantericos said:
Its the if and camera will become use less what the point. Just buy an android wear watch.
Click to expand...
Click to collapse
Hey, i live in Russia where smartwatch on Android Wear with heart meter will cost twice more (2x) than Gear 2
Kniazkoff said:
So is it real to port Android wear with working heart rate? camera and IR doesn't matter for me. Want donate to dev if he can make it real
Click to expand...
Click to collapse
+1 I'll donate too in case if it's became real.
Me too, will donate if successful so keep trying friend we all behind you.
diamantericos said:
Its the if and camera will become use less what the point. Just buy an android wear watch.
Click to expand...
Click to collapse
In my case I got my gear neo before android wear got physical products launched in my country, and theyre quite pricey for what they have... Anyway I guess its a matter of personal taste, I prefer a dual core than an old omap 3 cpu, and before the gear I had a Motoactv and the screen burnt. By itself. Big black spot in the middle... Just as the warranty period ended. So not buying from them anytime soon
Now back to the point, I temporarily had to stop this because it was driving me nuts, I was using an old mac mini as a development machine and it took me 5 hours to compile cyanogenmod. Just got new hardware so this week I hope Ill find some time to get back to testing!
Will keep you tuned if I can accomplish something more than getting a kernel crash
Sent from my Xperia Z using XDA Free mobile app
biktor_gj said:
In my case I got my gear neo before android wear got physical products launched in my country, and theyre quite pricey for what they have... Anyway I guess its a matter of personal taste, I prefer a dual core than an old omap 3 cpu, and before the gear I had a Motoactv and the screen burnt. By itself. Big black spot in the middle... Just as the warranty period ended. So not buying from them anytime soon
Now back to the point, I temporarily had to stop this because it was driving me nuts, I was using an old mac mini as a development machine and it took me 5 hours to compile cyanogenmod. Just got new hardware so this week I hope Ill find some time to get back to testing!
Will keep you tuned if I can accomplish something more than getting a kernel crash
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Much appreciated thanks.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What works
Booting (yeyyy)
RIL (calls,sms etc)
Wifi
Bluetooth
Sensors
GPS
What doesn't work
Audio (Mic, Music, Notifications, etc.)
Camera
Fingerprint
Haven't test anything else.
Known Bugs
LTE doesn't work
App switcher button doesn't work (hopefully fixed in the next build)
How to install it?
Download TWRP recovery from here
Flash the recovery (fastboot flash recovery BLU_PURE_XL_twrp.img)
Download CyanogenMod zip.
Boot to TWRP recovery
Do a wipe /Factory reset (IMPORTANT)
Flash the CyanogenMod zip
Flash Gapps zip(optional)
Done reboot and test
Download: Here
XDA:DevDB Information
[ROM][5.1][UNOFFICIAL]CyanogenMod 12.1 , ROM for the Blu Pure XL
Contributors
root-expert, acheron1502, redmi-note2 dev team, mtker
Source Code: https://github.com/root-expert/android_device_BLU_BLU_PURE_XL
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-05-03
Last Updated 2016-05-05
Reserved
Changelogs
Version 20160502
Intial commit
Reserved
Still a few things to iron out, but wanted to show everyone how far we have come
NOTE: I have only tested this ROM with my version of TWRP (link in my signature)
Good job guys!
From what I see from your code my version of TWRP should also allow users to flash CM (untill you add exact assert device line).
Can you post here some screenshots? My Allview seems to be dead
bemolx said:
Can you post here some screenshots?
Click to expand...
Click to collapse
Looks like barebones CM 12.1
Screenshots will come once we get Camera working
amazing!!!!! download to test an view this rom
testing and not working lte only run in 3g
2 button workin home and back the other not working
gionfj said:
testing and not working lte only run in 3g
2 button workin home and back the other not working
Click to expand...
Click to collapse
Thanks for reporting! I'll fix keys in the next build and I'll look into LTE
Hello, I've been testing this build for a few days. Things I noticed:
Mobile hotspot missing
Strict mode is forced on even with the setting turned off
Haptic feedback missing from regular taps on hardware keys
Videos freeze (possibly audio related)
Also, I've been noticing some weirdness with the notification light. It stays solid green off the charger and with no notifications and turns... yellow while charging.
Ashalinia said:
Hello, I've been testing this build for a few days. Things I noticed:
Mobile hotspot missing
Strict mode is forced on even with the setting turned off
Haptic feedback missing from regular taps on hardware keys
Videos freeze (possibly audio related)
Also, I've been noticing some weirdness with the notification light. It stays solid green off the charger and with no notifications and turns... yellow while charging.
Click to expand...
Click to collapse
Thanks for reporting!
I'll look into hotspot
Don't bother about strict mode i'm building in eng cause these are alpha builds
I'll check vibrator too
I believe they are audio related. I have to take a look at the logs though.
Don't mean to rush but any news on an update to fix sound? That's really the only thing keeping this from a daily driver for me.
Audio still not fixed yet
@root-expert is doing school exams right now & I am working crazy hours for my job.
We are trying to find time here and there, but Life does come first.
Please be patient as we squash bugs.
If you have logcats that you can post, that might also help us out. :highfive:
This is what I got when I played a song through the default CM music player, hopefully this helps.
Code:
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 48000,format 1, channels 3, flags 4
05-10 16:52:22.945 E/AudioTrack(25444): Could not get audio output for stream type 1, usage 0, sample rate 48000, format 0x1, channel mask 0x3, flags 0x4
05-10 16:52:22.946 E/SoundPool(25444): Error creating AudioTrack
05-10 16:52:22.949 I/MediaFocusControl(25444): AudioFocus requestAudioFocus() from [email protected][email protected] req=1flags=0x0
05-10 16:52:22.953 E/MediaPlayer(16725): Attempt to call getDuration without a valid mediaplayer
05-10 16:52:22.953 E/MediaPlayer(16725): error (-38, 0)
05-10 16:52:22.955 E/MediaPlayer(16725): start called in state 0
05-10 16:52:22.955 E/MediaPlayer(16725): error (-38, 0)
05-10 16:52:23.091 E/ (25444): cyw:virtual int CwMcuSensor::readEvents(sensors_event_t*, int):985:id:0,data:-1.39:5.30:8.10:T:78594939796932:now time:78595077298846:diff:137
05-10 16:52:23.369 E/MediaPlayer(16725): Error (-38,0)
05-10 16:52:23.369 W/MusicPlaybackService(16725): Music Server Error what: -38 extra: 0
05-10 16:52:23.372 E/MediaPlayer(16725): Error (-38,0)
05-10 16:52:23.372 W/MusicPlaybackService(16725): Music Server Error what: -38 extra: 0
05-10 16:52:23.749 E/ (25444): cyw:virtual int CwMcuSensor::readEvents(sensors_event_t*, int):985:id:0,data:-0.99:5.21:8.19:T:78595599796932:now time:78595735398769:diff:135
Ashalinia said:
This is what I got when I played a song through the default CM music player, hopefully this helps.
Code:
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
05-10 16:52:22.945 W/AudioPolicyManager(25217): getOutput() could not find output for stream 1, samplingRate 48000,format 1, channels 3, flags 4
05-10 16:52:22.945 E/AudioTrack(25444): Could not get audio output for stream type 1, usage 0, sample rate 48000, format 0x1, channel mask 0x3, flags 0x4
05-10 16:52:22.946 E/SoundPool(25444): Error creating AudioTrack
05-10 16:52:22.949 I/MediaFocusControl(25444): AudioFocus requestAudioFocus() from [email protected][email protected] req=1flags=0x0
05-10 16:52:22.953 E/MediaPlayer(16725): Attempt to call getDuration without a valid mediaplayer
05-10 16:52:22.953 E/MediaPlayer(16725): error (-38, 0)
05-10 16:52:22.955 E/MediaPlayer(16725): start called in state 0
05-10 16:52:22.955 E/MediaPlayer(16725): error (-38, 0)
05-10 16:52:23.091 E/ (25444): cyw:virtual int CwMcuSensor::readEvents(sensors_event_t*, int):985:id:0,data:-1.39:5.30:8.10:T:78594939796932:now time:78595077298846:diff:137
05-10 16:52:23.369 E/MediaPlayer(16725): Error (-38,0)
05-10 16:52:23.369 W/MusicPlaybackService(16725): Music Server Error what: -38 extra: 0
05-10 16:52:23.372 E/MediaPlayer(16725): Error (-38,0)
05-10 16:52:23.372 W/MusicPlaybackService(16725): Music Server Error what: -38 extra: 0
05-10 16:52:23.749 E/ (25444): cyw:virtual int CwMcuSensor::readEvents(sensors_event_t*, int):985:id:0,data:-0.99:5.21:8.19:T:78595599796932:now time:78595735398769:diff:135
Click to expand...
Click to collapse
Don't worry about the logcats guys i have collected infos and i haven't understood yet why audio is crashing. For your rom i have removed one lib so the phone can boot. If i add this lib it will bootloop with audio flinger crashing.
root-expert said:
Changelogs
Version 20160502
Intial commit
Click to expand...
Click to collapse
Hay there I'm thinking of getting a blu pure xl on amazon to replace my HTC one max that Mr flyhalf on xda did great work for us on Cyanogenmod unfortunately my max fall and car ran over it before I can pick it up how was you able to get Cyanogenmod on a mediatek chipset :laugh:
Heres hoping that all Root-experts hard studying gets him super high grades; and his summer can be dedicated to getting this rom working! lol
@root-expert use stock hostapd to fix wifi hotspot maybe this works
Hope your finals went well. Any updates on the build?
My exams are going pretty good. One more week to go and then I'm free... Hope I'll get something good cause audio seems pretty hard to fix it!
In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there.
Known Issues:
1. AOSP Camera App The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that. 2. "E:unknown command [log]" If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP. 3 Please report.
Tips:
1. DT2W At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results. 2. Built-in File Explorer There is an built-in file explorer in AOSP. We can explore the files as well as installing apks.
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)Change log:
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
- Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
- Android-7.1.2_r5 (N2G47J)
- PerformanceControl: boot up settings fixed
- Fix Wifi hotspot
- Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
- Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
- Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
- Android-7.1.1_r13 (N6F26Q)
- Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
- Android-7.1.1_r6 (NMF26Q)
- SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
- Android-7.1.1_r4 (NMF26O)
- Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
- Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
- Android-7.1.0_r4 (NDE36P)
- Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
- Android-7.0.0_r14 (NBD90Z)
- Shield the occasional crash in MTP Document provider
- USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
- Android-7.0.0_r6 (NRD90U)
- latest DC kernel (Android-7.0 branch)
- PerformanceControl: version 2.1.6
- Find a way to fix the hwcomposer for video/audio playback, need to review later
- A few sepolicy patches for Gapps and Mediaserver
- SELinux: Enforcing
Downloads: :highfive:
Hosts: Android File Host MEGA mirror: 百度网盘
Note: I only tested it in TWRP 3.0.2.
PerformanceControl app requires ROOT access.
Root access can be obtained by the systemless SuperSU from @Chainfire.
Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested
Sources:
Sources in github
Credits: :good:
** Definitely the AOSP
** The AndroidFielHost provide a FREE host with no limits and expiration.
** All the developers who help the Nexus 7 (2012) development
** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
Donations: :angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discussions
Anyone has any idea are welcome to post here
DT2W
Sometimes it won't wakeup after a long DEEP_SLEEP
When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
Fail after reboot
Code:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
@millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry wait,check
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic wait,check
Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.
How to recover?
Naturally, you have to flash TWRP again.
First of all, you need to boot into bootloader (fastboot mode)
Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
1. Connect to a charger.
2. Press the power button until you see the charging image
3. Release the power button immediately.
4. After that, press the volume down button first, and then the power button.
It would go to the bootloader.
Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.
For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula.
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Nintonito said:
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Click to expand...
Click to collapse
obviously.
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.
：手指划线：
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
ho0o0o11111 said:
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
Click to expand...
Click to collapse
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
daniel_hk said:
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
Click to expand...
Click to collapse
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
ho0o0o11111 said:
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
Click to expand...
Click to collapse
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
daniel_hk said:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
ho0o0o11111 said:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
Click to expand...
Click to collapse
Which version? eariler version might have a wrong fstab which have issue on f2fs.
Make sure you got the latest version 3.0.2
You can't go to boot loader?
That means you press pwr+vol down and it won't reboot to bootloader?
That's strange.
"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.
You may try this:
1. connect to the charger
2. pressing the pwr button for > 8 seconds.
See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.
If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.
Good luck!
@daniel_hk
Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.
A couple of observations:
As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.
I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL
After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.
Thanks again.
Mike T
Do games work on this rom?
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
paasoares said:
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Click to expand...
Click to collapse
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.
I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.
1. Try factory reset before flashing.
2. Flash ROM+Gapps+SuperSU
3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)
Good luck!
3yan said:
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Click to expand...
Click to collapse
I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.
There is a shell command "getenforce" which you can check the SEPolicy status.
If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com.
Good luck!
fat-lobyte said:
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
Click to expand...
Click to collapse
Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.
I already included some extra permissions which would be include in my later builds.
Anyway, we would encounter denials more often in apps. That's what newer Android intent to do.
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.
But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).
But the story ends well, as my video now works: great job !
fat-lobyte said:
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
Click to expand...
Click to collapse
Did you set "keep wi-fi on during deep sleep" to NEVER?
My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable
[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 by Exynos4 Team
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Exynos4 Team?
The Exynos4 team is composed of the current maintainers for T0LTE/T0LTEKOR for both LineageOS and Resurrection Remix.
(@Option58, @kozmo21 and @PoisonNinja)
Difference between this and official Lineage 14.1
This is more like a bleeding edge build. Upcoming changes/fixes will show up here first, and eventually make it into Lineage official. So, if you want the latest and greatest changes for the Note 2 and than ported to the i9305, if possible, flash this instead of official.
Due to LineageOS rules, if you are switching between official and unofficial builds you will have to clean flash.
Exynos4 Team like to say thanks to:
The great developer community out there. We've had a lot of help from other people.
- the LineageOS team
- the Galaxy S3 LineageOS maintainer github.com/fourkbomb.
- the NamelessROM project github.com/namelessrom.
- xda users for testing and bug reports.
And I want to say thanks to:
PoisonNinja and Option58, who helped me a lot to set up the device tree and vendor blobs for that Exynos4 rom,
which is mainly created or grown out of the hwc idea.
and credits to @p.a.n for his work and providing his changes and patches.
Working
Graphics
Wifi
Data
RIL
Bluetooth (?!?)
Sensors
Vibration
Camera
NFC
Audio
Video Playback
Not working/Bugs/Unknown
[*]GPS is not working currently Fix is in second post!!
Bluetooth audio (may or may not work for you), please check and report back
MTP crashes when uninstalling an app
Installation
Read the FAQ to familiarize yourself with any issues that may come up
Make sure you're using the latest TWRP version
Download and copy latest rom version to the phone, preferably on internal storage
Factory reset in TWRP (Very important! Do not skip)
Format system, cache, dalvik, data
Flash unofficial LineageOS 14.1
Flash Gapps
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
See the FAQ to avoid common issues
For updates, it's OK to dirty flash. If you experience any issues however, it is recommended that you clean flash.
Download
lineage-14.1-20170618-UNOFFICIAL-i9305-HWC.zip: June 18, 2017
6/18/2017 (i9305)
Sync with the latest Lineage sources
Hardware composer fixes
[*] Switch back to proprietary RIL 4.4 blobs
Properly fixed screencast
Lots of security patches in the kernel
Temporarily switched SELinux to permissive
XDA:DevDB Information
LineageOS 14.1 by Exynos4 Team, ROM for the Samsung SIII LTE (i9305)
Contributors
PoisonNinja, Option58, kozmo21, LineageOS team
Source Code: https://github.com/Exynos4
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-06-18
Last Updated 2017-06-18
Just a few info
Root
LineageOS removed builtin root, so you need to flash the root package linked above.
Please test especially calls, incoming and outgoing, mobile data and bluetooth.
The rom/build is based on pans vendor proprietary (ril) blobs and should improve our ril and hopefully fix our reboot problem.
Kernel is set to permissive at the moment. Stickt version also ok.
Please also test bluetooth (audio transfer), because I am not sure, whether it works correct.
GPS is currently not working. Will try to fix that with one of the next builds.
Edit: previous GPS fix is working and solve the problem. Changes will be added in next update.
You can also find it here attached fixed in version: 0702
Other than the HWC and blob changes, the rom is based on pure lineageos sources/repos.
if I need another one
I'm getting bootloops with that build (it doesn't reach far enough for adb to pull the logs). I tried building a build with older blobs yesterday. My build was getting SIGSEGV caused by ks. I'll try building a non hwc version using your blobs and i9305 repository.
I also noticed some reboots, but none anymore during the last night. So I assume that the reboots could not be solved with changing the blobs and also not with that different ril sources/blobs. I doubt that the reboots will be gone with a non hwc version, but we will see. Beside of that are the other things working? Calls, mobile data etc?
Non hwc version booted ok. at_distributor is having problems :
Code:
06-19 03:06:25.941 2812 2812 F libc : CANNOT LINK EXECUTABLE "/system/bin/at_distributor": cannot locate symbol "supportExpandedNV" referenced by "/system/bin/at_distributor"...
06-19 03:06:25.941 2812 2812 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2812 (at_distributor)
but RIL works anyway (at least SMS). I'll try replacing it with stock i9305 at_distributor. I've got one reboot but I didn't launch logcat/kmsg before and had only short last_kmsg. We should try replacing the blobs with the stock i9305 ones because for now they are mixed. We could give a shot to persist.radio.apm_sim_not_pwdn=1 in system.prop too. I haven't tested anything beside RIL reboots (I'm testing it during night and hoping it will manage to reboot before next day because for daily usage I'm going back to the last stable rom).
Many thanks and when you managed to solve the mix up and your tests are ok, it would be good, if you can upload your changes to github. Think it doesn't make sense that we do all the work twice
Edit: seems to be again or still:
Code:
Kernel panic - not syncing: Fatal exception
and I think caused because of:
Code:
<6>[ 184.685341] c0 mdm_hsic_pm_notify_event: unblock request
<6>[ 184.685375] c0 notify_modem_fatal or shutdown
<6>[ 184.685403] c0 ap2mdm_status is high
<6>[ 184.685425] c0 ap2mdm_errfatal is high
<6>[ 184.685449] c0 mdm2ap_status is low
<6>[ 184.685471] c0 mdm2ap_errfatal is low
<6>[ 184.685492] c0 During shutdown, return notify_modem_fatal
rodman01 said:
Many thanks and when you managed to solve the mix up and your tests are ok, it would be good, if you can upload your changes to github. Think it doesn't make sense that we do all the work twice
Edit: seems to be again or still:
Code:
Kernel panic - not syncing: Fatal exception
and I think caused because of:
Code:
<6>[ 184.685341] c0 mdm_hsic_pm_notify_event: unblock request
<6>[ 184.685375] c0 notify_modem_fatal or shutdown
<6>[ 184.685403] c0 ap2mdm_status is high
<6>[ 184.685425] c0 ap2mdm_errfatal is high
<6>[ 184.685449] c0 mdm2ap_status is low
<6>[ 184.685471] c0 mdm2ap_errfatal is low
<6>[ 184.685492] c0 During shutdown, return notify_modem_fatal
Click to expand...
Click to collapse
Don't worry, I'll upload when I have something that's worth uploading. If you got
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
then the issue is still there.
Update
at_distributor from stock references the same function (supportExpandedNV) so the problem rather doesn't lie in the at_distributor itself but in a missing file that contains the missing function.
Update 2
Replacing ks blob with i9305 stock one alone won't work. That leads to the problem that @p.a.n had (https://forum.xda-developers.com/showpost.php?p=64395738&postcount=218) (https://forum.xda-developers.com/showpost.php?p=64448961&postcount=269)
mtr_ said:
Update 2
Replacing ks blob with i9305 stock one alone won't work. That leads to the problem that @p.a.n had (https://forum.xda-developers.com/showpost.php?p=64395738&postcount=218) (https://forum.xda-developers.com/showpost.php?p=64448961&postcount=269)
Click to expand...
Click to collapse
There is a simple solution (or hack to be more precise) to this and I believe I`ve also described it somewhere here - open the ks binary with some binary editor, find the connect string (it should be there twice) and replace it something else with the same length (I used xonnect).
This is a linker related problem, ks contains symbol connect, which replaces connect from libc (I hope it is there, if not it is some other system library), but with a totally different functionality, which causes a crash. Don`t ask me why this is happening in one environment and in other (the old one), I don`t know.
Maybe this last_kmsg looks better now?
Code:
Samsung S-Boot 4.0 for GT-I9305 (Sep 12 2014 - 13:40:58)
EXYNOS4412(EVT 1.1) / 2044MB / 0MB / Rev 2 / I9305XXUFNI3 /(PKG_ID 0xb070018)
BOOTLOADER VERSION : I9305XXUFNI3
PMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
[mmc] capacity = 30777344
MODEL_NAME:{{GT-I9305}}
eMMC_SERIAL_NUMBER:{{1501004D4147344642F74A00ABD19F03}}
- read_bl1
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (4:0xe)
[RPMB] emmc_rpmb_open:
Get DATA success.
[RPMB] emmc_rpmb_close:
initialize_rpmb_data: usable! (GT-I9305:VERSION_-+A3)
PARAM ENV VERSION: v1.0..
set_charger_current: chg curr(3f), in curr(17)
set_charger_state: buck(1), chg(1), reg(0x05)
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
set_auto_current: ta_state(0), curr(700)
init_fuelgauge: fuelgauge power ok
init_fuelgauge: POR status
fuelgauge_por: POR start: vcell(3975), vfocv(4026), soc(79)
fuelgauge_por: update SDI M0 parameter
fuelgauge_por: RCOMP(0x0063), TEMPCO(0x0930)
fuelgauge_por: POR finish: vcell(3977), vfocv(4085), soc(73)
get_table_soc: vcell(3976) is caculated to t-soc(75.735)
init_fuelgauge: start: vcell(3976), vfocv(4081), soc(73), table soc(75)
init_fuelgauge: finish: vcell(3976), vfocv(4081), soc(73), table soc(75)
init_microusb_ic: before MUIC: CDETCTRL:0x2d
init_microusb_ic: after MUIC: CDETCTRL:0x2d
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID = 0x02
PMIC_IRQSRC = 0x00
PMIC_IRQ1 = 0x02
PMIC_IRQ2 = 0x00
PMIC_IRQ1M = 0xff
PMIC_IRQ2M = 0xff
PMIC_STATUS1 = 0x13
PMIC_STATUS2 = 0x00
PMIC_PWRON = 0x01
PMIC_RTCINT = 0x11
PMIC_RTCINTM = 0x3f
s5p_check_keypad: 0x100000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC(0xc1d0c0d6), RST_STAT(0x10000)
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
s5p_check_download: 0
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
check_pm_status: charger is not detected
check_pm_status: voltage(3978) is ok
cmu_div:1, div:7, src_clk:800000000, pixel_clk:38102400
s5p_dsim_display_config: VIDEO MODE
a2, 60, 90,
<start_checksum:481>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:483>offset:50, size:6296
<start_checksum:485>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:20
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
[mobi_drv] add: 0x43e52500, size: 3933
MobiCore INIT response = 0
MobiCore RTM has initialized!
MobiCore IDLE flag = 0
MobiCore driver address 43e52500, size = 3933
MobiCore RTM Notified back!
MobiCore Driver loaded and RTM IDLE!
MobiCore RTM has been uninitialized!
load_kernel: loading boot image from 106496..
Verify_Binary_Signature: failed.
pit_check_signature (BOOT) invalid.
Set invalid sign flag
No need to update kernel type.
SMC Num = 0x83000001
mobismc success!!! [ret = 0]
[s5p_check_sboot_version_rpmb]cur_version:VERSION_-+A3, rpmb_version:VERSION_-+A3
rpmb_version:51, cur_version:51
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 1FC00000 A0000000
ATAG_SERIAL: 4 54410006 42f74a00 abd19f03
ATAG_INITRD2: 4 54420005 42000000 17b548
ATAG_REVISION: 3 54410007 2
check_rustproof [0]
ATAG_CMDLINE: b1 54410009 'console=ram loglevel=4 androidboot.baseband=mdm sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=96 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=471c411f44a4d1cb9c99510ec7e578a1 connie=GT-I9305_OPEN_EUR_10e569b8255514f00b8793d908e78a26 androidboot.emmc_checksum=3 androidboot.boot_salescode= androidboot.odin_download=1 androidboot.bootloader=I9305XXUFNI3 androidboot.selinux=enforcing androidboot.warranty_bit=1 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=42f74a00abd19f03 snd_soc_core.pmdown_time=1000'
ATAG_NONE: 0 0
Starting kernel at 0x40008000...
SWITCH_SEL(3)
p.a.n said:
There is a simple solution (or hack to be more precise) to this and I believe I`ve also described it somewhere here - open the ks binary with some binary editor, find the connect string (it should be there twice) and replace it something else with the same length (I used xonnect).
This is a linker related problem, ks contains symbol connect, which replaces connect from libc (I hope it is there, if not it is some other system library), but with a totally different functionality, which causes a crash. Don`t ask me why this is happening in one environment and in other (the old one), I don`t know.
Click to expand...
Click to collapse
Thanks for hint, I know that you don't work on i9305 anymore. Isn't that connect that comes internally in ks used somewhere ? After all they had to have a reason to place an internal function like that. After you left the development, it seems that the current ks that is being used in LineageOS based roms seems to be taken from other device. The current situation is as follows: the modem crashes from time to time, ks during that crash is having issues during SAHARA protocol file transfer. I don't know whether it is the modem that causes the ks crash, or ks that causes modem crash.
rodman01 said:
Maybe this last_kmsg looks better now?
Click to expand...
Click to collapse
The pasted log contains only what happened after reboot. It shows the next boot. If you wanted to show a crash, it isn't saved. It could be truncated, because last_kmsg has limited buffer (for most of the modem issues it was just too small to show everything). You can use the methods to capture logs I posted somewhere else.
yes I noticed this too after pulling another one.
But with my current used blobs I do not have that:
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
anymore, but still reboots and:
Code:
<6>[ 1581.571051] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 1581.571210] c0 Kernel panic - not syncing: subsystem_restart_wq_func[eac9d720]: Failed to powerup external_modem!
rodman01 said:
yes I noticed this too after pulling another one.
But with my current used blobs I do not have that:
Code:
<6>[ 184.685425] c0 ap2mdm_errfatal is high
anymore, but still reboots and:
Code:
<6>[ 1581.571051] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 1581.571210] c0 Kernel panic - not syncing: subsystem_restart_wq_func[eac9d720]: Failed to powerup external_modem!
Click to expand...
Click to collapse
Still not good. Have you tried modyfing the stock ks as @p.a.n wrote ? I think that the blobs can be swapped on already installed Android, without recompiling everything. Doing adb push should work too. Something like: adb root, adb remount, adb push, reboot.
I know that this is not good.
No I haven't, I have no such editor and haven't searched for it. Have you tried that already?
rodman01 said:
I know that this is not good.
No I haven't, I have no such editor and haven't searched for it. Have you tried that already?
Click to expand...
Click to collapse
Any hex editor should be enough (for Windows you could try https://mh-nexus.de/en/hxd/ ). I haven't tried yet, I returned to stock rom.
mtr_ said:
Thanks for hint, I know that you don't work on i9305 anymore. Isn't that connect that comes internally in ks used somewhere ? After all they had to have a reason to place an internal function like that. After you left the development, it seems that the current ks that is being used in LineageOS based roms seems to be taken from other device. The current situation is as follows: the modem crashes from time to time, ks during that crash is having issues during SAHARA protocol file transfer. I don't know whether it is the modem that causes the ks crash, or ks that causes modem crash.
Click to expand...
Click to collapse
I actually do work on it, just don`t publish, since I was under impression that the official version is fine and the problem you are describing here is caused by old version of modem. I didn`t want to change it, so I solved the problem by using the KitKat RIL with the modification I mentioned.
As far as I know the connect symbol in the ks binary is used only internaly (and shouldn`t be exported at all). It seems like a simple name colision, which was handled differently in KitKat. I`ve been using the modified ks for a long time and it doesn`t seem to have any negative side effect.
I`ll try to put together all the changes against the official code I have and publish again some of my builds. LineageOS 14.1 is quite stable on my device, so I hope this will help you. I just cannnot promise, when this will be, since I am pretty bussy now (more I`ve ever been).
I am uploading at the moment a new test build, where in my logcat no at distributor error and no SIGABRT error or message is to be seen at the moment. Maybe someone is around who is willing to test it....?!?
New test build is uploaded now.
Its based on todays leos sources and nameless/crazyweasel 3.0 vendor/blobs.
Download
lineage-14.1-20170621-UNOFFICIAL-i9305-hwc.zip: https://www.androidfilehost.com/?fid=673368273298966239
Please report back about reboots and or any other error or bug.
GPS is fixed and should work now.
p.a.n said:
I actually do work on it, just don`t publish, since I was under impression that the official version is fine and the problem you are describing here is caused by old version of modem. I didn`t want to change it, so I solved the problem by using the KitKat RIL with the modification I mentioned.
Click to expand...
Click to collapse
Lucky. It seems that by doing that you avoided the RIL problems (and thus saved time ). The thing worth mentioning is that there are quite new stock releases available (I9305XXSFQ series).
rodman01 said:
New test build is uploaded now.
Its based on todays leos sources and nameless/crazyweasel 3.0 vendor/blobs.
Please report back about bootloops and or any other error or bug.
GPS is fixed and should work now.
Click to expand...
Click to collapse
Tested, unfortunately bootloops. Did you try it after a dirty flash or a clean one ?
I made a non hwc build with https://github.com/CrazyWeasel/proprietary_vendor_samsung/tree/n-3.0/i9305 and modified ks from https://github.com/p-an/android_device_samsung_i9305/blob/cm-14.1/proprietary/system/bin/ks . ks works, at_distributor doesn't whine about missing symbol, but that it can't connect to ATD.
Code:
06-22 04:24:28.916 5290 5290 V AT_Distributor_diag: can't connect to atd socket
06-22 04:24:29.046 5293 5293 V AT_Distributor_diag: ConnectToATD
I was running the build for an hour, so not long enough to tell whether the modem issue appears. 4:50 AM, time to get back to stock
I had a reboot during the night too. And now, since the last half an hour, several reboots again. So I would say, this test version is almost unusable at the moment. Did a clean flash after changing to crazyweasel blobs.
App that helps you monitor Android IDs on your Android devices.
Looking for a Command Line Tool? see The Original Thread.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes
Root privilege is required.
Works on Android 8+. (Target 8.1 API27/Min 8.0 API26)
Please be advised that any modification can be harmful to your system. Always make a backup to keep your data safe.
More features may be coming in the further versions!
Supported Features
Look up IDs
Modify IDs
Backup the settings (export current settings) Coming soon
Restore settings (import settings) Coming Soon
Detect corrupted setting file Not yet supported
Usage and Confusion Clarify
Open the app.
Root privilege is required.
A toast is shown on the app startup to indicate whether root permission is granted or not.
The app will NOT work if root permission is not available.
Tap on an app in the list that you want to work with.
A pop-up box will show up.
Modify the values in the text boxes.
These values should be hex-strings and should be exactly 16 characters long.
A hex string is a string that consists of only digits and characters from 'a' to 'f'.
The app automatically guarantees these properties.
It's not possible to input invalid characters.
If the value does not match the requirements, the "Commit" button will be grayed out.
What are "Current ID" and "Default ID"?
See this post.
"current ID" and "default ID" corresponds to "value" and "default value" in the above post.
Tap on the green SAVE button in the bottom right corner.
Settings will be written back to the system only if you press this button.
Restart your phone.
Changes will take effect on the next boot.
Known Bugs
Allow invalid values option will not work. (Not implemented and will be removed)
There are no known bugs currently for the latest version (0.9.3). If you do find a bug somewhere, please let me know. Thank you!
Change Log
v0.9.3-stable (16/Apr)
Slight UI adjustments.
Performance improvements.
v0.9.2-stable (13/Apr)
Entirely re-designed UI.
Added the "save changes" button. Settings won't be written back immediately after a commit now.
v0.9.1-stable (12/Apr)
Random generation function added.
Fully disallow invalid IDs. (Confirm button disappear if the inputted ID is invalid)
A new key is used to sign the apk file; please uninstall previous versions first if there are any.
v0.9.0 (12/Apr)
Major performance improvements.
Major stability improvements.
Validate IDs inputted.
Re-designed output generator for better file layout.
UI adjustments.
Apps will now be listed in ascending order in terms of their names.
v0.0.1 (11/Apr)
First experimental release.
Downloads
Please find the attachments below!
------------------------------------------------------------------------------------------------------------------------------------------------------
I'll update this thread soon, heading out for food now.
Hi,
Firstly thanks for making this app.
I am currently using 8.0 on S7 edge (935F).
v0.9.2 works perfectly without any problem, however v0.9.3 crashes when I press commit after changing the ID and when I press confirm button at save changes window.
I will test it on a new oreo 8.1 i hope.your app its working good...
Now after format, i install my banking app ( which the id needs for the restore)
But i can find it in the applist!?
I start the app, reboot but nothing not in the list ... In my stock rom can i find the app and backup no problem ... I install lineage os 15.1 ...
longsheep said:
Hi,
Firstly thanks for making this app.
I am currently using 8.0 on S7 edge (935F).
v0.9.2 works perfectly without any problem, however v0.9.3 crashes when I press commit after changing the ID and when I press confirm button at save changes window.
Click to expand...
Click to collapse
Sorry , I couldn't reproduce the issue you have encountered.
Please make sure your config file is both syntax and semantic valid, otherwise there does may be some errors while parsing it.
I will, too, look into the source code and see if anything is going wrong.
Anyway, thanks for reporting, any progress I make, I'll let you know.
yasars said:
I will test it on a new oreo 8.1 i hope.your app its working good...
Now after format, i install my banking app ( which the id needs for the restore)
But i can find it in the applist!?
I start the app, reboot but nothing not in the list ... In my stock rom can i find the app and backup no problem ... I install lineage os 15.1 ...
Click to expand...
Click to collapse
This app works by accessing the ssaid config file, which is located at /data/system/users/0/settings_ssaid.xml and is merely a regular xml document.
You can always manually edit this config file with a root explorer, which can be a workaround in your case.
My app isn't listed?
Hey
First of all thanks a lot for this app! Great work.
But sadly v0.9.3 isn't working for me. As soon as I hit the "commit" button, the app stops.
v0.9.2 however is working fine. So it's not a problem for me really, but you may want to look into it for future versions.
I'm using ExperienceOS R40.0 (Android 8.0.0, OnePlus 3), which is based on the official OxygenOS.
Newest version crashes when pressing commit
You know what would be awesome? A way to change ALL APP IDs at once with a "master" ID that you could set, or simply set a "master" which you would then open the app on the list and click Copy from master, and it would paste the ID you set as master.
Just an idea!
Tribes11 said:
You know what would be awesome? A way to change ALL APP IDs at once with a "master" ID that you could set, or simply set a "master" which you would then open the app on the list and click Copy from master, and it would paste the ID you set as master.
Just an idea!
Click to expand...
Click to collapse
I very much like that idea! Just like it used to suffice to restore a device ID with Titanium.
It would already be very helpful if IDs didn't have to be entered manually, backup/restore buttons would be awesome.
I've successfully fooled LastPass with this Device ID Changer so major thanks for that!
There's one app that still doesn't work though: itsme, the Belgian mobile ID app. After every clean flash (which is every 1 or 2 weeks) I have to go through a very cumbersome process to set it up again. Restoring its ID works and the app boots without any errors but it doesn't go beyond the splash screen. Is there anything else it could be looking for besides root and ID?
+1 for the idea of changing all the ids at once
---------- Post added at 09:59 AM ---------- Previous post was at 09:59 AM ----------
but it seems that atm the developer has abandoned this app very quickly. Lots of stuff unfinished. Latest version crashing and no answer from developer
Stability of previous version?
Just wanted to see if the v0.9.2-stable is stable enough to flash and run until the developer picks this project or another dev takes over.
If anyone could let me know, this is a business phone that actually needs this feature so I don't want to do anything to drastic as it is a Nexus 6p and last thing I want to do is throw it into infinite boot loop. It's running 8.1 Oreo right now. Any input from anyone would be greatly appreciated.
leadlaboratories said:
Just wanted to see if the v0.9.2-stable is stable enough to flash and run until the developer picks this project or another dev takes over.
If anyone could let me know, this is a business phone that actually needs this feature so I don't want to do anything to drastic as it is a Nexus 6p and last thing I want to do is throw it into infinite boot loop. It's running 8.1 Oreo right now. Any input from anyone would be greatly appreciated.
Click to expand...
Click to collapse
I've successfully fooled LastPass with it so it's stable on my end but that doesn't mean it will be on your end. I wouldn't recommend messing with a business phone though. Even more so if you're unsure on how to deal with a bootloop.
FYI: I'm running it on a OnePlus One, also on 8.1 Oreo (Resurrection Remix).
Timmmmaaahh said:
I've successfully fooled LastPass with it so it's stable on my end but that doesn't mean it will be on your end. I wouldn't recommend messing with a business phone though. Even more so if you're unsure on how to deal with a bootloop.
FYI: I'm running it on a OnePlus One, also on 8.1 Oreo (Resurrection Remix).
Click to expand...
Click to collapse
Thank you for your response. I will weigh any other options and with it being a business phone, it is one of many I have, I just am just setting this device up for a project model and need a device ID changer, like on older Marshmallow and Nougat phones that I have used. Just didn't realize that they had made Device ID app based, which is a pain now.
I have my personal Mate 9 but would prefer to try on the 6p as I have found it easier to fix issues on and is less expensive to replace, if something drastic were to happen. If I feel ballsy enough, I will report my results with that version here as well.
Awesome name and avatar by the way, thanks again.
neat apps mate! keep it up!
Thanks for making this app.
It helps to bypass uber eats app restrictions.
Thangamatg said:
Thanks for making this app.
It helps to bypass uber eats app restrictions.
Click to expand...
Click to collapse
What kind of restrictions? I haven't encountered any with Uber Eats.
Thanks for This app
Thanks for this app!!!
Hi,
I'm using the latest LineageOS 15 on my Huawei Nexus 6P and since some period of time (unfortunately I can't determine this exactly) I have troubles changing the Device ID (SSAID).
At the beginning of summer I was using "Device ID Changer" and it worked. Today I wanted to change the SSAID again and it didn't work anymore.
I tried several other tools and none is working. So I found this thread and gave your app a try.
As soon as I tap "commit" it crashes:
Code:
09-17 19:05:06.509 20466 20466 D AndroidRuntime: Shutting down VM
09-17 19:05:06.510 20466 20466 E AndroidRuntime: FATAL EXCEPTION: main
09-17 19:05:06.510 20466 20466 E AndroidRuntime: Process: tw.com.constarwu.deviceidchanger, PID: 20466
09-17 19:05:06.510 20466 20466 E AndroidRuntime: java.lang.IndexOutOfBoundsException: Index: 99, Size: 60
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at java.util.ArrayList.set(ArrayList.java:453)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at tw.com.constarwu.deviceidchanger.f.a(Unknown Source:32)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at tw.com.constarwu.deviceidchanger.a$2.onClick(Unknown Source:22)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at android.support.v7.app.AlertController$b.handleMessage(Unknown Source:23)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
09-17 19:05:06.510 20466 20466 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
09-17 19:05:06.520 4328 6951 W ActivityManager: Force finishing activity tw.com.constarwu.deviceidchanger/.ActivityMain
09-17 19:05:06.547 4328 4608 I ActivityManager: Showing crash dialog for package tw.com.constarwu.deviceidchanger u0
Maybe it has nothing to do with your app and the reason is in some way my device, but I don't know where else to look further. Maybe the logcat gives you a hint.
Does anyone test this app on Android Pie? I know the thread is for Oreo. Just wanna see if there is anything equivalent for android pie.
Thanks.